
Migrating IBM Websphere Commerce Version 7 Feature Pack 6 to HCL Commerce Version 9
The following section outlines the high-level steps that you must complete
to migrate to HCL Commerce Version 9.0. Begin by migrating your development environment, which
includes your development database, custom assets, storefront, and search application. With a
successfully migrated development environment, you can migrate your production databases, and
deploy your migrated assets to your HCL Commerce Version 9.0 production environments.
Before you begin
- Review Planning to migrate HCL Commerce.
- Upgrade your IBM Websphere Commerce Version 7 environments to Feature Pack 6, and enable all features.
- Update your development and production databases to one of the following versions.
- Update to NIST SP 800-131A security standards.Note: HCL Commerce Version 9 only permits a 32-bit merchant key. This step will migrate your existing database to 32-bit encryption prior to migrating to version 9. If you do not take this step, the version 9 application will not be able to read encrypted data (for example passwords or payment data) from the migrated database.
- From your Feature Pack 6 environment, ensure that all tasks are approved and all workspaces are closed.
- From your Feature Pack 6 environment, use the following utilities to ensure that your staging
database and production database are synchronized:Note: Once the staging and production databases are in sync, a content-freeze must be in effect until the live production database is migrated.
- Install your HCL Commerce Version 9 development environment, including the latest maintenance package.
- Plan and deploy your HCL Commerce Version 9 production environment, including your staging environment and the latest maintenance package.