General steps to develop inter-process communication

To know what is Inter-process communication or use of Wait & Notify activities Click here

1. Define the data that must be passed between the processes by creating a Notify Configuration shared configuration resource.


2. Determine the key that correlates processes with Notify activities with the corresponding processes with Receive Notification process starters or Wait activities.


3. Create process definitions that use the Receive Notification, Wait, and Notify activities. These activities are located in the General Activities palette.


4. If your process engines are on different machines, a database must be used to store process instance information. Wait/Notify information is stored in a database so that process engines on different machines can share information.

Read more...

How process instances can communicate? What is the use of Wait & Notify activities? What is inter-process communication?

TIBCO BusinessWorks allows two executing process instances to communicate. You may need process instances to communicate if you wish to synchronize process execution or if your processes must execute in a specific order.

TIBCO BusinessWorks provides the Wait and Notify activities and the Receive Notification process starter to handle inter-process communication. A process containing a Wait activity waits for another process to execute a corresponding Notify activity. Alternatively, the Receive Notification process starter creates a new process instance when another process executes the corresponding Notify activity.

The data sent between the activities is defined by a Notify Configuration shared configuration resource. The Notify activity only sends information to the Receive Notification process starter or Wait activity that specifies the same Notify Configuration resource.

If you wish only to signal the waiting process to continue but not exchange data, the Notify Configuration schema used by the Notify/Receive Notification/Wait activities can be empty.

To know the steps to develop Inter-process communication click here

Read more...

Steps to Configure Service activity as Web Server in Web Service Implementation

Before creating a Service resource, you will need to create the following resources:

• A WSDL file that contains an abstract interface description. The interface can include one or more operations.
• Process definitions will provide the implementation for each operation in the service’s interface. You can specify the same process definition for more than one operation.
• Either an HTTP Connection or JMS Connection shared configuration resource that specifies the transport used by clients of the service.

To configure a Service resource, follow these general steps:

1. Provide an abstract WSDL(Input, OutPut & type of operation) file that describes the interface to the service.
2. For each operation in the interface, specify a process definition that implements the operation.
3. Specify one or more endpoint bindings to expose the service to potential clients.
4. For each endpoint binding, specify a transport configuration (either HTTP Connection or JMS Connection).
5. Specify any transport-specific information, such as endpoint URL for HTTP transports or JMS Destination Name for JMS transports.
6. Specify any SOAP details, such as SOAP Version or encoding for each operation.
7. Specify attachments, headers, or context information for input and output messages, if necessary.

Read more...

Difference between JMS Queue Receiver & Get JMS Queue Message activities

JMS Queue Receiver:

1. It is a process starter activity. It continues to poll destination queue to start the execution of process definition.
2. After BusinessEngine started, a new process instance will be created for every single message it received.
3. It has only static selector option to configure. That means we can filter all the messages with one selector value only. If you wish to filter messages with different selector values you would need to create more process definitions with JMSQueue reciver.

Get JMS Queue Message:

1. It is NOT a process Starter activity. We could place this activity between starter and end activity of process definition. This activity executes only when its triggered.
2. It executes all the queue messages in a single process instance and retrives one message at a time even more messages on the queue.
3. It has both dynamic and static selectors. With a dynamic selector, one would be able to change the selector value for every message in the queue.

Read more...