Reference: Application based configuration¶
The application related configuration of nJAMS Client for BW6 takes place in a separate nJAMS properties file for each AppNode.
These property files reside in <TIBCO_HOME>/bw/<VERSION>/config/njams
.
Typically the name of the application related nJAMS property file follows this pattern: <DOMAIN>_<APPSPACE>_<APPNODE>_<APPLICATION>.application.json
, e.g. bw6_endurance_bw6_endurance_appspace_bw6_endurance_node1_HFMService.application.json
You can edit the properties file according to your needs.
This is the reference of available application related nJAMS Client for BW6 properties.
Note
Any change in this configuration file requires a re-start of the BW6 AppNode, respectively of the BW6 application.
LogMode¶
logMode: | Controls operation mode of the nJAMS Client for BW6:
|
---|
LogLevel¶
Loglevel controls the log level of an individual application.
logLevel: | Valid values for Loglevel can be: 0: Info (default) 1: Success 2: Warning 3: Error |
---|
Exclude¶
This setting allows to exclude individual processes from being monitored by nJAMS.
exclude: | Turn on/off exclujding processes.
|
---|
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
}
}
Recording¶
Enables/disables recording data for nJAMS Replay. This setting can be applied to the entire application or to individual processes.
recording: | Turn on/off recording.
|
---|
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 (“*”):
|
---|
Example¶
This is an example of an application based nJAMS Client for BW6 properties file:
{
"logMode" : "COMPLETE",
"processes" : {
">bw65_domain>bw65_appspace>bw65_appnode>tibco.bw.sample.core.soa.CallProcess.application>tibco/bw/sample/core/soa/callprocess/MainProcess>" : {
"logLevel" : "INFO",
"exclude" : false,
"activities" : {
"ClassificationByGenre" : {
"tracepoint" : {
"starttime" : "2018-11-11T08:00:00.000",
"endtime" : "2018-11-11T09:00:00.000",
"iterations" : 0,
"deeptrace" : false
}
"extract" : {
"name" : "ExtractruleType",
"extractRules" : [ {
"attribute" : "MovieName",
"attributeType" : "attribute",
"ruleType" : "xpath",
"rule" : "//*:movieName",
"inout" : "in"
} ]
}
}
},
"recording" : true
},
">bw65_domain>bw65_appspace>bw65_appnode>tibco.bw.sample.core.soa.CallProcess.application>tibco/bw/sample/core/soa/callprocess/OtherMoviesList>" : {
"logLevel" : "INFO",
"exclude" : false,
"activities" : {
"Start" : {
"extract" : {
"name" : "ExtractruleType",
"extractRules" : [ {
"attribute" : "Movie",
"attributeType" : "attribute",
"ruleType" : "xpath",
"rule" : "//*:movieName",
"inout" : "in"
} ]
}
}
},
"recording" : true
}
},
"dataMasking" : [ ],
"recording" : true
}