Basic concepts#
The nJAMS solution consists of the following main components:
nJAMS Client for BW monitors and evaluates process transactions of TIBCO BusinessWorks. nJAMS Client resides within TIBCO BusinessWorks runtime engine / design time environment.
nJAMS Subagent monitors various additional metrics from TIBCO BusinessWorks and resides within nJAMS Client for BW, respectively TIBCO BusinessWorks runtime engine / design time environment.
nJAMS Agent collects metrics from nJAMS Subagent operating on the host where TIBCO BusinessWorks is running.
nJAMS Server instance receives and persists incoming monitoring data, provides presentation and reporting of monitoring data, and furthermore supports rule based alerting.
The following figure shows how nJAMS Client for BW interacts with TIBCO BusinessWorks and other nJAMS components:
nJAMS Client for BW monitors various process information from TIBCO BusinessWorks, e.g. start time, end time, duration, status of process executions and sends event messages to the corresponding nJAMS Instance. In parallel nJAMS Subagent collects various additional metrics from TIBCO BusinessWorks engine and provides these information to nJAMS Agent. nJAMS Agent is a daemon that runs on the same machine and collects metrics information from any nJAMS Subagent as well as metrics from the host the daemon is running on. nJAMS Agent again sends the collected metrics to the corresponding nJAMS Instance.
It is recommended to separate your environments and have individual nJAMS Instances per environment. Assume you have two environments, a development environment and a production environment. In DEV environment nJAMS Client for BW should be pointed to your nJAMS DEV Instance, whereas the PROD environment points to nJAMS PROD Instance:
