1. Using B2B for Oracle Integration 3
  2. B2B Tracking
  3. Work with Business Messages

Work with Business Messages

On the Business messages page, you can resubmit, filter, or view details of business messages.

  1. Resubmit business messages.
    1. For inbound business messages, the Resubmit feature enables you to redeliver messages to the backend applications. To redeliver an inbound business message, click Retry iconResubmit. A dialog notifies that the message will be redelivered, click Resubmit in the dialog.
      The Resubmit message dialog.

      Redelivering an inbound business message may be required in the following scenarios:
      • Changes in an inbound agreement
      • A request from a backend application for a particular B2B message
      • A failure in the backend integration processing
    2. For outbound business messages, the Resubmit feature enables you to reprocess the application messages from the time of receipt (with older payloads). To reprocess an outbound business message, click Retry iconResubmit. A dialog notifies that the message will be reprocessed and redelivered, click Resubmit in the dialog.
      The Resubmit message dialog.

      Reprocessing an outbound business message may be required in the following scenarios:
      • Issues with the target trading partner's endpoint
      • Re-creation of business messages after an update to the agreement or document configurations

    When you resubmit a message, a notification is displayed indicating that it was resubmitted. If you refresh the screen, the message will have the Resubmitted label. Hover the cursor over the label to view the information indicating the user who resubmitted the message and the time at which it was done.

    Note:

    • You can resubmit both failed and successful transactions.
    • You can resubmit an original message multiple times. However, you cannot resubmit the child messages.
    • You can resubmit a message only if the underlying integration has a REST Adapter trigger or an AS2 Adapter trigger, and is allowed to run again.

      Auto-generated B2B integrations are allowed to run again by default. However, for backend-process integrations, you'll have to manually select the Allow to run again option while activating them. See Replay Integration Instances in Using Integrations in Oracle Integration 3.

  2. View details of business messages.

    Click View details View details icon on a message to open the Business message details panel.


    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.

    The panel contains the following tabs:

    • Properties: Shows the agreement name, document ID, group control number, interchange control number, and transaction control number.
    • Message logs (displayed by default): The message log is similar to the activity stream available for integrations. It provides the execution details.
    • Payloads: Shows the payload information related to the business message.
    • Correlations: Shows all messages related to the selected business message. This tab typically lists the corresponding wire messages, resubmitted messages, and the integration instance.

      In a resubmitted message, this tab contains a link to the original message. And in the original message, this tab contains a link to all resubmitted messages.

      To view a correlated message, click the corresponding link. Click the integration instance link to view the backend integration that includes this B2B message on the Instances page.

      For RosettaNet integrations, a Collaboration link is provided.


      The Properties, Message logs, Payloads, and Correlations tabs are shown. Correlations is selected. Below this are links for wire messages, integration instance, and collaboration.

      The Collaboration link shows the correlation of messages between buyer and seller. For example, if PIP3A4 is used, the following message correlation is shown.
      • Sent by buyer: request(:PurchaseOrderRequestAction)
      • Sent by seller: signal(:ReceiptAcknowledgement)
      • Sent by seller: response(:PurchaseOrderAcceptanceAction)
      • Sent by buyer: signal(:ReceiptAcknowledgement)


      The four messages are shown as being successfully processed.

      These messages are visible in both the buyer and seller integrations in the Track B2B messages page.

  3. Filter business messages.
    Click Filter Filter icon to filter messages by the last message created, time window, trading partner name, direction, message type, status, document standard, message ID, transport message ID, integration instance ID, error code, parent message ID, and so on.

    In addition, you can also filter messages based on the resubmit status and resubmitted message ID.