IBM Tivoli Asset Discovery for Distributed Version Installation Guide GI

Transcription

1 IBM Tioli Asset Discoery for Distributed Version Installation Guide GI

2

3 IBM Tioli Asset Discoery for Distributed Version Installation Guide GI

4 Installation Guide This edition applies to Version of IBM Tioli Asset Discoery for Distributed and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2002, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Planning the Tioli Asset Discoery for Distributed installation.. 1 Introduction Tioli Asset Discoery for Distributed components 1 Installation checklist - installing on the embedded WebSphere Application Serer Installation checklist - installing using sample scripts on the stand-alone WebSphere Application Serer Installation checklist - installing manually on the stand-alone WebSphere Application Serer... 4 Serer hardware and software requirements CPU and memory requirements for the serer and database Space requirements for the serer and database.. 6 Supported operating systems for the serer and database Other software prerequisites for the serer and database Supported ersions of WebSphere Application Serer Agent hardware and software requirements Supported operating systems for the agents.. 21 VMware and Microsoft irtualization considerations Other software requirements for the agents.. 35 Disk space requirements Supported enironments for J2EE application monitoring Support for high aailability enironments Support for system scaling using Intel QuickPath Interconnect Supported national languages for IBM i agents 45 Topology and capacity planning Network planning Security considerations Installation considerations Proof-of-concept installation Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed. 51 An oeriew of the installation process Installing the serer Preparing files for installation Preparing serer files Preparing DB2 files Software packages for installing Tioli Asset Discoery for Distributed Synchronizing the clocks of serer and database computers Changing SELinux settings before installing Tioli Asset Discoery for Distributed on Red Hat Linux Installing Tioli Asset Discoery for Distributed with the embedded ersion of WebSphere Application Serer Installing the serer in interactie mode Installing the Tioli Asset Discoery for Distributed serer in silent mode Resuming a failed Tioli Asset Discoery for Distributed serer installation Serer installation response files Installing the Tioli Asset Discoery for Distributed on WebSphere Application Serer.. 67 Installing WebSphere Application Serer Configuring WebSphere Application Serer.. 68 Updating WebSphere Application Serer and Integrated Solutions Console Extracting the installation files from the interactie installer Installing the database and its prerequisites.. 71 Modifying the settings of Jaa Virtual Machine Installing the serer components Manually installing the serer components.. 79 Enabling the Tioli Asset Discoery for Distributed command line interface Verifying the serer installation Installing Software Knowledge Base Toolkit Taking the first steps after the installation of IBM Tioli Software Knowledge Base Toolkit Installing agents - oeriew Adding scan groups Preparing agent certificates for client authentication Running Common Inentory Technology enabler 97 Disabling SELinux when installing the agent on RedHat Linux Installing agents using natie installers Installing agents on Windows using a natie installer Installing agents on Linux using natie installers Installing agents on Linux for zseries Installing agents on AIX using natie installers Installing agents on HP-UX using natie installers Installing agents on Solaris using natie installers Installing agents on IBM i using natie installers Using IBM Tioli Configuration Manager to install the agents in bulk Installing agents with Windows logon scripts 112 Performing a refresh installation of agents Agent installation response files Windows agent installation response file and logon script configuration file Copyright IBM Corp. 2002, 2010 iii

6 UNIX agents installation response file IBM i agent installation response file Agent installation software package blocks Software package parameters for UNIX and Windows platforms Software package parameters for IBM i Uninstalling Uninstalling the Tioli Asset Discoery for Distributed serers and databases Uninstalling the serer in interactie mode 126 Uninstalling the serer in silent mode Running scripts to uninstall Tioli Asset Discoery for Distributed Scripts used in undeploying the serer on WebSphere Application stand-alone ersion. 130 Uninstalling the agents Uninstalling Tioli Asset Discoery for Distributed agents using the tlmunins script. 130 Uninstalling agents using natie installation tools Remoing agents Troubleshooting and support Problems and solutions Troubleshooting serer installation Troubleshooting agent installation and upgrade Keeping up-to-date Importing new catalogs Importing a processor alue unit table Notices Trademarks Index i Installation Guide

7 Chapter 1. Planning the Tioli Asset Discoery for Distributed installation Before starting the installation, reiew the information in this section to learn about hardware and software requirements and other considerations. Introduction IBM Tioli Asset Discoery for Distributed proides software and hardware inentory information and use monitoring and is the source of inentory data for Tioli Asset Management for IT. It helps you maintain an up-to-date inentory of the distributed software assets in your IT infrastructure. Tioli Asset Discoery for Distributed components Tioli Asset Discoery for Distributed consists of a serer with a DB2 database and Web interface, a command-line interface and agents installed on monitored machines. Serer components WebSphere Application Serer (embedded or standalone) Integrated Solutions Console Tioli Asset Discoery for Distributed serer DB2 database Command-line interface Agents Serer components Tioli Asset Discoery for Distributed serer The serer collects the inentory data from the agents and enables subscribed users to be notified about eents which are releant to their roles. Each installation of Tioli Asset Discoery for Distributed has a single serer, which can run either on an embedded or a standalone ersion of the WebSphere Application Serer software. Database The Tioli Asset Discoery for Distributed database stores the collected data, such as products installed on systems, processor Copyright IBM Corp. 2002,

8 Agents alue units (PVU) information, hardware information needed for the PVU pricing model, and configuration settings. The database runs on DB2 software. Integrated Solutions Console Integrated Solutions Console is the Web interface for the serer. Registered users can use it to perform administratie tasks, such as producing reports of PVU capacity and inentory information oer time. Command-line interface The command-line interface can be used to manage Tioli Asset Discoery for Distributed. Agents are installed on each operating system that should be monitored by Tioli Asset Discoery for Distributed. They perform hardware and software scans and forward the results to the serer. Installation checklist - installing on the embedded WebSphere Application Serer You can print the checklist and use it during the installation to ensure that you hae completed all the necessary steps. Table 1. Installing Tioli Asset Discoery for Distributed on the embedded ersion of WebSphere Application Serer Step Task Status 1 Plan and prepare to install. 1.1 Ensure that the computer where you are installing the serer fulfills all software requirements. 1.2 Ensure that the computers where you are installing the agents fulfill all requirements. 1.3 Plan the topology. 1.4 Consider the leel of security for the communication between the serer and agents. 1.5 Prepare the files for installation. 2 Install the serer 2.1 If you are installing the serer and its database on different computers, synchronize the clocks of the serer and database computers. 2.2 Linux Change SELinux settings. 2.3 Perform one of the following steps: Ensure that you hae the required ersion of DB2 and its fix packs installed on your computer If you plan to install the bundled ersion of DB2, check if your computer meets all the requirements. 2.4 Run the installation wizard to install the serer or run the installation from the command-line interface. 3 Install the agents 3.1 Create scan groups and assign agents to chosen scan groups. 3.2 If you hae chosen maximum security leel, prepare agent certificates for client authentication. 2 Installation Guide

9 Table 1. Installing Tioli Asset Discoery for Distributed on the embedded ersion of WebSphere Application Serer (continued) Step Task Status 3.3 If you do not use VMware Virtual Center, run the Common Inentory Technology enabler. 3.4 Use the installation wizard or run the scripts to install the agents. On Windows, you can use Windows logon scripts to install the agents. If you hae Tioli Configuration Manager installed, you can use its function to deploy the agents Post-installation tasks 4.1 You can enable agent self-update. Installation checklist - installing using sample scripts on the stand-alone WebSphere Application Serer You can print the checklist and use it during the installation to ensure that you hae completed all the necessary steps. Table 2. Installing Tioli Asset Discoery for Distributed on the base ersion of WebSphere Application Serer using sample scripts Step Task Status 1 Plan and prepare to install. 1.1 Ensure that the computer where you are installing the serer fulfills all software requirements. 1.2 Ensure that the computers where you are installing the agents fulfill all requirements. 1.3 Plan the topology. 1.4 Consider the leel of security for the communication between the serer and agents. 1.5 Prepare the files for installation. 2 Install the serer 2.1 If you are instaling the serer and its database on different computers, synchronize the clocks of the serer and database computers. 2.2 Linux Change SELinux settings. 2.3 Perform one of the following steps: Ensure that you hae the required ersion of DB2 and its fix packs installed on your computer If you plan to install the bundled ersion of DB2, check if your computer meets all the requirements. 2.4 Install WebSphere Application Serer. 2.5 Configure WebSphere Application Serer. 2.6 Extract the installation files from the interactie installer. 2.7 Install the database and its prerequisites. 2.8 Modify the settings of Jaa Virtual Machine. 2.9 Edit the SetupWAS.properties file Run the scripts extracted from the interactie installer to install the serer. Chapter 1. Planning the installation 3

10 Table 2. Installing Tioli Asset Discoery for Distributed on the base ersion of WebSphere Application Serer using sample scripts (continued) Step Task Status 2.11 Start the Web user interface to erify that the serer installation has been successful. 3 Install the agents 3.1 Create scan groups and assign agents to chosen scan groups. 3.2 If you hae chosen maximum security leel, prepare agent certificates for client authentication. 3.3 If you do not use VMware Virtual Center, run the Common Inentory Technology enabler. 3.4 Use the installation wizard or run the scripts to install the agents. On Windows, you can use Windows logon scripts to install the agents. If you hae Tioli Configuration Manager installed, you can use its function to deploy the agents Post-installation tasks 4.1 You can enable agent self-update. Installation checklist - installing manually on the stand-alone WebSphere Application Serer You can print the checklist and use it during the installation to ensure that you hae completed all the necessary steps. Table 3. Installing Tioli Asset Discoery for Distributed on the base ersion of WebSphere Application Serer (manually) Step Task Status 1 Plan and prepare to install. 1.1 Ensure that the computer where you are installing the serer fulfills all software requirements. 1.2 Ensure that the computers where you are installing the agents fulfill all requirements. 1.3 Plan the topology. 1.4 Consider the leel of security for the communication between the serer and agents. 1.5 Prepare the files for installation. 2 Install the serer 2.1 If you are installing the serer and its database on different computers, synchronize the clocks of the serer and database computers. 2.2 Linux Change SELinux settings. 2.3 Perform one of the following steps: Ensure that you hae the required ersion of DB2 and its fix packs installed on your computer If you plan to install the bundled ersion of DB2, check if your computer meets all the requirements. 2.4 Install WebSphere Application Serer. 2.5 Configure WebSphere Application Serer. 4 Installation Guide

11 Table 3. Installing Tioli Asset Discoery for Distributed on the base ersion of WebSphere Application Serer (manually) (continued) Step Task Status 2.6 Extract the installation files from the interactie installer. 2.7 Install the database and its prerequisites. 2.8 Modify the settings of Jaa Virtual Machine. 2.9 Install the administration and Message Handler components Configure the connection between the serer and the database Configure the communication between the agent and the Message Handler Enable the command-line interface Start the Web user interface to erify that the serer installation has been successful. 3 Install the agents 3.1 Create scan groups and assign agents to chosen scan groups. 3.2 If you hae chosen maximum security leel, prepare agent certificates for client authentication. 3.3 If you do not use VMware Virtual Center, run the Common Inentory Technology enabler. 3.4 Use the installation wizard or run the scripts to install the agents. On Windows, you can use Windows logon scripts to install the agents. If you hae Tioli Configuration Manager installed, you can use its function to deploy the agents. 4 Post-installation tasks 4.1 You can enable agent self-update. Serer hardware and software requirements After reiewing the capacity requirements and planning your serer topology, confirm that you meet the system requirements for the arious serer components. CPU and memory requirements for the serer and database Ensure that the computer where you are installing the Tioli Asset Discoery for Distributed serer meets the minimal CPU, and memory requirements for the serer and database elements. The requirements are diided into: Hardware requirements for enironments with up to agents. Hardware requirements for enironments with to agents. Chapter 1. Planning the installation 5

12 Table 4. Hardware requirements for enironments with up to agents. CPU Serer AIX and Linux 2 Power4 1.2 GHz Database Linux and Windows x86, 32 and 64 bit Solaris SPARC HP-UX Linux on zseries at least one Intel Core Solo T GHz processor Sun-Fire-280R 1015 MHz two way processor rp2470, at least two PA-RISC MHz processors Type 2084, one dedicated processor. For CPU requirements for DB2 V9.1, 9.5, and 9.7 see 01.ibm.com/software/data/db2/9/sysreqs.html. Memory Serer only Serer and database 1GB RAM 3GB RAM Table 5. Hardware requirements for enironments with to agents. CPU Serer AIX and Linux At least one Power6 4.7 GHz processor Linux x86, 32 and 64 bit Intel Xeon 2.5 GHz, four-way processor Solaris SPARC One SPARC VI, 2150 MHz (4 threads) processor HP-UX rp8420, at least two PA-RISC GHz processors Linux on zseries Type 2084, two dedicated processors Windows x86, 32 and 64 bit One Dual Core AMD Opteron, 2.6 GHz processor Database For CPU requirements for DB2 V9.1, 9.5, and 9.7 see 01.ibm.com/software/data/db2/9/sysreqs.html. Memory Serer only Serer and database 1GB RAM 4GB RAM Space requirements for the serer and database Check if your computer has the required amount of disk space for serer and database installation. You can install the Tioli Asset Discoery for Distributed serer and database on the same computer, or on two different machines. When installing the database, you can also select whether you want to install the DB2 database software, which the Tioli Asset Discoery for Distributed database runs on, or whether it is already installed on your system. The table below shows how much space you need depending on your operating system and the components that you are 6 Installation Guide

13 installing on this machine. The space requirements for the serer component were measured for the embedded ersion of WebSphere Application Serer included in the installation package. If you want to install the Tioli Asset Discoery for Distributed serer on a standalone application serer (recommended for large enironments with more than 5000 agents), isit WebSphere Application Serer information center for space requirements: infocenter/wasinfo/7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ welcome_nd.html. Important: In addition to the space requirements described below, remember to resere some space for the database in the database location. When you sign a report, it is at first generated and stored as an XML file on your hard disk drie. For large enironments and long reporting periods the file can be up to 2 GB in size. If there is not enough free space, signing the report will fail. You can specify the location where the XML file should be generated by editing the reportpath parameter in the system.properties file. The requirements below are for installation only. Chapter 1. Planning the installation 7

14 Operating system AIX Installed components Directory Required space Serer and database, including the DB2 prerequisite Serer and database without the DB2 prerequisite Serer only Database, including the DB2 prerequisite Database without the DB2 prerequisite Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar Product installation directory Database installation directory /tmp /etc /ar Product installation directory /tmp /etc /ar Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar Product installation directory Database installation directory /tmp /etc /ar 1941 MB 507 MB 562 MB 632 MB under 1 MB under 1 MB 1941 MB 553 MB 632 MB under 1 MB 259 MB 1941 MB 632 MB under 1 MB under 1 MB 125 MB 507 MB 562 MB 632 MB under 1 MB 125 MB 125 MB 553 MB 121 MB under 1 MB 125 MB 8 Installation Guide

15 Operating system HP-UX Installed components Directory Required space Serer and database, including the DB2 prerequisite Serer and database without the DB2 prerequisite Serer only Database, including the DB2 prerequisite Database without the DB2 prerequisite Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar/tmp Product installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory /tmp /etc /ar/tmp Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory Database installation directory /tmp /etc /ar /ar/tmp 1873 MB 1537 MB 2973 MB 349 MB under 1 MB 418 MB 1873 MB 517 MB 343 MB under 1 MB under 1 MB 418 MB 1845 MB 343 MB under 1 MB 418 MB 293 MB 1537 MB 2973 MB 349 MB under 1 MB under 1 MB 418 MB 293 MB 472 MB 343 MB under 1 MB under 1 MB under 1 MB Chapter 1. Planning the installation 9

16 Operating system Linux Installed components Directory Required space Serer and database, including the DB2 prerequisite Serer and database without the DB2 prerequisite Serer only Database, including the DB2 prerequisite Database without the DB2 prerequisite Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory /tmp /etc /ar /ar/tmp Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory Database installation directory /tmp /etc /ar 1889 MB 830 MB 556 MB 121 MB under 1 MB under 1 MB under 1 MB 1889 MB 509 MB 591 MB under 1 MB under 1 MB under 1 MB 1889 MB 591 MB under 1 MB 4MB under 1 MB 296 MB 830 MB 556 MB 121 MB under 1 MB 2MB under 1 MB 296 MB 509 MB 121 MB under 1 MB 2MB 10 Installation Guide

17 Operating system Solaris Installed components Directory Required space Serer and database, including the DB2 prerequisite Serer and database without the DB2 prerequisite Serer only Database, including the DB2 prerequisite Database without the DB2 prerequisite Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory /tmp /ar /ar/tmp Product installation directory DB2 installation directory Database installation directory /tmp /etc /ar /ar/tmp Product installation directory Database installation directory /tmp /etc /ar 1999 MB 1262 MB 2370 MB 216 MB under 1 MB 260 MB 259 MB 1999 MB 472 MB 182 MB under 1 MB 222 MB 222 MB 1971 MB 182 MB 259 MB 259 MB 181 MB 1262 MB 2370 MB 216 MB under 1 MB 259 MB 260 MB 181 MB 508 MB 181 MB under 1 MB under 1 MB Chapter 1. Planning the installation 11

18 Operating system Windows Installed components Directory Required space Serer and database, including the DB2 prerequisite Serer and database without the DB2 prerequisite Serer only Database, including the DB2 prerequisite Database without the DB2 prerequisite Product installation directory DB2 installation directory /tmp Database installation directory Product installation directory DB2 installation directory /tmp Database installation directory Product installation directory /tmp Product installation directory DB2 installation directory /tmp Database installation directory Product installation directory DB2 installation directory /tmp Database installation directory 1662 MB 530 MB 590 MB 437 MB 1881 MB under 1 MB 590 MB 437 MB 1881 MB 590 MB 123 MB 530 MB 590 MB 437 MB 123 MB under 1 MB 112 MB 437 MB Supported operating systems for the serer and database Ensure that the computer where you are installing the Tioli Asset Discoery for Distributed serer runs on one of the supported ersions of operating systems. IBM AIX Table 6. Supported ersions of IBM AIX Version Required leel, serice packs, patches 6.1 APAR IZ to apply the fix, the AIX 6.1 instance needs to be upgraded to Technology Leel (64-bit) When installing the DB2 database on AIX, you also need the xlc.aix*.rte or higher XL C/C++ runtime enironment which you can download from software/awdtools/xlcpp/support/ APAR IZ to apply the fix, the libc library is required 12 Installation Guide

19 HP-UX Table 7. Supported ersion of HP-UX Version 11i for PA-RISC (64-bit, in 32-bit compatibility mode) Required leel, serice packs, patches Red Hat Enterprise Linux Note: The serer and database and their prerequisites require 32-bit support. If you are installing a serer or database on a Red Hat Enterprise Linux 64-bit platform, you must ensure that 32-bit support is enabled. In addition to the required packages listed below, you also need to install the Compatibility Architecture Support or Compatibility Architecture Deelopment Support on your system. Table 8. Supported ersions of Red Hat Enterprise Linux Version ES/AS/WS 6 for EM64T and AMD64 (64 bit) Required leel, serice packs, patches compat-libstdc++-33 compat-libstdc Both 64-bit and 32-bit ersions of the following packages: compat-libstdc++ compat-db libxp AS, ersion 6 for IBM iseries and pseries (64-bit) The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux compat-libstdc++-33 compat-libstdc Both 64-bit and 32-bit ersions of the following packages: compat-libstdc++ compat-db libxp The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux Update 1 or later for LPAR mobility Chapter 1. Planning the installation 13

20 Table 8. Supported ersions of Red Hat Enterprise Linux (continued) Version AS, ersion 6 for IBM zseries (64 bit) Required leel, serice packs, patches Update 1, compat-libstdc++-33 compat-libstdc Both 64-bit and 31-bit ersions of the following packages: compat-libstdc++ compat-db libxp ES/AS/WS 5 for Intel x86 (32 bit) ES/AS/WS 5 for EM64T and AMD64 (64 bit) The following 31-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux compat-libstdc++-33 compat-libstdc++-33 compat-libstdc Both 64-bit and 32-bit ersions of the following packages: compat-libstdc++ compat-db libxp AS, ersion 5 for IBM iseries and pseries (64-bit) The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux compat-libstdc++-33 compat-libstdc Both 64-bit and 32-bit ersions of the following packages: compat-libstdc++ compat-db libxp The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux Update 1 or later for LPAR mobility 14 Installation Guide

21 Table 8. Supported ersions of Red Hat Enterprise Linux (continued) Version AS, ersion 5 for IBM zseries (64 bit) Required leel, serice packs, patches Update 1, compat-libstdc++-33 compat-libstdc Both 64-bit and 31-bit ersions of the following packages: compat-libstdc++ compat-db libxp ES/AS/WS 4 for Intel x86 (32 bit) ES/AS/WS 4 for EM64T and AMD64 (64 bit) The following 31-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux compat-libstdc++-33 compat-libstdc++-33 compat-libstdc Both 64-bit and 32-bit ersions of the following packages: compat-libstdc++ compat-db libxp AS, ersion 4 for IBM iseries and pseries (64-bit) The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux compat-libstdc++-33 compat-libstdc Both 64-bit and 32-bit ersions of the following packages: compat-libstdc++ compat-db xorg-x11-deprecated-libs or xorg-x11-deprecated-libs The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux Chapter 1. Planning the installation 15

22 Table 8. Supported ersions of Red Hat Enterprise Linux (continued) Version AS, ersion 4 for IBM zseries (64 bit) Required leel, serice packs, patches compat-libstdc++-33 compat-libstdc Both 64-bit and 31-bit ersions of the following packages: compat-libstdc++ compat-db xorg-x11-deprecated-libs or xorg-x11-deprecated-libs The following 31-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux SUSE Linux Enterprise Serer Table 9. Supported ersions of SUSE Linux Enterprise Serer Version Required leel, serice packs, patches 11 for Intel/AMD x86 11 for EM64T and AMD64 pam-modules-32bit 11 for IBM iseries/pseries (64-bit) pam-modules-32bit 11 for IBM zseries (64-bit) on 64-bit pam-modules-32bit hardware 10 for Intel/AMD x86 compat-libstdc++ 10 for EM64T and AMD64 If you plan to install DB2 9.7: Serice Pack 2 glibc libaio-64bit The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux The following 64-bit ersion packages: xorg-x11-libs-64bit ppc.rpm expat-64bit ppc.rpm fontconfig-64bit ppc.rpm freetype2-64bit ppc.rpm pam-modules-32bit 16 Installation Guide

23 Table 9. Supported ersions of SUSE Linux Enterprise Serer (continued) Version Required leel, serice packs, patches 10 for IBM iseries/pseries (64-bit) compat-libstdc++ Serice Pack 1 or later for LPAR mobility If you plan to install DB2 9.7: Serice Pack 2 glibc libaio-64bit acpp.rte xlsmp.msg.rte xlsmp.rte The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux 10 for IBM zseries (64-bit) on 64-bit hardware The following 64-bit ersion packages: xorg-x11-libs-64bit ppc.rpm expat-64bit ppc.rpm fontconfig-64bit ppc.rpm freetype2-64bit ppc.rpm compat-libstdc++ If you plan to install DB2 9.7: Serice Pack 2 glibc libaio-64bit acpp.rte The following 31-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux The following 64-bit ersion packages: xorg-x11-libs-64bit ppc.rpm expat-64bit ppc.rpm fontconfig-64bit ppc.rpm freetype2-64bit ppc.rpm 9 for Intel x86 Serice Pack 3, compat-libstdc++ pam s390.rpm Chapter 1. Planning the installation 17

24 Table 9. Supported ersions of SUSE Linux Enterprise Serer (continued) Version Required leel, serice packs, patches 9 for EM64T and AMD64 compat-libstdc++ The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux 9 for IBM iseries/pseries (64-bit) Serice Pack 3a for iseries Serice Pack 3 for pseries The following 32-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux 9 for IBM zseries (64-bit) compat-libstdc++ The following 31-bit ersion packages: pam cracklib-dicts cracklib glib2 libselinux Sun Solaris Table 10. Supported ersions of Sun Solaris Version 10 Operating System for SPARC platforms (64-bit) 9 Operating System for SPARC platforms (64-bit) Required leel, serice packs, patches Windows Table 11. Supported ersions of Windows Version Required leel, serice packs, patches Serer 2008 R2 Datacenter (64-bit) for Intel x86(db2 9.5 and 9.7 only) Serer 2008 R2 Standard Edition (64-bit) for Intel x86(db2 9.5 and 9.7 only) Serer 2008 R2 Enterprise Edition (64-bit) for Intel x86(db2 9.5 and 9.7 only) 18 Installation Guide

25 Table 11. Supported ersions of Windows (continued) Version Serer 2008 Standard Edition (32-bit and 64-bit) for Intel x86 Serer 2008 Enterprise Edition (32-bit and 64-bit) for Intel x86 Serer 2003 Standard Edition (32-bit and 64-bit) Serer 2003 Enterprise Edition (32-bit and 64-bit) Required leel, serice packs, patches Supported partitioning technologies - serers Any partitioning technology that runs one of the supported operating systems mentioned aboe. Other software prerequisites for the serer and database Ensure that all prerequisite software is installed on the computer where you are installing the Tioli Asset Discoery for Distributed serer. Tioli Asset Discoery for Distributed includes the major software prerequisites, DB2 ersion 9.1 and WebSphere Application Serer ersion 6.1. You hae two options for installing the WebSphere software prerequisite: If you do not plan to support more than 5000 agents, you can install an embedded ersion of the WebSphere Application Serer from the Tioli Asset Discoery for Distributed wizard. To support a larger infrastructure, you must install a base ersion of WebSphere Application Serer before installing Tioli Asset Discoery for Distributed. You can install the base edition using the V6.1 installation media that are proided with this product, or you can use an existing installation of WebSphere Application Serer V6.1 or later. For more details about WebSphere installation, refer to the WebSphere information center. You hae three options for installing the DB2 software prerequisite: You can choose to install it at the same time as Tioli Asset Discoery for Distributed, from the installation wizard. You can install it ahead of time, using the installation media proided with Tioli Asset Discoery for Distributed. You can use an existing license of DB2 that you hae already installed. Refer to the following table for required software leels. Note: Install DB2 before you install the serer to be able to customize DB2 and troubleshoot problems that might occur during its installation. The following table summarizes additional software prerequisites. Chapter 1. Planning the installation 19

26 Software Serer Database drier JDBC drier type 4 is automatically installed if not already present. UNIX shell To install the serers on UNIX platforms you must hae the Bourne shell (sh) installed and actiated. It is not necessary to run the installation from the Bourne shell. You also need to install and actiate the Korn shell. Web browser A web browser is required to access the web user interface of the serer. It is also needed for the installation launchpad to start; howeer, it is also possible to start the installation of Tioli Asset Discoery for Distributed without the launchpad. Database Supported browsers on different platforms: Supported MS Windows ersions Internet Explorer 6.x, and 7.x, Firefox 2.0.x Other supported platforms Firefox 2.0.x Note: It is important not to turn the JaaScript option off in the browser as some of the functionalities of the web interface might not function properly. For secure connections, cookies need to be enabled. Database serer One of the following ersions: DB2, Enterprise Serer Edition serer, ersion 9.7 DB2, Enterprise Serer Edition serer, ersion 9.5 DB2, Enterprise Serer Edition serer, ersion 9.1 Note: 1. The DB2 serer must be configured for remote communication - the scename parameter needs to be set. 2. You must apply DB2 9.1 Fix Pack 4 to install on AIX 6.1 machines. 3. If you want to install DB2 9.1 on Windows Serer 2008, you need to apply the following fix packs: for Windows Serer 2008, DB2 9.1, Fix Pack 4 for non-partitioned DB2 systems that use Windows Serer 2008 Failoer Clusters, DB2 9.1 Fix Pack 5 for partitioned database enironments that use Windows Serer 2008 Failoer Clusters, DB2 9.1 Fix Pack 6 4. DB2 9.1 is not supported on Windows Serer 2008 R2. UNIX shell To install the databases on UNIX platforms you must hae the korn shell (ksh) installed and actiated. It needs to be set as the default shell for the DB2 instance owner. Note: The shell must be present but the setup command to install the database can be issued from any shell not necessarily the korn shell. 20 Installation Guide

27 Supported ersions of WebSphere Application Serer For large production enironments, you may want to install the serer on a base ersion of WebSphere Application Serer, instead of the embedded ersion that can be installed as a part of Tioli Asset Discoery for Distributed. Tioli Asset Discoery for Distributed supports the following ersion of WebSphere: WebSphere Application Serer, ersion 6.1, Fix Pack 23, Fix Pack 29 or later WebSphere Application Serer Network Deployment, ersion 6.1 (standard application serer profile only), Fix Pack 23, Fix Pack 29 or later Note: If you are installing on the Base ersion of WebSphere Application Serer, with enabled secure agent-serer communication, you must apply a Jaa update on WebSphere Application Serer. You can download the update from the following page: &uid=swg If you do not apply the Jaa update, the secure communication will not work properly. Depending on the security leel, the agent will be able to connect to the serer but other operations such as catalog download or the import of a priate certificate when configuring agents will cause GSKit exceptions. Agent hardware and software requirements The topics in this section contain information about hardware and software prerequisites that need to be fulfilled when deploying Tioli Asset Discoery for Distributed agents. Supported operating systems for the agents Ensure that the computer where you are installing the agent runs on one of the supported operating systems. Chapter 1. Planning the installation 21

28 IBM AIX Table 12. Supported ersions of IBM AIX Version Required leel, serice packs, patches 6.1 APAR IZ this fix is required if you are installing the agent in a WPAR enironment. APAR IZ this fix is required if you are installing the agent in a WPAR enironment and using WPAR or LPAR mobility/relocation. To apply the fix for IZ44998, the AIX 6.1 instance needs to be upgraded to Technology Leel 3. Supported partitioning technologies LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning PowerVM - Multiple Shared Processor Pools PowerVM - Shared Dedicated Processor System WPARs (both regulated and un-regulated, also RSET bound) Application WPARs LPAR mobility (Lie Partition Mobility) WPAR mobility (Lie Application Mobility) APAR IZ this fix is required for Technology Leel 4. AIX Technology Leel or higher is recommended in both LPARs between which a WPAR (with an agent installed) is being relocated. 5.3 xlc.aix50.rte or later Technology Leel 3 to support sub capacity pricing on Power 5 Note: Leel 3 is a minimum requirement, but use Technology Leel 7 to support Multiple Processor Shared Pools. Technology Leel 7 or later for LPAR mobility 5.2 xlc.aix50.rte or later APAR IY51805 LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning PowerVM - Multiple Shared Processor Pools PowerVM - Shared Dedicated Processor LPAR mobility (Lie Partition Mobility) LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool 22 Installation Guide

29 IBM i Table 13. Supported ersions of IBM i Version Required leel, serice packs, patches V6R1 V5R4 V7R1 PTF SI38154 for 5770SS1 Options 13 and 30 of 5770SS1 PTF SI38115 for 5761SS1 Options 13 and 30 of 5761SS1 LIC PTF MF46769 (if you are using secure communication) PTF SI38116 for 5722SS1 Supported partitioning technologies LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning PowerVM - Multiple Shared Processor Pools PowerVM - Shared Dedicated Processor LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning PowerVM - Multiple Shared Processor Pools PowerVM - Shared Dedicated Processor V5R3 Options 13 and 30 of 5722SS1 Crypto Access Proider 128-bit, PID: 5722AC3 (if secure communication is to be used) PTF SI33011 for 5722SS1 Options 13 and 30 of 5722SS1 PTF MF34223 to support sub capacity pricing on Power 5 Crypto Access Proider 128-bit, PID: 5722AC3 (if secure communication is to be used) LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning Chapter 1. Planning the installation 23

30 HP-UX Table 14. Supported ersions of HP-UX Version Required leel, serice packs, patches 11i 3 on PA-RISC 11i 2 on PA-RISC 64-bit (in 32-bit compatibility mode) Quality Pack Depot for 11i 2, September 2006 PHKL_35709 (s700_ pthread_cond_timedwait, hires timers, callout) PHCO_39699 (s700_ pthread library cumulatie patch) 11i 1 for PA-RISC PHSS_26946 PHSS_33033 PHCO_ i 3 on Itanium 2 Integrity Serer 11i 2 on Itanium 2 Integrity Serer Quality Pack Depot for 11i 2, September 2006 PHKL_35709 (s700_ pthread_cond_timedwait, hires timers, callout) PHCO_39699 (s700_ pthread library cumulatie patch) Supported partitioning technologies npar PAR npar PAR HP Integrity Virtual Machines 3.5 HP Integrity Virtual Machines 4.0 HP Integrity Virtual Machines 4.1 HP Integrity Virtual Machines 4.2 npar PAR Red Hat Enterprise Linux Table 15. Supported ersions of Red Hat Enterprise Linux Version Required leel, serice Supported partitioning technologies packs, patches 6 for Intel/AMD x86 (64-bit) compat-libstdc++-33 VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect 24 Installation Guide

31 Table 15. Supported ersions of Red Hat Enterprise Linux (continued) Version Required leel, serice Supported partitioning technologies packs, patches 6 for Intel/AMD x86 (32-bit) compat-libstdc++-33 VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect 6 for IBM iseries and compat-libstdc++-33 LPAR pseries (64-bit) PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning LPAR mobility (Lie Partition Mobility) 6 for IBM zseries compat-libstdc++-33 LPAR (31-bit) on 64-bit z/vm hardware 5 for Intel/AMD x86 (64-bit) compat-libstdc++-33 VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect Chapter 1. Planning the installation 25

32 Table 15. Supported ersions of Red Hat Enterprise Linux (continued) Version Required leel, serice packs, patches Supported partitioning technologies 5 for Intel/AMD x86 (32-bit) compat-libstdc++-33 VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit 5 for IBM iseries and pseries (64-bit) 5 for IBM zseries (31-bit) on 64-bit hardware ES/AS/WS 4 for Intel/AMD x86 (64-bit) compat-libstdc++-33 Update 1 or later for LPAR mobility compat-libstdc++-33 compat-libstdc++-33 System scaling using Intel QuickPath Interconnect LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning LPAR mobility (Lie Partition Mobility) LPAR z/vm VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect 26 Installation Guide

33 Table 15. Supported ersions of Red Hat Enterprise Linux (continued) Version Required leel, serice packs, patches Supported partitioning technologies ES/AS/WS 4 for Intel/AMD x86 (32-bit) Compatibility packs: 1. libgcc (32-bit) 2. compat-libstdc++-33 (must be installed in the specified order) VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit AS, ersion 4 for IBM iseries and pseries (64-bit) AS, ersion 4 for IBM zseries 64 bit AS, ersion 4 for IBM zseries (31-bit ) on 64-bit hardware Compatibility packs: 1. libgcc (32-bit) 2. compat-libstdc++-33 (must be installed in the specified order) compat-libstdc++-33 System scaling using Intel QuickPath Interconnect LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning LPAR z/vm LPAR z/vm Red Hat Linux Desktop Table 16. Supported ersions of Red Hat Linux Desktop Version Required leel, serice Supported partitioning technologies packs, patches ersion 6 for Intel/AMD x86 (32 and 64-bit) compat-libstdc++-33 ersion 5 for Intel/AMD x86 (32-bit) ersion 4 for Intel/AMD x86 (32-bit) compat-libstdc++-33 compat-libstdc++-33 Chapter 1. Planning the installation 27

34 SUSE Linux Enterprise Serer Table 17. Supported ersions of SUSE Linux Enterprise Serer Version Required leel, serice packs, patches Supported partitioning technologies 11 for Intel/AMD x86 (32 and 64-bit) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit 11 for IBM iseries/pseries (64-bit) 10 for IBM zseries (64-bit) on 64-bit hardware 10 for Intel/AMD x86 (32-bit and 64-bit) compat-libstdc++ compat-libstdc++ System scaling using Intel QuickPath Interconnect LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning APV - Lie Partition Mobility LPAR z/vm VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect 28 Installation Guide

35 Table 17. Supported ersions of SUSE Linux Enterprise Serer (continued) Version Required leel, serice packs, patches Supported partitioning technologies 10 for IBM iseries/pseries (64-bit) 10 for IBM zseries (64-bit) on 64-bit hardware 9 for Intel/AMD x86 (32-bit) compat-libstdc++ Serice Pack 1 for LPAR mobility compat-libstdc++ compat-libstdc++ LPAR PowerVM - DLPAR PowerVM - Single Shared Processor Pool PowerVM - Micro-Partitioning LPAR mobility (Lie Partition Mobility) LPAR z/vm VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit 9 for Intel/AMD x86 (64-bit) System scaling using Intel QuickPath Interconnect VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect Noell Linux Desktop Table 18. Supported ersions of Noell Linux Desktop Version Required leel, serice Supported partitioning technologies packs, patches 9 for Intel/AMD x86 (64-bit) compat-libstdc++ Chapter 1. Planning the installation 29

36 Table 18. Supported ersions of Noell Linux Desktop (continued) Version Required leel, serice Supported partitioning technologies packs, patches 9 for Intel/AMD x86 (32-bit) compat-libstdc++ SUSE Linux Enterprise Desktop Table 19. Supported ersions of SUSE Linux Enterprise Desktop Version Required leel, serice packs, patches Supported partitioning technologies 10 for Intel/AMD x86 compat-libstdc++ (32-bit) System scaling using Intel QuickPath Interconnect Sun Solaris Table 20. Supported ersions of Sun Solaris Version Required leel, serice packs, patches 10 Operating System for x86 (64-bit) 10 Operating System for SPARC and UltraSPARC (64-bit) 9 Operating System for UltraSPARC (32 bit and 64-bit) 8 Operating System for UltraSPARC (32-bit and 64-bit) Patches: Supported partitioning technologies Containers/Zones BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit Dynamic System Domains. Solaris in Dynamic System Domains is supported but not for full capacity. Full capacity PVU alues will need to be adjusted upward manually for the number of actiated cores on the serer. Containers/Zones: inside Dynamic System Domains Containers/Zones: node OS Dynamic System Domains. Solaris in Dynamic System Domains is supported but not for full capacity. Full capacity PVU alues will need to be adjusted upward manually for the number of actiated cores on the serer. Windows Table 21. Supported ersions of Windows Version Required leel, serice packs, patches 7 Professional, Ultimate, and Enterprise Supported partitioning technologies VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) System scaling using Intel QuickPath Interconnect 30 Installation Guide

37 Table 21. Supported ersions of Windows (continued) Version Required leel, serice packs, patches Supported partitioning technologies Vista Enterprise, Ultimate, and Business (32-bit and 64-bit) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit Serer 2008 R2 Standard and Enterprise (64-bit) for Intel x86 System scaling using Intel QuickPath Interconnect VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect Chapter 1. Planning the installation 31

38 Table 21. Supported ersions of Windows (continued) Version Required leel, serice packs, patches Supported partitioning technologies Serer 2008 Standard and Enterprise (32-bit and 64-bit) for Intel x86 VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Serer 2003 R2 (32-bit and 64-bit) Serer 2003 Datacenter (32-bit and 64-bit) XP Professional Serice Pack 2 Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit (with the exception of XP) System scaling using Intel QuickPath Interconnect 32 Installation Guide

39 Table 21. Supported ersions of Windows (continued) Version Required leel, serice packs, patches Supported partitioning technologies Serer 2003 Enterprise, and Standard Edition (32-bit and 64-bit) Serice Pack 2 VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Virtual Serer 2005 Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect Chapter 1. Planning the installation 33

40 Table 21. Supported ersions of Windows (continued) Version Required leel, serice Supported partitioning technologies packs, patches Windows 2000 Serer Serice Pack 3 or later Windows 2000 Adanced Serer mscp60.dll (for installing in interactie and silent mode) The minimum display setting must be at least 256 colors (for installing in interactie mode). VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) Microsoft Virtual Serer 2005 Microsoft Hyper-V 2008 Microsoft Hyper-V Serer 2008 R2 Role Microsoft Windows Serer 2008 R2 with Hyper-V Windows 2000 Professional Serice Pack 3 or later mscp60.dll (for installing in interactie and silent mode) The minimum display setting must be at least 256 colors (for installing in interactie mode). Microsoft Windows Serer 2008 R2 Hyper-V BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect VMware ESX Single Serer, Serer Farm, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi 4 - Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESX Single Serer, Cluster, Mobility (VMware Vmotion) VMware ESXi Single Serer, Cluster, Mobility (VMware Vmotion) BIOS (SMBIOS 2.5 or higher) & Operating System boot core limit System scaling using Intel QuickPath Interconnect 34 Installation Guide

41 VMware and Microsoft irtualization considerations Both the serer and agents can be installed in the host and guest operating systems of computers partitioned using VMware and Microsoft irtualization technologies. In the case of agent installation, some technologies require the deployment of the Common Inentory Technology enabler. Due to the nature of the VMware and Microsoft Virtual Serer irtualization technologies, agents deployed on them are not able to gather data about the host computer systems. Therefore, they are not able to gather and send information about, for example, processor types or number of processor cores. Without this kind of information, it is impossible to calculate processor alue unit (PVU) capacity for a gien software. To preent this, you can use a irtual machine manager to administer your irtual machines. VM managers are used to collect some additional information concerning irtual machines that are installed in your infrastructure, and they allow the serer to process the data collected by the agents. Connecting to a VM manager is the recommended solution for Tioli Asset Discoery for Distributed. You can also schedule the Common Inentory Technology enabler script to run on the host at regular interals to detect any changes in the configuration of partitions. This method is only recommended if you are not using VM manager or your machine cannot be connected to a irtual machine manager. Common Inentory Technology enabler is required on partitions not managed by a irtual machine manager for the following irtualization technologies: Microsoft Virtual Serer VMware ESX Serer 4.0 VMware ESX Serer 3.5 VMware ESX Serer 3.0 VMware ESX Serer 2.5 VMware Serer 1.0. On VMware ESX Serer 2.5, 3.0 and 3.5 the enabler can also be run on partitions which are managed through a serer using VMware Virtual Center. Howeer, it is recommended to use the VM manager in those cases. Important: You hae to use VM managers in cluster enironments to ensure that the irtual machine hierarchy is built correctly. Note that in such situations, you should not use Common Inentory Technology enabler because it cannot proide complete information about cluster topology. Other software requirements for the agents Ensure that the corequisite software is installed on the computer where you are installing the agent. Software corequisites for agents Deployment of the agent includes the deployment of corequisite software - Global Security Toolkit, Common Inentory Technology, and, on platforms where irtual machines are not administered by VM managers, also Common Inentory Technology enabler. Chapter 1. Planning the installation 35

42 Global Security Toolkit is used to proide security between monitoring components. A new ersion of Global Security Toolkit will be installed by the agent regardless of any ersions that may already present on the machine. It cannot be shared by other applications that are installed on this machine. Note: IBM i The agent does not install Global Security Toolkit, instead using the ersion that is already part of the system framework. Global Security Toolkit Operating Version Global Security Toolkit Version System IBM i V5R3, V5R4, V6R1 6b Other platforms Common Inentory Technology is a component technology used to collect hardware, software, file system, and registry information from systems in a network. Common Inentory Technology might already be deployed for use by other applications on the target computer so the deployment process checks that the installed ersion is supported for the Tioli Asset Discoery for Distributed agent. If the installed ersion is older than recommended, it is upgraded to the supported one. Common Inentory Technology enabler is a script that enables the Common Inentory Technology to obtain information about partitioned enironments. It is required by the agent on systems not managed by VM managers such as ESX or Virtual Center. Common Inentory Technology enabler Partitioning Platform Files Subdirectory technology VMWare Windows cpuid.exe wenmw.exe retriee.pl enabler\vmware\w32-ix86 Microsoft Virtual Serer Linux Windows cpuid wenmw.sh retriee.pl dispatcher cpuid.exe wenmss.exe ESX 2.5 enabler\vmware\esx-2.5 Other serers enabler\vmware\linuxix86 enabler\msvirtualserer Tools required to install the agent on a irtual machine If you are installing the agent in a partitioned enironment, you may need to install and actiate the irtualization tools required by some partitioning technologies. 36 Installation Guide

43 Table 22. Partitioning technology prerequisites Partitioning technology Tool VMware Serer 1.0 VMware ESX 2.5 VMware ESX 3.0 VMware ESX 3.5 VMware ESXi 3.5 VMware ESX 4 VMware ESXi 4 Microsoft Virtual Serer 2005 HP Integrity Virtual Machines VMware Tools - optional. If you do not use VM manager to augment the data reported by agents, they will be in 'Incomplete' state and will report the wrong topology and measures. Microsoft Virtual Machine Additions Host operating system HPVM package Guest operating system HPVM-Guest The installation of the lspd utility on Power5+ QCM processors On POWER 5+ QCM processors, you need to install the lspd utility on the target system. The lspd utility is proided by IBM for free and it is included in the "IBM Installation Toolkit for Linux" aailable for download from www14.software.ibm.com/webapp/set2/sas/f/lopdiags/installtools/home.html. The latest ersion of the lspd package is also aailable for download from "Serice and productiity tools for Linux on POWER systems" at After the installation of the lspd utility, you need to initialize the database by issuing the following command: /etc/init.d/lspd start Disk space requirements Before deploying the Tioli Asset Discoery for Distributed agents, and the WebSphere agent, ensure that your machine has the required amount of disk space. For all agent deployment methods, a space check is made to ensure that the installation will not start and then fail because of lack of sufficient space in the agent installation directory. If the space aailable is insufficient, the installation fails with return code -17. Table 23. Tioli Asset Discoery for Distributed agent space requirements Operating system Directory Space required Chapter 1. Planning the installation 37

44 Table 23. Tioli Asset Discoery for Distributed agent space requirements (continued) AIX Agent installation directory (default: /ar/itlm) 55 MB WebSphere agent directory (additional space in agent 230 MB installation directory) Temporary directory (default: /tmp) 70 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: /.swdis) 35 MB Directory for configuration files (default: /etc) under 1 MB Common Inentory Technology (default directory: /opt/tioli/cit) 30 MB HP-UX on PA-RISC Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Agent installation directory (default: /ar/itlm) WebSphere agent directory (additional space in agent installation directory) Temporary directory (default: /tmp) Tioli_Common_Directory/COD SWDCLI registry directory (default: /.swdis) Directory for configuration files (default: /etc) Common Inentory Technology (default directory: /opt/tioli/cit) Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. 100 MB 200 MB 90 MB 10 MB 35 MB under 1 MB 30 MB Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. 38 Installation Guide

45 Table 23. Tioli Asset Discoery for Distributed agent space requirements (continued) HP-UX on Itanium 2 Integrity Serer Agent installation directory (default: /ar/itlm) WebSphere agent directory (additional space in agent installation directory) Temporary directory (default: /tmp) Tioli_Common_Directory/COD SWDCLI registry directory (default: /.swdis) Directory for configuration files (default: /etc) Common Inentory Technology (default directory: /opt/tioli/cit) Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) 130 MB 200 MB 120 MB 10 MB 55 MB under 1 MB 50 MB Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. IBM i Agent installation directory 80 MB WebSphere agent directory in agent installation directory 150 MB Temporary directory (default: /tmp) 130 MB Tioli_Common_Directory/COD 10 MB Common Inentory Technology (default directory: /opt/tioli/cit) 55 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. Chapter 1. Planning the installation 39

46 Table 23. Tioli Asset Discoery for Distributed agent space requirements (continued) Linux x86 Agent installation directory (default: /ar/itlm) 40 MB WebSphere agent directory (additional space in agent 200 MB installation directory) Temporary directory (default: /tmp) 50 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: /root/.swdis) 20 MB Directory for configuration files (default: /etc) under 1 MB Common Inentory Technology 30 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. Linux pseries Agent installation directory (default: /ar/itlm) 40 MB WebSphere agent directory (additional space in agent 200 MB installation directory) Temporary directory (default: /tmp) 50 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: /root/.swdis) 20 MB Directory for configuration files (default: /etc) under 1 MB Common Inentory Technology 30 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. 40 Installation Guide

47 Table 23. Tioli Asset Discoery for Distributed agent space requirements (continued) Linux zseries Agent installation directory (default: /ar/itlm) 100 MB WebSphere agent directory (additional space in agent 200 MB installation directory) Temporary directory (default: /tmp) 60 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: /root/.swdis) 25 MB Directory for configuration files (default: /etc) under 1 MB Common Inentory Technology 30 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. Solaris on x86 Agent installation directory (default: /ar/itlm) 50 MB WebSphere agent directory (additional space in agent 200 MB installation directory) Temporary directory (default: /tmp) 55 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: /opt/tioli/swdis) 25 MB Directory for configuration files (default: /etc) under 1 MB Common Inentory Technology (default directory: /opt/tioli/cit) 25 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. Chapter 1. Planning the installation 41

48 Table 23. Tioli Asset Discoery for Distributed agent space requirements (continued) Solaris on SPARC Agent installation directory (default: /ar/itlm) 55 MB WebSphere agent directory (additional space in agent 200 MB installation directory) Temporary directory (default: /tmp) 65 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: /.swdis) 25 MB Directory for configuration files (default: /etc) under 1 MB Common Inentory Technology (default directory: /opt/tioli/cit) 25 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. Windows Agent installation directory (default: %WINDIR%/itlm). 35 MB WebSphere agent directory (additional space in agent 200 MB installation directory) Temporary directory (default: %TEMP%) 30 MB Tioli_Common_Directory/COD 10 MB SWDCLI registry directory (default: C:\swdis) 10 MB Directory for configuration files (default: %WINDIR%) under 1 MB Common Inentory Technology (default directory: C:\Program Files\tioli\cit) 10 MB Common Inentory Technology cache files (default: /opt/tioli/cit/cache_data/ username) Depends on the number of files, directories, and subdirectories to be scanned. Can be estimated by multiplying the number of files to be scanned by 40 bytes. 42 Installation Guide

49 Supported enironments for J2EE application monitoring The Tioli Asset Discoery for Distributed agent has a subagent that is responsible for monitoring J2EE applications. The WebSphere agent supports the following ersions of WebSphere: WebSphere Application Serer, ersion 7.0 WebSphere Application Serer, ersion 6.1 (excluding ersions with fix packs and ) WebSphere Application Serer, ersion 6.0 WebSphere Application Serer, ersion 5.1 WebSphere Application Serer, ersion 5.0 WebSphere Portal, ersion 6.1 WebSphere Portal, ersion 6.0 WebSphere Portal, ersion 5.1 WebSphere Portal, ersion 5.0 The WebSphere agent supports the following editions of the aboe mentioned ersions of WebSphere: WebSphere Application Serer, Network Deployment edition WebSphere Application Serer, Base edition When WebSphere Portal is installed, the file itlm.product exists in the WebSphere_Portal_Root\ersion directory. This fie contains entries that identify WebSphere portal products and ersions. For WebSphere Portal 5.0 and 5.1, to enable Tioli Asset Discoery for Distributed monitoring of products that you hae installed on WebSphere portal, you must edit the file and uncomment the lines that relate to ersion of your WebSphere Portal. For WebSphere Portal 6.0 and higher, it is enough to erify that the itlm.product file exists. The WebSphere Application Serer agent is automatically installed on monitored computers when a supported ersion of the WebSphere Application software is present. Support for high aailability enironments This topic proides information about the conditions in which monitoring of high aailability enironments, managed by IBM High Aailability Cluster Multiprocessing, has been alidated. Tioli Asset Discoery for Distributed agent is able to collect both use and install information about products running within high aailability clusters managed by High Aailability Cluster Multiprocessing. The following scenarios hae been alidated: High Aailability Cluster Multiprocessing configurations Hot StandBy Mutual Takeoer Concurrent Access with or without IBM General Parallel File System High Aailability Cluster Multiprocessing Policy Rotating Chapter 1. Planning the installation 43

50 Tioli Asset Discoery for Distributed configuration Agents installed on each node that is participating in the cluster, communicating correctly with serers, and not inoled in any high aailability switching. Applications Running on the local node with binaries located in file systems that are isible to High Aailability Cluster Multiprocessing or by General Parallel File System as local files. Supported software installed in High Aailability enironments is properly detected by Tioli Asset Discoery for Distributed, which means that processor alue unit consumption is calculated. If your software agreement allows for reduced processor alue unit consumption (e.g. in case of Hot StandBy), you can disable PVU calculation for your software installed in High Aailability Cluster Multiprocessing enironment by excluding one or more software instances. Support for system scaling using Intel QuickPath Interconnect IBM Tioli Asset Discoery for Distributed proides support for system scaling using Intel QuickPath Interconnect that enables scalable PVU consumption. The support has been introduced with Fix Pack 1 for Tioli Asset Discoery for Distributed IBM System x has introduced a new technology based on Intel Xeon Nehalem-EX processors and a feature called Intel QuickPath Interconnect. With this technology you can join two computers with a physical link, which increases the capacity of one of the computers. The increased number of cores is reflected in the full capacity of a computer and its PVU alue per core. The table illustrates the change in the capacity and PVU alue after 2 computers hae been linked with the QuickPath Interconnect link: Computer A capacity 2 sockets with Intel Xeon (Nehalem-EX) 4 cores with 70 PVU each Computer B capacity 2 sockets with Intel Xeon (Nehalem-EX), 4 cores with 70 PVU each The capacity of both computers linked with QuickPath Interconnect Computer A: 4 sockets and 16 cores with 100 PVU each Computer B: Offline When you link two computers with the use of QuickPath Interconnect, the reports generated might not proide information about the actual number of cores on both computers. The table illustrates the problem: Day 1: the computers are separated Computer A: Computer B: 2 sockets 2 sockets 8 cores 8 cores 70 PVU per core 70 PVU per core 1 agent with DB2 and WebSphere Application Serer installed 1 agent with DB2 installed Day 2, 10 a.m.: computer B is connected to computer A with the QuickPath Interconnect link 44 Installation Guide

51 Computer A: 4 sockets 16 cores 100 PVU per core 1 agent with DB2 and WebSphere Application Serer installed Computer B: The report generated for day 2 lists the following items: DB2: 24 cores WebSphere Application Serer: 16 cores Offline from 10 a.m. There is no technical possibility to automatically detect the problem and exclude computer B from the report for day 2. The situation might result in oercharging. To preent the problem, you can either disable the agent the day before you connect the computers (UTC time), or exclude the miscalculated product instances on the agent on computer B from the report. To disable the agent: 1. Shut down or uninstall the agent on computer B one day before the connection date. 2. Remoe the agent from the Tioli Asset Discoery for Distributed Web user interface. 3. Connect the computers the next day. To exclude the miscalculated product instances on the agent on computer B from the report: 1. Close the current audit report the day before the connection date. 2. Connect the computers the next day. 3. Exclude the miscalculated product instances on agent B from the report. Supported national languages for IBM i agents You must install one of the supported languages as your primary or secondary language on the IBM i node. Installed languages on IBM i Language code Language 2924 English 2928 French 2929 German 2931 Spanish 2932 Italian 2962 Japanese 2975 Czech 2976 Hungarian 2978 Polish 2979 Russian 2980 Portuguese (Brazil) 2986 Korean Chapter 1. Planning the installation 45

52 Installed languages on IBM i 2987 Traditional Chinese 2989 Simplified Chinese Topology and capacity planning Before installing Tioli Asset Discoery for Distributed to monitor the installed software in your organization, you need to determine what additional serer software you need, based on the size of your IT infrastructure, and how large the database might grow. Scan groups Scan groups are units for grouping agents. Scans of installed software and hardware are scheduled on a scan group leel. Decide how you want to diide agents between scan groups so that the operations which you can perform by scan groups are meaningful within your organization. Each agent must be assigned to a scan group. Note: Creating scan groups is not mandatory but preferable. There is always a default scan group to which agents are assigned by default. Placement of serer components For performance reasons, it is recommended that you install the serer software on a dedicated computer or on a dedicated partition (It means Tioli Asset Discoery for Distributed can consume all of the aailable processor and memory resources allocated to a dedicated computer/partition). You can install the database on the same computer/partition as the serer or on a different one. If you are installing the database on a different computer/partition than the serer, you must run the installer twice on both computers/partitions. Depending on the size of your IT infrastructure, you need to make the following choices: If you will support fewer than 5000 agents, you can install the limited-use ersion of WebSphere Application Serer software that is embedded with Tioli Asset Discoery for Distributed. If you will support more than 5000 agents, it is recommended that you install base WebSphere Application Serer ersion 6.1 or higher on the computer where you will install the Tioli Asset Discoery for Distributed serer. One instance of WebSphere Application Serer can support up to agents. Placement of agents In a partitioned operating enironment, you must install agents on eery guest operating system that hosts the software products for which you need to monitor license compliance. Agent backward compatibility The following ersions of Tioli Asset Discoery for Distributed agents are able to connect to the Tioli Asset Discoery for Distributed serer: Tioli Asset Discoery for Distributed 7.2 GA, and fix pack 1 46 Installation Guide

53 7.1 GA, and fix pack 1 Tioli License Compliance Manager 2.3 fix pack 4, 5, 6, and 7 Using secure communications The use of secure communications between the infrastructure elements is described fully in the "Security" section of the information center. Network planning Tioli Asset Discoery for Distributed and its agents do not generate heay data traffic for extended periods of time. Howeer, some network planning is required. A single agent does not require high bandwidth for the communication with the serer. The amount of data exchanged with the Tioli Asset Discoery for Distributed serer can be as high as 350 kilobytes in a 24-hour timeframe (This includes the upload of software and hardware scan results). If the database is installed on a separate computer from the monitoring serer, proide a high-speed connection between the two. Secure communication can hae an impact both on network traffic and serer performance, especially on the maximum security leel. Tioli Asset Discoery for Distributed uses the following ports for the data exchange between the serer and its agents. Note: The ports below are only the default alues and can be changed during the installation. Table 24. Ports used by Tioli Asset Discoery for Distributed Type User Interface Value 8899 (http) and 8888 (https) These ports are default ports for embedded WebSphere Application Serer. If you are not using default ports, you can check the port alues in Installation_folder/admin/master.tag. For the base ersion of WebSphere Application Serer, the port numbers are characteristic for the profile on which the product is deployed. Agent-serer communication 9988 (http), 9999 (https) and 9977 (https with client authentication) Database (DB2) default alue of For information about configuring DB2 ports see com.ibm.db2.udb.uprun.doc/doc/t htm. Security considerations There are some security issues that you need to take into consideration while installing and configuring the Tioli Asset Discoery for Distributed. Chapter 1. Planning the installation 47

54 Required access priileges for the installation In order to install the Tioli Asset Discoery for Distributed serer or agent you need to log on to the computer where you want to install the software as a user with administratie rights on Windows or as a root on Unix platforms. The only exception to this rule is if you are installing agents using IBM Tioli Configuration Manager. Database user IDs During the installation process, you need to specify a user ID and password for performing DB2 administratie tasks, such as creating and dropping databases. You also need to proide a password for the tlmsr ID, which is used by serer processes to access the database. Local operating system registries The administration serer uses only local operating system user registries during the installation of the administration serer - Lightweight Directory Access Protocol is not supported. Leels of security There are three possible leels of security used for communication between the serer and agents. You need to select one of them depending on the security regulations in your organization. Minimum The agent communicates with the serer computer on the unsecure port and no check of the client or serer identity is made. Medium The agent communicates on the secure port and an SSL certificate is used to authenticate the identity of the serer. Maximum The serer must authenticate all clients that contact it. Therefore, all agents that communicate with the serer must also be configured for maximum security and must hae personal certificates deployed. The serer listens on the secure port and the secure port is configured to require both client and serer authentication. Security-Enhanced Linux Installation considerations Security-Enhanced Linux set to enforcing mode can cause problems with the installation and use of Tioli Asset Discoery for Distributed serer and agents. If your operating system enables SELinux, you will need to either set it to permissie, or disable it completely. There are different installation types of the Tioli Asset Discoery for Distributed that you might choose from, depending on your business needs. You can choose one of the three scenarios for Tioli Asset Discoery for Distributed installation: 48 Installation Guide

55 Proof-of-concept installation This type of installation allows you to check if the elements of the infrastructure can communicate with one another efficiently. The database parameters are scaled down to allow fast communication between product components and quick testing. After performing proof of concept installation, you can run the production installation of Tioli Asset Discoery for Distributed. Installing the serer and database on one computer This is the recommended installation type but it should only be used if the computer on which you are installing the product meets the CPU and memory requirements for the serer and database on page 5. Installing the serer and database on different computers In this scenario, the serer and database components are installed on two different computers. You can decide to use it if the computer on which you want to install does not meet the hardware requirements, or if you hae an existing instance of DB2 installed. In the first case, you will need to run the installation program twice: once to install the database on the machine where the DB2 should run, and the second time to install the administration serer on the computer designated for it. If you hae DB2 already installed on a different computer than the one where you want to install the serer, you will need to locate the existing instance of the database during the serer installation. The installation will create the Tioli Asset Discoery for Distributed database in the existing DB2 and populate it with data, such as the pre-defined software catalog and the PVU table. It will also create the tlmsr database user used to connect to the database, in case it does not already exist. Proof-of-concept installation You can perform a proof-of-concept installation of the serer before the actual production installation. Proof-of-concept installation allows you to quickly set up an enironment, check if it is working and if it satisfies your business needs. Proof-of-concept installation has all the functions of the production ersion, but the database parameters are scaled down and the communication times between product components are reduced. If you use this mode of installation, you cannot install the Administration serer and Administration serer database on separate computers. You can launch proof-of-concept installation by selecting Test Enironment at the start of the serer installation. Note: Proof-of-concept installation can be performed only on the embedded ersion of WebSphere Application Serer. After you finish testing, you can uninstall the administration serer leaing the TLMA database untouched, and then install the serer in production mode either with the embedded or on the base ersion of WebSphere Application Serer. Below you will find a comparison of parameter alues between test (Proof of Concept) and production enironment installations. Table 25. Proof Of Concept and production installations System.properties Test enironment Production enironment Chapter 1. Planning the installation 49

56 Table 25. Proof Of Concept and production installations (continued) Serer productinentorybuilderperiod (minutes) maxaggregateusageage (days) 1 2 inentoryscangraceperiod (hours) 1 10 Agent maxagentinactiity (minutes) maxagentinactiitytodelete (minutes) Db configuration Serer BUFFERPOOL testenironmentenabled true false Agent down_parms_period (minutes) upload_usage_period (minutes) ping_period (minutes) Installation Guide

57 Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed Tioli Asset Discoery for Distributed is a separately installable component of Tioli Asset Management for IT. This component generates reports about installed licenses, which software asset managers use for monitoring compliance. After you hae planned your Tioli Asset Discoery for Distributed infrastructure, you are ready to start installing the product. An oeriew of the installation process Before Tioli Asset Discoery for Distributed is ready for use, you need to install and configure the serer and its database, then deploy the agents. Before you begin Plan your installation. Ensure that your serer and agent machines fulfill all hardware and software prerequisites. Plan the topology. Consider whether you want to use secure communications for the serer and agents. The following diagram presents a high leel oeriew of the installation process and all its stages. Copyright IBM Corp. 2002,

58 Ensure that your machines fulfill all prerequisites Install the Tioli Asset Discoery for Distributed serer Configure the serer Optional: Install security certificates Create Web user interface accounts Create agent scan groups Deploy the agents To do this: Procedure 1. Install the serer and database. You might also need to install the prerequisites. 2. Configure the serer. This includes both required and optional tasks, as follows: Required Import the IBM catalog to populate the database with information about products that can be monitored. Optional Import the processor alue unit table to hae up-to-date information about your processor alue unit capacity. Configure proxy serers for communications between the serer and agents. See the "Configuring" section of the information center for more details. Configure the serer to send notifications about significant licensing and system management eents. For more information see the "Configuring" section of the information center. Add users. See the "Administering" section of the information center for more information. 52 Installation Guide

59 Installing the serer Configure the process of discoering nodes where agents hae to be installed. For detailed instructions see the "Administering" section of the information center. 3. If you hae decided to use secure communications: a. Install certificates for the serer and prepare certificates for the agents. Refer to the "Security" section of the information center for more information. b. Create accounts for the users who will work on the Web user interface. For more information, see the topic "Controlling access" in the "Security" section of the information center. 4. Install agents on the systems that you want to monitor. Start the Tioli Asset Discoery for Distributed installation by installing the serer and database. Before you begin Ensure that the machine where you are installing the serer fulfills all hardware and software requirements. If you hae downloaded the installation image from Passport Adantage, ensure that you hae prepared the files for installation. Note: Install DB2 before you install the serer to be able to customize DB2 and troubleshoot problems that might occur during its installation. To do this: Procedure 1. If you want to install the database on a separate machine, ensure that the clocks of serer and database computers are synchronized. 2. UNIX Linux Install and actiate the Korn shell. 3. Red Hat Set SELinux to permissie or disabled. 4. Install the application serer and database. Depending on the size of your working enironment, you can choose one of the following options: Install together with the ersion of WebSphere Application Serer that is embedded with the product. This method is recommended for small to medium enironments (up to 5000 agents). Install on a full, base ersion of WebSphere Application Serer. This method is recommended for large enironments (up to agents). This alternatie is highly configurable and requires adanced administratie skills. You can install the base edition of WebSphere Application Serer that is bundled with Tioli Asset Discoery for Distributed or you can use a working installation of the application serer. In both cases it is recommended to create a dedicated profile on the application serer to effectiely separate Tioli Asset Discoery for Distributed from other applications running on it. 5. Reboot the system and start the Web user interface to erify the serer installation. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 53

60 Preparing files for installation If you downloaded the installation image from Passport Adantage, unpack the files before installing the product. Preparing serer files Procedure 1. Copy one of the following files to a directory on the serer computer: for AIX, TAD4D-serer-7.2.1_aix-ppc64.zip for HP-UX, TAD4D-serer-7.2.1_hpux_parisc.zip for Linux on Power Systems TAD4D-serer-7.2.1_linux-ppc64.zip for Linux on System z TAD4D-serer-7.2.1_linux-s390_64.zip for Linux x86, TAD4D-serer-7.2.1_linux-x86_32.zip for Linux x86 64-bit, TAD4D-serer-7.2.1_linux-x86_64.zip for Solaris, TAD4D-serer-7.2.1_solaris-sparc64.zip for Windows 32-bit, TAD4D-serer-7.2.1_windows-x86_32.zip for Windows 64-bit, TAD4D-serer-7.2.1_windows-x86_64.zip 2. Unpack your platform-specific installer file. Preparing DB2 files Procedure 1. Unpack the DB2_ESE_Restricted_Actiation_V91.zip file. 2. Depending on your operating system, copy the releant file into the disk1 directory that has been created in the preious step: for AIX, DB2_Enterprise_Sr_Ed_AIX_5L.tar for HP-UX, DB2_Enterprise_Sr_Ed_HP-UX_RISC.tar for Linux x86, DB2_ESE_V913_LNXX86.tar for Linux x86 64-bit, DB2_ESE_V913_LNXX86_64.tar for Linux on Power Systems, DB2_ESE_V913_LNXPPC.tar for Linux on System z, DB2_ESE_V913_LNXS390X.tar for Solaris, DB2_Enterprise_Sr_Ed_Solaris_SPARC.tar for Windows 32-bit, C13KRML.exe for Windows 64-bit, DB2_ESE_V913_WINX Unpack the file. 4. Specify the disk1 directory as the IBM DB2 setup location. Software packages for installing Tioli Asset Discoery for Distributed To perform the installation, you need seeral packages that you can download from the Passport Adantage or Software Support web site (fix pack) or copy from the product DVD. Some of the images may differ depending on whether you install on the embedded or base WebSphere Application Serer. You will also need fix pack files which are required for bringing WebSphere Application Serer to a required software leel. 54 Installation Guide

61 Table 26. Installation packages for installing on the embedded and base WebSphere Application Serer No Type of image If you install on embedded WebSphere Application Serer 1. Serer images Tioli Asset Discoery for Distributed platform specific serer installation package. It contains the following packages: The embedded WebSphere Application Serer V6.1 Integrated Solutions Console ersion for Embedded Websphere Application Serer If you install on the base WebSphere Application Serer Tioli Asset Discoery for Distributed Serer Installation Package Platform Specific You require the interactie installer because you need to start it to extract the files for manual installation. 2. Agent images Tioli Asset Discoery for Distributed Agent Installation Package (natie installer) 3. WebSphere Application Serer images Agent Installation Package, collection of Software Package Blocks only for Tioli Configuration Manager-based installation Common Inentory Technology Enabler IBM Update Installer V for WebSphere Software is aailable on the following download page or on the product DVD, in the directory serer/fixpacks. If you are installing on the embedded WebSphere Application Serer, you do not need to install the fix packs - they are installed together with the application serer (Fix packs for embedded WebSphere Application Serer are shipped within the Serer Installation Package.). WebSphere Application Serer V6.1 (32 or 64-bit) WebSphere Application Serer V6.1 Supplements, which contain: IBM HTTP Serer Web Serer Plug-ins Migration Tool IBM Support Assistant Update Installer Integrated Solutions Console ersion Package for Websphere Application Serer 4. DB2 images DB2 Enterprise Serer Edition V9.1 (32 or 64-bit) IBM Update Installer V for WebSphere Software is aailable on the following download page or on the product DVD, in the directory serer/fixpacks. WebSphere Application Serer V6.1.0 fix pack 23 is aailable on the following download page. Integrated Solutions Console V7.1.0, fix pack 7 is aailable on the product DVD in the directory serer/fixpacks. DB2 Enterprise Serer Edition V9.1 Restricted Use Actiation Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 55

62 Table 26. Installation packages for installing on the embedded and base WebSphere Application Serer (continued) No Type of image If you install on embedded WebSphere Application Serer If you install on the base WebSphere Application Serer 5. Documentation images 6. Additional images for Tioli Asset Discoery for Distributed Quick Start Guide V7.2.1 Quick Start (this image contains complete infocenter) WebSphere Application Serer V6.1 Quick Start CD Guide DB2 Information Center V9.1 for 32-bit and 64-bit DB2 Information Center V9.1 Updates for Windows and Linux PDF Documentation CD DB2 V9.1 English, Brazilian Portuguese, French, German, Italian, and Spanish PDF Documentation CD DB2 V9.1 English, Bulgarian, Croatian, Czech, Dutch, Hungarian, Portuguese, Romanian, Sloakian, Sloenian PDF Documentation CD DB2 V9.1 English, Danish, Finnish, Norwegian, Polish, Russian, Swedish PDF Documentation CD DB2 V9.1 English, Japanese, and Korean PDF Documentation CD DB2 V9.1 English, Simplified Chinese, and Traditional Chinese IBM Tioli Common Reporting V Tioli Asset Discoery for Distributed reports package for Tioli Common Reporting Synchronizing the clocks of serer and database computers If you hae decided to install the serer and the database on separate computers, the time difference between the two computers should not be grater than 300 seconds. A greater time difference might result in data loss or corruption in the serer database. If the clocks are not synchronized, the serer will start in problem determination mode, and some features will not be accessible. Use a non-manual method of clock synchronization, for example Network Time Protocol. All recent UNIX and Windows systems hae the ability to synchronize with Network Time Protocol serers. For other operating systems, refer to user documentation for information how to configure time synchronization. The following example shows how you can ensure that the clocks are synchronized the Windows XP operating system. The method shown here requires that both computers are connected to the Internet. Procedure 1. On the application serer, open the Windows Control Panel and select Date and Time. 2. On the Internet Time tab, select the time of the serer that you want to synchronize with. 3. Repeat this operation on the computer where you will install the database. 56 Installation Guide

63 Changing SELinux settings before installing Tioli Asset Discoery for Distributed on Red Hat Linux Red Hat enterprise Linux enables SELinux by default, which is incompatible with Tioli Asset Discoery for Distributed. To ensure proper serer installation, you need to change the SELinux setting from enforcing mode to either permissie or disabled. This change must be permanent because turning enforcing mode back on preents the serer from working. Beware of inadertently presering enforcing mode by changing the context to textrel_shlib_t for all the libraries used by serer. Procedure 1. Open the /etc/selinux/config file. 2. Change the SELINUX parameter to permissie or disabled. 3. Restart the computer. Installing Tioli Asset Discoery for Distributed with the embedded ersion of WebSphere Application Serer For small to medium-sized enironments (up to 5000 agents), you can select to automatically install the ersion of IBM WebSphere Application Serer that is embedded in the Tioli Asset Discoery for Distributed installation images. Both products are installed into the same target directory. Installing the serer in interactie mode Use the installation wizard to specify all parameters as the installation proceeds. Before you begin You must hae the following operating system priileges: UNIX Linux root Windows Administrator On UNIX and Linux machines, there must be graphical interface aailable. Otherwise, you must use silent mode. If you hae downloaded the installation image from Passport Adantage, ensure that you hae prepared your files for installation. If you plan to install the bundled ersion of DB2 using the Tioli Asset Discoery for Distributed installation wizard, ensure that all the requirements are met. To check the up-to-date system requirements for IBM DB2 9.5, go to Before you start the installation of the serer you need to apply the DB2 license entitlement certificate. For information on how to do that refer to the topic Registering a DB2 product or feature license key using the db2licm command (DB2 9.1). To get the db2ese_o.lic license file uncompress the DB2 Enterprise Serer Edition V9.1 Restricted Use Actiation package (part number C150QML, file name DB2_ESE_Restricted_Actiation_V91.zip) downloaded from Passport Adantage. Procedure 1. In the directory where you unpacked the installation files, run launchpad.exe (Windows) or launchpad.sh (other platforms). The Welcome page opens. You Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 57

64 can also launch the installation file TAD4D-serer your_platform.bat (Windows) or TAD4D-serer your_platform.sh (other platforms) directly from the DIRECTORY_WITH_INSTALLATION_FILES\serer. You do not need the Web browser for this method. You are directed straight to the language selection window. 2. In the left-hand naigation bar, click Install or upgrade to Tioli Asset Discoery for Distributed. 3. Click Launch the serer installation wizard. 4. Select the language of the installation and click OK. The installation wizard starts and the Welcome panel displays. 5. Click Next The License Acceptance panel opens. 6. After accepting the terms of the license agreement, specify the type of installation that you want: For a typical installation, select Production Enironment. For a proof of concept, select Test Enironment. 7. Specify the installation location. Note: If you are installing on Solaris, do not select a location in the tmpfs file system. A known problem preents the calculation of aailable space in this file system. 8. Select the components that you want to install. You can install the serer and database on the same computer or on different computers. If you hae already installed a component on this computer, or you are running the proof-of-concept installation, that selection is unaailable. If you hae decided to install the database on a different computer than the serer, you need to run the installer twice on each of the computers. It is recommended to start with the database installation. This way you will be able to test the connection between the serer and the database and after completing the installation on both computers, the serer will not need to be restarted to work. 9. Click Next. On the new panel select the option to install the serer on the embedded ersion of WebSphere Application Serer. 10. Click Next. If you are installing the database on this computer, specify whether to install the IBM DB2 software that is bundled with this program, or whether to use an existing instance of DB2 on this computer. Click Next. 58 Installation Guide

