Deployment Guide Series: IBM Tivoli Monitoring V6.2

Chapter 4. Upgrading from IBM Tivoli Monitoring V5.1.2 283

򐂰 If the agent is an OS agent, change the infrastructure baseline for the agent to

reflect the new name.

4.7 Migrating custom resource models

The procedure for migrating a custom resource model differs in these possible

respects for one for a standard resource model:

򐂰 When performing the migration, the resource model mapping file used by the

assess command must be created, either by copying and editing an existing

mapping file, or by creating it from scratch.

򐂰 To evaluate this mapping file, you might need to create a Java resource model

plug-in class, which allows you to add your own coding to the standard

evaluation used by the toolkit.

򐂰 If the resource model data collection is different from that used by the

standard resource models, you might also have to create a new agent to

collect the data using the agent builder. For this agent, you will also need to

create an agent mapping file to enable the migration to work correctly.

򐂰 If the data collection in the agent cannot be provided by standard operating

system facilities, you might need to create a Java agent plug-in class to do the

collection.

When these items have been developed and tested, the actual migration follows

exactly the same steps as the migration of standard resource models.

Thus, the procedure for migrating custom resource models requires you take the

following steps:

1. Perform a basic analysis of the resource model to determine the level of

customization. This should help you to determine whether you require

plug-ins or a new agent, or both, in addition to the obligatory resource model

mapping file.

2. Analyze the resource model to list the thresholds, parameters, and other

entities it uses, and render the logic of the resource model in the boolean

expressions required for V6.2.

3. Optionally, use the resource model analyzer tool to create the resource model

mapping file.

4. As an alternative to using the tool, use the data you recorded in step 2 and

create the resource model mapping file manually. You can create the file from

scratch, or base it on an existing mapping file from a standard resource

model, or one you have already created yourself.