Contact Us 1-800-596-4880
  1. Homepage
  2. Partner Manager (2.x)
  3. Message Flow Components
  4. Message Types

  5. Source at Host Message Type Settings

Source at Host Message Type Settings

The Source at Host message type defines the way in which your backend applications transform outbound transactions and send them to your organization.

You can define the CSV, JSON, or XML formats for the Source at Host message type.

CSV

Use the following settings to define CSV as the format for the Source at Host message type:

Setting Description Default Required

Usage

Message usage. Allowed value is Source at Host.

Yes

Format

Format of the message. Allowed value is CSV.

Yes

Separator character

Character that separates values in the file.

,

Yes

Quote character

Character used as a quote character in the file.

""

Yes

Escape character

Character used as an escape character in the file.

\

Yes

Header line

When selected, Partner Manager skips the header row when it processes a CSV file.

Selected

Ignore empty line

When selected, Partner Manager ignores empty lines when it processes a CSV file.

Selected

Reference identifiers and attributes mapping

Uploaded DataWeave map that extracts the reference identifiers and custom attributes from the payload received from the partner:

  • The extracted reference identifier values are used for dynamic routing into the appropriate message flow.

  • The extracted custom attributes provide visibility into the lifecycle of your B2B workflow. For more information, see Using Custom Messaging Attributes with Message Types.

No

JSON or XML

Use the following settings to define JSON or XML as the format for the Source at Host message type:

Setting Description Default Required

Format

Application message structure format. Allowed value is JSON or XML.

Yes

Schema

Imported JSON or XSD schema file for the message type.

No

Message type identifier

See Outbound Message Routing to understand how Partner Manager performs outbound routing and how your backend applications pass the message type identifier when sending application messages to Partner Manager endpoints.

Yes

Reference identifiers and attributes mapping

Uploaded DataWeave map that extracts the reference identifiers, business key, and custom message attributes from the payload received from the back-end application:

  • The extracted reference identifier values are used for dynamic routing into the appropriate message flow.

  • The extracted custom attributes enable you to have visibility into the lifecycle of your B2B workflow. For more information, see Using Custom Messaging Attributes with Message Types.

None

Yes

See Also