Description:
Currently,  TIBCO BusinessWorks ProcessMonitor (BWPM) does not have a feature to exclude processes time intervals. As a way to exclude/include processes being monitored is to check/uncheck the Exclude check box in the Administrator tab (at top beside the Reports tab) of the process for which you want to monitor. This can be used but it will require the daily manual task of exclude/include processes being monitored.

How to monitor processes in TIBCO BusinessWorks ProcessMonitor (BWPM) over a time span. (Process A should only be monitored from 10.00 AM to 7.00 PM).

Enhancement Request #1994 had been logged for this feature.

Workaround:

A way to Exclude/Include processes being monitored in TIBCO BusinessWorks ProcessMonitor (BWPM) is to check/uncheck the Exclude check box in the Administrator tab (at the top beside the Reports tab) of the process. This will need to be done daily for the process being monitored. For monitoring during a time range (from say, 10.00 AM to 7.00 PM) you will need to implement TIBCO BusinessWorks (BW) code which can enable monitoring @ 10.00 AM and exclude process (disable monitoring) @ 7.00 PM. As internal communication of BWPM server and BWPM client (BW engine) is done via the .command queue, you need to send a message on the .command queue to Exclude/include process.

<<<HERE>>>

Find the attached POC code (Filename: ExcludePOC.zip). There is a timer task which runs every morning at 10.00 AM to enable monitoring of the process "Process A.process". There is one more timer task which runs daily at 7.00 PM to disable/Exclude process "Process A.process". As we should know the exact JMS message to be sent on the EMS queue, we need to capture the JMS message once and can reuse the same message to implement our monitoring strategy. Note that the JMS message contains details such as BW_ENGINE, process details and domain details which differs from process to process and application to application.

Steps to implement the workaround:

1). Start monitoring temporary messages on the .command queue using tool like GEMS.
2). Log into the BWPM GUI and in the technical view navigate to Process A and select the Administration tab (nest to reports tab in top). Select the "Log Settings" tab and check the Exclude Process check box and apply.
3). In GEMS you will see three (receive, send, acknowledge) temporary messages created when you hit the Apply button. Check the message content. It should be something like the following in the captured message.

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

4). Similarly, if you uncheck the Exclude Process check box and Apply, check the message content. It should be something like the following in the captured message.

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

5). In the attached POC code we used a Timer activity to send the above message on the .command queue which enables/disables monitoring.