Completing the staging migration
After you migrate the staging database and your custom assets, complete remaining updates to your staging database.
Procedure
-
Update your SRCHCONF to contain the new version 8.0 preprocess directory.
-
Update your SRCHCONFEXT tables to contain the new search web server host name: by running the
following command:
Where:update SRCHCONFEXT set CONFIG = replace(CONFIG, 'old_hostname', 'new_hostname');
- 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.
-
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.
-
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'
-
Update the database SITE table by using the updateSiteRT ANT task.
-
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;
- Cloudscape:
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.