Tivoli Tivoli Provisioning Manager

Transcription

1 Tioli Tioli Proisioning Manager Version 2.1 Release Notes GI

2

3 Tioli Tioli Proisioning Manager Version 2.1 Release Notes GI

4 Note: Before using this information and the product it supports, be sure to read the general information under Notices on page 33. 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, 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, 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, All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents About this release New in this release Downloads and Updates Product compatibility Installation, migration, upgrade and configuration information Uninstallation information Known limitations, problems and workarounds Limitations Running scripts Serer must be stopped before using XMLImport Deleting applications and clusters created using a deployment plan Naming logical deice operations The SetAttribute logical deice Known problems and workarounds APAR IY57410 patch for DB Websphere MQ error MQJMS2002 fix Error installing WebSphere Application Serer ersion 5.0 fixpack Need to remoe ^M characters on Solaris when using XMLExport/XMLImport Changes to Tioli Proisioning Manager installation InstallShield MultiPlatform (ISMP) display may truncate translated text Icon iew is obscured Cygwin on Japanese, Traditional Chinese and Simplified Chinese Windows When using XMLImport or XMLExport, Jaa exceptions can be ignored The TEC serer needs 3.9 fixpack 1 installed Data center model export Credentials Changing object identifiers Workflows New Virtual Serer doesn t get added to correct Resource Pool Package repository attribute required for cluster during XMLImport unsafe command line parameter for XMLImport Transaction log full error when running post-install.cmd Automount needs to be disabled on Solaris Install the new Warehouse Enablement Pack (WEP) from the IBM Tioli Software Support site Documentation additions Data center fragment Configuring a data center fragment Viewing the software registry Registering software Deregistering software Editing the properties of a software module Creating a deployment plan Selecting a logical application structure Selecting software stacks Selecting an application deployment template Specifying additional deployment parameters Selecting a data center fragment Reiewing the deployment plan Finalizing the deployment plan Documentation updates Installation Guide correction Creating a new workflow Running a workflow using a defined serice access point Copyright IBM Corp. 2003, 2004 iii

6 Viewing workflow run history Stopping a workflow Displaying workflow run history Using the TC_HOME ariable Workflow ariables, parameters, and transitions Setting up Tioli Proisioning Manager to collect utilization data Required data center objects Sample XML file NAT support added SOAP commands for obtaining serer IDs Deploying a monitoring configuration to a serer SOAP command syntax reference: getapplicationmode Viewing the discoery ID of Discoery Objects Updates to running SOAP commands from a remote computer Jaa requirements Procedure for running commands remotely Log files Log file location Trace and message log file names Capacity on demand Creating resource reserations for an application Working with power units and outlets Migration Guide updates Database upgrade changes Changes to data migration Contacting Software Support Notices Trademarks i Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

7 About this release New in this release These release notes describe product changes and enhancements in the Tioli Proisioning Manager product release. Tioli Proisioning Manager ersion 2.1 includes the following new features and enhancements: Monitoring enhancements You can control monitoring of your data center by using external monitoring applications. This release includes support for monitoring of operating systems using IBM Tioli Monitoring. Fault management enhancements You can configure Tioli Proisioning Manager to send an eent to IBM Tioli Enterprise Console when a workflow fails. You can also set up Tioli Enterprise Console so that it can run SOAP commands when a specified eent occurs. Reporting integration with Tioli Data Warehouse Tioli Proisioning Manager now integrates with IBM Tioli Data Warehouse, which proides centralized data storage and reporting capabilities for multiple management systems. You can reiew historical reports of demand and performance, and print or export reports for your records. Workflow deelopment enhancements This release includes seeral workflow deelopment enhancements. The Web-based interface includes an editor that you can use to create or modify workflows. There are also seeral enhancements to workflows themseles, including conditional branching and loops. Managing new deices and external configuration changes Tioli Proisioning Manager can use discoery technologies to identify external configuration changes to deices and new deices that are not currently managed. Discoery capability helps you control external changes to your data center, and ensures that the data center model in Tioli Proisioning Manager accurately reflects the actual data center infrastructure that you are managing. Virtual serer support Virtual serer capability enables you to run multiple serers concurrently on a single computer. In Tioli Proisioning Manager, you can manage irtual serers and the associated host platforms. Globalized product This product is globalized to maximize interoperability and multilingual capability, and to support locale preferences such as date, time, and number formats. The current release is aailable in ten different languages. Copyright IBM Corp. 2003,

