Define variable EBM_HEADER of type corecom:EBMHeader. Define variable B2BM_HEADER of type corecom:B2BMHeader. Define variable B2BDoc_Var using the external B2BDocument definition. Define a partner link to the EBS.

18-14 Developers Guide for Oracle Application Integration Architecture Foundation Pack To develop a B2B connector service: 1. Create a SOA Composite application containing a SOA project with a BPEL component. 2. Choose the WSDL created in the previous step as the interface for the SOA composite. 3. The values to be used for creating the SOA application and project are listed in Table 18–1 . 4. Define variable B2BM_Var. This is the input variable to the BPEL process and is used in the receive activity. Define the variable based on the corecom:B2BM global element defined in the Meta.xsd.

5. Define variable EBM_HEADER of type corecom:EBMHeader.

This variable is used to store the AIA process context information and is used by the fault-handling mechanism. Define the variable based on the corecom:B2BM global element defined in the Meta.xsd.

6. Define variable B2BM_HEADER of type corecom:B2BMHeader.

This variable is used to store the B2B-specific AIA process context information and is used by the fault-handling mechanism. Define the variable based on the corecom:B2BMHeader global element defined in the Meta.xsd.

7. Define variable B2BDoc_Var using the external B2BDocument definition.

This is used as the source of the transformation from EBM. This variable is then assigned to the B2BDocB2BM_VarPayload.

8. Define a partner link to the EBS.

This is the AIA EBS that is invoked by the requester B2BCS. Table 18–1 Values Used to Create the SOA Application and Project Activity Value Application Name B2BStandard Verb EBO ReqB2BCSApp Project Name B2BStandard Verb EBO ReqB2BCSImpl Project Namespace http:xmlns.oracle.comB2BCSImplCore Standard Verb Object ReqB2BCSImplV1 Same as B2BCS WSDL namespace Composite Name B2BStandard Verb EBO ReqB2BCSImpl Composite Template Composite with BPEL BPEL Process Name B2BStandard Verb EBO ReqB2BCSImpl Namespace http:xmlns.oracle.comB2BCSImplCore Standard Verb Object ReqB2BCSImplV1 Same as B2BCS WSDL namespace Template Base on WSDL WSDL URL URL of B2BCS service WSDL referred from MDS Developing and Implementing Inbound B2B Integration Flows 18-15 The abstract EBS WSDL can be referenced from: oramds:appsAIAMetaDataAIAComponentsEnterpriseBusinessServiceLibrar yCoreEBOVxEBOName.wsdl. 9. Transform the EBM to the B2B Document. Use a transform activity to transform the EBM to the B2B Document format. Invoke an XSLT developed per the mapping created in the previous step. 10. Assign B2B-specific EBMHeader variables as shown here: ■ Element: corecom:EBMHeadercorecom:B2BProfilecorecom:SenderTradingPartnerco recom:TradingPartnerID Source B2BM XPATH: corecom:B2BMcorecom:B2BMHeadercorecom:SenderTradingPartnercorec om:TradingPartnerID ■ Element: corecom:EBMHeadercorecom:B2BProfilecorecom:ReceiverTradingPartnerc orecom:TradingPartnerID Source B2BM XPATH: corecom:B2BMcorecom:B2BMHeadercorecom:ReceiverTradingPartnercore com:TradingPartnerID This way, the sender and receiver trading-partner information identified by Oracle B2B is passed on to the EBM. 11. Invoke the EBS. Invoke the AIA EBS to process the EBM. 12. Compile the BPEL process and ensure that no errors occurred. You can use Oracle JDeveloper to deploy the BPEL process to a development server that has AIA Foundation Pack installed.

18.4.6 How to Annotate B2B Connector Services