Edit the AIAB2BInterfacecomposite.xml file using the Composite Editor, as Modify the AIAB2BInterfaceProcessB2BDocument.mplan file to add custom The input B2BM variable is received from the provider B2BCSs.

Developing and Implementing Outbound B2B Integration Flows 17-15 Figure 17–9 AIA B2B Interface Support for Custom Internal Delivery Channels and Legacy B2B Connectivity For example, you might have outbound Order documents being routed to a Fusion Middleware Oracle B2B component, and outbound Invoice documents being routed to an older B2B instance. To support this use case, define two routing rules: one for JMS invocation of Oracle B2B and another for Oracle Advanced Queuing invocation of the older B2B instance. Note that a given B2B document instance is likely to be routed to B2B using one of the multiple routing rules in the ProcessB2BDocument.mplan. In the highly unlikely event that a B2B document generated by the AIA layer needs to be routed to multiple B2B software instances, the routing rules in the ProcessB2BDocument.mplan mediator should be configured for sequential invocation. To make customizations to the AIA B2B Interface: 1. Open the SOA application, AIA_ HOMEInfrastructureB2BsrcAIAB2BInterfaceApp, using Oracle JDeveloper.

2. Edit the AIAB2BInterfacecomposite.xml file using the Composite Editor, as

shown in Figure 17–10 . Figure 17–10 AIAB2BInterfacecomposite.xml in the Composite Editor 17-16 Developers Guide for Oracle Application Integration Architecture Foundation Pack 3. Add a new adapter or web-service call required to interface to the third-party B2B software, as shown in Figure 17–11 . Figure 17–11 Addition of New Web Service Call to Interface with Third-Party B2B Software

4. Modify the AIAB2BInterfaceProcessB2BDocument.mplan file to add custom

routing rules to route outbound B2B documents to third-party B2B software, as shown in Figure 17–12 and Figure 17–13 . Figure 17–12 AIAB2BInterfaceProcessB2BDocument.mplan in the Composite Editor Developing and Implementing Outbound B2B Integration Flows 17-17 Figure 17–13 Addition of Custom Routing Rules to AIAB2BInterfaceProcessB2BDocument.mplan 5. Use a condition expression, as shown in Example 17–1 , on the GatewayID element to identify which B2B documents need to be routed to the third-party B2B software. Example 17–1 Condition Expression on the GatewayID Element condition language=xpath expressionin.SendB2BMcorecom:B2BMcorecom:B2BMHeadercorecom:GatewayID = MyB2BSoftwareexpression condition 6. Use a transformation step, assign step, or both, as required to provide input to the B2B software based on the input B2BM variable, in, as shown in Figure 17–14 . Note that support for Oracle B2B is prebuilt and does not require any modifications. Figure 17–14 Transformation Step to Provide Input to B2B Software

7. The input B2BM variable is received from the provider B2BCSs.

Table 17–4 provides the information from the B2BM variable that can be used to provide input to the B2B software. 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