Anypoint Partner Manager Architecture

With Anypoint Partner Manager, you can deploy B2B integration message flows with your partners, either to your own hosted Mule instances or to a MuleSoft-hosted CloudHub iPaaS platform.

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 and 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

Partner Manager high-level architecture
Callout Name Description

pm arch diagram 1

Partner Manager

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

pm arch diagram 2

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

pm arch diagram 3

Document Processing Service

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

pm arch diagram 4

API Replication Service

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

pm arch diagram 5

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 trading partners via AS2, HTTP, HTTPS, or SFTP

pm arch diagram 6

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.

Deploying Partner Manager on CloudHub

Partner Manager for On-Premises Mule Instances

When deploying B2B integration message flows to your own hosted on-premises Mule instance, the instance uses HTTP calls between processing stages during B2B message processing.

Runtime applications deployed to the server group (B2BServerGroup) contain configured data in your data center or private cloud.

Deploying Partner Manager on-premises

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub