Tivoli Tivoli Provisioning Manager

Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Unix GC32-1619-00

Note: Before using this information and the product it supports, be sure to read the general information under Notices on page 75. First Edition, June 2004 This edition applies to Version 2.1 of Tioli Proisioning Manager (product number 5724-I14) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2003, 2004. All rights resered. May only be used pursuant to a Tioli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tioli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieal system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, proided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. Copyright International Business Machines Corporation 2003, 2004. All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Copyright International Business Machines Corporation 2003, 2004. All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents Preface............... Publications.............. Tioli Proisioning Manager library..... Prerequisite publications......... Accessing publications online.......i Accessibility..............i Tioli technical training..........i Contacting Software Support.........i Conentions used in this book........ ii Path ariables used in this book....... ii Knowledge requirements......... iii Oracle knowledge........... iii Part 1. Before you begin migration.. 1 Chapter 1. About Tioli Proisioning Manager.............. 3 Chapter 2. Planning for migration.... 5 Migration paths.............5 Required software leels..........6 AIX considerations...........7 New software in this release.........7 Supported hardware............7 Assigning user roles............8 Other migration considerations........9 Chapter 3. Preparing for migration... 11 Updating your system...........11 Identifying the ersion of your existing system 11 Updating your system for migration.....11 Backing up your system..........11 General guidelines for backup and migration..12 Backing up serers...........12 Backing up the Tioli Proisioning Manager installation folder...........13 Backing up the data center model......13 Backing up workflows..........13 Backing up log files..........14 Backing up configuration files.......15 Saing reports............15 Setting up customized workflows for migration..15 Naming workflows, parameters, and ariables.. 16 Creating an automation package......16 Next steps..............20 Part 2. Installing and upgrading software............. 21 Chapter 4. System prerequisites.... 23 Enabling SNMP for Tioli NetView......23 Modifying the kernel parameter settings.....23 Required packages............25 Setting the DB2 Uniersal Database transaction log size.................25 Chapter 5. Upgrading the database serer............... 27 Upgrading DB2 Uniersal Database......27 Upgrading the DB2 Uniersal Database serer..27 Upgrading the DB2 Uniersal Database client..29 Loading the CMDB tablespace.......29 Using Oracle as the database serer......30 Chapter 6. Upgrading the directory serer............... 31 IBM Tioli Directory Serer.........31 Upgrading on Solaris..........31 AIX migration roadmap for Tioli Directory Serer...............33 Upgrading on AIX...........37 Upgrading the IBM Directory Serer 5.1 client..41 Microsoft Actie Directory.........42 Chapter 7. Upgrading WebSphere Application Serer.......... 43 Uninstalling WebSphere Application Serer Application Client............43 Uninstalling WebSphere Application Serer 5.0.1..43 Before you begin...........43 Pre-installation steps...........47 Creating WebSphere MQ file systems.....47 Setting up the group IDs and the user ID...48 Installing WebSphere Application Serer 5.1...48 Applying WebSphere Application Serer fixes...50 Applying the WebSphere Application Serer 5.1 Cumulatie Fix 3...........50 Applying the WebSphere MQ V5.3 fix....51 Importing the security certificate for Microsoft Actie Directory............51 Chapter 8. Migrating Tioli Proisioning Manager.............. 53 Before you begin............53 Installing Tioli Proisioning Manager 2.1....53 Part 3. Migrating data....... 57 Chapter 9. Migrating data....... 59 Data that is migrated automatically......59 Data that cannot be migrated........59 Installing core automation packages......59 Migrating customized workflow components...60 Workflow dependencies.........60 Conerting modified workflow components..60 Installing the conerted workflow components 61 Copyright IBM Corp. 2003, 2004 iii

Changing the locale of workflows......62 Chapter 10. Verifying migration.... 65 Starting the serer and signing on to the Web interface...............65 User accounts.............65 Data center model............65 Applications and proisioning........65 Customized workflows..........65 Part 4. Post-migration configuration 67 Chapter 11. Additional configuration tasks............... 69 Setting up SSL encryption.........69 Configuration for new and updated features...69 Importing new data center objects......70 Part 5. Appendixes......... 71 Appendix. Administratie Tasks.... 73 Starting the serer............73 Stopping Tioli Proisioning Manager.....73 Signing on to the Web interface........74 Signing off from the Web interface.......74 Notices.............. 75 Trademarks..............76 i Tioli Proisioning Manager Migration Guide

