# mulesoft Partner Manager - Full Documentation --- product: Partner Manager version: 2.x is-latest-version: true --- # Accessing Source Message Attributes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt When you create translation or reference maps for inbound or outbound message flows, you can access source message attributes in those maps. You can then map the attributes to fields in the translated message payload or use the attribute values in your mapping logic to perform dynamic condition execution. ## Common Use Cases Accessing source message attributes helps in many use cases, such as with performing dynamic message routing decisions, performing specific functions, and mapping fields within the data transformation in the message flow execution. Some common use cases include: - Achieving end-to-end transmission tracing Accessing transmission IDs in the translation maps enables end-to-end transmission tracing because these IDs are passed to the translated JSON or XML output file. - Mapping attributes to pass them to the backend For example, if the backend must see the source filename or a specific HTTP header, you can access the filename or HTTP header and map the values to the translated message payload fields. - Applying mapping logic based either on a filename part or pattern within the transformation For example, you can access a filename prefix through substring operations and then build dynamic mapping logic based on this prefix. - Mapping attributes to make them available in the search For example, you can access the source filename or a specific HTTP header value as a custom message attribute in the message type’s reference map to easily search for these values in the Activity screens. For more information, see [Use Case Implementation Examples](#implementation-examples). The source attributes that you can access are available within a predefined variable named `b2bMessageContext`. The content of this variable differs depending on the source endpoint’s protocol. ## AS2 Source Endpoint Messages received via AS2 contain the following fields in the `b2bMessageContext` variable: - sourceProtocol - transmissionId - sourceEndpointAttributes: - as2MessageId - as2From - as2To - fileName - subject - fileSize - customProtocolHeaders For security reasons, only the headers with the prefix `x-apm-` are available in the `b2bMessageContext` variable. For example: ```json { "b2bMessageContext": { "sourceProtocol": "AS2", "transmissionId": "06bc20c8-475e-4a6f-b010-9b7933b2bfac", "sourceEndpointAttributes": { "as2MessageId": "<2023-04-12T19:37:42.273-46b95696-83f4-4e65-9222-61c40a854200@partnera_mythical-as2>", "as2From": "partnera", "as2To": "mythical-as2", "fileName": "EDI_850_20230401_1245678.edi", "subject": "EDI Message via Mule Generic Service", "fileSize": 3887 }, "customProtocolHeaders": { "x-apm-order-type": "drop-ship", "x-apm-tracking-id": "9d26d4ce-59ea-4448-8b51-ccc975d4efec" }, "messageId": "9bf446f8-4a02-475f-afa3-c8772a340154" } } ``` ## FTP and SFTP Source Endpoint Messages received via FTP or SFTP contain the following fields in the `b2bMessageContext` variable: - sourceProtocol - transmissionId - sourceEndpointAttributes: - fileName - filePath - fileSize - fileTimeStamp - partnerReferenceId This attribute is available only for Receive from Partner endpoints that have the partner reference ID configured. - messageId For example: ```json { "b2bMessageContext": { "sourceProtocol": "SFTP", "transmissionId": "3ef5654a-5cda-41b1-8909-59a28c8b1537", "sourceEndpointAttributes": { "fileName": "RandomMessageType_PO_20230331_1559_003.xml", "filePath": "/partners/pacific-corp/in-orders", "fileSize": 4889, "fileTimeStamp": "2023-04-05T15:16:29", "partnerReferenceId": "PACIFICCORP" }, "messageId": "cdaf6c12-bb3b-4978-9ac6-e8ace053f7c5" } } ``` ## HTTP and HTTPS Source Endpoint Messages received via HTTP or HTTPS contain the following fields in the `b2bMessageContext` variable: - sourceProtocol - transmissionId - sourceEndpointAttributes: - path - fileSize - customProtocolHeaders For security reasons, only the headers with the prefix `x-apm-` are available in the `b2bMessageContext` variable. - messageId For example: ```json { "b2bMessageContext": { "sourceProtocol": "HTTPS", "transmissionId": "a7a800ad-4117-40c1-98a0-79892c982fd4", "sourceEndpointAttributes": { "path": "/", "fileSize": 866 }, "customProtocolHeaders": { "x-apm-order-number": "ORD12345-A", "x-apm-order-type": "drop-ship" }, "messageId": "cdaf6c12-bb3b-4978-9ac6-e8ace053f7c5" } } ``` ## Use Case Implementation Examples The following examples show how to implement some common use cases for source message attributes. This example shows how to map the `messageId` and `fileName` attributes in the translated data payload within a message flow’s translation map: messageId: vars.b2bMessageContext.messageId fileName: vars.b2bMessageContext.sourceEndpointAttributes.fileName This example shows how to apply mapping logic based on the filename prefix message in the message flow’s translation map: POPurpose: substringBefore(vars.b2bMessageContext.sourceEndpointAttributes.fileName, "\_") default "PO-CREATE", This example shows how to perform a `substringBefore` operation on the source filename to get the value before `_` and use it as the partner reference identifier: %dw 2.0 output application/json import \* from dw::core::Strings ns ns0 http://xmlns.mulesoft.com/enterpriseobjects/b2b/ --- { partnerReferenceId: substringBefore(vars.b2bMessageContext.sourceEndpointAttributes.fileName, "\_") default "UNKNOWN" , hostReferenceId: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#Seller, businessDocumentKey: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#PurchaseOrderNumber, customAttributes: \[ { alias: "purchaseOrderNumber", values: \[payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#PurchaseOrderNumber\] }, { alias: "buyerEmail", values: \[payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#BuyerEmailID\] } \] } This example shows how to: - Use the partner identifier associated with an FTP or SFTP Receive from Partners endpoint configuration as the partner reference identifier for routing the message. - Map the source filename as a custom message attribute. %dw 2.0 output application/json ns ns0 http://xmlns.mulesoft.com/enterpriseobjects/b2b/ --- { partnerReferenceId: vars.b2bMessageContext.sourceEndpointAttributes.partnerReferenceId, hostReferenceId: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#Seller, businessDocumentKey: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#PurchaseOrderNumber, customAttributes: \[ { alias: "purchaseOrderNumber", values: \[payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#PurchaseOrderNumber\] }, { alias: "buyerEmail", values: \[payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#BuyerEmailID\] }, { alias: "sourceFileName", values: \[vars.b2bMessageContext.sourceEndpointAttributes.fileName default “UNKNOWN\] } \] } This example shows how to map a custom header on the received HTTP message as a custom message attribute: %dw 2.0 output application/json ns ns0 http://xmlns.mulesoft.com/enterpriseobjects/b2b/ --- { partnerReferenceId: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#Seller, hostReferenceId: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#Buyer, businessDocumentKey: payload.ns0#B2BMessage.ns0#Data.ns0#PurchaseOrder.ns0#PurchaseOrderNumber, customAttributes: \[ { alias: "purchaseOrderNumber", values: payload.ns0#B2BMessage.ns0#Data.\*ns0#PurchaseOrder map ( purchaseOrder , indexOfPurchaseOrder ) -> purchaseOrder.ns0#PurchaseOrderNumber default "UNKNOWN" }, { alias: "supplierName", values: \[vars.b2bMessageContext.customProtocolHeaders.'x-apm-supplierName' default "UNKNOWN"\] } \] } ## See Also - [Translation Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps) - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [Creating Reference Maps for Message Types](https://docs.mulesoft.com/partner-manager/latest/create-reference-map) - [Tracking Transmissions](https://docs.mulesoft.com/partner-manager/latest/activity-tracking) --- product: Partner Manager version: 2.x is-latest-version: true --- # Adding and Versioning Translation Maps > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Translation maps are used to transform messages between different formats. You can add maps to the Maps page and version them to apply changes across your deployed message flows. > [!NOTE] You can apply mapping changes across deployed message flows by setting new versions as > active without needing to upload the updated file to each message flow and redeploy. See > [Select the Map for a Partner Manager Message Flow](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps#change-map) for more > information. ## Add a Map To add a map: 1. From the Partner Manager sidebar, select **Maps**. 2. Click **New Map** and select **Send to partner** or **Receive from partner**. 3. Enter a unique name for the map and click **Save**. This adds the map to the **Maps** page without any configuration. 4. On the map details page, select the message types. For more information about message types, see [Create Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) or [Create Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow). 5. In the **Map** section, click **Import** and select the `.dwl` file to import. 6. Assign a unique version label and optionally add a note. 7. Enter a description by clicking the pencil icon next to the **Description** field. 8. Click **Save**. ## Add a New Map Version Adding a new version of a map is a quick way to apply map changes across your deployed message flows or runtime applications without needing to redeploy individual message flows. Up to 10 versions of a map can be stored per mapping configuration. To import a new version of a map: 1. From the Partner Manager sidebar, select **Maps**. If you don’t have the **Maps** tab, update your Partner Manager applications to the latest runtime templates from version 2.25.0 or later. 2. Click the name of the map to open the details page. 3. Click **Select** in the **Map** section. 4. Click **Import new file** in the **Select a Map File** window. 5. Navigate to the `.dwl` file you want to import and click **Open** to add the new version of the map. 6. To replace the currently active map, select the radio button next to the version that you just uploaded. 7. Click **Set as Active**. 8. Click **Confirm**. ## Delete a Map To delete a map: 1. From the Partner Manager sidebar, select **Maps**. 2. Click the name of the map to open the details page. 3. Click **Delete**. > [!NOTE] Only inactive versions of a map can be deleted. To avoid disruption to existing message > flows, the current active version can’t be deleted. ## View Message Flows for a Map To view the message flows that use a particular map, click the number in the **Message flows** column for the map. This opens a message flow details window that shows the message flow name and deployment status. ## See Also - [Creating Translation Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps) --- product: Partner Manager version: 2.x is-latest-version: true --- # Anypoint Partner Manager for B2B Integration > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Perform bidirectional Business-to-Business (B2B) message exchanges with your external business partner ecosystem. Anypoint Partner Manager supports multiple transport protocols, including AS2, HTTP, HTTPS, SFTP, and FTP, and handles various message formats such as CSV, EDIFACT, EDI X12, JSON, and XML. Partner Manager enables use cases such as order to cash, procure to pay, logistics planning, warehouse management, and transportation execution. ## Partner Manager Capabilities Use Partner Manager to: - Perform technical onboarding of your partners. - Set up, manage, and monitor business message flows between your systems and your partners' systems. - Track and report on business transactions to achieve greater operational efficiency in B2B transactions. - View meta information, validation errors, and all messages included with each transmission payload. Transmission payloads can contain one or more business messages. Watch the Partner Manager Product Spotlight video to see a quick overview of Partner Manager: ![](https://play.vidyard.com/Byix7eAHCZyWCnt7tkFNGo.jpg) ## Before You Begin Using Partner Manager Before you begin using Partner Manager, you must have: - An Anypoint Platform account with the Partner Manager entitlement. - AS2, EDIFACT, and X12 Connector entitlements, if your organization uses these standards and protocols. - One or more of the user permissions for Partner Manager. - The Partner Manager Administrator role, which can assign permission levels to all users who need access to B2B message flows in their sandbox or production environment. - The required Mule runtime capacity, either vCore or messages and flows, to manage your B2B transaction workload needs. - Storage for the B2B transmission payloads you send or receive, such as a database, Amazon S3, and Azure Blob Storage. - Familiarity with EDI message formats. - Anypoint Studio 7.4 or later. - The ability to create DataWeave maps to use for performing data transformations. ## Partner Manager Concepts To use Partner Manager, you must understand the following concepts: ### Host Your Anypoint Platform organization or business group. A Partner Manager implementation has a single host for which you define a host profile. ### Partners The partners with whom you send and receive B2B transmissions. You define a partner profile for each partner in your B2B ecosystem. ### Payload Storage API An API that provides Partner Manager with a standardized way to connect to your solution for storing transmission content. ### Message Flows The paths along which a B2B message travels from its source, through a DataWeave translation map, to its target. There are two types of message flows: - Inbound Message Flows Inbound message flows receive messages from partners, including messages that go through third-party connections. When you create an inbound message flow, you can validate and transform the inbound messages and then send them to your backend applications. - Outbound message flows Outbound message flows receive messages from your backend applications, validate and transform these messages into your partner’s expected format, and send them to your partners directly or through third-party connections. Message flows consist of [endpoints](#endpoints), [message types](#message-types), [sender and receiver identifiers](#identifiers), and [translation maps](#translation-maps). ### Endpoints Define the transport protocol configurations necessary for: - Receiving messages from external partners or internal backend applications - Sending messages to external partners or backend applications You can configure the following types of endpoints: - Receive from Partners Source endpoint in an inbound message flow that receives inbound B2B messages from partners either directly or via third-party connections - Target at Host Target endpoint in an inbound message flow through which transformed messages are sent to the backend applications - Source at Host Source endpoint in an outbound message flow that receives application messages from the backend applications - Send to Partners Target endpoint in an outbound message flow through which transformed B2B messages are sent to the partners either directly or via third-party connections ### Message Types Define the structure of the transactions that Partner Manager receives or sends. Partner Manager supports the following message types: - Receive from Partners Defines the structure of the transactions that partners or third-party connections send to the host through inbound message flows. You can define [custom message attributes](#custom-attributes) for this message type. - Target at Host Defines the structure of the transactions that the host sends to the backend through inbound message flows. - Source at Host Defines the structure of the transactions that the backend sends to the host through outbound message flows. You can define custom message attributes for this message type. You can define [custom message attributes](#custom-attributes) for this message type. - Send to Partners Defines the structure of the transactions that the host sends to partners or third-party connections through outbound message flows. ### Sender and Receiver Identifiers Identifiers in AS2, EDIFACT, and X12 transactions that identify the message senders and receivers. For X12 messages, the identifiers in the ISA and GS headers provide information that identifies the appropriate flow to process the transaction. For EDIFACT messages, the identifiers in the UNB segment provide information that identifies the appropriate flow to process the transaction. For other formats, such as CSV and JSON, Partner Manager extracts the identifiers from data payloads or a message contact by dynamically executing the reference mapping supplied with the message type definition. ### Custom Message Attributes User-defined attributes associated with Receive from Partners or Source at Host message types through reference mapping. Messages extract key data fields, like Order Number, Invoice Number, and Shipment ID, as business transactions are processed. After a transaction processes, users can find the message attribute label and value by searching transactions on the Activity page in Partner Manager or via API calls. ### Translation Maps DataWeave maps transform business transactions between your partner’s message formats and your organization’s enterprise application message formats. You create the maps in Studio and import them into Partner Manager when you configure message flows. ### Templates Prebuilt templates that convert your B2B message flow configurations into runtime applications. When MuleSoft upgrades a template, you can upgrade your message flows to use them to take advantage of new capabilities that enable better integration with your partner’s ecosystem. ## Next Step Continue to [Getting Started with Partner Manager](https://docs.mulesoft.com/partner-manager/latest/get-started). ## See Also - [Partner Manager Architecture](https://docs.mulesoft.com/partner-manager/latest/partner-manager-architecture) - [Anypoint Partner Manager Setup](https://docs.mulesoft.com/partner-manager/latest/setup) --- product: Partner Manager version: 2.x is-latest-version: true keywords: release notes --- # Anypoint Partner Manager Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt These release notes are provided for Anypoint Partner Manager: - [Anypoint Partner Manager Release Notes](https://docs.mulesoft.com/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes) ## See Also - [Anypoint Partner Manager for B2B Integration](https://docs.mulesoft.com/partner-manager/latest/) - [Known Issues](https://help.salesforce.com/s/issues) --- product: Partner Manager version: 2.x is-latest-version: true --- # Apply Environment Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can apply changes to your environment’s Partner Manager or Access Management settings, like Mule runtime version or vCore and ActiveMQ configurations, to all your runtime applications at once. Follow these steps to apply the changes: 1. From the Message flows page, click **Manage deployments**. 2. Select **Apply runtime settings**. 3. Check the box to confirm that you understand the effects of these actions. 4. Click **Confirm**. Applying environment settings updates all the Mule applications in your runtime with the latest available template versions. --- product: Partner Manager version: 2.x is-latest-version: true --- # AS2 Receive Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt AS2 receive endpoint settings determine where to receive B2B messages received over AS2. An AS2 Receive from Partners endpoint (the only type of AS2 receive endpoint) acts as the source endpoint in an inbound message flow that receives B2B messages from partners either directly or via third-party connections. One AS2 endpoint can receive data from multiple partners, multiple third-party connections, or both. Only a host can own AS2 Receive from Partners endpoints. > [!IMPORTANT] Each AS2 receive endpoint configuration gets deployed as an individual Mule > application in the runtime. To minimize the number of vCores needed to run Anypoint Partner > Manager, use an existing AS2 receive endpoint configuration across multiple message flows. Create an AS2 Receive from Partners endpoint by configuring these settings on the **** page:
SettingDescriptionRequired

Owner

Host that owns the endpoint.

x

Usage

Endpoint function (Receive from partners).

x

Protocol

Protocol that the endpoint supports (AS2).

x

Endpoint name

Automatically generated name used to identify the endpoint, which you can modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

Private port (when deploying to VPC)

Applies when using Anypoint Virtual Private Cloud (Anypoint VPC) with CloudHub 1.0 deployments:

  • When enabled, the AS2 receive endpoint application deploys to the private port 8092 in your Anypoint VPC. You can manage the access control to the endpoint via the Anypoint VPC and dedicated load balancer settings.

  • When disabled, the AS2 receive endpoint application deploys to the public port 8082 by default.

    You can access the endpoint URL directly over the internet.

HTTPS

Applies to CloudHub 1.0 deployments.

Indicates whether Partner Manager deploys the AS2 receive endpoint as an HTTPS listener:

  • If enabled (default), Partner Manager deploys the AS2 receive endpoint as an HTTPS listener.

  • If disabled, Partner Manager deploys the AS2 receive endpoint as an HTTP listener.

The HTTPS option is disabled when creating Receive from Partners endpoints in CloudHub 2.0.

When deploying to Anypoint Runtime Fabric, Partner Manager always deploys the AS2 receive endpoint as an HTTP listener. With this type of deployment, you must configure an Ingress controller to provide external consumers with an HTTPS endpoint. For more information, see Configuring Ingress for Runtime Fabric.

When deploying to CloudHub 2.0, Partner Manager always deploys the AS2 Receive endpoint as an HTTPS listener.

  • When using a shared space as a deployment target, HTTP requests aren’t allowed.

  • If you want to allow HTTP requests to the AS2 receive endpoint application:

    1. Use a private space as the deployment target.

    2. On the Advanced tab, select Accept HTTP in the HTTP requests field.

    3. Optionally, configure Network-Level Ingress Rules to allow HTTP requests from specific IP addresses.

x

Manage with API Manager

Allows you to manage the endpoint in API Manager, where you can apply policies, such as authentication and client credentials, and configure SLA tiers. Document your message specifications by using Exchange and share them with your partners via public portals from Exchange or by obtaining an additional license and sharing the specifications in API Experience Hub.

To manage an endpoint in API Manager, create an HTTP API in API Manager in the same environment and organization as the endpoint.

When you create the API in API Manager:

  • Select HTTP API as the asset type.

  • Leave the defaults on the Endpoint configuration screen.

  • Copy the API instance ID and paste it into the API Auto discovery id field in the Partner Manager New endpoint: Receive from Partners window.

x

Use hyphen (-) as the secondary file name delimiter to determine non-EDI message type

Lets you use a hyphen as the secondary file name delimiter to determine the message type from the message’s file name.

No

AS2 URL

URL to the AS2 server (automatically generated).

x

Enforce security level

Indicates whether Partner Manager rejects incoming AS2 messages that aren’t signed, encrypted, or both. When Partner Manager rejects a message, it returns a negative Message Disposition Notification (MDN) to the sender.

Allowed values:

  • Signed & Encrypted

    (Default) Rejects incoming messages that aren’t both signed and encrypted.

  • Signed

    Rejects incoming messages that aren’t signed.

  • Encrypted

    Rejects incoming messages that aren’t encrypted.

  • None

    Accepts messages that aren’t signed or encrypted.

When deploying an AS2 endpoint to CloudHub using the HTTP protocol, you cannot change the default value (Signed & Encrypted).

x

App Name Substitution Type

Defines how the ingress URL template app-name is substituted for this AS2 endpoint to generate the Runtime Fabric public endpoint.

  • Select Default to use app-name as deployment-name.

  • Select Custom to provide a custom name for the app-name substitution.

  • Select BasePath to use the editable AS2 base path as the value for the app-name substitution.

No

<Host> keystore

Host keystore file that stores your organization’s public certificate and private key. Select an existing keystore file or create a new one.

To create a new keystore file:

  1. In the <host> Keystore field, click Select.

  2. Click New.

  3. Complete the fields on the New certficate for <host> window, as described in Managing AS2 Host Keystores.

  4. Click Create.

x

Follow these steps to add basic authentication for incoming AS2 messages from your partners: 1. Configure the endpoint with [Manage with API Manager](#manage-api-manager). 2. Configure a client credentials policy in API Manager and select **HTTP Basic Authentication Header** as the credentials origin. ![Configure client credentials policy in API Manager](/mulesoft/current/en-us/partner-manager/latest/_images/configure-client-credentials-policy.png) 3. Add documentation to the HTTP API from Exchange and engage with your partners by publishing it to the [public portal](https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal) from Exchange or via API Experience Hub. - If you publish via a portal, your partners must log in and request access. - If you follow the [API request process](https://docs.mulesoft.com/api-experience-hub/requesting-access-to-an-api-instance) on behalf of your partners, HTTP basic auth headers pass the client ID and client secret upon request. ## Next Step After you create an AS2 receive endpoint, you can deploy it, as described in [Deploying AS2, HTTP, and HTTPS Receive Endpoints](https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints). ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [AS2 Signature and Encryption Algorithms](https://docs.mulesoft.com/partner-manager/latest/as2-endpoints-algorithms) - [Managing Host Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # AS2 Send Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt AS2 send endpoint settings determine where to send B2B messages transmitted over AS2. An AS2 Send to Partners endpoint (the only type of AS2 send endpoint) can act as: - A target endpoint in an outbound message flow through which transformed B2B messages are sent to partners, either directly or via third-party connections - An acknowledgment endpoint in an inbound message flow Either a partner or a third-party connection can own AS2 send endpoints. Create AS2 endpoints by configuring these settings on the partner or third-party connection pages:
SettingDescriptionRequired

Owner

Partner or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Send to partners)

x

Protocol

Protocol that the endpoint supports (AS2)

x

Endpoint name

Automatically generated name used to identify the endpoint, which you can subsequently modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

<Host> AS2 identifier

Your organization’s AS2 identifier.

x

<Partner> AS2 identifier

Your partner’s AS2 identifier, which appears if the endpoint is used to send transactions directly to a partner without going through a third-party connection.

x

<VAN> AS2 identifier

Your VAN’s AS2 identifier, which appears if the endpoint is used to send transactions to a third-party connection.

x

Partner AS2 URL

Your partner’s or third-party connection’s AS2 URL to which outbound EDI transmissions are sent.

x

Certificate (TLS context)

(Applies when the Partner AS2 URL field starts with https) SSL certificate. Values are:

  • Use CA-signed certificates

    Uses a certificate that was issued and signed by a certificate authority (CA). With this option, you don’t need to upload an additional certificate.

  • Use a self-signed certificate

    Uses a certificate that was not issued or signed by a CA. With this option, you must either select an existing certificate or upload a new certificate in .pem format.

  • Allow insecure connection

    Allows an insecure connection that doesn’t perform certificate validation.

    Don’t use this option in production environments. Use it only during testing.

x

Transfer Mode

The transfer mode applied when sending AS2 transmissions. Values are:

  • Auto

    Selected by default.

  • Chunked Transfer Mode

    Always streaming.

  • Identity Transfer Mode

    Never streaming.

x

Connection timeout

Timeout for establishing a connection to the remote service. The default is 30 Seconds.

x

Retry interval

Frequency of reconnection attempts when unable to connect to the remote AS2 service. The default is 30 Seconds.

x

Maximum retry attempts

Maximum number of reconnection attempts to make. If you don’t want Partner Manager to retry after an initial connection failure, set this value to 0.

x

Respond to email address

Email address to use as the HTTP From header when sending.

x

Message subject

User-defined field for the MIME Subject header.

x

Filename pattern

Filename pattern required by your partner.

x

<Host> keystore

Host keystore file that stores your organization’s public certificate and private key. To create a new keystore when creating an endpoint:

  1. Click New.

  2. Complete the fields on the New keystore for <host> window.

  3. Click Upload Keystore.

For more information about host keystores, see Managing AS2 Host Keystores.

Encryption algorithm

Algorithm to use when encrypting the message to send.

x

Signature algorithm

Algorithm to use when setting the message-integrity check value.

x

Request receipt

Whether you want the partner to return a Message Disposition Notification (MDN) receipt.

x

MDN response

The AS2 messages sent from Partner Manager always request the receiver to send a Synchronous MDN receipt back. This value is always set to Sync.

x

MDN signature algorithm

Request for a partner to respond with a signed Message Disposition Notification (MDN) using this algorithm for calculating the Message Integrity Check (MIC).

x

## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Filename Patterns for Send Endpoints](https://docs.mulesoft.com/partner-manager/latest/file-name-pattern) - [AS2 Signature and Encryption Algorithms](https://docs.mulesoft.com/partner-manager/latest/as2-endpoints-algorithms) - [Managing Host Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # AS2 Signature and Encryption Algorithms > For the full documentation index, see: https://docs.mulesoft.com/llms.txt AS2 endpoints deployed from Partner Manager support the following signature and encryption algorithms: - Signature algorithms - `UNSIGNED (Default)` - `MD5` - `SHA1` - `SHA224` - `SHA256` - `SHA384` - `SHA512` - Encryption algorithms - `UNENCRYPTED (Default)` - `AES128_CBC` - `AES128_CCM` - `AES128_GCM` - `AES192_CBC` - `AES192_CCM` - `AES192_GCM` - `AES256_CBC` - `AES256_CCM` - `AES256_GCM` - `AES256_WRAP` - `CAST5` - `DES_EDE3` - `RC2` ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) --- product: Partner Manager version: 2.x is-latest-version: true --- # Cannot process B2B transactions successfully > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You discover that transactions are not being processed when you test the message flow or when your partner sends you B2B messages. ## Causes Any of the following can lead to this type of error: - Your payload storage is not set up correctly or is not functioning properly. If the payload storage is not functional, B2B messages are not processed. - The message flow configuration is not aligned with the message being received from the partner. Examples of incorrect message flow configuration include incorrect or missing identifiers, incorrect message types, and so forth. - The Mule servers that process your B2B integration workloads are not functioning properly. For example, your servers can be inactive, the apps might not be functioning correctly, and so forth. ## Solutions Perform some verifications with your payload storage or flow configurations. ### Verify Payload Storage Verify the appropriate configuration for the payload storage API. If the payload storage app is functioning, verify that the storage source (for example, the S3 bucket, Azure Blob store, or database) that you use as the storage solution is up and functioning. - Open Anypoint Runtime Manager to verify if the related payload storage app is active. - Try restarting the app. - Test your payload storage API configuration using a browser extension such as Postman on Google Chrome. ### Verify Flow Configurations Verify that your message flow configuration is compatible with that of your partner. 1. From within your Anypoint Partner Manager environment (either Sandbox or Production), select your profile. 2. Select **Message Flows**. 3. Search for your message flow by the partner name or the message type such as 850. 4. After you locate the message flow, click on the message flow card to open it up. 5. From the message flow configurator, verify that the following information is in accordance with your agreement with your partner: - The correct identifiers are associated with the partner. - The appropriate receive endpoint is configured in the flow. - The appropriate document type (such as X12, version - 4010, or message type - 850) is configured. - Verify that you have the appropriate acknowledgment configuration. - Verify that you have an appropriate DataWeave map in the transformation section. - Verify that you have configured an appropriate target, such as both the message type of the target and the associated endpoint configuration. 6. If all of these look good, then ensure that the last deployment for this flow was successful by viewing the latest deployment history next to the flow. 7. If you observe a Failed status, try to deploy the message flow to ensure all your configurations have persisted on the Mule apps. > [!NOTE] It can take up to five minutes for your changes to take effect on the runtime. ### Verify B2B Integration Apps Verify that your B2B integration apps are active. 1. From Anypoint Platform, select Anypoint Runtime Manager and **Applications**. 2. Verify that the B2B apps on Mule are active by looking for a status of `started`. The list of apps includes: - APIReplicationService - DocumentProcessingService - One or more inbound apps. The names of these apps are prefaced with inbound- - One or more outbound apps. The names of these apps are prefaced with outbound- - Possibly one or more acknowledgment apps. The names of these apps are prefaced with ack- For any of the B2B integration apps that do not have a started status: 1. From Anypoint Platform, select Anypoint Runtime Manager and **Applications**. 2. For each app that does not have started status, select its row in the table and select **Restart** from the drop-down menu in the upper right of the status area in the information panel. 3. If restarting the app does not help you recover the application, select its row in the table and select **Delete** from the drop-down menu in the upper right of the status area in the information panel and confirm the deletion. 4. Navigate back to the message flow related to the app you just deleted and deploy the message flow. Consider the following when performing a delete: - If you delete the `DocumentProcessingService` or the `APIReplicationService`, deploying any flow results in the redeployment of those apps. - If you delete any of the inbound, outbound, or ack apps, you must redeploy the specific flow corresponding to the deleted apps. If you can’t access the Support Portal, contact your Customer Success Manager or MuleSoft Account Management team for help. --- product: Partner Manager version: 2.x is-latest-version: true --- # Certificate and Keystore Storage > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Certificates and keystores in Anypoint Partner Manager are securely stored in the Anypoint Platform secrets manager, which uses secure vault technology to store and control access to private keys, passwords, certificates, and other secrets. For endpoints that use certificates or keystores, you can either select an available certificate or keystore that works with the endpoint type and protocol or upload a new one to Partner Manager. ## See Also - [Managing Host Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates) - [Managing AS2 Host Keystores](https://docs.mulesoft.com/partner-manager/latest/manage-as2-host-keystores) - [Managing Partner and Third-Party Connection Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring a Payload Storage API > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager enables you to configure your own storage solution (for example, a database, Amazon S3, or Azure Blob Storage) to store transmission content. To use your own storage solution, you must implement an API that provides Partner Manager with a standardized way to connect to your storage. > [!NOTE] If you want the payload to be available from the Partner Manager Activity page, the > payload storage API must be publicly accessible. If your payload storage API is accessible only > through your network, you must implement the API differently. See > [Payload view URL](#payload-view) for more information. ## Download and Deploy the Payload Storage API Before you create your first partner and message flow, you must configure your payload storage API within the host organization in Partner Manager: 1. Access and download the following APIs from Anypoint Exchange: - [Partner Manager Content Storage API](https://www.mulesoft.com/exchange/com.mulesoft.b2b/partner-manager-content-storage-api) RAML specification for the payload storage API, which includes the URI parameters and record ID (contentRecordId) that the API implementation’s HTTP response header must return - [Partner Manager Content Storage API - S3 Template](https://www.mulesoft.com/exchange/com.mulesoft.b2b/partner-manager-content-storage-service-s3) Sample template for creating the payload storage API using Amazon S3 2. [Implement the API](https://docs.mulesoft.com/general/api-led-develop) to connect with your choice of storage location; for example, a database, Amazon S3, or filesystem. 3. [Deploy the API](https://docs.mulesoft.com/runtime-manager/deployment-strategies) on a runtime that can access the storage solution. 4. Make a note of the API URL and configuration values: - Host, port, and path connection - Connection Idle and Response timeouts - Authentication types: - None - API Key - Basic - Client Credentials - OAuth Token - Certificate (`.PEM` format) and connection types You’ll need this information when you associate Anypoint Partner Manager with your payload storage API. Your payload storage API must be accessible over the internet via HTTPS. Ensure you implement the appropriate authentication mechanisms to enable access over HTTPS. ## Add the Payload Storage API to the Host Profile 1. In Anypoint Platform, open Anypoint Partner Manager. 2. From the sidebar, select your organization’s host page. 3. In the **Payload storage** section of the page, click **Edit** to add the path to your payload storage. 4. Enter the following values: - **Endpoint name**: The name of the payload storage API - **Description**: The optional description for your payload storage - **URL**: The path to your payload storage This URL does the following: - Stores payloads when transactions process in the runtime - Retrieves the payload when you click **View Payload** on the **Transaction Activity** page, unless a payload view URL is configured - **Payload view URL**: (Optional) A secondary payload storage API URL that you can use to view the payload on the **Activity** page if the payload storage API is restricted to your internal network. See the Partner Manager [API implementation](https://anypoint.mulesoft.com/exchange/com.mulesoft.muleesb.modules/apm-payload-storage-with-ext-ui-template/minor/1.0/) example in Exchange for more information. If the payload storage API _isn’t_ restricted to your internal network, leave this field blank so that you can view the payload by using the **View Payload** button. 5. Optionally, if you want to view (or allow your users to view) the raw payloads of the files you receive or send, select **Allow users to download payloads**. 6. Click **Save**. ## Change the Payload Storage API Configuration To change the payload storage API configuration: 1. In the **Payload storage** section of the **Host** page, click **Edit**. 2. Modify the field values that require changing. 3. Click **Save**. 4. To have the changes take effect, either redeploy an existing message flow or deploy a new message flow. ## See Also - [Configure and Manage a Host Profile](https://docs.mulesoft.com/partner-manager/latest/configure-host) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring and Managing a Host Profile > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Your Anypoint Platform organization or your business group is referred to as the _host_ in Anypoint Partner Manager. In Anypoint Platform, your host name is the same as your Anypoint Platform business group name. Use the **** page in Partner Manager to: - Add details about your organization, such as its name, website, logo, corporate address, and contacts. - [Add the EDI and AS2 identifiers](https://docs.mulesoft.com/partner-manager/latest/partner-manager-identifiers) used by your organization. - [Manage the host certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates) associated with your organization. - [Manage the AS2 host keystores](https://docs.mulesoft.com/partner-manager/latest/manage-as2-host-keystores) associated with your organization, if you plan to use AS2 endpoints. - [Create and manage source and target endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). - [Create and manage source and target message types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type). - [Configure a payload storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api) to provide Partner Manager with a standardized way to connect to your storage. - [Configure global settings for EDIFACT receive messages](https://docs.mulesoft.com/partner-manager/latest/configure-global-edifact-receive-settings). ## See Also - [Configuring and Managing Partners](https://docs.mulesoft.com/partner-manager/latest/configure-partner) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring and Managing Lookup Tables > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Lookup tables are centralized reference values that mappings use to translate data between systems in Partner Manager. They help you keep inbound and outbound transformations consistent and avoid repeating translation logic in each map. Use lookup tables when mappings depend on reusable code or ID translations across partners and systems. This approach simplifies updates, supports bidirectional translation scenarios, and scales as integrations grow. ## Lookup Table Types These lookup table types are available: - **Composite Key Lookup** Use composite key lookup when the result depends on one or more key columns together. This type uses AND logic, so all required key values must be provided for a match. Result: zero or one matching row. - **Cross-Reference Lookup** Use cross-reference lookup when a row can be identified by any one of one or more key columns. This type uses OR logic across key columns. Result: zero or one matching row. - **Generic Lookup (optional)** Enable generic lookup when you need flexible filtering by one or more columns and might need multiple matching rows. Result: zero, one, or many matching rows. ## View and Search Lookup Tables To access lookup tables, select **Lookup Tables** from the Partner Manager sidebar. You can search by name or description and filter by type. ## Lookup Table Limitations Lookup table limits by environment include: - Maximum lookup tables: 100 - Maximum columns per table: 10 - Maximum rows per table: 10,000 - Maximum lookup table name length: 50 characters - Maximum column name length: 30 characters - Maximum value length per cell: 200 characters > [!NOTE] Each lookup results in an Object Store v2 call. If you anticipate high transaction volume, > consider an Object Store v2 premium subscription. For details, see > [Object Store v2 Rate Limiting and Billing](https://docs.mulesoft.com/object-store/osv2-usage). ## Next Steps - To create lookup tables, see [Creating Lookup Tables](https://docs.mulesoft.com/partner-manager/latest/lookup-tables-create). - To use lookup tables in DataWeave mappings, see [Using Lookup Tables in DataWeave](https://docs.mulesoft.com/partner-manager/latest/lookup-tables-dataweave). --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring and Managing Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A message flow is the path along which a message travels from its source, through a DataWeave translation map, to its target. You set up message flows to send and receive messages between your systems and your partners. Anypoint 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 the configuration objects shown in the following diagram: ![A flowchart showing a message flow from the source endpoint to the target endpoint](/mulesoft/current/en-us/partner-manager/latest/_images/pm-message-flow.png) You can create message flows in one of the following contexts: - Inbound An inbound message flow receives messages from your partners, transforms them into your internal application message format, and sends the transformed messages to your backend systems. For more information, see [Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows). - Outbound An outbound message flow receives messages from your backend applications, transforms the messages to your partner’s message format, and sends the EDI messages to your partner. For more information, see [Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/outbound-message-flows). ## See Also - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring and Managing Partners > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the **Partners** page to create and manage partners. From this page, you can: - [Create a new partner](https://docs.mulesoft.com/partner-manager/latest/create-partner). - [Add the EDI and AS2 identifiers](https://docs.mulesoft.com/partner-manager/latest/partner-manager-identifiers) used by your partner. - [Manage the digital certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) associated with your partner. - [Create](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) and manage source and target endpoints owned by the partner. - Manage EDI validation settings for [X12 receive settings](https://docs.mulesoft.com/partner-manager/latest/x12-receive-read-settings), [EDIFACT receive settings](https://docs.mulesoft.com/partner-manager/latest/edifact-receive-read-settings), [X12 send settings](https://docs.mulesoft.com/partner-manager/latest/x12-send-settings), and [EDIFACT send settings](https://docs.mulesoft.com/partner-manager/latest/edifact-send-settings). - [Modify partner settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings). - [Delete a partner](https://docs.mulesoft.com/partner-manager/latest/partner-manager-delete-partner). ## See Also - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Troubleshooting Anypoint Partner Manager](https://docs.mulesoft.com/partner-manager/latest/troubleshooting) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring and Managing Third-Party Connections > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If your partners use third-party service providers such as VANs or 3PLs (third-party logistics providers) who manage the B2B connectivity with your organization on behalf of your partners, you can create a third-party connection to manage configurations such as the endpoints, identifiers, and certificates of the third-party provider. Use the **Partners** page to create and manage third-party connections. From this page, you can: - [Create a new third-party connection](https://docs.mulesoft.com/partner-manager/latest/create-third-party). - [Add the EDI and AS2 identifiers](https://docs.mulesoft.com/partner-manager/latest/partner-manager-identifiers) used by the third-party connection. - [Manage the digital certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) associated with the third-party connection. - [Create](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) and manage source and target endpoints owned by the third-party connection. - [Modify third-party connection settings](https://docs.mulesoft.com/partner-manager/latest/modify-third-party-settings). - [Delete a third-party connection](https://docs.mulesoft.com/partner-manager/latest/delete-third-party). After you create a third-party connection, you can select the endpoints and identifiers configured for that connection in message flows created for your partners. ## See Also - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [Troubleshooting Anypoint Partner Manager](https://docs.mulesoft.com/partner-manager/latest/troubleshooting) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring CloudHub 1.0 Deployment Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt To configure settings for deploying Anypoint Partner Manager to CloudHub 1.0, access the business unit and environment for which you want to deploy Partner Manager and then follow these steps: 1. From the access management **Configure a Partner Manager environment** window, enter the following general settings:
SettingDescriptionDefault

Deployment Target Type

Target type for your Partner Manager deployment. Select CloudHub 1.0.

CloudHub 1.0

Runtime Version

Mule runtime engine version to run Partner Manager applications.

4.6.0

If you select Mule runtime 4.9.0 LTS using Java 17, test your component versions and SFTP connections that rely on insecure ciphers to make sure they work as expected with Java 17.

Min Mule Version override

Minimum Mule runtime version required to deploy the runtime applications.

Configuring the Min Mule version enables you to apply a feature flagging mechanism for Partner Manager-deployed Mule runtime applications.

If you process cXML messages with <DOCTYPE> tags, you must set the minMuleVersion to 4.5.0 or higher. If you’re migrating from an earlier version, you must perform end-to-end regression testing on your existing workflows before changing the minMuleVersion.

None

If you select None, Partner Manager defaults to using 4.3.0 as the Min Mule version.

Payload compression

Select not to compress the payload, always compress the payload, or adaptively compress the payload only when Anypoint MQ fails because the payload size exceeds a certain threshold.

None (not compressed)

CloudHub Region

Region in CloudHub to which you want to deploy Partner Manager runtime applications. You can’t change the region if active message flows are deployed to the existing region. To change the region in this case, you must undeploy the message flows. You can redeploy the message flows after you change the region.

Retrieved from the business group’s Runtime Manager setting

Anypoint MQ Region

This value is automatically assigned based on the specified CloudHub region and you can’t change it.

Automatically restart app when not responding

Directs CloudHub to automatically restart your application when the monitoring system discovers an issue.

Selected

Einstein enabled

Enables Einstein features in Partner Manager, such as the message summarization feature for source and target payloads.

Not selected

2. Select **Applications** and enter the following application settings:
SettingDescriptionDefault

Each B2B endpoint

Reserved CPU space, CPU space limit, and memory capacity for each Partner Manager endpoint. Partner Manager deploys a generic Mule app to the runtime for each endpoint protocol and direction (receive or send) combination.

0.1 vCores

B2B API Replication Service

Reserved CPU space, CPU space limit, and memory capacity for the B2B API Replication Service.

0.2 vCores

B2B Document Processing Service

Reserved CPU space, CPU space limit, and memory capacity for the B2B Document Processing Service.

0.2 vCores

Deploy HTTP/AS2 apps to private port

Directs CloudHub to automatically deploy newly created AS2, HTTP, and HTTPS endpoints to a private port.

Selected

For help with sizing, contact your MuleSoft Account Team. 3. Click **Save**. ## See Also [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring CloudHub 2.0 Deployment Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt To configure settings for deploying Anypoint Partner Manager to CloudHub 2.0, access the business unit and environment for which you want to deploy Partner Manager and then follow these steps: 1. From the Access Management **Configure a Partner Manager environment** window, enter these general settings:
SettingDescriptionDefault

Deployment Target Type

Target type for your Partner Manager deployment. Select CloudHub 2.0.

None

Runtime Version

Mule runtime engine version to run Partner Manager applications.

4.6.0 LTS using Java 8

If you select Mule runtime 4.9.0 LTS using Java 17, test your component versions and SFTP connections that rely on insecure ciphers to make sure they work as expected with Java 17.

Min Mule Version override

Minimum Mule runtime version required to deploy the runtime applications.

Configuring the Min Mule version enables you to apply a feature flagging mechanism for Partner Manager-deployed Mule runtime applications.

If you process cXML messages with <DOCTYPE> tags, you must set the minMuleVersion to 4.5.0 or higher. If you’re migrating from an earlier version, you must perform end-to-end regression testing on your existing workflows before changing the minMuleVersion.

None (Uses 4.3.0)

If you select None, Partner Manager defaults to using 4.3.0 as the Min Mule version.

Payload compression

Select not to compress the payload, always compress the payload, or adaptively compress the payload only when Anypoint MQ fails because the payload size exceeds a certain threshold.

None (not compressed)

Deployment Target

Shared or private space to which you want to deploy Partner Manager runtime applications. You can change the deployment target after all active message flows are no longer deployed to an existing target. To change the region in these instances, undeploy the message flows, change the region, and then redeploy the message flows.

None

Einstein enabled

Enables Einstein features in Partner Manager, such as the message summarization feature for source and target payloads.

Not selected

2. Select **Applications** and enter these application settings:
SettingDescriptionDefault

Each B2B endpoint

Reserved CPU space, CPU space limit, and memory capacity for each Partner Manager endpoint application. Partner Manager deploys a generic Mule app to the runtime for each endpoint protocol and direction (receive or send) combination.

Partner manager deploys each AS2 and HTTPS inbound endpoint configuration as a separate Mule application. You can reuse the same endpoint configuration across multiple partners and message types.

0.1 vCores

B2B API Replication Service

Reserved CPU space, CPU space limit, and memory capacity for the B2B API Replication Service.

0.2 vCores

B2B Document Processing Service

Reserved CPU space, CPU space limit, and memory capacity for the B2B Document Processing Service.

0.2 vCores

For help with sizing, contact your MuleSoft Account Team. 3. Click **Save**. ## See Also [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Global EDIFACT Receive Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt When EDIFACT messages received from your partners do not contain a UNA segment, Partner Manager uses the delimiters specified in the **Global EDIFACT settings: Receive from partners** window to parse the received EDIFACT payloads. You define these settings in the host organization’s profile:
SettingDescriptionDefault Value

Data element separator

Data element separator character

+

Component separator

Component element separator character

:

Repetition separator

Repetition separator character

*

Segment terminator

Segment terminator character

'

Release character

Release character

?

## See Also [Configuring and Managing a Host Profile](https://docs.mulesoft.com/partner-manager/latest/configure-host) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Receive Settings for AS2 Inbound Messages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The AS2 encoding setting determines the character encoding type for all messages received from this partner. To configure the encoding type: 1. In the sidebar, select **Partners**. 2. Select the partner to which the setting applies. 3. In the **Global endpoint settings** section’s **Inbound endpoint settings** column, click **AS2**. 4. Select one of the following encoding types from the **Character encoding override** dropdown: - NONE - ASCII - ISO-8859-1 - ISO-8859-2 - ISO-8859-3 - ISO-8859-4 - ISO-8859-5 - ISO-8859-6 - ISO-8859-7 - ISO-8859-8 - ISO-8859-9 - UTF-8 5. Click **Save**. --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Receive Settings for Inbound EDIFACT Messages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Partner Manager receive settings include the EDIFACT acknowledgements and validation rules to apply when processing an inbound EDIFACT message from the specified partner. To configure EDIFACT receive settings: 1. In the sidebar, select **Partners**. 2. Select the partner to which these settings apply. 3. In the **Validation and acknowledgement settings** section’s **Receive from ** column, click **EDIFACT**. 4. Select a link to configure: - [Acknowledgment settings](#ack-settings) - [Validation settings](#validation-settings) - [Control Numbers](#control-numbers) 5. Click **Save**. > [!NOTE] Your changes can take up to five minutes take effect on the runtime. ## Acknowledgment Settings Optionally configure acknowledgment settings for each Inbound EDIFACT message flow by enabling the **Send CONTRL functional acknowledgement when messages fail to route to a message flow** setting. When there is a routing failure, this acknowledgment indicates that the message is rejected. If you enable one of these options, either select the partner endpoint to which to send the acknowledgments or create a new endpoint for this purpose. ## Validation Settings Select one or more of the following options to ensure that all EDIFACT messages received from the partner meet validation rules:
SettingDescriptionDefault

Enforce length limits

  • If selected, Partner Manager rejects a message with values that are too short or long.

  • If not selected, Partner Manager accepts the message.

Enabled

Enforce value repeats

  • If selected, Partner Manager rejects a message with values that are repeated too many or too few times.

  • If not selected, Partner Manager accepts the message.

Enabled

Enforce valid characters

  • If selected, Partner Manager rejects a message that contains invalid characters.

  • If not selected, the invalid characters are either ignored or replaced, and Partner Manager accepts the message.

Enabled

Allow unknown segments

  • If selected, Partner Manager ignores unknown segments.

  • If not selected, Partner Manager rejects a message that contains unknown segments.

Disabled

Enforce segment order

  • If selected, Partner Manager enables the segment to be reordered.

  • If not selected, Partner Manager rejects a message that contains segments that are out of order.

Enabled

Allow Unused segments

  • If selected, Partner Manager ignores unused segments.

  • If not selected, Partner Manager rejects a message that contains unused segments.

Enabled

Enforce segment repeats

  • If selected, Partner Manager rejects a message that contains segments that repeat too many times.

  • If not selected, Partner Manager accepts the message.

Enabled

Enforce code set validations

  • If selected, Partner Manager enforces EDIFACT code set validations, as defined in the EDIFACT schemas.

  • If not selected, Partner Manager accepts the message.

Disabled

If a message does not meet an enabled rule, Partner Manager rejects it. Partner Manager logs all errors and reports them in the CONTRL acknowledgments. ## Control Numbers Use these settings to apply validations related to your partner or to your use of control numbers within the EDIFACT message:
SettingDescriptionDefault

Require unique interchange control number

  • If selected, Partner Manager records the interchange numbers previously processed and rejects duplicate interchange numbers from the same partner, as determined by the interchange sender and receiver identification.

  • If not selected, Partner Manager enables processing of the received interchange to continue.

Disabled

Require unique message control number

If selected, Partner Manager enforces globally unique message control numbers (UNH01) for received transaction sets.

This configuration requires message control numbers to be unique across all EDIFACT messages received from the same partner and application, as determined by the interchange sender and receiver identification and application codes.

Disabled

## See Also - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Modify Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Receive Settings for Inbound X12 Messages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Partner Manager enables you to configure the X12 acknowledegments, validation rules, character encoding, and control numbers to apply when receiving inbound X12 messages from the selected partner. To configure X12 receive settings: 1. In the sidebar, select **Partners**. 2. Select the partner to associate with the settings. 3. In the **Validation and acknowledgement settings** section’s **Receive from ** column, click **X12**. 4. Select a link to configure: - [Acknowledgment settings](#ack-settings) - [Validation settings](#validation-settings) - [Control numbers](#control-numbers) - [Character set and separators](#character-set) 5. Click **Save**. > [!NOTE] It can take up to about five minutes for your configuration changes to sync with Mule. ## Acknowledgment Settings Use the following settings to configure the acknowledgments to send in response to inbound X12 messages:
SettingDescriptionDefault

Report non-fatal errors in acknowledgements

When checked, the AK3 segment of the generated 997 functional acknowledgment reports non-fatal errors.

When unchecked, the AK3 segment of the generated 997 functional acknowledgment doesn’t report non-fatal errors.

Enabled

Report segment details

If selected, the details of segment errors are included in the functional acknowledgements generated (997).

Enabled

Send TA1 for each transmission from <recipient>.

Provides a Technical Acknowledgment (TA1) to the Interchange sender that reports the status of the processing of an interchange header and trailer by the address receiver:

  • If the ISA and IEA of a received X12 message are valid, the host sends a positive TA1 ACK, regardless of the status of the other content.

  • If the ISA and IEA of a received X12 message are not valid, the host sends a TA1 ACK with an error code.

The TA1 ACK is sent inside an ISA or IEA envelope. The ISA and IEA are no different from any other interchange.

Disabled

Send 997 functional acknowledgment when messages fail to route to a message flow

Sends a functional acknowledgment (the receipt and syntactical acceptability of a message) when there is a failure to route the message to one of the message flows.

Disabled

### X12 997 Functional Acknowledgment The X12 997 functional acknowledgment reports the status of a received interchange. It reports all of the errors encountered while processing the received document. As with all X12 transaction sets, the 997 functional acknowledgment is sent inside a GS or GE envelope. The 997 functional acknowledgment does the following: - Acknowledges the receipt of an interchange or functional group - Accepts or rejects one or more functional groups or transactions - Verifies and reports compliance with the standard If an interchange contains multiple groups, a 997 acknowledgment is returned for each group. If a group contains multiple transaction sets, then the acknowledgment for that group contains one loop for each transaction set. This applies only if AK2 loops are generated for accepted transaction sets. ## Validation Settings Use these settings to ensure that all X12 messages received from a partner meet validation rules. Partner Manager logs all validation errors and reports them in the CONTRL acknowledgements.
SettingDescriptionDefault

Fail when value length outside allowed range

  • If selected, Partner Manager rejects transactions with data element values that are too long or too short against the definition in the EDI schema used.

  • If not selected, Partner Manager uses the values.

Enabled

Truncate values exceeding the length limits

If selected and Fail when value length outside allowed range isn’t selected, Partner Manager truncates the data elements that exceed the maximum length limit in the generated output.

Disabled

Fail when invalid character in value

  • If selected, Partner Manager rejects transactions with invalid characters.

  • If not selected, the characters are either passed through or substituted.

Enabled

Fail if value is repeated too many times

  • If selected, Partner Manager rejects transactions with values that are repeated too many or too few times.

  • If not selected, Partner Manager accepts the values.

Enabled

Fail if unknown segments are used

  • If selected, the Partner Manager rejects transactions that contain unknown segments.

  • If not selected, Partner Manager ignores unused segments.

Disabled

Fail when segments are out of order

  • If selected, Partner Manager rejects transactions that have out-of-order segments.

  • If not selected, the segments are reordered.

Enabled

Fail when too many repeats of segment

If selected, Partner Manager rejects transactions with segments repeated too many times.

Enabled

Fail when unused segments are included

  • If selected, Partner Manager rejects transactions containing segments marked as unused in the schema.

  • If not selected, Partner Manager ignores unused segments.

Disabled

Enforce conditional relationship validations

  • If selected, any missing conditional data elements cause the generation of the X12 transaction to fail.

  • If not selected, Partner Manager does not enforce relationship validations.

Disabled

Enforce code set validations

  • If selected, Partner Manager enforces X12 code set validations, as defined in the X12 schemas.

Disabled

Acknowledge every transaction

If selected, Partner Manager includes a separate AK2/AK5 segment for every received transaction set, even when all transactions are accepted in the 997 functional acknowledgment.

Disabled

Include trailer segment details

If selected, Partner Manager includes elements from the Interchange Trailer (IEA) and Group Trailer (GE) segments of the X12 data payload.

Disabled

Ignore included segments

If selected, the X12 read operation output includes segments with usage type 'Ignore', and you can use the segment s in message flow maps.

Disabled

### Control Numbers Use these settings to apply validations related to the use of control numbers within inbound X12 messages:
SettingDescriptionDefault

Requires unique interchange control number (ISA13)

If selected, the host records the interchange numbers previously processed and rejects duplicate interchange numbers from the same partner (as determined by the interchange sender and receiver identification).

Enabled

Requires unique group control number (GS06)

If selected, the host enforces globally unique Group Control Numbers (GS06) for received functional groups.

This configuration requires group numbers to be unique across all interchanges received from the same partner and application, as determined by the interchange sender and receiver identification, combined with the functional group sender and receiver application codes.

Disabled

Require unique transaction set control number (ST02)

If selected, the host enforces globally unique Transaction Set Control Numbers (ST02) for received transaction sets.

This configuration requires transaction set numbers to be unique across all functional groups received from the same partner and application, as determined by the interchange sender and receiver identification, combined with the functional group sender and receiver application codes.

Disabled

### Character Set and Encoding Use these settings to apply character set and encoding options for received X12 message:
SettingDescriptionDefault

Character set

Defines the characters allowed in string data. When set, invalid characters are replaced by the substitution character. If no substitution character is enabled for receive messages in the parser options, Partner Manager rejects the messages. Either way, the invalid characters are logged and are reported in the 997 functional acknowledgements for the receive messages.

EXTENDED

Character encoding

Indicates the character encoding for messages.

ISO8859_1

## See Also - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Modifying Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Runtime Fabric Deployment Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can deploy Partner Manager runtime applications to an [Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/) instance configured in your environment. ## Prerequisites for Deploying to Runtime Fabric Before you deploy Partner Manager to Runtime Fabric, you must: - Ensure that you have the required permissions for using Runtime Fabric. - Create and configure the Runtime Fabric instance into which to deploy Partner Manager services. See [Setting Up Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/setting-up-runtime-fabric). - If you already have an RTF instance, you can use it to deploy Partner Manager runtime applications. - Configure Persistence Gateway in Runtime Fabric, as described in [Persistence Gateway](https://docs.mulesoft.com/runtime-fabric/latest/persistence-gateway). Partner Manager uses a persistent Object Store via Persistence Gateway to store transaction processing information such as EDI control numbers and message routing information, which the Partner Manager runtime applications access. - Set up an ActiveMQ (JMS) messaging broker and configure the connection settings while configuring the Partner Manager Runtime Fabric deployment settings. Partner Manager uses ActiveMQ to reliably send payloads between different stages when it processes B2B transactions. The Partner Manager deployment service automatically creates the required message queues in your ActiveMQ instance when you deploy message flows. ## Configure Settings for Deploying to Runtime Fabric To configure settings for deploying Partner Manager to Runtime Fabric, access the business unit and environment for which you want to deploy Partner Manager and then follow these steps: 1. From the access management **Configure a Partner Manager environment** window, enter the following general settings:
SettingDescriptionDefault

Deployment Target Type

Target type for your Partner Manager deployment. Select Runtime Fabric.

CloudHub 1.0

Runtime Fabric

Name of the Runtime Fabric instance to use as your deployment target.

Runtime Version

Mule runtime engine version to run your Runtime Fabric instance.

4.6.0

If you select Mule runtime 4.9.0 LTS using Java 17, test your component versions and SFTP connections that rely on insecure ciphers to make sure they work as expected with Java 17.

Min Mule Version override

Minimum Mule runtime version required to deploy the runtime applications.

Configuring the Min Mule version enables you to apply a feature flagging mechanism for Partner Manager-deployed Mule runtime applications.

If you process cXML messages with <DOCTYPE> tags, you must set the minMuleVersion to 4.5.0 or higher. If you’re migrating from an earlier version, you must perform end-to-end regression testing on your existing workflows before changing the minMuleVersion.

None

If you select None, Partner Manager defaults to using 4.3.0 as the Min Mule version.

Host

The ingress template used for Partner Manager application deployments. For more information about ingress templates, see Ingress Templates.

On the Partner Manager host page, the URL column of the Endpoints section shows a placeholder URL for RTF Ingress endpoints. Partner Manager doesn’t have visibility into the RTF configuration.

Selected by Runtime Manager

Payload compression

Select not to compress the payload, always compress the payload, or adaptively compress the payload only when Anypoint MQ fails because the payload size exceeds a certain threshold.

None (not compressed)

Anypoint MQ Region

Region where Anypoint MQ is deployed.

When users replay transmissions when Partner Manager is deployed to Runtime Fabric, Partner Manager sends the associated transmission IDs to an Anypoint MQ queue. The document processing service app running in your Runtime Fabric instance reads the transmission IDs from Anypoint MQ to start reprocessing the transmission within your runtime applications. No transaction payload is processed via Anypoint MQ.

US East (N. Virginia)

Enforce deploying replicas across nodes

Whether Runtime Fabric enforces the deployment of Partner Manager application instances across different nodes.

Selected

Use persistent object store

Whether Partner Manager application instances must use a persistent object store. This value is always selected and you can’t modify it.

Selected

Einstein enabled

Enables Einstein features in Partner Manager, such as the message summarization feature for source and target payloads.

Not selected

2. Select **Applications** and enter the following application settings:
SettingDescriptionDefault

Application Name Prefix

Prefix appended to the Partner Manager application names. Maximum length is five characters.

Each B2B endpoint

