Migrate IBM WAS traditional applications

Preview

This product or feature is covered by the Pre-GA Offerings Terms of the Google Cloud Terms of Service. Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. For more information, see the launch stage descriptions.

IBM WebSphere Application Server (WAS) traditional is a software framework that hosts Java-based workloads. Migrate to Containers lets you modernize app workloads running in WAS traditional by converting them to application containers. You can then deploy the app containers to:

• GKE or Anthos cluster on Google Cloud
• Anthos clusters on VMware
• Anthos clusters on AWS

About migrating WebSphere Application Server traditional apps

A WAS traditional VM can contain multiple apps. Migrate to Containers helps you automate the modernization of WAS apps to containers by discovering deployed apps in the source VM and automatically suggesting the configuration for the modernization.

Google requires that you migrate each app to its own container image (ibmcom/websphere-traditional or openliberty/open-liberty). You can then test and deploy the migrated apps individually, rather than having to test and deploy multiple apps together.

The migration source can be WAS ND or WAS base. The target will be a Liberty or traditional WAS base container, and the respective ND clustering features will be delegated to Kubernetes.

About Migrate to Containers

Use Migrate to Containers to convert WAS traditional VM-based apps into containers in Google Kubernetes Engine (GKE) or Anthos.

To get started, please review the Migrate to Containers concepts and architecture documentation:

• Benefits of migrating to containers
• Migrate to Containers architecture
• Migration journey

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

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.

JBoss

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

Apache

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 an Apache 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.