Preface This book describes the steps to migrate a preious ersion of Tioli Proisioning Manager It is intended for system administrators or for anyone else responsible for performing installation and configuration tasks. Publications Read the descriptions of the Tioli Proisioning Manager library, the prerequisite publications, and the related publications to determine which publications you might find helpful. After you determine the publications you need, refer to the instructions for accessing publications online. Tioli Proisioning Manager library The publications in the Tioli Proisioning Manager library include: Tioli Proisioning Manager Installation Guide Tioli Proisioning Manager Migration Guide Tioli Proisioning Manager Release Notes Tioli Proisioning Manager Problem Determination Guide The remaining product documentation is aailable in the online help, which can be launched from the Web interface for the product. To enable ease of printing for help topics, PDF books hae been created directly from the online help contents. The topics hae been grouped and the following PDFs hae been created: Workflow Deeloper s Guide: This document contains the online help topics relating to creating workflows and automation packages. Tioli Proisioning Manager Online Help: This PDF contains the entire online help. Prerequisite publications To use the information in this book effectiely, you must hae some prerequisite knowledge, which you can obtain from the following publications: WebSphere Application Serer Information Center, aailable from http://www.ibm.com/websphere. You can also download the WebSphere Application Serer documentation plug-in and install it in the Tioli Proisioning Manager. This will allow you to iew the WebSphere Application Serer documentation in the same Information Center as the Tioli Proisioning Manager help. DB2 Uniersal Database Information Center, aailable from www.ibm.com/db2. Tioli Directory Serer documentation, aailable from the Tioli Software Information Library. The instructions in this book proide information on installing and configuring the bundled (packaged) software to work with Tioli Proisioning Manager. This book does not document how to install and configure third-party software supported by Tioli Proisioning Manager, such as Oracle9i Database and Microsoft Actie Copyright IBM Corp. 2003, 2004

Accessibility Directory. The exception to this are steps that require specific settings or configuration to configure that software for Tioli Proisioning Manager. Because eery datacenter and enironment is unique, it is expected that users following the instructions in this book hae the necessary prerequisite knowledge to install, configure and administer this software in their unique enironment. Accessing publications online The publications for this product are aailable online in Portable Document Format (PDF) in the Tioli software library: http://www.ibm.com/software/tioli/library Tioli technical training Contacting Software Support To locate product publications in the library, click the Product manuals link on the left side of the library page. Then, locate and click the name of the product on the Tioli software information center page. Product publications include release notes, installation guides, user s guides, administrator s guides, and deeloper s references. Note: To ensure proper printing of PDF publications, select the Fit to page check box in the Adobe Acrobat Print window (which is aailable when you click File Print). Accessibility features help a user who has a physical disability, such as restricted mobility or limited ision, to use software products successfully. With this product, you can use assistie technologies to hear and naigate the interface. You also can use the keyboard instead of the mouse to operate all features of the graphical user interface. For Tioli technical training information, refer to the IBM Tioli Education Web site: http://www.ibm.com/software/tioli/education. Before contacting IBM Tioli Software Support with a problem, refer to the IBM Tioli Software Support site by clicking the Tioli support link at the following Web site: http://www.ibm.com/software/support/ If you need additional help, contact Software Support by using the methods described in the IBM Software Support Guide at the following Web site: http://techsupport.serices.ibm.com/guides/handbook.html The guide proides the following information: Registration and eligibility requirements for receiing support Telephone numbers, depending on the country in which you are located A list of information you should gather before contacting Software Support i Tioli Proisioning Manager Migration Guide

Conentions used in this book This book uses the following highlighting conentions: Boldface type Monospace type Italic type Indicates commands or graphical user interface (GUI) controls such as names of fields, icons, or menu choices. Indicates examples of text you enter exactly as shown, file names, and directory paths and names. Used to emphasize words. Italics also indicate names for which you must substitute the appropriate alues for your system. Important These sections highlight especially important information. Attention These sections highlight information intended to protect your data. Oracle 2000 AIX Solaris 2000 Indicates information specific to Oracle9i Database or using Oracle9i Database with Tioli Proisioning Manager. Indicates information specific to AIX or using AIX with Tioli Proisioning Manager. Indicates information specific to Solaris operating system or using Solaris operating system with Tioli Proisioning Manager. Path ariables used in this book This guide uses the following ariables to represent directory paths: DB2_installdir This is the installation directory for DB2 Uniersal Database. The following are the installation directories for DB2 Uniersal Database: 2000 AIX /usr/opt/db2_08_01 Solaris 2000 /opt/ibm/db2/v8.1 Oracle_installdir This is the installation directory for Oracle9i Database. The following are the installation directories for Oracle9i Database: 2000 AIX /oracle/u01/app/oracle/product/9.2.0.1.0 Solaris 2000 /opt/oracle/u01/app/oracle/product/9.2.0.1.0 IDS_installdir This is the installation directory for Tioli Directory Serer. The following are the installation directories for Tioli Directory Serer: Preface ii

