Planning a migration
Before you migrate any production environment, make sure that you have migrated your staging or test environment and have tested your applications in the new environment.
Migrate to a new version for one or more of the following reasons:
- You want to improve performance.
- You need fixes that are in the new version.
- You want to use new features that are provided in the new version.
- Your existing product version is going out of service.
Use migration testing for one or more of the following reasons:
- You must estimate in advance the amount of downtime that will be needed for migration. An estimate of downtime cannot be created without testing.
- You want to make sure that the new version improves performance.
- You want to make sure that the fixes you require are in the new version and work as expected.
- You want to make sure that your existing applications work correctly in the new version.
To test the migration:
- Prepare test cases that are based on the existing functions and requirements.
- Prepare the test environment. The following factors must be the
same in both the test environment and the production environment:
- Operating system type and version
- Database type and version
- IBM® Business Automation Workflow version and WebSphere® Application Server version
- IBM Business Automation Workflow topology
- Test the migration. Make sure that all the migration steps run successfully.
- Use your test cases to make sure that all applications work correctly after migration.
- Make sure that you note all changes to your applications, and keep track of everything that you moved to the new environment, to help when you migrate the production environment.
Restriction: IBM Business
Automation Workflow V19.0.0.3 does
not support migration of the Unit Test Environment (UTE) for IBM Integration
Designer.
For tuning guidance on migration, see Chapter 6: Migration considerations in IBM Business Process Manager V8.5 Performance Tuning and Best Practices.