Copyright © Cloud Software Group, Inc. All Rights Reserved

Process Flows and Transaction Types

The following is an example of how a TIBCO BusinessConnect B2BPlugin for CMI process flow might proceed:

1.	A private process inside the Initiator company sends a TIBCO Rendezvous or JMS topic message to TIBCO BusinessConnect. The message contains all fields specified in Initiator Outbound Request. It includes a document specifying the business operation.

2.	TIBCO BusinessConnect B2BPlugin for CMI performs the following functions:

−	Looks up trading partner information to determine the address to which the document must be sent and the security required.

−	Establishes the necessary security for message transmission.

−	Enters transaction information for the audit and non-repudiation databases.

3.	TIBCO BusinessConnect sends the document to the Responder. The Responder receives the message, and sends out the document as a TIBCO Rendezvous or JMS topic message to the private process. See Responder Inbound Request.

What happens next depends on whether the transaction is defined as a notification transaction or a request-response transaction.

Notification Transaction

For notify activities, TIBCO BusinessConnect on the Initiator side considers the operation complete as soon as request is sent to Responder TIBCO BusinessConnect.

The Initiator TIBCO BusinessConnect creates a notify message that it sends back to its private process to indicate that a transaction has been successfully sent to the trading partner..

The Responder TIBCO BusinessConnect creates a notify message that it sends request from Initiator to its private process.

Request-Response Transaction

For request-response activity, the Responder site processes the response as follows:

1.	The private process must send a message with appropriate response information back to TIBCO BusinessConnect. See Responder Outbound Synchronous Response.

If the Responder private process is unable to handle the document, it must publish an error response back to the server so that the server can inform the Initiator that the request has failed. See Responder Outbound Synchronous Response.

2.	When the message arrives, the Responder TIBCO BusinessConnect adds appropriate information and converts it to HTTP format, using the specified trading partner, enveloping, and security information. It sends the response to the Initiator TIBCO BusinessConnect.

3.	The message arrives at the Initiator TIBCO BusinessConnect. The Initiator verifies the incoming information and sends to the private process.

See Initiator Inbound Response

Timeout and Validation Alerts

If at any point an error occurs, TIBCO BusinessConnect B2BPlugin for CMI will post the following alert messages to the private process:

•	Timeout Alert

Copyright © Cloud Software Group, Inc. All Rights Reserved