2000 AIX /usr/websphere/appserer Solaris 2000 /opt/websphere/appserer WAS_installdir This is the installation directory for WebSphere Application Serer. The following are the installation directories for WebSphere Application Serer: 2000 AIX /usr/websphere/appserer Solaris 2000 /opt/websphere/appserer Knowledge requirements This is the installation directory for Tioli Proisioning Manager. For migrated systems, the directory is /home/thinkcontrol both before and after migration. Tioli_commondir This is the location of the Tioli Common Directory. The Tioli Common Directory is a central location on systems running Tioli software for storing sericeability-related files, including log files. In Tioli Proisioning Manager, the default alue is /ar/ibm/tioli/common. This book should be read by system administrators or anyone else responsible for installing and configuring Tioli Proisioning Manager. People who are installing and configuring Tioli Proisioning Manager should hae knowledge in the following areas: IBM AIX or Sun Solaris operating systems Basic operating system commands DB2 Uniersal Database Enterprise Serer Edition or Oracle9i Database operation, configuration, and maintenance WebSphere Application Serer IBM HTTP Serer operation, configuration and maintenance Basic SQL commands Jaa programming XML The Internet Refer to the online help for more information on configuring and administering Tioli Proisioning Manager. Oracle knowledge Solaris 2000 This section lists some of the important Oracle concepts that you should know before using Oracle with Tioli Proisioning Manager. You can find information on these items in the Oracle9i Database Concepts document proided with your Oracle system. Before installing and setting up your Oracle system, it is highly recommended iii Tioli Proisioning Manager Migration Guide

that you read and understand the Oracle documentation supplied with your purchase of Oracle, in particular, the Concepts, Administration, and Installation information. Some of the concepts that you need to understand before configuring your Oracle system to work with WebSphere Commerce include: An Oracle Instance Database structure and space management. This includes: Logical database structure - Tablespaces - Schemas and schema Objects. - Data blocks, extents, and segments. Physical database structure - Datafiles - Redo log files - Control files Structured Query Language (SQL) Memory structure and processes System Global Area (SGA) Program Global Area (PGA) Oracle process architecture including serer and background processes Communications Software and Net9 The Program Interface Database Administrator user names SYS SYSTEM System Identifier (SID) Databases, tablespaces, and datafiles The SYSTEM tablespace Using multiple tablespaces Space management in tablespaces Online and offline tablespaces Temporary tablespaces Datafiles Preface ix

x Tioli Proisioning Manager Migration Guide

Part 1. Before you begin migration The Tioli Proisioning Manager system consists of many software products and subcomponents, each with its own underlying technology. It is therefore important to understand the oerall migration process and plan for the migration of your own system. Chapter 1, About Tioli Proisioning Manager, on page 3 Chapter 2, Planning for migration, on page 5 Chapter 3, Preparing for migration, on page 11 Copyright IBM Corp. 2003, 2004 1

2 Tioli Proisioning Manager Migration Guide

Chapter 1. About Tioli Proisioning Manager This guide describes how to migrate Tioli Proisioning Manager Version 1.1 for Unix to Version 2.1. It is intended for system administrators or for anyone else responsible for performing installation and configuration tasks. Use this guide to migrate your existing Tioli Proisioning Manager system as follows: 1. Prepare for migration using the information in Part 1, Before you begin migration, on page 1. This part of the guide proides planning and system backup information. 2. Update your software. Complete the tasks described in Part 2, Installing and upgrading software, on page 21 to upgrade your system. This includes prerequisite software as well as the Tioli Proisioning Manager software. 3. Migrate your data. The upgrade process automatically migrates some of your system data. Complete the tasks described in Part 3, Migrating data, on page 57 to migrate data that is not automatically processed during software upgrades. This part of the guide also proides guidance in erifying your migration. 4. Reiew Part 4, Post-migration configuration, on page 67 to learn about additional Tioli Proisioning Manager features that you might want to set up. Copyright IBM Corp. 2003, 2004 3

4 Tioli Proisioning Manager Migration Guide

Chapter 2. Planning for migration Migration paths The process to migrate your system to Tioli Proisioning Manager inoles the following high-leel tasks: 1. Planning the oerall migration at your site including the key decisions on the migration approach to adopt. 2. Taking inentory of your current assets, such as machines, software, databases, custom code, and so on. 3. Backing up your existing system. This includes: Tioli Proisioning Manager serer LDAP serer (if it is installed on a separate serer) Database serer 4. Upgrading prerequisite software to the leels required by Tioli Proisioning Manager. 5. Upgrading Tioli Proisioning Manager software. 6. Manually migrating data that is not migrated during the software upgrade process. 7. Verifying your migrated system. 8. Configuring new or updated features. This includes configuring additional data center assets, setting up reporting capability, and setting up integration with external products. This migration guide proides guidance in these areas. The following migration paths are supported: Tioli Proisioning Manager 1.1.2 to Tioli Proisioning Manager 2.1 The following migration paths are not supported: Tioli Proisioning Manager 1.1.0 or 1.1.1 to Tioli Proisioning Manager 2.1 Tioli Intelligent ThinkDynamic Orchestrator 1.1.0, 1.1.1, or 1.1.2 to Tioli Proisioning Manager 2.1 If your current system is at the ersion 1.1.0 or 1.1.1 leel, you must update your system to ersion 1.1.2 before you begin migration. For information about identifying and updating your current product leel, see Updating your system on page 11. This release supports local in-place migration only. In this approach, you replace your existing Tioli Proisioning Manager system with Tioli Proisioning Manager 2.1. This release does not support remote migration from a test system to your production system or coexisting ersions of Tioli Proisioning Manager. Copyright IBM Corp. 2003, 2004 5

