From 44c35c9ed379b4bc9193476f315996d1d4187e0c Mon Sep 17 00:00:00 2001 From: Tasha Date: Mon, 29 Sep 2025 12:22:24 -0500 Subject: [PATCH 01/13] Create ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 40 +++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 modules/ROOT/pages/ch2-migration.adoc diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc new file mode 100644 index 00000000..44412d9e --- /dev/null +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -0,0 +1,40 @@ += Partner Manager CloudHub 2.0 Migration Guide + +To migrate your B2B operations from CloudHub 1.0 to the more advanced CloudHub 2.0, follow the relevant path in this guide based on your deployment scenario. + +== Before You Begin + +For customers deploying with a Virtual Private Cloud (VPC) and Dedicated Load Balancer (DLB), start by following the prerequisite steps in xref:cloudhub::vpc-upgrade.adoc[]. + +== Migration With VPC and DLB with URL Preservation + +=== Preparation and Initial Setup + +. Use the VPC to Private Space Migration Tool to create your new Private Space in CloudHub 2, which is your deployment environment. +. Stop all inbound applications in CloudHub 1 and ensure no in-flight messages remain in the system. +. Delete all applications from your CloudHub 1 environment, except for your `inbound-as2` and `inbound-http` apps. These apps are critical for maintaining URL continuity and are used in the migration process. + +=== Migration to CloudHub 2 + +. Using the new API endpoint, which is available in Mule runtime 2.24, change the deployment target for your applications from CloudHub 1 to CloudHub 2. +. In Access Management, select the Private Space you created in the previous step. +. Start the `inbound-as2` and `inbound-http` applications in CloudHub 1, which must be in a Running status. Incoming messages are queued temporarily in Anypoint MQ. +. Use the CloudHub 1 to CloudHub 2 Migration Tool to perform an upgrade deployment of the `inbound-as2` and `inbound-http` applications. This process creates the applications' counterparts in CloudHub 2 with the same name but using a dummy jar, preserving their ingress URLs. At this point, traffic is 100% on CloudHub 1. +. In Partner Manager, either apply runtime settings or upgrade your applications. This action triggers the Partner Manager Orchestration service to deploy and update the `inbound-as2` and `inbound-http` applications in CloudHub 2. + +=== Traffic Cutover and Finalization + +. Keep the `inbound-as2` and `inbound-http` apps in CloudHub 1 running to handle all current traffic while you test the functionality of the new CloudHub 2 apps. +. In Runtime Manager, incrementally increase the traffic percentage to the CloudHub 2 applications over a period of a few days to allow for a smooth, controlled transition. +. Once you're confident, increase the traffic to 100% on CloudHub 2. +. Shut down the CloudHub 1 applications. +. Once you've stopped all CloudHub 1 apps that use the DLB, failover the DLB domain (anypointdns.net) to point to CloudHub 2. +. Delete the DLB in CloudHub 1. + +From this point on, any new message flow deployments you make in Partner Manager only update the applications in your CloudHub 2 environment. + +== Migration With VPC and DLB but Without URL Preservation + + + +== SLB Migration to a Private Space \ No newline at end of file From 4882e05129bad7ed2190ea95a20642e68fd41a40 Mon Sep 17 00:00:00 2001 From: Tasha Date: Thu, 9 Oct 2025 11:07:08 -0500 Subject: [PATCH 02/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 113 +++++++++++++++++++++----- 1 file changed, 92 insertions(+), 21 deletions(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 44412d9e..33f05ce3 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -8,33 +8,104 @@ For customers deploying with a Virtual Private Cloud (VPC) and Dedicated Load Ba == Migration With VPC and DLB with URL Preservation -=== Preparation and Initial Setup +. Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[CloudHub VPC to CloudHub 2.0 Private Space Upgrade] page to upgrade your CloudHub 1.0 (CH1) Virtual Private Cloud (VPC) to a CloudHub 2.0 (CH2) private space. +. In Runtime Manager: +.. Stop all inbound Partner Manager applications deployed to CH1. +.. Make sure you don't have any inflight messages. +.. Delete these Partner Manager deployed applications but not the `inbound-as2` and `inbound-http` applications: +... b2b-outbound-* +... b2b-document-processing-service-* +... b2b-api-replication-service-* +. On the Partner Manager tab in Access Management > Business Groups: +.. Click *Edit Configuration* for the environment you want to update. +.. Select CloudHub 2.0 and from the *Deployment Target Type* dropdown. +.. In the *Deployment Target* dropdown, select the private space that was configured previously. +.. Before saving, open your browser's developer tools and navigate to the *Network* tab and make sure the Method column is enabled. +.. Click *Save* in Access Management. +.. Check the *I understand the effects of this action* box, and then click *Save*. Ignore the error message about the target runtime type. +. In Developer Tools: +.. Right-click on the most recent PUT request, hover over *Copy* and select *Copy as CURL*. +.. Paste the CURL command into your preferred API Client, such as Postman. Set *forceUpdate* to True by updating the URL. +.. Send the PUT request. +. In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. +. In Runtime Manager, start the `inbound-as2` and `inbound-http` applications. +[NOTE] +Incoming messages are delivered to Anypoint MQ but aren't processed until the CH1 app is running. For the app switching to work, ensure the CH1 app is in a Running state. -. Use the VPC to Private Space Migration Tool to create your new Private Space in CloudHub 2, which is your deployment environment. -. Stop all inbound applications in CloudHub 1 and ensure no in-flight messages remain in the system. -. Delete all applications from your CloudHub 1 environment, except for your `inbound-as2` and `inbound-http` apps. These apps are critical for maintaining URL continuity and are used in the migration process. +. Use the CH1 to CH2 migration tool xref:cloudhub::app-migration.adoc[] to upgrade the deployment for the `inbound-as2` applications and `inbound-https` applications, which creates their counterparts in CH2. +.. Make sure the name remains the same. +.. Use a dummy jar file with the same name, dummy jar. +.. Preserve the ingress urls. Initially, the name resolution 0% CH2, 100% CH1. +. On the Message Flows tab in Partner Manager: +.. Click Manage Deployments and choose either Upgrade deployments or Apply environment settings. +.. Check the *I understand the effects of these actions*, and then click *Confirm*. ++ +Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files the apps in CH2. ++ +Before shifting any traffic, keep the CH1 inbound AS2 and HTTP applications running and handling 100% of traffic to confirm their functioning as expected post-migration. +. In Runtime Manager, increase the traffic on the CH2 app incrementally over a period of a few days to 100%. Keep the CH1 apps in a Shutdown status after traffic reaches 100%. +. After you've stopped all CH1 applications that use the DLB, failover the DLB domain (anypointdns.net) to CH2 and delete the DLB. -=== Migration to CloudHub 2 +New message flow deployments in Partner Manager beyond this point only update the CH2 apps. -. Using the new API endpoint, which is available in Mule runtime 2.24, change the deployment target for your applications from CloudHub 1 to CloudHub 2. -. In Access Management, select the Private Space you created in the previous step. -. Start the `inbound-as2` and `inbound-http` applications in CloudHub 1, which must be in a Running status. Incoming messages are queued temporarily in Anypoint MQ. -. Use the CloudHub 1 to CloudHub 2 Migration Tool to perform an upgrade deployment of the `inbound-as2` and `inbound-http` applications. This process creates the applications' counterparts in CloudHub 2 with the same name but using a dummy jar, preserving their ingress URLs. At this point, traffic is 100% on CloudHub 1. -. In Partner Manager, either apply runtime settings or upgrade your applications. This action triggers the Partner Manager Orchestration service to deploy and update the `inbound-as2` and `inbound-http` applications in CloudHub 2. -=== Traffic Cutover and Finalization - -. Keep the `inbound-as2` and `inbound-http` apps in CloudHub 1 running to handle all current traffic while you test the functionality of the new CloudHub 2 apps. -. In Runtime Manager, incrementally increase the traffic percentage to the CloudHub 2 applications over a period of a few days to allow for a smooth, controlled transition. -. Once you're confident, increase the traffic to 100% on CloudHub 2. -. Shut down the CloudHub 1 applications. -. Once you've stopped all CloudHub 1 apps that use the DLB, failover the DLB domain (anypointdns.net) to point to CloudHub 2. -. Delete the DLB in CloudHub 1. +== Migration With VPC and DLB but Without URL Preservation -From this point on, any new message flow deployments you make in Partner Manager only update the applications in your CloudHub 2 environment. +. Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[CloudHub VPC to CloudHub 2.0 Private Space Upgrade] page to upgrade your CloudHub 1.0 (CH1) Virtual Private Cloud (VPC) to a CloudHub 2.0 (CH2) private space. +. In Runtime Manager: +.. Stop all inbound Partner Manager applications deployed to CH1. +.. Make sure you don't have any inflight messages. +.. Delete these Partner Manager deployed applications: +... b2b-inbound-* +... b2b-outbound-* +... b2b-document-processing-service-* +... b2b-api-replication-service-* +. On the Partner Manager tab in Access Management > Business Groups: +.. Click *Edit Configuration* for the environment you want to update. +.. Select CloudHub 2.0 and from the *Deployment Target Type* dropdown. +.. In the *Deployment Target* dropdown, select the private space that was configured previously. +.. Before saving, open your browser's developer tools and navigate to the *Network* tab and make sure the Method column is enabled. +.. Click *Save* in Access Management. +.. Check *I understand the effects of this action*, and then click *Save*. Ignore the error message about the target runtime type. +. In Developer Tools: +.. Right-click on the most recent PUT request, hover over *Copy* and select *Copy as CURL*. +.. Paste the CURL command into your preferred API Client, such as Postman. Update the URL so that *forceUpdate* is set to True. +.. Send the PUT request. +. In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. +. On the Message Flows tab in Partner Manager: +.. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. +.. Check the *I understand the effects of these actions*, and then click *Confirm*. ++ +Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files the apps in CH2. -== Migration With VPC and DLB but Without URL Preservation +New message flow deployments in Partner Manager beyond this point only update the CH2 apps. +== SLB Migration to a Private Space +. In Runtime Manager: +.. Stop all inbound Partner Manager applications deployed to CH1. +.. Make sure you don't have any inflight messages. +.. Delete these Partner Manager deployed applications: +... b2b-inbound-* +... b2b-outbound-* +... b2b-document-processing-service-* +... b2b-api-replication-service-* +. On the Partner Manager tab in Access Management > Business Groups: +.. Click *Edit Configuration* for the environment you want to update. +.. Select CloudHub 2.0 and from the *Deployment Target Type* dropdown. +.. In the *Deployment Target* dropdown, select the private space or shared space. +.. Before saving, open your browser's developer tools and navigate to the *Network* tab and make sure the Method column is enabled. +.. Click *Save* in Access Management. +.. Check the *I understand the effects of this action* box, and then click *Save*. Ignore the error message about the target runtime type. +. In Developer Tools: +.. Right-click on the most recent PUT request, hover over *Copy* and select *Copy as CURL*. +.. Paste the CURL command into your preferred API Client, such as Postman. Update the URL so that *forceUpdate* is set to True. +.. Send the PUT request. +. In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. +. On the Message Flows tab in Partner Manager: +.. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. +.. Check the *I understand the effects of these actions*, and then click *Confirm*. ++ +Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files the apps in CH2. -== SLB Migration to a Private Space \ No newline at end of file +New message flow deployments in Partner Manager beyond this point only update the CH2 apps. From 33f8f2a7bdb0ec3f7c0cd47b74a6f2ab9408fde5 Mon Sep 17 00:00:00 2001 From: Tasha Date: Thu, 9 Oct 2025 11:15:04 -0500 Subject: [PATCH 03/13] Update nav.adoc --- modules/ROOT/nav.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index c1cd5391..d9c7c3d0 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -3,6 +3,7 @@ * xref:partner-manager-release-notes.adoc[Release Notes] * xref:get-started.adoc[Getting Started with Partner Manager] * xref:partner-manager-architecture.adoc[Partner Manager Architecture] +* xref:ch2-migration.adoc[Partner Manager CloudHub 2.0 Migration Guide] * xref:setup.adoc[Setting up the Partner Manager Environment] ** xref:deploy-partner-manager.adoc[] ** xref:cloudhub-deployment-settings.adoc[] From 6a78e6d38819d2427f993bba49c9bc6c7ab24c0c Mon Sep 17 00:00:00 2001 From: Tasha Date: Thu, 9 Oct 2025 16:01:57 -0500 Subject: [PATCH 04/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 60 +++++++++++++-------------- 1 file changed, 28 insertions(+), 32 deletions(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 33f05ce3..a56e7470 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -1,14 +1,10 @@ = Partner Manager CloudHub 2.0 Migration Guide -To migrate your B2B operations from CloudHub 1.0 to the more advanced CloudHub 2.0, follow the relevant path in this guide based on your deployment scenario. - -== Before You Begin - -For customers deploying with a Virtual Private Cloud (VPC) and Dedicated Load Balancer (DLB), start by following the prerequisite steps in xref:cloudhub::vpc-upgrade.adoc[]. +To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced CloudHub 2.0 (CH2), follow the relevant path in this guide based on your deployment scenario. == Migration With VPC and DLB with URL Preservation -. Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[CloudHub VPC to CloudHub 2.0 Private Space Upgrade] page to upgrade your CloudHub 1.0 (CH1) Virtual Private Cloud (VPC) to a CloudHub 2.0 (CH2) private space. +. Follow the steps on the xref:runtime-manager::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. .. Make sure you don't have any inflight messages. @@ -18,13 +14,13 @@ For customers deploying with a Virtual Private Cloud (VPC) and Dedicated Load Ba ... b2b-api-replication-service-* . On the Partner Manager tab in Access Management > Business Groups: .. Click *Edit Configuration* for the environment you want to update. -.. Select CloudHub 2.0 and from the *Deployment Target Type* dropdown. +.. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space that was configured previously. -.. Before saving, open your browser's developer tools and navigate to the *Network* tab and make sure the Method column is enabled. +.. Before saving, open your browser's developer tools and navigate to the *Network* tab to make sure the Method column is enabled. .. Click *Save* in Access Management. -.. Check the *I understand the effects of this action* box, and then click *Save*. Ignore the error message about the target runtime type. -. In Developer Tools: -.. Right-click on the most recent PUT request, hover over *Copy* and select *Copy as CURL*. +.. Check the *I understand the effects of this action* box and click *Save*. Ignore the error message about the target runtime type. +. In your browser's developer tools: +.. Right-click on the most recent PUT request, and then hover over *Copy* and select *Copy as CURL*. .. Paste the CURL command into your preferred API Client, such as Postman. Set *forceUpdate* to True by updating the URL. .. Send the PUT request. . In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. @@ -32,18 +28,18 @@ For customers deploying with a Virtual Private Cloud (VPC) and Dedicated Load Ba [NOTE] Incoming messages are delivered to Anypoint MQ but aren't processed until the CH1 app is running. For the app switching to work, ensure the CH1 app is in a Running state. -. Use the CH1 to CH2 migration tool xref:cloudhub::app-migration.adoc[] to upgrade the deployment for the `inbound-as2` applications and `inbound-https` applications, which creates their counterparts in CH2. +. Use the CH1 to CH2 migration tool xref:runtime-manager::app-migration.adoc[] to upgrade the deployment for the `inbound-as2` and `inbound-https` applications, which creates their counterparts in CH2. .. Make sure the name remains the same. -.. Use a dummy jar file with the same name, dummy jar. -.. Preserve the ingress urls. Initially, the name resolution 0% CH2, 100% CH1. +.. Use a dummy jar file with the same name, "dummy jar." +.. Preserve the ingress urls. Initially, the name resolution is 0% for CH2 and 100% for CH1. . On the Message Flows tab in Partner Manager: .. Click Manage Deployments and choose either Upgrade deployments or Apply environment settings. -.. Check the *I understand the effects of these actions*, and then click *Confirm*. +.. Check *I understand the effects of these actions* and click *Confirm*. + -Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files the apps in CH2. +Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. + -Before shifting any traffic, keep the CH1 inbound AS2 and HTTP applications running and handling 100% of traffic to confirm their functioning as expected post-migration. -. In Runtime Manager, increase the traffic on the CH2 app incrementally over a period of a few days to 100%. Keep the CH1 apps in a Shutdown status after traffic reaches 100%. +Before shifting traffic, keep the CH1 inbound AS2 and HTTP applications running and handling 100% of the traffic to confirm they're functioning as expected post-migration. +. In Runtime Manager, increase the traffic on the CH2 app incrementally over a period of a few days until it reaches 100%. Keep the CH1 apps in a Shutdown status after traffic reaches 100%. . After you've stopped all CH1 applications that use the DLB, failover the DLB domain (anypointdns.net) to CH2 and delete the DLB. New message flow deployments in Partner Manager beyond this point only update the CH2 apps. @@ -51,7 +47,7 @@ New message flow deployments in Partner Manager beyond this point only update th == Migration With VPC and DLB but Without URL Preservation -. Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[CloudHub VPC to CloudHub 2.0 Private Space Upgrade] page to upgrade your CloudHub 1.0 (CH1) Virtual Private Cloud (VPC) to a CloudHub 2.0 (CH2) private space. +. Follow the steps on the xref:runtime-manager::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint VPC to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. .. Make sure you don't have any inflight messages. @@ -62,21 +58,21 @@ New message flow deployments in Partner Manager beyond this point only update th ... b2b-api-replication-service-* . On the Partner Manager tab in Access Management > Business Groups: .. Click *Edit Configuration* for the environment you want to update. -.. Select CloudHub 2.0 and from the *Deployment Target Type* dropdown. +.. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space that was configured previously. -.. Before saving, open your browser's developer tools and navigate to the *Network* tab and make sure the Method column is enabled. +.. Before saving, open your browser's developer tools and navigate to the *Network* tab to make sure the Method column is enabled. .. Click *Save* in Access Management. -.. Check *I understand the effects of this action*, and then click *Save*. Ignore the error message about the target runtime type. +.. Check *I understand the effects of this action* and click *Save*. Ignore the error message about the target runtime type. . In Developer Tools: -.. Right-click on the most recent PUT request, hover over *Copy* and select *Copy as CURL*. +.. Right-click on the most recent PUT request, and then hover over *Copy* and select *Copy as CURL*. .. Paste the CURL command into your preferred API Client, such as Postman. Update the URL so that *forceUpdate* is set to True. .. Send the PUT request. . In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. . On the Message Flows tab in Partner Manager: .. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. -.. Check the *I understand the effects of these actions*, and then click *Confirm*. +.. Check *I understand the effects of these actions* and click *Confirm*. + -Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files the apps in CH2. +Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. New message flow deployments in Partner Manager beyond this point only update the CH2 apps. @@ -92,20 +88,20 @@ New message flow deployments in Partner Manager beyond this point only update th ... b2b-api-replication-service-* . On the Partner Manager tab in Access Management > Business Groups: .. Click *Edit Configuration* for the environment you want to update. -.. Select CloudHub 2.0 and from the *Deployment Target Type* dropdown. +.. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space or shared space. -.. Before saving, open your browser's developer tools and navigate to the *Network* tab and make sure the Method column is enabled. +.. Before saving, open your browser's developer tools and navigate to the *Network* tab to make sure the Method column is enabled. .. Click *Save* in Access Management. -.. Check the *I understand the effects of this action* box, and then click *Save*. Ignore the error message about the target runtime type. +.. Check the *I understand the effects of this action* box and click *Save*. Ignore the error message about the target runtime type. . In Developer Tools: -.. Right-click on the most recent PUT request, hover over *Copy* and select *Copy as CURL*. -.. Paste the CURL command into your preferred API Client, such as Postman. Update the URL so that *forceUpdate* is set to True. +.. Right-click on the most recent PUT request, and then hover over *Copy* and select *Copy as CURL*. +.. Paste the CURL command into your preferred API Client, such as Postman. Update the URL so that *forceUpdate* is set to True. .. Send the PUT request. . In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. . On the Message Flows tab in Partner Manager: .. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. -.. Check the *I understand the effects of these actions*, and then click *Confirm*. +.. Check *I understand the effects of these actions* and click *Confirm*. + -Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files the apps in CH2. +Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. New message flow deployments in Partner Manager beyond this point only update the CH2 apps. From 3fe9f0a29ecf8c18f98a5ce281fcd441ebbe3e12 Mon Sep 17 00:00:00 2001 From: Tasha Date: Thu, 9 Oct 2025 16:03:23 -0500 Subject: [PATCH 05/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index a56e7470..e888d641 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -45,7 +45,7 @@ Before shifting traffic, keep the CH1 inbound AS2 and HTTP applications running New message flow deployments in Partner Manager beyond this point only update the CH2 apps. -== Migration With VPC and DLB but Without URL Preservation +== Migration With VPC and DLB Without URL Preservation . Follow the steps on the xref:runtime-manager::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint VPC to a CH2 private space. . In Runtime Manager: From 00a7fb8cb5b81434bd9abf943ac0990d2a1559b5 Mon Sep 17 00:00:00 2001 From: Tasha Date: Fri, 10 Oct 2025 09:39:58 -0500 Subject: [PATCH 06/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index e888d641..4cc1fc35 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -4,7 +4,7 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced Clou == Migration With VPC and DLB with URL Preservation -. Follow the steps on the xref:runtime-manager::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. +. Follow the steps on the xref:runtime-manager::cloudhub/vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. .. Make sure you don't have any inflight messages. From 73fad750c1676f01478259cccd09b2d38aff94d5 Mon Sep 17 00:00:00 2001 From: Tasha Date: Fri, 10 Oct 2025 10:25:31 -0500 Subject: [PATCH 07/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 4cc1fc35..f1bf074e 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -4,7 +4,7 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced Clou == Migration With VPC and DLB with URL Preservation -. Follow the steps on the xref:runtime-manager::cloudhub/vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. +. Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. .. Make sure you don't have any inflight messages. From e0d4d12ed83be6d868cf4ae2ade416f5f9820c58 Mon Sep 17 00:00:00 2001 From: Tasha Date: Fri, 10 Oct 2025 10:32:10 -0500 Subject: [PATCH 08/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index f1bf074e..9f2bfbe6 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -28,7 +28,7 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced Clou [NOTE] Incoming messages are delivered to Anypoint MQ but aren't processed until the CH1 app is running. For the app switching to work, ensure the CH1 app is in a Running state. -. Use the CH1 to CH2 migration tool xref:runtime-manager::app-migration.adoc[] to upgrade the deployment for the `inbound-as2` and `inbound-https` applications, which creates their counterparts in CH2. +. Use the CH1 to CH2 migration tool xref:cloudhub::app-migration.adoc[] to upgrade the deployment for the `inbound-as2` and `inbound-https` applications, which creates their counterparts in CH2. .. Make sure the name remains the same. .. Use a dummy jar file with the same name, "dummy jar." .. Preserve the ingress urls. Initially, the name resolution is 0% for CH2 and 100% for CH1. @@ -47,7 +47,7 @@ New message flow deployments in Partner Manager beyond this point only update th == Migration With VPC and DLB Without URL Preservation -. Follow the steps on the xref:runtime-manager::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint VPC to a CH2 private space. +. Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint VPC to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. .. Make sure you don't have any inflight messages. From 2414051f7a323a48b9a69cb4424f3430a9f28fb0 Mon Sep 17 00:00:00 2001 From: Tasha Date: Mon, 13 Oct 2025 14:59:54 -0500 Subject: [PATCH 09/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 9f2bfbe6..3e69a3b0 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -97,7 +97,7 @@ New message flow deployments in Partner Manager beyond this point only update th .. Right-click on the most recent PUT request, and then hover over *Copy* and select *Copy as CURL*. .. Paste the CURL command into your preferred API Client, such as Postman. Update the URL so that *forceUpdate* is set to True. .. Send the PUT request. -. In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. +. In Access Management, refresh the *Partner Manager* tab. The deployment target is now CH2. . On the Message Flows tab in Partner Manager: .. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. .. Check *I understand the effects of these actions* and click *Confirm*. From e95004004c7307f06a04e7ae930b7a9efe17088e Mon Sep 17 00:00:00 2001 From: Tasha Date: Tue, 28 Oct 2025 12:15:38 -0500 Subject: [PATCH 10/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 3e69a3b0..7e24ec86 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -12,7 +12,12 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced Clou ... b2b-outbound-* ... b2b-document-processing-service-* ... b2b-api-replication-service-* -. On the Partner Manager tab in Access Management > Business Groups: + +[NOTE] +Don't undeploy your message flows in Partner Manager as part of this process. + +[start=2] +. On the Business Groups > Partner Manager tab in Access Management: .. Click *Edit Configuration* for the environment you want to update. .. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space that was configured previously. @@ -29,11 +34,11 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced Clou Incoming messages are delivered to Anypoint MQ but aren't processed until the CH1 app is running. For the app switching to work, ensure the CH1 app is in a Running state. . Use the CH1 to CH2 migration tool xref:cloudhub::app-migration.adoc[] to upgrade the deployment for the `inbound-as2` and `inbound-https` applications, which creates their counterparts in CH2. -.. Make sure the name remains the same. -.. Use a dummy jar file with the same name, "dummy jar." +.. Make sure the application name remains the same. +.. Use a dummy jar file with the same name, "dummy jar." You can use any placeholder jar file, since the file is overwritten in a later step with the correct jar file. .. Preserve the ingress urls. Initially, the name resolution is 0% for CH2 and 100% for CH1. . On the Message Flows tab in Partner Manager: -.. Click Manage Deployments and choose either Upgrade deployments or Apply environment settings. +.. Click *Manage Deployments* and choose either *Upgrade deployments* or *Apply environment settings*, which redeploys all Partner Manager applications without requiring you to redeploy each individual message flow. .. Check *I understand the effects of these actions* and click *Confirm*. + Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. @@ -56,7 +61,7 @@ New message flow deployments in Partner Manager beyond this point only update th ... b2b-outbound-* ... b2b-document-processing-service-* ... b2b-api-replication-service-* -. On the Partner Manager tab in Access Management > Business Groups: +. On the Business Groups > Partner Manager tab in Access Management: .. Click *Edit Configuration* for the environment you want to update. .. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space that was configured previously. @@ -86,7 +91,7 @@ New message flow deployments in Partner Manager beyond this point only update th ... b2b-outbound-* ... b2b-document-processing-service-* ... b2b-api-replication-service-* -. On the Partner Manager tab in Access Management > Business Groups: +. On the Business Groups > Partner Manager tab in Access Management: .. Click *Edit Configuration* for the environment you want to update. .. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space or shared space. From 357a975e84e24478940ece51051d68594006ad9d Mon Sep 17 00:00:00 2001 From: Tasha Date: Wed, 5 Nov 2025 14:13:37 -0600 Subject: [PATCH 11/13] Update ch2-migration.adoc --- modules/ROOT/pages/ch2-migration.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 7e24ec86..47df9358 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -21,7 +21,7 @@ Don't undeploy your message flows in Partner Manager as part of this process. .. Click *Edit Configuration* for the environment you want to update. .. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space that was configured previously. -.. Before saving, open your browser's developer tools and navigate to the *Network* tab to make sure the Method column is enabled. +.. Before saving, open your browser's developer tools and navigate to the *Network* or equivalent tab to make sure the Method column is enabled. .. Click *Save* in Access Management. .. Check the *I understand the effects of this action* box and click *Save*. Ignore the error message about the target runtime type. . In your browser's developer tools: @@ -38,7 +38,7 @@ Incoming messages are delivered to Anypoint MQ but aren't processed until the CH .. Use a dummy jar file with the same name, "dummy jar." You can use any placeholder jar file, since the file is overwritten in a later step with the correct jar file. .. Preserve the ingress urls. Initially, the name resolution is 0% for CH2 and 100% for CH1. . On the Message Flows tab in Partner Manager: -.. Click *Manage Deployments* and choose either *Upgrade deployments* or *Apply environment settings*, which redeploys all Partner Manager applications without requiring you to redeploy each individual message flow. +.. Click *Manage Deployments* and choose either *Upgrade deployments* or *Apply environment settings*, which redeploys all Partner Manager applications without requiring you to redeploy individual message flow. .. Check *I understand the effects of these actions* and click *Confirm*. + Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. @@ -65,7 +65,7 @@ New message flow deployments in Partner Manager beyond this point only update th .. Click *Edit Configuration* for the environment you want to update. .. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space that was configured previously. -.. Before saving, open your browser's developer tools and navigate to the *Network* tab to make sure the Method column is enabled. +.. Before saving, open your browser's developer tools and navigate to the *Network* or equivalent tab to make sure the Method column is enabled. .. Click *Save* in Access Management. .. Check *I understand the effects of this action* and click *Save*. Ignore the error message about the target runtime type. . In Developer Tools: @@ -74,7 +74,7 @@ New message flow deployments in Partner Manager beyond this point only update th .. Send the PUT request. . In Access Management, refresh the Partner Manager tab. The deployment target is now CH2. . On the Message Flows tab in Partner Manager: -.. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. +.. Click *Manage Deployments* and choose either *Upgrade deployments* or *Apply environment settings*, which redeploys all Partner Manager applications without requiring you to redeploy individual message flow. .. Check *I understand the effects of these actions* and click *Confirm*. + Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. @@ -95,7 +95,7 @@ New message flow deployments in Partner Manager beyond this point only update th .. Click *Edit Configuration* for the environment you want to update. .. Select CloudHub 2.0 from the *Deployment Target Type* dropdown. .. In the *Deployment Target* dropdown, select the private space or shared space. -.. Before saving, open your browser's developer tools and navigate to the *Network* tab to make sure the Method column is enabled. +.. Before saving, open your browser's developer tools and navigate to the *Network* or equivalent tab to make sure the Method column is enabled. .. Click *Save* in Access Management. .. Check the *I understand the effects of this action* box and click *Save*. Ignore the error message about the target runtime type. . In Developer Tools: @@ -104,7 +104,7 @@ New message flow deployments in Partner Manager beyond this point only update th .. Send the PUT request. . In Access Management, refresh the *Partner Manager* tab. The deployment target is now CH2. . On the Message Flows tab in Partner Manager: -.. Click *Manage Deployments* and choose either Upgrade deployments or Apply environment settings. +.. Click *Manage Deployments* and choose either *Upgrade deployments* or *Apply environment settings*, which redeploys all Partner Manager applications without requiring you to redeploy individual message flow. .. Check *I understand the effects of these actions* and click *Confirm*. + Partner Manager deploys and updates the corresponding apps in CH2 that were deployed with dummy jar files. From 4bd53d06022413b87d96f3f37a3ad5dfb8ca6a54 Mon Sep 17 00:00:00 2001 From: Tasha Date: Thu, 6 Nov 2025 08:44:08 -0600 Subject: [PATCH 12/13] added links and anchors --- modules/ROOT/pages/ch2-migration.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 47df9358..935c0ff4 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -2,6 +2,11 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced CloudHub 2.0 (CH2), follow the relevant path in this guide based on your deployment scenario. +* <> +* <> +* <> + +[#migration-with-vpc-and-dlb-with-url-preservation] == Migration With VPC and DLB with URL Preservation . Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. @@ -50,6 +55,7 @@ Before shifting traffic, keep the CH1 inbound AS2 and HTTP applications running New message flow deployments in Partner Manager beyond this point only update the CH2 apps. +[#migration-with-vpc-and-dlb-without-url-preservation] == Migration With VPC and DLB Without URL Preservation . Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint VPC to a CH2 private space. @@ -81,6 +87,7 @@ Partner Manager deploys and updates the corresponding apps in CH2 that were depl New message flow deployments in Partner Manager beyond this point only update the CH2 apps. +[#slb-migration-to-a-private-space] == SLB Migration to a Private Space . In Runtime Manager: From 103ad3a2b0dddeb69e2ae88284c50f1421fb88f9 Mon Sep 17 00:00:00 2001 From: Tasha Date: Thu, 6 Nov 2025 15:06:56 -0600 Subject: [PATCH 13/13] added section overviews --- modules/ROOT/pages/ch2-migration.adoc | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/ch2-migration.adoc b/modules/ROOT/pages/ch2-migration.adoc index 935c0ff4..2892fed0 100644 --- a/modules/ROOT/pages/ch2-migration.adoc +++ b/modules/ROOT/pages/ch2-migration.adoc @@ -4,11 +4,13 @@ To migrate your B2B operations from CloudHub 1.0 (CH1) to the more advanced Clou * <> * <> -* <> +* <> [#migration-with-vpc-and-dlb-with-url-preservation] == Migration With VPC and DLB with URL Preservation +This path is for customers migrating from a CH1 Virtual Private Cloud (VPC) with a Dedicated Load Balancer (DLB) who must preserve their external URLs for zero-downtime transition. The process keeps critical CH1 inbound apps active, updates the target environment via API, and uses the CH1 to CH2 Migration Tool to create CH2 counterparts that inherit existing URLs. Finally, traffic is incrementally shifted from CH1 to CH2 before the DLB is failed over and retired. + . Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint Virtual Private Cloud (Anypoint VPC) to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. @@ -58,6 +60,8 @@ New message flow deployments in Partner Manager beyond this point only update th [#migration-with-vpc-and-dlb-without-url-preservation] == Migration With VPC and DLB Without URL Preservation +This path is for customers who choose not to preserve external URLs when migrating from a CH1 Anypoint VPC with a DLB. Migration involves decommissioning all existing CH1 applications, upgrading the environment target via an API call, and then redeploying all applications directly to a new CH2 Private Space by using Partner Manager's deployment management tool. + . Follow the steps on the xref:cloudhub::vpc-upgrade.adoc[] page to upgrade your CH1 Anypoint VPC to a CH2 private space. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1. @@ -87,8 +91,10 @@ Partner Manager deploys and updates the corresponding apps in CH2 that were depl New message flow deployments in Partner Manager beyond this point only update the CH2 apps. -[#slb-migration-to-a-private-space] -== SLB Migration to a Private Space +[#shared-load-balancer-migration-to-a-private-space] +== Shared Load Balancer Migration to a Private Space + +This section details the straightforward path for customers moving applications from CH1 with a Shared Load Balancer (SLB) to a CH2 Private or Shared Space. Migration involves stopping and deleting all applications in CH1, updating the environment target via API, and then redeploying all applications directly to the new CH2 space by using the deployment management tool. . In Runtime Manager: .. Stop all inbound Partner Manager applications deployed to CH1.