Contact Free trial Login

Manage Message Flows

After your message flow is running and you are using it with your partners, it doesn’t require a lot of maintenance, but you can manage a message flow anytime, for example:

  • If you are no longer trading with a particular partner and need to delete the message flow you created for them.

  • You completed the testing for a deployed message flow in a pre-production environment, and now want to reclaim the previously allocated Mule runtime engine resources.

  • You want to change a message flow by adding identifiers, selecting different endpoints, or importing a different DataWeave map.

Edit Inbound Message Flows

After you establish a successful inbound message flow with your partner, you can edit the flow to add identifiers, endpoints and message types, or add different DataWeave maps.

Before you make changes, carefully consider the impact on your existing message flow.

  1. From the Anypoint Partner Manager menu on the left, select Message Flows in the upper left, select a <Message flow name> and click it to expand it.

  2. To add an identifier to the message flow, click See All and then New.

  3. To change a receiving endpoint, click Select from the Receiving endpoint section, click New, select your AS2 or SFTP protocol type.

  4. To create a new endpoint, see Create and Configure Endpoints.

  5. To replace your existing DataWeave map, click Import from the Map section to choose a different DataWeave map and click Upload mapping.

  6. To view the map, you can download it by clicking the <name>.dwl link.

    For more information about DataWeave map files, DataWeave Language

  7. To add a message type, click Select under the Source message, select New, and select a standard type such as X12 or JSON.

  8. To set up a target endpoint, click Select from the Target at <partner name>, and depending on the protocol, refer to one of the following:

  9. Verify that any sections of the flow that you updated show a green checkmark next to them, and click Deploy to deploy the configurations to Mule.

    It can take five minutes or so for your configuration changes to sync with Mule.
  10. To test your edited message flow. See Deploy and Test Message Flows.

After you confirm the successful deployment of your message flow, you can track its processed messages from the Activity page.

Manage Outbound Message Flows

After you establish a successful outbound message flow with your partner, you can edit the flow to add identifiers, endpoints and message types, or add different DataWeave maps.

Before you make changes, carefully consider the impact on your existing message flow.

  1. From the Anypoint Partner Manager menu on the left, select Message Flows in the upper left, select a <Message flow name> and click it to expand it.

  2. To change the outbound endpoint, click Select from the Endpoint: Source at <host>, select the endpoint, and click Save.

  3. To create a new outbound endpoint, see Create and Configure an Outbound Message Flow.

  4. To update your reference IDs, expand Reference IDs and select the new reference IDs from the drop-down menus.

  5. To replace your existing DataWeave map, click Import from the Map section to choose a different DataWeave map and click Upload mapping.

  6. To view the map, you can download it by clicking the <name>.dwl link.

    For more information about DataWeave map files, DataWeave Language

  7. To update your message type, click Select under the Source message and select a message type from the drop-down list.
    To create a new message type for the outbound message flow, click New.
    See Create and Configure Message Types.

  8. Verify that any sections of the flow that you updated show a green checkmark next to them, and click Deploy to deploy the configurations to Mule.

    It can take five minutes or so for your configuration changes to sync with Mule.
  9. To test your edited message flow. See Deploy and Test Message Flows.

After you confirm the successful deployment of your message flow, you can track its processed messages from the Activity page.

Delete Message Flows

You might want to delete a message flow when it no longer serves its purpose, for example, if your relationship with your partner changes.

You can delete your message flow from either a sandbox or a production environment.

If you delete a message flow before it is deployed, it does not affect the Mule apps.

For on-premises installations, you must undeploy a message flow before you can delete it.

Steps

After the undeployment is successful, delete the message flow:

  1. In the Partner Manager left navigation menu, select Message Flows.

  2. Select the message flow to delete from the list and click Delete in the upper right of the screen.

Any previous transmissions that were created as a result of a message being processed by the message flow you deleted have the following behavior:

  • The transmissions continue to stay in the transmission records within the Activity page, but the records indicate that the corresponding message flow used to process the transmission is now deleted.

  • These activities are converted into read-only mode, so no links to the message flow work.

  • Only links to the stored payloads (such as the original B2B message, any TA1 acknowledgments, the transformed payload, on so on) that were set up continue to work.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub