Deployment Guide Series: IBM Tivoli Monitoring V6.2

Chapter 3. Installation and configuration 49

Figure 3-2 Self-monitoring topology expanded

3.1.1 Considerations before installing the product

In this section, we discuss the things that you need to consider before starting

the installation.

򐂰 Installation parameters.

򐂰 Required order of installation component products.

򐂰 Windows installation considerations

򐂰 Linux or UNIX Installation considerations

򐂰 Other considerations

50 Deployment Guide Series: IBM Tivoli Monitoring V6.2

Installation parameters

You will need the following information before starting the installation:

򐂰 Name of the monitoring server that will be installed or to which the agent will

connect

򐂰 Host names of the systems that will be installed

򐂰 Port numbers (unless the default port numbers will be used)

򐂰 Whether the monitoring server being installed or being connected to is

configured as a hub or remote monitoring server

򐂰 Whether you want to configure the hot standby feature or not

Required order of installation component products

If any of the following products will be installed on the same computer as the

monitoring agents, they must be installed before the agent is installed:

򐂰 Hub Tivoli Enterprise Monitoring Server

򐂰 Remote monitoring server (if necessary)

򐂰 Tivoli Enterprise Management Agent Framework (although you can install a

remote monitoring server on a machine which already has an agent)

򐂰 Tivoli Enterprise Portal Server

򐂰 Tivoli Enterprise Portal desktop client

Windows installation considerations

Before installing the IBM Tivoli Monitoring V6.2 components on Windows, you

need to consider the items in the following sections.

User authority

To install IBM Tivoli Monitoring V6.2 on a Windows computer, you must have

Administrator privileges on that computer. You also need to run the IBM Tivoli

Monitoring V6.2 components as a user with Administrator privileges.

Installation using a Citrix client

When using a Citrix client to access the IBM Tivoli Monitoring V6.2 installation

program for Windows through Microsoft Windows Terminal Services, you need to

manually change Terminal Services to install mode before running the

installation. To change the Terminal Services to install mode, run the command

change user /install before starting the installation. After installation, run the

command change user /execute to return Terminal Services to normal mode.

Note: These products must be installed on at least one computer before the

agent can be properly configured.

Chapter 3. Installation and configuration 51

Linux or UNIX Installation considerations

The following sections provide information about issues specific to Linux and

UNIX installations.

Changes in the behavior of the autostart scripts

The behavior of the autostart scripts generated by the installation of fix packs on

UNIX platforms is different depending on the fix pack level:

򐂰 In Fix Pack 003, the installation process produced an autostart script with only

one entry using a generic CandleAgent start all command and users

modified this file as needed.

򐂰 In Fix Pack 004, the installation process generated individual entries for each

application in a particular installation, but the values captured in the file could

not be overridden.

򐂰 In Fix Pack 005, the multiple entries remain and an override capability has

been added.

The autostart script, named ITMAgents<N> or rc.itm<N> depending on the UNIX

platform, generated by an installation or upgrade contains an entry for each

application in a particular installation. The entries look similar to:

su - <USER> -c "ITM_Install_Home/bin/itmcmd agent start <product_code>"

or

su - <USER> -c "ITM_Install_Home/bin/itmcmd agent –o <Instance> start

<product_code>"

Where:

USER: The ID that the application will be started as. By default,

USER is the owner of the bin directory for the application.

For the UNIX Log Alert agent, USER is the owner of the

ITM_Install_Home/PLAT/ul/bin directory.

N: An integer specific to each installation on a system.

ITM_Install_Home: The full path to the IBM Tivoli Monitoring V6.2 installation

directory.

product_code: The two-character code for this application. Refer to IBM

Tivoli Monitoring Version 6.2.0 Installation and Setup

Guide, GC32-9407 for a list of the component codes.

instance: The instance name required to start this application.

PLAT: The platform directory where the application is installed.