Deployment Guide Series: IBM Tivoli Monitoring V6.2

352 Deployment Guide Series: IBM Tivoli Monitoring V6.2

6.3.3 Versioning

The Agent Builder agents do not use the Universal Agent versioning system.

They use the same versioning system used by all other IBM Tivoli Monitoring

agents. The developer of the agent assigns a version and determines when a

new version is created. This means that you can have multiple versions of an

Agent Builder agent in an IBM Tivoli Monitoring deployment at the same time and

the monitoring server, portal server, and portal will be able to correctly handle

each of the agents according to its version. You can upgrade a system from one

version to another just like other IBM Tivoli Monitoring agents.

6.3.4 Support of scripts

If you create an Agent Builder agent and put scripts into its project, they will

become part of the agent image and they will be pushed out with the agent when

it is pushed out to a system using remote deployment.

6.3.5 Log file monitoring

The Agent Builder built agents use the same code base as the Universal Agent

File Data Provider. All of the options included in the IBM Tivoli Monitoring V6.2

Universal Agent are also supported in the Agent Builder Agent. Most of the

options can be created using the Eclipse wizard.

6.3.6 Remote browsing

From the Eclipse based Agent Builder, you can remotely browse processes and

services on remote computers. You can also browse WMI, Perfmon, and SNMP.

The remote browser uses native Windows for WMI, Perfmon, and Services. For

all other options, it connects to a Tivoli Enterprise Management Server (TEMS)

to gather data from the remote systems OS agent (process, WMI, and Perfmon).

For SNMP, it browses a local MIB that has been loaded on the Agent Builder

machine.

6.3.7 Generate Migration Agent Mapping file

You can ease the IBM Tivoli Monitoring V5 migration by generating the Agent

Mapping file for Custom Resource Model migration.