Contact Free trial Login

Create and Configure an Outbound Message Flow

You can create and configure an outbound message flow to receive application messages from your backend systems, validate and transform these messages, and then send the translated EDI message to your trading partners.

Create an Outbound Message Flow

  1. From your Anypoint Partner Manager sandbox or production environment, select Message Flows in the left navigation menu.

  2. Click New message flow > Send to partner in the upper right of the page.

  3. Select an existing partner from the list and click Select or select New to create a trading partner.
    A new message flow is created.

Configure the Source at Host Endpoint

  1. Expand the Source at <host-name> section.

  2. In Endpoint: Source at <host-name>, click Select.

  3. In the Select an endpoint: Source at <host-name> window:

    1. To use an existing receiving endpoint:

      1. Select the endpoint from the list and click Select.
        The endpoint is added to the message flow, and a message appears indicating that the endpoint is missing an identifier.

      2. Click Add to add a unique identifier for the endpoint.

    2. To create a new receiving endpoint:

      1. Click New to the right of the search box.

      2. From the Owner drop-down list, select the endpoint’s owner.

      3. From the Protocol drop-down, select the protocol and configure it according to the protocol you select:

  4. Click Save.
    The endpoint is added to the message flow.

Configure the Source Message Type

  1. Expand the Source at <host> section.

  2. In the Source message type section, click Select.

  3. In the Select message type section:

    1. To use an existing message type, select the message type from the list and click Select.

    2. To create a new message type:

      1. Click New to the right side of the search box.

      2. From Format, select either:

        • JSON

        • XML

      3. From Schema, click Choose file and browse to the location of your custom schema.

      4. Accept the default value for Message type identifier or enter a new value.

      5. Click Choose file to browse to the location of the DataWeave map and select it.

      6. Click Save. The message type is added to the message flow.

Configure Reference IDs

  1. Expand the Source at <host> section.

  2. From the <host> reference ID drop-down list, select your organization’s internal reference ID (such as business unit name) as it would appear in the data element of the source JSON or XML payload from your backend systems.
    The reference ID is added to the message flow.

Import the Translation Map

Prerequisites

To create your outbound EDI-to-application message (JSON or XML) map in Anypoint Studio, see EDI Translation Maps.

Steps

  1. In the message flow, expand the Map section.

  2. Click Import and then click Choose file.

  3. In the New mapping file window, navigate to the DataWeave map you want to use and then click Open.

  4. Click Upload mapping.
    The translation map is added to the message flow.

Configure the Target Message Type

  1. Expand the Message type section and click Select.

  2. In the Select message type window:

    1. To use an existing message type, select the message type from the list and click Select.

    2. To create a new message type:

      1. Click New to the right of the search box.

      2. From Format, select X12.

      3. From Version, select the X12 version.

      4. From Message type, select the message type.

      5. From schema select Use standard X12-<version>-<message-type> or select Customize to define a custom schema.

      6. Click Save.
        The message type and its validation settings are added to the message flow.

  3. In the Acknowledgment section, select Expect functional acknowledgment if you expect your partner to return functional acknowledgments (997).

    1. In the Select an endpoint: Receive acknowledgment from <parter> window, click Select to specify the endpoint from which to receive the acknowledgment transactions from your partner.

    2. Alternatively, you can create a new receive from partner endpoint:

      1. Click New.

      2. From Owner, select the endpoint owner.

      3. From Protocol, select the protocol and configure it accordingly:

        • AS2

        • SFTP

      4. Click Save.

      5. In Mark overdue after, accept the default value of 24 Hours or configure values based on when you want the outbound transaction to be designated as overdue for an acknowledgment, according to the SLAs you have with your trading partner.
        When a functional acknowledgment is not received within the specified timer value, Partner Manager marks the outbound transactions as Overdue.

  4. In the X12 Settings drop-down list, select the X12 settings.

    By default, Partner Manager uses the X12 send settings that are configured in the trading partner profile page for message validation, delimiters, and character encoding.

    If you want to apply custom validation settings and delimiters for the message flow you are setting up, you can select Custom X12 settings and provide custom configuration values.

  5. In X12 Identifiers, select the sender and receiver identifiers that are configured under the host and trading partner profiles to use them on the X12 ISA and GS segments.

Verify the Message Flow is Complete

Partner Manager dynamically validates the message flow configuration elements for completeness and displays a green checkmark if all the building blocks of the message flow are complete. After you verify the configurations, you are ready to deploy the message flow.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub