fqp0 BK Install Server Windows Oracle PDF

IBM Systems Director

Installing IBM Systems Director on Windows and
configuring the Oracle® Database
Version 6.3


Installing IBM Systems Director on Windows and
configuring the Oracle® Database
Version 6.3
Note
Before using this information and the product it supports, read the information in “Notices” on
page 125.
© 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 Configuring the command-line interface . . . 63
Conventions and terminology . . . . . . . . v Reviewing Microsoft Internet Explorer security
Publications and related information . . . . . . v options . . . . . . . . . . . . . . 64
Web resources . . . . . . . . . . . . . viii Configuring IP address properties . . . . . 65
How to send your comments . . . . . . . . ix Changing IBM Systems Director server health
settings . . . . . . . . . . . . . . 66
Checklist: Installing IBM Systems Recovering from a failed installation of IBM
Systems Director Server 6.3.x . . . . . . . 68
Director Server . . . . . . . . . . . xi
Chapter 2. Installing agents . . . . . . 71
Checklist: Installing agents . . . . . xiii Running the Pre-Installation Utility on an agent
(Windows). . . . . . . . . . . . . . . 72
Chapter 1. Installing IBM Systems Installing Common Agent . . . . . . . . . 73
Director . . . . . . . . . . . . . . . 1 Preparing for a Common Agent managed system 74
Installation overview . . . . . . . . . . . 1 Obtaining licenses for Common Agent . . . 74
Installing IBM Systems Director Server . . . . . 2 Preparing to install Common Agent on
Acquiring IBM Systems Director Server . . . . 3 Windows . . . . . . . . . . . . . 74
Acquiring an installation DVD . . . . . . 4 Installing agents using the Agent Installation
Downloading the installation package . . . . 4 Wizard . . . . . . . . . . . . . . . 75
Preparing the management server . . . . . . 4 Installing Common Agent manually . . . . . 78
Installation worksheet for the management Installing Common Agent on Windows . . . 79
server. . . . . . . . . . . . . . . 4 Installing Platform Agent . . . . . . . . . . 86
Preparing the database application . . . . . 8 Preparing for a Platform Agent managed system 87
Preparing to install IBM Systems Director Preparing to install Platform Agent on
Server on Windows. . . . . . . . . . 13 Windows . . . . . . . . . . . . . 87
Preparing firewalls and proxies for IBM Installing agents using the Agent Installation
Systems Director. . . . . . . . . . . 14 Wizard . . . . . . . . . . . . . . . 88
Installing firmware and device drivers . . . 15 Installing Platform Agent manually . . . . . 91
Running the Pre-Installation Utility (PIU) . . . 19 Installing Platform Agent on Windows . . . 92
Running the IBM Systems Director Verifying the successful installation of an IBM
Pre-Installation Utility on the management Systems Director agent . . . . . . . . . . 99
server (Windows) . . . . . . . . . . 20
Windows pre-installation checks . . . . . 21 Chapter 3. Preparing agentless
Installing IBM Systems Director on the managed systems . . . . . . . . . 101
management server. . . . . . . . . . . 27 Preparing to manage service processors with IBM
Installing IBM Systems Director Server on Systems Director . . . . . . . . . . . . 101
Windows . . . . . . . . . . . . . 27 Preparing to manage an IBM BladeCenter chassis
Tips for creating the server response file for using IBM Systems Director Server on a non-blade
IBM Systems Director Server . . . . . . 33 server . . . . . . . . . . . . . . . . 108
Verifying the successful installation of IBM Preparing to manage an IBM BladeCenter chassis
Systems Director on the management server . . 34 using IBM Systems Director Server on a blade
Configuring IBM Systems Director Server after server . . . . . . . . . . . . . . . . 109
installation . . . . . . . . . . . . . 34 Preparing Windows managed systems . . . . . 111
Configuring the database for use with IBM Preparing Windows Server 2003 managed
Systems Director. . . . . . . . . . . 35 systems . . . . . . . . . . . . . . 111
Switching the database that IBM Systems Preparing Windows Server 2008 managed
Director uses . . . . . . . . . . . . 38 systems . . . . . . . . . . . . . . 112
Database configuration attributes . . . . . 43 Preparing Windows Vista managed systems . . 112
Tips for database user authorities and Preparing to manage an agentless managed
passwords . . . . . . . . . . . . . 52 system running Windows Vista . . . . . 113
Logging on to IBM Systems Director Server Preparing a Windows Vista system for
for the first time . . . . . . . . . . . 58 Platform Agent managed system
Restarting IBM Systems Director Server . . . 59 management. . . . . . . . . . . . 114
Enabling Dynamic IP support . . . . . . 60
Configuring IBM Systems Director plug-ins . 62
© Copyright IBM Corp. 1999, 2012 iii

Preparing a Windows Vista system for Uninstalling IBM Systems Director using the
Common Agent managed system Windows Add or Remove Programs feature . . 120
management. . . . . . . . . . . . 115 Uninstalling IBM Systems Director using the
Preparing Windows XP managed systems . . . 116 isduninst command . . . . . . . . . . 122
Chapter 4. Uninstalling . . . . . . . 119 Notices . . . . . . . . . . . . . . 125

Uninstalling IBM Systems Director on Windows 119 Trademarks . . . . . . . . . . . . . . 127
iv Installing on Windows and configuring the Oracle® Database

About this publication
This publication provides information about installing IBM® Systems Director for
the first time. It also covers the following topics:
v Preparing the server for the installation process
v Configuring a database for use with IBM Systems Director Server
v (Optional) Switching the database that IBM Systems Director uses
v Activating the advanced plug-ins of IBM Systems Director
v Installing agents and preparing agentless managed systems
v Uninstalling
If you are using a printed version of this information, you might consider printing
the following related PDFs:
v IBM Systems Director planning guide
v Upgrading and migrating to IBM Systems Director 6.3
v Systems management guide
You can access additional information and PDFs from the IBM Systems Director
information center Web site at publib.boulder.ibm.com/infocenter/director/pubs/
index.jsp.
Conventions and terminology

These notices are designed to highlight key information:
Note: These notices provide important tips, guidance, or advice.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
Attention: These notices indicate possible damage to programs, devices, or data.

An attention notice appears before the instruction or situation in which damage
can occur.
Publications and related information

You can view the same content in the IBM Systems Director Information Center as
PDF documents. To view a PDF file, you need Adobe Acrobat Reader, which can
be downloaded for free from the Adobe Web site at http://get.adobe.com/reader/.
Information centers and topic collections

v IBM Systems
http://publib.boulder.ibm.com/eserver/
View the IBM Systems information center landing page, which provides
integrated information for multiple IBM Systems products.
v IBM Systems Director
publib.boulder.ibm.com/infocenter/director/pubs/index.jsp
Updated periodically, the IBM Systems Director topic collection contains the
most up-to-date documentation available for IBM Systems Director.
© Copyright IBM Corp. 1999, 2012 v

v IBM Systems Director plug-ins
http://publib.boulder.ibm.com/infocenter/director/pubs/topic/extensions/
extensionparent.html
View the IBM Systems information center for information about how to install
and use plug-ins that extend the functionality of IBM Systems Director.
v IBM Systems Director Upward Integration Modules (UIMs)
publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html
Read the IBM Systems Director Upward Integration Modules (UIM) topic
collection to learn about how to install and use upward integration modules and
management packs that enable non-IBM workgroup and enterprise-management
products to interpret and display data that is provided by Common Agent and
Platform Agent.
v IBM Systems Director API Licensing
http://publib.boulder.ibm.com/infocenter/director/devsdk/index.jsp
View the license information regarding use of IBM Systems Director APIs and
their associated documentation. Fill out the form to request API access. After
your information is reviewed, you will be contacted with additional information
regarding access to and use of the APIs.
Publications
Release Notes 6.3.2
Provides an easy reference to planning, install and troubleshooting
information for IBM Systems Director
IBM Systems Director Planning Guide
Provides planning information, including hardware requirements for
running IBM Systems Director components, supported IBM Systems
Director hardware, operating systems, databases, and workgroup and
enterprise systems-management software.
PDF files for installing IBM Systems Director Server
Provides detailed instructions to prepare for, install, and configure the IBM
Systems Director Server.
PDF files for installing IBM Systems Director agents
Provides detailed instructions to prepare for and install IBM Systems
Director agents on your managed systems, as well as, prepare for agentless
managed systems.
PDF files for upgrading and migrating IBM Systems Director Server
Provides detailed instructions to upgrade and migrate the IBM Systems
Director Server.
PDF files for upgrading and migrating IBM Systems Director agents
Provides detailed instructions to upgrade and migrate IBM Systems
Director agents.
IBM Systems Director Systems Management Guide
Provides detailed instructions for using the Web interface and managing
systems and resources in your environment.
IBM Systems Director Troubleshooting Guide
Provides information about problems and how to solve them, and
strategies for troubleshooting common problems.
vi Installing on Windows and configuring the Oracle® Database

IBM Systems Director Events Reference
Provides information about IBM Systems Director events, including the
event type, description, severity, and extended details.
IBM Systems Director Commands Reference
Provides detailed information about the systems management
command-line interface (smcli) commands, and other commands that can
be run directly from the command line, including configuring the database,
and starting and stopping IBM Systems Director.
IBM Systems Director Hardware Command Line User's Guide
Provides information about installing and using the Hardware Command
Line (formerly known as the IBM Management Processor Command-Line
Interface). Command output in this release might vary from command
output in previous releases.
White papers and briefs

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/
XBW03006USEN.PDF
This paper provides a detailed overview of the changes in IBM Systems Director
V6.1, including the new Web interface, security features, operating system
agents, integrated plug-ins and additional plug-ins that can be separately
installed.
v Value Proposition for IBM Systems Director
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/
XBW03007USEN.PDF
This paper describes the challenges of operational management for enterprise
server installations and the value provided IBM Systems Director.
v Performance Tuning and Scaling Guide for IBM Systems Director 6.3
Hardware requirements for running IBM Systems Director Server
Provides information about how to plan, implement, configure, and use an IBM
Systems Director Server to manage a large configuration with optimal
performance. The Performance Tuning and Scaling Guide also contains
information about the following topics:
– Running IBM Systems Director plug-ins, such as IBM Systems Director Active
Energy Manager® and IBM Scalable Systems Manager
– Integration with Tivoli® 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
www.ibm.com/systems/management/director/
View the IBM Systems Director website on ibm.com® which provides links to
downloads and documentation for all currently supported versions of IBM
Systems Director.
v IBM Systems Director Downloads
www.ibm.com/systems/management/director/downloads/
View the IBM Systems Director Downloads website on ibm.com which provides
links to download code IBM Systems Director, IBM Systems Director plug-ins,
and IBM Systems Director upward integration modules.
v IBM Systems Director Documentation and Resources
www.ibm.com/systems/management/director/resources/
View the IBM Systems Director Documentation and Resources website on
ibm.com which provides links to product documentation, Redbooks, redpapers,
white papers, and learning modules that are related to IBM Systems Director,
IBM Systems Director plug-ins, and IBM Systems Director upward integration
modules.
v IBM Systems Director Upward Integration
www.ibm.com/systems/software/director/downloads/integration.html
View the IBM Systems Director Upward Integration website on ibm.com which
provides more information about IBM Systems Director upward integration
modules that are created by IBM and other companies. IBM Systems Director
UIMs enable third-party workgroup and enterprise systems-management
products to interpret and display data that is provided by IBM Systems Director
Platform Agent managed system.
v IBM Systems Director Best Practices Wiki
www.ibm.com/developerworks/wikis/display/WikiPtype/
IBM+Systems+Director+Best+Practices+Wiki
View updated documentation and best practices for IBM Systems Director on
various systems.
v IBM Servers
www.ibm.com/servers/
View the IBM Servers website to learn about IBM Systems server and storage
products.
v IBM ServerProven®
www.ibm.com/servers/eserver/serverproven/compat/us/
View the IBM ServerProven website to learn about hardware compatibility of
IBM System x® and BladeCenter® systems with IBM applications and
middleware, including IBM Systems Director.
viii Installing on Windows and configuring the Oracle® Database

Forums
v IBM Systems Director Forum (System x, System z®, 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 on Windows and configuring the Oracle® Database
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 (8).
__ 3. Prepare firewalls and proxies on the management server (14).
__ 4. Prepare the management server (13).
__ 5. Run the Pre-Installation Utility (19.
2 Install IBM Systems Director Server.
__ 1. Install IBM Systems Director Server (27).
__ 2. Configure the database application (35).
__ 3. Verifying the management server installation. (34
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 (34).
© Copyright IBM Corp. 1999, 2012 xi

xii Installing on Windows and configuring the Oracle® Database
Checklist: Installing agents
Use this checklist to guide you through the installation process.
1 Prepare your managed systems.

__ 1. Run the Pre-Installation Utility (72.
__ 2. Prepare systems for Platform Agent (87).
__ 3. Prepare systems for Common Agent (74).
__ 4. If relevant, prepare any agentless managed systems for discovery and
management by IBM Systems Director (101).
2 Install the agents.
__ 1. Use the Agent Installation Wizard to deploy agent packages to your
managed systems (75).
© Copyright IBM Corp. 1999, 2012 xiii

xiv Installing on Windows and configuring the Oracle® Database
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
Installing Verify success Configuring after

management server Check for updates installation
Preparing to install
Installing agents Verify success

Check for updates
FMQ0558-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

Discovery
Inventory
Configure
Plugins
FMQ0560-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 on Windows and configuring the Oracle® Database

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
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
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® 5.3, burn the image onto a DVD.
After you have an installation DVD, finish preparing to install the management
server to IBM Systems Director 6.3.x. For instructions, see “Preparing the
management server.”
Downloading the installation package

To download the installation package for installing IBM Systems Director Server,
1. Download the installation package from the IBM Systems Director Downloads
website at http://www-03.ibm.com/systems/software/director/downloads/
mgmtservers.html.
2. To extract the contents of the installation package, type the following command
depending on your operating system:
v Windows:
unzip
3. If you are using Windows, change to the directory in which the installation
script, dirinstall.server, is located by typing the following command and
pressing Enter:
cd \installed_files\server\i386|x64
Where installed_files is the path to the extracted installation files.
After you finish downloading the installation package, finish preparing to install
the management server to IBM Systems Director 6.3.x. For instructions, see
“Preparing the management server.”

Before installing IBM Systems Director Server, make sure that the requirements that
are applicable to your system have been met.
Related reference:
Hardware and software requirements
Supported operating systems

The installation worksheet describes the properties and parameters required to
complete the IBM Systems Director Server installation process for a custom

installation. Depending on your configuration, you may need to contact your
database administrator for specific values.
There are two paths through the IBM Systems Director Server installation process:
basic installation and custom installation. The basic installation path installs the
managed IBM DB2® database. The managed IBM DB2 database is packaged and
installed with IBM Systems Director Server 6.3.x by default. This database is
recommended if you are installing IBM Systems Director Server for the first time
and do not have an existing database that you intend to use with the IBM Systems
Director Server. It is installed on the same server as the IBM Systems Director
Server, does not require an extra license, and is updated as part of any IBM
Systems Director Server update.
A custom installation (either using the installation wizard or a response file) allows
you to use an existing database and configure it for use with the IBM Systems
Director Server.
Related concepts:
Database application
Related tasks:
Choosing the database application
Installation worksheet when using Oracle® Database:
Use this worksheet to record and plan for a custom IBM Systems Director
installation using an Oracle® Database.
Custom installation worksheet
During the installation process, you can select a basic or custom installation. Unlike
a basic installation, the custom installation requires some values that you may
want to acquire before the installation process. Use this worksheet to record and
plan for a custom installation.
Table 1. Properties or parameters required during a custom installation process
Custom installation Your value
Setup type Custom
User credentials
Local computer name
User name
Password
Common agent configuration
Common agent port 9510 (default)
number
Nonstop service ports 9514, 9515 (default)
Agent manager configuration
Select an agent manager Create an agent manager (default)
type
v Create an agent manager
v Select an existing agent
manager
Table 1. Properties or parameters required during a custom installation process (continued)
Custom installation Your value
New agent manager configuration
Agent manager user name
Agent manager password
Agent registration
password
Database type
Select the database you Oracle® Database
intend to use.
Note: The database must See Table 2 for specific database configuration details required
be installed and configured during the installation process.
on a system in your
network.
Database administrator
credentials
Administrator name
Administrator password
Web server ports
HTTP port 8421 (default)
HTTP secure port 8422 (default)
Server startup options
v Automatically start
server at the end of the
installation
v Configure the server
service as a nonstop
service
Note: Nonstop service
monitors the IBM
Systems Director server
and restarts the server if
it appears to have
stopped. It is selected by
default.
Table 2. Database configuration information and values

Database configuration
Description attribute Value
Selected database application DbmsApplication Oracle
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.

Table 2. Database configuration information and values (continued)
Host name of the server on which the DbmsServerName Custom value:
database is installed 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
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.
Fully qualified local installation folder of DbmsDatabaseAppHome Custom value:
the database server instance or admin Example: c:\oracle\product\10.2.0\
client instance on the IBM Systems Director client_1
Server system
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 DbmsUserId Custom value:
Example: myuserid
For detailed information about user IDs,
see “Tips for user authorities and
passwords for Oracle® Database” on page
56.
Password of the database user account DbmsPassword Custom value:
Example: mypwd
For detailed information about passwords,
56.
After you complete the installation worksheet, be sure to prepare your database
and management server for the installation.
Related concepts:
Agent manager
Related tasks:
Preparing the database application
Setting the agent manager
Preparing the database application

Prepare your chosen database for use with IBM Systems Director and configure
them to work together. If you choose to use the default embedded database, this
step is not necessary.
Ensure that you have chosen the supported database application that you will use
with IBM Systems Director. See “Choosing the IBM Systems Director database
application” for information that helps you decide the database application to use.
The effort required to prepare the database depends on the database application
that you choose. Preparation might include one or more of the following tasks:
v Downloading and installing the applicable database administrator client
v Downloading and installing the applicable Java™ Database Connectivity (JDBC)
drivers
v Creating a database or server ID
v Configuring and starting a TCP/IP listener
v Setting the authentication mode.
There is no preparation required to use the system’s default database. However,

there is a database prerequisite tool that you can run to ensure that system meets
the requirements of the default database.
To use a database other than your system's default database with IBM Systems
Director, follow the steps in the appropriate topic to prepare your database
application.
Note: You can install IBM Systems Director before preparing the database, but you
will only be able to use the default IBM DB2 database until you configure IBM
Systems Director Server to use a different database.
After the database application is prepared, you can install IBM Systems Director
Server and configure it to connect to the database.

Related concepts:
Related tasks:
Configuring the database
Choosing the database application

Related reference:
Database preparation considerations for upgrading and migrating
smsave command
smrestore command
Running the Pre-Installation Utility
Preparing the Oracle® Database:
To use Oracle® Database as the database for IBM Systems Director, you must
complete some tasks to prepare your system before you install IBM Systems
Director Server.
Complete the following tasks to prepare Oracle® Database before installing IBM
Systems Director Server:
Related reference:
Supported database applications
Preparing the database for upgrading and migrating to 6.3
cfgdbcmd command
All available ports

Related information:
Oracle Database 10g Release 2 administrator client will not install on Red Hat
Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10
Tasks for the Oracle server:

1. Install Oracle® Database. See the “Supported database applications” topic for
supported versions and installation options.
2. Start the database server.
3. Create the Oracle® Database on the Oracle® Database Server using supported
Oracle® Database installation tools. In order for IBM Systems Director to use
this database, you can select the default settings during the IBM Systems
Director installation process, except in the following cases:
v Remember the database identification value. The database name is required
during the IBM Systems Director installation steps and during the post
installation process.
v Remember the database credentials you create. The password is associated
with the User ID with DBA authority. By default, the user IDs with DBA
authority for the Oracle® Database server include: SYS and SYSTEM.
However, other you can create other user IDs.
v Ensure that the character set of your new database is UTF-8.
4. If you intend to use SQL authentication to connect to the Microsoft SQL Server
(not integrated security), create a unique user ID and password on the database
server for the runtime database connection. The user ID and password do not
need any special privileges. They only need to have authority to log on to the
database. Do not use the database administrator ID or password, or any default
database user ID or password.
Notes:
a. Remember the user ID and password that you create because you must
enter them during the installation process of IBM Systems Director or in the
cfgdbcmd.rsp configuration file after the installation of IBM Systems
Director.
b. For detailed information about user authorities and passwords, see Tips for
user authorities and passwords for Oracle® Database.
c. If you plan to use smsave or smrestore with IBM Systems Director Server
and the database, you must ensure that the database instance owner is in
the same primary group as the IBM Systems Director user who performs
the backup and restore operations. This enables the database server to read
and write the database backup image to the backup directory.
d. When you create the runtime user account on the database server, the “user
must change password at next logon” option is selected by default. Ensure
that you either clear this option or change the password before configuring
IBM Systems Director. You must do this because when you run the
cfgdbcmd command, the database configuration fails and you are not given
the option to change the password. IBM Systems Director does not save the
database server administrator account user ID and password.
Tasks for IBM Systems Director Server:

1. If you chose to install the Oracle® Database on a remote server, you must install
the Oracle® Database administrator client on the same system on which IBM
Systems Director Server is installed. See the Oracle® Database documentation
for details.
2. Ensure that the environment variables are correctly set before IBM Systems
Director startup. For detailed information about environment variables,
including the required settings, see “Environment variables for Oracle®
Database” on page 12.
Note: For Linux on Power Systems and Linux on System z , you must be
logged in as root user.
Final tasks:
1. Update the tnsnames.ora and listener.ora files on the Oracle® Database server
host to include the information for your newly created database.
a. Ensure that your listener.ora file resembles the following example for each
database instance (SID_DESC):
SID_LIST_LISTENER
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)

(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = db_name_2.oracle-10g2.netfinity.com)
(SID_NAME = db_name_2)
)
(SID_DESC =
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle-10g2.netfinity.com)(PORT = 1521))
)
)
b. Ensure that the content in the tnsnames.ora file on your server with IBM
Systems Director Server installed is consistent with your listener entries. For
example:
db_name_2 =
(DESCRIPTION =
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = db_name_2.oracle-10g2.netfinity.com)
)
)
db_name_1 =
(DESCRIPTION =
(CONNECT_DATA =
)
)
2. If the Oracle® Database server is remote, ensure that the information for the
newly created database is also added to the tnsnames.ora file on the Oracle®
Database client. It should contain the same entry for this database as is
contained in the tsanames.ora file from the Oracle® Database server. See the
Oracle® Database documentation for details.
3. If you will have multiple database instances in the listener.ora file, ensure that
your Oracle® Database server is properly set up to support this situation.
a. On the Oracle® Database server, enter either one of the following commands
to launch sqlplus:
v sqlplus sys/password@db_name as sysdba where db_name is the name of
the database and password is the password for accessing the database.
v sqlplus sys/password as sysdba where password is the password for
accessing the database.
b. In sqlplus, enter the following command to change the permissions of the
remote login password file (REMOTE_LOGIN_PASSWORDFILE) to shared:
SQL > alter system set remote_login_passwordfile=SHARED scope=spfile;
SQL > shutdown immediate;
SQL > startup
SQL > quit
c. Ensure that your listener.ora file resembles the following example for each
database instance (SID_DESC):
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(PROGRAM = extproc)
)
(SID_DESC =
)
(SID_DESC =
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
)
)
d. Ensure that the content in the tnsnames.ora file on your server with IBM
Systems Director installed is consistent with your listener entries, like in the
following example:
db_name_2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = oracle-10g2.netfinity.com) (PORT = 1521))
(CONNECT_DATA =
)
)
db_name_1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = oracle-10g2.netfinity.com) (PORT = 1521))
(CONNECT_DATA =
)
)
4. Configure and restart the Oracle® Database TCP/IP listener.
After you have prepared the Oracle® Database for use with IBM Systems Director,
you can continue preparing the management server for installation. For
instructions, see “Preparing the management server” on page 4.
Environment variables for Oracle® Database:
Review the environment variables for Oracle® Database and the settings required
for IBM Systems Director.
The following table lists the environment variables for Oracle® Database and the
settings required for IBM Systems Director.
On Linux, you can set environment variables in /etc/profile so that they work
across sessions.
Table 3. Environment variables for Oracle® Database
Environment variable Settings
ORACLE_HOME Set this variable to the installation directory of
the Oracle® Database server or client.

