Migrating Ticket Templates 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 Ticket Templates 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 Ticket Templates with Migration Manager... 4 Pre-requisite... 4 Introduction... 4 Usage... 4 Limitations... 6 Notices... 8 Trademarks

4 Migrating Ticket Templates with Migration Manager The Ticket Template object structure is content added to the product for Maximo Base Services Fix Pack Pre-requisite Reader must be thoroughly familiar with Ticket Templates 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 ticket templates between product environments. The object structure is DMTKTEMPLATE. This document describes the characteristics of the object structure and its limitations. This document does not describe the characteristics of ticket templates, or the Ticket Templates 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 DMTKTEMPLATE object structure. The group is TICKETTEMPLATEDATA. This group does not include any dependencies on other migration groups. Usage The DMTKTEMPLATE object structure can be used with either snapshot or change package definitions. Simply define the package and include the TICKETTEMPLATEDATA migration group in the definition. With a snapshot package, SQL criteria can be associated with the DMTKTEMPLATE object structure to collect a specified set of TKTEMPLATE records and their related records. 4

5 A TKTEMPLATE record may depend upon Person Group, Person, Service Group, Service, Company, Classification, or Organization. A TKTEMPLTACTIVITY record may depend upon a Job Plan, Organization, Site, Person, Person Group, Company, or Classification. TKTEMPLATESPEC record or TKTEMPLTACTYSPEC record may depend upon an Asset Attribute, or Unit of Measure. These data are not part of the DMTKTEMPLATE object structure. They must each be migrated separately to the target database or manually created in target using appropriate application in the target database prior to or after migrating any ticket template. If not, migration of a ticket template may fail as business rules are not met that require existence of these related data. The following table lists how such related data can be configured in a target database: Related Data Preparing Related Data Organization/Site Person Group Person Service Group/Service Company Classification Job Plan Asset Attribute Unit of Measure Migrate from source using DMORGANIZATION object structure or manually create directly in target using Organizations application Migrate from source using DMPERSONGROUP object structure or manually create directly in target using Person Groups application and link to the migrated ticket template Migrate from source using DMPERSON object structure or manually create directly in target using People application and link to the migrated ticket template Post-migration only: Manually create directly in target using Service Groups application and link to the migrated ticket template Post-migration only: Manually create directly in target using Companies application and link to the migrated ticket template Migrate from source using DMCLASSIFICATION object structure or manually create directly in target using Classifications application Post-migration only: Manually create directly in target using Job Plans application and link to the migrated ticket template Post-migration only: Manually create directly in target using Classifications or Asset application and link to the migrated ticket template Post-migration only: Manually create directly in target using Assets application and link to the migrated ticket template NOTE: A ticket template can be created and saved without any of the above related data. The related objects are listed above so that there is awareness that when a ticket template migration results in deployment error, the reason for the error may be validation failures against such related data. 5

6 NOTE: If a choice is made to migrate the related data supported by Migration Manager, that migration can be achieved using separate packages or a single package. It is beyond the scope of this document to describe the associated migration steps. Limitations The TEMPLATEID attribute which serves as the primary key for the TKTEMPLATE business object is enabled for auto-key out of the box. The DMTKTEMPLATE object structure implementation assumes that auto-key is enabled. With this assumption, during deployment into a target environment, a new auto-key value is generated for a ticket template being imported using Migration Manager. Thus, the auto-key value of a ticket template in source environment is not migrated as auto-key value into target environment. In order to enable an update of existing ticket template from source to target, the object structure implementation uses as alternate key a persistent attribute called EXTERNALREFID of the TKTEMPLATE business object. The source provided auto-key value is always held as the value of this attribute and this allows Migration Manager to perform an update from source to target. This attribute should not be modified in any form in either source or target environment. Such modification may cause the migration to stop working. If developers intend not to use auto-key values for the TEMPLATEID attribute, but want user-specified values only to be brought from source to target environments, they should use Database Configuration application to un-restrict the TEMPLATEID attribute in both source and target. The auto-key itself should be turned off for the TKTEMPLATE object using the Database Configuration application in both source and target. Finally, the alternate key defined on TKTEMPLATE object of DMTKTEMPLATE object structure should be removed from source and target using Object Structures application. In this situation, end users must provide a unique value for the TEMPLATEID attribute whenever they create a new ticket template. If the auto-key capability remains enabled but the TEMPLATEID attribute has been un-restricted and users did not override the generated auto-key value, that generated auto-key will be brought forward to target and if a ticket template is found with the same key value, the template will be updated even though it may be a complete different template record. This configuration of the TKTEMPLATE object is not recommended as it can break the migration process. 6

7 If ticket templates are to be migrated using change packages, specific steps must be followed as explained below: A change package definition must be activated before any ticket templates are created or updated. Once the desired changes are complete, the change package can be created and distributed. As soon as the change package has been successfully deployed into target, it is critical that Migration Manager s Reset Event Tracking Records action be executed in the source environment for the particular ticket template s change package definition so that older changes are removed from tracking and moved into the tracking history table. This step is necessary to prevent carrying over the same set of older changes to the target which may result in deployment errors. The Ticket Templates application has a limiting behavior in how a ticket template activity specification (TKTEMPLTACTYSPEC record) is created. When a activity specification needs to be created, a check is performed in Ticket Templates application code (against TKTEMPLATE record), if the ticket template has an associated classification. If there is no such classification, the application will return an error message. However, the application permits the creation of activities (as TKTEMPLTACTIVITY records) without any classification being associated with the ticket template itself. This discrepancy in turn imposes a limitation on the migration of ticket templates. In order to migrate a ticket template, it is MANDATORY for users to associate a classification with the template itself when that template will have activities and activity specifications. If users have not associated a classification with the ticket template itself, the migration will fail with a deployment error. DMTKTEMPLATE relies on a HIERARCHYPATH non-persistent attribute of the TKTEMPLATE, TKTEMPLTACTIVITY and TKTEMPLTACTYSPEC business objects. This attribute has been specifically included in the DMTKTEMPLATE object structure. Removal of this attribute from any of the named business objects will cause deployment errors. HIERARCHYPATH attribute must remain part of the object structure. Migration Manager will preserve the status of the ticket template during migration. If a template was active in source environment, it will imported into target environment in an active state. Yes To support Ticket Template migration, two new database indexes have been added at the database level. These indexes are utilized as alternate keys for the DMTKTEMPLATE object structure. Modification or removal of these indexes will prevent successful migration of ticket templates. The indexes are: o Index TKTEMPLTACTIV_NDX2 on TKTEMPLTACTIVITY table o Index TKTEMPLATE_NDX3 on TKTEMPLATE table 7

8 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. 8

9 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. 9

10 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. 10