Resolution:
Description:
=======
When using “Notify” and “Wait” activities, we can send a notify message to the wait activity successfully in just one BW engine. The problem is transferring messages between different engines or different machines. In this situation, it will fail to do like what was done in one engine. Use a database for help if wanting message transferring between two engines.

Example:

Archive A - Process A (Server 1) churns through some processes and sends a message and "waits" for the other process to finish.

Archive B - Process B (Server 2) receives a message, does some processing and notifies Process A that it is completed.


Resolution:
==========
1). Create a "Notify Configuration" activity in the project. In configuring the "Notify Configuration" activity, do not check the "Local Only" checkbox.

2). Create a JDBC Connection Resource in the project. Configure it with a Database.

3). Build two EAR files. One should contain a process with "notify" activity, the other with a process with "wait" Activity. The key should be the same.

4). Deploy and choose the Configuration/Process_Archive.par for Advanced tab. Go to the "TIBCO BusinessWorks Checkpoint Data Repository" tab and change the "Checkpoint Data Repository" to the JDBC Connection resource defined in your Designer. Note thT the table name should be the same.

5). Run your applications. Five tables will be created in your database and the notify message should be sent to another engine.