IBM MaximoAsset Management Version 7 Release 5€¦ · Chapter 1. Installation overview Installing IBM ®Maximo Asset Management requires system administrator rights and privileges

IBM Maximo Asset ManagementVersion 7 Release 5

Installation Guide(IBM WebSphere)

NoteBefore using this information and the product it supports, read the information in Notices on page 331.

This edition applies to version 7, release 5, modification 0 of IBM Maximo Asset Management and to all subsequentreleases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 2007, 2011.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Installation overview . . . . 1Installing IBM Maximo Asset Management . . . . 1

System architecture and components . . . . . 1Product information . . . . . . . . . . . . 2

Prerequisite hardware and software. . . . . . 2Supported languages . . . . . . . . . . 3

Chapter 2. Planning to deploy . . . . . 5Deployment topologies . . . . . . . . . . . 5

Administrative workstation . . . . . . . . 6Single server deployment . . . . . . . . . 6Multiple server deployment . . . . . . . . 7

Planning for security . . . . . . . . . . . 8Planning for serviceability . . . . . . . . . . 9Planning language support . . . . . . . . . 10Installation program log information . . . . . . 10

Chapter 3. Preparing for installation . . 13Deployment scenario road maps . . . . . . . 13Installation options . . . . . . . . . . . . 14

Middleware configuration options . . . . . . 16Simple or custom option . . . . . . . . . 17

Software installation images . . . . . . . . . 17Before you begin . . . . . . . . . . . . 18

Programmatically verifying prerequisites . . . 19Checking port availability . . . . . . . . 23AIX tar command requirements . . . . . . 24AIX font requirements . . . . . . . . . . 24Enabling asynchronous I/O on AIX . . . . . 24Checking for required libraries on Linux . . . 25Configuring the JRE in Linux . . . . . . . 25Setting the ulimit . . . . . . . . . . . 26Setting the swap size . . . . . . . . . . 26Setting shared memory . . . . . . . . . 26Remote configuration enablement . . . . . . 27SSL Client Authentication Restrictions . . . . 28System password policy settings . . . . . . 29Backing up the Deployment Engine database . . 29

Launchpad . . . . . . . . . . . . . . 30Starting the launchpad . . . . . . . . . 30

Chapter 4. Deploying with automaticmiddleware configuration (Scenario 1) . 33Middleware installation . . . . . . . . . . 35

Middleware installation program workspace . . 36Middleware installation program middlewaredeployment plan overview . . . . . . . . 38Installing and configuring middleware using themiddleware installation program . . . . . . 38

Middleware installation program logs . . . 51Configuring IBM Tivoli Directory Server userand group strings . . . . . . . . . . 63Configuring SSL between Microsoft ActiveDirectory and WebSphere Application ServerNetwork Deployment . . . . . . . . . 64

Uninstalling middleware . . . . . . . . . 69Installation program overview . . . . . . . . 71

Simple install path values . . . . . . . . 72Running the installation program . . . . . . 74Create a maxdemo database during installation 90

Language deployment after database updatedeferral . . . . . . . . . . . . . . . . 90

Manually deploying languages after databaseupdate deferral . . . . . . . . . . . . 90

Chapter 5. Deploying automaticallyreusing existing middleware (Scenario2) . . . . . . . . . . . . . . . . . 93Reusing middleware using the middlewareinstallation program . . . . . . . . . . . 95

Configuring an existing DB2 with themiddleware installation program . . . . . . 97Verifying an existing IBM Tivoli Directory Serverusing the middleware installer . . . . . . . 98Preparing Microsoft Active Directory for reuse . 99

Installation program overview. . . . . . . . 101Simple install path values . . . . . . . . 103Running the installation program. . . . . . 105Create a maxdemo database during installation 120

Language deployment after database updatedeferral . . . . . . . . . . . . . . . 121


Chapter 6. Deploying manuallyreusing existing middleware (Scenario3) . . . . . . . . . . . . . . . . 123Maximo Asset Management installation withmanual middleware configuration . . . . . . 126

Manually configuring the database server . . . 126Manually configuring DB2 9.x . . . . . . 127Manually configuring Oracle 11g . . . . . 128Manually configuring Oracle 10g . . . . . 131Manually configuring Microsoft SQL Server 133

Manually configuring the directory server . . . 135Manually configuring IBM Tivoli DirectoryServer . . . . . . . . . . . . . . 136Manually configuring Microsoft ActiveDirectory . . . . . . . . . . . . . 140

Manually configuring the J2EE server . . . . 144Manually configuring WebSphere ApplicationServer Network Deployment . . . . . . 144

Running the installation program withoutmiddleware autoconfiguration. . . . . . . . 165Create a maxdemo database during installation . . 178Language deployment after database updatedeferral . . . . . . . . . . . . . . . 179


Copyright IBM Corp. 2007, 2011 iii

Chapter 7. Silent installation . . . . . 181Installing Maximo Asset Management silently . . 181Silent installation properties . . . . . . . . 183

Chapter 8. Programmatically verifyingthat the installation was successful . . 199

Chapter 9. Verifying the installationmanually . . . . . . . . . . . . . 205

Chapter 10. Post installation tasks 207Accessing product documentation . . . . . . 207Initial data configuration . . . . . . . . . 207

Signing in using a default user ID . . . . . 207Configuring SMTP . . . . . . . . . . 208Create currency codes . . . . . . . . . 209Create item and company sets . . . . . . . 209Create an organization . . . . . . . . . 209Create a general ledger account component . . 210Applying changes to the database . . . . . 210Create a general ledger account . . . . . . 211Update General Ledger Component TypeAuthorization . . . . . . . . . . . . 211Update Company-Related Accounts . . . . . 212Create default insert site. . . . . . . . . 212Create worktypes . . . . . . . . . . . 212Signing out and signing in . . . . . . . . 213

Synchronizing users and groups . . . . . . . 213Create a maxdemo database after installation. . . 214Understanding and configuring security . . . . 215

Chapter 11. Uninstalling the product 217Uninstalling an automatically configureddeployment . . . . . . . . . . . . . . 217

Running the product uninstall program forautomatically configured middleware . . . . 218

Uninstalling a manually configured deployment 219Running the product uninstall program formanually configured middleware. . . . . . 219Database configuration recovery . . . . . . 220

Restoring the DB2 database server . . . . 220Restoring the Oracle database . . . . . . 221Restoring the Microsoft SQL Server database 222

Uninstalling the product without the uninstallationprogram . . . . . . . . . . . . . . . 223

Uninstall program recovery tool . . . . . . 223Using the uninstallation program recoverytool. . . . . . . . . . . . . . . 223

Manual uninstallation . . . . . . . . . 227Recovering WebSphere Application Serverconfiguration . . . . . . . . . . . 227Removing files from the system . . . . . 230

Chapter 12. Starting and stoppingmiddleware . . . . . . . . . . . . 231Restarting middleware on Windows . . . . . . 231Restarting middleware on UNIX . . . . . . . 232Stopping middleware on Windows . . . . . . 233Stopping middleware on Linux and AIX . . . . 234

Chapter 13. Advanced installationtopics. . . . . . . . . . . . . . . 237Installation program tasks . . . . . . . . . 237Manual middleware configuration for expert users 241WebSphere Application Server NetworkDeployment management . . . . . . . . . 251

Starting the application server from thecommand line . . . . . . . . . . . . 251Starting the application server from theadministrative console . . . . . . . . . 251Securing the WebSphere Application ServerNetwork Deployment administrative console . . 253Configuring Windows services . . . . . . 254

Configuring the WebSphere ApplicationServer Network Deployment applicationserver to run as a Windows service . . . . 254

Changing the middleware installation programconfiguration parameters . . . . . . . . . 255Deploying EAR files . . . . . . . . . . . 256

Building EAR files. . . . . . . . . . . 256Manually uninstalling applications fromWebSphere Application Server NetworkDeployment . . . . . . . . . . . . . 257Manually installing applications into WebSphereApplication Server Network Deployment . . . 257

Performing multiple product installations on oneadministrative workstation . . . . . . . . . 258

