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


Chapter 2 Process Flows and Functionalities : Operation Types and Process Flows

Operation Types and Process Flows
When you use TIBCO BusinessConnect to exchange SOAP messages with a partner, you can use different operation types for different kinds of transactions. Two operation types are in SOAP. Any operation defined must be one of these two operation types:
Notify  Use this operation type when the initiator only requires an acknowledgment from the responder to verify the receipt of the SOAP message.
Synchronous request-response  Use this operation type when the initiator and the responder do a more complex exchange of business documents by exchanging SOAP messages. When the initiator sends a request SOAP message to the responder, a response SOAP message is expected to be returned back from the responder in synchronous HTTP reply.
Notify Operations
The following process flow occurs in a Notify type operation. In this process flow, both the initiator and responder are assumed to be implemented by TIBCO BusinessConnect SOAP Protocol:
1.
2.
3.
4.
5.
Time Constrains and Resend
For a Notify type operation, you can specify the time constrains on the initiator side:
For the initiator: configure in HTTP/HTTPS transport configuration for the specific trading partner.
The flow of information and the associated predefined timing restrictions are as shown in Figure 1.
Figure 1 Notification
As the Initiator
From the initiator, an operation is processed with the following timing restrictions:
1.
2.
3.
Synchronous Request-Response Operations
The following process flow occurs in a synchronous request-response operation. In this process flow, both the initiator and responder are assumed to be implemented by TIBCO BusinessConnect SOAP Protocol:
1.
2.
3.
If the validation or unpackaging of the inbound SOAP message fails, the responder BusinessConnect server sends a SOAP fault on the same HTTP transport channel to the initiator BusinessConnect server, which forwards the fault content to the private process.
4.
The responder private process can also return an error message as a SOAP fault to responder BusinessConnect server if the private process cannot process the request SOAP message. To send a SOAP fault as the response on the responder side, ensure that the value in the statusCode field of the ae/SOAP/ResponderResponse AE message is not in the range of 200-299.
The ae/SOAP/ResponderResponse AE message class in the SOAP fault private message includes a field called soapFault. TIBCO BusinessConnect SOAP Protocol uses the values in the soapFault field to generate the public SOAPFault response message.
5.
6.
7.
Time Constrains and Resend
For a synchronous request-response operation, you can specify the following time constrains:
Figure 2 Synchronous Request-Response
As the Initiator
From the initiator, an operation is processed with the following timing restrictions:
1.
2.
3.
As the Responder
From the responder, an operation is processed with the following timing restrictions:
1.
2.
3.
4.
5.

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