Attention Since an in-place migration requires you to shut down your production system, consider the time required to take your system down for the duration of the migration. Careful planning is also required for recoery back to the original configuration in case you encounter a problem with the migration. Required software leels The following tables map the software ersions and leels required for Tioli Proisioning Manager. For a more detailed description of supported platforms, topologies, and software prerequisites, refer to the Tioli Proisioning Manager 2.1 Installation Guide. Note: The migration process does not support switching from one platform to another platform. Table 1. Required database Database DB2 Uniersal Database Enterprise Serer Edition Oracle9i Database Only supported in a Solaris enironment Tioli Proisioning Manager 1.1.2 DB2 Uniersal Database Workgroup Unlimited Edition 8.1.2 (Version 8.1 Unlimited Edition with fix pack 2) Solaris 2000 Oracle9i Database Release 2 Enterprise Edition with fix pack 1 Tioli Proisioning Manager 2.1.0 DB2 Uniersal Database Workgroup Unlimited Edition 8.1.3 (Version 8.1 Unlimited Edition with fix pack 3) Solaris 2000 Oracle9i Database Release 2 Enterprise Edition with fix pack 1 Database serers not listed in this table are not supported this includes ersions or editions of DB2 Uniersal Database not listed in this table. Table 2. Directory serer Directory serer Tioli Proisioning Manager 1.1.2 Tioli Directory Serer 5.1 5.2 Tioli Proisioning Manager 2.1.0 Microsoft Actie Directory Windows 2000 Serice Pack 2 Windows 2000 Serice Pack 4 Table 3. WebSphere Web Application Serer WebSphere Application Serer WebSphere Application Client Tioli Proisioning Manager 1.x Tioli Proisioning Manager 2.1 5.0.1 5.1.0.3 (Version 5.1 with Cumulatie Fix 3) 5.0.1 Not required 6 Tioli Proisioning Manager Migration Guide

AIX considerations 2000 AIX New software in this release Supported hardware Tioli Directory Serer 5.2 requires DB2 Uniersal Database Enterprise Edition, which is not supported by Tioli Proisioning Manager. If Tioli Directory Serer 5.2 is currently installed on the same AIX serer as DB2 Uniersal Database Workgroup Serer Unlimited Edition, you hae the following migration options: Moe DB2 Uniersal Database Workgroup Serer Unlimited Edition to the Tioli Proisioning Manager serer during the migration process so that you can install DB2 Uniersal Database Enterprise Edition on the Tioli Directory Serer 5.2 serer. Install Tioli Directory Serer 5.2 on a new serer. The serer does not hae to be running the same operating enironment as the Tioli Proisioning Manager serer. For AIX, you must also install DB2 Uniersal Database Enterprise Edition. For other operating enironments, Tioli Directory Serer 5.2 can share the same DB2 Uniersal Database Workgroup Serer Unlimited Edition installation as Tioli Proisioning Manager. For more information, refer to AIX migration roadmap for Tioli Directory Serer on page 33. This release includes the following software that was not aailable in preious releases of Tioli Proisioning Manager: WebSphere Studio Workbench to proide access to the Tioli Proisioning Manager information center. Tioli NetView for discoery features (optional) Language Pack (optional) This section lists the hardware requirements for Tioli Proisioning Manager 2.1. Ensure that you reiew the requirements for this release and make the necessary changes before you begin migration. Note: This does not include the hardware requirements for other software components such as WebSphere Application Serer, DB2 Uniersal Database, and Tioli Directory Serer which may be different. Ensure each machine in your Tioli Proisioning Manager configuration meets the minimum requirements for each of the software packages you plan on installing on that machine. For complete details about the prerequisites for each software application, refer to the documentation for that product, as described in Prerequisite publications on page IBM Compatible PC with Microsoft Windows 2000 or 2003 Serer: 2.8 GHz Intel Pentium 4 processor or equialent Minimum 4GB of free memory Minimum 20 GB of free disk space CD-ROM drie 2000 AIX IBM pseries with AIX 5.2: Chapter 2. Planning for migration 7

1 GHz CPU Minimum 4GB of free memory Minimum 20 GB of free disk space CD-ROM drie Solaris 2000 Sun SPARC or x86 Serer with Solaris 8 and 9: 1 GHz CPU Minimum 4GB RAM Minimum 20 GB free disk space CD-ROM drie Assigning user roles IBM Compatible PC with Red Hat Linux Adanced Serer 2.1: 2.8 GHz Intel Pentium 4 processor or equialent Minimum 4GB of free memory Minimum 20 GB of free disk space CD-ROM drie iseries Models that support LPAR with minimum 450CPW in Linux partition: Minimum 4GB RAM Minimum 20 GB free disk space CD-ROM drie In Tioli Proisioning Manager 1.1.2, indiidual access rights are assigned to user accounts. In release 2.1, user accounts are assigned to specific user roles that are associated with specific access rights. Administrator Proides access to all features. Assign this role to users who hae the authority to manage user accounts and make changes to any part of the system. The default user account (tioappadmin) is assigned the Administrator role. Operating Mode Controller Proides the ability to change the global operating mode and the operating mode of applications and clusters. Assign this role to users who hae the authority to control the degree of automation in the creation and approal of deployment requests. DCM Operator Proides the ability to manage data center assets in the data center model (DCM) and user accounts. Assign this role to data center administrators. Cluster and Pool Manager Proides the ability to manage clusters and spare pools. Assign this role to users who are responsible for adding and remoing serers from clusters and resource pools. Fault Manager and Runtime Performance Adisor Proides the ability to manually manage deployment requests and the failed status indicator for data center assets. Assign this role to users who are responsible for monitoring the system and making manual deployment changes. 8 Tioli Proisioning Manager Migration Guide

Reiew the users that you currently hae defined, and determine what role is appropriate for each user. Other migration considerations Some factors that can impact your migration are: In-place migration impact The leel of customization at your data center The size of your data center The leel of integration with third-party systems How well your system complies with recommended practices and standards Chapter 2. Planning for migration 9

10 Tioli Proisioning Manager Migration Guide

Chapter 3. Preparing for migration Updating your system This chapter describes the steps you need to perform with your existing system before you can upgrade the system software. Updating your system Backing up your system Setting up customized workflows for migration on page 15 If your current system is at the ersion 1.1.0 or 1.1.1 leel, you must update your system to ersion 1.1.2 before you begin migration. Identifying the ersion of your existing system Tioli Proisioning Manager 1.1.2 is required for migration, and some product features and procedures described in this guide are also specific to a particular product leel. If you do not know the current product leel of your existing system, you can erify it on the Welcome page in the Tioli Proisioning Manager Web interface. If you are currently logged onto the Web interface, click Home to iew the Welcome page. Note: On the Welcome page, Version 1.1 represents product leel 1.1.1 (Version 1.1 with Fix Pack 1). Version 1.2 represents product leel 1.1.2 (Version 1.1 with Fix Pack 2). Updating your system for migration To update your system, apply Tioli Proisioning Manager Fix Pack 2. You can obtain the fix pack from the Tioli Software Support site. On the IBM Software Support page at http://www.ibm.com/software/support/, search for reference number 4006668. Backing up your system Refer to the Fix Pack 2 Readme for details about applying the fix pack. After you hae applied the fix pack, erify that your updated Tioli Proisioning Manager system is working. 1. Start the Tioli Proisioning Manager serer. 2. Verify that you can log on to the Web interface successfully. For details about how to start the serer and access the Web interface, see Administratie Tasks, on page 73. Currently Tioli Proisioning Manager only supports in-place migration, which requires you to completely replace your existing system. It is therefore important to back up your existing system before you begin the migration process. This ensures that you can recoer the system if a migration problem occurs, and that your configuration and system data are stored for any required manual data migration processes. Copyright IBM Corp. 2003, 2004 11

Tioli Proisioning Manager does not include tools for backing up or restoring your system. You must follow the standard procedures for backup and recoery that are used by your company. Ensure that your system backup includes the following software and data: A full backup of the main Tioli Proisioning Manager serer. Backing up the entire serer ensures that you hae a working copy of all the software components installed on Tioli Proisioning Manager directory serer. A full backup of other system serers with supporting software, including the database serer and directory serer. A backup of data that you want to archie or migrate after your system is upgraded. This includes reports, automation packages, workflows, commands, and log files. General guidelines for backup and migration Ensure that you follow the guidelines in this section as you perform backup and migration tasks. Reiew the backup procedures in this chapter before you begin the backup process. For some procedures, you must extract or obtain information from your existing system, and then sae the data that you extract or collect. Most of the data required for these procedures is aailable from the Web interface. For most backup procedures, you must stop the Tioli Proisioning Manager serer. You should also ensure that workflows are not running before you perform system backup or migration tasks. For instructions on starting and stopping the serer and accessing the Web interface, see Administratie Tasks, on page 73. To search for workflows that are currently running, perform the following steps: 1. Log on to the Web interface. 2. If you hae applications running in automatic mode, put the applications in maintenance to preent further deployments. 3. Click System configuration and workflow management >Workflow Executions. 4. On the Workflow Executions page, search for workflows with a status of In progress. Any workflows that appear are currently running. You should wait until the workflows hae completed before starting system backups and migration tasks. Backing up serers Back up your current Tioli Proisioning Manager system so that you can recoer it if necessary. Perform your system backup in accordance with the documentation that is proided with your operating system or with any specialized backup and restore software that you use. Typically, you can back up your system to a tape drie, a ZIP drie, or some other file system. Back up the following serers: The Tioli Proisioning Manager serer. The database serer, if it is on a separate machine. The directory serer, if it is on separate machine. 12 Tioli Proisioning Manager Migration Guide