Chapter 14. Middleware on Solarisand HP-UX . . . . . . . . . . . . 259Operating system preparation . . . . . . . . 259

Solaris . . . . . . . . . . . . . . . 259HP-UX . . . . . . . . . . . . . . 259

Installing the components . . . . . . . . . 260Installing DB2 . . . . . . . . . . . . 260Installing IBM Tivoli Directory Server on Solaris 262Installing WebSphere Application ServerNetwork Deployment . . . . . . . . . 263

Installing the WebSphere update installer . . 264Installing and configuring IBM HTTP Server 264Installing the WebSphere plug-in . . . . . 267

Configuring Virtual Member Manager on IBMWebSphere Application Server NetworkDeployment . . . . . . . . . . . . . . 269

Chapter 15. Backup and restoration 271Backing up the administrative workstation . . . 271Restoring the administrative workstation . . . . 272Installation properties . . . . . . . . . . 272

Updating environment data . . . . . . . 285

Chapter 16. Troubleshooting . . . . . 289Troubleshooting the middleware installer . . . . 289

Middleware installation programtroubleshooting feature . . . . . . . . . 289

Using the middleware installation programtroubleshooting feature . . . . . . . . 289

Segmentation fault . . . . . . . . . . 290Encountering error CTGIN9048E . . . . . . 291Encountering error CTGIN9042E . . . . . . 293

iv IBM Maximo Asset Management: Installation Guide (IBM WebSphere)

Encountering error ACUINI0044E . . . . . 294Incorrect db2admin password . . . . . . . 294Password expiration for db2admin . . . . . 296Improper configuration of DB2 or IBM TivoliDirectory Server . . . . . . . . . . . 296Incorrect idsccmdb user password . . . . . 299Incorrect service pack requirement for AIX . . 300Failure when system directories cannot berenamed . . . . . . . . . . . . . . 300Invalid DB2 password value . . . . . . . 302Recovering from DB2 installation failure on AIX 303Troubleshooting middleware uninstall . . . . 305

WebSphere Application Server NetworkDeployment uninstall fails after unsuccessfulbinding to LDAP directory . . . . . . . 305

Troubleshooting the product installation program 306General troubleshooting of the productinstallation program . . . . . . . . . . 306

Common deployment failures . . . . . . 311Troubleshooting-specific errors of the productinstallation program . . . . . . . . . . 319

WebSphere Application Server NetworkDeployment node agent reported as notrunning . . . . . . . . . . . . . 319

Troubleshooting the product uninstallationprogram . . . . . . . . . . . . . . 320

Error CTG00001 when performing anuninstall . . . . . . . . . . . . . 320

Appendix A. Planning worksheet forproduct installation . . . . . . . . . 321

Appendix B. Planning worksheets formiddleware installation . . . . . . . 323

Notices . . . . . . . . . . . . . . 331Trademarks . . . . . . . . . . . . . . 332

Index . . . . . . . . . . . . . . . 335

Contents v

vi IBM Maximo Asset Management: Installation Guide (IBM WebSphere)

Chapter 1. Installation overview

Installing IBM Maximo Asset Management requires system administrator rightsand privileges.

Use this information to plan the installation, prepare your environment, and installMaximo Asset Management by using a deployment scenario that fits yourrequirements.

Installing IBM Maximo Asset Management

System architecture and components

Maximo Asset Management requires multiple software servers that are referred toas middleware. The middleware components can run on one or more computers.The following diagram shows the components that are used in a typical MaximoAsset Management installation.

HTTP Server

AdministrativeWorkstation

DatabaseServer

ApplicationServer

DirectoryServer

End User withweb browser

JDBC

HTTP/HTTPS

A Maximo Asset Management installation has the following required components:

Database

The Maximo database stores all information about assets, such as theirconditions, their locations, and related records. You can store thisinformation on the IBM DB2 database that is provided in the productinstallation image, or you can use any of the other supported databases. Alist of supported databases is provided in the prerequisites topic in thechapter that helps you prepare for the installation.

Application serverThe application server manages the Maximo Asset Management JavaServerPages (JSPs), XML, and business logic components. Maximo AssetManagement uses a commercial Java 2 Enterprise Edition (J2EE)application server: either IBM WebSphere Application Server or OracleWebLogic Server.

Copyright IBM Corp. 2007, 2011 1

Administrative workstation

The administrative workstation is used to install Maximo AssetManagement. The administrative workstation must be installed on aMicrosoft Windows system. After the installation, use the administrativeworkstation to make updates or changes to the configuration.

Web browser

Users access the Maximo Asset Management applications by using a Webbrowser, connected over a company network or over the Internet.

In addition to the required components, you can use the following optionalcomponents with Maximo Asset Management:

HTTP serverYou can configure a separate, dedicated HTTP server to work with theJ2EE application server.

Directory serverYou can configure a directory server to provide identity management andauthentication for the J2EE server.

Product informationBefore you install Maximo Asset Management, review the product installationinformation.

Review the following information in the Quick Start download and in the IBMMaximo Asset Management Information Center.

Quick Start GuideProvides brief information to help you get started. The Quick Startdownload and the web information center contain copies of the Quick StartGuide in several languages.

Download documentDescribes how to download the product installation images if you do nothave a product DVD. For more information, see theIBM Maximo AssetManagement 7.5 Download Document (www.ibm.com/support/docview.wss?uid=swg24029458).

Product support siteThe IBM Software Support website (www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Maximo_Asset_Management) gives you accessto the latest fixes and technical notes.

Upgrade GuideFor information about upgrading to version 7.5, see the Upgrade Guide, IBMMaximo Products V7.1 to V7.5 on the Maximo Upgrade Resources website(www.ibm.com/support/docview.wss?rs=3214&uid=swg21266217).

Prerequisite hardware and softwareReview the prerequisite hardware and software and ensure that your environmentmeets the minimum standards before you perform the installation.

The Maximo Asset Management installation and middleware installation programsinstall and configure IBM products that make up the Maximo Asset Managementarchitecture. Previously installed IBM products can be configured to be part of theMaximo Asset Management system. These existing resources must meet minimum

2 IBM Maximo Asset Management: Installation Guide (IBM WebSphere)

http://www.ibm.com/support/docview.wss?uid=swg24029458http://www.ibm.com/support/docview.wss?uid=swg24029458http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Maximo_Asset_Managementhttp://www.ibm.com/support/docview.wss?rs=3214&uid=swg21266217

release level requirements. In some cases, the Maximo Asset Managementinstallation programs can configure previously deployed products from othervendors to be used with Maximo Asset Management.

For information about the hardware, software, and network requirements forMaximo Asset Management, see the Overview and Planning page on the MaximoAsset Management wiki (www.ibm.com/developerworks/wikis/display/maximo/Overview+and+Planning).

Prerequisites that are listed for non-IBM products were valid at the time ofpublication. For the most up-to-date information about non-IBM productprerequisites, see the product documentation for each individual product.

Supported languagesThis section describes the languages supported by Maximo Asset Management.

The following are the supported languages:v Arabicv Brazilian Portuguesev Croatianv Czechv Danishv Dutchv Englishv Finnishv Frenchv Germanv Hebrewv Hungarianv Italianv Japanesev Koreanv Norwegianv Polishv Russianv Simplified Chinesev Slovenianv Spanishv Swedishv Traditional Chinesev Turkish

Note: While Maximo Asset Management itself supports the Turkish language, theinstallation program does not support Turkish. Furthermore, the administrativeworkstation must not be set to the Turkish locale before or after installing MaximoAsset Management. After Maximo Asset Management has been installedsuccessfully, Turkish can be deployed as either the base or as an additional

Chapter 1. Installation overview 3

http://www.ibm.com/developerworks/wikis/display/maximo/Overview+and+Planning

language using the language pack installation program. The administrativeworkstation must remain set to a non-Turkish locale to accommodate futureproduct deployment actions.


Chapter 2. Planning to deploy

Planning for a Maximo Asset Management installation is critical to a successfuldeployment.

