How to Annotate B2B Connector Services

17-18 Developers Guide for Oracle Application Integration Architecture Foundation Pack 8. The B2BCS is responsible for supplying the value of the GatewayID element to ensure that the desired value of the GatewayID is supplied before the AIAB2B Interface is invoked. 9. Save changes. Compile, test, and redeploy the AIA B2B Interface.

17.3.7 How to Annotate B2B Connector Services

To make key metadata about the B2BCS available to the Project Lifecycle Workbench and Oracle Enterprise Repository, the composite.xml file of the B2BCS Implementation SOA composite must be annotated in a specific manner. For more information about the Project Lifecycle Workbench, see Chapter 2, Working with Project Lifecycle Workbench. For more information about annotating B2B services, see Chapter 9, Annotating Composites. To annotate B2B Connector Services: 1. Table 17–5 lists the annotation elements that must be added to the service element composite.xml, as described subsequently. Table 17–4 B2BM Variable Information That Can Be Used to Provide Input to B2B Software Input Element Description Usage While Integrating with Oracle B2B in.B2BMB2BMHeaderSen derTradingPartner TradingPartnerID Sending trading partner in outbound flow. Map to: JMSProperty.FROM_ PARTY in.B2BMB2BMHeaderRece iverTradingPartner TradingPartnerID Receiving trading partner in outbound flow. Map to: JMSProperty.TO_ PARTY in.B2BMB2BMHeaderB2B DocumentTypeTypeCode B2B Document Type used in the outbound flow. For example, 850. Map to: JMSProperty. DOCTYPE_NAME in.B2BMB2BMHeaderB2B DocumentTypeVersion B2B Document Type version used in the outbound flow. For example, 4010. Map to: JMSProperty. DOCTYPE_REVISION in.B2BMB2BMHeaderB2B DocumentTypeTypeCode listAgencyID B2B standard used in the outbound flow. For example, X12. Not used. in.B2BMB2BMHeaderB2B MID Unique B2B document identifier. Unique across all trading partners. Map to: JMSProperty.MSG_ID in.B2BMB2BMHeaderPayl oad Actual payload being sent to trading partners. JMS text payload Developing and Implementing Outbound B2B Integration Flows 17-19 The following XML snippet, as shown in Figure 17–15 , is an example of an annotated B2BCS called X12ProcessSalesOrderReqB2BCSImpl composite.xml. Figure 17–15 Example Snippet of an Annotated B2BCS Called X12ProcessSalesOrderReqB2BCSImpl composite.xml 2. Table 17–6 lists AIA B2B interface utility service annotation elements in composite.xml. Table 17–5 Service Annotation Elements in composite.xml Annotation Element Description Example AIAServiceInterfaceDetailsServiceNa me Name of EBS implemented by this provider B2BCS Impl SalesOrderEBS AIAServiceInterfaceDetailsNamespa ce Namespace of EBS implemented by this provider B2BCS Impl http:xmlns.oracle.comEnterpriseServ icesCore SalesOrderV2 AIAServiceInterfaceDetailsArtifactTy pe EnterpriseBusinessService EnterpriseBusinessService AIAServiceInterfaceDetailsService Operation VerbEBOName UpdateSalesOrder AIAServiceImplementationDetailsAr tifactType ProviderB2BCSImplementation ProviderB2BCSImplementation AIAServiceImplementationDetailsSe rviceOperationName VerbEBOName UpdateSalesOrder AIAServiceImplementationDetailsB2 BDocument Target B2B Document Type of this B2BCS 855 AIAServiceImplementationDetailsB2 BDocumentVersion Target B2B Document Version of this B2BCS 4010 AIAServiceImplementationDetailsB2 BStandard Target B2B Standard of this B2BCS X12 AIAServiceImplementationDetailsB2 BStandardVersion Target B2B Standard Version of this B2BCS 4010 17-20 Developers Guide for Oracle Application Integration Architecture Foundation Pack The reference to the AIA B2B Interface utility service should be annotated in the composite.xml, as shown in Figure 17–16 . Figure 17–16 AIA B2B Interface Utility Service Annotation Elements in composite.xml snippet 3. The AIA_ HOMEInfrastructureB2BsrcB2BConnectorsEDIX12B2BCSAppX12Update SalesOrder ProvB2BCSImplcomposite.xml file has sample provider B2BCS Impl annotations for your reference.

17.3.8 How to Support Trading Partner-Specific Variants