Tivoli Asset Management for IT Release 7.

Installation Guide | IBM WebSphere Application Server

V ersion 7 Release 1.0

Tivoli Asset Management for IT Release 7.1

Installation Guide | IBM WebSphere Application Server

V ersion 7 Release 1.0

This edition applies to version 7, release 1, modification 0 of IBM Tivoli Asset Management for IT and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2007, 2008. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Chapter 1. Introduction . . . . . . . . 1
Tivoli Asset Management for IT components. . Tivoli Asset Management for IT component requirements . . . . . . . . . . . More information . . . . . . . . . . . . . . . 1 . 3 . 5 Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer. . . . . . . . . . . . . . . . Tivoli middleware installer logs . . . . . . Starting Tivoli Asset Management for IT middleware on Windows . . . . . . . . . . Starting Tivoli Asset Management for IT middleware on UNIX . . . . . . . . . . . Reusing middleware . . . . . . . . . . . Reusing DB2 . . . . . . . . . . . . . Reusing Oracle . . . . . . . . . . . . Reusing IBM Tivoli Directory Server . . . . . Reusing Microsoft Active Directory . . . . . Uninstalling Tivoli Asset Management for IT middleware . . . . . . . . . . . . . . Installing Tivoli Asset Management for IT middleware on zLinux (Linux/390) . . . . . . Installing and configuring DB2 on zLinux . . . Installing and configuring IBM Tivoli Directory Server on zLinux . . . . . . . . . . . Installing and configuring WebSphere Application Server Deployment Manager on zLinux . . . . . . . . . . . . . . . Creating profiles using 64-bit WebSphere Application Server Deployment Manager for zLinux . . . . . . . . . . . . . . . Installing and configuring IBM HTTP Server on zLinux . . . . . . . . . . . . . . . Installing and configuring the WebSphere Plug-in on zLinux . . . . . . . . . . . . . . Installing and configuring IBM Agent Controller on zLinux . . . . . . . . . . . . . . Installing and configuring Virtual Member Manager on WebSphere on zLinux . . . . . WebSphere management . . . . . . . . . . Starting the WebSphere Application Server . . . Securing the WebSphere Administrative Console Configuring the WebSphere Application Server to run as a Windows service . . . . . . . . Configuring the WebSphere node agent to run as a Windows service . . . . . . . . . . . WebSphere Portal Server overview . . . . . . Tivoli Asset Management for IT deployed on WebSphere Portal Server . . . . . . . . . 31 39 40 41 42 42 43 43 44 45 46 47 52

Chapter 2. Planning to deploy Tivoli Asset Management for IT . . . . . . . 7

Tivoli Asset Management for IT deployment topologies . . . . . . . . . . . . . . . 7 Tivoli Asset Management for IT administrative workstation . . . . . . . . . . . . . . 7 Single machine deployment . . . . . . . . 7 Multiple machine deployment . . . . . . . 8 Reusing existing middleware components . . . . 9 Middleware configuration options . . . . . . 9 Planning for Tivoli Asset Management for IT middleware worksheet . . . . . . . . . . 10 Planning for Tivoli Asset Management for IT worksheet . . . . . . . . . . . . . . . 16

Chapter 3. Preparing to install Tivoli Asset Management for IT . . . . . . . 19

DVD layout . . . . . . . . . . . . . Before you begin . . . . . . . . . . . Disabling the firewall . . . . . . . . . Deleting the TEMP and TMP user environment variables . . . . . . . . . . . . . Verifying the required rpm-build package is installed . . . . . . . . . . . . . Setting the ulimit . . . . . . . . . . Setting the swap size . . . . . . . . . Setting shared memory . . . . . . . . Enabling remote configuration . . . . . . Tivoli Asset Management for IT installation overview . . . . . . . . . . . . . . Tivoli Asset Management for IT launchpad . . . Starting the Tivoli Asset Management for IT launchpad . . . . . . . . . . . . . . 19 . 19 . 19 . 20 . . . . . 20 20 21 21 21

53

54 57 58 59 60 60 60 62 63 64 65 65

. 22 . 22 . 22

Chapter 4. Tivoli Asset Management for IT middleware installation . . . . . . 25

Tivoli middleware installer workspace . . Tivoli Asset Management for IT middleware deployment plan overview . . . . . . Options for invoking the deployment plan Preparing UNIX systems for Tivoli Asset Management for IT middleware . . . . Increasing AIX file size and number of descriptors . . . . . . . . . . Increasing AIX paging space . . . . . Enabling asynchronous I/O on AIX . . Checking for required libraries on Linux Configuring the JRE in Linux . . . .
Copyright IBM Corp. 2007, 2008

. . . . . . . . .

. . . . . . . . .

. 26 . 27 . 28 . 28 . . . . . 28 29 30 30 30

Chapter 5. Tivoli Asset Management for IT installation program overview. . . . 69

Tivoli Asset Management for IT simple install path values . . . . . . . . . . . . . . . . 70 Installing Tivoli Asset Management for IT . . . . 72 Tivoli Asset Management for IT installation with manual middleware configuration . . . . . . . 86 Manually configuring the database server . . . 86 Manually configuring the directory server . . . 99 Manually configuring the J2EE server . . . . 107

iii

Manually configuring Virtual Member Manager on WebSphere . . . . . . . . . . . . Performing post installation tasks for the J2EE server . . . . . . . . . . . . . . . Manually configuring JMS queues . . . . . Error queues. . . . . . . . . . . . . Manually creating a datasource for the persistence store . . . . . . . . . . . Installing Tivoli Asset Management for IT without middleware autoconfiguration . . . . Manually configuring the VMMSYNC cron task for Microsoft Active Directory . . . . . . .

108 111 113 119 121 123 132

Installing Integration Composer with the Launchpad . . . . . . . . . . .

. 147

Chapter 9. Tivoli Asset Management for IT language pack installation program overview . . . . . . . . . 151
Installing the language pack . . . . . . . . 151

Chapter 10. Tivoli Asset Management for IT post installation tasks . . . . . 153
Initial data configuration . . . . . . . Signing in using a default user ID . . . Create currency codes . . . . . . . Create item and company sets . . . . . Create an organization . . . . . . . Create a general ledger account component Create a general ledger account . . . . Create default insert site . . . . . . . Create a Work Type . . . . . . . . Signing out and signing in . . . . . . Synchronizing data . . . . . . . . . First steps to using Log and Trace Analyzer . Locations of the resource set definition files Modifying the config.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 153 154 154 154 155 155 155 156 156 156 158 158 158

Chapter 6. IBM Agent Controller overview . . . . . . . . . . . . . 135

IBM Agent Controller supported platforms Planning for serviceability . . . . . . Installing IBM Agent Controller . . . . Starting IBM Agent Controller . . . . . . . . . . . . . . . . 135 136 137 138

Chapter 7. Process solution package installation . . . . . . . . . . . . 141

Process solution packages . . . . . . . Before using the process solution installation program . . . . . . . . . . . . . Installing process managers using the process solution installation wizard . . . . . . . Process solution installation logs . . . . . . . . . . 141 . 141 . 142 . 143

Notices . . . . . . . . . . . . . . 161
Trademarks . . . . . . . . . . . . . . 163

Chapter 8. Integration Composer installation . . . . . . . . . . . . 147

Installing Integration Composer with the Integration Composer DVD . . . . . . . . 147

Index . . . . . . . . . . . . . . . 165

iv

Installation Guide for IBM WebSphere Application Server:

Chapter 1. Introduction
IBM Tivoli Asset Management for IT is a comprehensive suite of products built on a single, common platform. Tivoli Asset Management for IT combines enhanced enterprise asset management functionality with new service management capabilities that together improve the effectiveness of asset management strategies. Tivoli Asset Management for IT includes advanced IT asset management, service management, and a full-featured service desk, all based on the IT Infrastructure Library (ITIL) guidelines. Each product can be implemented separately as a stand-alone solution or deployed with other products. The solution enhances asset management and ensures service performance of production, facility, transportation, and IT assets.

Tivoli Asset Management for IT components

Tivoli Asset Management for IT requires multiple software servers that you can either install on separate, dedicated server machines (for best performance), or the same physical server. The following diagram depicts a typical Maximo configuration. For the system requirements for this configuration, see Tivoli Asset Management for IT component requirements on page 3.

Copyright IBM Corp. 2007, 2008

JDBC

SQ

LC

Integration Composer Server

Database Server

lie

nt

JDBC

Directory Server
TP HT

Administration Workstation

HTTP/HTTPS

IBM Tivoli Asset Management for IT On IBM WebSphere Application Server

End user with Microsoft Windows Internet Explorer 6 or 7 browser

Figure 1. Tivoli Asset Management for IT Components

v Database The Maximo database is the repository for all Configuration Items information. v Application server Tivoli Asset Management for IT is built using Java 2 Enterprise Edition (J2EE) technology, which requires a commercial application server, such as IBM WebSphere Application Server. The Application Server consists of Tivoli Asset Management for IT applications using JavaServer Pages (JSP), XML, and Tivoli Asset Management for IT-application-specific business components. IBM Integrated Solutions Console The Integrated Solutions Console brings the interfaces for many different software products into a single user interface, allowing you to centralize data analysis efforts and evaluate information in context. v HTTP server A separate, dedicated HTTP server can be configured to work with the J2EE application server. v Directory server A directory server works in conjunction with Virtual Member Manager in WebSphere to provide security within Tivoli Asset Management for IT . v Administrative system

Installation Guide for IBM WebSphere Application Server:

The administrative system is used to deploy Tivoli Asset Management for IT. After the initial deployment, the administrative system is used to make updates or changes to the deployment. Changes to the Tivoli Asset Management for IT deployment typically require that Tivoli Asset Management for IT Enterprise Archive (EAR) files be rebuilt, which can only be done from the administrative system. The administrative system can only be implemented as a Windows system.

Tivoli Asset Management for IT component requirements

While Tivoli Asset Management for IT includes a language pack installer, Tivoli Asset Management for IT does not support bi-directional languages or Turkish. Tivoli Asset Management for IT hardware and software requirements are listed in this section. Each product version listed reflects the minimum requirement for use with Tivoli Asset Management for IT. If available, the Tivoli Asset Management for IT administrative workstation and systems hosting Tivoli Asset Management for IT middleware can support IPv6 network configuration. Browser Tivoli Asset Management for IT supports Microsoft Internet Explorer 6 and later. Database
Software v DB2 UDB 9.1.3 (installed by the Tivoli middleware installer) or v8.2.8 v Oracle 9.2.0.8, Oracle 10.2.0.3 or Oracle 10.1.0.5, Standard or Enterprise version v Microsoft SQL Server 2005 SP2, Standard or Enterprise version. Operating System Refer to the database product specifications.

J2EE application server This is where you install WebSphere Application Server and where Tivoli Asset Management for IT runs.

Chapter 1. Introduction

Hardware v 24 dedicated processors