Use this information to understand and effectively deploy Maximo AssetManagement in your environment to suit your business needs. Once you arecomfortable with deployment concepts and planning material, you can useplanning worksheets found at the end of this information to record values you useduring the installation process.

Deployment topologiesDetermine the best deployment option for your environment and business needs.

From a topology standpoint, a Maximo Asset Management deployment consists ofan administrative system working with various middleware servers that have beenconfigured to work together as Maximo Asset Management components. AMaximo Asset Management deployment requires an administrative system, adatabase server, and a J2EE server. It might also include optional components. Forexample , depending on how you decide to configure security, an LDAP servercould optionally be configured as part of the deployment.

Maximo Asset Management works with a variety of database and J2EE serversoftware, all of which are listed in the hardware and software prerequisiteinformation. Maximo Asset Management includes a middleware installationprogram which you can use to install IBM middleware products such as IBM DB2

and IBM WebSphere Application Server Network Deployment. You can also reuseexisting resources in your environment. This might include supported versions ofboth IBM and non-IBM software middleware, including Microsoft SQL Server andOracle. A deployment can include a mix of new and existing servers consisting ofboth IBM and non-IBM middleware. Although IBM middleware software isincluded with Maximo Asset Management, you can deploy Maximo AssetManagement using non-IBM middleware exclusively.

There are two primary strategies to deploy Maximo Asset Management withinyour enterprise.

Single-serverThe single-server topology consists of loading all Maximo AssetManagement components, including all Maximo Asset Managementmiddleware, the Maximo Asset Management administrative system,process managers, and so on, onto one server. This deployment is typicalfor proof-of-concept purposes, as a demonstration, or as a learningenvironment. For managing enterprise assets and processes, you wouldtypically implement a multi-server topology.

Multi-serverThe multi-server topology consists of splitting Maximo Asset Managementcomponents across several different servers. This is beneficial as itoptimizes resource use and decreases the workload for each system. Thistype of deployment would be typical for production use within anenterprise.


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

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

Within IBM WebSphere Application Server Network Deployment, you cancreate deployment managers that provide centralized administration ofmanaged application server nodes and custom nodes as a single cell. IBMWebSphere Application Server Network Deployment provides basicclustering and caching support, including work balancing, automatedperformance optimization, and centralized management and monitoring.

A typical deployment life cycle might begin with a single-server topology thatwould progress with phases of demonstration, functional proof-of-concept, andtesting integration within the existing environment, and then gradually movetoward a pilot multi-server environment before finally implementing a productiondeployment within the enterprise.

Maximo Asset Management, like all ISM products, is built upon the processautomation engine. The process automation engine is a core set of functions usedby all ISM products. It serves as a common base for shared services andapplications inherited by all Maximo-based products. Process managers areworkflow-based applications that enable the creation of executable process flows.Process managers provide a user interface used to perform process procedures,gather information from various sources, interact with external tools, utilize andupdate information in a database, and provide information to monitoring, analysis,and reporting tools. In addition, process managers provide capabilities to trackexecution metrics and provide dashboards and reports that allow organizations toidentify bottlenecks and improve organizational productivity.

Administrative workstationYou install Maximo Asset Management from a Windows workstation designated asthe administrative workstation. This workstation is where the Maximo AssetManagement EAR files are built and later deployed to the application server.

For daily operations, the administrative workstation is not required after the initialinstallation and configuration of Maximo Asset Management. You use theadministrative workstation to install program fixes, product upgrades, newapplications, new process managers, and additional language packs. So, while nottypically used on a day-to-day basis, the administrative workstation is used in allphases of the product life cycle. This workstation is an important Maximo AssetManagement support component.

Single server deploymentA topology consisting of deploying IBM Maximo Asset Management on a singleserver is frequently used as a proof-of-concept, educational, or demonstrationconfiguration.

The following figure illustrates Maximo Asset Management deployed on a singlesystem that both serves as the Maximo Asset Management administrative system


and hosts middleware used with Maximo Asset Management.

When deploying everything onto a single server, if you choose the simpleinstallation path when prompted by the Maximo Asset Management installationprogram, Maximo Asset Management middleware is installed on the system usingdefault values that you cannot change. If you choose the custom installation path,you are able to supply your own values.Related concepts:Installation program overview on page 71The Maximo Asset Management installation program provides an interface forinstalling and deploying Maximo Asset Management, which includes the processautomation engine and process managers.

Multiple server deploymentThis section details deploying IBM Maximo Asset Management across multipleservers.

When deciding your deployment strategy, you must determine if it will includesystems already established in your network. Implementing Maximo AssetManagement by installing all new components using the Maximo AssetManagement middleware installation program can simplify the deployment. If youplan to reuse resources that already exist in your network, make adjustments toyour rollout plan to allow time for things such as bringing the existing resources toversion levels that are compatible with Maximo Asset Management.

Components for Maximo Asset Management: the database and LDAP servers, theJ2EE server and process managers, and the Maximo Asset Managementadministrative system are all installed on different servers. Maximo AssetManagement components can also be grouped logically and installed on the samesystem. In some instances, you will want to avoid the sharing of resources. Forexample, it is not recommended use the same DB2 database instance betweenMaximo Asset Management and IBM Tivoli Directory Server. During theinstallation, the database instance is restarted, which can disrupt the availability ofIBM Tivoli Directory Server to your enterprise. If you are using the automatedinstallation programs, separate instances are created for use by Maximo AssetManagement and IBM Tivoli Directory Server.

In a disparate environment, the collection of servers in this deployment can be amixture of Windows and UNIX servers.

Within WebSphere Application Server Network Deployment you can createdeployment managers that provide centralized administration of managedapplication servers nodes and custom nodes as a single cell. WebSphere

Figure 1. Single server deployment

Chapter 2. Planning to deploy 7

Application Server Network Deployment provides basic clustering and cachingsupport, including work balancing, automated performance optimization, andcentralized management and monitoring.

Planning for securityPlanning for security includes choosing a security option and deciding which userswork with each application in Maximo Asset Management.

Maximo Asset Management can be configured to manage users and theirmemberships in security groups.

When you install Maximo Asset Management, you must choose a method formanaging users and groups. This method applies to all products that you installtogether. If you are installing Maximo Asset Management with another productalready installed, the choice you made when installing the first product is used forMaximo Asset Management as well.

Choosing a security option

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

Choose one of these security options:

Database

Optional: LDAP

DB2OracleSQL Server

ITDSMicrosoft ActiveDirectory

J2EE Server

WebSphereWebLogic

Installnew orreuseexisting

Administrativeworkstation(Windows OS only)

Figure 2. Maximo Asset Management


Use application server and LDAP for authentication and user/groupmanagement

With this option, you create all your users and security groups in yourdirectory (LDAP) server. The information from the directory server isupdated in your Maximo database by using a cron task. With this option,you can create additional security groups and assign group membershipsin Maximo. All users must be added in the directory - adding users is notallowed in Maximo. Information entered in Maximo is never propagated toyour directory.

Use application server and LDAP for authentication onlyWith this option, you can create your users and groups in the directory(LDAP) server or in Maximo. The information from the directory server isupdated in your Maximo database by using a cron task. With this option,you can create additional users, security groups and assign groupmemberships in Maximo. Information entered in Maximo is neverpropagated to your directory.

Use Maximo internal authenticationWith this option, a directory server is not required. You create and manageusers and groups in the Users and Security Groups applications, separatelyfrom any corporate user data you might have.

Planning for serviceabilityServiceability refers to problem analysis from a central point, using data collectedfrom a wide range of sources.

Serviceability has changed from the method used in the previous version of theproduct. Serviceability is supported in Maximo Asset Management 7.5 through theuse of the IBM Support Assistant Workbench. The workbench is a free utility thatyou can configure to work with many different products.

Log files for the middleware installation program can be found in the workspacedirectory you defined when you ran the installation program. These files can beanalyzed by the Log Analyzer tool.

Log files for the Maximo Asset Management installation program are on theadministrative system in the following directories, where install_home equalsC:\IBM\SMP.

