1. Using B2B for Oracle Integration Generation 2
  2. B2B Tracking
  3. Track B2B Messages

Track B2B Messages

You can track the B2B message interaction between trading partners on the Track B2B Messages page. This page provides B2B-specific message tracking information that is not available on the Track Instances page for integrations.

Note:

This feature is only available on Oracle Integration Generation 2.
  1. In the left navigation pane, click Home > Monitoring > B2B Tracking.

    The Wire Messages tab of the Track B2B Messages page is displayed.

    Wire messages are raw messages exchanged between trading partners. Wire messages flow back and forth between trading partners across the dotted line shown in the following document transaction example. For the following example, an interaction is initiated by an inbound message sent from a trading partner to the host trading partner (site in which Oracle Integration is installed). There are four message interactions in this example. All four are tracked on the Track B2B Messages page.

    1. The host trading partner receives an invoice document (EDI 810) from a trading partner.
    2. The host trading partner performs the following actions:
      1. Sends a message disposition notification (MDN) to the trading partner to acknowledge receipt of the invoice.
      2. Parses the EDI document to a format understood by Oracle Integration.
    3. The host trading partner sends a functional acknowledgment (EDI 997) to the trading partner.
    4. The trading partner sends a message to the host trading partner acknowledging receipt of the EDI 997.

    These B2B message interaction details are captured on the Track B2B Messages page.
    Description of tp_wire_message.png follows
    Description of the illustration tp_wire_message.png

    The left column identifies the message direction. Inbound messages (those received by the host Oracle Integration trading partner) are identified by Inbound message and outbound messages (those sent from the host Oracle Integration trading partner) are identified by Outbound messages.

    The Payload Name column shows the payload file that was transmitted.

  2. Click Filter icon to filter B2B message display by the last message created, time window, trading partner name, direction, message type, status, transport protocol, message ID, transport message ID, integration instance ID, error code, payload name, and parent message ID.
  3. Click an entry in the Status column or click Details icon. For this example, a B2B document sent in the inbound direction to the host trading partner is selected. Note also that MDN acknowledgment messages that were sent or received are also available for selection.

    This opens the Wire Message Details page. The Message Logs tab is displayed by default.
    A table with columns for Status and Transport Message appears on the left side. The status of Successful is selected. To the right, the Wire Message Details dialog shows a Close button in the upper right. Below is the message ID number. Below is the Primary Information section with tabs for Properties, Message Logs, Payloads, and Correlations. Below this is the Execution Details section.

  4. View the following details in the four available tabs:
    • Message Logs (displayed by default): The message log is similar to the activity stream available for integrations. It provides details such as the following:
      • The message sent from the trading partner to the host trading partner (since this example is an inbound message). The trading partner names shown are based on the headers that you mapped to the B2B identifiers defined in the agreement. See Create Trading Partners.
      • The identity of the trading partner that sent the message.
      • The unpacking of the message (preprocessing tasks such as message decryption, signature verification, and others).
      • The status of the MDN acknowledgment message sent to the trading partner (for this example, the status is successful).
      • Additional postprocessing tasks.
    • Properties: Shows header properties and values (for example, HTTP and MIME).
      The Wire Message Details dialog shows a Close button in the upper right. Below is the message ID number. Below is the Primary Information section with tabs for Properties, Message Logs, Payloads, and Correlations. Below this is a table with columns for Property and Value.

    • Payloads: Shows the following details:
      • Packed Payload: Shows the physical EDI payload sent from the trading partner for this example. The payload may be encrypted and signed if both were configured by the trading partner. A signed payload ensures that your message cannot be repudiated.
      • Unpacked Payload: Shows the raw, unencrypted version of the payload sent from the trading partner. The payload format may be signed if it was configured by the trading partner.

      Click Download icon to download the packed or unpacked version of the payload.


      The Wire Message Details dialog shows a Close button in the upper right. Below is the message ID number. Below is the Packed Payload section, with a Download button to the right. Below is the Unpacked Payload section, which is expanded to display the message payload. A Download button is displayed to the right.
    • Correlations: Shows the messaging interaction between trading partners. This tab provides insight into the entire message interaction between trading partners.
      The Wire Message Details dialog shows a Close button in the upper right. Below is the message ID number. Below is the Primary Information section with tabs for Properties, Message Logs, Payloads, and Correlations. Below are links for MDN, Business Messages, and Integration Instance.

      • MDN(s):
        1. Click MDN(s) to show the B2B Messages tab filtered to show only details about the MDN message that the host trading partner sent back to the trading partner to acknowledge receipt of the initial inbound message (for this example).
        2. Click the status in the Status column (for example, MDN Sent) to show property, message log, payload, and correlation links with details about the sent MDN message.
        3. Click Correlations to show the message correlation in this transaction from the perspective of the MDN message.
          The MDN Message Details dialog shows a Close button in the upper right. Below is the message ID number. Below is the Primary Information section with tabs for Properties, Message Logs, Payloads, and Correlations. Below are links for Wire Messages and Integration Instance.

      • Business Message(s):
        1. Click Business Message(s) to show the Business Messages tab of the Track B2B Messages page filtered to show only details about the business message in this interaction. Depending upon the message interaction, multiple business messages can be displayed. When the payload is translated with the EDI parser, an XML message is created that corresponds to this business message.

          If the business message includes an invoice, a Customer Identifier column is displayed that provides the invoice number extracted from the business message.

        2. Click the status in the Status column to show property, message log, payload, and correlation details about the business message.
        3. Click Correlations to show the message correlation in this transaction from the perspective of the business message.
          The Business Message Details dialog shows a Close button in the upper right. Below is the message ID number. Below is the Primary Information section with tabs for Properties, Message Logs, Payloads, and Correlations. Below are links for Functional Acknowledgment, Wire Messages, and Integration Instance.

      • Integration Instance: number:
        1. Click Integration Instance: to access the backend integration that includes this B2B message on the Track Instances page.