8 Downloads and Updates Product compatibility The IBM Orchestration and Proisioning Automation Library is aailable online at: The IBM Orchestration and Proisioning Automation Library deliers the tools and community you need to build your business around on demand automation. New workflows and automation packages and updated readme files for automation packages shipped with Tioli Proisioning Manager will be posted to the IBM Orchestration and Proisioning Automation Library. This site will also contain the most up-to-date information about the full list of aailable workflows. Note: Many workflows cannot be categorized by platform, for example the network deices and storage workflows. Howeer, the workflow for each readme will document any platform-specific information. See the Tioli Proisioning Manager Installation Guide for product compatibility information. Installation, migration, upgrade and configuration information See the Tioli Proisioning Manager Installation Guide for installation and configuration information, and for information on upgrading Tioli Proisioning Manager 2.1 to Tioli Intelligent ThinkDynamic Orchestrator 2.1. See the Tioli Proisioning Manager Migration Guide for information on migrating from Tioli Intelligent ThinkDynamic Orchestrator 1.1 to Tioli Intelligent ThinkDynamic Orchestrator 2.1, or from Tioli Proisioning Manager 1.1 to Tioli Proisioning Manager 2.1. Note: Migration from Tioli Proisioning Manager 1.1 to Tioli Intelligent ThinkDynamic Orchestrator 2.1 is not supported. Uninstallation information See the Tioli Proisioning Manager Installation Guide for uninstallation information. 2 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

9 Known limitations, problems and workarounds Limitations This section describes the limitations that are associated with Tioli Proisioning Manager and proides workarounds for known problems, when workarounds are aailable. Running scripts If you are installing Tioli Proisioning Manager on Windows, any scripts you run must be run in a Windows command window and not in a Cygwin bash shell. Always run the.cmd ersion of the script and not the.sh ersion which might also be installed. Serer must be stopped before using XMLImport Tioli Proisioning Manager processes cache some information and they depend on JMS messages for notification when eents occur (for example, when the system runs logical deice operations and workflows). Howeer, an XML import does not send any notifications to the Tioli Proisioning Manager processes, when it loads the database. If you perform an XML import while the serer is running, unexpected behaior can result. To aoid unexpected behaior, shut down Tioli Proisioning Manager before you run an XML import and then restart it when the XML import is complete. Deleting applications and clusters created using a deployment plan Objects deployed through application topology using a deployment plan are not meant to be deleted manually, as they are created as part of a deployment process. During the deployment process, changes are made to the data center model to accommodate the deployment of the application. These objects, including clusters, are meant to be remoed through an undeployment process, so that not only the objects are remoed, but any data center configurations made to accommodate the objects are also reersed. While a complete undeployment workflow is not currently aailable, you can download a workflow from our support library at Downloads and Updates on page 2. This workflow performs a minimal clean-up of the structures created during the deployment process. This workflow has to be inoked manually, passing the ID of the application to the undeployment process. Before attempting to delete such an application, use this workflow to undeploy it first. Naming logical deice operations When naming a logical deice operation, it must be in the form: XXXX.YYYY, where XXXX is the logical deice name and YYYY is the operation name. Copyright IBM Corp. 2003,

10 The SetAttribute logical deice If you use the SetAttribute logical deice, you must set the AttributeType ariable as an integer. You cannot set the attribute as a string. Known problems and workarounds APAR IY57410 patch for DB2 If DB2 has been upgraded to at least fixpak 3, you must apply APAR IY57410 from the Tioli Proisioning Manager, Version 2.1 Generic Fixes CD. The following describes the process for each platform: AIX 1. Stop Tioli Proisioning Manager. 2. Logon as root. 3. Copy special_10829.tar.z from the Generic Fixes CD. 4. Stop DB2 and ensure all db2 processes are stopped. 5. Extract the contents fo the file to a temporary directory. 6. Make a backup copy of the originally installed DB2 files of the same names. 7. Copy the extracted files to the appropriate directory. 8. Be careful to ensure ownership and permissions are the same as those of the original files. 9. Restart DB2. Solaris 1. Stop Tioli Proisioning Manager. 2. Logon as root. 3. Copy special_10830.tar.z from the Generic Fixes CD. 4. Stop DB2 and ensure all db2 processes are stopped. 5. Extract the contents fo the file to a temporary directory. 6. Make a backup copy of the originally installed DB2 files of the same names. 7. Copy the extracted files to the appropriate directory. 8. Be careful to ensure ownership and permissions are the same as those of the original files. 9. Restart DB2. Linux intel 1. Stop Tioli Proisioning Manager. 2. Logon as root. 3. Copy special_10833.tar.z from the Generic Fixes CD. 4. Stop DB2 and ensure all db2 processes are stopped. 5. Extract the contents fo the file to a temporary directory. 6. Make a backup copy of the originally installed DB2 files of the same names. 7. Copy the extracted files to the appropriate directory. 8. Be careful to ensure ownership and permissions are the same as those of the original files. 9. Restart DB2. 4 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

