IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Upgrade from a previous installation > Plan your upgrade

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Required order of upgrade

Upgrade the products that comprise your configuration in the order described in this section.

If multiple components are being installed within a single installation directory, upgrade all components at once rather than running the upgrade multiple times.

  1. Event synchronization component

    If you use event synchronization, upgrade the event synchronization component first. If you are using Netcool/OMNIbus, refer to Set up event forwarding to Netcool/OMNIbus. If you are using Tivoli Enterprise Console, refer to Set up event forwarding to Tivoli Enterprise Console.

  2. Tivoli Data Warehouse

    1. Stop all instances of the Warehouse Proxy Agent and the Summarization and Pruning Agent.

    2. If you are upgrading from V6.1.x and are collecting warehouse data from any of the agents listed in Table 1, you must migrate your warehouse database before you upgrade other components. See Upgrade the warehouse from IBM Tivoli Monitoring V6.1.x levels and the user's guide for each agent for details.


      Agents requiring warehouse database migration

      • Windows OS agent

      • Unix OS agent

      • Monitor for Databases: DB2 Database for Linux, UNIX, and Windows agent

      • Monitor for Databases: Sybase agent

      • Monitor for Databases: mySAP agent

      • Monitor for Databases: Oracle agent

      Install the Tivoli Enterprise Portal Server (step 6) before you upgrade the warehouse components to ensure the SQL scripts needed for the warehouse upgrade are available. Ensure you upgrade all your site's Warehouse Proxy Agents and Summarization and Pruning Agents before performing step 13.

      Running the upgrade scripts a second time may cause loss of warehouse data.

      If you are upgrading from V6.2.x, you do not need to perform these migration steps.

  3. Hub Tivoli Enterprise Monitoring Server

    Upgrade the hub monitoring server is not required, but if the hub is not upgraded, new features of upgraded agents will not be available. If the hub is upgraded, it must be upgraded first. If the Hot Standby feature is used, the primary and secondary hub monitoring servers must be upgraded in that order before the remote monitoring servers are upgraded.

    Installing a back-level OS agent into an existing V6.3 monitoring server environment is not supported. If this is the desired configuration, install the back-level OS agent before upgrading the monitoring server.

  4. Tivoli Enterprise Monitoring Automation Server

  5. Remote monitoring servers (if necessary)

  6. Tivoli Enterprise Portal Server

    Installing a back-level OS agent into an existing V6.3 portal server environment is not supported. If this is the desired configuration, install the back-level OS agent before upgrading the portal server.

  7. Tivoli Enterprise Portal desktop client

    The client and the portal server must be at the same level for the client to connect successfully.

  8. Warehouse Proxy agents and Summarization and Pruning agent

  9. Tivoli Performance Analyzer:

  10. Infrastructure Management Dashboards for Servers

  11. Tivoli Authorization Policy Server

  12. tivcmd CLI for Authorization Policy

  13. Monitor agents

    The appropriate level of the Tivoli Enterprise Management Agent Framework is installed when an agent is installed. Self-describing monitoring agents is a feature that integrates the installation of an agent with the dispersal and installation of associated product support files throughout the IBM Tivoli Monitoring infrastructure. To use the self-describing monitoring function, the Tivoli Enterprise Management Agent Framework must be at version 6.2.3 or later. See Self-describing agent installation.

    If you do not plan to use the self-describing agent function then you should install the application support for latest version of the monitoring agents on the monitoring servers, portal server, and portal desktop client before upgrading the agents.

    To upgrade monitoring agents, you can either use remote deployment or perform local upgrades on systems where the agents are installed. See Deploy monitoring agents across your environment to use remote deployment. See Install monitoring agents to perform a local upgrade.

  14. Monitor agent reports

  1. Agents created with the Agent Builder require that the entire path from the agent, through the remote monitoring server it connects to, to the hub monitoring server, to the portal server, and the data warehouse be upgraded to V6.2 or later.

  2. Install components or agents in an existing CANDLEHOME or installation directory is supported as long as the user ID used to run the installation is always the same. Installing components or agents in an existing CANDLEHOME or installation directory using different user IDs is not supported.


Parent topic:

Plan your upgrade

+

Search Tips   |   Advanced Search