304 WebSphere Commerce V5.4 Handbook, Architecture and Integration Guide
The WebSphere Application Server installation, configuration, and verification
are now complete.
10.6 WebSphere Commerce installation
This section describes the steps necessary to install WebSphere Commerce
V5.4 and WebSphere Commerce Business Edition FixPak V5.4.0.2.
10.6.1 Install WebSphere Commerce V5.4
This section describes the high-level steps to install IBM WebSphere Commerce
V5.4, Business Edition for Windows.
1. Ensure the following Windows services are stopped:
DB2 and supporting services
IBM WS AdminServer
2. Create a Windows user with administrator authorities that WebSphere
Commerce will run under as a Windows service.
Tip: Before you proceed to the WebSphere Commerce installation, make a
backup copy of the httpd.conf. For example, we made a copy called
httpd.conf.was (WebSphere Application Server tested).
Note: A prerequisite of the WebSphere Commerce installation is that your
logon Windows user ID has no more than 8 characters. We could not find a
reason for this.
A workaround is that you open a Windows command prompt as a different
user and start the setup as follows:
Start -> Programs -> Accessories
Right-click Command Prompt.
Select Run as different user and click Apply.
Click Start -> Programs -> Accessories -> Command Prompt.
Type in the name and password of the user you want to use for the
installation, for example wcsadmin.
At the command prompt, go to the directory where the WebSphere
Commerce setup program is and start it.
Chapter 10. Windows two-tier remote DB2 database server runtime 305
3. Insert the WebSphere Commerce V5.4 CD 1 and run Setup. Accept the
defaults unless otherwise noted.
Note: Another prerequisite of the WebSphere Commerce installation is to
have a Windows user with some special rights.
If you do not want make the WebSphere Commerce user part of the
administration group, you can create a new group and assign the needed
rights to this new group.
To assign rights to a person or group:
Start -> Settings -> Control Panel -> Administrative Tools.
Select Local Policies -> User Rights Assignment.
At least one right is necessary: Act as part of the operating system.
4. Choose the Commerce Server and Web Server configuration, since you
installed the database server remotely as seen in Figure 10-2.
Figure 10-2 WebSphere Commerce component selection
Note: You will see a warning message: You need to increase your
virtual memory. It should be twice as much RAM.
This is not a requirement, but only a recommendation. It may not apply if
you have a system with a large amount or RAM (for example, 2 GB).
306 WebSphere Commerce V5.4 Handbook, Architecture and Integration Guide
5. When prompted for the product destination, we entered c:\ibm\wc.
6. Towards the end of the installation, the install will prompt you to insert CD 2.
This will install WebSphere Application Server e-fixes required for
WebSphere Commerce V5.4 GA.
7. When the installation program finishes, restart the system.
8. Review the WebSphere Commerce installation log, WCInstall.log, found by
default in the root of the target drive of installation.
10.6.2 Install WebSphere Commerce FixPak V5.4.0.2
This section describes where to download and install the WebSphere Commerce
Business Edition FixPak V5.4.0.2. It includes some fixes to some problems we
identified as part of this redbook project.
The WebSphere Commerce Business Edition FixPak V5.4.0.2 download
includes the following:
This PDF describes what was fixed and how to install the FixPak.
This zip file contains fixes for WebSphere Commerce V5.4. After installing the
FixPak, the level of WebSphere Commerce should be V5.4.0.2.
The high-level steps to download and install the FixPak are as follows:
1. Ensure that the following Windows services are stopped prior to the FixPak
Note: In our example, we installed additional WebSphere Application
Server V4 FixPak 3, which includes the e-fixes needed for WebSphere
Commerce Business Edition FixPak V5.4.0.2.
The WebSphere Commerce installer will attempt to update the WebSphere
Application Server V4.0.2 e-fixes and state incorrectly information about
prereq levels. This is because in our scenario we installed a higher level of
the WebSphere Application Server V4 FixPak 3. Ignore the message and
continue. This is also true for DB2.
Note: We recommend that you read the WC5402_Readme.pdf. It contains
a listing of the defects fixed as well as detailed installation procedures.

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

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.