Using nJAMS Client for BW in “exclusive” mode

You can control the fundamental mode of operation of nJAMS Client for BW by configuring the log mode. You can enable and disable nJAMS Client for BW by setting logMode to complete, respectively none. But beyond that you can also run nJAMS Client for BW in exclusive mode, which means nJAMS Client for BW is enabled, but only sends event messages, when an nJAMS activity is executed in the process execution path. Please assume the following scenario: you have a poller process that permanently polls for the existence of a file. In case the file exists, the process is processing the file, otherwise the process terminates immediately without doing anything. Normally, nJAMS Client for BW would trigger an event message every time the process polls for a file. If you presume that in most of the process calls the file does not exist, respectively in only a very few cases the file is present and being processed, a lot of nJAMS events are actually unnecessary. Basically you are only interested in the very few process executions, where the polling is successful and the file is being processed. Only in these few cases you want nJAMS to perform its magic and send event messages. You can exactly achieve this by setting logMode to exclusive.

See the following figures how exclusive mode works:

In the case above, no log events are sent to your nJAMSInstance.

In the following case, nJAMS events are sent:

The LogInfo activity is executed and therefore this case and all related log information will be shown in the user interface. That results in only one entry in nJAMSUI: