Description:
BWPM daily issue: data provider stay enabled
Symptoms:
TIBCO BusinessWorks ProcessMonitor(BWPM) 3.0 version has added new features to configure nodes. You can also configure more than one node to allow distributed data processing. Each node can consist of multiple data providers. Prior to BWPM 3.0, there is no node configuration functionality. Node configuration shows the data provider as enabled but you have to start the data provider manually after restarting the Tomcat server.

Node - A BWPM Node is a separate BWPM server running on a separate Application server connected to an existing BWPM instance. Multiple nodes can be configured to a cluster of BWPM servers that allows distributed data processing for load balance and inherent fault tolerance. For more details, refer to the BWPM 3.0 documents (TIBCO Business Works (TM) Process Monitor Server Administration Guide.pdf -> Configuration -> Data Providers).

To start data providers automatically, you can implement the following workaround in your environment to start data providers upon restarting Tomcat and verify the behavior.
------------
If only one data provider exists on the node then before starting Tomcat, you can change the content of controller_runstate.txt to "Running" instead of "Stopped", which is the default. The data provider will thenrestart. You can find this file in /opt/apache/tomcat_njams_ga_ora_2/webapps/bwpm/WEB-INF/data/controller_runstate.txt.

Stopped - means the data provider will not be started automatically.
Running - means the data provider will be started automatically.
 

In case you have more than one data provider configured, the content of the controller run state file looks a little different. For example, if there are two data providers, the controller runstate file contains:

<STATE>__<DP_ID_1>__<DP_ID_2> 
State is followed by the identifiers of the data providers separated by double underscore characters. 
You will find the identifiers of the data provider in the nJAMS database table "NJAMS_T_CONFIGURATION". The following SQL statement shows the identifiers of all dataproviders:
select name from njams_t_configuration where name like 'dataprovider.%.name';
The identifier is given between "dataprovider." and ".name". For example, the output of the select statement may be:
dataprovider.1384194805284.name
dataprovider.2.name
dataprovider.1387191958019.name
Your controller runstate file should now contain:
Running__2__1384194805284__1387191958019


If the Tomcat server stops, the content of the controller_runstate.txt file will be overwritten to “Stopped”. Therefore, the data provider will not start. This is a bug in the current version.
Cause:
BWPM daily issue: data provider stay enabled

 It will be fixed in release 3.0.1. 

Data Providers is not started automatically in TIBCO BusinessWorks ProcessMonitor(BWPM) 3.0.0.x when restating the Tomcat server.

3.0.1