Create and Configure an Inbound Message Flow

You can create and configure an inbound message flow to receive EDI messages from your partners, including messages that go through 3rd party connections.

When you create an inbound message flow, you can validate and transform the inbound messages and then send the translated message (JSON or XML) to your backend applications.

To receive messages sent from a partner through a 3rd party connection, select the partner as the source or target and an endpoint owned by the 3rd party connection.

Prerequisites

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

Steps

  1. From the Anypoint Partner Manager navigation menu, select Message Flows.

  2. Click New message flow > Receive from partner.

  3. Either select an existing partner from the list or select New to create a new partner, as described in Create a partner.

  4. Configure the receiving endpoint.

  5. Configure the source message type.

  6. Import the translation map.

  7. Verify that the message flow is complete.

Configure the Receiving Endpoint

Configure the endpoint that will receive the message you are sending. You can do either of the following:

  • Select an existing endpoint owned by the host, target partner, or 3rd party connection.

    If you select an endpoint owned by a 3rd party connection, the inbound message goes through that connection.

  • Create a new receiving endpoint for this message flow.

To specify 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 <partner> window, do either of the following:

    • Select an existing receiving endpoint and click Select.

    • Click New to create a new endpoint, as described in xref:Create and Configure Endpoints.

      The endpoint is added to the message flow, and a message appears indicating that the endpoint is missing an identifier.

AS2 Sender

If the protocol of the receive endpoint is AS2, select the AS2 sender from the dropdown menu:

  • Select the partner’s name (default) if your organization will receive the AS2 messages directly from the partner for whom the message flow is created.

  • Select the name of the 3rd party connection if your organization will receive the AS2 messages for the partner via a 3rd party connection, such as a VAN or 3PL. The AS2 identifier and certificate of the selected 3rd party connection will be used in AS2 message validation.

If you selected AS2 as the receive to partner endpoint protocol, you must import the AS2 certificate of the partner or the 3rd party connection sending the AS2 message, if a certificate already does not exist in the partner or 3rd party connection’s profile.

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, click New next to the search box, configure the X12 or EDIFACT message type, and click Save. The message type and its validation settings are added to the message flow.

  3. If your partner expects your organization to return functional acknowledgements:

    1. In the Acknowledgement section, select the check box next to Send 997 functional acknowledgment (X12) or Send CONTRL functional acknowledgement (EDIFACT) .

    2. Click Select.

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

    4. Alternatively, you can create a new send to partner endpoint:

      1. Click New.

      2. In the Owner field, select the endpoint owner.

      3. In the Protocol field, select and configure the protocol.

      4. Click Save.

        The acknowledgment is added to the message flow.

Import the Translation Map

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

  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 <host> section.

  2. In the Message Type section, click Select.

  3. In the Select message type window:

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

    • To create a new message type, click New next to the search box, define the target at host message type, and 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 <host> section, expand 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 next to 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:

      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 That the Message Flow Is Complete

Partner Manager dynamically validates the message flow configuration elements and confirms by displaying a green checkmark, which indicates that you are ready to deploy the message flow.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub