160 likes | 307 Views
IBM Tivoli Provisioning Manager 7.1.1 Migration and Upgrade. Topics. Feature Objective (Problems Solved) Feature Overview Common Use Cases. TPM 7.1.1 Migration/Upgrade Objective. Migrate TPM 5.1.1.2 server to TPM 7.1.1 level Gradual, phased migration for agents and depots
E N D
Topics • Feature Objective (Problems Solved) • Feature Overview • Common Use Cases
TPM 7.1.1 Migration/Upgrade Objective • Migrate TPM 5.1.1.2 server to TPM 7.1.1 level • Gradual, phased migration for agents and depots • N-1 principle of backward (version) compatibility • Agents move to 7.1.1 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 5.1.1.2 • Operational support of older agents (down to 5.1.0.2). • Existing agent certificates to work with new agent manager • Preserve the “Interface to the TPM black box” • Upgrade TPM 7.1 sevrer to TPM 7.1.1 level
Topics • Feature Objective (Problems Solved) • Feature Overview • Common Use Cases
TPM 7.1.1 Migration/Upgrade Overview • Migration: (TPM 5.1.1.2 TPM 7.1.1) • ‘Big switch’ migration approach • Upgrade: (TPM 7.1 TPM 7.1.1) • ‘In-place’ upgrade approach
Our Migration Process Focuses on … • Artifacts and Interfaces • Migrating the artifacts from 5.1.1.2 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
Phase 0: Artifacts to migrate Minimal set needed to migrate. Largely done when DCM is moved Additional work needed Tooling Provided Some artifacts are not easy to move. Need Manual means: Docs Provided
TPM 5.1.1.2 to 7.1.1. Migration: Gradual, phased migration process that leverages the existing infrastructure, minimizes disruption, and accommodates failures Common UI for Process Automation (Server + Desktop) TPM7.1.1 Tpae 7.1.1 Depots, & Fed. DMSs 5 Datacenter & Distributed Servers 7.1.1 agents
Details of Process TPM User Interface Common UI for Process Automation (Server + Desktop) TPM 7.1.1 TPM 5.1.1.2 • Preparing for migration on the current 5.1.1 server box • upgrade 511 box to 5112 level • upgrade old agents to the right level (i.e., CAS 1.3.2.29) using the current workflows in TPM 5.1.1.2. • 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 5.1.1.2) • Prepare a 7.1.1 server box in parallel • Installs 7.1.1 server code and prepares it for the big switch • Big switch to 7.1.1 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 7.1.1 level, in convenient batches TPAE Scalable Distribution Infrastructure (SDI) Datacenter & Distributed Servers
Topics • Feature Objective (Problems Solved) • Feature Overview • Common Use Cases
TPM 7.1.1 Migration Use Case (5.1.1.2 7.1.1) • 5.1.1.2 Box Pre-requisites (on the original 5.1.1.2 system) • Upgrade 511 box to 5112 FP level • Upgrade old agents to the right level (i.e., CAS 1.3.2.29) • 5.1.1.2 Box Preparation (on the original 5.1.1.2 system) • Run tpm511backup command to backup 5.1.1.2 artifacts including LDAP, database, configuration etc. • 7.1.1 Box preparation Prerequisite environment (on the new 7.1.1 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 7.1.1 system) • Run tpm711restore command to restore 5.1.1.2 database and configuration artifacts on 7.1.1 system • Run tpm711migrate command to migrate database; migrate/register/configure CAS; install/update CDS/DMS; configure WAS • Install BSI and TPM Web Components (on 7.1.1 Admin Workstation) • Install BSI and TPM Web Components • update hostname(ip) for Maximo in the maximo.property files • Change Host Names (on the new 7.1.1 system) • Run tpm711ChangeDBHost command to change database hostname to use the original 5.1.1.2 hostname • Run tpm711ChangeOtherHost command to change hostname for other TPM artifacts
TPM 7.1.1 Migration Use Case (Cont..) • Run master tcdriver update wkf - to finalize tcdriver migration - Triggered when TPM started (on the new 7.1.1 system) • Recapture OSD images (on the new 7.1.1 system) • Upgrade each depot, federated DMS pair from 5.1.1.2 to the 7.1.1 level • Upgrade each set of endpoints from 5.1.1.2 to the 7.1.1 level • Restore LDAP contents • Restore LDAP password (depends on import ldif to be done) • Migrate 5.1.1.2 access groups (depends on import ldif to be done) • Recreate 5.1.1.2 Inventory Extension reports (if needed)
TPM 7.1.1 Upgrade Use Case (from 7.1 7.1.1) • On TPM 7.1 server, run TPM 7.1.1 upgrade installer • In-place upgrade on the same 7.1 box • Upgrade base from Tpae 7.1.3 to Tpae 7.1.5 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 7.1.1 level using the agent upgrade workflow
TPM 7.1.1 Agent Upgrade Use Case • Same process as 5.1.1.2 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)
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