Table 1. Log file directories

Log file directory Details

install_home\logs

install_home\solutions\logs

install_home\maximo\tools\logs

install_home\CTG_DE

The ACULogger.properties anddeexlogger.properties files contain *fileDirkeys whose values provide the location forthe log files. The properties files can befound in

install_home\CTG_DE..

Log files are generated here if a problemoccurs during the validation sequence of theinstallation program.


After installation, during normal usage of Maximo Asset Management, it can beuseful 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 AssistantWorkbench, refer to the troubleshooting section of the Maximo Asset Managementinformation center.

Planning language supportPlan the language support in the product user interface.

Maximo Asset Management includes language support for languages supported byUTF-8 and UCS-2.

When deployed using Microsoft SQL Server, Maximo Asset Management does notsupport UTF-8. Language support is limited to those languages supported by thecurrent Windows system code page. Supported language set choices are either allLatin one languages and English or one double-byte character set language andEnglish.

Important: If you plan to add language support to Maximo Asset Management,you must use the Maximo Asset Management product installation program todefine the base language to use before you perform post installation steps. You canadd additional languages at a later date, but the base language must be set eitherduring or directly after the Maximo Asset Management installation.

Chapter 10, Post installation tasks, on page 207There are several post installation tasks required in order to complete theMaximo Asset Management deployment.

Installation program log informationLog files generated by the Maximo Asset Management installation program canprovide details on completed installation tasks and any installation errors thatmight occur.

Maximo Asset Management installation program log locations

Logs can be found in the following locations:v install_home\logsv install_home\solutions\logsv install_home\maximo\tools\logsv install_home\CTG_DE\logs

If you encounter an error during a validation task, logs can also be located withinthe home directory of the user that started the installation program. For example,C:\Documents and Settings\Administrator.

In addition, if you receive an error credited to the J2EE server, examine the logs inthe log directories for the deployment manager, node agent, and WebSphereApplication Server application server.

When engaging IBM product support services, be prepared to provide these logfiles in an archive file. The LogZipper utility provided in the install_home\scripts directory can be used for this task. If you use the LogZipper utility, all


relevant log files are archived in install_home/debug/YYYYMMDD_hhmmss.zip.


Chapter 3. Preparing for installation

These topics provide information about product media, preinstallationconsiderations, overview of the installation procedure, and instructions on usingthe Maximo Asset Management launchpad.

Use the preparatory information to familiarize yourself with the overall process ofa Maximo Asset Management deployment.

Deployment scenario road mapsDeployment scenario road maps are summaries consisting of product deploymenttasks.

The installation information provided with Maximo Asset Management 7.5describes three deployment scenarios.

Scenario 1 focuses on using the middleware installation program to install newIBM middleware, including the optional IBM Tivoli Directory Server, and allowingthe Maximo Asset Management installation program to automatically configurethat middleware.

Scenario 2 describes reusing middleware that you already have installed in yourenvironment, for example DB2 or Oracle, and allowing the Maximo AssetManagement installation program to automatically configure that middleware.

Scenario 3 describes reusing middleware that you already have installed in yourenvironment that you want to manually configure for use with Maximo AssetManagement. In this scenario, the middleware installation program is not used atall and you do not want Maximo Asset Management installation program toautomatically configure middleware.

The following series of road maps provide procedural summaries of Maximo AssetManagement deployment scenarios. The steps contained in each deploymentscenario road map briefly describe the overall task and then provide links to moredetailed information about that task.

The deployment scenarios provided include the following situations:

Deploying with automatic middleware configuration (Scenario 1)You want to establish Maximo Asset Management in a new environment.You intend to use Maximo Asset Management installation programs andtools to install and automatically configure new installations of middlewareand Maximo Asset Management.

This scenario is particularly useful for setting up a demonstrationenvironment for Maximo Asset Management. You want to use MaximoAsset Management installation programs and tools to automatically installand configure middleware and deploy Maximo Asset Management.

Note: The middleware installation program does not support the HP-UXand Oracle Solaris platforms, however, installable images for WebSphereApplication Server Network Deployment, DB2 and IBM Tivoli DirectoryServer are provided with Maximo Asset Management. You can install this


software individually using information in this guide if you want todeploy Maximo Asset Management using this middleware on thoseplatforms.

Deploying automatically reusing existing middleware (Scenario 2)You want to deploy Maximo Asset Management using middleware thatexists in your enterprise. You want to use Maximo Asset Managementinstallation programs and tools to automatically configure yourmiddleware.

This scenario would be applicable in situations where you already haveexisting middleware resources established in your enterprise. You want touse Maximo Asset Management installation programs and tools toautomatically configure that middleware.

Deploying manually reusing existing middleware (Scenario 3)You want to deploy Maximo Asset Management using middleware thatexists in your enterprise, and you want to manually configure thatmiddleware for use by Maximo Asset Management.

This scenario would be applicable to those situations in which you haveexisting middleware resources. You want to use these resources withMaximo Asset Management. You have particular company-sanctionedprocesses and regulations that restrict your use of automated configurationtools when deploying a new application in your enterprise. In thisscenario, you do not use the middleware installation program at any timeduring the deployment. All manual middleware configuration informationis contained in this scenario.

Chapter 4, Deploying with automatic middleware configuration (Scenario 1),on page 33Use this information to use product installation programs and tools to installand automatically configure a Maximo Asset Management deployment withinyour enterprise.Chapter 5, Deploying automatically reusing existing middleware (Scenario 2),on page 93Use this information to use Maximo Asset Management installation programsand tools to automatically configure existing middleware within your enterpriseduring the Maximo Asset Management deployment process.Chapter 6, Deploying manually reusing existing middleware (Scenario 3), onpage 123Use this information if you intend to deploy Maximo Asset Management byreusing existing middleware servers and manually configuring them to workwith Maximo Asset Management.

Installation optionsSeveral middleware installation options are available in your deployment.

You can reuse existing middleware installations as Maximo Asset Managementcomponents. For example, you might have an instance of DB2 or Oracle in anexisting database server farm which already has established access policies,redundancy measures, and backup plans in place.

If you plan to reuse existing middleware, ensure that they are at the levelsupported by Maximo Asset Management. The Maximo Asset Managementmiddleware and Maximo Asset Management installation programs do not providea mechanism for updating servers using unsupported versions of middleware, nor


do these programs provide remote prerequisite checks to ensure that they are atthe correct level. Use the prerequisite checking tool provided with the product.

If you intend to reuse existing Maximo Asset Management middleware serverswith Maximo Asset Management, they must be configured before running theMaximo Asset Management installation program. This reuse can be accomplishedin two ways.

Configure existing middleware for use with Maximo Asset Management usingthe middleware installation program and the Maximo Asset Managementinstallation program

In this scenario, you are using the installation programs supplied withMaximo Asset Management to configure existing middleware for you. Insome cases, you are required to perform a set or subset of manualconfiguration steps if you intend to reuse middleware that is notconfigurable with the middleware installation program.

Manually configuring existing middleware for use with Maximo AssetManagement

In this scenario, you are committing to configure existing middleware foruse with Maximo Asset Management manually. You are not using themiddleware installation program, and you are not using the Maximo AssetManagement installation program to auto-configure middleware resourceswhen prompted during the Maximo Asset Management installationprocess.

In some instances, you want to avoid the sharing of resources. For example, mostdeployments do not use the same DB2 database instance between Maximo AssetManagement and IBM Tivoli Directory Server. During the installation, the databaseinstance is restarted, which can disrupt the availability of IBM Tivoli DirectoryServer to your enterprise. If you are using the automated installation programs,separate instances are created for use by Maximo Asset Management and IBMTivoli Directory Server.

Chapter 3. Preparing for installation 15