Backing up the Tioli Proisioning Manager installation folder Back up the Tioli Proisioning Manager installation directory separately from your full system backup. This enables you to compare files in your current system with files in your upgraded system after migration, and can help you to diagnose any migration issues. In release 1.1.2, Tioli Proisioning Manager is installed in the /home/thinkcontrol subdirectory for the tioadmin user. Backing up the data center model Tioli Proisioning Manager 1.1.x releases do not support exporting of the data center model. Since the Tioli Proisioning Manager 2.1 installation program automatically migrates the data center model, you do not need to hae a copy of your existing data center model for migration purposes. Howeer, if you want to store a backup copy of your existing data center model, consider one of the following options: If you used an XML file to create your data center model, you can create a backup copy of this file. You can update this file to reflect your current data center configuration before you store the file. If you do not hae an XML file that defines your data center model, generate reports of your customers, applications, and data center inentory in Tioli Proisioning Manager, and then sae or print the reports. You can then use the information in the reports to rebuild your data center model, if necessary. Reports are aailable from the Reports naigation tree in the Web interface. Backing up workflows Any workflows that you hae created or modified must be exported and saed for migration. Tioli Proisioning Manager 2.1 includes a tool to back up these files. The backup tool: Extracts and saes all workflow components in your existing system to a backup folder. Generates log files of conersion actiity and reports of all workflow changes. Keep a copy of the backed up files. During the software upgrade process, the Tioli Proisioning Manager installation program replaces all existing workflows with updated workflows. If you do not back up and migrate workflow components that you created or modified, they will be inaccessible after the software is upgraded. If you made changes to workflow components, you must manually migrate the changed components. After the backup is complete, you must create automation packages that contains the customized components so that you can conert them to the proper format for Tioli Proisioning Manager 2.1 and install them on your migrated system. Notes: 1. The workflow backup tool is specific to release 1.1.x systems. You cannot use this tool to back up workflows after migration. 2. The backup process can take some time, depending on the number of workflows in your system and the amount of customization that you hae performed. Chapter 3. Preparing for migration 13

Before you back up workflow components Before you run the workflow backup tool, erify the following: If you plan to migrate your customized workflows, ensure that the workflows hae unique names. If you modified core workflows proided with Tioli Proisioning Manager 1.1.x but did not change the workflow names, name conflicts with Tioli Proisioning Manager 2.1 workflows will preent you from installing your customized workflows during the workflow migration process. You should also ensure that all names are alid. For information about requirements for workflow, parameter, and ariable names, see Naming workflows, parameters, and ariables on page 16. If you need to rename workflows, perform the following steps: 1. To identify workflows that hae been modified, run the backup tool as described in Backing up workflow components. 2. Reiew the log files that the tool creates to identify modified workflows. 3. In Tioli Proisioning Manager, rename modified workflows that still hae their original names. 4. Remoe the backup files, and then run the workflow backup tool again to sae your renamed workflows and other workflow components. The JAVA_HOME enironment ariable is set to the directory where IBM Jaa JDK 1.4.1 is installed. Backing up workflow components To back up workflow components: 1. Log on to the Tioli Proisioning Manager serer as tioadmin. 2. On Tioli Proisioning Manager, Version 2.1 CD, copy the /tools/wfbackup folder to the TIO_installdir/tools directory. The backup script is called wfbackup.sh. 3. Run the following command./wfbackup.sh The script backs up workflows that hae been added or changed, and displays a list of workflows that hae been modified, added, or remoed. You should sae the full set of backed up files and reports with the other system data that you are backing up. By default, backup files and report files are stored in the following directories: Back up files are stored in the./backup directory. Report files that describe changes to workflow components are stored in the./reports directory. The.diff files show the details of your workflow changes. The following log files list the backup actiity: Table 4. Workflow backup log files File name workflow.log command.log requesttype.log Contents Changes to workflows Changes to commands Changes to request types Backing up log files Back up your log files so that you hae a record of past system actiity and errors. This includes log files created for Tioli Proisioning Manager and WebSphere Application Serer. 14 Tioli Proisioning Manager Migration Guide

Log files for Tioli Proisioning Manager 1.1.x are stored in the TIO_installdir/logs directory. Log files for WebSphere Application Serer are stored in the WAS_installdir/logs/serer1 directory. Note: After you migrate your system, log files for Tioli Proisioning Manager 2.1 will be stored in the Tioli_commondir/COP/logs directory. Your old log files will not be remoed. Backing up configuration files If your current system is currently integrated with external software systems, such as Tioli Configuration Manager, consider backing up configuration files on the Tioli Proisioning Manager serer. For additional information about releant configuration files, refer to the documentation for the automation package that you used to integrate the external product. Saing reports Tioli Proisioning Manager 2.1 uses new reporting tools to collect report data and generate reports. In this release, Tioli Data Warehouse collects and stores data for reports, and Crystal Reports generates reports. The types of aailable reports hae also changed. In preious releases, reports were based on the current configuration of your system. In Tioli Proisioning Manager, reports are historical. You can generate reports based on a specified period in the past. If there are specific reports for your existing system that you want to keep, you must generate the reports, and then print or sae them. To generate a report, log on to the Web interface, and then click the report that you want to iew in the Reports naigation tree. Setting up customized workflows for migration If you made changes to workflows in your existing system, you need to prepare your customized workflow files for migration. Perform the following steps: 1. Reiew the.diff files that were created by the workflow backup tool to identify changes to workflows. You can then determine which workflow components you want to migrate. The workflow backup tool is described in Backing up workflows on page 13. 2. Create directory for each automation package (.tcdrier file) that you want to migrate in a temporary location. The files for each automation package will be placed in a contents subdirectory. Examples: TIO_installdir/custom_workflows/old/my_router/contents TIO_installdir/custom_workflows/old/my_switch/contents Note: The contents subdirectory is new in Tioli Proisioning Manager 2.1. 3. Create target directories where you want to store your conerted workflow components. Examples: TIO_installdir/custom_workflows/new/my_router TIO_installdir/custom_workflows/new/my_switch Chapter 3. Preparing for migration 15

