Tivoli Provisioning Manager

®

Version 7.2

Installation Guide for Windows

Tivoli Provisioning Manager
®

Version 7.2

Installation Guide for Windows

Note Before using this information and the product it supports, read the information in “Notices” on page 235.

Last updated: December 2010 This edition applies to IBM Tivoli Provisioning Manager 7.2 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2003, 2010. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Chapter 1. Installation overview . . . . 1
Supported platforms and Product components . . Installation types . . . Installation process . . compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 2 3 Installing Tivoli Provisioning components . . . . . . Installing Tivoli Provisioning components . . . . . . Manager . . . Manager . . . core . . . web . . . . . . 119 . 128

Chapter 4. Post-installation tasks . . . 131 Chapter 2. Preinstallation tasks . . . . 5
Preinstallation Step 1: Run the prerequisites scanner 6 Preinstallation Step 2: Read the release notes . . . 6 Preinstallation Step 3: Plan the topology . . . . . 6 Single-server deployment . . . . . . . . . 7 Multiserver deployment . . . . . . . . . 8 Preinstallation Step 4: Allocate appropriate hardware 9 Preinstallation Step 5: Verify component requirements . . . . . . . . . . . . . . 12 Supported operating systems and middleware combinations . . . . . . . . . . . . . 12 Operating system preinstallation tasks . . . . 13 Database and directory server requirements . . 15 Browser requirements . . . . . . . . . . 15 Preinstallation Step 6: Verify the environment . . . 16 Preinstallation Step 7: Verify requirements for user names, database names, and user passwords . . . 21 Preinstallation Step 8: Prepare installation media . . 23 If using downloaded installation images . . . . 23 If using installation DVDs . . . . . . . . 24 Installing the language pack for Tivoli Monitoring agent . . . . . . . . . . . . . . . . Backing up the administrative workstation . . . Configuring a web browser for Federal Information Processing Standard 140-2 compliance . . . . . Starting the provisioning server on Windows . . . Manually configuring directory synchronization for WebSphere Application Server Network Deployment . . . . . . . . . . . . . . Configuring the LDAP server for user authentication only . . . . . . . . . . . Adding users and security groups . . . . . Defining the boot server after installation . . . . Setting up the infrastructure for software distribution tasks . . . . . . . . . . . . 131 132 133 133

134 135 136 137 137

Chapter 5. Uninstalling Tivoli Provisioning Manager. . . . . . . . 139
Uninstalling Tivoli Provisioning Manager core components . . . . . . . . . . . . . . Uninstalling the Tivoli Monitoring agent . . . Uninstalling Tivoli Provisioning Manager for OS Deployment . . . . . . . . . . . . . Uninstalling Tivoli Provisioning Manager for Job Management Service federator . . . . . Uninstalling Tivoli Provisioning Manager for dynamic content delivery . . . . . . . . Uninstalling the agent manager . . . . . . Uninstalling Tivoli Provisioning Manager engines . . . . . . . . . . . . . . Uninstalling the DB2 client . . . . . . . . Uninstalling the base services and web components Uninstalling middleware . . . . . . . . . Removing items remaining after uninstallation . . Removing application files and configuration settings . . . . . . . . . . . . . . Removing the Global Unique Identifier . . . . Uninstalling and reinstalling the deployment engine database . . . . . . . . . . . . Reinstalling Tivoli Provisioning Manager . . . . 139 139 140 141 143 143 144 145 146 146 147 147 148 149 150

Chapter 3. Installing Tivoli Provisioning Manager . . . . . . . . . . . . . . 25
Example deployment scenarios . . . . . . . . 26 Starting the launchpad . . . . . . . . . . 29 Installing the middleware on Windows, AIX, and Linux . . . . . . . . . . . . . . . . 29 Planning worksheets for middleware installation 31 The middleware installer workspace . . . . . 34 The middleware installer logs . . . . . . . 34 Installing and configuring the middleware with the middleware installer . . . . . . . . . 36 Reusing middleware using the middleware installer. . . . . . . . . . . . . . . 45 Using manually configured middleware . . . . 49 Changing middleware installer configuration parameters . . . . . . . . . . . . . 93 Starting middleware on Windows . . . . . . 94 Stopping middleware . . . . . . . . . . 95 Checking middleware status. . . . . . . . 97 Installing the base services . . . . . . . . . 98 Planning worksheet for base services installation 110 Starting the launchpad . . . . . . . . . 111 Remote configuration enablement. . . . . . 111 Deploying Provisioning Manager EAR files . . 112 Manually installing Provisioning Manager applications into WebSphere Application Server Network Deployment . . . . . . . . . 114 Installing the language pack . . . . . . . 116
© Copyright IBM Corp. 2003, 2010

Appendix A. Troubleshooting installation . . . . . . . . . . . . 151
Problems during middleware installation . . Backing up and restoring the deployment engine database . . . . . . . . . CTGIN9077E error during middleware installation . . . . . . . . . . . Links in the launchpad do not work. . . . . . . . 151 . 151 . 152 . 152

iii

. . Turning on Admin mode is slow . . . Deployment of MAXIMO. . . . . . . . Core components or web components installation hangs during Cygwin installation . . . . . . . . . . . 152 153 153 154 154 155 155 156 156 156 157 158 158 159 160 161 161 162 162 164 164 165 165 166 167 167 168 168 173 178 179 180 181 183 Installation fails after WebSphere Application Server is uninstalled . . . . . . . . . . . . . . . . . . . . . . . Cygwin installation fails . . . . . . .ear fails . . Installation fails because of unrecognized font Cannot use hyphen in domain name suffix field Installation of dynamic content delivery fails Core components installation fails during the dependency check . . . . . . . Error when configuring WebSphere Application Server to run as tioadmin . . . . . Encountering error CTGIN9042E . . . . . . . . . . . . . . . Enabling RXA tracing . . . . . . . . WAS_HOME error when using login window manager . . 205 Installing Tivoli Provisioning Manager with default values . DB2 installation fails when configured names do not match . . . . . . Cannot log on after successful installation . . . Recovering from problems during core components installation . . . . 205 207 207 208 208 iv IBM Tivoli Provisioning Manager Version 7. . . . . . The Microsoft Active Directory configuration fails . . Step by step recovery for core components installation (default installation) . Database error during installation . . . . . . First discovery fails after installing Cygwin . . . . . . . Other installation and configuration tasks . . . . . . . . . Errors CTGIN2381E or CTGIN2489E during Maximo database upgrade . . . . . Password policy is set to never expire during base services installation. . Cannot connect to the database server during installation . . . . . . . Agent Manager installation fails . . . . . . . . Recovering from a failed installation without the uninstallation program . . . . . . . . . Tivoli Provisioning Manager does not install when terminal server is enabled . . . Web components installation fails with registry service unavailable Java exception (IURegException) . . . . . Recovering from errors during a default installation . . . . . Step by step recovery for core components installation (custom installation) . . . . Deployment engine error during web components installation . . Error CWLAA6003 occurs after CCMDB installation . . . . . . . . . . . . . . . . . . . . Removing a Cygwin installation . . . . . Maximo business objects from the deployment engine gets out of sync with the ones in the application server . . . . . . . . . . . . Recovering from deployment engine failure during installation. . . . . Collecting information about installation problems 183 183 184 185 185 186 186 187 187 188 188 189 189 189 190 190 190 192 193 194 194 197 197 198 198 198 199 199 200 200 200 201 Appendix B. . Node agent not started during web components installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The base services installer fails to validate the installation . . Missing tools from Cygwin installation . . . Errors creating the agent manager profile . . . . . . . . . Installing Cygwin manually . . . . . . . Silent installation exits before installation is completed . . . . . . . . . . Error CTGIN2252I during base services installation . . . The base services installation fails . Cannot connect to Tivoli Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering from errors during web components installation . . . . Recovering from problems during base services installation . . . . . . . . . . . . . . . . . . . Problems during base services installation . . Core components or web components installation hangs during Cygwin installation . . . . Error message Insert disk 1 . . . . . . . Maximo business objects are out of sync between the deployment engine and the WebSphere runtime . Removing a default installation . . . Problems during web components installation . . . Other problems. Disk space check failure during silent installation of Tivoli Provisioning Manager . . . . . The common agent and the agent manager cannot be installed . . . . . . . . . . . . . . . . . . . . . Tivoli Directory Server installation step fails during Tivoli Provisioning Manager installation . . . . . . . . Problems during core components installation . . . . Error configuring database during middleware installation . . . . . . . . . . Uninstallation of WebSphere Application Server Network Deployment fails after unsuccessful binding to the LDAP directory . . . . Silent installation and other installation tasks . . . . . . . . . Log files for process solution installer . . . . . . .2 Installation Guide . . . . . . . . . . . . Editing text files changes permissions . . . . . . . . . . . . . . . DB2 BIND warning during Tivoli Provisioning Manager for OS Deployment installation . . Tivoli Provisioning Manager installation fails with invalid directory name . . Log file errors after successful installation on Microsoft Windows Server 2008 R2 Standard Edition (x86 64-bit) any SP . . . . . The Tivoli Provisioning Manager installation fails with incorrect certificate value . . . . . . . . . . . Remote connection to database hangs when database server is on a multiprocessor computer Step by step recovery for IBM Tivoli Monitoring agent manual installation . . Silent installation of Tivoli Provisioning Manager fails .Errors with the middleware installer . .

. . . . . . . . . . . . . . . Adding the parameter values to the property file . . . . . . . . . . . . . . . Updating the database server host name from the administrative workstation . . Compliance with Federal Information Processing Standard 140-2 . . . . . . 222 . . . . 239 Contents v . . . . . . Starting and stopping. . Creating multiple users with maxadmin privileges Changing user passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 . . Working with users . . . . . 225 226 . . . Updating the remaining host names . . . . . . . 233 Notices . . . . . . . . . . . . . . . . . . Starting and stopping the Tivoli Monitoring agent . . . . . . . . . . . . . Verifying the installation of WebSphere Application Server . . . . . Starting and stopping Tivoli Provisioning Manager components. Changing the host name for the provisioning server . . . . . . Signing off the provisioning server . . 209 211 211 213 214 214 215 216 217 217 219 219 220 221 221 Assigning the new host name to the provisioning server . . . 232 . . . . . . . . . . . . Using the Tivoli Monitoring agent . 235 Index . Parameters for the host name rename feature Return codes . . . . . . . 231 . . . . . WebSphere Application Server tasks . . Installation directories and other paths . . Starting and stopping the provisioning server on Windows . . . . . . . . . . . Required passwords . . . . . . 224 . . . . . . . . . Verifying components . . . . . Signing on to the provisioning server . . . . . . 232 . . . . . . . . . . . . . . . . . . . . . .Installing Cygwin manually . . . . . . . . .

2 Installation Guide .vi IBM Tivoli Provisioning Manager Version 7.

1. The base services are a set of common routines that can be used by higher level functions such as process managers.1. you cannot share the same middleware or base services installation with Tivoli Provisioning Manager. Therefore. Base services compatibility Tivoli Provisioning Manager requires that the version of the base services is version 7. Supported operating systems Tivoli Provisioning Manager can be installed on the following operating systems: v Microsoft Windows Server 2008 R2 Enterprise Edition (x86 64-bit) v Microsoft Windows Server 2008 R2 Standard Edition (x86 64-bit) v Microsoft Windows Server 2008 Datacenter Edition (x86 64-bit) v Microsoft Windows Server 2008 Enterprise Edition (x86 64-bit) v Microsoft Windows Server 2008 Standard Edition (x86 64-bit) v v v v Microsoft Microsoft Microsoft Microsoft Windows Windows Windows Windows Server Server Server Server 2003 2003 2003 2003 R2 Enterprise Edition SP2 (x86 64-bit) R2 Standard Edition SP2 (x86 64-bit) Standard Edition SP2 (x86 64-bit) Enterprise Edition SP2 (x86 64-bit) Note: The supported operating systems and versions reflect what was tested with Tivoli Provisioning Manager. Installation overview A complete Tivoli® Provisioning Manager product installation is composed of multiple application components.6.6. After applying the fix pack. you must have a basic understanding of the installation components.2 Fix Pack 1 will not upgrade the base services.Chapter 1. Differences in other editions or changes implemented in other versions for an operating system might cause errors during or after installation. and other products that are used by Tivoli Provisioning Manager. the base services will remain unchanged at version 7.1. 2010 1 . Supported platforms and compatibility Tivoli Provisioning Manager supports specific operating systems and is compatible with other products that are installed together with the base services. see “Preinstallation Step 5: Verify component requirements” on page 12. For more information about the supported operating system requirements for middleware and other Tivoli Provisioning Manager components. To better understand the installation process. © Copyright IBM Corp. Tivoli Provisioning Manager V7. Middleware compatibility Tivoli Provisioning Manager does not support the following middleware. ensure that you are using the specific edition and version of the operating system as indicated. which might be supported by other products installed on base services: v Oracle WebLogic Server as an application server v Microsoft SQL Server as a database server v Oracle Database as a database server installed on Windows If you have installed another product on base services with any of these middleware applications. 2003. including the Tivoli Provisioning Manager application itself.1.

Table 1. Product components Component Application server: WebSphere Application Server ® Description Tivoli Provisioning Manager is a Web-based application that uses WebSphere Application Server as the application server. replication. Tivoli Provisioning Manager for OS Deployment is a component used for operating system provisioning. either the custom installation is supported only. this component acts as a federated server that manages job distribution. Also called the device manager service. Tivoli Provisioning Manager for Dynamic Content Delivery management center Tivoli Provisioning Manager for Job Management Service federator The agent manager Tivoli Provisioning Manager for Dynamic Content Delivery management center provides centralized control of the uploading. The database server hosts the provisioning database. and provides secure connections with managed computers on which the common agent is installed. It pushes incoming jobs to all of the endpoint agents or regional agents. It also monitors the state of depot servers in distributed locations and stores file data. or use an existing version of DB2 from your system. The Tivoli Monitoring agent is a component that lets you monitor the provisioning server. 2 IBM Tivoli Provisioning Manager Version 7. which includes the data model of managed assets.Product components Tivoli Provisioning Manager includes components that provide specific capability.2 Installation Guide . After the initial deployment. the administrative workstation is used to make updates or changes to the deployment and add additional process manager applications. you must obtain your own Microsoft Active Directory and install it before installing Tivoli Provisioning Manager. HTTP server: IBM® HTTP Server Database server: v DB2® Directory server: Tivoli Directory Server or Microsoft Active Directory The directory server provides user authentication and access control. and downloading of files. The agent manager is the server component of the Tivoli Common Agent Services. dedicated HTTP server that can be configured to work with the application server. The Tivoli Provisioning Manager web components are a set of applications specific to provisioning. you can either install it as part of the Tivoli Provisioning Manager installation. Tivoli Provisioning Manager uses the Tivoli Common Agent Services for software distribution and compliance. which can only be done from the administrative workstation. Changes to the deployment typically require that the product Enterprise Archive (EAR) files be rebuilt. or both a custom and default installation are supported. It provides operating system management capability including deployment of captured images and unattended setup. or use an existing version of Tivoli Directory Server from your system. you can either install it as part of the Tivoli Provisioning Manager installation. v If you want to use DB2. It also stores the Maximo® database which contains text for the user interface and field-level help. The HTTP server is a separate. v If you want to use Microsoft Active Directory. v If you want to use Tivoli Directory Server. Tivoli Provisioning Manager for OS Deployment Tivoli Monitoring agent Administrative workstation Web components Installation types Depending on the operating system. The administrative workstation is used to deploy Tivoli Provisioning Manager.

d. DB2. Default For a default installation. The middleware for a default installation is Tivoli Directory Server. see Chapter 2. b. directory server. it is important to understand the differences between them. All components are installed on a single computer. Installation overview 3 . proceed to “Installing Tivoli Provisioning Manager with default values” on page 205. 1. e. and WebSphere Application Server. Install Tivoli Provisioning Manager core components on the same computer as the application server. and port numbers. “Preinstallation tasks. To help you choose your installation type. see Chapter 4. install components in the following order: a. Install the middleware. evaluation. installation directories. see Chapter 3. Perform required post-installation tasks. or as a learning environment. or WebSphere Application Server for you. For more information. the installation of the software. 3. Allows you to customize settings such as user names. Tivoli Directory Server. Verify that you meet all the prerequisites for installation.” on page 25. The database server and the directory server can be installed on separate computers.” on page 131. English language installation only. Custom Default XML For more information about the custom installation. You cannot use an existing database server. v You can use middleware that is already installed: – WebSphere Application Server – DB2 – Oracle – Tivoli Directory Server or Microsoft Active Directory v The middleware installer can install DB2. If you are using existing middleware. For more information.Tivoli Provisioning Manager offers two installation options: a default and a custom one. Custom installation For managing production enterprise assets and processes. Default and custom installations are supported on Windows The following table compares default and custom installations to help you plan your installation: Table 2. Install the base services. or application server. c. Chapter 1. and post-installation tasks. Install the language pack on the same computer as the base services. it must be installed and configured as required. Install Tivoli Provisioning Manager web components on the same computer as the base services. 2. Includes Tivoli Provisioning Manager runtime in languages other than English. Start the launchpad to install the product. or testing purposes. “Installing Tivoli Provisioning Manager. Default versus custom installation Default installation For demonstration. “Post-installation tasks. Installation process These steps describe the preinstallation tasks. Installs Tivoli Provisioning Manager with default settings.” on page 5. Other supported middleware programs must be preinstalled and configured manually. For a custom installation.

2 Installation Guide .4 IBM Tivoli Provisioning Manager Version 7.

Verify user requirements 8. Run the prerequisites scanner 2. 1. Preinstallation steps for new installation If the provisioning server does not have Internet access. For more information. Verify component requirements 6. Read the release notes 3. Prepare installation media Ready for installation Figure 1. you must manually install Cygwin. Plan the topology 4. Allocate the appropriate hardware 5.Chapter 2. © Copyright IBM Corp. Preinstallation tasks Before starting the Tivoli Provisioning Manager installation. 2003. verify that your environment meets the requirements. 2010 5 . Verify the environment 7. see “Installing Cygwin manually” on page 208.

COZ" detail prereq_checker.tar or . This type of deployment is typical for production use within an enterprise. For more information about the latest documentation updates. see Tivoli Provisioning Manager Version 7. depending on your operating system.2 Release Notes. complete the tasks from “Preinstallation Step 5: Verify component requirements” on page 12 to “Preinstallation Step 8: Prepare installation media” on page 23 to resolve the problems before starting the installation. Review the output of the prerequisites scanner stored in the result.zip or . and process managers.ibm. Prerequisites scanner syntax Operating system and hardware 2008 2003 Syntax prereq_checker. Extract the prerequisites scanner from the .bat "COX. onto one server. This is typically used for evaluation purposes. the detail parameter specifies that the results of the prerequisites scanned are displayed on the console.Preinstallation Step 1: Run the prerequisites scanner To automatically verify if your environment meets the Tivoli Provisioning Manager installation requirements. operating system version. as a demonstration. and hardware. Preinstallation Step 3: Plan the topology Use this information to determine the best deployment option for your environment and business needs. This is beneficial because it optimizes resource use and decreases the workload on each server. 6 IBM Tivoli Provisioning Manager Version 7. the administrative workstation. Download the prerequisites scanner from the Integrated Service Management Library at http://www-01. For managing enterprise assets and processes.label=1TW10OT10. or as a learning environment.com/software/brandcatalog/ismlibrary/details?catalog. 2. Preinstallation Step 2: Read the release notes Before starting the installation.COZ" detail Microsoft Windows Server 2008 Microsoft Windows Server 2003 In the command.2 Installation Guide .txt file. There are two primary deployment strategies: Single-server The single-server topology consists of loading all runtime components. Run the command from the directory where you extracted the . use the prerequisites scanner. you would typically implement a multiserver topology.bat "COY. 4.tar file. see the latest documentation updates in the release notes for important information. What to do next If the results of the prerequisites scanner indicate failures. including all middleware. 3. Procedure 1. Table 3.zip file. Run the prerequisites scanner using the following command. Multiserver The multiserver topology consists of splitting components across several different servers.

Chapter 2. and then gradually move towards a pilot multiserver environment before finally implementing a production deployment within the enterprise. Single-server deployment A single-server deployment is frequently used as an evaluation. Provisioning server . For details about the supported installation platforms for product components. functional proof-of-concept.Base services . Preinstallation tasks 7 .Database server . and testing integration within the existing environment. but it is not required during operation of the product. The deployment software is used to install or update the product. The following figure shows a deployment with all the Tivoli Provisioning Manager runtime components on one server and a separate server being the administrative workstation. Administrative workstation The software that deploys the Tivoli Provisioning Manager support component. see “Preinstallation Step 5: Verify component requirements” on page 12. educational. This topology is used for a default installation.A typical deployment process might begin with a single-server topology that would move through phases of demonstration.Core components .Application server . or demonstration configuration.Web components You can install all components on a single server if you are using one of the following operating systems: v Microsoft Windows Server 2008 R2 Enterprise Edition (x86 64-bit) v Microsoft Windows Server 2008 R2 Standard Edition (x86 64-bit) v v v v v Microsoft Microsoft Microsoft Microsoft Microsoft Windows Windows Windows Windows Windows Server Server Server Server Server 2008 2008 2008 2003 2003 Datacenter Edition (x86 64-bit) Enterprise Edition (x86 64-bit) Standard Edition (x86 64-bit) R2 Enterprise Edition SP2 (x86 64-bit) R2 Standard Edition SP2 (x86 64-bit) v Microsoft Windows Server 2003 Standard Edition SP2 (x86 64-bit) v Microsoft Windows Server 2003 Enterprise Edition SP2 (x86 64-bit) The administrative workstation must be a separate server if the provisioning server is installed on a platform that is not supported by the deployment software for the base services and web components.Directory server . where all components are installed on a single server with default values.

2 Installation Guide . Deployment on multiple servers is only available for a custom installation. The following deployments are supported depending on the operating system.Base services .Web components Administrative workstation . and availability. In a disparate environment.Core components . but it is not required during the operation of the product.Database server . If you plan to reuse or migrate resources that already exist in your network. Tivoli Provisioning Manager has been deployed on a collection of systems.Core components . components for Tivoli Provisioning Manager are installed on separate systems to promote load balancing. Components can also be grouped logically and installed on the same system.Base services .Application server . Installing all new components using the middleware and Tivoli Provisioning Manager installation programs simplifies the deployment. When planning your deployment strategy. redundancy.Application server . reuse. determine if it will include systems that are already established in your network.Provisioning server . the collection of servers can be a mixture of Windows and UNIX servers. The administrative workstation is used to install or update the product.Deployment directory In this figure. 8 IBM Tivoli Provisioning Manager Version 7.Deployment directory Multiserver deployment Custom Default XML Deployment on multiple servers is the recommended deployment topology for a production environment. security. Directory server Database server Provisioning server . make adjustments to your rollout plan to allow time for bringing the existing resources to versions that are compatible with Tivoli Provisioning Manager.Web components Administrative workstation .Directory server . In the following figure.

For example. see the documentation provided with that product. For information about specific platforms for which Tivoli Directory Server 6. you might have a database instance in an existing database server.2.10 is supported. The middleware and installation programs do not provide a mechanism for patching servers at previous version levels. Preinstallation Step 4: Allocate appropriate hardware Hardware requirements depend on usage. v The directory server. The following middleware can be reused: Can be automatically configured DB2 9. Supported topologies for the administrative workstation when Windows is installed on the provisioning server Platform used for the provisioning server Windows . This must be on a separate computer if the provisioning server is installed on a platform that is not supported by the deployment software for the base services and web components.1.Table 4.0. Oracle Database (if supported). If you plan to reuse existing middleware.any supported platform Separate server: any supported Windows platform Separate server: AIX® 6. see “Reusing middleware using the middleware installer” on page 45. Reusing middleware You can reuse existing middleware as Tivoli Provisioning Manager components.0. redundancy measures. which already has established access policies. For information about reusing middleware. and backup plans in place. Preinstallation tasks 9 .0. Must be manually installed and configured IBM WebSphere Application Server. For more information. v The administrative workstation. nor do these programs provide remote prerequisite checks to ensure that they are at the correct level. and Microsoft Active Directory. see “Preinstallation Step 5: Verify component requirements” on page 12.1. ensure that they are at the level supported by Tivoli Provisioning Manager. see “Using manually configured middleware” on page 49.1 TL3 (IBM System p® 64-bit) Separate server: SUSE Linux(r) Enterprise Server 10 SP3 (x86 64-bit) Separate server: Red Hat Enterprise Linux 5 Update 4 (x86 64-bit) Same server Supported multiserver topologies The following components can be on a separate server: v The database server. For hardware requirements for software that is not listed in this section.4 GHz x86 64-bit or AMD64 processor Chapter 2.2 and 6.5 FP3a and Tivoli Directory Server 6. Processor requirements for the provisioning server v 2.10.

Minimum memory requirements for single and multiserver topology Single-server topology 8 GB RAM Multiserver topology DB2 server 4 GB RAM WebSphere Application Server Network Deployment 6 GB RAM Tivoli Directory Server 2 GB RAM Administrative workstation requirements v 2 GHz processor (minimum) v 2 GB RAM (minimum) v 10 Mbit/s network connection between administrative system and middleware servers (minimum) Note: The deployment engine used by the base services is always installed in the Windows system root directory of the administrative workstation. Table 6.5 GB Directory user-specified location Required free space 12 GB 10 IBM Tivoli Provisioning Manager Version 7. Disk space The following table details the disk space that must be allocated to each directory for the installation process. you can create soft links for the following directories to a local file system with correct lock management support: v TIO_HOME/lwi/conf v TIO_HOME/lwi/logs Windows disk space requirements Ensure that you have 60 GB of available space on disk C:\. you must ensure that the parent directory of these directories has sufficient space available for the installation. as detailed in the following table. Disk space requirements for Windows Component Installation images Administrative workstation Base services deployment directory Base services language pack System temporary directory C:\ibm\SMP C:\ibm\SMP %TEMP% 5 GB 100 MB 2. Network file systems: Tivoli Provisioning Manager includes a lightweight infrastructure run time that uses file system locking to manage concurrency. These lock files are managed in the lightweight infrastructure installation directory under the TIO_HOME directory in the file system. Because these directories do not exist before installation. If this type of lock support is unavailable. C:\program files\ibm\acsi. if the primary computer fails and is no longer available. in a high availability disaster recovery configuration.Minimum memory requirements Table 5. If you are installing Tivoli Provisioning Manager on a network file system. For example. the file system must be able to automatically unlock all the locks associated with the primary computer. regardless of the directory specified during the installation.2 Installation Guide . by default. ensure that the file system has adequate lock management support. Ensure that permissions are set to allow the deployment engine to be installed in the Windows root directory.

a total of 6 GB is required. Default Directory Required free space Temporary space for the middleware Temporary space for the software installer Default user-specified location (the default value is %TEMP%) user-specified location (the default value is %TEMP%) %TEMP% 1 GB 6 GB 2. Disk space requirements for Windows (continued) Component Temporary space If you use the system temporary directory (%TEMP%) for all three types of temporary space.Table 6.5 GB repository System temporary directory Installation components Cygwin GSK toolkit Tivoli Provisioning Manager Tivoli Monitoring agent Tivoli Provisioning Manager for OS Deployment C:\Cygwin C:\ibm\gsk7 C:\Program Files\IBM\tivoli\tpm C:\ibm\tivoli\ITM C:\Program Files\IBM\TPMfOSd C:\Program Files\Common Files\IBM Tivoli 200 MB 10 MB 6 GB 250 MB 5 MB 150 MB 150 MB 100 MB 200 MB 150 MB 100 MB 1 GB 10 GB 1. Otherwise. including common logs 2000 DB2 2000 DB2 2000 DB2 C:\Program Files\IBM\tivoli\CDS C:\Program Files\IBM\tivoli\common\COP\logs SystemDrive:\Program Files\IBM\SQLLIB C:\CTGINST1 SystemDrive:\Program Files\IBM\SQLLIB DB2 server DB2 database instance Custom Default XML DB2 client (for multiserver deployment) Tivoli Directory Server Tivoli Directory Server database Files for the Tivoli Directory Server database WebSphere Application Server IBM HTTP Server Files for the middleware installer Solution installer used by the middleware installer and the base services installer Common Tivoli files IBM JRE Default C:\Program Files\IBM\LDAP\V6.5 GB Tivoli Provisioning Manager for OS Deployment data directory The agent manager C:\tpmfosd C:\Program Files\IBM\AgentManager Tivoli Provisioning Manager for Job Management C:\Program Files\IBM\DeviceManager Service federator Tivoli Provisioning Manager for Dynamic Content Delivery Common Tivoli files. Preinstallation tasks 11 . ensure that you have enough space in each of the temporary locations.2 C:\IDSCCMDB C:\idslap-idsccmdb C:\Program Files\IBM\WebSphere\AppServer C:\Program Files\IBM\HTTPServer C:\ibm\tivoli\mwi C:\Program Files\IBM\Common\acsi C:\Program Files\tivoli C:\Program Files\IBM\Java50 450 MB 900 MB 1 MB 4 GB 1.1 GB 100 MB 400 MB 25 MB 250 MB 2 GB Back up files for a default installation C:\backup Chapter 2.

2 only 6.0.5. so that performance is not affected by other applications that are accessing the same device.29 Directory server Operating system and platform Microsoft Windows Server 2008 R2 Enterprise Edition (x86 64-bit) Microsoft Windows Server 2008 R2 Standard Edition (x86 64-bit) Microsoft Windows Server 2008 Datacenter Edition (x86 64-bit) Microsoft Windows Server 2008 Enterprise Edition (x86 64-bit) Microsoft Windows Server 2008 Standard Edition (x86 64-bit) Microsoft Windows Server 2003 R2 Enterprise Edition SP2 (x86 64-bit) Microsoft Windows Server 2003 R2 Standard Edition SP2 (x86 64-bit) DB2 9.0.5 FP3a Oracle Database IBM Tivoli Directory Server 6. Ensure that you meet the requirements for all the product components.0.0.2 only Microsoft Active Directory 2003 SP2 Administrative workstation 12 IBM Tivoli Provisioning Manager Version 7.10 or later is required on the provisioning server.0.2 only 6.2.2 only 6. Supported operating systems and middleware combinations This section outlines the middleware combinations with the supported operating systems and versions. The Tivoli Provisioning Manager software is installed on the same computer as the application server. installation of Tivoli Provisioning Manager in a XEN environment is not supported.2. Preinstallation Step 5: Verify component requirements Tivoli Provisioning Manager contains a number of components and products that work together.0.2. dedicated storage device.2. If you are using a multiserver topology.Table 6.0.2.0.1. The required disk space depends on various factors. Disk space requirements for Windows (continued) Component Note: v You might require more space on File Allocation Table (FAT) drives with large cluster sizes than with New Technology File System (NTFS) drives. Because Cygwin cannot be installed correctly in a XEN environment. Directory Required free space DVD drive If you are using DVDs to install the product. ensure that you verify the component requirements on each computer in the topology.2 only 6.2 only 6.2 6.1.2. allocate 50 GB of free disk space. v Plan for additional disk space for database growth.2.10 or 6. v “Supported operating systems and middleware combinations for Windows” Supported operating systems and middleware combinations for Windows Note: Cygwin 1. Consider storing the database on a separate. For example. Database Application server IBM WebSphere Application Server Network Deployment 6. if you are managing 50000 targets.2 Installation Guide . You can install Cygwin either as part of the Tivoli Provisioning Manager installation or manually before installing Tivoli Provisioning Manager. each computer in your topology must have a DVD drive.2 only 6.0. including the configuration of the database and the number of managed target computers.2.0.

Because Cygwin cannot be installed correctly in a XEN environment. You can install Cygwin either as part of the Tivoli Provisioning Manager installation or manually before installing Tivoli Provisioning Manager. Remote Registry: Ensure that this service is enabled. Windows Scripting Host is installed.0. Otherwise. Click Add or Remove Programs and Click Add/Remove Windows Components. If Terminal Server is installed.2 Microsoft Active Directory 2003 SP2 Administrative workstation Operating system preinstallation tasks Before installation. click Make a file type always open in a specific program. 2. 2003 Check if Terminal Server is installed and verify its settings 1. Preinstallation tasks 13 . 3.2.Note: Cygwin 1. 4.0. run fsutil behavior set disable8dot3 0 Check requirements for Windows services From the Control Panel.5. DNS Client: Disable this service so that host names are not cached and are always resolved by a DNS server with current IP addresses. open the Services panel and check the following services: 1.3 file format is enabled 1. Click Start > Control Panel. Open a command prompt and run the command: change user /install Check Windows Scripting Host By default. Database Application server IBM WebSphere Application Server Network Deployment 6. Under Default Programs. Windows Management Instrumentation: Ensure that this service is started. then the 8. If the output is disable8dot3 = 0.10 or later is required on the provisioning server. perform the following tasks depending on your operating system. In the list. Windows preinstallation tasks Verify that the 8. Open a command prompt window and run fsutil behavior query disable8dot3 2. Click Programs.3 file format is enabled. installation of Tivoli Provisioning Manager in a XEN environment is not supported. 3. configure Terminal Server to install mode.29 Directory server Operating system and platform Microsoft Windows Server 2003 Enterprise Edition SP2 (x86 64-bit) Microsoft Windows Server 2003 Standard Edition SP2 (x86 64-bit) DB2 9.10 or 6. 3. To check if Windows Scripting Host is enabled: 1. 2008 2.0. Click Start > Control Panel.1.1. Chapter 2.5 FP3a Oracle Database IBM Tivoli Directory Server 6. verify that Terminal Server is installed. 2.

5. otherwise the installation might fail. Under NetBIOS setting. Under NetBIOS setting. 3. select Default. To 1. Right-click Local area connection and click Properties. some Windows updates require a reboot of the provisioning server. Verify required user rights When installing WebSphere Application Server and DB2 on Windows 2003 and later operating systems. 2. If you do not disable them. you can enable the built-in Administrator account and use it to connect: From the Control Panel. 1. Click the File Types tab and verify that VBS VBScript script file is listed as a file type. click View network status and tasks. Click Advanced and click the WINS tab. 14 IBM Tivoli Provisioning Manager Version 7. In the list. Click Advanced and click the WINS tab. You must add the Administrator account to the following required rights: v Act as part of the operating system v Create token object v Lock pages in memory v Log on as a service v Adjust memory quotas for a process v Replace a process level token Disable automatic updates By default. select Default. the Windows automatic updates are enabled. click Manage network connections. 4. verify that NetBIOS is enabled: 2008 Click Start > Control Panel. 2.4. 6. Right-click the local area connection.2 Installation Guide . 2003 From the Control Panel. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. 4. click Tools > Folder Options. see your Microsoft Windows documentation. If you are a member of a local administrators group and you use a local user account. you must uninstall it before you start the installation. Verify that NetBIOS is enabled NetBIOS must be enabled because the Tivoli Provisioning Manager computer has a static IP address. Under Network and Internet. 5. select Internet Protocol (TCP/IP) and click Properties. open the Network Connections panel. verify that VBS VBScript script file is listed as a file type. the user who installs the product must be a member of administrators group and also have administrative permissions. For information about disabling Windows updates. click Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment. 2. In Windows Explorer. and then click Properties. 2008 Uninstall Global Secure ToolKit If Global Secure ToolKit (GSKit) is installed on your system. which might cause the Tivoli Provisioning Manager installation to fail. In the list. 3. 7. Under Tasks. 2003 1.

Ensure that you meet the browser requirements. and Linux. as part of the middleware installation. Note: You can remove the browser and the associated packages after the installation is completed. v You must obtain your own Microsoft Active Directory installation media and install it before installing Tivoli Provisioning Manager. Database server requirements DB2 is supported on Windows.5 FP3a If you are planning to use DB2 as your database. run: firefox -version Ensure that the command returns no errors before starting the installation. 2000 DB2 DB2 Enterprise Server 9.0 or 7. Preinstallation tasks 15 . you must perform the steps in “Changing user passwords” on page 219 before attempting to change user passwords. v Before installing and setting up your Microsoft Active Directory system. review the following information: v To meet the table space disk space requirements for the DB2 installation.Database and directory server requirements Ensure that you meet the requirements for your operating system or database before installing Tivoli Provisioning Manager. Browser requirements Tivoli Provisioning Manager requires a browser to run the installation launchpad and the web interface. To verify the Mozilla Firefox version.0 and higher. and you do not have corporate password change procedures already in place. ensure that you have a minimum of 8 GB of free space in the DB2 installation directory. review the following information: v Microsoft Active Directory Application Mode (ADAM) is not supported. review the following information: v Depending on the operating system. The following web browsers are supported: v Microsoft Internet Explorer version 6. Microsoft Windows Server 2003 Active Directory If you are planning to use Microsoft Windows Server 2003 Active Directory as your directory server. Tivoli Directory Server can be installed either automatically.0 with the latest patch. Tivoli Directory Server If you are planning to use Tivoli Directory Server as your directory server. Oracle Database is supported on UNIX and Linux. Directory server requirements Either Tivoli Directory Server or Microsoft Windows Server 2003 Active Directory are supported as directory server. or must be installed manually. ensure that you meet all requirements. UNIX. as detailed in the Microsoft Active Directory documentation. v If you are installing a new Tivoli Directory Server. v Mozilla Firefox 3. Chapter 2.

2008 1. b. example.example. 2) In the System Properties dialog box. For example.Preinstallation Step 6: Verify the environment Verify rules for host names. 6. the fully qualified domain name is river.com. if the host name is river and the domain name is example. mycomputer. Resolving host names with a DNS server If you are using a DNS server to resolve host names.com. complete the following steps: 1) Click Change Settings. Under Network and Internet. c. remote network connections. contact your system administrator. click View network status and tasks. 2. Change the suffix if necessary. A dynamic IP address is not supported for the provisioning server. domain. 3) Verify that the Computer name field displays the correct host name. Also. Right-click the LAN connection that represents your network adapter and click Properties. This value is case-sensitive. 4. mycomputer. and other environment requirements.com. 2003 Verify the computer name information: 3. Under Tasks. Ensure that Use the following IP address is selected and enter the IP address that you are using for the provisioning server. click Manage network connections.2 Installation Guide . contact your network or system administrator. the host name must be configured on the DNS server. v A static IP address must be configured. Select Internet Protocol (TCP/IP) and click Properties. If you do not know how to set a static IP address. 2. verify that Full computer name displays the fully qualified domain name of the computer. Ensure that Use the following IP address is selected and enter the IP address that you are using for the provisioning server. 3. verify that the Primary DNS suffix of this computer field displays the correct domain name suffix. For example. the host name configured on the DNS server must match the host name configured in the operating system. 5) In the DNS Suffix and NetBIOS Computer Name dialog box. Under Computer name. To configure a static IP address: Click Start > Control Panel > Network Connections. For example mycomputer. and workgroup settings. Click Start > Control Panel > System and Maintenance > System. Check the host name configured in the operating system. To verify that the host names match. This value is case-sensitive. For example. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.com. Change the name if necessary. 3. If you need to modify the name. 4) Click More. To configure a static IP address: Click Start > Control Panel. If you do not know the IP address. IP addresses. Right-click Local area connection and click Properties.example. 5. click Change. 2. 2003 1. for example. Host names and IP addresses The following requirements apply to host names: v A fully qualified domain name must be configured. ports. complete the following steps: 1. Run the following command: hostname The command returns the short host name for the computer. 16 IBM Tivoli Provisioning Manager Version 7. 4. 2008 Verify the computer name information: a.

Click OK. Click Start > Control Panel. For example mycomputer. ensure that the domain name is listed at the top of the list of DNS suffixes. and then click Properties. Click Advanced. there might be a problem with the format of your hosts file. g. Under Network and Internet. click Manage network connections. e. d. mycomputer. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. If Append these DNS suffixes is selected. Click the Computer Name tab. 3) Click More. h. e. If you receive an error. c. If the domain name is not included in the list. h. 4.com. g. verify that the Computer name field displays the correct host name. complete the following steps: 1) Click Change.example. example. b. Chapter 2. and host name of the computer where you are running the installer as the first entry. in the order that is specified: v The IP address. f. the file must be configured correctly. 2008 If the nslookup command does not return the correct domain name. 2003 If the nslookup command does not return the correct domain name. ensure that your 5. If Append these DNS suffixes (in order) is selected. If you need to modify the name. Select Internet Protocol (TCP/IP) and then click Properties. verify that the Primary DNS suffix of this computer field displays the correct domain name suffix. For example.com. 2) In the Computer Name Changes window. d. f.com. mycomputer. network connection is correctly configured to resolve domain names: a. ensure that the domain name is listed at the top of the list of DNS suffixes. Right-click Local area connection and click Properties. d.example. click Add to add the domain name and click the up arrow button to position it at the top of the list. for example. click View network status and tasks. Right-click the local area connection. The file is typically located in: v C:\WINDOWS\system32\drivers\etc\hosts Verify that you can run the command ping localhost successfully. Check the host name configured on the DNS server. Verify that the Full computer name field displays the fully qualified domain name of the computer. b. Change the name if necessary. Click the DNS tab. fully qualified domain name. Resolving host names with a hosts file If you are using a hosts file to resolve IP addresses. Run the following command: nslookup host_name where host_name is the short host name returned in the previous step. c. Click the DNS tab. The file must include the following information. Preinstallation tasks 17 . network connection is correctly configured to resolve domain names: a. Under Tasks. 4) In the DNS Suffix and NetBIOS Computer Name dialog box. c.a. ensure that your 6. i. Change the suffix if necessary. b. The nslookup command returns the fully qualified domain name configured on the DNS server. Click Advanced. Right-click My Computer and click Properties. For example. click Add to add the domain name and click the up arrow icon to position it at the top of the list. If the domain name is not included in the list. Click Start > Settings > Control Panel > Network Connections.

v To ensure correct operation. Networking requirements If you want to support IPv6 addressing in Tivoli Provisioning Manager. Network media speed settings 1.1. For example.2 Installation Guide . v Cygwin SSH is not supported. v The remote access protocol must be SMB.v The IP address 127. the base services installation uses Remote Execution and Access (RXA) to configure middleware. the file content is like the following example: #IP address 10. If Cygwin is installed on a remote Windows computer. ports 137 (NetBIOS name service) and 139 (NetBIOS session) must not be blocked. for a computer with the host name river. At a command prompt. Cygwin 1. Port requirements Verify dynamic port allocation: 1. set the Link Speed & Duplex option. To stop SSH.0. 2.example.localdomain. and the host name localhost. Contact your system administrator to set the option to the correct value. In a remote configuration.msc from the Start > Run menu.0. Ensure that the following services are started: – Computer Browser. run: cygrunsrv --stop sshd v If you are using a firewall. Under the Advanced tab.0.1 Fully Qualified Domain Name river. RXA requires access to the Interprocess Communications share (IPC$). Right-click Network adapters and click Properties.com localhost.localdomain Short Name river localhost Remote configuration for multiserver topologies If you are using a multiserver topology. accessing network drives on the local or remote system is not supported. to access %TEMP% and other directories. – File and Printer Sharing for Microsoft Networks.0. 2. To do this: 1. Ensure that the default protocols are enabled: – Client for Microsoft Networks or the server equivalent. To access remote registries. v You must use a user name with administrative access to connect to the computer. To use RXA. – Routing and Remote Access.0. Click Start > Control Panel > Administrative Services > Services. run: netsh int ipv4 show dynamicport tcp netsh int ipv4 show dynamicport udp 2008 18 IBM Tivoli Provisioning Manager Version 7.7 or later must be installed. Open the device manager by running the command devmgmt. the fully qualified domain name localhost.0. the SSH daemon must be stopped. a supported remote access protocol must be enabled on each computer on which you are installing middleware and an administrative user must be configured on each computer for remote access.12 127. RXA requires access to the hidden remote administrative disk share. 3.

change the starting port value by running: netsh int <ipv4|ipv6> set dynamic <tcp|udp> start=number num=range where number is the starting port number and range is the total number of ports.1.0.10000 are listed. because the ports in this range are used by WebSphere Application Server. Table 7. In the output.1.1 NBPServer NetBIOS name service UDP TCP 4012 137 ← ← → any 137 Used during installation. check the starting port value.1 DCHP REPLY DHCP REQUEST Directory server admin daemon port Directory server admin daemon secure port Directory server port Directory server secure port Eclipse embedded database FASTPort FileServerPort FileMCAST-Address HTTPServer MTFTPPort MTFTPClients UDP UDP (multicast) TCP UDP UDP UDP UDP UDP (broadcast) 67 67 3538 3539 389 636 1527 4025 4013 any 80 (9080) 4015 any ← → any 8500 IP:233. The ports listed in the following table must be available.0. PROXY DHCP UDP 4011 ← any ← ← ← → any any any 10000 → ← 68 any Direction ← ← Managed computer port any any Chapter 2. Preinstallation tasks 19 . In multiserver topologies. Note: A PING command issued from the administrative workstation during installation must receive a response from each server involved in the deployment. In the Direction column the arrow points from the source port to the destination port. 9512.netsh interface ipv4 show dynamicportrange tcp 2. Ensure that you do not set the starting port number to a value in the range from 8800 to 10000. If port numbers in the range 8800 . enable the port on a remote database server or remote directory server. Communication ports used by Tivoli Provisioning Manager. Ensure that each middleware host server is configured to respond to PING requests. 9513 4011 IP:233. Usage The agent manager BootDiscovery Protocol TCP UDP (multicast) Provisioning server port 9511.

9045. 2. 9046. In the file /etc/ssh/sshd_config.html. run: ps -ef | grep sshd If SSH is running. As an example.com/systems/power/software/aix/linux/ toolbox/download. The file /etc/ssh/sshd_config exists. Add JAVA_COMPILER=NONE to /etc/environment on the system. Using an X session 1. root access is permitted by the SSH daemon (sshd). SMB/NetBIOS SNMP SNMP-TRAP SSH Telnet TFTP TS WebSphere Application Server WebSphere Application Server SOAP port WebSphere Application Server Administrative Console secure port WebSphere Application Server Administrative Console Web Server port 2000 DB2 TCP UDP UDP TCP TCP UDP TCP TCP any any 162 any 23 69 any 8881./launchpad. 9061 9430 50005 DB2 instance port SSH requirements 1. Install the package by running the command: 20 IBM Tivoli Provisioning Manager Version 7. This file contains SSH configuration settings that are used to validate other SSH requirements for installation. 3. Ensure JAVA_HOME is not set in the environment. 2.Table 7. 9044 → → ← → ← ← → ← 445 161 any 22 any any 3389 any 9060. POWER7® 1. Start the launchpad using: cd /usr/IBM/source/install JAVA_COMPILER=NONE . ensure that the PermitRootLogin line is not commented out and that the value for this setting is yes. To check the status of SSH.ibm. 3. an entry for /usr/sbin/sshd is displayed. 2. SSH must be running to perform installation. remove /usr/java5/jre/bin:/usr/java5/bin from the path. Download the VNC package from http://www-03. 9443 8879 9043. Communication ports used by Tivoli Provisioning Manager (continued). 4.2 Installation Guide .sh Note: The DB2 shipped with the middleware installer is not supported on Power7. In the Direction column the arrow points from the source port to the destination port. 9082. Edit the $PATH environment variable to remove any directories containing a JRE.

Go to http://host_name:5801. For example. database names. Install a VNC client. “Uninstalling Tivoli Provisioning Manager. Chapter 2. Stop or reschedule these processes before starting the installation. Preinstallation Step 7: Verify requirements for user names. and names for DB2 objects such as database instances. see Chapter 5.log. These processes can cause some installation operations to time out. 3. VNC prompts you for the password for a VNC connection. and underscore (_). Set the geometry option so that the size of the VNC window is appropriate for your current display settings and video card. Run the VNC client and enter: host_name:port_number where host_name is the host name of the AIX computer. You might need to adjust the color depth and resolution with the depth and geometry options.vnc/host_name:display_number. The following command sets color depth to 24-bit and resolution to 1280 by 1024: /usr/bin/X11/vncserver -depth 24 -geometry 1280x1024 To connect to the VNC desktop from a Windows computer: v Using HTTP: 1. Antivirus software or process-intensive software Check the computers in your installation topology for processes that consume many system resources. Firefox requires a 24-bit color depth or a greater color depth. names can only contain English alphanumeric characters or the following characters: period (.). and user passwords The following general rules apply to all user names. such as a scheduled thorough antivirus scan. You can also access VNC desktop using other VNC clients. Reinstalling Tivoli Provisioning Manager You must uninstall Tivoli Provisioning Manager completely before attempting to install again. user passwords. database names.rpm -ivh package_name where package_name is the name of the package that you downloaded. and user passwords Verify requirements for user names. hyphen (-). Preinstallation tasks 21 .” on page 139. You can find the port number in $HOME/. 2. database names. 2000 DB2 The following additional restrictions on user names apply: v – Names cannot begin with a number or with the underscore (_) character. Log on as the user that connects to VNC. User names The following restrictions apply to characters in a user name: v Unless otherwise stated in other rules in this section. A lower color depth might cause browser failures. General requirements for user names. Start the VNC server. v Using VNC client: 1. and user passwords. For more information. database and database instance names. The default port number for the connection is 5801. 4. at sign (@).

– Cannot include special characters @. and mixed-case. v Do not use a period (. GUESTS. #. – Cannot begin with any of the following values: IBM. non-Windows 32-bit clients connecting to Windows with user names longer than 8 bytes are supported when the user name and password are specified explicitly. LOCAL. PUBLIC. or SYS. v Instance names cannot contain the # character. 22 IBM Tivoli Provisioning Manager Version 7.Begin with IBM. . the rules for user names and group names apply. Tivoli Directory Server database and instance names v Database names must be unique within the location in which they are cataloged.a through z User passwords Some restrictions apply to passwords that you can use.Be USERS. GUESTS. v Database and instance names: – Can have up to 8 bytes.Group names and user names can contain up to 30 bytes. – Cannot be any of the following values: USERS.A through Z . hyphen (-). or any SQL reserved word.A through Z .Names can be in upper. and underscore (_). – Cannot include accented characters.When not using Client authentication. In addition: DB2 database instance v Instance names can have up to 8 bytes.– You cannot use SQL reserved words. ADMINS. This location is: – A logical disk.) if it is at the end of the password. lower.0 through 9 – Must begin with one of the following characters: . . do not use them if you plan to use the database in another language.2 Installation Guide . v No instance can have the same name as a service name. LOCAL. PUBLIC. . v Database alias names must be unique within the system database directory. idsldap. – User and group names cannot: . you cannot create a database using a name that exists as a database alias. – . – Can include the following characters: . the alias defaults to the database name. SYS. v Database and database alias names can have up to 8 bytes. – User and group names must also follow the rules forced on specific operating systems by the related systems. As a result. Database and database instance names For instance names. SQL. even if there is no database with that name. SQL. Verify the following requirements: v Passwords can only contain English alphanumeric characters or the following characters: period (. When a new database is created. ADMINS.). and $ if you intend to use the database in a communications environment.a through z . Because these characters are not common to all keyboards.

If using downloaded installation images Procedure 1. Download all installation images into a single directory on the provisioning server. For more information. As a licensed customer. a user with administrator access is required to start the installation.v Do not use these characters in passwords: & ^ < > " ’ ) ( | ! ? $ # % ` \ + <space character> The following rules apply to DB2 user passwords.ibm. If you are using Microsoft Active Directory. The installer can then use the configured user accounts and user settings to perform the installation. Preinstallation Step 8: Prepare installation media The Tivoli Provisioning Manager package includes installation media for Tivoli Provisioning Manager and the prerequisite software. v The installation DVDs. Domain account users defined on a directory server are not supported for the users required during installation. v 2000 DB2 Additional considerations Some security controls configured in your environment can prevent the Tivoli Provisioning Manager installer from creating the required user accounts on your system for installation. go to http://www. Download the installation images from Passport Advantage. For example: C:\install_images Chapter 2. The default Windows user Administrator has the required access. – Passwords can be a maximum of 14 bytes. v Some operating systems and databases might have more password rules.wss?rs=1015&uid=swg24026704. The user must belong to the Administrators group. the user creation process fails for the user associated with the noncompliant password. – Passwords cannot begin with an ampersand (&). Some factors include: v Permissions or access control lists configured for the computer can prevent the installer from creating users.com/support/docview. you must obtain the installation media yourself. Preinstallation tasks 23 . such as minimum length and simplicity. See your DB2 documentation for further information. creating user-related files and directories. 2. see the operating system and database documentation. or assigning permissions. If you encounter problems with user creation during installation you might need to manually create the required users to ensure compliance with all security policies and compliance with Tivoli Provisioning Manager requirements. you can get the installation media from: v The IBM Passport Advantage® web site. Note: v Microsoft Active Directory installation images are not provided. v If a password that you specify during installation does not conform to the password policy configured in your environment. v Users are created as system accounts in the operating system. Additional user requirements on Windows v In addition to the created users. For more information.

use the appropriate Middleware DVD for your operating system and hardware. Extract the contents of all installation images into the directory that you have created. v During middleware installation. 24 IBM Tivoli Provisioning Manager Version 7.3. use the appropriate Installation DVD for your operating system. You can extract the installation images in any order. Some operating systems and hardware might require more than one DVD. If using installation DVDs v To start the installation launchpad and run installers from the launchpad.2 Installation Guide . when prompted. If you have Cygwin installed. you need the Installation Supplemental DVD. when prompted. run the following command to set the appropriate permissions: chmod -R 775 extract_dir where extract_dir is the full path of the directory where you extracted the images. v During core components installation. such as installing additional Tivoli Provisioning Manager for OS Deployment servers. v Use Winzip 4. select Yes. If you get a message saying that a file is replaced by another one. use the appropriate Core Components DVD for your operating system and hardware. v For some Tivoli Provisioning Manager for OS Deployment features. You must extract the files on the computer where you are running the installer so that the files have the correct permissions.

Install web components The web components must be installed on the computer where you installed the base services. directory server. 1. 4. 2010 25 . You can use supported middleware that you have already installed or use the middleware installer to install new middleware. Custom installation steps 1. 2003. you can install support for languages other than English by installing the language pack on the same computer as the base services. and application server must be installed first. Install or reuse middleware 2. Install web components Software is installed Figure 2. 3. Installing Tivoli Provisioning Manager This topic provides information about running a custom installation.Chapter 3. Install core components The core components must be installed on the computer where you installed WebSphere Application Server during the middleware installation step. Install or reuse middleware The database server. Install base services As part of the base services installation. 2. © Copyright IBM Corp. where you can customize installation settings and use a multiserver topology. Install core components Legend Administrative workstation Provisioning server 4. The following diagram shows the high-level steps for a custom installation. Install base services 3.

install the core components. 7. install the web components.2 Installation Guide . On Computer 2. 6. 5. See Chapter 4. If you want to install all runtime components on a single computer using a different operating system. install the base services. From the launchpad. install the base services. 4. From the launchpad. 3. see “Preinstallation Step 5: Verify component requirements” on page 12. “Post-installation tasks. Start the launchpad. 4. On Computer 1. 5. Computer 1 Install DB2 Computer 2 Install Tivoli Directory Server 26 IBM Tivoli Provisioning Manager Version 7. For information about the supported operating systems. This installation scenario is only supported if you are using an operating system that supports the administrative workstation software for deploying base services and web components. start the launchpad.” on page 131 for any additional configuration that is required after installation. 2.Example deployment scenarios The following examples show the high level steps for different deployment scenarios.” on page 131 for any additional configuration that is required after installation. you are installing all product components on one computer with DB2 as the database and Tivoli Directory Server as the directory server. install the web components. On Computer 1. 6. you are doing a full installation of all product components and you want to install DB2 and Tivoli Directory Server on separate computers. You can import your middleware settings from the middleware workspace to use default values for the installation settings. from the launchpad. From the launchpad. You can import your middleware settings from the middleware workspace to use default values for the installation settings. From the launchpad. from the launchpad. you must use a separate computer for the administrative workstation. 3. Example 2: Full installation: single-server installation with a separate administrative workstation The administrative workstation software is only supported on specific operating systems. Example 3: Full installation: multiserver topology In this example. start the launchpad. On Computer 2. install the middleware. install the core components. install the middleware. See Chapter 4. Example 1: Full installation: single-server installation In this example. You can import your middleware settings from the middleware workspace on the provisioning server. 1. From the launchpad. From the launchpad. You can import your middleware settings from the middleware workspace to use default values for the installation settings. 2. “Post-installation tasks. Computer 1 Provisioning server Computer 2 Administrative workstation 1.

start the launchpad. 2.properties file on Computer 3 so that the middleware installer is aware that the database server and directory server settings are from another computer. install the web components.properties file is: v C:\ibm\tivoli\mwi\workspace b.fenced. Change machine1 settings from the directory server to machine3. 13. 14. In this example. start the launchpad. Copy your middleware settings to the next computer: a. “Post-installation tasks. 9. Create a middleware workspace in a directory location that is accessible to all computers in the topology. This is the simplest way to share the installation data for installed middleware between each computer and the various installers you run. For more information about the middleware workspace. this line for the database server: machine1. From the launchpad. You can import your middleware settings from the middleware workspace on the provisioning server. Copy the topology. 10. run the middleware installer to install Tivoli Directory Server.properties file from Computer 1 to the middleware workspace on Computer 2. install the base services. From the launchpad. the computer is a Windows computer.properties file is saved for each middleware installation that you perform on each computer. Installation tasks 27 .user=tx2fenc1 Leave the original topology. 7. From the launchpad. 4. On Computer 1. 11. In each line. For example. The default location of the topology. run the middleware installer to install WebSphere Application Server. therefore a separate administrative workstation is not required. On Computer 2. Import the middleware settings from the middleware workspace. From the launchpad. 8. 6. Copy your middleware settings to the next computer: a. 12. 1.properties file from Computer 2 to the middleware workspace on Computer 3. install the core components. On Computer 2.properties on Computer 1 and Computer 2 unchanged. Leave the topology. change machine1 to machine2. Note: If you do not use a shared location for the middleware workspace.db2. see “The middleware installer workspace” on page 34.” on page 131 for any additional configuration that is required after installation. a separate topology. Chapter 3. manually create the workspace directory. Edit the topology.DB2_SERVER_9_1_1. Copy the topology. You must manually consolidate the data into a single topology.user=tx2fenc1 Must be changed to: machine2.properties file on Computer 2 so that the middleware installer is aware that the database server settings are from another computer. From the launchpad.properties file and copy the middleware workspace to a local directory on each computer in the topology as you perform the installation.DB2_SERVER_9_1_1.Computer 3 Install WebSphere Application Server and other components.properties file on Computer 1 unchanged.db2.fenced. run the middleware installer to install DB2. On Computer 3. Edit the topology. 3. See Chapter 4. From the launchpad. WebSphere Application Server must be installed after the directory server so that you can secure it with the directory server. The default location is: v C:\ibm\tivoli\mwi\workspace 5. start the launchpad. b.

user=tx2fenc1 5. run the middleware installer to install DB2. In this example. Create a middleware workspace in a directory location that is accessible to all computers in the topology.properties on Computer 1 and Computer 2. change machine1 to machine2. From the launchpad. this computer is a Windows computer so that a separate administrative workstation is not required. Copy the topology. For example. start the launchpad. run the middleware installer to install WebSphere Application Server. 2. This is the simplest way to share the installation data for installed middleware between each computer and the various installers you run. Edit the topology.fenced. 7. On Computer 1.fenced.Example 4: Reuse an existing directory server The topology for this example is the same as the previous one. 6. 8. b.properties file on Computer 2 so that the middleware installer is aware that the database server settings are from another computer. ensure that your existing directory server is configured correctly for Tivoli Provisioning Manager.DB2_SERVER_9_1_1.properties file and copy the middleware workspace to a local directory on each computer in the topology as you perform the installation. see “The middleware installer workspace” on page 34. 3.properties file on Computer 1 unchanged. but you are using an existing directory server instead of installing a new one. On Computer 2. For more information about the middleware workspace.db2. WebSphere Application Server must be installed after the directory server so that you can secure it with the directory server. Change machine1 settings from the directory server to machine3. From the launchpad. this line for the database server: machine1. See “Verifying an existing Tivoli Directory Server with the middleware installer” on page 48. Leave the original topology. Leave the topology.db2. Copy your middleware settings to the next computer: a. Note: If you do not use a shared location for the middleware workspace.DB2_SERVER_9_1_1. start the launchpad. 1.2 Installation Guide 28 .properties file is saved for each middleware installation that you perform on each computer. Edit the topology. b. a separate topology.properties file from Computer 2 to the middleware workspace on Computer 3.properties file on Computer 3 so that the middleware installer is aware that the database server and directory server settings are from another computer. Copy your middleware settings to the next computer: a. You must manually consolidate the data into a single topology. In each line.user=tx2fenc1 Must be changed to: machine2. Copy the topology. 4.properties file from Computer 1 to the middleware workspace on Computer 2. On Computer 3. You can use the middleware installer to verify your directory server configuration. IBM Tivoli Provisioning Manager Version 7. Computer 1 Install DB2 Computer 2 Reuse an existing Tivoli Directory Server installation Computer 3 Install WebSphere Application Server and other components.

Procedure 1. See Chapter 4. 11. AIX. Installation tasks 29 . When the launchpad is running. the generated launchpad messages are captured in a hidden log frame. install the base services. 3.2 in the Tivoli Provisioning Manager wiki. “Post-installation tasks. For some examples of the installation process for Tivoli Provisioning Manager and another product in a base services environment. and Linux Before you can install Tivoli Provisioning Manager. In the launchpad. There are some limitations to compatibility considerations described in “Supported platforms and compatibility” on page 1. and all Linux operating systems except SUSE Linux Enterprise Server 11. Example 5: Install Tivoli Provisioning Manager with another product in a base services environment Tivoli Provisioning Manager is compatible with other products installed on Version 7. You can save the messages from a runtime session by clicking Save at the bottom of the log frame and specifying where you want to save the file. From the launchpad.exe (Windows 32-bit) from the root directory. Import your middleware settings from the middleware workspace on the provisioning server.9.6 of the base services. 4.” on page 131 for any additional configuration that is required after installation. This topic provides information for installing the middleware on Windows.1. Run launchpad64. Results The launchpad panel is displayed. Starting the launchpad The launchpad lets you install all components that are required for Tivoli Provisioning Manager. Import the middleware settings from the middleware workspace. From the launchpad. insert the Installation DVD for Windows. install the core components. Log on to an account with system administration privileges. To display the log frame on the bottom of the launchpad panels during run time.1. Installing the middleware on Windows. select a language and click OK. 12. Messages that are generated while the launchpad is running are not automatically saved on the hard disk. If you are using DVDs. The installation of other products with Tivoli Provisioning Manager requires additional planning and manual configuration steps. there are several middleware products that must be deployed. The middleware installer provides an interface for installing and deploying middleware in a reliable manner. The following table describes middleware deployment options: Chapter 3. From the launchpad. see Installation of IBM Tivoli Change and Configuration Management Database and Tivoli Service Request Manager® with Tivoli Provisioning Manager version 7. hold Ctrl and click in the banner frame of the launchpad. 2. 10. install the web components. AIX. The disk must be inserted for the duration of the installation.exe (Windows 64-bit) or launchpad.

If you deploy a component using the middleware installer on a system. A process ID is generated each time the middleware installer is used to install or uninstall a set of middleware products. you must choose to install a new DB2 instance or reuse an existing DB2 server. Microsoft Active Directory You must install and configure the software manually. For more information. you must install and configure it manually. MM is a two-digit 30 IBM Tivoli Provisioning Manager Version 7. If you choose to install a new instance of Tivoli Directory Server. the middleware installer will attempt to locate an existing database instance to use. and then later decide you would also like to add Tivoli Directory Server to that same system. If it fails to locate an existing instance. Ensure you have a strategy for deploying middleware for each system you plan to use in your deployment. see “Manually configuring the authentication service” on page 82. and log messages. see “Manually configuring WebSphere Application Server” on page 70. If you choose to install the directory server but not the database server.2 Installation Guide . Additional software The middleware installer performs a number of additional tasks. Alternatively. DB2. the middleware installer must be run on each computer in the topology you have chosen. If you will not be using the middleware installer and will be configuring the existing middleware resources manually. where operation is a string indicating the operation being performed. When installing Tivoli Provisioning Manager middleware on a system. Middleware installation options Application Application server Installation options You must install a new instance of WebSphere Application Server 6. The application server deployment must be secured with a directory server. For more information. such as "INSTALL" or "UNINSTALL". v Configure authentication services. see “Manually configuring Virtual Member Manager on WebSphere Application Server” on page 71. you can use the Tivoli Provisioning Manager database server for the DB2 data store if the Tivoli Provisioning Manager database server uses DB2. see “Manually configuring Microsoft Active Directory” on page 60. The process ID will appear on the file system in various places related to logs and generated files. you must undeploy DB2 before redeploying it in the same middleware installer deployment plan that included Tivoli Directory Server. The process ID is a string of the format [operation_MMdd_HH. it installs a database for use with the directory server. such as file names.1. The process ID is used to group logs and other generated files that are related to the same invocation of the middleware installer. for example.29. You must choose to use a local or remote Tivoli Directory Server or Microsoft Active Directory. Tivoli Directory Server You can install a new instance of Tivoli Directory Server or use an existing instance. The directory server contains information about Tivoli Provisioning Manager users and groups and it communicates that information to the Maximo database using VMM to provide security and access to Tivoli Provisioning Manager applications. you must install all the middleware intended for that system at one time. directory names. Database server Directory server v 2000 DB2 You can install a new instance of DB2 or use an existing instance. To deploy middleware on separate computers. For more information.mm]. If you want to use an existing WebSphere Application Server. It also separates logs and other generated files that are related to different invocations of the middleware installer.0. you also need to perform the following tasks: v Configure VMM after the application server and the directory server have been installed and configured. For more information. The middleware installer deploys software on the computer where you are running it.Table 8.

HH is a two-digit number (0-23) indicating the current hour. User ID created for use with IBM WebSphere Application Server Network Deployment.45] An installation started on September 24 at 3:45pm v [UNINSTALL_1216_09. Windows Service user ID. Table 10. Users and groups In this table.number (1-12) indicating the current month. Here are some examples of process ID values: v [INSTALL_0924_15. list the middleware directory locations to use. Installation tasks 31 . Table 9. use the planning worksheets to record the values to specify when you install the middleware. dd is a two-digit number (1-31) indicating the current day in the month. You can also use the worksheets if you manually configure or reuse existing middleware. For distributed deployments. Description DB2 administrator. record multiple values where appropriate. and mm is a two-digit number (0-59) indicating the current minute. Used for Maximo database configuration. Directory locations Setting Workspace directory Middleware images source directory Compressed images directory Uncompressed images directory Default user_home\ibm\tivoli\mwi\ workspace n/a n/a n/a Your value 2000 DB2 Chapter 3. list the users and groups that you want to create if you do not want to use the default values. Your value Directory locations In this table.59] An uninstallation started on December 16 at 9:59am Planning worksheets for middleware installation Before you start the middleware installation. Users and groups created during middleware installation User db2admin Group v Administrators v DB2ADMNS v DB2USERS maximo wasadmin Not a system user.

DB2 configuration Setting Installation directory DAS user Instance name Port Database instance user ID DB2 administrators group DB2 users group Use same user name and password for remaining DB2 Services Configure Tools Catalog Default v SystemDrive:\Program Files\IBM\SQLLIB v db2admin ctginst1 50005 v db2admin v DB2ADMNS DB2USERS YES NO This value is relevant for reuse scenarios only. Enable operating system security for DB2 objects YES This value is relevant for reuse scenarios only. Table 12. Table 11. 50000 MAXDATA 5000 MB MAXTEMP 1000 MB Your value DB2 instance port Data table space name Data table space size Temporary table space name Temporary table space size WebSphere Application Server Network Deployment configuration List the configuration values to use when you install WebSphere Application Server Network Deployment.DB2 configuration In this table. list the configuration values to use when you install DB2. WebSphere Application Server Network Deployment configuration Setting Installation location Default v C:\Program Files\IBM\WebSphere\ AppServer Your value WebSphere Administration user name wasadmin Deployment Manager profile name Application server profile name Cell name Deployment Manager node name Application server node name HTTP server installation location ctgDmgr01 ctgAppSrv01 ctgCell01 ctgCellManager01 ctgNode01 v C:\Program Files\IBM\HTTPServer 32 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide .

2 cn=root ou=SWG o=IBM. Table 14.OU=SWG.DC=itsm.OU=SWG. WebSphere Application Server Network Deployment configuration (continued) Setting HTTP port Default 80 This port might be in use.c=US 389 636 3538 3539 security idsccmdb 50006 idsccmdb Your value Microsoft Active Directory configuration List the configuration values to use when you install Microsoft Active Directory. Microsoft Active Directory configuration Setting Directory server port LDAP base entry User suffix Group suffix Organization container suffix Bind distinguished name Default 389 DC=itsm.DC=itsm.DC=com DC=itsm. IBM Tivoli Directory Server configuration Setting Installation location Administrator distinguished name Organizational unit Organization and country suffix Directory server port Directory server secure port Administration port Administration secure port Database name Instance name Instance port Instance user name Default v C:\Program Files\IBM\LDAP\V6. or use another port that is unassigned. Table 13.DC=com CN=Administrator. list the configuration values to use when you install IBM Tivoli Directory Server.DC=com Your value Chapter 3.Table 12. Installation tasks 33 .CN=Users. HTTP admin server port HTTP plug-in profile name 8008 ctgAppSvr01 Your value IBM Tivoli Directory Server configuration In this table.DC=com OU=Users.DC=com OU=Groups. Ensure that you either free this port.DC=itsm.

and then configure the components selected as a single deployed application. Whenever a deployment plan is modified. The workspace contains the following items: Deployment Plan The deployment plan is a collection of installation steps. This file is created and then updated after every deployment or undeployment.2 Installation Guide . Topology File The topology file describes the configuration parameters of the middleware deployment. By default. It is generated through the middleware installer and it resides in the workspace directory. Logs Log files that contain information about the deployment can be found in the workspace directory. 34 IBM Tivoli Provisioning Manager Version 7.The middleware installer workspace The middleware installer is designed to record the options you select during install in a directory referred to as the workspace. User interface logs The logs generated by the middleware installation program user interface are located in the workspace directory. The composition and details of the deployment. When deployment steps are changed. which includes reconfiguration of existing deployment choices. The deployment plan configuration files contain information about the deployment plan itself. the existing deployment plan is deleted and replaced with the new deployment plan. configuration parameters for those steps. This file is saved in <workspace>/topology. The different types of log files are described below. The middleware installer logs The middleware installer log files are located in the workspace directory that was defined in the middleware installation program. In addition. The contents of this file can be used by the Tivoli Provisioning Manager installation program to populate its panels with meaningful default values. If you have not defined a workspace that is centrally located and accessible to all the systems that will be receiving middleware. and target computer information. log files native to the middleware itself are also contained in this directory. The existing plan must first be completely removed through the middleware installer before a different set of features and products can be deployed. this file will have to be copied to the workspace of each computer where middleware is being deployed. Locating the workspace on a shared resource avoids the need to copy files such as the topology file manually from one computer to another.properties. The recorded options can also be imported by other installers so that some fields can be filled automatically for you. as well as any logs generated by the middleware installer process are located in the workspace. the deployment plan configuration files will be deleted and regenerated when the deployment plan is redeployed. the middleware installer cannot subsequently deploy additional features and products onto the computer at a later time. the middleware installer workspace is defined as: v C:\ibm\tivoli\mwi\workspace The workspace can be defined on a shared resource that is made available to all the systems that will run the middleware installer. Once a plan has been deployed.

message. uninstall and checking work for the middleware installation program. and so on. Installation tasks 35 . mwi. which contains a few entries that summarize the result of invoking the step. The primary log files for the machine plan are named MachinePlan_host name_processID.log. where host name is the host name of the current system. These log files contain the output generated by ANT when running the machine plan ANT script.log file from earlier invocations of the middleware installation program. are copies of the mwi. The log files for the step are located in the logs subdirectory. The log files generated by a step are located in the same subdirectory and follow the same pattern as a step that is run as part of the deployment plan. for example: v dependency checking to ensure the operating system meets the deployment requirements v inventorying the software on the system to locate existing instances of middleware products deployed by the middleware installation program v checking the available disk space to ensure there is enough for the deployment Each of these checks is produced in the form of a step so that it can also be run as part of the deployment plan. An entry in this log file can direct you to a lower-level log file. mwi. The default workspace locations are: v C:\ibm\tivoli\mwi\workspace The mwi. the middleware installation program performs system checks. All steps will provide a trace log file named stepID_processID. a process ID is assigned and log files are generated. substepNum is the sequence number Chapter 3. The substeps perform the actual installation. The log files for the deployment plan are located in the subdirectory logs/processID. Log files named mwi. a high-level log file that lists the steps invoked as part of the deployment plan. where X is a number. Logs for the deployment plan The deployment plan is located in the directory <Workspace Directory>/host name/deploymentPlan. The primary log file for the deployment plan is DeploymentPlan. So.log1 is produced after the second invocation of the middleware installation program. for example. Logs for the workstation plan The machine plan is located in the directory <Workspace Directory>/host name/deploymentPlan/ MachinePlan_host name. examine this log file first. which contains many entries. Each substep is located in the directory <Workspace Directory>/host name/deploymentPlan/ MachinePlan_host name/stepNum_stepID/operation/substepNum_substepID.log file is the high-level log file that was generated by the most recent invocation of the middleware installation program. When the user interface runs a step. where stepNum is the sequence number of this step in installation processing order of the deployment plan and stepID identifies the step. where operation is the ANT target in the step ANT script that invokes this substep. Logs for substeps Each step contains one or more substeps. Some steps can provide a message log file named stepID_processID. Logs for steps run by the user interface In addition to collecting input from the user.log.The middleware installation program logs all information in <workspace_loc>/mwi. If an error occurs. it copies the step into a subdirectory of the workspace directory. The log files for the machine plan are located in the logs subdirectory. typically including information about the input parameters and the substeps invoked.logX.log0 is produced after the first invocation of the middleware installation program. Each time the deployment plan is used to install or uninstall middleware products. Logs for steps in the deployment plan Each step in the deployment plan is located in a directory named <Workspace Directory>/host name/deploymentPlan/MachinePlan_host name/stepNum_stepID.log.

As a result. For example: mwi-console -V forceHostname=true v When installing and configuring middleware. use fully qualified host names. 2000 DB2 DB2 naming conventions for DB2 instances v Instance names can have up to eight bytes and cannot contain the # character. and substepID identifies the substep. Before you begin v When entering values for host names. v Do not use the special characters @ # $ IBM Tivoli Directory Server naming conventions for databases and database aliases v Database names must be unique within the location in which they are cataloged. 36 IBM Tivoli Provisioning Manager Version 7. consider the following special character restrictions: Table 15. SYS. v Group names and user names can contain up to 30 bytes. For information about verifying host names. SQL. GUESTS. you cannot create a database using a name that exists as a database alias. LOCAL. Log files generated by the native middleware installation programs will also be kept here. uninstall. Special character restrictions for middleware configuration Naming convention 2000 DB2 DB2 naming conventions for group names. user names. Installing and configuring the middleware with the middleware installer This procedure explains how to use the middleware installer to create a deployment plan that is responsible for installing and configuring prerequisite middleware products. PUBLIC. the alias defaults to the database name. 2000 DB2 DB2 naming conventions for passwords v Passwords can be a maximum of 14 bytes. v No instance can have the same name as a service name. v Do not use the special characters @ # $ because they are not common to all keyboards. v Database and database alias names can have up to eight bytes. Typical values for operation are install. When a new database is created. see Resolving host names with a DNS server in “Preinstallation Step 6: Verify the environment” on page 16. ADMINS. This location is: – a logical disk v Database alias names must be unique within the system database directory. or any SQL-reserved word. This value is case-sensitive. even if there is no database with that name.of this substep in the processing order of the step. v You can force the use of alphanumeric host names within the middleware installation program by starting it from the command line and the forceHostname=true parameter. The log files for the substep are typically located in a subdirectory named processID/logs.2 Installation Guide . and user IDs Restrictions v Names and IDs cannot be any of the following values: USERS. v Names and IDs cannot begin with IBM. and check. or the underscore character (_).

and 0 through 9. or SYS. If you experience display problems. groups. or allow the middleware installation program to create a user ID.: . v Values must not include accented characters. Many directory server products consider a blank space as a special character that is part of the LDAP string. PUBLIC. you might encounter Provisioning Manager errors that are difficult to troubleshoot. or values you enter directly into a directory instance using the tools available from the directory server. v When entering LDAP values for Provisioning Manager installation panel fields. v Values can include characters A through Z. v The middleware installation program does not check for accented characters in user name values. you are prompted for user IDs to initiate the installation of DB2. a through z. be aware of the product-specific syntax rules for using special characters in an LDAP string. v Passwords cannot contain the following special characters: ` ' \ " | WebSphere Application Server naming conventions for users and passwords v The administrator name cannot contain the following characters: / \ * . if you mistakenly enter an LDAP string that contains a blank. GUESTS. You can either supply an existing system user ID. or idsldap v Values cannot begin with IBM. and IBM Tivoli Directory Server. v Values must begin with characters A through Z or a through z. for example. Chapter 3. at the end of a field value. and instances Restrictions v Values must not be longer than eight characters and cannot be any of the following values: USERS. they must be preceded by an escape character. Failing to escape special characters contained in an LDAP string used with Provisioning Manager might result in Provisioning Manager errors. entries in LDIF files. SQL. to make special characters readable by the directory server. The passwords that you provide must be valid for your environment. The use of accented characters might cause errors. WebSphere Application Server.=+?|< > & % ’"] [> # $ ~ ( ) { } v The administrator name cannot begin with a period.Table 15. See the product documentation for your directory server for more information about special characters in LDAP strings. databases. Special character restrictions for middleware configuration (continued) Naming convention IBM Tivoli Directory Server naming conventions for users. Installation tasks 37 . LOCAL. and you do not precede the blank character with an escape character. minimize and then maximize the middleware installer to force it to display the panel again. The installation can fail if you supply an existing user account to install DB2 or IBM Tivoli Directory Server and that user account is not located under the /home directory. v In some cases. v When you install middleware using the middleware installation program. v Double-byte characters cannot be used in administrator passwords values. ADMINS. Use the middleware installer locally on the system that hosts the middleware. fields and labels displayed within the middleware installer are not correctly displayed on the panel when installing through remote sessions. v The administrator name cannot contain leading and trailing spaces. In most cases. Middleware installation program naming conventions v The middleware installation program does not validate that your password is compliant with the operating system of the target host. v You cannot use the % character. Therefore.

38 IBM Tivoli Provisioning Manager Version 7. 3.31. and C:\ISM_middleware\WAS. 8. 6. 4. v 2000 DB2 To install a DB2 instance for an existing user. and then click Next. you encounter a subset of the panels included in these instructions that are relevant to the middleware that you want to install on a computer. the middleware installer does not allow you to select from a list of IP address host names. You can now start the middleware installer. However.v When installing middleware using the middleware installer. Perform the following steps on each computer where you are installing the middleware with the middleware installer: a. In this case. 9.26. After verifying and confirming the prerequisites. and then click Next. Accept the license agreement. In addition. 5. C:\ISM_middleware\ITDS. if the computer is configured for the host name real.2 Installation Guide . Select a language for the installation and click OK. IBM Tivoli Directory Server. Procedure 1. specify the directory for the middleware installer workspace. Check for an existing installation of the solution installer. For example. If you intend to deploy middleware products across an array of computers. 10. start it.31. but the virtual host name is virtual. In the launchpad navigation pane. do not install multiple products into the same custom directory. you must run the middleware installer on each computer.3.com. 7. In the Welcome panel. selecting which piece of middleware to install on that particular computer.31. If the IBM ADE service is not running. but the virtual IP address is 9.example. Configure the computer so that it is using the virtual IP address. when installing DB2. In the Choose Workspace panel. as specified in the middleware user preferences node. Configure the computer so that it is using the virtual host name that is bound to the virtual IP address. configure the computer for 9. Click Install middleware. You also cannot install one middleware product in a custom directory and then install another middleware product in a subdirectory of that custom directory. If you are installing middleware on a computer with a virtual IP address.26.com. these instructions assume that you are using the middleware installer to install a complete set of middleware for use with Tivoli Provisioning Manager on a single computer. For example. 2. click Custom Installation. The default location for the workspace is the last workspace location used by this user. click Next. click Verify middleware installation prerequisites. do not install them all in a custom directory called C:\ISM_middleware. Install the middleware. Ensure that you specify the virtual IP address and virtual host name for each middleware application that is installed on a computer where you configured a virtual IP address and host name. Start the launchpad.com. return to the custom installation page. you cannot install WebSphere Application Server Network Deployment into the custom directory C:\ISM_middleware. and WebSphere Application Server Network Deployment on the same computer.12. b. For example. configure the computer for the host name virtual. c. Under 1.12. you can install them in C:\ISM_middleware\DB2. For example. if the computer is configured for the address 9.26.example. start the service: v Check the Services control panel. The default installation location is: v C:\Program Files\IBM\Common\acsi If the solution installer is already installed.example. run the following command: ln -s /home_directory/<username> /home/<username> The instructions in this section are for a typical installation using default values. and then install IBM Tivoli Directory Server in C:\ISM_middleware\ITDS.

Directory server Data maintained by the directory server is used to secure Tivoli Provisioning Manager. if you install the database server on computer A first and then install directory server and application server on computer B. you must copy this file to each computer where you are installing middleware. v If you specify an invalid path. Secure the J2EE server using the Directory server Select this option to use a directory server to secure the J2EE server.DB2_SERVER_9_1_1.properties file is: v C:\ibm\tivoli\mwi\workspace b.properties file from computer A to the middleware workspace on computer B. 12. Important for Tivoli Directory Server: If you are installing Tivoli Directory Server. select the features to install on this computer. Installation tasks 39 .properties file on computer A must remain unchanged.fenced. If you choose to only install the J2EE server portion of the Tivoli Provisioning Manager middleware.fenced. After deployment. For example. the letters of the path are used to create a directory under Launchpad/Install/MWI. you are prompted to supply the directory server that you use to secure it. Database server The Tivoli Provisioning Manager database is used to store information about configuration items and how they relate to each other.DB2_SERVER_9_1_1. a valid drive letter is missing from the path. From the Deployment Choices panel. DB2 is also installed because Tivoli Directory Server uses DB2 as its database. you must: a. you specify a path of myworkspace. The workspace is therefore created in Launchpad\Install\MWI\myworkspace. then the default location for the workspace is: – C:\ibm\tivoli\mwi\workspace v If the selected directory does not exist.properties file can also be used after middleware installation by the Tivoli Provisioning Manager installer to configure the product core components. The topology. J2EE server The J2EE server is used to host and manage the Tivoli Provisioning Manager application. this line for the database server: computera.db2. If you do not want to Chapter 3. When you complete the installation of the directory server and application server on computer B. it is created. change computera to computerb. 11. Edit the topology. For example. the middleware installer also generates a topology file in this directory called topology.user=tx2fenc1 Must be changed to computerb.db2.properties file includes computerb values for the database server and computera values for the directory server and application server.user=tx2fenc1 The original topology. Your choices are to secure with an existing instance of Tivoli Directory Server. The default location of the topology.v If no previous workspace location exists in the middleware user preferences node. From the Install IBM Autonomic Deployment Engine panel. Copy the topology. For example.properties file on computer B so that the middleware installer is aware that the database server settings are from another computer. click Next. the topology. In each line. and then click Next.properties. or an existing instance of Microsoft Active Directory. If you are installing middleware on more than one computer.

The default value is: v DB2 Default Instance Port Enter the port that the default database instance uses. 14. You cannot clear this option once it has been selected. 13. 15. Default Instance Name Enter the name of the default database instance. If you want to use base services authentication and continue to use an LDAP server in your environment. The default value is: v db2admin Default Instance Username Password Enter the password for the default database instance user name. The default is: v SystemDrive:\Program Files\IBM\SQLLIB DB2 Administration Server username Enter the DB2 administrative account name: v The default value is db2admin. then you are required to provide an alphanumeric value in the Hostname field. you are required to provide a resolvable host name. This option is useful when there is more than a single host name assigned to the system.2 Installation Guide . you are able to change the value of the Hostname field. if you want to manually specify the host name of the computer that you are running the installation from. Note: If you have specified the virtual IP address and virtual host name for each middleware application that is installed on a computer. however. click Next.maintain the J2EE server using the directory server. leave this check box selected. An IP address results in an error message. you cannot clear it. However. When this option is selected. 16. Once this option has been selected. such as in cases where a system has more than one network interface. If you want to use base services authentication without using an LDAP server in your environment. In the Configurable Host Name panel. Default Instance Username Enter the user name for the default database instance. If you started the middleware installation program from the command line using the forceHostname=true parameter. The password that you specify must meet the restrictions for all passwords. Click Next. The default value is 50000. do not select this check box. From the Deployment Plan Summary window. Enter the following configuration parameters for DB2 Enterprise Edition Server and then click Next. select the Override the local machine hostname option and enter a host name value in the Hostname field. 40 IBM Tivoli Provisioning Manager Version 7. Enter the following configuration parameters for the default database instance and click Next. or it is configured to support virtual IP addresses. DB2 Administration Server password Enter the password for the DB2 administrative account. clear the Use this password as the value for all subsequent passwords check box. If you do not want to use this option. In the Password Reuse panel. you can select the Use this password as the value for all subsequent passwords check box and enter a password value. which lets you use the same password in all panels of the middleware installation program. You cannot install the directory server using the middleware installer. 17. do not select this option. you do not have to manually specify the host name of the computer that you are running the installation from in the next step. you can change the value you enter in the Hostname field. Install location Enter the location to install DB2. Select this option only if you want to manually specify the host name of the system instead of having the installation program programmatically detect it.

The default value is: v DB2ADMNS DB2 users group Enter the name of the DB2 users group. Enter the following configuration parameters for the Tivoli Provisioning Manager database instance. The default value is 389. Administration secure port Enter the secure administration port number of the Tivoli Directory Server. The default value is o=IBM. Organizational unit Enter the name of the Tivoli Directory Server organizational unit to use with Tivoli Provisioning Manager. Port Enter the port that the Tivoli Provisioning Manager database instance uses. Organization and country suffix Enter the name of the Tivoli Directory Server organization and country suffix to use with Tivoli Provisioning Manager. and then click Next. and then click Next. Chapter 3. The default value is 3538. 22. The default value is: v db2admin Instance username password Enter the password for the Tivoli Provisioning Manager database instance user name.c=US. Enter the following configuration parameters for theTivoli Directory Server database instance. Installation tasks 41 . Enter information about the DB2 user groups: DB2 administrators group Enter the name of the DB2 administrators group.2 Administrator distinguished name Enter the distinguished name of the Tivoli Directory Server administrator. The default value is ctginst1. Instance username Enter the user name for the Tivoli Provisioning Manager database instance. Instance name Enter the name of the Tivoli Provisioning Manager database instance. Administrator password Enter the password for the Tivoli Directory Server administrator. The default value is ou=SWG. and then click Next. Directory server port Enter the port number of the Tivoli Directory Server. The default value is 636. The default value is 3539. 19. Enter the following configuration parameters for IBM Tivoli Directory Server. The default value is 50005. Install location Enter the location to install Tivoli Directory Server. 21.18. Administration port Enter the administration port number of the Tivoli Directory Server. 20. The default value is cn=root. Directory server secure port Enter the secure port number of the Tivoli Directory Server. Enter the following configuration parameters for IBM Tivoli Directory Server. and then click Next. The default value is DB2USERS. The default value is: v C:\Program Files\IBM\LDAP\V6.

If you are using virtual host names and IP addresses for the computer.c=US 42 IBM Tivoli Provisioning Manager Version 7. you might encounter errors.com.o=IBM. See the product documentation for your directory server for more information about special characters in LDAP strings. The default value is ou=users. This value is case-sensitive.c=US User suffix Enter the user suffix of the LDAP instance to use for WebSphere Application Server security. or values you enter directly into a directory instance using the tools provided with the directory server. Instance name Enter the name of the Tivoli Directory Server database instance.c=US Organization container suffix Enter the organizational container suffix of the LDAP instance to use for WebSphere Application Server security. The default value is idsccmdb. and you do not precede the blank character with an escape character. Failing to escape special characters contained in an LDAP string used with Tivoli Provisioning Manager might result in errors. LDAP base entry Enter the LDAP base entry of the LDAP instance to use for WebSphere Application Server security.o=IBM. The default value is ou=SWG. For example. LDAP Host Name Enter the fully qualified domain name of the system hosting the LDAP instance to use for WebSphere Application Server security. Instance user password Enter the password for the instance user ID. The default value is 50006. In most cases. The default value is ou=SWG. if you mistakenly enter an LDAP string that contains a blank. Enter the following configuration parameters for WebSphere Application Server security.example.o=IBM. entries in LDIF files. This value is case-sensitive. Port Enter the port number used by the Tivoli Directory Server database instance.ou=SWG. ensure that you specify the correct virtual host name in the fully qualified domain name. A fully qualified domain name includes the host name and the domain suffix. Directory server port Enter the port number used by the LDAP server to use for WebSphere Application Server security. When entering installation values.c=US Group suffix Enter the group suffix of the LDAP instance to use for WebSphere Application Server security. The default value is 389.Database name Enter the name of the DB2 database you are using to hold Tivoli Directory Server data.2 Installation Guide . Note: The middleware installer does not validate all LDAP settings that you enter in the installer. 23.o=IBM. The default value is security. and then click Next. Many directory server products consider a blank space as a special character that is part of the LDAP string. The default value is ou=groups. tpmserver. special characters must be preceded by an escape character in order to make them readable by the directory server. at the end of a field value for example. be aware of the product-specific syntax rules for using special characters in an LDAP string. Therefore.ou=SWG.

you cannot start and stop the IBM HTTP Server from the administrative console. Cell name Enter the WebSphere Application Server Cell name. HTTP port Enter the port used by the IBM HTTP Server. you can start and stop IBM HTTP Server from within the administrative console. Enter the following configuration parameters for WebSphere Application Server. and then click Next. The default value is: v C:\Program Files\IBM\HTTPServer. You must stop the IBM HTTP Server from the command line. If you choose to install IBM HTTP Server into a directory path that does not contain any spaces. Application server profile name Enter the WebSphere Application Server profile name of the application server. Enter the following configuration parameters for WebSphere Application Server. Chapter 3. The default value is: v C:\Program Files\IBM\WebSphere\UpdateInstaller 28. 26. The default value is 80. The default value is ctgCell01. Install location Enter the location to install WebSphere Application Server. and then click Next. The default value is wasadmin. and then click Next. and then click Next. Deployment Manager profile name Enter the WebSphere Application Server profile name of the deployment manager server. WebSphere Administration password Enter the password for the WebSphere Application Server administrative account. Deployment Manager node name Enter the name of the WebSphere Application Server deployment manager node. Enter the following configuration parameters for WebSphere Application Server security. The default value is cn=root. Installation tasks 43 . such as Program Files. and then click Next. The default value is ctgCellManager01. Update Installer install location Enter the location where the WebSphere Application Server update installer is installed. The default value is ctgDmgr01. Application server node name Enter the name of the WebSphere Application Server node. 27. The default value is ctgNode01. Enter the following configuration parameters for IBM HTTP Server. 25. Enter the following configuration parameters for WebSphere Application Server.24. The default value is ctgAppSrv01. The default value is: v C:\Program Files\IBM\WebSphere\AppServer WebSphere Administration username Enter the WebSphere Application Server administrative account name. Bind password Enter the password for the bind distinguished name. Bind distinguished name Enter the bind distinguished name for binding to the LDAP instance. If you install IBM HTTP Server into a directory path that includes spaces. Install location Enter the location to install IBM HTTP Server.

com. If you are installing middleware on a computer with a virtual IP address. b. and then click Next. an error might occur.example. Specify the location of the middleware images. click Finish.3. 37. Once the deployment completes successfully. Profile name The default value is ctgAppSrv01. perform the following steps: 31.26. If you selected the option to copy install images from the source media. The default value is 8008. You can also change the deployment plan or parameters that you have previously configured in this panel. If you are installing middleware on more than one computer. replace the corrupted middleware image and then restart the middleware installation program.31.255. and then click Next.31. 34.31. 33. This value cannot be changed. complete the following steps: a. If you selected the option to specify a directory that already contained the middleware images. Specify a directory containing all the required middleware install images Select this option if you intend to specify a directory that already contains all the middleware installation images. select the option for checksum validation. insert the Middleware DVD for your operating system and platform before you click Next.cfg: – The file is located in the DB2 installation directory. 30. specify the source and destination directories. 35. If you are installing from DVDs. specify that directory.Admin Server port Enter the port to use to administer IBM HTTP Server. 29.2 Installation Guide . Ensure that you copy the topology.12 netmask 255. 32. Verify that the virtual IP address and host name are correctly configured. It is recommended to select this option to avoid any installation failures at a later stage during installation. If you do not select this option and the middleware images are corrupted or are not accessible from the directory specified.240 44 IBM Tivoli Provisioning Manager Version 7.properties file. Copy the middleware install images from the source media to a specified directory Select this option to copy the middleware images from the product media to a directory that you specify. From the Deployment Plan Operation panel.12 back to the original value of 9. and then click Next. Accept the following configuration parameter for WebSphere Application Server plug-in for the IBM HTTP Server and click Next. and then click Next.properties file from the workspace to the workspace of the next computer where you are installing middleware. v 2000 DB2 Check the file db2nodes. To resolve the error. Continuing with the example in step 2 on page 38. 2) Change the host name virtual. 36. On each computer where you configured the virtual IP address and host name. To confirm the integrity of the images before deploying the middleware.255. If the checksum operation fails. check the topology. 3) Run the command to configure the second IP address.26. The default location is C:\Program Files\IBM\SQLLIB.com back to the original real. For example: ifconfig eth0:1 9.example. review the contents of the summary and click Deploy. select Deploy the plan and click Next. Specify a directory to use for middleware installer temporary files and extracted middleware installation images. you would make the following changes: 1) Change the IP address 9. click Back and copy the images again before proceeding. v In the middleware workspace. From the Deployment Plan and Parameter Configuration summary panel. you can now configure the original IP address and host name values and configure the virtual IP as a secondary IP address.26.

Run this command on the computer ldap.example.com and Tivoli Directory Server is installed on the computer with the virtual host name ldap.38.example. 2. Back up the WebSphere Application Server configuration. instead of backing up the WebSphere Application Server configuration and the deployment engine database. This section contains information about configuring existing DB2.com: a.com : db2set -g DB2SYSTEM=database. then return to the custom installation page. What to do next 1. run the following command: rm /home/<username> CAUTION: Future fix packs can rely on this symbolic link. Run this command on the computer database. Alternatively. You cannot use the middleware installer to configure an existing Oracle Database (if supported) or WebSphere Application Server.example. Follow the instructions on the panel to back up. In the launchpad navigation pane. and Microsoft Active Directory servers using the middleware installer.com : db2set -g DB2SYSTEM=ldap.3 Back up WebSphere configuration.example. click Custom Installation and click 1. then return to the custom installation page. 3. Back up the deployment engine database. Tivoli Directory Server. consider the following restrictions: Chapter 3. Follow the instructions on the panel to back up.com b. When installing and configuring middleware in the middleware installer and the Tivoli Provisioning Manager installation program.4 Back up the deployment engine database. See “Using manually configured middleware” on page 49 for more information about those servers. This information also applies if you decide that you want to reuse existing middleware servers but you want to configure them to work with Tivoli Provisioning Manager manually instead of allowing the Tivoli Provisioning Manager installation program to configure them. If you want to remove the symbolic link. If you are using a virtual IP address on the computer where the DB2 server for Tivoli Provisioning Manager or the DB2 server for Tivoli Directory Server is installed.com Results The middleware is now installed. In the launchpad navigation pane.example. Example: If DB2 is installed on a computer with the virtual host name database. If you intend to reuse existing middleware servers with Tivoli Provisioning Manager. you can capture an entire system image of the provisioning server. click Custom Installation and click 1. they must be configured before installing Tivoli Provisioning Manager.example. Other middleware products must be configured manually if you want to reuse them. run the following DB2 command on the computer: db2set -g DB2SYSTEM=virtual_hostname Replace virtual_hostname with the virtual host name. Reusing middleware using the middleware installer You can use the middleware installer to configure some middleware products. Installation tasks 45 .

46 IBM Tivoli Provisioning Manager Version 7. SYS. even if there is no database with that name. SQL. As a result. v Double-byte characters cannot be used in administrator passwords values. v Group names and user names can contain up to 30 bytes. PUBLIC. 2000 DB2 DB2 naming conventions for passwords v Passwords can be a maximum of 14 bytes. v Values must begin with characters A through Z or a through z. databases. or idsldap v Values cannot begin with IBM. you cannot create a database using a name that exists as a database alias. user names. or the underscore character (_). or SYS. GUESTS. and user IDs Restrictions v Names and IDs cannot be any of the following values: USERS.: . This location is: – a logical disk v Database alias names must be unique within the system database directory. Special character restrictions for middleware configuration Naming convention 2000 DB2 DB2 naming conventions for group names. and 0 through 9. v Values must not include accented characters. v No instance can have the same name as a service name. ADMINS. v The administrator name cannot contain leading and trailing spaces. v Names and IDs cannot begin with IBM. v Passwords cannot contain the following special characters: ` ' \ " | WebSphere Application Server naming conventions for users and passwords v The administrator name cannot contain the following characters: / \ * . a through z. v Database and database alias names can have up to eight bytes. or any SQL-reserved word. PUBLIC. the alias defaults to the database name. GUESTS.2 Installation Guide . LOCAL. SQL.Table 16. v Do not use the special characters @ # $ because they are not common to all keyboards. When a new database is created. groups.=+?|< > & % ’"] [> # $ ~ ( ) { } v The administrator name cannot begin with a period. 2000 DB2 DB2 naming conventions for DB2 instances v Instance names can have up to eight bytes and cannot contain the # character. v Values can include characters A through Z. and instances v Values must not be longer than eight characters and cannot be any of the following values: USERS. ADMINS. LOCAL. IBM Tivoli Directory Server naming conventions for users. v Do not use the special characters @ # $ IBM Tivoli Directory Server naming conventions for databases and database aliases v Database names must be unique within the location in which they are cataloged.

example. Refer to “Installing and configuring the middleware with the middleware installer” on page 36 for more information. Login as a user with administrative authority. 2.com. select Database Server. Before you begin v Verify installation prerequisites described in Chapter 2.Table 16. The middleware installer does not validate all names and passwords entered in the installer. database names. From the Deployment Choices panel. select the appropriate instance to reuse. v To avoid installation errors. v The middleware installation program does not check for accented characters in user name values. From the Installation drop-down menu. 6.example.example. you must create them before running the Tivoli Provisioning Manager installation program. “Preinstallation tasks. Configuring an existing DB2 with the middleware installer You can use the middleware installer to configure an existing DB2 database. run this command on the computer database. 3. ensure that you review all requirements described in “Preinstallation Step 7: Verify requirements for user names. and then click Next. Installation tasks 47 . If you are using a virtual IP on the computer where the DB2 server for Tivoli Provisioning Manager is installed. and then click Next. 7. Example: If DB2 is installed on a computer with the virtual host name database. Users – db2admin Groups – db2admns To configure an existing DB instance for reuse with Tivoli Provisioning Manager: Procedure 1. run the following DB2 command on the computer: db2set -g DB2SYSTEM=virtual_hostname Replace virtual_hostname with the virtual host name. If they do not exist on the system. v You cannot use the % character.com: db2set -g DB2SYSTEM=database. v The following users and groups must already exist on the system.” on page 5. until you reach the Deployment Choices panel. 4. and user passwords” on page 21. The Tivoli middleware installer will display any instances of DB2 found on the system. Special character restrictions for middleware configuration (continued) Naming convention Middleware installation program naming conventions Restrictions v The middleware installation program does not validate that your password is compliant with the operating system of the target host.com Chapter 3. The use of accented characters might cause errors. 5. v Always use fully qualified domain names when entering values for computer host names. Launch the middleware installer from the launchpad. Complete the installation by proceeding through the remainder of the middleware installer panels. The passwords that you provide must be valid for your environment. Proceed through the middleware installer panels as instructed in “Installing and configuring the middleware with the middleware installer” on page 36.

Supply the correct Administrator Distinguished Name and password.2 Installation Guide .com. you can verify that it will work with Provisioning Manager using the middleware installer.What to do next Proceed to “Installing the base services” on page 98. and then click Next. run the following DB2 command on the computer: db2set -g DB2SYSTEM=virtual_hostname Replace virtual_hostname with the virtual host name.com: 48 IBM Tivoli Provisioning Manager Version 7. 3. Before you begin v Verify installation prerequisites described in Chapter 2. 7. If you intend to host a new Tivoli Directory Server instance on your existing Tivoli Directory Server. select the appropriate instance to reuse. until you reach the Deployment Choices panel. v The Tivoli Directory Server is running. Example: If Tivoli Directory Server is installed on the computer with the virtual host name ldap. database names. run this command on the computer ldap. 5. Verifying an existing Tivoli Directory Server with the middleware installer If you have an existing IBM Tivoli Directory Server installation that you would like to reuse for Provisioning Manager. 4. v Always use fully qualified domain names when entering values for computer host names. LDAP BASE DN. “Preinstallation tasks. Refer to “Installing and configuring the middleware with the middleware installer” on page 36 for more information. More information about creating an instance can be found in “Manually configuring IBM Tivoli Directory Server” on page 54. supply the correct Administrator Distinguished Name and password. If you want to reuse an existing Tivoli Provisioning Manager. Log in as a user with administrative authority. The middleware installer does not create a Tivoli Directory Server instance for use with Tivoli Provisioning Manager. The middleware installer displays any instances of Tivoli Directory Server found on the system. 6. 2. select Directory Server. ensure that you carefully review all requirements described in “Preinstallation Step 7: Verify requirements for user names. Directory server port. Complete the installation by proceeding through the remainder of the middleware installer panels. Directory server port. From the Installation drop-down menu. you must create it before running the middleware installer. From the Deployment Choices panel. and user passwords” on page 21. The middleware installer validates the following: v The version of Tivoli Provisioning Manager. If you are using a virtual IP on the computer where Tivoli Directory Server is installed. Proceed through the middleware installer panels as instructed in “Installing and configuring the middleware with the middleware installer” on page 36. v The Base DN information that you supply in the Tivoli Provisioning Manager. To verify an existing instance of Tivoli Directory Server: Procedure 1. Launch the middleware installer from the launchpad. and Administration port information for that instance on the middleware installer panels. v To avoid installation errors. and then click Next.example.” on page 5. and the Administration port information for that instance on the middleware installer panels when prompted. The middleware installer does not validate all names and passwords entered in the installer. the correct LDAP BASE DN.example.

Use the DB2 installation media provided with Tivoli Provisioning Manager to ensure that you are using the correct version. Before you begin v Ensure you have a minimum of 8 gigabytes of free space in the DB2 installation directory. the directory server. the database server. and disk requirements. If you are using disks. You must complete the manual configuration of each server you plan to not configure using the autoconfiguration feature of the Tivoli Provisioning Manager installation program before you run the Tivoli Provisioning Manager installation program. Also ensure that you allocate sufficient disk space for growth of the database. 2.db2set -g DB2SYSTEM=ldap. In the Welcome screen. Accept the licence agreement and click Next. insert the DVD. This section provides basic installation instructions for a typical installation of DB2. v Ensure that your system meets other installation. Using manually configured middleware Manual installations involve configuring middleware components. Log on as administrator. refer to the DB2 documentation. and security issues to consider when installing DB2. 4. memory. review installation prerequisites and the release notes for the latest information and then proceed with the installation. and the application server to work with Tivoli Provisioning Manager before using the Tivoli Provisioning Manager installation program. 9. Installation tasks 49 . configure the database server manually before you use the installation program. Select the file for the language that you want to install. click Next. For information about the DB2 requirements. The DB2 installer automatically calculates required disk space and determines if you have sufficient space. 5. 6.com What to do next Install the base services. Manually configuring the database server If you do not want the installation program to automatically configure the database server. From this window. 8. Alternatively. Change to the folder ese\image and run setup. Chapter 3. Extract the contents of the archive file. Click Install Products. Procedure 1. 3. The IBM DB2 Setup Launchpad opens. If you are using installation images. copy the archive file that starts with DB2_ESE_V91 to the directory you want to install DB2. you can choose to manually configure one or more of the middleware servers to work with Tivoli Provisioning Manager. You can elect to have one or more Tivoli Provisioning Manager middleware components configured automatically by the middleware installer.example. Select DB2 UDB Enterprise Server Edition and click Next. Installing the DB2 server: 2000 DB2 Follow these procedures to install the DB2 server. 7. refer to the installation information in the DB2 information center.exe to start the DB2 Setup wizard. If you require more information.

Continue with the installation and use the default values suggested by the installer. run this command on the computer database. This section provides basic installation instructions for a typical installation of DB2. copy the archive file that starts with DB2_CLIENT_V95 to the directory you want to install DB2. The IBM DB2 Setup Launchpad opens. 7.example. Select DB2 Administration Client and click Next. In the Welcome screen. Example: If DB2 is installed on a computer with the virtual host name database. 14.com What to do next 1. Run the following commands: db2set db2set db2set db2set DB2COMM=TCPIP DB2BQTRY=120 DB2BQTIME=2 DB2AUTOSTART=YES b. a status page opens. 11. Procedure 1.example. If you are using a virtual IP on the computer where the DB2 server for Tivoli Provisioning Manager is installed. If you are using DB2 on a separate node. If you are using images. During Tivoli Provisioning Manager installation. 2. 4. refer to the installation information in the DB2 information center. 2. 3. run the following DB2 command on the computer: db2set -g DB2SYSTEM=virtual_hostname Replace virtual_hostname with the virtual host name.com: db2set -g DB2SYSTEM=database.example. Proceed to “Installing the DB2 client. Click Install Products. After the installation completes. Log on as a user with administrator access. 50 IBM Tivoli Provisioning Manager Version 7. Perform the following post-installation steps: a. click Next.exe to start the DB2 Setup wizard.10. Accept the default value (Typical) and click Next. Click the Status report tab to ensure your installation was successful. insert the disk into the disk drive.” Installing the DB2 client: 2000 DB2 Follow these procedures to install the DB2 client. review installation prerequisites and the release notes for the latest information and then proceed with the installation. Configure DB2 for use with Tivoli Provisioning Manager by either manually configuring settings or by running the middleware installer to automatically configure settings. 5. Use the DB2 installation media provided with Tivoli Provisioning Manager to ensure that you are using the correct version. Select the Install DB2 UDB Enterprise Server Edition on this computer check box and click Next. 12. From this window. 6. If you are using DVDs. See “Configuring an existing DB2 with the middleware installer” on page 47.com. Change to the folder CLIENT and run setup. If you require more information. the DB2 client must be preinstalled on the Tivoli Provisioning Manager computer. 8. 13. the database client is used to connect to the DB2 server and configure it for use with Tivoli Provisioning Manager.2 Installation Guide .

Accept the default value (Typical) and click Next. Installation tasks 51 . or use custom values of your own.50005 ctginst1 Depending upon your environment. Click Finish to start the installation. it is not necessary to assign a specific group.x: This section contains instructions for manually configuring DB2 9. complete the following steps before launching the Provisioning Manager installation program: Procedure 1. d. b. Accept the default values for the remaining panels.password -r 50005. 13. you can add this information to your PATH.x servers for use by Provisioning Manager. Log on to the system as a user that has administrative permissions on the system. Accept the licence agreement and click Next. If you are configuring DB2 manually. log on to the system using the user IDs and change the password for each account. Manually configuring DB2 9. To configure an existing DB2 9. 11. 2. 12.5/instance directory. Start the ctginst1 database instance: db2start 3. You can use these user and group name values. Create a database: a. you might have to run this command from the /opt/ibm/db2/V9. After the user IDs have been created. but be sure to substitute them where appropriate in this procedure.x server for use with Provisioning Manager. use SMIT to add the users. Open up the DB2 Control Center for the instance you plan to use: 1) Open a command window. Create the DB2 instance: a. Use the following command to create the DB2 instance: db2icrt -s ese -u db2admin. b. review your settings. On the summary panel. 2) Type the following commands: set DB2INSTANCE=ctginst1 db2set DB2COMM=tcpip 3) Type the following command: db2cc 1) Open a command window. For AIX. Alternatively. 10. Set the listening port for the instance: db2 update dbm cfg using svcename 50005 c. you need to create users and groups manually using user management tools available on the system.9. The middleware installer creates a ctginst1 user that owns the database instance and assigns that user to a group called db2iadm1. You will need this information for Tivoli Provisioning Manager installation. Create a system group and system users. Create users named ctginst1 and maximo and assign the ctginst1 user to a group named db2iadm1. For the maximo user. Note the DB2 client installation directory. Create system users: a. Set instance service to start automatically: sc config ctginst1-0 start= auto where <instance name> is the login name of the instance. 2) Type the following commands: Chapter 3.

. and then click OK. This option creates a Unicode database with a code set of UTF-8. d. select Yes.) in the Value column. From the Database Configuration panel.. Alternatively.1.) in the Value column. select the LOGSECOND value and click the button labeled with the ellipsis (. enter maxdb71 for both the Database name and Alias fields. select the APPLHEAPSZ value and click the button labeled with the ellipsis (. f. if you do not want to use the database path as the storage path.) in the Value column. and then click Finish.. Right-click the Databases folder located below the instance name. If using DB2 9. i. Click Next. f. Enter 30000.. Restart the database by right-clicking the ctginst1 instance. click Next. m.. If using DB2 9. j. h.set DB2INSTANCE=ctginst1 db2set DB2COMM=tcpip 3) Type the following command: db2cc b. Enter 1024. and then select Create Database > With Automatic Maintenance. g. 5. and then click OK.. h. specify a different directory.) in the Value column. click OK. provide scheduling details for offline maintenance. select the LOCKLIST value and click the button labeled with the ellipsis (. g. From the DB2 Control Center. From the Database Configuration panel. From the Specify a name for your new database panel. If you specify a path.. From the Specify where to store your data panel. c.. From the Select your maintenance strategy panel. From the Specify when offline automatic maintenance activities can run panel. and then click OK. the directory must exist. 4. navigate to All Systems > <System hosting the database instance> > Instances. From the actions review panel.2 Installation Guide . From the Database Configuration panel. and then click Next. Add users to the database: 52 IBM Tivoli Provisioning Manager Version 7. k. Click Close. select the LOGFILSIZ value and click the button labeled with the ellipsis (. Click the button labeled with the ellipsis (. Enter 4. n. Enter 1024..5 or higher. and then click Next.. and choose Configure Parameters. From the Database Configuration panel. review the choices you have made. e. From the Provide a valid SMTP server panel. i. Configure the database: a. clicking Stop. l. k.) in the Value column. From the Database Configuration panel. If using DB2 9. Right-click the maxdb71 database created in the previous step. and then click OK. b. The database is created. enter the name of the SMTP server that is used to communicate DB2 messages concerning this database. I can specify an offline maintenance window of at least an hour when the database is inaccessible. d. select the APP_CTL_HEAP_SZ value. enable the Enable database for XML option. j. c. and then click Next. from the Database Configuration panel.1. and then click OK. select the appl_memory value. Enter 4096. e. and then clicking Start.

From the DB2 Control Center. and leave Extent size as 32. select Yes. Click Create to create a buffer pool for the table space. From the Add User dialog box. Alternatively. Select Regular as the type of table space and then click Next.secadm on database to user maximo 6. Click Finish. and then click OK. Specify MAXDATA as your new table space. and then click Next. b. j. you can use the following commands to complete the steps from the command line: grant use of tablespace maxdata to user maximo Note: If you created a separate index table space.create_not_fenced_routine. Grant permissions for the table space: a. e. Alternatively. Alternatively. highlight the user maximo and click Grant All. From the Database authorities window. right-click it and select Authorities.connect. locate and right-click the MAXDATA table spaces entry under the DB2 database that you created for use with Provisioning Manager. 7. and then click OK. Define a hard disk drive specification by choosing Server (SCSI). 8. d. you could create one now. c. If you would rather create a separate index table space. you can use the following commands to complete the steps from the command line: create bufferpool maxbufpool immediate size 4096 pagesize 32 k create regular tablespace maxdata pagesize 32 k managed by automatic storage extentsize 16 overhead 12. Once the database has restarted. From the right-click menu. Select the user maximo. Highlight the newly created buffer pool and click Next. From the Privileges drop-down menu. Ensure the Create buffer pool immediately choice is selected. Click OK. k. Create a schema: a. Create table space: a. Chapter 3. locate and right-click the Schema entry under the DB2 database that you created for use with Provisioning Manager. e. From the User tab of the Database Authorities window. and then click OK. b.createtab. select Create. g. d. c.a.18 bufferpool maxbufpool dropped table recovery on Note: By default. index data is stored in the data table space.implicit_schema. and then click Next. Installation tasks 53 .67 prefetchsize 16 transferrate 0. and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. i. h. and then click OK. c.create_external_routine. and then click Next. b. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Provisioning Manager. b. click Add User. From the DB2 Control Center. choose the Between 200 MB and 2 GB option. load.quiesce_connect. From the right-click menu. you can use the following commands to complete the steps from the command line: connect to maxdb71 grant dbadm. d. f. select Create. Click Add User. e. From the right-click menu. From the DB2 Control Center. select Privileges. Specify MAXBUFPOOL as your new buffer pool. you must grant permissions for it at this time.bindadd. From the Specify the extent and prefetch sizes for this table space panel. select the user maximo.

Many directory server products consider a blank space as a special character that is part of the LDAP string. entries in LDIF files. f. Be aware that the various DN and suffix values listed in these sections must be replaced with values that are applicable to existing LDAP hierarchies within your organization. Specify MAXTEMP for your new table space. you can use the following commands to complete the steps from the command line: CREATE SYSTEM TEMPORARY TABLESPACE MAXTEMP PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 OVERHEAD 12. Right-click on the new schema name and select Privileges. h. e. Define a hard disk drive specification by choosing Server (SCSI). for example. you can use the following commands to complete the steps from the command line: CREATE SCHEMA MAXIMO AUTHORIZATION ADMINISTRATOR GRANT CREATEIN. b. and then click OK. From the DB2 Control Center. From the right-click menu. Specify a name for your new schema. locate and right-click the table spaces entry under the DB2 database that you created for use with Provisioning Manager. if you mistakenly enter an LDAP string that contains a blank.2 Installation Guide .ALTERIN ON SCHEMA MAXIMO TO USER MAXIMO 9. g. Select the previously created buffer pool MAXBUFPOOL.5 FP3a installed. Manually configuring IBM Tivoli Directory Server: 54 IBM Tivoli Provisioning Manager Version 7. See the DB2 support page for more information. and then select the maximo user. and leave Extent size as 32. and then click Next. e. Click OK. c. or values you enter directly into a directory instance using the directory server's own tools. Failing to escape special characters contained in an LDAP string used with Tivoli Provisioning Manager will result in Tivoli Provisioning Manager errors.67 PREFETCHSIZE 16 TRANSFERRATE 0. See the product documentation for your directory server for more information about special characters in LDAP strings. at the end of a field value. Click Finish. Important: When entering LDAP values for Tivoli Provisioning Manager installation panel fields.c. h. Select the maximo user and then click Grant all. This name must be the same as was used for the database user ID. be aware of the product-specific syntax rules for using special characters in an LDAP string. g.DROPIN. Therefore. Alternatively. and then click Next.18 BUFFERPOOL MAXBUFPOOL 10. Create a temporary table space: a. and then click Next. f. special characters must be preceded by an escape character in order to make it readable by the directory server. d. Manually configuring the directory server You must complete the manual configuration of the directory server before you use the Tivoli Provisioning Manager installation program if you choose to not have the Tivoli Provisioning Manager installation program automatically configure it. Select System temporary as the type of table space and then click Next. select Add User. choose the Between 200 MB and 2 GB option. From the Specify the extent and prefetch sizes for this table space panel. From the dialog box. Ensure that you have DB2 Enterprise Server Edition 9. Alternatively. select No Grant. select Create. In most cases. d. you might get Tivoli Provisioning Manager errors. and click Next. From the Privileges drop-down menu. and then click OK. and you do not precede the blank character with an escape character.

complete the following fields and click Next. 8. In the TCP/IP settings for multihomed hosts panel. Procedure 1. From the Instance details window. In the Create a new instance window. 6. User name Select idsccmdb as the system user ID of the user who owns the instance. Before you begin Note: Sharing a DB2 instance between Tivoli Provisioning Manager and Tivoli Directory Server is not recommended. Create the user db2admin and make it a member of the following groups: v Windows Administrators v DB2ADMNS v DB2USERS 2. In the TCP/IP port settings panel. Encryption seed string Type a string of characters that are used as an encryption seed. Install location Enter the location where the instance files are stored. select Listen on all configured IP addresses. Server secure port number Enter 636 as the secure port for the server. Create a user on the system and assign it to the appropriate group. leave the following options selected and click Next. click Create an instance. and then click Next. you must create an instance of IBM Tivoli Directory Server. This name is also the name of the instance. Installation tasks 55 . In the Option steps panel. complete the following fields and click Next. If the Instance Administration tool is not already started. 4.To configure Tivoli Directory Server before starting the Tivoli Provisioning Manager installation program. click Create a new directory server instance and click Next. In the Instance Administration tool. If you are using the automated installation programs. 3. Chapter 3. the database instance is restarted. enter idsccmdb as the value for the DB2 instance name field and click Next. In the DB2 instance details panel. 5. log on as an administrator on the system and start the tool: v Click Programs > IBM Tivoli Directory Server 6. Admin daemon port number Enter 3538 as the administration daemon port. separate instances are created for use by Tivoli Provisioning Manager and Tivoli Directory Server.2 > Instance Administration Tool. During the installation. which could disrupt the availability of Tivoli Directory Server to your enterprise. 7. This value must be a minimum of 12 characters. Server port number Enter 389 as the contact port for the server. Instance description Enter a brief description of the instance. 9. Admin daemon secure port number Enter 3539 as the administration daemon secure port.

complete the following fields and click Next.2 Installation Guide . Create the following users in the LDAP repository.Configure admin DN and password You want to configure the administrator DN and password for the instance now. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected. complete the following fields and click Next. v wasadmin v maxadmin v mxintadm v maxreg To create the users. Ensure that you have at least 80 MB of free disk space in the location that you specify and that additional disk space is available to accommodate growth as new entries are added to the directory. Start the IBM Tivoli Directory Server Configuration tool: v Click Programs > IBM Tivoli Directory Server 6. Database name Enter idsccmdb as the database to be used with this directory instance. In the Configure administrator DN and password window panel. 15. Password Enter the password for the idsccmdb user. Administrator Password Enter a password for the Administrator DN.2 > Instance Administration Tool. Select Manage suffixes. Add the DN information. Click Close to exit the Instance Administration tool. 17. In the Manage suffixes panel. review the instance creation details provided and click Finish to create the idsccmdb instance. 20. 11. for example: ou=SWG. These users are required so that Virtual Member Manager can secure Provisioning Manager. 18. 10. Click Close to close the window and return to the main window of the Instance Administration tool. 12. type the following suffix and click Add. Click OK. In the Configure database panel.o=IBM.c=US 19. 13. Administrator DN Enter cn=root for the administrator distinguished name. you must create an LDIF file with the required information. In the Database options panel. Database user name Enter idsccmdb as the database user. Database install location Enter the location where you want the database instance to be created: v This value must be a drive letter. 16. 14. In the Verify settings panel.c=US ou=users 56 IBM Tivoli Provisioning Manager Version 7. o=IBM. complete the following fields and click Next. Configure database You want to configure the database for the directory server now.

SWG houses the ou=users organization units to place the users created for Provisioning Manager.c=US in this example indicate an organization unit called SWG.c=us uid: wasadmin userpassword: wasadmin objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: person objectclass: top title: WebSphere Administrator sn: wasadmin cn: wasadmin dn: uid=maxadmin.ou=SWG.Note: ou=SWG.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg. o=ibm. o=ibm.ou=SWG. o=ibm.ou=users.o=IBM. o=ibm.c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg After the creation of users. o=ibm.ou=users. you are required to create the following groups and assign the maxadmin user to them. o=ibm.ou=users. An LDIF file with the following content needs to be created: Chapter 3.ou=SWG. DC=IBM and DC=COM indicate a domain forest of ibm. Installation tasks 57 .com.c=us objectClass: top objectClass: organization o: IBM dn: ou=SWG.c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm.ou=SWG. Here is an example of an LDIF file that uses default values: dn: o=ibm.ou=users. You can replace the example with the directory structure of your own organization. Define the required users and their position within the ou=users DN entries you created.c=us ou: SWG objectClass: top objectClass: organizationalUnit dn: ou=users.c=us ou: users objectClass: top objectClass: organizationalUnit dn: cn=wasadmin.ou=SWG.

ou=SWG.ou=SWG. o=ibm.ou=SWG.c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=mxintadm.o=IBM.ou=groups.c=US member: uid=maxreg. 23.o=IBM. run the following DB2 command on the computer: db2set -g DB2SYSTEM=virtual_hostname 58 IBM Tivoli Provisioning Manager Version 7.C=US objectclass: groupofnames cn: TPWEBSERVICEUSER member: uid=maxadmin.c=US member: uid=mxintadm.C=US objectclass: groupofnames cn: TPDEPLOYMENTSPECIALIST member: uid=maxadmin.o=IBM.ou=groups.c=US To create the users and update the membership of the LDAP repository.c=US dn:cn=TPCONFIGURATIONLIBRARIAN. If you are using a virtual IP address on the computer where Tivoli Directory Server is installed. remove the ^M characters from the file before using.ou=SWG.ou=users. 21.ou=SWG.c=US cn: maxadmin dn: cn=maximousers.o=IBM.ou=SWG.C=US objectclass: groupofnames cn: TPADMIN member: uid=maxadmin.O=IBM.ou=SWG.ou=SWG. In the IBM Tivoli Directory Server Configuration tool.c=US dn:cn=TPCOMPLIANCEANALYST.ou=groups.O=IBM.C=US objectclass: groupofnames cn: TPCONFIGURATIONLIBRARIAN member: uid=maxadmin.O=IBM.ou=SWG.ou=groups. o=ibm.c=US dn:cn=TPWEBSERVICEUSER.ou=groups.ou=groups.ou=SWG.O=IBM.ou=users.o=IBM.c=US cn: maximousers dn:cn=TPDEPLOYMENTSPECIALIST.c=US dn:cn=TPADMIN. Close the IBM Tivoli Directory Server Configuration tool and restart the server.ou=users.o=IBM.o=IBM.o=IBM.o=IBM.c=US dn:cn=TPDEVELOPER.ou=users.ou=SWG.c=us ou: groups objectClass: top objectClass: organizationalUnit dn: cn=maxadmin.ou=users.O=IBM. Click Browse to locate the LDIF file and click Import.o=ibm.ou=SWG.ou=SWG.ou=SWG.ou=SWG.ou=users.ou=SWG.ou=SWG.ou=users.dn: ou=groups.ou=SWG.ou=users.c=US member: uid=maxadmin.ou=users.ou=SWG. click Import LDIF data.o=IBM.ou=groups. run the following command: ldapmodify -a -D cn=root -w <password> -i <file_name> If you create the LDIF file on a Windows computer.ou=groups.C=US objectclass: groupofnames cn: TPCOMPLIANCEANALYST member: uid=maxadmin.ou=users.2 Installation Guide .C=US objectclass: groupofnames cn: TPDEVELOPER member: uid=maxadmin.ou=SWG.O=IBM.c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=maxadmin.o=IBM. 22.ou=users.

Click Next. Ensure that Use the following IP address is selected and enter the IP address and subnet mask for the server. To Install Microsoft Active Directory: Procedure 1. In the Welcome page. 3. In the Windows Control Panel. run this command on the computer ldap. On the Database and Logs panel. Click Next. perform the following steps: 1. Installing Microsoft Active Directory: You must manually install Microsoft Active Directory before installing Tivoli Provisioning Manager. so make a note of it. The first part of the DNS name is typically sufficient. Add a gateway if required. 8. This setting is required for the DNS and Active Directory subsystems.example. On the NetBIOS Domain Name panel. 2. Enter the IP address of the server in the Preferred DNS server field. v Install and configure DNS. enter the NetBIOS name of the domain.example. 9.example. click Next. 4. Click Details and select the Domain Name System check box. but do not select the check box if it was not already selected. 1. v The latest Windows 2003 service pack is installed. and click Properties. Click OK and then Next and complete the installation of DNS. This name will be used during Tivoli Provisioning Manager installation. 6. 4. 3. 7. Ensure that you log on to the computer with an administrator account to perform installation. Click Start > Control Panel > Network Connections. click Next. Before you begin Ensure that the computer meets the hardware and software requirements for Microsoft Active Directory on Windows 2003. 2. If it is not currently installed. Chapter 3. Select Internet Protocol (TCP/IP). Click Next. 3.com. select Domain controller for a new domain and click Next. Right-click the connection that represents your primary network adapter and click Properties. Click Networking Services in the list of components. select Domain in a new forest and click Next. 5. enter the DNS suffix for your new Active Directory. select the folders for the Database and Logs.Replace virtual_hostname with the virtual host name. On the New Domain Name panel. v The primary network card has a static IP address. The default value is C:\Windows\NTDS. In the Operating system compatibility panel. 5. On the Domain Controller Type panel. double-click Add or Remove Programs and then click Add/Remove Windows Components. 2. On the Create New Domain panel.com: db2set -g DB2SYSTEM=ldap. Example: If Tivoli Directory Server is installed on the computer with the virtual host name ldap. Installation tasks 59 .com What to do next Proceed to “Installing Tivoli Provisioning Manager core components” on page 119. Click electing Start > Administration Tools > Configure your Server . Requirements for use with Tivoli Provisioning Manager include: v Microsoft Active Directory must be installed on a separate computer.

b. for example. Click Next to continue. On the Shared System Volume panel. Right click the Groups OU and select New > Group. What to do next You are now ready to configure Microsoft Active Directory. and select New > Organizational Unit. Enter Users as the name for the new OU and click OK. 12. Create a group object under the SWG organizational unit: a. Click Next. Before you begin v While Microsoft Windows Server 2008 is supported as a platform for the administrative workstation. Select Permissions compatible only with Windows 2000 or Windows Server 2003. In the Microsoft Active Directory Users and Computers user interface. Right-click the SWG OU. Enter Groups as the name for the new OU then click OK. 6. Click Start > Control Panel > Administrative Tools > Microsoft Active Directory Users and Computers and then select the domain that you are working with. 5. Click Next 13. After successful installation. these default passwords can be changed to conform to a stricter security policy. Right-click the SWG OU. Click OK. click OK. The Microsoft Active Directory security policy might need to be altered temporarily to allow the creation of these accounts in the format described. v Use this procedure if you plan to create users and groups manually in Microsoft Active Directory. 4. Create a users object under the SWG organizational unit: a. 60 IBM Tivoli Provisioning Manager Version 7. 11. The installation program gives you the opportunity to have these users and groups created automatically during the installation. 7. v The users and passwords created in the following steps need to match this exact configuration for the deployment to succeed. 8. b. If you configured DNS successfully. the Permissions setting panel is displayed. provided that you have properly set up SSL communication between Microsoft Active Directory and IBM WebSphere Application Server. Create the MAXADMIN group: a. as described in “Configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment” on page 65. The server will be rebooted as part of the process.2 Installation Guide . Manually configuring Microsoft Active Directory: To manually configure Microsoft Active Directory for use with Tivoli Provisioning Manager. enter a valid password to be used when running the Directory Services in Restore Mode. complete these steps before installing Tivoli Provisioning Manager. 9. 10. enter a valid directory for the system volume. 2. right-click the domain you want to work with and select New > Organizational Unit. or for hosting middleware. Procedure 1. and select New > Organizational Unit. On the Directory Services Restore Mode Administrator Password panel. and then click OK. and then click Raise. Verify the settings and Click Next to begin the Active Directory configuration. Enter a name for the new Organizational Unit (OU). SWG.10. Edit the domain functional level by selecting Action > Raise Domain Functional Level. C:\Windows\Sysvol is the default. Microsoft Active Directory on Microsoft Windows Server 2008 is not supported. When the domain raise task has completed. Select Microsoft Windows Server 2003 from the Select an available domain functional level menu. 3.

Group dialog. Create the wasadmin user: a. User cannot change password Ensure this check box is selected. Group scope Global Group type Security 12. enter the following information and click Next: Password Enter the password for wasadmin.b. Chapter 3. This value must be capitalized. enter the following values and click OK. This value must have a minimum of eight characters. Installation tasks 61 . From the New Object . From the New Object . Right click the Groups OU and select New > Group. enter the following values and click Next. User must change password at next logon Ensure this check box is cleared.User dialog. b. Right click the Users OU and select New > User. This value must be capitalized. First name Enter wasadmin. This value must be capitalized. Group name Enter MAXADMIN. From the next panel. From the New Object . User login name Enter wasadmin in the first field. User login name (pre-Windows 2000) This field is filled with the same value (wasadmin) entered for the User login name. Group scope Global Group type Security 11. enter the following values and click OK. c. b. Group name (pre-Windows 2000) Enter MAXADMINPRE2K as the pre-Windows 2000 group name. Full name Enter wasadmin. Initials Leave this field blank. This value must be capitalized and must be different than the name entered for Group name. Group name (pre-Windows 2000) Enter MAXIMOUSERS as the pre-Windows 2000 group name. Group name Enter MAXIMOUSERS. Create the MAXIMOUSERS group: a. Last name Leave this field blank.Group dialog. Leave the default value of the second field.

Full name Enter maxadmin. Right click the Users OU and select New > User. 62 IBM Tivoli Provisioning Manager Version 7. Account is disabled Ensure this check box is cleared. First name Enter mxintadm.2 Installation Guide . User must change password at next logon Ensure this check box is cleared. 13. User login name (pre-Windows 2000) This field is filled with the same value (maxadmin) entered for the User login name. enter the following values and click Next. and then click Next: First name Enter maxadmin. d. b. This value must have a minimum of eight characters. enter the following values. From the New Object . The preceding values are examples. Account is disabled Ensure this check box is cleared. You must set these fields to values that comply with the password policy of your organization.User dialog. Initials Leave this field blank.Password never expires Ensure this check box is selected. and click Finish. Right click the Users OU and select New > User. Password Enter the password for maxadmin. Password never expires Ensure this check box is selected. Last name Leave this field blank. Review the password settings in the summary panel. From the next panel. Leave the default value of the second field. User cannot change password Ensure this check box is selected. The preceding values are examples. You must set these fields to values that comply with the password policy of your organization. enter the following information and click Next. Initials Leave this field blank. and click Finish. From the New Object . Create the maxadmin user: a. Create the mxintadm user: a. b. User login name Enter maxadmin in the first field. Last name Leave this field blank. 14. c. Review the password settings in the summary panel.User dialog. d.

enter the following values and click Next. 15. User login name (pre-Windows 2000) This field is filled with the same value (maxreg) entered for the User login name. d. User login name (pre-Windows 2000) This field is filled with the same value (mxintadm) entered for User login name.User dialog. and click Finish. c. This value must have a minimum of eight characters. Password never expires Ensure this check box is selected. enter the following information and click Next.Full name Enter mxintadm. From the next panel. The preceding values are examples. Right click the Users OU and select New > User. This value must have a minimum of eight characters. Last name Leave this field blank. Account is disabled Ensure this check box is cleared. First name Enter maxreg. User login name Enter maxreg in the first field. Full name Enter maxreg. Review the password settings in the summary panel. Password Enter the password for the maxreg user. enter the following information and click Next. Password Enter the password for mxintadm. From the next panel. From the New Object . Initials Leave this field blank. User login name Enter mxintadm in the first field. Leave the default value of the second field. Installation tasks 63 . Leave the default value of the second field. You must set these fields to values that comply with the password policy of your organization. Password never expires Ensure this check box is selected. Chapter 3. User cannot change password Ensure this check box is selected. User must change password at next logon Ensure this check box is cleared. Create the maxreg user: a. User cannot change password Ensure this check box is selected. c. b. User must change password at next logon Ensure this check box is cleared.

d. and maxreg users. 18. Click the Groups object under the SWG OU. From the Search results list. and then click OK. mxintadm. g. Review the password settings in the summary panel. Ensure that you are selecting the maxadmin user and not the maxadmin group from this list. Computers. Using the same procedure for creating the MAXADMIN group. click Advanced. Click the Groups object under the SWG OU. From the MAXIMOUSERS properties dialog. select the maxadmin. f. g. create the following groups: v TPADMIN v TPCOMPLIANCEANALYST v TPDEPLOYMENTSPECIALIST v TPDEVELOPER v TPWEBSERVICEUSER 19. click Find Now. select the maxadmin and mxintadm users and click OK. From the Search results list. From the MAXADMIN properties dialog. you must add the roles to both the LDAP and the Tivoli Provisioning Manager database using VMMSYNC. The preceding values are examples. Add users to the MAXADMIN group: a. Double-click the MAXIMOUSERS group listed in the Groups pane. or Groups dialog. b. Click OK. 16. Using the same procedure for adding the maxadmin user to the MAXADMIN group. c. b. click Advanced. Add users to the MAXIMOUSERS group: a. Exit the Microsoft Active Directory Users and Computers user interface. Contacts. and click Finish. You must set these fields to values that comply with the password policy of your organization. or Groups dialog.xml file as follows: <ws-security-role>TPWEBSERVICEUSER<\ws-security-role> To configure this group to use another role. Click OK. click Find Now. Contacts. 20. e. 17. Double-click the MAXADMIN group listed in the Groups pane. select the Members tab and then click Add. From the Select Users. From the Select Users. Ensure that you are selecting the maxadmin user and not the maxadmin group from this list. On the Advanced panel.2 Installation Guide . select the Members tab and then click Add. add the maxadmin user to the following groups: v TPADMIN v TPCOMPLIANCEANALYST v TPDEPLOYMENTSPECIALIST v TPDEVELOPER v TPWEBSERVICEUSER Note: The TPWEBSERVICEUSER group for the Web Service interface is configured in the user-factory. d.Account is disabled Ensure this check box is cleared. c. 64 IBM Tivoli Provisioning Manager Version 7. On the Advanced panel. f. e. d. Computers.

select the Use custom settings to generate the key pair and CA certificate option. you cannot use port 80 for IBM HTTP Server. Configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment: Configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment allows the installation program to create users. Changing the name or domain of the certificate authority at any point invalidates certificates previously issued from that authority. Then select Add/Remove Windows Components. e. generate a certificate. From the Public and Private Key Pair panel. Chapter 3. and then add that certificate to WebSphere Application Server Network Deployment. select Stand alone root CA. select SHA-1 as the Hash algorithm. enter DC=itsm. From the Windows Components panel. you must change it to another value because Microsoft Internet Information Services must use port 80. From the CA Identifying Information panel. and then click Next. select Add or Remove Programs. Add this component by selecting the Internet Information Services or Application Server component and installing it. Replace these values with the details of the computer hosting Microsoft Active Directory. set the Validity period to 5 years. c. and then click Next. Procedure 1. Microsoft Internet Information Services are a prerequisite of the certificate service. b. If you have IBM HTTP Server installed on the same system. Ensure that you have host name resolution set up properly in your environment. set the Key length to 2048.DC=com for the Distinguished name suffix. You must enable SSL for Microsoft Active Directory. select Microsoft Strong Cryptographic Provider for the CSP value. enter host_name. d.Results Microsoft Active Directory configuration is complete and you are now ready to install the remaining middleware and configure the application server to use Microsoft Active Directory. f. and then click Next. and then click Next.itsm. If IBM HTTP Server was configured to use port 80. proceed with setting up certificate services as described in this procedure. Installation tasks 65 . Ensure that you have already installed Microsoft Internet Information Services with ASP extensions enabled on the system before configuring the certificate service required for SSL. Add the Certificate Services component: a. Microsoft Internet Information Services can be added as a Windows component from the Add/Remove Programs dialog. you have to configure SSL communication between Microsoft Active Directory and WebSphere Application Server Network Deployment. The values used in this step are example values only. From the Certificate Database Settings panel. and then click Next. From the CA Type panel. After you verify that these two conditions are met. select the Certificate Services option. you can keep the default value of C:\WINDOWS\system32\CertLog for both the Certificate database and Certificate database log fields.com in the Common name for this CA field. Before you begin To enable the Provisioning Manager installation program to automatically create users and groups within Microsoft Active Directory. Configuration of the component now begins. From the Control Panel of the Microsoft Active Directory server. Communication failures occur if the computer hosting Microsoft Active Directory cannot resolve host names for systems that have been issued certificates.

Certificate Chain. From the File to Import panel of the Certificate Import wizard. b. f.itsm. select Certificates and then click Add. or CRL page select Current for the CA certificate value. Type of Certificate Needed Select Server Authentication Certificate.itsm. 5. Identifying Information Enter the fully qualified name of the computer hosting Microsoft Active Directory in the Name field. Launch Internet Explorer. specify the type as Security Certificate and save the security certificate file as serverRootCA. and then click Download a CA Certificate. d.g. From the Certificate Store panel. In the Microsoft Management Console. select Certification Authority and then click Add. click Add. Select Local computer: (the computer this console is running on) and click Finish. From the Add Standalone Snap-in dialog box. From the Certificate Services page. click Create and submit a request to this CA. Certificate Chain. Launch the Microsoft Management Console. click Next. Transfer certificates to a store: a. Create and submit a request to the CA: a. c. navigate to http://host_name. Enter http://host_name. Select File > Add/Remove Snap-in. 66 IBM Tivoli Provisioning Manager Version 7. b. click install this CA certificate chain. From the Request a Certificate page. d. Click Finish. From the Certificate Services page. and then click Finish.itsm. g. Click Close to close the Add Standalone Snap-in dialog box.com/certsrv. Certificate Chain. Select Computer account and then click Next. e. Select Local computer: (the computer this console is running on) and click Finish. select Base 64 for the Encoding method. h. c. Right-click Certificates and select All Tasks > Import. j. When prompted.ITSM. c. c. Add the Certificates Snap-in: a. or CRL page. g. and then click Close. From the Download CA Certificate. d. b. click Add. select it. and then click Next. click advanced certificate request. Click OK on the Add/Remove Snap-in dialog box to close it.COM. Restart the system. e. f. This value must be capitalized.com in the Add this web site to the zone: field.com/certsrv in the browser. i. h. b. d. When the task has completed successfully. Select Tools > Internet Options > Security and click Sites. click the back button. select Place all certificates in the following store.2 Installation Guide . click Download a CA certificate. From the Advanced Certificate Request page. From the Advanced Certificate Request page. Download a CA certificate: a.cer file. for example HOST_NAME. From the Add Standalone Snap-in dialog box. h. click Request a certificate. From the Trusted Sites dialog box. enter the following information and then click Submit. From the Add/Remove Snap-in dialog box. or CRL. From the Download a CA Certificate. 2. Using Internet Explorer.cer 3. enter http://host_name. navigate to Console Root > Certificates (Local Computer) > Third-Party Root Certification Authorities. 4. browse to the location of the serverRootCA.

From the Export Private Key panel. double-click the entry displayed in uppercase. select SSL. Additional Options Set the Request Format option to PKCS10. on the Certificate Services page. From the File to Export panel. Click Home to return to the home page for Certificate Services. d. In the Microsoft Management Console.cer.com > Pending Requests. b. or change it to a more appropriate value. b. start the Microsoft Management Console and navigate to Console Root > Certificates (Local Computer) > Personal > Certificates. and Store certificate in the local computer certificate store options. e. and then click Finish. From the Export File Format panel. Select Connect. Configure the connection: a. and then click OK.com for Server. 9. select SHA-1. Select Connection. c. click the certificate request you created. b. Review the information displayed to verify your configuration values. Install the certificate: a. 8. click Next. From the Certificate dialog box. From the Certificate Export wizard Welcome panel. Default values are sufficient for the remaining fields on this page. select No. Installation tasks 67 . d. From the Certificate dialog box.Key Options For the CSP field. Mark keys as exportable. export the certificate as serverRootCA. For the Hash Algorithm field. Export certificate files: a. Launch the Microsoft Management Console and navigate to Console Root > Certificates (Local Computer) > Personal > Certificates. From the View the Status of a Pending Certificate Request page. From Internet Explorer. double-click the entry displayed in lowercase. click Install this certificate. enter the same exact value as entered for the Name field.CER). When the system has restarted. e. From the Certificate Issued page. b. Verify the private key: a. and then click Next. Restart the system. In the right pane. Select the Automatic key container name. d. f. 7. 6. In the right pane. c. f. and then click OK.itsm. you can either accept the default value of 1024. Right-click the uppercase certificate entry and select All Tasks > Export c. Enter host_name. e. click View the status of a pending certificate request.509(.itsm. do not export private key. and then click OK. ensure you can find the statement You have a private key that corresponds to this certificate. d. For the Friendly Name field. 636 for Port. and then click Next. In the right pane. click Next. select Microsoft RSA SChannel Cryptographic Provider. right-click the ID of the request. and then select All Tasks > Issue. e. Launch the Microsoft LDP utility. navigate to Console Root > Certification Authority (Local) > host_name. ensure you can find the statement You have a private key that corresponds to this certificate. c. Chapter 3. select Base-64 encoded X. For the Key Size field.

CER). Securing WebSphere Application Server with Microsoft Active Directory using the middleware installation program: If you have an existing Microsoft Active Directory instance. and then click OK. enter the path (including the file name) to the serverAuthCert. From the Available realm definitions drop-down list. select No. i.cer file in the File name field. Click Signer certificates and then click Add. Port Update this value to 636. d. select Base-64 encoded X. k. 68 IBM Tivoli Provisioning Manager Version 7. and then click Finish. From the Certificate Export wizard Welcome panel. Click Supported entity types and verify that the PersonAccount entity type is set to cn. select Federated repositories. applications. you can use it to secure WebSphere Application Server when you install it on the system. Click Add. From the Add signer certificate page. From the WebSphere Application Server Network Deployment administrative console. b.2 Installation Guide . Start the WebSphere Application Server Network Deployment administrative console. Login properties Set this value to cn.cer to the WebSphere Application Server Network Deployment system.cer file in the File name field. j. f. g. e. click the PersonAccount entity type and set it and then save the changes. Click the repository identifier for Microsoft Active Directory listed in Repositories in the realm table. Configure security: a. d. h. enter the path (including the file name) to the serverRootCA. Enter MSADServerAuthCert for the Alias. c. 10. Copy serverRootCA.cer. and then click Next. If it is not set to cn. b. and then click OK. From the WebSphere Application Server Network Deployment administrative console. i. Click CellDefaultTrustStore. Click Keystores and certificates. or by using the middleware installation program. 11. and then click Next. g. and infrastructure. h. Restart the domain manager. select Security > SSL certificate and key management. click Next.509(. click Next. enter MSADServerRootCA for the Alias. From the File to Export panel. Add signer certificates: a. You can either configure it manually. Requires SSL communications Ensure that this option is selected. and then click Configure. Use specific SSL alias Ensure that this option is selected with a value of CellDefaultSSLSettings.Right-click the lowercase certificate entry and select All Tasks > Export. f. Update the following properties and then click OK. From the Export File Format panel. do not export private key. select Security > Secure administration. c. export the certificate as serverAuthCert. e.cer and serverAuthCert. From the Export Private Key panel.

you must manually create the users and groups listed in “Manually configuring Microsoft Active Directory” on page 60. you will be able to change the value of the Hostname field. Navigate the middleware installation program panels as instructed in “Installing and configuring the middleware with the middleware installer” on page 36. Select this option only if you want to manually specify the host name of the system instead of having the installation program programmatically detect it.DC=itsm. If you do not want to use this option. ignore the Use this password as the value for all subsequent passwords option. When this option is selected. and then click Next. In the Deployment Plan Summary window. 8.Before you begin Note that before running the Provisioning Manager installation program. DC=itsm. 4. or it is configured to support virtual IP addresses. complete the following steps: Procedure 1. For example. such as in cases where a system has more than one network interface. Directory server port Enter the directory server port. click Next to configure the parameters displayed. 389 LDAP base entry Enter the LDAP base entry of the instance. In the next panel. you will not be able to clear it.OU=SWG. Use this option when there is more than a single host name assigned to the system. For example. 6. Installation tasks 69 . Start the middleware installation program from the launchpad. However. select the Override the local machine hostname option and enter a host name value in the Hostname field. and then click Next. enter a password value. In the Configurable Host Name panel. 5. 3. If you launched the middleware installation program from the command line using the forceHostname=true parameter. you can change the value you enter in the Hostname field. and click Next. To have the middleware installation program use an existing Microsoft Active Directory instance to secure WebSphere Application Server. but it must be completed before you begin using the Provisioning Manager installation program. From the Deployment Choices panel. 9. Configure the following values for WebSphere Application Server security. Select Secure with Microsoft Active Directory. 7. LDAP Host name Enter the fully qualified name of the server hosting Microsoft Active Directory. In the Password Reuse panel. then you will be required to provide an alphanumeric value in the Hostname field. you can select Use this password as the value for all subsequent passwords. until you reach the Deployment Choices panel. You can perform this step after you have installed middleware using the middleware installation program. which will allow you to use the same password as the default user password value in all panels of the middleware installation program. You cannot clear this option once it has been selected. however. 2. if you want to manually specify the host name of the computer you are running the installation from. The middleware installation program will prompt you for LDAP configuration parameters to use with WebSphere Application Server. The deployment plan is generated and you will be provided details about the plan. An IP address will result in an error message. and click Next. and then click Next.DC=com Chapter 3. you will be given the choice of selecting an existing instance of IBMTivoli Directory Server or Microsoft Active Directory to secure WebSphere Application Server. you are required to provide a resolvable host name. Log on as a user with administrative authority. Once this option has been selected. clear the Directory Server deployment option. For example.DC=com User suffix Enter the user suffix for the instance. OU=Users.

boulder. Select the Create a deployment manager option. Select the Run the Application Server as a Windows service and log on as a local system account.nd. 11. Click Next in the Profile summary dialog box. Accept the default installation location. 3. Click Next. Complete the installation by navigating the remainder of the middleware installation program panels. For example. Click Next. see “Installing and configuring the middleware with the middleware installer” on page 36.CN=Users. Supply the following configuration values for WebSphere Application Server security. 4.html.2 Installation Guide . Launch the profile creation wizard. 10. 8.DC=com Organization container suffix Enter the organization container suffix for the instance.DC=itsm. Click Next. You must replace itsm with the name of your own domain.DC=com In this example. OU=Groups. You must replace itsm with the name of your own domain. For example. For 64-bit platforms. 10.ibm. and Cell name. For more informaton. DC=itsm. Review the assigned port numbers. 70 IBM Tivoli Provisioning Manager Version 7.websphere.DC=itsm. Click Next. 5. Click Next.Group suffix Enter the group suffix for the instance. 2.com/ infocenter/wasinfo/v6r1/index. To create WebSphere Application Server profiles before running the Tivoli Provisioning Manager installation program: 1. Bind distinguished name Enter the bind distinguished name for the instance. Accept the default values or specify the Node name. CN=Administrator.doc/info/ae/ae/tpro_profiles. Manually configuring WebSphere Application Server If you do not want the Tivoli Provisioning Manager installation program to configure WebSphere Application Server automatically. you must configure the application server manually before you use the Tivoli Provisioning Manager installation program. Creating WebSphere Application Server profiles: This procedure provides task information for creating WebSphere Application Server profiles. Host name.OU=SWG. Click Next in the Welcome dialog box. 9. Note the Administrative port number.jsp?topic=/com.DC=com This value assumes that the Administrator user is already a member of the itsm domain. For example. Select the Launch the First steps console option. Bind password Enter the password for the Administrator user on the system hosting Microsoft Active Directory. 7. Before you begin You cannot use the Profile Management tool to create profiles for 64-bit platforms.ibm. You will use this context when invoking the console through a browser. see Creating and deleting IBM WebSphere Application Server profiles at http://publib. Click Finish. Click Next. 6. and then click Next. itsm is the domain name. Accept the default value or specify a Profile name.

The root of each repository is mapped to a base entry within the federated repository. Note that if you intend to configure VMM to use SSL with a federated LDAP repository. 16. The values provided here are for example purposes only. Click Next. you must manually configure VMM. enter the values used during the installation and configuration of IBM Tivoli Directory Server. Configure SSL after the Tivoli Provisioning Manager installation program has completed successfully. Click Finish.11. 23. which is a starting point within the hierarchical namespace of the virtual realm. close it. Click the Installation verification link. a subtree within that repository. 21. 14. Click Next. The federated repository consists of a single named realm. Before you begin Ensure you have a wasadmin user created in your LDAP repository. Use the launchpad command and click the Profile creation wizard to open the First Steps window (if not open already). then it will. Specify a unique Profile name. the installation will fail. Click Exit. After Installation Verification completes. in the case of LDAP. the Tivoli Provisioning Manager installation program provided you with the option of automatically configuring Tivoli Provisioning Manager middleware. 13. Do not configure a WebSphere Application Server VMM LDAP federated repository to use SSL with an LDAP directory before installing Tivoli Provisioning Manager. which is a set of independent user repositories. Select Create a custom profile. Manually configuring Virtual Member Manager on WebSphere Application Server: This procedure provides task information for manually configuring Virtual Member Manager (VMM) to secure Tivoli Provisioning Manager. 15. substitute values you used in “Securing WebSphere Application Server with Microsoft Active Directory using the middleware installation program” on page 68 and “Manually Chapter 3. 12. If you chose to have the middleware installer program automatically configure the middleware. 19. Specify a unique node name and the computer name (or IP address) of the machine where you are performing this installation. VMM lets you access and maintain user data in multiple repositories. During the installation process. If you are using IBM Tivoli Directory Server. close the output window. perform Virtual Member Manager (VMM) configuration for you. it must be done only after a successful Tivoli Provisioning Manager installation. Review the port number listings. 22. among other tasks. Installation tasks 71 . Click Next. To add an LDAP directory to the VMM virtual repository. Click Next. Click Next. Accept the default directory path. you must first add the LDAP directory to the list of repositories available for configuration for the federated repository and then add the root of baseEntries to a search base within the LDAP directory. 20. Each repository can be an entire external repository or. Multiple base entries can be added with different search bases for a single LDAP directory. Accept the default values or specify the appropriate information. Select the Launch the First steps console check box. If you are using Microsoft Active Directory. 18. If VMM is configured to use SSL with a federated LDAP repository before completing the Tivoli Provisioning Manager installation. If another First steps window is open. Click Next in the Profile summary dialog box. and federate that data into a single virtual repository. Click Next. Click Next in the Welcome dialog box. If not. 17.

select ISMMSAD. enter CN=Administrator. You need to replace itsm with the name of your own domain. Repository identifier For IBM Tivoli Directory Server. select Microsoft Windows Server 2003 Active Directory.CN=Users. applications. Primary host name Enter the fully-qualified host name or IP address of the IBM Tivoli Directory Server or the Microsoft Active Directory server. 72 IBM Tivoli Provisioning Manager Version 7.DC=com This value assumes that the Administrator user is already a member of the itsm domain. enter cn=root For Microsoft Active Directory. For Microsoft Active Directory. select Federated repositories from the Available realm definition field and click Configure. 3.configuring Microsoft Active Directory” on page 60 where appropriate in this procedure. For Microsoft Active Directory. select Federated repositories from the Available realm definitions list. and infrastructure. Enter the following values. and save the change. click Security > Secure administration.2 Installation Guide . select ISMITDS. Locate the Repositories in the realm section and click Add Base entry to Realm. click Remove. and click Configure. Certificate mapping Select EXACT_DN. Click Add to create the repository definition under the current default realm. Note that if there is an existing file repository entry in the Repositories in the realm table. Support referrals to other LDAP servers Set to ignore. and infrastructure. 2. Login properties Leave this value blank. For Microsoft Active Directory. Repository For IBM Tivoli Directory Server. enter ISMMSAD. To return to the Federated repositories page. 6. click Apply and click Save. Locate the User account repository section. applications. click Apply and click Save. Click Manage repositories located under Related Items. Log on to the admin console and go to Security > Secure administration. 7. To add IBM Tivoli Directory Server or Microsoft Active Directory to Virtual Member Manager: Procedure 1.DC=itsm. Bind password Enter the password for the bind distinguished name. 8. Enter the following values. 4. you must select it. after creating the new entry. Directory type For IBM Tivoli Directory Server. 5. Bind distinguished name For IBM Tivoli Directory Server. enter ISMITDS. You will also have to modify the VMMCRONTASK as shown in “Manually configuring directory synchronization for WebSphere Application Server Network Deployment” on page 134. select IBM Tivoli Directory Server Version 6. Port Enter 389.

DC=itsm. enter or verify the following values. From the OrgContainer configuration page. enter DC=itsm.DC=com This value assumes that the Administrator user is already a member of the itsm domain. 10.DC=com This value assumes that the Administrator user is already a member of the itsm domain.o=IBM. Base entry for the default parent For IBM Tivoli Directory Server. Relative Distinguished Name properties Enter cn 14.c=US For Microsoft Active Directory. Chapter 3. 11. 12. Relative Distinguished Name properties Enter uid. 13. Primary administrative user name Enter wasadmin. Entity type Verify that the value is PersonAccount.DC=itsm.o=IBM. Base entry for the default parent For IBM Tivoli Directory Server. You need to replace itsm with the name of your own domain.c=US For Microsoft Active Directory. From the Federated repositories configuration page. enter the following values. Ignore case for authorization Select this check box. 9. Click Supported entity types and click Group. enter ou=SWG.ou=SWG.c=US For Microsoft Active Directory. Server user identity Select Automatically generated server identity.ou=SWG. enter ou=users. Distinguished name of a base entry in this repository For IBM Tivoli Directory Server. You need to replace itsm with the name of your own domain. enter CN=Groups. enter the following values. Click Supported entity types. Realm name Enter ISMRealm.Distinguished name of a base entry that uniquely identifies this set of entries in the realm For IBM Tivoli Directory Server. enter CN=Users. From the PersonAccount configuration page. enter DC=itsm. This value must be a valid user from the configured LDAP repository.DC=com This value assumes that the Administrator user is already a member of the itsm domain.o=IBM. enter ou=groups. You need to replace itsm with the name of your own domain. From the Group configuration page. and then click OrgContainer.c=US For Microsoft Active Directory.o=IBM. enter ou=SWG. click OK and click Save. click Apply and click Save.DC=com This value assumes that the Administrator user is a member of the itsm domain. 15. Installation tasks 73 . click OK and click Save. Click Supported entity types and click PersonAccount. enter the following values: Entity type Verify that the value is Group. You need to replace itsm with the name of your own domain.

ear. c.bat Configuring Virtual Member Manager for Maximo authentication: This procedure provides task information for configuring Virtual Member Manager (VMM) for Maximo. a. <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. Click Set as current. Deploy WIM. <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode. enter DC=itsm. 19.ear" wsadmin>set attrib {} wsadmin>append attrib "-appname $wimAppname -cell $wimCell -node $wimNode -server $wimServer -systemApp" wsadmin>$AdminApp install $wimEar $attrib d. b. 17.cn 16. b. Enable Enable application security. <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager. that are hosting the authentication service client.2 Installation Guide . applications. Exit the wsadmin shell by typing exit. Deselect Use Java 2 security to restrict application access to local resources. Log on to the wsadmin shell by opening a command prompt and issuing the following command: wsadmin.bat c. applications. Base entry for the default parent For IBM Tivoli Directory Server. 18. Save the configuration: wsadmin>$AdminConfig save e. 74 IBM Tivoli Provisioning Manager Version 7. click Apply and click Save. d. Deploy the file: wsadmin>set wimAppname "WIM" wsadmin>set wimCell "ctgCell01" wsadmin>set wimNode "ctgCellManager01" wsadmin>set wimServer "dmgr" wsadmin>set wimEar "/opt/IBM/WebSphere/AppServer/systemApps/wim. Restart WebSphere Application Server and the managed nodes by running the following commands: a. Navigate to Security > Secure administration.bat b. e. WIM ear must be deployed in order for Provisioning Manager to launch in context to systems. select Federated repositories. <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode. You need to replace itsm with the name of your own domain. such as TADDM servers. Relative Distinguished Name properties Enter o. Open a command prompt on the system that hosts WebSphere Application Server. and infrastructure.ou.c=US For Microsoft Active Directory. enter ou=SWG.Entity type Verify that the value is OrgContainer.o=IBM. and change directory to WAS_HOME\bin.bat -username <WebSphere Admin User ID> -password <WebSphere Admin Password> c.dc. From Available realm definition. and infrastructure configuration page. From the Secure administration. a.bat d. complete the following fields. Enable Enable administrative security.DC=com This value assumes that the Administrator user is already a member of the itsm domain.

click Apply and then click Save. applications. Ignore case for authorization Select this check box. Enable Administrative security. Restart WebSphere Application Server and the managed nodes by running the following commands: a. v From the Available realm definitions. 4. 6. among other tasks. Invoke a browser window and open the administrative console by typing: http:// <server_name>:9060/admin.bat Configuring WebSphere Application Server Network Deployment: Use this procedure to perform WebSphere Application Server Network Deployment configuration tasks. Primary administrative user name Enter wasadmin. Disable Application security. select Federated repositories from the Available realm definition field and click Configure. Deselect Use Java 2 security to restrict application access to local resources. Locate the User account repository section. If not. <WAS_HOME>/profiles/ctgDmgr01/etc/trust. 2. then it will. and then click Save. Log on to the admin console and go to Security > Secure administration. Installation tasks 75 . enter the following values. 3. Chapter 3. you must manually configure VMM. perform Virtual Member Manager (VMM) configuration for you. From the Federated repositories configuration page. Enter a user name to log in. This URL address depicts the default port number (9060) and context (admin) for the administrative console.p12. Realm name Enter defaultWIMFileBasedRealm. Procedure 1. <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode. applications. applications. If you choose to manually configure Provisioning Manager middleware for use with Provisioning Manager. 5. <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode. and infrastructure. 7. From the Secure administration. For example. you must manually configure the WebSphere Application Server Network Deployment.bat c. enter the password for the wasadmin user and click OK. Manually copy the keystore file from the WebSphere Application Server Network Deployment manager host to a temporary directory on the administrative workstation. Navigate to Security > Secure administration. complete the following fields. <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager. click Apply and then click Save.bat b. Server user identity Select Automatically generated server identity.If you chose to have the middleware installer program automatically configure the middleware.bat d. <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. select Federated repositories and Set as current. Procedure 1. Note the browser is redirected to a secure port (9043). 2. In the General Properties. and infrastructure. v v v v Click Apply. and infrastructure configuration page. You need this keystore later during installation.

3. and click MXServer from the main window. d. 76 IBM Tivoli Provisioning Manager Version 7. Click the Host Aliases link. h. Accept all default settings and click Next. g. From the Server Infrastructure group. Click Finish. click maximo_host. Select the check box beside MXServer. From the System administration link in the navigation tree click Deployment manager. e. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum Heap Size and click OK. c. Open the Web Container Settings and click Web container transport chains. Click Process Definition.2 Installation Guide . 5. Click Java Virtual Machine. d. Click Apply. Accept default settings and click Next. c. From the Servers link in the navigation tree click Application servers. Click OK. Click New. From the Servers link in the navigation tree click Application servers. Create the virtual host. e. b. Click Save in the messages box. Click Save. f. a. Click Virtual Hosts. Expand Servers > Application servers. Click MXServer in the main window. In the General Properties section. This step is only necessary if you did not install WebSphere Application Server Network Deployment using the middleware installation program. Click New. From the Virtual Hosts window. Edit JVM Memory Settings for the application server. 4. a. Edit JVM Memory Settings for the deployment manager. b. Click New. b. From the Server Infrastructure group. 7. Click Start. d. Click Save in the messages box. g. 8. b. b. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum Heap Size and click OK. Type MXServer and click Next. Identify the HTTP Transfer Port Numbers. Click Save. Expand the Environment link from the navigation tree. a. type maximo_host in the Name box. g. Start the application server. Select the Synchronize changes with Nodes check box. e. c. a. c. Click Java Virtual Machine. and then click Apply. Note the default port number as it appears with WCInboundDefault (9080). 6. h. Click Process Definition. f. expand the Java and Process Management link. c. i. a. b. Expand the Servers link and click Application servers. a. d. c. f. e. expand the Java and Process Management link. i. f. Create the MXServer Application Server. j. Click Preferences.

y. Click OK.j. expand the Java and Process Management link. w. l. v. Click OK. z. f. Click Save. Close the command prompt. t. You can optionally start the node agent as a Windows service. 9. o. Click OK. Click MXServer in the main window. Type * (asterisk) for Host Name and type 9061 for the port number. WebSphere Application Server management: The tasks contained in this section must be performed regardless of whether you chose to install a new instance of WebSphere Application Server.log" -restart true where <WAS_HOME> is the directory where WebSphere Application Server is installed. p. Click OK. Installation tasks 77 . Click New. you can create a Windows service for starting the WebSphere node agent. Open a command prompt. Type * (asterisk) for Host Name and type the HTTP port number (by default 80). From the Server Infrastructure group. Creating a Windows service for the node agent: If your WebSphere Application Server is hosted on a Windows system. Type * (asterisk) for Host Name and type 9443 for the port number. 2. r. e. 4. Click Monitoring Policy. or chose to reuse an existing server. b. q. c. s. From the navigational breadcrumb trail. Click OK. Set Node restart state to RUNNING and click OK. 1. Click New. d. From the Servers link in the navigation tree click Application servers. Type * (asterisk) for Host Name and type 9044 for the port number. Change directory to <WAS_HOME>\bin. IBM provides comprehensive information about running and administering WebSphere Application Server at this URL: Chapter 3. Click Apply and then click OK. Type * (asterisk) for Host Name and type 9080 for the port number. WASService -add NodeAgent -serverName nodeagent -profilePath "<WAS_HOME>\profiles\Custom01" -wasHome "<WAS_HOME>" -logRoot "<WAS_HOME>\profiles\Custom01\logs\nodeagent" -LogFile "<WAS_HOME>\profiles\Custom01\logs\nodeagent\startServer. k. u. Click New. click maximo_host. Type the following command with no line breaks (case sensitive). Click Save. Enable automatic startup of the application server when the node agent is started: a. n. x. Click New. 3. m.

and click Start the service.bat %WAS_HOME%\profiles\ctgAppSrv01\bin\startNode.bat webserver1 Alternatively. Select the check box next to MXServer. Click Start. where host_name is the host name of the WebSphere Application Server and 9060 is the default port number for the administrative console. 3.com/infocenter/wasinfo/v6r1/index. Open a browser window and enter the following web address: http://host_name:9060/ibm/console 2. 2. Start the web server: %WAS_HOME%\profiles\ctgAppSrv01\bin\startServer.bat %WAS_HOME%\profiles\ctgDmgr01\bin\stopManager. Click Start. complete the following steps: 1. To start the MXServer application. click Servers > Application Servers. Before you begin Before you start the administrative console. Table 17.2 Installation Guide .bat 3. 3. and select Run. 4. Listing of server processes Server HTTP Server Go To %HTTP_SERVER_HOME%\bin\apache -k start %HTTP_SERVER_HOME%\bin\apache -k stop Deployment Manager Node Agent %WAS_HOME%\profiles\ctgDmgr01\bin\startManager. Type services.http://publib. Start the Node: %WAS_HOME%\profiles\ctgAppSrv01\bin\startNode. Select IBM Tivoli Directory Server Instance V6.bat %WAS_HOME%\profiles\ctgAppSrv01\bin\stopNode.bat 2. 78 IBM Tivoli Provisioning Manager Version 7. 1.ibm.msc and click OK.idsccmdb. you can start the MXServer from the WebSphere Application Server administrative console. verify that these server processes are running.boulder.2 . Start the Deployment Manager: %WAS_HOME%\profiles\ctgDmgr01\bin\startManager.bat ITDS Instance 1. 5.jsp Starting and stopping the WebSphere Application Server: This procedure provides task information for starting and stopping the WebSphere Application Server. if one is required. An application server named MXServer was created during installation. From the administrative console navigation pane. the name of the WebSphere Application Server. Enter an administrative user ID and password to log in.

where host_name is the host name of the WebSphere Application Server and 9060 is the default port number for the administrative console. an administrator cannot assign users and groups to the administrative user roles and administrative group roles including the adminsecuritymanager role. applications. and the permission that is required to access sensitive data. if one is required. Select the check box next to MXServer. For example. you can assign users and groups to the adminsecuritymanager role on the cell level through wsadmin scripts and the administrative console. First you identify users (or groups) that are defined in the active user registry. Open a browser window and enter the following web address: http://host_name:9060/ibm/console 2. and infrastructure > Administrative Group Roles to view the available administrative group roles. Users granted this role can perform both configuration actions and runtime operations on applications. 4. click Servers > Application Servers. The roles determine the administrative actions that a user can perform. the name of the WebSphere Application Server. Has monitor permissions and can change the runtime state. After enabling security. Click Stop. 5. From the administrative console navigation pane. Click Security > Secure administration. you can determine their level of access by assigning roles. Chapter 3.To stop the administrative console: 1. However. However. iscadmins Note: To manage users and groups. Installation tasks 79 . Securing the WebSphere Application Server Administrative Console: You can secure the Administrative Console so that only authenticated users can use it. you perform several steps to secure the console. You can use the Administrative Group Roles page to give groups specific authority to administer application servers through the administrative console. Has monitor permissions and can change the application server configuration. 3. Using the adminsecuritymanager role. you can assign users and groups to the administrative user roles and administrative group roles. Administrative group roles and permissions Admin Role Administrator Operator Configurator Monitor deployer adminsecuritymanager Description Has operator permissions. Has the least permissions. Fine-grained administrative security is available using wsadmin only. After you decide which users you want to access the console. configurator permissions. This role primarily confines the user to viewing the application server configuration and current state. click Users and Groups in the console navigation tree and then click either Manage Users or Manage Groups. Once you have enabled VMM for WebSphere Application Server security. a user must enter a valid administrator user ID and password to access the console. VMM must have been configured on the server where WebSphere Application Server is installed before securing the console. the operator can start or stop services. Table 18. Enter an administrative user ID and password to log in. Has administrator privileges for managing users and groups from within the administrative console only.

4. C:\Program Files\IBM\WebSphere\AppServer\ profiles logRoot Folder location of MXServer log file. Different roles can have different security authorizations. profilePath The profile directory of the server. for example. 9. 4.2 Installation Guide . 3. 6. WASService add MXServer serverName MXServer profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ ctgAppSrv01wasHome <D:>\IBM\WebSphere\AppServer 80 IBM Tivoli Provisioning Manager Version 7. Select MXServer and click Start. Click Servers > Application Servers.log) restart Restarts the existing service automatically if the service fails when set to true. 2. C:\Program Files\IBM\WebSphere\AppServer\bin. Users and groups are associated with roles defined in an application when the application is installed or configured. C:\Program Files\IBM\WebSphere\AppServer\ profiles\ctgAppSrv01 wasHome Home folder for MXServer. Select MXServer and click Stop. for example. Enter the following WASService command and press Enter. MXServer. Select the role and click either Look up users or Look up groups. Select Applications > Enterprise applications > application_name. Click >> to add users from the Available list to the Selected list. Run the WASService command with the following parameters: serverName Name of Maximo application server. Restart all the application servers. Enter an administrative user ID and password.Complete the following steps to map users and groups to security roles: Procedure 1. click Security role to user/group mapping. 5. for example. 3. for example. To configure WebSphere Application Server to run as a Windows service: Procedure 1. Use the Search pattern field to display users in the Available list. Configuring WebSphere Application Server to run as a Windows service: Configuring WebSphere Application Server to run as a Windows service can make it more convenient to manage. Under Detail properties. C:\Program Files\IBM\WebSphere\ AppServer\logs\ manageprofiles\ctgAppSrv01 logFile Log file name for MXServer (startServer. 7. Mapping users or groups to a role authorizes those users or groups to access applications defined by the role. Start the WebSphere Application Server Administrative Console by opening a browser window and entering the following URL: http://<host_name>:9060/ibm/console 2. Navigate to the bin folder where you installed the Maximo application server. 8. Open a command prompt window.

C:\Program Files\IBM\WebSphere\ AppServer\logs\manageprofiles\ ctgAppSrv01 logFile Log file name for node agent (startServer. for example. Change the Startup type field value to Automatic. for example. 4.log). then click OK. Enter the following WASService command and press Enter. Chapter 3. WASService -add NodeAgent -serverName nodeagent -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 -wasHome <D:>\IBM\WebSphere\AppServer -logRoot <D:>\IBM\WebSphere\AppServer\logs\nodeagent -logFile <D:>\IBM\WebSphere\AppServer\logs\nodeagent\startServer. Navigate to the bin folder where you installed the node agent. Configuring the WebSphere Application Server node agent to run as a Windows service: A node agent is a server running on every host computer in the deployed network. 3. Open a command prompt window. restart Restarts the existing service automatically if the service fails when set to true. C:\Program Files\IBM\WebSphere\AppServer\ profiles logRoot Folder location of node agent log file.0 Administrative Console by opening a browser window and entering the following URL: http://<host_name>:9060/ibm/console 2. 5. 7.log -restart true 8. 11. Open a Services window and double-click nodeagent. for example. 6. for example. Click Start to start the service. To configure the WebSphere Application Server node agent to run as a Windows service: Procedure 1. nodeAgent.logRoot C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01 logFile C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01\startServer. nodeagent). Run the WASService command with the following parameters: serverName Name of node agent. 12. C:\Program Files\IBM\WebSphere\AppServer\bin. click System Administration > Node agents. Installation tasks 81 . Enter an administrative user ID and password. for example. and click Stop.log restart true 10. Start the WebSphere Application Server 6. Open a Services window and double-click MXServer. It performs administrative functions. In the System Administration pane. To stop the node agent. profilePath The profile directory of the server. C:\Program Files\IBM\WebSphere\AppServer\ profiles\ctgAppSrv01 wasHome Home folder for MXServer. select the check box beside the name of the Node Agent (for example. Configuring the WebSphere Application Server node agent to run as a Windows service can make it easier to manage.

These instructions are provided for configuring the authentication service manually. and change directory to <WAS_HOME>/bin. 5.ScriptingException: WASX7280E: An application with name "authnsvc_ctges" does not exist.ear file: If nodeName was set to the default value by the middleware installation program. 10. Deploy the IBMESSAuthnSvc. Application Server. wsadmin>$AdminApp install <file_path>/IBMESSAuthnSvc. TADDM.bat -username <WebSphere Admin> -password <WebSphere Admin password> <WAS_HOME>\profiles\ctgAppsrv01\bin\startManager.bat <WAS_HOME>\profiles\ctgDmgr01\bin\startServer.1_GA directory of the Middleware DVD for your operating system and platform. exception information: com. the value is MXServer.bat <WAS_HOME>\profiles\ctgAppsrv01\bin\startNode. and then click OK. for example.2 Installation Guide .bat MXServer -username <WebSphere Admin> -password <WebSphere Admin password> <WAS_HOME>\profiles\ctgAppsrv01\bin\stopNode.ear {-usedefaultbindings -deployws -appname authnsvc_ctges–node (n 82 IBM Tivoli Provisioning Manager Version 7. This allows you to launch in context from Tivoli Provisioning Manager to the user interface of another server. Restart Deployment Manager.9. Verify that you do not already have authentication services deployed: wsadmin>$AdminApp view authnsvc_ctges This command returns an exception similar to the following: WASX7015E: Exception running command: "$AdminApp view authnsvc_ctges". If serverName was set to the default value by the Tivoli Provisioning Manager installation program. 2. Change the Startup type field value to Automatic. The middleware installer installs and configures the authentication service when used to install the middleware. 6. Log onto the wsadmin shell by opening a command prompt and issuing the following command: v wsadmin.ws.scripting. Manually configuring the authentication service: Use this information to manually configure the authentication service. provided that it has the authentication client installed and shares the same directory server for authentication.ear file to your local system. Before you begin This section provides information you can use to manually configure an authentication service on Tivoli Provisioning Manager that will provide the authentication for launch in context.bat MXServer 3. the value is ctgNode01. To configure the authentication service: Procedure 1. This file is located in the <Operating System>\WS-ESS_6. you are only required to authenticate once to the server hosting the client. Click Start to start the service.exe -username <WebSphere Admin User ID> -password <WebSphere Admin Password> 4.ibm. and MXServer using the correct profile names: <WAS_HOME>\profiles\ctgAppsrv01\bin\stopServer. Copy the IBMESSAuthnSvc. Under this scenario. Open a command prompt on the system that hosts WebSphere Application Server.bat -username <WebSphere Admin> -password <WebSphere Admin password> <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager.

15. Restart WebSphere and the managed nodes: <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.0. Manually configuring JMS queues: This procedure provides details on steps to configure JMS queues.sh <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.*] wsadmin>$AdminControl invoke $dmgr syncActiveNodes true 17.security. 13. Configure the service: wsadmin>$AdminTask configureESS 14. Chapter 3.bat 18.bat v <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.6. Refer to the “Configuring the client authentication” topic contained in the “Configuring for WebSphere federated repositories” section of the TADDM administrator's guide for more information about configuring client authentication. 11. Stop and restart WebSphere and the managed nodes: v <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode.sh -username <WebSphere Admin> -password <WebSphere Admin password> 10.1_GA directory of the Middleware DVD for your operating system and platform. Log back into the wsadmin shell. Copy the com.2.ibm. Ensure that all clients connecting to the service use the new export key file you generate. you will need to create a key. Synchronize the configuration: wsadmin>$AdminConfig save wsadmin>set dmgr [$AdminControl completeObjectName type=DeploymentManager.server_config. 9. Export the newly created key: wsadmin>$AdminTask exportESSLTPAKeys {-pathname <path_name>} For example: wsadmin>$AdminTask exportESSLTPAKeys {-pathname /root/avenESSLTPAKeyFile. Add the role called TrustClientRole to the WebSphere administrator user that you specified during the TADDM installation.bat -username <WebSphere Admin> -password <WebSphere Admin password> v <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager.jar file to the <WAS_HOME>/plugins directory on your local system. 16.bat -username <WebSphere Admin> -password <WebSphere Admin password> v <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. Installation tasks 83 .exported} 19. Create an LTPA Key: wsadmin>$AdminTask createESSLTPAKeys {-password <password>} If the key password is ever lost. Verify that the service is configured: wsadmin>$AdminTask isESSConfigured This command returns a value of true. This file is located in the <Operating System>\WS-ESS_6.sh -username <WebSphere Admin> -password <WebSphere Admin password> <WAS_HOME>/profiles/ctgDmgr01/bin/stopManager.ess. Exit the wsadmin shell by typing exit.7. Save the configuration: wsadmin>$AdminConfig save 8. Stop WebSphere Application Server and the managed nodes: <WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode.sh 12. which must be completed before deploying Tivoli Provisioning Manager EAR files. This will provide added security for the authentication service by restricting the users that can authenticate to the authentication service to only those with the TrustClientRole role.

4. click Add to open the Add a new bus member dialog box. unique ID (UUID). 3. Click New to open the Buses > New dialog box where you can add a new service integration bus. 9. 12. Click Next. 7. Click Service Integration > Buses to open the Buses dialog. 11. v The Secure option is unchecked. enter a URL similar to the following sample URL: http://localhost:9060/ibm/console 3. At the login screen. Click intjmsbus to open the Buses > intjmsbus dialog box. and then click Apply. If you elected to have the Tivoli Provisioning Manager installation program automatically configure the middleware. 13. then it will. If you leave this box checked. 4. 6. 84 IBM Tivoli Provisioning Manager Version 7. then click Log in. This action opens the Welcome screen for the WebSphere Application Server Administrative Console. Launch Internet Explorer and open the WebSphere Application Server Administrative Console by typing the following URL: http://<server_name>:<port_number>/ibm/console For example. Under Topology. Click Finish. 2. Click System administration > Console preferences.Before you begin During the installation process. Adding a server to the service integration bus: A server must be defined for the service integration bus. 8. 10. In the Buses > intjmsbus > Bus members dialog box. 5. selecting MXServer. Start the WebSphere Application Server. v Auto-generated. 2. you will have to manually configure these message queues. If you elected to manually configure Provisioning Manager middleware for use with Provisioning Manager. Click Save. 4BCAC78E15820FED. Deselect the Bus security check box. the Tivoli Provisioning Manager installation program provided you with the option of automatically configuring the middleware. From the WebSphere Application Server Administrative Console. Procedure 1. Start the MXServer server by navigating to Servers > Application Servers. enter your User ID. click Service Integration > Buses to open the Buses dialog box. To configure the JMS queues: Procedure 1. Confirm that the build completed screen displays the following information: v Bus name. Enter intjmsbus as the name of the new bus in the Name field. among other tasks.2 Installation Guide . and then clicking Start. intjmsbus inherits the Global Security setting of the cell. click Bus members. Select the Synchronize changes with Nodes option. create and configure JMS message queues for you. A bus is a group of interconnected servers and clusters that have been added as members of the bus. intjmsbus. This step propagates the JMS bus setup to the cluster configuration. for example. for example.

14. 7. Click OK. lower the threshold value if a higher value is degrading system performance. and then click Apply. 8. If you decide to change the High message threshold setting after the initial configuration. then click Finish to complete the creation of the CQINBD bus destination queue. the application server will take action to limit the addition of new messages in the processing queues. Click the Server drop-down arrow. 10. 4.5. for example. Check that the File store radio button is selected. click Next. 13. From the Provide the message store properties panel. Change the value of the High message threshold field to a minimum value of 500. You might. Click Finish. Click intjmsbus to open the Buses > intjmsbus dialog box. If the number of messages awaiting processing exceeds the High Message Threshold you set. is a virtual place within a service integration bus where applications can attach and exchange messages. A bus destination. Installation tasks 85 . From the WebSphere Application Server Administrative Console. and select the server name ctgNode01:MXServer to add to the bus. click Service Integration > Buses to open the Buses dialog box. Type CQINBD in the Identifier field and Continuous Queue Inbound in the Description field. 6. Depending on your message requirements. Before you begin To add a logical address for the continuous inbound bus destination queue (CQINBD) within the JMS bus. 9. Click Next to open the Confirm queue creation dialog box.000 messages. 2. for example CQINBD. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer as the bus member that will store and process messages for the CQINBD bus destination queue. 6. you might want to enter a higher message threshold value. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. then click Next to open the Create a new queue for point-to-point messaging dialog box. 9. Click Save. and click Next to open the Create new queue dialog box. Click Save. 11. 7. Leave Queue checked as the destination type. Creating the service integration bus destination for the continuous inbound (CQINBD) queue: You must create a service integration bus destination for the continuous inbound (CQINBD) queue. 8. You can determine an optimal message threshold setting by monitoring the messaging in/out queues and the impact of the message threshold setting on system performance. 12. 5. Review your selections. you must open the Additional Properties menu in the Administrative Console and change the threshold value for each child configuration. and then click Next. Click OK. and then click Next. Select intjmsbus. 3. Chapter 3. Click New to open the Create new destination dialog box. complete the following steps: Procedure 1.

Click New to open the Create new destination dialog box. Click Save. Click intjmsbus to open the Buses > intjmsbus dialog box. is a virtual place within a service integration bus where applications can attach and exchange messages. A bus destination.2 Installation Guide . Creating the service integration bus destination for the sequential inbound (SQINBD) queue: You must create the service integration bus destination for the sequential inbound (SQINBD) queue. Click Next to open the Confirm queue creation dialog box. Click None as the Exception destination value. complete the following steps: Procedure 1. 2. then click Finish to complete the creation of the SQINBD bus destination queue. 3. Navigate the path Buses > intjmsbus > Destinations. then click SQINBD to open the configuration dialog box. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. Leave Queue checked as the destination type. 7. 86 IBM Tivoli Provisioning Manager Version 7. 6. To add a logical address for the sequential outbound bus destination queue (SQOUTBD) within the service integration bus. 13. From the WebSphere Application Server Administrative Console. To add a logical address for the sequential inbound bus destination queue (SQINBD) within the service integration bus. 11. 8. and click Next to open the Create new queue dialog box. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the Description field. 12. complete the following steps: Procedure 1. Click Save. 10. then click CQINBD to open the configuration dialog box. 3. 11. then click Next to open the Create a new queue for point-to-point messaging dialog box. Click Apply. Creating the service integration bus destination for the sequential outbound (SQOUTBD) queue: You must create the service integration bus destination for the sequential outbound (SQOUTBD) queue. 4. 13. 4. 2.10. Click None as the Exception destination value. Review your selections. 9. 5. Note that you must use this value and it must contain only uppercase letters. Click Apply. Click New to open the Create new destination dialog box. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. 12. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer. Navigate the path Buses > intjmsbus > Destinations. click Service Integration > Buses to open the Buses dialog box. Click intjmsbus to open the Buses > intjmsbus dialog box. From the WebSphere Application Server Administrative Console. click Service Integration > Buses to open the Buses dialog box. for example SQOUTBD.

Click New. Note that you must use this value and it must contain only uppercase letters. click Resources > JMS > Queues. then click SQOUTBD to open the configuration dialog box where you must make the following changes: a. 4. 5. From the WebSphere Application Server Administrative Console. Click Apply. 3. 6. c. 7. Creating the continuous inbound (CQIN) JMS queue: You must create a JMS queue (CQIN) as the destination for continuous inbound point-to-point messages. complete the following steps: Procedure 1. 4. Navigate the path Buses > intjmsbus > Destinations. 8. Enter the following information. click Resources > JMS > Connection factories. then click Next to open the Create a new queue for point-to-point messaging dialog box. 2.5. 10. 2. and click Next to open the Create new queue dialog box. JNDI name Enter jms/maximo/int/cf/intcf Bus name Select intjmsbus. 5. Click OK. Click Save. Procedure 1. Leave Queue checked as the destination type. 8. then click Finish to complete the creation of the queue. To create the CQIN JMS queue. 6. Installation tasks 87 . Click Next to open the Confirm queue creation dialog box. 3. Name Enter CQIN. Enter the following information: Name Enter intjmsconfact. From the Scope list select Cell=ctgCell01. Click New. Click None as the Exception destination value. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer as the bus member that will store and process messages for the SQOUTBD bus destination queue. Chapter 3. select Cell=ctgCell01. From the Scope drop-down list. 9. Verify that the Default Messaging Provider is selected and click OK. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the Description field. 7. Click Apply. and click OK. Review your selections. Click Save Creating the JMS connection factory: Add a connection factory for creating connections to the associated JMS provider of point-to-point messaging queues. b. From the WebSphere Application Server Administrative Console. Verify that the Default Messaging Provider is selected and click OK.

click Resources > JMS > Queues. 3. Queue name Select CQINBD. Creating the sequential outbound (SQOUT) JMS queue: You must create a JMS queue (SQOUT) as the destination for sequential outbound point-to-point messages. complete the following steps: Procedure 1. 5. select Cell=ctgCell01. Enter the following information. To create the JMS queue (SQOUT). Enter the following information. Note that this value must contain only uppercase letters. 4. Click OK. Click New. From the WebSphere Application Server Administrative Console. select Cell=ctgCell01. From the Scope drop-down list. Name Enter SQOUT. Click OK. 5. Click Save. 7. 6. Verify that the Default Messaging Provider is selected and click OK. 88 IBM Tivoli Provisioning Manager Version 7. Queue name Select SQINBD. From the Scope drop-down list. complete the following steps: Procedure 1. 2. JNDI name Enter jms/maximo/int/queues/cqin Bus name Select intjmsbus. 3. JNDI name Enter jms/maximo/int/queues/sqin Bus name Select intjmsbus. Click Save. and click OK. Click New. 6. 4. Name Enter SQIN. Note that this value must contain only uppercase letters. Verify that the Default Messaging Provider is selected and click OK. click Resources > JMS > Queues. To create the JMS queue (SQIN).2 Installation Guide . and click OK.Note that this value must contain only uppercase letters. From the WebSphere Application Server Administrative Console. Creating the sequential inbound (SQIN) JMS queue: You must create a JMS queue (SQIN) as the destination for sequential inbound point-to-point messages. 2. 7.

7. 6. Creating the service integration bus destination for the inbound error queue (CQINERRBD): You must add a logical address for the inbound error queue (CQINERRBD) within the JMS bus. Click OK. 3. JNDI name intjmsact Destination type Queue Destination JNDI name jms/maximo/int/queues/cqin Bus name intjmsbus Maximum concurrent endpoints 10 6. Installation tasks 89 . Complete the following steps to activate the CQIN queue: Procedure 1. Complete the following steps: Chapter 3. Queue name Select SQOUTBD. This value must be lowercase. Name intjmsact This value is case sensitive. From the WebSphere Application Server Administrative Console. Enter the following information. Restart MXServer under Servers > Application servers. click Resources > JMS > Activation Specifications. Click New to complete the General Properties section for the new JMS activation specification. Click OK. Creating JMS activation specification for the continuous inbound queue (CQIN): You must activate the continuous inbound queue (CQIN) before it can receive messages. 5. select Cell=ctgCell01.JNDI name Enter jms/maximo/int/queues/sqout Bus name Select intjmsbus. 2. From the Scope drop-down list. Click Save. 4. Click Save. 7. and then click OK. Error queues: You can create an optional error queue that will receive redirected messages from the continuous queue (CQIN) when the messages go in error.

2. 4. 7. From the WebSphere Application Server Administrative Console. select Cell=ctgCell01. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. Note that you must use this value and it must contain only uppercase letters. Click OK. Set the Maximum failed deliveries value to 5. and click Next to open the Create new queue dialog box. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer. 6. Click Specify and enter CQINERRBD as the exception destination value. click Service Integration > Buses to open the Buses dialog box. Verify that the Default Messaging Provider is selected and click OK. Review your selections. click Resources > JMS > Queues. 3. 12. Click Apply. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. 14. you create the Error queue. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. 90 IBM Tivoli Provisioning Manager Version 7. b. Select CQINBD. 9. 3. Creating the error (CQINERR) JMS queue: After creating the Error Queue Bus Destination. Click intjmsbus to open the Buses > intjmsbus dialog box. and click OK. From the WebSphere Application Server Administrative Console. Click Next to open the Confirm queue creation dialog box. From the Scope drop-down list. 4. Navigate the path Buses > intjmsbus > Destinations. Click Save. 15. From the WebSphere Application Server Administrative Console. Name Enter CQINERR. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the Description field. Click New. complete the following steps: Procedure 1. To create the Error queue. 2.2 Installation Guide . 5. Specify CQINERRBD as the exception destination. Leave Queue checked as the destination type. Click Save. 13. Change the Maximum failed deliveries value to 5. 11. Enter the following information. click Service Integration > Buses to open the Buses dialog box. Click New to open the Create new destination dialog box. 17.Procedure 1. 18. 10. 16. 8. Click intjmsbus to open the Buses > intjmsbus dialog box. then click Finish to complete the creation of the CQINERRBD bus destination queue. then click Next to open the Create a new queue for point-to-point messaging dialog box. then click CQINERRBD to open the configuration dialog box where you must make the following changes: a. Note that this value must contain only uppercase letters. 5.

From the Scope drop-down list. For example. For more information about WebSphere Application Server Network Deployment message storage. 3. including the usage of products other than DB2. Enter the following information. a user named mxsibusr with a password of mxsibusr. Destination type Enter Queue. select Cell=ctgCell01. You will select whether you want to persist messages or not during base services installation. JNDI name Enter intjmsacterr. Click OK. Creating JMS activation specification for the inbound error queue (CQINERR): You must activate the continuous inbound queue (CQINERR) before it can receive messages. see the WebSphere Application Server documentation and Planning the configuration of a messaging engine to use a data store. Create a system user and password on the server hosting the database server. complete the following steps: Procedure 1. You have the option of having WebSphere Application Server Network Deployment use a DB2 database to store JMS messages. Click Save. 7. you must create a data source in order to store JMS messages in a DB2 database. Click Save. Destination JNDI name jms/maximo/int/queues/cqinerr 6.JNDI name Enter jms/maximo/int/queues/cqinerr Bus name Select intjmsbus. 7. Name Enter intjmsacterr. From the WebSphere Application Server Administrative Console. and click OK. Click OK. 4. Complete the following steps to activate the CQINERR queue: Procedure 1. 6. Installation tasks 91 . To create a data source for the persistent store. Queue name Select CQINERRBD. Manually creating a data source for the persistent store: If you chose to manually configure WebSphere Application Server Network Deployment and if you intend to persist messages. Click New to complete the General Properties section for the new JMS activation specification. Create and configure the database: Chapter 3. 2. 2. This value must only contain lowercase letters. Click OK. 5. click Resources > JMS > Activation Specifications.

Complete the following fields in the User identity form: Alias maxJaasAlias User ID mxsibusr Password Password that you created for mxsibusr. d. 3.2 Installation Guide . go to Resources > JDBC > JDBC Providers. Click Apply. and infrastructure. h. Click New. 92 IBM Tivoli Provisioning Manager Version 7. and then click Save. Open and log on to the WebSphere Application Server Network Deployment Administrative Console. j. Grant all authorities to the mxsibusr user with the exception of Security administrator authority. h. f. e. c. e. Create a database named maxsibdb using default settings. Click Apply. a. Description SIB database user alias. Verify that you can connect to the database using the mxsibusr user by right-clicking maxsibdb and selecting Connect. Complete the WebSphere Application Server variable ${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of <WAS_HOME>ctgMX\lib. b. g. Navigate to Security > Secure administration. c. Select mxsibusr from the User drop-down list. b. m. Click Next. f. a. C:\Program Files\IBM\WebSphere\ AppServer\ctgMX\lib. click on Java Authentication and Authorization Service > J2C authentication data. From the WebSphere Application Server Administrative Console navigation pane. l. Once the database has been created. For example. applications. Right-click DB Users and select Add. expand the maxsibdb database and select User and Group objects. Specify the following values: Database type DB2 Provider type DB2 Universal JDBC Driver Provider Implementation type XA data source Name maxJdbcProvider k. Right-click the Databases folder and select Create Database > Standard. Click New. Click Scope and then select Cell=ctgCell01. Under the Authentication header. Configure J2C authentication data and JDBC provider in WebSphere Application Server Network Deployment. Click Next. d. i. g. i. Navigate down to the Databases folder listed under your system.Open DB2 Control Center. j.

Click Scope and then select Cell=ctgCell01. f. Ensure that each jar file has the full path from ${DB2UNIVERSAL_JDBC_DRIVER_PATH} 5. Port number Specify the DB2 port number. Ensure the Use this data source in container managed persistence (CMP) option is enabled. and then exited the middleware installer before actually deploying the deployment plan. j. Specify the following values: Database name maxsibdb Driver type 4 Server name Specify the DB2 server host name. From the Component-managed authentication alias and XA recovery authentication alias drop-down list. b. select maxJaasAlias. Click Save. and correct the Class path if required for both db2jcc. Installation tasks 93 . and then click Next.jar to the <WAS_HOME>\ctgMX\lib directory. and then clicking Test Connection. d. o. Click New. Click Finish. i. Open a command prompt and copy <DB2_HOME>/java/db2jcc. Changing middleware installer configuration parameters You can change the configuration parameters you have entered for a deployment plan before deploying the plan. Specify the following values: Data source name intjmsds JNDI name jdbc/intjmsds e. entered configuration parameters for the plan. Verify the data source by selecting intjmsds. Click Save. 50005. Configure WebSphere Application Server: a. From the WebSphere Application Server Network Deployment Console. Click Next. You can use this option if you chose to cancel the deployment of the deployment plan that you developed by exiting the middleware installer. Click Next. Before you begin This information assumes that you have developed a deployment plan. For example. 6. Go back to Resources > JDBC > JDBC Providers > maxJdbcProvider. 4. k.n.jar and db2jcc_license_cu. c. h. Choose Select an existing JDBC provider.jar and <DB2_HOME>/java/ db2jcc_license_cu. l. Configuration parameters for a plan can be changed only before deploying the deployment plan. navigate to Resources > JDBC > Data sources. Click Finish. g.jar. and then select maxJdbcProvider from the drop-down list. Chapter 3.

7. 6. 8. 5. click Finish. enter the location for compressed images for the middleware contained in the deployment plan. Select Edit the configuration parameters. you can continue with the installation. Advance along the middleware installation program panels and make adjustments. 2000 DB2 Start DB2. The following table summarizes the possible options: Table 19. If the server does not have a virtual IP address a.To change middleware installer configuration parameters: Procedure 1. continue with the next step: v Start middleware that is stopped in the following order: See “Checking middleware status” on page 97 for steps to verify that middleware is started. and a directory to use to hold the extracted images. From the Deployment Plan and Parameter Configuration summary panel. Start the middleware installer from the launchpad and advance to the Choose Workspace panel. If you have not rebooted the server or stopped middleware. Starting middleware on Windows Middleware servers and services must be active before installing the base services installer. Once the deployment completes successfully. The Tivoli Directory Server database instance and administration server must be started manually. and then click Next. 2. In the following examples. the Tivoli Provisioning Manager core components. 3. the database instance is named ctginst1.2 Installation Guide . Steps to start middleware Situation Middleware is installed. and then click Next. From the Select Middleware Image Directories panel. review the contents of the summary. When all middleware is started. Specify the directory that you previously used as the middleware installation program workspace. Procedure 1. v If you have completed the Tivoli Provisioning Manager installation. and then click Next. but you have not completed the Tivoli Provisioning Manager installation. You have stopped middleware. The middleware that you need to start depends on your current task. Click Start and select Run. Log on as a user with administrative permissions. You rebooted the computer. continue with the next step: v If you are in the process of installing Tivoli Provisioning Manager. you can now continue with installation. Action The middleware is started for you when the middleware installation is complete. see “Starting and stopping the provisioning server on Windows” on page 211. and the Tivoli Provisioning Manager Web components. and then click Next. When you reach the Deployment Plan Operation panel. Once you have entered the two locations. 2. select Deploy the plan. v If you have completed the Tivoli Provisioning Manager installation. see “Starting and stopping the provisioning server on Windows” on page 211. 4. 94 IBM Tivoli Provisioning Manager Version 7. When all middleware is started. click Next.

idsccmdb. c.DB2COPY1 . If the server has a virtual IP address db2gcf -u -p 0 -i idsccmdb b.idsccmdb. Select IBM Tivoli Directory Admin Server V6. Alternatively.msc and click OK. Alternatively. If you need to restart a middleware application. 3) Select IBM Tivoli Directory Server Instance V6. see Starting the directory server instance at operating system startup in the Tivoli Directory Server information center. you must stop the application before restarting. 2) Type services. Click Start and select Run. c.bat Start Node WAS_HOME\profiles\ctgAppSrv01\bin\startNode.msc and click OK. Type services. b. a. the database instance for Tivoli Directory Server is named idsccmdb. 3) Select DB2 . If the server has a virtual IP address db2gcf -u -p 0 -i ctginst1 3.bat Stopping middleware Follow these procedures to stop middleware. Start the Tivoli Directory Server administration server: a. Select DB2 . run apache from the command line. run the following command from the command line: idsdiradm -I idsccmdb 4. Start the Tivoli Directory Server instance: 1) Click Start and select Run. Chapter 3. Start IBM HTTP Server and WebSphere Application Server webserver1 profile: a. and click Start the service. and click Start the service.msc and click OK.IDSCCMDB and click Start the service.1 and click Start the service. 5.msc and click OK. Select IBM HTTP Server 6. Alternatively. 2) Type services. 6. Type services. c. Start other WebSphere Application Server profiles: Start the deployment manager WAS_HOME\profiles\ctgDmgr01\bin\startManager. Start the Tivoli Directory Server database instance: If the server does not have a virtual IP address 1) Click Start and select Run.b. Installation tasks 95 . Type services.2 .DB2COPY1 . In the following examples. Click Start and select Run.msc and click OK. b.2 . Start Tivoli Directory Server.CTGINST1-0 and click Start the service. If you want to configure Tivoli Directory Server to start automatically with the operating system. run the following command: idsslapd -I idsccmdb Important: The directory server instance must remain as a manual startup type to synchronize correctly with the database in the context of Tivoli Provisioning Manager.

The commands in these steps use the default instance name idsccmdb. open a DB2 window with the command db2cmd. a. 3.bat MXServer -username wasadmin_username -password wasadmin_password The following parameters are used in the commands: wasadmin_username The WebSphere Application Server administrator user name.Procedure 1. use the following command to stop the database: db2gcf -d -p 0 -i idsccmdb b. a. Stop the WebSphere Application Server MXServer profile. 4. Change to the WAS_HOME\profiles\ctgAppSrv01\bin directory. set the instance name: 96 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide . c. c. if there are any instance attachments. Stop Tivoli Provisioning Manager. ibmdirctl –D cn=root –w password -h host_name stop password The password for the base DN (cn=root). Stop Tivoli Directory Server. wasadmin_password The password for the specified user name. Log on as a user with administrator access. Run the following command: stopServer. Stop the database instance. a. At a command prompt. b. Stop the DB2 database instance. The commands in these steps use the default instance name ctginst1. If you have Tivoli Directory Server on the same computer as the Tivoli Provisioning Manager database. Server has a virtual IP If you are using a virtual IP address for the DB2 server. however. 2) At a command prompt. 1) Log on as a user with administrator access. host_name The host name of the Tivoli Directory Server computer. open a DB2 window with the command db2cmd. b. No database connections are allowed when running this command. 2. Change to the TDS_HOME/bin directory. set the instance name: set db2instance=idsccmdb 4) Run the following command to check for other running applications: db2 list applications 5) If the command lists other applications. run the following command to disconnect them: db2 force applications all 6) Stop DB2: Server does not have a virtual IP Run the following command: db2stop Note: The db2stop command can only be run at the server. they are forced off before the instance is stopped. Stop Tivoli Directory Server. 3) If you have Tivoli Directory Server on the same computer as the Tivoli Provisioning Manager database.

If there are multiple DB2 instances listed. 2. Stop DB2: Server does not have a virtual IP Run the following command: db2stop Note: The db2stop command can only be run at the server. wasadmin_password The password for the specified user. they are forced off before the instance is stopped. however. 2. No database connections are allowed when running this command. In the list of server roles. Open the Services control panel. db2gcf -d -p 0 -i ctginst1 Checking middleware status Follow these procedures to check the status of middleware. Log on as Administrator. Find the entry for the IBM Tivoli Directory Server and check the status of the service. v To check the status of Tivoli Directory Server: 1. Installation tasks 97 . use the following command to stop the database. v To check the status of WebSphere Application Server: Tivoli Provisioning Manager profile 1. If the command lists other applications. 3. Chapter 3. Log on as Administrator. Find the DB2 instance and check the status of the service. Run the command: serverStatus MXServer -username wasadmin_username -password wasadmin_password The following parameters are used in the commands: wasadmin_username The WebSphere Application Server administrator user name. if there are any instance attachments. find the one for the Tivoli Provisioning Manager database owner. Server has a virtual IP If you are using a virtual IP address for the DB2 server. In this example. Open the Services control panel. Procedure v To check the status: 1. Run the following command to check for other running applications: db2 list applications e. v To check the status of Microsoft Active Directory: Click Start > Programs > Administrative Tools > Manage Your Server.set db2instance=ctginst1 d. 2. verify that the server is configured with the Domain Controller (Active Directory) role. the database instance is ctginst1. 2000 DB2 3. Change to the WAS_HOME\profiles\ctgAppSrv01\bin directory. run the following command to disconnect them: db2 force applications all f.

On the Summary panel. you can install the base services. the installation might fail when attempting to install language packages. see Resolving host names with a DNS server in “Preinstallation Step 6: Verify the environment” on page 16. Before you begin v Make sure that the middleware applications are started. you can set the following DB2 property and then restart the DB2 server: v db2 update dbm cfg using KEEPFENCED NO v Because of DB2 installation requirements. If you have rebooted the computer or if you installed the middleware manually. if your configuration requires the use of an administrative workstation. You must install the base services on either the provisioning server or the administrative workstation. either run the base services installer in English and configure the database manually outside of the base services installer. such as anti-virus software. You enter this user ID on the DB2 Administration screen and on the Remote Access Authorization screen of the Provisioning Manager installation program. For information about verifying host names. See the DB2 product documentation for information about creating a user with SYSADM (administration) authority on the DB2 server. in preparation for the product installation. To avoid this problem. v Complete the following tasks to prepare the DB2 database: – The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. v If you are installing Tivoli Provisioning Manager in a language other than English. If you installed the middleware with the middleware installer. You might get error messages CTGIN2289E and CTGIN0158E. see: – “Starting middleware on Windows” on page 94 v Review the planning worksheet for information about the base services installation settings. If you need to customize the table space sizes. temporarily shut down any non-critical processes that could have a negative effect on the installation.2 Installation Guide . the middleware applications are started automatically after installation. If the remote system is a Windows server. v Enable a remote execution and access service on every system with middleware installed. v If the operating system user ID that you use for the installation contains Russian language characters. remove the temporary environment variables before the DB2 installation and then redefine them. 98 IBM Tivoli Provisioning Manager Version 7. Remote access protocols include SSH and Windows SMB. use fully qualified host names. you must accept the default values for database table space size and index table space size. v When entering values for host names. v Enable RXA tracing to allow better troubleshooting in case there are connection problems between the administrative workstation and the provisioning server. you must configure remote execution and access to use SMB. install the product using a user ID with administrative authority that contains only English language characters. 2000 DB2 2000 DB2 To avoid high system memory usage by DB2. To resolve the problem. This value is case-sensitive. – The user ID for the DB2 instance administrator must have SYSADM (administration) authority. or modify the table space sizes after installation. Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server. For more information. these values are displayed as null. you might have removed the TEMP and TMP environment variables in order to get DB2 to install successfully (DB2 might fail to install when the path string used for the TMP and TEMP environment variables is too long). See “Planning worksheet for base services installation” on page 110.Installing the base services After you have installed the middleware. However. these environment variables must be defined before launching the product launchpad or product installation program if you are installing the product on the same Windows system that is hosting DB2. see “Enabling RXA tracing” on page 167. v If using an administrative workstation.

v For WebSphere Application Server Network Deployment, ensure that the Cell and all related nodes are actively running. v The database instance owner home directory must have 8 GB of space available regardless of whether a database will be installed into that location. v Do not use localhost for host name values in the installation program. Specify the fully qualified host name of the system for all host name values. This value is case-sensitive. The following instructions are for a multiserver installation using default values and assume that you want the base services installer to automatically configure middleware across multiple computers. If you get errors, resolve them before continuing with the installation. If you cancel the installation program after entering values across several installation panels, the installation program recalls the values the next time you start the base services installation program again. You can restore the default values in the base services installation program by deleting the file MAXIMO_HOME/applications/maximo/properties/maximo.properties. If you cannot locate the maximo.properties file in the MAXIMO_HOME directory, look for it in the system temporary directory. To install the base services:

Procedure
1. Check for an existing installation of the solution installer. The default installation location is: v C:\Program Files\IBM\Common\acsi If the solution installer is already installed, start the service: v Check the Services control panel. If the IBM ADE service is not running, start it. 2. Start the launchpad. 3. In the launchpad navigation pane, click Custom Installation, then click Verify base services installation prerequisites. After verifying and confirming the prerequisites, return to the custom installation page. 4. Click Install base services and required components. 5. Select a language for the installation and click OK. 6. In the Introduction panel, click Next. 7. In the Package Summary panel, review the package deployment actions, and then click Next. 8. Accept the license agreement and click Next. 9. In the Choose Install Folder panel, specify the base services installation directory, and then click Next. The path that you specify must not contain spaces. The default values are: v C:\IBM\SMP 10. In the Choose Deployment panel, select the Custom option. Note: The Simple option is not supported. 11. In the Import Middleware Configuration Information panel, specify that you want to use the field values that you enter into the middleware installer fields as default values for those same fields in the base services installer. Import middleware configuration information Select this check box if you want to allow the base services installer to reuse the values entered in the middleware installer. If you installed the middleware manually, leave this check box clear and enter the required values in the subsequent panels from the base services installer.

Chapter 3. Installation tasks

99

Note: If you select this feature while installing using RXA, the workspace location that you specify must reside locally on the remote system, and cannot be located on a network drive of the remote system. Host name Enter the fully qualified domain name of the system where the middleware installer was run. This value is case-sensitive. User ID Enter the user ID that was used to run the middleware installer on the computer specified in the Host name field. Password Enter the password for the user. Workspace location Enter the location of the topology file that contains the values entered for the middleware installer. This file is found in the workspace that was defined during the middleware installation. For more information, see “The middleware installer workspace” on page 34. 12. In the Database Type panel, select the product that you are using for the maximo database and click Next. Important for database support: SQL Server is not a supported database. Oracle is not supported when the provisioning server is installed on Windows. 13. In the Database panel, enter configuration information about the database, and then click Next.
2000 DB2

Host name Enter the fully qualified domain name of the computer hosting DB2, for example, database.example.com. This value is case-sensitive. Port Enter the port being used by the DB2 instance. The default value is 50005.

Database Name Enter the name of the database to use with Tivoli Provisioning Manager. The default database name is maxdb71. The database is created if it does not exist. Instance Enter the name of the database instance to be used with Tivoli Provisioning Manager. The default instance name is ctginst1. This instance is created if it does not exist. However, the user and its associated home directory must exist on the DB2 server. Database User ID Enter the user ID used for Tivoli Provisioning Manager to access DB2. This user ID cannot be the same as the instance administrator user ID. The default value is maximo. Database Password Enter the password for the user ID used to access DB2. 14. In the Automate Database Configuration panel, select Automate database creation and configuration, and then click Next. This option allows the base services installer to automatically configure the database for use by Tivoli Provisioning Manager. Examples of automated tasks include creating table spaces, creating database tables, creating database schemas, and creating users. Note: If you do not want the base services installer to configure the database automatically, you must configure it manually before the installation of the base services. 15. In the Remote Access Authorization panel, enter authorization information for the automatic database configuration feature, and then click Next.

100

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

User ID Enter a user ID for the base services installer to access the system that is hosting the database to be used with Tivoli Provisioning Manager. Enter administrator. Password Enter the password for the user ID. See “Remote configuration enablement” on page 111 for details about how to ensure successful remote access between the Provisioning Manager installation program and the remote server. 16. In the Database Administration panel, enter configuration information about the database, and then click Next.
2000 DB2

Installation directory Enter the directory where DB2 is installed. The default values are: v C:\Program Files\IBM\SQLLIB Instance administrator user ID Enter the user ID for the administrator of the DB2 instance. The default values are: v db2admin This user ID cannot be the same as the database user ID. This user must have DB2 administration authority, which is referred to as SYSADM authority in the DB2 product documentation. For more information about creating this user, see the DB2 product documentation. Instance administrator password Enter the password for the DB2 instance administrator user ID. Windows service user ID Enter the user ID used to start the DB2 service on Windows. This user ID must have administrative authority on the system. The default value is db2admin. Windows service password Enter the password for the user ID used to start the DB2 service on Windows. 17. In the Database Tablespace panel, enter information about the table space of the database, and then click Next.
2000 DB2

Data tablespace name Enter the name of the table space to be created in DB2 for Tivoli Provisioning Manager. The table space is created if it does not exist. The default value is MAXDATA. Data tablespace size Enter a size, in megabytes, for the data table space. The value must be 5000 Mb or greater. Temporary tablespace name Enter the name for the temporary table space to be created for DB2. Temporary table spaces hold data during sorting or collating actions. The table space is created if it does not exist. The default value is MAXTEMP. Temporary tablespace size (Mb) Enter a size for the temporary table space. The default value is 1000 Mb. Index tablespace name Enter a name for the index table space. The default value is MAXDATA. Index tablespace size Enter a size, in megabytes, for the index table space. The value must be greater than 3000 Mb. The default is 5000 Mb.
Chapter 3. Installation tasks

101

18. In the Application Server Type panel, select WebSphere Application Server. Important for application server support: Oracle WebLogic Server is not supported. 19. In the WebSphere Connectivity panel, enter host information about the WebSphere Application Server, and then click Next. Host name Enter the fully qualified domain name of the system hosting WebSphere Application Server. This value is case-sensitive. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere Application Server system. The default value is 8879. 20. In the Automate WebSphere configuration panel, select Automate WebSphere configuration and click Next. This option allows the installation program to automatically configure WebSphere Application Server for use by Tivoli Provisioning Manager. Note: If you do not select the option to configure WebSphere Application Server automatically, you must have configured the middleware manually before installing the base services. For more information about the manual configuration tasks. If your provisioning server is installed on Windows, AIX, or Linux (except for SUSE Linux Enterprise Server 11), see “Manually configuring WebSphere Application Server” on page 70. 21. In the WebSphere Remote Access Authorization panel, enter authorization information for WebSphere Application Server configuration, and then click Next. Operating system user ID v Enter a valid user ID for the base services installer to access the system that is hosting WebSphere Application Server. This user ID must have administrative rights on the machine you are accessing. Operating system password Enter the password for the system user ID. 22. In the WebSphere Application Server Network Deployment Configuration panel, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere Application Server is installed on the host system. For example: v C:\Program Files\IBM\WebSphere\AppServer User ID Enter the administrative user ID used to access WebSphere Application Server. The default value is wasadmin. Password Enter the password for the administrative user ID used to access WebSphere Application Server. Profile name Enter the name for the WebSphere Application Server profile. The default value is ctgDmgr01. 23. In the WebSphere Application Server Configuration panel, enter the following information, and then click Next. Web server port Enter the Web server port used by WebSphere Application Server. The default value is 80. Web server name Enter the name of the Web server. The default value is webserver1.

102

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

Node name Enter the name of the WebSphere Application Server node containing the application server. The default value is ctgNode01. Application server Enter the name of the WebSphere Application Server to associate with Tivoli Provisioning Manager. If the application server does not exist, it is created. The default value is MXServer. 24. In the Security panel, select a method for authenticating and authorizing users and groups and click Next. Use WebSphere application security for authentication and authorization Choose this option to automatically configure WebSphere Application Server Network Deployment application security to manage users and groups for authentication and authorization purposes. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. Important: You must select this option if you want to use LDAP and Microsoft Active Directory for authentication and authorization. Use WebSphere application security only for authentication Choose this option to automatically configure WebSphere Application Server Network Deployment application security for authentication only and allow Maximo security to manage groups and user to group memberships. With this option, you create all your users in your directory server, but you manage their membership in security groups in the Security Groups application in Tivoli Provisioning Manager. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. If you select this option, the next panel prompts you for your user base entry. The maxadmin, maxreg, and mxintadm users must be created before you proceed past this panel. Use Maximo security for authentication and authorization If you do not want to use WebSphere Application Server Network Deployment application security, select this option to have Maximo security manage users and groups for both authentication and authorization. 25. In the Enter Maximo users panel, enter the following information, and then click Next. Note: Ensure that you enter the correct passwords, as the installation program does not validate them. Maximo administration user Product administrator user ID used for initial configuration and adding users. The default value is maxadmin. Password Password for the Maximo administration user. Maximo system registration user User ID used for the self registration of users. The default value is maxreg. Password Password for the Maximo system registration user. Maximo system integration user User ID used with enterprise adapters. The default value is mxintadm. Password Password for the Maximo system integration user. 26. If you selected Use WebSphere application security only for authentication in the Security panel, specify the distinguished names of the user and group base entities that you are using, choose how users are created, and then click Next.
Chapter 3. Installation tasks

103

Important: When entering LDAP values for the base services installation, entries in LDIF files, or values that you enter directly into a directory instance using the directory server tools, follow the product-specific syntax rules for using special characters in an LDAP string. In most cases, special characters must be preceded by an escape character in order to make it readable by the directory server. Many directory server products consider a blank space as a special character that is part of the LDAP string. Therefore, if you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you might get errors. See the product documentation for your directory server for more information about special characters in LDAP strings. User base entry Enter the user base entry that is configured for your directory server. The default LDAP schema user base entry is ou=users,ou=SWG,o=IBM,c=US. Ensure that the base entry is in the proper format and is accurate. The middleware installer does not validate the base entry, but the base services installer validates it. If you entered an incorrect base entry, you must correct it before continuing with the base services installation. Group base entry Enter the group base entry that is configured for your directory server. The default LDAP schema group base entry is ou=groups,ou=SWG,o=IBM,c=US. Ensure that the group base entry is in the proper format and is accurate. The middleware installer does not validate the group base entry, but the base services installer validates it. If you entered an incorrect group base entry, you must correct it before continuing with the base services installation. Create the required users Tivoli Directory Server Keep this option selected to allow the installation program to create default users in WebSphere Application Server Virtual Member Manager (VMM). This operation requires write access to VMM. If you do not want to have the users created by the installation program, you must create them manually before continuing with the installation. See “Manually configuring directory synchronization for WebSphere Application Server Network Deployment” on page 134 for synchronization tasks that you must complete after the installation if you choose to customize your schema. Microsoft Active Directory Clear this option. If you are using Microsoft Active Directory to secure WebSphere Application Server, you already created the schema using the steps provided in “Securing WebSphere Application Server with Microsoft Active Directory using the middleware installation program” on page 68 and “Manually configuring Microsoft Active Directory” on page 60. Before continuing with installation, verify the following requirements in Microsoft Active Directory a. The following users exist in the directory server:
Group maxadmin Users mxintadm maxadmin

104

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

If you are not using the default LDAP schema.ou=SWG.ou=SWG.ou=SWG. Installation tasks 105 . See “Manually configuring directory synchronization for WebSphere Application Server Network Deployment” on page 134 for synchronization tasks you must complete after the installation if you choose to customize your schema. o=ibm.Group maximousers Users mxintadm maxadmin maxreg b.ou=users.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg. The values entered for User and Group base entry fields are used to configure the VMMSYNC cron task. o=ibm. The pre-Windows 2000 name for the group maxadmin is changed to a different name. o=ibm.ou=users.c=us Chapter 3. Below is an example of the default LDIF data that you need to modify and import into your LDAP repository if you want to customize the schema and create your own users manually: dn: o=ibm. This change is required because the maxadmin group contains a user that is also called maxadmin.ou=users. o=ibm.c=us ou: SWG objectClass: top objectClass: organizationalUnit dn: ou=users.c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm. you must have it created before advancing past this panel.ou=SWG.c=us objectClass: top objectClass: organization o: IBM dn: ou=SWG. o=ibm. o=ibm.c=us ou: users objectClass: top objectClass: organizationalUnit dn: cn=wasadmin.ou=users.c=us uid: wasadmin userpassword: wasadmin objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: person objectclass: top title: WebSphere Administrator sn: wasadmin cn: wasadmin dn: uid=maxadmin.ou=SWG.

ou=groups.ou=users.ou=SWG.o=ibm.O=IBM.O=IBM.o=IBM.O=IBM.ou=users.ou=groups.O=IBM.o=IBM.C=US objectclass: groupofnames cn: TPDEPLOYMENTSPECIALIST member: uid=maxadmin.2 Installation Guide . run the following command: ldapmodify -a -D cn=root -w <password> -i <file_name> 106 IBM Tivoli Provisioning Manager Version 7.ou=SWG.c=US dn:cn=TPCONFIGURATIONLIBRARIAN.o=IBM.ou=SWG.C=US objectclass: groupofnames cn: TPCOMPLIANCEANALYST member: uid=maxadmin.c=US To create the users and update the membership of the LDAP repository.C=US objectclass: groupofnames cn: TPWEBSERVICEUSER member: uid=maxadmin.ou=groups.c=US cn: maxadmin dn: cn=maximousers.C=US objectclass: groupofnames cn: TPCONFIGURATIONLIBRARIAN member: uid=maxadmin.o=IBM.o=IBM.ou=users.c=US dn:cn=TPDEVELOPER.c=US dn:cn=TPWEBSERVICEUSER.ou=groups.ou=users.O=IBM.ou=SWG.o=IBM.ou=SWG.c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=maxadmin.c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=mxintadm.o=IBM.c=us ou: groups objectClass: top objectClass: organizationalUnit dn: cn=maxadmin. o=ibm.ou=groups.ou=users.ou=users. you are required to create the following groups and assign the maxadmin user to them.c=US cn: maximousers dn:cn=TPDEPLOYMENTSPECIALIST. An LDIF file with the following content needs to be created: dn: ou=groups.ou=SWG.ou=SWG.userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg After the creation of users.ou=SWG.o=IBM.ou=SWG.ou=SWG.ou=groups.C=US objectclass: groupofnames cn: TPDEVELOPER member: uid=maxadmin.c=US member: uid=mxintadm.o=IBM.o=IBM.C=US objectclass: groupofnames cn: TPADMIN member: uid=maxadmin.ou=users.ou=SWG.ou=groups. o=ibm.ou=SWG.ou=SWG.ou=SWG.ou=SWG.ou=users.c=US dn:cn=TPCOMPLIANCEANALYST.ou=SWG.ou=users.c=US member: uid=maxreg.c=US member: uid=maxadmin.ou=SWG.ou=users.O=IBM.ou=SWG.o=IBM.ou=groups.ou=users.c=US dn:cn=TPADMIN.ou=SWG.ou=SWG.

Persist JMS messages Select this option if you want the installation program to persist messages within DB2. enter the following information. Installation directory Enter the installation directory for the DB2 server that is hosting the JMS database that contains the instance to be used with WebSphere Application Server. Database name Enter the name of the database serving as the JMS data store. This user is created if it does not exist. Password Enter the password for the user ID. User ID Enter the user ID used to access the database server. enter the following information. The JMS data store can only be created as a DB2 database. The default value is ctginst1. User ID Enter the user ID for the base services installer to access the system that hosts the JMS database. the installation program cannot configure message persistence. Port Enter the port used to access the database server. If you are using another database type. and then click Next. The default is the database user ID you entered when you selected your database type. JMS Data Source name Enter the name of the database to be used by JMS. This value is case-sensitive. enter authorization information for the automatic configuration feature. in the DB2 Database Server Configuration panel. Installation tasks 107 . 30. The default value is intjmsds.27. For more information. A JMS server requires a DB2 data repository to be configured to maintain messages. enter the following information. you must configure the JMS implementation manually. This user must have administrative rights on the computer that you are accessing. For example: v C:\Program Files\IBM\SQLLIB Instance Enter the JMS database instance to be used with WebSphere Application Server. 2000 DB2 In the DB2 Database Instance Configuration panel. see “Manually creating a data source for the persistent store” on page 91. Password Enter the password for the user ID to access the database server. If you chose to persist JMS messages. and then click Next. Instance administrator user ID Enter the user ID for the administrator of the JMS database instance. and then click Next. 2000 DB2 Host name Enter the fully qualified domain name of the server hosting the JMS data store. Do not persist JMS messages Select this option if you do not want the installation program to set the JMS implementation to persist messages automatically. In the Integration Adapter JMS Configuration panel. The default value is maxsibdb. in the DB2 Database Server Remote Access Authorization panel. The default value is 50005. 2000 DB2 If you chose to persist JMS messages. 28. 29. For example: v db2admin Chapter 3. This user must be a member of the DB2ADMNS group. and then click Next. If you later decide that you want to persist JMS messages.

Instance administrator password Enter the password for the JMS database instance administrator user ID. 31. In the SMTP Configuration panel, specify SMTP configuration information used by workflows to communicate with workflow participants. SMTP server Enter the fully qualified host name of the SMTP server that is sending messages to participants. This value is case-sensitive. Administrator e-mail Enter a valid e-mail address. This address is used to send messages. You can defer SMTP configuration by not providing information on this panel and advancing to the next panel. However, you must configure these parameters on interface after installation. For more information, see “Configuring SMTP” on page 115. 32. In the Run Configuration Step panel, select an option to perform the configuration and to deploy the application files, and then click Next. Perform installation configuration now Select this option to perform the configuration step during installation. Copy files now, and perform installation configuration later, manually Select this option to have the installation program copy files to the system only. The Tivoli Provisioning Manager installation program is used to complete tasks such as gathering information about your Tivoli Provisioning Manager deployment and configuration, copying files to your local system, and performing configuration tasks using the values that you have specified. If you select this option, the installation program will gather your configuration information and copy the Tivoli Provisioning Manager files to your local system now, and then allow you to run the configuration step at a later date. Deploy application files automatically Select this option to have the installation program perform EAR file deployment automatically during the installation. Deploy application files manually later Select this option to defer the deployment of application files. Deferring the deployment of application files can shorten the time it takes to deploy overall if you intend to install more than one service management product. Files can be deployed once all products have added their own functions to the application files. You might also want to use this option if your organization has application deployment restrictions that require that you deploy application files either manually or using another approved process. For manual application deployment instructions for WebSphere Application Server, see “Deploying Provisioning Manager EAR files” on page 112. 33. In the Choose Shortcut Folder panel, select the type of shortcut for Tivoli Provisioning Manager, and then click Next. If selecting In the Start Menu to be used with Internet Explorer, ensure that you have added the Tivoli Provisioning Manager URL to the trusted sites Web content zone and disable the option of requiring server verification for all sites in the zone. Note: Do not use the In the Quick Launch Bar options, because it will not create a shortcut in the Quick Launch bar. 34. In the Input Summary panel, review the information, and then click Next. 35. In the Pre-Installation Summary panel, review the information, and then click Install. 36. In the Install Complete panel, click Done.

108

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

Results
The base services installation is completed. Logs can be found in the following locations: v v v v MAXIMO_HOME/logs MAXIMO_HOME/solutions/logs MAXIMO_HOME/maximo/tools/maximo/log C:\program files\ibm\common\acsi\logs

In addition, logs can be found in the log directories for the WebSphere Application Server application server, deployment manager, and node agent. The configuration values that you entered are stored in the MAXIMO_HOME/applications/maximo/ properties/maximo.properties file. If you did not use the base services installer to perform the configuration, you can perform them outside of the base services installer by using the taskrunner utility, located in the MAXIMO_HOME/scripts directory. This utility uses the configuration values stored in the maximo.properties file to configure base services.
taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

Note: v If you reboot the system, you cannot use the taskrunner utility to run configuration scripts, because taskrunner data stores are not persisted. If you intend to use the taskrunner utility, do not reboot your system. v Passwords are encrypted in the maximo.properties file during the installation process. The encrypted data is stored in a section of the file after the line mxe.encrypted=true using various characters, including symbols other characters that are not alphanumeric. Ensure that you do not modify the encrypted section of the file. A version of the file with the unencrypted password is stored in maximo.properties_orig in the same directory. Important: Back up the unencrypted file maximo.properties_orig outside the system file structure. If you change the database user password, you must update this file with the new password and then create an encrypted maximo.properties file. If the installation fails, you can run taskrunner again after resolving the errors if it was run with the STOPONERROR parameter. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors.

What to do next
1. If you want to install support for other languages, proceed to “Installing the language pack” on page 116. 2. Back up the base services home directory. In the launchpad navigation pane, click Custom Installation, then scroll down to 2. Install the base services and required components and click 2.4 Back up base services home directory. Follow the instructions on the panel to back up, then return to the custom installation page. 3. Back up the deployment engine database. In the launchpad navigation pane, click Custom Installation, then scroll down to 2. Install the base services and required components and click 2.5 Back up the deployment engine database. Follow the instructions on the panel to back up, then return to the custom installation page. 4. If you chose not to configure WebSphere Application Server automatically during base services installation, you must manually create the following required groups and add the maxadmin user to the groups: TPADMIN, TPCOMPLIANCEANALYST, TPDEPLOYMENTSPECIALIST, TPDEVELOPER,
Chapter 3. Installation tasks

109

and TPWEBSERVICEUSER. For more information and depending on the directory server that you are using, see “Manually configuring Microsoft Active Directory” on page 60 or “Manually configuring IBM Tivoli Directory Server” on page 54. 5. Proceed to “Installing Tivoli Provisioning Manager core components” on page 119.

Planning worksheet for base services installation
This table lists the settings that you must provide during the base services and core components installation.
Table 20. Tivoli Provisioning Manager settings Setting Tivoli Provisioning Manager installation directory Database port number Default value v C:\Program Files\IBM\tivoli\tpm Your value

v v

2000 DB2 Oracle 2000

50005 1521

Tivoli Provisioning Manager database host name Maximo database name Maximo database instance Schema name Maximo database user ID
2000 DB2

maxdb71 ctginst1 maximo maximo v SystemDrive:\Program Files\IBM\SQLLIB

DB2 installation directory

2000 DB2

DB2 instance administrator v db2admin Windows DB2 service user db2admin MAXDATA v
2000 DB2

user ID
2000 DB2

ID Data table space name Data table space size Temporary table space name Temporary table space size Index table space name Index table space size WebSphere host name WebSphere SOAP port WebSphere server home directory WebSphere admin user ID WebSphere profile name Web server port Web server name Node name Cluster name 8879 v C:\Program Files\IBM\WebSphere\ AppServer wasadmin ctgDmgr01 9081 webserver1 ctgNode01 MAXIMOCLUSTER

5000 MB

MAXTEMP 1000 MB MAXDATA v
2000 DB2

5000 MB

110

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

Table 20. Tivoli Provisioning Manager settings (continued) Setting Application server JMS data source Name JMS database name JMS server name Database user ID Group base entry User base entry SMTP server Administrator email maxadmin ou=groups,ou=SWG,o=IM, c=US ou=users,ou=SWG,o=IM, c=US maxsibdb Default value MXServer. This value cannot be changed. Your value

Starting the launchpad
The launchpad lets you install all components that are required for Tivoli Provisioning Manager.

Procedure
1. Log on to an account with system administration privileges. 2. If you are using DVDs, insert the Installation DVD for Windows. The disk must be inserted for the duration of the installation. 3. Run launchpad64.exe (Windows 64-bit) or launchpad.exe (Windows 32-bit) from the root directory. 4. In the launchpad, select a language and click OK.

Results
The launchpad panel is displayed. When the launchpad is running, the generated launchpad messages are captured in a hidden log frame. To display the log frame on the bottom of the launchpad panels during run time, hold Ctrl and click in the banner frame of the launchpad. Messages that are generated while the launchpad is running are not automatically saved on the hard disk. You can save the messages from a runtime session by clicking Save at the bottom of the log frame and specifying where you want to save the file.

Remote configuration enablement
If you plan to take advantage of the Provisioning Manager installation program feature that automates the configuration of Provisioning Manager middleware, you must enable a remote access protocol for each system on which you intend to install Provisioning Manager middleware. Remote access protocols include rsh, rexec, SSH and Windows SMB. Before you start the installation program you must ensure that you can log on to your remote server or servers using the protocols you intend to use with the credentials you plan to supply to the installation program. For remote Windows systems, ensure the following requirements are met before installing the software: v The operating system user supplied to the installation program must be an administrator (a member of the Windows defined Administrators group). v Windows Management Instrumentation (WMI), Remote Registry and the Server Windows services must be enabled and running. v The SMB protocol must be enabled and configured. It can be configured to run via NetBIOS over TCP/IP using port 139 or directly on TCP/IP (without NetBIOS) using port 445.
Chapter 3. Installation tasks

111

v Be sure that ports used by protocols you are using are not blocked by firewalls or security policies. This would include ports 137 and 139 if SMB is configured to run on NetBIOS over TCP/IP, or port 445 if SMB is run directly on TCP/IP (without NetBIOS). v If your Windows configuration supports Simple File Sharing it must be disabled. v The Windows drive share name C$ and folder IPC$ must be shared. v For Windows 2008 Server systems that support it password protected sharing must be disabled and shares must be shared for the Guest or Everyone accounts. v For Windows 2008 Server, User Account Control (UAC) must be disabled. v If Cygwin is installed on the remote Windows system the SSH daemon (sshd) must be uninstalled or disabled. Remote configuration does not support accessing network drives on the local or remote system.

Deploying Provisioning Manager EAR files
This section contains information about deploying Provisioning Manager EAR files manually into WebSphere. The following instructions are used to manually deploy the Provisioning Manager maximo.ear and maximohelp.ear files into WebSphere Application Server. Although the Provisioning Manager installation program deploys these EAR files when you install, there might be a few instances where it would be desirable to redeploy these EAR files manually: v If you modify any database connection parameters in the maximo.properties file after the initial installation, you will have to rebuild of the maximo.ear file (procedure covered in the IBM Tivoli Provisioning Manager System Administrator Guide), and then redeploy it in WebSphere Application Server. In this scenario, you would likely only rebuild and redeploy the maximo.ear file. You would not be required to rebuild and redeploy the maximohelp.ear file. v Provisioning Manager must be installed into a WebSphere application server. However, Provisioning Manager can be run within the framework of a WebSphere cluster. If you want to deploy Provisioning Manager in a cluster, you can either redeploy the Provisioning Manager EAR files into a cluster, or, create a cluster from the application server used during the installation. If you have already installed Provisioning Manager into an application server but would like to redeploy into a cluster , then you will need to either uninstall the MAXIMO application (“Manually uninstalling Provisioning Manager applications from WebSphere Application Server Network Deployment” on page 115), or provide a new name for the application when installing the MAXIMO application into a cluster (“Manually installing Provisioning Manager applications into WebSphere Application Server Network Deployment” on page 114). v If you have installed Provisioning Manager into a development environment, you might at some point like to migrate the deployment into a test or production environment. In this scenario, you will need to deploy both the maximo and maximohelp applications into the new environment. The steps outlined in “Manually installing Provisioning Manager applications into WebSphere Application Server Network Deployment” on page 114 should be performed for both applications. Related tasks “Manually building EAR files” “Manually deploying EAR files” on page 113 “Completing MEA registraton” on page 113

Manually building EAR files
You can manually build Tivoli Provisioning Manager EAR files if, for example, you modify a database connection parameter in the maximo.properties file after the initial installation. To manually build Tivoli Provisioning Manager EAR files, complete the following steps:

112

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

<WASAdminUserName> A WebSphere® Application Server Network Deployment account with deployment privileges. Deploy the maximohelp EAR file: <CCMDB_HOME>\jacl\solutions\DeployApplication. Completing MEA registraton MEA registration is required for process managers that include integration with other software. Run the following command: Chapter 3. <WASApplicationServerName> The name of the WebSphere Application Server Network Deployment application server. 2. <WASAdminPassword> The password of the user specified in the WAS User parameter. you must manually perform MEA registration after manually deploying the maximo EAR file. <WASWebServerName> The name of the WebSphere Application Server Network Deployment Web server. complete the following steps: Procedure 1.bat <WASAdminUserName> <WASAdminPassword> "MAXIMO" <WASNodeName> <WASApplicationServerName> "<CCMDB_HOME>\maximo\deployment\default\maximo. Build the maximo EAR file: <CCMDB_HOME>\maximo\deployment\buildmaximoear. To manually deploy Tivoli Provisioning Manager EAR files. you must deploy the EAR files manually. Deploy the maximo EAR file: <CCMDB_HOME>\jacl\solutions\DeployApplication. Installation tasks 113 . If you have chosen the option of deploying application files manually later during the Tivoli Provisioning Manager installation process. To manually perform MEA registration.cmd|sh Manually deploying EAR files You can manually deploy Tivoli Provisioning Manager EAR files if your organization has application deployment restrictions that require that you deploy application files either manually or through another approved process.bat <WASAdminUserName> <WASAdminPassword> "MAXIMOHELP" <WASNodeName> <WASApplicationServerName> "<CCMDB_HOME>\maximo\deployment\default\maximohelp.cmd|sh 2. <WASNodeName> The name of the WebSphere Application Server Network Deployment node. <WASVirtualHost> The name of the WebSphere Application Server Network Deployment virtual host.ear" <WASVirtualHost> <WASWebServerName> where.Procedure 1. Open a command prompt on the administrative system. Note: If you are deploying using a WebLogic server.ear" <WASVirtualHost> <WASWebServerName> 2. complete the following steps: Procedure 1. Build the maximohelp EAR file: <CCMDB_HOME>\maximo\deployment\buildhelpear.

From the Choose to generate default bindings and mappings. and then click Install New Application. From the Select installation options page. <MAXPASSWD> The maximo user password. 16. Deploy enterprise beans. If you are deploying to a cluster and want to keep the application that was installed during the Provisioning Manager installation. WAR. <PORT> The HTTP port on the WebSphere Application Server Network Deployment manager server. From the Provide options to perform the EJB Deploy page. Procedure 1. <CELL_NAME> The WebSphere Application Server Network Deployment cell name. 14. From the Map shared libraries page. Manually installing Provisioning Manager applications into WebSphere Application Server Network Deployment This section contains information about manually installing Provisioning Manager applications into WebSphere Application Server Network Deployment. 114 IBM Tivoli Provisioning Manager Version 7. select your virtual host from the drop down box for all modules and then click Next. or SAR module to upload and install. Ensure Distribute application. accept the defaults and click Next. you will need to use a different application name value here. and then click Next. accept defaults and click Next. set the application name to be MAXIMO. and then click Next 6. From the Provide JSP reloading options for Web modules page. From the Specify the EAR. select Local file system. <WASDMGR> The fully-qualified host name of your WebSphere® Application Server Network Deployment manager server. and Create MBeans for resources are all checked and then click Next. 13.2 Installation Guide . From the Map virtual hosts for Web modules page. Select Show me all installation options and parameters.ear file. 2. accept defaults and click Next. From the Map modules to servers page. By default this value is ctgCell01. select Generate Default Bindings.ear/meaweb. ensure Activation specification is set to intjmsact. select the cluster (or application server) and webserver listed. 12. Also select all modules appearing in the modules table by selecting their respective check boxes. page. Click Apply. From the Provide JNDI names for beans page. accept defaults and click Next. 15. accept defaults and click Next. page. 8. 9. From the Application Security Warnings page. Click the Applications link. <MAXUSER> The maximo user. and then click Next. JAR. 4./installedApps/<CELL_NAME>/MAXIMO. 10. 5. 3. Log in to the WebSphere Application Server Network Deployment administrative console. 17. click Continue. From the Initialize parameters for servlets page. 11. From the Map EJB references to beans page. 7. in the Clusters and Servers text box. and then browse to the location on your system of the maximo. From the Bind listeners for message-driven beans.war/ WEB-INF/MeaRegistrationFiles/taddm where. accept defaults and click Next.<CCMDB_HOME>\jacl\solutions\meareg <WASDMGR> <PORT> <MAXUSER> <MAXPASSWD> none none . and then click Next.

click the check box next to the application just installed. first select the check box adjacent to the maximouser role. 3. 24. Click Uninstall. Select the mail. 22. 7. Once completed. complete the following steps. From the Map context roots for Web modules page. accept defaults and click Next. Manually uninstalling Provisioning Manager applications from WebSphere Application Server Network Deployment This section contains information about uninstalling Provisioning Manager applications from WebSphere Application Server Network Deployment. and then click Start.adminEmail Property Name. From the Live Refresh dialog. click Finish. From the WebSphere Application Server Administrative Console navigation pane. From the Ensure all unprotected 2.host property and set the Global Value attribute to your SMTP host.smtp. Click the Live Refresh icon in the toolbar. 6. Installation tasks 115 . Open the WebSphere Application Server Network Deployment Administrative Console. Select the Webserver listed in the table. 26. Expand the mail. 3. accept the defaults and then click Next. 19.x methods have the correct level of protection page. 2. From the Map security roles to users or groups page. 20. the Provisioning Manager applications are named maximo and maximohelp. 5. 4. Navigate to Go To > System Configuration > Platform Configuration > System Properties Using the Filter feature.smtp. and then check All authenticated? before clicking Next.smtp. Configuring SMTP If you did not configure SMTP parameters during installation. Procedure 1. 21. search for the mxe. you will have to configure them through the product console. To configure SMTP for Provisioning Manager. and then click Generate Plug-in. 25. select Servers > WebServers. From the summary page. 6. 23. Chapter 3. and click Start. click OK. Click Stop. 2. accept defaults and then click Next. Before you begin This task must be completed before you begin the tasks described in “Applying changes to the database” on page 116.host Property Name. click Propagate Plug-in. From the Map environment entries for Web modules page. Using the Filter feature.18. From the WebSphere Application Server Network Deployment Administrative Console navigation pane. 8. 4. Select the check box next to the application you are uninstalling.host record check box. 5. Click the Applications link. select Applications 27. Procedure 1. Select the check box next to the application you are uninstalling. Select the check box next to the application that was just installed. Click on Applications. Login to the console as maxadmin. search for the mail. By default.

10. decide which additional languages you need before starting the language pack installation. c. 116 IBM Tivoli Provisioning Manager Version 7. and you set the locale or your machine to a language that was installed as an additional language. Failing to turn off Admin Mode within the application will cause cron tasks to fail. and then click OK when prompted. Turn Admin Mode OFF. menu choices.bat 8. Restart the MXServer application within WebSphere Application Server Network Deployment. the previously installed languages will also be reloaded at that time. Navigate to Go To > System Configuration > Platform Configuration > Database Configuration. Click Turn Admin Mode OFF. item and company sets and so on. On the administrative system. Installing the language pack You can add languages to the product by installing the Tivoli Provisioning Manager language pack. Applying changes to the database When you create organizations. select Manage Admin Mode. Procedure 1. 12. Click the Live Refresh icon in the toolbar. v In some cases. v Note that even if you added additional languages through the language pack installation program. select Apply Configuration Changes. Every object that must be updated in the Maximo database will display a status of To Be Added. To Be Changed should not appear in the status column for objects listed. 6. This task will take several minutes to complete. This is a known limitation and does not indicate that the language pack installation failed. and then click OK when prompted. From the Select Action list. v You must load all languages that you need during the initial installation. a. Before you begin v If you plan to add language support to Tivoli Provisioning Manager. for example. 5. b. select Manage Admin Mode. On the Select Action list. Expand the mxe. shortcut elements appearing in the interface. Select the mxe.adminEmail record checkbox. Each additional language selected increases the installation time. which will apply the changes to the Maximo database. will only be displayed in the base language designated. you might still encounter instances in the product interface where items are displayed in the language you identified as the base language of the machine. To apply configuration changes to the Maximo database. these configuration changes must be applied to the Maximo database. If you decide to install additional languages at a later time. From the Live Refresh dialog. or in English only. 7. Log out of the Maximo console.2 Installation Guide . 11. work types. you must use the language pack installation program before you perform any post-installation steps. complete the following steps. 4.9.adminEmail property and set the Global Value attribute to your e-mail address. v Because language pack installation might take an extended period to complete. 3. You can use the Refresh Status button to view progress. Any changes made to the information from customization or fix pack installation will be lost. Click Turn Admin Mode ON. run the following command: v MAXIMO_HOME\maximo\tools\maximo\dropbackup. click OK. Navigate to Go To > System Configuration > Platform Configuration > Database Configuration. Login to the Maximo console as maxadmin 2. 9. Once Admin Mode has been successfully enabled.

In the launchpad navigation pane.v Ensure that MXServer is started. select the additional languages to be supported. From the Pre-installation Summary panel. see “Installing and refreshing language support files for a package” on page 119. 8. In the launchpad navigation pane. 6. Application EAR files will be deployed later either manually or through the use of the product installer at a later date. Start the launchpad. You cannot change the base language at a later time. or you can defer the task until a later date. From the Deploy Application Files panel. 3. click Next. Scroll down to 2. Follow the instructions on the panel to back up. Follow the instructions on the panel to back up. start that server or service. Deploy application files manually later Select this option to defer the deployment of application files. Back up the deployment engine database. using the Tivoli Provisioning Manager language pack installation program. 2. Chapter 3. From the language selection summary panel. and then click OK.4 Back up base services home directory. and process managers. From the Additional language selection panel. click Custom Installation. From the Introduction panel. 9. This is the only time that you can select a base language. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. click Custom Installation. 7. then return to the custom installation page. 5. Proceed to “Installing Tivoli Provisioning Manager core components” on page 119. review the information and then click Next. 2. At any time after you have successfully deployed Tivoli Provisioning Manager. For more information. What to do next 1. This choice is only for use during the installation and its selection will not affect the languages being installed. Select a language for the installation. To install the language pack: Procedure 1. In the launchpad navigation pane. Back up the base services home directory. 3. then return to the custom installation page. Install the base services and required components and click 2. see: – “Starting middleware on Windows” on page 94 You can choose to add language support during installation. and then click Next. Installation tasks 117 . Use this option if your organization has application deployment restrictions that require that you deploy application files either manually or through another approved process.5 Back up the deployment engine database. you can add language support to Tivoli Provisioning Manager. select how to deploy the language files. including the Tivoli Provisioning Manager user interface. click Install. 4. Install base services and required components and click Install the language pack. The Tivoli Provisioning Manager process managers can be updated using this method. select a base language that will be used with Tivoli Provisioning Manager. click Custom Installation. then scroll down to 2. v Ensure all middleware servers and services are running. then scroll down to 2. From the Base-language selection panel. and then run the language pack installation program again. and then click Next. Install the base services and required components and click 2. If you later deploy other process managers. If you get an error because of an inactive middleware server or service.

2 Installation Guide . Many process solution packages define a single language support feature with a feature identifier of LANG_SUPT_FEATURE. Deployment for packages with multiple language support features Packages can be deployed with multiple language support. you can install the language support files for the package by specifying the -loadlanguages command line flag when you perform a base install of a package using the -action install subcommand. Installing or refreshing language support after base install When the refreshlangs action of the Process Solution Command Line Interface is invoked for a package with multiple language support features. you can elect to also install the language support files for the package. Installing language support files at base install When you initially perform a base install of a package with the special language support feature. The language support for this special feature can also be installed after a base install or refreshed using the refreshlangs action of the Process Solution Command Line Interface. the language support features are managed just like other selectable features defined for the package. For these types of packages. you can install or refresh the language support files for the package.Deployment for packages with a single special language support feature Packages can be deployed with single special language support. only currently installed language support features for the package are refreshed. the Process Solution Installation wizard will unpack the language support files associated with the package and then invoke the Maximo Translation Data Toolkit -PMPUPDATE function. the Feature Selection Panel will display the language support feature in the set of available features for the package. The Process Solution Command Line Interface provides a -action refreshlangs subcommand for this purpose. The refresh processing is only performed against currently installed language support features. This is accomplished by re-execution of the deployment actions associated with all currently installed language support features. This action is only supported for packages that are already installed. The function is not available using the Process Solution Installation wizard. For these packages. the language support files for the package are unpacked and copied to the Provisioning Manager administrative workstation and the Maximo Translation Data Toolkit -PMPUPDATE function. Installing or refreshing language support after base install After the package has been initially installed. A process solution package that supports a variety of selectable features might also have multiple language support features. Note that this behavior differs from the 118 IBM Tivoli Provisioning Manager Version 7. In both scenarios. The action can be used even if the language support files were not installed when the package was originally installed. Installing language support files at base install The language support features for packages that define multiple language support could be deployed during a base install of the package or might be added after the base install using the new selectable feature support in the Process Solution Installation Wizard and Process Solution Command Line Interface. The refreshlangs action when invoked on a package with multiple language support features. Using the Installation Wizard When using the Process Solution Installation wizard to perform a base install of a package. The function to install or refresh language support files is only available using the Process Solution Command Line Interface. the Process Solution Command Line Interface allow this special language support feature to be deployed during a base install using the -loadlanguages parameter. will not install those language support features. When you select this check box. Using the Command Line Interface When using the Process Solution Command Line Interface.

For more information. as the installation program does not validate them. If you installed the middleware with the middleware installer. v If you are using a virtual host name on the computer where you are installing the core components. use the instructions provided in this section. see: v “Starting middleware on Windows” on page 94 2. see “Verifying WebSphere Application Server SSL Signer” on page 128. Tivoli Provisioning Manager for Dynamic Content Delivery. Installing Tivoli Provisioning Manager core components After you installed the base services. This utility imports the XLIFF files associated with the process manager into the Maximo database.refreshlangs behavior when applied against a package defining the special LANG_SUPT_FEATURE identifier. you can install the Tivoli Provisioning Manager core components. verify that SSL Signer is set properly. Make sure that you installed the base services. In that scenario. Tivoli Provisioning Manager for Job Management Service federator and Tivoli Provisioning Manager for OS Deployment). When a language support feature for a process solution package is installed using the process solution installers. Installing and refreshing language support files for a package A process solution package may define one or more language support features. XLIFF files associated with all support languages are unpacked onto the Tivoli Provisioning Manager administrative workstation. based on the base language and any other selected languages that have been installed into Maximo. Chapter 3. Make sure that the middleware applications are started. During installation: v Ensure that you enter the correct passwords in the installer panels. the special language support feature would be installed if it is not currently installed or refreshed if it is installed. The core components must be installed on the provisioning server (the agent manager. Installation tasks 119 . Procedure 1. The process solution installers provide some built-in special mechanisms for deploying language support for packages using this model. The Maximo Translation Data Toolkit -PMPUPDATE is invoked. v A package can define multiple language support features. Start the launchpad. 4. v Directory paths cannot contain a back slash as the last character of the path (\). v A package can define a single language support feature with a special feature identifier. Before you begin 1. the middleware applications are started automatically after installation. If you have rebooted the computer or if you installed the middleware manually. or you have installed another process manager. If you installed WebSphere Application Server manually (and not using the middleware installer). There are two models for how the process solution package can expose its language support. See “Installing the base services” on page 98. The selectable feature support in the process solution installers are used for deploying language support for packages using this model. v Always use fully qualified domain names when entering values for computer host names. If you intend to refresh language support files for the change or configuration management process managers. Tivoli Provisioning Manager for OS Deployment can only be accessed using the local host name of the computer. 3. note that Tivoli Provisioning Manager for OS Deployment does not support virtual host names.

select the Import data from middleware installer workspace check box and then specify the location of the middleware installer workspace. while DB2 is installed on a different computer. 5. v If the database server is on a separate computer. In the launchpad navigation pane. Select the language for the installation and click OK. The default value is: – C:\ibm\tivoli\mwi\workspace v Select the Use Service IP check box if you are using virtual IP addresses and host names for all the computers in your installation topology. If you selected Tivoli Provisioning Manager for OS Deployment. return to the custom installation page. v If you want to back up the database and the WebSphere Application Server configuration files. The virtual IP addresses and host names that you use in this installer must match the values that you specified during middleware installation. then do not select the DB2 client check box. If Cygwin is already installed. 3. Install Tivoli Provisioning Manager core components and click Verify core components installation prerequisites. This check box does not apply if you installed the middleware manually. Database Information You must use the same values that you used for the database during the base services installation. Accept the license agreement and click Next. v Only DB2 is supported. select the Use Remote Database check box. After verifying and confirming the prerequisites. 8. 6. Authentication Information Select the authentication type that is available in your environment: v Tivoli Directory Server v Microsoft Active Directory v Base Services Authentication To confirm that the base services administration user exists in the LDAP repository. Middleware Installer Workspace Information v If you installed the middleware with the middleware installer. Use this option only if you selected either Tivoli Directory Server or Microsoft Active Directory as the authentication type. Scroll down to 3. select the corresponding check box. this location is specified during middleware installation. click Next.2 Installation Guide . 7. 10. In the Welcome panel. accept the license agreement and click Next. specify all required fields and click Next. select the corresponding check box. The core components are: v v v v v Required: The agent manager Required: Tivoli Provisioning Manager for Dynamic Content Delivery Required: Tivoli Provisioning Manager for Job Management Service federator Optional: Tivoli Provisioning Manager for OS Deployment 2000 DB2 If you used the middleware installer to install the DB2 server and you are using a configuration where Tivoli Directory Server and Tivoli Provisioning Manager are installed on the same computer. 4. select all components and click Next. 9. click Custom Installation. In the Topology Configuration panel. In the Select Components panel. 120 IBM Tivoli Provisioning Manager Version 7. Oracle Database is not supported. Click Install core components.2. specify the directory where Cygwin is installed and click Next. In a multiserver topology.

specify the directory where they are located. if the database is located on a separate computer. in the FIPS 140-2 Configuration panel. specify all required fields and click Next. specify all required fields and click Next. specify all required fields and click Next. for single-server configurations. Block cipher mode Select a mode for encrypting blocks of data with the selected cipher algorithm.5. Cygwin 1. The default value is: – Program Files\IBM\tivoli\common If you have a process automation engine product installed on your system.10 or later is required. see the National Institute of Standards and Technology web site. These directories must exist either on the provisioning server. Generated key pair size Select the size of the generated encryption keys. v Specify the directories to store the backups for the WebSphere Application Server configuration files and the database files. v To enable support for Federal Information Processing Standard (FIPS) 140-2. A block cipher encrypts data blocks of a fixed length. v If you want to verify the integrity of the installation images. If you enabled FIPS 140-2 compliance. v For more information about this standard and Tivoli Provisioning Manager compliance. In the DB2 Configuration panel. select the Verify file integrity check box. v If you are using downloaded installation images. Cygwin 1. A location that is geographically closest to you is recommended. In the Directories for Core Components panel. v Specify the directory for temporary files. 2000 DB2 Chapter 3. If you want to install Cygwin.7 or later is required. v Specify the directory for log files and serviceability scripts. specify the destination directory where you want the images to be copied. User Name Specify the user name for running the Cygwin SSH service. see “Compliance with Federal Information Processing Standard 140-2” on page 232.v If you do not require support for IPv6 communication in the Tivoli Provisioning Manager environment. Select a Cygwin download mirror site Select a location that you want to use to download Cygwin installation files. and so this field is not displayed in the Directories for Core Components panel. v If you require support for IPv6 communication in the Tivoli Provisioning Manager environment. v If you want to copy the installation images from DVDs. 11. or on the database server. v For detailed technical descriptions of cipher algorithms and encryption key options in relation to FIPS 140-2. Key pair generator algorithm Select the algorithm that you want to use for generating encryption keys. Installation tasks 121 . and select the Copy installation images from DVDs check box. the directory for log files and serviceability scripts was set as a common location by the other product. The values must match the values that you specified when you installed DB2. A block cipher mode determines how to apply a cipher algorithm to reduce repetitive patterns in the encrypted data. which can result in repetitive patterns in the encrypted data. 12. specify encryption options. Cipher algorithm Select the method to use for encrypting data. 13. select the corresponding check box.

database. The default is: v C:\Program Files\IBM\WebSphere\AppServer Fully-qualified Domain Name of the WebSphere Application Server The fully qualified domain name of the computer where you are installing the provisioning 122 IBM Tivoli Provisioning Manager Version 7. The default value is MAXDB71 . This value is case-sensitive. This check box does not apply if your database is installed on a separate computer. if your database is installed on a separate computer.example. In the WebSphere Application Server Network Deployment Configuration panel. Enter the same name as the value from the Database user ID field used when installing the base services. DB2. DB2 Server User Name The name of the administrator user on the server where DB2 is installed. then specify an existing instance name. This setting is the recommended option for installation. for example. Installation Directory The directory where WebSphere Application Server is installed. For more information about WebSphere Application Server configuration. 14. Local DB2 Instance Name The database instance name for the DB2 client. while DB2 is installed on a different computer. for example. DB2 Server Instance Owner The user who owns the database instance. DB2 Server User Password The password for the specified administrator user on the database server. specify all required fields and click Next. for example. Database Name for the IBM Tivoli Provisioning Manager database The database name can only contain uppercase letters. Use Tivoli Provisioning Manager recommended database configuration Leave this check box selected so that the installer configures your database with performance settings. see the WebSphere Application Server documentation. and numbers.Fully Qualified Domain Name or IP Address The fully qualified domain name of the server where DB2 is installed. v The default value is SystemDrive:\Program Files\IBM\SQLLIB. The default value is maximo.2 Installation Guide . The default value is MAXDB71. The default value is ctginst1. ensure that you specify the correct virtual host name. such as cell and node configuration. Node name for remote database The node name for the database server. The default value is: v db2admin DB2 Server Instance Owner Password The password for the instance owner. This setting is the recommended option for installation. DB2 Server Instance Port Number The DB2 TCP/IP port number used by this server to listen for connection requests from clients.com. Use Tivoli Provisioning Manager recommended instance configuration Leave this check box selected so that the installer configures your instance with performance settings. If you are using a virtual IP address or host name. If you used the middleware installer to install the DB2 server and you are using a configuration where Tivoli Directory Server and Tivoli Provisioning Manager are installed on the same computer. lowercase letters. Local DB2 Instance SQLLIB Directory The location of the local DB2 instance for the DB2 client. 50005.

The directory server contains information about your users. ensure that you specify the correct IP address or host name. User Base DN Applies to Tivoli Directory Server only. not all fields described are displayed. ensure that you specify the correct virtual host name. The default value is wasadmin. tpmserver. for example. Installation tasks 123 . Host SSL Port Applies to Tivoli Directory Server only. Specify the base distinguished name (DN) for the directory server. specify all required fields and click Next. for example. The default value is ctgDmgr01. The default value is ctgCell01. Host Public Port The port number for Tivoli Directory Server or Microsoft Active Directory. Deployment Manager Administrator Password Enter the password for the WebSphere Application Server administrative account. Deployment Manager Administrator User Enter the WebSphere Application Server administrative account name. for example. Depending on the authentication option selected in the Topology Configuration panel. 15. Select this option to enable secure communication with the directory server. Cell Name Enter the WebSphere Application Server Cell name. For more information about specific directory server settings. The default value is 636. Fully-Qualified Domain Name or IP Address The fully qualified domain name of the directory server. If you want to use the Distinguished Name of the user that you specify for the LDAP Binding User Name. The settings must match the organizational unit and the organization and country suffix specified in the middleware installer. The default value is ctgAppSrv01.example.example. In the Authentication Configuration panel. Application Server Profile Name Enter the WebSphere Application Server profile name of the application server.c=US. The default is 8879.o=IBM. Enter the secure port number of the Tivoli Directory Server. ldap. Deployment Manager Port Enter the administrator port for WebSphere Application Server.com. Server Name Enter the name of the Maximo application server. If you are using a virtual IP address or host name.com. This value is case-sensitive. If you are using a virtual IP address or host name. Chapter 3. For example. ou=users. Application Server Node name Enter the name of the WebSphere Application Server node. MXServer.ou=SWG.server core components. This value is case-sensitive. The default value is 389. see your directory server documentation. WebSphere Deployment Manager Profile Name Enter the WebSphere Application Server profile name of the deployment manager server. The default value is ctgNode01. select the check box below this field. so enabling this option is recommended to ensure that data transmission between the directory server and other computers is secure. Use SSL for LDAP Server Applies to Tivoli Directory Server only.

For example. or sAMAccountName. for example. as entered during the base services installation. The default value is: – C:\Program Files\IBM\tivoli\tpm Note: For some components. Administrator. as entered during the base services installation. Base Services Administrator Password Enter the instance administrator password. The default value is mxintadm. The default value is maxreg. The domain name for Microsoft Active Directory. cn (Common Name). User Logon Name Attribute Specify the LDAP attribute for user names in your directory server. as entered during the base services installation. specify all required fields and click Next.Microsoft Active Directory Server Domain Name Applies to Microsoft Active Directory only. User Search Filter There is a check on the User Search Filter during the installation that has to be correctly set before continuing. the installation program uses the predefined installation locations for these components. The default value is maxadmin. the %v will be replaced with the real user name. Integration User Enter the integration user ID. It contains information such as the objectclass that the user belongs to.2 Installation Guide . v Specify the installation directory. The binding user name for Microsoft Active Directory. such as GUID. as entered during the base services installation. See the following examples: v For Tivoli Directory Server: (&(cn=%v)(objectclass=organizationalPerson)) v For Microsoft Active Directory: (&(sAMAccountName=%v)(objectcategory=user)) The parameter %v is necessary because during the search.com. This filter is used for searching for the user in the registry. as entered during the base services installation. so it always saves a number of files on: – %SystemDrive% 124 IBM Tivoli Provisioning Manager Version 7. LDAP Binding User Name Applies to Microsoft Active Directory only. LDAP Binder User Password Enter the password for the bind distinguished name. Registration User Enter the registration user. for example. Enter the bind distinguished name for binding to the LDAP instance. 16. testmsad. LDAP Binding Distinguished User Name Applies to Tivoli Directory Server only. uid (User ID). or the deployment engine. The default value is cn=root. In the IBM Tivoli Provisioning Manager Configuration panel. Registration User Password Enter the registration user password. Base Services Administration User Enter the instance administrator user ID.

The default port number is 9443. v Specify the following port numbers: Software Distribution Infrastructure Server SSL Port Specify the port for communication with the provisioning server. tpmserverNode01Cell. This user is created during installation and is used to start the Tivoli Provisioning Manager services. The default value is 9046.jks. The default value is jks. Software Distribution Infrastructure Non SSL Port Specify the secure HTTP port for communication with the provisioning server. which is the WebSphere Application Server HTTPS port. The default value is 9080. The keystore file is a key database file that contains both public keys and private keys for SSL communication. The default value is tpmKeyStore. Common Agent Services Standalone profile path Specify the full path of the profile directory for the agent manager.v Specify the password for the user tioadmin. Tivoli Provisioning Manager SSL Keystore Password Specify the password for the Tivoli Provisioning Manager keystore. The default value is 9045. Your company name Specify your company name. A truststore file is a key database file that contains the public keys for SSL communication with target computers. The default value is the host name followed by Node01Cell. Tivoli Provisioning Manager SSL Port A port using server-side SSL to provide encryption and to authenticate WebSphere Application Server to the other servers. For example. Tivoli Provisioning Manager SSL Truststore Name Specify the file name of the Tivoli Provisioning Manager truststore. For example. specify all required fields and click Next. v Specify the keystore and truststore information: Tivoli Provisioning Manager SSL Keystore Name Specify the file name of the keystore file for Tivoli Provisioning Manager. This name is used on the SSL certificate created during installation. Agents will connect to the agent manager using Specify whether you want agents on managed computers to connect to the agent manager using the IP address or the fully qualified domain name of the server. Cell Name Specify the WebSphere Application Server Cell name. Installation tasks 125 . The default is the host name followed by Node01.tpmTrustStore. tpmserverNode01. Software Distribution Infrastructure Client SSL Port Specify a port for communication with clients using mutually authenticated SSL. Chapter 3. Tivoli Provisioning Manager SSL Truststore Password Specify the password for the Tivoli Provisioning Manager truststore. The default value is casprofile. WebSphere Profile Name Specify the WebSphere Application Server profile name of the application server for the agent manager. Node Name Enter the name of the application node. 17. In the WebSphere Profile Configuration for Agent Manager panel. The default value is WAS_HOME/profiles/casprofile.

example.jks file. if you have two security domains for the networks users. 126 IBM Tivoli Provisioning Manager Version 7.com as the security domain.jks) files. Agent Manager Fully Qualified Domain Name This value is normally the fully qualified domain name of the Tivoli Provisioning Manager computer.example.intranet. specify all required fields and click Next. The default value is 9511. Resource Manager Password The password for the resource manager user. Tivoli Provisioning Manager has a resource manager and subagents for software distribution and software inventory scanning. The default is 21000. This password is used to create the common agent. 18. If you are using a remote computer for agent manager specify the IP address of the remote computer. This value is case-sensitive. Secure Port A port using server-side SSL with client authentication to provide encryption and authenticate the agent manager to clients.jks) and keystore (agentManagerKeys. The default value is 9513.com and dev. A common agent or resource manager compares the certificate in its copy of the agentTrust. If you are using an existing agent manager installation that was not installed with this installer.example. Resource Manager User Name The user name for the resource manager on the agent manager server.com. If you are using an existing agent manager installation that was not installed with this installer. Agent Manager Install Directory The installation directory for the agent manager. Registration Port The registration port uses server-side SSL to provide encryption and authenticate the agent manager to clients. you would specify users. For example. The default user name when you install the agent manager with this installer is tpmManager.intranet. Agent Manager Password This password is used by the agent manager to create the Certificate Authority Certificate and to unlock the agent manager trust keystore (agentManagerTrust. Specify the security domain that contains the assets to be managed with Tivoli Provisioning Manager. Agent Manager IP address The IP address of the agent manager computer. The default value is 9512. For example. specify the fully qualified domain name of that computer. Each product that uses Tivoli Common Agent Services has its own resource manager and subagents. the default password is password.intranet. Security Domain Specify the domain that is managed by a single access policy. Ensure that there are no extra spaces before or after specified path.com. and you only want Tivoli Provisioning Manager to manage assets in users.intranet.2 Installation Guide . In the Agent Manager Configuration panel.Starting Port Specify the lowest port number used by the agent manager. If you installed the agent manager on another computer. the default user name is manager. Public Port The unsecured port number for communications between the agent manager and the clients.jks file with the certificate presented by the agent manager to ensure that it registers with the correct agent manager.example. Registration password A common agent must provide this password to register with the agent manager and to unlock the agentTrust.

c. ensure that the value that you specify ends in a \. a.zip file from the Supplemental DVD for your operating system to the ITM server local directory. The default is 8080. In the Tivoli Provisioning Manager for Job Management Service federator Configuration panel. Results The following software components are installed: v Tivoli Provisioning Manager engines v The agent manager v Tivoli Provisioning Manager for Dynamic Content Delivery v Tivoli Provisioning Manager for Job Management Service federator v Tivoli Provisioning Manager for OS Deployment What to do next 1. Procedure 1. Installation tasks 127 . 2. Chapter 3. To change the language after installation. 21. to the directory where you extracted the files. The default directory is: v C:\tpmfosd files\. Proceed to “Installing Tivoli Provisioning Manager web components” on page 128. v Specify the installation directory for the dynamic content delivery. specify the installation directory for the Tivoli Provisioning Manager for Job Management Service federator and click Next. click Go To > Deployment > OS Management > Boot Servers. 20. HTTPS Port: The secure HTTP port for the Tivoli Provisioning Manager for OS Deployment console. and select the Configuration tab. specify all required fields and click Next. specify all required fields and click Next. Change the current directory. In the Tivoli Provisioning Manager for OS Deployment panel. Review the summary of your installation settings and click Next. 23. If you are using the root directory of a drive.19. 22. Installing the language pack for Tivoli Monitoring agent Follow these procedures to install the language pack. When the installation is complete. Extract the LP_ITMAgentForTPM72. Before you begin Ensure that %JAVA_HOME%\bin is in the PATH system variable. Data directory: The directory for operating system images and files managed by Tivoli Provisioning Manager for OS Deployment. You can install the language pack on a system which has one or more of the following components: v Tivoli Enterprise Portal server v Tivoli Enterprise Portal client v Tivoli Monitoring agent (Tivoli Provisioning Manager server). In the Dynamic Content Delivery Configuration panel. click Finish. For example D:\ Note: The language of Tivoli Provisioning Manager for OS Deployment installation is the language of the operating system. The default is 443. HTTP Port: The HTTP port for the Tivoli Provisioning Manager for OS Deployment console. b.

Run the following command to check if the SSL signer is set properly in WebSphere Application Server: wsadmin. click Next. Otherwise. On the Select Action panel.bat <candle_home> Tivoli Monitoring directory <install_mode> One of the following values: v gui v console v silent On the Tivoli Provisioning Manager computer lpinstaller. Enter your WebSphere Application Server user name and password. click Next and then click Done. select Tivoli Monitoring agent for Tivoli Provisioning Manager and click Next. Tivoli Enterprise Portal client. select Add/Update to install or update the language pack and click Next. 5.bat -lang jython 4. you can install the web components. If asked to add signer to the trust store. 128 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide . Procedure 1. type y. Results The language pack for Tivoli Monitoring agent is installed. 5.exe 4. verify that SSL Signer is set properly. Installing Tivoli Provisioning Manager web components After you have installed the core components.3. specify the path of where you extracted the nlspackge directory and click Next. 2. 10. On the Select Language panel. 8. Restart the Tivoli Enterprise Portal server. Start the Tivoli Provisioning Manager core component installation. select the language from the list and click Next. Log on as the administrator user. 6. You must install the web components on the same computer on which you installed the base services. On the Select Product panel. Change to the directory WAS_HOME/AppServer/profiles/AppSrv01/bin. 6. On the Preview panel. 3. and Tivoli Monitoring agent. 7. 9. On the Introduction panel. either the provisioning server or the administrative workstation. Run the installer with the appropriate command: On the Tivoli Enterprise Portal client and server lpinstaller. On the Choose Folder panel. Verifying WebSphere Application Server SSL Signer If you installed WebSphere Application Server manually (and not using the middleware installer). the signer was already added to the truststore.

In the Process Solution Installer Packages Installation panel. The default value is maximo. Accept the license agreement and click Next. click Custom Installation. To stop the Cygwin SSH daemon from a command window. If you have rebooted the computer or if you installed the middleware manually. Database User ID Enter the user ID to access the database. Ensure that the middleware is started. Note: Do not use the WebSphere Application Server console to modify Tivoli Provisioning Manager user passwords. 2. use the changePassword. verify that the middleware is started. See: v “Starting middleware on Windows” on page 94 3. For more information on how to change your password. Ensure that the Cygwin SSH daemon is stopped on the provisioning server and the administrative workstation (if your configuration requires one). Database Password Enter the password for the specified database user name. Base Services Installation Directory Specify the full path of the base services installation directory. The default value is wasadmin. Tivoli Provisioning Manager is configured to start the WebSphere Application Server profiles automatically with this user name when you start Tivoli Provisioning Manager. click Next. Ensure that the core components are installed. In the launchpad navigation pane. 5. This user must be the same user ID that you specified during base services installation. If you used the middleware installer to install the middleware.Before you begin 1. run: cygrunsrv --stop sshd Procedure 1. WebSphere Application Server Administrative User Name Enter the WebSphere Application Server administrator user name. Start the launchpad. WebSphere Application Server Remote Access Password Specify the password for the remote access user. Administrator. for example.cmd|sh tool to change the password. 3. specify all required fields and click Next. 4. see the changePassword command in the information center. the middleware applications are started after installation. Install the Tivoli Provisioning Manager web components and click Install Tivoli Provisioning Manager web components. run: net stop sshd To stop the Cygwin SSH daemon from a Cygwin shell window. The default location is: v C:\IBM\SMP Chapter 3. WebSphere Application Server Password Enter the password for the WebSphere Application Server administrator user. Instead. WebSphere Application Server Remote Access User Name Enter the name of a user with administrator access. In the Welcome panel. Installation tasks 129 . 2. See “Installing Tivoli Provisioning Manager core components” on page 119. Scroll down to 4.

“Post-installation tasks. otherwise no language packs are installed. Click Finish. In the Installation Preview panel. What to do next Before you start using Tivoli Provisioning Manager. you must select this check box. and then click Next. 7. 130 IBM Tivoli Provisioning Manager Version 7. Results The web components are now installed.” on page 131. additional configuration is required. review your installation settings.Load language support files associated with the packages Select the check box to update the language files for web components. When the installation is complete. If you installed language packs during base services installation using the steps in the topic “Installing the language pack” on page 116. See Chapter 4. 6. Important: Leave this check box clear if you installed a process automation engine product that does not install language pack support by default. the Installation Summary panel is displayed.2 Installation Guide .

Extract the LP_ITMAgentForTPM72. select the language from the list and click Next. to the directory where you extracted the files.exe 4. On the Select Action panel.zip file from the Supplemental DVD for your operating system to the ITM server local directory. 7. Procedure 1. Run the installer with the appropriate command: On the Tivoli Enterprise Portal client and server lpinstaller. click Next and then click Done. Before you begin Ensure that %JAVA_HOME%\bin is in the PATH system variable. 2003. 3. © Copyright IBM Corp. click Next.bat <candle_home> Tivoli Monitoring directory <install_mode> One of the following values: v gui v console v silent On the Tivoli Provisioning Manager computer lpinstaller. you must use the Tivoli Provisioning Manager language pack installation program before you perform these post-installation steps. 6. Important for language support: If you plan to add language support to Tivoli Provisioning Manager. Change the current directory. On the Preview panel. On the Select Product panel. 9. Installing the language pack for Tivoli Monitoring agent Follow these procedures to install the language pack. select Tivoli Monitoring agent for Tivoli Provisioning Manager and click Next. some configuration might be required after the product is installed. 2010 131 .Chapter 4. specify the path of where you extracted the nlspackge directory and click Next. select Add/Update to install or update the language pack and click Next. 5. 2. On the Introduction panel. 8. On the Choose Folder panel. On the Select Language panel. You can install the language pack on a system which has one or more of the following components: v Tivoli Enterprise Portal server v Tivoli Enterprise Portal client v Tivoli Monitoring agent (Tivoli Provisioning Manager server). Post-installation tasks Depending on the features that you plan to use.

Procedure 1. Backing up the administrative workstation If you do not want to keep the administrative workstation active after installation. Back up the installed base services and web components.2.1.2 Installation Guide . Copy the deployment directory to the new computer. new applications. Change to the following directory: v C:\ibm\SMP\de 4.0 132 IBM Tivoli Provisioning Manager Version 7.[bat|sh] 5. Run the following command: v de_backupdb. Tivoli Enterprise Portal client.cmd -bfile C:\IBM\SMP\DE_BACKUPS\AFTER_INSTALL_PMP_7. However. the computer is required to install program patches. run the following command: v de_restoredb. Restart the Tivoli Enterprise Portal server.cmd -bfile C:\IBM\SMP\DE_BACKUPS\AFTER_INSTALL_PMP_7.0. Because the installation of the deployment software on the administrative workstation also includes changes to the Windows registry. you must back up the installation so that all settings can be restored when you want to change your installation. product upgrades. Create a backup of the deployment directory. Table 21. v C:\IBM\SMP 3.2. perform the following steps: 1. and Tivoli Monitoring agent. run the following command: si_inst.0. To restore the backup of the installed packages. The default location is: v C:\IBM\SMP 2.0 2. Copy the registry entries into the Windows registry of the new computer. Registry entries for the base services Location My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Tivoli Base Services Key name InstallDir Version Key value C:\IBM\SMP 7. new process managers. you must create a backup of the software installed on the computer. a. Change to the following directory: v C:\Program Files\IBM\Common\acsi\bin b. If you are using a virtual server for your administrative workstation. 3. and additional language packs. You can also back up the administrative workstation manually as described in this section.10. If you later need to restore the backup.6 Results You now have a backup of the administrative workstation. you can create a virtual server image to save the administrative workstation configuration. Create a backup of the registry entries. The administrative workstation is not required to use Tivoli Provisioning Manager after installation. Results The language pack for Tivoli Monitoring agent is installed.1. To reinstall the deployment engine.

In Internet Explorer. click Tools > Options. For more information. Log on as the tioadmin user or the Administrator user. To start the provisioning server in other cases. Click OK. see “Starting middleware on Windows” on page 94.0. if the provisioning server is stopped and you need to restart it. Click Security Devices. Change to %TIO_HOME%\tools 3. Disable all TLS cipher suites that are not FIPS compliant. 8.0 4. 4. Click the Advanced tab.0 – Clear Use SSL 3. Post-installation tasks 133 . Click the Encryption tab. Under Security: – Clear Use SSL 2. Click Apply. 3. for example. Before you begin Ensure that the middleware applications are started. 7. Type tio. 2. Procedure v For Internet Explorer 6 or 7: 1. Follow these steps only if you want to start the provisioning server after installation. 3. Select NSS Internal PKCS #11 Module and then click Enable FIPS. 2. In the Protocols section. Starting the provisioning server on Windows After installing Tivoli Provisioning Manager. Note: You must have a master password set for each listed security device before FIPS-mode can be enabled. – Clear Use SSL 3. v For Firefox 3: 1. and then click OK. Click the Advanced icon. In Firefox.cmd start tpm Chapter 4. 5.0 – Select Use TLS 1. – Select Use TLS 1. click Tools > Options.Configuring a web browser for Federal Information Processing Standard 140-2 compliance If you have enabled Federal Information Processing Standard (FIPS) 140-2 compliance. you must enable Transport Layer Security (TLS) in the web browser to make the connections with the provisioning server FIPS 140-2 compliant. 6. 2. See step 3 of the instructions in the Firefox knowledge base article about FIPS 140-2 compliance for details. see “Starting and stopping the provisioning server on Windows” on page 211.0. Procedure 1. start the provisioning server so that you can use the product.

Procedure 1. Filter This value is the Virtual Member Manager object class that the service uses to search for group objects in LDAP: Group GroupSearchAttribute This value is the LDAP group object attribute used to search for groups under the configured directory subtree. 4. Click Go To > System Configuration > Platform Configuration > Cron Task Setup. Configure the following values: Active? Enable the Active? option by selecting the check box. cn. Credential This value is the password used for the Principal account. open a web browser and log on by typing: https://host_name:9443/maximo 5.2008 Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. Locate and select the VMMSYNC cron task. see User Account Control Step-by-Step Guide.ou=SWG. 2. The default user is maxadmin. Change the following object entries to use the organizational unit ou value that you defined for your organization when setting up Provisioning Manager middleware. and click it. Open a web browser and go to http://host_name:port/maximo. After the provisioning server is ready.2 Installation Guide . GroupMapping This field contains XML mapping files that map LDAP object attributes to database repository table columns. and press Enter.dc=IBM. VMMSYNC is the cron task that schedules the synchronization between Provisioning Manager and Virtual Member Manager. 6. 3. Customize it to use the organizational unit ou and domain name dc values that you defined for your organization 134 IBM Tivoli Provisioning Manager Version 7. 5.c=US for IBM Tivoli Directory Server and ou=groups. For more information about user account control in Windows 2008. ou=groups.dc=COM for Microsoft Active Directory. Log on to Provisioning Manager using the maxadmin user ID.o=IBM. The manual procedure is required only if you need to change the existing configuration of the cron task. 4.ou=SWG. For example. Principal This value is the user required by the CronTask application to connect to the local Virtual Member Manager service. This cron task is set up automatically during installation. Type VMM in the Cron Task field. For example. Manually configuring directory synchronization for WebSphere Application Server Network Deployment You can manually configure a cron task to schedule synchronization of users and groups between a directory server and Provisioning Manager. enter the password for wasadmin. This value can be any directory server administrative user that has authorization to connect to the local Virtual Member Manager service. Basedn This value defines the LDAP subtree that the Virtual Member Manager cron task uses to search for group objects. Type the user name and password. In this case.

Results By default. UserMapping This field contains XML mapping files that map LDAP object attributes to database repository table columns.ou=SWG.c=US for IBM Tivoli Directory Server and uid=wasadmin.ou=SWG. For example. SynchAdapter psdi. ou=users.vmm. For example.dc=IBM.ou=SWG. The updated parameters are used at the next scheduled synchronization. 7. Click the save icon.o=IBM. To configure security for this model.ou=SWG.ou=users. cn=wasadmin. complete the following steps to turn off VMMSync to separate the user and security group information. cn for IBM Tivoli Directory Server and uid for Microsoft Active Directory.vmm.ou=users. UserSearchAttribute This value is the LDAP user object attribute used to search for users under configured directory subtree. Filter PersonAccount This value is the Virtual Member Manager object class that the service uses to search for user objects in LDAP. Post-installation tasks 135 . The authorization process is handled by loading the security roles information from the provisioning database.when setting up the middleware. Change the following object entries to use the organizational unit ou value you defined for your organization when setting up the middleware. If you want authentication to be handled by the LDAP server.security. You must click the arrow located in the header of the Cron Task Parameters table to view all parameters.security. the cron task runs every 5 minutes.VMMSynchronizer This value is the Java class that connects to the Virtual Member Manager local service to search for required objects. which stores the user information only. Change the Schedule field of the cron task if you want to change the interval. SynchClass psdi.c=US for IBM Tivoli Directory Server and ou=users.DefaultVMMSyncAdapter This value is the Java class that writes LDAP data to the database. Configuring the LDAP server for user authentication only When the installation is completed. Basedn This value defines the LDAP subtree that the Virtual Member Manager cron task uses to search for group objects.dc=COM for Microsoft Active Directory.o=IBM. you can configure security so that the authentication process uses the LDAP server.dc=IBM. Chapter 4. instead of by the Tivoli Provisioning Manager database. For example. you can configure your environment to store user information in the LDAP server and security roles and groups in the provisioning database.dc=COM for Microsoft Active Directory.

LDAPUserMgmt property. log on to the web interface and click Go To > Security > Users. and the membership of the users to the security groups. This user must 2. b. Click OK. e. Expand Filter and search for the mxe. 4. Note: If an exception occurs when you are trying to add a user to a security group. 2. d. Results If Current Value has a value other than 0. 2. click the Users tab and click New Row. the access rights must be changed so that you can change the group membership.cmd start. Click VMMSync and click the Cron Task tab.Procedure 1. For the changes to take effect. Click the Group tab and click the security group. Users are now separated and stored in the LDAP server for authentication only. Click group. type the user name or click and select the user to add to the security group. Clear the Active check box.MAXPROPVALUE SET PROPVALUE = ’0’ WHERE PROPNAME = ’mxe. Enter the required information and save your changes. to save your changes. Click also be created in the LDAP for the authentication server. Click 5. a. Log on to the database server and run the following SQL command: UPDATE <schema_name>. 136 IBM Tivoli Provisioning Manager Version 7. 6. To add users to the security group. The MAXADMIN user must change the permissions. click Go To > Security > Security Groups. Ensure that the mxe.cmd stop and then enter tio.LDAPUserMgmt property is not enabled. Click Select Users and select the user that must have the access rights to add other users to that security group. To create a security group.LDAPUserMgmt’ where <schema_name> is the schema name. In the User field. 7. When new users are added to the LDAP server. Now that VMMSync is disabled. 4. Confirm the changes by clicking OK again. Security groups are stored in the provisioning database for authorization purposes. Click Select Action > Authorize Group Reassignment. Click Go To > System Configuration > Platform Configuration > Cron Task Setup. complete the following steps: 1. type VMMSynch. To create a user. the LDAP server and provisioning database are not synchronized. Adding users and security groups You must add users and security groups to the provisioning database. Click Go To > Security > Security Groups. Procedure 1. Log in as MAXADMIN. c. security groups and users. restart the provisioning server: v Enter tio. In the Cron Task field. Ensure that Current Value is set to zero (0). to create the user. 3.2 Installation Guide . to create the security 3. Click Go To > System Configuration > Platform Configuration > System Properties. Enter the required information and save your changes. must be manually added to the provisioning database using the web interface.

Post-installation tasks 137 . 2.EO. Procedure 1. Click Go To > Security > Security Groups. you must set a global variable to specify so. Find the TCA. the OS deployment boot server object is not created. To create it. Chapter 4.SAP global variable and set its value to false. This parameter is set to true by default.f. Log on to the web interface as the user who now has the appropriate access rights to the security group. You must set the TCA. g. Setting up the infrastructure for software distribution tasks This procedure explains how to set up a scalable distribution infrastructure. The TCA.SAP global variable to false if you do not want to use the scalable distribution infrastructure.Create. If you are planning to use the scalable distribution infrastructure for your software distribution tasks. Log on to the web interface. Defining the boot server after installation You must create your boot server if you ran the installation program without the Tivoli Provisioning Manager for OS Deployment component. see Discovering an OS deployment server in the information center. you must run the TPMfOSD Installation Discovery against your local provisioning server. For more information.Create.EO. Click Go To > Provisioning Global Settings > Variables. Select the User tab and add the user.SAP global variable determines if the scalable distribution infrastructure is used or not.Create. For more information about the scalable distribution infrastructure. If you are not planning to use the scalable distribution infrastructure for your software distribution tasks.EO. you do not need to complete this post-installation task. If you ran the installation program without the Tivoli Provisioning Manager for OS Deployment component and then ran it again with the Tivoli Provisioning Manager for OS Deployment component selected. see Scalable distribution infrastructure in the information center. 3.

138 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide .

2010 139 . To uninstall Tivoli Provisioning Manager. Uninstall core components 2. uninstall the agent: Log on as Administrator user. Do not use other methods to uninstall Provisioning Manager. Open the Add/Remove Programs control panel. configure the terminal server to install mode by running: change user /install To uninstall the core components. uninstall it before you uninstall core components such as the device manager service. 3. such as the Add/Remove Programs panel.Chapter 5. Uninstalling the Tivoli Monitoring agent If you installed the Tivoli Monitoring agent. Uninstalling Tivoli Provisioning Manager A single uninstallation program for all Tivoli Provisioning Manager components is not available. Click Change/Remove. Uninstall middleware 4. 4. complete the tasks in this section. From the list of applications. Procedure To 1. Before you begin If Windows Terminal Server is installed. Remove remaining items Software is uninstalled Uninstalling Tivoli Provisioning Manager core components This section describes how to uninstall Tivoli Provisioning Manager core components. 1. dynamic content delivery. Uninstall base services and Web components 3. you must remove the software in the order below. 2. select IBM Tivoli Monitoring for Provisioning. or agent manager. © Copyright IBM Corp. 2003.

click Tivoli Provisioning Manager for OS Deployment. run the following command to open a DB2 command window: db2cmd b. complete the following procedure to uninstall it. including user data. 6. select Remove Tivoli Provisioning Manager for OS Deployment completely. Stop Tivoli Provisioning Manager for OS Deployment. 8. dynamic content delivery. Set the database instance to the Tivoli Provisioning Manager database instance. Check if the following directories exist. uninstall it before you uninstall core components such the device manager service. In a command window. In a command window. run the following commands on a Tivoli Provisioning Manager server where a DB2 client is installed. delete them. Run the following command to drop the database: db2 uncatalog database TPMFOSD db2 uncatalog node TPMFOSD db2 terminate 12.2 Installation Guide . a. 3. Click OK to confirm the uninstallation. click Next. Select Remove and click Next. 9. 7. 7. set db2instance=ctginst1 c. 4. a. run: net stop remboagent net stop remboserver 2. 6. set db2instance=ctginst1 c. click Finish. Uninstalling Tivoli Provisioning Manager for OS Deployment on Windows If you installed Tivoli Provisioning Manager for OS Deployment. To completely remove Tivoli Provisioning Manager for OS Deployment. 140 IBM Tivoli Provisioning Manager Version 7. In the Add/Remove Programs control panel. Click Change.” Uninstalling Tivoli Provisioning Manager for OS Deployment If you installed Tivoli Provisioning Manager for OS Deployment. Drop the Tivoli Provisioning Manager for OS Deployment database in the database server. The default is ctginst1.5. or agent manager. run the following command to open a DB2 command window: db2cmd b. Click Finish to complete the uninstallation. If the DB2 server is on a remote system. Set the database instance to the Tivoli Provisioning Manager database instance. What to do next Proceed to “Uninstalling Tivoli Provisioning Manager for OS Deployment. When Tivoli Provisioning Manager for OS Deployment is uninstalled. Click Remove. Select a language and then click —>. 5. Click Remove. If they still exist. On the welcome panel. In a command window. The default value is ctginst1. 10. Procedure 1. Run the following command to drop the database: db2 drop database tpmfosd 11.

” 2. and the instance owner is maximo.v The IBM Tivoli folder. Chapter 5. Run the commands: set db2instance=ctginst1 db2 list db directory c. 4. Close all database command windows and device manager consoles. Remove the device manager service database tables: 2000 DB2 a. If you were unable to remove Tivoli Provisioning Manager for OS Deployment using the uninstaller. drop the database: db2 drop database tpmfosd 3. For more information about user account control in Windows 2008. Stop Tivoli Provisioning Manager. remove it manually: a. Verify that the WebSphere Application Server profiles and the database are running. Change to the TIO_HOME/tools/DMS directory.sh] stop -t 2008 Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. Run the following command from the /TIO_HOME/tools directory: [tio. Uninstallation tasks 141 . 2. Set the database instance to the Tivoli Provisioning Manager database instance. If the database exists. Procedure 1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboODBC HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboServer Uninstalling Tivoli Provisioning Manager for Job Management Service federator This procedure explains how to uninstall the device manager service. c. Before you begin 1. 3. The default instance for a custom installation is ctginst1. Start the DB2 command line: db2cmd d. Open a command window. Log out as tioadmin and log back on as: v Administrator 2. Check if the following directories exist. If the following registry keys exist. remove the keys and any children keys. The default location is C:\Program Files\Common Files\IBM Tivoli v The data directory. Log on to the Tivoli Provisioning Manager server: v Log on as administrator. The default location is C:\tpmfosd files b. proceed to “Uninstalling Tivoli Provisioning Manager for Job Management Service federator. If they still exist. Check if the database tpmfosd is created. delete them. see User Account Control Step-by-Step Guide.cmd|tio. The default location is C:\tpmfosd files What to do next 1. The default location is C:\Program Files\IBM\Tivoli v The data directory. v The IBM Tivoli folder. If you removed Tivoli Provisioning Manager for OS Deployment successfully. b.

db_owner The database instance owner. change the line to: instWASPassword=pass5word 6./DMSremoveconfig. Change to the _uninst directory in the following directory: v C:\Program Files\ibm\DeviceManager 142 IBM Tivoli Provisioning Manager Version 7.bat MAXDB71 db2admin pas5word c:\Progra~1\ibm\DeviceManager maximo 3.sh] -server -file DMSconfig. b.2 Installation Guide .set db2instance=ctginst1 e. ensure that you use short names. continue with step 7. change the value of the password in the file to the password for the current WebSphere Application Server administrator. Enter the following command on a single line: [DMS_DB2_uninstall. For example. skip step 7 and continue with step 8. c. If DMS_WebApp is not installed. if the current password is pass5word. change tioadmin to the current WebSphere Application Server administrator user name. complete the following steps: a. In the instWASUsername=tioadmin line. b. Open the file DMSconfig. If you changed the administrator user for the directory server to another user name. 4. The default owner is db2admin. db_owner_pwd The password for the database instance owner.properties -showtrace 8. Log on to the WebSphere Application Server administrative console. d. The default value is: v C:\Program Files\ibm\DeviceManager Note: v Ensure that you include a backslash (\) at the end of the path. Click Applications > Enterprise Applications and verify if an application named DMS_WebApp is installed. If DMS_WebApp is installed. if the current WebSphere Application Server administrator is wasadmin. Remove the device manager service configuration: [DMSremoveconfig. Open a command window. schema_name The database schema name. In the instWASPassword line.bat|./DMS_DB2_uninstall. For example Program Files must be shortened to Progra~1.sh] db_name db_owner db_owner_pwd dm_dir schema_name db_name The name of the Tivoli Provisioning Manager database. v The directory path cannot include spaces. Verify if the device manager service application is installed in WebSphere Application Server: a. 7.bat|. For example: v DMS_DB2_uninstall.properties in a text editor. Change to the config directory in the following directory: v C:\Program Files\ibm\DeviceManager 5. The default value is maximo. change the line to: instWASUsername=wasadmin c. For directories that contain spaces. For example. dm_dir The full path of the device manager service installation directory.

Remove the device manager service installation directory: v C:\Program Files\ibm\DeviceManager What to do next Proceed to “Uninstalling Tivoli Provisioning Manager for dynamic content delivery. Procedure 1. 8. 2. replication. Verify if the cds_manager directory contains some directories named Gen1 or Gen2.[exe|bin] 10. Chapter 5. Before you begin 1. 3. Open a command window. The uninstallation wizard does not drop the registry database or delete the agent manager objects from the database. Uninstallation tasks 143 . See “Uninstalling Tivoli Provisioning Manager for Job Management Service federator” on page 141 and “Uninstalling Tivoli Provisioning Manager for dynamic content delivery. Ensure that the device manager service and the dynamic content delivery are uninstalled.” Uninstalling the agent manager Uninstall the agent manager to remove the agent manager servlets from WebSphere Application Server.9. 5. see User Account Control Step-by-Step Guide.exe|. Log on as a user with administrator access. 3.” 2008 Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. See “Uninstalling Tivoli Provisioning Manager for Job Management Service federator” on page 141. The default value for the cds_manager directory is: v Program Files\Common Files\InstallShield\Universal\cds_manager If the Gen1 or Gen2 directories exist. The default location is: v C:\Program Files\IBM\tivoli\CDS\_uninst 6. delete them. Run the uninstaller: uninstaller. and downloading of files. What to do next Proceed to “Uninstalling the agent manager. 4. Ensure that Tivoli Provisioning Manager is stopped. Change to the _uninst directory of the following directory. 2. When the uninstallation is complete. Run the uninstaller: [uninstaller./uninstaller. For more information about user account control in Windows 2008. remove the dynamic content delivery installation directory.” Uninstalling Tivoli Provisioning Manager for dynamic content delivery Uninstall Tivoli Provisioning Manager for dynamic content delivery to remove the component responsible for centralized control of the uploading.bin] 7. Ensure that Tivoli Provisioning Manager is stopped. Ensure that the device manager service is uninstalled. Log on as tioadmin.

The default value is ctginst1. The default owner is db2admin.sh] MAXDB71 ctginst1 mypassword 3. Set the database instance to the Tivoli Provisioning Manager database instance.[exe|bin] 5. such as the monitoring agent.[bat|sh] -delete -profileName casprofile 7. Before you begin 1. 6. Open a command window. db_owner_pwd The password for the database instance owner.bat|. The default profile name is casprofile. Ensure that other core components.bat|. If you want the command window to remain open so that you can see the status of the command after it runs. set db2instance=ctginst1 c.sh] db_name db_owner db_owner_pwd Note: The CAS_DB2_uninstall. Log out as tioadmin and log on as Administrator.Procedure 1. the dynamic content delivery. see “Uninstalling Tivoli Provisioning Manager core components” on page 139.bat script closes the command window after you run it. 2. db_owner The database instance owner. WAS_HOME/bin/manageprofiles. Log on as a user with administrator access. 2. v 2000 DB2 a. What to do next Proceed to “Uninstalling Tivoli Provisioning Manager engines./CAS_DB2_uninstall. Run the uninstaller and follow the instructions in the wizard: AM_HOME/_uninst/uninstaller. Tivoli Provisioning Manager for Job Management Service federator.2 Installation Guide . and the agent manager. 4. Tivoli Provisioning Manager for OS Deployment. For more information. are uninstalled. To start the DB2 command line. run the command: db2cmd b. For example: [CAS_DB2_uninstall. Change to the TIO_HOME/tools/CAS directory and run the command: [CAS_DB2_uninstall. Remove the profile directory WAS_HOME/profiles/casprofile. remove the last exit statement from the script. 144 IBM Tivoli Provisioning Manager Version 7. Delete the agent manager installation directory. Remove the database tables.” Uninstalling Tivoli Provisioning Manager engines Each core component must be uninstalled individually. replace the parameters with the appropriate values: db_name The name of the Tivoli Provisioning Manager database. In the previous command. Remove the WebSphere Application Server profile for the agent manager./CAS_DB2_uninstall.

4.3. 3. proceed to “Uninstalling the DB2 client. you can use the db2start command from a command line to start CTGINST1. Keep the user tioadmin so that it is ready for the reinstallation. It does not remove: v The database and application server v The log files Procedure 1. select DB2 client. Select Remove and click Next. What to do next 1. If the server has a virtual IP address a. dynamic content delivery.DB2COPY1 . complete the following steps: a. Ensure that the database is still running. Run the following command: %TIO_HOME%\_uninst\_uninstTPM\uninstaller. Proceed to “Uninstalling the base services and web components” on page 146. c. Click Change/Remove. Stop Tivoli Provisioning Manager and ensure that any running Java processes are stopped. b. Log on as a user with administrative permissions. b. From the list of applications. 6.msc and click OK. Uninstallation tasks 145 . Start the database: db2gcf -u -p 0 -i ctginst1 The uninstallation only removes the Tivoli Provisioning Manager engines. Click OK and click Finish. Chapter 5. uninstall it after you uninstall core components such as the device manager service. If you plan to reinstall Tivoli Provisioning Manager. To start the database: v 2000 DB2 In the following steps. the database instance is named ctginst1. Remove the Tivoli Provisioning Manager installation directory. Uninstalling the DB2 client 2000 DB2 If you installed the DB2 client. skip this step. c. Type services. For more information. or agent manager. Click Start and select Run. uninstall the DB2 client on Windows: Log on as the Administrator user. see: v “Starting and stopping the provisioning server on Windows” on page 211 4. d. If you installed the DB2 client. Log on as a user with administrative permissions. b. Log on as tioadmin. 2.” Otherwise. Procedure To 1. If the server does not have a virtual IP address a. 5. 2.exe 2.CTGINST1-0 and click Start the service. Select DB2 . Alternatively. Open the Add/Remove Programs control panel.

Remove the MAXIMO_HOME directory. The default location for MAXIMO_HOME is C:\ibm\SMP. What to do next If you are uninstalling middleware on Windows.Uninstalling the base services and web components To remove the base services and the web components. v If you did not use the middleware installer to install your middleware. see your middleware documentation for uninstallation instructions. 3. See “Uninstalling the base services and web components. remove the existing instance owner and DB2 administrator group. v If you reinstall middleware. 2. see “Recovering the deployment engine” on page 159. Ensure that WebSphere Application Server is running. do not uninstall the base services and web components. you must uninstall the middleware using the same middleware installer. 2. This task must be done before rerunning the middleware installation program. Therefore. provide the same value used previously for the DB2 administrators group during the reinstallation. Procedure 1. DB2 attempts to associate the owner of the default instance with this new group. AIX or Linux. Log on to the administrative workstation: v As the Administrator user. you must run the middleware installer to undeploy the previously deployed deployment plan. users and groups are not removed. proceed to “Uninstalling middleware. For more information. Service Request Manager (SRM) or Change and Configuration Management Database (CCMDB).bat. This attempt fails because the owner already belongs to the group specified during the initial installation. Before you begin v Make sure that the base services are uninstalled. the registry created when installing the middleware no longer matches with what is deployed. errors might occur. v At points during the uninstallation process. 4. When DB2 is uninstalled. Ensure that the core components are uninstalled. Before you begin 1. or if the installation failed while installing the base services. Otherwise.” Uninstalling middleware To uninstall the middleware. if you then try to reinstall middleware using the middleware installer. The middleware installation program creates a default instance for DB2 and adds the owner of the default instance to the DB2 administrator group specified. To specify a new DB2 administrators group. for example. If you think that your uninstallation process has experienced an error.” v If you installed the middleware using the middleware installer. Restore the deployment engine database to the backup you created before installing the base services.2 Installation Guide . 146 IBM Tivoli Provisioning Manager Version 7. refer to the middleware installer log files. If a different DB2 administrators group value is supplied. the middleware installer progress bar might appear to pause. Run the following command: v MAXIMO_HOME\_uninstall\uninstall. Note: If another Tivoli process automation engine product is installed on the same computer as Tivoli Provisioning Manager. the middleware installer progress bar resumes shortly after pausing. In most cases. use these steps to remove the software.

To uninstall the application server. For example: v C:\ibm\tivoli\mwi\workspace 9.DB2COPY1 . 7. click Cancel to exit the middleware installer.idsccmdb).idsccmdb). Start the launchpad. 8. Select a language for the installation and click OK. specify the workspace directory containing the currently deployed plan and click Next. 3. From the Welcome panel. After uninstalling Tivoli Provisioning Manager.” Removing items remaining after uninstallation Some uninstallation programs do not remove all files or configuration settings on the computer. Reboot the system if you plan to reinstall middleware on this system using the middleware installer. check that the installation directory has been deleted. From the undeployment preview panel.idsccmdb). Tivoli Provisioning Manager If you uninstalled Tivoli Provisioning Manager. 5. From the Choose Workspace panel. 4. complete the following steps before using the middleware uninstaller: 1. 12. From the Select Operation panel. Start DB2. Ensure that you remove all items remaining after uninstallation if you want to reinstall any Tivoli Provisioning Manager software.2 . Accept the licence agreement and click Next.2 . Start the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin Server v6. you might need to perform some cleanup tasks. Click Install middleware. In the launchpad navigation pane. 2. 6. The default location is: v C:\Program Files\IBM\tivoli\tpm Chapter 5. Log in as: v Administrator 2.2 . Start the idsccmdb DB2 instance (DB2 . What to do next Proceed to “Removing items remaining after uninstallation. 3. Uninstallation tasks 147 . click Next to undeploy the plan. From the successful undeployment panel. Ensure that you check for files and settings that need to be removed. 11. 4. ensure that the directory server (Tivoli Directory Server or Microsoft Active Directory) is running. click Next. 5. If you want to uninstall middleware after a failed middleware installation. select Undeploy the plan and click Next. Procedure 1. 10. The default location for the workspace is the last workspace location specified.IDSCCMDB). Stop the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin Server v6. Removing application files and configuration settings Files and configuration settings that remain after some applications are uninstalled can cause an installation of Tivoli Provisioning Manager to fail. click Custom Installation. Do not uninstall the directory server until the application server has been uninstalled. Stop the IBM Tivoli Directory Server (IBM Tivoli Directory Server v6.

complete the following steps: Start regedit. the agent ID is not automatically removed from the system.00. such as C:\windows. 4. Set up the environment using the following command: v C:\Program Files\IBM\common\asci\setup\setenv. Navigate to \HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\GUID\. Delete the \asci directory.f0.11. WebSphere Application Server If WebSphere Application Server was previously installed on the computer. Restart the provisioning server. 2. Typically. You must remove existing agent IDs from the computer before you install Tivoli Provisioning Manager. The default location is: – C:\Program Files\IBM\WebSphere\AppServer v The vpd.2 Installation Guide . For more information about the file. – The file is located in the operating system installation directory.d7.c9. The agent ID is the name of the installation directory of the common agent.properties file lists program components that are installed. 3.If this directory remains after uninstallation.53. If you are uninstalling the Tivoli GUID tool or the Tivoli Common Agent. manually remove the GUID from the registry.properties file for entries that must be removed. Remove the deployment engine database using the si_inst command: v C:\Program Files\IBM\common\asci\bin\si_inst. 148 IBM Tivoli Provisioning Manager Version 7.e6.ca.94. reinstallation of the product might fail.e6. Check the vpd. The following is an example of the registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\GUID] "Path"="C:\Program Files\Tivoli\guid" "TIVGUID"=hex:32. Middleware Installer Directories Ensure that the following directories are deleted: v 2000 DB2 – SystemDrive:\Program Files\IBM\SQLLIB where SystemDrive is the disk drive that contains the hardware-specific files used to start Windows. v Tivoli Directory Server – C:\Program Files\IBM\LDAP\V6.b6 @="" To 1.9a. verify the following items: v Ensure that the WebSphere Application Server installation directory is deleted. Remove the GUID entry. Removing the Global Unique Identifier A Global Unique Identifier is used to identify a Tivoli common agent on a computer.2 v IBM HTTP Server – C:\Program Files\IBM\HTTPServer The deployment engine database 1.bat 3.cmd 2. the system drive is C. see the following topic in the WebSphere Application Server information center.b0.9b.60.

you encounter an error that stops the uninstallation process. The deployment engine is reinstalled when the product installation program is run again. To verify that middleware products were correctly uninstalled. Uninstall the deployment engine si_inst -r -f Results You can safely ignore warnings that all files and directories cannot be removed. This exception is also recorded in the mwi. The middleware installer creates a default instance for DB2 and adds the owner of the default instance to the DB2 administrator group specified. This is a destructive process. Remove any locks held by deployment engine: erase "c:\Program Files\IBM\Common\acsi\logs\. if a different DB2 administrators group value is supplied. v In most cases. DB2 attempts to associate the owner of the default instance with this new group. you must check the deployment plan logs. which might fail because the owner already belongs to the group specified during the initial installation. you must reset the database to a clean state by uninstalling and reinstalling the deployment engine. When DB2 is uninstalled. users and groups are not removed. 2. the middleware installer does not stop the uninstallation process or report failures during the uninstallation process. To uninstall and resinstall the deployment engine database. If you do not have a backup of the deployment engine database. What to do next v If you plan to reinstall middleware using the middleware installer. For more information. Back up the deployment engine database of the administrative system before and after applying any updates to an existing deployment. Only in the case where you are uninstalling an application server that was secured using IBM Tivoli Directory Server and that directory server has not been started.lock*" 3. see “The middleware installer logs” on page 34. ensure that you provide the same value for the DB2 administrators group during the reinstallation. Uninstalling and reinstalling the deployment engine database These instructions are for restoring the deployment engine database to the state it was in before process managers were installed. remove the existing instance owner and DB2 administrator group before running the middleware installer again.Results The Tivoli Provisioning Manager uninstallation is completed. this deletes data for those products also. complete the following steps: Procedure 1. Uninstallation tasks 149 . 2. Chapter 5. During the reinstallation. Having backups allows you to recover from partial installation attempts where process manager components were partially installed.%PATH% 4. Include jre (Java) in the class path: set path=C:\IBM\SMP\jre\bin. If you must specify a new DB2 administrators group during the reinstallation. Change directory to the deployment engine installation location.log file. Before you begin 1. Stop the deployment engine: v Control Panel > Administrative Tools > Services > IBM ADE Service. If products other than Tivoli Provisioning Manager are using the deployment engine.

If the IBM ADE service is not running. 1. 3. When DB2 is uninstalled. “Uninstalling Tivoli Provisioning Manager. the deployment engine for the solution installer must be started on all middleware computers. The base services v Middleware – “Starting middleware on Windows” on page 94 v The deployment engine for the solution installer on the administrative workstation: – Check the Services control panel. The middleware If you are using the middleware installer to reinstall the middleware. This task must be done before reinstalling the middleware. Ensure that you uninstalled all software as described in Chapter 5. v “Starting middleware on Windows” on page 94 Ensure that the Tivoli Provisioning Manager installation directory and the GUID are removed as described in “Removing items remaining after uninstallation” on page 147. if it is still installed.Reinstalling Tivoli Provisioning Manager Before you reinstall software. start it. If a different DB2 administrators group value is supplied.2 Installation Guide . DB2 attempts to associate the owner of the default instance with this new group. users and groups are not removed. 150 IBM Tivoli Provisioning Manager Version 7. ensure that the product has been uninstalled correctly and that the services required during each installation stage are started. provide the same value used previously for the DB2 administrators group during the reinstallation. The middleware steps do not need to be performed. This attempt fails because the owner already belongs to the group specified during the initial installation. To specify a new DB2 administrators group. remove the existing instance owner and DB2 administrator group. Tivoli Provisioning Manager core components Ensure that the middleware is started before you resume installation. The middleware installation program creates a default instance for DB2 and adds the owner of the default instance to the DB2 administrator group specified. Ensure that the services are started: 2.” on page 139. 2000 DB2 If you reinstall the middleware.

In addition to the problems listed in this topic.com/support/search. Back up the deployment engine database of the administrative system before and after applying any updates to an existing deployment.cmd 2. Run the command to back up the deployment engine registry: c:\Program Files\IBM\Common\acsi\bin\de_backupdb. If you used the launchpad links to back up the deployment engine database automatically. These instructions are provided for manual backup and restore of the deployment engine database. Troubleshooting installation Review the following topics for problems that you might encounter during installation.ibm. Problems during middleware installation See the following information to diagnose and resolve middleware installation errors. To restore a backup of the deployment engine database: c:\Program Files\IBM\Common\acsi\bin\de_restoredb -bfile "<backup_directory>\DEBackupBeforeMBS" where <backup_directory> is the directory that you selected to back up the deployment engine database. Set up the environment using the following command: c:\Program Files\IBM\Common\acsi\setenv. If you encounter errors during Tivoli Monitoring agent installation. Procedure 1. © Copyright IBM Corp. where <backup_file_name> is the file containing the deployment engine backup that you made. restore the deployment engine database from the location that you specified in the installer panels. Backing up and restoring the deployment engine database These instructions are for backing up and restoring the deployment engine database to the state it was before installing middleware on middleware servers or process managers on the administrative workstation.Appendix A. 2003. Before you begin 1.2 information center.2. v The Troubleshooting Guide in the IBM Tivoli Monitoring Version 6. see the following resources: v Troubleshooting information in the Tivoli Monitoring agent for Tivoli Provisioning Manager User Guide.wss?rs=1015&tc=SS2GNX&dc=DB560 &rankprofile=8&q1=mwi&sort=desc&dtm. Having backups allows you to recover from partial installation attempts where process manager components were partially installed.cmd <backup file name> Use a meaningful name for <backup_file_name> to indicate that it contains the state of the registry after your installation of Provisioning Manager. check the technotes for middleware installation problems available at http://www-01. 2010 151 . Stop the deployment engine: v Control Panel > Administrative Tools > Services > IBM ADE Service 2.

the following links in the launchpad do not work: v 1. Errors with the middleware installer Solutions to installation errors regarding insufficient disk space and the middleware installer. you must start it manually before running the middleware installer. and the launchpad.exe file is run from there. check that the deployment engine is working: 1) Run the command setenv. Symptoms The following error is generated in the installation step for the deployment engine: CTGIN9077E: Deployment Engine did not start successfully. Please try to manually start the Deployment Engine and restart the installer. Run the launchpad64. If the solution installer was previously installed by another product. The default installation location is: v C:\Program Files\IBM\Common\acsi b. Run the command: v net start "IBM ADE Service" If the deployment engine is started successfully. and launchpad. The solution installer is included with some IBM products.CTGIN9077E error during middleware installation If the middleware installer is canceled during middleware installation.2 Installation Guide . an error is displayed. 2. If the middleware installer reports insufficient disk space. Check the disk space requirements in the installation guide. Resolving the problem 1.3 Back up WebSphere Configuration v 2.exe (Windows 32-bit) file from your local hard disk drive directory to back up the WebSphere Application Server and base services. Exit the middleware installation program.exe (Windows 32-bit). 2) Run the following command from the solution installer directory: 152 IBM Tivoli Provisioning Manager Version 7. restart the middleware installation program and resume middleware deployment.4 Back up base service Home Directory v Start backup Resolving the problem 1. If an installation exists. 2.exe (Windows 64-bit) or launchpad. a. make more disk space available on the computer. Restart the deployment engine. and then restart the middleware installer program.ini files to the launchpad folder and the install/tools folder to your local hard disk directory.exe (Windows 64-bit) or launchpad. Resolving the problem 1. Symptoms 1. 2. you might encounter errors. Check for an existing installation of solution installer. Links in the launchpad do not work Symptoms If the installation binary files are copied in a Windows mapped network drive. If the middleware installer detects an existing installation and the service is not started. Copy the launchpad64.

listIU.cmd

If the deployment engine installed correctly, you receive output similar to the following:
IU UUID: DDCE934782398B3E81431666515AC8B5 Name: DE Extensions Interfaces CLI IU Version: 1.3.1 IU UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment Engine IU Version: 1.3.1 IU RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA Name: Install IU Version: 1.3.1

c. If solution installer is already installed, start the service: v Check the Services control panel. If the IBM ADE service is not running, start it.

DB2 installation fails when configured names do not match
2000 DB2

The node name and host name must match when installing DB2.

Symptoms
DB2 installation stops halfway when the configured node name is different from the configured host name.

Causes
The DB2 installation uses the uname -n command to obtain the node name of the computer. Typically, the node name is the same as the host name that is returned with the hostname command. Tivoli Provisioning Manager installation requires that the host name and the node name of the computer are identical.

Resolving the problem
Check the value of the host name and node name. You must change the node name if it does not match the host name. 1. Run the command hostname to obtain the host name. 2. Run the command uname -n to obtain the node name. 3. If the node name is different than the host name: a. Log on as root. b. Change the node name to match the host name. For example, to change the node name to myserver, run the following command:
uname -S myserver

Database error during installation
2000 DB2

You might receive an error stating that the DB2INSTANCE variable is missing, but it can be disregarded.

Symptoms
v You receive this error during installation:
SQL1390C The environment variable DB2INSTANCE is not defined or is invalid.

v The following message appears in the DB2 installation log called db2inst.log:
1: WARNING:A minor error occurred while installing "DB2 Enterprise Server Edition" on this computer. Some features may not function correctly.
Appendix A. Troubleshooting

153

Causes
This is a known issue. This error occurs because Tivoli Provisioning Manager is initially deployed without any DB2 instances. The DB2INSTANCE variable is defined later in the installation process.

Resolving the problem
This error message can be disregarded.

Cannot connect to Tivoli Directory Server
Tivoli Directory Server must be installed and running before you install Tivoli Provisioning Manager.

Symptoms
During the Tivoli Provisioning Manager installation, the system might indicate that it cannot connect to the IBM Tivoli Directory Server.

Causes
This error occurs because Tivoli Directory Server was not started before running the installer. Tivoli Directory Server must be started before you install Tivoli Provisioning Manager so that the installer can connect to it.

Resolving the problem
1. Ensure that Tivoli Directory Server is installed: a. If the installation destination directory was created, check the installation log file for the directory server: v C:\IBM\LDAP\ldapinst.log After the installation of the directory server is complete, an LDAP database must be created within DB2. For more information, refer to the Tivoli Provisioning Manager 7.2 Installation Guide. The ldapcfg.stat file shows the syntax that was used at the time of the database creation:
C:\IBM\ldap\bin\ldapcfg -n -a db2inst1 -w password -d LDAP -l C: -c -f C:\IBM\ldap\tmp\ldapcfg.dat

The ldapcfg.stat file is located in the following directory: v C:\IBM\ldap\tmp\ldapcfg.stat 2. Verify the status of the directory server, using the ibmdirctl tool, located in the following directory: v C:\IBM\ldap\bin Type the following command to check the directory server status:
ibmdirctl -D cn=root -w <password> status

3. If the directory server is not started, start it by using the following command:
start: ibmdirctl -D cn=root -w <password> start

Cannot connect to the database server during installation
The database server must be installed and running before you install Tivoli Provisioning Manager.

Symptoms
During the installation, the system indicates that it cannot connect to the database.

Causes

154

IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

This error occurred because the database was not started before running the installer. The database server must be started before you install Tivoli Provisioning Manager, so that the installer can connect to it.

Resolving the problem
Ensure that the database server is installed. Verify the status of the database server. If it is not started, start it. Use the following commands to start the DB2 server: v DB2 - <instance_name> If the database server was successfully started, you can see the following output:
db2start 12-21-2004 14:44:01 0 0 SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful

You must also verify whether the required port is available:
netstat -an |grep 50000

Tivoli Directory Server installation step fails during Tivoli Provisioning Manager installation
The Tivoli Directory Server instance creation will fail if it cannot write files to the home directory of the LDAP instance user or if the home directory does not exist.

Symptoms
During the Tivoli Management Agent installation, the Tivoli Directory Server installation step fails. The log file /tmp/itds60/idsicrt.log has an error message similar to the following:
GLPICR058E: The specified directory, /home/ldapinst, is not a valid directory, does not exist, or is not writable.

Causes
The LDAP instance user was manually created but the associated home directory does not exist. This causes the Tivoli Directory Server instance creation to fail because it cannot write files to the home directory of the LDAP instance user.

Resolving the problem
If the LDAP instance user is manually created, check to ensure that the home directory exists and that it is writable by the LDAP instance user.

The Microsoft Active Directory configuration fails
The Microsoft Active Directory SSL certificate must be generated and configured manually.

Symptoms
The Microsoft Active Directory configuration fails.

Causes
The Microsoft Active Directory SSL certificate is missing. If you run the Tivoli Provisioning Manager installer without the SSL certificate, the Microsoft Active Directory configuration will fail.

Resolving the problem

Appendix A. Troubleshooting

155

This is a manual configuration step that you must complete before you install Tivoli Provisioning Manager. 1. Generate the SSL certificate on the Microsoft Active Directory server. 2. Install the SSL certificate on the client. 3. Import the schema.ldif and ldap.ldif files into the Microsoft Active Directory server. Instructions for this step are found in theTivoli Provisioning Manager Installation Guide Version 7.2.

Error configuring database during middleware installation
An error occurs during the database configuration because of missing XML files when installing the middleware.

Symptoms
File corruption leads to missing XML files.

Causes
Older versions of Winzip causes an incompatibility problem.

Resolving the problem
Use a newer version of Winzip.

The Tivoli Provisioning Manager installation fails with incorrect certificate value
If your Tivoli Provisioning Manager installation fails with error code 1005, it is because your Microsoft Active Directory certificate value is incorrect.

Symptoms
The Tivoli Provisioning Manager installation exits with error 1005.

Causes
The Microsoft Active Directory certificate is missing but the user enters a value for the certificate location during the install. If the file does not exist, then the error occurs. There is no other information available with this error code.

Resolving the problem
Ensure that you have a correct certificate value.

WAS_HOME error when using login window manager
If you use a login window manager like Common Desktop Environment (CDE), it might bypass the user profile file for tioadmin. When the profile file is bypassed, the system cannot create a complete login environment, causing an error.

Symptoms
When starting Tivoli Provisioning Manager using a login window manager such as the Common Desktop Environment (CDE), a message informs you that WAS_HOME is not set.

Causes
156
IBM Tivoli Provisioning Manager Version 7.2 Installation Guide

The login window manager might have bypassed the required user profile file. The tioadmin user uses the bash shell as the login shell, which is supported for a line-mode login (for example, using telnet). If you use a login window manager, it might bypass the .profile file for tioadmin. When the profile file is bypassed, the system cannot create a complete login environment.

Resolving the problem
1. Create the .bashrc file in the tioadmin home directory, and insert the following line: $HOME/.profile 2. Save the file. 3. Edit the .dtprofile in the tioadmin home directory and remove the comment from the line: DTSOURCEPROFILE=true. This file is created automatically when user tioadmin logs in to the login window manager for the first time. 4. Login as tioadmin again to the login window manager.

Encountering error CTGIN9042E
During middleware installation using the middleware installer, you might encounter error CTGIN9042E which occurs during the installation step for WebSphere Application Server Network Deployment 6.1. If you encounter error CTGIN9042E during the normal use of the middleware installation program, it might be related to stale entries in the CEI registry. In order to troubleshoot this error, complete the following steps:

Procedure
1. First check de_processreq.log for failures related to VerifyLogsInInstallLogs Action. The de_processreq.log file can be found at:
<workspace>###BOT_TEXT###lt;machine name>\deploymentPlan\MachinePlan_<computer shortname> /00009_WAS_ND_6.1/install/01_BASE/[INSTALL_<processing.req.id>]/logs/de_processreq.log

So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the computer name is mycomputer, and the processing.req.id is created as a date_timestamp, then the de_processreq.log would be located in:
C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\ 00009_WAS_ND_6.1\install###BOT_TEXT###1_BASE\[INSTALL_1130_06.54]\logs

2. Next, check for any stale WebSphere Application Server Network Deployment entries: a. Extract the native image of WebSphere Application Server Network Deployment: v WAS-ND_WindowsIA32_Custom_v61023 b. Open the console window. c. Navigate to the bin folder of extracted image. For example:
\WAS\installRegistryUtils\bin

d. List registry entries: v installRegistryUtils.bat -listProducts e. Check for WebSphere Application Server Network Deployment related entries. If any WebSphere Application Server Network Deployment entries are listed, even if you have successfully uninstalled WebSphere Application Server Network Deployment, you will need to clean the registry entry. 3. Clean the registry entries: a. Clean WebSphere Application Server Network Deployment entries from the registry:
installRegistryUtils -cleanProduct -offeringID ND -installLocation <WAS installation location path>

Appendix A. Troubleshooting

157

Uninstallation of WebSphere Application Server Network Deployment fails after unsuccessful binding to the LDAP directory You encounter an error during the installation of WebSphere Application Server Network Deployment using the middleware installation program and then when you attempt to undeploy the middleware deployment plan related to unsuccessful binding to the LDAP directory. Problems during base services installation See the following information to diagnose and resolve base services installation errors.Boolean:java.Integer. the installation might fail at the WebSphere Application Server Network Deployment configuration step. you encounter the option to configure WebSphere Application Server Network Deployment security with an existing remote LDAP directory. c. and then save the file. a. run the middleware installation program again and restart the plan.properties file by removing any WebSphere Application Server Network Deployment entries.lang. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: operator. you need to provide the credentials to access the remote LDAP server. administrator.ctgCellManager01 IBM WebSphere Application Server V6. WebSphere Application Server Network Deployment cannot issue the stopManager command in order to stop the ctgDmgr01 profile. The file is located in the installation directory of the operating system: v C:\WINNT directory or C:\windows directory 4. For example. When using the middleware installation program. To configure WebSphere Application Server Network Deployment successfully.lang. WebSphere Application Server Network Deployment is now successfully installed in the default location.2 Installation Guide . To resolve the problem: 1. In the Services control panel. Restart the system.1 . Restart the middleware installation program to undeploy the plan.1 . IBM WebSphere Application Server V6. After cleaning the registry. If you provide the middleware installation program with the wrong credentials. The set of credentials include: v v v v Host name or IP address Port in which LDAP server is running LDAP base entry User. 158 IBM Tivoli Provisioning Manager Version 7. Once the initial installation has failed. the uninstallation (undeployment) of the deployment plan might fail due to incorrect credentials given at the time of installation. Edit the vpd. change the startup type of the following WebSphere Application Server Network Deployment entries from Automatic to Manual. C:\Program Files\IBM\WebSphere\AppServer. Group.nodeagent b. The following error is generated: SECJ0305I: The role-based authorization check failed for admin-authz operation Server:stop:java.b. The remote LDAP directory can be hosted by either Microsoft Active Directory or by IBM Tivoli Directory Server. and Organization suffix v Bind DN and password Also the WebSphere Application Server Network Deployment Administrator user ID and password must have existing entries in the remote LDAP Directory.

if the distinguished names for your User base entry is Test Users and LDAP Test. The default location is: v C:\IBM\SMP 5. Ensure that you are logged on as the same user ID used to start the installation program and delete the MAXIMO_HOME directory manually.” 3. This situation causes the deployment engine registry to not accurately reflect the state of the system. you must perform additional manual uninstallation tasks. 2. Troubleshooting 159 . Resolve the cause of the problem. 2. 6. For more information. Change to the MAXIMO_HOME/bin directory. 4.ou="LDAP Test". see “Recovering the deployment engine.DC=ibm.DC=mydomain. restart the directory server. skip this step.DC=tod. add quotation marks around the distinguished names. Causes Spaces in the LDAP distinguished names are not supported. If you are using IBM Tivoli Directory Server.DC=com Recovering the deployment engine Depending on your specific scenario. which includes both Provisioning Manager and non-Provisioning Manager components. Recovery from a partial installation in which no base services programs were registered in the deployment engine registry To determine if base services programs have been deployed and registered in the deployment engine registry: 1. Run the following command: Appendix A. Symptoms Manually entering the User base entry and Group base entry LDAP information during the base services installation causes the LDAP validation to fail. For example. Before using these uninstallation instructions or scripts. Recovering the deployment engine can result in loss of registration information about installed software components. For default installation on Windows. Drop the Provisioning Manager database and create it again. Attempt the installation again. Base services installation does not accept LDAP names with spaces Add quotation marks (" ") around the LDAP distinguished names if you need to include spaces. Resolving the problem Add quotation marks (" ") around the LDAP distinguished names. you might restore a previous backup of the deployment engine registry or remove the deployment engine completely. Custom Default XML Default Recover the database. Complete the following steps to uninstall Provisioning Manager: 1.Recovering from a failed installation without the uninstallation program If the installation program has failed at the point where it did not produce the product uninstallation program. Recover the deployment engine database. ou="Test Users". read the following information to determine the effect of these operations to your environment.

Recovery from a partial or full installation in which one or more base services programs were registered in the deployment engine registry If the showinstalled results indicate that there are one or more base services programs installed. For more information. Uninstall the base services. Log on to the database server as the database instance owner and recover the database. Recovering from problems during base services installation If the base services installation fails. Enter the following command on a single line: %WAS_HOME%\bin\restoreConfig.bat -username <wasadmin_user> -password <wasadmin_password> %WAS_HOME%\profiles\ctgDmgr01\bin\stopManager. the installation failed before any programs were installed and registered in the deployment engine registry.bat -username <wasadmin_user> -password <wasadmin_password> b. If no base services programs have been installed. if the default user is ctginst1: 2000 DB2 a.zip -logfile c:\backups\restore_appSrv01. you must restore the backup of the deployment engine database using the following command: v c:\Program Files\IBM\Common\acsi\bin\de_restoredb. Restore the ctgDmgr01 configuration. a. The current deployment engine registry must be preserved and does not prohibit installation of the base services programs during the subsequent installation. Symptoms The base services installation fails with the error message Failed to install IBM Tivoli Provisioning Manager base services.solutionInstaller -action showinstalled -type all The CTGIN0059I message indicates which base services programs are installed. and then start the base services installation again. There might be errors regarding a database update problem. Enter the following command on a single line. Restore the database. Stop WebSphere Application Server Network Deployment: %WAS_HOME%\profiles\ctgAppSrv01\bin\stopServer.log -user <wasadmin_user> -password <wasadmin_password> -profileName ctgAppSrv01 3. do not uninstall the deployment engine or restore a previous backup.zip -logfile c:\backups\restore_dmgr. Drop the database: db2 drop db <db_name> c. For example. <backup file name> is the file containing the deployment engine backup. Resolving the problem 1. You must not uninstall the deployment engine before reinstalling Provisioning Manager.cmd -bfile <backup file loc> where. see “Uninstalling the base services and web components” on page 146. Log on to the computer where WebSphere Application Server is installed and recover the backup data. restore the WebSphere Application Server configuration and the database to their previous states. set db2instance=ctginst1 b.bat c:\backups\WASBackup_beforeBSI_DMProfile. Restore the deployment engine database backup after completing the steps to remove the Process Manager configuration.bat MXServer -username <wasadmin_user> -password <wasadmin_password> %WAS_HOME%\profiles\ctgAppSrv01\bin\stopNode. Enter the following command on a single line: db2 restore database <db_name> user ctginst1 using <instance_owner_password> from <DB2_BACKUP_DIR> with 3 buffers buffer 1000 without rolling forward without prompting 160 IBM Tivoli Provisioning Manager Version 7.log -user <wasadmin_user> -password <wasadmin_password> -profileName ctgDmgr01 c. %WAS_HOME%\bin\restoreConfig. 2.bat c:\backups\WASBackup_beforeBSI_AppSrvProfile.2 Installation Guide . Restore the ctgAppSrv01 configuration. If no programs are installed.

Restart the base services installation. To log on to the web interface. the following error is displayed: CTGIN2252I: Can not access to base services web application.bat 6. where host_name is the fully-qualified domain name of the provisioning server and the default port number is 9443. Causes The port settings might not be properly set up.ear fails The port settings need to be properly set up on both the provisioning server and on the administrative workstation where the base services are installed. Resolving the problem If you did not encounter other installation errors for the web components and you can successfully log on to the web interface. Troubleshooting 161 . For more information. Symptoms At the end of base services installation. see “Installing the base services” on page 98. Causes At the end of the base services installation. restore the deployment engine database to the state before installing the base services. see “Backing up and restoring the deployment engine database” on page 151. Resolving the problem Verify the port settings on both the provisioning server and on the Windows computer where the base services are installed. Log on to the computer where WebSphere Application Server is installed and start WebSphere Application Server: %WAS_HOME%\profiles\ctgDmgr01\bin\startManager.bat %WAS_HOME%\profiles\ctgAppSrv01\bin\startNode. the installer tries to connect to the web application. ensure that the port speed settings for the network interface card and for the port switch match.ear. The connection might fail if the web application is not yet running on the application server. Symptoms The base services WebSphere Application Server trace logs indicate that there was a file transfer error for MAXIMO. open a browser window and type https://host_name:port/maximo.4. On both computers. you can continue with installation. you can continue with installation. Deployment of MAXIMO. If you are using the base services for other products that are installed in the same environment as Provisioning Manager. 5. Setting the port speed to bidirectional communication on both the network interface card and on the port switch is recommended. Error CTGIN2252I during base services installation If you did not encounter other installation errors for the web components and you can successfully log on to the web interface. For more information. Appendix A.

8. click Manage Admin Mode. 11. or the CTGInstallTrace00. but some serious errors occurred during the install.sh twice. Command: Database Upgrade command validation failed. Symptoms One of the following error messages can occur either in an installation panel. Resolving the problem To commit the pending database changes: 1. 12.bat|. this error might be displayed during middleware installation.log. If you get any error messages.2 Installation Guide . click Apply Configuration Changes. Symptoms The following message is displayed at the end of the base services installation: The installation is finished. Click Go To > System Configuration > Platform Configuration > Database Configuration. 9. From the Select Action menu. 4. click Manage Admin Mode. then wait for about five minutes for the change to take effect. 10.log file: CTGIN2489E: The Maximo database contains backup tables that must be manually removed before this update can be applied. 5. The error message tells you to check the file CTGInstallTrace00. Click Turn Admin Mode ON. The log file contains an error similar to the following example: 162 IBM Tivoli Provisioning Manager Version 7. Stop the MXServer. 7. 6. 2. Click OK. and dropbackup. Causes This message indicates that there were changes made in your environment that need to be committed in the database before new products can be added into the database. From the Select Action menu. The base services installation fails Make sure the deployment engine is running when installing the base services. In the directory <base_services_install_dir>\maximo\tools\maximo. run these scripts again. From the Select Action menu.Errors CTGIN2381E or CTGIN2489E during Maximo database upgrade By failing to commit environmental changes when installing a second ISM family product on a system that already hosts another ISM family product. run configdb. The following message can occur in the CCMDB_install. Continue with the installation.bat|. Please refer to the readme information that came with this update or the upgrade section of the guide for Planning and installing the product for more information. then monitor to completion. Click Go To > System Configuration > Platform Configuration > Database Configuration. Click Turn Admin Mode OFF.log file: CTGIN2381E: Maximo Database upgrade command failed.sh once. 3. CTGIN2381E: Maximo updatedb utility would fail.

4.3. Change to the MAXIMO_HOME\bin directory and run the following command: solutionInstaller -action showinstalled -type all 8. Run the listIU command again to verify the deployment engine installation. Causes There are several possible causes for this error. Run the listIU command again. 7. reinstall the deployment engine. Note: If you created images after completing stages of the Tivoli Provisioning Manager installation. the lock files might have been present in an image of the computer that you recovered before running the web components installer. si_inst.log and DE logs for additional information. If the IBM ADE service is not running. the installation fails.bat CONTINUE STOPONERROR Appendix A.1 IU RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA Name: Install IU Version: 1. 3. Set the environment: setenv.1 6. f. If the deployment engine is still is not running properly. Continue the base services installation. restart the administrative workstation and copy MAXIMO_HOME\CCMDBTaskStore back to %TEMP% or /tmp. Resolving the problem Verify the following: 1. If the deployment engine is not running properly: Copy a. e. Check the Services control panel.** ERROR: Autonomic Deployment Engine installation/upgrade failure. d.cmd 5. run the following command: taskRunner. Return code: 3 Failure: DE in use or general failure See the CCMDB si_inst. Run the following command from the solution installer directory. start it.3. Troubleshooting 163 . If you continue with web components installation on the same computer. %TEMP%\CCMDBTaskStore b.bat c.lck files.3.cmd If the deployment engine engine installed correctly. Change to the following directory: v C:\Program Files\IBM\Common\acsi 2.1 IU UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment Engine IU Version: 1. Ensure that the deployment engine service is running. In MAXIMO_HOME\de directory. In the MAXIMO_HOME\scripts directory. listIU. you receive output similar to the following example: IU UUID: DDCE934782398B3E81431666515AC8B5 Name: DE Extensions Interfaces CLI IU Version: 1. Verify that the deployment engine is running. Clean up any existing .

or upgrading TPAE fixes/hotfixes you must check that the files are in sync. Maximo business objects are out of sync between the deployment engine and the WebSphere runtime Ensure that the Tivoli Provisioning Manager deployment engine runtime and the Maximo WebSphere Application Server runtime must be in sync. or additional packages to WebSphere Application Server runtime under the base services are added. you must manually align the runtimes.jar file. Resolving the problem When running the base services installation. Copy the businessobjects. If any changes are made from base services.2 Installation Guide . Note: : If this is an ISM integration use case. with multiple middleware installer workspaces contain fragments of the middleware configuration information. it could cause code binary level to be out of sync. If the file sizes are different. Log in to the provisioning server as tioadmin. if a user installs a Change and Configuration Management database (CCMDB) or Service Request Manager (SRM) on top of the existing Tivoli Provisioning Manager server. Go to the /WebSphere/AppServer/profiles/ctgAppSrv01/installedApps/ctgCell01/MAXIMO. it fails because it does not have the complete set of data. Causes The businessobjects. Resolving the problem After installation or upgrade. For example. When you run the base services installation.jar file and other xml files must be synchronized between WebSphere Application Server runtime and the Tivoli Provisioning Manager LWI runtime. you must do this check each time you install or update a new Tivoli Process Automation Engine (TPAE) or application.jar file from the MAXIMO.ear/ folder to the Tivoli Provisioning Manager LWI runtime folder: 164 IBM Tivoli Provisioning Manager Version 7.jar folder: v TIO_HOME\lwi\runtime\tpm\eclipse\plugins\tpm_pmp\maximoLibs 3. 4. and type all the middleware information.jar and other version-related xml files in its deployment engine runtime.jar file size and make sure that the version from both WebSphere Application Server and Tivoli Provisioning Manager LWI runtime are the same size.The base services installer fails to validate the installation Symptoms When you have more than one middleware node installed and you import the middleware configuration information. the base services installation fails. deselect the Import data from Middleware Installer workspace check box. Back up the businessobjects.ear/ and locate the businessobjects. 2. Symptoms The Tivoli Provisioning Manager server uses Maximo businessobjects. Causes Middleware installed on different computers. the user must check the businessobjects. while starting MXServer as part of provisioning server startup. 1.

jar file in either directory. Resolving the problem If you have Tivoli Provisioning Manager deployed with other base services products. Because of this. it can potentially break the production deployment engine. Causes The ISC is corrupted following the CCMDB installation. Symptoms After the Change and Configuration Management Database (CCMDB) installation. then the fix pack is only deployed on the application server. follow these steps: 1. Symptoms If you install a fix pack for a different base services product in a base services environment. If these objects are out of sync. Maximo business objects from the deployment engine gets out of sync with the ones in the application server The Maximo business objects that the deployment engine uses need to be in sync with the Maximo business objects deployed in the application server. Error CWLAA6003 occurs after CCMDB installation To display the portlet. Troubleshooting 165 . it can potentially break the production deployment engine. If these objects are out of sync. Causes The Maximo business objects that the deployment engine uses need to be in sync with the Maximo business objects deployed in the application server. Restart the provisioning server. To do this.jar file is extracted from the maximo. 2.ear businessobjects. Resolving the problem Appendix A.jar This will generate a file named businessobjects. Note: The businessobjects.jar. the portlet may not be started. the Maximo business objects that the deployment engine is using might be out of sync with the ones in the application server. Copy the businessobjects. Enter these commands in the command prompt: MAXIMO_HOME unzip maximo.ear file that is created after deploying any fix pack from the MAXIMO_HOME/deployment/default directory.cp businessobjects. the Manage Users and Manage Groups in the ISC (Integrated Solutions Console) display the following error: CWLAA6003: Could not display the portlet.jar $TIO_HOME/lwi/runtime/tpm/eclipse/plugins/tpm_pmp/maximoLibs/businessobjects. you must reinstall the ISC. you must re-create and copy the Maximo business objects used by the Web application to the deployment engine.jar 5. overwrite it.jar file into the following directories: v TIO_HOME/eclipse/plugins/pm_pmp/maximoLibs v TIO_HOME/lwi/runtime/tpm/eclipse/plugins/tpm_pmp/maximoLibs If there is already a businessobjects. causing errors.

bat -conntype NONE -f deployConsole. Remove the %TEMP%###BOT_TEXT###lt;user_name> directory.1. delete it manually. WaitForStart main Caught an Exception in loop #2 while pinging the NetworkServerControl server. select the jservice. Run the following command: v WAS_HOME\profiles\profileName\bin\wsadmin. By default. 5. If the si_inst command does not remove the deployment engine database. and workspace directory content of <WAS Server1 or dmgr>\profiles\ profileName\logs and <WAS Server1 or dmgr>\profiles\profileName\wstemp.reinstall the ISC: Back up the current environment.bat -conntype NONE -f deployConsole. 2. 166 IBM Tivoli Provisioning Manager Version 7.0.S:Could not connect to Derby Network Server on host 127. Restart Server1 or dmgr process. Stop the Server1 stand alone profile or dmgr (deployment manager process) Clean up the old logs. port 4130. First attempt to remove the deployment engine database using the si_inst command: If the installation was done using the Administrator user C:\Program Files\IBM\Common\acsi\bin\si_inst -r If the installation was done using a user other than Administrator C:\Documents and Setting###BOT_TEXT###lt;userid>\acsi_<user_name>\si_inst -r where user_name is the name of the user who installed the deployment engine. click End Process. Before you begin You might see the following messages in the DE_Install.log file. you must clean it up using the steps in this procedure. where user_name is the name of the user that installed the deployment engine. the log file is located in: v C:\Program Files\IBM\Common\acsi\logs\Administrator where user_name is the name of the user who installed the deployment engine.py remove ISC ear was removed successfully. 6. Run the following command: v <WAS Server1 or dmgr>\profiles\profileName\bin\wsadmin. Administrator. Remove the %TEMP%\acu_de. which indicate a problem with the deployment engine: WaitForStart main Exception is: DRDA_NoIO. Check ISC reinstalled successfully. Removing the deployment engine database on Windows If the installation was done using the Administrator user: 1.0. for example. and then click OK. 4. if it exists. 2. 3. 4.log file.py install To 1.2 Installation Guide . 3. In Windows Task Manager. Recovering from deployment engine failure during installation If the deployment engine fails during installation. Remove the C:\Program Files\IBM\Common directory.exe process.

4. swgc302 OS type: IBM AIX. If the installation was done using a user other than Administrator: 1. Remove the %TEMP% \acsiTemp_<user_name> directory. Before you begin 1. Appendix A. Remove the C:\Documents and Settings###BOT_TEXT###lt;user_name>\My Documents\. Relaunch the base services installer. Causes The message indicates that the user is configured so that the account does not lock during the install process. While stopping these services is satisfactory. Set the environment variable ENABLE_RXA_TRACE=yes 2. delete the acsisrv entry found in the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services key of the Windows registry. Check the CTG installation trace log for the RXA trace information. Password policy is set to never expire during base services installation Symptoms The following message appears in the base services installation log files: The password has been successfully set to NEVER EXPIRE for user db_user on host_name machine where db_user is the database runtime user. Ensure the connection between the administrative workstation and provisioning server is working. Open the Windows Services panel. Enabling RXA tracing RXA tracing is enabled to allow better troubleshooting in case there are connection problems between the administrative workstation and the provisioning server. Reboot the computer.bat <hostname of TPM server> <username> <password> If the connection is successful. On the administrative workstation. Run the following command: v TestRXA. Procedure 1. If they exist. Remove the %TEMP% \acsitempLogs_<user_name> directory. if you want to remove them. The default value is maximo. where user_name is the name of the user that installed the deployment engine. Troubleshooting 167 . The base services installer did not change the password policy you configured. 3. ensure the IBM ADE Service or ACSI Service services are stopped. 6. 2. you are returned a message like: ** Successful RXA access to swgc302 using user/password: root/<password>. go to: v C:\IBM\SMP\scripts 2.5.acsi_<user_name> directory. Check that RXA tracing is enabled in the command window where you launched the installer with the following command: v echo %ENABLE_RXA_TRACE% 3.

3. Check the log files to determine the problem: TEMP/tclog_wrapper/DBbackupafterMBS-stdout. Resolve the cause and then try again. recover by uninstalling the failed component and restarting the installer.log 2. and then perform recovery.log TEMP/tclog_wrapper/extractDB2Client_err. Check the log files to determine the problem: TEMP/tclog_wrapper/extractDB2Client.” on page 139.log TEMP/tclog_wrapper/cygwin_ssh_config. TEMP represents: v %TEMP% v For information about uninstalling components.log TEMP/tclog_wrapper/cygwin_ssh_config. Resolve the cause of the problem. Step by step recovery for core components installation (custom installation) Custom Default XML Complete the following steps to recover from problems that you might encounter when installing Tivoli Provisioning Manager for the first time using a custom installation. database failure.log TEMP/tclog_wrapper/db2install-stderr. for example. 2000 DB2 If a problem occurs during the Tivoli Provisioning Manager installation. “Uninstalling Tivoli Provisioning Manager. 2000 DB2 If a problem occurs during the DB2 client installation (if using remote database) 1.log TEMP/tclog_wrapper/db2install-stdout.2 Installation Guide . If a problem occurs during the Cygwin installation and configuration 1.log TEMP/tclog_wrapper/instCygwin.log TEMP/tclog_wrapper/DBbackupafterMBS-stderr. v If the installation of a component fails during a post-installation step. Uninstall the DB2 client and then try again. 168 IBM Tivoli Provisioning Manager Version 7.log 2. quit and restart the installer and select only the components that remain to be installed. v Where log files are mentioned. see Chapter 5. Check the log files to determine the problem: C:\cygwin\var\log\ TEMP/tclog_wrapper/downloadCygwinSetup.Problems during core components installation See the following information to diagnose and resolve Tivoli Provisioning Manager core components installation errors.log TEMP/tclog_wrapper/downloadCygwinRep. Note the following general recovery information: v If the installation of a component fails and you need to modify or view the previous fields in a panel.err 2. Resolve the cause and then try again. DB2 backup 1.

Troubleshooting 169 . Restore the database and then try again. Check the log files to determine the problem: TEMP/tclog_wrapper/create_wasprofile. If you plan to use different values in the WebSphere Application Server Network Deployment Configuration panel after the failure: 1.log TEMP/tclog_wrapper/WASbackupAppSrv01-afterMBS-stdout. Check the log files to determine the problem: TEMP/tclog_wrapper/nonUI_install. Resolve the cause of the problem.log 2. WebSphere Application Server backup 1. Check the log files to determine the problem: TEMP/tclog_wrapper/call_was_config. Check the log files to determine the problem: TEMP/tclog_wrapper/amtrace. 3. engines installation 1. Resolve the cause of the problem. If a problem occurs during the Agent Manager installation.log TEMP/tclog_wrapper/WASbackupctgDmgr01-afterMBS-stderr. Resolve the cause and then try again.log TEMP/tclog 2.log TEMP/tclog_wrapper/WASbackupAppSrv01-afterMBS-stderr. 3. Check the log files to determine the problem: TEMP/tclog_wrapper/WASbackupctgDmgr01-afterMBS-stdout. WebSphere Application Server configuration. Resolve the cause of the problem. 3. Resolve the cause and then try again. Clean up the agent manager profile and then try again. JVM setup If you plan to use the same values in the WebSphere Application Server Network Deployment Configuration panel after the failure: 1. actual installation If only the agent manager installation fails and the agent manager profile is removed successfully: 1. If a problem occurs during theTivoli Provisioning Manager installation. remove the JVM parameter for the old values that were used in the WebSphere Application Server Network Deployment Configuration panel. Check the log files to determine the problem: TEMP/tclog_wrapper/call_was_config.If a problem occurs during the Tivoli Provisioning Manager installation. profile creation 1.log TEMP/tclog_wrapper/amtrace.log 2. Try again. 4. If a problem occurs during the Agent Manager installation.log TEMP/tclog_wrapper/call_was_config_fips.log TEMP/tclog_wrapper/call_was_config_fips. In the WebSphere Application Server console.log 2. If a problem occurs during the Tivoli Provisioning Manager installation.err TCA_HOME/logs TCA_HOME/toolkit/logs Appendix A.log WAS_HOME/AppServer/profiles/casprofile/logs/AboutThisProfile.log TEMP/tclog_wrapper/nonUI_install_err.txt 2.

3.err 2. Verify that the WebSphere Application Server profile for the agent manager is running and start it.err TEMP/tclog_wrapper/CDSinstall-stdout.err TEMP/tclog_wrapper/soap-sslconfig. actual installation 1. Check the log files to determine the problem: TEMP/tclog_wrapper/getAMPass4CDS. If a problem occurs during the Dynamic Content Delivery installation. Resolve the cause and then try again.log TEMP/tclog_wrapper/preparePingAM. Check the log files to determine the problem: TEMP/tclog_wrapper/preparePingAM. 170 IBM Tivoli Provisioning Manager Version 7. Attempt the installation again. if necessary: v Log in as the tioadmin user and run the following command: %WAS_HOME%\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. Resolve the cause of the problem. Verify that the WebSphere Application Server profile for the agent manager is running and start it. Resolve the cause of the problem. 3.log 2.bat server1 where the default value for <AM profile> is casprofile. registration with the common agent 1.log TEMP/tclog_wrapper/config_ssl.err TCA_HOME/logs TCA_HOME/toolkit/logs 2. 4. If a problem occurs during the Dynamic Content Delivery installation. Check the log files to determine the problem: TEMP/tclog_wrapper/config_ssl.log TEMP/tclog_wrapper/CDSinstall-stderr. Check the log files to determine the problem: TEMP/tclog_wrapper/amtrace. 3. SSL configuration 1.2 Installation Guide . 4. 3. Attempt the installation again.err TEMP/tclog_wrapper/call_pingam.bat server1 where the default value for <AM profile> is casprofile. Resolve the cause of the problem.2. If the failure occurs during removal of agent manager profile: 1.log DCD_HOME/log 2. If a problem occurs during the Dynamic Content Delivery installation. if necessary: v Log in as the tioadmin user and run the following command: %WAS_HOME%\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. Resolve the cause of the problem. Uninstall the dynamic content delivery. Clean up the agent manager profile and then try again.log TEMP/tclog_wrapper/amtrace.log TEMP/tclog_wrapper/soap-sslconfig.log TEMP/tclog_wrapper/getAMPass4CDS.log TEMP/tclog_wrapper/call_pingam_err.

Verify that the WebSphere Application Server profile for the agent manager is running and start it. configuration 1. Verify that the WebSphere Application Server profile for the agent manager is running and start it. if necessary: v Log in as the tioadmin user and run the following command: %WAS_HOME%\profiles###BOT_TEXT###lt;AM profile>\bin\startServer.bat server1 where the default value for <AM profile> is casprofile. Resolve the cause of the problem. If a problem occurs during the Device manager service installation. Appendix A. Troubleshooting 171 . 4. Attempt the installation again.bat server1 where the default value for <AM profile> is casprofile. 5. If the device manager service database was not installed successfully.bat server1 where the default value for <AM profile> is casprofile.log TEMP/tclog_wrapper/dms_getpass_err. Attempt the installation again. resolve the cause of the problem.err 2. Verify that the WebSphere Application Server profile for the agent manager is running and start it. Check the log files to determine the problem: TEMP/tclog_wrapper/dmsinstalltrace. If a problem occurs during the Device manager service installation.log 2. Attempt the installation again. Resolve the cause of the problem. actual installation 1. 4. Check the log files to determine the problem: TEMP/tclog_wrapper/dmsconfigtrace. uninstall the device manager service. If the device manager service database was installed successfully.log TEMP/tclog_wrapper/dmsconfigtrace.log 2. 3. if necessary: v Log in as the tioadmin user and run the following command: %WAS_HOME%\profiles###BOT_TEXT###lt;AM profile>\bin\startServer.err DMS_HOME/logs/dms_config_trace. if necessary: v Log in as the tioadmin user and run the following command: %WAS_HOME%\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. SSL configuration 1. If a problem occurs during the Device manager service installation. Resolve the cause of the problem. if necessary: v Log in as the tioadmin user and run the following command: %WAS_HOME%\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. Verify that the WebSphere Application Server profile for the agent manager is running and start it.bat server1 where the default value for <AM profile> is casprofile. 6. 5.log TEMP/tclog_wrapper/dmsinstalltrace. 3. 3.4.log DMS_HOME/logs/dms_config. Check the log files to determine the problem: TEMP/tclog_wrapper/dms_getpass.

Resolve the cause of the problem.err TEMP/tclog_wrapper/call_importXML4OSD.err TEMP/tclog_wrapper/changePermission_was.log TEMP/tclog_wrapper/call_db2_restart. Check the log files to determine the problem: TEMP/tclog_wrapper/call_db2_restart. Resolve the cause and then try again. Attempt the installation again.[bat|sh] server1 where the default value for <AM profile> is casprofile.log TEMP/tclog_wrapper/changePermission_cas.err TEMP/tclog_wrapper/start_nodedmgr_tioadmin. If a problem occurs while backing up the database 1. If a problem occurs while configuring WebSphere Application Server to run as tioadmin 1.log TEMP/tclog_wrapper/wasND_runastioadmin.err TEMP/tclog_wrapper/start_CASServer_tioadmin. 3.log 2.log TEMP/tclog_wrapper/changePermission_was.err TEMP/tclog_wrapper/stop_CASServer_root.err 2.err TEMP/tclog_wrapper/changePermission_cas.err TEMP/tclog_wrapper/stop_nodedmgr_root. 3. Resolve the cause of the problem. see “Error when configuring WebSphere Application Server to run as tioadmin” on page 179. Restart DB2 manually.log TEMP/tclog_wrapper/start_nodedmgr_tioadmin.err TEMP/tclog_wrapper/wasND_runastioadmin. Attempt the installation again.4.2 Installation Guide .log TEMP/tclog_wrapper/stop_CASServer_root. Check the log files to determine the problem: TEMP/tclog_wrapper/cas_runastioadmin.err 2.log TEMP/tclog_wrapper/tpmfosd. Check the log files to determine the problem: TEMP/tclog_wrapper/tpmfosd. Log in as the tioadmin user and run the following command: WAS_HOME/profiles/<AM profile>/bin/startServer. 172 IBM Tivoli Provisioning Manager Version 7.log TEMP/tclog_wrapper/call_importXML4OSD. 2000 DB2 If a problem occurs while restarting DB2 (if using a local database) 1. Verify that the WebSphere Application Server profile for the agent manager is running and start it. Uninstall Tivoli Provisioning Manager for OS Deployment.err 2. Check the log files to determine the problem: TEMP/tclog_wrapper/DBbackupafterTPMCore-stdout.log TEMP/tclog_wrapper/DBbackupafterTPMCore-stderr. 5. For information how to resolve the problem.log TEMP/tclog_wrapper/stop_nodedmgr_root.log TEMP/tclog_wrapper/start_CASServer_tioadmin. 4.err TEMP/tclog_wrapper/stop_MXServer_root. if necessary. If a problem occurs during the Tivoli Provisioning Manager for OS Deployment installation 1.log TEMP/tclog_wrapper/stop_MXServer_root.log TEMP/tclog_wrapper/cas_runastioadmin.

v If the installation of a component fails during a post-installation step. Note the following general recovery information: v If the installation of a component fails and you need to modify or view the previous fields in a panel.5\install###BOT_TEXT###1_BASE\ INSTALL_<timestamp>\logs MWI_workspace\hostname\deploymentPlan\MachinePlan_wind###BOT_TEXT###0004_DB2_9\logs WebSphere Application Server log files: MWI_workspace\hostname\deploymentplan\MachinePlan_hostname###BOT_TEXT###0009_WAS_ND_6. Step by step recovery for core components installation (default installation) Default Complete the following steps to recover from problems that you might encounter when installing Tivoli Provisioning Manager for the first time using a default installation.log C:\ibm\tivoli\mwi\workspace\mwi. v Where log files are mentioned.log %TEMP%\tclog_wrapper\downloadCygwinRep.1\install###BOT_TEXT###1_BASE\ INSTALL_<timestamp>\logs MWI_workspace\hostname\deploymentPlan\MachinePlan_hostname###BOT_TEXT###0009_WAS_ND_6.log TEMP/tclog_wrapper/WASbackupAppSrv01-afterTPMCore-stderr.log %TEMP%\tclog_wrapper\cygwin_ssh_config.err 2.log %TEMP%\tclog_wrapper\instCygwin.log 2. Check the log files to determine the problem: TEMP/tclog_wrapper/WASbackupctgDmgr01-afterTPMCore-stdout.err Deployment engine log files: MWI_workspace\hostname\deploymentPlan\logs\INSTALL_<timestamp> 2000 DB2 DB2 log files: MWI_workspace\hostname\deploymentplan\MachinePlan_hostname###BOT_TEXT###0004_DB2_9.log TEMP/tclog_wrapper/WASbackupAppSrv01-afterTPMCore-stdout. and then perform recovery. Resolve the cause and then try again. recover by uninstalling the failed component and restarting the installer. Check the log files to determine the problem. If a problem occurs during the middleware installation 1. database failure. TEMP represents: – %TEMP% v For information about uninstalling components.log TEMP/tclog_wrapper/WASbackupctgDmgr01-afterTPMCore-stderr. see Chapter 5. If a problem occurs during the Cygwin installation and configuration 1.If a problem occurs during the WebSphere Application Server backup 1. Check the log files to determine the problem: C:\cygwin\var\log\ %TEMP%\tclog_wrapper\downloadCygwinSetup. Troubleshooting 173 . C:\ibm\tivoli\mwi\workspace\mwi.” on page 139. quit and restart the installer and select only the components that remain to be installed.log %TEMP%\tclog_wrapper\cygwin_ssh_config.1\logs C:\Program Files\IBM\WebSphere\AppServer\logs\install\ Tivoli Directory Server log files: Appendix A. for example. “Uninstalling Tivoli Provisioning Manager. Resolve the cause and then try again.

backup 1. 3. Restore the deployment engine database and try again. If a problem occurs during the base services installation.log %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterMBS-stderr. Uninstall the base services. see Backing up and restoring the deployment engine database. actual installation 1.log %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterMBS-stderr. Check the log files to determine the problem: %TEMP%\tclog_wrapper\MBSBackupB4TPM-stdout. Remove the failed component and then try again.log 2.log 2. Check the log files to determine the problem: %TEMP%\tclog_wrapper\call_was_config.2 Installation Guide .log 2.log %TEMP%\tclog_wrapper\call_was_config_fips.log 2. If a problem occurs during the Tivoli Provisioning Manager installation. JVM setup If you plan to use the same values in the WebSphere Application Server Network Deployment Configuration panel after the failure: 1.log 174 IBM Tivoli Provisioning Manager Version 7.zip file in the MAXIMO_HOME\debug directory 2. Resolve the cause and then try again.log %TEMP%\tclog_wrapper\DBbackupafterMBS-stderr. If a problem occurs during the Tivoli Provisioning Manager installation. If you plan to use different values in the WebSphere Application Server Network Deployment Configuration panel after the failure: 1. Check the log files to determine the problem: %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterMBS-stdout. Check the log files to determine the problem: %TEMP%\tclog_wrapper\DBbackupafterMBS-stdout.log %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterMBS-stdout. Check the log files to determine the problem: %TEMP%\tclog_wrapper\call_was_config. DB2 backup 1. Resolve the cause of the problem. If a problem occurs during the Tivoli Provisioning Manager installation. Resolve the cause and then try again. If a problem occurs during the base services installation. Resolve the cause and then try again. WebSphere Application Server configuration. Resolve the cause and then try again.1\install###BOT_TEXT###2_BASE\ INSTALL_<timestamp>\logs\ MWI_workspace\hostname\deploymentPlan\MachinePlan_hostname###BOT_TEXT###0006_ITDS_DB2_CCMDB\logs MWI_workspace\hostname\deploymentPlan\MachinePlan_hostname###BOT_TEXT###0008_ITDS_Configuration\logs 2.log %TEMP%\tclog_wrapper\call_was_config_fips. Resolve the cause of the problem. For more information. 4. 3.log %TEMP%\tclog_wrapper\MBSBackupB4TPM-stderr. WebSphere Application Server backup 1. Check the log files to determine the problem: v Run the following command: MAXIMO_HOME\scripts\LogZipper.bat v Find the [current date]_[timestamp].MWI_workspace\hostname\deploymentplan\MachinePlan_hostname###BOT_TEXT###0007_ITDS_6.

3. Clean up the agent manager profile and then try again. registration with the common agent 1.log %TEMP%\tclog_wrapper\call_pingam_err. Resolve the cause of the problem.log %TEMP%\tclog_wrapper\nonUI_install_err. Check the log files to determine the problem: %TEMP%\tclog_wrapper\amtrace. 3. 3. Clean up the agent manager profile and then try again. Check the log files to determine the problem: %TEMP%\tclog_wrapper\preparePingAM. If a problem occurs during the Dynamic Content Delivery installation. 3.log %TEMP%\tclog 2.log %TEMP%\tclog_wrapper\amtrace. 4. Try again. If a problem occurs during the Agent Manager installation.log WAS_HOME\AppServer\profiles\casprofile\logs\AboutThisProfile 2. If the failure occurs during removal of agent manager profile: 1. 4. if necessary. In the WebSphere Application Server console.log 2.err 2.bat server1 where the default value for <AM profile> is casprofile. remove the JVM parameter for the old values that were used in the WebSphere Application Server Network Deployment Configuration panel. Resolve the cause of the problem. Attempt the installation again. 3. Troubleshooting 175 . Resolve the cause and then try again.log %TEMP%\tclog_wrapper\preparePingAM. engines installation 1. Check the log files to determine the problem: %TEMP%\tclog_wrapper\nonUI_install. Check the log files to determine the problem: %TEMP%\tclog_wrapper\create_wasprofile. Verify that the WebSphere Application Server profile for the agent manager is running and start it.2.err %TEMP%\tclog_wrapper\call_pingam. profile creation 1. If a problem occurs during the Agent Manager installation. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. actual installation If only the agent manager installation fails and the agent manager profile is removed successfully: 1. If a problem occurs during the Tivoli Provisioning Manager installation. Check the log files to determine the problem: TCA_HOME\logs TCA_HOME\toolkit\logs 2. Resolve the cause of the problem. Restore the database and then try again. Resolve the cause of the problem. Resolve the cause of the problem. Appendix A.

log DCD_HOME\log 2. SSL configuration 1. Resolve the cause of the problem. Verify that the WebSphere Application Server profile for the agent manager is running and start it. If a problem occurs during the Device manager service installation. 4. 176 IBM Tivoli Provisioning Manager Version 7. configuration 1.err 2. Resolve the cause of the problem.log 2.err 2.log DMS_HOME\logs\dms_config. Verify that the WebSphere Application Server profile for the agent manager is running and start it. If a problem occurs during the Dynamic Content Delivery installation. 3. 4. 5. 4. if necessary.log %TEMP%\tclog_wrapper\config_ssl.bat server1 where the default value for <AM profile> is casprofile.err DMS_HOME\logs\dms_config_trace.err %TEMP%\tclog_wrapper\soap-sslconfig. if necessary. Attempt the installation again. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. if necessary. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. Check the log files to determine the problem: %TEMP%\tclog_wrapper\getAMPass4CDS. Verify that the WebSphere Application Server profile for the agent manager is running and start it.bat server1 where the default value for <AM profile> is casprofile.err %TEMP%\tclog_wrapper\CDSinstall-stdout. Resolve the cause of the problem. Check the log files to determine the problem: %TEMP%\tclog_wrapper\config_ssl.log %TEMP%\tclog_wrapper\dmsinstalltrace. Check the log files to determine the problem: %TEMP%\tclog_wrapper\dmsinstalltrace.bat server1 where the default value for <AM profile> is casprofile.2 Installation Guide .log %TEMP%\tclog_wrapper\soap-sslconfig.If a problem occurs during the Dynamic Content Delivery installation. If a problem occurs during the Device manager service installation. 3.log %TEMP%\tclog_wrapper\CDSinstall-stderr. Attempt the installation again. Check the log files to determine the problem: %TEMP%\tclog_wrapper\dmsconfigtrace. Attempt the installation again. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer.log %TEMP%\tclog_wrapper\getAMPass4CDS. 3. Resolve the cause of the problem. actual installation 1. actual installation 1. Uninstall the dynamic content delivery.log %TEMP%\tclog_wrapper\dmsconfigtrace.

Restart DB2 manually.err 2. Attempt the installation again. 3. Verify that the WebSphere Application Server profile for the agent manager is running and start it.err %TEMP%\tclog_wrapper\call_importXML4OSD.3. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer.log %TEMP%\tclog_wrapper\call_db2_restart. 2000 DB2 If a problem occurs while restarting DB2 (if using a local database) 1. Resolve the cause of the problem. If the device manager service database was not installed successfully. If a problem occurs during the Tivoli Provisioning Manager for OS Deployment installation 1. 4. Check the log files to determine the problem: %TEMP%\tclog_wrapper\DBbackupafterTPMCore-stdout. 4. 4. 5. 3. if necessary. SSL configuration 1. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer.log 2. Attempt the installation again. 5.log %TEMP%\tclog_wrapper\dms_getpass_err. Verify that the WebSphere Application Server profile for the agent manager is running and start it.log %TEMP%\tclog_wrapper\DBbackupafterTPMCore-stderr. Uninstall Tivoli Provisioning Manager for OS Deployment.bat server1 where the default value for <AM profile> is casprofile.bat server1 where the default value for <AM profile> is casprofile. resolve the cause of the problem. Resolve the cause of the problem. if necessary. Check the log files to determine the problem: %TEMP%\tclog_wrapper\tpmfosd. 3. Verify that the WebSphere Application Server profile for the agent manager is running and start it. Check the log files to determine the problem: %TEMP%\tclog_wrapper\dms_getpass. Troubleshooting 177 . Attempt the installation again. 6.log Appendix A. Check the log files to determine the problem: %TEMP%\tclog_wrapper\call_db2_restart. Log in as the tioadmin user and run the following command: WAS_HOME\profiles###BOT_TEXT###lt;AM profile>\bin\startServer. if necessary.err 2. If a problem occurs during the Device manager service installation. If the device manager service database was installed successfully.log %TEMP%\tclog_wrapper\call_importXML4OSD. If a problem occurs while backing up the database 1.bat server1 where the default value for <AM profile> is casprofile. uninstall the device manager service.log %TEMP%\tclog_wrapper\tpmfosd. Resolve the cause of the problem.

Log on to the database server as the database instance owner and restore the database: 2000 DB2 a. Open the file TIO_HOME/config/dcm. and then start the core components installation again.ctginst1 c.bat c:\backups\WASBackup_afterMBS_ctgDmgr01. b.log -user <wasadmin_user> -password <wasadmin_password> -profileName ctgAppSrv01 3. Resolving the problem 1. 2. Restore base services backup and DE database backup from after the base services installation.bat MXServer -username <wasadmin_user> -password <wasadmin_password> WAS_HOME\profiles\ctgAppSrv01\bin\stopNode. Recovering from problems during core components installation If the core components installation fails. 5. Log on to the computer where WebSphere Application Server is installed and restore the backup data: a. see “Uninstalling Tivoli Provisioning Manager core components” on page 139. 4.zip -logfile c:\backups\restore_appSrv01.xml to verify the database name and user name.bat -username <wasadmin_user> -password <wasadmin_password> b. If a problem occurs during the WebSphere Application Server backup 1. Log on as Administrator and open a DB2 command window. Stop WebSphere Application Server Network Deployment: WAS_HOME\profiles\ctgAppSrv01\bin\stopServer. Check the log files to determine the problem: %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterTPMCore-stdout. 178 IBM Tivoli Provisioning Manager Version 7.log MAXIMO_HOME\solutions\logs\TPM_PMP 2. Uninstall the core components.bat -username <wasadmin_user> -password <wasadmin_password> WAS_HOME\profiles\ctgDmgr01\bin\stopManager. Resolve the cause and then try again. For example: su . Restore ctgAppSrv01 configuration.2. and the username element contains the user name. The default database owner is ctginst1. Restore the database. Resolve the cause of the problem. Restore WebSphere Application Server. Enter the command on a single line: WAS_HOME\bin\restoreConfig. For more information. 3. Restore ctgDmgr01 configuration.2 Installation Guide . The name element contains an alias for the database name. Enter the command on a single line: WAS_HOME\bin\restoreConfig.log %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterTPMCore-stderr. Symptoms Installation fails during the core components installation.log %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterTPMCore-stderr. restore the WebSphere Application Server and the database to their previous states. Resolve the cause and then try again.log %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterTPMCore-stdout. If a problem occurs during the Process solutions installer 1. Check the log files to determine the problem: %TEMP%\tclog_wrapper\psi_tpm.zip -logfile c:\backups\restore_dmgr.bat c:\backups\WASBackup_afterMBS_AppSrv01. 6.log 2. Change the user to your DB2 instance owner.log -user <wasadmin_user> -password <wasadmin_password> -profileName ctgDmgr01 c. Try again.

Run the following command to check for other running applications db2 list applications e.bat MXServer 5. complete some recovery steps to bring the computer back to a consistent state.bat WAS_HOME\profiles\ctgAppSrv01\bin\startNode.log log file contains one of the following error messages: v v v v Failed Failed Failed Failed to to to to configure the Agent Manager profile to run as tioadmin configure the WebSphere Application Server Network Deployment to run as tioadmin change the ownership of the Agent Manager profile change the ownership of the WebSphere Application Server Network Deployment Appendix A. The /tmp/tclog_wrapper/tcinstall. Symptoms Tivoli Provisioning Manager core components installation failed. If the command lists other applications.d. Start DB2: v If the server does not have a virtual IP address: db2start v If the server has a virtual IP address: db2gcf -u -p 0 -i ctginst1 j. Log on to the computer where WebSphere Application Server is installed and start WebSphere Application Server: WAS_HOME\profiles\ctgDmgr01\bin\startManager. Stop all DB2 interprocess communications by running ipclean. For more information. Stop DB2: v If the server does not have a virtual IP address: db2stop v If the server has a virtual IP address: db2gcf -d -p 0 -i ctginst1 h. End the DB2 session: db2 terminate g. If the server has a remote database. see “Installing Tivoli Provisioning Manager core components” on page 119. attach to the local host alias: db2 attach to LHOST0 user user_name using password l. i. run the following command to disconnect them db2 force applications all f. k. Restore the database backup: db2 restore db db_name user user_name using password from location where v db_name is the name of the database v user_name is the user name of the user restoring the database v password is the password of the user v location is the full path location of the backup 4. Error when configuring WebSphere Application Server to run as tioadmin To recover from installation errors when installing the Tivoli Provisioning Manager core components. Restart the core components installation.bat WAS_HOME\profiles\ctgAppSrv01\bin\startServer. Troubleshooting 179 . Delete and uncatalog the existing database: db2 drop db db_name where db_name is the name of the database.

log log file for a detailed error message. Symptoms During installation of the core components. 2. and fix the problem. Check the wasND_runastioadmin. 2. Validation failed The installer checks for the following requirements: v A profile with the same name does not already exist. but the profile is not successfully created. To remove casprofile. 1. run the following command: WAS_HOME/bin/manageprofiles. If the validation fails.[bat|sh] -listProfiles 180 IBM Tivoli Provisioning Manager Version 7. The instructions use the default profile name caseprofile. one of the following errors occurs for the WebSphere Application Server profile for the agent manager. Click Back to the Summary panel. Causes When the core components installer installs the agent manager. The validation is successful.err) To resolve the error: 1. then click Next to continue installation. Check the file cas_runastioadmin. If the profile directory already exists. the automatic removal might not work and the profile must be removed manually before you try to install the agent manager again. If a profile with the same name already exists. The installer checks the computer to verify that it can create the profile. v The cell name is the same as WebSphere Application Server Network Deployment cell name. it must be empty. 2. and then fix the problem. Click Back to the Summary panel. v If the log contains the error Failed to configure the Agent Manager profile to run as tioadmin: 1.[bat|sh] -delete -profileName casprofile 2. v If the log contains the error Failed to configure the WebSphere Application Server Network Deployment to run as tioadmin: 1. it automatically removes the WebSphere Application Server profile for the agent manager if the agent manager installation fails. Resolving the problem Perform the following steps to address the error. Errors creating the agent manager profile If the agent manager installation fails. then click Next to continue installation. Run the following command: WAS_HOME/bin/manageprofiles. check for an existing casprofile directory.log for a detailed error message. v If a directory for the profile already exists. specify a different name in the installer or remove the existing profile. and the validation fails.2 Installation Guide . you need to perform some recovery steps to bring the computer back to a consistent state.log (or validation_casprofile. The profile name is casprofile by default. In some situations.Resolving the problem If you encounter an installation error when configuring WebSphere Application Server to run under the user tioadmin. check the log files: v %TMP%\tclog_wrapper\validation_casprofile. you might need to remove the WebSphere Application Server profile manually before reinstalling the agent manager.

The provisioning server installer will detect that Tivoli Provisioning Manager is already installed and will install only the agent manager. Symptoms The installation of the agent manager fails during the Tivoli Provisioning Manager installation. If casprofile is listed. remove the directory WAS_HOME/profiles/casprofile. Check the following log files to identify the reason why the profile cannot be created. Fix the error described in the log. Validation passed but the profile cannot be created 1. Install Tivoli Provisioning Manager again. Possible causes might include: v The port required for the agent manager installation might be busy. Agent Manager installation fails Multiple causes of agent manager installation failure.log 2. v The agent manager has already been installed on your system. refer to the Tivoli Provisioning Manager Installation Guide. you must uninstall the agent manager first. Stop the agent manager server if it is running: v As a Windows service: Appendix A.If casprofile is not listed. Solution 2 If the agent manager was previously installed on the provisioning server. specify a different profile name or remove the existing profile as described in step 1. If the validation is successful. Causes Consult the agent manager logs to identify the cause of this problem. v Do not clean the agent manager tables from the registry or drop the registry database until all products that use the registry are uninstalled. and their solutions. perform the steps described in the previous section for a failed validation. Click Next. and then run the Tivoli Provisioning Manager installation again. Consult the agent manager log files and make all the necessary changes following the instructions in the logs. If the validation fails. Click Back in the core components installer to go to the panel before the installation preview. the installer tries to create the profile again. To uninstall the agent manager. The installer verifies the requirements to create the profile again. v %TMP%\tclog_wrapper\create_wasprofile. 3. 2. 4. Troubleshooting 181 . Important: To prevent the loss of data: v Do not uninstall the agent manager until all products that use it have been uninstalled. The agent manager log files are located in the AM_HOME\logs directory. For more details on the agent manager reinstallation. follow these steps: 1. follow these steps: 1. Resolving the problem Solution 1 If no agent manager installation has been performed on the provisioning server before the Tivoli Provisioning Manager installation.

If the agent manager application server is not named AgentManager. Optionally. you might have to perform this step on the remote database server instead of on the agent manager server. determine whether other Web applications are using that application server. By default. drop the database using the database administration tools for your type of database. In a command line window.2 Installation Guide . run the following command on the remote database server to uninstall the agent manager from that system: java -jar "Agent_Manager_install_dir/_uninstDS/uninstall. use the Windows Services window or the Services folder in the Microsoft Management Console to stop the service with the following name: IBM WebSphere Application Server V6. v If the registry database is used only by the agent manager and is not shared with another program. optionally delete the agent manager installation directory. By default.jar" -silent 7.To stop the agent manager server if the installation program created a Windows service. this is the following directory: v C:\Program Files\IBM\AgentManager Tip: You might have to restart the system before you can delete the agent manager installation directory. b. change to the AM_HOME/db/db2 directory. Run the following command: . If you will not be reinstalling the agent manager on this system. 8. 182 IBM Tivoli Provisioning Manager Version 7.exe 4. Run the following command: WAS_HOME\profiles\casprofile\bin\stopServer server1 When the agent manager server is stopped. the following message is generated: ADMU4000I: Server server1 stop completed. remove the agent manager-specific tables from the database by following the procedure for your database type. you can optionally delete the application server. If you do not need the uninstallation logs on the remote database server. remove agent manager objects from the registry database. or run the following command from a command prompt: AM_HOME\_uninst\uninstall. If you do not need the uninstallation logs. this is the following directory: v C:\Program Files\IBM\AgentManager Tip: You might have to restart the system before you can delete the agent manager installation directory. 6. If the registry is in a remote database.db2cmd /c /i /w "RemoveCASTables.1 . optionally delete the agent manager installation directory.Tivoli Agent Manager v On Windows but not as a service: To stop the agent manager server if it is not a Windows service: a. You can do this step on the agent manager server. even if the registry is in a remote database: – 2000 DB2 a.bat database_password" Replace database_password with the DB2 database password. v If the database is shared with other programs. If the registry is in a remote database. 3. 2. b. If no other applications are using that application server. remove the definition of TivoliAgentRecovery from your DNS servers. Open a command prompt window. Start the uninstallation program for your operating system: v Use either the Add/Remove Programs window to uninstall the agent manager. 5.

Resolving the problem Manually uninstall the common agent. Causes If WebSphere Application Server was uninstalled but the WebSphere Application Server installation directory was not removed. Reinstalling Tivoli Provisioning Manager: Install Tivoli Provisioning Manager again. The installer will detect that Tivoli Provisioning Manager is already installed. and will install only agent manager. the Tivoli Provisioning Manager installer might identify WebSphere Application Server as installed. perform the following steps: v Ensure that the WebSphere Application Server installation directory is removed. Installation fails after WebSphere Application Server is uninstalled If the WebSphere Application Server installation directory remains after it was uninstalled. You can now continue with the installation. Troubleshooting 183 . Resolving the problem If WebSphere Application Server was uninstalled on the computer. The common agent and the agent manager cannot be installed The common agent cannot be installed on the provisioning server if the agent manager is also installed on it.The agent manager is now uninstalled. Symptoms Appendix A. Click Next so that the installer can check again for installed components. where the agent manager is also installed. Causes Installing the common agent on the provisioning server. Symptoms The common agent and the agent manager cannot be installed. the Found column displays No if WebSphere Application Server is fully uninstalled. On the Validation Summary panel. and then fail during theTivoli Provisioning Manager installation. is not supported. Symptoms The installation of Tivoli Provisioning Manager installation fails if WebSphere Application Server was uninstalled. Core components or web components installation hangs during Cygwin installation Problems with your Cygwin installation might cause the installer to hang during prerequisite verification. the Tivoli Provisioning Manager installation might fail. The default location is: – C:\Program Files\IBM\WebSphere\AppServer v Click Back in the installer until you reach the Configure the target servers panel.

see the Troubleshooting Guide. Verify if Cygwin is installed. the IBM® Data Server Runtime Client cannot be used to bind the database utilities and DB2 CLI bind files.1. For more information. You must bind again after the installation. 2. The default instance name is ctginst1.5 and a DB2 server version 9. 184 IBM Tivoli Provisioning Manager Version 7. To get access to perform the BIND commands.5 and 9. 2. run the following commands: db2 db2 db2 db2 db2 terminate CONNECT TO TPMFOSD BIND path\db2schema. install it manually. To BIND. see “Installing Cygwin manually” on page 208. Resolving the problem 1.lst BLOCKING ALL GRANT PUBLIC ACTION ADD BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD where path is the full path name of the directory where the bind files are located.lst and db2cli.lst contain lists of required bind files used by DB2 database products. the following message appears: The Installation Wizard is checking the system prerequisites. Symptoms The following message appears in the installation panel: WARNING: DB2 bind warning occurred during Tivoli Provisioning Manager for OS Deployment installation. After waiting a few minutes. DB2 BIND warning during Tivoli Provisioning Manager for OS Deployment installation You need to perform the BIND commands if your DB2 client and server are 9. Close the installer. For more information. such as INSTHOME\sqllib\bnd where INSTHOME represents the home directory of the DB2 instance. Causes If you have a DB2 client version 9.While the installer verifies prerequisites during Tivoli Provisioning Manager core components or web components installation. db2ubind. Packages that are already bound will return an SQL0719N error. 1. 3.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE BIND path\@db2ubind. the installer seems to hang and the Next button remains disabled.2 Installation Guide . uninstall and then reinstall it manually. This is expected. run the following command: set DB2INSTANCE=DB_INSTANCE where DB_INSTANCE is the DB2 instance that was used to install Tivoli Provisioning Manager. Resolving the problem Perform the BIND commands from an IBM Data Server Client (or other DB2 database product) that is running on the same operating system and the same DB2 version and fix pack level as the Data Server Runtime Client. Causes There might be a problem with your Cygwin installation. If Cygwin is not installed. If Cygwin is installed.1 respectively.

Causes WebSphere Application Server was not started before the silent installation started. Resolving the problem To check the current configuration of short name capability. Appendix A. Symptoms The silent installation program for Tivoli Provisioning Manager exits before the installation is completed. run the following command to enable it: fsutil behavior set disable8dot3 0 Silent installation exits before installation is completed The silent installation of Tivoli Provisioning Manager exits prematurely if WebSphere Application Server is not running. Tivoli Provisioning Manager installation fails with invalid directory name Tivoli Provisioning Manager installation fails if its installation directory name is longer than eight characters and the Windows short name capability is disabled. For example. Symptoms Tivoli Provisioning Manager fails with an error message that is like the following: ’D:\Program’ is not recognized as an internal or external command. For more information. By default. run the following command: fsutil behavior query disable8dot3 The command returns one of the following messages: disable8dot3 = 0 Short name capability is enabled. This capability must be enabled if you want to install Tivoli Provisioning Manager in a directory other than the default directory. and if the directory name contains spaces. Windows supports the ability to create short names for directories whose names contain more than eight characters. These abbreviated names contain the first six characters of the original name and then a two-character extension. D:\Program Files can be abbreviated by the system as D:\Progra~1.3. Troubleshooting 185 . Verify that the Tivoli Provisioning Manager for OS Deployment is running. operable program or batch file. If short name capability is disabled. and the folder name with the space does not exist. see “Starting and stopping Tivoli Provisioning Manager components” on page 213. v The selected path contains a space. Causes This error occurs when all of the following conditions are true: v You selected a different installation directory from the default directory. disable8dot3 = 1 Short name capability is disabled. v Short name capability is disabled.

The error occurs if a recognized font cannot be resolved at startup time. 186 IBM Tivoli Provisioning Manager Version 7. Ensure that WebSphere Application Server is started. the installation fails with the following error: An error has occurred. Resolving the problem Increase the amount of free space on the partition. Symptoms The silent installation of core components for Tivoli Provisioning Manager exits before the installation is completed. Change Sub directories and font servers to 100dpi 75dpi misc hp sun ibm dec. If the required free space and available free space are different by a margin of 1000 MB.bin -options <response file path and name> -silent -W WzdSeq_PreInstallCheck. The tcinstall. 1.2 Installation Guide . navigate to Settings > Fonts. 2. [partition]. This can be fixed by changing the font settings in Reflection X. Resolving the problem You can fix the problem by changing font settings in Reflection X.active="false" -W DiskSpaceSeq.SWTError: Font not valid.Resolving the problem Before you run the silent installation: 1.Disk space check failed. Ensure that WebSphere Application Server security is not running.log file contains the following error message: [timestamp] ERROR DiskSpaceCheckWizardAction . See the log file /var/tmp/TopologyInstaller/workspace/.log The log file also contains an error that begins with org.swt.active="False" Command example: install/bin/setupSolarisSparc64. In the Reflection X Client Manager.active="False" Installation fails because of unrecognized font An installation error occurs if a recognized font cannot be resolved on startup. Causes This error has been observed when accessing a remote computer with Reflection X. but only [free space] MB is available Causes There is insufficient free space on the partition mentioned.[required space] MB of disk space is required.eclipse. Disk space check failure during silent installation of Tivoli Provisioning Manager The silent installation of Tivoli Provisioning Manager will exit prematurely if disk space check fails.metadata/. Symptoms During installation. run the following command to bypass the disk space checks: -W DiskSpaceSeq.

In the log file /opt/ibm/tivoli/ctgde/logs/ cds_upgrade. 2.jvm. and then run the installer again. Save your changes. 1. When you specify WebSphere Application Server settings on the Tivoli Provisioning Manager configuration tab of the installer. Reconnect to the computer that you are doing the installation on. Resolving the problem If you need to include a hyphen in the domain name suffix. Failed to launch the application. JavaHome is not resolved correctly in the jvm file /tmp/istemp7613004171417/ relative_to_upgrade.jarVerify java.versionVerification passed for / using the JVM file /tmp/istemp7613004171417/ relative_to_upgrade.jvm. Open the response file in a text editor and modify the domain name suffix so that it includes the hyphen character. Troubleshooting 187 .. Perform a silent installation. Cannot use hyphen in domain name suffix field You cannot use the hyphen (-) character in the Domain Name Suffix field when specifying WebSphere Application Server settings on the Tivoli Provisioning Manager configuration tab. run this command: Appendix A.binChecking the environment variables specified in the JVM files to find the JVM. Omit any hyphens from the domain name suffix. See the appendix "Performing a silent installation" in the Tivoli Provisioning Manager Installation Guide for instructions. /bin/java -cp /tmp/istemp7613004171417/Verify. Causes The location of Java cannot be found by the installer. Symptoms Installation of the dynamic content delivery service fails.. the following error is displayed: INSTALLER_PATH=/extra/ibm/tivoli/tio/CDS/scripts/. If you must use a hyphen. do a silent installation with a modified response file... when /bin is the directory listed in the PATH variable. perform a silent installation with a modified response file. Create your response file for a silent installation.2. you cannot use the hyphen (-) character in the Domain Name Suffix field. Symptoms The DNS suffix does not accept hyphens. Resolving the problem To fix the error. Causes This issue applies to a custom installation. See the appendix in the Tivoli Provisioning Manager Installation Guide instructions on creating a response file for silent installations. 3. This error occurs when Java is installed in the /bin/java directory. update the PATH variable so that the java command does not contain the /bin directory. 1. the dynamic content delivery installation will fail.vendor java. Verifying./setup. To confirm the location of Java. Installation of dynamic content delivery fails If the PATH variable does not properly indicate where Java is installed.txt.

ensure that /usr/bin is at the front of the PATH variable.2 Installation Guide . By default. insert the Installation DVD for your operating system. Core components installation fails during the dependency check The core components installation exits with an error message during the dependency check. 2. Restore the database backup taken after installing the base services. v Create a symbolic link for /bin/java under another directory and add that path to the front of the PATH variable. the backup is stored in: v 2000 DB2 <backup_dir>/DB2Backup_AfterMBS where <backup_dir> is the directory that you selected at the end of the base services installation. Symptoms The following error message appears: ERROR: Installation did not complete successfully. Resolving the problem If you receive this error. Uninstall Cygwin and install the correct version. Select Back followed by Next to try again. If the returned value is /bin/java. run the following command instead: type java 2. you can: v Move /bin to the end of the list of paths in the PATH variable. 188 IBM Tivoli Provisioning Manager Version 7. Causes There are multiple versions of Cygwin on the system registry which interfere with the dependency check. if you have a link in /usr/bin to the java command. If the first part of the path is /bin. or place /usr/bin before /bin in the list of paths. Normally the java command will resolve to /usr/bin/java. For more information. Causes This is caused by a limitation of the package installer program. see Installing Cygwin.log for more details. an error message Insert disk 1 appears. update the PATH variable so that /bin does not resolve the java command. 3. View the log at \tclog_wrapper\tcinstall. For example. run the following command to display the contents of the PATH variable: echo $PATH 3. Error message Insert disk 1 Symptoms During installation.which java If this command is unavailable on your system. Resolving the problem 1.

There is a db2. Symptoms When the database server is on a multiprocessor computer. Appendix A. the group for the file. Causes The Tivoli Provisioning Manager installation fails with DB2 when the terminal server is enabled. the remote connection to the database might hang. The DB2 command will not work.log file: DIA3208E Error encountered in TCP/IP protocol support. You can check the current permissions of a file in Cygwin by typing the following command: ls -l filename where filename is the name of the file. Remote connection to database hangs when database server is on a multiprocessor computer There might not be enough connection managers allocated from the database server. and other users. and those defaults can be changed with the umask command. Symptoms Files in a UNIX or Cygwin environment have specific permissions for the owner of the file. and then install again. The database server then logs the following error in the db2diag. Resolving the problem Stop the terminal server.exe application error. v If you are using a text editor that automatically creates file backups. or else adb2. it is recommended that you log on as the owner of the file. ensure that the updated file retains the original file permissions. restart the computer. Consider the following factors when editing text files: v Default user permissions. Each user has default permissions for files that they create. Causes There are various factors that can cause can change the permissions of a file. Socket was "920". Errno was "10061". If you edit a file in Cygwin using an editor such as vi. Troubleshooting 189 . Resolving the problem If you need to edit text files.Tivoli Provisioning Manager does not install when terminal server is enabled The terminal server needs to be stopped before installing Tivoli Provisioning Manager. Provide additional connection managers and take the number of processors into account when calculating the value of a given computer. Editing text files changes permissions Various factors can change permissions when editing text files. This means that file permissions for the user who created a file can be different than the permissions for another user.exe application error will occur and the installation will fail. your updated file might have different permissions than the original file. TCP/IP function "accept".

Resolving the problem 1.Causes Not enough connection managers are allocated from the database server. 3.2 Installation Guide . Problems during web components installation See the following information to diagnose and resolve Tivoli Provisioning Manager web components installation errors. Recovering from errors during a default installation If the default installation fails. refer to the DB2 product documentation. Resolve the cause of the problem. remove the installation and try the reinstall again. 190 IBM Tivoli Provisioning Manager Version 7. Symptoms If you receive an error during the monitoring agent manual installation. Symptoms Installation failed during a default installation with the error message Failed to install IBM Tivoli Provisioning Manager Web components. Uninstall the Tivoli Monitoring agent. 3. Resolving the problem 1. Update the database registry DB2TCPCONNMGRS to enable the database server to provide additional connection managers. Step by step recovery for IBM Tivoli Monitoring agent manual installation Complete the following steps to recover from problems that you might encounter when manually installing Tivoli Monitoring agent for the first time. check the log files to determine the problem.log 2. Run the following command to update the registry: db2set DB2TCPCONNMGRS=<value_calculated> 4.[bat|sh] server1 where the default value for <AM profile> is casprofile. if necessary. Attempt the installation again. 5. restart DB2 as follows: db2stop force db2start For more information. Check the log files: ITM_HOME\InstallITM/IBM Tivoli Monitoring for Provisioning<timestamp>. Log in as the tioadmin user and run the following command: WAS_HOME/profiles/<AM profile>/bin/startServer. Verify that the WebSphere Application Server profile for the agent manager is running and start it. use the following formula to determine the value of a given computer: Calculate the square root of the number of processors and then round up to a maximum value of 8. Considering that DB2TCPCONNMGRS takes values between 1 and 8. 4. 2. After changing the registry value.

Restore the database. c. Delete the C:\ibm\SMP folder. Server does not have a virtual IP Run the following commands: db2stop force db2start Server has a virtual IP If you are using a virtual IP address for the DB2 server. %DBTIMESTAMP% The timestamp of the most recent database backup file in the %BACKUPDIR% directory.bat" -timeout 1200 -username wasadmin -password %PASSWORD% 3.bat" %BACKUPDIR%\WASBackup_afterTPMCore_AppSrv01. Restore the base services folder and open a DOS command prompt. Restart the database. Run each command that starts with call on a single line. Troubleshooting 191 .00 In this example. call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin\stopNode. call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin\restoreConfig. 1. 4. use the following commands.CATN0000.bat" -username wasadmin -password %PASSWORD% call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin\stopManager. Close the DB2 window. the database instance is ctginst1. 2. In this example. b.20081009193807. Open a DB2 command window by running the following command at the command prompt: db2cmd b. 20081009193807 is the timestamp.zip to C:\ d.0. Exit the default installation installer and if it is still running. An example file name is: MAXDB71. Run each command that starts with call on a single line.log -username wasadmin -password %PASSWORD% -profileName ctgAppSrv01 Appendix A. db2 "restore database MAXDB71 user db2admin using %PASSWORD% from %BACKUPDIR% taken at %DBTIMESTAMP% with 3 buffers buffer 1000 without rolling forward without prompting" e. a.NODE0000.Resolving the problem The following steps describe how to remove a default installation when: v The default installation failed during web components installation. Enter the entire command on a single line. Open a DOS command window. v The installation completed successfully.CTGINST1. The following variables are used in the steps: %BACKUPDIR% The directory you specified in the Backup Files Location field of the default installation installer. Run the following command in the DB2 command window: set db2instance=ctginst1 c. %PASSWORD% The password you specified in the Generic Password field of the default installation installer. Restore WebSphere Application Server configurations. Extract the contents of %BACKUPDIR%\MBSBackupBeforeTPM. Restore the DB2 database: a. db2gcf -d -p 0 -i ctginst1 db2gcf -u -p 0 -i ctginst1 d. Stop WebSphere Application Server.zip -location C:\Progra~1\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\config\ -logfile %BACKUPDIR%\restore_ctgAppSrv01.

Delete the base services directory.cmd" -bfile "base_services_folder\DE_BACKUPS\AfterActions<timestamp>" where base_services_folder is the directory where the base services are installed. 192 IBM Tivoli Provisioning Manager Version 7. 3. Resolving the problem 1.ear\tpm_olh.zip. WAS_HOME\profiles\app_profile\bin\stopNode.cmd" -bfile "%BACKUPDIR%\DEBackupBeforeTPM" 6. Log on to the administrative workstation as the Administrator user.log -username wasadmin -password %PASSWORD% -profileName ctgDmgr01 5. Exit the installer if it is still running.2 Installation Guide .bat" 8. Restore the backup of the base services home directory to the removed base services folder. Run the default installation again. Restore the deployment engine registry. you must restore the provisioning server back to its previous state. Stop WebSphere Application Server Network Deployment. Start WebSphere Application Server. the default user ID is wasadmin. Remove the deployed information center. app_profile The WebSphere Application Server profile. The backup name is backup_folder/MBSBackupBeforeTPM. 2. was_adminID The WebSphere Application Server administrator ID.war" 7. b. where backup_folder is the location that you specified in the launchpad after installing the base services. Log on to the computer where WebSphere Application Server is installed as tioadmin and recover the backup data: a. Restore the base services folder: a.zip -location C:\Progra~1\IBM\WebSphere\AppServer\profiles\ctgDmgr01\config\ -logfile %BACKUPDIR%\restore_ctgDmgr01. Enter the following command on a single line: call "C:\Program Files\ibm\Common\acsi\bin\de_restoredb. Symptoms The web components installation has failed with the error message Failed to install IBM Tivoli Provisioning Manager Web components.call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin\restoreConfig.bat -username was_adminID -password was_admin_pwd WAS_HOME\profiles\dm_profile\bin\stopManager. Recovering from errors during web components installation If the web components installation fails.bat" call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin\startNode.bat" %BACKUPDIR%\WASBackup_afterTPMCore_ctgDmgr01.bat -username was_adminID -password was_admin_pwd where. If you are using read-only LDAP authentication. You must use the same user name and password that you used to run the default installation previously. The default values are: v C:\ibm\SMP c. Run each command that starts with call on a single line. call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin\startManager. Run the following command at the command prompt: call "C:\Program Files\ibm\Common\acsi\bin\de_restoredb. Run the following command at the command prompt: rmdir /S /Q "C:\Program Files\IBM\WebSphere\AppServer\systemApps\isclite. Restore the deployment engine registry. before installing the web components. 4.

Resolving the problem Appendix A. Start or restart the IBM Autonomic Computing Deployment Engine.log -user was_adminID -password was_admin_pwd -profileName app_profile 5. Enter the following command on a single line: WAS_HOME\bin\restoreConfig.zip -logfile backup_folder\restore_dmgr. db_admin_pwd The password of the database instance owner that was specified during Tivoli Provisioning Manager installation.bat WAS_HOME\profiles\app_profile\bin\startNode. Symptoms While installing the web components. the following error is generated: Error: The IBM Autonomic Computing Deployment Engine is not working. c. delete the file WAS_HOME/systemApps/isclite. Restore the database. To do this. dm_profile The deployment manager profile. Remove the deployed information center if it exists using the Administrator user. Restore the deployment manager profile configuration.war. you might encounter errors.was_admin_pwd The password for the WebSphere Application Server administrator. backup_files_location The directory specified in the Backup Files Location field in the Directories for Core Components panel. Enter the following command on a single line: db2 restore database MAXDB71 user db_adminID using db_admin_pwd from backup_files_location/DB2Backup_AfterTPMCore/ with 3 buffers buffer 1000 without rolling forward without prompting db_adminID The database instance owner that was used to install Tivoli Provisioning Manager. Enter the following command on a single line: WAS_HOME\bin\restoreConfig. Troubleshooting 193 . enter the password for the wasadmin user. If you are using read-only LDAP authentication.bat backup_folder\ WASBackup_afterTPMCore_ctgDmgr01. Log on to the database server as the database instance owner and recover the database. Run the following command: set DB2INSTANCE=<db2instance> The default value for <db2instance> is CTGINST1 db2cmd.bat Deployment engine error during web components installation While installing the web components. b.log -user was_adminID -password was_admin_pwd -profileName dm_profile where backup_folder is the backup directory where the backup data is stored.zip -logfile backup_folder\restore_appSrv01. 6. Restore the application server profile configuration. WAS_HOME\profiles\dm_profile\bin\startManager.bat backup_folder\ WASBackup_afterTPMCore_AppSrv01. b. 7.ear/tpm_olh. Log on to the computer where WebSphere Application Server is installed and start WebSphere Application Server. 2000 DB2 a.

CfgConfigWebSphere runJythonScript INFO: NOTE ^[runJythonScript] Result: 105 ^n^ Oct 8. the problem might be a mismatch between data that is stored in the properties for the installation and the values you are providing. indicating that the node agent was not started during web components installation.traceout for additional information. Rename the file to V7110_props. if the property mxe. In the \ibm\SMP\maximo\tools\maximo\ directory. In this example.db. Exception message (if any): "ADMN0022E: Access is denied for the getProcessType operation on Server MBean because of insufficient or empty credentials.bat command to check if the node agent is started. Verify this that the node agent is started.logSQLTimeLimit is already in the table. 6. please refer to the log file C:\IBM\SMP\wasclient\logs\wsadmin.ibm. then follow these steps: 1. 2008 3:09:18 PM com..dbc file so that it will not be imported again.common.> tag for that entry in the XML file. check the node agent logs for an error that indicates that the node agent is not started. rename the V7110_props. The following error is an example: Oct 8.Restart the deployment engine. 5. Import the base services properties located in <Maximo_HOME>\maximo\en\script\V7110_props. The following log files are associated with installation of web components. You can also run the startNode.xml file so that it only includes values that do not exist in your MAXPROP table.. Causes This error can be created from a variety of causes. Resolving the problem If the error is what was described above. For example.ccmdb. 2008 3:09:18 PM com. 2. 2.install. but you receive this error.was.ccmdb.ibm. run the updatedb command.tivoli.xml. Log files for process solution installer A chart of log file descriptions and locations. 3. Run the command: v net start "IBM ADE Service" Node agent not started during web components installation If you are able to log on to the WebSphere Application Server. Query the MAXPROP table to see what properties have been added to the database.2 Installation Guide . the start script cannot determine if the node agent is running because it cannot access the server due to incorrect credentials. Ensure that user and password are correct on the command line or in a properties file. If the node agent is running.dbc. the problem might be a mismatch between data that is stored in the properties for the installation and the values you are providing.. Modify the V7110_props. Check the following items: 1.CfgConfigWebSphere runJythonScript FINE: NOTE ^STDOUT: WASX7246E: Cannot establish "SOAP" connection to host "MYMACHINE" because of an authentication failure. remove the <Add_property. Log on to the WebSphere Application Server console for the node agent and see if the status is green. 4. 194 IBM Tivoli Provisioning Manager Version 7.config. Symptoms An error is displayed.. back up the V7110_props. In <Maximo_HOME>\maximo\en\script.was. After importing the properties successfully. If you are able to log on to the WebSphere Application Server.config.install. The process solution installer is called by the web components installer to deploy the web components.tivoli.common. but you receive this error.xml." WASX7213I: This scripting client is not connected to a server process.

These log files are typically vital to the debugging of package issues. both with the same pre-extension file name. Note: You might encounter messages like the following in the MAXIMO_DEPLOY_ERR. C:\IBM\SMP\lib\icl. The . Appendix A.out and .err files contain the contents of the Standard Error stream. C:\IBM\SMP\lib\ CTGInstallResources. C:\IBM\SMP\lib\ CTGInstallCommon. You might discover numerous (10-20) package log files generated for any particular package installed.out files contain the contents of the Standard Output stream as generated by the external command. Location MAXIMO_HOME\solutions\logs\ <PACKAGE_NAME>\ For instance.jar Although these messages are found in the error log file. Tivoli Provisioning Manager log The are logs kept by the PSI subsystem. and do not represent deployment errors. then the logs for the Change Package would be found in: C:\IBM\SMP\solutions\logs\ Change_PMP\. and the base services installation directory is C:\IBM\SMP. provided there was no error output (or if there were only error outputs). logs have two parts.err file found in the MAXIMO_HOME\solutions\logs directory for a process manager once it has been installed: v sys-package-mgr: processing new jar.jar v sys-package-mgr: processing new jar. These logs contain the trace output of the PSI subsystem. These messages can be safely ignored. It is common for one part to be blank. Log file information Log type Package log Description These files contain the StdOut and StdErr output of external commands launched by the package as it is processed by the deployment engine. if PSI encounters an error in the Change package. a . Troubleshooting 195 .log MAXIMO_HOME\logs\ CTGInstallTraceXX.log XX is a two-digit number such as 00. they are informational only.err file.jar v sys-package-mgr: processing new jar. The .Table 22. In general. MAXIMO_HOME\logs\ CTGInstallMessageXX.

if your WebSphere Application Server is installed in the C:\IBM\WebSphere\AppServer\. Location C:\Program Files\IBM\Common\acsi\ logs###BOT_TEXT###lt;USERNAME>\de_msg. WebSphere Application Server Logs These are logs kept of connections. and your server name is server1. your logs would be in this location: C:\IBM\WebSphere\AppServer\ profiles\AppSrv01\logs\ AboutThisProfile. PSI uses the IBM technology as the means to install and track installed packages. if you installed under the user name tioadmin.log WAS_HOME\profiles###BOT_TEXT###lt;PROFILE>\logs\ <SERVER_NAME>\stopServer. your profile name is AppSrv01. and other failures experienced by the WebSphere Application Server in its day-to-day running. It is strongly recommended that these logs be removed after a successful install. success. These are useful in tracking the progress.log v /usr/ibm/common/acsi/tioadmin/ de_msg.log For example. MAXIMO_HOME\maximo\tools\maximo\ log\updatedb<TIMESTAMP>. if your base services installation directory is C:\IBM\SMP\Maximo.txt WAS_HOME\profiles###BOT_TEXT###lt;PROFILE>\logs\ <SERVER_NAME>\startServer.txt Maximo Logs There are also a few logs kept by Maximo itself.Table 22. These logs are often helpful in the diagnosis of errors in particular EAR files or other back-end operations.log C:\Program Files\IBM\Common\acsi\ logs###BOT_TEXT###lt;USERNAME>\de_trace.log 196 IBM Tivoli Provisioning Manager Version 7.log For example.log So for instance. such as database connections. Log file information (continued) Log type Solution Install/Deployment Engine Logs Description These are logs kept by the IBM Solution Installer/Deployment engine run time. the logging information would be written to these files: C:\IBM\SMP\Maximo\ tools\maximo\log\ updatedb20070419170607. and failure of a few back-end commands provided by Maximo.2 Installation Guide .log WAS_HOME\profiles###BOT_TEXT###lt;PROFILE>\logs\ <SERVER_NAME>\SystemErr. This run time has its own logging system. exceptions. Note: After an installation these logs will contain sensitive credentials.log WAS_HOME\profiles###BOT_TEXT###lt;PROFILE>\logs\ AboutThisProfile. and that you run the UpdateDB command on April 19th at approximately 5:06:07PM.log WAS_HOME\profiles###BOT_TEXT###lt;PROFILE>\logs\ <SERVER_NAME>\SystemOut. the logs would be found under: v C:\Program Files\IBM\Common\ acsi\logs\tioadmin\de_msg.

If Cygwin is not installed. 2. Core components or web components installation hangs during Cygwin installation Problems with your Cygwin installation might cause the installer to hang during prerequisite verification. After waiting a few minutes. Close the installer. Symptoms While the installer verifies prerequisites during Tivoli Provisioning Manager core components or web components installation. uninstall and then reinstall it manually. Cygwin is not automatically installed during the Tivoli Provisioning Manager silent install. the installer seems to hang and the Next button remains disabled. Appendix A. 3. For more information. the exact actions the Thin Client took and the associated responses from the WebSphere Application Server are stored in logs. Silent installation of Tivoli Provisioning Manager fails A silent installation of Tivoli Provisioning Manager will fail if Cygwin is not installed. Resolving the problem Install Cygwin manually before running the silent installation. Log file information (continued) Log type WAS Thin Client Logs Description The WAS thin client is the mechanism by which the process manager packages communicate with the WebSphere Application Server.valout It is a good practice to rename existing logs before attempting a package installation. and required Cygwin settings are configured during the installation process. Resolving the problem 1. see “Installing Cygwin manually” on page 208. Troubleshooting 197 .traceout MAXIMO_HOME\wasclient\logs\ wsadmin. Symptoms The silent installation of Tivoli Provisioning Manager fails. It is useful to have a log that consists only of the information related to the success or failure of current package installation to facilitate problem determination. Causes Cygwin is not installed. Location MAXIMO_HOME\wasclient\logs\ CTGIN_wsadmin.traceout MAXIMO_HOME\wasclient\logs\ wsadmin. Causes There might be a problem with your Cygwin installation. If this automated deployment fails. Tivoli Provisioning Manager requires Cygwin.Table 22. install it manually. Verify if Cygwin is installed. If Cygwin is installed. the following message appears: The Installation Wizard is checking the system prerequisites.

If the problem persists. Symptoms You receive an error message that refers to missing tools. Click Back. Double-click the Cygwin icon on the Windows desktop on the Tivoli Provisioning Manager compute to create the missing directory.2 Installation Guide . Click Next in the installer to continue with the installation. no /home/Administrator directory is created. Causes The download site that you chose for the Cygwin install might be unavailable. Create the directory and then proceed normally. 3. the error message is displayed. Click OK to close the error window. cancel the installation. Causes If you installed Cygwin manually. Symptoms During the first discovery target server validation after installing Cygwin. you might be missing some of the required Cygwin installation packages and be missing tools such as Telnet or FTP as a result.First discovery fails after installing Cygwin After installing Cygwin. 2. 2. such as Telnet or FTP. Click Next to continue with the installation. 198 IBM Tivoli Provisioning Manager Version 7. uninstall Cygwin. Resolving the problem 1. the first discovery fails because of a missing directory. When the first discovery does not detect this directory. For more information. see “Installing Cygwin manually” on page 208. Select a different download site from the Cygwin Download Mirror Sites list. you might be missing some of the required Cygwin installation packages. Resolving the problem 1. 3. an error message like the following is displayed: First discovery failed: /home/administrator does not exist Causes After Cygwin is installed. Cygwin installation fails Cygwin installation will not work if the download site is unavailable. Symptoms The Cygwin installation fails. and then attempt to install Cygwin manually. Choose a different download site and try again. Missing tools from Cygwin installation If you installed Cygwin manually.

Note: You must have login access to the installation admin workstation to run the configdb command. Check the log files under Program Files\IBM\Common\acsi\logs\Administrator. 4.iuregistry. Causes Interactive user sessions or background processing might be occurring at the same time Admin mode is turning on. However. then the deployment engine is not in a working state. 2.si. Run the listIU command again. see “Installing Cygwin manually” on page 208.Resolving the problem Verify that you have a fresh Cygwin installation with all the required Cygwin packages. Turning on Admin mode is slow Interactive user sessions or background processing might be occurring at the same time Admin mode is turning on. you can manually run the configdb command to get into Admin mode without waiting.lang. WebSphere MX server. It will eventually turn on if left alone. Resolving the problem Typically. but you can also use it immediately by running the configdb command. if left alone.ac. Stop the application server. Program Files\IBM\Common\acsi\bin\listIU If the listIU command reports no output or a return code of 2. if you need to quickly apply database configuration changes. Symptoms Turning on Admin mode from the Database Configuration application takes a long time. For more information. Admin mode will eventually turn on.log: FINE: ENTER^java. Appendix A.IURegException: IURegistryServiceUnavailable Resolving the problem Ensure that the deployment engine is working by running the following commands and examine the output: 1. 1. Program Files\IBM\Common\acsi\setenv 2. 3. Use the Windows Control Panel to stop and start the service called IBM ADE Service. either using the WebSphere Administrative Console or the command line.ibm. Follow the steps below to quickly turn on Admin mode: 1. Troubleshooting 199 .RuntimeException: com. Web components installation fails with registry service unavailable Java exception (IURegException) Symptoms The following IURegException appears in MAXIMO_HOME\logs\CTGInstallTrace00. Start the web component installation again.

Other problems See the following information to diagnose and resolve other problems and installation errors. For more information about this command.2 Installation Guide .log v TIO_LOGS/console. you cannot log in to Tivoli Provisioning Manager as the Admin user.de. several log files contain error messages. Log file errors after successful installation on Microsoft Windows Server 2008 R2 Standard Edition (x86 64-bit) any SP After a successful installation of Tivoli Provisioning Manager on Microsoft Windows Server 2008 R2 Standard Edition (x86 64-bit) any SP. the Tivoli Provisioning Manager authentication service validates the user ID with the user ID value in LDAP. You receive the following error message when you try to log in: BMXAAA0035E . the installation completes successfully but you cannot log in to Tivoli Provisioning Manager.dto.orchestrator. the user ID is not recognized and you cannot log in. ClassNotFoundException: com. The user ID authentication validation between LDAP and the Tivoli Provisioning Manager MAXUSER table is case-sensitive so the values must be identical. Run the configDB command.maximo.java:243): COPDEX040E An unexpected deployment engine exception occurred: java. Symptoms After successfully installing Tivoli Provisioning Manager using the "Use WebSphere application security only for authentication" option.DeploymentRequestDAO. Stop the deployment engine using the tio. Some of the log files that contain error messages are: v TIO_LOGS/trace. Symptoms After successfully installing Tivoli Provisioning Manager.log The error messages look like the following: ERROR [Workflow Dispatcher] (WorkflowDispatcher.log v TIO_LOGS/install_wrapper/tcinstall. Diagnosing the problem Several log files contain error messages.The user Admin is not recognized. The user ID validation is case-sensitive so the Tivoli Provisioning Manager table name value and the user ID value in LDAP must be identical.2. several log files might contain error messages. see the section called Configuring the database in the System Administrator Guide. 200 IBM Tivoli Provisioning Manager Version 7.lang. Cannot log on after successful installation If you specify a user ID during base services installation that does not exactly match the corresponding Tivoli Provisioning Manager database user ID. 3. Please contact your system administrator Causes If the Tivoli Provisioning Manager user ID in the MAXUSER table does not exactly match the user ID value in LDAP. When you try to log in. Resolving the problem You can ignore these error messages. They do not indicate a problem with your installation. These particular error messages do not indicate a problem with your installation and you can ignore them.cmd stop command.ibm.tivoli.

collect the following information. run a SQL command like the following: SELECT USERID. update the database table as follows: UPDATE MAXUSER SET LOGINID=’maxadmin’ WHERE LOGINID=’Maxadmin’ 3. Run the following command from the WAS_HOME/bin directory: genVersionReport. if your LOGINID is Maxadmin. Note: Log files are encoded in UTF-8 format. Determine the value of the MAXUSER table. run the following command: UPDATE CREDENTIALS_PASSWORD SET USER_NAME=’maxadmin’ WHERE USER_NAME=’Maxadmin’ You should now be able to log in to Tivoli Provisioning Manager. Troubleshooting 201 . Update the database record to match the LDAP record by running a SQL command like the following one: UPDATE MAXUSER SET LOGINID=’<ldap_loginname>’ WHERE LOGINID=’Maxadmin’ For example. 2. Appendix A. If there are no values in the CREDENTIALS_PASSWORD table. To do this. ensure that you are using a text editor that supports UTF-8. When you are viewing log files. complete the following steps: 1. including service packs and fix packs.html. If v v v you need to contact IBM Tivoli Software Support. you can proceed to log in to Tivoli Provisioning Manager.LOGINID FROM MAXUSER WHERE LOGINID=’Maxadmin’ This returns output like: USERID LOGINID -------------------------------------------------MAXADMIN Maxadmin 1 record(s) selected. see Attribute mapping from LDAP to IBM Tivoli Provisioning Manager in the information center. Determine the values of the CREDENTIALS_PASSWORD table by running a command like the following: SELECT USER_NAME FROM CREDENTIALS_PASSWORD WHERE USER_NAME=’Maxadmin’ 4. Collecting information about installation problems Use this list to collect information when contacting IBM Tivoli Software Support. You can use the IBM Support Assistant to collect log files. if LOGINID in LDAP is maxadmin. which identifies the installed version of WebSphere Application Server and all installed maintenance packages. Operating system type and version. v The version of WebSphere Application Server.bat The command generates a report called versionReport. If there are values in the CREDENTIALS_PASSWORD table. For example. see Using log files for troubleshooting in the information center. The installation log files. For information about the user attribute mappings between LDAP and Tivoli Provisioning Manager. for example Windows Notepad.Resolving the problem To resolve this problem. For information about IBM Support Assistant. you can update the user ID values in the Tivoli Provisioning Manager MAXUSER and the CREDENTIALS_PASSWORD database tables to match the LDAP values. Hardware description.

com_hwoutput.example. Running the installation using Remote Desktop is not supported. 1. Change to the WAS_HOME directory and run: 2000 DB2 java -version Installation media type (disks or electronic download) and level.xml tpmserver. run db2level v The version of Java. You might need this information to perform some recovery actions.xml For some errors.com_vpdoutput. the file names include: cit_tpmserver.2 Installation Guide . insufficient disk space.log The files are located in: v %TEMP% Results are stored in XML files with the fully qualified domain name in the file name.xml tpmserver. antivirus software. Discovery: The installer uses discovery software to identify software and hardware on your computer.com_output. Log files for product components Component Cygwin Log file Log files are located in %TEMP%\cygwin-logs 202 IBM Tivoli Provisioning Manager Version 7.xml tpmserver. review information about the values used for the installation. For example if the fully qualified domain name is tpmserver. Cross-domain installation is not supported. check v %TEMP%\cit\cit. Discovery logs Type of information Installation of Inventory discovery Header If there are installation errors.com. Any Windows event log relevant to the installation error. Table 23. for example.v The version of the database server. you can click Back in the installer to go to the panel before the error occurred. You can also use these values if want to reinstall the product using the custom installation option. resolve the problem by making more space available. If you are logged on to the computer locally. Middleware installation: See “The middleware installer logs” on page 34 for information about the middleware installation logs. and then click Next to continue with the installation. v %TIO_LOGS%\install 4.example.log Inventory discovery scan log The results of discovery v %TEMP%\CITTrace. To check the version of DB2.example. v v v v Procedure If you performed a default installation.com_swoutput. Default 3. 2. for example.example. Windows services that were active during the installation. Software installation: The following log files are created during the software installation: Table 24.example. v If you are logged on as a local administrator or a domain administrator.

err files.log v trace_isx_install. Appendix A. If these logs are not available.log v *. Agent Manager certificate generation wsadmin.log v AgentManager\logs\am_upgrade. The defaults are: – %WAS_HOME%\profiles\ctgDmgr01\logs – %WAS_HOME%\profiles\ctgAppSrv01\logs DB2 The main installation logs are located in: v %TEMP%\db2_install_log. even if they are 0 KB.out v *.Table 24.log where AgentManager is the Agent Manager installation directory.##### Search for additional log files that start with db2 for other log information. Agent Manager Agent Manager v AgentManager\logs\AMReturnValues. you can ignore them as they do not indicate a problem with the Dynamic Content Delivery services.err file. If you see errors starting with The system cannot find the path specified in the MC-WAS-install-AS-CAS.out and *.err Ensure that you check the *. you can also check the following locations: %TMP%\tclog and %TMP%\tclog_wrapper WebSphere Application Server WebSphere Application Server v %TEMP%\was-logs\was-ismp-install.log Logs created by WebSphere Application Server Logs are stored in the following locations: v %WAS_HOME%\logs <user_root>\logs v where <user_root> is the WebSphere Application Server profile installation path.log WebSphere Application Server SystemOut log v %WAS_HOME%\profiles\ctgAppSrv01\logs\MXServer\SystemOut.traceout Dynamic Content Delivery Check the following location: v C:\Program Files\IBM\tivoli\common\ctgde The log files are: v trace_manager_install. Troubleshooting 203 . Log files for product components (continued) Component Tivoli Provisioning Manager core components Log file %TIO_LOGS%\install Logs for the Tivoli Provisioning Manager core component installer are located in TIO_LOGS/install_wrapper.

Uninstallation: When you uninstall Tivoli Provisioning Manager core components. C:\WebSphere\DeploymentManager\logs Tivoli common directory The Tivoli common log directory: v C:\Program Files\IBM\tivoli\common\COP\logs 5. Starting Tivoli Provisioning Manager.log is created in the default location: v C:\Program Files\IBM\tivoli\common\COP\logs 6. Log files for product components (continued) Component Tivoli Provisioning Manager for Job Management Service federator Log file The following log files are in TIO_HOME\DeviceManager\log: DMS_install. v CTGInstallMessage[nn]. the file tio_start. It also contains trace information after running the DMSconfig or DMSremoveconfig command with the showtrace option dms_config_trace.log Contains messages after running the DMSconfig or DMSremoveconfig command. the log files are located in: v %TIO_LOGS%\uninstall If the logs are not available in this location.zip file in the MAXIMO_HOME\debug directory. check the following location: v %TMP%/tclog_uninstall 204 IBM Tivoli Provisioning Manager Version 7.log Contains information about the Tivoli Provisioning Manager for Job Management Service federator installation.properties The base services Collect the log files from the computer where the base services are installed: v Run the following command: – MAXIMO_HOME\scripts\LogZipper. for example. dms_config_trace.2 Installation Guide .Table 24.log in the following directories: – C:\Documents and Settings\Administrator Collect the log files from the computer where WebSphere Application Server is installed: v Logs under the application server directory.log Contains detailed installation information when Tivoli Provisioning Manager for Job Management Service federator server and database is configured. for example.log and CTGInstallTrace[nn]. C:\IBM \WebSphere\AppServer\profiles\ctgAppSrv01\logs v Deployment manager logs in the deployment manager directory. When you start Tivoli Provisioning Manager. Values used for configuration are in: TIO_HOME\DeviceManager\config\DMSconfig.bat v Find the [current date]_[timestamp].

Run the default installation 2. Other installation and configuration tasks The topics in this section provide information about installation and configuration tasks that support the installation of Tivoli Provisioning Manager. 5. 2010 205 . Before you begin The following limitations apply to the default installation: v A default installation is only supported on Windows. If you selected Tivoli Provisioning Manager for OS Deployment. Verify your installation Figure 3. Perform required configuration Software is installed 3. On the Select Components panel. leave all the check boxes selected. accept the license agreement and click Next. If you are installing from a DVD. The following diagram shows the high level steps for a default installation. Click Default Installation and click Run default installation. Installing Tivoli Provisioning Manager with default values Default In a default installation. In the Welcome panel. 2. In the launchpad.exe (Windows 64-bit) or launchpad. all software is installed on a single Windows computer and default values are used for installation settings. 7. select a language and click OK. 3. Software installation Post-installation 1. the launchpad is on the Installation DVD for Windows. v A default installation is only supported on disk C:\. Log on with an account with system administration privileges.Appendix B. You must perform a custom installation instead.exe (Windows 32-bit) from the launchpad directory. 2003. 4. © Copyright IBM Corp. Double-click launchpad64. 6. click Next. Verify that the disk space requirements are met on disk C:\. Default installation steps To install Tivoli Provisioning Manager using a default installation: Procedure 1. v A default installation is not supported in Japanese due to limitations with the directory server installation.

hold Ctrl and click in the banner frame of the launchpad. and user passwords” on page 21. specify all required fields and click Next. Results The default installation is complete. the installer validates the workstation login information and then displays a summary of your installation settings. Messages that are generated while the launchpad is running are not automatically saved on the hard disk. the database instance owner. database names. Cygwin 1. 10. the generated launchpad messages are captured in a hidden log frame. and other administrator users created during installation. insert the Installation DVD for Windows again. For example. specify the directory where Cygwin is installed and click Next.8. Review your installation settings and then click Next. User Name Specify the user name for running the Cygwin SSH service. v If you do not require support for IPv6 communication in the Tivoli Provisioning Manager environment. This value is case-sensitive. To display the log frame on the bottom of the launchpad panels during run time. select the Copy installation images from media check box and specify the location of the images. You can save the messages from a runtime session by clicking Save 206 IBM Tivoli Provisioning Manager Version 7. 9. After the DVDs are copied. Generic Password for Default Installation Specify the password that you want to use for the main Tivoli Provisioning Manager administrator user.10 or later is required. Cygwin 1.2 Installation Guide . If Cygwin is already installed. Fully-Qualified Host Name The fully qualified domain name of the computer. If you want to copy the installation images from disks. Select a Cygwin download mirror site Select a location that you want to use to download Cygwin installation files. The password must meet DB2 password requirements described in “Preinstallation Step 7: Verify requirements for user names.example.com. Workstation Login User Name Specify the administrator user that you are using to perform the installation. When the launchpad is running. The default Windows administrator user is Administrator.5. specify the remaining settings for the installation and then click Next. tpmserver. Specify the location where you want to store the backup. you will be prompted to insert the DVDs so that the files can be copied. v If you require support for IPv6 communication in the Tivoli Provisioning Manager environment. If you selected the option to copy installation files from DVDs. Location of Images Specify the full path for the directory that contains the installation images.7 or later is required. tioadmin. If you want to install Cygwin. Backup Files Location The installer creates a backup of the database and key configuration files after the core component installation completes successfully. When you click Next. On the Default Installation panel. Specify the temporary directory for uncompressing installation images Select a temporary directory location to use during installation for extracting installation files from installation images. A location that is geographically closest to you is recommended.

at the bottom of the log frame and specifying where you want to save the file. This approach is useful in situations where you have installed Tivoli Provisioning Manager for testing or evaluation purposes. Installation of Tivoli Service Request Manager (SRM) with Tivoli Provisioning Manager See Installation of IBM Tivoli Change and Configuration Management Database and Tivoli Service Request Manager with Tivoli Provisioning Manager version 7.0. This task provides high-level instructions for installing Tivoli Provisioning Manager 7. open a web browser and log on by typing: https://host_name:9443/maximo. See Installing Tivoli Provisioning Manager silently .2. see “Step by step recovery for core components installation (default installation)” on page 173.1 on the same system. Removing a default installation To remove a completed default installation.2 to coexist with Tivoli Service Request Manager (SRM) 7. because the installation has failed.2. See Installing Tivoli Provisioning Manager silently .2. Once logged on.1 on the same system.0. the user name and password are maxadmin and maxadmin. This task provides high-level instructions for installing Tivoli Provisioning Manager 7. Other installation tasks 207 . What to do next Start Tivoli Provisioning Manager by running the following command: tio start tpm After it has started. you can reinstall the product if needed. Silent installation Default installation. When you have completely removed all Tivoli Provisioning Manager software. To remove a default installation at different stages.custom installation Uninstalling IBM Agent Controller Manually installing the IBM Tivoli Agent Controller Appendix B.default installation Custom installation. Installation of Tivoli Change and Configuration Management Database (CCMDB) with Tivoli Provisioning Manager See Installation of IBM Tivoli Change and Configuration Management Database and Tivoli Service Request Manager with Tivoli Provisioning Manager version 7. you must restore a system image that was captured before you started the installation. These topics can be found in the Tivoli Provisioning Manager wiki.2 to coexist with Tivoli Change and Configuration Management Database (CCMDB) 7.2. but might be useful depending on the configuration and products that you are using together with Tivoli Provisioning Manager. Silent installation and other installation tasks The following tasks are not mandatory for a Tivoli Provisioning Manager installation.

Stop the X11 server if it is running. you can install it again. Note: Install Cygwin just before installing the core components. cron. v If you require support for IPv6 communication in the Tivoli Provisioning Manager environment. For additional details. Remove all mount information with the following command: umount -A 208 IBM Tivoli Provisioning Manager Version 7. Removing a Cygwin installation To remove Cygwin: 1. Remove all Cygwin services such as sshd. Cygwin 1. If the service is running. Before you begin v If you do not require support for IPv6 communication in the Tivoli Provisioning Manager environment.2 Installation Guide .7 or later is required. If an existing version of Cygwin is installed. and stop any Cygwin programs that might be running in the background.Installing the monitoring agent for Tivoli Provisioning Manager Manually installing the monitoring agent for Tivoli Provisioning Manager Checking WebSphere Application Server status and version Checking WebSphere Application Server status and version Backing up the database and important data Backing up the database and important data Changing default passwords Changing default passwords Changing the transfer mode for the DVD-ROM Changing the transfer mode for the DVD-ROM Updating the port for the information center Updating the port for the information center Installing Cygwin manually The Tivoli Provisioning Manager core components installer and web components installer require a fresh installation of Cygwin.5. After Cygwin is removed.10 or later is required. see Setting up Cygwin. perform the following steps to remove it. stop it with the following command: cygrunsrv -E name where name is the name of the service. Cygwin 1. Then uninstall the service with the following command: cygrunsrv -R name 2. cygserver. and the computer must have only one Cygwin installation. and inetd. During a middleware installation Cygwin might cause an installation failure.

clear the Hide obsolete and administrative packages check box. 3. Reboot the computer. 7. 6. Normally. 3. If you added Cygwin to your system path. Installing Cygwin manually To install Cygwin manually: 1. 4. click Advanced. Go to www. 2. v If you receive a Permission Denied error. Log on to the Windows computer using a user account with administrator privileges.exe) gzip (contains gzip. 4. remove it.exe) Database Devel All default packages and the following additional package: cvs Doc All default packages and the following additional package: perl_manpages All default packages Package Appendix B.com and install an appropriate version of Cygwin based on the Cygwin version requirements.Exit the command prompt and ensure that no Cygwin processes remain. On the Security tab. On the Owner tab. Delete the Cygwin shortcuts on the Desktop and Start Menu. In Windows Registry. Other installation tasks 209 . ensure that all services are stopped and all Cygwin programs are closed. modify the permissions or ownership to your user account on the files or folders that caused the error. ensure that your account is listed as the owner. Select the Replace owner on subcontainers and objects check box and then click OK. Select the following packages: Table 25. To change ownership for the Cygwin folder from Windows Explorer. if it exists.cygwin. Delete the Cygwin installation directory and all its subdirectories. delete the registry tree Software\Cygnus Solutions under HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. the only information stored in the registry is the mount information.exe) shutdown Archive All default packages and the following additional packages: cabextract sharutils unzip zip Base All default packages and the following additional packages: bash (contains bash. right-click the Cygwin folder and click Properties. Cygwin packages Category Admin All default packages and the following additional packages: cron cygrunsrv (contains cygrunsrv. If you set the CYGWIN environment variable. remove it. 5. v If you receive an error about an object is in use. 8. On the Select Package panel of the Cygwin installer.

Cygwin packages (continued) Category Editors All default packages and the following additional packages: ed vim Gnome Graphics Interpreters The following packages: expect (contains expect. ftp) openssh (contains ssh.exe) ping rsync urlgrabber Publishing Shells All default packages and the following additional packages: ash bash (contains bash. After installation. The directory must be the first one in the %PATH% variable.exe) gawk perl Libs Mail Math Net All default packages All default packages All default packages All default packages and the following additional packages: curl inetutils (telnet.exe) System Text All default packages and the following additional package: util-linux Utils All default packages and the following additional packages: ccrypt cpio cygutils diffutils file keychain time Web All default packages and the following additional package: wget X11 PostInstallLast python All default packages All default packages All default packages All default packages All default packages All default packages All default packages Package 5.Table 25. add the Cygwin\bin directory to your Windows %PATH% environment variable.2 Installation Guide .exe) openssl (contains ssl. 210 IBM Tivoli Provisioning Manager Version 7.

The provisioning server communicates with the database to perform most of your actions on the web interface. and tracking and recording status and activity. You can start the provisioning server in one of the following ways: v From the Windows desktop v From the command line Important: The database server and directory server must be running before starting the provisioning server and remain running while the provisioning server is running. To start the middleware. d. see “Starting middleware on Windows” on page 94. Appendix B. After a reboot. In the System Variables section. 2. Click the Advanced tab. Starting the provisioning server Before you begin 1. The following example shows a Path value with the Cygwin\bin directory at the beginning. For information about other start and stop options for the provisioning server. 8. right-click My Computer and click Properties. Running it from a remote desktop can cause problems with Tivoli Provisioning Manager installation. c. To set up SSH. By default. Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. running provisioning tasks. If you modified the PATH variable. the WebSphere Application Server profiles associated with the provisioning server are also started. Open a Cygwin console and run the following commands: chmod +r /etc/passwd chmod +r /etc/group chmod 755 /var 7. These services are started automatically after installation or after a reboot. Ensure that SSH is running. reboot the computer before you continue with Tivoli Provisioning Manager installation to ensure that the changes take effect.%SystemRoot%\system32 6. Ensure that the middleware applications are started. Click Environment Variables. b. Starting and stopping the provisioning server on Windows Starting the provisioning server allows you work with the web interface. Starting and stopping Starting and stopping the provisioning server. except for the Tivoli Directory Server database instance and administration daemon. when you start the provisioning server. run the command ssh-host-config -y locally on the computer. For more information about user account control in Windows 2008. see User Account Control Step-by-Step Guide. Other installation tasks 211 .a. so you must start it manually. Ensure that permissions are set properly. PATH=C:\Cygwin\bin. 2008 Use the following procedure if the provisioning server is stopped and you must restart it. See the following topics for more information about starting and stopping the provisioning server. the provisioning server is not started automatically. including retrieving the data to be displayed. The provisioning server uses the directory server to authenticate users when they log on and to validate access permissions while using the product. On the desktop. edit the value of the Path variable. see the tio command in the Reference section of the information center. The actual contents of the variable will depend on the configuration of your computer.

log %TIO_LOGS%\dmsresultserver\dmsresultserver_start. or if you change a default administrator password.log Note: If you see errors that start with [ERROR] Failed to get reports in the tio_start. see the tio command in the Reference section of the information center. run the TPM Stop icon or the tio. enter the WebSphere Application Server administrator user name and password. 2. you can start the provisioning server. Stop the provisioning server.log %TIO_LOGS%\agentshellserver\agentshellserver_start. Log on as the tioadmin user. Start the provisioning server. Log on as the tioadmin or the Administrator user. these errors can be ignored and do not indicate a problem starting the provisioning server. b. Change to %TIO_HOME%\tools. the WebSphere Application Server profiles associated with the provisioning server are also stopped.log v %TIO_LOGS%\tio_start_service. you must stop the provisioning server.2 Installation Guide . You can stop the provisioning server in one of the following ways: v From the Windows desktop v From the command line By default. when you stop the provisioning server. the message TIO startup completed. From the Windows desktop Double-click TPM Start. If the provisioning server is not properly stopped and preventing startup. From the Windows desktop: Double-click TPM Stop. Procedure 1.cmd stop command again to stop the provisioning server properly. From the command line a.log v v v v %TIO_LOGS%\policyengine\policyengine_start. If the provisioning server does not start.log file or Failed to connect to server in the console. is displayed. When prompted. From the command line 212 IBM Tivoli Provisioning Manager Version 7. For information about other start and stop options for the provisioning server.log files.Procedure 1.log or trace. check the following log files for errors: v %TIO_LOGS%\tio_start.cmd start 3.log %TIO_LOGS%\activityplan\activityplanengine_start. When the provisioning server is properly stopped. Type tio. Results When the provisioning server is ready. Stopping the provisioning server If you must make configuration changes to the provisioning server. 2.

the message TIO shutdown completed.log If the provisioning server is not properly stopped. Open a command window and run: net start remboserver net start remboagent Alternatively. Log on as an administrative user. The webserver1 profile is started automatically with the HTTP server. run the appropriate commands. Change to the AM_HOME\bin directory. check the following log files for errors v %TIO_LOGS%\tio_stop. is displayed.log v %TIO_LOGS%\tio_stop_service.a. To start a component. b. The agent manager v Starts when you start Tivoli Provisioning Manager. and select Run. Select Monitoring Agent for Tivoli Provisioning Manager . Procedure 1. Other installation tasks 213 . “Stopping middleware” on page 95 Results Upon successful shutdown. Run the following command: startServer. Click Start.msc. Tivoli Monitoring agent v Starts automatically after installation or after a reboot: a. Tivoli Provisioning Manager for OS Deployment v Starts automatically after installation or after a reboot.cmd stop 3. run the TPM Stop icon or the tio. b. except webserver1. you must stop them separately. and click OK. c. “Starting and stopping Tivoli Provisioning Manager components” b. and click Start the service. b. b. 2.cmd stop command again to stop the provisioning server properly. If you must stop other components or middleware.Primary. a. Starting and stopping Tivoli Provisioning Manager components Use these instructions if you need to start or stop specific Tivoli Provisioning Manager components manually. Type tio. Log on as an administrative user. All WebSphere Application Server profiles are started automatically by Tivoli Provisioning Manager. See the following information: a. Type services. a.bat Appendix B. go to %TIO_HOME%\tools. At a command prompt. you can start Tivoli Provisioning Manager for OS Deployment from the Services control panel. If the provisioning server does not stop.

the device manager service is successfully installed. and click OK.To verify the status of the agent manager. c. and click Stop the service.msc. b. The default user is maxadmin. 3. go to http://host_name:9513/AgentMgr/Info. To start the monitoring agent: a. 3. To stop the monitoring agent: a. 214 IBM Tivoli Provisioning Manager Version 7. Start Tivoli Provisioning Manager: v “Starting and stopping the provisioning server on Windows” on page 211 2. b. In a command window. Procedure 1.log for any additional information. Tivoli Provisioning Manager for OS Deployment a. Log on with the Tivoli Provisioning Manager administrator user name and password that you specified during core components installation. Check the log file WAS_HOME/profiles/ctgAppSrv01/logs/MXServer/DMSMsg1. Verifying components Verify that you can access the main interface and that main components are running.Primary. Type services. Change to the WAS_HOME\profiles\casprofile\bin directory. Procedure 1. Run the following command: stopServer.Primary. b. and select Run. type the following URL: https://host_name:9045/admin b. A status page is displayed for the agent manager with information about the agent manager version and configuration. b. Select Monitoring Agent for Tivoli Provisioning Manager .msc. Type services. The agent manager a. 2. Log on as an administrative user. and select Run. b. and click Start the service. Click Start.2 Installation Guide . and click OK. type the following commands: net stop remboagent net stop remboserver Note: You can also stop Tivoli Provisioning Manager for OS Deployment from the Services control panel. c. Select Monitoring Agent for Tivoli Provisioning Manager . In a supported web browser.bat server1 -username wasadmin_username -password wasadmin_password Starting and stopping the Tivoli Monitoring agent Complete these steps to manually start or stop the Tivoli Monitoring agent. Click Start. run the appropriate command. In a supported web browser. type the following URL: https://host_name:9045/dmserver/TraceServlet?trace=set If you see the word SUCCESS!. Verify the installation of the device manager service: a. Verify that you can log on to the dynamic content delivery management center: a. To stop a component.

hostname.0 or 7. If you installed Tivoli Provisioning Manager for OS Deployment. Signing on to the provisioning server For security reasons. 6. you must sign on to the provisioning server. verify that FIPS compliance is enabled. To verify the Mozilla Firefox version. Appendix B. Click the Configuration tab to view information about the boot server. Click Go To > Deployment > OS Management > Boot Servers. run: firefox -version Ensure that the command returns no errors before starting the installation. v You know your user name and password for the provisioning server. v Mozilla Firefox 3. the maxadmin user must set up security roles and users for your organization. the dynamic content delivery management center was installed successfully. Click Go To > Administration > Provisioning > Provisioning Global Settings.If you can log on successfully. Click the FIPS tab. type the following URL: https://host_name:9043/ibm/console Log on with the WebSphere administrator user name and password. Other installation tasks 215 .com.0 and higher. c. FIPS compliance is enabled. type: https://host_name:9443/maximo b. Specific roles can be assigned to perform different provisioning tasks. d. see the Controlling user access topics in the Provisioning User Guide. In the list of boot servers. If you configured compliance with Federal Information Processing Standard (FIPS) 140-2 during installation. Make sure that the following requirements are met: v The provisioning server is running. For example. 4. verify the installation: a. c. v You have read the Controlling user access topics in the Tivoli Provisioning Manager information center to understand how security is implemented in Tivoli Provisioning Manager. FIPS compliance is disabled. In a supported web browser. In a supported web browser. v Do not use the maxadmin user to perform provisioning tasks. If the check box is selected. 7. a. Before starting to use Tivoli Provisioning Manager. If the check box is cleared. 5.domain. b. v You know the fully qualified domain name of the provisioning server. Verify that you can log on to the WebSphere administrator console. The default user name is wasadmin. type the following URL: https://host_name:9511/AgentMgr/Info Information about the agent manager version and configuration is displayed. This is the parent boot server.0 with the latest patch. verify that a computer with the Tivoli Provisioning Manager host name is in the list. Before you begin The following web browsers are supported: v Microsoft Internet Explorer version 6. For more information. In a supported web browser. Verify the status of the agent manager. Check the value of the variable called FIPS.

verify the following: Your system meets the logon prerequisites. 1.o=ibm. In Internet Explorer. maxadminusr. 216 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide . By default. 2. In the Log On window. Start the web browser and type https://host_name:port/maximo. Results You are now signed on to the provisioning server. If v v v you have problems logging on. 3. the password for each user ID is the same as the User Name (for example. Note: User names and passwords are case sensitive. If you are using customized settings for any of the web content zones. To sign on to the provisioning server: Procedure 1.ou=groups.Table 26. Click Tools > Internet Options. which displays the Start Center. The default user names and passwords are lowercase. 2.ou=swg.c=us" objectclass=* ibm-allmembers You can also use an LDAP browser tool to help you to obtain user and group information from your directory server. check the security settings in the browser. For the wasadmin user. type your User ID and Password and click Log On. where host_name is the fully qualified domain name of the provisioning server. log off the provisioning server after you have completed your tasks. click Default Level to use the default security level and then try to log on again.c=us" objectclass=person The following example command lists all members of the maxadmin group: ldapsearch -D cn=root -w <password> -s base -b "cn=maxadmin. Click the Security tab. For the users maxadmin. Signing off the provisioning server To prevent unauthorized access to the web interface. the password is the one that you specified during installation. you are automatically logged off after 30 minutes of inactivity. The default port number is 9443. Users and groups User wasadmin maxadmin (maxadminusr for MS Active Directory) mxintadm maxreg maxadmin maxadmin Groups The following example command lists users in a standard Tivoli Directory Server installation: ldapsearch -D cn=root -w <password> -s sub -b "o=ibm. maxadmin is both the user name and the default password). Your user name and password are correct. This value is case-sensitive. and mxintadm.

v The MAXADMIN group with the maxadmin and mxintadm users. Run the following code: Appendix B. run the following command: taskRunner CONTINUE STOPONERROR 6. define group privileges and add them to the database.adminuserid=<maxadmin> mxe. Set up a silent installation response file with the following lines: RUN_CONFIG_YES=0 RUN_CONFIG_NO=1 and ensure that the health check is turned off. What to do next You must completely close all tabs and exit the browser after logging off the web interface to completely end the session. Procedure 1. update the c:\ibm\smp\etc\install.Procedure Click Sign Out to sign out of the web interface. Run the following SQL commands: v 2000 DB2 Connect to the database. If you do not exit the browser after logging off. 2.int. maxreg. Working with users To create multiple users. After the installation is completed. In the c:\ibm\smp\scripts directory.adminPasswd=<maxadmin pwd> mxe.properties file with the following properties: mxe. Results You are now signed out of the web interface. another user can open a new tab and access the web interface without logging on.reguser=<maxreg> mxe. Set the following environment variable: set skipwasvalidation=yes 3. 4. and mxintadm users. define group privileges and add them to the database. Other installation tasks 217 . See the following topics for more information about working with users.adminloginid=<maxadmin> mxe.dfltuser=<mxintegration> 5. Creating multiple users with maxadmin privileges To create multiple maxadmin users. Create the following required users and groups in the directory: v The MAXIMOUSERS group with the maxadmin. Open a DB2 command window and run the following command: connect to maxdb71 user dbusername using dbpassword where dbusername and dbpassword are the runtime user name and password used to connect to the database.

type. null. databaseuserid. pwhintanswer. inactivesites. \ password. null.1. null. 1.loginid. defsite.rowstamp) \ values \ (NEXTVAL FOR GROUPUSERSEQ. \ null. databaseuserid.’TPCONFIGURATIONLIBRARIAN’. rowstamp) values \ (’NEWMXINTADM’.userid.userid. \ pwhintquestion.’TPDEVELOPER’. \ password. ’NEWMXINTADM’. defstoreroom. pwhintanswer. null. personid. NEXTVAL FOR MAXSEQ) insert into maxuser \ ( userid. 218 IBM Tivoli Provisioning Manager Version 7.groupname.’NEWMAXADM’.2 Installation Guide .0.’TPADMIN’.’TPDEPLOYMENTSPECIALIST’. failedlogins. pwexpiration. 1.’NEWMAXADM’. NEXTVAL FOR MAXUSERSEQ.screenreader. rowstamp) values \ (’NEWMAXREG’. \ null. ’NEWMAXADM’.groupname. Continue with the installation process.loginid. null. null. null.rowstamp) \ values \ (NEXTVAL FOR GROUPUSERSEQ. sysuser. \ pwhintquestion. \ pwhintquestion.NEXTVAL for MAXSEQ) insert into groupuser (groupuserid. defsite. status. null. querywithsite. maxuserid.screenreader. null. 0. ’ACTIVE’. storeroomsite. null. 0.NEXTVAL for MAXSEQ) insert into groupuser (groupuserid.’newmaxadm’. querywithsite.’NEWMAXADM’.forceexpiration. null.’TPCOMPLIANCEANALYST’. NEXTVAL FOR MAXUSERSEQ. null.insert into maxuser \ ( userid. querywithsite. personid. null.1. NEXTVAL FOR MAXUSERSEQ. null. 1.rowstamp) \ values \ (NEXTVAL FOR GROUPUSERSEQ.NEXTVAL for MAXSEQ) insert into groupuser (groupuserid. status. 0. type. null.forceexpiration. NEXTVAL FOR MAXSEQ) insert into maxuser \ ( userid. null. defsite. 1. failedlogins. 1. failedlogins. \ cast(’ABC’ as varchar(128) for bit data). null. storeroomsite.groupname. pwhintanswer.userid. memo. status. ’ACTIVE’.’newmxintadm’. null.’NEWMAXADM’. \ cast(’ABC’ as varchar(128) for bit data).forceexpiration.0. NEXTVAL FOR MAXSEQ) insert into groupuser (groupuserid. ’TYPE 1’.1. pwexpiration. \ cast(’ABC’ as varchar(128) for bit data).’NEWMAXADM’. \ null. pwexpiration. storeroomsite. defstoreroom. defstoreroom. type. memo. maxuserid.userid.NEXTVAL for MAXSEQ) insert into groupuser (groupuserid. memo.0.rowstamp) \ values \ (NEXTVAL FOR GROUPUSERSEQ. 0.screenreader.’newmaxreg’. rowstamp) values \ (’NEWMAXADM’.NEXTVAL for MAXSEQ) NEWMAXADM The value for MAXADMIN NEWMXINTADM The value for MXINTADM NEWMAXREG The value for MAXREG 7.groupname. 0. null. databaseuserid. ’TYPE 1’. \ password. personid. sysuser. maxuserid.groupname. inactivesites. null. 1. ’ACTIVE’. ’TYPE 1’. null. sysuser.userid. ’NEWMAXREG’.rowstamp) \ values \ (NEXTVAL FOR GROUPUSERSEQ.loginid. inactivesites. 0.

boulder.boulder.Changing user passwords User passwords cannot be changed in the web interface.jsp?topic=/com.doc/install27. Other installation tasks 219 . Launch the tool using the following web address: http://<hostname>:12100/IDSWebApp/IDSjsp/Login. Start the Web Administration Tool using the following command: v <install_path>\idstools\bin\startWebadminApp. Tivoli Directory Server provides a Web Administration Tool so that users can change their password.htm. for example: dn: cn=tioappadmin.com/infocenter/tivihelp/v2r1/ index.IBMDS.ibm. The LDAP administrator can update the permissions by running the following command: ldapmodify -D <adminDN> -w <AdminPwd> -i <modifyACL.jsp where hostname is the host name of the Tivoli Directory Server.ldif where the modifyACL. and correct common problems with the application that it monitors. Using the Tivoli Monitoring agent The monitoring agent for Tivoli Provisioning Manager enables you to monitor Tivoli Provisioning Manager and to perform basic operations with Tivoli Provisioning Manager. 2. The software includes the following features: v Monitoring v Data gathering Appendix B. Click User properties > Change password. After the Web Administration Tool is installed.ldif file contains the following information. For detailed instructions.dc=com with your user dn. If users receive the following error when they try to change their password.jsp?topic=/com. 3. Log on to the tool with your user name.htm.ibm.bat where install_path is the directory where you installed Tivoli Directory Server.dc=ibm. The user does not have the authority to modify the password. see the topic called Starting the Web application server to use the Web Administration Tool: http://publib.com/infocenter/tivihelp/v2r1/index.userpassword:rwsc Replace cn=tioappadmin.dc=com changetype: modify add: aclentry aclentry: access-id:cn=this:at.dc=ibm. users have the correct permissions to update their own passwords. 4. The Web Administration Tool is not installed by default.doc/ install18.ibm.ibm. The monitoring agent can identify.IBMDS. After the command is run.ldif> For example: ldapmodify -D cn=root -w password -i modifyACL. users can update their password: Procedure 1. See the documentation for details on how to install the Web Administration Tool: http://publib. notify you of. they do not have permission to update their own password: GLPWCO025W The password cannot be changed.

it is highly recommended that you create a backup image of the server before running the host name rename feature. and Tivoli Enterprise Portal desktop client. see the topics Deploying monitoring agents across your environment and Updating agents in the IBM Tivoli Monitoring Version 6. Task Monitoring Collects information about tasks that were executed in the last few days and tasks that are scheduled for today. This process is not always recoverable. Determine the Service IP address for the provisioning server HADR cluster. which means it is on another system other than the Tivoli Provisioning Manager server: v Changing the host name for the remote database system is not covered by this feature. Proceed with the HADR configuration. and the host name change solution may be used to establish the Service IP. v For information about using the monitoring agent. Before you use the monitoring agent for Tivoli Provisioning Manager. 220 IBM Tivoli Provisioning Manager Version 7. see Manually installing the monitoring agent for Tivoli Provisioning Manager in the Tivoli Provisioning Manager wiki. a few updates must be performed on the database.2 information center.2 information center . see Monitoring agent for Tivoli Provisioning Manager User Guide. Note: If the database or directory server is remote.2 Installation Guide . For example: 1. you must install the monitoring agent support on the Tivoli Enterprise Monitoring Server. related components. Tivoli Enterprise Portal Server. What to do next v For information about manual installation of the monitoring agent. v For more information on upgrading the Tivoli Monitoring agent. see the topic Installing and enabling application support in the IBM Tivoli Monitoring Version 6. To rename the host. and configurations. 2. Script execution tracks where it failed and skips any steps which had been previously performed. If any issues occur.2. try to resolve the error and continue from the current step. log on to the provisioning server and follow the instructions in sequence. High Availability and Disaster Recovery Considerations A common reason to perform a host name and IP change is in preparation for a High Availability and Disaster Recovery (HADR) configuration. Perform the host change scenario described herein using the Service IP.v Event management The monitoring agent for Tivoli Provisioning Manager can provide the following functions: Availability Monitoring Provides information about the provisioning server and the components that are dependent on Tivoli Provisioning Manager. Changing the host name for the provisioning server When the host name and IP address need to be changed for theTivoli Provisioning Manager server. 3. continue with a regular upgrade of the monitoring agent.2. For information about these tasks. The Tivoli Provisioning Manager HADR solution is based on the usage of a Service IP. v If you are working in a Windows environment. v Changing the LDAP server system using a different host name is not covered by this feature.

Open the property file. If the example value is correct. the parameter values are pulled from this file. it is recommended to contact Tivoli Provisioning Manager support if a host name change is required for an active provisioning server cluster. Edit the property file and add all the values for the parameters. Procedure 1. When you run the scripts. These parameters are used for the scripts that are run on the new provisioning server: v tpmChangeDBHost v tpmChangeOtherHost Requirements for the property files: v All parameters that specify a value in brackets ([]) are example values and must be reviewed.For an existing HADR configuration. Other installation tasks 221 .properties 2008 Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. delete the brackets. 2. general HADR considerations such as ensuring that the operational state of the resource group is offline. Complete the property file with all the parameter values that the scripts use when changing the host name. For more information about HADR. v TIO_HOME/tools/rename_host/script_win. would have to be considered. Adding the parameter values to the property file When changing the host name. There is one property file that manages all the parameters required for the scripts to back up the old provisioning server to change the host name to the new provisioning server. This is the user name to connect to the agent manager. Required passwords for changing the host name on the new provisioning server Component DB2 Agent Manager Resource Manager SSL WebSphere Application Server Password The password for the database instance or the database runtime user. delete the example value and the brackets and type the correct value. see User Account Control Step-by-Step Guide. The script checks that all brackets are removed for required parameters. The password for the WebSphere Application Server administrator. you run two scripts. the host change scenario has not been validated. Add the parameter values to change the other host names (the values are case-sensitive): Appendix B. For more information about user account control in Windows 2008. The password for the resource manager user name. If the example value is not correct. The default password for the resource manager is CDSRMPASS. While in theory the solution is general purpose. Changing the host name is completed using a series of steps which includes execution of two scripts which modify the application configurations. see High availability disaster recovery Required passwords Host name rename requires the input of passwords on some components. Given the installation-specific nature of many HADR solutions. Table 27.

From the Start Center. For example. Review the list of parameters and values to ensure that they are correct. proceed to “Assigning the new host name to the provisioning server. What to do next When you are satisfied that the parameter values are correct. or example values.v v v v v v v v v v v v v v v v v v dbIsRemote dbInstanceName dbPort dbHome dbOSUser wasUser wasCellName fqNewHostName fqOldHostName tpmfosdDataDir TrustedCertificateQuery. Ensure the fully qualified host name for the provisioning server defined in the data model contains all lowercase characters before performing the host name change operation: a. Ensure that the following middleware is running: v Database server. see: v “Starting middleware on Windows” on page 94 2. remove any parameters that are specific to Oracle database. For details on how to start these systems.Host v amUser v dmgrSoapPort v ldapType See “Parameters for the host name rename feature” on page 226 for a list of parameters and their default values.Host amPort CertManagement. 4.Host CatalogueService.Host httpServerHome AgentManagerQuery. some manual steps are required after assigning the new host name. v LDAP server.” Assigning the new host name to the provisioning server To change the host name of Tivoli Provisioning Manager.Server. click Go To > Deployment > Provisioning Computers. Save the property file. and descriptions. v WebSphere Application Server. 5. 3. 222 IBM Tivoli Provisioning Manager Version 7. Remove any database-specific parameters that do not apply to your provisioning environment. Before you begin 1.2 Installation Guide .Host Registration. if you use DB2 database.Host AgentQuery.

cmd When the script runs. right-click My Computer and select Properties. The new host name of the new provisioning server is returned. enter the IP address of the old provisioning server.b. Ensure that the name is defined in all lowercase characters. For example. Reboot the provisioning server. d. In the IP address field. see User Account Control Step-by-Step Guide. Stop any WebSphere Application Server Java processes that are running. b. If Tivoli Provisioning Manager is setup to run automatically. c. From the Computer Name tab. d. type ping <hostname>. d. click Change. Save your changes. To stop the provisioning server: v TIO_HOME\tools\tio stop 4. Host name: At the command prompt. select Internet Protocol (TCP/IP) and click Properties. a. Click Go To > IT Infrastructure > Provisioning Inventory > File Repositories. In the list. Other installation tasks 223 .xml file. In the Computer name field. c. v Use the Task Manager to stop the running processes. and run the following script from the TIO_HOME/tools/rename_host/ directory: v tmpChangeDBHost. if the host name is a fully qualified host name. or command shell. enter the host name of the old provisioning server. b. 2. Procedure 1. Validate the host name and IP address of the provisioning server. use a fully qualified host name for the new name. It is recommended that the user use only lowercase characters. where <hostname> is the host name of the new provisioning server. 5. Follow the naming convention used by the original host name that you are changing. b. 3. Change the new host name and new IP address of the provisioning server. Navigate to Control Panel > Network Connections and double-click the local area network connection that you are using. Log on to the new provisioning server. Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. Click OK to save your changes. change the IP address: a. IP address: At the command prompt. 6. Search for the provisioning server and check if the host name is defined all lowercase characters. it may fail now because the host name has been changed after the system has restarted. Open a command window. The new IP address of the new provisioning server is returned. For more information about user account control in Windows 2008. Appendix B. To change the host name: a. Search for the file repository using the provisioning server host name. To On the desktop. you are prompted for the database administrator user or database instance user password. v Log on to the new provisioning server as administrator. type hostname. c. Ensure that there are all lowercase characters for the provisioning server host name in TIO_HOME\xml\tpmfosdbootserver. 2008 This procedure changes the host name for the server and updates most of the Tivoli Provisioning Manager database configurations.

To validate that the change was successful. Replace the existing maximo.donotrun=ALL 4.properties file using a binary editor. 5. Log on to the provisioning server as tioadmin. update the base services maximo. v “Return codes” on page 227 What to do next Proceed to “Updating the database server host name from the administrative workstation. Note: After the maximo. 8. The log lists the status of each step that was completed. Procedure 1.crontask.log. Note: If you have a remote database server.” Updating the database server host name from the administrative workstation Change the host name and the IP address for the database server.2 Installation Guide .properties file to change the IP or host name for the database server. 7. Results When the script runs. view the potential problems and log files so that you can resolve the issue and continue.properties file is copied from a Windows administration workstation to a non-windows provisioning server. 224 IBM Tivoli Provisioning Manager Version 7. If the following line exists in the maximo. Use binary mode to copy the maximo. delete the line: mxe. After backing up the file. proceed to “Updating the remaining host names” on page 225. On the administrative workstation. Navigate to TIO_HOME\lwi\runtime\tpm\eclipse\plugins\tpm_pmp\properties and back up the existing maximo. go to TIO_LOGS/rename_host and open the tpmChangeDBHost_status.properties file. Navigate to MAXIMO_HOME\maximo\applications\maximo\properties and back up the maximo. you may see leading and trailing control characters in the file. If necessary. Reboot the provisioning server. Use caution and do not edit the last line or any lines containing symbol characters. restart the database after running the tpmChangeDBHost command. the MAXPROPVALUE table and relevant database configuration parameters. If you encounter any issues when the changing the host name script runs. 3. Do not touch the binary part of the file. update the password for the user to access the database.properties file by replacing the OldHostname with the NewHostname and save your changes. Edit the install. All steps are marked as DONE. 9. Log on to the administrative workstation and navigate to MAXIMO_HOME/etc. 6.properties file.properties file.properties file that you created on the administrative workstation to the TIO_HOME\lwi\runtime\tpm\eclipse\plugins\tpm_pmp\properties directory on the new provisioning server.2000 DB2 If your database is remote.properties file by replacing the OldHostname with the NewHostname and save your changes. or to update the password. it updates the host name of the provisioning server in the following areas: v The MAXPROPVALUE table v 2000 DB2 Local database server only: The DB2 registry. 2. edit the maximo.

navigate to TIO_LOGS/rename_host and open the tpmChangeOtherHost_status. Before you begin Ensure that the following middleware is running before you continue: v The LDAP server and the administrative daemon. You can also check the following files to see the updated information: a. and Tivoli Provisioning Manager for OS Deployment. The password for the database instance user. Open the TIO_HOME/config/dcm.properties file to see the host name of the provisioning server. Open a command window and run the following script from the TIO_HOME/tools/rename_host/ directory: v tpmChangeOtherHost. The web address in the <URL> tag must point to the database host name.Before you continue. see User Account Control Step-by-Step Guide. The password for the resource manager user name for the Agent Manager. the administrative daemon. To validate that the changes were successful. Procedure 1.” Updating the remaining host names Use the script to update the host names for the directory server. 2. WebSphere Application Server. All steps must be marked as DONE. restore the back-up file and redo the changes. remove these characters using a file-conversion utility like dos2unix.xml file. 3. The default password is CDSRMPASS. the software distribution infrastructure. The log lists the status of each step that was completed.log. What to do next Proceed to “Updating the remaining host names. see v “Starting the provisioning server on Windows” on page 133 2008 Select the option Run as administrator for all the commands that you run from %TIO_HOME%\tools. If Maximo fails to start later on. You are prompted for some of the following passwords: Table 28. For details on how to start your LDAP server. Navigate to TIO_HOME\lwi\runtime\tpm\eclipse\plugins\tpm_pmp\properties and ensure the following lines exist in the maximo. and the database server. Component passwords Component WebSphere Application Server DB2 Agent Manager Resource Manager SSL Password The password for theWebSphere Application Server administrator. it picks up from where it left off.properties file with the correct values: Appendix B. Open the TIO_HOME/config/endpoint. Other installation tasks 225 . For more information about user account control in Windows 2008. If the process times out while running the script.cmd Note: This process can take some time. b. v The database server. relaunch the script.

The fully qualified host name for the agent manager query service.xml file for database configuration if database reference points to local hostname.2 Installation Guide .xml file if the directory server is located on the same computer as the new provisioning server. Reconfigure Cygwin so that the Cygwin login function works correctly after the host name change: a. 6. Updates the dcm.Host cdsHome The fully qualified host name for the catalog service. b. Updates the host name in the user-factory. descriptions. This value is case-sensitive.properties and script_unix. If you encounter any issues when the script runs. Add the values to the parameters in the script_win. Updates the host name for the scalable distribution infrastructure. Updates the Tivoli Provisioning Manager for OS Deployment host name. Log on as administrator on the provisioning server.disablequeuemanager=1 mxe. exampleNewHost.com AgentQuery.Host Parameter description The fully qualified host name for the agent manager query service.com Default/Example value exampleNewHost. 4. The agent manager resource manager user name. and example values are provided here. Parameters for scripts for Windows and UNIX computers. back up and then delete the files in the /etc/passwd and /etc/group directories.conf and tivoli. Results When you run the host name script. This value is case-sensitive.conf files. the following tasks are completed: 1. 5.rmi. Dynamic content delivery installation directory. Parameters for the host name rename feature Various parameters are required for each of the scripts that are used in changing the host name.properties files Parameter name AgentManagerQuery. Run the following commands: mkpasswd -l > /etc/passwd mkgroup -l > /etc/group /usr/bin/ssh-host-config 5.ibm.report. Table 29.donotrun=ALL mxe.ibm.enabled=0 4. Updates the host name for WebSphere Application Server ND. Restart the IBM Tivoli Provisioning Manager server.ibm.receive. use the default. 3.mxe. CatalogueService. Unless you have changed this user name after the installation. view the potential problems and log files so that you can resolve the issue and continue.Host exampleNewHost. 2.com amPort amUser 9511 tpmManager v C:\Program Files\ibm\Tivoli\CDS\ 226 IBM Tivoli Provisioning Manager Version 7. This value is case-sensitive. The agent manager public registration port. Changes the host name in the tivoli.birt. c. A complete list of the parameters.send. At a Cygwin prompt. What to do next Proceed to “Return codes” on page 227. tpmManager.crontask. The IBM Tivoli Provisioning Manager new installer creates the user name.

properties files Parameter name CertManagement.ibm. Table 30. on a separate computer than the provisioning server. The HTTP server home directory. dmgrSoapPort fqNewHostName The deployment manager SOAP port. Add the values to the parameters in the script_win. Other installation tasks 227 . The specified LDAP type that is in use.Table 29. exampleNewHost. WebSphere Application Server administrator user. This value is case-sensitive. The new fully qualified host name for the IBM Tivoli Provisioning Manager. change the value to the correct port number.properties and script_unix.com tpmfosdDataDir The directory where the Tivoli Provisioning v C:\tpmfosd files Manager for OS Deployment configuration.com fqOldHostName exampleOldHost. List of return codes Code 12005 16000 Description Reorganizing the dynamic content delivery database failed. This value is case-sensitive. on the same computer as the provisioning server. Appendix B. 2000 DB2 ctginst1 dbHome dbPort The local database directory. v dbIsRemote Default/Example value exampleNewHost. v 8879 2000 DB2 Oracle 2000 50005 1521 examplenewhost. v Specify yes if the database server is remote. and must contain only lowercase characters. TrustedCertificateQuery. This value must be specified. If you do not have this installed.Host Parameter description The fully qualified host name for the agent manager certification manager. C:\Program Files\ibm\SQLLIB v If you have configured DB2 with a different port.ibm. v Specify no if the database server is local.Server.ibm.Host The fully qualified host name for the agent manager trusted certificate query service. This value is NOT case-sensitive.com wasCellName wasUser ctgCell01 wasadmin Return codes Review the list of return codes for information about how to resolve any problems during the host name change.ibm. exampleNewHost.ibm. A generic error occurred in the hostname rename process. logs.com httpServerHome ldapType v C:\Program Files\IBM\HTTPServer v ITDS v MSAD v MAXIMO Registration. See the step details to resolve the issue. The old fully qualified host name for the IBM Tivoli Provisioning Manager.Host The fully qualified host name for the agent manager registration server. and image files are located. or the database client directory if the database is remote. you can remove the parameter. This value is case-sensitive. The database host port. This value is case-sensitive. The WebSphere Application Server cell name. Parameters for scripts for Windows and UNIX computers (continued).com dbInstanceName 2000 DB2 ctginst1 The database instance name v Indicate the location of the database server.

List of return codes (continued) Code 16001 Description No script name has been provided for tracking. Changing the DB2 host name failed. The required version is '%FEATURE_VERSION%'. Log out and log in as '%runasuser%' and run the script again. The user name for the database cannot be determined. put the file compression utility in the PATH variable. A file compression utility is either not installed or the compression executable path is not included in PATH variable. The '%SETUPCMD%' script cannot be run. There is an unsupported database type '%DB_TYPE%'. The '%LaunchTitle%' must be run as the '%runasuser%' user. The host name rename process is not supported for this operating system. See the information center for details.xml file must be set to 'db2jcc' or 'ORACLE'. See the information center for details. Option "%~1" is not valid. Fix the error and try again. The host name rename process cannot be performed on the current version '%VERSION%'. Option "%~1" is missing a value. Check the usage syntax and try again. Check the code syntax if this error is reported. The '%DEST_DIR%' directory cannot be located. Unable to find the product version for Tivoli Provisioning Manager in the '%TIO_HOME%/config/build-version.xml file. The host name rename process is not supported for this Linux architecture.Table 30. Check the 'name' value under the TIO_HOME/config/dcm. Set it to 'ansi'. The TIO_LOGS environment is not defined so the process logs will be stored in the %TMP% directory. Unable to determine the product version of Tivoli Provisioning Manager. Check the ’username’ value under the TIO_HOME/config/dcm. Run the script as the tioadmin user and try again. See the information center for details. The TERM variable is not properly set. The Tivoli Provisioning Manager environment might be corrupted.2 Installation Guide 16002 16003 16004 16005 16006 16007 16009 16011 16012 16013 16015 16017 16018 16019 16021 16022 16025 16027 16028 16036 16040 16045 16046 16047 228 . See the information center for details. Ensure that all the "TrackBatch" calls in the '%LaunchTitle%'includes a script name and try again. Use the 'chmod +x' command to execute this script.properties' file. The user must belong to the '%TIOADMIN_GRP%' group to do the installation. The '%TIO_LOG%' value of the TIO_LOG variable must be defined as a valid directory. Check the directory path. See the information center for details. The 'type' value under the TIO_HOME/config/dcm. See the information center for details. See the information center for details. 'xterm' or 'vt100'. The '%DEST_DIR%' directory cannot be created because of the %ERRLEVEL% code. Reserved error for internal messages about invalid script tracking. The TIO_HOME environment must be defined. The database name cannot be determined. Cannot find the '%SETUPCMD%' file. Check the usage syntax and try again. Assign the user to the group and try again. Changing the Oracle Database host name failed. IBM Tivoli Provisioning Manager Version 7.xml file.

Table 30. Failed to update tivoli. They must be replaced with actual values without brackets in the '%PropertyFile%' file.receive. Other installation tasks 229 . Set the zipBackupFiles file to false in the '%PropertyFile%' file. A user has selected to exit the current process to change the input parameters. Failed to register the dynamic content delivery service.send. Restarting Tivoli Provisioning Manager for OS Deployment failed.conf file. The script input arguments are missing or invalid. Failed to update tec-event-customer-info. Changing the WebSphere Application Server host name failed.properties.properties file. run the script again and then perform a manual compressed file on the backup files. Appendix B.xml file.xml file. Failed to update the config. List of return codes (continued) Code 16048 16049 16050 16051 16052 16053 16054 16055 16057 16058 16059 16060 16061 16062 16063 16064 16065 16066 16067 16068 16069 Description Updating the database Maximo properties failed. Failed to update tivoli. Failed to find the file with the DB2 configuration file path. Failed to update the tpm-cds-authentication. Failed to open the temporary file. '%EXPECTING%' options include bracketed default values.conf file. Failed to open the target file. Failed to update endpoint.csv file. The default compressed file utility cannot be located in the Tivoli Provisioning Manager installation. Failed to update the user-factory. Changing the Tivoli Provisioning Manager for OS Deployment host name failed. Failed to update the dcm. Updating the Agent Manager host name failed.xml file.

Ensure that no other database clients are accessing the database and run the script again. Ensure that the user name and password are valid and run the script again. Failed to update the information center host name.xml to create the Tivoli Provisioning Manager for OS Deployment boot server object. In tpmfosdbootserver. Failed to drop the database temporary function.xml. 4. The host name value returned by the 'hostname' command is different than the new Tivoli Provisioning Manager fully qualified host name. Verify that the ctginst1 database is started. Ensure there is enough disk space and correct any issues reported. Ensure that no other database clients are accessing the database and run the script again. Ensure that no other database clients are accessing the database and run the script again. List of return codes (continued) Code 16077 Description Failed to import tpmfosdbootserver.xml file To resolve the error: 1.cmd or fails to create the parent OS deployment server on the provisioning server using the data in tpmfosdbootserver. This value is case-sensitive. Check the values and ensure that they match. Correct the issue and run the script again. Failed to drop the database temporary table. Failed to connect to database.Table 30. Unable to find the fully qualified Tivoli Provisioning Manager old host name from the TIO_HOME/xml/tpmserver. 16078 Unable to find the fully qualified new Tivoli Provisioning Manager host name from the TIO_HOME/lwi/runtime/tpm/eclipse/plugins/tpm_pmp/ properties/maximo. When you have performed all the previous steps. Failed to drop the original database schema.properties file. This error occurs when the script tpmChangeOtherHost.xml file. The host name checking failed. verify that the host-server attribute is either the short host name or fully qualified domain name of the provisioning server. The host name checking failed.cmd or to continue with the migration. Correct any reported issues and run the script again. run tpmChangeOtherHost. This value is case-sensitive. The source of the failure might be: v Problems with database connectivity v Incorrect data in the database v An invalid tpmfosdbootserver.2 Installation Guide .xml. Verify that the name of the Tivoli Provisioning Manager server object in the data model is either the short host name or fully qualified domain name of the provisioning server. Failed to copy the database schema. Failed to drop the database temporary stored procedure. 16079 16086 16087 23003 23004 23005 23006 23007 23008 23009 23010 230 IBM Tivoli Provisioning Manager Version 7. 2. Failed to create %NEW_DB_NAME% database [DB2 Return Code=%RETURNCODE%][Error Description=%RETURN_MSG%]. 3. Failed to restore %TC_DB% database [DB2 Return Code=%RETURNCODE %][Error Description=%RETURN_MSG%]. Correct the issue and run the script again.

Failed to update the property value in the database MAXPROPVALUE table. Failed to process the CDB schema during the database restore. Ensure that no other database clients are accessing the database and run the script again. Verify and correct the database system configuration and run the script again. Verify and correct the state of the database and run the script again. Contact IBM Support. Failed to stop the Database Administrator Server. Failed to open exported registry file. Failed to start the Database Administrator Server. Verify and correct the state of the database and run the script again. Failed to get the database admin configuration.xml file and run the script again. Ensure that there is enough disk space and correct any reported issues. Contact IBM Support. Failed to get the property value from the database MAXPROPVALUE table. Failed to install the database schema renaming stored procedures. Contact IBM Support. Check the reported issues and run the script again. Verify and correct the state of the database and run the script again. Check the tmp_ prefixed. Failed to open the file for registry import. Failed to alter the database buffer pool. The script input arguments are missed or they are not valid. Contact IBM Support. Appendix B. REGEDIT failed to import the DB2 registry from the file. contact IBM Support. Verify and correct the database issue reported and run the script again. Other installation tasks 231 . Verify and correct the database issue reported and run the script again. Failed to set the database parameter. 23020 23021 23022 23023 23024 23025 23026 23027 23028 23029 23030 23031 23032 WebSphere Application Server tasks WebSphere Application Server See the following topics for more information about WebSphere Application Server. Failed to back up the %TC_DB% database.Table 30. Failed to update database admin configuration. Validate the database user in the TIO_HOME/config/dcm.log files in the tmp or temp directory for error messages. If the problem persists. Failed to extract and save the path to the database configuration files. Check for the validity of all input parameters. Verify and correct the database system configuration and run the script again. Failed to update the database configuration. The table aliases in the CDB schema do not match with the expected list. REGEDIT failed to export DB2 registry to the file. List of return codes (continued) Code 23011 23013 23014 23015 23016 23017 23018 23019 Description Failed to drop the database temporary schema. Failed to start the database manager.

Credentials are encrypted using FIPS-compliant algorithms. the following services are used for connections: v RXA. FIPS-compliant SSL for the Common Agent Services If FIPS 140-2 compliance is enabled. for the ping command v SCP. Standard 140-2 specifies requirements for cryptography modules. Procedure To verify the installation of WebSphere Application Server. the Java virtual machine is configured to use compliant providers. When FIPS 140-2 compliance is enabled. which uses SMB and SSH protocols. The following protocols are supported: v File Transfer Protocol (FTP) and Telnet v ICMP. FIPS 140-2 cryptographic services for credentials in a service access point. SCP. for secure remote access v SNMP. These modules are validated for FIPS 140-2 compliance. Tivoli Provisioning Manager support for FIPS 140-2 includes: Centralized cryptographic module using FIPS 140-2 compliant providers For FIPS 140-2 compliance. Services are provided by the operating system or additional utilities and software applications. WebSphere Application Server integrates cryptographic modules including Java Secure Socket Extension (JSSE) and Java Cryptography Extension (JCE).bat Compliance with Federal Information Processing Standard 140-2 A Federal Information Processing Standard (FIPS) is a standard issued by the United States National Institute of Standards and Technology (NIST) for federal government computer systems. 232 IBM Tivoli Provisioning Manager Version 7. FIPS-compliant connections to UNIX computers that do not have the common agent. these services must be run in FIPS mode. Use of compliant signature and encryption algorithms is also configured. For more information about these standards. v SSH. credentials for the service access point are required for snmp-set and snmp-get operations. If the SNMP protocol is used. For running commands locally on managed computers. using a version of the cryptographic library that has been FIPS 140-2 certified. so an alternative FIPS-compliant SSH product must be used. The agent manager and common agent configuration provides: v FIPS-compliant SSL from agent shell server in the deployment engine to the common agent. This tool is located in the app_server_root/firststeps directory. for secure remote transfer of a file from one computer to another using the SSH protocol v SSH. and Telnet using scriptlets. see the National Institute of Standards and Technology. OpenSSH is not FIPS 140-2 compliant.2 Installation Guide . for queries and configurations. Run the appropriate file for your operating system: v firststeps. You can view the validation information on the NIST Web site. use the First Steps tool. the agent manager and the common agent are configured to use FIPS certified Java providers. The deployment engine runs provisioning workflows against managed computers using a combination of protocols and credentials. SMB uses the NT LAN Manager authentication protocol which is not FIPS-compliant. FIPS 140-2 compliance is only available for new installations of Tivoli Provisioning Manager.Verifying the installation of WebSphere Application Server Use the First Steps tool to verify the installation of WebSphere Application Server.

com/software/brandcatalog/ismlibrary/details?catalog. job management service federator. The SMB protocol is used for discovery operations on Windows computers and is available in a FIPS-enabled environment. the variable name matches the name of an environment variable that is set in the operating system.v FIPS-compliant SSL from the common agent to the agent manager. The following variables are used to represent installation and other directory paths. Typically. DCD_HOME DMS_HOME ECLIPSE_HOME HTTP_HOME ITM_HOME Tivoli Provisioning Manager for dynamic content delivery The device manager service installation directory Eclipse IBM HTTP Server Tivoli Monitoring agent v %Program Files%\IBM\tivoli\CDS v C:\Program Files\ibm\DeviceManager Defined by the user. For more information. The following product components are not FIPS-compliant: v Tivoli Provisioning Manager for OS Deployment. the following limitations apply in a FIPS-enabled environment: For Windows computers that do not have the common agent: v SMB connections provided by RXA are not FIPS-compliant. the system drive is C. Path variables Path variable AM_HOME APDE_HOME DB2_HOME Component The agent manager Automation Package Developer Environment DB2 Default directory v C:\Program Files\IBM\AgentManager APDE_HOME/eclipse v SystemDrive:\Program Files\IBM\SQLLIB SystemDrive is the disk drive that contains the hardware-specific files used to start Windows. v C:\Program Files\IBM\HTTPServer v C:\ibm\tivoli\ITM Appendix B. To make an SSH connection compliant. v The OpenSSH package included with Cygwin is not FIPS compliant.ibm. and dynamic content delivery service management center. you must install a FIPS-compliant SSH product. For example. Other installation tasks 233 . TIO_HOME represents the environment variable: v %TIO_HOME% Table 31. Integration with Tivoli Provisioning Manager for OS Deployment is not supported when FIPS compliance is enabled in Tivoli Provisioning Manager.label=1TW101084. v IBM Tivoli Monitoring Agent. Installation directories and other paths This topic provides information about installation directories and other path variables. Limitations Due to limitations of some software components used by Tivoli Provisioning Manager. see the white paper Tivoli Provisioning Manager: FIPS 140-2 Enablement in the Integrated Service Management Library at http://www-01. In some cases. The Tivoli Provisioning Manager for OS Deployment interface is not accessible when FIPS compliance is enabled.

Table 31. installed by the Tivoli Provisioning Manager installer: v %COMMONPROGRAMFILES%\IBM Tivoli Child servers.2 v C:\Program Files\IBM\tivoli\tpm v C:\Program Files\IBM\tivoli\common\COP\ logs When logged on as Administrator. Path variables (continued) Path variable JAVA_HOME Component Java Runtime Environment Default directory v For Automation Package Developer Environment. C:\Documents and Settings\Administrator\ Local Settings\Temp v C:\Program Files\IBM\WebSphere\ AppServer WAS_HOME WebSphere Application Server 234 IBM Tivoli Provisioning Manager Version 7. WAS_HOME/java MAXIMO_HOME MWI_workspace Oracle 2000 The base services Middleware installer directory Tivoli Provisioning Manager for OS Deployment data directory v C:\IBM\SMP v C:\ibm\tivoli\mwi\workspace Default data directory for Tivoli Provisioning Manager for OS Deployment parent servers: v %SYSTEMDRIVE%\tpmfosd files OSD_DATADIR Default data directory for Tivoli Provisioning Manager for OS Deployment child servers: v Oracle 2000 %SYSTEMDRIVE%\TPMfOSd Files OSD_HOME Tivoli Provisioning Manager for OS Deployment installation directory Parent servers. installed by the Tivoli Provisioning Manager for OS Deployment workflows: v TCA_HOME TDS_HOME TIO_HOME TIO_LOGS %TEMP% common agent Tivoli Directory Server Tivoli Provisioning Manager Tivoli Provisioning Manager runtime logs Windows directory for temporary files %COMMONPROGRAMFILES%\IBM Tivoli v C:\Program Files\tivoli\ep v C:\Program Files\IBM\LDAP\V6.2 Installation Guide . APDE_HOME\java\jre. For example: – C:\APDE\java\jre v For IBM Tivoli Provisioning Manager.

program. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. 2010 235 . to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. program. The furnishing of this document does not grant you any license to these patents. therefore. this statement may not apply to you. in writing.S. 1623-14. contact the IBM Intellectual Property Department in your country or send inquiries. in writing. or service that does not infringe any IBM intellectual property right may be used instead. Some states do not allow disclaimer of express or implied warranties in certain transactions. EITHER EXPRESS OR IMPLIED. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.A. NY 10504-1785 U. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Any reference to an IBM product. Consult your local IBM representative for information on the products and services currently available in your area.A. IBM may not offer the products. You can send license inquiries. to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. For license inquiries regarding double-byte (DBCS) information. However. This information could include technical inaccuracies or typographical errors. Any functionally equivalent product. or service may be used. Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND. BUT NOT LIMITED TO.Notices This information was developed for products and services offered in the U. Changes are periodically made to the information herein. Shimotsuruma. or features discussed in this document in other countries. or service is not intended to state or imply that only that IBM product. services. it is the user's responsibility to evaluate and verify the operation of any non-IBM product. program. © Copyright IBM Corp. program. IBM may have patents or pending patent applications covering subject matter described in this document. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. or service. 2003.S. INCLUDING. these changes will be incorporated in new editions of the publication.

A. Intel Centrino. and the Windows logo are trademarks of Microsoft Corporation in the United States. The sample programs are provided "AS IS". including in some cases payment of a fee. compatibility or any other claims related to non-IBM products. using. Trademarks IBM. IBM shall not be liable for any damages arising out of your use of the sample programs. registered in many jurisdictions worldwide. or both. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement. and/or other countries.. modify. Information concerning non-IBM products was obtained from the suppliers of those products. without warranty of any kind. Such information may be available. and distribute these sample programs in any form without payment to IBM. Intel. the Adobe logo. TX 78758 U. Linux is a registered trademark of Linus Torvalds in the United States. You may copy. which illustrate programming techniques on various operating platforms.ibm. IBM International Program License Agreement or any equivalent agreement between us. Other product and service names might be trademarks of IBM or other companies.com/legal/copytrade. Intel Inside. Intel Inside logo. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www. Intel logo. Intel SpeedStep. PostScript. and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States. other countries. for the purposes of developing. Windows.2 Installation Guide . Windows NT. marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. or both. Celeron. Intel Xeon. 236 IBM Tivoli Provisioning Manager Version 7. Adobe. cannot guarantee or imply reliability. IBM. subject to appropriate terms and conditions. IBM has not tested those products and cannot confirm the accuracy of performance.shtml. their published announcements or other publicly available sources. COPYRIGHT LICENSE: This information contains sample application programs in source language.S.com are trademarks or registered trademarks of International Business Machines Corp. the IBM logo. and ibm. other countries. serviceability.Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged. and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Intel Centrino logo. should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin. These examples have not been thoroughly tested under all conditions. or function of these programs. therefore. Microsoft. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Itanium.

Notices 237 . and is registered in the U. Patent and Trademark Office. and a registered community trademark of the Office of Government Commerce.S. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Other product and service names may be trademarks of IBM or other companies. UNIX is a registered trademark of The Open Group in the United States and other countries.ITIL is a registered trademark.

238 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide .

Index Numerics 1. 178 uninstalling 144 Creating MEA registation 113 CTGIN9077E error 152. 15 operating system 13 components Tivoli Provisioning Manager 2 © Copyright IBM Corp. 2010 G groups creating 217 H hardware allocating 9 hardware requirements installation 9 host name prerequisites completing the property file property file parameter values 221 scripts parameter values 221 221 239 . 197 recovery from failure 179 troubleshooting overview 168. 2003. 193 custom installation 25 installing silently 207 CWLAA6003 165 Cygwin installing 208 fails without download site 198 first discovery failure 198 missing tools 198 uninstalling 208 dynamic content delivery troubleshooting install fails because Java not found 187 uninstalling 143 A administrative workstation 6 administrative workstationbacking up 132 agent manager unistalling 143 authentication service 82 E EAR files 112 enabling RXA tracing 167 error CTGIN2381E 162 error CTGIN2489E 162 error messages core components recovery from failure 179 error CTGIN22521I 161 installation after uninstalling Websphere Application Server 183 base services 161 invalid directory name 185 errors return codes for migration 227 B base services installation troubleshooting fails to validate 164 fails without deployment engine 162 invalid LDAP names 159 overview 159 recovering from problems 160 removing 146 troubleshooting broken link 167 binding LDAP directory 158 browser configuring for FIPS 140-2 compliance 133 browser requirements installation 15 F FDCC Microsoft Windows Vista COPCOM618E 199 Federal Information Processing Standard browser configuration for standard 140-2 133 standard 140-2 232 FIPS See Federal Information Processing Standard firewalls required ports 16 D database upgrade errorMaximo 162 DB2 BIND commands 184 installing client 50 server 49 troubleshooting database error during installation 153 install failure from mismatched names 153 remote connection hangs on multiprocessor computer 189 DB2 client uninstallation 145 default installation 205 installing silently 207 Dependency checker Core components installation 188 deploying EAR files 113 deployment engine 159 deployment engine failure 166 device manager service uninstalling 141 directories default values 233 DVD disk 1 188 C CCMDB CWLAA6003 165 changing host 220 name 220 changing the host name database server updating the host name 224 scripts parameters for the new computer 226 commands BIND FDCC 184 compatibility installation 1 compliance Federal Information Processing Standard 140-2 232 component requirements installation 12.3 Back up WebSphere Configuration 152 components (continued) verifying after installation 214 configure Virtual Member Manager 75 configuring LDAP server for user authentication only 135 configuring VMM 75 core components error messages recovery from failure 179 installing 119 Cygwin 188 error when creating agent manager profile 180 hangs in Cygwin 183.

111 LDAP server migrating passwords 219 upgrading passwords 217 Linux troubleshooting editing files changes permissions 189 log files troubleshooting information 201 web components troubleshooting process solution installer 194 logging off the provisioning server 216 logging on error when using login window manager 156 provisioning server 215 P passwords device manager service FDCC 167 provisioning server password 221 required for changing the host name 221 rules 21 updating after migration 219 updating after upgrade 217 path variables 233 ports required 16 post-installation configuration 131 preinstallation checklist 5 prerequisite 36. 93 Tivoli Provisioning Manager core components 119 instance names rules 21 IP addresses installation requirements 16 M Manually building EAR files 112 Manually deploying EAR files 113 Maximo authentication 75 Maximo business objects 164 MEA registration 113 Microsoft Active Directory installing 59 middleware 29. 197 recovery from failure 179 troubleshooting 168 Cygwin fails without download site 198 first discovery failure 198 missing tools 198 DB2 database error 153 failure from mismatched names 153 DB2 client 50 DB2 server 49 dynamic content delivery failure because Java not found 187 error messages after uninstalling Websphere Application Server 183 base services 161 invalid directory name 185 fails with agent manager 181 Microsoft Active Directory configuration error 155 incorrect certificate value error 156 middleware for migration 29 insufficient disk space error 152 middleware troubleshooting 151 operating systems and middleware 12 other problems troubleshooting 200 Reflection X failure from unrecognized font 186 requirements 5 requirements for browsers 15 requirements for components 12. 15 installation (continued) requirements for operating system 13 supported topologies 6 Tivoli Directory Server cannot write files to home directory 155 Tivoli Provisioning Manager failure with terminal server enabled 189 recovery steps 201 types 3 web components hangs in Cygwin 183. 93 prerequisites checking automatically 6 prerequisites scanner running 6 provisioning server 220 provisioning server restarting on Windows 211 starting after installation on Windows 133 starting on Windows 211 240 IBM Tivoli Provisioning Manager Version 7.2 Installation Guide .host names changing database server 224 installation requirements 16 migrating components 225 provisioning server 222 I IBM Agent Controller installing and uninstalling 207 installation 29. 93 installing insufficient disk space error 152 uninstalling 146 middleware configuration base services installation validation 164 middleware installation 152. 36. 193 Error configuring database 156 migration return codes 227 missing XML 156 monitoring agent for Tivoli Provisioning Manager installing 207 N networking antivirus software installation requirements 16 installation requirements 16 O operating systems combinations middleware 12 out of sync 164 L launchpad links do not work 152 starting 29. 197 node agent error 194 removing default installation 190 restoring the provisioning server 192 troubleshooting 190 WebSphere Application Server invalid domain name suffix 187 verifying 232 installation directories 233 installation DVDs 23 installation images 23 installation process 3 installing 82 custom installation problems 168 Cygwin 208 default installation problems 173 prerequisite software products 36. 59 base services fails without deployment engine 162 invalid LDAP names 159 troubleshooting 159 cannot connect to database server 154 cannot connect to Tivoli Directory Server 154 cannot install agent manager and Tivoli Common Agent on same provisioning server 183 core components error when creating agent manager profile 180 hangs in Cygwin 183.

provisioning server (continued) stopping on Windows 211 R recovering deployment engine 159 reinstalling Tivoli Provisioning Manager 150 removing the deployment engine 166 requirements antivirus software 16 firewalls 16 host names 16 installation media 16 IP addresses 16 multibyte text 16 networking 16 ports 16 remote configuration 16 SSH 16 X session 16 runtime 164 RXA tracing 167 S scalable distribution infrastructure 137 security Federal Information Processing Standard 140-2 232 setting global variables 137 signing off the provisioning server 216 signing on provisioning server 215 silent installation 207 disk space check 186 exits before completion 185 fails without Cygwin 197 software distribution 137 SSL signer verifying 128 starting Tivoli Provisioning Manager for OS Deployment 213 starting the provisioning server 211 starting the provisioning server after installationon Windows 133 stopping monitoring agent 214 stopping the provisioning server 211 Tivoli Provisioning Manager (continued) uninstalling components 139 Tivoli Provisioning Manager for OS Deployment starting 213 uninstalling 140 Tivoli Provisioning Manager with another product installing 207 Tivoli Provisoning Manager installation failure with terminal server enabled 189 topologies supported for installation 6 troubleshooting Admin mode is slow 199 installation 151 base services 159 core components 168 other problems 200 web components 190 installing base services 160 log files process solution installer 194 troubleshooting information for installation 151 troubleshooting installation middleware 151 W Web Administration Tool installing 217.ear fails 161 invalid domain name suffix 187 not in sync with Maximo business objects 165 WebSphere Application Server tasks 231 Windows XP COPCOM618E FDCC 199 U uninstallation WebSphere Application Server Network Deployment 158 uninstalling agent manager 143 Cygwin 208 DB2 client 145 device manager service 141 dynamic content delivery 143 middleware 146 the base services 146 Tivoli Monitoring agent 139 Tivoli Provisioning Manager 139 Tivoli Provisioning Manager components 139 Tivoli Provisioning Manager core components 144 Tivoli Provisioning Manager for OS Deployment 140 UNIX editing files changes permissions 189 updating administrative workstation 224 updating workstation configuration 224 user authentication configuring LDAP server 135 user names rules 21 users creating 217 T tioadmin installing core components fails Tivoli Directory Server passwords 217. 219 Tivoli Monitoring agent starting 214 uninstalling 139 using 219 Tivoli Provisioning Manager components 2 reinstalling 150 uninstalling 139 179 V Virtual Member Manager 75 Index 241 . 197 node agent error 194 overview 190 restoring the provisioning server 190 log files process solution installer 194 WebSphere Application Server 164 checking status 207 checking version 207 installing verifying the installation 232 troubleshooting deployment of MAXIMO. 219 web components installation restoring the provisioning server 192 installation troubleshooting hangs in Cygwin 183.

2 Installation Guide .242 IBM Tivoli Provisioning Manager Version 7.

.

Printed in USA .