Reserved CPU space, CPU space limit, and memory capacity for each Partner Manager endpoint. Partner Manager deploys a generic Mule app to the runtime for each endpoint protocol and direction (receive or send) combination. For help with sizing, contact your MuleSoft Account Team.

  • Reserved CPU: 0.08 vCPU

  • CPU Limit: 0.5 vCPU

  • Memory: 0.9 GB

B2B API Replication Service

Reserved CPU space, CPU space limit, and memory capacity for the Partner Manager B2B API Replication Service.

  • Reserved CPU: 0.1 vCPU

  • CPU Limit: 0.5 vCPU

  • Memory: 1 GB

B2B Document Processing Service

Reserved CPU space, CPU space limit, and memory capacity for the Partner Manager B2B Document Processing Service.

  • Reserved CPU: 0.1 vCPU

  • CPU Limit: 0.5 vCPU

  • Memory: 1.2 GB

3. Click **Save**. 4. Select **JMS Connection** and enter the JMS connection settings:
SettingDescriptionDefault

JMS Broker URL

URL of the JMS broker.

Username

Username used to connect to the JMS broker.

Password

Password used to connect to the JMS broker.

5. Click **Save**. ## See Also [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Send Settings for Outbound EDIFACT Messages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Partner Manager enables you to configure the EDIFACT envelope parameters, validation rules, control numbers, character encoding, and separators to apply when sending an outbound EDIFACT transmission from the host to a partner. To configure a partner’s EDIFACT send settings: 1. In the sidebar, select **Partners**. 2. Select the partner for whom to configure the send settings. 3. In the **Validation and acknowledgement settings** section’s **Send to ** column, click **EDIFACT**. 4. Select the setting to configure: - [General settings](#general-settings) - [Global control numbers](#global-control-numbers) - [Character set & delimiters](#character-set) 5. Click **Save**. The values in the partner’s settings page are used by default for all EDIFACT messages sent to that partner. You can override the settings you configure at the message flow level by selecting the custom option while creating an outbound message flow. > [!NOTE] Your changes can take up to five minutes to take effect on the runtime. ## General Settings Use the following settings to configure the general validation rules for outbound EDIFACT messages:
SettingDescriptionDefault Value

Send Syntax Version

Syntax version for outbound messages

VERSION4

Send UNA

If enabled, adds a UNA segment at the beginning of the generated EDIFACT payload

Enabled

Enforce valid characters

Enforces valid characters

Enabled

Enforce length limits

Validates data elements against length limits defined in the EDI schema used

Enabled

Expect CONTRL for each transmission sent to <partner>

When enabled, sets UNB-09 to 1, indicating that a technical acknowledgment is expected in the partner’s response

Disabled

Enforce code set validations

If selected, Partner Manager enforces EDIFACT code set validations, as defined in the EDIFACT schemas.

Disabled

## Global Control Numbers Partner Manager applies a global control number at the partner level on the EDIFACT interchanges generated from outbound message flows. These control numbers are sequenced across all message types sent to a partner, including functional acknowledgments. The control number starts with a default value of `1` and increases sequentially each time your organization sends outbound transmissions. To change the initial value to maintain sequencing and avoid duplication: 1. Click **Change** and enter the desired initial control number, up to 14 characters. 2. Click **Save**. \[NOTE\] Your changes can take up to five minutes to take effect on the runtime. ## Character Set and Delimiters Use the following settings to set the character encoding and separators for the generated EDIFACT payload:
SettingDescriptionDefault

Character encoding

Character encoding used for messages.

ASCII_B

Data element separator

Character used to separate data elements (can be a hex code).

+

Component separator

Character used to separate components (can be a hex code).

:

Repetition separator

Repetition separator character (can be a hex code).

*

Segment terminator

Segment terminator character (can be a hex code).

'

Release character

Character that acts as an escape for characters used as separators.

?

Segment line ending

Character to use for line endings between segments to improve the readability of the output message text. Possible values include:

  • NONE

    Generates the EDIFACT payload as a single line with segments separated by this character

  • CR

    Carriage return

  • CRLF

    Carriage return and line feed

  • LF

    Line Feed

CRLF

Test Indicator

Indicates if the EDIFACT transaction set is for testing or production.

No

Use segment line ending in last Line

If Yes, Partner Manager applies the segment line ending character to the last segment in the payload.

No

## See Also - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Modify Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Configuring Send Settings for Outbound X12 Messages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Partner Manager enables you to configure the X12 envelope parameters, delimiters, validation rules, character encoding, and control numbers to apply when sending an outbound X12 transmission to a partner. To configure a partner’s X12 send settings: 1. In the sidebar, select **Partners**. 2. Select the partner for whom you want to configure the settings. 3. In the **Validation and acknowledgement settings** section’s **Send to ** column, click **X12**. 4. In the menu, select the setting to configure: - [General settings](#general-settings) - [Authorization settings](#authorization-settings) - [TA1 Acknowledgment settings](#ta1-ack-settings) - [Global control numbers](#global-control-numbers) - [Character set & separators](#character-set) 5. Click **Save**. The values you configure in the partner’s settings page are used by default for all X12 messages going to that partner. You can override the settings you configure at the partner level except for TA1 and control numbers. You can override the message-flow-level settings by selecting the **Custom** option while creating an outbound message flow. > [!NOTE] Your changes can take up to five minutes to take effect on the runtime. ## General Settings Use the following settings to configure the transaction usage, specify the responsible standards agency, and enforce length limits and conditional relationship validations:
SettingDescriptionDefault Value

Usage indicator (ISA15)

Indicates if the X12 transaction sent is for testing, production, or information only.

Possible values include:

  • I - Information

  • T - Test

  • P - Production

  • P - Production
    For production environments

  • T - Test
    For sandbox environments

Responsible agency code (GS07)

Define the standards agency responsible for the standard in the GS segment.

Possible values include:

  • T - Transportation Data Coordinating Committee (TDCC)

  • X - Accredited Standards Committee X12

X

Enforce length limits

If selected, any data elements with a length outside of the definition in the X12 schema cause the generation of the X12 transaction to fail.

Enabled

Enforce conditional relationship validations

If selected, any missing conditional data elements cause the generation of the X12 transaction to fail.

Enabled

Enforce code set validations

If selected, Partner Manager enforces X12 code set validations, as defined in the X12 schemas.

Disabled

## Authorization Settings Use the following settings to configure the authorization and security qualifier for the transactions:
SettingDescriptionDefault

Authorization qualifier (ISA01)

None

Security qualifier (ISA03)

None

## TA1 Acknowledgment Settings Use the following settings to configure whether a technical acknowledgment is required, and the receive endpoint for the acknowledgment:
SettingDescriptionDefault

Expect TA1 for each transmission sent to <partner>

If selected, sets the value in ISA14 to 1 on the generated X12 payload, indicating that a technical acknowledgment (TA1) is required.

Disabled

Endpoint

When the option to expect a TA1 is selected, click Select to specify the Receive from <partner> endpoint. Partner Manager will receive the TA1 as an inbound transmission.

None

## Global Control Numbers Partner Manager applies a global control number at the partner level on the X12 interchanges and functional groups generated from outbound message flows. These control numbers are sequenced across all message types (including functional acknowledgments) that are sent to a partner. The control number starts with a default value of `1`, and is sequentially increased as your organization begins sending outbound transmissions. To set the control number sequence value to a different number to maintain sequencing and avoid duplication: 1. Click **Change** and enter the desired control number. 2. Click **Save**. > [!NOTE] Your changes can take up to five minutes to take effect on the runtime. ## Character Set & Separators Use the following settings to set the character encoding and delimiters for the generated X12 payload:
SettingDescriptionDefault Value

Character set

Set of characters allowed in string data.

EXTENDED

Character encoding

Character encoding for messages.

UTF8

Segment terminator

Segment terminator character.

~

Data element separator

Data element separator character (can be a hex code).

*

Component element separator (ISA16)

Component element separator character (can be a hex code).

>

Line ending between segments

Character to use for line endings between segments to improve the readability of the output message text. Possible values include:

  • NONE

    Generates the EDIFACT payload as a single line with segments separated by this character

  • CR

    Carriage return

  • CRLF

    Carriage return and line feed

  • LF

    Line Feed

CRLF

Use segment line ending in last line

If Yes, Partner Manager applies the segment line ending character to the last segment in the payload.

No

## See Also - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Modify Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can create new endpoints from the **Partners**, ****, or third-party page, or by using the Message Flow wizard. ## Create Endpoints from the Partners Page Use the **Partners** page to create new send and receive endpoints owned by partners or third-party connections: 1. In the sidebar, select **Partners**. 2. Select the partner or third-party connection for which to create the endpoint. 3. In the **Endpoints** section, click **New**. 4. In the **New Endpoint** window **Usage** field, select **Receive from partners** or **Send to partners**. 5. In the **Protocol** field, select the protocol to use for the endpoint. 6. [Configure the endpoint](#configure-endpoint) according to the endpoint type and protocol. 7. Click **Save**. Ownership of endpoints is automatically assigned based on the partner or third-party connection from which you are creating the endpoint. Partner Manager environments support up to 2,000 endpoints. To maximize your environment’s capacity, reuse endpoint configurations across partners and message flows. ## Create Endpoints from the Host Page Use the **** page to create new send and receive endpoints owned by the host: 1. In the sidebar, select the host. 2. In the **Endpoints** section, click **New**. 3. In the **New Endpoint** window **Usage** field, select the endpoint type. 4. In the **Protocol** field, select the protocol to use for the endpoint. 5. [Configure the endpoint](#configure-endpoint) according to the endpoint type and protocol. 6. Click **Save**. ## Create Endpoints Using the Message Flow Wizard You can use the Message Flow Wizard to create send and receive endpoints owned by hosts, partners, or third-party connections. For information about using the Message Flow wizard to create new endpoints, see [Create Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) and [Create Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow). ## Protocol-Specific Endpoint Settings The values for the endpoint’s settings vary according to the endpoint type and protocol: - [AS2 Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-receive) - [AS2 Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-send) - [FTP Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-ftp-receive) - [FTP Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-ftp-send) - [HTTP and HTTPS Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-receive) - [HTTP and HTTPS Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-send) - [SFTP Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-receive-target) - [SFTP Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-send) ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Deploying Receive Endpoints](https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints) - [Modifying Endpoints](https://docs.mulesoft.com/partner-manager/latest/modify-endpoints) - [Deleting Endpoints](https://docs.mulesoft.com/partner-manager/latest/delete-endpoints) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Inbound Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create inbound message flows to receive messages from partners, including messages that go through third-party connections. When you create an inbound message flow, you can validate and transform the inbound messages and then send them to your backend applications. Anypoint Partner Manager routes inbound messages based on matching identifiers configured for the partner. Before you create your first message flow, configure your [payload storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api). To create an inbound message flow: 1. From the Partner Manager sidebar, select **Message Flows**. 2. Click **New message flow > Receive from partner**. 3. Either select an existing partner from the list or select **New** to create a new partner, as described in [Create a Partner](https://docs.mulesoft.com/partner-manager/latest/create-partner). 4. Configure the receiving endpoint. 5. Configure the source message type. 6. Select the translation map. 7. Configure the target message type. 8. Configure the target endpoint. 9. Verify that the message flow is complete. ## Configure the Receiving Endpoint The receiving endpoint (Receive from Partners endpoint) in an inbound message flow receives the messages that your partners send, either directly or via third-party connections. To configure a receiving endpoint, you can either select an existing endpoint owned by the host, partner, or third-party connection, or you can create a new endpoint. Partner Manager supports the AS2, FTP, HTTP, HTTPS, and SFTP formats for the receiving endpoint in an inbound message flow. To configure the receiving endpoint: 1. In the message flow, expand the **Receiving endpoint** section and click **Select**. 2. In the **Select an endpoint: Receive from ** window, do either of the following: - Select an existing Receive from Partners endpoint and click **Select**. - Click **New** to create a new Receive from Partners endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). If you select an endpoint owned by a third-party connection, the messages go through that connection. After you select an endpoint, it is added to the message flow. If the protocol of the receiving endpoint is AS2, perform these additional steps: 1. Select the AS2 sender from the dropdown menu and then select either of the following: - The partner’s name, to enable your organization to receive the AS2 messages directly from the partner for whom the message flow is created - The name of a third-party connection, to enable your organization to receive the partner’s AS2 messages via a third-party connection, such as a VAN or 3PL The AS2 identifier and certificate of the selected third-party connection are used for validating the AS2 messages. 2. If there is no valid certificate in the associated profile, import one from the partner or from the third-party connection sending the AS2 message. ## Configure the Source Message Type The source message type (Receive from Partners message type) in an inbound message flow defines the structure of the messages that Partner Manager receives from a partner or third-party connection. Partner Manager supports the CSV, EDIFACT, JSON, X12, and XML formats for source message types in an inbound message flow. To configure the source message type: 1. In the message flow, expand the **Source message** section and click **Select**. 2. In the **Select message type** window, do either of the following: - Select an existing Receive from Partners message type and click **Select**. - Click **New** to create a new Receive from Partners message type, as described in [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type). The message type and its validation settings are added to the message flow. If the source message type is X12 or EDIFACT and your partner expects your organization to return functional acknowledgments, perform these additional steps: 1. In the **Acknowledgement** section, select the checkbox next to **Send 997 functional acknowledgement (X12)** or **Send CONTRL functional acknowledgement (EDIFACT)**. 2. Click **Select**. 3. In the **Select an endpoint: Send acknowledgement to ** window, do either of the following: - Select the endpoint to receive the acknowledgment messages from your partner and click **Select**. - Click **New** to create a new endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). The acknowledgment is added to the message flow. If the source message type is: - X12, select the partner and host organization’s ISA (Interchange) identifiers from the dropdown menu. - EDIFACT, select the partner and host organization’s UNA (Interchange) identifiers from the dropdown menu. - CSV, JSON, or XML, select the partner and host organization’s reference identifiers from the dropdown menu. To route inbound messages from partners matching any of the partner or host identifiers, select **All identifiers** from the dropdown menu. For more information about the order of precedence in inbound message routing, see [Inbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/inbound-message-routing). ## Select the Translation Map A translation map in an inbound message flow transforms your inbound message format to your organization’s enterprise application format. Maps are created using DataWeave and are imported to the [Maps](https://docs.mulesoft.com/partner-manager/latest/maps) page. For more information about creating maps, see [Translation Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps). To select the map: 1. In the message flow, expand the **Map** section. 2. Click **Select** and select the map from the table. The map is added to the message flow. Only the mapping configurations that match your source and target message types are shown. Choosing a map configuration with a different source and target message type updates the corresponding message type in your message flow. In the map for an inbound message flow, you can access source message attributes, which makes them available in the message payload. The attributes that you can access depend on the protocol of the source endpoint. For more information, see [Accessing Source Message Attributes](https://docs.mulesoft.com/partner-manager/latest/access-source-message-attributes). ## Configure the Target Message Type The target message type (Target at Host message type) in an inbound message flow defines the structure of the messages that Partner Manager sends to the backend applications. Partner Manager supports the CSV, JSON, and XML formats for the target message type in an inbound message flow. To configure the target message type: 1. In the message flow, expand the **Target at ** section. 2. In the **Message Type** section, click **Select**. 3. In the **Select message type** window, do either of the following: - Select an existing Target at Host message type and click **Select**. - Click **New** to create a new Target at Host message type. 4. Click **Save**. ## Configure the Target Endpoint The target endpoint (Target at Host Endpoint) in an inbound message flow receives the transformed messages on the backend applications. Partner Manager supports the FTP, HTTP, HTTPS, and SFTP formats for the target endpoint in an inbound message flow. To configure the target endpoint: 1. In the message flow, expand the **Target at ** section. 2. In the **Target at ** section, expand the **Endpoint** section and click **Select**. 3. In the **Select an endpoint: Target to ** window, do either of the following: - Select an existing Target at Host endpoint and click **Select**. - Click **New** to create a new Target at Host endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). After you select an endpoint, it is added to the message flow. ## Verify That the Message Flow Is Complete Partner Manager dynamically validates the message flow configuration elements for completeness and displays a green checkmark if all of the message flow building blocks are complete. After you verify the message flow configuration, you can deploy and test the message flow. ## See Also - [Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows) - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows) - [Accessing Source Message Attributes](https://docs.mulesoft.com/partner-manager/latest/access-source-message-attributes) - [Inbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/inbound-message-routing) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Lookup Tables > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create lookup tables in Partner Manager to support value translation across systems. For an overview of lookup table types and benefits, see [Configuring and Managing Lookup Tables](https://docs.mulesoft.com/partner-manager/latest/lookup-tables-overview). > [!NOTE] Each lookup results in an Object Store v2 call. If you anticipate processing a high volume > of transactions that use lookup tables, consider an Object Store v2 premium subscription. This > subscription level removes the standard 10 TPS cap, making sure your message flows remain fast and > reliable during peak processing times. For more information about rate limiting, see > [Object Store v2 Rate Limiting and Billing](https://docs.mulesoft.com/object-store/osv2-usage). ## Create a Lookup Table To create a lookup table: 1. From the Partner Manager sidebar, select **Lookup Tables**. 2. Click **New Lookup Table** and select **Composite Key Lookup** or **Cross-Reference Lookup**. 3. Enter a unique name with no spaces and a maximum of 50 characters. Names can include **\_** and **\-** characters. 4. Optionally add a description. 5. Click **Next**. 6. Optionally enable generic lookup so that searches can use any combination of columns to find one or more matching rows. 7. Configure up to 10 columns. Give each column a unique name and use no more than 30 characters. For both table types, the **Mandatory** and **Key** options are selected by default for the first column and can’t be unselected. For cross-reference lookup tables, both options are also selected by default for the second column. 8. For each column, configure options as needed: - **Mandatory** - Column value is required when you add or import rows. - **Key** - Column can be used as a lookup input. 9. Click **Save**. > [!NOTE] Columns can’t be added or modified after the table has at least one row. > [!NOTE] If generic lookup is enabled, table limits are lower. A generic lookup table supports up > to 1,000 rows and 6 columns. ## Add Rows to a Lookup Table After creating a lookup table, you can add up to 10,000 rows. To add a row, click **Add Row** and enter up to 200 characters for the value in each column. New rows are added to the top of the lookup table. > [!NOTE] Duplicate values aren’t permitted in key columns. For DataWeave functions and examples, see [Using Lookup Tables in DataWeave](https://docs.mulesoft.com/partner-manager/latest/lookup-tables-dataweave). ## Import Data from a CSV File To import data from a CSV file: 1. Click **Import CSV** and select the file. 2. Append the data to the existing lookup table or replace the existing lookup table. If you replace the lookup table, the existing data is deleted and can’t be recovered. 3. Click **Import**. ## Export a Lookup Table To export a lookup table, click **Export CSV**. The lookup table is exported and can then be downloaded as a CSV file. ## Delete a Lookup Table To delete a lookup table: 1. Click **Delete**. 2. Indicate that you understand that this action can’t be undone and click **Delete**. --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can create new message types from the **** page or by using the Message Flow wizard. ## Create a Message Type from the Host Page To create a message type from the **** page: 1. In the sidebar, select ****. 2. From the **Message types** section, click **New**. 3. In the **Usage** drop-down list, select the message usage. 4. Add values to the remaining settings. For setting descriptions, see the topic that corresponds to the message type usage: - [Receive from Partners Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/message-type-receive-from-partners) - [Send to Partners Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/message-type-send-to-partners) - [Target at Host Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/message-type-target-at-host) - [Source at Host Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/message-type-source-at-host) After you create Receive from Partners and Source at Host message types, you can add up to five custom message attributes to them. For information, see [Using Custom Message Attributes with Message Types](https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes). ## Create a Message Type by Using the Message Flow Wizard To create a message type by using the Message Flow Wizard, see [Create Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) and [Create Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow). ## See Also - [Modifying Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/modify-message-type-settings) - [Deleting Message Types](https://docs.mulesoft.com/partner-manager/latest/delete-message-types) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Outbound Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create outbound message flows to receive messages from your backend applications, validate and transform these messages to the format your partners expect, and then send them to your partners either directly, or through third-party connections. Before you create your first message flow, configure your [payload storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api). To create an outbound message flow: 1. From the Anypoint Partner Manager sidebar, select **Message Flows**. 2. Click **New message flow > Send to partner**. 3. Either select an existing partner or select **New** to create a new partner, as described in [Create a Partner](https://docs.mulesoft.com/partner-manager/latest/create-partner). 4. Configure the receiving endpoint. 5. Configure the source message type. 6. Configure reference IDs for the partner and host. 7. Select the translation map. 8. Configure the target message type. 9. Configure the target endpoint. 10. Verify that the message flow is complete. ## Configure the Receiving Endpoint The receiving endpoint (Source at Host endpoint) in an outbound message flow receives application messages from the backend applications. Partner Manager supports the FTP, HTTP, HTTPS, and SFTP formats for the receiving endpoint. To configure the receiving endpoint: 1. In the message flow, expand the **Source at ** section and click **Select**. 2. In the **Select an endpoint: Source at ** window, do either of the following: - Select an existing Source at Host endpoint and click **Select**. - Click **New** to create a new Source at Host endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). ## Configure the Source Message Type The source message type (Source at Host message type) in an outbound message flow defines the structure of the messages that Partner Manager receives from the backend applications. Partner Manager translates these messages to a configured Send to Partners message type, and then sends them to your partners, either directly or through a third-party connection. Partner Manager supports the CSV, JSON, and XML source message types in outbound message flows. To create the source message type: 1. In the message flow, expand the **Source message type** section and click **Select**. 2. In the **Source message type** window, do either of the following: - Select an existing Source at Host message type and click **Select**. - Click **New** to create a new Source at Host message type, as described in [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type). ## Configure Reference IDs for the Partner and Host Partner Manager uses the partner reference ID and host reference ID to locate the appropriate message flow for routing outbound messages. For information about how this routing process works, see [Sender and Receiver Identifiers](https://docs.mulesoft.com/partner-manager/latest/partner-manager-identifiers) and [Outbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/outbound-message-routing). To configure a partner reference ID, either select **All available identifiers** or select a specific partner identifier. To configure a host reference ID, either select **Ignore** or select your organization’s internal reference ID (such as the business unit name) as it appears in the data element of the source JSON or XML message from your backend applications. ## Select the Translation Map A translation map in an outbound message flow transforms outbound messages from your organization’s enterprise application format to the format your partners expect. Maps are created using DataWeave and are imported to the [Maps](https://docs.mulesoft.com/partner-manager/latest/maps) page. For more information about creating maps, see [Translation Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps). To select the map: 1. In the message flow, expand the **Map** section. 2. Click **Select** and select the map from the table. The map is added to the message flow. Only the mapping configurations that match your source and target message types are shown. Choosing a map configuration with a different source and target message type updates the corresponding message type in your message flow. In the map for an outbound message flow, you can access source message attributes, which makes them available in the message payload. The attributes that you can access depend on the protocol of the source endpoint. For more information, see [Accessing Source Message Attributes](https://docs.mulesoft.com/partner-manager/latest/access-source-message-attributes). ## Configure the Target Message Type The target message type (Send to Partners message type) in an outbound message flow defines the structure of the messages that Partner Manager sends to the partner, either directly or via a third-party connection. Partner Manager supports the CSV, EDIFACT, JSON, X12, and XML formats for target message types. For the EDIFACT and X12 message types, configuring the target message type also involves the following: - Configuring acknowledgments (optional) - Creating custom EDIFACT settings (optional) - Selecting EDIFACT identifiers to use for routing the outbound messages To configure the target message type: 1. Expand the **Message type** section and click **Select**. 2. In the **Select message type** window, do either of the following: - Select an existing Send to Partners message type and click **Select**. - Click **New** to create a new Send to Partners message type, as described in [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type). 3. Click **Save**. The message type and its validation settings are added to the message flow. 4. Optionally configure acknowledgment settings for the outbound message. 5. Optionally apply custom validation settings delimiters and character encoding to the outbound message flow. 6. In the ** Identifiers** section, select the sender and receiver identifiers to use on either the X12 ISA and GS segments or the EDIFACT UNB segments. These identifiers are configured in the host and partner profiles. ### Configure Acknowledgment Settings To configure acknowledgment settings for the outbound messages that use the message flow: 1. In the **Acknowledgement** section, select **Expect functional acknowledgement** (X12) or **Expect CONTRL functional acknowledgement** (EDIFACT). 2. Do either of the following: - Select an existing endpoint at which to receive your partner’s acknowledgment transaction. - Click **New** to create a new endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). 3. In the **Mark overdue after** field, accept the default value of **24 Hours** or configure when to mark the outbound transaction as overdue for an acknowledgment, according to the SLAs you have with your partner. ### Optionally Apply Custom Validation Settings to EDIFACT and X12 Endpoints By default, Partner Manager uses the EDIFACT or X12 send settings configured for the partner or third-party connection for message validation, delimiters, and character encoding. To apply custom validation settings and delimiters to the outbound message flow, follow these steps: 1. In the **EDIFACT Settings** section, select either **Custom X12 settings** or **Custom EDIFACT settings** and provide custom configuration values. 2. In the ** Identifiers** section, select the sender and receiver identifiers to use on either the X12 ISA and GS segments or the EDIFACT UNB segments. These identifiers are configured in the host and partner profiles. ## Configure the Target Endpoint The Target endpoint (Send to Partners endpoint) is the target endpoint to which transformed messages are sent to partners, either directly or via third-party connections. Use a third-party-owned Send to Partners endpoint for partners that use a third-party connection. Partner Manager supports the EDIFACT and X12 protocols for Send to Partners endpoints. To configure the target endpoint: 1. In the message flow, expand the **Send to ** section and click **Select**. 2. Do either of the following: - Select an existing Send to Partners endpoint and click **Select**. You can select any previously configured Send to Partners endpoints owned by the host, the partner for whom the message flow is configured, or a third-party connection. - Click **New** to create a new Send to Partners endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). If you selected AS2 as the protocol and there is no certificate associated with the partner or third-party profile, import the certificate of the partner or third-party connection that owns the endpoint. ## Verify That the Message Flow Is Complete Partner Manager dynamically validates the message flow configuration elements as you complete them and displays a green checkmark next to each of the validated elements. After you verify the configurations, you are ready to deploy the message flow. ## See Also - [Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/outbound-message-flows) - [Outbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/outbound-message-routing) - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Partners > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create a new partner by using the **Partners** page to specify partner-specific information such as name, identifiers, endpoints, and validation rules. Before you create your first partner, [make sure that you have configured your payload storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api) and that you have the following information: - The partner’s name (usually the name of the company) - One or more partner identifiers (such as the AS2 ID, X12-ISA, X12 GS, and so on) To create a partner: 1. In Partner Manager, select **Partners** in the sidebar. 2. Click **Create partner > Partner**. 3. Enter the following information:
SettingDescription

Name

Text string that uniquely identifies your partner

Type

Identifier type

Qualifier

Value that appears if you selected X12-ISA or EDIFACT-UNB as the type

Identifier Value

Value that uniquely identifies your partner in the EDI stream

4. Click **Create partner**. Partner Manager environments support a maximum of 1,000 partners each. To onboard more partners, create an additional environment. ## Configure Additional Partner Settings Add the following settings for the new partner, either now or later on:
SettingsActionAdditional Information

Information about the partner, such as the partner’s address, website, and contact details.

Click Edit in the About section.

Additional identifiers to associate with the partner.

Click New in the Identifiers section.

Sender and Receiver Identifiers

Partner’s digital certificates, such as X.509 certificates.

Click New in the Certificates section.

Managing Partner and Third-Party Connection Certificates

Partner-specific endpoints to use for sending and receiving messages to and from your partner, including acknowledgment endpoints. If you plan to use host endpoints only, you don’t need to create partner-specific endpoints.

Click New in the Endpoints section.

Creating Endpoints

Acknowledgments, validations, and control numbers for each message format that the partner uses. For EDIFACT and X12, you can also configure character sets and separators (send formats only).

Click the links in the Validation and acknowledgement settings.

Character encoding override option for received AS2 messages.

Click AS2 in Global endpoint settings.

AS2 Receive Settings

## Next Step After you create a partner and configure partner-level endpoints (if needed), you can set up message flows. ## See Also - [Configuring and Managing Message Flows](https://docs.mulesoft.com/partner-manager/latest/message-flows) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Modifying Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings) - [Deleting Partners](https://docs.mulesoft.com/partner-manager/latest/partner-manager-delete-partner) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Reference Maps for Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt When you create a new Source at Host or Receive from Partners message type with a CSV, JSON, or XML format, you must associate the message type with a DataWeave reference map. This is optional for Receive from Partners message types with an EDFIACT or X12 format. Reference maps can include custom message attributes that are extracted from the message payloads at runtime. The extracted attributes are visible in the payload and are available for searching and tracking. If the definition for the message type includes an uploaded schema, the input of the reference map is the payload that follows the schema. The output of the reference map contains the following fields:

Field

Description

Required or Optional

partnerReferenceId

Identifier that uniquely identifies the partner

Required for:

  • All Source at Host message types

  • Receive from Partners message types with a CSV. JSON, or XML format

You can hardcode this value as a static value, depending on your data processing and routing needs.

hostReferenceId

Identifier that uniquely identifies the host

  • Required for:

    • Receive from Partners message types with a CSV, JSON, or XML format

  • Optional for:

    • Receive from Partners message types formatted with an EDIFACT or X12 format

    • All Source at Host message types

You can hardcode this value as a static value, depending on your data processing and routing needs.

The JSON schema allows hostReferenceId to be null because it’s shared across message types. For Receive from Partners message types that use JSON, CSV, or XML, hostReferenceId is still required.

businessDocumentKey.

Key reference value, such as Order Number or Invoice number

Optional

customAttributes

Array of custom message attributes to extract from the payload. You can specify up to 100 custom message attributes in a given environment and can make up to 25 of them searchable.