65 Note: UNIX A known problem causes the installation wizard to consider the last element on the DB2 instance owner file path (with home directory in it) the DB2 instance owner name, thus if your DB2 instance owner home directory does not follow the pattern <unix_home_dir>/ <db2_instance_owner_name>, create a symbolic link that will point to the DB2 instance owner home directory and select this symbolic link as an instance owner name during the installation of database component. 11. If you are installing the bundled ersion of DB2 on this computer, specify the following configuration settings: IBM DB2 setup location. You can leae this field empty and specify it later. IBM DB2 destination path - the directory where you want to install the DB2 software. Port number - the number of port to use when communicating with the administration serer. User ID and password. DB2 user group Note: Do not install DB2 using the Tioli Asset Discoery for Distributed installer if DB2 is already installed on the target serer. 12. Click Next. Accept or change the ports for communication with the serer console and agents. The installer checks if the ports you selected are already in use, and lets you know if there are any conflicts. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 59

66 13. Specify the password for the tlmsr user ID, which is responsible for authorized DB connection and is used by serer processes to access the database. The password must adhere to the security requirements of the serer. Depending on your operating system, there might be different rules, such as minimum length. The tlmsr is stored in encrypted form in the application serer configuration files. 14. If you chose to install the database on this computer, define the security settings: Use FIPS cryptography This option is aailable only when you are installing the serer. Select it to enable the encryption of data using approed algorithms from the Federal Information Processing Standard This setting applies to the serer that communicates with the agents. IBM i FIPS cannot be used on IBM i platforms. If your enironment includes een one agent running on IBM i, FIPS cannot be turned on. Security Leel This option is only aailable only when you are installing the database. If you set the minimum or medium security leel, agents can communicate with the serer by either the secure or the unsecure port, depending on the security leel that you defined when you deploy the agent. If you set the maximum security leel, you must set the same leel of security for all agents when you deploy them. 60 Installation Guide

67 15. Click Next and reiew the installation information. Important: The installation program creates some temporary files, so at times more disk space is required than the total size shown on this page. Consider this extra requirement before proceeding with the installation; if necessary, clear additional space. 16. Click Next. The first stage of the installation commences. Do not interrupt this stage. If it fails for any reason, you might need to clean up files manually. 17. If you selected to install DB2 ersion 9.1, the Locate the Installation Image panel opens. Naigate to the DB2 installation image deliered with Tioli Asset Discoery for Distributed, select the appropriate setup file for your platform and click Open. This panel does not appear if you hae already proided the path to the installation image in step 10. The installation of DB2 starts. 18. If you want to stop the installation at the end of the current task, click Stop. You can resume it later at the same point. 19. When the installation completes, click Finish to exit the wizard. If you are installing the serer and database on separate computers, log on to the other computer and run the installer again. After both the serer and database are installed, configure the serer security, add users in the Web interface, and install the agents. Installing the Tioli Asset Discoery for Distributed serer in silent mode As an alternatie to using the installation wizard, you can specify parameters in a response file and start the installation from a command line. Use this approach for unattended installation. Before you begin You must hae the following operating system priileges: UNIX Linux root Windows Administrator Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 61

68 Linux UNIX Ensure that the setupserers.bin and TAD4D-serer your_platform.sh files hae execution rights. If you hae downloaded the installation image from Passport Adantage, ensure that you hae prepared the files for installation. Before you start the installation of the serer you need to apply the DB2 license entitlement certificate. For information on how to do that refer to the topic Registering a DB2 product or feature license key using the db2licm command (DB2 9.1). To get the db2ese_o.lic license file uncompress the DB2 Enterprise Serer Edition V9.1 Restricted Use Actiation package (part number C150QML, file name DB2_ESE_Restricted_Actiation_V91.zip) downloaded from Passport Adantage. To do this: Procedure 1. Read the license agreement in the license.txt file. The file is located in the directory <DIRECTORY_WITH_INSTALLATION_FILES>/license/your_language. 2. In the <DIRECTORY_WITH_INSTALLATION_FILES>/serer directory, edit the response file that fits your scenario: For production installations, edit installresponseproduction.txt For test installations, edit installresponsepoc.txt Important: a. Ensure that the licenseaccepted parameter is set to true. If you do not accept the license, the installation will fail. b. Do not install DB2 using the Tioli Asset Discoery for Distributed installer if DB2 is already installed on the target serer. 3. To start the installation, run the following command: Linux UNIX TAD4D-serer your_platform.sh options response_file_path silent Windows TAD4D-serer your_platform.bat options response_file_path silent Where response_file_path is either the full or relatie path to the response file you are using. If you are installing the serer and database on separate computers, log on to the other computer and run the installer again. When both the serer and database are installed, configure the serer security and add users in the Web interface, then install the agents. For more information, refer to the "Security" section of the Information Center". Resuming a failed Tioli Asset Discoery for Distributed serer installation If the installation fails or if you stop it after the initial copying files to the target directory, you can resume installation after resoling the problem. Howeer, if the installation fails during the initial copy stage, you cannot resume and you might need to do manual cleanup. 62 Installation Guide

69 This task assumes you are installing from the wizard. If you are installing from a response file, and the installation failed, resole the problem (see the "Troubleshooting" section of this guide), uninstall the serer and install it again. Installation can be resumed by running the installation script with -resume switch: Windows TAD4D-serer your_platform.bat -resume UNIX TAD4D-serer your_platform.sh -resume Procedure 1. If you hae not yet exited the wizard, click Diagnose failure. A panel opens showing the status of installation tasks. 2. To identify why the installation failed, click the task with the status Error. Refer to the Troubleshooting and support section of this guide for possible solutions. 3. If you hae already exited the wizard, check the log files for information about why the installation failed. If the information in log files is not sufficient, uninstall the serer and install it again. 4. When you hae soled the problem, change the task status to Ready. 5. Click Run All. Serer installation response files Response files proide input parameters that are used when you install from a command prompt or in silent mode. There are two response files. Both are located in the directory TAD4D-serer base/serer/. Some parameters hae default alues that you can accept or change. Others hae no default, so you must proide a alue. Note: Some parameters are passwords and are stored in the options file in unencrypted form. Ensure that this is not against the security policy of your organization before using this installation method. Common parameters The following parameters are required for all installations of Tioli Asset Discoery for Distributed, regardless of whether you are installing the serer, the database or both. Table 27. Response file parameters for all installations Parameter Parameter key name Default License agreement acceptance Installation location -G licenseaccepted true Delete the hash that flags this statement as a comment. The installation will fail if you do not explicitly agree with the license agreement by changing this statement from comment status. -P installlocation Specify an empty directory where the selected elements will be installed. If the directory does not exist, it will be created. If the directory path contains spaces, enclose it in double-quotation marks. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 63

70 Table 27. Response file parameters for all installations (continued) Parameter Parameter key name Default Installation type -W setuptype.selectedsetuptypeid Specify the type of installation to be performed. Possible alues are: Setup: administration serer component selection Setup: administration database component selection Base configuration: tlmsr user password Test Admin Unpack Installs the selected components in test (proof-of-concept) mode. Use this type of installation to quickly check if Tioli Asset Discoery for Distributed is working and if it satisfies your business needs. Installs the selected components in production mode. Unpacks the installation files needed to install the serer on the base ersion of WebSphere Application Serer. Specifying this alue means that the serer components will not be installed by the installation wizard. The files are unpacked into the directory specified by the -P installlocation parameter and you can proceed with the installation on the base WebSphere Application Serer. -P admin.actie true Specify whether or not the Tioli Asset Discoery for Distributed serer element should be installed. Possible alues are: true false The serer will be installed on this computer. The serer will not be installed on this computer. -P admindb.actie true Specify whether or not the database element should be installed. Possible alues are: true false The database will be installed on this computer. The database will not be installed on this computer. -W dbinstalladmin.tlmsrpwd Specify the password to be used to authenticate access to a database by serer processes. This password is assigned to a user with ID tlmsr that is created on the target computer when a database element is installed for the first time. The password is also stored in an encrypted form in a properties file on the serer computer. Base configuration: ports used by administration serer The maximum length is 20 characters and the characters allowed are: A-Z, a-z, 0-9, +, -, *,, =. The password must follow the security policy of the operating system of the computer on which it will be created. Note: Passwords entered in this file are not encrypted. This may be a security iolation in your organization. -W baseconfig.adminport 8899 The port used by the administration serer console. -W baseconfig.adminsslport 8888 The port used by the administration serer console in secure mode. -W baseconfig.minsecport 9988 The port used for minimum security leel communications. -W baseconfig.medsecport 9999 The port used for medium security leel communications (HTTPS serer authentication). -W baseconfig.maxsecport 9977 The port used for maximum security leel communications (HTTPS serer and agent authentication). 64 Installation Guide

71 Table 27. Response file parameters for all installations (continued) Parameter Parameter key name Default Setup: Specify security parameters Administration database port number -W setsecurity.specifysecuritysettings false Specify whether or not the security parameters specified in this response file are to be used instead of default alues. Possible alues are: true false Custom security parameters will be used. Default security parameters will be used. -W dbinstalladmin.portnumber If you are installing only the serer on this machine, specify the port number to connect to the database. If you are also installing the database and the DB2 prerequisite, you can leae this field blank. The database port number is then set to the alue specified for the DB2 installation in the -W db2inputpanel.db2_port parameter. Serer parameters The following parameters are only needed if you are installing the serer on this computer. Table 28. Parameters for silent installation of the Tioli Asset Discoery for Distributed serer Parameter Parameter key name Default Description Administration serer: remote administration database: address Setup: Use FIPS cryptography -W dbinstalladmin.hostname localhost Supply the host name or the IP address where the administration serer database will be installed. If you want to the database to be installed on the same machine as the serer, set this parameter to localhost. -W setsecurity.enablefips false Specify whether FIPS-approed encryption algorithms are to be used. Possible alues are: true false FIPS approed cryptographic algorithms are used. Default algorithms are used. Database parameters The following parameters are only needed if you are installing the serer on this computer. Some of them may not be required, depending on whether you are also installing the DB2 prerequisite, or whether it is already installed on your system. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 65

72 Table 29. Database parameters for silent installation Parameter Parameter key name Default Description Prerequisite search: IBM DB2 database serer Administration database: local instance owner (UNIX only) DB2 prerequisite: prerequisite image location DB2 prerequisite: install location -W databasesererpathpanel.prerequisiteinstalled false Specify whether a supported ersion of DB2 is already installed on the computer. Possible alues are: true Indicates that the prerequisite is installed in the location specified in the databasesererpathpanel.locationpath parameter key. The wizard checks that a supported ersion is in the specified location. If this alue is selected and no ersion of DB2 can be found, the installation will fail. false Indicates that no supported ersion is installed. The wizard installs the bundled DB2 database serer prerequisite. If any ersion of DB2 is already installed on the computer, the prerequisite installation will fail. -W databasesererpathpanel.locationpath If a supported ersion of DB2 is installed (-W databasesererpathpanel.prerequisiteinstalled=true), specify the location in which it is installed. It must be proided as a full pathname. If the pathname includes directories with spaces in their names, it must be enclosed in double quotes. For UNIX, supply the path of the home directory of the DB2 instance owner. -W dbinstalladmin.dbadminuser db2inst1 On UNIX platforms, specify the instance owner of the DB2 administration serer database. If DB2 is being installed as together with the database, the instance owner is set to the alue specified in -W db2inputpanel.db2_username and this parameter is not used. -W db2inputpanel.db2_setuploc If the wizard is to install the DB2 prerequisite on a Windows serer, specify the location of the setup file. It must be proided as a full pathname, and if the pathname includes directories with spaces in their names, it must be enclosed in double quotes. -W db2inputpanel.db2_instloc If the wizard is to install the DB2 prerequisite, specify the directory in which to install it. It must be proided as a full pathname, and if the pathname includes directories with spaces in their names, it must be enclosed in double quotes. DB2 prerequisite: DB2 port number DB2 prerequisite: DB2 administrator ID DB2 prerequisite: DB2 administrator group For UNIX, supply the home directory of the DB2 instance owner, that, when concatenated with the DB2 instance owner ID, gies the path to the install location of DB2. For example, if the location is /home/db2inst1, where db2inst1 is the instance owner's id, enter just /home. -W db2inputpanel.db2_port If the wizard is to install the DB2 prerequisite, specify the port on which DB2 will listen. -W db2inputpanel.db2_username db2admin If the wizard is to install the DB2 prerequisite, specify the DB2 administrator user ID that the wizard will create on the computer. The ID must not exist on the computer where it is to be created, and must respect the user id rules of that computer. -W db2inputpanel.db2_usergroup Optional parameter. You can specify the administrator group to which the administrator ID will belong. 66 Installation Guide