Note: Ensure that both your source and target directories hae full file access permissions so that the all workflows can be accessed by the conersion tool during the workflow conersion process. 4. Organize your automation packages. If you already hae.tcdrier files for the workflow components you want to conert, extract the file structure for each automation package to its own directory. For example, if you hae an automation package called my_router.tcdrier, extract the files to the TIO_installdir/custom_workflows/old/my_router/contents directory. After extracting the files, the file structure includes the following directories: TIO_installdir/custom_workflows/old/my_router/contents TIO_installdir/custom_workflows/old/my_router/contents/workflow TIO_installdir/custom_workflows/old/my_router/contents/doc TIO_installdir/custom_workflows/old/my_router/contents/bin TIO_installdir/custom_workflows/old/my_router/contents/lib TIO_installdir/custom_workflows/old/my_router/contents/TC-INF If you did not create automation packages with your customized workflows, create the file structure required for each automation package using the files in the./backup directory. For information about the required file structure for an automation package, see Creating an automation package. Copy each automation package file structure to the appropriate directory created in step 2. Naming workflows, parameters, and ariables To ensure that your workflows can be installed properly, ensure that you use alid names for workflows, parameters and ariables. Only the following characters can be used in workflow names: a-z, A-Z, 0-9, underscore (_), and period (.). The first character can be any of: a-z, A-Z, or underscore (_). It cannot be 0-9 or a period (.) The last character in the name cannot be a period (.) Interening characters between the first character and the last character in the workflow can be: a-z, A-Z, 0-9, underscore (_), or period (.) Workflow descriptions can be 255 characters in length. Only the following characters can be used for workflow parameter and ariable names: a-z, A-Z, 0-9, and underscore (_). The first character can only be: a-z, A-Z, or underscore (_). It cannot be 0-9. The remaining characters can be: a-z, A-Z, 0-9, or underscore (_). Note: Any Unicode character can be used to enter comments in workflow scripts. Creating an automation package Automation packages are deice driers that support one particular type of software or physical deice. It contains all of the workflows, database table entries, JAR files, and external scripts that are necessary to operate that physical deice, for example a Cisco CSS11000 switch. For the purposes of migration, you must create an automation package that contains all the workflow components that you added or modified and want to migrate. 16 Tioli Proisioning Manager Migration Guide

Existing automation packages are located in the TIO_installdir/driers directory on the Tioli Proisioning Manager serer. When you use the workflow backup tool, the files are stored in a backup directory as described in Backing up workflow components on page 14. Contents of automation packages Automation packages hae a specific internal structure. The workflow components must be organized in this structure when you want to create a new automation package. When you use the conerttcdrier tool to conert your workflows, all indiidual files must be aailable in the required file structure. When you need to install an automation package, the file structure must be zipped into a single file with a.tcdrier file extension. The structure of an automation package includes the following directories: command This directory contains all of the commands that are aailable for that specific physical deice. doc This directory contains the documentation for implementation of the automation package in a readme.txt file. jaa-plugin This directory contains all of the Jaa plug-ins that are installed and used on that specific physical deice. TC-INF This directory contains the manifest file for the automation package. For details on the content of the manifest file, refer to Manifest file contents. workflow This directory contains a collection of workflows that hae been deeloped to operate that specific physical deice. lib This directory contains any Jaa JAR files that need to be copied to the TIO_installdir/driers/lib directory and made aailable to the deployment engine class path. bin This directory contains any script files to be copied to a repository, for example TIO_installdir/bin files, which are then used by workflows. Manifest file contents The manifest file for automation packages are an.xml file, tc-drier.xml, that contains the name and the ersion number of the automation packages, the ersion number of the automation package template, and describes all of the automation package dependencies on other automation packages. The manifest file includes the following main sections: <dependencies> This section lists all of the other driers that the current automation package depends on. <actions> This section lists all of the separate classes that are necessary to install separate items like Jaa driers, commands, and so on. <items> This section lists all the items to be installed on the automation package. Each item identifies a certain operation that will be performed on that automation package. Chapter 3. Preparing for migration 17

