---
schema_version: "1"
id: 4710246a1ff20b12b30106f54135885d5bf2d351baedc606f7a9026434a2e1fc
title: Partner Manager Deployment Architecture
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/partner-manager-architecture.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/partner-manager-architecture
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 6ab3e06de022c08963ce1ddc03df02c7eb7c962a96fcf6532ccdd26c701e9d79
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
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)

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Callout</th><th>Name</th><th>Description</th></tr></thead><tbody><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-1.png" alt="A circle with a number 1 inside"></span></p></td><td><p>Partner Manager</p></td><td><p>MuleSoft-hosted cloud control plane enabling users to configure partner profiles, build and deploy B2B integration message flows, and monitor B2B transaction activity</p></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-2.png" alt="A circle with a number 2 inside"></span></p></td><td><p>Receive Endpoint Services</p></td><td><p>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</p></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-3.png" alt="A circle with a number 3 inside"></span></p></td><td><p>Document Processing Service</p></td><td><p>Core B2B processing engine responsible for parsing, validating, and translating received B2B messages based on configurations and mapping in Partner Manager</p></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-4.png" alt="A circle with a number 4 inside"></span></p></td><td><p>API Replication Service</p></td><td><p>Tracking service responsible for updating transmissions and transaction activities to the control plane and the payload storage API</p></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-5.png" alt="A circle with a number 5 inside"></span></p></td><td><p>Send Endpoint Services</p></td><td><p>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</p></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-6.png" alt="A circle with a number 6 inside"></span></p></td><td><p>Payload Storage API</p></td><td><p>API to store B2B payload data in your storage solution</p></td></tr></tbody></table>

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