Migrating Classifications with Migration Manager

Transcription

1 IBM Maximo Asset Management 7.1 IBM Maximo Asset Management for IT 7.1 IBM Tivoli Change and Configuration Management Database IBM Tivoli Service Request Manager 7.1 Migrating Classifications with Migration Manager

2 Note Before using this information and the product it supports, read the information in Notices on page 8 This edition applies to version 7, release 1, modification 1 of IBM Maximo Asset Management, IBM Maximo Asset Management for IT, IBM Tivoli Change and Configuration Management Database, and IBM Tivoli Service Request Manager, and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 2

3 Contents Migrating Classifications with Migration Manager... 4 Pre-requisite... 4 Introduction... 4 Usage... 4 Limitations... 5 Notices... 7 Trademarks

4 Migrating Classifications with Migration Manager The Classification object structure is migration content added to the product for Maximo Base Services Fix Pack Pre-requisite Reader must be thoroughly familiar with Classifications application. Reader must also be experienced with the use of object structures and Migration Manager. Introduction A new object structure has been added to Migration Manager to enable the migration of classifications between product environments. The object structure is DMCLASSIFICATION. This document describes the characteristics of the object structure and its limitations. This document does not describe the characteristics of classification, classification hierarchy or the Classifications application. The following diagram shows the business objects included in the object structure: A new migration group has been added to Migration Manager that includes the DMCLASSIFICATION object structure. The group is CLASSIFICATIONDATA. This group does not include any dependencies on other migration groups. Usage The DMCLASSIFICATION object structure can be used with either snapshot or change package definitions. Simply define the package and include the CLASSIFICATIONDATA migration group in the definition. With a snapshot package, SQL criteria can be associated with the DMCLASSIFICATION object structure to collect a specified set of CLASSSTRUCTURE records and their related records. 4

5 A CLASSSTRUCTURE record may depend upon an organization and/or site. A CLASSUSEWITH record may depend upon a specific business object. A CLASSSPEC record may depend upon a domain, a unit of measure, site and/or organization. A CLASSSPECUSEWITH record may depend upon organization, site or specific business object. These data are not part of the DMCLASSIFICATION object structure. They must each be migrated separately to the target database or manually created using appropriate application in the target database prior to migrating any classification. If not, migration of classifications may fail as business rules are not met that require existence of organization, site, unit of measure or business object. The following table lists how such related data can be configured in a target database: Related Data Preparing Related Data Organization/Site Domain Business Object Unit of Measure Migrate from source using DMORGANIZATION object structure or manually create directly in target using Organizations application Migrate from source using DMMAXDOMAIN object structure of manually create directly in target using Domains application Migrate from source using DMMAXOBJECTCFG or manually create directly in target using Database Configuration application; if created manually, the configuration changes should be applied successfully using configdb utility Manually create directly in target using Assets application NOTE: If a choice is made to migrate organization, site, domain and business object, that migration can be achieved using separate packages or a single package. It is beyond the scope of this document to describe the migration steps. Limitations DMCLASSIFICATION object structure relies on a non-persistent attribute called HIERARCHYPATH to determine if an update or insert needs to be performed. Removing this non-persistent attribute from the object structure will cause processing errors during import. HIERARCHYPATH attribute should remain part of the object structure. DMCLASSIFICATION object structure requires the non-persistent attribute called DATATYPE to be part of the XML to adhere to classification object business rules. Removing this non-persistent attribute from the object structure will cause processing errors during import. DATATYPE attribute should remain part of the object structure. 5

6 DMCLASSIFICATION object structure does not migrate data pertaining to the CLASSIFICATION table. Any attributes of CLASSIFICATION table that are managed through the Classifications application are not supported. This includes the DESCRIPTION attribute of CLASSIFICATION table. Any update of a classification description performed through the Add/Modify Properties Classifications dialog in Classifications application is not supported. The primary key of the CLASSSTRUCTURE table is CLASSSTRUCTUREID. This attribute is auto-keyed out of the box. However, it is not exposed in the user interface of the Classifications application. If the attribute is exposed in the user interface and end users are allowed to substitute their own arbitrary key values instead of accepting the default auto-key value, this object structure will fail to migrate such classifications. The object structure is designed to rely on the default auto-key value to facilitate proper migration. Migration of a classification hierarchy where a parent classification has been changed thereby altering the parent-child classification relationship is not supported. If the HIERARCHYPATH value is changed in a source database as a result of changing the parent classification in a parent-child relationship, Migration Manager will no longer be able to identify the correct CLASSSTRUCTURE record. This in turn will cause processing errors during import. With snapshot migration packages, the processing action for XML documents in the package can be either replace or addchange. However, as long as a matching HIERARCHYPATH value is found in the target database based on information in the XML, only an update will be performed. The type of processing action does not matter. The DMCLASSIFICATION object structure does not support a scenario where there are two different classifications with the same HIERARCHYPATH value. This can be done using the Classifications application only. 6

7 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. 7

8 Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear. 8

9 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at Windows is a trademark of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. 9