Deployment Guide Series: IBM Tivoli Monitoring V6.2

284 Deployment Guide Series: IBM Tivoli Monitoring V6.2

5. If the resource model mapping file contains any of the following, create a Java

resource model plug-in class that the toolkit will run during the migration:

– Complex parameters that need special coding to be parsed

– Context variables that need to be manipulated

– A restriction on the creation of the V6.2 situation that has a condition that

requires special coding

6. If the resource model data collection cannot be performed by the standard

agent at the appropriate endpoints, create a custom agent using the agent

builder tool.

7. If you have created a custom agent, create the corresponding agent mapping

file.

8. If the custom agent cannot collect the data you require using the standard

operating system facilities, create a Java agent plug-in class that the toolkit

will run during the migration.

9. Assess the profile that contains the custom resource model, as described in

4.4.4, “Phase C: Migrating the profiles” on page 231.

10.Check very carefully that the created situations map exactly what you require,

paying particular attention that the V6.2 agent attributes have been correctly

described.

11.The custom resource model can now be fully migrated.

All the above mentioned steps are described in a very detailed way in Part 3,

“Migrating custom resource models”, in Upgrading from IBM Tivoli Monitoring

V5.1.2, GC32-1976.

4.7.1 Resource model Analyzer tool

For customers that have developed their own resource models on IBM Tivoli

Monitoring V5.1.2, the resource model Analyzer Tool (RM Analyzer Tool) offers

specific migration assistance.

The RM Analyzer tool is expected to be published shortly in the IBM Tivoli

Monitoring section of the IBM Service-Oriented Architecture Business Catalog

(OPAL) at:

http://catalog.lotus.com/wps/portal/tm

The RM Analyzer Tool provides a quick start for creating resource model

mapping files.

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

This tool is separate from the migration toolkit, operates independently, and can

be used in conjunction with the IBM Tivoli Monitoring Migration Toolkit to prepare

the conversion of IBM Tivoli Monitoring V5.1.2 PAC resource model indications

into IBM Tivoli Monitoring V6.2 situations.

This tool installs easily, is easy to invoke, and executes very quickly on a per

resource model basis to analyze one or more resource models.

With the input being a single resource model or any number of resource models

combined into a single subdirectory, the RM Analyzer Tool conducts a best-effort

analysis of the VisitTree logic in the resource model and writes the output to two

XML files:

򐂰 One output file contains the XML representation of logic relative to resource

model indications.

򐂰 A resource model mapping file that can be used as input into the migration

toolkit.

The mapping files are not in final form, but can be completed with minimal effort

from the user. The analysis output contains information that recommends and

assists in completing the mapping file.

The RM Analyzer Tool will not successfully process all types of custom resource

models and custom metrics into situations. It supports JavaScript™ resource

models only (.dmjsws and .jrm). In those cases where the tool cannot interpret

the resource model successfully, it states that and gives information pertaining to

why it could not.

It will, however, provide an XML template that can be used to manually create

situations that will run in an IBM Tivoli Monitoring V6.2 environment.

Note: PAC stands for Proactive Analysis Component. For PAC resource

models, we refer to any base IBM Tivoli Monitoring V5.1.2 and IBM Tivoli

Monitoring (for Databases, Applications, Messaging, and Collaboration and so

on) resource models.

Note: The RM Analyzer Tool does not support Visual Basic®. Thus, for

resource models that were generated by Visual Basic, the user will be

required to generate their own mapping files using the resultant template

provided by the RM Analyzer Tool.