Software v Windows Server 2003 (Standard SP2, Enterprise, or DataCenter) (32-bit, 64-bit) v IBM AIX 5.3 v Red Hat Enterprise Linux v4 (Enterprise or Advanced) (update 4+5 or later) (Intel) (32 bit) v SuSE Linux (SLES) 9.0 Enterprise Server System z SP4 or later (manual install only) Note: Tivoli Asset Management for IT supports the following operating system. However, if you are using an IBM DB2 Universal Database with Tivoli Asset Management for IT 7.1, you cannot use the following operating system on your Application Server: v Sun Solaris version 9 or 10 (SPARC processor-based systems v IBM WebSphere Network Deployment 6.1.0.11 (provided by IBM Corporation)

v 2 GB RAM per processor v 1.5 GB or greater of disk space for Maximo and Java/Web Server components

Integration options
Software The following product can serve as integration options for a Tivoli Asset Management for IT 7.1 deployment. v IBM Integrated Solutions Console 7.1.1 IBM Integrated Solutions Console 7.1 is installed as part of IBM WebSphere Network Deployment 6.1.0.11 v IBM WebSphere Portal Server 6.0 Operating System Tivoli Asset Management for IT integration components can be run on any operating system supported by the integration software.

HTTP server
Software The following product can serve as the HTTP server component of a Tivoli Asset Management for IT 7.1 deployment. v IBM HTTP Server v6.1 FP13 Operating System v Windows Server 2003 SP2 (Standard SP2, Enterprise, or DataCenter) (32-bit, 64-bit) v Windows Vista (Business, Enterprise, Ultimate) (32-bit, 64-bit) v Windows XP Professional SP2 (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 V5.3 TL level 5300-06 (64-bit kernel) v SuSE Linux (SLES) 9.0 Enterprise Server System z SP4 or later (manual install only)

Installation Guide for IBM WebSphere Application Server:

Directory server
Software v IBM Tivoli Directory Server v6.1 FP1 v Microsoft Windows Server 2003 SP2 Active Directory Microsoft Active Directory Application Mode is not supported. Operating System v Windows Server 2003 (Standard SP2, Enterprise, or DataCenter) (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 V5.3 TL level 5300-06 (64-bit kernel) v SuSE Linux (SLES) 9.0 Enterprise Server System z SP4 or later (manual install only)

Administrative system
Hardware v Intel-based Pentium processor v 1 GB RAM v SVGA 1024 x 768 resolution; if used for Application Designer 1280 x 1024 resolution Software v Windows Server 2003 (Standard SP2, Enterprise, or DataCenter) (32-bit, 64-bit) v Windows Vista (Business, Enterprise, Ultimate) (32-bit, 64-bit) v Windows XP Professional SP2 (32-bit, 64-bit) v Adobe Acrobat Reader 6.0 Note: The Tivoli Asset Management for IT Workflow Designer requires a Java Runtime Environment. JRE 1.4.2 JRE1.5 are supported.

Client system
Hardware v Intel-based Pentium processor v 1 GB RAM v SVGA 1024 x 768 resolution; if used for Application Designer 1280 x 1024 resolution Software v Windows Vista (Business, Enterprise, Ultimate) (32-bit, 64-bit) v Windows XP Professional SP2 (32-bit, 64-bit) v Adobe Acrobat Reader 6.0

More information
Use these resources to find more information about Tivoli Asset Management for IT. Before you install Tivoli Asset Management for IT, you can find information on the Quick Start DVD (or the corresponding downloadable image) and the Web infocenter at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/ index.jsp?topic=/com.ibm.itmaxam.doc/welcome.htm. Review these resources before you install Tivoli Asset Management for IT: Quick Start Guide A two-page document that gives you the information you need to get started. The Quick Start DVD and Web infocenter contain copies of the Quick Start Guide in several languages.
Chapter 1. Introduction

Download document Describes how to download the product images from PassPort Advantage. Published on the Web; the Quick Start Guide and Web infocenter have pointers to it. IBM Tivoli Asset Management for IT 7.1 Installation Guide (IBM WebSphere) This guide. Available in PDF on the Quick Start DVD or the Web infocenter. After you install Tivoli Asset Management for IT, you can use the Product support site as a source of information. The IBM Software Support Web site for Tivoli Asset Management for IT at http://www-306.ibm.com/software/tivoli/products/assetmanagement-it/ gives you access to the latest fixes and technical notes about Tivoli Asset Management for IT.

Installation Guide for IBM WebSphere Application Server:

Chapter 2. Planning to deploy Tivoli Asset Management for IT

Use this information to plan your Tivoli Asset Management for IT deployment.

Tivoli Asset Management for IT deployment topologies

Use this information to determine the best deployment option for your environment and business needs. There are two primary strategies to deploy Tivoli Asset Management for IT within your enterprise. Single-server The single-server topology consists of loading all Tivoli Asset Management for IT components onto one machine. This topology is used typically for proof-of-concept purposes, as a demonstration, or as a learning environment. For managing enterprise assets and processes, you would typically implement a multi-server topology. Multi-server The multi-server topology consists of splitting Tivoli Asset Management for IT components across several different machines. This strategy is beneficial as it optimizes resource use and decreases the load on each system. This type of deployment would be typical for production use within an enterprise. A typical deployment lifecycle might begin with a single-server topology that moves through phases of demonstration, functional proof-of-concept, and testing integration within the existing environment, and then gradually move towards a pilot multi-server environment before finally implementing a production deployment within the enterprise.

Tivoli Asset Management for IT administrative workstation

You install Tivoli Asset Management for IT from a Windows workstation designated as the administrative workstation. This workstation is where the Tivoli Asset Management for IT EAR files are built and later deployed to the application server. There is not a Tivoli Asset Management for IT runtime requirement for the Administrative Workstation. For daily operations, the administrative workstation will not be required after the initial installation and configuration of Tivoli Asset Management for IT. You use the administrative workstation to install program patches, product upgrades, new applications, and additional language packs. While not typically used on a daily basis, the administrative workstation is used in all phases of the product lifecycle and is an important Tivoli Asset Management for IT support component.

Single machine deployment

A topology consisting of deploying Tivoli Asset Management for IT on a single machine is frequently used as a proof-of-concept, educational, or demonstration configuration.

Copyright IBM Corp. 2007, 2008

The following figure details the Application Server MXServer running Tivoli Asset Management for IT on a single physical machine.

Figure 2. Single server deployment

Multiple machine deployment

This section details deploying Tivoli Asset Management for IT across multiple machines. In order to provide load balancing, availability, reuse, and redundancy, Tivoli Asset Management for IT must be deployed on multiple machines. This topology is the recommended deployment topology for a production environment. When contemplating your deployment strategy, determine whether it includes systems already established in your network. Implementing Tivoli Asset Management for IT by installing all new components using the Tivoli Asset Management for IT middleware and Tivoli Asset Management for IT installation programs simplifies the deployment. If you plan to reuse or migrate resources that exist in your network, make adjustments to your rollout plan to allow time for things such as bringing the existing resources to version levels that are compatible with Tivoli Asset Management for IT. In a disparate environment, the collection of machines in this deployment could be a mixture of Windows and UNIX machines. Only the Administrative system must be hosted on a Windows system. Within WebSphere Application Server Network Deployment you can create deployment managers that provide centralized administration of managed Application Server nodes and custom nodes as a single cell. WebSphere Network Deployment provides basic clustering and caching support, including work balancing, automated performance optimization, and centralized management and monitoring.

Installation Guide for IBM WebSphere Application Server:

Tivoli Asset Management for IT Deployed in a Cluster.

WebSphere Cell
(ctgCell01)

Database Server

MAXIMOCLUSTER ctgNode3

WebSphere Deployment Manager

ctgNode2 ctgNode1 ApplSrv1 Srv2

Srv3

Directory Server

(ctgCellManager01)

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

While Tivoli Asset Management for IT requires a new WebSphere Application Server Network Deployment application server for deployment, once Tivoli Asset Management for IT has been deployed, you can add the application server used by Tivoli Asset Management for IT as a new member of an existing WebSphere Application Server Network Deployment cluster. For more information about adding a new member to an existing WebSphere Application Server Network Deployment cluster, refer to http://publib.boulder.ibm.com/infocenter/wasinfo/ v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ trun_wlm_member.html.

Reusing existing middleware components

You can reuse some existing middleware installations as Tivoli Asset Management for IT components. For example, you might have an instance of DB2 or Oracle in an existing database server which already has established access policies, redundancy measures, and backup plans in place. If you plan to reuse existing middleware, ensure that they are at the level supported by Tivoli Asset Management for IT. The middleware and Tivoli Asset Management for IT installation programs do not provide a mechanism for patching backlevel servers, nor do these programs provide remote prerequisite checks to ensure they are at the right level.

Middleware configuration options

After middleware has been installed through the Tivoli middleware installer, you have two options of configuring the servers for use with Tivoli Asset Management for IT. You are presented with the option of either allowing the Tivoli Asset Management for IT installation program to configure middleware automatically, or configuring each middleware component manually. Auto-configure The Tivoli Asset Management for IT installation program automatically configure middleware to work together with Tivoli Asset Management for IT. This option is recommended if you are installing new instances of

Chapter 2. Planning to deploy Tivoli Asset Management for IT

middleware components, or if you have existing middleware instances that are not governed by policies that restrict programmatic configuration. Manual You can manually configure middleware that exists in your environment, or has been installed by the Tivoli middleware installer. This configuration must be completed prior to running the Tivoli Asset Management for IT installation program. If you have policies in place that dictate certain procedures and guidelines when configuring systems in your environment, you can choose this deployment path .

Planning for Tivoli Asset Management for IT middleware worksheet

These tables list the settings for values that you must supply when installing the Tivoli Asset Management for IT middleware. Although many of the defaults can be accepted when navigating the panels of the Tivoli middleware installer, you want to review this worksheet if you plan to configure manually or reuse existing middleware. In a multi-machine deployment scenario, you might have multiple values to consider.
Table 1. List of users and groups created during Tivoli Asset Management for IT installation User db2admin Group v DB2USERS v DB2ADMNS Description DB2 administrator. Windows Service User ID. This user is created by the Tivoli middleware installer if it does not exist. idsccmdb v Windows Users ITDS user v Windows v AIX v Linux Platform Windows Your value

This user is created by Administrators the Tivoli middleware installer if it does not v AIX exist. idslad v Linux idslad db2grp1 maximo v Users v Administrators Used for Maximo database configuration.

v Windows v Linux

This user is created by v AIX the Tivoli Asset v Sun Solaris Management for IT installation program if it does not exist. ctginst1 The system user used as v AIX the database instance v Administrators v Linux owner on UNIX ctginst1 must be a platforms. member of This user is created by db2grp1 with secondary groups the Tivoli middleware installer if it does not of staff and exist. dasadm1 v Users

10

Installation Guide for IBM WebSphere Application Server:

Table 1. List of users and groups created during Tivoli Asset Management for IT installation (continued) User db2fenc1 Group db2fgrp1 Description Platform Your value

UNIX system user used v AIX as the fenced user ID for v Linux DB2. This user is created by the Tivoli middleware installer if it does not exist.

wasadmin

Not a system user.

This is a user ID created v Windows for use with WebSphere v AIX Application Server. v Linux This user is created by v Sun Solaris the Tivoli middleware installer if it does not exist.

Table 2. Tivoli middleware installer Setting Workspace directory Middleware images source directory Compressed images directory Uncompressed images directory Table 3. DB2 configuration Setting Installation directory Default Windows <SystemDrive>\ Program Files\IBM\SQLLIB Linux AIX DAS user /opt/IBM/db2/ V9.1 /opt/IBM/db2/ V9.1 Your value Default <user home>\ibm\tivoli\ mwi\workspace Your value

Windows db2admin Linux AIX dasusr1 dasusr1 db2fenc1 db2fenc1

Fenced user

Linux AIX

Chapter 2. Planning to deploy Tivoli Asset Management for IT

11

Table 3. DB2 configuration (continued) Setting Fenced user group name Default Linux AIX Fenced user home directory Linux AIX: Instance name Port Instance user name home directory Database instance user ID ctginst1 50005 Linux: AIX: /home/ctginst1 /home/ctginst1 db2fgrp1 db2fgrp1 /home/db2fenc1 /home/db2fenc1 Your value

Windows: db2admin Linux: AIX: ctginst1 ctginst1

DB2 administrators group

Windows: DB2ADMNS Linux: AIX: db2grp1 db2grp1

DB2 users group

Windows: DB2USERS YES

Use same user name and p/w for remaining DB2 Services Configure Tools Catalog

NO This value is relevant for reuse scenarios only.

Enable O/S Security for DB2 YES objects This value is relevant for reuse scenarios only. DB2 instance port Data tablespace name Data tablespace size MAXDATA medium (1000Mb) DB2 Temporary tablespace name Temporary tablespace size Medium (5000Mb)

MAXTEMP 1000Mb

12

Installation Guide for IBM WebSphere Application Server:

Table 4. Oracle configuration Setting Installation directory Default Windows <SystemDrive>\ oracle\product\ 10.2.0\oradata Linux /opt/app/oracle/ product/10.2.0/ oradata /opt/app/oracle/ product/10.2.0/ oradata Your value

AIX

Sun Solaris /opt/app/oracle/ product/10.2.0/ oradata Administrator User ID Oracle Software Owner ID sys Windows Administrator Linux AIX oracle oracle

Sun Solaris oracle Instance Location Windows On Windows, this value might be C:\oracle\product\ 10.2.0\oradata Linux On Linux, this value might be /opt/app/oracle/ product/10.2.0/ oradata /opt/app/oracle/ product/10.2.0/ oradata

AIX

Sun Solaris /opt/app/oracle/ product/10.2.0/ oradata Data tablespace name Data tablespace size MAXDATA medium (1000Mb) Oracle Temporary tablespace name Temporary tablespace size Medium (1000Mb)

MAXTEMP 1000Mb

Chapter 2. Planning to deploy Tivoli Asset Management for IT

13

Table 5. SQL Server configuration Setting Installation directory Named instance SQL Server administrator SQL Server administrator password Port Database name User ID User ID password Data file name Log file name maxdb71_dat maxdb71_log 1433 maxdb71 maximo Default <ProgramFiles>\Microsoft SQL Server\90 maximo sa Your value

Table 6. WebSphere Application Server configuration Setting Install location Default Windows: C:\Program Files\IBM\ WebSphere\ AppServer Linux: /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer Your value

AIX:

Sun Solaris /opt/IBM/ WebSphere/ AppServer WebSphere Administration User Name wasadmin

Deployment Manager profile ctgDmgr01 name Application server profile name Profile directory ctgAppSrv01

Linux:

/opt/IBM/ WebSphere/ AppServer/profiles /usr/IBM/ WebSphere/ AppServer/profiles

AIX:

Sun Solaris /opt/IBM/ WebSphere/ AppServer/profiles

14

Installation Guide for IBM WebSphere Application Server:

Table 6. WebSphere Application Server configuration (continued) Setting Cell name Deployment Manager node name Application server node name HTTP server install location Default ctgCell01 ctgCellManager01 ctgNode01 Your value

Windows: C:\Program Files\IBM\ HTTPServer Linux: AIX: /opt/IBM/ HTTPServer /usr/IBM/ HTTPServer

Sun Solaris /opt/IBM/ HTTPServer HTTP port 80 Note: On Windows, this port might already be in use. Ensure that you either free up this port, or use another port that is unassigned. 8008 ctgAppSvr01

HTTP admin server port HTTP plugin profile name

Table 7. IBM Tivoli Directory Server configuration Setting Install location Default Windows: C:\Program Files\IBM\LDAP\ V6.1 Linux: AIX: Administrator distinguished name Organizational unit Organization and country suffix Directory server port Directory server secure port Administration port Administration secure port Database name cn=root ou=SWG o=IBM,c=US 389 636 3538 3539 security
Chapter 2. Planning to deploy Tivoli Asset Management for IT

Your value

/opt/IBM/ldap/ V6.1 /opt/IBM/ldap/ V6.1

15

Table 7. IBM Tivoli Directory Server configuration (continued) Setting Instance name Instance port Instance user name Default idsccmdb 50006 idsccmdb Your value

Table 8. Microsoft Active Directory configuration Setting Directory server port LDAP base entry User suffix Group suffix Organization container suffix Bind distinguished name Default 389 DC=ism71,DC=com CN=Users,DC=ism71,DC=com DC=ism71,DC=com DC=ism71,DC=com CN=Administrator,CN=Users, DC=ism71,DC=com Your value

Table 9. IBM Agent Controller configuration Setting IBM Agent Controller installation location Default Windows: C:\Program Files\IBM\ AgentController Linux: AIX: /opt/IBM/ AgentController /opt/IBM/ AgentController Your value

Planning for Tivoli Asset Management for IT worksheet

These tables list the settings whose values that you must supply when using the Tivoli Asset Management for IT installation program.
Table 10. Settings for a custom installation Setting Installation directory API port DB2 host name DB2 port Maximo database name Maximo database instance Maximo database user ID 50005 maxdb71 ctginst1 maximo Default C:\IBM\SMP 9530 Your value

16

Installation Guide for IBM WebSphere Application Server:

Table 10. Settings for a custom installation (continued) Setting DB2 installation directory Default Windows C:\Program Files\IBM\SQLLIB Linux AIX DB2 instance administrator user ID /opt/IBM/db2/ V9.1 /opt/IBM/db2/ V9.1 Your value

Windows db2admin Linux AIX ctginst1 ctginst1

Windows DB2 service user ID Oracle installation directory

db2admin

Windows C:\oracle\product\ 10.2.0\oradata Linux /opt/app/oracle/ product/10.2.0/ oradata /opt/app/oracle/ product/10.2.0/ oradata

AIX

Sun Solaris /opt/app/oracle/ product/10.2.0/ oradata Oracle administrator user ID Oracle software owner user ID SQL installation directory Data tablespace name Data tablespace size sys oracle <CProgramFiles>\Microsoft SQL Server\90 MAXDATA medium DB2 Oracle Medium (5000Mb) Medium (1000Mb)

SQL Server (Initial data file size) Medium (1000Mb) Temporary tablespace name Temporary tablespace size WebSphere host name WebSphere SOAP port 8879 MAXTEMP 1000Mb

Chapter 2. Planning to deploy Tivoli Asset Management for IT

17

Table 10. Settings for a custom installation (continued) Setting WebSphere server home directory Default Windows C:\Program Files\IBM\ WebSphere\ AppServer Linux /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer Your value

AIX

Sun Solaris /opt/IBM/ WebSphere/ AppServer WebSphere admin user ID WebSphere profile name Web server port Web server name Node name Cluster name Application server wasadmin ctgDmgr01 80 webserver1 ctgNode01 MAXIMOCLUSTER MXServer Note: This value cannot be changed.

JMS Data Source name JMS database name JMS server name Database server port Database user ID Directory server host name Directory server port Directory server administrator DN Bind password Maximo installation folder C:\IBM\SMP Note: Maximo can only be installed on the Tivoli Asset Management for IT administrative system, which must be a Windows system. 389 cn=root 50000 maxadmin maxsibdb

SMTP server Workflow Admin E-mail Admin E-mail

18

Installation Guide for IBM WebSphere Application Server:

Chapter 3. Preparing to install Tivoli Asset Management for IT

These topics provide information about product media, preinstallation considerations, overview of the installation procedure, and instructions on using the Tivoli Asset Management for IT launchpad.

DVD layout
IBM Tivoli Asset Management for IT ships on a set of DVDs that contain the prerequisite middleware, middleware fix packs, and the product code. Alternatively, you can download Tivoli Asset Management for IT files containing these same images from Passport Advantage. The following DVDs contain files for the Tivoli Asset Management for IT product: Tivoli Asset Management for IT V7.1 Contains the launchpad, Tivoli Asset Management for IT middleware installer, Tivoli Asset Management for IT installer, IBM Agent Controller installer, the Log and Trace Analyzer and Resource Generator tool, and the Tivoli Asset Management for IT language pack installation program for Windows. Middleware for Windows 2003 Contains prerequisite middleware software for Windows 2003. Middleware for Red Hat Enterprise Linux V4 Contains prerequisite middleware software for Red Hat Enterprise Linux version 4. Middleware for AIX V5.3 Contains prerequisite middleware software for AIX version 5.3. Tivoli Asset Management for IT V7.1 Quick Start Contains copies of the Quick Start guide in all languages and a copy of the information center.

Before you begin

This section describes the steps that you must take before you install middleware or Tivoli Asset Management for IT. To perform any of the steps, you must be logged in as a user with administrator privileges on Windows or as root on UNIX. Note: Make a copy of the image of the system on which you are planning to install the product. An automated uninstall feature is not supplied with IBM Tivoli Asset Management for IT, version 7.1. If the installation fails, restore the system to its previous working state using the copy of the disk image prior to attempting the installation again.

Disabling the firewall

Prior to the installation, disable the firewall for the system to which you are installing Tivoli Asset Management for IT middleware. See the documentation that comes with your Operation System for information on disabling the firewall.
Copyright IBM Corp. 2007, 2008

19

Deleting the TEMP and TMP user environment variables

The existence of the TEMP and TMP user variables can cause errors with the installation of DB2 on a Windows system. Prior to installing DB2, remove these variables for the user ID that performs the installation. These variables are user environment variables that must be deleted, not system variables. To remove the TEMP and TMP user variables on a Windows system, complete the following steps: 1. Access the System Properties dialog by right-clicking the My Computer icon on your desktop and selecting Properties. 2. From the System Properties dialog, first select the Advanced tab, and then click Environment Variables. 3. In the User variables section, select TEMP, and then click Delete. Repeat the process for the TMP variable. 4. Click OK. 5. Exit the System Properties dialog by clicking OK.

Verifying the required rpm-build package is installed

This procedure describes how to verify that the rpm-build package is installed on Linux. This package must be installed before you install the Tivoli Asset Management for IT middleware. This procedure applies only if you are installing on Linux. To verify that the rpm-build package is installed, perform the following steps: 1. Run rpm -qa | grep build. 2. If the command returns a value like rpm-build-4.3.3.-18_nonptl, the rpm-build package is installed. If nothing is returned, you must install the rpm-build package which is located on disk 3 (of 5) of the Red Hat Enterprise Advanced Server version 4 installation CDs using the rpm tool with the -i option.

Setting the ulimit

This section details how to set the ulimit in Linux, which is used to define user system and process resource limits. For Linux systems, you must set the ulimit for the system prior to installing Tivoli Asset Management for IT middleware. To set the ulimit, complete the following steps: 1. From a command line, type ulimit -f unlimited 2. From a command line, type ulimit -n 8192 If you set the ulimit in the .profile for root, the ulimit setting will apply to all processes. For AIX systems, refer to Increasing AIX file size and number of descriptors on page 28.

20

Installation Guide for IBM WebSphere Application Server:

Setting the swap size

Tivoli Asset Management for IT can be a resource-intensive application. It is recommended that you configure and tune your system for maximum performance. This section details how to set the size of the swap space used in Linux systems. Typically, the swap size set for Linux systems should be equivalent to twice the amount of physical RAM in the machine. Additional swap space can be made available to the system by: v increasing the size of the existing swap partition v creating a new, additional swap partition v creating a swap file Refer to the product documentation for your Linux distribution for more information. For AIX systems, refer to Increasing AIX paging space on page 29.

Setting shared memory

This section details how to set a minimum shared memory value in Linux. For Linux systems, set a minimum shared memory value for the system prior to installing the Tivoli Asset Management for IT middleware. To set the minimum shared memory value, complete the following steps: 1. From a command line, type sysctl -w kernel.shmmax and determine if the value is less than 268,435,456 bytes (256Mb). 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.

Enabling remote configuration

If you plan to take advantage of the Tivoli Asset Management for IT installation program feature that automates the configuration of Tivoli Asset Management for IT middleware, you must enable a Remote Execution and Access (RXA) service for each system on which you intend to install Tivoli Asset Management for IT middleware. RXA requires that the target system enable at least one of the protocols supported by RXA, which include rsh, rexec, SSH and Windows SMB. Before you start the Tivoli Asset Management for IT installation program, ensure that one of these protocols is running and will accept remote logins using a user name and password configured on the target machine. If the remote system is a Windows machine, you must configure RXA to work over SMB. For Windows machines, you cannot use Cygwin ssh. If Cygwin is present on the Windows machine, the installation will fail. Default installations of AIX systems might not include a suitable protocol and will need to have RXA compatible protocols enabled. RXA does not support accessing network drives on the local or remote system.

Chapter 3. Preparing to install Tivoli Asset Management for IT

21

Tivoli Asset Management for IT installation overview

Installation and deployment of IBM Tivoli Asset Management for IT consists of the following tasks: 1. Installation and configuration of required Tivoli Asset Management for IT middleware software products. Refer to Chapter 4, Tivoli Asset Management for IT middleware installation, on page 25. 2. Installation and configuration of Tivoli Asset Management for IT. 3. Configuration of optional Tivoli Asset Management for IT middleware software products, such as WebSphere Portal Server. Refer to WebSphere Portal Server overview on page 65. 4. Installation and configuration of the IBM Agent Controller (installed by the Tivoli middleware installer). Refer to Chapter 6, IBM Agent Controller overview, on page 135. 5. Installation of the language pack. Refer to Chapter 9, Tivoli Asset Management for IT language pack installation program overview, on page 151. 6. Enabling Tivoli Asset Management for IT License for usage. Refer to Chapter 7, Process solution package installation, on page 141. The installation programs for these Tivoli Asset Management for IT components can be initiated through the launchpad, where you can also access product information.

Tivoli Asset Management for IT launchpad

The IBM Tivoli Asset Management for IT launchpad serves as a centralized interface for launching a collection of installation programs and product information. The launchpad application will assist you in choosing which product installation programs you should install and indicates the order in which they should be installed. Use the Tivoli Asset Management for IT launchpad to: v Access the Tivoli Asset Management for IT Information Center v Access information used to plan the Tivoli Asset Management for IT installation and deployment v Start the Tivoli middleware installer v Start the Tivoli Asset Management for IT installation program v Start the Tivoli Asset Management for IT language pack installation program v Enable the Tivoli Asset Management for IT license for usage

Starting the Tivoli Asset Management for IT launchpad

To start the IBM Tivoli Asset Management for IT launchpad, complete the following steps: 1. Log on to an account with system administration privileges on the computer where Tivoli Asset Management for IT components are to be installed. 2. Start the launchpad from the root directory of the product DVD: v Windows: Start the launchpad by using the launchpad.exe program if the Windows autorun feature is disabled.

22

Installation Guide for IBM WebSphere Application Server:

v AIX: Start the launchpad from the root directory by using the launchpad.sh program. The launchpad program uses the system default browser to run. If the default browser on AIX is Firefox, it is likely that the launchpad program will not run properly due to the ksh shell interface. If you want to use the launchpad with the Firefox browser, follow these steps to modify it. a. Copy all of the files from disk1 to a local directory (for example, /user_dir). If you have downloaded the product images rather than using physical media, download and extract the launchpad images as described in the download document. b. Modify /user_dir/launchpad/Firefox.sh and remove the following lines:
typeset +r LOGNAME 2>/dev/null LOGNAME=lp_user_$$; export LOGNAME

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

Running the launchpad from the root directory avoids complications that would arise if you ran it inside the mounted directory and you wanted to swap disks. If you changed directory to the mounted DVD and launched the launchpad from that directory, at a certain point in the deployment process you would need to swap to another DVD, but you would not be able to because launchpad was still running from the directory on DVD you have mounted. You would not be able to unmount the disk without terminating the launchpad. v Sun Solaris: Start the launchpad from the root directory by using the launchpad.sh program. For more information on installation and configuration parameters you may encounter while installing Tivoli Asset Management for IT, refer to Planning for Tivoli Asset Management for IT middleware worksheet on page 10 and Planning for Tivoli Asset Management for IT worksheet on page 16.

Chapter 3. Preparing to install Tivoli Asset Management for IT

23

24

Installation Guide for IBM WebSphere Application Server:

Chapter 4. Tivoli Asset Management for IT middleware installation

Before you can install the IBM Tivoli Asset Management for IT, there are several Tivoli Asset Management for IT middleware products that must be deployed. The Tivoli middleware installer provides an interface for installing and deploying Tivoli Asset Management for IT middleware in a reliable and repeatable fashion. The Tivoli middleware installer records choices you make about your Tivoli Asset Management for IT deployment and configuration parameters associated with those choices, and then installs and deploys Tivoli Asset Management for IT middleware based upon the information you entered. The Tivoli middleware installer installs and deploys the following software: v Database server Tivoli Asset Management for IT uses the Maximo database to store details about the attributes and history of each configuration item and the details about the relationships between configuration items. You will have the choice of installing a new instance of DB2 UDB 9.1, or using a preexisting instance of DB2 UDB 8.2 or DB2 UDB 9.1. If you choose to use MS SQL Server or Oracle for your Tivoli Asset Management for IT deployment, you will have to install and configure them separately. v Directory server The directory server is used to secure the Tivoli Asset Management for IT J2EE application. You will have the choice of installing a new instance of IBM Tivoli Directory Server 6.1, or using a preexisting IBM Tivoli Directory Server or MS Active Directory server. If you choose to install a new version of IBM Tivoli Directory Server, you must choose to install a new DB2 UDB instance or reuse an existing DB2 UDB server. If you choose to use MS Active Directory Server for your directory server, you will have to install and configure it separately. v J2EE server The J2EE server is the application server used to serve and manage the Tivoli Asset Management for IT application. You must install a new instance of IBM WebSphere Network Deployment 6.1. A directory server can be configured to secure the J2EE server deployment. You can use a local or remote IBM Tivoli Directory Server or MS Active Directory Server. The J2EE component includes the following subcomponents: IBM HTTP Server IBM HTTP Server is used as the primary HTTP server. You will install a new instance of IBM HTTP Server. IBM HTTP Server Plugin The IBM HTTP Server Plug-in is used as the interface between IBM HTTP Server and the J2EE server You will install a new instance of IBM HTTP Server Plug-in. The WebLogic Server and MS Active Directory Server, if you choose to use it, will have to be installed and configured separately.
Copyright IBM Corp. 2007, 2008

25

The Tivoli middleware installer deploys software on a single machine. To deploy Tivoli Asset Management for IT middleware on multiple machines, the Tivoli middleware installer must be invoked on each machine in the topology configuration you have chosen. Ensure you have a strategy for deploying Tivoli Asset Management for IT middleware for each system you plan to use in your Tivoli Asset Management for IT deployment. If you deploy a Tivoli Asset Management for IT component using the Tivoli middleware installer on a system, for example, DB2, and then later decide you would also like to add IBM Tivoli Directory Server to that same system, you will have to undeploy DB2 before redeploying it in the same Tivoli middleware installer deployment plan that included IBM Tivoli Directory Server. When installing Tivoli Asset Management for IT middleware on a system, you must install all of the middleware intended for that system at one time. A process ID is generated each time the Tivoli middleware installer is used to install or uninstall a set of middleware products. The process ID will appear on the filesystem in various places related to logs and generated files, such as file names, directory names, and log messages. The process ID is used to group logs and other generated files that are related to the same invocation of the Tivoli middleware installer. It also separates logs and other generated files that are related to different invocations of the Tivoli middleware installer. The process ID is a string of the format [operation_MMdd_HH.mm], where operation is a string indicating the operation being performed, such as INSTALL or UNINSTALL, MM is 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, HH is a two-digit number (0-23) indicating the current hour, and mm is 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:45pm v [UNINSTALL_1216_09.59] An uninstallation started on December 16 at 9:59am In addition to installing and configuring Tivoli Asset Management for IT middleware, the Tivoli middleware installer performs additional tasks. If you choose to not run the Tivoli Asset Management for IT middleware installer because you intend to perform the necessary configuration on existing middleware resources manually, you will need to perform the following tasks. v Configure VMM after the J2EE server and the Directory server have been installed and configured. Refer to Manually configuring Virtual Member Manager on WebSphere on page 108 for more information. v Install IBM Agent Controller. Refer to Chapter 6, IBM Agent Controller overview, on page 135 for more information.

Tivoli middleware installer workspace

The Tivoli middleware installer is designed to record the options you select during install in a directory referred to as the workspace, and then configure the components selected as a single deployed application. Once a plan has been deployed, the Tivoli middleware installer cannot subsequently deploy additional features and products onto the machine at a later time. The existing plan must first be completely undeployed through the Tivoli middleware installer before a different set of features and products can be deployed.

26

Installation Guide for IBM WebSphere Application Server:

The composition and details of the deployment, as well as any logs generated by the Tivoli middleware installer process are located in the workspace. By default, the Tivoli middleware installer workspace is defined as: Windows C:\ibm\tivoli\mwi\workspace UNIX /ibm/tivoli/mwi/workspace The workspace can be defined on a shared resource that is made available to all the systems that will run the Tivoli middleware installer. Locating the workspace on a shared resource avoids the need to copy files such as the topology file manually from one machine to another. The workspace contains the following items: Deployment Plan The deployment plan is a collection of installation steps, configuration parameters for those steps, and target machine information. It is generated through the Tivoli middleware installer and it resides in the workspace directory. When deployment steps are changed, the existing deployment plan is deleted and replaced with the new deployment plan. The deployment plan configuration files contain information about the deployment plan itself. Whenever a deployment plan is modified, which includes reconfiguring existing deployment choices, the deployment plan configuration files will be deleted and regenerated when the deployment plan is redeployed. Topology File The topology file is a properties file that describes the configuration parameters of the Tivoli Asset Management for IT middleware deployment. This file is created and then updated after every deployment or undeployment. If you have not defined a workspace that is centrally located and accessible to all the systems that will be receiving Tivoli Asset Management for IT middleware, this file will have to be copied to the workspace of each machine where Tivoli Asset Management for IT middleware is being deployed. The contents of this file can be used by the Tivoli Asset Management for IT installation program to populate its panels with meaningful default values. This file is saved in <workspace>/topology.xml. Logs Log files that contain information about the deployment can be found in the workspace directory. In addition, log files native to the Tivoli Asset Management for IT middleware itself are also contained in this directory.

Tivoli Asset Management for IT middleware deployment plan overview

The deployment plan resides in the workspace directory and is generated from deployment choices selected in the Tivoli middleware installer. The plan is a series of deployment steps and configuration parameters. Each step is responsible for installing and uninstalling one portion of the middleware. When deployment choices are changed, the existing deployment plan is deleted and replaced with the new deployment plan.

Chapter 4. Tivoli Asset Management for IT middleware installation

27

Once the deployment plan has been generated using the information you entered in the Tivoli middleware installer, you have the option to have the Tivoli middleware installer execute it. This method of executing the deployment plan is recommended in most instances.

Options for invoking the deployment plan

Once the deployment plan has been generated using the information you entered in the Tivoli middleware installer, you have several options for executing it. Have the Tivoli middleware installer execute the deployment plan after it has been generated This is the most common method of implementing the deployment plan. Create the plan using the Tivoli middleware installer and then have it execute the plan by installing and configuring the middleware selected. This option also includes configuring existing instances of middleware present in your environment that will be used with Tivoli Asset Management for IT. This method of executing the deployment plan is recommended in most instances. Have the Tivoli middleware installer create the deployment plan and then componentize and distribute it The deployment plan consists of a collection of XML files that can be used to deploy middleware either through the Tivoli middleware installer or by Apache Ant. Ant is an open source software tool used to automate the software build process. Ant uses XML to describe build tasks and dependencies. You must have Ant 1.6.5 and the Java 1.5 JRE installed in order to execute a deployment plan outside of the Tivoli middleware installer. This method of executing the deployment plan should be reserved for advanced users that have a need to modify deployment plan parameters that are not configurable through the Tivoli middleware installer.

Preparing UNIX systems for Tivoli Asset Management for IT middleware

Certain UNIX parameters must be set to specific values to create an environment on the system that can accommodate Tivoli Asset Management for IT and its associative middleware.

Increasing AIX file size and number of descriptors

For Tivoli Asset Management for IT to function correctly, you need to increase the default number of file descriptors allowed for the root user, and also set the maximum allowable file size to unlimited. To increase the allowable file size and number of allowable descriptors for the root user in AIX, complete the following steps: 1. 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.

28

Installation Guide for IBM WebSphere Application Server:

root: fsize = -1 nofiles = 8192

3. A value of -1 for the fsize parameter indicates no limit. 4. Save and exit the file. You must log out as root and log back in for these changes to take effect. 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) file(blocks) data(kbytes) stack(kbytes) memory(kbytes) coredump(blocks) nofiles(descriptors) unlimited unlimited 2097152 32768 unlimited 2097151 8192

Increasing AIX paging space

To successfully install and run Tivoli Asset Management for IT, you must 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. To determine the current amount of paging space available to the server, issue the following command:
lsps -a

This command will result in output similar to the following:

Page Space hd6 Physical Volume hdisk0 Volume Group rootvg Size 5632MB %Used 2

To determine the size of a logical partition, issue the following command:

lslv hd6

This command will result in output that will include partition information similar to the following:
LPs: PP SIZE: 44 128 megabyte(s)

In the example output, there are a total of 44 Logical Partitions that are each 128 Mb in size. This results show a total of 5632 Mb of paging space available to the system. In order to add more paging space, you will add more logical partitions to the system. To add 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 logical volume. For example,
Chapter 4. Tivoli Asset Management for IT middleware installation

29

chps -s 10 hd6

adds 10 logical partitions to the logical volume hd6, which results in adding 1280 Mb to the paging space.

Enabling asynchronous I/O on AIX

Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems. Without asynchronous I/O, DB2 and Oracle database instances cannot be started successfully. It is an operational requirement, not an installation requirement so this step can be run at any time before full operation of the product. You only need to perform this step if the system will host the IBM Tivoli Directory Server. To turn asynchronous I/O on follow these steps: 1. 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 STATE to be configured at system restart from defined to available. 4. Click OK. 5. Exit SMIT. 6. Run the following command from the command line:
smit aio

7. From the System Management Interface Tool (SMIT) dialog box, select Configure Defined Asynchronous I/O, and then click Enter. 8. Reboot the system to enable the changes.

Checking for required libraries on Linux

The Tivoli Asset Management for IT middleware installation program requires the libstdc+.so.5 system library to be present on a Linux system in order to launch the Tivoli Asset Management for IT middleware installation program user interface. If you do not have this library installed, you will receive an error indicating that the Tivoli Asset Management for IT middleware installation program is unable to run in graphical mode. If you receive this error, check the /usr/lib/ directory to determine if you have the libstdc+.so.5 library installed. This library is included as part of Red Hat Enterprise Linux v4 update 4. If you cannot locate this library on your system, locate the RPM package for your system that contains this library and install the package.

Configuring the JRE in Linux

In some cases, the Tivoli middleware installer will fail on RHEL 5 systems, or other systems with SELinux enabled. In one failure scenario, Tivoli middleware installer will fail with an error message stating that the Java Runtime Environment (JRE) could not be found on the system. If this is the case, implement one of the following solutions: v Temporarily disable SELinux by using the setenforce 0 command, run the install, and then re-enable SELinux by using the setenforce 1command.

30

Installation Guide for IBM WebSphere Application Server:

v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled. This solution, however, affects the level of security for the entire system. In another failure scenario, Tivoli middleware installer will fail stating that it cannot find the VM. If this is the case, implement one of the following solutions: v Manually issue the chcon -R -t textrel_shlib_t <install_dir/jvm/jre> command. v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled. This solution, however, affects the level of security for the entire system.

Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer
This procedure explains how to use the Tivoli middleware installer to create a deployment plan that is responsible for installing and configuring prerequisite middleware products. The instructions provided in this section are for a typical installation using default values. In addition, these instructions assume you are using the Tivoli middleware installer to install a complete set of Tivoli Asset Management for IT middleware for use with Tivoli Asset Management for IT on a single machine. If you intend to deploy Tivoli Asset Management for IT middleware products across an array of machines, you will have to run the Tivoli middleware installer on each machine, choosing which piece of middleware to install on that each particular machine. In this case, you will encounter a subset of the panels included in these instructions that are relevant to the middleware you have chosen to install on a machine. The Tivoli middleware installer can also configure existing middleware products. If you intend to reuse existing Tivoli Asset Management for IT middleware products for your Tivoli Asset Management for IT deployment, refer to Reusing middleware on page 42. Refer to the Tivoli Asset Management for IT planning information to learn about using custom values during a custom installation. In some cases, fields and labels displayed within the Tivoli middleware installer are not correctly displayed on the panel when installing through remote sessions. It is recommended that you use the Tivoli middleware installer locally on the system that will host the middleware. If you do experience this phenomenon, first minimize and then maximize the install wizard to force it to redisplay the panel. Avoid using localhost for host name values in the installation program. Specify the actual fully-qualified host name of the system on which you are installing. For Linux systems, ensure that the command hostname -f returns a fully-qualified hostname. If it does not, consult the appropriate documentation for your operating system to ensure that the hostname command returns a fully qualified hostname. For Windows systems, ensure 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.

Chapter 4. Tivoli Asset Management for IT middleware installation

31

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. Important: When entering LDAP values for Tivoli Asset Management for IT installation panel fields, entries in LDIF files, or values you enter directly into an directory instance using the directory servers own tools, be aware of the product-specific syntax rules for using special characters in an LDAP string. In most cases, special characters must be preceded by an escape character in order to make it readable by the directory server. Failing to escape special characters contained in an LDAP string used with Tivoli Asset Management for IT will result in Tivoli Asset Management for IT errors. Many directory server products consider a blank space as a special character that is part of the LDAP string. Therefore, if you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you will encounter Tivoli Asset Management for IT errors that will be difficult to troubleshoot. Refer to the product documentation for your directory server for more information on special characters in LDAP strings. To install the prerequisite middleware products for Tivoli Asset Management for IT, follow these steps: 1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad. a. Start the launchpad: Windows On the DVD titled Tivoli Asset Management for IT 7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.exe. Linux On the DVD titled Tivoli Asset Management for IT 7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh. AIX On the DVD titled Tivoli Asset Management for IT 7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh.

Sun Solaris On the DVD titled Tivoli Asset Management for IT 7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh. 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.

32

Installation Guide for IBM WebSphere Application Server:

5. The Tivoli middleware installer license agreement window is displayed. 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 directory you will use as the Tivoli middleware installer workspace, and then click Next. The default location for the workspace will be the last workspace location used by this user, as specified in the middleware user preferences node. If no previous workspace location exists in the middleware user preferences node, then the default location for the workspace will be C:\ibm\tivoli\mwi\ workspace for Windows and /ibm/tivoli/mwi/workspace for UNIX. If the selected directory does not exist, it will be created. After deployment, the Tivoli middleware installer also generates a topology file in this directory. This topology file can be manually copied by the user to the workspace of the next machine in the topology, so that information about the deployment of middleware will be available to the Tivoli middleware installer when it is executed on the next machine. 7. From the Install IBM Autonomic Deployment Engine panel, click Next to install the IBM Autonomic Deployment Engine. 8. From the Deployment Choices panel, select the features to deploy on this machine, and then click Next. Choices include: Database Server The Database Server is used to store details about the attributes and history of each configuration item and the details about the relationships among configuration items. Directory Server The directory server is used to secure the J2EE Server. This feature should be selected to either install a new directory server locally or reuse a local directory server. J2EE Server The J2EE server is the application server used to serve and manage the application. If you choose to only install the J2EE server portion of the Tivoli Asset Management for IT middleware, you will be prompted to supply the directory server you will use to secure it. Your choices will be to secure with an existing instance of IBM Tivoli Directory Server, or an existing instance of Microsoft Active Directory. Secure the J2EE Server using the Directory Server. This option allows you to use a directory server to secure the J2EE server. By default this option is selected. It must remain selected in order for you to enable the Directory Server option. If you elect to opt out of maintaining J2EE server through the use of the directory server, you will be unable to install the directory server through the Tivoli Asset Management for IT Middleware installation program. 9. From the Deployment Plan Summary window, click Next to configure the parameters displayed. The deployment plan is generated and you will be provided details about the plan. 10. From the Credentials panel, enter the Username and Password you will use to deploy the plan with, and then click Next.

Chapter 4. Tivoli Asset Management for IT middleware installation

33

You can choose to enable the option of using the same password as the default user password value in all panels of the Tivoli middleware installer by enabling the Use this password as the value for all subsequent passwords option at the top of this panel. 11. Enter the following configuration parameters for DB2 Enterprise Edition Server and then click Next. Install location Enter the location to install DB2. Windows: Default is C:\Program Files\IBM\SQLLIB Linux: Default is /opt/IBM/db2/V9.1 AIX: Default is /opt/IBM/db2/V9.1

DB2 Administration Server username Enter the DB2 administrative account name. Windows: Default is db2admin Linux: Default is dasusr1 AIX: Default is dasusr1

DB2 Administration Server password Enter the password for the DB2 administrative account. Fenced user (Linux and AIX only) Enter a system user ID that can be used as a DB2 fenced user account. Default fenced user is db2fenc1 12. Enter the following configuration parameters for the Tivoli Asset Management for IT database instance, and then click Next. Instance name Enter the name of the Tivoli Asset Management for IT database instance. Default for all platforms is ctginst1 Port Enter the port that the Tivoli Asset Management for IT database instance will use. Default for all platforms is 50005. Instance username Enter the user name for the Tivoli Asset Management for IT database instance. Windows: Default is db2admin Linux: Default is ctginst1 AIX: Default is ctginst1

Instance username password Enter the password for the Tivoli Asset Management for IT database instance user name. 13. Enter information about the DB2 user groups: DB2 administrators group Enter the name of the DB2 administrators group.

34

Installation Guide for IBM WebSphere Application Server:

Windows: Default is DB2ADMNS Linux: Default is db2grp1 AIX: Default is db2grp1

DB2 users group (Windows only) Enter the name of the DB2 users group. Default is DB2USERS 14. Enter the following configuration parameters for IBM Tivoli Directory Server, and then click Next. Install location Enter the location to install IBM Tivoli Directory Server. Windows: Default is C:\Program Files\IBM\LDAP\V6.1 Linux: Default is /opt/IBM/ldap/V6.1 AIX: Default is /opt/IBM/ldap/V6.1

Administrator distinguished name Enter the distinguished name of the IBM Tivoli Directory Server administrator. Default for all platforms is cn=root. Administrator password Enter the password for the IBM Tivoli Directory Server administrator. 15. Enter the following configuration parameters for IBM Tivoli Directory Server, and then click Next. Organizational unit Enter the name of the IBM Tivoli Directory Server organizational unit to use with Tivoli Asset Management for IT. Default for all platforms is ou=SWG. Organization and country suffix Enter the name of the IBM Tivoli Directory Server organization and country suffix to use with Tivoli Asset Management for IT. Default for all platforms is o=IBM,c=US. Directory server port Enter the port number of the IBM Tivoli Directory Server. Default for all platforms is 389. Directory server secure port Enter the secure port number of the IBM Tivoli Directory Server. Default for all platforms is 636. Administration port Enter the administration port number of the IBM Tivoli Directory Server. Default for all platforms is 3538. Administration secure port Enter the secure administration port number of the IBM Tivoli Directory Server.
Chapter 4. Tivoli Asset Management for IT middleware installation

35

Default for all platforms is 3539. 16. Enter the following configuration parameters for IBM Tivoli Directory Server database instance, and then click Next. Database name Enter the name of the DB2 database you are using to hold IBM Tivoli Directory Server data. Default for all platforms is security. Instance name Enter the name of the IBM Tivoli Directory Server database instance. Default for all platforms is idsccmdb. Port Enter the port number used by the IBM Tivoli Directory Server database instance. Default for all platforms is 50006. Instance user password Enter the password for the instance user ID. 17. Enter the following configuration parameters for WebSphere Application Server security, and then click Next. LDAP Host Name Enter the host name of the system hosting the LDAP instance to use for WebSphere security. Directory server port Enter the port number used by the LDAP server to use for WebSphere security. Default is 389. LDAP base entry Enter the LDAP base entity of the LDAP instance to use for WebSphere security. Default is ou=SWG,o=IBM,c=US User suffix Enter the user suffix of the LDAP instance to use for WebSphere security. Default is ou=users,ou=SWG,o=IBM,c=US Group suffix Enter the group suffix of the LDAP instance to use for WebSphere security. Default is ou=groups,ou=SWG,o=IBM,c=US Organization container suffix Enter the organizational container suffix of the LDAP instance to use for WebSphere security. Default is ou=SWG,o=IBM,c=US 18. Enter the following configuration parameters for WebSphere Application Server security, and then click Next. Bind distinguished name Enter the bind distinguished name for binding to the LDAP instance. Default is cn=root

36

Installation Guide for IBM WebSphere Application Server:

Bind password Enter the password for the bind distinguished name. 19. Enter the following configuration parameters for WebSphere Application Server Version, and then click Next. Install location Enter the location to install WebSphere. Windows: Default is C:\Program Files\IBM\WebSphere\AppServer Linux: Default is /opt/IBM/WebSphere/AppServer AIX: Default is /usr/IBM/WebSphere/AppServer

WebSphere Administrator username Enter the WebSphere administrative account name. Default for all platforms is wasadmin. WebSphere Administrator password Enter the password for the WebSphere administrative account. 20. Enter the following configuration parameters for WebSphere Application Server, and then click Next. Deployment Manager profile name Enter the WebSphere profile name of the deployment manager server. Default for all platforms is ctgDmgr01. Application server profile name Enter the WebSphere profile name of the application server. Default for all platforms is ctgAppSrv01. 21. Enter the following configuration parameters for WebSphere Application Server, and then click Next. Cell name Enter the WebSphere Cell name. Default for all platforms is ctgCell01. Deployment Manager node name Enter the name of the WebSphere deployment manager node. Default for all platforms is ctgCellManager01. Application server node name Enter the name of the WebSphere application server node. Default for all platforms is ctgNode01. Update Installer install location Enter the location where the WebSphere update installer will be installed. Windows: Default is C:\Program Files\IBM\WebSphere\UpdateInstaller Linux: Default is /opt/IBM/WebSphere/UpdateInstaller AIX: Default is /usr/IBM/WebSphere/UpdateInstaller 22. Enter the following configuration parameters for IBM HTTP Server, and then click Next.

Chapter 4. Tivoli Asset Management for IT middleware installation

37

Install location Enter the location to install IBM HTTP Server. Windows: Default is C:\Program Files\IBM\HTTPServer Linux: Default is /opt/IBM/HTTPServer AIX: Default is /usr/IBM/HTTPServer

HTTP port Enter the port used by the IBM HTTP Server. Default for all platforms is 80. Admin Server port Enter the port to use to administer IBM HTTP Server. Default for all platforms is 8008. 23. Enter the following configuration parameters for WebSphere Application Server plugin for the IBM HTTP Server, and then click Next. Profile name Enter the profile name. Default for all platforms is ctgAppSvr01. This value cannot be changed. 24. Enter the following configuration parameters for IBM Agent Controller, and then click Next. Install location Enter the location to install IBM Agent Controller. Windows: Default is C:\Program Files\IBM\AgentController Linux: Default is /opt/IBM/AgentController AIX: Default is /opt/IBM/AgentController 25. Specify the location of the Tivoli Asset Management for IT middleware images, and then click Next. Copy the middleware install images from the source media to a specified directory Select this option to copy the Tivoli Asset Management for IT middleware images from the product media to a directory that you will specify. Specify a directory containing all the required middleware install images Select this option if you intend to specify a filesystem directory that already contains all of the Tivoli Asset Management for IT middleware installation images. 26. If you selected the option to copy install images from the source media, specify the source and destination directories, and then click Next. If you selected the option to specify a directory that already contained the middleware images, specify that directory, and then click Next. 27. Specify a directory to use for Tivoli middleware installer temporary files and extracted middleware installation images, and then click Next. 28. From the Deployment Plan Operation panel, select Deploy the plan, and then click Next.

38

Installation Guide for IBM WebSphere Application Server:

You can also elect to make changes to the deployment plan or parameters you have previously configured from this panel. 29. From the Deployment Plan and Parameter Configuration summary panel, review the contents of the summary, and then click Deploy to initiate the installation and configuration of the middleware you selected. 30. Once the deployment completes successfully, click Finish to exit.

Tivoli middleware installer logs

Tivoli middleware installer log files are located in the workspace directory that was defined in the Tivoli middleware installer. The different types of log files are described below. User interface logs The logs generated by the Tivoli middleware installer user interface are located in the workspace directory. The mwi.log file is the high-level log file that was generated by the most recent invocation of the Tivoli middleware installer. If an error occurs, examine this log file first. An entry in this log file may direct you to a lower-level log file. Log files named mwi.logX, where X is a number, are copies of the mwi.log file from earlier invocations of the Tivoli middleware installer So, for example, mwi.log0 is produced after the first invocation of Tivoli middleware installer, mwi.log1 is produced after the second invocation of Tivoli middleware installer, and so on. Logs for steps run by the user interface In addition to collecting input from the user, the user interface of the Tivoli middleware installer also performs several system checks. Examples of system checks run by the user interface runs include: v dependency checking to ensure the operating system meets the deployment requirements v inventorying the software on the system to locate existing instances of middleware products deployed by the Tivoli middleware installer v checking the available disk space to ensure there is enough for the deployment Each of these checks is produced in the form of a step so that it can also be run as part of the deployment plan. When the user interface runs a step, it copies the step into a subdirectory of the workspace directory. The log files generated by a step are located in the same subdirectory and follow the same pattern as a step that is run as part of the deployment plan. Logs for the deployment plan The deployment plan is located in the directory <Workspace Directory>/hostname/deploymentPlan, where hostname is the hostname of the current system. Each time the deployment plan is used to install or uninstall middleware products, a process ID is assigned and log files are generated. The log files for the deployment plan are located in the subdirectory logs/processID. The primary log file for the deployment plan is DeploymentPlan.log, a high-level log file that lists the steps invoked as part of the deployment plan.

Chapter 4. Tivoli Asset Management for IT middleware installation

39

Logs for the machine plan The machine plan is located in the directory <Workspace Directory>/hostname/deploymentPlan/MachinePlan_hostname. The log files for the machine plan are located in the logs subdirectory. The primary log files for the machine plan are named MachinePlan_hostname_processID. These log files contain the output generated by ANT when running the machine plan ANT script. Logs for steps in the deployment plan Each step in the deployment plan is located in a directory named <Workspace Directory>/hostname/deploymentPlan/ MachinePlan_hostname/stepNum_stepID, where stepNum is the sequence number of this step in install processing order of the deployment plan and stepID identifies the step. The log files for the step are located in the logs subdirectory. Some steps may provide a message log file named stepID_processID.message, which contains a few entries that summarize the result of invoking the step. All steps will provide a trace log file named stepID_processID.log, which contains many entries, usually including information about the input parameters and the substeps invoked. Logs for substeps Each step contains one or more substeps. The substeps perform the actual install, uninstall and checking work for the Tivoli middleware installer. Each substep is located in the directory <Workspace Directory>/hostname/ deploymentPlan/MachinePlan_hostname/stepNum_stepID/operation/ substepNum_substepID, where operation is the ANT target in the step ANT script that invokes this substep. substepNum is the sequence number of this substep in the processing order of the step, and substepID identifies the substep. Typical values for operation are install, uninstall, and check. The log files for the substep are usually located in a subdirectory named processID/logs. Log files generated by the native middleware installation programs will also be kept here.

Starting Tivoli Asset Management for IT middleware on Windows

This procedure describes how to start middleware on Windows, should you need to restart any middleware services. To properly start middleware products on Windows, perform the following steps: 1. Log in as a user with Administrative permissions. 2. Start servers by executing the following scripts in the order in which they are listed: Start ctginst1 a. Click Start, and select Run. b. Type services.msc, and click OK. c. Select DB2 - DB2COPY1 - CTGINST1-0, and click Start the service. Alternatively, you can use the db2start command from a command line to start CTGINST1. Start ITDS Admin Daemon a. Click Start, and select Run.

40

Installation Guide for IBM WebSphere Application Server:

b. Type services.msc, and click OK. c. Select IBM Tivoli Directory Admin Daemon V6.1 - idsccmdb, and click Start the service. Alternatively, you can use the following command from the command line to start the ITDS admin daemon:
idsdiradm -I idsccmdb

Start the ITDS instance: a. Click Start, and select Run. b. Type services.msc, and click OK. c. Select IBM Tivoli Directory Server Instance V6.1 - idsccmdb, and click Start the service. Alternatively, you can use the following command from the command line to start the ITDS instance:
idsslapd -I idsccmdb

Important: The IBM Tivoli Directory Server Instance must remain as a manual startup type. It must be started manually in order to synchronize correctly with the database in the context of Tivoli Asset Management for IT. Start HTTP Server and webserver1 a. Click Start and select Run b. Type services.msc, and click OK. c. Select IBM HTTP Server 6.1, and click Start the service. Alternatively, you can type apache from the command line to start the HTTP Server . Start Domain Manager <WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat Start Node <WAS_HOME>\profiles\ctgAppSvr01\bin\startNode.bat Start MXServer <WAS_HOME>\profiles\ctgAppSrv01\bin\startServer.bat MXServer

Starting Tivoli Asset Management for IT middleware on UNIX

This procedure describes how to start middleware on Linux and UNIX platforms, should you need to restart any middleware services. To properly start middleware products on Linux and UNIX systems, perform the following steps: 1. Log in as root. 2. Start servers by executing the following scripts in the order in which they are listed: Start ctginst1 instance su - ctginst1 -c db2start Start ITDS Admin Daemon <ITDS_HOME>/sbin/idsdiradm -I idsccmdb Start ITDS server daemon: ibmslapd <ITDS_HOME>/sbin/ibmslapd -I idsccmdb
Chapter 4. Tivoli Asset Management for IT middleware installation

41

Start HTTP Server Linux /opt/IBM/HTTPServer/bin/apachectl start AIX /usr/IBM/HTTPServer/bin/apachectl start

Sun Solaris /opt/IBM/HTTPServer/bin/apachectl start Start Deployment Manager <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh Start Node <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh Start webserver1 <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh webserver1 -username <username> -password <password> Start MXServer <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer -username <username> -password <password>

Reusing middleware
If you intend to reuse existing Tivoli Asset Management for IT middleware servers, they must be configured prior to running the Tivoli Asset Management for IT installation program. This section contains information about configuring existing DB2 and ITDS servers for use with Tivoli Asset Management for IT using the Tivoli middleware installer. You cannot use the Tivoli middleware installer to configure existing Oracle, MS SQL, or Microsoft Active Directory servers. Refer to Tivoli Asset Management for IT installation with manual middleware configuration on page 86 for more information about those servers. Information found in Tivoli Asset Management for IT installation with manual middleware configuration on page 86 also applies if you decide that you want to reuse existing Tivoli Asset Management for IT middleware servers but you want to configure them to work with Tivoli Asset Management for IT manually instead of allowing the Tivoli Asset Management for IT installation program to configure them. Ensure that all of your middleware is at the level described in Tivoli Asset Management for IT component requirements on page 3.

Reusing DB2
If you have an existing DB2 installation that you would like to reuse for Tivoli Asset Management for IT, run the Tivoli middleware installer on the system. The Tivoli middleware installer will identify instances of middleware that already exist on the system that are compatible with Tivoli Asset Management for IT, and it will configure the existing instance for use with Tivoli Asset Management for IT. To have the Tivoli middleware installer configure an existing DB instance for reuse with Tivoli Asset Management for IT, complete the following steps: 1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad.

42

Installation Guide for IBM WebSphere Application Server:

3. Proceed through the Tivoli middleware installer panels as instructed in Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer on page 31, until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, select Database Server, and then click Next. The Tivoli middleware installer will display any instances of DB2 found 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 the Tivoli middleware installer panels. Refer to Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer on page 31 for more information. Note that if you are reusing an existing DB2 server with Tivoli Asset Management for IT, the following users and groups must already exist on the system. Users v db2admin v dasusr1 (UNIX) v db2fenc1 (UNIX) Groups v db2admns (Windows) v dasadm1 (UNIX) v dbgrp1 (UNIX) v db2fgrp1 (UNIX) If these users do not exist on the system, you will have to create them prior to running the Tivoli Asset Management for IT installation program.

Reusing Oracle
If you have an existing Oracle 10g instance that you would like to reuse for Tivoli Asset Management for IT, you will have to manually configure it. Refer toManually configuring Oracle 10g on page 93 for information. For an existing Oracle 9.2 instance, refer to Manually configuring Oracle9i Rel2 on page 95

Reusing IBM Tivoli Directory Server

If you have an existing IBM Tivoli Directory Server installation that you would like to reuse for Tivoli Asset Management for IT, run the Tivoli middleware installer on the system. The Tivoli middleware installer will identify middleware that already exists on the system that is compatible with Tivoli Asset Management for IT, and it will configure it for use with Tivoli Asset Management for IT. Note: The Tivoli middleware installer will create a new instance on the existing IBM Tivoli Directory Server that you identify. This new instance will contain default Tivoli Asset Management for IT LDAP information. If you intend to use Tivoli Asset Management for IT with an existing IBM Tivoli Directory Server instance that contains your organizations LDAP information, do not run the Tivoli middleware installer to configure the existing IBM Tivoli Directory Server. To use the existing IBM Tivoli Directory Server instance that contains your organizations
Chapter 4. Tivoli Asset Management for IT middleware installation

43

LDAP information with Tivoli Asset Management for IT, refer to Manually configuring IBM Tivoli Directory Server on page 99. To have the Tivoli middleware installer configure an existing IBM Tivoli Directory Server instance for reuse with Tivoli Asset Management for IT, complete the following steps: 1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad. 3. Proceed through the Tivoli middleware installer panels as instructed in Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer on page 31, until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, select Directory Server, and then click Next. The Tivoli middleware installer will display any instances of IBM Tivoli Directory Server found 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 the Tivoli middleware installer panels. Refer to Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer on page 31 for more information.

Reusing Microsoft Active Directory

If you have an existing Microsoft Active Directory instance, you can use it to secure WebSphere when you install it on the system. The Tivoli middleware installer will prompt you for LDAP configuration parameters to use with WebSphere. To have the Tivoli middleware installer configure an existing Microsoft Active Directory instance to secure WebSphere, complete the following steps: 1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad. 3. Proceed through the Tivoli middleware installer panels as instructed in Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer on page 31, until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, deselect the Directory Server deployment option, and then click Next. In the next panel, will be given the choice of selecting an existing instance of IBM Tivoli Directory Server or Microsoft Active Directory to secure WebSphere. 5. Select Secure with Active Directory, and click Next. 6. Supply the following configuration values for WebSphere security, and then click Next. LDAP Hostname Enter the fully qualified name of the machine hosting Microsoft Active Directory. Directory server port 389

44

Installation Guide for IBM WebSphere Application Server:

LDAP base entity DC=itsm,DC=com User suffix OU=Users,OU=SWG,DC=itsm,DC=com Group suffix OU=Groups,OU=SWG,DC=itsm,DC=com Organization container suffix DC=itsm,DC=com In this example. itsm is the domain name. You need to replace itsm with the name of your own domain. 7. Supply the following configuration values for WebSphere security, and then click Next. Bind distinguished name CN=Administrator,CN=Users,DC=itsm,DC=com This value assumes that the Administrator user is already a member of the itsm domain. Bind password Enter the password for the Administrator user on the system hosting Microsoft Active Directory. In this example. itsm is the domain name. You need to replace itsm with the name of your own domain. 8. Complete the installation by proceeding through the remainder of the Tivoli middleware installer panels. Refer to Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer on page 31 for more information. Note that prior to running the Tivoli Asset Management for IT installation program, you must manually create the users and groups listed in Manually configuring Microsoft Active Directory on page 102. This step can be performed after you have installed middleware using the Tivoli middleware installer, but it must be completed before you begin using the Tivoli Asset Management for IT installation program.

Uninstalling Tivoli Asset Management for IT middleware

Uninstalling middleware consists of running the Tivoli middleware installer and using it to undeploy the previously deployed deployment plan. Note: You must use the Tivoli middleware installer to uninstall any Tivoli Asset Management for IT middleware installed by the Tivoli middleware installer. The Tivoli middleware installer creates a registry when installing Tivoli Asset Management for IT middleware. If you use the native middleware uninstall programs, this registry will be out of sync with what is deployed. This will cause errors if you then try to reinstall Tivoli Asset Management for IT middleware using the Tivoli middleware installer. Note: At points during the uninstall process, the Tivoli middleware installer uninstall progress bar might appear to pause. This is normal behavior. In most cases, the Tivoli middleware installer uninstall progress bar will resume shortly

Chapter 4. Tivoli Asset Management for IT middleware installation

45

after pausing. If you suspect your uninstall process has experienced an error, refer to the Tivoli middleware installer log files. To uninstall the J2EE server, ensure the directory server (IBM Tivoli Directory Server or Active Directory) is active. Do not uninstall the directory server until the J2EE server has been uninstalled. To undeploy Tivoli Asset Management for IT middleware, complete the following steps: 1. Login as Administrator on Windows and root on Linux, AIX and Sun Solaris. 2. Launch the Tivoli middleware installer from the launchpad. a. Start the launchpad: v Windows: On the DVD titled Tivoli Asset Management for IT V7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.exe. v Linux: On the DVD titled Tivoli Asset Management for IT V7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh. v AIX : On the DVD titled Tivoli Asset Management for IT V7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh. v Sun Solaris: On the DVD titled Tivoli Asset Management for IT V7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh 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. 5. The Tivoli middleware installer license agreement window is displayed. 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 the workspace will be the last workspace location specified. The default location for the workspace is c:\ibm\tivoli\mwi\ workspace 7. From the Select Operation panel, select Undeploy the plan, and then click Next. 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 Tivoli middleware installer.

Installing Tivoli Asset Management for IT middleware on zLinux (Linux/390)

While the Tivoli Asset Management for IT middleware installation program does not support the automated installation of Tivoli Asset Management for IT middleware on zLinux systems, the Tivoli Asset Management for IT product package includes installation images for the following middleware products: v IBM DB2 9.1 v IBM Tivoli Directory Server 6.1

46

Installation Guide for IBM WebSphere Application Server:

v WebSphere Application Server ND 6.1 Using the native installation program for each product, you could install middleware manually in the order shown above if you choose to deploy Tivoli Asset Management for IT in an environment where zLinux systems will host Tivoli Asset Management for IT middleware. If you have existing DB2 and Tivoli Directory Server instances at the appropriate level in your network, you can also reuse those resources in your Tivoli Asset Management for IT deployment. IBM Tivoli Directory Server uses DB2 as its data repository, while WebSphere uses IBM Tivoli Directory Server for security. You will have to copy the images off of the product media provided and uncompress them onto your system.

Installing and configuring DB2 on zLinux

Use this information to successfully install and configure DB2 on zLinux. To install DB2 version 9 on your zLinux system, certain operating system, hardware, and communications prerequisites must be met. Before you start the DB2 Setup wizard, consider the following: v Refer to the relevant information for installing DB2 on Linux at the DB2 9 Enterprise Edition infocenter: http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp. v Ensure that your system meets installation, memory, and disk requirements. Refer to the DB2 9 Enterprise Edition infocenter to ensure you meet all hardware and software prerequisites. v You must have root authority to perform the installation. v The DB2 product image must be available. If the Tivoli Asset Management for IT 7.1 Middleware for zLinux DVD does not automount, mount your Tivoli Asset Management for IT 7.1 Middleware for zLinux product DVD. v The DB2 Setup wizard is a graphical installer (Available only on Linux for x86 and Linux on AMD 64/EM64T.). You must have X windows software capable of rendering a graphical user interface for the DB2 Setup wizard to run on your machine. Ensure that the X windows server is running. Ensure that you have properly exported your display. For example, export DISPLAY=<youripaddress>:0. v (DB2 Clients only) If you plan to use Kerberos Authentication, you require IBM Network Authentication Service (NAS) client version 1.4 or higher. The NAS client can be downloaded from https://www6.software.ibm.com/dl/dm/dmnas-p. v One of the following browsers is required to view online help and to run First Steps (db2fs): Mozilla 1.4 and up Firefox 1.0 and up Netscape 7.0 and up The use of XML features is restricted to a database that is defined with the code set UTF-8 and has only one database partition. The DB2 Setup wizard is used to define your installation preferences and to install your DB2 product on your system. Features include:

Chapter 4. Tivoli Asset Management for IT middleware installation

47

v A launchpad from which you can view installation notes and release notes, and learn about DB2 Version 9 features. v Selecting DB2 installation type (typical, compact, or custom). v Selecting DB2 product installation location. v Setting up database partitioning options for the DB2 instance. v Setting the user interface and product messages. The user interface and product messages are available in several languages and are installed in the languages that you choose. By installing multiple languages, you can view the interface and messages in your preferred languages. v Setting up the DB2 Administration Server (including DAS user setup). v Setting up Administration contact and health monitor notification. v Setting up and configuring your instance setup and configuration (including instance user setup). v Preparing the DB2 tools catalog. v Creating response files. Installation help is available from the DB2 Setup wizard installation panels to guide you through the steps. To invoke the installation help, click Help or press F1. You can click Cancel at any time to end the installation. Your DB2 product will be installed, by default, in the /opt/IBM/db2/V9.1 directory. The installation logs, db2setup.log and db2setup.err will be located, by default, in the /tmp directory. You can specify the location of the log files. The db2setup.log file captures all DB2 installation information including errors. The db2setup.err file captures any error output that is returned by Java (for example, exceptions and trap information). To install DB2 on zLinux, follow these steps: 1. Log in as root. 2. Create a user (recommended value is maximo with a password of maximo) on the system and assign the new user to a group with administrative authority. 3. Insert the Tivoli Asset Management for IT 7.1 Middleware for zLinux DVD in your DVD-ROM drive. 4. Change directory to linux390\DB2-ESE_9.1.0 on the DVD. 5. Copy the DB2_Enterprise_Svr_Ed_Linux_zSeries.tar file down to a local directory on your system. 6. Unpack the file: tar -xvf DB2_Enterprise_Svr_Ed_Linux_zSeries.tar. 7. Type ./db2setup to start the DB2 Setup wizard. The IBM DB2 Setup launchpad opens. From this window, you can view installation prerequisites and the release notes, or you can proceed directly to the installation. You may want to review the installation prerequisites and release notes for late-breaking information. 8. Click Install a Product. The Install a Product window will display the products available for installation. 9. Launch the DB2 Enterprise Server Edition installation by clicking Install New. The Welcome to DB2 setup wizard panel is displayed. 10. Click Next. The Software License Agreement panel is displayed. 11. Review the license agreement displayed, select Accept, and then click Next. The Select the installation type panel is displayed.

48

Installation Guide for IBM WebSphere Application Server:

12. Select Typical: 410 - 500 MB, and then click Next. The Selection installation, response file creation, or both panel is displayed. 13. Select Install DB2 Enterprise Server Edition on this computer and save my settings in a response file. You will have to enter a location and file name to store response file values. 14. Enter a path and filename for the response file, and then click Next. The Select the installation directory panel is displayed. 15. Provide the following information, and then click Next. Directory Designate a directory for installing DB2. By default, this path is /opt/IBM/db2/V9.1. The Set user information for the DB2 Administration Server panel is displayed. 16. Provide the following information, and then click Next. New user Select New user to enable the fields for creating a new DB2 user. User name Enter a user name to associate with the DB2 administration server. The user name should consist of 1 - 8 characters. The default is dasusr1. The user name should have SYSADM authority so it can start and stop instances. UID Leave Use default UID checked to have the installation program generate a UID for the user.

Group name Enter a primary group for the user. If it does not already exist on the system, it will be created. The default is dasadm1. GID Leave Use default GID checked to have the installation program generate a GID for the group.

Password Create a password for the user. The password should consist of 1 - 8 characters Home directory Enter a directory to use for storing information about the database instance. The default is /home/dasusr1. The Set up a DB2 instance panel is displayed. 17. Select Create a DB2 instance, and then click Next. The Set up partitioning options for the DB2 instance panel is displayed. 18. Select Single partition instance, and then click Next. If you wish to set up the DB2 instance across multiple partitions, refer to the installation wizard panel help by using the F1 function key. The Set user information for the DB2 instance owner panel is displayed. 19. Provide the following information, and then click Next.
Chapter 4. Tivoli Asset Management for IT middleware installation

49

New user Select New user to enable the fields for creating a new DB2 user. User name Enter a user name to associate with the DB2 instance. The user name should consist of 1 - 8 characters. The default is ctginst1. The user name should have SYSADM authority so it can start and stop instances. UID Leave Use default UID checked to have the installation program generate a UID for the user.

Group name Enter a primary group for the user. If it does not already exist on the system, it will be created. The default for UNIX is db2grp1. GID Leave Use default GID checked to have the installation program generate a GID for the group.

Password Create a password for the user. The password should consist of 1 - 8 characters Home directory Enter a directory to use as the home directory of the database instance user. The default is /home/ctginst1. The Set user information for the fenced user panel is displayed. 20. Provide the following information, and then click Next. New user Select New user to enable the fields for creating a new DB2 user. User name Enter a user name to assign as the fenced user. The user name should consist of 1 - 8 characters. The default is db2fenc1. The user name should have SYSADM authority so it can start and stop instances. UID Leave Use default UID checked to have the installation program generate a UID for the user.

Group name Enter a primary group for the user. If it does not already exist on the system, it will be created. The default is db2fgrp1. GID Leave Use default GID checked to have the installation program generate a GID for the group.

Password Create a password for the user. The password should consist of 1 - 8 characters

50

Installation Guide for IBM WebSphere Application Server:

Home directory Enter a directory to use as the home directory of the fenced user.. The default is /home/db2fenc1. The Prepare the DB2 tools catalog panel is displayed. 21. Select Do not prepare the DB2 tools catalog, and then click Next. If you wish to set up the DB2 tools catalog, refer to the installation wizard panel help for more information by using the F1 function key. The Set up notifications panel is displayed. 22. Select Set up your DB2 server to send notifications, provide the following information, and then click Next. Notification SMTP server Enter the name of the SMTP server that will be responsible for sending database notifications to the database administrator. Administration contact list location Local Remote Select Remote and then provide the fully qualified name of the remote DB2 server to use an existing contact list that will be used remotely. The Specify a contact for the health monitor notification panel is displayed. 23. Select New contact, provide the following information, and then click Next. Name Enter the user name of the individual assigned to receive notifications related to the state of the DB2 instance The default is ctginst1. E-mail address Enter the e-mail address for the contact entered in the Name field. The Start copying files and create response file panel is displayed. 24. Click Finish to initiate the installation. 25. After successfully completing the DB2 installation, install DB2 Fix Pack 2. a. Change directory to linux390\DB2-Universal_9.1_Fixpacks on the zLinux Middleware DVD. b. Copy the v9fp2_linux390_universal_fixpack.tar.gz file down to a local directory on your system. c. Uncompress the file: gzip -dfv v9fp2_linux390_universal_fixpack.tar.gz d. Unpack the file: tar -xvf v9fp2_linux390_universal_fixpack.tar e. cd to universal/disk1 then run ./installFixPack to start the Fix Pack installation. f. When prompted, enter the install location of DB2. g. After the Fix Pack installation has concluded, stop all instances associated with this copy. su - db2inst1 db2stop Select Local to create a contact list on the local machine.

Chapter 4. Tivoli Asset Management for IT middleware installation

51

h. Run update: <DB2DIR>/instance/db2iupdt -e 26. Start the DB2 instances.

Installing and configuring IBM Tivoli Directory Server on zLinux

Use this information to successfully install and configure IBM Tivoli Directory Server on zLinux. There are two installation paths used in the IBM Tivoli Directory Server installation program. Typical Use the Typical installation path if you want to accept default settings, install all the IBM Tivoli Directory Server components that are not already installed, and create a default directory server instance. Typical installation does not allow you to select features for installation. Custom Use the Custom installation path if you want to select components for installation and create a directory server instance using the Instance Administration Tool. When you use this tool you can customize the directory server instance. This section will detail how to install IBM Tivoli Directory Server using the Custom installation path on a machine that is not hosting other Tivoli Asset Management for IT prerequisite components. For more information about reusing an existing DB2 server for use with IBM Tivoli Directory Server, consult the IBM Tivoli Directory Server product information for conducting an IBM Tivoli Directory Server custom installation. Note that IBM Tivoli Directory Server cannot make use of a remote DB2 server as its data repository. Also, Tivoli Asset Management for IT is not designed to interact with a system that has two different active copies of DB2 running at the same time, so plan accordingly when you are designing your Tivoli Asset Management for IT deployment. To install IBM Tivoli Directory Server V6.1 on your zLinux system, the following operating system, hardware, and communications prerequisites must be met:
Table 11. Prerequisite Comments

To install IBM Tivoli Directory Server 6.1 using the Custom installation path, follow these steps: 1. Log in as root. 2. Insert the Tivoli Asset Management for IT 7.1 Middleware for zLinux DVD in your DVD-ROM drive. 3. Change directory to linux390 on the DVD. 4. Copy the tds61-linux-s390x-CD1_w_entitlement.tar file down to a local directory on your system.

52

Installation Guide for IBM WebSphere Application Server:

5. Unpack the file: tar -xvf tds61-linux-s390x-CD1_w_entitlement.tar 6. Change to the /tdsV6.1/tds directory and then type ./install_tds.sh If you prefer, you can specify a temporary directory other than the system temporary directory. To use this option, change directories to the appropriate directory and type ./install_tds.sh -is:tempdir directory at a command prompt, where directory is the directory you want to use for temporary space. Be sure that you have at least 400 MB of free space in this directory. For example: ./install_tds.sh -is:tempdir /opt/tmp The Select Language panel is displayed. 7. Select the language you want to use during IBM Tivoli Directory Server installation, and then click OK. This is the language used in the installation program, not in IBM Tivoli Directory Server. The language used in IBM Tivoli Directory Server is determined by the language pack you install. The Welcome panel is displayed. 8. Click Next. The License Agreement panel is displayed. 9. Read the software license agreement, select I accept both the IBM and the non-IBM terms, and then click Next. 10. Select Custom and then click Next. 11. De-select DB2 V9.1, Embedded WebSphere Application Server, and Tivoli Directory Integrator, and then click Next. You will install the products separately. The Select WebSphere Application Server panel is displayed. 12. Select Do not specify. I will manually deploy at a later time, and then click Next. The Summary panel is displayed. 13. Click Install. IBM Tivoli Directory Server will be installed into the /opt/IBM/ldap/V6.1 directory. 14. Click Finish. The Tivoli Directory Server instance creation tool will now launch. 15. Create the idsccmdb ITDS instance. Refer to Manually configuring IBM Tivoli Directory Server on page 99 for more information. 16. Start ITDS. /opt/IBM/ldap/V6.1/sbin/idsdiradm -I idsccmdb /opt/IBM/ldap/V6.1/sbin/ibmslapd -I idsccmdb

Installing and configuring WebSphere Application Server Deployment Manager on zLinux

Use this information to successfully install and configure WebSphere Application Server Deployment Manager on zLinux. This section provides instructions for installing WebSphere Application Server Deployment Manager on zLinux. To install WebSphere Application Server Deployment Manager V6.1 (32-bit) on your zLinux system, the following operating system, hardware, and communications prerequisites must be met:
Table 12. Prerequisite Comment

To install WebSphere Application Server Deployment Manager, follow these steps: 1. Log in as root.
Chapter 4. Tivoli Asset Management for IT middleware installation

53

2. Insert the Tivoli Asset Management for IT 7.1 Middleware for zLinux DVD in your DVD-ROM drive. 3. Change directory to linux390/WS-WAS_ND_6.1.0.13_Custom_ISCAE71 on the DVD. 4. Copy the WAS-ND_linux390_Custom_v6113.tar.gz file down to a local directory on your system. 5. Uncompress the file: gzip -dfv WAS-ND_linux390x_Custom_v6113.tar.gz 6. Unpack the file: tar -xvf WAS-ND_linux390x_Custom_v6113.tar 7. Enter the ./install command from the WebSphere directory, /WAS, for example, where you unpacked the tar file to start the WebSphere Setup wizard. The Welcome to the IBM WebSphere Application Server Network Deployment install wizard panel is displayed. 8. Click Next. The Software License Agreement panel is displayed. 9. Review the license agreement displayed, select Accept, and then click Next. The Prerequisite Check panel is displayed. 10. Confirm that your operating system is supported and that you have installed all necessary patches, and then click Next. The Installation Directory panel is displayed. 11. Enter the installation path for IBM WebSphere Application Server Network Deployment, and then click Next. The default is /opt/IBM/WebSphere/ AppServer. Do not use symbolic links as the destination directory. Symbolic links are not supported. Spaces are not supported in the name of the installation directory. The WebSphere Application Server Environments panel is displayed. 12. Select None as your environment, and then click Next. Selecting None means you will be creating the Tivoli Asset Management for IT deployment cell, deployment manager profile, and the application server profile using the profile management tool. 13. Click Yes to indicate that you want to proceed. The Installation Summary panel is displayed. 14. Click Next. The Installation Results panel is displayed. 15. Click Finish.

Creating profiles using 64-bit WebSphere Application Server Deployment Manager for zLinux
Use this information to successfully create profiles using 64-bit WebSphere Application Server Deployment Manager for zLinux. This section provides instructions for creating two profiles that will be expected by the Tivoli Asset Management for IT installation program. To create 64-bit WebSphere Application Server Deployment Manager profiles on your zLinux system, the following prerequisite tasks must first be completed:

54

Installation Guide for IBM WebSphere Application Server:

Table 13. Prerequisite Task Augment the ctgDmgr01 profile. Command <WAS_HOME>/bin/manageprofiles.sh -augment -templatePath <WAS_HOME>/ profileTemplates/iscae71 -profileName ctgDmgr01 -serverName dmgr <WAS_HOME>/profiles/ctgDmgr01/bin/ stopManager.sh -username <username> -password <password> <WAS_HOME>/profiles/ctgDmgr01/bin/ startManager.sh

Restart servers after augmenting the ctgDmgr01 profile.

The 64-bit version of IBM WebSphere Network Deployment for zLinux includes the manageprofiles command line tool which you will use to create profiles required by Tivoli Asset Management for IT. The following commands can be useful for managing profiles:
Table 14. Profile commands Task Delete a profile Refresh the profile registry (for example, after deleting a profile) List existing profiles Command <WAS_HOME>/bin/manageprofiles.sh -delete -profileName <profile name> <WAS_HOME>/bin/manageprofiles.sh -validateAndUpdateRegistry <WAS_HOME>/bin/manageprofiles.sh -listProfiles

To create profiles, follow these steps: 1. Source the setupCmdLine.sh script in the bin directory of the <WAS_HOME> folder to set the WebSphere Application Server environment to the configuration instance. <WAS_HOME>/bin/setupCmdLine.sh 2. Create a profile ports file for the ctgDmgr01 profile. This file will be used by the manageprofiles command to set the ports that will be used by this profile. It is important that you ensure no spaces appear after any value in this file. If there is an extra space trailing any of the values, as can happen when cutting and pasting an example, WebSphere will use that space as the last character of that value. For example, you might intend the value WC_adminhost=9060, but with an extra space, that value will be WC_adminhost=9060<sp> where <sp> denotes a blank space. a. Create a new text file named _portdef_DMgr.props and enter the following text: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9403 WC_adminhost=9060 DCS_UNICAST_ADDRESS=9352 BOOTSTRAP_ADDRESS=9809 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9401 CELL_DISCOVERY_ADDRESS=7277 SOAP_CONNECTOR_ADDRESS=8879

Chapter 4. Tivoli Asset Management for IT middleware installation

55

3.

4. 5.

6.

7. 8.

ORB_LISTENER_ADDRESS=9100 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9402 WC_adminhost_secure=9043 b. Place the file in the <WAS_HOME> directory. Create the ctgDmgr01 profile using the manageprofiles command: <WAS_HOME>/bin/manageprofiles.sh -create -templatePath <WAS_HOME>/profileTemplates/dmgr -hostName yourfullyqualifiedhost -profileName ctgDmgr01 -profilePath <WAS_HOME>/profiles/ctgDmgr01 -portsFile <WAS_HOME>/_portdef_DMgr.props -cellName ctgCell01 -nodeName ctgCellManager01 -enableAdminSecurity false -adminUserName wasadmin -adminPassword wasadmin Start the ctgDmgr01 server: <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh Create a profile ports file for the ctgAppSrv01 profile. This file will be used by the manageprofiles command to set the ports that will be used by this profile. a. Create a new text file named _portdef_AppSvr.props and enter the following text: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9201 DCS_UNICAST_ADDRESS=9353 NODE_DISCOVERY_ADDRESS=7272 NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS=5001 BOOTSTRAP_ADDRESS=2809 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9901 SOAP_CONNECTOR_ADDRESS=8878 NODE_MULTICAST_DISCOVERY_ADDRESS=5000 ORB_LISTENER_ADDRESS=9101 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9202 b. Place the file in the <WAS_HOME> directory. Create the ctgAppSrv01 profile using the manageprofiles command: <WAS_HOME>/bin/manageprofiles.sh -create -templatePath <WAS_HOME>/profileTemplates/managed -hostName yourfullyqualifiedhost -profileName ctgAppSrv01 -profilePath <WAS_HOME>/profiles/ctgAppSrv01 -cellName ctgNodeCell01 -nodeName ctgNode01 -portsFile <WAS_HOME>/_portdef_AppSvr.props -dmgrHost yourfullyqualifiedhost -dmgrAdminUserName wasadmin -dmgrAdminPassword wasadmin -dmgrPort 8879 -isDefault If it is not already started, start the ctgAppSrv01 node. <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh Launch firststeps.sh to verify installation: <WAS_HOME>/profiles/ctgDmgr01/firststeps/firststeps.sh

56

Installation Guide for IBM WebSphere Application Server:

Installing and configuring IBM HTTP Server on zLinux

Use this information to successfully install and configure IBM HTTP Server on zLinux. This section provides instructions for installing IBM HTTP Server on zLinux. To install IBM HTTP Server, follow these steps: 1. Log in as root on the machine where you have installed WebSphere. 2. Log into the WebSphere Administration Console and ensure the ctgDmgr01 deployment manager is running and the SOAP port is set to listen at the correct port (8879 is the default). If the deployment manager needs to be started, use the following command: <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh 3. From a command line, launch the IBM HTTP Server installation program: <WebSphere Image Directory>/IHS/install The Welcome panel is displayed. 4. Click Next. The License Agreement panel is displayed. 5. Accept the license agreement and click Next System prerequisites check panel is displayed. 6. Click Next. 7. Specify the install location information and click Next. The default is /opt/IBM/HTTPServer. The Port Values Assignment panel is displayed. 8. Specify the following values and then click Next. HTTP Port 80 HTTP Administration Port 8008 The Setup HTTP Administration Server panel is displayed. 9. Create a User ID for IBM HTTP Administration server authentication and click Next. 10. Specify the following values, and click Next. Setup IBM HTTP administration server to administer IBM HTTP Server Enabled Create a unique user ID and group for IBM HTTP Server administration Enabled User ID wasadmin Group ihsadmin The IBM HTTP Server Plug-in for WebSphere Application Server panel is displayed. 11. Specify the following values, and click Next. Install the IBM HTTP Server Plug-in for IBM WebSphere Application Server Disable In an environment where you have multiple deployment manager profiles, it is more practical to run the Web server plug-ins installation task separately by running the plug-in installation program after
Chapter 4. Tivoli Asset Management for IT middleware installation

57

exiting the IBM HTTP Server installation program. However, if your WebSphere environment only contains the single deployment manager profile used for Tivoli Asset Management for IT, you can leave the WebSphere plug-in option selected, which will launch the Web server plug-ins installation task when you click Next. The Installation Summary panel is displayed. 12. Click Next. 13. Click Finish. 14. Install the following IBM HTTP Server fixpack: linux390\WSWAS_IHS_6.1.0_FP13\6.1.0-WS-IHS-LinuxS39064-FP0000013.pak For more information about deployment scenarios for IBM HTTP Server, refer to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/ com.ibm.websphere.ihs.doc/info/welcome_ihs.html .

Installing and configuring the WebSphere Plug-in on zLinux

Use this information to successfully install and configure the WebSphere Plug-in on zLinux. This section provides instructions for installing the WebSphere Plug-in on zLinux. To install the WebSphere Plug-in, follow these steps: 1. Log in as root on the machine where you have installed WebSphere. 2. From a command line, launch the WebSphere Plug-in installation program: <WebSphere Image Directory>/plugin/install The Welcome panel is displayed. 3. 4. 5. 6. 7. Click Next. The License Agreement panel is displayed. Accept the license agreement and click Next From the system check panel, click Next Select WebSphere Application Server machine (local), and then lick Next. The web server install path panel is displayed. Browse to the directory where you installed IBM HTTP Server, and then click Next. By default, this directory is listed as /opt/IBM/HTTPServer/Plugins. The WebSphere install path panel is displayed. Browse to the directory where you installed WebSphere, and then click Next. By default, this directory is listed as /opt/IBM/WebSphere/AppServer. The select profile panel is displayed. Select ctgDmgr01 from the drop-down list, and then click Next. The web server configuration file panel is displayed. Specify the following: Select the existing IBM HTTP Server httpd.conf file Browse to the location of the httpd.conf file. By default, this file is located at /opt/IBM/HTTPServer/conf/httpd.conf. Specify the Web server port 80 The Web server definition panel is displayed. 11. Specify a unique Web server definition name (webserver1, for example), and then click Next. The Web server plugin-cfg.xml file panel is displayed. 12. Accept the default, and click Next. The input summary panel is displayed.

8.

9. 10.

58

Installation Guide for IBM WebSphere Application Server:

13. Click Next. The installation summary panel is displayed. 14. When the installation is complete, click Finish. 15. Install the following WebSphere Plug-in fixpack: linux390\WSWAS_Plugins_6.1.0_FP13\6.1.0-WS-PLG-LinuxS39064-FP0000013.pak 16. Restart deployment manager: Stop the deployment manager <WAS_HOME>/profiles/ctgDmgr01/bin/stopManager.sh Start the deployment manager <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh Copy the /opt/IBM/HTTPServer/Plugins/bin/configurewebserver1.sh file to <WAS_HOME>/bin/ Change directory to <WAS_HOME>/bin and then execute the following command: ./configurewebserver1.sh Start the HTTP servers: /opt/IBM/HTTPServer/bin/adminctl start /opt/IBM/HTTPServer/bin/apachectl start Login to the WebSphere administrator console and ensure that webserver1 has started.

17. 18.

19.

20.

Installing and configuring IBM Agent Controller on zLinux

Use this information to successfully install and configure IBM Agent Controller on zLinux. This section provides instructions for installing IBM Agent Controller on zLinux. The IBM Agent Controller is used to retrieve log and trace data for use by the log and trace analyzer. To install IBM Agent Controller , follow these steps: 1. Log in as root. 2. Insert the Tivoli Asset Management for IT 7.1 Middleware for zLinux DVD in your DVD-ROM drive. 3. Change directory to linux390/Rational-AgentController_7.0.3/linux_s390 on the DVD. 4. Type ./setup.bin to start the setup wizard. The Welcome panel is displayed. 5. Click Next. The license agreement panel is displayed. 6. Accept the license agreement, and then click Next. 7. Enter the install directory path, and then click Next. 8. Select V6.0 or later for the WebSphere version, and then click Next. 9. Choose Any computer for the access list, and then click Next. The security panel is displayed. 10. Click Next. 11. Enter the following user IDs and then click Next. v wasadmin v root v maximo 12. From the summary panel, click Install. 13. Click Finish. when the process is complete.
Chapter 4. Tivoli Asset Management for IT middleware installation

59

Installing and configuring Virtual Member Manager on WebSphere on zLinux

Use this information to successfully install and configure Virtual Member Manager on WebSphere on zLinux. Virtual Member Manager (VMM) provides you with the ability to access and maintain user data in multiple repositories, and federate that data into a single virtual repository. Refer to Manually configuring Virtual Member Manager on WebSphere on page 108 for information on adding an IBM Tivoli Directory Server repository to VMM.

WebSphere management
IBM provides comprehensive information on running and administering WebSphere at this URL:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

Starting the WebSphere Application Server

An application server named MXServer was created during installation. To start the MXServer application , complete the following steps: 1. Start the Deployment Manager: UNIX <WAS_HOME>/AppServer/profiles/ctgDmgr01/bin/startManager.sh Windows <WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat 2. Start the Node: UNIX <WAS_HOME>r/profiles/ctgAppSrv01/bin/startNode.sh Windows <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat 3. Start the web server: UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh webserver1 -username <username> -password <password> Windows <WAS_HOME>profiles\ctgAppSrv01\bin\startServer.bat webserver1 -username <username> -password <password> 4. Start the App Server : UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer -username <username> -password <password> Windows <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.bat MXServer -username <username> -password <password> Alternatively you can start MXServer from the WebSphere administrative console: 1. To start the administrative console, open a browser window and enter the following URL:
http://<machine_name>:9060/ibm/console

60

Installation Guide for IBM WebSphere Application Server:

Where <machine_name> is the host name of the WebSphere Application Server and 9060 is the default port number for the Administrative Console. 2. Enter an administrative user ID and password to login, if one is required. 3. From the administrative console navigation pane, click Servers Application Servers. 4. Select the check box next to MXServer, the name of the WebSphere Application Server. 5. Click Start. Notice that the icon in the Status column changes to running 6. To stop the WebSphere Application Server, click Stop. Notice that the icon in the Status column changes to stopped. Before you start the Administrative console, verify that these server processes are running.
Table 15. Server HTTP Server Go To Windows <HTTP_SERVER_HOME>\bin\apache -k start \<HTTP_SERVER_HOME>\bin\apache -k stop UNIX <HTTP_SERVER_HOME>/bin/apachectl start <HTTP_SERVER_HOME>/bin/apachectl stop Deployment Manager Windows <WAS_HOME> \profiles\ctgDmgr01\bin\startManager.bat <WAS_HOME> \profiles\ctgDmgr01\bin\stopManager.bat UNIX <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh <WAS_HOME>/profiles/ctgDmgr01/bin/stopManager.sh Node Agent Windows <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode.bat UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh <WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode.sh ITDS Instance Windows 1. Click Start, and select Run. 2. Type services.msc, and click OK. 3. Select IBM Tivoli Directory Server Instance V6.1 - idsccmdb, and click Start the service. UNIX Directory Server Database /ldap/V6.1/sbin/ibmslapd -I idsccmdb

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 su - idsccmdb -c db2start

Chapter 4. Tivoli Asset Management for IT middleware installation

61

To start the Administrative Console, , complete the following steps: 1. Open a browser window, and enter the following URL:
http://<machine_name>:9060/ibm/console

Where <machine_name> is the host name of the WebSphere Application Server and 9060 is the default port number for the Administrative Console. 2. Enter a user ID to login. Until you enable security, you can login with any user ID. The user ID does not have to be a valid system user.

Securing the WebSphere Administrative Console

You can secure the Administrative Console so that only authenticated users can use it. VMM must have been configured on the WebSphere server prior to securing the console. Once you have enabled VMM for WebSphere security, you perform 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 want to access the console, you can determine their level of access by assigning roles. The roles determine the administrative actions that a user can perform. After enabling security, a user must enter a valid administrator user ID and password to access the console. You can use the Administrative Group Roles page to give groups specific authority to administer application servers through the administrative console. Simply click Security Secure administration, applications, and infrastructure Administrative Group Roles to view the available administrative group roles.
Table 16. Admin Role Administrator Operator Configurator Monitor deployer adminsecuritymanager Description Has operator permissions, configurator permissions, and the permission that is required to access sensitive data. Has monitor permissions and can change the run-time state. For example, the operator can start or stop services. Has monitor permissions and can change the application server configuration. Has the least permissions. This role primarily confines the user to viewing the application server configuration and current state. Users granted this role can perform both configuration actions and runtime operations on applications. Fine-grained administrative security is available using wsadmin only. However, you can assign users and groups to the adminsecuritymanager role on the cell level through wsadmin scripts and the administrative console. Using the adminsecuritymanager role, you can assign users and groups to the administrative user roles and administrative group roles. However, an administrator cannot assign users and groups to the administrative user roles and administrative group roles including the adminsecuritymanager role. Has administrator privileges for managing users and groups from within the administrative console only.

iscadmins

Note: To manage users and groups, click Users and Groups in the console navigation tree and then click either Manage Users or Manage Groups.

62

Installation Guide for IBM WebSphere Application Server:

Complete the following steps to map users and groups to security roles: 1. 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 or groups to a role authorizes those users or groups to access applications defined by the role. Users and groups are associated with roles defined in an application when the application is installed or configured. Use the Search pattern field to display users in the Available list. Click >> to add users from the Available list to the Selected list. 4. Restart all the application servers.

Configuring the WebSphere Application Server to run as a Windows service

To configure the WebSphere Application Server to run as a Windows service, complete the following steps: 1. Start the WebSphere Administrative Console by opening a browser window and entering the following URL
http://<machine_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: serverName name of Maximo application server, MXServer profilePath the profile directory of the server, for example,
C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01

wasHome home folder for MXServer, for example,

C:\Program Files\IBM\WebSphere\AppServer\profiles

logRoot folder location of MXServer log file, for example,

C:\Program Files\IBM\WebSphere\AppServer\logs\ manageprofiles\ctgAppSrv01

logFile log file name for MXServer (startServer.log) restart restarts the existing service automatically if the service fails when set to true. 9. Enter the WASService command using the following syntax:

Chapter 4. Tivoli Asset Management for IT middleware installation

63

WASService add MXServer serverName MXServer profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ ctgAppSrv01wasHome <D:>\IBM\WebSphere\AppServer logRoot C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01 logFile C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01\startServer.log restart true

10. Press <Enter> after you type the WASService command, and you will see a confirmation message. 11. Open a Services window and double-click MXServer. Then perform the following 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 service

A node agent is a server running on every host computer in the deployed network. It performs administrative functions. To configure the WebSphere node agent to run as a Windows service, complete the following steps: 1. Start the WebSphere 6.1 Administrative Console by opening a browser window and entering the following URL:
http://<machine_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: serverName name of node agent, for example, nodeAgent profilePath the profile directory of the server, for example,
C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01

wasHome home folder for MXServer, for example,

C:\Program Files\IBM\WebSphere\AppServer\profiles

logRoot folder location of node agent log file, for example,

C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01

logFile log file name for node agent (startServer.log)

64

Installation Guide for IBM WebSphere Application Server:

restart restarts the existing service automatically if the service fails when set to true. 9. Enter the WASService command using the following syntax:
WASService add NodeAgent serverName nodeagent profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 wasHome <D:>\IBM\WebSphere\AppServer logRoot <D:>\IBM\WebSphere\AppServer\logs\nodeagent logFile <D:>\IBM\WebSphere\AppServer\logs\nodeagent\ startServer.log restart true

10. Press <Enter> after you type the WASService command, and you will see a confirmation message. 11. Open a Services window and double-click the Node Agent service, for example, 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.

WebSphere Portal Server overview

An existing WebSphere Portal Server system can be configured to work with your Tivoli Asset Management for IT deployment after it has been successfully installed. You can access Tivoli Asset Management for IT applications through the WebSphere Portal Server interface transparently, centralizing Tivoli Asset Management for IT application access alongside other service-oriented applications used by your organization. WebSphere Portal Server needs to be hosted on a system other than the system hosting the Tivoli Asset Management for IT J2EE server. WebSphere Portal Server must be configured to use a version of WebSphere that it supports.

Tivoli Asset Management for IT deployed on WebSphere Portal Server

Tivoli Asset Management for IT deployed on WebSphere Portal Server After Tivoli Asset Management for IT has been completely deployed, the user interface for any Tivoli Asset Management for IT application can be accessed through a portlet hosted on an existing WebSphere Portal Server instance. The following EAR files are deployed by the Tivoli Asset Management for IT installation and the Process Solution installation programs and are candidates for being modified, rebuilt, and redeployed:
Table 17. Tivoli Asset Management for IT EAR and WAR files EAR File maximo.ear Description This EAR file contains the maximo.war file which includesTivoli Asset Management for IT base tasks. This EAR file contains the maximohelp.war file which is for Tivoli Asset Management for IT Help Location <TAMIT_HOME>\maximo\ deployment\default

maximohelp.ear

<TAMIT_HOME>\maximo\ deployment\default

Chapter 4. Tivoli Asset Management for IT middleware installation

65

To create a page with a portlet for a Tivoli Asset Management for IT application you wish to access through WebSphere Portal Server, ensure you have a working and active Tivoli Asset Management for IT deployment, and then complete the following steps: 1. From the Tivoli Asset Management for IT administrative workstation, open a Web browser and access the WebSphere Portal Server Administration tool.
http://<hostname>:<portnumber>/wps/portal

2. Log in as the WebSphere Portal Server administrator. 3. From the WebSphere Portal Server welcome page, click Administration, found at the bottom of the user interface. 4. From the WebSphere Portal Administration page, click Web Modules, found under the Portlet Management heading of the navigation pane. 5. From the Manage Web Modules page, you see a table listing all of the web modules that have been installed on the server. Click Install to install a new module. 6. From the Select War File page, using the Browse button, locate the Tivoli Asset Management for IT WAR file you intend to deploy. War files will be located on the Tivoli Asset Management for IT Administrative system. Once you have located the intended War file, click Next. In this example, we are deploying the War file maximo.war. 7. From the War file content summary page, review the War file contents, and then click Finish. If the deployment is successful, you will be returned to the Manage Web Modules page. A message will be displayed confirming that the War file was correctly deployed. For each War file you deploy, you will need to edit its maximointegration .properties file. This file is found in the deployment directory created after the deployment of each War, under the WEB-INF directory. 8. Open the appropriate maximointegration.properties file in a text editor, and edit the following properties: maximo_host_name Ensure this value is the same as the host name used to access the Maximo servlet on WebSphere Application Server. maximo_port Ensure this value is the same as the port used to access the Maximo servlet on WebSphere Application Server. maximo_url_protocol This value defaults to http, but you should change it to https in order to access a secure environment. The process of editing the maximointegration.properties file will have to be repeated for every War file you deploy in WebSphere Portal Server. The next step is to create a new page and place a portlet for the Tivoli Asset Management 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.

66

Installation Guide for IBM WebSphere Application Server:

13. Enter Tivoli Asset Management for IT 7.1 in the Title field of the Page Properties window, and then click OK. A new label titled Tivoli Asset Management for IT 7.1 will be created and displayed in the Pages in Context Root table. 14. From the Pages in Context Root table of the Manage Pages page, click Tivoli Asset Management for IT 7.1. 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, and then click OK. We are creating a page for the Tivoli Asset Management for IT Change application. 17. Click the Edit Page Layout icon located to the right of the new entry in the Pages in Tivoli Asset Management for IT 7.1 table. 18. From the Edit Layout page, click Add Porlets. 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. You can now launch the portlet from the WebSphere Portal Server Launch menu.

Chapter 4. Tivoli Asset Management for IT middleware installation

67

68

Installation Guide for IBM WebSphere Application Server:

Chapter 5. Tivoli Asset Management for IT installation program overview

The Tivoli Asset Management for IT installation program provides an interface for installing and deploying Tivoli Asset Management for IT. The Tivoli Asset Management for IT installation program records choices you make about your Tivoli Asset Management for IT deployment and configuration parameters associated with those choices, and then installs and deploys Tivoli Asset Management for IT based upon the information you entered. There are two installation paths available to you when installing Tivoli Asset Management for IT. Simple A simple deployment consists of installing all middleware on one system. You will not have the option of using existing middleware within your organization with Tivoli Asset Management for IT. All middleware used in conjunction with Tivoli Asset Management for IT must have been installed on the system using the Tivoli middleware installer using default values. Tivoli Asset Management for IT will be installed using default values provided by the Tivoli middleware and Tivoli Asset Management for IT installation programs. For a list of values being set when using this option, refer to Tivoli Asset Management for IT simple install path values on page 70. If you intend to override default values used by the simple deployment path, you will have to use the custom deployment path instead. Custom A custom deployment typically involves deploying Tivoli Asset Management for IT across several systems, some of which probably already host middleware products that you wish to use with your Tivoli Asset Management for IT deployment. Deploying through the custom installation path also allows you to modify default installation values. This deployment option does not require you to spread the Tivoli Asset Management for IT deployment across several systems. You can enter the name of the local host as the destination for all Tivoli Asset Management for IT components that are to be installed using the Tivoli middleware installer and the Tivoli Asset Management for IT installation program. The Tivoli Asset Management for IT installation program can automate the configuration of middleware for use with Tivoli Asset Management for IT. If you choose not to have the Tivoli Asset Management for IT installation program automatically configure middleware, configure that piece of middleware manually prior to the installation of Tivoli Asset Management for IT. While you can deploy Tivoli Asset Management for IT in a distributed environment consisting of predominately UNIX systems, the Tivoli Asset Management for IT installation program must be run from a Windows system. Important: When entering LDAP values for Tivoli Asset Management for IT installation panel fields, entries in LDIF files, or values you enter directly into a directory instance using the directory server tools, be aware of the product-specific syntax rules for using special characters in an LDAP string. In most cases, in order
Copyright IBM Corp. 2007, 2008

69

to make them readable by the directory server, special characters must be preceded by an escape character. Failing to escape special characters contained in an LDAP string used with Tivoli Asset Management for IT result in Tivoli Asset Management for IT errors. Many directory server products consider a blank space as a special character that is part of the LDAP string. Therefore, if you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you will encounter Tivoli Asset Management for IT errors that are difficult to troubleshoot. Refer to the product documentation for your directory server for more information on special characters in LDAP strings. Information that you input into the Tivoli Asset Management for IT installation program is stored in the maximo.properties file and the Maximo database. These values are populated into the panel fields of the Tivoli Asset Management for IT installation program on subsequent uses of the program . Therefore, if you cancel the installation program after entering values across several installation panels, the installation program will recall the values the next time you start up the Tivoli Asset Management for IT installation program (except for the Tivoli Asset Management for IT install directory and the shortcut option chosen). You can restore the default values in the Tivoli Asset Management for IT installation program by deleting <TAMIT_HOME>/maximo/applications/maximo/ properties/maximo.properties.

Tivoli Asset Management for IT simple install path values

If you elect to install Tivoli Asset Management for IT using the simple install path, the following values are set. You will be able to provide values where indicated.
Table 18. Tivoli Asset Management for IT Simple Install Path Values Category Deployment Option Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Field Deployment Database Type Host name Port Database Name Instance User ID Automate Database Configuration Remote Access User ID yes Yes 50005 maxdb71 ctginst1 Yes Value simple DB2 Yes Provided by User?

70

Installation Guide for IBM WebSphere Application Server:

Table 18. Tivoli Asset Management for IT Simple Install Path Values (continued) Category Database Configuration Field Database Install Directory Value Windows C:\Program Files\IBM\ SQLLIB UNIX Database Configuration Instance Administrator User ID Windows Service User ID /opt/IBM/ db2/V9.1 Yes Provided by User?

Windows db2admin UNIX ctginst1

Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration WebSphere Connectivity WebSphere Connectivity WebSphere Configuration

db2admin

Data tablespace name maxdata Data tablespace size medium

Temporary tablespace maxtemp name Temporary tablespace 1000 size Host name SOAP Port WebSphere server home directory 8879 Yes

Windows C:\Program Files\IBM\ WebSphere\ AppServer Linux /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer

AIX

Sun Solaris /opt/IBM/ WebSphere/ AppServer WebSphere Configuration WebSphere Configuration WebSphere Configuration WebSphere Configuration User name Profile name wasadmin ctgDmgr01 Yes

Automate WebSphere yes Configuration Remote Access User ID Yes

Chapter 5. Tivoli Asset Management for IT installation program overview

71

Table 18. Tivoli Asset Management for IT Simple Install Path Values (continued) Category WebSphere Application Server Configuration WebSphere Application Server Configuration WebSphere Application Server Configuration WebSphere Application Server Configuration WebSphere Application Server Configuration Integration Adapter JMS Configuration Integration Adapter JMS Configuration Security Configuration Security Configuration Maximo Configuration Configuration Step Field Web server port Value 80 Provided by User?

Web server name

webserver1

Node name

ctgNode01

Cluster name

MAXIMOCLUSTER

Application server

MXServer This value cannot be changed. meajmsds

JMS DataSource name

Persist JMS messages no Use Default Schema Create Users automatically Install directory Run Configuration Now yes yes C:\IBM\SMP yes Yes

Installing Tivoli Asset Management for IT

This procedure explains how to use the Tivoli Asset Management for IT installation program to install Tivoli Asset Management for IT. In addition to configuring new instances of Tivoli Asset Management for IT middleware products installed by the Tivoli middleware installer, the Tivoli Asset Management for IT installation program can configure existing instances of prerequisite products, including those from other vendors, that you want to use with Tivoli Asset Management for IT. The instructions provided are for a multiple machine installation using default values and assume that you choose to have the Tivoli Asset Management for IT installation program automatically configure middleware across multiple machines to work with Tivoli Asset Management for IT. If you do not allow the Tivoli Asset Management for IT installation program to configure middleware automatically, it still performs programmatic checks to verify that the documented manual steps were performed properly. If any errors are encountered, a dialog box detailing the error appear. You will not be permitted to continue in the Tivoli Asset Management for IT installation task until the errors are resolved.

72

Installation Guide for IBM WebSphere Application Server:

The Tivoli Asset Management for IT installation program can only be run from a Windows-based system. Before you begin, ensure you have addressed the following prerequisite conditions: v For Linux systems, ensure that the command hostname -f returns a fully qualified host name. If it does not, consult the appropriate documentation for your operating system to ensure that the hostname command returns a fully qualified host name. v The middleware environment is installed and running properly. v If you plan to take advantage of the Tivoli Asset Management for IT installation program feature that automates the configuration of Tivoli Asset Management for IT middleware, enable a Remote Execution and Access (RXA) service for each system on which you intend to install Tivoli Asset Management for IT middleware. RXA requires that the target system enable at least one of the protocols supported by RXA, which includes rsh, rexec, SSH, and Windows SMB. Before you start the Tivoli Asset Management for IT installation program, ensure that one of these protocols is running and accepting remote logins using a user name and password configured on the target machine. If the remote system is a Windows machine, configure RXA to work over SMB. Default installations of AIX systems might not include a suitable protocol and must have RXA compatible protocols enabled. v If you are using DB2 with Tivoli Asset Management for IT, and you want to use the fully automated database configuration capabilities of the Tivoli Asset Management for IT installation program, ensure that the following conditions are met: For DB2 UNIX installations, create the instance user on the DB2 server before starting the Tivoli Asset Management for IT installation program. For example if you plan to create the Maximo database in a DB2 instance (ctginst1 is recommended), create a user (including the home directory for the user) on the UNIX DB2 server prior to starting the install. The user ID specified as the Instance administrator user ID that you enter on the DB2 Administration panel of the Tivoli Asset Management for IT installation program must have DB2 administration authority, which is referred to as SYSADM authority in the DB2 product documentation. For more information about creating this user, refer to the DB2 product documentation. The user ID specified on the Remote Access Authorization panel of the Tivoli Asset Management for IT installation program must have DB2 administration authority. It is used to create the DB2 instance, database, and schema. It must have SYSADM authority, as defined by DB2. This requires the ID to be a member of the group defined by the sysadm_group configuration parameter for the DB2 instance you plan to use. For example, on Windows, the user must belong to the DB2ADMNS group. For more information about creating this user, refer to the DB2 product documentation. For UNIX systems, the fenced user must be db2fenc1. For UNIX systems, add root to the DB2GRP1 group prior to starting the Tivoli Asset Management for IT installation program. v For all DB2 installations, you might encounter ever increasing system memory usage linked with DB2. If you experience this behavior, set the following DB2 property and then restart the DB2 server:
db2 update dbm cfg using KEEPFENCED NO

v If you are using Oracle with Tivoli Asset Management for IT, ensure that the following conditions are met:
Chapter 5. Tivoli Asset Management for IT installation program overview

73

 Ensure the Oracle 10gR2 patch 3 is installed. v If you are using MS SQL Server 2005 with Tivoli Asset Management for IT, ensure that the following conditions are met: Ensure the MS SQL Server 2005 service pack 2 is installed. Tivoli Asset Management for IT uses port 1433 when configured with SQL Server. By default, this port is not enabled. Enable this port. Refer to http://msdn.microsoft.com/en-us/library/ms177440.aspx for instructions. v If you are using Microsoft Active Directory to secure WebSphere, ensure the users and groups listed in Manually configuring Microsoft Active Directory on page 102 have been manually created in the Microsoft Active Directory instance. v For IBM WebSphere Network Deployment, ensure that the following task is complete: Ensure that the Cell and all related nodes are actively running. Avoid using localhost for host name values in the install program. Specify the actual fully qualified host name of the system for all host name values. To install Tivoli Asset Management for IT, follow these steps: 1. Login as Administrator on the Tivoli Asset Management for IT administrative system. 2. Launch the Tivoli Asset Management for IT installation program from the launchpad. a. Start the launchpad: v On the DVD titled Tivoli Asset Management for IT V7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.exe. b. In the launchpad navigation pane, click Install the Product. c. Click Tivoli Asset Management for IT. 3. Select a language for the installation and click OK. 4. From the Introduction panel, click Next. 5. From the Import Middleware Configuration Information panel, specify that you want to use field values you input into the Tivoli middleware installer as default values for those same fields in the Tivoli Asset Management for IT installation program. Import Middleware Configuration Information Select this check box if you want to allow the Tivoli Asset Management for IT installation program to reuse values entered for DB2 in the Tivoli middleware installer. Note that if you select this feature while installing Tivoli Asset Management for IT by way of RXA, the Workspace Location that you specify cannot be located on a networked drive of the remote system. It must reside locally on the remote system. The middleware default information will not be used if you select the Simple deployment path. Host name Enter the fully qualified host name of the system where the Tivoli middleware installer was run. User ID Enter the User ID that was used to run the Tivoli middleware installer.

74

Installation Guide for IBM WebSphere Application Server:

Password Enter the password of the User ID that was used to run the Tivoli middleware installer. Workspace Location Enter the location of the topology file that contains the values entered for the Tivoli middleware installer. This file is found in the workspace that was defined during the Tivoli Asset Management for IT middleware installation task. For example, C:\ibm\tivoli\mwi\ workspace. 6. From the Choose Deployment panel, select the Custom deployment topology, and then click Next. Simple Select simple if you want to deploy all Tivoli Asset Management for IT components on a single system. This deployment option is typically only used for demonstration, proof-of-concept, or training purposes. Custom Select custom if you want to deploy Tivoli Asset Management for IT components across several systems. This deployment option is typically used in a production environment. 7. From the Choose Install Folder panel, specify the directory you use to install Tivoli Asset Management for IT, and then click Next. Where Would You Like to Install? Enter the path to install Tivoli Asset Management for IT. By default, this value is C:\IBM\SMP. The path you specify must not contain spaces. 8. From the Maximo Database Type panel, select the product that you use for the Maximo database, and then click Next. DB2 Select this choice to use IBM DB2 UDB as the Maximo database.

Oracle Select this choice to use Oracle as the Maximo database. SQL Server Select this choice to use MS SQL Server 2005 as the Maximo database. Each database will have its own unique set of configurable parameters and values. 9. From the Maximo Database panel, enter configuration information about the database, and then click Next. DB2 Host name Enter the host name of the machine hosting DB2. The host name must be fully qualified. Port Enter the port being used by DB2 instance. The default is 50005 Database name Enter the name of the database to use with Maximo. The default database name is maxdb71. The database is created if it does not exist.

Chapter 5. Tivoli Asset Management for IT installation program overview

75

Instance Enter the name of the database instance to be used with Maximo. The default instance name is ctginst1. This instance is created if it does not exist, however, the user and its associated home directory must exist on the DB2 server. Database user ID Enter the user ID used for 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 instance administrator user ID. Database password Enter the password for the user ID used to access DB2. Oracle Host name Enter the host name of the machine hosting Oracle. The host name must be fully qualified. Port Enter the port being used by Oracle. The default is 1521 Instance Enter the name of the database instance to be used with Maximo. The default instance name is ctginst1. Database user ID Enter the user ID used for Maximo to access Oracle. Default for all platforms is maximo. This user ID is created if it does not exist. Database password Enter the password for the user ID used to access Oracle. SQL Server Host name Enter the host name of the machine hosting SQL Server. The host name must be fully qualified. Port Enter the port being used by SQL Server. The default is 1433 Database Name Enter the name of the database to use with Maximo. The default database name is maxdb71. Database user ID Enter the user ID used to access SQL Server. Default for all platforms is maximo.

76

Installation Guide for IBM WebSphere Application Server:

This user ID is created if it does not exist. Database password Enter the password for the user ID used to access SQL Server. 10. From the Automate Database Configuration panel, select Automate database configuration, and then click Next. This step allows the Tivoli Asset Management for IT installation program to configure the database automatically for use by Tivoli Asset Management for IT. Examples of automated tasks include creating tablespaces, creating database tables, creating database schemas, creating users, and so on. If you choose not to have the Tivoli Asset Management for IT installation program automatically configure the database, you must configure a database manually prior to the installation of Tivoli Asset Management for IT. If you do not elect to automate the database configuration and you have not manually configured the database prior to selecting Do not automate database configuration from within the Tivoli Asset Management for IT installation program, the installation will verify that you have not completed these pre-install tasks and you will receive errors. Complete these manual tasks prior to restarting the Tivoli Asset Management for IT installation program. 11. From the Remote Access Authorization panel, enter authorization information for the automatic database configuration feature, and then click Next. User ID Enter a valid user ID that gives the Tivoli Asset Management for IT installation program access to the system that is hosting the database to be used with Tivoli Asset Management for IT. This user ID must have administrative rights on the machine you are accessing. If youre using DB2 for the Maximo database, this user must be a member of the DB2ADMNS group (Windows) or the db2grp1 group (UNIX). Password Enter the password for the user ID. Refer to Enabling remote configuration on page 21 for details about how to ensure successful remote access between the Tivoli Asset Management for IT installation program and the remote server. 12. From the Database Administration panel, enter configuration information about the database, and then click Next. DB2 Installation directory Enter the directory where DB2 is installed. Windows On Windows, this value might be C:\Program Files\IBM\SQLLIB Linux On Linux, this value might be /opt/IBM/db2/V9.1 AIX On AIX, this value might be /opt/IBM/db2/V9.1

Instance administrator user ID Enter the administrator user ID for the DB2 instance. Windows On Windows, this value might be db2admin.
Chapter 5. Tivoli Asset Management for IT installation program overview

77

Linux On Linux, this value might be ctginst1. AIX: On AIX, this value might be ctginst1

This user ID cannot be the same one as is as the database user ID. Instance administrator password Enter the password for the DB2 instance administrator user ID. Windows service user ID Enter the user ID used to start the DB2 service on Windows. The default is db2admin. This user ID must have administrative authority on the system. Windows service password Enter the password for the user ID used to start the DB2 service on Windows. Oracle Installation directory Enter the directory where Oracle is installed. Windows On Windows, this value might be C:\oracle\product\10.2.0\oradata Linux On Linux, this value might be /opt/app/oracle/ product/10.2.0/oradata AIX On AIX, this value might be /opt/app/oracle/ product/10.2.0/oradata

Sun Solaris On Sun Solaris, this value might be /opt/app/oracle/product/10.2.0/oradata Administrator User ID Enter the administrator user ID for Oracle. For all platforms, the default is sys. Administrator Password Enter the password for the administrator user ID for Oracle. Oracle Software Owner ID Enter the user ID of the user that was used to install Oracle. For all platforms, the default is oracle Oracle Owner Password Enter the password for the user ID of the user that was used to install Oracle. SQL Server SQL Server administrator Enter the administrator user ID for MS SQL Server. Default is sa. SQL Server administrator password Enter the password for the administrator user ID for MS SQL Server.

78

Installation Guide for IBM WebSphere Application Server:

Data file name Enter the name of the MS SQL Server data file. Default value is maxdb71_dat Data file initial size Select the initial size of the MS SQL Server data file. Default is set to Medium (1000 MB) Log file name Enter the name for the MS SQL Server log file. Default is maxdb71_log 13. From the Database Tablespace panel, enter information about the tablespace of the database, and then click Next. DB2 Data tablespace name Enter the name of the tablespace that will be created in DB2 for Maximo. For all platforms, the default is MAXDATA. If the tablespace does not exist, it is created. Data tablespace size Enter a size for the tablespace by selecting one of the following values: v small (3000Mb) Select this size if supporting between 1-20 users v medium (5000Mb) Select this size if supporting between 20-100 users v large (8000Mb) Select this size if supporting 100+ users Tablespace size is measured in Mb. Temporary tablespace name Enter the name for the temporary tablespace to be created for DB2. Temporary tablespaces hold data during sorting or collating actions. For all platforms, the default is MAXTEMP. If the tablespace does not exist, it is created. Temporary tablespace size Enter a size for the temporary tablespace. Temporary tablespace size is measured in Mb. This value must be set to 1000Mb. Oracle Instance Location Enter the path where the database instance is loaded. Windows On Windows, this value might be C:\oracle\product\10.2.0\oradata\dbs
Chapter 5. Tivoli Asset Management for IT installation program overview

79

Linux On Linux, this value might be /opt/app/oracle/ product/10.2.0/oradata AIX On AIX, this value might be /opt/app/oracle/ product/10.2.0/oradata

Sun Solaris On Sun Solaris, this value might be /opt/app/oracle/product/10.2.0/oradata Tablespace name Enter the name of the tablespace that is created in Oracle for Maximo. For all platforms, the default is maxdata Tablespace Size Enter a size for the tablespace by selecting one of the following values: v small (500Mb) Select this size if supporting between 1-2 users v medium (1000Mb) Select this size if supporting between 20-100 users v large (5000Mb) Select this size if supporting 100+ users Tablespace size is measured in Mb. Temporary tablespace name Enter the name for the temporary tablespace to be created for Oracle. Temporary tablespaces hold data during sorting or collating actions. For all platforms, the default is maxtemp Temporary tablespace size Enter a size for the temporary tablespace, which will be used for sort operations. Temporary tablespace size is measured in Mb. For all platforms, the default is 100Mb. The Tivoli Asset Management for IT installation program now connects to the database server and validate all of the information you have entered. 14. From the Maximo Application Server Type panel, select IBM WebSphere Application Server. 15. From the WebSphere Connectivity panel, enter host information about the WebSphere server, and then click Next. Host name Enter the fully qualified host name of the system hosting WebSphere. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere system. The default value for this field is 8879.

80

Installation Guide for IBM WebSphere Application Server:

16. From the WebSphere Remote Access Authorization panel, enter authorization information for WebSphere configuration, and then click Next. Operating system user ID Enter a valid user ID that gives the Tivoli Asset Management for IT installation program access to the system that is hosting WebSphere. This user ID must have administrative rights on the machine you are accessing. Operating system password Enter the password for the system user ID. 17. From the Automate WebSphere Configuration panel, select Automate WebSphere configuration, and then click Next. This allows the Tivoli Asset Management for IT installation program to configure WebSphere automatically for use by Tivoli Asset Management for IT. If you choose not to have the Tivoli Asset Management for IT installation program automatically configure WebSphere, you will have to configure WebSphere manually prior to the installation of Tivoli Asset Management for IT. Configuration tasks include creating a profile, running WebSphere as a Windows service, copying the WebSphere keystore file from the machine where WebSphere is installed to the administrative workstation, setting up JMS queues, and so on. 18. From the WebSphere Deployment Manager configuration panel, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere is installed on the host system. Windows On Windows, this value might be C:\Program Files\IBM\WebSphere\AppServer Linux On Linux, this value might be /opt/IBM/WebSphere/ AppServer AIX On AIX, this value might be /usr/IBM/WebSphere/ AppServer

Sun Solaris On Sun Solaris, this value might be /opt/IBM/WebSphere/ AppServer User ID Enter the administrative user ID used to access the WebSphere server. Default for all platforms is wasadmin. Password Enter the password for the administrative user ID used to access the WebSphere server. Profile name Enter the name of the WebSphere 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 port Enter the Web server port used by WebSphere.
Chapter 5. Tivoli Asset Management for IT installation program overview

81

Default for all platforms is 80 Web server name Enter the name of the Web server. Default for all platforms is webserver1 Node name Enter the name of the WebSphere node containing the application server. Default for all platforms is ctgNode01. Cluster name Enter the name of the WebSphere cluster containing the application server. Default for all platforms is MAXIMOCLUSTER. The cluster name is optional. The cluster and application server will be created if they do not exist. 20. From the Security panel, indicate whether application server security should be enabled automatically, and then click Next. 21. From the Integration Adapter JMS Configuration panel, enter the following information, and then click Next. JMS DataSource name A JMS server requires a DB2 data repository to be configured to maintain messages. Enter the name of the database to be used by JMS. Default is intjmsds. Select whether the JMS datastore should be persisted. Persist JMS messages Select this option of you want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages. Do not persist JMS messages Select this option if you do not want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages automatically. A database will not be used to persist messages. If you later decide that you would like to persist JMS messages, you will have to configure the JMS implementation manually. The next several steps of this Tivoli Asset Management for IT installation procedure assume you are allowing the Tivoli Asset Management for IT installation program to configure the JMS implementation to persist messages. 22. From the DB2 Database Server Configuration panel, enter the following information, and then click Next. Note: The JMS DataStore can only be created as a DB2 database. Host name Enter the fully qualified host name of the server hosting the JMS datastore. Port Enter the port used to access the database server. Default for all platforms is 50005.

82

Installation Guide for IBM WebSphere Application Server:

Database name Enter the name of the database serving as the JMS datastore. Default for all platforms is maxsibdb. User ID Enter the user ID used to access the database server. Default for all platforms is the database user ID you entered when you selected your database type. If the user does not exist, it will be created for you. Password Enter the password for the User ID used to access the database server. 23. From the DB2 Database Server Remote Access Authorization panel, enter authorization information for the automatic configuration feature, and then click Next. User ID Enter a valid user ID that will allow the Tivoli Asset Management for IT installation program to access the system that is hosting the JMS database. This user ID should have administrative rights on the machine you are accessing. For Windows, this user must be a member of the DB2ADMNS group. For Unix, this user must be a member of the db2grp1 group Password Enter the password for the user ID. 24. From the DB2 Database Instance Configuration panel, enter the following information, and then click Next. Installation directory Enter the installation directory for the DB2 server that is hosting the JMS database that contains the instance to be used with WebSphere. Windows On Windows, this value might be C:\Program Files\IBM\SQLLIB Linux On Linux, this value might be /opt/IBM/db2/V9.1 Instance Enter the JMS database instance to be used with WebSphere. For all platforms, the default is ctginst1 Instance administrator user ID Enter the administrators user ID for the JMS database instance. Windows On Windows, this value might be db2admin. Linux On UNIX, this value might be ctginst1. Instance administrator password Enter the password for the JMS database instance administrators user ID. 25. From the Maximo panel, enter the following configuration information, and then click Next.

Chapter 5. Tivoli Asset Management for IT installation program overview

83

Installation directory Select the folder where Maximo will be installed. C:\IBM\maximo is the default value. The path you specify must not contain spaces. SMTP server Enter the mail server configured to work with Tivoli Asset Management for IT. This server will be used to send workflow and process notifications. This field is optional. Workflow administrator e-mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Workflow Administrator. This address will be used for workflow notifications. This field is optional. Administrator e-mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Administrator This field is optional. If you choose to not configure optional properties at this time, you can configure them in the Tivoli Asset Management for IT user interface using the System Properties application. The relevant properties are: v mail.smtp.host v mxe.workflow.admin v mxe.adminEmail 26. From the Run Configuration Step panel, select when you would like to configure Tivoli Asset Management for IT, and then click Next. Run the configuration step now Tivoli Asset Management for IT will be configured when you select this option and press Next. Do not run the configuration step now You will have to configure Tivoli Asset Management for IT after you have completed the Tivoli Asset Management for IT installation task. The Tivoli Asset Management for IT installation program is used to complete three tasks: gathering information about your Tivoli Asset Management for IT deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting Do not run the configuration steps now, you can instruct the Tivoli Asset Management for IT installation program to gather your configuration information and copy Tivoli Asset Management for IT files to your local system now, and then allow you to run the configuration step at a later date. The configuration values that you enter are stored in the <Maximo_Home>\applications\maximo\properties\ maximo.properties file. You can execute the configuration steps outside of the Tivoli Asset Management for IT installation program by using the taskrunner utility, located in the <TAMIT_HOME>\scripts directory. Simply run the taskrunner utility from the command line, and it will use the configuration values stored in the maximo.properties file to configure Tivoli Asset Management for IT.

84

Installation Guide for IBM WebSphere Application Server:

<TAMIT_HOME>\scripts\taskrunner

If there is an installation failure, the taskrunner utility can be run again after the error conditions have been rectified. The taskrunner utility will resume the install at the point where the last successfully completed task was recorded in the previous attempt. 27. From the Choose Shortcut Folder panel, select the type of shortcut you would like to arrange for Tivoli Asset Management for IT, and then click Next. In a new Program Group Select this option and enter the name of a new program group if you would like to create Tivoli Asset Management for IT shortcuts in a new program group. In an existing Program Group Select this option and choose the name of an existing program group to store Tivoli Asset Management for IT shortcuts. In the Start Menu Select this option to create shortcuts for Tivoli Asset Management for IT in the Start menu. In order to use the Start Menu shortcut in conjunction with Internet Explorer, ensure that you have added the Tivoli Asset Management for IT URL to the trusted sites Web content zone and disable the option of requiring server verification for all sites in the zone. On the Desktop Select this option to create shortcuts for Tivoli Asset Management for IT on the desktop. In the Quick Launch Bar Do not select this option. Selecting this option does not create a shortcut in the Quick Launch bar. Other Select this option and use the Choose... button to select another location to create Tivoli Asset Management for IT shortcuts. Dont create icons Select this option if you do not want any Tivoli Asset Management for IT shortcuts created. Create Icons for All Users Select this option if you would like Tivoli Asset Management for IT desktop icons to appear on the desktop for all system users. 28. From the Input Summary panel, review the information you have provided to the Tivoli Asset Management for IT installation program, and then click Next. Use the Previous button to return to previous panels to change anything. 29. From the Pre-Installation Summary panel, review the installation information presented, and then click Install. The installation now begins. Progress can be monitored by viewing messages displayed above the progress bar. 30. From the Install Complete panel, click Done. Once the Tivoli Asset Management for IT installation program has completed installation and configuration tasks, it exits. Logs can be found at <TAMIT_Home>/logs.

Chapter 5. Tivoli Asset Management for IT installation program overview

85

Tivoli Asset Management for IT installation with manual middleware configuration

You can elect to have your database server configured automatically by the Tivoli Asset Management for IT installation program. Alternatively, you can choose to configure your database server manually to work with Tivoli Asset Management for IT. All other middleware components, that is, the directory server and the J2EE server, must be configured manually to work with Tivoli Asset Management for IT prior to using the Tivoli Asset Management for IT installation program. The information contained in this section provides details on how to manually configure Tivoli Asset Management for IT middleware prior to running the Tivoli Asset Management for IT installation program. Also included in this section is a procedure describing how to advance through the Tivoli Asset Management for IT installation program to complete the Tivoli Asset Management for IT deployment. Before you begin, ensure you have addressed the following prerequisite conditions: v You have designated a Windows-based machine that will be used to launch the Tivoli Asset Management for IT installation program. v All of your middleware is at the level described in Tivoli Asset Management for IT component requirements on page 3.

Manually configuring the database server

If you choose to not have the Tivoli Asset Management for IT installation program automatically configure the database server, you must complete the manual configuration before you use the Tivoli Asset Management for IT installation program . For DB2 on UNIX systems, ensure you have a minimum of 8 GB (binary) free of space in the DB2 database instance home directory (/home/ctginst1) in order to meet the default tablespace disk space requirements of the DB2 install. For DB2 on Windows, ensure you have a minimum of 8 GB of free space in the DB2 installation directory.

Manually configuring DB2 9.1

To configure an existing DB2 9.1 server for use with Tivoli Asset Management for IT, complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. Create system users. a. Log into the system as a user that has administrative permissions on the system. b. DB2 requires user accounts that are operating system user accounts. Create operating system users named ctginst1 and maximo, using user management tools available on the system. For AIX, use SMIT to add the users. For the ctginst1 user, assign the primary group as db2grp1 and secondary groups of staff and dasadm1. For the maximo user, it is not necessary to assign a specific group. After the user IDs have been created, log into the system using the user IDs and change the password for each account. 2. Create the DB2 instance: a. Use the following command to create the DB2 instance:

86

Installation Guide for IBM WebSphere Application Server:

Windows
db2icrt -s ese -u db2admin,<pwd> -r 50005,50005 ctginst1

Linux
db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1

AIX
db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1

b. Set the listening port for the instance Windows

db2 update dbm cfg using svcename 50005

c. Set instance service to start automatically Windows

sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance: Windows

db2start

UNIX
su - ctginst1 db2start

3. Create a database a. Open up the DB2 Control Center for the instance you plan to use: Windows 1) Open a command window. 2) Type the following command:
set DB2INSTANCE=ctginst1 db2set DB2COMM=tcpip