Table 3. Environment variables for Oracle® Database (continued)
Environment variable Settings
PATH v Windows: oracle_install_root\bin
v AIX and Linux: oracle_install_root/bin
where oracle_install_root is the installation
directory of the Oracle® Database server or
client.
Preparing to install IBM Systems Director Server on Windows

Before installing IBM Systems Director on a management server running Windows,
make sure that your server meets all the applicable requirements.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Review any technical notes related to installation issues. You can search for
technical notes on the IBM Support Portal at: http://www-01.ibm.com/support/
search.wss?rs=0&q=eServerOnDemandKBRCH&r=100&sort=desc.
v Run the Pre-Installation Utility and fix any errors that it identifies. For
instructions, see “Running the Pre-Installation Utility (PIU)” on page 19.
v Ensure that your system meets the hardware and software requirements
(including those for databases, security, and networking) for installation, as
described in “Hardware and software requirements.”
v If there is an operating system update in progress, ensure that the process is
complete and you restart the system before starting the IBM Systems Director
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Systems Director” for information about these
drivers and mapping layers.
v Ensure that the Windows Installer service is enabled. If the Windows Installer
service is not enabled, the installation may fail.
v Before installing IBM Systems Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Systems Director Server, you can
reinstall IBM Storage Configuration Manager on a different system.
v Ensure that the system clocks on the systems that contain IBM Systems Director
Server and Common Agent remain synchronized.
v Acquire IBM Systems Director Server. You can install IBM Systems Director
Server from either a downloaded installation package or from an installation
DVD. Depending on which method you choose, you must either download the
installation package or prepare to use the installation DVD. For instructions, see
Acquiring IBM Systems Director Server.
v When you log on to Windows and install IBM Systems Director, the IBM
Systems Director service will automatically use your Windows user ID and
password for interactions between IBM Systems Director Server and its managed
resources. If your security policy requires an approved user ID and password for
communication between IBM Systems Director and its managed resources, you
need to change the IBM Systems Director service to use the secure service
account. To change ownership of the service account after installing IBM
Systems Director Server, complete the following steps:
1. In Windows, select Computer Management > Services and Applications >
Services.
2. Right-click IBM Systems Director Server service and select Properties.
3. Select the Log On tab.
4. Select This Account and enter the credentials of the service account. The
account must have admin rights on all of the managed resources.
v Review the Release Notes® for IBM Systems Director 6.3.2. To view and
download the Release Notes, see .
After you have prepared your management server, install IBM Systems Director.
Related tasks:
Acquiring Systems Director Server
Related reference:

Windows installation troubleshooting
Preparing firewalls and proxies for IBM Systems Director

You must configure the firewalls and proxy server to enable installation and
operation of IBM Systems Director if you have firewalls in your network, or if the
management server must use a proxy server to access the internet.
IBM Systems Director must be able to access all the managed objects in the
network, and if you will use a remote Web browser to access the management
server, the remote systems running the Web browser and the management server
must have access to each other. In addition, some functions of IBM Systems
Director, including update manager, require access to the Internet.
To enable this access, you must configure firewalls and proxies in your network to
allow access by IBM Systems Director components.
Complete the following steps to configure firewalls and proxies in your network:
1. Identify the ports that you will use in your systems-management environment
and ensure that those ports are open before you start installation. For example,
you must ensure that the listener ports for IBM Systems Director Server and
Common Agent are open. See “All available ports” for a complete list of the
ports that IBM Systems Director components can use.
Note: HTTP port 80 is required to be open for downloading updates using

Update Manager.
2. Ensure that internet connections exist to the following internet addresses as
they are required by IBM Systems Director and various plug-ins.
Note: IP addresses are subject to change, so ensure that you use DNS names
whenever possible.
Table 4. Required internet connections
DNS name IP address Port(s) Protocol(s)
Update manager

Table 4. Required internet connections (continued)
DNS name IP address Port(s) Protocol(s)
www.ibm.com 129.42.56.216, 443 and 80 https and http
129.42.58.216,
129.42.60.216
www-03.ibm.com 204.146.30.17 443 and 80 https and http
download3.boulder.ibm.com 170.225.15.76 443 and 80 https and http
download3.mul.ie.ibm.com 129.35.224.114 443 and 80 https and http
download4.boulder.ibm.com 170.225.15.107 443 and 80 https and http
download4.mul.ie.ibm.com 129.35.224.107 443 and 80 https and http
delivery04-bld.dhe.ibm.com 170.225.15.104, 443 and 80 https and http
129.35.224.104
delivery04-mul.dhe.ibm.com 129.35.224.115, 443 and 80 https and http
170.225.15.115
delivery04.dhe.ibm.com 129.35.224.105, 443 and 80 https and http
170.225.15.105
Service and Support Manager
eccgw01.boulder.ibm.com 207.25.252.197 443 https
eccgw02.rochester.ibm.com 129.42.160.51 443 https
www-945.ibm.com 129.42.26.224, 443 https
129.42.34.224,
129.42.42.224
www6.software.ibm.com 170.225.15.41 443 https
www.ecurep.ibm.com 192.109.81.20 443 https
testcase.boulder.ibm.com 170.225.15.31 21 ftps
3. If the management server requires access to the Internet but does not have
direct access, complete the following steps to configure the management server
to use the proxy when accessing the Internet.
a. Ensure that the selected proxy server is configured to use basic
authentication. The update manager task supports only basic authentication
with the proxy server. If digest or NTLM authentication are required,
update manager will be unable to access update packages from IBM.
b. Use the update manager Settings page to configure the management server
to use the proxy server. See “Changing update settings” for more
information.
Related reference:
All available ports
IBM Support Portal
Installing firmware and device drivers

Before installing IBM Systems Director on Red Hat Enterprise Linux, SUSE Linux,
VMware ESX Server, Windows Server 2003, Windows Server 2008, or Windows
Server 2012 you need to install the latest firmware and device drivers for IBM
service processors, ServeRAID controllers, and IBM adapters such as Brocade and
QLogic. To accomplish this, you can either use the IBM UpdateXpress System Pack
Installer (UXSPi) or you can install the files manually.
Note: This topic only applies to Windows and Linux for System x.
Decide the level of agent management that is required for your system. See
“Choosing the management level for managed systems” for information.
RSA II notes for installing on Linux:

v The RSA II daemon requires the libusb and libusb-devel packages, which are
typically installed by default. If your distribution or installation does not include
or install these packages, you must install them prior to installing the RSA II
daemon.
v If you are running Linux, the RSA II daemon requires that you configure RSA II
for “Linux OS” prior to installation. Change this setting through the RSA II Web
management interface or through a setting found in the system BIOS setup
utility.
To install the latest firmware and device drivers for IBM service processors and
ServeRAID controllers and ServeRAID Manager plug-ins, use the IBM
UpdateXpress System Pack Installer (UXSPi) for the latest UpdateXpress System
Pack (UXSP) that is built for the target systems that you are updating. The UXSPi
will automatically install the latest BIOS, IPMI baseboard management controller
(BMC), Remote Supervisor Adapter II (RSA II), ServeRAID, and other firmware as
a set, as required for your server. It will also automatically install the required
IPMI device drivers for the BMC and the RSA Server Software for the RSA II.
Notes:
v If newer versions of the individual driver and firmware updates that were
included in your UXSP are released after you apply the UXSP, do not install the
newer individual updates unless they address a very specific need or fix.
Instead, wait until a new UXSP is released, then apply that.
v IBM Systems Director has compliance policies that provide visual indications of
a system's level of compliance as determined by rules that you set up in each
compliance policy. If you utilize compliance policies, it is recommended to base
them on UXSP updates instead of individual driver and firmware updates. For
example, a recommended compliance policy would stipulate that all of the
systems in your environment should have at least the latest UXSP installed, and
an environment that contains the latest UXSP will be considered in compliance.
IBM Hardware Support will also consider such an environment as appropriate
and fully supported, and PMRs should not require that you apply any further
updates to your systems unless a fix is identified in a newer version of an
individual update.
To download the UXSP that contains the needed firmware and drivers for your
system, see "IBM Support Portal" and select the appropriate UXSP library.
If you choose to not use the UpdateXpress System Pack Installer, perform the
following steps to download and install the latest firmware and device driver files
for your Red Hat Enterprise Linux, SUSE Linux, or VMware ESX Server system.
Install only the required firmware for each of the following elements that you have
in your environment.
Notes:
v These steps apply to only Red Hat Enterprise Linux, SUSE Linux, or VMware
ESX Server systems, though the steps that are required for Windows systems are
similar.

v See “Preparing to manage service processors with IBM Systems Director” for
more information about service processors.
v If your system contains an Integrated systems management processor (ISMP),
you need to instead install LM78 and SMBus drivers. See “Installing the IBM
LM78 or SMBus device driver” for information.
1. Install the latest firmware for BMC service processors.
a. Download into a temporary directory the
ibm_fw_bmc_XXXXXXX_linux_i386.sh BMC firmware file from "IBM Support
Portal." This file is available for all supported Red Hat Enterprise Linux,
SUSE Linux, and VMware ESX Server operating systems, so download the
version that applies to your system.
b. Navigate to the temporary directory into which you downloaded the file.
c. Use a console prompt from the temporary directory to run the following
command:
./ibm_fw_bmc_XXXXXXX_linux_i386.sh -s -a -s
2. Install the latest daemon for the RSA II service processors.
a. Download into a temporary directory the ibm_svc_rsa2_XXXXXXX_linux_32-
64.tgz RSA II daemon file from "IBM Support Portal." This file is available
for all supported Red Hat Enterprise Linux, SUSE Linux, and VMware ESX
Server operating systems, so download the version that applies to your
system.
commands:
tar xzf ibm_svc_rsa2_XXXXXXX_linux_32-64.tgz
export PATH=$PATH:/usr/local/bin;./install.sh --update
3. Install the latest firmware for the RSA II service processors.
a. Download into a temporary directory the
ibm_fw_rsa2_XXXXXXX_linux_i386.sh RSA II firmware file from "IBM
Support Portal." This file is available for all supported Red Hat Enterprise
Linux, SUSE Linux, and VMware ESX Server operating systems, so
download the version that applies to your system.
commands:
tar xzf ibm_fw_rsa2_XXXXXXX_linux_i386.sh
export PATH=$PATH:/usr/local/bin;./install.sh --update -force-if-overridden
4. Install the latest device drivers for your Integrated Management Module (IMM)
service processors.
a. Go to "IBM Support Portal."
b. Download firmware file ibm_fw_imm_yuoo******.bin into a temporary
directory.
c. Log in to the IMM web console.
d. Navigate to the "Update Firmware" page and click Browse.
e. Select the downloaded firmware file and click Update. The firmware file is
uploaded to the IMM.
f. When the upload completes, click Continue to complete the installation.
5. Install the latest device drivers for your Integrated Management Module II
(IMM2) service processors.
b. Download the firmware file ibm_fw_imm2_1aoo******_anyos_noarch.uxz into
a temporary directory.
c. Log in to the IMM2 web console.
d. Navigate to the "Server Firmware" page and click Update Firmware.
e. Select the downloaded firmware file.
f. Click Next. The firmware file is uploaded to the IMM2.
g. When the upload completes, the "Action 1" drop-down list is displayed.
Select "Update the primary bank (default action)" or "Update the backup
bank" from the list. If you want to update both, click the Add action button
and make sure both actions are selected.
h. Click Next to complete the installation.
6. Install the latest firmware and device drivers for ServeRAID controllers.
Note: If you are installing "IBM ServeRAID Firmware and BIOS Update 7.12.14
for Windows - IBM System x" , the 8.3 short file name (SFN) should be enabled,
and the TMP environment variable should exist and point to a directory. For
information about how to enable the 8.3 short file name support, refer to your
Windows support documentation.
a. Download into a temporary directory the following individual files that are
required for your servers from "IBM Support Portal."
Note: The firmware packages apply to all Linux and VMware ESX Server
distributions, but you must download the appropriate device driver for
your particular distribution.
Table 5. Required ServeRAID controller firmware and device driver files
Files (see RHEL AS 5 RHEL AS 5 SLES 9 SLES 9 SLES 10 SLES 10 VMware
Key 1) U1 32-bit U1 64-bit 32-bit 64-bit 32-bit 64-bit ESX Server
1 X X
2 X X
3 X X
4 X X X X X X X
5 X X
6 X X
7 X X
8 X X X X X X X
Key 1:
v 1: ServeRAID MR 10 Device driver (systems with ServeRAID 10
hardware): ibm_dd_sraidmr_XXXXXXXX_rhel5_32-64.tgz
hardware): ibm_dd_sraidmr_XXXXXXXX_sles9_32-64.tgz
hardware): ibm_dd_sraidmr_XXXXXXXX_sles10_32-64.tgz
v 4: ServeRAID MR 10 Firmware (systems with ServeRAID 10 hardware):
ibm_fw_sraidmr_XXXXXXXXXXX_linux_32-64.bin
v 5: ServeRAID 8 Device driver (systems with ServeRAID 8 hardware):
ibm_dd_aacraid_XXXXXXXXXXX_rhel5_32-64.tgz

ibm_dd_aacraid_XXXXXXXXXXX_sles9_32-64.tgz
ibm_dd_aacraid_XXXXXXXXXXX_sles10_32-64.tgz
v 8: ServeRAID 8 Firmware (systems with ServeRAID 8 hardware):
ibm_fw_aacraid_8k-8kl-X.X.X-XXXXX_linux_32-64.bin
b. Navigate to the temporary directory into which you downloaded the files.
c. Use a console prompt from the temporary directory to run the installation
command for each of the downloaded files. Use the following installation
command examples as guides:
Example: ServeRAID 8 on RHEL 5
tar xzf ibm_dd_aacraid_1.1.5.2434_sles10_32-64.tgz
export PATH=/usr/local/bin:$PATH ; ./install.sh --update
./ibm_XX_aacraid_XXXXXXXXXXX_XXXX_XXX.bin -s
Example: ServeRAID 10 on RHEL 5
tar xzf ibm_dd_sraidmr_XXXXXXXX_rhel5_32-64.tgz
export PATH=/usr/local/bin:$PATH ; ./install.sh --update
./ibm_fw_sraidmr_XXXXXXXXXXX_linux_32-64.bin -s
7. Install the latest device drivers for your IBM Brocade Adapters.
b. Download the following device drivers:
v For the IBM Flex System FC Adapter, download version 3.1.0.0 device
drivers.
v For the IBM System x HBA cards, download version 3.1.0.0 device
drivers.
Running the Pre-Installation Utility (PIU)

Use the Pre-Installation Utility to ensure that your system meets the IBM Systems
Director requirements.
The IBM Systems Director Pre-Installation Utility scans the local system to identify
potential problems that might prevent IBM Systems Director from installing
successfully. The utility runs checks on disk space, memory, prerequisite software,
processors, and more. It does not scan for device drive or firmware requirements.
The tool is run automatically during the installation process; however, you can
choose to run the tool before starting the installation wizard as well. This practice
is a good way to find and fix possible problems in advance.
Note: If you are using a local database, the requirements might be slightly higher
than what is checked by the Pre-Installation Utility. See the hardware requirements
topics for information related to database considerations.
Related concepts:
“Installation overview” on page 1
Related tasks:
Preparing to upgrade and migrate

Related reference:
Planning
Pre-Installation Utility
Running the IBM Systems Director Pre-Installation Utility on the

management server (Windows)
To run the IBM Systems Director Pre-Installation Utility on Windows, complete the
following steps.
You can obtain or run the Pre-Installation Utility from three locations.
Table 6. Obtaining the Pre-Installation Utility
Location Action
IBM Systems Director 6.3.2 DVD If you do not already have the DVD, you
can burn the image onto DVD from the IBM
Systems Director Downloads website.
SysDir_PreInstUtil_6_3_2_Windows.zip Download the Pre-Installation Utility
directly from the IBM Systems Director
Downloads website.
Included in the Download the entire IBM Systems Director
SysDir6_3_2_Server_Windows.zip file installation package from the Downloads
website. The Pre-Installation Utility is
automatically started as part of the
installation process on the management
server.
Note: The IBM Systems Director downloads website always contains the most recent
version of the Pre-Installation Utility.
1. To start the IBM Systems Director Pre-Installation Utility, choose the applicable
method:
v DVD
v Directly from the Pre-Installation Utility download
v Included with the installation package
Complete the following steps.
v DVD
a. Insert the DVD into the DVD-ROM drive.
b. If the IBM Systems Director Welcome window automatically opens, then
1) Select your language.
2) Click Systems Director Server.

3) Click Systems Director Pre-Installation Utility.
c. If the IBM Systems Director Welcome window does not automatically
open, then complete the following steps, as applicable:
1) Click Start > Run
2) In the Open field, type the following command and press Enter:
e:\server\{i386 or x64}\checkds\checkds.bat
where e is the DVD-ROM drive letter on your system. The IBM

Systems Director Pre-Installation Utility starts.
v Directly from the Pre-Installation Utility download
a. Extract the contents of the Pre-Installation Utility package, type the
following command, and press Enter:
unzip SysDir_PreInstUtil_6_3_2_Windows.zip
b. Change to the directory where the Pre-Installation Utility script is located
by running the following command:
cd checkds
c. Start the Pre-Installation Utility by running the following command:
checkds.bat
v Included with the installation package
These steps assume you already downloaded IBM Systems Director and
extracted the installation package.
a. Change to the directory where the launchpad*.exe file resides, type the
following command (as applicable), and press Enter:.
launchpad.exe
or
launchpad64.exe
The IBM Systems Director Welcome window appears.

b. On the Welcome window, complete the following steps to start the
Pre-Installation Utility:
2. Reports are generated and results are displayed in the command window or
the default browser. Refer to the \checkds\readme.txt file for more information
about checkds.bat options, the reports that are generated, and return codes. The
\checkds.bat -? command also displays supported syntax.
Related reference:
JAWS does not read Pre-Installation Utility content
Windows pre-installation checks

After you run the Pre-Installation Utility, you receive a report summarizing the
results of the pre-installation checks performed on your system. Use this
information to correct potential problems before installing IBM Systems Director
Server 6.3.x.
Some of the checks performed by the Pre-Installation Utility include:
v Runtime authentication
v OS compatibility
v Host architecture
v Processors
v Disk space available
v Memory available
v Performance information
v User name
v Short name
v Paging size
v Managed IBM DB2 prerequisite check
Note:
The managed IBM DB2 prerequisite check is available through the installation
process when installing IBM Systems Director from the DVD or the
downloadable installation package. The managed IBM DB2 prerequisite check is
not available from the downloadable Pre-Installation Utility.
Related reference:
Pre-Installation Utility
Port availability:
IBM Systems Director Server and Common Agent require a number of ports to be
available.
Ensure the following ports are available and start the installation process again.
Option Description
Management server The IBM Systems Director installation
processes and Web server require access to a
number of ports on the management server.
If these ports are blocked by a firewall or
used by another process, the installation
fails. By default, IBM Systems Director
server requires the following ports:
v 8421
v 8422
v 20000

Option Description
Common Agent Ensure that the installation is set to use
ports that are not already in use. By default,
the Common Agent installation process
requires the following ports:
v 9510
v 9514
v 9515
If these ports are already in use when you
install the agent, the installation fails. These
ports might be in use is if you have a
different version of the CAS agent installed,
for example as part of the Tivoli
Provisioning Manager agent. Ensure these
ports are available and start the installation
process again.
Platform Agent Ensure that the installation is set to use
ports that are not already in use. By default,
the Platform Agent installation process
requires the following ports:
v 15988
v 15989
v 6989
If these ports are already in use when you
install the agent, the installation fails.
Related reference:
All available ports
Promotion check:
The promotion check determines whether you can perform an upgrade or