11 Linux i-series 1. Stop Tioli Proisioning Manager. 2. Logon as root. 3. Copy special_10841.tar.z from the Generic Fixes CD. 4. Stop DB2 and ensure all db2 processes are stopped. 5. Extract the contents fo the file to a temporary directory. 6. Make a backup copy of the originally installed DB2 files of the same names. 7. Copy the extracted files to the appropriate directory. 8. Be careful to ensure ownership and permissions are the same as those of the original files. 9. Restart DB2. Windows 1. Copy hotfixpkg_10831.exe to your local directory. 2. Please stop all DB2 processes before you apply hotfixpkg_10831.exe. Stop all DB2 processes using serices, just running db2stop is not enough. 3. Run: hotfixpkg_ a -f. This will stop all DB2 processes. 4. Under..\sqllib\ run hotfix -l and db2leel. They should display the special build. 5. To uninstall the hotfix, run either hotfix -u HotFixID to uninstall the most recent hotfix; or hotfix -u all to uninstall all the hotfixes. Note: You may also use winzip to extract the hotfixpkg_10831.exe to a directory and run hotfix -f to automatically terminate all DB2 processes and install the hotfix. Websphere MQ error MQJMS2002 fix If you are running Tioli Proisioning Manager serer for a long period of time, for instance oer an hour, and workflow deployment stops working, check the console.log file in the deploymentengine directory. If you see error MQJMS2002, then you need to install WebSphere MQ 5.3 CSD05 to resole the problem. This patch can be downloaded from Error installing WebSphere Application Serer ersion 5.0 fixpack 2 When installing WebSphere Application Serer ersion 5.0 fixpack 2 on Windows 2000 or Windows 2003, the embedded messaging installation fails and a dialog box is displayed containing the following message: Error installing CSD 04. Examine log file <WAS_HOME>\logs\MQCSDLog.txt. (AMQ4760) The file MQCSDLog.txt contains the following entries: Installing <WMQ HOME>\bin\amqxms0n.dll copying from <CSD HOME>\CSD\CSD00001\amqxms0n.dll to <WMQ HOME>\bin\amqxms0n.dll source ersion: target: source file time Sep at 15:25 ( ) target file time Oct at 08:00 ( ) ***Copy failed 1224 Known limitations, problems and workarounds 5

12 Finished file installation MessageBox: Error installing CSD 04. Examine log file <WAS HOME>\logs\MQCSDLog.txt. (AMQ4760) Ending with RC 1603 (0x ) This problem occurs because the Windows Managment Instrumentation system serice uses the file amqxms0n.dll. If you attempt to install fixpack 2 while this serice is running, the fixpack is unable to update the file, as it is currently in use. Before installing fixpack 2, ensure that the Windows Management Instrumentation system serice is stopped. To stop this serice: 1. Click Settings Control Panel from the Windows Start menu. The Control Panel is displayed. 2. Click Administratie Tools. 3. Click Serices. The Serices applet is displayed. 4. Identify the entry for the Windows Management Instrumentation serice in the list of serices, right click it and then click Stop in the displayed menu. You can now install WebSphere Application Serer ersion 5.0 fixpack 2. Need to remoe ^M characters on Solaris when using XMLExport/XMLImport When you use XMLExport to create a file you want to subsequently use with XMLImport, carriage return characters are included throughout the file. On Solaris systems, these appear as a ^M periodically and can cause problems with an import. To aoid problems, use the UNIX tr command to remoe the ^M characters prior to performing an XMLImport. To do this: 1. Backup the original file to <filename.bak>, where <filename.bak> is the name of the file you want to backup with a.bak extension. For example: cp filename filename.bak 2. Run the command to truncate the characters: tr -d \r > filename Changes to Tioli Proisioning Manager installation The following change applies to the Migrating Tioli Proisioning Manager chapter: One of the notes at the end of the installation procedure recommends a DB2 Uniersal Database locklist alue of If you do not increase the locklist alue from the default alue of 50, you might experience timeout or deadlock errors. To preent these errors, ensure that the locklist alue is set to 2000 or greater for Tioli Proisioning Manager. InstallShield MultiPlatform (ISMP) display may truncate translated text There is a known issue with the translated ersions of the InstallShield MultiPlatform (ISMP) installation wizard. In some languages, text on the translated ersion of the Database Configuration Panel may appear truncated. Specifically, the sentence: Do not perform database configuration steps. (For adanced users only) appears truncated. To iew the entire sentence, resize the window. 6 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

