34 IBM Workplace Collaboration Services: Release 2.5 Deployment Guide
representative. If you are an IBM Business Partner, we encourage you to learn
more about the “Managed Availability” Workplace Managed Client at:
http://www.lotus.com/partnerswmc
2.5 Installation work sheets
This section provides checklists of key administrator names and preinstallation
activities.
Administrator names and passwords work sheet
Table 2-3 provides an administrator names and passwords work sheet.
Table 2-3 Administrator names and passwords work sheet
Information
needed
Description Name and
password for your
site
1 IBM AIX 5L, Linux,
or Sun Solaris
administrator
Create a user with administrative privileges who can
install software on this server. Log in as this user
when you are ready to install Workplace
Collaboration Services.
2Microsoft Windows
administrator
Create a user with administrative privileges who can
install software on this server. Log in as this user
when you are ready to install Workplace
Collaboration Services.
3 IBM i5/OS
administrator
Create a user with administrative privileges who can
install software on this server. The user must have at
least *ALLOBJ, *IOSYSCFG, and *JOBCTL special
authorities. Log in as this user when you are ready to
install Workplace Collaboration Services.
4 Workplace
Collaboration
Services
administrator
Decide on a name and password for the Workplace
Collaboration Services administrator. If you will
connect Workplace Collaboration Services to an
existing LDAP directory, this user name and
password must already exist in your user directory.
You will be prompted for this administrator name
during the Workplace Collaboration Services
installation. This user is the same name that you will
specify for user #13.
Before connecting a DBMS to Workplace Collaboration Services
Chapter 2. Planning 35
5 Database
administrator
A user name and password with administrator access
to the DBMS server; typically, you will use the account
created during the DBMS server installation. In DB2
UDB, the standard database administrator account is
called db2admin in Windows and db2inst1 in AIX 5L,
Linux, and Solaris. In Oracle, it is called system, and
in Microsoft SQL Server it is called SA. Any account
with administrative privileges can be used.
6 Database client A user name and password with authority to
administer remote databases on the DBMS server;
normally, you will use the account created during the
client installation (typically, this account receives the
same name as is used on the DBMS server). This
user does not have to be listed in the LDAP directory.
7 Workplace
Collaboration
Services
application data
source user
DB2 UDB; only If you do not want Workplace
Collaboration Services using the DB2 database
administrator (db2admin) account to access the data
source, create a separate DB2 user account for this
purpose. This user is not needed for Oracle and
Microsoft SQL Server, because authentication is
handled differently.
8 IBM WebSphere
Portal database
user
The user ID and password for the administrator of the
WebSphere Portal wps50 database. For DB2 UDB,
this can be the DB2 administrator or another user. For
Oracle and Microsoft SQL Server, create a user with
the name WPSDBUSR and assign a password.
9 WebSphere
Member Manager
WebSphere Portal
database user
The additional user ID and password for the
administrator of the WebSphere Portal database. For
DB2 UDB, this should be the same as user #8. For
Oracle and Microsoft SQL Server, create a user with
the name WMMDBUSR and assign a password.
Information
needed
Description Name and
password for your
site

Get IBM Workplace Collaboration Services: Release 2.5 Deployment Guide now with O’Reilly online learning.

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