6320ch_post_migration.fm

Draft Document for Review July 28, 2004 7:33 pm

12.1 Post migration steps for IBM HTTP Server

After migrating WebSphere Commerce, there are still some steps that require to be done manually. These steps will vary from one environment to another depending if it is a single or a multi-node environment.

12.1.1 Migrating static content

The static HTML content must be moved over manually. This is done simply by copying all the content from the HTTP document root on WebSphere Commerce Suite V5.1 system to the HTTP document root on WebSphere Commerce V5.6 system. In our example we had our document root set to:

d:\static_http

This directory was copied from WebSphere Commerce Suite V5.1 system to WebSphere Commerce V5.6 system.

Note: This should be enough as the document root will already be set to the correct directory (IBM HTTP Server settings are preserved, see Updating configuration)

If the document root is not set, it can be set in the manually in the IBM HTTP Server configuration file. The configuration of the IBM HTTP Server is stored in:

<ihs_home>\conf\httpd.conf

in our example:

D:\WebSphere\IBMHttpServer\conf\httpd.conf

The document root is added as described below:

DocumentRoot "d:/static_http/content/htdocs"

The IBM HTTP Server needs to be restarted in order for the changes to take effect.

12.1.2 Updating configuration

The WCIM tool will migrate the IBM HTTP Server configuration automatically, if IBM HTTP Server is on WebSphere Commerce V5.6 system, installed locally on the same node. All customized configuration in the configuration file (httpd.conf) will be migrated, assuming that no customized configuration exists in the blocks tagged as shown in Example 12-1.

230Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Page 248
Image 248
IBM SG24-6320-00 manual Post migration steps for IBM Http Server, Migrating static content, Updating configuration