WAS migration overview

At a high-level, the process of migrating your WAS apps consists of:

  1. 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:

  2. 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.

  3. Deploying your migrated apps

    After migrating your apps, deploy them to GKE or Anthos clusters on Google Cloud, to Anthos clusters on VMware, or to a 1.4 version or later of Anthos clusters on AWS.

Migration Procedure

The following image shows the steps to migrate a WAS app:

Migrate WAS apps to individual app containers.

To perform a migration:

  1. Add a migration source.

    Add the migration source that represents the source platform.

  2. Create a migration.

    Create the migration plan, which you can customize before executing the migration.

  3. Customize the migration plan.

    Edit the migration plan, including selecting the WAS app that you want to migrate. You migrate one WAS app per migration.

  4. Generate and review migration artifacts.

    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.

  5. Build an app container image.

    Use the migration artifacts (Dockerfile, build.sh,anddeployment_spec.yaml) to build the container for your migrated app.

  6. Deploy an app container to a target cluster.

Next steps