10.2 Details on configuring Web server node 1

After installing a Web server node, it needs to be configured for routing requests to the WebSphere Commerce application and for serving WebSphere Commerce specific static content.

Assuming that IBM HTTP Server has been installed on Web server node 1 as described in 8.5, Install IBM HTTP Server, the following sections point out some important configuration details with regard to serving a clustered WebSphere Commerce instance.

When a WebSphere Commerce instance is created (see the whitepaper Clustering WebSphere Commerce V6.0 with WebSphere Application Server V6.0), only one remote Web server can be automatically configured. We refer to it as Web server node 1, avoiding the term primary, as after the instance configuration is complete, it will not be different from any further Web servers serving the instance. For further Web server nodes, Web server definitions have to be added to the WebSphere Application Server configuration, and configuration files and static content have to be copied from Web server node 1 manually, as described in Chapter 11, Web server clustering. Web server node 1 serves as a model or template for setting up additional Web servers.

xxxx