Filter
Top Products
Chapter 9. Installing WebSphere Commerce V5.6 165
Draft Document for Review July 28, 2004 7:33 pm 6320ch_install_56.fm
The user must be defined locally on the system and must belong to the local
Administrators group.
The user must have the following privileges assigned:
– Act as part of the operating system
– Create a token object
– Increase quotas
– Log on as a service
– Replace a process level token
The user ID must not exceed 20 characters in length.
The password must not exceed 14 characters in length.
Both user ID and password may only contain characters from the set A-Z, a-z,
0-9.
The user ID may not be any of the following: USERS, ADMINS, GUESTS, PUBLIC, or
LOCAL, regardless of case.
The user ID must not be the same as any Windows service name.
9.2 Installation
Follow the instructions in this section to install WebSphere Commerce V5.6 on a
single-tier node, with DB2 Universal Database V8.1, WebSphere Application
Server V5.0.2, and WebSphere Commerce Payments.
Note: You must log off and log in again for these privileges to take effect.
Important: If you choose to install the software from a directory on a local
hard drive, or from a network location, you must ensure that the path to the
WebSphere Application Server installation images not contain any long
directory names (names that exceed the 8.3 naming scheme). An alternative
solution is outlined in the following technote:
http://www.ibm.com/support/docview.wss?uid=swg21157884
Also, do not install from a UNC path, such as \\server\share. Map the share to
a drive letter instead.