Configuring Delivery Retry Options

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. 5-44 Oracle Fusion Middleware Users Guide for Oracle B2B See Chapter 12, Scheduling Trading Partner Downtime for information about scheduling and managing trading partner downtime.

5.9 Broadcasting Messages to Multiple Trading Partners

Oracle B2B provides the capability to send the same message to multiple trading partners. This gives you the flexibility to create your own groups of trading partners specific to certain business needs. The back-end application interface can then send a message to the group and Oracle B2B sends the message to all the members of the group. The salient points of the feature are: 1. Prevents BPEL from sending multiple files, reducing the traffic on BPEL-B2B and also in B2B. 2. Introduces the concept of trading partner groups in B2B and uses it for broadcasting. This will prevent BPEL users from knowing about trading partner details as well as the group because it is B2B-specific metadata. 3. Provides an event driven approach to handle the multiple messages to various trading partners. To use broadcasting, specify the group name as part of the actionName attribute. The actionName attribute would look like this: actionName = Grouping:name_of_the_group Broadcasting requires an additional identifier to be added to the Trading Partner configuration indicating the group to which the partner is assigned. This is achieved by creating a new custom Identifier and associating the same for the required trading partners. See Section 10.3, Creating Custom Trading Partner Parameter Types for more information.