Introduction to Error Handling for Oracle B2B Errors

Introduction to Oracle AIA Error Handling 13-5

13.4 Introduction to Error Handling for Oracle B2B Errors

The Oracle AIA Error Handling Framework is automatically triggered when there is an error in Oracle B2B. Oracle B2B can encounter errors while exchanging B2B documents with trading partners. Some common reasons for errors in the Oracle B2B layer include the following scenarios: ■ Failure of document schema validation in the B2B layer. ■ Incorrect or missing trading partner agreements in Oracle B2B. ■ Incorrect or missing document-type definitions in Oracle B2B. ■ Network errors or unavailability of a trading partner system. ■ Authentication failures, for example invalid digital certificates, and so forth. When Oracle B2B encounters these system errors, its default behavior is to publish the error to the Oracle Advanced Queuing AQ queue defined in the Oracle B2B infrastructure schema. The details of the AQ to which Oracle B2B posts errors are covered in Table 13–1 . Figure 13–2 illustrates the way in which the AIA error handling framework captures B2B errors: Note: Business process failures, such as an order being rejected by the trading partner if the ordered item is not in stock, are not considered to be Oracle B2B errors. Response or acknowledgment messages from trading partner applications containing these failures are treated as independent flows. Table 13–1 Oracle B2B Error AQ Details Queue Name IP_IN_QUEUE Database Schema SH_SOAINFRA Queue Consumer b2berroruser Data Source jdbcSOADatasource 13-6 Infrastructure Components and Utilities Users Guide Figure 13–2 Error Handling Framework Support for Capturing B2B Errors These errors can be viewed in error reports available in the Oracle B2B console. For more information about viewing Oracle B2B error reports, see Chapter 19, Accessing Oracle B2B Errors. For Oracle B2B inbound and outbound flows, when an error occurs within the Oracle B2B server and not in the AIA layer, the AIA fault has the capacity to capture only the B2B-specific details. Enterprise Business Message EBM details will not be available. However, in the case of an error in an outbound flow, AIA is able to track the EBMID and include that information in the fault. 14 Setting Up Error Handling 14-1 14 Setting Up Error Handling This chapter provides and overview and discusses how to create user roles, associate email addresses to user roles, configure notification details, and how to set up error handling configuration details. This chapter includes the following sections: ■ Section 14.1, Introduction to Setting Up Error Handling