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 objects

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

  • Inbound

    An inbound message flow receives EDI payloads from your trading partners, translates them into your internal application message format, and sends the translated messages to your backend systems.

  • Outbound[Outbound message flow]

    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
Setting Description Supported Formats or Protocols

Receiving endpoint

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

  • AS2

  • FTP

  • SFTP

Source message type

The message type of the input payload.

  • X12

  • EDIFACT

Transform

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

N/A

Target message type

The format into which the DataWeave map transforms received messages.

  • JSON

  • XML

Target endpoint

The endpoint to which the translated JSON or XML payload needs to be sent. This is typically a process API.

  • FTP

  • HTTP

  • HTTPS

  • SFTP

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 the transformation of your outbound business transactions from your organization’s backend systems to your trading partners:

Outbound message flow
Setting Description Supported Formats or Protocols

Receiving endpoint

The endpoint where the host receives transmissions from the backend.

  • FTP

  • HTTP

  • HTTPS

  • SFTP

Source message type

The message type of the input payload received from the backend.

  • JSON

  • XML

Transform

The DataWeave map for JSON or XML to EDI translation.

N/A

Target message type

The message type to which the input payload needs to be translated.

  • EDIFACT

  • X12

Target endpoint

The trading partner endpoint to which the translated EDI payload needs to be sent.

  • AS2

  • FTP

  • HTTP

  • HTTPS

  • SFTP

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub