Using Transport Sync Callback

Configuring Trading Partners 5-41 If the message ID MSG_ID is provided from a back end application, then MSG_ID is set to JMS Correlation ID in the B2B output, otherwise the JMS Message ID is set to JMS Correlation ID in the B2B output.

5.5.5 Configuring Delivery Retry Options

In the critical situations of B2B world, it is important to have the message delivered to the destination without fail and receive the exchange level acknowledgement or functional acknowledgement on time. Oracle B2B provides the ability to retry message delivery at the Channel and Document levels.

5.5.5.1 Delivery Retry at the Channel Level

Channel retry is associated with the delivery channel, and is used to ensure successful delivery. You can configure the Retry Count and Retry Interval parameters for the number of times to retry and the interval between each retry. Oracle B2B retries the message for a successful delivery until all available retries are exhausted before errors are written. See Table 5–4 for information about the channel retry parameters. Channel Details screen with Channel Attributes tab selected showing Retry Interval, Retry Count, Description, and Transport Callout parameters. For any exchange protocol with Acknowledgement case for example MDN in AS2 and Acknowledgement in ebMS, the channel retry is used to retry the business message until the message gets to either the COMPLETE or ERROR state after completing the configured retry count. For generic exchange, channel level retry plays a role only in case of transport error. The number of remaining retries in the retry count and retry interval for a specific message can be seen as part of the business message report.

5.5.5.2 Delivery Retry at the Document Level

Document retry is associated with an Agreement, and is used to ensure the successful integration of the message with the recipient trading partner. This feature consists of configuring a timeout value within which the Functional Acknowledgment has to be received for outbound business messages. To enable this feature, set the Document Retry Count and Document Retry Interval parameters as shown in the following graphic. 5-42 Oracle Fusion Middleware Users Guide for Oracle B2B Agreement configuration screen showing the Agreement Parameters in the bottom section of the screen: Validate checked, Translate checked, Functional Ack checked, FA Handled by B2B set to None, Document Retry Interval set to 1, Document Retry Count set to 3. After successful transmission of a business message, B2B must wait for Functional Acknowledgment for specified time. If FA is not received after retries are exhausted, B2B will raise an exception message to B2B Inbound Queue. The number of remaining retry and interval for a specific message can be seen as part of the business message report. Generic Exchange Scenario For generic exchange, document retry attempts are triggered only upon successful transport Acknowledgment, and in the case of standard based exchange such as AS1AS2, only upon receipt of Positive Acknowledgment. That is, for a generic exchange, document retry attempts are triggered only post-transmit, whereas for a standard Acknowledgment case, attempts are triggered only upon receipt of positive Acknowledgment. For a negative Acknowledgment, document retry attempts are not triggered. Channel-level Retry Interoperability Channel-level retry attempts are not triggered by document level retries attempts. In cases where no channel retry parameters are configured, document-level retry attempts are triggered after Document Retry Interval expires.

5.6 Using the Auto Create Agreement Feature

In the Partner area, shown in Figure 5–24 , you can use the Auto Create Agreement icon to create an agreement for a remote trading partner.