Note
Before using this information and the product it supports, read the information in Notices on
page 115.
Copyright IBM Corporation 1999, 2012.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . v
Conventions and terminology . . . . . . . . v
Publications and related information . . . . . . v
Web resources . . . . . . . . . . . . . viii
How to send your comments . . . . . . . . ix
Checklist: Installing IBM Systems
Director Server . . . . . . . . . . . xi
Checklist: Installing agents . . . . . xiii
Chapter 1. Installing IBM Systems
Director . . . . . . . . . . . . . . . 1
Installation overview . . . . . . . . . . . 1
Installing IBM Systems Director Server . . . . . 2
Acquiring IBM Systems Director Server . . . . 3
Acquiring an installation DVD . . . . . . 4
Downloading the installation package . . . . 4
Preparing the management server . . . . . . 4
Installation worksheet for the management
server. . . . . . . . . . . . . . . 4
Preparing the database application . . . . . 7
Preparing to install IBM Systems Director
Server on Windows . . . . . . . . . . 9
Preparing firewalls and proxies for IBM
Systems Director. . . . . . . . . . . 10
Installing firmware and device drivers . . . 11
Running the Pre-Installation Utility (PIU) . . . 15
Running the IBM Systems Director
Pre-Installation Utility on the management
server (Windows) . . . . . . . . . . 16
Windows pre-installation checks . . . . . 17
Installing IBM Systems Director on the
management server. . . . . . . . . . . 23
Installing IBM Systems Director Server on
Windows . . . . . . . . . . . . . 23
Tips for creating the server response file for
IBM Systems Director Server . . . . . . 29
Verifying the successful installation of IBM
Systems Director on the management server . . 30
Configuring IBM Systems Director Server after
installation . . . . . . . . . . . . . 30
Switching the database that IBM Systems
Director uses . . . . . . . . . . . . 31
Database configuration attributes . . . . . 33
Tips for database user authorities and
passwords . . . . . . . . . . . . . 42
Logging on to IBM Systems Director Server
for the first time . . . . . . . . . . . 48
Restarting IBM Systems Director Server . . . 49
Enabling Dynamic IP support . . . . . . 50
Configuring IBM Systems Director plug-ins . 52
Configuring the command-line interface . . . 53
Reviewing Microsoft Internet Explorer security
options . . . . . . . . . . . . . . 54
Configuring IP address properties . . . . . 55
Changing IBM Systems Director server health
settings . . . . . . . . . . . . . . 56
Recovering from a failed installation of IBM
Systems Director Server 6.3.x . . . . . . . 58
Chapter 2. Installing agents. . . . . . 61
Running the Pre-Installation Utility on an agent
(Windows). . . . . . . . . . . . . . . 62
Installing Common Agent . . . . . . . . . 63
Preparing for a Common Agent managed system 64
Obtaining licenses for Common Agent . . . 64
Preparing to install Common Agent on
Windows . . . . . . . . . . . . . 64
Installing agents using the Agent Installation
Wizard . . . . . . . . . . . . . . . 65
Installing Common Agent manually . . . . . 68
Installing Common Agent on Windows . . . 69
Installing Platform Agent . . . . . . . . . . 76
Preparing for a Platform Agent managed system 77
Preparing to install Platform Agent on
Windows . . . . . . . . . . . . . 77
Installing agents using the Agent Installation
Wizard . . . . . . . . . . . . . . . 78
Installing Platform Agent manually . . . . . 81
Installing Platform Agent on Windows . . . 82
Verifying the successful installation of an IBM
Systems Director agent . . . . . . . . . . 89
Chapter 3. Preparing agentless
managed systems . . . . . . . . . . 91
Preparing to manage service processors with IBM
Systems Director. . . . . . . . . . . . . 91
Preparing to manage an IBM BladeCenter chassis
using IBM Systems Director Server on a non-blade
server . . . . . . . . . . . . . . . . 98
Preparing to manage an IBM BladeCenter chassis
using IBM Systems Director Server on a blade
server . . . . . . . . . . . . . . . . 99
Preparing Windows managed systems . . . . . 101
Preparing Windows Server 2003 managed
systems . . . . . . . . . . . . . . 101
Preparing Windows Server 2008 managed
systems . . . . . . . . . . . . . . 102
Preparing Windows Vista managed systems . . 102
Preparing to manage an agentless managed
system running Windows Vista . . . . . 103
Preparing a Windows Vista system for
Platform Agent managed system
management . . . . . . . . . . . 104
Preparing a Windows Vista system for
Common Agent managed system
management . . . . . . . . . . . 105
Copyright IBM Corp. 1999, 2012 iii
Preparing Windows XP managed systems . . . 106
Chapter 4. Uninstalling . . . . . . . 109
Uninstalling IBM Systems Director on Windows 109
Uninstalling IBM Systems Director using the
Windows Add or Remove Programs feature . . 110
Uninstalling IBM Systems Director using the
isduninst command . . . . . . . . . . 112
Notices . . . . . . . . . . . . . . 115
Trademarks . . . . . . . . . . . . . . 117
iv Installing with managed IBM DB2 database on Windows
About this publication
This publication provides information about installing IBM
products
Implementing high availability
IBM Redbooks
publications
www.ibm.com/redbooks/
You can also search this Web page for documents that focus on IBM Systems
Director and specific IBM hardware; such documents often contain
systems-management material. The following book is available for IBM Systems
Director V6.1:
Implementing IBM Systems Director 6.1
Tip: Be sure to note the date of publication and to determine the version of IBM
Systems Director software to which the Redbooks publication refers.
About this publication vii
Further information
See Searching knowledge bases for more resources for further information about
IBM Systems Director.
Web resources
Listed here are the websites and information center topics that relate to IBM
Systems Director.
Websites
v IBM Systems Director
www.ibm.com/systems/management/director/
View the IBM Systems Director website on ibm.com
www.ibm.com/servers/eserver/serverproven/compat/us/
View the IBM ServerProven website to learn about hardware compatibility of
IBM System x
and BladeCenter
, Power Systems
)
www.ibm.com/developerworks/forums/forum.jspa?forumID=759
View the IBM Systems Director Forum website on ibm.com to discuss
product-related issues that pertain to IBM Systems Director, IBM Systems
Director UIMs, and IBM Systems Director extensions. This website includes a
link for obtaining the forum by using a Rich Site Summary (RSS) feed.
v IBM Systems Director 6.x SDK Forum
www.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0
View the IBM Systems Director 6.x SDK Forum website to discuss issues that
pertain to the IBM Systems Director Software Development Kit (SDK). This
website includes a link for obtaining the forum by using a Rich Site Summary
(RSS) feed.
v IBM Systems Forums
www.ibm.com/developerworks/forums/dw_esforums.jsp
View the IBM Systems Forums website on ibm.com to learn about various
forums that are available to discuss technology-related and product-related
issues that pertain to IBM Systems hardware and software products. This
website includes a link for obtaining the forum by using a Rich Site Summary
(RSS) feed.
How to send your comments
Your feedback is important in helping to provide the most accurate and highest
quality information.
If you have any comments about this book or any other IBM Systems Director
publication, go to the IBM Systems Director information center Web site at
publib.boulder.ibm.com/infocenter/director/pubs/index.jsp. There you will find
the feedback page where you can enter and submit comments.
About this publication ix
x Installing with managed IBM DB2 database on Windows
Checklist: Installing IBM Systems Director Server
Use this checklist to guide you through the installation process.
1 Prepare the management server.
__ 1. Reference the installation worksheets (4.
__ 2. Prepare the database application (7).
__ 3. Prepare firewalls and proxies on the management server (10).
__ 4. Prepare the management server (9).
__ 5. Run the Pre-Installation Utility (15.
2 Install IBM Systems Director Server.
__ 1. Install IBM Systems Director Server (23).
__ 2. Verifying the management server installation. (30
3 Configuring after installation (logging in for the first time, switching databases, and more)
__ 1. Perform some post install configuration of IBM Systems Director Server (30).
Copyright IBM Corp. 1999, 2012 xi
xii Installing with managed IBM DB2 database on Windows
Checklist: Installing agents
Use this checklist to guide you through the installation process.
1 Prepare your managed systems.
__ 1. Run the Pre-Installation Utility (62.
__ 2. Prepare systems for Platform Agent (77).
__ 3. Prepare systems for Common Agent (64).
__ 4. If relevant, prepare any agentless managed systems for discovery and
management by IBM Systems Director (91).
2 Install the agents.
__ 1. Use the Agent Installation Wizard to deploy agent packages to your
managed systems (65).
Copyright IBM Corp. 1999, 2012 xiii
xiv Installing with managed IBM DB2 database on Windows
Chapter 1. Installing IBM Systems Director
If you are installing IBM Systems Director for the first time, use these instructions
to install the latest version on your system.
This procedure assumes that your system has no version of IBM Systems Director
or IBM Director and therefore, there is nothing to upgrade or migrate. If you are
upgrading or migrating data from a previous version of IBM Systems Director, see
Upgrading and migrating IBM Systems Director.
Related tasks:
Upgrading and migrating Systems Director
Related reference:
Installation and migration troubleshooting
Installation overview
Before you install IBM Systems Director, understand the overall installation process
and components.
Installation process
The graphic below illustrates the overall installation process. After you prepare
your existing environment for IBM Systems Director and determine how you plan
to use the product, you must prepare your system to install the management
server. There is a Pre-Installation Utility, installation worksheets, and tasks to help
prepare your server for a smooth installation process. Keep in mind this overall
flow as you progress through the pre-installation and installation tasks. After you
verify that the management server is installed successfully, there are tasks to
configure the management server and tailor its settings to your needs. Similar tasks
are required to install the agent on managed systems.
Prepared environment
Acquiring Systems
Director
Configuring after
installation
Preparing to install
Installing
management server
Verify success
Check for updates
Verify success
Check for updates
Installing agents
F
M
Q
0
5
5
8
-
0
After IBM Systems Director is installed and configured for the first time, you can
continue to discover new systems, collect inventory, and configure plug-ins.
Copyright IBM Corp. 1999, 2012 1
Inventory
Discovery
Configure
Plugins
F
M
Q
0
5
6
0
-
0
The base plug-ins in IBM Systems Director provide core function to manage the
full life cycle of IBM servers, storage, network, and virtual servers. Plug-ins that
provide advanced function or function tailored to a particular environment can be
downloaded and installed on top of IBM Systems Director.
The advanced plug-ins below are automatically installed with IBM Systems
Director:
v Active Energy Manager
v Service and Support Manager
v IBM Systems Director VMControl
These plug-ins no longer have a separate installation or uninstallation process.
Although you do not need to download, install or configure these plug-ins
separately, you must activate Active Energy Manager and IBM Systems Director
VMControl before using them. For more information about activating or using
these plug-ins, see Configuring IBM Systems Director plug-ins.
Note: For more information about discovery, inventory, and using the Web
interface, see Publications and related information to access the Systems
Management guide.
Related tasks:
Acquiring IBM Systems Director Server
Preparing the management server
Running the Pre-Installation Utility (PIU)
Installing the Systems Director Server
Configuring after installation
Verifying the successful installation of IBM Systems Director on the management
server
Updating Systems Director
Related reference:
Planning
Installation worksheet for the management server
Installing IBM Systems Director Server
Installing IBM Systems Director Server requires some preparation.
The following graphic outlines the installation process for IBM Systems Director
Server. Use the links provided to acquire, prepare for, install, and configure the
IBM Systems Director Server.
2 Installing with managed IBM DB2 database on Windows
Note: For information about discovery, inventory, and using the Web interface, see
Publications and related information to access the Systems Management guide.
Related concepts:
System discovery
Related tasks:
Planning
Updating Systems Director
Discovering systems with system discovery
Activating advanced plugins
Logging on to IBM Systems Director Server for the first time
Related reference:
Systems Director Downloads
Acquiring IBM Systems Director Server
You can either download the installation package or acquire an installation DVD.
Then, you can use the installation package or DVD to install IBM Systems Director
Server 6.3.x.
Chapter 1. Installing 3
Related concepts:
Installation overview on page 1
Related reference:
Planning
Installation worksheet for the management server
Acquiring an installation DVD
If you do not already have an installation DVD for IBM Systems Director Server,
complete the following steps:
1. Download the DVD image from the IBM Systems Director Downloads website
at http://www.ibm.com/systems/software/director/downloads/
mgmtservers.html.
2. If you are using Windows or AIX
Database.
The following procedure applies to your situation if you are currently using IBM
Systems Director 6.3.x with some type of existing database. You want to continue
to use IBM Systems Director 6.3.x, but switch your database application to one of
the following database types:
v An external IBM DB2 database and not the managed IBM DB2 database that is
included with IBM Systems Director Server
v Microsoft SQL Server
v Microsoft SQL Server Express
v Oracle
Database
Chapter 1. Installing 31
For example, you are currently using Oracle
Database:
There are database configuration attributes that must be set in the cfgdbcmd.rsp
response file in order to configure the Oracle
Database.
Database configuration attributes
The following table lists the database configuration attributes for Oracle
Database,
a description of each attribute, and an example of each attribute.
40 Installing with managed IBM DB2 database on Windows
Table 9. Database configuration information and values
Description
Database configuration
attribute Value
Selected database application
Notes:
v If you want to configure IBM Systems
Director Server by setting options in a
database-configuration response file,
then the value for DbmsApplication
must match the database value that you
select.
v You must enter into the cfgdbcmd.rsp
response file the exact value for the
database as it appears here.
DbmsApplication Oracle
Host name of the server on which the
database is installed
DbmsServerName Custom value:
Examples:
v 10.0.0.72
v MyServer
v localhost
Use a host name or localhost instead of
an IP address for this attribute in the
following situations:
v Use localhost if the following
statements are true:
You are using a local, non-default,
database.
The IP address of IBM Systems
Director Server might change in the
future. For example, the IP address is
assigned by using DHCP.
v Use a host name if the IP address of the
database server might change in the
future. For example, the IP address is
assigned by using DHCP.
In these situations, if you use an IP
address, you must manually update all of
the files that end in database.properties
with the changed IP address. You must
make this update each time the IP address
changes. The files that end in
database.properties, such as
database.properties and
aem_database.properties, are located in
the install_root\lwi\conf\overrides
directory.
Database name DbmsDatabaseName Custom value:
Example: mydatabase
Note: This value must match the name of
the database that is created in the chosen
database application.
Chapter 1. Installing 41
Table 9. Database configuration information and values (continued)
Description
Database configuration
attribute Value
Fully qualified local installation folder of
the database server instance or admin
client instance on the IBM Systems Director
Server system
DbmsDatabaseAppHome Custom value:
Example: c:\oracle\product\10.2.0\
client_1
Do not include double quotation marks
around the path name.
TCP/IP listener port ID for the database DbmsTcpIpListenerPort Default or custom value:
Example: 1521
User ID of the database user account
For detailed information about user IDs,
see Tips for user authorities and
passwords for Oracle
Database on page
46.
DbmsUserId Custom value:
Example: myuserid
Password of the database user account
For detailed information about passwords,
see Tips for user authorities and
passwords for Oracle
Database on page
46.
DbmsPassword Custom value:
Example: mypwd
Example cfgdbcmd.rsp file for Windows
DbmsApplication = Oracle
DbmsTcpIpListenerPort = 1521
DbmsServerName = 10.0.0.72
DbmsDatabaseName = mydatabase
DbmsUserId = myuserid
DbmsPassword = mypwd
DbmsDatabaseAppHome = c:\oracle\product\10.2.0\client_1
Related tasks:
Configuring the database
Switching the database
Enabling Dynamic IP support
Tips for database user authorities and passwords
Use these tips and techniques to configure, manage, and troubleshoot user
authorities and passwords for your database application.
Related tasks:
Configuring the database
Switching the database
Related reference:
Database configuration attributes
Tips for user authorities and passwords for the managed IBM DB2 database:
Use these tips and techniques to configure, manage, and troubleshoot user
authorities and passwords for the managed IBM DB2 database.
42 Installing with managed IBM DB2 database on Windows
Default user ID and password
IBM Systems Director automatically creates the user ID of the database system
administrator. The default user ID is dirinst1.
When you initially configure the managed IBM DB2 database, you can specify the
password for the dirinst1 user ID. Depending on your operating system, you can
specify the password as follows:
v You can specify the password in the installation or migration panels of the
installation wizard.
v You can specify the password by using the DbmsPassword configuration attribute
in the cfgdbcmd.rsp file.
Do not use any of the following characters in the password of the database
administrator:
! % ^ & ( ) | " ? , < >
If you use any of these characters, the database connection between IBM Systems
Director Server and the database fails.
If you do not specify a password during the initial configuration, IBM Systems
Director automatically generates the password for the dirinst1 user ID.
After installation or migration, you can change the password by using the
changePassword command.
Related concepts:
Database application
Related tasks:
Switching to the managed IBM DB2 database
Related reference:
cfgdbcmd command
changePassword tool
Database configuration attributes for the managed IBM DB2 database
Tips for user authorities and passwords for IBM DB2:
Use these tips and techniques to configure, manage, and troubleshoot user
authorities and passwords for the IBM DB2 database.
IBM Systems Director grants dbadm authority to the IBM Systems Director database
user ID. The IBM Systems Director database user ID is the user ID specified in the
DbmsUserID configuration attribute in the cfgdbcmd.rsp file. One exception is when
the -dbAdmin user ID is the same as the DbmsUserID user ID. In this case, IBM
Systems Director assumes that the user ID already has the required level of
authority.
Do not use the database user ID dirinst1. This user ID is reserved for the
managed IBM DB2 database that is installed with IBM Systems Director Server.
Do not use any of the following characters in the password of the database
administrator:
Chapter 1. Installing 43
! % ^ & ( ) | " ? , < >
If you use any of these characters, the database connection between IBM Systems
Director Server and the database fails.
If you are using Storage Control, the IBM Systems Director database user ID must
be the same as the database administrator ID. In other words, the value for the
DbmsUserID configuration attribute in the cfgdbcmd.rsp file must be the same as the
-dbAdmin user ID.
The cfgdbcmd tool
The cfgdbcmd tool automatically encrypts the database user password that you
specify in the cfgdbcmd.rsp file.
Differences between user ID and password parameters, configuration attributes,
and arguments
The -dbAdmin parameter for the cfgdbcmd tool serves a different purpose than the
DbmsUserId database configuration attribute in the cfgdbcmd.rsp file. The -dbAdmin
parameter specifies the ID of the instance owner so that the cfgdbcmd tool has the
authority to create a database. The DbmsUserId database configuration attribute
specifies the user ID that IBM Systems Director uses to store data in the database.
The -dbAdminPW parameter for the cfgdbcmd tool serves a different purpose than the
DbmsPassword database configuration attribute in the cfgdbcmd.rsp file. The
-dbAdminPW parameter specifies the password of the instance owner so that the
cfgdbcmd tool has the authority to create a database. The DbmsPassword database
configuration attribute specifies the password that IBM Systems Director uses to
store data in the database.
Do not specify the same user ID in the cfgdbcmd.rsp configuration file as is
specified in the -dbAdmin parameter to the cfgdbcmd tool. Doing so might result in
an error or in having the administrator authority of the user revoked. If you
mistakenly used this configuration in the past, you might need to grant
administrator authority again to this user ID after the cfgdbcmd command runs.
When you back up and restore the database by using the smsave command and the
smrestore command, you enter the user ID and password of the database system
administrator as follows:
v You enter the user ID of the database system administrator in the -dbUserName
argument.
v You enter the password of the database system administrator in the -dbUserPwd
argument.
If you do not specify a value for these arguments, the commands prompt you to
specify a value.
44 Installing with managed IBM DB2 database on Windows
Related tasks:
Configuring the database
Switching the database
Related reference:
cfgdbcmd command
smsave command
smrestore command
Database configuration attributes for IBM DB2
Tips for user authorities and passwords for Microsoft SQL Server and Microsoft
SQL Server Express:
Use these tips and techniques to configure, manage, and troubleshoot user
authorities and passwords for Microsoft SQL Server and Microsoft SQL Server
Express.
Integrated security
If you use integrated security (DbmsIntegratedSecurity=true), IBM Systems
Director connects to the database by using the Windows user ID.
If you do not use integrated security (DbmsIntegratedSecurity=false), IBM
Systems Director connects to the database by using the user ID and password that
you specify in the cfgdbcmd.rsp file. You specify the user ID in the DbmsUserId
configuration attribute and you specify the password in the DbmsPassword
configuration attribute.
User ID roles and authorities
If IBM Systems Director creates the user ID of the database system administrator
during the installation process, IBM Systems Director automatically assigns the
db_owner role to the user ID.
If you create the user ID of the database system administrator before you configure
the database for use with IBM Systems Director:
v The cfgdbcmd tool keeps the user ID that you create and does not delete it.
v The user ID must have the following authorities and roles:
db_datareader authority
db_datawriter authority
db_ddladmin role or db_owner role
These authorities and roles are required in order to create database tables.
If you use integrated security (DbmsIntegratedSecurity=true), the previous list
of authorities and roles applies to the Windows user ID.
The cfgdbcmd tool
The cfgdbcmd tool automatically encrypts the database user password that you
specify in the cfgdbcmd.rsp file.
Chapter 1. Installing 45
Differences between user ID and password parameters, configuration attributes,
and arguments
If you do not use integrated security (DbmsIntegratedSecurity=false):
v The -dbAdmin parameter for the cfgdbcmd tool serves a different purpose than the
DbmsUserId database configuration attribute in the cfgdbcmd.rsp file. The
-dbAdmin parameter specifies the user ID for the database system administrator.
The DbmsUserId database configuration attribute specifies the user ID that IBM
Systems Director uses to store data in the database.
v The -dbAdminPW parameter for the cfgdbcmd tool serves a different purpose than
the DbmsPassword database configuration attribute in the cfgdbcmd.rsp file. The
-dbAdminPW parameter specifies the password for the database system
administrator. The DbmsPassword database configuration attribute specifies the
password that IBM Systems Director uses to store data in the database.
v Do not specify the same user ID in the cfgdbcmd.rsp configuration file as is
specified in the -dbAdmin parameter to the cfgdbcmd tool. Doing so might result
in an error or in having the administrator authority of the user revoked. If you
mistakenly used this configuration in the past, you might need to grant
administrator authority again to this user ID after the cfgdbcmd command runs.
v When you back up and restore the database by using the smsave command and
the smrestore command, you enter the user ID and password of the database
system administrator as follows:
You enter the user ID of the database system administrator in the -dbUserName
argument.
You enter the password of the database system administrator in the
-dbUserPwd argument.
If you do not specify a value for these arguments, the commands prompt you to
specify a value.
If you use integrated security (DbmsIntegratedSecurity=true):
v You do not need to specify -dbAdmin and -dbAdminPW parameters when using the
cfgdbcmd command.
v You do not need to specify the -dbUserName argument and the -dbUserPwd
argument when using the smsave command and the smrestore command.
v You do not need to specify the DbmsUserId configuration attribute and the
DbmsPassword configuration attribute in cfgdbcmd.rsp file.
Related tasks:
Configuring the database
Switching the database
Related reference:
cfgdbcmd command
smsave command
smrestore command
Database configuration attributes for Microsoft SQL Server and Microsoft SQL
Server Express
Tips for user authorities and passwords for Oracle
Database:
46 Installing with managed IBM DB2 database on Windows
Use these tips and techniques to configure, manage, and troubleshoot user
authorities and passwords for Oracle
Database.
The user ID of the database system administrator must be granted the admin
option to the database.
The user ID uses the default table space called users and the temporary table
space called temp. If you receive errors while running the smreset command to
create tables, you might need to increase the size of the temporary table space.
IBM Systems Director grants the following authorities to the user ID of the
database system administrator:
v create any table
v alter any table
v delete any table
v drop any table
v insert any table
v lock any table
v select any table
v update any table
v create any index
v alter any index
v drop any index
v create view
v create any procedure
v alter any procedure
v drop any procedure
v execute any procedure
The cfgdbcmd tool
If you create the user ID before you run the cfgdbcmd command, the cfgdbcmd
command uses the user ID that you create. The cfgdbcmd command does not delete
the user ID and create a new one.
The cfgdbcmd tool automatically encrypts the database user password that you
specify in the cfgdbcmd.rsp file.
Differences between user ID and password parameters, configuration attributes,
and arguments
The -dbAdmin parameter for the cfgdbcmd tool serves a different purpose than the
DbmsUserId database configuration attribute in the cfgdbcmd.rsp file. The -dbAdmin
parameter specifies the user ID for the database system administrator. The
DbmsUserId database configuration attribute specifies the user ID that IBM Systems
Director uses to store data in the database.
The -dbAdminPW parameter for the cfgdbcmd tool serves a different purpose than the
DbmsPassword database configuration attribute in the cfgdbcmd.rsp file. The
-dbAdminPW parameter specifies the password for the database system
administrator. The DbmsPassword database configuration attribute specifies the
password that IBM Systems Director uses to store data in the database.
Chapter 1. Installing 47
Do not specify the same user ID in the cfgdbcmd.rsp configuration file as is
specified in the -dbAdmin parameter to the cfgdbcmd tool. Doing so might result in
an error or in having the administrator authority of the user revoked. If you
mistakenly used this configuration in the past, you might need to grant
administrator authority again to this user ID after the cfgdbcmd command runs.
When you back up and restore the database by using the smsave command and the
smrestore command, you enter the user ID and password of the database system
administrator as follows:
v You enter the user ID of the database system administrator in the -dbUserName
argument.
v You enter the password of the database system administrator in the -dbUserPwd
argument.
If you do not specify a value for these arguments, the commands prompt you to
specify a value.
Related tasks:
Configuring the database
Switching the database
Related reference:
cfgdbcmd command
smsave command
smrestore command
smreset command
Database configuration attributes for Oracle
Database
Logging on to IBM Systems Director Server for the first time
After installing IBM Systems Director Server, you need to log on using a Web
browser, update IBM Systems Director Server, discover managed systems, and
request access to those managed systems.
You must already have installed and started IBM Systems Director Server before
beginning this task. When you start IBM Systems Director for the first time,
inventory is automatically collected on the management server.
1. Log on to IBM Systems Director using a Web browser.
a. Point your browser to the following URL:
http://System_Name:Port_Number/ibm/console
where System_Name is the name of the system on which IBM Systems
Director Server is installed and Port_Number is the first (lower) of two
consecutive port numbers that you specified for the Web server to use. The
default ports for the Web server are 8421 and 8422. If you use port 8422,
make sure that you specify https to indicate a secure port.
b. Type the user ID and password that correspond to an authorized IBM
Systems Director administrator user ID and password. Authorized
administrator credentials include credentials for the root user or any user
that is a member of the smadmin group.
48 Installing with managed IBM DB2 database on Windows
Note: The first time you log in, use the administrator user ID that you used
during the installation or the root user. After this initial login, you can add
other users to the smadmin group.
c. Click Log in.
Note: A security alert window might be displayed before logging in. This is
due to incorrect configuration of the Secure Sockets Layer (SSL) certificate.
For information see Configuring Secure Sockets Layer (SSL) between IBM
Systems Director and the Web browser client.
Note: Logging in to IBM Systems Director will be slower with SSL enabled.
2. Follow the steps on the Initial Setup tab on the home page to set up IBM
Systems Director for the first time.
After you complete the tasks on the Start page, you can:
v Begin managing the systems you have discovered.
v Install agents on managed systems to enable additional management capabilities.
Related concepts:
System discovery
Related tasks:
Installing IBM Systems Director Server
Authenticating users
Updating IBM Systems Director
Managing access
Collecting inventory
Restarting IBM Systems Director Server
Restarting IBM Systems Director Server requires that you run one command to
stop the management server processes and then run another command to start
them again.
Before you stop the IBM Systems Director Server, warn users to finish their work
or stop the processes they are running.
To restart the IBM Systems Director Server, complete the following steps:
Note: You must run all the commands in the following procedure on the IBM
Systems Director management server.
1. Stop the IBM Systems Director processes that are running on the management
server.
v If you are running Windows, run the following command: net stop
dirserver.
2. Restart the IBM Systems Director processes that run on the management server.
v If you are running Windows, run the following command: net start
dirserver.
3. Check to ensure that the IBM Systems Director Server started successfully.
v If you are running Windows, check the status of the server by checking the
system tray.
Chapter 1. Installing 49
Related tasks:
Enabling Dynamic IP support
Changing IBM Systems Director server health settings on page 56
Related reference:
smstart command
smstatus command
smstop command
Enabling Dynamic IP support
Enabling the Dynamic IP support feature automatically reconfigures IBM Systems
Director Server and notifies the managed resources of the IP address change if the
IP address of the system running IBM Systems Director Server changes.
In IBM Systems Director 6.1.x and earlier releases, the IP address of the
management server had to remain static. Thus, the IP address of the management
server was not supposed to change after IBM Systems Director Server was
installed on the system. In IBM Systems Director 6.2 and later releases, changing
the IP address of IBM Systems Director Server is supported. If the IP address of
the IBM Systems Director Server system changes, the embedded Dynamic IP
feature automatically detects the changed IP address when the IBM Systems
Director Server stops, starts, and initiates the following actions:
v It reconfigures IBM Systems Director Server for the new IP address.
v It notifies the resources that are managed by IBM Systems Director Server that
the IP of the management server has changed and the managed resources are
updated to use the new IP address of the server. This notification ensures that
the resources that are managed by IBM Systems Director Server maintain
communication with the server after its IP address has changed.
This feature is supported on IBM Director 5.20.x agents, IBM Systems Director 6.2
(or later) common agents, and all IBM Systems Director platform agents.
Restriction: This feature is not supported if you are managing 6.1.x common
agents. To use this feature, you must first upgrade 6.1.x common agents to 6.2 or
later releases.
The following manageable resource types support updating the IBM Systems
Director Server IP address when it changes:
v Operating system
v BCChassis
v Server (RSA, IMM, BMC)
v HMC
v IVM
v StoragePlatform
v StorageSubSystem
v Switch
50 Installing with managed IBM DB2 database on Windows
Attention: If you configure the switch to send SNMP traps to IBM Systems
Director Server, the switch does not automatically update if the IP address
changes. Because it requires a manual action from the user to set the SNMP trap
destination, it also requires a manual action to change it. Most switches support
setting multiple SNMP trap destinations. So, configure the switch to send SNMP
traps to the primary IBM Systems Director Server IP address and to any backup
IP addresses to which IBM Systems Director Server could potentially move.
However, this configuration is only possible you know ahead of time that there
is a small set of IP addresses to which IBM Systems Director Server could
potentially move.
Notes:
v Frequent IP address changes can drive network traffic in association with
updating the managed resources with the new IBM Systems Director Server IP
address. IP address changes can also cause the CPU utilization of IBM Systems
Director Server to increase and slow down the overall performance. This
performance change occurs during the time period that the IP address updates
are sent to the managed resources.
v Dynamic IP does not support on-the-fly processing, meaning that it does not
work unless you restart IBM Systems Director Server.
v Start IBM Systems Director Server for the first time on the same IP address on
which it was installed. Changing the IP address any time after the first startup is
supported.
v Processing for an IP address change is not supported for the scenario where the
configuration for one IBM Systems Director Server and data is captured with the
smsave command and restored to another IBM Systems Director Server with the
smrestore command and both of these IBM Systems Director Server instances
have different IP addresses.
To enable the Dynamic IP function, complete the following steps when the IP
address of the IBM Systems Director Server system changes:
1. Stop IBM Systems Director Server.
2. Start IBM Systems Director Server.
Note: IBM Systems Director Server takes more time to start (become active)
when it is restarted for the first time with a new or modified IP address. IBM
Systems Director Server takes more time because it must configure itself to the
new IP address.
IBM Systems Director Server is active.
3. Perform Lite Query on the local operating-system agent by issuing the
following command in a command prompt or shell on the management system:
smcli querysystem OID_of_local_OS_MEP 1
After you complete this procedure, the processes of reconfiguring and notifying the
managed resources about the IP change commences.
Note: It takes typically 8 - 10 minutes after IBM Systems Director Server becomes
active for the IP address change notifications to be sent to the managed resources.
By default, IP address related processing is enabled (turned on) on IBM Systems
Director Server. To turn the processing for an IP address change on or off, set the
com.ibm.usmi.kernel.localsystem.USMSLocalSystemService
.enableIPChangeProcessing property in the install_root\lwi\conf\overrides\
USMIKernel.properties file:
Chapter 1. Installing 51
Turn on IP address change processing
To turn on IP address change processing, delete the property or set it to
true:
com.ibm.usmi.kernel.localsystem.USMSLocalSystemService.
enableIPChangeProcessing=true
If this property is not set or present, the Dynamic IP change processing is
enabled by default.
Turn IP address change processing off
To turn off IP address change processing, add or edit the property to set it
to false:
com.ibm.usmi.kernel.localsystem.USMSLocalSystemService.
enableIPChangeProcessing=false
Related tasks:
Restarting IBM Systems Director Server
Configuring IBM Systems Director plug-ins
IBM Systems Director Server automatically installs some plug-ins that require
configuration in order to use them. If you want to use plug-ins that IBM Systems
Director Server does not automatically install, you must install and configure them
after you install IBM Systems Director Server.
If you do not intend to use a plug-in, you do not need to configure it.
To install or configure the plug-ins that you intend to use, complete the following
steps:
1. Configure console settings, including encryption, console navigation, and event
log settings.
2. Configure users and roles. Click Security > Users and Security > Roles.
3. Optional: Activate or configure the advanced plug-ins that were automatically
installed with IBM Systems Director Server:
v Activate the free trial period for Active Energy Manager. For instructions, see
Activating Active Energy Manager.
v Configure Electronic Service Agent
management
1. Configure SMI-S
providers.
2. Configure external
storage applications.
1. Managing SMI-S
providers
2. Installing and configuring
external storage
applications
52 Installing with managed IBM DB2 database on Windows
Table 10. Configuration tasks and information resources for IBM Systems Director
plug-ins (continued)
Plug-in Tasks Information resources
Remote access manager
1. Configure Virtual
Network Computing
(VNC).
2. Configure Remote
Desktop.
1. Virtual Network
Computing
2. Configuring Microsoft
Windows Remote
Desktop Connection
Update manager Optional: Complete the
Getting Started wizard and
change update settings.
Configuring update manager
Advanced plug-ins
IBM Systems Director
Network Control
Install the plug-in. Installing and uninstalling
IBM Systems Director
Network Control
IBM Systems Director
Storage Control 4.2.3
Install the plug-in. Installing Storage Control
The following base plug-ins are installed with IBM Systems Director Server and
have no configuration tasks:
v Automation manager
v Configuration manager
v Discovery manager
v IBM BladeCenter Chassis management
v IBM Power Systems management
v IBM System x management
v IBM System z management
v Network manager
v Status manager
Related concepts:
Base function and extensible plug-ins
IBM Systems Director plug-ins
Related tasks:
Installing IBM Systems Director plug-ins
Configuring the command-line interface
Before running the smcli commands or displaying help for them, ensure that
required software is installed and the locale is correctly installed and configured on
the system.
You can run smcli commands in one of the following ways:
v You can run them locally on the management server.
v You can run them remotely by accessing the management server by using a
remote-access utility, such as Secure Shell (SSH) or Telnet
Perform these steps on the management server and on all other systems that you
might use to access the management server to run commands.
Chapter 1. Installing 53
1. (Windows only) Management servers running Windows 2000 or Windows 2003
require msvcr80.dll to run smcli. You can obtain the dynamic link library
(DLL) by installing vcredist_x86.exe. For information about downloading and
installing this file, see https://www.microsoft.com/downloads.
2. Ensure that the desired locale is supported by IBM Systems Director and is
installed correctly on the client system, from where smcli is run.
Tips:
v To verify languages supported by smcli, see Language specifications for smcli
commands.
v If your system does not support double-byte character sets, you see garbage
characters or small block-like characters when you display operating-system
specific man pages.
Related reference:
smcli - Systems management command-line interface
Reviewing Microsoft Internet Explorer security options
If you are using Microsoft Internet Explorer Web browsers that have Enhanced
Security Configuration enabled, and are running on Windows Server 2008, review
these instructions.
When using a Web browser with Enhanced Security Configuration enabled, some
properties of the IBM Systems Director Web interface might not display as
expected.
Internet Explorer Enhanced Security Configuration establishes a configuration for
your server and for Internet Explorer that decreases the exposure of your server to
potential attacks that can occur through Web content and application scripts. As a
result, some websites might not display or perform as expected.
Using a server for Internet browsing is not a good security practice because
Internet browsing increases the exposure of your server to potential security
attacks. It is a best practice recommendation that you run your Web browser on a
system that is not a server. However, if you must use a server running Windows
Server, you must turn off Internet Explorer Enhanced Security Configuration.
Complete the following applicable steps to disable Internet Explorer Enhanced
Security:
On Windows Server 2008 systems:
1. Close any instances of the Internet Explorer Web browser.
2. Start Server Manager.
3. In the Details pane, locate the Security Information area that is displayed under
the Server Summary area.
4. In the Security Information area, click Configure IE ESC.
5. In the Internet Explorer Enhanced Security Configuration window, click the
applicable option:
v If your user account is a member of the Administrators group, click Off
under Administrators.
v If your user account is a member of a standard users group, click Off under
Users.
6. Click OK.
54 Installing with managed IBM DB2 database on Windows
Configuring IP address properties
Configure IP address properties when your management server has more than one
IP address, when your network uses one or more subnets that IBM Systems
Director does not manage, and when resources that you want to manage have
more than one IP address. Configure IP address properties by creating or updating
the IPPreference.properties file.
Specifying the preferred IP address for the management server:
Specify the IP address that you want the server to use when your management
server has more than one IP address. For example, a server that has more than one
network interface card has more than one IP address. Specify the preferred IP
address for the management server by creating or updating the
IPPreference.properties file.
To specify the preferred IP address for the management server, perform the
following steps:
1. Use a text editor to open an empty file named IPPreference.properties in the
following location: install_path/data/IPPreference.properties
where
install_path is the path where you installed IBM Systems Director.
Note: If the /data/IPPreference.properties file exists, open the file with a text
editor, then go to the next step.
2. On a single line, type the following entry:
com.ibm.director.server.preferred.ip=<IP_address>
whereIP_address is the IPv4 or IPv6 address for the management server.
v Each entry in the IPPreference.properties file must be on a separate line.
v To insert a comment, begin the line with a number (#) character.
Note: If a com.ibm.director.server.preferred.ip entry exists, confirm that the
change correctly supersedes the current entry.
3. Save and close the file.
For Systems Director to recognize the preferred IP address, you must restart the
management server.
Related tasks:
Excluding IP addresses
Excluding IP addresses
Excluding IP addresses:
Exclude IP addresses by creating or updating the IPPreferences.properties file for
resources that you do not want IBM Systems Director to manage or that have
multiple IP addresses, or for subnets that you do not want Systems Director to
manage.
You can exclude one or more individual IP addresses, an IP address range, or an
entire subnet. Consider the following examples:
v When a managed resource has multiple network interface cards, exclude all but
the IP address that Systems Director uses to communicate with the resource.
v When managed resources are on more than one subnet, exclude the subnet that
Systems Director does not use to manage resources.
Chapter 1. Installing 55
To exclude IP addresses, perform the following steps:
1. Use a text editor to open an empty file named IPPreference.properties in the
following location: install_path/data/IPPreference.properties
where
install_path is the path where you installed Systems Director.
Note: If the /data/IPPreference.properties file exists, open the file with a text
editor, then go to the next step.
2. Type the IP addresses that you want to exclude:
com.ibm.director.endpoint.excluded.ip.prefix=<IP_addresses>
where IP_address is one or more IPv4 or IPv6 addresses or address ranges that
you want to exclude.
v To exclude one or more individual IP addresses, use a comma character (,) to
separate the IP addresses:
com.ibm.director.endpoint.excluded.ip.prefix=192.168.53.1,192.168.53.22
v To exclude an IP address range:
com.ibm.director.endpoint.excluded.ip.prefix=192.168.53.1-192.168.53.150
v To exclude a subnet, use the asterisk character (*) as a wildcard:
com.ibm.director.endpoint.excluded.ip.prefix=192.168.*
Note:
v All entries in the IPPreference.properties file must be on the same line.
v To insert a comment, begin the line with a number (#) character.
3. Save and close the file.
For Systems Director to ignore the excluded IP addresses, you must restart the
management server.
Related tasks:
Specifying the preferred IP address for the management server on page 55
Specifying the preferred IP address for the management server
Changing IBM Systems Director server health settings
You can change local system health settings to customize when you will receive a
warning. For example, by default, you will get a warning when the Systems
Director server CPU usage is at 90% for 30 minutes, but your environment might
require notification sooner or later than the default.
When the warning threshold for a setting is met, the following happens:
v An event appears in the event log.
v The problem shows in the Problems view.
v The overall status of the Systems Director server endpoint is warning.
1. Navigate to USMIKernel.properties and open it for editing. The location of this
file depends on your operating system:
v On Windows: C:\Program Files\IBM\Director\lwi\conf\overrides\
USMIKernel.properties
2. Add entries for any properties you want to modify:
Table 11. Settings with default values that can be changed
Property Input value Default value
System properties
56 Installing with managed IBM DB2 database on Windows
Table 11. Settings with default values that can be changed (continued)
Property Input value Default value
com.ibm.usmi.kernel.
localsystem.
cpuWarningThreshold
The percentage that triggers
the warning.
90%
com.ibm.usmi.kernel.
localsystem.
cpuTimeForWarning
The number of milliseconds
the CPU must be at the
threshold level to trigger a
warning.
By default, this warning is
triggered after the CPU is
at 90% for 30 minutes.
1 800 000 milliseconds (30
minutes)
Example: By default you get a warning when the Systems Director
server CPU usage is at 90% for 30 minutes.
Disk usage properties
com.ibm.usmi.kernel.
localsystem.
diskSpaceWarning
The amount of free space
before triggering the
warning.
1 073 741 824 bytes (1 GB)
com.ibm.usmi.kernel.
localsystem.
diskSpaceCrit
The amount of free space
before triggering a critical
event.
500 MB
Example: By default you get a warning when the Systems Director
server free space available is less than 1 GB.
Memory usage properties
com.ibm.usmi.kernel.
localsystem.
memoryWarningPercentage
The percentage of memory
usage that triggers the
warning.
90%
com.ibm.usmi.kernel.
localsystem.
memoryWarningTime
The amount of time, in
milliseconds, that memory
use must be sustained to
trigger the warning.
By default, this warning is
triggered after the memory
usage is at 90% for 1 hour.
3 600 000 milliseconds (1
hour)
Example: By default you get a warning when the Systems Director
server memory usage is at 90% for 1 hour.
Managed endpoint (MEP)
count properties
com.ibm.usmi.maxSystems The maximum number of
MEPs supported.
10 000
com.ibm.usmi.maxSystems.derby The maximum number of
MEPs supported when the
Apache Derby database is
used.
1 000
Example: By default the Systems Director server supports 1000
MEPs when using the Apache Derby database.
Page space properties
com.ibm.usmi.kernel.
localsystem.
psWarningPercentage
The page space usage
percentage that triggers the
warning.
80
Chapter 1. Installing 57
Table 11. Settings with default values that can be changed (continued)
Property Input value Default value
com.ibm.usmi.kernel.
localsystem.
psWarningTime
The time in milliseconds
that page space usage must
be sustained to trigger the
warning.
By default, this warning is
triggered after the page
space usage is at 80% for 20
minutes.
1 200 000 milliseconds (20
minutes)
Example: By default you get a warning when the Systems Director
server page space usage is at 80% for 20 minutes.
Example:
com.ibm.usmi.kernel.localsystem.cpuWarningThreshold=90
com.ibm.usmi.kernel.localsystem.cpuTimeForWarning=1800000
3. Restart the server.
Related tasks:
Restarting IBM Systems Director Server
Recovering from a failed installation of IBM Systems Director
Server 6.3.x
You can recover from a failed installation of IBM Systems Director Server 6.3.x by
fixing the problems that are identified in the log files and then performing the
installation procedure again.
To recover from a failed installation, complete the following steps:
1. Access the log files for the installation and fix all of the problems that the log
files identify. The following table lists the locations of applicable log files for
IBM Systems Director 6.3.x.
Table 12. Example locations of log files for IBM Systems Director 6.3.x
AIX IBM i Linux Windows
IBM Systems Director Server installation logs:
v /var/log/dirinst.log
v /var/log/director/*
v /opt/ibm/director/log/
recovery.txt
Not applicable
v /var/log/dirinst.log
v /opt/ibm/director/log/
*.log
v /opt/ibm/director/log/
recovery.txt
v C:\Windows\
dirserverinst_time.log
v C:\Windows\
dirserversetup.log
v C:\Windows\
db2prereqcheck.log
v C:\Windows\
prereqcheckdb2.log
v C:\Windows\
installdb2.log
v C:\Windows\
tivguidinst64.log
(64-bit Windows only)
v c:\Program
Files\IBM\Director\log\
recovery.txt
Common Agent installation logs:
58 Installing with managed IBM DB2 database on Windows
Table 12. Example locations of log files for IBM Systems Director 6.3.x (continued)
AIX IBM i Linux Windows
/var/log/dirinst.log
v /tmp/director/
installAgent.log
v /tmp/director/
installDirAgent.log
v /www/cas/lwi/runtime/
agent/logs/install
All of these can be found in
the dirmedic results.
/var/log/dirinst.log
v C:\Windows\
agent_install.log
v C:\Windows\CasInst.log
v C:\Windows\certutil.log
v C:\Windows\
diragentinst_time.log
v C:\Windows\
diragentsetup.log
v C:\Windows\
tivguidinst.log
Platform Agent installation logs:
/var/log/dirinst.log Not applicable /var/opt/ibm/platform/
log/install.log
C:\Windows\
platinst_time.log
Common Agent uninstallation logs:
Not applicable /tmp/director/
uninstallDirAgent.log,
which can be found in the
dirmedic results.
Platform Agent uninstallation logs:
/var/log/diruninst.log Not applicable /var/opt/ibm/platform/
log/uninstall.log
v C:\Windows\
platuninst_time.log
v C:\Windows\
sysdirremoval.log
Migration logs:
/var/tmp/
director_save_630/logs
Not applicable /var/tmp/
director_save_630/logs
%APPDATA%\ISD62x\logs
Configuration logs:
/var/log/director/* Not applicable /opt/ibm/director/log/
*.log
C:\Program
Files\IBM\Director\log\
*.log
Default managed IBM DB2 database logs:
v /tmp/installdb2.log
v /tmp/db2setup.log
v Directory structure for
your installed IBM DB2
database product (Linux)
Not applicable
v /tmp/installdb2.log
v /tmp/db2setup.log
v Directory structure for
your installed IBM DB2
database product (Linux)
C:\Windows\installdb2.log
2. Perform the installation procedure again. For instructions, see Installing IBM
Systems Director on the management server on page 23 and select your
operating system.
When you are finished recovering from a failed installation, verify that the
recovery was successful. For instructions, see Verifying the successful installation
of IBM Systems Director on the management server on page 30.
Chapter 1. Installing 59
Related information:
Installation and migration troubleshooting
Exchanging information with IBM
Managed IBM DB2 installation fails
60 Installing with managed IBM DB2 database on Windows
Chapter 2. Installing agents
Prepare your managed systems and environment for agent and subagent
installation and then install Common Agent, Platform Agent, or IBM z/VM
or
), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at Copyright and trademark information at www.ibm.com/legal/
copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United
States, other countries, or both.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, or service names may be trademarks or service marks of
others.
Notices 117
118 Installing with managed IBM DB2 database on Windows
Printed in USA