Introduction to Requester B2B Connector Services How to Identify the Message Exchange Pattern How to Develop a B2BCS Service Contract

18-10 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 18–11 Step 3: Developing a New Requester B2B Connector Service The requester B2BCS is very similar to a requester 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 ABCSs requester and provider. For more information about developing ABCSs, see Chapter 12, Constructing the ABCS.

18.4.1 Introduction to Requester B2B Connector Services

The key function provided by a requester B2BCS is to enable inbound B2B document integration by performing the following tasks: ■ Receive B2B documents sent by trading partners from Oracle B2B. ■ Transform B2B documents into AIA EBMs. ■ Use EBMs as request payloads to invoke AIA Enterprise Business Services EBSs. Figure 18–12 illustrates the processing that takes place in a simple fire-and-forget message exchange pattern-based provider B2BCS. Developing and Implementing Inbound B2B Integration Flows 18-11 Figure 18–12 Process Flow of a Simple Fire-and-Forget Message Exchange Pattern-Based Provider B2BCS Step-by-step instructions for developing B2BCSs are provided in the following sections.

18.4.2 How to Identify the Message Exchange Pattern

Similar to outbound B2B flows, most inbound B2B flows can be modeled using the fire-and-forget message exchange pattern. Responses to be sent to trading partners can be modeled using separate outbound fire-and-forget flows. Also, depending on the protocol involved, Oracle B2B can be configured to automatically send a confirmation or acknowledgement message to trading partners. For more information, see Section 17.3.2, How to Identify the Message Exchange Pattern. For more information about identifying message exchange patterns, see Section 11.3, Identifying the MEP.

18.4.3 How to Develop a B2BCS Service Contract

First, define the service contract WSDL of the requester B2BCS. The service contract of the provider B2BCS specifies how it is invoked by an AIA flow. The service contract 18-12 Developers Guide for Oracle Application Integration Architecture Foundation Pack specifies the B2B operation being implemented and the B2B document type that it is capable of processing as the input request message. For more information about creating WSDLs for ABCSs, see Section 11.2, Defining the ABCS Contract. Following are the naming conventions recommended for use in the B2BCS WSDL definitions: ■ WSDL File Name: ■ Naming guideline: B2BStandardVerbEBOReqB2BCSImpl.wsdl ■ Example: X12ProcessSalesOrderReqB2BCSImpl.wsdl ■ Service Namespace: ■ http:xmlns.oracle.comB2BCSImpl{Core|IndustryIndustryName }B2BStandardVerbEBOReqB2BCSImplABCSVersion ■ Example: http:xmlns.oracle.comB2BCSImplCoreX12ProcessSalesOrderProvB2BC SImplV1 Please note that the ABCS Service version is independent of the B2B documentstandard version. For more information about recommendations on versioning AIA services, see Section 13.8, Versioning ABCS. ■ Service Name: ■ Naming guideline: B2BStandardVerbEBOReqB2BCSImpl ■ Example: X12ProcessSalesOrderProvB2BCSImpl ■ Port Type Name: ■ Naming guideline: B2BStandardVerbEBO ReqB2BCSImplService ■ Example: X12ProcessSalesOrderProvB2BCSImplService ■ Operation Name: ■ VerbEBO ■ ProcessSalesOrder ■ Request Message Name: ■ VerbEBOReqMsg ■ ProcessSalesOrderReqMsg

18.4.4 How to Store a WSDL in Oracle Metadata Services Repository