Contact Free trial Login

Partner Manager Message Flows

A message flow is the path along which a message travels from its source, through a DataWeave transformation map, to its target. You set up message flows to send and receive messages between your systems and your trading partners.

Partner Manager message flows consist of objects such as endpoints, message types, identifiers, and mappings. Partner Manager’s message framework orchestrates the processing of your business transactions from source to target using these configuration objects as shown in the following diagram:

Partner Manager message flow configuration building blocks

You can create message flows in one of the following contexts:

  • Inbound
    Receive messages from trading partners

  • Outbound
    Send messages to trading partners. An outbound message flow receives application messages from your backend systems, translates the message to EDI, and sends the EDI transmissions to your trading partner.

Inbound Message Flows

Create an inbound message flow to receive and translate application messages from your partner and forward them to your backend systems:

Inbound message flow configuration building blocks diagram
Setting Description Supported Formats or Protocols

Receiving endpoint

The endpoint where the host receives transmissions from the trading partner.

  • AS2

  • SFTP

Source message type

The message type to process for the message flow.

  • EDI X12 formats

  • EDI identifiers

Transform

The DataWeave map used to transform EDI into XML or JSON formats.

  • JSON

  • XML

Target message type

The format into which the DataWeave map transforms received messages.

  • JSON

  • XML

Target endpoint

The final destination of a message flow. The target endpoint is defined by a host message type and endpoint, often a host API.

  • SFTP

  • HTTP

  • HTTPS

Outbound Message Flows

Create an outbound message flow to receive and transform application messages from your backend systems and then forward the translated EDI messages to your partners.

The following diagram shows the configurations of an outbound message flow. The diagram also shows how Partner Manager’s message processing framework orchestrates the end-to-end routing and transformation of your outbound business transactions from your organization’s backend systems to your trading partners.

Outbound message flow configuration building blocks diagram
Setting Description Supported Formats or Protocols

Receiving endpoint

The endpoint where the host receives transmissions from the backend.

  • HTTP

  • HTTPS

  • SFTP

Source message type

The message type to process for the message flow.

  • JSON

  • XML

Transform

The DataWeave map for JSON or XML to EDI translation.

  • JSON

  • XML

Target message type

The message type to process for this message flow, using the X12 format and EDI identifiers.

  • JSON

  • XML

Target endpoint

The final destination of a message flow.

  • AS2

  • SFTP

  • HTTP

  • HTTPS

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub