IBM SG24-6320-00 manual Setting up aliases, Lightweight test environment

6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm

8.1 Setting up aliases

The application that we migrated contained static web content that was addressed outside the scope of the web application in order to minimize the load on the application server.

The WebSphere Commerce V5.6 Toolkit does not contain any static web projects when installed, so in order to support static web content, you must do the following:

1.Create a new Dynamic Web Project:

a.File -> New -> Dynamic Web Project

b.The New Web Project wizard appears. Ensure that Configure advanced options is checked, enter the name of the project in the Project name entry field and click Next.

We used the name static_http.

c.The J2EE Setting Page appears. Enter the prefix the Context root entry field that your static web content must use and click Next.

We needed support for all paths that are not used for WebSphere Commerce servlets, so we entered / (forward slash).

d.The Features Page appears. Ensure that none of the features are checked and click Next.

e.The Select a Page Template for the Web Site page appears. Ensure that Use a default Page Template for the Web Site is unchecked and click Finish.

f.The New Web Project wizard starts creating the web project. When finished, a prompt asking if you want to switch to the Web Perspective. Click No.

2.Edit the looseconfig.xmi file located in one of the following directories, depending on the type of test environment that you use:

–Full test environment:

<wctoolkit_home>\conf\servers\fullconfig\looseconfig.xmi

–Lightweight test environment:

<wctoolkit_home>\conf\servers\lightconfig\looseconfig.xmi

As shown in the excerpt in Example 8-1.The part in bold shows the new content. If you entered a different name for the Web Project replace static_http in the file for the one you just entered.

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