---
schema_version: "1"
id: 4c68c72745ad37ba942cf8d86a7dbba30ea6346252a2623f01e3727ba0a3113a
title: Source at Host Message Type Settings
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/message-type-source-at-host.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/message-type-source-at-host
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 56acc757d7d4e9568c42458ba21f950060d5b1e40532b433ed482cb07848eb52
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Source at Host Message Type Settings

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th><th>Required</th></tr></thead><tbody><tr><td><p>Usage</p></td><td><p>Message usage. Allowed value is <code>Source at Host</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Format</p></td><td><p>Format of the message. Allowed value is <code>CSV</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Separator character</p></td><td><p>Character that separates values in the file.</p></td><td><p>,</p></td><td><p>Yes</p></td></tr><tr><td><p>Quote character</p></td><td><p>Character used as a quote character in the file.</p></td><td><p>""</p></td><td><p>Yes</p></td></tr><tr><td><p>Escape character</p></td><td><p>Character used as an escape character in the file.</p></td><td><p>\</p></td><td><p>Yes</p></td></tr><tr><td><p>Header line</p></td><td><p>When selected, Partner Manager skips the header row when it processes a CSV file.</p></td><td><p>Selected</p></td><td></td></tr><tr><td><p>Ignore empty line</p></td><td><p>When selected, Partner Manager ignores empty lines when it processes a CSV file.</p></td><td><p>Selected</p></td><td></td></tr><tr><td><p>Reference identifiers and attributes mapping</p></td><td><div><div><p>Uploaded DataWeave map that extracts the reference identifiers and custom attributes from the payload received from the partner:</p></div><div><ul><li><p>The extracted reference identifier values are used for dynamic routing into the appropriate message flow.</p></li><li><p>The extracted custom attributes provide visibility into the lifecycle of your B2B workflow. For more information, see <a href="https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes">Using Custom Messaging Attributes with Message Types</a>.</p></li></ul></div></div></td><td></td><td><p>No</p></td></tr></tbody></table>

## JSON or XML

Use the settings in the table to define JSON or XML as the format for the Receive from Partners
message type.

If you process cXML messages with <DOCTYPE> tags, you must set the `minMuleVersion` to 4.5.0 or
higher and upgrade your runtime environment. For more information, see Partner Manager deployment
settings for [CloudHub](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings),
[CloudHub 2.0](https://docs.mulesoft.com/partner-manager/latest/cloudhub2-deployment-settings), and [Runtime Fabric](https://docs.mulesoft.com/partner-manager/latest/rtf-deployment-settings).

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th><th>Required</th></tr></thead><tbody><tr><td><p>Format</p></td><td><div><div><p>Application message structure format. Allowed value is <code>JSON</code> or <code>XML</code>.</p></div></div></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Schema</p></td><td><p>Imported JSON or XSD schema file for the message type.</p></td><td></td><td><p>No</p></td></tr><tr><td><p>Message type identifier</p></td><td><div><div><p>See <a href="https://docs.mulesoft.com/partner-manager/latest/outbound-message-routing">Outbound Message Routing</a> 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.</p></div></div></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Reference identifiers and attributes mapping</p></td><td><div><div><p>Uploaded DataWeave map that extracts the reference identifiers, business key, and custom message attributes from the payload received from the back-end application:</p></div><div><ul><li><p>The extracted reference identifier values are used for dynamic routing into the appropriate message flow.</p></li><li><p>The extracted custom attributes enable you to have visibility into the lifecycle of your B2B workflow. For more information, see <a href="https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes">Using Custom Messaging Attributes with Message Types</a>.</p></li></ul></div></div></td><td><p>None</p></td><td><p>Yes</p></td></tr></tbody></table>

## See Also

- [Message Types](https://docs.mulesoft.com/partner-manager/latest/document-types)

- [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type)

- [Deleting Message Types](https://docs.mulesoft.com/partner-manager/latest/delete-message-types)