Setting up administrator and owner

accounts
When you run the IBM InfoSphere Information Server installation program, you must
specify the user names and passwords for administrator and owner accounts for the
program. In some circumstances, the installation program can create these accounts for
you, but depending on your system administration policies, you might want to create
these user IDs and passwords on each of the tier computers before you
install InfoSphere Information Server.
About this task
Creating administrator and owner accounts before you install InfoSphere Information
Server ensures that operating system policies, such as requiring a password change at
the first login, do not interfere with the installation program use of the accounts.
Create the accounts as local operating system accounts, lightweight directory access
protocol (LDAP), accounts, or NIS accounts.
Important

If you use LDAP, PAM, or NIS accounts, you must create these accounts before you run
the InfoSphere Information Server installation program. The installation program cannot create
these accounts.

When you create the accounts, record the user ID and password for each user. If you
choose to not use the default user IDs, the names that you choose must be distinct from
each other in the same way that the default user IDs are.
Procedure
1. On the operating systems where you install InfoSphere Information Server, make sure
that the user who installs InfoSphere Information Server can log in using the following
accounts.
The user must log in using one of these accounts to install InfoSphere
Information Server.

Table 1. User accounts that are required to install the product

Operating Accounts
system

AIX The root user account.

Linux

Solaris
 Table 1. User accounts that are required to install the product

Operating Accounts
system

Windows A user account in the local Administrators group. This account

must be one of the following types:

o A local account that is directly assigned to the

Windows local Administrators group.
o A domain account that is directly assigned to the
Windows local Administrators group.

2. AIX Solaris Linux: On the operating systems where you install each engine tier, create
the following additional accounts and record the passwords.
Note

If your installation does not include an engine tier, you can skip this step.

Table 2. Accounts that you create for an engine tier (AIX SolarisLinux)

Account Default Primary Secondary group Notes

description user group
name

Administrator dsadm dstage You customize this This user performs

for group to apply to administrative
the InfoSphere your security tasks, such as
Information model. adding new
Serverengine projects and
defining their
properties. To run
jobs, create a
separate user with
the developer role.

This account must be

an account on the
local operating
 Table 2. Accounts that you create for an engine tier (AIX SolarisLinux)

Account Default Primary Secondary group Notes

description user group
name

system. During
installation time, you
cannot specify a
Lightweight Directory
Access Protocol
(LDAP) account as
the engine
administrator account.

3. Create the following database schema accounts based on your product set and record
the passwords.
Note

When using a DB2 database, these accounts are operating system accounts. When
you use a DB2 database for the repository, the DB2 database uses the operating system
authentication for connection requests. There are no specific group membership
requirements for these accounts.

Table 3. Database schema accounts that you create on the metadata

repository tier

Products Account Default Notes

description user name

Required Metadata xmeta Important

for all repository owner
products Do not specify the DB2 instance owner
or administration server user for this
user name.

Required Staging area xmetasr Important

Table 3. Database schema accounts that you create on the metadata
repository tier

Products Account Default Notes

description user name

for all user

products
This user name must be different from
the user name that you specify for the
owner of the metadata repository
(xmeta). The xmetasr schema must be
in the same database as the xmeta
schema. Do not specify the DB2
instance owner or administration
server user for this user name.

Informati Owner of the iauser Important

on Information
Analyzer Analyzer Do not specify the DB2 instance owner
analysis or administration server user for this
database user name.

QualitySt Owner of the srduser Important

age QualityStage
Standardization Do not specify the DB2 instance owner
Rules Designer or administration server user for this
database user name. If you are installing the
repository tier, this ID must be created
before or during installation. If you use
the Database Support scripts to create
your metadata repository database,
do not create this user ID before
installing InfoSphere Information
Server. Provide the user ID and
password for the srduser during
installation. Scripts to configure this
user and its tables will be generated
 Table 3. Database schema accounts that you create on the metadata
repository tier

Products Account Default Notes

description user name

by the installation program and will be

put in
the IIS_install_path/SQLScripts direct
ory.

QualitySt QualityStage No default The InfoSphere Information Server

age Matching user name installation program does not create
(optional) Database the Match Designer results database.
You create the database before or
after the installation, as long as the
database is configured and accessible
when you use the Match Designer.

DataStag Owner of the dsodb Do not specify the DB2 instance owner
e operations or administration server user for this
(optional) database for the user name. If you are installing the
DataStage repository tier, this ID must be created
Operations before or during installation if you
Console want the installation program to
create the operations database. If you
use the Database Support scripts to
create your metadata repository
database, scripts to configure this user
and its tables will be generated during
installation and are put in
the IIS_install_path/SQLScripts direct
ory.

4. If you choose to install DB2 as part of the InfoSphere Information Server installation,
create the following additional accounts on the operating system where you install the
metadata repository tier and record the passwords.
 Table 4. Accounts that you create on the metadata repository tier before
installing DB2

Account Default Primary Secondary Notes

descripti user name group group
on

Windows db2admin db2admns None Create the operating system

account for DB2 database only.
DB2
administrat
ion server
user

AIXSolaris db2inst1 db2iadm1 None Create the operating system

account for DB2 database only.
Linux
DB2 AIX Solaris Linux:
instance
owner This account must have
read, write, and execute
permission to the
following directories:

o /tmp
o /var/tmp

AIXSolaris db2fenc1 db2fadm1 None Create the operating system

account for DB2 database only.
Linux
DB2
fenced user

5. AIX Solaris Linux: The InfoSphere Information Server installation program must have
root access. Root must have write permissions to the following directories:
o /tmp
o /var
o /var/tmp
o /usr/local/bin
6. Verify permissions for all users including root. If any directories are mounted from
network file systems such as AFS, permissions might not be adequate to perform a
successful installation.
7. Determine the names and passwords to use for the following administrator accounts:
 Table 5. Administrator accounts set up by the installation program

Account description Default user name

Administrator for IBM WebSphere wasadmin

Application Server Network Deployment

Administrator for InfoSphere Information isadmin

Server

8. Log in to each account to confirm that it functions correctly. Some operating systems are
set up to force a password change during the first login. Therefore, a manual login is
required to activate the accounts appropriately.