Contact Free trial Login

Examples

Current Anypoint Partner Manager solutions will continue to be supported in accordance with the Product Support and Maintenance Terms but will not be available for new customers or upgrades. Contact your MuleSoft representative for more information on MuleSoft’s B2B solutions.

This page identifies examples of Anypoint Partner Manager in use.

For conceptual information, see Key Concepts.

For information about the procedures you would use to implement a given example, see Configure Trading Partners and Transaction Monitoring.

End-to-End Use Case

In this example, a user performs a series of configuration tasks in APM and Anypoint Studio, resulting in the ability to view events and track transmissions.

In APM

  • Enter home organization settings

  • Enter external trading partner settings

In Anypoint Studio

  1. Create your flow.

  2. Configure the Partner Manager Connector.

  3. Configure Partner Manager-enabled connectors to use the Partner Manager Connector.

  4. Use standard MuleSoft connectors and processors to complete the processing and integration of the message into downstream systems as required.

Back in APM

Go to the B2B Transmissions area of APM to view tracked events and messages.

Promotion Scenarios

Current Anypoint Partner Manager solutions will continue to be supported in accordance with the Product Support and Maintenance Terms but will not be available for new customers or upgrades. Contact your MuleSoft representative for more information on MuleSoft’s B2B solutions.

This section identifies common scenarios for promoting partners from one environment to another. For more information, see Promoting a Partner.

In each of these scenarios, a trading partner P1 has been created in an environment E1. In the table below, that partner is therefore identified as P1E1.
Another partner P1 has been created in environment E2 (P1E2 below). In some scenarios, P1E2 was created by promoting P1E1 from E1 to E2.

In the last scenario, an additional trading partner P2 has been created in environment E2 (P2E2 below).

Scenario Override
Certificates
Checkbox
Keep
Identifiers
Checkbox
Result

P1E1 has previously been promoted to P1E2

Selected

Either selected or not selected

If P1E1 contains any new cerfificates, they will be copied to P1E2

Not Selected

Either selected or not selected

P1E1 will not be copied to P1E2

P1E1 and P1E2 were identical at some point, but a set of identifiers (types and values) has subsequently been configured for AS2, EDI X12 and EDIFACT in P1E1.

Either selected or not selected

Selected

P1E1 identifiers will be copied to P1E2 because the copied data may need information associated with the identifiers (for example Endpoints, or Document Definitions)

Not selected

P1E1 identifiers will be copied to P1E2 because the copied data may need information associated with the identifiers (for example Endpoints, or Document Definitions)

P1E1 and P1E2 were identical at some point, but a set of identifiers (types and values) has subsequently been configured for AS2, EDI X12 and EDIFACT in P1E1 and in addition, E2 has another partner (say, P1E3) that coincidentally has the same identifiers (that is, types & values) as P1E2.

Either selected or not selected

Promotion fails, because having the same set of identifiers (types and values) more than once causes an error.

P1E1 and P1E2 were identical at some point. Subsequently, a set of identifiers (types and values) has been configured for AS2, EDI X12 and EDIFACT in P1E1 and a different set of identifiers (types and values) has been configured for AS2, EDI X12 and EDIFACT in P1E2.

Selected

P1E1 values replace P1E2 values.

Not selected

P1E2 values are not replaced.

P1E1 has a set of identifiers (types and values) for AS2, EDI X12 and EDIFACT.
P2E2, for whatever reason, has exactly the same set of identifiers as P1E1.

Either selected or not selected

Promotion fails, because having the same set of identifiers (types and values) more than once (that is, in both P1E2 and P2E2) causes an error.