When specifying a custom message attribute, configure the following fields in the reference map:

  • alias

    Alias that uniquely identifies a pre-configured custom message attribute configuration. The aliases in the reference map must match the message type’s attribute definitions. If the map contains aliases that don’t exist, creating or updating the message type fails.

  • values

    An array of values, such as order numbers or invoice numbers.

    Use an array of strings, even if there is only one attribute to extract. Using an array enables support for transactions with one-to-many relationships, such as transactions in which one shipment notice includes multiple purchase order numbers.

Optional

The output of a reference map must conform to this validation schema: %dw 2.0 output application/json --- { "definitions": {}, "$schema": "http://json-schema.org/draft-07/schema#", "title": "Root", "type": "object", "properties": { "partnerReferenceId": { "type": "string", "default": "", "pattern": "^.\*$" }, "hostReferenceId": { "type": \["string", "null"\], "default": "", "pattern": "^.\*$" }, "businessDocumentKey": { "type": \["string", "null"\], "default": "", "pattern": "^.\*$" }, "customAttributes": { "type": "array", "default": \[\], "items":{ "type": "object", "required": \[ "alias", "values" \], "properties": { "alias": { "type": "string", "default": "", "pattern": "^.\*$" }, "values": { "type": "array", "default": \[\], "items":{ "type": "string", "default": "", "pattern": "^.\*$" } } } } } } } If the output of a reference map does not conform to the validation schema, the custom message attributes won’t appear in the Partner Manager GUI. To ensure that the output of a reference map conforms to the validation schema, you can add an Anypoint Connector for X12 EDI (X12 Connector) **Validate schema** operation to your MuleSoft app, as shown in these Exchange examples: - [B2B/EDI: Order to Cash - Mapping Examples](https://anypoint.mulesoft.com/exchange/com.mulesoft.muleesb.modules/b2b-order-to-cash-mapping/) - [B2B/EDI: Procure to Pay Mapping Examples](https://www.mulesoft.com/exchange/com.mulesoft.muleesb.modules/b2b-procure-to-pay-mappings/) When you create a reference map, you can access other source message attributes in those maps. For information, see [Accessing Source Message Attributes](https://docs.mulesoft.com/partner-manager/latest/access-source-message-attributes). ## Example Map for a Receive from Partners Message Type The following map transforms a partner’s inbound X12 payload. The map contains a business document key and two custom message attributes: - The value of the business document key is `payload.TransactionSets.v004010."855".Heading."020_BAK".BAK03[0]`. - The value of the `purchaseOrderNumber` custom message attribute is `payload.TransactionSets.v004010."855".Heading."020_BAK".BAK03[0]`. - The value of the `vendorSalesOrderNumber` custom message attribute is `payload.TransactionSets.v004010."855".Heading."020_BAK".BAK08[0]`. The input to the map looks like this: %dw 2.0 output application/json { businessDocumentKey: payload.TransactionSets.v004010."855".Heading."020\_BAK".BAK03\[0\] default "", customAttributes: \[ { alias: "purchaseOrderNumber", values: \[payload.TransactionSets.v004010."855".Heading."020\_BAK".BAK03\[0\]\] }, { alias: "vendorSalesOrderNumber", values: \[payload.TransactionSets.v004010."855".Heading."020\_BAK".BAK08\[0\]\] } \] } The generated output of the map looks like this: { "businessDocumentKey": "ORDER-70010", "customAttributes": \[ { "alias": "purchaseOrderNumber", "values": \[ "ORDER-70010" \] }, { "alias": "vendorSalesOrderNumber", "values": \[ "SO-5100803142" \] } \] } ## Example Map for a Source at Host Message Type The following map transforms the outbound JSON or XML payload from the backend. The map contains the partner reference ID, host reference Id, business document key, and three custom attributes: - The value of the partner reference ID is `payload.Header.CustomerName`. - The value of the host reference ID is `payload.Invoice.Header.LineOfBusiness`. - The value of the business document key is `payload.Invoice.Header.InvoiceNumber`. - The value of the `invoiceNumber` custom attribute is `payload.Invoice.Header.InvoiceNumber`. - The value of the `purchaseOrderNumber` custom message attribute is `payload.Invoice.Header.PurchaseOrderNumber`. - The value of the `invoiceAmount` custom message attribute is `payload.Invoice.Header.TotalInvoiceAmt`. The input to the map looks like this: %dw 2.0 output application/json --- { partnerReferenceId: payload.Invoice.Header.CustomerName, hostReferenceId: payload.Invoice.Header.LineOfBusiness default "MYTHICAL", businessDocumentKey: payload.Invoice.Header.InvoiceNumber, customAttributes: \[ { alias: "invoiceNumber", values: \[payload.Invoice.Header.InvoiceNumber default "UNKNOWN"\] }, { alias: "purchaseOrderNumber", values: \[payload.Invoice.Header.PurchaseOrderNumber default "UNKNOWN"\] }, { alias: "invoiceAmount", values: \[ "\\$ " ++ payload.Invoice.Header.TotalInvoiceAmt default "UNKNOWN"\] } \] } The generated output of the map looks like this: { "partnerReferenceId": "ALPHA-CAN", "hostReferenceId": "Mythical-MG", "businessDocumentKey": "INV97750061", "customAttributes": \[ { "alias": "invoiceNumber", "values": \[ "INV97750061" \] }, { "alias": "purchaseOrderNumber", "values": \[ "ORD3893988" \] }, { "alias": "invoiceAmount", "values": \[ "$ 3756.24" \] } \] } ## Exchange Examples of DataWeave Maps For examples of DataWeave maps on Exchange that include custom message attributes, see: - [B2B/EDI: Order to Cash - Mapping Examples](https://anypoint.mulesoft.com/exchange/com.mulesoft.muleesb.modules/b2b-order-to-cash-mapping/) - [B2B/EDI: Procure to Pay Mapping Examples](https://www.mulesoft.com/exchange/com.mulesoft.muleesb.modules/b2b-procure-to-pay-mappings/) ## See Also - [Creating a Message Type](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type) - [Modifying Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/modify-message-type-settings) - [Using Custom Message Attributes with Message Types](https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Third-Party Connections > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create a new third-party connection by using the **Partners** page to specify the connection’s name, identifiers, connection-specific endpoints (if needed), and other settings. Before you create your first third-party connection, make sure that you have [configured your payload storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api) and that you obtain the following information: - The connection name (usually the name of the company) - One or more AS2 identifiers for the connection To create a third-party connection: 1. In Partner Manager, select **Partners** in the sidebar. 2. Click **Create partner > 3rd party connection**. 3. Enter the following information:
SettingDescription

Name

Text string that uniquely identifies the connection

Type

Identifier type

Identifier Value

Either a value that uniquely identifies the connection within the EDI stream or the AS2 identifier (if the connection uses AS2)

4. Click **Create 3rd party connection**. ## Configure Additional Connection Settings Add the following settings for the new third-party connection, either now or later on:
SettingsTo access this settingAdditional Information

Information about the connection, such as the address, website, and contact details for the third-party company.

Click Edit in the About section.

Additional identifiers to associate with the connection.

Click New in the Identifiers section.

Sender and Receiver Identifiers

The connection’s digital certificates, such as X.509 certificates.

Click New in the Certificates section.

Managing Partner and Third-Party Connection Certificates

The connection-specific endpoints to use for sending and receiving messages through the connection. If you plan to use host-owned endpoints only, you don’t need to create connection-specific endpoints.

Click New in the Endpoints section.

Creating Endpoints

## Next Step After you create a third-party connection and configure third-party-specific endpoints (if needed), you can set up message flows that use the connection. ## See Also - [Partner Manager Message Flows](https://docs.mulesoft.com/partner-manager/latest/message-flows) - [Modifying Third-Party Connection Settings](https://docs.mulesoft.com/partner-manager/latest/modify-third-party-settings) - [Deleting Third-Party Connections](https://docs.mulesoft.com/partner-manager/latest/delete-third-party) --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Translation Maps > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager uses DataWeave translation maps to transform business transactions between your partner’s message formats (CSV, EDIFACT, X12, JSON, or XML) and your organization’s enterprise application message formats (CSV, JSON, or XML). To use a map, create the map in Anypoint Studio and then import the map to the [Maps](https://docs.mulesoft.com/partner-manager/latest/maps) page in Partner Manager. To start with an example of a map, download and then customize the [B2B/EDI: Order to Cash - Mapping Examples](https://mulesoft.com/exchange/com.mulesoft.muleesb.modules/b2b-order-to-cash-mapping/minor/1.0/) from Exchange. This example includes the following transformations for message flows: - Inbound message flows: - X12 4010 850 to JSON - EDIFACT D97A to JSON - CSV to JSON - XML to JSON - Outbound message flows: - JSON to X12 4010 855 - JSON to EDIFACT D97A - JSON to CSV - JSON to XML To customize this example: 1. Open the `.jar` file in Studio. 2. Change the source message type. 3. Change the target message type. 4. Map the input to the output. 5. Test the map locally. 6. Import the map to a Partner Manager message flow. ## Open the .jar File in Studio To open the `.jar` file: 1. Launch Studio. 2. From the **File** menu, select **Import > Packaged mule application (.jar)** and click **Next**. 3. Select the downloaded `.jar` file and click **Open**. 4. Click **Finish**. ## Change the Source Message Type To change the message type: 1. Click the **Global Elements** tab at the base of the Studio canvas. 2. From **Global Configuration Elements**, select the configuration for the map to use in an inbound or outbound message flow. 3. Click **Edit**. 4. In **Name**, change the name of the configuration to something meaningful. 5. If the message flow uses the EDI, JSON, X12, or XML format: 1. In **Schema definitions**, select **Edit inline**. 2. In **Value**, enter the version and transaction set to map to or from. For example, set **Value** to `/x12/005010/830.esl` to map to or from a `005010-830` transaction. 6. Click **OK**. ## Change the Target Message Type To change the target message type: 1. If your target message type has an associated schema, copy the schema file into the `/src/main/resources` folder in the project. 2. Select the **Transform Message** component. The new transaction set structure displays in one pane of the Transform Message graphical view, and your application message structure (CSV, JSON, or XML) displays in the other pane of this view. 3. Map the input fields to the output fields. ## Test the Map Locally To test the map locally: 1. In **Package Explorer**, right-click on the template project, and select **Run > Run as Mule application**. 2. Use a REST client to post a message payload. For example Postman calls, see the `B2B-Order-to-Cash-Mapping-Studio.postman_collection.json` file in the `examples` folder. The application returns the transformed payload. 3. After you verify that the map works correctly, copy the DataWeave map from `src/main/resources` and rename it to something meaningful. ## Select the Map for a Partner Manager Message Flow When you configure a message flow, you can select the `.dwl` file when adding the map from the **Maps** page or on the **Select a map** page of the message flow. You can also [version the map](https://docs.mulesoft.com/partner-manager/latest/maps#version-a-map) and change the map selection on a deployed message flow. ## See Also - [Create Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Create Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [DataWeave Quickstart](https://docs.mulesoft.com/dataweave/latest/dataweave-quickstart) - [Adding and Versioning Maps](https://docs.mulesoft.com/partner-manager/latest/maps) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deleting Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can delete endpoints from the host or partner page if the endpoints are not used in message flows: 1. From Anypoint Partner Manager, do either of the following: - If the host owns the endpoint, select the **** from the sidebar. - If a partner or third-party connection owns the endpoint, select **Partners** from the sidebar and then select the owning partner or third-party connection. 2. In the **Endpoints** section, locate the endpoint that you want to delete. To locate endpoints that don’t have associated message flows, look for `-` in the **Message Flows** column. 3. In the row containing the endpoint that you want to delete, hover over the endpoint name, select the trash can icon that appears, and click **Delete**. ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Modifying Endpoints](https://docs.mulesoft.com/partner-manager/latest/modify-endpoints) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deleting Identifiers > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can delete identifiers such as X12 ISA, X12 GS, AS2, and DUNS. Although you must always have at least one identifier per message flow, you can delete identifiers that are no longer used in that message flow. Before you delete an identifier, consider the following: - You cannot delete an identifier that is used in a message flow. - Deleting an existing host or partner identifier impacts the identification and routing of B2B messages to the associated partner. - If you need to replace the identifier with another identifier, record the required values and qualifier type. ## Steps 1. In the sidebar, select **Partners**. 2. Select the partner containing the identifier to delete. 3. In the **Identifiers** row, hover over the identifier to delete and click the trash can icon. ## See Also - [Sender and Receiver Identifiers](https://docs.mulesoft.com/partner-manager/latest/partner-manager-identifiers) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deleting Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can delete message flows that no longer serve their purpose, for example, if your relationship with your partner changes. You can delete message flows from any environment. Deleting a message flow automatically undeploys the flow. To delete a message flow: 1. In the sidebar, select **Message Flows**. 2. Select the message flow to delete and click **Delete** in the upper right of the screen. Transmissions already sent by a message flow that is subsequently deleted remain recorded in the **Activity page**. Links to the stored payloads (such as the original B2B message), TA1 acknowledgments, the transformed payload, and so on, continue to work. ## See Also - [Undeploying Message Flows](https://docs.mulesoft.com/partner-manager/latest/undeploy-message-flows) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deleting Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can delete message types from the **** page if they are not used in message flows: 1. In the sidebar, select ****. 2. In the **Message type** section, locate the message type you want to delete. To locate message types that don’t have associated message flows, look for `-` in the **Message Flows** column. 3. In the row containing the endpoint you want to delete, hover over the message type name, select the trash can that appears, and click **Delete**. ## See Also - [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type) - [Modifying Message Types](https://docs.mulesoft.com/partner-manager/latest/modify-message-type-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deleting Partners > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you are no longer trading with a partner, you can delete the partner. When you delete a partner, the partner is removed from the Partner Manager’s **Partners** page. All of the partner’s data is deleted, except for partner activities that occurred before the partner was deleted. To delete a partner: 1. From your Anypoint Partner Manager sandbox or production environment, select **Partners** from the sidebar. 2. Select the partner to delete and click **Delete**. 3. In the confirmation dialog, confirm the deletion. After you delete a partner, you can reuse the partner name. ## See Also - [Configuring and Managing Partners](https://docs.mulesoft.com/partner-manager/latest/configure-partner) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Modifying Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deleting Third-Party Connections > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you are no longer using a third-party connection, you can delete it from Anypoint Partner Manager. However, you cannot delete third-party connections if you have configured or deployed message flows for your partners that reference the third-party identifier or endpoints. When you delete a third-party connection, it is removed from the **Partners** page. Also, all of the connection’s data is deleted, except for information about connection-related activities that occurred before the deletion. To delete a third-party connection: 1. In Partner Manager, select **Partners** in the sidebar. 2. Select the third-party connection to delete and click **Delete**. 3. Confirm the deletion. After you delete a third-party connection, you can reuse the connection name. ## See Also - [Creating Third-Party Connections](https://docs.mulesoft.com/partner-manager/latest/create-third-party) - [Modifying Third-Party Connection Settings](https://docs.mulesoft.com/partner-manager/latest/modify-third-party-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deployed Message flow configuration not found for Message: > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You might occasionally see tracking information such as this in the Activity section of Anypoint Partner Manager: ```xml X12 from Received File control # TA1 sent ``` ## Causes This information appears in the Activity section when one of the following occurs: - A transmission is received that contains a message type that is not configured for any partner or flow. - A transmission is received that contains a message type that is not supported by Anypoint Partner Manager. ## Solution Verify that the message type was received via the transmission: 1. For the activity that you are viewing, inspect the message to determine the message type received. The message should contain a message identifier string like this: `v004010-810-1548-000000001`. Parts of this message are: - v004010: X12 format version received in a transmission - 810: Message type received - 1548: Group Segment Identifier (GS06) - 000000001: Message Segment Identifier (ST02) 2. From within your Anypoint Partner Manager, Sandbox or Production environment select **Message Flows**. 3. If you know the specific flow you are searching for, click on the card related to that flow to expand the associated configurations. 4. If you do not know which flow you are looking for, search by partner name or message type (such as 850) to identify possible related message flows, and click on the message flow card to open up the flow. 5. In the message flow configurator, verify that the appropriate message type (such as X12, version - 4010, message type - 850) is configured and that this matches the type of file that was listed in the Activity that indicated that an unrecognized standard was being used. 6. If there is a discrepancy between the type of message configured in the message flow compared to the message received in the activity, then either contact your partner and ask them to send the appropriate file, or correct your message flow to ensure that the message type configured matches the type you expect to receive from your partner. Partner Manager supports receiving only X12 files. If your partner sends you any other type of file such as (JSON, XML, CSV, and so on), contact your partner and ask them to send the appropriate file type to you. --- product: Partner Manager version: 2.x is-latest-version: true --- # Deploying and Testing Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager dynamically validates the message flow configuration elements as you complete them and displays a green checkmark next to each of the validated elements. After Partner Manager validates the message flow configuration elements, deploy and test the message flow in a sandbox environment. It can take up to five minutes from the time the message flow deployment completes in the UI for the changes to take effect in the runtime. ## Deploy Message Flows To deploy a message flow, click the **Deploy** button. The message flow is deployed to Mule runtime engine, enabling you to: - Start receiving messages from your partner. - Use the **Activity** page to track the processed messages. ## Test a Deployed Message Flow After you deploy the message flow, send test messages to verify that: - You can receive messages and acknowledgments from your partners. - The DataWeave map transformed the payload correctly. - Your backend applications received the transformed messages. Test your message flow in the Partner Manager sandbox environment by sending a test file to the receiving endpoint: 1. In the sidebar, select **Activity**. 2. Search for the transmission by specifying the desired filters. 3. In the transmission search results, you can do the following: - Verify that the transmission was sent or received. - Verify that Partner Manager sent the transmission to the correct endpoint. - If TA1 and functional acknowledgments (997) were set, review and confirm that they are present in the transmission. 4. Click the transmission to view more summary information. Here, you can verify whether Partner Manager routed the transmission to the correct message flow. If the transmission involves AS2 endpoints, you can also verify whether the transmission sent a message disposition notification (MDN). 5. Click the messages link to view summary information for the messages in the transmission and then click an individual message. 6. Click **Target payload** in the **Target** section to view the message’s payload and determine whether Partner Manager transformed the message correctly. 7. Repeat steps 5-6 for each message to verify. ## See Also - [Undeploying Message Flows](https://docs.mulesoft.com/partner-manager/latest/undeploy-message-flows) - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deploying AS2, HTTP, and HTTPS Receive Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can deploy AS2 receive, HTTP receive, and HTTPS receive endpoints on a public or private port. ## Deploy to CloudHub 1.0 on a Public Port When an AS2 or HTTPS receive endpoint is deployed to CloudHub with the private port configuration disabled, the endpoint application is deployed on the public HTTPS port (`8082`) or HTTP port (`8081`), with the traffic routed through the [shared load balancer](https://docs.mulesoft.com/cloudhub/dedicated-load-balancer-tutorial). The value in the URL field is automatically generated when you deploy a message flow that uses this endpoint. You can view the runtime application name and external URL for a deployed endpoint from the endpoint details page. For example: ![Example of a runtime application name and external URL](/mulesoft/current/en-us/partner-manager/latest/_images/pm-receive-endpoint-url.png) You can share the external URL with the partners that send AS2, HTTP, or HTTPS messages to this endpoint. If your organization uses Anypoint Virtual Private Cloud without a dedicated load balancer (DLB), your organization’s platform administrator can configure the necessary [Anypoint VPC firewall rules](https://docs.mulesoft.com/cloudhub/vpc-firewall-rules-concept) to allow specific partner or third-party connection IP addresses to access the endpoint. ## Deploy to CloudHub 1.0 on a Private Port To deploy an AS2, HTTP, or HTTPS receive endpoint to CloudHub 1.0 with the private port configuration enabled, you can: - Deploy a message flow that includes the receive endpoint. - Set CloudHub to automatically deploy newly created endpoints to a private port, as described in [Configuring CloudHub 1.0 Deployment Settings](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings). Endpoints with the private port configuration enabled are deployed to the private HTTPS port `8092` or HTTP (only for AS2) port `8091`. You can view the runtime application name, internal URL, and external URL for a deployed endpoint from the endpoint details page, which you can access from the <\*host\*> page (AS2 endpoints) or partner page (HTTP or HTTPS endpoints), or from a message flow. Once an endpoint is deployed, follow these steps: 1. Configure URL mapping rules to forward the messages received from your partners to an application, as described in the following sections and in [Dedicated Load Balancer Mapping Rules](https://docs.mulesoft.com/cloudhub/lb-mapping-rules). 2. Have your organization’s platform administrator add your partner’s IP addresses to a list of allowed addresses in the DLB setting, as described in [Dedicated Load Balancer Allowlists](https://docs.mulesoft.com/cloudhub/lb-allowlists). ## Deploy to CloudHub 2.0 Partner Manager deploys AS2 and HTTP inbound endpoints on CloudHub 2.0 with a HTTPS listener. - When using a shared space as the deployment target, the endpoints are accessible over the Internet and HTTP requests aren’t allowed. - When using a private space as the deployment target, you can use CloudHub 2.0 networking configurations, such as Ingress and Firewall rules, to manage and route incoming requests to your runtime applications. - If you want to allow HTTP requests to the AS2, HTTP, or HTTPS inbound endpoint application: 1. Use a private space as the deployment target. 2. On the **Advanced** tab, select `Accept HTTP` in the **HTTP requests** field. 3. Optionally, configure Network-Level Ingress Rules to allow HTTP requests from specific IP addresses. - To keep a custom public ingress URL stable across redeployments for AS2 or HTTP inbound endpoints, enable **Preserve Public URL of Ingress application** in the endpoint settings. If this option isn’t enabled, Partner Manager can regenerate the public ingress URL when redeploying the endpoint or message flow. ## External URLs and Mapping Rules for Deployed Receive Endpoints The external URLS for receive endpoints deployed to public or private ports vary depending on the endpoint type, DLB domain, and input start\_paths. You can share external URLs with your partners. ### External URL and Mapping Rules for an AS2 Receive Endpoint The external URL for an AS2 receive endpoint is `https://{DLB-domain}/{Input-path}/receive-as2`. For example, if the name of your DLB domain is `mythical.lb.anypointdns.net` and the runtime application name is `b2b-inbound-as2-zap3`, your administrator can add a URL mapping rule in the DLB settings to forward incoming requests to the runtime application within your Anypoint VPC: ![URL mapping rules for AS2 in the DLB settings](/mulesoft/current/en-us/partner-manager/latest/_images/url-mapping-rules-as2.png) With this configuration, the external AS2 endpoint URL is `https://mythical.lb.anypointdns.net/as2/mythical/receive-as2/`. ### External URL and Mapping Rule for an HTTPS Receive Endpoint The external URL for an HTTPS endpoint is `https://{DLB-domain}/{Input-path}/{base-path}/{message-type}`. For example, if the name of your DLB domain is `mythical.lb.anypointdns.net`, the base path you configured for the endpoint is `send2`, and the runtime application name is `b2b-inbound-http-ognq`, then your administrator can add a URL mapping rule in the DLB settings to forward incoming requests to the runtime application within your Anypoint VPC. For example: ![URL mapping rules for HTTPS in the DLB settings](/mulesoft/current/en-us/partner-manager/latest/_images/url-mapping-rules-https.png) ## Deploy to Runtime Fabric Partner Manager deploys AS2 and HTTP inbound endpoints to Runtime Fabric with an HTTP listener. You can expose HTTPS endpoints for internal and external users by using Runtime Fabric network configurations and Ingress rules. ## See Also - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [AS2 Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-receive) - [HTTP and HTTPS Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-receive) --- product: Partner Manager version: 2.x is-latest-version: true --- # Deploying Partner Manager Runtime Apps > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can deploy Anypoint Partner Manager runtime apps to either CloudHub or Anypoint Runtime Fabric. To configure Partner Manager deployment settings, use the **Partner Manager Settings** page in access management. You can configure separate deployment settings for each business group environment. You must have the `Partner Manager Administrator` permission to configure or modify deployment settings. ## Deploy Partner Manager Runtime Apps to a New Environment You must configure Partner Manager settings for a new environment if there is no Partner Manager configuration for any environment in a particular business group: 1. Log in to Anypoint Platform using an account that has the `Organization Administrator` permission. 2. On the main Anypoint Platform page, click **Access Management**. 3. In the Access Management sidebar, click **Business Groups**. 4. Click **Partner Manager** and then click **Configure new environment**. 5. Select the environment and deployment target types. 6. In the **Configure a Partner Manager environment** window, configure either [CloudHub 1.0 deployment settings](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0 deployment settings](https://docs.mulesoft.com/partner-manager/latest/cloudhub2-deployment-settings), or [Runtime Fabric deployment settings](https://docs.mulesoft.com/partner-manager/latest/rtf-deployment-settings). ## Deploy Partner Manager Runtime Apps to an Existing Environment Follow these steps to deploy Partner Manager to an existing business group environment: 1. Log in to Anypoint Platform using an account that has the `Organization Administrator` permission. 2. On the main Anypoint Platform page, click **Access Management**. 3. In the Access Management sidebar, click **Business Groups**. 4. Click **Partner Manager**. 5. In the **Configure a Partner Manager environment** window, configure [CloudHub 1.0 deployment settings](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0 deployment settings](https://docs.mulesoft.com/partner-manager/latest/cloudhub2-deployment-settings), or [Runtime Fabric deployment settings](https://docs.mulesoft.com/partner-manager/latest/rtf-deployment-settings). ## Modify Partner Manager Deployment Settings You can modify all Partner Manager deployment settings for an environment if you haven’t deployed any message flows to that environment. If you’ve deployed message flows to an environment, you can change the following settings: - For CloudHub deployments, you can change all settings except for the deployment target (CloudHub to Runtime Fabric) and deployment region. - For Runtime Fabric deployments, you can change all settings except for the deployment target (Runtime Fabric to CloudHub), application name prefix, and Anypoint MQ region. To modify other deployment settings: 1. Undeploy all message flows in the environment. 2. Modify the deployment settings. 3. Redeploy the message flows. ## See Also - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Undeploying Message Flows](https://docs.mulesoft.com/partner-manager/latest/undeploy-message-flows) --- product: Partner Manager version: 2.x is-latest-version: true --- # EDI Acknowledgment Reconciliation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt As your partners acknowledge your messages, Partner Manager automatically updates their acknowledgment status. To be notified, you must specifically configure acknowledgment settings when you create the message. If you expect to receive functional acknowledgments from your partners, you must [configure the acknowledgment settings](https://docs.mulesoft.com/partner-manager/latest/x12-send-settings) when you create the outbound message flow. When your organization receives the functional acknowledgment (X12 997 or EDIFACT CONTRL) from your partner, Partner Manager updates the status of the corresponding outbound transaction to one of the following: - `Accepted` - `Accepted with errors` - `Partially accepted` - `Rejected` - `Overdue`, if your organization does not receive the functional acknowledgment within the specified time period The following are examples of the actions your operations team might take while troubleshooting acknowledgment issues: - Retriggering the transaction from the back-end application when reviewing rejected transactions due to missing data elements - Asking your partner to confirm receipt of the outbound transaction when reviewing overdue transactions ## Troubleshoot Rejected or Overdue Acknowledgments You can view all the outbound transactions that have either received an X12 997 or EDIFACT CONTRL rejection or that are overdue for the functional acknowledgment: 1. In the sidebar, select **Activity**. 2. Use the search filters to filter functional acknowledgments by: - **Type** Type of message transmission: - **Both directions** - **Sent to partners** - **Received from partners** - **From Date** Filter for transmissions sent or received after this date. - **To Date** Filter for transmissions that are sent or received up to and including this date. - **Ack Status** Filter for transmissions based on their acknowledgment status: - **All** - **Overdue** - **Rejected** 3. Click the transaction you want to review. 4. From the transaction detail page, in the **Transmission** section, expand the **Sent to ** section. 5. Click **Review**. ![A transmission log that tracks all sent and received messages](/mulesoft/current/en-us/partner-manager/latest/_images/partner-manager-review-ack.png) When you review an X12 997 or EDIFACT CONTRL rejection, you see the X12 997 or EDIFACT CONTRL payload received from your partner. For example (for X12 997): ![X12 997 payload received from the partner](/mulesoft/current/en-us/partner-manager/latest/_images/partner-manager-997-ack-review-payload.png) 6. Enter a review comment to indicate the action taken on the transaction’s acknowledgment status and then click **Mark reviewed**. 7. Optionally, download the X12 payload by clicking **Download**. After an overdue or rejected transaction is marked as reviewed, it is no longer displayed in the transaction **Activity** page when you search for transactions with the acknowledgment status of `Overdue` or `Rejected`. You see only the transactions that are not reviewed by your operations team. ## See Also - [Track Transmission Activity](https://docs.mulesoft.com/partner-manager/latest/activity-tracking) - [Troubleshooting Anypoint Partner Manager](https://docs.mulesoft.com/partner-manager/latest/troubleshooting) --- product: Partner Manager version: 2.x is-latest-version: true --- # Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Endpoints define the transport protocol configurations necessary to receive or send messages with external partners or internal backend applications. Anypoint Partner Manager uses endpoints to: - Receive messages from partners - Receive messages from backend applications - Define transport protocols - Specify message or message acknowledgment destinations ## Endpoint Ownership Depending on the endpoint type, you can assign the host, partner, or third-party connection as the endpoint owner to control the use of endpoints within inbound and outbound message flows. When creating partner-facing endpoints directly from a partner or third-party connection, the ownership of the endpoint is automatically assigned to the entity from which the endpoint was created. In a message flow, endpoint availability depends on the endpoint ownership: - If an endpoint is owned by the host, any partner or third-party connection can select the endpoint. - If an endpoint is owned by a specific partner or third-party connection, then that endpoint is available only to the partner or third-party connection to which the endpoint is assigned. ## Supported Endpoint Protocols The configuration of Partner Manager endpoints depends on the endpoint type and protocol. The following table describes the endpoint types, along with their supported protocols and possible owners:
Endpoint TypeProtocolOwner

Source at Host

FTP, HTTP, HTTPS, SFTP

Host

Target at Host

FTP, HTTP, HTTPS, SFTP

Host

Receive from Partners

AS2

Host

FTP, HTTP, HTTPS, SFTP

Host, partner, third-party connection

Send to Partners

AS2

Partner, third-party connection

FTP, HTTP, HTTPS, SFTP

Host, partner, third-party connection

## Endpoint Runtime Services Using dynamic configurations, Partner Manager deploys generic endpoint services that can receive data from or send data to different endpoint configurations. You can reuse the endpoint configurations of all supported protocols across various message flows and partners. Partner Manager’s deployment orchestration service inspects the message flow and associated configuration objects and determines which endpoint services to deploy or update based on whether any new endpoint configurations are added, updated, or removed. The number and type of endpoint services deployed to your runtime depend on the transport protocols used to exchange data with your partners and backend systems. Each unique AS2, HTTP, and HTTPS receive endpoint configuration results in the deployment of its own runtime application. You can view the runtime application name corresponding to a given configuration in Partner Manager, from the endpoint details page. The endpoints for the transport protocols are always managed within a single generic endpoint service for the protocol and direction. The following table shows the prefix for the endpoint services:
ProtocolDirectionApplication Name Prefix

AS2

Receive

b2b-inbound-as2-

AS2

Send

b2b-outbound-as2-

FTP

Receive

b2b-inbound-ftp-

FTP

Send

b2b-outbound-ftp-

HTTP or HTTPS

Receive

b2b-inbound-http-

HTTP or HTTPS

Send

b2b-outbound-http-

SFTP

Receive

b2b-inbound-sftp-

SFTP

Send

b2b-outbound-sftp-

If you deploy to CloudHub, you can assign static IP addresses to the endpoint applications that connect to external systems from Runtime Manager, if your organization or your partners require allowlisting IP addresses. You can share the [static IP](https://docs.mulesoft.com/cloudhub/managing-applications-on-cloudhub#static-ips) address assigned to your endpoint application with your partners for them to allowlist the IP address, allowing the application to connect with their server. ## See Also - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Deploying AS2, HTTP, and HTTPS Receive Endpoints](https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints) --- product: Partner Manager version: 2.x is-latest-version: true --- # Failed to deploy: You cannot deploy this message flow because there is not enough capacity in this environment to deploy this message flow. > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## Cause You do not have sufficient vCore capacity to deploy the applications that support the message flow. ## Solution Contact your MuleSoft Platform Administrator to review the vCore allocation for your business group. If vCores are added, wait at least 15 minutes before attempting deployment. --- product: Partner Manager version: 2.x is-latest-version: true --- # Failed to Find Deployed Message Flow Configurations > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This error sometimes occurs when you try to find a deployed message flow on the Activity page in Anypoint Partner Manager: ```text Failed to find deployed message flow configurations. ``` ## Cause The system is still processing the deployment of the message flow. ## Solution Wait for the deployment to complete. This process can take up to 15 minutes. --- product: Partner Manager version: 2.x is-latest-version: true --- # `Failure to store message payload` > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You might occasionally see tracking information such as this in the Activity section of Anypoint Partner Manager: ```xml Unrecognized standard from unrecognized partner Received `Failure to store message payload` File ``` ## Causes This information appears in the Activity section when one of the following occurs: - The payload storage API on the host’s profile is not appropriately configured. - The payload storage API is not functioning. - The storage solution associated with the payload storage API is not functioning. ## Solution Take the following actions to verify the Payload Storage API configuration: 1. Verify the appropriate configuration for the payload storage API by performing a simple test request using a browser extension such as Postman on Google Chrome. 2. Visit Anypoint Runtime Manager to verify that the related payload storage API is active and functioning by restarting the app. 3. If the payload storage app is functioning, verify that the storage solution you are using (such as the S3 bucket, Azure Blob store, database, and so on) is up and functioning. If all these scenarios have been verified successfully, and you still cannot deploy message flows, please raise a case on the MuleSoft Support Portal. If you have an existing commercial relationship with MuleSoft and are experiencing problems accessing your Anypoint Platform account, you can open a case at [Salesforce Help](https://help.salesforce.com/s/support). If you can’t access the Support Portal, contact your Customer Success Manager or MuleSoft Account Management team for assistance. --- product: Partner Manager version: 2.x is-latest-version: true --- # Filename Patterns for Send Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Using property placeholders, Partner Manager enables you to configure a template that specifies properties and their order in the filename patterns for files delivered to SFTP and AS2 send endpoints. When filename pattern fields are configured with property placeholders (specified within `${ }`), Partner Manager dynamically populates the filename with updated information at runtime. Any filename property field that is not specified within the placeholder is static and is not updated at runtime. The following table shows the property placeholders that Partner Manager supports and the dynamic value the placeholder is replaced with at runtime. All dates and times must be in UTC format.
PlaceholderReplaced with

${DocType}

EDI Document Type

${GSSender}

Group ID of the Sender

${GSReceiver}

Group ID of the Receiver

${ISASender}

Interchange ID of the Sender

${ISAReceiver}

Interchange ID of the Receiver

${uuid}

Unique Identifier: for example: 93de0793-63e1-5a06-aedf-fcd052ed2155

${YYYY}

Year: for example, 2021

${MM}

Month: for example, 04

${DD}

Date: for example, 14

${HH}

Hour: for example, 15

${mm}

Minute: for example, 25

${SS}

Seconds: for example, 46

${sss}

Milliseconds: for example, 345

${timeInMillis}

Current time in milliseconds: for example, 1648805073834

${ICN}

Interchange Control Number

${GCN}

Group Control Number

${BusKey}

Primary Business Key value: for example, PO12345

${FormatTypeExt}

File format:

  • edifact

  • json

  • x12

  • xml

## Examples
Filename PatternGenerated Filename

${DocType}_${ISASender}_${YYYYMMDD}_${HHmmSSsss}_${ICN}.edi

850_NTORETAIL_20201102_192655521_300001.edi

INVOICE_${SenderGSID}_${ICN}.${FormatTypeExt}

INVOICE_MYTHICALSUPPLIERS_12355343.xml

${uuid}.edi

93de0793-63e1-5a06-aedf-fcd052ed2155.edi

${DocType}-${YYYY}-${MM}-${DD}-${HHmmSSsss}.dat

204-2020-06-24-192655521.dat

${DocType}_${ISASender}_${YYYYMMDD}_${HHmmSSsss}_${ICN}.${FormatTypeExt}

850_NTORETAIL_20201102_192655521_300001.json

## See Also - [AS2 Send Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-send) - [SFTP Send Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-send) --- product: Partner Manager version: 2.x is-latest-version: true --- # FTP Receive Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt FTP receive endpoints determine where to receive B2B messages transmitted over FTP. There are two types of FTP endpoints: - Receive from Partners Source endpoint in an inbound message flow that receives B2B messages from partners either directly or via third-party connections. A host, partner, or third-party connection can own FTP Receive from Partners endpoints. - Source at Host Source endpoint in an outbound message flow that receives messages from the backend applications. Only a host can own FTP Source at Host endpoints. Create FTP receive endpoints by configuring these settings on the **** or **Partner** pages. You can also create these endpoints when you configure an outbound message flow:
NameDescriptionRequired

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Receive from partners or Source at host).

x

Protocol

Protocol that the endpoint supports (FTP).

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can subsequently modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

Host

FTP server host, such as ftp.mulesoft.com, localhost, or 192.168.0.1. The host must be accessible from your Mule environment.

x

Port

Port number of the FTP server.

x

Character encoding override

Enables inbound endpoints to receive non UTF-8 encoded documents.

Username

Username for connecting to the FTP server.

x (if the server is authenticated)

Password

Password for the FTP server.

x (if the server is authenticated)

Source path

Path on the FTP server to which the partner or third-party connection sends the inbound files.

x

Skip Delete

When enabled, Partner Manager keeps the source file after reading and processing.

Use this configuration only when connecting to SFTP/FTP hosts that don’t allow explicit file deletion after the first read. Using this configuration with other SFTP/FTP hosts can result in duplicate file processing.

Skip empty files

Skip empty files during processing.

No

Polling Frequency

Frequency with which the server checks the source path for new files. The default is 1 minute.

x

Supported Format Type

Applies only to FTP endpoints owned by partners or third-party connections. Indicates whether the endpoint supports EDI messages (EDIFACT, X12) or non-EDI messages (JSON, XML).

x

Use hyphen (-) as the secondary file name delimiter to determine non-EDI message type

Lets you use a hyphen as the secondary file name delimiter to determine the message type from the message’s file name. Only shows if the supported format type is non-EDI.

No

Size check wait time

Wait time, in seconds, between size checks to determine if a file is ready for processing. The default of 1 second enables a file write to finish before processing the file.

Mule performs two size checks by waiting the amount of time specified in this field. If both checks return the same value, the file is ready to process.

To disable this feature, specify a negative number or omit the value.

x

Associated message type

(Applies when the format type is non-EDI) Message type to associate with the endpoint. If you select a message type, Partner Manager routes files received via the endpoint based on the selected message type instead of the filename.

Associated reference identifier

(Applies to partner and third-party endpoints when the format type is non-EDI) Partner information, such as the partner ID or third-party ID.

File name pattern

Filename pattern required by your partner.

Archival Path

FTP server path at which to store a copy of the file obtained from the source path.

The runtime application attempts to create the archive file up to three times. If permission or connection errors prevent Partner Manager from deleting the file, Partner Manager logs the issue in the runtime application and skips the archival step to prevent duplicate message processing.
## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) --- product: Partner Manager version: 2.x is-latest-version: true --- # FTP Send Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt FTP send endpoint settings configure where to send B2B messages transmitted over FTP. There are two types of FTP send endpoints: - Send to Partners - Target endpoint in an outbound message flow through which transformed B2B messages are sent to partners, either directly or through third-party connections - Acknowledgement endpoint in an inbound message flow A host, partner, or third-party connection can own FTP Send to Partners endpoints. - Target at Host Target endpoint in an inbound message flow through which transformed B2B messages are sent to the backend applications Only a host can own FTP Target at Host endpoints. Create FTP send endpoints by configuring these settings on the **** or **Partner** pages. You can also create these endpoints when you configure an outbound message flow:
NameDescriptionRequired

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Send to partners or Target at host).

