Lifecycle

The Lifecycle page allows nJAMS Administrators to check the state of all internal nJAMS components at a glance. You can also see the dependencies of the components.

Furthermore an nJAMS Administrator can start/stop components on this page. For example, if the ClientCommunication component has to be reset, click on its component state button to stop/start the component.

List of components:

This is the list of nJAMS Server components:

Component	Description
Database	The database component connect to RDBMS via JDBC
JC	Job Controller is the scheduler (Quartz Jobs) for internal Jobs. See chapter ‘Jobs’ above.
FM	FeatureManager is responsible for working with nJAMS features. FM is dependent on the Job Controller.
RES	RulesEngineStatistic component calculates the statistic for the Rule executions
RE	RulesEngine executes Rule instances on matching incoming log messages
RS	Request Store component for Indexer.
I	Indexer component is connected to Elasticsearch and is responsible for Indexing and Searching.
AC	ArgosCache component.
MC	Metrics component processes metrics data required for Argos.
DPC	DataProviderComponent manages DataProvider instances: starting/stopping, check state, etc.

Dependencies of components:

You can see the state and the dependencies of the components on Lifecycle page.

Component is started

Component is stopped

In case all components are started, the state is all green:

In case one of the components is failing, you can identify which dependent component is affected. In the following example, the DataProviderStatistics (DPS) component is stopped which causes the DataProviderController (DPC) component to stop also:

The Database component is the basic component on which all others depend. If the Database component is stopped, all other components will stop as well: