Deployment Guide Series: IBM Tivoli Monitoring V6.2

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

Figure 4-15 Migrated TEC server

4.4.5 Phase D: Migrating the profile managers

As with the other phases in the migration process, this one is made of four steps:

assess, analyze, migrate, and status check.

In this case, the resources to be migrated are profile managers.

Step 13: Migrate profile managers – assess

This step results in the creation of an XML file for each profile manager that

determines which endpoints (managed systems) will be included in which

managed system list.

The full mapping logic is:

򐂰 The subscribers to the profile manager become managed system lists. There

is one managed system list for each profile and agent type.

򐂰 The distribution relationship between profiles and subscribers is applied to

situations and managed systems.

256 Deployment Guide Series: IBM Tivoli Monitoring V6.2

򐂰 It assesses all profiles contained in the profile manager (unless the –p filter is

specified or the profile has already been assessed).

򐂰 It assesses all endpoint contained in the profile manager (unless the –e filter

is specified or the endpoint has already been assessed).

򐂰 If there are subscribed profile managers, they and their profiles and endpoints

are similarly assessed.

򐂰 The -o flatten option can be used to avoid running the assess recursively in

environments with nested profile managers.

Example 4-24 shows the execution of the steps in our environment.

Example 4-24 Migrate profile managers - assess step

We started from the profiles managers list in our environment:

C:\Tivoli\db\cairo.db\AMK\analyze\profiles>wlookup -ar ProfileManager

|grep ITM

ITM_AIX_PM 1713357986.1.1359#TMF_CCMS::ProfileManager#

ITM_CUSTOM_PM 1713357986.1.1374#TMF_CCMS::ProfileManager#

ITM_HPUX_PM 1713357986.1.1379#TMF_CCMS::ProfileManager#

ITM_LINUX_PM 1713357986.1.1368#TMF_CCMS::ProfileManager#

ITM_WINDOWS_PM 1713357986.1.1371#TMF_CCMS::ProfileManager#

Whit the below command we assessed the profile manager called

ITM_AIX_PM:

C:\Tivoli\db\cairo.db\AMK\analyze\profilemanagers>witmmtk assess -pm

ITM_AIX_PM

AMKUT0016I Processing the request.

.

AMKUT5003I Loading the resource snapshot for the assessment.

AMKUT0057I Loading the infrastructure baseline file:

"C:\Tivoli\db\cairo.db\AMK\analyze\scans\1713357986.xml".

AMKUT5006I Starting the resource assessment.

AMKUT5080I Converting profile manager ITM_AIX_PM.

AMKUT5007I All resources are assessed. Processing is complete.

.

AMKUT0008I The command completed successfully. See log

"C:\Tivoli\db\cairo.db\AMK\logs\log_wmtkassess_20071010_16_24_46.log"fo

r more information.

The generated XML file for the above profile manager is listed in Example 4-25

on page 257.

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

Example 4-25 XML file for the profile manager ITM_AIX_PM

<?xml version="1.0" encoding="UTF-8"?>

<!--Copyright IBM Corporation 2006-->

<?xml-stylesheet type="text/xsl"

href="../../data/stylesheet/ProfileManagerAssess.xsl"?>

<ProfileManagerAssess aggregateStatus="0" comment="" name="ITM_AIX_PM"

xmlns="http://www.ibm.com/tivoli/itm/assess/profilemanager"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.ibm.com/tivoli/itm/assess/profilemanager

ProfileManagerAssess.xsd">

<ManagedSystemList

affinity="00f20000000000000000000000000000#m000000000" comment=""

name="557_KUX" product="KUX" profile="AIX" status="NOT_DEPLOYED">

<ManagedSystem hostname="server2.itsc.austin.ibm.com"

name="server2.itsc.austin.ibm.com:KUX" source="server2-ep"/>

<ManagedSystem hostname="paris.itsc.austin.ibm.com"

name="paris.itsc.austin.ibm.com:KUX" source="paris-ep"/>

</ManagedSystemList>

</ProfileManagerAssess>

Step 14: Migrate profile managers – analyze

After creating the assess files, you should check that the number of files created

corresponds with your expectations, given the input to the command.

Each profile manager assess file contains elements that describe the managed

system lists that will be created. You may decide you want to check this

information.

For further details, refer to Chapter 18, “Assess data file XML reference” in

Upgrading from IBM Tivoli Monitoring V5.1.2, GC32-1976, which describes the

assess file, and gives details on how you can view it. It also explains the naming

convention for managed system lists.

Step 15: Migrate profile managers – migrate

The migrate tool is used to:

򐂰 Create the V6 managed system lists.

򐂰 Create the distribution relationship between situations and managed systems.

򐂰 Distribute situations to the appropriate managed systems and activate them.

򐂰 Associate navigation items using the association class for the Tivoli

Enterprise Portal.

򐂰 Update the profile manager assess file status.