1. IBM Tivoli Provisioning Manager 7.1.1 Migration and Upgrade
IBM Software Group | Tivoli Brand Software
IBM Tivoli Provisioning Manager Migration and Upgrade
IBM Tivoli Monitoring for Transaction Performance v52 ESP Workshop Workshop Guide

2. Topics Feature Objective (Problems Solved) Feature Overview
Common Use Cases

3. TPM 7.1.1 Migration/Upgrade Objective
Migrate TPM server to TPM level
Gradual, phased migration for agents and depots
N-1 principle of backward (version) compatibility
Agents move to in batches. Failures accommodated.
One-step switch of TPM server
Little to no additional hardware required
Most artifact migration automatic. Rest: Data export & Docs
In-place upgrade of agents beginning
Operational support of older agents (down to ).
Existing agent certificates to work with new agent manager
Preserve the “Interface to the TPM black box”
Upgrade TPM 7.1 sevrer to TPM level

4. Topics Feature Objective (Problems Solved) Feature Overview
Common Use Cases

5. TPM 7.1.1 Migration/Upgrade Overview
Migration: (TPM  TPM 7.1.1)
‘Big switch’ migration approach
Upgrade: (TPM 7.1  TPM 7.1.1)
‘In-place’ upgrade approach

6. Our Migration Process Focuses on …
Artifacts and Interfaces
Migrating the artifacts from to 7.1.1
Interfaces of different kinds
APIs (also Web service interfaces)
Data Formats (e.g., xml import formats)
CLIs, Data Model entities, workflow language
Skills and Tools
Skills are closely related to the current tools customers use (for example, SPE, APDE)
Preserving the tools - Preserves skill investment
Timeline
Ability to stretch the migration process so remote endpoints can migrate over time
Ability to complete a critical amount of migration in a single maintenance window

7. Phase 0: Artifacts to migrate
Minimal set needed to migrate.
Largely done when DCM is moved
Additional work needed
TPM Workflows Preserved in TPM 7.1.1
Activity Plans Preserved in TPM 7.1.1
SPBs Preserved in TPM 7.1.1
Users, Roles, user/resource groups and Security Policies Migration Tooling and some manual mapping to new roles & permissions
TPM Compliance Checks Preserved in TPM 7.1.1
Static Resource Groups -- Covered by schema & data migration (configure Sec. manually)
DCM contents and Customer extensions -- Schema Migration and DB migration in 7.1.1
Default file repositories (eg. SPB storage) -- Will migrate with DB in 7.1.1
Discovery/Inventory scan schedules (TPM) -- Will migrate with DB in
Tooling
Provided
Some artifacts are not easy to move. Need Manual means:
OOTB Reports and Customer Reports Manually rebuild using BIRT (can start w/ current sql queries)
Customer code leveraging TPM Web service interfaces -- Minor changes needed
Dynamic Group Definitions in TPM 5.x -- Manually create in (can start w/ current sql queries)
Web Replay Scenarios from TPM 5.x – Manually recreate in (now Tpae based)
TPMfOSD-EE images from TPM – Need to deploy and recapture images in 7.1.1
Favorite Tasks in TPM 5.x Manually recreate in 7.1.1
Docs
Provided

8. TPM to Migration: Gradual, phased migration process that leverages the existing infrastructure, minimizes disruption, and accommodates failures
Common UI for Process
Automation (Server + Desktop)
TPM 7.1.1
Tpae
7.1.1 Depots,
& Fed. DMSs 5
Datacenter &
Distributed
Servers
7.1.1 agents

9. Distribution Infrastructure (SDI)
Details of Process
Common UI for Process
Automation (Server + Desktop)
TPM User Interface
Preparing for migration on the current server box
upgrade 511 box to level
upgrade old agents to the right level (i.e., CAS ) using the current workflows in TPM
Prepare necessary data export files (e.g., ldiff file for users/groups in TPM)
backup 5112 db
shut down 5112 box (Safety – allows reverting to )
Prepare a server box in parallel
Installs server code and prepares it for the big switch
Big switch to server in a maintenance Window
System is operational now …
After some days … start migrating depots & federated DMSs
After all of SDI migrated, migrate agents to level, in convenient batches
TPM 7.1.1
TPM
TPAE
Scalable
Distribution Infrastructure (SDI)
Datacenter &
Distributed
Servers

10. Topics Feature Objective (Problems Solved) Feature Overview
Common Use Cases

11. TPM 7.1.1 Migration Use Case (5.1.1.2  7.1.1)
 Box Pre-requisites (on the original system)
Upgrade 511 box to 5112 FP level
Upgrade old agents to the right level (i.e., CAS )
Box Preparation (on the original system)
Run tpm511backup command to backup artifacts including LDAP, database, configuration etc.
7.1.1 Box preparation Prerequisite environment (on the new system)
Install middleware on 711 box (use 711 MWI installer)
Install WAS ifix
Create max71db and maximo user
Install TPM core
7.1.1 Box Big Switch (on the new system)
Run tpm711restore command to restore database and configuration artifacts on system
Run tpm711migrate command to migrate database; migrate/register/configure CAS; install/update CDS/DMS; configure WAS
Install BSI and TPM Web Components (on Admin Workstation)
Install BSI and TPM Web Components
update hostname(ip) for Maximo in the maximo.property files
Change Host Names (on the new system)
Run tpm711ChangeDBHost command to change database hostname to use the original hostname
Run tpm711ChangeOtherHost command to change hostname for other TPM artifacts

12. TPM 7.1.1 Migration Use Case (Cont..)
Run master tcdriver update wkf - to finalize tcdriver migration - Triggered when TPM started (on the new system)
Recapture OSD images (on the new system)
Upgrade each depot, federated DMS pair from to the level
Upgrade each set of endpoints from to the level
Restore LDAP contents
Restore LDAP password (depends on import ldif to be done)
Migrate access groups (depends on import ldif to be done)
Recreate Inventory Extension reports (if needed)

13. TPM 7.1.1 Upgrade Use Case (from 7.1  7.1.1)
On TPM 7.1 server, run TPM upgrade installer
In-place upgrade on the same 7.1 box
Upgrade base from Tpae to Tpae using the Solution Installer delta PMP install mechanism
Upgrade TPM web component using the Solution Installer delta PMP install mechanism
Upgrade TPM Core components (including the tcdriver upgrade and the schema upgrade)
Upgrade agent to the latest level using the agent upgrade workflow

14. TPM 7.1.1 Agent Upgrade Use Case
Same process as agent upgrade
Uses SDI Depots and Agent Credentials
The agent upgrade is performed using SPB
The SPB contain the TCA and subagents upgrade
A SPB per platform is created (AIX, HPIA64, HP, Linux86, LinuxPPC, LinuxS390, SolarisIX86, solaris and Windows)

15. BACK UPS

16. Summary Compelling reasons to move to 7.1.1
Gradual, phased, and failure-tolerant process
No need to buy additional hardware – gradual switchover of server, depots
Preserves investment in artifacts (SPBs, Activity Plans) and Skills
Flexible timeline for migration while minimizing service down time