x

Protocol

Protocol that the endpoint supports (FTP).

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

Retry interval (in seconds)

Frequency of reconnection attempts when unable to connect to the remote AS2 service. The default is 30 Seconds.

No

Maximum retry attempts

Maximum number of reconnection attempts to make. If you don’t want Partner Manager to retry after an initial connection failure, set this value to 0.

No

Host

FTP server host, such as ftp.mulesoft.com, localhost, or 192.168.0.1. The host must be accessible from your Mule environment.

x

Port

Port number of the FTP.

x

Username

Username for the FTP server.

x

Password

Password for the FTP server.

x

Target Path

Path on your FTP server to EDI files that were generated from outbound message flows. This is also the path on your FTP server for storing transformed JSON and XML files generated from inbound message flows.

x

File name pattern

Filename pattern required by your partner or back-end application.

## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Filename Patterns for Send Endpoints](https://docs.mulesoft.com/partner-manager/latest/file-name-pattern) --- product: Partner Manager version: 2.x is-latest-version: true --- # Getting Started with Partner Manager > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Partner Manager provides a simplified, configuration-driven B2B integration solution to manage B2B partner ecosystems. To use Partner Manager, follow these steps: 1. [Assign permissions to Partner Manager users](#assign-permissions). 2. [Configure Partner Manager deployment settings](#deployment-settings). 3. [Set up the Payload Storage API](#payload-storage-api). 4. [Configure a host profile](#configure-host-profile). 5. [Configure a profile for each of your partners](#configure-partners). 6. [Optionally configure third-party connections](#configure-third-party). 7. [Configure message flows](#configure-message-flows). 8. [Deploy and test configured message flows](#deploy-test-message-flows). 9. [Monitor transmissions and individual messages](#monitor-transmissions). 10. [Troubleshoot rejected or overdue acknowledgements](#troubleshoot-acks). ## Assign Permissions to Partner Manager Users For each environment, use access management to assign permissions to each Partner Manager user. You can assign the following permissions: - **Partner Manager Administrator** - Has full permissions - **View Host, Partners, and Message Flows** - Has view-only access to the host, partner, and message flow configurations - Can’t view transaction activity - **Manage Partners and Message Flows** - Can create, modify, and delete partners or message flow configurations - Can view partner configurations - Can’t view and manage transaction activity - **Manage Activity** - Can view and manage transaction activity - Can’t view or modify either partner or message flow configurations - **Manage Host** - Can create, modify, and delete host configurations - Can’t view or modify partner configurations or transaction activity This access applies even if the user has the Anypoint Platform Org Admin role. - **View Activity** - Has view-only access to transaction activity - Can’t view or modify either partner or message flow configurations For more information, see [Permissions Available in Anypoint Platform](https://docs.mulesoft.com/access-management/permissions-by-product). ## Configure Partner Manager Deployment Settings You can deploy Partner Manager runtime applications to CloudHub 1.0, CloudHub 2.0, or Anypoint Runtime Fabric. To configure deployment options, use the **Partner Manager Settings** page in access management. For more information, see [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager). ## Set Up the Payload Storage API Partner Manager requires that you deploy a payload storage API for storing transmission information. You can connect this API to your choice of a storage location, such as a database, Amazon S3, or a file system. For more information, see [Configuring a Payload Storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api). ## Configure a Host Profile Use the **** page in Partner Manager to configure a host profile for your Anypoint Platform organization or business group. A host profile consists of the EDI and AS2 identifiers used by your organization, associated digital certificates and keystores, host-owned endpoints, message types, Payload Storage API details, and global settings for EDIFACT receive messages. For more information, see [Configuring and Managing a Host Profile](https://docs.mulesoft.com/partner-manager/latest/configure-host). ## Configure a Partner Profile for Each of Your Partners A partner profile consists of partner-specific settings such as: - The partner’s name - Identifiers (such as the AS2 ID, X12-ISA, X12 GS, and so on) - Digital certificates (such as X.509 certificates) - Endpoints to use for sending and receiving messages to and from your partner - The acknowledgments, validations, and control numbers for each message format that the partner uses Configure a partner profile for each of your partners. If you plan to use only host endpoints, you don’t need to create partner-specific endpoints. For more information, see [Configuring and Managing Partners](https://docs.mulesoft.com/partner-manager/latest/configure-partner). ## Configure Third-Party Connections If your partners use third-party service providers such as VANs or 3PLs (third-party logistics providers) that manage the B2B connectivity with your organization on behalf of your partners, then create configurations for these connections. Creating third-party connections is similar to configuring partner profiles, except that the acknowledgements, validations, and control numbers associated with message formats are configured only at the partner level. For more information, see [Configuring and Managing Third-Party Connections](https://docs.mulesoft.com/partner-manager/latest/configure-third-party). ## Configure Message Flows Message flows contain the following components, which execute end-to-end B2B message processing: - Partner identifiers - Receive and send endpoints - Source and target message types - DataWeave translation maps Create inbound message flows to receive messages from your partners, transform the messages into your internal application format, and send the transformed message to your backend system. Create outbound message flows to receive messages from your backend applications, transform the messages to your partner’s message format, and send the messages to your partner. For more information, see [Configuring and Managing Message Flows](https://docs.mulesoft.com/partner-manager/latest/message-flows) and [Message Flow Components](https://docs.mulesoft.com/partner-manager/latest/partner-manager-configuration-objects). ## Deploy and Test Configured Message Flows Deploy and test the message flows in a sandbox environment. After you verify that a message flow is successful, you can undeploy it from the sandbox and redeploy it to your production environment. For more information, see [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) and [Undeploying Message Flows](https://docs.mulesoft.com/partner-manager/latest/undeploy-message-flows). ## Monitor Transmissions and Individual Messages Monitor transmission activity by searching for transactions based on criteria such as the: - Partner name - Message direction - Send and receive dates - Messaging processing status - Partner and host message type You can also search for transactions based on any custom message attributes that you defined for the message type using DataWeave. Monitor individual message activity by searching for messages based on criteria such as the: - Partner name - Message direction - Date range within which the message was sent - Acknowledgement status - Messaging process status - Partner and host message types You can also search for individual messages based on any custom message attribute that you defined for the message type using DataWeave. For more information, see [Tracking Transmissions](https://docs.mulesoft.com/partner-manager/latest/activity-tracking), [Using Custom Message Attributes with Message Types](https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes), and [Tracking Individual Messages](https://docs.mulesoft.com/partner-manager/latest/activity-message-tracking). ## Troubleshoot Rejected or Overdue Acknowledgments When you monitor transmissions, you can search by acknowledgment status (**Ack Status** field) to find outbound transmissions that either received an X12 997 or EDIFACT CONTRL rejection or that are overdue for the functional acknowledgment. Then, you can review the X12 997 or EDIFACT CONTRL payload received from your partners and add a comment to indicate the action taken. For more information, see [EDI Acknowledgment Reconciliation](https://docs.mulesoft.com/partner-manager/latest/edi-ack-reconciliation). ## See Also - [Partner Manager Overview](https://docs.mulesoft.com/partner-manager/latest/) - [Partner Manager Deployment Architecture](https://docs.mulesoft.com/partner-manager/latest/partner-manager-architecture) - [Setting up the Partner Manager Environment](https://docs.mulesoft.com/partner-manager/latest/setup) --- product: Partner Manager version: 2.x is-latest-version: true --- # HTTP and HTTPS Receive Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt HTTP and HTTPS receive endpoints configure where to receive B2B messages transmitted over HTTP or HTTPS, respectively. There are two type of HTTP and HTTPS endpoints: - Receive from Partners Source endpoint in an inbound message flow that receives inbound B2B messages from partners either directly or via third-party connections. A host, partner, or third-party connection can own HTTP and HTTPS Receive from Partners endpoints. - Source at Host Source endpoint in an outbound message flow that receives application messages from the backend applications Only a host can own HTTP or HTTPS Source at Host endpoints. > [!IMPORTANT] Each HTTP and HTTPS receive endpoint configuration gets deployed as an individual > Mule application in the runtime. To minimize the number of vCores needed to run Anypoint Partner > Manager, use an existing HTTP or HTTPS receive endpoint configuration across multiple message > flows. Create HTTP and HTTPS receive endpoints by configuring these settings on the **** page:
NameDescriptionRequired

Endpoint Name

Automatically generated name used to identify the endpoint, which you can modify manually.

x

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Receive from partners or Source at host).

x

Protocol

Protocol that the endpoint supports (HTTP or HTTPS).

x

Description

User-supplied value that describes the purpose of the endpoint.

Private port (when deploying to VPC)

Applies when using Anypoint Virtual Private Cloud (Anypoint VPC) with CloudHub deployments:

  • When enabled, the AS2 receive endpoint application deploys to the private port 8092 in your Anypoint VPC. You can manage the access control to the endpoint via the Anypoint VPC and dedicated load balancer settings.

  • When disabled, the AS2 receive endpoint application deploys to the public port 8082 by default.

    You can access the endpoint URL directly over the internet.

Manage with API Manager

Enable this setting to manage the endpoint, including its access control, with API Manager. When you manage an endpoint with API Manager, you can apply various policies, including authentication and client credentials, and you can configure SLA tiers for the endpoint. You can also leverage Anypoint Exchange to document your message specifications and share them with your partners via public portals by leveraging Anypoint API Experience Hub. (This requires an additional license.)

To have an endpoint managed with API Manager, create an HTTP API in API Manager in the same environment and organization as the endpoint.

When you create this API in API Manager:

  • Select HTTP API as the asset type.

  • Leave the defaults on the Endpoint configuration screen.

  • Copy the API instance ID and paste it into the API Auto discovery id field in the Partner Manager New endpoint: Receive from Partners window.

Using this feature requires an API Manager license.

URL

HTTP or HTTPS address where you receive outbound source messages from backend applications or inbound B2B messages from your partners. Partner Manager automatically generates this ID after the first message flow that uses the endpoint is deployed.

x

Preserve Public URL of Ingress application

Applies to CloudHub 2.0 inbound endpoint deployments.

When enabled, Partner Manager preserves the user-defined public URL for the ingress application across endpoint or message flow redeployments.

When disabled, Partner Manager can regenerate the public ingress URL during redeployment.

No

Response timeout (in milliseconds)

Response timeout period in milliseconds. The default is 15000.

x

App Name Substitution Type

Defines how the ingress URL template app-name is substituted for this AS2 endpoint to generate the Runtime Fabric public endpoint.

  • Select Default to use app-name as deployment-name.

  • Select Custom to provide a custom name for the app-name substitution.

  • Select BasePath to use the editable AS2 base path as the value for the app-name substitution.

No

Authentication type

Authentication method used to protect the HTTP or HTTPS endpoint. This field is disabled when you manage the endpoint with API Manager.

Valid values are:

x

> [!NOTE] > > - When deploying to Anypoint Runtime Fabric, Partner Manager deploys the HTTP or HTTPS receive > endpoint as an HTTP listener. > > - You must configure an Ingress controller to provide external consumers with an HTTPS endpoint. > For more information, see > [Configuring Ingress for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/custom-ingress-configuration). > > - When deploying to CloudHub 2.0, Partner Manager deploys the HTTP or HTTPS Receive endpoint as an > HTTPS listener. > > - When using a shared space as a deployment target, HTTP requests aren’t allowed. > > - To keep a user-defined public ingress URL stable across redeployments, select **Preserve > Public URL of Ingress application** in the endpoint settings. > > - If you want to allow HTTP requests to the HTTP or HTTPS receive endpoint application: > > 1. Use a private space as the deployment target. > > 2. On the **Advanced** tab, select `Accept HTTP` in the **HTTP requests** field. > > 3. Optionally, configure Network-Level Ingress Rules to allow HTTP requests from specific IP > addresses. ## API Key Authentication Authentication type that requires a valid API key in the HTTP request header. Use the following settings to configure API Key authentication:
NameDescriptionRequired

HTTP Header Name

HTTP header parameter associated with the API key value.

x

API Key

Value of the API key.

After saving your new or reconfigured endpoint, you cannot subsequently retrieve or modify the API key.

x

Certificate

Certificate to use for authentication.

### Basic Authentication Authentication type that requires a username and password in the HTTP or HTTP request header. Use the following settings to configure Basic authentication:
NameDescriptionRequired

Username

Username to use when making a request.

x

Password

Password to use when making a request.

x

## Next Step After you create an HTTP or HTTPS receive endpoint, you can deploy it, as described in [Deploying AS2, HTTP, and HTTPS Receive Endpoints](https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints). ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Managing Partner and Third-Party Connection Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # HTTP and HTTPS Send Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt HTTP and HTTPS send endpoint settings configure where to send B2B messages transmitted over HTTP or HTTPS, respectively. There are two types of HTTP and HTTPS send endpoints: - Send to Partners - Target endpoint in an outbound message flow through which transformed B2B messages are sent to the partners either directly or via a third-party connection - Acknowledgement endpoint in an inbound message flow A host, partner, or third-party connection can own HTTP and HTTPS Send to Partners endpoints. - Target at Host Target endpoint in an inbound message flow through which transformed messages are sent to the backend applications. Only a host can own HTTP and HTTPS Target at Host endpoints. Create HTTP and HTTPS send endpoints by configuring these settings on the host, partner, or third-party connection page. You can also create these endpoints when you configure an outbound message flow.
NameDescriptionRequired

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Send to partners or Target at host).

x

Protocol

Protocol that the endpoint supports (HTTP or HTTPS).

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can subsequently modify manually.

x

Description

User-supplied value that describes the purpose the endpoint.

URL

Target HTTP or HTTPS service to which to send transformed X12, EDIFACT, JSON, XML, or CSV messages. The URL must be accessible from the runtime environment that processes your B2B integrations. Enter a well-formed URL (including the path) that specifies where to send the request, for example: https://www.mulesoft.com/sendRequest

x

Response Timeout (in milliseconds)

Maximum time, in milliseconds, for the request element to block the execution of a flow that is waiting for the HTTP response. The default is 15000 milliseconds.

x

Retry interval (in seconds)

Frequency of reconnection attempts when unable to connect to the remote HTTP or HTTPS service. The default is 60 seconds.

x

Maximum retry attempts

Maximum number of reconnection attempts. To prevent Partner Manager from retrying after an initial connection failure, set this value to 0. The default is 3.

x

Authentication type

Authentication method used to protect the HTTP or HTTPS endpoint. Values are:

x

Certificate (TLS Context)

(Applies to HTTPS endpoints) SSL certificate. Values are:

  • Use CA-signed certificates

    Uses a certificate that was issued and signed by a certificate authority (CA). With this option, you don’t need to upload an additional certificate.

  • Use a self-signed certificate

    Uses a certificate that was not issued or signed by a CA. With this option, you must either select an existing certificate or upload a new certificate in <certifcate name>.PEM format.

  • Allow insecure connection

    Allows an insecure connection that doesn’t perform certificate validation.

x

## API Key Authentication Authentication type that requires a valid API key in the HTTP request header. Use the following settings to configure API Key authentication:
NameDescriptionRequired

HTTP Header Name

HTTP header parameter associated with the API key value.

x

API Key

Value of the API key.

After saving your new or reconfigured endpoint, you cannot subsequently retrieve or modify the API key.

x

Certificate

Certificate to use for authentication.

### Basic Authentication Authentication type that requires a username and password in the HTTP or HTTP request header. Use the following settings to configure Basic authentication:
NameDescriptionRequired

Username

Username to use when making a request.

x

Password

Password to use when making a request.

x

### Client Credentials Authentication Authentication type that requires a valid client ID and client secret in the HTTP or HTTPS request header. Use the following settings to configure Credit Credentials authentication:
NameDescriptionRequired

Client ID header name

HTTP header name that the client ID uses to call the endpoint URL. Default is "client_id".

x

Client ID header value

HTTP header value for the client ID.

x

Client secret header name

HTTP header name for the client secret. Default is "client_secret".

x

Client secret header value

HTTP header value for the client secret.

x

### OAuth Token Authentication Authentication type that requires a valid OAuth token in the HTTP or HTTPS request header. Use the following settings to configure OAuth Token authentication:
NameDescriptionRequired

Token URL

URL of the authentication server that provides access tokens.

x

Client ID

Client ID provided when registering your application with the authorization server.

x

Client Secret

Client secret provided when registering your application with the authorization server.

x

Scope

Permissions granted to a client application. Enter values as a space-separated list, where each string represents a permission requested by the client application. The field only applies to HTTP endpoints.

No

## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Managing Partner and Third-Party Connection Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # Inbound Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt An inbound message flow does the following: 1. Receives application messages from your partner, either directly or through a third-party connection 2. Transforms the messages to the format used by your back-end applications 3. Forwards the messages to those applications The following diagram shows the components of an inbound message flow: ![A flowchart showing an inbound message flow](/mulesoft/current/en-us/partner-manager/latest/_images/pm-inbound-message-flow.png)
CalloutSettingDescriptionSupported Formats or Protocols

A circle with a number 1 inside

Receiving endpoint

Endpoint at which a host receives transmissions from a partner

  • AS2

  • FTP

  • HTTP

  • HTTPS

  • SFTP

A circle with a number 2 inside

Source message type

Message type of the received message payload

  • CSV

  • EDIFACT

  • JSON

  • X12

  • XML

A circle with a number 3 inside

Map

DataWeave map used to transform the source message type to the target message type

N/A

A circle with a number 4 inside

Target message type

Format into which the DataWeave map transforms received messages

  • JSON

  • XML

A circle with a number 5 inside

Target endpoint

Endpoint to which the transformed message is sent (typically, a process API)

  • FTP

  • HTTP

  • HTTPS

  • SFTP