<deice-models> This section lists all the items to be installed on the automation package. Each item identifies a certain operation that will be performed on that automation package. <post-install-workflows> This optional section names a workflow along with its parameters to be executed after all the items are installed. This workflow may be one installed by the current Automation Package, or one preiously installed. <property> This optional section defines a macro substitution that can be used for any subsequent quoted strings in the manifest file, using an Ant like syntax. For example, if we hae the following entry: <property name="tc.pkg" location="com.thinkdynamics.kanaha.tcdriermanager.action" /> then, whereer ${tc.pkg} occurs in an attribute string inside tc-drier.xml, a substitution is made. <software=products> This section defines any software product entries to be installed in the Data Center Model database. The syntax is identical to the <software> element in the XML format used by the xmlimport utility, but has been extended to allow using the ${xxx} properties substitutions within attribute alues. <drier-name> Name of the drier <drier-ersion> Optional ersion number 18 Tioli Proisioning Manager Migration Guide <description> Short, one sentence description of the purpose of this Automation Package. <documentation> Specifies the name of a text file in the Automation Package contents that proides an in-depth description and any special instructions. Here is an example of the syntax: <documentation location="doc/readme.txt"/> The following is an example of an XML manifest file for the AIX-Operating-System: Note: Some lines may be split in two, with the second line indented, for presentation purposes only. All lines, in particular those beginning with <item name= should be written on a single line with no line breaks. <?xml ersion="1.0" encoding="utf-8"?>  <tc-drier> <tc-drier-format>1.0</tc-drier-format> <drier-name>aix-operating-system</drier-name> <ersion>1.0</ersion>

<description>this Automation Package contains workflows for controlling AIX serers</description> <documentation location="doc/aix-operating-system.txt" /> <dependencies> <dependency name="core"/> </dependencies> <property name="tc.pkg" location="com.thinkdynamics.kanaha. tcdriermanager.action"/> <actions> <action name="command" class="${tc.pkg}.simplecommandactions"/> <action name="copy-file" class="${tc.pkg}.copyfileactions"/> <action name="workflow" class="${tc.pkg}.workflowactions"/> <action name="jaa-plugin" class="${tc.pkg}.jaapluginactions"/> </actions> <items> <item name="repository/configip.sh" action="copy-file"> <param name="dest.path" alue="${tc.home}/repository/ AIX-Operating-System/configIP.sh"/> <param name="chmod" alue="755" /> </item> <item name="repository/configroute.sh" action="copy-file"> <param name="dest.path" alue="${tc.home}/repository/ AIX-Operating-System/configRoute.sh"/> <param name="chmod" alue="755" /> </item> <item name="doc/aix-operating-system.txt" action="copy-file"> <param name="dest.path" alue="${tc.home}/driers/ AIX-Operating-System.txt"/> </item>  <item name="jaa-plugin/com.ibm.thinkdynamics.jaaplugin.software.aix. GetRoutingTableInfo.xml" action="jaa-plugin"/> <item name="workflow/aix Software Reboot Async.xml" action="workflow"/> <item name="workflow/aix Software Reboot Sync.xml" action="workflow"/> <item name="workflow/aix Copy File from Local.xml" action="workflow"/> <item name="workflow/aix Remote Remoe File.xml" action="workflow"/> <item name="workflow/aix chde an Interface.xml" action="workflow"/> <item name="workflow/aix Add IP Address.xml" action="workflow"/> <item name="workflow/aix Remoe IP Address.xml" action="workflow"/> <item name="workflow/aix Check OS Install.xml" action="workflow"/> <item name="workflow/aix Apply Routing Table.xml" action="workflow"/> </items> <deice-models> <deice-model name="aix Operating System" category="software Products"> <workflow name="aix Software Reboot Async"/> <workflow name="aix Software Reboot Sync"/> <workflow name="aix Add IP Address"/> <workflow name="aix Remoe IP Address"/> <workflow name="aix Check OS Install"/> <workflow name="aix Apply Routing Table"/> </deice-model> </deice-models> <!-- Chapter 3. Preparing for migration 19

<software-products> <software name="aix" is-deice-model="aix Operating System" ersion="5.0" package_path="_" install_path="_" type="operating_system"> </software> </software-products> --> </tc-drier> Next steps To complete migration of workflow components, seeral additional steps are required: 1. When you hae completed the backup tasks described in this chapter, upgrade your software as described in Part 2, Installing and upgrading software, on page 21. 2. Install the core automation packages proided with Tioli Proisioning Manager by following the steps in Installing core automation packages on page 59. 3. Migrate your customized workflows by following the steps in Migrating customized workflow components on page 60: 20 Tioli Proisioning Manager Migration Guide

Part 2. Installing and upgrading software This part describes how to: Upgrade your prerequisite software to the leels required by Tioli Proisioning Manager. Upgrade Tioli Proisioning Manager software. Prior to upgrading your software, ensure that you back up your system as described in Chapter 3, Preparing for migration, on page 11. If you need to stop any of your software components, see the appropriate installation guide for your product and platform. Chapter 4, System prerequisites, on page 23 Chapter 5, Upgrading the database serer, on page 27 Chapter 6, Upgrading the directory serer, on page 31 Chapter 7, Upgrading WebSphere Application Serer, on page 43 Chapter 8, Migrating Tioli Proisioning Manager, on page 53 Copyright IBM Corp. 2003, 2004 21