Getting Started with Partner Manager

For each environment, use access management to assign permissions to each Partner Manager user. You can assign the following permissions:

For more information, see Permissions Available in Anypoint Platform.

You can deploy Partner Manager runtime applications to either CloudHub 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.

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.

Use the <host> 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.

A partner profile consists of partner-specific settings such as:

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.

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.

Message flows contain the following components, which execute end-to-end B2B message processing:

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 and Message Flow Components.

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 and Undeploying Message Flows.

Monitor transmission activity by searching for transactions based on criteria such as the:

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:

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, Using Custom Message Attributes with Message Types, and Tracking Individual Messages.

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.