Related concepts:Reusing middleware using the middleware installation program on page 95If you intend to reuse existing middleware servers with Maximo AssetManagement, they must be configured before running the Maximo AssetManagement installation program.Related tasks:Running the installation program on page 74Install Maximo Asset Management and automatically configure middleware onmultiple servers, using default values.Running the installation program without middleware autoconfiguration onpage 165Maximo Asset Management can be deployed with middleware that has beenpreviously configured. You might not want to have the Maximo Asset Managementinstallation program automatically configure middleware. If your organization hasspecific policies and procedures that govern how you create databases, databaseinstances, and users within your organization, use these instructions.Programmatically verifying prerequisites on page 19You can use the prerequisite verification utility to verify that installation programprerequisites are present on a system. Use this utility before starting themiddleware and product installation programs.Related information:Maximo Asset Management installation with manual middleware configurationon page 126Manually configured installations involve configuring middleware components, thedatabase server, the directory server, and the J2EE server, to work with MaximoAsset Management before using the Maximo Asset Management installationprogram.

Middleware configuration optionsThere are two options available for configuring Maximo Asset Managementmiddleware.

If the middleware has been either been installed by the middleware installationprogram or you have identified an existing middleware resource you intend to use,you have two options of configuring the servers for use with Maximo AssetManagement. You have the option of the Maximo Asset Management installationprogram automatically configuring middleware, or manually configuringmiddleware. If you choose to manually configure middleware, it must be donebefore running the installation program.

Auto-configureThe Maximo Asset Management installation program automaticallyconfigures middleware to work together with Maximo AssetManagement. Use this option if you are installing new instances ofmiddleware components using the middleware installation program. Alsouse this option if you have existing middleware instances that are notgoverned by policies that restrict programmatic configuration.

ManualYou can manually configure middleware that either exists in yourenvironment, or has been installed by the middleware installation program.This configuration must be completed before running the Maximo AssetManagement installation program. You might choose this deployment pathif you have policies in place that dictate certain procedures and guidelineswhen configuring systems in your environment.


Related concepts:Reusing middleware using the middleware installation program on page 95If you intend to reuse existing middleware servers with Maximo AssetManagement, they must be configured before running the Maximo AssetManagement installation program.Related tasks:Running the installation program on page 74Install Maximo Asset Management and automatically configure middleware onmultiple servers, using default values.Running the installation program without middleware autoconfiguration onpage 165Maximo Asset Management can be deployed with middleware that has beenpreviously configured. You might not want to have the Maximo Asset Managementinstallation program automatically configure middleware. If your organization hasspecific policies and procedures that govern how you create databases, databaseinstances, and users within your organization, use these instructions.Related information:Maximo Asset Management installation with manual middleware configurationon page 126Manually configured installations involve configuring middleware components, thedatabase server, the directory server, and the J2EE server, to work with MaximoAsset Management before using the Maximo Asset Management installationprogram.

Simple or custom optionEarly in the installation, you can choose which type of installation you want,simple, or custom.

Maximo Asset Management can be installed in one of two ways:

SimpleSelect simple if you want to deploy all Maximo Asset Managementcomponents on a single system using all IBM middleware. Thisdeployment option is typically only used for demonstration,proof-of-concept, or training purposes.

CustomSelect custom if you want to deploy Maximo Asset Managementcomponents across several systems. This deployment option is typicallyused in a production environment. If you are deploying Maximo AssetManagement on Oracle WebLogic Server, you must choose this option.

Related tasks:Running the installation program on page 74Install Maximo Asset Management and automatically configure middleware onmultiple servers, using default values.

Software installation imagesYou access the IBM Maximo Asset Management product software from IBMPassport Advantage or from the product DVD if you requested a product DVD.

The installation images that you download from Passport Advantage can comprisemultiple downloadable files. Download all files in the package to a single directoryand extract the files for execution.


For instructions and a full list of installation images, see the IBM Maximo AssetManagement 7.5 Download Document (www.ibm.com/support/docview.wss?uid=swg24029458).

Before you beginA set of tasks must be completed before installing Maximo Asset Management. Insome cases, to perform the steps, you must be logged in as a user withadministrator privileges on Windows. Some processes, such as anti-virus programs,can negatively affect Maximo Asset Management installation on the system. Youmust temporarily shut down any noncritical processes before running the MaximoAsset Management installation program.

Most tasks must be completed for middleware installed on UNIX systems,regardless of whether you intend to use the middleware installation program toinstall and configure Maximo Asset Management middleware. These tasks must becompleted for any UNIX systems hosting middleware you intend to use withMaximo Asset Management.

Note: Make a copy of the image of the system, database, and application server onwhich you are planning to install the product.

Note: IBM publishes updates to the middleware installation program. Before usingit, visit the IBM Support Portal http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Maximo_Asset_Management to see whether there is anupdated copy of the installation program available for your use.

Ensure that you have adequate disk space for the future on the systems being usedfor the Maximo Asset Management deployment. Filling up the disk space on aMaximo Asset Management deployment system can cause problems with MaximoAsset Management operations.

Fully qualified host names provided to the installation programs must resolvebetween systems involved in the product deployment. Ensure all IP addressesconfigured for systems targeted for the product deployment are reachable usingthe ping command from the administrative workstation.

Checking port availability on page 23You need to ensure that certain ports are available before using the productinstallation programs.AIX tar command requirements on page 24Enabling asynchronous I/O on AIX on page 24IBM Tivoli Directory Server requires asynchronous I/O be enabled on AIX

systems. Without asynchronous I/O, DB2 and Oracle database instances cannotbe started successfully.Checking for required libraries on Linux on page 25The Maximo Asset Management deployment requires certain Linux systemlibraries.Configuring the JRE in Linux on page 25In some cases, the middleware installation program fails on Red Hat EnterpriseLinux 5 systems, or other systems with Security-Enhanced Linux (SELinux)enabled.Setting the ulimit on page 26This section details how to set the ulimit in Linux, which is used to define usersystem and process resource limits.


http://www.ibm.com/support/docview.wss?uid=swg24029458http://www.ibm.com/support/docview.wss?uid=swg24029458

Setting the swap size on page 26Maximo Asset Management can be a resource-intensive application. Configureand tune your system for maximum performance. This section details how toset the size of the swap space used in Linux systems.Setting shared memory on page 26This section details how to set a minimum shared memory value in Linux.Remote configuration enablement on page 27The Maximo Asset Management installation program can automaticallyconfigure middleware. You must enable a remote access protocol for eachsystem on which you intend to install the middleware.SSL Client Authentication Restrictions on page 28The Maximo Asset Management installation program and the process solutioninstaller fail if the client authentication feature of SSL is enabled in the IBMHTTP Server.System password policy settings on page 29Be familiar with the password policies of systems you are using as part of aMaximo Asset Management deployment.Backing up the Deployment Engine database on page 29These instructions are for backing up the Deployment Engine database.Backups are used to restore the database to the state it was before installing.Programmatically verifying prerequisitesYou can use the prerequisite verification utility to verify that installationprogram prerequisites are present on a system. Use this utility before startingthe middleware and product installation programs.

Programmatically verifying prerequisitesYou can use the prerequisite verification utility to verify that installation programprerequisites are present on a system. Use this utility before starting themiddleware and product installation programs.

About this task

The prerequisite verification utility checks the following items:v Operating system requirements, including fix packs.v Hardware requirements, including memory and hard disk space.v Port availability.v Middleware requirements such as software packages, library files, directory

permissions, host names, and installation locations.

You can start the prerequisite verification utility from the product installationlaunchpad or from the command line. When started from the launchpad, the utilityruns in interactive mode. When started from the command line, the prerequisiteverification utility accepts various parameters. The prerequisite verification utilitymust be run on the system hosting the prerequisite being checked. You cannot usethis utility to check prerequisites on a remote system.


Table 2. System verification parameters

Parameters Details

-component Specifies the type of component being verified. At least one component must beused with the prerequisite verification utility.

dbserverUse the dbserver parameter to have the prerequisite verification utility checkfor DB2 prerequisites.

dirserverUse the dirserver parameter to have the prerequisite verification utility checkfor IBM Tivoli Directory Server prerequisites.

j2eeserverUse the j2eeserver parameter to have the prerequisite verification utilitycheck for WebSphere Application Server Network Deployment prerequisites.

