Filter
Top Products
Chapter 3. Migration Strategy and Planning 45
Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm
After migration only the new development environment could operate on this
machine and as such it is important that you have another WebSphere
Commerce Studio V5.1 environment if you need to continue to develop or
maintain WebSphere Commerce Suite V5.1 site.
The following is a general ordered list of tasks that are required to complete
development migration:
1. Backup: Backup files, database and environment assets
2. Install/migrate software stack
3. Perform pre-migration steps
4. Import files to WebSphere Commerce V5.6 development environment
5. Generate deployment code and access beans
6. Apply changes for code migration
7. Migrate WebSphere Commerce development instance
8. Migrate database schema and unencrypted data
9. Migrate encrypted data
10.Setting up Test environment and Testing the migrated application
3.5 Migration approaches for runtime environment
This section describes three different approaches to migrating from WebSphere
Commerce Suite V5.1 to WebSphere Commerce V5.6 runtime environment. A
number of factors goes into deciding which approach is best suited to the system
to be migrated such as: existing configuration, hardware resources available,
and acceptable downtime of the production system during course of migration.
When the appropriate migration approach is chosen, the downtime of the
production system can be kept to a minimum. The following sections describes
options provided by the migration tools of WebSphere Commerce V5.6. Consider
the approaches and decide which is best suited for your system. The approaches
are as follows:
Switch-Over migration scenario- involves creating a separated WebSphere
Commerce V5.6 environment on a remote node while keeping WebSphere
Commerce Suite V5.1 environment operational.
Co-existence migration scenario - involves migrating to WebSphere
Commerce V5.6 environment and creating a new instance while the
WebSphere Commerce Suite V5.1 environment is still running on the same
machine. This is possible if the WebSphere Commerce Suite V5.1 node has