Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle B2B
11g Release 1 (11.1.1)

Part Number E10229-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

D Exception Handling

Oracle B2B handles exceptions for inbound and outbound messages. This appendix describes the exception handling, error messages, and structures for Oracle B2B.

This appendix contains the following topics:

D.1 Inbound Messages

This section describes the following inbound message types:

D.1.1 Request or Response Messages

For an incoming request or response message that results in an exception, the following actions occur:

  • An exception message is sent to the application.

    The exception message is enqueued to B2B_IN_QUEUE and has the recipient name b2berroruser. The enqueued exception is based on ipException.xsd and contains information such as the error message (errorText has a short description and errorDescription has a longer description) and the error code.

  • An exception message is sent to the trading partner, if mandated by the exchange specification.

    The exception message is sent back to the trading partner only if there is enough information to identify the outgoing trading partner agreement. For this purpose, the flag B2BHeader.sendException is used. The flag is set to true when enough information is extracted from the incoming message to send the exception message to the trading partner.

  • Oracle B2B catches exceptions thrown by exchange or document layers.

    If the B2Bheader.sendException flag is set to true, the outgoing trading partner agreement is processed and an exception message is sent to the trading partner.

D.1.2 Acknowledgment Messages

For an incoming acknowledgment message that results in an exception, the following actions occur:

  • An exception message is sent to the application.

    The exception message is enqueued to B2B_IN_QUEUE and has the recipient name b2berroruser. The enqueued exception is based on ipException.xsd and contains information such as error text and error code.

  • No exception message is sent back to the trading partner.

D.1.3 Exception Messages

For an incoming exception message, the following actions occur:

  • The original message is updated so that it is in an errored state. The incoming exception is processed and delivered to the application normally.

  • If the incoming exception message itself results in an exception, an exception message is sent to the application.

    The exception message is enqueued to B2B_IN_QUEUE and has the recipient name b2berroruser. The enqueued exception is based on ipException.xsd and contains information such as error text and error code. No exception message is sent back to the trading partner in this case.

B2B errors cannot be delivered on other queues that you may configure (for example, an AQ or JMS queue).

D.1.4 Failures with Inbound ebMS, AS1, and AS2 Messages

If the following types of failure occur while an incoming message is processing, then the receiving trading partner sends a negative acknowledgment to the sender.

  • Decryption fails

  • Verification fails

  • Agreement is not found

  • Document identification fails

  • Document validation fails (and so on)

The negative acknowledgment message has the reference for the original (request) message details to correlate at the sender side.

D.2 Outbound Messages

If an exception occurs while an outbound message is being sent (for example, if the trading partner identification fails), then an exception message is sent to the application. The exception message is enqueued to B2B_IN_QUEUE and has the recipient name b2berroruser. The enqueued exception is based on ipException.xsd and contains information such as error text and error code.

If an exception occurs during Oracle B2B startup, then an exception message is enqueued to B2B_IN_QUEUE and has the recipient name b2berroruser. The enqueued exception is based on ipException.xsd and contains information such as error text and error code. The correlation ID is not populated in this case.

Note the following:

D.3 Inbound Exception Handling Scenarios

Table D-1 describes inbound exception handling scenarios.

Table D-1 Inbound Exception Handling Scenarios

If an exception occurs because. . . Then Oracle B2B does . . .

The identification of the exchange fails or the exchange is not supported

  • Notifies the middleware

  • Updates the wire message as in an errored state

  • Creates a business message in an errored state for the wire message

  • Sends a transport error message to the trading partner if the sendException flag is set in the exchange layer

Message unpacking fails

  • Notifies the middleware

  • Updates the wire message as in an errored state

  • Creates a business message in an errored state for the wire message

Incoming message decoding fails

  • Notifies the middleware

  • Updates the wire message as in an errored state

  • Creates a business message in an errored state for the wire message

  • Sends an exception message to the trading partner, if the sendException flag is set in the exchange layer

The message is duplicated

  • Notifies the middleware

  • Updates the wire message as a duplicated message error

  • Creates a business message as a duplicated message error for the wire message

Document identification fails

  • Notifies the middleware

  • Updates the wire message as in an errored state

  • Creates a business message in an errored state for the wire message

  • Sends an exception message to the trading partner, if the sendException flag is set in the exchange layer

Incoming trading partner agreement processing fails

  • Notifies the middleware

  • Updates the wire message as in an errored state

  • Creates a business message in an errored state for the wire message

  • Sends an exception message to the trading partner, if the sendException flag is set in the exchange layer

Incoming document processing fails

  • Notifies the middleware

  • Updates the wire message as in an errored state

  • Creates a business message in an errored state for the wire message

  • Sends an exception message to the trading partner, if the sendException flag is set in the exchange layer


Note the following:

D.4 Exception Payload Definition

The exception payload, ipException.xsd, is defined as follows:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://integration.oracle.com/B2B/Exception" targetNamespace="http://integration.oracle.com/B2B/Exception">
 
  <xs:element name="Exception">
    <!--xs:complexType name="Exception"-->
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="correlationId"/>
        <xs:element ref="b2bMessageId"/>
        <xs:element ref="errorCode"/>
        <xs:element ref="errorText"/>
        <xs:element ref="errorDescription"/>
        <xs:element ref="errorSeverity"/>
        <xs:element ref="errorDetails" minOccurs="0" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>
  <xs:element name="correlationId" type="xs:string"/>
  <xs:element name="b2bMessageId" type="xs:string"/>
  <xs:element name="errorCode" type="xs:string"/>
  <xs:element name="errorText" type="xs:string"/>
  <xs:element name="errorDescription" type="xs:string"/>
  <xs:element name="errorSeverity" type="xs:string"/>
  <xs:element name="errorDetails">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="parameter" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
  <xs:element name="parameter">
    <xs:complexType>
      <xs:attribute name="name" type="xs:string" use="required" /> 
      <xs:attribute name="value" type="xs:string" use="required" /> 
    </xs:complexType>
  </xs:element>
</xs:schema>