Vous êtes sur la page 1sur 296

Tivoli IBM Maximo Asset Management

Version 7 Release 1.0

Installation Guide

Tivoli IBM Maximo Asset Management

Version 7 Release 1.0

Installation Guide

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

This edition applies to version 7, release 1, modification 0 of IBM Maximo Asset Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2007 - 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Chapter 1. Introduction to IBM Maximo Asset Management . . . . . . . . . . 1
System architecture and components . Product information . . . . . . . . . . . . . . . . 1 . 2 Installing middleware with the Tivoli middleware installer . . . . . . . Middleware installer logs . . . . . Installing Maximo Asset Management and automatically configuring middleware . . Simple install path values . . . . . Running the Maximo Asset Management installation program . . . . . . . Completing post-installation tasks . . . . Deploying the confhelp.properties file . Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . 50 . 63 . 65 . 65 . . . . 67 80 81 81

Chapter 2. Planning to install Maximo Asset Management . . . . . . . . . . 3


Deployment environments . . . . . . . . . . 3 Role of the administrative workstation. . . . . 5 Deployment engine overview . . . . . . . 5 Performing multiple product installations using one administrative workstation . . . . . . 5 Deployment scenarios . . . . . . . . . . . 6 Middleware configuration planning. . . . . . . 7 Planning worksheets for middleware installation . . 8 Planning worksheet for the product installation . . 13 Security planning . . . . . . . . . . . . 15 Planning for serviceability . . . . . . . . . 16

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware. . 83
Installing existing middleware using the middleware installation program . . . . . . Reusing DB2 . . . . . . . . . . . . Reusing IBM Tivoli Directory Server . . . . PreparingMicrosoft Active Directory for reuse . Middleware installer logs . . . . . . . . Reusing middleware with the Maximo Asset Management installation program . . . . . . Simple install path values . . . . . . . Running the Maximo Asset Management installation program . . . . . . . . . Completing post-installation tasks . . . . . Deploying the confhelp.properties file . . . Verifying the installation . . . . . . . . . . . . 84 84 85 86 88

Chapter 3. Preparing to install Maximo Asset Management . . . . . . . . . 19


DVD or image file contents . . . . . . . . Prerequisite hardware and software . . . . . Preparing for the installation . . . . . . . Remote configuration enablement . . . . . Handling SSL client authentication restrictions. Backing up the deployment engine database . Preparing Linux and UNIX systems for Maximo Asset Management middleware . . . . . Accessing system directories. . . . . . AIX tar command requirements . . . . Increasing AIX file size and number of descriptors . . . . . . . . . . . Increasing AIX paging space. . . . . . Enabling asynchronous I/O on AIX . . . Verifying the required rpm-build package is installed . . . . . . . . . . . . Checking for required libraries on Linux . Configuring the JRE in Linux . . . . . Setting the ulimit . . . . . . . . . Setting the swap size . . . . . . . . Setting shared memory . . . . . . . Maximo Asset Management installation overview Maximo Asset Management launchpad . . . . Starting the Maximo Asset Management launchpad . . . . . . . . . . . . . . . . . . . 19 19 37 37 38 38

. 89 . 104 . . . . 106 119 120 120

. 39 . 39 . 40 . 40 . 40 . 41 . . . . . . 42 42 42 43 43 43 44 . 44

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware . . . . . 123
Manually installing and configuring middleware Manually configuring the database server . . Manually configuring DB2 9.x . . . . . Manually configuring DB2 8.2 . . . . . Manually configuring Oracle 11g . . . . Manually configuring Oracle 10g . . . . Manually configuring Oracle9i Rel2 . . . Manually configuring DB2 8.2 . . . . . Manually configuring SQL Server . . . Manually configuring the directory server . . Manually configuring IBM Tivoli Directory Server . . . . . . . . . . . . . Manually configuring Microsoft Active Directory . . . . . . . . . . . . Manually configure the J2EE server . . . . Manually configuring Websphere. . . . Manually configuring the WebLogic server Installing Maximo Asset Management and manually configuring middleware . . . . . Installing Maximo Asset Management without automatic middleware configuration . . . . . . . . . . . . 125 125 125 130 134 136 139 140 144 146

. 146 . 150 . 160 . 160 178 . 182 . 182

. 44

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware . . . 47
Installing new middleware . . . . . Middleware installer workspace . . Middleware deployment plan overview Activating the deployment plan .
Copyright IBM Corp. 2007 - 2010

. . . .

. . . .

. . . .

. . . .

48 49 50 50

iii

Completing post-installation tasks . . . . . Post product installation process manager tasks Manually configuring PSI packages . . . Deploying the confhelp.properties file . . . Verifying the installation . . . . . . .

. 195 195 . 196 . 197 . 198

Chapter 7. Deployment of optional packages . . . . . . . . . . . . . 201


Optional deployment of Maximo Asset Management language packages . . . . . . Installing the language pack . . . . . . Process solution package installation . . . . Process solution packages . . . . . . . Before using the process solution installation program . . . . . . . . . . . . . Installing process managers using the process solution installation wizard. . . . . . . Process solution installation logs . . . . . . . . . 201 201 203 203

WebSphere configuration . . . . . . . . WebSphere Application Server configuration Starting the WebSphere Application Server Securing the WebSphere Application Server Network Deployment Administrative Console through VMM . . . . . . . Configuring the WebSphere Application Server to run Windows services . . . . Configuring the WebSphere node agent to run Windows services . . . . . . .

. 219 219 219

. 221 . 222 . 224

Chapter 9. Troubleshooting . . . . . 227


Troubleshooting the middleware installer . . . Encountering error CTGIN9042E . . . . . Encountering error ACUINI0044E . . . . Incorrect db2admin password . . . . . . Improper configuration of DB2 or IBM Tivoli Directory Server . . . . . . . . . . Incorrect idsccmdb user password . . . . Incorrect service pack requirement for AIX . Failure when system directories cannot be renamed . . . . . . . . . . . . . SOAP connection problem . . . . . . . Invalid DB2 password value . . . . . . Troubleshooting the product installation program General troubleshooting of the product installation program . . . . . . . . . Common deployment failures . . . . . Restarting middleware . . . . . . . . . Restarting middleware on Windows . . . . Restarting middleware on UNIX . . . . . Uninstall the product or middleware . . . . Uninstalling middleware . . . . . . . Troubleshooting middleware uninstall . . Uninstalling the product. . . . . . . . Uninstalling an automatically configured deployment . . . . . . . . . . . Uninstalling a manually configured deployment . . . . . . . . . . . Installation properties . . . . . . . . Updating environment data . . . . . . . . . 227 227 228 229

. 203 . 204 . 205

Chapter 8. Post-installation configuration . . . . . . . . . . . 209


Post installation steps . . . . . . . . . . Initial data configuration . . . . . . . . Signing in using a default user ID . . . . Configuring SMTP . . . . . . . . . Creating currency codes . . . . . . . . Create item and company sets . . . . . . Create an organization . . . . . . . . Creating a general ledger account component Applying changes to the database . . . . Create a general ledger account . . . . . Update General Ledger Component Type Authorization . . . . . . . . . . . Update Company-Related Accounts . . . . Create default insert site. . . . . . . . Create a Work Type . . . . . . . . . Signing out and signing in . . . . . . . Configure directory server for Microsoft Active Directory . . . . . . . . . . . . . . Manually configuring directory services for WebSphere Application Server Network Deployment . . . . . . . . . . . . Manually configuring directory services for Oracle WebLogic Server . . . . . . . . Updating the port for the information center Maximo Asset Management Security . . . . Tuning DB2 . . . . . . . . . . . . . 209 209 209 210 210 211 211 211 212 212 213 213 214 214 215 215

. 230 . 233 . 234 . 234 . 236 . 237 239 . . . . . . . . . 239 243 255 255 256 257 257 259 261

. 262 . 263 . 267 . 280

215 217 217 217 218

Notices . . . . . . . . . . . . . . 283
Trademarks . . . . . . . . . . . . . . 285

Index . . . . . . . . . . . . . . . 287

iv

Installation Guide:

Chapter 1. Introduction to IBM Maximo Asset Management


IBM Maximo Asset Management is a comprehensive suite of products that is built on a single, common platform. Maximo Asset Management combines enhanced enterprise asset management functionality with new service management capabilities that together improve the effectiveness of asset management strategies.

System architecture and components


A Maximo Asset Management system includes the product and several additional software servers. Maximo Asset Management requires multiple software servers that are referred to as middleware. The middleware components can run on one or more computers. The following diagram shows the components that are used in a typical Maximo Asset Management installation.
Database Server

Directory Server

JDBC

Administrative Workstation

Application Server HTTP/HTTPS

HTTP Server

End User with web browser

A Maximo Asset Management installation has the following required components: Database The Maximo database stores all information about assets. You can store this information on the IBM DB2 database that is provided on the product DVD, or you use any other supported database. A list of supported databases is provided in the prerequisites topic in the chapter that helps you prepare for the installation. Application server The application server manages the Maximo Asset Management JavaServer Pages (JSPs), XML, and business logic components. Maximo Asset Management uses a commercial Java 2 Enterprise Edition (J2EE) application server: either IBM WebSphere Application Server or Oracle WebLogic Server. Administrative workstation
Copyright IBM Corp. 2007 - 2010

The administrative workstation is used to install Maximo Asset Management. The administrative workstation must be installed on a Microsoft Windows system. After the installation, use the administrative workstation to make updates or changes to the configuration. Web browser Users access the Maximo Asset Management applications by using a Web browser, connected over a company network or over the Internet. In addition to the required components, you can use the following optional components with Maximo Asset Management: HTTP server You can configure a separate, dedicated HTTP server to work with the J2EE application server. Directory server You can configure a directory server to provide identity management and authentication for the J2EE server.

Product information
Review the product installation information before you begin a Maximo Asset Management installation. Before you install Maximo Asset Management, review the following information on the Quick Start DVD and the Maximo Asset Management information center. The information center is located at http://publib.boulder.ibm.com/infocenter/ tivihelp/v3r1/index.jsp?topic=/com.ibm.mam.doc_7.1/mam_welcome.htm : Quick Start Guide Provides brief information to help you get started. The Quick Start DVD and Web information center contain copies of the Quick Start Guide in several languages. Download document Describes how to download the product images if you do not have a product DVD. Product support site The IBM Software Support Web site at http://www.ibm.com/software/ sysmgmt/products/support/IBMMaximoAssetManagement.html provides access to the latest fixes and technical notes.

Installation Guide:

Chapter 2. Planning to install Maximo Asset Management


Use this information to plan your Maximo Asset Management installation.

Deployment environments
You can deploy Maximo Asset Management and the middleware on a single computer or distributed across multiple computers. You can also configure a cluster of application servers to improve performance and provide redundancy in a large deployment. A deployment environment can use existing middleware, but the simplest approach is to install new middleware. The install program configures new middleware to work with Maximo Asset Management. If you intend to use existing middleware, you must update and configure it to be compatible with Maximo Asset Management. Plan to use one of the following deployment environments: Stand-alone environment In a stand-alone environment, you install Maximo Asset Management and the middleware on one computer. This environment is used typically for proof-of-concept purposes, demonstrations, testing, and learning environments.

Administrative workstation
(Windows OS only)

Middleware ? Maximo Asset Management Database ? J2EE server


(Windows, Linux, AIX, Solaris, HP-UX OS)

Distributed environment In a distributed environment, you install Maximo Asset Management and the middleware across multiple computers. This environment optimizes resource use and decreases the load on each system. Use this environment for production. In a distributed environment, you can install the middleware on a mixture of Windows, Linux, and UNIX computers. Only the administrative workstation must be hosted on a Windows system.

Copyright IBM Corp. 2007 - 2010

Install new or reuse existing Database ? DB2 ? Oracle ? SQL Server Optional: LDAP ? ITDS ? Microsoft Active Directory J2EE Server
? WebSphere ? WebLogic

Administrative workstation (Windows OS only)


Clustered environment You can configure the J2EE server to support a cluster of application servers to provide load-balancing and performance optimization, with centralized administration and management. If you plan to implement a cluster of servers, see the J2EE server documentation for instructions to configure and manage clustered services.

WebSphere Cell (ctgCell01) WebSphere Deployment Manager


(ctgCellManager01)

Maximo Cluster ctgNode1 ApplSrv1 ctgNode2

Database Server

Application Server

ApplSrv2 ctgNode3 ApplSrv3

A typical implementation uses a stand-alone environment for demonstration and testing, and a distributed or clustered environment for production.

Installation Guide:

Role of the administrative workstation


Install Maximo Asset Management from an administrative workstation where the Maximo Asset Management files are configured and deployed to the application server.

Deployment engine overview


The deployment engine is distributed with IBM products and stores information about IBM products that are installed on a computer. The deployment engine contains a database of information about IBM software installed on the system. When you start to install and IBM product, the installation program checks for the existence of the deployment engine on the system. If the deployment engine exists on the system, it provides details of the IBM products that are installed on the system. If a deployment engine does not exist, the installation program installs it. The deployment engine can be configured in a number of ways: v As a global instance v As a single instance that is available to all users on the system. v As a local instance for the sole use of the User ID that installs it. If the deployment engine is deployed as a global instance, it is not possible to create a local instance of the deployment engine on that system. If you use the middleware installation program to install middleware on the administrative workstation, it installs a global instance of the deployment engine and will prevent you from deploying multiple instances of the product on that system. The same user ID must perform all future software installations on the system, including applying fix packs, upgrades, and installing new products. When you perform subsequent installation actions, complete them on one system at a time, to avoid any potential confusion that can arise when running several instances of these programs at once.

Performing multiple product installations using one administrative workstation


You can use a single computer to deploy multiple instances of the product. For example, you can use the same computer to deploy a test environment, a development environment, and a training environment.

About this task


One administrative workstation can support several Maximo Asset Management installation by hosting multiple local instances of the deployment engine.

Procedure
1. Create a separate, non-administrative user ID on the administrative workstation for each installation. 2. Launch the product installation program while logged in as the non-administrative system user ID, to create a local instance of the deployment engine instance. 3. During the installation, a message is displayed that an error was encountered that is related to the registry service being unavailable. 4. Exit the installation wizard and add this user ID to the administrator group for the system. 5. Restart the installation program and continue with the installation.
Chapter 2. Planning to install Maximo Asset Management

6. In the Specify Install Folder screen, specify a directory that is separate from all other Maximo Asset Management installation directories on the same administrative workstation.

Example
In this example, the product is installed in a directory called C:\IBM\ development \SMP and is intended for use as a development environment. 1. Create the non-administrative system user ID for the development installation. This system user must have write access to the installation directory, but must not be a member of the system administrator group. In this example, we create a user named development. If you plan to use Windows Remote Desktop Connection to log in to the system with this user ID, add the ID to the Remote Desktop Users group. 2. Log in to the system using the development user ID 3. Launch the installation program and proceed through the introductory screens of the installation wizard. This phase of the installation creates a local instance of the deployment engine in the %USERPROFILE%\acsi_%USERNAME% director. In this example, the instance is created at C:\Documents and Settings\development\acsi_development. After the instance is created, an error message is displayed. Although the deployment engine instance was created successfully, the installation program is unable to immediately use it. 4. Click Next to exit the installation program. 5. Add the development user ID to the system administrators group. You must perform this step after the deployment engine is deployed locally. If you add the user ID to the administrators group before starting the installation, a global instance of the deployment engine is created. 6. Restart the installation program. 7. Proceed through the installation wizard screens. When you get to the Choose Install Folder screen, use a meaningful directory name that represents the purpose of this deployment. It can be useful to create an installation directory based on the user ID associated with this installation, for example, C:\IBM\SMP\development. 8. Repeat these steps for each subsequent installation on the same workstation. For each installation, use a different non-administrative user ID, installation directory, and middleware topology. to avoid conflict with other deployments.

Deployment scenarios
These deployment scenarios provide a road map of the tasks associated with each deployment option. The deployment scenarios summarize the installation and deployment tasks that you perform, depending on how you want to install and use middleware. The following deployment scenarios are provided: Deployment of Maximo Asset Management with automatic configuration of new middleware Use this scenario if you want to install and automatically configure the product with new middleware. This scenario is useful for setting up a demonstration environment.

Installation Guide:

Deployment of Maximo Asset Management with automatic configuration of existing middleware Use this scenario if you want to reuse middleware and you want to automatically configure it for use by Maximo Asset Management. If you plan to reuse middleware components, ensure that they are at the level supported by Maximo Asset Management. The installation programs do not perform remote prerequisite checks and do not provide a mechanism for patching unsupported servers. This scenario is suitable if you have existing middleware resources that you want to automatically configure for use by Maximo Asset Management. For example, you might have an instance of a DB2 server in an existing database server farm. Deployment of Maximo Asset Management with manual configuration of middleware Use this scenario if you want to reuse middleware and you want to manually configure it for use by Maximo Asset Management. If you plan to reuse existing middleware components, ensure that they are at the level supported by Maximo Asset Management. The installation programs do not perform remote prerequisite checks and do not provide a mechanism for patching unsupported servers. This scenario is suitable if you want to use existing middleware, but your company restricts the use of automated configuration tools when deploying a new application in your enterprise.

Middleware configuration planning


You can choose middleware from a wide selection of supported applications. Maximo Asset Management can automatically configure some new or existing middleware components, while others require manual configuration. In all deployment scenarios, you must install middleware before you install Maximo Asset Management. The Tivoli middleware installer that is included with the product, includes a set of IBM middleware components you can use. Alternatively, you can use any of the other supported middleware products from third-party vendors. The Maximo Asset Management installation program can automatically configure new or existing middleware that is supported by the middleware installer. You must manually configure middleware components that are not supported by the middleware installer. You might also choose to manually configure middleware, for example if your company security policies restrict use of automatic configuration tools. Automatic configuration The Maximo Asset Management installation program automatically configures middleware to work with Maximo Asset Management. This option is useful if you are installing new middleware, or if you have existing middleware that is not governed by policies that restrict automatic configuration. Manual configuration Alternatively, you can manually configure middleware that exists in your environment or has been installed by the Tivoli middleware installer. You must complete manual configuration before running the Maximo Asset Management installation program. This option is useful if you have policies in place that govern configuration procedures.
Chapter 2. Planning to install Maximo Asset Management

Planning worksheets for middleware installation


Before you start the installation, use the planning worksheets to record the values that you must specify when you perform the middleware installation.

Users and groups


Before you begin, record the values to use, so that you can quickly specify these values during the installation For distributed deployments, record multiple values where appropriate. The worksheets are also helpful if you intend to manually configure or reuse existing middleware. In this table, list the users and groups that you want to create if you do not want to use the default values.
Table 1. Users and groups created during Maximo Asset Management installation User db2admin Group v DB2USERS v DB2ADMNS Description DB2 administrator. Windows Service user ID. This user is created by the middleware installation program if it does not exist. idsccmdb Windows v Users v Administrators Linux, AIX, HP-UX, Solaris v idsldap v db2grp1 IBM Tivoli Directory Server user. This user is created by the middleware installation program if it does not exist. Your value

maximo

v Users v Administrators

Used for Maximo database configuration. This user is created by the Maximo Asset Management installation program if it does not exist.

ctginst1

v Users v Administrators ctginst1 must be a member of db2iadm1 or whichever group has been designated as the instance administration authorization group.

The system user that is used as the database instance owner on UNIX systems. This user is created by the middleware installation program if it does not exist.

db2fenc1

db2fgrp1

UNIX system user that is used as the fenced user ID for DB2. This user is created by the middleware installation program if it does not exist.

Installation Guide:

Table 1. Users and groups created during Maximo Asset Management installation (continued) User wasadmin Group Not a system user. Description User ID created for use with WebSphere Application Server. This user is created by the middleware installation program if it does not exist. Your value

Directory locations
In this table, list the middleware directory locations to use.
Table 2. Directory locations Setting Workspace directory Middleware images source directory Compressed images directory Uncompressed images directory Default user_home\ibm\tivoli\mwi\ workspace Your value

DB2 configuration
In this table, list the configuration values to use when you install DB2.
Table 3. DB2 configuration Setting Installation directory Default Windows SystemDrive\Program Files\IBM\SQLLIB Linux, AIX, HP-UX, Solaris /opt/IBM/db2/V9.5 DAS user Windows db2admin Linux, AIX, HP-UX, Solaris dasusr1 Fenced user Linux, AIX, HP-UX, Solaris db2fenc1 Linux, AIX, HP-UX, Solaris db2fgrp1 Linux, AIX, HP-UX /home/db2fenc1 Solaris /export/home/db2fenc1 Instance name Port ctginst1 50005 Your value

Fenced user group name

Fenced user home directory

Chapter 2. Planning to install Maximo Asset Management

Table 3. DB2 configuration (continued) Setting Instance user name home directory Default Linux, AIX, HP-UX /home/ctginst1 Solaris /export/home/ctginst1 Database instance user ID Windows db2admin Linux, AIX, HP-UX, Solaris ctginst1 DB2 administrators group Windows DB2ADMNS Linux, AIX, HP-UX, Solaris db2iadm1 DB2 users group Windows DB2USERS YES NO This value is relevant for reuse scenarios only. Enable O/S Security for DB2 objects YES This value is relevant for reuse scenarios only. DB2 instance port Data table space name Data table space size MAXDATA medium (1000 MB) DB2 Temporary table space name Temporary table space size Medium (5000 MB) Your value

Use same user name and password for remaining DB2 Services Configure Tools Catalog

MAXTEMP 1000 MB

Oracle configuration
In this table, list the configuration values to use when you install Oracle.
Table 4. Oracle configuration Setting Installation directory Default Windows SystemDrive\oracle\ product\11.1.0\db_1 Linux, AIX, HP-UX, Solaris /opt/app/oracle/product/ 11.1.0/db_1 Administrator User ID sys Your value

10

Installation Guide:

Table 4. Oracle configuration (continued) Setting Oracle Software Owner ID Default Windows Administrator Linux, AIX, HP-UX, Solaris oracle Instance Location Windows C:\oracle\product\11.1.0\ db_1 Linux, AIX, HP-UX, Solaris /opt/app/oracle/product/ 11.1.0/db_1 Data table space name Data table space size MAXDATA medium (1000 MB) Oracle Temporary table space name Temporary table space size Medium (1000 MB) Your value

MAXTEMP 1000 MB

Microsoft SQL Server configuration


In this table, list the configuration values to use when you install Microsoft SQL Server.
Table 5. Microsoft SQL Server configuration Setting Installation directory Named instance Microsoft SQL Server administrator Microsoft 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

WebSphere Application Server configuration


In this table, list the configuration values to use when you install WebSphere Application Server.

Chapter 2. Planning to install Maximo Asset Management

11

Table 6. WebSphere Application Server configuration Setting Installation location Default Windows C:\Program Files\IBM\WebSphere\ AppServer Linux, HP-UX, Solaris /opt/IBM/WebSphere/ AppServer AIX /usr/IBM/WebSphere/ AppServer Your value

WebSphere Administration user name wasadmin Deployment Manager profile name Application server profile name Profile directory ctgDmgr01 ctgAppSrv01 Linux, HP-UX, Solaris /opt/IBM/WebSphere/ AppServer/profiles AIX Cell name Deployment Manager node name Application server node name HTTP server installation location /usr/IBM/WebSphere/ AppServer/profiles

ctgCell01 ctgCellManager01 ctgNode01 Windows C:\Program Files\IBM\HTTPServer Linux, HP-UX, Solaris /opt/IBM/HTTPServer AIX /usr/IBM/HTTPServer

HTTP port

80 On Windows, this port might already be in use. Ensure that you either free this port, or use another port that is unassigned.

HTTP admin server port HTTP plug-in profile name

8008 ctgAppSvr01

IBM Tivoli Directory Server configuration


In this table, list the configuration values to use when you install IBM Tivoli Directory Server.

12

Installation Guide:

Table 7. IBM Tivoli Directory Server configuration Setting Install location Default Windows C:\Program Files\IBM\LDAP\V6.2 Linux, AIX, HP-UX, Solaris /opt/IBM/ldap/V6.1 Administrator distinguished name Organizational unit Organization and country suffix Directory server port Directory server secure port Administration port Administration secure port Database name Instance name Instance port Instance user name cn=root ou=SWG o=IBM,c=US 389 636 3538 3539 security idsccmdb 50006 sidsccmdb Your value

Microsoft Active Directory configuration


In this table, list the configuration values to use when you install Microsoft Active Directory.
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 Your value

Planning worksheet for the product installation


Before you start the Maximo Asset Management product installation, use this worksheet to record values that you specify when you perform a custom installation.
Table 9. Settings for a custom installation Setting Installation directory DB2 host name DB2 port Maximo database name 50005 maxdb71 Default C:\IBM\SMP Your value

Chapter 2. Planning to install Maximo Asset Management

13

Table 9. Settings for a custom installation (continued) Setting Maximo database instance Schema name Maximo database user ID DB2 installation directory Default ctginst1 maximo maximo Windows SystemDrive\Program Files\IBM\SQLLIB Linux, AIX, HP-UX, Solaris /opt/IBM/db2/V9.5 DB2 instance administrator user ID Windows db2admin Linux, AIX, HP-UX, Solaris ctginst1 Windows DB2 service user ID Oracle installation directory db2admin Windows SystemDrive\oracle\ product\11.1.0\db_1 Linux, AIX, HP-UX, Solaris /opt/app/oracle/product/ 11.1.0/db_1 Oracle administrator user ID Oracle software owner user ID SQL installation directory Data table space name Data table space size sys oracle C:\Program Files\Microsoft SQL Server\90 MAXDATA medium (1000 MB) DB2 Oracle Medium (5000 MB) Medium (1000 MB) Your value

Microsoft SQL Server (initial data file size) Medium (1000 MB) Temporary table space name Temporary table space size Index table space name Index table space size MAXTEMP 1000 MB MAXDATA DB2 Oracle Schema name WebSphere host name WebSphere SOAP port 8879 Medium (5000 MB) Medium (1000 MB)

maximo (must be the same value as the owner of the table spaces)

14

Installation Guide:

Table 9. Settings for a custom installation (continued) Setting WebSphere server home directory Default Windows C:\Program Files\IBM\WebSphere\ AppServer Linux, HP-UX, Solaris /opt/IBM/WebSphere/ AppServer AIX WebSphere admin user ID WebSphere profile name Web server port Web server name Node name Application server JMS data source name JMS database name JMS server name Database server port Database user ID Group base entry User base entry SMTP server Administrator e-mail 50000 maxadmin ou=groups,ou=SWG,o=IBM, c=US ou=users,ou=SWG,o=IBM, c=US maxsibdb /usr/IBM/WebSphere/ AppServer Your value

wasadmin ctgDmgr01 9081 webserver1 ctgNode01 MXServer

Security planning
While you plan your installation, you must consider the type of security management to use. You must also consider the applications that users can access, and, optionally, the assets that users can work with. Each service management process defines its own roles. You must decide whether to use the roles that are defined by the service management processes or to define your own. The roles that are defined by the processes are implemented as security groups. After installation, you can assign each defined user to one or more security groups to enable the users to perform the tasks that are assigned to the roles. You can also specify the applications that the members of each security group can use.

Security options
When you install Maximo Asset Management, you choose an option for managing your users and their memberships in security groups. The security option determines how your system performs authentication (sign in validation), and authorization (the applications that a user can access).

Chapter 2. Planning to install Maximo Asset Management

15

The option that you choose applies to all products that you install on a system. If you plan to install Maximo Asset Management with a product that was already installed, the choice you made when installing the first product applies to Maximo Asset Management as well. The following security options are available: Use application security for authentication and authorization With this option, you create all your users and security groups in your directory (LDAP) server. The information is updated in your Maximo database by using a cron task. If you use this option and also choose automatic configuration of your directory server, the roles are defined. Use application security for authentication only With this option, you create all your users in the directory server, but you manage their membership in security groups in the Security Groups application. Use Maximo security for authentication and authorization With this option, a directory server is not required. You create and manage users and groups in the Users and Security Groups applications, separately from any corporate user data you might have.

Security configuration
Although you choose a security option during the installation, you configure the security environment after installation. The post-installation tasks can include creating users, assigning users to security groups, and defining the applications that members of each security group can use.

Planning for serviceability


Serviceability refers to problem analysis from a central point, using data collected from a wide range of sources. Serviceability has changed from the method used in the previous version of the product. Serviceability is supported in Maximo Asset Management 7.1 through the use of the IBM Support Assistant Workbench. The workbench is a free utility that you can configure to work with many different products. Log files for the middleware installation program can be found in the workspace directory you defined when you ran the installation program. These files are analyzed by the Log Analyzer tool. Log files for the Maximo Asset Management installation program are on the administrative system in the following directories, where <MAM_HOME> equals C:\IBM\SMP.
Table 10. Log file directories Log file directory <CTG_MAM_HOME>\logs <CTG_MAM_HOME>\solutions\logs <CTG_MAXIMO_HOME>\maximo\tools\logs C:\Program Files\ibm\common\acsi\logs Details

16

Installation Guide:

Table 10. Log file directories (continued) Log file directory Details

Log files are generated here if a problem The ACULogger.properties and deexlogger.properties files contain *fileDir occurs during the validation sequence of the keys whose values provide the location for installation program. the log files. The properties files can be found on Windows at C:\ProgramFiles\IBM\ common\acsi or C:\Documents and Settings\username\acsi_username , and on other platforms at /var/ibm/common/acsi or /home/username/.acsi_username.

After installation, during normal usage of Maximo Asset Management, it can be useful to examine the logs generated for the MXServer application server, WebSphere deployment manager, and the WebSphere node agent. For more information about log information and the IBM Support Assistant Workbench, refer to the troubleshooting section of the Maximo Asset Management information center.

Chapter 2. Planning to install Maximo Asset Management

17

18

Installation Guide:

Chapter 3. Preparing to install Maximo Asset Management


After you plan your installation and deployment approach, but before you install Maximo Asset Management, you must do some further preparation. The preparation includes ensuring that all hardware and software prerequisites are met, and that the ports, protocols, and operating system environments are correctly installed and configured.

DVD or image file contents


A set of DVDs contains the prerequisite middleware, middleware fix packs, and the product code. Instead of using DVDs, you can download the files that contain the DVD images from Passport Advantage. Ensure that you have the following DVDs or images: Maximo Asset Management V7.1 Contains the following items: v v v v v Launchpad for starting installation programs Maximo Asset Management installer Maximo Asset Management middleware installer IBM Agent Controller installer Log and Trace Analyzer

v Resource Generator tool v Maximo Asset Management language pack installation program for Windows Middleware for Windows Contains middleware for Windows Server 2003 and Windows Server 2008. Middleware for Red Hat Enterprise Linux V4 Contains middleware for Red Hat Enterprise Linux version 4. Middleware for AIX V5.3 Contains middleware for AIX version 5.3. Middleware for Solaris 10 Contains middleware for Solaris 10. Middleware for HP UX 11g Contains middleware for HP UX 11g. Maximo Asset Management V7.1 Quick Start Contains the Quick Start guide in all languages and a copy of the product information center.

Prerequisite hardware and software


Review each of the tables for the prerequisite hardware and software and ensure that your environment meets the minimum standards before you perform the installation. The Maximo Asset Management installation and middleware installation programs install and configure IBM products that make up the Maximo Asset Management
Copyright IBM Corp. 2007 - 2010

19

architecture. For some IBM products already deployed in the enterprise, if they meet minimum release level requirements, the installation programs can configure them to be part of the Maximo Asset Management system. In some cases, the Maximo Asset Management installation programs can even configure previously deployed products from other vendors to be used with Maximo Asset Management. Prerequisites listed for non-IBM products were valid at the time this document was created. For the most up-to-date information about non-IBM product prerequisites, refer to the product documentation for each individual product. Maximo Asset Management supports IPv6 network configuration. The middleware installer can work in a pure IPv6 environment. However, deployments that include Windows systems require a hybrid environment in which the IPv4 protocol is also enabled. The product installation program and the process solution installation program use NETBIOS to connect to remote machines and validate host names. NETBIOS requires TCP/IPv4. The Internet Protocol (TCP/IP) network protocol must be enabled on any Microsoft Windows XP, Microsoft Windows Server 2003, and Microsoft Windows Server 2008 systems included in a deployment for IPv6 environments. Application performance For optimal application performance, allow one JVM per every 40 users, with a minimum of 2 GB of RAM and 1 CPU per JVM. Port availability The following ports need to be enabled in support of the installation and deployment.
Port 22 80 9080 389 636 1433 1521 3538 3539 8879 9043, 9044 Use SSH HTTPServer WebSphere Application Server virtual host port number, in the JVM. Directory server port Directory server secure port Microsoft SQL Server (default) Oracle (default) Directory server admin daemon port Directory server admin daemon secure port SOAP port to IBM WebSphere Application Server Network Deployment IBM WebSphere Application Server Network Deployment administrative console secure port IBM WebSphere Application Server Network Deployment administrative console IBM WebSphere Application Server Network Deployment SSL port Database port for Tivoli Directory Server DB2 Database instance port

9060, 9061 9443 50000 50005

20

Installation Guide:

A PING command issued from the administrative workstation must receive a response from each server used in the deployment. Ensure that each middleware host server is configured to respond to PING requests. Hardware (stand-alone environment)
Software v IBM DB2 v IBM WebSphere Application Server Network Deployment v IBM Tivoli Directory Server Hardware v 2 GHz processor v 40 GB disk space v 4 GB RAM (6 GB RAM recommended)

Hardware (distributed environment)


Software Administrative workstation Hardware v 2 GHz processor (minimum) v 2 GB RAM (minimum) v 10 Mbit/s network connection between administrative system and middleware servers (minimum) v 10 GB disk space Restriction: When you install a single deployment of Maximo Asset Management, the deployment engine is installed in the system root directory of the Windows administrative workstation. On Windows systems, this directory is C:\program files\ibm\acsi. You can specify that Maximo Asset Management is installed on a disk drive other than the C: drive, but the deployment engine is always installed in the system root directory. See the topic about performing multiple deployments from a single administrative workstation in the Planning chapter for further information. Ensure that permissions are set to allow the deployment engine to be installed in the appropriate directories. You must have 10 GB of disk space available on the administrative workstation to install Maximo Asset Management. An additional 6 GB of disk space must be available in the TEMP (or TMP) directory. IBM DB2 Minimum 20 GB disk space.

IBM WebSphere Application Server Network v 2 GHz processor Deployment v 20 GB disk space v 4 GB RAM IBM Tivoli Directory Server v For UNIX, 1 GB of space available in the /opt directory.

Chapter 3. Preparing to install Maximo Asset Management

21

For hardware requirements for software not listed here, refer to the product documentation provided with that product. Browser
Software Operating System

Any operating system that supports one of Microsoft Internet Explorer version 6 and 7.Maximo Asset Management version 7.1.1.6 the browsers listed in column 1. supports Microsoft Internet Explorer version 8. Firefox version 3. All user computers that run Maximo Asset Management must have the Java Runtime Environment (JRE), version 1.5 or 1.6, from IBM, installed. The JRE v1.5 or v1.6 can be downloaded at the following Web site: http://www.ibm.com/developerworks/ java/jdk/ Instruct your users to download and install the JRE before they start using the product.

File systems The following table lists the disk space to allocate to each directory for the Maximo Asset Management installation process. These directories do not exist before installing Maximo Asset Management. You must ensure that the parent directory of those directories have sufficient space available for the installation. The middleware installation program does not support the use of linked file systems when installing middleware on Linux or UNIX systems because during use it renames directories. For example, if the directory /opt/IBM/db2/V9.5 is a file system link, errors occur during middleware installation of DB2, because it is not able to rename it. Create file system links in a parent directory such as /opt/IBM/db2, /opt/IBM or /opt.
Product DB2 IBM Tivoli Directory Server IBM Tivoli Directory Server WebSphere Application Server WebSphere Application Server Update Installer IBM HTTP Server File system C:\Program Files\IBM\SQLLIB C:\Program Files\IBM\LDAP\V6.2 C:\idslap-idsccmdb C:\Program Files\IBM\ WebSphere\AppServer C:\Program Files\IBM\ WebSphere\ UpdateInstaller C:\Program Files\IBM\ HTTPServer Available Space Required (in MB) 1500 MB 800 MB 1049 MB 1420 MB 000 500 MB Windows (32bit) Operating System Windows (32bit) Windows (32bit) Windows (32bit) Windows (32bit)

1074 MB

Windows (32bit)

22

Installation Guide:

Product

File system

Available Space Required (in MB)

Operating System Windows (32bit)

Installation programs Temporary space 1049 MB designated for use by the middleware installation program. Maximo Asset Management Various Various Deployment engine Workspace directory System temporary directory User temporary directory C:\Program Files\IBM\Common\ acsi C:\Program Files\IBM\SQLLIB C:\Program Files\IBM\LDAP\V6.2 C\idslap-idsccmdb C:\Program Files\IBM\ WebSphere\AppServer C:\Program Files\IBM\ WebSphere\ UpdateInstaller C:\Program Files\IBM\ HTTPServer 512 MB 200 MB 615 MB 180 MB

Windows (32bit) Windows (32bit) Windows (32bit) Windows (32bit)

DB2 IBM Tivoli Directory Server IBM Tivoli Directory Server WebSphere Application Server WebSphere Application Server Update Installer IBM HTTP Server

1500 MB 800 MB 1049 MB 1700 MB

Windows (64bit) Windows (64bit) Windows (64bit) Windows(64bit)

500 MB

Windows (64bit)

1074 MB

Windows (64bit)

1049 MB Installation programs Temporary space designated for use by the middleware installation program. Maximo Asset Management Various Various Deployment engine Workspace directory System temporary directory User temporary directory C:\Program Files\IBM\Common\ acsi /opt/IBM/db2/V9.5 The mount point for this path must be defined as /opt/IBM/db2 512 MB 450 MB 615 MB 180 MB

Windows (64bit)

Windows (64bit) Windows (64bit) Windows (64bit) Windows (64bit)

DB2

2208 MB

AIX

Chapter 3. Preparing to install Maximo Asset Management

23

Product IBM Tivoli Directory Server

File system /opt/IBM/LDAP/V6.2 The mount point for this path must be defined as /opt/ibm/LDAP /home/idsccmdb /usr/IBM/WebSphere/ AppServer /usr/IBM/WebSphere/ UpdateInstaller /usr/IBM/HTTPServer

Available Space Required (in MB) 900 MB

Operating System AIX

IBM Tivoli Directory Server WebSphere Application Server WebSphere Application Server Update Installer IBM HTTP Server

1049 MB 2420 MB

AIX AIX

500 MB

AIX

1074 MB

AIX

2098 MB Installation programs Temporary space designated for use by the middleware installation program. Maximo Asset Management Various Deployment engine DB2 Workspace directory System temporary directory /usr/ibm/common/ acsi /opt/ibm/db2/V9.5 The mount point for this path must be defined as /opt/ibm/db2 Linux (32-bit Intel) only supports DB2 9.1 FP6 DB2 /home/ctginst1 175 MB 512 MB 615 MB 400 MB 2208 MB

AIX

AIX AIX AIX Linux

Linux

IBM Tivoli Directory Server

/opt/ibm/LDAP/V6.2 The mount point for this path must be defined as /opt/ibm/LDAP /home/idsccmdb /opt/IBM/WebSphere/ AppServer

900 MB

Linux

IBM Tivoli Directory Server WebSphere Application Server

1049 MB 2420 MB

Linux Linux

24

Installation Guide:

Product WebSphere Application Server Update Installer IBM HTTP Server

File system /opt/IBM/WebSphere/ UpdateInstaller /opt/IBM/HTTPServer

Available Space Required (in MB) 500 MB

Operating System Linux

1074 MB

Linux

Installation programs Temporary space 2098 MB designated for use by the middleware installation program. Maximo Asset Management Various Deployment Engine Workspace directory System temporary directory /usr/ibm/common/ acsi 512 MB 615 MB 400 MB

Linux

Linux Linux Linux

Database The following products can serve as the database component of a Maximo Asset Management 7.1 deployment.
Software Operating System

v DB2 9.5 FP3a (installed by the middleware v Microsoft Windows Server 2003 installation program), DB2 9.1 FP6, or DataCenter SP2 (32-bit Intel) V8.2 FP 15 (manual configuration only) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) v Windows Server 2008 DataCenter SP1 (32-bit Intel) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T)

Chapter 3. Preparing to install Maximo Asset Management

25

Software

Operating System v Red Hat Enterprise Linux v4 (AS and ES update 4) (32-bit Intel) v Red Hat Enterprise Linux v5.1 (AS and ES) (32-bit Intel) Red Hat Enterprise Linux (32-bit Intel) only supports DB2 9.1 FP6 v Red Hat Enterprise Linux v4 (AS and ES update 4) (64-bit Intel) v Red Hat Enterprise Linux v5.1 (AS and ES) (64-bit Intel) v Red Hat Enterprise Linux v4 (AS and ES update 4) for IBM System z v Red Hat Enterprise Linux v5.1 (AS and ES) for IBM System z v SUSE Linux Enterprise Server 9.0 SP4 (32-bit) v SUSE Linux Enterprise Server 10.0 SP1 (32-bit) v SUSE Linux Enterprise Server 11.0 (32-bit) (Manual installation only) SUSE Linux Enterprise Server (32-bit Intel) only supports DB2 9.1 FP6 v SUSE Linux Enterprise Server 9.0 SP4 (64-bit) v SUSE Linux Enterprise Server 10.0 SP1 (64-bit) v SUSE Linux Enterprise Server 11.0 (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 9.0 SP4 for IBM System z v SUSE Linux Enterprise Server 10.0 SP1 for IBM System z v SUSE Linux Enterprise Server 11.0 for IBM System z (Manual installation only)

26

Installation Guide:

Software

Operating System v AIX 5.3 TL 6 (64-bit kernel) IBM C++ runtime environment - xlC.rte, xlC.aix50.rte must be 9.0.0.1 or greater v AIX 6.1 TL 01 SP2 (64-bit kernel) IBM C++ runtime environment - xlC.rte, xlC.aix61.rte must be 9.0.0.1 or greater DB2 9.5 requires IBM C++ Run time Environment Components for AIX which includes xlC.rte 9.0.0.1. It is available at http://www.ibm.com/systems/p/support/ index.html. The lslpp command is used to display information about installed filesets or file set updates. Use the following commands to determine the C++ run time level for your system: lslpp -l | grep xlC.rte lslpp -l | grep xlC.aix50.rte lslpp -l | grep xlC.aix61.rte

v Oracle 9i v2, v Oracle 10g Rel1 or Oracle 10g Rel2 at level 10.2.0.5

v Microsoft Windows Server 2003 SP2 (Manual installation only) v Windows Server 2008 SP1 (Manual installation only) Windows Server 2008 only supports Oracle 10g Rel2 and Oracle 11g v Red Hat Enterprise Linux v4 (Advanced Server update 4) (32-bit Intel), (Manual installation only) Red Hat Enterprise Linux v4 only supports Oracle 10g Rel1 or Oracle 10g Rel2 For Oracle 10G Rel1 , Oracle patch set 3 (10.0.1.3) must be installed. v IBM AIX 5.3 TL 6 (Manual installation only) IBM AIX 5.3 TL 6 only supports Oracle 10g Rel1 or Oracle 10g Rel2 For Oracle 10G Rel1 installed on a 64-bit systems, Oracle patch set 3 (10.0.1.3) must be installed. v AIX 6.1 TL 01 SP2 (Manual installation only) AIX 6.1 TL 01 SP2 only supports Oracle 10g Rel2

v Oracle 11g at level 11.1.0.6 or 11.1.0.7

Chapter 3. Preparing to install Maximo Asset Management

27

Software

Operating System v SUSE Linux Enterprise Server 9.0 SP4 (32-bit) (Manual installation only) v SUSE Linux Enterprise Server 10.0 SP1 (32-bit) (Manual installation only) v SUSE Linux Enterprise Server 11.0 (32-bit) (Manual installation only) v SUSE Linux Enterprise Server 9.0 SP$ (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 10.0 SP1 (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 11.0 (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 9.0 SP4 for IBM System z (Manual installation only) v SUSE Linux Enterprise Server 10.0 SP1 for IBM System z (Manual installation only) SUSE Linux Enterprise Server only supports Oracle 10g Rel1 or Oracle 10g Rel2. v SUSE Linux Enterprise Server 11.0 for IBM System z (Manual installation only) v Red Hat Enterprise Linux v4 (AS and ES update 4) (IBM System z) Manual installation only v Red Hat Enterprise Linux v5.1 (AS and ES) (IBM System z) (Manual installation only) (Oracle 10g Rel2 only with patch set 10.2.0.4) v HP-UX 11i v2 (PA-RISC only) v HP-UX 11i v3 (PA-RISC only) v Sun Solaris 10.0

28

Installation Guide:

Software v Microsoft SQL Server 2005, SP 2 Standard or Enterprise version. v Microsoft SQL Server 2005, SP 1 Standard or Enterprise version. v Microsoft SQL Server 2008, SP 1 Standard or Enterprise version. v Microsoft SQL Server 2008, Standard or Enterprise version.

Operating System Microsoft SQL Server 2005 SP2, v Microsoft Windows Server 2003 DataCenter SP2 (32-bit Intel) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) v Windows Server 2008 DataCenter SP1 (32-bit Intel) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T)

J2EE application server The following products can serve as the J2EE application server component of a Maximo Asset Management 7.1 deployment. This is where Maximo Asset Management runs.

Chapter 3. Preparing to install Maximo Asset Management

29

Software v WebSphere Application Server Network Deployment v6.1 FP 23

Operating System v Microsoft Windows Server 2003 DataCenter SP2 (32-bit Intel) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) v Windows Server 2008 DataCenter SP1 (32-bit Intel) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T) v Red Hat Enterprise Linux v4 (AS and ES update 4) (32-bit Intel) v Red Hat Enterprise Linux v5.1 (AS and ES) (32-bit Intel) v Red Hat Enterprise Linux v4 (AS and ES update 4) (64-bit Intel) v Red Hat Enterprise Linux v5.1 (AS and ES) (64-bit Intel) v Red Hat Enterprise Linux v4 (AS and ES update 4) for IBM System z v Red Hat Enterprise Linux v5.1 (AS and ES) for IBM System z

30

Installation Guide:

Software

Operating System v SUSE Linux Enterprise Server 9.0 SP4 (32-bit) v SUSE Linux Enterprise Server 10.0 SP1 (32-bit) v SUSE Linux Enterprise Server 11.0 (32-bit) (Manual installation only) (requires fix pack 29, 6.1.0.29) v SUSE Linux Enterprise Server 9.0 SP4 (64-bit) v SUSE Linux Enterprise Server 10.0 SP1 (64-bit) v SUSE Linux Enterprise Server 11.0 SP1 (64-bit) (Manual installation only) (requires fix pack 29, 6.1.0.29) v SUSE Linux Enterprise Server 9.0 SP4 for IBM System z v SUSE Linux Enterprise Server 10.0 SP1 for IBM System z v SUSE Linux Enterprise Server 11.0 for IBM System z (Manual installation only) (requires fix pack 29, 6.1.0.29) v AIX 5.3 TL 6 (64-bit kernel) IBM C++ runtime environment - xlC.rte, xlC.aix50.rte must be 9.0.0.1 or greater v AIX 6.1 TL 01 SP2 (64-bit kernel) IBM C++ runtime environment - xlC.rte, xlC.aix61.rte must be 9.0.0.1 or greater

Chapter 3. Preparing to install Maximo Asset Management

31

Software Oracle WebLogic Server 9.2

Operating System v Microsoft Windows Server 2003 DataCenter SP2 (32-bit Intel) (Manual installation only) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) (Manual installation only) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) (Manual installation only) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) (Manual installation only) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) (Manual installation only) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) (Manual installation only) v Windows Server 2008 DataCenter SP1 (32-bit Intel) (Manual installation only) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) (Manual installation only) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) (Manual installation only) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) (Manual installation only) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) (Manual installation only) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T) (Manual installation only) v Red Hat Enterprise Linux v4 (AS and ES update 4) (32-bit Intel) (Manual installation only) Red Hat Enterprise Linux v5.1 (AS and ES) (32-bit Intel) (Manual installation only) v AIX 5.3 TL 6 (64-bit kernel) (Manual installation only) v AIX 6.1 TL 01 SP2 (64-bit kernel) (Manual installation only) v Sun Solaris 10.0

Administrative system The administrative system is a required component of Maximo Asset Management. It can run on the following platforms.

32

Installation Guide:

Software v Maximo Asset Management administrative system

Operating System v Microsoft Windows Server 2003 DataCenter SP2 (32-bit Intel) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Vista (Business, Enterprise, Ultimate) (32-bit) v Windows Microsoft Windows XP Professional SP2 (32-bit, 64-bit) v Windows Server 2008 DataCenter SP1 (32-bit Intel) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T)

Optional components The following products can be used with Maximo Asset Management, but they are optional. HTTP server The following product can serve as the HTTP server component of a Maximo Asset Management 7.1 deployment.

Chapter 3. Preparing to install Maximo Asset Management

33

Software v IBM HTTP Server v6.1 FP23

Operating System v Microsoft Windows Server 2003 DataCenter SP2 (32-bit Intel) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) v Windows Server 2008 DataCenter SP1 (32-bit Intel) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T) v Red Hat Enterprise Linux v4 (AS and ES update 4) (32-bit Intel) v Red Hat Enterprise Linux v5.1 (AS and ES) (32-bit Intel) v Red Hat Enterprise Linux v4 (AS and ES update 4) (64-bit Intel) v Red Hat Enterprise Linux v5.1 (AS and ES) (64-bit Intel) v Red Hat Enterprise Linux v4 (AS and ES update 4) for IBM System z v Red Hat Enterprise Linux v5.1 (AS and ES) for IBM System z v SUSE Linux Enterprise Server 9.0 SP2 (32-bit) v SUSE Linux Enterprise Server 10.0 (32-bit) v SUSE Linux Enterprise Server 9.0 SP3 (64-bit) v SUSE Linux Enterprise Server 10.0 SP1 (64-bit) v SUSE Linux Enterprise Server 9.0 SP3 for IBM System z v SUSE Linux Enterprise Server 10.0 SP3 for IBM System z

34

Installation Guide:

Software

Operating System v AIX 5.3 TL 6 (64-bit kernel) v AIX 6.1 TL 01 SP2 (64-bit kernel)

Directory server The following products can serve as the Directory server component of a Maximo Asset Management 7.1 deployment.
Software v IBM Tivoli Directory Server v6.2 Interim Fix 2 (installed by the middleware installation program) and IBM Tivoli Directory Server v6.1 FP1 Operating System When WebSphere Application Server is the application server, IBM Tivoli Directory Server is configured to synchronize user information with Virtual Member Manager, within WebSphere Application Server Network Deployment, to provide security for Maximo Asset Management. v Microsoft Windows Server 2003 DataCenter SP2 (32-bit Intel) v Microsoft Windows Server 2003 Standard Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 Enterprise Edition SP2 (32-bit Intel) v Microsoft Windows Server 2003 DataCenter x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Standard x64 Edition SP2 (64-bit AMD64 and EM64T) v Microsoft Windows Server 2003 Enterprise x64 Edition SP2 (64-bit AMD64 and EM64T) v Windows Server 2008 DataCenter SP1 (32-bit Intel) v Windows Server 2008 Standard Edition SP1 (32-bit Intel) v Windows Server 2008 Enterprise Edition SP1 (32-bit Intel) v Windows Server 2008 DataCenter x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Standard x64 Edition SP1 (64-bit AMD64 and EM64T) v Windows Server 2008 Enterprise x64 Edition SP1 (64-bit AMD64 and EM64T) v Red Hat Enterprise Linux v4 (AS and ES update 4) (32-bit Intel) Red Hat Enterprise Linux v5 for 32-bit Intel is not supported.

Chapter 3. Preparing to install Maximo Asset Management

35

Software

Operating System v AIX 5.3 TL 6 (64-bit kernel) IBM C++ runtime environment - xlC.rte, xlC.aix50.rte must be 9.0.0.1 or greater The loc.iso.en_US locale module must be present on AIX 5.3 systems and it must be at level 5.3.0.0 or greater. Use the lslpp command to determine if the loc.iso.en_US locale module is installed on the system: lslpp -l | grep bos.loc.iso.en_US v AIX 6.1 TL 01 SP2 (64-bit kernel) IBM C++ runtime environment - xlC.rte, xlC.aix61.rte must be 9.0.0.1 or greater IBM Tivoli Directory Server 6.2 requires IBM C++ Run time Environment Components for AIX which includes xlC.rte 9.0.0.1. It is available at http://www.ibm.com/systems/ p/support/index.html. The lslpp command is used to display information about installed filesets or file set updates. Use the following commands to determine the C++ run time level for your system: lslpp -l | grep xlC.rte lslpp -l | grep xlC.aix50.rte lslpp -l | grep xlC.aix61.rte v SUSE Linux Enterprise Server 9.0 SP2 (32-bit) v SUSE Linux Enterprise Server 10.0 (32-bit) v SUSE Linux Enterprise Server 11.0 (32-bit) (Manual installation only) (requires fix pack 2, 6.2.0.2) v SUSE Linux Enterprise Server 9.0 SP3 (64-bit) v SUSE Linux Enterprise Server 10.0 SP1 (64-bit) v SUSE Linux Enterprise Server 11.0 SP1 (64-bit) (Manual installation only) (requires fix pack 2, 6.2.0.2) v SUSE Linux Enterprise Server 9.0 SP3 for IBM System z v SUSE Linux Enterprise Server 10.0 SP3 for IBM System z v SUSE Linux Enterprise Server 11.0 for IBM System z (Manual installation only) (requires fix pack 2, 6.2.0.2)

36

Installation Guide:

Software v Microsoft Windows Server 2003 SP2 Active Directory Microsoft Active Directory Application Mode (ADAM) is not supported. Note that while Windows Server 2008 is supported as a platform for the administrative workstation, or for hosting middleware, Maximo Asset Management does not support Active Directory on Windows Server 2008.

Operating System When Oracle WebLogic Server is the application server, Microsoft Active Directory can be optionally configured to synchronize user information with Virtual Member Manager, within WebSphere Application Server Network Deployment, to provide security for Maximo Asset Management. Refer to the product documentation for Microsoft Windows Server 2003 Active Directory for support details.

Preparing for the installation


You must prepare the environment before you install middleware or Maximo Asset Management. To perform any of the steps, you must be logged in as a user with administrator privileges on Windows or as root on UNIX.

Remote configuration enablement


If you plan to use Maximo Asset Management to automatically configure middleware, you must enable a remote access protocol for each system on which you intend to install the middleware. The remote access protocols that support remote configuration are SSH for logging on to and configuring remote Linux and UNIX systems and Windows SMB for logging on to and configuring remote Windows systems. Windows SMB is a Windows protocol. The IBM JRE on the administrative workstation includes SSH, so you do not need an SSH client to remotely configure middleware on Linux or UNIX systems. But you must install OpenSSH on remote non-Windows workstations so that you can log on to them, using SSH protocol. Before you start the installation program, ensure that you can log in to any remote servers with the protocols that you intend to use and the credentials that you plan to supply to the installation program. For remote Windows systems, ensure the following requirements are met before installing the software: v The user name that you provide to the installation program must exist as a local account on the remote machine and the user must be a member of the Windows Administrators group. v The following Windows services must be started on the remote machine before you begin a remote installation and configuration: winmgmt (Windows Management Instrumentation) RemoteRegistry (Remote Registry) lanmanserver (Service) v The SMB protocol must be enabled and configured to use send NetBIOS over TCP/IP, by choosing to use port 139. Alternatively, you can configure SMB to use TCP/IP as the transport protocol, without NetBIOS, by configuring it to use port 445. v Ensure that any ports that you use for remote protocols are not blocked by firewalls or security policies, including ports 137 and 139. Port 139 is used if
Chapter 3. Preparing to install Maximo Asset Management

37

SMB is configured to run on NetBIOS over TCP/IP, and port 445 is used if SMB is run directly on TCP/IP, without NetBIOS. v To disable simple file sharing, start Windows Explorer. Click Tools Folder Options, and deselect the Use Simple File Sharing check box. v The Windows administrative share (C$) and the interprocess communications (IPC$) folder must be shared. v For Windows 2008 Server systems that support password-protected sharing, disable password-protection. Shares must be shared for the Guest or Everyone accounts. v For Windows systems that have User Account Control (UAC) enabled, it must be disabled before software can be remotely installed and configured. v If Cygwin is installed on the remote Windows system the SSH daemon (sshd) must be uninstalled or disabled. For remote Linux or UNIX systems, ensure the following requirements are met before installing the software: v The user name that you provide to the installation program must exist as a privileged account (for example, root) on the remote machines. v Ensure that a current version of OpenSSH is installed and running. Do not use OpenSSH 4.7.0.5302. v For Solaris systems, the remote access protocols require the use of internal shell scripts that must be run within the korn (ksh) shell. The methods need ksh, even if the user ID that you use to log on to the remote system is configured to use a different shell. Consequently, Solaris systems must have the ksh environment installed and properly configured. v If you plan to remotely configure software on remote Linux or UNIX computers, ensure that SSH is installed. Remote configuration does not support accessing network drives on the local or remote system.

Handling SSL client authentication restrictions


If you plan to install IBM HTTP Server, and configure it to use SSL/TLS (https), disable client authentication before you start the installation Maximo Asset Management. The installation programs fail if client authentication is enabled.

Procedure
1. Remove the SSLClientAuth Required directive in the httpd.conf configuration file of the IBM HTTP Server. 2. Stop and restart the IBM HTTP Server. 3. Install Maximo Asset Management. 4. Add the SSLClientAuth Required directive back to the httpd.conf configuration file of the IBM HTTP Server. 5. Stop and restart the IBM HTTP Server.

Backing up the deployment engine database


The deployment engine is a registry that stores information about the IBM software that you install on a particular computer. Perform a backup of the deployment engine database before and after installing new applications, or if you change a deployment.

38

Installation Guide:

About this task


The backup can help you recover from partial installation attempts, where middleware or process manager components were partially installed, but not completely. If an installation does fail, the deployment engine database might record (register) that a product was installed, when it actually was not. A corrupted deployment engine database might prevent you from later installing a product that you need. Copy the backup file to your hard disk to restore the registry to an uncorrupted state.

Procedure
1. Set up the environment using the following command: Windows OS
c:\Program Files\IBM\Common\acsi\setenv.cmd

Linux or UNIX OS
cd /var/ibm/common/acsi ./setenv.sh

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


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

Linux or UNIX OS
cd /usr/ibm/common/acsi/bin ./backupdb.sh backup_file_name

Use a descriptive name for the backup file to make it easy to identify the file to restore in the event of an error. For example, after successfully installing Maximo Asset Management, name the backup file DEBackupAfterMAMInstall.

Preparing Linux and UNIX systems for Maximo Asset Management middleware
If you intend to install middleware components on Linux or UNIX systems, prepare the system environment before the middleware installation. Certain system parameters must be set to specific values to create an environment on the system that can accommodate Maximo Asset Management middleware.

Accessing system directories


Before using the middleware installation directory, assign access permission to the /tmp and /home.

About this task


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

Procedure
1. Log in to the system as a user with administrative authority on the system. 2. Enter the following commands:
#chmod 777 /tmp #chmod 777 /home

Chapter 3. Preparing to install Maximo Asset Management

39

AIX tar command requirements


The middleware installation program requires both the native UNIX tar command and the GNU version of the tar command. Because the native utility does not support long file names, ensure that GNU tar version 1.14 or higher is installed, so that the installation files can be extracted. You can download GNU tar from http://www.ibm.com/systems/p/os/aix/linux/ toolbox/download.html. Verify that the system path variable contains both native UNIX tar and GNU tar paths, with the GNU tar path being defined before the native UNIX tar path. For example, the native tar utility is installed in /usr/bin and the GNU tar utility is installed in /opt/freeware/bin/tar. If you have set a symbolic link to overwrite the native UNIX tar command with the GNU tar command, you will encounter an error.

Increasing AIX file size and number of descriptors


Increase the default number of file descriptors allowed for the administrative user and set the maximum allowable file size to unlimited.

About this task


For Maximo Asset Management 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.

Procedure
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.
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. 5. Verify the settings from a command window by issuing the following command:
ulimit -a

Results
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


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.

40

Installation Guide:

Procedure
1. To determine the current amount of paging space available to the server, issue the following command:
lsps -a

This command will result in output that will include partition information similar to the following:
Page Space hd6 lslv hd6 Physical Volume hdisk0 Volume Group rootvg Size 5632MB %Used 2

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

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, with a total of 5632 Mb of paging space available to the system. 3. To increase paging space, add more logical partitions using 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,
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.

About this task


This requirement is an operational requirement, and you can perform this task 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.

Procedure
1. Log into the system as a root (administrative) user. 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

Chapter 3. Preparing to install Maximo Asset Management

41

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

Verifying the required rpm-build package is installed


Before you install the Maximo Asset Management middleware on a Linux system, verify that the rpm-build package is installed

About this task


To verify that the rpm-build package is installed, perform the following tasks:

Procedure
1. Run rpm -qa | grep build 2. If the command returns a value, such as rpm-build-4.3.3.-18_nonptl, the rpm-build package is installed. If nothing is returned, install the rpm-build package. For Red Hat Enterprise Advanced Server, the packcage is on disk 3 (of 5) of the Red Hat Enterprise Advanced Server version 4 installation CDs. For SUSE Linux, the package is on disk x of the SUSE Linux installation CDs. Use the rpm tool with the -i option to install the package.

Checking for required libraries on Linux


The Maximo Asset Management middleware installation program requires that the libstdc+.so.5 system library is present on a Linux system.

About this task


If this library is not installed, you receive an error indicating that the Maximo Asset Management 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. 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


About this task
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. 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.

42

Installation Guide:

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.

Setting the ulimit


Set the ulimit in Linux, to define user system and process resource limits.

About this task


For Linux systems, set the ulimit for the system prior to installing Maximo Asset Management middleware. Set the ulimit in the.profile for the root user so that the ulimit setting will apply to all processes.

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

Setting the swap size


Set the size of the swap space used in Linux systems to improve performance of Maximo Asset Management.

About this task


Typically, the swap size set for Linux systems must be the equivalent of 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 an, additional swap partition v creating a swap file See the product documentation for your Linux distribution for more information.

Setting shared memory


Set a minimum shared memory value in Linux systems to improve performance of Maximo Asset Management.

About this task


For Linux systems, set a minimum shared memory value for the system prior to installing the Maximo Asset Management middleware.

Procedure
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

Chapter 3. Preparing to install Maximo Asset Management

43

Maximo Asset Management installation overview


The installation process consists of several tasks that must be performed in sequence. To complete an installation, perform the following tasks: 1. Install and configure the required middleware. 2. Install and configure 3. Configure optional Maximo Asset Management middleware software products. 4. Install language packs. This step is necessary only if you need to support languages other than English. The installation programs for these components are started from the launchpad, where you can also access product information.

Maximo Asset Management launchpad


The IBM Maximo Asset Management launchpad is a central location where you can launch a range of installation programs and product information. The launchpad application assists you in choosing which product installation programs to install and indicates the order in which to install them.. Use the Maximo Asset Management launchpad to: v access the Maximo Asset Management Information Center v access information used to plan the Maximo Asset Management installation and deployment v start the Tivoli middleware installer v start the Maximo Asset Management installation program v start the Maximo Asset Management language pack installation program

Starting the Maximo Asset Management launchpad


The launchpad provides a single interface, from which you can install the required and optional middleware products

About this task


The launchpad uses the browser that is registered in the operating system as the default browser. On Linux systems, the launchpad runs in the Korn shell (ksh). If you are using Firefox, the Firefox properties need to be modified. To start the launchpad, complete the following steps:

Procedure
1. Log on as a local user, who has administrative privileges on the computer where Maximo Asset Management components are to be installed. Domain user logins are not supported. 2. Insert the launchpad DVD into a DVD drive. The DVD contains an autorun file, which can cause the launchpad program to start when you insert the launchpad DVD. If the autorun feature is disabled, or if your system does not

44

Installation Guide:

support autorun, you must start the launchpad program. The launchpad.exe (Windows systems) or launchpad.sh (non-Windows systems) is in the root directory of the launchpad DVD. v AIX: The launchpad program uses the system default browser to run. If the default browser on your system is Firefox, it is likely that the launchpad program will not run properly because the launchpad requires the ksh shell. If you want to use Firefox as the browser that the lauchpad uses, follow these steps to modify Firefox. a. Copy all of the files from disk 1 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, before you start the launchpad program:
typeset +r LOGNAME 2>/dev/null LOGNAME=lp_user_$$; export LOGNAME

Chapter 3. Preparing to install Maximo Asset Management

45

46

Installation Guide:

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware
To install Maximo Asset Management and automatically configure new middleware, follow the procedures in this chapter. This deployment scenario is the simplest to implement. To deploy Maximo Asset Management with existing middleware, use one of the alternative deployment scenario.

Before you begin


Ensure that you understand the system architecture and components and perform the planning and preparation tasks outlined in this guide.

About this task


This information provides a road map of tasks required to install Maximo Asset Management and perform automatic configuration of other system components. In this scenario, the middleware installation program installs new instances of DB2, IBM Tivoli Directory Server, and WebSphere Application Server Network Deployment that are provided with the product. After these installations, the Maximo Asset Management installation program performs additional configuration tasks to complete the deployment.

Install middleware using the middleware installation program

Install IBM Maximo Asset Management and automatically configure middleware

Verify the installation

Perform post-installation tasks

Procedure
1. Install and configure middleware using the middleware installation program.
Copyright IBM Corp. 2007 - 2010

47

2. Install Maximo Asset Management and perform additional middleware configuration tasks. 3. Verify the installation. 4. Complete post-installation tasks.

What to do next
After you complete the deployment, you can optionally perform the following tasks: v Install additional languages. v Install process solution packages

Installing new middleware


Use this deployment scenario to install new middleware and automatically configure it to work with Maximo Asset Management. The Tivoli middleware installer provides a set of IBM middleware products that you can install to deploy a Maximo Asset Management system. The Tivoli middleware installation wizard records the deployment and configuration parameters that you select in each screen, and then installs and deploys the middleware based on this information. The Tivoli middleware installer can install the following software: v Database server The Maximo database stores information about the attributes and history of each asset and the relationships between assets. The Tivoli middleware installer installs a new instance of DB2 UDB 9.5. To install an existing instance of DB2 UDB 8.2, DB2 UDB 9.1, or DB2 UDB 9.5, follow the instructions in the next chapter. If you want to install a new or existing SQL Server or Oracle database, follow the instructions in the manual deployment chapter. v Directory server Optional: You can use a directory server to secure the Maximo Asset Management J2EE application. This scenario installs a new instance of IBM Tivoli Directory Server 6.2 with a new instance of DB2. If you want to use Active Directory Server as your directory server, choose one of the other deployment scenarios. v J2EE server The J2EE server is the application server that serves and manages the Maximo Asset Management application. This scenario installs a new instance of IBM WebSphere Network Deployment 6.1. If you want to use Oracle WebLogic Server as your J2EE server, follow the instructions in the manual deployment chapter. A directory server can be configured to secure the J2EE server deployment. The J2EE component includes the following subcomponents: IBM HTTP Server You can install a new instance of IBM HTTP Server to act as the primary HTTP server. IBM HTTP Server Plugin

48

Installation Guide:

You can install a new instance of IBM HTTP Server Plug-in to provide communications between IBM HTTP Server and the J2EE server. In this scenario, the middleware installer deploys software on a single computer. To deploy middleware on multiple computers, choose an alternative deployment scenario.

Middleware installer workspace


The 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 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 middleware installer before a different set of features and products can be deployed. The composition and details of the deployment, as well as any logs generated by the middleware installer process are located in the workspace. By default, the 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 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 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 Maximo Asset Management 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 Maximo Asset Management middleware, this file will have to be copied to the workspace of each machine where Maximo Asset Management middleware is being deployed. The contents of this file can be used by the Maximo Asset Management installation program to populate its panels with meaningful default values.
Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

49

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 Maximo Asset Management middleware itself are also contained in this directory.

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. 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.

Activating the deployment plan


After you generate the deployment plan 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 Maximo Asset Management. 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.

Installing middleware with the Tivoli middleware installer


The Tivoli middleware installer provides an installation wizard that guides you through installing middleware required for a Maximo Asset Management system.

50

Installation Guide:

Before you begin


These instructions are for the installation on a single computer of a complete set of middleware for use with Maximo Asset Management, based on default values. This deployment scenario is suitable for demonstration, test, or training purposes. For a production environment, installing middleware on multiple computers improves performance and load-balancing. To deploy middleware on multiple computers, you must run the Tivoli middleware installer on each computer, choosing which middleware component to install on each. If you want to configure existing middleware products for use with Maximo Asset Management, follow the instructions for that deployment scenario. In some cases, information about the Tivoli middleware installer screens is not correctly displayed when installing through a remote session. To avoid such a problem, run the Tivoli middleware installer locally on the system that is to host the middleware. If you do encounter the problem, first minimize and then maximize the install wizard to redisplay the screen. Do not install multiple middleware products into the same custom directory. For example, when installing DB2 and WebSphere on the same computer, you cannot install both in a C:\ISM_middleware directory. You can, however, install them in C:\ISM_middleware\DB2, C:\ISM_middleware\ITDS, and C:\ISM_middleware\WAS. You also cannot install one middleware product in a custom directory and then install another middleware product in a subdirectory of that custom directory. For example, if you install WebSphere Application Server Network Deployment into C:\ISM_middleware, you cannot then install IBM Tivoli Directory Server into C:\ISM_middleware\ITDS. Do not use localhost for host name values in the installation program. Specify the fully qualified host name of the system on which you are installing. For Linux or UNIX systems, if the hostname -f command does not return a fully qualified host name, consult the system documentation for assistance. For Windows systems, 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. 4. The Computer Name Changes panel is displayed. 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. Verify that the Primary DNS suffix field displays a domain name, and then click OK. From the Computer Name Changes panel, click OK. Click Apply and close the System Properties panel.

5. 6. 7.

When installing and configuring middleware in the middleware installation program and the Maximo Asset Management installation program, consider the following special characters restrictions:

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

51

Table 11. Middleware object naming conventions Middleware object DB2 naming conventions for Group names, user names, and user IDs. Description Group names and user IDs on Linux and UNIX operating systems can contain up to eight characters and must consist of lowercase characters only. Group names and user names on Windows OS can contain up to 30 characters. Names and IDs cannot be any of the following values: USERS, ADMINS, GUESTS, PUBLIC, LOCAL, or any SQL-reserved word. Names and IDs cannot begin with IBM, SQL or SYS. They must also not begin with the underscore (_) character. DB2 naming conventions for DB2 instances. Instance names can have up to eight characters. On Windows, no instance can have the same name as a service name. DB2 naming conventions for passwords. For UNIX systems, passwords can be a maximum of eight characters. For Windows systems, passwords can be a maximum of 14 characters. IBM Tivoli Directory Server conventions for databases and database aliases. Database names must be unique within the location in which they are cataloged. For Linux and UNIX, this location is a directory path. For Windows OS, it is a logical disk. Database alias names must be unique within the system database directory. When a new database is created, the alias defaults to the database name. As a result, you cannot create a database using a name that exists as a database alias, even if there is no database with that name. Database and database alias names can have up to eight characters. The special characters @, #, and $ are not common to all keyboards. Avoid using these characters when creating a database name.

52

Installation Guide:

Table 11. Middleware object naming conventions (continued) Middleware object IBM Tivoli Directory Server conventions for users, groups, databases, and instances Description Do not use values that are longer than eight characters. Do not use: USERS, ADMINS, GUESTS, PUBLIC, LOCAL, or idsldap as values. Values cannot begin with IBM, SQL, or SYS. Values must not include accented characters. Values can include characters A through Z, a through z, and 0 through 9. Values must begin with characters A through Z or a through z. Do not use double-byte characters in administrator passwords. Passwords cannnot contain the following special characters: ` ' \ " | WebSphere Application Server Network Deployment The administrator name cannot contain the following characters: / \ * ,: ;=+?|< > & % '"] [> # $ ~ ( ) ! The administrator name cannot begin with a period. The administrator name cannot contain leading and trailing spaces. The administrator password must consist of eight characters. Middleware installation program The middleware installation program does not validate that your password is compliant with the operating system of the target host. Ensure that the password values you provide are valid for your environment. You cannot use the '%' character on Windows OS, or !, $, #, % characters on Linux and UNIX OS. The middleware installation program does not check for accented characters in user name values. The use of accented characters can cause errors.

Important: When entering LDAP values in the Maximo Asset Management installation wizard, in LDIF files, or into the directory server, follow the product-specific syntax rules for using special characters in an LDAP string. In most cases, you must precede special characters with an escape character in order to make it readable by the directory server. Failing to escape special characters in an LDAP string used with Maximo Asset Management can cause 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
Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

53

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 Maximo Asset Management errors that will be difficult to troubleshoot. See the product documentation for your directory server for more information on special characters in LDAP strings. If the middleware installation program reports that you have insufficient disk space to install middleware, you must increase the available disk space on the system, and then restart the middleware installation program. When you run the middleware installation program, you are prompted for user IDs to initiate the installation of DB2, WebSphere Application Server Network Deployment, and IBM Tivoli Directory Server. You can either supply an existing system user ID, or allow the middleware installation program to create a new user ID. The installation can fail if you specify an existing user account to install DB2 or IBM Tivoli Directory Server and that user account is not located under the /home directory. If you run the middleware installation program from a Linux or UNIX terminal window, you must be logged in as a user with administrative authority (root). If you are logged in as another user, and plan to use the su command in order to use the shell of the administrative user, you will encounter errors during the installation ofIBM Tivoli Directory Server. During installation, the middleware installation program sets environmental variables that must be set for the administrative user. If you encounter the following error, it indicates that you are attempting to use the 64-bit middleware installation program executable (mwi-AMD64.exe) on a 32-bit Windows system.
CreateProcess failed ==> The image file %1 is valid, but for a machine type other than the current machine

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

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

About this task


1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad. a. Start the launchpad: Windows OS On the DVD titled Maximo Asset Management 7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.exe. Linux or UNIX OS On the DVD titled Maximo Asset Management 7.1, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh.

54

Installation Guide:

Typically, when you launch the middleware installation program from the launchpad, the middleware installation program files are copied from the media to a temp directory on the system. You can use the following setup scripts to launch the middleware installation program directly and prevent the installer from copying the files to the system. Windows OS
\mam_launchpad\Install\MWI\setupwin.bat /l

Linux or UNIX OS
\mam_launchpad\Install\MWI\setupUNIX.sh -l

The following errors can occur when using the setup scripts.
Table 12. Middleware installation program setup script error codes Error Code 11 Error Unsupported operating system Description The middleware installation program or one of the middleware products cannot run on this operating system. The middleware installation program or one of the middleware products is not supported on this Linux kernel. Currently only Red Hat and SuSE are supported. The middleware installation program is supported on Linux 32/64 bit mode and on AIX 64 bit mode. The middleware installation program or one of the middleware products is not supported on this processor architecture. Currently only x86 and AMD64 architecture are supported. The environment variable must be set to the middleware installation program install files location: Windows OS LaunchPadBatchPath Linux or UNIX OS mwi_launchpadroot 22 The middleware installation program executable file not found The middleware installation program install file is missing or not accessible. Check to ensure the specified file exists in the current directory. The middleware installation program or one of the middleware products requires a fully-qualified host name defined.

12

Unsupported Linux distribution

13

Unsupported kernel bit mode

14

Unsupported Processor architecture

21

Env variable mwi_launchpadroot(UNIX) / LaunchPadBatchPath(Win) is not set

31

Host name is not a fully-qualified domain name.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

55

Table 12. Middleware installation program setup script error codes (continued) Error Code 32 Error SELinux is enabled or set in Enforcing mode Description Middleware product installation fails with the following error: JRE could not be found on the system Disable SELinux using one of the following methods: v setenforce 0 v Add the following entry to the /etc/system file: set fmac_enforcing = 0

33

The library libstdc++.so.5 (64-bit) is not installed.

The installer requires libstdc++.so.5 (64-bit) It should be located in /usr/lib64/libstdc++.so.5. If the system does not have this library installed, search for an RPM package (64-bit) compatible with system that contains this library and install it. The installer requires libstdc++.so.5. It should be located in /usr/lib/libstdc++.so.5. If the system does not have this library installed, search for an RPM package compatible with system that contains this library and install it.

34

The library libstdc++.so.5 is not installed.

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 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.

56

Installation Guide:

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 stores information about the attributes and history of each asset and about the relationships between assets. 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 Maximo Asset Management middleware, you can supply the directory server you will use to secure it. Your choices are to secure with an existing instance of IBM Tivoli Directory Server, or an existing instance of Microsoft Active Directory. The Tivoli Middleware Installer does not install WebLogic Server; to use it as your J2EE server you must install it manually. See the Deployment of Maximo Asset Management with manual configuration of middleware for instructions. 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 Maximo Asset Management 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. In the Configurable Host Name panel, if you want to manually specify the host name of the machine you are running the installation from, select the Override the local machine hostname option, enter a value in the Hostname field, and then click Next. Select this option only if you want to manually specify the host name of the system instead of having the installation program programmatically detect it. This option is useful when there is more than a single host name assigned to the system, such as in cases where a system has more than one network interface, or it is configured to support virtual IP addresses. When this option is selected, you are required to provide a resolvable host name. You cannot deselect this option once it has been selected, however, you will be able to change the value of the Hostname field. If you launched the middleware installation program from the command line using the forceHostname=true parameter, then you will be required to provide an alphanumeric value in the Hostname field. An IP address will result in an error message. Once this option has been selected, you will not be able to deselect it. However, you can change the value you enter in the Hostname field. 11. In the password reuse panel, you can optionally select Use this password as the value for all subsequent passwords, enter a password value, and then click Next, which will allow you to use the same password as the default user
Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

57

password value in all panels of the middleware installation program. If you do not wish to use this option, ignore the Use this password as the value for all subsequent passwords option, and click Next. 12. Enter the following configuration parameters for DB2 Enterprise Edition Server and then click Next. Install location Enter the location to install DB2. Windows OS: Default is C:\Program Files\IBM\SQLLIB Linux or UNIX OS: Default is /opt/IBM/db2/V9.5 DB2 Administration Server username Enter the DB2 administrative account name. Windows OS: Default is db2admin Linux or UNIX OS: Default is dasusr1 DB2 Administration Server password Enter the password for the DB2 administrative account. Fenced user (Linux or UNIX OS only) Enter a system user ID that can be used as a DB2 fenced user account. Default fenced user is db2fenc1 Note: During installation, the middleware installation program will automatically create the following default instances ofDB2: Windows OS DB2 Linux or UNIX OS db2inst1 The password for the default instance is the same password provided for the DB2 Administration Server password (DAS) 13. Enter the following configuration parameters for the default database instance, and then click Next. Default Instance Name Enter the name of the default database instance. The default for Windows systems is ctginst1. For all other systems, the default is db2inst1. Default Instance Port Enter the port that the default database instance will use. The default for Windows systems is 50005. The default for all other platforms is 50000. Default Instance Username Enter the user name for the default database instance. Windows OS: Default is db2admin

58

Installation Guide:

Linux or UNIX OS: Default is db2inst1 Default Instance Username Password Enter the password for the default database instance user name. 14. Enter the following configuration parameters for the Maximo Asset Management database instance, and then click Next. Instance name Enter the name of the Maximo Asset Management database instance. Default for all platforms is ctginst1 Port Enter the port that the Maximo Asset Management database instance will use. Default for all platforms is 50005. Instance username Enter the user name for the Maximo Asset Management database instance. Windows OS: Default is db2admin Linux or UNIX OS: Default is ctginst1 Instance username password Enter the password for the Maximo Asset Management database instance user name. 15. Enter information about the DB2 user groups: DB2 administrators group Enter the name of the DB2 administrators group. Windows OS: Default is DB2ADMNS Linux or UNIX OS: Default is db2grp1 DB2 users group (Windows only) Enter the name of the DB2 users group. Default is DB2USERS 16. Enter the following configuration parameters for IBM Tivoli Directory Server, and then click Next. Install location Enter the location to install IBM Tivoli Directory Server. Windows OS: Default is C:\Program Files\IBM\LDAP\V6.2 Linux or UNIX OS: Default is /opt/IBM/ldap/V6.2 Administrator distinguished name Enter the distinguished name of the IBM Tivoli Directory Server administrator. Default for all platforms is cn=root.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

59

Administrator password Enter the password for the IBM Tivoli Directory Server administrator. 17. 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 Maximo Asset Management. 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 Maximo Asset Management. 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. Default for all platforms is 3539. 18. 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. 19. 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.

60

Installation Guide:

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 20. 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 Bind password Enter the password for the bind distinguished name. 21. Enter the following configuration parameters for WebSphere Application Server Version, and then click Next. Install location Enter the location to install WebSphere. Windows OS: Default is C:\Program Files\IBM\WebSphere\AppServer Linux OS: Default is /opt/IBM/WebSphere/AppServer UNIX OS: 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. 22. Enter the following configuration parameters for WebSphere Application Server, and then click Next.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

61

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. 23. 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. Application server name Enter the name of the WebSphere application server. Default for all platforms is MXServer Update Installer install location Enter the location where the WebSphere update installer will be installed. Windows OS: Default is C:\Program Files\IBM\WebSphere\UpdateInstaller Linux OS: Default is /opt/IBM/WebSphere/UpdateInstaller UNIX OS: Default is /usr/IBM/WebSphere/UpdateInstaller 24. Enter the following configuration parameters for IBM HTTP Server, and then click Next. Install location Enter the location to install IBM HTTP Server. Windows OS: Default is C:\Program Files\IBM\HTTPServer Linux OS: Default is /opt/IBM/HTTPServer UNIX OS: 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.

62

Installation Guide:

Default for all platforms is 8008. 25. In the Configuration Parameters for WebSphere Application Server plugin for the IBM HTTP Server, the default profile name is ctgAppSvr01. You cannot change this value. To accept the value, click Next. 26. Specify the location of the Maximo Asset Management 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 Maximo Asset Management 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 file system directory that already contains all of the Maximo Asset Management middleware installation images. 27. If you selected the option to copy install images from the source media, specify the source and destination directories, and then click Next. If you selected the option to specify a directory that already contained the middleware images, specify that directory, and then click Next. 28. Specify a directory to use for Tivoli middleware installer temporary files and extracted middleware installation images, and then click Next. 29. From the Deployment Plan Operation panel, select Deploy the plan, and then click Next. You can also elect to make changes to the deployment plan or parameters you have previously configured from this panel. 30. 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. 31. When the deployment completes successfully, click Finish to exit the installation wizard.

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:
Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

63

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. 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.

64

Installation Guide:

Log files generated by the native middleware installation programs will also be kept here.

Installing Maximo Asset Management and automatically configuring middleware


To automatically configure middleware when you install Maximo Asset Management follow these instructions. The IBM Maximo installation wizard guides you through the product installation. The program records deployment and configuration parameters that you select in each screen, and then installs and deploys the product based on this information. You can install middleware on any platform, but you must run the IBM Maximo installation program from the administrative workstation which must be installed on a supported Windows system. Values that you supply to the IBM Maximo installation program are stored in the maximo.properties file, the install.properties file, and in the Maximo database. These values are retrieved and populated into installation screen fields if you run the installation program again. If you cancel the installation program after entering values in several screens, the installation program reuses most of those values the next time you start the installation program. Values that are not reused are the installation directory and the shortcut option you chose for a previous installation. To restore the defaults for a fresh installation, delete the old maximo.properties file and the install.properties file which are stored in the MAM_HOME/maximo/ applications/maximo/properties/ directory. You must also delete the information in the MAXTEMP table in the database.

Simple install path values


Put your short description here; used for first paragraph and abstract. If you elect to install Maximo Asset Management using the simple install path, the following values are set. You will be able to provide values where indicated.
Table 13. Maximo Asset Management Simple Install Path Values Category Deployment Option 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 yes 50005 maxdb71 ctginst1 Yes Value simple DB2 Yes Provided by User?

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

65

Table 13. Maximo Asset Management Simple Install Path Values (continued) Category Database Configuration Database Configuration Field Remote Access User ID Database Install Directory Windows OS C:\Program Files\IBM\ SQLLIB Linux or UNIX OS /opt/IBM/ db2/V9.5 Database Configuration Instance Administrator User ID Windows OS db2admin Linux or UNIX OS ctginst1 Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration WebSphere Connectivity WebSphere Connectivity WebSphere Configuration Windows Service User ID db2admin Yes Value Provided by User? Yes

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 OS C:\Program Files\IBM\ WebSphere\ AppServer Linux /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer

AIX

Sun Solaris /opt/IBM/ WebSphere/ AppServer HP-UX /opt/IBM/ WebSphere/ AppServer WebSphere Configuration User name wasadmin Yes

66

Installation Guide:

Table 13. Maximo Asset Management Simple Install Path Values (continued) Category WebSphere Configuration WebSphere Configuration WebSphere Configuration 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 Profile name Value ctgDmgr01 Provided by User?

Automate WebSphere yes Configuration Remote Access User ID Web server port 80 Yes

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

Running the Maximo Asset Management installation program


Use these instructions to install Maximo Asset Management and automatically configure middleware on multiple servers, using default values.

Before you begin


Before you start the installation program, ensure that the system meets the following conditions: v On the administrative workstation, temporarily shut down any non-critical processes that could have a negative effect on the installation, such as anti-virus software.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

67

v The middleware environment is installed and running properly. See the Troubleshooting chapter for instructions on restarting middleware if you need to do so. v Enable a remote execution and access service on every system with middleware installed. Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server. Remote access protocols include rsh, rexec, SSH and Windows SMB. If the remote system is a Windows server, you must configure remote execution and access to use SMB. v Perform the following tasks to prepare the DB2 database: If DB2 is installed on a Linux or UNIX system, you must create the instance user and the home directory for the user on the DB2 server. The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. The user ID for the DB2 instance administrator must have SYSADM (administration) authority. You enter this user ID on the DB2 Administration screen and on the Remote Access Authorization screen of the Maximo Asset Management installation program. See the DB2 product documentation for information about creating a user with SYSADM (administration) authority on the DB2 server. To avoid high system memory usage by DB2, you can set the following DB2 property and then restart the DB2 server:
db2 update dbm cfg using KEEPFENCED NO

If you had to shorten the TEMP and TMP environment variables when you installed DB2 on aWindows system, and you intend to install the product on the same system, redefine these variables before you begin the product installation. If you are plan to install Maximo Asset Management in a language other than English, you must accept the default values for database table space size and index table space size and these values are displayed as null during the installation. If you want to customize the table space sizes, you must either run the Maximo Asset Management installation program in English, manually configure the database, or modify the table space sizes after installation. v For WebSphere Application Server Network Deployment, ensure that the Cell and all related nodes are actively running. v The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed into that location. Automatic configuraton creates an empty Maximo database on the system. You can create a maxdemo database, including sample data, during the installation. To create a maxdemo database, complete either of following two procedures: v Enter a command to create a maxdemo database: 1. In the command line, navigate to the directory where the Maximo Asset Management files are extracted. 2. Change to the install\MAM\Install\new folder. 3. On a 32-bit Windows system, run the following command:
install.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes d

On a 64-bit Windows system, run the following command:


install_win64.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes

v When you are running the installation wizard, create a maxdemo database by performing the following tasks:

68

Installation Guide:

1. In the Run Configuration Step screen in the installation wizard (Step 31 in the procedure), select the Copy files now. Perform installation configuration later option. 2. When the installation finishes, exit the installation wizard. 3. Rename the ibm\smp\maximo\tools\maximo\en\maximo file. 4. Copy the ibm\smp\maximo\tools\maximo\en\maxdemo file to ibm\smp\maximo\tools\maximo\en\maximo. where en is the language folder and dbtype is ora/sqs/db2. 5. From a command prompt navigate to ibm\smp\scripts and run the following command:
taskrunner.bat CONTINUE STOPONERROR

Do not restart the computer after you copy files but before you run the taskrunner command because the taskrunner utility does not create a persistent store of information. 6. When taskrunner finishes running, rename the files back to their original names. When taskrunner successfully completes, r 7. Restart the installation program to continue with the license enablement If you intend to perform multiple installations of the product using the same administrative workstation, review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations.. When you are installing the product, specify the fully-qualified host name of the system for all host name values. If you are installing on a system using a system ID that contains Russian language characters, the installation fails with error message CTGIN2289E when attempting to install language packages. This circumstance causes a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E. To avoid this problem, install the product using a user ID with administrative authority that contains only English language characters. See the troubleshooting chapter for information about errors that occur during the installation.

About this task


To install Maximo Asset Management, follow these steps:

Procedure
1. Log in as Administrator on the Maximo Asset Management administrative system. 2. Ensure the database server, directory server, and application server services are running. 3. Start the Maximo Asset Management installation program from the launchpad. a. Start the launchpad. Navigate to the root directory of the product DVD or the downloaded installation image, and run the following command: launchpad.exe b. In the launchpad navigation screen, click Install the Product. c. Click Maximo Asset Management.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

69

Alternatively, you can start the Maximo Asset Management installation program directly. Navigate to \\Install\MAM\ on the product DVD or on the downloaded installation image and run one of the following commands: v install.exe v install_win64.exe Select a language for the installation and click OK. In the Introduction screen, click Next. In the Package Summary screen, review the package deployment actions, and then click Next. In the software license agreement screen, read the license information and select I accept both the IBM and the non-IBM terms. if you agree with the terms, and then click Next. In the Choose Install Folder screen, specify the install directory for Maximo Asset Management, and then click Next. Where Would You Like to Install? Enter the path to install Maximo Asset Management. By default, this value is C:\IBM\SMP. The path you specify must not contain spaces. 9. In the Choose Deployment screen, select the Custom option, and then click Next. Simple A simple installation deploys all Maximo Asset Management components on a single system. A simple installation does not support reuse of middleware. This deployment option is typically used for demonstration, proof-of-concept, or training purposes only. Custom A custom installation can deploy Maximo Asset Management components across several systems, and can reuse existing middleware components. This deployment option is typically used in a production environment. 10. In the Import Middleware Configuration Information screen, specify that you want to use the field values that you used with the middleware installation program as default values for those same fields in the Maximo Asset Management installation program and then click Next.. Import middleware configuration information Select this check box if you want to allow the Maximo Asset Management installation program to reuse values entered in the middleware installation program. The middleware default information is not used if you select the Simple deployment path. Host name Enter the host name of the system where the middleware installation program was run. User ID Enter the user ID that was used to run the middleware installation program. Password Enter the password of the user ID that was used to run the middleware installation program.

4. 5. 6. 7.

8.

70

Installation Guide:

Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. This file is found in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows and /root/ibm/tivoli/mwi/workspace for UNIX. 11. In the Database Type screen, select the DB2 database, and then click Next. 12. In the Database screen, enter configuration information about the database, and then click Next. Host name Enter the fully-qualified host name of the server hosting DB2. 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. 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. After you enter configuration information for the database, the Maximo Asset Management installation program connects to the database server to validate the information you have entered. 13. In the Automate Database Configuration screen, select Automate database creation and configuration, and then click Next. 14. In the Remote Access Authorization screen, enter authorization information for the automatic database configuration feature, and then click Next. User ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting the database to be used with Maximo Asset Management. This user ID must have administrative rights on the server you are accessing. For Windows OS, this user must be a member of the DB2ADMNS group.
Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

71

For Linux or UNIX OS, this user must be root and a member of a group with SYSADM authority for the database instance. Password Enter the password for the user ID. See the Remote configuration enablement topic in the Preparing to install Maximo Asset Management chapter for information about configuring remote access. 15. In the Database Administration screen, enter configuration information about the database, and then click Next. Installation directory Enter the directory where DB2 is installed. Windows OS This value might be C:\Program Files\IBM\SQLLIB Linux or UNIX OS This value might be /opt/IBM/db2/V9.5 Instance administrator user ID Enter the user ID for the administrator of the DB2 instance. Windows OS This value might be db2admin. Linux or UNIX OS This value might be ctginst1. This user ID cannot be the same as the database user ID. Instance administrator password Enter the password for the user ID of the administrator for theDB2 instance. 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. 16. In the Database Tablespace panel, enter information about the table space of the database, and then click Next. Data tablespace name Enter the name of the table space that is created in DB2 for Maximo. For all platforms, the default is MAXDATA. If the table space does not exist, it is created. Data tablespace size Enter a size, in megabytes, for the data table space. Temporary tablespace name Enter the name for the temporary table space to be created for DB2. Temporary table spaces hold data during sorting or collating actions. For all platforms, the default is MAXTEMP. If the table space does not exist, it is created.

72

Installation Guide:

Temporary tablespace size (Mb) Enter a size for the temporary table space. The default value is 1000 Mb. Index tablespace name Enter a name for the index table space. For all platforms, the default is MAXDATA. Index tablespace size Enter a size, in megabytes, for the index table space. The Maximo Asset Management installation program now connects to the database server and validates the information you entered. 17. When the database validation is completed, in the Application Server Type panel, select WebSphere Application Server Network Deployment as the application server to use, and then click Next. 18. In the WebSphere Connectivity panel, enter host information about the WebSphere Application Server Network Deployment, and then click Next. Host name Enter the fully-qualified host name of the system hosting WebSphere Application Server Network Deployment. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere Application Server Network Deployment system. The default value for this field is 8879. 19. In the Automate WebSphere configuration panel, select Automate WebSphere configuration, and then click Next. 20. In the WebSphere Remote Access Authorization panel, enter authorization information for WebSphere Application Server Network Deployment configuration, and then click Next. Operating system user ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting WebSphere Application Server Network Deployment. This user ID should have administrative rights on the server you are accessing. Operating system password Enter the password for the system user ID. 21. In the WebSphere Deployment Manager Configuration panel, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere Application Server Network Deployment is installed on the host system. Windows OS This value might be C:\Program Files\IBM\WebSphere\ AppServer Linux or UNIX OS This value might be /opt/IBM/WebSphere/AppServer or /usr/IBM/WebSphere/AppServer

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

73

User ID Enter the administrative user ID used to access the WebSphere Application Server Network Deployment Server. Default for all platforms is wasadmin. Password Enter the password for the administrative user ID used to access the WebSphere Application Server Network Deployment Server. Profile name Enter the name of the WebSphere Application Server Network Deployment profile. Default for all platforms is ctgDmgr01. 22. In the WebSphere Application Server Configuration panel, enter the following information, and then click Next. Web server port Enter the Web server port used by WebSphere Application Server Network Deployment. 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 Application Server Network Deployment node containing the application server. Default for all platforms is ctgNode01. Application server Enter the name of the WebSphere Application Server Network Deployment application server to associate with Maximo Asset Management. Default for all platforms is MXServer. This value can be customized. The application server is created if it does not exist. 23. In the Security panel, select a method for authenticating and authorizing users and groups, and then click Next. WebSphere application security for authentication and authorization Choose this option to automatically configure WebSphere Application Server Network Deployment application security to manage users and groups for authentication and authorization purposes. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. WebSphere application security only for authentication Choose this option to automatically configure WebSphere Application Server Network Deployment application security for authentication only and allow Maximo security to manage users and groups. With this option, you create all your users in your directory server, but you manage their membership in security groups in the base services Security Groups application. This option requires application security to already be enabled in WebSphere Application Server Network Deployment.

74

Installation Guide:

If you select this option, the next panel you encounter prompts you for your user base entry. The maxadmin, maxreg, and mxintadm users and MAXIMOUSERS and MAXADMIN groups must have been created before you proceed past this panel. Maximo security for authentication and authorization If you do not want to use WebSphere Application Server Network Deployment application security, select this option to have Maximo security manage users and groups for both authentication and authorization. 24. In the Specify Maximo users panel, enter the following information, and then click Next. Maximo administration user Product administrator user ID used for initial configuration and adding users. Default value is maxadmin. Password Password for the Maximo administration user. Maximo system registration user User ID used for the self registration of users. Default value is maxreg. Password Password for the Maximo system registration user. Maximo system integration user User ID used with enterprise adapters. Default value is maxintadm. Password Password for the Maximo system integration user. 25. In the Security panel, which you encounter if you chose to use WebSphere Application Server Network Deployment application security for authentication and authorization, specify the distinguished names of the user and group base entities you are using, choose how Maximo Asset Management users are created, and then click Next. User base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the user base entry you intend to use in this field. The default LDAP schema user base entry is ou=users,ou=SWG,o=IBM,c=US Group base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the group base entry you intend to use in this field. The default LDAP schema group base entry is ou=groups,ou=SWG,o=IBM,c=US Create the required users Keep this option selected to allow the Maximo Asset Management installation program to create default users in WebSphere Application Server Network Deployment Virtual Member Manager. This operation requires write access to Virtual Member Manager.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

75

If you do not want to have the users created by the Maximo Asset Management installation program, you will have to create them manually before continuing the Maximo Asset Management installation from this point. If you are not using the default LDAP schema provided with Maximo Asset Management, you must create it yourself before advancing beyond this panel. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask. Following is an example of the default add on ldif data you have to modify and import into your LDAP repository if you chose 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=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=maxadmin,ou=users,ou=SWG,o=IBM,c=US member: uid=mxintadm,ou=users,ou=SWG,o=IBM,c=US member: uid=maxreg,ou=users,ou=SWG,o=IBM,c=US cn: maximousers

26. In the Integration Adapter JMS Configuration screen, enter the following information, and then click Next. A JMS server requires a DB2 data repository to be configured to maintain messages. JMS Data Source name Enter intjmsds as the name of the data source to be used by JMS. Select whether the JMS data store should be persisted.

76

Installation Guide:

Persist JMS messages Select this option to enable theMaximo Asset Management installation program to set the JMS implementation to persist messages within DB2. Do not persist JMS messages If you select this option, the Maximo Asset Management installation program will not set the JMS implementation to persist messages automatically in DB2. You can configure the JMS implementation manually at a later date. If you select this option, when you click Next, the installation wizard skips to step 30, where you configure SMTP. 27. If you chose to persist JMS messages, in the DB2 Database Server Configuration panel, enter the following information, and then click Next. If you chose not to persist JMS messages, the wizard skips to step 30, and you do not see this screen. Note: The JMS data store can only be created as a DB2 database. Host name Enter the fully qualified host name of the server hosting the JMS data store. 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 data store. 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. 28. If you chose to persist JMS messages, in the DB2 Database Server Remote Access Authorization panel, enter authorization information for the automatic configuration feature, and then click Next .If you chose not to persist JMS messages, the wizard skips to step 30, and you do not see this screen. User ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting the JMS database. This user ID must have administrative rights on the server you are accessing. For Windows OS, this user must be a member of the DB2ADMNS group. For Linux or UNIX OS, this user must be root and a member of a group with SYSADM authority for the database instance. Password Enter the password for the user ID.

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

77

29. If you chose to persist JMS messages, in the DB2 Database Instance Configuration panel, enter the following information, and then click Next. If you chose not to persist JMS messages, the wizard skips to step 30, and you do not see this screen. Installation directory Enter the installation directory for the DB2 server that is hosting the JMS database that contains the instance to be used with WebSphere Application Server Network Deployment. Windows OS This value might be C:\Program Files\IBM\SQLLIB Linux or UNIX OS This value might be /opt/IBM/db2/V9.5 Instance Enter the JMS database instance to be used with WebSphere Application Server Network Deployment. For all platforms, the default is ctginst1 Instance administrator user ID Enter the user ID of the administrator for the JMS database instance. Windows OS This value might be db2admin. Linux or UNIX OS This value might be ctginst1. Instance administrator password Enter the password for the user ID of the administrator for the JMS database instance. 30. In the SMTP Configuration panel, specify SMTP configuration information used by workflows to communicate with workflow participants, and then click Next. SMTP server Enter the fully qualified host name of the SMTP server that sends messages to participants. Administrator e-mail Enter a valid e-mail address. This address is to send messages. You can defer SMTP configuration at this time by not providing any information for this panel and clicking through to the next panel. However, you must configure these parameters through the product interface as a post installation task which is described in Configuring SMTP on page 210. 31. From the Run Configuration Step panel, decide how you would like to perform the configuration step of the installation, and then click Next. a. Choose when you would like to run the configuration step: Perform installation configuration now Select this option to have the installation program perform the configuration step during installation. Copy files now. Perform installation configuration later. Select this option to have the installation program copy files to the system only.

78

Installation Guide:

The Maximo Asset Management installation program is used to complete three tasks: gathering information about your Maximo Asset Management deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting this option, you can instruct the Maximo Asset Management installation program to gather your configuration information and copy Maximo Asset Management 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 <MAM_HOME>maximo\applications\maximo\properties\ maximo.properties file. You can run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility, located in the <MAM_HOME>\scripts directory. Run the taskrunner utility from the command line, and it uses the configuration values stored in the maximo.properties file to configure Maximo Asset Management.
<MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

Note: If you reboot the system, you are not able to use the taskrunner utility to run configuration scripts. Taskrunner data stores are not persisted. If you intend to use the taskrunner utility, do not reboot your system. In the case of an installation failure, the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. b. Choose how to deploy application files. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. Deploy application files manually later Select this option to defer the deployment of application files. Deferring the deployment of application files can shorten the time it takes to deploy overall if you intend to install more than one service management product. Files can be deployed once all products have added their own functions to the application files. You might also want to use this option if your organization has application deployment restrictions that require that you deploy application files either manually or through another approved process. See the instructions for manually configuring WebSphere Application Server in the Deployment of .Maximo Asset Management with manual configuration of middleware. 32. In the Choose Shortcut Folder panel, select the type of shortcut you would like to arrange for Maximo Asset Management, 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 Maximo Asset Management shortcuts in a new program group.
Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

79

In an existing Program Group Select this option and choose the name of an existing program group to store Maximo Asset Management shortcuts. In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. In order to use the Start Menu shortcut with Internet Explorer, ensure that you have added the Maximo Asset Management 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 Maximo Asset Management on the desktop. In the Quick Launch Bar This option must not be used. 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 Maximo Asset Management shortcuts. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. Create Icons for All Users Select this option if you would like Maximo Asset Management desktop icons to appear on the desktop for all system users. 33. In the Input Summary panel, review the information you have provided to the Maximo Asset Management installation program, and then click Next. Use the Previous button to return to previous panels to make changes. 34. In the Pre-Installation Summary panel, review the installation information presented, and then click Install. The installation task begins. Progress can be monitored by viewing messages displayed above the progress bar. 35. In the Install Complete panel, click Done.

What to do next
When the Maximo Asset Management installation program has completed installation and configuration tasks, it will exit.

Completing post-installation tasks


To complete the deployment, you must perform several additional tasks after the installation. If you intend to support multiple languages in Maximo Asset Management, install the language pack before performing other configuration tasks. See the Deployment of optional packages chapter for language pack installation instructions. The chapter also describes how to install process solution packages, including process manager products and integration modules. The Post-installation configuration chapter describes the configuration tasks to complete within the product user interface.

80

Installation Guide:

Deploying the confhelp.properties file


The confhelp.properties file must be deployed to enable the help system for the product.

Before you begin About this task


To deploy the confhelp.properties file, complete the following steps:

Procedure
1. Ensure you are logged into the administrative workstation. 2. Run the following command:
<MAM_HOME>\jacl\solutions\Sendfile.bat <WASDeploymentManagerHostName> <WASRemoteAccessUserName> <WASRemoteAccesspassword> "<MaximoInstallLocation>\applications\maximohelp \helpweb\webmodule\WEB-INF\confhelp.properties" "<WASInstallLocation>\properties" "confhelp.properties"

Verifying the installation


After you have exited the Maximo Asset Management installation program without encountering any errors, you can further verify that the installation completed successfully by locating key artifacts and performing a few simple tasks.

Before you begin


The product installation program performs installation verification, or a health check, by logging into the product before exiting the installation. The product installation program returns a success message if all installation steps, including the product log in task, are successful. If the health check task is unsuccessful, a HealthCheckFailed error thrown for the getUrlContentString function will be found in the <MAM_HOME>\logs\CTGInstallTraceXX.log file, where XX is a two digit number such as 00. For more information about log files and troubleshooting errors encountered during the installation, refer to Troubleshooting the product installation program on page 239.

About this task


To further verify that the Maximo Asset Management installation was completed successfully, perform the following verification procedures:

Procedure
1. Examine the CTGInstallTrace00.log file for success messages. The following success messages are found in the CTGInstallTrace00.log file and can be used to verify which phases of the installation were successful: v CTGIN2114I: The database was created successfully v CTGIN2135I: Tablespace maxdata created successfully v CTGIN2135I: Tablespace maxtemp created successfully

Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware

81

v CTGIN2079I: Base services database configuration completed successfully (This message indicates that maxinst finished successfully.) v CTGIN2222I: WebSphere Application Server creation successful v CTGIN2188I: Creation and configuration of service integration bus successfully completed v CTGIN2184I: Creation and configuration of JMS resources successfully completed v CTGIN2310I: Application server security was successfully enabled for the base services v CTGIN2253I: buildmaximoear.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMO was successful v CTGIN2253I: buildhelpear.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMOHELP was successful v CTGIN2208I: runConfigurationStep completed successfully v CTGIN2370I: The installation finished successfully If you chose the option of having the installation program automatically configure WebSphere Application Server Network Deployment, the following messages, found in the CTGInstallTrace00.log file, indicate the configuration was successful:
<symptom>CTGIN2228I.*client</symptom> <symptom>CTGIN2230I.*node</symptom> <symptom>CTGIN2232I.*NodeAgent</symptom> <symptom>CTGIN2240I.*server</symptom> <symptom>CTGIN2238I.*security</symptom>

Search the CTGInstallTrace00.log file for the following message, which indicates that the maxinst task completed successfully:
CTGIN2079I, maxinst.*completed

2. Compare the packages chosen for installation with the packages that were installed. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages that will be installed. You can compare the contents of that panel with a listing of what was actually installed on the system. Use the solutioninstaller command to list installed packages:
<MAM_HOME>\bin\setupPSIenv.bat <MAM_HOME>\bin\solutionInstaller.bat -action showInstalled -all

The resulting list should match the packages listed in the Package Summary panel. 3. Log into the product and verify applications are present. Being able to log into the product manually is a good indicator that the installation was successful. Once you have logged in, navigate through the GoTo menu to verify that it has been populated with the applications you expect.

82

Installation Guide:

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware
This deployment option uses Maximo Asset Management installation programs and tools to automatically configure existing middleware.

Before you begin


Review the information in the planning and preparation chapters, including completing the planning worksheets.

About this task


In this scenario, you use the middleware installation program and the Maximo Asset Management installation program to automatically configure existing middleware resources before deploying the product itself.

Run the middleware installation program on existing middleware servers

Install IBM Maximo Asset Management and automatically configure middleware

Verify the installation

Perform post-installation tasks

Figure 1. Deploying Maximo Asset Management reusing existing middleware

Procedure
1. Install and configure middleware using the middleware installation program. 2. Install Maximo Asset Management and perform additional middleware configuration tasks. 3. Verify the installation. 4. Complete post-installation tasks
Copyright IBM Corp. 2007 - 2010

83

What to do next
After you complete the deployment, you can optionally perform the following tasks: v Install additional languages. v Install process solution packages

Installing existing middleware using the middleware installation program


You can reuse some middleware servers for use in a Maximo Asset Management deployment. The middleware installation program can identify components that exist on the system that are compatible with Maximo Asset Management. and can configure them for use with Maximo Asset Management If you intend to reuse middleware servers, you must configure them before you run the Maximo Asset Management installation program. With the Tivoli middleware installer, you can reuse an existing DB2 server, an IBM Tivoli Directory Server, or a Microsoft Active Directory server and configure them automatically for use with Maximo Asset Management. You can manually configure these components, for example, if your enterprise has security policies that prohibit automatic configuration. See the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions. If you want to reuse other middleware components, such as an Oracle Database, an Oracle WebLogic Server, or a Microsoft SQL Server, you must configure them manually. See the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions.

Reusing DB2
You can use the Tivoli middleware installer to configure an existingDB2 server for use with Maximo Asset Management.

Before you begin


Check that your version of DB2 is supported in the prerequisites topic in the Preparing to install Maximo Asset Management chapter.DB2 8.2 is incompatible with the IBM Tivoli Directory Server 6.2. You must use a later version of DB2 if you want to use IBM Tivoli Directory Server 6.2 in your deployment. Before using the middleware installation program to configure an existing DB2 server, you must create a set of users and groups that are used by the middleware installation program during configuration. The default values are: Users v db2admin (Windows OS) v dasusr1 (Linux or UNIX OS) v db2fenc1 ((Linux or UNIX OS) Groups v db2admns (Windows OS) v dasadm1 ((Linux or UNIX OS)

84

Installation Guide:

v dbgrp1 ((Linux or UNIX OS) v db2fgrp1 ((Linux or UNIX OS) These are default values which you can customize. If you use different values, ensure that you provide matching values when you run the middleware installation program. If these users do not exist on the system, you must create them before running the installation program.

About this task


To use the middleware installation program to configure an existing instance of DB2 for reuse with Maximo Asset Management, complete the following steps:

Procedure
1. Login as a user with administrative authority. 2. Launch the middleware installation program from the launchpad. 3. Navigate the screens of the installation wizard until you reach the Deployment Choices screen. 4. In the Deployment Choices screen, select onlyDatabase Server, and then click Next. The middleware installation program displays any instances of DB2 that it finds on the system. 5. From the Installation drop-down menu, select the instance you want to reuse, and then click Next. 6. Complete the installation by navigating the remaining screens in the installation wizard.

Reusing IBM Tivoli Directory Server


If you want to reuse an existing IBM Tivoli Directory Server installation with Maximo Asset Management, you can verify that it will work with Maximo Asset Management using the middleware installer.

About this task


The middleware installer validates the following items: v The version of IBM Tivoli Directory Server is compatible with Maximo Asset Management. v The IBM Tivoli Directory Server is running. v The Base DN information that you supply in the middleware installer screens is present in the IBM Tivoli Directory Server you are using. The middleware installer does not create a new instance of IBM Tivoli Directory Server for use with Maximo Asset Management. To reuse an existing instance of IBM Tivoli Directory Server, supply the correct Administrator Distinguished Name and password, LDAP BASE DN, directory server port, and the administration port information for that instance on the middleware installer panels when prompted. To host a new instance on your existing IBM Tivoli Directory Server, you must create it before running the middleware installer. Note: While you can technically share a DB2 instance between Maximo Asset Management and the one required by IBM Tivoli Directory Server, it is not a recommended practice. During the installation, the database instance is restarted, which could disrupt the availability of IBM Tivoli Directory Server in your enterprise. If you are using the automated installers, separate instances are created for use by Maximo Asset Management and IBM Tivoli Directory Server.
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

85

To verify an existing instance of IBM Tivoli Directory Server for reuse with Maximo Asset Management, complete the following steps.

Procedure
1. Log into the system as a user with administrative authority. 2. Launch the middleware installer from the product launchpad. 3. Navigate the screens of the installation wizard until you reach the Deployment Choices screen. 4. In the Deployment Choices panel, select Directory Server, and then click Next. The middleware installer displays any instances of IBM Tivoli Directory Server it finds on the system. 5. In the Installation drop-down menu, select the instance that you want to reuse, and then click Next. 6. Complete the installation by navigating the remaining installation wizard screens.

PreparingMicrosoft Active Directory for reuse


If you have an existing instance of Microsoft Active Directory, you can use it to secure WebSphere Application Server Network Deployment when you install it on the system.

Before you begin


Before running the Maximo Asset Management installation program, you must manually create the necessary users and groups. You can perform this task after you run the middleware installation program, but you must complete it before you run the Maximo Asset Management installation program.

About this task


The middleware installation program prompts you for LDAP configuration parameters to use with WebSphere Application Server Network Deployment. To use an existing Microsoft Active Directory instance to secure WebSphere Application Server Network Deployment, complete the following steps:

Procedure
1. Login as a user with administrative authority. 2. Launch the middleware installation program from the launchpad. 3. Navigate the installation wizard screens until you reach the Deployment Choices screen. 4. In the Deployment Choices screen, select only the Directory Server deployment option, and then click Next. In the next screen, select the Microsoft Active Directory to secure WebSphere Application Server Network Deployment option, and then click Next. 5. In the Deployment Plan Summary screen, click Next to configure the parameters. The deployment plan is generated and details of the plan are provided. 6. Optional: In the Configurable Host Name screen, if you want to manually specify the host name of the machine you are running the installation from, select the Override the local machine hostname option and enter a host name value in the Hostname field. Select this option only if you want to manually

86

Installation Guide:

specify the host name of the system instead of having the installation program programmatically detect it. This option is useful when there is more than a single host name assigned to the system, for example where a system has more than one network interface, or it is configured to support virtual IP addresses. When this option is selected, you must provide a resolvable host name. You cannot deselect this option after selecting it but you can change the value of the Hostname field. If you launched the middleware installation program from the command line using the forceHostname=true parameter, you are required to provide an alphanumeric value in the Hostname field. An IP address will result in an error message. 7. Optional: In the password reuse screen, you can select Use this password as the value for all subsequent passwords and enter a password value. This option allows you to use the same password as the default user password value in all screens of the middleware installation wizard. 8. Select Secure with Microsoft Active Directory, and click Next. 9. Configure the following values for WebSphere Application Server Network Deployment security, and then click Next. LDAP Host name Enter the fully-qualified name of the server hosting Microsoft Active Directory. Directory server port Enter the directory server port. For example, 389 LDAP base entry Enter the LDAP base entry of the instance. For example, DC=ism71,DC=com User suffix Enter the user suffix for the instance. For example, OU=Users,OU=SWG,DC=ism71,DC=com Group suffix Enter the group suffix for the instance. For example, OU=Groups,OU=SWG,DC=ism71,DC=com Organization container suffix Enter the organization container suffix for the instance. For example, DC=ism71,DC=com In this example. ism71 is the domain name. Replace ism71 with the name of your own domain. 10. Supply the following configuration values for WebSphere Application Server Network Deployment security, and then click Next. Bind distinguished name Enter the bind distinguished name for the instance. For example, CN=Administrator,CN=Users,DC=ism71,DC=com This value assumes that the Administrator user is already a member of the ism71 domain. Replace ism71 with the name of your own domain. Bind password Enter the password for the Administrator user on the system hosting Microsoft Active Directory. 11. Complete the installation by navigating the remaining installation wizard screens.
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

87

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. 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.

88

Installation Guide:

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.

Reusing middleware with the Maximo Asset Management installation program


Use these instructions to install Maximo Asset Management and automatically configure middleware on multiple servers, using default values.

Before you begin


Before you start the installation program, ensure that the system meets the following conditions: v On the administrative workstation, temporarily shut down any non-critical processes that could have a negative effect on the installation, such as anti-virus software. v For Linux or UNIX systems with middleware installed, the command hostname -f must return a fully-qualified host name. If necessary, consult the documentation for your operating system to ensure this. v If you experience problems with the user interface of the installation program when installing on AIX 6 systems remotely, reattempt the installation locally on the system through the console or an x terminal. v The middleware environment is installed and running properly. See the Troubleshooting chapter for instructions on restarting middleware if you need to do so. v Enable a remote execution and access service on every system with middleware installed. Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server.
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

89

Remote access protocols include rsh, rexec, SSH and Windows SMB. If the remote system is a Windows server, you must configure remote execution and access to use SMB. v Perform the following tasks to prepare the DB2 database: If DB2 is installed on a Linux or UNIX system, you must create the instance user and the home directory for the user on the DB2 server. The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. The user ID for the DB2 instance administrator must have SYSADM (administration) authority. You enter this user ID on the DB2 Administration screen and on the Remote Access Authorization screen of the Maximo Asset Management installation program. See the DB2 product documentation for information about creating a user with SYSADM (administration) authority on the DB2 server. To avoid high system memory usage by DB2, you can set the following DB2 property and then restart the DB2 server:
db2 update dbm cfg using KEEPFENCED NO

If you had to shorten the TEMP and TMP environment variables when you installed DB2 on aWindows system, and you intend to install the product on the same system, redefine these variables before you begin the product installation. If you are plan to install Maximo Asset Management in a language other than English, you must accept the default values for database table space size and index table space size and these values are displayed as null during the installation. If you want to customize the table space sizes, you must either run the Maximo Asset Management installation program in English, manually configure the database, or modify the table space sizes after installation. v If you are using Oracle 10 with Maximo Asset Management, ensure that the Oracle 10gR2 patch 3 is installed. Automatic configuration of Oracle 9 is not supported. If you plan to use Oracle 9 in the Maximo Asset Management system, follow the instructions in the Deployment of Maximo Asset Management with manual configuration of middleware chapter. v Perform the following tasks to prepare Microsoft SQL Server 2005: Ensure that the Microsoft SQL Server 2005 service pack 2 is installed. Enable port 1433 which is the port used by Maximo Asset Management when configured with Microsoft SQL Server. By default, this port is not enabled. Consult the Microsoft SQL Server for information on enabling the port. v If you plan to use Microsoft Active Directory to secure WebSphere Application Server Network Deployment, you must configure SSL and manually create users on the Microsoft Active Directory instance. See the Manually configuring Microsoft Active Directory topic in the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions. v For WebSphere Application Server Network Deployment, ensure that the Cell and all related nodes are actively running. If you intend to perform multiple installations of the product using the same administrative workstation, review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations.. When you are installing the product, specify the fully-qualified host name of the system for all host name values.

90

Installation Guide:

If you are installing on a system using a system ID that contains Russian language characters, the installation fails with error message CTGIN2289E when attempting to install language packages. This circumstance causes a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E. To avoid this problem, install the product using a user ID with administrative authority that contains only English language characters. See the troubleshooting chapter for information about errors that occur during the installation.

About this task


To install Maximo Asset Management, follow these steps:

Procedure
1. Log in as Administrator on the Maximo Asset Management administrative system. 2. Ensure the database server, directory server, and application server services are running. 3. Start the Maximo Asset Management installation program from the launchpad. a. Start the launchpad. Navigate to the root directory of the product DVD or the downloaded installation image, and run the following command: launchpad.exe b. In the launchpad navigation screen, click Install the Product. c. Click Maximo Asset Management. Alternatively, you can start the Maximo Asset Management installation program directly. Navigate to \\Install\MAM\ on the product DVD or on the downloaded installation image and run one of the following commands: v install.exe v install_win64.exe 4. Select a language for the installation and click OK. 5. In the Introduction screen, click Next. 6. In the Package Summary screen, review the package deployment actions, and then click Next. 7. In the software license agreement screen, read the license information and select I accept both the IBM and the non-IBM terms. if you agree with the terms, and then click Next. 8. In the Choose Install Folder screen, specify the install directory for Maximo Asset Management, and then click Next. Where Would You Like to Install? Enter the path to install Maximo Asset Management. By default, this value is C:\IBM\SMP. The path you specify must not contain spaces. 9. In the Choose Deployment screen, select the Custom option, and then click Next. Simple A simple installation deploys all Maximo Asset Management components on a single system. A simple installation does not support reuse of middleware. This deployment option is typically used for demonstration, proof-of-concept, or training purposes only. Custom A custom installation can deploy Maximo Asset Management
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

91

components across several systems, and can reuse existing middleware components. This deployment option is typically used in a production environment. 10. In the Import Middleware Configuration Information screen, specify that you want to use the field values that you used with the middleware installation program as default values for those same fields in the Maximo Asset Management installation program and then click Next.. Import middleware configuration information Select this check box if you want to allow the Maximo Asset Management installation program to reuse values entered in the middleware installation program. The middleware default information is not used if you select the Simple deployment path. Host name Enter the host name of the system where the middleware installation program was run. User ID Enter the user ID that was used to run the middleware installation program. Password Enter the password of the user ID that was used to run the middleware installation program. Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. This file is found in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows and /root/ibm/tivoli/mwi/workspace for UNIX. 11. In the Database Type screen, select the DB2 database, and then click Next. 12. In the Database screen, enter configuration information about the database, and then click Next. Host name Enter the fully-qualified host name of the server hosting DB2. 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. 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.

92

Installation Guide:

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. After you enter configuration information for the database, the Maximo Asset Management installation program connects to the database server to validate the information you have entered. 13. In the Automate Database Configuration screen, select Automate database creation and configuration, and then click Next. 14. In the Remote Access Authorization screen, enter authorization information for the automatic database configuration feature, and then click Next. User ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting the database to be used with Maximo Asset Management. This user ID must have administrative rights on the server you are accessing. For Windows OS, this user must be a member of the DB2ADMNS group. For Linux or UNIX OS, this user must be root and a member of a group with SYSADM authority for the database instance. Password Enter the password for the user ID. See the Remote configuration enablement topic in the Preparing to install Maximo Asset Management chapter for information about configuring remote access. 15. In the Database Administration screen, enter configuration information about the database, and then click Next. DB2 Installation directory Enter the directory where DB2 is installed. Windows OS This value might be C:\Program Files\IBM\SQLLIB. Linux or UNIX OS This value might be /opt/IBM/db2/V9.5 Instance administrator user ID Enter the user ID for the administrator of the DB2 instance. Windows OS This value might be db2admin. Linux or UNIX OS This value might be ctginst1. This user ID cannot be the same as the database user ID.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

93

Instance administrator password Enter the password for the user ID of the administrator for theDB2 instance. 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 OS This value might be C:\oracle\product\10.2.0\db_1 Linux and UNIX OS This value might be /opt/app/oracle/product/10.2.0/ db_1 Administrator User ID Enter the user ID of the administrator for Oracle. For all platforms, the default is sys. Administrator Password Enter the password for the user ID for the administrator of 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 Software Owner Password Enter the password for the user ID of the user that was used to install Oracle. Microsoft SQL Server Microsoft SQL Server administrator Enter the user ID of the administrator for Microsoft SQL Server. Default is sa. Microsoft SQL Server administrator password Enter the password for the user ID of the administrator for Microsoft SQL Server. Data file name Enter the name of the Microsoft SQL Server data file. Default value is maxdb71_dat Data file initial size Select the initial size of the Microsoft SQL Server data file. Default is set to Medium (1000 Mb).

94

Installation Guide:

Log file name Enter the name for the Microsoft SQL Server log file. Default is maxdb71_log. 16. In the Database Tablespace screen, enter information about the table space of the database, and then click Next. DB2 Data tablespace name Enter the name of the table space that is created in DB2 for Maximo. For all platforms, the default is MAXDATA. If the table space does not exist, it is created. Data tablespace size Enter a size, in megabytes, for the data table space. Temporary tablespace name Enter the name for the temporary table space to be created for DB2. Temporary table spaces hold data during sorting or collating actions. For all platforms, the default is MAXTEMP. If the table space does not exist, it is created. Temporary tablespace size (Mb) Enter a size for the temporary table space. The default value is 1000 Mb. Index tablespace name Enter a name for the index table space. For all platforms, the default is MAXDATA. Index tablespace size Enter a size, in megabytes, for the index table space. Oracle Instance Location Enter the path where the database instance is loaded. Windows OS This value might be C:\oracle\product\10.2.0\db_1\ dbs Linux or UNIX OS This value might be /opt/app/oracle/product/10.2.0/ db_1 Data Tablespace name Enter the name of the table space that is created in Oracle for Maximo. For all platforms, the default is maxdata Data tablespace size Enter a size, in megabytes, for the data table space.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

95

Temporary tablespace name Enter the name for the temporary table space to be created for Oracle. Temporary table spaces hold data during sorting or collating actions. For all platforms, the default is maxtemp Temporary tablespace size (Mb) Enter a size for the temporary table space. The default value is 1000 Mb. Index tablespace name Enter a name for the index table space. For all platforms, the default is MAXDATA. Index tablespace size Enter a size, in megabytes, for the index table space. The Maximo Asset Management installation program now connects to the database server and validates all the information you have entered. 17. When the database validation task has completed, in the Application Server Type screen, select the application server that you use for the Maximo Asset Management deployment, and then click Next. IBM WebSphere Application Server Select this option to configure WebSphere Application Server Network Deployment as the J2EE server to use with Maximo Asset Management. If you select WebSphere Application Server Network Deployment, you have the option of configuring it automatically through the Maximo Asset Management installation program. Oracle WebLogic Server Select this option to configure WebLogic Server as the J2EE server to use with Maximo Asset Management. If you select WebLogic Server, you cannot configure it automatically with the Maximo Asset Management installation program. 18. In the WebSphere Connectivity screeen, enter host information about the WebSphere Application Server Network Deployment, and then click Next. Host name Enter the fully qualified host name of the system hosting WebSphere Application Server Network Deployment. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere Application Server Network Deployment system. The default value for this field is 8879. 19. In the Automate WebSphere configuration screen, select Automate WebSphere configuration, and then click Next. This option allows the Maximo Asset Management installation program to automatically configure WebSphere Application Server Network Deployment for use by Maximo Asset Management.

96

Installation Guide:

If you choose not to have the Maximo Asset Management installation program automatically configure WebSphere Application Server Network Deployment, you have to configure it manually before you install the product. 20. In the WebSphere Remote Access Authorization screen, enter authorization information for WebSphere Application Server Network Deployment configuration, and then click Next. Operating system user ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting WebSphere Application Server Network Deployment. This user ID must have administrative rights on the server you are accessing. Operating system password Enter the password for the system user ID. 21. In the WebSphere Deployment Manager Configuration screen, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere Application Server Network Deployment is installed on the host system. Windows OS This value might be C:\Program Files\IBM\WebSphere\ AppServer. Linux or UNIX OS This value might be /opt/IBM/WebSphere/AppServer or /usr/IBM/WebSphere/AppServer. User ID Enter the administrative user ID used to access the WebSphere Application Server Network Deployment Server. Default for all platforms is wasadmin. Password Enter the password for the administrative user ID used to access the WebSphere Application Server Network Deployment Server. Profile name Enter the name of the WebSphere Application Server Network Deployment profile. Default for all platforms is ctgDmgr01. 22. In the WebSphere Application Server Configuration screen, enter the following information, and then click Next. Web server port Enter the Web server port used by WebSphere Application Server Network Deployment. Default for all platforms is 80 Web server name Enter the name of the Web server. Default for all platforms is webserver1

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

97

Node name Enter the name of the WebSphere Application Server Network Deployment node containing the application server. Default for all platforms is ctgNode01. Application server Enter the name of the WebSphere Application Server Network Deployment application server to associate with Maximo Asset Management. Default for all platforms is MXServer. This value can be customized. The application server is created if it does not exist. 23. In the Security screen, select a method for authenticating and authorizing users and groups, and then click Next. WebSphere application security for authentication and authorization Choose this option to automatically configure WebSphere Application Server Network Deployment application security to manage users and groups for authentication and authorization purposes. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. WebSphere application security only for authentication Choose this option to automatically configure WebSphere Application Server Network Deployment application security for authentication only and allow Maximo security to manage users and groups. With this option, you create all your users in your directory server, but you manage their membership in security groups in the base services Security Groups application. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. If you select this option, the next panel you encounter prompts you for your user base entry. The maxadmin, maxreg, and mxintadm users and MAXIMOUSERS and MAXADMIN groups must have been created before you proceed past this panel. Maximo security for authentication and authorization If you do not want to use WebSphere Application Server Network Deployment application security, select this option to have Maximo security manage users and groups for both authentication and authorization. 24. In the Specify Maximo users screen, enter the following information, and then click Next. Maximo administration user Product administrator user ID used for initial configuration and adding users. Default value is maxadmin. Password Password for the Maximo administration user. Maximo system registration user User ID used for the self registration of users. Default value is maxreg. Password Password for the Maximo system registration user. Maximo system integration user User ID used with enterprise adapters. Default value is maxintadm.

98

Installation Guide:

Password Password for the Maximo system integration user. The password values you enter for Maximo users are not validated by the installation program. Incorrect values cause a failure during the installation process. Ensure that you have entered the correct password values for Maximo users. 25. In the Security screen, which you encounter if you chose to use WebSphere Application Server Network Deployment application security for authentication and authorization, specify the distinguished names of the user and group base entities you are using, choose how Maximo Asset Management users are created, and then click Next. User base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the user base entry you intend to use in this field. The default LDAP schema user base entry is ou=users,ou=SWG,o=IBM,c=US Group base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the group base entry you intend to use in this field. The default LDAP schema group base entry is ou=groups,ou=SWG,o=IBM,c=US Create the required users Keep this option selected to allow the Maximo Asset Management installation program to create default users in WebSphere Application Server Network Deployment Virtual Member Manager. This operation requires write access to Virtual Member Manager. If you do not want to have the users created by the Maximo Asset Management installation program, you will have to create them manually before continuing the Maximo Asset Management installation from this point. See the Synchronizing users and groups topic in the Post-installation configuration chapter for information on customizing your schema. If you are not using the default LDAP schema provided with Maximo Asset Management, you have to have created it yourself before advancing beyond this panel. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask. Here is an example of the default add on ldif data you would have to modify and import into your LDAP repository if you choose 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
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

99

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=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=maxadmin,ou=users,ou=SWG,o=IBM,c=US member: uid=mxintadm,ou=users,ou=SWG,o=IBM,c=US member: uid=maxreg,ou=users,ou=SWG,o=IBM,c=US cn: maximousers

26. In the Integration Adapter JMS Configuration screen, enter the following information, and then click Next. A JMS server requires a DB2 data repository to be configured to maintain messages. If you are using another database type, you must manually configure message persistence. JMS Data Source name Enter the name of the data source to be used by JMS. If you are using Microsoft SQL Server or Oracle, this field is pre-populated. If it is not, enter intjmsds. Select whether the JMS data store should be persisted. Persist JMS messages Select this option of you want the Maximo Asset Management installation program to set the JMS implementation to persist messages within DB2. If you select this option, the installation wizard guides you through additional JMS configuration screens. Do not persist JMS messages Select this option if you do not want the Maximo Asset Management installation program to set the JMS implementation to persist messages automatically or if you are using a database type other than DB2. If you later decide that you would like to persist JMS messages, you will have to configure the JMS implementation manually. If you select this option, the installation wizard skips to Step 30, where you configure SMTP.

100

Installation Guide:

27. In the DB2 Database Server Configuration screen, enter the following information, and then click Next. Note: The JMS data store can only be created as a DB2 database. Host name Enter the fully-qualified host name of the server hosting the JMS data store. 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 data store. 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. 28. In the DB2 Database Server Remote Access Authorization screen, enter authorization information for the automatic configuration feature, and then click Next. User ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting the JMS database. This user ID must have administrative rights on the server you are accessing. For Windows, this user must be a member of the DB2ADMNS group. For UNIX, this user must be an administrator user and a member of a group with SYSADM authority for the database instance. Password Enter the password for the user ID. 29. In the DB2 Database Instance Configuration screen, 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 Application Server Network Deployment. Windows OS This value might be C:\Program Files\IBM\SQLLIB. Linux or UNIX OS This value might be /opt/IBM/db2/V9.5. Instance Enter the JMS database instance to use with WebSphere Application Server Network Deployment. For all platforms, the default is ctginst1

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

101

Instance administrator user ID Enter the user ID of the administrator for the JMS database instance. Windows OS This value might be db2admin. Linux or UNIX OS This value might be ctginst1. Instance administrator password Enter the password for the user ID of the administrator for the JMS database instance. 30. In the SMTP Configuration screen, specify SMTP configuration information used by workflows to communicate with workflow participants, and then click Next SMTP server Enter the fully qualified host name of the SMTP server that sends messages to participants. Administrator e-mail Enter a valid e-mail address. This address is to send messages. You can defer SMTP configuration at this time by not providing any information for this panel and clicking through to the next panel. However, you must configure these parameters through the product interface as a post-installation task which is described in the Configuring SMTP topic in the Post-installation configuration chapter. 31. From the Run Configuration Step screen, decide how you would like to perform the configuration step of the installation, and then click Next. a. Choose when you would like to run the configuration step: Perform installation configuration now Select this option to have the installation program perform the configuration step during installation. Copy files now. Perform installation configuration later. Select this option to have the installation program copy files to the system only. The Maximo Asset Management installation program is used to complete three tasks: gathering information about your Maximo Asset Management deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting this option, you can instruct the Maximo Asset Management installation program to gather your configuration information and copy Maximo Asset Management 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 <MAM_HOME>maximo\applications\maximo\properties\ maximo.properties file. You can run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility, located in the <MAM_HOME>\scripts directory. Run the taskrunner utility from the command line, and it uses the configuration values stored in the maximo.properties file to configure Maximo Asset Management.
<MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

102

Installation Guide:

Note: If you reboot the system, you are not able to use the taskrunner utility to run configuration scripts. Taskrunner data stores are not persisted. If you intend to use the taskrunner utility, do not reboot your system. In the case of an installation failure, the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. b. Choose how to deploy application files. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. Deploy application files manually later Select this option to defer the deployment of application files. Deferring the deployment of application files can shorten the time it takes to deploy overall if you intend to install more than one service management product. Files can be deployed once all products have added their own functions to the application files. You might also want to use this option if your organization has application deployment restrictions that require that you deploy application files either manually or through another approved process. See the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions to manually deploy WebSphere Application Server. 32. In the Choose Shortcut Folder screen, select the type of shortcut you would like to arrange for Maximo Asset Management, and then click Next. Note: Shortcuts are created for Windows systems only. Note: Because deployment on WebLogic Server systems is a manual process, you are required to manually update any shortcuts you create for WebLogic Server deployments after you have manually deployed the Maximo Asset Management EAR files. In a new Program Group Select this option and enter the name of a new program group if you would like to create Maximo Asset Management 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 Maximo Asset Management shortcuts. In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. In order to use the Start Menu shortcut with Internet Explorer, ensure that you have added the Maximo Asset Management URL to the trusted sites Web content zone and disable the option of requiring server verification for all sites in the zone.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

103

On the Desktop Select this option to create shortcuts for Maximo Asset Management on the desktop. In the Quick Launch Bar This option must not be used. 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 Maximo Asset Management shortcuts. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. Create Icons for All Users Select this option if you would like Maximo Asset Management desktop icons to appear on the desktop for all system users. 33. In the Input Summary screen, review the information you have provided to the Maximo Asset Management installation program, and then click Next. Use the Previous button to return to previous screens to make changes. 34. In the Pre-Installation Summary screens, review the installation information presented, and then click Install. The installation task begins. Progress can be monitored by viewing messages displayed above the progress bar. 35. In the Install Complete screen, click Done.

What to do next
When the installation has completed the installation wizard closes.

Simple install path values


Put your short description here; used for first paragraph and abstract. If you elect to install Maximo Asset Management using the simple install path, the following values are set. You will be able to provide values where indicated.
Table 14. Maximo Asset Management Simple Install Path Values Category Deployment Option 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 yes 50005 maxdb71 ctginst1 Yes Value simple DB2 Yes Provided by User?

104

Installation Guide:

Table 14. Maximo Asset Management Simple Install Path Values (continued) Category Database Configuration Database Configuration Field Remote Access User ID Database Install Directory Windows OS C:\Program Files\IBM\ SQLLIB Linux or UNIX OS /opt/IBM/ db2/V9.5 Database Configuration Instance Administrator User ID Windows OS db2admin Linux or UNIX OS ctginst1 Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration WebSphere Connectivity WebSphere Connectivity WebSphere Configuration Windows Service User ID db2admin Yes Value Provided by User? Yes

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 OS C:\Program Files\IBM\ WebSphere\ AppServer Linux /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer

AIX

Sun Solaris /opt/IBM/ WebSphere/ AppServer HP-UX /opt/IBM/ WebSphere/ AppServer WebSphere Configuration User name wasadmin Yes

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

105

Table 14. Maximo Asset Management Simple Install Path Values (continued) Category WebSphere Configuration WebSphere Configuration WebSphere Configuration 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 Profile name Value ctgDmgr01 Provided by User?

Automate WebSphere yes Configuration Remote Access User ID Web server port 80 Yes

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

Running the Maximo Asset Management installation program


Use these instructions to install Maximo Asset Management and automatically configure middleware on multiple servers, using default values.

Before you begin


Before you start the installation program, ensure that the system meets the following conditions: v On the administrative workstation, temporarily shut down any non-critical processes that could have a negative effect on the installation, such as anti-virus software.

106

Installation Guide:

v The middleware environment is installed and running properly. See the Troubleshooting chapter for instructions on restarting middleware if you need to do so. v Enable a remote execution and access service on every system with middleware installed. Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server. Remote access protocols include rsh, rexec, SSH and Windows SMB. If the remote system is a Windows server, you must configure remote execution and access to use SMB. v Perform the following tasks to prepare the DB2 database: If DB2 is installed on a Linux or UNIX system, you must create the instance user and the home directory for the user on the DB2 server. The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. The user ID for the DB2 instance administrator must have SYSADM (administration) authority. You enter this user ID on the DB2 Administration screen and on the Remote Access Authorization screen of the Maximo Asset Management installation program. See the DB2 product documentation for information about creating a user with SYSADM (administration) authority on the DB2 server. To avoid high system memory usage by DB2, you can set the following DB2 property and then restart the DB2 server:
db2 update dbm cfg using KEEPFENCED NO

If you had to shorten the TEMP and TMP environment variables when you installed DB2 on aWindows system, and you intend to install the product on the same system, redefine these variables before you begin the product installation. If you are plan to install Maximo Asset Management in a language other than English, you must accept the default values for database table space size and index table space size and these values are displayed as null during the installation. If you want to customize the table space sizes, you must either run the Maximo Asset Management installation program in English, manually configure the database, or modify the table space sizes after installation. v For WebSphere Application Server Network Deployment, ensure that the Cell and all related nodes are actively running. v The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed into that location. Automatic configuraton creates an empty Maximo database on the system. You can create a maxdemo database, including sample data, during the installation. To create a maxdemo database, complete either of following two procedures: v Enter a command to create a maxdemo database: 1. In the command line, navigate to the directory where the Maximo Asset Management files are extracted. 2. Change to the install\MAM\Install\new folder. 3. On a 32-bit Windows system, run the following command:
install.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes d

On a 64-bit Windows system, run the following command:


install_win64.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes

v When you are running the installation wizard, create a maxdemo database by performing the following tasks:
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

107

1. In the Run Configuration Step screen in the installation wizard (Step 31 in the procedure), select the Copy files now. Perform installation configuration later option. 2. When the installation finishes, exit the installation wizard. 3. Rename the ibm\smp\maximo\tools\maximo\en\maximo file. 4. Copy the ibm\smp\maximo\tools\maximo\en\maxdemo file to ibm\smp\maximo\tools\maximo\en\maximo. where en is the language folder and dbtype is ora/sqs/db2. 5. From a command prompt navigate to ibm\smp\scripts and run the following command:
taskrunner.bat CONTINUE STOPONERROR

Do not restart the computer after you copy files but before you run the taskrunner command because the taskrunner utility does not create a persistent store of information. 6. When taskrunner finishes running, rename the files back to their original names. When taskrunner successfully completes, r 7. Restart the installation program to continue with the license enablement If you intend to perform multiple installations of the product using the same administrative workstation, review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations.. When you are installing the product, specify the fully-qualified host name of the system for all host name values. If you are installing on a system using a system ID that contains Russian language characters, the installation fails with error message CTGIN2289E when attempting to install language packages. This circumstance causes a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E. To avoid this problem, install the product using a user ID with administrative authority that contains only English language characters. See the troubleshooting chapter for information about errors that occur during the installation.

About this task


To install Maximo Asset Management, follow these steps:

Procedure
1. Log in as Administrator on the Maximo Asset Management administrative system. 2. Ensure the database server, directory server, and application server services are running. 3. Start the Maximo Asset Management installation program from the launchpad. a. Start the launchpad. Navigate to the root directory of the product DVD or the downloaded installation image, and run the following command: launchpad.exe b. In the launchpad navigation screen, click Install the Product. c. Click Maximo Asset Management.

108

Installation Guide:

Alternatively, you can start the Maximo Asset Management installation program directly. Navigate to \\Install\MAM\ on the product DVD or on the downloaded installation image and run one of the following commands: v install.exe v install_win64.exe Select a language for the installation and click OK. In the Introduction screen, click Next. In the Package Summary screen, review the package deployment actions, and then click Next. In the software license agreement screen, read the license information and select I accept both the IBM and the non-IBM terms. if you agree with the terms, and then click Next. In the Choose Install Folder screen, specify the install directory for Maximo Asset Management, and then click Next. Where Would You Like to Install? Enter the path to install Maximo Asset Management. By default, this value is C:\IBM\SMP. The path you specify must not contain spaces. 9. In the Choose Deployment screen, select the Custom option, and then click Next. Simple A simple installation deploys all Maximo Asset Management components on a single system. A simple installation does not support reuse of middleware. This deployment option is typically used for demonstration, proof-of-concept, or training purposes only. Custom A custom installation can deploy Maximo Asset Management components across several systems, and can reuse existing middleware components. This deployment option is typically used in a production environment. 10. In the Import Middleware Configuration Information screen, specify that you want to use the field values that you used with the middleware installation program as default values for those same fields in the Maximo Asset Management installation program and then click Next.. Import middleware configuration information Select this check box if you want to allow the Maximo Asset Management installation program to reuse values entered in the middleware installation program. The middleware default information is not used if you select the Simple deployment path. Host name Enter the host name of the system where the middleware installation program was run. User ID Enter the user ID that was used to run the middleware installation program. Password Enter the password of the user ID that was used to run the middleware installation program.
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

4. 5. 6. 7.

8.

109

Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. This file is found in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows and /root/ibm/tivoli/mwi/workspace for UNIX. 11. In the Database Type screen, select the DB2 database, and then click Next. 12. In the Database screen, enter configuration information about the database, and then click Next. Host name Enter the fully-qualified host name of the server hosting DB2. 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. 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. After you enter configuration information for the database, the Maximo Asset Management installation program connects to the database server to validate the information you have entered. 13. In the Automate Database Configuration screen, select Automate database creation and configuration, and then click Next. 14. In the Remote Access Authorization screen, enter authorization information for the automatic database configuration feature, and then click Next. User ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting the database to be used with Maximo Asset Management. This user ID must have administrative rights on the server you are accessing. For Windows OS, this user must be a member of the DB2ADMNS group.

110

Installation Guide:

For Linux or UNIX OS, this user must be root and a member of a group with SYSADM authority for the database instance. Password Enter the password for the user ID. See the Remote configuration enablement topic in the Preparing to install Maximo Asset Management chapter for information about configuring remote access. 15. In the Database Administration screen, enter configuration information about the database, and then click Next. Installation directory Enter the directory where DB2 is installed. Windows OS This value might be C:\Program Files\IBM\SQLLIB Linux or UNIX OS This value might be /opt/IBM/db2/V9.5 Instance administrator user ID Enter the user ID for the administrator of the DB2 instance. Windows OS This value might be db2admin. Linux or UNIX OS This value might be ctginst1. This user ID cannot be the same as the database user ID. Instance administrator password Enter the password for the user ID of the administrator for theDB2 instance. 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. 16. In the Database Tablespace panel, enter information about the table space of the database, and then click Next. Data tablespace name Enter the name of the table space that is created in DB2 for Maximo. For all platforms, the default is MAXDATA. If the table space does not exist, it is created. Data tablespace size Enter a size, in megabytes, for the data table space. Temporary tablespace name Enter the name for the temporary table space to be created for DB2. Temporary table spaces hold data during sorting or collating actions. For all platforms, the default is MAXTEMP. If the table space does not exist, it is created.
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

111

Temporary tablespace size (Mb) Enter a size for the temporary table space. The default value is 1000 Mb. Index tablespace name Enter a name for the index table space. For all platforms, the default is MAXDATA. Index tablespace size Enter a size, in megabytes, for the index table space. The Maximo Asset Management installation program now connects to the database server and validates the information you entered. 17. When the database validation is completed, in the Application Server Type panel, select WebSphere Application Server Network Deployment as the application server to use, and then click Next. 18. In the WebSphere Connectivity panel, enter host information about the WebSphere Application Server Network Deployment, and then click Next. Host name Enter the fully-qualified host name of the system hosting WebSphere Application Server Network Deployment. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere Application Server Network Deployment system. The default value for this field is 8879. 19. In the Automate WebSphere configuration panel, select Automate WebSphere configuration, and then click Next. 20. In the WebSphere Remote Access Authorization panel, enter authorization information for WebSphere Application Server Network Deployment configuration, and then click Next. Operating system user ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting WebSphere Application Server Network Deployment. This user ID should have administrative rights on the server you are accessing. Operating system password Enter the password for the system user ID. 21. In the WebSphere Deployment Manager Configuration panel, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere Application Server Network Deployment is installed on the host system. Windows OS This value might be C:\Program Files\IBM\WebSphere\ AppServer Linux or UNIX OS This value might be /opt/IBM/WebSphere/AppServer or /usr/IBM/WebSphere/AppServer

112

Installation Guide:

User ID Enter the administrative user ID used to access the WebSphere Application Server Network Deployment Server. Default for all platforms is wasadmin. Password Enter the password for the administrative user ID used to access the WebSphere Application Server Network Deployment Server. Profile name Enter the name of the WebSphere Application Server Network Deployment profile. Default for all platforms is ctgDmgr01. 22. In the WebSphere Application Server Configuration panel, enter the following information, and then click Next. Web server port Enter the Web server port used by WebSphere Application Server Network Deployment. 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 Application Server Network Deployment node containing the application server. Default for all platforms is ctgNode01. Application server Enter the name of the WebSphere Application Server Network Deployment application server to associate with Maximo Asset Management. Default for all platforms is MXServer. This value can be customized. The application server is created if it does not exist. 23. In the Security panel, select a method for authenticating and authorizing users and groups, and then click Next. WebSphere application security for authentication and authorization Choose this option to automatically configure WebSphere Application Server Network Deployment application security to manage users and groups for authentication and authorization purposes. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. WebSphere application security only for authentication Choose this option to automatically configure WebSphere Application Server Network Deployment application security for authentication only and allow Maximo security to manage users and groups. With this option, you create all your users in your directory server, but you manage their membership in security groups in the base services Security Groups application. This option requires application security to already be enabled in WebSphere Application Server Network Deployment.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

113

If you select this option, the next panel you encounter prompts you for your user base entry. The maxadmin, maxreg, and mxintadm users and MAXIMOUSERS and MAXADMIN groups must have been created before you proceed past this panel. Maximo security for authentication and authorization If you do not want to use WebSphere Application Server Network Deployment application security, select this option to have Maximo security manage users and groups for both authentication and authorization. 24. In the Specify Maximo users panel, enter the following information, and then click Next. Maximo administration user Product administrator user ID used for initial configuration and adding users. Default value is maxadmin. Password Password for the Maximo administration user. Maximo system registration user User ID used for the self registration of users. Default value is maxreg. Password Password for the Maximo system registration user. Maximo system integration user User ID used with enterprise adapters. Default value is maxintadm. Password Password for the Maximo system integration user. 25. In the Security panel, which you encounter if you chose to use WebSphere Application Server Network Deployment application security for authentication and authorization, specify the distinguished names of the user and group base entities you are using, choose how Maximo Asset Management users are created, and then click Next. User base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the user base entry you intend to use in this field. The default LDAP schema user base entry is ou=users,ou=SWG,o=IBM,c=US Group base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the group base entry you intend to use in this field. The default LDAP schema group base entry is ou=groups,ou=SWG,o=IBM,c=US Create the required users Keep this option selected to allow the Maximo Asset Management installation program to create default users in WebSphere Application Server Network Deployment Virtual Member Manager. This operation requires write access to Virtual Member Manager.

114

Installation Guide:

If you do not want to have the users created by the Maximo Asset Management installation program, you will have to create them manually before continuing the Maximo Asset Management installation from this point. If you are not using the default LDAP schema provided with Maximo Asset Management, you must create it yourself before advancing beyond this panel. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask. Following is an example of the default add on ldif data you have to modify and import into your LDAP repository if you chose 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=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=maxadmin,ou=users,ou=SWG,o=IBM,c=US member: uid=mxintadm,ou=users,ou=SWG,o=IBM,c=US member: uid=maxreg,ou=users,ou=SWG,o=IBM,c=US cn: maximousers

26. In the Integration Adapter JMS Configuration screen, enter the following information, and then click Next. A JMS server requires a DB2 data repository to be configured to maintain messages. JMS Data Source name Enter intjmsds as the name of the data source to be used by JMS. Select whether the JMS data store should be persisted.
Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

115

Persist JMS messages Select this option to enable theMaximo Asset Management installation program to set the JMS implementation to persist messages within DB2. Do not persist JMS messages If you select this option, the Maximo Asset Management installation program will not set the JMS implementation to persist messages automatically in DB2. You can configure the JMS implementation manually at a later date. If you select this option, when you click Next, the installation wizard skips to step 30, where you configure SMTP. 27. If you chose to persist JMS messages, in the DB2 Database Server Configuration panel, enter the following information, and then click Next. If you chose not to persist JMS messages, the wizard skips to step 30, and you do not see this screen. Note: The JMS data store can only be created as a DB2 database. Host name Enter the fully qualified host name of the server hosting the JMS data store. 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 data store. 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. 28. If you chose to persist JMS messages, in the DB2 Database Server Remote Access Authorization panel, enter authorization information for the automatic configuration feature, and then click Next .If you chose not to persist JMS messages, the wizard skips to step 30, and you do not see this screen. User ID Enter a valid user ID that allows the Maximo Asset Management installation program to access the system that is hosting the JMS database. This user ID must have administrative rights on the server you are accessing. For Windows OS, this user must be a member of the DB2ADMNS group. For Linux or UNIX OS, this user must be root and a member of a group with SYSADM authority for the database instance. Password Enter the password for the user ID.

116

Installation Guide:

29. If you chose to persist JMS messages, in the DB2 Database Instance Configuration panel, enter the following information, and then click Next. If you chose not to persist JMS messages, the wizard skips to step 30, and you do not see this screen. Installation directory Enter the installation directory for the DB2 server that is hosting the JMS database that contains the instance to be used with WebSphere Application Server Network Deployment. Windows OS This value might be C:\Program Files\IBM\SQLLIB Linux or UNIX OS This value might be /opt/IBM/db2/V9.5 Instance Enter the JMS database instance to be used with WebSphere Application Server Network Deployment. For all platforms, the default is ctginst1 Instance administrator user ID Enter the user ID of the administrator for the JMS database instance. Windows OS This value might be db2admin. Linux or UNIX OS This value might be ctginst1. Instance administrator password Enter the password for the user ID of the administrator for the JMS database instance. 30. In the SMTP Configuration panel, specify SMTP configuration information used by workflows to communicate with workflow participants, and then click Next. SMTP server Enter the fully qualified host name of the SMTP server that sends messages to participants. Administrator e-mail Enter a valid e-mail address. This address is to send messages. You can defer SMTP configuration at this time by not providing any information for this panel and clicking through to the next panel. However, you must configure these parameters through the product interface as a post installation task which is described in Configuring SMTP on page 210. 31. From the Run Configuration Step panel, decide how you would like to perform the configuration step of the installation, and then click Next. a. Choose when you would like to run the configuration step: Perform installation configuration now Select this option to have the installation program perform the configuration step during installation. Copy files now. Perform installation configuration later. Select this option to have the installation program copy files to the system only.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

117

The Maximo Asset Management installation program is used to complete three tasks: gathering information about your Maximo Asset Management deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting this option, you can instruct the Maximo Asset Management installation program to gather your configuration information and copy Maximo Asset Management 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 <MAM_HOME>maximo\applications\maximo\properties\ maximo.properties file. You can run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility, located in the <MAM_HOME>\scripts directory. Run the taskrunner utility from the command line, and it uses the configuration values stored in the maximo.properties file to configure Maximo Asset Management.
<MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

Note: If you reboot the system, you are not able to use the taskrunner utility to run configuration scripts. Taskrunner data stores are not persisted. If you intend to use the taskrunner utility, do not reboot your system. In the case of an installation failure, the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. b. Choose how to deploy application files. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. Deploy application files manually later Select this option to defer the deployment of application files. Deferring the deployment of application files can shorten the time it takes to deploy overall if you intend to install more than one service management product. Files can be deployed once all products have added their own functions to the application files. You might also want to use this option if your organization has application deployment restrictions that require that you deploy application files either manually or through another approved process. See the instructions for manually configuring WebSphere Application Server in the Deployment of .Maximo Asset Management with manual configuration of middleware. 32. In the Choose Shortcut Folder panel, select the type of shortcut you would like to arrange for Maximo Asset Management, 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 Maximo Asset Management shortcuts in a new program group.

118

Installation Guide:

In an existing Program Group Select this option and choose the name of an existing program group to store Maximo Asset Management shortcuts. In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. In order to use the Start Menu shortcut with Internet Explorer, ensure that you have added the Maximo Asset Management 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 Maximo Asset Management on the desktop. In the Quick Launch Bar This option must not be used. 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 Maximo Asset Management shortcuts. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. Create Icons for All Users Select this option if you would like Maximo Asset Management desktop icons to appear on the desktop for all system users. 33. In the Input Summary panel, review the information you have provided to the Maximo Asset Management installation program, and then click Next. Use the Previous button to return to previous panels to make changes. 34. In the Pre-Installation Summary panel, review the installation information presented, and then click Install. The installation task begins. Progress can be monitored by viewing messages displayed above the progress bar. 35. In the Install Complete panel, click Done.

What to do next
When the Maximo Asset Management installation program has completed installation and configuration tasks, it will exit.

Completing post-installation tasks


To complete the deployment, you must perform several additional tasks after the installation. If you intend to support multiple languages in Maximo Asset Management, install the language pack before performing other configuration tasks. See the Deployment of optional packages chapter for language pack installation instructions. The chapter also describes how to install process solution packages, including process manager products and integration modules. The Post-installation configuration chapter describes the configuration tasks to complete within the product user interface.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

119

Deploying the confhelp.properties file


The confhelp.properties file must be deployed to enable the help system for the product.

Before you begin About this task


To deploy the confhelp.properties file, complete the following steps:

Procedure
1. Ensure you are logged into the administrative workstation. 2. Run the following command:
<MAM_HOME>\jacl\solutions\Sendfile.bat <WASDeploymentManagerHostName> <WASRemoteAccessUserName> <WASRemoteAccesspassword> "<MaximoInstallLocation>\applications\maximohelp \helpweb\webmodule\WEB-INF\confhelp.properties" "<WASInstallLocation>\properties" "confhelp.properties"

Verifying the installation


After you have exited the Maximo Asset Management installation program without encountering any errors, you can further verify that the installation completed successfully by locating key artifacts and performing a few simple tasks.

Before you begin


The product installation program performs installation verification, or a health check, by logging into the product before exiting the installation. The product installation program returns a success message if all installation steps, including the product log in task, are successful. If the health check task is unsuccessful, a HealthCheckFailed error thrown for the getUrlContentString function will be found in the <MAM_HOME>\logs\CTGInstallTraceXX.log file, where XX is a two digit number such as 00. For more information about log files and troubleshooting errors encountered during the installation, refer to Troubleshooting the product installation program on page 239.

About this task


To further verify that the Maximo Asset Management installation was completed successfully, perform the following verification procedures:

Procedure
1. Examine the CTGInstallTrace00.log file for success messages. The following success messages are found in the CTGInstallTrace00.log file and can be used to verify which phases of the installation were successful: v CTGIN2114I: The database was created successfully v CTGIN2135I: Tablespace maxdata created successfully v CTGIN2135I: Tablespace maxtemp created successfully

120

Installation Guide:

v CTGIN2079I: Base services database configuration completed successfully (This message indicates that maxinst finished successfully.) v CTGIN2222I: WebSphere Application Server creation successful v CTGIN2188I: Creation and configuration of service integration bus successfully completed v CTGIN2184I: Creation and configuration of JMS resources successfully completed v CTGIN2310I: Application server security was successfully enabled for the base services v CTGIN2253I: buildmaximoear.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMO was successful v CTGIN2253I: buildhelpear.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMOHELP was successful v CTGIN2208I: runConfigurationStep completed successfully v CTGIN2370I: The installation finished successfully If you chose the option of having the installation program automatically configure WebSphere Application Server Network Deployment, the following messages, found in the CTGInstallTrace00.log file, indicate the configuration was successful:
<symptom>CTGIN2228I.*client</symptom> <symptom>CTGIN2230I.*node</symptom> <symptom>CTGIN2232I.*NodeAgent</symptom> <symptom>CTGIN2240I.*server</symptom> <symptom>CTGIN2238I.*security</symptom>

Search the CTGInstallTrace00.log file for the following message, which indicates that the maxinst task completed successfully:
CTGIN2079I, maxinst.*completed

2. Compare the packages chosen for installation with the packages that were installed. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages that will be installed. You can compare the contents of that panel with a listing of what was actually installed on the system. Use the solutioninstaller command to list installed packages:
<MAM_HOME>\bin\setupPSIenv.bat <MAM_HOME>\bin\solutionInstaller.bat -action showInstalled -all

The resulting list should match the packages listed in the Package Summary panel. 3. Log into the product and verify applications are present. Being able to log into the product manually is a good indicator that the installation was successful. Once you have logged in, navigate through the GoTo menu to verify that it has been populated with the applications you expect.

Chapter 5. Deployment of Maximo Asset Management with automatic configuration of existing middleware

121

122

Installation Guide:

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware


Use this information if you intend to deploy Maximo Asset Management by reusing existing middleware servers and manually configuring them to work with Maximo Asset Management. To deploy Maximo Asset Management manually, using middleware already established in your enterprise, use this roadmap to perform the tasks in the correct order. Before you start the deployment, review the information in the planning and preparation chapters to ensure that your environment is ready and your planning is complete.

Copyright IBM Corp. 2007 - 2010

123

Manually configure the database

Optional: Manually configure the directory server

Manually configure the J2EE server

Install Maximo Asset Management using manual middleware configuration option

Complete post product installation process manager tasks

Verify the installation

Perform post-installation tasks

Figure 2. Deploying Maximo Asset Management with manual middleware configuration

You must install middleware before you install Maximo Asset Management. Perform the installation in the following order: 1. Configure the database following the instructions for the database you plan to use. 2. Optional: Configure the directory server. 3. Configure the J2EE server. 4. Run the Maximo Asset Management installation program and select the options that indicate that the middleware is already configured.

124

Installation Guide:

5. Optional: If you did not automatically configure the J2EE server during the Maximo Asset Management installation, perform manual configuration tasks to configure process managers. 6. Complete post-installation tasks to verify the deployment and perform initial system configuration.

Manually installing and configuring middleware


You can elect to have one or more Maximo Asset Management middleware components configured automatically by the Maximo Asset Management installation program. Alternatively, you can choose to manually configure one or more of the middleware servers to work with Maximo Asset Management. Manually configured installations involve configuring middleware components, the database server, the directory server, and the J2EE server, to work with Maximo Asset Management prior to using the Maximo Asset Management installation program. The information contained in this section provides details on how to manually configure Maximo Asset Management middleware prior to running the Maximo Asset Management installation program. Also included in this section is a procedure describing how to advance through the Maximo Asset Management installation program to complete the Maximo Asset Management 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 Maximo Asset Management installation program. v For IBM WebSphere Network Deployment, ensure that the Cell and all related nodes are active. You must complete the manual configuration of each server you plan to not configure using the autoconfigure feature of the Maximo Asset Management installation program before you actually install Maximo Asset Management. Ensure that all of your middleware is at the level described in Prerequisite hardware and software on page 19.

Manually configuring the database server


If you choose to not have the Maximo Asset Management installation program automatically configure the database server, you must complete the manual configuration before you use the Maximo Asset Management installation program . For DB2 on Linux or 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 a Windows system, ensure you have a minimum of 8 GB of free space in the DB2 installation directory.

Manually configuring DB2 9.x


About this task
To configure an existing DB2 9.x server for use with Maximo Asset Management, complete the following steps prior to launching the Maximo Asset Management installation program.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

125

1. Create system users. a. Log into the system as a user that has administrative permissions on the system. b. Create a system group and system users. The middleware installer creates a ctginst1 user that will own the database instance and assigns that user to a group called db2iadm1. If you are configuring DB2 manually, you need to create users and groups manually using user management tools available on the system. Create users named ctginst1 and maximo and assign the ctginst1 user to a group named db2iadm1. For the maximo user, it is not necessary to assign a specific group. You can use these user and group name values, or use custom values of your own, but be sure to substitute them where appropriate in this procedure. For AIX, use SMIT to add the users. 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 OS
db2icrt -s ese -u db2admin,password -r 50005,50005 ctginst1

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

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

Depending upon your environment, you might have to run this command from the /opt/ibm/db2/V9.5/instance directory. Alternatively, you can add this information to your PATH. b. Set the listening port for the instance Windows OS
db2 update dbm cfg using svcename 50005

c. Set instance service to start automatically Windows OS


sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance: Windows OS


db2start

Linux or UNIX OS
su - ctginst1 db2start

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

3) Type the following command:


db2cc

Linux or UNIX OS 1) Open a command window.

126

Installation Guide:

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 to create 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. 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 16384, and then click OK. f. From the Database Configuration panel, select the APPLHEAPSZ value and click the button labeled with the ellipsis (...) in the Value column. g. Enter 2048, and then click OK. h. From the Database Configuration panel, select the LOCKLIST value and click the button labeled with the ellipsis (...) in the Value column. i. Enter 30000, and then click OK. j. From the Database Configuration panel, select the LOGSECOND value and click the button labeled with the ellipsis (...) in the Value column.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

127

k. Enter 15, and then click OK. l. 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. Alternatively, you can use the following commands to complete the steps from the command line:
connect to maxdb71 update db cfg for maxdb71 using auto_maint on update db cfg for maxdb71 using auto_tbl_maint on update db cfg for maxdb71 using auto_runstats on update db cfg for maxdb71 using auto_reorg on update db cfg for maxdb71 using auto_db_backup on update alert cfg for database on maxdb71 using db.db_backup_req set thresholdschecked yes update alert cfg for database on maxdb71 using db.tb_reorg_req set thresholdschecked yes update alert cfg for database on maxdb71 using db.tb_runstats_req set thresholdschecked yes update database configuration using applheapsz 2048 deferred update database configuration using app_ctl_heap_sz 16384 deferred update database configuration using logfilsiz 4096 deferred update database configuration using logsecond 15 deferred update database configuration using locklist 30000 automatic immediate connect reset restart db maxdb71

5. Add users to the database. a. After the database is restarted, right-click it and select Authorities. b. From the User tab of the Database Authorities window, click Add User. c. From the Add User dialog, select the user maximo, and then click OK. d. Highlight the user, maximo, in the Database Authorities window, and click Grant All. e. Click OK. 6. Create table space. a. From the DB2 Control Center, locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. b. From the right-click menu, select Create. c. Specify MAXDATA as your new table space, and then click Next. d. Select Regular as the type of table space and then click Next. e. Click Create to create a buffer pool for the table space. f. Specify MAXBUFPOOL as your new buffer pool, and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. g. Ensure the Create buffer pool immediately choice is selected, and then click OK. h. Highlight the newly created buffer pool and click Next. i. From the Specify the extent and prefetch sizes for this table space panel, choose the Between 200 MB and 2 GB option, and leave Extent size as 32, and then click Next. j. Define a hard 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.

128

Installation Guide:

l. Click Finish. Alternatively, you can use the following commands to complete the steps from the command line:
create bufferpool maxbufpool immediate size 4096 pagesize 32 k create regular tablespace maxdata pagesize 32 k managed by automatic storage extentsize 32 overhead 12.67 prefetchsize 16 transferrate 0.18 bufferpool maxbufpool dropped table recovery on

By default, index data is stored in the data table space. If you would rather create a separate index table space, you could create one at this point. 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 Maximo Asset Management. 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. Alternatively, you can use the following commands to complete the steps from the command line:
grant use of tablespace maxdata to user maximo

If you created a separate index table space, you will have to grant permissions for it at this time. 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 Maximo Asset Management. 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. Alternatively, you can use the following commands to complete the steps from the command line:
create schema maximo authorization administrator grant createin,dropin,alterin on schema maximo to user maximo

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 Maximo Asset Management. b. c. d. e. From the right-click menu, select Create. Specify MAXTEMP for your new table space, and then click Next. Select System temporary as the type of table space and then click Next. Select the previously created bufferpool (MAXBUFPOOL), and click Next.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

129

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 table space by enabling the Enable dropped table recovery option, and then click Next. i. Click Finish. Alternatively, you can use the following commands to complete the steps from the command line:
create system temporary tablespace maxtemp pagesize 32 k managed by automatic storage extentsize 32 overhead 12.67 prefetchsize 16 transferrate 0.18 bufferpool maxbufpool connect reset

10. Install the appropriate fix pack indicated in the prerequisites topic in the chapter that describes how to prepare for the installation.. 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 OS
C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

Linux or UNIX OS
DB2DIR/instance/db2iupdt ctginst1

Manually configuring DB2 8.2


About this task
To configure an existing DB2 8.2 server for use with Maximo Asset Management, complete the following steps prior to launching the Maximo Asset Management 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 OS
db2icrt -s ese -u db2admin,password -r 50005,50005 ctginst1

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

130

Installation Guide:

AIX 64-bit system


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

b. Set the listening port for the instance Windows OS


db2 update dbm cfg using svcename 50005

c. Set instance service to start automatically Windows OS


sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance: Windows OS


db2start

Linux or UNIX OS
su - ctginst1 db2start

3. Create the database: Windows OS 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

Linux or UNIX OS 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_serverInstancesCTGINST1DatabasesMAXDB71 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.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

131

l. From the Database Configuration panel, select the LOGSECOND value and click the button labeled with the ellipsis (...) in the Value column. m. Enter 4, and then click OK. n. From the Database Configuration panel, click OK. o. Click Close. p. Restart the database by right-clicking the ctginst1 instance, clicking Stop, and then clicking Start. 5. Add users to the database. a. Once the database has restarted, right-click it and select Authorities. b. From the User tab of the Database Authorities window, click Add User. c. From the Add User dialog, select the user maximo, and then click OK. d. Highlight the user, maximo in the Database Authorities window, and click Grant All. e. Click OK. 6. Create 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 Maximo Asset Management. 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 new 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 Space management panel, specify Database-managed space and click Next. j. From the Containers panel, click Add. k. Set the Type to File, Size to 5000 Mb, and File name to CTGDAT. 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 Maximo Asset Management. 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.

132

Installation Guide:

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. 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 Maximo Asset Management. 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 Maximo Asset Management. 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 listed in the prerequisites topic in the chapter that describes how to prepare for the installation. 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 OS
C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

Linux or UNIX OS
<DB2DIR>/instance/db2iupdt ctginst1

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

133

Manually configuring Oracle 11g


Use the following instructions to manually configure Oracle 11g for use with Maximo Asset Management.

About this task


To configure an existing Oracle 11g server for use with Maximo Asset Management, complete the following steps before launching the Maximo Asset Management installation program:

Procedure
1. Log in as the Oracle software user. Typically this user is named oracle. 2. Create the database listener. The listener manages requests to connect to the database. This step is only required if you do not already have an existing listener in place. a. Open the Oracle Network Configuration Assistant application. b. From the Welcome panel, select Listener configuration, and then click Next. c. From the action panel, select Add, and then click Next. d. Enter a name for the listener or accept the default value, and then click Next. e. Accept the default Selected Protocols listed by clicking Next. f. From the port panel, select Use the standard port of 1521, and then click Next. g. Select No to indicate that you are finished configuring listeners, and then click Next. h. From the Listener Configuration Done panel, click Next. i. Click Finish. 3. Create a database for use by Maximo Asset Management. a. Open the Oracle Database Configuration Assistant. b. Click Next. c. Select Create a Database, and then click Next. d. Select General Purpose or Transaction Processing, and then click Next. e. Enter ctginst1 for both the Global Database Name value and the SID value, and then click Next. f. Leave the defaults selected, and click Next. g. Ensure Use the Same Administrative Password for All Accounts is selected, enter a password for Oracle users, and then click Next h. Ensure File System is selected as the storage mechanism to use for 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 allocation panel, select Custom, provide the following values (measured in Mb), and then click Next. Memory Management Set this value to Manual Shared Memory Management.

134

Installation Guide:

Shared Pool Set this value to 251. Buffer Cache Set this value to 755. Java Pool Set this value to 20 Large Pool Set this value to 114. PGA Size Set this value to 380. m. From the Character Sets tab, select Use Unicode (AL32UTF8). n. Click All Initialization Parameters.... o. Click Show Advanced Parameters. p. Locate the following parameters, change them to the values indicated, and then click Close. nls_length_semantics Change this value to CHAR. open_cursors Change this value to 1000. cursor_sharing Set this value to FORCE. shared_pool_reserved_size Leave set to the default value. q. From the Security Settings panel, accept the defaults, and then click Next. r. From the Automatic Maintenance Tasks panel, accept the defaults, and then click Next. s. t. u. v. From the Initialization Parameters panel, click Next. From the Database Storage panel, click Next. From the Creation Options panel, click Finish. Click Exit to exit the Database Configuration Assistant. The database has been successfully created.

Note: The Oracle Database Configuration Assistant executes the ORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of the configuration of the CTXSYS user. You must execute this script manually if the Oracle Database Configuration Assistant is not used. 4. Create a table space using the following command in SQL*Plus:
Create tablespace maxdata datafile 'C:\oracle\product\11.1.0\db_1\dbs\maxdata.dbf' size 1000M autoextend on;

Change the directory specified in the example to the location where the database will reside. If the directory does not already exist, this command will fail. 5. Create a temporary table space using the following command in SQL*Plus
create temporary tablespace maxtemp tempfile 'C:\oracle\product\11.1.0\db_1\dbs\maxtemp.dbf' size 1000M autoextend on maxsize unlimited;

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

135

Change the directory specified in the example to the location where the database will reside. If the directory does not already exist, this command will fail. 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 connect to maximo; grant create job to maximo; grant create trigger to maximo; grant create session to maximo; grant create sequence to maximo; grant create synonym to maximo; grant create table to maximo; grant create view to maximo; grant create procedure to maximo; grant alter session to maximo; grant execute on ctxsys.ctx_ddl to maximo; alter user maximo quota unlimited on maxdata;

If you created a separate table space for indexing, you must also grant access to that index table space to the maximo user. For example, execute the following command if you created a separate table space for indexing called TSI_MAM_OWN.":
alter user maximo quota unlimited on TSI_MAM_OWN

These instructions assume that you have not modified the default role sets that are assigned to the Oracle DBA user or user IDs created to connect to the database. If you restricted the default privileges granted to user IDs, you must explicitly grant them to the maximo user. So, for example, if you do not by default grant a role such as the select_catalog_role role to user IDs connecting to the database, in order to deploy Maximo Asset Management successfully, you will have to explicitly grant that role to the maximo user by executing the SQL*Plus command:
grant select_catalog_role to maximo

Manually configuring Oracle 10g


About this task
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 Maximo Asset Management, complete the following steps before launching the Maximo Asset Management installation program: 1. Log in as the Oracle software user. Typically this user is named oracle. 2. Create the database listener. The listener manages requests to connect to the database. a. Open the Oracle Network Configuration Assistant application. b. From the Welcome panel, select Listener configuration, and then click Next. c. From the action panel, select Add, and then click Next. d. Enter a name for the listener or accept the default value, and then click Next. e. Accept the default Selected Protocols listed by clicking Next. f. From the port panel, select Use the standard port of 1521, and then click Next.

136

Installation Guide:

g. Select No to indicate that you are finished configuring listeners, and then click Next. h. From the Listener Configuration Done panel, click Next. i. Click Finish. 3. Create a database for use by Maximo Asset Management. 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 allocation panel, select Custom, provide the following values (measured in MB), and then click Next. Shared Memory Management Set this value to Manual. Shared Pool Set this value to 150. Buffer Cache Set this value to 275. Java Pool Set this value to 32. Large Pool Set this value to 8. PGA Size Set this value to 36. m. From the Character Sets tab, select Use Unicode (AL32UTF8). n. Click All Initialization Parameters.... o. Click Show Advanced Parameters. p. Locate the following parameters, change them to the values indicated, and then click Close. nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000. cursor_sharing Set this value to FORCE.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

137

From the Initialization Parameters panel, click Next. From the Database Storage panel, click Next. From the Creation Options panel, click Finish. When the database is successfully created, click Password Management Unlock the CTXSYS account by clearing the check mark in the Lock Account? column for that entry, enter a password for the account, and then click OK. v. Click Exit to exit the Database Configuration Assistant. The database has been successfully created. The Oracle Database Configuration Assistant executes the ORACLE_HOME/ctx/ admin/defaults/drdefus.sql script as part of the configuration of the CTXSYS user. You must execute this script manually if the Oracle Database Configuration Assistant is not used. 4. Create a table space using the following command in SQL*Plus: q. r. s. t. u.
Create tablespace maxdata datafile 'C:\oracle\product\10.2.0\oradata\ctginst1\maxdata.dbf' size 1000M autoextend on;

Change the directory specified in the example to the location where the database will reside. If the directory does not exist, this command will fail. 5. Create a temporary table space 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;

Change the directory specified in the example to the location where the database will reside. If the directory does not exist, this command will fail. 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 connect to maximo; grant create job to maximo; grant create trigger to maximo; grant create session to maximo; grant create sequence to maximo; grant create synonym to maximo; grant create table to maximo; grant create view to maximo; grant create procedure to maximo; grant alter session to maximo; grant execute on ctxsys.ctx_ddl to maximo; alter user maximo quota unlimited on maxdata;

If you created a separate table space for indexing, you must also grant access to that index table space to the maximo user. For example, execute the following command if you created a separate table space for indexing called TSI_MAM_OWN:
alter user maximo quota unlimited on TSI_MAM_OWN

These instructions assume that you have not modified the default role sets that are assigned to the Oracle DBA user or user IDs created to connect to the database. If you restricted the default privileges granted to user IDs, you must explicitly grant them to the maximo user. So, for example, if you do not by default grant a role such as the select_catalog_role role to user IDs connecting to the database, in order to deploy Maximo Asset Management successfully, you must explicitly grant that role to the maximo user by executing the SQL*Plus command:
grant select_catalog_role to maximo

138

Installation Guide:

Manually configuring Oracle9i Rel2


About this task
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 Maximo Asset Management, complete the following steps prior to launching the Maximo Asset Management installation program: 1. Create a new database for use by Maximo Asset Management. 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. 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 cursor_sharing Set this value to FORCE. 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.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

139

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. This procedure ensures that the Maximo database does not share a temporary table space with other instances of the database and enables you to control its size. 4. 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 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;

What to do next

Manually configuring DB2 8.2


About this task
To configure an existing DB2 8.2 server for use with Maximo Asset Management, complete the following steps prior to launching the Maximo Asset Management 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

140

Installation Guide:

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 OS
db2icrt -s ese -u db2admin,password -r 50005,50005 ctginst1

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

AIX 64-bit system


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

b. Set the listening port for the instance Windows OS


db2 update dbm cfg using svcename 50005

c. Set instance service to start automatically Windows OS


sc config ctginst1-0 start= auto

d. Start the ctginst1 database instance: Windows OS


db2start

Linux or UNIX OS
su - ctginst1 db2start

3. Create the database: Windows OS 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

Linux or UNIX OS 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_serverInstancesCTGINST1DatabasesMAXDB71 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.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

141

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. 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 Maximo Asset Management. 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. 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 Space management panel, specify Database-managed space and click Next. j. From the Containers panel, click Add. k. Set the Type to File, Size to 5000 Mb, and File name to CTGDAT. 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. b. c. d. e. f.

142

Installation Guide:

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 Maximo Asset Management. 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. 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 Maximo Asset Management. 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 Maximo Asset Management. 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 listed in the prerequisites topic in the chapter that describes how to prepare for the installation. If you installed a fix pack, run the dasupdt command to update the DB2 Administration Server to the applied fix pack.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

143

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 OS
C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1

Linux or UNIX OS
<DB2DIR>/instance/db2iupdt ctginst1

Manually configuring SQL Server


You can manually configure Microsoft SQL Server for use with Maximo Asset Management.

Before you begin


Microsoft SQL Server provides limited multilingual support. You can support multiple languages on one database instance only if they share the same character set. For example, a database instance can support English, French, and Portuguese which use the same character set but does not support Portuguese and Chinese because they have different character sets. Microsoft SQL Server collation settings must be set to the following options: v Dictionary order v Case-insensitive v For use with 1252 Character set

About this task


To configure an existing Microsoft SQL Server for use with Maximo Asset Management, complete the following steps before launching the Maximo Asset Management installation program: This procedure describes an installation of Microsoft SQL Server 2008. Follow the same procedure to install Microsoft SQL Server 2005, substituting 2005 for 2008 in directory paths.

Procedure
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 Microsoft SQL Server Database Engine and Microsoft SQL Server Compact Edition are configured select any available port when the service starts. When connecting to a named instance across a firewall, configure the Database Engine to listen on a specific port, to open this port in the firewall. a. Open Programs Microsoft SQL Server 2008 Configuration Tools SQL Server Configuration Manager b. From the Microsoft SQL Server Configuration Manager navigation pane, expand SQL Server Network Configuration Protocols for <instance name>, 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 that 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 Maximo Asset Management requires Microsoft 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.

144

Installation Guide:

f. Click OK. g. From the SQL Server Configuration Manager navigation pane, click SQL Server Services. h. Right-click SQL Server (<instance name>) and then click Restart, to stop and restart Microsoft SQL Server. i. Verify the Microsoft SQL Server instance is running, and then close SQL Server Configuration Manager. 2. Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server 2008. To determine if Full-text Search is installed on your existing Microsoft SQL Server database, perform the following steps: a. Open SQL Server Management Studio, choose SQL Server Authentication as the authentication type, and enter the credentials for the sa user ID, and then click Connect. b. Click New Query. c. Type the following command:
select FULLTEXTSERVICEPROPERTY ( 'IsFulltextInstalled' )

If you did not install Full-text Search (the resulting value is zero), you must do so at this time. To install Full-text Search, insert the Microsoft SQL Server 2008 product media into the system and launch the installation wizard. Navigate through the wizard and enable the Full-Text Search option located on the Custom portion of the Setup Type dialog box. To finish the installation process, restart the server. 3. Create a Microsoft SQL Server Database. a. Open SQL Server Management Studio (Start Programs Microsoft SQL Server 2008 SQL Server Management Studio) b. Right-click the Databases folder from the tree view, and select New Database. c. In the Database name field, specify a unique database name (for example maxdb71) d. For the maxdb71 Logical Name, change the Initial Size (MB) attribute to 500 (MB), and set the Autogrowth value to By 1MB, unrestricted growth. e. If you prefer, modify the log settings to accommodate your production environment. f. Click OK. 4. Create the Maximo User for Microsoft SQL Server. a. Open Microsoft SQL Server Management Studio (Start Programs Microsoft SQL Server 2008 SQL Server Management Studio) b. Click New Query. c. Select the Maximo Asset Management database (maxdb71) from the Available Databases drop-down menu, d. Enter the following script to create the Microsoft SQL user ID MAXIMO with a password of MAXIMO.
sp_addlogin MAXIMO,MAXIMO go

This value is case sensitive. e. Click Execute. f. Enter the following script to change the database owner to maximo.
sp_changedbowner MAXIMO go
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

145

g. Click Execute.

What to do next
If you add additional logical names to the database and set their file group to a value other than PRIMARY, you must complete the following steps after you set up the database and create the Maximo user: 1. Run the Maximo Asset Management installation program and choose the Do not run the configuration step now option. 2. Add the following property to the <Maximo_Home>\applications\maximo\ properties\maximo.properties file:
Database.SQL.DataFilegroupName=<your logical name>

3. Run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility, located in the <MAM_HOME>\scripts directory. Complete these additional steps only if you 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 Maximo Asset Management installation program if you choose to not have the Maximo Asset Management installation program automatically configure it. Important: When entering LDAP values for Maximo Asset Management installation panel fields, entries in LDIF files, or values you enter directly into an directory instance using the directory server's 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 Maximo Asset Management will result in Maximo Asset Management 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 Maximo Asset Management 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


Use the following instructions to manually configure IBM Tivoli Directory Server for use with Maximo Asset Management.

About this task


To configure IBM Tivoli Directory Server before launching the Maximo Asset Management installation program, you must create a new instance of IBM Tivoli Directory Server. Note: While you can technically share a DB2 instance between Maximo Asset Management and the one needed by IBM Tivoli Directory Server, it is not a

146

Installation Guide:

recommended practice. During the installation, the database instance restarts, which can disrupt the availability of IBM Tivoli Directory Server to your enterprise. If you are using the automated installation programs, separate instances are created for use by Maximo Asset Management and IBM Tivoli Directory Server.

Procedure
1. Using your preferred method, create a user on the system and assign it to the appropriate group. Windows OS Create the user idsccmdb and make it a member of the following groups: v Windows Administrators v DB2ADMNS v DB2USERS Linux or UNIX OS Create the user idsccmdb and make it a member of the root, db2iadm1, 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 OS Select Programs IBM Tivoli Directory Server 6.2 Instance Administration Tool. Linux or UNIX OS Type ./opt/IBM/ldap/V6.2/sbin/idsxinst at the command line. 3. In the Instance Administration Tool, click Create an instance. 4. In the Create a new instance window, click Create a new directory server instance, and then click Next. 5. From the Instance details window, complete the following fields, and then click Next. User name Select idsccmdb as the system user ID of the user who will own the instance. This name will also be the name of the instance. Install location Enter the location where the 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. In the DB2 instance details panel, enter idsccmdb as the value for the DB2 instance name field, and then click Next. 7. In the TCP/IP settings for multihomed hosts panel, select Listen on all configured IP addresses, and then click Next. 8. In 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.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

147

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. In the Option steps panel, leave the following options selected, and then click Next. Configure admin DN and password Configure the administrator DN and password for the instance now. Configure database Configure the database for the directory server now. 10. In 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. Database name Enter idsccmdb as the database to be used with this directory instance. 12. In the Database options panel, complete the following fields, and then click Next. Database install location Type the location for the database in the Database install location field Windows OS For Windows platforms, this must be a drive letter. Linux or UNIX OS For non-Windows platforms, the location must be a directory name, such as /home/ldapdb. Ensure that you have at least 80 MB of free hard disk space in the location you specify and that additional disk space is available to accommodate growth as new entries are added to the directory. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected. In 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. Launch the IBM Tivoli Directory Server Configuration Tool:

13. 14. 15. 16.

148

Installation Guide:

Windows OS SelectPrograms IBM Tivoli Directory Server 6.2 Instance Administration Tool. Linux or UNIX OS Type ./opt/IBM/ldap/V6.2/sbin/idsxcfg at the command line. 17. Select Manage suffixes. 18. In the Manage suffixes panel, type the following suffix, and then click Add.
o=IBM,c=US

19. Click OK. 20. Create and save an LDIF file. Add the DN information, for example: v ou=SWG,o=IBM,c=US v ou=users v ou=groups Note: ou=SWG,o=IBM,c=US in this example refers to an organization unit called SWG which is where we intend to create OU=Groups and OU=Users organization units to place the users created for Maximo Asset Management. DC=IBM and DC=COM would indicate a domain forest of ibm.com. You can replace the example shown above with the directory structure of your own organization. Define the following users and groups and their positions within the ou=users and ou=groups DN's you created. These users and groups are defined in order for Virtual Member Manager to be used to secure Maximo Asset Management. Important: Before you begin this procedure, ensure you have the following users and groups created in your LDAP repository:
Table 15. Base Maximo Asset Management required users User wasadmin maxadmin mxintadm maxreg

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
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

149

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 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

Note: If you create the LDIF file on Windows, ensure that you remove the ^M characters from the file before using. Note: Before you can import an LDIF file on UNIX systems, you must run the dos2unix command to format the file. 21. In the IBM Tivoli Directory Server Configuration Tool, click Import LDIF data. 22. Use the browse button to locate the LDIF file. 23. Click Import. 24. Close the IBM Tivoli Directory Server Configuration Tool and restart the server.

Manually configuring Microsoft Active Directory


You can manually configure Microsoft Active Directory for use with Maximo Asset Management.

150

Installation Guide:

Before you begin


Use this procedure to manually create users and groups within Microsoft Active Directory. You can create these users and groups automatically if you configure SSL communication between Microsoft Active Directory and WebSphere Application Server Network Deployment. Instructions for configuring SSL are provided following this section. Important: The users and passwords you create in the following steps must match this exact configuration for the deployment to succeed. It is sometimes necessary to temporarily alter theMicrosoft Active Directory security policy to create these accounts in the required format. After installation, you can change these default passwords to conform to a stricter security policy. Although you can use Windows Server 2008 as a platform for the administrative workstation, or to host middleware, Maximo Asset Management does not support Active Directory on Windows Server 2008.

About this task


If you choose to manually configure a Microsoft Active Directory resource for use with Maximo Asset Management, complete the following steps before running the Maximo Asset Management installation program:

Procedure
1. Select Start Control Panel Administrative Tools Microsoft Active Directory Users and Computers and then select the domain that you will be working with. 2. Edit the functional level of the domain by selecting Action Raise Domain Functional Level. The Raise Domain Functional Level dialog box will appear. 3. Select Microsoft Windows Server 2003 from the Select an available domain functional level dropdown menu, and then click Raise. An alert dialog box will appear. 4. Click OK. 5. When the domain raise task has completed, click OK. 6. In the Microsoft Active Directory Users and Computers user interface, right-click the domain you want to work with and select New Organizational Unit. 7. Enter a name for the new Organizational Unit (OU), for example, SWG, and then click OK. 8. Create a groups object under the SWG organizational unit: a. Right-click the SWG OU, and select New Organizational Unit. b. Enter Groups as the name for the new OU then click OK. 9. Create a users object under the SWG organizational unit: a. Right-click the SWG OU, and select New Organizational Unit. b. Enter Users as the name for the new OU then click OK. 10. Create the wasadmin user: a. Right click the Users OU and select New User. b. From the New Object - User dialog, enter the following values, and then click Next:

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

151

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-Microsoft Windows 2000) This field is 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: Password Enter a 7 character password for wasadmin. User must change password at next logon Ensure this check box is deselected. User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is deselected. The preceding values are examples. Enter values that comply with the password policy of your organization. d. Review the password settings in the summary panel, and click Finish. 11. Create an administrator user, for example maxadmin: a. Right click the Users OU and select New User. b. From the New Object - User dialog, enter the following values, and then click Next: First 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-Microsoft Windows 2000) This field will be filled with the same value (maxadmin) entered for the User login name.

152

Installation Guide:

c. From the next panel, enter the following information, and then click Next: Password Enter maxadmin as the password for the maxadmin user. This password value is required and expected by the Maximo Asset Management installation program. If you must use a different password value for this user, you must defer the configuration step of the Maximo Asset Management installation, modify property values, and complete the configuration using the taskrunner utility. Complete the following steps if you choose to use a different value for the maxadmin password: 1) Complete middleware installation and configuration, including the manual Microsoft Active Directory configuration tasks described in this topic, providing a password value other than maxadmin for the maxadmin user. 2) Begin the Maximo Asset Management installation. 3) Proceed with the installation and select the option Copy files now, and perform installation configuration later, manually . Complete the installation. 4) Edit the <MAM_HOME>\etc\install.properties file and provide the desired value for the mxe.adminPasswd property. 5) Complete product configuration by using the taskrunner utility:
MAM_HOME\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

6) Edit the <MAM_HOME>maximo\reports\birt\tools\ reporttools.properties file and provide the same password value for the maximo.report.birt.password property. User must change password at next logon Ensure this check box is deselected. User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is deselected. The preceding values are examples. Enter values that comply with the password policy of your organization. d. Review the password settings in the summary panel, and click Finish. 12. 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: First name Enter mxintadm. Initials Leave this field blank. Last name Leave this field blank.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

153

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-Microsoft 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 check box is deselected. User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is deselected. The preceding values are examples. You should set these fields to values that comply with the password policy of your organization. d. Review the password settings in the summary panel, and click Finish. 13. Create the maxreg user: 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-Microsoft Windows 2000) This field is 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: Password Enter a 7 character value as the password for the maxreg user. User must change password at next logon Ensure this check box is deselected.

154

Installation Guide:

User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is deselected. The preceding values are examples. Enter values that comply with the password policy of your organization. d. Review the password settings in the summary panel, and click Finish. 14. 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, maxreg, 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. 15. 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 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. 16. You can now exit the Microsoft Active Directory Users and Computers user interface.

What to do next
Microsoft Active Directory configuration is complete and you are now ready to install the remaining Maximo Asset Management middleware and configure the J2EE server to use Microsoft Active Directory. Configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment: This section provides details on configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

155

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

156

Installation Guide:

8. 9. 10. 11. 12. 13. 14.

15.

16. 17. 18. 19. 20.

Restart the system. Launch Internet Explorer. Select Tools Internet Options Security and click Sites. From the Trusted Sites dialog box, enter http://mymachine.ism71.com in the Add this Web site to the zone: field, click Add, and then click Close. Enter the following address in the browser: http://mymachine.ism71.com/ certsrv From the Certificate Services page, click Download a CA certificate, Certificate Chain, or CRL. From the Download a CA Certificate, Certificate Chain, or CRL page, click install this CA certificate chain. When the task has completed successfully, click the back button. From the Download CA Certificate, Certificate Chain, or CRL page select Current for the CA certificate value, choose Base 64 for the Encoding method, and then click Download a CA Certificate. When prompted, specify the type as Security Certificate and save the security certificate file as serverRootCA.cer. Launch the Microsoft Management Console. Select File Add/Remove Snap-in. From the Add/Remove Snap-in dialog box, click Add. From the Add Standalone Snap-in dialog box, select Certificates and then click Add.

21. Select Computer account and then click Next. 22. Select Local computer: (the computer this console is running on) and click Finish. 23. From the Add Standalone Snap-in dialog box, select Certification Authority and then click Add. 24. Select Local computer: (the computer this console is running on) and click Finish. 25. Click Close to close the Add Standalone Snap-in dialog box. 26. Click OK on the Add/Remove Snap-in dialog box to close it. 27. In the Microsoft Management Console, navigate to Console Root Certificates (Local Computer) Third-Party Root Certification Authorities. 28. Right-click Certificates and select All Tasks Import. 29. From the File to Import panel of the Certificate Import wizard, browse to the location of your serverRootCA.cer file, select it, and then click Next. 30. From the Certificate Store panel, select Place all certificates in the following store, click Next, and then click Finish. 31. Using Internet Explorer, navigate to http://mymachine.ism71.com/certsrv. From the Certificate Services page, click Request a certificate. 32. From the Request a Certificate page, click advanced certificate request. 33. From the Advanced Certificate Request page, click Create and submit a request to this CA. 34. From the Advanced Certificate Request page, enter the following information and then click Submit. Identifying Information For the Name field, enter the fully qualified name of the machine hosting Microsoft Active Directory. This value must be capitalized, for example MYMACHINE.ISM71.COM.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

157

Type of Certificate Needed Select Server Authentication Certificate. Key Options For the CSP field, select Microsoft RSA SChannel Cryptographic Provider. Select the Automatic key container name, Mark keys as exportable, and Store certificate in the local computer certificate store options. For the Key Size field, you can either accept the default value of 1024, or change it to a more appropriate value. Additional Options Set the Request Format option to PKCS10. For the Hash Algorithm field, select SHA-1. For the Friendly Name field , enter the same exact value as entered for the Name field. Default values are sufficient for the remaining fields on this page. 35. Click Home to return to the home page for Certificate Services. 36. In the Microsoft Management Console, navigate to Console Root Certification Authority (Local) mycomputer.ism71.com Pending Requests. 37. In the right pane, right-click the ID of the request, and then select All Tasks Issue. 38. From Internet Explorer, on the Certificate Services page, click View the status of a pending certificate request. 39. From the View the Status of a Pending Certificate Request page, click the certificate request you created. 40. From the Certificate Issued page, click Install this certificate. 41. Restart the system. 42. When the system has restarted, invoke the Microsoft Management Console and navigate to Console Root Certificates (Local Computer) Personal Certificates. 43. In the right pane, double-click the entry displayed in uppercase. 44. From the Certificate dialog box, ensure you can find the statement You have a private key that corresponds to this certificate, and then click OK. 45. In the right pane, double-click the entry displayed in lowercase. 46. From the Certificate dialog box, ensure you can find the statement You have a private key that corresponds to this certificate, and then click OK. 47. 48. 49. 50. 51. 52. 53. 54. Launch the Microsoft LDP utility. Select Connection. Select Connect. Enter mymachine.ism72.com for Server, 636 for Port, select SSL, and then click OK. Review the information displayed to verify your configuration values. Launch the Microsoft Management Console and navigate to Console Root Certificates (Local Computer) Personal Certificates. Right-click the uppercase certificate entry and select All Tasks Export From the Certificate Export Wizard Welcome panel, click Next. From the Export Private Key panel, select No, do not export private key, and then click Next.

158

Installation Guide:

55. From the Export File Format panel, select Base-64 encoded X.509(.CER), and then click Next. 56. From the File to Export panel, export the certificate as serverRootCA.cer, click Next, and then click Finish. 57. Right-click the lowercase certificate entry and select All Tasks Export 58. From the Certificate Export Wizard Welcome panel, click Next. 59. From the Export Private Key panel, select No, do not export private key, and then click Next. 60. From the Export File Format panel, select Base-64 encoded X.509(.CER), and then click Next. 61. From the File to Export panel, export the certificate as serverAuthCert.cer, click Next, and then click Finish. 62. Copy serverRootCA.cer and serverAuthCert.cer to the WebSphere Application Server Network Deployment system. 63. Invoke the WebSphere Application Server Network Deployment administrative console. 64. From the WebSphere Application Server Network Deployment administrative console, select Security SSL certificate and key management. 65. Click Keystores and certificates. 66. Click CellDefaultTrustStore. 67. Click Signer certificates and then click Add. 68. From the Add signer certificate page, enter MSADServerRootCA for the Alias, enter the path (including the file name) to the serverRootCA.cer file in the File name field, and then click OK. 69. Click Add. 70. Enter MSADServerAuthCert for the Alias, enter the path (including the file name) to the serverAuthCert.cer file in the File name field, and then click OK. 71. From the WebSphere Application Server Network Deployment administrative console, select Security Secure administration, applications, and infrastructure. 72. From the Available realm definitions drop-down list, select Federated repositories, and then click Configure. 73. Click the repository identifier for Microsoft Active Directory listed in Repositories in the realm table. 74. Update the following properties and then click OK. Port Update this value to 636.

Login properties Set this value to cn. Requires SSL communications Ensure that this option is selected. Use specific SSL alias Ensure that this option is selected with a value of CellDefaultSSLSettings. 75. Click Supported entity types and verify that the PersonAccount entity type is set to cn. If it is not set to cn, click the PersonAccount entity type and set it and then save the changes. 76. Restart the domain manager.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

159

Manually configure the J2EE server


This section contains instructions for manually configuring an existing J2EE server for use by Maximo Asset Management. If you want to deploy Maximo Asset Management using Oracle WebLogic Server, you must configure it manually. If you want to deploy Maximo Asset Management with WebSphere Application Server Network Deployment, you can perform a manual configuration if automatic configuration does not meet your requirements. A supported JDEE server must be installed and configured before you install Maximo Asset Management.

Manually configuring Websphere


You can configure Websphere manually to work with Maximo Asset Management. Creating WebSphere Application Server Network Deployment profiles: If you are manually configuring WebSphere Application Server Network Deployment, profiles must be created before launching the Maximo Asset Management installation program Before you begin You cannot use the Profile Management tool to create profiles for 64-bit platforms. For 64-bit platforms, see Creating IBM WebSphere Application Server profiles at http://www-01.ibm.com/support/docview.wss?rs=0&q1=7015423 &uid=swg27015423&loc=en_CA&cs=utf-8&cc=ca&lang=en. About this task You must complete the manual configuration of the J2EE server before you use the Maximo Asset Management installation program if you choose to not have the Maximo Asset Management installation program automatically configure it. To configure the J2EE server prior to launching the Maximo Asset Management 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 Maximo Asset Management administrative system where you are installing Maximo Asset Management: <WAS_home>/profiles/ctgDmgr01/etc/trust.p12 2. Launch the profile creation wizard. 3. Click Next in the Welcome dialog box. 4. Select the create a deployment manager option. Click Next. 5. Accept the default value or specify a Profile name. Click Next. 6. Accept the default installation location. Click Next. 7. Accept the default values or specify the Node name, Host name, and Cell name. Click Next. 8. Review the assigned port numbers. Click Next. Note the Administrative port number. You will use this context when invoking the console through a browser.

160

Installation Guide:

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: You can manually configuring Virtual Member Manager (VMM) to secure Maximo Asset Management if you want to use LDAP to secure the application server.. About this task During the installation process, the Maximo Asset Management installation program provided you with the option of automatically configuring Maximo Asset Management middleware. If you elected to have the Maximo Asset Management installation program automatically configure Maximo Asset Management middleware, then it will, among other tasks, perform Virtual Member Manager (VMM) configuration for you. If you elected to manually configure Maximo Asset Management middleware for use with Maximo Asset Management, 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 Maximo Asset Management installation. If VMM is configured to use SSL with a federated LDAP repository prior to completing the Maximo Asset Management installation, the installation will fail. Do not configure a WebSphere VMM LDAP federated repository to use

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

161

SSL with an LDAP directory prior to installing Maximo Asset Management. Configure SSL after the Maximo Asset Management 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. These instructions are for IBM Tivoli Directory Server. To configure VMM to use Microsoft Active Directory, substitute the values you used when you configured Microsoft Active Directory where appropriate in this procedure. You must also modify the VMM cron task. 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. 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.

162

Installation Guide:

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. 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.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

163

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. What to do next Performing WebSphere Application Server Network Deployment configuration tasks: Use this procedure to perform WebSphere Application Server Network Deployment configuration tasks. About this task During the installation process, the Maximo Asset Management installation program provided you with the option of automatically configuring Maximo Asset Management middleware. If you elected to have the Maximo Asset Management installation program automatically configure Maximo Asset Management middleware, then it will, among other tasks, perform WebSphere Application Server Network Deployment configuration for you. If you elected to manually configure middleware for use with Maximo Asset Management, you will have to manually configure WebSphere Application Server Network Deployment. 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 Application Server Network Deployment using the middleware installer.

164

Installation Guide:

a. b. c. d. e.

Expand the Servers link and click Application servers. Click New. Type MXServer and click Next. Accept all default settings and click Next. Accept default settings and click Next.

f. Click Finish. g. Click Preferences. h. Check the Synchronize changes with Nodes check box, and then click Apply. i. Click Save. j. Click OK. 3. Edit JVM Memory Settings for the application server a. From the Servers link in the 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. The default settings for Java Virtual Machine can be adequate. However, if you encounter memory or performance issues, you can adjust JVM memory settings. You can use the ackTimeout parameter to avoid memory leaks in a high-performance environment. The default value for the ackTimeout parameter is 600000 milliseconds or 10 minutes. The recommended setting is 10000 or 10 seconds. Reducing the ackTimeout value causes the server to check objects more often and can increase CPU utilization. If you plan to change this value, balance performance requirements against CPU utilization. The argument to change the parameter is -Dsun.rmi.dgc.ackTimeout=10000. To improve the performance of TCP/IP V4 packets, you can set -Djava.net.preferIPv4Stack=true, so that WebSphere Application Server does not have to programmatically determine them. To set these parameters in the WebSphere Application Server admiistration console, select Application servers > application name > Process Definition > Java Virtual Machine, and enter the relevant argument in the Generic JVM Argument field. 5. Start the application server:
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

165

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: 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. f. Click Save. g. h. i. j. 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. l. Click New. m. Type * (asterisk) for Host Name and type 9061 for the port number. n. Click OK. o. p. q. r. Click New. Type * (asterisk) for Host Name and type 9443 for the port number. Click OK. Click New.

s. Type * (asterisk) for Host Name and type 9080 for the port number. t. Click OK. u. Click New. v. Type * (asterisk) for Host Name and type 9044 for the port number. w. Click OK. x. From the navigational breadcrumb trail, click maximo_host. y. Click Apply and then click OK. What to do next Manually configuring Java Messaging Services: If you perform a manual configuration of the J2EE server, you must manually configure Java Messaging Services (JMS). To configure JMS, enable it on the J2EE server and then create the messaging queues. Adding a server to the service integration bus:

166

Installation Guide:

A server must be defined for the service integration bus. Before you begin About this task Complete the following steps to add a server to the service integration bus: Procedure 1. From the WebSphere Application Server Network Deployment 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. 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. What to do next Creating the service integration bus destination for the continuous inbound (CQINBD) queue: You must create a service integration bus destination for the continuous inbound (CQINBD) queue.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

167

Before you begin About this task To add a logical address for the continuous inbound bus destination queue (CQINBD) within the JMS bus, complete the following steps: Procedure 1. From the WebSphere Application Server Network Deployment 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. 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. 11. Click None as the Exception destination value. 12. Click Apply. 13. Click Save. What to do next Creating the service integration bus destination for the sequential inbound (SQINBD) queue: You must create the service integration bus destination for the sequential inbound (SQINBD) queue. Before you begin About this task To add a logical address for the sequential inbound bus destination queue (SQINBD) within the service integration bus, complete the following steps: Procedure 1. From the WebSphere Application Server Network Deployment Administrative Console, click Service Integration Buses to open the Buses dialog box. 2. Click intjmsbus to open the Buses intjmsbus dialog box.

168

Installation Guide:

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. 11. Click None as the Exception destination value. 12. Click Apply. 13. Click Save. What to do next Creating the service integration bus destination for the sequential outbound (SQOUTBD) queue: You must create the service integration bus destination for the sequential outbound (SQOUTBD) queue. Before you begin About this task To add a logical address for the sequential outbound bus destination queue (SQOUTBD) within the service integration bus, complete the following steps: Procedure 1. From the WebSphere Application Server Network Deployment 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. 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.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

169

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 queue. 10. Navigate the path Buses intjmsbus Destinations, then click SQOUTBD to open the configuration dialog box where you must make the following changes: 11. Click None as the Exception destination value. 12. Click Apply. 13. Click Save. What to do next Creating the JMS connection factory: Add a connection factory for creating connections to the associated JMS provider of point-to-point messaging queues. Before you begin About this task To create the JMS connection factory, complete the following steps: Procedure 1. From the WebSphere Application Server Network Deployment Administrative Console, click Resources JMS Connection factories. 2. 3. 4. 5. From the Scope drop-down list select Cell=ctgCell01, and then click Apply. Click New. Verify that the Default Messaging Provider is selected and click OK. Enter the following information: Name Enter intjmsconfact. JNDI name Enter jms/maximo/int/cf/intcf. Bus name Select intjmsbus. 6. Click Apply. 7. Click Save. 8. Click OK. What to do next Creating the continuous inbound (CQIN) JMS queue: You must create a JMS queue (CQIN) as the destination for continuous inbound point-to-point messages.

170

Installation Guide:

Before you begin About this task To create the CQIN JMS queue, complete the following steps: Procedure 1. From the WebSphere Application Server Network Deployment Administrative Console, click Resources JMS Queues. 2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply. 3. Click New. 4. Verify that the Default Messaging Provider is selected and click OK. 5. Enter the following information, and click OK. Name Enter CQIN. Note that this value must contain only uppercase letters. JNDI name Enter jms/maximo/int/queues/cqin Bus name Select intjmsbus. Queue name Select CQINBD. 6. Click OK. 7. Click Save. What to do next Creating the sequential inbound (SQIN) JMS queue: Before you begin About this task You must create a JMS queue (SQIN) as the destination for sequential inbound point-to-point messages. Procedure 1. From the WebSphere Application Server Network Deployment 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 that this value must contain only uppercase letters. JNDI name Enter jms/maximo/int/queues/sqin Bus name Select intjmsbus.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

171

Queue name Select SQINBD. 6. Click OK. 7. Click Save. What to do next Creating the sequential outbound (SQOUT) JMS queue: Before you begin About this task You must create a JMS queue (SQOUT) as the destination for sequential outbound point-to-point messages. Procedure 1. From the WebSphere Application Server Network Deployment 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 that this value must contain only uppercase letters. JNDI name Enter jms/maximo/int/queues/sqout Bus name Select intjmsbus. Queue name Select SQOUTBD. 6. Click OK. 7. Click Save. What to do next Manually create JMS error queues: You must create an 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: You must add a logical address for the inbound error queue (CQINERRBD) queue within the JMS bus.

172

Installation Guide:

Before you begin About this task Complete the following steps: Procedure 1. From the WebSphere Application Server Network Deployment 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 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. 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 CQINERRBD bus destination queue. 10. Navigate the path Buses intjmsbus Destinations, then click CQINERRBD to open the configuration dialog box where you must make the following changes: a. Click Specify and enter CQINERRBD as the exception destination value. b. 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. From the WebSphere Application Server Network Deployment Administrative Console, click Service Integration Buses to open the Buses dialog box. Click intjmsbus to open the Buses intjmsbus dialog box. Click Destinations under Destination resources to open the Buses intjmsbus Destinations dialog box. Select CQINBD. Specify CQINERRBD as the exception destination. . Set the Maximum failed deliveries value to 5. Click OK. Click Save.

11. 12. 13. 14. 15. 16. 17. 18. 19.

What to do next Creating the error (CQINERR) JMS queue: After creating the Error Queue Bus Destination, you create the Error queue.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

173

Before you begin About this task To create the Error queue, complete the following steps. Procedure 1. From the WebSphere Application Server Network Deployment 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 that this value must contain only uppercase letters. JNDI name Enter jms/maximo/int/queues/cqinerr Bus name Select intjmsbus. Queue name Select CQINERRBD. 6. Click OK. 7. Click Save. What to do next Creating JMS activation specification for the continuous inbound queue (CQIN): You must activate the continuous inbound queue (CQIN) before it can receive messages. Before you begin About this task Complete the following steps to activate the CQIN queue: Procedure 1. From the WebSphere Application Server Network Deployment Administrative Console, click Resources JMS Activation Specifications. 2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply. 3. Click New to complete the General Properties section for the new JMS activation specification. 4. Click OK. 5. Enter the following information, and then click OK. Name intjmsact This value is case-sensitive. This value must be lowercase. JNDI name intjmsact

174

Installation Guide:

Destination type Queue Destination JNDI name jms/maximo/int/queues/cqin Bus name intjmsbus Maximum concurrent endpoints 10 6. Click OK, and then click Save. What to do next Creating JMS activation specification for the inbound error queue (CQINERR): You must activate the continuous inbound queue (CQINERR) before it can receive messages. Before you begin About this task Complete the following steps to activate the CQINERR queue: Procedure 1. From the WebSphere Application Server Network Deployment Administrative Console, click Resources JMS Activation Specifications. 2. From the Scope drop-down list, select Cell=ctgCell01, and then click Apply. 3. Click New to complete the General Properties section for the new JMS activation specification. 4. Click OK. 5. Enter the following information, and click OK. Name Enter intjmsacterr. This value must only contain lowercase letters. JNDI name Enter intjmsacterr. This value must be the same as the one used for the Name field. Destination type Enter Queue. Destination JNDI name jms/maximo/int/queues/cqinerr Bus name intjmsbus Maximum concurrent endpoints 10 Click OK. Click Save. Ensure you stop all IBM-related processes and daemons. You must now restart these processes for the update to take effect.

6. 7. 8. 9.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

175

10. 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. What to do next Manually creating a data source for the persistent store: If you chose to manually configure WebSphere Application Server Network Deployment, you will need to create a data source in order to store JMS messages in a DB2 database. About this task You have the option of having WebSphere Application Server Network Deployment use a DB2 database to store JMS messages. For more information about WebSphere Application Server Network Deployment 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 To create a data source for the persistent store, complete the following steps: Procedure 1. Create a system user and password on the server hosting the database server. For example, a user named mxsibusr with a password of mxsibusr. 2. Create and configure the database. a. Open DB2 Control Center. Navigate down to the Databases folder listed under your system. Right-click the Databases folder and select Create Database Standard. Create a database named maxsibdb using default settings. 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 Application Server Network Deployment. a. Open and login to the WebSphere Application Server Network Deployment Administrative Console. b. Navigate to Security Secure administration, applications, and infrastructure. b. c. d. e. 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.

176

Installation Guide:

Alias

maxJaasAlias

User ID mxsibusr Password Password you created for mxsibusr. Description SIB database user alias. Click Apply, and then click Save. From the WebSphere Application Server Administrative Console navigation pane, navigate to Resources JDBC JDBC Providers. Click Scope and then select Cell=ctgCell01, and then click Apply. Click New. Specify the following values, and then click Apply: Database type DB2 Provider type DB2 Universal JDBC Driver Provider Implementation type XA data source Name maxJdbcProvider k. Click Next. l. Complete the WebSphere Application Server 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. 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 Application Server: a. From the WebSphere Application Server Network Deployment 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.
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

f. g. h. i. j.

177

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 data source by selecting intjmsds, and then clicking Test Connection. What to do next

Manually configuring the WebLogic server


Complete the manual configuration of the WebLogic Server before you run the Maximo Asset Management installation program.

Before you begin


If you do not have Oracle WebLogic Server 9.2.2 installed, follow the instructions that come with WebLogic Server to install it. Ensure that you do not install the Node Manager Service.

About this task


To configure the WebLogic server prior to launching the Maximo Asset Management installation program, follow these steps:

Procedure
1. Launch the Configuration Wizard.
Platform Windows Command From the Start menu: Start > All Programs > BEA Products > Tools > Configuration Wizard. cd to /<product_installation_dir>/common/ bin and type sh config.sh

UNIX

2. From the Welcome window, accept the default to create a WebLogic domain and then click Next. 3. From the Select Domain Source window, accept the default value to generate a domain configured automatically and click Next. 4. Enter an administrator user name and a password and then click Next.

178

Installation Guide:

5. From the Configure Server Start Mode and JDK window, select Production Mode in the WebLogic Domain Startup Mode section, and Sun JDK 1.5.0_04 in the Oracle Supplied JDKs section. Click Next. 6. From the Customize Environment and Services settings window, select Yes if you plan to implement the integration framework. If you select Yes, configure JMS options after you finish configuring the WebLogic Server. See the topic about coinfguring JMS for Oracle WebLogic Server in the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions. 7. From the Create WebLogic Domain window, accept the default value or specify a different domain name and then click the Create button. The domain is created in a minute. 8. Click Done. Do not select the checkbox for Start Admin Server.

What to do next
You then must install the updated Sun JDK 1.5.0. Performing post installation tasks for the WebLogic Server: Use this procedure to perform post installation steps for the WebLogic Server. About this task 1. Install the updated Sun JDK 1.5.0. a. Obtain the latest Sun JDK 1.5.0 program, for example, JDK 1.5.0_14, from this URL: http://java.sun.com. b. Start the installation program. On Windows, it is jdk-1_5_0_14windowsi586p.exe c. Accept the license agreement. d. Change the installation destination path to be within your Oracle Home folder, for example, c:\bea\jdk150_14, and click OK then Next. e. Accept any additional prompts to install the Sun JRE so that the installation process can complete successfully. 2. Edit the domain configuration file for proper Java settings. Windows: Navigate to C:\bea\user_projects\domains\mydomain\bin. UNIX: Navigate to <home_directory>/bea/user_projects/domains/mydomain/ bin. a. Right-click and edit (do not double-click) setDomainEnv.cmd (Windows) or setDomainEnv.sh (UNIX). b. Using your text editor, search for and replace jdk150_04 with jdk150_14 to point WebLogic to use the updated Sun JDK. Two instances must be replaced. c. (Oracle only) Search for PRE_CLASSPATH. Set the parameter as follows:
set PRE_CLASSPATH=%WL_HOME%\server\lib\oraclethin.jar (Windows) PRE_CLASSPATH={WL_HOME}/server/lib/oraclethin.jar (UNIX)

Note: This step is required for connecting to Oracle databases from the WebLogic Server. d. Increase the Java Heap parameters by searching for MEM_ARGS and setting the parameter as follows:
set MEM_ARGS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m (Windows) MEM_ARGS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m (UNIX)
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

179

These parameters are case sensitive. Ensure to include the minus (-) sign before each parameter and to include the m after each value. e. Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Insert an option right after this string as follows:
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0

The entry will look like this when complete:


set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dwlw.iterativeDev=%iterativeDevFlag% -Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%logErrorsToConsoleFlag%

f. Save and close the setDomainEnv.cmd file. 3. Start the Server without being prompted for user name and password. If you are working in Production mode and do not want to be prompted for the WebLogic user name and password, create a boot.properties file. This procedure stores the user name and password in an encrypted format. Place the following two lines in a text file:
username=<administrator username> password=<administrator password>

The user name and password values must match an existing user account in the Authentication provider for the default security realm. If you save the file as boot.properties and locate it in the mydomain folder (for example: c:\bea\user_projects\domains\mydomain), the server automatically uses this file during its subsequent startup cycles. The first time you use this file to start a server, the server reads the file and then overwrites it with an encrypted version of the User Name and password. 4. Verify settings by Starting the WebLogic Server. To ensure that the edits that you made to the previous WebLogic files were accurate, start the WebLogic Server. Configuring JMS Options for the WebLogic Server: This procedure provides details on steps to configure JMS queues. If you have received the MEA Product Enabler and plan to implement the MEA, define the required Java Message Service (JMS) Options at this time. Before you begin You must be familiar with the Oracle WebLogic Server Administration Console to complete the following procedure. See your Oracle WebLogic documentation on how to navigate through the Weblogic Server Administration Console. Procedure 1. Launch Internet Explorer and open the MAXIMOSERVER Admin Console by typing the following URL: http://<host name>:7001/console. 2. Sign in by entering your User ID and password. 3. Create three persistent file stores with the following configuration parameters:
Parameter File Store Name Value sqinstore sqoutstore cqinstore

180

Installation Guide:

Parameter File Store Target File Store Directory

Value MAXIMOSERVER C:\bea92 or another directory of your choice

File stores have better performance in general. However, you can choose to create database-based stores. To choose between file stores and database-based stores, consult your WebLogic documentation. 4. Create three JMS servers with the following configuration parameters:
Parameter Properties Name Value sqinserver sqoutserver cqinserver MAXIMOSERVER 20% or below of the allotted JVM heap size

Server Target Bytes Maximum

It is recommended that you configure the Bytes Maximum for the JMS servers to a value of 20% or below of the allotted JVM heap size to prevent the Weblogic Server from running out of memory. 5. Create a JMS system module named intjmsmodule with MAXIMOSERVER as the target server. 6. Add a connection factory resource to the JMS module:
Parameter Name JNDI Name Target Value intjmsconfact jms/maximo/int/cf/intcf MAXIMOSERVER

7. Add three queue resources to the JMS Module: a. Create the queue resource type. b. Create a new subdeployment with the same name as the queue. c. Assign the <subdeployment_name>server server target to the subdeployment.
Parameter Queue 1 Queue 2 Queue 3 Template Value Name: sqin JNDI Name: jms/maximo/int/queues/sqin Name: sqout JNDI Name: jms/maximo/int/queues/sqout Name: cqin JNDI Name: jms/maximo/int/queues/cqin None

8. Enable the JMS connection factory for MEA: a. Select the intjmsconfact link. b. From the Transactions tab, check the XA Connection Factory Enabled checkbox. c. Set the Maximum Messages per Session to -1. 9. Save and activate the changes.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

181

What to do next You must now stop and restart the MAXIMOSERVER application server for the update to take effect.

Installing Maximo Asset Management and manually configuring middleware


After manual configuration of middleware you can install Maximo Asset Management. The IBM Maximo installation wizard guides you through the product installation. The program records deployment and configuration parameters that you select in each screen, and then installs and deploys the product based on this information. You can install middleware on any platform, but you must run the IBM Maximo installation program from the administrative workstation which must be installed on a supported Windows system. Values that you supply to the IBM Maximo installation program are stored in the maximo.properties file, the install.properties file, and in the Maximo database. These values are retrieved and populated into installation screen fields if you run the installation program again. If you cancel the installation program after entering values in several screens, the installation program reuses most of those values the next time you start the installation program. Values that are not reused are the installation directory and the shortcut option you chose for a previous installation. To restore the defaults for a fresh installation, delete the old maximo.properties file and the install.properties file which are stored in the MAM_HOME/maximo/ applications/maximo/properties/ directory. You must also delete the information in the MAXTEMP table in the database.

Installing Maximo Asset Management without automatic middleware configuration


You can install Maximo Asset Management without automatic middleware configuration. You might choose manual configuration of middleware if your organization has policies and procedures that restrict, for example, how you create databases, database instances, and users.

Before you begin


Ensure that all middleware servers and services are started and active. If you intend to use DB2 on a Linux or UNIX system, you must add root to a group with SYSADM authority for the database instance before starting the Maximo Asset Management installation program. If you are installing WebSphere Application Server Network Deployment, do not use the following special characters when entering passwords for users, such as wasadmin:
&, ^, <, >, ", ', ), (, |, !, $, #, %

182

Installation Guide:

If you plan to use Microsoft Active Directory to secure WebSphere Application Server Network Deployment, follow the instructions provided earlier in this chapter to configure SSL communication before you install Maximo Asset Management If you are installing using a system ID that contains Russian language characters, the installation fails with error message CTGIN2289E when attempting to install language packages. This failure will, in turn, cause a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E. To avoid this problem, install the product using a user ID with administrative authority that contains only English language characters. If you intend to perform multiple installations of the product using the same administrative workstation, review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations.. To create a maxdemo database, complete either of the following two procedures: v Enter a command to create a maxdemo database: 1. In the command line, navigate to the directory where the Maximo Asset Management files are extracted. 2. Change to the install\MAM\Install\new folder. 3. On a 32-bit Windows system, run the following command:
install.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes d

On a 64-bit Windows system, run the following command:


install_win64.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes

v When you are running the installation wizard, create a maxdemo database by performing the following tasks: 1. In the Run Configuration Step screen in the installation wizard (Step 31 in the procedure), select the Copy files now. Perform installation configuration later option. 2. When the installation finishes, exit the installation wizard. 3. Rename the ibm\smp\maximo\tools\maximo\en\maximo file. 4. Copy the ibm\smp\maximo\tools\maximo\en\maxdemo file to ibm\smp\maximo\tools\maximo\en\maximo. where en is the language folder and dbtype is ora/sqs/db2. 5. From a command prompt navigate to ibm\smp\scripts and run the following command:
taskrunner.bat CONTINUE STOPONERROR

Do not restart the computer after you copy files but before you run the taskrunner command because the taskrunner utility does not create a persistent store of information. 6. When taskrunner finishes running, rename the files back to their original names. When taskrunner successfully completes, r 7. Restart the installation program to continue with the license enablement The troubleshooting chapter describes errors that occur during theMaximo Asset Management installation.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

183

About this task


To install Maximo Asset Management, follow these steps:

Procedure
1. Log in as Administrator on the Maximo Asset Management administrative workstation. 2. Launch the Maximo Asset Management installation program from the launchpad. a. To start the Maximo Asset Management launchpad, navigate to the root directory of the product DVD or the product downloaded product installation directory and run launchpad.exe. b. In the launchpad navigation screen, click Install Maximo Asset Management. c. Click Install IBM Maximo Asset Management. Alternatively, you can launch the Maximo Asset Management installation program directly. On the product DVD or in the product downloaded product installation directory navigate to \Maximo Asset Management\, and run the appropriate command: v install.exe v install_win64.exe 3. Select a language for the installation and click OK. 4. In the Introduction panel, click Next. 5. In the Package Summary panel, review the package deployment actions, and then click Next. 6. In the software program license agreement window, read the license information and select I accept both the IBM and the non-IBM terms. if you agree with the terms, and then click Next. 7. In the Choose Install Folder panel, specify a directory to install Maximo Asset Management, and then click Next. By default, this value is C:\IBM\SMP. The path you specify must not contain spaces. 8. In the Choose Deployment panel, select the Custom deployment topology, and then click Next. Simple Select simple if you want to deploy all Maximo Asset Management 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 Maximo Asset Management components across several systems. This deployment option is typically used in a production environment. 9. In the Import Middleware Configuration Information panel, enter the following values, and then click Next. Import middleware configuration information Select this check box if you want to allow the Maximo Asset Management installation program to reuse values entered in the middleware installation program. The middleware default information is not used if you select the Simple deployment path.

184

Installation Guide:

Host name Enter the host name of the system where the middleware installation program was run. User ID Enter the user ID that was used to run the middleware installation program. Password Enter the password of the user ID that was used to run the middleware installation program. Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. This file is found in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows OS and /root/ibm/tivoli/mwi/workspace for Linux or UNIX OS. 10. In the Database Type panel, select the product that you are using for the Maximo database, and then click Next. DB2 Select this choice to use DB2 as the Maximo database.

Oracle Select this choice to use Oracle as the Maximo database. SQL Server Select this choice to use Microsoft SQL Server as the Maximo database. Each database has its own unique set of configurable parameters and values. 11. In the Database panel, enter configuration information about the database, and then click Next. DB2 Host name Enter the host name of the server 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. 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. Schema name Enter the schema name for the database. The name of the database schema is required to be the same value as the owner of the table spaces defined, for example, maximo.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

185

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 server 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. Microsoft SQL Server Host name Enter the host name of the server hosting Microsoft SQL Server. The host name must be fully qualified. Port Enter the port being used by Microsoft 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 Microsoft SQL Server. 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 Microsoft SQL Server.

186

Installation Guide:

After you have entered configuration information for the database that was selected, the Maximo Asset Management installation program connects to the database server to validate the information you have entered. 12. In the Automate Database Configuration panel, select The database has already been created and configured, and then click Next. Note that this step assumes you have already created a database instance, a database, table spaces, a user, and schema for use with Maximo Asset Management. Refer to Manually configuring the database server on page 125. If you have not manually configured the database before selecting this option from within the Maximo Asset Management installation program, the installation verifies that you have not completed these pre-installation tasks and you are reminded to complete them before restarting the Maximo Asset Management installation program. 13. In the Database Tablespace screen, enter information about the table space of the database, and then click Next. DB2 Data tablespace name Enter the name of the table space that is created in DB2 for Maximo. For all platforms, the default is MAXDATA. If the table space does not exist, it is created. Temporary tablespace name Enter the name for the temporary table space to be created for DB2. Temporary table spaces hold data during sorting or collating actions. For all platforms, the default is MAXTEMP. If the table space does not exist, it is created. Index tablespace name Enter a name for the index table space. For all platforms, the default is MAXINDEX. Oracle Data Tablespace name Enter the name of the table space to be created in Oracle for Maximo. For all platforms, the default is maxdata Temporary tablespace name Enter the name for the temporary table space to be created for Oracle. Temporary table spaces hold data during sorting or collating actions. For all platforms, the default is maxtemp Index tablespace name Enter a name for the index table space. For all platforms, the default is MAXDATA.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

187

The Maximo Asset Management installation program connects to the database server and validates the information you entered. 14. In the Application Server Type screen, select the application server that you are using for the Maximo Asset Management deployment, and then click Next. IBM WebSphere Application Server Select this option to configure WebSphere Application Server Network Deployment as the J2EE server to use with Maximo Asset Management. If you select WebSphere Application Server Network Deployment, you have the option of configuring it automatically through the Maximo Asset Management installation program. Oracle WebLogic Server Select this option to configure WebLogic Server as the J2EE server to use with Maximo Asset Management. If you select WebLogic Server, you do not have the option of configuring it automatically through the Maximo Asset Management installation program. You have to both manually configure WebLogic Server and manually deploy application files. If you select this option, the next panel you encounter is the Run Configuration Step panel. 15. Once the database validation task has completed, in the WebSphere Connectivity panel, enter host information about the WebSphere Application Server Network Deployment, and then click Next. Host name Enter the fully qualified host name of the system hosting WebSphere Application Server Network Deployment. Alternatively, you can provide the IP address for the system. SOAP port Enter the SOAP port of the WebSphere Application Server Network Deployment system. The default value for this field is 8879. 16. In the Automate WebSphere configuration panel, select Do not automate WebSphere configuration, and then click Next. Remember that in choosing not to have the Maximo Asset Management installation program automatically configure middleware, you had to configure WebSphere Application Server Network Deployment manually before the installation of Maximo Asset Management. Configuration tasks include creating a profile, running WebSphere Application Server Network Deployment as a Windows service, copying the WebSphere Application Server Network Deployment keystore file from the server where WebSphere Application Server Network Deployment is installed to the administrative workstation, setting up JMS queues, and so on. If you do choose not to automatically configure WebSphere Application Server Network Deployment, you must perform several post-installation tasks for process managers after you complete the Maximo Asset Management installation. The decision not to automate the configuration is also propagated to the process solution installation program. The post-installation process manager tasks are described later in this chapter and the process solution installation program is described in the Deployment of optional packages chapter.

188

Installation Guide:

17. In the WebSphere Deployment Manager Configuration panel, enter values for the following fields, and then click Next. WebSphere installation directory Enter the directory where WebSphere Application Server Network Deployment is installed on the host system. Windows OS On Windows, this value might be C:\Program Files\IBM\WebSphere\AppServer Linux or UNIX OS On a Linux or UNIX OS, this value might be /opt/IBM/WebSphere/AppServer or /usr/IBM/WebSphere/ AppServer User ID Enter the administrative user ID used to access the WebSphere Application Server Network Deployment. Default for all platforms is wasadmin. Password Enter the password for the administrative user ID used to access the WebSphere Application Server Network Deployment. Profile name Enter the name of the WebSphere Application Server Network Deployment profile. Default for all platforms is ctgDmgr01. 18. In the WebSphere Application Server Configuration panel, enter the following information, and then click Next. Web server port Enter the Web server port used by WebSphere Application Server Network Deployment. 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 Application Server Network Deployment node containing the application server. Default for all platforms is ctgNode01. Application server Enter the name of the WebSphere Application Server Network Deployment to associate with Maximo Asset Management. Default for all platforms is MXServer. This value can be customized. The application server is created if it does not exist. 19. In the Security panel, select a method for authenticating and authorizing users and groups, and then click Next. WebSphere application security for authentication and authorization Choose this option to automatically configure WebSphere application

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

189

security to manage users and groups for authentication and authorization purposes. This options requires application security to already be enabled in WebSphere. WebSphere application security only for authentication Choose this option to automatically configure WebSphere application security for authentication only and allow Maximo security to manage users and groups. With this option, you create all users in the directory server, but you manage membership in security groups in the base services Security Groups application. This option requires application security to already be enabled in WebSphere. If you select this option, the next panel you encounter prompts you for your user base entry. The maxadmin, maxreg, and mxintadm users and MAXIMOUSERS and MAXADMIN groups must have been created before you proceed past this panel. Maximo security for authentication and authorization If you do not want to use WebSphere application security, select this option to have Maximo security manage users and groups for both authentication and authorization. 20. In the Specify Maximo users panel, enter the following information, and then click Next. Maximo administration user Product administrator user ID used for initial configuration and adding users. Default value is maxadmin. Password Password for the Maximo administration user. Maximo system registration user User ID used for the self registration of users. Default value is maxreg. Password Password for the Maximo system registration user. Maximo system integration user User ID used with enterprise adapters. Default value is maxintadm. Password Password for the Maximo system integration user. The password values you enter in the directory server for Maximo users are not validated by the installation program. Incorrect values cause a failure during the installation process. Ensure that you have entered the correct password values for Maximo users. 21. In the Security panel, which you encounter if you chose to use WebSphere application security for authentication and authorization, specify the distinguished names of the user and group base entities you are using, choose how Maximo Asset Management users are created, and then click Next. User base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the user base entry you intend to use in this field. The default LDAP schema user base entry is ou=users,ou=SWG,o=IBM,c=US

190

Installation Guide:

Group base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management, enter the group base entry you intend to use in this field. The default LDAP schema group base entry is ou=groups,ou=SWG,o=IBM,c=US Create the required users Keep this option selected to allow the Maximo Asset Management installation program to create default users in WebSphere Application Server Network Deployment Virtual Member Manager. This operation requires write access to Virtual Member Manager. If you do not want to have the users created by the Maximo Asset Management installation program, you must create them manually before continuing the installation from this point. If you customize the schema, perform the tasks to synchronize users and groups that are described in the Post-installation tasks chapter. If you are not using the default LDAP schema provided with Maximo Asset Management, you must have created it yourself before advancing beyond this panel. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask. If you do not want the installation program to create users and groups automatically in Microsoft Active Directory, you must have already created the schema when you configured Microsoft Active Directory. 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
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

191

objectClass: top 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=maxadmin,ou=users,ou=SWG,o=IBM,c=US member: uid=mxintadm,ou=users,ou=SWG,o=IBM,c=US member: uid=maxreg,ou=users,ou=SWG,o=IBM,c=US cn: maximousers

22. In the Integration Adapter JMS Configuration panel, enter the following information, and then click Next. A JMS server requires a DB2 data repository to be configured to maintain messages. If you are using another database type, you cannot have the installation program configure message persistence. JMS Data Source name Enter the name of the data source to be used by JMS. Select whether the JMS data store should be persisted. Persist JMS messages Select this option of you want the Maximo Asset Management installation program to set the JMS implementation to persist messages within DB2. Do not persist JMS messages Select this option if you do not want the Maximo Asset Management installation program to set the JMS implementation to persist messages automatically or if you are using a database type other than DB2. If you select this option, when you click Next, the installation wizard skips to step 26, where you configure SMTP. Select this option if you are deploying Maximo Asset Management with Oracle or Microsoft SQL Server. 23. If you chose to persist JMS messages, in the DB2 Database Server Configuration panel, enter the following information, and then click Next. If you chose not to persist JMS messages, the wizard skips to step 26, and you do not see this screen. Note: The JMS data store can only be created as a DB2 database. Host name Enter the fully qualified host name of the server hosting the JMS data store. 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 data store. 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.

192

Installation Guide:

24. If you chose to persist JMS messages, in the WebSphere Application Server Network Deployment keystore file panel, navigate to where you copied the trust.p12 keystore, and then click Next. If you chose not to persist JMS messages, the wizard skips to step 26, and you do not see this screen. 25. In the SMTP Configuration panel, specify SMTP information for use by workflows to communicate with workflow participants, and then click Next. SMTP server Enter the fully qualified host name of the SMTP server used for sending messages to participants. Administrator e-mail Enter a valid e-mail address. This address is used to send messages. If you do not enter any information at this point, you can configure these parameters later. For instructions, see the Configuring SMTP topic in the Post-installation tasks chapter. 26. From the Run Configuration Step panel, decide how you would like to perform the configuration step of the installation, and then click Next. a. Choose when you would like to run the configuration step: Perform installation configuration now Select this option to have the installation program perform the configuration step during installation. Copy files now. Perform installation configuration later. Select this option to have the installation program copy files to the system only. The Maximo Asset Management installation program is used to complete three tasks: gathering information about your Maximo Asset Management deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting this option, you can instruct the Maximo Asset Management installation program to gather your configuration information and copy Maximo Asset Management 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 run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility, located in the <MAM_HOME>\scripts directory. Run the taskrunner utility from the command line, and it uses the configuration values stored in the maximo.properties file to configure Maximo Asset Management.
<MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR>

Note: If you reboot the system, you are not able to use the taskrunner utility to run configuration scripts. Taskrunner data stores are not persisted. If you intend to use the taskrunner utility, do not reboot your system. If the installation fails, the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. The taskrunner utility resumes the installation at the point where the last successfully completed task
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

193

was recorded in the previous attempt. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. b. Choose how to deploy application files. If you chose to deploy Maximo Asset Management with WebLogic Server, these options are not available from this panel. Deploy application files automatically Select this option to have the installation program perform EAR file deployment automatically during the installation. Deploy application files manually later Select this option to defer the deployment of application files. Deferring the deployment of application files can shorten the time it takes to deploy overall if you intend to install more than one service management product. Files can be deployed once all products have added their own functions to the application files. You might also want to use this option if your organization has application deployment restrictions that require that you deploy application files either manually or through another approved process. See the Deployment of Maximo Asset Management with manual configuration of middleware for instructions. 27. In the Choose Shortcut Folder panel, select the type of shortcut you would like to arrange for Maximo Asset Management, and then click Next. Note: Shortcuts are created for Windows systems only. Note: Because deployment on WebLogic Server systems is a manual process, you are required to manually update any shortcuts you create for WebLogic Server deployments after you have manually deployed the Maximo Asset Management EAR files. In a new Program Group Select this option and enter the name of a new program group if you would like to create Maximo Asset Management 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 Maximo Asset Management shortcuts. In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. In order to use the Start menu shortcut with Internet Explorer, ensure that you have added the Maximo Asset Management 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 Maximo Asset Management on the desktop. In the Quick Launch Bar This option must not be used. Do not select this option. Selecting this option does not create a shortcut in the Quick Launch bar.

194

Installation Guide:

Other Select this option and use the Choose... button to select another location to create Maximo Asset Management shortcuts. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. Create Icons for All Users Select this option if you would like Maximo Asset Management desktop icons to appear on the desktop for all system users. 28. In the Input Summary panel, review the information you have provided to the Maximo Asset Management installation program, and then click Next. Use the Previous button to return to previous panels to change values. 29. In the Pre-Installation Summary panel, review the installation information presented, and then click Install. The installation task begins. Progress can be monitored by viewing messages displayed above the progress bar. 30. In the Install Complete panel, click Done.

What to do next
Once the Maximo Asset Management installation program has completed installation and configuration tasks, it exits.

Completing post-installation tasks


To complete the deployment, you must perform several additional tasks after the installation. If you intend to support multiple languages in Maximo Asset Management, install the language pack before performing other configuration tasks. See the Deployment of optional packages chapter for language pack installation instructions. The chapter also describes how to install process solution packages, including process manager products and integration modules. The Post-installation configuration chapter describes the configuration tasks to complete within the product user interface.

Post product installation process manager tasks


If you have chosen WebLogic Server as your J2EE server, or you have chosen to not automate the configuration of your WebSphere Application Server Network Deployment server during the Maximo Asset Management installation process, there are several post-installation tasks that must be performed for product PSI packages. PSI packages contain bundles of process solution components that comprise the features and functions of each ISM product and are managed by the process solution installer. Ensure that you have run the configuration step portion of the Maximo Asset Management installation either by performing it during installation, or outside the Maximo Asset Management installation program by using the taskrunner utility. The product installation program invokes the process solution installer and deploys product PSI packages. If you have chosen WebLogic Server as your J2EE server, or you have chosen to not automate the configuration of your WebSphere Application Server Network Deployment server, certain package tasks will not be performed and must be completed manually.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

195

Post product installation PSI package tasks include the following steps: 1. Manually configuring PSI packages 2. Deploying the confhelp.properties file on page 81 The following table contains a summary of manual post-installation tasks that are required when J2EE configuration cannot be automated:
Table 16. Post-installation PSI package tasks
Create groups within LDAP (if using application server security) base services Package base_services_7.1.1.5.zip IBM Tivoli Maximo Common PMP common_pmp_7..1.1.5.zip PMREQUESTER Add user maxadmin to group Note: This group can be created through PMREQUESTER VMM if you are using WebSphere Application Server Network Deployment. Add users to a group within LDAP (if using application server security) Deploy WAR files to ISC (WebSphere Application Server Network Deployment only) isccommontasks.war

Manually configuring PSI packages


A process solution package, or PSI package, is a self-contained archive file of installation artifacts and deployment logic that can be deployed using the process solution installation program. Some of the PSI packages must be configured manually if you have chosen WebLogic Server as your J2EE server, or you have chosen to not automate the configuration of your WebSphere Application Server Network Deployment server during the Maximo Asset Management installation process.

About this task


To manually configure PSI packages for Maximo Asset Management, complete the following steps:

Procedure
Configure the common_pmp_7.1.1.5.zip package: 1. If using application server security, create a new group called PMREQUESTER in your LDAP repository. If using WebSphere Application Server Network Deployment for application server security, use the createVMMGroup script to create the PMREQUESTER group. Use the following syntax with the createVMMGroup script:
<MAM_HOME>\jacl\solutions\createVMMGroup.bat <WASAdminUserID> <WASAdminPassword> <VMMGroupName>

So, for example,


<MAM_HOME>\jacl\solutions\createVMMGroup.bat wasadmin wasadminpwd PMREQUESTER

2. If using application server security, add the user maxadmin to the PMREQUESTER group you created. If using WebSphere Application Server Network Deployment for application server security, use the addMemberToVMMGroup script to add the user maxadmin to the PMREQUESTER group. Use the following syntax with the addMemberToVMMGroup script:

196

Installation Guide:

<MAM_HOME>\jacl\solutions\addMemberToVMMGroup.bat <WASAdminUserID> <WASAdminPassword> "uid=maxadmin,ou=users,ou=SWG,o=IBM,c=US" "cn=PMREQUESTER,ou=groups,ou=SWG,o=IBM,c=US"

WebSphere-specific tasks: About this task Complete these additional PSI package configuration tasks if you are using WebSphere Application Server Network Deployment for application server security. Procedure Configure the base_services_7.1.1.5.zip package: 1. Extract the isccommontasks.war file located in the FILES directory of the <MAM_HOME>\pmp\base_services_7.1.1.5.zip file to <MAM_HOME>\temp. 2. Deploy the file.
<MAM_HOME>\jacl\solutions\ISCHandler.bat "<Remote System>" "<Remote Execution and Access User>" "<Remote Execution and Access Password>" "<MAM_HOME>\temp\files\isccommontasks.war" "<Remote WAS Home>" "<WASAdminUserID>" "<WASAdminPassword>" "isccommontasks.war" "isccommontasks"

So, for example,


<MAM_HOME>\jacl\solutions\ISCHandler.bat "myremotemachine.mydomain.com" "remoteuser" "remoteuserpassword" "<MAM_HOME>\temp\files\isccommontasks.war" "/opt/IBM/WebSphere/AppServer" "wasadmin" "wasadminpwd" "isccommontasks.war" "isccommontasks"

Deploying the confhelp.properties file


The confhelp.properties file must be deployed to enable the help system for the product.

Before you begin About this task


To deploy the confhelp.properties file, complete the following steps:

Procedure
1. Ensure you are logged into the administrative workstation. 2. Run the following command:
<MAM_HOME>\jacl\solutions\Sendfile.bat <WASDeploymentManagerHostName> <WASRemoteAccessUserName>
Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

197

<WASRemoteAccesspassword> "<MaximoInstallLocation>\applications\maximohelp \helpweb\webmodule\WEB-INF\confhelp.properties" "<WASInstallLocation>\properties" "confhelp.properties"

Verifying the installation


After you have exited the Maximo Asset Management installation program without encountering any errors, you can further verify that the installation completed successfully by locating key artifacts and performing a few simple tasks.

Before you begin


The product installation program performs installation verification, or a health check, by logging into the product before exiting the installation. The product installation program returns a success message if all installation steps, including the product log in task, are successful. If the health check task is unsuccessful, a HealthCheckFailed error thrown for the getUrlContentString function will be found in the <MAM_HOME>\logs\CTGInstallTraceXX.log file, where XX is a two digit number such as 00. For more information about log files and troubleshooting errors encountered during the installation, refer to Troubleshooting the product installation program on page 239.

About this task


To further verify that the Maximo Asset Management installation was completed successfully, perform the following verification procedures:

Procedure
1. Examine the CTGInstallTrace00.log file for success messages. The following success messages are found in the CTGInstallTrace00.log file and can be used to verify which phases of the installation were successful: v CTGIN2114I: The database was created successfully v CTGIN2135I: Tablespace maxdata created successfully v CTGIN2135I: Tablespace maxtemp created successfully v CTGIN2079I: Base services database configuration completed successfully (This message indicates that maxinst finished successfully.) v CTGIN2222I: WebSphere Application Server creation successful v CTGIN2188I: Creation and configuration of service integration bus successfully completed v CTGIN2184I: Creation and configuration of JMS resources successfully completed v CTGIN2310I: Application server security was successfully enabled for the base services v CTGIN2253I: buildmaximoear.cmd completed successfully v v v v v CTGIN2224I: CTGIN2253I: CTGIN2224I: CTGIN2208I: CTGIN2370I: Deployment of application MAXIMO was successful buildhelpear.cmd completed successfully Deployment of application MAXIMOHELP was successful runConfigurationStep completed successfully The installation finished successfully

198

Installation Guide:

If you chose the option of having the installation program automatically configure WebSphere Application Server Network Deployment, the following messages, found in the CTGInstallTrace00.log file, indicate the configuration was successful:
<symptom>CTGIN2228I.*client</symptom> <symptom>CTGIN2230I.*node</symptom> <symptom>CTGIN2232I.*NodeAgent</symptom> <symptom>CTGIN2240I.*server</symptom> <symptom>CTGIN2238I.*security</symptom>

Search the CTGInstallTrace00.log file for the following message, which indicates that the maxinst task completed successfully:
CTGIN2079I, maxinst.*completed

2. Compare the packages chosen for installation with the packages that were installed. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages that will be installed. You can compare the contents of that panel with a listing of what was actually installed on the system. Use the solutioninstaller command to list installed packages:
<MAM_HOME>\bin\setupPSIenv.bat <MAM_HOME>\bin\solutionInstaller.bat -action showInstalled -all

The resulting list should match the packages listed in the Package Summary panel. 3. Log into the product and verify applications are present. Being able to log into the product manually is a good indicator that the installation was successful. Once you have logged in, navigate through the GoTo menu to verify that it has been populated with the applications you expect.

Chapter 6. Deployment of Maximo Asset Management with manual configuration of middleware

199

200

Installation Guide:

Chapter 7. Deployment of optional packages


After you install Maximo Asset Management before you perform initial configuration tasks, add language support and process solutions as required. The product DVD or installation images include optional language procuess solution packages. Complete these installations before you configure the system;.

Optional deployment of Maximo Asset Management language packages


You can install optional language packages to provide support for additional languages, other than English, for Maximo Asset Management users. If you want to support additional languages, install language packages before you complete the post installation configuration tasks. After you have successfully installed Maximo Asset Management, you can add support for languages, other than English, to the Maximo Asset Management user interface The Maximo Asset Management server, typically called MXServer on WebSphere Application Server and MAXIMOSERVER on WebLogic Server, must be started before you install additional languages. Important: If you plan to add additional languages Maximo Asset Management, use the Maximo Asset Management language pack installation program before you perform the tasks described in the Post installation configruation tasks chapter.

Installing the language pack


This procedure provides task information for installing support for languages, other than the base language, in the Maximo Asset Management user interface.

Before you begin


When you run the language pack installation program, you have an opportunity to select your base language. The base language is the language that is displayed as the default for the text that is displayed in the Maximo Asset Management user interface. Currently, the default base language is English. You can use the language pack installation program to change the base language to something other than English, and you can also specify additional languages to install, so Maximo Asset Management users can browse the user interface and see information in a language that is appropriate for their own locale. For example, you might specify English as the base language, and install Brazilian Portuguese, Spanish, and French as additional languages. Users in Brazil, Spain, and France can have text in the Maximo Asset Management interface displayed in their own languages, and not in English. Turkish language is not supported. It can take several hours to install additional languages. To minimize installation time, select only the languages that you have a need for at this time.
Copyright IBM Corp. 2007 - 2010

201

Do not add your base language to the list of additional languages to install .

About this task


To use the Maximo Asset Management language pack installation program to install the Maximo Asset Management language pack, complete the following steps: 1. Ensure that all Maximo Asset Management middleware servers and services are running. If you encounter a failure resulting from an inactive Maximo Asset Management middleware server or service, start that server or service, and then rerun the language pack installation program. The language pack installation program first uninstalls 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 Maximo Asset Management administrative system. 3. On the launchpad, click the Maximo Asset Management Language Pack installer link under 3. Install Additional Languages. 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 Introduction panel, click Next. 6. From the Base language Selection panel, select a base language that is to be used for Maximo Asset Management, and then click Next. This is the only opportunity you can select a base language. You cannot change the base language at a later time. 7. From the Additional language selection panel, select 0 or more additional languages to be supported, and then click Next. Do not specify the base language as an additional language; doing so is redundant and simply increases the time needed to install the additional languages. 8. From the language selection summary panel, review the information and then click Next. 9. From the summary panels and click Install. Even if you added additional languages through the language pack installation program, and you set the locale of your machine to a language that was installed as an additional language, you might still encounter instances in the Maximo Asset Management user interface 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 Maximo Asset Management language pack installation failed. In some cases, shortcut elements appearing in the Maximo Asset Management interface, for example, menu choices, only display in the base language that you select.

202

Installation Guide:

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 Maximo Asset Management 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 Maximo Asset Management 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. Ensure the application server (MAXIMOSERVER) is stopped Stop the application server if it is running. Wait 12 minutes before starting the process solution installation program. If the application server is not stopped, the process solution installation stops and issues a message prompting you to stop the application server.
Chapter 7. Deployment of optional packages

203

Installing process managers using the process solution installation wizard


About this task
Complete the following steps to install a process solution package into Maximo Asset Management using the process solution installation wizard: 1. Launch the process solution installation program by navigating to the <MAM_HOME>\bin directory of your Maximo Asset Management installation, and executing solutionInstallerGUI.bat. The Process Solution Installation Install Anywhere Installer executes on the Maximo administrative workstation. The launch script is deployed and configured by the Maximo Asset Management installation program. No post-installation configuration is required. 2. Select a language for your installation, and then click OK. 3. In this case, the PSI package selected is a base install of the Maximo Asset Management 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. 4. From the Package Validation Results panel, review and verify the information displayed, and then click Next. 5. 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. 6. 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. 7. 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. 8. From the Pre-Install Summary panel, review and verify the information displayed, and then click Next. The process solution installation program begins the package installation process. A progress panel informs you of the deployment progress of the installation. 9. 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.

204

Installation Guide:

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 17. Process solution installation logs Log type Package log Description Location

These are log files containing <MAM_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.

Solution Install/Deployment Engine Logs

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.

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

Chapter 7. Deployment of optional packages

205

Table 17. Process solution installation logs (continued) Log type Maximo Asset Management Logs Description There are also a few logs kept by Maximo Asset Management. These are useful in tracking the progress, success, and failure of a few back-end commands provided by Maximo Asset Management. Location <MAM_HOME>\maximo\ tools\maximo\log\ updatedb<TIMESTAMP>.log So if your Maximo Asset Management 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

Table 18. WebSphere Application Server Network Deployment logs Log type WebSphere Application Server Network Deployment Logs Description These are logs kept of connections, exceptions, and other failures experienced by the WebSphere Application Server Network Deployment 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. Location <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 Network Deployment 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

206

Installation Guide:

Table 18. WebSphere Application Server Network Deployment logs (continued) Log type WebSphere Application Server Network Deployment Thin Client Logs Description The WebSphere Application Server Network Deployment thin client is the mechanism by which the process manager packages communicate with the WebSphere Application Server Network Deployment. If this automated deployment happens to fail, the exact actions the Thin Client took and the associated responses from the WebSphere Application Server Network Deployment are stored in logs. Location <MAM_HOME>\wasclient\ logs\ CTGIN_wsadmin.traceout <MAM_HOME>\wasclient\ logs\wsadmin.traceout <MAM_HOME>\wasclient\ logs\wsadmin.valout So if your Maximo Asset Management install location were "C:\IBM\SMP", the following log files would contain the WebSphere Application Server Network Deployment Thin 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

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. Deployment of optional packages

207

208

Installation Guide:

Chapter 8. Post-installation configuration


After you complete the Maximo Asset Management installation, you must perform some initial application configuration. This section also provides information about configuring the WebSphere server.

Post installation steps


After you have installed the product, additional steps are necessary to prepare it for use. If you want to add support for additional languages, you must perform the language pack installation before you perform the post-installation tasks. See Optional deployment of Maximo Asset Management language packages on page 201 for more information about the language pack installation. The post installation steps can include the following tasks. Some of these tasks, such as configuring SMTP, may have already been performed for you when the product was installed. v Signing in using a default user ID v Configuring SMTP to notify someone of system events v Creating currency codes v Creating company and item sets v v v v v v v v v Creating an organization Creating a general ledger account component Applying configuration changes to the database Creating a general ledger account Updating general ledger component type authorization Updating of any company-related accounts Creating a default insert site Creating a work type Signing out and signing in, if you have changed security groups

Initial data configuration


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

Signing in using a default user ID


The default user ID that was created when the product was installed can be used to log on to the application to verify that it is operational. You can create additional IDs and roles, as your business needs dictate. If you specified a different name for the default user ID, use that account name to log on to the application.

Before you begin


The installation program provides a default user ID (maxadmin) but it does not supply a default password. You need both a valid user name and password to log
Copyright IBM Corp. 2007 - 2010

209

on. User names and passwords are context-sensitive.

Procedure
1. Open a browser session to the IBM Maximo web service interface. You need the hostname or IP address, and the port number of the application. The default port number is 9081. For example: http://my_server_example.com:9081 2. Specify the default user name. 3. Specify the default password. 4. Click Sign In.

Configuring SMTP
Installation panels provide an opportunity to configure an SMTP server to send an administrator, or other users, e-mail notifications of system events. If you skip these panels when you install Maximo Asset Management, you can use the Maximo Asset Management interface to configure SMTP parameters.

Before you begin


This task must be completed before you begin the tasks described in Applying changes to the database on page 212.

About this task


To configure SMTP for Maximo Asset Management, complete the following steps.

Procedure
1. log in to the console as maxadmin. 2. Navigate to Go To System Configuration Platform Configuration System Properties 3. Using the Filter feature, search for the mail.smtp.host Property Name. 4. Expand the mail.smtp.host property and set the Global Value attribute to your SMTP host. 5. Select the mail.smtp.host record check box. 6. Click the Live Refresh icon in the toolbar. 7. From the Live Refresh dialog, click OK. 8. Using the Filter feature, search for the mxe.adminEmail Property Name. 9. Expand the mxe.adminEmail property and set the Global Value attribute to your e-mail address. 10. Select the mxe.adminEmail record check box. 11. Click the Live Refresh icon in the toolbar. 12. From the Live Refresh dialog, click OK.

Creating currency codes


A currency code must be defined for each organization.

About this task


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.

210

Installation Guide:

3. Enter a currency name, for example, USD. 4. Click Save.

Create item and company sets


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

8. Click Save.

Create an organization
About this task
You must define at least one organization for Maximo Asset Management. 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 Sites tab. 9. Click New Row. 10. Enter a site name in the Site field. For example, B901. 11. Click Save.

Creating a general ledger account component


You must create a general ledger account component for Maximo Asset Management.

About this task


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
Chapter 8. Post-installation configuration

211

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.

Applying changes to the database


When you create a general ledger account component, it must be applied to the Maximo database.

About this task


To apply configuration changes to the Maximo database, complete the following steps.

Procedure
1. Log in to the Maximo console as maxadmin 2. Navigate to Go To System Configuration Platform Configuration Database Configuration. Every object that must be updated in the Maximo database has a status of To Be Added. 3. On the Select Action drop-down list, select Manage Admin Mode. 4. Click Turn Admin Mode ON, and then click OK when prompted. This task takes several minutes to complete. You can use the Refresh Status button to view progress. 5. Once Admin Mode has been successfully enabled, select Apply Configuration Changes, to apply the changes to the Maximo database. To Be Changed should not appear in the status column for objects listed. 6. Turn Admin Mode OFF. a. Navigate to Go To System Configuration Platform Configuration Database Configuration. b. From the Select Action drop-down list, select Manage Admin Mode. c. Click Turn Admin Mode OFF, and then click OK when prompted. Failing to turn off Admin Mode within the application causes cron tasks to fail.

Create a general ledger account


About this task
You must create a general ledger account for Maximo Asset Management. 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 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.

212

Installation Guide:

7. Select your General Ledger Account. 8. Click Save. 9. Open the Organizations application by selecting Goto > Administration > Organizations 10. Click the organization name you created. For example, ENGLENA. 11. From the Clearing Account field, select the General Ledger Account you just created. 12. Select Active. 13. Click Save.

Update General Ledger Component Type Authorization


About this task
You must update the general ledger component type authorization for Maximo Asset Management. To authorize a Security Group to change a general ledge component type, complete the following steps:

Procedure
1. Open the Security Groups application by selecting Go To Security Security Groups. 2. Select the Group that will be provided authorization (for example, SCHEDULING). 3. Click the GL Components tab. 4. Click the Authorized checkbox for each GL Component. 5. Click Save

Update Company-Related Accounts


About this task
You must update the company related accounts for Maximo Asset Management. To update the company related accounts, complete the following steps:

Procedure
1. Open the Chart of Accounts application by selecting Go To Financials Chart of Accounts. 2. From the action dropdown box, select Company-Related Accounts. 3. On the dialog click New Row. 4. Select company type 'C'. 5. Set the RBNI Account, AP Suspense Account and AP Control Account to the components you created. 6. Click OK. 7. From the action dropdown box, select Update Database. 8. Click OK.

Chapter 8. Post-installation configuration

213

Create default insert site


About this task
You must create a default insert site for Maximo Asset Management. 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. 3. Enter the site you created earlier in the Default Insert Site field. For example, B901. 4. Enter the site you created earlier in the Storeroom Site for Self Service Requisitions field. For example, B901. 5. Click Save. 6. Open the WebSphereWebLogic Server Admin Console and restart the MXServerMAXIMOSERVER application server. If you encounter 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


About this task
You must create a Work Type for Maximo Asset Management. 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 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. 8. 9. 10. 11. 12. 13. Set the Work Type as AR. Set Start Status as INPRG. 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.

14. Set Complete Status as COMP. 15. Click OK. 16. Click Save.

214

Installation Guide:

Signing out and signing in


About this task
When you change a security group that your user ID is a member of, 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.

What to do next

Configure directory server for Microsoft Active Directory


You can manually configure users and groups on a directory server to synchroinze with users and groups on the Maximo Asset Management server. To synchronize users and groups between a directory server and Maximo Asset Management, follow the instructions for the application server in your system.

Manually configuring directory services for WebSphere Application Server Network Deployment
You can manually configure a Maximo Asset Management cron task to schedule synchronization of users and groups between a directory server and the sMaximo ystem.

About this task


VMMSYNC is the cron task that schedules the synchronization between Maximo Asset Management and the WebSphere Application Server Network Deployment directory server. This cron task is set up automatically during installation. The manual procedure is required only if you need to change the existing configuration of the cron task. To configure the synchronization schedule between the directonry server and Maximo Asset Management, complete the following steps:

Procedure
1. Open a Web browser and point to http://host name/maximo. 2. Log in to Maximo Asset Management using the maxadmin user ID. 3. From the Maximo Asset Management interface, navigate to Go To System Configuration Platform Configuration Cron Task Setup. 4. Type VMM in the Cron Task field, and press Enter. 5. Locate the VMMSYNC cron task, and click it. 6. Configure the following values: Active? Enable the Active? option by selecting the check box. Credential This should be the password used for the Principal account. In this case, enter the password for wasadmin. GroupMapping This field contains XML mapping files that map LDAP object attributes
Chapter 8. Post-installation configuration

215

to database repository table columns. Change the following object entries to use the organizational unit ou value you defined for your organization when setting up Maximo Asset Management middleware. Basedn This defines the LDAP sub-tree under which the Virtual Member Manager Crontask will search for group objects. For example, ou=groups,ou=SWG,o=IBM,c=US. Filter This is the Virtual Member Manager object class that the service uses to search for group objects in LDAP.
Group

GroupSearchAttribute This value is the LDAP group object attribute used to search for groups under the configured directory sub-tree. For example, cn. Principal This is the user required by the CronTask application to connect to the local Virtual Member Manager service. This value can be any directory server administrative user that has authorization to connect to the local Virtual Member Manager service. Customize it to use the organizational unit ou and domain name dc values you defined for your organization when setting up Maximo Asset Management middleware. For example, cn=wasadmin,ou=users,ou=SWG,o=IBM,c=US . SynchAdapter psdi.security.vmm.DefaultVMMSyncAdapter This value is the Java class that writes LDAP data to the database. SynchClass psdi.security.vmm.VMMSynchronizer This value is the Java class that connects to the Virtual Member Manager local service to search for required objects. UserMapping This field contains XML mapping files that map LDAP object attributes to database repository table columns. Change the following object entries to use the organizational unit ou value you defined for your organization when setting up Maximo Asset Management middleware. Basedn This defines the LDAP sub-tree under which the Virtual Member Manager Crontask will search for user objects. For example, ou=users,ou=SWG,o=IBM,c=US. Filter PersonAccount This is the Virtual Member Manager object class that the service uses to search for user objects in LDAP. UserSearchAttribute This value is the LDAP user object attribute used to search for users under configured directory sub-tree. For example, cn.

216

Installation Guide:

You must click the arrow located in the header of the Cron Task Parameters table to view all parameters. 7. Click the save icon.

Results
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. The updated parameters are used at the next scheduled synchronization.

Manually configuring directory services for Oracle WebLogic Server


When you use Oracle WebLogic Server as the application server, a cron task synchronizes users and groups between an LDAP directory server and the Maximo Asset Management server. The LDAPSYNC cron task runs at scheduled intervals to ensure that user and group data that is created and maintained on the directory server is added to the user and group information for Maximo Asset Management.

About this task


See the information about application server security in the IBM Maximo Asset Management System Administrator Guide to configure and use the LDAPSYNC cron task.

Updating the port for the information center


Some of the documentation for Maximo Asset Management is provided in an Eclipse-based information center.

Before you begin


The links from the product user interface to the information center specify the port used by the IBM Eclipse Help System on the deployment manager server. This port is the port that you specified for the WebSphere Application Server Network Deployment Administrative Console when you installed WebSphere Application Server Network Deployment. If you did not choose the default value, 9060, you must supply the correct port number so that the links to the information center will connect properly.

Procedure
1. Locate the confhelp.properties file on your J2EE server. It should be in the properties directory of the WebSphere Application Server installation. For example, on a Windows workstation, it might be in C:\Program Files\IBM\WebSphere\AppServer\properties. 2. Edit the file, update the port number, and save the file. 3. If you have Maximo Asset Management installed on several J2EE servers, for example in a clustered environment, you must copy the updated file to each J2EE server you add to the cluster.

Maximo Asset Management Security


You must configure security to ensure that only authorized users can log in to Maximo Asset Management and to ensure that the appropriate users have access to the applications and configuration items that they need to work with.

Chapter 8. Post-installation configuration

217

The Security section of the Maximo Asset Management information center provides an overview of the following information: v How security is implemented. v The steps you perform configure security.

Tuning DB2
This section details how to tune DB2 after you have completed installation.

About this task


Maximo Asset Management provides scripts that can be used to tune DB2. The use of these scripts is strictly optional and contain configuation parameters that might not be ideal for all environments. However, you can modify these scripts to suit your particular configuration and workload. Before modifying these scripts, you should make a backup copy of the original script. The following database configuration parameters will be set: v DFT_QUERYOPT 2 v LOCKLIST 15000 DEFERRED v MAXLOCKS 60 v v v v v v v v v v v PCKCACHESZ 12600 DBHEAP 2000 CATALOGCACHE_SZ 800 LOGBUFSZ 256 UTIL_HEAP_SZ 10000 APP_CTL_HEAP_SZ 16384 DEFERRED APPLHEAPSZ 2048 STAT_HEAP_SZ 8196 CHNGPGS_THRESH 40 MAXFILOP 200 LOGFILSIZ 2048 DEFERRED

v STMTHEAP 16384

v LOGPRIMARY 10 v LOGSECOND 15 DEFERRED The following database manager configuration parametes will also be set: v PRIV_MEM_THRESH 32767 v NUMDB 2 The DB2 tuning scripts are found in the <MAM_HOME>/scripts/database directory, and must be run by a user with database administration authority. Windows db2tuning.cmd [ dbName [ dbInstance ] ] Linux and UNIX OS db2tuning.sh [ dbName [ dbInstance ] ] If the dbName is not provided, it will default to MAXDB71.

218

Installation Guide:

If the dbInstance is not provided it will default to ctginst1. If a database instance other than the default is needed, the dbName must also be provided.

WebSphere configuration
This section describes how to configure WebSphere to work with Maximo Asset Management. For detailed information about using WebSphere, consult the product information at ???

WebSphere Application Server configuration


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


About this task
An application server named MXServer was created during installation. To start the MXServer application , complete the following steps: 1. Start the Deployment Manager: Linux, HP-UX, Solaris, AIX
<WAS_HOME>/AppServer/profiles/ctgDmgr01/bin/startManager.sh

Windows a. Click Start, and select Run. b. Type services.msc, and click OK. c. Select IBMWAS61Service - ctgCellManager01, and click Start the service. Alternatively, you can use the following command from the command line to start the domain manager:
<WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat

2. Start the Node: Linux, HP-UX, Solaris, AIX


<WAS_HOME>r/profiles/ctgAppSrv01/bin/startNode.sh

Windows
<WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat

3. Start the web server: Linux, HP-UX, Solaris, AIX Windows 4. Start the App Server : Linux, HP-UX, Solaris, AIX Windows

<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh webserver1 -username <username> -pas

<WAS_HOME>profiles\ctgAppSrv01\bin\startServer.bat webserver1 -username <username> -pas

<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer -username <username> -passw

<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.bat MXServer -username <username> -pass

Chapter 8. Post-installation configuration

219

Alternatively you can start MXServer from the WebSphere Application Server administrative console: 1. To start the administrative console, open a browser window and enter the following URL:
http://<machine_name>:9060/ibm/console

2. 3. 4. 5. 6.

Where <machine_name> is the host name of the WebSphere Application Server and 9060 is the default port number for the Administrative Console. Enter an administrative user ID and password to login, if one is required. From the administrative console navigation pane, click Servers Application Servers. Select the check box next to MXServer, the name of the WebSphere Application Server. Click Start. Notice that the icon in the Status column changes to running 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 19. Server processes Server HTTP Server Go To Windows <HTTP_SERVER_HOME>\bin\apache -k start <HTTP_SERVER_HOME>\bin\apache -k stop Linux, HP-UX, Solaris, AIX <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 Linux, HP-UX, Solaris, AIX <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 Linux, HP-UX, Solaris, AIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh <WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode.sh

220

Installation Guide:

Table 19. Server processes (continued) Server ITDS Instance Go To 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. Linux, HP-UX, Solaris, AIX /ldap/V6.1/sbin/ibmslapd -I idsccmdb

Directory Server Database

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. Linux, HP-UX, Solaris, AIX su - idsccmdb -c db2start

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 the WebSphere Application Server administrator user ID and password to login.

Securing the WebSphere Application Server Network Deployment Administrative Console through VMM
About this task
You can secure the WebSphere Application Server Network Deployment Administrative Console through VMM so that only authenticated users can use it. VMM must have been configured on the WebSphere Application Server Network Deployment server before securing the console. Once you have enabled VMM for WebSphere Application Server Network Deployment 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

Chapter 8. Post-installation configuration

221

Security Secure administration, applications, and infrastructure Administrative Group Roles to view the available administrative group roles.
Table 20. Administrative group roles 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. 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.

What to do next

Configuring the WebSphere Application Server to run Windows services


About this task
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

222

Installation Guide:

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:\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:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01

wasHome Home folder for MXServer, for example,


C:\IBM\WebSphere\AppServer

logRoot Folder location of MXServer log file, for example,


C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\ logs\MXServer

logFile Log file name for MXServer, for example,


C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs \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:
WASService -add MXServer -serverName MXServer -profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01" -wasHome "C:\IBM\WebSphere\AppServer" -logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer" -logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer\ 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.

Chapter 8. Post-installation configuration

223

Configuring the WebSphere node agent to run Windows services


About this task
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:\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:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01

wasHome Home folder for MXServer, for example,


C:\IBM\WebSphere\AppServer

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


C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent

logFile Log file name for node agent


C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\ 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:
WASService -add NodeAgent -serverName nodeagent -profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01" -wasHome "C:\IBM\WebSphere\AppServer" -logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent" -logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\ startServer.log" -restart true

10. Press <Enter> after you type the WASService command, and you will see a confirmation message.

224

Installation Guide:

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.

Chapter 8. Post-installation configuration

225

226

Installation Guide:

Chapter 9. Troubleshooting
If you encounter issues using the product or middleware installation programs, review the troubleshooting information for answers to common problems.

Troubleshooting the middleware installer


Use the information contained in this section to troubleshoot errors encountered when using the middleware installer. This section contains both general troubleshooting advice and solutions to specific errors encountered when using the middleware installer.

Encountering error CTGIN9042E


During middleware installation using the middleware installer, you might encounter error CTGIN9042E which occurs during the install step for WebSphere Application Server Network Deployment 6.1.

Before you begin


Maximo Asset Management

About this task


If you encounter error CTGIN9042E through the normal use of the middleware installation program, it might be related to stale entries in the CEI registry. In order to troubleshoot this error, complete the following steps:

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

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

2. Next, check for any stale WebSphere Application Server Network Deployment entries: a. Extract the native image of WebSphere Application Server Network Deployment: Windows WAS-ND_WindowsIA32_Custom_v61023 Linux WAS-ND_LinuxIA32_Custom_v61023.tar.gz AIX
Copyright IBM Corp. 2007 - 2010

WAS-ND_AIXppc64_Custom_v61023.tar.gz

227

b. Open the console window. c. Navigate to the bin folder of extracted image. For example:
\WAS\installRegistryUtils\bin

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

b. Edit the vpd.properties file, remove any WebSphere Application Server Network Deployment entries, and then save the file. The file is located in the installation directory of the operating system: Windows C:\WINNT directory or C:\windows directory UNIX /usr/lib/objrepos/ 4. After cleaning the registry, run the middleware installation program again and Restart the plan. WebSphere Application Server Network Deployment will now be successfully installed in the default location, for example, C:\Program Files\IBM\WebSphere\AppServer for Windows.

Encountering error ACUINI0044E


During middleware installation using the middleware installer, you might encounter error ACUINI0044E which occurs during the install step for the deployment engine.

Before you begin About this task


If you encounter error ACUINI0044E through the normal use of the middleware installation program, it might be related to a failure of the deployment engine to be installed or started. The following messages will be displayed after a failure to deploy the deployment engine is encountered:
Deployment Engine did not start successfully. Please try to manually start the Deployment Engine and restart the installer. ACUINI0044E Failed to register and start Deployment Engine IBM ADE Service

In order to troubleshoot this error, complete the following steps:

228

Installation Guide:

Procedure
1. Exit the middleware installation program. 2. Restart the deployment engine using the following commands: Windows
net start "IBM ADE Service"

Linux
/usr/ibm/common/acsi/bin/acsisrv.sh -start

AIX
/usr/ibm/common/acsi/bin/acsisrv.sh -start

If the deployment engine is started successfully, restart the middleware installation program and resume middleware deployment. If the deployment engine fails to start, you will have to manually uninstall the deployment engine as described in Common deployment failures on page 243. Note that this will also eliminate the deployment engine registry information for other products installed on the system, so use caution when uninstalling the deployment engine.

Incorrect db2admin password


If you encounter error CTGIN9042E Errors were encountered during the execution of the step DB2 Enterprise Server Edition Version 9.1.4. through the normal use of the middleware installation program, it might be related to the fact that there is an existing user named db2admin on the system, but with a different password than the one entered in the middleware installation program. Check the db2_91_inst.log file for an error similar to the following:
ERROR:The password specified is invalid. Enter a valid password.

The db2_91_inst.log file is located at: <Workspace>\<machine name>\ deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9.1\install\ 01_BASE\[INSTALL_<processing.req.id>]/logs/ db2_91_inst.log So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the machine name is mymachine, and the processing.req.id is created as a date_timestamp, then the db2_91_inst.log file would be located in:C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\ MachinePlan_mymachine\00004_DB2_9.1\install\01_BASE\[INSTALL_0424_09.32]\ logs Check the de_processreq.log file for an error similar to the following:
<errorMessages> <errorMessage>[com.ibm.ac.si.ap.action.ExternalCommandActionException: ACUOSI0050E External command action failed with return code 87. Invocation string: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1/DB2-ESE_9.1.0/ESE/setup.exe, /f, /l, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.32]/db2_91_inst.log, /u, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.32]/ Decrypted_ResponseFile.txt], com.ibm.ac.common.hosts.CreationFailedException: : ]</errorMessage> <errorMessage>[com.ibm.ac.common.hosts.CreationFailedException: : ] </errorMessage> </errorMessages> <actionErrorEvents> <actionErrorEvent actionID="InstallProduct" actionName="externalCommand"> ACUCME1100E </actionErrorEvent> </actionErrorEvents>
Chapter 9. Troubleshooting

229

The de_processreq.log file is located at:<Workspace>\<machine name>\deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9.1\install\ 01_BASE\[INSTALL_<processing.req.id>]/logs/ de_processreq.log So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the machine name is mymachine, and the processing.req.id is created as a date_timestamp, then the de_processreq.log file would be located in: C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\ MachinePlan_mymachine\00004_DB2_9.1\install\01_BASE\[INSTALL_0424_09.32]\ logs These errors indicate that the existing system user db2admin has different password than the one entered in the middleware installation program. To resolve this issue, complete the following steps: 1. If you have not done so, click Finish to exit out of the of the middleware installation program install wizard. 2. Resolve the issue using one of the following methods: v If you are the Administrator for that machine/user and if you know the password for the user db2admin you can use the same password for the middleware installation program installation. v You can delete the user db2admin and restart the middleware installation program . v You can set or change the password for existing DB2 user db2admin. To set the password for Windows, follow these steps a. Right click the My Computer icon and select Manage. b. From the Computer Management console, select Local Users and Groups in System Tools. c. Expand Local Users and Groups and then select Users d. Right-click the db2admin user and then click Set password. e. Enter the password, confirm it, and then click OK f. Click OK once again. For Linux and AIX, you can login as the root user and use the passwd command from the command line to change the password for the db2admin user:
passwd db2admin

3. Navigate to the directory containing the middleware installation program DVD image and restart the middleware installation program. 4. 5. 6. 7. 8. Select Restart the Plan and click Next. Specify the directory for the middleware install images and click Next. Specify the temporary directory and click Next. After disk space checks are completed, click Deploy to start the install. After install completes click Finish to exit the wizard.

Improper configuration of DB2 or IBM Tivoli Directory Server


While running the middleware installation program on an AIX system, you encounter the error message CTGIN9042E, which relates to a failure to properly configure DB2 or IBM Tivoli Directory Server.

230

Installation Guide:

If you encounter error CTGIN9042E through the normal use of the middleware installation program on an AIX machine, you should check the following log files to determine the precise cause of the error: Check the mwi.log file located within the workspace directory (for example:/ibm/tivoli/mwi/workspace), and look for an error similar to the following:
Caused by: <workspace>/<machine name>/deploymentPlan/MachinePlan_<machine name>/ 00005_DB2_Configuration/install/02_CONFIG/02_CONFIG_AIX.xml:173: Failed to create database instance ctginsxy.

Also check the createinstance.log file at <workspace>/<machine name>/deploymentPlan/MachinePlan_<machine shortname>/ 00005_DB2_Configuration/install/02_CONFIG/[INSTALL_<processing.req.id>]/ logs/createinstance.log for an error similar to the following:
Caused by: <workspace>/<machine name>/deploymentPlan/MachinePlan_ <machine name>/00008_ITDS_Configuration/install/02_CONFIG/02_CONFIG_AIX.xml:173: Failed to create itds database instance itdsccmxy.

Finally, check the startInstanceTool.log file at <workspace>/<machine name>/deploymentPlan/MachinePlan_<machine shortname>/ 00008_ITDS_Configuration/install/02_CONFIG/[INSTALL_<processing.req.id>]/ logs/startInstanceTool.log for any error similar to the following:
DBI1703E No valid service name or port number found

If you locate any of these errors in the log files listed, the error can be attributed to a failure to properly configure either DB2 or IBM Tivoli Directory Server. To resolve this issue, complete the following steps: 1. Click Finish to exit out of the middleware installation program install wizard. 2. Restart the middleware installation program and proceed through the wizard until you reach the Restart or Undeploy the Plan panel. 3. Select Undeploy the Plan, and then click Next. 4. Select Partial uninstall, and then click Next. 5. Select only the Configuration for DB2 Enterprise Server Edition option, and then click Next. 6. Proceed through the panels to complete the uninstall and click Finish to exit the installer. 7. Download to your local system the mwi_db2instance.sh and mwi_itdsinstance.sh files attached to the technote located at http://www.ibm.com/support/docview.wss?uid=swg21304976. Alternatively, you can create your own copies of these files. a. Create a text file named mwi_db2instance.sh and add the following content:
#!/bin/ksh port1=0 var1=3 if [ -f /etc/services ] then if [ $# -eq 0 ]
Chapter 9. Troubleshooting

231

then cat >> /etc/services << EOF DB2_ctginst1 60000/tcp DB2_ctginst1_END 60003/tcp EOF elif [ $# -gt 0 ] then port1=`expr $2 + $var1` cat >> /etc/services << EOF DB2_$1 $2/tcp DB2_$1_END $port1/tcp EOF fi fi

b. Create a text file named mwi_itdsinstance.sh and add the following content:
#!/bin/ksh port1=0 var1=3 if [ -f /etc/services ] then if [ $# -eq 0 ] then cat >> /etc/services << EOF DB2_idsccmdb 60004/tcp DB2_idsccmdb_END 60007/tcp EOF elif [ $# -gt 0 ] then port1=`expr $2 + $var1` cat >> /etc/services << EOF DB2_$1 $2/tcp DB2_$1_END $port1/tcp EOF fi fi

8. Based on the deployment choices you made in the middleware installation program, run the following scripts: v If you elected to deploy both the Database Server and Directory Server, run both the mwi_db2instance.sh and mwi_itdsinstance.sh scripts. v If you elected to deploy the Database Server only, run the mwi_db2instance.sh script. v If you elected to deploy the Directory Server only, run the mwi_itdsinstance.sh script. 9. Run the middleware installation program again and select the option to Restart the plan, which will install everything you selected in the original deployment plan. 10. Proceed through the rest of the installation process and exit the installation program when complete. When using the mwi_db2instance.sh script, DB2 will be installed with default values if you initiate the script without passing any parameters. If you want to use custom values run mwi_db2instance.sh and pass values for DB2 instance name and the DB2 port number in the following order as shown below:./ mwi_db2instance.sh ctginsxy 50007 where ctginzxy and 50007 are the values entered in middleware installation program DB2 Configuration Panel. When using the mwi_itdsinstance.sh script, IBM Tivoli Directory Server will be installed with default values if you initiate the script without passing any

232

Installation Guide:

parameters. If you want to use custom values run mwi_itdsinstance.sh and pass values for the instance name and the port number in the following order as shown below: ./mwi_itdsinstance.sh itdsccmxy 60007 where itdsccmxy and 60007 are the values entered in middleware installation program IBM Tivoli Directory Server DB2 instance Configuration Panel.

Incorrect idsccmdb user password


If you encounter error CTGIN9042E through the normal use of the middleware installation program, it might be related to the fact that there is an existing user named idsccmdb on the system, but with a different password than the one entered in the middleware installation program. The error might look like the following:
CTGIN9042E: Errors were encountered during the execution of the step Configuration for IBM Tivoli Directory Server

Check the configureDB.log file for an error similar to the following:


GLPCDB018E The DB2 administrator ID or password you specified is not valid.

This would indicate that the existing IBM Tivoli Directory Server user idsccmdb has different password in the system . The configureDB.log file is located at: <Workspace>\<machine name>\ deploymentPlan\MachinePlan_<machine shortname>\00008_ITDS_Configuration\ install\02_CONFIG\logs\configureDB.log Windows So, for example in Windows, if the workspace is located at: C:\ibm\tivoli\workspace, the machine name is mymachine, then the configureDB.log file would be located in: C:\ibm\tivoli\mwi\workspace\ mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\ 00008_ITDS_Configuration\install\02_CONFIG\logs Linux In Linux, if the workspace is located at: /root/ibm/tivoli/mwi/workspace, the machine name is mymachine, then the configureDB.log would be located in: /root/ibm/tivoli/mwi/workspace/mymachine.ibm.com/ deploymentPlan/MachinePlan_mymachine.ibm.com/ 00008_ITDS_Configuration/install/02_CONFIG/logs AIX In AIX, if the workspace is located at: /ibm/tivoli/mwi/workspace, the machine name is mymachine, then the configureDB.log would be located in: /ibm/tivoli/mwi/workspace/mymachine.ibm.com/deploymentPlan/ MachinePlan_mymachine.ibm.com/00008_ITDS_Configuration/install/ 02_CONFIG/logs

To resolve this issue, complete the following steps: 1. If you have not done so, click Finish to exit out of the of the middleware installation program install wizard. 2. Resolve the issue using one of the following methods: v If you are the Administrator for that machine and if you know the password for the user idsccmdb you can use the same password for the middleware installation program installation. v You can delete the user idsccmdb and restart the middleware installation program . v You can set or change the password for existing IBM Tivoli Directory Server user idsccmdb .
Chapter 9. Troubleshooting

233

To set the password we have to follow the below steps Windows a. Right click on My Computer icon and click Manage menu item. b. From the Computer Management console, select Local Users and Groups in System Tools. c. Expand Local Users and Groups and then select Users d. Right-click on the idsccmdb user and then click the set password menu item. e. Enter the password, confirm it, and then click OK f. Click OK once again. Linux AND AIX a. Log in as root and open command prompt. b. Run the following command at terminal: # passwd idsccmdb c. Enter the new password and confirm it. Navigate to the directory containing the middleware installation program DVD image and restart the middleware installation program. Select Undeploy the Plan and click Next. Select Partial Uninstall and click Next. Select Configuration for IBM Tivoli Directory Server and click Next.

3. 4. 5. 6.

7. Click Undeploy to start the uninstall. 8. After install completes click Finish to exit the wizard. 9. Navigate to the directory containing the middleware installation program DVD image and restart the middleware installation program. 10. Select Restart the Plan and click Next. 11. Specify the directory for the middleware install images and click Next. 12. Specify the temporary directory and click Next. 13. After disk space checks are completed, click Deploy to start the install. 14. After install completes click Finish to exit the wizard.

Incorrect service pack requirement for AIX


When running the middleware installation program on AIX platforms, you might encounter the following message: CTGIN9061E: Unsupported Technology Level. OS Technology Level should be 06 or greater and SP level 02 or greater. This message is shown when the cited service pack level is incorrect. When you encounter error CTGIN9061E, note that while the error message indicates SP level 02 or greater is a prerequisite, SP level 01 or greater is the actual middleware installation program prerequisite.

Failure when system directories cannot be renamed


During middleware installation you encounter CTGIN9042E during the execution of a number of installation steps. This can occur during the execution of any of the middleware steps where renaming of the product install directories has failed. If you encounter error message: CTGIN9042E: Errors were encountered during the execution of step <step_name>, where <step_name> can be any of a number of middleware installation steps. For example: "CTGIN9042E: Errors were

234

Installation Guide:

encountered during the execution of step DB2 Enterprise Server Edition Version 9.1.4". Prior to installing the specific middleware product, the middleware installer attempts to save any existing product install directories by renaming them. For example, if you are installing to /opt/IBM/db2/V9.1, and this directory already exists from a previous installation or it has been previously created, the middleware installer will attempt to rename it to /opt/IBM/db2/ V9.1_<date_time_stamp>. This renaming of existing directories can fail in certain situations. For example: 1. if it has been previously created as a filesystem (instead of a directory within a defined filesystem) 2. if the filesystem or directory has been created with Read Only access To determine if this is the cause of the error complete the following steps: 1. Check the DeploymentPlan.log This log file is located at /ibm/tivoli/mwi/workspace/<Machine_name>/ deploymentPlan/logs/[INSTALL_<date_time_stamp>]/DeploymentPlan.log, where /ibm/tivoli/mwi/workspace is the default middleware workspace or the path you specified on the installer workspace panel, and <Machine_name> is the host name of the machine on which you are installing. Locate the step name that has failed. For example:
2008-12-15 04:07:44.595 : Failed: Deployment Step: step_00004_DB2_9.1 2008-12-15 04:07:44.595 : Machine Plan: MachinePlan_mymachine.mydomain.com

The failed step in this case is "step_00004_DB2_9.1" Also check the DeploymentPlan.log for the following sample error text (substitute your machine name instead of the host name shown here):
ml:284: The following error occurred while executing this line: /ibm/tivoli/mwi/workspace/<host name>/deploymentPlan/MachinePlan_<host name> /deploymentPlan/MachinePlan_00004_DB2_9.1/common/Utils.x ml:544: Deployment Engine command de_processReq reported an error.

Check the de_processReq output file at /ibm/tivoli/mwi/works pace/<host name>/deploymentPlan/MachinePlan_<host name>/00004_DB2_9.1/install/ 01_BASE/[INSTALL_1215_04.00 ]/logs/de_processreq.log_utf8 Check de_trace.log at /ibm/tivoli/mwi/workspace/<host name>/ deploymentPlan/MachinePlan_<host name>/00004_DB2_9.1/install/01_BASE/ [INSTALL_1215_04.00]/logs. 2. Check the location and the logs indicated by the error message from step #1: Check de_processreq.log_utf8 at /ibm/tivoli/mwi/workspace/<host name>/deploymentPlan/MachinePlan_<host name>/00004_DB2_9.1/install/ 01_BASE/[INSTALL_1215_04.00 ]/logs/de_processreq.log_utf8 for the following error text:
<errorMessage>[com.ibm.ac.si.ap.action.ExternalCommandActionException: ACUOSI0050E External command action failed with return code 1. <actionErrorEvent actionID=RenameExistingInstallLocation_Unix actionName="externalCommand">ACUCME1100E</actionErrorEvent>

If this error is found in de_processreq.log_utf8, check for the existence of the following error file that might contain additional information: <Product_Name>_RenameExistingInstallLocation_Unix_<Date_Time_stamp>.err For example,

Chapter 9. Troubleshooting

235

DB2_Enterprise_Server_Edition_RenameExistingInstallLocation_ Unix_20081215_040712GMT-05.00.err

. View the contents of the file if it exists and determine if it contains an error message similar to the following:
mv: 0653-401 Cannot rename /db2 to /db2_20081215_040712GMT-05.00: The requested resource is busy.

In this case /db2 is the name of the existing filesystem or directory and /db2_20081215_040712GMT-05.00 is the new name the middleware installer is using for the mv command to rename the filesystem or directory. To resolve the problem: a. If this is a filesystem, rerun the installer and specify a new directory within the filesystem: 1) Restart the middleware installer, and select Undeploy the plan. Choose Complete Uninstall and click Undeploy. 2) Restart the middleware installer and select Edit the configuration parameters. 3) Specify a directory (for example, /db2/V9.1) within the filesystem for the install location of the product that previously failed. 4) Deploy the plan b. If this is a filesystem or directory with Read Only access, give write permission for the user or owner of the filesystem (directory) and the user performing the installation. Then, run the middleware installer again to deploy the plan.

SOAP connection problem


If you encounter error CTGIN9042E through the normal use of the middleware installation program on a Microsoft Windows Server 2003 system configured to use dual IP addresses for IPv4 and IPv6, it might be caused by a SOAP connector performance issue. This error occurs during the execution of the WebSphere Application Server ND 6.1 configuration or authentication service configuration steps. Check log files for WebSphere ND configuration failure messages in the following location: <workspace>\<machine name>\deploymentPlan\MachinePlan_<machine shortname>\00010_WAS_ND_Configuration\install\01_BASE/ [INSTALL_<processing.req.id>]/logs/ Check log files for authentication service configuration failure messages in the following location: <workspace>\<machine name>\deploymentPlan\ MachinePlan_<machine shortname>\00012_ESS_6.1\install\01_CONFIG\ [INSTALL_<processing.req.id>]/logs So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the machine name is mymachine, and the processing.req.id is created as a date_timestamp, log files would be located in:C:\ibm\tivoli\mwi\workspace\ mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\00009_WAS_ND_6.1\ install\01_BASE\[INSTALL_1130_06.54]\logs Also check log files for the following error:
Unable to connect to the process dmgr on node ctgCellManager01 using SOAP connector.

To resolve this issue when you encounter it, complete the following steps:

236

Installation Guide:

1. Click Finish to exit out of the Tivoli middleware installation program. 2. Restart the Tivoli middleware installation program. 3. Proceed through the wizard until you reach the panel that gives you the choices of Restart the Plan or Undeploy the Plan. 4. Select Undeploy the Plan and click Next. 5. Click Undeploy. 6. Once the uninstall is complete, click Finish to exit the Tivoli middleware installation program installation program. 7. Manually delete the workspace folder (for example C:\ibm\tivoli\mwi\ workspace). 8. Open a system prompt and launch the Tivoli middleware installation program again from within the cd_image directory using the RMI option.
mwi.exe -V USE_RMI_FOR_IPV6=yes

These steps will resolve the SOAP connection problem with the process deployment manager.

Invalid DB2 password value


If you encounter the following error while using the middleware installation program:
CTGIN9042E: Errors were encountered during the execution of the step DB2 Enterprise Server Edition Version 9.1

it could be attributed to the use of a password value entered for the DB2 user in the middleware installation program that is incompatible with the password policy of the system. Check the db2_91_inst.log file for an error similar to the following:
1: ERROR:The installation program has been unable to create the user "db2admin" on computer "mymachine" because the password specified is too short. 1: ERROR:The response file specified "C:\WINNT\TEMP\2\_INSTA~1.18_/DECRYP~1.TXT" is not valid.

The db2_91_inst.log file is located at: <Workspace>\<machine name>\ deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9.1\install\ 01_BASE\[INSTALL_<processing.req.id>]/logs/ db2_91_inst.log So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the machine name is mymachine, and the processing.req.id is created as a date_timestamp, then the db2_91_inst.log would be located in:C:\ibm\tivoli\mwi\ workspace\mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\ 00004_DB2_9.1\install\01_BASE\[INSTALL_0424_09.32]\logs. Also check the de_processreq.log file for an error similar to the following:
<errorMessages> <errorMessage>[com.ibm.ac.si.ap.action.ExternalCommandActionException: ACUOSI0050E External command action failed with return code 87. Invocation string: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1/DB2-ESE_9.1.0/ ESE/setup.exe, /f, /l, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\ [INSTALL_0424_09.32]/db2_91_inst.log, /u, C:\DOCUME~1\ADMINI~1\LOCALS~1\ Temp\1\[INSTALL_0424_09.32]/Decrypted_ResponseFile.txt], com.ibm.ac.common.hosts.CreationFailedException: : ]</errorMessage> <errorMessage>[com.ibm.ac.common.hosts.CreationFailedException: : ] </errorMessage>
Chapter 9. Troubleshooting

237

</errorMessages> <actionErrorEvents> <actionErrorEvent actionID="InstallProduct" actionName="externalCommand">ACUCME1100E </actionErrorEvent> </actionErrorEvents>

The de_processreq.log file is located at: <Workspace>\<machine name>\deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9.1\install\ 01_BASE\[INSTALL_<processing.req.id>]/logs/ de_processreq.log. So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the machine name is mymachine, and the processing.req.id is created as a date_timestamp, then the de_processreq.log would be located in: C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\ MachinePlan_mymachine\00004_DB2_9.1\install\01_BASE\[INSTALL_0424_09.32]\ logs. This would indicate that the password provided for the DB2 user db2admin in the middleware installation program is not supported by the policy of the operating system. To resolve this issue, complete the following steps: 1. If you have not done so, click Finish to exit out of the of the middleware installation program install wizard. 2. Check the system rules defined for passwords by navigating to Start Control Panel Administrative Tools Local Security Policy Security Settings Account Policies Password Policy. 3. Restart the middleware installation program. Windows On the DVD titled IBM Maximo Asset Management V7.1 Launchpad for all Platforms, 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 IBM Maximo Asset Management V7.1 Launchpad for all Platforms, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh. On the DVD titled IBM Maximo Asset Management V7.1 Launchpad for all Platforms, navigate to the root directory of the product disc or the downloaded installation image, and run the following command: launchpad.sh. 4. Proceed through the panels until you reach the option to select Undeploy the Plan and then click Finish to exit the wizard. AIX 5. Restart the middleware installation program. 6. Select Edit the Configuration parameters. 7. Enter a valid password for the DB2 user based upon the password policy rules you observed earlier. 8. Specify the directory for the middleware install images and click Next. 9. Specify the temporary directory and click Next. 10. After disk space checks are completed, click Deploy to start the install. 11. After install completes click Finish to exit the wizard.

238

Installation Guide:

Troubleshooting the product installation program


Use the information contained in this section to troubleshoot errors encountered when using the product installation program. This section contains both general troubleshooting advice and solutions to specific errors encountered when using the product installation program.

General troubleshooting of the product installation program


Refer to this section for general troubleshooting information about the product installation program. Because Maximo Asset Management is typically deployed as a distributed system with code running on several different servers, errors can be generated from multiple sources. The install error panel will display any failure messages encountered during execution of the configuration step of the deployment. These messages direct you to the source of the problem, which will tell you which set of logs to examine for further details. All installation related messages begin with the prefix CTGIN. Informational message end with a suffix of I, warning messages end with a suffix of W, and error messages end with a suffix of E. There are four main categories of logs that can be used for installation error remediation. v Install trace logs v Solution install logs v Maximo logs v Middleware logs

Install trace logs


Install trace logs are generated on the Maximo Asset Management administrative workstation in the <MAM_HOME>\logs directory. These logs can be searched for the error message displayed on the install error panel, and can be useful in getting more diagnostic information on why the error occurred. Install trace logs contain historical data about when the installation program was invoked, which options were chosen for the deployment, and information about updates and fix packs. Searching on the term maxinst will place you in the general proximity of information about database configuration. If you encounter an error during a validation task, install trace logs can also be located within the C:\Documents and Settings\Administrator directory. They are moved to the <MAM_HOME>\logs directory during execution of the configuration step of the deployment. The following trace log files are found in the <MAM_HOME>\logs directory: CTGInstallTrace00.log This log contains information produced by the Maximo Asset Management installation program which includes information generated by the configuration code that performs the automated configuration of WebSphere Application Server Network Deployment and DB2 and also
Chapter 9. Troubleshooting

239

information related to embedded calls to the process solution installation program. Information generated from subsequent invocations of the Maximo Asset Management installation program or the process solution installation program will be appended to this file. The following success message examples are found in the CTGInstallTrace00.log file and can be used to determine which phases of the installation were successful: v CTGIN2114I: The database was created successfully v CTGIN2135I: Tablespace maxdata created successfully v CTGIN2135I: Tablespace maxtemp created successfully v CTGIN2079I: Base services database configuration completed successfully (This message indicates that maxinst finished successfully.) v CTGIN2222I: WebSphere Application Server creation successful v CTGIN2188I: Creation and configuration of service integration bus successfully completed v CTGIN2184I: Creation and configuration of JMS resources successfully completed v CTGIN2310I: Application server security was successfully enabled for the base services v CTGIN2253I: buildmaximoear.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMO was successful v CTGIN2253I: buildhelpear.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMOHELP was successful v CTGIN2208I: runConfigurationStep completed successfully v CTGIN2370I: The installation finished successfully The following warning message example is found in the CTGInstallTrace00.log file and indicates that while a function completed successfully, you should perform some additional steps outside of the installation program. v CTGIN2420W The undoConfiguration function completed but some manual clean-up is required for the following component: <Variable formatSpec="{0}">manual component</Variable>. The following error message example indicates that while the installation completed, there were some serious errors. v CTGIN2371E: The installation is finished, but some serious errors occurred during the install. In this error case, open the CTGInstallTrace00.log file and examine the most recent logged information located at the bottom of the file to determine what caused the failure. In some cases, the error will be the result of a failed configuration task that was attempted by Maximo Asset Management installation program configuration scripts. CTGInstallMessage00.log This log contains named message statements generated by the Maximo Asset Management installation program, configuration tasks, and the process solution installation program during the installation. CCMDB_install.log This log contains information about the Maximo Asset Management installation program itself, including values that you provided and options you selected during the installation.

240

Installation Guide:

Note that in some instances, you will find trace logs containing 01, 02, and so on in the file name. These files contain information similar to what is found in the files that include 00 in the file name. These files are generated when a second JVM is started during the installation, and it begins logging information.

Solution install logs


Solution install logs are generated on the Maximo Asset Management administrative workstation in the <MAM_HOME>\solutions\logs and C:\program files\ibm\common\acsi\logs\<administrative user> directories. These logs provide in depth information about exceptions and errors related to process manager packages, other PSI packages, and also the deployment engine.

Maximo logs
Core components of Maximo Asset Management include deployment utilities such as updatedb, configdb, maxinst, tdtoolkit, buildmaximoear, and deployapplication. Logs for these components are generated on the Maximo Asset Management administrative workstation in the <MAM_HOME>\maximo\tools\maximo\log directory.

Middleware logs
Native middleware logs for the database server and the J2EE server can be examined for failures occurring on the middleware server itself.J2EE-related logs generated for the WebSphere Application Server application server, deployment manager, and node agent can be used to troubleshoot errors attributed to EAR file deployment or ISC module deployment failures. Refer to the troubleshooting section of the information center for more information regarding log files generated by middleware. If you encounter errors related to EAR file deployment, examine the SystemOut.log and SystemError.log files.

Log utility
When engaging IBM product support services, be prepared to provide log files in an archive file. The LogZipper.bat utility provided in the <MAM_HOME>\scripts directory can be used for this task. If you use the LogZipper.bat utility, all relevant log files will be archived in <MAM_HOME>\debug\YYYYMMDD_hhmmss.zip. When contacting IBM support personnel, you will typically be asked to provide log files from the following directories: v <WAS_PROFILE_HOME>\logs (from both the WebSphere Application Server Network Deployment application server and the WebSphere Application Server Network Deployment deployment manager) v <PORTAL_HOME>\log v <MAM_HOME>\logs v v v v <MAM_HOME>\solution/logs <MAM_HOME>\maximo\applications\maximo\properties <MAM_HOME>\etc\install.properties <Middleware_Installer_Workspace>

Chapter 9. Troubleshooting

241

IBM Support Assistant Workbench


The IBM Support Assistant (ISA) V4 is a free, standalone serviceability workbench that you can download from IBM. ISA, using product-specific add-ons, provides a central location to learn more about products, gather data for troubleshooting problems, and manage problem submissions. The IBM Service Management and IBM Maximo Asset Management (Maximo Asset Management) add-ons to the ISA Workbench provide a quick and direct way to learn more about the product. If you encounter a problem while running Maximo Asset Management, you can use the ISA with these add-ons to search support documents for fixes or recommendations and quickly gather relevant logs for diagnosis. You can use the Log Analyzer to view the logs, use the filter feature to reduce the amount of data to examine, and use the symptom catalogs to analyze the logs. You can use the ISA to perform these tasks: v Search documents concurrently. Rapidly search IBM documentation in many different locations at the same time for answers to your questions or problems. ISA returns results that are categorized by source for easy review. v Access product information. Quickly access key product information links, such as the product support page and home page, online product documentation, and RSS feed information for the latest Flash notes, APARs, fixes, and technotes. v Gather data. Collect files to document problems related to installation, databases, security, and general problems relevant to troubleshooting your environment. The collected data is packaged in compressed form for transmission to IBM. v Analyze log data. Use the Log Analyzer to review collected log files and troubleshoot problems. v Report problems. Connect to the IBM Electronic Service Request system to open and update Problem Management Records and then send the information that the IBM Service Management data collection scripts gather to IBM for diagnosis. To learn about supported platforms, system requirements, and how to install the IBM Support Assistant, visit http://www.ibm.com/software/support/isa/isa40/ install.html.

Deployment properties
Deployment of ISM solutions often happens in stages. You might install one ISM product and then deploy another at a later date. Because follow up deployments rely on the installation and configuration data from previous installations, for example, how to connect to the database used with the original product deployment, this information must be persisted and protected. This is achieved by storing deployment data in both the product database and a set of properties files. This redundancy protects the deployment information in case anything were to happen to the database. After a successful deployment, deployment properties are kept both in the database and in two property files. maximo.properties The maximo.properties file is an encrypted file which is located in the <MAM_HOME>\maximo\applications\maximo\properties\ directory. This property file contains database connection properties.

242

Installation Guide:

install.properties The install.properties file is an encrypted file which is located in the <MAM_HOME>\etc\ directory and contains the majority of properties related to the deployment. If you experience errors related to an inability to connect or authenticate to middleware servers during an upgrade or fix pack installation, it might be caused by obsolete property values. For example, if you have changed the password for a user ID that you used during the initial Maximo Asset Management installation without updating that value in the relevant property file, the next installation action will fetch the outdated value from the property file and a failure will occur. Refer to Installation properties on page 267 for detailed information about properties contained in these files and also for information on updating properties following a successful deployment.

License files
License files are located on the media and are not packaged with the installation executable. If you copy the installation program from the product media to the file system, the License directory must also be copied.

Problem resolution
The configuration step of the Maximo Asset Management installation process occurs once you have navigated through all of the install wizard panels and then clicked the Install button. Errors experienced before the configuration step are typically related to the inability of the install program to verify input values you have provided. If you experience this sort of error, investigate the trace logs, resolve the issue, and then proceed through the rest of the install wizard. If you experience an error after the configuration step, you must exit the installation program, examine the trace, solution install, and Maximo logs, resolve the issue, and then complete the installation using the taskrunner utility by invoking it from the command line:
C:\IBM\SMP\scripts\taskRunner.bat CONTINUE STOPONERROR

Note: If you reboot the system, you will not be able to use the taskrunner utility to run configuration scripts. Taskrunner data stores are not persisted. If you intend to use the taskrunner utility, do not reboot your system. The taskrunner utility will resume the installation at the point where the last successfully completed task was recorded in the previous attempt. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner will continue despite errors.

Common deployment failures


Refer to this section for general troubleshooting information about common deployment failures.

Chapter 9. Troubleshooting

243

Invoking the installation program


If you invoke the product installer for a new installation or upgrade from a drive that is different than the one you choose as the installation destination, the installation will fail. This behavior occurs when invoking the installer directly or though the product launchpad. To resolve this problem, start the installer or launchpad application from the drive where you will install the product. For example, if you want to install the product on the g: drive, open a command prompt and switch to the g: drive prior to invoking the installer. So, if your installer was located on the d: drive the command might look like the following:
g:\> d:\temp\install.exe

(where g:> is your Windows command prompt) Windows explorer normally sets the system default drive to "%HOMEDRIVE%" which is typically the drive where Windows is installed. If that is the target drive of the product install you can start the installer or launchpad from Windows Explorer. If you plan to install the product on a drive other than the one hosting Windows, you should not start the installer from Windows Explorer. Invoke the installer from the command line as described earlier.

Remote access configuration


If you choose to configure WebSphere Application Server Network Deployment and the database using the automated configuration feature of the Maximo Asset Management installation program, you must enable a remote access protocol for each system hosting a middleware server. Refer to Remote configuration enablement on page 37 for more information. Messages with the prefix CTGRI found in the CTGInstallTrace.log file are related the Maximo Asset Management installation program not being able to access remote systems that have been designated as part of the product deployment. Ports An error reporting a failure to reach the remote host can sometimes be related to a required port not being available to the Maximo Asset Management installation program. Ensure the following ports are accessible on servers that will be hosting middleware: 445 139 Port 445 is used for SMB over TCP. Port 139 is used for TCP NetBIOS connections.

Remote registry permissions Error CTGRI0011E is issued if the user ID provided to the installation program that is used to access a remote Windows system does not have appropriate permissions to the registry. Remote access to the registry is determined by the HKLM\System\CurrentControlSet\Control\ SecurePipeServers\winreg registry key entry. Visit the Microsoft help and support web site (http://support.microsoft.com/) and use the issue search facility to locate the article on how to manage remote access to the registry. Connection exceptions Remote access connection exceptions typically manifest themselves as

244

Installation Guide:

either an authorization failure or as a host connection failure. Search the CTGInstallTrace.log file to determine the cause of the connection exception. An authorization error is triggered by an incorrect user ID or password value supplied to the Maximo Asset Management installation program. Errors for this type of exception typically look similar to the following example:
SEVERE: EXIT ^RxaConnectFailure:^o^{{com.ibm.tivoli.remoteaccess. RemoteAccessAuthException: CTGRI0000E Could not establish a connection to the target machine with the authorization credentials that were provided. at com.ibm.tivoli.remoteaccess.BaseProtocol.beginSession(BaseProtocol. java:522) at com.ibm.tivoli.ccmdb.install.common.util.rxa.RxaHost.init(RxaHost. java:130) at com.ibm.tivoli.ccmdb.install.common.util.rxa.RxaHost.<init>(RxaHost. java:78) at com.ibm.tivoli.ccmdb.install.common.ia.CmnInstallAnywhereUtils.getOSType (CmnInstallAnywhereUtils.java:303) at com.ibm.tivoli.ccmdb.install.foundation.appsvr.FndWasRemoteActions.install (FndWasRemoteActions.java:237) at com.zerog.ia.installer.actions.CustomAction.installSelf(DashoA10*..) at ZeroGab8.run(DashoA10*..)

A host connection failure is triggered when the remote protocols Maximo Asset Management installation program cannot reach the remote system using the protocols it supports. This error typically looks similar to the following example:
RemoteSystem can't be reached using Supported RXA protocols.

Once you have resolved these errors, you can continue to use the Maximo Asset Management installation program.

Application server
SOAP errors Details for errors resulting from the failure to deploy the maximo.ear and maximohelp.ear files can be found in several places, including the CTGInstallTrace00.log file and also the SystemOut.log, SystemError.log, and Trace.log files hosted on the WebSphere Application Server Network Deployment deployment manager. Refer to the troubleshooting section of the information center for more information regarding log files generated by middleware. Typical EAR file deployment failures can include SOAP connection errors where the SOAP port (8879) is not available, or inadequate space on the WebSphere Application Server Network Deployment server to either transfer or deploy the maximo.ear file. You might encounter a SOAPException error during deployment of the maximo.ear or maximohelp.ear from the administrative system to the WebSphere Application Server Network Deployment. Under certain conditions, the WebSphere Application Server Network Deployment may be unable to service requests to deploy the maximo or maximohelp applications and will display a SOAPException. The following CTGInstallTrace00.log log information is an example of the error information that is displayed when such an exception is encountered.
----- START OF LOG FILE INFORMATION Exception caught during installation of
Chapter 9. Troubleshooting

245

C:/IBM/SMP/maximo/deployment/default/maximo.ear . Review JVM logs in WebSphere, install trace logs and wsadmintrace.out for more information Exception Type: com.ibm.ws.scripting.ScriptingException Value: com.ibm.ws.scripting.ScriptingException: com.ibm.websphere.management.exception.ConfigServiceException com.ibm.websphere.management.exception.ConnectorException org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.net.SocketException: Operation timed out: connect:could be due to invalid address; targetException=java.lang.IllegalArgumentException: Error opening socket: java.net.SocketException: Operation timed out: connect:could be due to invalid address] ----- END OF LOG FILE INFORMATION

You may see an error similar to the above error in process solution installation log files contained in the solutions\logs sub-directory under your Maximo Asset Management installation. The file names of the log files will include the words Deploy and EAR as part of the filename. You should take note of the filepath of the EAR file that was unable to be successfully deployed. In the above example, the filepath of the EAR file is C:/IBM/SMP/maximo/deployment/default/maximo.ear. The conditions that trigger this problem are often temporary in nature. You should first check the health of the WebSphere Application Server Network Deployment by attempting to log into the Deployment Manager using the WebSphere administrative console. If you are unable to successfully log in, review the WebSphere Application Server Network Deployment log files to determine the nature of the failure. If you are able to successfully log in, you may attempt to workaround this problem by deploying the EAR to WebSphere Application Server Network Deployment using either the WebSphere administrative console or the deployApplication.bat script. The syntax for the deployApplication.bat script follows. Syntax elements in brackets <> need to be replaced with the values for those properties in your environment.
<MAMInstallLocation>\jacl\solutions\DeployApplication.bat <WASAdminUserName> <WASAdminPassword> <ApplicationName> Either MAXIMO or MAXIMOHELP <WASNodeName> <WASApplicationServerName> <path-to-EAR-file> <WASVirtualHost> <WASWebServerName>

So, for example:


C:\IBM\SMP\jacl\solutions\DeployApplication.bat" wasadmin <waspassword> MAXIMO ctgNode01 MXServer C:\IBM\SMP\maximo\deployment\default\maximo.ear maximo_host webserver1

Connecting to the application Near the end of the installation process, the Maximo Asset Management installation program performs a health check to ensure the deployment was successful. This health check consists of logging into the application. If it fails, you will see the following error:
CTGIn2252IW: Cannot connect to base services web app

246

Installation Guide:

This likely means that either the JVM or the HTTP server is not functional and routing requests, you did not specify the correct port for your environment during the installation, or the application was not started correctly. You should attempt to log into the application directly after exiting the installer. If that fails, check the logs of the JVM, HTTP server, and MXServer located on the WebSphere Application Server Network Deployment server to verify they are up and running. Note: Port 80 is the HTTPServer port and should be the value used during installation, assuming you have installed the HTTPServer. If the HTTPServer is installed but not bound to port 80, then use the port that it is bound to. For future use, the port is saved in the Maximo database table maxpropvalue and can be updated to match your environment once the installation has completed.

Database
Updatedb The updatedb command is run several times during Maximo Asset Management installation. Each time updatedb is run, a time-stamped log file is generated in the <MAM_HOME>\maximo\tools\maximo\log directory. If you encounter an error attributed to updatedb, refer to the updatedb log with the most recent timestamp for details. Once you have performed corrective measures, you can complete the deployment using the taskrunner utility as described in General troubleshooting of the product installation program on page 239. MAXPRESENTATION update error While installing Maximo Asset Management, you might encounter a MAXPRESENTATION error. If you receive the following errors when installing, it indicates the presence of database values that are not synchronized.
Error: (RECONLINK) Unable to update MAXPRESENTATION - null java.lang.Exception Error: (RECONLINK) Unable to update MAXPRESENTATION - null at psdi.webclient.upgrade. MXApplyTransactions.saveApplicationDocument(Unknown Source)

If you encounter these errors, execute the following SQL statements against the database to verify the cause:
select maxreserved from maxsequence where tbname = 'MAXPRESENTATION'; select max(maxpresentationid) from maxpresentation;

The maxreserved value should be greater than or equal to the max(maxpresentationid) value. If it is not, execute the following SQL statement to correct it.
update maxsequence set maxreserved = (select max(maxpresentationid) from maxpresentation) where tbname='MAXPRESENTATION' and name='MAXPRESENTATIONID';

Microsoft SQL Server and MEA registration failure When installing Maximo Asset Management on an upgraded Microsoft SQL Server database, if the error CTGIN2254I: The C:\IBM\SMP\jacl\ solutions\MEAReg.bat did not complete successfully. is displayed, complete the steps below to work around the problem. You might also find the following errors within the mxserver logs:
Chapter 9. Troubleshooting

247

BMXAA5228E - Could not register event listeners for all active Migration Manager change packages. BMXAA4156E - Not a valid data type.

1. From the Microsoft SQL Server Control Center, go to the MAXUSER table, and modify the SCREENREADER column name null attribute to not allow nulls (required) 2. Execute the following SQL statement:
alter table maxuser alter column screenreader smallint;

Microsoft SQL Server and ICfgConfigurationStep When you attempt to install the product using Microsoft SQL Server, you might also encounter the following error message: CTGIN2074E: Exception caught creating ICfgConfigurationStep object. The origin of this error can be confirmed by examining the CTGInstallTrace00.log for the following details:
FINE: ENTER^ENTER^S^Using Connection: com.inet.tds.an@7ba07ba0 Sep 17, 2008 4:21:14 PM com.ibm.tivoli.ccmdb.install.common.util. CmnEncryptPropertiesUtil init() SEVERE: NOTE ^^T^[ITAMBVT-WIN]Invalid object name 'MaxPropValue'. com.inet.tds.at: Msg 208, Level 16, State 1, Line 1, Sqlstate S0002 [ITAMBVT-WIN]Invalid object name 'MaxPropValue'. at com.inet.tds.aq.a(Unknown Source) at com.inet.tds.k.b(Unknown Source) at com.inet.tds.k.a(Unknown Source) at com.inet.tds.b.a(Unknown Source) at com.inet.tds.b.a(Unknown Source) at com.inet.tds.b.b(Unknown Source) at com.inet.tds.u.f(Unknown Source) at com.inet.tds.u.executeQuery(Unknown Source) at com.ibm.tivoli.ccmdb.install.common.util.CmnEncryptProperties Util.init(CmnEncryptPropertiesUtil.java:192)

This error is caused by the collation settings for your Microsoft SQL Server. For ISM products, Microsoft SQL Server collation settings must be set to the following options: v Dictionary order v For use with 1252 Character set For Microsoft SQL Server collation setting details, refer to the user documentation provided with the software. Invalid data type While installing Maximo Asset Management, if you encounter error CTGIN2252I: Cannot connect to base services web application or BMXAA415E - Not a Valid Data Type, use the steps below to resolve it. 1. Run the following SQL statements against the database:
update maxattribute set maxtype='YORN' where objectname='MAXSESSION' and attributename='ACTIVE'; update maxattributecfg set maxtype='YORN' where objectname='MAXSESSION' and attributename='ACTIVE';

2. From the DB2 Command Center, modify the MAXSESSION.ACTIVE data type to be an integer. Oracle Text indexing Maximo Asset Management requires a series of text indices to improve performance of text searches. These are created when the maxinst command is run as part of the installation. If maxinst fails when attempting to create text indices for an Oracle database, you will see errors similar to the following in the CTGInstallTrace.log file:

248

Installation Guide:

ORA-01031 ORA-04045 with MDSYS.SDO_GEOR_TRUNC_TABLE

To resolve the issue, you must install Oracle Spatial: 1. Connect to the database instance specifying AS SYSDBA. 2. Create the MDSYS user with a command in the following format:
SQL> CREATE USER MDSYS IDENTIFIED BY <password>;

3. Grant the required privileges to the MDSYS user by running the following procedure:
SQL> @ORACLE_HOME/md/admin/mdprivs.sql

4. Connect as MDSYS. 5. Install Spatial by running the following procedure:


SQL> @ORACLE_HOME/md/admin/catmd.sql

6. Connect as SYS and lock the MDSYS user account to prevent unauthorized use.
SQL> ALTER USER MDSYS ACCOUNT LOCK;

7. Rebuild the triggers by running the following:


@/<oracle_home>/rdbms/admin/utlprp.sql 0

Directory server
If you create users and groups manually in Microsoft Active Directory, as described in Manually configuring Microsoft Active Directory on page 150, but, during the Maximo Asset Management installation, you select the option to have the installer create the required users, you will receive an error similar to the following example:
Aug 4, 2008 2:17:26 PM com.ibm.tivoli.ccmdb.install.common.config.was.CfgConfigWebSphere runJythonScript INFO: EXIT ^^o^{{ReturnCode: 1 CompletionMessage: CTGIN2255I: The script D:\TCCMDB711TEMP\scripts\was\DeploymentManager.py completed with returncode 1. StandardOutput: WASX7209I: Connected to process "dmgr" on node wasundm2Manager using SOAP connector; The type of process is: DeploymentManager WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[vmmUsersAndGroupsExist, MAXADMIN:mxintadm,maxadmin, MAXIMOUSERS:mxintadm,maxadmin,maxreg]" wasundm2Cell case:vmmUsersAndGroupsExist, with arguments:['MAXADMIN:mxintadm,maxadmin', 'MAXIMOUSERS:mxintadm,maxadmin,maxreg'] ENTER:vmmUsersAndGroupsExist args passed ['vmmUsersAndGroupsExist', 'MAXADMIN:mxintadm,maxadmin', 'MAXIMOUSERS:mxintadm,maxadmin,maxreg'] MAXADMIN:mxintadm,maxadmin group MAXADMIN doesn't exist EXIT:vmmUsersAndGroupsExist RC= 1 StandardError:

To correct this error, deselect the Create the required users option shown on the security panel of the Maximo Asset Management installation program, and then continue with the installation.

Chapter 9. Troubleshooting

249

Obsolete and prohibited property values


Deployment details are stored in the database and also on the administrative system in the install.properties and maximo.properties files. Obsolete property values When you install a fix pack or otherwise upgrade an existing ISM product, the installation program uses values recorded from the previous deployment. If you have made changes to any of the systems used for the original deployment, such as changing a host name or updating a password, for example, they must be recorded in the install.properties and maximo.properties files. If you see the message: CTGIN2233I WebSphere Node Agent Not Running in the status bar of the installation program, log into the WebSphere Application Server Network Deployment administrative console to verify that the node agent is up and running. If you discover it is running, stop and restart the node agent and attempt the installation once more. If you still receive this message, chances are it is related to a mismatch between the WebSphere Application Server Network Deployment administrator user ID or password property value originating from the initial deployment and the current value. In this case, you would need to update the property in the install.properties file. The following example errors found in the wsadmin.traceout file indicate that properties recorded for the initial deployment do not match those that are being used for a subsequent installation action:
javax.management.JMRuntimeException: ADMN0022E: Access is denied for the getProcessType operation on Server MBean because of insufficient or empty credentials. [2/3/09 15:06:24:946 EST] 0000000a AbstractShell A WASX7093I: Issuing message: "WASX7246E: Cannot establish "SOAP" connection to host "myhostname.com" because of an authentication failure. Ensure that user and password are correct on the command line or in a properties file. Exception message (if any): "ADMN0022E: Access is denied for the getProcessType operation on Server MBean because of insufficient or empty credentials.""

The following example errors found in the CTGInstallTrace00.log file indicate that properties recorded for the initial deployment do not match those that are being used for a subsequent installation action:
Input Error: Can not find script file "E:\IBM\SMP\wasclient\sleep.vbs". WASX7246E: Cannot establish "SOAP" connection to host "myhost.com" because of an authentication failure. Ensure that user and password are correct on the command line or in a properties file. FINE: ENTER^^S^CTGIN2233I: WebSphere NodeAgent is not Running.

The following example error encountered in the Maximo Asset Management installation program also indicates the property values require updating.
CTGIN0210E: Process Solution Installer is unable to access deployment configuration properties from the Maximo Database. Ensure that the properties in the maximo.properties file are correct and that the Maximo Database is started.

250

Installation Guide:

To correct these errors, update properties as described in and then Updating environment data on page 280, and then complete the deployment using the taskrunner utility as described in General troubleshooting of the product installation program on page 239. Prohibited property values System users created by the installation programs must adhere to the requirements of the system. For example, the database user created by the installation program is an operating system user. The password you provide for that user needs to match the operating system password rules. If it does not, you will encounter an error message. Ensure that you enter a password of the appropriate length on the installation panel for the DB2 user that will be created. To verify the password you entered for the database user is the appropriate length, prior to clicking Install, search the CTGInstallTrace00.log for the following message:
The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements. More help is available by typing NET HELPMSG 2245.

If this message is present, then you did not create a user with the right password length. You will need to fix the operating system user password, and the password in the maximo.properties file before continuing with the installation program.

Deployment Engine
The deployment engine is a runtime environment that includes a database of information about software installed on the system. You should back up the deployment engine database of the system before and after applying any updates to an existing deployment as described in Backing up the deployment engine database on page 38. Having backups allows you to recover from partial installation attempts where middleware or process manager components were partially installed. While installing the product, you might encounter an error message CTGIN2389E. This messages indicate that the deployment engine was not installed correctly or otherwise failed to start. Examine the CTGInstallTrace00.log log file to determine the nature of the deployment engine errors that have occurred.
Dec 2, 2008 4:51:25 AM com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction handleInstall FINE: ENTER^^o^{{com.zerog.ia.api.pub.InstallerProxy@6ac06ac0,}} Dec 2, 2008 4:51:25 AM com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction handleInstall FINE: NOTE ^** ERROR: Autonomic Deployment Engine installation/upgrade failure.Return code: 3 Failure: DE in use or general failure See the CCMDB si_inst.log and DE logs for additional information. Dec 2, 2008 4:51:25 AM com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction
Chapter 9. Troubleshooting

251

failInstall FINE: ENTER^^n^Dec 2, 2008 4:51:25 AM com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction failInstall FINE: NOTE ^Setting flags to opt-out of configuration due to DE installation failure.^n^Sep 24, 2008 1:19:45 PM com.ibm.tivoli.ccmdb.install.common.config.pmp.CfgProcessManagerPackageConfig runConfigurationStep FINE: EXIT ^^o^{ReturnCode: -1CompletionMessage: DE Database backup failed, see trace for detail.StandardOutput:StandardError:,} Sep 5, 2008 11:10:43 AM com.ibm.tivoli.ccmdb.install.common.config.pmp.CfgProcessManagerPackageConfig runConfigurationStep SEVERE: EXIT ^ Output of error during PMPs Installation : ^S^java.lang.RuntimeException: com.ibm.ac.si.iuregistry.IURegException: IURegistryServiceUnavailable

The return code of 3 indicates that the deployment engine is in use or cannot be used at this time. Ensure the deployment engine service is up and running. For Windows systems, check that the IBM ADE service is currently running. If it is not, start the service. The deployment engine also generates lock files when in use. This will sometimes prevent the product installation program from working correctly. When the deployment engine is active, lock files (files with .lck and .lock extensions are generated in the C:\Program Files\IBM\common\acsi and C:\Program Files\IBM\common\acsi\logs directories. When a normal installation completes, these lock files are removed. If these locked files continue to exist on the system due to an install action that ended abnormally, they must be deleted before you run the product installation program. Use caution when removing lock files for products unrelated to the Maximo Asset Management deployment. You can verify that the version of deployment engine is valid and functional by examining the <MAM_HOME>\logs\si_inst.log file. Another useful exercise is to verify that the deployment engine can be used by the process solution installer by running the following commands:
<MAM_HOME>\bin\setupPSIEnv.bat <MAM_HOME>\bin\solutionInstaller.bat -action showInstalled -type all

If the deployment engine is operational, this command will produce a list of all process solution installer packages that are currently deployed and their version. If you receive an exception when running the command, the deployment engine is not operational. If the deployment engine failed to install, you can manually install it using the following command:
<MAM_HOME>\scripts\si_inst_wrapper.bat

After successfully installing the deployment engine, verify that it can be used by the process solution installer by running the solutionInstaller command once again. You can then complete the deployment using the taskrunner utility as described in General troubleshooting of the product installation program on page 239. If the deployment engine was installed, but not operational, there are two primary recovery scenarios. Use this information only when you have experienced a failure during installation or uninstallation or a new deployment related to the

252

Installation Guide:

deployment engine database in cases where you want to remove the product from the system completely. Deployment engine uninstall operations can result in loss of registration information about installed software components, which includes both Maximo Asset Management and non-Maximo Asset Management components. This will cause the deployment engine registry to not accurately reflect the state of the system. Recovery from a partial installation in which no PMPs were registered in the deployment engine registry To determine if Maximo Asset Management components have been deployed and registered in the deployment engine registry, use the showinstalled action of the process solution installation program command line interface:
cd <MAM_HOME>\bin solutionInstaller -action showinstalled -type all

The CTGIN0059I informational message will indicate the PMPs installed. If no PMPs have been installed, the installation failure occurred before PMPs were installed and registered in the deployment engine registry. If no PMPs are installed, you do not need to and should not uninstall deployment engine or restore a previous backup. The current deployment engine registry should be preserved and will not prohibit installation of the PMPs during the subsequent installation. Recovery from a partial or full installation in which one or more Maximo Asset Management PMPs were registered in the deployment engine registry If the showinstalled output indicates that there are one or more PMPs installed, then you need to determine if there are other non-PMP components registered in the deployment engine registry. Within this case, there are two separate scenarios: The deployment engine registry was backed up before installing Maximo Asset Management If you have a backup of the deployment engine database, created using the procedure described in Backing up the deployment engine database on page 38, you can use the following command to restore it: Windows
c:\Program Files\IBM\Common\acsi\bin\restoredb <backup file>

where <backup file name> is the file containing the deployment engine backup you made. Restore the deployment engine database backup after completing the steps to remove the Process Manager configuration. You should not uninstall deployment engine before reinstalling Maximo Asset Management. The deployment engine registry was not backed up before installing Maximo Asset Management If you do not have a backup of the deployment engine registry, the action you will take will depend on whether there are other non-PMP components registered in the deployment engine registry. Note that if you used the Maximo Asset Management middleware installation program to deploy middleware to the Maximo administration workstation, then you do indeed have non-PMP components in the deployment engine registry. You can list the contents of the deployment engine registry using the following command:
Chapter 9. Troubleshooting

253

Windows
C:\Program Files\IBM\common\acsi\bin\listiu

Note that the output resulting from the listiu command will always contain the following entries:
IU UUID: DDCE934782398B3E81431666515AC8B5 Name: DE Extensions Interfaces CLI IU Version: 1.3.1 IU UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment Engine IU Version: 1.3.1 IU RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA Name: Install IU Version: 1.3.1

These entries are internal to deployment engine and do not have to be considered when evaluating which components are currently registered. If the only other entries displayed are those associated with the PMPs shown in the showinstalled output, then only Maximo Asset Management components have been registered in the deployment engine registry. You can safely uninstall the Deployment engine. If non-PMP registry entries are present, you will still need to uninstall the deployment engine to proceed with Maximo Asset Management recovery, but be advised that if you used the Maximo Asset Management middleware installation program to deploy middleware to the Maximo administration workstation, you will not be able to use it to uninstall the middleware deployed. You also will not be able to uninstall, upgrade, or apply fixes to any non-PMP software that was installed using the deployment engine. If this is an unacceptable alternative, your only recourse is to reinstall Maximo Asset Management after reimaging your system. If, you do not have a deployment engine backup available, or the only entries registered in the deployment engine registry are related to the Maximo Asset Management deployment, you can use the following instructions to delete the deployment engine database. Windows Local Deployment Engine Deployment
C:\Documents and Setting\<userid>\acsi_<userid>\si_inst -r

Global Deployment Engine Deployment


C:\Program Files\IBM\Common\acsi\bin\si_inst -r

If the si_inst -r command fails to uninstall the deployment engine, complete the following steps to manually delete the deployment engine. Windows 1. Select the jservice.exe process, click End Process, and then click OK. 2. Remove the deployment engine home directory. Global deployment engine installations Remove the C:\Program Files\IBM\Common directory. Local deployment engine installations Remove the C:\Documents and Settings\<user_name>\My Documents\.acsi_<user_name> directory. 3. Clean up the system %TEMP% directory.

254

Installation Guide:

Global deployment engine installations Remove the %TEMP%\acu_de.log file, if it exists. Remove the %TEMP% \<user_name> directory, where <user_name> is the ID of the user that installed the deployment engine, for example, Administrator. Local deployment engine installations Remove the %TEMP% \acsitempLogs_<user_name> directory. Remove the %TEMP% \acsiTemp_<user_name> directory. 4. Open the Windows Services panel. If they exist, ensure the IBM ADE Service or ACSI Service services are stopped. While stopping these services is satisfactory, if you wish to remove them, delete the acsisrv entry found in the HKEY_LOCAL_MACHINE/SYSTEM/ CurrentControlSet/Services key of the Windows registry. 5. Reboot the machine.

Restarting middleware
During the Maximo Asset Management installation, middleware starts automatically. It can be necessary to restart middleware services, for example following a power failure or after a maintenance shutdown. To restart middleware services, follow the instructions relevant to your environment.

Restarting middleware on Windows


This procedure describes how to restart middleware on Windows, if you need to restart any middleware services.

About this task


To properly start middleware products on Windows, perform the following steps:

Procedure
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. 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:
Chapter 9. Troubleshooting

255

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 Maximo Asset Management. 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 a. Click Start, and select Run. b. Type services.msc, and click OK. c. Select IBMWAS61Service - ctgCellManager01, and click Start the service. Alternatively, you can use the following command from the command line to start the domain manager:
<WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat

Start Node a. Click Start, and select Run. b. Type services.msc, and click OK. c. Select IBMWAS61Service - nodeagent, and click Start the service. Alternatively, you can use the following command from the command line to start the node:
<WAS_HOME>\profiles\ctgAppSvr01\bin\startNode.bat

Start MXServer If you have chosen to create a service for starting the MXServer application server, you can use the Services control panel to start and stop it. Alternatively, you can use the following command from the command line to start the application server:
<WAS_HOME>\profiles\ctgAppSrv01\bin\startServer.bat MXServer

Restarting middleware on UNIX


This procedure describes how to restart middleware on Linux and UNIX platforms, if you need to restart any middleware services.

256

Installation Guide:

About this task


To properly start middleware products on Linux and UNIX systems, perform the following steps:

Procedure
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 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>

Uninstall the product or middleware


To uninstall the product or any associated middleware, for example to perform an upgrade, follow the procedures in this section.

Uninstalling middleware
Uninstalling IBM Maximo Asset Management middleware consists of running the middleware installation program and using it to undeploy the previously deployed deployment plan.

Before you begin


To uninstall the J2EE server, if you chose to deploy using a directory server, ensure IBM Tivoli Directory Server or Microsoft Active Directory is active. Do not uninstall the directory server until the J2EE server has been uninstalled.

Chapter 9. Troubleshooting

257

About this task


You must use the middleware installation program to uninstall any Maximo Asset Management middleware installed by the middleware installation program. The middleware installation program creates a registry when installing Maximo Asset Management 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 Maximo Asset Management middleware using the middleware installation program. Note: At points during the uninstall process, the middleware installation program uninstall progress bar might appear to pause. This is normal behavior. In most cases, the middleware installation program uninstall progress bar will resume shortly after pausing. If you suspect your uninstall process has experienced an error, refer to the middleware installation program log files. Note: If you intend to reinstall middleware using the middleware installation program, and you used DB2 as your database, ensure you provide the same value for the DB2 administrators group during the reinstallation. The middleware installation program creates a default instance for DB2 and adds the owner of the default instance to the DB2 administrator group specified. When DB2 is uninstalled, users and groups are not removed. During the reinstall, if a different DB2 administrators group value is supplied, DB2 will try to associate the owner of the default instance with this new group which will fail because the owner already belongs to the group specified during the initial installation. If you must specify a new DB2 administrators group during the reinstall, remove the existing instance owner and DB2 administrator group before rerunning the middleware installation program. Note: In most cases, the middleware installation program does not fail or report failures during the uninstall process. Only in the case where you are uninstalling a J2EE server that was secured using IBM Tivoli Directory Server and that directory server has not been started, will you encounter an error that will halt the uninstall process. This exception will also be recorded in the mwi.log file. In order to verify that middleware products were properly uninstalled, you will need to examine deployment plan step logs. The log files for the deployment plan are located in the subdirectory Workspace Directory/host name/deploymentPlan/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. Note: If you are undeploying middleware from a failed middleware installation, complete the following steps before using the middleware uninstaller: 1. Stop the IBM Tivoli Directory Server (IBM Tivoli Directory Server v6.2 idsccmdb). 2. Stop the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin Server v6.2 - idsccmdb). 3. Start DB2. 4. Start the idsccmdb DB2 instance (DB2 - DB2COPY1 - IDSCCMDB). 5. Start the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin Server v6.2 - idsccmdb) To undeploy Maximo Asset Management middleware, complete the following steps:

258

Installation Guide:

Procedure
1. Login as Administrator on Windows and root on Linux and AIX. 2. Launch the middleware installation program from the launchpad. a. Start the launchpad: Windows On the DVD titled <IBM Maximo Asset Management V7.1 Launchpad for all Platforms, 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 IBM Maximo Asset Management V7.1 Launchpad for all Platforms, 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 IBM Maximo Asset Management V7.1 Launchpad for all Platforms, 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. In the Middleware section, click Install the middleware. 3. Select a language for the installation and click OK. 4. From the Welcome panel, click Next. The middleware installation program 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 5. 7. In 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 middleware installation program. 10. On UNIX systems, remove all DB2 references from the /etc/services file. The entries that need to be removed are: v db2c_db2insxy 50001/tcp v db2c_db2inst1 50000/tcp 11. Reboot the system if you intend to reinstall middleware on this system using the middleware installation program.

Troubleshooting middleware uninstall


Use the information contained in this section to troubleshoot middleware uninstall issues. Use the information contained in this section to troubleshoot errors encountered uninstalling middleware installed through the middleware installation program. Uninstallation of WebSphere Application Server Network Deployment fails after unsuccessful binding to the LDAP directory:

Chapter 9. Troubleshooting

259

You encounter an error during the installation of WebSphere Application Server Network Deployment using the middleware installation program and then when you attempt to undeploy the middleware deployment plan related to unsuccessful binding to the LDAP directory. Before you begin About this task When using the middleware installation program, you encounter the option to configure WebSphere Application Server Network Deployment security with an existing remote LDAP directory. The remote LDAP directory can be hosted by either Microsoft Active Directory or by IBM Tivoli Directory Server. In order to configure WebSphere Application Server Network Deployment successfully, you need to provide the credentials to access the remote LDAP server. The set of credentials include: v Host name or IP address v Port in which LDAP server is running v LDAP base entry v User, Group and Organization suffix v Bind DN and password Also the WebSphere Application Server Network Deployment Administrator user ID and password should have existing entries in the remote LDAP Directory. If you provide the middleware installation program with the wrong credentials, the installation will fail at the WebSphere Application Server Network Deployment configuration step. Once the initial installation has failed, the uninstallation (undeployment) of the deployment plan will also fail due to incorrect credentials given at the time of installation. WebSphere Application Server Network Deployment will not be able to issue the stopManager command in order to stop the ctgDmgr01 profile. This will result in the following error:
SECJ0305I: The role-based authorization check failed for admin-authz operation Server:stop:java.lang.Boolean:java.lang.Integer. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: operator, administrator.

If you encounter the error described above, complete the following steps as a workaround: Procedure 1. For UNIX systems, complete the following steps: a. List Java processes.
ps -ef | grep -i java

b. Locate the process-id of the Java thread: <WebSphere Install Location>/java/bin/java and then kill the process.
kill -9 <process-id>

c. Restart the middleware installation program to undeploy the plan. 2. For Windows systems, complete the following steps: a. In Services control panel, change the startup type of the following WebSphere Application Server Network Deployment entries from Automatic to Manual.
IBM WebSphere Application Server V6.1 - ctgCellManager01 IBM WebSphere Application Server V6.1 - nodeagent

260

Installation Guide:

b. Restart the system. c. Restart the middleware installation program to undeploy the plan.

Uninstalling the product


This section contains information about uninstalling Maximo Asset Management 7.1. The procedures and instructions provided here are based upon a scenario in which the Maximo Asset Management installation program has experienced an error or failure. Maximo Asset Management uninstallation is a comprehensive procedure and does not support partial removal of individual components or process managers, including those deployed by other products. If you have deployed a product that includes process managers before you deployed Maximo Asset Management, and you want to uninstall Maximo Asset Management, be advised that you will also be removing the process managers deployed with the other product. Note that you will only run the Maximo Asset Management uninstallation program once. If there are errors, messages are generated that indicate conditions that you must resolve manually before attempting a reinstall. This also includes manually removing files from the administrative workstation. Maximo Asset Management can only be uninstalled using the Maximo Asset Management uninstallation program as directed. Do not use other methods to attempt to uninstall Maximo Asset Management, such as using the Add/Remove Programs panel. The uninstall procedure you follow depends on the type of Maximo Asset Management deployment you are uninstalling. For uninstallation purposes, Maximo Asset Management deployments will fall into one of the following categories: Fully-automated configuration In this scenario, you selected the option to allow the Maximo Asset Management installation program to automatically configure middleware during deployment. Refer to Uninstalling an automatically configured deployment on page 262 for information about uninstalling Maximo Asset Management for this type of deployment. Manual configuration In this scenario, you selected the option to manually configure middleware. You did not allow the Maximo Asset Management installation program to automatically configure middleware during deployment. Refer to Uninstalling a manually configured deployment on page 263 for information about uninstalling Maximo Asset Management for this type of deployment. After the Maximo Asset Management uninstall process is complete, you can reinstall Maximo Asset Management by restarting the Maximo Asset Management installation program.

Chapter 9. Troubleshooting

261

Uninstalling an automatically configured deployment


Use the information provided in this section to uninstall a Maximo Asset Management deployment that was deployed using the automatic middleware configuration options. Running the product uninstall program for automatically configured middleware: Running the Maximo Asset Management uninstall program will revert the administrative system and middleware servers back to their previous state. Before you begin Ensure all applicable services are running and all middleware servers are accessible. The Maximo Asset Management uninstall program must be able to access the database used with Maximo Asset Management to fetch installation properties and configuration data. If the Maximo Asset Management uninstall program cannot access the database because it is unavailable, corrupt, or otherwise inaccessible, then the Maximo Asset Management uninstall program will remove files from the administrative workstation and inform you that some manual recovery might be required before another Maximo Asset Management installation can be successful. The uninstall program will use values entered during the initial installation during uninstall. If credentials used to access the database and J2EE server are still valid, you will not be prompted to input them again. If the uninstall program is unable to validate these credentials, for example, if you updated passwords since the original installation, you will be prompted to supply the updated information. About this task Procedure 1. To run the Maximo Asset Management uninstall program, from the administrative workstation, open a command prompt and issue the following command: Windows
<MAM_HOME>\_uninstall\uninstall.bat

2. From the application server information panel, enter the following information and then click Next. Remote user ID Enter a user ID in order to access the system hosting the application server. The remote user ID must be able to access the server using the remote access protocol enabled on that system. Remote password Enter a password for the remote user ID. User ID Enter the password for the application server administrator. Password Enter the password for the application server administrator user ID. 3. From the database administration panel, for DB2, enter the following information and then click Next.

262

Installation Guide:

Remote user ID Enter a user ID in order to access the system hosting the database. The remote user ID must be able to access the server using the remote access protocol enabled on that system. Remote password Enter a password for the remote user ID. Instance administrator user ID Enter the database instance administrator user ID that you input during the installation. Instance administrator password Enter the password for the database instance administrator user ID. For Oracle databases, you can supply the credentials for the Administrator user ID and the Oracle software owner ID. For Microsoft SQL Server databases, you can supply the SQL Server administrator user ID and password. 4. Review the components that are listed in the uninstall summary panel, and then click Uninstall. 5. After the uninstall process has completed, specify whether you want to restart the computer now or later, and click Done to exit the program. 6. Check to ensure the uninstall program removed the Maximo Asset Management installation directory, for example, c:\ibm\smp. If the Maximo Asset Management installation failed early in the process, the Maximo Asset Management uninstall program might not remove the Maximo Asset Management installation directory. If this directory still exists after you have completed the uninstall process, you will have to remove it manually before you proceed to the reinstallation process. What to do next

Uninstalling a manually configured deployment


Use the information provided in this section to uninstall a Maximo Asset Management deployment that was deployed with middleware that you configured manually. Uninstalling a manually configured Maximo Asset Management deployment consists of running the Maximo Asset Management uninstallation program, and then manually dropping and recreating the database you intend to use with the reinstall process. Running the product uninstall program for manually configured middleware: Running the Maximo Asset Management uninstall program will revert the administrative system and middleware servers back to a state where you can rerun the Maximo Asset Management installation program. Before you begin Ensure all applicable services are running and all middleware servers are accessible. The Maximo Asset Management uninstall program must be able to access the database used with Maximo Asset Management to fetch installation properties and configuration data. If the Maximo Asset Management uninstall program cannot access the database because it is unavailable, corrupt, or otherwise inaccessible,
Chapter 9. Troubleshooting

263

then the Maximo Asset Management uninstall program will remove files from the administrative workstation and inform you that some manual recovery might be required before another Maximo Asset Management installation can be successful. The uninstall program will use values entered during the initial installation during uninstall. If credentials used to access the database and J2EE server are still valid, you will not be prompted to input them again. If the uninstall program is unable to validate these credentials, for example, if you updated passwords since the original installation, you will be prompted to supply the updated information. About this task Procedure 1. To run the Maximo Asset Management uninstall program, from the administrative workstation, open a command prompt and issue the following command: Windows
<MAM_HOME>\_uninstall\uninstall.bat

2. From the Introduction panel, read the introductory information and then click Next. 3. From the application server information panel, enter the following information and then click Next. User ID Enter the password for the application server administrator. Password Enter the password for the application server administrator user ID. 4. Review the components that are listed in the uninstall summary panel, and then click Uninstall. 5. After the uninstall process has completed, click Done to exit the program. 6. Check to ensure the uninstall program removed the Maximo Asset Management installation directory, for example, c:\ibm\smp. If the Maximo Asset Management installation failed early in the process, the Maximo Asset Management uninstall program might not remove the Maximo Asset Management installation directory. If this directory still exists after you have completed the uninstall process, you will have to remove it manually before you proceed to the reinstallation process. What to do next You can now proceed with recovery of your manually configured database. Database configuration recovery: Database objects that you created before running the Maximo Asset Management installation program must be deleted after a failed installation before you can rerun the Maximo Asset Management installation program again. Before rerunning the Maximo Asset Management installation program, you must drop the Maximo Asset Management database and recreate it. Restoring the DB2 database server:

264

Installation Guide:

In order to rerun the Maximo Asset Management installation program, you must first restore the DB2 database server to the same state as before Maximo Asset Management was installed. Before you begin Ensure that the MXServer application server on the WebSphere Application Server is stopped before dropping the database. About this task Restoring the DB2 database server to the same state as before Maximo Asset Management was installed, requires you to drop the Maximo Asset Management database that you manually created and then recreate it before rerunning the Maximo Asset Management installation program. To restore the Maximo Asset Management database, complete the following steps: Procedure 1. Log onto the system hosting the DB2 server. 2. Start a DB2 command session or run db2cmd from the command prompt. 3. First list and then force all applications connected to the database to close using the following commands: a. To list applications, type this command:
db2 list applications

You might see output similar to the following sample output:


Auth Id -------CTGINST1 CTGINST1 CTGINST1 Application Name ----------db2taskd db2stmm db2bp Appl. Handle ------507 506 504 Application Id DB Name ---------------------------- ------*LOCAL.DB2.071113150237 MAXDB71 *LOCAL.DB2.071113150236 MAXDB71 *LOCAL.ctginst1.071113150234 MAXDB71 # of Agents ----1 1 1

b. If any connections exist, close the connect application using a command similar to the following sample command:
db2 force application '( 507,506,504 )'

4. Drop the Maximo Asset Management database (MAXDB71, by default):


db2 drop database MAXDB71

5. Manually recreate the maxdb71 database. Refer to Manually configuring DB2 9.x on page 125 or Manually configuring DB2 8.2 on page 130 for more information. Restoring the Oracle database: In order to rerun the Maximo Asset Management installation program, you must first restore the Oracle database server to the same state as before Maximo Asset Management was installed. Before you begin Ensure that the MXServer application server on WebSphere Application Server Network Deployment is stopped before deleting the database.

Chapter 9. Troubleshooting

265

About this task Restoring the Oracle database server to the same state as before Maximo Asset Management was installed, requires you to drop the Maximo Asset Management database schema user before rerunning the Maximo Asset Management installation program. To restore the Maximo Asset Management database, complete the following steps: Procedure 1. Log into the Oracle database server as the Oracle software owner. 2. Log into the Oracle instance using SQLPlus as a DBA user: Note that the Oracle SID for a clean install is ctginst1. If you are using an existing Oracle instance with Maximo Asset Management, use the Oracle SID associated with the existing instance. AIX, Linux, HP-UX, Solaris a. Set the environment variable from the command line:
ORACLE_SID=<your sid> export ORACLE_SID

b. Invoke SQLPlus from the command line:


sqlplus /nolog

c. Log into SQLPlus as a DBA user:


connect sys/<sys password> as sysdba

Windows a. Set the environment variable from the command line:


set ORACLE_SID=<your sid>

b. Invoke SQLPlus from the command line:


sqlplus /nolog

c. Log into SQLPlus as a DBA user:


connect sys/<sys password> as sysdba

3. Delete the Maximo Asset Management database user (maximo, by default) using an SQL command similar to the following sample command:
drop user maximo cascade;

Do not disconnect from the database. If you receive an error when issuing this command that you cannot drop a currently connected user, issue the following SQL commands and then try the SQL drop command again:
shutdown immediate; startup;

4. Manually recreate the database. Refer to Manually configuring Oracle 10g on page 136 or Manually configuring Oracle9i Rel2 on page 139 for more information. Restoring the Microsoft SQL Server database: In order to rerun the Maximo Asset Management installation program, you must first restore the Microsoft SQL Server database server to the same state as before Maximo Asset Management was installed.

266

Installation Guide:

Before you begin Ensure that the MXServer application server on WebSphere Application Server Network Deployment is stopped before deleting the database. About this task Restoring the Microsoft SQL Server database server to the same state as before Maximo Asset Management was installed, requires you to drop the Maximo Asset Management database that you manually created and then recreate it before rerunning the Maximo Asset Management installation program. To restore the Maximo Asset Management database, complete the following steps: Procedure 1. Open the Microsoft SQL Server Management Studio. 2. Log into the instance of Microsoft SQL Server that is used by Maximo Asset Management install using the sa user ID, and then click Connect. 3. To delete the database, expand the instance tree down to the databases category, right-click the database name you created during installation (MAXDB71 for example), and then click Delete. 4. In the Delete Object window, select Delete backup and restore history information for databases and Close existing connections, and then click OK. 5. Manually recreate the maxdb71 database. Refer to Manually configuring SQL Server on page 144 more information.

Installation properties
Installation properties are recorded in properties files during a deployment and are used as input by future install-related actions. Listed in the table below are installation properties that are found in the install.properties and maximo.properties files. If there are any updates made to installation properties, for example, a password or host name change, between the time of the initial product deployment and a subsequent installation action, such as applying a fix pack or performing an upgrade, the corresponding properties must be updated in these files. Refer to Updating environment data on page 280 for more information.
Table 21. Installation properties Category MAXIMO Properties Property Maximo.InstallLocation Definition Install location of the maximo directory. For example, C:\\IBM\\SMP\\maximo mxe.db.user Database user that the server uses to attach to the database server. For example, maximo mxe.db.schemaowner Owner of the database schema. For example, maximo. This value must be dbo for Microsoft SQL Server.

Chapter 9. Troubleshooting

267

Table 21. Installation properties (continued) Category Property mxe.db.password mail.smtp.host mxe.workflow.admin mxe.adminEmail mxe.name Definition Password for the database user name. SMTP host server. E-mail account of the workflow administrator. Valid E-mail address used by workflows to communicate with workflow participants. Name to bind the MXServer server object to in the RMI registry. For example, mxserver. mxe.hostname mxe.rmi.port Name of the machine and port hosting MXServer. RMI communication port. If set at zero, RMI uses any available port. You can select another available port number. The port number used to bind RMI/JRMP communications. For example, 13400. The RMI registry is started by the first instance of the maximo application to run. A WebSphere Application Server Network Deployment environment could have multiple instances of the product application running at one time. This registry coordinates these instances. There is a single central RMI registry server. This is the port available for the other application instances to communicate with the central server. mxe.allowLocalObjects Set to true in production environments, to improve system performance. Set to false for development work, or for custom applications. The default is false. mxe.useAppServerSecurity Indicates whether to use LDAP or native authentication. Setting this value to 1 indicates you are using LDAP for security. By default, the multi-language metadata cache loads one object at a time. Set this flag to 1 to load all objects simultaneously for one language. The product enabler (license key) is used during installation. If the product enabler changes this value must be updated. The administrative user. Used by the server for administrative tasks and to run cron tasks. This user must have access to all Sites in the system.

mxe.registry.port

mxe.MLCacheLazyLoad

mxe.UserLicenseKey

mxe.adminuserid

268

Installation Guide:

Table 21. Installation properties (continued) Category Property mxe.adminuserloginid Definition Defines the default login user ID for the product application. The default value is maxadmin. mxe.adminPasswd mxe.system.reguser The password for the mxe.adminuserloginid user.. Self registration user. This user is responsible for the process by which users can cerate their own accounts. The default value is maxreg. mxe.system.regpassword User registration login password. This is the password for the user listed for mxe.system.reguser. The character set for e-mail notifications sent from the product. When this property is defined, it is the charset that is used to encode the subject and message when an e-mail notification is sent. mxe.reorder.previewtimeout The reorder preview time out period (in minutes), which should be similar to the Web server session time out. The default value is 30 minutes. mxe.security.provider The security provider is obtained from the policy file, which is normally com.sun.crypto.provider.SunJCE. To use a different provider, you can specify a value for this parameter. mxe.mbocount Displays the number of business objects created by the server. The default is 1. You can change the value to 0 which will disable this feature. mxe.esig.defaultuserid Set this flag to true if you want the Esignature login dialog to default to the login ID. The default value is true. maximo.min.required.db.version Defines what the minimum level of database is required for an upgrade. An example value would be 7100. Property used by the application to determine if property files are encrypted. This value is set to true if the file is encrypted.

mxe.email.charset

mxe.encrypted

Chapter 9. Troubleshooting

269

Table 21. Installation properties (continued) Category Property mxe.LDAPUserMgmt Definition Indicates whether LDAP owns user management when mxe.userAppServerSecurity = 1. The default value is 1. CCMDB specific Properties CCMDB.InstallLocation Product install location. For example, C:\\IBM\\SMP. CCMDB.JREInstallLocation JRE install location. For example, C:\\IBM\\SMP\\JRE. CCMDB.SDKInstallLocation SDK install location. For example, C:\\IBM\\SMP\\SDK. CCMDB.PMP CCMDB.Locale Unused property.. The locale setting of the administrative workstation system. For example, en. CCMDB.BaseLanguage Base language that was set for the product. For example, en. CCMDB.AdditionalLanguages CCMDB.DeploySampleData Additional languages installed for the product. Binary value that determines whether sample data is to be loaded during the installation. For example, false. CCMDB.UserShortcuts Location of the shortcut menu items for the process solution installer and the product console. Type of installation, which includes fix pack, upgrade, or new installation. For example, Install. CCMDB.DeployEar Binary value that indicates if EAR files will be deployed during the installation based upon choices the user made in the installation program wizard. For example, true. Base Services specific Properties BASE.DeployOptionalContent Binary value that indicates if optional content will be deployed during the installation based upon choices the user made in the installation program wizard. For example, true.

CCMDB.InstallType

270

Installation Guide:

Table 21. Installation properties (continued) Category Property BASE.DeployOptionalContentSet Definition Indicates whether or not you selected to deploy optional content during the initial upgrade. This value, once set, is a fixed value and cannot be changed. This value will be used for all future upgrades and fix packs. The previous version of base services that was installed. WebSphere Application Server Network Deployment thin client install location. For example, C:\\IBM\\SMP\\WASClient. WAS.SOAPConnectorPort SOAP port of the WebSphere Application Server Network Deployment deployment manager. For example, 8879. WAS.ThinClientFullyAutomatedConfig Binary value that indicates if the installation program will download the keystore from the WebSphere Application Server Network Deployment deployment manager. If this value is set to false, the user will have to copy it manually. WAS.ThinClientLocalKeystore Location of the keystore file. For example, C:\\ibm\\WebSphere\\ AppServer\\profiles\\ctgDmgr02\\etc\\ trust.p12. WAS.Scripts.Location Location of scripts used by the installation program. For example, C:\\IBM\\SMP WebSphere Application WAS.RMIConnectorPort Server Network Deployment RMI port RMI port on the WebSphere Application Server Network Deployment deployment manager which is used if SOAP is not being used. Needed when using IPV6 WebSphere Application WAS.AutomateConfig Server Network Deployment specific properties Binary value that indicates if WebSphere Application Server Network Deployment will be automatically configured by the installation program. A value of false indicates that the user manually configured the WebSphere Application Server Network Deployment server before running the installation program. WAS.InstallLocation Installation location for WebSphere Application Server Network Deployment. For example, C:\\IBM\\WebSphere\\ AppServer

BASE.VersionUpgradingFrom WAS Thin Client specific Properties WAS.ThinClientInstallLocation

Chapter 9. Troubleshooting

271

Table 21. Installation properties (continued) Category Property WAS.DeploymentManagerHostName Definition Host name of the WebSphere Application Server Network Deployment deployment manager. WebSphere Application Server Network Deployment CELL name. For example, ctgCell01 WAS.DeploymentManagerProfileName WebSphere Application Server Network Deployment profile name. For example, ctgDmgr01 WAS.DeploymentManagerProfileRoot Location of the WebSphere Application Server Network Deployment profile. For example, C:/IBM/WebSphere/AppServer/ profiles/ctgDmgr01 WAS.ServerProfileName WebSphere Application Server Network Deployment application server profile name. For example, ctgAppSrv01 WAS.NodeName WebSphere Application Server Network Deployment node name. For example, ctgNode01 WAS.ApplicationServerName WebSphere Application Server Network Deployment application server name. For example, MXServer WAS.ClusterName WebSphere Application Server Network Deployment cluster name. For example, MAXIMOCLUSTER. This property is designated for future use. WAS.AdminUserName WebSphere Application Server Network Deployment administrator name. For example, wasadmin WAS.AdminPassword WAS.RemoteAccessUserName WebSphere Application Server Network Deployment administrator password. WebSphere Application Server Network Deployment deployment manager system user ID used for tasks such as copying ISC WAR files and fetching the keystore. WebSphere Application Server Network Deployment deployment manager system user password. Name of the WebSphere Application Server Network Deployment virtual host. For example, maximo_host.

WAS.CellName

WAS.RemoteAccessPassword

WAS.VirtualHost

272

Installation Guide:

Table 21. Installation properties (continued) Category Property WAS.VirtualHostPort Definition Port for virtual host for listening for HTTP server. For example, 80. WAS.WebServerHostName WAS.AppServerJvmHeapMin Host name where the HTTP server is located. Minimum heap size setting for the application server JVM. For example, 512. WAS.AppServerJvmHeapMax Maximum heap size setting for the application server JVM. For example, 1024. WAS.SibName Name of the service integration bus. For example, intjmsbus. WAS.SibHiMsg Service integration bus high message count. For example, 500000. WAS.WebServerName Name of the WebSphere Application Server Network Deployment web server. Used to manage HTTP server from within WebSphere Application Server Network Deployment. For example, webserver1. WAS.SibPersistMessages Binary value that indicates if service integration bus messages will be persisted in either the product database or a local derby database. A value of true indicates that the messages will be persisted. WAS.SibDSName Service integration bus data source name created to access the service integration bus persistence store. For example, intjmsds. WAS.SibDBType Database type where the service integration bus messages are being stored. For example, DB2. WAS.SibDBName WAS.SibDBInstance WAS.SibDBServerName Name of the service integration bus messages database. Instance name of the service integration bus database. Server name of the system hosting the service integration bus message database.

Chapter 9. Troubleshooting

273

Table 21. Installation properties (continued) Category Property WAS.SibDBServerPort Definition Database server port for the database containing the service integration bus messages. For example, 50005. WAS.SibDBUserName User ID used to access the persistence datastore database for service integration bus messages. Password for user ID named in WAS.SibDBUserName. Where the service integration bus database is installed. For example, C:\Program Files\IBM\SQLLIB. WAS.SibDbFencedUser Fenced user ID for the service integration bus database. This property is only used for databases hosted on UNIX systems. For example, db2fenc1. WAS.SibDbInstanceAdminUser WAS.SibDbInstanceAdminPassword WAS.SibDbRemoteAccessUser Instance owner for the service integration bus database. Password for the instance owner of the service integration bus database. Database server system user used to configure the service integration bus remotely. Password for user ID named in WAS.SibDbRemoteAccessUser. Unused property. Binary value that indicates if the installation program will create users and directories. For example, true. WAS.VmmUserRDN LDAP tree where users are stored. For example, ou=users,ou=SWG,o=IBM, c=US. WAS.VmmGroupRDN LDAP tree where groups are stored. For example, ou=groups,ou=SWG,o=IBM, c=US. LDAP Server specific Properties LDAP.AutomateConfig Binary value that indicates whether the installation program will automatically configure the directory server. For example, true. LDAP.Vendor LDAP.ServerHostName LDAP.AdminDN The type of LDAP repository. Host name of the LDAP system host. Administrator distinguished name. For example, cn=root.

WAS.SibDBUserPass WAS.SibDBInstallDir

WAS.SibDbRemoteAccessPassword WAS.UseDefaultVmmSchema WAS.VmmFullyAutomatedConfig

274

Installation Guide:

Table 21. Installation properties (continued) Category Property LDAP.AdminPassword LDAP.ServerPort Definition Password for user ID named in LDAP.AdminDN. Port listening for connection requests. For example, 389. LDAP.InstallLocation Install location of the directory server. For example, C:\Program Files\IBM\LDAP\V6.2. Database specific Properties Database.AutomateConfig Binary value that indicates whether the installation program will automatically configure the database. For example, true. Database.Vendor Database type. For example, DB2. Database.RemoteAccessUserName Database.RemoteAccessPassword mxe.db.driver Database server system user ID that is used for configure the database remotely. Password for user ID named in Database.RemoteAccessUserName. Javaclass name of the JDBC driver. For example, com.ibm.db2.jcc.DB2Driver, oracle.jdbc.OracleDriver, or com.inet.tds.TdsDriver. mxe.db.url JDBC URL of the database.

For example, jdbc:db2:// mymachine.mydomain.com:50005/maxdb71, jdbc:inetdae7a:mymachine.mydomain.com:1433?database=max or jdbc:oracle:thin:@mymachine.mydomain.com:1521:ctginst1. mxe.db.initialConnections Number of database connections to create when the application server is started. For example, 8. mxe.db.maxFreeConnections Maximum number of free database connections available in the connection pool. For example, 8. mxe.db.minFreeConnections Minimum number of free database connections needed in the connection pool in order for more connections to be allocated. For example, 5. mxe.db.newConnectionCount Number of new connections to be created when the minimum free connections are available in the connection pool. For example, 3.

Chapter 9. Troubleshooting

275

Table 21. Installation properties (continued) Category Property mxe.db.transaction_isolation Definition The system install sets the value to: TRANSACTION_READ_COMMITTED. This value cannot be modified. mxe.db.format.upper This value defines the database uppercase function for the system. This value cannot be modified. mxe.db.autocommit This value sets the autocommit mode used for the Write connections. Can be either true or false. The default is false. This value cannot be modified. mxe.db.systemdateformat System date format. For IBM DB2, the value is current timestamp. For Oracle, the value is sysdate, and the default value cannot be edited. For SQL Server, the value is getdate(). mxe.db.format.nullvalue The database-specific format of the nullvalue function. For IBM DB2 the value is COALESCE, and the default value cannot be edited. The value for Oracle is NVL, and the default value cannot be edited. The value for SQL Server must be set to ISNULL. mxe.db.sqlserverPrefetchRows Setting to reduce lock contention. Optimal setting is 200 rows. Setting a value larger than 500 can degrade performance. The default value is 0. This value is only valid for SQL Server. mxe.db.logSQLTimeLimit The system logs the SQL statements that take longer than the specified time limit. The time is measured in milliseconds (thousandths of a second). The default value is 1000 milliseconds. To disable, edit the file to read: mxe.db.logSQLTimeLimit=0.

276

Installation Guide:

Table 21. Installation properties (continued) Category Property mxe.db.fetchResultLogLimit Definition When this setting is enabled, a stack trace is printed in the log for every business object set that fetches beyond the set limit of rows. The stack trace log is also repeated for every multiple of such fetches. The default is 200 rows. To disable, edit the file to read: mxe.db.fetchResultLogLimit=0. Oracle DB Properties Database.Oracle.InstanceName Database.Oracle.SoftwareOwner Oracle instance name. Owner of the software installation. For example, oracle. Database.Oracle.SoftwareOwnerPassword Database.Oracle.InstallLocation Database.Oracle.DataTablespaceName Password for the user ID listed in Database.Oracle.SoftwareOwner. Oracle installation location. For example, /opt/app/oracle/product/10.2.0/db_1. Oracle tablespace name for the product database. For example, maxdata. Database.Oracle.InstanceLocation Oracle instance location. For example, /opt/app/oracle/ product/10.2.0/db_1. Database.Oracle.DataTablespaceLocation Database.Oracle.DataTablespaceSize Location of Oracle database tablespace. Tablespace size, measured in Mb. For example, 1000. Database.Oracle.DataTablespaceMaxSize Maximum size of the tablespace, measured in Mb. For example, 8000. Database.Oracle.TempTablespaceName Temporary tablespace name. For example, maxtemp. Database.Oracle.TempTablespaceLocation Database.Oracle.TempTablespaceSize Location of temporary tablespace. Temporary tablespace size, measured in Mb. For example, 1000. Database.Oracle.TempTablespaceMaxSize Maximum size of the temporary tablespace, measured in Mb. For example, 8000. Database.Oracle.IndexTablespaceName Index tablespace name. For example, maxdata. Database.Oracle.IndexTablespaceLocation Database.Oracle.IndexTablespaceSize Location of index tablespace. Index tablespace size, measured in Mb. For example, 1000.

Chapter 9. Troubleshooting

277

Table 21. Installation properties (continued) Category Property Database.Oracle.IndexTablespaceMaxSize Definition Maximum size of the index tablespace, measured in Mb. For example, 8000. mxe.db.schemaowner Database.Oracle.SchemaPassword Database.Oracle.ServerHostName Database.Oracle.ServerPort Owner of the database schema. Password for user listed in mxe.db.schemaowner. Host name of the Oracle server. Port number used by Oracle. For example, 1521. Database.DBAUserName Oracle DBA user name. For example, sys. Database.DBAPassword DB2 DB Properties mxe.db.schemaowner Database.DB2.ServerHostName Password for user ID listed for Database.DBAUserName. Owner of the database schema. Hostname of the DB2 server. For example, mymachine.mydomain.com. Database.DB2.ServerPort Database server port. For example, 50005. Database.DB2.InstanceName Name of the database instance. For example, ctginst1. Database.DB2.DatabaseName Name of the database. For example, maxdb71. Database.DB2.InstallLocation Install location of the database. For example, /opt/IBM/db2/V9.5 Database.DB2.LogFileSize Set the size for transaction logs. For example, 4096 Database.DB2.AppCtlHeapSize Application control heap size. For example, 1024 Database.DB2.ApplHeapSize Application heap size. For example, 1024 Database.DB2.LockListSize Size allocated to the lock list. For example, 30000 Database.DB2.LogSecond Number of secondary log files allowed. For example, 4 Database.DB2.ServiceUser Database.DB2.ServicePassword User ID used to autostart. Password for Database.DB2.ServiceUser.

278

Installation Guide:

Table 21. Installation properties (continued) Category Property Database.DB2.PageSize Definition Page size setting. Measured in kb. For example, 32 Database.DB2.ExtentSize Number of pages per extent (group of pages). For example, 32 Database.DB2.FencedUser System user used as the fenced user ID for DB2 on UNIX systems. For example, db2fenc1. Database.DB2.AuthType Method DB2 uses to authenticate users. For example, server. Database.DB2.DataTablespaceName DB2 tablespace name for the product database. For example, maxdata. Database.DB2.BufferPoolName DB2 buffer pool name. For example, MAXBUFPOOL. Database.DB2.BufferPoolLocation Database.DB2.BufferPoolSize Location of the buffer pool. Size of the buffer pool. For example, 32 Database.DB2.DataTablespaceLocation Database.DB2.DataTablespaceSize Location of DB2 database tablespace. Tablespace size, measured in Mb. For example, 1000. Database.DB2.DataTablespaceMaxSize Maximum size of the tablespace, measured in Mb. For example, 8000. Database.DB2.TempTablespaceName Temporary tablespace name. For example, maxtemp. Database.DB2.TempTablespaceLocation Database.DB2.TempTablespaceSize Location of temporary tablespace. Temporary tablespace size, measured in Mb. For example, 1000. Database.DB2.TempTablespaceMaxSize Maximum size of the tablespace, measured in Mb. For example, 8000. Database.DB2.IndexTablespaceName Index tablespace name. For example, maxdata. Database.DB2.IndexTablespaceLocation Database.DB2.IndexTablespaceSize Location of index tablespace. Temporary tablespace size, measured in Mb. For example, 1000.

Chapter 9. Troubleshooting

279

Table 21. Installation properties (continued) Category Property Database.DB2.IndexTablespaceMaxSize Definition Maximum size of the index tablespace, measured in Mb. For example, 8000. Database.DB2.InstanceAdminUserName Database.DB2.InstanceAdminPassword SQL Server DB Properties mxe.db.schemaowner Administrative user or the database instance. Password for the user ID specified for Database.DB2.InstanceAdminUserName Owner of the database schema. This value must be dbo for Microsoft SQL Server. Database.SQL.DatabaseName Name of the database. For example, maxdb71. Database.SQL.InstallLocation SQL Server installation location. For example,C:\\Program Files\\Microsoft SQL Server\\90. Location for database data file A way to specify the name of the data file used for the database. For example, maxdb71_dat. Maximum size for data file for database. Initial size for data file for database. A way to specify the name for the database transaction log file. For example, maxdb71_log. SQLServer Database transaction log file size. Database logical name file group. For example, PRIMARY. Host name of the database server. For example, myhost.mydomain.com. Database server port. For example, 1433. Administrative user for the SQL Server instance. used during install for creating database, creating database user, and modifying the database. Administrative users password. Location of the deployment engine. For example, C:\\Program Files (x86)\\IBM\\Common\\acsi. Indicates which application server was chosen during installation. For example, WebSphere.

Database.SQL.DataFileLocation Database.SQL.DataFileName

Database.SQL.DataFileMaxSize Database.SQL.DataFileSize Database.SQL.LogFileName

Database.SQL.LogFileSize Database.SQL.DataFilegroupName Database.SQL.ServerHostName Database.SQL.ServerPort Database.SQL.InstanceAdminUserName

Database.SQL.InstanceAdminPassword ADE (DE) Properties DE.InstalllLocation

Application Server Type Properties

ApplicationServer.Vendor

Updating environment data


When you install a fix pack or otherwise upgrade an existing ISM product, the installation program uses values recorded from the previous deployment. These values are stored on the administrative system in the install.properties and maximo.properties files. If you have made any environmental changes to any of

280

Installation Guide:

the systems used for the original deployment, such as changing a host name or updating a password, for example, they must be recorded in the install.properties and maximo.properties files.

Before you begin


As previously stated, when the product installation program is run for an upgrade task, it will attempt to use values found in the install.properties and maximo.properties files to complete the upgrade. During the upgrade operation, if you have not updated the user name or password for a system used in the previous deployment, the installation program will use the credentials found in the properties files, and, pending successful use of these credentials, you will not be prompted to provide them again. If the installation program is unsuccessful in its attempt to log into a system using the credentials found in the properties files, you will be prompted to supply the correct information. These values will then be written to the appropriate property file. This method of updating credential information in property files has one exception. Database connection and credential information must always be current before you attempt an upgrade operation. Database connection and credential information is stored in the maximo.properties file. Any changes to this information from the time of the original deployment must be manually recorded in the maximo.properties file before you upgrade.

About this task Procedure


1. Complete the following steps to update database properties within the maximo.properties file: a. Change directory to <Product_Home>\maximo\applications\maximo\ properties\ b. Make a backup of the maximo.properties file. c. Delete the maximo.properties file. d. Change directory to <Product_Home>\etc e. Make a backup of the maximo.properties_orig found in the directory. This backup should be a permanent backup that can be copied from when you need to update properties in the future. f. Rename the unencrypted file named maximo.properties_orig to maximo.properties g. Copy the maximo.properties file to <Product_Home>\maximo\applications\ maximo\properties\ h. Edit the maximo.properties file and update the credential or connection information for the database server. i. Save the file. j. Run the encryptproperties.bat file located in <Product_Home>\maximo\ tools\maximo\ directory against the file to encrypt it. 2. Complete the following steps to update properties within the install.properties file: The install.properties file contains the majority of properties used by the installation program, including non-connection related properties for the database. These values must be up to date before you apply a fix pack or other upgrade operation. If these values have changed from the previous deployment, you must first manually update them. a. Change directory to <Product_Home>\etc\
Chapter 9. Troubleshooting

281

b. Edit the install.properties file and make updates. Do not make changes to encrypted properties (prefixed by [enc]). You will be prompted for updated values during the update operation. These values will then be written to the install.properties file. c. Save the file. There is one important exception to this procedure. When changing the value of the WebSphere Application Server Network Deployment host name (WAS.DeploymentManagerHostName), in addition to updating this property value in the install.properties file, you must also update a property for the WebSphere Application Server Network Deployment thin client in the thinwasadmin.bat file and then run that file. 3. To update the WebSphere Application Server Network Deployment host name that was used in the previous deployment, complete the following steps: a. Update the WAS.DeploymentManagerHostName value in the install.properties file, as described in the previous procedure. b. Edit the C:\IBM\SMP\WASClient\thinwasadmin.bat file. c. Update the following line of the file with the new, fully-qualified, host name of the WebSphere Application Server Network Deployment server.
set wsadminHost=-Dcom.ibm.ws.scripting.host=<fully-qualified host name>

d. Run thinwasadmin.
thinwsadmin.bat -username <domain manager user name> -password <password>

e. When prompted, indicate that you do want to download the truststore file.

Results
After you have completed these updates, you will be able to upgrade, install a fix pack, or install another ISM product using the corrected values.

282

Installation Guide:

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 user's 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 - 2010

283

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 IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's 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

284

Installation Guide:

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

285

286

Installation Guide:

Index Numerics
220829 237 middleware 51 Middleware 49 auto-configuration 7 installer logs 63, 88 manual configuration 7 reusing 84 starting on UNIX 257 starting on Windows 255 MSAD LDAPSYNC 217

A
access collection 15 administrative workstation 5 Architecture Maximo Asset Management 1

D
Database server manual configuration 125 DB2 manual configuration, 8.2 130, 140 manual configuration, 9.x 125 Deployment environments clustered environment 3 distributed environment 3 stand-alone environment 3

O
Oracle manual configuration, 10g 136 manual configuration, 9i 139

P
Planning Maximo Asset Management Preparation Maximo Asset Management installation 19 prerequisite 51 Prerequisites procedures 42, 43 Process solution packages before installing 203 installation logs 205 installing 204 overview 203 3

I
Installation language pack 201 Maximo Asset Management 65, 182 middleware installer logs 63, 88 middleware installer workspace 49 overview 44 post installation tasks 209, 210, 211, 212, 214, 215 process solution package 203 roadmap 44 installer workspace 49 installing prerequisite software products 51

R
role 15

S J
J2EE server manual configuration post installation 179 178 security group 15

L
Language pack installing 201 overview 201 Launchpad 44 LDAPSYNC 217

M
MEA Configuring JMS Media Installation 19 180

Copyright IBM Corp. 2007 - 2010

287

288

Installation Guide:

Printed in USA

Vous aimerez peut-être aussi