IBM SG24-6320-00 Manuel D’Utilisation
Chapter 3. Migration Strategy and Planning
49
Draft Document for Review July 28, 2004 7:33 pm
6320ch_planning.fm
The following is a general ordered list of tasks that are required to complete an
In-place migration:
In-place migration:
Take WebSphere Commerce Suite V5.1 production server offline
Backup production system
Perform pre-migration actions
Install (for coexistence) or update software levels to WebSphere Commerce
V5.6
V5.6
Perform instance migration
Migrate database
Deploy migrated code from the development machine
Complete required migration tasks on the test server
Test migrated instance
Bring WebSphere Commerce V5.6 test server online to become the new
production server
production server
3.6 Approach used for this migration
In our approach our main goal was to minimize the downtime of the production
server. To achieve this we chosen the Switch-Over migration.
server. To achieve this we chosen the Switch-Over migration.
Our final production environment consisted of a three nodes - a WebSphere
Commerce node with a remote database node and a remote WebSphere
Commerce Payments node. Initially, however, we migrated the WebSphere
Commerce and database to a single node. Then, once we had successfully
tested the migrated environment and we were satisfied with migration to
WebSphere Commerce V5.6, we moved the database to a remote database
server creating a three node environment as the original system topology.
Commerce node with a remote database node and a remote WebSphere
Commerce Payments node. Initially, however, we migrated the WebSphere
Commerce and database to a single node. Then, once we had successfully
tested the migrated environment and we were satisfied with migration to
WebSphere Commerce V5.6, we moved the database to a remote database
server creating a three node environment as the original system topology.
While we were migrating the solution, the first stage of the migration, the
WebSphere Commerce Suite V5.1 remained running thus we had minimal
downtime. As soon as we had migrated we switched over the actual production
environment from WebSphere Commerce Suite V5.1 to WebSphere Commerce
V5.6, WebSphere Commerce Suite V5.1 remained operational as our backup
incase of problems.
WebSphere Commerce Suite V5.1 remained running thus we had minimal
downtime. As soon as we had migrated we switched over the actual production
environment from WebSphere Commerce Suite V5.1 to WebSphere Commerce
V5.6, WebSphere Commerce Suite V5.1 remained operational as our backup
incase of problems.
Below are described the high level tasks we performed to do a complete
migration on the development and runtime. It is important to migrate the
development environment first so that you have the migrated code for
deployment after you have migrated the production environment:
migration on the development and runtime. It is important to migrate the
development environment first so that you have the migrated code for
deployment after you have migrated the production environment:
1. Migrate development environment
2. Migrate production environment