1. Configuring and Managing B2B Messaging
  2. Validate Inbound Collaboration Messaging Setup

Validate Inbound Collaboration Messaging Setup

After you set up B2B messaging in Collaboration Messaging Framework, you need to validate the setup.

Let's see how you can do that for Inbound Collaboration Messages.

  1. In the Collaboration Messaging work area, click the Validate Inbound Collaboration Messaging Setup task.

  2. On the Validate Inbound Collaboration Messaging Setup: Select Sender page, select the sender of the message that you want to validate by selecting your Service Provider and From Partner ID (trading partner), and click Next.

  3. Select the message that you want to validate the setup for by selecting these fields:

    Field

    Description

    External Message Name

    This drop-down list displays all the external message definition names that you set up as inbound messages for the service provider, or trading partner if no service provider is used.

    Collaboration Message Definitions

    This drop-down list displays all the collaboration message definition names that you can use to transform the external message.

    Processing Service

    If your external message standard is OAGIS, select any processing service from the drop-down list as you need.

    If the standard isn't OAGIS, select CollaborationMessageV2.Process or CollaborationMessageV2.ProcessAsync as you need.

  4. Click Next.

  5. On the Validate Inbound Collaboration Messaging Setup: Define Payload page, click Create Message Payload.

    A sample XML payload associated with the message definition is displayed.

  6. Click Process.

    The message is processed as if it were being received from a service provider.

  7. Click Next.

    The processed results appear on the Collaboration Message scree that contains four sections:

    • Details: Displays the details of the business message, trading partner, service provider, and message processing information.

    • Configuration: Displays the details about the configuration of the document and its transformation.

    • Original Message: The sample XML payload associated with the message definition used for transformation.

    • Transformed Message: This shows the message after the XSL transformation has been applied.