fqp0_bk_install_server_windows_managed_db2.pdf

IBM Systems DirectorInstalling IBM Systems Director with managed IBM DB2database on WindowsVersion 6.3

NoteBefore using this information and the product it supports, read the information in Notices onpage 115.

Copyright IBM Corporation 1999, 2012.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsAbout 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 . . . . . 7Preparing to install IBM Systems DirectorServer on Windows . . . . . . . . . . 9Preparing firewalls and proxies for IBMSystems Director. . . . . . . . . . . 10Installing firmware and device drivers . . . 11

Running the Pre-Installation Utility (PIU) . . . 15Running the IBM Systems DirectorPre-Installation Utility on the managementserver (Windows) . . . . . . . . . . 16Windows pre-installation checks . . . . . 17

Installing IBM Systems Director on themanagement server. . . . . . . . . . . 23

Installing IBM Systems Director Server onWindows . . . . . . . . . . . . . 23Tips for creating the server response file forIBM Systems Director Server . . . . . . 29

Verifying the successful installation of IBMSystems Director on the management server . . 30Configuring IBM Systems Director Server afterinstallation . . . . . . . . . . . . . 30

Switching the database that IBM SystemsDirector uses . . . . . . . . . . . . 31Database configuration attributes . . . . . 33Tips for database user authorities andpasswords . . . . . . . . . . . . . 42Logging on to IBM Systems Director Serverfor the first time . . . . . . . . . . . 48Restarting IBM Systems Director Server . . . 49Enabling Dynamic IP support . . . . . . 50Configuring IBM Systems Director plug-ins . 52Configuring the command-line interface . . . 53

Reviewing Microsoft Internet Explorer securityoptions . . . . . . . . . . . . . . 54Configuring IP address properties . . . . . 55Changing IBM Systems Director server healthsettings . . . . . . . . . . . . . . 56

Recovering from a failed installation of IBMSystems Director Server 6.3.x . . . . . . . 58

Chapter 2. Installing agents . . . . . . 61Running the Pre-Installation Utility on an agent(Windows). . . . . . . . . . . . . . . 62Installing Common Agent . . . . . . . . . 63

Preparing for a Common Agent managed system 64Obtaining licenses for Common Agent . . . 64Preparing to install Common Agent onWindows . . . . . . . . . . . . . 64

Installing agents using the Agent InstallationWizard . . . . . . . . . . . . . . . 65Installing Common Agent manually . . . . . 68

Installing Common Agent on Windows . . . 69Installing Platform Agent . . . . . . . . . . 76

Preparing for a Platform Agent managed system 77Preparing to install Platform Agent onWindows . . . . . . . . . . . . . 77

Installing agents using the Agent InstallationWizard . . . . . . . . . . . . . . . 78Installing Platform Agent manually . . . . . 81

Installing Platform Agent on Windows . . . 82Verifying the successful installation of an IBMSystems Director agent . . . . . . . . . . 89

Chapter 3. Preparing agentlessmanaged systems . . . . . . . . . . 91Preparing to manage service processors with IBMSystems Director. . . . . . . . . . . . . 91Preparing to manage an IBM BladeCenter chassisusing IBM Systems Director Server on a non-bladeserver . . . . . . . . . . . . . . . . 98Preparing to manage an IBM BladeCenter chassisusing IBM Systems Director Server on a bladeserver . . . . . . . . . . . . . . . . 99Preparing Windows managed systems . . . . . 101

Preparing Windows Server 2003 managedsystems . . . . . . . . . . . . . . 101Preparing Windows Server 2008 managedsystems . . . . . . . . . . . . . . 102Preparing Windows Vista managed systems . . 102

Preparing to manage an agentless managedsystem running Windows Vista . . . . . 103Preparing a Windows Vista system forPlatform Agent managed systemmanagement . . . . . . . . . . . 104Preparing a Windows Vista system forCommon Agent managed systemmanagement . . . . . . . . . . . 105

Copyright IBM Corp. 1999, 2012 iii

Preparing Windows XP managed systems . . . 106

Chapter 4. Uninstalling . . . . . . . 109Uninstalling IBM Systems Director on Windows 109

Uninstalling IBM Systems Director using theWindows Add or Remove Programs feature . . 110

Uninstalling IBM Systems Director using theisduninst command . . . . . . . . . . 112

Notices . . . . . . . . . . . . . . 115Trademarks . . . . . . . . . . . . . . 117