13 Icon iew is obscured When using the Icon View, menu items or popup windows might be obscured. If this occurs, return to the Details View and try again. Cygwin on Japanese, Traditional Chinese and Simplified Chinese Windows In Japanese, Traditional Chinese and Simplified Chinese Windows enironments, it is recommended that you use only English characters for the object names which the user defines, and for the external object names to which the workflow refers. Some double-byte character set (DBCS) languages use encoding schemes with characters that hae the hexadecimal alue 0x5C as the second byte. This is the ASCII hexidecimal code for a backslash (\). Some commands in the Cygwin bash shell interpret double-byte characters without understanding that the bytes should be processed in pairs. When these languages see the 0x5C alue they interpret it is a backslash. This causes an error since it is really just the second byte of a single DBCS character. The bash shell is used by Tioli Proisioning Manager for executing commands from within workflows. For Japanese, Traditional Chinese or Simplified Chinese on Windows systems, if these commands or their results are DBCS characters, and one of those characters happens to contain 0x5C, the command fails. Limiting the characters to English is the easiest way to aoid this problem. (The workflows that ship with Tioli Proisioning Manager are designed to operate in English using English data.) Note: This problem does not occur in Korean language workflows. When using XMLImport or XMLExport, Jaa exceptions can be ignored When errors occur while using XMLImport or XMLExport, there might be some Jaa exceptions displayed along with the Tioli Proisioning Manager error message, in the form COPxxxyyy ID. The exceptions are extraneous and they should be ignored. Use only the alid Tioli Proisioning Manager error message to troubleshoot the problem. The TEC serer needs 3.9 fixpack 1 installed The TEC Serer crashes when it receies eents with locale specific decimal characters [.] in the eent string. Installing the TEC 3.9 Fixpack 1 soles the problem. Data center model export Out of memory error on a data center model export You may experience a JVM out-of-memory error during a data center model export with a large number of entities. The possibility of failure depends on the number of data center model entities and the physical memory installed on the Tioli Proisioning Manager serer. To aoid the problem, do one of the following: Shut down the Tioli Proisioning Manager serer and try again. Increase the physical memory installed on the Tioli Proisioning Manager serer. Increase the irtual memory setting. Known limitations, problems and workarounds 7

14 Credentials Running dcmexport.cmd on a CYGWIN console This problem only applies to Windows platforms. When running the dcmexport.cmd on a CYGWIN console, the optional output file pathname cannot be correctly passed to the dcmexport.cmd script. You must run the dcmexport.cmd on a Windows DOS console. Creating credentials for host and client communication If your enironment contains two serer objects that are located on one machine, you must still create two sets of credentials for both host and client communication. Credentials deleted from a software stack If an entire system image is replaced, all old credentials that are associated with a software stack are deleted from the database after a new image is installed. All new credentials that are configured with the image software stack will be installed automatically after the old ones are deleted. Changing object identifiers Currently, data acquisition engine SNMP driers for UNIX and Windows rely on fixed object identifiers (OIDs) to retriee their information. You can change the object identifiers for a Windows data acquisition engine drier using a DCM import file. For example: <dae-drier deice= serer classname= com.thinkdynamics.kanaha.dataacquisitionengine.snmp.windowsdrier > <property name= snmp.oid alue= /> </dae-drier> Workflows There is no similar capability for UNIX. Deleting workflows You cannot delete a workflow that is referenced by another workflow or Jaa plug-in, and you cannot uninstall an automation package that includes workflows or Jaa plug-ins that are referenced by other workflows or Jaa plug-ins. You must remoe these references first before you can delete the workflow or Jaa plug-in. Alternatiely, you can use forceuninstalldrier, as shown on Uninstalling automation packages on page 9. Creating a workflow with a different locale Tioli Proisioning Manager workflows that are shipped with the product are locale sensitie and are designed to work in only the en_us locale. To use the functionality of a workflow in a locale other than en_us, the workflow must be copied and modified for use in that locale. If the workflow uses an external shell script which has a locale dependency, the script file must be modified accordingly. For example, if the script expects messages from a target application, it should be modified to accept messages for the target locale. To identify referenced script files, please see the deice drier document corresponding to the workflow. The packaged files section of the document includes a list of referenced scripts. The example below describes how to copy and modify the Telnet_Execute_Command workflow to work with the Japanese ja_jp locale. The expect script file telnet_execute.exp is referenced from the Telnet_Execute_Command workflow. In this example, the script file should be modified as well. 8 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

