---
schema_version: "1"
id: cb37a2ed0250399ed34944e885deca9d8126c3f27273fadd8c0246a40de2e994
title: Anypoint Partner Manager Setup Guide
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/salesforce-oms/latest/anypoint-partner-manager-setup-guide.md
canonical_url: https://docs.mulesoft.com/salesforce-oms/latest/anypoint-partner-manager-setup-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 88c4f7b3e28a39d3c227f908daa03221b73cdad26553c4e0e24f04528f784f20
description: MuleSoft Documentation Site
release: "1.1"
latest: true
---
---
product: Salesforce OMS
version: 1.1
is-latest-version: true
---

# Anypoint Partner Manager Setup Guide

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To configure Anypoint Partner Manager, follow the Postman collection instructions in the
[Accelerators B2B Common Resources](https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-b2b-common-resources-src/)
project.

The collection creates the following configurations:

- Endpoints, message types, and custom message attributes

- Partners

- Message flows

Once the collection runs successfully, go to Partner Manager in Anypoint Platform and verify that
the configurations were created successfully.

## Run the Postman Collection

Use the Partner Manager setup collection in the
[Accelerator B2B Common Resource](https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-b2b-common-resources-src/)
project to configure message flows and their components in Partner Manager for the Accelerator for
Salesforce OMS solution.

To run the collection, you must set the following variables:

<table><colgroup><col> <col></colgroup><thead><tr><th>Property Name</th><th>Description</th></tr></thead><tbody><tr><td><p>env_identifier_x12-isa-zz_id</p></td><td><p>The ID of the identifier type X12-ISA-ZZ.</p></td></tr><tr><td><p>env_identifier_x12-gs_id</p></td><td><p>The ID of the identifier type X12-GS for partner.</p></td></tr><tr><td><p>env_identifier_ref-id_id</p></td><td><p>The ID of the identifier type Reference ID. This is static across all the organizations.</p></td></tr><tr><td><p>http_endpoint_type_id</p></td><td><p>The <code>endpointTypeId</code> of an HTTPS endpoint type. The value is the same across all environments. Note that you can find the <code>endpointTypeId</code> value by opening the details of an endpoint in Partner Manager, and then running a request from the <strong>Network</strong> tab in the developer view of your browser. The value is available from the <strong>Preview</strong> tab of the run result.</p></td></tr><tr><td><p>host_anypoint_org</p></td><td><p>The host name of the Anypoint Platform organization.</p></td></tr><tr><td><p>devx.orgid</p></td><td><p>The ID of the Anypoint Platform organization.</p></td></tr><tr><td><p>devx.envid</p></td><td><p>The ID of the environment in the Anypoint Platform organization.</p></td></tr><tr><td><p>partner_x12_isa_identifier_value</p></td><td><p>The value of the partner identifier type X12-ISA-ZZ. This example uses <code>ORANGE</code>.</p></td></tr><tr><td><p>partner_reference_id_identifier_value</p></td><td><p>The value of the partner identifier type Reference ID. This example uses <code>ORANGE</code>.</p></td></tr><tr><td><p>partner_x12_gs_identifier_type_value</p></td><td><p>The value of the partner identifier type X12 - GS. This example uses <code>ORANGE</code>.</p></td></tr><tr><td><p>host_x12_isa_identifier_value</p></td><td><p>The value of the host identifier type X12-ISA-ZZ. This example uses <code>MYTHICAL</code>.</p></td></tr><tr><td><p>host_reference_id_identifier_value</p></td><td><p>The value of the host identifier type Reference ID. This example uses <code>MYTHICAL</code>.</p></td></tr><tr><td><p>host_x12_gs_identifier_type_value</p></td><td><p>The value of the host identifier type X12 - GS. This example uses <code>MYTHICAL</code>.</p></td></tr><tr><td><p>b2b_orders_process_api_host_name</p></td><td><p>The host name of the B2B Orders Process API.</p></td></tr><tr><td><p>b2b_orders_prc_api_orders_path</p></td><td><p>The URI path for <code>Orders</code> in the B2B Orders Process API.</p></td></tr><tr><td><p>b2b_storage_sys_api_host_name</p></td><td><p>The host name of the B2B Storage System API.</p></td></tr><tr><td><p>b2b_erp_prc_api_host_name</p></td><td><p>The host name of the ERP Process API. This example uses the B2B Simulator Process API.</p></td></tr><tr><td><p>b2b_erp_prc_api_invoices_path</p></td><td><p>The URI path for Invoices in the ERP Process API. This example uses the B2B Simulator Process API.</p></td></tr><tr><td><p>b2b_orders_prc_api_payments_path</p></td><td><p>The URI path for Payments in the B2B Orders Process API.</p></td></tr><tr><td><p>b2b_erp_prc_api_acknowledgements_path</p></td><td><p>The URI path for Acknowledgments in the ERP Process API. This example uses the B2B Simulator Process API.</p></td></tr><tr><td><p>partner_name</p></td><td><p>The name of the partner.</p></td></tr><tr><td><p>partner_description</p></td><td><p>The description of the partner.</p></td></tr><tr><td><p>partner_website_url</p></td><td><p>The website URL of the partner.</p></td></tr></tbody></table>

## See Also

- [Prerequisites](https://docs.mulesoft.com/salesforce-oms/latest/prerequisites)

- [MuleSoft Accelerator for Salesforce OMS](https://docs.mulesoft.com/salesforce-oms/latest/)