Nav

Partner Manager Connector

This page provides information about the Partner Manager Connector (PMC), including:

Overview

PMC provides connectivity to Anypoint Partner Manager (APM). The connector allows the management of APM-enabled connectors from APM and tracking of B2B exchanges.

Installing the Connector

Follow the steps below to install the PMC in Anypoint Studio.

  1. On the Help menu in Anypoint Studio, select Install New Software…​ to bring up the Available Software dialog box.

  2. Press the Add…​ button, next to the Work with selection box, to add the PMC’s update site.

  3. Once added, expand the Premium drop-down and choose Partner Manager Connector.

  4. Click Next >. The Install Details page appears.

  5. Review the details of the item you selected and click Next >.

  6. Accept terms and conditions of the product and press Finish.

  7. Click Restart Now to complete the installation.

Configuring the Connector

Configuration without file persistence

  1. From Anypoint Studio, select the Global Elements view and press Create.

  2. Enter Partner Manager in the filter.

  3. Choose Basic Configuration and click OK.

  4. In the API Key attribute, enter your private API key which is generated from APM portal.

  5. Enter in the Environment ID attribute the CloudHub environment you want PMC to run in.

  6. Press OK.

Configuration using Amazon S3 for file persistence

  1. From Anypoint Studio, select the Global Elements view and press Create.

  2. Enter Partner Manager in the filter.

  3. Choose Amazon S3 File Storage and click OK.

  4. In the API Key attribute, enter your private API key which is generated from APM portal.

  5. Enter in the Environment ID attribute the CloudHub environment you want PMC to run in.

  6. Enter the settings of the S3 bucket to be used for storing files. These settings are obtained from your AWS console.

  7. Press OK.

Configuration using a Mule flow for file persistence

  1. From Anypoint Studio, select the Global Elements view and press Create.

  2. Enter Partner Manager in the filter.

  3. Choose Custom File Storage and click OK.

  4. In the API Key attribute, enter your private API key which is generated from APM portal.

  5. Enter in the Environment ID attribute the CloudHub environment you want PMC to run in.

  6. Type in the name of the flow to be used for persisting files in the Flow Name attribute.

  7. Optionally, inside the File URL attribute, set a MEL expression to read the file URL from the message produced by the flow.

  8. Press OK.

Supported Operations

The connector supports the following operations:

Track Transmission

Track transmissions originating from sources other than APM-enabled connectors like the filesystem. User-defined metadata can also be tracked as part of the transmission. The connector expects metadata to be a java.util.Map. Nested maps represent nested metadata. You have the option to define the map inline via the Object Browser, or alternatively, specify from the attribute its location in the Mule message. The reserved key "label" can be used in metadata to label a transmission. A transmission label allows you to easily distinguish between different transmissions in APM portal.

Track Document

Track documents like XML documents. The Document attribute must be set accordingly for APM to inspect the document and perform tasks such as property extraction. User-defined metadata can also be tracked as part of the document. The connector expects metadata to be a java.util.Map. Nested maps represent nested metadata. You have the option to define the map inline via the Object Browser, or alternatively, specify from the attribute its location in the Mule message. The reserved key "label" can be used in metadata to label a document. A document label allows you to easily distinguish between different documents in APM portal.

Track Error

Track errors originating from the processing of transactions, documents, transmissions, or business processes. The origin of the error is selected from source attribute and the ID identifying the source is set in the Source ID attribute.

Resolve Routes

Fetch routes that have a source channel matching the document type and transport type. An empty java.util.List is returned if no routes could be found.

Start Transactions Replay

Fetch replayable transactions and set them as replaying. Replaying transactions that have timed out and are identified as such through the Replaying Timeout attribute are included with the result set.

End Transactions Replay

Mark transactions, identified by the entered list of transaction IDs, as replayed.

Search a resource using APM’s query language.