Contact Free trial Login

Create and Configure a Message Flow

You can create and configure a message flow either when you create a trading partner or afterward. After you deploy the message flow, it’s best to test it.

  1. From within your Anypoint Partner Manager Sandbox or Production environment click New message flows in the upper right.

  2. Select an existing Partner. You can do this from the Select a partner dialog, by searching for a partner by name.

  3. Once you find a match, choose the partner name and click Select. Clicking each section of the message flow expands it. A green checkmark next to any section indicates that it is complete.

    • Alternatively from the Select a partner dialog, you can create a new partner by clicking New. This is the same as Create a Trading Partner except that when you are finished, you’ll click Create Partner and Message Flow. You can add more information to the partner later.

  4. Click Select from the Receiving endpoint section to configure the source endpoint where you receive the transmission.

  5. Click Select to search and select an existing endpoint or click New to create a new endpoint.

  6. To create a new endpoint, depending on the protocol, refer to the following:

    • AS2 Endpoint Settings

    • SFTP Receive Endpoint Settings

      NOTE: For B2B workloads on-premises, deploying a message flow for a new trading partner while using an existing AS2 endpoint to receive messages can result in a brief interruption to the service for existing AS2 trading partner users. To minimize the impact of the service interruption, we recommend performing these message flow deployments outside of your regular business hours. This issue does not exist on CloudHub, as CloudHub provides a zero-downtime update of the AS2 endpoint application.

  7. In the Source message section, click Select to expand the Message Type section.

  8. Either search and click Select to choose a previously used message type or click New to create a new message type.

  9. For a new message type, depending on the message standard, refer to the following:

  10. To optionally edit the validation settings, click View and the hostname. For more information, see X12 Settings - Receive from Partner.

    It may take five minutes or so for your configuration changes to sync with Mule runtime.
  11. For X12 partner requirements, optionally configure the type of functional acknowledgment and the endpoint to which you send it.

  12. Click the Map section and then click Import to choose a DataWeave map.

  13. Select a map and click Upload mapping.

  14. Click the Target at <Partner name> section and click Select to set up a target message type. This is the target message type and the Endpoint where you want to route the transformed message.

  15. Either search and select an existing message type, or create a new message type. To create a new message type, depending on the message standard, follow instructions in one of these sections.

  16. Click Select to set up a target endpoint.

    NOTE: Translated files are delivered to file-based endpoints with a unique file name with the pattern <doctype>-<senderid>-<ISACtrlNum>-<GSCtrlNum>-<STCtrlNum>-<timeInMillis>.<format>. Example: 850-ABCCORP-40952-5850-179960-1587685726355.JSON

  17. Either search for and select an existing endpoint or create a new endpoint by clicking New.

  18. After you create the source, map, and target sections in the interface, confirm that each shows a green checkmark next to it in the flow, and click Deploy to deploy the configurations to Mule.

Your message flow configuration is deployed to your Mule runtime engine and you can start receiving messages from your partner. After a message flow is successfully deployed, you can track its processed messages using the Activity page.

Test Message Flows

You should send test messages through the message flow after you deploy to verify the following:

  • You are receiving messages and acknowledgments from your partners.

  • Make sure that the DataWeave map is working and your backend systems receive the transformed message.

You can test the flow by deploying it in a sandbox environment. When you verify that the flow is successful, you can undeploy it from the sandbox and deploy it to your production environment.

Test your message flow in your Anypoint Partner Manager Sandbox or Production environment:

  1. Initiate a transmission on the receiving endpoint.

  2. From within Anypoint Partner Manager, select Activity and select the transmission from the list.

  3. Scan for an exclamation point (!) in any of the boxes next to the displayed flow stages, indicating an issue with the transmission and address them.

  4. If the system was set up to view payloads, you can review the received payload by clicking View payload next to the Received transmission section. If you are unsure about whether you should be able to view a payload, contact your B2B System Administrator.

  5. If you have TA1 and functional acknowledgments (999 or 997) set, review and confirm that they are there.

  6. Verify that the transmission routed messages to the correct message flows.

  7. Verify that the messages are routed to the target system:

    • Successfully delivered to the target endpoint

    • Transformed correctly

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub