I am creating 1 .ear file for my project but 2 separate process archives for WAIT process and NOTIFY process; then why do theWAIT and NOTIFY activities fail to communicate?
Article ID: KB0087947
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
As processes in different process archives are running in different BW engines (JVMs), you have to use database for storing notification data and make sure that all the engines are using the same table name otherwise it will not work.
Steps to enable database storage for notification data:
(1) Create a JDBC connection in your project and confirm it is included into the Shared Archive.
(2) Once you load this EAR file in the Administrator, please select each .par in configuration, click the Advanced Tab and you will see "Tibco Business Works Checkpoint Data Repository", instead of the Local Repository, select the JDBC connection from the drop down menu. Here it will ask you for a table name, please make sure that this name is the same across all the .par (multiple engines).
(3) Deploy the EAR with “Start successfully deployed services” unchecked.
(4) For the first time, start the process instances ONE BY ONE or they may all try to create the table and result in a JDBC error.
As processes in different process archives are running in different BW engines (JVMs), you have to use database for storing notification data and make sure that all the engines are using the same table name otherwise it will not work.
Steps to enable database storage for notification data:
(1) Create a JDBC connection in your project and confirm it is included into the Shared Archive.
(2) Once you load this EAR file in the Administrator, please select each .par in configuration, click the Advanced Tab and you will see "Tibco Business Works Checkpoint Data Repository", instead of the Local Repository, select the JDBC connection from the drop down menu. Here it will ask you for a table name, please make sure that this name is the same across all the .par (multiple engines).
(3) Deploy the EAR with “Start successfully deployed services” unchecked.
(4) For the first time, start the process instances ONE BY ONE or they may all try to create the table and result in a JDBC error.
Issue/Introduction
I am creating 1 .ear file for my project but 2 separate process archives for WAIT process and NOTIFY process; then why do theWAIT and NOTIFY activities fail to communicate?
Feedback
Yes
No
Powered by