promotion on the system. An upgrade installs a later version of the product. A
promotion installs a common agent over an existing platform agent.
Related tasks:
Determining your upgrade path
Determining the installed version
Migration checks:
Migrating IBM Systems Director Server from 6.2.x to 6.3.2 is not supported. The
migration validity check determines whether 6.2.x is installed, and instructs the
user to migrate to 6.3.0 and then to use update manager to update to 6.3.2.
This check only shows a failure if it detects a version before IBM Systems Director
Server 6.2.x. If the Pre-Installation Utility cannot read existing product data, you
receive a warning.
1. Verify that you have IBM Systems Director Server 6.2.x installed.
2. Ensure that your management server is running IBM Systems Director Server
6.2.x. If not, you must first upgrade your system to IBM Systems Director
Server 6.2.x. If you do not want to retain previous product files or data, you
might prefer to uninstall an older version and perform a new 6.3 installation.
Related tasks:
Determining your upgrade path
Determining the installed version
RSA check:
You cannot upgrade when the Remote Supervisor Adapter II (RSA II) is installed
and enabled.
If the Pre-Installation Utility detects the Remote Supervisor Adapter II (RSA II) or
if it detects RSA II along with IBM Director Core Services 5.20.31 or older, the
Pre-Installation Utility check fails.
1. Ensure that the management server is running IBM Systems Director Server
6.2.x before you upgrade. If not, you must first upgrade your system to IBM
Systems Director Server 6.2.x. If you do not want to migrate existing data, you
might prefer to uninstall an older version and perform a new IBM Systems
Director Server 6.3 installation.
2. If you uninstall the old version of IBM Systems Director Server, ensure that the
RSA service processor is uninstalled or disabled.
Host name check:
Ensure that your system is able to resolve both its own name and localhost name.
Use either the domain name server (DNS) or the /etc/hosts file
(%WinDir%\System32\Drivers\etc\hosts file for Windows) to ensure that your
system can resolve its own name and localhost name.
Important: If there is no DNS setting on your Common Agent system, to ensure

that Common Agent works properly, you must set all global IP addresses in
/etc/hosts (%WinDir%\System32\Drivers\etc\hosts for Windows).
1. Use the ping command to ensure that the localhost name resolves successfully. If
the ping command is unsuccessful, ping the gateway IP address and the DNS
server IP address to help identify where the communication problem is
occurring.
2. View the IP address and host name information in the /etc/hosts file to ensure
that they are listed correctly.
Valid user ID check:
Your user ID must be valid for both Windows and IBM DB2.
You will receive an error if the user ID that you used to log on to Windows is not
valid for managed IBM DB2. Ensure that your user ID meets the following
requirements:
1. Cannot be USERS, ADMINS, GUESTS, PUBLIC, or LOCAL.
2. Cannot begin with IBM, SQL or SYS.
3. Cannot be any of the following SQL reserved words:
A

ACTION, ACTIVATE, ADD, AFTER, ALIAS, ALL, ALLOCATE, ALLOW,
ALTER, AND, ANY, APPEND, AS, ASC, ASENSITIVE, ASSOCIATE, ASUTIME,
AT, ATTRIBUTES, AUDIT, AUTHORIZATION, AUX, AUXILIARY
B
BEFORE, BEGIN, BETWEEN, BINARY, BIND, BIT, BUFFERPOOL, BY
C
CACHE, CALL, CALLED, CAPTURE, CARDINALITY, CASCADED, CASE,
CAST, CCSID, CHAR, CHARACTER, CHECK, CLIENT, CLONE, CLOSE,
CLUSTER, COLLECT, COLLECTION, COLLID, COLUMN, COMMENT,
COMMIT, COMPACT, COMPRESS, CONCAT, CONDITION, CONNECT,
CONNECTION, CONSTRAINT, CONTAINS, CONTINUE, COPY, COUNT,
COUNT_BIG, CREATE, CROSS, CUBE, CURRENT, CURRENT_DATE,
CURRENT_LC_CTYPE, CURRENT_PATH, CURRENT_SCHEMA,
CURRENT_SERVER, CURRENT_TIME, CURRENT_TIMESTAMP,
CURRENT_TIMEZONE, CURRENT_USER, CURSOR, CYCLE
D
DATA, DATABASE, DATAPARTITIONNAME, DATAPARTITIONNUM, DATE,
DAY, DAYS, DB2GENERAL, DB2GENRL, DB2SQL, DBINFO,
DBPARTITIONNAME, DBPARTITIONNUM, DEACTIVATE, DEALLOCATE,
DECLARE, DEFAULT, DEFAULTS, DEFER, DEFINE, DEFINITION, DELETE,
DENSE_RANK, DENSERANK, DESC, DESCRIBE, DESCRIPTOR,
DETERMINISTIC, DIAGNOSTICS, DISABLE, DISALLOW, DISCONNECT,
DISTINCT, DO, DOCUMENT, DOUBLE, DROP, DSSIZE, DYNAMIC
E
EACH, EDITPROC, ELSE, ELSEIF, ENABLE, ENCODING, ENCRYPTION,
END, END-EXEC, ENDING, ENFORCED, ERASE, ESCAPE, EVERY, EXCEPT,
EXCEPTION, EXCLUDING, EXCLUSIVE, EXECUTE, EXISTS, EXIT, EXPLAIN,
EXTEND, EXTERNAL, EXTRACT
F
FENCED, FETCH, FIELDPROC, FILE, FINAL, FOR, FOREIGN, FREE,
FREEPAGE, FROM, FULL, FUNCTION
G
GBPCACHE, GENERAL, GENERATED, GET, GLOBAL, GO, GOTO, GRANT,
GRAPHIC, GROUP
H
HANDLER, HASH, HASHED_VALUE, HAVING, HINT, HOLD, HOUR,
HOURS
I
IDENTITY, IF, IMMEDIATE, IMPLICITLY, IN, INCLUDE, INCLUDING,
INCLUSIVE, INCREMENT, INDEX, INDICATOR, INF, INFINITY, INHERIT,
INNER, INOUT, INSENSITIVE, INSERT, INTEGRITY, INTERSECT, INTO, IS,
ISOBID, ISOLATION, ITERATE
J
JAR, JAVA, JOIN
K
KEEP, KEY
L
LABEL, LANGUAGE, LATERAL, LC_CTYPE, LEAVE, LEFT, LEVEL2, LIKE,
LINKTYPE, LOCAL, LOCALDATE, LOCALE, LOCALTIME,
LOCALTIMESTAMP, LOCATOR, LOCATORS, LOCK, LOCKMAX, LOCKSIZE,
LOG, LOGGED, LONG, LOOP
M
MAINTAINED, MATERIALIZED, MAXVALUE, MICROSECOND,
MICROSECONDS, MINPCTUSED, MINUTE, MINUTES, MINVALUE, MIXED,
MODE, MODIFIES, MONTH, MONTHS
N
NAN, NATIONAL, NCHAR, NCLOB, NEW, NEW_TABLE, NEXTVAL, NO,
NOCACHE, NOCYCLE, NODENAME, NODENUMBER, NOMAXVALUE,
NOMINVALUE, NONE, NOORDER, NORMALIZED, NOT, NULL, NULLS,
NUMPARTS, NVARCHAR
O
OBID, OF, OLD, OLD_TABLE, ON, OPEN, OPTIMIZATION, OPTIMIZE,
OPTION, OR, ORDER, ORGANIZE, OUT, OUTER, OVER, OVERRIDING
P
PACKAGE, PADDED, PAGE, PAGESIZE, PARAMETER, PART, PARTITION,
PARTITIONED, PARTITIONING, PARTITIONS, PASSWORD, PATH, PCTFREE,
PIECESIZE, PLAN, POSITION, PRECISION, PREPARE, PREVVAL, PRIMARY,
PRIQTY, PRIVILEGES, PROCEDURE, PROGRAM, PSID, PUBLIC
Q
QUERY, QUERYNO
R
RANGE, RANK, RCDFMT, READ, READS, RECOVERY, REFERENCES,
REFERENCING, REFRESH, RELEASE, RENAME, REPEAT, RESET, RESIGNAL,
RESTART, RESTRICT, RESULT, RESULT_SET_LOCATOR, RETURN, RETURNS,
REVOKE, RID, RIGHT, ROLE, ROLLBACK, ROLLUP, ROUND_CEILING,
ROUND_DOWN, ROUND_FLOOR, ROUND_HALF_DOWN,
ROUND_HALF_EVEN, ROUND_HALF_UP, ROUND_UP, ROUTINE, ROW,
ROW_NUMBER, ROWNUMBER, ROWS, ROWSET, RRN, RUN
S
SAVEPOINT, SBCS, SCHEMA, SCRATCHPAD, SCROLL, SEARCH, SECOND,
SECONDS, SECQTY, SECURITY, SELECT, SENSITIVE, SEQUENCE, SESSION,
SESSION_USER, SET, SIGNAL, SIMPLE, SKIP, SNAN, SOME, SOURCE,
SPECIFIC, SQL, SQLID, STACKED, STANDARD, START, STARTING,
STATEMENT, STATIC, STATMENT, STAY, STOGROUP, STORES, STYLE,
SUBSTRING, SUMMARY, SYNONYM, SYSFUN, SYSIBM, SYSPROC, SYSTEM,
SYSTEM_USER
T
TABLE, TABLESPACE, TABLESPACES, THEN, TIME, TIMESTAMP, TO,
TRANSACTION, TRIGGER, TRIM, TRUNCATE, TYPE
U
UNDO, UNION, UNIQUE, UNTIL, UPDATE, USAGE, USER, USING
V
VALIDPROC, VALUE, VALUES, VARIABLE, VARIANT, VCAT, VERSION,
VIEW, VOLATILE, VOLUMES
W
WHEN, WHENEVER, WHERE, WHILE, WITH, WITHOUT, WLM, WRITE
X

XMLELEMENT, XMLEXISTS, XMLNAMESPACES
Y
YEAR, YEARS, YES
Installing IBM Systems Director on the management server

After preparing your system, use the IBM Systems Director Server installation
procedure for the operating system on which you plan install IBM Systems
Director Server.
As part of the installation process, the Pre-Installation Utility runs automatically to

ensure that your system meets specific requirements. In addition, Service and
Support Manager, Active Energy Manager, and IBM Systems Director VMControl
are also installed. However, Active Energy Manager and IBM Systems Director
VMControl must be activated if you intend to use them.
Note: You are advised to not install IBM Systems Director on the same system as
IBM Storage Configuration Manager (SCM).
Related tasks:
Installing IBM Systems Director Server on Windows

After preparing your system, you can install IBM Systems Director Server on a
Windows system by downloading the installation files from the IBM Systems
Director support Web site or by using the DVD. You can then perform a standard
installation or upgrade by using the wizard in a standard interactive mode, or you
can perform an unattended (either with or without status feedback) installation or
upgrade by using a response file that automatically provides answers to the
questions that the wizard poses.
Installing IBM Systems Director Server on Windows using the installation

wizard:
Use the IBM Systems Director Server installation wizard to install IBM Systems
Director Server on a system that is running Windows.
The following graphic shows all the components included in the installation
package.
Management server
Installation includes:
- Management Server
- Web Interface
- Command-line Interface
- Common Agent
- Platform Agent
- Service and Support Manager
FQM0557-0
- Active Energy Manager

- VMControl
When you install IBM Systems Director Server, the installation wizard
automatically installs the necessary components and databases that you choose.
You can install IBM Systems Director Server on Windows from either installation
media or from a downloaded installation package.
To install IBM Systems Director Server, log in with an administrator account and
1. Start the install from the installation source:
v Downloaded installation files:
a. Click Start > Run.
b. In the Open field, type the following command and press Enter:
\installation_directory\installation_file
where:
– installation_directory is the path to the extracted installation files.
– installation_file is IBMSystemsDirectorServerSetup.exe for 32 bit
systems or IBMSystemsDirectorServerSetup64.exe for 64 bit systems.
For more robust installation logs, specify the verbose option.
c. The installation wizard for IBM Systems Director is shown.
v DVD media:
b. Determine whether the IBM Systems Director Welcome window
automatically opens:
– If yes, go to Step 3f.
– If no, go to Step 3c.
c. Click Start > Run
d. In the Open field, type the following command and press Enter:
\dvd_drive\launchpad_file
where:
– dvd_drive is the drive that contains the DVD.
– launchpad_file is launchpad.exe for 32-bit systems or launchpad64.exe
for 64 bit systems.
e. The Welcome window opens.
f. Select your language.
g. Click IBM Systems Director Server.
h. Click Install IBM Systems Director Server.
Alternately, you can start the installation wizard by using the keyboard. For
instructions, see “Starting the installation wizard for IBM Systems Director
Server on Windows by using the keyboard” on page 32.
2. Click Next. The License Agreement page is displayed
3. Select I accept the terms in the license agreement and click Next. The Feature
and installation directory selection page is displayed.
4. Continue to complete the wizard. There is a basic setup type and a custom
setup type.
Basic With basic installation, you are presented with the minimum number of
setup screens and IBM Systems Director default settings are used. The
user ID and password that you enter on the User account page is also
used for the configuration of the embedded agent manager for the
server.

Custom
With custom installation, you are presented with all the setup screens
and can change the IBM Systems Director default values, such as which
database application to use, the web server ports, and agent manager
configuration, as necessary. Use the Custom installation worksheet to
record and collect parameters required during a custom installation
process.
5. If you used the DVD for installation, remove the DVD from the drive.
6. If you are prompted to restart your system, click Yes.
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installed
on the system, it is installed during the IBM Systems Director Server
installation. If the upgrade is necessary, the system prompts you to restart
following the installation of IBM Systems Director Server without specifying
that MSI was installed. You are prompted to restart whether or not the IBM
Systems Director Server installation is completed successfully.
After you have installed IBM Systems Director Server, you can start IBM Systems
Director Server and verify that the installation was successful. For instructions, see
“Verifying the successful installation of IBM Systems Director on the management
server” on page 34.
Related tasks:
Upgrading and migrating Systems Director on Windows using the installation

wizard
Recovering from a failed installation of IBM Systems Director Server 6.3.x
Related reference:
smstart command

Exchanging information with IBM
Performing an unattended or silent installation of IBM Systems Director Server

on Windows:
After preparing your System x server for the installation of IBM Systems Director,
you can perform an unattended or silent installation of IBM Systems Director
Server by using a response file. This method creates a standard installation file that
can be used on many systems.
The following graphic shows all the components included in the installation
package.
Management server
Installation includes:
- Management Server
- Web Interface
- Command-line Interface
- Common Agent
- Platform Agent
- Service and Support Manager
FQM0557-0
- Active Energy Manager
- VMControl
When you perform an unattended installation of IBM Systems Director Server, the
response file provides answers to the questions that are posed by the installation
wizard.
You can install IBM Systems Director Server on Windows from either installation
media or from a downloaded installation package.
After the installation process, you can configure a database to use with IBM
Systems Director and configure the agent manager.
To use a response file to install IBM Systems Director Server on Windows, log in
with an administrator account and complete the following steps:
1. If you are using the downloaded installation package, then go to the next step.
If you are using a DVD, then complete the following substeps to start the
installation:
b. If the installation program starts automatically and the IBM Systems
Director Setup window opens, close it.
c. Copy the dirserv.rsp response file to a local directory. A sample response
file named dirserv.rsp is located in the \i386 folder or the \x64 folder.
2. Open the copy of the dirserv.rsp file, which follows the Windows INI file
format, in an ASCII text editor.
3. Modify and save the response file with a new file name. For example, rename
the dirserv.rsp file to myresponsefile.rsp. This file is fully commented.
For information and tips for modifying the dirserv.rsp file, see “Tips for
creating the server response file for IBM Systems Director Server” on page 33.
4. Open a command prompt and change to the directory that contains the IBM
Systems Director Server installation file (IBMSystemsDirectorServerSetup.exe
or IBMSystemsDirectorServerSetup64.exe).
5. From the command prompt, type the following command and press Enter:
installationfile installationtype rsp="responsefile" option
where the variables are defined as follows:
installationfile
One of the following installation files:
v For a 32 bit system, the installation file is the
IBMSystemsDirectorServerSetup.exe file.

v For a 64 bit system, the installation file is the
IBMSystemsDirectorServerSetup64.exe file.
installationtype
One of the following commands:
v The unattended command shows the progress of the installation but
does not require any user input.
v The silent command suppresses all output to the screen during
installation.
responsefile
The absolute path and name of the response file that you created
previously. For example, c:\myfolder\myresponsefile.rsp. The rsp
parameter is optional. If you do not include the rsp parameter, the
installer uses the default response file in the package.
option One of the following optional parameters:
Table 7. Optional installation parameters
Optional parameter What it does
waitforme Ensures that installation processing will not end until this
installation is completed.
debug Logs all messages that are sent by the Microsoft Windows
Installer log engine, including status and information
messages.
log=logfilename Specifies the fully qualified name of an alternative log file.
verbose Enables verbose logging.
encryptonly Prepares the response file to use a secure managed IBM DB2
password.
For example, type the following command:

IBMSystemsDirectorServerSetup.exe silent rsp="c:\myfolder\myresponsefile.rsp"
This example performs a silent installation of IBM Systems Director Server on

Windows using the myresponsefile.rsp response file.
6. If you set the RebootIfRequired parameter to Y in the response file, reboot the
system if prompted to do so.
Notes:
a. For Windows 2008, Service Pack 1 and earlier, if Microsoft Windows
Installer (MSI) 4.5 is not installed, then you are prompted to install
Microsoft Windows Installer (MSI) 4.5 and to run the installation program
again after the system restarts.
b. For Windows 2008 R2, MSI version 4.5 comes installed on the system.
c. For all other supported Windows platforms, if Microsoft Windows Installer
(MSI), version 4.5 or later is not installed on the system, it is installed
during the IBM Systems Director Server installation. If the upgrade of MSI
is necessary, the system prompts you to restart following the installation of
IBM Systems Director Server without specifying that MSI was upgraded.
Unless you install IBM Systems Director Server by using the response file
and set the RebootIfRequired parameter to N, you are prompted to restart
whether the IBM Systems Director Server installation completes
successfully.
8. You must configure your database if you choose one of the following
installation options:
v Basic silent installation with managed IBM DB2 database and then a switch
to a custom database
v Custom silent installation with any database other than the managed IBM
DB2 database
For instructions, see Configuring the database for use with IBM Systems
Director.
9. Run the following command in the \director\bin directory to configure the
agent manager:
cfgserver.bat -am
10. Run the following command to manually restart the IBM Systems Director
Server service:
net start dirserver
After you have installed IBM Systems Director Server, you can start IBM Systems
Director Server and verify that the installation was successful. For instructions, see
“Verifying the successful installation of IBM Systems Director on the management
server” on page 34.
Related tasks:

Recovering from a failed installation of IBM Systems Director Server 6.3.x
Related reference:
smstart command
cfgdbcmd command
smreset command

Starting the installation wizard for IBM Systems Director Server on Windows by
using the keyboard:
Screen readers might not process the IBM Systems Director Setup window
correctly when you use a mouse. You can start the installation wizard for IBM
Systems Director Server on Windows using the keyboard.
To start the installation wizard for IBM Systems Director Server by using the
keyboard, complete the following steps:
1. Open Windows Explorer.
2. Browse to the \server\platform directory on the DVD, where platform is i386
or x64.

3. Run the IBMSystemsDirectorServerSetup.exe or
IBMSystemsDirectorServerSetup64.exe program. The installation wizard starts,
and the IBM Systems Director Setup window opens.
Tips for creating the server response file for IBM Systems
Director Server
You can use these tips and techniques to modify the sample dirserv.rsp server
response file for your IBM Systems Director Server 6.3.2 installation or IBM
Systems Director Server 6.3.0 upgrade.
About the server response file
You can specify the following items in the server response file:
v Specify the Web console port numbers
v Specify the Tivoli Provisioning Manager host name and IP address
v Enable or disable the nonstop service, which keeps the server continuously
running
v Specify a different location from where to install updates
v If you are installing IBM Systems Director Server, you must specify the database
type that you plan to use with IBM Systems Director Server:
– If you want to use IBM DB2, Microsoft SQL Server, Microsoft SQL Server
Express, or Oracle® Database, you must specify USE_MANAGED_DB=0.
v If you are upgrading IBM Systems Director Server to version 6.3.0 and migrating
your database, you must specify migration options:
– If you plan to migrate your database data, you must specify
MIGRATE_DATA=1.
– If you do not plan to migrate your database data, you must specify
MIGRATE_DATA=0.
– If you do not plan to migrate to the managed IBM DB2 database, you must
specify MIGRATE_TO_MANAGED_DB2=0.
Tips and techniques
Apply the following tips when you modify the sample dirserv.rsp server
response file during the installation or upgrade processes of IBM Systems Director
Server:
v A sample response file named dirserv.rsp resides in the same directory as the
dirinstall.server installer.
v In the response file, “1” indicates that an item is installed or upgraded and “0”
indicates that an item is not installed or upgraded.
v If you want to use the default for any value in the response file, comment out
that value with a “#” symbol at the beginning of the line instead of leaving the
value blank.
v If you need to enter any Windows-based locations, ensure that you include the
back slash after drive_letter. For example, use C:\foldername instead of
C:foldername.
Related tasks:

Managed IBM DB2 installation fails
Verifying the successful installation of IBM Systems Director

on the management server
You can verify a successful installation by logging into the Web interface, and
verifying the environment variables.
To verify that the installation was successful, complete the following steps:
1. Log in to the Web interface for IBM Systems Director Server. For instructions,
see Logging on to IBM Systems Director Server for the first time.
2. If you are using Oracle® Database, verify that your library path environment
variables are still set correctly, and fix any that are not correct. For detailed
information about environment variables, see “Environment variables for
Oracle® Database” on page 12.
After you have verified that the installation was successful, complete the following
tasks:
1. Use update manager to update to the latest version of IBM Systems Director, if
updates are available. For instructions, see Updating IBM Systems Director.
2. If IBM Systems Director Server is running on Windows and you uninstalled
IBM Storage Configuration Manager before the install, reinstall IBM Storage
Configuration Manager on a different system.
3. Configure IBM Systems Director plug-ins that were installed with IBM Systems
Director Server. For instructions, see Configuring IBM Systems Director
plug-ins.
4. You can switch your database to a different database type at any time. For
instructions, see Switching the database that IBM Systems Director uses.
Configuring IBM Systems Director Server after installation

You might need to configure the database, configure systems, and set up your
environment before you start to use IBM Systems Director.
Configure IBM Systems Director Server after a successful installation, so that you
can get the most benefit from the product, and be able to work efficiently. Do not
confuse this task with Configuring Systems, which is a separate topic for
configuring those resources that are controlled by IBM Systems Director.
The IBM Systems Director home page provides a quick overview, as well as links
to all necessary configuration tasks.
To configure IBM Systems Director, complete the following topics.

