Migration Manager Guide - IBM

3y ago
75 Views
3 Downloads
573.96 KB
79 Pages
Last View : 16d ago
Last Download : 6m ago
Upload by : Amalia Wilborn
Transcription

IBM Maximo Asset Management 7.1IBM Maximo Asset Management for IT 7.1IBM Tivoli Change and Configuration Management Database 7.1.1IBM Tivoli Service Request Manager 7.1Migration Manager Guide

NoteBefore using this information and the product it supports, read the information in “Notices” on page 67.This edition applies to version 7, release 1, modification 0 of IBM Maximo Asset Management, IBM Maximo Asset Managementfor IT, and IBM Tivoli Service Request Manager, and to version 7, release 1, modification 1 of IBM Tivoli Change andConfiguration Management Database, and to all subsequent releases and modifications until otherwise indicated in neweditions. Copyright International Business Machines Corporation 2008. All rights reserved.US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorp.

ContentsAbout This Publication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vIntended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vChapter 1: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration Manager concepts and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package definitions and packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration objects and migration groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Compiled sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Sources and target environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration Manager applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object Structures application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration Groups application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration Manager application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migrating configuration content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11122334444455Chapter 2: Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Planning configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Determine the types of configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Organizing your configuration content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Content in the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Content outside the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Migration between environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Scheduling migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Preparing for migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Validating the integrity of your configuration content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Backing up your database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Chapter 3: Migrating configuration content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Pre-migration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Create migration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Create migration groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Organize and upload compiled source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Structure of a package definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package definition types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Snapshot package definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Change package definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package definition statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package Definition report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17171718181919202020212222 Copyright IBM Corp. 2008iii

Package statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How package content affects deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package content types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Deployment process steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Restrictions on package deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Post-migration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package Life Cycle report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222323242424282930Chapter 4: Troubleshooting migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package creation errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package distribution errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Package deployment errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration Manager application logger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Error messages and corrective actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313131313232Appendix A: Migration object structures included with the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Data Dictionary migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Document Library migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Application migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Resources migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Functional migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Application Security migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Reporting migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the System migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Integration migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Business Process Management migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object structures in the Migration migration group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393945464849505354565962Appendix B: Migration groups included with the product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71ivMigration Manager

About this publicationThis guide helps you to use the Migration Manager set of applications to migrateconfiguration data from one product environment to another.Intended audienceThis guide is for deployment managers, deployment specialists, databaseadministrators, and component developers. Copyright IBM Corp. 2008v

Intended audienceviMigration Manager

1OverviewMigration overviewIn the context of Migration Manager, migration is the process of promotingproduct configuration content from one product environment to another.Configuration content is the data that the system requires to construct and run abusiness application in the application server and make it available to end usersin the enterprise. Product environments can include development, test, andproduction.For example, you might want to extend the Purchase Order application bymaking the following configuration changes:TAdd a new table and several columns to the database (using the DatabaseConfiguration application)T Add a new domain that contains several lookup values (using the Domainsapplication)T Add a new tab in the Purchase Order application screen presentation (usingthe Application Designer application)T Develop a workflow process to automate an approval of data managedthrough the new table (using the Workflow Designer application)All of the preceding configuration changes are product configurations that aretypically created in a development environment and promoted to production.Migration Manager overviewMigration Manager is a set of applications that enables a structured set of steps topromote your configurations from one product environment to another.Use Migration Manager to perform the following tasks: Copyright IBM Corp. 2008TOrganize and consolidate all the configurations and customizations for a newproduct environmentTPromote your configurations from a development environment to a testenvironment for validationTPromote your validated configurations from a test environment to aproduction environment.1

Migration Manager overviewMigration Manager concepts and componentsPackage definitions and packagesYou manage the configuration content that you want to migrate in the form ofpackage definitions and packages. You migrate configuration content inpackages. A package is an instance of a package definition. A package definitionserves as a template from which you create unique packages. A packagedefinition organizes the content to be migrated.A package contains data either from the product database or from files that aredeployed on the application server. Data from the product database is organizedin migration objects and migration groups. Files are organized as compiledsources.Package contentsTypes of packagedefinitions and packagesA package contains the following:TPackage manifest - contains important information about a package, such asthe source environment versions, the migration objects whose data isincluded in the package, the types of content in the package, the record countfor each migration object, and readme information entered in the sourceenvironment by an administrator to help during deployment to a targetenvironment.TPackage metadata - defines metadata information that pertains to the packagedefinition of the package to be deployed in a target environmentTStructural configuration content - data that must be used to create or updatedatabase tables, columns, views, keys, indexes and sequencesTNon-structural configuration content - configuration content that resides inthe form of records of various configuration tablesTCompiled sources - files that include source code customizations, libraries,configuration files, and report executable filesTHistory data - life cycle information regarding the packageThere are two types of package definitions and packages:TTSnapshotChangeA snapshot package contains “as is” configuration content collected for a packageon demand. You define the snapshot package at any time, even after theconfiguration changes have been made.A change package contains configuration content collected over a period of time.The data collected is based on database inserts, updates and deletes that occurbetween the time you activate the package definition and the time that you createthe package. A change package can contain configuration records inserted,updated, or deleted by designated users. You define the change package beforethe changes occur.2Migration Manager

Migration Manager overviewMigration objects and migration groupsConfiguration content is organized into migration objects and migration groups.Migration objectsA migration object is a group of one or more related business objects thatrepresent one or more database tables.Examples of migration objects are:TWorkflow processesIntegration channelsT Cron tasksT User interface presentationsT Security groupsTYou define migration objects in a development instance and then move them intotest and production environments. The product includes a comprehensive set ofmigration objects. Migration objects are implemented using the Object Structuresapplication. You can also create your own migration objects using thisapplication.Migration groupsA migration group is a collection of related migration objects.ExampleThe Business Process Management (BPM) migration group contains severalmigration objects, including the DMWFPROCESS migration object (themigration object for workflow process definitions included with the product).The DMWFPROCESS migration object consists of 16 business objects,including the following logically related business objects:TWFPROCESSLONGDESCRIPTIONT WFNODET WFTASKTA migration group can be either internal or user-defined. Internal migrationgroups are included with the product and are linked to other logically relatedmigration groups called dependencies. You cannot modify internal migrationgroups. User-defined migration groups are migration groups that you create.Compiled sourcesYou can include compiled sources in a package definition.Compiled sources define content from outside the database that packages containwhen they are migrated. Compiled sources are files that must be part of theEnterprise Archive (EAR) file of the product. They can include many types offiles, such as class files, archive files, image files, and properties files. They canalso be aggregations of files from the server file system that must be migratedwith configuration data from the database.If you need to migrate multiple compiled source files, aggregate them into asingle compressed file to simplify the migration process.Overview3

Migration Manager overviewSources and target environmentsThe environment from which you are migrating content is the sourceenvironment. The environment to which you are migrating content is the targetenvironment. Migration Manager identifies sources and targets uniquely acrossall of your product environments. Migration Manager generates thisidentification in the form of a string comprising three parts

Migration overview In the context of Migration Manager, migration is the process of promoting . A migration group can be either internal or user-defined. Internal migration groups are included with the product and are linked to other logically related migration groups called dependencies. You cannot modify internal migration

Related Documents:

Modi ed IBM IBM Informix Client SDK 4.10 03/2019 Modi ed IBM KVM for IBM z Systems 1.1 03/2019 Modi ed IBM IBM Tivoli Application Dependency Discovery Manager 7.3 03/2019 New added IBM IBM Workspace Analyzer for Banking 6.0 03/2019 New added IBM IBM StoredIQ Suite 7.6 03/2019 New added IBM IBM Rational Performance Test Server 9.5 03/2019 New .

IBM Spectrum Protect Snapshot (formerly IBM Tivoli Storage FlashCopy Manager) For more details about IBM Spectrum Copy Data Management, refer to IT Modernization . A9000R snapshots, see IBM Hyper-Scale Manager for IBM Spectrum Accelerate Family: IBM XIV, IBM FlashSystem A9000 and A9000R, and IBM Spectrum Accelerate, SG24-8376.

IBM 360 IBM 370IBM 3033 IBM ES9000 Fujitsu VP2000 IBM 3090S NTT Fujitsu M-780 IBM 3090 CDC Cyber 205 IBM 4381 IBM 3081 Fujitsu M380 IBM RY5 IBM GP IBM RY6 Apache Pulsar Merced IBM RY7

Data Migration Planning Analysis, Solution Design and Development Mock Migration Pilot Migration Released Data Migration Active Data and User Migration Inactive Data Migration Post Migration Activities Small Bang The details for each step include: Data Migration Planing - Develop the migration strategy and approach, and define the scope,

IBM Rational Asset Manager V7.0 IBM Rational Software Architect V7.0 IBM Rational Application Developer V7.0 IBM Rational BuildForge V7.0 IBM Tivoli Service Request Manager V6.2.1 IBM Tivoli Provisioning Manager for Software Deployment, which is comprised of the following products: IBM

Product Analysis for IBM Lotus Domino, IBM Lotus Notes, IBM Lotus iNotes, IBM Lotus Foundations, IBM Lotus Quickr, IBM Lotus Sametime, IBM Lotus Connections, and IBM LotusLive. This report is intended for Organizations, Vendors, and Investors who need to make informed decisions about the Email and Collaboration market. Figure 1: Worldwide IBM .

IBM Wave for z/VM IBM Operations Manager for z/VM IBM Backup and Restore Manager for z/VM IBM Tivoli Storage Manager Extended Edition IBM Tivoli OMEGAMON XE on z/VM and Linux In this lab, you will work with IBM Tivoli Storage Manager Extended Edition . Separate labs are available for the remaining products in the suite.

Dictator Adolf Hitler was born in Branau am Inn, Austria, on April 20, 1889, and was the fourth of six children born to Alois Hitler and Klara Polzl. When Hitler was 3 years old, the family moved from Austria to Germany. As a child, Hitler clashed frequently with his father. Following the death of his younger brother, Edmund, in 1900, he became detached and introverted. His father did not .