Contact Free trial Login

Create and Configure an Inbound Message Flow

You can create and configure an inbound message flow either when you create a trading partner, or after you create a trading partner.

After you create the inbound message flow, you configure the receive endpoint, source message type, target message type, and target endpoint.

Create an Inbound 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 > Receive from partner in the upper right of the page.

  3. Select an existing Partner from the list and click Select.
    A new message flow is created.
    Alternatively, from the Select a partner dialog, you can click New to create a new partner. Follow the process to create a Trading Partner, except that when you are finished, click Create Partner and Message Flow.

Configure the Receive Endpoint

  1. Expand the Receiving endpoint section and click Select.

  2. To use an existing receiving endpoint:

    1. Select the endpoint from the list and click Select in the lower right side of the page.
      The endpoint is added to the message flow, and you see a message that tells you the endpoint is missing an identifier.

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

  3. 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.

Configure the Source Message Type

  1. Expand the Source message type section, and click Select.

  2. To use an existing message type:

    1. Select the message type from the list and click Select in the lower right side of the page.
      The message type is added to the message flow.

  3. 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

Expand the Map section and click Import to upload the DataWeave map to translate the EDI message to your application message format.

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

Configure the Target Message Type

  1. Expand the Target at <your organization> section.

  2. Click Select to select the message type of your backend system to which to map the EDI transaction.
    Partner Manager routes inbound EDI transactions based on matching identifiers configured at the Partner level.

Configure the Target Endpoint

  1. Select the endpoint to which to send the translated message (XML or JSON) for further processing in your backend system.
    In the Select endpoint window, click New to create a new endpoint.
    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