User
IDs required to complete the Installation wizard
Prepare all of the user IDs required to complete your WebSphere Commerce installation.
To complete the installation
of WebSphere Commerce,
define the following IDs:
| User ID | Description | |
|---|---|---|
| Local Windows user ID | This ID
is required to install WebSphere Commerce.
This ID is also assigned to start the services for the following WebSphere Commerce components
and supporting software during the installation:
Ensure that this user ID has the user rights that are documented in DB2 Database user ID requirements. If your Windows user ID does not have Administrator authority, is longer than 20 character, or is not defined on the local machine, you cannot proceed with the installation. Notes:
|
|
| User ID | Description | |
|---|---|---|
| DB2 database user ID | This operating system ID is required
if you want WebSphere Commerce to
install DB2 Database.
This ID must not exist before you install DB2 Database through the WebSphere Commerce installation wizard. As part of the installation of DB2 Database, the user ID under which all DB2 processes run is created. To
create the DB2 user, the following information is required:
Note: The
user ID must meet DB2 Database user
ID requirements that are outlined in DB2 Database user ID requirements. |
|
| Oracle database user ID | This operating system ID is required
if you are using Oracle database with WebSphere Commerce.
This ID is the operating system user ID that owns the physical Oracle database files
on the system. This ID must exist before you installWebSphere Commerce.
During the installation of WebSphere Commerce,
you are prompted for the following information about the Oracle database
user ID:
Ensure that the Note: The user ID must meet
any Oracle database user
ID requirements that are outlined in the Oracle database documentation. |
|
| WebSphere Commerce non-root user ID | This operating system ID must exist before you install WebSphere Commerce. Ensure that you
set the password for this user ID. Otherwise, someone can access the operating system with this
unprotected user ID. This ID prevents any security exposures that might occur from running the application servers as a user with root privileges. This ID is also required to start and stop the WebSphere Commerce and WebSphere Commerce Payments application servers.Note: You must start and stop your application servers with this non-root user
ID. However, you might be prompted to input the WebSphere Application Server administrator ID and
password to stop a WebSphere Application Server profile. The WebSphere Application Server
administrator ID associated with the WebSphere Commerce instance is the same as the Configuration Manager
ID. To create the non-root WebSphere Commerce user ID, the
following information is required:
| |
- Instructions for creating the WebSphere Commerce
non-root user are provided in Creating
WebSphere Commerce users and groupsCreating
WebSphere Commerce users and groupsCreating WebSphere Commerce users and groups.
Instructions for creating the WebSphere Commerce IDs
for IBM i are provided in Creating
a user profile.
Notes:
- Windows IDs must be defined on the local machine.
IDs defined on a Windows domain server are not supported by the WebSphere Commerce installation
program.
- For installing WebSphere Commerce with a local database, all user IDs can be the same ID on the local machine.
- The database administrator ID and database user ID must meet DB2 Database user ID requirements.
Notes:
- Oracle
IDs must be defined on the
Oracle server machine. For installing WebSphere Commerce with
a local database, the Oracle server machine and WebSphere Commerce machine
are the same machine. For installing WebSphere Commerce with
a remote database, the Oracle server machine and WebSphere Commerce machine
are different machines.
- The database administrator ID and database user ID must meet any requirements for Oracle database user IDs as outlined in the Oracle database documentation.
- Oracle IDs are case-sensitive. Ensure that you have the correct case for the database administrator ID and the database user ID.
DB2 Database user ID requirements
DB2 requires that the user IDs for database
administrators and database users adhere to the following rules:
- The user ID cannot be more than 8
characters in length.
- The user ID cannot be more than 20 characters
in length.
- The user ID can contain only the
characters a to z and 0 to 9 (uppercase letters are not permitted).
- The user ID can contain only the characters
A to Z, a to z, 0 to 9.
- The user ID cannot begin with an underscore (_).
- The user ID cannot be any of the following words, in upper, lower,
or mixed case:
USERS,ADMINS,GUESTS,PUBLIC,LOCAL. - The user ID cannot begin with any of the following words in upper,
lower, or mixed case:
IBM,SQL,SYS. - The user ID cannot be the same as any Windows® service name.
- The user ID must be defined on the local machine,
and belong to the Local Administrator's group.
DB2 requires that passwords for database administrators
and database users adhere to the following rules:
- The password cannot be more than
8 characters in length.
- The password cannot be more than 14 characters
in length.
The following are the default DB2 Database user
IDs that are created during the installation:
- daswc1
- db2inst1
- db2fwc1