There are several installation options for installing IBM Tivoli Monitoring V5.1.1 on an existing Tivoli environment, especially for interfaces with other products and environments. It supports the Tivoli Software Installation Service or the Tivoli Desktop installation method. Rapid deployment is not applicable because this is an existing environment.
You can install the following components individually:
 |
IBM Tivoli Monitoring Version 5.1.1 |
This is the server and gateway code that needs to be installed on the Tivoli Management Region (TMR) server and all gateways.
|
Tivoli Monitoring Tivoli Business Systems Manager (TBSM) Adapter, Version 5.1.1 |
This is the Common listener adapter feed to TBSM. It must be installed on the TMR server and all gateways which connect to the TBSM common listener.
|
Tivoli Monitoring Gathering Historical Data Component, Version 5.1.2 |
This is the interface to the older Tivoli Decision Support's Server Performance Prediction.
|
Tivoli Monitoring Tivoli Enterprise Data Warehouse Support Version 5.1.2 |
This is the interface to Tivoli Data Warehouse. It must be installed on one of the managed nodes to access the database. This feature also allows the collection of monitoring metrics from resource models into a RDBMS interface module (RIM) database.
To begin the installation, from the Tivoli Desktop, complete these tasks:
| 1. |  |
|
Select Desktop ÆInstall Æ Install Product. |
| 2. | |
|
Select the component that you want to install. |
| 3. | |
|
Install the IBM Tivoli Monitoring V5.1.1 component first and then install individually other components. |
To perform a command line installation, type:
winstall -c cdrom_dir -i ind_file
Installation using Tivoli Software Installation Service goes through the steps of importing the software media to the Tivoli Software Installation Service (SIS) depot. Then you can select the software to be installed to the target machines.
To install the IBM Tivoli Monitoring V5.1.1.1 product using Tivoli Desktop, follow these steps:
| 1. | Back up the object database and the Tivoli file system using either of the following options: |
  From
the Tivoli desktop, select Desktop ÆBackup.
|
|
Enter
the
wbkupdb command.
|
We recommend that you back up the entire Tivoli file system of the node on which the product will be installed.
| 2. | Install the IBM Tivoli Monitoring V5.1.1 product on the TMR server and gateways. |
|
Tip: If any problems occur during the installation process, they are registered in the /tmp/tivoli.cinstall (UNIX) or %DBDIR%/tmp/tivoli.cinstall (Windows) file. |
In our ITSO environment, we installed the product using the following steps:
| 1. | From the Tivoli desktop, select Desktop ÆInstall ÆInstall Product. |
| 2. | The Install Product window (Figure 4-1) shows three products that are available to install. |
| a.
Select IBM Tivoli
Monitoring V5.1.1. |
| b.
Select your TMR server and the
gateways on which you want to install IBM Tivoli Monitoring
V5.1.1. |
| c.
Click Install.
|
| 3. | Follow the standard installation windows. |
Figure 4-1 Products to install
|
Tip: If you are installing or upgrading IBM Tivoli Monitoring V5.1.1 on a Windows TMR server environment, you must perform the following the procedures to create the IBM Tivoli Monitoring V5.1.1 Task Libraries. |
In the Windows-based TMR box, set the Tivoli environment variables and enter in bash mode. Run the after_install_win.sh script. Example 4-1 shows the script contents.
Example 4-1 Contents of the after_install_win.sh script
IRO=`wlookup InterRegion`
IROname=`idlattr -t -g $IRO name string`
IROname=`eval echo $IROname`
DefaultMw2kRegionName="TivoliDefaultMw2kRegion-$IROname"
wtll -r -p $DefaultMw2kRegionName -P $BINDIR/tools/cat $BINDIR/TME/Tmw2k/tmnt.tll
wtll -r -p $DefaultMw2kRegionName -P $BINDIR/tools/cat $BINDIR/TME/Tmw2k/tmnt_util.tll
This completes the installation of the base IBM Tivoli Monitoring V5.1.1 code.
During the installation, policy region TivoliDefaultMw2kRegion-regionname is created. To access this policy region, select Desktop ÆTMR Connections ÆTop Level Policy Region. This policy region contains a profile manager and two task libraries, as shown in Figure 4-2.
Figure 4-2 Profile manager and task library