IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Maintaining monitoring agents > Agent tasks in the Tivoli Enterprise Portal
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Update an agent through the Tivoli Enterprise Portal
When a new version of a distributed monitoring agent is released, you can apply the new version locally or remotely to one managed system at a time, or to many simultaneously. Use the Configure Managed System window in the Tivoli Enterprise Portal client to apply the update.
This capability does not apply to the OS monitoring agents, z/OS-based agents, or any products that do not support the remote agent deployment feature. The agents to be updated must also have been originally installed using remote agent deployment. The types of managed systems that you can add to a computer depend on what agent bundles are in the agent depot on the monitoring server to which the OS agent is connected. See the "Deploying monitoring agents across your environment" topics in the IBM Tivoli Monitoring Installation and Setup Guide for more information.
Before starting the update, install application support on the Tivoli Enterprise Portal Server for any agent that you are going to deploy with the procedure that follows.
Agent application support updates are automatic and this procedure is not necessary if your monitoring agent is running on an IBM Tivoli Monitoring Version 6.2.3 or later infrastructure, unless the self-describing capability is disabled.
Complete these steps to apply a patch for a monitoring agent through the portal client:
Procedure
- Right-click the Navigator item for the agent that you want to upgrade.
- Click Configure to open the Configure Managed System window.
- Click the Agent tab.
- Compare the installed version of the monitoring agent with any available product updates, then highlight the row of the agent to update and click Install Updates.
Results
Installation of the updates begins and might take several minutes to complete. The list that displays reflects the contents of the deployment depot. If Install Updates is disabled, one or more of the following conditions exist:
- The depot entry does not match the product type.
- The VVRR fields for the agent and the depot entry are not the same, where VV is the version number and RR is the revision number. For example, an entry of 0610 prevents you from applying a fix pack intended for a version 6.2 agent.
- The depot entry is at an older version than the agent.
- The host version field of the depot entry does not contain the host platform for the agent.
- The prereq field of the depot entry does not contain an agent of the same type as the agent itself. For example, if 6.1 UD (DB2 monitoring) is the selected agent, the prereq field in the depot entry must contain a deployment bundle notation such as ud:061000000, which is one way to denote a patch deployment bundle.
Parent topic:
Agent tasks in the Tivoli Enterprise Portal