Step 6: Configuring Oracle B2B and Defining Trading Partner Agreements Step 7: Deploying and Configuring AIA Services

Developing and Implementing Inbound B2B Integration Flows 18-21 Figure 18–20 Step 5: Developing or Extending an Existing Provider ABCS For more information about how to design and construct a provider ABCS, see Chapter 11, Designing Application Business Connector Services and Chapter 12, Constructing the ABCS.

18.6.1 What You Need to Know About Transformations

While you are developing this transformation from EBM to ABM, the Sender and Receiver Trading Partner information can be mapped to appropriate fields in the ABM to capture the source and target of the B2B message, as shown in Table 18–5 . At the end of this step, all of the required AIA services for developing an outbound B2B integration flow are ready.

18.7 Step 6: Configuring Oracle B2B and Defining Trading Partner Agreements

The next step, as shown in Figure 18–21 , is to create trading partner agreements in Oracle B2B. Table 18–5 Sender and Receiver Trading Partner Fields in the EBM EBM Header Element Description Example Value EBMHeaderB2BProfileSen derTradingPartnerTradingPa rtnerID ID of the sending trading partner as defined in Oracle B2B. For inbound flows, this is the remote trading partner. GlobalChips EBMHeaderB2BProfileRec eiverTradingPartnerTrading PartnerID ID of the receiving trading partner as defined in Oracle B2B. For inbound flows, this is the host trading partner. Acme 18-22 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 18–21 Step 6: Configuring Oracle B2B and Defining Trading Partner Agreements For more information about how to define trading partners and associate B2B capabilities with them, see Configuring Trading Partners in Oracle Fusion Middleware Users Guide for Oracle B2B. In addition, for EDI-based outbound B2B flows, Oracle B2B can be configured for batch processing of outbound documents. Parameters such as the batch size and time-out can be configured in Oracle B2B without having to make any changes to the AIA layer.

18.8 Step 7: Deploying and Configuring AIA Services

The next step, as shown in Figure 18–22 , is to deploy the AIA services. You can deploy the services to a target Oracle SOA server using Oracle JDeveloper. Developing and Implementing Inbound B2B Integration Flows 18-23 Figure 18–22 Step 7: Deploying and Configuring AIA Services If any domain value mapping DVM and configuration files are used by the AIA services required for the outbound integration, you must enter data corresponding to your B2B configuration. You can also use the Project Lifecycle Workbench application to create a bill of material XML file for the AIA project, which can be used to autogenerate a deployment plan. This deployment plan can be used to deploy all of the AIA services and resources that make up the integration project in multiple development, test, and production environments. For more information about generating bills of material, see Chapter 2, Working with Project Lifecycle Workbench. For more information about generating deployment plans, see Chapter 6, Generating Deployment Plans and Deploying Artifacts. In addition, configure the AIA Error Handling framework and set up appropriate roles to be notified of errors in AIA flows. For more information about error handling, see Setting Up Error Handling in Oracle Fusion Middleware Infrastructure Components and Utilities Users Guide for Oracle Application Integration Architecture Foundation Pack.

18.9 Step 8: Testing and Verifying