WebSphere Commerce Version 8.0.1.0 or later

Completing the staging migration

After you migrate the staging database and your custom assets, complete remaining updates to your staging database.

Procedure

  1. Update your SRCHCONF to contain the new version 8.0 preprocess directory.
    1. Connect to your database.
    2. Run the following SQL command:
      update SRCHCONF set CONFIG = replace(CONFIG, 'old_PreProcessdir', 'new_PreProcessdir');
      Where:
      old_PreProcessdir
      The preprocess directory of the version 7.0 search server.
      new_PreProcessdir
      The preprocess directory of the version 8.0 search server.
  2. Update your SRCHCONFEXT tables to contain the new search web server host name: by running the following command:
    update SRCHCONFEXT set CONFIG = replace(CONFIG, 'old_hostname', 'new_hostname');
    Where:
    old_hostname
    The fully qualified host name of the version 7.0 search web server.
    new_hostname
    The fully qualified host name of the version 8.0 search web server.
  3. If you used catalog filters and pricing rules in version 7.0 and plan on using those functions in version 8.0, you need to enable them manually.
    1. Set the VALUE for the wc.search.entitlement property to 1 by using the following SQL command:
      UPDATE STORECONF SET VALUE='1' WHERE STOREENT_ID=STOREENT_ID AND NAME='wc.search.entitlement';
      Where:
      STOREENT_ID
      The STOREENT_ID for your store.
    2. Repeat for all applicable STOREENT_ID entries.
  4. If you customized any searchable attributes in version 7.0 and plan to use them in version 8.0, you must update KEYS table for the SRCHATTR table by running the following SQL command:
    update keys set counter = case when (select max(srchattr_id) from srchattr) > 
    counter then (select max(srchattr_id) from srchattr) else counter end where tablename = 'srchattr'
  5. Update the database SITE table by using the updateSiteRT ANT task.
    1. Log on as the WebSphere Commerce non-root user.
    2. Go to the following directory:
      • WC_installdir\bin
    3. Run one of the following commands:
      • Windowsconfig_ant.bat -buildfile WC_installdir/migration/xml/updateSiteTable.xml updateSiteRT -DinstanceName instanceName -DdbUserName dbUserName -DdbUserPassword dbUserPassword -DdbName dbName
      • AIXLinuxconfig_ant.sh -buildfile WC_installdir/migration/xml/updateSiteTable.xml updateSiteRT -DinstanceName instanceName -DdbUserName dbUserName -DdbUserPassword dbUserPassword -DdbName dbName
      instanceName
      The WebSphere Commerce instance name.
      dbUserName
      The database user name of the migrated database.
      dbUserPassword
      The database user password of the migrated database.
      dbName
      This parameter is only for remote databases and refers to the fully qualified host name, port, and database name of the migrated database, for example:
      • DB2hostname:port/database name
      • Oraclehostname:port:database name
    4. After the command completes, review of the following log to ensure that the command ran successfully:
      • WC_installdir\bin\updateServerSiteTable.log
  6. If you are migrating from WebSphere Commerce Version 7 Feature Pack 1, Feature Pack 2, Feature Pack 3, Feature Pack 4, Feature Pack 5, or Feature Pack 6, and you have configured workspaces and have already run the update workspaces schema script after migrating, run the following SQL statement in each workspace write schema:
    • Cloudscape:
      ALTER TABLE PAGELAYOUT ALTER COLUMN PAGELAYOUTTYPE_ID NULL;
    • DB2:
      ALTER TABLE PAGELAYOUT ALTER COLUMN PAGELAYOUTTYPE_ID DROP NOT NULL;
      
      CALL SYSPROC.ADMIN_CMD ('REORG TABLE PAGELAYOUT');
    • Oracle:
      ALTER TABLE PAGELAYOUT MODIFY PAGELAYOUTTYPE_ID NULL;

Results

  • Business users can start working on the version 8.0 staging or authoring environment. However, they must not commit any work items.
  • Site administrators must not run any staging utilities.