## See Also - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows) - [Inbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/inbound-message-routing) --- product: Partner Manager version: 2.x is-latest-version: true --- # Inbound Message Routing > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Depending on the endpoint type and protocol, the successful routing of your partner’s send messages to the configured source endpoints uses the message type ID, file-naming pattern, and content type. ## Messages That Use an AS2 Receive from Partners Endpoint To successfully route inbound messages that use an AS2 Receive from Partners endpoint, your partner does the following: - For non-EDI files (JSON or XML), uses a filename that begins with `{message-type-id}_`. For example, if the message type is named `custom-po`, the filename must begin with `custom-po_`. There are no filename restrictions for EDI files. - Sets the AS2 MIME-Type in the inbound AS2 message as follows, depending on the message type: - EDIFACT: `application/EDIFACT` or `text/plain` - JSON: `application/json` - X12: `application/EDI-X12` or `text/plain` - XML: `application/xml` - CSV: `text/csv` ## Messages That Use an FTP or SFTP Endpoint The process that Partner Manager uses to route inbound messages differs depending on whether the messages are EDIFACT or X12 EDI messages or non-EDI messages, such as CSV, JSON, or XML. ### EDI Messages Partner Manager routes an inbound EDIFACT or X12 EDI message based on the EDI identifier, such as ISA identifier for X12 or UNB identifier for EDIFACT, in the message content. ### Non-EDI Messages Partner Manager routes an inbound non-EDI message, such as CSV, JSON, or XML, based on either the associated message type or the filename: - If you specified an associated message type in the endpoint configuration, Partner Manager routes the message based on that message type. - If you didn’t specify an associated message type in the endpoint configuration, Partner Manager routes the message based on the filename. The filename must begin with `{message-type-id}_` and have an appropriate file extension: - `.json` for JSON files - `.xml` for XML files - `*.csv` for CSV files For example, if the message type is named `custom-po` and it’s formatted as XML, the filename must begin with `custom-po_` and end with `.xml`. ### Receive from Partners Endpoint When Partner Manager deploys endpoint applications in Mule runtime, the protocol and endpoint configurations dictate the steps the applications follow, as shown in the diagram. Next, the document processing service routes the message via the `dps-inbound-queue`. The API replication service receives a copy of the message via the `tracking-queue`, stores the message payload in your storage, and updates the tracking information in Partner Manager. [![A flowchart of the inbound message processing for AS2, HTTP, and SFTP/FTP protocols](/mulesoft/current/en-us/partner-manager/latest/_images/pm-inbound-message-routing2.png)](_images/pm-inbound-message-routing2.png) ### Document Processing The document processing application uses the inbound message’s attributes, such as content-type header, URL relative path, file name, and payload, to route the message, as shown in the diagram. If Partner Manager doesn’t find a matching message flow, the transmission receives a **Failed** status and an error message shows. ![A flowchart that depicts message flow processing and matching](/mulesoft/current/en-us/partner-manager/latest/_images/pm-dps-inbound-processing2.png) ## Messages That Use an HTTP or HTTPS Receive from Partners Endpoint To successfully route inbound messages that use an HTTP Receive from Partners endpoint or an HTTPS Receive from Partners endpoint, your partner does the following: - For EDI messages (EDIFACT or X12), posts them to the base URL and sets the Content-Type value in the incoming HTTP request as follows, depending on the message format: - EDIFACT: `application/EDIFACT` or `text/plain` - JSON: `application/json` - X12: `application/EDI-X12` or `text/plain` - XML: `application/xml` - CSV: `text/csv` - For non-EDI messages (JSON or XML), includes the message type ID in the relative path of the HTTP request. For example, suppose you have the following scenario in a CloudHub deployment: - The base URL of the HTTP or HTTPS Receive from Partners endpoint is `https://b2b-inbound-http-abcd.us-e2.cloudhub.io:443/receive1/`. - The expected message type ID for the inbound message is `custom-po`. In this case, your partner should post the message to the `https://b2b-inbound-http-abcd.us-e2.cloudhub.io:443/receive1/custom-po` URL. ## See Also - [Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows) - [Create Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Track Transmission Activity](https://docs.mulesoft.com/partner-manager/latest/activity-tracking) --- product: Partner Manager version: 2.x is-latest-version: true --- # Managing AS2 Host Keystores > For the full documentation index, see: https://docs.mulesoft.com/llms.txt AS2 host keystores consist of a public certificate and private key. Configure at least one AS2 host keystore if you use AS2 endpoints. ## Create an AS2 Host Keystore To create an AS2 host keystore: 1. In the sidebar, access the **** page. 2. In the **Certificates** section, click **New**. 3. In the **Certificate Type** field, select **Private Keypair**. 4. In the **Keystore Name** field, enter the name of the keystore file to store your organization’s private key. 5. In the ** Public Certificate** field, click **Choose file** to select a public certificate. 6. In the ** Private Key File** field, click **Choose file** to select a key file. 7. In the **Key Passphrase** field, enter a passphrase for protecting the private key. ## Update an AS2 Host Keystore When the certificate for your AS2 keystore is about to expire, perform the following steps to obtain a new one. You can update the keystore in a non-production environment and coordinate when to make the change in production with your partners. 1. Depending on your organization’s policies, create a self-signed certificate and key pair, or obtain a new AS2 certificate from your certificate authority. 2. Define a date on which you plan to switch to the new certificate. 3. Share the new public certificate with your AS2 partners to give them sufficient lead time to plan the certificate switch on their side. When it’s time to update the keystore with the new certificate, follow these steps: 1. In the sidebar, access the **** page. 2. In the **Certificates** section, click the keystore to update and then click **Edit**. 3. In the ** public certificate** field, click **Choose file**, navigate to the updated public certificate, and click **Open**. 4. In the ** private key file** field, click **Choose file**, navigate to the private key file, and click **Open**. 5. In the **Key passphrase** field, enter the passphrase for the new keystore. 6. Click **Update keystore**. 7. After the keystore updates, do either of the following: - If you have only one AS2 Receive from Partners or Send to Partners endpoint that uses the keystore, open one message flow that references the endpoint and redeploy the flow. - If you have more than one AS2 Receive from Partners or Send to Partners endpoint that uses the keystore, redeploy one message flow for each endpoint that uses the keystore. Anypoint Partner Manager updates the inbound and outbound AS2 applications in the runtime. The update can take up to 10 minutes to complete. ## Remove an AS2 Host Keystore You can remove an AS2 host keystore from Partner Manager if it isn’t associated with an endpoint. You cannot delete a host keystore if it is the only keystore that is uploaded to Partner Manager. To remove an AS2 host keystore: 1. In the sidebar, access the **** page. 2. In the **Certificates** section, click the keystore certificate to remove. 3. Click **Delete**. ## See Also - [Certificate and Keystore Storage](https://docs.mulesoft.com/partner-manager/latest/certificates) - [AS2 Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-receive) - [AS2 Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-send) - [Managing Host Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # Managing Host Certificates > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager supports the following types of host certificates:
Certificate TypeDescriptionUsed by

Identity key

Private key used for authentication

The following types of endpoints, when the authentication type is Identity Key or Basic and Identity Key:

  • SFTP Receive from Partners endpoints owned by the host

  • SFTP Source at Host endpoints

  • SFTP Send to Partners endpoints owned by the host

  • SFTP Target at Host endpoints

Public certificate

Certificate generated by a certificate authority (CA)

  • HTTPS Send to Partners endpoints owned by the host, when the TLS context is set to Use a self-signed certificate

  • HTTPS Target at Host endpoints, when the TLS context is set to Use a self-signed certificate