3) Type the following command:

db2cc

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, right-click the Databases folder located below the instance name, and then select Create Database? With Automatic Maintenance. c. From the Specify a name for your new database panel, enter maxdb71 for both the Database name and Alias fields. d. Enable the Enable database for XML option. This creates a Unicode database with a code set of UTF-8. e. Click Next. f. 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 a different directory. If you specify a path, the directory must exist. g. From the Select your maintenance strategy panel, select Yes, I can specify an offline maintenance window of at least an hour when the database is inaccessible, and then click Next.

Chapter 5. Tivoli Asset Management for IT installation program overview

87

h. From the Specify when offline automatic maintenance activities can run, provide scheduling details for offline maintenance, and then click Next. i. From the Provide a valid SMTP server panel, enter the name of the SMTP server that is used to communicate DB2 messages concerning this database, and then click Next. j. From the Review the actions that will take place when you click Finish panel, review the choices you have made, and then click Finish. The database is then created. For AIX 5.3 systems, use the following command to create the DB2 instance.
db2icrt a SERVER s ese p 50005 u db2fenc1 ctginst1

To create the database on AIX systems, su to ctginst1 and use the 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 Value column. e. Enter 1024, 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 1024, 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 4, 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. For AIX 5.3 systems, you cannot launch the DB2 Control Center locally. The best way to configure the database on AIX 5.3 systems is to configure 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 tablespace.

