Preparing 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

Back up, then restore your database.
Before you migrate, you need to backup the database from the previous WebSphere Commerce Version 5.6.1 or Version 6 database node, then restore the database backup to the WebSphere Commerce Version 7 database node. The WebSphere Commerce migration script will operate on the restored database only.
- Depending on the version of DB2 you are using, refer to one of the following:
  - Back up your DB2 Version 9.5 database and Restore your DB2 Version 9.5 database.
  - Back up your DB2 Version 9.7 database and Restore your DB2 Version 9.7 database
- See the database vendor's user manual for information about backup and restore procedures.
  Note: When you restore the Oracle database, the character sets are automatically converted to AL32UTF8.
- See Backing up and restoring IBM i database.
On the restored database, ensure that the data in your KEYS table is valid. In particular, ensure that any rows you have added for custom tables have valid data.
Free enough disk space on your system to accommodate a backup of the WebSphere Commerce Version 5.6.1 or 6.0 database.
As the WebSphere Commerce root user, increase the file handle limit with the following command:
```
ulimit -n 8192
```
Note: 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 you must run this step) if you close this command window.

In the restored database, drop or disable custom constraints. The following table summarizes the customization actions that are recommended for your 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 ../../com.ibm.commerce.database.doc/refs/rdbnamingconventions.html, WebSphere Commerce can migrate this customization – leave it as-is. Otherwise, you need to 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, you need to 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.

DB2 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

Ensure that the contents of your Updating the WebSphere Commerce configuration file are identical between the following two files:
- The master configuration that is managed by the Configuration Manager, instance_name.xml
- The configuration file that is used at runtime, wc-server.xml.
See the Updating the WebSphere Commerce configuration file topic for more information about these files.