Related concepts:
The Home page

Related tasks:
Upgrading and migrating IBM Systems Director Server
Logging into IBM Systems Director Server
Collecting and viewing inventory data
Configuring the database for use with IBM Systems Director

Complete this procedure to configure IBM Systems Director to use a non-default
database if you are installing IBM Systems Director Server 6.3.x.
The following procedure applies to your situation if you are installing IBM
Systems Director Server 6.3.x and plan to use one of the following databases:
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
You do not need to perform this procedure in the following situations:

v If you are installing IBM Systems Director Server 6.3 on Windows by using the
installation program wizard, you do not need to perform this procedure. The
installation program wizard collects the required configuration information
instead of using the cfgdbcmd.rsp response file.
v If you plan to use the managed IBM DB2 database, you do not need to complete
this procedure. IBM Systems Director Server 6.3.x automatically installs and
configures the database for use with IBM Systems Director Server 6.3.x.
Before you start, complete the following steps:

v Ensure that the database instance is created and accessible.
v Ensure that all prerequisites for connecting to the database application are
installed and configured. For instructions, see Preparing the database
application.
v Verify that there is no other IBM Systems Director Server configured to use the
database. Do not configure more than one IBM Systems Director Server to use
the same database.
v Ensure that IBM Systems Director Server is stopped before starting this
procedure.
Complete the following steps to use the cfgdbcmd.rsp file to configure your
database:
1. Open the cfgdbcmd.rsp file with any text editor. The cfgdbcmd.rsp file resides
in the <install_root>\proddata directory, where <install_root> is the root
directory of your IBM Systems Director installation. For example on Windows,
\program files\ibm\director\proddata.
2. In the cfgdbcmd.rsp file, ensure that the configuration information for your
chosen database is commented correctly:
v Ensure that the information for your database is not commented out.
v Ensure that the information for the other possible databases is commented
out.
Information that is commented out is ignored. By default, all database
configuration information is commented out using the “;” character before the
line and is therefore ignored by IBM Systems Director Server. So, to ensure that
your chosen database is not commented out, remove the “;” character at the
beginning of each applicable line for your database.
3. Enter information in all of the fields required for your chosen database
application. Do not use any quotes in the response file because they cause
errors during database configuration. For a detailed description and examples
of the required attributes, see “Database configuration attributes” on page 43
and select your database type.
4. Save and close the cfgdbcmd.rsp file.
5. Run the cfgdbcmd tool. If you are performing a silent installation of IBM
Systems Director Server on Windows, run the cfgdbcmd tool in
install_root\bin, where install_root is the root directory of your IBM Systems
Director installation. The cfgdbcmd tool uses the cfgdbcmd.rsp response file that
you previously filled in to properly connect IBM Systems Director Server to the
chosen database.
6. Optional: Verify the connection to your database. For instructions, see Verifying
a successful database connection.
Attention: Connectivity problems with the database server affect IBM Systems
Director. For example, if the database server goes offline or becomes
unreachable, IBM Systems Director Server stops responding and hangs.
7. After the cfgdbcmd tool completes, run the smreset command located in the
install_root\bin folder to reinitialize the databases and clear all persistent
data.
Attention: If you do not complete this step, IBM Systems Director Server does
not start correctly.
After the database configuration is complete, return to the point in the installation
instructions for your operating system where you configured the database and
finish installing IBM Systems Director Server 6.3.x. For instructions, see Installing
IBM Systems Director on the management server and select your operating system.

Related tasks:
Related reference:
cfgdbcmd command
smstop command
smreset command

Technote: IBM Systems Director Functions Fail Without Database Connectivity
Database configuration troubleshooting
Verifying a successful database connection:
Test the database connection to ensure that it operates correctly.
If you are having problems connecting to the database or want to verify the
connection during the configuration process, complete the following steps:
1. General: From a command prompt, run the following command:
ping DbmsServerName
Where DbmsServerName is the value of the DbmsServerName attribute in the

cfgdbcmd.rsp response file.
Note: If you cannot ping the DbmsServerName, you must investigate and
resolve the connectivity issues in your network before you can use IBM
Systems Director.
2. For managed IBM DB2, perform the following steps:
a. Run the following command to verify the IBM DB2 connection:
smdbcli connect
smdbcli is located in the install_root\bin directory, where install_root is the

root directory of your IBM Systems Directorr installation.
Alternatively, you can run the following command to verify that the
managed IBM DB2 server is active:
smdb status
b. If the managed IBM DB2 server is down, run the following command to
restart it:
smdb start
smdb is also located in the install_root\bin directory.

3. For IBM DB2, perform the following steps:
a. Use the IBM DB2 command-line tool to make a connection to the database.
For example, run the following command depending on your operating
system:
v Windows:
db2cmd
db2
b. Run connect to MYDB user MYUSERID using ’MYPASSWORD’.
Note: Where MYDB is the IBM Systems Director database, MYUSERID is

the IBM Systems Director database user ID, and MYPASSWORD is the
password for the IBM Systems Director database user ID.
4. Microsoft SQL Server: Use a tool similar to Microsoft SQL Server Management
Studio Express® to connect to the database.
5. For Oracle® Database: To Connect to the Oracle® Database instance locally or
from your Oracle® Database client, complete the following steps.
a. Open a command prompt.
b. Type sqlplus Admin_ID/Admin_PW@DB_name as sysdb.
Notes:
v Admin_ID = the user ID for the Oracle® Database administrator
v Admin_PW = the Oracle® Database administrator password
v DB_Name = the name/SID of the database to which you want to connect
If the connection is successful, you receive general information about the
database and the verification is complete. If it was unsuccessful, you receive
an error. If you receive an error, do one or more of the following actions
and try again:
v Check the tnsnames.ora file and the listener.ora file. You might not
have configured them correctly.
v Restart the listener service on your Oracle® Database Server.
Related reference:
Tips for database user authorities and passwords
Database configuration attributes
Switching the database that IBM Systems Director uses

You can switch the type of database you are currently using with IBM Systems
Director 6.3.x from one database type to another at any time.
When you switch your database to the default managed IBM DB2 database, you
can migrate your database data to the managed IBM DB2 database.
When you switch your database to any type of non-default database, you cannot
migrate your database data.
Related tasks:
Determining your database migration path
Switching the database to a non-default database:
You can switch the type of database you are currently using with IBM Systems
Director 6.3.x to IBM DB2, Microsoft SQL Server, Microsoft SQL Server Express, or
Oracle® 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
For example, you are currently using Oracle® Database with IBM Systems Director
6.3.x and want to use IBM DB2 instead.
If you are switching from managed IBM DB2 to another type of database, managed
IBM DB2 will be uninstalled and the managed IBM DB2 database will be removed.
Restriction: When you switch your database to any type of non-default database,
you cannot migrate your database data.
Before you start, complete the following steps:

v Ensure that the database instance is created and accessible.
v Ensure that all prerequisites for connecting to the database application are
installed and configured. For instructions, see Preparing the database
application.
v Verify that there is no other IBM Systems Director Server configured to use the
database. Do not configure more than one IBM Systems Director Server to use
the same database.
v Ensure that IBM Systems Director Server is stopped before starting this
procedure.
Complete the following steps to switch your database:

1. Open the cfgdbcmd.rsp file with any text editor. The cfgdbcmd.rsp file resides
in the <install_root>\proddata directory, where <install_root> is the root
directory of your IBM Systems Director installation. For example on Windows,
\program files\ibm\director\proddata.
2. In the cfgdbcmd.rsp file, ensure that the configuration information for your
chosen database is commented correctly:
v Ensure that the information for your database is not commented out.
out.
your chosen database is not commented out, remove the “;” character at the
beginning of each applicable line for your database.
3. Enter information in all of the fields required for your chosen database
application. Do not use any quotes in the response file because they cause
errors during database configuration. For a detailed description and examples
of the required attributes, see “Database configuration attributes” on page 43
and select your database type.
4. Save and close the cfgdbcmd.rsp file.
5. Run the cfgdbcmd tool. If you are performing a silent installation of IBM
Systems Director Server on Windows, run the cfgdbcmd tool in
install_root\bin, where install_root is the root directory of your IBM Systems
Director installation. The cfgdbcmd tool uses the cfgdbcmd.rsp response file that
you previously filled in to properly connect IBM Systems Director Server to the
chosen database.
6. Optional: Verify the connection to your database. For instructions, see Verifying
a successful database connection.
Attention: Connectivity problems with the database server affect IBM Systems
Director. For example, if the database server goes offline or becomes
unreachable, IBM Systems Director Server stops responding and hangs.
7. After the cfgdbcmd tool completes, run the smreset command located in the
install_root\bin folder to reinitialize the databases and clear all persistent
data.
Attention: If you do not complete this step, IBM Systems Director Server does
not start correctly.
After you finish switching your database application to a different type, complete
the following steps:
1. Start IBM Systems Director Server:
v On Windows, run the following command from the service control panel:
net start dirserver
2. After you have confirmed that the server is working well, consider removing
the old database that was configured. You can refer to the documentation for
the specific database application for information about how to do that.
Note: If you are switching from managed IBM DB2 to another type of database,
you can skip this step.
Related tasks:

Related reference:
smstop command
smreset command
smstart command
cfgdbcmd command
Switching the database to the managed IBM DB2 database:
You can use the managed IBM DB2 database with IBM Systems Director 6.3.x.
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 the
managed IBM DB2 database. For example, you are currently using Oracle®
Database with IBM Systems Director 6.3.x and want to use the managed IBM DB2
database instead.
When you switch your database to the default managed IBM DB2 database, you
can migrate your database data to the managed IBM DB2 database.

Before you start, ensure that IBM Systems Director Server is stopped.
Complete the following steps to switch your database to the managed IBM DB2
database:
1. Download the installation package or acquire an installation DVD of IBM
Systems Director Server.
Note: Ensure that you use the correct media. If your IBM Systems Director
Server is at a version earlier than 6.3.2, you must use the installation package
or installation DVD that you used to install IBM Systems Director. If your IBM
Systems Director Server is at version 6.3.2.x or later, you must use the IBM
Systems Director 6.3.2 downloadable ISO image.
For instructions, see Acquiring IBM Systems Director Server.
2. Determine whether you want to use the default configuration attributes for the
managed IBM DB2 database or whether you want to specify custom
configuration attributes:
v If you want to use the default configuration attributes, go to Step 7.
v If you want to specify custom configuration attributes, go to Step 3.
To view the default configuration attributes, see “Database configuration
attributes for the managed IBM DB2 database” on page 43.
3. Open the cfgdbcmd.rsp file with any text editor. The cfgdbcmd.rsp file is
located in the install_root\proddata directory, where install_root is the root
directory of your IBM Systems Director Server installation. For example, on
Windows :\program files\ibm\director\prodata.
4. In the cfgdbcmd.rsp file, ensure that the configuration information for the
managed IBM DB2 database is commented correctly:
v Ensure that the information for the managed IBM DB2 database is not
commented out.
out.
the managed IBM DB2 database is not commented out, remove the “;”
character at the beginning of each applicable line for the managed IBM DB2
database.
5. Enter information in all of the fields required for the managed IBM DB2
database. Do not use any quotes in the response file because they cause errors
during database configuration. For a detailed description and examples of the
required attributes, see “Database configuration attributes for the managed IBM
DB2 database” on page 43.
6. Optional: You can save the cfgdbcmd.rsp file to a non-default location.
7. From the installation image that you acquired in Step 1, locate the
installdb2.sh script or the installdb2.bat file:
v Windows 32 bit: installed_filesisdserver\i386\db2
v Windows 64 bit: installed_files\isdserver\x64\db2
Where installed_files is the path to the files that you extracted in Step 1.
8. From a command prompt, run one of the following commands depending on
which file you located in Step 7:
v If you located the installdb2.sh script, run the following command:
installdb2.sh -option -option
v If you located the installdb2.bat file, run the following command:
installdb2.bat -option -option
You can specify the following options:
-rspfile rspfilelocation
rspfilelocation is the path to the location of the cfgdbcmd.rsp file. You
must specify this option if one or more of the following situations are
true:
v You decided to specify custom configuration attributes in step 2 on
page 41. If you do not specify this option, the command uses the
default cfgdbcmd.rsp file instead of the file that you customized.
v You saved the cfgdbcmd.rsp file to a non-default location in Step 6
on page 41.
-noPrompt
Specify this option if you want to install the managed IBM DB2
database in silent mode. If you decided to use the default configuration
attributes in step 2 on page 41, this option automatically uses the
default configuration attributes and does not prompt you for
confirmation.
-dbMigrate value
You can specify the following values for this option:
v true: This value is the default value. The command migrates your
existing database data to the managed IBM DB2 database.
v false: The command does not migrate your existing database data to
the managed IBM DB2 database. If you specify this value, you lose
your data. The command resets your database to an empty database
with no contents.
If you do not specify this option, the command automatically migrates
your existing database data to the managed IBM DB2 database.
-dbIgnorePrereqs value
You can specify the following values for this option:
v true: The command does not verify that the system meets the
prerequisite requirements for the managed IBM DB2 database.
v false: This value is the default value. The command verifies that the
system meets the prerequisite requirements for the managed IBM
DB2 database.
-dbPort port_number
port_number is the port number that you want the managed IBM DB2
database to use. When you specify this option, it overrides the default
port value and it overrides the port value specified in the cfgdbcmd.rsp
file.
After you finish switching your database application to the managed IBM DB2
database, complete the following steps:
1. Start IBM Systems Director Server:
v On Windows, run the following command from the service control panel:
net start dirserver
2. After you have confirmed that the server is working well, consider removing
the old database that was configured. You can refer to the documentation for
the specific database application for information about how to do that.

Related concepts:
Related tasks:

Related reference:
smstop command
smstart command

You can learn about the database configuration attributes that must be set in the
cfgdbcmd.rsp response file in order to configure the database.
Related tasks:
Switching the database

Related reference:
Database configuration attributes for the managed IBM DB2 database:
There are database configuration attributes that must be set in the cfgdbcmd.rsp
response file in order to switch your database type to the managed IBM DB2
database. This information applies only to the managed IBM DB2 database that is
provided with IBM Systems Director 6.3 and not to external IBM DB2 databases.
The following table lists the database configuration attributes for the managed IBM
DB2 database, a description of each attribute, and an example of each attribute.
Selected database application DbmsApplication Managed DB2
Host name or IP address of the IBM DB2 DbmsServerName localhost
server instance
Location for the managed IBM DB2 DbmsDatabaseHome Default value:
instance. v Windows: C:\DIRINST1
For Windows, you must specify a drive Custom value:
letter. Examples:
v Windows: C
TCP/IP service port number for the DbmsTcpIpListenerPort Default value: 50010
managed IBM DB2 server instance
Custom value: You can specify a port that
is available and not in use.
Password of the database user account DbmsPassword Default value: Leave this attribute blank.
For detailed information about passwords, When you leave this attribute blank, IBM
see “Tips for user authorities and Systems Director automatically generates a
passwords for the managed IBM DB2 password for you.
database” on page 52.
Custom value:
Example: mypwd
Example cfgdbcmd.rsp file for Windows

DbmsApplication = Managed DB2
DbmsTcpIpListenerPort = 50010
DbmsServerName = localhost
DbmsDatabaseHome = C
DbmsPassword = mypwd
Related concepts:
Related tasks:
Switching to the managed IBM DB2 database
Database configuration attributes for IBM DB2:
response file in order to configure the IBM DB2 database. This information applies
only to external IBM DB2 databases and not to the managed IBM DB2 database
that is provided with IBM Systems Director 6.3.
The following table lists the database configuration attributes for IBM DB2, a
description of each attribute, and an example of each attribute.

Selected database application DbmsApplication DB2
Notes:
select.
Host name or IP address of the IBM DB2 DbmsServerName Custom value:
server instance Examples:
Note: A IBM DB2 database must always be v host1.domain.com
considered remote, even if IBM Systems
v 127.0.0.1
Director Server and IBM DB2 server
instances reside on the same system. v localhost
Therefore, a host name or IP address is
required here. Use a host name or localhost instead of
database.
directory.
Notes: Example: DIRDB01
v If the database does not exist, then it is
created later on by the cfgdbcmd task. If
the database does exist, then it is used.
v Use a database name and instance name
that do not exceed 8 characters.
Local installation folder in which the IBM DbmsDatabaseAppHome Custom value:
DB2 client instance resides Examples:
v Windows: C:\Program Files\IBM\SQLLIB
For Windows systems:
v This value must be the fully qualified Do not include double quotation marks
path name. around the path name.
v This value is the location of the SQLLIB
directory. For example, a typical
Windows installation specifies this value
as C:\Program Files\IBM\SQLLIB. You
can determine the
DbmsDatabaseAppHome value by
opening an IBM DB2 command window
and specifying DB2SET DB2PATH.
TCP/IP service port number for the IBM DbmsTcpIpListenerPort Custom value:
DB2 server instance Example: 50000
On Windows, you can determine the

DbmsTcpIpListenerPort value by opening
an IBM DB2 command window and
specifying db2 get dbm config . Look for
the value associated with SVCENAME. If
SVCENAME is a number, that is the port
number. If it is a name (such as db2c_DB2)
you must find the name in the services file,
which is typically located at
C:\WINDOWS\system32\drivers\etc\ on
Windows and at /etc on Unix. Inside that
services file, find the SVCENAME value
that matches the one returned from the db2
get dbm config command. It includes a
port number. For example, it might look
like db2c_DB2 50000/tcp, which indicates a
port number of 50000.
User ID of the database user account that DbmsUserId Custom value:
is used to connect to the database Example: myuserid
Notes:
v Database tables are created under the
schema for this user ID.
v If you do not use the database
administrator user ID for the runtime
connection, provide a second user with
access to the information collection
panel.
v For detailed information about user IDs,
passwords for IBM DB2” on page 53.
Example: mypwd
passwords for IBM DB2” on page 53.

DbmsApplication = DB2
DbmsServerName = 10.9.1.2
DbmsDatabaseName = dirdb
DbmsUserId = myuserid
DbmsDatabaseAppHome = C:\Program Files\IBM\SQLLIB
Related tasks:
Enabling Dynamic IP support
Database configuration attributes for Microsoft SQL Server and Microsoft SQL
Server Express:
response file in order to configure the Microsoft SQL Server database and the
Microsoft SQL Server Express database.
The following table lists the database configuration attributes for Microsoft SQL
Server and Microsoft SQL Server Express, a description of each attribute, and an
example of each attribute.
Selected database application DbmsApplication SQLServer
Notes:
select.
v 10.9.1.1
Optional: You can include the
DbmsInstanceName with the v MyServer
DbmsServerName in the form of v localhost
DbmsServerName\DbmsInstanceName.
database.
directory.
Examples:
v DIRDB
v MyDatabase
Instance name of the database that is DbmsInstanceName Custom value:
applicable only if a non-default instance is Examples:
used v MyInstance
v If you have only one instance of
Microsoft SQL Server or Microsoft SQL
Server Express, you do not need to set
this attribute.
v If you specified the instance name with
the DbmsServerName attribute, you can
leave this attribute blank.

the database server instance or admin Examples:
client instance on the IBM Systems Director v C:\sqljdbc2\sqljdbc_4.0\enu
Server system
v C:\Program Files\Microsoft SQL Server
Note: This value is the location of the
JDBC Driver 4.0\sqljdbc_4.0\enu
JDBC driver, sqljdbc4.jar. For example, a
typical Windows installation specifies this Do not include double quotation marks
value as C:\PROGRA~1\MICROS~4\ around the path name.
sqljdbc_4.0\enu or C:\Downloads\SQLJDBC\
extract\sqljdbc_4.0\enu.
Example: 1433
Whether IBM Systems Director is to DbmsIntegratedSecurity __ v true
connect to the Microsoft SQL Server __ v false
database by using Windows authentication
Examples:
(“true”) or Microsoft SQL Server
authentication (“false”) v Microsoft SQL Server authentication:
Notes: false
v For IBM Systems Director version 6.2.0 v Windows authentication: true
and previous versions, the Windows
authentication option is supported only
when Microsoft SQL Server is installed
on the same system as IBM Systems
Director.
v If DbmsIntegratedSecurity is set to
“false”, then Microsoft SQL Server must
be configured with mixed mode
authentication.
v For detailed information about user IDs
and passwords, see “Tips for user
authorities and passwords for Microsoft
SQL Server and Microsoft SQL Server
Express” on page 55.
Notes: Example: myuserid
v It is recommended that you choose a
different database user ID than the
database administrator user ID. The
database user does not need as much
authority to the database as the database
administrator user.
v For detailed information about user IDs,
passwords for Microsoft SQL Server and
Microsoft SQL Server Express” on page
55.
Example: mypwd
passwords for Microsoft SQL Server and
Microsoft SQL Server Express” on page 55.
Example cfgdbcmd.rsp file for Microsoft SQL Server authentication
DbmsApplication = SQLServer
DbmsDatabaseName = DIRDB
DbmsInstanceName = MyInstance
DbmsDatabaseAppHome = C:\sqljdbc2\sqljdbc_4.0\enu
DbmsIntegratedSecurity = false
Example cfgdbcmd.rsp file forWindows authentication

DbmsServerName = MyServer\MyInstance
DbmsDatabaseName = DIRDB
DbmsUserId =
DbmsPassword =
DbmsDatabaseAppHome = C:\sqljdbc2\sqljdbc_4.0\enu
DbmsIntegratedSecurity = true
Example cfgdbcmd.rsp file forWindows authentication for remote Microsoft SQL

Server
DbmsServerName = MyServer
DbmsDatabaseName = MyDatabase
DbmsInstanceName = MyInstance
DbmsUserId =
DbmsPassword =
DbmsDatabaseAppHome = C:\Program Files\Microsoft SQL Server JDBC Driver 4.0 /
\sqljdbc_4.0\enu
DbmsIntegratedSecurity = true
Related tasks:
Database configuration attributes for Oracle® Database:
response file in order to configure the Oracle® Database.
The following table lists the database configuration attributes for Oracle® Database,
a description of each attribute, and an example of each attribute.

Selected database application DbmsApplication Oracle
Notes:
select.
v 10.0.0.72
v MyServer
v localhost

