Reference: Application based properties

The application related configuration of nJAMS Client for ADADB takes place in a separate nJAMS properties file for each TIBCO Adapter for Database Service instance. These property files reside in <TIBCO_ADADB_HOME>/plugins/conf. Typically the name of the application related nJAMS property file follows this pattern: <adapter_service_name>_njams4.json, e.g. adadb_rpc-jmsServer_njams4.json You can edit the properties file according to your needs.

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

Note

Any change in this configuration file requires a re-start of the TIBCO Adapter for Database Service instance.

LogMode

logMode:

Controls operation mode of the nJAMS Client for ADADB:

complete nJAMS Client for ADADB will monitor TIBCO Adapter for Database Service instance (default).

exclusive nJAMS Client for ADADB will only monitor TIBCO Adapter for Database Service instance that executes an Extract. When there is no Extract defined on the execution path, nJAMS Client for ADADB does not send log messages.

none the nJAMS Client for ADADB functionality is completely disabled.

LogLevel

Loglevel controls the log level of a TIBCO Adapter for Database Service instance. For example, if logLevel = 3, nJAMS Client for ADADB will only send log events, when an error event is generated during execution.

logLevel:

Valid values for Loglevel can be:

0: Info (default)

1: Success

2: Warning

3: Error

Exclude

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

exclude:

Turn on/off excluding TIBCO Adapter for Database Service executions.

true excludes process.

false do not exclude process (default).

Activity configuration

Contains Tracing and Extract configuration for activities.

For example:

"activities" : {
"ClassificationByGenre" : {
    "tracepoint" : {
    "starttime" : "2018-11-11T08:00:00.000",
    "endtime" : "2018-11-11T09: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.

dataMasking:

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>" ]

Example

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

{
"logMode" : "COMPLETE",
"processes" : {
    ">fs_endurance>adadb_rpc>adadb_rpc-jmsServer>ADBServer>" : {
    "logLevel" : "INFO",
    "exclude" : false,
    "activities" : {
        "ADADB_START" : {
        "extract" : {
            "name" : "ExtractruleType",
            "extractRules" : [ {
            "attribute" : "SQLstatement",
            "attributeType" : "attribute",
            "ruleType" : "xpath",
            "rule" : "//*:SQL__STRING",
            "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
}