iv Installing with managed IBM DB2 database on Windows

About this publicationThis 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 guideYou 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 terminologyThese 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 Systemshttp://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.

PublicationsRelease Notes 6.3.2

Provides 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 with managed IBM DB2 database on Windows

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 Directorftp://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 Directorftp://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.3Hardware 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 Directorwww.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 with managed IBM DB2 database on Windows

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 with managed IBM DB2 database on Windows

Checklist: Installing IBM Systems Director ServerUse this checklist to guide you through the installation process.

1 Prepare the management server.

__ 1. Reference the installation worksheets (4.__ 2. Prepare the database application (7).__ 3. Prepare firewalls and proxies on the management server (10).__ 4. Prepare the management server (9).__ 5. Run the Pre-Installation Utility (15.

2 Install IBM Systems Director Server.

__ 1. Install IBM Systems Director Server (23).__ 2. Verifying the management server installation. (30

3 Configuring after installation (logging in for the first time, switching databases, and more)

__ 1. Perform some post install configuration of IBM Systems Director Server (30).

Copyright IBM Corp. 1999, 2012 xi

xii Installing with managed IBM DB2 database on Windows

Checklist: Installing agentsUse this checklist to guide you through the installation process.

1 Prepare your managed systems.

__ 1. Run the Pre-Installation Utility (62.__ 2. Prepare systems for Platform Agent (77).__ 3. Prepare systems for Common Agent (64).__ 4. If relevant, prepare any agentless managed systems for discovery and

management by IBM Systems Director (91).2 Install the agents.

__ 1. Use the Agent Installation Wizard to deploy agent packages to yourmanaged systems (65).

Copyright IBM Corp. 1999, 2012 xiii

xiv Installing with managed IBM DB2 database on Windows

Chapter 1. Installing IBM Systems DirectorIf 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 VMControlThese 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 with managed IBM DB2 database on Windows

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:


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, seePreparing 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


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.

Note: You can choose to configure the managed IBM DB2 after the initialinstallation is complete or switch databases to use the managed IBM DB2 databaseat a later time.

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 managed IBM DB2:

Use this worksheet to record and plan for a custom IBM Systems Directorinstallation with the managed 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 mightwant to acquire before the installation process. Use this worksheet to record andplan for a custom installation.

Table 1. Properties or parameters required during a custom installation processCustom installation Your value

Setup type Custom

User credentials

Local computer name The panel displays the default value of the local computer.

User name The panel displays the default value of the local computer.

Password

Common agent configuration

Common agent portnumber

9510 (default)

Nonstop service ports 9514, 9515 (default)

Agent manager configuration


Table 1. Properties or parameters required during a custom installation process (continued)Custom installation Your value

Select an agent managertype

v Create an agent managerv Select an existing agentmanager

Create an agent manager (default)

New agent manager configurationTip: To make it easier to remember, you might set the Agent manager user name,password, and registration password to match the local computer user name andpassword.

Agent manager user name

Agent manager password

Agent registrationpassword

Database type

Select the database youintend to use.

IBM DB2 managed by IBM Systems Director Server

Local installation folder

Database port 50010 (default)

Drive to contain thedatabase

The default values include:

v Windows: CNote: While the C drive is the typical default, the valuematches the location where you install IBM SystemsDirector.

Initial database password Generated by default; however, you can choose to specifyyour own.

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.

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 managerRelated reference:Tips for user authorities and passwords for the managed IBM DB2 database

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)drivers

v 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 systems 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.


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 for Managed IBM DB2:

Before installing IBM Systems Director 6.3.x, ensure that your system meetsrequirements for the default database.1. To ensure that your operating system meets the software requirements for the

managed IBM DB2 database, run the Pre-Installation Utility (PIU). For moreinformation, see "Running the Pre-Installation Utility (PIU)."

2. IBM Systems Director installs the managed IBM DB2 database using atemporary password. The temporary password is later changed to theappropriate password value. On IBM Systems Director Server 6.3.2 (and later),the temporary password is only used when installing managed IBM DB2through the IBM Systems Director Server installer with the option to userandomly generated passwords. For all other cases with IBM Systems DirectorServer 6.3.2, including post-installation configuration, the appropriate passwordis set immediately when managed IBM DB2 is installed.IBM Systems Director uses the following temporary passwords:v For AIX and Linux: think4mev For Windows: d1Think4Me (IBM Systems Director 6.3.x) sd1_632Thnk4Me (IBM Systems Director 6.3.2 and later)

If your security policy does not support the temporary password, ensure thatyou install with the IBM Systems Director 6.3.2 downloadable ISO image andthat you specify your own password for managed IBM DB2 when you performthe installation.

After you have prepared for the managed IBM DB2 database, you can continuepreparing the management server for installation. For instructions, see Preparingthe management server on page 4.


Related tasks:Running the Pre-Installation Utility (PIU)Related reference:

Installation requirements for DB2 database products

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 fortechnical 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 15.

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.


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:


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 2. Required internet connectionsDNS 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


Table 2. 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


delivery04-mul.dhe.ibm.com 129.35.224.115,170.225.15.115


delivery04.dhe.ibm.com 129.35.224.105,170.225.15.105


Service and Support Manager

eccgw01.boulder.ibm.com 207.25.252.197 443 https

eccgw02.rochester.ibm.com 129.42.160.51 443 https

www-945.ibm.com 129.42.26.224,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. SeeChoosing the management level for managed systems for information.


RSA II notes for installing on Linux:

v The RSA II daemon requires the libusb and libusb-devel packages, which 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.


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.


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.


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.


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 3. Required ServeRAID controller firmware and device driver filesFiles (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


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.


Related concepts:Installation overview on page 1Related tasks:

Preparing to upgrade and migrateRelated reference:



Pre-Installation Utility


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 4. Obtaining the Pre-Installation UtilityLocation 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 packageComplete 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 automatically

open, then complete the following steps, as applicable:1) Click Start > Run2) 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 downloada. Extract the contents of the Pre-Installation Utility package, type the

following command, and press Enter:unzip SysDir_PreInstUtil_6_3_2_Windows.zip

b. Change to the directory where the Pre-Installation Utility script is 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 packageThese 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


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:


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 8421v 8422v 20000


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 9510v 9514v 9515If 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 15988v 15989v 6989If 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


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


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


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


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.


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 > Rund. 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 28.

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.


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, seeVerifying the successful installation of IBM Systems Director on the managementserver on page 30.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:


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.


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

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.


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 butdoes not require any user input.

v The silent command suppresses all output to the screen duringinstallation.

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 5. Optional installation parametersOptional 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.


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 switchto a custom database

v Custom silent installation with any database other than the managed IBMDB2 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, seeVerifying the successful installation of IBM Systems Director on the managementserver on page 30.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:


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.


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 continuouslyrunning

v Specify a different location from where to install updatesv If you are installing IBM Systems Director Server, you must specify the databasetype that you plan to use with IBM Systems Director Server: If you want to use the default managed IBM DB2 database, you must specify

USE_MANAGED_DB=1. This value is the default.v If you are upgrading IBM Systems Director Server to version 6.3.0 and migratingyour 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 plan to migrate to the managed IBM DB2 database, you must specify

MIGRATE_TO_MANAGED_DB2=1. If you are currently using the Apache Derby database, it does not matter

which value you specify for the MIGRATE_TO_MANAGED_DB2 option. Theupgrade and migration process automatically migrates your Apache Derbydatabase to the managed IBM DB2 database.

v If you plan to use the managed IBM DB2 database, you can specify thefollowing options: You can specify the password that the managed IBM DB2 database uses in

the DB_PWD option. If you leave this option blank, the installation orupgrade process automatically generates a password.

You can specify the port that the managed IBM DB2 database uses in theDB_PORT option. If you leave this option blank, the installation or upgradeprocess automatically uses the default port 50010. If that port is in use, theinstallation or upgrade process automatically searches for and uses the nextavailable port.

You can specify a non-default location to store the managed IBM DB2database data in one of the following options:- For Windows, use the DB_DATADRIVE option. If you leave this optionblank, the installation or upgrade process automatically stores the managedIBM DB2 database data in the same location that it installs IBM SystemsDirector Server.


If your system has user ID and password restrictions, you might need tospecify certain options to ensure that the installation succeeds. For moreinformation, see "Managed IBM DB2 installation fails."

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 0indicates that an item is not installed or upgraded.

v If you want to use the default for any value in the response file, comment outthat 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.

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

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: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 areinstalled 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 \proddata directory, where 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 commentedout.

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 33and 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 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:

De

fqp0_bk_install_server_windows_managed_db2.pdf

Documents

ibm systems director

ibm systems directorserver

ibm systemsdirector

managed ibm db2database

copyright ibm corporation

common agent onwindows

agent installationwizard

platform agent onwindows