Skip to main content
Version: 7.2405.x.x LTS

Technical architecture

Overview

The figure below extends the previous figure Architecture overview by showing the different interfaces within nevisDetect:

Technical architecture

The table below lists the interfaces within nevisDetect:

Interface nameDescriptionTypeProviderConsumer
ICAP (0)ICAP interfaceICAPnevisDetect Feature CorrelatornevisProxy (ICAP filter)
Request Data (1)Interface for forwarding the data of the actual request as well as returning the generated rule in case of synchronous communication.JMS queuenevisDetect CorenevisDetect Feature Correlator
Authentication Data (2)Interface for forwarding the data of the actual authentication as well as returning the generated rule in case of synchronous communication.JMSqueuenevisDetect CorenevisAuth (nevisDetect AuthState)
Statistic (3)Interface for updating the user related statistical data and for persisting generated rules.RESTnevisDetect PersistencynevisDetect Core
Configuration (4)Interface for reading the system configuration and the persisted rules.RESTnevisDetect PersistencynevisDetect CorenevisDetect Feature Correlator
Entities (5)Interface for read/write access to the persisted entities.RESTnevisDetect PersistencynevisDetect Web App
Component Control (6)Interface for getting the runtime status of all nevisDetect components.RESTnevisDetect ControllernevisDetect Web App
Component Status (7)Interface for getting the status of a single nevisDetect component.JMS topicnevisDetect CorenevisDetect Feature CorrelatornevisDetect PersistencynevisDetect Controller

The next table lists the runtime of the nevisDetect components:

ComponentRuntimeRemarks
nevisDetect Feature CorrelatorStandalone JVMTCP/IP server listening on localhost
nevisDetect AuthStatenevisAuth execution environmentAuthState deployed by nevisAuth
nevisDetect CoreStandalone JVMA JMS Messaging Listener
nevisDetect PersistencyServlet containerWeb application implementing REST services
nevisDetect ControllerServlet containerWeb application implementing REST servicesServes the nevisDetect Web App with static content
nevisDetect Web AppBrowserSingle Page Application (SPA) based on Angular 2

Runtime

The following figure shows the asynchronous processing of an HTTP request within nevisDetect:

HTTP request processing

The processing of an HTTP request during authentication is shown in the following figure:

Authentication request processing

Scaling and fail-safeness

Fail-safeness and scaling of nevisDetect is guaranteed by the message bus. The figure below is therefore showing the system from a messaging point of view:

Request data queue

Monitoring

nevisDetect is a distributed system consisting of several components. The runtime status of all components is monitored by JMS topic:

Monitoring nevisDetect

The monitoring described here is displayed in the nevisDetect web application. For machine-related monitoring services, see chapter Liveness and health services.