---
schema_version: "1"
id: e162cde410b5db5c8360412ff929527633afae4cf727f53ddf0bbc31b82abb31
title: Configuring CloudHub 2.0 Deployment Settings
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/cloudhub2-deployment-settings.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/cloudhub2-deployment-settings
source_site: docs.mulesoft.com
content_type: documentation
content_hash: b983d0cdb3894b307286c8565982024fef227ca6e8f2343946f4189966c153e0
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Configuring CloudHub 2.0 Deployment Settings

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

To configure settings for deploying Anypoint Partner Manager to CloudHub 2.0, access the business
unit and environment for which you want to deploy Partner Manager and then follow these steps:

1.  From the Access Management **Configure a Partner Manager environment** window, enter these
    general settings:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th></tr></thead><tbody><tr><td><p>Deployment Target Type</p></td><td><p>Target type for your Partner Manager deployment. Select <strong>CloudHub 2.0</strong>.</p></td><td><p>None</p></td></tr><tr><td><p>Runtime Version</p></td><td><p>Mule runtime engine version to run Partner Manager applications.</p></td><td><div><div><p>4.6.0 LTS using Java 8</p></div><div><div data-type="NOTE">If you select Mule runtime 4.9.0 LTS using Java 17, test your component versions and SFTP connections that rely on insecure ciphers to make sure they work as expected with Java 17.</div></div></div></td></tr><tr><td><p>Min Mule Version override</p></td><td><p>Minimum Mule runtime version required to deploy the runtime applications.</p><p>Configuring the Min Mule version enables you to apply a <a href="https://docs.mulesoft.com/mule-runtime/latest/feature-flagging#configure-feature-flags-for-a-mule-application">feature flagging</a> mechanism for Partner Manager-deployed Mule runtime applications.</p><p>If you process cXML messages with &lt;DOCTYPE&gt; tags, you must set the <code>minMuleVersion</code> to 4.5.0 or higher. If you’re migrating from an earlier version, you must perform end-to-end regression testing on your existing workflows before changing the <code>minMuleVersion</code>.</p></td><td><div><div><p>None (Uses 4.3.0)</p></div><div><div data-type="NOTE">If you select <code>None</code>, Partner Manager defaults to using <code>4.3.0</code> as the Min Mule version.</div></div></div></td></tr><tr><td><p>Payload compression</p></td><td><p>Select not to compress the payload, always compress the payload, or adaptively compress the payload only when Anypoint MQ fails because the payload size exceeds a certain threshold.</p></td><td><p>None (not compressed)</p></td></tr><tr><td><p>Deployment Target</p></td><td><p>Shared or private space to which you want to deploy Partner Manager runtime applications. You can change the deployment target after all active message flows are no longer deployed to an existing target. To change the region in these instances, undeploy the message flows, change the region, and then redeploy the message flows.</p></td><td><p>None</p></td></tr><tr><td><p>Einstein enabled</p></td><td><p>Enables Einstein features in Partner Manager, such as the <a href="https://docs.mulesoft.com/partner-manager/latest/activity-message-tracking#message-summaries">message summarization</a> feature for source and target payloads.</p></td><td><p>Not selected</p></td></tr></tbody></table>

2.  Select **Applications** and enter these application settings:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th></tr></thead><tbody><tr><td><p>Each B2B endpoint</p></td><td><div><div><p>Reserved CPU space, CPU space limit, and memory capacity for each Partner Manager endpoint application. Partner Manager deploys a generic Mule app to the runtime for each endpoint protocol and direction (receive or send) combination.</p></div><div><div data-type="NOTE">Partner manager deploys each AS2 and HTTPS inbound endpoint configuration as a separate Mule application. You can reuse the same endpoint configuration across multiple partners and message types.</div></div></div></td><td><p>0.1 vCores</p></td></tr><tr><td><p>B2B API Replication Service</p></td><td><p>Reserved CPU space, CPU space limit, and memory capacity for the B2B API Replication Service.</p></td><td><p>0.2 vCores</p></td></tr><tr><td><p>B2B Document Processing Service</p></td><td><p>Reserved CPU space, CPU space limit, and memory capacity for the B2B Document Processing Service.</p></td><td><p>0.2 vCores</p></td></tr></tbody></table>

    For help with sizing, contact your MuleSoft Account Team.

3.  Click **Save**.

## See Also

[Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/partner-manager/latest/deploy-partner-manager)