Before you begin

Before you begin a migration, you must first perform the following tasks.

Install Migrate to Containers

Install Migrate to Containers on your processing cluster. A processing cluster is a Google Kubernetes Engine (GKE) or Anthos cluster with Migrate to Containers components installed, and which you use to migrate VMs. See Installation overview for all installation instructions.

Note: Use Migrate to Containers version 1.11.0 or higher.

Optionally install Migrate to VMs

To use Migrate to Containers to migrate Linux VMs to Google Cloud from VMware, AWS and Azure, you must install Migrate to VMs which handles the transport. See Set up Migrate to VMs for more.

Set up the binaryAppScanner.jar

Note:

Make sure to download the latest version of the binaryAppScanner.jar. If you have already downloaded the tool, you can check the modification date on the download page to ensure that you have the latest version.

You can also use the following command to determine your current version:

java -jar binaryAppScanner.jar --version

Then compare your current version to the version shown in the IBM license that appears when you click Migration Toolkit for Application Binaries to download the file.

Migrate to Containers automates the use of the binaryAppScanner.jar, available as part of the IBM WebSphere Application Server Migration Toolkit for Application Binaries, to extract configuration information and files for WAS applications in the source VM.

Before you can perform a migration, you must:

• Accept the license agreement and download the IBM WebSphere Application Server Migration Toolkit for Application Binaries, and then extract the binaryAppScanner.jar file.

• Create a Dockerfile and prepare the plugin bundled with the binary scanner.

To set up binaryAppScanner.jar:

1. Download the installer file, binaryAppScannerInstaller.jar, from IBM Support.You must accept the license agreement as part of the download.

2. Run the following command to extract the binaryAppScanner.jar file and to accept the License Agreement:

   java -jar binaryAppScannerInstaller.jar --acceptLicense --verbose
   

3. Specify the target directory for the extraction. For example, /tmp. The installer creates a directory named /wamt below the target directory.

4. Navigate to the /wamt directory. For example:

   cd /tmp/wamt
   

5. Create a Dockerfile with the following two commands:

   FROM us-docker.pkg.dev/migrate-modernize-public/modernize-prod/v2k-websphere:v1.11.0
   ADD binaryAppScanner.jar /
   

6. Build and push the docker image:

   gcloud builds submit --timeout 1h -t gcr.io/PROJECT_ID/v2k-websphere-with-scanner:v1 --project PROJECT_ID
   

7. Edit the plugin CRD to bundle it with binary-scanner as following:

   $ kubectl edit appxplugins.anthos-migrate.cloud.google.com -n v2k-system websphere-container
   
   # Set the value gcr.io/PROJECT_ID/v2k-websphere-with-scanner:v1 in both 
   # spec.discoveryImage and spec.generateArtifactsImage:
   
   apiVersion: anthos-migrate.cloud.google.com/v1beta2
   kind: AppXPlugin
   metadata:
     namespace: v2k-system
     name: websphere-container
     labels:
       anthos-migrate.cloud.google.com/preview-type: "public"
     annotations:
       anthos-migrate.cloud.google.com/display-name: "Websphere container"
   spec:
     discoverImage: gcr.io/PROJECT_ID/v2k-websphere-with-scanner:v1
     discoverCommand:
     - /bin/sh
     - -c
     - /websphere-discovery
     parameterDefs:
       - name: was-home
         usage: Path of the Websphere WAS_HOME on the original instance.
         envVar: APPX_WAS_HOME
     generateArtifactsImage: gcr.io/PROJECT_ID/v2k-websphere-with-scanner:v1
     generateArtifactsCommand:
     - /bin/sh
     - -c
     - /websphere-extraction
   

8. Save the CRD.

What's next

Linux

Migrate

1. Add a migration source.
2. Create a migration plan.
3. Migrate data.
4. Customize your migration plan.
5. Execute the migration.
6. Monitor a migration.
7. Delete a migration.

Deploy

1. Review generated artifacts.
2. Configure logging.
3. Mounting external volumes.
4. Deploy a workload to a target cluster.
5. Deploy migrated VMs.
6. Post-migration image updates.
7. Monitor migrated workload.
8. Test your migrate app and validate the migration.

Windows

Migrate

1. Add a migration source.
2. Create a migration plan.
3. Customize your migration plan.
4. Execute the migration.
5. Monitor the migration.
6. Build a Windows container image.
7. Delete a migration.

Deploy

1. Deploy a workload to a target cluster.
2. Deploy migrated VMs.
3. Monitor migrated workload.
4. Test your migrate app and validate the migration.

Tomcat

Migrate

1. Add a migration source.
2. Create a migration.
3. Migrate data.
4. Customize your migration plan.
5. Execute the migration.
6. Monitor the migration.
7. Build a Tomcat container image.
8. Delete a migration.

Deploy

1. Deploy a workload to a target cluster.
2. Deploy migrated VMs.
3. Monitor migrated workload.
4. Test your migrate app and validate the migration.

WebSphere (Pre-Ga)

Migrate

1. Migration overview.
2. Requirements.
3. Before you begin.
4. Add a migration source.
5. Create a migration plan.
6. Migrate data.
7. Customize the migration plan.
8. Execute the migration.
9. Monitor the migration.
10. Build an app container image.
11. Deploy an app container to a target cluster.
12. Delete a migration.
13. Troubleshooting.

Deploy

1. Deploy a workload to a target cluster.
2. Deploy migrated VMs.
3. Monitor migrated workload.
4. Test your migrate app and validate the migration.