How to Implement the EBF as a BPEL Service Overview of B2B Integration Using AIA

Designing and Constructing Enterprise Business Flows 15-5

15.2.3 How to Identify the Message Structure

To identify the message structure: 1. A CBP is implemented by orchestrating calls to external services. The event triggering the CBP indicates the business object with which the CBP will be dealing. 2. Depending on the integration style, the message structure is decided as described below: a. If the business object is available in the existing Enterprise Business Message EBM, use it. b. If the business object is not available in the existing EBM but can be assembled from the existing Enterprise Business Object EBO Library, construct it. c. If the business object is not available in the EBO Library, identify a payload suitable for capturing all relevant information and processing in the CBP.

15.3 How to Create the Contract for an EBF

To create the contract for an EBF: 1. Identify the EBM. 2. Construct the WSDL for the EBF. 3. Annotate the service interface. 4. Ensure WS-1 basic profile conformance.

15.3.1 Constructing the WSDL for the EBF

Because the EBF development starts with constructing a WSDL, the end result of the technical design process is an EBF WSDL.

15.4 How to Implement the EBF as a BPEL Service

To implement the EBF: 1. Create a new WSDL. Create a WSDL for the EBF following the EBF naming standards and the WSDL templates provided. 2. Implement the EBF as a synchronous or asynchronous BPEL process. For more information about the details of creating BPEL projects in Oracle JDeveloper, see the Oracle BPEL Process Manager Developers Guide. Follow Section 12.5, Implementing the Asynchronous Request Delayed Response MEP for details on how to use BPEL to implement asynchronous request-delayed response pattern. The difference is that the EBF deals with EBMs. 3. Enable error handling and logging. EBSs should handle errors to enable clients or administrators to resubmit or retrigger processes. This is done through a central error handler. For more information, see Chapter 24, Configuring Oracle AIA Processes for Error Handling and Trace Logging 15-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack 4. Enable extensibility points in the EBF. 16 Introduction to B2B Integration Using AIA 16-1 16 Introduction to B2B Integration Using AIA Business-to-business B2B integration requires the ability to exchange business information with trading partners using a choice of B2B document protocols. This chapter includes the following sections: ■ Section 16.1, Overview of B2B Integration Using AIA ■ Section 16.2, Understanding B2B Document Flows ■ Section 16.3, Understanding the Oracle B2B Component of Oracle Fusion Middleware ■ Section 16.4, Understanding the Foundation Pack Infrastructure for B2B

16.1 Overview of B2B Integration Using AIA

The Oracle Application Integration Architecture AIA B2B solution consists of the following key features: ■ A flexible integration architecture that can be used to rapidly build support for new B2B document protocols. ■ Infrastructure components that can be used to build end-to-end B2B flows using AIA and Oracle Fusion Middleware. ■ Prebuilt support for popular B2B document protocols. ■ Support for customization of shipped B2B integration artifacts. Figure 16–1 illustrates how the canonical-based integration architecture of AIA can be applied to meet the B2B integration needs of large enterprises. 16-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 16–1 Schematic Overview of the B2B Architecture of AIA Following are some of the key benefits of using AIA for B2B integrations: ■ AIA decouples participating applications from the B2B integration layer. Participating applications no longer need to track the varying B2B integration needs of trading partners. In addition, customers can add support for new B2B protocols and trading partner requirements without any impact to participating application code. ■ B2B document flows are often a subset of tasks that make up complex business processes, such as Order Capture. By building B2B functionality as a layer on top of Foundation Pack, the functionality is made available for reuse by multiple applications and business processes. ■ Existing AIA Enterprise Business Objects EBOs such as Customer, Supplier, Item, Purchase Order, Shipment, Invoice, and Catalog Address map to most of the commonly used B2B documents. Usage of these readily available EBOs, along with prebuilt B2B connector services B2BCSs for these EBOs, result in significant time and cost savings for B2B integrations.

16.2 Understanding B2B Document Flows