No change in the TIBCO BusinessWorks ProcessMonitor(BWPM) njams_config.xml on changing the log mode to none/complete from the BWPM Server GUI.

No change in the TIBCO BusinessWorks ProcessMonitor(BWPM) njams_config.xml on changing the log mode to none/complete from the BWPM Server GUI.

book

Article ID: KB0093002

calendar_today

Updated On:

Products Versions
TIBCO BusinessWorks ProcessMonitor -
Not Applicable -

Description

Description:
The 'njams_config.xml' file of TIBCO BusinessWorks ProcessMonitor(BWPM) in the resource folder gets updated at the backend but does not show any changes in the loglevel value when changing log mode. In both cases the entry remains the same, that is <“loglevel="0"/> .
Symptoms:
When choosing a log mode, say complete in the TIBCO BusinessWorks ProcessMonitor(BWPM) Server GUI, the 'njams_config.xml' file which is in the resource folder gets updated but the entry for loglevel remains the same. It will remain as <“loglevel="0"/>.

Cause:
In TIBCO BusinessWorks ProcessMonitor(BWPM), when the log mode is changed from the Server GUI, the loglevel value in the 'njams_config.xml' file is not updated.

Issue/Introduction

No change in the TIBCO BusinessWorks ProcessMonitor(BWPM) njams_config.xml on changing the log mode to none/complete from the BWPM Server GUI.

Resolution

Though the changes are not reflected, the TIBCO BusinessWorks ProcessMonitor(BWPM) client works according to what log mode is set. You can ignore this file shows log level=0 as we are changing the log mode and not the log level.

These are some messages on the EMS command queue that were captured.

Case 1: Setting log mode none.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Instruction xmlns="http://www.faizsiegeln.com/njams/client/plugin/instruction"><Request Command="SetLogLevel"><Parametergroup>
<Parameter Name="domainObjectName" Value="MyProject-Process_Archive"/><Parameter Name="loglevel" Value="0"/>
<Parameter Name="logmode" Value="none"/>
<Parameter Name="exclude" Value="false"/></Parametergroup></Request><Response/></Instruction>

Case 2: Setting log mode complete.


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Instruction xmlns="http://www.faizsiegeln.com/njams/client/plugin/instruction">
<Request Command="SetLogLevel"><Parametergroup><Parameter Name="domainObjectName" Value="MyProject-Process_Archive"/>
<Parameter Name="loglevel" Value="0"/><Parameter Name="logmode" Value="complete"/><Parameter Name="exclude" Value="false"/>
</Parametergroup></Request><Response/></Instruction>

Case 3: Setting log mode exclusive.


<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Instruction xmlns="http://www.faizsiegeln.com/njams/client/plugin/instruction">
<Request Command="SetLogLevel"><Parametergroup><Parameter Name="domainObjectName" Value="MyProject-Process_Archive"/>
<Parameter Name="loglevel" Value="0"/><Parameter Name="logmode" Value="exclusive"/><Parameter Name="exclude" Value="false"/>
</Parametergroup></Request><Response/></Instruction>

As seen in these examples, the value of logmode is changed on changing the log mode but this is not reflected in the 'njams_config.xml' file. (The logmode field is itself absent). On changing the log mode, the loglevel value is unchanged in the message as well as in the 'njams_config.xml' file.