Description of the illustration com_ofm_faultmessage.gif

The figure shows fault messages created and submitted from two error sources, either a partnerLink error coming from a composite process, or a composite catch block error coming from a composite process with custom business error handling.

The integration submits these faults to the Oracle AIA error topic as follows:

  1. The integration sends the faults to the Oracle AIA common error handler as follows, depending on the source of the error:

    • Errors coming from a regular composite process go to the composite fault policy, which implements the handleCompositeSystemError method. This method includes a composite error Java action, which sends the message to the AIA common error handler.

    • Errors coming from a composite process with custom business error handling go to the AIA error handler asynchronous composite process, which implements the HandleBusinessError method. This method includes a business error handler that communicates with a business extension handler and sends the message to the Oracle AIA common error handler.

  2. The Oracle AIA common error handler adds the errors from either type of composite process to the Oracle AIA error topic and the Oracle AIA error logger.

  3. The AIA error topic creates the error task list, which users can view in the error console.

  4. The Oracle AIA logger creates the error log, which users can view in the Oracle Enterprise Manager console.