Reference: Application based properties#
The application related configuration of nJAMS Client for ADR3 takes place in a separate nJAMS properties file for each TIBCO Adapter for SAP Service instance.
These property files reside in <TIBCO_SAP_ADAPTER_HOME>/plugins/conf
.
Typically the name of the application related nJAMS property file follows this pattern: <adapter_service_name>_njams4.json
, e.g. SAPAdapterServices-OrderService_SAPADR3_IN_njams4.json
You can edit the properties file according to your needs.
This is the reference of available application related nJAMS Client for ADR3 properties.
Note
Any change in this configuration file requires a re-start of the TIBCO Adapter for SAP Service instance.
LogMode#
- logMode:
Controls operation mode of the nJAMS Client for ADR3:
complete
nJAMS Client for ADR3 will monitor TIBCO Adapter for SAP Service instance (default).exclusive
nJAMS Client for ADR3 will only monitor TIBCO Adapter for SAP Service instance that executes an Extract. When there is no Extract defined on the execution path, nJAMS Client for ADR3 does not send log messages.none
the nJAMS Client for ADR3 functionality is completely disabled.
LogLevel#
Loglevel controls the log level of a TIBCO Adapter for SAP Service instance. For example, if logLevel = 3, nJAMS Client for ADR3 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 SAP 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 ADR3 properties file:
{
"logMode" : "COMPLETE",
"processes" : {
">fs_endurance>SAPAdapterServices>SAPAdapterServices-OrderService_SAPADR3_IN>BUPAFS_FS_CREATE_FRM_DATA01Subscriber>" : {
"logLevel" : "INFO",
"exclude" : false,
"activities" : {
"ADR3_PROCESS" : {
"extract" : {
"name" : "ExtractruleType",
"extractRules" : [ {
"attribute" : "correlationlogid",
"attributeType" : "attribute",
"ruleType" : "xpath",
"rule" : "//*:DOCNUM",
"inout" : "in"
} ]
}
},
"ADR3_SEND" : { },
"ADR3_START" : {
"extract" : {
"name" : "ExtractruleType",
"extractRules" : [ {
"attribute" : "correlationlogid",
"attributeType" : "attribute",
"ruleType" : "xpath",
"rule" : "//*:DOCNUM",
"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
}