Filter
Top Products
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm
208 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
approach would result in minimum hassle. All the database migration tasks were
done in WebSphere Commerce V5.6 system. Refer to Appendix C, “Migration
scripts” on page 255 for details on custom scripts behavior.
Here is the high level steps and order required to migrate the WebSphere
Commerce database:
1. Migrating the database
2. Choosing the master catalog
3. Migrating the encrypted data
11.3.1 Migrating the database
Before the migration can take place ensure that the steps outlined in
Section 10.3, “Database preparation” on page 188 has been completed.
It is recommended to understand the behavior of the database migration tool
before proceeding with the database migration. The behavior of the database
migration tool is described in Appendix C, “Migration scripts” on page 255.
The migration script can check if everything is correct before it makes any
changes. This can be done with precheck option set. This executes the
WebSphere Commerce V5.6 migration script in “read-only” mode.
The migration script migratedb.bat for the database is located in the following
directory:
<wc56_home>\bin\
In our example:
D:\WebSphere\CommerceServer56\bin
The script receives the following parameters:
-dbtype <database_type>
-dbname <database_name>
-dbuser <user>
-dbpass <password>
-from <version>
-instance <instance_name>
Note: The custom migration scripts mentioned in this book are not necessary
to accomplish the WebSphere Commerce migration, we created those scripts
with the only purpose of automating mainly the pre and post migration tasks.
These scripts become more useful if you have to repeat these steps several
times when you have several environments to migrate.