Installing on WebSphere Application Server

Tivoli® IBM Tivoli Asset Management for ITVersion 7.2.2

Installing on IBM WebSphereApplication Server

��

Tivoli® IBM Tivoli Asset Management for ITVersion 7.2.2

Installing on IBM WebSphereApplication Server

��

This edition applies to version 7, release 2, modification 2 of IBM Tivoli Asset Management for IT and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2002, 2010.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

Chapter 1. Introduction . . . . . . . . 1Software components . . . . . . . . . . . 1Hardware and software requirements . . . . . . 3

Chapter 2. Planning to deploy . . . . . 9Administrative workstation . . . . . . . . . 9Deployment topologies . . . . . . . . . . 10Planning for Tivoli middleware worksheet . . . . 12Reusing existing middleware components . . . . 16Planning for the product worksheet . . . . . . 17Planning for security . . . . . . . . . . . 19Planning for port availability . . . . . . . . 20Planning language support . . . . . . . . . 21Configuring SSL between Microsoft Active Directoryand WebSphere Application Server NetworkDeployment . . . . . . . . . . . . . . 22System password policy settings . . . . . . . 26

Chapter 3. Preparing to install. . . . . 27Product media and Launchpads . . . . . . . 27

Starting the Launchpads . . . . . . . . . 29Before you begin . . . . . . . . . . . . 30

Checking port 50000 availability . . . . . . 31Accessing system directories. . . . . . . . 31Disabling the firewall . . . . . . . . . . 31Verifying the required Rational Portfolio Managerbuild package is installed. . . . . . . . . 32Setting the ulimit . . . . . . . . . . . 32Setting the swap size . . . . . . . . . . 32Setting shared memory . . . . . . . . . 33Remote configuration enablement . . . . . . 33Backing up the Deployment Engine database . . 34Preparing UNIX systems for the requiredmiddleware . . . . . . . . . . . . . 35

AIX tar command requirements . . . . . 35Increasing AIX file size and number ofdescriptors . . . . . . . . . . . . 36Increasing AIX paging space. . . . . . . 36Enabling asynchronous I/O on AIX . . . . 37Checking for required libraries on Linux . . 37Configuring the JRE in Linux . . . . . . 38

Chapter 4. Installing middleware. . . . 39Process ID . . . . . . . . . . . . . . . 40Tivoli middleware installer workspace . . . . . 41Tivoli Asset Management for IT middlewaredeployment plan overview . . . . . . . . . 42Options for invoking the deployment plan . . . . 42Installing middleware with the Tivoli middlewareinstaller. . . . . . . . . . . . . . . . 42

Configuring IBM Tivoli Directory Server user andgroup strings . . . . . . . . . . . . . . 55Installing the required middleware silently . . . . 57

Silent middleware installation options . . . . 58Installing middleware on Solaris, HP-UX, and SUSELinux Enterprise Server . . . . . . . . . . 61

Operating system preparation . . . . . . . 61Solaris 10 . . . . . . . . . . . . . 61HP-UX 11i . . . . . . . . . . . . . 61SUSE Linux Enterprise Server 11 . . . . . 62

Installing the middleware components . . . . 62Installing DB2 . . . . . . . . . . . 62Installing IBM Tivoli Directory Server . . . 65Installing WebSphere Application ServerNetwork Deployment . . . . . . . . . 67

Configuring Virtual Member Manager onWebSphere Application Server . . . . . . . 75Configuring the authentication service . . . . 76

Chapter 5. Installation programoverview . . . . . . . . . . . . . . 79Installation prerequisites . . . . . . . . . . 80Tivoli Asset Management for IT simple install pathvalues . . . . . . . . . . . . . . . . 83

Chapter 6. Deploying with automaticmiddleware configuration. . . . . . . 85Performing installation . . . . . . . . . . 86

Chapter 7. Deploying automaticallyreusing existing middleware . . . . . 105Reusing middleware . . . . . . . . . . . 105

Reusing IBM DB2 . . . . . . . . . . . 106Reusing Oracle . . . . . . . . . . . . 107Reusing IBM Tivoli Directory Server. . . . . 107Reusing Microsoft Active Directory . . . . . 107

Performing installation . . . . . . . . . . 109

Chapter 8. Installing with manualmiddleware configuration . . . . . . 129Manually configuring the database server . . . . 130

Manually configuring DB2 9.x . . . . . . . 130Manually configuring DB2 8.2 . . . . . . . 134Manually configuring Oracle 11g . . . . . . 138Manually configuring Oracle 10g . . . . . . 141Manually configuring Oracle 9i Rel2. . . . . 143Manually configuring SQL Server . . . . . 145

Manually configuring the directory server . . . . 147Manually configuring Directory Server . . . . 147Manually configuring Microsoft ActiveDirectory . . . . . . . . . . . . . . 151

Configuring SSL between Microsoft ActiveDirectory and WebSphere Application ServerNetwork Deployment . . . . . . . . 155

© Copyright IBM Corp. 2002, 2010 iii

Manually configuring the J2EE server . . . . . 160Manually configuring Virtual Member Manageron IBM WebSphere Application Server . . . . 161Manually configuring WebSphere ApplicationServer Network Deployment . . . . . . . 164

Manually configuring JMS queues . . . . 164Performing post installation tasks for theapplication server . . . . . . . . . . . 176

Installing IBM Tivoli Asset Management for ITmanually . . . . . . . . . . . . . . . 178

Chapter 9. Verifying the installation 191

Chapter 10. Process solution packageinstallation methods . . . . . . . . 193Software life cycle operations . . . . . . . . 193Process solution packages . . . . . . . . . 194Package types . . . . . . . . . . . . . 195Aggregation packages . . . . . . . . . . 197Determining which process solution installationprogram to use . . . . . . . . . . . . . 197Supported operations for the process solutioninstallation programs . . . . . . . . . . . 198Before using the process solution installationprograms . . . . . . . . . . . . . . . 199Managing process solution deployment from theadministrative workstation . . . . . . . . . 199Typical deployment operation . . . . . . . . 200Selectable features . . . . . . . . . . . . 201Application server and database-relatedconfiguration deferral . . . . . . . . . . 205

Manually completing deployment . . . . . 206Pre-deployment system check . . . . . . . . 207Installing process managers using the processsolution installation wizard. . . . . . . . . 209Process solution installation client command-lineinterface . . . . . . . . . . . . . . . 211

Invoking the process solution installation clientcommand-line interface . . . . . . . . . 211

General syntax . . . . . . . . . . . 211Perform action . . . . . . . . . . . 212Summary of supported parameters . . . . 212

Process solution command-line interfacereference . . . . . . . . . . . . . . 214

showinstalled action - list installed packages 214showavail action - list available packages 215install action - install a package . . . . . 216upgrade action - incrementally update apackage . . . . . . . . . . . . . 216undo action - undo an update to a package 217uninstall action - uninstall a package . . . 218applyfix action - apply interim fix to apackage . . . . . . . . . . . . . 219undofix action - undo an interim fix from apackage . . . . . . . . . . . . . 220showfixes action - list installed fixes for apackage . . . . . . . . . . . . . 220refreshlang action - refresh languages for apackage . . . . . . . . . . . . . 221

showfeatures action - show features of asolution package . . . . . . . . . . 222modfeatures action - modify existing featuresof a deployed package . . . . . . . . 223

Installing and refreshing language support files fora package . . . . . . . . . . . . . . 224

Deployment for packages with a single speciallanguage support feature . . . . . . . . 225Deployment for packages with multiplelanguage support features . . . . . . . . 225

Chapter 11. Installing language packs 227Installing language packs with the Launchpad . . 227Installing language packs with Process SolutionInstaller . . . . . . . . . . . . . . . 228Language deployment after database updatedeferral . . . . . . . . . . . . . . . 230

Manually deploying languages after databaseupdate deferral . . . . . . . . . . . . 230

Chapter 12. Installing IntegrationComposer . . . . . . . . . . . . . 235IBM Tivoli Integration Composer overview . . . 235Hardware and software requirements . . . . . 236Integration adapter data schemas renamed duringupgrading . . . . . . . . . . . . . . 238Installation prerequisites. . . . . . . . . . 239Performing the IBM Tivoli Integration Composerinstallation . . . . . . . . . . . . . . 239

Installing IBM Tivoli Integration Composerusing the Launchpad . . . . . . . . . . 240Installing IBM Tivoli Integration Composer onUNIX operating systems in console mode . . . 242

Confirming the installation . . . . . . . . . 244Post-installation tasks. . . . . . . . . . . 244

Verifying the settings in the IntegrationComposer fusion.properties file . . . . . 244Changing the memory allocation in thestartFusion file (optional) . . . . . . . . 246Changing the memory allocation in thecommandLine file (optional) . . . . . . . . 246

Uninstalling Integration Composer . . . . . . 247Uninstalling Integration Composer on Windowsoperating systems . . . . . . . . . . . 247Uninstalling IBM Tivoli Integration Composeron UNIX operating systems . . . . . . . 248

Chapter 13. Enabling IBM Tivoli AssetManagement for IT for ServiceProviders . . . . . . . . . . . . . 249

Chapter 14. Post installation tasks 253Initial data configuration . . . . . . . . . 253

Signing in using a default user ID . . . . . 254Configuring SMTP . . . . . . . . . . 254Create currency codes . . . . . . . . . 255Create item and company sets . . . . . . . 255Create an organization . . . . . . . . . 256Create a general ledger account component . . 256

iv Installing on WebSphere Application Server

Applying changes to the database . . . . . 257Create a general ledger account . . . . . . 257Update general ledger component typeauthorization . . . . . . . . . . . . 258Create default insert site. . . . . . . . . 258Create a work type . . . . . . . . . . 259Create a classification structure for IT assets . . 259Specify a top-level class for IT assets andsoftware . . . . . . . . . . . . . . 260Signing out and signing in . . . . . . . . 261Manually configuring directory services . . . 261

Before working with BIRT reports . . . . . . 263Tuning IBM DB2 . . . . . . . . . . . . 263Completing integration framework registration . . 265Generating xml request pages . . . . . . . . 266Synchronizing data . . . . . . . . . . . 266Configuring connections to other products . . . 268

Configuring the integration to SoftwareKnowledge Base Toolkit . . . . . . . . . 268

Chapter 15. Installation properties . . 269Updating environment data . . . . . . . . 282

Chapter 16. Troubleshootinginstallation . . . . . . . . . . . . 285General troubleshooting of the product deployment 285

Middleware installation programtroubleshooting feature . . . . . . . . . 289Tivoli middleware installer logs . . . . . . 289Middleware installation program setup scripterror codes . . . . . . . . . . . . . 291Process solution installation logs . . . . . . 292

Encountering error ACUINI0044E . . . . . . . 295Encountering error on a 32 - bit Windows system 296Improper configuration of IBM DB2 or IBM TivoliDirectory Server . . . . . . . . . . . . 296Encountering the CTGIN9042E SOAP connectionproblem . . . . . . . . . . . . . . . 298Encountering error CTGIN9042E . . . . . . . 299Failure when system directories cannot be renamed 301Incorrect db2admin password . . . . . . . . 303DB2 password value not valid. . . . . . . . 304Incorrect idsccmdb user password . . . . . . 306Error CTGIN2371E occurs during installation ofmore than one IBM Service Management producton the same administrative workstation . . . . 307Intermittent error when installing on WebSphereApplication Server 6.1.0.23 . . . . . . . . . 308Error CTG00001 when performing an uninstall . . 308

Chapter 17. Performing multipleproduct installations using oneadministrative workstation. . . . . . 311

Chapter 18. Starting and stoppingmiddleware . . . . . . . . . . . . 313Starting middleware on Windows . . . . . . 313Starting middleware on UNIX . . . . . . . . 314Stopping middleware on Windows . . . . . . 315

Stopping middleware on UNIX systems . . . . 315

Chapter 19. IBM WebSphereApplication Server management . . . 317Starting the MXServer application server from thecommand line . . . . . . . . . . . . . 317Starting the MXServer application server from theadministrative console . . . . . . . . . . 318Securing WebSphere Administrative Console . . . 319Configuring the WebSphere Application Server torun as a Windows service . . . . . . . . . 320Configuring the WebSphere node agent to run as aWindows service . . . . . . . . . . . . 322Creating WebSphere Application Server NetworkDeployment cluster . . . . . . . . . . . 323

Chapter 20. IBM WebSphere PortalServer overview . . . . . . . . . . 325Tivoli Asset Management for IT deployed onWebSphere Portal Server . . . . . . . . . 325

Chapter 21. Uninstalling themiddleware . . . . . . . . . . . . 329

Chapter 22. Uninstalling Tivoli AssetManagement for IT . . . . . . . . . 331Uninstalling an automatically configured TivoliAsset Management for IT deployment . . . . . 331

Running the IBM Tivoli Asset Management forIT uninstallation program for automaticallyconfigured middleware . . . . . . . . . 332

Uninstalling a manually configured IBM TivoliAsset Management for IT deployment . . . . . 333

Running the IBM Tivoli Asset Management forIT uninstallation program for a manuallyconfigured deployment . . . . . . . . . 333IBM Tivoli Asset Management for IT databaseconfiguration recovery . . . . . . . . . 334

Restoring the DB2 database server . . . . 335Restoring the Oracle database . . . . . . 336Restoring the Microsoft SQL Server database 337

Uninstalling the product without the uninstallationprogram . . . . . . . . . . . . . . . 337

Recovering the Deployment Engine . . . . . 338IBM Tivoli Asset Management for IT databaseconfiguration recovery . . . . . . . . . 340

Restoring the DB2 database server . . . . 340Restoring the Oracle database . . . . . . 341Restoring the Microsoft SQL Server database 342

Recovering the Asset Management for ITProcess Manager configuration . . . . . . 343Removing files from the system . . . . . . 345

Uninstalling and reinstalling the DeploymentEngine database . . . . . . . . . . . . 346Uninstalling IBM Tivoli Asset Management for ITsilently . . . . . . . . . . . . . . . 347

Notices . . . . . . . . . . . . . . 349Trademarks . . . . . . . . . . . . . . 350

Contents v

Index . . . . . . . . . . . . . . . 353

vi Installing on WebSphere Application Server

Figures

1. Tivoli Asset Management for IT Components 22. Tivoli Asset Management for IT Deployed in a

Cluster . . . . . . . . . . . . . . 11

© Copyright IBM Corp. 2002, 2010 vii

viii Installing on WebSphere Application Server

Tables

1. List of users and groups created during TivoliAsset Management for IT installation. Planyour value here. . . . . . . . . . . . 12

2. Tivoli middleware installer. Plan your valuehere. . . . . . . . . . . . . . . . 13

3. DB2 configuration. . . . . . . . . . . 134. Oracle configuration . . . . . . . . . 145. SQL Server configuration . . . . . . . . 146. WebSphere Application Server configuration 157. IBM Tivoli Directory Server configuration 158. Microsoft Active Directory configuration 169. Settings for a custom Tivoli Asset Management

for IT installation . . . . . . . . . . 1710. Ports used by Tivoli Asset Management for IT 2111. Middleware object naming conventions 4412. Middleware installation program setup script

error codes . . . . . . . . . . . . . 4713. Profile commands . . . . . . . . . . 6814. Tivoli Asset Management for IT Simple Install

Path Values . . . . . . . . . . . . 8315. Tivoli Asset Management for IT required

users and groups . . . . . . . . . . 150

16. The available process solution installerarchive packages . . . . . . . . . . 194

17. Operations and package types . . . . . . 19618. Process solution operations . . . . . . . 19819. Process solution command-line interface

actions . . . . . . . . . . . . . . 21220. Out-of-the-box data schema names for the

Integration Composer 7.2.2 integrationadapters . . . . . . . . . . . . . 239

21. Login specifications for the Maximo database 24122. Tivoli Asset Management for IT users and

groups . . . . . . . . . . . . . . 25423. Installation properties . . . . . . . . . 26924. Middleware installation program setup script

error codes . . . . . . . . . . . . 29125. Process solution installation logs . . . . . 29226. WebSphere Application Server processes. 31827. Administrative Group Roles and their

descriptions. . . . . . . . . . . . . 32028. Tivoli Asset Management for IT EAR and

WAR files . . . . . . . . . . . . . 325

© Copyright IBM Corp. 2002, 2010 ix

x Installing on WebSphere Application Server

Chapter 1. Introduction

IBM® Tivoli® Asset Management for IT is a comprehensive suite of products that arebuilt on a single, common platform. The product combines enhanced enterpriseasset management functionality with service management capabilities that togetherimprove the effectiveness of asset management strategies.

Tivoli Asset Management for IT includes advanced IT asset management, servicemanagement, and a full-featured service desk, all based on the IT InfrastructureLibrary® (ITIL®) guidelines. The product can be implemented separately as astand-alone solution or deployed with other products. The solution enhances assetmanagement and ensures service performance of production, facility,transportation, and IT assets.

IBM Tivoli Asset Management for IT for Service Providers is an optional, chargeablecomponent that gives a service provider the ability to capture, integrate, andmaintain technical and financial information about customers and their IT assets,from planning, procurement, deployment, and maintenance to end of life anddisposal.

Software componentsIBM Tivoli Asset Management for IT requires multiple software components thatyou can either install on separate, dedicated servers (for best performance), or thesame server. The diagram included in this topic shows a typical Tivoli AssetManagement for IT configuration.

Tivoli Asset Management for IT for Service Providers is a separately licensedcomponent that offers additional features after Tivoli Asset Management for IT forService Providers is enabled.

© Copyright IBM Corp. 2002, 2010 1

Database server

Tivoli Asset Management for IT uses the Maximo® database to store detailsabout the attributes and history of each asset and the details about therelationships between assets.

Application server

Tivoli Asset Management for IT uses Java™ 2 Enterprise Edition (J2EE)technology, which requires a commercial application server, such as IBMWebSphere® Application Server. The application server consists of productapplications that use JavaServer Pages (JSP), XML, and Tivoli AssetManagement for IT-application-specific business components.

HTTP server

A separate, dedicated HTTP server can be configured to work with theJ2EE application server.

Directory server

The directory server is used to secure the Tivoli Asset Management for ITJ2EE application.

The server works with Virtual Member Manager in WebSphere ApplicationServer to provide security within the product.

Administrative systemThe administrative system is the computer to deploy Tivoli AssetManagement for IT from. After the initial deployment, the administrativesystem is used to make updates or changes to the deployment. Changes tothe product deployment typically require that Enterprise Archive (EAR)files be rebuilt, which can only be done from the administrative system.

IntegrationComposerworkstation

JDBC

Directoryserver

Administrationworkstation

Databaseserver

End user with aninternet browser

HTTP

JDBC

HTTP/HTTPS

IBM Tivoli Asset Managementfor IT on IBM WebSphereApplication Server

Figure 1. Tivoli Asset Management for IT Components

2 Installing on WebSphere Application Server

Note: You can install multiple IBM Service Management products from thesame administrative workstation. However, if their base services versionsare not the same, you might encounter the error CTGIN2371E. Go to thesection “Error CTGIN2371E occurs during installation of more than oneIBM Service Management product on the same administrative workstation”on page 307 to read more.

Related concepts

“Administrative workstation” on page 9You install IBM Tivoli Asset Management for IT from a workstation designated asthe administrative workstation. This workstation is where the Tivoli AssetManagement for IT EAR files are built and deployed to the application server.Related reference

“Hardware and software requirements”IBM Tivoli Asset Management for IT consists of a collection of components andproducts that work together to form a powerful resource and process managementsystem.

Hardware and software requirementsIBM Tivoli Asset Management for IT consists of a collection of components andproducts that work together to form a powerful resource and process managementsystem.

The Tivoli Asset Management for IT installation, process manager installation, andmiddleware installation programs install and configure IBM products that make upthe Tivoli Asset Management for IT architecture. Certain IBM products that mightbe already deployed in the enterprise (and that meet minimum release-levelrequirements) can be configured by the product installation programs to be part ofthe Tivoli Asset Management for IT deployment. In some cases, even previouslydeployed products from other vendors can be configured by the installationprograms for use with Tivoli Asset Management for IT.

Prerequisites listed below for non-IBM products were valid at the time thisinformation was published. However, for the most up-to-date information aboutprerequisites for a non-IBM product, refer to that product's documentation.

Important: While Tivoli Asset Management for IT itself supports the Turkishlanguage, the installation program does not support Turkish. Furthermore, theadministrative workstation must not be set to the Turkish locale before or afterinstalling Tivoli Asset Management for IT. After Tivoli Asset Management for IThas been installed successfully, Turkish can be deployed as either the base or as anadditional language using the language pack installation program. Theadministrative workstation must remain set to a non-Turkish locale toaccommodate future product deployment actions.

Tivoli Asset Management for IT supports deployment in IPv6 networks. Themiddleware and product installers can be used in a pure IPv6 environment,provided all the deployment systems support IPv6. If you use an administrativeworkstation that does not support IPv6 natively, for example, Microsoft®

Windows® XP, a hybrid environment that tolerates both IPv6 and IPv4 is required.

To view the components whose hardware and software are described below, referto Figure 1 on page 2.

Browser

Chapter 1. Introduction 3

v Microsoft Internet Explorer 6 or later.v Mozilla Firefox 3 (Windows client)

All computers that run Tivoli Asset Management for IT GUI must haveJava Runtime Environment 1.5 or 1.6 installed.

Database software products

Refer to the database product specifications for supported operatingsystems. For example, see http://www.oracle.com/technology/products/database/oracle10g/index.html for the Oracle databases information.v IBM DB2® Enterprise Edition Version 9.7 for all supported operating

systems and processor architectures, except RHEL 4 and SLES 9 (thisdatabase is installed by the middleware installation program)

v IBM DB2 Enterprise Edition Version 9.7 for Linux®, UNIX®, andWindows, fix pack 3a; it does not support 32-bit Linux

v IBM DB2 Enterprise Edition Version 9.1, Fix Pack 8, on 32-bit Linuxv IBM DB2 Enterprise Edition Version 9.1 for Linux, UNIX, and Windows

Fix Pack 1v IBM DB2 Universal Database™ 8.2 with Fix Pack 14

Note: DB2 8.2 is only supported for manual configuration scenarios.v Oracle Database 11g Release 1

Note: Oracle Database 11g Release 2 is supported as an upgrade. AfterTivoli Asset Management for IT with Oracle Database 11g Release 1 hasbeen installed, you can upgrade Release 1 to Release 2.

v Oracle Database 10g Release 2v Oracle Database 10g Release 1v Oracle Database 9i Release 2.9.2.0.8v Microsoft SQL Server 2008 Standard or Enterprise version.v Microsoft SQL Server 2005 service pack 2 and 3, Standard or Enterprise

version.

Note: If you use Microsoft SQL Server 2005 with Microsoft Windows2008, make sure that you installed service pack 3.

v Microsoft SQL Server 2000 Standard or Enterprise version.

J2EE application server

J2EE is a server where you install WebSphere Application Server andwhere Tivoli Asset Management for IT runs.

Hardware requirements

v 2–4 dedicated processorsv 4GB RAM per processorv 20GB or greater of disk space for Maximo base services and

Java/Web Server components (11GB)

SoftwareThe middleware installation program supports the automateddeployment of middleware on the following platforms, unlessmanual deployment is specified.


http://www.oracle.com/technology/products/database/oracle10g/index.html

http://www.oracle.com/technology/products/database/oracle10g/index.html

v Application server: IBM WebSphere Application Server 6.1.0.23.See also “Intermittent error when installing on WebSphereApplication Server 6.1.0.23” on page 308.

Important: If you are installing WebSphere Application ServerNetwork Deployment 6.1 on SUSE Linux Enterprise Server 11,you need to obtain and apply the product Fix Pack 27, or later.

v HP-UX 11i 3 (on Intel® Itanium® hardware)v IBM AIX® 5L 5.3 (32-bit)v IBM AIX 5L 5.3 (64-bit)v IBM AIX 5L 6.1 (32-bit)v IBM AIX 5L 6.1 (64-bit)v Microsoft Windows Server 2003 (Standard Service Pack 2,

Enterprise, or Datacenter) (on x86-32 hardware)v Microsoft Windows Server 2003 (Standard service pack 2,

Enterprise, or Datacenter) (on x86-64 hardware)v Microsoft Windows Server 2008 Standard Edition, Release 2 (on

x86-64 hardware)v Red Hat Enterprise Linux 4 (on x86-32 hardware)v Red Hat Enterprise Linux 4 (on x86-64 hardware)v Red Hat Enterprise Linux 4 (on zSeries® and System z®

hardware)v Red Hat Enterprise Linux 5 (on x86-32 hardware)v Red Hat Enterprise Linux 5 (on x86-64 hardware)v Red Hat Enterprise Linux 5 (on zSeries and System z hardware)v Sun Solaris 9 (on SPARC processor-based systems)1

v Sun Solaris 10 (on SPARC processor-based systems)2

v SUSE Linux Enterprise Server (SLES) 9 (on System z hardware);SLES 9 is supported, but you must deploy the middlewaremanually if you use SLES 9

v SUSE Linux Enterprise Server (SLES) 10 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 10 (on x86-32 hardware)v SUSE Linux Enterprise Server (SLES) 10 (on x86-64 hardware)v SUSE Linux Enterprise Server (SLES) 11 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 11 (on x86-32 hardware)v SUSE Linux Enterprise Server (SLES) 11 (on x86-64 hardware)v VMWare ESX Server 3

Integration options

Tivoli Asset Management for IT integration components can be runon any operating system supported by the integration software.The following products can serve as integration options for aproduct deployment:v IBM Integrated Solutions Console 7.1.1. It is installed as part of

IBM WebSphere Application Server Network Deployment6.1.0.23.

1. Do not use with IBM DB2

2. Do not use with IBM DB2


v IBM WebSphere Portal Server 6.0 and 6.1.

HTTP serverIBM HTTP Server 6.1 Fix Pack 23 can serve as the HTTP server componentof a deployment. Supported operating systems:v Microsoft Windows Server 2003 service pack 2 (Standard Service Pack 2,

Enterprise, or Datacenter) (32-bit, 64-bit)v Microsoft Windows Server 2008 (Standard Service Pack 2, Enterprise, or

Datacenter) (32-bit, 64-bit)v Microsoft Windows Vista (Business, Enterprise, Ultimate) (32-bit, 64-bit)v Microsoft Windows XP Professional Service Pack 2 (32-bit, 64-bit)v Red Hat Enterprise Linux v4 (Enterprise or Advanced) (update 4+5 or

later) (Intel) (32-bit)v IBM AIX 5L™ 5L 5.3 TL level 5300-06 (64-bit kernel)v IBM AIX 6.1 (64-bit)v SUSE Linux (SLES) 9.0 Enterprise Server System z Service Pack 4 or later

(manual install only)v SUSE Linux (SLES) 10 Enterprise Server System zv SUSE Linux Enterprise Server (SLES) 11 (on System z hardware, manual

install only)v SUSE Linux Enterprise Server (SLES) 11 (on x86-32 hardware, manual

install only)v SUSE Linux Enterprise Server (SLES) 11 (on x86-64 hardware, manual

install only)

Directory server

Software

v IBM Tivoli Directory Server 6.2 fix pack 1v Microsoft Windows Server 2003 Service Pack 2 Active Directoryv Microsoft Windows Server 2008 Active Directory

Microsoft Active Directory Application Mode is not supported.

Operating system

v Microsoft Windows Server 2003 and 2008 (Standard, servicepack 2, Enterprise, or Datacenter) (32-bit, 64-bit)

v Red Hat Enterprise Linux (Enterprise or Advanced) (update 4+5or later) Intel (32-bit)

v IBM AIX 5.3 (64-bit kernel)v IBM AIX 6.1v SUSE Linux (SLES) 9.0 Enterprise Server System z service 4 or

later (manual install only)v SUSE Linux (SLES) 10 Enterprise Server System z (manual

install only)v SUSE Linux Enterprise Server (SLES) 11 (on System z hardware,

manual install only)v SUSE Linux Enterprise Server (SLES) 11 (on x86-32 hardware,

manual install only)v SUSE Linux Enterprise Server (SLES) 11 (on x86-64 hardware,

manual install only)


HardwareFor UNIX, 1GB of space available in the /opt directory.

Administrative system (administrative workstation)

Hardware

By default, the deployment engine is installed in the/usr/ibm/common/acsi directory for UNIX systems, and in theC:\program files\ibm\acsi for Windows.v Intel Pentium® - based processorv PowerPC® 64-bitv Integrated Facility for Linux (IFL)v 2GB RAM of memory (minimum)v To perform a fresh installation of Tivoli Asset Management for

IT:– Using a single server topology

The administrative workstation requires 42GB disk spacewhen the administrative workstation hosts the applicationserver on the same machine. Most installation files can bedeleted at the end of your installation, leaving 10GB diskspace consumed on the administrative workstation

– Using a distributed topologyThe administrative workstation requires 31GB of disk space andthe J2EE application server needs 11GB of disk space. Mostinstallation files can be deleted at the end of the installation,leaving 2GB disk space on the administrative workstation and8GB on the application server.

For AIX systems, ensure that the IATEMPDIR environmentvariable is set to tmp directory.

v SVGA 1024 x 768 resolution; if used for Application Designer1280 x 1024 resolution

Software

v SUSE Linux (SLES) 10 Enterprise Server (x86-32, x86-64, andLinux on System z)

v SUSE Linux (SLES) 11 Enterprise Server (x86-32, x86-64, andLinux on System z)

v IBM AIX 5.3 (32-bit, 64-bit)v IBM AIX 6.1 (32-bit, 64-bit)v Red Hat Enterprise Linux 4 (x86-32, x86-64 processor-based

systems)v Red Hat Enterprise Linux 5 (x86-32, x86-64, and Linux on

System z processor-based systems)v Microsoft Windows Server 2003 Enterprise Edition (x86-32,

x86-64)v Microsoft Windows Server 2008 Enterprise Edition (x86-32,

x86-64)v Microsoft Windows Server 2008 Refresh 2 (x86-32, x86-64)v Microsoft Windows Vista (x86-32, x86-64)v Microsoft Windows XP Professional (x86-32, x86-64)v Microsoft Windows 7 Professional and Ultimate (x86-32, x86-64)


http://www-03.ibm.com/systems/z/os/linux/solutions/ifl.html

v Adobe® Acrobat Reader 6.0 and higher

Note: The Tivoli Asset Management for IT Workflow Designerrequires Java Runtime Environment 5.0 Service Release 5.

Client system

Hardware

v Intel-based Pentium processorv 1GB RAM of memoryv SVGA 1024 x 768 resolution; if used for Application Designer

1280 x 1024 resolution

Software

v Microsoft Windows Vista (Business, Enterprise, Ultimate)(32-bit, 64-bit)

v Microsoft Windows XP Professional Service Pack 2 (32-bit,64-bit)

v Adobe Acrobat Reader 6.0 and higherRelated concepts

“Hardware and software requirements” on page 236Hardware and software requirements for Tivoli Integration Composer“Administrative workstation” on page 9You install IBM Tivoli Asset Management for IT from a workstation designated asthe administrative workstation. This workstation is where the Tivoli AssetManagement for IT EAR files are built and deployed to the application server.“Software components” on page 1IBM Tivoli Asset Management for IT requires multiple software components thatyou can either install on separate, dedicated servers (for best performance), or thesame server. The diagram included in this topic shows a typical Tivoli AssetManagement for IT configuration.


Chapter 2. Planning to deployUse this information to plan your IBM TivoliAsset Management for IT deployment, todetermine the best deployment option foryour environment and business needs. Itallows you to better understand andeffectively plan your topologies.

Administrative workstationYou install IBM Tivoli Asset Management for IT from a workstation designated asthe administrative workstation. This workstation is where the Tivoli AssetManagement for IT EAR files are built and deployed to the application server.

Attention: Run the installation program only from supported operating systemsfor the administrative workstation.

Use the administrative workstation to install program fixes, product upgrades, newapplications, new process managers, and additional language packs. After youcomplete the initial installation and configuration of Tivoli Asset Management forIT, the administrative workstation is not required for daily use. Although nottypically used in day-to-day operations, the administrative workstation is used inall phases of the product life cycle and is an important support component for theproduct.

Important: While Tivoli Asset Management for IT itself supports the Turkishlanguage, the installation program does not support Turkish. Therefore theadministrative workstation must not be set to the Turkish locale before or afterinstalling Tivoli Asset Management for IT. After Tivoli Asset Management for IThas been installed successfully, Turkish can be deployed as either the base or as anadditional language using the language pack installation program. Theadministrative workstation must remain set to a non-Turkish locale toaccommodate future product deployment actions.


Related concepts

“Managing process solution deployment from the administrative workstation” onpage 199Process solution deployment is managed from the Tivoli Asset Management for ITadministrative workstation.“Typical deployment operation” on page 200Process solutions use the IBM Tivoli Asset Management for IT deployment model.In this model, as process solution packages are deployed, database content andmetadata in the package is loaded into the Maximo database and the Maximo coreJ2EE applications are redeployed with Java code provided in the process solutionpackage. It effectively merges the functionality of the process solution package intothe Maximo database and Maximo J2EE application.Related reference

“Hardware and software requirements” on page 3Refer to this link for a list of supported platforms for the administrativeworkstation.

Deployment topologiesA typical deployment lifecycle typically begins with a single-server topology thatwould move through phases of demonstration, functional proof-of-concept, andtesting integration within the existing environment. It then gradually movestowards a pilot multi-server environment before finally implementing a productiondeployment within the enterprise.

There are two primary strategies to deploy IBM Tivoli Asset Management for ITwithin your enterprise.

Single-server (single computer deployment)The single-server topology consists of loading all Tivoli Asset Managementfor IT components onto one computer. This topology is used typically forproof-of-concept purposes, as a demonstration, or as a learningenvironment. For managing enterprise assets and processes, you wouldtypically implement a multi-server topology.

Multi-server (multiple computer deployment)The multi-server topology consists of splitting Tivoli Asset Management forIT components across several different computers. (compare with thefigure). This strategy is beneficial as it optimizes resource use anddecreases the load on each system. This type of deployment would betypical for production use within an enterprise.

When contemplating your deployment strategy, determine whether itincludes systems already established in your network. Implementing byinstalling all new components using the Tivoli middleware and the productinstallation programs simplifies the deployment. If you plan to reuse ormigrate resources that exist in your network, adjust your rollout plan toallow time for things such as bringing the existing resources to versionlevels that are compatible with Tivoli Asset Management for IT.

In a disparate environment, the collection of computers in this deploymentcould be a mixture of Windows and UNIX computers.

Within WebSphere Application Server Network Deployment, you cancreate deployment managers that provide centralized administration ofmanaged application server nodes and custom nodes as a single cell.WebSphere Application Server Network Deployment provides basic


clustering and caching support, including work balancing, automatedperformance optimization, and centralized management and monitoring.

While Tivoli Asset Management for IT requires a new WebSphereApplication Server Network Deployment application server fordeployment, once the product has been deployed, you can add theapplication server used by the product as a new member of an existingcluster. For more information about adding a new member to an existingWebSphere Application Server Network Deployment cluster, refer toAdding members to a cluster.

ctgNode3ApplSrv3

ctgNode2ApplSrv2

ctgNode1ApplSrv1

MAXIMOCLUSTER

WebSphereDeployment Manager

WebSphere Cell (ctgCell01)

Directoryserver

Asset Management for IT application server

Databaseserver

Figure 2. Tivoli Asset Management for IT Deployed in a Cluster

Chapter 2. Planning to deploy 11

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_member.html

Related tasks

“Creating WebSphere Application Server Network Deployment cluster” on page323This section contains information about creating a WebSphere Application ServerNetwork Deployment cluster.Chapter 8, “Installing with manual middleware configuration,” on page 129You can have one or more IBM Tivoli Asset Management for IT middlewarecomponents configured automatically by the installation program. Alternatively,you can choose to manually configure one or more of the middleware servers towork with Tivoli Asset Management for IT. Configure the components before youinstall the product.

Planning for Tivoli middleware worksheetThe tables in this section list the settings for values that you need to supply wheninstalling the Tivoli Asset Management for IT middleware. Although many of thedefaults can be accepted when navigating the panels of the middleware installer,you want to review this worksheet if you plan to configure manually or reuseexisting middleware. In a multi-computer deployment scenario, you might havemultiple values to consider.

Where blanks provided, there are no default values.

Table 1. List of users and groups created during Tivoli Asset Management for IT installation.Plan your value here.

User, description Group or groups, Supported platforms

db2admin.

DB2 administrator. Windows Service user ID.

This user is created by the middleware installer if it doesnot exist.

Windows:DB2USERS, DB2ADMNS

idsccmdb.

IBM Tivoli Directory Server user.


Windows:Users, Administrators

AIX: idsldap

Linux: idsldap, db2grp1

maximo.

Used for Maximo database configuration.

This user is created by the Tivoli Asset Management for ITinstallation program if it does not exist.

Windows:Users, Administrators

AIX: Users, Administrators

Linux: Users, Administrators

Solaris: Users, Administrators

ctginst1.

The system user used as the database instance owner onUNIX platforms. ctginst1 must be a member of db2grp1with secondary groups of staff and dasadm1.


AIX: Users, Administrators

Linux: Users, Administrators

db2fenc1. UNIX system user used as the fenced user ID forDB2.


AIX: db2fgrp1

Linux: db2fgrp1


Table 1. List of users and groups created during Tivoli Asset Management for IT installation.Plan your value here. (continued)

User, description Group or groups, Supported platforms

wasadmin.Note: Not a system user. It is a user ID created for usewith WebSphere Application Server.


v Windows

v AIX

v Linux

v Solaris

Table 2. Tivoli middleware installer. Plan your value here.

Setting Default

Workspace directory (workspace_dir) your_dir\ibm\tivoli\mwi\workspace

Middleware images source directory

Compressed images directory

Uncompressed images directory

Table 3. DB2 configuration.

Setting Default

Installation directory (db2_install_dir)Windows:

system_drive\Program Files\IBM\SQLLIB

Linux, AIX:/opt/IBM/db2/V9.7

DAS userWindows:

db2admin

Linux, AIX:dasusr1

Fenced userLinux, AIX:

db2fenc1

Fenced user group nameLinux, AIX:

db2fgrp1

Fenced user home directoryLinux, AIX:

/home/db2fenc1

Instance name ctginst1

Port 50005

Instance user name home directoryLinux, AIX:

/home/ctginst1

Database instance user IDWindows:

db2admin

Linux, AIX:ctginst1

DB2 administrators groupWindows:

DB2ADMNS

Linux, AIX:db2grp1

DB2 users groupWindows:

DB2USERS


Table 3. DB2 configuration. (continued)

Setting Default

Use same user name and p/w for remaining DB2Services

YES

Database name ctginst1

Configure Tools Catalog NO

This value is relevant for reuse scenarios only.

Enable O/S Security for DB2 objects YES

This value is relevant for reuse scenarios only.

DB2 instance port

Data table space name MAXDATA

Data table space size medium (1000 MB)

DB2 Medium (5000 MB)

Temporary table space name MAXTEMP

Temporary table space size 1000 MB

Table 4. Oracle configuration

Setting Default

Installation directory (oracle_install_dir)Windows:

system_drive\oracle\product\oracle_version\db_1

Linux, AIX, Solaris:/opt/app/oracle/product/oracle_version/db_1

Administrator user ID sys

Oracle Software Owner IDWindows:

Administrator

Linux, AIX, Solaris:oracle

Instance LocationWindows:

This value might beC:\oracle\product\oracle_version\db_1

Linux, AIX, Solaris:This value might be/opt/app/oracle/product/oracle_version/db_1

Oracle database name ctginst1


Data table space size medium (1000 MB)

Oracle Medium (1000 MB)



Table 5. SQL Server configuration

Setting Default

Installation directory (sql_install_dir) ProgramFiles\Microsoft SQL Server\90

Named instance maximo

SQL Server administrator sa


Table 5. SQL Server configuration (continued)

Setting Default

SQL Server administrator password

Port 1433

Database name maxdb71

User ID maximo

User ID password

Data file name maxdb71_dat

Log file name maxdb71_log

Table 6. WebSphere Application Server configuration

Setting Default

Install location (was_install_dir)Windows:

C:\Program Files\IBM\WebSphere\AppServer

Linux, Solaris:/opt/IBM/WebSphere/AppServer

AIX: /usr/IBM/WebSphere/AppServer

WebSphere Application Server administration username

wasadmin

Deployment Manager profile name ctgDmgr01

Application server profile name ctgAppSrv01

Profile directoryLinux, Solaris:

/opt/IBM/WebSphere/AppServer/profiles

AIX: /usr/IBM/WebSphere/AppServer/profiles

Cell name ctgCell01

Deployment Manager node name ctgCellManager01

Application server node name ctgNode01

HTTP server install location(http_server_install_dir) Windows:

C:\Program Files\IBM\HTTPServer

Linux, Solaris:/opt/IBM/HTTPServer

AIX: /usr/IBM/HTTPServer

HTTP port 80Note: On Windows, this port might already be inuse. Ensure that you either free up this port, oruse another port that is unassigned.

HTTP admin server port 8008

HTTP plug-in profile name ctgAppSvr01

Table 7. IBM Tivoli Directory Server configuration

Setting Default

Install locationWindows:

C:\Program Files\IBM\LDAP\V6.2

Linux, AIX:/opt/IBM/ldap/V6.2

Administrator distinguished name cn=root

Organizational unit ou=SWG


Table 7. IBM Tivoli Directory Server configuration (continued)

Setting Default

Organization and country suffix o=IBM,c=US

Directory Server port 389

Directory Server secure port 636

Administration port 3538

Administration secure port 3539

Database name security

Instance name idsccmdb

Instance port 50006

Instance user name idsccmdb

Table 8. Microsoft Active Directory configuration

Setting Default

Directory server port 389

LDAP base entry DC=ism71,DC=com

User suffix CN=Users,DC=ism71,DC=com

Group suffix DC=ism71,DC=com

Organization container suffix DC=ism71,DC=com

Bind distinguished name CN=Administrator,CN=Users,DC=ism71,DC=com

Related reference

“Planning for the product worksheet” on page 17There are tables provided to list the settings whose values you need to supplywhen using the IBM Tivoli Asset Management for IT installation program. Theyinclude default values, and where blank spaces occur, you are prompted to provideyour own values.

Reusing existing middleware componentsYou can reuse some existing middleware installations as IBM Tivoli AssetManagement for IT components. If you plan to do so, ensure that they are at thelevel supported by Tivoli Asset Management for IT. The middleware andinstallation programs do not provide a mechanism for patching unsupportedservers, nor do these programs provide remote prerequisite checks to ensure thatthey are at the right level.

For example, you probably have an instance of IBM DB2 or Oracle in an existingdatabase server farm which already has established access policies, redundancymeasures, and backup plans in place.

Note: When deploying Tivoli Asset Management for IT on SUSE Linux EnterpriseServer 11 reusing the existing middleware, make sure that you use WebSphereApplication Server 6.1.0.27

Middleware configuration options

You are presented with the option of either allowing the Tivoli Asset Managementfor IT installation program to configure middleware automatically, or configuringeach middleware component manually.


Auto-configureThe Tivoli Asset Management for IT installation program automaticallyconfigure middleware to work together with the product. This option isrecommended if you are installing new instances of middlewarecomponents, or if you have existing middleware instances that are notgoverned by policies that restrict programmatic configuration.

ManualYou can manually configure middleware that exists in your environment,or has been installed by the middleware installer. This configuration mustbe completed before running the Tivoli Asset Management for ITinstallation program. If you have policies in place that dictate certainprocedures and guidelines when configuring systems in your environment,you can choose this deployment path.

Related concepts

“Reusing middleware” on page 105If you intend to reuse existing middleware servers with the existing Tivoli AssetManagement for IT, they must be configured before running the installationprogram. This section contains information about configuring existing DB2 andIBM Tivoli Directory Server servers for use with Tivoli Asset Management for ITusing the middleware installer.Related tasks

Chapter 6, “Deploying with automatic middleware configuration,” on page 85The automatic IBM Tivoli Asset Management for IT installation consists ofsubsequent tasks that need to be performed in a specified order. You are guidedthrough the tasks by the Tivoli Asset Management for IT Launchpad.Chapter 7, “Deploying automatically reusing existing middleware,” on page 105This information provides a high-level overview or road map of tasks you need tocomplete in order to deploy IBM Tivoli Asset Management for IT automatically,using middleware already established in your enterprise.Chapter 8, “Installing with manual middleware configuration,” on page 129You can have one or more IBM Tivoli Asset Management for IT middlewarecomponents configured automatically by the installation program. Alternatively,you can choose to manually configure one or more of the middleware servers towork with Tivoli Asset Management for IT. Configure the components before youinstall the product.

Planning for the product worksheetThere are tables provided to list the settings whose values you need to supplywhen using the IBM Tivoli Asset Management for IT installation program. Theyinclude default values, and where blank spaces occur, you are prompted to provideyour own values.

Table 9. Settings for a custom Tivoli Asset Management for IT installation

Setting Default

Installation directory (tamit_install_dir) C:\IBM\SMP

API port 9530

IBM DB2 host name

DB2 port 50005

Maximo database name maxdb71

Maximo database instance ctginst1

Maximo database user ID maximo


Table 9. Settings for a custom Tivoli Asset Management for IT installation (continued)

Setting Default

IBM DB2 installation directory (db2_install_dir)Windows:

C:\Program Files\IBM\SQLLIB

Linux, AIX:/opt/IBM/db2/V9.7

DB2 instance administrator user IDWindows:

db2admin

Linux, AIX:ctginst1

Windows DB2 service user ID db2admin

Oracle installation directory (oracle_install_dir)Windows:

C:\oracle\product\oracle_version\db_1

Linux, AIX, Solaris:/opt/app/oracle/product/oracle_version/db_1

Oracle administrator user ID sys

Oracle software owner user ID oracle

SQL installation directory C:/ProgramFiles/Microsoft SQL Server/90


Data table space size medium

DB2 Medium (5000 MB)

Oracle Medium (1000 MB)

SQL Server (Initial data file size)Medium (1000 MB)



WebSphere Application Server host name

WebSphere Application Server SOAP port 8879

WebSphere Application Server home directory(was_install_dir) Windows:

C:\Program Files\IBM\WebSphere\AppServer

Linux, Solaris:/opt/IBM/WebSphere/AppServer


WebSphere Application Server administration userID

wasadmin

WebSphere Application Server profile name ctgDmgr01

Web server port 80

Web server name webserver1

Node name ctgNode01

Cluster name MAXIMOCLUSTER

Application server MXServerNote: This value cannot be changed.

JMS data source name

JMS database name maxsibdb

JMS server name

Database server port 50000


Table 9. Settings for a custom Tivoli Asset Management for IT installation (continued)

Setting Default

Database user ID MAXADMIN

Directory server host name

Directory server port 389

Directory server administrator DN cn=root

Bind password. See also “System password policysettings” on page 26.

Windows

Maximo installation folder (tamit_install_dir)

C:\IBM\SMP

SMTP server

Workflow Admin e-mail

Admin e-mail

Planning for securityPlanning for security includes choosing a security option, deciding which users canwork with each application in IBM Tivoli Asset Management for IT, and optionallywhich users can work with which assets.

Each service management process defines its own roles. If you install more processmanagers, additional roles for those processes are added.

The roles are based on roles defined in the Information Technology InfrastructureLibrary (ITIL). IBM implements ITIL using IBM Tivoli Unified Process. Refer to theIBM Tivoli Unified Process content for more detailed information about roles andtheir responsibilities.

You need to decide whether to use the roles defined by the service managementprocesses, or define your own.

The roles defined by the processes are implemented as security groups. You canassign each user defined to one or more security groups, which enables them toperform the responsibilities assigned to those roles. You can modify theapplications that members of each security group can use in the Security Groupsapplication.

Choosing a security option

Tivoli Asset Management for IT offers three options for managing your users andtheir memberships in security groups.

When you install the product, you need to choose one of three options formanaging users and groups. This choice applies to all products that you installtogether. If you are installing Tivoli Asset Management for IT with another productalready installed, the choice you made when installing the first product is used forTivoli Asset Management for IT as well.

The security option you choose determines how your system performsauthentication, which is the validation of a user signing in to Tivoli AssetManagement for IT, and authorization, which uses security groups to control whichusers can work with each application.


Choose one of these security options:

Use WebSphere application security for authentication and authorizationChoose this option to automatically configure WebSphere ApplicationServer Network Deployment application security to manage users andgroups for authentication and authorization purposes. This option requiresapplication security to be enabled in WebSphere Application ServerNetwork Deployment before you perform the installation.

Use WebSphere application security for authentication onlyChoose this option to automatically configure WebSphere ApplicationServer Network Deployment application security for authentication onlyand allow Maximo security to manage users and groups. You create allyour users in your directory server, but you manage their membership insecurity groups in the Security Groups application. This option requiresapplication security to already be enabled in WebSphere Application ServerNetwork Deployment.

Use Maximo security for authentication and authorizationIf you do not want to use WebSphere Application Server NetworkDeployment application security, select this option to have Maximosecurity manage users and groups for both authentication andauthorization.

With this option, you cannot configure single sign-on to launch-in-contextto the Software Knowledge Base Toolkit interface. Users will have toprovide separate credentials when they use the launch-in-context feature tolog into the Software Knowledge Base Toolkit.

Configuring security

Configure your security environment by creating users and assigning them tosecurity groups, defining the applications that members of each security group canuse, and optionally by creating access collections, after you have finished installingthe product.Related tasks

“Signing in using a default user ID” on page 254User management is managed through the application server or the directoryserver you have configured to use with Tivoli Asset Management for IT. When firstinstalled, Tivoli Asset Management for IT contains the following default user IDs,which are members of the specified security groups described in this section.“Manually configuring Virtual Member Manager on IBM WebSphere ApplicationServer” on page 161This procedure provides task information for manually configuring VirtualMember Manager (VMM) to secure Tivoli Asset Management for IT.“Manually configuring Microsoft Active Directory” on page 151

Windows You can choose to configure a Microsoft Active Directory resourcemanually for better use with Tivoli Asset Management for IT.“Securing WebSphere Administrative Console” on page 319You can secure the administrative console so that only authenticated users can useit. Virtual Member Manager must have been configured on the WebSphere serverbefore securing the console.

Planning for port availabilityMake sure that you enabled ports in support of the installation and deployment.


A PING command issued from the administrative workstation during installationmust receive a response from each server involved in the deployment. Ensure eachmiddleware host server is configured to respond to PING requests.

Table 10. Ports used by Tivoli Asset Management for IT

Port number Use

389 Directory server port

3538 Directory server admin daemon port

3539 Directory server admin daemon secure port

636 Directory server secure port

50006 Directory server instance port

50000 Database port for directory server. Refer to “Checking port 50000 availability”on page 31 for more information.

8879 SOAP port to IBM WebSphere Application Server Network Deployment. Referto “Encountering the CTGIN9042E SOAP connection problem” on page 298 fortroubleshooting information.

9043, 9044 IBM WebSphere Application Server Network Deployment AdministrativeConsole secure port

9060, 9061 IBM WebSphere Application Server Network Deployment AdministrativeConsole

9443 IBM WebSphere Application Server Network Deployment SSL port

9430, 80 Web Server port

80 (9080) IBM HTTP Server port

1433 Microsoft SQL Server (default)

1521 Oracle (default)

22 SSH

50005 Database instance port

50000 Database server port

9530 Tivoli Asset Management for IT API port

139 This port is used if SMB is configured to run on NetBIOS over TCP/IP. Refer to“Remote configuration enablement” on page 33 for more information.

445 This port is used if SMB is run directly on TCP/IP, without NetBIOS. Refer to“Remote configuration enablement” on page 33 for more information.

Planning language supportLanguage support refers to the languages you plan to support in the Tivoli AssetManagement for IT user interface.

IBM Tivoli Asset Management for IT includes language support for languagessupported by UTF-8 and UCS-2.

When deployed using Microsoft SQL Server, Tivoli Asset Management for IT doesnot support UTF-8. Language support is limited to those supported by the currentWindows system code page. Supported language set choices are either all Latin 1languages and English, or one double-byte character set language and English.

Important: If you plan to add language support to Tivoli Asset Management forIT, you need to use the Tivoli Asset Management for IT language pack installation


program to define the base language to use before you perform post-installationsteps described in Chapter 14, “Post installation tasks,” on page 253. You can addadditional languages at a later date, but the base language must be set eitherduring or directly after the product installation.Related tasks

“Deployment for packages with multiple language support features” on page 225Packages can be deployed with a multiple language support.“Installing language packs with Process Solution Installer” on page 228The Process Solution Installer guides you through the installation of a processmanager product (PMP) or Integration Module. Use the Process Solution Installerto refresh languages to synchronize them with Maximo languages.Chapter 11, “Installing language packs,” on page 227“Generating xml request pages” on page 266Perform this task after you installed Tivoli Asset Management for IT and before yourun request pages. This procedure needs to be performed for every language thatis enabled on your system.“Installing process managers using the process solution installation wizard” onpage 209To install a process solution package into your IBM Tivoli Asset Management forIT instance, you might use the Process Solution Installer wizard.

Configuring SSL between Microsoft Active Directory and WebSphereApplication Server Network Deployment

If you want the IBM Tivoli Asset Management for IT installation program toautomatically create users and groups required by the product when usingMicrosoft Active Directory, you need to configure SSL communication betweenMicrosoft Active Directory and WebSphere Application Server NetworkDeployment. This procedure involves enabling SSL for Microsoft Active Directory,generating a certificate, and then adding that certificate to WebSphere ApplicationServer Network Deployment.

Before you begin

Changing the name or domain of the certificate authority at any point invalidatescertificates previously issued from that authority.

Ensure that you have host name resolution set up properly in yourenvironment. Communication failures occur if the computer hosting MicrosoftActive Directory cannot resolve host names for systems that have been issuedcertificates.

Ensure that you already have installed Microsoft Internet Information Services withASP extensions enabled on the system before configuring the certificate servicerequired for SSL. Microsoft Internet Information Services are a prerequisite of thecertificate service. Microsoft Internet Information Services can be added as aWindows component from the Add/Remove Programs dialog. Add thiscomponent by selecting the Internet Information Services or Application Servercomponent and installing it. If you have IBM HTTP Server installed on the samesystem, you cannot use port 80. If the HTTP Server was configured to use port 80,you need to change it to another value because Microsoft Internet InformationServices must use port 80. Once you verify that these two conditions are met,proceed with setting up certificate services as described in this procedure.


About this task

To configure SSL communication between Microsoft Active Directory andWebSphere Application Server Network Deployment

Procedure1. From the Control Panel of the computer hosting Microsoft Active Directory,

select Add or Remove Programs and then select Add/Remove WindowsComponents.

2. From the Windows Components panel, select the Certificate Services option,and then click Next.

3. From the CA Type panel, select Stand alone root CA, select the Use customsettings to generate the key pair and CA certificate option, and then clickNext.

4. From the Public and Private Key Pair panel, select Microsoft StrongCryptographic Provider for the CSP value, select SHA-1 as the Hashalgorithm, set the Key length to 2048, and then click Next.

5. From the CA Identifying Information panel, enter computer_name.ism71.com inthe Common name for this CA field, enter DC=ism71,DC=com for theDistinguished name suffix, set the Validity period to 5 years, and then clickNext. The values used in this step are example values only. Replace thesevalues with the details of the computer hosting Microsoft Active Directory.

6. From the Certificate Database Settings panel, you can keep the default valueof C:\WINDOWS\system32\CertLog for both the Certificate database andCertificate database log fields, and then click Next. Configuration of thecomponent now begins.

7. Click Finish.8. Reboot the system.9. Launch Internet Explorer.

10. Select Tools → Internet Options → Security and click Sites.11. From the Trusted Sites dialog box, enter http://computer_name.ism71.com in

the Add this Web site to the zone: field, click Add, and then click Close.12. Enter the following address in the browser: http://computer_name.ism71.com/

certsrv

13. From the Certificate Services page, click Download a CA certificate,Certificate Chain, or CRL.

14. From the Download a CA Certificate, Certificate Chain, or CRL page, clickinstall this CA certificate chain. When the task has completed successfully,click the back button.

15. From the Download CA Certificate, Certificate Chain, or CRL page selectCurrent for the CA certificate value, choose Base 64 for the Encodingmethod, and then click Download a CA Certificate.

16. When prompted, specify the type as Security Certificate and save the securitycertificate file as serverRootCA.cer.

17. Launch the Microsoft Management Console.18. Select File → Add/Remove Snap-in.19. From the Add/Remove Snap-in dialog box, click Add.20. From the Add Standalone Snap-in dialog box, select Certificates and then

click Add.21. Select Computer account and then click Next.


22. Select Local computer: (the computer this console is running on) and clickFinish.

23. From the Add Standalone Snap-in dialog box, select Certification Authorityand then click Add.

24. Select Local computer: (the computer this console is running on) and clickFinish.

25. Click Close to close the Add Standalone Snap-in dialog box.26. Click OK on the Add/Remove Snap-in dialog box to close it.27. In the Microsoft Management Console, navigate to Console Root →

Certificates (Local Computer) → Third-Party Root Certification Authorities.28. Right-click Certificates and select All Tasks → Import.29. From the File to Import panel of the Certificate Import wizard, browse to the

location of your serverRootCA.cer file, select it, and then click Next.30. From the Certificate Store panel, select Place all certificates in the following

store, click Next, and then click Finish.31. Using Internet Explorer, navigate to http://computer_name.ism71.com/

certsrv. From the Certificate Services page, click Request a certificate.32. From the Request a Certificate page, click advanced certificate request.33. From the Advanced Certificate Request page, click Create and submit a

request to this CA.34. From the Advanced Certificate Request page, enter the following information

and then click Submit.

Identifying InformationFor the Name field, enter the fully qualified name of the computerhosting Microsoft Active Directory. This value must be capitalizedentirely. In this example, computer_name.ism71.com.

Type of Certificate NeededSelect Server Authentication Certificate.

Key OptionsFor the CSP field, select Microsoft RSA SChannel CryptographicProvider.

Select the Automatic key container name, Mark keys as exportable,and Store certificate in the local computer certificate store options.

For the Key Size field, you can either accept the default value of 1024,or change it to a more appropriate value.

Additional OptionsSet the Request Format option to PKCS10.

For the Hash Algorithm field, select SHA-1.

For the Friendly Name field, enter the same exact value as entered forthe Name field.

Default values are sufficient for the remaining fields on this page.35. Click Home to return to the home page for Certificate Services.36. In the Microsoft Management Console, navigate to Console Root →

Certification Authority (Local) → mycomputer.ism71.com → PendingRequests.

37. In the right pane, right-click the ID of the request, and then select All Tasks →Issue.


38. From Internet Explorer, on the Certificate Services page, click View the statusof a pending certificate request.

39. From the View the Status of a Pending Certificate Request page, click thecertificate request you created.

40. From the Certificate Issued page, click Install this certificate.41. Reboot the system.42. Once the system has rebooted, invoke the Microsoft Management Console and

navigate to Console Root → Certificates (Local Computer) → Personal →Certificates.

43. In the right pane, double-click the entry displayed in uppercase.44. From the Certificate dialog box, ensure you can find the statement You have a

private key that corresponds to this certificate, and then click OK.45. In the right pane, double-click the entry displayed in lowercase.46. From the Certificate dialog box, ensure you can find the statement You have a

private key that corresponds to this certificate, and then click OK.47. Launch the Microsoft LDP utility.48. Select Connection.49. Select Connect.50. Enter computer_name.ism72.com for Server, 636 for Port, select SSL, and then

click OK. Review the information displayed to verify your configurationvalues.

51. Launch the Microsoft Management Console and navigate to Console Root →Certificates (Local Computer) → Personal → Certificates.

52. Right-click the uppercase certificate entry and select All Tasks → Export

53. From the Certificate Export Wizard Welcome panel, click Next.54. From the Export Private Key panel, select No, do not export private key, and

then click Next.55. From the Export File Format panel, select Base-64 encoded X.509(.CER), and

then click Next.56. From the File to Export panel, export the certificate as serverRootCA.cer, click

Next, and then click Finish.57. Right-click the lowercase certificate entry and select All Tasks → Export

58. From the Certificate Export Wizard Welcome panel, click Next.59. From the Export Private Key panel, select No, do not export private key, and

then click Next.60. From the Export File Format panel, select Base-64 encoded X.509(.CER), and

then click Next.61. From the File to Export panel, export the certificate as serverAuthCert.cer,

click Next, and then click Finish.62. Copy serverRootCA.cer and serverAuthCert.cer to the WebSphere

Application Server Network Deployment system.63. Invoke WebSphere Administrative Console.64. From WebSphere Administrative Console, select Security → SSL certificate and

key management.65. Click Keystores and certificates.66. Click CellDefaultTrustStore.67. Click Signer certificates and then click Add.


68. From the Add signer certificate page, enter MSADServerRootCA for the Alias,enter the path (including the file name) to the serverRootCA.cer file in theFile name field, and then click OK.

69. Click Add.70. Enter MSADServerAuthCert for the Alias, enter the path (including the file

name) to the serverAuthCert.cer file in the File name field, and then clickOK.

71. From the WebSphere Administrative Console, select Security → Secureadministration, applications, and infrastructure.

72. From the Available realm definitions drop-down list, select Federatedrepositories, and then click Configure.

73. Click the repository identifier for Microsoft Active Directory listed inRepositories in the realm table.

74. Update the following properties and then click OK.

Port Update this value to 636.

Login propertiesSet this value to cn.

Requires SSL communicationsEnsure that this option is selected.

Use specific SSL aliasEnsure that this option is selected with a value ofCellDefaultSSLSettings.

75. Click Supported entity types and verify that the PersonAccount entity type isset to cn. If it is not set to cn, click the PersonAccount entity type and set itand then save the changes.

76. Restart the domain manager.

System password policy settingsBefore deploying IBM Tivoli Asset Management for IT, be sure that you arefamiliar with the password policies of systems used in the deployment, or youmight experience errors during installation.

For example, Microsoft Windows Server 2008 systems have a stricter set ofpassword requirements than previous versions configured by default. If you arenot familiar with these stronger password requirements, you might experience anerror during the installation of Tivoli Asset Management for IT when creating userson a Microsoft Windows Server 2008 system.

Password values that you provide during the product installation must becompliant with the password policies set for the target system.

Go to the sections “Incorrect db2admin password” on page 303 and “DB2password value not valid” on page 304 to read about potential problems withsystem password policy settings while installing Tivoli Asset Management for ITmiddleware.


Chapter 3. Preparing to install

To prepare to install, review the information about product media, preinstallationconsiderations, overview of the installation procedure, and instructions on usingthe IBM Tivoli Asset Management for IT Launchpads.

Product media and LaunchpadsIBM Tivoli Asset Management for IT ships on a set of DVDs that contain theprerequisite middleware, Quick Start Guide, and the product code. The optional,purchasable components, IBM Tivoli Asset Management for IT for Internal ServiceProviders and IBM Tivoli Asset Management for IT for Service Providers, are alsoshipped on DVDs. Alternatively, you can download the product files containingthese same images from IBM Passport Advantage®. The Launchpads serve ascentralized interfaces for launching a collection of installation programs andproduct information.

The following DVDs contain files for the IBM Tivoli Asset Management for ITproduct components:v IBM Tivoli Asset Management for IT Quick Startv IBM Tivoli Asset Management for IT for Multiplatforms.

This is the main product DVD, which contains the middleware and base servicescode for Tivoli Asset Management for IT, delivered as a Launchpad (see “IBMTivoli Asset Management for IT Launchpad” on page 28)

v IBM Tivoli Asset Management for IT for Service ProvidersThis is an additional DVD, which contains the extensions and enablement keyfor the optional, chargeable component available for managed service providers(see “IBM Tivoli Asset Management for IT for Service Providers Launchpad” onpage 28).

v IBM Tivoli Asset Management for IT for Internal Service ProvidersThis is an additional DVD, which contains the extensions and enablement keyfor the optional, chargeable component available for internal service providers(see “IBM Tivoli Asset Management for IT for Internal Service ProvidersLaunchpad” on page 29).

v Windows Tivoli Middleware Installer Images for Windows Server x86–32

v Windows Tivoli Middleware Installer Images for Windows Server x86–64

v Linux Tivoli Middleware Installer Images for Linux x86–32

v Linux Tivoli Middleware Installer Images for Linux x86–64

v Linux Tivoli Middleware Installer Images for Linux on System z

v AIX Tivoli Middleware Installer Images for AIX PPC-64

v Solaris Tivoli Middleware Installer Images for Solaris SPARC-64

v HP�UX Tivoli Middleware Installer Images for HP-UX x86–64v IBM Tivoli Software Knowledge Base Toolkitv Maximo eCommerce Adapter

The Launchpads assist you in choosing which product component (and in whichorder) to install. They do not support silent installation. Each installation task is


conducted in silent mode directly. Before launching, ensure that you meet themiddleware prerequisites listed in “Hardware and software requirements” on page3. Ensure that you have the correct service pack levels for your environments andalways use fully-qualified domain names when entering values for the installationprogram.

IBM Tivoli Asset Management for IT Launchpad

The options on the Tivoli Asset Management for IT Launchpad enable you to planthe installation, install the product, access the information center, and exit theinstallation program.

Plan the installation (Installation Planning)Plan the installation using:v Release notes for technical informationv Quick Start Guide for available features and deployment optionsv Planning installation guides for system requirements and deployment

options

Install the ProductInstall the software. The Launchpad guides you through the installation toperform the following tasks in the right order:1. “Installing middleware with the Tivoli middleware installer” on page

42,2. Installing Tivoli Asset Management for IT 7.2.2 and the appropriate

Language Pack3. Installing Tivoli Integration Composer

Information CenterAccess the information center.

Exit Exit the installer.

IBM Tivoli Asset Management for IT for Service ProvidersLaunchpad

Use the Tivoli Asset Management for IT for Service Providers Launchpad to installthe required service provider extensions and enablement key for managed serviceproviders.


options

Install the ProductInstall the software. The Launchpad guides you through the serviceprovider process solution installation and enablement.1. Installing Tivoli Asset Management for IT for Service Providers 7.2.2.

See Chapter 13, “Enabling IBM Tivoli Asset Management for IT forService Providers,” on page 249.



Exit Exit the installer.

IBM Tivoli Asset Management for IT for Internal ServiceProviders Launchpad

Use the Tivoli Asset Management for IT for Internal Service Providers Launchpadto install the required service provider extensions and enablement key for internalservice providers.


options

Install the ProductInstall the software. The Launchpad guides you through the serviceprovider process solution installation and enablement.1. Installing Tivoli Asset Management for IT for Internal Service Providers

7.2.2. See Chapter 13, “Enabling IBM Tivoli Asset Management for ITfor Service Providers,” on page 249.


Exit Exit the installer.Related tasks

“Starting the Launchpads”IBM Tivoli Asset Management for IT and the IBM Tivoli Asset Management for ITcomponents can be installed using the Tivoli Asset Management for ITLaunchpads.

Starting the LaunchpadsIBM Tivoli Asset Management for IT and the IBM Tivoli Asset Management for ITcomponents can be installed using the Tivoli Asset Management for ITLaunchpads.

About this task

To start the Launchpads, complete the following steps:

Procedure1. Log on to an account with system administration privileges on the computer

where Tivoli Asset Management for IT components need to be installed.2. Start the Launchpads from the root directory of the product DVD:

v Windows Windows: Start the Launchpads by using the launchpad.exeprogram if the Windows autorun feature is disabled.

v AIX AIX: Start the Launchpads from the root directory by using thelaunchpad.sh program.The Launchpad program uses the system default browser to run. If thedefault browser on AIX is Firefox, it is likely that the Launchpad programdoes not run properly due to the ksh shell interface. If you want to use theLaunchpad with the Firefox browser, follow these steps to modify it.

Chapter 3. Preparing to install 29

a. Copy all the files from disk1 to a local directory (for example, /your_dir).If you have downloaded the product images rather than using physicalmedia, download and extract the Launchpad images as described in thedownload document.

b. Modify /your_dir/launchpad/Firefox.sh and remove the following lines:typeset +r LOGNAME 2>/dev/nullLOGNAME=lp_user_$$; export LOGNAME

c. Modify the launchpad.sh file in a text editor. Replace the last line of thefile$LaunchPadBatchPath/jclp.sh || eval exec $whichBrowserScript

with$LaunchPadBatchPath/jclp.sh || eval exec /Tamit7.2.2.0/launchpad/Firefox.sh

d. Run the Launchpads from your_dir directory, using the command:launchpad.sh

v Linux Linux: Start the Launchpad from the root directory by using thelaunchpad.sh program.For example,./media/cdrecorder/launchpad.sh

Running the Launchpad from the root directory avoids complications thatwould arise if you ran it inside the mounted directory and you wanted toswap disks. If you changed directory to the mounted DVD and launched theLaunchpad from that directory, at a certain point in the deployment processyou would need to swap to another DVD, but you would not be able tobecause Launchpad was still running from the directory on the DVD youhave mounted. You would not be able to unmount the disk withoutterminating the Launchpad.

What to do next

For more information about installation and configuration parameters you mightencounter while installing Tivoli Asset Management for IT, refer to “Planning forTivoli middleware worksheet” on page 12 and “Planning for the productworksheet” on page 17.Related reference

“Product media and Launchpads” on page 27IBM Tivoli Asset Management for IT ships on a set of DVDs that contain theprerequisite middleware, Quick Start Guide, and the product code. The optional,purchasable components, IBM Tivoli Asset Management for IT for Internal ServiceProviders and IBM Tivoli Asset Management for IT for Service Providers, are alsoshipped on DVDs. Alternatively, you can download the product files containingthese same images from IBM Passport Advantage. The Launchpads serve ascentralized interfaces for launching a collection of installation programs andproduct information.

Before you beginThis section describes the steps that you need to take before you installmiddleware or IBM Tivoli Asset Management for IT. To perform any of the steps,you need to be logged in as a user with administrator privileges on Windows or asroot on UNIX.


Checking port 50000 availabilityYou need to ensure that certain ports are available before using the productinstallation programs.

About this task

You need to manually check to see if port 50000 is in use for the system you areusing to host IBM DB2. It is the default port value used by DB2. If you intend touse this value, ensure that the port is not already assigned before you run themiddleware installation program.

Procedure1. Open the appropriate port checking utility on the host system.2. Check the availability of port 50000. If you find that port already assigned,

ensure that you choose another value for DB2 when prompted by themiddleware installation program.

Related reference

“Planning for port availability” on page 20Make sure that you enabled ports in support of the installation and deployment.

Accessing system directoriesLinux Before using the middleware installation directory, you need to assign

access permission to particular directories.

Before you begin

Before using the middleware installation directory, you need to assign accesspermission for the /tmp and /home directories on Linux systems.

About this task

The product installation programs require read, write and execute permissions forthe /tmp and /home directories. If one of these directories uses a symbolic link, forexample, /products/home, ensure that symbolic link directory also has the properaccess.

Procedure1. Log in to the system as a user with root authority on the system.2. Enter the following commands:

#chmod 777 /tmp#chmod 777 /home

Disabling the firewallBefore the installation, disable the firewall for the system to which you areinstalling Tivoli Asset Management for IT middleware.

About this task

See the documentation that comes with your Operating System for informationabout disabling the firewall.


Verifying the required Rational Portfolio Manager buildpackage is installed

Linux On Linux, this procedure describes how to verify that the RationalPortfolio Manager build package is installed on Linux. This package must beinstalled before you run the middleware installation program.

About this task

To verify that the Rational Portfolio Manager-build package is installed, performthe following steps:

Procedure1. Run rpm -qa | grep build command.2. If the command returns a value like rpm-build-4.3.3.-18_nonptl, the Rational

Portfolio Manager build package is installed. If nothing is returned, install theRational Portfolio Manager-build package which is located on disk 3 (of 5) ofthe Red Hat Enterprise Advanced Server 4 (32 - bit Intel) installation mediausing the Rational Portfolio Manager tool with the -i option.

Setting the ulimitLinux This section details how to set the ulimit in Linux, which is used to

define user system and process resource limits.

About this task

Set the ulimit for the system before installing Tivoli Asset Management for ITmiddleware. To set the ulimit, complete the following steps:

Procedure1. From a command line, type ulimit -f unlimited.2. From a command line, type ulimit -n 8192.

Results

If you set the ulimit in the .profile for root, the ulimit setting will apply to allprocesses.

AIX For AIX systems, refer to “Increasing AIX file size and number ofdescriptors” on page 36.

Setting the swap sizeLinux Tivoli Asset Management for IT can be a resource-intensive application.

It is recommended that you configure and tune your system for maximumperformance. This section details how to set the size of the swap space used inLinux systems.

About this task

Typically, the swap size set for Linux systems must be equivalent to twice theamount of physical RAM in the computer.

Additional swap space can be made available to the system by:


Procedurev increasing the size of the existing swap partitionv creating an additional swap partitionv creating a swap file

What to do next

Refer to the product documentation for your Linux distribution for moreinformation.

AIX For AIX systems, refer to “Increasing AIX paging space” on page 36.

Setting shared memoryLinux This section details how to set a minimum shared memory value in

Linux before you start to install IBM Tivoli Asset Management for IT

Before you begin

Set a minimum shared memory value for the system before installing the TivoliAsset Management for IT middleware.

About this task

To set the minimum shared memory value, complete the following steps:

Procedure1. From a command line, type sysctl -w kernel.shmmax and determine if the

value is less than 268,435,456 bytes (256 MB).2. If you want to increase the value, from a command line, type sysctl -w

kernel.shmmax=268435456.3. Update the value in /etc/sysctl.conf.

Remote configuration enablementIf you plan to use IBM Tivoli Asset Management for IT to automatically configuremiddleware, you need to enable a remote access protocol for each system on whichyou intend to install the middleware.

The remote access protocols that support remote configuration are SSH for loggingon to and configuring remote Linux and UNIX systems and Windows SMB forlogging on to and configuring remote Windows systems. Windows SMB is aWindows protocol. The IBM JRE on the administrative workstation includes SSH,so you do not need an SSH client to remotely configure middleware on Linux orUNIX systems. But you need to install OpenSSH on remote non-Windowsworkstations so that you can log on to them, using SSH protocol.

Before you start the installation program, ensure that you can log in to any remoteservers with the protocols that you intend to use and the credentials that you planto supply to the installation program.

Windows For remote Windows systems, ensure that the following requirementsare met before installing the software:


v The user name that you provide to the installation program must exist as a localaccount on the remote computer and the user must be a member of theWindows Administrators group.

v The following Windows services must be started on the remote computer beforeyou begin a remote installation and configuration:– winmgmt (Windows Management Instrumentation)– RemoteRegistry (Remote Registry)– lanmanserver (Service)

v The SMB protocol must be enabled and configured to use send NetBIOS overTCP/IP, by choosing to use port 139. Alternatively, you can configure SMB touse TCP/IP as the transport protocol, without NetBIOS, by configuring it to useport 445.

v Ensure that any ports that you use for remote protocols are not blocked byfirewalls or security policies, including ports 137 and 139. Port 139 is used ifSMB is configured to run on NetBIOS over TCP/IP, and port 445 is used if SMBis run directly on TCP/IP, without NetBIOS. Refer to “Planning for portavailability” on page 20.

v To disable simple file sharing, start Windows Explorer. Click Tools → FolderOptions, and clear the Use Simple File Sharing check box.

v The Windows administrative share (C$) and the interprocess communications(IPC$) folder must be shared.

v For Windows 2008 Server systems that support password-protected sharing,disable password-protection. Shares must be shared for the Guest or Everyoneaccounts.

v For Windows systems that have User Account Control (UAC) enabled, it mustbe disabled before software can be remotely installed and configured.

v If Cygwin is installed on the remote Windows system the SSH daemon (sshd)must be uninstalled or disabled.

UNIX For remote Linux or UNIX systems, ensure that the followingrequirements are met before installing the software:v The user name that you provide to the installation program must exist as a

privileged account (for example, root) on the remote computers.v Ensure that a current version of OpenSSH is installed and running. Do not use

OpenSSH 4.7.0.5302.v For Solaris systems, the remote access protocols require the use of internal shell

scripts that must be run within the korn (ksh) shell. The methods need ksh, evenif the user ID that you use to log on to the remote system is configured to use adifferent shell. Consequently, Solaris systems must have the ksh environmentinstalled and properly configured.

v If you plan to remotely configure software on remote Linux or UNIX computers,ensure that SSH is installed.

Remote configuration does not support accessing network drives on the local orremote system.

Backing up the Deployment Engine databaseThese instructions are for backing up the Deployment Engine database. Backupsare used to restore the database to the state it was before installing middleware orprocess managers.


Before you begin

Back up the Deployment Engine database of the system before and after applyingany updates to an existing deployment. Use backups to recover from partialinstallation attempts where middleware or process manager components werepartially installed.

About this task

To back up the Deployment Engine database, complete the following steps:

Procedure1. Set up the environment using the following command:

Windowsc:\Program Files\IBM\Common\acsi\setenv.cmd

UNIXcd /var/ibm/common/acsi./setenv.sh

2. Run the command to back up the Deployment Engine registry:

Windowsc:\Program Files\IBM\Common\acsi\bin\backupdb.cmd backup_file_name

UNIXcd /usr/ibm/common/acsi/bin./backupdb.sh backup_file_name

Use a meaningful name for backup_file_name to reflect the fact that it containsthe state of the registry after your installation of Tivoli Asset Management forIT. For example, DEBackupAfterTAM4ITInstall.

Preparing UNIX systems for the required middlewareUNIX Certain UNIX parameters must be set to specific values to create an

environment on the system that can accommodate Tivoli Asset Management for ITand its associated middleware.

AIX tar command requirementsBoth the native UNIX tar command and the GNU version of the tar command arerequired by the middleware installation program. Because the native utility doesnot support long file names, ensure that GNU tar 1.14 or higher is installed, so thatthe installation files can be extracted.

To download GNU tar, go to http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html.

Verify that the system path variable contains both native UNIX tar and GNU tarpaths. The GNU tar path must be defined before the native UNIX tar path. Forexample, the native tar utility is installed in /usr/bin and the GNU tar utility isinstalled in /opt/freeware/bin/tar.

If you have set a symbolic link to overwrite the native UNIX tar command withthe GNU tar command an error occurs.


http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html

http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html

Increasing AIX file size and number of descriptorsAIX To make Tivoli Asset Management for IT function correctly, you need to

increase the default number of file descriptors allowed for the root user, and alsoset the maximum allowable file size to unlimited.

About this task

To increase the allowable file size and number of allowable descriptors for the rootuser in AIX, complete the following steps:

Procedure1. Edit the /etc/security/limits file by opening it in a text editor.2. Locate the section for the root user, and then make changes to the parameters

below using the values listed.root:

fsize = -1nofiles = 8192

A value of -1 for the fsize parameter indicates no limit.3. Save and exit the file. You need to log out as root and log back in for these

changes to take effect.

What to do next

Verify the settings from a command window by issuing the following command:ulimit -a

Output from the ulimit command should be similar to the following:time(seconds) unlimitedfile(blocks) unlimiteddata(kbytes) 2097152stack(kbytes) 32768memory(kbytes) unlimitedcoredump(blocks) 2097151nofiles(descriptors) 8192

Increasing AIX paging spaceAIX To successfully install and run Tivoli Asset Management for IT, you need

to increase the default paging space for the AIX system to a minimum of 4 GB, or,preferably, the total amount of physical memory in the system.

Procedurev Determine the current amount of paging space available to the server by issuing

the following command.lsps -a

This command results in output like the following sample output:Page Space Physical Volume Volume Group Size %Usedhd6 hdisk0 rootvg 5632MB 2

v Determine the size of a logical partition by issuing the following command:lslv hd6

This command results in output that includes partition information like thefollowing sample information:LPs: 44PP SIZE: 128 megabyte(s)


In the example output, there are a total of 44 Logical Partitions that are each 128MB in size. These results show a total of 5632 MB of paging space available tothe system.

v In order to add more paging space, add more logical partitions to the system. Toadd more logical partitions, use the following command:chps -s xx yyy

Where xx is the number of logical partitions to add and yyy identifies the logicalvolume.For example,chps -s 10 hd6

adds 10 logical partitions to the logical volume hd6, which results in adding1280 MB to the paging space.

Enabling asynchronous I/O on AIXAIX Tivoli Directory Server requires asynchronous I/O be enabled on AIX

systems. Without asynchronous I/O, DB2 and Oracle database instances cannot bestarted successfully. It is an operational requirement, not an installationrequirement so this step can be run at any time before full operation of theproduct.

About this task

You only need to perform this step if the system will host the IBM Tivoli DirectoryServer.

To turn asynchronous I/O on follow these steps:

Procedure1. Log into the system as root.2. Open a terminal and run the following command:

smit chgaio

3. From the System Management Interface Tool (SMIT) dialog box, change STATEto be configured at system restart from defined to available, and then clickOK.

4. Exit SMIT.5. Run the following command from the command line:

smit aio

6. From the System Management Interface Tool dialog box, select ConfigureDefined Asynchronous I/O, and then click Enter.

7. Reboot the system to enable the changes.

Checking for required libraries on LinuxLinux The Tivoli Asset Management for IT middleware installation program

requires the libstdc+.so.5 system library to be present on a Linux system in orderto launch the middleware installation program user interface.

About this task

If you do not have this library installed, you will receive an error indicating thatthe Tivoli Asset Management for IT middleware installation program is unable torun in graphical mode.


If you receive this error, check the /usr/lib/ directory to determine if you havethe libstdc+.so.5 library installed. This library is included as part of Red HatEnterprise Linux v4 update 4. If you cannot locate this library on your system,locate the Rational Portfolio Manager package for your system that contains thislibrary and install the package.

Configuring the JRE in LinuxLinux In some cases, the Tivoli middleware installation fails on Red Hat

Enterprise Linux 5 systems, or other systems with SELinux enabled.

About this task

In one scenario, the middleware installation fails with an error message stating thatthe Java Runtime Environment (JRE) could not be found on the system. In anotherscenario, the middleware installation program fails stating that it cannot find thevirtual machine.

Complete the following steps to avoid these problems:

Procedure1. Temporarily disable SELinux by using the setenforce 0 command.2. Run the middleware installation program.3. Re-enable SELinux by using the setenforce 1 command.4. Manually issue the chcon -R -t textrel_shlib_t install_dir/jvm/jre

command.

Results

The middleware installation program is now able to locate the JRE. Alternatively,you can edit the /etc/selinux/config file and set SELINUX to either permissiveor disabled for a more permanent fix. This solution, however, affects the level ofsecurity for the entire system.Related information

http://www.crypt.gen.nz/selinux/disable_selinux.htmlHow to disable SELinux


http://www.crypt.gen.nz/selinux/disable_selinux.html

Chapter 4. Installing middleware

Before you install IBM Tivoli Asset Management for IT, there are several TivoliAsset Management for IT middleware products that must be deployed. Themiddleware installer provides an interface for installing and deploying the productmiddleware in a reliable and repeatable fashion.

The middleware installer records choices you make about your Tivoli AssetManagement for IT deployment and configuration parameters associated withthose choices, and then installs and deploys the middleware based upon theinformation you entered.

The middleware installer installs and deploys the following software (comparewith Figure 1 on page 2):

Database server

See “Software components” on page 1 for additional information.

You can either install a new instance of IBM DB2, or use an existinginstance. If you choose to use Microsoft SQL Server or Oracle for yourTivoli Asset Management for IT deployment, install and configure themseparately.

Directory server


You can install a new instance of IBM Tivoli Directory Server 6.2 or use apreexisting Directory Server or Microsoft Active Directory server.v If you choose to install a new version of Directory Server, choose to

install a new DB2 instance, or reuse an existing DB2 server.v If you choose to use Microsoft Active Directory Server for your directory

server, install and configure it separately.

J2EE server


A directory server can be configured to secure the J2EE server deployment.You can use a local or remote IBM Tivoli Directory Server or MicrosoftActive Directory Server.

The J2EE component includes the following subcomponents:

IBM HTTP ServerThe server is used as the primary HTTP server. You install a newinstance of IBM HTTP Server.

IBM HTTP Server Plug-inThe IBM HTTP Server plug-in is used as the interface between theHTTP Server and the J2EE server. You install a new instance ofHTTP Server plug-in.

The middleware installer deploys software on a single computer. To deploy TivoliAsset Management for IT middleware on multiple computers, the middlewareinstaller must be invoked on each computer in the topology configuration youhave chosen.


Ensure that you have a strategy for deploying product middleware for each systemyou plan to use in your Tivoli Asset Management for IT deployment. If you deploya product component using the middleware installer on a system, for example,DB2, and then later decide you would also like to add Directory Server to thatsame system, undeploy DB2 before redeploying it in the same middleware installerdeployment plan that included Directory Server.

When installing Tivoli Asset Management for IT middleware on a system, installall the middleware intended for that system at one time.

In addition to installing and configuring the product middleware, the middlewareinstaller performs additional tasks: if you choose to not run the middlewareinstaller because you intend to perform the necessary configuration on existingmiddleware resources manually, you need to configure Virtual Member Managerafter the J2EE server and the Directory Server have been installed and configured.Refer to “Manually configuring Virtual Member Manager on IBM WebSphereApplication Server” on page 161 for more information.

Process IDEvery time you use Tivoli middleware installer to install or uninstall middlewareproducts, a process ID is generated.

A process ID:v Appears on the file system in various places related to logs and generated files,

such as file names, directory names, and log messages.v It is used to group logs and other generated files that are related to the same

invocation of the middleware installer.v It also separates logs and other generated files that are related to different

invocations of the middleware installer.

The process ID is a string of the format[operation_MMdd_HH.mm],

where

operationis a string indicating the operation being performed, such as “INSTALL” or“UNINSTALL”,

MMis a two-digit number (1-12) indicating the current month,

dd is a two-digit number (1-31) indicating the current day in the month,

HHis a two-digit number (0-23) indicating the current hour,

mmis a two-digit number (0-59) indicating the current minute.

Here are some examples of process ID values:v [INSTALL_0924_15.45]

An installation started on September 24 at 3:45pmv [UNINSTALL_1216_09.59]

An uninstallation started on December 16 at 9:59am


Tivoli middleware installer workspaceThe Tivoli middleware installer is designed to record the options you select duringinstall in a directory referred to as the workspace, and then configure thecomponents selected as a single deployed application. Once a plan has beendeployed, the middleware installer cannot subsequently deploy additional featuresand products onto the computer at a later time.

The existing plan must first be completely undeployed through the middlewareinstaller before a different set of features and products can be deployed.

The composition and details of the deployment, as well as any logs generated bythe middleware installer process are located in the workspace.

By default, the middleware installer workspace is defined as:

Windows Windows:C:\ibm\tivoli\mwi\workspace

UNIX UNIX:/ibm/tivoli/mwi/workspace

The workspace can be defined on a shared resource that is made available to allthe systems that will run the middleware installer. Locating the workspace on ashared resource avoids the need to copy files such as the topology file manuallyfrom one computer to another.

The workspace contains the following items:

Deployment PlanThe deployment plan is a collection of installation steps, configurationparameters for those steps, and target computer information. It isgenerated through the middleware installer and it resides in the workspacedirectory.

When deployment steps are changed, the existing deployment plan isdeleted and replaced with the new deployment plan.

The deployment plan configuration files contain information about thedeployment plan itself. Whenever a deployment plan is modified, whichincludes reconfiguring existing deployment choices, the deployment planconfiguration files will be deleted and regenerated when the deploymentplan is redeployed.

Topology FileThe topology file is a properties file that describes the configurationparameters of the Tivoli Asset Management for IT middleware deployment.This file is created and then updated after every deployment orundeployment. If you have not defined a workspace that is centrallylocated and accessible to all the systems that will be receiving Tivoli AssetManagement for IT middleware, this file will have to be copied to theworkspace of each computer where Tivoli Asset Management for ITmiddleware is being deployed. The contents of this file can be used by theTivoli Asset Management for IT installation program to populate its panelswith meaningful default values.

This file is saved in workspace_dir/topology.xml.

Logs Log files that contain information about the deployment can be found in

Chapter 4. Installing middleware 41

the workspace directory. In addition, log files native to the Tivoli AssetManagement for IT middleware itself are also contained in this directory.

Tivoli Asset Management for IT middleware deployment plan overviewThe deployment plan resides in the workspace directory and is generated fromdeployment choices selected in the middleware installer. The plan is a series ofdeployment steps and configuration parameters.

Each step is responsible for installing and uninstalling one portion of themiddleware. When deployment choices are changed, the existing deployment planis deleted and replaced with the new deployment plan.

Once the deployment plan has been generated using the information you enteredin the middleware installer, you have the option to have the middleware installerexecute it. This method of executing the deployment plan is recommended in mostinstances.

Options for invoking the deployment planOnce the deployment plan has been generated using the information you enteredin the Tivoli middleware installer, you have several options for executing it.

Have the Tivoli middleware installer execute the deployment plan after it hasbeen generated

This is the most common method of implementing the deployment plan.Create the plan using the middleware installer and then have it execute theplan by installing and configuring the middleware selected. This option alsoincludes configuring existing instances of middleware present in yourenvironment that will be used with Tivoli Asset Management for IT.

This method of executing the deployment plan is recommended in mostinstances.

Have the Tivoli middleware installer create the deployment plan and thencomponentize and distribute it

The deployment plan consists of a collection of XML files that can be used todeploy middleware either through the middleware installer or by Apache Ant.Ant is an open source software tool used to automate the software buildprocess. Ant uses XML to describe build tasks and dependencies.

You need to have Ant 1.6.5 and the Java 1.5 JRE installed in order to execute adeployment plan outside of the middleware installer.

This method of executing the deployment plan should be reserved foradvanced users that have a need to modify deployment plan parameters thatare not configurable through the middleware installer.

Installing middleware with the Tivoli middleware installerThis procedure explains how to use the middleware installation program to createa deployment plan that is responsible for installing and configuring prerequisitemiddleware products.

Before you begin

The instructions provided are for the installation on a single computer of acomplete set of middleware for use with IBM Tivoli Asset Management for IT,


based on default values. This deployment scenario is suitable for demonstration,test, or training purposes. For a production environment, installing middleware onmultiple computers improves performance and load-balancing. To deploymiddleware on multiple computers, you need to run the middleware installationprogram on each computer, choosing which middleware component to install oneach.

If you want to configure existing middleware products for use with Tivoli AssetManagement for IT, follow the instructions for that deployment scenario.

In some cases, information about the middleware installation program screens isnot correctly displayed when installing through a remote session. To avoid such aproblem, run the middleware installation program locally on the system that is tohost the middleware. If you do encounter the problem, first minimize and thenmaximize the install wizard to redisplay the screen.

Do not install multiple middleware products into the same custom directory. Forexample, when installing IBM WebSphere Application Server and IBM DB2 on thesame computer, you cannot install both in a C:\ISM_middleware directory. You can,however, install them in C:\ISM_middleware\DB2, C:\ISM_middleware\ITDS, andC:\ISM_middleware\WAS. You also cannot install one middleware product in acustom directory and then install another middleware product in a subdirectory ofthat custom directory. For example, if you install WebSphere Application Serverinto C:\ISM_middleware, you cannot then install IBM Tivoli Directory Server intoC:\ISM_middleware\ITDS.

Do not use local_host for host name values in the installation program. Specifythe fully qualified host name of the system on which you are installing.

v Linux For Linux or UNIX systems, ensure that the command host_name -freturns a fully qualified host name. If it does not, consult the appropriatedocumentation for your operating system to ensure that the host namecommand returns a fully qualified host name.

v Windows Ensure that a Windows Primary DNS suffix is defined.

To verify a fully qualified host name, complete the following steps:1. On the desktop, right-click My Computer.2. Select Properties. The System Properties panel is displayed.3. From the Computer Name tab, click Change. The Computer Name Changes

panel is displayed.4. Enter your fully qualified host name in the Computer name field, and then

click More. The DNS Suffix and NetBIOS Computer Name panel is displayed.5. Verify that the Primary DNS suffix field displays a domain name, and then

click OK.6. From the Computer Name Changes panel, click OK.7. Click Apply and close the System Properties panel.

When installing and configuring middleware in the middleware installationprogram and the Tivoli Asset Management for IT installation program, considerthe following special characters restrictions:


Table 11. Middleware object naming conventions

Middleware object Description

IBM DB2 naming conventions for Group names,user names, and user IDs

UNIX

Group names and user IDs on UNIX operatingsystems can contain up to eight characters andmust consist of lowercase characters only.

Windows

Group names and user names on Windows cancontain up to 30 characters.

Names and IDs cannot be any of the followingvalues: USERS, ADMINS, GUESTS, PUBLIC, LOCAL, orany SQL-reserved word.

Names and IDs cannot begin with IBM, SQL orSYS. They must also not begin with the underscore(_) character.

IBM DB2 naming conventions for DB2 instances Instance names can have up to eight characters.

Windows

On Windows, no instance can have the same nameas a service name.

DB2 naming conventions for passwords UNIX

For UNIX operating systems, passwords can be amaximum of eight characters.

Windows

For Windows systems, passwords can be amaximum of 14 characters.

IBM Tivoli Directory Server conventions fordatabases and database aliases.

Database names must be unique within thelocation in which they are cataloged.

UNIX

For UNIX operating systems, this location is adirectory path.

Windows

For Windows, it is a logical disk.

Database alias names must be unique within thesystem database directory. When a new database iscreated, the alias defaults to the database name. Asa result, you cannot create a database using aname that exists as a database alias, even if there isno database with that name.

Database and database alias names can have up toeight characters.

The special characters @, #, and $ are not commonto all keyboards. Avoid using these characterswhen creating a database name.


Table 11. Middleware object naming conventions (continued)

Middleware object Description

IBM Tivoli Directory Server conventions for users,groups, databases, and instances

Do not use values that are longer than eightcharacters.

Do not use: USERS, ADMINS, GUESTS, PUBLIC, LOCAL,or idsldap as values.

Values cannot begin with IBM, SQL, or SYS.

Values cannot include accented characters.

Values can include characters A through Z, athrough z, and 0 through 9.

Values must begin with characters A through Z ora through z.

Do not use double-byte characters in administratorpasswords.

Passwords cannot contain the following specialcharacters: ` ' \ " |

IBM WebSphere Application Server NetworkDeployment

The administrator name cannot contain thefollowing characters:

/ \ * ,: ;=+?|< > & % ’"] [> # $ ~ ( ) !

The administrator name cannot begin with aperiod.

The administrator name cannot contain leadingand trailing spaces.

The administrator password must consist of eightcharacters.

Middleware installation program The middleware installation program does notvalidate that your password is compliant with theoperating system of the target host. Ensure that thepassword values you provide are valid for yourenvironment.

Windows

You cannot use the % character on Windows

UNIX

You cannot use the !, $, #, % characters on Linuxand UNIX systems.

The middleware installation program does notcheck for accented characters in user namevalues. The use of accented characters can causeerrors.

Important: When entering LDAP values for Tivoli Asset Management for ITinstallation panel fields, entries in LDIF files, or values you enter directly into adirectory instance using the tools of the directory server, follow theproduct-specific syntax rules for using special characters in an LDAP string. Inmost cases, you need to precede special characters with an escape character inorder to make it readable by the directory server. Failing to escape specialcharacters contained in an LDAP string used with the product can result in errors.


Many directory server products consider a blank space as a special character that ispart of the LDAP string. If you enter an LDAP string that contains a blank in afield, you encounter errors that are difficult to troubleshoot. You must precede anyblank characters with an escape character. See the product documentation for yourdirectory server for more information about special characters in LDAP strings.

If the middleware installation program reports that you have insufficient diskspace to install middleware, you need to increase the available disk space on thesystem, and then restart the middleware installation program.

When you run the middleware installation program, you are prompted for userIDs to initiate the installation of DB2, WebSphere Application Server, and thedirectory server. You can either supply an existing system user ID, or allow themiddleware installation program to create a new user ID. The installation can failif you specify an existing user account to install DB2 or directory server and thatuser account is not located under the /home directory.

UNIX If you run the middleware installation program from a Linux or UNIXterminal window, you need to be logged in as a user with administrative authority(root). If you are logged in as another user, and plan to use the su command inorder to use the shell of the administrative user, you encounter errors during theinstallation of IBM Tivoli Directory Server. During installation, the middlewareinstallation program sets environmental variables that must be set for theadministrative user.

If you encounter the following error, it indicates that you are attempting to use the64-bit middleware installation program (mwi-AMD64.exe) on a 32-bit Windowssystem.CreateProcess failed ==> The image file %1 is valid, but for a machine typeother than the current machine

The appropriate middleware installation program for 32-bit Windows systems ismwi.exe. Alternatively, run the following command to automatically select theappropriate program for the system:setupwin.bat /l

About this task

To install the prerequisite middleware products for Tivoli Asset Management forIT, follow these steps:

Procedure1. Log in as a user with administrative authority.2. Launch the middleware installer from the Launchpad.

a. Start the Launchpad: On the DVD titled “Tivoli Asset Management for IT7.2.2”, navigate to the root directory of the product disc or thedownloaded installation image, and run the command:launchpad.[exe|sh], depending on your operating system.When you launch the middleware installation program from theLaunchpad, the middleware installation program files are copied from themedia to a temporary directory on the system. You can use the followingsetup scripts to launch the middleware installation program directly andprevent the installer from copying the files to the system.


Windowslaunchpad\Install\MWIsetupwin.bat /l

Linux and UNIXlaunchpad\Install\MWIsetupUNIX.sh -l

Errors can occur when using the setup scripts. The following errors canoccur when using the setup scripts.

Table 12. Middleware installation program setup script error codes

ErrorCode Error Description

11 Unsupported operating system The middleware installation programor one of the middleware productscannot run on this operating system.

12 Unsupported Linux distribution The middleware installation programor one of the middleware products isnot supported on this Linux kernel.Currently only Red Hat and SuSE aresupported.

13 Unsupported kernel bit mode The middleware installation program issupported on Linux 32/64 bit modeand on AIX 64 bit mode.

14 Unsupported Processor architecture The middleware installation programor one of the middleware products isnot supported on this processorarchitecture. Currently only x86 andAMD64 architecture are supported.

21 Env variablemwi_launchpadroot(UNIX) /LaunchPadBatchPath(Win) is not set

The environment variable must be setto the middleware installation programinstall files location:

WindowsLaunchPadBatchPath

Linux and UNIXmwi_launchpadroot

22 The middleware installation programfile not found

The middleware installation programinstall file is missing or not accessible.Check to ensure that the specified fileexists in the current directory.

31 Host name is not a fully qualifieddomain name.

The middleware installation programor one of the middleware productsrequires a fully qualified host namedefined.

32 SELinux is enabled or set in Enforcingmode

Middleware product installation failswith the following error:

JRE could not be found on the system

Disable SELinux using one of thefollowing methods:v setenforce 0

v Add the following entry to the/etc/system file:

set fmac_enforcing = 0


Table 12. Middleware installation program setup script error codes (continued)


33 The library libstdc++.so.5 (64-bit) isnot installed.

The installer requires libstdc++.so.5(64-bit), which is located in/usr/lib64/libstdc++.so.5. If thesystem does not have this libraryinstalled, search for an RPM package(64-bit) compatible with system thatcontains this library and install it.

34 The library libstdc++.so.5 is notinstalled.

The installer requires libstdc++.so.5,which is located in/usr/lib/libstdc++.so.5. If the systemdoes not have this library installed,search for an RPM package compatiblewith system that contains this libraryand install it.

b. In the Launchpad navigation pane, click Install the Product.c. Click the Middleware link under Install the middleware.

3. Select a language for the installation and click OK.4. In the Welcome panel, click Next. The middleware installer license agreement

window is displayed.5. Read the license information and select I accept both the IBM and the

non-IBM terms if you agree with the terms. Click Next.6. In the Choose Workspace panel, specify the directory you want to use as the

middleware installation program workspace, and then click Next.The default location for the workspace (workspace_dir) is the last workspacelocation you used, as specified in the middleware user preferences node. If noprevious workspace location exists in the middleware user preferences node,then the default location for the workspace is:

v Windows Windows: C:\ibm\tivoli\mwi\workspace

v UNIX UNIX: /ibm/tivoli/mwi/workspace

If the selected directory does not exist, it is created.After deployment, the middleware installation program also generates atopology file in this directory. You can manually copy this topology file to theworkspace of the next computer in the topology, so that information about thedeployment of middleware is available to the middleware installer when it isexecuted on the next computer.

7. In the Install IBM Autonomic Deployment Engine panel, click Next.8. In the Deployment Choices panel, select the features to deploy on this

computer, and then click Next.Choices include:v Database Server.v Directory Server.

v J2EE Server.If you choose to only install the server portion of the middleware, you areprompted to supply the directory server you use to secure it. In this caseyou secure with an existing instance of the directory server, or an existinginstance of Microsoft Active Directory.

v Secure the J2EE Server using the Directory Server.


This option allows you to use a directory server to secure the server. Thisoption is required if you are installing the Server option. By default thisoption is selected. It must remain selected in order for you to enable theDirectory Server option.If you select to opt out of maintaining server through the use of thedirectory server, you are not able to install the directory server through themiddleware installation program.

9. In the Deployment Plan Summary window, click Next to configure theparameters displayed. The deployment plan is generated and you areprovided details about the plan.

10. In the Configurable Host Name panel, if you want to manually specify thehost name of the machine you are running the installation from, select theOverride the local machine hostname option and enter a host name value inthe Hostname field, and then click Next. Select this option only if you want tomanually specify the host name of the system instead of having theinstallation program programmatically detect it. This option is useful whenthere is more than a single host name assigned to the system. This situation ispresent when a system has more than one network interface, or it isconfigured to support virtual IP addresses. When this option is selected, youare required to provide a resolvable host name. You cannot clear this optiononce it has been selected. However, you are able to change the value of theHostname field. If you launched the middleware installation program fromthe command line using the forceHostname=true parameter, then you arerequired to provide an alphanumeric value in the Hostname field. An IPaddress results in an error message. Once this option has been selected, youcannot able to clear it. However, you can change the value you enter in theHostname field.

11. In the password reuse panel, you can optionally select Use this password asthe value for all subsequent passwords. You then enter a password value andthen click Next. This option allows you to use the same password as thedefault user password value in all panels of the middleware installationprogram. If you do not want to use this option, ignore the Use this passwordas the value for all subsequent passwords option, and click Next.

12. Enter configuration parameters for Enterprise Edition Version and then clickNext.

Install location (db2_install_dir)Enter the location to install IBM DB2.

Windows Windows:Default is C:\Program Files\IBM\SQLLIB

Linux Linux:Default is /opt/IBM/db2/V9.7

AIX AIX:Default is /opt/IBM/db2/V9.7

DB2 Administration Server usernameEnter the DB2 administrative account name.

Windows Windows:Default is db2admin

Linux Linux:Default is dasusr1


AIX AIX:Default is dasusr1

DB2 Administration Server passwordEnter and confirm the password for the DB2 administrative account.

Linux AIX Fenced userEnter a system user ID that can be used as a DB2 fenced user account.Default fenced user is db2fenc1.

Note: During installation, the middleware installation programautomatically creates the following default instances of DB2:

Windows Windows:DB2

UNIX UNIX systems:db2inst1

The password for the default instance is the same password providedfor the DB2 Administration Server password (DAS).

13. Enter the following configuration parameters for the default database instance,and click Next:

Default Instance NameEnter the name of the Tivoli Asset Management for IT databaseinstance.

Default for Windows is ctginst1. For all other systems, the default isdb2inst1.

Default Instance PortEnter the port that the database instance uses.

Default for all platforms is 50000.

Default Instance UsernameEnter the user name for the database instance.


UNIX UNIX operating systems:Default is db2inst1

Default Instance User PasswordEnter and confirm the password for the database instance user name.

14. Enter the following configuration parameters for the database instance, andclick Next.

Instance nameEnter the name of the database instance.

Default for all platforms is ctginst1.

Port Enter the port that the database instance uses.


Instance usernameEnter the user name for the database instance.



UNIX UNIX operating systems:Default is ctginst1

Instance username passwordEnter and confirm the password for the database instance user name.

15. Enter information about the DB2 user groups:

DB2 administrators groupEnter the name of the DB2 administrators group.

Windows Windows:Default is DB2ADMNS

UNIX UNIX operating systems:Default is db2grp1

Windows DB2 users groupEnter the name of the DB2 users group.

Default is DB2USERS

16. Enter the following configuration parameters for IBM Tivoli Directory Server,and then click Next.

Install location (itds_install_dir)Enter the location to install the directory server.

Windows Windows:Default is C:\Program Files\IBM\LDAP\V6.2

UNIX UNIX operating systems:Default is /opt/IBM/ldap/V6.2

Administrator distinguished nameEnter the distinguished name of the administrator.

Default for all platforms is cn=root.

Administrator passwordEnter and confirm the password for the directory server administrator.

17. Enter the following configuration parameters for IBM Tivoli Directory Server,and then click Next.

Organizational unitEnter the name of the directory server organizational unit to use withTivoli Asset Management for IT.

Default for all platforms is ou=SWG.

Organization and country suffixEnter the name of the directory server organization and country suffix.

Default for all platforms is o=IBM,c=US.

Directory server portEnter the port number of the directory server.


Directory server secure portEnter the secure port number of the directory server.



Administration portEnter the administration port number of the directory server.


Administration secure portEnter the secure administration port number of the directory server.

Default for all platforms is 3539.18. Enter the following configuration parameters for IBM Tivoli Directory Server

Database Instance, and then click Next.

Database nameEnter the name of the DB2 database you are using to hold directoryserver data.

Default for all platforms is security.

Instance nameEnter the name of the directory server database instance.

Default for all platforms is idsccmdb.

Port Enter the port number used by the directory server database instance.


Instance user passwordEnter and confirm the password for the instance user ID.

19. Enter the following configuration parameters for WebSphere ApplicationServer security, and then click Next.

LDAP Host NameEnter the host name of the system hosting the LDAP instance to usefor WebSphere Application Server security.

Directory server portEnter the port number used by the LDAP server.

Default is 389.

LDAP base entryEnter the LDAP base entity of the LDAP instance.

Default is ou=SWG,o=IBM,c=US

User suffixEnter the user suffix of the LDAP instance.

Default is ou=users,ou=SWG,o=IBM,c=US

Group suffixEnter the group suffix of the LDAP instance.

Default is ou=groups,ou=SWG,o=IBM,c=US

Organization container suffixEnter the organizational container suffix of the LDAP instance.

Default is ou=SWG,o=IBM,c=US.20. Enter the following configuration parameters for WebSphere Application

Server security, and then click Next.

Bind distinguished nameAssign a distinguished name for the LDAP instance.


Default is cn=root

Bind passwordEnter the password for the distinguished name.

When you click Next, the middleware installation program validates the hostand directory information for the directory server. Items checked includeserver host name and port, the IBM WebSphere Application Server NetworkDeployment administrator credentials, bind distinguished name andpassword, base entry, user suffix, group suffix, and organizational containersuffix. If it cannot verify that the values you provided, an error messageappears. You cannot proceed with the installation until you provide valuesthat the middleware installation program can verify.

21. Enter the following configuration parameters for WebSphere ApplicationServer Network Deployment, and then click Next.

Install location (was_install_dir)Enter the location to install WebSphere Application Server

Windows Windows:Default is C:\Program Files\IBM\WebSphere\AppServer

Linux Linux:Default is /opt/IBM/WebSphere/AppServer

UNIX UNIXDefault is /usr/IBM/WebSphere/AppServer

WebSphere Administration usernameEnter the WebSphere Application Server administrative account name.

Default for all platforms is wasadmin.

WebSphere Administration passwordEnter the password for the WebSphere Application Serveradministrative account.

22. Enter the following configuration parameters for WebSphere ApplicationServer, and then click Next.

Deployment Manager profile nameEnter the profile name of the deployment manager server.

Default for all platforms is ctgDmgr01.

Application server profile nameEnter the profile name of the application server.

Default for all platforms is ctgAppSrv01.23. Enter the following configuration parameters for WebSphere Application

Server, and then click Next.

Cell nameEnter the Cell name.

Default for all platforms is ctgCell01.

Deployment Manager node nameEnter the name of the deployment manager node.

Default for all platforms is ctgCellManager01.

Application server node nameEnter the name of the node.


Default for all platforms is ctgNode01.

Update Installer install locationEnter the location where the update installer is placed.

Windows Windows:Default is C:\Program Files\IBM\WebSphere\UpdateInstaller

Linux Linux:Default is /opt/IBM/WebSphere/UpdateInstaller

UNIX UNIX systems:Default is /usr/IBM/WebSphere/UpdateInstaller

24. Enter the following configuration parameters for IBM HTTP Server, and thenclick Next.

Install location (http_server_install_dir)Enter the location to install HTTP Server.

Windows Windows:Default is C:\Program Files\IBM\HTTPServer

You cannot start and stop IBM HTTP Server from theadministrative console if you install it into a directory paththat includes spaces. For example, Program Files. You have tostart and stop theIBM HTTP Server from the command line.

Linux Linux:Default is /opt/IBM/HTTPServer

UNIX UNIX systems:Default is /usr/IBM/HTTPServer

HTTP portEnter the port used by the HTTP Server.


Admin Server portEnter the port to use to administer HTTP Server.

Default for all platforms is 8008.25. Enter the configuration parameter Profile name for WebSphere Application

Server plug-in for the IBM HTTP Server, and then click Next. Default for allplatforms is ctgAppSvr01, and this value cannot be changed.

26. The required middleware install images are listed. Verify that your plan iscorrect.Specify the location of the Tivoli Asset Management for IT middlewareimages, and then click Next.

Copy the imagesSelect this option to copy the middleware images from the productmedia to a directory that you specify.

Specify a directorySelect this option if you intend to specify a file system directory thatalready contains all the middleware installation images.

27. If you selected the option to copy install images from the source media,specify the source and destination directories, and then click Next. If youselected the option to specify a directory that already contained themiddleware images, specify that directory, and then click Next. There is an


option for checksum validation for the middleware images. Select this optionif you want to confirm the integrity of the images before deploying themiddleware. If the checksum operation fails, click the Back button and recopythe images before proceeding. If you do not select this option and themiddleware images are corrupted or otherwise inaccessible from the directoryspecified, an error occurs. If you encounter this error, you must replace thecorrupted middleware image and then restart the middleware installationprogram.

28. Specify a directory to use for middleware installer temporary files andextracted middleware installation images, and then click Next. If you specify acustom value for the temporary location on Windows Server 2008 systems,you might encounter an error when you try to undeploy the middlewareusing the middleware installation program. This problem can occur if youspecify a custom temporary directory value and restart the system beforeusing the middleware installation program to uninstall middleware. To avoidthis problem, use the default value listed for the temporary directory location.If this problem occurs, restart the middleware installation program andundeploy the middleware.

29. In the deployment plan operation panel, select Deploy the plan, and thenclick Next. You can also choose to change the deployment plan or parametersyou have previously configured from this panel.

30. In the summary panel, review the contents of the summary, and then clickDeploy to initiate the installation and configuration of the middleware youselected. Review the middleware dependency checks. The installation mighttake up to 2 hours.

31. Once the deployment completes successfully, click Finish to exit. All theinstalled components are displayed in the deployment summary window.

What to do next

You have the middleware installed and configured. Go to the Launchpad pane tocontinue with Tivoli Asset Management for IT installation.Related tasks

“Encountering error on a 32 - bit Windows system” on page 296Windows When you attempt to use the 64 - bit middleware installation program

on a 32 - bit Windows system, you encounter an error.Related reference

“Planning for Tivoli middleware worksheet” on page 12The tables in this section list the settings for values that you need to supply wheninstalling the Tivoli Asset Management for IT middleware. Although many of thedefaults can be accepted when navigating the panels of the middleware installer,you want to review this worksheet if you plan to configure manually or reuseexisting middleware. In a multi-computer deployment scenario, you might havemultiple values to consider.

Configuring IBM Tivoli Directory Server user and group stringsUse this information to configure Directory Server user and group strings postinstallation, on systems that only host Directory Server.

About this task

If you need to configure Directory Server user and group strings for a system thatonly hosts the Directory Server, it is necessary to manually create properties in the


input.properties file of the ITDS_CONFIGURATION step of the deployment plan.

Procedure1. Edit the input.properties file located in the directory server folder at:

Workspace\computer_name\deploymentPlan\MachinePlan_computer_ shortname\00006_ITDS_Configuration

Windows WindowsFor example, if the workspace is located at: C:\ibm\tivoli\workspaceand the computer name is my_machine, then the input.propertieswould be located in:C:\ibm\tivoli\mwi\workspace\my_machine.ibm.com\deploymentPlan\MachinePlan_my_machine\00006_ITDS_Configuration

Linux LinuxFor example, if the workspace is located at: /root/ibm/tivoli/mwi/workspace and the computer name is my_machine, then theinput.properties would be located in:/root/ibm/tivoli/mwi/workspace/my_machine.ibm.com/deploymentPlan/MachinePlan_my_machine.ibm.com/00006_ITDS_Configuration

AIX AIXFor example, if the workspace is located at: /ibm/tivoli/mwi/workspace, the computer name is my_machine, then theinput.properties would be located in:/ibm/tivoli/mwi/workspace/my_machine.ibm.com/deploymentPlan/MachinePlan_my_machine.ibm.com/00006_ITDS_Configuration

2. Create properties in the input.properties file that are like the followingsample property:was_nd.secure.GroupSuffix=ou\=groups,ou\=SWG,o\=IBM,c\=USwas_nd.secure.UserSuffix=ou\=users,ou\=SWG,o\=IBM,c\=US

These group and user strings are default strings. These strings can becustomized.

Example

For example, if you want to change the strings groups to grpous and users tousarious, the properties are like the following sample strings:was_nd.secure.GroupSuffix=ou\=grupos,ou\=SWG,o\=IBM,c\=USwas_nd.secure.UserSuffix=ou\= usarious,ou\=SWG,o\=IBM,c\=US

So, in the configuration parameters panel for Directory Server, if you have givencustom values instead of default values for Organizational unit, such as ou=SWG1and an Organization country suffix such as o=IBM1,c=US1 then you have tomanually replace all the occurrences of ou=SWG with ou=SWG1 and o=IBM, c=US witho=IBM1, c=US1 in the input.properties file.

In this example, the properties are like the following sample properties:was_nd.secure.GroupSuffix=ou\= grpous,ou\=SWG1,o\=IBM1,c\=US1was_nd.secure.UserSuffix=ou\= usarious,ou\=SWG1,o\=IBM1,c\=US1


Installing the required middleware silentlyIBM Tivoli Asset Management for IT provides the option of installing middlewaresilently. The Tivoli Asset Management for IT middleware silent installation optionallows you to interface with the middleware installation program using acommand prompt (not the product Launchpad), and a response file. It can be usedto deploy, undeploy, or restart the deployment of an existing deployment plan. Itcan also be used to select deployment choices, generate a deployment plan andenter configuration parameters provided you have a valid response file with theappropriate entries.

Before you begin

The middleware installation program includes a record option that allows you torecord the responses entered when installing, and then produces a response file. Byproviding a text-based response file and invoking the middleware installationprogram silently, a deployment plan can be processed without the use of themiddleware installation program user interface and without requiring userinteraction.

You need to create a separate silent installation response file for each combinationof the features that you want deployed. For example, you can create one silentresponse file for an all inclusive installation which includes the deployment andconfiguration of a database, application server, and directory server, or you cancreate one silent response file for each piece of middleware, where only one servertype is selected to be deployed and configured.

Note: Passwords are encrypted strings in response files. If you are modifyingpassword values in a response file, you enter clear text values. The middlewareinstallation program silent installation feature can work with either encrypted orclear text values.

An error can occur when reinstalling middleware silently after it has beenuninstalled. This error occurs if you use the same command window you used touninstall middleware to reinstall using the middleware installation program. Toavoid this error, after a successful uninstall operation, close the command windowyou used to invoke the installation program and use a new command window torun the middleware installation program.

About this task

To install Tivoli Asset Management for IT middleware silently, complete thefollowing steps:

Procedure1. Create a response file by generating a deployment plan and making

configuration choices using the middleware installation program.a. Open a command window, and invoke the middleware installation program

user interface using the following command:

Windows Windows:

v 32 - bitmwi-console.exe -options -record response_file_path

v 64 - bitmwi-AMD64.exe -options -record response_file_path


Linux Linux:mwi.bin -options -record response_file_path

AIX AIX:mwi_aix.bin -options -record response_file_path

b. Navigate the middleware installation program user interface, makingdeployment and configuration choices.

c. When you reach the Deployment Preview Panel, select one of the following:

Finish The Finish button generates a response file containing the choicesyou made.

CancelThe Cancel button quits the installation.

The middleware installation program executable files are located in themiddleware directory of the “IBM Tivoli Asset Management for IT 7.2.2”product DVD.

2. Open the response file in a text editor and make any necessary changes.Changes might include supplying different passwords or installation paths.

3. Copy the response file to the target system.4. Launch the middleware installation program silently and identify the response

file to be used.

Windows Windows:

v 32 - bitmwi -console.exe -options response_file_path -silent

v 64 - bitmwi-AMD64.exe -options response_file_path -silent

Linux Linux:mwi.bin -options response_file_path -silent

AIX AIX:mwi_aix.bin -options response_file_path -silent

The value for response_file_path needs to contain the fully qualifiedpath and name of the response file being used.

The middleware installation program executable files are located in themiddleware directory of the “IBM Tivoli Asset Management for IT 7.2.2”product DVD.

What to do next

When the installation is complete, you receive a success message output to theconsole.

Silent middleware installation optionsResponse files contain a number of options that you can edit before invoking themiddleware installation program silent installation program.

Response file options are detailed in comments contained in the response file itself.

Each option exists as an entry in the middleware installation program responsefile, in the following format:-V option_name option_value


The following text is an excerpt of a response file:##########################################################################date time# Replay feature output# ---------------------# This file was built by the Replay feature of InstallAnywhere.# It contains variables that were set by Panels, Consoles or Custom Code.

#Has the license been accepted#-----------------------------LICENSE_ACCEPTED=TRUE

#Choose Install Folder#---------------------USER_INSTALL_DIR=C:\\IBM\\SMP

#Choose Deployment#-----------------SIMPLE=0ADVANCED=1

#Import Middleware Configuration Information#-------------------------------------------MWI_IMPORT_DATA=1MWI_HOSTNAME=127.0.0.1MWI_USER_ID=AdministratorMWI_PASSWORD=MWI_LOCATION=C:\\ibm\\tivoli\\mwi\\workspace

#Database Type#-------------DB_TYPE_DB2=1DB_TYPE_ORACLE=0DB_TYPE_SQLSERVER=0

#Database#--------DB_HOST_NAME=127.0.0.1DB_PORT=50005DB_NAME=maxdb71DB_INSTANCE=ctginst1DB_SCHEMA=maximoDB_USER=maximoDB_PASSWORD=

#Automate Database Configuration#-------------------------------AUTOMATE_DB=1DO_NOT_AUTOMATE_DB=0

#Remote Access Authorization#---------------------------DB_RXA_USER=administratorDB_RXA_PASSWORD=

#DB2 Administration#------------------DB_INSTALL_DIR=C:\\Program Files\\IBM\\SQLLIBDB_ADMIN_USER=db2adminDB_ADMIN_PASSWORD=DB_WIN_SERVICE_USER=db2adminDB_WIN_SERVICE_PASSWORD=

#DB2 Tablespace#--------------


DB_TABLE_SPACE_NAME=MAXDATADB_TABLE_SPACE_SIZE=5000DB_TEMP_TABLE_SPACE_NAME=MAXTEMPDB_TEMP_TABLE_SPACE_SIZE=1000DB_INDEX_TABLE_SPACE_NAME=MAXDATADB_INDEX_TABLE_SPACE_SIZE=5000

#Application Server Type#-----------------------APPLICATION_SERVER_TYPE_WAS=1APPLICATION_SERVER_TYPE_BEA=0

#WebSphere Connectivity#----------------------WAS_HOSTNAME=127.0.0.1WAS_SOAP_PORT=8879

#Automate WebSphere Configuration#--------------------------------AUTOMATE_WAS_CLIENT=1DO_NOT_AUTOMATE_WAS_CLIENT=0

#WebSphere Remote Access Authorization#-------------------------------------WAS_CLIENT_RXA_USER=administratorWAS_CLIENT_RXA_PASSWORD=

#WebSphere Deployment Manager Configuration#------------------------------------------WAS_HOME_DIR=C:\\Program Files\\IBM\\WebSphere\\AppServerWAS_USER=wasadminWAS_PASSWORD=WAS_PROFILE=ctgDmgr01

#WebSphere Application Server Configuration#------------------------------------------WAS_VIRTUAL_HOST_PORT=80WAS_WEB_SERVER_NAME=webserver1WAS_NODE_NAME=ctgNode01WAS_CLUSTER_NAME=MAXIMOCLUSTERWAS_APPLICATION_SERVER_NAME=MXServer

#Security#--------LDAP_OPTION1=0LDAP_OPTION2=0LDAP_OPTION3=1

#Integration Adapter JMS Configuration#-------------------------------------WAS_SIB_DS_NAME=intjmsdsWAS_JMS_PERSIST_DATASTORE=0WAS_JMS_DO_NOT_PERSIST_DATASTORE=1

#SMTP Configuration#------------------SMTP_SERVER=ADMIN_EMAIL=

#Run Configuration Step#----------------------RUN_CONFIG_YES=1RUN_CONFIG_NO=0DEPLOY_EAR_YES=1DEPLOY_EAR_NO=0

#Choose Shortcut Folder


#----------------------USER_SHORTCUTS=C:\\Documents and Settings\\All Users\\

Start Menu\\Programs\\Tivoli Asset Management for IT

#Language Support#----------------INSTALL_LANGUAGE_VALUE=0DO_NOT_INSTALL_LANGUAGE=1

Installing middleware on Solaris, HP-UX, and SUSE Linux EnterpriseServer

Middleware versions that are not installable by the middleware installationprogram are installed by using graphical installation programs that are providedwith each middleware product.

The procedures in this document can be used to manually install the followingmiddleware on Solaris 10 SPARC, HP-UX 11i v2 64 - bit, and SUSE LinuxEnterprise Server 11:v IBM DB2 Enterprise Server Edition 9.7v IBM Tivoli Directory Server 6.2 interim fix 2v IBM WebSphere Application Server Network Deployment 6.1 with fix pack 23 or

27 for SUSE Linux Enterprise Server 11v IBM HTTP Server 6.1 with fix pack 23Related reference

“Hardware and software requirements” on page 3IBM Tivoli Asset Management for IT consists of a collection of components andproducts that work together to form a powerful resource and process managementsystem.

Operating system preparationSome operating system default configuration settings must be changed to providean environment that can host middleware operations.

The steps needed to prepare each newly supported operating system are operatingsystem dependent.

Perform the operating system preparation steps before installing any middleware.

Solaris 10Some of the default kernel configuration parameters on Solaris 10 might not besufficient to run IBM DB2 9.7.

In order to ensure that your Solaris system has required kernel parameters inplace, run the db2osconf utility after you install DB2, but before you create anydatabase objects. See http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp for more information.

HP-UX 11iIn order for IBM DB2 9.7 to run correctly on HP-UX 11i, certain group membershiprequirements must be addressed following the installation of IBM DB2.

After IBM DB2 9.7 has been installed, you need to ensure that the root user hasbeen assigned as a member of the db2iadm1 group.


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp


In order to ensure that your HP-UX system has required kernel parameters inplace, you need to run the db2osconf utility after you install DB2, but before youcreate any database objects. See http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp for more information.

SUSE Linux Enterprise Server 11Linux In order for IBM DB2 9.7 to run correctly on SUSE Linux Enterprise

Server 11, certain prerequisites must be met before the installation of IBM DB2.

Before IBM DB2 9.7 is installed, ensure thatv libaio.so.1 library resides in the /usr/lib64/ directory of the target system.v system environment variable $tmp or $temp is defined on the system.

In order to ensure that your SUSE Linux Enterprise Server system has requiredkernel parameters in place, run the db2osconf utility after you install DB2, butbefore you create any database objects. See http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp for more information.

Installing the middleware componentsAfter the operating system is configured as needed, install the middlewarecomponents.

Middleware components are installed in the following order:1. IBM DB22. IBM Tivoli Directory Server3. IBM WebSphere Application Server Network Deployment4. IBM HTTP Server

Note: The media or Web site you use to install middleware has directory-specificlocations for each supported operating system. The directory structure isos/product.

These commands following display the contents the operating_system/productdirectory.cd osls

Within each os subdirectory are the installation directories for each middlewareproduct.ls solarisDB2-ESE_9.7DB2-ESE_9.7_FP3aTIV-DirectoryServer_6.2.0WS-ESS_6.2WS-WAS_IHS_6.1.0_FP23WS-WAS_ND6.1.0.23_Custom_ISCAE71WS-WAS_ND_6.1.0_SupplementalWS-WAS_Plugins_6.1.0_FP23WS-WAS_UpdateInstaller_7.0.0.3

Installing DB2There are a number of things you need to check to ensure a successful installation.To install IBM DB2, run the db2setup program.






Before you begin

Before you install IBM DB2, review the requirements. See the DB2 informationcenter at http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp foroperating system-specific information.

Before you start the DB2 setup wizard, consider the following prerequisiteconditions:v Typically, if you choose to automate database configuration when you install

Tivoli Asset Management for IT, the user maximo is created for you on the systemhosting the database server. On Solaris, HP-UX, and SUSE Linux EnterpriseServer systems, create the user maximo manually, regardless of whether youchoose to manually configure the database or have the installation programautomatically configure it. Ensure that you have created the maximo user on thedatabase server before installing Tivoli Asset Management for IT.

v db2setup launches a wizard installer so X Window System must be installed andrunning before you start the DB2 installation program. Export your display:export DISPLAY= your_ip_address:0

v If NIS, NIS+, or similar security software is used in your environment, manuallycreate the required DB2 users, before you start the DB2 setup wizard. Refer tothe centralized user-management considerations topic in the DB2 informationcenter. See http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0007059.html

v In general, you can choose to defer some installation activities. For example, ifyou choose to not set up e-mail notifications of database events at installationtime. If you want to defer specific installation activities, select that option, andconfigure them later.

v Some middleware products have specific requirements or conventions foraccount names and other settings. Override the installation defaults as shown ifthe defaults provided are not satisfactory. On panels that prompt for passwords,both the password and its confirmation entry must be specified before theinstaller can continue to the next panel.

About this task

This procedure describes how to perform a typical installation of DB2 on a singlecomputer. If you need to install DB2 components on multiple computers, see theDB2 information center for those instructions.

Databases must contain a single partition and Unicode data (UTF-8).

DB2 is installed, by default, in the /opt/IBM/db2/V9.7 directory (db2_install_dir).

The /opt/IBM/db2/V9.7/logs directory contains a db2install.history file. This filecontains the installation settings used, and errors that occurred during theinstallation process. The vmrfis.history file contains information aboutmaintenance that has been applied to DB2, such as fix packs that have beeninstalled.

The db2setup.log file captures all DB2 installation information including errors.The db2setup.err file captures any error output that is returned by Java (forexample, exceptions and trap information). By default, both logs are created in the/tmp directory, unless you change that location during the installation process.



http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0007059.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0007059.html

Procedure1. Log in as root.2. Copy the IBM DB2 Enterprise Server Edition archive files to a writable disk

and if necessary, unpack the files.

Solaris For SolarisCopy solaris/DB2-ESE_9.7/DB2_ESE_V95_SUN_SPARC.tar

HP�UX For HP-UXCopy hpux-ia64/DB2-ESE_9.7/DB2_ESE_V95_HP-UX_IA64.tar

Linux

v For 32 - bit platforms, copy linux/DB2-ESE_9.7.0/DB2_Enterprise_Svr_Ed_Linux_x86.tar.

v For 64 - bit platforms, copy linux64/DB2-ESE_9.7/DB2_ESE_V95_Linux_x86-64.tar.

3. Change to the directory where you copied the tar file and run the followingcommand:- xvf tar_file_name.tar

4. Extract the file DB2_Enterp_Svr_OEM_Activation.zip into an appropriatedirectory. For example, for Solaris, solaris64/DB2-ESE_9.7/

5. Change to the ese directory.6. Start the installer. Type ./db2setup.7. From the Launchpad, select Install a Product.8. Under the DB2 Enterprise Server Edition heading, click Install New.9. Accept the license agreement.

10. From the Welcome panel, click Next.11. In general, accept all defaults, except where you need to provide custom

values. For example, the e-mail address of the recipient of e-mail notificationsof database events defaults to host_name@local_server_name. This value needsto be changed to a valid e-mail address if you choose to enable SMTPnotifications. You can also change it at a later time.

12. On the Start copying files and create response file panel, click Finish toinitiate the installation.

13. Register the DB2 server license:a. Use the DB2 license management tool command to apply the license:

cd /opt/ibm/db2/adm/./db2licm -a full_path_to_the_license_file

The license file can be found in the folder in which you extracted thelicense files.

Solaris For example, the license file could be located insolaris/DB2-ESE_9.5/DB2_Enterp_Svr_OEM_Activation/db2/license/db2ese_o.lic.

b. Verify that the license was installed successfully:./db2licm -l

This command might result in output like the following commands:Product name: "DB2 Enterprise Server Edition"License type: "Restricted"Expiry date: "Permanent"Product identifier: "db2ese"Version information: "9.7"


Installing DB2 fix packs:

Installing the fix pack for IBM DB2 ensures that it is up to date with the latestfixes.

Before you begin

Stop all instances of DB2 before installing a fix pack.1. Log in as root.2. Run db2ilist to view all instances.3. Become (su) the instance owner of a DB2 account.4. Stop each instance, use db2stop instance_name for each instance.

Procedure

1. Copy the fix pack tar file to a writeable disk.

Solaris On SolarisCopy DB2-ESE_9.7_FP3a/v9.7fp3a_sun64_server.tar.gz

HP�UX On HP-UXCopy DB2-ESE_9.7_FP3a/v9.7fp3a_hpipf64_server.tar.gz

Linux On SUSE Linux Enterprise Server

v For 32-bit platforms, copy DB2-ESE_9.1.0_FP8/v9fp8_linux_ese.tar.gz

v For 64-bit platforms, copy DB2-ESE_9.7_FP3a/v9.5fp3a_linuxx64_server.tar.gz.

2. Uncompress the file:gzip -dfv fixpack_name.tar.gz

3. Unpack the file:tar -xvf fixpack_name.tar

4. Change to the /server directory.5. To start the fix pack installation, type ./installFixPack -bdb2_install_dir,

where db2_install_dir is the location of the DB2 product that you want toupdate. For example, /opt/IBM/db2/V9.7.

6. Run the update command on each instance:db2_install_dir/instance_name/db2iupdt -e

7. Run the db2_install_dir/instance_name/dasupdt command.8. Restart each instance that you stopped before you installed the fix pack.

Installing IBM Tivoli Directory ServerIBM Tivoli Directory Server is typically installed on a computer that is not hostingother middleware products.

Procedure1. Log in as root.2. Copy the tar files for IBM Tivoli Directory Server to a writable disk. The files

are in the TIV-DirectoryServer_6.2.0 directory.

Solaris For SolarisCopy the C1N9LML.tar and C1N9QML.tar files fromMiddleware/solaris/TIV-DirectoryServer_6.2.0.


HP�UX For HP-UXCopy the C1N9LML.tar and C1N9QML.tar files fromMiddleware/hpux-ia64/TIV-DirectoryServer_6.2.0

Linux For SUSE Linux Enterprise Server

v For 32-bit platforms, copy the tds62-linux-ia32-base.tar filefrom linux/TIV-DirectoryServer_6.2.0

v For 64-bit platforms, copy the tds62-linux-x86_64-base.tar filefrom linux64/TIVDirectoryServer_ 6.2.0

3. Unpack the files. Solaris For example:tar -xvf C1N9LML.tartar -xvf C1N9QML.tar

4. Change to the /tdsV6.2/tds directory, and then type ./install_tds.bin

If you prefer, you can specify a temporary directory other than the systemtemporary directory. To use this option, change directories to the appropriatedirectory and type the following command at a command prompt:./install_tds.bin -is:tempdir directory

where directory is the directory you want to use for temporary space. Be surethat you have at least 400 MB of free space in this directory. For example:./install_tds.bin -is:tempdir /opt/tmp

5. When the installation wizard starts, select a language to use for theinstallation process, accept the license agreement, and choose a Custominstallation.

6. If the DB2, Embedded WebSphere Application Server, and Tivoli DirectoryIntegrator feature options appear, clear them, and then click Next.You install these products separately. Select the following options: C Client,Java Client, Web Administration Tool, Proxy Server, Server.

7. From the Select WebSphere Application Server panel, select Do not specify. Iwill manually deploy at a later time, then click Next.

8. Click Install.9. Click Finish.

The IBM Tivoli Directory Server instance creation tool launches.10. Create the idsccmdb instance. Refer to “Manually configuring Directory

Server” on page 147 for details. When creating the idsccmdb user, include it asa member of the root, db2iadm1, and idsldap groups, where root is theprimary group for the idsccmdb user.

11. Apply the interim fix file operating_system/TIV-DirectoryServer_6.2.0.0-

TIV-ITDS-operating system-IF0002.tar Solaris For example, this file isfound in the 6.2.0.0-TIV-ITDS-SolarisSparc-IF0002.tar interim fix file,which is found in the solaris64/TIV-DirectoryServer_6.2.0 directory of theproduct media. Uncompress the interim fix file into a temporary directory andthen run the ./idsinstall -u command.

Important: If you are installing IBM Tivoli Directory Server 6.2 on SUSELinux Enterprise Server 11, obtain and apply the product fix pack 2 or later.

12. Start the directory server, type the following commands:a. /opt/ibm/ldap/V6.2/sbin/idsdiradm -I idsccmdb

b. /opt/ibm/ldap/V6.2/sbin/idsdirctl -D admin_user_id -wadmin_user_password


Installing WebSphere Application Server Network DeploymentIBM WebSphere Application Server Network Deployment must be installed, andyou need to create two profiles that are used at a later time.

Before you begin

Important: If you are installing WebSphere Application Server NetworkDeployment 6.1 on SUSE Linux Enterprise Server 11, you need to obtain and applythe product fix pack 27, or later.

Procedure1. Log in as root.2. Copy the WebSphere Application Server Network Deployment compressed file

to a writable disk. The file is in the WS-WAS_ND_6.1.0.23_Custom_ISCAE71directory.

Solaris For SolarisCopy WS-WAS_ND_6.1.0.23_Custom_ISCAE71/WAS-ND_Solaris-Sparc-Custom_v6.1023_ISC7106.tar.gz

HP�UX For HP-UXCopy WS-WAS_ND_6.1.0.23_Custom_ISCAE71/WAS-ND_HpuxIA64_Custom_v6.1023_ISC7106.tar.gz


v For 32 - bit platforms, copy WS-WAS_ND_6.1.0.23_Custom_ISCAE71/WASND_ LinuxIA32_Custom_v61023_ISC7106.tar.gz

v For 64 - bit platforms, copy WS-WAS_ND_6.1.0.23_Custom_ISCAE71/WASND_ LinuxIA64_Custom_v61023_ISC7106.tar.gz.

3. Uncompress and unpack the file:gzip -dfv file_name.gz | tar xvf -

4. Change to the directory where you unpacked the tar file.5. Change to the was_install_dir directory.6. Type ./install.7. Accept the license agreement and accept the defaults provided unless you

have a specific reason to change them.8. On the Installation directory panel, accept the default installation directory.

The default directory is /opt/IBM/WebSphere/AppServer.If you change the installation directory, do not use symbolic links as thedestination directory and do not add space characters to the path.

9. From the WebSphere Application Server Network Deployment environmentspanel, select None as your environment, and click Next.Selecting None means that you plan to create the deployment cell,deployment manager profile, and the application server profile using theprofile management tool.

10. Click Yes to indicate that you want to proceed.11. Advance to the end of the installation and click Finish.

Creating profiles:


The 64 - bit version of WebSphere Application Server Network Deploymentincludes the manageprofiles command-line tool which you use to create profiles.For 32 - bit platforms, use the profile creation wizard.

Before you begin

Ensure that you are familiar with the character limitations for commands or theshell you are using. In some cases, you might have to enter commands in order toavoid exceeding these limitations. Refer to WebSphere Application Server NetworkDeployment product documentation for more information about entering lengthycommands on more than one line.

About this task

The following commands can be useful for managing profiles:

Table 13. Profile commands

Task Command

Delete a profile was_install_dir/bin/manageprofiles.sh -delete-profileNameprofile_name

Refresh the profile registry (for example, afterdeleting a profile)

was_install_dir/bin/manageprofiles.sh-validateAndUpdateRegistry

List existing profiles was_install_dir/bin/manageprofiles.sh-listProfiles

Procedure

1. Source the setupCmdLine.sh script in the bin directory of the was_install_dirfolder to set the WebSphere Application Server Network Deploymentenvironment to the configuration instance. was_install_dir is typically in/opt/IBM/WebSphere/AppServer.. was_install_dir/bin/setupCmdLine.sh

2. Create a profile ports file for the ctgDmgr01 profile. This file is used on themanageprofiles command to set the ports that are used by this profile.

Note: It is important that you ensure no spaces appear after any value in thisfile. This circumstance can sometimes occur when cutting and pasting anexample. If there is an extra space trailing any of the values, as can happenwhen cutting and pasting an example, WebSphere Application Server usesthat space as the last character of that value. For example, For example, youspecify the value WC_adminhost=9060, but an extra space is typed after 9060.The value is interpreted as WC_adminhost=9060<sp> (where <sp> represents aspace character).a. Create a new text file named _portdef_DMgr.props and enter the following

text:CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS= 9403WC_adminhost= 9060DCS_UNICAST_ADDRESS= 9352BOOTSTRAP_ADDRESS= 9809SAS_SSL_SERVERAUTH_LISTENER_ADDRESS= 9401CELL_DISCOVERY_ADDRESS= 7277SOAP_CONNECTOR_ADDRESS= 8879ORB_LISTENER_ADDRESS= 9100CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS= 9402WC_adminhost_secure= 9043

b. Place the file in the was_install_dir directory.


3. Create the ctgDmgr01 profile using the manageprofiles command. Type thefollowing command, all on one line, with a space between each entry:was_install_dir/bin/manageprofiles.sh

-create-templatePath was_install_dir/profileTemplates/dmgr-hostName your_fully_qualified_host-profileName ctgDmgr01-profilePath was_install_dir/profiles/ctgDmgr01-portsFile was_install_dir/_portdef_DMgr.props-cellName ctgCell01-nodeName ctgCellManager01-enableAdminSecurity "false"

4. Start the ctgDmgr01 server:was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

5. Create a profile ports file for the ctgAppSrv01 profile. This file is used by themanageprofiles command to set the ports that are used by this profile.a. Open a new text file named _portdef_AppSvr.props and enter the

following text:CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS= 9201DCS_UNICAST_ADDRESS= 9353NODE_DISCOVERY_ADDRESS= 7272NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS= 5001BOOTSTRAP_ADDRESS= 2809SAS_SSL_SERVERAUTH_LISTENER_ADDRESS= 9901SOAP_CONNECTOR_ADDRESS= 8878NODE_MULTICAST_DISCOVERY_ADDRESS= 5000ORB_LISTENER_ADDRESS= 9101CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS= 9202

b. Place the file in the was_install_dir directory.6. Create the ctgAppSrv01 profile using the manageprofiles command:

was_install_dir/bin/manageprofiles.sh-create

-templatePath was_install_dir/profileTemplates/managed-hostName your_fully_qualified_host-profileName ctgAppSrv01-profilePath was_install_dir/profiles/ctgAppSrv01-cellName ctgNodeCell01-nodeName ctgNode01-portsFile was_install_dir/_portdef_AppSvr.props-dmgrHost your_fully_qualified_host-dmgrPort 8879-isDefault

7. Start the ctgAppSrv01 node.was_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

8. Augment the ctgDmgr01 profile:was_install_dir/bin/manageprofiles.sh

-augment-templatePath was_install_dir/profileTemplates/iscae71-profileName ctgDmgr01-serverName dmgr

9. Restart servers.was_install_dir/profiles/ctgDmgr01/bin/stopManager.shwas_install_dir/profiles/ctgDmgr01/bin/startManager.shwas_install_dir/profiles/ctgAppSrv01/bin/stopNode.shwas_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

10. Launch firststeps.sh and select the Installation Verification option toconfirm that your server has been properly installed and started.was_install_dir/profiles/ctgDmgr01/firststeps/firststeps.sh


Installing update installer:

This procedure is optional; it can be performed now or later, when you want touse the update installer to apply maintenance. During the initial installation ofmiddleware, maintenance is not applied using the update installer. The updateinstaller simplifies maintenance of IBM WebSphere Application Server NetworkDeployment and its related components, such as the IBM HTTP Server plug-in andfix packs.

Before you begin

Complete documentation for the update installer is at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tins_updi_install.html. Review theprerequisites before installing the update installer.

Procedure

1. Copy the update installer archive file to a writable disk. The file is in theWS-WAS_UpdateInstaller_7.0.0.3 directory.

Solaris For SolarisCopy 7.0.0.3-WS-UPDI-SolarisSparc64.zip

HP�UX For HP-UXCopy 7.0.0.3-WS-UPDI-HpuxIA64.zip


v For 32 - bit platforms, copy 7.0.0.3-WS-UPDI-LinuxIA32.zip

v For 64 - bit platforms, copy 7.0.0.3-WS-UPDI-HpuxIA64.zip

2. Uncompress the file. Type the following command:unzip file_name.zip

3. Change to the directory containing the uncompressed files and type: ./install.4. Accept the license agreement.5. The default installation directory is /usr/IBM/WebSphere/UpdateInstaller.

Change it if you need to do so; otherwise accept the default location.6. Before you finish the installation, clear the option to Launch IBM Update

Installer for WebSphere software on exit.

Installing and configuring IBM HTTP Server:

This procedure provides task information for manually installing and configuringIBM HTTP Server.

Procedure

1. Log on as root, on the computer where you installed WebSphere ApplicationServer Network Deployment.

2. Log in to the WebSphere Administrative Console and ensure the ctgDmgr01deployment manager is running and that the SOAP port is set to listen at thecorrect port (8879 is the default).If the deployment manager needs to be started, use the following command:was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

3. Copy the IBM HTTP Server compressed file to a writable disk.


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tins_updi_install.html



Solaris For SolarisCopy Middleware/solaris/WS-WAS_ND_6.1.0_Supplemental/C943UML.tar.gz

HP�UX For HP-UXCopy hpux-ia64/WS-WAS_ND_6.1.0_Supplemental\C88TNML.tar.gz


v For 32 - bit platforms, copy linux/WS-WAS_ND_6.1.0_Supplemental/C88T0ML.tar.gz

v For 64 - bit platforms, copy linux64/WSWAS_ND_6.1.0_Supplemental/C1G36ML.tar.gz

4. Uncompress the archive file.5. Extract the contents of the tar file.6. Change to the IBM HTTP Server directory and start the installation program:

./install

7. From the Welcome panel, click Next.8. Accept the license agreement and click Next to display the installation root

directory panel.9. From the System prerequisites check panel, click Next.

10. Specify the install location, the default is /opt/IBM/HTTPServer, and click Next.11. From the Port Values Assignment panel, specify the following values, and

click Next.

HTTP Port80

HTTP Administration Port8008

12. From the HTTP Administration Server Authentication panel, specify thefollowing values, and click Next.

Create a user ID for IBM HTTP administration server authenticationEnable this option by selecting this check box.

User IDSpecify wasadmin

PasswordEnter the password for the wasadmin user.

13. From the Setup HTTP Administration Server panel, specify the followingvalues, and click Next.

Setup IBM HTTP administration server to administer IBM HTTP ServerEnable this option by selecting this check box.

Create a unique user ID and group for IBM HTTP Server administrationEnable this option by selecting this check box.

User IDSpecify wasadmin.

Group Specify ihsadmin

14. From the IBM HTTP Server plug-in for WebSphere Application Server panel,specify the following values, and click Next.

Install the IBM HTTP Server Plug-in for IBM WebSphere ApplicationServer Enable or clear this check box to disable this option as is appropriate


for your configuration. In an environment where you have multipledeployment manager profiles, it is more practical to run the Webserver plug-ins installation task separately by running the plug-ininstallation program after exiting the IBM HTTP Server installationprogram. However, if your WebSphere Application Serverenvironment only contains a single deployment manager profile, youcan leave the WebSphere Application Server plug-in option selected.When it is selected, the Web server plug-ins installation task startswhen you click Next.

For more information about deployment scenarios for IBM HTTPServer, refer to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/welcome_ihs.html

If you decide to install the HTTP Server plug-in now, you need toconfigure it. Perform the following steps to configure the plug-in.

a. Stop and start the deployment manager:was_install_dir/profiles/ctgDmgr01/bin/stopManager.sh

was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

b. Copy the /opt/IBM/HTTPServer/Plugins/bin/configurewebserver1.sh fileto was_install_dir/bin/

c. Change directory to was_install_dir/bin and then execute the followingcommand:./configurewebserver1.sh

d. Start the HTTP servers:/opt/IBM/HTTPServer/bin/adminctl start/opt/IBM/HTTPServer/bin/apachectl start

e. Log in to the WebSphere Administrative Console and ensure thatwebserver1 has started.

Installing IBM HTTP Server fix packs:

HTTP server fix pack 23 needs to be installed to update the base installation of theHTTP server to the latest maintenance level.

Before you begin

Important: If you are installing IBM HTTP Server 6.1 on SUSE Linux EnterpriseServer 11, obtain and apply the product fix pack 27 or later.

Procedure

1. Copy the fix pack file to the /opt/IBM/HTTPServer/maintenance directory.Create this directory if it does not exist.

Solaris For SolarisCopy Middleware\solaris\WS-WAS_IHS_6.1.0_FP23\6.1.0-WS-IHS-SolarisSparc64-FP0000023.pak

HP�UX For HP-UXCopy hpux-ia64/WS-WAS_IHS_6.1.0_FP23/6.1.0-WS-IHS-HpuxIA64-FP0000023.pak



http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/welcome_ihs.html



v For 32 - bit platforms, copy linux/WS-WAS_ND_6.1.0_Supplemental/C88T0ML.tar.gz

v For 64 - bit platforms, copy linux64/WSWAS_ ND_6.1.0_Supplemental/C1G36ML.tar.gz.

2. Stop the HTTP server. Type /opt/IBM/IBMHttpServer/bin/.apachectl stop

3. Stop WebSphere Application Server and the managed nodes using thefollowing commands.a. was_install_dir/profiles/ctgAppSrv01/bin/stopNode.sh

b. was_install_dir/profiles/ctgDmgr01/bin/stopManager.sh

4. Install the fix pack. Type /opt/IBM/WebSphere/UpdateInstaller/.update.sh.a. When the update installer wizard starts, select IBM HTTP Server from the

Directory name drop down list.b. Click Next to install the maintenance package.c. Browse to the /opt/IBM/HTTPServer directory and select the fix pack (.pak)

file from the file list; click Open and then click Next on the MaintenancePackage Selection screen.

5. Start the HTTP server. Type /opt/IBM/IBMHttpServer/bin/.apachectl start

6. Restart WebSphere Application Server and the managed nodes:a. was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

b. was_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

Installing WebSphere plug-in:

This procedure provides task information for manually installing and configuringIBM WebSphere Application Server plug-in for IBM HTTP Server. This procedureis optional if you chose to install and configure the WebSphere plug-in when youinstalled the IBM HTTP Server.

Procedure

1. Log on as root to the computer where you have installed IBM WebSphereApplication Server Network Deployment.

2. Change to the directory where you previously extracted the tar file (when youinstalled IBM HTTP Server).

Solaris

For example, for Solaris, this path might be solaris64/WS-WAS_ND_6.1.0_Supplemental/plugin.

3. Change to the plugin directory.4. From a command line, launch the WebSphere Application Server plug-in

installation program../install

5. On the Welcome panel, clear the option to learn more about the Installationroadmap: Overview and installation scenarios. Click Next.

6. Accept the license agreement and click Next.7. From the plug-in selection panel, select the IBM HTTP Server V6 or 6.1

plug-in, and then click Next.8. From the installation scenario panel, select WebSphere Application Server

machine (local), and then click Next.9. Accept or change the installation directory (http_server_install_dir); the

default is /opt/IBM/HTTPServer/Plugins1. Click Next.


10. Specify the location where you installed the application server(was_install_dir); the default is /opt/IBM/WebSphere/AppServer. Click Next.

11. From the Select Profile panel, select ctgDmgr01 from the drop-down list, andthen click Next.

12. From the Web server configuration file panel, specify the followinginformation:

Select the existing IBM HTTP Server httpd.conf fileBrowse to the location of the httpd.conf file; the default is/opt/IBM/HTTPServer/conf/httpd.conf.

Specify the Web server portThe default is port 80.

Clicking Next might produce warning message that indicates that the selectedIBM HTTP Server configuration file already contains plug-in entries. If youproceed, this configuration file is updated with a new plugin-cfg.xml filelocation. Click OK to proceed.

13. From the Web server definition panel, specify a unique Web server definitionname; the default name (webserver1) is satisfactory.

14. Accept the default Web server plug-in configuration file name(plugin-cfg.xml and location.

15. Click Next to acknowledge the manual configuration steps.16. From the installation summary panel, click Next.17. When the installation is complete, click Finish.18. Stop and start the deployment manager:

was_install_dir/profiles/ctgDmgr01/bin/stopManager.sh

was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

19. Copy the /opt/IBM/HTTPServer/Plugins/bin/configurewebserver1.sh file towas_install_dir/bin/

20. Change directory to was_install_dir/bin and then execute the followingcommand:./configurewebserver1.sh

21. Start the HTTP servers:/opt/IBM/HTTPServer/bin/adminctl start/opt/IBM/HTTPServer/bin/apachectl start

22. Log in to WebSphere Administrative Console and ensure that webserver1 hasstarted.

Installing WebSphere plug-in fix packs:

The WebSphere Application Server plug-in fix pack 23 needs to be installed toupdate the base installation of the plug-in to the latest maintenance level.

Procedure

1. Copy the fix pack file to the /opt/IBM/WebSphere/UpdateInstaller/maintenancedirectory. Create this directory if it does not exist.

Solaris For SolarisCopy Middleware/solaris/WS-WAS_Plugins_6.1.0_FP23/6.1.0-WS-PLG-SolarisSparc64-FP0000023.pak


HP�UX For HP-UXCopy hpux-ia64/WS-WAS_Plugins_6.1.0_FP23/6.1.0-WS-PLG-HpuxIA64-FP0000023.pak


v For 32 - bit platforms, copy linux/WS-WAS_Plugins_6.1.0_FP23/6.1.0-WSPLG- LinuxX32-FP0000023.pak

v For 64 - bit platforms, copy linux64/WS-WAS_Plugins_6.1.0_FP23/6.1.0-WS-PLG-LinuxX64- FP0000023.pak

2. Stop the HTTP server. Type /opt/IBM/HTTPServer/bin/apachectl stop

3. Stop the administration server. Type /opt/IBM/HttpServer/bin/adminctl stop.4. Stop WebSphere Application Server and the managed nodes using the

following commands.a. was_install_dir/profiles/ctgAppSrv01/bin/stopNode.sh


5. Install the fix pack.a. Launch the update installer wizard:

/opt/IBM/WebSphere/UpdateInstaller/update.sh

b. Click Next.c. From the Product Selection panel, select the IBM HTTP Server Plugins1

directory by browsing to the /opt/IBM/HTTPServer/Plugins1 directory, andthen clicking Next.

d. From the Maintenance Operation Selection panel, select Install maintenancepackage, and click Next.

e. From the Maintenance Package Directory Selection panel, browse to the/opt/IBM/HTTPServer/maintenance directory, and then click Next.

f. From the Available Maintenance Package to Install panel, click SelectRecommended Updates, select the target update, and click Next.

g. On the Installation Summary screen, click Next to begin the installation ofthe critical fixes.

6. Start the HTTP server. Type /opt/IBM/IBMHttpServer/bin/apachectl start

7. Start the administration server. Type /opt/IBM/HTTPServer/bin/adminctl start.8. Restart WebSphere Application Server and the managed nodes:

a. was_install_dir/profiles/ctgDmgr01/bin/startManager.sh


Configuring Virtual Member Manager on WebSphereApplication Server

Virtual Member Manager (VMM) provides you with the ability to access andmaintain user data in multiple repositories, and federate that data into a singlevirtual repository.

Before you begin

Before configuring Virtual Member Manager, you might consider creating a systembackup image. It allows you to restore the system to a pre-VMM state, whichwould allow you to reconfigure Virtual Member Manager to use a different LDAPserver if you chose to relocate your LDAP data in the future.


About this task

Refer to “Manually configuring Virtual Member Manager on IBM WebSphereApplication Server” on page 161 for information about adding an IBM TivoliDirectory Server repository to Virtual Member Manager. It is a required task thatmust be performed.

To add an LDAP directory to the Virtual Member Manager virtual repository, youneed to first add the LDAP directory to the list of repositories available forconfiguration for the federated repository and then add the root of baseEntries to asearch base within the LDAP directory. Multiple base entries can be added withdifferent search bases for a single LDAP directory.

Configuring the authentication serviceThe authentication service provides the ability to “launch-in-context”.Launch-in-context provides a means for launching from an application, like TivoliAsset Management for IT, to the user interface of an external Web-basedapplication such as Software Knowledge Base Toolkit. Both applications must usethe same directory server for authentication, and the external application musthave the authentication client installed. You authenticate only once, to the serverhosting the client; you do not need to authenticate again to the external applicationwhen they launch-in-context to it.

Procedure1. Open a command prompt on the server that hosts in IBM WebSphere

Application Server Network Deployment.2. Change to was_install_dir/bin.3. Log on to the wsadmin shell using the following command. If you did not

change the wsadmin user name or password when you installed the applicationserver, the default is wsadmin for the user and wsadmin for the password../wsadmin.sh

4. Verify that you do not already have authentication services deployed:wsadmin>$AdminApp view authnsvc_ctges

If the command returns a message that indicates that the authnsvc_ctgesapplication does not exist, authentication services have not been deployed.

5. Open a new X Window System and copy the os/WS-ESS_6.1_GA/

IBMESSAuthnSvc.ear file to a local drive. Solaris For example, this file islocated in solaris64/WS-ESS_6.1_GA/IBMESSAuthnSvc.ear

6. Return to the wsadmin shell window and deploy the IBMESSAuthnSvc.ear usingthe following command. Type all characters as shown.wsadmin>$AdminApp install file_path/IBMESSAuthnSvc.ear"-usedefaultbindings -deployws -appname authnsvc_ctges"

Solaris For example, file_path could be solaris/WS-ESS_6.2/.7. Save the configuration:

wsadmin>$AdminConfig save

8. Exit the wsadmin shell by typing exit.9. Stop WebSphere Application Server and the managed nodes using the

following commands.a. was_install_dir/profiles/ctgAppSrv01/bin/stopNode.sh



10. Copy the operating_system//WS-ESS_6.2/com.ibm.security.ess.server_config.6.2.0.jar file to thewas_install_dir/plugins directory.This file is located in the operating_system\WS-ESS_6.2 directory on themiddleware DVD.

11. Restart WebSphere Application Server and the managed nodes:a. was_install_dir/profiles/ctgDmgr01/bin/startManager.sh


12. Change to was_install_dir/bin.

13. Type ./wsadmin.sh to log in to the wsadmin shell.14. Configure the service, type the following command at the wsadmin prompt:

$AdminTask configureESS.

15. Type the wsadmin command to verify that the service is configured:$AdminTask isESSConfigured. If true is returned, the service is configured.

16. Create a Lightweight Third Party Authentication (LTPA) key, which is required tosupport single sign-on, by typing the following command. The password thatyou specify is the LTPA key password. Record it in a secure place. If the keypassword is lost, you need to create a new key. Ensure all clients that connectto the service use the export key file that you create in Step 19.wsadmin>$AdminTask createESSLTPAKeys "-password password"

Note: If the key password is every lost, you need to create a new key. Ensureall clients connecting to the service use the new export key file you generate.

17. Synchronize the configuration.wsadmin>$AdminConfig savewsadmin>set dmgr [$AdminControl completeObjectName type=DeploymentManager,*]wsadmin>$AdminControl invoke $dmgr syncActiveNodes truewsadmin>quit

18. Stop and restart WebSphere Application Server and the managed nodes:a. was_install_dir/profiles/ctgAppSrv01/bin/stopNode.sh


c. was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

d. was_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

19. Export the newly created key:# wsadminwsadmin>$AdminTask exportESSLTPAKeys "-pathname file_path"

For example,wsadmin>$AdminTask exportESSLTPAKeys "-pathname /root/avenESSLTPAKeyFile.exported"

Related tasks

“Encountering the CTGIN9042E SOAP connection problem” on page 298This error might occurs during the execution of the WebSphere Application ServerNetwork Deployment 6.1 configuration or authentication service configurationsteps.



Chapter 5. Installation program overview

The IBM Tivoli Asset Management for IT installation program provides aninterface for installing and deploying Tivoli Asset Management for IT. Theinstallation program records choices you make about your deployment andconfiguration parameters associated with those choices, and then installs anddeploys the product based upon the information you entered.

Note: Run the installation program only from supported operating systems for theadministrative workstation

There are two installation paths available to you when installing Tivoli AssetManagement for IT.

SimpleA simple deployment consists of installing all middleware on one system.You do not have the option of using existing middleware within yourorganization with Tivoli Asset Management for IT. All middleware musthave been installed on the system using the middleware installer, usingdefault values. Tivoli Asset Management for IT is installed using defaultvalues provided by the middleware and Tivoli Asset Management for ITinstallation programs.

For a list of values being set when using this option, refer to “Tivoli AssetManagement for IT simple install path values” on page 83. If you intend tooverride default values used by the simple deployment path, you need touse the custom deployment path instead.

Note: On choosing a simple deployment, you might encounter this errormessage:CTGIN2375E: J2EE application security not enabled in J2EE application server

Make sure that you have the WebSphere Application Server securityswitched on. Refer to the WebSphere Application Server InformationCenter for instructions.

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp.

CustomA custom deployment typically involves deploying Tivoli AssetManagement for IT across several systems, some of which probablyalready host middleware products that you want to use with yourdeployment. Deploying through the custom installation path also allowsyou to modify default installation values.

This deployment option does not require you to spread the Tivoli AssetManagement for IT deployment across several systems. You can enter thename of the local host as the destination for all product components thatneed to be installed using the middleware installer and the Tivoli AssetManagement for IT installation program..

The Tivoli Asset Management for IT installation program can automate theconfiguration of middleware. If you choose not to have the installation programautomatically configure middleware, configure that piece of middleware manuallybefore the installation of Tivoli Asset Management for IT.


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

Important: When entering LDAP values for installation panel fields, entries inLDIF files, or values you enter directly into a directory instance using the directoryserver tools, be aware of the product-specific syntax rules for using specialcharacters in an LDAP string. In most cases, in order to make them readable by thedirectory server, special characters must be preceded by an escapecharacter. Failing to escape special characters contained in an LDAP string usedwith Tivoli Asset Management for IT results in installation errors.

Many directory server products consider a blank space as a special character that ispart of the LDAP string. Therefore, if you mistakenly enter an LDAP string thatcontains a blank, at the end of a field value, for example, and you do not precedethe blank character with an escape character, you encounter errors that are difficultto troubleshoot.

Refer to the product documentation for your directory server for more informationabout special characters in LDAP strings.

Information that you enter into the Tivoli Asset Management for IT installationprogram is stored in the maximo.properties file and the Maximo database. Thesevalues are populated into the panel fields of the installation program onsubsequent uses of the program. Therefore, when you cancel the installationprogram after entering values across several installation panels, the installationprogram recalls the values the next time you start up the installation program(except for the Tivoli Asset Management for IT installation directorytamit_install_dir and the shortcut option chosen). You can restore the defaultvalues in the installation program by deleting tamit_install_dir/maximo/applications/maximo/properties/maximo.properties.Related reference

Chapter 15, “Installation properties,” on page 269Installation properties are recorded in properties files during a deployment and areused by future install-related actions.

Installation prerequisitesBefore you start to install IBM Tivoli Asset Management for IT, make sure that theprerequisites are met.

IBM DB2

If you use DB2 database with Tivoli Asset Management for IT, and you want touse the fully automated database configuration capabilities of the installationprogram, ensure that the following conditions are met:v If DB2 is installed on a Linux or UNIX system, you must create the instance user

and the home directory for the user on the DB2 server.v The database instance owner home directory must have 8 GB of space available

regardless of whether a database is installed in that location.v The user ID for the DB2 instance administrator must have SYSADM

(administration) authority. You enter this user ID on the DB2 Administrationscreen and on the Remote Access Authorization screen of the Tivoli AssetManagement for IT installation program. This ID must belong to the groupdefined by the sysadm_group configuration parameter for the DB2 instance youplan to use.

– Windows For example, the user needs to belong to the DB2ADMNS group.

– Linux For example, the user needs to belong to the db2fenc1 group.


See the DB2 product documentation for information about creating a user withSYSADM (administration) authority on the DB2 server. You must add root to agroup with SYSADM authority for UNIX systems.

v Linux Add root to the DB2GRP1 group before starting the installationprogram.

v To avoid high system memory usage by DB2, you can set the following DB2property and then restart the DB2 server:db2 update dbm cfg using KEEPFENCED NO

v If you plan to install Tivoli Asset Management for IT in a language other thanEnglish, you must accept the default values for database table space size andindex table space size and these values are displayed as null during theinstallation. If you want to customize the table space sizes, you have threeoptions. Run the Tivoli Asset Management for IT installation program inEnglish, manually configure the database, or modify the table space sizes afterinstallation

For more information about creating DB2 users, see the IBM DB2 productdocumentation:


Other conditions

Ensure that you have addressed the following prerequisite conditions:v On the administrative workstation, temporarily shut down any non-critical

processes that could have a negative effect on the installation, such as anti-virussoftware.

v For Linux and UNIX systems with middleware installed, the commandhostname -f must return a fully qualified host name. If necessary, consult thedocumentation for your operating system.

v If you experience problems with the user interface of the installation programwhen installing on AIX 6.x systems remotely, reattempt the installation locally onthe system through the console or an x terminal.

v Ensure that the middleware environment is installed and running properly. Seethe instructions on restarting middleware if you need to do so.

v Enable a remote execution and access service on every system with middlewareinstalled. Each remote system must support a remote access protocol and acceptremote logins from a user name and password configured on the target server.Remote access protocols include SSH and Windows SMB. If the remote system isa Windows server, you must configure remote execution and access to use SMB.

v Database users and database instance names for DB2 and Oracle cannot containspaces.

v If you plan to take advantage of the installation program feature that automatesthe configuration of Tivoli Asset Management for IT middleware, enable aRemote Execution and Access (RXA) service for each system on which youintend to install the middleware. RXA requires that the target system enable atleast one of the protocols supported by RXA, which includes rsh, REXEC, SSH,and Windows SMB. Before you start the installation program, ensure that one ofthese protocols is running and accepting remote logins using a user name andpassword configured on the target computer.

v Windows If the remote system is a Windows computer, configure RXA to workover SMB.

Chapter 5. Installation overview 81


v AIX Default installations of AIX systems might not include a suitableprotocol and must have RXA compatible protocols enabled.

v Windows If you are using Microsoft Active Directory to secure WebSphereApplication Server, ensure the users and groups listed in “Manually configuringMicrosoft Active Directory” on page 151 have been manually created in theMicrosoft Active Directory instance.

v If appropriate, ensure that Oracle 9i, 10g or 11g (see “Hardware and softwarerequirements” on page 3 for comparison).

v If appropriate, ensure that Microsoft SQL Server 2008 is installed.v Tivoli Asset Management for IT uses port 1433 when configured with SQL

Server. By default, this port is not enabled. Enable this port. Refer tohttp://msdn.microsoft.com/en-us/library/ms177440.aspx for instructions.

v If you intend to perform multiple installations using the same administrativeworkstation, review this information in the Planning to install information beforeyou begin the installation. If you do not follow those instructions, it might notbe possible to use the same administrative workstation for multiple installations.

v If you are installing on a system using a system ID that contains Russianlanguage characters, the installation fails with error message CTGIN2289E whenattempting to install language packages. This circumstance causes a WebSphereApplication Server Network Deployment connection failure reporting errorCTGIN0158E. To avoid this problem, install the product using a user ID withadministrative authority that contains only English language characters. See thetroubleshooting chapter for information about errors that occur during theinstallation.

v When you are installing the product, enter the fully qualified host name of thesystem for all host name values.

v While Tivoli Asset Management for IT itself supports the Turkish language, theinstallation program does not support Turkish. Furthermore, the administrativeworkstation must not be set to the Turkish locale before or after installing TivoliAsset Management for IT. After Tivoli Asset Management for IT has beeninstalled successfully, Turkish can be deployed as either the base or as anadditional language using the language pack installation program. Theadministrative workstation must remain set to a non-Turkish locale toaccommodate future product deployment actions.

Creating a maxdemo database

Automatic configuration creates an empty Maximo database on the system. Youcan create a maxdemo database, including sample data, during the installation. Tocreate a maxdemo database, complete either of following two procedures:v Enter a command to create a maxdemo database:

1. In the command line, navigate to the directory where the Tivoli AssetManagement for IT files are extracted.

2. Change to the install\MAM\Install\new folder.3. On a 32-bit Windows system, run the following command:

install.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yesd

On a 64-bit Windows system, run the following command:install_win64.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes

v When running the installation wizard, create a maxdemo database byperforming the following tasks:


http://msdn.microsoft.com/en-us/library/ms177440.aspx

1. In the Run Configuration Step screen in the installation wizard, select theCopy files now. Perform installation configuration later option.

2. When the installation finishes, exit the installation wizard.3. Rename the ibm\smp\maximo\tools\maximo\en\maximo.dbtype file.4. Copy the ibm\smp\maximo\tools\maximo\en\maxdemo.dbtype file to

ibm\smp\maximo\tools\maximo\en\maximo.dbtype. where en is the languagefolder and dbtype is ora/sqs/db2.

5. From a command prompt navigate to ibm\smp\scripts and run the followingcommand:taskrunner.bat CONTINUE STOPONERROR

Do not restart the computer after you copy files but before you run thetaskrunner command because the taskrunner utility does not create apersistent store of information.

6. When taskrunner finishes running, rename the files back to their originalnames.

Tivoli Asset Management for IT simple install path valuesIf you choose to install Tivoli Asset Management for IT using the simple installpath, the values listed in this section are set. You are able to provide values whereindicated.

Table 14. Tivoli Asset Management for IT Simple Install Path ValuesCategory Field Value

Deployment Option Deployment Simple

Database Configuration Database Type DB2

Host name

Port 50005

Database Name maxdb71

Instance ctginst1

User ID

Automate Database Configuration yes

Remote Access user ID

Database Install DirectoryWindows: C:\Program Files\IBM\SQLLIB

UNIX: /opt/IBM/db2/V9.7

Instance Administrator user IDWindows: db2admin

UNIX: ctginst1

Windows Service user ID db2admin

Data table space name maxdata

Data table space size (MB) 5000


Temporary table space size (MB) 1000

Index table space name MAXDATA

Index table space size (MB) 3000

WebSphere DeploymentManager Configuration

Host name

SOAP Port 8879

WebSphere Application Server installationdirectory (was_install_dir) Windows: C:\Program Files\IBM\WebSphere\AppServer

Linux, Sun Solaris:/opt/IBM/WebSphere/AppServer


User ID wasadmin

Profile name ctgDmgr01

Automate WebSphere Configuration yes

Remote Access user ID

WebSphere ApplicationServer configuration

Web server port 80

Web server name webserver1

Node name ctgNode01

Cluster name MAXIMOCLUSTER

Application server MXServerNote: This value cannot be changed.

Chapter 5. Installation overview 83

Table 14. Tivoli Asset Management for IT Simple Install Path Values (continued)Category Field Value

Integration Adapter JMSConfiguration

JMS data source name intjmsds

Persist JMS messages no

Security ServerConfiguration

Configure J2EE server application security yes

Use WebSphere Application Server securityfor authentication and authorization

yes

User base entry ou=users,ou=SWG,o=IBM,c=US

Group base entry ou=groups,ou=SWG,o=IBM,c=US

Create the required users yes

Maximo Configuration Install directory C:\IBM\SMP

Configuration Step Perform installation configuration now yes


Chapter 6. Deploying with automatic middleware configuration

The automatic IBM Tivoli Asset Management for IT installation consists ofsubsequent tasks that need to be performed in a specified order. You are guidedthrough the tasks by the Tivoli Asset Management for IT Launchpad.

About this task

Installation and deployment of Tivoli Asset Management for IT involves:

Install middleware using themiddleware installation program

Install Tivoli Asset Management for ITand automatically configure middleware

Complete post installation tasks

1. Installing and configuring required Tivoli AssetManagement for IT middleware software products.Refer to Chapter 4, “Installing middleware,” on page39.

2. Installing and configuring Tivoli Asset Managementfor IT components:

a. Installing and configuring Tivoli AssetManagement for IT .

b. Optionally, installing and configuring additionallanguage support. Refer to Chapter 11, “Installinglanguage packs,” on page 227.

3. Optionally, installing and configuring TivoliIntegration Composer. See “Installing IBM TivoliIntegration Composer using the Launchpad” on page240 in the Chapter 12, “Installing IntegrationComposer,” on page 235.

4. Configuration of optional Tivoli Asset Managementfor IT middleware software products, such asWebSphere Portal Server. Refer to Chapter 20, “IBMWebSphere Portal Server overview,” on page 325.

5. Completing post installation tasks.

What to do next

The installation programs for these product components can be initiated throughthe Launchpad, where you can also access product information. If you decide todeploy Tivoli Asset Management for IT automatically or manually, pay specialattention to Step 19 on page 94 in “Performing installation” on page 86.


Related concepts

“Reusing existing middleware components” on page 16You can reuse some existing middleware installations as IBM Tivoli AssetManagement for IT components. If you plan to do so, ensure that they are at thelevel supported by Tivoli Asset Management for IT. The middleware andinstallation programs do not provide a mechanism for patching unsupportedservers, nor do these programs provide remote prerequisite checks to ensure thatthey are at the right level.

Performing installationIn addition to configuring new instances of IBM Tivoli Asset Management for ITmiddleware products installed by the middleware installer, the installationprogram can configure existing instances of prerequisite products, including onesfrom other vendors, that you want to use with Tivoli Asset Management for IT.The instructions provided are for a multiple computer installation using defaultvalues and assume that you choose to have the installation program automaticallyconfigure middleware across multiple computers to work with Tivoli AssetManagement for IT.

Before you begin

If you do not allow the Tivoli Asset Management for IT installation program toconfigure middleware automatically, it still performs programmatic checks to verifythat the documented manual steps were performed properly. If any errors areencountered, a dialog box detailing the error appears. You cannot continue theinstallation task until the errors are resolved.

Make sure that the middleware is running. For WebSphere Application ServerNetwork Deployment, ensure that the Cell and all related nodes are activelyrunning.


About this task

The following steps explain how to install Tivoli Asset Management for IT.

Procedure1. Log in as a user with administrative authority.2. Ensure that the database server, directory server, and application server

services are running.3. Launch the installation program from the launchpad:

a. Start the launchpad: On the DVD titled “IBM Tivoli Asset Managementfor IT 7.2.2”, navigate to the root directory of the product disk or thedownloaded installation image, and run the following commanddepending on your operating system.

Windowslaunchpad.exe

UNIX launchpad.sh

.


b. In the launchpad navigation pane, click Install the Product.c. Click Install Tivoli Asset Management for IT V 7.2.2.0.

Alternatively, you can launch the Tivoli Asset Management for ITinstallation program directly. On the DVD titled “Tivoli Asset Managementfor IT V7.2.2 Launchpad for platform”, navigate to \Tivoli AssetManagement for IT\, and run the following command:

Windows

v install.exe

v install_win64.exe

UNIX

v install_aix64.bin

v install_linux32.bin


4. Select a language for the installation and click OK.5. In the Introduction panel, click Next. The Pre-installation Progress window is

displayed.

Note: The installation program analyzes whether to install or upgrade yourproduct, and the IBM Autonomic Computing Deployment Engine detects theexisting instances.

6. In the Package Summary panel, review the package deployment actions, andthen click Next. This panel lists version information for both new and existingpackages on the system. Target package version information indicates thepackage version being currently deployed. In certain upgrade scenarios, aquestion mark can be displayed alongside a package listed. This symbolserves as a reminder that there might be an updated version of this packageavailable. It does not indicate a failure of the installation program.v If a package exists on your target computer, the Already deployed at target

version status is displayed. Review all the package names marked by ( )v If a package does not exist on your target computer, the Will deploy to

target version status is displayed. Review all the package names marked by( )

7. In the Software License Agreement panel, choose I accept both the IBM andnon-IBM terms, if you agree with the terms, and click Next.

8. In the Choose Install Folder panel, specify the directory you use to installTivoli Asset Management for IT, and then click Next.

Where Would You Like to Install?Enter the installation directory path.

By default, this value is C:\IBM\SMP.

The path that you specify must not contain spaces.9. In the Choose Deployment panel, select the Custom deployment topology,

and then click Next.

SimpleSelect Simple if you want to deploy all components on a singlesystem. This deployment option is typically used for demonstration,proof-of-concept, or training purposes only. The default values aredisplayed in Table 14 on page 83.

Chapter 6. Deploying with automatic middleware configuration 87

CustomSelect Custom if you want to deploy product components acrossseveral systems and can reuse existing middleware components. Thisrecommended deployment option is typically used in a productionenvironment. You choose this option to have the possibility to providecustom configuration options at later time.

As a result, the product configuration for your system processing window isdisplayed.

10. In the Import Middleware Configuration Information panel, specify that youwant to use field values that you entered into the middleware installationprogram as default values for those same fields in the installation program.

Import middleware configuration informationSelect this check box to allow the installation program to reuse valuesspecified in the middleware installation program.

If you select this feature while installing Tivoli Asset Management forIT by way of RXA, the Workspace Location that you specify cannotbe located on a networked drive of the remote system. It must residelocally on the remote system.

The middleware default information is not used if you select theSimple deployment path.

Host nameEnter the host name of the system where the middleware installationprogram was run.

User IDEnter the user ID that was used to run the middleware installationprogram.

PasswordEnter the password of the user ID that was used to run themiddleware installation program.

Workspace LocationEnter the location of the topology file that contains the values enteredfor the middleware installation program. This file is found in theworkspace that was defined during the middleware installation task.For example, C:\ibm\tivoli\mwi\workspace for Windows and/root/ibm/tivoli/mwi/workspace for UNIX.

11. In the Database Type panel, select the product that you use for the Maximodatabase, and then click Next.

DB2 Select this choice to use DB2 as the Maximo database.

Oracle Select this choice to use Oracle as the Maximo database.

Microsoft SQL ServerSelect this choice to use Microsoft SQL Server as the Maximo database.

Each database has its own unique set of configurable parameters and values.12. In the Database panel, enter configuration information about the database,


DB2

Host nameEnter the fully qualified host name of the server hosting DB2.

Port Enter the port being used by DB2 instance.


The default is 50005.

Database nameEnter the name of the database to use with Maximo. Thedefault database name is maxdb71. The database is created if itdoes not exist.

InstanceEnter the name of the database instance to be used withMaximo.

The default instance name is ctginst1. This instance is createdif it does not exist; however, the user and its associated homedirectory must exist on the DB2 server.

Schema nameEnter the schema name for the database.

The name of the DB2 database schema. This value can be thesame value as the owner of the table spaces defined or adifferent value. For example, maximo.

Database user IDEnter the user ID used for Maximo to access DB2.

Default for all platforms is maximo.

This user ID is created if it does not exist.

This user ID cannot be the same one used as the instanceadministrator user ID.

Database passwordEnter the password for the user ID used to access DB2.

Oracle

Host nameEnter the host name of the computer hosting Oracle.

The host name must be fully qualified.

Port Enter the port being used by Oracle.



The default instance name is ctginst1.

Database user IDEnter the user ID used for Maximo to access Oracle.



Database passwordEnter the password for the user ID used to access Oracle.

Microsoft SQL Server

Host nameEnter the host name of the computer hosting Microsoft SQLServer.



Port Enter the port being used by Microsoft SQL Server.


Database NameEnter the name of the database to use with Maximo.

The default database name is maxdb71.

Database user IDEnter the user ID used to access Microsoft SQL Server.



Database passwordEnter the password for the user ID used to access MicrosoftSQL Server.

After you have specified configuration information for the database that wasselected, the installation program connects to the database server to validatethe information you have specified.

13. In the Automate Database Configuration panel, select Automate databaseconfiguration, and then click Next.This option allows the installation program to configure the databaseautomatically for use by Tivoli Asset Management for IT. Examples ofautomated tasks include creating table spaces, creating database tables,creating database schemas, creating users, and so on. Do not select theAutomate database configuration option if you are using Oracle 9. Onlymanual configuration is supported for Oracle 9.If you choose not to have the installation program automatically configure thedatabase, you need to configure a database manually before the installation ofTivoli Asset Management for IT.If you do not choose to automate the database configuration and you have notmanually configured the database before selecting Do not automate databaseconfiguration from within the installation program, the installation verifiesthat you have not completed these preinstall tasks and you receive errors.Complete these manual tasks before restarting the installation program.

14. In the Remote Access Authorization panel, enter authorization information forthe automatic database configuration feature, and then click Next.

User IDEnter a valid user ID that gives the installation program access to thesystem that is hosting the database to be used with Tivoli AssetManagement for IT.

This user ID must have administrative rights on the server that youare accessing.

If you are using DB2 for the Maximo database, you need to be amember of the:

v Windows Windows: DB2ADMNS group

v UNIX UNIX: db2grp1 group.

PasswordEnter the password for the user ID.


See the Remote configuration enablement topic in the Preparing to install sectionfor configuring remote access instructions.

15. In the database administration panel, enter configuration information aboutthe database, and then click Next.

DB2

Installation directory (db2_install_dir)Enter the directory where DB2 is installed.

Windows WindowsThis value might be C:\Program Files\IBM\SQLLIB.

Linux LinuxThis value might be /opt/IBM/db2/V9.7.

AIX AIXThis value might be /opt/IBM/db2/V9.7.

Instance administrator user IDEnter the administrator user ID for the DB2 instance.

Windows WindowsThis value might be db2admin.

Linux LinuxThis value might be ctginst1.

AIX AIX:This value might be ctginst1.

This user ID cannot be the same one as is as the database userID.

Instance administrator passwordEnter the password for the DB2 instance administrator userID.

Windows Windows service user IDThis value might be db2admin. This user ID must haveadministrative authority on the system.

Windows Windows service passwordEnter the password for the user ID used to start the DB2service.

Oracle

Installation directory (oracle_install_dir)Enter the directory where Oracle is installed.

Windows WindowsThis value might be C:\oracle\product\10.2.0\db_1.

Linux LinuxThis value might be /opt/app/oracle/product/10.2.0/db_1.

AIX AIXThis value might be /opt/app/oracle/product/10.2.0/db_1.


Solaris Sun SolarisThis value might be /opt/app/oracle/product/10.2.0/db_1.

Administrator User IDEnter the administrator user ID for Oracle. For all platforms,the default is sys.

Administrator PasswordEnter the password for the administrator user ID for Oracle.

Oracle Software Owner IDEnter the user ID of the user that was used to install Oracle.For all platforms, the default is oracle.

Oracle Owner PasswordEnter the password for the user ID of the user that was usedto install Oracle.


SQL Server administratorEnter the administrator user ID for SQL Server Default is sa.

SQL Server administrator passwordEnter the password for the administrator user ID for SQLServer.

Data file nameEnter the name of the SQL Server data file. Default value ismaxdb71_dat.

Data file initial sizeSelect the initial size of the SQL Server data file. Default is setto Medium (1000 MB).

Log file nameEnter the name for the SQL Server log file. Default ismaxdb71_log.

16. In the database tablespace panel, enter information about the table space ofthe database, and then click Next.

DB2

Data tablespace nameEnter the name of the table space that is created in DB2 forMaximo.

For all platforms, the default is MAXDATA.

If the table space does not exist, it is created.

Data tablespace sizeEnter a size for the table space by selecting one of thefollowing values:v small (3000 MB)

Select this size if supporting 1 - 20 usersv medium (5000 MB)

Select this size if supporting 20 - 100 usersv large (8000 MB)

Select this size if supporting 100+ users


Table space size is measured in MB.

Temporary tablespace nameEnter the name for the temporary table space to be created forDB2.

Temporary table spaces hold data during sorting or collatingactions.

For all platforms, the default is MAXTEMP.


Temporary tablespace sizeEnter a size for the temporary table space.

Temporary table space size is measured in MB.

This value must be set to 1000 MB.

Index tablespace name

Enter the name for the index table space to be created forDB2.


Index tablespace sizeEnter a size for the index table space for DB2.



Oracle

Instance LocationEnter the path where the database instance is loaded.

Windows WindowsThis value might be C:\oracle\product\10.2.0\db_1\dbs.



Solaris SolarisThis value might be /opt/app/oracle/product/10.2.0/db_1.

Tablespace NameEnter the name of the table space that is created in Oracle forthe product.

For all platforms, the default is maxdata.

Tablespace SizeEnter a size for the table space by selecting one of thefollowing values:v small (500 MB)






Temporary Tablespace NameEnter the name for the temporary table space to be created forOracle.


For all platforms, the default is maxtemp.

Temporary Tablespace SizeEnter a size for the temporary table space, which is used forsort operations.


For all platforms, the default is 1000 MB.

Index Tablespace NameEnter a name for the index table space.


Index Tablespace SizeEnter a size for the index table space.


The installation program now connects to the database server and validates allthe information you have entered.

17. In the Application Server Type panel, select IBM WebSphere ApplicationServer and then click Next.

18. In the WebSphere Connectivity panel, enter host information about theWebSphere Application Server, and then click Next.

Host nameEnter the fully qualified host name of the system hosting WebSphereApplication Server.

Alternatively, you can provide the IP address for the system.

SOAP portEnter the SOAP port of the system.

The default value for this field is 8879.19. In the Automate WebSphere Remote Configuration panel, select whether you

would like to automate the WebSphere Application Server configuration, andthen click Next.

Automate WebSphere ConfigurationThis option is recommended. Ensure that you have a remote accessprotocol enabled.

Windows Windows:The SSH or SMB protocol is required.


UNIX UNIX :The SSH or rsh REXEC protocol is required.

Do not automate WebSphere configurationIf you choose this option, you need to configure WebSphereApplication Server manually before you start to install Tivoli AssetManagement for IT.

20. In the WebSphere Remote Access Authorization panel, enter authorizationinformation for WebSphere Application Server configuration, and then clickNext.

Operating system user IDEnter a valid user ID that gives the installation program access to thesystem that is hosting WebSphere Application Server.

This user ID must have administrative rights on the computer you areaccessing.

Operating system passwordEnter the password for the system user ID.

21. In the Automate WebSphere Configuration panel, select Automate WebSphereconfiguration, and then click Next.It allows the installation program to configure WebSphere Application Serverautomatically for use by Tivoli Asset Management for IT.If you choose not to have the installation program automatically configureWebSphere Application Server, you need to configure WebSphere ApplicationServer manually before the installation. Configuration tasks include creating aprofile, running WebSphere Application Server as a Windows service, copyingthe keystore file from the application server to the administrative workstation,setting up JMS queues, and so on. For more information, see “Manuallyconfiguring the J2EE server” on page 160.

22. In the WebSphere Deployment Manager Configuration panel, enter values forthe following fields, and then click Next.

WebSphere installation directory (was_install_dir)Enter the directory where WebSphere Application Server is installedon the host system.

Windows Windows:This value might be C:\Program Files\IBM\WebSphere\AppServer.

Linux Linux:This value might be /opt/IBM/WebSphere/AppServer.

AIX AIX:This value might be /usr/IBM/WebSphere/AppServer

Solaris Sun Solaris:This value might be /opt/IBM/WebSphere/AppServer.

User IDEnter the administrative user ID used to access the WebSphereApplication Server server.



PasswordEnter the password for the administrative user ID used to access theapplication server.

Profile nameEnter the name of the application server profile.

Default for all platforms is ctgDmgr01.23. In the WebSphere Application Server Configuration panel, enter the following

information, and then click Next.

Web server portEnter the Web server port used by WebSphere Application Server.Default for all platforms is 80.

Web server nameEnter the name of the Web server. Default for all platforms iswebserver1.

Node nameEnter the name of the node containing the application server. Defaultfor all platforms is ctgNode01.

Application serverEnter the name of the application server. Default for all platforms isMXServer.

24. In the Security panel, select a method for authenticating and authorizingusers, and then click Next.

Use WebSphere application security for authentication and authorizationChoose this option to automatically configure WebSphere ApplicationServer Network Deployment application security to manage users andgroups for authentication and authorization purposes. This optionrequires application security to already be enabled in WebSphereApplication Server Network Deployment.

WebSphere application security only for authenticationChoose this option to automatically configure WebSphere ApplicationServer Network Deployment application security for authenticationonly and allow Maximo security to manage users and groups. Youcreate all your users in your directory server, but you manage theirmembership in security groups in the Security Groups application.This option requires application security to already be enabled inWebSphere Application Server Network Deployment.

If you select this option, the next panel you encounter prompts youfor your user base entry. The maxadmin, maxreg, and mxintadm usersmust have been created before you proceed past this panel.


25. In the Enter Maximo users panel, enter the following information, and thenclick Next.

Maximo administration userEnter the Maximo administration user ID. Default is maxadmin.


PasswordEnter the Maximo administration user ID password.

Maximo system registration userEnter the Maximo runtime user ID.

PasswordEnter the Maximo system registration user password.

Maximo system integration userEnter the integration user ID.

PasswordEnter the Maximo system integration user password.

Custom Maximo user ID and password values are stored in the Maximodatabase. The default Maximo user IDs of maxadmin, maxreg, and maxintadmare also created as users in the Maximo database. Creation of the default userIDs is done for internal processing purposes. If you use Maximo security forauthentication and authorization, the default user IDs can be used to log in tothe application. If you view this condition as a security risk, you can modifythe passwords for these default user IDs. Passwords for these user IDs can bemodified through the Users application.

26. In this security panel, which you encounter if you chose to use WebSphereApplication Server Network Deployment application security forauthentication and authorization, enter the distinguished names of the userand group base entities you are using, choose how Tivoli Asset Managementfor IT users are created, and then click Next.

User base entryIf you do not plan to use the default LDAP schema provided withTivoli Asset Management for IT, enter the user base entry you intendto use in this field.

The default LDAP schema user base entry isou=users,ou=SWG,o=IBM,c=US

Group base entryIf you do not plan to use the default LDAP schema provided withTivoli Asset Management for IT, enter the group base entry you intendto use in this field.

The default LDAP schema group base entry isou=groups,ou=SWG,o=IBM,c=US

Create the required usersKeep this option selected to allow the Tivoli Asset Management for ITinstallation program to create default users in WebSphere ApplicationServer Network Deployment Virtual Member Manager.

This operation requires write access to Virtual Member Manager.

If you do not want to have the users created by the Tivoli AssetManagement for IT installation program, you have to create themmanually before continuing the Tivoli Asset Management for ITinstallation from this point.

If you are not using the default LDAP schema provided with Tivoli AssetManagement for IT, you must create it yourself before advancing beyond thispanel. The values specified for User and Group base entry fields are used toconfigure the VMMSYNC cron task.


Following is an example of the default add on ldif data you have to modifyand import into your LDAP repository if you chose to customize the schemaand create your own users manually.dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxadminuid: maxadminobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxadmincn: maxadmin

dn: uid=mxintadm,ou=users,ou=SWG, o=ibm,c=ususerPassword: mxintadmuid: mxintadmobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: mxintadmcn: mxintadm

dn: uid=maxreg,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxreguid: maxregobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxregcn: maxreg

27. In the Integration Adapter JMS Configuration panel, enter the followinginformation, and then click Next. A JMS server requires a DB2 data repositoryto be configured to maintain messages. If you are using another databasetype, you cannot have the installation program configure message persistence.

JMS Data Source nameEnter the name of the database to be used by JMS.

If you are using Microsoft SQL Server, this field is pre-populated. If itis not, enter intjmsds.

Select whether the JMS data store should be persisted.

Persist JMS messagesSelect this option to enable the Tivoli Asset Management forIT installation program to set the JMS implementation topersist messages within DB2.

Do not persist JMS messagesIf you select this option, the Tivoli Asset Management for ITinstallation program does not set the JMS implementation topersist messages automatically in DB2. You can configure theJMS implementation manually at a later date. If you select thisoption, when you click Next, the installation wizard skips tostep 30, where you configure SMTP.

Select this option if you are deploying Tivoli AssetManagement for IT with OracleOracle or Microsoft SQLServer.


28. If you chose to persist JMS messages, in the DB2 Database ServerConfiguration panel, enter the following information, and then click Next. Ifyou chose not to persist JMS messages you do not see this panel.

Note: The JMS data store can only be created as a DB2 database.

Host nameEnter the fully qualified host name of the server hosting the JMS datastore.

Port Enter the port used to access the database server.


Database nameEnter the name of the database serving as the JMS data store.

Default for all platforms is maxsibdb.

User IDEnter the user ID used to access the database server.

Default for all platforms is mxsibusr.

PasswordEnter the password for the user ID used to access the database server.

29. If you chose to persist JMS messages, in the DB2 Database Server RemoteAccess Authorization panel, enter authorization information for the automaticconfiguration feature, and then click Next. If you chose not to persist JMSmessages you do not see this panel.

User IDEnter a valid user ID that allows the Tivoli Asset Management for ITinstallation program to access the system that is hosting the JMSdatabase.

This user ID must have administrative rights on the server you areaccessing.

For Windows, this user must be a member of the DB2ADMNS group.

For Linux or UNIX, this user must be root and a member of a groupwith SYSADM authority for the database instance.


30. If you chose to persist JMS messages, in the DB2 Database InstanceConfiguration panel, enter the following information, and then click Next. Ifyou chose not to persist JMS messages you do not see this panel.

Installation directoryEnter the installation directory for the DB2 server that is hosting theJMS database that contains the instance to be used with WebSphereApplication Server Network Deployment.

WindowsThis value might be C:\Program Files\IBM\SQLLIB

Linux or UNIXThis value might be /opt/IBM/db2/V9.7

InstanceEnter the JMS database instance to be used with WebSphereApplication Server Network Deployment.


For all platforms, the default is ctginst1

Instance administrator user IDEnter the user ID of the administrator for the JMS database instance.

WindowsThis value might be db2admin.

Linux or UNIXThis value might be ctginst1.

Instance administrator passwordEnter the password for the user ID of the administrator for the JMSdatabase instance.

31. In the SMTP Configuration panel, enter the SMTP server and Administratore-mail. Click Next. This information is used by workflows to communicatewith workflow participants.

SMTP serverEnter the mail server configured to work with Tivoli AssetManagement for IT. This server is used to send workflow and processnotifications. This field is optional.

Administrator e-mailEnter the e-mail address of the person assigned to the role ofadministrator. This field is optional.

You can defer SMTP configuration at this time by not providing anyinformation for this panel and clicking through to the next panel. However,you must configure these parameters through the product interface as a postinstallation task.

32. In the Data Integration Services and Context Menu Service DeploymentOptions panel, select a deployment option.The Data Integration Service and Context Menu Service allow products toregister themselves in order to offer launch in context to all other registeredproducts. This ability is provided without unique product-to-productintegration efforts. A single integration effort through Data Integration Serviceand Context Menu Service allows registered products to gain launch access forall other registered products.

Deploy data integration and context menu services into the same databasethat you created for the product.

Select this option to use the Tivoli Asset Management for IT databaseas the Data Integration Service and Context Menu Service.

Configure data integration and context menu services for this product usinga previously deployed data integration and context menu service instance.

Select this option to configure Data Integration Service and ContextMenu Service for Tivoli Asset Management for IT using a previouslydeployed database.

Defer or skip data integration service and context menu service setup andconfiguration

Select this option to defer the configuration of Data Integration Serviceand Context Menu Service to a later time. If you defer thedeployment, proceed to the Run Configuration Step panel.

33. In the Database Information panel, enter configuration information about theData Integration Service database and then click Next.


Use the product database for the data integration service.Select this option if you want to use the Tivoli Asset Management forIT database as the Data Integration Service database.

Use the same database for both data integration and context menu servicesSelect this option if you want to use the Data Integration Servicedatabase as the Context Menu Service database.

DB2 Select this option if there is a DB2 database that is already set up forData Integration Service. This database must be configured before theTivoli Asset Management for IT installation.

Oracle Select this option if there is an Oracle database that is already set upfor Data Integration Service. This database must be configured beforethe Tivoli Asset Management for IT installation.

Microsoft SQL ServerMicrosoft SQL Server is not a valid option for Tivoli AssetManagement for IT. Do not select this option.

Host nameEnter the fully qualified host name of the database server hosting theData Integration Service database.

Port Enter the port of the Data Integration Service database instance. Forexample, 50005.

Database nameEnter the name of the database.

InstanceEnter the database instance.

User IDEnter the user ID to use to access the database.

PasswordEnter the password of the user ID used to access the database.

34. If you did not select the Use the same database for both data integration andcontext menu services option in the previous panel, the Context Menu ServiceDatabase Information panel is displayed. In this panel, enter configurationinformation about the Context Menu Service database and then click Next.

Use the product database for the context menu service.Select this option if you want to use the Tivoli Asset Management forIT database as the Context Menu Service database.

DB2 Select this option if there is a DB2 database that is already set up forthe Context Menu Service. This database must be configured beforethe Tivoli Asset Management for IT installation.

Oracle Select this option if there is an Oracle database that is already set upfor the Context Menu Service. This database must be configuredbefore the Tivoli Asset Management for IT installation.


Host nameEnter the fully qualified host name of the database server hosting theContext Menu Service database.


Port Enter the port of the Context Menu Service database instance. Forexample, 50005.





35. In the Run Configuration Step window, choose whether to performconfiguration steps, or to defer them until later, manual configuration. If youdo not select any options, when you click Next, the configuration step willproceed.

Copy files now, but perform the installation configuration step later.Select this option if you would like to copy files from the installationsource to the administrative workstation. You will have to performthe configuration step at a later time to complete the deployment. Youmight choose this option if you intend to install more than one ISMproduct and want to perform the configuration step once for all theproducts.

The configuration values that you enter are stored in the<tamit_install_dir>maximo\applications\maximo\properties\maximo.properties file. You can run the configuration steps outside ofthe Tivoli Asset Management for IT installation program by using thetaskrunner utility, in the <tamit_install_dir>\scripts directory. Runthe taskrunner utility from the command line, and it will use theconfiguration values stored in the maximo.properties file to configureTivoli Asset Management for IT.<tamit_install_dir>\scripts\taskrunnerCONTINUE <STOPONERROR|NOSTOPONERROR>

Note: If you reboot the system, you will not be able to use thetaskrunner utility to run configuration scripts. Taskrunner data storesare not persisted. If you intend to use the taskrunner utility, do notreboot your system.

In the event of an installation failure, the taskrunner utility can be runagain after the error conditions have been rectified if it was run withthe STOPONERROR parameter. The taskrunner utility will resumethe installation at the point where the last successfully completed taskwas recorded in the previous attempt. If you run taskrunner with theNOSTOPONERROR parameter, the taskrunner will continue despiteerrors.

Deploy application files manually later.Select this option if you would like to manually deploy applicationfiles to WebSphere Application Server Network Deployment.Application EAR files will be created, but they will not beautomatically deployed. You will have to manually deploy them at alater time. You might choose this option if you intend to install morethan one ISM product. Application files are rebuilt during eachproduct installation. Using this option, you can defer deployingapplication files until they are finalized.


Defer the update of the Maximo database.Select this option if you would like to manually run the databaseupdate task for the product deployment. You will have to manuallyrun the updatedb command to write data to the Maximo database inorder to complete the deployment. The installation program is limitedto copying files to the administrative system and registering productprocess solution packages. This option can be used in cases wherethere is a fix pack available that addresses known issues with theupdatedb script. In this scenario, you would chose the Defer theupdate of the Maximo database option, apply the fix pack, and thenrun the updatedb -v1 command manually.

36. In the Choose Shortcut Folder panel, select the type of shortcut you wouldlike to arrange for Tivoli Asset Management for IT, and then click Next.

In a new Program GroupSelect this option and enter the name of a new program group if youwould like to create the product shortcuts in a new program group.

In an existing Program GroupSelect this option and choose the name of an existing program groupto store the shortcuts.

In the Start MenuSelect this option to create shortcuts for the product in the Start menu.

In order to use the Start menu shortcut with Microsoft InternetExplorer, add the Tivoli Asset Management for IT URL to the trustedsites Web content zone and disable the option of requiring serververification for all sites in the zone.

On the DesktopSelect this option to create shortcuts for Tivoli Asset Management forIT on the desktop.

In the Quick Launch BarThis option must not be used. Do not select this option. Selecting thisoption does not create a shortcut in the Quick Launch bar.

Other Select this option and use the Choose... button to select anotherlocation to create the shortcuts.

Don't create iconsSelect this option if you do not want any shortcuts created.

Create Icons for All UsersSelect this option if you want the Tivoli Asset Management for ITdesktop icons to appear on the desktop for all system users.

37. In the Input Summary panel, review the information you have provided to theinstallation program, and then click Next.Use the Previous button to return to previous panels to change anything.

38. In the Pre-Installation Summary panel, review the installation informationpresented, and then click Install. The installation now begins. Progress can bemonitored by viewing messages displayed.

39. From the Install Complete panel, click Done.


What to do next

Once the Tivoli Asset Management for IT installation program has completedinstallation and configuration tasks, it exits. Logs can be found attamit_install_dir/logs.


Chapter 7. Deploying automatically reusing existingmiddleware

This information provides a high-level overview or road map of tasks you need tocomplete in order to deploy IBM Tivoli Asset Management for IT automatically,using middleware already established in your enterprise.

Before you begin

Ensure that you have reviewed the following information:v Chapter 2, “Planning to deploy,” on page 9v Chapter 3, “Preparing to install,” on page 27

About this task

Installation and deployment of IBM Tivoli Asset Management for IT involves:

Run the middleware installationon existing middleware servers

Install Tivoli Asset Management for ITand automatically configure middleware


1. Running middleware installation on theexisting middleware servers

2. Installing Tivoli Asset Management for IT,and optionally, installing language packs andTivoli Integration Composer

3. Chapter 9, “Verifying the installation,” onpage 191

4. Completing post installation tasks.

Related concepts

“Reusing existing middleware components” on page 16You can reuse some existing middleware installations as IBM Tivoli AssetManagement for IT components. If you plan to do so, ensure that they are at thelevel supported by Tivoli Asset Management for IT. The middleware andinstallation programs do not provide a mechanism for patching unsupportedservers, nor do these programs provide remote prerequisite checks to ensure thatthey are at the right level.

Reusing middlewareIf you intend to reuse existing middleware servers with the existing Tivoli AssetManagement for IT, they must be configured before running the installationprogram. This section contains information about configuring existing DB2 andIBM Tivoli Directory Server servers for use with Tivoli Asset Management for ITusing the middleware installer.

You cannot use the middleware installer to configure existing Oracle, MicrosoftSQL Server, or Microsoft Active Directory servers. Refer to Chapter 8, “Installingwith manual middleware configuration,” on page 129 for more information aboutthose servers. Information found in this section also applies if you decide that you


want to reuse existing middleware servers, but you want to configure them towork with Tivoli Asset Management for IT manually instead of allowing theinstallation program to configure them.

Ensure that all of your middleware is at the level described in “Hardware andsoftware requirements” on page 3.

Reusing IBM DB2If you have an existing IBM DB2 installation that you would like to reuse for IBMTivoli Asset Management for IT, run the Tivoli middleware installer on the system.The middleware installer identifies instances of middleware that exist on thesystem that are compatible with Tivoli Asset Management for IT, and it configuresthe existing instance for use with the product.

About this task

To have the middleware installer configure an existing database instance for reusewith Tivoli Asset Management for IT, complete the following steps:

Procedure1. Log in as a user with administrative authority.2. Launch the middleware installer from the Launchpad.3. Proceed through the middleware installer panels as instructed in “Installing

middleware with the Tivoli middleware installer” on page 42, until you reachthe Deployment Choices panel.

4. From the Deployment Choices panel, select Database Server, and then clickNext. The middleware installer displays any instances of DB2 found on thesystem.

5. From the Installation drop-down menu, select the appropriate instance to reuse,and then click Next.

6. Complete the installation by proceeding through the remainder of themiddleware installer panels.

Note: If you are reusing an existing DB2 server with Tivoli Asset Managementfor IT, the following users and groups must exist on the system:

Users

v db2admin

v UNIX dasusr1

v UNIX db2fenc1

Groups

v Windows db2admns

v UNIX dasadm1

v UNIX dbgrp1

v UNIX db2fgrp1

If these users do not exist on the system, create them before running theinstallation program.


Reusing OracleIf you have an existing Oracle 10g instance that you would like to reuse for TivoliAsset Management for IT, configure it manually.

About this task

Refer tov “Manually configuring Oracle 11g” on page 138v “Manually configuring Oracle 10g” on page 141 for information.v For an existing Oracle 9.2 instance, refer to “Manually configuring Oracle 9i

Rel2” on page 143

Reusing IBM Tivoli Directory ServerIf you have an existing IBM Tivoli Directory Server installation that you would liketo reuse for Tivoli Asset Management for IT, run the Tivoli middleware installer onthe system. The middleware installer identifies middleware that already exists onthe system that is compatible with Tivoli Asset Management for IT, and configuresit for use with the product.

Before you begin

The middleware installer creates an instance on the existing Directory Server thatyou identify. This instance contains default Tivoli Asset Management for IT LDAPinformation. If you intend to use Tivoli Asset Management for IT with an existingDirectory Server instance that contains your organization's LDAP information, donot run the middleware installer to configure the existing Directory Server.

About this task

To have the middleware installer configure an existing Directory Server instancefor reuse with Tivoli Asset Management for IT, complete the following steps:

Procedure1. Log in as a user with administrative authority.2. Launch the middleware installer from the Launchpad.3. Proceed through the middleware installer panels as instructed in “Installing

middleware with the Tivoli middleware installer” on page 42, until you reachthe Deployment Choices panel.

4. From the Deployment Choices panel, select Directory Server, and then clickNext. The middleware installer will display any instances of Directory Serverfound on the system.

5. From the Installation drop-down menu, select the appropriate instance to reuse,and then click Next.

6. Complete the installation by proceeding through the remainder of themiddleware installer panels. Refer to “Installing middleware with the Tivolimiddleware installer” on page 42 for more information.

Reusing Microsoft Active DirectoryWindows An existing Microsoft Active Directory instance can be used to secure

WebSphere Application Server Network Deployment. The middleware installationprogram can be used to validate Microsoft Active Directory configurationinformation.

Chapter 7. Deploying automatically reusing existing middleware 107

Before you begin

Before running the installation program, manually create the users listed in“Manually configuring Microsoft Active Directory” on page 151. You can performthis task after you run the middleware installation program, but you mustcomplete it before you run the Tivoli Asset Management for IT installationprogram.

About this task

The middleware installation program prompts you for LDAP configurationparameters to use with WebSphere Application Server Network Deployment.

To validate Microsoft Active Directory configuration information using themiddleware installation program use, complete the following steps:

Procedure1. Log in as a user with administrative authority.2. Start the middleware installation program from the Launchpad.3. Proceed through the middleware installation program panels as instructed in

Chapter 4, “Installing middleware,” on page 39, until you reach theDeployment Choices panel.

4. From the Deployment Choices panel, clear the Directory Server deploymentoption, and then click Next. In the next panel, you are given the choice ofselecting an existing instance of Tivoli Directory Server or Microsoft ActiveDirectory to secure WebSphere Application Server Network Deployment.

5. In the Deployment Plan Summary window, click Next to configureparameters. The deployment plan is generated and you are provided detailsabout the plan.

6. In the Configurable Host Name panel, you can manually specify the hostname of the system you are running the installation from. Select the Overridethe local machine hostname option and enter a host name value in theHostname field. Select this option only if you want to manually specify thehost name of the system instead of having the installation programprogrammatically detect it. This option is useful when there is more than onehost name assigned to the system. This configuration occurs when a systemhas more than one network interface, or it is configured to support virtual IPaddresses. When this option is selected, you are required to provide aresolvable host name. You cannot clear this option after it has been selected.However, you can still change the value of the Hostname field. If you startedthe middleware installation program from the command line using theforceHostname=true parameter, then you are required to provide analphanumeric value in the Hostname field. Use of an IP address causes errormessage. When this option has been selected, you are not able to clearit. However, you can change the value you enter in the Hostname field.

7. In the password reuse panel, you can optionally select Use this password asthe value for all subsequent passwords. This option allows you to use thesame password as the default user password value in all panels of themiddleware installation program. If you do not want to use this option, ignorethe Use this password as the value for all subsequent passwords option, andclick Next.

8. Select Secure with Microsoft Active Directory, and click Next.9. Configure the following values for WebSphere Application Server Network

Deployment security, and then click Next.


LDAP Host nameEnter the fully qualified name of the server hosting Microsoft ActiveDirectory.

LDAP base entryEnter the LDAP base entry of the instance. For example,DC=ism71,DC=com

User suffixEnter the user suffix for the instance. For example,OU=Users,OU=SWG,DC=ism71,DC=com

Group suffixEnter the group suffix for the instance. For example,OU=Groups,OU=SWG,DC=ism71,DC=com

Organization container suffixEnter the organization container suffix for the instance. For example,DC=ism71,DC=com

In this example. ism71 is the domain name. You must replace ism71with the name of your own domain.

10. Supply the following configuration values for WebSphere Application ServerNetwork Deployment security, and then click Next.

Bind distinguished nameEnter the bind distinguished name for the instance. For example,CN=Administrator,CN=Users,DC=ism71,DC=com

This value assumes that the Administrator user is already a memberof the ism71 domain. You must replace ism71 with the name of yourown domain.

Bind passwordEnter the password for the Administrator user on the system hostingMicrosoft Active Directory.

11. Finish the installation by completing the remainder of the middlewareinstallation program panels.See Chapter 4, “Installing middleware,” on page 39 for more information.

Performing installationIn addition to configuring new instances of IBM Tivoli Asset Management for ITmiddleware products installed by the middleware installer, the installationprogram can configure existing instances of prerequisite products, including onesfrom other vendors, that you want to use with Tivoli Asset Management for IT.The instructions provided are for a multiple computer installation using defaultvalues and assume that you choose to have the installation program automaticallyconfigure middleware across multiple computers.

Before you begin

If you do not allow the Tivoli Asset Management for IT installation program toconfigure middleware automatically, it still performs programmatic checks to verifythat the documented manual steps were performed properly. If any errors areencountered, a dialog box detailing the error appears. You cannot continue in theinstallation task until the errors are resolved.


Make sure that the middleware is running. For WebSphere Application ServerNetwork Deployment, ensure that the Cell and all related nodes are activelyrunning.


About this task


Procedure1. Log in as a user with administrative authority.2. Ensure that the database server, directory server, and application server

services are running.3. Launch the installation program from the launchpad:

a. Start the launchpad: On the DVD titled “Tivoli Asset Management for IT7.2.2”, navigate to the root directory of the product disk or thedownloaded installation image, and run the following command,depending on your operating system:


UNIX launchpad.shb. In the launchpad navigation pane, click Install the Product.c. Click Install Tivoli Asset Management for IT V 7.2.2.0.

Alternatively, you can launch the Tivoli Asset Management for ITinstallation program directly. On the DVD titled “Tivoli Asset Managementfor IT V7.2.2 Launchpad for platform”, navigate to \Tivoli AssetManagement for IT\, and run the following command

Windows

v install.exe

v install_win64.exe

UNIX

v install_aix64.bin




displayed.


6. In the Package Summary panel, review the package deployment actions, andthen click Next. This panel lists version information for both new and existingpackages on the system. Target package version information indicates thepackage version being currently deployed. In certain upgrade scenarios, aquestion mark can be displayed alongside a package listed. This symbolserves as a reminder that there might be an updated version of this packageavailable. It does not indicate a failure of the installation program.


v If a package exists on your target computer, the Already deployed at targetversion status is displayed. Review all the package names marked by ( )

v If a package does not exist on your target computer, the Will deploy totarget version status is displayed. Review all the package names marked by( )

7. In the Software License Agreement panel, choose I accept both the IBM andnon-IBM terms, if you agree with them, and click Next.

8. In the Choose Install Folder panel, specify the directory you use to install theproduct, and then click Next.

Where Would You Like to Install?Enter the installation directory path.

By default, this value is C:\IBM\SMP.

The path you specify must not contain spaces.9. In the Choose Deployment panel, select the Custom deployment topology,


SimpleSelect Simple if you want to deploy all Tivoli Asset Management forIT components on a single system. This deployment option is typicallyonly used for demonstration, proof-of-concept, or training purposes.The default values are displayed in Table 14 on page 83.

CustomSelect custom if you want to deploy Tivoli Asset Management for ITcomponents across several systems and can reuse existing middlewarecomponents. This recommended deployment option is typically usedin a production environment. You choose this option to havepossibility to provide custom configuration options at later time.


10. In the Import Middleware Configuration Information panel, specify that youwant to use field values you enter into the middleware installation programas default values for those same fields in the installation program.

Import Middleware Configuration InformationSelect this check box if you want to allow the installation program toreuse values specified in the middleware installer.


The middleware default information is not used if you select thesimple deployment path.

Host nameEnter the host name of the system where the middleware installer wasrun.




Workspace LocationEnter the location of the topology file that contains the values enteredfor the middleware installation program. This file is found in theworkspace that was defined during the middleware installation task.For example, C:\ibm\tivoli\mwi\workspace for Windows and/root/ibm/tivoli/mwi/workspace for UNIX.

11. In the Database Type panel, select the product that you use for the Maximodatabase, and then click Next.



Microsoft SQL ServerSelect this choice to use Microsoft SQL Server as the Maximo database.

Each database has its own unique set of configurable parameters and values.12. In the Database panel, enter configuration information about the database,


DB2


Port Enter the port being used byDB2 instance.












Oracle























After you have specified configuration information for the database that wasselected, the installation program connects to the database server to validatethe information you have specified.

13. In the Automate Database Configuration panel, select Automate databaseconfiguration, and then click Next.This option allows the installation program to configure the databaseautomatically. Examples of automated tasks include creating table spaces,creating database tables, creating database schemas, creating users, and so on.Do not select the Automate database configuration option if you are usingOracle 9. Only manual configuration is supported for Oracle 9.If you choose not to have the installation program automatically configure thedatabase, you need to configure a database manually before the installation ofTivoli Asset Management for IT.


If you do not choose to automate the database configuration and you have notmanually configured the database before selecting Do not automate databaseconfiguration from within the installation program, the installation verifiesthat you have not completed these preinstall tasks and you receive errors.Complete these manual tasks before restarting the installation program.

14. In the Remote Access Authorization panel, enter authorization information forthe automatic database configuration feature, and then click Next.

User IDEnter a valid user ID that gives the installation program access to thesystem that is hosting the database to be used with Tivoli AssetManagement for IT.


If you are using DB2 for the Maximo database, you need to be amember of the:

v Windows Windows: DB2ADMNS group

v UNIX UNIX: db2grp1 group.


See the Remote configuration enablement topic in the Preparing to install sectionfor configuring remote access instructions.

15. In the database administration panel, enter configuration information aboutthe database, and then click Next.

DB2

Installation directory (db2_install_dir)Enter the directory where DB2 is installed.

Windows WindowsThis value might be C:\Program Files\IBM\SQLLIB.

Linux LinuxThis value might be /opt/IBM/db2/V9.7.

AIX AIXThis value might be /opt/IBM/db2/V9.7.

Instance administrator user IDEnter the administrator user ID for the DB2 instance.

Windows WindowsThis value might be db2admin.

Linux LinuxThis value might be ctginst1.

AIX AIX:This value might be ctginst1.

This user ID cannot be the same one as is as the database userID.


Instance administrator passwordEnter the password for the DB2 instance administrator userID.

Windows Windows service user IDThis value might be db2admin.

Windows Windows service passwordEnter the password for the user ID used to start the DB2service.

Oracle

Installation directory (oracle_install_dir)Enter the directory where Oracle is installed.

Windows WindowsThis value might be C:\oracle\product\10.2.0\db_1.




Administrator User IDEnter the administrator user ID for Oracle. For all platforms,the default is sys.

Administrator PasswordEnter the password for the administrator user ID for Oracle.

Oracle Software Owner IDEnter the user ID of the user that was used to install Oracle.For all platforms, the default is oracle.

Oracle Owner PasswordEnter the password for the user ID of the user that was usedto install Oracle.


Microsoft SQL Server administratorEnter the administrator user ID for Microsoft SQL Server.Default is sa.

Microsoft SQL Server administrator passwordEnter the password for the administrator user ID for MicrosoftSQL Server.

Data file nameEnter the name of the Microsoft SQL Server data file. Defaultvalue is maxdb71_dat.

Data file initial sizeSelect the initial size of the Microsoft SQL Server data file.Default is set to Medium (1000 MB).


Log file nameEnter the name for the Microsoft SQL Server log file. Defaultis maxdb71_log.

16. In the database table space panel, enter information about the table space ofthe database, and then click Next.

DB2




Data tablespace sizeEnter a size for the table space by selecting one of thefollowing values:v small (3000 MB)









Temporary tablespace sizeEnter a size for the temporary table space.



Index tablespace name

Enter the name for the index table space to be created forDB2.


Index tablespace sizeEnter a size for the index table space for DB2.



Oracle

Instance LocationEnter the path where the database instance is loaded.


Windows WindowsThis value might be C:\oracle\product\10.2.0\db_1\dbs.




Tablespace NameEnter the name of the table space that is created in Oracle forMaximo.


Tablespace SizeEnter a size for the table space by selecting one of thefollowing values:v small (500 MB)





Temporary tablespace nameEnter the name for the temporary table space to be created forOracle.



Temporary tablespace sizeEnter a size for the temporary table space, which is used forsort operations.



Index tablespace nameEnter a name for the index table space.


Index tablespace sizeEnter a size for the index table space.



The installation program now connects to the database server and validates allthe information you have entered.

17. In the Application Server Type panel, select IBM WebSphere ApplicationServer and then click Next.

18. In the WebSphere Connectivity panel, enter host information about theWebSphere Application Server, and then click Next.

Host nameEnter the fully qualified host name of the system hosting WebSphereApplication Server.


SOAP portEnter the SOAP port of the WebSphere Application Server system.

The default value for this field is 8879.19. In the Automate WebSphere Remote Configuration panel, select whether you

would like to automate the WebSphere Application Server configuration, andthen click Next.

Automate WebSphere ConfigurationThis option is recommended. Ensure that you have a remote accessprotocol enabled.

Windows Windows:The SSH or SMB protocol is required.

UNIX UNIX:The SSH or rsh REXEC protocol is required.

Do not automate WebSphere configurationIf you choose this option, you need to configure WebSphereApplication Server manually before you start to install Tivoli AssetManagement for IT.

20. In the WebSphere Remote Access Authorization panel, enter authorizationinformation forWebSphere Application Server configuration, and then clickNext.

Operating system user IDEnter a valid user ID that gives the installation program access to thesystem that is hosting WebSphere Application Server.


Operating system passwordEnter the password for the system user ID.

21. In the Automate WebSphere Configuration panel, select Automate WebSphereconfiguration, and then click Next.It allows the installation program to configure WebSphere Application Serverautomatically for use by Tivoli Asset Management for IT.If you choose not to have the installation program automatically configureWebSphere Application Server, you need to configure the application servermanually before the installation. Configuration tasks include creating a profile,running WebSphere Application Server as a Windows service, copyingkeystore file from the computer where the application server is installed to theadministrative workstation, setting up JMS queues, and so on. For moreinformation, see “Manually configuring the J2EE server” on page 160.


22. In the WebSphere Deployment Manager Configuration panel, enter values forthe following fields, and then click Next.

WebSphere installation directory (was_install_dir)Enter the directory where WebSphere Application Server is installedon the host system.

Windows Windows:This value might be C:\Program Files\IBM\WebSphere\AppServer.

Linux Linux:This value might be /opt/IBM/WebSphere/AppServer.

AIX AIX:This value might be /usr/IBM/WebSphere/AppServer

Solaris Sun Solaris:This value might be /opt/IBM/WebSphere/AppServer.

User IDEnter the administrative user ID used to access the application server.


PasswordEnter the password for the administrative user ID used to access theapplication server.

Profile nameEnter the name of the application profile.

Default for all platforms is ctgDmgr01.23. In the WebSphere Application Server Configuration panel, enter the following

information, and then click Next.

Web server portEnter the Web server port used by WebSphere Application Server.Default for all platforms is 80.

Web server nameEnter the name of the Web server. Default for all platforms iswebserver1.

Node nameEnter the name of the node containing the application server. Defaultfor all platforms is ctgNode01.


24. In the Security panel, select a method for authenticating and authorizingusers, and then click Next.



WebSphere application security only for authenticationChoose this option to automatically configure WebSphere ApplicationServer Network Deployment application security for authenticationonly and allow Maximo security to manage users and groups. Youcreate all your users in your directory server, but you manage theirmembership in security groups in the Security Groups application.This option requires application security to already be enabled inWebSphere Application Server Network Deployment.




Maximo administration userEnter the Maximo administration user ID. Default is maxadmin.

PasswordEnter the Maximo administration user ID password.

Maximo system registration userEnter the Maximo runtime user ID.

PasswordEnter the Maximo system registration user password.

Maximo system integration userEnter the integration user ID.

PasswordEnter the Maximo system integration user password.











If you are not using the default LDAP schema provided with Tivoli AssetManagement for IT, you must create it yourself before advancing beyond thispanel. The values specified for User and Group base entry fields are used toconfigure the VMMSYNC cron task.Following is an example of the default add on ldif data you have to modifyand import into your LDAP repository if you chose to customize the schemaand create your own users manually.dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxadminuid: maxadminobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxadmincn: maxadmin



27. In the Integration Adapter JMS Configuration panel, enter the followinginformation, and then click Next. A JMS server requires a DB2 data repositoryto be configured to maintain messages. If you are using another databasetype, you cannot have the installation program configure message persistence.


JMS Data Source nameEnter the name of the database to be used by JMS. If you are usingMicrosoft SQL Server, this field is pre-populated. If it is not, enterintjmsds.

Select whether the JMS datastore should be persisted.

Persist JMS messagesSelect this option to enable the Tivoli Asset Management forIT installation program to set the JMS implementation topersist messages within DB2.

Do not persist JMS messagesIf you select this option, the Tivoli Asset Management for ITinstallation program does not set the JMS implementation topersist messages automatically in DB2. You can configure theJMS implementation manually at a later date. If you select thisoption, when you click Next, the installation wizard skips to32 on page 123, where you configure SMTP.

Select this option if you are deploying Tivoli AssetManagement for IT with OracleOracle or Microsoft SQLServer.

28. If you chose to persist JMS messages, in the DB2 Database ServerConfiguration panel, enter the following information, and then click Next. Ifyou chose not to persist JMS messages you do not see this panel.

Note: The JMS data store can only be created as a DB2 database.

Host nameEnter the fully qualified host name of the server hosting the JMS datastore.

Port Enter the port used to access the database server.


Database nameEnter the name of the database serving as the JMS data store.

Default for all platforms is maxsibdb.

User IDEnter the user ID used to access the database server.

Default for all platforms is mxsibusr.

PasswordEnter the password for the user ID used to access the database server.

29. If you chose to persist JMS messages, in the DB2 Database Server RemoteAccess Authorization panel, enter authorization information for the automaticconfiguration feature, and then click Next. If you chose not to persist JMSmessages you do not see this panel.

User IDEnter a valid user ID that allows the Tivoli Asset Management for ITinstallation program to access the system that is hosting the JMSdatabase.

This user ID must have administrative rights on the server you areaccessing.

For Windows, this user must be a member of the DB2ADMNS group.


For Linux or UNIX, this user must be root and a member of a groupwith SYSADM authority for the database instance.


30. If you chose to persist JMS messages, in the DB2 Database InstanceConfiguration panel, enter the following information, and then click Next. Ifyou chose not to persist JMS messages you do not see this panel.

Installation directoryEnter the installation directory for the DB2 server that is hosting theJMS database that contains the instance to be used with WebSphereApplication Server Network Deployment.

WindowsThis value might be C:\Program Files\IBM\SQLLIB

Linux or UNIXThis value might be /opt/IBM/db2/V9.7

InstanceEnter the JMS database instance to be used with WebSphereApplication Server Network Deployment.

For all platforms, the default is ctginst1

Instance administrator user IDEnter the user ID of the administrator for the JMS database instance.

WindowsThis value might be db2admin.

Linux or UNIXThis value might be ctginst1.

Instance administrator passwordEnter the password for the user ID of the administrator for the JMSdatabase instance.

31. In the WebSphere Keystore File panel, enter the location of the keystore file,and then click Next.Attention: This step is only required if you selected not to automateWebSphere Application Server.

Note: If you install Tivoli Asset Management for IT on a remote computer,make sure that you copied keystore file from the computer where WebSphereApplication Server is installed. The keystore name is trust.p12 and it is keptin the was_install_dir/profiles/your_profile/etc directory.

32. In the SMTP Configuration panel, enter the SMTP server and Administratore-mail. Click Next. This information is used by workflows to communicatewith workflow participants.

SMTP serverEnter the mail server configured to work with Tivoli AssetManagement for IT. This server is used to send workflow and processnotifications. This field is optional.

Administrator e-mailEnter the e-mail address of the person assigned to the role ofadministrator. This field is optional.



33. In the Data Integration Service and Context Menu Service DeploymentOptions panel, select a deployment option.The Data Integration Service and Context Menu Service allow products toregister themselves in order to offer launch in context to all other registeredproducts. This ability is provided without unique product-to-productintegration efforts. A single integration effort through Data Integration Serviceand Context Menu Service allows registered products to gain launch access forall other registered products.


Select this option to use the Tivoli Asset Management for IT databaseas the Data Integration Service and Context Menu Service database.




Select this option to defer the configuration of Data Integration Serviceand Context Menu Service to a later time. You must run the productinstallation program again in the future to configure this feature. Ifyou defer the deployment, you proceed to the Run Configuration Steppanel.

34. In the Data Integration Service Database Information panel is displayed, enterconfiguration information about the Data Integration Service database andthen click Next.





Microsoft SQL ServerMicrosoft SQL Server is not a valid option for Tivoli AssetManagement for IT. Do not select this option









Use the product database for the context menu service.Select this option if you want to use theTivoli Asset Management forIT database as the Context Menu Service database.











Copy files now, but perform the installation configuration step later.Select this option if you would like to copy files from the installationsource to the administrative workstation. You will have to performthe configuration step at a later time to complete the deployment. You


might choose this option if you intend to install more than one ISMproduct and want to perform the configuration step once for all theproducts.

The configuration values that you enter are stored in thetamit_install_dir/maximo\applications\maximo\properties\maximo.properties file. You can run the configuration steps outside ofthe Tivoli Asset Management for IT installation program by using thetaskrunner utility, in the <tamit_install_dir>\scripts directory. Runthe taskrunner utility from the command line, and it will use theconfiguration values stored in the maximo.properties file to configureTivoli Asset Management for IT.<tamit_install_dir>\scripts\taskrunnerCONTINUE <STOPONERROR|NOSTOPONERROR>





37. In the Choose Shortcut Folder panel, select the type of shortcut you wouldlike to arrange for Tivoli Asset Management for IT, and then click Next.

In a new Program GroupSelect this option and enter the name of a new program group if youwould like to create the shortcuts in a new program group.

In an existing Program GroupSelect this option and choose the name of an existing program groupto store the shortcuts.


In the Start MenuSelect this option to create shortcuts in the Start menu.

In order to use the Start menu shortcut with Microsoft InternetExplorer, add the Tivoli Asset Management for IT URL to the trustedsites Web content zone and disable the option of requiring serververification for all sites in the zone.

On the DesktopSelect this option to create shortcuts on the desktop.

In the Quick Launch BarThis option must not be used. Do not select this option. Selecting thisoption does not create a shortcut in the Quick Launch bar.

Other Select this option and use the Choose... button to select anotherlocation to create the shortcuts.

Don't create iconsSelect this option if you do not want any shortcuts created.

Create Icons for All UsersSelect this option if you want the Tivoli Asset Management for ITdesktop icons to appear on the desktop for all system users.

38. From the Input Summary panel, review the information you have provided tothe installation program, and then click Next.Use the Previous button to return to previous panels to change anything.

39. From the Pre-Installation Summary panel, review the installation informationpresented, and then click Install. The installation now begins. Progress can bemonitored by viewing messages displayed above the progress bar.


What to do next

Once the Tivoli Asset Management for IT installation program has completedinstallation and configuration tasks, it exits. Logs can be found attamit_install_dir/logs.



Chapter 8. Installing with manual middleware configuration

You can have one or more IBM Tivoli Asset Management for IT middlewarecomponents configured automatically by the installation program. Alternatively,you can choose to manually configure one or more of the middleware servers towork with Tivoli Asset Management for IT. Configure the components before youinstall the product.

About this task

Manually configured installations involve configuring:v middleware components,v the database server,v the directory server,v the application server

to work with Tivoli Asset Management for IT before using the installationprogram.

Manually configure the database

Manually configure the directory server

Manually configure the J2EE server

Install Tivoli Asset Management for ITusing Manual middleware option

Complete post product installationprocess manager tasks


1. Manually configure the database server

2. Manually configure the directory server

3. Manually configure the application server

4. Install Tivoli Asset Management for IT

5. [ Optional ]

v Install Tivoli Integration Composer

v Install language packs

v Enable Tivoli Asset Management for IT forService Providers

6. Complete post installation tasks

7. Verify the installation

Also included in this section is a procedure describing how to advance through theinstallation program to complete the Tivoli Asset Management for IT deployment.

Before you begin, for IBM WebSphere Application Server Network Deployment,ensure that the Cell and all related nodes are active.


You need to complete the manual configuration of each server you plan to notconfigure using the autoconfigure feature of the installation program before youactually install the product.

Ensure that all of your middleware is at the level described in “Hardware andsoftware requirements” on page 3.Related concepts

“Deployment topologies” on page 10A typical deployment lifecycle typically begins with a single-server topology thatwould move through phases of demonstration, functional proof-of-concept, andtesting integration within the existing environment. It then gradually movestowards a pilot multi-server environment before finally implementing a productiondeployment within the enterprise.“Reusing existing middleware components” on page 16You can reuse some existing middleware installations as IBM Tivoli AssetManagement for IT components. If you plan to do so, ensure that they are at thelevel supported by Tivoli Asset Management for IT. The middleware andinstallation programs do not provide a mechanism for patching unsupportedservers, nor do these programs provide remote prerequisite checks to ensure thatthey are at the right level.

Manually configuring the database serverIf you choose to not have the IBM Tivoli Asset Management for IT installationprogram automatically configure the database server, you need to complete themanual configuration before you use the Tivoli Asset Management for ITinstallation program.

v UNIX For IBM DB2 on UNIX systems, ensure that you have a minimum of 8GB (binary) free of space in the DB2 database instance home directory(/home/ctginst1) in order to meet the default table space disk spacerequirements of the DB2 install.

v Windows For IBM DB2 on Windows, ensure that you have a minimum of 8 GBof free space in the DB2 installation directory.

Manually configuring DB2 9.xFor better performance, you might need to manually configure IBM DB2 9.x beforerunning the IBM Tivoli Asset Management for IT installer to set the preferableenvironment on different operating systems.

About this task

To configure an existing IBM DB2 9.x server for use with Tivoli Asset Managementfor IT, complete the following steps before launching the installation program:

Procedure1. Create system users:

a. Log in to the system as a user that has administrative permissions on thesystem.

b. DB2 requires user accounts that are operating system user accounts. Createoperating system users named ctginst1 and maximo, using usermanagement tools available on the system.


c. AIX For AIX, use SMIT to add the users. For the ctginst1 user,assign the primary group as db2grp1 and secondary groups of staff anddasadm1. For the maximo user, it is not necessary to assign a specific group.After the user IDs have been created, log in to the system using the userIDs and change the password for each account.

2. Create the DB2 instance:a. Use the following command to create the DB2 instance:

Windows Windows:db2icrt -s ese -u db2admin,password -r 50005,50005 ctginst1

Linux Linux:db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1

AIX AIX:db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1

b. Set the listening port for the instance. For example, for Windows

Windows:db2 update dbm cfg using svcename 50005

c. Set instance service to start automatically. For example, for Windows

Windows:sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance:

Windows Windows:db2start

UNIX UNIX:su - ctginst1db2start

3. Create a database:a. Open up the DB2 Control Center for the instance you plan to use:

Windows Windows:

1) Open a command window.2) Type the following command:

set DB2INSTANCE=ctginst1db2set DB2COMM=tcpip

3) Type the following command:db2cc

UNIX UNIX:

1) Open a command window.2) Source the instance you plan to use.3) Type the following command:

db2cc

b. From the DB2 Control Center, navigate to All Systems →system_hosting_the_database_instance → Instances.

c. Right-click the Databases folder located below the instance name, and thenselect Create Database → With Automatic Maintenance.

d. From the Specify a name for your new database panel, enter maxdb71 forboth the Database name and Alias fields.

Chapter 8. Installing with manual middleware configuration 131

e. Enable the Enable database for XML option. It creates a Unicode databasewith a code set of UTF-8.

f. Click Next.g. From the Specify where to store your data panel, click Next. Alternatively,

if you do not want to use the database path as the storage path, specify adifferent directory. If you specify a path, the directory must exist.

h. From the Select your maintenance strategy panel, select Yes, I can specifyan offline maintenance window of at least an hour when the database isinaccessible, and then click Next.

i. From the Specify when offline automatic maintenance activities can run,provide scheduling details for offline maintenance, and then click Next.

j. From the Provide a valid SMTP server panel, enter the name of the SMTPserver that is used to communicate DB2 messages concerning this database,and then click Next.

k. From the Review the actions that appears when you click Finish panel,review the choices you have made, and then click Finish.

The database is created.

AIX For AIX 5.3 systems, you can use the following command to createthe DB2 instance.db2icrt –a SERVER –s ese –p 50005 –u db2fenc1 ctginst1

To create the database on AIX 5.3 systems, switch the user to ctginst1, and usethe following command:db2 create database maxdb71 using codeset UTF-8 territory us pagesize 32 K

4. Configure the database.a. Right-click the maxdb71 database created in the previous step, and choose

Configure Parameters.b. From the Database Configuration panel, select the LOGFILSIZ value and

click the button labeled with the ellipsis (...) in the Value column.c. Enter 4096, and then click OK.d. From the Database Configuration panel, select the APP_CTL_HEAP_SZ

value and click the button labeled with the ellipsis (...) in the Valuecolumn.

e. Enter 16384, and then click OK.f. From the Database Configuration panel, select the APPLHEAPSZ value

and click the button labeled with the ellipsis (...) in the Value column.g. Enter 2048, and then click OK.h. From the Database Configuration panel, select the LOCKLIST value and

click the button labeled with the ellipsis (...) in the Value column.i. Enter 30000, and then click OK.j. From the Database Configuration panel, select the LOGSECOND value

and click the button labeled with the ellipsis (...) in the Value column.k. Enter 15, and then click OK.l. From the Database Configuration panel, click OK.m. Click Close.n. Restart the database by right-clicking the ctginst1 instance, clicking Stop,

and then clicking Start.


Note: AIX For AIX 5.3 systems, you cannot launch the DB2 ControlCenter locally. The best way to configure the database on AIX 5.3 systems is toconfigure it remotely from a system that can run the DB2 Control Center,using the DB2 client.

5. Add users to the database.a. Once the database has restarted, right-click it and select Authorities.b. From the User tab of the Database Authorities window, click Add User.c. From the Add User dialog, select the user maximo, and then click OK.d. Highlight the user, maximo in the Database Authorities window, and click

Grant All.e. Click OK.

6. Create table space:a. From the DB2 Control Center, locate and right-click the Table Spaces entry

under the DB2 database that you created for use with Tivoli AssetManagement for IT.

b. From the right-click menu, select Create.c. Specify MAXDATA as your new table space, and then click Next.d. Select Regular as the type of table space and then click Next.e. Click Create to create a buffer pool for the table space.f. Specify MAXBUFPOOL as your new buffer pool, and then change the Page size

value to 32 and the Size in 32 KB pages value to 4096.g. Ensure the Create buffer pool immediately choice is selected, and then

click OK.h. Highlight the newly created buffer pool and click Next.i. From the Specify the extent and prefetch sizes for this table space panel,

choose the Between 200 MB and 2 GB option, and leave Extent size as 32,and then click Next.

j. Define a hard disk specification by choosing Server (SCSI), and then clickNext.

k. Click Finish.

Note: By default, index data is stored in the data table space. If you wouldrather create a separate index table space, you could create one.

7. Grant permissions for the table space:a. From the DB2 Control Center, locate and right-click the MAXDATA Table

Spaces entry under the DB2 database that you created for use with TivoliAsset Management for IT.

b. From the right-click menu, select Privileges.c. Click Add User.d. Select the user maximo, and then click OK.e. From the Privileges drop-down menu, select Yes, and then click OK.

Note: If you created a separate index table space, grant permissions for it atthis time.

8. Create a schema:a. From the DB2 Control Center, locate and right-click the Schema entry


b. From the right-click menu, select Create.


c. Specify a name for your new schema, and then click OK. This name mustbe the same as was used for the Database user ID.

d. Right-click on the new schema name and select Privileges.e. From the Privileges drop-down menus, select Add User, and then select

the maximo user.f. Click OK.g. Select the maximo user and then click Grant all.h. From the dialog box, select No Grant, and then click OK.

9. Create a temporary table space:a. From the DB2 Control Center, locate and right-click the Table Spaces entry


b. From the right-click menu, select Create.c. Specify MAXTEMP for your new table space, and then click Next.d. Select System temporary as the type of table space and then click Next.e. Select the previously created buffer pool (MAXBUFPOOL), and click Next.f. From the Specify the extent and prefetch sizes for this table space panel,

choose the Between 200 MB and 2 GB option, and leave Extent size as 32,and then click Next.

g. Define a hard disk specification by choosing Server (SCSI), and then clickNext.

h. Specify the dropped table recovery option for the table space by enablingthe Enable dropped table recovery option, and then click Next.

i. Click Finish.10. Refer to the tables presented in “Hardware and software requirements” on

page 3 and install the appropriate fix pack. Ensure that you review andcomplete all the installation and post-installation tasks contained within thefix pack readme file. Failure to do so can potentially cause the Tivoli AssetManagement for IT installation to fail. Refer to the appropriate productsupport page for more information.

What to do next

After you have installed the fix pack, run the dasupdt command to update theDB2 Administration Server to the applied fix pack. Refer to the DB2 Version 9.7 forLinux, UNIX, and Windows information center to find out more about commandsupdating DB2 Administration Server.

Also run the db2iupdt command to update the DB2 instance. Start by firststopping all processes that are running for the database instance (ctginst1), andthen run the following command:

Windows Windows:C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

UNIX UNIX:db2_install_dir/instance/db2iupdt ctginst1

Manually configuring DB2 8.2This section contains instructions for manually configuring DB2 8.2 servers for useby IBM Tivoli Asset Management for IT. Tivoli Asset Management for IT supportsIBM DB2 8.2 only when manually configured.


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.cmd.doc/doc/r0011816.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.cmd.doc/doc/r0011816.html

About this task

To configure an existing IBM DB2 8.2 server for use with Tivoli Asset Managementfor IT, complete the following steps before launching the product installationprogram:

Procedure1. Create system users:

a. Log in to the system as a user that has administrative permissions on thesystem.

b. DB2 requires user accounts that are operating system user accounts. Createoperating system users named ctginst1 and maximo, using usermanagement tools available on the system.

AIX For AIX, use SMIT to add the users. For the ctginst1 user,assign the primary group as db2grp1 and secondary groups of staff anddasadm1. For the maximo user, it is not necessary to assign a specific group.After the user IDs have been created, log in to the system using the userIDs and change the password for each account.

2. Create the DB2 instance:a. Use the following command to create the DB2 instance:

Windows Windows:db2icrt -s ese -u db2admin,password -r 50005,50005 ctginst1

Linux Linux:db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1

AIX AIX:db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1

b. Set the listening port for the instance:

Windows Windows:db2 update dbm cfg using svcename 50005

c. Set instance service to start automatically:

Windows Windows:sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance:

Windows Windows:db2start

UNIX UNIX:su - ctginst1db2start

3. Create the database:

Windows Windows:

a. Open a command window and type the following command:set DB2INSTANCE=ctginst1

b. Type db2cmd to open the DB2 Command Window.c. From the new instance window issue the following commands:

db2startdb2 create db maxdb71 using codeset utf-8 territory us pagesize32 k


UNIX UNIX:

a. Open a command window and type the following command:su - ctginst1

b. From the new instance window issue the following commands:db2startdb2 create db maxdb71 using codeset utf-8 territory us pagesize32 k

4. Configure the database:a. From the DB2 Command Window, type the following command:

db2cc

b. From the DB2 Control Center, navigate to All Systems → DB2_server →Instances → CTGINST1 → Databases → MAXDB71.

c. Right-click the maxdb71 database and choose Configure Parameters.d. From the Database Configuration panel, select the LOGFILSIZ value and

click the button labeled with the ellipsis (...) in the Value column.e. Enter 16384, and then click OK.f. From the Database Configuration panel, select the APP_CTL_HEAP_SZ

value and click the button labeled with the ellipsis (...) in the Valuecolumn.

g. Enter 2048, and then click OK.h. From the Database Configuration panel, select the APPLHEAPSZ value

and click the button labeled with the ellipsis (...) in the Value column.i. Enter 1024, and then click OK.j. From the Database Configuration panel, select the LOCKLIST value and

click the button labeled with the ellipsis (...) in the Value column.k. Enter 15, and then click OK.l. From the Database Configuration panel, select the LOGSECOND value

and click the button labeled with the ellipsis (...) in the Value column.m. Enter 4, and then click OK.n. From the Database Configuration panel, click OK.o. Click Close.p. Restart the database by right-clicking the ctginst1 instance, clicking Stop,

and then clicking Start.5. Add users to the database:

a. Once the database has restarted, right-click it and select Authorities.b. From the User tab of the Database Authorities window, click Add User.c. From the Add User dialog, select the user maximo, and then click OK.d. Highlight the user, maximo in the Database Authorities window, and click

Grant All.e. Click OK.

6. Create table space:a. From the DB2 Control Center, locate and right-click the Table Spaces entry


b. From the right-click menu, select Create.c. Specify MAXDATA as your new table space, and then click Next.d. Select Regular as the type of table space, and then click Next.e. Click Create to create a buffer pool for the table space.


f. Specify MAXBUFPOOL as your new buffer pool, and then change the Page sizevalue to 32 and the Size in 32 KB pages value to 4096.

g. Ensure the Create buffer pool immediately choice is selected, and thenclick OK.

h. Highlight the newly created buffer pool and click Next.i. From the Space management panel, specify Database-managed space and

click Next.j. From the Containers panel, click Add.

k. Set the Type to File, Size to 5000 MB, and File name to CTGDAT. UNIX

For UNIX, enter /home/ctginst1 as the location of the file.l. Click OK, and then click Next.m. From the Specify the extent and prefetch sizes for this table space panel,

click Next.n. Define a hard disk specification by choosing Server (SCSI), and then click

Next.o. Specify the dropped table recovery option for the table space by enabling

the Enable dropped table recovery option, and then click Next.p. From the Summary panel, click Finish.

Note: By default, index data is stored in the data table space. If you wouldrather create a separate index table space, you could create one at this point.

7. Create a temporary table space:a. From the DB2 Control Center, locate and right-click the Table Spaces entry


b. From the right-click menu, select Create.c. Specify MAXTEMP for your new table space, and then click Next.d. Select System temporary as the type of table space and then click Next.e. Select the previously created buffer pool (MAXBUFPOOL), and click Next.f. From the Space management panel, specify Database-managed space, and

then click Next.g. From the Containers panel, click Add.

h. Set the Type to File, Size to 3000MB, and File name to CTGTMP. UNIX

For UNIX, enter /home/ctginst1 as the location of the file.i. Click OK, and then click Next.j. From the Specify the extent and prefetch sizes for this table space panel,

click Next.k. Define a hard disk drive specification by choosing Server (SCSI), and then

click Next.l. From the Summary panel, click Finish.

8. Grant permissions for the table space:a. From the DB2 Control Center, locate and right-click the MAXDATA table

spaces entry under the DB2 database that you created for use with TivoliAsset Management for IT.

b. From the right-click menu, select Privileges.c. Click Add User.d. Select the user maximo, and then click OK.e. From the Privileges drop-down menu, select Yes, and then click OK.


Note: If you created a separate index table space, grant permissions for it atthis time.

9. Create a schema:a. From the DB2 Control Center, locate and right-click the Schema entry


b. From the right-click menu, select Create.c. Specify a name for your new schema, and then click OK. This name must

be the same as was used for the database user ID.d. Right-click on the new schema name and select Privileges.e. From the Privileges drop-down menus, select Add User, and then select

the maximo user.f. Click OK.g. Select the maximo user and then click Grant all.h. From the dialog box, select No Grant, and then click OK.

10. Install the appropriate fix pack. Refer to the tables presented in “Hardwareand software requirements” on page 3.

What to do next

If you installed a fix pack, run the dasupdt command to update the DB2Administration Server to the applied fix pack.

After you have installed a fix pack, you will also need to run the db2iupdtcommand to update the DB2 instance. Start by first stopping all processes that arerunning for the database instance (ctginst1), and then run the followingcommand:

Windows Windows:C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

UNIX UNIX:db2_install_dir/instance/db2iupdt ctginst1

Manually configuring Oracle 11gUse the following instructions to manually configure Oracle 11g for use with IBMTivoli Asset Management for IT.

Before you begin

Set the max_cursors size for the Tivoli Asset Management for IT database to 1000before Tivoli Asset Management for IT installation.

About this task

To configure an existing Oracle 11g server for use with Tivoli Asset Managementfor IT, complete the following steps before launching the installation program:

Procedure1. Log in as the Oracle software user. Typically this user is named oracle.2. Create the database listener. The listener manages requests to connect to the

database.a. Open the Oracle Network Configuration Assistant application.


b. From the Welcome panel, select Listener configuration, and then click Next.c. From the action panel, select Add, and then click Next.d. Enter a name for the listener or accept the default value, and then click

Next.e. Accept the default Selected Protocols listed by clicking Next.f. From the port panel, select Use the standard port of 1521, and then click

Next.g. Select No to indicate that you are finished configuring listeners, and then

click Next.h. From the Listener Configuration Done panel, click Next.i. Click Finish.

3. Create a database for use by Tivoli Asset Management for IT.a. Open the Oracle Database Configuration Assistant.b. Click Next.c. Select Create a Database, and then click Next.d. Select General Purpose or Transaction Processing, and then click Next.e. Enter ctginst1 for both the Global Database Name value and the SID value,

and then click Next.f. Leave the defaults selected, and click Next.g. Ensure Use the Same Administrative Password for All Accounts is

selected, enter a password for Oracle users, and then click Next

h. Ensure File System is selected as the storage mechanism to use for thedatabase, and then click Next.

i. Ensure Use Database File Locations from Template is selected as the valueto use for database file location, and then click Next.

j. Leave defaults selected for the database recovery options panel, and thenclick Next.

k. From the Sample Schemas panel, click Next.l. From the memory allocation panel, select Custom, provide the following

values (measured in MB), and then click Next.

Shared Memory ManagementSet this value to Manual Shared Memory Management.

Shared PoolSet this value to 251.

Buffer CacheSet this value to 755.

Java PoolSet this value to 20.

Large PoolSet this value to 114.

PGA SizeSet this value to 380.

m. From the Character Sets tab, select Use Unicode (AL32UTF8),

n. Click All Initialization Parameters....o. Click Show Advanced Parameters.p. Locate the following parameters, change them to the values indicated, and

then click Close.


nls_length_semanticsChange this value to CHAR

open_cursorsChange this value to 1000

cursor_sharingSet this value to FORCE.

shared_pool_reserved_sizeSet to the default value.

q. From the Security Settings panel, accept the defaults, and then click Next.r. From the Automatic Maintenance Tasks panel, accept the defaults, and then

click Next.s. From the Initialization Parameters panel, click Next.t. From the Database Storage panel, click Next.u. From the Creation Options panel, click Finish.v. Once the database has been successfully created, click Password

Management.w. Unlock the CTXSYS account by clearing the check mark in the Lock

Account? column for that entry, enter a password for the account, and thenclick OK.

x. Click Exit to exit the Database Configuration Assistant. The database hasbeen successfully created.

Note: The Oracle Database Configuration Assistant executes theoracle_install_dir/ctx/admin/defaults/drdefus.sql script as part of theconfiguration of the CTXSYS user. It needs to be executed manually if the OracleDatabase Configuration Assistant is not used.

4. Create a table space using the following command in SQL*Plus:Create tablespace maxdata datafile’C:\oracle\product\11.1.0\db_1\dbs\maxdata.dbf’size 1000M autoextend on;

Change the directory specified in the example to the location where thedatabase resides. If the directory does not exist, this command fails.

5. Create a temporary table space using the following command in SQL*Pluscreate temporary tablespace maxtemp tempfile’C:\oracle\product\11.1.0\db_1\dbs\maxtemp.dbf’size 1000M autoextend on maxsize unlimited;

Change the directory specified in the example to the location where thedatabase resides. If the directory does not exist, this command fails.

6. Create the maximo user and grant permissions using the following command inSQL*Plus:create user maximo identified by maximo default tablespace maxdata temporarytablespace maxtemp;grant connect to maximo;grant create job to maximo;grant create trigger to maximo;grant create session to maximo;grant create sequence to maximo;grant create synonym to maximo;grant create table to maximo;grant create view to maximo;grant create procedure to maximo;grant alter session to maximo;grant execute on ctxsys.ctx_ddl to maximo;alter user maximo quota unlimited on maxdata;


If you created a separate table space for indexing, grant access to that indextable space to the maximo user. For example, execute the following command ifyou created a separate table space for indexing called TSI_TAMIT_OWN:alter user maximo quota unlimited on TSI_TAMIT_OWN

These instructions assume that you have not modified the default role sets thatare assigned to the Oracle DBA user or user IDs created to connect to thedatabase. If you restricted the default privileges granted to user IDs, explicitlygrant them to the maximo user. So, for example, if you do not by default grant arole such as the select_catalog_role role to user IDs connecting to the database,in order to deploy Tivoli Asset Management for IT, you need to explicitly grantthat role to the maximo user by executing the SQL*Plus command:grant select_catalog_role to maximo

Manually configuring Oracle 10gIf you want to use the existing Oracle 10g server instance for IBM Tivoli AssetManagement for IT, make sure that you complete these steps before installingTivoli Asset Management for IT.

Before you begin

If you are using Oracle 10g Rel2, ensure the Oracle 10g Rel2 patch 3 is installed.

About this task

To configure an existing Oracle 10g Rel2 or 10g Rel1 server for use with TivoliAsset Management for IT, complete the following steps before launching theinstallation program:

Procedure1. Log in as a user designated as a dba, such as sys or system.2. Create a database for use by Tivoli Asset Management for IT.

a. Open the Oracle Database Configuration Assistant, and click Next.b. Select Create a Database, and then click Next.c. Select General Purpose, and then click Next.d. Enter ctginst1 for both the Global Database Name value and the SID

value, and then click Next.e. Leave the defaults selected, and click Next.f. Ensure Use the Same Password for All Accounts is selected, enter a

password for Oracle users, and then click Next.g. Ensure File System is selected as the storage mechanism to use for the

database, and then click Next.h. Ensure Use Database File Locations from Template is selected as the value

to use for database file location, and then click Next.i. Leave defaults selected for the database recovery options panel, and then

click Next.j. From the Sample Schemas panel, click Next.k. From the memory allocation panel, select Custom, provide the following

values (measured in MB), and then click Next.

Shared Memory ManagementSet this value to Manual Shared Memory Management.







l. From the Database Character Set tab, select Use Unicode (AL32UTF8),m. Click All Initialization Parameters....n. Click Show Advanced Parameters.o. Locate the following parameters, change them to the values indicated, and

then click Close.

nls_length_semanticsChange this value to CHAR

open_cursorsChange this value to 1000


shared_pool_reserved_sizeSet to the default value.

p. From the Initialization Parameters panel, click Next.q. From the Database Storage panel, click Next.r. From the Creation Options panel, click Finish.s. From the Confirmation panel, click OK.t. Click Exit to exit the Database Configuration Assistant.The database has been successfully created.

3. Log in to SQL *Plus using the following information:

User Namesystem

PasswordPassword you entered in Step 2f on page 141.

Host Stringctginst1

4. Create a table space using the following command in SQL*Plus:Create table space maxdata datafile’C:\oracle\product\10.2.0\db_1\ctginst1\maxdata.dbf’size 1000M autoextend on;

Change the directory specified in the example to the location where thedatabase resides.

5. Create a temporary table space using the following command in SQL*Plus:Create temporary tablespace maxtemp tempfile’C:\oracle\product\10.2.0\db_1\ctginst1\maxtemp.dbf’size 1000M autoextend on maxsize unlimited;



6. Create the Maximo user and grant permissions using the following commandin SQL*Plus:Create user maximo identified by maximo default table space maxdata temporarytablespace maxtemp;grant create job to maximo;grant create trigger to maximo;grant create session to maximo;grant create sequence to maximo;grant create synonym to maximo;grant create table to maximo;grant create view to maximo;grant create procedure to maximo;grant alter session to maximo;grant execute on ctxsys.ctx_ddl to maximo;alter user maximo quota unlimited on maxdata;

Manually configuring Oracle 9i Rel2If you want to use the existing Oracle 9i Rel2 server instance for IBM Tivoli AssetManagement for IT, make sure that you complete the configuration steps before theproduct installation.

Before you begin

If you are using Oracle 9i Rel2, ensure that Oracle 9.2.0.8 is installed.

About this task

To configure an existing Oracle 9i Rel2 server for use with the product, completethe following steps before launching the installation program:

Procedure1. Create a database for use by Tivoli Asset Management for IT:

a. Open the Oracle Database Configuration Assistant, and click Next.b. Select Create a database, and then click Next.c. Select General Purpose, and then click Next.d. Enter ctginst1 for both the Global Database Name value and the SID

value, and then click Next.e. Leave the default of Dedicated Server Mode selected, and click Next.f. From the Memory tab, select Custom, enter the following values (MB), and

then click Next:







g. Select the Character Sets tab and select Use Unicode (AL32UTF8) as theDatabase Character Set.

h. Click All Initialization Parameters.i. Locate the following parameters, change them to the values indicated, and

then click Close, and then Next:

nls_length_semanticsChange this value to CHAR.

open_cursorsChange this value to 1000.


j. From the Database Storage panel, click Next.k. From the Creation Options panel, select the Create Database option, and

click Finish.l. From the Confirmation panel, click OK.m. Once the database has been successfully created, click Password

Management.n. Unlock the CTXSYS account by removing the check mark in the Lock

Account? column for that entry, enter a password for the account, and thenclick OK.

o. Click Exit to exit the Database Configuration Assistant.

The database has been successfully created.2. Create a table space using the following command in SQL*Plus:

Create table space maxdata datafile’C:\oracle\db_1\maxdata\maxdata.dbf’size 1000M autoextend on;


3. Create a temporary table space using the following command in SQL*Plus:create temporary table space maxtemp tempfile’C:\oracle\db_1\maxtemp\maxtemp.dbf’size 1000M autoextend on maxsize unlimited;


4. Create the Maximo user and grant permissions using the following commandin SQL*Plus:create user maximo identified by maximo default table space maxdata temporarytable space maxtemp;grant connect to maximo;grant create job to maximo;grant create trigger to maximo;grant create session to maximo;grant create sequence to maximo;grant create synonym to maximo;grant create table to maximo;grant create view to maximo;grant create procedure to maximo;grant alter session to maximo;grant execute on ctxsys.ctx_ddl to maximo;alter user maximo quota unlimited on maxdata;


Manually configuring SQL ServerWindows If you want to use the existing SQL Server instance for IBM Tivoli Asset

Management for IT, make sure that you complete these steps before installing theproduct.

Before you begin

Because Microsoft SQL Server does not support UTF-8, Tivoli Asset Managementfor IT does not have multilingual support when deployed with Microsoft SQLServer.

The server collation settings must be set to the following options:v Dictionary orderv For use with 1252 Character set

About this task

To configure an existing SQL Server 2008 for use with Tivoli Asset Management forIT, complete the following steps before launching the installation program:

Procedure1. Configure the listener port.

If enabled, the default instance of the Microsoft SQL Server Database Enginelistens on TCP port 1433. Named instances of the SQL Server Database Engineand SQL Server Compact Edition are configured for dynamic ports, whichmeans they select an available port when the SQL Server service is started.When connecting to a named instance through a firewall, configure theDatabase Engine to listen on a specific port, so that the appropriate port can beopened in the firewall.a. Open Programs → Microsoft SQL Server 2008 → Configuration Tools →

Microsoft SQL Server Configuration Manager.b. From the Microsoft SQL Server Configuration Manager navigation pane,

expand SQL Server 2008 Network Configuration → Protocols foryour_instance_name for the instance name to be used with Tivoli AssetManagement for IT, and then double-click TCP/IP.

c. In the TCP/IP Properties dialog box, click the IP Addresses tab.d. For each IP address listed, ensure the TCP Dynamic Ports field is blank. If

the TCP Dynamic Ports field contains a value of 0, that IP address is usingdynamic ports. Since Tivoli Asset Management for IT requires SQL Serverto listen on a static port, this field must be blank.

e. For each IP address listed, enter 1433 for the TCP Port field, and click OK.f. From the SQL Server Configuration Manager navigation pane, click SQL

Server 2008 Services.g. Right-click SQL Server instance_name and then click Restart, to stop and

restart SQL Server.2. Verify that you enabled the Full-text Search setting during the installation of

Microsoft SQL Server 2008. To determine if Full-text Search is installed on yourexisting Microsoft SQL Server database, perform the following steps:a. Open SQL Query Analyzer. You can run SQL Query Analyzer from the Start

menu, from inside SQL Server Enterprise Manager, or from the commandprompt by executing isqlw.

b. Type the following command:


select FULLTEXTSERVICEPROPERTY ( ’IsFulltextInstalled’ )

If you did not install Full-text Search (the resulting value is zero), you need todo so at this time. The following steps provide a general guideline describinghow you can change this and other settings after having installed SQL Server.a. Insert the “Microsoft SQL Server 2008” CD-ROM onto the server where

you had it installed originally.b. Navigate through the installation dialog boxes and from the Setup Type

dialog box, select Custom.c. Check the Full-Text Search option.d. Complete remaining installation steps. You finish the installation process by

choosing to restart the server.3. Create a SQL Server Database for Maximo

a. Open SQL Server Enterprise Manager Studio: Start → Programs → MicrosoftSQL Server 2008 → SQL Server Management Studio.

b. Right-click the Databases folder from the navigation tree, and select NewDatabase.

c. In the Database Properties dialog box, in the General tab, specify a uniquedatabase name (for example maxdb71).

d. For the maxdb71 Logical Name, change the Initial size attribute to 500 (MB),and also set the value of the Autogrowth field to By 1 MB, unrestrictedgrowth.

e. If you prefer, modify the log settings to accommodate your productionenvironment.

f. Click Add.4. Create the Maximo user for SQL Server:

a. Open SQL Server Enterprise Manager Studio: Start → Programs → MicrosoftSQL Server 2008 → SQL Server Management Studio.

b. Click New Query.c. Select the Tivoli Asset Management for IT database (maxdb71) from the

Available Databases drop-down menu.d. Enter the following script to create the Maximo user.

sp_addlogin MAXIMO,MAXIMOgo

e. Click Execute.f. Enter the following script to change the database owner to maximo.

sp_changedbowner MAXIMOgo

g. Click Execute.

What to do next

Note: If you add additional logical names to the database and set their file groupto a value other than PRIMARY, you will have to complete the following steps afteryou have completed setting up the database and created the Maximo user:1. Run the Tivoli Asset Management for IT installation program and choose the

Do not run the configuration step now option.2. Add the following property to the tamit_install_dir\maximo\applications\

maximo\properties\maximo.properties file:Database.SQL.DataFilegroupName=your_logical_name


3. Execute the configuration steps outside of the Tivoli Asset Management for ITinstallation program by using the taskrunner utility, located in thetamit_install_dir\scripts directory.

These additional steps must be completed only if you have added additionallogical names to the database and set their file group to a value other thanPRIMARY.

Manually configuring the directory serverYou need to complete the manual configuration of the directory server before youuse the Tivoli Asset Management for IT installation program if you choose to nothave the Tivoli Asset Management for IT installation program automaticallyconfigure it.

Important: When entering LDAP values for the installation panel fields, entries inLDIF files, or values you enter directly into a directory instance using the directoryserver own tools, be aware of the product-specific syntax rules for using specialcharacters in a LDAP string. In most cases, special characters must be preceded byan escape character in order to make it readable by the directory server. Failing toescape special characters contained in a LDAP string used with Tivoli AssetManagement for IT results in errors.

Many directory server products consider a blank space as a special character that ispart of the LDAP string. Therefore, if you mistakenly enter a LDAP string thatcontains a blank, at the end of a field value, for example, and you do not precedethe blank character with an escape character, you encounter errors that are difficultto troubleshoot.

Refer to the product documentation for your directory server for more informationabout special characters in LDAP strings.

Manually configuring Directory ServerTo configure IBM Tivoli Directory Server before launching the IBM Tivoli AssetManagement for IT installation program, you need to create a Directory Serverinstance.

Procedure1. Create a user on the system and assign it to the appropriate group:

Windows Windows:Create the user idsccmdb and make it a member of the WindowsAdministrators group.

UNIX UNIX:Create the user idsccmdb and make it a member of the root, db2grp1,and idsldap groups. The user idsccmdb must have root assigned as itsprimary group.

2. If the Instance Administration Tool is not already started, ensure that you arelogged in as an administrator on the system, and then start the tool:

Windows Windows:Select Programs → IBM Tivoli Directory Server 6.2 → InstanceAdministration Tool.


UNIX UNIX:Type in /opt/IBM/ldap/V6.2/sbin/idsxinst at the command line.

3. From the instance administration tool, click Create.4. On the Create a directory server instance window, click Create a new

directory server instance, and then click Next.5. From the Instance details window, complete the following fields, and then

click Next.

User nameSelect idsccmdb as the system user ID of the user who owns thedirectory server instance. This name is also the name of the directoryserver instance.

Install locationEnter the location where the directory server instance files are stored.

Encryption seed stringType a string of characters that are used as an encryption seed. Thisvalue must be a minimum of 12 characters.

Instance descriptionEnter a brief description of the instance.

6. From the DB2 instance details panel, enter idsccmdb as the value for the DB2instance name field, and then click Next.

7. From the TCP/IP settings for multihomed hosts panel, select Listen on allconfigured IP addresses, and then click Next.

8. On the TCP/IP port settings panel, complete the following fields, and thenclick Next.

Server port numberEnter 389 as the contact port for the server.

Server secure port numberEnter 636 as the secure port for the server.

Admin daemon port numberEnter 3538 as the administration daemon port.

Admin daemon secure port numberEnter 3539 as the administration daemon secure port.

9. From the Option steps panel, leave the following options selected, and thenclick Next.

Configure admin DN and passwordYou configure the administrator DN and password for the directoryserver instance now.

Configure databaseYou configure the database for the directory server instance now.

10. From the Configure administrator DN and password window panel, completethe following fields, and then click Next.

Administrator DNEnter cn=root for the administrator distinguished name.

Administrator PasswordEnter a password for the Administrator DN.

11. From the Configure database panel, complete the following fields, and thenclick Next.


Database user nameEnter idsccmdb as the database user.

PasswordEnter the password for the idsccmdb user.

Database nameEnter idsccmdb as the database to be used with this directory instance.

12. From the Database options panel, complete the following fields, and then clickNext.

Database install locationEnter the location where you installed DB2.

Character-set optionLeave the Create a universal DB2 database (UTF-8/UCS-2) optionselected.

13. From the Verify settings panel, review the instance creation details provided,and then click Finish to create the idsccmdb instance.

14. Click Close to close the window and return to the main window of theinstance administration tool.

15. Click Close to exit the instance administration tool.16. Ensure that the server is stopped:

Windows Windows:IBM Tivoli Directory Server Instance V6.2 - idsccmdb

UNIX UNIX:V6.2 ibmslapd server daemon

17. Launch the directory server configuration tool:

Windows Windows:Select Programs → IBM Tivoli Directory Server 6.2 → InstanceAdministration Tool.

UNIX UNIX:Type in /opt/IBM/ldap/V6.2/sbin/idsxcfg at the command line.

18. Click Configure.19. Select Manage suffixes.20. From the Manage suffixes panel, type the following suffix, and then click

Add:o=IBM,c=US

Then, click OK.21. Create and save an LDIF file.

Add the following DNs:v ou=SWG,o=IBM,c=US

v ou=users

v ou=groups

Define the following users and groups and their positions within the ou=usersand ou=groups of the DN you created. These users and groups are defined inorder for Virtual Member Manager to be used to secure Tivoli AssetManagement for IT.


Important: Before you begin this procedure, ensure that you have thefollowing users and groups created in your LDAP repository:

Table 15. Tivoli Asset Management for IT required users and groups

User Groups

wasadmin

maxadmin MAXADMIN (must be uppercase)

mxintadm MAXADMIN (must be uppercase)

maxreg

Note: Windows If you create the LDIF file on Windows, ensure that youremove the ^M characters from the file before using.

22. From the Directory Server Configuration Tool, click Import LDIF data. Usethe browse button to locate the LDIF file.

23. Click Import.24. Close the Directory Server Configuration Tool, and restart the server.

Example

Here is an example of the default base LDIF data:dn: o=ibm,c=usobjectClass: topobjectClass: organizationo: IBM

dn: ou=SWG, o=ibm,c=usou: SWGobjectClass: topobjectClass: organizationalUnit

dn: ou=groups,ou=SWG, o=ibm,c=usou: groupsobjectClass: topobjectClass: organizationalUnit

dn: ou=users,ou=SWG, o=ibm,c=usou: usersobjectClass: topobjectClass: organizationalUnit

dn: cn=wasadmin,ou=users,ou=SWG, o=ibm,c=usuid: wasadminuserpassword: wasadminobjectclass: organizationalPersonobjectclass: inetOrgPersonobjectclass: personobjectclass: toptitle: WebSphere Administratorsn: wasadmincn: wasadmin

dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxadminuid: maxadminobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxadmincn: maxadmin




Manually configuring Microsoft Active DirectoryWindows You can choose to configure a Microsoft Active Directory resource

manually for better use with Tivoli Asset Management for IT.

Before you begin

Use this procedure to manually create users and groups within Microsoft ActiveDirectory. You can create these users and groups automatically. Creating usersautomatically requires SSL communication between Microsoft Active Directory andWebSphere Application Server Network Deployment.

Important: The users and passwords you create in the following steps must matchthis exact configuration for the deployment to succeed. It is sometimes necessary totemporarily alter the Microsoft Active Directory security policy to create theseaccounts in the required format. After installation, you can change these defaultpasswords to conform to a stricter security policy.

Although you can use Microsoft Windows Server 2008 as a platform for theadministrative workstation, or to host middleware, Tivoli Asset Management for ITdoes not support Active Directory on Microsoft Windows Server 2008.

About this task

Before starting theTivoli Asset Management for IT installation program, configureMicrosoft Active Directory. Complete the following steps

Procedure1. Select Start → Control Panel → Administrative Tools → Microsoft Active

Directory Users and Computers and then select the domain that you will beworking with.

2. Edit the functional level of the domain by selecting Action → Raise DomainFunctional Level. The Raise Domain Functional Level dialog box is displayed.

3. Select Microsoft Windows Server 2003 from the Select an available domainfunctional level menu, and then click Raise. An alert dialog box is displayed.

4. Click OK.5. When the domain raise task has completed, click OK.


6. In the Microsoft Active Directory Users and Computers interface, right-clickthe domain to work with. Select New → Organizational Unit.

7. Enter a name for the new Organizational Unit (OU), for example, SWG, andthen click OK.

8. Create a groups object under the SWG organizational unit:a. Right-click the SWG OU, and select New → Organizational Unit.b. Enter Groups as the name for the new OU then click OK.

9. Create a users object under the SWG organizational unit:a. Right-click the SWG OU, and select New → Organizational Unit.b. Enter Users as the name for the new OU then click OK.

10. Create the wasadmin user:a. Right click the Users OU and select New → User.b. From the New Object - User dialog, enter the following values, and then

click Next:

First nameEnter wasadmin.

InitialsLeave this field blank.

Last nameLeave this field blank.

Full nameEnter wasadmin.

User login nameEnter wasadmin in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is filled with the same value (wasadmin) entered for theUser login name.

c. From the next panel, enter the following information, and then click Next:

PasswordEnter a 7 character password for wasadmin.

User must change password at next logonEnsure this check box is cleared.

User cannot change passwordEnsure this check box is selected.

Password never expiresEnsure this check box is selected.

Account is disabledEnsure this check box is cleared.

The preceding values are examples. Enter values that comply with thepassword policy of your organization.

d. Review the password settings in the summary panel, and click Finish.11. Create an administrator user, for example maxadmin:

a. Right click the Users OU and select New → User.b. From the New Object - User dialog, enter the following values, and then

click Next:


First nameEnter maxadmin.



Full nameEnter maxadmin.

User login nameEnter maxadmin in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is populated with the same value (maxadmin) enteredfor the User login name.


PasswordEnter maxadmin as the password for the maxadmin user.

This password value is required and expected by the Tivoli AssetManagement for IT installation program.

If you must use a different password value for this user, you mustdefer the configuration step of the Tivoli Asset Management for ITinstallation. Modify property values and then complete theconfiguration using the taskrunner utility.

Complete the following steps if you choose to use a different valuefor the maxadmin password:1) Complete middleware installation and configuration, including

the manual Microsoft Active Directory configuration tasks.Provide a password value other than maxadmin for themaxadmin user.

2) Begin the Tivoli Asset Management for IT installation.3) Proceed with the installation and select the option Copy files

now, and perform installation configuration later, manually. Complete the installation.

4) Edit the <MAM_HOME>\etc\install.properties file and providethe value for the mxe.adminPasswd property.

5) Complete product configuration by using the taskrunner utility:CCMDB_HOME\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

6) Edit the <CCMDB_HOME>maximo\reports\birt\tools\reporttools.properties file and provide the same passwordvalue for the maximo.report.birt.password property.







d. Review the password settings in the summary panel, and click Finish.12. Create the mxintadm user:


click Next:

First nameEnter mxintadm.



Full nameEnter mxintadm.

User login nameEnter mxintadm in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is displayed with the same value (mxintadm) entered forthe User login name.


PasswordEnter a seven character value as the password for the mxintadmuser.





The preceding values are examples. You must set these fields to valuesthat comply with the password policy of your organization.

d. Review the password settings in the summary panel, and click Finish.13. Create the maxreg user:


click Next:

First nameEnter maxreg.




Full nameEnter maxreg.

User login nameEnter maxreg in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is filled with the same value (maxreg) entered for theUser login name.


PasswordEnter a seven character value as the password for the maxreg user.






d. Review the password settings in the summary panel, and click Finish.14. You can now exit the Microsoft Active Directory Users and Computers tool.

What to do next

Microsoft Active Directory configuration is finished and you are now ready toinstall the remaining Tivoli Asset Management for IT middleware and configurethe J2EE server to use Microsoft Active Directory.Related concepts

“Planning for security” on page 19Planning for security includes choosing a security option, deciding which users canwork with each application in IBM Tivoli Asset Management for IT, and optionallywhich users can work with which assets.

Configuring SSL between Microsoft Active Directory andWebSphere Application Server Network DeploymentConfiguring SSL between Microsoft Active Directory and WebSphere ApplicationServer Network Deployment allows the installation program to create users.

Before you begin

To enable the Tivoli Asset Management for IT installation program to automaticallycreate users and groups within Microsoft Active Directory, you have to configureSSL communication between Microsoft Active Directory and WebSphereApplication Server Network Deployment.

You must enable SSL for Microsoft Active Directory, generate a certificate, and thenadd that certificate to WebSphere Application Server Network Deployment.


Changing the name or domain of the certificate authority at any point invalidatescertificates previously issued from that authority.

Ensure that you have host name resolution set up properly in yourenvironment. Communication failures occur if the machine hosting MicrosoftActive Directory cannot resolve host names for systems that have been issuedcertificates.

Ensure that you have already installed Microsoft Internet Information Services withASP extensions enabled on the system before configuring the certificate servicerequired for SSL. Microsoft Internet Information Services are a prerequisite of thecertificate service. Microsoft Internet Information Services can be added as aWindows component from the Add/Remove Programs dialog. Add thiscomponent by selecting the Internet Information Services or Application Servercomponent and installing it. If you have IBM HTTP Server installed on the samesystem, you cannot use port 80 for IBM HTTP Server. If IBM HTTP Server wasconfigured to use port 80, you must change it to another value because MicrosoftInternet Information Services must use port 80. After you verify that these twoconditions are met, proceed with setting up certificate services as described in thisprocedure.

Procedure1. Add the Certificate Services component:

a. From the Control Panel of the Microsoft Active Directory server, selectAdd or Remove Programs. Then select Add/Remove WindowsComponents.

b. From the Windows Components panel, select the Certificate Servicesoption, and then click Next.

c. From the CA Type panel, select Stand alone root CA, select the Usecustom settings to generate the key pair and CA certificate option, andthen click Next.

d. From the Public and Private Key Pair panel, select Microsoft StrongCryptographic Provider for the CSP value, select SHA-1 as the Hashalgorithm, set the Key length to 2048, and then click Next.

e. From the CA Identifying Information panel, enter mymachine.ism71.com inthe Common name for this CA field, enter DC=ism71,DC=com for theDistinguished name suffix, set the Validity period to 5 years, and thenclick Next. The values used in this step are example values only. Replacethese values with the details of the machine hosting Microsoft ActiveDirectory.

f. From the Certificate Database Settings panel, you can keep the defaultvalue of C:\WINDOWS\system32\CertLog for both the Certificate databaseand Certificate database log fields, and then click Next. Configuration ofthe component now begins.

g. Click Finish.h. Restart the system.

2. Download a CA certficate:a. Launch Internet Explorer.b. Select Tools → Internet Options → Security and click Sites.c. From the Trusted Sites dialog box, enter http://mymachine.ism71.com in

the Add this Web site to the zone: field, click Add, and then click Close.


d. Enter the following address in the browser: http://mymachine.ism71.com/certsrv

e. From the Certificate Services page, click Download a CA certificate,Certificate Chain, or CRL.

f. From the Download a CA Certificate, Certificate Chain, or CRL page, clickinstall this CA certificate chain. When the task has completed successfully,click the back button.

g. From the Download CA Certificate, Certificate Chain, or CRL page selectCurrent for the CA certificate value, choose Base 64 for the Encodingmethod, and then click Download a CA Certificate.

h. When prompted, specify the type as Security Certificate and save thesecurity certificate file as serverRootCA.cer.

3. Add the Certificates Snap-in:a. Launch the Microsoft Management Console.b. Select File → Add/Remove Snap-in.c. From the Add/Remove Snap-in dialog box, click Add.d. From the Add Standalone Snap-in dialog box, select Certificates and then

click Add.e. Select Computer account and then click Next.f. Select Local computer: (the computer this console is running on) and click

Finish.g. From the Add Standalone Snap-in dialog box, select Certification

Authority and then click Add.h. Select Local computer: (the computer this console is running on) and

click Finish.i. Click Close to close the Add Standalone Snap-in dialog box.j. Click OK on the Add/Remove Snap-in dialog box to close it.

4. Transfer certificates to a store:a. In the Microsoft Management Console, navigate to Console Root →

Certificates (Local Computer) → Third-Party Root CertificationAuthorities.

b. Right-click Certificates and select All Tasks → Import.c. From the File to Import panel of the Certificate Import wizard, browse to

the location of the serverRootCA.cer file, select it, and then click Next.d. From the Certificate Store panel, select Place all certificates in the

following store, click Next, and then click Finish.5. Create and submit a request to the CA:

a. Using Internet Explorer, navigate to http://mymachine.ism71.com/certsrv.From the Certificate Services page, click Request a certificate.

b. From the Request a Certificate page, click advanced certificate request.c. From the Advanced Certificate Request page, click Create and submit a

request to this CA.d. From the Advanced Certificate Request page, enter the following

information and then click Submit.

Identifying InformationEnter the fully qualified name of the machine hosting MicrosoftActive Directory in the Name field. This value must be capitalized,for example MYMACHINE.ISM71.COM.


Type of Certificate NeededSelect Server Authentication Certificate.

Key OptionsFor the CSP field, select Microsoft RSA SChannel CryptographicProvider.

Select the Automatic key container name, Mark keys asexportable, and Store certificate in the local computer certificatestore options.

For the Key Size field, you can either accept the default value of1024, or change it to a more appropriate value.

Additional OptionsSet the Request Format option to PKCS10.

For the Hash Algorithm field, select SHA-1.

For the Friendly Name field, enter the same exact value as enteredfor the Name field.

Default values are sufficient for the remaining fields on this page.e. Click Home to return to the home page for Certificate Services.

6. Install the certificate:a. In the Microsoft Management Console, navigate to Console Root →

Certification Authority (Local) → mycomputer.ism71.com → PendingRequests.

b. In the right pane, right-click the ID of the request, and then select AllTasks → Issue.

c. From Internet Explorer, on the Certificate Services page, click View thestatus of a pending certificate request.

d. From the View the Status of a Pending Certificate Request page, click thecertificate request you created.

e. From the Certificate Issued page, click Install this certificate.f. Restart the system.

7. Verify the private key:a. When the system has restarted, invoke the Microsoft Management Console

and navigate to Console Root → Certificates (Local Computer) → Personal→ Certificates.

b. In the right pane, double-click the entry displayed in uppercase.c. From the Certificate dialog box, ensure you can find the statement You

have a private key that corresponds to this certificate, and then click OK.d. In the right pane, double-click the entry displayed in lowercase.e. From the Certificate dialog box, ensure you can find the statement You

have a private key that corresponds to this certificate, and then click OK.8. Configure the connection:

a. Launch the Microsoft LDP utility.b. Select Connection.c. Select Connect.d. Enter mymachine.ism72.com for Server, 636 for Port, select SSL, and then

click OK. Review the information displayed to verify your configurationvalues.

9. Export certificate files:


a. Launch the Microsoft Management Console and navigate to Console Root→ Certificates (Local Computer) → Personal → Certificates.

b. Right-click the uppercase certificate entry and select All Tasks → Export

c. From the Certificate Export wizard Welcome panel, click Next.d. From the Export Private Key panel, select No, do not export private key,

and then click Next.e. From the Export File Format panel, select Base-64 encoded X.509(.CER),

and then click Next.f. From the File to Export panel, export the certificate as serverRootCA.cer,

click Next, and then click Finish.g. Right-click the lowercase certificate entry and select All Tasks → Export

h. From the Certificate Export wizard Welcome panel, click Next.i. From the Export Private Key panel, select No, do not export private key,

and then click Next.j. From the Export File Format panel, select Base-64 encoded X.509(.CER),

and then click Next.k. From the File to Export panel, export the certificate as serverAuthCert.cer,

click Next, and then click Finish.10. Add signer certificates:

a. Copy serverRootCA.cer and serverAuthCert.cer to the WebSphereApplication Server Network Deployment system.

b. Invoke the WebSphere Application Server Network Deploymentadministrative console.

c. From the WebSphere Application Server Network Deploymentadministrative console, select Security → SSL certificate and keymanagement.

d. Click Keystores and certificates.e. Click CellDefaultTrustStore.f. Click Signer certificates and then click Add.g. From the Add signer certificate page, enter MSADServerRootCA for the Alias,

enter the path (including the file name) to the serverRootCA.cer file in theFile name field, and then click OK.

h. Click Add.i. Enter MSADServerAuthCert for the Alias, enter the path (including the file

name) to the serverAuthCert.cer file in the File name field, and then clickOK.

11. Configure security:a. From the WebSphere Application Server Network Deployment

administrative console, select Security → Secure administration,applications, and infrastructure.

b. From the Available realm definitions drop-down list, select Federatedrepositories, and then click Configure.

c. Click the repository identifier for Microsoft Active Directory listed inRepositories in the realm table.

d. Update the following properties and then click OK.

Port Update this value to 636.

Login propertiesSet this value to cn.


Requires SSL communicationsEnsure that this option is selected.

Use specific SSL aliasEnsure that this option is selected with a value ofCellDefaultSSLSettings.

e. Click Supported entity types and verify that the PersonAccount entitytype is set to cn. If it is not set to cn, click the PersonAccount entity typeand set it and then save the changes.

f. Restart the domain manager.

Manually configuring the J2EE serverYou need to complete the manual configuration of the J2EE server before you usethe Tivoli Asset Management for IT installation program if you choose to not havethe Tivoli Asset Management for IT installation program automatically configure it.

About this task

To configure the J2EE server before launching the Tivoli Asset Management for ITinstallation program, follow these steps:

Procedure1. Manually copy the keystore file from the WebSphere Network Deployment

manager host to a temporary directory on the Tivoli Asset Management for ITadministrative system where you are installing Tivoli Asset Management forIT:was_install_dir/profiles/ctgDmgr01/etc/trust.p12.

2. Launch the profile creation wizard.3. Click Next in the Welcome dialog box.4. Select the create a deployment manager option. Click Next.5. Accept the default value or specify a Profile name. Click Next.6. Accept the default installation location. Click Next.7. Accept the default values or specify the Node name, Host name, and Cell

name. Click Next.8. Review the assigned port numbers. Click Next. Note the Administrative port

number. You will use this context when invoking the console through abrowser.

9. Select the Run the Application Server as a Windows service and log on as alocal system account. Click Next.

10. Click Next in the Profile summary dialog box.11. Select the Launch the First steps console option. Click Finish.12. Click the Installation verification link.13. After Installation Verification completes, close the output window.14. Use the Launchpad command and click the Profile creation wizard to open

the First Steps window (if not open already) .15. Click Next in the Welcome dialog box.16. Select Create a custom profile. Click Next.17. Accept the default values or specify the appropriate information. Click Next.18. Specify a unique Profile name and select the Make this profile the default

check box. Click Next.


19. Accept the default directory path. Click Next.20. Specify a unique node name and the computer name (or IP address) of the

computer where you are performing this installation. Click Next.21. Review the port number listings. Click Next.22. Click Next in the Profile summary dialog box.23. Select the Launch the First steps console check box. Click Finish.24. Click Exit. If another First steps window is open, close it.

Manually configuring Virtual Member Manager on IBMWebSphere Application Server

This procedure provides task information for manually configuring VirtualMember Manager (VMM) to secure Tivoli Asset Management for IT.

Before you begin

During the installation process, the Tivoli Asset Management for IT installationprogram provided you with the option of automatically configuring Tivoli AssetManagement for IT middleware. If you elected to have the Tivoli AssetManagement for IT installer automatically configure the middleware, then it will,among other tasks, perform Virtual Member Manager configuration for you.

If you elected to manually configure the middleware for use with Tivoli AssetManagement for IT, you will have to manually configure Virtual Member Manager.

Virtual Member Manager provides you with the ability to access and maintain userdata in multiple repositories, and federate that data into a single virtual repository.The federated repository consists of a single named realm, which is a set ofindependent user repositories. Each repository might be an entire externalrepository or, in the case of LDAP, a subtree within that repository. The root ofeach repository is mapped to a base entry within the federated repository, which isa starting point within the hierarchical namespace of the virtual realm.

Note that if you intend to configure Virtual Member Manager to use SSL with afederated LDAP repository, it must be done only after a successful Tivoli AssetManagement for IT installation. If Virtual Member Manager is configured to useSSL with a federated LDAP repository prior to completing the Tivoli AssetManagement for IT installation, the installation will fail. Do not configure a VirtualMember Manager LDAP federated repository to use SSL with an LDAP directorybefore installing Tivoli Asset Management for IT. Configure SSL after the TivoliAsset Management for IT installation program has completed successfully.

To add an LDAP directory to the Virtual Member Manager virtual repository, youneed to first add the LDAP directory to the list of repositories available forconfiguration for the federated repository and then add the root of baseEntries to asearch base within the LDAP directory. Multiple base entries can be added withdifferent search bases for a single LDAP directory.

The instructions provided here are for IBM Tivoli Directory Server. If you areconfiguring Virtual Member Manager to use Microsoft Active Directory, substitutevalues you used in “Reusing Microsoft Active Directory” on page 107 and“Manually configuring Microsoft Active Directory” on page 151 where appropriatein this procedure. You will also have to modify the VMMCRONTASK as shown in“Manually configuring directory services” on page 261.


Important: Before you begin this procedure, ensure you have a wasadmin usercreated in your LDAP repository.

About this task

To add the Directory Server to Virtual Member Manager, complete the followingsteps:

Procedure1. Log in to the administrative console, then navigate to Security → Secure

administration, applications, and infrastructure.2. Locate the User account repository section and select Federated repositories

from Available realm definition, and then click Configure.3. Click Manage repositories, located under Related Items.4. Click Add to create new repository definition under the current default realm.5. Enter the following values, and then click Apply and the click Save.

Repository identifierEnter ISMITDS.

Directory typeSelect the directory type, in this example, Directory Server 6.2.

Primary host nameEnter the fully-qualified host name or IP address of the DirectoryServer.

Port Enter 389.

Support referrals to other LDAP serversSet this to ignore.

Bind distinguished nameEnter cn=root.

Bind passwordEnter the password for the bind distinguished name.

Login propertiesLeave this value blank.

Certificate mappingSelect EXACT_DN.

6. Return to the Federated repositories page by clicking Security → Secureadministration, applications, and infrastructure, selecting Federatedrepositories from the Available realm definitions drop-down list, and thenclicking Configure.

7. Locate the Repositories in the realm section and click Add Base entry toRealm.Note that if there is an existing file repository entry in the Repositories in therealm table, you need to select it, click Remove, and save the change, aftercreating the new entry.

8. Enter the following values, and then click Apply and then click Save.

RepositorySelect ISMITDS.


Distinguished name of a base entry that uniquely identifies this set ofentries in the realm

ou=SWG,o=IBM,c=US

Distinguished name of a base entry in this repositoryou=SWG,o=IBM,c=US

9. From the Federated repositories configuration page, enter the following valuesand then click Apply and then click Save:

Realm nameEnter ISMRealm.

Primary administrative user nameEnter wasadmin. This value should be a valid user from the configuredLDAP repository.

Server user identitySelect Automatically generated server identity.

Ignore case for authorizationSelect this check box.

10. Click Supported entity types, and then click PersonAccount.11. From the PersonAccount configuration page, enter the following values:

Entity typeVerify that the value is PersonAccount.

Base entry for the default parentEnter ou=users,ou=SWG,o=IBM,c=US.

Relative Distinguished Name propertiesEnter uid.

12. Click OK and then click Save .13. Click Supported entity types, and then click Group.14. From the Group configuration page, enter the following values:

Entity typeVerify that the value is Group.

Base entry for the default parentEnter ou=groups,ou=SWG,o=IBM,c=US.

Relative Distinguished Name propertiesEnter cn.

15. Click Supported entity types, and then click OrgContainer.16. From the OrgContainer configuration page, enter or verify the following

values:

Entity typeVerify that the value is OrgContainer.

Base entry for the default parentEnter ou=SWG,o=IBM,c=US.

Relative Distinguished Name propertiesEnter o;ou;dc;cn.

17. Click OK and then click Save .18. Navigate to Security → Secure administration, applications, and

infrastructure.


19. From the Secure administration, applications, and infrastructure configurationpage, complete the following:a. Enable Enable administrative security.b. Enable Enable application security.c. Deselect Use Java 2 security to restrict application access to local resources.d. From Available realm definition, select Federated repositories.e. Click Set as current.

20. Click Apply, and then click Save.21. Restart WebSphere Application Server and the managed nodes:

a. was_install_dir\profiles\ctgDmgr01\bin\stopManager.bat

b. was_install_dir\profiles\ctgAppSrv01\bin\stopNode.bat

c. was_install_dir\profiles\ctgDmgr01\bin\startManager.bat

d. was_install_dir\profiles\ctgAppSrv01\bin\startNode.bat

Note: UNIX Substitute UNIX path and file extension values whereappropriate.

What to do next

You have now successfully completed setting up Virtual Member Manager. Thenext step is to perform post install J2EE server tasks.Related concepts


Manually configuring WebSphere Application Server NetworkDeployment

This section contains instructions for manually configuring an existing WebSphereApplication Server Network Deployment for use by Tivoli Asset Management forIT.

You need to complete the manual configuration of WebSphere Application ServerNetwork Deployment before you use the Tivoli Asset Management for ITinstallation program if, in the case of WebSphere Application Server NetworkDeployment, you choose to not have the Tivoli Asset Management for ITinstallation program automatically configure it.

Manually configuring JMS queuesThis procedure provides details on steps to configure JMS queues, which must becompleted before deploying Tivoli Asset Management for IT EAR files.

Before you begin

During the installation process, the IBM Tivoli Asset Management for ITinstallation program provided you with the option of automatically configuring themiddleware. If you elected to have the Tivoli Asset Management for IT installationprogram automatically configure middleware, then it does, among other tasks,create, and configure JMS message queues for you. If you elected to manuallyconfigure the middleware for use with Tivoli Asset Management for IT , you needto manually configure these message queues.


About this task

To configure the JMS queues, complete the following steps:

Procedure1. Start the WebSphere Application Server.2. Launch the browser and open the WebSphere Administrative Console by

typing the following URL:http://computer_name:port_number/ibm/console

For example, enter a URL like:http://local_host:9060/ibm/console

3. At the Welcome, please enter your information login screen, enter your userID, then click Log in. This action opens the Welcome screen for theWebSphere Administrative Console.

4. Start the MXServer server by navigating to Servers → Application Servers,selecting MXServer, and then clicking Start.

5. Click System → administration → Console preferences.6. Select the Synchronize changes with Nodes option, and then click Apply.7. Click Service Integration → Buses to open the Buses dialog. A bus is a group

of interconnected servers and clusters that have been added as members ofthe bus.

8. Click New to open the Buses → New dialog box where you can add a newservice integration bus.

9. Enter intjmsbus as the name of the new bus in the Name field.10. Clear the Bus security check box. If you leave this box checked, intjmsbus

inherits the Global Security setting of the cell.11. Click Next → Finish → Save. Marking Save propagates the JMS bus setup to

the cluster configuration. Confirm that build completed screen displays thefollowing:v Bus name, for example, intjmsbus.v Auto-generated, unique ID (UUID), for example, 4BCAC78E15820FED.v The Secure field is cleared.

Adding a server to the service integration bus:

A complete, step-by-step procedure of adding a server to the service integrationbus is described in this section.

About this task

Complete the following steps to add a server to the service integration bus:

Procedure

1. From the WebSphere Administrative Console, click Service Integration →Buses to open the Buses dialog box.

2. Click intjmsbus to open the Buses → intjmsbus dialog box.3. Under Topology, click Bus members.4. In the Buses → intjmsbus → Bus members dialog box, click Add to open the

Add a new bus member dialog box.


5. Click the Server drop-down arrow, and select the server namectgNode01:MXServer to add to the bus, and then click Next.

6. Check that the File store radio button is selected, and then click Next.7. From the Provide the message store properties panel, click Next.8. Click Finish → Save → OK, and then select intjmsbus.9. Change the value of the High Message Threshold field to a minimum value

of 500,000 messages, and then click Apply.If the number of messages awaiting processing exceeds the High MessageThreshold you set, the application server will take action to limit the additionof new messages in the processing queues.Depending on your message requirements, you might want to enter a highermessage threshold value. You can determine an optimal message thresholdsetting by monitoring the messaging in/out queues and the impact of themessage threshold setting on system performance. You might, for example,lower the threshold value if a higher value is degrading system performance.If you decide to change the High Message Threshold setting after the initialconfiguration, you need to open the Additional Properties menu in WebSphereAdministrative Console and change the threshold value for each childconfiguration.

10. Click Save, and then OK.

Creating the service integration bus destination for the continuous inbound(CQINBD) queue:

The procedure in this section describes how to add a logical address for thecontinuous inbound bus destination queue.

About this task

To add a logical address for the continuous inbound bus destination queue(CQINBD) within the JMS bus, complete the following steps:

Procedure


2. Click intjmsbus to open the intjmsbus dialog box.3. Click Destinations under Destination resources to open the Buses →

intjmsbus → Destinations dialog box.A bus destination, for example CQINBD, is a virtual place within a serviceintegration bus where applications can attach and exchange messages.

4. Click New to open the Create new destination dialog box.5. Leave Queue checked as the destination type, and click Next to open the

Create new queue dialog box.6. Type CQINBD in the Identifier field and Continuous Queue Inbound in the

Description field, then click Next to open the Create a new queue forpoint-to-point messaging dialog box.

Note: You need to use this value and it must contain only uppercase letters.7. Select the Bus Member pull-down and choose

Node=ctgNode01:Server=MXServer as the bus member that will store andprocess messages for the CQINBD bus destination queue.

8. Click Next to open the Confirm queue creation dialog box.


9. Review your selections, then click Finish to complete the creation of theCQINBD bus destination queue.

10. Navigate to Buses → intjmsbus → Destinations, then click CQINBD to openthe configuration dialog box where you need to make the following changes:

11. Click None as the Exception destination value.12. Click Apply → Save to complete the task.

Creating the service integration bus destination for the sequential inbound(SQINBD) queue:

To add a logical address for the sequential inbound bus destination queue (SQINBD)within the service integration bus, complete the steps in the section.

Procedure


2. Click intjmsbus to open the Buses → intjmsbus dialog box.3. Click Destinations under Destination resources to open the Buses →

intjmsbus → Destinations dialog box. A bus destination is a virtual placewithin a service integration bus where applications can attach and exchangemessages.


Create new queue dialog box.6. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the

Description field, then click Next to open the Create a queue forpoint-to-point messaging dialog box.


Node=ctgNode01:Server=MXServer.8. Click Next to open the Confirm queue creation dialog box.9. Review your selections, then click Finish to complete the creation of the

SQINBD bus destination queue.10. Navigate the path Buses → intjmsbus → Destinations, then click SQINBD to

open the configuration dialog box where you need to make the followingchanges:

11. Click None as the Exception destination value.12. Click Apply.13. Click Save.

Creating the service integration bus destination for the sequential outbound(SQOUTBD) queue:

This section describes the procedure how to add a logical address for thesequential outbound bus destination queue (SQOUTBD) within the service integrationbus.

About this task

To add a logical address for the sequential outbound bus destination queue(SQOUTBD) within the service integration bus, complete the following steps:


Procedure



intjmsbus → Destinations dialog box. A bus destination, for example SQOUTBD,is a virtual place within a service integration bus where applications canattach and exchange messages.


Create new queue dialog box.6. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the


Note: The value you type in must contain only uppercase letters.7. Select the Bus Member pull-down and choose

Node=ctgNode01:Server=MXServer as the bus member that will store andprocess messages for the SQOUTBD bus destination queue.

8. Click Next to open the Confirm queue creation dialog box.9. Review your selections, then click Finish to complete the creation of the

sqinbd queue.10. Navigate to the Buses → intjmsbus → Destinations, then click SQOUTBD to

open the configuration dialog box where you need to make the followingchanges:

11. Click None as the Exception destination value.12. Click Apply, and then Save.

Creating the JMS connection factory:

You add a connection factory for creating connections to the associated JMSprovider of point-to-point messaging queues.

About this task

To add a connection factory for creating connections to the associated JMSprovider, perform the following:

Procedure

1. From the WebSphere Administrative Console, click Resources → JMS →Connection factories.

2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply.3. Click New.4. Verify that the Default Messaging Provider is selected, and click OK.5. Enter the following information, and then click OK:

Name Enter intjmsconfact.

JNDI nameEnter jms/maximo/int/cf/intcf.

Bus nameSelect intjmsbus.


6. Click Apply.7. Click Save.8. Click OK.

Creating the continuous inbound (CQIN) JMS queue:

You need to create a JMS queue (CQIN) as the destination for continuous inboundpoint-to-point messages.

About this task

To create a JMS queue (CQIN), perform the following steps:

Procedure

1. From WebSphere Administrative Console, click Resources → JMS → Queues.2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply.3. Click New.4. Verify that the Default Messaging Provider is selected and click OK.5. Enter the following information, and click OK.

Name Enter CQIN.

Note this value must only contain uppercase letters.

JNDI nameEnter jms/maximo/int/queues/cqin


Queue nameSelect CQINBD.

6. Click OK, and then Save.

Creating the sequential inbound (SQIN) JMS queue:

You need to create a JMS queue (SQIN) as the destination for sequential inboundpoint-to-point messages.

About this task

To create a JMS queue, perform the following procedure:

Procedure

1. From the WebSphere Administrative Console, click Resources → JMS → Queues.2. From the Scope drop-down list, select Cell=ctgCell01, and click New.3. Verify that the Default Messaging Provider is selected and click OK.4. Enter the following information, and click OK.

Name Enter SQIN.

Note this value must only contain uppercase letters.

JNDI nameEnter jms/maximo/int/queues/sqin



Queue nameSelect SQINBD.


Creating the sequential outbound (SQOUT) JMS queue:

You need to create a JMS queue (SQOUT) as the destination for sequentialoutbound point-to-point messages.

About this task

To create a SQOUT JMS queue, perform the following steps:

Procedure

1. From the WebSphere Administrative Console, click Resources → JMS → Queues.2. From the Scope drop-down list, select Cell=ctgCell01. Click New.3. Verify that the Default Messaging Provider is selected and click OK.

Name Enter SQOUT.

Note: This value must only contain uppercase letters.

JNDI nameEnter jms/maximo/int/queues/sqout


Queue nameSelect sqoutbd.

4. Enter the following information, and click OK, and then Save.

Creating JMS activation specification for the continuous inbound queue(CQIN):

You need to activate the continuous inbound queue (CQIN) before it can receivemessages.

About this task

Complete the following steps to activate the CQIN queue:

Procedure

1. From the WebSphere Administrative Console, click Resources → JMS →Activation Specifications .

2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply.3. Click New to complete the General Properties section for the new JMS

activation specification.4. Click OK.5. Enter the following information, and then click OK:

Name intjmsact

This value is case-sensitive. This value must be lowercase.

JNDI nameintjmsact


Destination typeQueue

Destination JNDI namejms/maximo/int/queues/cqin

Bus nameintjmsbus

Maximum concurrent endpoints10


Error queues:

You can create an optional error queue that will receive redirected messages fromthe continuous queue (cqin) when the messages go in error.

Creating the service integration bus destination for the inbound error queue(CQINERRBD):

This section describes a step-by-step procedure how to add a logical address forthe inbound error queue (CQINERRBD) queue within the JMS bus.

About this task

To add a logical address for the inbound error queue (CQINERRBD) within the JMSbus, complete the following steps:

Procedure



intjmsbus → Destinations dialog box.A bus destination is a virtual place within a service integration bus whereapplications can attach and exchange messages.


Create new queue dialog box.6. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the



Node=ctgNode01:Server=MXServer.8. Click Next to open the Confirm queue creation dialog box.9. Review your selections, then click Finish to complete the creation of the

CQINERRBD bus destination queue.10. Navigate to the Buses → intjmsbus → Destinations, then click CQINERRBD to

open the configuration dialog box where you need to make the followingchanges:a. Click Specify and enter CQINERRBD as the exception destination value.


b. Change the Maximum failed deliveries value to 5. This is the maximumnumber of times you want the system to process a failed messagingattempt before forwarding the message to the exception destination.

11. Click Apply, and then Save.12. From WebSphere Administrative Console, click Service Integration → Buses to

open the Buses dialog box.13. Click intjmsbus to open the Buses → intjmsbus dialog box.14. Click Destinations under Destination resources to open the Buses → intjmsbus

→ Destinations dialog box.15. Select CQINBD.16. Specify CQINERRBD as the exception destination. . Set the Maximum failed

deliveries value to 5.17. Click OK, and then Save.

Creating the error (CQINERR) JMS queue:

After creating the Error Queue Bus Destination, you create the error queue.

About this task

To create an error queue:

Procedure

1. From the WebSphere Administrative Console, click Resources → JMS → Queues.2. From the Scope drop-down list, select Cell=ctgCell01, and then click New.3. Verify that the Default Messaging Provider is selected and click OK.4. Enter the following information, and click OK.

Name Enter CQINERR.

Note: This value must only contain uppercase letters.

JNDI nameEnter jms/maximo/int/queues/cqinerr


Queue nameSelect CQINERR.


What to do next

For a complete message queue configuration information, see Message queueconfiguration in the Integrating IT asset management data section in this informationcenter.

Creating JMS activation specification for the inbound error queue (CQINERR):

You need to activate the inbound queue (CQINERR) before it can receive messages.Follow the procedure described in this section to do so.


About this task

Complete the following steps to activate the CQINERR queue:

Procedure

1. From the WebSphere Administrative Console, click Resources → JMS →Activation Specifications.

2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply.3. Click New to complete the General Properties section for the new JMS

activation specification.4. Click OK.5. Enter the following information, and click OK:

Name Enter intjmsacterr.

This value must only contain lowercase letters.

JNDI nameEnter intjmsacterr.

This value must be the same as the one used for the Name field.

Destination typeEnter Queue.

Destination JNDI namejms/maximo/int/queues/cqinerr.

Bus nameintjmsbus

Maximum concurrent endpoints10

6. Click OK, and then Save.7. Ensure you stop all IBM-related processes and daemons.8. You need to now restart these processes for the update to take effect.9. Start the bus member for the ctgNode MXServer intjmsbus if it is not started. If

you cannot start ctgNode MXServer intjmsbus, restart MXServer under Servers→ Application servers.

Manually creating a data source for the persistent store:

If you chose to manually configure IBM WebSphere Application Server, you needto create a data source in order to store JMS messages in a IBM DB2 database.

About this task

You have the option of having WebSphere Application Server use a DB2 databaseto store JMS messages. For more information about WebSphere Application Servermessage storage, including the usage of products other than DB2, refer to

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/welcome_nd.html

and

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc/tasks/tjm0035_.html






To create a data source for the persistence store, complete the following steps:

Procedure

1. Create a system user and password on the computer hosting the databaseserver.For example, mxsibusr/mxsibusr.

2. Create and configure the database:a. Open DB2 Control Center.b. Navigate down to the Databases folder listed under your system.c. Right-click the Databases folder and select Create Database → Standard.d. Create a database named maxsibdb using default settings.e. Once the database has been created, expand the maxsibdb database and

select User and Group objects.f. Right-click DB Users and select Add.g. Select mxsibusr from the User drop-down list.h. Grant all authorities to the mxsibusr except for Security administrator

authority. Click Apply.i. Verify that you can connect to the database using the mxsibusr user by

right-clicking maxsibdb and selecting Connect.3. Configure J2C authentication data and JDBC provider in WebSphere

Application Server:a. Open and login to the WebSphere Administrative Console.b. Navigate to Security → Secure administration, applications, and

infrastructure.c. Under the Authentication header, click Java Authentication and

Authorization Service → J2C authentication data, and then click New.d. Complete the following fields in the User identity form:

Alias maxJaasAlias

User IDmxsibusr

PasswordPassword you created for mxsibusr.

DescriptionSIB database user alias.

e. Click Apply, and then click Save.f. Click Scope and then select Cell=ctgCell01.g. From the WebSphere Administrative Console navigation pane, navigate to

Resources → JDBC → JDBC Providers, and then click New.h. Specify the following values, and then click Apply:

Database typeDB2

Provider typeDB2 JDBC Driver Provider

Implementation typeXA data source

Name maxJdbcProvider


i. Click Next.j. Fill in the WebSphere Application Server variable: ${db2_jdbc_driver_path}

field with a value of was_install_dir\ctgMX\lib. For example, C:\ProgramFiles\IBM\WebSphere\AppServer\ctgMX\lib.

k. Click Next, Finish, and then Save.4. Open a command prompt and copy db2_install_dir/java/db2jcc.jar and

db2_install_dir/java/db2jcc_license_cu.jar to the was_install_dir\ctgMX\lib directory.Go back to Resources → JDBC → JDBC Providers → maxJdbcProvider, andcorrect the Class path if required for both db2jcc.jar anddb2jcc_license_cu.jar.Ensure that each jar file has the full path from ${db2_jdbc_driver_path}.

5. Configure WebSphere Application Server:a. From the WebSphere Administrative Console, navigate to Resources →

JDBC → Data sources.b. Click Scope and then select Cell=ctgCell01.c. Click New.d. Specify the following values:

Data source nameintjmsds

JNDI namejdbc/intjmsds

e. From the Component-managed authentication alias and XA recoveryauthentication alias drop-down list, select maxJaasAlias.

f. Click Next.g. Choose Select an existing JDBC provider, and then select maxJdbcProvider

from the drop-down list.h. Click Next.i. Specify the following values:

Database namemaxsibdb

Driver type4

Server nameSpecify the DB2 server host name.

Port numberSpecify the DB2 port number. For example, 50005.

j. Ensure the Use this data source in container managed persistence (CMP)option is enabled, and then click Next.

k. Click Finish, and then click Save.6. Verify the data source by selecting intjmsds, and then clicking Test

Connection.


Related information

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.websphere.wps.z.620.doc/doc/rins_zos_sib_lose_lock.html

Performing post installation tasks for the application serverDuring the installation process, the Tivoli Asset Management for IT installationprogram provided you with the option of automatically configuring themiddleware. Use this procedure to perform post installation steps for theapplication server.

About this taskv If you elected to have the Tivoli Asset Management for IT installer automatically

configure the middleware, then it, among other tasks, performs the applicationserver configuration for you.

v If you elected to manually configure middleware, manually configure theapplication server.

Procedure1. Invoke a browser window and open the administrative console by typing in the

browser address bar: http://computer_name:9060/admin. This URL addressdepicts the default port number (9060) and context (admin) for theadministrative console. Enter a user name to log in.

Note: The browser is redirected to a secure port (9043).2. Create the MXServer application server. This step is only necessary if you did

not install WebSphere Application Server using the middleware installer.a. Expand the Servers link and click Application servers.b. Click New.c. Type MXServer and click Next.d. Accept all default settings and click Next.e. Accept default settings and click Next.f. Click Finish.g. Click Preferences.h. Check the Synchronize changes with Nodes check box, and then click

Apply.i. Click Save.j. Click OK.

3. Edit JVM Memory Settings for the application server:a. From the Servers link in the navigation tree, click Application servers.b. Click MXServer in the main window.c. From the Server Infrastructure group, expand the Java and Process

Management link.d. Click Process Definition.e. Click Java Virtual Machine.f. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum

Heap Size and click OK.g. Click Save in the messages box.

4. Edit JVM Memory Settings for the deployment manager:




a. From the System administration link in the navigation tree, clickDeployment manager.

b. From the Server Infrastructure group, expand the Java and ProcessManagement link.

c. Click Process Definition.d. Click Java Virtual Machine.e. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum

Heap Size and click OK.f. Click Save in the messages box.

5. Start the application server:a. From the Servers link in the navigation tree, click Application servers.b. Select the check box beside MXServer.c. Click Start.

6. Identify the HTTP Transfer port numbers:a. Expand Servers → Application servers, and click MXServer from the main

window.b. Open the Web Container Settings and click Web container transport chains.

Note the default port number as it appears with WC_defaulthost (9080).c. Click Save.

7. Create the virtual host:a. Expand the Environment link from the navigation tree.b. Click Virtual Hosts.c. Click New.d. In the General Properties section, type maximo_host in the Name box.e. Click Apply.f. Click Save.g. From the Virtual Hosts window, click maximo_host.h. Click the Host Aliases link.i. Click New.j. Type * (asterisk) for host name and type the HTTP port number (by default

80).k. Click OK.l. Click New.m. Type * (asterisk) for host name and type 9061 for the port number.n. Click OK.o. Click New.p. Type * (asterisk) for host name and type 9443 for the port number.q. Click OK.r. Click New.s. Type * (asterisk) for host name and type 9080 for the port number.t. Click OK.u. Click New.v. Type * (asterisk) for host name and type 9044 for the port number.w. Click OK.x. From the navigational breadcrumb trail, click maximo_host.y. Click Apply and then click OK.


Related concepts

Chapter 14, “Post installation tasks,” on page 253There are some post installation tasks that must be completed following asuccessful Tivoli Asset Management for IT deployment.Related reference

“Planning for port availability” on page 20Make sure that you enabled ports in support of the installation and deployment.

Installing IBM Tivoli Asset Management for IT manuallyThis procedure explains how to install IBM Tivoli Asset Management for IT andwithout choosing to have the installation program autoconfigure the Tivoli AssetManagement for IT middleware servers. You might not want have the installationprogram autoconfigure the middleware if your organization has specific policiesand procedures that govern how you create databases, database instances, users,and so on.

Before you begin


About this task

If you intend to use DB2 on UNIX systems with Tivoli Asset Management for IT,you need to add root to the DB2GRP1 group before starting the installer.


Procedure1. Log in as a user with administrative authority.2. Ensure the database server, directory server, and application server services

are running.3. Launch the installation program from the Launchpad:

a. On the DVD titled “Tivoli Asset Management for IT V7.2.2”, navigate tothe root directory of the product disc or the downloaded installationimage, and run the following command, depending on your operatingsystem.


UNIX launchpad.shb. In the launchpad navigation pane, click Install the Product.c. Click Install Tivoli Asset Management for IT V 7.2.2.0.


displayed.


6. In the Package Summary panel, review the package deployment actions, andthen click Next. This panel lists version information for both new and existing


packages on the system. Target package version information indicates thepackage version being currently deployed. In certain upgrade scenarios, aquestion mark can be displayed alongside a package listed. This symbolserves as a reminder that there might be an updated version of this packageavailable. It does not indicate a failure of the installer.

7. In the software license agreement panel, read the license information andselect I accept both the IBM and the non-IBM terms. if you agree with theterms, and then click Next.

8. In the Choose Install Folder panel, specify the directory you use to installTivoli Asset Management for IT, and then click Next. Fill the Where WouldYou Like to Install? field, providing the information about the path you wantto install Tivoli Asset Management for IT (tamit_install_dir). By default, forWindows, it is C:\IBM\SMP. The path you specify must not contain spaces.

9. In the Choose Deployment panel, select the Custom deployment topology,and then click Next.

SimpleSelect simple if you want to deploy all components on a singlesystem. This deployment option is typically only used fordemonstration, proof-of-concept, or training purposes.

CustomSelect custom if you want to deploy components across severalsystems. This recommended deployment option is typically used in aproduction environment. You choose this option to have thepossibility to provide custom configuration options at later time.


10. In the Import Middleware Configuration Information panel, specify that youwant to use field values you enter into the middleware installation programas default values for those same fields in the Tivoli Asset Management for ITinstallation program.

Import Middleware Configuration InformationSelect this check box if you want to allow the installer to reuse valuesentered in the middleware installation program.


The middleware default information is not used if you select theSimple deployment path.

Host nameEnter the host name of the system where the middleware installationprogram was run.



Workspace LocationEnter the location of the topology file that contains the values entered


for the middleware installation program (workspace_dir). This file isfound in the workspace that was defined during the middlewareinstallation task. For example, C:\ibm\tivoli\mwi\workspace forWindows and /root/ibm/tivoli/mwi/workspace for UNIX.

11. In the Maximo Database Type panel, select the product that you want to usefor the Maximo database, and then click Next.



SQL ServerSelect this choice to use Microsoft SQL Server as the Maximo database.

Each database has its own unique set of configurable parameters and values.12. From the Maximo Database panel, enter configuration information about the

database, and then click Next.

DB2


Port Enter the port being used byDB2 instance.












Oracle























After you have entered configuration information for the database that wasselected, the installation program connects to the database server to validatethe information you have entered.

13. From the Automate Database Configuration panel, select Do not automatedatabase configuration, and then click Next.

Note: This step assumes that you have already created a database instance, adatabase, table spaces, a user, and schema for use with Tivoli AssetManagement for IT. If you have not manually configured the database beforeselecting Do not automate database configuration from within the TivoliAsset Management for IT installer, the installation verifies that you have notcompleted these preinstall tasks and you are prompted to complete thembefore restarting the installation program.

14. In the Database Tablespace panel, enter information about the table space ofthe database, and then click Next.

DB2





Data tablespace sizeEnter a size, in megabytes, for the data table space.





Temporary tablespace size (Mb)Enter a size for the temporary table space. The default value is1000 Mb.



Index tablespace sizeEnter a size, in megabytes, for the index table space.

Oracle

Instance LocationEnter a path for the database instance.

WindowsOn Windows, this value might beC:\oracle\product\10.2.0\db_1\dbs

Linux On Linux or UNIX, this value might be/opt/app/oracle/product/10.2.0/db_1

Data Tablespace nameEnter the name of the table space to be created in Oracle forthe product..


Data tablespace sizeEnter a size, in megabytes, for the data table space.

Temporary tablespace nameEnter the name for the temporary table space to be created forOracle.



Temporary tablespace size (Mb)Enter a size for the temporary table space. The default value is1000 Mb.




Index tablespace sizeEnter a size, in megabytes, for the index table space.

The Tivoli Asset Management for IT installation program now connects to thedatabase server and validates the information you specified.

15. Once the database validation task has completed, in the Application ServerType panel, select WebSphere Application Server Network Deployment, andthen click Next.

16. In the WebSphere Connectivity panel, enter host information about theWebSphere Application Server Network Deployment, and then click Next.

Host nameEnter the fully qualified host name of the system hosting WebSphereApplication Server Network Deployment.


SOAP portEnter the SOAP port of the WebSphere Application Server NetworkDeployment system.

The default value for this field is 8879.17. From the Automate WebSphere configuration panel, select Do not automate

WebSphere configuration, and then click Next.

Note: Choosing not to have the installation program automatically configuremiddleware, you will have had to configure WebSphere Application Servermanually before the installation of Tivoli Asset Management for IT.Configuration tasks include creating a profile, running WebSphere ApplicationServer as a Windows service, copying the WebSphere keystore file from thecomputer where WebSphere Application Server is installed to theadministrative workstation, setting up JMS queues, and so on.

18. From the WebSphere Deployment Manager configuration panel, enter valuesfor the following fields, and then click Next.

WebSphere installation directoryEnter the directory where WebSphere Application Server is installedon the host system.

Windows WindowsOn Windows, this value might be C:\ProgramFiles\IBM\WebSphere\AppServer

Linux LinuxOn Linux, this value might be /opt/IBM/WebSphere/AppServer

AIX AIXOn AIX, this value might be /usr/IBM/WebSphere/AppServer

Solaris Sun SolarisOn Sun Solaris, this value might be /opt/IBM/WebSphere/AppServer

User IDEnter the administrative user ID used to access the WebSphereApplication Server.



PasswordEnter the password for the administrative user ID used to access theWebSphere Application Server.

Profile nameEnter the name of the WebSphere Application Server profile.

Default for all platforms is ctgDmgr01.19. From the WebSphere Application Server Configuration panel, enter the

following information, and then click Next.

Web server portEnter the Web server port used by WebSphere Application Server.


Web server nameEnter the name of the Web server.

Default for all platforms is webserver1.

Node nameEnter the name of the WebSphere Application Server node containingthe application server.

Default for all platforms is ctgNode01.


20. In the Security panel, select a method for authenticating and authorizingusers.


WebSphere application security only for authenticationChoose this option to automatically configure WebSphere ApplicationServer Network Deployment application security for authenticationonly and allow Maximo security to manage users and groups. Youcreate all your users in your directory server, but you manage theirmembership in security groups in the base services Security Groupsapplication. This option requires application security to already beenabled in WebSphere Application Server Network Deployment.


Use Maximo security for authentication and authorizationIf you do not want to use WebSphere Application Server NetworkDeploymentapplication security, select this option to have Maximosecurity manage users and groups for both authentication andauthorization.



Maximo administration userProduct administrator user ID used for initial configuration andadding users. Default value is maxadmin.

PasswordPassword for the Maximo administration user.

Maximo system registration userUser ID used for the self registration of users. Default value is maxreg.

PasswordPassword for the Maximo system registration user.

Maximo system integration userUser ID used with enterprise adapters. Default value is maxintadm.

PasswordPassword for the Maximo system integration user.











If you are not using the default LDAP schema provided with Tivoli AssetManagement for IT, you must create it yourself before advancing beyond thispanel. The values specified for User and Group base entry fields are used toconfigure the VMMSYNC cron task.Following is an example of the default add on ldif data you have to modifyand import into your LDAP repository if you chose to customize the schemaand create your own users manually.dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxadminuid: maxadminobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxadmincn: maxadmin



23. From the WebSphere keystore file panel, navigate to where you copied thetrust.p12 keystore, and then click Next.

24. In the SMTP Configuration panel, enter SMTP configuration information usedby workflows to communicate with workflow participants, and then clickNext.

SMTP serverEnter the fully qualified host name of the SMTP server that sendsmessages to participants.

Administrator e-mailEnter a valid e-mail address. This address is to send messages.


25. In the Data Integration Service and Context Menu Service DeploymentOptions panel, select a deployment option.The Data Integration Service and Context Menu Service allow products toregister themselves in order to offer launch in context to all other registeredproducts. This ability is provided without unique product-to-product


integration efforts. A single integration effort through Data Integration Serviceand Context Menu Service allows registered products to gain launch access forall other registered products.


Select this option to use the Tivoli Asset Management for IT databaseas the Data Integration Service and Context Menu Service database.




Select this option to defer the configuration of Data Integration Serviceand Context Menu Service to a later time. You must run the productinstallation program again in the future to configure this feature. Ifyou defer the deployment, proceed to the Run Configuration Steppanel.

26. In the Data Integration Service Database Information panel, enterconfiguration information about the Data Integration Service database andthen click Next.














Use the product database for the context menu service.Select this option if you want to use the Tivoli Asset Management forIT database as the Context Menu Service database.



Microsoft SQL ServerMicrosoft SQL Server is not a valid option for Tivoli AssetManagement for IT. Do not select this option








Copy files now, but perform the installation configuration step later.Select this option if you would like to copy files from the installationsource to the administrative workstation. You will have to performthe configuration step at a later time to complete the deployment. Youmight choose this option if you intend to install more than one ISMproduct and want to perform the configuration step once for all theproducts.

The configuration values that you enter are stored in thetamit_install_dir\maximo\applications\maximo\properties\maximo.properties file. You can run the configuration steps outside ofthe Tivoli Asset Management for IT installation program by using thetaskrunner utility, in the tamit_install_dir\scripts directory. Run


the taskrunner utility from the command line, and it will use theconfiguration values stored in the maximo.properties file to configureTivoli Asset Management for IT.tamit_install_dir\scripts\taskrunnerCONTINUE <STOPONERROR|NOSTOPONERROR>





29. From the Choose Shortcut Folder panel, select the type of shortcut you wouldlike to arrange for Tivoli Asset Management for IT, and then click Next.

In a new Program GroupSelect this option and enter the name of a new program group if youwant to create the product shortcuts in a new program group.

In an existing Program GroupSelect this option and choose the name of an existing program groupto store the product shortcuts.

In the Start MenuSelect this option to create shortcuts for the product in the Start menu.

In order to use the Start menu shortcut with Internet Explorer, ensurethat you have added the Tivoli Asset Management for IT URL to thetrusted sites Web content zone and disable the option of requiringserver verification for all sites in the zone.


On the DesktopSelect this option to create shortcuts for the product on the desktop.

In the Quick Launch BarDo not select this option.

Other Select this option and use the Choose... button to select anotherlocation to create Tivoli Asset Management for IT shortcuts.

Don't create iconsSelect this option if you do not want any Tivoli Asset Management forIT shortcuts created.

Create Icons for All UsersSelect this option if you would like the product desktop icons toappear on the desktop for all system users.

30. From the Input Summary panel, review the information you have provided tothe installer, and then click Next.Use the Previous button to return to previous panels to change previoussettings.

31. From the Pre-Installation Summary panel, review the installation informationpresented, and then click Install. The installation task begins. Progress can bemonitored by viewing messages displayed.


What to do next

Once the Tivoli Asset Management for IT installation program has completedinstallation and configuration tasks, it exits. Logs can be found attamit_install_dir/logs. Complete post installation tasks required fornon-automated middleware configuration installation.


Chapter 9. Verifying the installation

After you have exited the IBM Tivoli Asset Management for IT installationprogram without encountering any errors, you can further verify that theinstallation completed successfully by locating key artifacts and performing a fewsimple tasks.

Before you begin

The product installation program performs installation verification, or a healthcheck, by logging into the product before exiting the installation. The productinstallation program returns a success message if all installation steps, includingthe product log in task, are successful. If the health check task is unsuccessful, aHealthCheckFailed error thrown for the getUrlContentString function is found inthe tamit_install_dir\logs\CTGInstallTraceXX.log file, where XX is a two digitnumber such as 00.

For more information about log files and troubleshooting errors encounteredduring the installation, refer to Chapter 16, “Troubleshooting installation,” on page285. Read also about LogZipper utility in “General troubleshooting of the productdeployment” on page 285.

About this task

To further verify that the Tivoli Asset Management for IT installation wascompleted successfully, perform the following verification procedures:

Procedure1. Examine the CTGInstallTrace00.log file for success messages.

The following success messages are found in the file and can be used to verifywhich phases of the installation were successful:v CTGIN2114I: The database was created successfully

v CTGIN2135I: Tablespace maxdata created successfully

v CTGIN2135I: Tablespace maxtemp created successfully

v CTGIN2079I: Base services database configuration completedsuccessfully (This message indicates that maxinst finished successfully.)

v CTGIN2222I: WebSphere Application Server creation successful

v CTGIN2188I: Creation and configuration of service integration bussuccessfully completed

v CTGIN2184I: Creation and configuration of JMS resources successfullycompleted

v CTGIN2310I: Application server security was successfully enabled forthe base services

v CTGIN2253I: buildmaximoear.cmd completed successfully

v CTGIN2224I: Deployment of application MAXIMO was successful

v CTGIN2253I: buildhelpear.cmd completed successfully

v CTGIN2224I: Deployment of application MAXIMOHELP was successful

v CTGIN2208I: runConfigurationStep completed successfully

v CTGIN2370I: The installation finished successfully


If you chose the option of having the installation program automaticallyconfigure WebSphere Application Server Network Deployment, the followingmessages, found in the CTGInstallTrace00.log file, indicate the configurationwas successful:<symptom> CTGIN2228I.*client </symptom><symptom> CTGIN2230I.*node </symptom><symptom> CTGIN2232I.*NodeAgent </symptom><symptom> CTGIN2240I.*server </symptom><symptom> CTGIN2238I.*security </symptom>

Search the CTGInstallTrace00.log file for the following message, whichindicates that the maxinst task completed successfully:CTGIN2079I, maxinst.*completed

2. Compare the packages chosen for installation with the packages that wereinstalled. The Package Summary panel of the Tivoli Asset Management for ITinstallation program provides a summary of all the packages that will beinstalled. You can compare the contents of that panel with a listing of what wasactually installed on the system. Use the solutioninstaller command to listinstalled packages:tamit_install_dir\bin\setupPSIenv.battamit_install_dir\bin\solutionInstaller.bat -action showInstalled -all

The resulting list should match the packages listed in the Package Summarypanel.

3. Log in to the product and verify applications are present. Being able to log intothe product manually is a good indicator that the installation was successful.Once you have logged in, navigate through the “Go to” menu to verify that ithas been populated with the applications you expect.

Related tasks

“Confirming the installation” on page 244Verifying Tivoli Integration Composer installation


Chapter 10. Process solution package installation methods

Included within IBM Tivoli Asset Management for IT are common installationprograms that provide you with the ability to manage the software lifecycle ofTivoli Asset Management for IT process solutions, including functions to query,install, upgrade, and uninstall process solution packages. These commoninstallation programs are collectively referred to as the process solution installationprograms.

Tivoli Asset Management for IT provides a flexible approach for incrementaldeployment of service management functionality using separately packagedprocess solutions. Process solutions can be partitioned into Process ManagerProducts and Integration Modules.

Process solution packages can be installed and deployed using two mechanisms:

Process solution installation wizardThe process solution installation wizard provides you with a user interfacefor installing process solution packages.

Process solution command-line interfaceThe process solution command-line interface allows you to install processsolution packages from a command line.

The product must have been completely deployed, including post-installationsteps, before the installation and deployment of additional process managers.Related tasks

“Installing language packs with Process Solution Installer” on page 228The Process Solution Installer guides you through the installation of a processmanager product (PMP) or Integration Module. Use the Process Solution Installerto refresh languages to synchronize them with Maximo languages.

Software life cycle operationsProcess solutions are software components with versions assigned. The processsolution installation programs support various software life cycle operations thatmight be applied against process solutions.

The following software life cycle operations are available:

Base InstallThis operation installs and deploys a new process solution into your TivoliAsset Management for IT environment.

Add Feature and Modify FeatureThese operations allow specific features within a package to be added orremoved after the package has been installed.

Incremental Update or UpgradeOnce installed, a process solution might be updated in several ways. AnIncremental Update or Upgrade operation modifies the existing installedprocess solution and changes its version. Often a process solution fix packis applied using the Incremental Update operation.

Apply FixAnother operation that can be used to update an installed process solution


is the Apply Fix operation. This operation is used to install individualinterim fixes or patches to a currently installed process solution.

Back off, Undo, Undo FixSome incremental updates or fixes are designed to be able to be removedor backed off. The Undo operation is used to remove the effects of anIncremental Update operation and return the process solution to itsprevious version and state. The Undo Fix operation removes a currentlyinstalled interim fix from a process solution.

UninstallThe Uninstall operation removes a currently installed process solution.

Process solution packagesA process solution package is a self-contained archive file of installation artifacts anddeployment logic that can be deployed using the process solution installationprograms.

Installation artifacts are the files and content that are installed into your IBM TivoliAsset Management for IT environment to enable the services managementfunctionality of the Process Manager Product or Integration Module. For example,a Process Manager Product provides the application server content and databasecontent.

The deployment logic consists of the actions that are carried out in order to deploythe process solution into the Tivoli Asset Management for IT environment.Typically, these actions include building and deploying J2EE applications, runningdatabase scripts that load the process solution content into the database, andadding users and groups for security. Refer to “Securing WebSphereAdministrative Console” on page 319. Additionally, optional sample data can beinstalled.

Some packages are automatically installed when Tivoli Asset Management for IT isinstalled. Using Launchpads, you allow the installation program to performpackages installation for you.

Table 16. The available process solution installer archive packages

File name When used

base_services_7.1.1.7.zip This package is deployed automatically whenperforming Tivoli Asset Management for ITinstallation. It installs Maximo base services 7.1.1.7.

common_pmp_7.1.1.7.zip This package installs Maximo base services 7.1.1.7.

TAMIT_SP_7.2.2.0.zip This package contains Tivoli Asset Managementfor IT and Tivoli Asset Management for IT forService Providers extensions for use when serviceprovider is enabled on the server.

It installs the service providers software on yourcomputer.

The package is contained within the “IBM TivoliAsset Management for IT for Service Providers7.2.2” Launchpad.

ITIC_PMP_7.2.2.0.zip This package installs database entries that arerequired by IBM Tivoli Integration Composer intothe Maximo database. The package is containedwithin the “IBM Tivoli Asset Management for IT7.2.2” Launchpad.


Table 16. The available process solution installer archive packages (continued)

File name When used

Tamit_ENG_7.2.2.0.zip This package contains the Tivoli AssetManagement for IT product code.

Tamit_ID_7.2.2.0.zip The is the product enablement package. For TivoliAsset Management for IT 7.2.2, it is installed withthe Tamit_ENG_7.2.2.0.zip package.

NRS_1.0.0.0.zip This is a PSI package for installing Naming andReconciliation Services (NRS) 1.0. This file isavailable for customers who have installed aproduct that is based on Tivoli's processautomation engine version 7116 and want to installTivoli Asset Management for IT version 7.2.2 butdo not want to upgrade to the process automationengine level included in the Tivoli AssetManagement for IT installation program.

Related concepts

“Supported operations for the process solution installation programs” on page 198There are multiple operations and functions that are supported by the processsolution installation wizard and process solution command-line interface.Related tasks

Enabling Service ProviderTivoli Asset Management for IT for Service Providers is an optional, separatelylicensed component that adds functionality to existing applications. The addedfeatures enable service providers to manage the data centers of multiple customers.Strict customer segmentation ensures that the data, IT assets, and process recordsare maintained securely and separately, by customer. Follow these procedures toenable service provider.Installing Tivoli Integration Composer

Windows UNIX For IBM Tivoli Asset Management for IT installations, therecommended way to install IBM Tivoli Integration Composer is from theLaunchpad. Use the Launchpad to install Tivoli Integration Composer on Windowsor UNIX operating systems.“Installing language packs with Process Solution Installer” on page 228The Process Solution Installer guides you through the installation of a processmanager product (PMP) or Integration Module. Use the Process Solution Installerto refresh languages to synchronize them with Maximo languages.Related reference


Package typesClosely related to the concept of the software life cycle operation is softwarepackage type.

Chapter 10. Process solution package installation methods 195

The process solution installation programs are able to process the followingpackage types:

Base Install PackageIt is required to install a new process solution using the Base Installoperation.

Incremental Update PackageIt is required when performing an Upgrade operation.

Fix PackageIt is required when applying an interim fix to a process solution.

Full Update PackageIt can be used in two separate operations. It might be used to perform aBase Install operation if no instance of the process solution is currentlyinstalled or it might be used to perform an Upgrade operation on acurrently installed process solution.

Aggregation packageIt consists of multiple process solution installable packages that can bedeployed as one package in a single process solution installation clientcommand-line interface or user interface session.

The process solution installation programs ensure that the appropriate packagetype is processed for any given operation.

The process solution command-line interface issues appropriate messages when aninappropriate package type is specified for a life cycle operation. For example, amessage is issued if a Fix Package was specified for a Base Install operation. Youcan use the showavail action of the process solution command-line interface todetermine the package type associated with a process solution installable package.

The process solution installation wizard determines the operation to employ basedon the type of the package and the current state of the installed components. Forexample, if you select to deploy a Full Update Package, the process solutioninstallation wizard performs an Upgrade operation if a suitable base version of theprocess solution is already installed and a Base Install operation if no suitable baseversion is detected. When using the process solution installation wizard, you canview the package type for the package you selected on the Package ValidationResults panel.

The following table highlights the supported operations with their requiredpackage types:

Table 17. Operations and package types

Operation Package type

Base Install Base Install Package or Full Update Package

Incremental Update/Fix Pack Incremental Update Package or Full UpdatePackage

Apply Interim Fix Fix Package


Aggregation packagesA process solution package might be composed from other process solutionpackages. This technique allows construction of single offering-level packages thatmight be deployed using a single session with the process solution installationprograms. Such a package is referred to as a process solution aggregate package.The sub packages that are bundled within a process solution aggregate package arereferred to as child packages.

Process solution aggregate packages are deployed using the same mechanismsused to deploy non-aggregate packages. All actions defined within the processsolution command-line interface might be applied to a process solution aggregatepackage. Similarly, the process solution installation wizard can be used to baseinstall, upgrade, and apply fixes to a process solution aggregate package.

Process solution aggregate packages support the same package types (Base Install,Full Update, Incremental Update, and Fix) and the same life cycle operations asnon-aggregate packages.

Process solution aggregate packages often expose their child packages as selectablefeatures of the aggregate. It permits you to selectively deploy only the pieces of theaggregate that you prefer.

A process solution aggregate has a version, unique identifier, and display nameinformation just like a non-aggregate package. When you use the showinstalledaction of the process solution command-line interface, the output includesinformation about the installed parent aggregate package and any of the childpackages within that parent aggregate package that have also been installed.

Determining which process solution installation program to useThe process solution installation program programs provided each have uniquebenefits and both should be used in the appropriate scenario.

About this task

Consider the following facts when deciding which process solution installationprogram to use.

Procedurev The process solution installation program wizard provides a user experience

typical of most software installation programs. You select the process solutionpackage to install and provide additional installation options from wizardpanels. Process Solution Installer performs an attended installation.

v The process solution command-line interface provides a simple command-linesyntax for specifying the life cycle operation to perform and the package againstwhich the operation is performed. You enter a command and messages andcommand output are displayed to the command line as the command isprocessed.

v All functions and operations are available in the process solution command-lineinterface program. Only a subset of those functions is supported in the processsolution installation program wizard. Generally, you use the wizard if itsupports the operation you need to perform.

v The process solution installation program command-line interface is usefulwhere you require an unattended or silent installation. The command-line


interface passes return codes detailing the success of the command back to theoperating system. It makes the command-line interface suitable for use in ahigher-level deployment automation package or script.

Related concepts

“Process solution installation client command-line interface” on page 211The process solution installation client command-line interface enables you toquery, install, upgrade, and uninstall process solution packages, which can consistof process modules and integration modules.Related tasks

“Installing process managers using the process solution installation wizard” onpage 209To install a process solution package into your IBM Tivoli Asset Management forIT instance, you might use the Process Solution Installer wizard.Related reference

“Process solution installation logs” on page 292If you experience any problems or encounter any error messages during the use ofthe process solution installation program, refer to these log files.

Supported operations for the process solution installation programsThere are multiple operations and functions that are supported by the processsolution installation wizard and process solution command-line interface.

The following table highlights the operations and functions that are supported bythe process solution installation wizard and process solution command-lineinterface.

Table 18. Process solution operations

Operation

Supported bycommand-lineinterface Supported by the wizard

List Installed Packages Yes No

List Available Packages Yes No

Base Install Yes Yes

Incremental Update/Fix Pack Yes Yes

Full Update Yes Yes

Undo Incremental Update/FixPack

Yes No

Uninstall Yes No

Apply Interim Fix Yes Yes

Undo Interim Fix Yes No

List Installed Fixes for a Package Yes No

Refresh Language Support Yes No

Load Language Support Files Yes Yes

Add Features Yes Yes

Remove Features Yes Yes

Show Available Features Yes Yes

Note: The process solution installation programs allow an uninstall action to beinitiated against a package. However, not all packages support the uninstall action.If an uninstall action is initiated against a package that does not support thisaction, a message detailing this condition is displayed. If you want to restore your


environment to the state before the installation of the Tivoli Asset Management forIT process managers, you need to back up your affected middleware serversbefore running the Tivoli Asset Management for IT installation program.Related reference

“Perform action” on page 212The process solution installation program uses an action parameter wheninterfacing with packages.

Before using the process solution installation programsWhen you perform a deployment operation using the process solution installationprograms, you are running actions that modify the configuration and content ofyour application server, database, and directory middleware servers. Review theinformation included, before invoking the process solution installation programs.

Before you begin

Make sure that you:

Have middleware login information availableThe process solution installation programs require access to middlewareservers in order to automate the deployment of the process solutionpackage. You need to know the administrative user IDs and passwords forthe impacted middleware servers. The actual middleware servers whoselogin information is required depend on the process solution packagebeing installed. The process solution installation programs ensure that anyrequired login information is specified before continuing with thedeployment operation.

Back up middleware servers and administrative workstationCreate backups for impacted application server, database, and directoryservers before you deploy a process solution package using the processsolution installation programs.

Ensure that middleware servers are startedStart any impacted middleware servers before running the process solutioninstallation programs. Before the actions associated with a package areexecuted, the process solution installation programs attempt to connect tothe middleware servers using the middleware login information that youspecify. If the targeted middleware servers are not started or if connectionsto the middleware servers cannot be established with the specifiedmiddleware login information, then the process solution installationprograms display error messages and do not continue on with thedeployment actions.

Managing process solution deployment from the administrativeworkstation

Process solution deployment is managed from the Tivoli Asset Management for ITadministrative workstation.

Process solution installation programs are installed on the Tivoli AssetManagement for IT administrative workstation (refer to Figure 1 on page 2), whenthe Tivoli Asset Management for IT is installed. In addition to invoking processsolution installation programs from the Tivoli Asset Management for IT


administrative workstation, you need to also have access to any process solutionpackages from the Tivoli Asset Management for IT administrative workstation.

The Tivoli Asset Management for IT administrative workstation provides adeployment hub from which the process solution packages are deployed. In orderto automate deployment, the process solution installation programs connect toeither local or remote middleware servers from the administrative workstation.Related concepts

“Administrative workstation” on page 9You install IBM Tivoli Asset Management for IT from a workstation designated asthe administrative workstation. This workstation is where the Tivoli AssetManagement for IT EAR files are built and deployed to the application server.

Typical deployment operationProcess solutions use the IBM Tivoli Asset Management for IT deployment model.In this model, as process solution packages are deployed, database content andmetadata in the package is loaded into the Maximo database and the Maximo coreJ2EE applications are redeployed with Java code provided in the process solutionpackage. It effectively merges the functionality of the process solution package intothe Maximo database and Maximo J2EE application.

High-level deployment steps are:1. Files in the process solution package are unpacked onto the Maximo

installation directory (Tivoli Asset Management for IT, tamit_install_dir) onthe administrative workstation. The directory contains the Maximo content forthe process solution being deployed as well as any other currently installedTivoli Asset Management for IT process solutions or Maximo applications andindustry solutions.

2. J2EE applications are rebuilt on the product administrative workstation tocontain the functionality of the process solution package. This functionalityincludes Java classes, report definitions, and other artifacts.

3. The process solution installation programs deploy the update applications tothe application server. This server can be local or remote to the Tivoli AssetManagement for IT administrative workstation.

4. Database content scripts associated with the package being installed areprocessed on the Tivoli Asset Management for IT administrative workstation.This results in updates to the database.

Important: When you deploy process solution packages, the updates are made tothe application and database servers, which include redeploying the Tivoli AssetManagement for IT application. Deployment is scheduled for a time when a briefinterruption of service can be tolerated, such as during a scheduled maintenanceperiod.


Related concepts

“Administrative workstation” on page 9You install IBM Tivoli Asset Management for IT from a workstation designated asthe administrative workstation. This workstation is where the Tivoli AssetManagement for IT EAR files are built and deployed to the application server.“Managing process solution deployment from the administrative workstation” onpage 199Process solution deployment is managed from the Tivoli Asset Management for ITadministrative workstation.

Selectable featuresA process solution package might define one or more features that representuser-selectable, optional content. Examples of typical features include globalizationand samples. Process solution installation methods support operations on features,including capabilities for querying, adding, and removing features.

Feature support in a process solution package is optional. Features are alsopackage-specific. The process solution installation methods examine the processsolution install package and ensure that only features defined within the packageare able to be manipulated.

Attributes of a feature

Associated with every feature are the following attributes:v Feature Identifier represents a non-localized name by which the feature is

uniquely identified within its package. When using the process solutioncommand-line interface, the Feature Identifier is used to specify the feature toadd or remove.

v Feature Display Name is a localized label for the feature.v Parent Identifier identifies the parent feature associated with a feature. A feature

with no parent is termed a top-level feature.v Install State indicates whether the feature is installed.v Required Attribute indicates whether the feature is a required feature. A

required feature is a feature that must be installed if its parent feature isinstalled and might not be installed if its parent feature is not installed. Atop-level feature that is required is always installed.

Operations associated with features

Both the process solution command-line interface and process solution installationwizard provide functionality for managing features associated with a processinstall package. This section describes those capabilities.

Installing features during a Base InstallIf a process solution package defines features, you can select the features toinstallation during the base installation of the package.

Installing features using the wizardFor the process solution installation wizard, a Feature Selectionpanel is displayed after license acceptance processing if thepackage being deployed supports features. The Feature Selectionpanel displays a tree where the nodes in the tree are features andthe tree nesting represents parent feature and child featurerelationships. Each node has a check box that indicates the


selection state of the feature. You select a feature to be installed byselecting the check box for the feature.

Installing features using the command-line interfaceFor the process solution command-line interface, the -addfeatlistparameter on the install action allows you to specify the featuresto be installed during the base installation of the package. Thevalue specified for this parameter is a colon separated list ofFeature Identifiers representing the features to install.

Adding featuresAfter the base installation of a package, you can incrementally add featuresif there exists at least one feature not already installed for that package.

Adding features using the wizardWhen using the process solution installation wizard, if the packageis already installed but has at least one feature not alreadyinstalled, you can elect to install additional features after thePackage Validation panel is displayed.

Note that the Deployment Engine does not support bothincremental feature add and removal in the same deploymentoperation. If the state of the installed features on a package is suchthat features can be both added or removed, then the Add orRemove Features panel is displayed that allows you to selectwhether you want to add or remove features from the package.

If you select to install additional features from the Add or RemoveFeatures panel, the Feature Selection panel is again displayed withthe currently installed features checked and disabled. You can notuninstall currently installed features in this mode, but you canselect additional features for installation.

Adding features using command-line interfaceFor the process solution command-line interface, a newmodfeatures action allows you to install features to an alreadyinstalled process solution package. The parameters on this actionare like the install action. You specify the path of the processsolution package and required middleware user IDs andpasswords. The -addfeatlist parameter on the modfeatures actionallows you to specify the features to be added. The value specifiedfor this parameter is a colon separated list of Feature Identifiersrepresenting the features to be installed.

Removing featuresAfter the base installation of a package, you can incrementally remove oruninstall features if there exists at least one feature already installed forthat package.

Feature Uninstall is optionalSupport for uninstall of features is optional. A process solutionpackage that supports incremental feature installation might notsupport uninstall of its features. If the process solution packagedoes not support uninstall of its features, then the process solutioninstallation programs do not permit you to uninstall features onthe package. The wizard does not allow you to initiate featureuninstall operations against the package. The process solutioncommand-line interface issues messages if uninstall operations areattempted against a package that does not support featureuninstall.


Removing features using the wizardWhen using the process solution installation wizard, if the packageis already installed and has at least one feature already installed,you can elect to uninstall features after the Package Validationpanel is displayed.

If the state of the installed features on a package is such thatfeatures can be both added or removed, then the Add or RemoveFeatures panel is displayed that allows you to select whether youwant to add or remove features from the package.

If you select to uninstall currently installed features from the Addor Remove Features panel, the Feature Selection panel is againdisplayed with the currently installed features checked. You mightnot install new features in this mode, but you might clear currentlyinstalled features to trigger the uninstall operation against thosefeatures.

Removing features using command-line interfaceFor the process solution command-line interface, the modfeaturesaction also allows you to uninstall features that are alreadyinstalled on a currently installed process solution package. The-delfeatlist parameter on the modfeatures action allows you tospecify the features to be uninstalled. The value specified for thisparameter is a colon separated list of Feature Identifiersrepresenting the features to be uninstalled.

Showing feature information for a packageThe process solution installation programs allow you to displayinformation about the supported and installed features for a processsolution package.

Showing feature information using the wizardThe Feature Selection panel of the process solution installationwizard displays the feature tree of a process solution package. Thispanel depicts the parent-child relationships between the featuresand also displays whether the features are currently installed.

Showing feature information using the command-line interfaceFor the process solution command-line interface, the showfeaturesaction allows you to display information about the featuresassociated with a process solution package. Input to the action isthe path to the process solution package. The output lists thefeature attributes for the features defined for the package.

Feature selection processing rules and behavior

When using the process solution installation programs to manage the features, theactual collection of features to install or uninstall are derived using a combinationof the input selections/deselections you specify and a set of feature selectionsrules. For example, you might select a single feature for installation, but, due tofeature selection rule processing, additional features can also be installed.

When you install or uninstall features, the process solution installation programsenforce these feature selection rules to ensure that the derived set of featureselections are valid and meet all the feature selection rules.

This section highlights the feature selection rules that are enforced by the processsolution installation programs.


Summary of feature selection rules

1. Features can be arranged in a Parent-Child tree structure. Child featurescannot be installed unless their parent feature is installed.

2. A feature can be marked as required which indicates that the featuremust be installed if its parent is installed. A top-level feature that ismarked required is always installed.

3. Features that are marked required can never be selected/deselectedexplicitly by you. The selection state of a required feature is alwaysderived from the selection state of their parent feature.

4. A feature can have real content (files/actions) or can be a nestingfeature which acts as a parent feature for other child features.

5. A Nesting Feature might not be installed unless at least one of its childfeatures (with content) is also installed. This violation is detectedduring Feature Selection Validation. Message CTGIN0200E is issuedwhen this rule is violated.

6. Special select-if-selected rules can be coded into the package to assertprerequisite dependencies between features. They are specific to aparticular package. For example, select-if-selected rules can be definedin a package that ensures that Feature �A� is installed if Features �B� or�C� are installed.

Feature selection processing

1. When a child feature is selected, all its ancestor features (Parent,Grandparent, and so on) are selected as well.

2. When a parent feature is selected, any of its required child features areautomatically selected.

3. When a feature is selected, that select-if-selected of feature rules areevaluated and any dependent features are automatically selected.

4. The rules are applied against all features in the tree until there are nomore features to select.

Feature deselection processing

1. When a parent feature is cleared, all its descendant features (Childfeatures, Grandchild features, and so on) are cleared as well.

2. When a feature is cleared, all select-if-selected rules targeting thatfeature are evaluated and any dependent features are cleared.

3. The rules are applied against all features in the tree until there are nomore features to clear.

Feature selection validationThe process solution installation programs enforce feature selection rulesby performing a feature selection validation process. It is the process ofderiving the complete set of features that are to be processed anddetermining if the user input violates any rules. If any feature ruleviolations are detected, then the operation to install or uninstall features isnot carried out by the process solution installation programs.

Feature validation using the wizardWhen you use the process solution installation wizard, most rulesare dynamically enforced as selections/deselections are madeagainst the feature tree on the Feature Selection panel. Forexample, when you select a child feature, all of its ancestor featuresare automatically selected.


Additional rules are validated when you have finished makingyour selections and attempt to move to the next panel. If anyviolations of the rules are detected, messages describing theviolations are displayed on the Feature Selection panel and youneed to correct your input before proceeding.

Feature validation using command-line interfaceFor the process solution command-line interface, the same featureselection rules are enforced and the complete set of features toinstall or uninstall is derived using those rules.

For example, if you specify only a child feature in your -addfeatlistparameter, the process solution installation command-line interfaceadds all ancestor features to the list that are installed. Similarly, ifyou specify a parent Feature on the -delfeatlist parameter, thenany installed child features under that parent feature is also beuninstalled.

Additionally, the process solution command-line interface alsoperforms additional checks against the features you specify. Thesechecks include:1. Ensuring that any feature identifier specified is a valid

identifier for the package.2. Ensuring that features specified using the -addfeatlist

parameter are not already installed for the package.3. Ensuring that features specified using the -delfeatlist parameter

are already installed for the package.Related concepts

“Package types” on page 195Closely related to the concept of the software life cycle operation is softwarepackage type.

Application server and database-related configuration deferralThe process solution installation programs allow you to defer the automatedredeployment of the Maximo J2EE applications and the automated update of theMaximo database with content from the process solution package being deployed.

There are several reasons for why you might want to elect to skip this automation:v Your organization might have policies that prohibit remote access and update of

the J2EE application, database, or directory servers from the Tivoli AssetManagement for IT administrative workstation.

v You might not have the authority to perform administrative functions againstthe targeted middleware servers.

v Your organization might have existing procedures in place for how applicationsget deployed to middleware servers.

Using the installation wizardWhen using the process solution installation wizard, you can defer J2EEand database-related configuration steps by selecting the Defer theRegeneration and Redeployment of the Maximo J2EE Applications andthe Defer the Update of the Maximo Database check boxes on thePackage Installation Options panel.

Using the command-line interfaceWhen using the process solution command-line interface, you can defer


application server and database-related configuration steps by specifyingthe -skipj2eecfg and -skipdbcfg command-line flags.

Even if none of the scenarios apply, you might still want to defer the automaticJ2EE deployment if you are installing multiple process solution packages insequence. The regeneration and redeployment of the Maximo J2EE applications isprocessing intensive and time consuming. When deploying a series of processsolution packages, you can improve overall deployment time by only performingthe regeneration and redeployment of the Maximo J2EE applications after allprocess solutions have been unpacked to the Maximo administrative workstation.

For example, if you are installing Process Manager Products �A�, �B�, and �C� aspart of your deployment scenario, skip the regeneration/redeployment of theMaximo J2EE applications when deploying Process Manager Products �A� and �B�.When deploying Process Manager Product �C�, specify the options to perform theredeployment of the Maximo J2EE applications.

When choosing to not automate the update of the Maximo database, do not usethe process solution installation program with the -loadsampdata option, becauseyou cannot load sample data in this case.

Note: Always defer the configuration of the application server and databasetogether. Never defer one and not the other.

If you defer configuration of the application server allowing the database to beconfigured, then the Maximo database is updated with the content of the processsolution package, but the J2EE applications are not regenerated and redeployedwith the content of that process solution package. You can navigate to theapplication associated with the process solution package in the user interface. Ifyou attempt to create records with those applications, you get error messages. Theapplications contained in the installed package are then unusable until the Maximoapplications are regenerated and redeployed. Similarly, if you defer theconfiguration of the database, but allow the application server to be configured, theMaximo applications are regenerated and redeployed with the content of theprocess solution package, but the Maximo database is not updated with thecontent of that process solution package. The applications associated with theprocess solution package appear under the list of applications displayed from Help→ System in the user interface, but do not appear in the list of selectableapplications. The applications contained in the installed package are then unusableuntil the database configuration task is completed.

You rebuild and redeploy the Maximo EAR file from IBM WebSphere ApplicationServer.Related tasks

“Manually configuring the J2EE server” on page 160You need to complete the manual configuration of the J2EE server before you usethe Tivoli Asset Management for IT installation program if you choose to not havethe Tivoli Asset Management for IT installation program automatically configure it.

Manually completing deploymentThis procedure provides task information for manually deploying the processsolution package after you elected to defer J2EE and database-related configurationin the process solution installation program.


About this task

When you elect to defer automated configuration, you are responsible for manuallyinvoking the configuration operations required to complete the deployment of theprocess solution package. Until the manual configuration steps are completed, theprocess solution package is in an incomplete and unusable state.

The following procedure assumes that you have run the process solutioninstallation program and deferred the application server and databaseconfiguration during package deployment.

To manually deploy the process solution package, complete the following steps:

Procedure1. Log in to the Integrated Solutions Console, navigate to Servers → Application

Servers, and stop the MXServer server.2. Update the Maximo database:

maximo_install_dir\tools\maximo\updatedb -sl

3. Rebuild the maximo.ear and maximohelp.ear files.tamit_install_dir\deployment\buildmaximoearmaximo_install_dir\deployment\buildhelpear

4. Uninstall the MAXIMO and MAXIMOHELP applications from within WebSphereApplication Server.

5. Reinstall the MAXIMO and MAXIMOHELP applications within WebSphere ApplicationServer.

6. Restart the MXServer.Related concepts

“Application server and database-related configuration deferral” on page 205The process solution installation programs allow you to defer the automatedredeployment of the Maximo J2EE applications and the automated update of theMaximo database with content from the process solution package being deployed.

Pre-deployment system checkBefore the actions associated with a software life cycle operation are initiated, theprocess solution installation programs perform a system check activity. Associatedwith each process solution package are a set of requirements that must be satisfiedbefore the deployment operation is carried out. The system check is a process thatanalyzes the requirements to determine that all requirements have been satisfiedbefore continuing on with the deployment operation.

The actual requirements are specific to each process solution package.Requirements include disk space and memory consumption checks for the packageand dependency checks between a process solution package and other processsolution packages. When unsatisfied requirements are detected during the systemcheck, the process solution installation programs display messages that describethe failed requirements. Before trying the deployment operation again, you need toupdate your environment such that all requirements associated with the processsolution package are satisfied.

Bypassing unsatisfied requirementsUnder certain circumstances, you might find it necessary to bypass thesystem check processing and carry out a deployment operation even if oneor more requirements associated with the process solution package are not


satisfied. For example, a process solution package might have embeddedan incorrectly specified disk space check which would prohibit the packagefrom being installed on a system that has adequate free disk space requiredby the package.

Both process solution installation programs provide a mechanism thatallows you to bypass failed requirements and continue with thedeployment operation.

Using the installation wizardWhen using the process solution installation wizard, a SystemCheck Failed panel is displayed that displays messages for anyfailed requirements. From this panel, you can bypass the systemcheck failures by selecting the check box entitled Ignore SystemCheck Failures. When you select this check box, the processsolution installation wizard continues with the deployment of theprocess solution package.

Using command-line interfaceWhen using the process solution command-line interface, you canbypass unsatisfied system check requirements by specifying the-force command-line flag.

Package requirements represent criteria put in place to ensure a successfuldeployment. While it is not recommended to bypass any requirements, theprocess solution installation programs permit the following types ofrequirements to be bypassed:v Capacity and consumption checks, for example, disk space and memory

requirements for a package.v Relationships defined for a root package. For example, Package �B�

might require that Package �A� is installed, before Package �B� can beinstalled. You can force processing of the install operation for Package�B�, even if Package �A� is not currently installed.

v Property checks defined for the package, for example, a check of thetype of operating system on which the install is being performed.

v Any custom checks defined for the package.

Note: Prerequisite, corequisite, and exrequisite dependencies definedbetween fix packages cannot be overridden.

System check progress messagesDuring the processing of the system check, the IBM Autonomic ComputingDeployment Engine publishes events detailing the progress of the systemcheck. The process solution installation programs receive the events andconvert them into localized messages with identifier CTGIN0146I which aredisplayed to the user. The messages include the label for the check beingperformed, the number of completed checks, and the total number ofchecks that are to be performed.

The IBM Autonomic Computing Deployment Engine is not able tocompute the total number of checks to be carried out before any checks areprocessed. As a result, the counter associated with the total number ofchecks to be performed can increase during system check processing. Forexample, the following set of messages might be issued during the systemcheck processing. The counter associated with the total number of checks isnot fixed, but recalculated and increased during system check processing.


CTGIN0146I: Completed system check for check "1" of "2". Check display name:"Check_Common_PMP_Installed".CTGIN0146I: Completed system check for check "2" of "3". Check display name:"Check_LTA_WAR_Package_Installed".CTGIN0146I: Completed system check for check "3" of "4". Check display name:"Check_Foundation_PM_Package_Installed".CTGIN0146I: Completed system check for check "4" of "4". Check display name:"MaximoDiskSpaceCheck".

Installing process managers using the process solution installationwizard

To install a process solution package into your IBM Tivoli Asset Management forIT instance, you might use the Process Solution Installer wizard.

About this task

Complete the following steps to install a process solution package into Tivoli AssetManagement for IT using the process solution installation wizard:

Procedure1. Launch the Process Solution Installer by navigating to the

tamit_install_dir\bin directory of your Tivoli Asset Management for ITinstance, and executing solutionInstallerGUI.bat. As with the processsolution installation command-line interface client, the process solutioninstallation (Install Anywhere) program executes on the administrativeworkstation. The launch script is deployed and configured by the Tivoli AssetManagement for IT installation program. No post-installation configuration isrequired. Invoke solutionInstallerGUI.bat and the wizard is launched.Alternatively, if you elected to create program shortcuts during the TivoliAsset Management for IT install, a link to the process solution installationprogram user interface might be available from the Start menu, a desktopicon, or a quick launch bar.

2. Select a language for your installation, and then click OK.3. From the Introduction panel, click Next.4. From the Choose PSI Package panel, click Choose and navigate to the package

file you want to deploy, select it, and then click Open. The process solutioninstallation package selected can be a base install, incremental update, fullupdate, or fix packageOnce a package has been selected and you click Next, the process solutioninstallation program performs a series of validation checks to verify that thepackage you selected is valid. The system is checked to ensure that thepackage has not already been deployed, or, if the package is intended as anupgrade, the system is checked to ensure that the base package has alreadybeen installed.

5. From the Package Validation Results panel, review and verify the informationdisplayed, and then click Next.

6. If it is the first time you have installed this process manager, the processsolution installation program license agreement window is displayed. Readthe license information and select I accept the terms in the license agreementif you agree with the terms. Click Next. If you are incrementally adding orremoving features from a previously installed process manager, you mightencounter an Add or Remove Features? panel where you declare whether you


are adding or removing features from the process manager, followed byanother panel where you select which specific features you are adding orremoving.

7. If it is the first time you have installed this process manager and it hasselectable features, you are prompted by the Feature Selection panel to selector deselect features you would like to install or uninstall from the previouslydeployed package.

8. From the Middleware Login Information panel, enter the credentials for whichyou are being prompted, and then click Next. The contents of this panel areconstructed dynamically, depending on the type of package you are installing.The package is queried to determine what middleware login credentials arenecessary to complete the installation of the package.Once you have entered the requested user IDs and passwords, the processsolution installation wizard validates the credentials by connecting to themiddleware servers using the supplied credentials.

9. After the credentials have been verified, a package options panel is displayedthat details the deployment options that the package supports. If the processsolution installation installable package supports the Overwrite CustomerModified Data during Update option, you can select it from this page. Afteryou specify which options to use, the process solution installation programperforms a system check. to ensure that all system requirements necessary forthe package to be installed are present. Click Next to advance.

10. From the Pre-Install Summary panel, review and verify the informationdisplayed, and then click Next. At this point, the process solution installationprogram begins the package installation process. A progress panel informsyou of the deployment progress of the installation.

11. When the installation has completed successfully, from the PackageSuccessfully Deployed panel, click Next. If there is a package failure, amessage is displayed for the step that failed. If it was a Feature Add, orRemoval, a message indicates that the feature was added or removedsuccessfully.

12. From the Install Another Package? panel, select Install Another Package? andclick Done, to install another package. Otherwise, ensure that Install AnotherPackage? is cleared and click Done to exit the process solution installationwizard.

Results

You might see an installation progress bar displayed briefly after you click Done.The process solution installation wizard is actually terminating and no installationactivities are being performed. The deployment of the process solution packageyou were installing has already completed and the progress bar can be safelyignored.


Related concepts

“Planning language support” on page 21Language support refers to the languages you plan to support in the Tivoli AssetManagement for IT user interface.Related tasks

“Installing language packs with Process Solution Installer” on page 228The Process Solution Installer guides you through the installation of a processmanager product (PMP) or Integration Module. Use the Process Solution Installerto refresh languages to synchronize them with Maximo languages.

Process solution installation client command-line interfaceThe process solution installation client command-line interface enables you toquery, install, upgrade, and uninstall process solution packages, which can consistof process modules and integration modules.

Invoking the process solution installation client command-lineinterface

A launch script is provided for starting the process solution command-lineinterface. The script is named solutionInstaller.bat and is deployed and configuredin the tamit_install_dir\bin directory.

The process solution command-line interface executes on the Tivoli AssetManagement for IT administrative workstation. The launch script is deployed andconfigured by the Tivoli Asset Management for IT installation program. Nopost-installation configuration is required. Invoke solutionInstaller.bat with thepreferred command string and the action is performed.

During processing of the command, the process solution command-line interfacewrites messages to the standard output of the command window from which thecommand was launched.

General syntaxRefer here for the general syntax of invoking the process solution installationprogram.

The syntax for invoking solutionInstaller is:solutionInstaller.bat parameter-clause-1 parameter-clause-2 ... parameter-clause-n

v Each parameter-clause consists of either -parameter_name parameter_value or-parameter_name.

v -parameter_name parameter_value is used for parameters that require aparameter value.

v -parameter_name is used for parameters that represent switches or flags whichdo not require a parameter value.

v parameter_name represents the name of one of the supported parameters.v parameter_names are always prefaced with a dash.v parameter_value represents the value associated with a particular parameter

name.v parameter_values that contained embedded spaces should be enclosed in

double-quotes.


Perform actionThe process solution installation program uses an action parameter wheninterfacing with packages.

A special parameter, -action, must be specified on each invocation ofsolutionInstaller. This parameter specifies the action or software life cycle operationto be performed. Based on the value specified for this parameter, additionalparameters might need to be specified. For example, when -action showinstalled isspecified, the type parameter must also be provided. The following table identifiesthe supported actions that might be specified for the process solutioncommand-line interface.

Table 19. Process solution command-line interface actions

Operation Value of -action Parameter

List Installed Packages showinstalled

List Available Packages showavail

Base Install install

Incremental Update/Fix Pack upgrade

Undo Incremental Update/Fix Pack undo

Uninstall uninstall

Apply Interim Fix applyfix

Undo Interim Fix undofix

List Installed Fixes for a Package showfixes

Refresh Language Support Files for a Package refreshlangs

Add or Remove Features modfeatures

Show Available Features showfeatures

Related concepts

“Supported operations for the process solution installation programs” on page 198There are multiple operations and functions that are supported by the processsolution installation wizard and process solution command-line interface.

Summary of supported parametersThis section contains a summary of parameters supported by the command-lineinterface.

The collection of supported parameters for the process solution command-lineinterface:

-actionSpecifies the function or software life cycle operation to perform.

-addfeatlistSpecifies the list of features to be installed. A feature is identified by itsuntranslated English Feature Identifier. Multiple features in the list areseparated by a colon character. If any of the Feature Identifiers includes aspace, then the entire value for this parameter is enclosed in quotationmarks.

-dbpwdSpecifies the password of the database user ID that is used to access theMaximo database.

dbuserSpecifies the database user ID that is used to access the Maximo database.


-delfeatlistSpecifies the list of features to be deleted. A feature is identified by itsuntranslated English Feature Identifier. Multiple features in the list areseparated by a colon character. If any of the Feature Identifiers includes aspace, then the entire value for this parameter is enclosed in quotationmarks.

-fixid Specifies the unique identifier of an interim fix/patch that you wantprocessed.

-force Specifies whether to continue on with a deployment operation even if thereare one or more unsatisfied requirements associated with the packagebeing processed.

-licenseSpecifies if you want to automatically accept the license agreement or ifyou want to be prompted for the acceptance or rejection of the licenseagreement by using one of the following values: accept or prompt.

-loadlanguagesSpecifies whether options language support files for the package need tobe loaded into the Maximo database

-loadsampdataSpecifies whether to load sample or demonstration data associated with thepackage being processed.

-maxpwdSpecifies the password of the Tivoli Asset Management for ITadministrative user that is used to access the product application.

-maxuserSpecifies the Tivoli Asset Management for IT administrative user ID that isused to access the Maximo console.

-pkgpathSpecifies the file path of a process solution package. Paths that haveembedded spaces are to be enclosed in quotes.

-pkguuidSpecifies the unique identifier of the process solution package that youwant processed.

-pkgverSpecifies the version of the process solution package that you wantprocessed.

-skipdbcfgSpecifies whether to defer the update of the Maximo database duringpackage deployment.

-skipj2eecfgSpecifies whether to defer the regeneration and redeployment of theMaximo J2EE applications during package deployment.

-type Specify one of the following types of solution element package to bereturned when the showavail or showinstalled actions are invoked. Validvalues are processmodule, integrationmodule, or all.

-waspwdSpecifies the WebSphere Application Server administrator password(was_admin_password).


-wasrxapwdSpecifies the password for the user ID under which remote access to theWebSphere Deployment Manager system is performed.

-wasrxauserSpecifies the user ID under which remote access to the WebSphereDeployment Manager system is performed.

-wasuserSpecifies the WebSphere Application Server administrator user ID(was_admin_user_id).

Process solution command-line interface referenceRefer to the following sections for process solution command-line interfacereference information.

Several of the command-line interface actions reference a syntax element named[middleware_login_information].

The syntax for the middleware login element is:[-wasuser was_user -waspwd was_password ][-dbuser userid -dbpwd password][-maxuser userid -maxpwd password][-wasrxauser userid -wasrxapwd password].

The descriptions of the various parameters are described in “Summary ofsupported parameters” on page 212 The actual user IDs and passwords that arerequired depend on the package being processed. For example, a package that onlydeploys content to the Maximo database would only require the -dbuser and-dbpwd parameters.

showinstalled action - list installed packagesThe showinstalled action displays a list of the currently installed process solutionpackages that have been installed into the Tivoli Asset Management for IT.Information about each installed package is written to the command prompt.

Actionshowinstalled

PurposeList information about the currently installed process solution packages.

SyntaxsolutionInstaller

-action showinstalled-type {processmodule|integrationmodule|all}

DescriptionThe following columns of information are displayed for each installedpackage:v Name identifies the display name of the installed package.v Version identifies the version-release-modification level of the installed

package.v Solution Type identifies whether the installed package is a Process

Manager Product or a System Integration Module.v Package Type identifies whether the installed package is a Base Install,

Incremental Update, or Full Update package.


v Unique Identifier identifies the 32 character hexadecimal value thatuniquely identifies the package.

PreconditionsNone

The following example displays information about all currently installed ProcessManager Products.solutionInstaller -action showinstalled -type processmodule

showavail action - list available packagesThe showavail action lists information about process solution package archive filesresiding in the Tivoli Asset Management for IT installation directory.

Actionshowavail


-action showavail-type {processmodule|integrationmodule|all}

DescriptionThe showavail action displays information about the process solutionpackage archive files that are located under the Tivoli Asset Managementfor IT installation directory. This command examines the process solutionpackage archive files that are located in the tamit_install_dir\pmpdirectory. When the showavail action is initiated, the process solutioninstallation service will query this directory and display information abouteach process solution package archive file in the directory.

The following columns of information are displayed for each package:v Name identifies the display name of the process solution package.v Version/Fix Name identifies the version-release-modification level of the

process solution package for a Base Install, Incremental Update, or FullUpdate package and the fix identifier for a Fix Package.

v Solution Type identifies whether the process solution package is for aProcess Manager Product or a System Integration Module. Package Typeidentifies whether the process solution package is a Base Install,Incremental Update, Fix, or Full Update package.

v Package Path identifies the file path of the process solution packagearchive file whose information is displayed.

Note: A process solution package archive does not need to reside in thisdirectory in order to be processed by the process solution command-lineinterface action. Any process solution package archive file that is accessiblefrom the Tivoli Asset Management for IT administrative workstation mightbe identified as the parameter value for the -pkgpath parameter.

PreconditionsNone

The following example shows information about all the Integration Module processsolution package archive files that are located under the tamit_install_dir\installableApps\solutions directory.solutionInstaller -action showavail -type integrationmodule


install action - install a packageThe install action is used to install a process solution package into Tivoli AssetManagement for IT. When installing a package, the file name of the processsolution package archive file to be installed is specified using the -pkgpathparameter.

Actioninstall

PurposePerform a Base Install of a process solution package not already installed.


-action install-pkgpath path_to_base_install_package_file[middleware_login_information][-license <accept|prompt>][-skipj2eecfg] [-skipdbcfg] [-loadlanguages] [-loadsampdata] [-force]

PreconditionsBefore using this action, ensure that:v The process solution package archive file you specify is a valid Base

Install package.v The package is not already to be installed. You can check it by using the

showinstalled action.v All additional requirements associated with the package specified are

satisfied.

The following example shows a Base Install of the Process Manager Product whoseprocess solution package is located C:\common_pmp_7.1.1.6.zip file. Access to boththe Maximo database and to the WebSphere Application Server are performedusing the specified user IDs and passwords. The license agreement associated withpackage is displayed for confirmation. Sample data associated with the ProcessManager Product package is loaded into the Maximo database.solutionInstaller

-action install-pkgpath C:\common_pmp_7.1.1.6.zip-wasuser user_id -waspwd password-dbuser user_id -dbpwd password-license prompt -loadsampdata

upgrade action - incrementally update a packageThe upgrade action is used to upgrade a currently installed process solutionpackage. During the upgrade process, the process solution installation servicechecks to ensure that a currently installed instance suitable to be upgraded hasalready been installed. When upgrading a package, you need to specify the filename of the process solution package file containing the upgraded artifacts.

Actionupgrade

PurposePerform an incremental update of a currently installed process solutionpackage.


-action upgrade-pkgpath path_to_update_package_file


[middleware_login_information][-license accept|prompt][-skipj2eecfg] [-skipdbcfg] [-loadlanguages] [-loadsampdata] [-force][-overwrite]

Description

There are two types of upgrade packages supported:

Incremental Update packageAn incremental update package requires that an existing instanceof the process solution package that is being upgraded is alreadyinstalled.

Full Update packageA full update package can be used to upgrade an existing instance,or it can be used to install a new instance using the -action installcommand.

PreconditionsBefore using this action, you need to ensure that:v The process solution package archive file you specify is a valid

Incremental Update or Full Update package.v An instance of the process solution package that is eligible to be

upgraded is already installed.v All additional requirements associated with the package specified are

satisfied.

The following example performs an incremental update of an already installedprocess solution package. The update package is located in theC:\TAMIT_ENG_7.2.1.0.zip file. Access to both the Maximo database and to theWebSphere Application Server are performed using the specified user IDs andpasswords. The license agreement associated with package is accepted withoutprompting for user confirmation.solutionInstaller

-action upgrade-pkgpath C:\TAMIT_ENG_7.2.1.0.zip-wasuser user_id -waspwd was_password-dbuser user_id -dbpwd password-license accept

undo action - undo an update to a packageThe undo action is used to remove the changes that were made by a previouslyinitiated incremental update. This action restores the process solution package toits previous state. During the undo process, the process solution installation servicechecks to ensure that the specified version of the package is an incremental updateversion and that the incremental update can be undone.

Actionundo

PurposeRemove the changes made to process solution package during a previousincremental update.


-action undo-pkguuid unique_id_of_package -pkgver package_version[middleware_login_information][-force]


Description

When undoing an Incremental Update, the user need to specify the uniqueidentifier and version of the incremental update that is to be undone. Aparticular incremental update package might not support the undo action.If an undo action is initiated for such a package, the process solutioninstallation client displays a message.

PreconditionsBefore using this action, ensure that:v The process solution package identified by the unique ID and version

that you specify is currently installed and represents an IncrementalUpdate Package.

v The Incremental Update that you are attempting to undo supports theundo action.

v All additional requirements associated with the package specified aresatisfied.

The following example performs undo from a previously made incremental updateto the process solution package with the specified unique identifier at version 1.1.1.Access to both the Maximo database and to the WebSphere Application Server areperformed using the specified user IDs and passwords.solutionInstaller

-action undo-pkguuid DC2894C667CE48ABAC25214A7FED16D5 -pkgver 1.1.1-wasuser was_user -waspwd was_password-dbuser user_id -dbpwd password

uninstall action - uninstall a packageThe uninstall action is used to uninstall a currently installed process solutionpackage. When uninstalling a package, the user will specify the unique identifierof the process solution package to uninstall. The unique identifier is displayedwhen the showinstalled action is run.

Actionuninstall

PurposeUninstall a currently installed process solution package.


-action uninstall-pkguuid unique_id_of_package[middleware_login_information][-force]

Description

Not all process solution packages support the ability to be uninstalled. Forexample, the uninstall action is not supported for the process solutionpackages distributed and installed as part of Tivoli Asset Management forIT. If the package does not support full uninstall, messages are displayedduring the uninstall action.

PreconditionsBefore using this action, ensure that:v The process solution package identified by the unique ID that you

specify is currently installed.v The process solution package supports partial or full uninstallation.


v All additional requirements associated with the package specified aresatisfied.

The following example shows how to perform uninstall of the process solutionpackage with the specified unique identifier. Access to both the Maximo databaseand to the WebSphere Application Server are performed using the specified userIDs and passwords.solutionInstaller

-action uninstall-pkguuid DC2894C667CE48ABAC25214A7FED16D5-wasuser was_user -waspwd was_password-dbuser user_id -dbpwd password

applyfix action - apply interim fix to a packageThe applyfix action is used to apply patches or interim fixes to a currentlyinstalled process solution package. During the upgrade process, the processsolution installation service checks to ensure that a currently installed instancesuitable to be patched has already been installed. When applying a fix to apackage, you need to specify the file name of the process solution package filecontaining the artifacts associated with the fix. This package file is referred to as anInterim Fix Package.

Actionapplyfix

PurposeApply an Interim Fix package to a currently installed process solutionpackage.


-action applyfix-pkgpath path_to_fix_package_file[middleware_login_information][-license <accept|prompt>][-skipj2eecfg] [-skipdbcfg] [-skipdbcfg] [-loadsampdata] [-force][-overwrite]

PreconditionsBefore using this action, ensure that:v The process solution package archive file you specify is a valid Interim

Fix package.v An instance of the process solution package that is eligible to be patched

by the Interim Fix package is already installed.v All additional requirements associated with the package specified are

satisfied.

The following example applies an Interim Fix package to a currently installedprocess solution package. The Interim Fix package is located in thepath_to_fix_package_file file. Access to both the Maximo database and to theWebSphere Application Server are performed using the specified user IDs andpasswords. The license agreement associated with package is accepted withoutprompting for user confirmation.solutionInstaller

-action applyfix-pkgpath C:\path_to_fix_package_file-wasuser was_user -waspwd was_password-dbuser user_id -dbpwd password-license accept


undofix action - undo an interim fix from a packageThe undofix action is used to remove a previously applied fix package. Eachinterim fix package has a fix identifier that uniquely identifies the interim fixwithin a process solution package. You specify this fix identifier (as well as theunique identifier of the base package) when you invoke the undofix action. Duringthe process, the process solution installation service checks to ensure that thespecified fix is already applied.

Actionundofix

PurposeRemove a previously applied interim fix from a process solution package.


-action undo-pkguuid unique_id_of_package -fixid fix_identifier[middleware_login_information][-force]

Description

Note: A particular interim fix package might not support the undofixaction. If an undofix action is initiated for such a package, the processsolution installation client displays a message.

You can determine the set of interim fixes already applied to a processsolution package using the showfixes action of the process solutioncommand-line interface.

PreconditionsBefore using this action, you need to ensure that:v The process solution package identified by the unique ID is currently

installed.v The interim fix identified by the fix identifier is already applied to the

process solution package.v The interim fix that you are attempting to undo supports the undofix

action.v All additional requirements associated with the package specified are

satisfied.

The following example shows how a previously applied interim fix with fixidentifier PTF00001 is undone from the process solution package with the specifiedunique identifier. Access to both the Maximo database and to the WebSphereApplication Server are performed using the specified user IDs and passwords.solutionInstaller

-action undofix-pkguuid DC2894C667CE48ABAC25214A7FED16D5-fixid PTF00001-wasuser was_user -waspwd was_password-dbuser db_user -dbpwd db_password

showfixes action - list installed fixes for a packageThe showfixes action displays a list of the currently installed Interim Fixes thathave been previously applied to a currently installed process solution package.Information about each installed fix is written to the command prompt. When you


use this action, you specify the unique identifier and version of the currentlyinstalled process solution package for which the collection of Interim Fixes is to bedisplayed.

Actionshowfixes

PurposeList information about the Interim Fixes that have been applied to acurrently installed process solution package.


-action showfixes-pkguuid unique_id_of_package-pkgver package_version

Description

The following columns of information are displayed for each applied fix:v Name identifies the unique identifier for the Interim Fix.v Fix Type identifies the type of the Interim Fix.

PreconditionsBefore using this action, ensure that:v The process solution package identified by the unique ID and version

that you specify is currently installed.

The following example lists the currently applied Interim Fixes for the processsolution package having the specified unique identifier and version.solutionInstaller

-action showfixes-pkguuid 1480586C22E24D6A8754265DC38AEBDD-pkgver 1.1.0

refreshlang action - refresh languages for a packageThe refreshlang action is used to either install or refresh the language support filesassociated with a package that is already installed. The action unpacks thelanguage support files contained within the package, write those language supportfiles to the administrative workstation, and then load the language support filesinto the Maximo database.

The following items define the refreshlang:

Actionrefreshlang

PurposeInstall or refresh the language support files for a package that is alreadyinstalled.


-action refreshlangs-pkgpath path_to_base_install_package_file[middleware_login_information][-license <accept|prompt>][-skipj2eecfg] [-skipdbcfg] [-force]

DescriptionThe refreshlangs action is used to either install or refresh the languagesupport files associated with a package that is already installed. The action


unpacks the language support files contained within the package, writethose language support files to the Tivoli Asset Management for ITadministrative workstation, and then load the language support files intothe Maximo database.

This action can be used even if language support files were not originallyinstalled using the -loadlanguages flag when the base install for thepackage was performed using the -action install command.

PreconditionsBefore using this action, ensure that:v The process solution package archive file you specify is a valid base

install package.v The package was previously installed. You can check it by using the

showinstalled action.v The package supports user-selectable deployment of language support

files.v All additional requirements associated with the package specified are

satisfied.

The following example shows how to refresh the language support files containedwithin the Process Manager Product whose process solution package is locatedC:\Tamit_ENG_7.2.1.0.zip file. Access to the Maximo database is performed usingthe specified userid and password.solutionInstaller

-action refreshlangs-pkgpath C:\Tamit_ENG_7.2.1.0.zip-dbuser user_id -dbpwd password-license accept

showfeatures action - show features of a solution packageThe showfeatures action displays a list of information about the supported andcurrently installed features for a process solution package. Information about eachfeature is written to the command prompt.

Actionshowfeatures

PurposeList information about installed and available features associated with aprocess solution package.


-action showfeatures-pkgpath path_to_base_install_package_file

Description

This action can be used against any process solution package, even if thatprocess solution package has not already been installed.v Use this command against a currently installed process solution package

to determine the features that are currently installed for the package andto determine the available features (not yet installed) that might beadded.

v Use this command against a process solution package not alreadyinstalled to determine the available features that might be specified onthe –addfeatlist parameter of the –action install command-line interfaceaction.


When you use this action, you specify the package path of a processsolution package for which the feature information is to be displayed. Thecommand output includes an indication of whether the package isinstalled.

The following columns of information are displayed for each feature:

Feature ID Identifies the unique identifier for feature

Display Name Identifies the localized display name for thefeature

Parent ID Lists the parent of this feature , if applicable

Is Installed? Identifies whether the feature is currently installed

Is Required? Indicates whether this is a required feature forinstallation

PreconditionsBefore using this action, ensure that:v The process solution package identified by the -packagepath is a valid

process solution package archive file.

The following example lists information about the features associated with theprocess solution package having the specified package path.solutionInstaller

-action showfeatures-pkgpath C:\path_to_base_install_package_file

modfeatures action - modify existing features of a deployedpackageDescription of the action used to modify existing features of a deployed package.

Actionmodfeatures

PurposeModify features of a currently installed process solution package.


-action modfeatures-pkgpath path_to_base_install_package_file[-addfeatlist Feature �A�:Feature �B�:¦:Feature �n�][-delfeatlist Feature �A�:Feature �B�:¦:Feature �n�][middleware_login_information][-skipj2eecfg] [-skipdbcfg] [-force]

DescriptionThe modfeatures action is used to modify the installed features for acurrently installed process solution package. When modifying features, thefile name of the process solution package archive file containing thefeatures to be modified is specified using the -pkgpath parameter. To addnew features not already installed, you use the –addfeatlist parameter. Toremove currently installed features, you use the parameter. You might notboth add and remove features with one invocation. One and exactly one ofeither the or the –delfeatlist parameters must be provided when thiscommand is invoked.

PreconditionsBefore using this action, ensure that:


v The process solution package archive file you specify is a valid BaseInstall package.

v The package is already installed. You can check it by using theshowinstalled action.

v Any features specified with the are valid for the specified package andare not already deployed.

v Any features specified with the are valid for the specified package andare already installed.

v All additional requirements associated with the features being specifiedare satisfied.

v The exact feature name is known. It can be obtained by using the action

The following example adds the features with identifiers Samples and DBSupport.The process solution package being modified is located base_services_7.1.1.6.zipfile. Access to both the Maximo database and to the WebSphere Application Serverare performed using the specified user IDs and passwords.solutionInstaller

-action modfeatures-pkgpath C:\base_services_7.1.1.6.zip-wasuser was_user b -waspwd was_password-dbuser db_user -dbpwd db_password-addfeatlist Samples:DBSupport

Installing and refreshing language support files for a packageA process solution package might define one or more language support features.

When a language support feature for a process solution package is installed usingthe process solution installation programs, XLIFF files associated with all supportlanguages are unpacked onto the Tivoli Asset Management for IT administrativeworkstation. The Maximo Translation Data toolkit PMPUPDATE is invoked. Thisutility imports the XLIFF files associated with the process manager into theMaximo database, based on the base language and any other selected languagesthat have been installed.

If you intend to install language support for Tivoli Asset Management for ITprocess managers for the first time, refer to Chapter 11, “Installing languagepacks,” on page 227. If you intend to refresh language support files for the TivoliAsset Management for IT process managers, or you have installed another processmanager, use the instructions provided in this section.

There are two models for how the process solution package can expose itslanguage support.v A package can define a single language support feature with a special feature

identifier. The process solution installation programs provide some built-inspecial mechanisms for deploying language support for packages using thismodel.

v A package can define multiple language support features. The selectable featuresupport in the process solution installation programs are used for deployinglanguage support for packages using this model.


Related tasks

“Manually configuring Directory Server” on page 147The example included shows a LDIF example.Chapter 11, “Installing language packs,” on page 227

Deployment for packages with a single special languagesupport feature

Packages can be deployed with a single special language support.

About this task

Many process solution packages define a single language support feature with afeature identifier of LANG_SUPT_FEATURE. For these packages, the processsolution command-line interface allows this special language support feature to bedeployed during a base install using the -loadlanguages parameter. The languagesupport for this special feature can also be installed after a base install or refreshedusing the refreshlangs action of the process solution command-line interface.

Installing language support files at base installWhen you initially perform a base install of a package with the speciallanguage support feature, you can elect to also install the language supportfiles for the package.

Using the installation wizardWhen using the process solution installation wizard to perform abase install of a package, the Feature Selection Panel displays thelanguage support feature in the set of available features for thepackage. When you select this check box, the process solutioninstallation wizard unpacks the language support files associatedwith the package and then invokes the Maximo Translation Datatoolkit PMPUPDATE function.

Using the command-line interfaceWhen using the process solution command-line interface, you caninstall the language support files for the package by specifying the-loadlanguages command-line flag when you perform a baseinstall of a package using the -action install subcommand.

Installing or refreshing language support after base installAfter the package has been initially installed, you can install or refresh thelanguage support files for the package. The process solution command-lineinterface provides an -action refreshlangs subcommand for this purpose.This action is only supported for packages that are already installed. Theaction can be used even if the language support files were not installedwhen the package was originally installed. In both scenarios, the languagesupport files for the package are unpacked and copied to the Tivoli AssetManagement for IT administrative workstation and the MaximoTranslation Data toolkit PMPUPDATE function.

Note: The function to install or refresh language support files is onlyavailable using the process solution command-line interface. The functionis not available using the wizard.

Deployment for packages with multiple language supportfeatures

Packages can be deployed with a multiple language support.


About this task

A process solution package that supports various selectable features might alsohave multiple language support features.

Installing language support files at base installThe language support features for packages that define multiple languagesupport can be deployed during a base install of the package or might beadded after the base install using the new selectable feature support in theprocess solution installation wizard and process solution command-lineinterface. For these types of packages, the language support features aremanaged just like other selectable features defined for the package.

Installing or refreshing language support after base installWhen the refreshlangs action of the process solution command-lineinterface is invoked for a package with multiple language support features,only currently installed language support features for the package arerefreshed. It is accomplished by re-execution of the deployment actionsassociated with all currently installed language support features.

The refreshlangs action when invoked on a package with multiplelanguage support features never installs those language support features.The refresh processing is only performed against currently installedlanguage support features.

Note: This behavior differs from the refreshlangs behavior when appliedagainst a package defining the special LANG_SUPT_FEATURE identifier.In that scenario, the special language support feature is installed if it is notcurrently installed, or it is refreshed if it is installed.

Related concepts

“Planning language support” on page 21Language support refers to the languages you plan to support in the Tivoli AssetManagement for IT user interface.


Chapter 11. Installing language packsIf you choose to install IBM Tivoli AssetManagement for IT with manual IBMWebSphere Application Server configuration,follow the procedures described in “Installingand refreshing language support files for apackage” on page 224 and “Installinglanguage packs with Process SolutionInstaller” on page 228.

MXServer must be started before running thelanguage pack installation program. If youplan to add language support to Tivoli AssetManagement for IT, use the language packinstallation program before you perform postinstallation steps.

Related concepts

“Installing and refreshing language support files for a package” on page 224A process solution package might define one or more language support features.“Planning language support” on page 21Language support refers to the languages you plan to support in the Tivoli AssetManagement for IT user interface.Related tasks

“Generating xml request pages” on page 266Perform this task after you installed Tivoli Asset Management for IT and before yourun request pages. This procedure needs to be performed for every language thatis enabled on your system.

Installing language packs with the LaunchpadAfter you installed IBM Tivoli Asset Management for IT, set the Maximo language.Tivoli Asset Management for IT installation program does not install languages, soyou need to add them.

Before you begin

Because language pack installation can take several hours to complete, decidewhich additional languages you need before starting installation. Each additionalselected language increases the amount of time to complete the installation. Also,do not add as an additional language the language you select as your base. It isnot necessary and only increases the installation time.

Important:

v MXServer must be started before running the Tivoli Asset Management for ITlanguage pack installation.

v If you plan to add language support to Tivoli Asset Management for IT, use theTivoli Asset Management for IT language pack installation before you performpost installation steps described in Chapter 14, “Post installation tasks,” on page253.


About this task

To use the Tivoli Asset Management for IT language pack installation program toinstall the language pack, complete the following steps:

Procedure1. Ensure that all Tivoli Asset Management for IT middleware servers and

services are running. If you encounter a failure resulting from an inactivemiddleware server or service, start that server or service, and then rerun thelanguage pack installation program. The language pack installation programfirst uninstalls the base and additional languages installed by the processsolution installation wizard in the failed installation attempt, and performs areinstall.

2. Log in as Administrator on the Tivoli Asset Management for IT administrativesystem.

3. On the Launchpad, click the Tivoli Asset Management for IT Language PackInstaller link under 2.

4. Select a language for the install, and then click OK. This choice is only for useduring the installation and its selection does not affect the languages beinginstalled.

5. From the Welcome panel, click Next.6. From the Base Language panel, select a base language that is to be used with

Tivoli Asset Management for IT, and then click Next.Attention: This is the only opportunity to select a base language. You cannotchange the base language at a later time.

7. From the Additional language selection panel, select additional languages to besupported, and then click Next. You are not prevented from selecting thelanguage you specified in the Base Language panel as an Additional Language.While no error occurs during installation, in practice, do not specify the baselanguage as an additional language. Doing so is redundant.

8. From the language selection summary panel, review the information and thenclick Next.

9. From the Pre-install Summary Panel, click Install.

Results

Even if you added additional languages through the language pack installationprogram, and you set the locale of your computer to a language that was installedas an additional language, you might still encounter instances in the Tivoli AssetManagement for IT user interface where items are displayed in the language youidentified as the base language of the computer. This problem is a knownlimitation and does not indicate that the language pack installation failed.

In some cases, shortcut elements appearing in the Tivoli Asset Management for ITuser interface, for example menu choices, are displayed only in the base languagedesignated or in English.

Installing language packs with Process Solution InstallerThe Process Solution Installer guides you through the installation of a processmanager product (PMP) or Integration Module. Use the Process Solution Installerto refresh languages to synchronize them with Maximo languages.


Before you begin

If you have run the language pack installation, you have Maximo languages set.The next step is to refresh languages for IBM Tivoli Asset Management for IT 7.2.2.

About this task

Note: Perform this task after you installed Tivoli Asset Management for IT andIntegration Composer. To pick up language packs for Tivoli Asset Management forIT and Integration Composer, install ITIC_PMP_7.2.2.0.zip andTAMIT_ENG_7.2.2.0.zip packages again, after running the Launchpad.

To install additional languages with Process Solution Installer, launch the wizardand follow the instructions on the consecutive windows. In the Choose PSIPackage window, you are prompted to choose PMP archive files.

By default, the packages are located in the tamit_install_dir/pmp directory.

To choose and install any PSI package, perform these steps:

Procedure1. On the administrative workstation, launch the Process Solution Installer (PSI):

Click Start → Programs → IBM Tivoli base services → Process Solution Installer.2. Select a language for your installation, and then click OK.3. On the Introduction panel, click Next.4. On the Choose PSI Package panel, click Choose and:

a. Navigate to the temporary directory where you downloaded anduncompressed the fix pack.

b. Select a PSI archive package and click Open.5. On the Package Validation Results panel, review and verify the information

displayed, and then click Next.6. On the Middleware Login Information panel, enter the credentials for which

you are being prompted, and then click Next.The contents of this panel are constructed dynamically, depending on the typeof package you are installing. The package is queried to determine whichmiddleware login credentials are necessary to complete the installation of thepackage.After you enter the requested user IDs and passwords, the Process SolutionInstaller validates the credentials by connecting to the middleware serversusing the supplied credentials.

7. After the credentials have been verified, a package options panel is displayedthat details the deployment options that the package supports.

Note: When installing any of the fix pack PSI packages using PSI, theupdatedb step cannot be deferred. DO NOT select the option to Defer theUpgrade of the Maximo Database.After you specify which options need to be used, the Process Solution Installerperforms a system check to ensure that all system requirements necessary forthe package to be installed are present. Click Next.

8. On the Pre-Install Summary panel, review and verify the informationdisplayed, and then click Next. The Process Solution Installer begins installingthe PSI package. A progress panel informs you of the progress of the

Chapter 11. Installing language packs 229

deployment. When the installation is complete, the Package SuccessfullyDeployed panel is displayed. Click Next.

9. On the Install Another Package panel, do one of the following:v If you want to install another PSI package, select Install Another Package?

and click Done. Then repeat the preceding steps of this procedure, startingwith 4 on page 229.

v If you are finished installing PSI packages, clear Install Another Package?and click Done to exit the Process Solution Installer.

Related concepts

“Planning language support” on page 21Language support refers to the languages you plan to support in the Tivoli AssetManagement for IT user interface.Chapter 10, “Process solution package installation methods,” on page 193Included within IBM Tivoli Asset Management for IT are common installationprograms that provide you with the ability to manage the software lifecycle ofTivoli Asset Management for IT process solutions, including functions to query,install, upgrade, and uninstall process solution packages. These commoninstallation programs are collectively referred to as the process solution installationprograms.

Language deployment after database update deferralSelecting the option to defer the update of the Maximo database when installingthe product affects how you deploy languages.

During installation, you have the option to defer the database update task. Thisoption prevents writing data to the database during the installation. Theinstallation program is limited to copying files to the administrative system andregistering product process solution packages.

When you select the option to defer the database update, the type of installationthat you do determines how you deploy languages.

For new installations, you add languages by completing the installation, manuallyupdating the database, and then using the language pack installation program.This scenario does not include installing the product alongside another solutionmanagement product.

For upgrade or fix pack installation scenarios, you must manually deploylanguages for individual PSI packages. This scenario also includes installing theproduct alongside another solution management product. See “Manually deployinglanguages after database update deferral” for more information.

Manually deploying languages after database update deferralLanguages must be deployed manually if you perform an upgrade task and deferdatabase updates by the installation program.

Before you begin

During the application of language pack files for a PSI package, it is important thatyou provide the appropriate version parameter to the TDToolkit command.Parameters provided must be compatible with the version of the PSI package thatis currently installed.


The following values are valid at the current version of the product:v V7100-000v V7113-000v V7114-000v V7115-000v V7116-000v V7117-000

When performing an upgrade action, you must first identify the level of eachexisting PSI package. You can then determine the appropriate version parametervalue to use.

To determine the levels of existing PSI packages, type the following command:solutioninstaller.bat -action showinstalled -type all

This command produces a list of all PSI packages that are currently deployed andtheir version.

The version reported must be incremented to the next level of language pack thathas been made available through releases and fix packs. No matter which versionof the product you are installing, you must always only increment to the nextlanguage pack version from the current version. So, for example, if a PSI packagelevel is reported at version 7.1.1.3, you must set the version parameter of theTDToolkit command to V7114-000. If the PSI package level is reported as 7.1.1.3,and you are upgrading to version 7.2 of the product, you set the version parameterto V7114-000. V7114-000 is the next level of language support available. Identifyingthe next increment communicates to the TDToolkit command the earliest versionthat it must supply new language support files for.

The following procedure assumes you have manually updated the database usingthe updatedb -v1 command.

About this task

To manually configure languages for PSI packages, complete the following steps:

Procedure1. Update language support for the Maximo core components. The following

language packs are available in the C:\IBM\SMP\pmp directory:CCMDB_Lang_Pkg_7.1.1.7_Ar.zipCCMDB_Lang_Pkg_7.1.1.7_Cs.zipCCMDB_Lang_Pkg_7.1.1.7_Da.zipCCMDB_Lang_Pkg_7.1.1.7_De.zipCCMDB_Lang_Pkg_7.1.1.7_En.zipCCMDB_Lang_Pkg_7.1.1.7_Es.zipCCMDB_Lang_Pkg_7.1.1.7_Fi.zipCCMDB_Lang_Pkg_7.1.1.7_Fr.zipCCMDB_Lang_Pkg_7.1.1.7_He.zipCCMDB_Lang_Pkg_7.1.1.7_Hr.zipCCMDB_Lang_Pkg_7.1.1.7_Hu.zipCCMDB_Lang_Pkg_7.1.1.7_It.zip


CCMDB_Lang_Pkg_7.1.1.7_Ja.zipCCMDB_Lang_Pkg_7.1.1.7_Ko.zipCCMDB_Lang_Pkg_7.1.1.7_Nl.zipCCMDB_Lang_Pkg_7.1.1.7_No.zipCCMDB_Lang_Pkg_7.1.1.7_Pl.zipCCMDB_Lang_Pkg_7.1.1.7_Pt_BR.zipCCMDB_Lang_Pkg_7.1.1.7_Ru.zipCCMDB_Lang_Pkg_7.1.1.7_Sl.zipCCMDB_Lang_Pkg_7.1.1.7_Sv.zipCCMDB_Lang_Pkg_7.1.1.7_Tr.zipCCMDB_Lang_Pkg_7.1.1.7_Zh_CN.zipCCMDB_Lang_Pkg_7.1.1.7_Zh_TW.zip

Within each language pack, located under the \FILES directory, there is apackage of xliff files for that language. So, for example, in theCCMDB_Lang_Pkg_7.1.1.7_Es.zip language pack file, you would findCCMDBLangPkgEsXliff.zip within the \FILES directory of the languagepack. This file contains the actual xliff files which need to be extracted to the<CCMDB_HOME>\maximo directory. Proceed to unpack the xliff files into theC:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system,where locale is the directory for a specific language.a. For each language you want to enable for this package, extract the xliff files

found in the corresponding language pack file located in theC:\IBM\SMP\pmp directory. The xliff files are located in the \FILESsubdirectory of the compressed language package file. You need to extractthe xliff files for a language into the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory.

b. To update a language as the base language to use for the product, run thefollowing command:<TAMIT_HOME>\maximo\tools\maximo\TDToolkit.bat-IMPORT-SLEN-TLlocale-version"version-000"-maxmessfix

c. To add one or more languages as additional languages for use with theproduct, run the following command for each language you want to add:<TAMIT_HOME>\maximo\tools\maximo\TDToolkit.bat-ADDLANGlocale-version"version-000"-maxmessfix

2. Update language support for common_pmp_7.1.1.7.zip:a. For each language you want to enable for this package, extract the xliff files

found in the corresponding language pack file located in theC:\IBM\SMP\pmp directory. The xliff files are located in the \FILESsubdirectory of the compressed file. The xliff files for a language areuncompressed into the <TAMIT_HOME>\Maximo\Tools\Maximo\locale\xliff\directory.

b. Update language support using the following commands:<TAMIT_HOME>\maximo\tools\maximo\TDToolkit.bat-pmpupdatecommon_pmp-version"version-000"

3. Update language support for ITIC_PMP_7.2.2.zip:


a. For each language you want to enable for this package, extract the xliff filesfound in the corresponding language pack file located in theC:\IBM\SMP\pmp directory. The xliff files are located in the \FILESsubdirectory of the compressed file. The xliff files for a language areuncompressed into the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\directory.

b. Update language support using the following commands:<TAMIT_HOME>\maximo\tools\maximo\TDToolkit.bat-pmpupdateitic_pmp-version"version-000"

4. Update language support for TAMIT_ENG_7.2.2.zip:a. For each language you want to enable for this package, extract the xliff files

found in the corresponding language pack file located in theC:\IBM\SMP\pmp directory. The xliff files are located in the \FILESsubdirectory of the compressed file. The xliff files for a language areuncompressed into the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\directory.

b. Update language support using the following commands:<TAMIT_HOME>\maximo\tools\maximo\TDToolkit.bat-pmpupdatetloam_pmp-version"version-000"

5. If applicable, update language support for ServiceProviderFixpack7112.zip:a. For each language you want to enable for this package, extract the xliff files

found in the corresponding language pack file located in theC:\IBM\SMP\pmp directory. The xliff files are located in the \FILESsubdirectory of the compressed file. The xliff files for a language areuncompressed into the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\directory.

b. Update language support using the following commands:<TAMIT_HOME>\maximo\tools\maximo\TDToolkit.bat-pmpupdateserviceprovider-version"version-000"



Chapter 12. Installing Integration ComposerAfter you have successfully installed the IBM TivoliAsset Management for IT components, you canoptionally install IBM Tivoli Integration Composer, anintegration tool that imports information technology (IT)data into the Maximo database.

Tivoli Asset Management for IT installations use theLaunchpad as an interface for installing IntegrationComposer. However, if necessary, you can installIntegration Composer on a UNIX operating system inconsole mode, from the command line.

When you install Integration Composer and Tivoli AssetManagement for IT from the Launchpad, the installerautomatically updates the Integration Composerdatabase tables in the Integration Composer repositoryfor you.

IBM Tivoli Integration Composer overviewIntegration Composer is the IBM application for transforming and importinginventory data about deployed hardware and software. This inventory data isimported from a discovery or system management tool database into the Maximodatabase tables for deployed assets or configuration items.

With Integration Composer, an enterprise can aggregate data collected by externaldiscovery tools and integrate it into the Maximo database, creating a centralrepository for enterprise IT asset management, reporting, and decision support.The Maximo database is the repository used by:v IBM Tivoli Asset Management for ITv IBM Tivoli Service Request Managerv IBM Tivoli Change and Configuration Management Database

To collect the data about deployed assets or configuration items, a discovery toolscans computers, network devices, and network printers deployed in an enterpriseand records information about the hardware and software it finds there.Integration Composer uses an integration adapter to transform the data collectedby the discovery tool and move it from the discovery tool database into theMaximo database. (For more about creating your own integration adapter, see thebook Integration Composer Administrator Guide.)

You can view imported data from various applications on your system. The data isalso used to generate reports.

Note: Integration Composer is used to import hardware and software inventorydata from a discovery tool database into the Deployed Asset, Actual CI, or (for thepurposes of asset initialization) Asset tables in the Maximo database. The import orexport of data into or out of other tables within the Maximo database isaccomplished using a different tool, the integration framework. Refer to the relatedbook, Integration Guide, for more on this subject.


Hardware and software requirementsThis section describes the products and versions supported by IntegrationComposer, plus the hardware and software requirements for the corequisiteapplications.

The hardware and software requirements for Integration Composer and itscorequisites are as follows:

IBM TivoliIntegrationComposer

Integration Composer 7.2.2 has the following minimum requirements:

v 3 GB memoryv 70 MB disk spacev IBM Java Software Development Kit 5.0 Service Release 5

IBM Tivoli AssetManagement for IT,

IBM Tivoli ServiceRequest Manager,

IBM Maximo AssetManagement forEnergyOptimization, or

IBM Tivoli Changeand ConfigurationManagementDatabase

IBM Tivoli Asset Management for IT 7.2.2 is required and must be installed beforeyou can use IBM Tivoli Integration Composer.

For details about compatibility with the following products, see the documentationfor the specific product:

v IBM Tivoli Service Request Managerv IBM Maximo Asset Management for Energy Optimizationv IBM Tivoli Change and Configuration Management Database

Each product includes the Maximo database.


IBM TivoliIntegrationComposer server

A dedicated server is required for running the Integration Composer applicationand Java components. Integration Composer can run on any of the followingoperating systems:

v HP-UX 11i 3 (on Intel Itanium hardware)v IBM AIX 5L 5.3 (32-bit)v IBM AIX 5L 5.3 (64-bit)v IBM AIX 5L 6.1 (32-bit)v IBM AIX 5L 6.1 (64-bit)v Microsoft Windows Server 2003 Enterprise Edition (on x86-32 hardware)v Microsoft Windows Server 2003 Enterprise Edition (on x86-64 hardware)v Microsoft Windows Server 2008 Enterprise Edition, Release 2 (on x86-64

hardware)v Microsoft Windows Server 2008 Standard Edition, Release 2 (on x86-64

hardware)v Red Hat Enterprise Linux 4 (on x86-32 hardware)v Red Hat Enterprise Linux 4 (on x86-64 hardware)v Red Hat Enterprise Linux 4 (on zSeries and System z hardware)v Red Hat Enterprise Linux 5 (on x86-32 hardware)v Red Hat Enterprise Linux 5 (on x86-64 hardware)v Red Hat Enterprise Linux 5 (on zSeries and System z hardware)v Sun Solaris 9 (on SPARC processor-based systems)v Sun Solaris 10 (on SPARC processor-based systems)v SUSE Linux Enterprise Server (SLES) 9 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 10 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 10 (on x86-32 hardware)v SUSE Linux Enterprise Server (SLES) 10 (on x86-64 hardware)v SUSE Linux Enterprise Server (SLES) 11 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 11 (on x86-32 hardware)v SUSE Linux Enterprise Server (SLES) 11 (on x86-64 hardware)v VMWare ESX Server 3

Note: Bidirectional languages are not supported on the Sun Solaris platform.

Chapter 12. Installing Tivoli Integration Composer 237

Database servers The customer is responsible for the database servers, which contain and manageone or more source databases and a target (Maximo) database.

The following databases are supported:

v IBM DB2 Universal Database Express Edition 8.2 (on all supported operatingsystems)

v IBM DB2 Enterprise Server Edition 9.1, Fix Pack 1 (on all supported operatingsystems)

v IBM DB2 Enterprise Server Edition 9.1, Fix Pack 8 on 32-bit Linuxv IBM DB2 Enterprise Server Edition 9.5 (on all supported operating

systems—does not support 32-bit Linux)v IBM DB2 Enterprise Server Edition 9.7v IBM DB2 Enterprise Server Edition 9.7v Microsoft SQL Server 2005 (on Microsoft Windows operating systems only)v Microsoft SQL Server 2008 Enterprise Edition (on Microsoft Windows operating

systems only)v Oracle Database 9i Enterprise Edition Release 2.9.2.0.8 (on all supported

operating systems)v Oracle Database 10g Enterprise Edition Release 1 (on all supported operating

systems)v Oracle Database 10g Enterprise Edition Release 2 (on all supported operating

systems)v Oracle Database 11g Enterprise Edition Release 1 (on all supported operating

systems)

See the appropriate database documentation for the database server hardwarerequirements.

Web browser To display its help information, Integration Composer requires a Web browser.

Integration adapter data schemas renamed during upgradingIf you are upgrading fromTivoli Asset Management for IT 7.1 and currently useTivoli Integration Composer 7.1 with an integration adapter, the name of your dataschema might be changed when you upgrade.

In previous releases, data schemas were installed with the integration adapters. Butwith Tivoli Asset Management for IT 7.2.2 they are installed directly into thedatabase. If the name of the data schema you currently use matches any of thedata schema names in Table 20 on page 239, the installation program will add thetext string renamed by TAMIT 7.2.2 to the existing data schema name. For example,Centennial Discovery 2005 is changed to Centennial Discovery 2005 renamed byTAMIT 7.2.2.

Only the data schema name as it appears in the Integration Composer userinterface will be renamed. The name of your existing data schema (.schm) fileremains as is. Renaming prevents your original Integration Composerconfiguration and settings from being overwritten during the upgrading process.

Table 20 on page 239 lists the integration adapters whose data schema namesmatch those of previous releases. If your existing data schema name matches anyof the names in the table, it will be renamed during upgrading:


Table 20. Out-of-the-box data schema names for the Integration Composer 7.2.2 integrationadapters

Integration adapter Data schema names

Centennial Discovery 2005 Centennial Discovery 2005

Centennial Discovery 2006 and 2007 Centennial Discovery 2006/2007

IBM Tivoli Network Manager IP Edition 3.7 Tivoli Network Manager IP Edition 3.7

Tivoli Application Dependency Discovery Manager 7.1Tivoli Application Dependency DiscoveryManager 7.1

Tivoli Provisioning Manager 5.1 Tivoli Provisioning Manager 5.1

Installation prerequisitesBefore installing, you need to have the IBM Java SDK prerequisite for IntegrationComposer on your system, and any software that adversely affects theInstallAnywhere installation program must be removed.

IBM Java SDK 5.0 Service Release 5 for the appropriate operating system is aninstallation prerequisite that must be present on the Integration Composercomputer. The IBM Java SDK is provided on the IBM Tivoli Asset Management forIT Support site.

UNIX In addition, on UNIX based operating systems, be sure the PATHenvironment variable includes the location of the Java Virtual Machine (forexample, Java50).

Because the following software can adversely affect InstallAnywhere—theinstallation program used by Integration Composer—disable the followingprograms before attempting to install Integration Composer:v Antivirus software, such as Norton Antivirus or Symantec Client Firewallv Dell OpenManagev Search software, such as pcAnywhere

Use of these software programs affects the ability of InstallAnywhere to installprograms; however, the problem is not specific to Integration Composer.

Before beginning your installation, make sure that you have on hand theinformation about the target (Maximo) database described in Table 21 on page 241.

Performing the IBM Tivoli Integration Composer installationTivoli Asset Management for IT installations that want to use IntegrationComposer must install it from the Launchpad, as described herein. If you need toinstall Integration Composer on a UNIX operating system in console mode,instructions to do that are also described.

Results

When the installation completes successfully, you can access Integration Composeras follows:

Windows From the Start menu, or by entering the command: startFusion.bat


UNIX By entering the command: ./startFusion.sh

Installing IBM Tivoli Integration Composer using theLaunchpad

Windows UNIX For IBM Tivoli Asset Management for IT installations, therecommended way to install IBM Tivoli Integration Composer is from theLaunchpad. Use the Launchpad to install Tivoli Integration Composer on Windowsor UNIX operating systems.

Before you begin

Make sure that you have up to 70 MB of free space for the installation directory.

About this task

To install IBM Tivoli Integration Composer from the Launchpad, complete thesteps that follow.

Procedure1. Insert the Launchpad DVD into the server where you install Tivoli Integration

Composer.If you are installing on a UNIX operating system, you might have to start theLaunchpad manually by running the launchpad.sh command, which is locatedin the root directory of the Launchpad DVD. (On Windows operatingsystems, the launchpad.exe command runs automatically.)

2. From the Launchpad, launch the Tivoli Integration Composer installationprogram by clicking the link under 3. Install Tivoli Integration Composer.

Note: If you do not have the prerequisite IBM Java SDK 5.0 Service Release 5currently installed and in your system path, the installation ends. For UNIXusers, the following explanatory message is displayed:No Java Virtual Machine could be found from your PATH environment variable.You must install a VM prior to running this program.

3. In the IBM Tivoli Integration Composer window, select your language fromthe drop-down list at the bottom and click OK.

4. [UNIX only.] In the Select Install Type window, select New Install and clickNext.

5. In the Introduction window, review the information and click Next.6. In the Choose IBM SDK Location window, type the directory where IBM Java

SDK 5.0 Service Release 5 is located, or click Choose to browse and select thedirectory. Then click Next.

7. In the Choose Install Folder window, accept the default location or type a filepath to specify where you want to install the product. (Or you can clickChoose to browse and select the location you want.) Then click Next.

8. In the Database Type window, select your Maximo database type (the Maximodatabase is where the Tivoli Integration Composer repository is installed) andclick Next. IBM DB2 is the default.The Database Login Information window is displayed.

9. On the Database Login Information window, type login specifications for thedatabase and click Next.


The Database Login Information window is where you define the parametersfor connecting to the Maximo database. The fields displayed in this windowvary slightly, depending on the type of database you chose in the previousstep. The following table defines the fields that the installation programdisplays for the supported databases.

Table 21. Login specifications for the Maximo database

Field Description

Database Server Name Name of the server on which the Maximo databaseresides

Port Number Port number of the server on which the Maximodatabase resides

Database Name (SID)

or

Database Name

For Oracle databases, this is the session identifier(SID) for the database; that is, the databaseinstance

For SQL Server or IBM databases, this is simplythe name of the database

Database Username Valid user name for signing in to the Maximodatabase

Database/Schema Owner Database or schema owner

Tip: Make note of the values that you specified here. Later, when you launchTivoli Integration Composer, use the values entered in these fields to defineconnection parameters for the Maximo database.

10. On the Update Software Instances window, select one of the following optionsand click Next:

Yes, disable software updatesIf you select this option, when Tivoli Integration Composer importsdata into the Maximo database, Integration Composer inserts ordeletes software records but does not update software records. Thisoption is preferred.

No, don't disable software updatesIf you select this option, when Tivoli Integration Composer importsdata into the Maximo database, Integration Composer updatesexisting software records.

In the Software Class Name field, it is recommended to accept the defaultvalue Software. The Software Class name is used to identify the class that youdo not want to update based on the choice you made. In the Deployed Assetstarget schema, the name is Software.

11. [UNIX only.] In the Choose Internet Browser File window, accept the defaultbrowser or choose another browser to be used for displaying the TivoliIntegration Composer online help, then click Next.

12. On the Preinstallation Summary window, review the installation details. (Ifnecessary, use the Previous buttons to go back and make corrections, and usethe Next buttons to return to this window.) When satisfied with the summarydata, click Install.The Installing Integration Composer progress window displays duringinstallation. When installing is finished, the Installation Complete window isdisplayed.

13. In the Installation Complete window, click Done.


Installing IBM Tivoli Integration Composer on UNIX operatingsystems in console mode

UNIX Use the procedure described here if you have to install Tivoli IntegrationComposer on a UNIX computer in console (command line) mode.

Before you begin

Make sure you have up to 70 MB of free space for the installation directory.

About this task

The Integration Composer files are located on the “Tivoli Asset Management forIT 7.2.2” DVD in the \Install\ITIC directory. Use the setup.bin command fromthe DVD layout to start the installation process:setup.bin ←setup.exe

To install Integration Composer on a UNIX-based operating system, complete thefollowing steps:

Procedure1. Sign on to the server as an administrator (for example, as root).2. Save the binary Integration Composer installation file, setup.bin, on the

server where you intend to install Integration Composer.3. Make sure IBM Java SDK is in your system path.

To add IBM Java SDK to the path, enter the following commands (whereSDK_location is the path for your IBM Java SDK; for example, /opt/java1.5):JAVA_HOME=SDK_locationexport JAVA_HOMEPATH=$JAVA_HOME:$PATHexport PATH

4. Navigate to the location where you saved the setup.bin file.5. Enter the following command to make the binary installation file executable:

chmod +x setup.bin

6. Run the Integration Composer installation program in console mode byentering the following command at the shell prompt:sh ./setup.bin -i console

In console mode, you are prompted to enter information line by line.

Note: If you do not have the prerequisite IBM Java SDK 5.0 Service Release 5currently installed on the Integration Composer server, an error messagedisplays and the installation ends. The error states: No Java Virtual Machinecould be found from your PATH environment variable. You must install aVM prior to running this program. To correct the problem, install IBM JavaSDK 5.0 Service Release 5 on your operating system and run setup.bin again.The IBM Java SDK is provided on the IBM Tivoli Asset Management for IT7.2.2 Launchpad DVD.

7. In the Choose Locale step, type the number of your locale from the list oflocales and press Enter.

8. In the Introduction step, review the Introduction information and press Enter.9. In the Select Install Type step, press Enter to accept the default (New Install).


10. In the Choose Install Folder step, specify where you want to install IntegrationComposer by doing one of the following:v Accept the default location and press Enter.v Type a different file path for the location and press Enter; then type y to

confirm the new location, and press Enter again.11. In the IBM SDK Location step, specify the file path where IBM Java SDK 5.0

Service Release 5 is installed by doing one of the following:v Accept the default location and press Enter.v Type a different file path for the location and press Enter.

12. In the Database Type step, indicate your Maximo database type (the Maximodatabase is where the Integration Composer repository will be installed) bytyping the associated number; then press Enter. The Database LoginInformation step is displayed.This Database Login Information step is where you define the parameters forconnecting to the Maximo database. The fields displayed in this step varyslightly, depending on the type of database you chose in the previous step.The following table defines the fields that the installation program displaysfor the supported databases.

Field Description

Database Server Name Name of the server on which the target databaseresides

Port Number Port number of the server on which the targetdatabase resides

Database Name (SID)

or

Database Name

For Oracle databases, this is the session identifier(SID) for the database; that is, the database instance

For SQL Server or databases provided by IBM, thisis simply the name of the database

Database Username Valid user name for signing in to the targetdatabase

Database/Schema Owner Database or schema owner

13. In the Database Login Information step, type each login specification for thedatabase, one at a time, pressing Enter after each entry to advance to the nextspecification.

Tip: Make note of the values that you specified here. Later, when you launchIntegration Composer, use the values entered in these fields to defineconnection parameters for the target data source.

14. In the Update Software Instances step, type a number to select one of thefollowing options, and press Enter:v Yes, disable software updates

If you select this option, when Integration Composer imports data into thetarget database, Integration Composer inserts or deletes software recordsbut does not update software records. This option is preferred forperformance reasons.

v No, don't disable software updates

If you select this option, when Integration Composer imports data into thetarget database, Integration Composer updates existing software records.


15. In the Software Class Name step, accept the default and press Enter.16. In the Choose Internet Browser File step, accept the default browser, Netscape

(only the Netscape browser is supported on UNIX-based operating systems);then press Enter.

17. In the Preinstallation Summary step, review the installation details and pressEnter to begin installing Integration Composer. The Installing progress bardisplays during installation.When installation is complete, the Installation Complete step is displayed.

18. In the Installation Complete step, press Enter. The installation is done and youare returned to the UNIX command prompt.

Confirming the installationThis section explains how to verify that your new Integration Composerinstallation is working properly.

About this task

To determine if Integration Composer is installed correctly, complete the followingsteps:

Procedure1. Open the Integration Composer application by doing one of the following

things:

Windows From the Windows Start menu, select Start → Programs → IBM Tivoli →Integration Composer → IBM Tivoli Integration Composer

or

from the command line, enter the command: startFusion.bat

UNIX Enter the command: ./startFusion.sh.

2. Sign in to the Integration Composer application using the database (or schemaowner) username and password that you supplied during the installation.

3. From the Help menu in the Integration Composer main window, select About.4. On the About Integration Composer window, check that the number in the

Version field is 7.2.2. If this number is displayed, Integration Composer wassuccessfully installed.

Post-installation tasksThis section provides instructions for verifying that Integration Composer isconfigured correctly.

Verifying the settings in the Integration Composerfusion.properties file

The fusion.properties file is the properties file for Integration Composer. Amongother things, these properties specify Maximo and Integration Composerdatabase-related properties and application properties. This verification task is toensure that, after you have installed Integration Composer, critical propertysettings in the fusion.properties file are correct.


Before you begin

The Integration Composer fusion.properties file is located as follows:

itic_install_dir\data\properties\fusion.properties

About this task

To review the critical settings in your fusion.properties file:

Procedure1. Locate the Integration Composer fusion.properties file in your Integration

Composer installation directory, itic_install_dir.2. In the IBM Tivoli Maximo Database–Related Properties section, verify that the

database schema owner, JDBC driver specification, and JDBC URL specificationare correct. Use the following table as a guide:

Property Description Value

mxe.db.schemaowner Database schemaowner

Enter the appropriate schema for your database; for example, dbo.

mxe.db.driver JDBC driverspecification

This varies depending on the database, for example:

IBM DB2com.ibm.db2.jcc.DB2Driver

Oracle JDBC Thin driver:oracle.jdbc.driver.OracleDriver

i-net Opta driver (SqlServer):com.inet.tds.TdsDriver

mxe.db.url JDBC database URL This varies depending on the database, for example:

IBM DB2jdbc:db2://host_name:host_port/database_name

Oracle JDBC Thin driver:jdbc:oracle:thin:@host_name:host_port:host_SID

i-net Opta driver (SqlServer 7.0 or higher):jdbc:inetdae7:host_name:host_port?database=database_name

mxe.db.user Database user loginname

3. UNIX In the IBM Tivoli Integration Composer (ITIC) Application Propertiessection, users of UNIX-based operating systems should check that themxe.fusion.browser property specifies netscape. For UNIX, Netscape is theonly supported Web browser for Integration Composer:mxe.fusion.browser=netscape

Note: Windows For Windows operating systems, the browser always defaultsto Microsoft Windows Explorer.


Changing the memory allocation in the startFusion file(optional)

The startFusion file, named startFusion.bat in Windows operating systems orstartFusion.sh in UNIX-based operating systems, is the startup file for theIntegration Composer graphical user interface. This verification task is to ensurethat, after you have installed Integration Composer, the memory allocation in thestartFusion file is correct.

Before you begin

This task is optional. You need to perform it only if the Integration Composergraphical user interface does not start as described in “Confirming the installation”on page 244.

About this task

The Integration Composer startFusion file is located in the Windows and UNIXinstallation directories, as follows:

Windows itic_install_dir\bin\startFusion.bat

UNIX itic_install_dir/bin/startfusion.sh

When you install Integration Composer, the installation program assigns 1536megabytes as the default amount of virtual RAM to allocate to the application. But,for example, if your server only has 1GB of physical memory, the 1536M setting willnot work for you.

Procedure

If the Integration Composer graphical user interface does not start, check thememory setting for the start javaw.exe command in the startFusion file, anddecrease memory as necessary.

Example

For example, change -Xmx1536M to -Xmx1024M.

Changing the memory allocation in the commandLine file(optional)

The commandLine file, named commandLine.bat in Windows operating systems orcommandLine.sh in UNIX-based operating systems, is the startup file for theIntegration Composer command-line interface. This verification task is to ensurethat, after you have installed Integration Composer, the memory allocation in thecommandLine file is correct.

Before you begin

This task is optional. You need to perform it only if the Integration Composercommand-line interface does not start.


About this task

The Integration Composer commandLine file is located in the Windows andUNIX-based installation directories, as follows:

Windows itic_install_dir\bin\commandLine.bat

UNIX itic_install_dir/bin/commandLine.sh

When you install Integration Composer, the installation program assigns 1536 MBas the default amount of virtual RAM to allocate to the application. But, forexample, if your server only has 1 GB of physical memory, the 1536M setting willnot work for you.

Procedure

If the Integration Composer command-line interface does not start, check thememory setting for the java command in the commandLine file, and decreasememory as necessary.

Example

For example, change -Xmx1536M to -Xmx1024M.

Uninstalling Integration ComposerThis section provides instructions for removing Integration Composer fromMicrosoft Windows and UNIX-based operating systems.

Uninstalling Integration Composer on Windows operatingsystems

Procedure1. In Microsoft Windows Explorer, go to the uninstall folder, installation_dir\

Uninstall_Integration_Composer, where Integration Composer 7.2.2 wasinstalled.

2. In the uninstall folder, double-click the uninstall file,Uninstall_Integration_Composer.exe. The Integration Composer utility foruninstalling the application displays the Uninstall IBM Tivoli IntegrationComposer window.

3. Click Uninstall. The Uninstall IBM Tivoli Integration Composer progresswindow is displayed as the uninstall utility removes the application.

Note: If necessary, you can click Cancel to stop the uninstallation.When the removal of Integration Composer is finished, the Uninstall Completewindow is displayed.

4. Click Done. The removal of Integration Composer is completed.5. Optional. When the utility removes Integration Composer, one or more files

sometimes remain in the installation directory. (For example, these files mightbe files that someone manually put into the directory, such as mapping files orschema files that the user imported, or they might be log files that IntegrationComposer created.) You can delete these files manually.


Uninstalling IBM Tivoli Integration Composer on UNIXoperating systems

Procedure1. Go to the uninstall folder, itic_install_dir\Uninstall_Integration_Composer,

where Integration Composer 7.2.2 was installed.2. In the uninstall folder, do one of the following options:

v If you installed the Integration Composer using the X Window Systemapplication, type:sh ./Uninstall_IBM_Tivoli_Integration_Composer

v If you installed the Integration Composer using console mode, typesh ./Uninstall_IBM_Tivoli_Integration_Composer -i console

The instructions that follow describe the remaining uninstallation steps usingconsole mode.

3. Press Enter to initiate the command from the previous step. The Uninstallingprogress bar is displayed as the uninstall utility removes the application.When the removal of Integration Composer is finished, you are returned to thecommand prompt.

4. [Optional.] After the utility removes Integration Composer, one or more filessometimes remain in the installation directory. (For example, these files mightbe files that someone manually put into the directory, such as mapping files orschema files that the user imported, or they might be log files that IntegrationComposer created.) You can delete these files manually.


Chapter 13. Enabling IBM Tivoli Asset Management for IT forService Providers

Tivoli Asset Management for IT for Service Providers is an optional, separatelylicensed component that adds functionality to existing applications. The addedfeatures enable service providers to manage the data centers of multiple customers.Strict customer segmentation ensures that the data, IT assets, and process recordsare maintained securely and separately, by customer. Follow these procedures toenable service provider.

Before you begin

Before you begin, you might want to review some of the following information:v Tivoli Asset Management for IT for Service Providers in the “Product overview” in

the information center.v “Process solution packages” on page 194v “Selectable features” on page 201v “Before using the process solution installation programs” on page 199v “Determining which process solution installation program to use” on page 197

Run the Tivoli Asset Management for IT for Service Providers installation from theTivoli Asset Management for IT for Service Providers Launchpad, or from the Startmenu.

About this task

The following steps explain how to enable the service provider key.

Procedure1. Log in as a user with administrative authority.2. Launch the installation program from the Launchpad:

a. Start the Launchpad: On the DVD titled “Tivoli Asset Management for ITfor Service Providers” or “Tivoli Asset Management for IT for InternalService Providers,” navigate to the root directory of the product disk orthe downloaded installation image, and run the launchpad.[exe|sh]command, depending on your operating system.

b. In the Launchpad navigation pane, click Install the Product.c. Click IBM Tivoli Asset Management for IT for Service Providers.

3. In the window that specifies the language, select the appropriate languageand click OK.

4. In the Package Validation Results window, verify that the package informationis correct. Click Next.

5. In the Software License Agreement window, select I accept the terms in thelicense agreement. Click Next.

6. In the Middleware Login Information window, provide a user ID andpassword for the Maximo database (Maximo DB tab), WebSphereadministration user ID and password (WebSphere Admin tab), andWebSphere Application Server remote access user ID and password. ClickNext to continue.


7. In the Package Options window, click Next. You can defer operations relatedto associated packages.

8. In the System Check window, the system service provider package checkprogress is displayed. If the installer encounters a problem, the status messageappears. Click Next when it is ready.

9. In the Pre-Install Summary window, verify that no errors are reported. If noerrors are reported on the System Check Messages tab, continue by pressingNext.You can monitor the deployment process in the Deployment Progress window.

10. In the Package Successfully Deployed window, review the DeploymentMessages tab.The package that you installed might require some additional post-installationsteps.

11. Verify that the installation was successful:a. Open an Internet browser.b. Go to http://host_name:port_number/maximo. Log in.c. Click Help → System Information. Make sure that Tivoli Asset

Management for IT for Service Providers is listed.d. Select Go To → Security → Security Groups , select the maxadmin group,

and on the Applications tab verify that the following applications arepresent in the Security Groups application:v Software Catalogv Deployed Softwarev View Assetv Licenses

If appropriate, you can grant access to the users who need access to theseapplications.

e. Make sure that the following applications are not present in the TivoliAsset Management for IT user interface:v Activities and Tasks (SP)v Asset Link Results (SP)v Asset Reconciliation Results (SP)v Assets (SP)v Comparison Rules (SP)v Computers (SP)v Item Master (SP)v Link Rules (SP)v Network Devices (SP)v Network Printers (SP)v Reconciliation Tasks (SP)v Task Filters (SP)v Work Order Tracking (SP)

f. Sign out by clicking Sign Out.


Related concepts

“Supported operations for the process solution installation programs” on page 198There are multiple operations and functions that are supported by the processsolution installation wizard and process solution command-line interface.Related reference


Chapter 13. Enabling Tivoli Asset Management for IT for Service Providers 251


Chapter 14. Post installation tasks

There are some post installation tasks that must be completed following asuccessful Tivoli Asset Management for IT deployment.1. Provide values to Software Knowledge Base Toolkit cron task in Tivoli Asset

Management for IT user interface and load the software catalog from SoftwareKnowledge Base Toolkit.

2. Provide values to Asset Discovery for z/OS® cron task in Tivoli AssetManagement for IT user interface and load the software catalog from AssetDiscovery for z/OS.

3. Load the Software Knowledge Base Toolkit catalog from Software KnowledgeBase Toolkit into Asset Discovery for Distributed.

4. Define the lauch-in-context to Software Knowledge Base Toolkit from TivoliAsset Management for IT user interface

5. Define the lauch-in-context to Software Knowledge Base Toolkit from AssetDiscovery for Distributed user interface

6. Define the Data sources/Mappings for Asset Discovery for Distributed inIntegration Composer and import discovered data from Asset Discovery forDistributed

7. Define the Data sources/Mappings for Asset Discovery for z/OS in IntegrationComposer and import discovered data from Asset Discovery for z/OS.

The tasks include the following areas:v “Initial data configuration”v Chapter 11, “Installing language packs,” on page 227Related concepts

“Configuring connections to other products” on page 268From IBM Tivoli Asset Management for IT, you can launch IBM Tivoli SoftwareKnowledge Base Toolkit. This launch-in-context feature enables you to viewadditional information about software or to perform related tasks in IBM TivoliSoftware Knowledge Base Toolkit.“Configuring the integration to Software Knowledge Base Toolkit” on page 268After you install IBM Tivoli Asset Management for IT, configure the launch incontext parameters for connecting to IBM Tivoli Software Knowledge Base Toolkitso that you can launch the knowledge base from Asset Management for IT.Related tasks

“Performing post installation tasks for the application server” on page 176During the installation process, the Tivoli Asset Management for IT installationprogram provided you with the option of automatically configuring themiddleware. Use this procedure to perform post installation steps for theapplication server.

Initial data configurationOnce you have successfully installed and configured Tivoli Asset Management forIT components, there are several data configuration tasks you need to completebefore using Tivoli Asset Management for IT.


Signing in using a default user IDUser management is managed through the application server or the directoryserver you have configured to use with Tivoli Asset Management for IT. When firstinstalled, Tivoli Asset Management for IT contains the following default user IDs,which are members of the specified security groups described in this section.

Before you begin

When first installed, Tivoli Asset Management for IT contains the following defaultuser IDs, which are members of the specified security group:

Important: Before you begin this procedure, ensure you have the following usersand groups created:

Table 22. Tivoli Asset Management for IT users and groups

User Groups

wasadmin

maxadmin (maxadminusr for Microsoft ActiveDirectory)

maxadmin

mxintadm maxadmin

maxreg

The default password for each user ID is the same as the User Name (for example,maxadmin is both the user name and default password).

Note: User names and passwords are case sensitive. The default user names andpasswords are lowercase.

About this task

To sign in, complete the following steps:

Procedure1. Open a browser window.2. Navigate to the Tivoli Asset Management for IT log in URL, for example:

http://host_name:port_number/maximo.3. Enter the user name maxadmin (lower case).4. Enter the password maxadmin (lower case), and click Enter. The software

displays an empty start center.Related concepts


Configuring SMTPIf you did not configure SMTP parameters during installation, you need toconfigure them through the product console.


Before you begin

This task must be completed before you begin the tasks described in “Applyingchanges to the database” on page 257.

About this task

To configure SMTP for Tivoli Asset Management for IT, complete the followingsteps.

Procedure1. Login to the console as maxadmin.2. Navigate to Go To → System Configuration → Platform Configuration →

System Properties

3. Using the Filter feature, search for the mail.smtp.host Property Name.4. Expand the mail.smtp.host property and set the Global Value attribute to your

SMTP host.5. Select the mail.smtp.host record checkbox.6. Click the Live Refresh icon in the toolbar.7. From the Live Refresh dialog, click OK.8. Using the Filter feature, search for the mxe.adminEmail Property Name.9. Expand the mxe.adminEmail property and set the Global Value attribute to

your e-mail address.10. Select the mxe.adminEmail record checkbox.11. Click the Live Refresh icon in the toolbar.12. From the Live Refresh dialog, click OK.

Create currency codesYou need to define a currency code for an organization.

About this task

To define a currency code for an organization, complete the following steps:

Procedure1. Open the Currency Code application for Users by selecting Go to → Financial →

Currency Code.2. Click New Row.3. Enter a currency name. For example, USD.4. Click Save.

Create item and company setsYou need to define item and company sets for an organization.

About this task

To define item and company sets for an organization, complete the following steps:

Chapter 14. Post installation tasks 255

Procedure1. Open the Sets application for Users by selecting Goto → Administration → Sets.2. Click New Row.3. Enter a company set name. For example, IT Comps.4. Enter ITEM in the Type field.5. Click New Row.6. Enter an item set name. For example, IT Items.7. Enter COMPANY in the Type field.8. Click Save.

Create an organizationDefine at least one organization for IBM Tivoli Asset Management for IT.

About this task

To define an organization, complete the following steps:

Procedure1. Open the Organizations application by selecting Go To → Administration →

Organizations.2. Click the New Organization icon in the toolbar.3. Enter an organization name in the Organization field. For example, ENGLENA.4. Enter the base currency you defined in the Base Currency 1 field. For

example, USD.5. Enter the item set you defined in the Item Set field. For example, IT Items.6. Enter the company set you defined in the Company Set field. For example,

IT Comps.7. Enter the default item status of PENDING in the Default Item Status field.8. Click Sites tab.9. Click New Row.

10. Enter a site name in the Site field. For example, B901.11. Click Save.

Create a general ledger account componentYou need to create a general ledger account component for IBM Tivoli AssetManagement for IT.

About this task

To create a general ledger account component, complete the following steps:

Procedure1. Open the Database Configuration application by selecting Go to → System

Configuration → Platform Configuration → Database Configuration.2. Select GL Account Configuration from the Select Action drop-down menu.3. Click New Row.4. Enter a component name in the Component field. For example, MYCOMPONENT.5. Enter a numeric length for the component. For example, 5.6. Enter a type for the component. For example, ALN.


7. Click OK.

Applying changes to the databaseWhen you create a general ledger account component, it must be applied to theMaximo database.

About this task

To apply configuration changes to the Maximo database, complete the followingsteps.

Procedure1. Log in to the Maximo console as maxadmin.2. Navigate to Go to → System Configuration → Platform Configuration →

Database Configuration. Every object that must be updated in the Maximodatabase displays a status of To Be Added.

3. On the Select Action drop-down list, select Manage Admin Mode.4. Click Turn Admin Mode ON, and then click OK when prompted. Completing

this task takes several minutes. You can use the Refresh Status button to viewprogress.

5. Once Admin Mode has been successfully enabled, select Apply ConfigurationChanges, which applies the changes to the Maximo database. Make sure To BeChanged status does not appear in the status column for objects listed.

6. Turn Admin Mode OFF.a. Navigate to Go To → System Configuration → Platform Configuration →

Database Configuration.b. From the Select Action drop-down list, select Manage Admin Mode.c. Click Turn Admin Mode OFF, and then click OK when prompted. Failing

to turn off Admin Mode within the application can cause cron tasks to fail.Related tasks

“Create a general ledger account component” on page 256You need to create a general ledger account component for IBM Tivoli AssetManagement for IT.“Create a general ledger account”You need to create a general ledger account for Tivoli Asset Management for IT.

Create a general ledger accountYou need to create a general ledger account for Tivoli Asset Management for IT.

About this task

To create a general ledger account, complete the following steps:

Procedure1. Open the Chart of Accounts application by selecting Goto → Financials →

Chart of Accounts.2. Click the name of your organization to select it. For example, click

ENGLENA.3. Select GL Component Maintenance from the Select Action drop-down menu.4. Click New Row.5. Add a GL Component value and then click OK. For example, 1234.


6. Click New Row.7. Select your General Ledger Account.8. Click Save.9. Open the Organizations application by selecting Goto → Administration →

Organizations.10. Click the organization name you created. For example, ENGLENA.11. From the Clearing Account field, select the General Ledger Account you just

created.12. Select Active.13. Click Save.

Update general ledger component type authorizationYou need to update the general ledger component type authorization for TivoliAsset Management for IT.

About this task

To authorize a Security Group to change a general ledger component type,complete the following steps:

Procedure1. Open the Security Groups application by selecting Go to → Security → Security

Groups.2. Select the Group that is provided authorization (for example, PMSCOA).3. Click the GL Components tab.4. Click the Authorized check box for each GL Component.5. Click Save.

Create default insert siteYou need to create a default insert site for Tivoli Asset Management for IT.

About this task

To create a default insert site, complete the following steps:

Procedure1. Open the Users application by selecting Go to → Security → Users.2. Search for maxadmin and then select it to open the record for maxadmin.3. Enter the site you created earlier (“Create an organization” on page 256) in the

Default Insert Site field. For example, B901.4. Enter the site you created earlier in the Storeroom Site for Self Service

Requisitions field. For example, B901.5. Click Save.6. Open the WebSphere Administrative Console and restart the MXServer

application server.

Results

If you encounter an error message that indicates that the record is being updatedby another user, log out as MAXADMIN and then log back in.


Create a work typeAfter you installed IBM Tivoli Asset Management for IT, you might need tooptionally create a work type.

About this task

To create a work type:

Procedure1. Open the Organizations application by selecting Go to → Administration →

Organizations.2. Search for the organization you created, for example, ENGLENA.3. Click the name of the organization to open the record for that organization.4. Select Work Order Options → Work Type from the Select Action drop-down

menu.5. Click New Row.

What to do next

Depending on your product deployment configuration, select the work type ofyour choice from a drop-down list.

Create a classification structure for IT assetsBefore you can implement IT asset management, you need to define a classificationstructure for IT assets.

About this task

Tivoli Asset Management for IT provides a Classifications application that letsadministrators set up a nested, hierarchical structure in which to classifyinformation about a company's assets. This structure lets you group assets withsimilar or common characteristics into categories or classes. You can use theclassification to retrieve instances of assets that belong to the class. For example,you can specify that the class computers has the following subclasses: notebooks,servers, desktops. If you want to analyze or review data about all notebooks inyour enterprise, you can search for all assets classified as notebooks and retrieveinstances of notebooks.

Best practices content for creating classifications is provided in the Open ProcessAutomation Library.

The steps for creating classifications follow.

Procedure1. On the navigation bar in Tivoli Asset Management for IT, click Go to →

Administration → Classifications.2. In the Classifications application, create classifications as needed. For

instructions about creating classifications and other information related toclassifications, see the integrated online help for the Classifications applicationin the Tivoli Asset Management for IT user interface.


What to do next

After you create an IT asset classification structure, specify the top-level IT assetclassification and the top-level software classification in the Organizationsapplication.

Specify a top-level class for IT assets and softwareTo distinguish IT assets from other types of assets, specify a top-level class for ITassets. Any asset that belongs to the hierarchy of the top-level IT asset class is anIT asset. Also, define a top-level class for software.

Before you begin

Before you can specify top-level classifications for IT assets and software, create aclassification structure for IT assets and software in the Classifications application.

About this task

The class structure ID that is displayed in the System Settings window is a valuestored in the database. If the classifications structure changes such that thetop-level IT asset class no longer exists at the same place in the hierarchy, the ITAsset Class Structure ID field will remain populated, but the IT Asset Top-LevelClass field will be blank or show the wrong class. Consequently, if changes aremade to the database, and the classification is moved within the classificationstructure, or deleted and re-added, repeat this procedure to update the classstructure ID.

The steps required to specify a top-level classification for IT assets and softwarefollow.

Procedure1. On the navigation bar in Tivoli Asset Management for IT, click Go to →

Administration → Organizations.2. From the Select Action menu in the Organizations application, select System

Settings.3. To specify the top-level IT asset, complete the following steps:

a. In the IT Options section in the Systems Settings window, in the IT AssetTop-Level Class field, click the Detail Menu and select Classify. Ifnecessary, you can select Clear Classification to clear the value displayedand then click Classify.

b. In the Classify window, select the top-level asset class for IT assets byclicking the blue square to the left of the classification name. Theapplication closes the Classify dialog box and populates the IT AssetTop-Level Class field.

4. To specify the top-level software classification, complete the following steps:a. In the IT Options section in the Systems Settings window, in the IT

Software Top-Level Class field, click the Detail Menu and select Classify.b. In the Classify window, select the top-level asset class for IT assets by

clicking the blue square to the left of the classification name. Theapplication closes the Classify dialog box and populates the IT SoftwareTop-Level Class field.

5. Click OK to save the settings and close the dialog box.


Signing out and signing inWhen you change a security group that your user ID is a member of, sign out andsign in again in order to see the changes.

Example

For example, even though you have granted the MAXADMIN group permission tocreate start center templates, the actions are not visible until you sign in again.1. Sign out as MAXADMIN.2. Sign in as MAXADMIN.Related concepts

“Planning for security” on page 19Planning for security includes choosing a security option, deciding which users canwork with each application in IBM Tivoli Asset Management for IT, and optionallywhich users can work with which assets.Related tasks

“Signing in using a default user ID” on page 254User management is managed through the application server or the directoryserver you have configured to use with Tivoli Asset Management for IT. When firstinstalled, Tivoli Asset Management for IT contains the following default user IDs,which are members of the specified security groups described in this section.

Manually configuring directory servicesYou can manually configure a IBM Tivoli Asset Management for IT cron task toschedule synchronization of users and groups between a directory server andTivoli Asset Management for IT system.

About this task

VMMSYNC is the cron task that schedules the synchronization between Tivoli AssetManagement for IT and the directory server. This cron task is set up automaticallyduring installation. The manual procedure is required only if you need to changethe existing configuration of the cron task.

To configure the synchronization schedule between the directory server and TivoliAsset Management for IT, complete the following steps:

Procedure1. Open a Web browser and point to http://host_name/maximo.2. Log in to Tivoli Asset Management for IT using the maxadmin user ID.3. From the product interface, navigate to Go To → System Configuration →

Platform Configuration → Cron Task Setup.4. Type VMM in the Cron Task field, and press Enter.5. Locate the VMMSYNC cron task, and click it.6. Configure the following values:

Active?Enable the Active? option by selecting the check box.

CredentialPassword for wasadmin in LDAP


GroupMappingThis field contains XML mapping files that map LDAP object attributesto database repository table columns. Change the following objectentries to use the organizational unit ou value you defined for yourorganization when setting up the middleware.

BasednIt defines the LDAP subtree under which the Virtual MemberManager cron task searches for group objects.

For example, ou=groups,ou=SWG,o=IBM,c=US.

Filter It is the Virtual Member Manager object class that the serviceuses to search for group objects in LDAP.Group

GroupSearchAttributeThis value is the LDAP group object attribute used to search for groupsunder the configured directory subtree. For example, cn

PrincipalIt is the user required by the CronTask application to connect to thelocal Virtual Member Manager service. This value can be any directoryserver administrative user that has authorization to connect to the localVirtual Member Manager service. Customize it to use the organizationalunit ou and domain name dc values you defined for your organizationwhen setting up Tivoli Asset Management for IT middleware. Forexample, cn=wasadmin,ou=Users,ou=SWG,dc=itsm,dc=com

SynchAdapterpsdi.security.vmm.DefaultVMMSyncAdapter

This value is the Java class that writes LDAP data to the database.

SynchClasspsdi.security.vmm.VMMSynchronizer

This value is the Java class that connects to the Virtual MemberManager local service to search for required objects.

UserMappingThis field contains XML mapping files that map LDAP object attributesto database repository table columns. Change the following objectentries to use the organizational unit ou value you defined for yourorganization when setting up the middleware.<basedn>ou=Users,ou=SWG,dc=itsm,dc=com</basedn>

BasednIt defines the LDAP subtree under which the Virtual MemberManager cron task searches for user objects.

For example, ou=users,ou=SWG,o=IBM,c=US.

Filter PersonAccount

This is the Virtual Member Manager object class that the serviceuses to search for user objects in LDAP.

UserSearchAttribute

This value is the LDAP user object attribute used to search for usersunder configured directory subtree.

For example, cn.


Click the arrow located in the header of the Cron Task Parameters table to viewall parameters.

7. Click the Save icon.

Results

By default, the cron task performs its task every 5 minutes. Change the Schedulefield of the cron task if you want to change the interval. The updated parametersare used at the next scheduled synchronization.

Before working with BIRT reportsBefore running any reports, you need to set up manually themxe.report.birt.tempfolder in JVM system Properties in the BIRT report engine.

Before you begin

The mxe.report.birt.tempfolder property specifies the location of a temporaryfolder on the reporting server for BIRT.

About this task

To configure BIRT, set up JVM System Properties mxe.report.birt.tempfolder.

Procedure1. Log in to Integrated Solutions Console.2. Go to Servers → Application servers.3. From the right panel, click the server name where you have deployed Tivoli

Asset Management for IT.4. Go to Process Definition under Server Infrastructure.5. Click Java Virtual Machine under Additional Properties.6. Add -Dmxe.report.birt.tempfolder=c:\tempReport\BIRT-TEMP to Generic JVM

Argument, and then click Save.7. Restart the server.

Tuning IBM DB2This section details how to tune IBM DB2 after you have completed installation.

About this task

IBM Tivoli Asset Management for IT provides scripts that can be used to tune DB2.The use of these scripts is strictly optional and contain configuration parametersthat might not be ideal for all environments. However, you can modify thesescripts to suit your particular configuration and workload. Before modifying thesescripts, make a backup copy of the original script.

The following database configuration parameters are set:v DFT_QUERYOPT 2v LOCKLIST15000 DEFERREDv MAXLOCKS 60v PCKCACHESZ 12600v DBHEAP 2000


v CATALOGCACHE_SZ 800v LOGBUFSZ 256v UTIL_HEAP_SZ10000v APP_CTL_HEAP_SZ16384 DEFERREDv STMTHEAP 16384v APPLHEAPSZ 2048v STAT_HEAP_SZ 8196v CHNGPGS_THRESH 40v MAXFILOP 200v LOGFILSIZ 2048 DEFERREDv LOGPRIMARY 10v LOGSECOND 15 DEFERRED

The following database manager configuration parameters are also set:v PRIV_MEM_THRESH 32767v NUMDB 2

The DB2 tuning scripts are found in the tamit_install_dir/scripts/databasedirectory, and must be run by a user with database administration authority.

Windows Windowsdb2tuning.cmd [ db_name [ db_instance ] ]

UNIX UNIXdb2tuning.sh [ db_name [ db_instance ] ]

If the db_name is not provided, the default MAXDB71 is used.

If the db_name is not provided, the default ctginst1 is used. If a database instanceother than the default is needed, the db_name must also be provided.


Related tasks

Reusing DB2If you have an existing IBM DB2 installation that you would like to reuse for IBMTivoli Asset Management for IT, run the Tivoli middleware installer on the system.The middleware installer identifies instances of middleware that exist on thesystem that are compatible with Tivoli Asset Management for IT, and it configuresthe existing instance for use with the product.Manually configuring DB2 9.xFor better performance, you might need to manually configure IBM DB2 9.x beforerunning the IBM Tivoli Asset Management for IT installer to set the preferableenvironment on different operating systems.Manually configuring DB2 8.2This section contains instructions for manually configuring DB2 8.2 servers for useby IBM Tivoli Asset Management for IT. Tivoli Asset Management for IT supportsIBM DB2 8.2 only when manually configured.

Completing integration framework registrationIntegration framework registration is required for process managers that includeintegration with other software. If you have chosen the option of deployingapplication files manually later during the IBM Tivoli Asset Management for ITinstallation process, you need to manually perform integration frameworkregistration after manually deploying the maximo EAR file.

Before you begin

The syntax used with the integration framework registration command includesthe following parameters:

was_dmgrThe fully-qualified host name of your WebSphere Application ServerNetwork Deployment manager server

port_numberThe HTTP port on the WebSphere Application Server NetworkDeployment manager server

MAXUSERThe Maximo user

MAXPASSWDThe Maximo user password

CELL_NAMEThe WebSphere Application Server Network Deployment cell name (bydefault this value is ctgCell01)

About this task

To manually perform integration framework registration, complete the followingsteps:

Procedure1. Open a command prompt on the administrative system.2. Run the following command:

tamit_install_dir\jacl\solutions\meareg was_dmgr port_number MAXUSER MAXPASSWD none none ./installedApps/CELL_NAME/MAXIMO.ear/meaweb.war/WEB-INF/


Generating xml request pagesPerform this task after you installed Tivoli Asset Management for IT and before yourun request pages. This procedure needs to be performed for every language thatis enabled on your system.

Before you begin

When multiple languages are enabled in Maximo applications, request pages haveto be generated in each of the enabled languages.

Procedure1. Log in as a maxadmin user.2. From the Start menu, go to Administrator → Reporting → Report

Administration

3. Review all rows in the list view then in the bottom right corner click GenerateRequest Page button. Wait a couple of minutes for the process to complete.

Related concepts

“Planning language support” on page 21Language support refers to the languages you plan to support in the Tivoli AssetManagement for IT user interface.

Synchronizing dataThe scheduled synchronization of data that occurs between LDAP repositories andIBM Tivoli Asset Management for IT is governed by the federated repositoriesmanaged by Virtual Member Manager in WebSphere Application Server, and theTivoli Asset Management for IT Virtual Member Manager cron task.

About this task

For specific information about configuring the VMMSYNC cron task for MicrosoftActive Directory, refer to “Manually configuring directory services” on page 261.

To configure the synchronization schedule between LDAP repositories and TivoliAsset Management for IT, complete the following steps:

Procedure1. Open a Web browser and point to http://host_name:9081/maximo

2. Log in to product using the maxadmin user ID.3. From the Tivoli Asset Management for IT interface, navigate to Go To → System

Configuration → Platform Configuration → Cron Task Setup.4. Type VMM in the Cron Task field, and press Enter.5. Locate the VMMSYNC cron task, and click it.6. Ensure that the following values are used for each field:

Principalcn=wasadmin,ou=users,ou=SWG,o=IBM,c=US

This is the user required by the CronTask application to connect to thelocal Virtual Member Manager service. This value can be anyWebSphere Application Server administrative user that hasauthorization to connect to the local Virtual Member Manager service.


CredentialIt is the password used for the principal account. In this case, enter thepassword for wasadmin.

GroupSearchAttributeThis value is the LDAP group object attribute used to search for groupsunder the configured directory subtree.cn

UserSearchAttributeThis value is the LDAP user object attribute used to search for usersunder configured directory subtree.Uid

SynchAdapterThis value is the Java class that writes LDAP data to the database.psdi.security.vmm.DefaultVMMSyncAdapter

SynchClassThis value is the Java class that connects to the Virtual MemberManager local service to search for required objects.psdi.security.vmm.VMMSynchronizer

Group MappingThis field contains XML mapping files that map LDAP object attributesto database repository table columns. Change the following objectentries:

BasednIt defines the LDAP subtree under which the Virtual MemberManager cron task searches for group objects.ou=groups,ou=SWG,o=IBM,c=US

Filter It is the Virtual Member Manager object class that the serviceuses to search for group objects in LDAP.Group

User MappingThis field contains XML mapping files that map LDAP object attributesto database repository table columns. Change the following objectentries:

BasednIt defines the LDAP subtree under which the Virtual MemberManager cron task searches for user objects.ou=users,ou=SWG,o=IBM,c=US

Filter It is the Virtual Member Manager object class that the serviceuses to search for user objects in LDAP.PersonAccount

7. Set the task to active.

What to do next

By default, the cron task performs its task every 5 minutes. Change the Schedulefield of the cron task if you want to change the interval.


Configuring connections to other productsFrom IBM Tivoli Asset Management for IT, you can launch IBM Tivoli SoftwareKnowledge Base Toolkit. This launch-in-context feature enables you to viewadditional information about software or to perform related tasks in IBM TivoliSoftware Knowledge Base Toolkit.

To enable launch-in-context to IBM Tivoli Software Knowledge Base Toolkit,specify the parameters for connecting to this product.

Configuring the integration to Software Knowledge BaseToolkit

After you install IBM Tivoli Asset Management for IT, configure the launch incontext parameters for connecting to IBM Tivoli Software Knowledge Base Toolkitso that you can launch the knowledge base from Asset Management for IT.

From the Software Catalog application in Asset Management for IT, you can openSoftware Knowledge Base Toolkit if you want to view additional details aboutsoftware. As part of the configuration tasks for IT asset management integration,you must specify the parameters for connecting to Software Knowledge BaseToolkit. You must specify the host name and port number of the server on whichSoftware Knowledge Base Toolkit is installed.

You can define the connection parameters in the Launch in Context application inAsset Management for IT. The Launch in Context application contains a predefinedlaunch-in-context entry, SWKBT EDIT GUID, provided for the Software KnowledgeBase Toolkit integration.

For more information about defining launch-in-context parameters, see the"Defining launch in context parameters for Software Knowledge Base Toolkit "topic in the "Integrating IT asset management data" section of the informationcenter.


Chapter 15. Installation properties

Installation properties are recorded in properties files during a deployment and areused by future install-related actions.

Table 23 contains installation properties that are found in the install.propertiesand maximo.properties files. The table lists the complete set of properties that canbe found in these two properties files. Your installation properties will be a subsetof the properties in the table, based on the particular deployment options youchose.

If updates are made between the time of the initial product deployment and asubsequent installation action, properties must be updated in these files. Changesinclude changes to passwords or host names, for example. Subsequent installationactions refer to applying a fix pack or performing an upgrade. Refer to “Updatingenvironment data” on page 282 for more information.

Table 23. Installation properties

Category Property Definition

MAXIMO Properties Maximo.InstallLocation Install location of the Maximo directory.

For example, C:\\IBM\\SMP\\maximo

mxe.db.user Database user that the server uses to attachto the database server.

For example, maximo

mxe.db.schemaowner Owner of the database schema.

For example, maximo

mxe.db.password Password for the database user name.

mail.smtp.host SMTP host server.

mxe.workflow.admin The e-mail account of the workflowadministrator.

mxe.adminEmail Valid e-mail address used by workflows tocommunicate with workflow participants.

mxe.name Name to bind the MXServer server object toin the RMI registry.

For example, mxserver.

mxe.hostname Name of the computer and port hostingMXServer

mxe.rmi.port RMI communication port. If set at zero, RMIuses any available port. You can selectanother available port number.


Table 23. Installation properties (continued)


mxe.registry.port The port number used to bind RMI/JRMPcommunications.

For example, 13400.

The RMI registry is started by the firstinstance of the Maximo application to run. AIBM WebSphere Application Server NetworkDeployment environment could havemultiple instances of the product applicationrunning at one time. This registrycoordinates these instances. There is a singlecentral RMI registry server. This port is theport available for the other applicationinstances to communicate with the centralserver.

mxe.allowLocalObjects Set to true in production environments, toimprove system performance. Set to false fordevelopment work, or for customapplications.

The default is false.

mxe.useAppServerSecurity Indicates whether to use LDAP or nativeauthentication. Setting this value to 1indicates you are using LDAP for security.

mxe.MLCacheLazyLoad By default, the multi-language metadatacache loads one object at a time. Set this flagto 1 to load all objects simultaneously for onelanguage.

mxe.UserLicenseKey The product enabler (license key) is usedduring installation. If the product enablerchanges this value must be updated.

mxe.adminuserid The administrative user. Used by the serverfor administrative tasks and to run crontasks. This user must have access to all Sitesin the system.

mxe.adminuserloginid Defines the default login user ID for theproduct application.

The default value is maxadmin.

mxe.adminPasswd The password for the mxe.adminuserloginiduser.

mxe.system.reguser Self registration user. This user is responsiblefor the process by which users can createtheir own accounts.

The default value is maxreg.

mxe.system.regpassword User registration login password. Thispassword is the password for the user listedfor mxe.system.reguser.




mxe.email.charset The character set for e-mail notifications sentfrom the product.

When this property is defined, it is thecharset that is used to encode the subject andmessage when an e-mail notification is sent.

mxe.reorder.previewtimeout The reorder preview time out period (inminutes), which is set to a value like the Webserver session time out.

The default value is 30 minutes.

mxe.security.provider The security provider is obtained from thepolicy file, which is normallycom.sun.crypto.provider.SunJCE.

To use a different provider, you can specify avalue for this parameter.

mxe.mbocount Displays the number of business objectscreated by the server.

The default is 1. You can change the value to0 which disables this feature.

mxe.esig.defaultuserid Set this flag to true if you want theSignature login dialog to default to the loginID.

The default value is true.

maximo.min.required.db.version Defines what the minimum level of databaseis required for an upgrade. An examplevalue would be 7100.

mxe.encrypted Property used by the application todetermine if property files are encrypted.

This value is set to true if the file isencrypted.

mxe.LDAPUserMgmt Indicates whether LDAP owns usermanagement whenmxe.userAppServerSecurity = 1.

The default value is 1.

Tivoli AssetManagement for IT-specific properties

CCMDB.InstallLocation Product install location.

For example, C:\\IBM\\SMP.

CCMDB.JREInstallLocation JRE install location.

For example, C:\\IBM\\SMP\\JRE.

CCMDB.SDKInstallLocation SDK install location.

For example, C:\\IBM\\SMP\\SDK.

CCMDB.PMP This property is no longer used.

CCMDB.Locale The locale setting of the administrativeworkstation system.

For example, en.

Chapter 15. Installation properties 271



CCMDB.BaseLanguage Base language that was set for the product.

For example, en.

CCMDB.AdditionalLanguages Additional languages installed for theproduct.

CCMDB.DeploySampleData Binary value that determines whether sampledata is to be loaded during the installation.

For example, false.

CCMDB.UserShortcuts Location of the menu of shortcut items forthe process solution installer and the productconsole.

CCMDB.InstallType Type of installation, which includes fix pack,upgrade, or new installation.

For example, Install.

CCMDB.DeployEar Binary value that indicates if EAR filesdeploy during the installation based uponchoices the user made in the installationprogram wizard.

For example, true.

Base ServicesProperties

BASE.DeployOptionalContent Binary value that indicates if optionalcontent deployed during the installationbased upon choices the user made in theinstallation program wizard.

For example, true.

BASE.DeployOptionalContentSet Indicates whether you selected to deployoptional content during the initial upgrade.This value, once set, is a fixed value andcannot be changed. This value will be usedfor all future upgrades and fix packs.

BASE.VersionUpgradingFrom The previous version of base services thatwas installed.

WebSphere ApplicationServer NetworkDeployment ThinClient specificProperties

WAS.ThinClientInstallLocation WebSphere Application Server NetworkDeployment thin client install location.

For example, C:\\IBM\\SMP\\WASClient.

WAS.SOAPConnectorPort SOAP port of the WebSphere ApplicationServer Network Deployment deploymentmanager.

For example, 8879.

WAS.ThinClientFullyAutomatedConfig Binary value that indicates if the installationprogram downloads the keystore from theWebSphere Application Server NetworkDeployment deployment manager.

If this value is set to false, the user has tocopy it manually.




WAS.ThinClientLocalKeystore Location of the keystore file.

For example, C:\\ibm\\WebSphere\\AppServer\\profiles\\ctgDmgr02\\etc\\trust.p12.

WAS.Scripts.Location Location of scripts used by the installationprogram.

For example, C:\\IBM\\SMP

WebSphere ApplicationServer NetworkDeployment RMI port

WAS.RMIConnectorPort RMI port on the WebSphere ApplicationServer Network Deployment deploymentmanager which is used if SOAP is not beingused.

Needed when using IPV6

WebSphere ApplicationServer NetworkDeployment specificproperties

WAS.AutomateConfig Binary value that indicates if WebSphereApplication Server Network Deploymentwas automatically configured by theinstallation program.

A value of false indicates that the usermanually configured the WebSphereApplication Server Network Deploymentserver before running the installationprogram.

WAS.InstallLocation Installation location for WebSphereApplication Server Network Deployment.

For example, C:\\IBM\\WebSphere\\AppServer

WAS.DeploymentManagerHostName The host name of the WebSphere ApplicationServer Network Deployment deploymentmanager.

WAS.CellName WebSphere Application Server NetworkDeployment CELL name.

For example, ctgCell01

WAS.DeploymentManagerProfileName WebSphere Application Server NetworkDeployment profile name.

For example, ctgDmgr01

WAS.DeploymentManagerProfileRoot Location of the WebSphere ApplicationServer Network Deployment profile.

For example, C:/IBM/WebSphere/AppServer/profiles/ctgDmgr01

WAS.ServerProfileName WebSphere Application Server NetworkDeployment application server profile name.

For example, ctgAppSrv01

WAS.NodeName WebSphere Application Server NetworkDeployment node name.

For example, ctgNode01




WAS.ApplicationServerName WebSphere Application Server NetworkDeployment application server name.

For example, MXServer

WAS.ClusterName WebSphere Application Server NetworkDeployment cluster name.

For example, MAXIMOCLUSTER.

This property is designated for future use.

WAS.AdminUserName WebSphere Application Server NetworkDeployment administrator name.

For example, wasadmin

WAS.AdminPassword WebSphere Application Server NetworkDeployment administrator password.

WAS.RemoteAccessUserName WebSphere Application Server NetworkDeployment deployment manager systemuser ID used for tasks such as copying ISCWAR files and fetching the keystore.

WAS.RemoteAccessPassword WebSphere Application Server NetworkDeployment deployment manager systemuser password.

WAS.VirtualHost Name of the WebSphere Application ServerNetwork Deployment virtual host.

For example, maximo_host.

WAS.VirtualHostPort Port for virtual host for listening for HTTPserver.

For example, 80.

WAS.WebServerHostName The host name where the HTTP server islocated.

WAS.AppServerJvmHeapMin Minimum heap size setting for theapplication server JVM.

For example, 512.

WAS.AppServerJvmHeapMax Maximum heap size setting for theapplication server JVM.

For example, 1024.

WAS.SibName Name of the service integration bus.

For example, intjmsbus.

WAS.SibHiMsg Service integration bus high message count.

For example, 500000.

WAS.WebServerName Name of the WebSphere Application ServerNetwork Deployment web server. Used tomanage HTTP server from within WebSphereApplication Server Network Deployment.

For example, webserver1.




WAS.SibPersistMessages Binary value that indicates if serviceintegration bus messages are persisted ineither the product database or a local derbydatabase.

A value of true indicates that the messagesare persisted.

WAS.SibDSName Service integration bus data source namecreated to access the service integration buspersistence store.

For example, intjmsds.

WAS.SibDBType Database type where the service integrationbus messages are being stored.

For example, DB2.

WAS.SibDBName Name of the service integration busmessages database.

WAS.SibDBInstance Instance name of the service integration busdatabase.

WAS.SibDBServerName Server name of the system hosting theservice integration bus message database.

WAS.SibDBServerPort Database server port for the databasecontaining the service integration busmessages.

For example, 50005.

WAS.SibDBUserName The user ID used to access the persistencedata store database for service integrationbus messages.

WAS.SibDBUserPass Password for user ID named inWAS.SibDBUserName.

WAS.SibDBInstallDir Where the service integration bus database isinstalled.

For example, C:\Program Files\IBM\SQLLIB.

WAS.SibDbFencedUser Fenced user ID for the service integrationbus database. This property is only used fordatabases hosted on UNIX systems.

For example, db2fenc1.

WAS.SibDbInstanceAdminUser Instance owner for the service integrationbus database.

WAS.SibDbInstanceAdminPassword Password for the instance owner of theservice integration bus database.

WAS.SibDbRemoteAccessUser Database server system user used toconfigure the service integration busremotely.

WAS.SibDbRemoteAccessPassword Password for user ID named inWAS.SibDbRemoteAccessUser.

WAS.UseDefaultVmmSchema This property is no longer used.




WAS.VmmFullyAutomatedConfig Binary value that indicates if the installationprogram creates users and directories.

For example, true.

WAS.VmmUserRDN LDAP tree where users are stored.

For example, ou=users,ou=SWG,o=IBM, c=US.

WAS.VmmGroupRDN LDAP tree where groups are stored.

For example, ou=groups,ou=SWG,o=IBM, c=US.

LDAP Server-specificProperties

LDAP.AutomateConfig Binary value that indicates whether theinstallation program automatically configuresthe directory server.

For example, true.

LDAP.Vendor The type of LDAP repository.

LDAP.ServerHostName The host name of the LDAP system host.

LDAP.AdminDN Administrator distinguished name.

For example, cn=root.

LDAP.AdminPassword Password for user ID named inLDAP.AdminDN.

LDAP.ServerPort Port listening for connection requests.

For example, 389.

LDAP.InstallLocation Install location of the directory server.

For example, C:\ProgramFiles\IBM\LDAP\V6.2.

Database-specificProperties

Database.AutomateConfig Binary value that indicates whether theinstallation program automatically configuresthe database.

For example, true.

Database.Vendor Database type.

For example, DB2.

Database.RemoteAccessUserName Database server system user ID that is usedfor configure the database remotely.

Database.RemoteAccessPassword Password for user ID named inDatabase.RemoteAccessUserName.

mxe.db.driver Java class name of the JDBC driver.

For example, com.ibm.db2.jcc.DB2Driver.

mxe.db.url JDBC URL of the database.

For example, jdbc:db2://computer_name.my_domain.com:50005/maxdb71.




mxe.db.initialConnections Number of database connections to createwhen the application server is started.

For example, 8.

mxe.db.maxFreeConnections Maximum number of free databaseconnections available in the connection pool.

For example, 8.

mxe.db.minFreeConnections Minimum number of free databaseconnections needed in the connection pool inorder for more connections to be allocated.

For example, 5.

mxe.db.newConnectionCount Number of new connections to be createdwhen the minimum free connections areavailable in the connection pool.

For example, 3.

mxe.db.transaction_isolation The system install sets the value to:TRANSACTION_READ_COMMITTED.

This value cannot be modified.

mxe.db.format.upper This value defines the database uppercasefunction for the system.


mxe.db.autocommit This value sets the autocommit mode usedfor the Write connections. Can be either trueor false. The default is false.


mxe.db.systemdateformat System date format.

For IBM DB2, the value is currenttimestamp.

For Oracle, the value is sysdate, and thedefault value cannot be edited.

For SQL Server, the value is getdate().

mxe.db.format.nullvalue The database-specific format of the nullvalue function.

For IBM DB2 the value is COALESCE, and thedefault value cannot be edited.

The value for Oracle is NVL, and the defaultvalue cannot be edited.

The value for SQL Server must be set toISNULL.




mxe.db.sqlserverPrefetchRows Setting to reduce lock contention.

Optimal setting is 200 rows. Setting a valuelarger than 500 can degrade performance.

The default value is 0.

This value is only valid for Microsoft SQLServer.

mxe.db.logSQLTimeLimit The system logs the SQL statements that takelonger than the specified time limit. The timeis measured in milliseconds (thousandths ofa second).

The default value is 1000 milliseconds.

To disable, edit the file to read:mxe.db.logSQLTimeLimit=0.

mxe.db.fetchResultLogLimit When this setting is enabled, a stack trace isprinted in the log. Entries include everybusiness object set that fetches beyond theset limit of rows. The stack trace log is alsorepeated for every multiple of such fetches.

The default is 200 rows.

To disable, edit the file to read:mxe.db.fetchResultLogLimit=0.

Oracle DB Properties Database.Oracle.InstanceName Oracle instance name.

Database.Oracle.SoftwareOwner Owner of the software installation.

For example, oracle.

Database.Oracle.SoftwareOwnerPassword Password for the user ID listed inDatabase.Oracle.SoftwareOwner.

Database.Oracle.InstallLocation Oracle installation location. For example,/opt/app/oracle/product/10.2.0/db_1.

Database.Oracle.DataTablespaceName Oracle table space name for the productdatabase.

For example, maxdata.

Database.Oracle.InstanceLocation Oracle instance location.

For example, /opt/app/oracle/product/10.2.0/db_1.

Database.Oracle.DataTablespaceLocation Location of Oracle database table space.

Database.Oracle.DataTablespaceSize Tablespace size, measured in MB.

For example, 1000.

Database.Oracle.DataTablespaceMaxSize Maximum size of the table space, measuredin MB.

For example, 8000.




Database.Oracle.TempTablespaceName Temporary table space name.

For example, maxtemp.

Database.Oracle.TempTablespaceLocation Location of temporary table space.

Database.Oracle.TempTablespaceSize Temporary table space size, measured in MB.

For example, 1000.

Database.Oracle.TempTablespaceMaxSize Maximum size of the temporary table space,measured in MB.

For example, 8000.

Database.Oracle.IndexTablespaceName Index table space name.


Database.Oracle.IndexTablespaceLocation Location of index table space.

Database.Oracle.IndexTablespaceSize Index table space size, measured in MB.

For example, 1000.

Database.Oracle.IndexTablespaceMaxSize Maximum size of the index table space,measured in MB.

For example, 8000.


Database.Oracle.SchemaPassword Password for user listed inmxe.db.schemaowner.

Database.Oracle.ServerHostName The host name of the Oracle server.

Database.Oracle.ServerPort Port number used by Oracle.

For example, 1521.

Database.DBAUserName Oracle DBA user name.

For example, sys.

Database.DBAPassword Password for user ID listed forDatabase.DBAUserName.

IBM DB2 Properties mxe.db.schemaowner Owner of the database schema.

Database.DB2.ServerHostName The host name of the DB2 server.

For example, computer_name.my_domain.com.

Database.DB2.ServerPort Database server port.

For example, 50005.

Database.DB2.InstanceName Name of the database instance.

For example, ctginst1.

Database.DB2.DatabaseName Name of the database.

For example, maxdb71.

Database.DB2.InstallLocation Install location of the database.

For example, /opt/IBM/db2/V9.7




Database.DB2.LogFileSize Set the size for transaction logs.

For example, 4096

Database.DB2.AppCtlHeapSize Application control heap size.

For example, 1024

Database.DB2.ApplHeapSize Application heap size.

For example, 1024

Database.DB2.LockListSize Size allocated to the lock list.

For example, 30000

Database.DB2.LogSecond Number of secondary log files allowed.

For example, 4

Database.DB2.ServiceUser The user ID used to autostart.

Database.DB2.ServicePassword Password for Database.DB2.ServiceUser.

Database.DB2.PageSize Page size setting.

Measured in kB. For example, 32

Database.DB2.ExtentSize Number of pages per extent (group ofpages).

For example, 32

Database.DB2.FencedUser System user used as the fenced user ID forDB2 on UNIX systems.

For example, db2fenc1.

Database.DB2.AuthType Method DB2 uses to authenticate users.

For example, server.

Database.DB2.DataTablespaceName DB2 table space name for the productdatabase.


Database.DB2.BufferPoolName DB2 buffer pool name.

For example, MAXBUFPOOL.

Database.DB2.BufferPoolLocation Location of the buffer pool.

Database.DB2.BufferPoolSize Size of the buffer pool.

For example, 32

Database.DB2.DataTablespaceLocation Location of DB2 database table space.

Database.DB2.DataTablespaceSize table space size, measured in MB.

For example, 1000.

Database.DB2.DataTablespaceMaxSize Maximum size of the table space, measuredin MB.

For example, 8000.




Database.DB2.TempTablespaceName Temporary table space name.

For example, maxtemp.

Database.DB2.TempTablespaceLocation Location of temporary table space.

Database.DB2.TempTablespaceSize Temporary table space size, measured in MB.

For example, 1000.

Database.DB2.TempTablespaceMaxSize Maximum size of the table space, measuredin MB.

For example, 8000.

Database.DB2.IndexTablespaceName Index table space name.


Database.DB2.IndexTablespaceLocation Location of index table space.

Database.DB2.IndexTablespaceSize Temporary table space size, measured in MB.

For example, 1000.

Database.DB2.IndexTablespaceMaxSize Maximum size of the index table space,measured in MB.

For example, 8000.

Database.DB2.InstanceAdminUserName Administrative user or the database instance.

Database.DB2.InstanceAdminPassword Password for the user ID specified forDatabase.DB2.InstanceAdminUserName

Microsoft SQL ServerProperties


Database.SQL.DatabaseName Name of the database.

For example, maxdb71.

Database.SQL.InstallLocation SQL Server installation location(sql_install_dir). For example:

C:\\Program Files\\Microsoft SQL Server\\90

Database.SQL.DataFileLocation Location for database data file.

Database.SQL.DataFileName A way to specify the name of the data fileused for the database. For example,maxdb71_dat.

Database.SQL.DataFileMaxSize Maximum size for data file for database.

Database.SQL.DataFileSize Initial size for data file for database

Database.SQL.LogFileName A way to specify the name for the databasetransaction log file. For example,maxdb71_log.

Database.SQL.LogFileSize SQL Server database transaction log file size.

Database.SQL.DataFilegroupName Database logical name file group. Forexample, PRIMARY.

Database.SQL.ServerHostName Host name of the database server. Forexample, host_name.my_domain.com.

Database.SQL.ServerPort Database server port. For example, 1433.




Database.SQL.InstanceAdminUserName Administrative user for the SQL Serverinstance. Used during install for creatingdatabase, creating database user, andmodifying the database

Database.SQL.InstanceAdminPassword Administrative users password.

Application ServerType Properties

ApplicationServer.Vendor Indicates which application server waschosen during installation. For example,WebSphere.

Updating environment dataWhen you install a fix pack or otherwise upgrade an existing IBM ServiceManagement product, the installation program uses values recorded from theprevious deployment. These values are stored on the administrative system in theinstall.properties and maximo.properties files. If you have made anyenvironmental changes to any of the deployment systems, they must be recordedin the install.properties and maximo.properties files. Example environmentalchanges include changing a host name or updating a password.

Before you begin

When the product installation program is run for an upgrade task, it uses valuesfound in the install.properties and maximo.properties files. During the upgradeoperation, the installation program uses the credentials found in the propertiesfiles. If they are used successfully, you are not prompted to provide them again. Ifthe installation program cannot log in to a system using the credentials found inthe properties files, you need to supply the correct information. These values arewritten to the appropriate property file.

This method of updating credential information in property files has one exception.Database connection and credential information must always be current before youattempt an upgrade operation. Database connection information and credentials arestored in the maximo.properties file. Any changes to this information from thetime of the original deployment must be manually recorded in themaximo.properties file before you upgrade.

Procedure1. Complete the following steps to update database properties within the

maximo.properties file:a. Change directory to product_install_dir\maximo\applications\maximo\

properties\

b. Make a backup of the maximo.properties file.c. Delete the maximo.properties file.d. Change directory to product_install_dir\etc

e. Make a backup of the maximo.properties_orig found in the directory. Thisbackup is a permanent backup that can be copied from when you need toupdate properties in the future.

f. Rename maximo.properties_orig to maximo.properties

g. Copy the maximo.properties file to product_install_dir\maximo\applications\maximo\properties\


h. Edit the maximo.properties file and update the credential or connectioninformation for the database server.

i. Save the file.j. Run the encryptproperties.bat file located in product_install_dir\maximo\

tools\maximo\ directory against the file to encrypt it.2. Complete the following steps to update properties within the

install.properties file: The install.properties file contains most propertiesused by the installation program, including non-connection related propertiesfor the database. These values must be up to date before you apply a fix packor other upgrade operation. If these values have changed from the previousdeployment, you must first manually update them.a. Change directory to product_install_dir\etc\

b. Edit the install.properties file and make updates. Do not changeencrypted properties (prefixed by [enc]). You are prompted for updatedvalues during the update operation. These values are written to theinstall.properties file.

c. Save the file.

There is one important exception to this procedure. When changing the valueof the WebSphere Application Server Network Deployment host name(WAS.DeploymentManagerHostName), in addition to updating this propertyvalue in the install.properties file, you need to also update a property forthe WebSphere Application Server Network Deployment thin client in thethinwasadmin.bat file and then run that file.

3. To update the WebSphere Application Server Network Deployment host namethat was used in the previous deployment, complete the following steps:a. Update the WAS.DeploymentManagerHostName value in the

install.properties file, as described in the previous procedure.b. Edit the C:\IBM\SMP\WASClient\thinwasadmin.bat file.c. Update the following line of the file with the new, fully qualified, host name

of the WebSphere Application Server Network Deployment server.set wsadminHost=-Dcom.ibm.ws.scripting.host=fully_qualified_host_name

d. Run thinwasadmin.thinwsadmin.bat -username domain_manager_user_name -password password

e. When prompted, indicate that you do want to download the truststore file.

Results

After you have completed these updates, you are able to upgrade, install a fixpack, or install another Service Management product using the corrected values.



Chapter 16. Troubleshooting installation

The topics in this section describe installation-related problems that have beenfound and their solutions.

General troubleshooting of the product deploymentRefer to this section for general troubleshooting information about the productinstallation program.

Overview

Because IBM Tivoli Asset Management for IT is typically deployed as a distributedsystem with code running on several different servers, errors can be generatedfrom multiple sources. The install error panel displays any failure messagesencountered during execution of the configuration step of the deployment. Thesemessages direct you to the source of the problem, which tells you which set of logsto examine for further details.

All installation-related messages begin with the prefix CTGIN. Informationalmessage end with a suffix of I, warning messages end with a suffix of W, and errormessages end with a suffix of E.

There are four main categories of logs that can be used for installation errorremediation.v Install trace logsv Solution install logsv Maximo logsv Middleware logs

Install trace logs

Install trace logs are generated on the Tivoli Asset Management for ITadministrative workstation in the tamit_install_dir\logs directory. These logs canbe searched for the error message displayed on the install error panel, and can beuseful in getting more diagnostic information about why the error occurred.Install trace logs contain historical data about when the installation program wasinvoked and which options were chosen for the deployment. It also containsinformation about updates and fix packs.

Searching on the term maxinst places you in the general proximity of informationabout database configuration.

If you encounter an error during a validation task, install trace logs can also belocated within the C:\Documents and Settings\Administrator directory. They aremoved to the tamit_install_dir\logs directory during execution of theconfiguration step of the deployment.

The following trace log files are found in the tamit_install_dir\logs directory:

CTGInstallTrace00.logThis log contains information produced by the Tivoli Asset Managementfor IT installation program, which includes information generated by the


configuration code that performs the automated configuration of IBMWebSphere Application Server Network Deployment and IBM DB2OracleWebLogic Server and the database software, and also information relatedto embedded calls to the process solution installationprogram. Information generated from subsequent invocations of theinstallation program or the process solution installation program isappended to this file.

The following success message examples are found in theCTGInstallTrace00.log file. These messages can be used to determinewhich phases of the installation were successful:v CTGIN2114I: The database was created successfully

v CTGIN2135I: Tablespace maxdata created successfully

v CTGIN2135I: Tablespace maxtemp created successfully

v CTGIN2079I: Base services database configuration completedsuccessfully(This message indicates that maxinst finished successfully.)

v CTGIN2222I: WebSphere Application Server creation successful

v CTGIN2188I: Creation and configuration of service integration bussuccessfully completed

v CTGIN2184I: Creation and configuration of JMS resourcessuccessfully completed

v CTGIN2310I: Application server security was successfully enabledfor the base services

v CTGIN2253I: buildmaximoear.cmd completed successfully

v CTGIN2224I: Deployment of application MAXIMO was successful

v CTGIN2253I: buildhelpear.cmd completed successfully

v CTGIN2224I: Deployment of application MAXIMOHELP was successful

v CTGIN2208I: runConfigurationStep completed successfully

v CTGIN2370I: The installation finished successfully

The following warning message example is found in theCTGInstallTrace00.log file. This message indicates that while a functioncompleted successfully, you need to perform additional steps outside of theinstallation program.v CTGIN2420W The undoConfiguration function completed but some

manual clean-up is required for the following component: <VariableformatSpec="{0}">manual component</Variable>

The following error message example indicates that while the installationcompleted, there were some serious errors.v CTGIN2371E: The installation is finished, but some serious errors

occurred during the install.

In this error case, open the CTGInstallTrace00.log file and examine themost recent logged information located at the bottom of the file. Determinewhat caused the failure. In some cases, the error is the result of a failedconfiguration task that was attempted by Tivoli Asset Management for ITinstallation program configuration scripts.

CTGInstallMessage00.logThis log contains named message statements generated by the Tivoli AssetManagement for IT installation program, configuration tasks, and theprocess solution installation program during the installation.


tamit_log_file_name.logThis log contains information about the Tivoli Asset Management for ITinstallation program itself, including values that you provided and optionsyou selected during the installation.

In some instances, you find trace logs containing 01, 02, and so on, in the filename. These files contain information like what is found in the files that include00 in the file name. These files are generated when a second JVM is started duringthe installation, and it begins logging information.

Solution install logs

Solution install logs are generated on the Tivoli Asset Management for ITadministrative workstation in the tamit_install_dir\solutions\logs andC:\program files\ibm\common\acsi\logs\administrative_user directories. Theselogs provide in-depth information about exceptions and errors related to processmanager packages, other process solution installation packages, and also thedeployment engine.

Maximo logs

Core components of Tivoli Asset Management for IT include deployment utilitiessuch as updatedb, configdb, maxinst, tdtoolkit, buildmaximoear, anddeployapplication. Logs for these components are generated on the administrativeworkstation in the tamit_install_dir\maximo\tools\maximo\log directory.

Middleware logs

Native middleware logs for the database server and an application server can beexamined for failures occurring on the middleware server itself. Applicationserver-related logs generated for WebSphere Application Server, deploymentmanager, and node agentare used to troubleshoot EAR file deployment orIntegrated Solutions Console module deployment failures.

If you encounter errors related to EAR file deployment, examine the SystemOut.logand SystemError.log files.

Log utility

When engaging IBM product support services, be prepared to provide log files inan archive file. The LogZipper.bat utility provided in the tamit_install_dir\scripts directory can be used for this task. If you use the LogZipper.bat utility, allrelevant log files are archived in tamit_install_dir\debug\YYYYMMDD_hhmmss.zip.

When contacting IBM support personnel, you are asked to provide log files fromthe following directories:v was_install_dir\logs (from both the WebSphere Application Server Network

Deployment application server and the deployment manager)v was_portal_dir\log

v tamit_install_dir\logs

v tamit_install_dir\solution/logs

v tamit_install_dir\maximo\applications\maximo\properties

v tamit_install_dir\etc\install.properties

v workspace_dir

Chapter 16. Troubleshooting installation 287

Deployment properties

Deployment of IBM Service Management solutions often happens in stages. Youmight install one IBM Service Management product and then deploy another at alater date. Follow-up deployments rely on the installation and configuration datafrom previous installations. For example, how to connect to the database used withthe original product deployment. This information must be persisted andprotected. This data is persisted by storing deployment data in both the productdatabase and a set of properties files. This redundancy protects the deploymentinformation in case anything were to happen to the database.

After a successful deployment, the deployment properties are kept both in thedatabase and in two property files.

maximo.propertiesThe maximo.properties file is an encrypted file which is located in thetamit_install_dir\maximo\applications\maximo\properties\ directory.This property file contains database connection properties.

install.propertiesThe install.properties file is an encrypted file which is located in thetamit_install_dir\etc\ directory and contains most properties related tothe deployment.

Errors related to an inability to connect or authenticate to middleware serversduring an upgrade or fix pack installation might be caused by obsolete propertyvalues. For example, if you have changed the password for a user ID that youused during the initial Tivoli Asset Management for IT installation withoutupdating that value in the relevant property file, the next installation action fetchesthe outdated value from the property file and a failure occurs.

Refer to Chapter 15, “Installation properties,” on page 269 for detailed informationabout properties contained in these files and also for information about updatingproperties following a successful deployment.

License files

License files are located on the media and are not packaged with the installationprogram. If you copy the installation program from the product media to the filesystem, the License directory must also be copied.

Problem resolution

The configuration step of the Tivoli Asset Management for IT installation processoccurs once you have navigated through all the install wizard panels and thenclicked the Install button.

Errors experienced before the configuration step are typically related to theinability of the install program to verify that input values you have provided. Ifyou experience this error, investigate the trace logs, resolve the issue, and thenproceed through the rest of the install wizard.

If you experience an error after the configuration step, you need to exit theinstallation program. Examine the trace, solution install, and Maximo logs. Resolvethe issue and then complete the installation using the taskrunner utility byinvoking it from the command line:C:\IBM\SMP\scripts\taskRunner.bat CONTINUE STOPONERROR


Note: If you reboot the system, you are not be able to use the taskrunner utility torun configuration scripts. Taskrunner data stores are not persisted. If you intend touse the taskrunner utility, do not reboot your system.

The taskrunner utility resumes the installation at the point where the lastsuccessfully completed task was recorded in the previous attempt. If you runtaskrunner with the NOSTOPONERROR parameter, the taskrunner continuesdespite errors.

Middleware installation program troubleshooting featureThe middleware installation program includes a feature that improves your abilityto troubleshoot installation errors by directing you to troubleshooting information.

When an error occurs during the plan deployment, the middleware installationprogram displays an error summary panel. This panel provides details on thenature of the error and when it occurred. This panel provides links to moredetailed information about the error through the use of a Logs button and aTroubleshooting button.

The Logs button opens a new window containing the directory hosting the logfiles relevant to the error. Parse these logs for information to troubleshoot theerror.

The Troubleshooting button launches your default Web browser and loadsrelevant troubleshooting information directly from the product support site. Usethe information from the support site to diagnose and resolve the error condition.

The links that bind an error condition to the URL of the product support site arefound in the MWITroubleshooting.xml file. This file is contained in the middlewaremedia package. The middleware installation program downloads the latest versionof this file when it is started. If it is unable to connect to the product support siteto update the file, it uses the local copy of the file.

Tivoli middleware installer logsTivoli middleware installer log files are located in the workspace directory(workspace_dir) that was defined in the middleware installer. Compare the differenttypes of log files described in this section.

User interface logsThe logs generated by the middleware installer user interface are located inthe workspace directory.

The mwi.log file is the high-level log file that was generated by the mostrecent invocation of the middleware installer. If an error occurs, examinethis log file first. An entry in this log file might direct you to a lower-levellog file.

Log files named mwi.logX, where X is a number, are copies of the mwi.logfile from earlier invocations of the middleware installer So, for example,mwi.log0 is produced after the first invocation of the middleware installer,mwi.log1 is produced after the second invocation of the middlewareinstaller, and so on.

Logs for steps run by the user interfaceIn addition to collecting input from the user, the user interface of themiddleware installer also performs several system checks. Examples ofsystem checks run by the user interface runs include:


v dependency checking to ensure the operating system meets thedeployment requirements

v inventorying the software on the system to locate existing instances ofmiddleware products deployed by the middleware installer

v checking the available disk space to ensure there is enough for thedeployment

Each of these checks is produced in the form of a step so that it can also berun as part of the deployment plan. When the user interface runs a step, itcopies the step into a subdirectory of the workspace directory. The log filesgenerated by a step are located in the same subdirectory and follow thesame pattern as a step that is run as part of the deployment plan.

Logs for the deployment planThe deployment plan is located in the directory workspace_dir/host_name/deploymentPlan, where host name is the host name of the current system.Each time the deployment plan is used to install or uninstall middlewareproducts, a process ID is assigned and log files are generated.

The log files for the deployment plan are located in the subdirectorylogs/process_ID. The primary log file for the deployment plan isDeploymentPlan.log, a high-level log file that lists the steps invoked as partof the deployment plan.

Logs for the computer planThe computer plan is located in the directory workspace_dir/host_name/deploymentPlan/computerPlan_host_name. The log files for the computerplan are located in the logs subdirectory. The primary log files for thecomputer plan are named computerPlan_host_name_process_ID. These logfiles contain the output generated by ANT when running the computerplan ANT script.

Logs for steps in the deployment planEach step in the deployment plan is located in a directory namedworkspace_dir/host_name/deploymentPlan/MachinePlan_host_name/step_num_step_ID, where step_num is the sequence number of this step ininstall processing order of the deployment plan and step_ID identifies thestep. The log files for the step are located in the logs subdirectory.

Some steps might provide a message log file namedstep_ID_process_ID.message, which contains a few entries that summarizethe result of invoking the step. All steps will provide a trace log file namedstep_ID_process_ID.log, which contains many entries, usually includinginformation about the input parameters and the substeps invoked.

Logs for substepsEach step contains one or more substeps. The substeps perform the actualinstall, uninstall and checking work for the middleware installer.

Each substep is located in the directory workspace_dir/hostname/deploymentPlan/MachinePlan_host_name/step_num_step_ID/operation/substep_num_substep_ID, where operation is the ANT target in the stepANT script that invokes this substep.v substep_num is the sequence number of this substep in the processing

order of the stepv substep_ID identifies the substep

Typical values for operation are install, uninstall, and check.


The log files for the substep are usually located in a subdirectory namedprocess_ID/logs.

Log files generated by the native middleware installation programs willalso be kept here.

Middleware installation program setup script error codesWhen you encounter middleware installation problems, make sure that you reviewthe installation error codes to resolve problems.

Table 24. Middleware installation program setup script error codes


11 Unsupported operating system The middleware installation program or oneof the middleware products cannot run onthis operating system.

12 Unsupported Linux distribution The middleware installation program or oneof the middleware products is not supportedon this Linux kernel. Refer to “Hardwareand software requirements” on page 3.

13 Unsupported kernel bit mode The middleware installation program issupported on Linux 32/64 - bit mode and onAIX 64 - bit mode.

14 Unsupported Processor architecture The middleware installation program or oneof the middleware products is not supportedon this processor architecture. Currently onlyx86 and AMD64 architecture are supported.

21 Environment variable: mwi_launchpadroot /LaunchPadBatchPath is not set

The environment variable must be set to themiddleware installation program install fileslocation:

Windows Windows:LaunchPadBatchPath

Linux UNIX operating systems:mwi_launchpadroot

22 The middleware installation programexecutable file not found

The middleware installation program installfile is missing or not accessible. Check toensure that the specified file exists in thecurrent directory.

31 Host name is not a fully qualified domainname.

The middleware installation program or oneof the middleware products requires a fullyqualified host name defined.

32 SELinux is enabled or set in Enforcing mode Middleware product installation fails withthe following error:

JRE could not be found on the system

Disable SELinux using one of the followingmethods:v setenforce 0

v Add the following entry to the/etc/system file:

set fmac_enforcing = 0


Table 24. Middleware installation program setup script error codes (continued)


33 The library libstdc++.so.5 (64 - bit) is notinstalled.

The installer requires libstdc++.so.5 (64 -bit) It is located in /usr/lib64/libstdc++.so.5. If the system does not havethis library installed, search for an Rational®

Portfolio Manager package (64 - bit)compatible with system that contains thislibrary and install it.

34 The library libstdc++.so.5 is not installed. The installer requires libstdc++.so.5. It islocated in /usr/lib/libstdc++.so.5. If thesystem does not have this library installed,search for an Rational Portfolio Managerpackage compatible with system thatcontains this library and install it.

Related reference

“Tivoli middleware installer logs” on page 289Tivoli middleware installer log files are located in the workspace directory(workspace_dir) that was defined in the middleware installer. Compare the differenttypes of log files described in this section.

Process solution installation logsIf you experience any problems or encounter any error messages during the use ofthe process solution installation program, refer to these log files.

Log files are kept in the following locations:

Table 25. Process solution installation logs

Log type Description Location

Package log These are log files containing theStdOut/StdErr output of externalcommands launched by thepackage as it is processed by theDeployment Engine. These logfiles are typically vital to theproper debugging of packageissues.

In general, logs have two parts, a“.out” and “.err” file, both withthe same pre-extension file name.“.out” files contain the contentsof the Standard Output stream asoutput by the external command..err files contain the contents ofthe Standard Error stream. It isnormal for one to be blank,provided there was no erroroutput (or there was ONLY erroroutput).

You might discover numerous(10-20) package log filesgenerated for any particularpackage installed.

tamit_install_dir\solutions\logs\package_name\

For instance, if the processsolution installer encounters anerror in the Config Managementpackage, and Tivoli AssetManagement for IT is installed toC:\IBM\SMP, then the logs for theConfig Package can be found in:C:\IBM\SMP\solutions\logs\Config_PMP\.


Table 25. Process solution installation logs (continued)


Tivoli Asset Management for ITlog

The logs kept by the processsolution installation subsystem.

tamit_install_dir\logs\CTGInstallMessageXX.logtamit_install_dir\logs\CTGInstallTrace.log

XX is a two-digit number such as00. These logs contain the traceoutput of the process solutioninstaller subsystem.

Note: You might encountermessages like the followingmessage in theMAXIMO_DEPLOY_ERR.err file foundin the tamit_install_dir\solutions\logs directory for aprocess manager once it has beeninstalled:

v *sys-package-mgr*:processing new jar,'C:\IBM\SMP\lib\icl.jar'

v *sys-package-mgr*:processing new jar,'C:\IBM\SMP\lib\CTGInstallCommon.jar'

v *sys-package-mgr*:processing new jar,'C:\IBM\SMP\lib\CTGInstallResources.jar'

Although these messages appearin an error log file, they areinformational only, and do notrepresent deploymenterrors. These messages can besafely ignored.

Solution Install/DeploymentEngine Logs

The logs kept by the solutioninstallation program/Deployment engine run time.process solution installation usesthe IBM technology as the meansto installation and tracksinstalled packages. This run timehas its own logging system.

Note: After an installation thelogs contain sensitive credentials.It is recommended that theselogs be removed after asuccessful installation.

C:\Program Files\IBM\Common\acsi\logs\user_name\de_msg.log

C:\Program Files\IBM\Common\acsi\logs\user_name\de_trace.log

For instance, if you installedunder the user nameAdministrator, the logs would befound under: C:\ProgramFiles\IBM\Common\acsi\logs\Administrator\de_msg.log




WebSphere Application ServerLogs

The logs kept of connections,exceptions, and other failuresexperienced by the WebSphereApplication Server in itsday-to-day running. These logsare often helpful in the diagnosisof errors in particular EAR filesor other back-end operations,such as database connections.

was_install_dir\profiles\profile\logs\AboutThisProfile.txt

was_install_dir\profiles\profile\logs\server_name\startServer.log

was_install_dir\profiles\profile\logs\server_name\stopServer.log

was_install_dir\profiles\profile\logs\server_name\SystemErr.log

was_install_dir\profiles\profile\logs\server_name\SystemOut.log

For instance, if your WebSphereApplication Server was installedin C:\IBM\WebSphere\AppServer\,your profile name was AppSrv01,and your server name wasserver1, you would provide thefollowing logs:C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\AboutThisProfile.txt

Maximo logs There are also a few logs kept byMaximo itself. They are useful intracking the progress, success,and failure of a few back-endcommands provided by Maximo.

tamit_install_dir\maximo\tools\maximo\log\updatedb\time_stamp\.log

If your Maximo installationlocation was C:\IBM\SMP\Maximo,and the package executed theUpdateDB command on April19th at approximately 5:06:07PM,the logging information wouldbe written to the file:C:\IBM\SMP\Maximo\tools\maximo\log\updatedb20070419170607.log




WebSphere Application ServerThin Client Logs

The WebSphere ApplicationServer thin client is themechanism by which the processmanager packages communicatewith the WebSphere ApplicationServer. If this automateddeployment fails, the exactactions the Thin Client took andthe associated responses from theWebSphere Application Serverare stored in logs.

tamit_install_dir\wasclient\logs\CTGIN_wsadmin.traceout

tamit_install_dir\wasclient\logs\wsadmin.traceout

tamit_install_dir\wasclient\logs\wsadmin.valout

If your Tivoli Asset Managementfor IT installation location isC:\IBM\SMP, the following logfiles would contain the ThinWebSphere Application ServerClient tracing information:

C:\IBM\SMP\wasclient\logs\CTGIN_wsadmin.traceout

C:\IBM\SMP\wasclient\logs\wsadmin.traceout

C:\IBM\SMP\wasclient\logs\wsadmin.valout

It is a good practice to rename existing logs before attempting a package install. Itis useful to have a log consisted of only the information related to the success orfailure of current package installation to facilitate problem determination.

Encountering error ACUINI0044EDuring middleware installation using the middleware installer, you mightencounter error ACUINI0044E, which occurs during the install step for thedeployment engine.

About this task

If you encounter error ACUINI0044E through the normal use of the middlewareinstallation program, it might be related to a failure of the deployment engine tobe installed or started. The following messages are displayed after a failure todeploy the deployment engine is encountered:Deployment Engine did not start successfully. Please try to manuallystart the Deployment Engine and restart the installer.

ACUINI0044E Failed to register and start Deployment EngineIBM ADE Service

In order to troubleshoot this error, complete the following steps:

Procedure1. Exit the middleware installation program.2. Restart the deployment engine.

Windows Windows:net start "IBM ADE Service"

UNIX UNIX:/usr/ibm/common/acsi/bin/acsisrv.sh -start


If the deployment engine is started successfully, restart the middlewareinstallation program and resume middleware deployment. If the deploymentengine fails to start, you have to manually uninstall the deployment engine.This action also eliminates the deployment engine registry information forother products installed on the system, so be cautious when you uninstall thedeployment engine.

Encountering error on a 32 - bit Windows systemWindows When you attempt to use the 64 - bit middleware installation program

on a 32 - bit Windows system, you encounter an error.

About this task

If you encounter the following error, it indicates that you are attempting to use the64 - bit middleware installation program (mwi-AMD64.exe) on a 32 - bit Windowssystem.CreateProcess failed ==> The image file %1 is valid, but for a machine typeother than the current machine

The appropriate middleware installation program executable for 32 - bit Windowssystems is mwi.exe. Alternatively, run the following command to automaticallyselect the appropriate executable for the system:setupwin.bat /l

Improper configuration of IBM DB2 or IBM Tivoli Directory ServerWhile running the middleware installation program on an AIX system, youencounter the error message CTGIN9042E, which relates to a failure to properlyconfigure DB2 or IBM Tivoli Directory Server.

Before you begin

If you encounter error CTGIN9042E through the normal use of the middlewareinstallation program on an AIX computer, check the following log files todetermine the precise cause of the error:

Check the mwi.log file located within the workspace directory workspace_dir (forexample:/ibm/tivoli/mwi/workspace), and look for an error like the followingsample:Caused by:workspace_dir/computer_name/deploymentPlan/MachinePlan_computer_name/00005_DB2_Configuration/install/02_CONFIG/02_CONFIG_AIX.xml:173: Failedto create database instance ctginsxy.

Also check the createinstance.log file at workspace_dir/computer_name/deploymentPlan/MachinePlan_computer_shortname/00005_DB2_Configuration/install/02_CONFIG/[INSTALL_processing.req.id]/logs/createinstance.log

for an error like the following sample:Caused by: workspace_dir/computer_name/deploymentPlan/MachinePlan_computer_name/00008_ITDS_Configuration/install/02_CONFIG/02_CONFIG_AIX.xml:173:Failed to create itds database instance itdsccmxy.


Check the startInstanceTool.log file at workspace_dir/computer_name/deploymentPlan/MachinePlan_computer_shortname/00008_ITDS_Configuration/install/02_CONFIG/[INSTALL_processing.req.id]/logs/startInstanceTool.log

for any error like the following sample:DBI1703E No valid service name or port number found

If you locate any of these errors in the log files listed, the error can be attributed toa failure to properly configure either DB2 or Tivoli Directory Server.

About this task

To resolve this issue, complete the following steps:

Procedure1. Click Finish to exit out of the middleware installation program install wizard.2. Restart the middleware installation program and proceed through the wizard

until you reach the Restart or Undeploy the Plan panel.3. Select Undeploy the Plan, and then click Next.4. Select Partial uninstall, and then click Next.5. Select only the Configuration for DB2 Enterprise Server Edition option, and

then click Next.6. Proceed through the panels to complete the uninstall and click Finish to exit

the installer.7. Download the mwi_db2instance.sh and mwi_itdsinstance.sh files attached to

this document to your local system. Alternatively, you can create your owncopies of these files.a. Create a text file named mwi_db2instance.sh and add the following

content:#!/bin/kshport1=0var1=3if [ -f /etc/services ]thenif [ $# -eq 0 ]thencat >> /etc/services << EOFDB2_ctginst1 60000/tcpDB2_ctginst1_END 60003/tcpEOFelif [ $# -gt 0 ]thenport1=`expr $2 + $var1`cat >> /etc/services << EOFDB2_$1 $2/tcpDB2_$1_END $port1/tcpEOFfifi

b. Create a text file named mwi_itdsinstance.sh and add the followingcontent:#!/bin/kshport1=0var1=3if [ -f /etc/services ]thenif [ $# -eq 0 ]


thencat >> /etc/services << EOFDB2_idsccmdb 60004/tcpDB2_idsccmdb_END 60007/tcpEOFelif [ $# -gt 0 ]thenport1=`expr $2 + $var1`cat >> /etc/services << EOFDB2_$1 $2/tcpDB2_$1_END $port1/tcpEOFfifi

8. Based on the deployment choices you made in the middleware installationprogram, run the following scripts:v If you elected to deploy both the database server and directory server, run

both the mwi_db2instance.sh and mwi_itdsinstance.sh scripts.v If you elected to deploy the database server only, run the

mwi_db2instance.sh script.v If you elected to deploy the directory server only, run the

mwi_itdsinstance.sh script.9. Run the middleware installation program again and select the option to

Restart the plan, which installs everything you selected in the originaldeployment plan.

10. Proceed through the rest of the installation process and exit the installationprogram when complete.

Example

When using the mwi_db2instance.sh script, DB2 is installed with default values ifyou initiate the script without passing any parameters. If you want to use customvalues run mwi_db2instance.sh and pass values for DB2 instance name and theDB2 port number in the following order:./mwi_db2instance.sh ctginsxy 50007where ctginzxy and 50007 are the values entered in middleware installationprogram DB2 Configuration Panel.

When using the mwi_itdsinstance.sh script, the directory server is installed withdefault values if you initiate the script without passing any parameters. If youwant to use custom values run mwi_itdsinstance.sh and pass values for theinstance name and the port number in the following order: ./mwi_itdsinstance.shitdsccmxy 60007 where itdsccmxy and 60007 are the values entered in middlewareinstallation program.

Encountering the CTGIN9042E SOAP connection problemIf you encounter error CTGIN9042E through the normal use of the middlewareinstallation program on a Windows 2003 system configured to use dual IPaddresses for IPv4 and IPv6, it might be caused by a SOAP connector performanceissue. This error occurs during the execution of the WebSphere Application ServerNetwork Deployment 6.1 configuration or authentication service configurationsteps.

Before you begin

Check log files for WebSphere Application Server Network Deploymentconfiguration failure messages in the following location: workspace_dir\


computer_name\deploymentPlan\MachinePlan_computer_shortname\00010_WAS_ND_Configuration\install\01_BASE/[INSTALL_processing.req.id]/logs/

Check log files for authentication service configuration failure messages in thefollowing location: workspace_dir\computer_name\deploymentPlan\MachinePlan_computer_shortname\00012_ESS_6.1\install\01_CONFIG\[INSTALL_processing.req.id]/logs

If the workspace is located at: C:\ibm\tivoli\workspace, the computer name ismy_computer, and the processing.req.id is created as a date_timestamp, log filesare located in:C:\ibm\tivoli\mwi\workspace_dir\mymachine.ibm.com\deploymentPlan\MachinePlan_my_computer\00009_WAS_ND_6.1\install\01_BASE\[INSTALL_1130_06.54]\logs

Also check log files for the following error:Unable to connect to the process dmgr on node ctgCellManager01 using SOAP connector.

About this task

To resolve the issue:

Procedure1. Click Finish to exit out of the Tivoli middleware installation program.2. Restart the Tivoli middleware installation program.3. Proceed through the wizard until you reach the panel that gives you the

choices of Restart the Plan or Undeploy the Plan.4. Select Undeploy the Plan and click Next.5. Click Undeploy.6. Once the uninstall is complete, click Finish to exit the Tivoli middleware

installation program.7. Manually delete the workspace folder (for example C:\ibm\tivoli\mwi\

workspace).8. Open a system prompt and launch the middleware installation program from

within the cd_image directory using the RMI option.mwi.exe -V USE_RMI_FOR_IPV6=yes

Related tasks

“Configuring the authentication service” on page 76The authentication service provides the ability to “launch-in-context”.Launch-in-context provides a means for launching from an application, like TivoliAsset Management for IT, to the user interface of an external Web-basedapplication such as Software Knowledge Base Toolkit. Both applications must usethe same directory server for authentication, and the external application musthave the authentication client installed. You authenticate only once, to the serverhosting the client; you do not need to authenticate again to the external applicationwhen they launch-in-context to it.

Encountering error CTGIN9042EDuring middleware installation using the middleware installer, you mightencounter error CTGIN9042E which occurs during the install step for IBMWebSphere Application Server Network Deployment 6.1.


About this task

If you encounter error CTGIN9042E through the normal use of the middlewareinstallation program, it might be related to stale entries in the CEI registry.

In order to troubleshoot this error, complete the following steps:

Procedure1. First check de_processreq.log for failures related to VerifyLogsInInstallLogs

Action. The de_processreq.log file can be found at:workspace_dir\computer_name\deploymentPlan\MachinePlan_computer_short_name\00009_WAS_ND_6.1\install\01_BASE/[INSTALL_processing.req.id]/logs/de_processreq.log

For example, if the workspace is located at C:\ibm\tivoli\workspace, thecomputer name is my_computer, and the processing.req.id is created as adate_timestamp, then the de_processreq.log is located in:C:\ibm\tivoli\mwi\workspace\my_computer.ibm.com\deploymentPlan\MachinePlan_my_computer\00009_WAS_ND_6.1\install\01_BASE\[INSTALL_1130_06.54]\logs

2. Next, check for any stale WebSphere Application Server Network Deploymententries:a. Extract the native image of WebSphere Application Server Network

Deployment:

Windows Windows:WAS-ND_WindowsIA32_Custom_v61023

Linux Linux:WAS-ND_LinuxIA32_Custom_v61023.tar.gz

AIX AIX:WAS-ND_AIXppc64_Custom_v61023.tar.gz

b. Open the console window.c. Navigate to the bin folder of extracted image. For example:

\WAS\installRegistryUtils\bin

d. List registry entries:

Windows Windows:installRegistryUtils.bat -listProducts

UNIX UNIX:installRegistryUtils.sh -listProducts

e. Check for WebSphere Application Server Network Deployment relatedentries. If any entries are listed, even if you have successfully uninstalledWebSphere Application Server Network Deployment, you need to clean theregistry entry.

3. Clean the registry entries:a. Clean WebSphere Application Server Network Deployment entries from the

registry:installRegistryUtils -cleanProduct -offeringID ND -installLocationwas_install_dir

b. Edit the vpd.properties file, remove any WebSphere Application ServerNetwork Deployment entries, and then save the file. The file is located inthe installation directory of the operating system:


Windows Windows:C:\WINNT directory or C:\windows directory

UNIX UNIX:/usr/lib/objrepos/

4. After cleaning the registry, run the middleware installation program again andRestart the plan. WebSphere Application Server Network Deployment is nowsuccessfully installed in the default location, for example, C:\ProgramFiles\IBM\WebSphere\AppServer for Windows.

Failure when system directories cannot be renamedDuring middleware installation you might encounter CTGIN9042E during theexecution of a number of installation steps. This error can occur during theexecution of any of the middleware steps where renaming of the product installdirectories has failed.

Before you begin

If you encounter error message:CTGIN9042E: Errors were encountered during the execution of step step_name

,where step_name can be any of a number of middleware installation steps. Forexample:CTGIN9042E: Errors were encountered during the execution of step Errors were encountered during the execution of step DB2 Enterprise Server Edition V

Before installing the specific middleware product, the middleware installerattempts to save any existing product install directories by renaming them.

The renaming of existing directories can fail in certain situations. For example:1. If it has been previously created as a file system (instead of a directory within a

defined file system).2. If the file system or directory has been created with Read Only access.

About this task

To determine if this situation is the cause of the error complete the following steps:

Procedure1. Check the DeploymentPlan.log

This log file is located at /ibm/tivoli/mwi/workspace/computer_name/deploymentPlan/logs/[INSTALL_date_time_stamp]/DeploymentPlan.log, where/ibm/tivoli/mwi/workspace is the default middleware workspace or the pathyou specified on the installer workspace panel, and computer_name is the hostname of the computer on which you are installing.Locate the step name that has failed. For example:2008-12-15 04:07:44.595 : Failed: Deployment Step: step_00004_DB2_9.72008-12-15 04:07:44.595 : Machine Plan: MachinePlan_mymachine.mydomain.com

The failed step in this case is "step_00004_DB2_9.7"Also check the DeploymentPlan.log for the following sample error text(substitute your computer name instead of the host name shown here):


ml:284: The following error occurred while executing this line:/ibm/tivoli/mwi/workspace/host_name/deploymentPlan/MachinePlan_<host name>/deploymentPlan/MachinePlan_00004_DB2_9.7/common/Utils.x

ml:544: Deployment Engine command de_processReq reported an error.

Check the de_processReq output file at /ibm/tivoli/mwi/workspace/host_name/deploymentPlan/MachinePlan_host_name/00004_DB2_9.7/install/01_BASE/[INSTALL_1215_04.00 ]/logs/de_processreq.log_utf8

Check de_trace.log at /ibm/tivoli/mwi/workspace/host_name/deploymentPlan/MachinePlan_host_name/00004_DB2_9.7/install/01_BASE/[INSTALL_1215_04.00]/logs.

2. Check the location and the logs indicated by the error message from StepCheck de_processreq.log_utf8 at /ibm/tivoli/mwi/workspace/host_name/deploymentPlan/MachinePlan_host_name/00004_DB2_9.7/install/01_BASE/[INSTALL_1215_04.00 ]/logs/de_processreq.log_utf8 for the following errortext:<errorMessage>[com.ibm.ac.si.ap.action.ExternalCommandActionException:ACUOSI0050E External command action failed with return code 1.<actionErrorEvent actionID=RenameExistingInstallLocation_UnixactionName="externalCommand">ACUCME1100E</actionErrorEvent>

If this error is found in de_processreq.log_utf8, check for the existence of thefollowing error file that might contain additional information:product_name_RenameExistingInstallLocation_Unix_date_time_stamp.err Forexample,DB2_Enterprise_Server_Edition_RenameExistingInstallLocation_Unix_20081215_040712GMT-05.00.err

. View the contents of the file if it exists and determine if it contains an errormessage like the following sample:mv: 0653-401 Cannot rename /db2 to /db2_20081215_040712GMT-05.00:The requested resource is busy.

In this case, /db2 is the name of the existing file system or directory./db2_20081215_040712GMT-05.00 is the new name the middleware installer isusing for the mv command to rename the file system or directory.To resolve theproblem:a. If /db2 is a file system, rerun the installer and specify a new directory

within the file system:1) Restart the middleware installer, and select Undeploy the plan. Choose

Complete Uninstall and click Undeploy.2) Restart the middleware installer and select Edit the configuration

parameters.3) Specify a directory (for example, /db2/V9.7) within the file system for

the install location of the product that previously failed.4) Deploy the plan.

b. If /db2 is a file system or directory with Read Only access, give writepermission for the user or owner of the file system (directory). Also givewrite permission to the user performing the installation. Then, run themiddleware installer again to deploy the plan.


Incorrect db2admin passwordIf you encounter error CTGIN9042E Errors were encountered during theexecution of the step DB2 Enterprise Server Edition Version 9.1.4. throughthe normal use of the middleware installation program, it might be related to thefact that there is an existing user named db2admin on the system, but with adifferent password than the one entered in the middleware installation program.

Check the db2_91_inst.log file for an error similar to the following:ERROR:The password specified is invalid. Enter a valid password.

The db2_91_inst.log file is located at: workspace_dir\computer_name\deploymentPlan\MachinePlan_computer_shortname\00004_DB2_9.1\install\01_BASE\[INSTALL_processing.req.id]/logs/ db2_91_inst.log

So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, thecomputer name is mymachine, and the processing.req.id is created as adate_timestamp, then the db2_91_inst.log file is located in:C:\ibm\tivoli\mwi\workspace\my_computer.ibm.com\deploymentPlan\MachinePlan_mymachine\00004_DB2_9.1\install\01_BASE\[INSTALL_0424_09.32]\logs

Check the de_processreq.log file for an error similar to the following:<errorMessages>

<errorMessage>[com.ibm.ac.si.ap.action.ExternalCommandActionException:ACUOSI0050E External command action failed with return code 87. Invocationstring: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1/DB2-ESE_9.1.0/ESE/setup.exe,/f, /l, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.32]/db2_91_inst.log,/u, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.32]/

Decrypted_ResponseFile.txt],com.ibm.ac.common.hosts.CreationFailedException: : ]</errorMessage>

<errorMessage>[com.ibm.ac.common.hosts.CreationFailedException: : ]</errorMessage>

</errorMessages><actionErrorEvents>

<actionErrorEvent actionID="InstallProduct" actionName="externalCommand">ACUCME1100E</actionErrorEvent>

</actionErrorEvents>

The de_processreq.log file is located at:workspace_dir\computer_name\deploymentPlan\MachinePlan_computer_shortname\00004_DB2_9.1\install\01_BASE\[INSTALL_processing.req.id]/logs/ de_processreq.log

If the workspace is located at: C:\ibm\tivoli\workspace, the computer name ismy_computer, and the processing.req.id is created as a date_timestamp, then thede_processreq.log file is located in: C:\ibm\tivoli\mwi\workspace\my_computer.ibm.com\deploymentPlan\MachinePlan_mymachine\00004_DB2_9.1\install\01_BASE\[INSTALL_0424_09.32]\logs

These errors indicate that the existing system user db2admin has differentpassword than the one entered in the middleware installation program.

To resolve this issue, complete the following steps:1. If you have not done so, click Finish to exit out of the of the middleware

installation program install wizard.2. Resolve the issue using one of the following methods:


v If you are the Administrator for that computer/user and if you know thepassword for the user db2admin you can use the same password for themiddleware installation program installation.

v You can delete the user db2admin and restart the middleware installationprogram .

v You can set or change the password for existing DB2 user db2admin.To set the password follow these stepsa. Right click the My Computer icon and select Manage.b. From the Computer Management console, select Local Users and Groups

in System Tools.c. Expand Local Users and Groups and then select Users

d. Right-click the db2admin user and then click Set password.e. Enter the password, confirm it, and then click OK

f. Click OK once again.3. Navigate to the directory containing the middleware installation program DVD

image and restart the middleware installation program.4. Select Restart the Plan and click Next.5. Specify the directory for the middleware install images and click Next.6. Specify the temporary directory and click Next.7. After disk space checks are completed, click Deploy to start the install.8. After install completes click Finish to exit the wizard.

DB2 password value not validWhile installing the middleware, you might encounter a problem with the IBMDB2 password that is not compliant with the password policy of the system.

If you encounter the following error while using the middleware installationprogram:CTGIN9042E: Errors were encountered during the execution of the step DB2Enterprise Server Edition Version 9.7

it could be attributed to the use of a password value entered for the DB2 user inthe middleware installation program that is incompatible with the password policyof the system.

Check the db2_95_inst.log file for an error like the following:1: ERROR:The installation program has been unable to create the user"db2admin" on computer "computer_name" because the password specified is too short.

1: ERROR:The response file specified "C:\WINNT\TEMP\2\_INSTA~1.18_/DECRYP~1.TXT"is not valid.

The db2_95_inst.log file is located at: workspace_dir\computer_name\deploymentPlan\MachinePlan_computer_short_name\00004_DB2_9.5\install\01_BASE\[INSTALL_processing.req.id]/logs/ db2_95_inst.log

If the workspace is located at: C:\ibm\tivoli\workspace, the computer name iscomputer_name, and the processing.req.id is created as a date_timestamp, then thedb2_95_inst.log would be located in:C:\ibm\tivoli\mwi\workspace\computer_name.ibm.com\deploymentPlan\MachinePlan_computer_name\00004_DB2_9.5\install\01_BASE\[INSTALL_0424_09.32]\logs.


Also check the de_processreq.log file for an error like the following error:<errorMessages>

<errorMessage>[com.ibm.ac.si.ap.action.ExternalCommandActionException:ACUOSI0050E External command action failed with return code 87.Invocation string: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1/DB2-ESE_9.5.0/ESE/setup.exe, /f, /l, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.32]/db2_95_inst.log, /u, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.32]/Decrypted_ResponseFile.txt],com.ibm.ac.common.hosts.CreationFailedException: : ]</errorMessage>

<errorMessage>[com.ibm.ac.common.hosts.CreationFailedException: : ]</errorMessage>

</errorMessages><actionErrorEvents>

<actionErrorEvent actionID="InstallProduct"actionName="externalCommand">ACUCME1100E</actionErrorEvent>

</actionErrorEvents>

The de_processreq.log file is located at: Workspace\computer_name\deploymentPlan\MachinePlan_computer_shortname\00004_DB2_9.5\install\01_BASE\[INSTALL_processing.req.id]/logs/ de_processreq.log.

If the workspace is located at: C:\ibm\tivoli\workspace, the computer name iscomputer_name, and the processing.req.id is created as a date_timestamp, then thede_processreq.log is located in: C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\00004_DB2_9.5\install\01_BASE\[INSTALL_0424_09.32]\logs.

It indicates that the password provided for the DB2 user db2admin in themiddleware installation program is not supported by the policy of the operatingsystem.

To resolve this issue, complete the following steps:1. If you have not done so, click Finish to exit out of the middleware installation

program install wizard.2. Check the system rules defined for passwords by navigating to Start →

Control Panel → Administrative Tools → Local Security Policy → SecuritySettings → Account Policies → Password Policy.

3. Restart the middleware installation program, by running thelaunchpad.[exe|sh] command.

4. Proceed through the panels until you reach the option to select Undeploy thePlan and then click Finish to exit the wizard.

5. Restart the middleware installation program.6. Select Edit the Configuration parameters.7. Enter a valid password for the DB2 user based upon the password policy

rules you observed earlier.8. Specify the directory for the middleware install images and click Next.9. Specify the temporary directory and click Next.

10. After disk space checks are completed, click Deploy to start the install.11. After install completes, click Finish to exit the wizard.


Related concepts

“System password policy settings” on page 26Before deploying IBM Tivoli Asset Management for IT, be sure that you arefamiliar with the password policies of systems used in the deployment, or youmight experience errors during installation.

Incorrect idsccmdb user passwordIf you encounter error CTGIN9042E through the normal use of the middlewareinstallation program, it might be related to the fact that there is an existing usernamed idsccmdb on the system, but with a different password than the one enteredin the middleware installation program.

Before you begin

The error might look like the following sample:CTGIN9042E: Errors were encountered during the execution of the stepConfiguration for IBM Tivoli Directory Server

Check the configureDB.log file for an error like the following sample:GLPCDB018E The DB2 administrator ID or password you specified is not valid.

This message indicates that the existing IBM Tivoli Directory Server user idsccmdbhas different password in the system.

The configureDB.log file is located at: workspace_dir\computer_name\deploymentPlan\MachinePlan_computer_short_name\00008_ITDS_Configuration\install\02_CONFIG\logs\configureDB.log

Windows Windows:If the workspace is located at: C:\ibm\tivoli\workspace, the computername is computer_name, then the configureDB.log file is located in:C:\ibm\tivoli\mwi\workspace\computer_name.ibm.com\deploymentPlan\MachinePlan_computer_name\00008_ITDS_Configuration\install\02_CONFIG\logs

Linux Linux:If the workspace is located at: /root/ibm/tivoli/mwi/workspace, thecomputer name is computer_name, then the configureDB.log is located in:/root/ibm/tivoli/mwi/workspace/computer_name.ibm.com/deploymentPlan/MachinePlan_computer_name.ibm.com/00008_ITDS_Configuration/install/02_CONFIG/logs

AIX AIX:If the workspace is located at: /ibm/tivoli/mwi/workspace, the computername is computer_name, then the configureDB.log is located in:/ibm/tivoli/mwi/workspace/computer_name.ibm.com/deploymentPlan/MachinePlan_computer_name.ibm.com/00008_ITDS_Configuration/install/02_CONFIG/logs

About this task

To resolve this issue, complete the following steps:


Procedure1. If you have not done so, click Finish to exit out of the middleware installation

program install wizard.2. Resolve the issue using one of the following methods:

v If you are the Administrator for that computer and if you know thepassword for the user idsccmdb, you can use the same password for themiddleware installation.

v You can delete the user idsccmdb and restart the middleware installationprogram.

v You can set or change the password for existing Directory Server useridsccmdb.

To set the password, complete the following steps:a. Right-click on My Computer icon and click Manage menu item.b. From the Computer Management console, select Local Users and Groups

in System Tools.c. Expand Local Users and Groups and then select Users.d. Right-click on the idsccmdb user and then click the set password menu

item.e. Enter the password, confirm it, and then click OK.f. Click OK once again.

For Linux Linux, AIX AIX:a. Log in as root and open command prompt.b. Run the following command at terminal:

# passwd idsccmdb

c. Enter the new password and confirm it.3. Navigate to the directory containing the middleware installation program

DVD image and restart the middleware installation program.4. Select Undeploy the Plan and click Next.5. Select Partial Uninstall and click Next.6. Select Configuration for IBM Tivoli Directory Server and click Next.7. Click Undeploy to start the uninstall.8. After install completes click Finish to exit the wizard.9. Navigate to the directory containing the middleware installation program

DVD image and restart the middleware installation program.10. Select Restart the Plan and click Next.11. Specify the directory for the middleware install images and click Next.12. Specify the temporary directory and click Next.13. After disk space checks are completed, click Deploy to start the install.14. After install completes click Finish to exit the wizard.

Error CTGIN2371E occurs during installation of more than one IBMService Management product on the same administrative workstation

You can install multiple Service Management products from the sameadministrative workstation. Ideally, the products you install share the same level ofbase services, which, in turn, assures that the products all share the same versionof the deployment engine.


If you first deploy an Service Management product that includes the latest versionof base services, and then install another Service Management product whichincludes a version of base services that is older than the first, you receive an errorand the product will not be configured.CTGIN2371E: The installation is finished, but some serious errors occurred during the install.

To confirm that the situation described above is the cause of the error, search theCTGInstallTrace00.log file for an error that states the deployment engine installoperation has failed, In this scenario, the installation program cannot upgrade theexisting, newer deployment engine. If this error is found, you can still successfullydeploy the additional Service Management product outside of the installationprogram using the deployment engine installed with the original product.

When this error occurs, product files are still extracted to the administrativeworkstation but the configuration step is not performed. The installation behavesas if you had selected the Copy files now, and perform installation configurationlater, manually option from the Run Configuration Step panel within the productinstallation program. The configuration step must be completed by using thetaskrunner utility.

To complete the deployment, run the following command in order to perform theconfiguration step of the additional product:ism_install_dir\scripts\taskrunner.bat STOPONERROR CONTINUE

Intermittent error when installing on WebSphere Application Server6.1.0.23

Use this workaround if you receive an intermittent error when installing IBMTivoli Asset Management for IT on WebSphere Application Server version 6.1.0.23

Error

If you receive the following combination of error messages, use the workaroundthat follows to resolve the problem.v In the CTGInstallTrace00.log, you see the error message:

CTGIN2233E: The WebSphere NodeAgent is not running. It must be runningbefore continuing with the installation.

v And in the WebSphere Application Server middleware log SystemOut.log, yousee the following error message:HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 7seconds.

Workaround

Update your WebSphere Application Server 6.1 installation to fix pack 6.1.0.27 orlater.

Error CTG00001 when performing an uninstallIn certain instances, while performing a product uninstall from the administrativesystem, you might encounter error CTG00001 The uninstall was unsuccessful.You will need to manually uninstall the Maximo product.


About this task

Click OK on the error message dialog box to finish the automated uninstallprocess.

To complete the uninstall, you will need:

Procedure1. Manually delete installation directories located under C:\IBM\SMP\maximo.2. Verify registry entries for the product and base services product are removed.

What to do next

Registry entries can be found under HKEY_LOCAL_MACHINE/SOFTWARE/IBM/Tivoli Base Services and under the of the ISM family product, for example,Tivoli Asset Management for IT.



Chapter 17. Performing multiple product installations usingone administrative workstation

You can use a single computer to deploy multiple instances of the product. Forexample, you can use the same computer to deploy a test environment, adevelopment environment, and a training environment.

About this task

One administrative workstation can support several Asset Management for ITdeployments by hosting multiple local instances of the deployment engine. If thereis a globally deployed deployment engine on the system, you cannot create localdeployment engine instances on that system. Using the middleware installationprogram to install middleware on the administrative workstation results in a globaldeployment engine instance being deployed on the system.

Future software deployment operations associated with a particular installationmust be conducted by the same system user ID that completed the originalinstallation. These operations include applying fix packs and upgrades, and addingadditional products. When performing follow-up installation actions or softwarelifecycle operations, complete them for a single installation before carrying themout for the next. This practice applies to using the future install actions using theprocess solution installer, the product installation program, or applying fix packs.This practice helps to avoid any potential confusion that can arise when runningseveral instances of these programs at once.

This scenario does not limit the middleware targets used in each deployment. So,you could conceivably use the same J2EE server for all the deployments, or severaldifferent J2EE servers.

If you use Windows Remote Desktop Connection to log in to the Windows systemusing the new development user ID, you need to add it to the Remote DesktopUsers group.

Procedure1. Create a separate, non-administrative user ID on the administrative workstation

for each installation.2. Launch the product installation program while logged in as the

non-administrative system user ID to create a local instance of the deploymentengine instance.

3. Proceed through the installation program panels as directed. When you get tothe Choose Install Folder panel, use a meaningful directory name thatrepresents the purpose of this deployment. During the pre-installationprocessing phase of the installation process, a local deployment engine instanceis created.

4. In the Specify Install Folder screen, specify a directory that is separate from allother Asset Management for IT installation directories on the sameadministrative workstation.

5. Complete the installation as normal. The installation program creates a TivoliAsset Management for IT folder, with Maximo Console and Process SolutionInstaller shortcuts, on your desktop.


6. Double-click Maximo Console in the newly created Tivoli Asset Managementfor IT folder to log in to the product and verify applications are present. Theability to log into the user interface manually is a good indicator that theinstallation was successful. Once you have logged in, navigate through the Goto menu to verify that it has been populated with the applications you expect.

Results

The product is now installed using a local deployment engine instance. Repeatthese steps for each subsequent installation on the same workstation, using adifferent non-root user ID and installation directory.

To perform an uninstall, you must change directory toLOCAL_DE_PRODUCT_INSTALL_HOME\_uninstall and then run the uninstall.[bat|sh]script to uninstall that instance of the product.

Example

In this example, the product is installed in a directory called C:\IBM\development\SMP and is intended for use as a development environment.1. Create the non-administrative system user ID for the development installation.

This system user must have write access to the installation directory, but mustnot be a member of the system administrator group. In this example, we createa user named development. If you use Windows Remote Desktop Connection tolog in to the system with this user ID, add the ID to the Remote Desktop Usersgroup.

2. Log in to the system using the development user ID3. Launch the installation program and proceed through the introductory screens

of the installation wizard. This phase of the installation creates a local instanceof the deployment engine in the %USERPROFILE%\acsi_%USERNAME% directory. Inthis example, the instance is created at C:\Documents and Settings\development\acsi_development.

4. Proceed through the installation wizard screens. When you get to the ChooseInstall Folder screen, use a meaningful directory name that represents thepurpose of this deployment. It can be useful to create an installation directorybased on the user ID associated with this installation, for example,C:\IBM\SMP\development.

5. Verify the installation by opening the newly created Tivoli Asset Managementfor IT folder, double-clicking Maximo Console, and confirming that theapplications you expect are present.

6. Repeat these steps for each subsequent installation on the same workstation.For each installation, use a different non-administrative user ID, andinstallation directory to avoid conflict with other deployments.


Chapter 18. Starting and stopping middleware

This procedure describes how to start and stop middleware on your operatingsystem, should you need to restart any middleware services, such as when areboot occurs. Middleware servers and services must be active before running theTivoli Asset Management for IT installation program.

Starting middleware on WindowsAbout this task

Windows To properly start middleware products on Windows, perform thefollowing steps:

Procedure1. Log in as a user with administrative authority.2. Start servers by executing the following scripts in the order in which they are

listed:a. Start ctginst1.

1) Click Start, and select Run.2) Type services.msc, and click OK.3) Select DB2 - DB2COPY1 - CTGINST1-0, and click Start the service.

Alternatively, you can use the db2start command from a command line tostart CTGINST1.

b. Start IBM Tivoli Directory Server Admin Daemon:1) Click Start, and select Run.2) Type services.msc, and click OK.3) Select IBM Tivoli Directory Admin Daemon V6.2 - idsccmdb, and click

Start the service.

Alternatively, you can use the following command from the command lineto start the Directory Server admin daemon:idsdiradm -I idsccmdb

c. Start the IBM Tivoli Directory Server instance:1) Click Start, and select Run.2) Type services.msc, and click OK.3) Select IBM Tivoli Directory Server Instance V6.2 - idsccmdb, and click

Start the service.

Alternatively, you can use the following command from the command lineto start the Directory Server instance:idsslapd -I idsccmdb

Important: The Directory Server instance must remain as a manual startuptype. It must be started manually in order to synchronize correctly with thedatabase in the context of Tivoli Asset Management for IT.

d. Start IBM HTTP Server and webserver1:1) Click Start and select Run

2) Type services.msc, and click OK.


3) Select IBM HTTP Server 6.1, and click Start the service.

Alternatively, you can type apache from the command line to start theHTTP Server.

e. Start Domain Manager:was_install_dir\profiles\ctgDmgr01\bin\startManager.bat

f. Start Node:was_install_dir\profiles\ctgAppSvr01\bin\startNode.bat

g. Start MXServer:was_install_dir\profiles\ctgAppSrv01\bin\startServer.bat MXServer

Starting middleware on UNIXAbout this task

UNIX To properly start middleware products on Linux and UNIX systems,perform the following steps:

Procedure1. Log in as root.2. Start servers by executing the following scripts:

a. Start ctginst1 instance:su - ctginst1 -c db2start

b. Start IBM Tivoli Directory Server Admin Daemon:itds_install_dir/sbin/idsdiradm -I idsccmdb

c. Start IBM Tivoli Directory Server server daemon: ibmslapditds_install_dir/sbin/ibmslapd -I idsccmdb

d. Start HTTP Server

Linux Linux:/opt/IBM/HTTPServer/bin/apachectl start

AIX AIX:/usr/IBM/HTTPServer/bin/apachectl start

Solaris Sun Solaris:/opt/IBM/HTTPServer/bin/apachectl start

e. Start Deployment Manager:was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

f. Start Node:was_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

g. Start webserver1:was_install_dir/profiles/ctgAppSrv01/bin/startServer.sh webserver1-username was_user-password was_password

h. Start MXServer:was_install_dir/profiles/ctgAppSrv01/bin/startServer.sh MXServer-username was_user-password was_password


Stopping middleware on WindowsAbout this task

Windows To properly stop middleware products on Windows, perform thefollowing steps:

Procedure1. Log in as a user with administrative authority.2. Stop servers by executing the following scripts:

a. Stop Node:was_install_dir\profiles\ctgAppSvr01\bin\stopNode.bat

Note: If this process has been configured to run as a service (per theinstructions in “Configuring the WebSphere node agent to run as aWindows service” on page 322), stop the service this way instead:1) Click Start → Services → Control Panel.2) Click IBM WebSphere Node Agent.3) Right click and click Stop.

b. Stop MXServer:was_install_dir\profiles\ctgAppSrv01\bin\stopServer.bat MXServer-username was_user-password was_password

Note: If this process has been configured to run as a service (per theinstructions in “Configuring the WebSphere Application Server to run as aWindows service” on page 320, then stop the service this way instead:1) Click Start → Services → Control Panel.2) Click IBM WebSphere.3) Right click and click Stop.

Note: Unless you changed the installation locations, the following are thedefault values:

http_server_install_dirC:\Program Files\IBM\HTTPServer\bin

was_install_dirC:\Program Files\IBM\WebSphere\AppServer

Stopping middleware on UNIX systemsAbout this task

UNIX To properly stop middleware on AIX and LINUX, perform the followingsteps:

Procedure1. Log in as root.2. Stop servers by executing the following scripts:

a. Stop node:was_install_dir/profiles/ctgAppSrv01/bin/stopNode.sh

b. Stop MXServer:

Chapter 18. Starting and stopping middleware 315

was_install_dir/profiles/ctgAppSrv01/bin/stopServer.shMXServer -username was_user -password was_password


Chapter 19. IBM WebSphere Application Server management

IBM provides comprehensive information about running and administering IBMWebSphere Application Server.

Go to the WebSphere Application Server Information Center to read more.

Starting the MXServer application server from the command lineAfter you created an application server named MXServer during installation (eithermanually or automatically), you can start it to get it into operational mode.

About this task

To start the MXServer application , complete the following steps:

Procedure1. Start the Deployment Manager:

UNIX

UNIX: was_install_dir/AppServer/profiles/ctgDmgr01/bin/startManager.sh

Windows

Windows:was_install_dir\profiles\ctgDmgr01\bin\startManager.bat

2. Start the Node:

UNIX

UNIX: was_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

Windows

Windows:was_install_dir\profiles\ctgAppSrv01\bin\startNode.bat

3. Start the Web server:

UNIX

UNIX: was_install_dir/profiles/ctgAppSrv01/bin/startServer.shwebserver1 -username username-password password

Windows

Windows:was_install_dir\profiles\ctgAppSrv01\bin\startServer.batwebserver1 -username username-password password

4. Start the application server:

UNIX

UNIX: was_install_dir/profiles/ctgAppSrv01/bin/startServer.sh MXServer-username username-password password


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

Windows

Windows:was_install_dir/profiles/ctgAppSrv01/bin/startServer.bat MXServer-username username-password password

Starting the MXServer application server from the administrativeconsole

An application server named MXServer is created during Tivoli Asset Managementfor IT deployment, either manually, or automatically by the Tivoli AssetManagement for IT installation program.

About this task

To start the MXServer application server from the administrative console, completethe following steps:

Procedure1. Before you start the administrative console, verify that the following server

processes are running. If necessary, use the commands shown from a commandprompt in order to start them.

Table 26. WebSphere Application Server processes.

Server Go To

HTTP ServerWindows

Windows:http_server_install_dir\bin\apache -k start

http_server_install_dir\bin\apache -k stop

UNIX

UNIX: http_server_install_dir/bin/apachectl start

http_server_install_dir/bin/apachectl stop

DeploymentManager Windows

Windows:was_install_dir\profiles\ctgDmgr01\bin\startManager.bat

was_install_dir\profiles\ctgDmgr01\bin\stopManager.bat

UNIX

UNIX: was_install_dir/profiles/ctgDmgr01/bin/startManager.sh

was_install_dir/profiles/ctgDmgr01/bin/stopManager.sh

Node AgentWindows

Windows:was_install_dir\profiles\ctgAppSrv01\bin\startNode.bat

was_install_dir\profiles\ctgAppSrv01\bin\stopNode.bat

UNIX

UNIX: was_install_dir/profiles/ctgAppSrv01/bin/startNode.sh

was_install_dir/profiles/ctgAppSrv01/bin/stopNode.sh


Table 26. WebSphere Application Server processes. (continued)

Server Go To

IBM TivoliDirectory ServerInstance

Windows

Windows:

1. Click Start, and select Run.

2. Type services.msc, and click OK.

3. Select IBM Tivoli Directory Server Instance V6.2 - idsccmdb, andclick Start the service.

UNIX

UNIX: /ldap/V6.2/sbin/ibmslapd -I idsccmdb

Directory ServerDatabase Windows

Windows:

1. Click Start, and select Run.

2. Type services.msc, and click OK.

3. Select DB2 - DB2COPY1 - CTGINST1-0, and click Start the service.

UNIX

UNIX: su - idsccmdb -c db2start

2. To start the administrative console, open a browser window and enter thefollowing URL:http://computer_name:9060/ibm/console

Where computer_name is the host name of the WebSphere Application Serverand 9060 is the default port number for the administrative console.

3. Enter an administrative user ID and password to log in, if one is required.4. From the administrative console navigation pane, click Servers → Application

Servers.5. Select the check box next to MXServer, the name of the WebSphere Application

Server.6. Click Start. Notice that the icon in the Status column changes to running.

Under WebSphere Application Server, click Stop, which will cause the icon inthe Status column to change to stopped.

Securing WebSphere Administrative ConsoleYou can secure the administrative console so that only authenticated users can useit. Virtual Member Manager must have been configured on the WebSphere serverbefore securing the console.

Before you begin

Once you have enabled Virtual Member Manager for WebSphere security, youperform several steps to secure the console. First you identify users (or groups)that are defined in the active user registry. After you decide which users you wantto access the console, you can determine their level of access by assigning roles.The roles determine the administrative actions that a user can perform. Afterenabling security, a user must enter a valid administrator user ID and password toaccess the console.

Chapter 19. WebSphere Application Server management 319

About this task

You can use the Administrative Group Roles page to give groups specific authorityto administer application servers through the administrative console. Simply clickSecurity → Secure administration, applications, and infrastructure →Administrative Group Roles to view the available administrative group roles.

Table 27. Administrative Group Roles and their descriptions.Admin Role Description

Administrator Has operator permissions, configurator permissions, and the permission that isrequired to access sensitive data.

Operator Has monitor permissions and can change the runtime state. For example, theoperator can start or stop services.

Configurator Has monitor permissions and can change the application server configuration.

Monitor Has the least permissions. This role primarily confines the user to viewing theapplication server configuration and current state.

Deployer Users granted this role can perform both configuration actions and runtimeoperations on applications.

adminsecuritymanager Fine-grained administrative security is available using wsadmin only. However, youcan assign users and groups to the adminsecuritymanager role on the cell levelthrough wsadmin scripts and the administrative console. Using theadminsecuritymanager role, you can assign users and groups to the administrativeuser roles and administrative group roles. However, an administrator cannot assignusers and groups to the administrative user roles and administrative group rolesincluding the adminsecuritymanager role.

iscadmins Has administrator privileges for managing users and groups from within theadministrative console only.

Note: To manage users and groups, click Users and Groups in the consolenavigation tree and then click either Manage Users or Manage Groups.

Complete the following steps to map users and groups to security roles:

Procedure1. Select Applications → Enterprise applications → application_name.2. Under Detail properties, click Security role to user/group mapping.3. Select the role and click either Look up users or Look up groups.

Different roles can have different security authorizations. Mapping users orgroups to a role authorizes those users or groups to access applications definedby the role. Users and groups are associated with roles defined in anapplication when the application is installed or configured. Use the Searchpattern field to display users in the Available list. Click >> to add users fromthe Available list to the Selected list.

4. Restart all the application servers.Related concepts


Configuring the WebSphere Application Server to run as a Windowsservice

Windows If you plan to install a Tivoli Asset Management for IT instance onWindows with WebSphere Application Server, you might want to run theWebSphere Application Server as a Windows service.


About this task

To configure the WebSphere Application Server to run as a Windows service,complete the following steps:

Procedure1. Start the WebSphere Administrative Console by opening a browser window

and entering the following URL:http://computer_name:9060/ibm/console

2. Enter an administrative user ID and password.3. Click Servers → Application Servers in the navigation pane.4. In the Application Servers pane, select MXServer and click Start. This action

creates a server log folder used by the WASService command.5. Select MXServer, and click Stop.6. Open a command prompt window.7. Navigate to the bin folder where you installed the Maximo application server.

For example:C:\Program Files\IBM\WebSphere\AppServer\bin

8. Run the WASService command with the following parameters:

serverNameMaximo application server name, MXServer.

profilePathThe profile directory of the server, for example,C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01

wasHomeHome folder for MXServer, for example,C:\Program Files\IBM\WebSphere\AppServer\profiles

logRootFolder location of MXServer log file, for example,C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ctgAppSrv01

logFileLog file name for MXServer (startServer.log)

restartRestarts the existing service automatically if the service fails when set totrue.

9. Enter the WASService command using the following syntax:WASService add MXServer serverName MXServerprofilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01wasHome <D:>\IBM\WebSphere\AppServerlogRoot C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ctgAppSrv01logFile C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ctgAppSrv01\startServer.log restart true

10. Press Enter after you type the WASService command. A confirmation messageis displayed.

11. Open a Services window and double-click MXServer. Then perform thefollowing actions:a. Change the Startup type field value to Automatic.b. Click Start to start the service.


c. Click OK.

Configuring the WebSphere node agent to run as a Windows serviceWindows A node agent is a server running on every host computer in the

deployed network. It performs administrative functions.

About this task

To configure the IBM WebSphere Application Server node agent to run as aWindows service, complete the following steps:

Procedure1. Start the WebSphere Administrative Console by opening a browser window

and entering the following URL:http://computer_name:9060/ibm/console

2. Enter an administrative user ID and password.3. Click System Administration in the navigation pane.4. In the System Administration pane, select the name of the Node Agent (for

example, nodeagent), and click Start.5. Before you run the WASService command, select nodeagent in the

Administration pane, and click Stop.6. Open a command prompt window.7. Navigate to the bin folder where you installed the Node Agent. For example:

C:\Program Files\IBM\WebSphere\AppServer\bin

8. Run the WASService command with the following parameters:

serverNameThe name of node agent, for example, nodeAgent

profilePaththe profile directory of the server, for example,C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01

wasHomeHome folder for MXServer. For example,C:\Program Files\IBM\WebSphere\AppServer\profiles

logRootFolder location of node agent log file, for example,C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ctgAppSrv01

logFileLog file name for node agent (startServer.log)

restart Restarts the existing service automatically if the service fails when setto true.

9. Enter the WASService command using the following syntax:WASService add NodeAgent serverName nodeagent profilePathC:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01wasHome <D:>\IBM\WebSphere\AppServerlogRoot <D:>\IBM\WebSphere\AppServer\logs\nodeagentlogFile <D:>\IBM\WebSphere\AppServer\logs\nodeagent\startServer.log restart true


10. Press Enter after you type the WASService command, to see a confirmationmessage.

11. Open a Services window and double-click the Node Agent service, forexample, nodeAgent. Then perform the following actions:a. Change the Startup type field value to Automatic.b. Click Start to start the service.c. Click OK.

Creating WebSphere Application Server Network Deployment clusterThis section contains information about creating a WebSphere Application ServerNetwork Deployment cluster.

About this task

You might want to manually create WebSphere Application Server NetworkDeployment cluster to host IBM Tivoli Asset Management for IT. There are twoapproaches; using a default or existing application server template, or creating thecluster using an existing application server as the first cluster member (see Figure 2on page 11).

When creating a cluster, you have a few options for determining the first member.The template you choose is replicated and used for all other members of thecluster.

Procedure1. Log in to the WebSphere Application Server Network Deployment

administrative console.2. From the WebSphere Application Server Network Deployment administrative

console navigation pane, select Servers → Clusters

3. Click New.4. From the Enter basic cluster information page, enter a new Cluster name for

the new member, and then click Next.5. From the Create first cluster member page, enter a name for the new member

and select the first member node from the Select node drop-down menu.6. If you want to create all cluster members based upon the application server

created when Tivoli Asset Management for IT was installed, select MXServerfrom the Create the member using an application server template drop-downmenu. In this case, the fields for member name and node name is disabled andset to values for MXServer. Otherwise, you can select default from the Createthe member using an application server template drop-down menu, whichcreates cluster members based upon the default application server template. Inthis case, you need to manually install the Tivoli Asset Management for ITapplications.

7. Click Next.8. From the Create additional cluster members page, you can add additional

cluster members by typing a new member name and selecting the node for themember. Click Next when finished.

9. On the summary panel, click Finish.


Related concepts

“Deployment topologies” on page 10A typical deployment lifecycle typically begins with a single-server topology thatwould move through phases of demonstration, functional proof-of-concept, andtesting integration within the existing environment. It then gradually movestowards a pilot multi-server environment before finally implementing a productiondeployment within the enterprise.


Chapter 20. IBM WebSphere Portal Server overview

An existing IBM WebSphere Portal Server system can be configured to work withyour IBM WebSphere Application Server deployment after it has been successfullyinstalled.

You can access IBM Tivoli Asset Management for IT applications through theWebSphere Portal Server interface transparently, centralizing Tivoli AssetManagement for IT application access alongside other service-oriented applicationsused by your organization.

WebSphere Portal Server needs to be hosted on a system other than the systemhosting the Tivoli Asset Management for IT J2EE server. WebSphere Portal Servermust be configured to use a version of WebSphere Application Server that itsupports.

Tivoli Asset Management for IT deployed on WebSphere Portal ServerAfter IBM Tivoli Asset Management for IT has been deployed, the user interfacefor any application can be accessed through a portlet hosted on an existingWebSphere Portal Server instance.

Before you begin

The following EAR files are deployed by the Tivoli Asset Management for ITinstallation and the process solution installation programs and are candidates forbeing modified, rebuilt, and redeployed:

Table 28. Tivoli Asset Management for IT EAR and WAR files

EAR File Description Location

maximo.ear This EAR file contains themaximo.war file whichincludesTivoli Asset Managementfor IT base tasks.

tamit_install_dir\maximo\deployment\default

maximohelp.ear This EAR file contains themaximohelp.war file which is forTivoli Asset Management for ITHelp

tamit_install_dir\maximo\deployment\default

About this task

To create a page with a portlet for an Tivoli Asset Management for IT applicationyou want to access through WebSphere Portal Server, ensure that you have aworking and active Tivoli Asset Management for IT deployment, and thencomplete the following steps:

Procedure1. From the Tivoli Asset Management for IT administrative workstation, open a

Web browser and access the WebSphere Portal Server administration tool:http://host_name:port_number/wps/portal

2. Log in as the WebSphere Portal Server administrator.


3. From the WebSphere Portal Server welcome page, click Administration, foundat the bottom of the user interface.

4. From the WebSphere Portal Administration page, click Web Modules, foundunder the Portlet Management heading of the navigation pane.

5. From the Manage Web Modules page, you see a table listing all the webmodules that have been installed on the server. Click Install to install a newmodule.

6. From the Select War File page, using the Browse button, locate the TivoliAsset Management for IT WAR file you intend to deploy. WAR files arelocated on the Tivoli Asset Management for IT administrative system. Onceyou have located the intended WAR file, click Next. In this example, we aredeploying the WAR file maximo.war.

7. From the WAR file content summary page, review the WAR file contents, andthen click Finish.v If the deployment is successful, the Manage Web Modules page is displayed

. A message is displayed confirming that the WAR file was correctlydeployed.

v For each WAR file you deploy, you need to edit itsmaximointegration.properties file. This file is found in the deploymentdirectory created after the deployment of each WAR, under the WEB-INFdirectory.

8. Open the appropriate maximointegration.properties file in a text editor, andedit the following properties:

maximo_host_nameEnsure that this value is the same as the host name used to access theMaximo servlet on WebSphere Application Server.

maximo_portEnsure that this value is the same as the port used to access the Maximoservlet on WebSphere Application Server.

maximo_url_protocolThis value defaults to http, but do not change it to https in order to accessa secure environment.

Repeat the process of editing the maximointegration.properties file for everyWAR file you deploy in WebSphere Portal Server.The next step is to create a page and place a portlet for the Tivoli AssetManagement for IT application on a new portal page.

9. Click Administration, found at the bottom of the user interface.10. Click Manage Pages, found under the Portal User Interface heading of the

navigation pane.11. From the Manage Pages page, click the Context Root entry found in the My

Pages table.12. Click New Label.13. Enter Tivoli Asset Management for IT 7.2.2 in the Title field of the Page

Properties window, and then click OK.14. From the Pages in Context Root table of the Manage Pages page, click Tivoli

Asset Management for IT 7.2.2.15. Click New Page.16. In the Title field of the Page Properties window, enter a title that identifies the

Tivoli Asset Management for IT application, for example, Change for theChange application, and then click OK.


17. Click the Edit Page Layout icon located to the right of the new entry in thePages in Tivoli Asset Management for IT 7.2.2 table.

18. From the Edit Layout page, click Add Portlets.19. Use the search feature of this page to locate the appropriate portlet, select it in

the table, and then click OK.20. From the Edit Layout page, click Done.

What to do next

You can now launch the portlet from the WebSphere Portal Server Launch menu.

Chapter 20. WebSphere Portal Server overview 327


Chapter 21. Uninstalling the middleware

You need to use the middleware installer to uninstall any IBM Tivoli AssetManagement for IT middleware installed by the Tivoli middleware installer.

Before you begin

The middleware installer creates a registry when installing Tivoli AssetManagement for IT middleware. If you use the native middleware uninstallprograms, this registry is out of sync with what is deployed. It causes errors if youthen try to reinstall the middleware using the middleware installer. At pointsduring the uninstall process, the middleware installer uninstall progress bar mightappear to pause. It is normal behavior. In most cases, the middleware installeruninstall progress bar will resume shortly after pausing. If you suspect youruninstall process has experienced an error, refer to the “Tivoli middleware installerlogs” on page 289.

About this task

To uninstall the application server, ensure the directory server (IBM TivoliDirectory Server or Microsoft Active Directory) is active. Do not uninstall thedirectory server until the J2EE server has been uninstalled.

To undeploy Tivoli Asset Management for IT middleware, complete the followingsteps:

Procedure1. Log in as Administrator on Windows and root on Linux, AIX and Sun Solaris.2. Launch the middleware installer from the Launchpad.

a. Start the Launchpad: On the DVD titled “Tivoli Asset Management for IT7.2.2”, navigate to the root directory of the product disc or the downloadedinstallation image, and run the command: launchpad.[exe|sh], dependingon the operating system.

b. In the Launchpad navigation pane, click Install the Product.c. Click the middleware link under 1. Install the middleware.

3. Select a language for the installation and click OK.4. From the Welcome panel, click Next. The middleware installer license

agreement window is displayed.5. Read the license information and select I accept both the IBM and the

non-IBM terms if you agree with the terms. Click Next.6. From the Choose Workspace panel, specify the workspace directory containing

the currently deployed plan, and then click Next. The default location for theworkspace is the last workspace location specified. The default location for theworkspace is c:\ibm\tivoli\mwi\workspace.

7. From the Select Operation panel, select Undeploy the plan, and then clickNext.

8. From the undeployment preview panel, click Next to undeploy the plan.9. From the successful undeployment panel, click Next to select a new operation,

such as redeploying components, or click Cancel to exit the middlewareinstaller.


Related tasks

Chapter 22, “Uninstalling Tivoli Asset Management for IT,” on page 331The procedures and instructions provided here are based upon a scenario in whichthe IBM Tivoli Asset Management for IT installation program has experienced anerror or failure.


Chapter 22. Uninstalling Tivoli Asset Management for IT

The procedures and instructions provided here are based upon a scenario in whichthe IBM Tivoli Asset Management for IT installation program has experienced anerror or failure.

Before you begin

Tivoli Asset Management for IT uninstallation is a comprehensive procedure anddoes not support partial removal of individual components or process managers,including process managers deployed by other products. If you have deployed aproduct that includes process managers before you deployed the product, and youwant to uninstall Tivoli Asset Management for IT, be advised that doing soremoves the process managers deployed with the other product.

Run the uninstallation program once only. If there are errors, messages aregenerated that indicate conditions that you need to resolve manually beforeattempting a reinstall. It also includes manually removing files from theadministrative workstation.

Tivoli Asset Management for IT can only be uninstalled using the Tivoli AssetManagement for IT uninstallation program as directed. Do not use other methodsto attempt to uninstall the product, such as using the Add/Remove Programspanel.

About this task

The uninstall procedure you follow depends on the type of the deployment youare uninstalling. For uninstallation purposes, Tivoli Asset Management for ITdeployments fall into one of the following categories:

Fully-automated configurationIn this scenario, you selected the option to allow the installation programto automatically configure middleware during deployment.

Manual configurationIn this scenario, you selected the option to manually configure middleware.You did not allow the installation program to automatically configuremiddleware during deployment.

What to do next

After the Tivoli Asset Management for IT uninstall process is complete, you canreinstall the product by restarting the installation program.

Uninstalling an automatically configured Tivoli Asset Management forIT deployment

Uninstall a Tivoli Asset Management for IT deployment that was deployed usingthe automatic middleware configuration options.


Running the IBM Tivoli Asset Management for IT uninstallationprogram for automatically configured middleware

Running the Tivoli Asset Management for IT uninstallation program reverts theadministrative system and middleware servers back to a state where you can rerunthe Tivoli Asset Management for IT installation program.

Before you begin

Ensure that all applicable services are running and all middleware servers areaccessible.

The Tivoli Asset Management for IT uninstallation program must be able to accessthe database used with Tivoli Asset Management for IT to fetch installationproperties and configuration data. If the Tivoli Asset Management for ITuninstallation program cannot access the database because it is unavailable,corrupted, or otherwise inaccessible, then the Tivoli Asset Management for ITuninstallation program removes files from the administrative workstation andinform you that some manual recovery might be required before another TivoliAsset Management for IT installation can be successful.

The uninstallation program uses values entered during the initial installation. Ifcredentials used to access the database and J2EE server are still valid, you are notprompted to enter them again. If the uninstallation program is unable to validatethese credentials, you are prompted to supply the updated information. Theuninstallation program cannot validate credentials if you updated passwords afterthe original installation.

To run the Tivoli Asset Management for IT uninstallation program:

Procedure1. To run the Tivoli Asset Management for IT uninstallation program, from the

administrative workstation, open a command prompt and issue the followingcommand:

Windows<MAM_HOME>\_uninstall\uninstall.bat

UNIX<MAM_HOME>\_uninstall\uninstall.sh

2. From the Application Server Information panel, enter the following informationand then click Next.

Remote user IDEnter a user ID in order to access the system hosting the applicationserver. The remote user ID must be able to access the server using theremote access protocol enabled on that system.

Remote passwordEnter a password for the remote user ID.

User IDEnter the password for the application server administrator.

PasswordEnter the password for the application server administrator user ID.

3. From the database administration panel, for DB2, enter the followinginformation and then click Next.


Remote user IDEnter a user ID in order to access the system hosting the database. Theremote user ID must be able to access the server using the remoteaccess protocol enabled on that system.

Remote passwordEnter a password for the remote user ID.

Instance administrator user IDEnter the database instance administrator user ID that you type duringthe installation.

Instance administrator passwordEnter the password for the database instance administrator user ID.

For Oracle databases, you can supply the credentials for the Administrator userID and the Oracle software owner ID. For Microsoft SQL Server databases, youcan supply the SQL Server administrator user ID and password.

4. Review the components that are listed in the uninstallation summary panel,and then click Uninstall.

5. After the uninstallation process has completed, specify whether you want torestart the computer now or later, and click Done to exit the program.

6. Check to ensure that the uninstallation program removed the Tivoli AssetManagement for IT installation directory (tamit_install_dir), for example,c:\ibm\smp. If the Tivoli Asset Management for IT installation failed early inthe process, the Tivoli Asset Management for IT uninstallation program mightnot remove the Tivoli Asset Management for IT installation directory. If thisdirectory still exists after you have completed the uninstallation process, youwill have to remove it manually before you proceed to the reinstallationprocess.

Uninstalling a manually configured IBM Tivoli Asset Management for ITdeployment

Uninstalling a manually configured Tivoli Asset Management for IT deploymentconsists of running the Tivoli Asset Management for IT uninstallation program,and then manually dropping and recreating the database you intend to use withthe reinstall process.

Running the IBM Tivoli Asset Management for IT uninstallationprogram for a manually configured deployment

Running the Tivoli Asset Management for IT uninstallation program reverts theadministrative system and middleware servers back to a state where you can rerunthe Tivoli Asset Management for IT installation program.

Before you begin

Ensure that all applicable services are running and all middleware servers areaccessible.

The Tivoli Asset Management for IT uninstallation program must be able to accessthe database used with Tivoli Asset Management for IT to fetch installationproperties and configuration data. If the Tivoli Asset Management for ITuninstallation program cannot access the database because it is unavailable,corrupted, or otherwise inaccessible, then the Tivoli Asset Management for ITuninstallation program removes files from the administrative workstation and

Chapter 22. Uninstalling Tivoli Asset Management for IT 333

inform you that some manual recovery might be required before another TivoliAsset Management for IT installation can be successful.

If you have not changed passwords that were used for the initial installation, youdo not have to enter values for password fields in the uninstallation program.

About this task

To run the Tivoli Asset Management for IT uninstallation program:

Procedure1. Open a command prompt and issue the following command, depending on

your operating system:tamit_install_dir\_uninstall\uninstall.[exe|sh]

2. From the Introduction panel, read the introductory information and then clickNext.

3. From the application server information panel, enter the following informationand then click Next.

User IDEnter the password for the application server administrator.

PasswordEnter the password for the application server administrator user ID.

4. Review the components that are listed in the uninstallation summary panel,and then click Uninstall.

5. After the uninstallation process has completed, click Done to exit theprogram.

6. Check to ensure that the uninstallation program removed the Tivoli AssetManagement for IT installation directory. If the Tivoli Asset Management forIT installation failed early in the process, the Tivoli Asset Management for ITuninstallation program might not remove the Tivoli Asset Management for ITinstallation directory. If this directory still exists after you have completed theuninstallation process, remove it manually before you proceed to thereinstallation process.

7. After the uninstallation process has completed, specify whether you want torestart the computer now or later, and click Done to exit the program.

8. Using Windows services, stop IBM ADE Service.9. To delete the service, use the following command: sc delete acsisrv.

10. Go to Program Files → IBM → Common and delete the asci folder.11. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ acsisrv and

remove the registry keys if any exist.12. Restart the computer.

What to do next

You can now proceed with recovery of your manually configured database.

IBM Tivoli Asset Management for IT database configurationrecovery

Database objects that you created before running the Tivoli Asset Management forIT installation program must be deleted after a failed installation before you canrerun the Tivoli Asset Management for IT installation program again.


Before you begin

Before rerunning the Tivoli Asset Management for IT installation program, youneed to drop the Tivoli Asset Management for IT database and recreate it.

Restoring the DB2 database serverIn order to rerun the IBM Tivoli Asset Management for IT installation program,you need to first restore the DB2 database server to the same state as before TivoliAsset Management for IT was installed.

Before you begin

Ensure that the MXServer application server on WebSphere Application Server isstopped before dropping the database.

About this task

Restoring the DB2 database server to the same state as before Tivoli AssetManagement for IT was installed, requires you to drop the Tivoli AssetManagement for IT database that you manually created and then recreate it beforererunning the Tivoli Asset Management for IT installation program.

To restore the Tivoli Asset Management for IT database, complete the followingsteps:

Procedure1. Log on to the system hosting the DB2 server.2. Start a DB2 command session or run db2cmd from the command prompt.3. First list and then force all applications connected to the database to close using

the following commands:a. To list applications, type this command:

db2 list applications

You might see output like the following sample output:Auth Id Application Appl. Application Id DB # ofName Handle Name Agents-------- ----------- ------- ---------------------------- ------- -----CTGINST1 db2taskd 507 *LOCAL.DB2.071113150237 MAXDB71 1CTGINST1 db2stmm 506 *LOCAL.DB2.071113150236 MAXDB71 1CTGINST1 db2bp 504 *LOCAL.ctginst1.071113150234 MAXDB71 1

b. If any connections exist, close the connect application using a command likethe following sample command:db2 force application ’( 507,506,504 )’

4. Drop the Tivoli Asset Management for IT database (MAXDB71, by default):db2 drop database MAXDB71

5. Manually recreate the MAXDB71 database.


Related tasks

“Manually configuring DB2 9.x” on page 130For better performance, you might need to manually configure IBM DB2 9.x beforerunning the IBM Tivoli Asset Management for IT installer to set the preferableenvironment on different operating systems.“Manually configuring DB2 8.2” on page 134This section contains instructions for manually configuring DB2 8.2 servers for useby IBM Tivoli Asset Management for IT. Tivoli Asset Management for IT supportsIBM DB2 8.2 only when manually configured.

Restoring the Oracle databaseIn order to rerun the IBM Tivoli Asset Management for IT installation program,you need to first restore the Oracle database server to the same state as beforeTivoli Asset Management for IT was installed.

Before you begin

Ensure that the MXServer application server on WebSphere Application ServerNetwork Deployment is stopped before deleting the database.

About this task

Restoring the Oracle database server to the same state as before Tivoli AssetManagement for IT was installed, requires to drop the Tivoli Asset Managementfor IT database that you manually created, and then recreate it before rerunningthe Tivoli Asset Management for IT installation program.


Procedure1. Log in to the Oracle database server as the Oracle software owner.2. Log in to the Oracle instance using SQLPlus as a DBA user: Oracle SID for a

clean install is ctginst1. If you are using an existing Oracle instance with TivoliAsset Management for IT, use the Oracle SID associated with the existinginstance.

Linux UNIX:

a. Set the environment variable from the command line:ORACLE_SID=your_SIDexport ORACLE_SID

b. Invoke SQLPlus from the command line:sqlplus /nolog

c. Log in to SQLPlus as a DBA user:connect sys/sys_password as sysdba

Windows Windows:

a. Set the environment variable from the command line:ORACLE_SID=your_SID




3. Delete the Tivoli Asset Management for IT database user (maximo, by default)using an SQL command like the following sample command:drop user maximo cascade;

Do not disconnect from the database. If you receive an error when issuing thiscommand that you cannot drop a currently connected user, issue the followingSQL commands and then try the SQL drop command again:shutdown immediate;startup;

4. Manually recreate the database. Refer to “Manually configuring Oracle 10g” onpage 141 or “Manually configuring Oracle 9i Rel2” on page 143 for moreinformation.

Restoring the Microsoft SQL Server databaseIn order to rerun IBM Tivoli Asset Management for IT installation program, youneed to first restore the Microsoft SQL Server database server to the same state asbefore Tivoli Asset Management for IT was installed.

Before you begin


About this task

Restoring the Microsoft SQL Server database server to the same state as beforeTivoli Asset Management for IT was installed, requires you to drop the Tivoli AssetManagement for IT database that you manually created and then recreate it beforererunning the Tivoli Asset Management for IT installation program.


Procedure1. Open the Microsoft SQL Server Management Studio.2. Log in to the instance of Microsoft SQL Server that is used by Tivoli Asset

Management for IT install using the sa user ID, and then click Connect.3. To delete the database, expand the instance tree down to the databases

category, right-click the database name you created during installation (MAXDB71for example), and then click Delete.

4. In the Delete Object window, select Delete backup and restore historyinformation for databases and Close existing connections, and then click OK.

5. Manually recreate the MAXDB71 database. Refer to Manually configuring SQLServer for more information.

Uninstalling the product without the uninstallation programWhen a Tivoli Asset Management for IT installation fails without producing anuninstallation program, you can still recover the Deployment Engine, yourdatabase configuration, and the Process Manager configuration, and run yourinstallation again.

If the installation program has experienced a failure that causes it to not producethe product uninstallation program, you must perform additional manualuninstallation tasks.


If you are not able to uninstall Tivoli Asset Management for IT using theseprocedures:v “Uninstalling an automatically configured Tivoli Asset Management for IT

deployment” on page 331, orv “Uninstalling a manually configured IBM Tivoli Asset Management for IT

deployment” on page 333

You can uninstall the product without using the uninstallation program by doingthe following procedures:1. “Recovering the Deployment Engine”2. Recover the database as described in “IBM Tivoli Asset Management for IT

database configuration recovery” on page 334.3. “Recovering the Asset Management for IT Process Manager configuration” on

page 3434. Manually remove files from the system as described in “Removing files from

the system” on page 345.

Recovering the Deployment EngineDepending on your specific scenario you might restore a previous backup of theDeployment Engine registry or remove the Deployment Engine completely.

About this task

Recovering the Deployment Engine can result in loss of registration informationabout installed software components, which includes both Tivoli AssetManagement for IT and non-Tivoli Asset Management for IT components. Thissituation causes the Deployment Engine registry to not accurately reflect the stateof the system. Before using these uninstallation instructions or scripts, read thefollowing information to determine the ramifications of these operations to yourenvironment.

There are two primary recovery scenarios:

Recovery from a partial installation in which no PMPs were registered in theDeployment Engine registry

To determine if Tivoli Asset Management for IT components have beendeployed and registered in the Deployment Engine registry, use theshowinstalled action of the process solution installation programcommand-line interface (see “showinstalled action - list installedpackages” on page 214).cd tamit_install_dir\binsolutionInstaller -action showinstalled -type all

The CTGIN0059I informational message indicates which PMPs areinstalled. If no PMPs have been installed, the installation failure occurredbefore PMPs were installed and registered in the Deployment Engineregistry. If no PMPs are installed you do not uninstall the DeploymentEngine or restore a previous backup. The current Deployment Engineregistry must be preserved and does not prohibit installation of the PMPsduring the subsequent installation.

Recovery from a partial or full installation in which one or more Tivoli AssetManagement for IT PMPs were registered in the Deployment Engine registry

If the showinstalled results indicate that there are one or more PMPs


installed, then you must determine if there are other non-PMP componentsregistered in the Deployment Engine Registry.

Within this case, there are two separate scenarios:

The Deployment Engine registry was backed up before installing TivoliAsset Management for IT

If you have a backup of the Deployment Engine database, createdusing the procedure described in “Backing up the DeploymentEngine database” on page 34, you can use the following commandto restore it:

Windows Windowsc:\Program Files\IBM\Common\acsi\bin\restoredb backup_file_name

UNIX UNIXcd /usr/ibm/common/acsi/bin./restoredb.sh backup_file_name

where backup_file_name is the file containing the DeploymentEngine backup you made. Restore the Deployment Enginedatabase backup after completing the steps to remove the ProcessManager configuration. You must not uninstall Deployment Enginebefore reinstalling Tivoli Asset Management for IT.

The Deployment Engine registry was not backed up before installingTivoli Asset Management for IT

If you do not have a backup of the Deployment Engine registry,the action you take depends on other non-PMP componentsregistered in the Deployment Engine registry. If you used the TivoliAsset Management for IT middleware installation program todeploy middleware to the Maximo administration workstation,then you do indeed have non-PMP components in the DeploymentEngine registry.

You can list the contents of the Deployment Engine registry usingthe following command:

Windows WindowsC:\Program Files\IBM\common\acsi\bin\listiu

UNIX UNIX/usr/ibm/common/acsi/bin/listiu.sh

The listiu command result always contains the following entries:IU UUID: DDCE934782398B3E81431666515AC8B5 Name: DE ExtensionsInterfaces CLI IU Version: 1.3.1IU UUID: C37109911C8A11D98E1700061BDE7AEA Name: DeploymentEngine IU Version: 1.3.1IU RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA Name:Install IU Version: 1.3.1

These entries are internal to Deployment Engine. They are notconsidered when evaluating which components are currentlyregistered.

If the only other entries displayed are entries associated with thePMPs shown in the showinstalled results, then only Tivoli AssetManagement for IT components have been registered in theDeployment Engine registry. You can safely uninstall the


Deployment engine using the instructions found in “Uninstallingand reinstalling the Deployment Engine database” on page 346.

If non-PMP registry entries are present, you still must uninstall theDeployment Engine to proceed with Tivoli Asset Management forIT recovery. Be advised that if you used the Tivoli AssetManagement for IT middleware installation program to deploymiddleware to the Maximo administration workstation, you cannotuse it to uninstall the middleware deployed. You also cannotuninstall, upgrade, or apply fixes to any non-PMP software thatwas installed using the Deployment Engine. If this scenario is anunacceptable alternative, your only recourse is to reinstall TivoliAsset Management for IT after reimaging your system.

IBM Tivoli Asset Management for IT database configurationrecovery

Database objects that you created before running the Tivoli Asset Management forIT installation program must be deleted after a failed installation before you canrerun the Tivoli Asset Management for IT installation program again.

Before you begin

Before rerunning the Tivoli Asset Management for IT installation program, youneed to drop the Tivoli Asset Management for IT database and recreate it.

Restoring the DB2 database serverIn order to rerun the IBM Tivoli Asset Management for IT installation program,you need to first restore the DB2 database server to the same state as before TivoliAsset Management for IT was installed.

Before you begin

Ensure that the MXServer application server on WebSphere Application Server isstopped before dropping the database.

About this task

Restoring the DB2 database server to the same state as before Tivoli AssetManagement for IT was installed, requires you to drop the Tivoli AssetManagement for IT database that you manually created and then recreate it beforererunning the Tivoli Asset Management for IT installation program.


Procedure1. Log on to the system hosting the DB2 server.2. Start a DB2 command session or run db2cmd from the command prompt.3. First list and then force all applications connected to the database to close using

the following commands:a. To list applications, type this command:

db2 list applications

You might see output like the following sample output:


Auth Id Application Appl. Application Id DB # ofName Handle Name Agents-------- ----------- ------- ---------------------------- ------- -----CTGINST1 db2taskd 507 *LOCAL.DB2.071113150237 MAXDB71 1CTGINST1 db2stmm 506 *LOCAL.DB2.071113150236 MAXDB71 1CTGINST1 db2bp 504 *LOCAL.ctginst1.071113150234 MAXDB71 1

b. If any connections exist, close the connect application using a command likethe following sample command:db2 force application ’( 507,506,504 )’

4. Drop the Tivoli Asset Management for IT database (MAXDB71, by default):db2 drop database MAXDB71

5. Manually recreate the MAXDB71 database.Related tasks

“Manually configuring DB2 9.x” on page 130For better performance, you might need to manually configure IBM DB2 9.x beforerunning the IBM Tivoli Asset Management for IT installer to set the preferableenvironment on different operating systems.“Manually configuring DB2 8.2” on page 134This section contains instructions for manually configuring DB2 8.2 servers for useby IBM Tivoli Asset Management for IT. Tivoli Asset Management for IT supportsIBM DB2 8.2 only when manually configured.

Restoring the Oracle databaseIn order to rerun the IBM Tivoli Asset Management for IT installation program,you need to first restore the Oracle database server to the same state as beforeTivoli Asset Management for IT was installed.

Before you begin


About this task

Restoring the Oracle database server to the same state as before Tivoli AssetManagement for IT was installed, requires to drop the Tivoli Asset Managementfor IT database that you manually created, and then recreate it before rerunningthe Tivoli Asset Management for IT installation program.


Procedure1. Log in to the Oracle database server as the Oracle software owner.2. Log in to the Oracle instance using SQLPlus as a DBA user: Oracle SID for a

clean install is ctginst1. If you are using an existing Oracle instance with TivoliAsset Management for IT, use the Oracle SID associated with the existinginstance.

Linux UNIX:

a. Set the environment variable from the command line:ORACLE_SID=your_SIDexport ORACLE_SID

b. Invoke SQLPlus from the command line:


sqlplus /nolog


Windows Windows:

a. Set the environment variable from the command line:ORACLE_SID=your_SID



3. Delete the Tivoli Asset Management for IT database user (maximo, by default)using an SQL command like the following sample command:drop user maximo cascade;

Do not disconnect from the database. If you receive an error when issuing thiscommand that you cannot drop a currently connected user, issue the followingSQL commands and then try the SQL drop command again:shutdown immediate;startup;

4. Manually recreate the database. Refer to “Manually configuring Oracle 10g” onpage 141 or “Manually configuring Oracle 9i Rel2” on page 143 for moreinformation.

Restoring the Microsoft SQL Server databaseIn order to rerun IBM Tivoli Asset Management for IT installation program, youneed to first restore the Microsoft SQL Server database server to the same state asbefore Tivoli Asset Management for IT was installed.

Before you begin


About this task

Restoring the Microsoft SQL Server database server to the same state as beforeTivoli Asset Management for IT was installed, requires you to drop the Tivoli AssetManagement for IT database that you manually created and then recreate it beforererunning the Tivoli Asset Management for IT installation program.


Procedure1. Open the Microsoft SQL Server Management Studio.2. Log in to the instance of Microsoft SQL Server that is used by Tivoli Asset

Management for IT install using the sa user ID, and then click Connect.3. To delete the database, expand the instance tree down to the databases

category, right-click the database name you created during installation (MAXDB71for example), and then click Delete.

4. In the Delete Object window, select Delete backup and restore historyinformation for databases and Close existing connections, and then click OK.


5. Manually recreate the MAXDB71 database. Refer to Manually configuring SQLServer for more information.

Recovering the Asset Management for IT Process Managerconfiguration

Use this procedure if your Asset Management for IT installation fails beforeproviding an uninstallation program, and you want to return your system to astate where you can run the installation program again.

Before you begin

Recover the database as described in “IBM Tivoli Asset Management for ITdatabase configuration recovery” on page 334.

About this task

Follow the instructions provided below to recover to the point at which processmanager objects that are created or changed by the Asset Management for ITinstallation can be reinstalled.

The following process managers are installed as part of the Asset Management forIT installation:v Base Servicesv Common

This procedure does not completely reverse all installation actions that havecompleted. This procedure puts the system back to a state where installation of theprocess managers can be attempted again. In this case, the procedure removes anyWAR files deployed by the failed installation. When reinstalling, you cannotdeploy a new WAR file if the old file is still on the system.

You run this procedure on the administrative workstation from a commandprompt. The scripts used in this procedure must be run from the directories wherethey are installed, for example:ISCRemoveHandler.bat: C:\ibm\SMP\jacl\solutions\ISCRemoveHandler.bat

The variable <tamit_home> represents the installation directory for AssetManagement for IT (C:\IBM\SMP or /opt/IBM/SMP, by default).

The ISCRemoveHandler script requires the specification of the IBM WebSphereApplication Server home directory. When specifying this value, you must useforward slashes (/). If the home directory path includes spaces, enclose the valuein double quotation marks.

At the conclusion of step 1, there is a code sample that you can copy into a .cmdfile. You can use this code to complete the tasks described in the step.

Procedure1. Restore Base Services and Common.

The Base Services process manager is located in tamit_home\pmp\base_services_7.1.1.7.zip. To restore the Base Services process manager to astate where it can be reinstalled, complete the following tasks.


Note: You cannot deploy a new WAR file if the old file is still on the system.Manually running ISCRemoveHandler.bat removes the WAR file, if present. If aWAR file is found, you receive a message stating that the WAR file wasremoved and that the batch file ran successfully. If no WAR file is found, youreceive a message that tells you so, and that the batch file ran successfully.a. Start the following script to remove the isccommontasks.war file:

ISCRemoveHandler.bat <WAS_SERVER> <WAS_REMOTE_USER> <WAS_REMOTE_PASSWORD><WAS_HOME> <WAS_USER> <WAS_PASSWORD> isccommontasks.war

WAS_SERVERThe host name of the IBM WebSphere Application Server.

WAS_REMOTE_USERThe user name of a user with administrative access to the serveridentified by WAS_SERVER (Administrator or root, for example).

WAS_REMOTE_PASSWORDThe password associated with WAS_REMOTE_USER.

WAS_HOMEThe directory on WAS_SERVER where the IBM WebSphereApplication Server resides (C:\IBM\WebSphere\AppServer, forexample).

WAS_USERThe administrative user for the IBM WebSphere Application Server(wasadmin, for example).

WAS_PASSWORDThe password associated with WAS_USER.

b. Invoke the following script to remove the PortalLogTraceAnalyzer.war

ISCRemoveHandler.bat <WAS_SERVER> <WAS_REMOTE_USER> <WAS_REMOTE_PASSWORD><WAS_HOME> <WAS_USER> <WAS_PASSWORD> PortalLogTraceAnalyzer.war

WAS_SERVERThe host name of the IBM WebSphere Application Server.

WAS_REMOTE_USERThe user name of a user with administrative access to the serveridentified by WAS_SERVER (Administrator or root, for example).

WAS_REMOTE_PASSWORDThe password associated with WAS_REMOTE_USER.

WAS_HOMEThe directory on WAS_SERVER where the IBM WebSphereApplication Server is installed (C:\IBM\WebSphere\AppServer, forexample).

WAS_USERThe administrative user for the IBM WebSphere Application Server(wasadmin, for example).

WAS_PASSWORDThe password associated with WAS_USER.

Alternatively, you can copy the following sample into a file,u_base_services_PMP.cmd, for example, and run that file to finish this step:@echo all@REM *************** Begin Standard Header - Do not add comments here *****@REM@REM Licensed Materials - Property of IBM@REM


@REM Restricted Materials of IBM@REM@REM 5724-M19@REM@REM (C) COPYRIGHT IBM CORP. 2006, 2010. All Rights Reserved.@REM@REM US Government Users Restricted Rights - Use, duplication or@REM disclosure restricted by GSA ADP Schedule Contract with IBM Corp.@REM@REM **************************** End Standard Header *********************

@rem@rem Parameters:@rem@rem 1: DMGR fully-qualified host name.@rem 2: Administrative user on the DMGR host.@rem 3: Administrative pw for "user" on the DMGR host.@rem 4: WebSphere home directory (enclose in quotes if there are blanks in@rem the path).@rem 5: WebSphere administrative user@rem 6: Password for WebSphere administrative user.@remset HOST=%1set AUSER=%2set APW=%3set WHOME=%4set WUSER=%5set WPW=%6%

if ".%WPW%" equ "." goto BADPARM

call %CTG_TAMIT_HOME%\jacl\solutions\ISCRemoveHandler.bat %HOST% %AUSER%%APW% %WHOME% %WUSER% %WPW% isccommontasks.warcall %CTG_TAMIT_HOME%\jacl\solutions\ISCRemoveHandler.bat %HOST% %AUSER%%APW% %WHOME% %WUSER% %WPW% PortalLogTraceAnalyzer.warexit /b %ERRORLEVEL%

:BADPARMecho offecho *echo * Missing parameter:echo * 1: fully-qualified host name of WebSphere DMGRecho * 2: Administrative user on the DMGR host.echo * 3: Administrative pw for "user" on the DMGR host.echo * 4: WebSphere home directory (enclose in quotes if there are blanks inecho * the path).echo * 5: WebSphere administrative userecho * 6: Password for WebSphere administrative user.exit /b 4

2. Close the command window.

Removing files from the systemIf an uninstallation program is unavailable due to failed installation, product filesmust be manually removed from the system.

About this task

Remove files from the system by completing the following steps:

Procedure1. Ensure that you are logged in to the system with the same user ID used to start

the product installation program.2. Manually delete the product home directory:


Windows WindowsThe default location of this directory is C:\IBM\SMP.

UNIX UNIX sustemsThe default location of this directory is /opt/IBM/SMP.

Uninstalling and reinstalling the Deployment Engine databaseThese instructions are for restoring the Deployment Engine database to the state itwas in before process managers were installed.

Before you begin

See “Recovering the Deployment Engine” on page 338 to determine if you need torestore a backup of the Deployment Engine registry, uninstall the DeploymentEngine, or leave the Deployment Engine installation in its current state. Do notdecide upon an option until you understand the consequences of each of thesechoices.

About this task

If you do not have a backup of the Deployment Engine database, you must resetthe database to a clean state by uninstalling and reinstalling the DeploymentEngine. This is a destructive process. If products other than Asset Management forIT are using Deployment Engine, this deletes data for those products also.

To uninstall and resinstall the Deployment Engine database, complete thefollowing steps:

Procedure1. Open a command-line window on the administrative system.2. Stop the IBM ADE service.

WindowsControl Panel → Administrative Tools → Services → IBM ADE Service

UNIX /usr/ibm/common/acsi/bin/acsisrv.sh -stop

3. Change directory to <ccmdb_home>\de.4. Remove any locks held by Deployment Engine.

erase "c:\Program Files\IBM\Common\acsi\logs\.lock*"

5. Include jre (Java) in the class path:set path=C:\IBM\SMP\jre\bin;%PATH%

6. Uninstall Deployment Engine:si_inst -r -f

7. Reinstall Deployment Engine:si_inst

Results

You can safely ignore warnings that all files and directories cannot be removed.

Alternatively, you can copy the following sample into a file, resetDE.cmd, forexample, and run that file to complete this step:


@echo all@REM *************** Begin Standard Header - Do not add comments here ******@REM@REM Licensed Materials - Property of IBM@REM@REM Restricted Materials of IBM @REM @REM 5724-M19@REM@REM (C) COPYRIGHT IBM CORP. 2006, 2007. All Rights Reserved.@REM@REM US Government Users Restricted Rights - Use, duplication or@REM disclosure restricted by GSA ADP Schedule Contract with IBM Corp.@REM@REM **************************** End Standard Header **********************@rem@rem@rem

erase "c:\Program Files\IBM\Common\acsi\logs\.lock*"set path=%CTG_CCMDB_HOME%\jre\bin;%PATH%call %CTG_CCMDB_HOME%\de\si_inst -r -fcall %CTG_CCMDB_HOME%\de\si_instexit /b %ERRORLEVEL%

Uninstalling IBM Tivoli Asset Management for IT silentlyIn order to uninstall Tivoli Asset Management for IT silently, you need to have avalid response file to use with the uninstallation program.

Before you begin

Note: If the Tivoli Asset Management for IT deployment included Oracleconfiguration, the response file must be edited to remove extraneous backslashes.Refer to “Silent middleware installation options” on page 58 for more information.

Procedure1. Open the response file in a text editor and ensure the INSTALLER_UI property

is set to INSTALLER_UI=silent.2. Copy the response file to the target system.3. Run the Tivoli Asset Management for IT uninstall program in silent mode by

opening a console window on the administrative workstation and using thefollowing command:tamit_install_dir_uninstall\uninstall.exe -f response_file_path

Include the whole path name while specifying the response file.4. After the Tivoli Asset Management for IT uninstall program completes, you can

reinstall by restarting the installation program. After a successful installation,the server you are installing from, the administrative system prompts you toreboot the system.

5. Check to ensure that the uninstall program removed the Tivoli AssetManagement for IT installation installation directory, for example, c:\ibm\smp.If the Tivoli Asset Management for IT installation failed early in the process,the uninstall program might not remove the installation directory. If thisdirectory still exists after you have completed the uninstall process, you need toremove it manually before you proceed to the reinstallation process.



Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 79758 U.S.A

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

Adobe is a registered trademark of Adobe Systems Incorporated in the UnitedStates, and/or other countries.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks ofIntel Corporation or its subsidiaries in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

Notices 351


Index

Special characters–addfeatlist 223, 224–delfeatlist 223, 224-showfeatures 224action parameter 212LANG_SUPT_FEATURE 226

Aaccess collection 19action

install 211showavail 211showinstalled 211undo 211uninstall 211

actions on process solution packagesaction parameter 212

ACUINI0044E 295administrative workstation 1, 9, 199aggregation packages 197AIX

paging space 36AIX file size 36application server

deferred configuration 205applyfix action 219authentication service

configuration 76WebSphere Application Server

Network Deployment 76

CcommandLine command 246configuration

Java Runtime Environment 38remote 33

configuringOracle 107

configuring JMS queuesJMS connection factory 168

confirming the Integration Composerinstallation 244

CQIN JMS queue 169, 170CQINERRBD 171creating JMS activation specification

queues 170CTGIN9042E 301CTGInstallTrace00.log log file 191

Ddata

cron task 266synchronization 266

data sourcemanually creating 173

databaseapplying changes 257

database configurationdatabase

dropping 335, 340recovery 335, 340

database server 1manual configuration 130

database-relateddeferred configuration 205

DB2manual configuration, 8.2 135manual configuration, 9.x 130

DB2 database serverrestoring 335, 340

DB2 fix packsinstallation 65

deployment 9WebSphere Portal Server 325

deployment planinvoking 42

deployment topologymulti-server 10single-server 10

directory server 1Directory Server

reusing 107DVDs 27

EEAR files 9enablement key 249environment data 282error CQINERR JMS queue 172error CTG00001

Tivoli Asset Management for ITuninstallation 309

error CTGIN9042E 300error queues 171

Ffeatures

process solution package 201firewall

disabling 31

Ggeneral ledger account 257general ledger account component 256general syntax

solutionInstaller 211general troubleshooting 285group 55

Hhardware and software requirements,

Integration Composer 236HP-UX 11i middleware

installation 61HTTP server 1

IIBM DB2

reusing 106IBM HTTP Server

configuration 70fix packs

on HP-UX 72on Solaris 72on SUSE Linux Enterprise

Server 72installation 70

IBM Tivoli Asset Management for ITautomatic deployment

reusing middleware 105uninstallation 331

automatically configured 332IBM Tivoli Directory Server 55idsccmdb password 306inbound error queue 171inbound error queue CQINERR 173input.properties 55install action 216install.properties 269installation 79, 85, 311

DB2 fix pack 65HP-UX middleware 61IBM DB2 63IBM Tivoli Integration Composer

with Launchpad 235language packs

with the Launchpad 227language support files 224middleware 39

error codes 291middleware installer logs 289middleware installer workspace 41on Hp-UX 63on Solaris 63on SUSE Linux 11 63overview 85post installation tasks 253, 254, 255,

256, 257, 259, 261prerequisite software products 42prerequisites 31, 80process solution client

command-line interface 211roadmap 85silent 57solution packages 209Tivoli Asset Management for IT 79,

86, 109Tivoli Integration Composer 240


installation (continued)verification 191WebSphere Application Server

Network Deployment 67WebSphere Application Server

plug-ins 74Installation

post installation tasks 258installation prerequisites, Integration

Composer 239installation properties 269installer workspace 41Integration Composer installation

prerequisites 239Integration Composer installation,

confirming 244Integration Composer overview 235Integration Composer requirements,

hardware and software 236Integration Composer, uninstalling 247integration framework

configuring JMS queues 164, 166,167, 169

CQINBD queue 166creating SQOUT JMS queues 170JMS queues configuration 167, 169

interim fix 220Interim Fix Package 219Interim Fixes 221

JJ2EE application server 1J2EE applications 205Java Runtime Environment

configuration 38JMS activation specification

inbound error queue CQINERR 173JMS queues 164

Llanguage enablement 266language support files

for a PMP package 224installation and refreshment 224

languagesdeploying after database update

deferral 230languages support

planning 21Lauchpad

language packs 227Launchpad 85LTPA key password 76

Mmanual

installation 178without middleware

autoconfiguration 178manual configuration

Oracle database 138Maximo applications 205maximo user 63

maximo.properties 269media

installation 27memory allocation

changing 246Microsoft Active Directory

configuration 22reusing 108

Microsoft SQL Serverrestoring 337, 342

middleware 41, 42IBM HTTP Server 70installation 39installer logs 289planning 12reusing 16, 105starting and stopping 313starting on UNIX 314stopping on UNIX 315stopping on Windows 315uninstallation 329

middleware componentsinstallation

UNIX systems 62middleware configuration

manual 129middleware installation

error CTGIN9042E 298on HP-UX 61on Solaris 61on SUSE Linux Enterprise Server 61

middleware installation programtroubleshooting

feature 289multiple 311multiple IBM Service Management

products 308multiple language support

deployment 226features 226

MXServerstarting

from the administrativeconsole 318

from the command line 317

Nnode agents

configuration 322

OOracle

manual configuration, 10g 141manual configuration, 9i 143reusing 107

Oracle 11gmanual configuration 138

Oracle databaserestoring 336, 341

organization 256overview

WebSphere Portal Server 325overview, Integration Composer 235

Ppackages 194persistent store 173planning

middleware 12Tivoli Asset Management for IT 9Tivoli Asset Management for IT

worksheet 17worksheet

middleware 12port 50000 31ports 21post installation tasks

error queues 171IBM DB2

tuning 263post-installation tasks 244

top-level class for ITassets 260software 260

preparationIBM Tivoli Asset Management for IT

installation 27preparation for middleware

HP-UX 11i 61Solaris 10 61SUSE Linux Enterprise Server 11 61

preparing to installmiddleware 36

prerequisite 42prerequisites

installation 31procedures 31, 32, 33process solution installation 199

process ID 40Process Manager Product 215process manager products 193process managers

installation 209process solution

deployment 199process solution command-line interface

supported parameters 212process solution installation 205, 207,

209command syntax 211logs 292packages 194prerequisites 199process solution package 220

process solution installation client 211process solution installation program

command-line interface 197wizard 197

Process Solution Installerinstallation 229

language packs 229language packs

installation 229PMP 229

process solution package 207, 215aggregation packages 197applyfix 219deployment

manual completion 207install 216refreshlang 221


process solution package (continued)showfeatures 222showfixes 221showinstalled 214undo 217uninstall 218upgrade 216

process solution packagesinstallation methods 193list 194

process solutions 193high-level deployment steps 200typical deployment 200

Qqueues

JMS 164

RRational Portfolio Manager

packages 32refreshlang action 221remote

configuration 33remote access protocols 33requirements

hardware and software 3response file

options 58restoring

DB2 database server 335, 340Oracle database 336, 341

reusingMicrosoft Active Directory 108

role 19

Ssecurity

planning 19security group 19security groups 261SELinux

disablement 38enablement 38

service integration busadding a server 165

shared memory 33showfeatures action 222showfixes action 221showinstalled action 197, 214silent

installation 57, 58uninstallation 347

softwarelife cycle

operations 193software components

IBM Tivoli Asset Management forIT 1

Solaris 10middleware configuration 61

solution packages 209solutioninstaller 191

solutionInstallergeneral syntax 211

solutionInstaller scriptsolutionInstaller.bat 211solutionInstaller.sh 211

SQIN JMS queue 169SQINBD queue 167SQL Server

manual configuration 145SQL Server 145

SQOUTBD queue 167SSL

configuration 22startFusion file

memory allocation 246SUSE Linux Enterprise Server 11

middleware configuration 62system check

pre-deployment 207system directories

accessing 31System Integration Module 215system passwords

settings 26

Ttar command

requirements 35taskrunner utility 308Tivoli Asset Management for IT

for Service Providersenablement 249

ports 21Tivoli Asset Management for IT

middlewareUNIX systems 35

Tivoli Integration Composerinstallation 240installing

with process solutioninstallationpackage 242

UNIX systems 242troubleshooting

32 - bit Windows system 296middleware installation 291

troubleshooting middleware installernot valid DB2 password 304

Uulimit

setting 32undo action 217undofix action 220uninstall

system files removal 345uninstall action 218uninstallation

automatically configured IBM TivoliAsset Management for IT 332

database recovery 335, 340IBM Tivoli Asset Management for

IT 347middleware 329

uninstallingIBM Tivoli Asset Management for IT

manually deployed 333uninstalling Integration Composer 247uninstalling Integration Composer on

Unix-based operating systems 248uninstalling Integration Composer on

Windows operating systems 247update installer

WebSphere Application ServerNetwork Deployment 70

upgrade action 216user 55

Vverification

installation 191

WWebSphere Application Server

compressed file 67plug-ins

installation 74WebSphere Application Server Network

Deploymentupdate installer 70

WebSphere Network Deploymentconfiguration 22

WebSphere Portal Serverdeployment 325overview 325

Windows services 322work type 259

Xxml request pages 266

Index 355


��

Printed in USA

Date post:	03-Feb-2022
Category:	Documents
Upload:	others
View:	11 times
Download:	0 times