15 Changing the workflow using Web-based interface 1. Open the Telnet_Password_Execute_Command workflow. 2. Change the name of the workflow to Telnet_Password_Execute_Command_ja_JP. 3. Change the en_us argument of the CheckDeiceLocale transition to ja_jp. 4. Compile the workflow. 5. Refresh the tree and expand Deice Dries Serice Access Point, and open Telnet Serice Access Point. 6. Remoe the Telnet_Password_Execute_Command workflow and add the Telnet_Password_Execute_Command_ja_JP workflow. Note: For limitations on non-en_us workflows, see Cygwin on Japanese, Traditional Chinese and Simplified Chinese Windows on page 7. Modifying the script (prerequisite: requires Expect knowledge) 1. Change to the thinkcontrol/bin directory. 2. Add the line: exp_internal 1 to the top of the telnet_execute.exp file. 3. Add parity 0 before the expect {} block and parity 1 after the block. 4. Do not close the file. 5. Run the script and the matching information will be displayed on the screen. expect: does "\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n \r\n\r\n\r\n\r\n\r\n\r\n\raix Version 5\r\n\r(C) Copyrights by IBM and by others 1982, \r\n\rlogin: tioadmin\r\ntioadmin $N%Q%9%o!<%I: " (spawn_id 4) match regular expression "assword: [ \r\t\n\x0c]*$"? no "passwd: $"? no 6. Find the input receied from the telnet serer ($N%Q%9%o!<%I:), copy the text, and paste it into the expect script as shown below. You may need to add backslashes (\) before any special characters such as $. parity 0 expect { -re "\\\$N%Q%9%o!<%I: $" { send "$pass\r" exp_continue } 7. Run and modify the script until you find the matching patterns for all expected patterns. expect: does "tioadmin\r\ntioadmin $N%Q%9%o!<%I: " (spawn_id 4) match regular expression "\$N%Q%9%o!<%I: $"? yes expect: set expect_out(0,string) "$N%Q%9%o!<%I: " expect: set expect_out(spawn_id) "4" expect: set expect_out(buffer) "tioadmin\r\ntioadmin $N%Q%9%o!<%I: " 8. Remoe the exp_internal 1 line when you are finished. Uninstalling automation packages On a Windows platform, the Tioli Proisioning Manager deployment engine must be shut down before an automation package can be uninstalled. If the deployment engine is not shut down, the automation package jar file is locked and the automation package cannot be uninstalled. To uninstall an automation package that is already associated with a deice model: 1. Change the directory to %TIO_HOME%/tools 2. Run tcdrier-manager forceuninstalldrier <automation package name> Known limitations, problems and workarounds 9

16 Workflow ariable alue limits Workflow ariable alues are limited to 4000 bytes. If a scriptlet or Jaa plug-in returns a alue longer than 4000 bytes, DB2 will throw an exception error. Naming 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. New Virtual Serer doesn t get added to correct Resource Pool When trying to allocate a irtual serer on a Tioli Proisioning Manager AIX managed serer and specifying the resource pool, it successfully calls and runs the workflow pseries Create Virtual Serer, but it doesn t put the new irtual serer in the resource Pool specified. Instead, the irtual serer ends up in the no-owner serer list. To rectify this, set that property manually. Package repository attribute required for cluster during XMLImport A cluster import throws an exception because it could not find a property. The error is: COPCOM062E The system cannot find the deployment engine property PackageRepositoryDir. 10:41:40,219 ERROR [main] xmlimport.xmlimport: COPCOM062E The system cannot find the deployment engine property PackageRepositoryDir. com.thinkdynamics.kanaha.datacentermodel.xmlimport.objectnotfoundexception: COPCOM062E The system cannot find the deployment engine property PackageRepositoryDir. at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcluster. getrepositorydir(importcluster.jaa:137) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcluster. importelement(importcluster.jaa:308) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importapplication. importelement(importapplication.jaa:128) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcustomer. importelement(importcustomer.jaa:101) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.xmlimport. importdata(xmlimport.jaa:335) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.xmlimport.main(xmlimport.jaa:114) 10:41:40,594 MSG_ERROR [main] xmlimport.xmlimport: COPCOM062E The system cannot find the deployment engine property PackageRepositoryDir. com.thinkdynamics.kanaha.datacentermodel.xmlimport.objectnotfoundexception: COPCOM062E The system cannot find the deployment engine property PackageRepositoryDir. at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcluster. getrepositorydir(importcluster.jaa:137) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcluster. 10 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

17 importelement(importcluster.jaa:308) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importapplication. importelement(importapplication.jaa:128) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcustomer. importelement(importcustomer.jaa:101) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.xmlimport. importdata(xmlimport.jaa:335) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.xmlimport. main(xmlimport.jaa:114) com.thinkdynamics.kanaha.datacentermodel.xmlimport.objectnotfoundexception: COPCOM062E The system cannot find the deployment engine property PackageRepositoryDir. at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcluster. getrepositorydir(importcluster.jaa:137) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcluster. importelement(importcluster.jaa:308) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importapplication. importelement(importapplication.jaa:128) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.importcustomer. importelement(importcustomer.jaa:101) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.xmlimport. importdata(xmlimport.jaa:335) at com.thinkdynamics.kanaha.datacentermodel.xmlimport.xmlimport. main(xmlimport.jaa:114) It should not be mandatory for this property to be present, but for now you hae to enter a alue for the PackageRepositoryDir for the import to succeed.. -unsafe command line parameter for XMLImport If XMLImport fails with SQL exception SQL0964C, use the unsafe command line parameter. This error typically occurs when you are importing huge data center model (DCM) files. It is not possible to use this parameter within the reinit script. A workaround is to import an empty file during reinit and then use XMLImport with the unsafe parameter to import your DCM file. Note: Using the unsafe parameter will damage the database if your DCM file contains any errors. If this happens, the database must be recreated using the reinit script. If you are unsure about the alidity of your DCM file, export your database first using the XMLExport utility. This way, should the database become corrupt, you can recoer quickly. Transaction log full error when running post-install.cmd If you are getting this error, you need to increase the allotted size of the database parameter LOGFILSIZ to The default size on UNIX is 1000, and on Windows the default size is 250. To change the database log file size to 8000, run the following command: db2 update database configuration for db_name using LOGFILSIZ 8000 LOGPRIMARY 6 where db_name is the name of your database. The large log file size is needed to accommodate all possible transactions, which in some cases can be considerable. The LOGFILSIZ parameter is used by the primary log and the secondary log. The number of primary log files set with the LOGPRIMARY parameter works in combination with the LOGFILSIZ parameter to proide enough space for all possibilities. Known limitations, problems and workarounds 11

18 Automount needs to be disabled on Solaris Tioli Proisioning Manager fails to create user account on Solaris due to Automount daemon keeping /home as the mount point. The user needs to: 1. Login as root. 2. Edit the file /etc/auto_master. For example, i /etc/auto_master. 3. Comment out the entry for /home. To do this, put an octothorpe (#) in front of the auto_home line: Change this: /home auto_home to this: #/home auto_home 4. Sae the edited auto_master file. 5. Run Automount to read in the changes. Note: If this change is only required temporarily, remember to uncomment the /home line and rerun Automount to apply the change. Install the new Warehouse Enablement Pack (WEP) from the IBM Tioli Software Support site An updated Warehouse Enablement Pack (WEP) is aailable from the IBM Tioli Software Support site at Before following the instructions to install Tioli Data Warehouse and the Warehouse Enablement Pack, download the latest ersion of the Warehouse Enablement Pack from the Support Web site. The update contains key fixes to enable Oracle support and schema changes to support rollup and pruning. To get the update: 1. Go to 2. Search on Tioli Proisioning Manager in Downloads only. 3. When the search results are displayed, change the sort order to Date-newest first so the most recently aailable downloads are listed first. 4. Download and install the update. 12 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

19 Documentation additions Data center fragment This section contains help topics which, due to time constraints, are not aailable in the online help. A data center fragment (DCF) is a subset of the data center model (DCM). The DCF is a collection of DCM objects that are required to support the application deployment template (ADT). You can edit the deployment plan to remoe any elements chosen by using the DCF after creating the deployment plan. Data center fragments include: switches A DCF can only contain one switch fabric, so all switches in a data center fragment must belong to the same switch fabric. routers pools serers These appear as detached resources in the DCF, een though routers are a subset of switches in the data center model (DCM). Pools that are not in the DCF can still be used for the clusters in a deployment plan, but you must manually add them when you create or edit the deployment plan. Any serer in the DCM can be added to the DCF. Some are used to create new pools if there are no pools aailable in the DCF. Only no-owner (not already in a cluster or pool) serers are used to assemble new pools. If there are none aailable to be selected, the user must manually select which serers to use. load balancers At deployment time, if there are any Logical Deployment Templates containing clusters using load balancers, the system chooses which load balancers to use from the list defined in the Data Centre Fragment. Howeer, the user can oerride this behaior and use any other load balancers defined in the entire Data Centre Model by editing the Deployment Plan. Configuring a data center fragment As soon as a DCF has been created from the indiidual deices, you can configure it as a whole. To configure a data center fragment: 1. Click Data center assets and resources Inentory Data Center Fragments. The Data Center Fragments Inentory page is displayed. 2. Click the name of the DCF you want to configure. The Data Center Fragment General page is displayed. Note: To rename the DCF, click Edit Properties, make your changes and then click Sae when you are done. You can also fine-tune your DCF by Copyright IBM Corp. 2003,

20 Viewing the software registry remoing preiously added deices. Identify the deice you want to remoe and then click More Remoe. The software registry is a repository of software modules used when creating a deployment plan. To iew the software registry: Click Data center assets and resources Inentory Software Registry. The Software Registry page is displayed. Registering software The registry is configured by adding capabilities, requirements and supported requirement types to software products and stacks already existing in the data center model (DCM). To register software: 1. Click Data center assets and resources Inentory Software Registry. The Software Registry page is displayed. 2. Click Edit Register. The Register Software dialog is displayed. 3. Click the type of software you would like to register in the Software Type list. Depending on your selection and what software products currently exist in the DCM, the Software list is populated with options. 4. Click the software to register in the Software list. 5. Click Sae. The selected software is displayed in the Software Registry list. Deregistering software To deregister software preiously registered: 1. Click Data center assets and resources Inentory Software Registry. The Software Registry page is displayed. 2. Identify the software in the list you would like to deregister. 3. Click More Deregister. 4. Click OK when prompted. The page refreshes and the selected software is remoed from the list. Editing the properties of a software module If a software module has capabilities (the ability to host or satisfy the requirements of other software modules), it is referred to as an infrastructure software module. To edit the properties of a software module: 1. Click Data center assets and resources Inentory Software Registry. The Software Registry page is displayed. 2. Identify the module in the list you want to edit. 3. Click More Edit. The Software Module page is displayed, showing all existing requirements and capabilities. 14 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

21 To add requirements 1. Click Edit Add Requirement. The New Requirement dialog box is displayed. 2. Click the name of the new requirement in the Name list. 3. Click the type of the new requirement in the Type list. 4. Depending on the item selected in the Name list, there could also be Aailable Values in this dialog. If there are, select all the check boxes which apply to the requirement you are adding. 5. If the requirement being added is of hosting type, select the Hosting check box. 6. Click Sae. The new requirement is added to the existing list of requirements for this software module. Note: If more than one Aailable Values check box was selected, the list under Requirement Values has all the selected alues and you can choose which one should be current by clicking it in the Requirement Value list. To edit a requirement 1. Identify the requirement you want to delete in the Requirement Name list. 2. Click More Edit. The Edit Requirement dialog box is displayed. 3. Make changes as required. 4. Click Sae. The requirement is updated in the existing list of requirements for this software module. Note: If more than one Aailable Values check box was selected, the list under Requirement Values has all the selected alues and you can choose which one should be current by clicking it in the Requirement Value list. To delete a requirement 1. Identify the requirement you want to delete in the Requirement Name list. 2. Click More Delete. 3. Click OK when prompted. The requirement is updated in the existing list of requirements for this software module. To add a supported requirement 1. Click Edit Add Supported Requirement. The Supported Requirement Type dialog box is displayed. 2. Click the supported type in the Aailable Requirement Types list. 3. Click Sae. The new Supported Requirement Type Name is added to the existing list of supported requirement type names for this software module. To delete a supported requirement 1. Identify the supported requirement you want to delete in the Supported Requirement Type Name list. 2. Click More Delete. 3. Click OK when prompted. To add a capability 1. Click Edit Add Capability. The New Capability dialog box is displayed. 2. Click the name of the capability you want to add in the Name list. 3. If the capability has a alue, enter it in the Value field. Documentation additions 15

22 4. Click Sae. The new Capability is added to the existing list of capabilities for this software module. To edit a capability 1. Identify the capability you want to edit in the Capability Name list. 2. Click More Edit. The Edit Capability dialog box is displayed. 3. Click the name of the capability you want to add in the Name list. 4. Edit the alue as required. 5. Click Sae. Creating a deployment plan A deployment plan is a list of resources, configurations and implementations required to realize the deployment of a business application. A business application, unlike a standalone software application, can span across multiple tiers, serers or systems. The actual implementation is achieed through the use of workflows. You must follow seen steps to create a deployment plan. Each step must be completed before the next can be started. The seen steps are: Step 1. Step 2. Step 3. Step 4. Step 5. Step 6. Step 7. Select a logical application structure. For each module in the logical application structure, select a software stack which satisfies the hosting requirements of the application. Select an application deployment template. Specify the deployment parameters. Select a data center fragment. Edit the deployment plan. Finalize the deployment plan. To create a deployment plan: 1. If the application for the deployment plan doesn t exist, create it. 2. Click Customer applications and then click a customer_name. Then click an application_name. The Application Oeriew Clusters page is displayed. Note: If there are currently no applications in the data center model, the actual first step will be creating one. 3. Click the Deployment Topology tab. The Application Deployment Topology page is displayed. 4. Click Deployment Create New Deployment Plan and click OK when prompted. Selecting a logical application structure Before performing this action, you need to complete Creating a deployment plan. A logical application structure (LAS) consists of a collection of business modules. The LAS is selected from a list of LAS templates in the database, or a new LAS template can be uploaded to the database. The system identifies these by their name. 16 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

23 Note: Make sure the names defined in the LAS, ADT, LDT and NTT templates are unique. To select a logical application structure: 1. Click a name in the logical application structure list to select a template already in the database. If the template you want to select is not yet in the database, click Upload Template File, browse for your template on your local system and click Update to add the template to the database, and then click the name in the logical application structure list to select the just added template. 2. Click Next. Selecting software stacks Before performing this action, you need to complete Selecting a logical application structure on page 16. Tioli Proisioning Manager builds the software stack for each module in the logical application structure (LAS) based on the information in the software registry. If more than one possible solution exists, all solutions are added to the Hosting options list so the user can select the most appropriate one. This happens for each module in the LAS. To select software stacks: 1. For each module in the list, click a software stack name in the Hosting options list. Note: The number of modules which appear in the list is determined by the number of modules in the LAS template selected in the preious step. 2. Click Next. Note: If you want to make any changes to the preious step, click Back. Proceed to Selecting an application deployment template. Selecting an application deployment template Before performing this action, you need to complete Selecting software stacks. The application deployment template (ADT) is a combination of the logical deployment template (LDT) and the network topology template (NTT). If the ADT doesn t already exist in your database, you can upload one, or create one from an existing LDT in combination with an existing NTT. To select an application deployment template: Click a name in the application deployment template list to select a template already in the database. If the template you want to select is not yet in the database, click Upload Template File, browse for your template on your local system and click Update to add the template to the database. Then click the the template name in the application deployment template list. Note: If you want to make any changes to the preious step, click Back. Documentation additions 17

24 Specifying additional deployment parameters Before performing this action, you need to complete Selecting an application deployment template on page 17. Some clusters can be parameterized during deployment. This means that their minimum and maximum alue is not hardcoded. For each module, you can enter the minimum and maximum size of the cluster at this point in the wizard. To specify additional deployment parameters for each module in the list: 1. Type the initial, or minimum, alue of the module you want in the min-size field. 2. Repeat for each listed module. 3. Type the maximum alue of the module you want in the max-size field. 4. Click Next. Note: If you want to make any changes to the preious step, click Back. Selecting a data center fragment Before performing this action, you need to complete Specifying additional deployment parameters. Selecting a data center fragment (DCF) tells the deployment plan what resources it has access to. If no DCF is selected, the entire data center model (DCM) is assumed. Note: Be aware that selecting a DCF does not resere the objects in the DCF for the deployment plan, it simply restricts the selection possibilities. To select a data center fragment: 1. Click a name in the data center fragment list to select a DCF already in the database. 2. Click Next to generate the deployment plan. Note: If you want to make any changes to the preious step, click Back. Reiewing the deployment plan Before performing this action, you need to complete Selecting a data center fragment. Reiewing the deployment plan produced by the wizard, allows you to fine-tune the plan before finalizing it. You can rename elements either by clicking on their name or by clicking properties, if the element has a properties icon menu associated with it. Note: In the plan, you will see seeral elements called <serer template>. Based on your input in the preious wizard steps, the clusters and serers created in your plan need basic, structural information. For instance, you will need to know how many NICs should be configured for this serer and what all their lan/subnet/port details are. This information can be changed later, but it needs to be created at this stage. 18 Tioli Intelligent ThinkDynamic Orchestrator Version Release Notes

25 To reiew the deployment plan: 1. Reiew and rename elements, as desired. 2. Click Next to finalize the deployment plan. Note: If you want to make any changes to the preious step, click Back. Finalizing the deployment plan Documentation updates Before performing this action, you need to complete Reiewing the deployment plan on page 18. When you finalize the deployment plan, you are saing it. If you return to this application later, the plan you generated will still be there. Note: Finalizing or saing a deployment plan does not resere the objects in the plan, it simply proides a configuration snapshot at the time the plan was generated. You can also make the same changes here that you can during the reiew step. To finalize the deployment plan: 1. Select the Realize the Plan Immediately check box if you want to implement this plan right away. 2. Click Finish to finalize or sae the deployment plan. Note: If you want to make any changes to the preious step, click Back. To deploy a saed plan at a later date, without changes, simply come back to this application and on the Deployment Topology page, click Deployment Deploy. The following sections contain errata which complements or corrects existing help information. Installation Guide correction In the Installation Guide section titled Post-Installation steps there are instructions to edit the file datacenter.xml after you hae installed Tioli Proisioning Manager. This file is found either in %TIO_HOME%\xml, for Windows enironments, or in $TIO_HOME/xml, for UNIX enironments. You should not perform these steps at that point of the installation process, as required information has not yet been defined. The datacentermodel.xml file requires that you declare some ariables for your data center before importing it, such as lan, subnet or software product. You must first enter the VLAN, subnet and software product for your Tioli Proisioning Manager system before you can import the xml file which references (or uses) it. To enter the alues in the application, after completing the installation: 1. Logon to Tioli Proisioning Manager. For more information, refer to the Installation Guide. 2. Enter the information required for the subnet, VLAN and software product in your data center. Information on completing this task can be found in the online help. 3. Logoff from Tioli Proisioning Manager. Documentation additions 19