73 Table 29. Database parameters for silent installation (continued) Parameter Parameter key name Default Description DB2 prerequisite: DB2 administrator password Agent to serer security leel -W db2inputpanel.db2_password If the wizard is to install the IBM DB2 prerequisite, specifies the DB2 administrator password that will be used when the DB2 Administrator ID is created. The maximum length is 20 characters and the characters allowed are: A-Z a-z =. Thepassword must follow the security policy of the operating system of the computer on which it will be created. Note: Passwords entered in this file are not encrypted. This may be a security iolation in your organization. -W setsecurity.agenttoserersecurityleel 0 Determines the leel of security to be used for communication between the agent and the serer. This option is used only when installing the administration serer database component. Possible alues are: 0 To use unsecure communication. 1 To use secure communications with serer authentication. 2 To use secure communications with client and serer authentication. Note: 1. Agents with minimum (0) and medium (1) security leels can communicate with serers that hae security leels of minimum or medium, proided that both the secure and unsecure ports are configured. If the maximum security leel is used, both the agent and the serer must be aligned with the security leel set to maximum. 2. If you select medium (1) or maximum (2) security, you must perform a series of tasks to set up and install certificates. For full information about enabling security, see the "Security" section of the Tioli Asset Discoery for Distributed infocenter. Installing the Tioli Asset Discoery for Distributed on WebSphere Application Serer As an alternatie to installing the serer on the embedded ersion of WebSphere Application Serer, you can install on a full, base ersion of WebSphere Application Serer. This method allows you to deploy a greater number of agents in your infrastructure (up to 45000) and is suitable for larger enironments. If you are installing on the Base ersion of WebSphere Application Serer, with enabled secure agent-serer communication, you must apply a Jaa update on WebSphere Application Serer. You can download the update from the following page: If you do not apply the Jaa update, the secure communication will not work properly. Depending on the security leel, the agent will be able to connect to the serer but other operations such as catalog download or the import of a priate certificate when configuring agents will cause GSKit exceptions. Installing WebSphere Application Serer Before you begin to install Tioli Asset Discoery for Distributed serer and database, WebSphere Application Serer must already be installed. If you do not already hae an installed application serer, you can use the installation media for the base edition of WebSphere Application Serer that is bundled with Tioli Asset Discoery for Distributed. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 67

74 Procedure Locate the installation media or images for WebSphere Application Serer and start the setup program. For more information, consult the WebSphere documentation aailable in the WebSphere information center. Configuring WebSphere Application Serer Before you begin to install Tioli Asset Discoery for Distributed serer and database, WebSphere Application Serer must already be present in your infrastructure. You can use a freshly-installed or working installation of WebSphere Application Serer, howeer, it is recommended to create a dedicated profile on it to effectiely separate Tioli Asset Discoery for Distributed from other applications. For WebSphere Application Serer Network Deployment, only the default (standard or base) profile is supported. Procedure 1. Create a new dedicated profile for Tioli Asset Discoery for Distributed to ensure that the product is separate from other applications installed on the WebSphere Application Serer, and that it can be configured or uninstalled independently. You can use an existing profile if no other application than Tioli Asset Discoery for Distributed uses it. To create a new profile, issue the following command: manageprofiles.bat -templatepath -profilename -profilepath -cellname -nodename -serername -create template_path profile_name profile_path cell_name node_name serer_name A message confirms that the profile was successfully created. 2. (Recommended) Back up your profile after performing any of the tasks described in this section. This will enable you to return to the configuration from before performing the task. Issue the following command: manageprofiles.bat -profilename -backupfile -backupprofile profile_name backup_file_path If you performed a backup of your profile, you can restore it by issuing the following command: manageprofiles.bat -backupfile -restoreprofile backup_file_path manageprofiles.bat -restoreprofile - backupfile backup_file_path 68 Installation Guide

75 Remember: Before you restore your profile, you need to delete it from WebSphere Application Serer. You can do it with the manageprofiles.bat -delete -profilename profile_name command. You also need to delete the directory where the profile is located. Updating WebSphere Application Serer and Integrated Solutions Console After installing WebSphere Application Serer and Integrated Solutions Console, you need to update them with the latest fix packs. Procedure 1. Download the Update Installer from the following Web site: If you hae an earlier ersion of Update Installer on your computer, you need to uninstall it before installing this one. 2. Stop WebSphere Application Serer. 3. Download the fix pack 23 for WebSphere Application Serer 6.1 from: 4. Copy the Integrated Solutions Console update file from the DIR_WHERE_THE_DVD_IS_MOUNTED/serer/fixpacks/ISC/ WS- WASFeature-FEISCAE7107.pak to the same folder where you downloaded the fix pack 23 for WebSphere Application Serer. 5. Run the Update Installer installation file. 6. On the Welcome panel, read what products are supported and click Next. 7. Specify the path to the WebSphere installation directory, for example C:\Program Files\IBM\WebSphere\AppSerer on Windows systems (Windows) or /opt/ibm/websphere/appserer (UNIX). 8. Select Install maintenance package. 9. Enter the name of the directory where you had placed the update and fix pack files. 10. On the Aailable Maintenance Package to install page, select the update and fix pack files and click Next. 11. Click Install. 12. On the last page, click Finish. The packages are installed. 13. (optional) Change the serername property in the deployiscaewars.ant file if the serer name is different then default serer1. In the file deployiscaewars.ant located in WAS/profilesTemplates/iscae71/actions directory proide a alid serer name in the following line: property name="serername" alue="serer1". 14. To link the Integrated Solutions Console update with the profile where the Tioli Asset Discoery for Distributed serer will be installed, issue the following command: Linux UNIX manageprofiles.sh augment -profilename profile_name templatepath /opt/ibm/websphere/appserer/ profiletemplates/iscae71/ Windows manageprofiles.bat augment profilename profile_name -templatepath \was_install_dir\ibm\websphere\appserer\ profiletemplates\iscae71\ To erify whether the Integrated Solutions Console is updated and working, confirm that the My Startup Pages item and Settings node are isible in the Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 69

76 left-hand naigation panel of the user interface. The Settings item should also be open in tabs. Additionally, on the naigation bar there should be "one-click expand/roll" button. You can also check the output from: Linux UNIX websphere_application_directory/bin/historyinfo.sh Windows websphere_application_directory/bin/historyinfo.bat to find out whether the feature WS-WASFeature-FEISCAE7107.pak is installed. You are now ready to extract the Tioli Asset Discoery for Distributed installation files. Extracting the installation files from the interactie installer Use the Tioli Asset Discoery for Distributed installation wizard to extract the files needed for installing the serer and command-line interface. Before you begin Ensure that you hae created and augmented the Tioli Asset Discoery for Distributed WebSphere Application Serer profile. To do this task: Procedure 1. Prepare the files for installation. 2. Run launchpad.exe (Windows) or launchpad.sh (other platforms). The Welcome page opens. 3. In the left-hand naigation pane, click Install or upgrade to Tioli Asset Discoery for Distributed. 4. Click Launch the serer installation wizard. 5. Select the language of the installation and click OK. The installation wizard starts. 6. Click Next. After accepting the license agreement, click Next again. 7. Select Production Enironment as the type of installation and proceed to the next page. This page opens only if no preious ersion of the product is discoered in the system. 8. Accept the default installation location or click Browse to select a different location. Click Next. This page appears only if no preious ersion of the application is discoered in the system. Note: If you are installing on Solaris, do not select a location in the tmpfs file system. A known problem preents the calculation of aailable space in this file system. 9. Select Administration serer as the component that you want to install and click Next. 10. On next panel select the Unpack the files needed for manual deployment option and specify the directory where you want to extract the files and click Next. 11. Specify the directory where you want to extract the files and click Next. 12. A progress indicator shows when the extract is complete. Click Finish. 70 Installation Guide

77 The installer extracts the required installation files, including the keystore files key.p12 and trust.jks, needed to enable secure communications between the serer and its agents. The installation package contains the installation files, keystore files, JDBC drier files and the command-line interface. You can delete the.ear and.war installation files after you hae deployed them. Howeer, you must retain keystore files, JDBC drier files and the command-line interface files. It is recommended that you moe them to the Tioli Asset Discoery for Distributed installation directory for easy reference. Installing the database and its prerequisites After extracting the installation files, use the installation wizard to install the DB2 ersion 9.1 that is deliered with Tioli Asset Discoery for Distributed using the installation wizard. Before you begin You must hae the following operating system priileges: UNIX Linux root Windows Administrator The network firewall on the target computer may cause problems in communication between the database and the serer. Make sure a port is aailable to allow for the connection with the database. The default port is 50000; you can oerride that at installation time. Procedure 1. Log on to the computer where you want to install the database, as a user with administratie rights (Administrator on Windows platforms or root on UNIX platforms). 2. Start the installation launchpad. a. When you are ready to install, click Install or upgrade to Tioli Asset Discoery for Distributed and then click Launch the serer installation wizard. b. After selecting your language and accepting the license agreement, click Next. 3. On the next page, select Production Enironment and click Next. 4. Specify the installation location. Note: If you are installing on Solaris, do not select a location in the tmpfs file system. A known problem preents the calculation of aailable space in this file system. 5. Click Next. On the next page, when prompted to select the components that you want to install, select Administration serer database. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 71

78 6. The DB2 prerequisite page is displayed. Select the option to let the wizard install DB2 and click Next. Note: If you installed DB2 separately before, point to the directory where it is located and moe to step On the next page, supply the following information: IBM DB2 setup location (Optional) The directory where DB2 installation files are located. IBM DB2 destination path The directory where DB2 will be installed. Port number The port on which DB2 will listen. DB2 administrator user, DB2 user group and password A user ID and password pair that will be created on this computer for performing DB2 administratie tasks, such as creating and dropping databases. The User ID must not already exist on the computer, and the password must conform to any local rules that are in force. You also need to proide the name of a DB2 user group. 72 Installation Guide

79 Click Next. 8. On the next page, specify and confirm the password to be used by serer processes to access the database. During installation of the database, the user tlmsr is created with a password set to this alue. The password must comply with any local rules that are in force in your enironment and can contain only the following characters: A-Z, a-z, 0-9, +, -, *,, =. Keep a note of this password. You must specify it again when you install the serer. Click Next. 9. On the next page, define the security settings for the database serer. Specify agent to serer security leel This setting has the following alues: Minimum To use unsecure communication. Medium To use secure communications with serer authentication. Maximum To use secure communications with client and serer authentication. If you set the minimum or medium security leel, agents can communicate with the database serer by either the secure or the unsecure port, depending on the security leel defined when the agent is deployed. If you set the maximum security leel, when you deploy agents you must set the same leel of security for all agents that are to contact the serer. Chapter 2. Installing and setting up Tioli Asset Discoery for Distributed 73

80 A summary panel opens, showing the amount of space required for DB2 and the Tioli Asset Discoery for Distributed serer database. 10. On the installation summary page, check the information that is proided and confirm that you hae enough space to complete the installation. The creation of temporary files might require more space, than the total size shown. If the amount of aailable space is close to the total size shown, clear some space before proceeding. 11. Click Next to begin the installation. During the first stage of the installation, files are copied. If this stage fails for any reason, you might need to clean the enironment manually because the uninstaller is not created until the end of the installation process. 12. If you did not specify the location of the installation files earlier, a popup window prompts you to locate the installation image for DB2. Naigate to the installation image and select the appropriate folder in which the setup file is located for the platform where you are installing. Click OK. Note: Skip this step if you hae already specified the location of your DB2 instance in step The installation of the DB2 software starts, followed by set up of the database. Note: If you installed DB2 separately before, limit this step to setting up the database only. Starting with the DB2 installation, the installation process is diided into a series of tasks and can be stopped at the end of a task and resumed later. A Stop button is aailable and you can click it to stop the installation at the end of the task currently being performed. If you stop the wizard, or if the installation fails during any of these tasks, you can resume the installation from that point. 14. When the installation completes successfully, a summary panel opens showing the installation tasks that were completed. Click Finish to exit from the wizard. When this procedure is successfully completed, the following results are achieed: Installation of the DB2 Enterprise Serer Edition serer, ersion 9.1 software that is proided with Tioli Asset Discoery for Distributed. 74 Installation Guide