Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Migrating
Before you migrate WebSphere Commerce, review this information for an overview of the migration process.
Taking your first steps after WebSphere Commerce migration
After you have migrated your database and application tiers, migrate applicable WebSphere Commerce features, functions and customizations you have performed.
Reusing custom staging triggers
If you created custom tables with staging triggers in a previous version of WebSphere Commerce, you can continue to use your custom triggers. Run the provided scripts to allow the unchanged custom triggers to continue to use the KEYS table to maintain the primary key values of the STAGLOG table.

Reusing custom staging triggers

If you created custom tables with staging triggers in a previous version of WebSphere Commerce, you can continue to use your custom triggers. Run the provided scripts to allow the unchanged custom triggers to continue to use the KEYS table to maintain the primary key values of the STAGLOG table.

Note: Alternatively, you can update your existing staging triggers for better performance and scalability. For an example of how to update your trigger, see Staging trigger example.

Procedure

Connect to the staging database.
- db2 connect to stagingdbuser db_user using db_password
- sqlplus db_user/db_password@stagingdb
Run the following script:
- db2 -td# -vf WC_installdir/schema/db2/wcs.stage.heteroTriggerSupport.sql
- sqlplus @WC_installdir/schema/oracle/wcs.stage.heteroTriggerSupport.sql