Contact Free trial Login

Create and Configure an Inbound Message Flow

You can create and configure an inbound message flow to receive EDI messages from your trading partners, validate and transform those messages, and then send the translated application (JSON or XML) message to your backend applications.

Create an Inbound Message Flow

Prerequisites

Before you create your first inbound message flow, you must configure your payload storage API.

Steps

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

  2. Click New message flow > Receive from partner in the upper right of the page.

  3. Either 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 Receiving Endpoint

  1. In the message flow, expand the Receiving from <partner> section and click Select endpoint.

  2. In the Receiving endpoint section, click Select.

  3. In the Select an endpoint: Receive from <host> 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 on the right of the search box.

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

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

        • AS2

        • SFTP

          Translated files are delivered to file-based endpoints with a unique file name with the pattern <doctype>-<senderid>-<ISACtrlNum>-<GSCtrlNum>-<STCtrlNum>-<timeInMillis>.<format>, for example: 850-ABCCORP-40952-5850-179960-1587685726355.JSON
      4. Click Save.
        The endpoint is added to the message flow.

Configure the Source Message Type

  1. In the message flow, expand the Source message 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 then click Select.

    2. To create a new message type:

      1. Click New on the right side 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.

Import the Translation Map

Prerequisites

To create your inbound EDI-to-application message (JSON or XML) map in Anypoint Studio, follow these instructions.

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

  1. In the message flow, expand the Target at <your organization> section.

  2. In the Message Type section, click Select.

  3. In the Select message type window:

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

    2. To create a new message type:

      1. Click New on the right side 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 is selected for your backend system to use to map the EDI transaction. Partner Manager routes inbound EDI transactions based on matching identifiers configured at the Partner level.

  4. In the Target at <your organization> section, exand the Endpoint section and click Select.

  5. In the Select an endpoint: Target to <host> window:

    1. To use an existing endpoint, select the endpoint from the list and then click Select.

    2. To create a new endpoint:

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

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

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

        • HTTP or HTTPS

        • SFTP

          Translated files are delivered to file-based endpoints with a unique file name with the pattern <doctype>-<senderid>-<ISACtrlNum>-<GSCtrlNum>-<STCtrlNum>-<timeInMillis>.<format>, for example: 850-ABCCORP-40952-5850-179960-1587685726355.JSON
      4. Click Save.
        The endpoint to which to send the translated message (JSON or XML) for further processing in your backend system is added to the message flow. Partner Manager routes inbound EDI transactions based on matching identifiers configured at the partner level.

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