Correlating Messages Using JMS Queues

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. Configuring Trading Partners 5-43 Figure 5–24 The Auto Create Agreement Feature The image shows the Oracle B2B screen. The top left pane is labeled Partner and shows the list of partners Acme and GChips. The bottom left pane is labeled Agreement and shows the list of agreements. The top right of the screen shows a Confirmation dialog box with messages for the page. This feature creates one agreement for each document definition associated with the selected remote trading partner. You can further customize the agreement on the Agreement tab. See Chapter 6, Creating and Deploying Trading Partner Agreements, for more information about the Agreement tab.

5.7 Using Identifiers for Trading Partner Lookup

Identifiers available in design-time data are used to look up trading partners. Identifiers do not need to be part of a deployed, active agreement. The appropriate document and exchange identifiers are used for lookup; for example: ■ For the AS2-1.1 exchange protocol, the AS2 identifier is used. ■ For the EDI X12 document protocol, the Sender Group ID and Sender Interchange ID are used.

5.8 Scheduling Trading Partner Downtime

On occasion a trading partner will need to go offline for planned maintenance. You can configure downtime so that partners are adequately notified and messages are queued for delivery when downtime ends.