Embed Size (px)
Citation preview
IBM Systems Director
Installing IBM Systems Director on Windows andconfiguring an IBM DB2 databaseVersion 6.3
���
IBM Systems Director
Installing IBM Systems Director on Windows andconfiguring an IBM DB2 databaseVersion 6.3
���
NoteBefore using this information and the product it supports, read the information in “Notices” onpage 125.
© Copyright IBM Corporation 1999, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.
Contents
About this publication . . . . . . . . vConventions and terminology . . . . . . . . vPublications and related information . . . . . . vWeb resources . . . . . . . . . . . . . viiiHow to send your comments . . . . . . . . ix
Checklist: Installing IBM SystemsDirector Server . . . . . . . . . . . xi
Checklist: Installing agents . . . . . xiii
Chapter 1. Installing IBM SystemsDirector . . . . . . . . . . . . . . . 1Installation overview . . . . . . . . . . . 1Installing IBM Systems Director Server . . . . . 2
Acquiring IBM Systems Director Server . . . . 3Acquiring an installation DVD . . . . . . 4Downloading the installation package . . . . 4
Preparing the management server . . . . . . 4Installation worksheet for the managementserver. . . . . . . . . . . . . . . 4Preparing the database application . . . . . 9Preparing to install IBM Systems DirectorServer on Windows. . . . . . . . . . 13Preparing firewalls and proxies for IBMSystems Director. . . . . . . . . . . 14Installing firmware and device drivers . . . 15
Running the Pre-Installation Utility (PIU) . . . 19Running the IBM Systems DirectorPre-Installation Utility on the managementserver (Windows) . . . . . . . . . . 20Windows pre-installation checks . . . . . 21
Installing IBM Systems Director on themanagement server. . . . . . . . . . . 27
Installing IBM Systems Director Server onWindows . . . . . . . . . . . . . 27Tips for creating the server response file forIBM Systems Director Server . . . . . . 33
Verifying the successful installation of IBMSystems Director on the management server . . 34Configuring IBM Systems Director Server afterinstallation . . . . . . . . . . . . . 34
Configuring the database for use with IBMSystems Director. . . . . . . . . . . 35Switching the database that IBM SystemsDirector uses . . . . . . . . . . . . 38Database configuration attributes . . . . . 43Tips for database user authorities andpasswords . . . . . . . . . . . . . 52Logging on to IBM Systems Director Serverfor the first time . . . . . . . . . . . 58Restarting IBM Systems Director Server . . . 59Enabling Dynamic IP support . . . . . . 60Configuring IBM Systems Director plug-ins . 62
Configuring the command-line interface . . . 63Reviewing Microsoft Internet Explorer securityoptions . . . . . . . . . . . . . . 64Configuring IP address properties . . . . . 65Changing IBM Systems Director server healthsettings . . . . . . . . . . . . . . 66
Recovering from a failed installation of IBMSystems Director Server 6.3.x . . . . . . . 68
Chapter 2. Installing agents . . . . . . 71Running the Pre-Installation Utility on an agent(Windows). . . . . . . . . . . . . . . 72Installing Common Agent . . . . . . . . . 73
Preparing for a Common Agent managed system 74Obtaining licenses for Common Agent . . . 74Preparing to install Common Agent onWindows . . . . . . . . . . . . . 74
Installing agents using the Agent InstallationWizard . . . . . . . . . . . . . . . 75Installing Common Agent manually . . . . . 78
Installing Common Agent on Windows . . . 79Installing Platform Agent . . . . . . . . . . 86
Preparing for a Platform Agent managed system 87Preparing to install Platform Agent onWindows . . . . . . . . . . . . . 87
Installing agents using the Agent InstallationWizard . . . . . . . . . . . . . . . 88Installing Platform Agent manually . . . . . 91
Installing Platform Agent on Windows . . . 92Verifying the successful installation of an IBMSystems Director agent . . . . . . . . . . 99
Chapter 3. Preparing agentlessmanaged systems . . . . . . . . . 101Preparing to manage service processors with IBMSystems Director . . . . . . . . . . . . 101Preparing to manage an IBM BladeCenter chassisusing IBM Systems Director Server on a non-bladeserver . . . . . . . . . . . . . . . . 108Preparing to manage an IBM BladeCenter chassisusing IBM Systems Director Server on a bladeserver . . . . . . . . . . . . . . . . 109Preparing Windows managed systems . . . . . 111
Preparing Windows Server 2003 managedsystems . . . . . . . . . . . . . . 111Preparing Windows Server 2008 managedsystems . . . . . . . . . . . . . . 112Preparing Windows Vista managed systems . . 112
Preparing to manage an agentless managedsystem running Windows Vista . . . . . 113Preparing a Windows Vista system forPlatform Agent managed systemmanagement. . . . . . . . . . . . 114
© Copyright IBM Corp. 1999, 2012 iii
Preparing a Windows Vista system forCommon Agent managed systemmanagement. . . . . . . . . . . . 115
Preparing Windows XP managed systems . . . 116
Chapter 4. Uninstalling . . . . . . . 119Uninstalling IBM Systems Director on Windows 119
Uninstalling IBM Systems Director using theWindows Add or Remove Programs feature . . 120Uninstalling IBM Systems Director using theisduninst command . . . . . . . . . . 122
Notices . . . . . . . . . . . . . . 125Trademarks . . . . . . . . . . . . . . 127
iv Installing on Windows and configuring an IBM DB2 database
About this publication
This publication provides information about installing IBM® Systems Director forthe first time. It also covers the following topics:v Preparing the server for the installation processv Configuring a database for use with IBM Systems Director Serverv (Optional) Switching the database that IBM Systems Director usesv Activating the advanced plug-ins of IBM Systems Directorv Installing agents and preparing agentless managed systemsv Uninstalling
If you are using a printed version of this information, you might consider printingthe following related PDFs:v IBM Systems Director planning guidev Upgrading and migrating to IBM Systems Director 6.3v Systems management guide
You can access additional information and PDFs from the IBM Systems Directorinformation 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 avoidinconvenient 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 damagecan occur.
Publications and related informationYou can view the same content in the IBM Systems Director Information Center asPDF documents. To view a PDF file, you need Adobe Acrobat Reader, which canbe downloaded for free from the Adobe Web site at http://get.adobe.com/reader/.
Information centers and topic collectionsv IBM Systems
http://publib.boulder.ibm.com/eserver/View the IBM Systems information center landing page, which providesintegrated information for multiple IBM Systems products.
v IBM Systems Directorpublib.boulder.ibm.com/infocenter/director/pubs/index.jspUpdated periodically, the IBM Systems Director topic collection contains themost up-to-date documentation available for IBM Systems Director.
© Copyright IBM Corp. 1999, 2012 v
v IBM Systems Director plug-inshttp://publib.boulder.ibm.com/infocenter/director/pubs/topic/extensions/extensionparent.htmlView the IBM Systems information center for information about how to installand 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.htmlRead the IBM Systems Director Upward Integration Modules (UIM) topiccollection to learn about how to install and use upward integration modules andmanagement packs that enable non-IBM workgroup and enterprise-managementproducts to interpret and display data that is provided by Common Agent andPlatform Agent.
v IBM Systems Director API Licensinghttp://publib.boulder.ibm.com/infocenter/director/devsdk/index.jspView the license information regarding use of IBM Systems Director APIs andtheir associated documentation. Fill out the form to request API access. Afteryour information is reviewed, you will be contacted with additional informationregarding access to and use of the APIs.
Publications
Release Notes 6.3.2Provides an easy reference to planning, install and troubleshootinginformation for IBM Systems Director
IBM Systems Director Planning GuideProvides planning information, including hardware requirements forrunning IBM Systems Director components, supported IBM SystemsDirector hardware, operating systems, databases, and workgroup andenterprise systems-management software.
PDF files for installing IBM Systems Director ServerProvides detailed instructions to prepare for, install, and configure the IBMSystems Director Server.
PDF files for installing IBM Systems Director agentsProvides detailed instructions to prepare for and install IBM SystemsDirector agents on your managed systems, as well as, prepare for agentlessmanaged systems.
PDF files for upgrading and migrating IBM Systems Director ServerProvides detailed instructions to upgrade and migrate the IBM SystemsDirector Server.
PDF files for upgrading and migrating IBM Systems Director agentsProvides detailed instructions to upgrade and migrate IBM SystemsDirector agents.
IBM Systems Director Systems Management GuideProvides detailed instructions for using the Web interface and managingsystems and resources in your environment.
IBM Systems Director Troubleshooting GuideProvides information about problems and how to solve them, andstrategies for troubleshooting common problems.
vi Installing on Windows and configuring an IBM DB2 database
IBM Systems Director Events ReferenceProvides information about IBM Systems Director events, including theevent type, description, severity, and extended details.
IBM Systems Director Commands ReferenceProvides detailed information about the systems managementcommand-line interface (smcli) commands, and other commands that canbe 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 GuideProvides information about installing and using the Hardware CommandLine (formerly known as the IBM Management Processor Command-LineInterface). Command output in this release might vary from commandoutput in previous releases.
White papers and briefsv IBM Systems Director
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/XBW03006USEN.PDFThis paper provides a detailed overview of the changes in IBM Systems DirectorV6.1, including the new Web interface, security features, operating systemagents, integrated plug-ins and additional plug-ins that can be separatelyinstalled.
v Value Proposition for IBM Systems Director
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/XBW03007USEN.PDFThis paper describes the challenges of operational management for enterpriseserver 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 ServerProvides information about how to plan, implement, configure, and use an IBMSystems Director Server to manage a large configuration with optimalperformance. The Performance Tuning and Scaling Guide also containsinformation 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 SystemsDirector and specific IBM hardware; such documents often containsystems-management material. The following book is available for IBM SystemsDirector V6.1:
Implementing IBM Systems Director 6.1
Tip: Be sure to note the date of publication and to determine the version of IBMSystems Director software to which the Redbooks publication refers.
About this publication vii
Further information
See Searching knowledge bases for more resources for further information aboutIBM Systems Director.
Web resourcesListed here are the websites and information center topics that relate to IBMSystems Director.
Websitesv IBM Systems Director
www.ibm.com/systems/management/director/View the IBM Systems Director website on ibm.com® which provides links todownloads and documentation for all currently supported versions of IBMSystems Director.
v IBM Systems Director Downloadswww.ibm.com/systems/management/director/downloads/View the IBM Systems Director Downloads website on ibm.com which provideslinks to download code IBM Systems Director, IBM Systems Director plug-ins,and IBM Systems Director upward integration modules.
v IBM Systems Director Documentation and Resourceswww.ibm.com/systems/management/director/resources/View the IBM Systems Director Documentation and Resources website onibm.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 integrationmodules.
v IBM Systems Director Upward Integrationwww.ibm.com/systems/software/director/downloads/integration.htmlView the IBM Systems Director Upward Integration website on ibm.com whichprovides more information about IBM Systems Director upward integrationmodules that are created by IBM and other companies. IBM Systems DirectorUIMs enable third-party workgroup and enterprise systems-managementproducts to interpret and display data that is provided by IBM Systems DirectorPlatform Agent managed system.
v IBM Systems Director Best Practices Wikiwww.ibm.com/developerworks/wikis/display/WikiPtype/IBM+Systems+Director+Best+Practices+WikiView updated documentation and best practices for IBM Systems Director onvarious systems.
v IBM Serverswww.ibm.com/servers/View the IBM Servers website to learn about IBM Systems server and storageproducts.
v IBM ServerProven®
www.ibm.com/servers/eserver/serverproven/compat/us/View the IBM ServerProven website to learn about hardware compatibility ofIBM System x® and BladeCenter® systems with IBM applications andmiddleware, including IBM Systems Director.
viii Installing on Windows and configuring an IBM DB2 database
Forumsv IBM Systems Director Forum (System x, System z®, Power Systems™)
www.ibm.com/developerworks/forums/forum.jspa?forumID=759View the IBM Systems Director Forum website on ibm.com to discussproduct-related issues that pertain to IBM Systems Director, IBM SystemsDirector UIMs, and IBM Systems Director extensions. This website includes alink for obtaining the forum by using a Rich Site Summary (RSS) feed.
v IBM Systems Director 6.x SDK Forumwww.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0View the IBM Systems Director 6.x SDK Forum website to discuss issues thatpertain to the IBM Systems Director Software Development Kit (SDK). Thiswebsite includes a link for obtaining the forum by using a Rich Site Summary(RSS) feed.
v IBM Systems Forumswww.ibm.com/developerworks/forums/dw_esforums.jspView the IBM Systems Forums website on ibm.com to learn about variousforums that are available to discuss technology-related and product-relatedissues that pertain to IBM Systems hardware and software products. Thiswebsite includes a link for obtaining the forum by using a Rich Site Summary(RSS) feed.
How to send your commentsYour feedback is important in helping to provide the most accurate and highestquality information.
If you have any comments about this book or any other IBM Systems Directorpublication, go to the IBM Systems Director information center Web site atpublib.boulder.ibm.com/infocenter/director/pubs/index.jsp. There you will findthe feedback page where you can enter and submit comments.
About this publication ix
x Installing on Windows and configuring an IBM DB2 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 (9).__ 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 an IBM DB2 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 yourmanaged systems (75).
© Copyright IBM Corp. 1999, 2012 xiii
xiv Installing on Windows and configuring an IBM DB2 database
Chapter 1. Installing IBM Systems Director
If you are installing IBM Systems Director for the first time, use these instructionsto install the latest version on your system.
This procedure assumes that your system has no version of IBM Systems Directoror IBM Director and therefore, there is nothing to upgrade or migrate. If you areupgrading or migrating data from a previous version of IBM Systems Director, seeUpgrading and migrating IBM Systems Director.Related tasks:
Upgrading and migrating Systems DirectorRelated reference:
Installation and migration troubleshooting
Installation overviewBefore you install IBM Systems Director, understand the overall installation processand components.
Installation process
The graphic below illustrates the overall installation process. After you prepareyour existing environment for IBM Systems Director and determine how you planto use the product, you must prepare your system to install the managementserver. There is a Pre-Installation Utility, installation worksheets, and tasks to helpprepare your server for a smooth installation process. Keep in mind this overallflow as you progress through the pre-installation and installation tasks. After youverify that the management server is installed successfully, there are tasks toconfigure the management server and tailor its settings to your needs. Similar tasksare required to install the agent on managed systems.
Prepared environment
Acquiring SystemsDirector
Configuring afterinstallation
Preparing to install
Installingmanagement server
Verify successCheck for updates
Verify successCheck for updates
Installing agents
FM
Q0
55
8-0
After IBM Systems Director is installed and configured for the first time, you cancontinue to discover new systems, collect inventory, and configure plug-ins.
© Copyright IBM Corp. 1999, 2012 1
Inventory
Discovery
ConfigurePlugins
FM
Q0560-0
The base plug-ins in IBM Systems Director provide core function to manage thefull life cycle of IBM servers, storage, network, and virtual servers. Plug-ins thatprovide advanced function or function tailored to a particular environment can bedownloaded and installed on top of IBM Systems Director.
The advanced plug-ins below are automatically installed with IBM SystemsDirector:v Active Energy Managerv Service and Support Managerv 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-insseparately, you must activate Active Energy Manager and IBM Systems DirectorVMControl before using them. For more information about activating or usingthese plug-ins, see Configuring IBM Systems Director plug-ins.
Note: For more information about discovery, inventory, and using the Webinterface, see Publications and related information to access the SystemsManagement guide.Related tasks:Acquiring IBM Systems Director ServerPreparing the management serverRunning the Pre-Installation Utility (PIU)Installing the Systems Director ServerConfiguring after installationVerifying the successful installation of IBM Systems Director on the managementserver
Updating Systems DirectorRelated reference:
PlanningInstallation worksheet for the management server
Installing IBM Systems Director ServerInstalling IBM Systems Director Server requires some preparation.
The following graphic outlines the installation process for IBM Systems DirectorServer. Use the links provided to acquire, prepare for, install, and configure theIBM Systems Director Server.
2 Installing on Windows and configuring an IBM DB2 database
Note: For information about discovery, inventory, and using the Web interface, seePublications and related information to access the Systems Management guide.Related concepts:
System discoveryRelated tasks:
Planning
Updating Systems Director
Discovering systems with system discovery
Activating advanced pluginsLogging on to IBM Systems Director Server for the first timeRelated reference:
Systems Director Downloads
Acquiring IBM Systems Director ServerYou can either download the installation package or acquire an installation DVD.Then, you can use the installation package or DVD to install IBM Systems DirectorServer 6.3.x.
Chapter 1. Installing 3
Related concepts:“Installation overview” on page 1Related reference:
PlanningInstallation worksheet for the management server
Acquiring an installation DVDIf 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 managementserver to IBM Systems Director 6.3.x. For instructions, see “Preparing themanagement server.”
Downloading the installation packageTo download the installation package for installing IBM Systems Director Server,complete the following steps: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 commanddepending on your operating system:v Windows:
unzip
3. If you are using Windows, change to the directory in which the installationscript, dirinstall.server, is located by typing the following command andpressing 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 installthe management server to IBM Systems Director 6.3.x. For instructions, see“Preparing the management server.”
Preparing the management serverBefore installing IBM Systems Director Server, make sure that the requirements thatare applicable to your system have been met.Related reference:
Hardware and software requirements
Supported operating systems
Installation worksheet for the management serverThe installation worksheet describes the properties and parameters required tocomplete the IBM Systems Director Server installation process for a custom
4 Installing on Windows and configuring an IBM DB2 database
installation. Depending on your configuration, you may need to contact yourdatabase 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 themanaged IBM DB2® database. The managed IBM DB2 database is packaged andinstalled with IBM Systems Director Server 6.3.x by default. This database isrecommended if you are installing IBM Systems Director Server for the first timeand do not have an existing database that you intend to use with the IBM SystemsDirector Server. It is installed on the same server as the IBM Systems DirectorServer, does not require an extra license, and is updated as part of any IBMSystems Director Server update.
A custom installation (either using the installation wizard or a response file) allowsyou to use an existing database and configure it for use with the IBM SystemsDirector Server.Related concepts:
Database applicationRelated tasks:
Choosing the database application
Installation worksheet when using IBM DB2:
Use this worksheet to record and plan for a custom IBM Systems Directorinstallation using an IBM DB2 database.
Custom installation worksheet
During the installation process, you can select a basic or custom installation. Unlikea basic installation, the custom installation requires some values that you maywant to acquire before the installation process.
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 portnumber
9510 (default)
Nonstop service ports 9514, 9515 (default)
Agent manager configuration
Select an agent managertype
v Create an agent manager
v Select an existing agentmanager
Create an agent manager (default)
New agent manager configuration
Chapter 1. Installing 5
Table 1. Properties or parameters required during a custom installation process (continued)
Custom installation Your value
Agent manager user name
Agent manager password
Agent registrationpassword
Database type
Select the database youintend to use.Note: The database mustbe installed and configuredon a system in yournetwork.
IBM DB2 databaseNote: See Table 2 for specific database configuration detailsrequired during the installation process
Database administratorcredentials
Administrator name
Administrator password
Web server ports
HTTP port 8421 (default)
HTTP secure port 8422 (default)
Server startup options
v Automatically startserver at the end of theinstallation
v Configure the serverservice as a nonstopserviceNote: Nonstop servicemonitors the IBMSystems Director serverand restarts the server ifit appears to havestopped. It is selected bydefault.
Table 2. Database configuration information and values
DescriptionDatabase configurationattribute Value
Selected database applicationNotes:
v If you want to configure IBM SystemsDirector Server by setting options in adatabase-configuration response file,then the value for DbmsApplicationmust match the database value that youselect.
v You must enter into the cfgdbcmd.rspresponse file the exact value for thedatabase as it appears here.
DbmsApplication DB2
6 Installing on Windows and configuring an IBM DB2 database
Table 2. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
Host name or IP address of the IBM DB2server instanceNote: A IBM DB2 database must always beconsidered remote, even if IBM SystemsDirector Server and IBM DB2 serverinstances reside on the same system.Therefore, a host name or IP address isrequired here.
DbmsServerName Custom value:Examples:
v host1.domain.com
v 127.0.0.1
v localhost
Use a host name or localhost instead ofan IP address for this attribute in thefollowing situations:
v Use localhost if the followingstatements are true:
– You are using a local, non-default,database.
– The IP address of IBM SystemsDirector Server might change in thefuture. For example, the IP address isassigned by using DHCP.
v Use a host name if the IP address of thedatabase server might change in thefuture. For example, the IP address isassigned by using DHCP.
In these situations, if you use an IPaddress, you must manually update all ofthe files that end in database.propertieswith the changed IP address. You mustmake this update each time the IP addresschanges. The files that end indatabase.properties, such asdatabase.properties andaem_database.properties, are located inthe install_root\lwi\conf\overridesdirectory.
Database nameNotes:
v If the database does not exist, then it iscreated later on by the cfgdbcmd task. Ifthe database does exist, then it is used.
v Use a database name and instance namethat do not exceed 8 characters.
DbmsDatabaseName Custom value:Example: DIRDB01
Chapter 1. Installing 7
Table 2. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
Local installation folder in which the IBMDB2 client instance resides
For Windows systems:
v This value must be the fully qualifiedpath name.
v This value is the location of the SQLLIBdirectory. For example, a typicalWindows installation specifies this valueas C:\Program Files\IBM\SQLLIB. Youcan determine theDbmsDatabaseAppHome value byopening an IBM DB2 command windowand specifying DB2SET DB2PATH.
DbmsDatabaseAppHome Custom value:Examples:
v Windows: C:\Program Files\IBM\SQLLIB
Do not include double quotation marksaround the path name.
TCP/IP service port number for the IBMDB2 server instance
On Windows, you can determine theDbmsTcpIpListenerPort value by openingan IBM DB2 command window andspecifying db2 get dbm config . Look forthe value associated with SVCENAME. IfSVCENAME is a number, that is the portnumber. If it is a name (such as db2c_DB2)you must find the name in the services file,which is typically located atC:\WINDOWS\system32\drivers\etc\ onWindows and at /etc on Unix. Inside thatservices file, find the SVCENAME valuethat matches the one returned from the db2get dbm config command. It includes aport number. For example, it might looklike db2c_DB2 50000/tcp, which indicates aport number of 50000.
DbmsTcpIpListenerPort Custom value:Example: 50000
User ID of the database user account thatis used to connect to the databaseNotes:
v Database tables are created under theschema for this user ID.
v If you do not use the databaseadministrator user ID for the runtimeconnection, provide a second user withaccess to the information collectionpanel.
v For detailed information about user IDs,see “Tips for user authorities andpasswords for IBM DB2” on page 53.
DbmsUserId Custom value:Example: myuserid
Password of the database user account
For detailed information about passwords,see “Tips for user authorities andpasswords for IBM DB2” on page 53.
DbmsPassword Custom value:Example: mypwd
8 Installing on Windows and configuring an IBM DB2 database
After you complete the installation worksheet, be sure to prepare your databaseand management server for the installation.Related concepts:
Agent managerRelated tasks:Preparing the database applicationPreparing the management server
Setting the agent manager
Preparing the database applicationPrepare your chosen database for use with IBM Systems Director and configurethem to work together. If you choose to use the default embedded database, thisstep is not necessary.
Ensure that you have chosen the supported database application that you will usewith IBM Systems Director. See “Choosing the IBM Systems Director databaseapplication” for information that helps you decide the database application to use.
The effort required to prepare the database depends on the database applicationthat you choose. Preparation might include one or more of the following tasks:v Downloading and installing the applicable database administrator clientv Downloading and installing the applicable Java™ Database Connectivity (JDBC)
driversv Creating a database or server IDv Configuring and starting a TCP/IP listenerv 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 meetsthe requirements of the default database.
To use a database other than your system's default database with IBM SystemsDirector, follow the steps in the appropriate topic to prepare your databaseapplication.
Note: You can install IBM Systems Director before preparing the database, but youwill only be able to use the default IBM DB2 database until you configure IBMSystems Director Server to use a different database.
After the database application is prepared, you can install IBM Systems DirectorServer and configure it to connect to the database.
Chapter 1. Installing 9
Related concepts:
Database applicationRelated tasks:Configuring the database
Choosing the database applicationRelated reference:
Supported operating systems
Database preparation considerations for upgrading and migrating
smsave command
smrestore commandRunning the Pre-Installation Utility
Preparing IBM DB2:
To use the IBM DB2 database application for IBM Systems Director, you need tocomplete some tasks before installing IBM Systems Director Server. Theseinstructions only apply if you are not using the IBM DB2 application that isprovided, as the default database application, with IBM Systems Director 6.3.
Follow the steps for your operating system to prepare IBM DB2 for use with IBMSystems Director.
Preparing IBM DB2 on Windows:
To use an existing IBM DB2 as the database application for IBM Systems Director,you must complete some tasks to prepare your Windows system before you installIBM Systems Director Server. These instructions only apply if you are not using theIBM DB2 application that is provided, as the default database application, withIBM Systems Director 6.3.
The tasks that you need to complete are grouped into two categories: tasks for theIBM DB2 server, and tasks for the IBM Systems Director server. The IBM SystemsDirector server and IBM DB2 server can reside on two different systems or on thesame system. The tasks are the same and applicable to both scenarios. When onlyone system is used, you must run all the tasks on that system. From theperspective of the IBM Systems Director server, the database connection is alwaysremote and uses the TCP/IP protocol, even if both servers are on the same system.
Note: Do not use IPC to connect to the local IBM DB2 server instance.
10 Installing on Windows and configuring an IBM DB2 database
Related reference:
Supported operating systems
Supported database applications
Preparing the database for upgrading and migrating to 6.3
cfgdbcmd command
All available ports
IBM DB2 Database for Linux, UNIX, and Windows Information Center
Tasks for the IBM DB2 server:To prepare the IBM DB2 server, complete the following tasks before you installIBM Systems Director Server:1. Install the IBM DB2 server. See the IBM DB2 Database for Linux, UNIX, and
Windows Information Center for instructions. See the “Supported databaseapplications” topic for supported versions and installation options.
2. Create an IBM DB2 server instance with TCP/IP support.3. (Optional) Complete the following steps to set DB2_WORKLOAD to TPM on the
newly created IBM DB2 server instance. TPM is a predefined setting that turnson DB2_SKIPINSERTED, DB2_SKIPDELETED, and DB2_EVALUNCOMMITTED. SettingDB2_WORKLOAD to TPM improves concurrency through instance level configurationsettings.
Note: You must run the following commands in CLI command mode, notinteractive mode.a. Ensure that the CLI environment is initialized by running the following
command:
On Windows:db2cmd
Note: Registry keys and values are not case-sensitive.b. Enter the following command to set DB2_WORKLOAD to TPM:
db2set DB2_WORKLOAD=TPM
c. Enter the following command to stop the database instance:db2stop force
d. Enter the following command to restart the database instance:db2start
4. Create, in the same primary group as the IBM DB2 server instance ID, a uniquesystem user ID and password that IBM Systems Director Server uses to connectto this instance. 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 thedatabase administrator ID or password, or any default database user ID orpassword.
Notes:
v If you plan to use Storage Control with IBM Systems Director in the future,you should skip this step. Storage Control requires that IBM SystemsDirector Server be configured with the database administrator user ID andwill not work properly with a user ID with lesser authority.
Chapter 1. Installing 11
v For detailed information about user authorities and passwords, see Tips foruser authorities and passwords for IBM DB2.
v If you plan to use smsave or smrestore with IBM Systems Director Serverand the database, you must ensure that the database instance owner is in thesame primary group as the IBM Systems Director user who performs thebackup and restore operations. This enables the database server to read andwrite the database backup image to the backup directory.
5. Optional: Create the IBM DB2 database that you want IBM Systems Director touse. If the IBM DB2 database is not created, IBM Systems Director will createthis database during the database configuration process. If you pre-create thedatabase, ensure that the IBM DB2 node on your IBM Systems Director Servermachine is catalogued to point at this database.
Tasks for the IBM Systems Director server:To prepare the IBM Systems Director server, complete the following tasks beforeyou install IBM Systems Director Server:1. Install the IBM DB2 client. See the “Supported database applications” topic for
supported versions and installation options.
Note: If the IBM Systems Director server and the IBM DB2 server reside on thesame system, it is possible to use the same IBM DB2 installation for the IBMDB2 server instance and the IBM DB2 client instance, in which case it is notnecessary to install the IBM DB2 Data Server Client separately. However,installing a separate IBM DB2 Data Server Client ensures that you can movethe IBM DB2 server instance to a remote system without affecting the currentIBM Systems Director setup, and that you can apply IBM DB2 patches to theserver or client instance independently.
2. Create an IBM DB2 client instance. If not done, IBM Systems Director does thisinstance for you as part of the database configuration.
3. Ensure that the IBM DB2 administration server is initialized by running thefollowing command:DB2ADMIN START
4. (Optional) Complete the following steps to enable automatic reorganization inIBM DB2.a. In the IBM DB2 Control Center, right-click the database instance that you
want to configure for automatic reorganization and select ConfigureAutomatic Maintenance. The Configure Automatic Maintenance wizard isdisplayed.
b. Click Next.c. Select Change automation settings.d. Click Next. The Specify when automatic maintenance activities can run
page is displayed.e. Next to the On-line maintenance window, click Change.f. Specify a start time of 00:00 and duration of 24.g. Click OK.h. Click Next.i. Click Next. The Select maintenance activity to configure page is displayed.j. In the Automate column, select Reorg and RUNSTATS.k. Click Finish.
12 Installing on Windows and configuring an IBM DB2 database
After you have prepared the IBM DB2 server and client instances for use with IBMSystems Director, you can continue preparing the management server forinstallation. For instructions, see “Preparing the management server” on page 4.
Note: The IBM DB2 Database for Linux, UNIX, and Windows Information Center hascurrent information about security in IBM DB2.
Preparing to install IBM Systems Director Server on WindowsBefore 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 prepareyour 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. Forinstructions, 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, asdescribed in “Hardware and software requirements.”
v If there is an operating system update in progress, ensure that the process iscomplete and you restart the system before starting the IBM Systems Directorinstallation process.
v Systems with service processors: Install the supporting device drivers andmapping layers, if they are not already installed. See “Preparing to manageservice processors with IBM Systems Director” for information about thesedrivers and mapping layers.
v Ensure that the Windows Installer service is enabled. If the Windows Installerservice is not enabled, the installation may fail.
v Before installing IBM Systems Director Server on a system that has IBM StorageConfiguration Manager installed, you must first uninstall IBM StorageConfiguration Manager. After installing IBM Systems Director Server, you canreinstall IBM Storage Configuration Manager on a different system.
v Ensure that the system clocks on the systems that contain IBM Systems DirectorServer and Common Agent remain synchronized.
v Acquire IBM Systems Director Server. You can install IBM Systems DirectorServer from either a downloaded installation package or from an installationDVD. Depending on which method you choose, you must either download theinstallation package or prepare to use the installation DVD. For instructions, seeAcquiring IBM Systems Director Server.
v When you log on to Windows and install IBM Systems Director, the IBMSystems Director service will automatically use your Windows user ID andpassword for interactions between IBM Systems Director Server and its managedresources. If your security policy requires an approved user ID and password forcommunication between IBM Systems Director and its managed resources, youneed to change the IBM Systems Director service to use the secure serviceaccount. To change ownership of the service account after installing IBMSystems 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.
Chapter 1. Installing 13
4. Select This Account and enter the credentials of the service account. Theaccount must have admin rights on all of the managed resources.
v Review the Release Notes® for IBM Systems Director 6.3.2. To view anddownload the Release Notes, see .
After you have prepared your management server, install IBM Systems Director.Related tasks:Acquiring Systems Director ServerRelated reference:
Hardware and software requirements
Supported operating systemsRelated information:
Windows installation troubleshooting
Preparing firewalls and proxies for IBM Systems DirectorYou must configure the firewalls and proxy server to enable installation andoperation of IBM Systems Director if you have firewalls in your network, or if themanagement server must use a proxy server to access the internet.
IBM Systems Director must be able to access all the managed objects in thenetwork, and if you will use a remote Web browser to access the managementserver, the remote systems running the Web browser and the management servermust have access to each other. In addition, some functions of IBM SystemsDirector, including update manager, require access to the Internet.
To enable this access, you must configure firewalls and proxies in your network toallow 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 andCommon Agent are open. See “All available ports” for a complete list of theports that IBM Systems Director components can use.
Note: HTTP port 80 is required to be open for downloading updates usingUpdate Manager.
2. Ensure that internet connections exist to the following internet addresses asthey are required by IBM Systems Director and various plug-ins.
Note: IP addresses are subject to change, so ensure that you use DNS nameswhenever possible.
Table 3. Required internet connections
DNS name IP address Port(s) Protocol(s)
Update manager
www.ibm.com 129.42.56.216,129.42.58.216,129.42.60.216
443 and 80 https and http
www-03.ibm.com 204.146.30.17 443 and 80 https and http
14 Installing on Windows and configuring an IBM DB2 database
Table 3. Required internet connections (continued)
DNS name IP address Port(s) Protocol(s)
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,129.35.224.104
443 and 80 https and http
delivery04-mul.dhe.ibm.com 129.35.224.115,170.225.15.115
443 and 80 https and http
delivery04.dhe.ibm.com 129.35.224.105,170.225.15.105
443 and 80 https and http
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,129.42.34.224,129.42.42.224
443 https
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 havedirect access, complete the following steps to configure the management serverto 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 authenticationwith 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 serverto use the proxy server. See “Changing update settings” for moreinformation.
Related reference:
All available ports
IBM Support Portal
Installing firmware and device driversBefore installing IBM Systems Director on Red Hat Enterprise Linux, SUSE Linux,VMware ESX Server, Windows Server 2003, Windows Server 2008, or WindowsServer 2012 you need to install the latest firmware and device drivers for IBMservice processors, ServeRAID controllers, and IBM adapters such as Brocade andQLogic. To accomplish this, you can either use the IBM UpdateXpress System PackInstaller (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.
Chapter 1. Installing 15
RSA II notes for installing on Linux:
v The RSA II daemon requires the libusb and libusb-devel packages, which aretypically installed by default. If your distribution or installation does not includeor install these packages, you must install them prior to installing the RSA IIdaemon.
v If you are running Linux, the RSA II daemon requires that you configure RSA IIfor “Linux OS” prior to installation. Change this setting through the RSA II Webmanagement interface or through a setting found in the system BIOS setuputility.
To install the latest firmware and device drivers for IBM service processors andServeRAID controllers and ServeRAID Manager plug-ins, use the IBMUpdateXpress System Pack Installer (UXSPi) for the latest UpdateXpress SystemPack (UXSP) that is built for the target systems that you are updating. The UXSPiwill automatically install the latest BIOS, IPMI baseboard management controller(BMC), Remote Supervisor Adapter II (RSA II), ServeRAID, and other firmware asa set, as required for your server. It will also automatically install the requiredIPMI 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 wereincluded in your UXSP are released after you apply the UXSP, do not install thenewer 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 ofa system's level of compliance as determined by rules that you set up in eachcompliance policy. If you utilize compliance policies, it is recommended to basethem on UXSP updates instead of individual driver and firmware updates. Forexample, a recommended compliance policy would stipulate that all of thesystems in your environment should have at least the latest UXSP installed, andan environment that contains the latest UXSP will be considered in compliance.IBM Hardware Support will also consider such an environment as appropriateand fully supported, and PMRs should not require that you apply any furtherupdates to your systems unless a fix is identified in a newer version of anindividual update.
To download the UXSP that contains the needed firmware and drivers for yoursystem, see "IBM Support Portal" and select the appropriate UXSP library.
If you choose to not use the UpdateXpress System Pack Installer, perform thefollowing steps to download and install the latest firmware and device driver filesfor 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 havein your environment.
Notes:
v These steps apply to only Red Hat Enterprise Linux, SUSE Linux, or VMwareESX Server systems, though the steps that are required for Windows systems aresimilar.
v See “Preparing to manage service processors with IBM Systems Director” formore 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 IBMLM78 or SMBus device driver” for information.
16 Installing on Windows and configuring an IBM DB2 database
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 SupportPortal." This file is available for all supported Red Hat Enterprise Linux,SUSE Linux, and VMware ESX Server operating systems, so download theversion 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 availablefor all supported Red Hat Enterprise Linux, SUSE Linux, and VMware ESXServer operating systems, so download the version that applies to yoursystem.
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
commands:tar xzf ibm_svc_rsa2_XXXXXXX_linux_32-64.tgzexport 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 "IBMSupport Portal." This file is available for all supported Red Hat EnterpriseLinux, SUSE Linux, and VMware ESX Server operating systems, sodownload 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
commands:tar xzf ibm_fw_rsa2_XXXXXXX_linux_i386.shexport 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.a. Go to "IBM Support Portal."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.
Chapter 1. Installing 17
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 backupbank" from the list. If you want to update both, click the Add action buttonand 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.14for 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. Forinformation about how to enable the 8.3 short file name support, refer to yourWindows 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 Serverdistributions, but you must download the appropriate device driver foryour particular distribution.
Table 4. Required ServeRAID controller firmware and device driver files
Files (seeKey 1)
RHEL AS 5U1 32-bit
RHEL AS 5U1 64-bit
SLES 932-bit
SLES 964-bit
SLES 1032-bit
SLES 1064-bit
VMwareESX 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 10hardware): ibm_dd_sraidmr_XXXXXXXX_rhel5_32-64.tgz
v 2: ServeRAID MR 10 Device driver (systems with ServeRAID 10hardware): ibm_dd_sraidmr_XXXXXXXX_sles9_32-64.tgz
v 3: ServeRAID MR 10 Device driver (systems with ServeRAID 10hardware): 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
v 6: ServeRAID 8 Device driver (systems with ServeRAID 8 hardware):ibm_dd_aacraid_XXXXXXXXXXX_sles9_32-64.tgz
v 7: ServeRAID 8 Device driver (systems with ServeRAID 8 hardware):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
18 Installing on Windows and configuring an IBM DB2 database
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 installationcommand examples as guides:
Example: ServeRAID 8 on RHEL 5tar xzf ibm_dd_aacraid_1.1.5.2434_sles10_32-64.tgzexport PATH=/usr/local/bin:$PATH ; ./install.sh --update./ibm_XX_aacraid_XXXXXXXXXXX_XXXX_XXX.bin -s
Example: ServeRAID 10 on RHEL 5tar xzf ibm_dd_sraidmr_XXXXXXXX_rhel5_32-64.tgzexport 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.a. Go to "IBM Support Portal."b. Download the following device drivers:
v For the IBM Flex System FC Adapter, download version 3.1.0.0 devicedrivers.
v For the IBM System x HBA cards, download version 3.1.0.0 devicedrivers.
Running the Pre-Installation Utility (PIU)Use the Pre-Installation Utility to ensure that your system meets the IBM SystemsDirector requirements.
The IBM Systems Director Pre-Installation Utility scans the local system to identifypotential problems that might prevent IBM Systems Director from installingsuccessfully. 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 canchoose to run the tool before starting the installation wizard as well. This practiceis a good way to find and fix possible problems in advance.
Note: If you are using a local database, the requirements might be slightly higherthan what is checked by the Pre-Installation Utility. See the hardware requirementstopics for information related to database considerations.
Chapter 1. Installing 19
Related concepts:“Installation overview” on page 1Related tasks:
Preparing to upgrade and migrateRelated reference:
PlanningInstallation worksheet for the management server
Hardware and software requirements
Pre-Installation Utility
Systems Director Downloads
Running the IBM Systems Director Pre-Installation Utility on themanagement server (Windows)To run the IBM Systems Director Pre-Installation Utility on Windows, complete thefollowing steps.
You can obtain or run the Pre-Installation Utility from three locations.
Table 5. Obtaining the Pre-Installation Utility
Location Action
IBM Systems Director 6.3.2 DVD If you do not already have the DVD, youcan burn the image onto DVD from the IBMSystems Director Downloads website.
SysDir_PreInstUtil_6_3_2_Windows.zip Download the Pre-Installation Utilitydirectly from the IBM Systems DirectorDownloads website.
Included in theSysDir6_3_2_Server_Windows.zip file
Download the entire IBM Systems Directorinstallation package from the Downloadswebsite. The Pre-Installation Utility isautomatically started as part of theinstallation process on the managementserver.
Note: The IBM Systems Director downloads website always contains the most recentversion of the Pre-Installation Utility.
1. To start the IBM Systems Director Pre-Installation Utility, choose the applicablemethod:v DVDv Directly from the Pre-Installation Utility downloadv 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
complete the following steps:1) Select your language.2) Click Systems Director Server.
20 Installing on Windows and configuring an IBM DB2 database
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 IBMSystems Director Pre-Installation Utility starts.
v Directly from the Pre-Installation Utility download
a. Extract the contents of the Pre-Installation Utility package, type thefollowing command, and press Enter:unzip SysDir_PreInstUtil_6_3_2_Windows.zip
b. Change to the directory where the Pre-Installation Utility script is locatedby 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 andextracted 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
orlaunchpad64.exe
The IBM Systems Director Welcome window appears.b. On the Welcome window, complete the following steps to start the
Pre-Installation Utility:1) Select your language.2) Click Systems Director Server.3) Click Systems Director Pre-Installation Utility.
2. Reports are generated and results are displayed in the command window orthe default browser. Refer to the \checkds\readme.txt file for more informationabout 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
Systems Director Downloads
Windows pre-installation checksAfter you run the Pre-Installation Utility, you receive a report summarizing theresults of the pre-installation checks performed on your system. Use thisinformation to correct potential problems before installing IBM Systems DirectorServer 6.3.x.
Some of the checks performed by the Pre-Installation Utility include:
Chapter 1. Installing 21
v Runtime authenticationv OS compatibilityv Host architecturev Processorsv Disk space availablev Memory availablev Performance informationv User namev Short namev Paging sizev Managed IBM DB2 prerequisite check
Note:The managed IBM DB2 prerequisite check is available through the installationprocess when installing IBM Systems Director from the DVD or thedownloadable installation package. The managed IBM DB2 prerequisite check isnot 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 beavailable.
Ensure the following ports are available and start the installation process again.
Option Description
Management server The IBM Systems Director installationprocesses and Web server require access to anumber of ports on the management server.If these ports are blocked by a firewall orused by another process, the installationfails. By default, IBM Systems Directorserver requires the following ports:
v 8421
v 8422
v 20000
22 Installing on Windows and configuring an IBM DB2 database
Option Description
Common Agent Ensure that the installation is set to useports that are not already in use. By default,the Common Agent installation processrequires the following ports:
v 9510
v 9514
v 9515
If these ports are already in use when youinstall the agent, the installation fails. Theseports might be in use is if you have adifferent version of the CAS agent installed,for example as part of the TivoliProvisioning Manager agent. Ensure theseports are available and start the installationprocess again.
Platform Agent Ensure that the installation is set to useports that are not already in use. By default,the Platform Agent installation processrequires the following ports:
v 15988
v 15989
v 6989
If these ports are already in use when youinstall the agent, the installation fails.
Related reference:
All available ports
Promotion check:
The promotion check determines whether you can perform an upgrade orpromotion on the system. An upgrade installs a later version of the product. Apromotion 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. Themigration validity check determines whether 6.2.x is installed, and instructs theuser 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 DirectorServer 6.2.x. If the Pre-Installation Utility cannot read existing product data, youreceive 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
Chapter 1. Installing 23
Server 6.2.x. If you do not want to retain previous product files or data, youmight 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 installedand enabled.
If the Pre-Installation Utility detects the Remote Supervisor Adapter II (RSA II) orif it detects RSA II along with IBM Director Core Services 5.20.31 or older, thePre-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 IBMSystems Director Server 6.2.x. If you do not want to migrate existing data, youmight prefer to uninstall an older version and perform a new IBM SystemsDirector Server 6.3 installation.
2. If you uninstall the old version of IBM Systems Director Server, ensure that theRSA 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 yoursystem can resolve its own name and localhost name.
Important: If there is no DNS setting on your Common Agent system, to ensurethat 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 DNSserver IP address to help identify where the communication problem isoccurring.
2. View the IP address and host name information in the /etc/hosts file to ensurethat 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 notvalid for managed IBM DB2. Ensure that your user ID meets the followingrequirements: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
24 Installing on Windows and configuring an IBM DB2 database
ACTION, ACTIVATE, ADD, AFTER, ALIAS, ALL, ALLOCATE, ALLOW,ALTER, AND, ANY, APPEND, AS, ASC, ASENSITIVE, ASSOCIATE, ASUTIME,AT, ATTRIBUTES, AUDIT, AUTHORIZATION, AUX, AUXILIARYB
BEFORE, BEGIN, BETWEEN, BINARY, BIND, BIT, BUFFERPOOL, BYC
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, CYCLED
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, DYNAMICE
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, EXTRACTF
FENCED, FETCH, FIELDPROC, FILE, FINAL, FOR, FOREIGN, FREE,FREEPAGE, FROM, FULL, FUNCTIONG
GBPCACHE, GENERAL, GENERATED, GET, GLOBAL, GO, GOTO, GRANT,GRAPHIC, GROUPH
HANDLER, HASH, HASHED_VALUE, HAVING, HINT, HOLD, HOUR,HOURSI
IDENTITY, IF, IMMEDIATE, IMPLICITLY, IN, INCLUDE, INCLUDING,INCLUSIVE, INCREMENT, INDEX, INDICATOR, INF, INFINITY, INHERIT,INNER, INOUT, INSENSITIVE, INSERT, INTEGRITY, INTERSECT, INTO, IS,ISOBID, ISOLATION, ITERATEJ
JAR, JAVA, JOINK
KEEP, KEYL
Chapter 1. Installing 25
LABEL, LANGUAGE, LATERAL, LC_CTYPE, LEAVE, LEFT, LEVEL2, LIKE,LINKTYPE, LOCAL, LOCALDATE, LOCALE, LOCALTIME,LOCALTIMESTAMP, LOCATOR, LOCATORS, LOCK, LOCKMAX, LOCKSIZE,LOG, LOGGED, LONG, LOOPM
MAINTAINED, MATERIALIZED, MAXVALUE, MICROSECOND,MICROSECONDS, MINPCTUSED, MINUTE, MINUTES, MINVALUE, MIXED,MODE, MODIFIES, MONTH, MONTHSN
NAN, NATIONAL, NCHAR, NCLOB, NEW, NEW_TABLE, NEXTVAL, NO,NOCACHE, NOCYCLE, NODENAME, NODENUMBER, NOMAXVALUE,NOMINVALUE, NONE, NOORDER, NORMALIZED, NOT, NULL, NULLS,NUMPARTS, NVARCHARO
OBID, OF, OLD, OLD_TABLE, ON, OPEN, OPTIMIZATION, OPTIMIZE,OPTION, OR, ORDER, ORGANIZE, OUT, OUTER, OVER, OVERRIDINGP
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, PUBLICQ
QUERY, QUERYNOR
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, RUNS
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_USERT
TABLE, TABLESPACE, TABLESPACES, THEN, TIME, TIMESTAMP, TO,TRANSACTION, TRIGGER, TRIM, TRUNCATE, TYPEU
UNDO, UNION, UNIQUE, UNTIL, UPDATE, USAGE, USER, USINGV
VALIDPROC, VALUE, VALUES, VARIABLE, VARIANT, VCAT, VERSION,VIEW, VOLATILE, VOLUMESW
WHEN, WHENEVER, WHERE, WHILE, WITH, WITHOUT, WLM, WRITEX
26 Installing on Windows and configuring an IBM DB2 database
XMLELEMENT, XMLEXISTS, XMLNAMESPACESY
YEAR, YEARS, YES
Installing IBM Systems Director on the management serverAfter preparing your system, use the IBM Systems Director Server installationprocedure for the operating system on which you plan install IBM SystemsDirector Server.
As part of the installation process, the Pre-Installation Utility runs automatically toensure that your system meets specific requirements. In addition, Service andSupport Manager, Active Energy Manager, and IBM Systems Director VMControlare also installed. However, Active Energy Manager and IBM Systems DirectorVMControl must be activated if you intend to use them.
Note: You are advised to not install IBM Systems Director on the same system asIBM Storage Configuration Manager (SCM).Related tasks:Preparing the management server
Installing IBM Systems Director Server on WindowsAfter preparing your system, you can install IBM Systems Director Server on aWindows system by downloading the installation files from the IBM SystemsDirector support Web site or by using the DVD. You can then perform a standardinstallation or upgrade by using the wizard in a standard interactive mode, or youcan perform an unattended (either with or without status feedback) installation orupgrade by using a response file that automatically provides answers to thequestions that the wizard poses.
Installing IBM Systems Director Server on Windows using the installationwizard:
Use the IBM Systems Director Server installation wizard to install IBM SystemsDirector Server on a system that is running Windows.
The following graphic shows all the components included in the installationpackage.
Management server
Installation includes:- Management Server- Web Interface- Command-line Interface- Common Agent- Platform Agent- Service and Support Manager- Active Energy Manager- VMControl
FQ
M0557-0
When you install IBM Systems Director Server, the installation wizardautomatically installs the necessary components and databases that you choose.
Chapter 1. Installing 27
You can install IBM Systems Director Server on Windows from either installationmedia or from a downloaded installation package.
To install IBM Systems Director Server, log in with an administrator account andcomplete the following steps: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:a. Insert the DVD into the DVD-ROM drive.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. Forinstructions, see “Starting the installation wizard for IBM Systems DirectorServer on Windows by using the keyboard” on page 32.
2. Click Next. The License Agreement page is displayed3. 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 ofsetup screens and IBM Systems Director default settings are used. Theuser ID and password that you enter on the User account page is alsoused for the configuration of the embedded agent manager for theserver.
28 Installing on Windows and configuring an IBM DB2 database
CustomWith custom installation, you are presented with all the setup screensand can change the IBM Systems Director default values, such as whichdatabase application to use, the web server ports, and agent managerconfiguration, as necessary. Use the Custom installation worksheet torecord and collect parameters required during a custom installationprocess.
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 installedon the system, it is installed during the IBM Systems Director Serverinstallation. If the upgrade is necessary, the system prompts you to restartfollowing the installation of IBM Systems Director Server without specifyingthat MSI was installed. You are prompted to restart whether or not the IBMSystems Director Server installation is completed successfully.
After you have installed IBM Systems Director Server, you can start IBM SystemsDirector Server and verify that the installation was successful. For instructions, see“Verifying the successful installation of IBM Systems Director on the managementserver” on page 34.Related tasks:Preparing the management server
Upgrading and migrating Systems Director on Windows using the installationwizardRecovering from a failed installation of IBM Systems Director Server 6.3.xRelated reference:
smstart commandInstallation worksheet for the management server
Systems Director DownloadsRelated information:
Windows installation troubleshooting
Exchanging information with IBM
Performing an unattended or silent installation of IBM Systems Director Serveron 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 DirectorServer by using a response file. This method creates a standard installation file thatcan be used on many systems.
The following graphic shows all the components included in the installationpackage.
Chapter 1. Installing 29
Management server
Installation includes:- Management Server- Web Interface- Command-line Interface- Common Agent- Platform Agent- Service and Support Manager- Active Energy Manager- VMControl
FQ
M0557-0
When you perform an unattended installation of IBM Systems Director Server, theresponse file provides answers to the questions that are posed by the installationwizard.
You can install IBM Systems Director Server on Windows from either installationmedia or from a downloaded installation package.
After the installation process, you can configure a database to use with IBMSystems Director and configure the agent manager.
To use a response file to install IBM Systems Director Server on Windows, log inwith 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 theinstallation:a. Insert the DVD into the DVD-ROM drive.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 forcreating 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 IBMSystems Director Server installation file (IBMSystemsDirectorServerSetup.exeor 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:
installationfileOne of the following installation files:v For a 32 bit system, the installation file is the
IBMSystemsDirectorServerSetup.exe file.
30 Installing on Windows and configuring an IBM DB2 database
v For a 64 bit system, the installation file is theIBMSystemsDirectorServerSetup64.exe file.
installationtypeOne 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.
responsefileThe absolute path and name of the response file that you createdpreviously. For example, c:\myfolder\myresponsefile.rsp. The rspparameter is optional. If you do not include the rsp parameter, theinstaller uses the default response file in the package.
option One of the following optional parameters:
Table 6. Optional installation parameters
Optional parameter What it does
waitforme Ensures that installation processing will not end until thisinstallation is completed.
debug Logs all messages that are sent by the Microsoft WindowsInstaller log engine, including status and informationmessages.
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 DB2password.
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 onWindows using the myresponsefile.rsp response file.
6. If you set the RebootIfRequired parameter to Y in the response file, reboot thesystem if prompted to do so.
Notes:
a. For Windows 2008, Service Pack 1 and earlier, if Microsoft WindowsInstaller (MSI) 4.5 is not installed, then you are prompted to installMicrosoft Windows Installer (MSI) 4.5 and to run the installation programagain 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 installedduring the IBM Systems Director Server installation. If the upgrade of MSIis necessary, the system prompts you to restart following the installation ofIBM Systems Director Server without specifying that MSI was upgraded.Unless you install IBM Systems Director Server by using the response fileand set the RebootIfRequired parameter to N, you are prompted to restartwhether the IBM Systems Director Server installation completessuccessfully.
Chapter 1. Installing 31
7. If you used the DVD for installation, remove the DVD from the drive.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 databasev Custom silent installation with any database other than the managed IBM
DB2 database
For instructions, see Configuring the database for use with IBM SystemsDirector.
9. Run the following command in the \director\bin directory to configure theagent manager:cfgserver.bat -am
10. Run the following command to manually restart the IBM Systems DirectorServer service:net start dirserver
After you have installed IBM Systems Director Server, you can start IBM SystemsDirector Server and verify that the installation was successful. For instructions, see“Verifying the successful installation of IBM Systems Director on the managementserver” on page 34.Related tasks:Preparing the management server
Upgrading and migrating Systems DirectorRecovering from a failed installation of IBM Systems Director Server 6.3.xRelated reference:
smstart command
cfgdbcmd command
smreset command
Systems Director DownloadsRelated information:
Windows installation troubleshooting
Exchanging information with IBM
Starting the installation wizard for IBM Systems Director Server on Windows byusing the keyboard:
Screen readers might not process the IBM Systems Director Setup windowcorrectly when you use a mouse. You can start the installation wizard for IBMSystems Director Server on Windows using the keyboard.
To start the installation wizard for IBM Systems Director Server by using thekeyboard, complete the following steps:1. Open Windows Explorer.2. Browse to the \server\platform directory on the DVD, where platform is i386
or x64.
32 Installing on Windows and configuring an IBM DB2 database
3. Run the IBMSystemsDirectorServerSetup.exe orIBMSystemsDirectorServerSetup64.exe program. The installation wizard starts,and the IBM Systems Director Setup window opens.
Tips for creating the server response file for IBM SystemsDirector ServerYou can use these tips and techniques to modify the sample dirserv.rsp serverresponse file for your IBM Systems Director Server 6.3.2 installation or IBMSystems 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 numbersv Specify the Tivoli Provisioning Manager host name and IP addressv Enable or disable the nonstop service, which keeps the server continuously
runningv Specify a different location from where to install updatesv 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 serverresponse file during the installation or upgrade processes of IBM Systems DirectorServer: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 thevalue blank.
v If you need to enter any Windows-based locations, ensure that you include theback slash after drive_letter. For example, use C:\foldername instead ofC:foldername.
Chapter 1. Installing 33
Related tasks:
Upgrading and migrating Systems DirectorRelated information:
Managed IBM DB2 installation fails
Verifying the successful installation of IBM Systems Directoron the management server
You can verify a successful installation by logging into the Web interface, andverifying the environment variables.
To verify that the installation was successful, complete the following steps:
Log in to the Web interface for IBM Systems Director Server. For instructions, seeLogging on to IBM Systems Director Server for the first time.
After you have verified that the installation was successful, complete the followingtasks: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 StorageConfiguration Manager on a different system.
3. Configure IBM Systems Director plug-ins that were installed with IBM SystemsDirector Server. For instructions, see Configuring IBM Systems Directorplug-ins.
4. You can switch your database to a different database type at any time. Forinstructions, see Switching the database that IBM Systems Director uses.
Configuring IBM Systems Director Server after installationYou might need to configure the database, configure systems, and set up yourenvironment before you start to use IBM Systems Director.
Configure IBM Systems Director Server after a successful installation, so that youcan get the most benefit from the product, and be able to work efficiently. Do notconfuse this task with Configuring Systems, which is a separate topic forconfiguring those resources that are controlled by IBM Systems Director.
The IBM Systems Director home page provides a quick overview, as well as linksto all necessary configuration tasks.
To configure IBM Systems Director, complete the following topics.
34 Installing on Windows and configuring an IBM DB2 database
Related concepts:
The Home pageRelated tasks:Installing IBM Systems Director Server
Upgrading and migrating IBM Systems Director Server
Logging into IBM Systems Director Server
Discovering systems with system discovery
Collecting and viewing inventory data
Configuring the database for use with IBM Systems DirectorComplete this procedure to configure IBM Systems Director to use a non-defaultdatabase if you are installing IBM Systems Director Server 6.3.x.
The following procedure applies to your situation if you are installing IBMSystems 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 Serverv Microsoft SQL Serverv Microsoft SQL Server Expressv 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. Theinstallation program wizard collects the required configuration informationinstead of using the cfgdbcmd.rsp response file.
v If you plan to use the managed IBM DB2 database, you do not need to completethis procedure. IBM Systems Director Server 6.3.x automatically installs andconfigures 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 databaseapplication.
v Verify that there is no other IBM Systems Director Server configured to use thedatabase. Do not configure more than one IBM Systems Director Server to usethe same database.
v Ensure that IBM Systems Director Server is stopped before starting thisprocedure.
Complete the following steps to use the cfgdbcmd.rsp file to configure yourdatabase: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 rootdirectory of your IBM Systems Director installation. For example on Windows,\program files\ibm\director\proddata.
Chapter 1. Installing 35
2. In the cfgdbcmd.rsp file, ensure that the configuration information for yourchosen 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 databaseconfiguration information is commented out using the “;” character before theline and is therefore ignored by IBM Systems Director Server. So, to ensure thatyour chosen database is not commented out, remove the “;” character at thebeginning of each applicable line for your database.
3. Enter information in all of the fields required for your chosen databaseapplication. Do not use any quotes in the response file because they causeerrors during database configuration. For a detailed description and examplesof the required attributes, see “Database configuration attributes” on page 43and 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 ininstall_root\bin, where install_root is the root directory of your IBM SystemsDirector installation. The cfgdbcmd tool uses the cfgdbcmd.rsp response file thatyou previously filled in to properly connect IBM Systems Director Server to thechosen database.
6. Optional: Verify the connection to your database. For instructions, see Verifyinga successful database connection.Attention: Connectivity problems with the database server affect IBM SystemsDirector. For example, if the database server goes offline or becomesunreachable, IBM Systems Director Server stops responding and hangs.
7. After the cfgdbcmd tool completes, run the smreset command located in theinstall_root\bin folder to reinitialize the databases and clear all persistentdata.Attention: If you do not complete this step, IBM Systems Director Server doesnot start correctly.
After the database configuration is complete, return to the point in the installationinstructions for your operating system where you configured the database andfinish installing IBM Systems Director Server 6.3.x. For instructions, see InstallingIBM Systems Director on the management server and select your operating system.
36 Installing on Windows and configuring an IBM DB2 database
Related tasks:Installing IBM Systems Director ServerRelated reference:
cfgdbcmd command
smstop command
smreset command
Supported database applicationsRelated information:
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 theconnection 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 thecfgdbcmd.rsp response file.
Note: If you cannot ping the DbmsServerName, you must investigate andresolve the connectivity issues in your network before you can use IBMSystems 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 theroot directory of your IBM Systems Directorr installation.Alternatively, you can run the following command to verify that themanaged IBM DB2 server is active:smdb status
b. If the managed IBM DB2 server is down, run the following command torestart 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 operatingsystem:v Windows:
db2cmddb2
Chapter 1. Installing 37
b. Run connect to MYDB user MYUSERID using ’MYPASSWORD’.
Note: Where MYDB is the IBM Systems Director database, MYUSERID isthe IBM Systems Director database user ID, and MYPASSWORD is thepassword for the IBM Systems Director database user ID.
4. Microsoft SQL Server: Use a tool similar to Microsoft SQL Server ManagementStudio Express® to connect to the database.
5. For Oracle® Database: To Connect to the Oracle® Database instance locally orfrom 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 administratorv Admin_PW = the Oracle® Database administrator passwordv DB_Name = the name/SID of the database to which you want to connect
If the connection is successful, you receive general information about thedatabase and the verification is complete. If it was unsuccessful, you receivean error. If you receive an error, do one or more of the following actionsand 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 passwordsDatabase configuration attributes
Switching the database that IBM Systems Director usesYou can switch the type of database you are currently using with IBM SystemsDirector 6.3.x from one database type to another at any time.
When you switch your database to the default managed IBM DB2 database, youcan migrate your database data to the managed IBM DB2 database.
When you switch your database to any type of non-default database, you cannotmigrate your database data.Related tasks:
Configuring the database
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 SystemsDirector 6.3.x to IBM DB2, Microsoft SQL Server, Microsoft SQL Server Express, orOracle® Database.
The following procedure applies to your situation if you are currently using IBMSystems Director 6.3.x with some type of existing database. You want to continueto use IBM Systems Director 6.3.x, but switch your database application to one ofthe following database types:
38 Installing on Windows and configuring an IBM DB2 database
v An external IBM DB2 database and not the managed IBM DB2 database that isincluded with IBM Systems Director Server
v Microsoft SQL Serverv Microsoft SQL Server Expressv Oracle® Database
For example, you are currently using Oracle® Database with IBM Systems Director6.3.x and want to use IBM DB2 instead.
If you are switching from managed IBM DB2 to another type of database, managedIBM 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 databaseapplication.
v Verify that there is no other IBM Systems Director Server configured to use thedatabase. Do not configure more than one IBM Systems Director Server to usethe same database.
v Ensure that IBM Systems Director Server is stopped before starting thisprocedure.
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 rootdirectory 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 yourchosen 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 databaseconfiguration information is commented out using the “;” character before theline and is therefore ignored by IBM Systems Director Server. So, to ensure thatyour chosen database is not commented out, remove the “;” character at thebeginning of each applicable line for your database.
3. Enter information in all of the fields required for your chosen databaseapplication. Do not use any quotes in the response file because they causeerrors during database configuration. For a detailed description and examplesof the required attributes, see “Database configuration attributes” on page 43and 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 ininstall_root\bin, where install_root is the root directory of your IBM Systems
Chapter 1. Installing 39
Director installation. The cfgdbcmd tool uses the cfgdbcmd.rsp response file thatyou previously filled in to properly connect IBM Systems Director Server to thechosen database.
6. Optional: Verify the connection to your database. For instructions, see Verifyinga successful database connection.Attention: Connectivity problems with the database server affect IBM SystemsDirector. For example, if the database server goes offline or becomesunreachable, IBM Systems Director Server stops responding and hangs.
7. After the cfgdbcmd tool completes, run the smreset command located in theinstall_root\bin folder to reinitialize the databases and clear all persistentdata.Attention: If you do not complete this step, IBM Systems Director Server doesnot start correctly.
After you finish switching your database application to a different type, completethe 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 removingthe old database that was configured. You can refer to the documentation forthe 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:
Determining your database migration pathRelated reference:
smstop command
smreset command
smstart command
cfgdbcmd command
Supported database applications
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 IBMSystems Director 6.3.x with some type of existing database. You want to continueto use IBM Systems Director 6.3.x, but switch your database application to themanaged 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 DB2database instead.
When you switch your database to the default managed IBM DB2 database, youcan migrate your database data to the managed IBM DB2 database.
40 Installing on Windows and configuring an 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 DB2database: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 DirectorServer is at a version earlier than 6.3.2, you must use the installation packageor installation DVD that you used to install IBM Systems Director. If your IBMSystems Director Server is at version 6.3.2.x or later, you must use the IBMSystems 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 themanaged IBM DB2 database or whether you want to specify customconfiguration 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 configurationattributes for the managed IBM DB2 database” on page 43.
3. Open the cfgdbcmd.rsp file with any text editor. The cfgdbcmd.rsp file islocated in the install_root\proddata directory, where install_root is the rootdirectory of your IBM Systems Director Server installation. For example, onWindows :\program files\ibm\director\prodata.
4. In the cfgdbcmd.rsp file, ensure that the configuration information for themanaged IBM DB2 database is commented correctly:v Ensure that the information for the managed IBM DB2 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 databaseconfiguration information is commented out using the “;” character before theline and is therefore ignored by IBM Systems Director Server. So, to ensure thatthe managed IBM DB2 database is not commented out, remove the “;”character at the beginning of each applicable line for the managed IBM DB2database.
5. Enter information in all of the fields required for the managed IBM DB2database. Do not use any quotes in the response file because they cause errorsduring database configuration. For a detailed description and examples of therequired attributes, see “Database configuration attributes for the managed IBMDB2 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\db2v 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:
Chapter 1. Installing 41
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 rspfilelocationrspfilelocation is the path to the location of the cfgdbcmd.rsp file. Youmust specify this option if one or more of the following situations aretrue:v You decided to specify custom configuration attributes in step 2 on
page 41. If you do not specify this option, the command uses thedefault cfgdbcmd.rsp file instead of the file that you customized.
v You saved the cfgdbcmd.rsp file to a non-default location in Step 6on page 41.
-noPromptSpecify this option if you want to install the managed IBM DB2database in silent mode. If you decided to use the default configurationattributes in step 2 on page 41, this option automatically uses thedefault configuration attributes and does not prompt you forconfirmation.
-dbMigrate valueYou 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 loseyour data. The command resets your database to an empty databasewith no contents.
If you do not specify this option, the command automatically migratesyour existing database data to the managed IBM DB2 database.
-dbIgnorePrereqs valueYou 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 IBMDB2 database.
-dbPort port_numberport_number is the port number that you want the managed IBM DB2database to use. When you specify this option, it overrides the defaultport value and it overrides the port value specified in the cfgdbcmd.rspfile.
After you finish switching your database application to the managed IBM DB2database, 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 removingthe old database that was configured. You can refer to the documentation forthe specific database application for information about how to do that.
42 Installing on Windows and configuring an IBM DB2 database
Related concepts:
Database applicationRelated tasks:
Determining your database migration pathRelated reference:
smstop command
smstart command
Supported database applications
Database configuration attributesYou can learn about the database configuration attributes that must be set in thecfgdbcmd.rsp response file in order to configure the database.Related tasks:
Configuring the database
Switching the databaseRelated reference:Tips for database user authorities and passwords
Database configuration attributes for the managed IBM DB2 database:
There are database configuration attributes that must be set in the cfgdbcmd.rspresponse file in order to switch your database type to the managed IBM DB2database. This information applies only to the managed IBM DB2 database that isprovided with IBM Systems Director 6.3 and not to external IBM DB2 databases.
Database configuration attributes
The following table lists the database configuration attributes for the managed IBMDB2 database, a description of each attribute, and an example of each attribute.
Table 7. Database configuration information and values
DescriptionDatabase configurationattribute Value
Selected database application DbmsApplication Managed DB2
Host name or IP address of the IBM DB2server instance
DbmsServerName localhost
Location for the managed IBM DB2instance.
For Windows, you must specify a driveletter.
DbmsDatabaseHome Default value:
v Windows: C:\DIRINST1
Custom value:Examples:
v Windows: C
Do not include double quotation marksaround the path name.
Chapter 1. Installing 43
Table 7. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
TCP/IP service port number for themanaged IBM DB2 server instance
DbmsTcpIpListenerPort Default value: 50010
Custom value: You can specify a port thatis available and not in use.
Password of the database user account
For detailed information about passwords,see “Tips for user authorities andpasswords for the managed IBM DB2database” on page 52.
DbmsPassword Default value: Leave this attribute blank.
When you leave this attribute blank, IBMSystems Director automatically generates apassword for you.
Custom value:Example: mypwd
Example cfgdbcmd.rsp file for WindowsDbmsApplication = Managed DB2DbmsTcpIpListenerPort = 50010DbmsServerName = localhostDbmsDatabaseHome = CDbmsPassword = mypwd
Related concepts:
Database applicationRelated tasks:
Determining your database migration path
Switching to the managed IBM DB2 database
Database configuration attributes for IBM DB2:
There are database configuration attributes that must be set in the cfgdbcmd.rspresponse file in order to configure the IBM DB2 database. This information appliesonly to external IBM DB2 databases and not to the managed IBM DB2 databasethat is provided with IBM Systems Director 6.3.
Database configuration attributes
The following table lists the database configuration attributes for IBM DB2, adescription of each attribute, and an example of each attribute.
44 Installing on Windows and configuring an IBM DB2 database
Table 8. Database configuration information and values
DescriptionDatabase configurationattribute Value
Selected database applicationNotes:
v If you want to configure IBM SystemsDirector Server by setting options in adatabase-configuration response file,then the value for DbmsApplicationmust match the database value that youselect.
v You must enter into the cfgdbcmd.rspresponse file the exact value for thedatabase as it appears here.
DbmsApplication DB2
Host name or IP address of the IBM DB2server instanceNote: A IBM DB2 database must always beconsidered remote, even if IBM SystemsDirector Server and IBM DB2 serverinstances reside on the same system.Therefore, a host name or IP address isrequired here.
DbmsServerName Custom value:Examples:
v host1.domain.com
v 127.0.0.1
v localhost
Use a host name or localhost instead ofan IP address for this attribute in thefollowing situations:
v Use localhost if the followingstatements are true:
– You are using a local, non-default,database.
– The IP address of IBM SystemsDirector Server might change in thefuture. For example, the IP address isassigned by using DHCP.
v Use a host name if the IP address of thedatabase server might change in thefuture. For example, the IP address isassigned by using DHCP.
In these situations, if you use an IPaddress, you must manually update all ofthe files that end in database.propertieswith the changed IP address. You mustmake this update each time the IP addresschanges. The files that end indatabase.properties, such asdatabase.properties andaem_database.properties, are located inthe install_root\lwi\conf\overridesdirectory.
Database nameNotes:
v If the database does not exist, then it iscreated later on by the cfgdbcmd task. Ifthe database does exist, then it is used.
v Use a database name and instance namethat do not exceed 8 characters.
DbmsDatabaseName Custom value:Example: DIRDB01
Chapter 1. Installing 45
Table 8. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
Local installation folder in which the IBMDB2 client instance resides
For Windows systems:
v This value must be the fully qualifiedpath name.
v This value is the location of the SQLLIBdirectory. For example, a typicalWindows installation specifies this valueas C:\Program Files\IBM\SQLLIB. Youcan determine theDbmsDatabaseAppHome value byopening an IBM DB2 command windowand specifying DB2SET DB2PATH.
DbmsDatabaseAppHome Custom value:Examples:
v Windows: C:\Program Files\IBM\SQLLIB
Do not include double quotation marksaround the path name.
TCP/IP service port number for the IBMDB2 server instance
On Windows, you can determine theDbmsTcpIpListenerPort value by openingan IBM DB2 command window andspecifying db2 get dbm config . Look forthe value associated with SVCENAME. IfSVCENAME is a number, that is the portnumber. If it is a name (such as db2c_DB2)you must find the name in the services file,which is typically located atC:\WINDOWS\system32\drivers\etc\ onWindows and at /etc on Unix. Inside thatservices file, find the SVCENAME valuethat matches the one returned from the db2get dbm config command. It includes aport number. For example, it might looklike db2c_DB2 50000/tcp, which indicates aport number of 50000.
DbmsTcpIpListenerPort Custom value:Example: 50000
User ID of the database user account thatis used to connect to the databaseNotes:
v Database tables are created under theschema for this user ID.
v If you do not use the databaseadministrator user ID for the runtimeconnection, provide a second user withaccess to the information collectionpanel.
v For detailed information about user IDs,see “Tips for user authorities andpasswords for IBM DB2” on page 53.
DbmsUserId Custom value:Example: myuserid
Password of the database user account
For detailed information about passwords,see “Tips for user authorities andpasswords for IBM DB2” on page 53.
DbmsPassword Custom value:Example: mypwd
46 Installing on Windows and configuring an IBM DB2 database
Example cfgdbcmd.rsp file for WindowsDbmsApplication = DB2DbmsTcpIpListenerPort = 50000DbmsServerName = 10.9.1.2DbmsDatabaseName = dirdbDbmsUserId = myuseridDbmsPassword = mypwdDbmsDatabaseAppHome = C:\Program Files\IBM\SQLLIB
Related tasks:
Configuring the database
Switching the database
Enabling Dynamic IP support
Database configuration attributes for Microsoft SQL Server and Microsoft SQLServer Express:
There are database configuration attributes that must be set in the cfgdbcmd.rspresponse file in order to configure the Microsoft SQL Server database and theMicrosoft SQL Server Express database.
Database configuration attributes
The following table lists the database configuration attributes for Microsoft SQLServer and Microsoft SQL Server Express, a description of each attribute, and anexample of each attribute.
Table 9. Database configuration information and values
DescriptionDatabase configurationattribute Value
Selected database applicationNotes:
v If you want to configure IBM SystemsDirector Server by setting options in adatabase-configuration response file,then the value for DbmsApplicationmust match the database value that youselect.
v You must enter into the cfgdbcmd.rspresponse file the exact value for thedatabase as it appears here.
DbmsApplication SQLServer
Chapter 1. Installing 47
Table 9. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
Host name of the server on which thedatabase is installed
Optional: You can include theDbmsInstanceName with theDbmsServerName in the form ofDbmsServerName\DbmsInstanceName.
DbmsServerName Custom value:Examples:
v 10.9.1.1
v MyServer
v localhost
Use a host name or localhost instead ofan IP address for this attribute in thefollowing situations:
v Use localhost if the followingstatements are true:
– You are using a local, non-default,database.
– The IP address of IBM SystemsDirector Server might change in thefuture. For example, the IP address isassigned by using DHCP.
v Use a host name if the IP address of thedatabase server might change in thefuture. For example, the IP address isassigned by using DHCP.
In these situations, if you use an IPaddress, you must manually update all ofthe files that end in database.propertieswith the changed IP address. You mustmake this update each time the IP addresschanges. The files that end indatabase.properties, such asdatabase.properties andaem_database.properties, are located inthe install_root\lwi\conf\overridesdirectory.
Database name DbmsDatabaseName Custom value:Examples:
v DIRDB
v MyDatabase
Note: This value must match the name ofthe database that is created in the chosendatabase application.
Instance name of the database that isapplicable only if a non-default instance isused
DbmsInstanceName Custom value:Examples:
v MyInstance
v If you have only one instance ofMicrosoft SQL Server or Microsoft SQLServer Express, you do not need to setthis attribute.
v If you specified the instance name withthe DbmsServerName attribute, you canleave this attribute blank.
48 Installing on Windows and configuring an IBM DB2 database
Table 9. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
Fully qualified local installation folder ofthe database server instance or adminclient instance on the IBM Systems DirectorServer systemNote: This value is the location of theJDBC driver, sqljdbc4.jar. For example, atypical Windows installation specifies thisvalue as C:\PROGRA~1\MICROS~4\sqljdbc_4.0\enu or C:\Downloads\SQLJDBC\extract\sqljdbc_4.0\enu.
DbmsDatabaseAppHome Custom value:Examples:
v C:\sqljdbc2\sqljdbc_4.0\enu
v C:\Program Files\Microsoft SQL ServerJDBC Driver 4.0\sqljdbc_4.0\enu
Do not include double quotation marksaround the path name.
TCP/IP listener port ID for the database DbmsTcpIpListenerPort Default or custom value:Example: 1433
Whether IBM Systems Director is toconnect to the Microsoft SQL Serverdatabase by using Windows authentication(“true”) or Microsoft SQL Serverauthentication (“false”)Notes:
v For IBM Systems Director version 6.2.0and previous versions, the Windowsauthentication option is supported onlywhen Microsoft SQL Server is installedon the same system as IBM SystemsDirector.
v If DbmsIntegratedSecurity is set to“false”, then Microsoft SQL Server mustbe configured with mixed modeauthentication.
v For detailed information about user IDsand passwords, see “Tips for userauthorities and passwords for MicrosoftSQL Server and Microsoft SQL ServerExpress” on page 55.
DbmsIntegratedSecurity __ v true__ v false
Examples:
v Microsoft SQL Server authentication:false
v Windows authentication: true
User ID of the database user accountNotes:
v It is recommended that you choose adifferent database user ID than thedatabase administrator user ID. Thedatabase user does not need as muchauthority to the database as the databaseadministrator user.
v For detailed information about user IDs,see “Tips for user authorities andpasswords for Microsoft SQL Server andMicrosoft SQL Server Express” on page55.
DbmsUserId Custom value:Example: myuserid
Password of the database user account
For detailed information about passwords,see “Tips for user authorities andpasswords for Microsoft SQL Server andMicrosoft SQL Server Express” on page 55.
DbmsPassword Custom value:Example: mypwd
Chapter 1. Installing 49
Example cfgdbcmd.rsp file for Microsoft SQL Server authenticationDbmsApplication = SQLServerDbmsTcpIpListenerPort = 1433DbmsServerName = 10.9.1.1DbmsDatabaseName = DIRDBDbmsInstanceName = MyInstanceDbmsUserId = myuseridDbmsPassword = mypwdDbmsDatabaseAppHome = C:\sqljdbc2\sqljdbc_4.0\enuDbmsIntegratedSecurity = false
Example cfgdbcmd.rsp file forWindows authenticationDbmsApplication = SQLServerDbmsTcpIpListenerPort = 1433DbmsServerName = MyServer\MyInstanceDbmsDatabaseName = DIRDBDbmsUserId =DbmsPassword =DbmsDatabaseAppHome = C:\sqljdbc2\sqljdbc_4.0\enuDbmsIntegratedSecurity = true
Example cfgdbcmd.rsp file forWindows authentication for remote Microsoft SQLServerDbmsApplication = SQLServerDbmsTcpIpListenerPort = 1433DbmsServerName = MyServerDbmsDatabaseName = MyDatabaseDbmsInstanceName = MyInstanceDbmsUserId =DbmsPassword =DbmsDatabaseAppHome = C:\Program Files\Microsoft SQL Server JDBC Driver 4.0 /\sqljdbc_4.0\enuDbmsIntegratedSecurity = true
Related tasks:
Configuring the database
Switching the database
Enabling Dynamic IP support
Database configuration attributes for Oracle® Database:
There are database configuration attributes that must be set in the cfgdbcmd.rspresponse file in order to configure the Oracle® Database.
Database configuration attributes
The following table lists the database configuration attributes for Oracle® Database,a description of each attribute, and an example of each attribute.
50 Installing on Windows and configuring an IBM DB2 database
Table 10. Database configuration information and values
DescriptionDatabase configurationattribute Value
Selected database applicationNotes:
v If you want to configure IBM SystemsDirector Server by setting options in adatabase-configuration response file,then the value for DbmsApplicationmust match the database value that youselect.
v You must enter into the cfgdbcmd.rspresponse file the exact value for thedatabase as it appears here.
DbmsApplication Oracle
Host name of the server on which thedatabase is installed
DbmsServerName Custom value:Examples:
v 10.0.0.72
v MyServer
v localhost
Use a host name or localhost instead ofan IP address for this attribute in thefollowing situations:
v Use localhost if the followingstatements are true:
– You are using a local, non-default,database.
– The IP address of IBM SystemsDirector Server might change in thefuture. For example, the IP address isassigned by using DHCP.
v Use a host name if the IP address of thedatabase server might change in thefuture. For example, the IP address isassigned by using DHCP.
In these situations, if you use an IPaddress, you must manually update all ofthe files that end in database.propertieswith the changed IP address. You mustmake this update each time the IP addresschanges. The files that end indatabase.properties, such asdatabase.properties andaem_database.properties, are located inthe install_root\lwi\conf\overridesdirectory.
Database name DbmsDatabaseName Custom value:Example: mydatabaseNote: This value must match the name ofthe database that is created in the chosendatabase application.
Chapter 1. Installing 51
Table 10. Database configuration information and values (continued)
DescriptionDatabase configurationattribute Value
Fully qualified local installation folder ofthe database server instance or adminclient instance on the IBM Systems DirectorServer system
DbmsDatabaseAppHome Custom value:Example: c:\oracle\product\10.2.0\client_1
Do not include double quotation marksaround the path name.
TCP/IP listener port ID for the database DbmsTcpIpListenerPort Default or custom value:Example: 1521
User ID of the database user account
For detailed information about user IDs,see “Tips for user authorities andpasswords for Oracle® Database” on page56.
DbmsUserId Custom value:Example: myuserid
Password of the database user account
For detailed information about passwords,see “Tips for user authorities andpasswords for Oracle® Database” on page56.
DbmsPassword Custom value:Example: mypwd
Example cfgdbcmd.rsp file for WindowsDbmsApplication = OracleDbmsTcpIpListenerPort = 1521DbmsServerName = 10.0.0.72DbmsDatabaseName = mydatabaseDbmsUserId = myuseridDbmsPassword = mypwdDbmsDatabaseAppHome = c:\oracle\product\10.2.0\client_1
Related tasks:
Configuring the database
Switching the database
Enabling Dynamic IP support
Tips for database user authorities and passwordsUse these tips and techniques to configure, manage, and troubleshoot userauthorities and passwords for your database application.Related tasks:
Configuring the database
Switching the databaseRelated reference:Database configuration attributes
Tips for user authorities and passwords for the managed IBM DB2 database:
Use these tips and techniques to configure, manage, and troubleshoot userauthorities and passwords for the managed IBM DB2 database.
52 Installing on Windows and configuring an IBM DB2 database
Default user ID and password
IBM Systems Director automatically creates the user ID of the database systemadministrator. The default user ID is dirinst1.
When you initially configure the managed IBM DB2 database, you can specify thepassword for the dirinst1 user ID. Depending on your operating system, you canspecify 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 databaseadministrator:! % ^ & ( ) | " ’ ? , < >
If you use any of these characters, the database connection between IBM SystemsDirector Server and the database fails.
If you do not specify a password during the initial configuration, IBM SystemsDirector automatically generates the password for the dirinst1 user ID.
After installation or migration, you can change the password by using thechangePassword command.Related concepts:
Database applicationRelated tasks:
Switching to the managed IBM DB2 databaseRelated reference:
cfgdbcmd command
changePassword toolDatabase configuration attributes for the managed IBM DB2 database
Tips for user authorities and passwords for IBM DB2:
Use these tips and techniques to configure, manage, and troubleshoot userauthorities and passwords for the IBM DB2 database.
IBM Systems Director grants dbadm authority to the IBM Systems Director databaseuser ID. The IBM Systems Director database user ID is the user ID specified in theDbmsUserID configuration attribute in the cfgdbcmd.rsp file. One exception is whenthe -dbAdmin user ID is the same as the DbmsUserID user ID. In this case, IBMSystems Director assumes that the user ID already has the required level ofauthority.
Do not use the database user ID dirinst1. This user ID is reserved for themanaged IBM DB2 database that is installed with IBM Systems Director Server.
Do not use any of the following characters in the password of the databaseadministrator:
Chapter 1. Installing 53
! % ^ & ( ) | " ’ ? , < >
If you use any of these characters, the database connection between IBM SystemsDirector Server and the database fails.
If you are using Storage Control, the IBM Systems Director database user ID mustbe the same as the database administrator ID. In other words, the value for theDbmsUserID 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 youspecify 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 theDbmsUserId database configuration attribute in the cfgdbcmd.rsp file. The -dbAdminparameter specifies the ID of the instance owner so that the cfgdbcmd tool has theauthority to create a database. The DbmsUserId database configuration attributespecifies 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 theDbmsPassword database configuration attribute in the cfgdbcmd.rsp file. The-dbAdminPW parameter specifies the password of the instance owner so that thecfgdbcmd tool has the authority to create a database. The DbmsPassword databaseconfiguration attribute specifies the password that IBM Systems Director uses tostore data in the database.
Do not specify the same user ID in the cfgdbcmd.rsp configuration file as isspecified in the -dbAdmin parameter to the cfgdbcmd tool. Doing so might result inan error or in having the administrator authority of the user revoked. If youmistakenly used this configuration in the past, you might need to grantadministrator 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 thesmrestore command, you enter the user ID and password of the database systemadministrator 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 tospecify a value.
54 Installing on Windows and configuring an IBM DB2 database
Related tasks:
Configuring the database
Switching the databaseRelated reference:
cfgdbcmd command
smsave command
smrestore commandDatabase configuration attributes for IBM DB2
Tips for user authorities and passwords for Microsoft SQL Server and MicrosoftSQL Server Express:
Use these tips and techniques to configure, manage, and troubleshoot userauthorities and passwords for Microsoft SQL Server and Microsoft SQL ServerExpress.
Integrated security
If you use integrated security (DbmsIntegratedSecurity=true), IBM SystemsDirector connects to the database by using the Windows user ID.
If you do not use integrated security (DbmsIntegratedSecurity=false), IBMSystems Director connects to the database by using the user ID and password thatyou specify in the cfgdbcmd.rsp file. You specify the user ID in the DbmsUserIdconfiguration attribute and you specify the password in the DbmsPasswordconfiguration attribute.
User ID roles and authorities
If IBM Systems Director creates the user ID of the database system administratorduring the installation process, IBM Systems Director automatically assigns thedb_owner role to the user ID.
If you create the user ID of the database system administrator before you configurethe 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 listof authorities and roles applies to the Windows user ID.
The cfgdbcmd tool
The cfgdbcmd tool automatically encrypts the database user password that youspecify in the cfgdbcmd.rsp file.
Chapter 1. Installing 55
Differences between user ID and password parameters, configuration attributes,and arguments
If you do not use integrated security (DbmsIntegratedSecurity=false):v The -dbAdmin parameter for the cfgdbcmd tool serves a different purpose than the
DbmsUserId database configuration attribute in the cfgdbcmd.rsp file. The-dbAdmin parameter specifies the user ID for the database system administrator.The DbmsUserId database configuration attribute specifies the user ID that IBMSystems Director uses to store data in the database.
v The -dbAdminPW parameter for the cfgdbcmd tool serves a different purpose thanthe DbmsPassword database configuration attribute in the cfgdbcmd.rsp file. The-dbAdminPW parameter specifies the password for the database systemadministrator. The DbmsPassword database configuration attribute specifies thepassword 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 isspecified in the -dbAdmin parameter to the cfgdbcmd tool. Doing so might resultin an error or in having the administrator authority of the user revoked. If youmistakenly used this configuration in the past, you might need to grantadministrator authority again to this user ID after the cfgdbcmd command runs.
v When you back up and restore the database by using the smsave command andthe smrestore command, you enter the user ID and password of the databasesystem administrator as follows:– You enter the user ID of the database system administrator in the -dbUserName
argument.– You enter the password of the database system administrator in the
-dbUserPwd argument.
If you do not specify a value for these arguments, the commands prompt you tospecify a value.
If you use integrated security (DbmsIntegratedSecurity=true):v You do not need to specify -dbAdmin and -dbAdminPW parameters when using the
cfgdbcmd command.v You do not need to specify the -dbUserName argument and the -dbUserPwd
argument when using the smsave command and the smrestore command.v You do not need to specify the DbmsUserId configuration attribute and the
DbmsPassword configuration attribute in cfgdbcmd.rsp file.Related tasks:
Configuring the database
Switching the databaseRelated reference:
cfgdbcmd command
smsave command
smrestore commandDatabase configuration attributes for Microsoft SQL Server and Microsoft SQLServer Express
Tips for user authorities and passwords for Oracle® Database:
56 Installing on Windows and configuring an IBM DB2 database
Use these tips and techniques to configure, manage, and troubleshoot userauthorities and passwords for Oracle® Database.
The user ID of the database system administrator must be granted the adminoption to the database.
The user ID uses the default table space called users and the temporary tablespace called temp. If you receive errors while running the smreset command tocreate 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 thedatabase system administrator:v create any tablev alter any tablev delete any tablev drop any tablev insert any tablev lock any tablev select any tablev update any tablev create any indexv alter any indexv drop any indexv create viewv create any procedurev alter any procedurev drop any procedurev execute any procedure
The cfgdbcmd tool
If you create the user ID before you run the cfgdbcmd command, the cfgdbcmdcommand uses the user ID that you create. The cfgdbcmd command does not deletethe user ID and create a new one.
The cfgdbcmd tool automatically encrypts the database user password that youspecify 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 theDbmsUserId database configuration attribute in the cfgdbcmd.rsp file. The -dbAdminparameter specifies the user ID for the database system administrator. TheDbmsUserId database configuration attribute specifies the user ID that IBM SystemsDirector uses to store data in the database.
The -dbAdminPW parameter for the cfgdbcmd tool serves a different purpose than theDbmsPassword database configuration attribute in the cfgdbcmd.rsp file. The-dbAdminPW parameter specifies the password for the database systemadministrator. The DbmsPassword database configuration attribute specifies thepassword that IBM Systems Director uses to store data in the database.
Chapter 1. Installing 57
Do not specify the same user ID in the cfgdbcmd.rsp configuration file as isspecified in the -dbAdmin parameter to the cfgdbcmd tool. Doing so might result inan error or in having the administrator authority of the user revoked. If youmistakenly used this configuration in the past, you might need to grantadministrator 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 thesmrestore command, you enter the user ID and password of the database systemadministrator 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 tospecify a value.Related tasks:
Configuring the database
Switching the databaseRelated reference:
cfgdbcmd command
smsave command
smrestore command
smreset commandDatabase configuration attributes for Oracle® Database
Logging on to IBM Systems Director Server for the first timeAfter installing IBM Systems Director Server, you need to log on using a Webbrowser, update IBM Systems Director Server, discover managed systems, andrequest access to those managed systems.
You must already have installed and started IBM Systems Director Server beforebeginning 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 SystemsDirector Server is installed and Port_Number is the first (lower) of twoconsecutive port numbers that you specified for the Web server to use. Thedefault 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 IBMSystems Director administrator user ID and password. Authorizedadministrator credentials include credentials for the root user or any userthat is a member of the smadmin group.
58 Installing on Windows and configuring an IBM DB2 database
Note: The first time you log in, use the administrator user ID that you usedduring the installation or the root user. After this initial login, you can addother users to the smadmin group.
c. Click Log in.
Note: A security alert window might be displayed before logging in. This isdue to incorrect configuration of the Secure Sockets Layer (SSL) certificate.For information see “Configuring Secure Sockets Layer (SSL) between IBMSystems 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 discoveryRelated tasks:Installing IBM Systems Director Server
Authenticating users
Updating IBM Systems Director
Managing access
Collecting inventory
Restarting IBM Systems Director ServerRestarting IBM Systems Director Server requires that you run one command tostop the management server processes and then run another command to startthem again.
Before you stop the IBM Systems Director Server, warn users to finish their workor 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 IBMSystems 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 startdirserver.
3. Check to ensure that the IBM Systems Director Server started successfully.v If you are running Windows, check the status of the server by checking the
system tray.
Chapter 1. Installing 59
Related tasks:“Enabling Dynamic IP support”“Changing IBM Systems Director server health settings” on page 66Related reference:
smstart command
smstatus command
smstop command
Enabling Dynamic IP supportEnabling the Dynamic IP support feature automatically reconfigures IBM SystemsDirector Server and notifies the managed resources of the IP address change if theIP address of the system running IBM Systems Director Server changes.
In IBM Systems Director 6.1.x and earlier releases, the IP address of themanagement server had to remain static. Thus, the IP address of the managementserver was not supposed to change after IBM Systems Director Server wasinstalled on the system. In IBM Systems Director 6.2 and later releases, changingthe IP address of IBM Systems Director Server is supported. If the IP address ofthe IBM Systems Director Server system changes, the embedded Dynamic IPfeature automatically detects the changed IP address when the IBM SystemsDirector 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 areupdated to use the new IP address of the server. This notification ensures thatthe resources that are managed by IBM Systems Director Server maintaincommunication 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 commonagents. To use this feature, you must first upgrade 6.1.x common agents to 6.2 orlater releases.
The following manageable resource types support updating the IBM SystemsDirector Server IP address when it changes:v Operating systemv BCChassisv Server (RSA, IMM, BMC)v HMCv IVMv StoragePlatformv StorageSubSystemv Switch
60 Installing on Windows and configuring an IBM DB2 database
Attention: If you configure the switch to send SNMP traps to IBM SystemsDirector Server, the switch does not automatically update if the IP addresschanges. Because it requires a manual action from the user to set the SNMP trapdestination, it also requires a manual action to change it. Most switches supportsetting multiple SNMP trap destinations. So, configure the switch to send SNMPtraps to the primary IBM Systems Director Server IP address and to any backupIP addresses to which IBM Systems Director Server could potentially move.However, this configuration is only possible you know ahead of time that thereis a small set of IP addresses to which IBM Systems Director Server couldpotentially move.
Notes:
v Frequent IP address changes can drive network traffic in association withupdating the managed resources with the new IBM Systems Director Server IPaddress. IP address changes can also cause the CPU utilization of IBM SystemsDirector Server to increase and slow down the overall performance. Thisperformance change occurs during the time period that the IP address updatesare sent to the managed resources.
v Dynamic IP does not support on-the-fly processing, meaning that it does notwork unless you restart IBM Systems Director Server.
v Start IBM Systems Director Server for the first time on the same IP address onwhich it was installed. Changing the IP address any time after the first startup issupported.
v Processing for an IP address change is not supported for the scenario where theconfiguration for one IBM Systems Director Server and data is captured with thesmsave command and restored to another IBM Systems Director Server with thesmrestore command and both of these IBM Systems Director Server instanceshave different IP addresses.
To enable the Dynamic IP function, complete the following steps when the IPaddress 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 byyour database application for information and instructions.
b. Do the changes that you identified in the previous step and restart yourdatabase server.
c. View the lwi/conf/overrides/database.properties file and determine ifit contains the previous IP address. If so, for each file in thelwi/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. IBMSystems Director Server takes more time because it must configure itself to thenew IP address.IBM Systems Director Server is active.
Chapter 1. Installing 61
4. Perform Lite Query on the local operating-system agent by issuing thefollowing 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 themanaged resources about the IP change commences.
Note: It takes typically 8 - 10 minutes after IBM Systems Director Server becomesactive 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 SystemsDirector Server. To turn the processing for an IP address change on or off, set thecom.ibm.usmi.kernel.localsystem.USMSLocalSystemService.enableIPChangeProcessing property in the install_root\lwi\conf\overrides\USMIKernel.properties file:
Turn on IP address change processingTo 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 isenabled by default.
Turn IP address change processing offTo turn off IP address change processing, add or edit the property to set itto “false”:com.ibm.usmi.kernel.localsystem.USMSLocalSystemService.enableIPChangeProcessing=false
Related tasks:Restarting IBM Systems Director Server
Configuring IBM Systems Director plug-insIBM Systems Director Server automatically installs some plug-ins that requireconfiguration in order to use them. If you want to use plug-ins that IBM SystemsDirector Server does not automatically install, you must install and configure themafter 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 followingsteps: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 supportfiles, inventory, and Performance Management data to support. Forinstructions, see Activating Electronic Service Agent.
62 Installing on Windows and configuring an IBM DB2 database
v Activate the free trial period for IBM Systems Director VMControl. Forinstructions, see Activating IBM Systems Director VMControl.
4. Install and configure all other IBM Systems Director plug-ins that you intend touse.
Table 11. Configuration tasks and information resources for IBM Systems Director plug-ins
Plug-in Tasks Information resources
Base plug-ins
IBM System Storage®
management1. Configure SMI-S
providers.
2. Configure externalstorage applications.
1. Managing SMI-Sproviders
2. Installing and configuringexternal storageapplications
Remote access manager 1. Configure VirtualNetwork Computing(VNC).
2. Configure RemoteDesktop.
1. Virtual NetworkComputing
2. Configuring MicrosoftWindows RemoteDesktop Connection
Update manager Optional: Complete theGetting Started wizard andchange update settings.
Configuring update manager
Advanced plug-ins
IBM Systems DirectorNetwork Control
Install the plug-in. Installing and uninstallingIBM Systems DirectorNetwork Control
IBM Systems DirectorStorage Control 4.2.3
Install the plug-in. Installing Storage Control
The following base plug-ins are installed with IBM Systems Director Server andhave no configuration tasks:v Automation managerv Configuration managerv Discovery managerv IBM BladeCenter Chassis managementv IBM Power Systems managementv IBM System x managementv IBM System z managementv Network managerv Status manager
Related concepts:
Base function and extensible plug-ins
IBM Systems Director plug-insRelated tasks:Installing IBM Systems Director plug-ins
Configuring the command-line interfaceBefore running the smcli commands or displaying help for them, ensure thatrequired software is installed and the locale is correctly installed and configured onthe system.
Chapter 1. Installing 63
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 youmight 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 andinstalling this file, see https://www.microsoft.com/downloads.
2. Ensure that the desired locale is supported by IBM Systems Director and isinstalled correctly on the client system, from where smcli is run.
Tips:
v To verify languages supported by smcli, see Language specifications for smclicommands.
v If your system does not support double-byte character sets, you see garbagecharacters or small block-like characters when you display operating-systemspecific man pages.
Related reference:
smcli - Systems management command-line interface
Reviewing Microsoft Internet Explorer security optionsIf you are using Microsoft Internet Explorer Web browsers that have EnhancedSecurity Configuration enabled, and are running on Windows Server 2008, reviewthese instructions.
When using a Web browser with Enhanced Security Configuration enabled, someproperties of the IBM Systems Director Web interface might not display asexpected.
Internet Explorer Enhanced Security Configuration establishes a configuration foryour server and for Internet Explorer that decreases the exposure of your server topotential attacks that can occur through Web content and application scripts. As aresult, some websites might not display or perform as expected.
Using a server for Internet browsing is not a good security practice becauseInternet browsing increases the exposure of your server to potential securityattacks. It is a best practice recommendation that you run your Web browser on asystem that is not a server. However, if you must use a server running WindowsServer, you must turn off Internet Explorer Enhanced Security Configuration.
Complete the following applicable steps to disable Internet Explorer EnhancedSecurity:
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.
64 Installing on Windows and configuring an IBM DB2 database
5. In the Internet Explorer Enhanced Security Configuration window, click theapplicable 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 propertiesConfigure IP address properties when your management server has more than oneIP address, when your network uses one or more subnets that IBM SystemsDirector does not manage, and when resources that you want to manage havemore than one IP address. Configure IP address properties by creating or updatingthe 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 managementserver has more than one IP address. For example, a server that has more than onenetwork interface card has more than one IP address. Specify the preferred IPaddress for the management server by creating or updating theIPPreference.properties file.
To specify the preferred IP address for the management server, perform thefollowing steps:1. Use a text editor to open an empty file named IPPreference.properties in the
following location: install_path/data/IPPreference.propertieswhereinstall_path is the path where you installed IBM Systems Director.
Note: If the /data/IPPreference.properties file exists, open the file with a texteditor, 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 thechange correctly supersedes the current entry.
3. Save and close the file.
For Systems Director to recognize the preferred IP address, you must restart themanagement server.Related tasks:Excluding IP addresses“Excluding IP addresses”
Excluding IP addresses:
Chapter 1. Installing 65
Exclude IP addresses by creating or updating the IPPreferences.properties file forresources that you do not want IBM Systems Director to manage or that havemultiple IP addresses, or for subnets that you do not want Systems Director tomanage.
You can exclude one or more individual IP addresses, an IP address range, or anentire 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.propertieswhereinstall_path is the path where you installed Systems Director.
Note: If the /data/IPPreference.properties file exists, open the file with a texteditor, 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 thatyou 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 themanagement server.Related tasks:“Specifying the preferred IP address for the management server” on page 65Specifying the preferred IP address for the management server
Changing IBM Systems Director server health settingsYou can change local system health settings to customize when you will receive awarning. For example, by default, you will get a warning when the SystemsDirector server CPU usage is at 90% for 30 minutes, but your environment mightrequire 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.
66 Installing on Windows and configuring an IBM DB2 database
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 12. Settings with default values that can be changed
Property Input value Default value
System properties
com.ibm.usmi.kernel.localsystem.cpuWarningThreshold
The percentage that triggersthe warning.
90%
com.ibm.usmi.kernel.localsystem.cpuTimeForWarning
The number of millisecondsthe CPU must be at thethreshold level to trigger awarning.
By default, this warning istriggered after the CPU isat 90% for 30 minutes.
1 800 000 milliseconds (30minutes)
Example: By default you get a warning when the Systems Directorserver CPU usage is at 90% for 30 minutes.
Disk usage properties
com.ibm.usmi.kernel.localsystem.diskSpaceWarning
The amount of free spacebefore triggering thewarning.
1 073 741 824 bytes (1 GB)
com.ibm.usmi.kernel.localsystem.diskSpaceCrit
The amount of free spacebefore triggering a criticalevent.
500 MB
Example: By default you get a warning when the Systems Directorserver free space available is less than 1 GB.
Memory usage properties
com.ibm.usmi.kernel.localsystem.memoryWarningPercentage
The percentage of memoryusage that triggers thewarning.
90%
com.ibm.usmi.kernel.localsystem.memoryWarningTime
The amount of time, inmilliseconds, that memoryuse must be sustained totrigger the warning.
By default, this warning istriggered after the memoryusage is at 90% for 1 hour.
3 600 000 milliseconds (1hour)
Example: By default you get a warning when the Systems Directorserver memory usage is at 90% for 1 hour.
Managed endpoint (MEP)count properties
com.ibm.usmi.maxSystems The maximum number ofMEPs supported.
10 000
Chapter 1. Installing 67
Table 12. Settings with default values that can be changed (continued)
Property Input value Default value
com.ibm.usmi.maxSystems.derby The maximum number ofMEPs supported when theApache Derby database isused.
1 000
Example: By default the Systems Director server supports 1000MEPs when using the Apache Derby database.
Page space properties
com.ibm.usmi.kernel.localsystem.psWarningPercentage
The page space usagepercentage that triggers thewarning.
80
com.ibm.usmi.kernel.localsystem.psWarningTime
The time in millisecondsthat page space usage mustbe sustained to trigger thewarning.
By default, this warning istriggered after the pagespace usage is at 80% for 20minutes.
1 200 000 milliseconds (20minutes)
Example: By default you get a warning when the Systems Directorserver page space usage is at 80% for 20 minutes.
Example:com.ibm.usmi.kernel.localsystem.cpuWarningThreshold=90com.ibm.usmi.kernel.localsystem.cpuTimeForWarning=1800000
3. Restart the server.Related tasks:Restarting IBM Systems Director Server
Recovering from a failed installation of IBM Systems DirectorServer 6.3.x
You can recover from a failed installation of IBM Systems Director Server 6.3.x byfixing the problems that are identified in the log files and then performing theinstallation 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 forIBM Systems Director 6.3.x.
Table 13. Example locations of log files for IBM Systems Director 6.3.x
AIX IBM i Linux Windows
IBM Systems Director Server installation logs:
68 Installing on Windows and configuring an IBM DB2 database
Table 13. Example locations of log files for IBM Systems Director 6.3.x (continued)
AIX IBM i Linux Windows
v /var/log/dirinst.log
v /var/log/director/*
v /opt/ibm/director/log/recovery.txt
Not applicable v /var/log/dirinst.log
v /opt/ibm/director/log/*.log
v /opt/ibm/director/log/recovery.txt
v C:\Windows\dirserverinst_time.log
v C:\Windows\dirserversetup.log
v C:\Windows\db2prereqcheck.log
v C:\Windows\prereqcheckdb2.log
v C:\Windows\installdb2.log
v C:\Windows\tivguidinst64.log(64-bit Windows only)
v c:\ProgramFiles\IBM\Director\log\recovery.txt
Common Agent installation logs:
/var/log/dirinst.log v /tmp/director/installAgent.log
v /tmp/director/installDirAgent.log
v /www/cas/lwi/runtime/agent/logs/install
All of these can be found inthe dirmedic results.
/var/log/dirinst.log v C:\Windows\agent_install.log
v C:\Windows\CasInst.log
v C:\Windows\certutil.log
v C:\Windows\diragentinst_time.log
v C:\Windows\diragentsetup.log
v C:\Windows\tivguidinst.log
Platform Agent installation logs:
/var/log/dirinst.log Not applicable /var/opt/ibm/platform/log/install.log
C:\Windows\platinst_time.log
Common Agent uninstallation logs:
Not applicable /tmp/director/uninstallDirAgent.log,which can be found in thedirmedic results.
Platform Agent uninstallation logs:
/var/log/diruninst.log Not applicable /var/opt/ibm/platform/log/uninstall.log
v C:\Windows\platuninst_time.log
v C:\Windows\sysdirremoval.log
Migration logs:
/var/tmp/director_save_630/logs
Not applicable /var/tmp/director_save_630/logs
%APPDATA%\ISD62x\logs
Configuration logs:
/var/log/director/* Not applicable /opt/ibm/director/log/*.log
C:\ProgramFiles\IBM\Director\log\*.log
Default managed IBM DB2 database logs:
Chapter 1. Installing 69
Table 13. Example locations of log files for IBM Systems Director 6.3.x (continued)
AIX IBM i Linux Windows
v /tmp/installdb2.log
v /tmp/db2setup.log
v Directory structure foryour installed IBM DB2database product (Linux)
Not applicable v /tmp/installdb2.log
v /tmp/db2setup.log
v Directory structure foryour installed IBM DB2database product (Linux)
C:\Windows\installdb2.log
2. Perform the installation procedure again. For instructions, see “Installing IBMSystems Director on the management server” on page 27 and select youroperating system.
When you are finished recovering from a failed installation, verify that therecovery was successful. For instructions, see “Verifying the successful installationof IBM Systems Director on the management server” on page 34.Related information:
Installation and migration troubleshooting
Exchanging information with IBM
Managed IBM DB2 installation fails
70 Installing on Windows and configuring an IBM DB2 database
Chapter 2. Installing agents
Prepare your managed systems and environment for agent and subagentinstallation 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 timeas, the agents that are installed on the management server are updated to 6.3.2. Ifyou attempt to update a local agent to 6.3.2 before updating IBM Systems DirectorServer, 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 amanaged resource has multiple IP addresses, specify which IP address SystemsDirector uses to manage the resource. To specify the IP address to use, you specifythat the management server ignore (or exclude) the other IP addresses associatedwith the resource. For more information, see “Excluding IP addresses.”
© Copyright IBM Corp. 1999, 2012 71
Note: For more information about using the Web interface, see Publications andrelated information to access the Systems Management guide.Related tasks:
Choosing the level of agent capabilities to deploy on managed systems
Updating Systems DirectorExcluding IP addresses
Installing VMControl agents and subagentsRelated 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 14. Obtaining the Pre-Installation Utility
Location Action
IBM Systems Director 6.3.2 DVD If you do not already have the DVD, youcan burn the image onto DVD from the IBMSystems Director Downloads website.
SysDir_PreInstUtil_6_3_2_Windows.zip Download the Pre-Installation Utility fromthe IBM Systems Director Downloadswebsite.Note: The downloads website alwayscontains the most recent version.
1. To start the IBM Systems Director Pre-Installation Utility, choose the applicablemethod:v DVDv Pre-Installation Utility download
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
complete the following steps: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 automaticallyopen, then complete the following steps, as applicable:1) Click Start > Run
2) To change to the directory where the Pre-Installation Utility script islocated, type the following command in the Open field and pressEnter:e:\server\{i386 or x64}\checkds\
72 Installing on Windows and configuring an IBM DB2 database
where e is the DVD-ROM drive letter on your system. If youdownloaded the utility, use the directory in which the Pre-InstallationUtility 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 theserver. So, you must specify -p and designate whether you arerunning the tool to prepare for the common agent or platform agentinstallation.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 thefollowing command, and press Enter:unzip
b. To change to the directory where the Pre-Installation Utility script islocated, 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 toolto 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 orthe default browser. Refer to the e:\checkds\readme.txt file for moreinformation about checkds.bat options, the reports that are generated, andreturn codes. The checkds.bat -? command also displays supported syntax.
Related tasks:
Preparing to upgrade and migrateRelated reference:
Systems Director Downloads
Installing Common AgentPrepare your systems and environment for installing Common Agent. Then, usethe Agent Installation wizard, or alternatively, use the manual instructions, toinstall 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 themanagement server after installing IBM Systems Director Server.
v Ensure that the system clocks on the systems that contain IBM Systems DirectorServer and Common Agent remain synchronized.
Related tasks:Running the Pre-Installation Utility
Preparing for a Common Agent managed systemBefore installing Common Agent on a managed system, ensure that therequirements 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 IBMSystems Director Server, ensure that the PasswordAuthentication value in/etc/ssh/sshd_config is set to yes. So, the corresponding line in the sshd_configfile will appear as follows:PasswordAuthentication yes
Note: You must restart the ssh server for any changes made to sshd_config to takeeffect.Related reference:
Hardware requirements for systems running Common Agent or PlatformAgent
Obtaining licenses for Common AgentIBM Systems Director includes licenses for up to 20 installations of Common Agenton non-IBM x86 systems. To install Common Agent on additional non-IBM x86systems, 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/. Fromthe 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 WindowsBefore installing Common Agent on a managed system running Windows, makesure that your system meets all the applicable requirements.
Review the following information and complete the necessary steps to prepareyour system for installation:v Run the Pre-Installation Utility and fix any errors that it identifies. For
instructions, see “Running the Pre-Installation Utility on an agent (Windows)”on page 72.
74 Installing on Windows and configuring an IBM DB2 database
v Ensure that your system meets the hardware and software requirements forinstallation, as described in “Hardware and software requirements”.
v If there is an operating system update in progress, ensure the process iscomplete and you restart the system before starting the IBM Systems Directorinstallation process.
v Ensure that any agentless managed systems are prepared for discovery, asdescribed in “Preparing agentless managed systems”.
v Systems with service processors: Install the supporting device drivers andmapping layers, if they are not already installed. See “Preparing to manageservice processors with IBM Systems Director” for information about thesedrivers and mapping layers.
v If you want to use IBM Systems Director Server on System x for heterogeneousserver management, you can install Common Agent or Platform Agent on theplatforms you want to manage. You can obtain Common Agent and PlatformAgent for the supported operating systems from the IBM Systems Director Website at www.ibm.com/systems/software/director/downloads/agents.html.
v The IBM Systems Director for x86 DVD no longer includes OpenSSH forWindows. If a Platform Agent managed system or Common Agent managedsystem does not have a Secure Shell (SSH) package installed, IBM SystemsDirector Server cannot communicate securely with the managed system. Tosecure communication, install OpenSSH on the managed system. DownloadOpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ andupdate the managed system with SSH.
Related tasks:
Installing agents using the Agent Installation WizardInstalling Common Agent on WindowsRelated reference:
Hardware and software requirements
Supported operating systems
IBM Systems Director Web page
OpenSSH for WindowsRelated information:
Windows installation troubleshooting
Installing agents using the Agent Installation WizardYou can use the Agent Installation Wizard to install agent packages on managedsystems.
IBM Systems Director Server requires a number of agent packages that can bedeployed to managed systems using the Agent Installation Wizard.The importedagent packages are located in the dynamic group “Agent Package Groups” and canbe accessed by clicking Release Management > Agents in the navigation area. Youuse the Agent Installation Wizard to select one of these agent packages to installand one or more systems on which to install the agent package. Then, the wizardcreates 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 theAgent Installation Wizard to install and update agents:
Chapter 2. Installing agents 75
v The root user account was used to initially request access to the managedsystem.
v IBM Systems Director Server on non-Windows systems has SSH, and asuccessful SSH connection exists in both directions between the server and theagent.
v IBM Systems Director Server on Windows systems has DCOM, and a successfulDCOM 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 packagesfrom the “Remote Deployment using Agent Installation wizard” section.
2. Copy the packages to a location of your choice on the IBM Systems DirectorServer 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 Agentmanually” or “Installing Platform Agent manually” for instructions about howto 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 onsystems > Deploy Agents.
v Right-click an agent package or a managed system and select ReleaseManagement > 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 theAvailable list.
Note: A subagent plugs in to a base agent and provides additionalcapabilities to support IBM Systems Director plug-ins such as IBM SystemsDirector 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, theSelected list might already contain one or more agent packages.
v The Agent Installation Wizard can install only one agent package at atime. 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 packagein the Available list.
b. Click Add. The selected systems are displayed in the Selected list.
Notes:
76 Installing on Windows and configuring an IBM DB2 database
v Depending on how you started the Agent Installation Wizard, theSelected list might already contain one or more systems.
v Depending on the agent package that you are installing, some selectedsystems are potentially not valid targets for installation. The wizardchecks the selected systems for some or all of the following criteria toensure 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 theweekend.
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 issent 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 followingcriteria 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 thenumber of systems on which the job had errors. Therefore, if the job runson five systems, the job has errors on two systems, and you set thecriterion 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.
Chapter 2. Installing agents 77
Tip: Make sure that you know the time and time zone to which therespective systems' clocks are set.
b. Select whether you want the job to fail if a system is offline or if you wantthe 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 fromwhich you started the Scheduler. If the job creation fails, a message is displayedin the Launch Job window so that you can correct the job.The job created by the Agent Installation Wizard will transfer the agentself-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 Agentinstall_root/SwDistPk
After the files are copied, the installation file sets are extracted into the /tmpdirectory and installed. The files are then removed after a successfulinstallation. You need to ensure that there is sufficient space on the targetsystem to copy the self-extracting script and extract the file sets. Refer to thespace requirements as specified in “Hardware requirements for systemsrunning Common Agent or Platform Agent”.If the agent deployment completes with errors, check the log file for your targetoperating 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 provideto 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 TrapForwarding by installing and configuring Net-SNMP. For instructions andinformation, see http://www.net-snmp.org/.
Installing Common Agent manuallyYou can use these manual instructions to install Common Agent on a managedsystem. These manual instructions provide an alternative method of installation tousing the Agent Installation Wizard.
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 notnecessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server.
v Ensure that the system clocks on the systems that contain IBM Systems DirectorServer and Common Agent remain synchronized.
78 Installing on Windows and configuring an IBM DB2 database
Related tasks:Preparing a Common Agent managed system
Installing Common Agent on WindowsAfter preparing your system, you can install Common Agent on a Windowssystem by downloading the installation files from the IBM Systems Directorsupport Web site or by using the DVD. You can then perform a standardinstallation or upgrade by using the wizard in a standard interactive mode, or youcan perform an unattended (either with or without status feedback) installation orupgrade by using a response file that automatically provides answers to thequestions that the wizard poses.
Installing Common Agent on Windows using the installation wizard:
After preparing your Windows system, you can use the installation wizard toinstall 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 notnecessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server.
v Ensure that the system clocks on the systems that contain IBM Systems DirectorServer and Common Agent remain synchronized.
Common Agent 6.3.2 and Platform Agent 6.3.2 are primarily intended to supportnew hardware and operating systems. You can install them for the first time onany system that has the supported operating system and hardware, or you caninstall them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exceptionis that the Platform Agent 6.3 installation does not upgrade agents that have theIBM Systems Director 5.20.x on systems with an RSA service processor. In thissituation, 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 IBMDirector Core Services 5.20.31 or 5.20.32.
v To use Common Agent 6.3.2 with reduced support on these systems, firstuninstall 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, firstuninstall IBM Director Core Services 5.20.31 or 5.20.32 and then install PlatformAgent 6.3.2.
Depending on the version of Common Agent that you are installing, you caninstall Common Agent on Windows from either installation media or from adownloaded installation package.
Table 15. Installation options for Common Agent on Windows
Installation method Title or file name
DVD media IBM Systems Director for x86, V6.3.2 DVDNote: To obtain an image of the IBMSystems Director for x86, V6.3.2 DVD,download theSysDir6_3_2_DVD_Windows_x86-64.iso orSysDir6_3_2_DVD_Windows.iso file.
Chapter 2. Installing agents 79
Table 15. Installation options for Common Agent on Windows (continued)
Installation method Title or file name
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 InstallationWizard installation)
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installed onthe system, it is installed during the Common Agent 6.3.2 installation. If theupgrade is necessary, the system prompts you to restart following the installationof Common Agent 6.3.2 without specifying that MSI was installed. Unless youinstall using the response file and set the RebootIfRequired parameter to N, you areprompted to restart whether or not the Common Agent 6.3.2 installation iscompleted successfully.
To install Common Agent on Windows using the installation wizard, log in withan 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,complete the following steps: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 packageto a temporary directory.
c. Click Start > Run.d. In the Open field, type the following command and press Enter:
\installation_directory\IBMSystemsDirectorAgentSetup.exe
where installation_directory is the path to the extracted installationfiles. The Welcome to the installation wizard for IBM Systems DirectorCommon Agent window opens.
DVD media: To start the installation from the DVD, complete the followingsteps:a. Insert the DVD into the DVD-ROM drive.b. If the IBM Systems Director Welcome window automatically opens, then
complete the following steps:1) Select your language.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:1) Click Start > Run
2) In the Open field, type the following commands and press Enter:v For 64-bit:
80 Installing on Windows and configuring an IBM DB2 database
e:\server\x64\bin>miniunz.exee:\agent\SysDir6_3_2_Common_Agent_Windows.jar -d c:\632CA\
v For 32-bit:e:\server\i386\bin>miniunz.exee:\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 existingfolder where the installation files are to be extracted.
3) From the directory where you saved the installation files, open therepository folder and run IBMSystemsDirectorAgentSetup.exe
The installation program starts.4) Go to the next step.
Accessibility note: Screen readers might not process the IBM SystemsDirector Welcome window correctly. To start the installation wizard forCommon 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.2. Click Next. The License Agreement page is displayed3. Select I accept the terms in the license agreement and click Next. The Feature
and installation directory selection page is displayed.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 youwant to register CAS Agent with agent manager and enter in the informationfor that existing agent manager:
Agent Manager Hostname or IP AddressThe host name or IP address of the existing agent manager. If theagent is installed in a network address translation environment, setthis parameter to ensure that the agent has the correct IP address tocontact the agent manager.
Agent Manager Registration PasswordThe 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 completewindow is displayed.
11. Click Finish.12. If you used the DVD for installation, remove the DVD from the drive.13. If you are prompted to restart your system, click Yes.
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installedon the system, it is installed during the IBM Systems Director Server
Chapter 2. Installing agents 81
installation. If the upgrade is necessary, the system prompts you to restartfollowing the installation of IBM Systems Director Server without specifyingthat MSI was installed. You are prompted to restart whether or not the IBMSystems Director Server installation is completed successfully.
When the installation has completed, the resource will be set up as a manageableresource.
To ensure full functionality of your new Common Agent instance, discover it withIBM Systems Director Server.Related tasks:Windows
Importing agent packages
Upgrading and migrating agents
Restarting Common AgentRelated reference:
Systems Director DownloadsRelated information:
Windows installation troubleshooting
Exchanging information with IBM
Performing an unattended installation of Common Agent on Windows:
After preparing your Windows system, you can use a response file to perform anunattended installation of Common Agent. The response file that you create can beemployed on supported systems in your environment 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 notnecessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server.
v Ensure that the system clocks on the systems that contain IBM Systems DirectorServer and Common Agent remain synchronized.
Common Agent 6.3.2 and Platform Agent 6.3.2 are primarily intended to supportnew hardware and operating systems. You can install them for the first time onany system that has the supported operating system and hardware, or you caninstall them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exceptionis that the Platform Agent 6.3 installation does not upgrade agents that have theIBM Systems Director 5.20.x on systems with an RSA service processor. In thissituation, 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 IBMDirector Core Services 5.20.31 or 5.20.32.
v To use Common Agent 6.3.2 with reduced support on these systems, firstuninstall Common Agent 6.1 and then install Common Agent 6.3.2.
82 Installing on Windows and configuring an IBM DB2 database
v To use Platform Agent 6.3.2 with reduced support on these systems, firstuninstall IBM Director Core Services 5.20.31 or 5.20.32 and then install PlatformAgent 6.3.2.
Depending on the version of Common Agent that you are installing, you caninstall Common Agent on Windows from either installation media or from adownloaded 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 DVDNote: To obtain an image of the IBMSystems Director for x86, V6.3.2 DVD,download theSysDir6_3_2_DVD_Windows_x86-64.iso orSysDir6_3_2_DVD_Windows.iso file.
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 InstallationWizard installation)
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installed onthe system, it is installed during the Common Agent 6.3.2 installation. If theupgrade is necessary, the system prompts you to restart following the installationof Common Agent 6.3.2 without specifying that MSI was installed. Unless youinstall using the response file and set the RebootIfRequired parameter to N, you areprompted to restart whether or not the Common Agent 6.3.2 installation iscompleted successfully.
To use a response file to install Common Agent on Windows, log in with anadministrator account and complete the following steps:1. Start the installation from the installation source:
Downloaded installation files: To start the installation from a Web download,complete the following steps: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 packageto a temporary directory.
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, wheredirectory is the local directory into which you extracted the files.
DVD media: To start the installation from the DVD, complete the followingsteps:a. Insert the DVD into the DVD-ROM drive.b. If the installation program starts automatically and the IBM Systems
Director Setup window opens, close it.c. If the IBM Systems DirectorWelcome window does not automatically open,
then complete the following steps to extract the jar file:
Chapter 2. Installing agents 83
1) Click Start > Run
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 existingfolder where the installation files are to be extracted.
3) Go to the next step.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.3. Modify and save the response file with a new file name. For example, rename
the diragent.rsp file to myresponsefile.rsp. This file is fully commented.The following parameters are used in the diragent.rsp file to register theCommon Agent services with an agent manager. These parameters are optional,but, if one is specified, then both must be specified.
CASInstall.AgentManagerHostnameThe host name or IP address for the agent manager. If the agent isinstalled in a network address translation environment, set thisparameter to ensure that the agent has the correct IP address to contactthe agent manager.
CASInstall.RegistrationPasswordThe password for registering with the agent manager.
The following parameters are used to set the ports that the common agentservices will use. A valid number for each port is a number that is greater than1024 and lesser than 65535. The values listed are the default values for eachparameter.v CASInstall.AgentPort=9510
v CASInstall.NostopPort1=9514
v CASInstall.NonstopPort2=9515
4. Open a command prompt and change to the directory that contains theCommon 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
where the variables are defined as follows:
installationtypeOne of the following commands: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.
responsefileThe absolute path and name of the response file that you createdpreviously. For example, c:\myfolder\myresponsefile.rsp. The rsp
84 Installing on Windows and configuring an IBM DB2 database
parameter is optional. If you do not include the rsp parameter, theinstaller uses the default response file in the package.
option One of the following optional parameters:
Table 17. Optional installation parameters
Optional parameter What it does
waitforme Ensures that installation processing will not end until thisinstallation is completed.
debug Logs all messages that are sent by the Microsoft WindowsInstaller log engine, including status and informationmessages.
log=logfilename Specifies the fully qualified name of an alternative log file.
verbose Enables verbose logging.
For example, type the following command:IBMSystemsDirectorAgentSetup.exe /s /a silentrsp="c:\myfolder\myresponsefile.rsp"
This example performs a silent installation of Common Agent on Windowsusing the myresponsefile.rsp response file.
6. If you set the RebootIfRequired parameter to Y in the response file, reboot thesystem if prompted to do so.
Notes:
a. For Windows 2008, Service Pack 1 and earlier, if Microsoft WindowsInstaller (MSI) 4.5 is not installed, then you are prompted to installMicrosoft Windows Installer (MSI) 4.5 and to run the installation programagain 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 installedduring the IBM Systems Director Server installation. If the upgrade of MSIis necessary, the system prompts you to restart following the installation ofIBM Systems Director Server without specifying that MSI was upgraded.Unless you install IBM Systems Director Server by using the response fileand set the RebootIfRequired parameter to N, you are prompted to restartwhether the IBM Systems Director Server installation completes successfully.
7. If you used the DVD for installation, remove the DVD from the drive.
To ensure full functionality of your new Common Agent instance, discover it withIBM Systems Director Server.
Chapter 2. Installing agents 85
Related tasks:Windows
Importing agent packages
Upgrading and migrating agents
Restarting Common AgentRelated reference:
Systems Director DownloadsRelated information:
Windows installation troubleshooting
Exchanging information with IBM
Installing Platform AgentPrepare your systems and environment for installing Platform Agent. Then, use theAgent Installation wizard, or alternatively, use the manual instructions, to installPlatform Agent.
Important:
v Installation of IBM Systems Director installs IBM Systems Director Server,Common Agent (when applicable), and Platform Agent all together. Therefore, itis not necessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server. In most cases,any IBM Systems Director tasks requiring Common Agent or Platform Agentwill be performed for systems with IBM Systems Director Server installed.
v Ensure that the system clocks on systems that contain IBM Systems DirectorServer and Platform Agent remain synchronized.
v If you have BMC, IMM, or IMM2 service processors, use Platform Agent 6.1.1 orlater to help ensure full functionality and support.
v If you have RSA service processors, use IBM Director Core Services 5.20.x tohelp ensure full functionality and support. If you do decide to use PlatformAgent 6.3.2, you must first uninstall IBM Director Core Services 5.20.x beforeinstalling Platform Agent 6.3.2.
Restriction: Platform Agent 6.3.2 will block updates on IBM Director CoreServices 5.20.x systems and RSA service processors. You will no longer be able tomanage the RSA in-band. You can manage it out-of-band by connecting it to thenetwork and discovering it with IBM Systems Director.
v Platform Agent 6.1.1 and later uses a newer version of the LSI MR provider. Thisprovider 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 PlatformAgent systems.
v See “Installing and uninstalling KVM Platform Agent” for considerationsregarding the use of Red Hat Enterprise Linux with Linux Kernel-based VirtualMachine (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
86 Installing on Windows and configuring an IBM DB2 database
again allows the correct functionality to be reflected in IBM Systems Director. Forexample if you are upgrading an endpoint from Agentless managed system toPlatform Agent through the manual agent installation script, you must thendiscover the endpoint again with IBM Systems Director.Related tasks:Running the Pre-Installation Utility
Binding Platform Agent to specific IP addresses
Installing and uninstalling KVM Platform Agent
Preparing for a Platform Agent managed systemBefore installing Platform Agent on a managed system make sure that therequirements 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, themanagement server will be unable to unlock the managed system.To avoid the problem of system-time mismatch, you can configure managedsystems and the management server to synchronize their clocks using a commonnetwork time protocol (NTP) server.Related reference:
RedHat chkconfig bug fix
Preparing to install Platform Agent on WindowsBefore installing Platform Agent on a managed system running Windows, makesure that your system meets all the applicable requirements.
Review the following information and complete the necessary steps to prepareyour system for installation:v Run the Pre-Installation Utility and fix any errors that it identifies. For
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 forinstallation, as described in “Hardware and software requirements”.
v If there is an operating system update in progress, ensure the process iscomplete and you restart the system before starting the IBM Systems Directorinstallation process.
v Ensure that any agentless managed systems are prepared for discovery, asdescribed in “Preparing agentless managed systems”.
v Systems with service processors: Install the supporting device drivers andmapping layers, if they are not already installed. See “Preparing to manageservice processors with IBM Systems Director” for information about thesedrivers and mapping layers.
v If you want to use IBM Systems Director Server on System x for heterogeneousserver management, you can install Common Agent or Platform Agent on theplatforms you want to manage. You can obtain Common Agent and PlatformAgent for the supported operating systems from the IBM Systems Director Website at www.ibm.com/systems/software/director/downloads/agents.html.
Chapter 2. Installing agents 87
v The IBM Systems Director for x86 DVD no longer includes OpenSSH forWindows. If a Platform Agent managed system or Common Agent managedsystem does not have a Secure Shell (SSH) package installed, IBM SystemsDirector Server cannot communicate securely with the managed system. Tosecure communication, install OpenSSH on the managed system. DownloadOpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ andupdate the managed system with SSH.
Related tasks:
Installing agents using the Agent Installation WizardInstalling Platform Agent on WindowsRelated reference:
Hardware and software requirements
Supported operating systems
Systems Director Web page
OpenSSH for WindowsRelated information:
Windows installation troubleshooting
Installing agents using the Agent Installation WizardYou can use the Agent Installation Wizard to install agent packages on managedsystems.
IBM Systems Director Server requires a number of agent packages that can bedeployed to managed systems using the Agent Installation Wizard.The importedagent packages are located in the dynamic group “Agent Package Groups” and canbe accessed by clicking Release Management > Agents in the navigation area. Youuse the Agent Installation Wizard to select one of these agent packages to installand one or more systems on which to install the agent package. Then, the wizardcreates 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 theAgent 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 theagent.
v IBM Systems Director Server on Windows systems has DCOM, and a successfulDCOM 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 packagesfrom the “Remote Deployment using Agent Installation wizard” section.
2. Copy the packages to a location of your choice on the IBM Systems DirectorServer system.
3. Import the packages with the Agent Installation Wizard.
88 Installing on Windows and configuring an IBM DB2 database
4. Make any required changes to the diragent.rsp and or platform.rsp responsefiles. See the topic for your operating system under “Installing Common Agentmanually” or “Installing Platform Agent manually” for instructions about howto 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 onsystems > Deploy Agents.
v Right-click an agent package or a managed system and select ReleaseManagement > 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 theAvailable list.
Note: A subagent plugs in to a base agent and provides additionalcapabilities to support IBM Systems Director plug-ins such as IBM SystemsDirector 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, theSelected list might already contain one or more agent packages.
v The Agent Installation Wizard can install only one agent package at atime. 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 packagein the Available list.
b. Click Add. The selected systems are displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, theSelected list might already contain one or more systems.
v Depending on the agent package that you are installing, some selectedsystems are potentially not valid targets for installation. The wizardchecks the selected systems for some or all of the following criteria toensure 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.
Chapter 2. Installing agents 89
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 theweekend.
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 issent 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 followingcriteria 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 thenumber of systems on which the job had errors. Therefore, if the job runson five systems, the job has errors on two systems, and you set thecriterion 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 therespective systems' clocks are set.
b. Select whether you want the job to fail if a system is offline or if you wantthe 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 fromwhich you started the Scheduler. If the job creation fails, a message is displayedin the Launch Job window so that you can correct the job.The job created by the Agent Installation Wizard will transfer the agentself-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
90 Installing on Windows and configuring an IBM DB2 database
6.x Platform Agent/tmp/platformagent_temp
5.x Common Agentinstall_root/SwDistPk
After the files are copied, the installation file sets are extracted into the /tmpdirectory and installed. The files are then removed after a successfulinstallation. You need to ensure that there is sufficient space on the targetsystem to copy the self-extracting script and extract the file sets. Refer to thespace requirements as specified in “Hardware requirements for systemsrunning Common Agent or Platform Agent”.If the agent deployment completes with errors, check the log file for your targetoperating 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 provideto 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 TrapForwarding by installing and configuring Net-SNMP. For instructions andinformation, see http://www.net-snmp.org/.
Installing Platform Agent manuallyYou can use these manual instructions to install Platform Agent on a managedsystem. These manual instructions provide an alternative method of installation tousing the Agent Installation Wizard.
Important:
v Installation of IBM Systems Director installs IBM Systems Director Server,Common Agent (when applicable), and Platform Agent all together. Therefore, itis not necessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server. In most cases,any IBM Systems Director tasks requiring Common Agent or Platform Agentwill be performed for systems with IBM Systems Director Server installed.
v Ensure that the system clocks on systems that contain IBM Systems DirectorServer and Platform Agent remain synchronized.
v If you have BMC, IMM, or IMM2 service processors, use Platform Agent 6.1.1 orlater to help ensure full functionality and support.
v If you have RSA service processors, use IBM Director Core Services 5.20.x tohelp ensure full functionality and support. If you do decide to use PlatformAgent 6.3.2, you must first uninstall IBM Director Core Services 5.20.x beforeinstalling Platform Agent 6.3.2.
Restriction: Platform Agent 6.3.2 will block updates on IBM Director CoreServices 5.20.x systems and RSA service processors. You will no longer be able tomanage the RSA in-band. You can manage it out-of-band by connecting it to thenetwork and discovering it with IBM Systems Director.
v Platform Agent 6.1.1 and later uses a newer version of the LSI MR provider. Thisprovider will not function properly with older versions of the LSI device drivers.
Chapter 2. Installing agents 91
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 PlatformAgent systems.
v See “Installing and uninstalling KVM Platform Agent” for considerationsregarding the use of Red Hat Enterprise Linux with Linux Kernel-based VirtualMachine (KVM).
Related tasks:Preparing a Platform Agent managed system
Installing Platform Agent on WindowsAfter preparing your system, you can install Platform Agent on a system that isrunning Windows by downloading the installation files from the IBM SystemsDirector support Web site or by using the DVD. You can then perform a standardinstallation or upgrade by using the wizard in a standard interactive mode, or youcan perform an unattended (either with or without status feedback) installation orupgrade by using a response file that automatically provides answers to thequestions that the wizard poses.
Installing Platform Agent on Windows using the installation wizard:
To use the installation wizard to install Platform Agent on a system that is runningWindows, download the installation files from the IBM Systems Director supportWeb site or use the DVD.
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 notnecessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server.
v Ensure that the system clocks on systems that contain IBM Systems DirectorServer and Platform Agent remain synchronized.
Common Agent 6.3.2 and Platform Agent 6.3.2 are primarily intended to supportnew hardware and operating systems. You can install them for the first time onany system that has the supported operating system and hardware, or you caninstall them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exceptionis that the Platform Agent 6.3 installation does not upgrade agents that have theIBM Systems Director 5.20.x on systems with an RSA service processor. In thissituation, 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 IBMDirector Core Services 5.20.31 or 5.20.32.
v To use Common Agent 6.3.2 with reduced support on these systems, firstuninstall 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, firstuninstall IBM Director Core Services 5.20.31 or 5.20.32 and then install PlatformAgent 6.3.2.
You can install Platform Agent on Windows from either installation media or froma downloaded installation package.
92 Installing on Windows and configuring an IBM DB2 database
Table 18. Installation options for Platform Agent on Windows
Installation method Title or file name
DVD media IBM Systems Director for x86, V6.3.2 DVDNote: To obtain an image of the IBM Systems Director forx86, V6.3.2 DVD, download theSysDir6_3_2_DVD_Windows_x86-64.iso orSysDir6_3_2_DVD_Windows.iso file.
Downloaded installationpackage 6.3.2 agents
Install the 6.3.2 agents unless you need fullsupport for downlevel agents that have thepreviously specified hardware and softwareconfigurations.
v SysDir6_3_2_Platform_Agent_Windows.zip(agent package for manual installation)
v SysDir6_3_2_Platform_Agent_Windows.jar(agent package for Agent Installation Wizardinstallation)
Notes:
v The Platform Agent 6.3.2 installer installs MSI 4.5 as a prerequisite. On Windows2008, the Platform Agent installer issues an error message and exits if MSI 4.5 isnot already installed, because an immediate reboot is required. On otherversions of Windows, an immediate reboot is not required and the PlatformAgent 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 usingRemote 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 PlatformAgent 6.3.2 will be blocked on systems that contain any of the these items alongwith IBM Director Core Services 5.20.31 or older. You can force the installation ofPlatform Agent 6.3.2 by specifying the force option with the followingcommand:dir6.3.2_platformagent_windows.exe force
However, rather than force the installation of Platform Agent 6.3.2, insteaduninstall IBM Director Core Services 5.20.31 and then install Platform Agent6.3.2.
To install Platform Agent on Windows using the installation wizard, complete thefollowing 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:
Chapter 2. Installing agents 93
Downloaded installation files: To start the installation from a Web download,complete the following steps: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 packageto a temporary directory.
c. Click Start > Run.d. In the Open field, type the following command and press Enter:
\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 PlatformAgent window opens.
DVD media: To start the installation from the DVD, complete the followingsteps:a. Insert the DVD into the DVD-ROM drive.b. If the IBM Systems Director Welcome window automatically opens, then
complete the following steps:1) Select your language.2) Click IBM Systems Director Agents.3) Click Install IBM Systems Director Platform Agent.4) Go to the next step.
If the IBM Systems Director Welcome window does not automatically open,then complete the following steps:1) Click Start > Run
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_Platform_Agent_Windows.jar /-d c:\632PA\
v For 32-bit:e:\server\i386\bin>miniunz.exe /e:\agent\SysDir6_3_2_Platform_Agent_Windows.jar /-d c:\632PA\
where e is the drive letter of the drive and c:\632PA\ is an existingfolder where the installation files are to be extracted.
3) From the directory where you saved the installation files, open therepository folder and run dir6.3.2_platformagent_windows.exeThe installation program starts.
4) Go to the next step.
Accessibility note: Screen readers might not process the IBM Systems DirectorWelcome window correctly. To start the installation wizard for Platform Agentusing 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.
94 Installing on Windows and configuring an IBM DB2 database
2. Click Next. The License Agreement page is displayed3. Select I accept the terms in the license agreement and click Next. The Feature
and installation directory selection page is displayed.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 windowis displayed.
7. Click Finish.8. If you used the DVD for installation, remove the DVD from the drive.9. If you are prompted to restart your system, click Yes.
Note: If Microsoft Windows Installer (MSI), version 4.5 or later is not installedon the system, it is installed during the IBM Systems Director Serverinstallation. If the upgrade is necessary, the system prompts you to restartfollowing the installation of IBM Systems Director Server without specifyingthat MSI was installed. You are prompted to restart whether or not the IBMSystems Director Server installation is completed successfully.
Note: On Windows and Linux RSA II systems, Platform Agent 6.3.2 will install theLSI MegaRAID provider along with the RSA II service. Platform Agent 6.3.2 willalso install the OSA IPMI driver on Windows 2003 systems that need it. Use theVerify Connection page to query vital properties after you upgrade to PlatformAgent 6.3.2. This will immediately renew alert subscriptions for the LSI MegaRAIDprovider and Basic RAID hardware. If you do not verify the connection, the alertsubscriptions might take as long as an hour to update.Related tasks:Preparing to install Platform Agent on Windows
Importing agent packages
Restarting Platform AgentRelated reference:
Systems Director DownloadsRelated information:
Windows installation troubleshooting
Exchanging information with IBM
Performing an unattended installation of Platform Agent on Windows:
You can perform an unattended installation of Platform Agent using a responsefile, which provides answers to the questions that are posed by the installationwizard. You can use this method to create a standard installation file that can beused on many systems.
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 95
necessary to separately install Common Agent or Platform Agent on themanagement server after installing IBM Systems Director Server.
v Ensure that the system clocks on systems that contain IBM Systems DirectorServer and Platform Agent remain synchronized.
Common Agent 6.3.2 and Platform Agent 6.3.2 are primarily intended to supportnew hardware and operating systems. You can install them for the first time onany system that has the supported operating system and hardware, or you caninstall them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exceptionis that the Platform Agent 6.3 installation does not upgrade agents that have theIBM Systems Director 5.20.x on systems with an RSA service processor. In thissituation, 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 IBMDirector Core Services 5.20.31 or 5.20.32.
v To use Common Agent 6.3.2 with reduced support on these systems, firstuninstall 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, firstuninstall IBM Director Core Services 5.20.31 or 5.20.32 and then install PlatformAgent 6.3.2.
You can install Platform Agent on Windows from either installation media or froma downloaded installation package.
Table 19. Installation options for Platform Agent on Windows
Installation method Title or file name
DVD media IBM Systems Director for x86, V6.3.2 DVDNote: To obtain an image of the IBM Systems Director forx86, V6.3.2 DVD, download theSysDir6_3_2_DVD_Windows_x86-64.iso orSysDir6_3_2_DVD_Windows.iso file.
Downloaded installationpackage 6.3.2 agents
Install the 6.3.2 agents unless you need fullsupport for downlevel agents that have thepreviously specified hardware and softwareconfigurations.
v SysDir6_3_2_Platform_Agent_Windows.zip(agent package for manual installation)
v SysDir6_3_2_Platform_Agent_Windows.jar(agent package for Agent Installation Wizardinstallation)
Notes:
v The Platform Agent 6.3.2 installer installs MSI 4.5 as a prerequisite. On Windows2008, the Platform Agent installer issues an error message and exits if MSI 4.5 isnot already installed, because an immediate reboot is required. On otherversions of Windows, an immediate reboot is not required and the PlatformAgent 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 usingRemote Desktop Connection. To enable Remote Desktop Connection to start,issue one of the following commands:
96 Installing on Windows and configuring an IBM DB2 database
– 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 PlatformAgent 6.3.2 will be blocked on systems that contain any of the these items alongwith IBM Director Core Services 5.20.31 or older. You can force the installation ofPlatform Agent 6.3.2 by specifying the force option with the followingcommand:dir6.3.2_platformagent_windows.exe force
However, rather than force the installation of Platform Agent 6.3.2, insteaduninstall IBM Director Core Services 5.20.31 and then install Platform Agent6.3.2.
1. Start the installation from the installation source:Downloaded installation files: To start the installation from a Web download,complete the following steps: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 packageto a temporary directory.
c. Copy the platformagent.rsp response file to a new location. This file is inthe \directory directory, where directory is the local directory into whichyou extracted the files.
Note: The IBM Director Core Services 5.20.31 coresvcs.rsp response file isin the \directory\FILES directory, where directory is the local directory intowhich you extracted the 5.20.31 files.
DVD media: To start the installation from the DVD, complete the followingsteps:a. Insert the DVD into the DVD-ROM drive.b. If the installation program starts automatically and the IBM Systems
Director Setup window opens, close it.c. If the IBM Systems Director Welcome window does not automatically open,
then complete the following steps to extract the jar file:1) Click Start > Run
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_Platform_Agent_Windows.jar /-d c:\632PA\
v For 32-bit:e:\server\i386\bin>miniunz.exe /e:\agent\SysDir6_3_2_Platform_Agent_Windows.jar /-d c:\632PA\
where e is the drive letter of the drive and c:\632PA\ is an existingfolder where the installation files are to be extracted.
3) Go to the next step.
Chapter 2. Installing agents 97
d. Copy the platformagent.rsp response file to a local directory. This file is inthe repository folder within the directory to which you extracted theinstallation files.
2. Open the copy of the platformagent.rsp file, which follows the Windows INIfile format, in an ASCII text editor.
3. Modify and save the response file with a new file name. For example, renamethe 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
where the variables are defined as follows:
installationtypeOne of the following commands: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.
responsefileThe absolute path and name of the response file that you createdpreviously. For example, c:\myfolder\myresponsefile.rsp. The rspparameter is optional. If you do not include the rsp parameter, theinstaller uses the default response file in the package.
option One of the following optional parameters:
Table 20. Optional installation parameters
Optional parameter What it does
waitforme Ensures that installation processing will not end until thisinstallation is completed.
debug Logs all messages that are sent by the Microsoft WindowsInstaller log engine, including status and informationmessages.
log=logfilename Specifies the fully qualified name of an alternative log file.
verbose Enables verbose logging.
For example, type the following command:dir6.3.2_platformagent_windows.exe /s /a silent \rsp="c:\myfolder\myresponsefile.rsp"
This example performs a silent installation of Platform Agent on Windowsusing the myresponsefile.rsp response file.
Tip: After running a silent installation, you can verify that the installation iscomplete by checking for the process in Windows Task Manager.
5. If you set the RebootIfRequired parameter to Y in the response file, reboot thesystem if prompted to do so.
Notes:
a. For Windows 2008, Service Pack 1 and earlier, if Microsoft WindowsInstaller (MSI) 4.5 is not installed, then you are prompted to installMicrosoft Windows Installer (MSI) 4.5 and to run the installation programagain after the system restarts.
98 Installing on Windows and configuring an IBM DB2 database
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 installedduring the IBM Systems Director Server installation. If the upgrade of MSIis necessary, the system prompts you to restart following the installation ofIBM Systems Director Server without specifying that MSI was upgraded.Unless you install IBM Systems Director Server by using the response fileand set the RebootIfRequired parameter to N, you are prompted to restartwhether the IBM Systems Director Server installation completes successfully.
6. If you used the DVD for installation, remove the DVD from the drive.
Note: On Windows and Linux RSA II systems, Platform Agent 6.3.2 will install theLSI MegaRAID provider along with the RSA II service. Platform Agent 6.3.2 willalso install the OSA IPMI driver on Windows 2003 systems that need it. Use theVerify Connection page to query vital properties after you upgrade to PlatformAgent 6.3.2. This will immediately renew alert subscriptions for the LSI MegaRAIDprovider and Basic RAID hardware. If you do not verify the connection, the alertsubscriptions might take as long as an hour to update.Related tasks:Preparing to install Platform Agent on Windows
Importing agent packages
Restarting Platform AgentRelated reference:
Systems Director DownloadsRelated information:
Windows installation troubleshooting
Exchanging information with IBM
Verifying the successful installation of an IBM Systems Director agentYou 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 managedsystems 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 followingcommand 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.
Chapter 2. Installing agents 99
3. The IBM Systems Director Home page provides a quick overview, as well aslinks 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 plansv Check for updates on discovered systems.v Set up additional user securityv Start configuring your systems
After you have verified that the agent installation was successful, complete thefollowing 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 SystemsDirector.
Related tasks:
Logging in
Discovering systems with system discovery
Collecting and viewing inventory data
Importing agent packages
100 Installing on Windows and configuring an IBM DB2 database
Chapter 3. Preparing agentless managed systems
Prepare the agentless managed systems in your environment before you discoveror 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 amanaged resource has multiple IP addresses, specify which IP address SystemsDirector uses to manage the resource. To specify the IP address to use, you specifythat the management server ignore (or exclude) the other IP addresses associatedwith 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 thesshd_config file will appear as follows:PasswordAuthentication yes
2. On all agentless managed systems that use the root user for request access forthe 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 takeeffect.
2. IBM Systems Director does not support the ssh protocol on VMware ESXihosts. If ssh is discovered on a VMware ESXi managed system, it might causeproblems when attempting to collect inventory.
Related tasks:Excluding IP addressesRelated reference:
Hardware and software requirements
Supported operating systems
AIX Pegasus CIM server and providers
Preparing to manage service processors with IBM Systems DirectorYou can use IBM Systems Director to manage supported service processors that areinstalled in a managed system.
IBM Systems Director can manage service processors that are installed in Agentlessmanaged systems, Platform Agent managed systems, and Common Agentmanaged 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
© Copyright IBM Corp. 1999, 2012 101
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 CommonAgent managed system to enable management of the service processor, completethe 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 21.
Note: For information about specific IBM Systems Director functions thatsupport or do not support these systems, see IBM ServerProven atwww.ibm.com/servers/eserver/serverproven/compat/us/.
Table 21. Servers with service processors that are supported for Platform Agent or Common Agent management byIBM Systems Director
Server type Supported models
IBM BladeCenter blade servers withan IPMI baseboard managementcontroller (BMC)
See the “IBM BladeCenter, System x,and System x servers with an IPMIbaseboard management controller(BMC) or with an integrated systemsmanagement module (IMM)” columnin Table 22 on page 105.
v IBM BladeCenter HC10v IBM BladeCenter HS20, machine types 1883, 1884, 7981, 8843v IBM BladeCenter HS12, machine types 8014, 8028v IBM BladeCenter HS21v IBM BladeCenter HS21 XMv IBM BladeCenter HS40v IBM BladeCenter JS12 Expressv IBM BladeCenter JS20v IBM BladeCenter JS21v IBM BladeCenter JS22v IBM BladeCenter LS20v IBM BladeCenter LS21v IBM BladeCenter LS22v IBM BladeCenter LS41v IBM BladeCenter LS42v IBM BladeCenter QS21
IBM BladeCenter blade servers withan integrated systems managementmodule (IMM)Note: The IMM internally contains aBMC.
See the “IBM BladeCenter, System x,and System x servers with an IPMIbaseboard management controller(BMC) or with an integrated systemsmanagement module (IMM)” columnin Table 22 on page 105.
v IBM BladeCenter HS22 machine type 7870v IBM BladeCenter HS22V machine type 7871v IBM BladeCenter HX5 machine type 7872
IBM BladeCenter blade servers withan Integrated systems managementprocessor (ISMP)
See the “IBM BladeCenter andSystem x servers with an integratedsystems management processor(ISMP)” column in Table 22 on page105.
IBM BladeCenter HS20, machine types 8678, 8832, 8833
102 Installing on Windows and configuring an IBM DB2 database
Table 21. Servers with service processors that are supported for Platform Agent or Common Agent management byIBM Systems Director (continued)
Server type Supported models
eServer™ servers with an IPMIbaseboard management controller(BMC)
See the “eServer servers with anIPMI baseboard managementcontroller (BMC)” column in Table 22on page 105.Note: Some systems supportinstallation of an optional RemoteSupervisor Adapter or RemoteSupervisor Adapter II serviceprocessor. If this optional serviceprocessor is installed, it supersedesthe standard service processor forthat system, and all managementoccurs through the RemoteSupervisor Adapter or RemoteSupervisor Adapter II.
v IBM eServer 325, machine type 8835v IBM eServer 326, machine type 8848v IBM eServer 326m, machine type 7969v IBM eServer 326m, machine type 7992
System x and System x servers withan IPMI baseboard managementcontroller (BMC)
See the “IBM BladeCenter, System x,and System x servers with an IPMIbaseboard management controller(BMC) or with an integrated systemsmanagement module (IMM)” columnin Table 22 on page 105.Note: Some systems supportinstallation of an optional RemoteSupervisor Adapter or RemoteSupervisor Adapter II serviceprocessor. If this optional serviceprocessor is installed, it supersedesthe standard service processor forthat system, and all managementoccurs through the RemoteSupervisor Adapter or RemoteSupervisor Adapter II.
v System x3200v System x3200 M2v System x3250v System x3250 M2v System x3250 M3v System x3350v System x3400v System x3450v System x3455v System x3500v System x3550v System x3610v System x3650v System x3650 Tv System x3655v System x3755v System x3755 M31
v System x3800v System x3850
v System x 206mv System x 236v System x 260v System x 306mv System x 336v System x 346v System x 347v System x 366
1 The BMC in this system provides a subset of the function found in theother system BMCs.
Chapter 3. Preparing agentless managed systems 103
Table 21. Servers with service processors that are supported for Platform Agent or Common Agent management byIBM Systems Director (continued)
Server type Supported models
System x and System x servers withan integrated systems managementmodule (IMM)Note: The IMM internally contains aBMC.
See the “IBM BladeCenter, System x,and System x servers with an IPMIbaseboard management controller(BMC) or with an integrated systemsmanagement module (IMM)” columnin Table 22 on page 105.
v System x3200 M3 machine types 7327 and 7328v System x3250 M2 machine types 4190, 4191, and 4194v System x3400 M2 machine types 7836 and 7837v System x3400 M3 machine types 7378 and 7379v System x3500 M2 machine type 7839v System x3500 M3 machine type 7380v System x3550 M2 machine type 7946v System x3550 M3 machine type 7944v System x3620 M3 machine type 7376v System x3650 M2 machine type 7947v System x3650 M3 machine type 7945v System x3690 X5 machine type 7148v System x3850 M2 machine type 7233v System x3850 X5 machine type 7145v System x3950 M2 machine types 7141 and 7233v System x3950 X5 machine type 7145
System x and System x servers witha Remote Supervisor Adapter II orRemote Supervisor Adapter IISlimLine
See the “System x and System xservers with a Remote SupervisorAdapter II or Remote SupervisorAdapter II SlimLine” column inTable 22 on page 105.Note: On some of these systems,installation of the Remote SupervisorAdapter or Remote SupervisorAdapter II service processor isoptional. If this optional serviceprocessor is not installed, allmanagement occurs through eitheran IPMI baseboard managementcontroller (BMC) or an integratedsystems management processor(ISMP).Restriction: When IBM DirectorAgent 5.20.x or IBM Director CoreServices 5.20.x is installed, you canmanage Remote Supervisor AdapterII or Remote Supervisor Adapter IISlimLine in-band. When CommonAgent 6.1.x or 6.2.x, or PlatformAgent 6.1.x or 6.2.x are installed, youare no longer able to manage theRSA in-band. You can manage itout-of-band by connecting it to thenetwork and discovering it with IBMSystems Director.
v System x3105v System x3200v System x3200 M2v System x3250v System x3250 M2v System x3350v System x3400v System x3455v System x3500v System x3550v System x3650v System x3650 Tv System x3655v System x3755v System x3800v System x3850v System x3850 M2v System x3950v System x3950 Ev System x3950 M2
v System x 206v System x 206mv System x 225v System x 226v System x 232v System x 236v System x 255v System x 260v System x 305v System x 306v System x 306mv System x 335v System x 336v System x 342v System x 345v System x 346v System x 347v System x 360v System x 366v System x 445v System x 460v System x MXE 460
104 Installing on Windows and configuring an IBM DB2 database
Table 21. Servers with service processors that are supported for Platform Agent or Common Agent management byIBM Systems Director (continued)
Server type Supported models
System x servers with an integratedsystems management processor(ISMP)
See the “IBM BladeCenter andSystem x servers with an integratedsystems management processor(ISMP)” column in Table 22.
v System x 232v System x 235v System x 255v System x 335v System x 342v System x 343v System x 345
IBM Flex System compute nodeswith the integrated managementmodule II (IMM2)
v IBM Flex System x220 ComputeNode, Types 2585 and 7906
v IBM Flex System x240 ComputeNode, 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 operatingsystem in Table 22.
RSA restriction: When IBM Director Agent 5.20.x or IBM Director CoreServices 5.20.x is installed, you can manage Remote Supervisor Adapter II orRemote Supervisor Adapter II SlimLine in-band. When Common Agent 6.1.x or6.2.x, or Platform Agent 6.1.x or 6.2.x are installed, you are no longer able tomanage the RSA in-band. You can manage it out-of-band by connecting it tothe network and discovering it with IBM Systems Director.
Table 22. Required drivers for in-band management of service processors
Operating system ofmanaged server
IBM BladeCenter,System x, and System xservers with an IPMIbaseboard managementcontroller (BMC) orwith an integratedsystems managementmodule (IMM)
eServer servers with anIPMI baseboardmanagement controller(BMC)
System x and System xservers with a RemoteSupervisor Adapter IIor Remote SupervisorAdapter II SlimLine
IBM BladeCenter andSystem x servers withan integrated systemsmanagement processor(ISMP)
v Red Hat EnterpriseLinux, version 4
v Red Hat EnterpriseLinux, version 5.0
OpenIPMI driver OpenIPMI driver
LM78 driver
RSA daemon
USB drivers
LM78 driver
SMBus driver
Other Red HatEnterprise Linuxdistributions
OSA IPMI driver
IBM Mapping Layer
MSI IPMI driver
IBM Mapping Layer
LM78 driver
RSA daemon
USB drivers
LM78 driver
SMBus driver
v SUSE LinuxEnterprise Server 9 forx86
v SUSE LinuxEnterprise Server 10for x86
OpenIPMI driver OpenIPMI driver
LM78 driver
RSA daemon
USB drivers
LM78 driver
SMBus driver
Other SUSE Linuxdistributions
OSA IPMI driver
IBM Mapping Layer
MSI IPMI driver
IBM Mapping Layer
LM78 driver
RSA daemon
USB drivers
LM78 driver
SMBus driver
Chapter 3. Preparing agentless managed systems 105
Table 22. Required drivers for in-band management of service processors (continued)
Operating system ofmanaged server
IBM BladeCenter,System x, and System xservers with an IPMIbaseboard managementcontroller (BMC) orwith an integratedsystems managementmodule (IMM)
eServer servers with anIPMI baseboardmanagement controller(BMC)
System x and System xservers with a RemoteSupervisor Adapter IIor Remote SupervisorAdapter II SlimLine
IBM BladeCenter andSystem x servers withan integrated systemsmanagement processor(ISMP)
Virtual systems usingXen
OpenIPMI driver OpenIPMI driver
LM78 driver
RSA daemon
USB drivers
LM78 driver
SMBus driver
VMware ESX Server,versions 4.0, 4.0.1, and4.1.
OpenIPMI driver OpenIPMI driver
LM78 driver
USB drivers
LM78 driver
SMBus driver
Other VMwaredistributions
OSA IPMI driver
IBM Mapping Layer
MSI IPMI driver
IBM Mapping Layer
LM78 driver
Not supported SMBus driver
Windows Server 2008 MS IPMI driver MS IPMI driver RSA Library The necessary driversare installed withCommon Agent orPlatform Agent.
Windows Server 2003 R2 MS IPMI driver MS IPMI driver RSA Library
USB drivers
The necessary driversare installed withCommon Agent orPlatform Agent.
Other Windowsoperating systems
OSA IPMI driver
IBM Mapping Layer
MSI IPMI driver
IBM Mapping Layer
LM78 driver
RSA Library
USB drivers
The necessary driversare installed withCommon Agent orPlatform Agent.
4. Install the required drivers.
Note: If required, the MSI IPMI driver and the OSA IPMI driver must beinstalled before the IBM Mapping Layer.
IBM Mapping LayerThe IBM Mapping Layer is used to translate IBM Systems Director"generic" requests into driver-specific requests for different IPMIdrivers. Download this driver from the IBM Support Web Site atwww.ibm.com/support/us.
LM78 driverThe LM78 device driver ensures that IBM Systems Director Serverreceives memory and processor Predictive Failure Analysis (PFA) alerts.
See “Installing IBM LM78 and SMBus device drivers” for installationinstructions.
MS IPMI driverIBM Systems Director agent can use the Intelligent PlatformManagement Interface (IPMI) driver included with Windows 2003 R2and Windows 2008. In order for IBM Systems Director Server toprovide in-band alerting from the Baseboard Management Controller(BMC) or Integrated Management Module (IMM), the MS IPMI driveris required. By default, the MS IMPI driver is not installed withWindows 2003 R2. To install the Microsoft IPMI device driver on
106 Installing on Windows and configuring an IBM DB2 database
Windows 2003 R2, see “Managing IPMI Devices in Windows 2003 R2and Windows 2008” in the IBM Systems Director Best Practices Wiki.
The MS IPMI driver is included with the Windows 2008 operatingsystem. No separate installation is required.
MSI IPMI driverThe MSI IPMI device driver is used to communicate with the IPMIbaseboard management controller. All other systems should use theOSA IPMI driver. Download this driver from the IBM Support Web Siteat www.ibm.com/support/us.
OpenIPMI driverThis driver is included with the operating system. No separateinstallation is required.
OSA IPMI driverThe OSA IPMI device driver is used to communicate with the IPMIbaseboard management controller. Download this driver from the IBMSupport Web Site at www.ibm.com/support/us.
RSA daemonThe RSA daemon is a Linux-only program that is used to interface withthe Remote Supervisor Adapter. Download this driver from the IBMSupport Web Site at www.ibm.com/support/us.
RSA libraryThe RSA library device driver is a Windows-only driver that is used tointerface with the Remote Supervisor Adapter. It also prevents drivercommunication from interfering with IBM Systems Director. Downloadthis driver from the IBM Support Web Site at www.ibm.com/support/us.
SMBus driverThe SMBus device driver ensures that configuration manager andstatus manager tasks function correctly, and is used to communicatewith the integrated systems management processor (ISMP) on someservers.
See “Installing IBM LM78 and SMBus device drivers for Linux” forinstallation instructions.
USB driversThe RSA daemon and RSA library use this driver to communicate withthe Remote Supervisor Adapter II. This driver is included with theoperating system. No separate installation is required.
5. Make sure that you have the latest firmware installed for your serviceprocessors.
Chapter 3. Preparing agentless managed systems 107
Related concepts:
Platform agent
Common agentRelated tasks:Installing the LM78 or SMBus device driverRelated reference:
Hardware and software requirements
Supported operating systems
Support Web siteRelated information:
Unresponsive service processor
Preparing to manage an IBM BladeCenter chassis using IBM SystemsDirector Server on a non-blade server
You can install IBM Systems Director Server on a non-blade server. With thismanagement server you can manage one or more IBM BladeCenter units and theblade servers installed in them. You must configure the network so that thisinstallation is possible.
Complete the following steps to prepare to manage an IBM BladeCenter chassisusing 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 anIBM BladeCenter management module is first started, it searches for a DHCPserver. If a DHCP server is not found, the IBM BladeCenter managementmodule assigns IP address 192.168.70.125 to the external management port.Because this static IP address is the same for all management modules, IPaddress conflicts can occur if you do not use a DHCP server and introducemultiple IBM BladeCenter chassis onto a network simultaneously. When youconfigure the IBM BladeCenter chassis, you assign static IP addresses to theswitch module and the external and internal ports of the management module.
2. Set up a separate management network to configure and manage your IBMBladeCenter chassis and blade servers. By separating the LAN segment usedfor production from the LAN segment to which the IBM BladeCentermanagement module is connected, you can ensure that only authorized systemadministrators 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 themanagement 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 atwww.ibm.com/servers/.
108 Installing on Windows and configuring an IBM DB2 database
This network configuration ensures that applications running on the blade serverscannot modify chassis settings, because the blade servers have no connection toeither the management module or the switch module configuration ports.
Note: If you are using an IBM BladeCenter management module instead of anadvanced management module, only one of the following software applicationscan communicate with it at any given time:v Cluster Systems Management (CSM)v IBM Systems Director Serverv IBM Management Processor Command-Line Interface (MPCLI)
Preparing to manage an IBM BladeCenter chassis using IBM SystemsDirector Server on a blade server
You can install IBM Systems Director Server on a blade server. With thismanagement server you can manage the IBM BladeCenter unit, including theserver on which IBM Systems Director Server is installed, and other IBMBladeCenter units. You must configure the network so that this installation ispossible.
Consider the following issues when managing the IBM BladeCenter unit thatcontains 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 removethe instance of IBM Systems Director Server from the network and halt theentire IBM Systems Director environment.Specifically, do not perform these tasks on the blade server where IBM SystemsDirector Server is installed without careful consideration:– Powering off that blade server
Figure 1. Example of IBM BladeCenter deployment network when IBM Systems DirectorServer is not installed on a blade server
Chapter 3. Preparing agentless managed systems 109
– Changing the boot options on that blade serverv Create a network setup that enables the IBM BladeCenter Management Module
to communicate with the management server. Otherwise IBM Systems Directorwill be unable to discover the IBM BladeCenter chassis that contains themanagement server.
By default, the blade servers installed in a IBM BladeCenter chassis cannotcommunicate automatically with the IBM BladeCenter Management Module. Thisarchitecture is designed to prevent the blade servers from modifying the IBMBladeCenter chassis settings. If you install IBM Systems Director Server on a bladeserver and want to use the instance of IBM Systems Director to manage the IBMBladeCenter unit in which the management server is installed, you must enablecommunication 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 anIBM BladeCenter management module is first started, it searches for a DHCPserver. If a DHCP server is not found, the IBM BladeCenter managementmodule assigns IP address 192.168.70.125 to the external management port.Because this static IP address is the same for all management modules, IPaddress conflicts can occur if you do not use a DHCP server and introducemultiple IBM BladeCenter chassis onto a network simultaneously. When youconfigure the IBM BladeCenter chassis, you assign static IP addresses to theswitch module and the external and internal ports of the management module.
2. Set up a separate management network to configure and manage your IBMBladeCenter chassis and blade servers. By separating the LAN segment usedfor production from the LAN segment to which the IBM BladeCentermanagement module is connected, you can ensure that only authorized systemadministrators 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 theIBM BladeCenter unit in which the management server is installed, enablecommunication between the Campus LAN and the Management LAN. Figure 2on 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 atwww.ibm.com/servers/.
110 Installing on Windows and configuring an IBM DB2 database
With this configuration, IBM Systems Director Server can communicate through theCampus LAN to the Management LAN and then onto the management module.
Note: If you are using an IBM BladeCenter management module instead of anadvanced management module, only one of the following software applicationscan communicate with it at any given time:v Cluster Systems Management (CSM)v IBM Systems Director Serverv IBM Management Processor Command-Line Interface (MPCLI)Related reference:
Systems
Preparing Windows managed systemsYou might need to configure certain Windows systems before you can discoverthem with IBM Systems Director Server. Ensure that each Windows system thatyou want to manage has been appropriately configured.
Preparing Windows Server 2003 managed systemsYou might need to configure certain Windows Server 2003 systems before you candiscover them with IBM Systems Director Server. Ensure that each Windows Server2003 system that you want to manage has been appropriately configured.
Typically, managed systems are first discovered using the discovery task in IBMSystems Director Web interface. Then, Platform Agent or Common Agent isinstalled on the managed systems directly from IBM Systems Director Webinterface. 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 enablediscovery by IBM Systems Director Server:
Figure 2. Example of IBM BladeCenter deployment network when IBM Systems DirectorServer is installed on a blade server
Chapter 3. Preparing agentless managed systems 111
Verify that remote registry administration is enabled. Remote registryadministration must be enabled in order for Agentless managed system discoveryto run commands and run scripts on the managed system. The default setting forremote registry administration on Windows systems is enabled. Complete thefollowing 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 systemsYou might need to configure certain Windows Server 2008 systems before you candiscover them with IBM Systems Director Server. Ensure that each Windows Server2008 system that you want to manage has been appropriately configured.
Typically, managed systems are first discovered using the discovery task in IBMSystems Director Web interface. Then, Platform Agent or Common Agent isinstalled on the managed systems directly from IBM Systems Director Webinterface. 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 enablediscovery by IBM Systems Director Server:
Verify that remote registry administration is enabled. Remote registryadministration must be enabled in order for Agentless managed system discoveryto run commands and run scripts on the managed system. The default setting forremote registry administration on Windows systems is enabled. Complete thefollowing 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 systemsSome Windows Vista systems might need to be configured before you can bediscover or manage them with IBM Systems Director Server. Make sure eachWindows Vista system that you want to manage has been appropriatelyconfigured.
Typically, managed systems are first discovered using the Discovery task in IBMSystems Director Web interface. Then, Platform Agent or Common Agent isinstalled on the managed systems directly from IBM Systems Director Web
112 Installing on Windows and configuring an IBM DB2 database
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 enablemanagement by IBM Systems Director Server:Related reference:
Hardware and software requirements
Supported operating systems
Preparing to manage an agentless managed system runningWindows VistaBefore IBM Systems Director can manage a system running Windows Vista, youmust configure a password-protected administrator account on the managedsystem and enable sharing and the remote registry service.
To prepare the Windows Vista system for management by IBM Systems Director,complete the following steps:1. Configure the user account that IBM Systems Director will use.
Type of account Configuration steps
Built-inAdministratoraccount on themanaged system
Enable the Administrator account and set a password for theaccount.
1. Click Start > Control Panel > System and Maintenance >Administrative Tools.
2. In the Administrative Tools window, double-click LocalSecurity 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, andthen set a password for the account.
Local user accountother thanAdministrator
Disable User Account Control, create the user account, and set apassword for the account.
1. Click Start > Control Panel > System and Maintenance >Administrative Tools.
2. In the Administrative Tools window, double-click LocalSecurity Policy.
3. Click Security Settings > Local Policies > Security Options.
4. Double-click User Account Control: Run all administrators inAdmin 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.
Chapter 3. Preparing agentless managed systems 113
Type of account Configuration steps
Domain account Disable User Account Control.
1. Click Start > Control Panel > System and Maintenance >Administrative Tools.
2. In the Administrative Tools window, double-click LocalSecurity Policy.
3. Click Security Settings > Local Policies > Security Options.
4. Double-click User Account Control: Run all administrators inAdmin Approval Mode.
5. Click Disabled, and then click OK.
To enable these changes, you will need to shut down and restart the managedsystem.
2. Verify that remote registry administration is enabled. Remote registryadministration must be enabled in order for Agentless managed systemdiscovery to run commands and run scripts on the managed system. Thedefault setting for remote registry administration on Windows systems isenabled. Complete the following steps to verify or change the remote registryadministration 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 discoveryv File sharingv 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 useRemote Execution and Access (RXA) ports 135, 137, 138, and 139, as well asDCOM port 445, to communicate with the managed system.
7. Click OK.
Preparing a Windows Vista system for Platform Agent managedsystem managementBefore IBM Systems Director can manage Platform Agent on a system runningWindows Vista, you must configure the firewall to allow communication on theSLP, CIM, and CIM SSL ports.
114 Installing on Windows and configuring an IBM DB2 database
To prepare the Windows Vista system for Platform Agent managed systemmanagement 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 WindowsVista.” Configuration for Agentless managed system management is required inorder to access the managed system.
2. Click Start > Control Panel > Network and Internet > Windows Firewall.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 23.a. Click Add port.b. Specify the Name, Port number, and Protocol in the Add port window.c. Click OK.
Table 23. Ports required for Platform Agent managed system management of Windows Vistasystems
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 managedsystem managementBefore IBM Systems Director can manage Platform Agent on a system runningWindows Vista, you must configure the firewall to allow communication withCommon Agent on ports 14247 and 14248.
To prepare the Windows Vista system for Common Agent managed systemmanagement 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 WindowsVista.” Configuration for Agentless managed system management is required inorder to access the managed system.
2. Click Start > Control Panel > Network and Internet > Windows Firewall.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 on page 116.a. Click Add port.b. Specify the Name, Port number, and Protocol in the Add port window.c. Click OK.
Chapter 3. Preparing agentless managed systems 115
Table 24. Ports required for Common Agent managed system management of Windows Vistasystems
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 systemsYou might need to configure certain Windows XP systems before you can discoverthem with IBM Systems Director Server. Ensure that each Windows XP system thatyou want to manage has been appropriately configured.
Typically, managed systems are first discovered using the discovery task in IBMSystems Director Web interface. Then, Platform Agent or Common Agent isinstalled on the managed systems directly from IBM Systems Director Webinterface. The configuration of some Windows XP managed systems, however, canprevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows XP system to enable discovery byIBM Systems Director Server:1. Disable Simple File Sharing. Windows XP targets must have Simple File
Sharing disabled for Agentless managed system discovery to work. Completethe following steps to disable simple file sharing on the Windows XP system tobe 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 byIBM Systems Director Server. Windows XP (before Service Pack 2) includes abuilt-in firewall called Internet Connection Firewall (ICF), which is disabled bydefault. Windows XP Service Pack 2 includes Windows Firewall, which isenabled by default. Either firewall will block attempted accesses by Agentlessmanaged system discovery unless the firewall is disabled or an exception isdefined for the management server on which IBM Systems Director Server isinstalled.Complete the following steps to enable IBM Systems Director Server to accessthe 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.
116 Installing on Windows and configuring an IBM DB2 database
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 thisconfiguration.
3. Verify that remote registry administration is enabled. Remote registryadministration must be enabled in order for Agentless managed systemdiscovery to run commands and run scripts on the managed system. Thedefault setting for remote registry administration on Windows systems isenabled. Complete the following steps to verify or change the remote registryadministration 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. Thedefault hidden administrative disk shares are required for correct operation ofAgentless managed system discovery.At a command prompt, type net share and press Enter to list the sharesdefined on the managed system.
Related reference:
Hardware and software requirements
Supported operating systems
Chapter 3. Preparing agentless managed systems 117
118 Installing on Windows and configuring an IBM DB2 database
Chapter 4. Uninstalling
Uninstall IBM Systems Director and its components (including the defaultdatabase) from your system.
Notes:
v Ensure that you uninstall any IBM Systems Director plug-ins before using thesemethods to uninstall IBM Systems Director Server, Common Agent, or PlatformAgent. For information, see the uninstallation instructions provided with eachplug-in.
v Consider retaining the configuration data when you uninstall IBM SystemsDirector. This enables you to reinstall or upgrade IBM Systems Director andaccess the saved configuration data. Should you reinstall, be sure to reinstallIBM Systems Director in the same location.
v If you want to change your installation of IBM Systems Director 6.x to aprevious IBM Director 5.20.x version, you need to first uninstall all instances ofCommon Agent 6.x and Platform Agent 6.x. This is necessary because IBMDirector Server 5.20.x cannot discover Common Agent 6.x nor Platform Agent6.x. As a result, the pre-6.x installation will not provide any indication that anIBM Systems Director 6.x component is present.Attempting to install an earlier version of Common Agent or Platform Agentthan that which already exists on the system has the potential to causeproblems. Therefore, first uninstall the existing, later version of Common Agentor Platform Agent before installing the earlier version.
v If you are uninstalling agents on a previously discovered endpoint, you mustdiscover the endpoint again after you uninstall the agent. Discovering theendpoint again allows the correct functionality to be reflected in IBM SystemsDirector.
Related tasks:Installing the management serverPreparing agentless managed systemsInstalling Common AgentInstalling Platform AgentRelated information:
Installation or uninstallation fails and requires cleanup
Uninstalling IBM Systems Director on WindowsUninstall IBM Systems Director and its components (including the defaultdatabase) by using either the Windows Add or Remove Programs feature or acommand-line prompt. You can use either of these methods to uninstall IBMSystems Director Server, Common Agent and Platform Agent.
© Copyright IBM Corp. 1999, 2012 119
Related tasks:Installing the management serverPreparing agentless managed systemsInstalling Common AgentInstalling Platform AgentRelated information:
Installation or uninstallation fails and requires cleanup
Uninstalling IBM Systems Director using the Windows Add orRemove Programs feature
Use the Windows Add or Remove Programs feature to uninstall IBM SystemsDirector from Windows.
Note: Only the highest level IBM Systems Director component that is installed islisted. The highest level component is IBM Systems Director Server, followed byCommon Agent, and then Platform Agent.
Ensure that you uninstall any IBM Systems Director plug-ins before using thesemethods to uninstall IBM Systems Director Server, Common Agent, or PlatformAgent. For information, see the uninstallation instructions provided with eachplug-in.
Ensure that any instances of Common Agent or Platform Agent that you uninstallare not discovered by IBM Systems Director Server. If they are discovered, removethem from IBM Systems Director Server before you uninstall them.
To uninstall IBM Systems Director using the Windows Add or Remove Programsfeature, 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 softwarecomponent.
Note: Depending on your operating system version and the components thatyou are removing, the uninstallation task might take a long time (up to anhour) to complete.
5. Remove the TIVguid package if it is not in use by another product. TheTIVguid package is not automatically removed in case it is needed by anotherproduct.
Note: An example of a scenario in which you would leave the TIVguidpackage installed is where you already manage a resource with IBM SystemsDirector Server and plan to reinstall and continue to manage that resource. IBMSystems Director Server will use TIVguid to identify the resource instance. IfTIVguid is removed and then the agent is reinstalled, IBM Systems DirectorServer 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 ofuninstalling and reinstalling an agent, you should remove the agent from anymanagement servers that are managing it before performing the uninstallation.
120 Installing on Windows and configuring an IBM DB2 database
Then perform a rediscovery after the agent has been reinstalled.If you determine that it is not needed elsewhere, remove it using the Add orRemove Programs window. You can then remove the following relateddirectories if you have first ensured that they are empty (other IBM or Tivolisoftware that is installed at these locations could be damaged if you remove thefolders):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 oruninstall process. It is recommended that you keep these files:v Windows\diragentinst_date_time.logv Windows\diragentuninst_date_time.logv Windows\platinst_date_time.logv Windows\platuninst_date_time.logv Windows\dirserverinst_date_time.logv Windows\dirserveruninst_date_time.logv Windows\dirserver_sysdirremoval.logv Windows\SoftwareDistribution\DataStore\Logs\edbtmp.logv Windows\SoftwareDistribution\DataStore\Logs\tmp.edb
Attention: If you plan to uninstall IBM Systems Director and then install anearlier release of IBM Systems Director, you must remove TIVguid. If you leavethe newer TIVguid on the system, the installation of common agent serviceswill fail.
6. Restart Windows.
Chapter 4. Uninstalling 121
Related tasks:Installing the management serverPreparing agentless managed systemsInstalling Common AgentInstalling Platform AgentUninstalling using the isduninst commandRelated information:
Installation or uninstallation fails and requires cleanup
Uninstalling IBM Systems Director using the isduninstcommand
Use the isduninst command to uninstall IBM Systems Director from Windows.
Ensure that you uninstall any IBM Systems Director plug-ins before using thesemethods to uninstall IBM Systems Director Server, Common Agent, or PlatformAgent. For information, see the uninstallation instructions provided with eachplug-in.
Ensure that any instances of Common Agent or Platform Agent that you uninstallare not discovered by IBM Systems Director Server. If they are discovered, removethem from IBM Systems Director Server before you uninstall them.
Complete the following step to uninstall the IBM Systems Director component thatis 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 neededby another product. If you determine that it is not needed elsewhere, removeit 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.
122 Installing on Windows and configuring an IBM DB2 database
Table 25. Possible values for isduninst and dirunins options
Variable Parameter What it does
option debug Logs all messages that are sent by the WindowsInstaller log engine, including status and informationmessages
log=logfilename Specifies the fully qualified name of an alternativeinstallation log file
noreboot Suppresses any required restart
silent Suppresses all output to the screen
unattended Shows the progress of the uninstallation but does notrequire any user input
verbose Enables verbose logging
Note: Depending on your operating system version and the components thatyou are removing, the uninstallation task might take a long time (up to anhour) to complete.
2. Restart Windows.Related tasks:Installing the management serverPreparing agentless managed systemsInstalling Common AgentInstalling Platform AgentRelated information:
Installation or uninstallation fails and requires cleanup
Chapter 4. Uninstalling 123
124 Installing on Windows and configuring an IBM DB2 database
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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:
IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:
Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.
This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.
Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.
© Copyright IBM Corp. 1999, 2012 125
IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:
IBM CorporationDept. LRAS/Bldg. 90311501 Burnet RoadAustin, TX 78758-3400U.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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.
Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.
All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject tochange before the products described become available.
This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,
126 Installing on Windows and configuring an IBM DB2 database
modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable 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, mustinclude 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 colorillustrations may not appear.
TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks 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 orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand 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, othercountries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Othernames may be trademarks of their respective owners.
UNIX is a registered trademark of The Open Group in the United States and othercountries.
Other company, product, or service names may be trademarks or service marks ofothers.
Notices 127
128 Installing on Windows and configuring an IBM DB2 database
����
Printed in USA
