1.Front coverIBM Tivoli ProvisioningManager V7.1.1: Deploymentand IBM Service ManagementIntegration GuideLearn how to implement Tivoli ProvisioningManager V7.1.1 in your environmentExperiment with IBM ServiceManagement integration scenariosLearn TPM troubleshooting andhow to migrate from V5.1.2troubleshootingGhufran Shah Jenna LauAlfredo OlivieriLuca Balestrazzi Anna PintusMichael Edler Annarosa Mallozzivon der Planitz Claudio SantucciRaffaela BoveDanilo Allocca Valentina MariottiniFabrizio Salustri Vasfi GucerGabriella Santoro Vittorio Calafiore GianFilippo Maniscalco Wing L Leungibm.com/redbooks

2. International Technical Support OrganizationIBM Tivoli Provisioning Manager V7.1.1:Deployment and IBM Service ManagementIntegration GuideDecember 2009 SG24-7773-00 3. Note: Before using this information and the product it supports, read the information in Notices on page xiii.First Edition (December 2009)This edition applies to IBM Tivoli Provisioning Manager Version 7, Release 1, Modification 1. Copyright International Business Machines Corporation 2009. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp. 4. Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv The team who wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiPart 1. Concepts and architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Tivoli Provisioning Manager V7.1.1 overview . . . . . . . . . . . . . . 3 1.1 Introduction to Tivoli Provisioning Manager . . . . . . . . . . . . . . . . . . . . . . . . 41.1.1 Tivoli Provisioning Manager concepts. . . . . . . . . . . . . . . . . . . . . . . . . 41.1.2 The data center model (DCM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.2 What is new in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2.1 Custom attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.2 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.3 Compliance with Federal Information Processing Standard 140-2 . . 121.2.4 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.5 Discovery Library Adapter (DLA) . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.6 High availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.8 IPv6 addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.9 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.10 Operating systems management . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.11 Patch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.12 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.13 Scalable distribution infrastructure (SDI). . . . . . . . . . . . . . . . . . . . . 151.2.14 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.15 Start Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.16 Target computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.17 Task management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.18 Virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.3 Tivoli Provisioning Manager Version 7.X client value . . . . . . . . . . . . . . . . 17 Chapter 2. Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.1 Tivoli process automation engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.1 Common User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Copyright IBM Corp. 2009. All rights reserved.iii 5. 2.1.2 Common Configuration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.1.3 Common Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.1.4 Process Workflow Runtime and Services . . . . . . . . . . . . . . . . . . . . . 232.1.5An integrated Service Management portfolio on top of the Tivoli processautomation engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.2 Tivoli Provisioning Manager capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.2.1 How Tivoli Provisioning Manager extends the Tivoli process automationengine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.2.2 Tivoli Provisioning Manager V7.1.1 component architecture . . . . . . 27 2.2.3 Tivoli Provisioning Manager V7.1.1 configuration for high availability anddata integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.2.4 Tivoli Provisioning Manager V7.1.1 scalability . . . . . . . . . . . . . . . . . 34Part 2. Planning for deployment and implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Chapter 3. Installation planning and deployment scenarios. . . . . . . . . . . 373.1 Installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.2 Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.3 Installation topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.4 Single node installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.5 Multi-node installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.6 Reusing existing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.7 Considerations for the firewall environment . . . . . . . . . . . . . . . . . . . . . . . 483.8 Gateway manager and gateway service . . . . . . . . . . . . . . . . . . . . . . . . . . 55Chapter 4. Installation steps for integration . . . . . . . . . . . . . . . . . . . . . . . . 574.1 Integration assumptions and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2 Steps to install and set up the environment to run integration scenarios . 594.3 Tivoli Provisioning Manager V7.1.1 installation . . . . . . . . . . . . . . . . . . . . . 68 4.3.1 Pre-install Cygwin on the local system . . . . . . . . . . . . . . . . . . . . . . . 68 4.3.2 Base Services install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4.3.3 Tivoli Provisioning Manager core components . . . . . . . . . . . . . . . . . 75 4.3.4 Tivoli Provisioning Manager Web components . . . . . . . . . . . . . . . . . 894.4 Other samples of integrated environments . . . . . . . . . . . . . . . . . . . . . . . . 92 4.4.1 Installing CCMDB on top of Tivoli Provisioning Manager V7.1.1 . . . 92 4.4.2 Installing Tivoli Service Request Manager on top of Tivoli ProvisioningManager 7.1.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Chapter 5. Customizing Tivoli Provisioning Manager V7.1.1 after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015.1 Customization after Tivoli Provisioning Manager V7.1.1 installation . . . . 102 5.1.1 Security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.1.2 Creating a new user or security group and import these into Tivoli Provisioning Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103ivIBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 6. 5.2 Implementing the scalable distribution infrastructure . . . . . . . . . . . . . . . 1075.2.1 Dynamic content delivery service . . . . . . . . . . . . . . . . . . . . . . . . . . 1095.2.2 Device management service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 5.3 Tivoli Provisioning Manager: Software deployment and management . . 121 5.4 Launching and configuring the Software Package Editor . . . . . . . . . . . . 1225.4.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225.4.2 Software Catalog, Software Products and Software Definitions . . . 126 5.5 Creating and saving a software package block by using SPE . . . . . . . . 1275.5.1 Software product capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305.5.2 Software product requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 5.6 Distributing software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Part 3. The new GUI and IBM Service Management integration scenarios . . . . . . . . . . . 135 Chapter 6. Tivoli process automation engine based user interface . . . . 137 6.1 Start Center configuration for LDAP users . . . . . . . . . . . . . . . . . . . . . . . 138 6.2 Start Center templates and instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 6.3 Overview of main functionality in the Start Center . . . . . . . . . . . . . . . . . 139 6.4 Configuring the Tivoli process automation engine Web-based interface forusers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1436.4.1 Creating new users in LDAP and assign them to groups . . . . . . . . 1446.4.2 Synchronizing Tivoli process automation engine users configuration with LDAP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456.4.3 Creating a new Start Center template . . . . . . . . . . . . . . . . . . . . . . . 1476.4.4 Assigning permissions to a security group . . . . . . . . . . . . . . . . . . . 1496.4.5 Creating a Key Performance Indicator . . . . . . . . . . . . . . . . . . . . . . 1536.4.6 Modifying a Key Performance Indicator cron task. . . . . . . . . . . . . . 1546.4.7 Choosing which portlets to display in your Start Center instance . . 1556.4.8 Modifying the content of a portlet within your Start Center instance 1556.4.9 Modifying an existing Start Center template . . . . . . . . . . . . . . . . . . 1566.4.10 Updating your Start Center instance according to the template . . 1576.4.11 Choosing how to display a multi-tabbed Start Center . . . . . . . . . . 158 6.5 Tivoli Provisioning Manager Start Center templates . . . . . . . . . . . . . . . . 1596.5.1 Provisioning Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596.5.2 Deployment Specialist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616.5.3 Compliance Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1626.5.4 Provisioning Configuration Librarian . . . . . . . . . . . . . . . . . . . . . . . . 1646.5.5 Automation Package Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 6.6 Benefits of the new GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 6.7 Overview of the GUI differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676.7.1 Welcome to Tivoli Provisioning Manager versus Start Center . . . . 1686.7.2 Tracking Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706.7.3 Managing Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Contents v 7. 6.7.4 Managing Depots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1746.7.5 Computer Details: Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766.7.6 Workflow Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Chapter 7. Integrated Service Management with IBM Service Management Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1817.1 IBM Service Management solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1827.2 Tivoli Provisioning Manager in the context of Service Management . . . . 1837.3 Customer scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 7.3.1 Service provisioning scenario using TADDM, CCMDB, Tivoli ServiceRequest Manager, and Tivoli Provisioning Manager . . . . . . . . . . . 186 7.3.2 Outage remediation scenario using Tivoli Provisioning Manager andTivoli Service Request Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 7.3.3 Tivoli Provisioning Manager TADDM Discovery and synchronizationprocess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 7.3.4 Software installation, compliance, and remediation scenario . . . . . 192 7.3.5 Change scenario using Tivoli Provisioning Manager and ChangeManagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Chapter 8. IBM Service Management integration scenarios: TADDMDiscovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1958.1 Introduction to TADDM integration with Tivoli Provisioning Manager . . . 196 8.1.1 Lab environment: IBM Service Management integration scenarios 196 8.1.2 Installed components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 8.1.3 Tivoli Provisioning Manager and TADDM life cycle . . . . . . . . . . . . 199 8.1.4 Supported applications in Tivoli Provisioning Manager. . . . . . . . . . 2018.2 Discovering applications in Tivoli Provisioning Manager. . . . . . . . . . . . . 203 8.2.1 Discovering applications in TADDM . . . . . . . . . . . . . . . . . . . . . . . . 203 8.2.2 Configuring Tivoli Provisioning Manager to use TADDM . . . . . . . . 2048.3 Working with discovered applications in Tivoli Provisioning Manager . . 209 8.3.1 Viewing the application configuration data in Tivoli ProvisioningManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 8.3.2 Configuring communication to the discovered computers andapplications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 8.3.3 Controlling software applications from Tivoli Provisioning Manager 215Chapter 9. IBM Service Management integration scenarios: Compliance and remediation with TADDM . . . . . . . . . . . . . . . . . . . . . . . . . 2179.1 Overview of Compliance Management . . . . . . . . . . . . . . . . . . . . . . . . . . 2189.2 Compliance and remediation features. . . . . . . . . . . . . . . . . . . . . . . . . . . 218 9.2.1 Compliance checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 9.2.2 Built-in auto-remediation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2209.3 The compliance and remediation process. . . . . . . . . . . . . . . . . . . . . . . . 2239.4 Scenario: Compliance and remediation with TADDM . . . . . . . . . . . . . . . 225vi IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 8. 9.4.1Scenario introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2269.4.2Setting up users and permissions . . . . . . . . . . . . . . . . . . . . . . . . . . 2279.4.3Scenario implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2319.4.4Scenario conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Chapter 10. IBM Service Management integration scenarios: IncidentManagement integration with Tivoli Service Request Managerand ITIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27110.1 Information Technology Infrastructure Library (ITIL) and IncidentManagement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 10.1.1 Service considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 10.1.2 Incident Management process . . . . . . . . . . . . . . . . . . . . . . . . . . . 27310.2 Tivoli Service Request Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 10.2.1 Overview of Tivoli Service Request Manager . . . . . . . . . . . . . . . . 274 10.2.2 Service Desk functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27410.3 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27610.4 Prerequisites steps for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 10.4.1 Posts-installation tasks for Tivoli Change and Configuration Management Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 10.4.2 Import of Configuration Items from Tivoli Application Dependency Discovery Manager to CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 10.4.3 Import of Computers from Tivoli Application Dependency Discovery Manager to Tivoli Provisioning Manager Data Center Model . . . . . 29710.5 Incident Management integration scenario . . . . . . . . . . . . . . . . . . . . . . 300 10.5.1 Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 10.5.2 Creation and configuration of users needed to run the Incident Management integration scenario . . . . . . . . . . . . . . . . . . . . . . . . . 301 10.5.3 Creation of components needed for the execution of the Incident Management integration scenario . . . . . . . . . . . . . . . . . . . . . . . . . 303 10.5.4 Implementation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Chapter 11. IBM Service Management integration scenarios: Problem andChange Management integration with Tivoli Service RequestManager and CCMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32511.1 Problem and Change Management according to ITIL. . . . . . . . . . . . . . 326 11.1.1 IBM Tivoli Change and Configuration Management Database (CCMDB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 11.1.2 Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 11.1.3 Problem Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32811.2 Scenario process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 11.2.1 Users of the scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 11.2.2 Users and groups as defined in WebSphere . . . . . . . . . . . . . . . . 33011.3 The scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 11.3.1 From Service Request to Incident . . . . . . . . . . . . . . . . . . . . . . . . . 333Contentsvii 9. 11.3.2 From Incident record to Problem and Change record . . . . . . . . . . 336 11.3.3 From Change to software patch deployment . . . . . . . . . . . . . . . . 341 Chapter 12. Tivoli Provisioning Manager integration methods with non-IBM solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 12.1 Introduction to various integration methods . . . . . . . . . . . . . . . . . . . . . 349 12.2 Functional integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35012.2.1 Advantages and disadvantages of functional integration . . . . . . . 35112.2.2 Tivoli Provisioning Manager workflows . . . . . . . . . . . . . . . . . . . . . 35212.2.3 Tivoli Provisioning Manager Web Services, SOAP Services, and SOAPCli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35912.2.4 Functional integration summary . . . . . . . . . . . . . . . . . . . . . . . . . . 361 12.3 Data integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36212.3.1 Advantages and disadvantages of data integration . . . . . . . . . . . 36212.3.2 Tivoli Provisioning Manager data importing/exporting capabilities 36312.3.3 IBM Tivoli Integration Composer (ITIC). . . . . . . . . . . . . . . . . . . . . 36512.3.4 Data integration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 12.4 Data federation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36612.4.1 Advantages and disadvantages of data federation . . . . . . . . . . . . 36712.4.2 IBM InfoSphere Federation Server . . . . . . . . . . . . . . . . . . . . . . . . 367Part 4. Patch Management, Operating System Deployment, and IBM Tivoli Monitoringagent for Tivoli Provisioning Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Chapter 13. Patch Management scenarios . . . . . . . . . . . . . . . . . . . . . . . . 371 13.1 Changes and improvements to Windows and UNIX Patch Management capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 13.2 Patch Management in small Windows environments . . . . . . . . . . . . . . 37213.2.1 Predefined roles for Patch Management. . . . . . . . . . . . . . . . . . . . 37413.2.2 Requirements for Patch Management . . . . . . . . . . . . . . . . . . . . . 37413.2.3 Web Replay scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37513.2.4 Patch Management in small Windows environments . . . . . . . . . . 37613.2.5 Patch Management in large Windows environments . . . . . . . . . . 380 13.3 Patch Management in AIX environments . . . . . . . . . . . . . . . . . . . . . . . 39613.3.1 Acquiring patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39913.3.2 Setting up compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40013.3.3 Scanning for missing patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40113.3.4 Approving compliance recommendations . . . . . . . . . . . . . . . . . . . 40113.3.5 Distributing patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40213.3.6 Installing patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40213.3.7 Verifying compliance results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40313.3.8 Uninstalling patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 13.4 Patch Management in SUSE Linux Enterprise environments . . . . . . . . 40413.4.1 Patch Management solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404viiiIBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 10. 13.4.2 SUSE Linux update site model . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Chapter 14. Operating system provisioning . . . . . . . . . . . . . . . . . . . . . . . 409 14.1 Tivoli Provisioning Manager for OS Deployment architecture . . . . . . . . 41114.1.1 Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41114.1.2 DHCP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41314.1.3 Deployment basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 14.2 Parent-child boot servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 14.3 Software modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42614.3.1 Windows platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42614.3.2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45114.3.3 AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45114.3.4 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45114.3.5 Tivoli common agent software modules . . . . . . . . . . . . . . . . . . . . 45214.3.6 Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 14.4 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 14.5 Unattended setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46914.5.1 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46914.5.2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48314.5.3 AIX, Solaris, and Linux on PPC . . . . . . . . . . . . . . . . . . . . . . . . . . 487 14.6 Cloning computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48914.6.1 Golden master image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49014.6.2 Point-in-time snapshot image . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 Chapter 15. The IBM Tivoli Monitoring Agent for Tivoli ProvisioningManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 15.1 IBM Tivoli monitoring agent software . . . . . . . . . . . . . . . . . . . . . . . . . . 49815.1.1 Features and functions of the monitoring agent . . . . . . . . . . . . . . 49815.1.2 Configuring the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 15.2 Installing support files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 15.3 Predefined workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 15.4 Sample workspaces data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503Part 5. Troubleshooting and migration from Tivoli Provisioning Manager V5.1.2 . . . . . 509 Chapter 16. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 16.1 Troubleshooting basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51316.1.1 What are the symptoms of the problem? . . . . . . . . . . . . . . . . . . . 51316.1.2 Where does the problem occur? . . . . . . . . . . . . . . . . . . . . . . . . . . 51316.1.3 When does the problem occur? . . . . . . . . . . . . . . . . . . . . . . . . . . 51416.1.4 Under which conditions does the problem occur? . . . . . . . . . . . . 51416.1.5 Can the problem be reproduced? . . . . . . . . . . . . . . . . . . . . . . . . . 515 16.2 Installation troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51516.2.1 Troubleshooting the provisioning server . . . . . . . . . . . . . . . . . . . . 515 Contents ix 11. 16.2.2 Tivoli Provisioning Manager core components . . . . . . . . . . . . . . . 51716.2.3 Tivoli Provisioning Manager Web components . . . . . . . . . . . . . . . 51716.2.4 Tivoli Provisioning Manager installation logs . . . . . . . . . . . . . . . . 51816.2.5 Troubleshooting the infrastructure components installation . . . . . 519 16.3 Runtime troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52016.3.1 Configuring logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52016.3.2 Setting logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 16.4 Collecting logs from Tivoli Provisioning Manager server. . . . . . . . . . . . 523 16.5 Displaying and exporting provisioning workflow logs . . . . . . . . . . . . . . 524 16.6 Verifying if the Tivoli Common Agent is working . . . . . . . . . . . . . . . . . . 526 16.7 Setting up the Tivoli common agent log levels . . . . . . . . . . . . . . . . . . . 527 16.8 Collecting a log file from the Tivoli common agent . . . . . . . . . . . . . . . . 528 16.9 Verifying if the depot has been successfully installed . . . . . . . . . . . . . . 529 16.10 Collecting a log file from the depot server . . . . . . . . . . . . . . . . . . . . . . 531 16.11 Troubleshooting the software distribution . . . . . . . . . . . . . . . . . . . . . . 53116.11.1 Debugging the software distribution in a scalable distributioninfrastructure (SDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53116.11.2 Debugging the software distribution in a deployment engineinfrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 16.12 Troubleshooting operating system provisioning . . . . . . . . . . . . . . . . . 540 Chapter 17. Migrating from Tivoli Provisioning Manager Version 5.1.1.2 to Tivoli Provisioning Manager Version 7.1.1 . . . . . . . . . . . . . . . 541 17.1 Migration objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54317.1.1 Gradual phased migration process approach . . . . . . . . . . . . . . . . 54317.1.2 Artifacts migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544 17.2 Environment used for the migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 54517.2.1 Tivoli Provisioning Manager Version 5.1.1.2 system . . . . . . . . . . 54617.2.2 Tivoli Provisioning Manager Version 7.1.1 system . . . . . . . . . . . . 547 17.3 Migration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 17.4 Tivoli Provisioning Manager Version 5.1.1.2 pre-migration tasks . . . . . 55017.4.1 Upgrading the provisioning server to version 5.1.1.2 . . . . . . . . . . 55117.4.2 Upgrading the common agent to version 1.3.2.29 . . . . . . . . . . . . 55217.4.3 Copying the files for the scalable distribution infrastructure (SDI)installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55217.4.4 Copying the backup tools to the 5.1.1.2 provisioning server. . . . . 55317.4.5 Backing up the LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55417.4.6 Pre-migration tasks for Tivoli Directory Server . . . . . . . . . . . . . . . 55417.4.7 Prerequisites for migrating automation packages . . . . . . . . . . . . . 55517.4.8 Exporting the 5.1.1.2 report query. . . . . . . . . . . . . . . . . . . . . . . . . 55617.4.9 Migrating file repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55617.4.10 Migrating images created using Tivoli Provisioning for OSDeployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557x IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 12. 17.4.11 Removing nicknames and views . . . . . . . . . . . . . . . . . . . . . . . . . 55717.5 Tivoli Provisioning Manager Version 7.1.1 pre-installation tasks . . . . . 55817.6 Tivoli Provisioning Manager Version 7.1.1 installation . . . . . . . . . . . . . 559 17.6.1 Starting the launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 17.6.2 Installing the middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 17.6.3 Creating the database and database server user . . . . . . . . . . . . . 565 17.6.4 Core components installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56717.7 Completing the property file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57717.8 Migrating Tivoli Provisioning Manager . . . . . . . . . . . . . . . . . . . . . . . . . 591 17.8.1 Migration tasks for the Tivoli Provisioning Manager Version 5.1.1.2 system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591 17.8.2 Migration tasks for the Tivoli Provisioning Manager Version 7.1.1 system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 17.8.3 Changing the WebSphere Application Server casprofile profile password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616 17.8.4 Installing the base services and the Web components . . . . . . . . . 616 17.8.5 Assigning the hostnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 17.8.6 Continuing the migration on the 7.1.1 provisioning server . . . . . . 63817.9 Post-migration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655 17.9.1 Backing up the administrative workstation . . . . . . . . . . . . . . . . . . 656 17.9.2 Configuring SSL with IBM HTTP Server . . . . . . . . . . . . . . . . . . . . 657Appendix A. Miscellaneous upgrade scenarios . . . . . . . . . . . . . . . . . . . . 671Upgrade to Tivoli Provisioning Manager V7.1.1 and Tivoli CCMDB V7.1.1.5 672Upgrade to Tivoli Provisioning Manager V7.1.1 and Tivoli Service RequestManager V7.1.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674Integration between Tivoli Provisioning Manager V7.1.1 and IBM Tivoli AssetManagement for IT V7.1.0.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678Installing Tivoli Asset Management for IT on top of Tivoli Provisioning Manager V7.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678Installing Tivoli Provisioning Manager on top of Tivoli Asset Management for IT V7.1.0.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680Appendix B. Tivoli Provisioning Manager Version 7.1.1 pre-installationchecks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685File systems creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686Required packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688openssl and openssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690Operating System checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692Environment checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695Prepare the installation media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697Appendix C. tpm5112backup.sh script . . . . . . . . . . . . . . . . . . . . . . . . . . . 699tpm5112backup.sh script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700Contentsxi 13. Appendix D. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 System requirements for downloading the Web material . . . . . . . . . . . . . 712 How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721xii IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 14. NoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the usersresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to:IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof express or implied warranties in certain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM maymake improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirmthe accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe capabilities of non-IBM products should be addressed to the suppliers of those products.This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Copyright IBM Corp. 2009. All rights reserved. xiii 15. TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. These and other IBM trademarkedterms are marked on their first occurrence in this information with the appropriate symbol ( or ),indicating US registered or common law trademarks owned by IBM at the time this information waspublished. Such trademarks may also be registered or common law trademarks in other countries. A currentlist of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtmlThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:AIX 5L Maximo ServerGuideAIXMVSSystem pAS/400 NetcoolSystem zDB2 Universal Database NetfinitySystemViewDB2NetViewTivoli Enterprise ConsoleEnterprise Asset ManagementOS/2 TivoliIBMPowerPCTotalStorageInfoSphere Redbooks WebSphereiSeriesRedbooks (logo) Library Reader RomaThe following terms are trademarks of other companies:AMD, the AMD Arrow logo, and combinations thereof, are trademarks of Advanced Micro Devices, Inc.ITIL is a registered trademark, and a registered community trademark of the Office of GovernmentCommerce, and is registered in the U.S. Patent and Trademark Office.Snapshot, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. andother countries.Novell, SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United Statesand other countries.Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporationand/or its affiliates.SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries.Java, Java runtime environment, JDBC, JRE, JumpStart, SmartStart, Solaris, Sun, Sun Java, Ultra, and allJava-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, orboth.Active Directory, BitLocker, Internet Explorer, Microsoft, Visual Basic, Windows Server, Windows Vista,Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, othercountries, or both.Intel, Itanium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks ofIntel Corporation or its subsidiaries in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Linux is a trademark of Linus Torvalds in the United States, other countries, or both.Other company, product, or service names may be trademarks or service marks of others.xiv IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 16. Preface This IBM Redbooks publication is a complete reference for the recently available Tivoli Provisioning Manager V7.1.1 product. This document provides information valuable to those who want to plan for, customize, and use the IBM Tivoli Provisioning Manager V7.1.1 product to automate and manage IT provisioning and integrated IT service management processes in their environments. It includes five parts: Concepts and architecture: Provides an overview of provisioning concepts and introduces Tivoli Provisioning Manager V7.1.1 concepts and architecture, in perspective with the overall Tivoli process automation engine platform. Planning for deployment and implementation: Discusses planning considerations for deploying Tivoli Provisioning Manager V7.1.1 in a production environment, installation and initial customization of product components, and a sample software deployment scenario to verify the successful deployment of the product. The new GUI and IBM Service Management integration scenarios: Covers value added integration scenarios with several IBM Service Management products such as IBM Tivoli Application Dependency Discovery Manager, IBM Tivoli Service Request Manager, and IBM Tivoli Change and Configuration Management Database. Also included is a section explaining the Start Center based new GUI, and a section on implementing Tivoli Provisioning Manager V7.1.1 with a non-IBM configuration management database. Patch Management, Operating System Deployment, and IBM Tivoli Monitoring Agent for Tivoli Provisioning Manager: Introduces several scenarios on Patch Management and Operating System Deployment, focusing on the new features. Also provided is an overview of the IBM Tivoli Monitoring Agent for Tivoli Provisioning Manager. Troubleshooting and migration from Tivoli Provisioning Manager V 5.1.2: Provides some tips for troubleshooting Tivoli Provisioning Manager V 7.1.1 installation and operation and discusses a migration scenario from Tivoli Provisioning Manager V 5.1.2.The team who wrote this book This book was produced by a team of specialists from around the world working at the Tivoli Rome Lab in Italy. Copyright IBM Corp. 2009. All rights reserved. xv 17. Alfredo Olivieri is an IT Architect working in SoftwareGroup Services in Italy. He holds a degree in ElectronicEngineering and is ITIL v3 certified. He has ten yearsexperience in IT, nine of which have been spent in IBM.Throughout his career, he has been involved in thedesign and the implementation of several projects in theavailability and automation areas of the Tivoli portfoliofor clients all over Europe. His experience includesNetcool and IBM Service Management familyproducts. At present he is working as an IT Architect onCCMDB and TBSM projects in Italy.Anna Pintus is a Tivoli Technical Consultant working forIBM Software Group Tivoli Lab Services, in Italy. She isan Open Group Master Certified IT Specialist. Annaaccumulated more than 15 years of experience inInformation Technology working across Network andSystems Management areas. Throughout her careershe has been involved in several large-scale Tivoliprojects for important customers located in Italy andEMEA and she gained extensive experience with manyTivoli products and solutions.Her current interests are in the Provisioning and ServiceManagement areas. Before joining the Tivoli LabServices she worked for five years in the L2 CustomerSupport team as technical leader for the PAN-EMEATivoli Framework escalation team. In the past she spentsome years in the Rome Tivoli Lab Verification teamworking on different technologies and applications(NetView DM, SystemView, TME10 NetFinity, TivoliConfiguration Manager). She holds a degree inEngineering and she is SOA and ITIL v3 certified. Shehas also received some Deployment ProfessionalCertifications in the Tivoli Provisioning Manager area.xvi IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 18. Annarosa Mallozzi is a Certified IT Specialist (SystemsManagement) working in the IBM L2 Customer Supportorganization. She has 11 years experience in IT, eightof which were in IBM. She is a DB2 Associate Certified,ITIL Service Management Foundation Certified andDeployment Professional Tivoli Data WarehouseCertified.Throughout her career, she gained a wide experiencewith different platforms, RDBMSs and IBM products.She worked as a Services Consultant in the mainframearea (CICS, IMS, DB2), developed applicationmonitoring solutions on UNIX based on shell scripting,built data analysis procedures in PL*SQL (Oracle),acquired a significant experience with MQSeriesinstallation and configuration on Windows, DB2 DataWarehouse solutions, DB2 installation andconfiguration. She has been involved in several projectsfor important world wide customers with different Tivoliproducts in the provisioning area (Tivoli ConfigurationManager, Tivoli Provisioning Manager for OSDeployment, Tivoli Data Warehouse and Tivoli LicenseManager). She teaches IBM methods applied toprojects and for method tailoring tools such as RationalMethod Composer.Claudio Santucci is a Software Support Specialistworking for Italy in Tivoli Customer Support within IBMGlobal Services. He has worked for IBM since 1996,and has extensive experience with the AS/400 SWPlatform. Before joining the Tivoli Support team, heworked as a certified iSeries IT Specialist and hasjoined multiple projects to implement AS/400 solutionsfor clients of IBM Italy. He also worked for several yearsin iSeries Customer support. In March 2007, he joinedthe Tivoli Customer Support within IBM Global Service.Danilo Allocca has been working for IBM since 2004.He worked on development and testing for the IBMTivoli License Manager product. In the past year, he hasbeen working in the Support Area (G.R.T. GlobalResponse Team) for S.P.A. products. Prefacexvii 19. Fabrizio Salustri is a Software Support Specialist working for Italy IMT in Tivoli Customer Support within IBM Global Services. He worked for IBM since 1996, and has extensive experience with Tivoli products suite. Throughout his career, Fabrizio has been involved in several projects implementing Tivoli solutions for important clients of IBM Italy. Before joining the Tivoli Support team, he worked as a Certified AIX System Administrator in AIX Technical Support. In March 2005 he got an IBM Tivoli Monitoring 5.1.1 Deployment Professional Certification and in April 2006, an IBM Tivoli Monitoring 6.1 Deployment Professional Certification. Gabriella Santoro started working for IBM in 1990 at the IBM Software Laboratory in Rome. During these years she built a broad and valuable knowledge with experience on both IBM (Tivoli) Systems Management products, and the software development life cycle, starting from requirements collection and prioritization, as EMEA Product Manager, until post sale implementation at the Customer site, as Tivoli Services Project Manager. Her main involvement has been in the Quality Assurance area, testing systems management products across different life cycle phases. In 2008 she received the IBM Tivoli Workload Scheduler V8.3 Deployment Professional Certification. These are the products she has worked on: Tivoli Provisioning Manager, Tivoli Workload Scheduler, IBM Tivoli Monitoring, Tivoli Enterprise Console, Tivoli Business Systems Manager, Tivoli Inventory, Tivoli Software Distribution, Tivoli Framework, Tivoli Remote Control, Tivoli NetView, Telecommunications Manager Network for AIX, OSI/X.400, OSI/6000 X.400 and NetView Distribution Manager for OS/2.xviii IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 20. GianFilippo Maniscalco is a Software SupportSpecialist working in Rome in Tivoli Customer Supportwithin Tivoli Lab. He holds a degree in ElectronicEngineering in 1996. He has worked for IBM since 2000and has extensive experience in IT (Build/PackagingSpecialist and UNIX System Administrator) andcustomer support, mainly on Tivoli products such asTivoli onfiguration Manager, Tivoli ProvisioningManager Express, and Tivoli Provisioning Manager. InDecember 2007 he received the ITIL v.3 certificationand in January 2008 he received the Certified TivoliProvisioning Manager V5.1 and Tivoli ProvisioningManager Express V4.1 for Software DistributionDeployment Professional certification.Ghufran Shah is an IBM Certified AdvancedDeployment Professional in Enterprise, Provisioning,and Business Application Management Solutions. Hehas 15 years of experience in Systems Developmentand Enterprise Systems Management and holds adegree in Computer Science. His areas of expertiseinclude Tivoli Systems Management Architecture,Implementation, and Tivoli Training, together withBusiness Process Improvement. He has writtenextensively about Event Management, Monitoring, andBusiness Systems Management integration and hastaught IBM Tivoli. courses worldwide. He is currently atTeamSwift Solutions, a trusted advisor for IT ServiceManagement Solutions with a focus on Automation,Service Provisioning, Monitoring, and Virtualization.Jenna Lau is an IBM Software Developer at the IBMToronto Lab. She has been with IBM Canada since2006, and has worked in automation packagedevelopment, test automation, and various other testphases for Tivoli Provisioning Manager V5.1 throughV7.1.1. Prior to IBM, she attended York University whereshe completed a double major in Computer Science andCreative Writing. Preface xix 21. Luca Balestrazzi is a Certified IBM IT Architect inGlobal Technology Services in Italy. He has five yearsof experience in the RNSL Rome Laboratory in servicesupport, two years of experience in service support forSystemView and Netfinity products, and 10 years ofexperience with Tivoli Area of Network and SystemsManagement products. He also has experience withIBM Service Management family products. He has adegree in Economics and is ITIL v3 certified. Luca isworking as a Delivery IT Architect on Change andConfiguration Management Database (CCMDB)Projects in Italy.Michael Edler von der Planitz is an IBM IT Specialistworking for IBM Tivoli Support in Germany. He workedin IBM and the formerly subsidiary company IT Servicesand Solutions GmbH since 1995. Michael has extensiveexperiences with the System Management portfolio ofTivoli products such as Tivoli Framework and TivoliConfiguration Manager. For this he was involved inseveral projects implementing Tivoli SystemManagement solutions for clients in Germany beside hiswork in Tivoli Support team Germany. He is also amember of the Virtual Front-End for Tivoli ProvisioningManager, a European team providing extended skills forTivoli Provisioning Manager support. Before joining IBMTivoli support, he worked in the banking area andtelecommunication sector and was involved in nationaland international projects implementing and developingIBM products. In 2005 he got a Certified DeploymentProfessional for IBM Tivoli Configuration Manager 4.2.Raffaela Bove is a Software Support Specialist at theIBM Maintenance & Technology Service in Italy. Shejoined IBM in 1998 and has extensive experience withthe Tivoli products suite. Throughout her career,Raffaela has been involved in several projectsimplementing Tivoli solutions for Italy importantcustomers. She is a certified Tivoli Storage Managerspecialist. Since 2007, she is the Team Leader of theTivoli Provisioning Manager Virtual Front-end.xx IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 22. Valentina Mariottini joined IBM in 1998 and started to work for as an IT Specialist on AIX, gaining knowledge and experience on various products and IT environments. Since 2004, she has been working for the Italy Tivoli Technical support as Front-End. Vasfi Gucer is a project leader at the ITSO Austin/TX. He has more than 15 years of experience in Systems Development and Enterprise Systems Management. He writes extensively and teaches IBM classes worldwide on Tivoli software. Vasfi is also an IBM Certified Senior IT Specialist, PMP, and ITIL Expert. Vittorio Calafiore is a Software Support Specialist working in Rome in Tivoli Customer Support within Tivoli Lab. He holds a degree in Electronic Engineering in 1997. He has worked for IBM since 2000 and has extensive experience in test, development, and customer support, mainly on Tivoli products such as License Management and Provisioning. In November 2007 he received the ITIL v.3 certification. In June 2008 he received the Certified Tivoli Provisioning Manager V5.1 Deployment Professional certification. Wing L Leung is a Senior Process Automation Specialist working in the ISST ATG SWAT team. He has over 10 years of experience with IBM working on various teams ranging from OS2 development, IBM Global Services (IGS) consulting, Tivoli development, ATG Security and Provisioning SWAT teams. He is ITIL certified and currently enjoys his role where he supports potential customers world wide in better understanding, evaluating, and utilizing IBM Service Management solutions.Thanks to the following people for their contributions to this project:Wade WallaceInternational Technical Support Organization, Austin CenterYvonne LyonInternational Technical Support Organization, San Jose CenterPreface xxi 23. Sarvi Aryanpour, Linda Burn, Pablo Caceres, Paul Chen, AndrewKaye-Cheveldayoff, Dragan Damnjanovic, Andrew Edgar, Tesshu Flower,Daniela Grigoriu, Yang Han, Juliana Hsu, Andreea Jurj, Partha Kaushik, CindyLee, Kimberly Mungal, Wing Lee, Mark Leitch, Michael Li, Lewis Lo, Jeffrey Luo,Jeff McRae, Mike Ng, Vincenzo Pasquantonio, Eugen Postea, Delia Rusu, DukeShih, Amy Song, Di Qiu, Ian Watts, Ting Xue, Nicola Yap, Alice Yeung, Ken SZhangIBM CanadaScott Berens, Mark Fantacone, Willie Harris, Emma Jacobs, Hari Madduri,Sanjay D. Pillay, Rajeeta Shah, Lily Orozco, Adriana Lopez Russell, PatrickWoodsIBM USASilvia Bellucci, Gianluca Bolognesi, Luigi Buoscio, Anna Ciotti, Donatello LeDonne, Giuseppe Grammatico, Giulia Farinelli, Claudio De Ingeniis, FabrizioLoppini, Salvatore Matrone, Giuseppe Parisi, Federica Scarfone, EdoardoTuranoIBM ItalyMarcio Rogerio LuccasIBM BrazilPawel NiezgodaIBM PolandLucian TicovIBM RomaniaGary Hamilton, Phil BillinIBM UKThe team would like to express special thanks to people managers CalogeroBufalino Marinella and Pietro Scarscioni from IBM Italy and Steve Roberts fromIBM Canada for providing the logistics and resources for the project.Also we would like to acknowledge the efforts of Stefano Sidoti and DavideCosentino from IBM Rome Lab, who provided the technical support andcoordinated access to the resources during the residency.Finally, a well deserved thank you to Barbara Fierro from IBM USA and IrisLeung from IBM Canada, for their support in IBM Service Managementscenarios.xxii IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 24. Become a published authorJoin us for a two- to six-week residency program! Help write a book dealing withspecific products or solutions, while getting hands-on experience withleading-edge technologies. You will have the opportunity to team with IBMtechnical professionals, Business Partners, and Clients.Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you will develop a network of contacts in IBM development labs, andincrease your productivity and marketability.Find out more about the residency program, browse the residency index, andapply online at:ibm.com/redbooks/residencies.htmlComments welcomeYour comments are important to us!We want our books to be as helpful as possible. Send us your comments aboutthis book or other IBM Redbooks publications in one of the following ways: Use the online Contact us review Redbooks form found at: ibm.com/redbooks Send your comments in an e-mail to: redbooks@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400 Prefacexxiii 25. xxiv IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 26. Part 1Part 1 Concepts and architecture In this part of the book, we first provide a brief overview of provisioning concepts. We then introduce Tivoli Provisioning Manager V7.1.1 and explain how this product can be used to implement a comprehensive provisioning solution in your environment, focusing on the business value of the solution. We also discuss Tivoli Provisioning Manager architecture, in perspective with the overall Tivoli process automation engine platform. Copyright IBM Corp. 2009. All rights reserved. 1 27. 2 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 28. 1Chapter 1. Tivoli Provisioning Manager V7.1.1 overview In this chapter we provide an overview of Tivoli Provisioning Manager Version 7.1.1, together with the new features in this release, as well as a summary of the changes between this version and Tivoli Provisioning Manager Version 5.1.x. We cover the following topics: Introduction to Tivoli Provisioning Manager on page 4 1.2, What is new in this release on page 11 Tivoli Provisioning Manager Version 7.X client value on page 17 Copyright IBM Corp. 2009. All rights reserved.3 29. 1.1 Introduction to Tivoli Provisioning ManagerProvisioning is an end-to-end capability to automatically deploy anddynamically optimize resources in response to business objectives inheterogeneous environments. Provisioning helps you to respond to changingbusiness conditions by enabling a dynamic allocation of the existing availableresources to the processes that most need them, as driven by business policies.Provisioning of individual elements, such as identities, storage, servers,applications, operating systems, and middleware is a critical step to orchestratethe entire environment enabling it to respond to business needs on demand.Provisioning focuses on the self-configuring, dynamic allocation of individualelements of the IT infrastructure so that identities or storage or servers aresupplied as business needs dictate. These elements could be: A single software package A software stack, which consists of a group of software packages A server, which conforms to a template that is a defined set of software and hardware resources1.1.1 Tivoli Provisioning Manager conceptsIf you are new to Tivoli Provisioning Manager, the following section will help youunderstand some of the important concepts related with the product.Workflow A series of steps that are sequentially executed to accomplish a particular task. A step in a workflow is called a transition. Each workflow has a single compensating workflow that is executed if any transition fails.Automation package A collection of commands, shell scripts, workflows, logical device operations, and Java plug-ins that applies to the operation of a specific type of software component or a physical device.Device driverAlso referred to as a device model, this is a group of workflows that can be a applied to an IT asset.Logical device A task that is abstracted from its implementation.operationLogical device operations (LDOs) are implemented by Enterprise Java Beans (EJB). They provide a common interface and can perform logic. An example is a data center task of adding an IP address. It is a logical operation in that it makes no assumptions about the implementation. (Note that adding an IP address to Linux is very different from adding an IP address to Windows.)4 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 30. TransitionA step in a workflow. This could be another workflow, alogical operation, a simple command, or a Java plug-in.Data center model A representation of all of the physical and logical assetsunder Tivoli Provisioning Manager management.CustomerA customer owns applications. Customers can be uniquecorporations or departments within a single corporation.Application A grouping of one or more clusters. Service level priority(Silver, Gold, Platinum) is assigned at this level.Application tierA grouping or container for like resources or servers thatsupport an application. Automated resource allocationand deallocation occurs at the cluster level.Resource pool A container of available (deallocated) servers that supportone or more application clusters. Also referred to as aspare pool.Servers Data center model objects that represent physicalservers. They belong to or are assigned to pools andclusters.Software stackEither an image stack or product stack that contains anordered list of software products, software stacks, or both.Software productThe attributes and the methods for deploying a piece ofsoftware on an asset. A software product can beuser-written or COTS (commercial off-the-shelf).CapabilityIdentifies attributes of a piece of software that can beused for prerequisite and co-requisite validation.Requirement Defines dependencies on software or hardware.Requirements can be used to define different types ofrelationships, such as requirements that identify aninstallation mechanism, requirements to run the software,hosting requirements.Service AccessA definition of the protocol and credentials used byPoint (SAP) or associated with an asset. The configuration data for aservice access point includes the application protocol,network protocol, and the endpoint details (IP address,port...). An asset can have more than one SAP. Chapter 1. Tivoli Provisioning Manager V7.1.1 overview5 31. Software Configuration Template (Software Resource Template (SRT))A software configuration template identifies softwareresources and associated configuration details that youwant to represent in the data center model after thesoftware is installed on a system. Each softwareconfiguration template is used to create a softwareresource on the target system.Figure 1-1 shows the relationship between device model, logical deviceoperations, workflows, and data center infrastructure.Figure 1-1 Data center infrastructure mapped into the device model6 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 32. 1.1.2 The data center model (DCM) The data center model is a model of physical assets in a data center with a logical organizational structure to give context. The logical organizational structure answers questions such as, What customer is using this server? and Which applications can use this server when their needs increase? The data center model is an internal representation of the data center including hardware, software, logical entities and customers. In order to make intelligent decisions about reallocating resources, the current state is always modeled. When changes are made, the ramifications of those changes must be completely understood. A server can belong to one resource pool, be assigned to a given application tier, be a member of a particular VLAN (virtual lan), and so on. All of these relationships need to be understood so that when the server is moved, it is returned to the correct pool, it is changed to the correct VLAN if necessary and so on. The data center model captures all of these relationships and maintains them appropriately when reallocating resources. The data center model is implemented as a relational database. When software is installed on a computer using Tivoli Provisioning Manager, the software will be installed on the physical machine, and also the DCM will be updated to update the logical model in the DCM. If management operations such as software installs or computer network re-configuration are performed without using the Tivoli Provisioning Manager environment, then the logical model in the DCM will no longer be a correct representation of the real physical environment. Data center model objects Physical elements in the data center are modeled as DCM objects that are generic representations of the physical elements. See Figure 1-2. A Cisco 2600 and a Cisco 3548 would each be modeled as a Switch DCM object; an xSeries server and a pSeries server would each be modeled as a Computer DCM object; and an installation binary for Apache on Windows or Apache on Linux would each be modeled as a SoftwareInstallable DCM object. Chapter 1. Tivoli Provisioning Manager V7.1.1 overview 7 33. WSDLLogical Device Operation (LDO) Normalized Interfaces Device AbstractionServer ResourcesProprietary Name ClassInterfaces to Data Software Stack NIC Switch Center Devices DCM Automation PackagesFigure 1-2 Data center model objectsConfiguration information is also modeled in the DCM. An example of this isinformation used to connect to remote systems. This connection information ismodeled as a ServiceAccessPoint DCM object.Management operationsTypical management operations are generalized and grouped by the sort ofdevice that would be the target of the operation. Operations such as turn port onand turn port off are most often run against switches, so those operations aregrouped and associated with a logical device called Switch. Operations such asexecute command and copy file are so generic that they are grouped andassociated with a logical device called Device. Because all of the genericoperations are associated with logical devices, they are called logical deviceoperations (LDOs).DCM objects can behave like one or more logical devices. It is possible toassociate any LDO with any DCM object, but not all of these associations wouldmake sense and not all LDOs would function (some validate the DCM object typebefore running).WorkflowsWorkflows are the instructions that the deployment engine executes when it iscarrying out a management task. These instructions are expressed in ascript-like language and can call logical device operations and other workflows.8 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 34. Parameters can be passed to workflows at run time, and parameters can belooked up by the workflow when it is running, allowing for modular and reusableworkflows.Using LDOs, a workflow can be written at a high level to carry out a complicatedmanagement task, and the LDOs can call other workflows to interact with specifichardware and software. Important: As shown in Figure 1-2 on page 8, Tivoli Provisioning Manager is an object oriented system where not only data about resources can be stored but also operations on them. Invoking those operations programmatically leads to task automation. It is extensible to accommodate new device types, by adding automation packages. Programmability is a key strength of Tivoli Provisioning Manager.Customer topologyA typical data center will be used to provide to provide one or more services toone or more customers. When servers are being utilized to provide amanagement service such as Web Hosting to Application Hosting, the customertopology can be used to model this situation.As shown in Figure 1-3, A Customer can be defined, each with one or moreApplications. Each Application can have one or more Application Tiers. EachApplication Tier will have one more servers assigned to it. Application Tiers canhave a number of dedicated servers, or a number of servers that have beenassigned from a Resource Pool.Figure 1-3 Customer modelling in the DCMChapter 1. Tivoli Provisioning Manager V7.1.1 overview 9 35. Resource pools are used to share resources (Servers) between differentapplication tiers, and are defined to increase the utilization rates of servers in adata center. Increased utilization rates are the result of sharing processorsamong multiple applications. In order to realize these performanceimprovements, one must share the servers. Resource pools are unallocatedresources that can be given to an application cluster in response to increaseddemand. Likewise, when demand declines, servers are returned to the resourcepool by the applications. (Resource pools are also called spare pools.)An example is shown in Figure 1-4.Figure 1-4 Customer example in the DCM1.1.3 SecurityIn Tivoli Provisioning Manager, the security consists of: Authentication Authorization Workflow security servicesAuthentication is the process of logging into Tivoli Provisioning Manager.It uses the framework provided by Tivoli process automation engine platform(see 2.1, Tivoli process automation engine on page 20). This is integrated intoWebSphere security service to accomplish the authentication service.Authorization is the control of which users can use which applications.10 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 36. The resources that a user has permission to access are defined by security constraints. Security constraints in Tivoli Provisioning Manager 7.1.1 are the combination of conditions and data restrictions in Maximo. Workflows can be protected. This means that they can only be run by a user having the correct set of permissions. The underlying security for workflow uses Maximo (its combination of conditions and data restrictions). All of them are integrated in the Maximo Security Framework, which is now part of the Tivoli process automation engine.1.2 What is new in this release This section provides a summary of new product features and enhancements in Tivoli Provisioning Manager version 7.1.1 as compared to Tivoli Provisioning Manager version 7.1. Most of these enhancements are expanded in the subsequent chapters of this book.Note: You can refer to the following link for an overview of Tivoli ProvisioningManager V7.1.1 features:http://publib.boulder.ibm.com/infocenter/tivihelp/v28r1/index.jsp?topic=/com.ibm.tivoli.tpm.scenario.doc/overview/covw_overview.html. We discuss the following enhancements in this section:Custom attributesComplianceCompliance with Federal Information Processing Standard 140-2DiscoveryDiscovery Library Adapter (DLA)InstallationIPv6 addressingMigrationOperating systems managementPatch ManagementReportingScalable distribution iInfrastructure (SDI)SecurityStart CentersTarget computersTask managementVirtualizationChapter 1. Tivoli Provisioning Manager V7.1.1 overview 11 37. 1.2.1 Custom attributesYou can now add custom attributes, both as data model properties andConfiguration Item (CI) extended attributes. Note: A Configuration Item is any component of an IT infrastructure that is under the control of configuration management. A Configuration Item extended attribute is an attribute that is not part of the original data model, but is added by the user.1.2.2 ComplianceYou can now create a software configuration template that represents a standardsoftware configuration to be implemented on target computers. After you havecreated the template, you can create a software configuration check based on itand run the check to compare the configuration of the application on targetcomputers with the standard configuration for that application.See Chapter 9, IBM Service Management integration scenarios: Complianceand remediation with TADDM on page 217 for a compliance scenario.1.2.3 Compliance with Federal Information Processing Standard140-2You can enable FIPS 140-2 compliance for new Tivoli Provisioning Managerinstallations. Note: FIPS 140-2 compliance is not supported for upgrade from version 7.1 to version 7.1.1.1.2.4 DiscoveryHere are some improved discovery capabilities: By using custom inventory extensions, you can extend the data model inventory schema with additional attributes, and you can perform custom inventory scans. You can generate reports for inventory extensions. Improved automation packages for HMC (Hardware Management Console) discovery are available in this release. Discovery of IPv6 addresses is now supported12 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 38. 1.2.5 Discovery Library Adapter (DLA)The Tivoli Provisioning Manager Discovery Library Adapter (DLA) has beenenhanced. You can now export a specific subset of data types, such as softwareproducts or a set of computers, computer related objects (software installationsand operating systems), and attributes to the discovery library book. In addition,the DLA now writes physical CPU information into the discovery library book,which can be consumed by other products through the DLA itself.1.2.6 High availabilityThe managed agents can now be automatically configured to work with aback-up manager. When the secondary manager is established, the managedagents are reconfigured to be associated with the new manager.See 2.2.3, Tivoli Provisioning Manager V7.1.1 configuration for high availabilityand data integrity on page 34 for details of configuring Tivoli ProvisioningManager for high availability.1.2.7 InstallationThe following enhancements have been made: Administrative workstation on UNIX operating systems is supported. New platforms and versions are supported for installation: Windows Server 2008, Windows Server 2003 R2, AIX 6.1, Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 10, and Solaris 10. A new database version is supported for installation: Oracle 11g. A new directory server version is supported for installation: IBM Tivoli Directory Server 6.2. Enhanced installation process and user interface are available: The installation process is more streamlined by installing the base services before Tivoli Provisioning Manager components. The launchpad options are better designed and the fields provide more details and explanatory information. This release offers enhanced verification of prerequisites during the installation process: Created additional checks for the required packages. Included checks for AIX disk space requirements. Added requirements checklists to be reviewed and validated by the user during the installation process. Consolidated the prerequisite check results. Chapter 1. Tivoli Provisioning Manager V7.1.1 overview 13 39. The recovery procedure was enhanced by automating the WebSphere Application Server, database, and base services deployment folder backup procedures.Refer to 4.3, Tivoli Provisioning Manager V7.1.1 installation on page 68 forTivoli Provisioning Manager installation.1.2.8 IPv6 addressingA dual stack environment supports communication using either IPv4 and IPv6addressing. The dual stack environment helps organizations to transition theirnetwork from IPv4 to IPv6 addressing. By default, IPv6 support is disabled. If youwant to use IPv6 support, you must enable it after installation. Note: For Tivoli Provisioning Manager on Windows, IPv6 enablement is not supported.1.2.9 MigrationYou can migrate data and artifacts from version 5.1.1.2 to the version 7.1.1 level.See Chapter 17, Migrating from Tivoli Provisioning Manager Version 5.1.1.2 toTivoli Provisioning Manager Version 7.1.1 on page 541 for a detailed coverageof the migration. Note: To migrate your data from version 5.1.1.2, you must install version 7.1.1 on another computer on the same VLAN as the 5.1.1.2. That is because at a certain point in the migration process, you have to configure the new system to use the 5.1.1.2 system host name and IP address.1.2.10 Operating systems managementThe following enhancements have been made: You can view the replication status of your OS deployment servers. You can copy log files from a remote OS deployment server to the local repository on the provisioning server using a provisioning workflow. You can create an image properties file that defines parameters for to all future deployments of an image. An image properties file includes settings that are not available in the Web interface.14 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 40. Refer to Chapter 14, Operating system provisioning on page 409 for a detailedcoverage and scenarios.1.2.11 Patch ManagementThe following enhancements have been added: Scalable Patch Management on Linux RHEL 5 target computers using the scalable distribution infrastructure. Patch Management for HP-UX environments using Software Assistant (SWA). Patch Management solution for SUSE Linux environments using the rug command-line tool, provided with SLES 10 operating systems. Enhanced Patch Management solution for Solaris environments using Sun Update Connection Enterprise.For more information, see Chapter 13, Patch Management scenarios onpage 371.1.2.12 ReportingNew notification reports are available using the Business Intelligence andReporting Tool (BIRT) framework.1.2.13 Scalable distribution infrastructure (SDI)The following SDI enhancements have been added: IPv6 addressing can be used in the scalable distribution infrastructure. An enhanced agent upgrade mechanism using the scalable distribution infrastructure is available. This solution provides highly scalable update distribution capabilities to previously installed agents. The maximum size of a software package block for software distribution has been doubled and can reach now up to 4 GB.For more information, see 5.2, Implementing the scalable distributioninfrastructure on page 107. Chapter 1. Tivoli Provisioning Manager V7.1.1 overview 15 41. 1.2.14 SecurityThe following security enhancements have been added: Multiple LDAP repositories are now used for storing user and group information with the help of the Virtual Member Manager (VMM) framework. Authorization on workflow executions is enabled by instance level security. Authorization for Web interface elements based on role permissions and new security groups is now available. These are provisioning permission groups that identify the specific user, the permission, and the resources to be protected.For more information about implementing Tivoli Provisioning Manager V7.1.1security, refer to 5.1.1, Security overview on page 102.1.2.15 Start CentersNew Start Centers exist for focused role-based access to functions and data. Formore information, see Chapter 6, Tivoli process automation engine based userinterface on page 137.1.2.16 Target computersThe following new operating systems and functions are supported onprovisioning server target computers: Linux RHEL 5 is now supported on endpoints. The ability to pause and resume a deployment operation offers the ability to define the maintenance window for each target computer under management.1.2.17 Task managementThe following enhancements have been made in the task management area: You can create a group from the target computers, on which you have run a provisioning task. In this way, you can schedule new tasks to run on the same set of targets. You have now the ability to rerun a failed task on specific target computers where the initial task failed.16 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 42. You can define a concurrency level within a provisioning task before the provisioning task is run. The concurrency level determines the maximum number of concurrent jobs that are permitted within a task.1.2.18 VirtualizationThe following virtualization enhancements have been added: The virtual server status can be verified from the provisioning server before requesting a virtual machine. Because of the multipath I/O function, you now have continuous access when a virtual I/O server has to be taken offline for planned outages. Streamlined creation of VMware virtual machines by supporting the discovery and deployment of VMware templates. When creating a virtual server template, you can now specify a target folder for the virtual server container. Advanced search capabilities are available for virtualization management.1.3 Tivoli Provisioning Manager Version 7.X client valueFor existing Tivoli Provisioning Manager V5.X customers, the following listsummarizes the business benefits that will be realized after moving to a TivoliProvisioning Manager V7.1 or Tivoli Provisioning Manager V7.1.1 environment: Inclusion of Tivoli Provisioning Manager tasks in Change, Release, and Tivoli Service Request Manager flow definitions. Ability to easily take Tivoli Provisioning Manager actions on CCMDB CIs: The use of CMDB CIs as database for process flow construction and information is automatically translated to Tivoli Provisioning Manager DCM for operational purposes. Ability to use Tivoli process automation engine workflow editor to design and formalize Tivoli Provisioning Manager activities: You can define Tivoli process automation engine workflows to formalize and automate multi-person Tivoli Provisioning Manager activity flows. Tivoli Provisioning Manager activity flows can include non-Tivoli Provisioning Manager related tasks (for example, sign-offs, escalations). Extensive Web Replay scenario library provides guidelines and education on product use (quick method for product education and skills transfer).Chapter 1. Tivoli Provisioning Manager V7.1.1 overview 17 43. New, highly customizable Tivoli Provisioning Manager GUI technology: Easy modification of existing applications. Ability to create your own applications. Easily customizable to display only required data and tasks for a specific role or user. Consistent look and feel across IBM Service Management products provides seamless interactions and minimizes user education requirements. Ability to incorporate functions from multiple IBM Service Management products on single screen. Orchestrated automation capabilities: Advanced automation technology can be used to support infrastructure service level agreements (SLAs) through dynamic resource allocation based on monitoring inputs. Enhanced integration with Tivoli Application Dependency Discovery Manager (TADDM), Tivoli Storage Productivity Center (TPC), and IBM Rational Test Lab Manager (RTLM): TADDM: Closed loop desired state management for software configurations. TPC: Launch in context from Tivoli Provisioning Manager to TPC. RTLM: Test lab server provisioning with transitions to production. Integration with Tivoli Provisioning Manager for Operating System Deployment: Seamless transition from using Tivoli Provisioning Manager to using Tivoli Provisioning Manager for Operating System Deployment; no product switching is required to utilize baremetal or initial image install functions. Automated database exchange between the two products. Enhanced SDI management capabilities: Better status information and enhanced control of deployment infrastructure. Additional virtualization technology support. Additional OS support.18 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 44. 2Chapter 2. Architecture In this chapter we address the challenge of integrating many solutions to multiple problems in a service management environment, especially when the solutions were supplied by different vendors. We cover the following topics: Tivoli process automation engine on page 20 How Tivoli Provisioning Manager extends the Tivoli process automation engine on page 25 Tivoli Provisioning Manager V7.1.1 component architecture on page 27 Tivoli Provisioning Manager V7.1.1 configuration for high availability and data integrity on page 34 Tivoli Provisioning Manager V7.1.1 scalability on page 34 Copyright IBM Corp. 2009. All rights reserved.19 45. 2.1 Tivoli process automation engineBecause there are multiple problems to tackle in a service managementenvironment, you need to implement multiple solutions, such as AssetManagement, and Configuration Management, as shown in Figure 2-1. Thechallenge is how to integrate all these different solutions to provide an end-to-endservice management environment, especially when these solutions weresupplied by different vendors.Tivolis strategy is to build the complete IBM Service Management portfolio ofproducts on top of a common platform, called the Tivoli process automationengine. This platform provides the common user interface, configurationservices, process workflow runtime and services, and common data system.It is more than what Maximo was in previous Maximo products. It includesinstallation solutions, common services needed for IBM Service Management,and other services.This approach has two important benefits: You can introduce these solutions incrementally. All of these solutions are integrated on top of the Tivoli process automation engine platform to provide an overall, end-to-end service management solution. You do not need to implement this integration yourself.The Tivoli process automation engine is unique in its ability to: Combine asset and service management in one environment Deliver a federated configuration management system Provide advanced business process management and integration with other Web-based tools Preserve upgradeability and ease of configuration, and offer full end-to-end management views of business applications20 IBM Tivoli Provisioning Manager V7.1.1: Deployment and IBM Service Management Integration Guide 46. ,gy y ,pyIntegrated Solution Integrated SolutionAn Integrated set of solutions represent An Integrated set of solutions represent the full management of data, processes,the full management of data, processes, tooling and peopletooling and people Service Request and Server & ApplicationFulfillment ManagementProvisioning & Release ManagementCommon Data ModelCommon Data Model CIs IT AssetsProcess ArtifactsThe core solutions share a common dataThe core solutions share a common dataRelated to CIs andAttributessubsystem for simple data sharing subsystem for simple data sharingAttributesAssets Relationships RelationshipsProcess Definitions Configuration Data Processes that Work Together Processes that Work TogetherTivolis process automation engine The core solutions share a process The core solutions share a processworkflow automation engineworkflow automation engine Common applications | Common workflow | Common reporting | Common User Interface | CommonAutonomic Extensions No Rip and Replace No Rip and ReplaceLeverage existing investments in IBM andLeverage existing investments in IBM and 3rd party IT management tools 3rd party IT management toolsAsset, Change &Incident and Problem ConfigurationManagement Management Lower Cost of Ownership Lower Cost of Ownership Lower infrastructure and training costs, Lower infrastructure and training costs, simple upgrade model simple upgrade modelFigure 2-1 Tivoli process automation engineAs you can see from Figure 2-2, the Tivoli process automation engine iscomposed of four blocks, which are sets of core capabilities: Common User Interface Common Configuration Services Process Workflow Runtime and Services Common Data SubsystemChapter 2. Architecture21 47. Figure 2-2 Tivoli process automation engine core capabilities2.1.1 Common User Interface The Common