Upgrade Applications Using the Migration Tool
Use the application migration tool for apps in private spaces created from upgraded VPCs. Link a CloudHub app to a CloudHub 2.0 app, configure deployment settings, and prepare the DLB for traffic switching.
Eligibility
To use the application migration tool, first upgrade your CloudHub VPC to a CloudHub 2.0 private space using the VPC upgrade tool.
The application upgrade tool works only in CloudHub 2.0 private spaces that were upgraded from a CloudHub VPC.
Step 1: Start the Upgrade
Open the upgrade page for your CloudHub application in Runtime Manager.
-
In Anypoint Platform, select Runtime Manager > Applications.
-
Select the CloudHub application you want to upgrade, then click Settings.
If your application is eligible for the upgrade, the upgrade tooling appears on the Settings page.
-
Click Upgrade to CloudHub 2.0, then click Start Upgrade.
The Upgrade Application to CloudHub 2.0 page opens with these fields.
-
Application Name — Shows the inherited CloudHub application name by default. To use a different name for your CloudHub 2.0 application, edit this field.
-
Upgrading From — Shows the name of the CloudHub application you’re migrating from. You can’t edit this field.
-
Deployment Target — Shows the preselected private space based on the upgraded CloudHub VPC. You can’t edit this field.
-
Step 2: Configure the Application File
Provide the application file by uploading it or importing it from Exchange.
-
Upload an app file: Download the app asset from the link under Application File, make the required changes, and upload it to deploy the new app to the CloudHub 2.0 private space.
-
Import a file from Anypoint Exchange: Import the CloudHub app to upgrade.
Step 3: Configure Ingress
Configure the endpoint in the Ingress tab so traffic reaches the CloudHub 2.0 application.
-
Select a Host from the dropdown list.
If you’re using the anypointdns.netendpoint without a TLS context, the Ingress tab doesn’t show it as a possible endpoint. -
Select a subdomain from the dropdown list.
-
Add a path.
-
Optionally, add a path rewrite.
-
Select whether to provide internal or external access to your endpoint.
| If you use a different name for the CloudHub 2.0 application, enter the original CloudHub application name in the subdomain field of the Ingress tab endpoint configuration. If you configure the URLs incorrectly, traffic doesn’t reach the CloudHub 2.0 application during traffic switching. |
| The Host dropdown list shows only the domains that were initially added under the certificates of the underlying VPC’s DLB configuration. If you add a new certificate to the original VPC’s DLB after the application upgrade starts, add it manually under the Domain & TLS tab of your new private space for that domain to appear in the Host dropdown list. |
Step 4: Configure Application Properties
Review the properties that the upgrade process copies from your CloudHub application, and edit them so they persist.
| The upgrade process doesn’t automatically carry over application properties to CloudHub 2.0. |
-
The upgrade process copies your CloudHub application’s properties during configuration. However, these properties don’t persist unless you edit at least one property or add a new one. Editing or adding a single property causes all copied properties to persist.
-
The upgrade process copies protected properties with
******as the displayed value. Manually change this value to the correct protected value in your CloudHub 2.0 application settings.
Step 5: Deploy the Application
Deploy the application to your CloudHub 2.0 private space. For the full procedure, see Deploying Apps to CloudHub 2.0.
Step 6: Restart the DLB
After deploying the application to CloudHub 2.0, restart the dedicated load balancer (DLB) to.
-
Clear cached routing tables.
-
Rediscover application endpoints.
-
Load updated DNS records for CloudHub 2.0 applications.
-
Establish connections to CloudHub 2.0 ingress controllers.