database.
directory.
Example: mydatabase
the database server instance or admin Example: c:\oracle\product\10.2.0\
client instance on the IBM Systems Director client_1
Server system
Example: 1521
Example: myuserid
For detailed information about user IDs,
56.
Example: mypwd
56.

DbmsApplication = Oracle
DbmsDatabaseName = mydatabase
DbmsDatabaseAppHome = c:\oracle\product\10.2.0\client_1
Related tasks:

Use these tips and techniques to configure, manage, and troubleshoot user
authorities and passwords for your database application.
Related tasks:

Related reference:
Tips for user authorities and passwords for the managed IBM DB2 database:
authorities and passwords for the managed IBM DB2 database.

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:
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:
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:
! % ^ & ( ) | " ’ ? , < >
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.

Related tasks:

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:
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
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
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.
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:

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:

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.

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.
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
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.
specify a value.
Related tasks:

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.

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:
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.
Related tasks:
“Enabling Dynamic IP support”
“Changing IBM Systems Director server health settings” on page 66
Related reference:
smstart command
smstatus command
smstop command

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

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. Change the IP address of the system on which IBM Systems Director Server is
installed:
v If the database server is not the managed IBM DB2 database, complete the
following steps:
a. Determine if there are any changes required so that your database server
works with the IP address change. See the documentation provided by
your database application for information and instructions.
b. Do the changes that you identified in the previous step and restart your
database server.
c. View the lwi/conf/overrides/database.properties file and determine if
it contains the previous IP address. If so, for each file in the
lwi/conf/overrides/ directory that ends in database.properties,
manually update the file with the changed IP address.
3. 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.
4. 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:
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:
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™ in Service and Support Manager to
securely transmit serviceable hardware problems and associated support
files, inventory, and Performance Management data to support. For
instructions, see Activating Electronic Service Agent.

v Activate the free trial period for IBM Systems Director VMControl. For
instructions, see Activating IBM Systems Director VMControl.
4. Install and configure all other IBM Systems Director plug-ins that you intend to
use.
Table 12. Configuration tasks and information resources for IBM Systems Director plug-ins
Plug-in Tasks Information resources
Base plug-ins
IBM System Storage® 1. Configure SMI-S 1. Managing SMI-S
management providers. providers
2. Configure external 2. Installing and configuring
storage applications. external storage
applications
Remote access manager 1. Configure Virtual 1. Virtual Network
Network Computing Computing
(VNC). 2. Configuring Microsoft
2. Configure Remote Windows Remote
Desktop. Desktop Connection
Update manager Optional: Complete the Configuring update manager
Getting Started wizard and
change update settings.
Advanced plug-ins
IBM Systems Director Install the plug-in. Installing and uninstalling
Network Control IBM Systems Director
Network Control
IBM Systems Director Install the plug-in. Installing Storage Control
Storage Control 4.2.3
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.
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.
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.
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 65
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 13. Settings with default values that can be changed
Property Input value Default value
System properties
com.ibm.usmi.kernel. The percentage that triggers 90%
localsystem. the warning.
cpuWarningThreshold
com.ibm.usmi.kernel. The number of milliseconds 1 800 000 milliseconds (30
localsystem. the CPU must be at the minutes)
cpuTimeForWarning threshold level to trigger a
warning.
By default, this warning is

triggered after the CPU is
at 90% for 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. The amount of free space 1 073 741 824 bytes (1 GB)
localsystem. before triggering the
diskSpaceWarning warning.
com.ibm.usmi.kernel. The amount of free space 500 MB
localsystem. before triggering a critical
diskSpaceCrit event.
server free space available is less than 1 GB.
Memory usage properties
com.ibm.usmi.kernel. The percentage of memory 90%
localsystem. usage that triggers the
memoryWarningPercentage warning.
com.ibm.usmi.kernel. The amount of time, in 3 600 000 milliseconds (1

localsystem. milliseconds, that memory hour)
memoryWarningTime use must be sustained to
trigger the warning.

triggered after the memory
usage is at 90% for 1 hour.
server memory usage is at 90% for 1 hour.
Managed endpoint (MEP)
count properties
com.ibm.usmi.maxSystems The maximum number of 10 000
MEPs supported.
Table 13. Settings with default values that can be changed (continued)
Property Input value Default value
com.ibm.usmi.maxSystems.derby The maximum number of 1 000
MEPs supported when the
Apache Derby database is
used.
Example: By default the Systems Director server supports 1000
MEPs when using the Apache Derby database.
Page space properties
com.ibm.usmi.kernel. The page space usage 80
localsystem. percentage that triggers the
psWarningPercentage warning.
com.ibm.usmi.kernel. The time in milliseconds 1 200 000 milliseconds (20
localsystem. that page space usage must minutes)
psWarningTime be sustained to trigger the
warning.

triggered after the page
space usage is at 80% for 20
minutes.
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:
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 14. Example locations of log files for IBM Systems Director 6.3.x
AIX IBM i Linux Windows
IBM Systems Director Server installation logs:

Table 14. Example locations of log files for IBM Systems Director 6.3.x (continued)
v /var/log/dirinst.log Not applicable v /var/log/dirinst.log v C:\Windows\