> [!NOTE] For AS2 endpoints, you must also configure at least one host keystore, as described in > [Managing AS2 Host Keystores](https://docs.mulesoft.com/partner-manager/latest/manage-as2-host-keystores). ## Add a Host Certificate To add a host certificate: 1. In the sidebar, access the **** page. 2. In the **Certificates** section, click **New**. 3. Select a certificate type. 4. Enter the settings for the selected certificate type: - [Public Certificate](#public-certificate) - [Identity Key](#identity-key) 5. Click **Save**. ### Public Certificate Settings To configure settings for a public certificate: 1. In the **Certificate name** field, enter the name of the public certificate. 2. In the **Certificate** field, click **Choose file** and select a public certificate. ### Identity Key Certificate Settings To configure settings for an identity key certificate: 1. In the **Identity Key Name** field, enter the name of the identity key certificate. 2. In the ** Identity Key PEM File** field, click **Choose file** and select an identity key certificate. 3. In the **Key Passphrase** field, enter a passphrase for protecting the identity key certificate. 4. In the **Expiration Date** field, optionally enter an expiration date for the certificate. This date is a reminder for you, but Anypoint Partner Manager doesn’t enforce it. ## Update a Host Certificate Update a host certificate by selecting a different certificate file to associate with the it: 1. In the sidebar, access the **** page. 2. In the **Certificates** section, click the name of the certificate that you want to update. 3. Click **Edit**. 4. Click **Choose File** and select a certificate file. 5. Click **Update**. ## Remove a Host Certificate If a host certificate isn’t associated with an endpoint, you can remove it from Anypoint Partner Manager: 1. In the sidebar, access the **** page. 2. In the **Certificates** section, hover over the name of the host certificate to remove. 3. Click the trash can icon on the right. ## Enforce Certificate Expiration Dates for AS2 Requests To prevent inbound AS2 requests with expired certificates from being processed by Anypoint Partner Manager: 1. In the sidebar, access the **** page. 2. In the **Global endpoint settings** section, click **AS2** in the **Inbound endpoint settings** column. 3. Select **Enforce AS2 certificate expiration date**. 4. Click **Save**. ## See Also - [Certificate and Keystore Storage](https://docs.mulesoft.com/partner-manager/latest/certificates) - [Configuring and Managing a Host Profile](https://docs.mulesoft.com/partner-manager/latest/configure-host) - [Managing Partner and Third-Party Connection Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # Managing Partner and Third-Party Connection Certificates > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager supports the following types of partner and third-party-connection certificates:
Certificate TypeDescriptionUsed by

Public certificate

Certificate generated by a certificate (CA)

  • AS2 Send to Partners endpoints

  • HTTPS Send to Partners endpoints

Identity key certificate

Private key used for authentication

  • SFTP Receive from Partners endpoints, when the authentication type is Identity Key or Basic and Identity Key

  • SFTP Send to Partners endpoints, when the authentication type is Identity Key or Basic and Identity Key

## Add a Certificate To add a partner or third-party-connection certificate: 1. In the sidebar, access the **Partners** page. 2. Click the partner or third-party connection that you want to create a certificate for. 3. In the **Certificates** section, click **New**. 4. Select a certificate type. 5. Enter the settings for the selected certificate type: - [Public Certificate](#public-certificate) - [Identity Key](#identity-key) 6. Click **Save**. After you create a public certificate, you can assign it to the partner to use with AS2 Send to Partners endpoints. To do this, hover over the AS2 cell in the row containing the certificate and click **Assign**. Assigning a certificate to a partner unassigns the previously-assigned certificate. > [!NOTE] You can also add certificates when you create endpoints. For more information, see > [HTTP and HTTPS Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-send), > [SFTP Receive Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-receive-target), and > [SFTP Send Endpoint Settings](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-send). ### Public Certificate Settings To configure settings for a public certificate: 1. In the **Certificate name** field, enter the name of the public certificate. 2. In the **Certificate** field, click **Choose file** and select a public certificate. ### Identity Key Certificate Settings To configure settings for an identity key certificate: 1. In the **Identity Key Name** field, enter the name of the identity key certificate. 2. In the ** Identity Key PEM File** field, click **Choose file** and select an identity key certificate. 3. In the **Key passphrase** field, enter a passphrase for protecting the identity key certificate. 4. In the **Expiration date** field, optionally enter an expiration date for the certificate. This date is a reminder for you, but Anypoint Partner Manager doesn’t enforce it. ## Update a Certificate Update a partner or third-party certificate by selecting a different certificate file to associate with it: 1. In the sidebar, access the **Partners** page. 2. Click the partner or third-party connection whose certificate to update. 3. In the **Certificates** section, click the name of the certificate to update. 4. Click **Edit**. 5. Click **Choose File** and select a certificate file. 6. Click **Update**. ## Remove a Certificate You can remove an identity key certificate from Partner Manager if the certificate isn’t associated with an endpoint. You can remove a public certificate from Partner Manager if the certificate isn’t associated with an endpoint and if it isn’t assigned to a partner or third-party connection. To remove a certificate: 1. In the sidebar, access the **Partners** page. 2. Click the partner or third-party connection whose certificate you want to remove. 3. In the **Certificates** section, hover over the name of the certificate configuration to remove. 4. Click the trash can icon that appears on the right. ## See Also - [Certificate and Keystore Storage](https://docs.mulesoft.com/partner-manager/latest/certificates) - [Configuring and Managing Partners](https://docs.mulesoft.com/partner-manager/latest/configure-partner) - [Configuring and Managing Third-Party Connections](https://docs.mulesoft.com/partner-manager/latest/configure-third-party) - [Managing Host Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # Message Flow Components > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A message flow in Partner manager comprises configuration objects that execute end-to-end B2B message processing: - [Partner identifiers](https://docs.mulesoft.com/partner-manager/latest/partner-manager-identifiers) Send and receive identifiers, such as X12 ISA and GS identifiers and AS2 identifiers - [Receive and Send endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) Receive source messages or send transformed messages using a standard transport protocol - [Source and target message types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type) Settings that define the structures of received messages and of the transformed messages sent to the backend. - [Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps) DataWeave translation maps that convert inbound EDI transactions to the back-end application format or transactions outbound from the backend to EDI format --- product: Partner Manager version: 2.x is-latest-version: true --- # Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Message types define the structure of the transactions that Anypoint Partner Manager receives or sends. You can define the following kinds of message types: - Receive from Partners Defines the structure of the transactions that partners or third-party connections send to the host through inbound message flows - Target at Host Defines the structure of the transactions that the host sends to the backend through inbound message flows - Source at Host Defines the structure of the transactions that the backend sends to the host through outbound message flows - Send to Partners Defines the structure of the transactions that the host sends to partners or third-party connections through outbound message flows Message types are always managed on the ** page, regardless of whether they are used for a single partner or for multiple partners. Additionally, message types are reusable across message flows for different partners. ## See Also - [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type) - [Receive from Partners Message Type](https://docs.mulesoft.com/partner-manager/latest/message-type-receive-from-partners) - [Target at Host Message Type](https://docs.mulesoft.com/partner-manager/latest/message-type-target-at-host) - [Source at Host Message Type](https://docs.mulesoft.com/partner-manager/latest/message-type-source-at-host) - [Send to Partners Message Type](https://docs.mulesoft.com/partner-manager/latest/message-type-send-to-partners) --- product: Partner Manager version: 2.x is-latest-version: true --- # Missing TA1 acknowledgements for my transmissions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager sends TA1 acknowledgments for a received transmission if configured to do so. Your partner might contact you to tell you that they are not receiving TA1 acknowledgments. ## Causes Any of the following can lead to this type of error: - The X12 settings for your partners are not configured to send TA1’s back to the partner. - The endpoint to which you are sending that TA1’s back may be incorrectly configured. ## Solution If you are not receiving TA1 configurations, review the following configuration: 1. From within your Anypoint Partner Manager environment (either Sandbox or Production), select **Partners** and **Receive from **. 2. Scroll to Validation and Acknowledgment settings and click **X12**. 3. Within the Acknowledgments section, ensure that the option for _Send TA1 for each transmission from _ is selected. 4. Configure the acknowledgment endpoint as in [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints). 5. Click **Save** when done. This enables TA1 acknowledgments for all transmissions received by the specific partner. --- product: Partner Manager version: 2.x is-latest-version: true --- # Modifying Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Although endpoint settings don’t often require changes, you might need to modify them under certain circumstances. For example: - Customers move their data center, so you must change the IP address or host name. - Customers update their credentials, so you must change the user credentials in the endpoint configuration. - Customers change their file naming conventions and response timeout requirements, so you must change these configurations for the endpoint. - The downstream API that receives translated inbound data moves from one region to another, so you must change the endpoint URL. To modify an endpoint: 1. Access the endpoint you want to modify from the endpoint owner’s page (the ****, ****, or third-party page, depending on the endpoint). 2. Click **Edit**. 3. Modify the desired settings. What you can modify depends on the endpoint protocol and usage, as described in the following sections: - [AS2 Receive Endpoints](#as2-receive) - [AS2 Send Endpoints](#as2-send) - [FTP Receive Endpoints](#ftp-receive) - [FTP Send Endpoints](#ftp-send) - [SFTP Receive Endpoints](#sftp-receive) - [SFTP Send Endpoints](#sftp-send) - [HTTP Receive Endpoints](#http-receive) - [HTTP Send Endpoints](#http-send) - [HTTPS Receive Endpoints](#https-receive) - [HTTPS Send Endpoints](#https-send) 4. Click **Save** to save your changes. 5. On the confirmation window that opens, select the **I understand the effects of these actions** checkbox and then click **Confirm**. Partner Manager displays a **Deploy** button next to the modified endpoint. 6. Click **Deploy** to keep the endpoint changes. 7. On the confirmation window that opens, select the **I understand the effects of these actions** checkbox and then click **Confirm**. Partner Manager redeploys the endpoint and all message flows that use the endpoint. If required, Partner Manager also automatically deploys the Mule runtime applications that Partner Manager uses. The deployment of Mule runtime applications can take up to five minutes or longer to complete, depending on how many runtime applications are affected. ## AS2 Receive Endpoints You can modify the following fields for an AS2 Receive from Partners endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Endpoint name

Yes

Description

Yes

Enforce security level and associated fields

No

## AS2 Send Endpoints You can modify the following fields for an AS2 Send to Partners endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Authentication type and associated fields

No

Connection timeout

No

Description

No

Encryption algorithm

No

Endpoint name

No

Filename pattern

No

<host> AS2 identifier

No

<host> keystore

Yes

Maximum retry attempts

No

MDN signature algorithm

No

Message subject

No

<partner> AS2 identifier

No

<partner> AS2 URL, except for changing HTTP to HTTPS or vice versa

No

Request receipt

No

Respond to email address

No

Retry interval

No

Signature algorithm

No

## FTP Receive Endpoints You can modify the following fields for an FTP Receive from Partners or Source at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Archival path

Yes

Endpoint name

Yes

Description

No

File name pattern

Yes

Host

Yes

Password

Yes

Polling frequency

Yes

Port

Yes

Character encoding override

Yes

Size check wait time

Yes

Source path

Yes

Username

Yes

## FTP Send Endpoints You can modify the following fields for an FTP Send to Partners or Target at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Description

No

Endpoint name

No

File name pattern

No

Host

No

Password

Yes

Port

No

Target path

No

Username

Yes

## SFTP Receive Endpoints You can modify the following fields for an SFTP Receive from Partners or Source at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Endpoint name

Yes

Description

No

Host

Yes

Port

Yes

Character encoding override

Yes

Authentication type

Yes

Username

Yes

Password

Yes

SSH

Yes

Source path

Yes

Polling frequency

Yes

Size check wait time

Yes

File name pattern

Yes

Archival path

Yes

## SFTP Send Endpoints You can modify the following fields for an SFTP Send to Partners or Target at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Endpoint name

No

Description

No

File name pattern

No

Host

No

Port

No

Authentication type

Yes

Username

Yes

Password

Yes

SSH

Yes

Target path

No

Filename pattern

No

## HTTP Receive Endpoints You can modify the following fields for an HTTP Receive from Partners or Source at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Connection idle timeout (in milliseconds)

Yes

Description

Yes

Endpoint name

Yes

Manage with API Manager and API Auto discovery ID

Yes

Preserve Public URL of Ingress application

Yes

## HTTP Send Endpoints You can modify the following fields for an HTTP Send to Partners or Target at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Authentication type and associated fields

Yes

Endpoint name

No

Description

No

URL

No

Response timeout (in milliseconds)

No

## HTTPS Receive Endpoints You can modify the following fields for an HTTPS Receive from Partners or Source at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Authentication type and associated fields

Yes

Connection idle timeout (in milliseconds)

Yes

Credentials

Yes

Description

Yes

Endpoint name

Yes

Manage with API Manager and API Auto discovery ID

Yes

Preserve Public URL of Ingress application

Yes

## HTTPS Send Endpoints You can modify the following fields for an HTTPS Send to Partners or Target at Host endpoint:
FieldRedeploys the Runtime Application for the Endpoint

Authentication type and associated fields

Yes

Certificate

Yes

Description

No

Endpoint name

No

Response timeout (in milliseconds)

No

URL

No

## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Deleting Endpoints](https://docs.mulesoft.com/partner-manager/latest/delete-endpoints) --- product: Partner Manager version: 2.x is-latest-version: true --- # Modifying Message Flow Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Active message flows between you and your partners don’t require much maintenance. However, you might need to: - Change flow identifiers, endpoints, or maps. - Switch from a sandbox environment and reclaim production-environment resources. - Delete the flow when it becomes inactive, as described in [Deleting Message Flows](https://docs.mulesoft.com/partner-manager/latest/delete-message-flows). > [!IMPORTANT] Before making changes, carefully consider the impact on the message flow. ## Modify the Settings of an Inbound Message Flow To modify the settings of an inbound message flow: 1. In the sidebar, select **Message Flows**. 2. On the **Message flows** page, select the message flow to modify. 3. Change any of the following settings:
SettingActionsAdditional Information

Receive from <partner>

Select different identifiers for the partner.

Partner Manager Identifiers

Receiving endpoint <endpoint name>

  • Select a different receiving endpoint.

  • (AS2 endpoint) Select a different AS2 sender.

  • (AS2 endpoint) View the AS2 certificate associated with the endpoint.

Source message

  • Select a different receive from partners message type.

  • (EDIFACT or X12 message type) View current validation settings.

  • (EDIFACT or X12 message type) Indicate whether to send a 997 functional acknowledgment and select the endpoint to which to send the acknowledgment.

Map

View the associated translation map, add additional source attributes to the map, or import another one.

Target at <host>

  • Select a different Target at Host message type.

  • Select a different Target at Host endpoint.

4. Verify that any modified sections of the flow show a green checkmark next to them and then click **Deploy** to deploy the updated message flow to Mule. > [!NOTE] It can take five minutes or so for your configuration changes to sync with Mule. 5. To test your modified message flow, see [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows). After you confirm the successful deployment of your message flow, you can track its processed messages from the **Activity** page. ## Modify the Settings of an Outbound Message Flow To modify the settings of an outbound message flow: 1. In the sidebar, select **Message Flows**. 2. On the **Message flows** page, select ****. 3. Change any of the following settings:
SubsectionActionsAdditional Information

Source at <host>

  • Select a different Source at Host endpoint.

  • Select a different Source at Host message type.

  • Select different reference IDs to use for outbound routing.

Map

View the associated translation map, add additional source attributes to the map, or import another one.

Message type

  • Select a different Send to Partners message type.

  • (EDIFACT or X12 message type) Indicate whether to send a 997 functional acknowledgment and select the endpoint to which to send the acknowledgment.

  • (EDIFACT or X12 message type) View current validation settings.

  • Select a different identifier for the host and partner. Each identifier field accepts one value and doesn’t allow multiple identifiers.

Send to <partner>

  • Select a different Send to Partners endpoint.

  • (AS2 endpoint) View the AS2 associated with the endpoint.

4. Verify that any modified sections of the flow show a green checkmark next to them and then click **Deploy** to deploy the configurations to Mule. > [!NOTE] It can take five minutes or so for your configuration changes to sync with Mule. 5. To test your modified message flow, see [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows). After you confirm the successful deployment of your message flow, you can track its processed messages from the **Activity** page. ## See Also - [Deploying and Undeploying Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Troubleshooting Anypoint Partner Manager](https://docs.mulesoft.com/partner-manager/latest/troubleshooting) --- product: Partner Manager version: 2.x is-latest-version: true --- # Modifying Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can modify a message type’s settings, but what you can modify depends on the message type’s usage and protocol: 1. In the sidebar, select the **** page. 2. Locate the message type you want to modify. 3. Change any of the following settings in the **Edit message type** window:
Message TypeFormatWhat You Can Modify

Receive from Partners

EDIFACT or X12

  • Select a different schema file, if the Schema field is set to Customize.

  • Select a different reference map file to map the reference identifiers, business key, and custom attributes.

  • Add new custom message attributes.

JSON or XML

  • Select a different schema file.

  • Select a different reference map file to map the reference identifiers, business key, and custom attributes.

Send to Partners

Any

Select a different schema file, if the Schema field is set to Customize.

Source at Host

EDIFACT or X12

  • Select a different schema file, if the Schema field is set to Customize.

  • Select a different reference map file to map the reference identifiers, business key, and custom attributes.

  • Add new custom message attributes.

JSON or XML

  • Select a different schema file.

  • Select a different reference map file to map the reference identifiers, business key, and custom attributes.

Target at Host

Any

Select a different schema file, if the Schema field is set to Customize.

4. To dissociate an associated custom message attribute from a Receive from Partners or Source at Host message type, remove it from the associated reference map. ## See Also - [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type) - [Creating Reference Maps for Message Types](https://docs.mulesoft.com/partner-manager/latest/create-reference-map) - [Deleting Message Types](https://docs.mulesoft.com/partner-manager/latest/delete-message-types) --- product: Partner Manager version: 2.x is-latest-version: true --- # Modifying Partner Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can modify a partner’s settings including contact details, identifiers, digital certificates, acknowledgments, control numbers, and more. To modify a partner’s settings: 1. In Partner Manager, select **Partners** in the sidebar. 2. Click the partner. 3. Change any of the following settings:
SettingsActionsAdditional Information

Partner information, including a partner’s address, website, and contact details

  • Modify partner information

    Click Edit in the About section, click the contact type, and make the desired modifications.

  • Delete a contact

    Click Edit in the About section, click the contact type, and click the Delete contact link.

Identifiers

  • Add a new identifier

    Click New in the Identifiers section and enter the required fields.

  • Delete an identifier

    Select the identifier and click Delete.

    Because a partner must have at least one identifier, you can’t delete the last one.

Sender and Receiver Identifiers

The partner’s digital certificates, such as X.509 certificates

Click New in the Certificates section.

Managing Partner and Third-Party Connection Certificates

Endpoints

  • Create a new endpoint

    Click New in the Endpoints section and enter the required fields.

  • Delete an endpoint

    Click the endpoint’s link and click Delete.

Creating Endpoints

Acknowledgements, validations, control numbers, character sets (X12 only), and separators (X12 send format only).

  • Modify

    Click the appropriate link in the Validation and acknowledgement settings section, and make the desired modifications.

Character encoding override option for received AS2 messages.

  • Modify

    Click AS2 in Global endpoint settings.

AS2 Receive Character Encoding Override Settings

## See Also - [Configuring and Managing Partners](https://docs.mulesoft.com/partner-manager/latest/configure-partner) - [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner) - [Deleting Partners](https://docs.mulesoft.com/partner-manager/latest/partner-manager-delete-partner) --- product: Partner Manager version: 2.x is-latest-version: true --- # Modifying Third-Party Connection Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can modify third-party connection settings including contact details, identifiers, and digital certificates. To modify third-party connection settings: 1. In Partner Manager, select **Partners** in the sidebar. 2. Click the connection to modify. 3. Modify any of the following settings:
SettingsActionAdditional Information

Third-party company information, including the company’s address, website, and contact details

  • Modify partner information:

    Click Edit in the About section, click the contact type, and make the desired modifications.

  • Delete a contact

    Click Edit in the About section, click the contact type, and click the Delete contact link.

Identifiers

  • Add a new identifier

    Click New in the Identifiers section and enter the required fields.

  • Delete an identifier:

    Select the identifier and click Delete.

    Because a third-party connection must have at least one identifier, you can’t delete the last one.

Sender and Receiver Identifiers

The partner’s digital certificates, such as X.509 certificates

Click New in the Certificates section.

Endpoints

  • Create a new connection-owned endpoint

    Click New in the Endpoints section and enter the required fields.

  • Delete a connection-owned endpoint

    Click the endpoint’s link and click Delete.

Creating Endpoints

## See Also - [Creating Third-Party Connections](https://docs.mulesoft.com/partner-manager/latest/create-third-party) - [Deleting Third-Party Connections](https://docs.mulesoft.com/partner-manager/latest/delete-third-party) --- product: Partner Manager version: 2.x is-latest-version: true --- # Outbound Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt An outbound message flow receives application messages from the backend, transforms the messages to the format your partner supports, and then forwards the messages to your partner. The following diagram shows the components of an outbound message flow: ![A flowchart showing how outbound messages are configured](/mulesoft/current/en-us/partner-manager/latest/_images/pm-outbound-message-flow.png)
CalloutSettingDescriptionSupported Formats or Protocols

A circle with a number 1 inside

Receiving endpoint

Endpoint where the host receives transmissions from the backend

  • FTP

  • HTTP

  • HTTPS

  • SFTP

A circle with a number 2 inside

Source message type

Message type of the message received from the backend

  • CSV

  • JSON

  • XML

A circle with a number 3 inside

Transform

DataWeave map used to transform the JSON or XML formats to EDIFACT or X12. The map must have Java output (output application/java) to transform JSON or XML formats to EDIFACT.

N/A

A circle with a number 4 inside

Target message type

Message type to which to transform the input message

  • CSV

  • EDIFACT

  • JSON

  • X12

  • XML

A circle with a number 5 inside

Target endpoint

Partner endpoint to which to send the transformed message

  • AS2

  • FTP

  • HTTP

  • HTTPS

  • SFTP

## See Also - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows) - [Outbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/outbound-message-routing) --- product: Partner Manager version: 2.x is-latest-version: true --- # Outbound Message Routing > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The Anypoint Partner Manager outbound message routing framework enables you to implement receiving endpoints in a variety of ways. You can: - Use a single endpoint to receive different types of application messages, such as advance shipment notices and invoices, from your backend systems. - Use dedicated endpoints for each message type from backend systems. - Follow a balanced approach by implementing a mixed set of receive endpoints to receive application messages from backend systems. When messages are received by the endpoint, Partner Manager routes the payload to the appropriate message flow based on the message type, partner reference ID, and host reference ID configurations: 1. Identifies the message type using the following criteria: - Relative path for HTTP or HTTPS endpoints - Filename for SFTP endpoints, which follow this convention: `_.`. For example, if your message type ID is ar-invoice, then the filename is `ar-invoice_20210217_1055_000.json`. 2. Validates the payload against the schema supplied during the message type definition. 3. Uses the supplied DataWeave map to obtain the partner reference ID, optional host reference IDs, and the business key. The partner reference ID and host reference ID specify the message flow through which the transaction is processed. ![A flowchart showing how outbound messages are routed](/mulesoft/current/en-us/partner-manager/latest/_images/pm-outbound-message-routing.png) ## See Also - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows) - [Track Transmission Activity](https://docs.mulesoft.com/partner-manager/latest/activity-tracking) --- product: Partner Manager version: 2.x is-latest-version: true --- # Partner Manager Administration > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Administering Partner Manager involves tracking the activity of transmissions and individual messages, reconciling EDI acknowledgments, and upgrading message flow runtime templates. For information about assigning permissions, see [Getting Started with Partner Manager](https://docs.mulesoft.com/partner-manager/latest/get-started). --- product: Partner Manager version: 2.x is-latest-version: true --- # Partner Manager Deployment Architecture > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Understanding how Partner Manager deploys runtime applications helps you choose the right deployment target for your B2B integrations. The runtime architecture differs between CloudHub and Runtime Fabric, though the configuration experience remains the same. When you deploy a message flow, Partner Manager automatically transforms your configurations and deploys runtime applications to orchestrate end-to-end B2B processing. These applications include receive endpoint services for inbound messages, document processing for parsing and translation, replication service for transaction tracking, and send endpoint services for delivering messages to partners or internal systems. ![A flowchart showing how data moves between trading partners and backend systems](/mulesoft/current/en-us/partner-manager/latest/_images/pm-high-level-arch.png)
CalloutNameDescription

A circle with a number 1 inside

Partner Manager

MuleSoft-hosted cloud control plane enabling users to configure partner profiles, build and deploy B2B integration message flows, and monitor B2B transaction activity

A circle with a number 2 inside

Receive Endpoint Services

Services to receive inbound B2B or EDI messages from partner transport protocols such as AS2 and SFTP or outbound application messages from your organization’s backend systems via HTTP, HTTPS, or SFTP

A circle with a number 3 inside

Document Processing Service

Core B2B processing engine responsible for parsing, validating, and translating received B2B messages based on configurations and mapping in Partner Manager

A circle with a number 4 inside

API Replication Service

Tracking service responsible for updating transmissions and transaction activities to the control plane and the payload storage API

A circle with a number 5 inside

Send Endpoint Services

Services to deliver transformed inbound application messages to internal applications such as ERP, billing, order management via transport protocols like HTTP, HTTPS, or SFTP; or outbound B2B EDI payloads to your partners via AS2, HTTP, HTTPS, or SFTP

A circle with a number 6 inside

Payload Storage API

API to store B2B payload data in your storage solution

## Partner Manager for CloudHub 1.0 or 2.0 When deploying B2B integration message flows to CloudHub 1.0, CloudHub 2.0, Anypoint MQ uses queues between processing stages to add additional reliability to B2B message processing. Anypoint MQ generates queues automatically in the same or nearest available region during the deployment process. Runtime applications for environments configured to deploy to CloudHub 1.0 deploy to the CloudHub region configured in the environment settings in Access Management. Runtime applications for environments configured to deploy to CloudHub 2.0 deploy to the shared or private space configured in the environment settings in Access Management. New runtime applications deploy to the same region as the first deployment. ![A diagram that illustrates how data moves through CloudHub](/mulesoft/current/en-us/partner-manager/latest/_images/cloudhub-deployment.png) ## Partner Manager for Runtime Fabric When deploying message flows to Runtime Fabric, Partner Manager uses ActiveMQ queues (set up and configured by the user) between processing stages to add additional reliability to B2B message processing. ActiveMQ destinations (queues) are automatically created when the first transaction is processed through the runtime applications. ![A flowchart showing the architecture of a data processing system](/mulesoft/current/en-us/partner-manager/latest/_images/rtf-deployment.png) ## See Also - [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager) - [Configuring and Managing Message Flows](https://docs.mulesoft.com/partner-manager/latest/message-flows) --- product: Partner Manager version: 2.x is-latest-version: true --- # Receive Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager receive endpoints have the following functions: - Receive from Partners endpoints act as source endpoints in inbound message flows that receive B2B messages from partners either directly or via third-party connections. - Source at Host endpoints act as source endpoints in outbound message flows that receive messages from backend applications. Partner Manager supports the following formats for receive endpoints: - [AS2 (Receive from Partners endpoints only)](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-receive) - [FTP](https://docs.mulesoft.com/partner-manager/latest/endpoint-ftp-receive) - [HTTP and HTTPS](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-receive) - [SFTP](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-receive-target) ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) --- product: Partner Manager version: 2.x is-latest-version: true --- # Receive from Partners Message Type Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The Receive from Partners message type defines the way in which Anypoint Partner Manager transforms the inbound transactions sent from your partner to your organization. You can define the CSV, EDIFACT, JSON, X12, or XML format for the Receive from Partners message type. ## CSV Use the following settings to define CSV as the format for the Receive from Partners message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Receive from Partners.

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

## EDIFACT Use the following settings to define EDIFACT as the format for the Receive from Partners message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Receive from partners.

Yes

Format

Format of the message. Allowed value is EDIFACT.

Yes

Version

EDIFACT version, such as d10b or d96a.

Yes

Message type

EDIFACT message type, such as ORDERS, DESADV, or INVOIC.

Yes

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 enable you to have visibility into the lifecycle of your B2B workflow. For more information, see Using Custom Messaging Attributes with Message Types.

No

Schema

EDI schema for the message type. Options include:

  • Use standard EDIFACT-<version>
    Applies the standard EDIFACT schema for the configured format and version.

  • Customize
    Enables you to import a customized EDI schema language file, if you must make adjustments to the standard EDIFACT schema.

    When using the customized EDI schema, you can assign a custom name to the message type definition, for example, EDIFACT-d97a-ORDERS-<PartnerName>.

Use standard EDIFACT <version>

Yes

## 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 tags, you must set the `minMuleVersion` to 4.5.0 or higher and upgrade your runtime environment in Access Management. 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).
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Receive from partners.

Yes

Format

Format of the message. Allowed value is JSON or XML.

Yes

Schema

Imported JSON or XSD schema file for the message type.

No

Message type identifier

Message type identifier value used in the dynamic message routing of inbound B2B transactions:

  • If a schema is associated with the message type, Partner Manager automatically generates the message type identifier from the schema filename.

    You can modify this value.

  • If a schema is not assciated with the message type, you must enter the message type identifier manually.

Your partner must pass the message type identifier as follows when sending inbound messages:

  • If you receive the payload via an HTTP-based endpoint, your partner must pass the message type identifier as the relative path in the HTTP request.

  • If you receive the payload via AS2 or a file-based endpoint protocol such as SFTP or FTP, your partner must prefix the message type identifier to the filename (<message-type-id>_<filename>).

Yes

Reference identifiers and attributes mapping

Uploaded DataWeave map that extracts the reference identifiers, business key, and custom messaging 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 enable you to have visibility into the lifecycle of your B2B workflow. For more information, see Using Custom Messaging Attributes with Message Types.

Yes

## X12 Use the following settings to define X12 as the format for the Receive from Partners message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Receive from partners.

Yes

Format

Format of the message. Allowed value is X12.

Yes

Version

X12 version, such as 3010 or 5020.

Yes

Message type

X12 transaction set number, such as 850 (purchase order) or 214( for (shipment status).

Yes

Reference identifiers and attributes mapping

Uploaded DataWeave map that extracts the reference identifiers, business key, and attribute 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 enable you to have visibility into the lifecycle of your B2B workflow. For more information, see Using Custom Messaging Attributes with Message Types.

No

Schema

EDI schema for the message type. Options include:

  • Use standard X12-<version>
    Applies the standard X12 schema for the version and message type configured.

  • Customize
    Enables you to import a customized EDI schema language file if you must make adjustments to the standard X12 schema.

    When using the customized EDI schema, you can assign a custom name to the message type definition, for example, X12-7050-204-PartnerName.

Use standard X12-<version>

Yes

For an example that shows how to customize an X12 schema, see [Customize EDI X12 Schema for B2B Integrations](https://www.mulesoft.com/exchange/works.integration/b2b-x12-custom-schema-example) in Anypoint Exchange. ## 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) --- product: Partner Manager version: 2.x is-latest-version: true --- # Replaying Transmissions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Transmissions can fail due to data validation, mapping, or connectivity issues. If a transmission fails after an Anypoint Partner Manager endpoint secures it, you can replay the transmission. You can also replay transmissions that processed successfully. You might want to do this if: - The translated payload is missing a field. In this scenario, you can upload a new translation map and replay the original transmission so that it goes through the updated map. - The target system or partner that received the original translated payloads lost data due to a system issue and requested that it be resent. Replaying a transmission regenerates the transmission source and reprocesses the original transmission as a new transmission. You can replay both inbound and outbound transmissions. The following rules apply to replaying transmissions: - You can replay any original transmission that has a status of `Failed` or `Delivered`, except for inbound transmissions that failed AS2 security validation. - The maximum number of transmissions that you can replay in a single request is 100. - Partner Manager links replayed transmission instances to the original transmission record. - When a transmission is replayed, Partner Manager sets its transmission status to `Replaying`. Once the replay action completes, Partner Manager shows the date of the last replay. To check the status of a replayed transmission, refresh the **Activity** screen and locate the transmission. - Partner Manager processes the transmission payload through the active version of the message flow. Therefore, the new transmission uses the current map and endpoint configurations for resolution and routing. If Partner Manager doesn’t find an active message flow for the transmission or message, it returns an error. - Partner Manager doesn’t check for duplicate control numbers when it replays inbound transmissions. - Partner Manager sends acknowledgments for replayed inbound transmissions based on the partner or message flow configurations at the time of replaying. ## Replay Transmissions from the Transmission List View To replay one or more transmissions from the transmissions list view: 1. In the sidebar, select **Activity**. 2. Select **Transmissions**. 3. To replay one transmission: 1. Locate the transmission. 2. On the transmission action menu (**…​**), click **Replay**. 4. To replay multiple transactions: 1. Locate and then select the transmissions. 2. Click **Replay**. ## Replay a Transmission from the Transmission Details View You can replay a transmission from the transmissions details view: 1. In the sidebar, select **Activity**. 2. Select **Transmissions**. 3. Locate the transmission to replay. 4. Click the transmission to display the transmission details view. 5. Click **Replay**. ## View a Transmission’s Replay History The replay history for a transmission shows the date for each replay and provides links to the replays. To view a transmission’s replay history: 1. In the transmissions list view, locate the transmission for which you want to see the replay history. 2. Click the transmission to bring up the transmission details view. 3. Click the last replayed date to see the following information about all replays of the transmission: - ID of the repayed transmissions - Replay dates - Replay status (a green checkmark for successful replay and a red exclamation point for a failed replay) ## See Also - [Tracking Transmissions](https://docs.mulesoft.com/partner-manager/latest/activity-tracking) --- product: Partner Manager version: 2.x is-latest-version: true --- # Send Endpoints > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager send endpoints have the following functions: - Send to Partners endpoints act as target endpoints in outbound message flows to which transformed messages are sent to partners either directly or via third-party connections. - Target at Host endpoints act as target endpoints in inbound message flows to which transformed messages are sent to backend applications. Partner Manager supports the following formats for send endpoints: - [AS2 (Send to Partners endpoints only)](https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-send) - [FTP](https://docs.mulesoft.com/partner-manager/latest/endpoint-ftp-send) - [HTTP and HTTPS](https://docs.mulesoft.com/partner-manager/latest/endpoint-https-send) - [SFTP](https://docs.mulesoft.com/partner-manager/latest/endpoint-sftp-send) ## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) --- product: Partner Manager version: 2.x is-latest-version: true --- # Send to Partners Message Type Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The Send to Partners message type defines the way in which Anypoint Partner Manager transforms the outbound transactions sent from your organization to your partner. You can define the CSV, EDIFACT, JSON, X12, or XML format for a Send to Partners message type. ## CSV Use the following settings to define CSV as the format for the Send to Partners message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Send to Partners.

Yes

Format

Format of the message. Allowed value is CSV.

Yes

## EDIFACT Use the following settings to define EDIFACT as the format for the Send to Partners message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Send to partners.

Yes

Format

Format of the message. Allowed value is EDIFACT.

Yes

Version

EDIFACT version, such as d03b or d12a.

Yes

Message type

EDIFACT message type, such as ORDERS, DESADV, or INVOIC.

Yes

Schema

EDI schema for the message type. Options include:

  • Use standard EDIFACT-<version>-<message-type>
    Applies the standard EDIFACT schema for the version and message type configured.

  • Customize
    Enables you to import a customized EDI schema language file if you must make adjustments to the standard EDIFACT schema.

    When using a customized EDI schema, you can assign a custom name to the message type definition, for example, EDIFACT-d97a-ORDERS-<PartnerName>.

Use standard EDIFACT- <version>

Yes

Name

Message type name that Partner Manager automatically generates from the schema filename. You can modify this name.

Yes

## 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 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).
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Send to partners.

Yes

Format

Format of the message. Allowed value is JSON or XML.

Yes

Schema

Imported JSON or XSD schema file for the message type.

No

Name

Name of the new message type

Yes

## X12 Use the following settings to define X12 as the format for the Send to Partners message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Send to partners.

Yes

Format

Format of the message. Allowed value is X12.

Yes

Version

X12 version, such as 3010 or 5040.

Yes

Message type

X12 transaction set number, such as 850 for a purchase order or 214 for the shipment status.

Yes

Schema

EDI schema for the message type. Options include:

  • Use standard X12-<version>-<message-type>
    Applies the standard X12 schema for the version and message type configured.

  • Customize
    Enables you to import a customized EDI schema language file if you must make adjustments to the standard X12 schema.

    When using the customized EDI schema, you can assign a custom name to the message type definition, for example, X12-7050-204-PartnerName.

Use standard X12-<version>

Yes

Name

Message type name that Partner Manager automatically generates from the schema filename. You can modify this name.

Yes

For an example that shows how to customize an X12 schema, see [Customize EDI X12 Schema for B2B Integrations](https://www.mulesoft.com/exchange/works.integration/b2b-x12-custom-schema-example) in Anypoint Exchange. ## 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) --- product: Partner Manager version: 2.x is-latest-version: true --- # Sender and Receiver Identifiers > For the full documentation index, see: https://docs.mulesoft.com/llms.txt AS2, EDIFACT, and X12 transactions use identifiers in messages to identify the senders and receivers of the messages. For X12 messages, the identifiers in the ISA and GS headers provide valuable information that enables identification of the appropriate flow to use to process the transaction. Add identifiers and configure their values in the **** page. ## Add and Configure a New Identifier 1. Access the ** page**. 2. In the **Identifiers** section, click **New**. 3. In the **New Identifier** dialog, select the identifier type from the drop-down list: - [AS2 Identity](#as2-identifier) - [EDIFACT-UNB](#edifact-unb) - [Reference ID](#reference-id) - [X12 - GS](#x12-gs) - [X12 - ISA](#x12-isa) 4. In **Identifier Value**, enter a value to uniquely name your identifier. 5. If you selected **EDIFACT-UNB** or **X12-ISA** as the **Type** value, you must also select a **Qualifier** from the list. 6. Click **Create identifier**. ## EDIFACT UNB Identifier Values Use the following values to configure the EDIFACT UNB identifier type:
SettingDescriptionRequired

Qualifier

Select the qualifier types for the partner’s EDIFACT UNB identifier from the drop-down menu.

Yes

Identifier value

Specify the EDIFACT-UNB ID for your partner, which can be up to 15 characters. Your partner supplies you with the proper EDIFACT Interchange Sender and Receiver IDs during onboarding.

Yes

## AS2 Identifier Values To use AS2 transport to exchange B2B transactions with your partner, first configure the AS2 identifier for your organization and for your partner. Use the following values to configure the AS2 identifier:
SettingDescriptionRequired

Identifier value

The AS2 identity for your partner. Your partner supplies you with the corresponding Sender and Receiver AS2 IDs during the onboarding process.

Yes

## X12 ISA Identifier Values Use the following values to configure the X12 ISA identifier type:
SettingDescriptionRequired

Qualifier

Select the qualifier type for the partner’s X12-ISA identifier from the drop-down menu.

Yes

Identifier value

EDI X12-ISA ID for your partner, which can be up to 15 characters. Your partner supplies you with the proper EDI X12 Interchange Sender and Receiver IDs during onboarding.

Yes

## X12 GS Identifier Values Use the following values to configure the X12 GS identifier type:
SettingDescriptionRequired

Identifier value

EDI X12-GS ID for your partner, which can be up to 15 characters. Your partner supplies you with the proper EDI X12 Group Sender and Receiver IDs during onboarding.

Yes

## Outbound Message Flow Partner Reference Identifiers Outbound message flows that transform your back-end application messages to EDI format use the partner Reference ID when sending data to your partners. Unlike EDI transactions that have well-defined standards for how sender, receiver, and document type information is presented in the data, the source messages for outbound B2B data exchange originating from your enterprise back-end systems typically follow schemas. These schemas are usually defined by your back-end application teams according to your organization’s data models. The receiving partner information about the application message from the back-end application might not necessarily be the same as the name of the partner in Partner Manager. This scenario is similar to how ISA and GS identifiers on an inbound EDI message might not be the same as the profile name of the partner. The Partner Manager outbound message processing framework makes a dynamic lookup to determine the receiving partner based on the content in the application message received from the backend systems. ### Example In this example, an outbound purchase order XML message from your ERP system to your partner, Mythical Supplier, has the following content in the payload: `MYTHICAL SUPPLIER, LLC` An outbound payment remittance advice JSON message from your Financials system to the same partner contains the following content in the payload: `"PayeeName": "MYTHICAL ENTERPRISES"` For Partner Manager to route these outbound transactions to the appropriate message flows for Mythical Supplier, you must add these values as Partner Reference IDs from the partner’s profile page. To do this [create a new identifier](#create-identifier) and select the type as **Reference ID**. If your back-end application sends outbound transactions to partners on behalf of more than one internal line of business, thus requiring you to set different X12 ISA and X12 GS sender identifiers on the transformed outbound data (depending on which line of business is sending the transaction), you can configure partner reference identifiers on your host profile, with the value in the application message’s payload that uniquely identifies the sending LoB. The actual usage of partner reference identifiers and how outbound message routing is determined, is explained in the outbound message documentation. ## See Also - [Delete Identifiers](https://docs.mulesoft.com/partner-manager/latest/delete-identifiers) - [Message Flows](https://docs.mulesoft.com/partner-manager/latest/message-flows) - [Outbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/outbound-message-routing) --- product: Partner Manager version: 2.x is-latest-version: true --- # Setting up the Partner Manager Environment > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Setting up the Anypoint Partner Manager environment involves the following: - Configuring Partner Manager deployment settings. You can deploy Partner Manager to either CloudHub or Anypoint Runtime Fabric, and you can configure separate deployment settings for each business group environment. Configure Partner Manager deployment settings in access management, as described in [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager). - Configuring a payload storage API. You must configure a payload storage API that provides Partner Manager with a standardized way to connect to your solution for storing transmission content. For more information, see [Configuring a Payload Storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api). - Uploading your own, self-signed certificates, if you want to use them to establish secure connections with endpoints. You can use CA-signed certificates instead of your own self-signed certificates. For more information, see [Certificate and Keystore Storage](https://docs.mulesoft.com/partner-manager/latest/certificates). --- product: Partner Manager version: 2.x is-latest-version: true --- # SFTP Receive Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt SFTP receive endpoints configure where to receive B2B messages transmitted over SFTP. There are two types of SFTP receive endpoints: - Receive from Partners Source endpoint in an inbound message flow that receives B2B messages from partners either directly or via third-party connections. A host, partner, or third-party connection can own SFTP Receive from Partners endpoints. - Source at Host Source endpoint in an outbound message flow that receives messages from the backend applications. Only a host can own SFTP Source at Host endpoints. Create SFTP receive endpoints by configuring these settings on the **** or **Partner** page:
NameDescriptionRequired

Owner

Partner or host that owns the endpoint.

x

Usage

Endpoint function (Receive from partners or Source at host).

x

Protocol

Protocol that the endpoint supports (SFTP).

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can subsequently modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

Host

SFTP server host, such as sftp.mulesoft.com, localhost, or 192.168.0.1. The host must be accessible from your Mule environment.

x

Port

Port number of the SFTP server.

x

Character encoding override

Enables inbound endpoints to receive non UTF-8 encoded documents for XML, CSV, and X12 document types.

Authentication type

Authentication method used to secure the SFTP endpoint. Values are:

  • None

    Provides no authentication for the endpoint

  • Basic

    Authenticates by using a username and password

  • Identity Key

    Authenticates by using a private SSH identity key

  • Basic and Identity Key

    Authenticates by using a username, password, and public SSH identity key

x

Username

(Applies to all authentication types except None)

Username for the SFTP server.

x

Password

(Applies to these authentication types: Basic, Basic and Identity Key)

Password for the SFTP server.

x

SSH

(Applies to these authentication types: Identity Key, Basic and Identity Key)

SSH private key file. The following considerations apply:

  • Send and receive endpoints that have the same owner can use the same SSH private key file.

  • Multiple message flows for the same or different partners can reference endpoints that use the same SSH private key file.

You can either select a private key file (.pem) that’s already configured in Anypoint Partner Manager or create a new configuration for a private key file.

To create a new configuration for a private key file:

  1. In the <partner> SSH or <host> SSH field, click Select.

  2. In the Select a <partner> ssh or Select a <host> ssh dialog, click New.

  3. Complete the fields in the New certificate for <partner> or New certificate for <host> dialog:

    • Identity Key name

      Enter the name of the private key file.

    • <partner> identity key PEM file or <host> identity key PEM file

      Click Choose file to select the private key file.

    • Key passphrase

      Enter the passphrase for the private key file.

    • Expiration date

      Enter the date on which you want the private key file to expire. This date is a reminder for you, but Anypoint Partner Manager doesn’t enforce it.

  4. Click Create.

x

Source path

Path on the SFTP server to which your partner sends the inbound files.

x

Skip Delete

When enabled, Partner Manager keeps the source file after reading and processing.

Use this configuration only when connecting to SFTP/FTP hosts that don’t allow explicit file deletion after the first read. Using this configuration with other types of SFTP/FTP hosts can result in duplicate file processing.

Skip empty files

Skip empty files during processing.

No

Polling Frequency

Frequency at which the server checks the source path for new files. The default value is 1 minute.

x

Size check wait time

Wait time, in seconds, between size checks to determine if a file is ready for processing. The default value is 1 second. This allows a file write to complete before processing.

Mule performs two size checks by waiting the amount of time specified in the Size check wait time field. If both checks return the same value, the file is ready to process.

To disable this feature, specify a negative number or omit the value.

x

Support Format type

Indicates whether the endpoint supports EDI messages (EDIFACT, X12) or non-EDI messages (JSON, XML).

x

Associated message type

(Applies only to endpoints that support non-EDI formats) Message type to associate with the endpoint. If you select a message type, Partner Manager processes files received via the endpoint as the selected message type, regardless of the file naming convention.

Use hyphen (-) as the secondary file name delimiter to determine non-EDI message type

Lets you use a hyphen as the secondary file name delimiter to determine the message type from the message’s file name. Only shows if the supported format type is non-EDI.

No

Associated reference identifier

(Applies only to endpoints that support non-EDI formats that are owned by partners or third-party connections.) Partner information, such as the partner ID or third-party ID.

File name pattern

Filename pattern required by your partner.

Archival Path

Directory path on the SFTP server at which to store a copy of the file after processing.

The runtime application attempts to create the archive file up to three times. If permission or connection errors prevent Partner Manager from deleting the file, Partner Manager logs the issue in the runtime application and skips the archival step to prevent duplicate message processing.
## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Managing Partner and Third-Party Connection Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-partner-certificates) --- product: Partner Manager version: 2.x is-latest-version: true --- # SFTP Send Endpoint Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt SFTP send endpoint settings configure where to send B2B messages transmitted over SFTP. There are two types of SFTP send endpoints: - Send to Partners - Target endpoint in an outbound message flow through which transformed B2B messages are sent to partners, either directly or through third-party connections - Acknowledgement endpoint in an inbound message flow A host, partner, or third-party connection can own SFTP Send to Partners endpoints. - Target at Host Target endpoint in an inbound message flow through which transformed JSON and XML messages are sent to the backend applications. Only a host can own SFTP Target at Host endpoints. Create SFTP send endpoints by configuring these settings on the **** or **** pages. You can also create these endpoints when you configure an outbound message flow:
NameDescriptionRequired

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Send to partners or Target at host).

x

Protocol

Protocol that the endpoint supports (SFTP).

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

Retry interval (in seconds)

Frequency of reconnection attempts when unable to connect to the remote AS2 service. The default is 30 Seconds.

No

Maximum retry attempts

Maximum number of reconnection attempts to make. If you don’t want Partner Manager to retry after an initial connection failure, set this value to 0.

No

Host

SFTP server host, such as sftp.mulesoft.com, localhost, or 192.168.0.1. The host must be accessible from your Mule environment.

x

Port

Port number of the SFTP.

x

Authentication type

Authentication method used to secure the SFTP endpoint. Values are:

  • None

    Provides no authentication for the endpoint

  • Basic

    Authenticates by using a username and password

  • Identity Key

    Authenticates by using a private SSH identity key

  • Basic and Identity Key

    Authenticates by using a username, password, and public SSH identity key

x

Username

(Applies to all authentication types except None)

Username for the SFTP server.

x

Password

(Applies to these authentication types: Basic, Basic and Identity Key)

Password for the SFTP server.

x

SSH

(Applies to these authentication types: Identity Key, Basic and Identity Key)

SSH private key file. The following considerations apply:

  • Send and receive endpoints that have the same owner can use the same SSH private key file.

  • Multiple message flows for the same or different partners can reference endpoints that use the same SSH private key file.

You can either select a private key file (.pem) that’s already configured in Anypoint Partner Manager or create a new configuration for a private key file.

To create a new configuration for a private key file:

  1. In the <partner> SSH or <host> SSH field, click Select.

  2. In the Select a <partner> ssh or Select a <host> ssh dialog, click New.

  3. Complete the fields in the New certificate for <partner> or New certificate for <host> dialog:

    • Identity Key name

      Enter the name of the private key file.

    • <partner> identity key PEM file or <host> identity key PEM file

      Click Choose file to select the private key file.

    • Key passphrase

      Enter the passphrase for the private key file.

    • Expiration date

      Enter the date on which you want the private key file to expire. This date is a reminder for you, but Anypoint Partner Manager doesn’t enforce it.

  4. Click Create.

x

Target Path

Path on your SFTP server to EDI files that were generated from outbound message flows. This is also the path on your SFTP server for storing transformed JSON and XML files generated from inbound message flows.

x

Filename pattern

Filename pattern required by your partner or back-end application.

## See Also - [Endpoints](https://docs.mulesoft.com/partner-manager/latest/endpoints) - [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint) - [Filename Patterns for Send Endpoints](https://docs.mulesoft.com/partner-manager/latest/file-name-pattern) --- 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:
SettingDescriptionDefaultRequired

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 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 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).
SettingDescriptionDefaultRequired

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 - [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) --- product: Partner Manager version: 2.x is-latest-version: true --- # Target at Host Message Type > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The Target at Host message type defines the way in which Anypoint Partner Manager transforms inbound transactions sent from your organization to your backend applications. You can define the CSV, JSON, or XML format for the Target at Host message type. ## CSV Use the following settings to define CSV as the format for the Target at Host message type:
SettingDescriptionDefaultRequired

Usage

Message usage. Allowed value is Target at Host.

Yes

Format

Format of the message. Allowed value is CSV.

Yes

## 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 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).
SettingDescriptionDefaultRequired

Format

Format of the message. Allowed value is JSON or XML.

Yes

Schema

Imported JSON or XSD schema file for the message type.

No

Name

Message type name that Partner Manager automatically generates:

  • If a schema is associated with the message type, Partner Manager automatically generates the message type name from the schema filename.

    You can modify this value.

  • If a schema is not associated with the message type, you must enter the message type name manually.

Yes

## 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) --- product: Partner Manager version: 2.x is-latest-version: true --- # Tracking Individual Messages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The message view in Anypoint Partner Manager provides visibility into individual transactions within a transmission. Use the message view to monitor the messages exchanged between partner and suppliers, view the message payload, and see how individual messages are processed and routed. The message view has one record for each transaction. For example, if an incoming transmission contains 30 transactions, the message view has 30 corresponding records. A message record contains the following information: - Business key and other custom attributes that are included in the message type definition - Pre-translated and post-translated payloads Partner Manager does not create message view records when: - An inbound transaction fails during validation, resulting in a complete rejection of the transaction. - An inbound transaction fails due to AS2 security issues. - An outbound transaction fails when translating the source payload to a different format. - An outbound transaction fails when writing X12 or EDIFACT data. To track transmissions instead of individual messages, see [Tracking Transmissions](https://docs.mulesoft.com/partner-manager/latest/activity-tracking). ## Locate a Message Select a message to view its details and view and download its contents: 1. In the sidebar, select **Activity**. 2. Leave the default, **Messages**. 3. Search for the message. 4. Optionally, filter the search results based on the following criteria: - Partner name - Message direction - Date range within which the message was sent You can retrieve up to one week’s worth of messages. - Message processing status, such as `Received` - Acknowledgement status, such as `Overdue` - Partner message type, such as `X12 - 850` - Host message type, such as `JSON host-purchase-order` - Message attribute, if the message type associated with the message has custom attributes - Message value - Transmission or message ID Partner Manager returns a list of messages that meet your search criteria along with related information such as the date the message was received, message status, message type, partner, document ID, business key, and acknowledgment status. 5. Click on a message to review additional information about the message and to view its message flow. ## View Additional Details for an Inbound Message The additional details for an inbound message include the following information: - Message ID - Transmission ID - Message flow name - Functional acknowledgment name, if one exists - Information about the message source, including the date and time when the message was received from the source, partner message type, endpoint name, filename, and target protocol - Identifiers and control number associated with the message - Information about the message target, including the date and time when the message was delivered, host message type, target endpoint, protocol, and target filename Take any of the following actions to view and download additional information about the inbound message:
ActionSteps

View the transmission that contains the message.

Click the link in the Transmission Id field.

View information about the source (Receive from Partner) endpoint.

In the Source section, click the link in the Source endpoint field.

View information about the target (Target at Host) endpoint.

In the Target section, click the link in the Target endpoint field.

View and download the payload received from the partner.

  1. In the Source section, click the link in the Source file field.

  2. Specify a wrap character, if needed.

  3. Click Download.

View and download the payload sent to the backend.

  1. In the Target section, click the link in the Target file field.

  2. Specify a wrap character, if needed.

  3. Click Download.

View and download the MDN message sent to the partner in response to inbound AS2 transmissions.

  1. Click the link in the Transmission details field to access the Transmission Flow section.

  2. In the Sent MDN field, click View MDN.

  3. Specify a wrap character, if needed.

  4. Click Download.

View and download the EDIFACT CONTRL message or X12 997 acknowledgment message sent to the partner, if one exists.

  1. Click the link in the Transmission details field to access the Transmission Flow section.

  2. In the Processed message through message flows section, click View Control or View 997.

  3. Specify a wrap character, if needed.

  4. Click Download.

View the message flow diagram for the transmitted message.

Click the link in the Processed message through message flows field.

Expand the message flow diagram sections to view additional information, including information about the receiving (Receive from Partners) endpoint, source message, DataWeave map, target message type, and target (Target at Host) endpoint.

## View Details for an Outbound Message The details for an outbound message include the following information: - Date and time when the file was received from the backend - Functional acknowledgment, if one exists - Name of the transmitted file - Information about the message source, including the source message type, source endpoint name, and source protocol - Identifiers and control numbers associated with the message - Information about the message target, including the partner message type, date, and time when the message was sent to the partner, target filename, and target endpoint name Take any of the following actions to view and download additional information about the outbound message:
ActionSteps

View and download the payload transmitted to the partner.

  1. In the Summary section, click the link in the Transmission details field.

  2. Click the link in the File field.

  3. Specify a wrap character, if needed.

  4. Click Download.

View information about the source (Source at Host) endpoint.

In the Source section, click the link in the Source endpoint field.

View and download the payload received from the backend.

  1. In the Source section, click the link in the Source file field.

  2. Specify a wrap character, if needed.

  3. Click Download.

View information about the target (Send to Partners) endpoint.

In the Target section, click the link in the Target endpoint field.

View and download the payload sent to the partner.

  1. In the Target section, click the link in the Target file field.

  2. Specify a wrap character, if needed.

  3. Click Download.

View and download the MDN received from the partner in response to outbound AS2 transmissions.

  1. In the Summary section, click the link in the Transmission details field to access the message flow diagram.

  2. In the message flow diagram, expand the Sent to section.

  3. In the Received MDN field, click View payload.

  4. Specify a wrap character, if needed.

  5. Click Download.

View the EDIFACT CONTRL or X12 997 acknowledgment message received from the partner, if one exists.

  1. In the Summary section, click the link in the Transmission details field to access the message flow diagram.

  2. In the message flow diagram, expand the Sent to section.

  3. In the Sent transmission field, click View payload.

  4. Specify a wrap character, if needed.

  5. Click Download.

View and download the DataWeave map that transformed the transmission.

  1. In the Summary section, click the link in the Transmission details field to access the message flow diagram.

  2. Click the Map section to expand it.

  3. Click the link in this section.

  4. Click Download.

## View Message Summaries Use AI to generate a summary of the message payload. Make sure you’ve enabled Einstein in [CloudHub 1.0](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0](https://docs.mulesoft.com/partner-manager/latest/cloudhub2-deployment-settings), or [Runtime Fabric](https://docs.mulesoft.com/partner-manager/latest/rtf-deployment-settings) deployment settings. To generate a summary, open the source or target payload on the message details page and click **Summarize**. If this is the first time you’re viewing a summary, accept the conditions to allow the use of Einstein. The summary shows key details, such as the message type, sender, and receiver, as well as the contents of the message like the order number, customer name, and order details. ## See Also - [Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows) - [Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/outbound-message-flows) - [EDI Acknowledgment Reconciliation](https://docs.mulesoft.com/partner-manager/latest/edi-ack-reconciliation) - [Troubleshooting Anypoint Partner Manager](https://docs.mulesoft.com/partner-manager/latest/troubleshooting) --- product: Partner Manager version: 2.x is-latest-version: true --- # Tracking Transmissions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In Anypoint Partner Manager, one transmission can consist of one or more messages. Use the transmission view to monitor transmissions exchanged between partners and to view the transmission contents. At a high level, a transmission record contains the following information: - Data payloads received from partners or sent to partners via a configured protocol such as AS2, HTTP, SFTP or FTP - Message disposition notifications (MDNs), if the payload is exchanged with partners via AS2 protocol functional acknowledgments To track individual messages, see [Tracking Individual Messages](https://docs.mulesoft.com/partner-manager/latest/activity-message-tracking). ## Locate a Transmission Select a transmission to view its details and view and download the message contents: 1. In the sidebar, select **Activity**. 2. Select **Transmissions**. 3. Search for the transmission. 4. Optionally, filter the search results based on the following criteria: - Partner name - Message direction - Date range within which the message was sent You can retrieve up to one week’s worth of messages. - Message processing status, such as `Received` - Acknowledgment status, such as `Overdue` - Partner message type, such as `X12 - 850` - Host message type, such as `JSON host-purchase-order` - Transmission ID - Whether transmissions are replays Partner Manager returns a list of transmissions that meet your search criteria along with related information, such as the date the transmission was received, number of messages in the transmission, message type, control number, and acknowledgment status. 5. Do either of the following: - Click a transmission to review additional information about the transmission and to view its message flow. - Click **messages** to see information about the messages in the transaction, as described in [Activity Message Tracking](https://docs.mulesoft.com/partner-manager/latest/activity-message-tracking). ## View Details for an Inbound Transmission The additional details for an inbound transmission include the following information: - Transmission status (a green checkmark for success or a red exclamation point for failure) - Transmission ID - Control number associated with the transmitted file, if available - Information about the message source, including the date and time that the message was received, control number, name and protocol of the receiving (Receive from Partners) endpoint, and message type, such as `mythical-po-ack` - Number of received messages for each message type in the transmitted file - Custom message attributes, if any. If the transmission is a replay, the details also include a link to the original (replayed) transmission. If this transmission was replayed, the details also include the date and time of the most recent replay. Take any of the following actions to view and download additional information about the inbound transmission:
ActionSteps

View the original transmission if the message is a replay.

Click the link in the Original Transmission Id field.

View the messages in the transmission.

Click messages.

View and download the transmission payload received from the partner.

  1. In the Received transmission field, click View Payload.

  2. Specify a wrap character, if needed, and click Apply.

  3. Click Download.

View and download the MDN message sent to the partner in response to an inbound AS2 transmission, if an MDN message exists.

  1. In the Sent MDN field, click View MDN.

  2. Specify a wrap character, if needed, and click Apply.

  3. Click Download.

View and download the EDIFACT CONTRL or X12 997 acknowledgment message sent to the partner, if one exists.

  1. In the Processed message through message flows field, click View CONTRL or View 997 for each message type.

  2. Specify a wrap character, if needed, and click Apply.

  3. Click Download.

View the message flow diagram for the transmission.

Click the link in the Processed message through message flows field to view the message flow diagram.

From the message flow diagram, you can expand the message flow sections to view additional information, including information about the receiving (Receive from Partners) endpoint, source message, DataWeave translation map, and target message type and endpoint.

## View Details for an Outbound Transmission The details for an outbound transmission include the following information: - Transmission status (a green checkmark for success or a red exclamation point for failure) - Message ID - Transmission ID - Date and time when the file was sent - Control number associated with the transmitted file, if one exists - Message type, such as `mythical-po-ack-json: ORD-9892330` - Name of the sending (Send to Partners) endpoint - Name of the transmitted file - Number of messages in the transmission If this transmission is a replay, the details also include the transmission ID of the original (replayed) transmission. If this transmission was replayed, the details also include the date and time of the most recent replay. Take any of the following actions to view and download additional information about the outbound transmission:
ActionSteps

View the original transmission if the message is a replay.

Click the link in the Original Transmission Id field.

View information about the sending (Send to Partner) endpoint.

In the Summary section, click the link in the Endpoint field.

View and download the transmission payload.

  1. In the Summary section, click the link in the File field.

  2. Specify a wrap character, if needed.

  3. Click Download.

View and download the payload received from the backend.

  1. In the message flow diagram, expand the Source section.

  2. Click View Payload.

  3. Specify a wrap character, if needed.

  4. Click Download.

View information about the source (Source at Host) endpoint

  1. In the message flow diagram, expand the Source section.

  2. Click the link in the Received payload section.

View and download the DataWeave map that transformed the transmission.

  1. In the message flow diagram, expand the Map section.

  2. Click the link in this section.

  3. Specify a wrap character, if needed.

  4. Click Download.

View information about the message type, including its name, type, identifiers, and control numbers

In the message flow diagram, expand the Message Type section.

View and download the payload sent to the partner.

  1. In the message flow diagram, expand the Sent to section.

  2. In the Sent transmission field, click View payload.

  3. Specify a wrap character, if needed.

  4. Click Download.

View and download the MDN received from the partner in response to outbound AS2 transmissions.

  1. In the message flow diagram, expand the Sent to section.

  2. In the Received MDN field, click View payload.

  3. Specify a wrap character, if needed.

  4. Click Download.

View the EDIFACT CONTRL or X12 997 acknowledgment message received from the partner, if one exists.

  1. In the message flow diagram, expand the Sent to section.

  2. In the Sent transmission field, click View payload.

  3. Specify a wrap character, if needed.

  4. Click Download.

View the original transmission if the current transmission is a replay.

  1. In the message flow diagram, expand the Last replayed section.

  2. Click the link in this section.

## See Also - [Replaying Transmissions](https://docs.mulesoft.com/partner-manager/latest/replay-transmissions) - [Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows) - [Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/outbound-message-flows) - [EDI Acknowledgment Reconciliation](https://docs.mulesoft.com/partner-manager/latest/edi-ack-reconciliation) - [Troubleshooting Anypoint Partner Manager](https://docs.mulesoft.com/partner-manager/latest/troubleshooting) --- product: Partner Manager version: 2.x is-latest-version: true --- # Translation Maps > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Translation maps are DataWeave transformation files that enable Anypoint Partner Manager to convert business transactions between your partner’s message formats and your organization’s enterprise application message formats. These maps are essential for B2B integration, allowing seamless data exchange between different systems and formats. ## Get Started with Translation Maps To use translation maps in Partner Manager: 1. Start by creating or customizing a DataWeave maps in Anypoint Studio. 2. Import the completed map to the [Maps](https://docs.mulesoft.com/partner-manager/latest/maps) page in Partner Manager. 3. Select and deploy the map in message flows. 4. Version the map as your business requirements evolve. 5. Apply updated versions of your translation maps without needing to individually upload the map file to each message flow. ## Supported Map Formats and Transformations Partner Manager supports mapping translations between these formats: - **Partner formats** CSV, EDIFACT, X12, JSON, or XML - **Enterprise application formats** CSV, JSON, or XML ## See Also - [Creating Translation Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps) - [Adding and Versioning Maps](https://docs.mulesoft.com/partner-manager/latest/maps) - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) - [DataWeave Quickstart](https://docs.mulesoft.com/dataweave/latest/dataweave-quickstart) --- product: Partner Manager version: 2.x is-latest-version: true --- # Troubleshooting Anypoint Partner Manager > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager relies on several different MuleSoft technologies including but not limited to Mule, Anypoint Runtime Manager, secrets manager, and your infrastructure for B2B storage payloads. Because Anypoint Partner Manager is used with other technologies, troubleshooting an issue with Partner Manager often involves troubleshooting these other technologies as well. Look for solutions in the documentation about connectivity and related errors or use the documentation page’s navigation pane to locate troubleshooting information specific to either Anypoint Partner Manager or its related technologies. ## See Also - [Known Issues](https://help.salesforce.com/s/issues) --- product: Partner Manager version: 2.x is-latest-version: true --- # Troubleshooting Configuration and Deployment-Related Errors > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you encounter errors as you set up your partners and message flows, the messages and solutions described here can help you resolve your issue. ## See Also - [Known Issues](https://help.salesforce.com/s/issues) --- product: Partner Manager version: 2.x is-latest-version: true --- # Troubleshooting Connectivity or System-Related Errors > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you have problems receiving or sending data, the messages and solutions described here can help resolve your issue. ## See Also - [Known Issues](https://help.salesforce.com/s/issues) --- product: Partner Manager version: 2.x is-latest-version: true --- # Troubleshooting Data Processing-Related Errors > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you encounter problems with message validations and transformations, the messages and solutions described here can help you resolve your issue. ## See Also - [Known Issues](https://help.salesforce.com/s/issues) --- product: Partner Manager version: 2.x is-latest-version: true --- # Undeploying Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Undeploying a message flow prevents future messages from being processed and enables you to recover resources that are consumed by a message flow that you no longer need. You can undeploy your message flow from either a sandbox or a production environment. The undeployment process takes about five minutes, during which actions such as `Deploy` and `Delete` are unavailable. > [!IMPORTANT] During the undeployment process, do not log out of Anypoint Partner Manager or close > your browser window. To undeploy a message flow: 1. In the sidebar, select **Message Flows**. 2. Select the message flow to undeploy from the list and click **Undeploy**. Partner Manager checks to see if any of the applications deployed to Mule are orphaned as a result of the undeployment. Partner Manager then cleans up orphaned applications to release any resources that the applications consumed. ## See Also - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) - [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow) - [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow) --- product: Partner Manager version: 2.x is-latest-version: true --- # `Unrecognized partner` transaction reported > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You might occasionally see tracking information such as this in the Activity section of Anypoint Partner Manager: ```xml from Unrecognized partner control # Partner not found for with ``` ## Causes This information appears in the Activity section when one of the following occurs: - Partner Manager cannot identify the sender of the transmission either because the partner is not configured in Partner Manager, or because the identifier associated with the partner is not configured. - Partner Manager cannot identify the receiver for the transmission because the identifier associated with the receiver is not configured. - Partner Manager cannot identify both the sender and the receiver of this transmission. ## Solutions Verify partner and host identifiers. ### Verify Partner’s Identifiers Verify that your partner has the appropriate identifiers configured as needed to support the transmission. 1. From within your Anypoint Partner Manager, Sandbox or Production environment select **Partners** . 2. From the Partners profile, scroll to the Identifiers section and verify that the identifier you are looking for is present in the table. 3. If the desired partner identifier is not present, click **New** and select an identifier type from the Type list to uniquely identify your partner. 4. Provide a value for your identifier (and a qualifier for X12-ISA) and click **Create identifier** to save your changes. See [X12 - ISA Identifier Values](https://docs.mulesoft.com/partner-manager/latest/x12-identity-settings) for more information about X12-ISA settings. ### Verify Organization (Host) Identifiers Verify that your organization (the host) has the appropriate identifiers configured as needed to support the transmission. 1. From within your Anypoint Partner Manager, Sandbox or Production environment select **Partners** . 2. Within the Host’s profile page, scroll to the Identifiers section and verify that the identifier you are looking for is present in the table. 3. If the desired host identifier is not present, click **New** and select an identifier type from the Type list to uniquely identify your partner. 4. Provide a value for your identifier (and a qualifier for X12-ISA) and click **Create identifier** to save your changes. See [X12 - ISA Identifier Values](https://docs.mulesoft.com/partner-manager/latest/x12-identity-settings) for more information about X12-ISA settings. --- product: Partner Manager version: 2.x is-latest-version: true --- # `Unrecognized standard from unrecognized partner` > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You might occasionally see tracking information such as this in the Activity section of Anypoint Partner Manager: ```xml Unrecognized standard from unrecognized partner Received File ``` ## Causes This information appears in the Activity section when one of the following occurs: - Partner Manager receives a transmission that is in an unsupported data format: for example, receiving a PDF, image, and so forth on receiving endpoints. - Your partner sends you a valid X12 file but you have not configured a message flow that can accept it. - You do not recognize the partner because you did not set them up in Anypoint Partner Manager. ## Solution If you encounter any of these situations, verify that your partner is sending valid X12-formatted files that align with the message flows that you associated with that partner. --- product: Partner Manager version: 2.x is-latest-version: true --- # Updated message flow configuration does not take effect on the runtime B2B integration applications > For the full documentation index, see: https://docs.mulesoft.com/llms.txt As you continue to use Anypoint Partner Manager, you might need to update the configuration associated with a previously deployed message flow. For example, after updating the configuration, you still find your message flow executing with the previous or older set of configurations. ## Causes Any of the following can lead to this type of error: - You might have not deployed the message flow after making changes to the message flow’s configuration. - You might be within the five-minute synchronization window for changes from Anypoint Partner Manager to reflect on your B2B integration applications. ## Solutions You can deploy the changed message flow or wait for the synchronization window to complete. ### Deploy the Changed Message Flow After you make changes to the message flow configuration, you must deploy it in order for the new configurations to become effective on your B2B integration applications. To deploy your message flow after making changes: 1. From within your Anypoint Partner Manager environment (either Sandbox or Production), select your profile. 2. Select **Message Flows**. 3. Search for your message flow by name. 4. After you locate the message flow, click on the message flow card to open it. 5. Confirm that each section in the flow shown in the interface displays a green checkmark next to it, and click Deploy to deploy the configurations to Mule. 6. Provide the necessary reason to trigger a new deployment, and wait for the process to complete. When the deployment is successfully completed, Anypoint partner manager responds with a successful notification. ### Wait for the Synchronization Window to Complete for All Changes Your runtime B2B integration applications executing on your Mule runtimes receive the latest configuration from the Anypoint Partner Manager control plane at five-minute intervals. Depending on when you made the configuration changes to your message flows in Partner Manager and deployed them, your changes can take up to five minutes to take effect on the runtime. --- product: Partner Manager version: 2.x is-latest-version: true --- # Upgrading Message Flow Runtime Templates > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Partner Manager uses prebuilt templates to convert your B2B message flow configurations into generic runtime applications. As these templates are updated, you can upgrade your message flows to use them to take advantage of new capabilities that enable better integration with your partner’s ecosystem. Runtime templates related to Partner Manager are upgraded when: - A new feature or functionality is added - A component on which your environment is dependent, such as a connector version, is upgraded - A security vulnerability is fixed - Functional and performance defects are resolved in the template - Flow optimizations are implemented When new runtime templates are available, a tooltip shows on the **Manage deployments** button to indicate there’s a new version available. To take advantage of new features, click **Manage deployments**, select **Upgrade deployments**, confirm that you understand the effects of these actions, and then click **Confirm**. Upgrading deployments updates all the Mule applications in your runtime with the latest template versions that contain new features or bug fixes. The process of updating all your message flows can take several minutes, depending on the number of message flow configurations and runtime applications in your environment. Your existing message flows continue uninterrupted during the upgrade process. Before upgrading your production environment, upgrade your nonproduction environments to test the changes on some of your message flows. ## See Also - [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows) --- product: Partner Manager version: 2.x is-latest-version: true --- # Using Custom Message Attributes with Message Types > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can associate up to five custom message attributes with a Receive from Partners or Source at Host message type. Using these attributes enables you to have visibility into the full lifecycle of your B2B workflow. For example, you can define attributes for a message’s PO number, Sales order number, Invoice number, and Shipment ID. When you associate these attributes with a message type in a message flow, Partner Manager extracts this data from the inbound or outbound payload and displays it in the message view of the **Activity** window. From there, you can search for an attribute value, such as a specific PO Number, so you can view every message that has the specified attribute value. ## Create a Custom Message Attribute Use the **** page to create new custom message attributes: 1. In the sidebar, select ****. 2. From the **Custom message attributes** section, click **New**. 3. Enter the attribute alias and label. The alias is used in the reference map that is associated with the message type. The label is used in the message view of the transactions. Both the alias and the label must be unique across the host. 4. To make the attribute searchable on the **Activity** window, select the **Is searchable** checkbox. 5. Repeat these steps for each new attribute you want to define. 6. Click **Save**. ## Associate a Custom Message Attribute with a Message Type To associate a custom message attribute with a message type, include definitions for those attributes in the message type’s reference map. For more information, see [Creating Reference Maps for Message Types](https://docs.mulesoft.com/partner-manager/latest/create-reference-map). ## Dissociate a Custom Message Attribute from a Message Type To dissociate a custom message attribute from a message type, remove it from the message type’s reference map. ## Delete a Custom Message Attribute You can delete custom attributes that are not used in reference maps: 1. In the sidebar, select the ****. 2. In the **Custom message attributes** section, locate the attribute you want to delete. 3. In the row containing the attribute you want to delete, hover over the attribute label, select the trash can that appears, and click **Delete**. ## See Also - [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type) - [Modifying Message Type Settings](https://docs.mulesoft.com/partner-manager/latest/modify-message-type-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # Using Lookup Tables in DataWeave > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use DataWeave lookup utility functions to retrieve values from Partner Manager lookup tables during map execution. To call lookup tables from DataWeave, import the lookup utilities module: ```dwl import * from modules::b2blookuputils ``` ## Function Compatibility by Lookup Table Type Lookup functions are type-specific and can’t be used interchangeably.
FunctionSupported table type

b2bCompositeKeyLookup

Composite Key Lookup only

b2bCrossReferenceLookup

Cross-Reference Lookup only

b2bGenericLookup

Generic-enabled tables only

b2bGenericLookupWithFilter

Generic-enabled tables only

> [!IMPORTANT] If a function is called with an unsupported table type, the lookup call fails. ## Composite Key Lookup Function: `b2bCompositeKeyLookup(tableName, lookupObject, failIfNoMatchFound)` Use this function only with **Composite Key Lookup** table types. ### Parameters
ParameterTypeRequiredDescription

tableName

String

Yes

Lookup table name.

lookupObject

Object

Yes

Key-value pairs where each key is a table column name and each value is the value to match.

failIfNoMatchFound

Boolean (default true)

No

If false, the function returns empty data when no match is found.

### Response
FieldTypeDescription

status

String

Lookup operation status.

errorMessage

String

Error details when the operation fails.

data

Object

Matching row data.

Example: ```dwl %dw 2.0 output application/json import * from modules::b2blookuputils --- b2bCompositeKeyLookup( "B2B-Customer-Order-Profile", {"PARTNER_ID": "PARTNER_001", "CUSTOMER_NAME": "ACME_RETAIL"}, true ) ``` ## Cross-Reference Lookup Function: `b2bCrossReferenceLookup(tableName, columnName, columnValue, failIfNoMatchFound)` Use this function only with **Cross-Reference Lookup** table types. ### Parameters
ParameterTypeRequiredDescription

tableName

String

Yes

Lookup table name.

columnName

String

Yes

Key column name.

columnValue

String

Yes

Value to search in the key column.

failIfNoMatchFound

Boolean (default true)

No

If false, the function returns empty data when no match is found.

### Response
FieldTypeDescription

status

String

Lookup operation status.

errorMessage

String

Error details when the operation fails.

data

Object

Matching row data.

Example: ```dwl %dw 2.0 output application/json import * from modules::b2blookuputils --- b2bCrossReferenceLookup("Item_Code_Mapping", "Internal_SKU", "SKU-5520", true) ``` ## Generic Lookup Function: `b2bGenericLookup(tableName, failIfNoMatchFound)` Use this function only with tables where generic lookup is enabled. ### Parameters
ParameterTypeRequiredDescription

tableName

String

Yes

Lookup table name.

failIfNoMatchFound

Boolean (default true)

No

If false, the function returns empty data when no match is found.

### Response
FieldTypeDescription

status

String

Lookup operation status.

errorMessage

String

Error details when the operation fails.

data

Array<Object>

Entire table data.

Example: ```dwl %dw 2.0 output application/json import * from modules::b2blookuputils --- b2bGenericLookup("Payment_Terms_Mapping", true) ``` ## Generic Lookup with Filter Function: `b2bGenericLookupWithFilter(tableName, lookupObject, failIfNoMatchFound)` Use this function only with tables where generic lookup is enabled. ### Parameters
ParameterTypeRequiredDescription

tableName

String

Yes

Lookup table name.

lookupObject

Object

Yes

Key-value pairs used as filters.

failIfNoMatchFound

Boolean (default true)

No

If false, the function returns empty data when no match is found.

### Response
FieldTypeDescription

status

String

Lookup operation status.

errorMessage

String

Error details when the operation fails.

data

Array<Object>

One or more rows matching the provided filters.

Example: ```dwl %dw 2.0 output application/json import * from modules::b2blookuputils --- b2bGenericLookupWithFilter( "Payment_Terms_Mapping", {"Internal_Terms_Code": "NET30", "Salesforce_Payment_Term": "Net 30"}, true ) ``` > [!TIP] If a transformation requires multiple lookups from the same table, retrieve table data once > with `b2bGenericLookup` and then filter locally in DataWeave. For lookup table concepts and type selection guidance, see [Configuring and Managing Lookup Tables](https://docs.mulesoft.com/partner-manager/latest/lookup-tables-overview). --- product: Partner Manager version: 2.x is-latest-version: true --- # X12 - ISA Identifier Values > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Refer to this information specifically for using ISA with X12.
SettingDescriptionRequired

Qualifier

The following Qualifier types are available with Anypoint Partner Manager:

  • 01 (DUNS Number)

  • 02 (SCAC - Standard Carrier Alpha Code)

  • 03 (FMC - Federal Maritime Commission)

  • 04 (IATA - International Air Transport Association)

  • 07 (Global Location Number (GLN))

  • 08 (UCC EDI Number)

  • 09 (X.121)

  • 10 (DoD - Department of Defense Activity Address Code)

  • 11 (DEA - Drug Enforcement Administration)

  • 12 (Phone Number)

  • 13 (UCS Code)

  • 14 (DUNS Number and Suffix Number)

  • 15 (Petroleum Accountants Society of Canada Company Code)

  • 16 (DUNS Number with a Four Character Suffix)

  • 17 (American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit))

  • 18 (Association of American Railroads (AAR) Standard Distribution Code)

  • 19 (EDI Council of Australia Communications ID)

  • 20 (HIN - Health Industry Number)

  • 21 (Integrated Postsecondary Education Data System, or (IPEDS))

  • 22 (Federal Interagency Commission on Education, or FICE)

  • 23 (National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes, or NCES)

  • 24 (The College Board’s Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ATP)

  • 25 (ACT, Inc. 4-Digit Code of Postsecondary Institutions.)

  • 26 (Statistics of Canada List of Postsecondary Institutions)

  • 27 (Carrier Identification Number)

  • 28 (Fiscal Intermediary Identification Number)

  • 29 (Medicare Provider and Supplier Identification Number)

  • 30 (U.S. Federal Tax Identification Number)

  • 31 (Jurisdiction Identification Number Plus 4)

  • 32 (U.S. Federal Employer Identification Number (FEIN))

  • 33 (National Association of Insurance Commissioners Company Code (NAIC))

  • 34 (Medicaid Provider and Supplier Identification Number)

  • 35 (Statistics Canada Canadian College Student Information System Institution Codes)

  • 36 (Statistics Canada University Student Information System Institution Codes)

  • 37 (Society of Property Information Compilers and Analysts)

  • 38 (The College Board and ACT, Inc. 6-Digit Code List of Secondary Institutions)

  • AM (Association Mexicana del Codigo de Producto (AMECOP) Communication ID)

  • NR (NRMA - National Retail Merchants Association)

  • SA (User Identification Number)

  • SN (Standard Address Number)

  • ZZ (Mutually Defined)

Yes

Identifier value

EDI X12-ISA ID for your partner; can be up to 15 characters. Your partner should supply you with the proper EDI X12 Interchange Sender and Receiver IDs.

Yes

## X12 - GS Values Refer to this information specifically for using GS with X12.
SettingDescriptionRequired

Identifier Value

EDI X12-GS ID for your partner; can be up to 15 characters. Your partner should supply you with the proper EDI X12 Group Sender/Receiver ID.

Yes

## DUNS Refer to this information specifically for using the DUNS number as an identifier.
SettingDescriptionRequired

Identifier Value

The DUNS number for your partner. The DUNS number is a nine-digit number that your partner supplies that corresponds to the Sender/Receiver ID.

Yes

## AS2 Identity Refer to this information specifically for using the AS2 identity to identify a partner.
SettingDescriptionRequired

Identifier Value

The AS2 identity for your partner. Your partner should supply you with the proper Sender/Receiver AS2 identity.

Yes

## Delete Identifiers You might want to delete an identifier when it is no longer needed. Deleting an existing host or partner identifier impacts the identification and routing of B2B messages to the associated partner. Remember that there must always be at least one identifier per message flow. Ask yourself the following when deleting an identifier: Why do you want to delete it? Do you need to replace it with another identifier? After successfully deleting an identifier, you can create a new identifier with the same value as the one you deleted. If you need to replace the identifier you are deleting, record the values and qualifier type needed. 1. In the sidebar, select **Partners**. 2. In the **Identifiers** section, hover over the identifier that you want to delete and click the trash can icon that appears in the right-hand side of the row. 3. If you need a replacement identifier, you can add it now by clicking **New**. ## See Also - [X12 Settings - Receive from Partner](https://docs.mulesoft.com/partner-manager/latest/x12-receive-read-settings) --- product: Partner Manager version: 2.x is-latest-version: true --- # You cannot deploy this message flow because the payload storage is not properly configured > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## Cause You have not configured the Payload Storage. ## Solutions If your payload storage is configured, verify that it is active: 1. From within Anypoint Partner Manager, select your `hostname` profile. 2. Scroll down to Payload storage and click **Edit**. 3. Review your payload storage configuration and status. 4. If your payload storage is not configured, configure it as described in [Configuring a Payload Storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api).