How to Enable Error Handling

17-24 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 17–25 DVM Used to Store Trading Partner B2B Document Type and Document Revision Information While the configuration files described previously can be created and stored locally within the Oracle JDeveloper project, a best-practice recommendation is to externalize these files, store them in MDS, and refer to them from your B2BCS Implementation BPEL project using oramds lookup. Note that though this approach of using DVM files to store the B2B document preference and trading partner-specific transformation information works, the Trading Partner information between the application and these DVM files must be kept synchronized. Each time a new trading partner is defined in the application, a corresponding record should be created in this DVM to store the B2B document preference of the trading partner. A well-established administrative process to manage these changes should be available.

17.3.9 How to Enable Error Handling

For more information about how to enable AIA services for error handling and recovery, see Setting Up Error Handling in Oracle Fusion Middleware Infrastructure Components and Utilities Users Guide for Oracle Application Integration Architecture Foundation Pack. In short, the following steps must be taken: ■ Associate a fault-policy.xml with the B2BCS composite. ■ Invoke the AIAAsyncErrorHandlingBPELProcess for business faults, as shown in Figure 17–26 and Figure 17–27 . Developing and Implementing Outbound B2B Integration Flows 17-25 Figure 17–26 B2BCS Composite Defined to Invoke AIAAsyncErrorHandlingBPELProcess Figure 17–27 Invocation of the AIAAsyncEHService While invoking the AIAAsyncErrorHandlingBPELProcess, the following B2B-specific elements in the fault schema can be populated as described in Table 17–7 . Table 17–7 B2B-Specific Elements in the Fault Schema That Can Be Populated by AIAAsyncErrorHandlingBPELProcess Fault Element Schema Description Example FaultB2BMReferenceB2BMI D Unique identifier of the B2B document 13232325 FaultB2BMReferenceB2BDo cumentTypeTypeCode Document type of the B2B document being generated by the provider B2BCS 855 FaultB2BMReferenceB2BDo cumentTypeVersion Document version of the B2B document being generated by the provider B2BCS 4010 FaultB2BMReferenceB2BDo cumentTypeTypeCodelist AgencyID Standard of the B2B document being generated by the provider B2BCS X12 FaultB2BMReferenceGatew ayID Name of the B2B software being used Oracle B2B FaultB2BMReferenceSender TradingPartnerTradingPartn erID Sender trading partner, mapped from the EBMHeader MyCompany 17-26 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 17–28 provides the B2B-specific elements in the corecom:Fault. Figure 17–28 B2B-Specific Elements in the corecom:Fault The B2B details of the failed AIA service now available in the fault instance will be logged and available for debugging the failed flow.

17.4 Step 3: Developing or Extending an Existing Enterprise Business Service

The next step, as shown in Figure 17–29 , is to develop a new EBS or extend an existing EBS to invoke the provider B2BCS developed in the previous step. For example, the UpdateSalesOrderEBS has to be developed or modified to invoke the X12UpdateSalesOrderProvB2BCSImpl process. FaultB2BMReferenceReceiv erTradingPartnerTradingPar tnerID Receiver trading partner, mapped from the EBMHeader Global Table 17–7 Cont. B2B-Specific Elements in the Fault Schema That Can Be Populated by AIAAsyncErrorHandlingBPELProcess Fault Element Schema Description Example