Partner Manager Architecture
With Anypoint Partner Manager, you can deploy B2B integration message flows to a MuleSoft-hosted CloudHub iPaaS platform or an Anypoint Runtime Fabric instance.
The functional features and user experience in configuring B2B integrations with Partner Manager are deployment-target agnostic; however, differences in the underlying architecture when implementing the functionality in the runtime occur.
When you deploy a configured message flow, Partner Manager automatically transforms the configurations used in the message flow. It then deploys and updates a set of applications necessary to orchestrate end-to-end B2B processing to the Mule instance. These applications include:
-
Receive endpoint services
-
Document processing service
-
Replication service
-
Send endpoint services
| Callout | Name | Description |
|---|---|---|
|
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 |
|
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 |
|
Document Processing Service |
Core B2B processing engine responsible for parsing, validating, and translating received B2B messages based on configurations and mapping in Partner Manager |
|
API Replication Service |
Tracking service responsible for updating transmissions and transaction activities to the control plane and the payload storage API |
|
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 |
|
Payload Storage API |
API to store B2B payload data in your storage solution |
Partner Manager for CloudHub
When deploying B2B integration message flows to CloudHub, Anypoint MQ uses queues between processing stages to add additional reliability to B2B message processing.
As of the first deployment from Partner Manager, runtime applications deploy to the CloudHub region specified in the business group’s default settings in Runtime Manager by default. Anypoint MQ queues automatically generate during the deployment process in the same or the nearest available region. Any new runtime applications deploy to the same region as the first deployment.
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.
