Preparing to migrate your IBM Websphere Commerce Version 7 Feature Pack 7 production database

Now that you have migrated your development environment and deployed your containers in HCL Commerce Version 9, you can now build and deploy your customizations, and migrate your IBM Websphere Commerce Version 7 database to HCL Commerce Version 9.

Migrating the production database is broken up into two parts. First, you back up and restore your IBM Websphere Commerce Version 7 production database to your HCL Commerce Version 9 environment, where you can test your container technology with an offline version of your IBM Websphere Commerce Version 7 production database. After your testing is complete, you can execute the second part of the migration, which is to put your IBM Websphere Commerce Version 7 live store in maintenance mode, and point your HCL Commerce Version 9 environment to your live IBM Websphere Commerce Version 7 database, then migrate that database.

Before you begin

  1. By using the WCB tool, build your migrated custom assets into input packages
  2. Deploy your customizations to your HCL Commerce application.

Procedure

  1. Ensure that the data in your KEYS table is valid in your IBM Websphere Commerce Version 7 database. In particular, ensure that any rows you added for custom tables have valid data.
  2. Back up your IBM Websphere Commerce Version 7 production database:
  3. Restore the backup of your IBM Websphere Commerce Version 7 production database to your HCL Commerce Version 9 production database server.
  4. DB2 Ensure that your SYSADMIN user has DBADM authority.
  5. DB2Update the restored database configure with the following configuration:
    Note:
    • The sum of the values for the logprimary and logsecond parameters must be less than 256.
    • Record your original database parameter values to restore them once the migration is complete.
    DB2 parameter Value
    locklist 2400
    indexrec RESTART
    logfilsiz 8192*
    logprimary 150
    logsecond 100
    pckcachesz 4096
    catalogcache_sz 4096
    locktimeout 45
    * If you encounter the following error, indicating that the transaction log for the database is full, work with a database administrator to ensure that your log file size can be expanded to accommodate a larger log.
    SQLCODE=-964, SQLSTATE=57011
    • To see database configurations:
      db2 get db cfg for database_name
      For example:
      db2 get db cfg for mall
    • To update database configurations:
      db2 update db cfg for database_name using parameter_name parameter_value
      For example:
      db2 update db cfg for mall using locklist automatic logprimary 150 logsecond 100 pckcachesz automatic