Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Configuring Protocol Features : Process Flows and Transaction Types

Process Flows and Transaction Types
The following is an example of how a TIBCO BusinessConnect EDI Protocol powered by Instream process flow might proceed:
1.
2.
3.
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 an acknowledgment is received from the Responder TIBCO BusinessConnect.
The Initiator TIBCO BusinessConnect creates a notify message that it sends back to its private process to indicate that a previously sent transaction has been successfully reconciled upon receiving an acknowledgment from the trading partner. See Initiator Acknowledgment From Partner.
The Responder TIBCO BusinessConnect creates a notify message that it sends back to its private process to indicate the success or failure of the posting of an acknowledgment to the Initiator. See Responder Acknowledgment to Partner.
Request-Response Transaction
For request-response activity, the Responder site processes the response as follows:
1.
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 on page 113.
2.
3.
See Initiator Inbound Response on page 98.
Timeout and Validation Alerts
If at any point an error occurs, TIBCO BusinessConnect EDI Protocol powered by Instream will post one of the following alert messages to the private process:

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved