WAS migration overview
At a high-level, the process of migrating your WAS apps consists of:
Identifying the migration source
Use Migrate to Containers when you have Linux VMs running WAS apps on VMware, AWS, Azure, or Compute Engine and you want to run the applications in containers on GKE or Anthos:
For VMware, AWS and Azure, when the target is Google Cloud there is a dependency on installing Migrate for Compute Engine to facilitate the transfer of workloads into Google Cloud. See Set up Migrate for Compute Engine (if needed) for more.
For VMware, when you want to migrate the application to run in a container on-prem, install Anthos clusters on VMware on the vCenter/vSphere environment of the source VMware VM to perform the migration.
Creating a migration processing cluster
Use a cluster to run the Migrate to Containers components that perform the transformations required to migrate a workload from a source VM to a target container. This cluster is referred to as the processing cluster. The processing cluster can be a GKE or Anthos cluster on Google Cloud, Anthos clusters on VMware, or Anthos clusters on AWS.
Deploying your migrated apps
The following image shows the steps to migrate a WAS app:
To perform a migration:
Add the migration source that represents the source platform.
Create the migration plan, which you can customize before executing the migration.
Edit the migration plan, including selecting the WAS app that you want to migrate. You migrate one WAS app per migration.
Perform the migration to generate the app container. You can monitor the migration process, and when finished, review the artifacts in preparation for building the deployable app image.
Use the migration artifacts (
deployment_spec.yaml) to build the container for your migrated app.