Migrate > Migrating WebSphere Commerce > Prepare to migrate WebSphere Commerce

Prepare the WebSphere Commerce environment

Before beginning the first phase of migration, you need to ensure that the WebSphere Commerce environment is ready for migration.

Procedure

1. Clean up the database, using the Database Cleanup utility. In particular, it is recommended that you clean up all orders in the trash can if you have the OrderTrashCan feature enabled. If you do not clean up the database, you might encounter performance issues during and after migration.

   To remove orders in the trash can:

   1. Follow the steps in Delete order objects, with markfordelete as the value of the type parameter.

2. Verify the data in the KEYS table is valid. In particular, ensure that any rows you have added for custom tables have valid data.

3. Free enough disk space on the system to accommodate a backup of the WebSphere Commerce v5.6.1 or 6.0 database.

4. As the WebSphere Commerce non-root user, increase the file handle limit with the following command:

   ulimit -n 8192
   

   You must run the WCIM migration wizard or wcim_ant script in the same command window that you ran the ulimit command in. The ulimit setting is lost (and run this step) if you close this command window.

5. Drop or disable custom constraints in the WebSphere Commerce Version 5.6.1 or 6.0 environment before running the migration script. The following table summarizes the customization actions that are recommended for the customization, depending on the table you have customized:

   	WebSphere Commerce tables recreated during migration	Other WebSphere Commerce tables	Custom tables
   Foreign key	A	A	A
   Index	B	D	A
   Triggers, Procedure, View, Summary table, Function, and Methods	C	E	E

   Where:

   A

   WebSphere Commerce can migrate this customization. Leave the customization object as-is.

   B

   • WebSphere Commerce can migrate this customization. Leave the customization as-is.

   • You need to reapply this customization after migration.

   C

   You need to reapply this customization after migration. The migration script does not migrate it, because JDBC has no corresponding API.

   D

   If the index has been customized as per the Database schema object naming conventions, WebSphere Commerce can migrate this customization – leave it as-is. Otherwise, manually drop the custom index before migration and reapply this custom index after migration.

   E

   If the customization does not refer to default WebSphere Commerce recreated tables, it can be migrated normally – leave it as-is. Otherwise, drop the customization manually before database migration and reapply this customization after database migration.

   The following table lists the WebSphere Commerce tables that are recreated during migration:

   	From WebSphere Commerce Version 5.6.1	From WebSphere Commerce Version 6.0
   	BUSAUDIT, CACHEIVL, CATENCALCD, CATGPCALCD, EMLMSG, ICMREGDESC, ORDERS, ORGENTITY, PX_PROMOTION, REFKEYS, STOREENTDS	BUSAUDIT, CATENTRYATTR, GEONDDS, INVCNF, STLOCATTR, STLOCDS
   	CATENCALCD, CATGPCALCD, EMLMSG, ORGENTITY, REFKEYS	CATENTRYATTR, GEONDDS, INVCNF, PPCBATCH, STLOCATTR, STLOCDS
   	BUSAUDIT, CATENCALCD, CATGPCALCD, EMLMSG, ICMREGDESC, ORDERS, ORGENTITY, PX_PROMOTION, REFKEYS, STOREENTDS	BUSAUDIT

   Any customized foreign key constraints that have been added to the WebSphere Commerce environment are handled automatically by the migration script. The script drops these foreign key constraints at the beginning of the database tier migration. The foreign key constraints are added back at the end of the database tier migration.

   Any customized indexes that have been added to the WebSphere Commerce environment are handled automatically by the migration script. The script drops these customized indices at the beginning of the database tier migration and adds them back at the end of the database tier migration.

   • Use the drop action for these custom constraints

   • Use the drop or disable actions for these custom constraints

6. Verify the contents of the WebSphere Commerce configuration file are identical between the following two files:

   • The master configuration that is managed by the Configuration Manager, instance.xml

   • The configuration file that is used at runtime, wc-server.xml.

   See the WebSphere Commerce configuration file topic for more information about these files.

Previous topic:

Upgrade software

Next topic:

Update the DB2 database configuration

+

Search Tips   |   Advanced Search