bsiUse the bsi parameter to have the prerequisite verification utility check forprerequisites required by the product installation program. Run theprerequisite verification utility with the bsi parameter on the administrativeworkstation.

Syntax example:

tpae_req_check.bat -component dbserver

If you do not use the -component parameter, you are prompted to specifycomponents when using the utility.

Multiple components can be specified as comma-separated values.

-input The prerequisite verification utility can accept a property file as input. The utilityverifies property values found in the file. For example, the default DB2 server portparameter is DB2_SERVER_PORT=50000. The prerequisite verification utility verifiesthat this port is available on the DB2 server host.

The default input property file is tpae.properties, and is found on themiddleware installation media in the SystemRequirements directory. There are alsoseveral sample property files found in the SystemRequirements\sample_property_files. These sample property files contain custom valuesdefined for particular operating systems. You can copy these property files to thesystem and modify them, or create your own, before running the prerequisiteverification utility.

Syntax example:

tpae_req_check.bat -component dbserver -input path to the property file

If you do not use the input parameter when you run the prerequisite verificationutility, the utility is run in interactive mode. You are prompted for individualvalues to be verified.


Table 2. System verification parameters (continued)

Parameters Details

-mode The prerequisite verification utility can be run in silent or interactive mode.

interactiveBy default, the prerequisite verification utility is run in interactive mode. Ifyou do not specify the -mode parameter, the utility defaults to running ininteractive mode. When started from the launchpad, the utility runs ininteractive mode.

silentIf you use the silent qualifier, you can also use the input parameter andsupply a property file. If an input file not provided, default property valuesare used. The output must also be directed to a file to view the results.

Syntax example:

tpae_req_check.bat-component dbserver-mode silent-input path to the property file > prereqresults.log

-lang Parameter used to specify the locale of the system being verified.

Syntax example:

tpae_req_check.bat-component dbserver-lang en

Results are produced in the language of the locale specified.

This is an optional parameter.

By default, the language set in the system locale is used. If the resource bundle isnot found for the system locale, or, the system locale language is not supported,messages are displayed in English.

-trace Parameter used to specify trace output statements while the utility is running.

NoneSelecting this qualifier results in no trace information being generated whilethe utility is running.

VerboseSelecting this qualifier results in detailed trace information being generatedwhile the utility is running.

NormalSelecting this qualifier results in default trace information being generatedwhile the utility is running.

Syntax example:

tpae_req_check.bat-component dbserver-trace None

Procedure1. Log on to the system you are checking for prerequisites with a user ID that has

permission to run scripts on the system. Ensure that the middlewareinstallation media is mounted or otherwise available to the system. Thisexample procedure uses values found in the default tpae.properties file toverify that a system is suitable to host DB2 for a Maximo Asset Managementdeployment.


2. Open a command-line window and change directory to the SystemRequirementsdirectory of the middleware installation media.

3. Run the prerequisite verification utility. Specify the component being checkedand the property file to use.tpae_req_check.bat-component dbserver-input d:\SystemRequirements\tpae.properties

In this example, the tpae.properties file is located in the same directory as thetpae_req_check.bat script.

Results

After the prerequisite verification utility has completed successfully, results areprinted to the screen.

CTGIN8117I : The Tivoli Pre-requisite Scanner has been launched.CTGIN8118I : The Tivoli Pre-requisite Scanner exited with the return codeIBM Prerequisite Scanner

Version : 1.0.34Build : 20101109OS Name : Microsoft Windows Server 2003, Enterprise Edition Service Pack 2User Name: Administrator

Machine InfoMachine name : MYMACHINESerial Number: KKKKKK0OS Serial : 66666-666-6666666-66666

PAE [not defined] [version 07500000]:Property Result Found Exp...======== ====== ===== ===...os.totalPhysicalMemory PASS 2.00GB 1.90GBnetwork.hasFQDN FAIL False TrueDisk#1 (C:\ibm\tivoli\mwi\workspace) PASS 27.99GB 300MBDisk#2 (C:\Temp\1) PASS 27.99GB 1000MBDisk#3 (C:\Temp\1) PASS 27.99GB 250MBnetwork.availablePorts.db2 PASS 135,445,1025,2967,3389,5800,5900,139 50000network.availablePorts.ctginst PASS 135,445,1025,2967,3389,5800,5900,139 50005Disk#4 (C:\Program Files\IBM\SQLLIB) PASS 27.99GB 1.40GB

ALL COMPONENTS :Property Result Found Exp...======== ====== ===== ===...C: PASS 27.99GB 2.91GB

Prereq Scanner Overall Result: FAILprereq_checker.bat 1

These values can also be redirected to a file when starting the command from thecommand line.

If any of the verification steps report a failure, resolve the issue and rerun theverification utility before installing Maximo Asset Management components.

Table 3 contains a list of the properties checked. Use this information to analyzeprerequisite verification utility results.

Table 3. Prerequisite verification utility properties

Property Description

CpuArchitecture Verifies the machine architecture is supported.


Table 3. Prerequisite verification utility properties (continued)

Property Description

disk(rw permissions) Checks read/write permissions of required directories.

network.availablePorts.* Verifies required ports are available.

The following example checks to ensure a port required by DB2 is available.

network.availablePorts.db2inst=50000

network.dns Verifies there is a DNS entry for the system on the DNS server.

network.fqdn Verifies that the system host name is fully qualified.

os.architecture Verifies the operating system architecture is supported.

os.dir.tmp/home Verifies required permissions for the system directories

os.FreePagingSpace Verifies adequate free paging space is available on the system.

os.iodevicestatus Verifies the I/O device status of the system.

os.lib.ksh Checks the ksh library.

os.lib.libstdc++.so.5 Verifies a prerequisite library is available on the system.

os.lib.xlC.rte=xlC.rte.9.0.0.8+ Verifies a prerequisite library is available on the system.

os.mountcheck Checks for the existence of nosuid on the file system.

os.package.rpm Verifies prerequisite packages are available on the system.

os.RAMSize Reports system RAM available.

os.SELinux Determines if selinux is enabled.

os.servicePack Verifies required service packs are installed on the system.

os.shell.default Determines the default shell for users.

os.space.* Determines disk space availability for various file systems.

The following example shows the check made for the middleware installationprogram workspace.

os.space.root=[dir:root=/root/ibm/tivoli/mwi/workspace,unit:MB]300

os.totalPhysicalMemory Reports physical RAM available to the operating system.

os.ulimit Identifies user limits configured on the system.

os.Version Reports the operating system type and version.

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

About this task

You must check to see if ports are in use and accepting connections for the systemyou are using to host middleware. For example, port 50000 must be made availablefor DB2. Port 9060 must be made available for IBM WebSphere Application ServerNetwork Deployment. If you intend to use these default port values, ensure thatthe port is not already assigned before you run installation programs.

You can either use the prerequisite verification utility to check for port availability,or you can check manually.


Procedure1. Open the appropriate port checking utility on the host system. If present, check

firewall rules for the system.2. Check the availability of ports required by Maximo Asset Management. If you

find that port already assigned, ensure that you choose another value whenprompted by the middleware installation program.Programmatically verifying prerequisites on page 19You can use the prerequisite verification utility to verify that installationprogram prerequisites are present on a system. Use this utility before startingthe middleware and product installation programs.

AIX tar command requirements

Both the native UNIX tar command and the GNU version of the tar command arerequired by the middleware installation program. Because the native utility doesnot support long file names, ensure that GNU tar version 1.14 or higher isinstalled. GNU tar version 1.14 ensures that installation files can be extracted.

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

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

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

AIX font requirementsAIX requires specific fonts in order to produce reports.

About this task

When producing reports from AIX systems, TrueType fonts must be available onthe system.

Procedure1. Install TrueType fonts on the AIX system.2. Ensure the fonts-path environment variable refers to the location of the fonts.

Enabling asynchronous I/O on AIXIBM Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems.Without asynchronous I/O, DB2 and Oracle database instances cannot be startedsuccessfully.

About this task

Enabling asynchronous I/O on AIX is an installation requirement, so this stepmust be run before running the middleware installation program. You only need toperform this step if the system hosts the IBM Tivoli Directory Server.

To turn on asynchronous I/O follow these steps:


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

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

smit chgaio

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

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

smit aio

7. In the System Management Interface Tool (SMIT) dialog box, select ConfigureDefined Asynchronous I/O, and then click Enter.

8. Reboot the system to enable the changes.

Checking for required libraries on LinuxThe Maximo Asset Management deployment requires certain Linux systemlibraries.

Procedure1. Locate the libstdc+.so.5 library in the /usr/lib/ directory. If this library is not

installed, the middleware installation program throws an error when runningthe middleware installation program in graphical mode. If you cannot locatethis library on your system, locate the RPM package for your system thatcontains this library and install the package.

2. Ensure that you have the libstdc++33-32bit-3.3.3-11.9.x86_64.rpm packageinstalled before running the product installation program. SUSE LinuxEnterprise Server 10 64-bit systems hosting manually configured middlewaremust host this package.

Configuring the JRE in LinuxIn some cases, the middleware installation program fails on Red Hat EnterpriseLinux 5 systems, or other systems with Security-Enhanced Linux (SELinux)enabled.

About this task

In one scenario, the middleware installation program fails with an error statingthat the Java Runtime Environment (JRE) cannot be found. In another scenario, themiddleware installation program fails stating that it cannot find the VM.

Complete the following steps to avoid these problems:

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


Results

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

Setting the ulimitThis section details how to set the ulimit in Linux, which is used to define usersystem and process resource limits.

About this task

For Linux systems, you must set the ulimit for the system before using themiddleware installation program.

If you set the ulimit in .profile for root, the ulimit setting applies to all processes.

To set the ulimit, complete the following steps:

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

Setting the swap sizeMaximo Asset Management can be a resource-intensive application. Configure andtune your system for maximum performance. This section details how to set thesize of the swap space used in Linux systems.

About this task

Typically, the swap size for Linux is set to twice the amount of physical RAM inthe server. See the product documentation for your Linux distribution for moreinformation.

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

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

Setting shared memoryThis section details how to set a minimum shared memory value in Linux.

About this task

For Linux systems, you must set a minimum shared memory value for the systembefore using the middleware installer.

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


Procedure1. From a command line, type sysctl kernel.shmmax and determine if the value is

less than 268435456 bytes (256 Mb).2. If you must increase the value, from a command line, type sysctl -w

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

Remote configuration enablementThe Maximo Asset Management installation program can automatically configuremiddleware. You must enable a remote access protocol for each system on whichyou intend to install the middleware.

Use SSH for logging on to and configuring remote Linux and UNIX systems. UseWindows SMB for logging on to and configuring remote Windows systems.Windows SMB is a Windows protocol. The IBM JRE on the administrativeworkstation includes SSH.

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

For remote Windows systems, ensure that the following requirements are metbefore installing the software:v The user name that you provide to the installation program must exist as a local

account on the remote system. This user must be a member of the WindowsAdministrators group.

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

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

v Ensure that any ports that you use for remote protocols are not blocked byfirewalls or security policies, including ports 137 and 139. Port 139 is used ifSMB is configured to run on NetBIOS over TCP/IP. Port 445 is used if SMB isrun directly on TCP/IP, without NetBIOS.

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

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

v For Microsoft Windows Server 2008 systems that support password-protectedsharing, disable password-protection. Shares must be shared for the Guest orEveryone accounts.

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

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


For remote Linux or UNIX systems, ensure that the following requirements are metbefore installing the software:v For AIX systems, set the following SSH parameters located in the

/etc/ssh/sshd_config file: ClientAliveInterval 900 ClientAliveCountMax 10

Stop the SSH daemon using the stopsrc -s sshd command and then restart itusing the startsrc -s sshd command.

v For AIX systems, set the TMOUT and TIMEOUT variables in the user profilescript to 0. This setting prevents the user from idling out and being logged offthe remote system during the installation.

v The user name that you provide to the installation program must exist as aprivileged account (for example, root) on the remote systems.

v Ensure that a current version of OpenSSH is installed and running. Do not useOpenSSH 4.7.0.5302.

v For Oracle Solaris systems, the remote access protocols require the use ofinternal shell scripts that must be run within the korn (ksh) shell. The methodsneed ksh, even if the user ID that you use to log on to the remote system isconfigured to use a different shell. Consequently, Oracle Solaris systems musthave 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 orremote system.

SSL Client Authentication RestrictionsThe Maximo Asset Management installation program and the process solutioninstaller fail if the client authentication feature of SSL is enabled in the IBM HTTPServer.

Before you begin

The Maximo Asset Management installation and process solution installerprograms use HTTP client requests for various configuration actions. While theMaximo Asset Management installation program does not configure WebSphereApplication Server Network Deployment or IBM HTTP Server to use securesockets layer (SSL), they do function in environments where WebSphereApplication Server Network Deployment and IBM HTTP Server have beenpreviously configured manually to use SSL. However, Maximo Asset Managementinstallation programs and standard deployment procedures do not work correctlyif the client authentication feature of SSL is enabled in the IBM HTTP Server.Validation of product administrative credentials or import of data using MaximoEnterprise Adapter fails. Client authentication is enabled in the IBM HTTP Serverusing the SSLClientAuth Required directive in the httpd.conf configuration file ofthe IBM HTTP Server.

About this task

If client authentication must be enabled for the IBM HTTP Server, use thefollowing workaround procedure to install the product.


Procedure1. 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. Run the Maximo Asset Management installation program or process solution

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

System password policy settingsBe familiar with the password policies of systems you are using as part of aMaximo Asset Management deployment.

Your organization might have password policy regulations enforced on systems onyour network. Before deploying Maximo Asset Management, be sure that you arefamiliar with the password policies of systems used in the deployment, or youmight experience errors during installation.

For example, Microsoft Windows Server 2008 systems have a stricter set ofpassword requirements than previous versions configured by default. If you arenot familiar with these stronger password requirements, you might experience anerror during the installation of Maximo Asset Management. This error occurswhen creating users on a Microsoft Windows Server 2008 system.

Password values that you provide during the Maximo Asset Managementinstallation must be compliant with the password policies set for the target system.Passwords are not validated against the password policies of target systems at thetime you enter them on the installation program panels. If your passwords do notconform to the password policies of systems used to deploy the product, errorsoccur when the installation program attempts to create these passwords during theconfiguration step,

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

Before you begin

Back up the Deployment Engine database of the system before and after applyingany updates to an existing deployment. Use backups to recover from partialinstallation attempts.

About this task

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

Procedure1. Set up the environment using the following command:

Windowsc:\install_home\ctg_DE\acsi\setenv.cmd

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


Windowsc:\install_home\ctg_DE\acsi\bin\backupdb.cmd backup file name

Use a meaningful name for backup file name to reflect the fact that it contains thestate of the registry after your installation of Maximo Asset Management. Forexample, DEBackupAfterInstall.

LaunchpadThe IBM Maximo Asset Management launchpad serves as a centralized interfacefor launching a collection of installation programs and product information.

The launchpad application assists you in choosing which product installationprograms you must install and indicates the order in which they must be installed.

Use the Maximo Asset Management launchpad to:v start the middleware installation program.v start the prerequisite checker utility.v start the Maximo Asset Management installation program.v access the Maximo Asset Management information center, including information

used to plan the Maximo Asset Management installation and deployment.

Just before starting the launchpad, ensure that you meet the middlewareprerequisites. Ensure that you have the correct service pack levels for yourenvironments and always use fully qualified domain names when entering valuesfor the installation program.

Starting the launchpadUse the following information to start the Maximo Asset Management launchpad

Before you begin

Launchpad generated messages are captured in a hidden log frame while thelaunchpad is running. To show the log frame on the bottom of the launchpadpanels, hold the CTRL key while simultaneously clicking the banner frame of thelaunchpad. Messages that are generated while the launchpad is running are notautomatically saved on the hard disk drive. You can manually save the messagesfrom a session by clicking Save at the bottom of the log frame and then specifyingwhere you want to save the file.