88

Installation Guide for IBM WebSphere Application Server:

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 Asset Management for IT. b. From the right-click menu, select Create. c. Specify MAXDATA as your new tablespace, and then click Next. d. Select Regular as the type of tablespace and then click Next. e. Click Create to create a buffer pool for the tablespace. 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 drive specification by choosing Server (SCSI), and then click Next. k. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option, and then click Next. l. Click Finish. 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 Tivoli Asset 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. 8. Create a schema. a. From the DB2 Control Center, locate and right-click the Schema entry under the DB2 database that you created for use with Tivoli Asset Management for IT. 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. 9. Create a temporary 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 Asset Management for IT. b. From the right-click menu, select Create. c. Specify MAXTEMP for your new tablespace, and then click Next. d. Select System temporary as the type of tablespace and then click Next.
Chapter 5. Tivoli Asset Management for IT installation program overview

89

e. Select the previously created bufferpool (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 drive specification by choosing Server (SCSI), and then click Next. h. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option, and then click Next. i. Click Finish. 10. Install the appropriate fix pack. Refer to the tables presented in Tivoli Asset Management for IT component requirements on page 3. After you have installed the fix pack, run the dasupdt command to update the DB2 Administration Server to the applied fix pack. Also run the db2iupdt command to update the DB2 instance. Start by first stopping all processes that are running for the database instance (ctginst1), and then run the following command: Windows
C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

UNIX
<DB2DIR>/instance/db2iupdt ctginst1

Manually configuring DB2 8.2

To configure an existing DB2 8.2 server for use with Tivoli Asset Management for IT, complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. Create system users. a. Log into the system as a user that has administrative permissions on the system. b. DB2 requires user accounts that are operating system user accounts. Create operating system users named ctginst1 and maximo, using user management tools available on the system. For AIX, use SMIT to add the users. For the ctginst1 user, assign the primary group as db2grp1 and secondary groups of staff and dasadm1. For the maximo user, it is not necessary to assign a specific group. After the user IDs have been created, log into the system using the user IDs and change the password for each account. 2. Create the DB2 instance: a. Use the following command to create the DB2 instance: Windows
db2icrt -s ese -u db2admin,<pwd> -r 50005,50005 ctginst1

Linux
db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1

AIX
db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1

b. Set the listening port for the instance Windows

db2 update dbm cfg using svcename 50005

90

Installation Guide for IBM WebSphere Application Server:

c. Set instance service to start automatically Windows

sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance: Windows

db2start

UNIX
su - ctginst1 db2start

3. Create the database: Windows a. Open a command window and type the following command:
set DB2INSTANCE=ctginst1

b. Now type db2cmd to open the DB2 Command Window: c. From the new instance window issue the following commands:
db2start db2 create db maxdb71 using codeset utf-8 territory us pagesize 32 k

UNIX a. Open a command window and type the following command:

su - ctginst1

b.

From the new instance window issue the following commands:

db2start db2 create db maxdb71 using codeset utf-8 territory us pagesize 32 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 4096, 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 Value column. g. Enter 1024, 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 30000, 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.
Chapter 5. Tivoli Asset Management for IT installation program overview

91

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 tablespace. 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 Asset Management for IT. b. c. d. e. f. g. h. i. j. k. From the right-click menu, select Create. Specify MAXDATA as your new tablespace, and then click Next. Select Regular as the type of tablespace and then click Next. Click Create to create a new buffer pool for the tablespace. 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. Ensure the Create buffer pool immediately choice is selected, and then click OK. Highlight the newly created buffer pool and click Next. From the Space management panel, specify Database-managed space and click Next. From the Containers panel, click Add. Set the Type to File, Size to 5000 Mb, and File name to CTGDAT.

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 drive specification by choosing Server (SCSI), and then click Next. o. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option, and then click Next. p. From the Summary panel, click Finish. 7. Create a temporary 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 Asset Management for IT. b. From the right-click menu, select Create. c. Specify MAXTEMP for your new tablespace, and then click Next. d. Select System temporary as the type of tablespace and then click Next. e. Select the previously created bufferpool (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.

92

Installation Guide for IBM WebSphere Application Server:

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 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 Tivoli Asset 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. 9. Create a schema. a. From the DB2 Control Center, locate and right-click the Schema entry under the DB2 database that you created for use with Tivoli Asset Management for IT. b. From the right-click menu, select Create. c. Specify a name for your new schema, and then click OK. This name should 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 Tivoli Asset Management for IT component requirements on page 3. If you installed a fix pack, run the dasupdt command to update the DB2 Administration Server to the applied fix pack. After you have installed a fix pack, you will also need to run the db2iupdt command to update the DB2 instance. Start by first stopping all processes that are running for the database instance (ctginst1), and then run the following command: Windows
C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

UNIX
<DB2DIR>/instance/db2iupdt ctginst1

Manually configuring Oracle 10g

If you are using Oracle 10g Rel2, ensure the Oracle 10g Rel2 patch 3 is installed To configure an existing Oracle 10g Rel2 or 10g Rel1 server for use with Tivoli Asset Management for IT, complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. Log in as a dba, such as sys or system.
Chapter 5. Tivoli Asset Management for IT installation program overview

93

2. Create a new 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, 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 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 the database, and then click Next. i. Ensure Use Database File Locations from Template is selected as the value to use for database file location, and then click Next. j. Leave defaults selected for the database recovery options panel, and then click Next. k. From the Sample Schemas panel, click Next. l. From the Memory tab, select Custom, provide the following values (measured in bytes), and then click the Character Sets tab. Shared Memory Management Set this value to Manual. Shared Pool Set this value to 157286400. Buffer Cache Set this value to 36000000. Java Pool Set this value to 33554432. Large Pool Set this value to 8388608. PGA Size Set this value to 37748736. m. From the Database Character Set 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. cursor_sharing Change this value to FORCE nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000 From the Initialization Parameters panel, click Next. From the Database Storage panel, click Next. From the Creation Options panel, click Finish. From the Confirmation panel, click OK.

q. r. s. t.

94

Installation Guide for IBM WebSphere Application Server:

u. Click Exit to exit the Database Configuration Assistant. The database has been successfully created. 3. Log into SQL *Plus using the following information: User Name system Password Password you entered in step 2g. Host String ctginst1 4. Create a tablespace using the following command in SQL*Plus:
Create tablespace maxdata datafile C:\oracle\product\10.2.0\oradata\ctginst1\maxdata.dbf size 1000M autoextend on;

The directory specified in the example should be changed to the location where the database will reside. 5. Create a temporary tablespace using the following command in SQL*Plus:
Create temporary tablespace maxtemp tempfile C:\oracle\product\10.2.0\oradata\ctginst1\maxtemp.dbf size 1000M autoextend on maxsize unlimited;

The directory specified in the example should be changed to the location where the database will reside. 6. Create the maximo user and grant permissions using the following command in SQL*Plus:
Create user maximo identified by maximo default tablespace maxdata temporary tablespace 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 Oracle9i Rel2

If you are using Oracle9i Rel2, ensure Oracle 9.2.0.8 is installed To configure an existing Oracle Oracle9i Rel2 server for use with Tivoli Asset Management for IT, complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. Create a new 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, 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 default of Dedicated Server Mode selected, and click Next.

Chapter 5. Tivoli Asset Management for IT installation program overview

95

g. From the Memory tab, select Custom, enter the following values (M Bytes), and then click Next. Shared Pool Set this value to 150. Buffer Cache Set this value to 36. Java Pool Set this value to 32. Large Pool Set this value to 8. PGA Size Set this value to 36. h. Select the Character Sets tab and select Use Unicode (AL32UTF8) as the Database Character Set. i. Click All Initialization Parameters. j. Locate the following parameters, change them to the values indicated, and then click Close. nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000 k. Click Next. l. From the Database Storage panel, click Next. m. From the Creation Options panel, select the Create Database option, and click Finish. n. From the Confirmation panel, click OK. o. Once the database has been successfully created, click Password Management. p. Unlock the CTXSYS account by removing the check mark in the Lock Account? column for that entry, enter a password for the account, and then click OK. q. Click Exit to exit the Database Configuration Assistant. The database has been successfully created. The database has been successfully created. 2. Create a tablespace using the following command in SQL*Plus:
Create tablespace maxdata datafile C:\oracle\oradata\maxdata\maxdata.dbf size 1000M autoextend on;

The directory specified in the example should be changed to the location where the database will reside. 3. Create a temporary tablespace using the following command in SQL*Plus:
create temporary tablespace maxtemp tempfile C:\oracle\oradata\maxtemp\maxtemp.dbf size 1000M autoextend on maxsize unlimited;

The directory specified in the example should be changed to the location where the database will reside. 4. Create the maximo user and grant permissions using the following command in SQL*Plus:

96

Installation Guide for IBM WebSphere Application Server:

create user maximo identified by maximo default tablespace maxdata temporary tablespace 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 Server

Ensure the MS SQL Server 2005 service pack 2 is installed. To configure an existing SQL Server 2005 server for use with Tivoli Asset Management for IT, complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. Configure the listener port. If enabled, the default instance of the Microsoft SQL Server Database Engine listens on TCP port 1433. Named instances of the SQL Server Database Engine and SQL Server Compact Edition are configured for dynamic ports, which means they select an available port when the SQL Server service is started. When connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port can be opened in the firewall. a. Open Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager b. From the SQL Server Configuration Manager navigation pane, expand SQL Server 2005 Network Configuration > Protocols for <instance name to be used with Tivoli Asset Management 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 using dynamic ports. Since Tivoli Asset Management for IT requires SQL Server to listen on a static port, this field must be blank. e. For each IP address listed, enter 1433 for the TCP Port field, f. Click OK. g. From the SQL Server Configuration Manager navigation pane, click SQL Server 2005 Services. h. 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 2005. To determine if Full-text Search is installed on your existing 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 command prompt by executing isqlw. b. Type the following command:
select FULLTEXTSERVICEPROPERTY ( IsFulltextInstalled )
Chapter 5. Tivoli Asset Management for IT installation program overview

97

In the event that you did not install Full-text Search (the resulting value is zero), you must do so at this time. The following steps provide a general guideline describing how you can change this and other settings after having installed SQL Server. a. Insert the Microsoft SQL Server 2005 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 > Microsoft SQL Server 2005 > SQL Server Management Studio). b. Right-click the Databases folder from the tree view, and select New Database. c. In the Database Properties dialog box, in the General tab, specify a unique database 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 1MB, unrestricted growth. e. If you prefer, modify the log settings to accommodate your production environment. f. Click Add. 4. Create the Maximo User for SQL Server a. Open SQL Server Enterprise Manager Studio (Start > Programs > Microsoft SQL Server 2005 > 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,MAXIMO go

e. Click Execute. f. Enter the following script to change the database owner to maximo.
sp_changedbowner MAXIMO go

g. Click Execute. Note that because SQL Server does not support UTF-8, Tivoli Asset Management for IT does not have multilingual support when deployed with SQL Server. Note: If you add additional logical names to the database and set their file group to a value other than PRIMARY, you will have to complete the following steps after you 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_HOME>\maximo\applications\ maximo\properties\maximo.properties file:
Database.SQL.DataFilegroupName=<your logical name>

98

Installation Guide for IBM WebSphere Application Server:

3. Execute the configuration steps outside of the Tivoli Asset Management for IT installation program by using the taskrunner utility, located in the <TAMIT_HOME>\scripts directory. Note that these additional steps must be completed only if you have added additional logical names to the database and set their file group to a value other than PRIMARY.

Manually configuring the directory server

You must complete the manual configuration of the directory server before you use the Tivoli Asset Management for IT installation program if you choose to not have the Tivoli Asset Management for IT installation program automatically configure it. Important: When entering LDAP values for Tivoli Asset Management for IT installation panel fields, entries in LDIF files, or values you enter directly into an directory instance using the directory servers own tools, be aware of the product-specific syntax rules for using special characters in an LDAP string. In most cases, special characters must be preceded by an escape character in order to make it readable by the directory server. Failing to escape special characters contained in an LDAP string used with Tivoli Asset Management for IT will result in Tivoli Asset Management for IT errors. Many directory server products consider a blank space as a special character that is part of the LDAP string. Therefore, if you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you will encounter Tivoli Asset Management for IT errors that will be difficult to troubleshoot. Refer to the product documentation for your directory server for more information on special characters in LDAP strings.

Manually configuring IBM Tivoli Directory Server

To configure IBM Tivoli Directory Server prior to launching the Tivoli Asset Management for IT installation program, you must create a new ITDS instance. 1. Using your preferred method, create a user on the system and assign it to the appropriate group. Windows Create the user idsccmdb and make it a member of the Windows Administrators group. 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 its primary group. 2. If the Instance Administration Tool is not already started, ensure you are logged in as an administrator on the system, and then start the tool Windows Select Programs > IBM Tivoli Directory Server 6.1 > Instance Administration Tool. UNIX Type ./opt/IBM/ldap/V6.1/sbin/idsxinst at the command line. 3. From the Instance Administration Tool, click Create. 4. On the Create a new directory server instance window, click Create a new directory server instance, and then click Next.
Chapter 5. Tivoli Asset Management for IT installation program overview

99

5. From the Instance details window, complete the following fields, and then click Next. User name Select idsccmdb as the system user ID of the user who will own the directory server instance. This name will also be the name of the directory server instance. Install location Enter the location where the directory server instance files will be stored. Encryption seed string Type a string of characters that will be used as an encryption seed. This value must be a minimum of 12 characters. Instance description Enter a brief description of the instance. 6. From the DB2 instance details panel, enter idsccmdb as the value for the DB2 instance name field, and then click Next. 7. From the TCP/IP settings for multihomed hosts panel, select Listen on all configured IP addresses, and then click Next. 8. On the TCP/IP port settings panel, complete the following fields, and then click Next. Server port number Enter 389 as the contact port for the server. Server secure port number Enter 636 as the secure port for the server. Admin daemon port number Enter 3538 as the administration daemon port. Admin daemon secure port number Enter 3539 as the administration daemon secure port. 9. From the Option steps panel, leave the following options selected, and then click Next. Configure admin DN and password You will configure the administrator DN and password for the directory server instance now. Configure database You will configure the database for the directory server instance now. 10. From the Configure administrator DN and password window panel, complete the following fields, and then click Next. Administrator DN Enter cn=root for the administrator distinguished name. Administrator Password Enter a password for the Administrator DN. 11. From the Configure database panel, complete the following fields, and then click Next. Database user name Enter idsccmdb as the database user. Password Enter the password for the idsccmdb user.

100

Installation Guide for IBM WebSphere Application Server:

Database name Enter idsccmdb as the database to be used with this directory instance. 12. From the Database options panel, complete the following fields, and then click Next. Database install location Enter the location where you installed DB2. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected. From the Verify settings panel, review the instance creation details provided, and then click Finish to create the idsccmdb instance. Click Close to close the window and return to the main window of the Instance Administration Tool. Click Close to exit the Instance Administration Tool. Ensure the server is stopped. Windows IBM Tivoli Directory Server Instance V6.1 - idsccmdb UNIX V6.1 ibmslapd server daemon 17. Launch the IBM Tivoli Directory Server Configuration Tool: Windows Select Programs > IBM Tivoli Directory Server 6.1 > Instance Administration Tool. UNIX Type ./opt/IBM/ldap/V6.1/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

13. 14. 15. 16.

21. Click OK. 22. 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=users and ou=groups DNs you created. These users and groups are defined in order for VMM to be used to secure Tivoli Asset Management for IT. Important: Before you begin this procedure, ensure you have the following users and groups created in your LDAP repository:
Table 19. Tivoli Asset Management for IT required users and groups User wasadmin maxadmin mxintadm MAXADMIN (must be uppercase) MAXADMIN (must be uppercase) Groups

Chapter 5. Tivoli Asset Management for IT installation program overview

101

Table 19. Tivoli Asset Management for IT required users and groups (continued) User maxreg Groups

Here is an example of the default base ldif data:

dn: o=ibm,c=us objectClass: top objectClass: organization o: IBM dn: ou=SWG, o=ibm,c=us ou: SWG objectClass: top objectClass: organizationalUnit dn: ou=groups,ou=SWG, o=ibm,c=us ou: groups objectClass: top objectClass: organizationalUnit dn: ou=users,ou=SWG, o=ibm,c=us ou: users objectClass: top objectClass: organizationalUnit dn: cn=wasadmin,ou=users,ou=SWG, o=ibm,c=us uid: wasadmin userpassword: wasadmin objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: person objectclass: top title: WebSphere Administrator sn: wasadmin cn: wasadmin

23. 24. 25. 26.

Note: If you create the LDIF file on Windows, ensure that you remove the ^M characters from the file before using. From the IBM Tivoli Directory Server Configuration Tool, click Import LDIF data. Use the browse button to locate the LDIF file. Click Import. Close the IBM Tivoli Directory Server Configuration Tool and restart the server.

Manually configuring Microsoft Active Directory

If you choose to manually configure a Microsoft Active Directory resource for use with Tivoli Asset Management for IT, complete the following steps prior to running the Tivoli Asset Management for IT installation program: 1. Open the domains security policy for editing by selecting Start > Administrative Tools > Domain Security Policy. 2. From the Default Domain Security Settings interface, navigate to Security Settings > Account Policies > Password Policy. 3. For each password policy setting displayed, right-click the setting, select Properties, and set it to the appropriate value, as shown in the table below:

102

Installation Guide for IBM WebSphere Application Server:

Table 20. Policy Setting Enforce password history Value Not Defined Step On the properties panel, set the check box for Define this policy setting to unchecked. On the properties panel, set the check box to unchecked. On the properties panel, set the check box to unchecked. On the properties panel set the check box Define this policy setting to checked and set the value to 7. On the properties panel, set the check box Define this policy setting to checked and ensure that the value Disabled is selected. On the properties panel, set the check box Define this policy setting to checked and ensure that the value Disabled is selected.

Maximum password age Minimum password age Minimum Passsword length

Not Defined Not Defined 7 characters

Password must meet complexity requirements

Disabled

Store passwords using reversible encryption

Disabled

4. Open a command prompt window and type gpupdate /force, or, alternatively, you can simply reboot the system. 5. Open the Active Directory Users and Computers user interface by selecting Start > Control Panel > Administrative Tools > Active Directory Users and Computers and then select the domain that you will be working with. 6. Edit the domain functional level of the domain by selecting Action > Raise Domain Functional Level. The Raise Domain Functional Level dialog box will appear. 7. Select Windows Server 2003 from the Select an available domain functional level dropdown menu, and then click Raise. An alert dialog box will appear. 8. Click OK. 9. When the domain raise task has completed, click OK. 10. In the Active Directory Users and Computers user interface, right-click the domain you want to work with and select New > Organizational Unit. 11. Enter a name for the new Organizational Unit (OU), for example, SWG, and then click OK. 12. 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. 13. 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. 14. Create the MAXADMIN group: a. Right click the Groups OU and select New > Group. b. From the New Object - Group dialog, enter the following values, and then click OK:
Chapter 5. Tivoli Asset Management for IT installation program overview

103

Group name Enter MAXADMIN as the group name. This value must be capitalized. Group name (pre-Windows 2000) Enter MAXADMINPRE2K as the pre-Windows 2000 group name. This value must be capitalized and must be different than the name entered above for Group name. Group scope Global Group type Security 15. Create the MAXIMOUSERS group: a. Right click the Groups OU and select New > Group. b. From the New Object - Group dialog, enter the following values, and then click OK: Group name Enter MAXIMOUSERS as the group name. This value must be capitalized. Group name (pre-Windows 2000) Enter MAXIMOUSERS as the pre-Windows 2000 group name. This value must be capitalized. Group scope Global Group type Security 16. 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 name Enter wasadmin. Initials Leave this field blank. Last name Leave this field blank. Full name Enter wasadmin. User login name Enter wasadmin in the first field. Leave the default value of the second field. User login name (pre-Windows 2000) This field will be filled with the same value (wasadmin) entered for the User login name. c. From the next panel, enter the following information, and then click Next:

104

Installation Guide for IBM WebSphere Application Server:

Password Enter a 7 character password for wasadmin. User must change password at next logon Ensure this checkbox is deselected. User cannot change password Ensure this checkbox is selected. Password never expires Ensure this checkbox is selected. Account is disabled Ensure this checkbox is deselected. d. Review the password settings in the summary panel, and click Finish. 17. Create the maxadmin 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 name Enter maxadmin. Initials Leave this field blank. Last name Leave this field blank. Full name Enter maxadmin. User login name Enter maxadmin in the first field. Leave the default value of the second field. User login name (pre-Windows 2000) This field will be filled with the same value (maxadmin) entered for the User login name. c. From the next panel, enter the following information, and then click Next: Password Enter maxadmin as the password for the maxadmin user. User must change password at next logon Ensure this checkbox is deselected. User cannot change password Ensure this checkbox is selected. Password never expires Ensure this checkbox is selected. Account is disabled Ensure this checkbox is deselected. d. Review the password settings in the summary panel, and click Finish. 18. Create the mxintadm 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:

Chapter 5. Tivoli Asset Management for IT installation program overview

105

First name Enter mxintadm. Initials Leave this field blank. Last name Leave this field blank. Full name Enter mxintadm. User login name Enter mxintadm in the first field. Leave the default value of the second field. User login name (pre-Windows 2000) This field will be filled with the same value (mxintadm) entered for the User login name. c. From the next panel, enter the following information, and then click Next: Password Enter a 7 character value as the password for the mxintadm user. User must change password at next logon Ensure this checkbox is deselected. User cannot change password Ensure this checkbox is selected. Password never expires Ensure this checkbox is selected. Account is disabled Ensure this checkbox is deselected. d. Review the password settings in the summary panel, and click Finish. 19. Create the maxreg 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 name Enter maxreg. Initials Leave this field blank. Last name Leave this field blank. Full name Enter maxreg. User login name Enter maxreg in the first field. Leave the default value of the second field. User login name (pre-Windows 2000) This field will be filled with the same value (maxreg) entered for the User login name. c. From the next panel, enter the following information, and then click Next:

106

Installation Guide for IBM WebSphere Application Server:

Password Enter a 7 character value as the password for the maxreg user. User must change password at next logon Ensure this checkbox is deselected. User cannot change password Ensure this checkbox is selected. Password never expires Ensure this checkbox is selected. Account is disabled Ensure this checkbox is deselected. d. Review the password settings in the summary panel, and click Finish. 20. Add users to the MAXADMIN group: a. Click on the Groups object under the SWG OU. b. Double-click the MAXADMIN group listed in the Groups pane. c. From the MAXADMIN properties dialog, select the Members tab and then click Add. d. From the Select Users, Contacts, Computers, or Groups dialog, click Advanced. e. On the Advanced panel, click Find Now. f. From the Search results list, select the maxadmin and mxintadm users, and then click OK. Ensure you are selecting the maxadmin user and not the maxadmin group from this list. g. Click OK to add the users. 21. Add users to the MAXIMOUSERS group: a. Click on the Groups object under the SWG OU. b. Double-click the MAXIMOUSERS group listed in the Groups pane. c. From the MAXIMOUSERS properties dialog, select the Members tab and then click Add. d. From the Select Users, Contacts, Computers, or Groups dialog, click Advanced. e. On the Advanced panel, click Find Now. f. From the Search results list, select the maxadmin, mxintadm, and maxreg users, and then click OK. Ensure you are selecting the maxadmin user and not the maxadmin group from this list. g. Click OK to add the users. 22. You can now exit out of the Active Directory Users and Computers user interface. Microsoft Active Directory configuration is complete and you are now ready to install the remaining Tivoli Asset Management for IT middleware and configure the J2EE server to use Microsoft Active Directory.

Manually configuring the J2EE server

You must complete the manual configuration of the J2EE server before you use the Tivoli Asset Management for IT installation program if you choose to not have the Tivoli Asset Management for IT installation program automatically configure it.
Chapter 5. Tivoli Asset Management for IT installation program overview

107

To configure the J2EE server prior to launching the Tivoli Asset Management for IT installation program, follow these steps: IBM WebSphere Network Deployment 1. Manually copy the keystore file from the IBM WebSphere Network Deployment deployment manager host to a temporary directory on the Tivoli Asset Management for IT administrative system where you are installing Tivoli Asset Management for IT: 2. 3. 4. 5. 6. <WAS_home>/profiles/ctgDmgr01/etc/trust.p12 Launch the profile creation wizard. Click Next in the Welcome dialog box. Select the create a deployment manager option. Click Next. Accept the default value or specify a Profile name. Click Next. 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 a browser. 9. Select the Run the Application Server as a Windows service and log on as a local 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 machine 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 WebSphere

This procedure provides task information for manually configuring Virtual Member Manager (VMM) to secure Tivoli Asset Management for IT. During the installation process, the Tivoli Asset Management for IT installation program provided you with the option of automatically configuring Tivoli Asset Management for IT middleware. If you elected to have the Tivoli Asset Management for IT installation program automatically configure Tivoli Asset Management for IT middleware, then it will, among other tasks, perform Virtual

108

Installation Guide for IBM WebSphere Application Server:

Member Manager (VMM) configuration for you. If you elected to manually configure Tivoli Asset Management for IT middleware for use with Tivoli Asset Management for IT, you will have to manually configure VMM. VMM provides you with the ability to access and maintain user data 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 of independent user repositories. Each repository may be an entire external repository or, in the case of LDAP, a subtree within that repository. The root of each repository is mapped to a base entry within the federated repository, which is a starting point within the hierarchical namespace of the virtual realm. Note that if you intend to configure VMM to use SSL with a federated LDAP repository, it must be done only after a successful Tivoli Asset Management for IT installation. If VMM is configured to use SSL with a federated LDAP repository prior to completing the Tivoli Asset Management for IT installation, the installation will fail. Do not configure a WebSphere VMM LDAP federated repository to use SSL with an LDAP directory prior to installing Tivoli Asset Management for IT. Configure SSL after the Tivoli Asset Management for IT installation program has completed successfully. To add an LDAP directory to the VMM virtual repository, you must first add the LDAP directory to the list of repositories available for configuration for the federated repository and then add the root of baseEntries to a search base within the LDAP directory. Multiple base entries can be added with different search bases for a single LDAP directory. The instructions provided here are for IBM Tivoli Directory Server. If you are configuring VMM to use Microsoft Active Directory, substitute values you used in Reusing Microsoft Active Directory on page 44 and Manually configuring Microsoft Active Directory on page 102 where appropriate in this procedure. You will also have to modify the VMMCRONTASK as shown in Manually configuring the VMMSYNC cron task for Microsoft Active Directory on page 132. Important: Before you begin this procedure, ensure you have a wasadmin user created in your LDAP repository. To add the IBM Tivoli Directory Server to VMM, complete the following steps: 1. Login to the admin 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 identifier Enter ISMITDS. Directory type Select the directory type, in this example, IBM Tivoli Directory Server Version 6 Primary host name Enter the fully-qualified host name or IP address of the IBM Tivoli Directory Server server.
Chapter 5. Tivoli Asset Management for IT installation program overview

109

Port

Enter 389.

Support referrals to other LDAP servers Set this to ignore. Bind distinguished name Enter cn=root Bind password Enter the password for the bind distinguished name. Login properties Leave this value blank. Certificate mapping Select EXACT_DN 6. Return to the Federated repositories page by clicking Security ? Secure administration, applications, and infrastructure, selecting Federated repositories from the Available realm definitions drop-down list, and then clicking Configure. 7. Locate the Repositories in the realm section and click Add Base entry to Realm. Note that if there is an existing file repository entry in the Repositories in the realm table, you must select it click Remove, and save the change, after creating the new entry. 8. Enter the following values, and then click Apply and then click Save. Repository Select ISMITDS. Distinguished name of a base entry that uniquely identifies this set of entries in the realm ou=SWG,o=IBM,c=US Distinguished name of a base entry in this repository ou=SWG,o=IBM,c=US 9. From the Federated repositories configuration page, enter the following values and then click Apply and then click Save.: Realm name Enter ISMRealm. Primary administrative user name Enter wasadmin. This value should be a valid user from the configured LDAP repository. Server user identity Select Automatically generated server identity. Ignore case for authorization Select this check box. 10. Click Supported entity types, and then click PersonAccount. 11. From the PersonAccount configuration page, enter the following values: Entity type Verify that the value is PersonAccount. Base entry for the default parent Enter ou=users,ou=SWG,o=IBM,c=US. Relative Distinguished Name properties Enter uid.

110

Installation Guide for IBM WebSphere Application Server:

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 type Verify that the value is Group. Base entry for the default parent Enter ou=groups,ou=SWG,o=IBM,c=US. Relative Distinguished Name properties Enter cn. 15. Click Supported entity types, and then click OrgContainer. 16. From the OrgContainer configuration page, enter or verify the following values: Entity type Verify that the value is OrgContainer. Base entry for the default parent Enter ou=SWG,o=IBM,c=US. Relative Distinguished Name properties Enter 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 configuration page, 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 and the managed nodes: a. <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager.bat b. <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode.bat c. <WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat d. <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat Note: Substitute UNIX path and file extension values where appropriate. You have now successfully completed setting up VMM. The next step is to perform post J2EE server tasks.

Performing post installation tasks for the J2EE server

Use this procedure to perform post installation steps for the J2EE server. During the installation process, the Tivoli Asset Management for IT installation program provided you with the option of automatically configuring Tivoli Asset Management for IT middleware. If you elected to have the Tivoli Asset Management for IT installation program automatically configure Tivoli Asset Management for IT middleware, then it will, among other tasks, perform J2EE

Chapter 5. Tivoli Asset Management for IT installation program overview

111

server configuration for you. If you elected to manually configure Tivoli Asset Management for IT middleware for use with CCMDB, you will have to manually configure the J2EE server. 1. Invoke a browser window and open the Administrative Console by typing in the browser address bar: http://<machine_name>:9060/admin. This URL address depicts the default port number (9060) and context (admin) for the Administrative Console. Enter a username to login. Note the browser will be redirected to a secure port (9043). 2. Create the MXServer Application Server. This step is only necessary if you did not install WebSphere using the Tivoli middleware installer. a. Expand the Servers link and click Application servers. b. Click New. c. d. e. f. g. h. Type MXServer and click Next. Accept all default settings and click Next. Accept default settings and click Next. Click Finish. Click Preferences. 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 tree view 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 tree view click Deployment manager. b. From the Server Infrastructure group, expand the Java and Process Management 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 tree view click Application servers. b. Select the checkbox beside MXServer. c. Click Start. 6. Identify the HTTP Transfer Port Numbers:

112

Installation Guide for IBM WebSphere Application Server:

a. Expand Servers > Application servers, and click MXServer from the main window. b. Open the Web Container Settings and click Web container transport chains. c. Note the default port number as it appears with WC_defaulthost (9080). d. Click Save. 7. Create the virtual host. a. Expand the Environment link from the tree view. b. Click Virtual Hosts. c. Click New. d. In the General Properties section, type maximo_host in the Name box. e. Click Apply. Click Save. From the Virtual Hosts window, click maximo_host. Click the Host Aliases link. Click New. Type * (asterisk) for Host Name and type the HTTP port number (by default 80). k. Click OK. f. g. h. i. j. 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. t. u. v. w. x. y. Type * (asterisk) for Host Name and type 9080 for the port number. Click OK. Click New. Type * (asterisk) for Host Name and type 9044 for the port number. Click OK. From the navigational breadcrumb trail, click maximo_host. Click Apply and then click OK.

Manually configuring JMS queues

This procedure provides details on steps to configure JMS queues, which must be completed prior to deploying Tivoli Asset Management for IT EAR files. During the installation process, the Tivoli Asset Management for IT installation program provided you with the option of automatically configuring Tivoli Asset Management for IT middleware. If you elected to have the Tivoli Asset Management for IT installation program automatically configure Tivoli Asset Management for IT middleware, then it will, among other tasks, create and configure JMS message queues for you. If you elected to manually configure Tivoli Asset Management for IT middleware for use with Tivoli Asset Management for IT, you will have to manually configure these message queues. To configure the JMS queues, complete the following steps: 1. Start the WebSphere application server.
Chapter 5. Tivoli Asset Management for IT installation program overview

113

2. Launch Internet Explorer and open the WebSphere Administrative Console by typing the following URL:
http://<machine_name>:<port_number>/ibm/console

For example, enter a URL similar to the following:

http://localhost:9060/ibm/console

3. At the Welcome, please enter your information login screen, enter your User ID, then click Log in. This action opens the Welcome screen for the WebSphere 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 of the bus. 8. Click New to open the Buses > New dialog box where you can add a new service integration bus. 9. Enter intjmsbus as the name of the new bus in the Name field. 10. Deselect the Bus security check box. If you leave this box checked, intjmsbus inherits the Global Security setting of the cell. 11. Click Next. 12. Click Finish. 13. Click Save. This step propagates the JMS bus setup to the cluster configuration. Confirm that build completed screen displays the following: v Bus name, for example, intjmsbus. v Auto-generated, unique ID (UUID), for example, 4BCAC78E15820FED. v The Secure field is unchecked.

Adding a server to the service integration bus

Complete the following steps to add a server to the service integration bus: 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 name ctgNode01: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. 9. Click Save. 10. Click OK. 11. Select intjmsbus. 12. Change the value of the High message threshold field to a minimum value of 500,000 messages, and then click Apply.

114

Installation Guide for IBM WebSphere Application Server:

If the number of messages awaiting processing exceeds the High Message Threshold you set, the application server will take action to limit the addition of new messages in the processing queues. Depending on your message requirements, you may want to enter a higher message threshold value. You can determine an optimal message threshold setting by monitoring the messaging in/out queues and the impact of the message threshold setting on system performance. 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 initial configuration, you must open the Additional Properties menu in the Administrative Console and change the threshold value for each child configuration. 13. Click Save. 14. Click OK.

Creating the service integration bus destination for the continuous inbound (CQINBD) queue
To add a logical address for the continuous inbound bus destination queue (CQINBD) within the JMS bus, complete the following steps: 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. 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 service integration 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 for point-to-point messaging dialog box. Note that you must 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 and process 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 the CQINBD bus destination queue. 10. Navigate the path Buses > intjmsbus > Destinations, then click CQINBD to open the configuration dialog box where you must make the following changes: v Click None as the Exception destination value. v Change the Maximum failed deliveries value to 1. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. 11. Click Apply. 12. Click Save.

Chapter 5. Tivoli Asset Management for IT installation program overview

115

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 following steps: 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. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. A bus destination is a virtual place within a service integration 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. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the Description field, then click Next to open the Create a new queue for point-to-point messaging dialog box. Note that you must use this value and it must contain only uppercase letters. 7. Select the Bus Member pull-down and choose 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 must make the following changes: v Click None as the Exception destination value. v Change the Maximum failed deliveries value to 1. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. 11. Click Apply. 12. Click Save.

Creating the service integration bus destination for the sequential outbound (SQOUTBD) queue
To add a logical address for the sequential outbound bus destination queue (SQOUTBD) within the service integration bus, complete the following steps: 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. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. A bus destination, for example SQOUTBD, is a virtual place within a service integration 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.

116

Installation Guide for IBM WebSphere Application Server:

6. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the Description field, then click Next to open the Create a new queue for point-to-point messaging dialog box. Note that you must 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 and process 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 the path Buses > intjmsbus > Destinations, then click SQOUTBD to open the configuration dialog box where you must make the following changes: v Click None as the Exception destination value. v Change the Maximum failed deliveries value to 1. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. 11. Click Apply. 12. Click Save.

Creating the JMS connection factory

You add a connection factory for creating connections to the associated JMS provider of point-to-point messaging queues. 1. From the WebSphere Administrative Console, click Resources JMS Connection factories. 2. From the Scope drop-down list select Cell=ctgCell01 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 name Enter jms/maximo/int/cf/intcf. Bus name Select intjmsbus. 6. Click Save.

Creating the continuous inbound (CQIN) JMS queue

You must create a JMS queue (CQIN) as the destination for continuous inbound point-to-point messages. 1. From the WebSphere Administrative Console, click Resources > JMS > Queues. 2. From the Scope drop-down list, select Cell=ctgCell01. 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.
Chapter 5. Tivoli Asset Management for IT installation program overview

117

JNDI name Enter jms/maximo/int/queues/cqin Bus name Select intjmsbus. Queue name Select CQINBD. 6. Click OK. 7. Click Save.

Creating the sequential inbound (SQIN) JMS queue

You must create a JMS queue (SQIN) as the destination for sequential inbound point-to-point messages. 1. From the WebSphere Administrative Console, click Resources > JMS > Queues. 2. From the Scope drop-down list, select Cell=ctgCell01. 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 SQIN. Note this value must only contain uppercase letters. JNDI name Enter jms/maximo/int/queues/sqin Bus name Select intjmsbus. Queue name Select SQINBD. 6. Click OK. 7. Click Save.

Creating the sequential outbound (SQOUT) JMS queue

You must create a JMS queue (SQOUT) as the destination for sequential outbound point-to-point messages. 1. From the WebSphere Administrative Console, click Resources > JMS > Queues. 2. From the Scope drop-down list, select Cell=ctgCell01. 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 SQOUT. Note this value must only contain uppercase letters. JNDI name Enter jms/maximo/int/queues/sqout Bus name Select intjmsbus. Queue name Select sqoutbd. 6. Click OK.

118

Installation Guide for IBM WebSphere Application Server:

7. Click Save.

Creating JMS activation specification for the continuous inbound queue (CQIN)
You must activate the continuous inbound queue (CQIN) before it can receive messages. Complete the following steps to activate the CQIN queue: 1. From the WebSphere Administrative Console, click Resources JMS Activation Specifications. 2. From the Scope drop-down list, select Cell=ctgCell01. 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 name intjmsact Destination type Queue Destination JNDI name jms/maximo/int/queues/cqin Bus name intjmsbus Maximum concurrent endpoints 10 6. 7. 8. 9. Click Save. Ensure to stop all IBM-related processes and daemons. You must now restart these processes for the update to take effect. 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.

Error queues
You can create an optional error queue that will receive redirected messages from the continuous queue (cqin) when the messages go in error.

Creating the service integration bus destination for the inbound error queue (CQINERRBD) queue
To add a logical address for the inbound error queue (CQINERRBD) queue within the JMS bus, complete the following steps: 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. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box.

Chapter 5. Tivoli Asset Management for IT installation program overview

119

4. 5. 6.

7. 8. 9. 10.

11. 12.

A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. Click New to open the Create new destination dialog box. Leave Queue checked as the destination type, and click Next to open the Create new queue dialog box. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the Description field, then click Next to open the Create a new queue for point-to-point messaging dialog box. Note that you must use this value and it must contain only uppercase letters. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer Click Next to open the Confirm queue creation dialog box. Review your selections, then click Finish to complete the creation of the CQINERRBD bus destination queue. Navigate the path Buses > intjmsbus > Destinations, then click CQINERRBD to open the configuration dialog box where you must make the following changes: v Click Specify and enter CQINERRBD as the exception destination value. v Change the Maximum failed deliveries value to 5. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. Click Apply. Click Save.

13. From the WebSphere Administrative Console, click Service Integration > Buses to open the Buses dialog box. 14. Click intjmsbus to open the Buses > intjmsbus dialog box. 15. Select CQINBD. 16. Specify CQINERRBD as the exception destination. . Set the Maximum failed deliveries value to 5. 17. Click OK. 18. Click Save.

Creating the error (CQINERR) JMS queue

After creating the Error Queue Bus Destination, you create the Error queue. 1. From the WebSphere Administrative Console, click Resources JMS Queues. 2. From the Scope drop-down list, select Cell=ctgCell01. 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 CQINERR. Note this value must only contain uppercase letters. JNDI name Enter jms/maximo/int/queues/cqinerr Bus name Select intjmsbus.

120

Installation Guide for IBM WebSphere Application Server:

Queue name Select CQINERR. 6. Click OK. 7. Click Save.

Creating JMS activation specification for the inbound error queue (CQINERR)
You must activate the continuous inbound queue (CQINERR) before it can receive messages. Complete the following steps to activate the CQINERR queue: 1. From the WebSphere Administrative Console, click Resources JMS Activation Specifications. 2. From the Scope drop-down list, select Cell=ctgCell01. 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 name Enter intjmsacterr Destination type Enter Queue. Destination JNDI name jms/maximo/int/queues/cqinerr. 6. Click OK. 7. Click Save.

Manually creating a datasource for the persistence store

You have the option of having WebSphere use a DB2 database to store JMS messages. For more information about WebSphere message 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 If you chose to manually configure WebSphere, you will need to create a datasource in order to store JMS messages in a DB2 database. To create a datasource for the persistence store, complete the following steps: 1. Create a system user and password on the machine hosting the database server. 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.

Chapter 5. Tivoli Asset Management for IT installation program overview

121

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 with the exception of Security administrator authority. i. Click Apply. j. 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. a. Open and login to the WebSphere Administrative Console. b. Navigate to Security Secure administration, applications, and infrastructure. c. Under the Authentication header, click on Java Authentication and Authorization Service J2C authentication data. d. Click New. e. Complete the following fields in the User identity form. Alias maxJaasAlias

User ID mxsibusr Password Password you created for mxsibusr. Description SIB database user alias. f. Click Apply, and then click Save. g. From the WebSphere Administrative Console navigation pane, navigate to Resources JDBC JDBC Providers. h. Click Scope and then select Cell=ctgCell01. i. Click New. j. Specify the following values: Database type DB2 Provider type DB2 Universal JDBC Driver Provider Implementation type XA data source Name maxJdbcProvider k. Click Next. l. Fill in the WebSphere variable ${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of <WAS_HOME>ctgMX\lib. For example, C:\Program Files\IBM\WebSphere\AppServer\ctgMX\lib. m. Click Next. n. Click Finish. o. Click Save.

122

Installation Guide for IBM WebSphere Application Server:

4. Open a command prompt and copy <DB2_HOME>/java/db2jcc.jar and <DB2_HOME>/java/db2jcc_license_cu.jar to the <WAS_HOME>\ctgMX\lib directory. Go back to Resources JDBC JDBC Providers maxJdbcProvider, and correct the Class path if required for both db2jcc.jar and db2jcc_license_cu.jar. Ensure that each jar file has the full path from ${DB2UNIVERSAL_JDBC_DRIVER_PATH} 5. Configure WebSphere: 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 name intjmsds JNDI name jdbc/intjmsds e. From the Component-managed authentication alias and XA recovery authentication 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 name maxsibdb Driver type 4 Server name Specify the DB2 server host name. Port number Specify 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. l. Click Save. 6. Verify the datasource by selecting intjmsds, and then clicking Test Connection.

Installing Tivoli Asset Management for IT without middleware autoconfiguration

This procedure will instruct you on installing Tivoli Asset Management for IT and choosing to not have the Tivoli Asset Management for IT installation program autoconfigure the Tivoli Asset Management for IT middleware servers. You might elect to not have the Tivoli Asset Management for IT installation program autoconfigure Tivoli Asset Management for IT middleware if your organization has specific policies and procedures that govern how you create databases, database instances, users, and so on, within your organization.

Chapter 5. Tivoli Asset Management for IT installation program overview

123

If you intend to use DB2 on UNIX systems with Tivoli Asset Management for IT, you must add root to the DB2GRP1 group prior to starting the Tivoli Asset Management for IT installation program. To install Tivoli Asset Management for IT, follow these steps: 1. Login to the Tivoli Asset Management for IT administrative workstation as Administrator. 2. Launch the Tivoli Asset Management for IT installation program from the launchpad. a. Start the launchpad: v On the DVD titled Tivoli Asset Management for IT V7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.exe. b. In the launchpad navigation pane, click Install the Product. c. Click Tivoli Asset Management for IT. Alternatively, you can launch the Tivoli Asset Management for IT installation program directly. On the DVD titled Tivoli Asset Management for IT V7.1, navigate to \Maximo\, and run the following command: install.exe. 3. Select a language for the installation and click OK. 4. From the Introduction panel, click Next. 5. From the Import Middleware Configuration Information panel, specify that you want to use field values you input into the Tivoli middleware installer as default values for those same fields in the Tivoli Asset Management for IT installation program. Import Middleware Configuration Information Select this check box if you want to allow the Tivoli Asset Management for IT installation program to reuse values entered in the Tivoli middleware installer. The middleware default information will not be used if you select the Simple deployment path. Host name Enter the host name of the system where the Tivoli middleware installer was run. User ID Enter the User ID that was used to run the Tivoli middleware installer. Password Enter the password of the User ID that was used to run the Tivoli middleware installer. Workspace Location Enter the location of the topology file that contains the values entered for the Tivoli middleware installer. This file is found in the workspace that was defined during the Tivoli Asset Management for IT middleware installation task. For example, C:\ibm\tivoli\mwi\ workspace. 6. From the Choose Deployment panel, select the Custom deployment topology, and then click Next. Simple Select simple if you want to deploy all Tivoli Asset Management for IT components on a single system. This deployment option is typically only used for demonstration, proof-of-concept, or training purposes.

124

Installation Guide for IBM WebSphere Application Server:

Custom Select custom if you want to deploy Tivoli Asset Management for IT components across several systems. This deployment option is typically used in a production environment. 7. From the Choose Install Folder panel, specify the directory you will use to install Tivoli Asset Management for IT, and then click Next. Where Would You Like to Install? Enter the path to install Tivoli Asset Management for IT. By default, this value is C:\IBM\SMP. The path you specify must not contain spaces. 8. From the Maximo Database Type panel, select the product that you will be using for the maximo database, and then click Next. DB2 Select this choice to use IBM DB2 UDB as the Maximo database.

Oracle Select this choice to use Oracle as the Maximo database. SQL Server Select this choice to use MS SQL Server 2005 as the Maximo database. Each database will have its own unique set of configurable parameters and values. 9. From the Maximo Database panel, enter configuration information about the database, and then click Next. DB2 Host name Enter the host name of the machine hosting DB2. The host name must be fully qualified. Port Enter the port being used by DB2 instance. The default is 50005 Database Name Enter the name of the database to use with Maximo. The default database name is maxdb71. The database will be created if it does not already exist. Instance Enter the name of the database instance to be used with Maximo. The default instance name is ctginst1. This instance will be created if it does not already exist, however, the user and its associated home directory must already exist on the DB2 server. Database User ID Enter the user ID used for Maximo to access DB2. Default for all platforms is maximo. This user ID will be created if it does not already exist. This user ID cannot be the same one used as the instance administrator user ID. Database Password Enter the password for the user ID used to access DB2.
Chapter 5. Tivoli Asset Management for IT installation program overview

125

Oracle Host name Enter the host name of the machine hosting Oracle. The host name must be fully qualified. Port Enter the port being used by Oracle. The default is 1521 Instance Enter the name of the database instance to be used with Maximo. The default instance name is ctginst1. Database User ID Enter the user ID used for Maximo to access Oracle. Default for all platforms is maximo. This user ID will be created if it does not already exist. Database Password Enter the password for the user ID used to access Oracle. SQL Server Host name Enter the host name of the machine hosting SQL Server. The host name must be fully qualified. Port Enter the port being used by SQL Server. The default is 1433 Database Name Enter the name of the database to use with Maximo. The default database name is maxdb71. User ID Enter the user ID used to access SQL Server. Default for all platforms is maximo. This user ID will be created if it does not already exist. Password Enter the password for the user ID used to access SQL Server. After you have entered configuration information for the database that was selected, the Tivoli Asset Management for IT installation program will connect to the database server to validate the information you have entered. 10. From the Automate Database Configuration panel, select Do not automate database configuration, and then click Next. Note that this step assumes you have already created a database instance, a database, tablespaces, a user, and schema for use with Tivoli Asset Management for IT. Refer to Manually configuring the database server on page 86. If you have not manually configured the database prior to selecting Do not automate database configuration from within the Tivoli Asset Management for IT installation program, the installation will verify that you have not completed these pre-install tasks and you will be reminded to complete them prior to restarting the Tivoli Asset Management for IT installation program.

126

Installation Guide for IBM WebSphere Application Server:

11. Once the database validation task has completed, from the WebSphere Connectivity panel, enter host information about the WebSphere server, and then click Next. Host name Enter the fully-qualified host name of the system hosting WebSphere. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere system. The default value for this field is 8879. 12. From the Remote Access Authorization panel, enter authorization information for WebSphere configuration, and then click Next. Operating system user ID Enter a valid user ID that will allow the Tivoli Asset Management for IT installation program to access the system that is hosting WebSphere. This user ID should have administrative rights on the machine you are accessing. Operating system password Enter the password for the system user ID. 13. From the Automate WebSphere configuration panel, select Do not automate WebSphere configuration, and then click Next. Remember that in choosing not to have the Tivoli Asset Management for IT installation program automatically configure middleware, you will have had to configure WebSphere manually prior to the installation of Tivoli Asset Management for IT. Configuration tasks include creating a profile, running WebSphere as a Windows service, copying the WebSphere keystore file from the machine where WebSphere is installed to the administrative workstation, setting up JMS queues, and so on. 14. From the WebSphere Deployment Manager configuration panel, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere is installed on the host system. Windows On Windows, this value might be C:\Program Files\IBM\WebSphere\AppServer Linux On Linux, this value might be /opt/IBM/WebSphere/ AppServer AIX HP-UX On HP-UX, this value might be /opt/IBM/WebSphere/ AppServer Sun Solaris On Sun Solaris, this value might be /opt/IBM/WebSphere/ AppServer User ID Enter the administrative user ID used to access the WebSphere server. On AIX, this value might be /usr/IBM/WebSphere/ AppServer

Chapter 5. Tivoli Asset Management for IT installation program overview

127

Default for all platforms is wasadmin. Password Enter the password for the administrative user ID used to access the WebSphere server. Profile name Enter the name of the WebSphere profile. Default for all platforms is ctgDmgr01. 15. From the WebSphere Application Server Configuration panel, enter the following information, and then click Next. Web server port Enter the Web server port used by WebSphere. Default for all platforms is 80 Web server name Enter the name of the Web server. Default for all platforms is webserver1 Node name Enter the name of the WebSphere node containing the application server. Default for all platforms is ctgNode01. Cluster name Enter the name of the WebSphere cluster containing the application server. Default for all platforms is MAXIMOCLUSTER. The cluster name is optional. The cluster and application server will be created if they do not exist. 16. From the Security panel, indicate application server security should not be enabled automatically, and then click Next. Youll be prompted to manually configure security. Use the default schema. Leave this option selected. Selecting this option indicates that WebSphere Virtual Member Manager (VMM) has been configured using the default schema supplied with Tivoli Asset Management for IT with a default VMM base entry, ou=swg,o=IBM,c=us. If you have elected to supply your own schema for use with VMM, you should deselect this option. You will be required to manually configure VMM to work with your custom schema and also manually configure the VMM synchronization crontask. Create the required users. Leave this option selected. Selecting this option indicates that you wish to have Tivoli Asset Management for IT default users created automatically by the Tivoli Asset Management for IT installation program. You will need write access to VMM.

128

Installation Guide for IBM WebSphere Application Server:

If you have elected to create users manually, you should deselect this option. Users must be created prior to advancing past the Security panel. Here is an example of the default add on ldif data you would have to modify and import into your LDAP repository if you elected to customize the schema and create your own users manually.
dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm,ou=users,ou=SWG, o=ibm,c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg,ou=users,ou=SWG, o=ibm,c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg dn: cn=maxadmin,ou=groups,ou=SWG, o=ibm,c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=maxadmin,ou=users,ou=SWG,o=IBM,c=US member: uid=mxintadm,ou=users,ou=SWG,o=IBM,c=US cn: maxadmin dn: cn=maximousers,ou=groups,ou=SWG, o=ibm,c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=mxintadm,ou=users,ou=SWG,o=IBM,c=US member: uid=maxreg,ou=users,ou=SWG,o=IBM,c=US member: uid=maxadmin,ou=users,ou=SWG,o=IBM,c=US cn: maximousers

Refer to Synchronizing data on page 156 for synchronization tasks you will have to complete post installation if you choose to customize your schema. 17. From the Integration Adapter JMS Configuration panel, enter the following information, and then click Next. JMS DataSource name A JMS server requires a DB2 data repository to be configured to maintain messages. Enter the name of the database to be used by JMS. Default is intjmsds. Select whether the JMS datastore should be persisted.
Chapter 5. Tivoli Asset Management for IT installation program overview

129

Persist JMS messages Select this option of you want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages. Refer to Manually creating a datasource for the persistence store on page 121 for more information. Do not persist JMS messages Select this option if you do not want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages automatically. If you later decide that you would like to persist JMS messages, you will have to configure the JMS implementation manually. The next several steps of this Tivoli Asset Management for IT installation procedure assumes you are allowing the Tivoli Asset Management for IT installation program to configure the JMS implementation to persist messages. 18. From the DB2 Database Server Configuration panel, enter the following information, and then click Next. Note: The JMS DataStore can only be created as a DB2 database. Host name Enter the fully qualified host name of the server hosting the JMS datastore. Port Enter the port used to access the database server. Default for all platforms is 50000. Database name Enter the name of the database serving as the JMS datastore. Default for all platforms is maxsibdb. User ID Enter the user ID used to access the database server. Default for all platforms is mxsibusr. Password Enter the password for the User ID used to access the database server. 19. From the WebSphere keystore file panel, navigate to where you copied the trust.p12 keystore, and then click Next. 20. From the Maximo panel, enter the following configuration information, and then click Next. Select the installation folder Select the folder where Maximo will be installed. C:\IBM\maximo is the default value. The path you specify must not contain spaces. SMTP server Enter the mail server configured to work with Tivoli Asset Management for IT. This server will be used to send workflow and process notifications. This field can be left blank.

130

Installation Guide for IBM WebSphere Application Server:

Workflow Admin E-Mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Workflow Administrator. This address will be used for workflow notifications. This field can be left blank. Admin E-Mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Administrator This field is optional. If you choose to not configure optional properties at this time, you can configure them in the Tivoli Asset Management for IT user interface using the System Properties application. The relevant properties are: v mail.smtp.host v mxe.workflow.admin v mxe.adminEmail 21. From the Run Configuration Step panel, select when you would like to configure Tivoli Asset Management for IT, and then click Next. Run the configuration step now Tivoli Asset Management for IT will be configured when you select this option and press Next. Do not run the configuration step now You will have to configure Tivoli Asset Management for IT after you have completed the Tivoli Asset Management for IT installation task. The Tivoli Asset Management for IT installation program is used to complete three tasks: gathering information about your Tivoli Asset Management for IT deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting Do not run the configuration steps now, you can instruct the Tivoli Asset Management for IT installation program to gather your configuration information and copy Tivoli Asset Management for IT files to your local system now, and then allow you to run the configuration step at a later date. The configuration values that you enter are stored in the <Maximo_Home>\applications\maximo\properties\ maximo.properties file. You can execute the configuration steps outside of the Tivoli Asset Management for IT installation program by using the taskrunner utility, located in the <TAMIT_HOME>\scripts directory. Simply run the taskrunner utility from the command line, and it will use the configuration values stored in the maximo.properties file to configure Tivoli Asset Management for IT.
<TAMIT_HOME>\scripts\taskrunner

In the event of an installation failure, the taskrunner utility can be run again after the error conditions have been rectified. The taskrunner utility will resume the install at the point where the last successfully completed task was recorded in the previous attempt. 22. From the Choose Shortcut Folder panel, select the type of shortcut you would like to arrange for Tivoli Asset Management for IT, and then click Next.

Chapter 5. Tivoli Asset Management for IT installation program overview

131

In a new Program Group Select this option and enter the name of a new program group if you would like to create Tivoli Asset Management for IT shortcuts in a new program group. In an existing Program Group Select this option and choose the name of an existing program group to store Tivoli Asset Management for IT shortcuts. In the Start Menu Select this option to create shortcuts for Tivoli Asset Management for IT in the Start menu. In order to use the Start Menu shortcut in conjunction with Internet Explorer, ensure that you have added the Tivoli Asset Management for IT URL to the trusted sites Web content zone and disable the option of requiring server verification for all sites in the zone. On the Desktop Select this option to create shortcuts for Tivoli Asset Management for IT on the desktop. In the Quick Launch Bar This option should not be used. Do not select this option. Selecting this option will not create a shortcut in the Quick Launch bar. Other Select this option and use the Choose... button to select another location to create Tivoli Asset Management for IT shortcuts. Dont create icons Select this option if you do not want any Tivoli Asset Management for IT shortcuts created. Create Icons for All Users Select this option if you would like Tivoli Asset Management for IT desktop icons to appear on the desktop for all system users. 23. From the Input Summary panel, review the information you have provided to the Tivoli Asset Management for IT installation program, and then click Next. Use the Previous button to return to previous panels to make any changes. 24. From the Pre-Installation Summary panel, review the installation information presented, and then click Install. The installation task will begin. Progress can be monitored by viewing messages displayed above the progress bar. 25. From the Install Complete panel, click Done. Once the Tivoli Asset Management for IT installation program has completed installation and configuration tasks, it will exit. Logs can be found at <TAMIT_Home>/logs.

Manually configuring the VMMSYNC cron task for Microsoft Active Directory
This topic details how to manually configure the VMMSYNC cron task for Microsoft Active Directory. VMMSYNC is the cron task that schedules the synchronization between Tivoli Asset Management for IT and the LDAP repository and is configured through the Maximo Console. This procedure is required if you use Microsoft Active Directory

132

Installation Guide for IBM WebSphere Application Server:

as your directory server. For more general information about configuring the VMMSYNC cron task, refer to Synchronizing data on page 156. The steps below detail how to reconfigure the VMMSYNC cron task for use with Microsoft Active Directory. To modify the VMMSYNC cron task for Microsoft Active Directory, complete the following steps: 1. Log into the Maximo console as maxadmin. 2. Navigate to the Cron Task Setup application by selecting Go To > System Configuration > Platform Configuration > Cron Task Setup. 3. Click the VMMSYNC cron task and configure the following values: Active? Enable the Active? option by selecting the checkbox. Credential Password for wasadmin in LDAP GroupMapping Edit the <basedn> entry of the XML file.
<basedn>ou=Groups,ou=SWG,dc=itsm,dc=com</basedn>

GroupSearchAttribute cn Principal cn=wasadmin,ou=Users,ou=SWG,dc=itsm,dc=com SynchAdapter psdi.security.vmm.DefaultVMMSyncAdapter SynchClass psdi.security.vmm.VMMSynchronizer UserMapping Edit the <basedn> entry of the XML file.
<basedn>ou=Users,ou=SWG,dc=itsm,dc=com</basedn>

UserSearchAttribute Uid You will have to click the arrow located in the header of the Cron Task Parameters table to view all parameters. 4. Click the save icon. The updated parameters will be used at the next scheduled synchronization.

Chapter 5. Tivoli Asset Management for IT installation program overview

133

134

Installation Guide for IBM WebSphere Application Server:

Chapter 6. IBM Agent Controller overview

The IBM Agent Controller (AC) imports log and trace information from remote systems to the IBM Log and Trace Analyzer application. In order to import log and trace data, the IBM Agent Controller must be installed and running on every server from which you wish to retrieve log file information using the log and trace analyzer. The IBM Tivoli middleware installer installs the Agent Controller during the installation of the following: v IBM Tivoli Directory Server v WebSphere Application Server v DB2 In some circumstances you must manually invoke the IBM Agent Controller installation program using the launchpad application. For instance, if you are using another supported software like Oracle, Microsoft Active Directory, Microsoft SQL, or if your product has its own log parser, then IBM Agent Controller has to be manually installed on that remote location in order to import log and trace data. This is also the case if you have a previous version of an Agent Controller installed. If you have a previous version, the installation program prompts you to uninstall that version and invoke a manual install of the latest IBM Agent Controller. Summary of situations requiring a manual installation of the IBM Agent Controller v Using another supported software v That software has its own log parser v You have a previous version of IBM Agent Controller installed already For more information about invoking the launchpad see, Installing the IBM Agent Controller and the list of supported platforms.

IBM Agent Controller supported platforms

This topic supplies a list of the supported platforms for installing IBM Agent Controller. You can install IBM Agent Controller on the following supported platforms: v AIX v5.2, v5.3, and 5L on PowerPC (32-bit) v z/OS V1R4, V1R5, V1R6 and V1R7 on zSeries (32-bit) v OS/400 V5R2, V5R3 and V5R4 on iSeries Linux 2.4 and 2.6 kernel. Examples of supported distributions include: v Red Hat Linux Advanced Server v2.1 on Intel IA32 v Red Hat Enterprise Linux AS release 3 on PowerPC (64-bit) v Red Hat Enterprise Linux (RHEL) v3.0 and v4.0 v SuSE Linux Enterprise Server (SLES) v9 on Intel IA32 v SuSE Linux Enterprise Server (SLES) v8 on zSeries (32-bit) v Windows 2000 Server or Advanced Server (SP4) on Intel IA32
Copyright IBM Corp. 2007, 2008

135

v v v v v v

Windows 2000 Professional (SP3) on Intel IA32 Windows Server 2003 Standard and Enterprise (SP1) on Intel IA32 Windows Server 2003 Enterprise x64 Edition (SP1) on EM64T (64-bit) Windows XP Professional (SP2) on Intel IA32 HP-UX v11.0, v11i on PA-RISC Sun Solaris v8, v9, and v10.0 on SPARC

Planning for serviceability

Serviceability refers to problem analysis from a central point using data collected from a wide range of sources. You can customize the serviceability provided by Tivoli Asset Management for IT by choosing where to deploy instances of the IBM Agent Controller which work with the Log and Trace Analyzer hosted on the IBM WebSphere Network Deployment manager. IBM Agent Controller gathers information from log files residing on remote servers and passes it on to the Log and Trace Analyzer. By default, the IBM Agent Controller agent is installed on machines where you have run the Tivoli middleware installer, which includes the application server, the directory server, and the database server. You can choose to install IBM Agent Controllers on other resources, such as Operational Management Products (OMPs), or other nodes located on the IBM WebSphere Network Deployment cluster, from which you want to retrieve log files.

IBM Agent Controller TADDM Log and Trace Analyzer IBM Agent Controller WebSphere Application Server Node WebSphere Deployment Manager

IBM Agent Controller Database

IBM Agent Controller Directory Server

IBM Agent Controller WebSphere Application Server Node

IBM Agent Controller Operational Management Product

Figure 4. Tivoli Asset Management for IT Serviceability

Log files for the Tivoli middleware installer can be found in the workspace directory you defined when you ran the installation program.Log files for the Tivoli Asset Management for IT installation program can be found in <TAMIT_HOME>\logs. After installation, during normal usage of Tivoli Asset

136

Installation Guide for IBM WebSphere Application Server:

Management for IT, you might find it useful to examine the application server logs generated for the MXServer application server.

Installing IBM Agent Controller

Installing the IBM Agent Controller allows you to import log and trace information from remote systems and view the information using the Log and Trace Analyzer. Before installing the Agent Controller, if you have a previous version of the Agent Controller installed, you must uninstall the previous version. 1. Locate the installation files. The Agent Controller installation files are located in the Rational-AgentController_7.0.3.1 directory on the Tivoli Asset Management for IT 7.1 DVD. The following list identifies the installation files in the directory:
For platform Windows on Intel IA32 Windows on EM64 AIX Linux on Intel IA32 Installation files ibmrac.win_ia32_V7.0.3.1.zip ibmrac.win_em64t_V7.0.3.1.zip ibmrac.aix_powerpc_V7.0.3.1.zip ibmrac.linux_ia32_V7.0.3.1.zip

2. Extract the installation files to the following directories:

For platform Windows on Intel IA32 Windows on EM64 AIX Linux on Intel IA32 Directories <temp_dir>\win_ia32 <temp_dir>\win_em64t <temp_dir>/aix_powerpc <temp_dir>/linux_ia32

3. Log in. On Windows operating systems, use a Windows logon ID with Administrator authority. On Linux and AIX systems, use the root ID. 4. Close all Eclipse platforms. 5. Change the directory to the directory where you unzipped the installation files for the appropriate operating system. 6. Start the installation program by running setup.exe (Windows) or setup.bin (Linux and AIX) A welcome page is displayed. 7. Click Next. 8. On the license agreement page, read the terms of the license agreement and, if you agree with the terms, click I accept the terms of the license agreement and click Next. You must accept the terms of the license agreement to continue the installation. 9. Type or browse to the location where the Agent Controller should be installed and click Next. 10. On the Select the version of WebSphere Application Server page, click V6.0 or later and click Next. 11. On the Access List page, specify which hosts can access the Agent Controller. The following list identifies the options:
Option This computer only Description Allows only the local host to access the Agent Controller.
Chapter 6. IBM Agent Controller overview

137

Option Specific computers Any computer

Description Allows a specified list of clients to access the Agent Controller. Allows any client to access the Agent Controller. This option is the default. Note: If you use an authentication mechanism, for example, LDAP, selecting the Any computer option requires that you disable the Agent Controller user authentication after the installation process is complete. Refer to the Agent Controller documentation for instructions to complete this task.

12. On the Security page, specify the security setting. If you selected Any computer in the previous step, security is enabled. To disable security, refer to the Agent Controller documentation. If security is disabled, communication are not encrypted and access control is limited to the defined host list. If you selected the other options on the Access List page, security is enabled by default but changeable. Click Next. 13. If security is enabled, on the Security page, type a comma-separated list of users that can connect to the Agent Controller. These user are required to authenticate to use the tool. Click Next. 14. Review the summary information and click Install. 15. Click Finish to close the installation program.

Starting IBM Agent Controller

On Windows operating systems, the Agent Controller system service is started automatically. On Linux and AIX operating systems the Agent Controller must be started manually. To start the Agent Controller on a Linux or AIX operating system, complete the following steps: 1. Set the appropriate environment settings.
For platform Linux Installation files The Agent Controller server requires the directories of the JRE that contain executable libraries, such as libjvm.so, to be added to the library path environment variable. The following example shows the path variable setting based on default installation locations of the JVMs supported for the Linux platform. You must enter a path that matches the path for the JRE you specify when you installed the Agent Controller. The JRE you specify is used by the Agent Controller for launching Java applications. LD_LIBRARY_PATH=/opt/IBMJava2-141/jre /bin/classic:/opt/IBMJava2-141/jre/bin: $LD_LIBRARY_PATH export LD_LIBRARY_PATH

138

Installation Guide for IBM WebSphere Application Server:

For platform AIX

Installation files For certain JVMs, the LDR_CNTRL environment variable needs to be set to USERREGS to work properly with the Agent Controller. To set this variable, run the following command before running the RAStart.sh script: export LDR_CNTRL=USERREGS In addition, the Agent Controller server requires the directories of the JRE that contain executable libraries, such as libjvm.so, to be added to the library path environment variable. The following example shows the path variable setting based on default installation locations of the JVMs supported for the AIX platform. You must enter a path that matches the path for the JRE you specify when you installed the Agent Controller. The JRE you specify is used by the Agent Controller for launching Java applications. LIBPATH=/usr/java14/jre/bin:/usr/java14 /jre/bin/classic: $LIBPATH export LIBPATH

2. Change to the installation location bin directory and run the following command:./RAStart.sh To stop the Agent Controller process, do the following: v On Linux or AIX systems, change to the installation location bin directory and run the following command: ./RAStop.sh v On Windows system, use the Windows Services dialog, which is part of the Control Panel, and stop IBM Rational Agent Controller.

Chapter 6. IBM Agent Controller overview

139

140

Installation Guide for IBM WebSphere Application Server:

Chapter 7. Process solution package installation

These topics provide information about installation of packaged process solution. Process solutions can be partitioned into Process Manager Products and Integration Modules. Process solution packages can be installed and deployed through the process solution installation (PSI) wizard, accessible from the launchpad.

Process solution packages

A process solution package is a self-contained ZIP file of installation artifacts and deployment logic that can be deployed using the process solution installation program. Installation artifacts are the files and content that are installed into your Tivoli Asset Management for IT environment to enable the services management functionality of the Process Manager Product or Integration Module. The deployment logic are the actions that are carried out in order to deploy the process solution into the Tivoli Asset Management for IT environment. Typically, these actions include building and deploying J2EE applications, running database scripts that load the process solution content into the Maximo database, and adding users and groups for security. Additionally, optional sample data can be installed. Note: Separately deploying a process solution package is only needed if you run the PSI install outside the launchpad, for instance, when you install directly from the product DVD.

Before using the process solution installation program

When you perform a deployment operation using the process solution installation program, you are running actions that modify the configuration and content of your J2EE, database, and directory middleware servers. Review the following steps before invoking the process solution installation program. Have Middleware Login Information Available The process solution installation program requires access to middleware servers in order to automate the deployment of the process solution package. You must know the administrative user IDs and passwords for the impacted middleware servers. The actual middleware servers whose login information is required depend on the process solution package being installed. The process solution installation program ensures that any required login information is specified before continuing with the deployment operation. Backup Middleware Servers and Administrative Workstation Create backups for impacted J2EE, database, and directory servers before you deploy a process solution package using the process solution installation program.

Copyright IBM Corp. 2007, 2008

141

Ensure Middleware Servers Are Started Start any impacted middleware servers before running the process solution installation programs Before the actions associated with a package are executed, the process solution installation programs attempt to connect to the middleware servers using the middleware login information that you specify. If the targeted middleware servers are not started or if connections to the middleware servers cannot be established with the specified middleware login information, the process solution installation programs display error messages and do not continue on with the deployment actions.

Installing process managers using the process solution installation wizard

Complete the following steps to install a process solution package into Tivoli Asset Management for IT using the process solution installation wizard: 1. From the Launchpad, launch the process solution installation program by clicking the link under 3. Enable Tivoli Asset Management for IT License for usage. The Process Solution Installation Install Anywhere Installer executes on the Maximo administrative workstation. The launch script is deployed and configured by the Tivoli Asset Management for IT installation program. No post-installation configuration is required. 2. Select a language for your installation, and then click OK. In this case, the PSI package selected is a base install of the Tivoli Asset Management for IT 7.1 package. The process solution installation program performs a series of validation checks to verify that the package you selected is valid. The system is checked to insure that the package has not already been deployed. 3. From the Package Validation Results panel, review and verify the information displayed, and then click Next. 4. The process solution installation program license agreement window is displayed. Read the license information and select I accept the terms in the license agreement if you agree with the terms. Click Next. 5. From the Middleware Login Information panel, enter the credentials for which you are being prompted, and then click Next. Once you have entered the requested user IDs and passwords, the process solution installation wizard validates the credentials by connecting to the middleware servers using the supplied credentials. 6. After the credentials have been verified, a package options panel is displayed that details the deployment options that the package supports. Leave the Package Options box unchecked to have the EAR files redeployed and Maximo database updated by the process solution installation program and click Next. The process solution installation program then performs a system check to ensure that all system requirements necessary for the package to be installed are present. Click Next to advance. 7. From the Pre-Install Summary panel, review and verify the information displayed, and then click Next. At this point, the process solution installation program begins the package installation process. A progress panel will inform you of the deployment progress of the installation.

142

Installation Guide for IBM WebSphere Application Server:

8. When the installation has completed successfully, from the Package Successfully Deployed panel, click Done to exit the process solution installation wizard. If there is a package failure, a message is displayed for the step that failed. In some cases, you see an installation progress bar displayed briefly after you click Done. The Process Solution Installation Wizard is actually terminating and no installation activities are being performed. The deployment of the Process Solution Package you were installing has already completed and the progress bar can be safely ignored.

Process solution installation logs

If you experience any problems or encounter any error messages during the use of the process solution installation program, refer to the log files kept in the following locations:
Table 21. Log type Package log Description Location

These are log files containing <TAMIT_HOME>\solutions\ the StdOut/StdErr output of logs\<PACKAGE_NAME>\ external commands launched by the package as it is processed by the Deployment Engine. These log files are typically vital to the proper debugging of package issues. In general, logs will have two parts, a .out and .err file, both with the same pre-extension filename. .out files contain the contents of the Standard Output stream as output by the external command. .err files contain the contents of the Standard Error stream. It is normal for one to be blank, provided there was no error output (or there was ONLY error output). Note that you might discover numerous (10-20) package log files generated for any particular package installed.

Chapter 7. Process solution package installation

143

Table 21. (continued) Log type Solution Install/Deployment Engine Logs Description These are logs kept by the IBM Solution Installer/Deployment engine runtime. PSI utilizes the IBM technology as the means to install and keep track of installed packages. This runtime has its own logging system. Location C:\Program Files\IBM\Common\acsi\ logs\<USERNAME>\ de_msg.log C:\Program Files\IBM\Common\acsi\ logs\<USERNAME>\ de_trace.log So for instance, if you installed under the user name Administrator, the logs would be found under: C:\Program Files\IBM\Common\acsi\ logs\Administrator\ de_msg.log WebSphere Application Server Logs These are logs kept of connections, exceptions, and other failures experienced by the WebSphere Application Server in its day-to-day running. These logs are often helpful in the diagnosis of errors in particular EAR files or other back-end operations, such as database connections. <WAS_HOME>\profiles\ <PROFILE>\logs\ AboutThisProfile.txt <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ startServer.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ stopServer.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ SystemErr.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ SystemOut.log So for instance, if your WebSphere Application Server was installed in C:\IBM\WebSphere\ AppServer\, your profile name was AppSrv01, and your server name was server1, you would provide the following logs:: C:\IBM\WebSphere\ AppServer\profiles\ AppSrv01\logs\ AboutThisProfile.txt

144

Installation Guide for IBM WebSphere Application Server:

Table 21. (continued) Log type Description Location <TAMIT_HOME>\maximo\ tools\maximo\log\ updatedb<TIMESTAMP>.log So if your Tivoli Asset Management for IT install location was C:\IBM\SMP, and the package executed the UpdateDB command on April 19th at approximately 5:06:07PM, the logging information would be written to the file: C:\IBM\SMP\maximo\ tools\maximo\log\ updatedb20070419170607.log <TAMIT_HOME>\ wasclient\logs\ CTGIN_wsadmin.traceout <TAMIT_HOME>\ wasclient\logs\ wsadmin.traceout <TAMIT_HOME>\ wasclient\logs\ wsadmin.valout So if your Tivoli Asset Management for IT install location were C:\IBM\SMP, the following log files would contain the Thin WAS Client tracing information: C:\IBM\SMP\wasclient\ logs\ CTGIN_wsadmin.traceout C:\IBM\SMP\wasclient\ logs\wsadmin.traceout C:\IBM\SMP\wasclient\ logs\wsadmin.valout

Tivoli Asset Management for There are also a few logs IT Logs kept by Tivoli Asset Management for IT. These are useful in tracking the progress, success, and failure of a few back-end commands provided by Tivoli Asset Management for IT.

WAS Thin Client Logs

The WAS thin client is the mechanism by which the process manager packages communicate with the WebSphere Application Server. If this automated deployment happens to fail, the exact actions the Thin Client took and the associated responses from the WebSphere Application Server are stored in logs.

It is a good practice to rename existing logs before attempting a package install. It is useful to have a log comprised of only the information related to the success or failure of current package installation to facilitate problem determination.

Chapter 7. Process solution package installation

145

146

Installation Guide for IBM WebSphere Application Server:

Chapter 8. Integration Composer installation

The IBM Tivoli Asset Management for IT Launchpad can be used as an interface for installing Integration Composer, or the separate Integration Composer DVD can be used to install it. IBM Tivoli Integration Composer must be installed on a separate server. When installing Integration Composer, there are two options. You can use the IBM Tivoli Asset Management for IT Launchpad. Note, however, that you cannot use the Launchpad to install Integration Composer if you have a 64-bit operating system. The other installation option is to use one of the Integration Composer installation DVDs provided with the IBM Tivoli Asset Management for IT package. The separate Integration Composer DVD, which provides documentation in addition to an installation program, is the preferred option for installation. The installation guide on the Integration Composer DVD provides important installation information. IBM Tivoli Asset Management for IT includes two DVDs for installing Integration Composer, one for Windows and one for UNIX.

Installing Integration Composer with the Integration Composer DVD

You can use theIBM Tivoli Integration Composer DVD provided with Tivoli Asset Management for IT to install Integration Composer. Upgrade note: Installing Integration Composer 7.1.1 will upgrade the previous version of Integration Composer. You do not need to remove the previous version first. To avoid losing any of your current data, back up your Integration Composer data\dataschema and data\mappings directories before installing. To install Integration Composer, use the Integration Composer DVD provided with the Tivoli Asset Management for IT package. This DVD includes an IBM Tivoli Integration Composer Installation Guide, which explains in detail how to install Integration Composer. Please refer to this guide for installation instructions.

Installing Integration Composer with the Launchpad

This section explains the procedure for installing Integration Composer with the Launchpad. Do not use this installation option if you have a 64-bit operating system. Upgrade note: Installing Integration Composer 7.1.1, as described in this section, will upgrade the previous version of Integration Composer. You do not need to remove the previous version first. To avoid losing any of your current data, back up your Integration Composer data\dataschema and data\mappings directories before installing. To install Integration Composer with the Launchpad, complete the steps that follow. 1. Insert the Launchpad DVD into the server where you will install Integration Composer, and, from the Launchpad, launch the Integration Composer installation program by clicking the link under 3. Install Tivoli Integration Composer.
Copyright IBM Corp. 2007, 2008

147

2. 3. 4.

5.

6.

Note: If you do not have the prerequisite IBM Java SDK 5.0 Service Release 5 currently installed on the Integration Composer server, an error window displays and the installation ends. The error states: Windows error 3 occurred while loading the Java VM. To correct the problem, install IBM Java SDK 5.0 Service Release 5 on your operating system and run the setup command again. On the IBM Tivoli Integration Composer window, select your language from the drop-down list at the bottom and click OK. On the Introduction window, review the information and click Next. On 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 the directory. Then click Next. On the Choose Install Folder window, accept the default location or type a file path to specify the directory where you want to install Integration Composer. (Alternatively, you can click Choose to browse and select the location you want.) Then click Next. On the Database Type window, select the database you intend to use with Integration Composer and click Next. The Database Login Information window is displayed. This Database Login Information window is where you define the parameters for connecting to the Maximo database. The fields displayed in this window vary slightly, depending on the type of database you chose in the previous step. The following table defines the fields that the installation program displays for the supported databases.

Table 22. Login specifications for the Maximo database

Field Database Server Name Port Number Database Name (SID) or Database Name Database Username Database/Schema Owner

Description Name of the server on which the Maximo database resides Port number of the server on which the Maximo database resides For Oracle databases, this is the session identifier (SID) for the database; that is, the database instance For SQL Server or IBM databases, this is simply the name of the database Valid user name for signing in to the Maximo database Database or schema owner

7. On the Database Login Information window, type login specifications for the database and click Next. Tip: Make note of the values that you specified here. Later, when you launch Integration Composer, use the values entered in these fields to define connection parameters for the Maximo database. 8. On the Update Software Instances window, select one of the following options and click Next: v Yes, disable software updates

148

Installation Guide for IBM WebSphere Application Server:

If you select this option, when Integration Composer imports data into the Maximo database, Integration Composer inserts or deletes software records but does not update software records. This option is preferred. v No, dont disable software updates If you select this option, when Integration Composer imports data into the Maximo database, Integration Composer updates existing software records. 9. On the Preinstallation Summary window, review the installation details and click Next. 10. On the Begin Installing window, click Install to begin installing Integration Composer. The Installing Integration Composer progress window displays during installation. Note: If necessary, you can click Cancel to end the installation. When installing is finished, the Installation Complete window is displayed. 11. On the Installation Complete window, click Done.

Chapter 8. IBM Tivoli Integration Composer installation

149

150

Installation Guide for IBM WebSphere Application Server:

Chapter 9. Tivoli Asset Management for IT language pack installation program overview
After you have successfully deployed Tivoli Asset Management for IT, you can add language support to Tivoli Asset Management for IT user interface using the Tivoli Asset Management for IT language pack installation program. MXServer must be started prior to running the Tivoli Asset Management for IT language pack installation program. Important: If you plan to add language support to Tivoli Asset Management for IT, use the Tivoli Asset Management for IT language pack installation program before you perform post installation steps described in Chapter 10, Tivoli Asset Management for IT post installation tasks, on page 153.

Installing the language pack

This procedure provides task information for installing the Tivoli Asset Management for IT language pack. Because language pack installation can several hours to complete, decide which additional languages you will need prior to starting the language pack installation. Each additional language selected will increase the amount of time to complete the installation will take. Also, do not add as an additional language the language you select as your base. This is not necessary and only increases the installation time. To use the Tivoli Asset Management for IT language pack installation program to install the Tivoli Asset Management for IT language pack, complete the following steps: 1. Ensure all Tivoli Asset Management for IT middleware servers and services are running. If you encounter a failure resulting from an inactive Tivoli Asset Management for IT middleware server or service, start that server or service, and then rerun the language pack installation program. The language pack installation program will first uninstall the base and additional languages installed by the process solution installation wizard from the failed installation attempt, and perform a reinstall. 2. Login as Administrator on the Tivoli Asset Management for IT administrative system. 3. On the launchpad, click the Tivoli Asset Management for IT Language Pack installer link under 2. Install IBM Tivoli Asset Management for IT 7.1 4. Select a language for the install, and then click OK. This choice is only for use during the installation and its selection will not affect the languages being installed. 5. From the Welcome panel, click Next. 6. From the Base Language panel, select a base language to be used with Tivoli Asset Management for IT, and then click Next. This is the only opportunity you will have to select a base language. You cannot change the base language at a later time.

Copyright IBM Corp. 2007, 2008

151

7. From the Additional language selection panel, select 0 or more additional languages to be supported, and then click Next. You are not prevented from selecting the language you specified in the Base Language panel as an Additional Language. While no error will occur during installation, in practice, do not specify the base language as an additional language. Doing so would be redundant. 8. From the language selection summary panel, review the information and then click Next. 9. From the Pre-install Summary Panel, click Install. Even if you added additional languages through the language pack installation program, and you set the locale or your machine to a language that was installed as an additional language, you might still encounter instances in the Tivoli Asset Management for IT UI where items are displayed in the language you identified as the base language of the machine. This problem is a known limitation and does not indicate that the Tivoli Asset Management for IT language pack installation failed. In some cases, shortcut elements appearing in the Tivoli Asset Management for IT UI, for example, menu choices, only display in the base language designated or in English only.

152

Installation Guide for IBM WebSphere Application Server:

Chapter 10. Tivoli Asset Management for IT post installation tasks

There are several post installation tasks that need to be completed following a successful Tivoli Asset Management for IT deployment. v Initial data configuration v Chapter 9, Tivoli Asset Management for IT language pack installation program overview, on page 151 Important: If you plan to add language support to Tivoli Asset Management for IT, use the Tivoli Asset Management for IT language pack installation program before you perform these post installation steps. Refer to Chapter 9, Tivoli Asset Management for IT language pack installation program overview, on page 151 for more information about the Tivoli Asset Management for IT language pack installation program.

Initial data configuration

Once you have successfully installed and configured Tivoli Asset Management for IT components, there are several data configuration tasks you must complete prior to using Tivoli Asset Management for IT.

Signing in using a default user ID

User management is managed though the directory server you have configured to use with Tivoli Asset Management for IT. When first installed, Tivoli Asset Management for IT contains the following default user IDs, which are members of the specified security group: Important: Before you begin this procedure, ensure you have the following users and groups created:
Table 23. Tivoli Asset Management for IT users and groups User wasadmin maxadmin (maxadminusr for MS Active Directory) mxintadm maxreg maxadmin maxadmin Groups

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 and passwords are lowercase. To sign in, complete the following steps: 1. Open a browser window. 2. Navigate to the Tivoli Asset Management for IT log in URL.
Copyright IBM Corp. 2007, 2008

153

For example: http://hostname:<port>/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.

Create currency codes

You must define a currency code for an organization. To define a currency code for an organization, complete the following steps: 1. Open the Currency Code application for Users by selecting Goto Financial Currency Code. 2. Click New Row. 3. Enter a currency name, for example, USD. 4. Click Save.

Create item and company sets

You must define item and company sets for an organization. To define a currency code for an organization, complete the following steps: 1. Open the Sets application for Users by selecting Goto Administration Sets. 2. Click New Row. 3. 4. 5. 6. Enter a company set name, for example, IT Items. Enter ITEM in the Type field. Click New Row. Enter an item set name, for example, IT Comps.

7. Enter COMPANY in the Type field. 8. Click Save.

Create an organization
You must define at least one organization for Tivoli Asset Management for IT. To define an organization, complete the following steps: 1. Open the Organizations application by selecting Goto 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 on Sites tab. 9. Click New Row. 10. Enter a site name in the Site field. For example, B901.

154

Installation Guide for IBM WebSphere Application Server:

11. Click Save.

Create a general ledger account component

You must create a general ledger account component for Tivoli Asset Management for IT. To create a general ledger account component, complete the following steps: 1. Open the Database Configuration application by selecting Goto 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 numerical length for the component. For example, 5. 6. Enter a type for the component. For example, ALN. 7. Click OK.

Create a general ledger account

You must create a general ledger account for Tivoli Asset Management for IT. To create a general ledger account, complete the following steps: 1. Open the Chart of Accounts application by selecting Goto Financials Chart of Accounts. 2. Click on 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.

Create default insert site

You must create a default insert site for Tivoli Asset Management for IT. To create a default insert site, complete the following steps: 1. Open the Users application by selecting Goto Security Users. 2. Search for maxadmin and then select it to open the record for maxadmin.

Chapter 10. Tivoli Asset Management for IT post installation tasks

155

3. Enter a the site you created earlier in the Default Insert Site field. For example, B901. 4. Enter a the site you created earlier in the Storeroom Site for Self-Service Requisitions field. For example, B901. 5. Click Save. 6. Open the WebSphere Admin Console and restart the MXServer application server. If you receive an error message that indicates that the record is being updated by another user, log out as MAXADMIN and then log back in.

Create a Work Type

You must create a Work Type for Tivoli Asset Management for IT. To create a Work Type, complete the following steps: 1. Open the Organizations application by selecting Goto Administration Organizations. 2. Search for the organization you created, for example, ENGLENA. 3. Click on 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. 6. Select PMCFGWO as the Work Order class. 7. Set the Work Type as AR. 8. Set Start Status as INPRG. 9. 10. 11. 12. 13. 14. 15. Set Complete Status as COMP. Click New Row. Select PMCFGWO as the Work Order class. Set the Work Type as UR. Set Start Status as INPRG. Set Complete Status as COMP. Click OK.

16. Click Save.

Signing out and signing in

When you make changes to a security group that your user ID is a member of, you must sign out and sign in again in order to see the changes. For example, even though you have granted the MAXADMIN group permission to create start center templates, the actions are not visible until you sign in again. 1. Sign out as MAXADMIN. 2. Sign in as MAXADMIN.

Synchronizing data
The scheduled synchronization of data that occurs between LDAP repositories and Tivoli Asset Management for IT is governed by the federated repositories managed by VMM in WebSphere, and the Tivoli Asset Management for IT VMM crontask.

156

Installation Guide for IBM WebSphere Application Server:

For specific information on configuring the VMMSYNC cron task for Microsoft Active Directory, refer to Manually configuring the VMMSYNC cron task for Microsoft Active Directory on page 132. To configure the synchronization schedule between LDAP repositories and Tivoli Asset Management for IT, complete the following steps: 1. Open a Web browser and point to http://hostname:9081/maximo. 2. Log into Tivoli Asset Management for IT 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 hit Enter. 5. Locate the VMMSYNC cron task, and click it. 6. Ensure the following values are used for each field: Principal
cn=wasadmin,ou=users,ou=SWG,o=IBM,c=US

This is the user required by the CronTask application to connect to the local VMM service. This value can be any WebSphere administrative user that has authorization to connect to the local VMM service. Credential This should be the password used for the Principal account. In this case, enter the password for wasadmin. GroupSearchAttribute This value is the LDAP group object attribute used to search for groups under the configured directory sub-tree.
cn

UserSearchAttribute This value is the LDAP user object attribute used to search for users under configured directory sub-tree.
Uid

SynchAdapter This value is the Java class that writes LDAP data to the database.
psdi.security.vmm.DefaultVMMSyncAdapter

SynchClass This value is the Java class that connects to the VMM local service to search for required objects.
psdi.security.vmm.VMMSynchronizer

Group Mapping This field contains XML mapping files that map LDAP object attributes to database repository table columns. Change the following object entries: Basedn This defines the LDAP sub-tree under which the VMM Crontask will search for group objects.
ou=groups,ou=SWG,o=IBM,c=US

Filter

This is the VMM object class that the service uses to search for group objects in LDAP.
Group

Chapter 10. Tivoli Asset Management for IT post installation tasks

157

User Mapping This field contains XML mapping files that map LDAP object attributes to database repository table columns. Change the following object entries: Basedn This defines the LDAP sub-tree under which the VMM Crontask will search for user objects.
ou=users,ou=SWG,o=IBM,c=US

Filter

This is the VMM object class that the service uses to search for user objects in LDAP.
PersonAccount

7. Set the task to active. By default, the crontask will perform its task every 5 minutes. Make changes to the Schedule field of the crontask if you want to change the interval.

First steps to using Log and Trace Analyzer

Before you begin using Log and Trace Analyzer and the Log and Trace Analyzer Resource Set Generator follow the guidelines in this topic. Before you begin, ensure that the IBM Agent Controller (AC) has been properly installed on all of the remote systems from which you want Log and Trace Analyzer to gather information and you have completed the post installation requirements.

Locations of the resource set definition files

After the Middleware installer installs the AC, it creates a resource set definition called the logAnalyzerConfig.xml file at the following location: AGENTCONTROLLER_HOME\plugins\com.ibm.ccmdb\config. For example, where AGENTCONTROLLER_HOME = C:\Program Files\IBM\AgentController the logAnalyerConfig.xml file would be found under the C:\Program Files\IBM\AgentController\plugins\com.ibm.ccmdb\config directory. Log and Trace Analyzer creates a configuration file called, config.properties. This file designates where the logAnalyzerConfig.xml files should reside. The Log and Trace Analyzer Resource Set Generator updates the config.properties file with the path where the resource set definition files reside if the config.properties ConfigFileDir key is not already set.

Modifying the config.properties file

If you have not invoked the Resource Set Generator, it is necessary to specify the location where the resource definition files will reside in the config.properties file. This location is used by the Log and Trace Analyzer to locate the resource definition files during the creation of a resource set. To modify, enable, and set the path for the resource definition files perform the following: 1. Open the WEBSPHERE_HOME\AppServer\systemApps\isclite.ear\ PortalLogTraceAnalyzer.war\config.properties file 2. Locate the ConfigFileDir properties key. 3. If the ConfigFileDir key has a # symbol in front of # ConfigFileDir = d:/config, remove the # to enable the ConfigFileDir properties key.

158

Installation Guide for IBM WebSphere Application Server:

Note: If the key does not have # ConfigFileDir = d:/config then the Resource Set Generator may have already been invoked and has set the path. Ensure that you manually copy the logAnalyzerConfig.xml files generated by the Middleware installer to that directory. Skip step 4. 4. Choose a path to save the resource definition files that the Log and Trace Analyzer Resource Set Generator creates and where you will manually copy the logAnalyzerConfig.xml files generated by the Middleware installer.

Copying resource definition files to ConfigFileDir location

Copy the resource set definition files, logAnalyzerConfig.xml files created by the Middleware installer into the directory specified for the ConfigFileDir. In order to avoid naming collision when copying the file, modify the name of the file to logAnalyzerConfigN.xml. For example, you can choose a sequential naming convention like: logAnalyzerConfig1.xml and logAnalyzerConfig2.xml.

Starting the Log and Trace Analyzer Resource Set Generator

The Log and Trace Analyzer is located in a zip file in the LPCT directory of the Tivoli Asset Management for IT 7.1 DVD media. The name of the zip file is: context_file_generation_tool-AC-4.2.2.zip. Before you start the Log and Trace Analyzer Resource Set Generator, edit the sample configuration files packaged with the tool. After you create a configuration file perform the following: 1. Set the WEBSPHERE_HOME environment variable to the directory where WebSphere Application Server is installed. 2. Optional: To display debugging information in the standard output, edit the ctxgen.bat (Windows) and ctxgen.sh (Linux) file in the bin directory where the tool is installed. v For Windows, replace set TRACE=off=disabled with set TRACE=info=enabled. v For Linux, replace TRACE=off=disabled with TRACE=info=enabled. 3. For Linux, modify the permissions for the ctxgen.sh script file by entering chmod +x bin/ctxgen.sh at the command line. 4. Run the ctxgen command on the command line to start the Log and Trace Analyzer Resource Set Generator.

Chapter 10. Tivoli Asset Management for IT post installation tasks

159

160

Installation Guide for IBM WebSphere Application Server:

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

161

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Software Interoperability Coordinator, Department 49XA 3605 Highway 52 N Rochester, MN 55901 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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBMs suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating

162

Installation Guide for IBM WebSphere Application Server:

platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks
For trademark attribution, visit the IBM Terms of Use Web site (http://www.ibm.com/legal/us/) The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.

Notices

163

164

Installation Guide for IBM WebSphere Application Server:

Index A
Agent Controller 59 Installing 137 Starting 138 Stopping 138

D
DB2 47

I
IBM Agent Controller 59 IBM HTTP Server 57 IBM Tivoli Directory Server 52 IHS 57 installing 46 prerequisite software products 31 installing Integration Composer with the DVD 147 installing Integration Composer with the Launchpad 147 ITDS 52

M
middleware 31, 46

P
Plug-in 58 prerequisite 31

V
Virtual Member Manager VMM 60 60

W
WAS 53, 54 WebSphere Application Server Deployment Manager 53, 54 WebSphere Plug-in 58

Z
zLinux 46 creating profiles 54 installing 47, 52, 53, 57, 58, 59, 60

Copyright IBM Corp. 2007, 2008

165

166

Installation Guide for IBM WebSphere Application Server:

Printed in USA