IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Overview of the upgrade process

This section outlines the steps for upgrading from IBM Tivoli Monitoring V6.1 or V6.2 to IBM Tivoli Monitoring V6.3.

Table 1. Upgrading from IBM Tivoli Monitoring V6.1 or V6.2 to IBM Tivoli Monitoring V6.3
Task		Where to find information
Before upgrading your monitoring environment	Review the upgrade planning information to identify what you can and cannot upgrade, as well as the required upgrade order.	Planning your upgrade
	Determine if any prerequisite software must be installed or upgraded.	Hardware and software requirements
	Linux and UNIX sites: If your Tivoli Enterprise Portal Server is running as a non-root process and you plan to upgrade it using a non-root userid, then a special procedure must be performed prior to upgrade.	Linux and UNIX: Upgrading a portal server running as a non-root process
	Stop all components that you are upgrading and change their startup from Automatic to Manual. Stop Manage Tivoli Enterprise Monitoring Services, and do not start any other Tivoli Management Services components while you complete this upgrade.	Starting and stopping components
	Restart the computer on which you are installing IBM Tivoli Monitoring.	Starting and stopping components
Upgrading your monitoring environment	Run the IBM Tivoli Monitoring installation program on all components that you want to upgrade. Use your existing installation directory as your IBM Tivoli Monitoring directory.	Required order of upgrade Installing IBM Tivoli Monitoring
After upgrading your monitoring environment	On platforms other than Windows, you must reconfigure the Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Portal Server.² Note: On Windows platforms, the installer manages the reconfiguration process.	Configuring IBM Tivoli Monitoring components
	On Windows platforms, if you chose upgrade seeding, support for base agents is upgraded automatically, but you must add application support for any other monitoring agents you are upgrading.	Configuring application support for nonbase monitoring agents
	After upgrading your Tivoli Enterprise Monitoring Server, you must add application support to it.² This step updates existing situation definitions and installs new situations provided with Tivoli Monitoring V6.3. Application support is contained in the ms component. You are automatically prompted to add application support to the monitoring server using the kms_upg.sql file. You must initiate upgrade reseeding using the itmcmd support command and specifying the ms component: `./itmcmd support -t tems_name ms` When reseeding completes, recycle your monitoring server: `./itmcmd server stop tems_name ./itmcmd server start tems_name`	Installing and enabling application support
Note: The installation instructions sometimes reference the default path for the installation of IBM Tivoli Monitoring. If you did not install the product in the default path, you must specify the correct path whenever the upgrade procedures require a path specification. After you upgrade a UNIX monitoring server, you must run the itmcmd config -S command to configure the upgraded monitoring server. During this upgrade you are asked if you want to update application support files as well. If a silent upgrade is performed by default, all installed support files are updated. You can use the tacmd updateAgent command to install an agent update on a specified managed system. For reference information about this command and related commands, see the IBM Tivoli Monitoring Command Reference. You must recycle (stop and restart) the portal server to use upgraded workspaces for your monitoring agents.

Feedback