Reference: Application based properties

The application related configuration of nJAMS Client for Mule4 takes place in a separate nJAMS properties file for each MuleSoft Runtime Engine application instance. Typically the name of the application related nJAMS property file follows this pattern: <name_of_service>_njams4.json. You can edit the properties file according to your needs.

This is the reference of available application related nJAMS Client for Mule4 properties.


Any change in this configuration file requires a re-start of the MuleSoft Runtime Engine application instance.



Controls operation mode of the nJAMS Client for Mule4:

complete nJAMS Client for Mule4 will monitor flows of MuleSoft Runtime Engine (default).

exclusive nJAMS Client for Mule4 will only monitor flows of MuleSoft Runtime Engine that generate nJAMS event(s) on the execution path. When there is no nJAMS event created on the execution path, nJAMS Client for Mule4 does not send a log message.

none the nJAMS Client for Mule4 functionality is completely disabled.


Loglevel controls the log level of a MuleSoft Runtime Engine application. For example, if logLevel = ERROR, nJAMS Client for Mule4 will only send log events, when an error event is generated during execution.


Valid values for Loglevel can be:

0: Info (default)

1: Success

2: Warning

3: Error


This setting allows to exclude executions from being monitored by nJAMS.


Turn on/off excluding MuleSoft Runtime Engine flow executions.

true excludes flow.

false do not exclude flow (default).

Activity configuration

Contains Tracing and Extract configuration for activities.

For example:

"activities" : {
"ClassificationByGenre" : {
    "tracepoint" : {
    "starttime" : "2019-11-05T08:00:00.000",
    "endtime" : "2019-11-05T09:00:00.000",
    "iterations" : 0,
    "deeptrace" : false

Data Masking

Data Masking allows you to mask particular parts of Trace Data, which should remain confidential. Assume you have Tracing enabled for an activity that processes password information. By default, the nJAMS UI provides Trace Data including the password information in plain text. To prevent password information from being shown in plain text, you can use Data Masking. This setting can be applied to the entire application or to individual processes.


Enter a regular expression. For example, the following regular expression replaces any information that matches XML tag “Password” in Trace Data with an asterisk character (“*”):

"dataMasking" : [ "<Password>(\\p{Alpha}|/|\\p{Digit})*</Password>" ]


This is an example of an application based nJAMS Client for Mule4 properties file:

"logMode" : "COMPLETE",
"processes" : {
    ">SuperHeroService>Demo>SuperHeroService>getRocketsFlow>" : {
    "logLevel" : "INFO",
    "exclude" : false,
    "activities" : {
        "HTTP /rockets" : {
        "extract" : {
            "name" : "ExtractruleType",
            "extractRules" : [ {
            "attribute" : "businessService",
            "attributeType" : "attribute",
            "ruleType": "value",
            "rule": "SuperHeroService",
            "inout" : "out"
            }, {
            "attribute" : "eventType",
            "attributeType" : "event",
            "ruleType" : "value",
            "rule" : "info",
            "inout" : "out"
            } ]
        "tracepoint" : {
            "starttime" : "2019-10-22T14:28:00.054659",
            "endtime" : "2019-10-22T14:43:00.054659",
            "iterations" : 0,
            "deeptrace" : false
    "recording" : true
"dataMasking" : [ ],
"recording" : true