v /var/log/director/* v /opt/ibm/director/log/ dirserverinst_time.log
v /opt/ibm/director/log/ *.log v C:\Windows\
recovery.txt v /opt/ibm/director/log/ dirserversetup.log
recovery.txt 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:
/var/log/dirinst.log v /tmp/director/ /var/log/dirinst.log v C:\Windows\
installAgent.log agent_install.log
v /tmp/director/ v C:\Windows\CasInst.log
installDirAgent.log v C:\Windows\certutil.log
v /www/cas/lwi/runtime/ v C:\Windows\
agent/logs/install diragentinst_time.log
All of these can be found in v C:\Windows\
the dirmedic results. diragentsetup.log
v C:\Windows\
tivguidinst.log
Platform Agent installation logs:
/var/log/dirinst.log Not applicable /var/opt/ibm/platform/ C:\Windows\
log/install.log 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/ v C:\Windows\
log/uninstall.log platuninst_time.log
v C:\Windows\
sysdirremoval.log
Migration logs:
/var/tmp/ Not applicable /var/tmp/ %APPDATA%\ISD62x\logs
director_save_630/logs director_save_630/logs
Configuration logs:
/var/log/director/* Not applicable /opt/ibm/director/log/ C:\Program
*.log Files\IBM\Director\log\
*.log
Default managed IBM DB2 database logs:
Table 14. Example locations of log files for IBM Systems Director 6.3.x (continued)
v /tmp/installdb2.log Not applicable v /tmp/installdb2.log C:\Windows\installdb2.log

v /tmp/db2setup.log v /tmp/db2setup.log
v Directory structure for v Directory structure for
your installed IBM DB2 your installed IBM DB2
database product (Linux) database product (Linux)
2. Perform the installation procedure again. For instructions, see “Installing IBM
Systems Director on the management server” on page 27 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 34.
Installation and migration troubleshooting
Managed IBM DB2 installation fails

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®
Manageability Access Point Agent.
IBM Systems Director Server must be updated to 6.3.2 before, or at the same time
as, the agents that are installed on the management server are updated to 6.3.2. If
you attempt to update a local agent to 6.3.2 before updating IBM Systems Director
Server, then the IBM Systems Director Server update to 6.3.2 fails.
Use the following flowchart as a guide through the installation process for agents.
Note: A managed system might have more than one IP address (for example,
when the system contains more than one network interface card). When a
managed resource has multiple IP addresses, specify which IP address Systems
Director uses to manage the resource. To specify the IP address to use, you specify
that the management server ignore (or exclude) the other IP addresses associated
with the resource. For more information, see “Excluding IP addresses.”

Note: For more information about using the Web interface, see Publications and
related information to access the Systems Management guide.
Related tasks:
Choosing the level of agent capabilities to deploy on managed systems

Installing VMControl agents and subagents

Related reference:
Systems Director Agent Deployment Cookbook
Running the Pre-Installation Utility on an agent (Windows)

Use these instructions to run the IBM Systems Director Pre-Installation Utility
(PIU) on Windows.
You can obtain or run the Pre-Installation Utility from two locations.
Table 15. Obtaining the Pre-Installation Utility
Location Action
IBM Systems Director 6.3.2 DVD If you do not already have the DVD, you
can burn the image onto DVD from the IBM
Systems Director Downloads website.
SysDir_PreInstUtil_6_3_2_Windows.zip Download the Pre-Installation Utility from
the IBM Systems Director Downloads
website.
Note: The downloads website always
contains the most recent version.
1. To start the IBM Systems Director Pre-Installation Utility, choose the applicable
method:
v DVD
v Pre-Installation Utility download
Complete the following steps.
v DVD
c. If the IBM Systems Director Welcome window does not automatically
open, then complete the following steps, as applicable:
2) To change to the directory where the Pre-Installation Utility script is
located, type the following command in the Open field and press
Enter:
e:\server\{i386 or x64}\checkds\

where e is the DVD-ROM drive letter on your system. If you
downloaded the utility, use the directory in which the Pre-Installation
Utility is located.
3) To start the utility, type the following command and press Enter:
checkds.bat -p [platformagent|commonagent]
For example:
checkds.bat -p commonagent
Note: If you do not specify the -p attribute, the tool is run for the
server. So, you must specify -p and designate whether you are
running the tool to prepare for the common agent or platform agent
installation.
The IBM Systems Director Pre-Installation Utility starts.
4) See Step 2.
v Pre-Installation Utility download
a. Extract the contents of the Pre-Installation Utility package, type the
following command, and press Enter:
unzip
b. To change to the directory where the Pre-Installation Utility script is
located, type the following command (as applicable) and press Enter:
cd checkds
c. To start the utility, type the following command and press Enter:
checkds.bat -p [platformagent|commonagent]
For example:
checkds.bat -p commonagent
Note: If you do not specify the -p attribute, the tool is run for the server.
So, you must specify -p and designate whether you are running the tool
to prepare for the common agent or platform agent installation.
The IBM Systems Director Pre-Installation Utility starts.
2. Reports are generated and results are displayed in the command window or
the default browser. Refer to the e:\checkds\readme.txt file for more
information about checkds.bat options, the reports that are generated, and
return codes. The checkds.bat -? command also displays supported syntax.
Related tasks:
Preparing to upgrade and migrate

Related reference:
Installing Common Agent

Prepare your systems and environment for installing Common Agent. Then, use
the Agent Installation wizard, or alternatively, use the manual instructions, to
install Common Agent.
Important:
v Installation of IBM Systems Director installs IBM Systems Director Server,
Common Agent, and Platform Agent all together as a bundle. Therefore, it is not
Chapter 2. Installing agents 73

necessary to separately install Common Agent or Platform Agent on the
management server after installing IBM Systems Director Server.
Related tasks:
Preparing for a Common Agent managed system

Before installing Common Agent on a managed system, ensure that the
requirements applicable to your system have been met.
Complete the following steps on each system to be managed with Common Agent:
On all managed systems that use the ssh protocol to communicate with IBM
Systems Director Server, ensure that the PasswordAuthentication value in
/etc/ssh/sshd_config is set to yes. So, the corresponding line in the sshd_config
file will appear as follows:
PasswordAuthentication yes
Note: You must restart the ssh server for any changes made to sshd_config to take
effect.
Related reference:
Hardware requirements for systems running Common Agent or Platform

Agent
Obtaining licenses for Common Agent

IBM Systems Director includes licenses for up to 20 installations of Common Agent
on non-IBM x86 systems. To install Common Agent on additional non-IBM x86
systems, you must obtain a license from IBM.
1. Determine which non-IBM x86 systems require Common Agent licenses.
2. Obtain licenses for each installation of Common Agent on non-IBM x86 systems
from the software ordering web page at http://www.ibm.com/us/en/. From
the ibm.com web page, complete the following steps:
a. Click Products.
b. Under Systems and servers, select System x (xSeries).
c. Under Options and upgrades, select All options and upgrades.
d. Under More options and upgrades, select Software.
Related concepts:
License information
Preparing to install Common Agent on Windows

Before installing Common Agent on a managed system running Windows, make
sure that your system meets all the applicable requirements.
instructions, see “Running the Pre-Installation Utility on an agent (Windows)”
on page 72.

v Ensure that your system meets the hardware and software requirements for
installation, as described in “Hardware and software requirements”.
v If there is an operating system update in progress, ensure the process is
v Ensure that any agentless managed systems are prepared for discovery, as
described in “Preparing agentless managed systems”.
v If you want to use IBM Systems Director Server on System x for heterogeneous
server management, you can install Common Agent or Platform Agent on the
platforms you want to manage. You can obtain Common Agent and Platform
Agent for the supported operating systems from the IBM Systems Director Web
site at www.ibm.com/systems/software/director/downloads/agents.html.
v The IBM Systems Director for x86 DVD no longer includes OpenSSH for
Windows. If a Platform Agent managed system or Common Agent managed
system does not have a Secure Shell (SSH) package installed, IBM Systems
Director Server cannot communicate securely with the managed system. To
secure communication, install OpenSSH on the managed system. Download
OpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ and
update the managed system with SSH.
Related tasks:
Installing agents using the Agent Installation Wizard

Installing Common Agent on Windows
Related reference:
IBM Systems Director Web page
OpenSSH for Windows


You can use the Agent Installation Wizard to install agent packages on managed
systems.
IBM Systems Director Server requires a number of agent packages that can be
deployed to managed systems using the Agent Installation Wizard.The imported
agent packages are located in the dynamic group “Agent Package Groups” and can
be accessed by clicking Release Management > Agents in the navigation area. You
use the Agent Installation Wizard to select one of these agent packages to install
and one or more systems on which to install the agent package. Then, the wizard
creates an agent installation job that can run immediately or at a scheduled time.
Important: Ensure that the following requirements are met to enable use of the
Agent Installation Wizard to install and update agents:

v The root user account was used to initially request access to the managed
system.
v IBM Systems Director Server on non-Windows systems has SSH, and a
successful SSH connection exists in both directions between the server and the
agent.
v IBM Systems Director Server on Windows systems has DCOM, and a successful
DCOM connection exists in both directions between the server and the agent.
Complete the following steps to import the agent packages:

1. Download the remote agent packages from http://www.ibm.com/systems/
software/director/downloads/agents.html. Ensure that you choose packages
from the “Remote Deployment using Agent Installation wizard” section.
2. Copy the packages to a location of your choice on the IBM Systems Director
Server system.
3. Import the packages with the Agent Installation Wizard.
4. Make any required changes to the diragent.rsp and or platform.rsp response
files. See the topic for your operating system under “Installing Common Agent
manually” or “Installing Platform Agent manually” for instructions about how
to change the response files.
Complete the following steps to install agents using the Agent Installation Wizard:
1. Start the Agent Installation Wizard. You can start the wizard in multiple ways:
v From the Home page, click Additional Setup. Then, click Install agents on
systems > Deploy Agents.
v Right-click an agent package or a managed system and select Release
Management > Install Agent.
2. If the Agent Installation Wizard Welcome page appears, click Next.
3. In the Agent Installation Wizard Agents page, complete the following steps:
a. Select the agent or subagent package that you want to install in the
Available list.
Note: A subagent plugs in to a base agent and provides additional

capabilities to support IBM Systems Director plug-ins such as IBM Systems
Director VMControl. This documentation uses the collective term “agents”
to refer to both agents and subagents.
b. Click Add. The selected agent package is displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, the
Selected list might already contain one or more agent packages.
v The Agent Installation Wizard can install only one agent package at a
time. If more than one agent package is displayed in the Selected list,
you will not be able to advance to the Systems page.
c. Click Next.
4. In the Agent Installation Wizard Systems page, complete the following steps:
a. Select the managed systems on which you want to install the agent package
in the Available list.
b. Click Add. The selected systems are displayed in the Selected list.
Notes:

Selected list might already contain one or more systems.
v Depending on the agent package that you are installing, some selected
systems are potentially not valid targets for installation. The wizard
checks the selected systems for some or all of the following criteria to
ensure that the systems are valid targets before allowing you to continue:
– Operating system family
– Operating system version
– Operating system distribution
– Operating system name
– Server architecture
c. Click Next.
5. In the Agent Installation Wizard Summary page, review the Selected Agents
and Selected Systems lists to ensure that they are correct.
v If the selections are not correct, click Back and make the necessary changes.
v If the selections are correct, click Finish.
After you click Finish, the Run - Install Agent window opens.
6. In the Run - Install Agent window, click the Schedule tab. On this page, you
can choose to run the job immediately or schedule the job to run at a later time.
a. A job name is required and the Name field provides a unique default name.
To change the default name, type a job name in the field.
b. To run the job immediately, click Run Now and go to step 7. Otherwise,
click Schedule.
c. In the Schedule list, select how frequently you want the job to run. The
default setting is Once. Other values are Hourly, Daily, Weekly, Monthly,
Yearly, or Custom. Also, you can specify whether to run the job on the
weekend.
d. Select the date and time to run the job for the first time.
e. Select the time range for the job to repeat.
7. Click the Notification tab. On this page you can customize a notification that is
sent by e-mail.
a. Select from the available criteria to customize when the mail notification is
sent. You can specify that the mail be sent when one of the following
criteria is met:
v When the job begins.
v When the job completes successfully.
v When the job fails. You can further customize this criterion by setting
either the percentage of target systems on which the job had errors or the
number of systems on which the job had errors. Therefore, if the job runs
on five systems, the job has errors on two systems, and you set the
criterion threshold to 50%, the notification is not sent.
v When the job receives any error.
b. Type your mail address, mail server, and mail server port.
Tip: You can provide only one mail address.

8. Click the Options tab. On this page you can select additional options for the
job behavior.
a. Select whether you want the job to run according to your management
server's time or the target system's time.

Tip: Make sure that you know the time and time zone to which the
respective systems' clocks are set.
b. Select whether you want the job to fail if a system is offline or if you want
the job to run when the system is online again.
9. Click OK to save the job.
Click Cancel to exit from the Launch Job window without saving the job.
If the job is created successfully, a message is displayed on the page from
which you started the Scheduler. If the job creation fails, a message is displayed
in the Launch Job window so that you can correct the job.
The job created by the Agent Installation Wizard will transfer the agent
self-extracting script and the agent response file into the following directory,
which depends on your version and agent level, on the target system:
6.x Common Agent
/tmp/commonagent_tmp
6.x Platform Agent
/tmp/platformagent_temp
5.x Common Agent
install_root/SwDistPk
After the files are copied, the installation file sets are extracted into the /tmp
directory and installed. The files are then removed after a successful
installation. You need to ensure that there is sufficient space on the target
system to copy the self-extracting script and extract the file sets. Refer to the
space requirements as specified in “Hardware requirements for systems
running Common Agent or Platform Agent”.
If the agent deployment completes with errors, check the log file for your target
operating system for a possible root cause:
v Windows: %WINDIR%/diragentinst_timestamp.log or %WINDIR%/
platint_timestamp.log
Note: For more information about error log files, see “Information to provide
to the IBM Technical Support Center”.
You can view the status of the agent installation job by clicking Task Management
> Active and Scheduled Jobs.
If you installed Platform Agent on Linux, enable SNMP Access and Trap
Forwarding by installing and configuring Net-SNMP. For instructions and
information, see http://www.net-snmp.org/.
Installing Common Agent manually

You can use these manual instructions to install Common Agent on a managed
system. These manual instructions provide an alternative method of installation to
using the Agent Installation Wizard.
Important:

Related tasks:
Preparing a Common Agent managed system
Installing Common Agent on Windows

After preparing your system, you can install Common Agent on a Windows
system by downloading the installation files from the IBM Systems Director
support Web site or by using the DVD. You can then perform a standard
Installing Common Agent on Windows using the installation wizard:
After preparing your Windows system, you can use the installation wizard to
install Common Agent.
Important:
Common Agent 6.3.2 and Platform Agent 6.3.2 are primarily intended to support
new hardware and operating systems. You can install them for the first time on
any system that has the supported operating system and hardware, or you can
install them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exception
is that the Platform Agent 6.3 installation does not upgrade agents that have the
IBM Systems Director 5.20.x on systems with an RSA service processor. In this
situation, you have the following options:
v To maintain full support of agents on these systems, continue to use Common
Agent 6.1 for Windows, Common Agent 6.1.2.3 for Linux for System x, or IBM
Director Core Services 5.20.31 or 5.20.32.
v To use Common Agent 6.3.2 with reduced support on these systems, first
uninstall Common Agent 6.1 and then install Common Agent 6.3.2.
v To use Platform Agent 6.3.2 with reduced support on these systems, first
uninstall IBM Director Core Services 5.20.31 or 5.20.32 and then install Platform
Agent 6.3.2.
Depending on the version of Common Agent that you are installing, you can
install Common Agent on Windows from either installation media or from a
downloaded installation package.
Table 16. Installation options for Common Agent on Windows
Installation method Title or file name
DVD media IBM Systems Director for x86, V6.3.2 DVD
Note: To obtain an image of the IBM
Systems Director for x86, V6.3.2 DVD,
download the
SysDir6_3_2_DVD_Windows_x86-64.iso or
SysDir6_3_2_DVD_Windows.iso file.

Table 16. Installation options for Common Agent on Windows (continued)
Downloaded installation package v
SysDir6_3_2_Common_Agent_Windows.zip
(agent package for manual installation)
v
SysDir6_3_2_Common_Agent_Windows.jar
(agent package for Agent Installation
Wizard installation)
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installed on
the system, it is installed during the Common Agent 6.3.2 installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of Common Agent 6.3.2 without specifying that MSI was installed. Unless you
install using the response file and set the RebootIfRequired parameter to N, you are
prompted to restart whether or not the Common Agent 6.3.2 installation is
completed successfully.
To install Common Agent on Windows using the installation wizard, log in with
an administrator account and complete the following steps:
1. Start the installation from the Common Agent installation source:
Downloaded installation files: To start the installation from a Web download,
a. Download the installation package from the IBM Systems Director
Downloads Web Site at (http://www-03.ibm.com/systems/software/
director/downloads/agents.html).
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Click Start > Run.
\installation_directory\IBMSystemsDirectorAgentSetup.exe
where installation_directory is the path to the extracted installation

files. The Welcome to the installation wizard for IBM Systems Director
Common Agent window opens.
DVD media: To start the installation from the DVD, complete the following
steps:
2) Click IBM Systems Director Agents.
3) Click Install IBM Systems Director Common Agent.
4) Go to the next step.
If the IBM Systems DirectorWelcome window does not automatically open,
then complete the following steps:
2) In the Open field, type the following commands and press Enter:
v For 64-bit:

e:\server\x64\bin>miniunz.exe
e:\agent\SysDir6_3_2_Common_Agent_Windows.jar -d c:\632CA\
v For 32-bit:
e:\server\i386\bin>miniunz.exe
e:\agent\SysDir6_3_2_Common_Agent_Windows.jar -d c:\632CA\
where e is the drive letter of the drive and c:\632CA\ is an existing
folder where the installation files are to be extracted.
3) From the directory where you saved the installation files, open the
repository folder and run IBMSystemsDirectorAgentSetup.exe
The installation program starts.
Accessibility note: Screen readers might not process the IBM Systems
Director Welcome window correctly. To start the installation wizard for
Common Agent using the keyboard, complete the following steps:
a. Close the IBM Systems Director Welcome window.
b. Open Windows Explorer.
c. Browse to the directory where you extracted the installation files.
d. Run the IBMSystemsDirectorAgentSetup.exe program. The installation
wizard starts, and the Common Agent Welcome window opens.
4. To select an alternative location for the creation of the installation, click
Change and select another directory.
5. Click Next. The Common Agent configuration page is displayed.
6. Specify the common agent port numbers for the common agent that is
installed with the server.
7. Click Next. The Registering Common Agent Services (CAS) page is displayed.
8. If you want the agent that you are installing to register with an agent
manager that already exists in your environment, select Check only if you
want to register CAS Agent with agent manager and enter in the information
for that existing agent manager:
Agent Manager Hostname or IP Address
The host name or IP address of the existing agent manager. If the
agent is installed in a network address translation environment, set
this parameter to ensure that the agent has the correct IP address to
contact the agent manager.
Agent Manager Registration Password
The password associated with the existing agent manager.
9. Click Next. The Ready to Install the Program window is displayed.
10. Click Install. Various windows that display the status of the installation are
displayed. When the installation is complete, the Installation complete
window is displayed.
11. Click Finish.

When the installation has completed, the resource will be set up as a manageable
resource.
To ensure full functionality of your new Common Agent instance, discover it with
Related tasks:
Windows
Importing agent packages
Upgrading and migrating agents
Restarting Common Agent

Related reference:

Performing an unattended installation of Common Agent on Windows:
After preparing your Windows system, you can use a response file to perform an
unattended installation of Common Agent. The response file that you create can be
employed on supported systems in your environment to install Common Agent.
Important:

Agent 6.3.2.
Depending on the version of Common Agent that you are installing, you can
install Common Agent on Windows from either installation media or from a
downloaded installation package.
Table 17. Installation options for Common Agent on Windows
Note: To obtain an image of the IBM
Systems Director for x86, V6.3.2 DVD,
download the
Downloaded installation package v
SysDir6_3_2_Common_Agent_Windows.zip
v
SysDir6_3_2_Common_Agent_Windows.jar
(agent package for Agent Installation
Wizard installation)
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installed on
the system, it is installed during the Common Agent 6.3.2 installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of Common Agent 6.3.2 without specifying that MSI was installed. Unless you
install using the response file and set the RebootIfRequired parameter to N, you are
prompted to restart whether or not the Common Agent 6.3.2 installation is
completed successfully.
To use a response file to install Common Agent on Windows, log in with an

administrator account and complete the following steps:
1. Start the installation from the installation source:
Downloads Web Site at http://www-03.ibm.com/systems/software/
director/downloads/agents.html.
c. Copy the diragent.rsp response file to a new location. This file is in the
\directory\FILES (5.20.31) or the \directory (6.1.x or later) directory, where
directory is the local directory into which you extracted the files.
steps:
c. If the IBM Systems DirectorWelcome window does not automatically open,
then complete the following steps to extract the jar file:

v For 64-bit:
e:\server\x64\bin>miniunz.exe /
e:\agent\SysDir6_3_2_Common_Agent_Windows.jar /
-d c:\632CA\
v For 32-bit:
e:\server\i386\bin>miniunz.exe /
e:\agent\SysDir6_3_2_Common_Agent_Windows.jar /
-d c:\632CA\
where e is the drive letter of the drive and c:\632CA\ is an existing
d. Copy the diragent.rsp response file to a local directory. This file is in the
repository folder within the directory where you extracted the jar file.
2. Open the copy of the diragent.rsp file, which follows the Windows INI file
format, in an ASCII text editor.
the diragent.rsp file to myresponsefile.rsp. This file is fully commented.
The following parameters are used in the diragent.rsp file to register the
Common Agent services with an agent manager. These parameters are optional,
but, if one is specified, then both must be specified.
CASInstall.AgentManagerHostname
The host name or IP address for the agent manager. If the agent is
installed in a network address translation environment, set this
parameter to ensure that the agent has the correct IP address to contact
the agent manager.
CASInstall.RegistrationPassword
The password for registering with the agent manager.
The following parameters are used to set the ports that the common agent
services will use. A valid number for each port is a number that is greater than
1024 and lesser than 65535. The values listed are the default values for each
parameter.
v CASInstall.AgentPort=9510
v CASInstall.NostopPort1=9514
v CASInstall.NonstopPort2=9515
4. Open a command prompt and change to the directory that contains the
Common Agent installation file. This file is in the \respository directory.
5. From the command prompt, type the following command and press Enter:
IBMSystemsDirectorAgentSetup.exe /s /a installationtype \
rsp="responsefile" option
installationtype
v unattended shows the progress of the installation but does not
require any user input.
v silent suppresses all output to the screen during installation.
responsefile
messages.

IBMSystemsDirectorAgentSetup.exe /s /a silent
rsp="c:\myfolder\myresponsefile.rsp"
This example performs a silent installation of Common Agent on Windows

using the myresponsefile.rsp response file.
Notes:
whether the IBM Systems Director Server installation completes successfully.
To ensure full functionality of your new Common Agent instance, discover it with

Related tasks:
Windows
Upgrading and migrating agents
Restarting Common Agent

Related reference:

Installing Platform Agent

Prepare your systems and environment for installing Platform Agent. Then, use the
Agent Installation wizard, or alternatively, use the manual instructions, to install
Platform Agent.
Important:
Common Agent (when applicable), and Platform Agent all together. Therefore, it
is not necessary to separately install Common Agent or Platform Agent on the
management server after installing IBM Systems Director Server. In most cases,
any IBM Systems Director tasks requiring Common Agent or Platform Agent
will be performed for systems with IBM Systems Director Server installed.
v Ensure that the system clocks on systems that contain IBM Systems Director
Server and Platform Agent remain synchronized.
v If you have BMC, IMM, or IMM2 service processors, use Platform Agent 6.1.1 or
later to help ensure full functionality and support.
v If you have RSA service processors, use IBM Director Core Services 5.20.x to
help ensure full functionality and support. If you do decide to use Platform
Agent 6.3.2, you must first uninstall IBM Director Core Services 5.20.x before
installing Platform Agent 6.3.2.
Restriction: Platform Agent 6.3.2 will block updates on IBM Director Core
Services 5.20.x systems and RSA service processors. You will no longer be able to
manage the RSA in-band. You can manage it out-of-band by connecting it to the
network and discovering it with IBM Systems Director.
v Platform Agent 6.1.1 and later uses a newer version of the LSI MR provider. This
provider will not function properly with older versions of the LSI device drivers.
In order to ensure that CIM data and alerts function properly with LSI devices,
it is important that the device drivers are at the latest levels for all Platform
Agent systems.
v See “Installing and uninstalling KVM Platform Agent” for considerations
regarding the use of Red Hat Enterprise Linux with Linux Kernel-based Virtual
Machine (KVM).
Note: If you are upgrading agents manually on a previously discovered endpoint,

you must discover the endpoint again after the upgrade. Discovering the endpoint

again allows the correct functionality to be reflected in IBM Systems Director. For
example if you are upgrading an endpoint from Agentless managed system to
Platform Agent through the manual agent installation script, you must then
discover the endpoint again with IBM Systems Director.
Related tasks:
Binding Platform Agent to specific IP addresses
Installing and uninstalling KVM Platform Agent
Preparing for a Platform Agent managed system

Before installing Platform Agent on a managed system make sure that the
requirements that are applicable to your system have been met.
Complete the following steps on each system to be managed with Platform Agent:
Set the clock on the managed system to match the time of the management server.
If the managed system time is earlier than that of the management server, the
management server will be unable to unlock the managed system.
To avoid the problem of system-time mismatch, you can configure managed
systems and the management server to synchronize their clocks using a common
network time protocol (NTP) server.
Related reference:
RedHat chkconfig bug fix
Preparing to install Platform Agent on Windows

Before installing Platform Agent on a managed system running Windows, make
sure that your system meets all the applicable requirements.
instructions, see “Running the Pre-Installation Utility on an agent (Windows)”
on page 72.
v Ensure that your system meets the hardware and software requirements for
installation, as described in “Hardware and software requirements”.
v If there is an operating system update in progress, ensure the process is
v Ensure that any agentless managed systems are prepared for discovery, as
described in “Preparing agentless managed systems”.
v If you want to use IBM Systems Director Server on System x for heterogeneous
server management, you can install Common Agent or Platform Agent on the
platforms you want to manage. You can obtain Common Agent and Platform
Agent for the supported operating systems from the IBM Systems Director Web
site at www.ibm.com/systems/software/director/downloads/agents.html.

v The IBM Systems Director for x86 DVD no longer includes OpenSSH for
Windows. If a Platform Agent managed system or Common Agent managed
system does not have a Secure Shell (SSH) package installed, IBM Systems
Director Server cannot communicate securely with the managed system. To
secure communication, install OpenSSH on the managed system. Download
OpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ and
update the managed system with SSH.
Related tasks:

Installing Platform Agent on Windows
Related reference:
Systems Director Web page
OpenSSH for Windows


You can use the Agent Installation Wizard to install agent packages on managed
systems.
IBM Systems Director Server requires a number of agent packages that can be
deployed to managed systems using the Agent Installation Wizard.The imported
agent packages are located in the dynamic group “Agent Package Groups” and can
be accessed by clicking Release Management > Agents in the navigation area. You
use the Agent Installation Wizard to select one of these agent packages to install
and one or more systems on which to install the agent package. Then, the wizard
creates an agent installation job that can run immediately or at a scheduled time.
Important: Ensure that the following requirements are met to enable use of the
Agent Installation Wizard to install and update agents:
v The root user account was used to initially request access to the managed
system.
v IBM Systems Director Server on non-Windows systems has SSH, and a
successful SSH connection exists in both directions between the server and the
agent.
v IBM Systems Director Server on Windows systems has DCOM, and a successful
DCOM connection exists in both directions between the server and the agent.
Complete the following steps to import the agent packages:

1. Download the remote agent packages from http://www.ibm.com/systems/
software/director/downloads/agents.html. Ensure that you choose packages
from the “Remote Deployment using Agent Installation wizard” section.
2. Copy the packages to a location of your choice on the IBM Systems Director
Server system.
3. Import the packages with the Agent Installation Wizard.

4. Make any required changes to the diragent.rsp and or platform.rsp response
files. See the topic for your operating system under “Installing Common Agent
manually” or “Installing Platform Agent manually” for instructions about how
to change the response files.
Complete the following steps to install agents using the Agent Installation Wizard:
1. Start the Agent Installation Wizard. You can start the wizard in multiple ways:
v From the Home page, click Additional Setup. Then, click Install agents on
systems > Deploy Agents.
v Right-click an agent package or a managed system and select Release
Management > Install Agent.
2. If the Agent Installation Wizard Welcome page appears, click Next.
3. In the Agent Installation Wizard Agents page, complete the following steps:
a. Select the agent or subagent package that you want to install in the
Available list.
Note: A subagent plugs in to a base agent and provides additional

capabilities to support IBM Systems Director plug-ins such as IBM Systems
Director VMControl. This documentation uses the collective term “agents”
to refer to both agents and subagents.
b. Click Add. The selected agent package is displayed in the Selected list.
Notes:
Selected list might already contain one or more agent packages.
v The Agent Installation Wizard can install only one agent package at a
time. If more than one agent package is displayed in the Selected list,
you will not be able to advance to the Systems page.
c. Click Next.
4. In the Agent Installation Wizard Systems page, complete the following steps:
a. Select the managed systems on which you want to install the agent package
in the Available list.
b. Click Add. The selected systems are displayed in the Selected list.
Notes:
Selected list might already contain one or more systems.
v Depending on the agent package that you are installing, some selected
systems are potentially not valid targets for installation. The wizard
checks the selected systems for some or all of the following criteria to
ensure that the systems are valid targets before allowing you to continue:
– Operating system family
– Operating system version
– Operating system distribution
– Operating system name
– Server architecture
c. Click Next.
5. In the Agent Installation Wizard Summary page, review the Selected Agents
and Selected Systems lists to ensure that they are correct.
v If the selections are not correct, click Back and make the necessary changes.

v If the selections are correct, click Finish.
After you click Finish, the Run - Install Agent window opens.
6. In the Run - Install Agent window, click the Schedule tab. On this page, you
can choose to run the job immediately or schedule the job to run at a later time.
a. A job name is required and the Name field provides a unique default name.
To change the default name, type a job name in the field.
b. To run the job immediately, click Run Now and go to step 7 on page 77.
Otherwise, click Schedule.
c. In the Schedule list, select how frequently you want the job to run. The
default setting is Once. Other values are Hourly, Daily, Weekly, Monthly,
Yearly, or Custom. Also, you can specify whether to run the job on the
weekend.
d. Select the date and time to run the job for the first time.
e. Select the time range for the job to repeat.
7. Click the Notification tab. On this page you can customize a notification that is
sent by e-mail.
a. Select from the available criteria to customize when the mail notification is
sent. You can specify that the mail be sent when one of the following
criteria is met:
v When the job begins.
v When the job completes successfully.
v When the job fails. You can further customize this criterion by setting
either the percentage of target systems on which the job had errors or the
number of systems on which the job had errors. Therefore, if the job runs
on five systems, the job has errors on two systems, and you set the
criterion threshold to 50%, the notification is not sent.
v When the job receives any error.
b. Type your mail address, mail server, and mail server port.
Tip: You can provide only one mail address.

8. Click the Options tab. On this page you can select additional options for the
job behavior.
a. Select whether you want the job to run according to your management
server's time or the target system's time.
Tip: Make sure that you know the time and time zone to which the
respective systems' clocks are set.
b. Select whether you want the job to fail if a system is offline or if you want
the job to run when the system is online again.
9. Click OK to save the job.
Click Cancel to exit from the Launch Job window without saving the job.
If the job is created successfully, a message is displayed on the page from
which you started the Scheduler. If the job creation fails, a message is displayed
in the Launch Job window so that you can correct the job.
The job created by the Agent Installation Wizard will transfer the agent
self-extracting script and the agent response file into the following directory,
which depends on your version and agent level, on the target system:
6.x Common Agent
/tmp/commonagent_tmp

6.x Platform Agent
/tmp/platformagent_temp
5.x Common Agent
install_root/SwDistPk
After the files are copied, the installation file sets are extracted into the /tmp
directory and installed. The files are then removed after a successful
installation. You need to ensure that there is sufficient space on the target
system to copy the self-extracting script and extract the file sets. Refer to the
space requirements as specified in “Hardware requirements for systems
running Common Agent or Platform Agent”.
If the agent deployment completes with errors, check the log file for your target
operating system for a possible root cause:
v Windows: %WINDIR%/diragentinst_timestamp.log or %WINDIR%/
platint_timestamp.log
Note: For more information about error log files, see “Information to provide
to the IBM Technical Support Center”.
You can view the status of the agent installation job by clicking Task Management
> Active and Scheduled Jobs.
If you installed Platform Agent on Linux, enable SNMP Access and Trap
Forwarding by installing and configuring Net-SNMP. For instructions and
information, see http://www.net-snmp.org/.
Installing Platform Agent manually

You can use these manual instructions to install Platform Agent on a managed
system. These manual instructions provide an alternative method of installation to
using the Agent Installation Wizard.
Important:
Common Agent (when applicable), and Platform Agent all together. Therefore, it
is not necessary to separately install Common Agent or Platform Agent on the
management server after installing IBM Systems Director Server. In most cases,
any IBM Systems Director tasks requiring Common Agent or Platform Agent
will be performed for systems with IBM Systems Director Server installed.
v If you have BMC, IMM, or IMM2 service processors, use Platform Agent 6.1.1 or
later to help ensure full functionality and support.
v If you have RSA service processors, use IBM Director Core Services 5.20.x to
help ensure full functionality and support. If you do decide to use Platform
Agent 6.3.2, you must first uninstall IBM Director Core Services 5.20.x before
installing Platform Agent 6.3.2.
Restriction: Platform Agent 6.3.2 will block updates on IBM Director Core
Services 5.20.x systems and RSA service processors. You will no longer be able to
manage the RSA in-band. You can manage it out-of-band by connecting it to the
network and discovering it with IBM Systems Director.
v Platform Agent 6.1.1 and later uses a newer version of the LSI MR provider. This
provider will not function properly with older versions of the LSI device drivers.

In order to ensure that CIM data and alerts function properly with LSI devices,
it is important that the device drivers are at the latest levels for all Platform
Agent systems.
v See “Installing and uninstalling KVM Platform Agent” for considerations
regarding the use of Red Hat Enterprise Linux with Linux Kernel-based Virtual
Machine (KVM).
Related tasks:
Preparing a Platform Agent managed system
Installing Platform Agent on Windows

After preparing your system, you can install Platform Agent on a system that is
running Windows by downloading the installation files from the IBM Systems
Director support Web site or by using the DVD. You can then perform a standard
Installing Platform Agent on Windows using the installation wizard:
To use the installation wizard to install Platform Agent on a system that is running
Windows, download the installation files from the IBM Systems Director support
Web site or use the DVD.
Important:
Agent 6.3.2.
You can install Platform Agent on Windows from either installation media or from
a downloaded installation package.

Table 19. Installation options for Platform Agent on Windows
Note: To obtain an image of the IBM Systems Director for
x86, V6.3.2 DVD, download the
Downloaded installation
6.3.2 agents
package
Install the 6.3.2 agents unless you need full
support for downlevel agents that have the
previously specified hardware and software
configurations.
v SysDir6_3_2_Platform_Agent_Windows.zip
v SysDir6_3_2_Platform_Agent_Windows.jar
(agent package for Agent Installation Wizard
installation)
Notes:
v The Platform Agent 6.3.2 installer installs MSI 4.5 as a prerequisite. On Windows
2008, the Platform Agent installer issues an error message and exits if MSI 4.5 is
not already installed, because an immediate reboot is required. On other
versions of Windows, an immediate reboot is not required and the Platform
Agent installer is able to continue. To bypass this scenario on Windows 2008,
create Windows virtual images with MSI 4.5 already installed.
v Platform Agent 6.3.2 uses MSI 4.5, which requires a special option when using
Remote Desktop Connection. To enable Remote Desktop Connection to start,
issue one of the following commands:
– For Windows XP SP2 or Windows 2003:
mstsc /console
– For Windows XP SP3 or Windows 2008 or later:
mstsc /admin
v Platform Agent 6.3.2 does not support RSA II. Any attempt to install Platform
Agent 6.3.2 will be blocked on systems that contain any of the these items along
with IBM Director Core Services 5.20.31 or older. You can force the installation of
Platform Agent 6.3.2 by specifying the force option with the following
command:
dir6.3.2_platformagent_windows.exe force
However, rather than force the installation of Platform Agent 6.3.2, instead
uninstall IBM Director Core Services 5.20.31 and then install Platform Agent
6.3.2.
To install Platform Agent on Windows using the installation wizard, complete the
following steps:
Tip: You can find the installation logs for this process in C:\Windows\
Platinst*.log.
1. Start the installation from the Common Agent installation source:

c. Click Start > Run.
\installation_directory\dir6.3.2_platformagent_windows.exe
where installation_directory is the path to the extracted installation files.

The Welcome to the installation wizard for IBM Systems Director Platform
Agent window opens.
steps:
2) Click IBM Systems Director Agents.
3) Click Install IBM Systems Director Platform Agent.
If the IBM Systems Director Welcome window does not automatically open,
then complete the following steps:
v For 64-bit:
e:\agent\SysDir6_3_2_Platform_Agent_Windows.jar /
-d c:\632PA\
v For 32-bit:
-d c:\632PA\
where e is the drive letter of the drive and c:\632PA\ is an existing
3) From the directory where you saved the installation files, open the
repository folder and run dir6.3.2_platformagent_windows.exe
The installation program starts.
Accessibility note: Screen readers might not process the IBM Systems Director
Welcome window correctly. To start the installation wizard for Platform Agent
using the keyboard, complete the following steps:
a. Close the IBM Systems Director Setup window.
b. Open Windows Explorer.
c. Browse to the directory where you extracted the installation files.
d. Run the dir6.3.2_platformagent_windows.exe program. The installation
wizard starts, and the IBM Systems Director Welcome window opens.

4. To select an alternative location for the creation of the installation, click Change
and select another directory.
5. Click Next. The Ready to Install the Program window is displayed.
6. Click Install. Various windows that display the status of the installation are
displayed. When the installation is complete, the Installation complete window
is displayed.
7. Click Finish.
Note: On Windows and Linux RSA II systems, Platform Agent 6.3.2 will install the
LSI MegaRAID provider along with the RSA II service. Platform Agent 6.3.2 will
also install the OSA IPMI driver on Windows 2003 systems that need it. Use the
Verify Connection page to query vital properties after you upgrade to Platform
Agent 6.3.2. This will immediately renew alert subscriptions for the LSI MegaRAID
provider and Basic RAID hardware. If you do not verify the connection, the alert
subscriptions might take as long as an hour to update.
Related tasks:
Restarting Platform Agent

Related reference:

Performing an unattended installation of Platform Agent on Windows:
You can perform an unattended installation of Platform Agent using a response

file, which provides answers to the questions that are posed by the installation
wizard. You can use this method to create a standard installation file that can be
used on many systems.
Important:

Agent 6.3.2.
You can install Platform Agent on Windows from either installation media or from
a downloaded installation package.
Table 20. Installation options for Platform Agent on Windows
Note: To obtain an image of the IBM Systems Director for
x86, V6.3.2 DVD, download the
Downloaded installation
6.3.2 agents
package
Install the 6.3.2 agents unless you need full
support for downlevel agents that have the
previously specified hardware and software
configurations.
v SysDir6_3_2_Platform_Agent_Windows.zip
v SysDir6_3_2_Platform_Agent_Windows.jar
(agent package for Agent Installation Wizard
installation)
Notes:
v The Platform Agent 6.3.2 installer installs MSI 4.5 as a prerequisite. On Windows
2008, the Platform Agent installer issues an error message and exits if MSI 4.5 is
not already installed, because an immediate reboot is required. On other
versions of Windows, an immediate reboot is not required and the Platform
Agent installer is able to continue. To bypass this scenario on Windows 2008,
create Windows virtual images with MSI 4.5 already installed.
v Platform Agent 6.3.2 uses MSI 4.5, which requires a special option when using
Remote Desktop Connection. To enable Remote Desktop Connection to start,
issue one of the following commands:

– For Windows XP SP2 or Windows 2003:
mstsc /console
– For Windows XP SP3 or Windows 2008 or later:
mstsc /admin
v Platform Agent 6.3.2 does not support RSA II. Any attempt to install Platform
Agent 6.3.2 will be blocked on systems that contain any of the these items along
with IBM Director Core Services 5.20.31 or older. You can force the installation of
Platform Agent 6.3.2 by specifying the force option with the following
command:
dir6.3.2_platformagent_windows.exe force
However, rather than force the installation of Platform Agent 6.3.2, instead
uninstall IBM Director Core Services 5.20.31 and then install Platform Agent
6.3.2.
1. Start the installation from the installation source:
c. Copy the platformagent.rsp response file to a new location. This file is in
the \directory directory, where directory is the local directory into which
you extracted the files.
Note: The IBM Director Core Services 5.20.31 coresvcs.rsp response file is
in the \directory\FILES directory, where directory is the local directory into
which you extracted the 5.20.31 files.
steps:
c. If the IBM Systems Director Welcome window does not automatically open,
then complete the following steps to extract the jar file:
v For 64-bit:
-d c:\632PA\
v For 32-bit:
-d c:\632PA\
where e is the drive letter of the drive and c:\632PA\ is an existing

d. Copy the platformagent.rsp response file to a local directory. This file is in
the repository folder within the directory to which you extracted the
installation files.
2. Open the copy of the platformagent.rsp file, which follows the Windows INI
file format, in an ASCII text editor.
the platformagent.rsp file to myresponsefile.rsp.
4. From the repository folder, type the following command and press Enter:
dir6.3.2_platformagent_windows.exe /s /a installationtype \
rsp="responsefile" option
installationtype
v unattended shows the progress of the installation but does not
require any user input.
v silent suppresses all output to the screen during installation.
responsefile
messages.

dir6.3.2_platformagent_windows.exe /s /a silent \
rsp="c:\myfolder\myresponsefile.rsp"
This example performs a silent installation of Platform Agent on Windows

using the myresponsefile.rsp response file.
Tip: After running a silent installation, you can verify that the installation is
complete by checking for the process in Windows Task Manager.
Notes:

whether the IBM Systems Director Server installation completes successfully.
Note: On Windows and Linux RSA II systems, Platform Agent 6.3.2 will install the
LSI MegaRAID provider along with the RSA II service. Platform Agent 6.3.2 will
also install the OSA IPMI driver on Windows 2003 systems that need it. Use the
Verify Connection page to query vital properties after you upgrade to Platform
Agent 6.3.2. This will immediately renew alert subscriptions for the LSI MegaRAID
provider and Basic RAID hardware. If you do not verify the connection, the alert
subscriptions might take as long as an hour to update.
Related tasks:
Restarting Platform Agent

Related reference:

Verifying the successful installation of an IBM Systems Director agent

You can verify a successful installation by starting IBM Systems Director Server,
logging into the Web interface, and discovering the new managed system.
To verify that the agent installation was successful and ensure your managed
systems can be discovered, complete the following steps:
1. If IBM Systems Director Server is running on AIX or Linux, complete the
following steps to start IBM Systems Director Server:
a. If it is not already started, start IBM Systems Director processes on the
management servers by running the smstart command:
install_root/bin/smstart
b. To view the IBM Systems Director Server status, type the following
command and press Enter:
install_root/bin/smstatus -r
Note: You can use Ctrl+C to exit from smstatus -r if necessary.

When this command returns a value of Active, the server is started.
2. Log in to the Web interface for IBM Systems Director Server. For instructions,
see Logging into IBM Systems Director Server.

3. The IBM Systems Director Home page provides a quick overview, as well as
links to all necessary configuration tasks. To configure IBM Systems Director,
perform these steps:
a. Click System Discovery on the Initial Setup tab to discovery
recently-installed agents.
b. Click Collect Inventory on the Initial Setup tab to collect inventory data on
all the recently-installed agents.
c. Run these options from the Additional Setup tab.
v Create event thresholds and automation plans
v Check for updates on discovered systems.
v Set up additional user security
v Start configuring your systems
After you have verified that the agent installation was successful, complete the
following tasks:
1. (Optional) Configure and activate any plug-ins you want to use. For
instructions, see Activating or upgrading the advanced plug-ins of IBM Systems
Director.
Related tasks:
Logging in
Collecting and viewing inventory data

Chapter 3. Preparing agentless managed systems
Prepare the agentless managed systems in your environment before you discover
or manage them with IBM Systems Director.
Note: A managed system might have more than one IP address (for example,
when the system contains more than one network interface card). When a
managed resource has multiple IP addresses, specify which IP address Systems
Director uses to manage the resource. To specify the IP address to use, you specify
that the management server ignore (or exclude) the other IP addresses associated
with the resource. For more information, see “Excluding IP addresses.”
Complete the following steps on each system to be managed.

1. On all managed systems that use the ssh protocol to communicate with IBM
Systems Director Server, ensure that the PasswordAuthentication value in
/etc/ssh/sshd_config is set to yes. So, the corresponding line in the
sshd_config file will appear as follows:
PasswordAuthentication yes
2. On all agentless managed systems that use the root user for request access for
the ssh protocol, ensure that the PermitRootLogin value in
/etc/ssh/sshd_config is set to yes.
Notes:
1. You must restart the ssh server for any changes made to sshd_config to take
effect.
2. IBM Systems Director does not support the ssh protocol on VMware ESXi
hosts. If ssh is discovered on a VMware ESXi managed system, it might cause
problems when attempting to collect inventory.
Related tasks:
Related reference:
AIX Pegasus CIM server and providers
Preparing to manage service processors with IBM Systems Director

You can use IBM Systems Director to manage supported service processors that are
installed in a managed system.
IBM Systems Director can manage service processors that are installed in Agentless
managed systems, Platform Agent managed systems, and Common Agent
managed systems.
v For Agentless managed systems, you do not need to install drivers to perform
Agentless management of the service processors.
v For Platform Agent managed systems and Common Agent managed systems,
management of the service processor uses the Common Information Model
(CIM) standard, and requires not only installation of either Platform Agent or
Common Agent on the managed system, but also installation of a device driver,
and possibly a shared library to access the device driver.
To install the required drivers on a Platform Agent managed system or Common

Agent managed system to enable management of the service processor, complete
the following steps:
1. See the documentation for your managed server to identify the type of service
processor that is installed.
2. Identify your server type in Table 22.
Note: For information about specific IBM Systems Director functions that
support or do not support these systems, see IBM ServerProven at
www.ibm.com/servers/eserver/serverproven/compat/us/.
Table 22. Servers with service processors that are supported for Platform Agent or Common Agent management by
Server type Supported models
IBM BladeCenter blade servers with v IBM BladeCenter HC10
an IPMI baseboard management v IBM BladeCenter HS20, machine types 1883, 1884, 7981, 8843
controller (BMC) v IBM BladeCenter HS12, machine types 8014, 8028
v IBM BladeCenter HS21
See the “IBM BladeCenter, System x, v IBM BladeCenter HS21 XM
and System x servers with an IPMI v IBM BladeCenter HS40
baseboard management controller v IBM BladeCenter JS12 Express
(BMC) or with an integrated systems v IBM BladeCenter JS20
management module (IMM)” column v IBM BladeCenter JS21
in Table 23 on page 105. v IBM BladeCenter JS22
v IBM BladeCenter LS20
v IBM BladeCenter QS21
IBM BladeCenter blade servers with v IBM BladeCenter HS22 machine type 7870
an integrated systems management v IBM BladeCenter HS22V machine type 7871
module (IMM) v IBM BladeCenter HX5 machine type 7872
Note: The IMM internally contains a
BMC.
See the “IBM BladeCenter, System x,

and System x servers with an IPMI
baseboard management controller
(BMC) or with an integrated systems
management module (IMM)” column
in Table 23 on page 105.
IBM BladeCenter blade servers with IBM BladeCenter HS20, machine types 8678, 8832, 8833
an Integrated systems management
processor (ISMP)
See the “IBM BladeCenter and

System x servers with an integrated
systems management processor
(ISMP)” column in Table 23 on page
105.

IBM Systems Director (continued)
™
eServer servers with an IPMI v IBM eServer 325, machine type 8835
baseboard management controller v IBM eServer 326, machine type 8848
(BMC) v IBM eServer 326m, machine type 7969
v IBM eServer 326m, machine type 7992
See the “eServer servers with an
IPMI baseboard management
controller (BMC)” column in Table 23
on page 105.
Note: Some systems support
installation of an optional Remote
Supervisor Adapter or Remote
Supervisor Adapter II service
processor. If this optional service
processor is installed, it supersedes
the standard service processor for
that system, and all management
occurs through the Remote
Supervisor Adapter or Remote
Supervisor Adapter II.
System x and System x servers with v System x3200 v System x 206m
an IPMI baseboard management v System x3200 M2 v System x 236
controller (BMC) v System x3250 v System x 260
v System x3250 M2 v System x 306m
See the “IBM BladeCenter, System x, v System x3250 M3 v System x 336
and System x servers with an IPMI v System x3350 v System x 346
baseboard management controller v System x3400 v System x 347
(BMC) or with an integrated systems v System x3450 v System x 366
management module (IMM)” column v System x3455
in Table 23 on page 105. v System x3500
Note: Some systems support v System x3550
installation of an optional Remote v System x3610
Supervisor Adapter or Remote v System x3650
Supervisor Adapter II service v System x3650 T
processor. If this optional service v System x3655
processor is installed, it supersedes v System x3755
the standard service processor for v System x3755 M31
that system, and all management v System x3800
occurs through the Remote v System x3850
Supervisor Adapter or Remote 1
Supervisor Adapter II. The BMC in this system provides a subset of the function found in the
other system BMCs.
Chapter 3. Preparing agentless managed systems 103

System x and System x servers with v System x3200 M3 machine types 7327 and 7328
an integrated systems management v System x3250 M2 machine types 4190, 4191, and 4194
module (IMM) v System x3400 M2 machine types 7836 and 7837
Note: The IMM internally contains a v System x3400 M3 machine types 7378 and 7379
BMC. v System x3500 M2 machine type 7839
v System x3500 M3 machine type 7380
See the “IBM BladeCenter, System x, v System x3550 M2 machine type 7946
and System x servers with an IPMI v System x3550 M3 machine type 7944
baseboard management controller v System x3620 M3 machine type 7376
(BMC) or with an integrated systems v System x3650 M2 machine type 7947
management module (IMM)” column v System x3650 M3 machine type 7945
in Table 23 on page 105. v System x3690 X5 machine type 7148
v System x3850 M2 machine type 7233
v System x3850 X5 machine type 7145
v System x3950 M2 machine types 7141 and 7233
v System x3950 X5 machine type 7145
System x and System x servers with v System x3105 v System x 206
a Remote Supervisor Adapter II or v System x3200 v System x 206m
Remote Supervisor Adapter II v System x3200 M2 v System x 225
SlimLine v System x3250 v System x 226
v System x3250 M2 v System x 232
See the “System x and System x v System x3350 v System x 236
servers with a Remote Supervisor v System x3400 v System x 255
Adapter II or Remote Supervisor v System x3455 v System x 260
Adapter II SlimLine” column in v System x3500 v System x 305
Table 23 on page 105. v System x3550 v System x 306
Note: On some of these systems, v System x3650 v System x 306m
installation of the Remote Supervisor v System x3650 T v System x 335
Adapter or Remote Supervisor v System x3655 v System x 336
Adapter II service processor is v System x3755 v System x 342
optional. If this optional service v System x3800 v System x 345
processor is not installed, all v System x3850 v System x 346
management occurs through either v System x3850 M2 v System x 347
an IPMI baseboard management v System x3950 v System x 360
controller (BMC) or an integrated v System x3950 E v System x 366
systems management processor v System x3950 M2 v System x 445
(ISMP). v System x 460
Restriction: When IBM Director v System x MXE 460
Agent 5.20.x or IBM Director Core
Services 5.20.x is installed, you can
manage Remote Supervisor Adapter
II or Remote Supervisor Adapter II
SlimLine in-band. When Common
Agent 6.1.x or 6.2.x, or Platform
Agent 6.1.x or 6.2.x are installed, you
are no longer able to manage the
RSA in-band. You can manage it
out-of-band by connecting it to the
network and discovering it with IBM
Systems Director.

System x servers with an integrated v System x 232
systems management processor v System x 235
(ISMP) v System x 255
v System x 335
See the “IBM BladeCenter and v System x 342
System x servers with an integrated v System x 343
systems management processor v System x 345
(ISMP)” column in Table 23.
IBM Flex System compute nodes v IBM Flex System x220 Compute
with the integrated management Node, Types 2585 and 7906
module II (IMM2)
v IBM Flex System x240 Compute
Node, Types 7863, 8737, and 8738
3. Identify the required drivers for in-band (Platform Agent or Common Agent)
management of the service processors for your server type and operating
system in Table 23.
RSA restriction: When IBM Director Agent 5.20.x or IBM Director Core
Services 5.20.x is installed, you can manage Remote Supervisor Adapter II or
Remote Supervisor Adapter II SlimLine in-band. When Common Agent 6.1.x or
6.2.x, or Platform Agent 6.1.x or 6.2.x are installed, you are no longer able to
manage the RSA in-band. You can manage it out-of-band by connecting it to
the network and discovering it with IBM Systems Director.
Table 23. Required drivers for in-band management of service processors
IBM BladeCenter,
System x, and System x
servers with an IPMI
baseboard management System x and System x IBM BladeCenter and
controller (BMC) or eServer servers with an servers with a Remote System x servers with
with an integrated IPMI baseboard Supervisor Adapter II an integrated systems
Operating system of systems management management controller or Remote Supervisor management processor
managed server module (IMM) (BMC) Adapter II SlimLine (ISMP)
v Red Hat Enterprise OpenIPMI driver OpenIPMI driver RSA daemon SMBus driver
Linux, version 4
LM78 driver USB drivers
v Red Hat Enterprise
Linux, version 5.0 LM78 driver
Other Red Hat OSA IPMI driver MSI IPMI driver RSA daemon SMBus driver
Enterprise Linux
distributions IBM Mapping Layer IBM Mapping Layer USB drivers
LM78 driver LM78 driver
v SUSE Linux OpenIPMI driver OpenIPMI driver RSA daemon SMBus driver
Enterprise Server 9 for
x86
v SUSE Linux LM78 driver
Enterprise Server 10
for x86
Other SUSE Linux OSA IPMI driver MSI IPMI driver RSA daemon SMBus driver
distributions
IBM Mapping Layer IBM Mapping Layer USB drivers
LM78 driver LM78 driver

Table 23. Required drivers for in-band management of service processors (continued)
IBM BladeCenter,
System x, and System x
servers with an IPMI
baseboard management System x and System x IBM BladeCenter and
controller (BMC) or eServer servers with an servers with a Remote System x servers with
with an integrated IPMI baseboard Supervisor Adapter II an integrated systems
Operating system of systems management management controller or Remote Supervisor management processor
managed server module (IMM) (BMC) Adapter II SlimLine (ISMP)
Virtual systems using OpenIPMI driver OpenIPMI driver RSA daemon SMBus driver
Xen
LM78 driver
VMware ESX Server, OpenIPMI driver OpenIPMI driver USB drivers SMBus driver
versions 4.0, 4.0.1, and
4.1. LM78 driver LM78 driver
Other VMware OSA IPMI driver MSI IPMI driver Not supported SMBus driver
distributions
IBM Mapping Layer IBM Mapping Layer
LM78 driver
Windows Server 2008 MS IPMI driver MS IPMI driver RSA Library The necessary drivers
are installed with
Common Agent or
Platform Agent.
Windows Server 2003 R2 MS IPMI driver MS IPMI driver RSA Library The necessary drivers
are installed with
USB drivers Common Agent or
Platform Agent.
Other Windows OSA IPMI driver MSI IPMI driver RSA Library The necessary drivers
operating systems are installed with
IBM Mapping Layer IBM Mapping Layer USB drivers Common Agent or
Platform Agent.
LM78 driver
4. Install the required drivers.
Note: If required, the MSI IPMI driver and the OSA IPMI driver must be
installed before the IBM Mapping Layer.
IBM Mapping Layer
The IBM Mapping Layer is used to translate IBM Systems Director
"generic" requests into driver-specific requests for different IPMI
drivers. Download this driver from the IBM Support Web Site at
www.ibm.com/support/us.
LM78 driver
The LM78 device driver ensures that IBM Systems Director Server
receives memory and processor Predictive Failure Analysis (PFA) alerts.
See “Installing IBM LM78 and SMBus device drivers” for installation
instructions.
MS IPMI driver
IBM Systems Director agent can use the Intelligent Platform
Management Interface (IPMI) driver included with Windows 2003 R2
and Windows 2008. In order for IBM Systems Director Server to
provide in-band alerting from the Baseboard Management Controller
(BMC) or Integrated Management Module (IMM), the MS IPMI driver
is required. By default, the MS IMPI driver is not installed with
Windows 2003 R2. To install the Microsoft IPMI device driver on

Windows 2003 R2, see “Managing IPMI Devices in Windows 2003 R2
and Windows 2008” in the IBM Systems Director Best Practices Wiki.
The MS IPMI driver is included with the Windows 2008 operating
system. No separate installation is required.
MSI IPMI driver
The MSI IPMI device driver is used to communicate with the IPMI
baseboard management controller. All other systems should use the
OSA IPMI driver. Download this driver from the IBM Support Web Site
at www.ibm.com/support/us.
OpenIPMI driver
This driver is included with the operating system. No separate
installation is required.
OSA IPMI driver
The OSA IPMI device driver is used to communicate with the IPMI
baseboard management controller. Download this driver from the IBM
Support Web Site at www.ibm.com/support/us.
RSA daemon
The RSA daemon is a Linux-only program that is used to interface with
the Remote Supervisor Adapter. Download this driver from the IBM
Support Web Site at www.ibm.com/support/us.
RSA library
The RSA library device driver is a Windows-only driver that is used to
interface with the Remote Supervisor Adapter. It also prevents driver
communication from interfering with IBM Systems Director. Download
this driver from the IBM Support Web Site at www.ibm.com/support/
us.
SMBus driver
The SMBus device driver ensures that configuration manager and
status manager tasks function correctly, and is used to communicate
with the integrated systems management processor (ISMP) on some
servers.
See “Installing IBM LM78 and SMBus device drivers for Linux” for
installation instructions.
USB drivers
The RSA daemon and RSA library use this driver to communicate with
the Remote Supervisor Adapter II. This driver is included with the
operating system. No separate installation is required.
5. Make sure that you have the latest firmware installed for your service
processors.

Related concepts:
Platform agent
Common agent
Related tasks:
Installing the LM78 or SMBus device driver
Related reference:
Support Web site

Unresponsive service processor
Preparing to manage an IBM BladeCenter chassis using IBM Systems

Director Server on a non-blade server
You can install IBM Systems Director Server on a non-blade server. With this
management server you can manage one or more IBM BladeCenter units and the
blade servers installed in them. You must configure the network so that this
installation is possible.
Complete the following steps to prepare to manage an IBM BladeCenter chassis

using IBM Systems Director Server installed on a non-blade server:
1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to
assign an address to the external port of the management module. When an
IBM BladeCenter management module is first started, it searches for a DHCP
server. If a DHCP server is not found, the IBM BladeCenter management
module assigns IP address 192.168.70.125 to the external management port.
Because this static IP address is the same for all management modules, IP
address conflicts can occur if you do not use a DHCP server and introduce
multiple IBM BladeCenter chassis onto a network simultaneously. When you
configure the IBM BladeCenter chassis, you assign static IP addresses to the
switch module and the external and internal ports of the management module.
2. Set up a separate management network to configure and manage your IBM
BladeCenter chassis and blade servers. By separating the LAN segment used
for production from the LAN segment to which the IBM BladeCenter
management module is connected, you can ensure that only authorized system
administrators can connect to the IBM BladeCenter chassis and switch modules.
Figure 1 on page 109 shows such a network configuration.
3. If you intend to use Remote Deployment Manager (RDM), install RDM on the
management server.
4. Consider installing the database server on the management LAN.
5. Make sure that you have installed the latest version of the management module
firmware. To download the firmware, go to the IBM Servers Web site at
www.ibm.com/servers/.

Figure 1. Example of IBM BladeCenter deployment network when IBM Systems Director
Server is not installed on a blade server
This network configuration ensures that applications running on the blade servers
cannot modify chassis settings, because the blade servers have no connection to
either the management module or the switch module configuration ports.
Note: If you are using an IBM BladeCenter management module instead of an

advanced management module, only one of the following software applications
can communicate with it at any given time:
v Cluster Systems Management (CSM)
v IBM Systems Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
Preparing to manage an IBM BladeCenter chassis using IBM Systems

Director Server on a blade server
You can install IBM Systems Director Server on a blade server. With this
management server you can manage the IBM BladeCenter unit, including the
server on which IBM Systems Director Server is installed, and other IBM
BladeCenter units. You must configure the network so that this installation is
possible.
Consider the following issues when managing the IBM BladeCenter unit that
contains the management server:
v Enable access for authorized administrators as determined by the security policy
established for the user environment.
v Be careful when making changes to the configuration of the IBM BladeCenter
chassis from IBM Systems Director itself. Such changes could effectively remove
the instance of IBM Systems Director Server from the network and halt the
entire IBM Systems Director environment.
Specifically, do not perform these tasks on the blade server where IBM Systems
Director Server is installed without careful consideration:
– Powering off that blade server

– Changing the boot options on that blade server
v Create a network setup that enables the IBM BladeCenter Management Module
to communicate with the management server. Otherwise IBM Systems Director
will be unable to discover the IBM BladeCenter chassis that contains the
management server.
By default, the blade servers installed in a IBM BladeCenter chassis cannot

communicate automatically with the IBM BladeCenter Management Module. This
architecture is designed to prevent the blade servers from modifying the IBM
BladeCenter chassis settings. If you install IBM Systems Director Server on a blade
server and want to use the instance of IBM Systems Director to manage the IBM
BladeCenter unit in which the management server is installed, you must enable
communication between the management server and the management module.
1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to
assign an address to the external port of the management module. When an
IBM BladeCenter management module is first started, it searches for a DHCP
server. If a DHCP server is not found, the IBM BladeCenter management
module assigns IP address 192.168.70.125 to the external management port.
Because this static IP address is the same for all management modules, IP
address conflicts can occur if you do not use a DHCP server and introduce
multiple IBM BladeCenter chassis onto a network simultaneously. When you
configure the IBM BladeCenter chassis, you assign static IP addresses to the
switch module and the external and internal ports of the management module.
2. Set up a separate management network to configure and manage your IBM
BladeCenter chassis and blade servers. By separating the LAN segment used
for production from the LAN segment to which the IBM BladeCenter
management module is connected, you can ensure that only authorized system
administrators can connect to the IBM BladeCenter chassis and switch modules.
Figure 1 on page 109 shows such a network configuration.
3. To use an installation of IBM Systems Director Server on a blade to manage the
IBM BladeCenter unit in which the management server is installed, enable
communication between the Campus LAN and the Management LAN. Figure 2
on page 111 shows such a network configuration.
4. Consider installing the database server on the management LAN.
5. Make sure that you have installed the latest version of the management module
firmware. To download the firmware, go to the IBM Servers Web site at
www.ibm.com/servers/.

Figure 2. Example of IBM BladeCenter deployment network when IBM Systems Director
Server is installed on a blade server
With this configuration, IBM Systems Director Server can communicate through the
Campus LAN to the Management LAN and then onto the management module.
Note: If you are using an IBM BladeCenter management module instead of an

advanced management module, only one of the following software applications
can communicate with it at any given time:
v Cluster Systems Management (CSM)
v IBM Systems Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
Related reference:
Systems
Preparing Windows managed systems

You might need to configure certain Windows systems before you can discover
them with IBM Systems Director Server. Ensure that each Windows system that
you want to manage has been appropriately configured.
Preparing Windows Server 2003 managed systems

You might need to configure certain Windows Server 2003 systems before you can
discover them with IBM Systems Director Server. Ensure that each Windows Server
2003 system that you want to manage has been appropriately configured.
Typically, managed systems are first discovered using the discovery task in IBM
Systems Director Web interface. Then, Platform Agent or Common Agent is
installed on the managed systems directly from IBM Systems Director Web
interface. The configuration of some Windows Server 2003 managed systems,
however, can prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows Server 2003 system to enable
discovery by IBM Systems Director Server:

Verify that remote registry administration is enabled. Remote registry
administration must be enabled in order for Agentless managed system discovery
to run commands and run scripts on the managed system. The default setting for
remote registry administration on Windows systems is enabled. Complete the
following steps to verify or change the remote registry administration setting:
1. Click Start > Control Panel > System and Maintenance > Administrative
Tools.
2. In the Administrative Tools window, double-click Services.
3. In the list of services in the Services window, right-click the Remote Registry
service and select Properties from the menu.
4. On the General page, set the Startup type to Automatic.
5. If the Service status is not Started, click Start to start the service.
6. Click OK to apply the new settings and close the window.
Preparing Windows Server 2008 managed systems

You might need to configure certain Windows Server 2008 systems before you can
discover them with IBM Systems Director Server. Ensure that each Windows Server
2008 system that you want to manage has been appropriately configured.
interface. The configuration of some Windows Server 2008 managed systems,
however, can prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows Server 2008 system to enable
discovery by IBM Systems Director Server:
Verify that remote registry administration is enabled. Remote registry

administration must be enabled in order for Agentless managed system discovery
to run commands and run scripts on the managed system. The default setting for
remote registry administration on Windows systems is enabled. Complete the
following steps to verify or change the remote registry administration setting:
1. Click Start > Control Panel > System and Maintenance > Administrative
Tools.
2. In the Administrative Tools window, double-click Services.
3. In the list of services in the Services window, right-click the Remote Registry
service and select Properties from the menu.
4. On the General page, set the Startup type to Automatic.
5. If the Service status is not Started, click Start to start the service.
6. Click OK to apply the new settings and close the window.
Preparing Windows Vista managed systems

Some Windows Vista systems might need to be configured before you can be
discover or manage them with IBM Systems Director Server. Make sure each
Windows Vista system that you want to manage has been appropriately
configured.
Typically, managed systems are first discovered using the Discovery task in IBM

interface. The configuration of some Windows Vista managed systems, however,
can prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows Vista system to enable

management by IBM Systems Director Server:
Related reference:
Preparing to manage an agentless managed system running

Windows Vista
Before IBM Systems Director can manage a system running Windows Vista, you
must configure a password-protected administrator account on the managed
system and enable sharing and the remote registry service.
To prepare the Windows Vista system for management by IBM Systems Director,
1. Configure the user account that IBM Systems Director will use.
Type of account Configuration steps

Built-in Enable the Administrator account and set a password for the
Administrator account.
account on the 1. Click Start > Control Panel > System and Maintenance >
managed system Administrative Tools.
2. In the Administrative Tools window, double-click Local
Security Policy.
3. Click Security Settings > Local Policies > Security Options.
4. Double-click Accounts: Administrator account status.
5. Click Enabled, and then click OK.
6. Log in to Windows Vista using the Administrator account, and
then set a password for the account.
Local user account Disable User Account Control, create the user account, and set a
other than password for the account.
Administrator 1. Click Start > Control Panel > System and Maintenance >
Administrative Tools.
Security Policy.
4. Double-click User Account Control: Run all administrators in
Admin Approval Mode.
5. Click Disabled, and then click OK.
6. Create the user account you will use for IBM Systems Director,
if it does not already exist.
7. Set the user account type to administrator.
8. Set a password for the account.

Type of account Configuration steps
Domain account Disable User Account Control.
1. Click Start > Control Panel > System and Maintenance >
Administrative Tools.
Security Policy.
4. Double-click User Account Control: Run all administrators in
Admin Approval Mode.
5. Click Disabled, and then click OK.
To enable these changes, you will need to shut down and restart the managed
system.
2. Verify that remote registry administration is enabled. Remote registry
administration must be enabled in order for Agentless managed system
discovery to run commands and run scripts on the managed system. The
default setting for remote registry administration on Windows systems is
enabled. Complete the following steps to verify or change the remote registry
administration setting:
a. Click Start > Control Panel > System and Maintenance > Administrative
Tools.
b. In the Administrative Tools window, double-click Services.
c. In the list of services in the Services window, right-click the Remote
Registry service and select Properties from the menu.
d. On the General page, set the Startup type to Automatic.
e. If the Service status is not Started, click Start to start the service.
f. Click OK to apply the new settings and close the window.
3. Configure Sharing and Discovery preferences. Complete the following steps:
a. Click Start > Control Panel > Network and Internet > Network and
Sharing Center.
b. Under Sharing and Discovery, turn on each of the following items:
v Network discovery
v File sharing
v Password protected sharing
4. Click Start > Control Panel > Network and Internet > Windows Firewall.
5. Click Allow a program through a Windows Firewall. The Windows Firewall
Settings window opens and displays the Exceptions page.
6. In the list of exceptions, select the File and Printer Sharing check box.
Note: Enabling file and printer sharing allows IBM Systems Director to use
Remote Execution and Access (RXA) ports 135, 137, 138, and 139, as well as
DCOM port 445, to communicate with the managed system.
7. Click OK.
Preparing a Windows Vista system for Platform Agent managed

system management
Before IBM Systems Director can manage Platform Agent on a system running
Windows Vista, you must configure the firewall to allow communication on the
SLP, CIM, and CIM SSL ports.

To prepare the Windows Vista system for Platform Agent managed system
management by IBM Systems Director, complete the following steps:
1. Configure the system for Agentless managed system management as described
in “Preparing to manage a Agentless managed system running Windows
Vista.” Configuration for Agentless managed system management is required in
order to access the managed system.
3. Click Allow a program through Windows Firewall.
4. Select the Remote administration check box.
5. Specify ports to allow through Windows Firewall. Complete the following steps
for each of the ports listed in Table 24.
a. Click Add port.
b. Specify the Name, Port number, and Protocol in the Add port window.
c. Click OK.
Table 24. Ports required for Platform Agent managed system management of Windows Vista
systems
Name Port number Protocol
SLP 427 TCP
SLP 427 UDP
CIM 5988 TCP
CIM SSL 5989 TCP
CIM Listener 6988 TCP
6. Click OK.
Preparing a Windows Vista system for Common Agent managed

system management
Before IBM Systems Director can manage Platform Agent on a system running
Windows Vista, you must configure the firewall to allow communication with
Common Agent on ports 14247 and 14248.
To prepare the Windows Vista system for Common Agent managed system
management by IBM Systems Director, complete the following steps:
1. Configure the system for Agentless managed system management as described
in “Preparing to manage a Agentless managed system running Windows
Vista.” Configuration for Agentless managed system management is required in
order to access the managed system.
3. Click Allow a program through Windows Firewall.
4. Select the Remote administration check box.
5. Specify ports to allow through Windows Firewall. Complete the following steps
for each of the ports listed in Table 25 on page 116.
a. Click Add port.
b. Specify the Name, Port number, and Protocol in the Add port window.
c. Click OK.

Table 25. Ports required for Common Agent managed system management of Windows Vista
systems
Name Port number Protocol
Director IPC 14247 TCP 14247 TCP
Director IPC 14247 UDP 14247 UDP
Director IPC 14248 TCP 14248 TCP
Director IPC 14248 UDP 14248 UDP
6. Click OK.
Preparing Windows XP managed systems

You might need to configure certain Windows XP systems before you can discover
them with IBM Systems Director Server. Ensure that each Windows XP system that
you want to manage has been appropriately configured.
interface. The configuration of some Windows XP managed systems, however, can
prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows XP system to enable discovery by

IBM Systems Director Server:
1. Disable Simple File Sharing. Windows XP targets must have Simple File
Sharing disabled for Agentless managed system discovery to work. Complete
the following steps to disable simple file sharing on the Windows XP system to
be managed:
a. Select Start > Control Panel > Folder Options.
b. In the Folder Options window, click the View tab.
c. In the View panel, scroll to the bottom of the Advanced settings list; then,
clear the Use simple file sharing (Recommended) check box.
d. Click OK.
2. Configure Windows Firewall (Internet Connection Firewall) to allow access by
IBM Systems Director Server. Windows XP (before Service Pack 2) includes a
built-in firewall called Internet Connection Firewall (ICF), which is disabled by
default. Windows XP Service Pack 2 includes Windows Firewall, which is
enabled by default. Either firewall will block attempted accesses by Agentless
managed system discovery unless the firewall is disabled or an exception is
defined for the management server on which IBM Systems Director Server is
installed.
Complete the following steps to enable IBM Systems Director Server to access
the managed system:
a. Select Start > Control Panel > Network Connections > connection. The
connection is the network connection that will be used for discovery.
Typically, this is Local Area Connection.
b. In the General tab of the Connection Status window, click Properties.
c. In the Connection Properties window, click the Advanced tab.
d. In the Advanced panel, click the firewall Settings button.
e. If the firewall is turned off, no further configuration is required. Continue to
step 3 on page 117.

f. If the firewall is enabled, click the Exceptions tab.
g. In the Exceptions panel, select the File and Printer Sharing check box.
h. Click OK.
Note: The network administrator can define a group policy for this
configuration.
3. Verify that remote registry administration is enabled. Remote registry
administration must be enabled in order for Agentless managed system
discovery to run commands and run scripts on the managed system. The
default setting for remote registry administration on Windows systems is
enabled. Complete the following steps to verify or change the remote registry
administration setting:
a. Click Start > Control Panel > System and Maintenance > Administrative
Tools.
b. In the Administrative Tools window, double-click Services.
c. In the list of services in the Services window, right-click the Remote
Registry service and select Properties from the menu.
d. On the General page, set the Startup type to Automatic.
e. If the Service status is not Started, click Start to start the service.
f. Click OK to apply the new settings and close the window.
4. Verify the hidden administrative disk shares such as C$, D$, and so on. The
default hidden administrative disk shares are required for correct operation of
Agentless managed system discovery.
At a command prompt, type net share and press Enter to list the shares
defined on the managed system.
Related reference:

Chapter 4. Uninstalling
Uninstall IBM Systems Director and its components (including the default
database) from your system.
Notes:
v Ensure that you uninstall any IBM Systems Director plug-ins before using these
methods to uninstall IBM Systems Director Server, Common Agent, or Platform
Agent. For information, see the uninstallation instructions provided with each
plug-in.
v Consider retaining the configuration data when you uninstall IBM Systems
Director. This enables you to reinstall or upgrade IBM Systems Director and
access the saved configuration data. Should you reinstall, be sure to reinstall
IBM Systems Director in the same location.
v If you want to change your installation of IBM Systems Director 6.x to a
previous IBM Director 5.20.x version, you need to first uninstall all instances of
Common Agent 6.x and Platform Agent 6.x. This is necessary because IBM
Director Server 5.20.x cannot discover Common Agent 6.x nor Platform Agent
6.x. As a result, the pre-6.x installation will not provide any indication that an
IBM Systems Director 6.x component is present.
Attempting to install an earlier version of Common Agent or Platform Agent
than that which already exists on the system has the potential to cause
problems. Therefore, first uninstall the existing, later version of Common Agent
or Platform Agent before installing the earlier version.
v If you are uninstalling agents on a previously discovered endpoint, you must
discover the endpoint again after you uninstall the agent. Discovering the
endpoint again allows the correct functionality to be reflected in IBM Systems
Director.
Related tasks:
Installing the management server
Preparing agentless managed systems
Installation or uninstallation fails and requires cleanup
Uninstalling IBM Systems Director on Windows

Uninstall IBM Systems Director and its components (including the default
database) by using either the Windows Add or Remove Programs feature or a
command-line prompt. You can use either of these methods to uninstall IBM
Systems Director Server, Common Agent and Platform Agent.

Related tasks:
Uninstalling IBM Systems Director using the Windows Add or

Remove Programs feature
Use the Windows Add or Remove Programs feature to uninstall IBM Systems
Director from Windows.
Note: Only the highest level IBM Systems Director component that is installed is
listed. The highest level component is IBM Systems Director Server, followed by
Common Agent, and then Platform Agent.
Ensure that you uninstall any IBM Systems Director plug-ins before using these
plug-in.
Ensure that any instances of Common Agent or Platform Agent that you uninstall
are not discovered by IBM Systems Director Server. If they are discovered, remove
them from IBM Systems Director Server before you uninstall them.
To uninstall IBM Systems Director using the Windows Add or Remove Programs
feature, complete the following steps:
1. Shut down all applications.
2. Click Start > Settings > Control Panel. The Control Panel window opens.
3. Double-click Add or Remove Programs. The Add or Remove Programs
window opens.
4. Click the IBM Systems Director software component that you want to remove,
and then click Change/Remove. Follow the prompts to uninstall the software
component.
Note: Depending on your operating system version and the components that
you are removing, the uninstallation task might take a long time (up to an
hour) to complete.
5. Remove the TIVguid package if it is not in use by another product. The
TIVguid package is not automatically removed in case it is needed by another
product.
Note: An example of a scenario in which you would leave the TIVguid

package installed is where you already manage a resource with IBM Systems
Director Server and plan to reinstall and continue to manage that resource. IBM
Systems Director Server will use TIVguid to identify the resource instance. If
TIVguid is removed and then the agent is reinstalled, IBM Systems Director
Server will treat the resource as a different system with the same IP address,
which can lead to confusion. Therefore, if you are going through this process of
uninstalling and reinstalling an agent, you should remove the agent from any
management servers that are managing it before performing the uninstallation.

Then perform a rediscovery after the agent has been reinstalled.
If you determine that it is not needed elsewhere, remove it using the Add or
Remove Programs window. You can then remove the following related
directories if you have first ensured that they are empty (other IBM or Tivoli
software that is installed at these locations could be damaged if you remove the
folders):
v Program Files\Common Files\IBM\icc\
v Program Files\IBM\Director\
v Program Files\IBM\tivoli\common\
v Program Files\IBM\tivoli\
v Program Files\tivoli\
v Users\Administrator\AppData\Local\Temp\
v Windows\tivoli\
v Windows\Temp\
v Windows\Temp\eclipse\.update\
v Windows\ServiceProfiles\LocalService\AppData\Local\Temp\
v Program Files\Common Files\InstallShield\
v ipmi\
v LSI\
Log files
The following files might be needed if debugging is necessary for the install or
uninstall process. It is recommended that you keep these files:
v Windows\diragentinst_date_time.log
v Windows\diragentuninst_date_time.log
v Windows\platinst_date_time.log
v Windows\platuninst_date_time.log
v Windows\dirserverinst_date_time.log
v Windows\dirserveruninst_date_time.log
v Windows\dirserver_sysdirremoval.log
v Windows\SoftwareDistribution\DataStore\Logs\edbtmp.log
v Windows\SoftwareDistribution\DataStore\Logs\tmp.edb
Attention: If you plan to uninstall IBM Systems Director and then install an
earlier release of IBM Systems Director, you must remove TIVguid. If you leave
the newer TIVguid on the system, the installation of common agent services
will fail.
6. Restart Windows.
Chapter 4. Uninstalling 121

Related tasks:
Uninstalling using the isduninst command
Uninstalling IBM Systems Director using the isduninst

command
Use the isduninst command to uninstall IBM Systems Director from Windows.
Ensure that you uninstall any IBM Systems Director plug-ins before using these
plug-in.
Ensure that any instances of Common Agent or Platform Agent that you uninstall
are not discovered by IBM Systems Director Server. If they are discovered, remove
them from IBM Systems Director Server before you uninstall them.
Complete the following step to uninstall the IBM Systems Director component that
is running on a Windows system:
1. From a command-line prompt, run the command that applies to the component
that you are removing:
v To uninstall IBM Systems Director Server and any installed IBM Systems
Director plug-ins, type the following command and press Enter:
install_root/bin/isduninst server option
Note: The TIVguid package is not automatically removed in case it is needed

by another product. If you determine that it is not needed elsewhere, remove
it manually.
v To uninstall Common Agent, type the following command and press Enter:
install_root/agent/bin/isduninst agent option
v To uninstall Platform Agent, type the following command and press Enter:
install_root/bin/dirunins platagent option
The following table contains information about values for the option variable.

Table 26. Possible values for isduninst and dirunins options
Variable Parameter What it does
option debug Logs all messages that are sent by the Windows
messages
log=logfilename Specifies the fully qualified name of an alternative
installation log file
noreboot Suppresses any required restart
silent Suppresses all output to the screen
unattended Shows the progress of the uninstallation but does not
require any user input
verbose Enables verbose logging
Note: Depending on your operating system version and the components that
you are removing, the uninstallation task might take a long time (up to an
hour) to complete.
2. Restart Windows.
Related tasks:
Chapter 4. Uninstalling 123

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Dept. LRAS/Bldg. 903
11501 Burnet Road
Austin, TX 78758-3400
U.S.A
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,

modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol (® 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 127

Printed in USA

fqp0 BK Install Server Windows Oracle PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

fqp0 BK Install Server Windows Oracle PDF

Hochgeladen von

Copyright:

Verfügbare Formate

IBM Systems Director

IBM Systems Director

© Copyright IBM Corporation 1999, 2012.

© Copyright IBM Corp. 1999, 2012 iii

Chapter 4. Uninstalling . . . . . . . 119 Notices . . . . . . . . . . . . . . 125

iv Installing on Windows and configuring the Oracle® Database

Conventions and terminology

Note: These notices provide important tips, guidance, or advice.

Attention: These notices indicate possible damage to programs, devices, or data.

Publications and related information

Information centers and topic collections

© Copyright IBM Corp. 1999, 2012 v

vi Installing on Windows and configuring the Oracle® Database

White papers and briefs

IBM Redbooks® publications

About this publication vii

viii Installing on Windows and configuring the Oracle® Database

How to send your comments

About this publication ix

1 Prepare the management server.

© Copyright IBM Corp. 1999, 2012 xi

1 Prepare your managed systems.

© Copyright IBM Corp. 1999, 2012 xiii

Upgrading and migrating Systems Director

Installation and migration troubleshooting

Installing Verify success Configuring after

Installing agents Verify success

© Copyright IBM Corp. 1999, 2012 1

Updating Systems Director

Installing IBM Systems Director Server

2 Installing on Windows and configuring the Oracle® Database

Updating Systems Director

Discovering systems with system discovery

Activating advanced plugins

Systems Director Downloads

Acquiring IBM Systems Director Server

Acquiring an installation DVD

Downloading the installation package

Where installed_files is the path to the extracted installation files.

Preparing the management server

Hardware and software requirements

Supported operating systems

Installation worksheet for the management server

4 Installing on Windows and configuring the Oracle® Database

Choosing the database application

Installation worksheet when using Oracle® Database:

Custom installation worksheet

Table 2. Database configuration information and values

6 Installing on Windows and configuring the Oracle® Database

Use a host name or localhost instead of

Setting the agent manager

Preparing the database application

There is no preparation required to use the system’s default database. However,

8 Installing on Windows and configuring the Oracle® Database

Choosing the database application

Supported operating systems

Database preparation considerations for upgrading and migrating

Preparing the Oracle® Database:

Supported operating systems

Supported database applications

Preparing the database for upgrading and migrating to 6.3

All available ports