332 WebSphere Commerce V5.4 Handbook, Architecture and Integration Guide
11.1 Remote Web server installation
This section describes how to install an IBM HTTP Server remote Web server for
use with WebSphere Commerce.
11.1.1 Install IBM HTTP Server
To install the IBM HTTP Server on the remote Web server, complete the following
high-level steps:
1. Preinstallation for the IBM HTTP Server.
Refer to 10.4.1, IBM HTTP Server preinstallation on page 290.
2. Install the IBM HTTP Server on the remote Web server.
Refer to 10.4.2, Install IBM HTTP Server on page 291.
3. Configure the IBM HTTP Server.
When configuring the httpd.conf for SSL support, we copied the httpd.conf
from the existing two-tier Web server and modified the host name. We used a
backup copy called httpd.conf.ssl that does not include the WebSphere
Commerce instance aliases and other directives. Alternatively, you can follow
the procedure documented in the
Additional Software Guide, IBM WebSphere
Commerce V5.4 Professional and Business Edition for Windows
. The key
issue here is to ensure that SSL is configured and working before proceeding.
Refer to 10.4.3, Configure IBM HTTP Server on page 291.
4. Verify the IBM HTTP Server.
Refer to 10.4.4, Verify IBM HTTP Server installation on page 295.
11.1.2 Install WebSphere plug-in
In order for the IBM HTTP Server to redirect requests to the WebSphere
Application Server, the WebSphere plug-in needs to be installed on the IBM
HTTP Server.
The WebSphere plug-in installation on the remote Web server system is
organized as follows:
Install the WebSphere plug-in
Post-installation of the WebSphere plug-in
Install WebSphere Application Server V4 FixPak 3 (V4.0.3)
Chapter 11. Windows: Add a remote IBM HTTP Server 333
Install the WebSphere plug-in
To install the WebSphere plug-in on the remote Web server, do the following:
1. Ensure that the user that is installing the WebSphere Application Server
plug-in has act as part of the operating system user rights.
2. Stop the following Windows services:
IBM HTTP Server
IBM HTTP Administration
3. Run Setup from the root of the WebSphere Application Server CD.
4. We selected the following options during the installation:
Select
Custom Installation.
When prompted to choose the components, select the
Webserver
Plugins
, and IBM JDK 1.3.0 components only.
When prompted to choose the Web server plug-in, select the
IBM HTTP
Server
.
We changed the installation path to c:\ibm\was to match the installation
path of the WebSphere Application Server installation path on system B.
5. When the installation is finished, restart the system.
Post-installation of the WebSphere plug-in
In order to verify that the WebSphere plug-in has been successfully installed, do
the following:
1. Open the httpd.conf file on the remote Web server system.
Note: If the WebSphere Application Server and the WebSphere
Application Server plug-in are not installed in the same path on the two
machines (remote Web server and application server), then you will need
to change the paths in the plugin-cfg.xml file to reflect the installation path
of the plug-in after copying it to the Web server machine.
For this reason, we recommend keeping the WebSphere plug-in path on
the Web server the same as the installation path of the application server.
Note: In the wssetup.log file, there may be errors after the WebSphere
plug-in is installed. If there are, continue with the rest of the installation and
configuration.

Get WebSphere Commerce V5.4 Handbook: Architecture and Integration Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.