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.