About this task

To start the IBM Maximo Asset Management launchpad, complete the followingsteps:

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

where you want Maximo Asset Management components to be installed.2. Start the launchpad from the root directory of the installation image:

v Windows: Start the launchpad by using the launchpad.exe program.Appendix B, Planning worksheets for middleware installation, on page 323Before you start the installation, use the planning worksheets to record valuesto specify when installing the components you choose for your deployment.


Appendix A, Planning worksheet for product installation, on page 321These tables list the values for settings you supply when using the MaximoAsset Management installation program. Values you enter depend on thecomponents you select for the deployment.


Chapter 4. Deploying with automatic middleware configuration(Scenario 1)

Use this information to use product installation programs and tools to install andautomatically configure a Maximo Asset Management deployment within yourenterprise.

Before you begin

Ensure you have reviewed the following information:v Chapter 2, Planning to deploy, on page 5v Chapter 3, Preparing for installation, on page 13

About this task

This information provides a high-level overview or road map of tasks you need tocomplete in order to deploy Maximo Asset Management with automaticmiddleware configuration. Use the information provided in the Concepts list tofamiliarize yourself with the ideas behind each step, and then refer to the Tasks listand perform the tasks listed in order to complete the step.

In this scenario, you use the middleware installation program to install andautomatically configure new instances of DB2, WebSphere Application ServerNetwork Deployment, and IBM Tivoli Directory Server and then use the productinstallation program to perform further middleware configuration tasksautomatically before finally deploying the product itself.


Procedure1. Install and configure middleware using the middleware installation program.

The middleware installation program is used to install and automaticallyconfigure middleware used by Maximo Asset Management.

ConceptsMiddleware installation on page 35

Tasks Installing and configuring middleware using the middlewareinstallation program on page 38

2. Install Maximo Asset Management and complete further middlewareconfiguration tasks using the Maximo Asset Management installation program.

ConceptsInstallation program overview on page 71

Tasks Running the installation program on page 743. Complete post-installation tasks

Concepts

v Chapter 10, Post installation tasks, on page 207Tasks

a. Initial data configuration on page 207b. Synchronizing users and groups on page 213c. Understanding and configuring security on page 215

Install middleware using the middlewareinstallation program

Install IBM Maximo Asset Managementand automatically configure middleware

Verify the installation

Perform post-installation tasks

Figure 3. Deploying Maximo Asset Management using automatic middleware configuration


What to do next

After you have completed the deployment process, you can optionally perform thefollowing tasks:v Create startup scripts for middleware.

You can create startup scripts that will automatically start Maximo AssetManagement middleware services upon a system reboot.

Middleware installationBefore you can install the Maximo Asset Management, there are several MaximoAsset Management middleware products that can be deployed, or, if you intend toreuse existing resources, configured either manually or using the Maximo AssetManagement installation programs

The middleware installation program provides an interface for installing anddeploying Maximo Asset Management middleware in a reliable and repeatablefashion. The middleware installation program records choices you make aboutyour Maximo Asset Management deployment and configuration parametersassociated with those choices, and then installs and deploys Maximo AssetManagement middleware based upon the information you entered.

The middleware includes the following software:v Database server

Maximo Asset Management uses the Maximo database to store details about theattributes and history of each configuration item and the details about therelationships between configuration items. A database is a required componentfor deploying Maximo Asset Management.You have the choice of installing a new instance of DB2 9.7 using themiddleware installation program, or using a preexisting instance of DB2 9.5, orDB2 9.7. You can also choose to use Microsoft SQL Server or Oracle for yourMaximo Asset Management deployment, but you must install and configurethem manually.

v Directory serverThe directory server is an optional component that can be used to secureMaximo Asset Management if you choose to use an LDAP server for security.You have the choice of installing a new instance of IBM Tivoli Directory Server6.3 for Windows and UNIX, or using a preexisting IBM Tivoli Directory Serveror Microsoft Active Directory server. If you choose to install a new version ofIBM Tivoli Directory Server, you must choose to install a new DB2 instance orreuse a an existing DB2 server. Alternatively, you can use the Maximo AssetManagement database server for the DB2 data store if the Maximo AssetManagement database server uses DB2. If you choose to install the directoryserver but not the database server, the middleware installation program attemptsto locate an existing database instance to use. If it fails to locate an existinginstance, it installs a database for use with the directory server. If you choose touse Microsoft Active Directory Server for your directory server, you must installand configure it separately.

v J2EE serverThe J2EE server is the application server used to serve and manage the MaximoAsset Management application.The J2EE server can optionally be secured with a IBM Tivoli Directory Server orMicrosoft Active Directory directory server.

Chapter 4. Deploying with automatic middleware configuration (Scenario 1) 35

The J2EE component includes the following subcomponents: IBM HTTP Server

IBM HTTP Server is used as the primary HTTP server.You install a new instance of IBM HTTP Server.

IBM HTTP Server plug-inThe IBM HTTP Server plug-in is used as the interface between IBM HTTPServer and the J2EE serverYou install a new instance of IBM HTTP Server plug-in.

The middleware installation program deploys software on a single server. Todeploy Maximo Asset Management middleware on multiple servers, themiddleware installation program must be started on each server in the topologyconfiguration you have chosen. Ensure that you have a strategy for deployingMaximo Asset Management middleware for each system you plan to use in yourMaximo Asset Management deployment. If you deploy a Maximo AssetManagement component using the middleware installation program on a system,for example, DB2, and then later decide you would also like to add IBM TivoliDirectory Server to that same system, you must undeploy DB2 before redeployingit in the same middleware installation program deployment plan that includedIBM Tivoli Directory Server. When installing Maximo Asset Managementmiddleware on a system, you must install all of the middleware intended for thatsystem at one time.

A process ID is generated each time the middleware installation program is usedto install or uninstall a set of middleware products. The process ID appears on thefile system in various places related to logs and generated files, such as file names,directory names, and log messages. The process ID is used to group logs and othergenerated files that are related to the same invocation of the middlewareinstallation program. It also separates logs and other generated files that arerelated to different invocations of the middleware installation program. The processID is a string of the format [operation_MMdd_HH.mm], where operation is astring indicating the operation being performed, such as "INSTALL" or"UNINSTALL", MM is a two-digit number (1-12) indicating the current month, ddis a two-digit number (1-31) indicating the current day in the month, HH is atwo-digit number (0-23) indicating the current hour, and mm is a two-digit number(0-59) indicating the current minute. Here are some examples of process ID values:v [INSTALL_0924_15.45]

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

An uninstallation started on December 16 at 9:59am

Note: The middleware installation program does not support the HP-UX andOracle Solaris platforms, however, installable images for DB2, WebSphereApplication Server Network Deployment, and IBM Tivoli Directory Server areprovided with Maximo Asset Management. You can install this softwareindividually using information in this guide if you want to deploy Maximo AssetManagement using this middleware on those platforms.

Middleware installation program workspaceThe middleware installation program is designed to record the options you selectduring installation in a directory known as the workspace, and then configure thecomponents selected as a single deployed application.


After a plan has been deployed, the middleware installation program cannotdeploy additional features and products onto the system at a later time. Theexisting plan must first be undeployed with the middleware installation programbefore a different set of features and products can be deployed.

The composition and details of the deployment and any logs generated by themiddleware installation program process are located in the workspace.

By default, the middleware installation program workspace is defined as:

WindowsC:\ibm\tivoli\mwi\workspace

AIX /ibm/tivoli/mwi/workspace

Linux /root/ibm/tivoli/mwi/workspace

The workspace can be defined on a shared resource that is made available to allthe systems that run the middleware installation program. Locating the workspaceon a shared resource avoids the need to copy files such as the topology filemanually from one system to another.

The workspace contains the following items:

Deployment PlanThe deployment plan is a collection of installation steps, configurationparameters for those steps, and target system information. It is generatedby the middleware installation program and is located in the workspacedirectory.

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

The deployment plan configuration files contain information about thedeployment plan itself. Whenever a deployment plan is modifie