Introduction to a Provider B2B Connector Service How to Identify the Message Exchange Pattern

17-8 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ Section 17.3.4, How to Store a WSDL in the Oracle Metadata Repository ■ Section 17.3.5, How to Develop a B2B Connector Service ■ Section 17.3.6, How to Customize the AIA B2B Interface ■ Section 17.3.7, How to Annotate B2B Connector Services ■ Section 17.3.8, How to Support Trading Partner-Specific Variants ■ Section 17.3.9, How to Enable Error Handling The next step, as shown in Figure 17–6 , is to develop the provider B2BCS to support the outbound B2B integration flow. Figure 17–6 Step 2: Developing a New Provider B2B Connector Service The provider B2BCS is very similar to a provider Application Business Connector Service ABCS, with the only difference being that it integrates with trading partners via Oracle B2B instead of integrating with an application. Hence, we recommend that you familiarize yourself with the design and development of ABCS requester and provider as well.

17.3.1 Introduction to a Provider B2B Connector Service

The key functionality provided by a provider B2BCS is to enable outbound B2B document integration by performing the following tasks: ■ Transforming AIA EBMs into B2B documents. ■ Invoking Oracle B2B to send these B2B documents to trading partners. Figure 17–7 illustrates the processing that takes place in a simple fire-and-forget message exchange pattern-based provider B2BCS. Developing and Implementing Outbound B2B Integration Flows 17-9 Figure 17–7 Processing Flow for a Fire-and-Forget Provider B2BCS Step-by-step instructions for developing B2BCSs are provided in the following sections.

17.3.2 How to Identify the Message Exchange Pattern

Most B2B document flows can be modeled as asynchronous one-way calls. For example, consider a use case in which a purchase order created in a Procurement application needs to be sent to a supplier using an outbound B2B document flow. Upon receipt of this Purchase Order document, the supplier processes it and sends back a Purchase Order Acknowledgement B2B document. In this use case, even if a response is expected from the supplier in the form of the Purchase Order Acknowledgement document, the Procurement application can continue with its processing, which involves the purchase order being communicated to and processed by the vendor. The Procurement application also generally can correlate the Purchase Order Acknowledgement document to the original purchase order because the Vendor is expected to provide the same purchase order identification used in the request in the 17-10 Developers Guide for Oracle Application Integration Architecture Foundation Pack Acknowledgement message. In this way, the request and response can be modeled as two asynchronous one-way flows. However, a similar analysis must be performed for each B2B document flow being designed. For more information about identifying message exchange patterns, see Section 11.3, Identifying the MEP.

17.3.3 How to Develop a B2BCS Service Contract