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

. . . . Incorrect service pack requirement for AIX . . . Invalid DB2 password value . . . . . . . . . . . . . . 234 . . Installing process managers using the process solution installation wizard. . . . Updating the port for the information center Maximo Asset Management Security . . . . . Post-installation configuration . . . . . Encountering error CTGIN9042E . . Encountering error ACUINI0044E . . . 201 201 203 203 WebSphere configuration . . . . Uninstalling an automatically configured deployment . . . . . . . . . Improper configuration of DB2 or IBM Tivoli Directory Server . . . . . . . . . . . . . . . . Common deployment failures . . . . . . . . . . . . 280 215 217 217 217 218 Notices . 221 . . . . Verifying the installation . . . . . . . . Update General Ledger Component Type Authorization . . . . . . . Create item and company sets . . . . . Manually configuring directory services for WebSphere Application Server Network Deployment . . . . . . 263 . 224 Chapter 9. . . Incorrect idsccmdb user password . . . . . . . . . . . . . . . . . . Create a general ledger account . . 239 243 255 255 256 257 257 259 261 . . . Troubleshooting middleware uninstall . . . . Uninstalling a manually configured deployment . . Manually configuring directory services for Oracle WebLogic Server . . . . . . . .properties file . . . . . . . . . . . . . . . . Configuring SMTP . . . . . 227 227 228 229 . 230 . . . . . . . . . 205 Chapter 8. 219 219 219 . . . . . . . . . . 201 Optional deployment of Maximo Asset Management language packages . . 197 . . . . . 204 . . . . . . . . . . . Troubleshooting the product installation program General troubleshooting of the product installation program . . . Uninstall the product or middleware . . Creating currency codes . Restarting middleware . . . . . . . . . Create a Work Type . . . . . . . . . . . . . . . . 198 Chapter 7. . . . . . . . . . 227 Troubleshooting the middleware installer . . . . . . . . . . . . . . Create an organization . . . . . . . . . . . . . . . . . Before using the process solution installation program . . . . Process solution package installation . . . . . . . . . . 203 . . . . 209 209 209 210 210 211 211 211 212 212 213 213 214 214 215 215 . . . . . . . . . . . . . . 196 . Process solution installation logs . . WebSphere Application Server configuration Starting the WebSphere Application Server Securing the WebSphere Application Server Network Deployment Administrative Console through VMM . . . . . . . . Uninstalling middleware . . . . Process solution packages . . . . . . . 262 . . 209 Post installation steps . . Signing out and signing in . . . 236 . . . Uninstalling the product. . . . Troubleshooting . . . . . . SOAP connection problem . . . . . 234 . . . . . Configuring the WebSphere Application Server to run Windows services . . . . . . . Creating a general ledger account component Applying changes to the database . . . Failure when system directories cannot be renamed . . . . . . . Deployment of optional packages . . . . . 222 . . . . . . . . . . . . . Create default insert site. . Initial data configuration . 283 Trademarks . . . 267 . . . Configure directory server for Microsoft Active Directory . . . . . . . Updating environment data . Post product installation process manager tasks Manually configuring PSI packages . . . 233 . . . . Incorrect db2admin password . . . 285 Index . . . . . . . . . . . 195 195 . . Restarting middleware on Windows . . . . . . . . . . . . . . . . Deploying the confhelp. . 287 iv Installation Guide: . . . Configuring the WebSphere node agent to run Windows services . . Tuning DB2 . . . . . . . . . . . . . . . . . . . Installing the language pack . . . . . . Signing in using a default user ID . . . . 237 239 . Installation properties . Restarting middleware on UNIX . . .Completing post-installation tasks . Update Company-Related Accounts . .

Chapter 1. or you use any other supported database. You can store this information on the IBM DB2 database that is provided on the product DVD. A list of supported databases is provided in the prerequisites topic in the chapter that helps you prepare for the installation. System architecture and components A Maximo Asset Management system includes the product and several additional software servers. The following diagram shows the components that are used in a typical Maximo Asset Management installation. common platform.2010 1 . 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. 2007 . and business logic components. The middleware components can run on one or more computers. Administrative workstation © Copyright IBM Corp. Application server The application server manages the Maximo Asset Management JavaServer Pages (JSPs). XML. Introduction to IBM Maximo Asset Management IBM® Maximo Asset Management is a comprehensive suite of products that is built on a single. Maximo Asset Management combines enhanced enterprise asset management functionality with new service management capabilities that together improve the effectiveness of asset management strategies. Maximo Asset Management uses a commercial Java™ 2 Enterprise Edition (J2EE™) application server: either IBM WebSphere® Application Server or Oracle WebLogic Server. Maximo Asset Management requires multiple software servers that are referred to as middleware.

Product support site The IBM Software Support Web site at http://www. use the administrative workstation to make updates or changes to the configuration.com/software/ sysmgmt/products/support/IBMMaximoAssetManagement. After the installation. Product information Review the product installation information before you begin a Maximo Asset Management installation. dedicated HTTP server to work with the J2EE application server. Download document Describes how to download the product images if you do not have a product DVD. Directory server You can configure a directory server to provide identity management and authentication for the J2EE server. review the following information on the Quick Start DVD and the Maximo Asset Management information center. 2 Installation Guide: . The information center is located at http://publib.boulder.com/infocenter/ tivihelp/v3r1/index.The administrative workstation is used to install Maximo Asset Management. Before you install Maximo Asset Management. Web browser Users access the Maximo Asset Management applications by using a Web browser.jsp?topic=/com. In addition to the required components.ibm.1/mam_welcome.htm : Quick Start Guide Provides brief information to help you get started. you can use the following optional components with Maximo Asset Management: HTTP server You can configure a separate.doc_7.mam. The Quick Start DVD and Web information center contain copies of the Quick Start Guide in several languages. The administrative workstation must be installed on a Microsoft® Windows® system.ibm.ibm. connected over a company network or over the Internet.html provides access to the latest fixes and technical notes.

2010 3 . Administrative workstation (Windows OS only) Middleware ? Maximo Asset Management Database ? J2EE server (Windows. and learning environments. Deployment environments You can deploy Maximo Asset Management and the middleware on a single computer or distributed across multiple computers. A deployment environment can use existing middleware. This environment optimizes resource use and decreases the load on each system. In a distributed environment. Linux. You can also configure a cluster of application servers to improve performance and provide redundancy in a large deployment. 2007 . Plan to use one of the following deployment environments: Stand-alone environment In a stand-alone environment. Planning to install Maximo Asset Management Use this information to plan your Maximo Asset Management installation. you can install the middleware on a mixture of Windows. you install Maximo Asset Management and the middleware across multiple computers. © Copyright IBM Corp.Chapter 2. you install Maximo Asset Management and the middleware on one computer. testing. This environment is used typically for proof-of-concept purposes. Only the administrative workstation must be hosted on a Windows system. If you intend to use existing middleware. Solaris. and UNIX computers. demonstrations. The install program configures new middleware to work with Maximo Asset Management. AIX. but the simplest approach is to install new middleware. HP-UX OS) Distributed environment In a distributed environment. Linux. you must update and configure it to be compatible with Maximo Asset Management. Use this environment for production.

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. 4 Installation Guide: . with centralized administration and management. If you plan to implement a cluster of servers. 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. see the J2EE server documentation for instructions to configure and manage clustered services. and a distributed or clustered environment for production.

For example. When you start to install and IBM product. including applying fix packs. 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. 4. If a deployment engine does not exist. non-administrative user ID on the administrative workstation for each installation. you can use the same computer to deploy a test environment. upgrades. Chapter 2. and installing new products. If you use the middleware installation program to install middleware on the administrative workstation.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. About this task One administrative workstation can support several Maximo Asset Management installation by hosting multiple local instances of the deployment engine. During the installation. 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 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. a message is displayed that an error was encountered that is related to the registry service being unavailable. and a training environment. to create a local instance of the deployment engine instance. 5. Planning to install Maximo Asset Management 5 . 3. a development environment. it installs a global instance of the deployment engine and will prevent you from deploying multiple instances of the product on that system. Restart the installation program and continue with the installation. it is not possible to create a local instance of the deployment engine on that system. Launch the product installation program while logged in as the non-administrative system user ID. complete them on one system at a time. the installation program installs it. Create a separate. Procedure 1. The same user ID must perform all future software installations on the system. Exit the installation wizard and add this user ID to the administrator group for the system. v As a local instance for the sole use of the User ID that installs it. it provides details of the IBM products that are installed on the system. The deployment engine contains a database of information about IBM software installed on the system. When you perform subsequent installation actions. 2. the installation program checks for the existence of the deployment engine on the system. If the deployment engine is deployed as a global instance. If the deployment engine exists on the system.

This scenario is useful for setting up a demonstration environment. the instance is created at C:\Documents and Settings\development\acsi_development. 2. C:\IBM\SMP\development. depending on how you want to install and use middleware. Add the development user ID to the system administrators group. Repeat these steps for each subsequent installation on the same workstation. an error message is displayed. Restart the installation program. If you add the user ID to the administrators group before starting the installation. 4. a global instance of the deployment engine is created. After the instance is created. 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. Click Next to exit the installation program. It can be useful to create an installation directory based on the user ID associated with this installation. 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 system user must have write access to the installation directory. In this example. You must perform this step after the deployment engine is deployed locally. For each installation. use a meaningful directory name that represents the purpose of this deployment. Deployment scenarios These deployment scenarios provide a road map of the tasks associated with each deployment option. the product is installed in a directory called C:\IBM\ development \SMP and is intended for use as a development environment. and middleware topology. In this example. 6 Installation Guide: . we create a user named development. The deployment scenarios summarize the installation and deployment tasks that you perform. Proceed through the installation wizard screens. 5. specify a directory that is separate from all other Maximo Asset Management installation directories on the same administrative workstation. the installation program is unable to immediately use it. 7. Example In this example. to avoid conflict with other deployments. but must not be a member of the system administrator group. Although the deployment engine instance was created successfully. for example. add the ID to the Remote Desktop Users group.6. If you plan to use Windows Remote Desktop Connection to log in to the system with this user ID. 8. 6. In the Specify Install Folder screen. use a different non-administrative user ID. installation directory. 1. This phase of the installation creates a local instance of the deployment engine in the %USERPROFILE%\acsi_%USERNAME% director. Create the non-administrative system user ID for the development installation. When you get to the Choose Install Folder screen.

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. In all deployment scenarios. The Maximo Asset Management installation program can automatically configure new or existing middleware that is supported by the middleware installer. You must complete manual configuration before running the Maximo Asset Management installation program. If you plan to reuse middleware components. ensure that they are at the level supported by Maximo Asset Management. includes a set of IBM middleware components you can use. This scenario is suitable if you have existing middleware resources that you want to automatically configure for use by Maximo Asset Management. while others require manual configuration. Chapter 2. The installation programs do not perform remote prerequisite checks and do not provide a mechanism for patching unsupported servers. This option is useful if you are installing new middleware. for example if your company security policies restrict use of automatic configuration tools. Manual configuration Alternatively.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. Automatic configuration The Maximo Asset Management installation program automatically configures middleware to work with Maximo Asset Management. The Tivoli® middleware installer that is included with the product. Middleware configuration planning You can choose middleware from a wide selection of supported applications. Alternatively. You might also choose to manually configure middleware. ensure that they are at the level supported by Maximo Asset Management. you must install middleware before you install Maximo Asset Management. Maximo Asset Management can automatically configure some new or existing middleware components. This option is useful if you have policies in place that govern configuration procedures. This scenario is suitable if you want to use existing middleware. The installation programs do not perform remote prerequisite checks and do not provide a mechanism for patching unsupported servers. You must manually configure middleware components that are not supported by the middleware installer. Planning to install Maximo Asset Management 7 . but your company restricts the use of automated configuration tools when deploying a new application in your enterprise. For example. If you plan to reuse existing middleware components. you might have an instance of a DB2® server in an existing database server farm. you can use any of the other supported middleware products from third-party vendors. you can manually configure middleware that exists in your environment or has been installed by the Tivoli middleware installer. or if you have existing middleware that is not governed by policies that restrict automatic configuration.

ctginst1 v Users v Administrators ctginst1 must be a member of db2iadm1 or whichever group has been designated as the instance administration authorization group. idsccmdb Windows v Users v Administrators Linux®. record the values to use. The worksheets are also helpful if you intend to manually configure or reuse existing middleware. Users and groups Before you begin. This user is created by the middleware installation program if it does not exist. The system user that is used as the database instance owner on UNIX® systems. use the planning worksheets to record the values that you must specify when you perform the middleware installation. Windows Service user ID. This user is created by the middleware installation program if it does not exist. This user is created by the middleware installation program if it does not exist. list the users and groups that you want to create if you do not want to use the default values. record multiple values where appropriate. AIX®. 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. 8 Installation Guide: . Solaris v idsldap v db2grp1 IBM Tivoli Directory Server user.Planning worksheets for middleware installation Before you start the installation. HP-UX. so that you can quickly specify these values during the installation For distributed deployments. Table 1. This user is created by the Maximo Asset Management installation program if it does not exist. Your value maximo v Users v Administrators Used for Maximo database configuration. Users and groups created during Maximo Asset Management installation User db2admin Group v DB2USERS v DB2ADMNS Description DB2 administrator. In this table.

Solaris db2fgrp1 Linux. Solaris db2fenc1 Linux. Table 3. 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. Solaris /opt/IBM/db2/V9. AIX. Solaris dasusr1 Fenced user Linux. HP-UX. DB2 configuration Setting Installation directory Default Windows SystemDrive\Program Files\IBM\SQLLIB Linux. AIX. Planning to install Maximo Asset Management 9 . This user is created by the middleware installation program if it does not exist. HP-UX.5 DAS user Windows db2admin Linux. AIX. HP-UX. HP-UX. Table 2. AIX. Users and groups created during Maximo Asset Management installation (continued) User wasadmin Group Not a system user. list the middleware directory locations to use. AIX. 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. Description User ID created for use with WebSphere Application Server.Table 1. Your value Directory locations In this table. list the configuration values to use when you install DB2.

AIX. HP-UX.0\db_1 Linux. Enable O/S Security for DB2 objects YES This value is relevant for reuse scenarios only. list the configuration values to use when you install Oracle. AIX.1. HP-UX. DB2 configuration (continued) Setting Instance user name home directory Default Linux. Solaris /opt/app/oracle/product/ 11. 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. AIX. AIX. HP-UX /home/ctginst1 Solaris /export/home/ctginst1 Database instance user ID Windows db2admin Linux. Solaris db2iadm1 DB2 users group Windows DB2USERS YES NO This value is relevant for reuse scenarios only. Table 4.1. Oracle configuration Setting Installation directory Default Windows SystemDrive\oracle\ product\11. HP-UX.Table 3. Solaris ctginst1 DB2 administrators group Windows DB2ADMNS Linux.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

Log files for the Maximo Asset Management installation program are on the administrative system in the following directories. the roles are defined. where <MAM_HOME> equals C:\IBM\SMP.1 through the use of the IBM Support Assistant Workbench. 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: . you create all your users and security groups in your directory (LDAP) server. Security configuration Although you choose a security option during the installation. you configure the security environment after installation. The following security options are available: Use application security for authentication and authorization With this option.The option that you choose applies to all products that you install on a system. Planning for serviceability Serviceability refers to problem analysis from a central point. separately from any corporate user data you might have. Table 10. a directory server is not required. The information is updated in your Maximo database by using a cron task. If you plan to install Maximo Asset Management with a product that was already installed. Log files for the middleware installation program can be found in the workspace directory you defined when you ran the installation program. Serviceability is supported in Maximo Asset Management 7. using data collected from a wide range of sources. You create and manage users and groups in the Users and Security Groups applications. Use application security for authentication only With this option. The post-installation tasks can include creating users. If you use this option and also choose automatic configuration of your directory server. and defining the applications that members of each security group can use. the choice you made when installing the first product applies to Maximo Asset Management as well. assigning users to security groups. These files are analyzed by the Log Analyzer tool. you create all your users in the directory server. The workbench is a free utility that you can configure to work with many different products. but you manage their membership in security groups in the Security Groups application. Use Maximo security for authentication and authorization With this option. Serviceability has changed from the method used in the previous version of the product.

properties and deexlogger. Chapter 2. and on other platforms at /var/ibm/common/acsi or /home/username/.Table 10. The properties files can be found on Windows at C:\ProgramFiles\IBM\ common\acsi or C:\Documents and Settings\username\acsi_username . After installation. WebSphere deployment manager. the log files. during normal usage of Maximo Asset Management. and the WebSphere node agent.acsi_username. refer to the troubleshooting section of the Maximo Asset Management information center. it can be useful to examine the logs generated for the MXServer application server.properties files contain *fileDir occurs during the validation sequence of the keys whose values provide the location for installation program. Log file directories (continued) Log file directory Details Log files are generated here if a problem The ACULogger. For more information about log information and the IBM Support Assistant Workbench. Planning to install Maximo Asset Management 17 .

18 Installation Guide: .

The Maximo Asset Management installation and middleware installation programs install and configure IBM products that make up the Maximo Asset Management © Copyright IBM Corp. Middleware for Red Hat Enterprise Linux V4 Contains middleware for Red Hat Enterprise Linux version 4. Maximo Asset Management V7. Ensure that you have the following DVDs or images: Maximo Asset Management V7. Preparing to install Maximo Asset Management After you plan your installation and deployment approach.1 Quick Start Contains the Quick Start guide in all languages and a copy of the product information center. Instead of using DVDs. DVD or image file contents A set of DVDs contains the prerequisite middleware. you must do some further preparation. protocols.2010 19 .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.3. Middleware for Solaris 10 Contains middleware for Solaris 10. 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. and operating system environments are correctly installed and configured. Middleware for AIX V5. and the product code.Chapter 3. middleware fix packs. but before you install Maximo Asset Management. Middleware for HP UX 11g Contains middleware for HP UX 11g. The preparation includes ensuring that all hardware and software prerequisites are met. and that the ports. you can download the files that contain the DVD images from Passport Advantage®. 2007 .3 Contains middleware for AIX version 5.

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

Chapter 3. the deployment engine is installed in the system root directory of the Windows administrative workstation. IBM DB2 Minimum 20 GB disk space.A PING command issued from the administrative workstation must receive a response from each server used in the deployment. Preparing to install Maximo Asset Management 21 . An additional 6 GB of disk space must be available in the TEMP (or TMP) directory. 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. 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. 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. Ensure that each middleware host server is configured to respond to PING requests. this directory is C:\program files\ibm\acsi. On Windows systems. You must have 10 GB of disk space available on the administrative workstation to install Maximo Asset Management. but the deployment engine is always installed in the system root directory. You can specify that Maximo Asset Management is installed on a disk drive other than the C: drive.

For example.6 the browsers listed in column 1.For hardware requirements for software not listed here.ibm. Create file system links in a parent directory such as /opt/IBM/db2. because it is not able to rename it.1.1. errors occur during middleware installation of DB2.com/developerworks/ java/jdk/ Instruct your users to download and install the JRE before they start using the product. The JRE v1.6 can be downloaded at the following Web site: http://www. from IBM. Browser Software Operating System Any operating system that supports one of Microsoft Internet Explorer version 6 and 7. supports Microsoft Internet Explorer version 8. 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.5 is a file system link. All user computers that run Maximo Asset Management must have the Java Runtime Environment (JRE). Firefox version 3.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 (32–bit) Operating System Windows (32–bit) Windows (32–bit) Windows (32–bit) Windows (32–bit) 1074 MB Windows (32–bit) 22 Installation Guide: . if the directory /opt/IBM/db2/V9. refer to the product documentation provided with that product. 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. File systems The following table lists the disk space to allocate to each directory for the Maximo Asset Management installation process. installed. version 1. These directories do not exist before installing Maximo Asset Management.5 or 1. You must ensure that the parent directory of those directories have sufficient space available for the installation.6.5 or v1.Maximo Asset Management version 7. /opt/IBM or /opt.

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 (64–bit) Windows (64–bit) Windows (64–bit) Windows (64–bit) Windows (64–bit) DB2 2208 MB AIX Chapter 3.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 (32–bit) Windows (32–bit) Windows (32–bit) Windows (32–bit) 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 (64–bit) Windows (64–bit) Windows (64–bit) Windows(64–bit) 500 MB Windows (64–bit) 1074 MB Windows (64–bit) 1049 MB Installation programs Temporary space designated for use by the middleware installation program.Product File system Available Space Required (in MB) Operating System Windows (32–bit) Installation programs Temporary space 1049 MB designated for use by the middleware installation program. Preparing to install Maximo Asset Management 23 . 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.

Maximo Asset Management Various Deployment engine DB2 Workspace directory System temporary directory /usr/ibm/common/ acsi /opt/ibm/db2/V9.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.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: .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.5 The mount point for this path must be defined as /opt/ibm/db2 Linux (32-bit Intel®) only supports DB2 9.

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.1 deployment. Software Operating System v DB2 9. 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.1 FP6. DB2 9. Preparing to install Maximo Asset Management 25 .5 FP3a (installed by the middleware v Microsoft Windows Server 2003 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.

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 SUSE Linux Enterprise Server 9.0 for IBM System z (Manual installation only) 26 Installation Guide: .0 SP4 (32-bit) v SUSE Linux Enterprise Server 10.0 SP4 (64-bit) v SUSE Linux Enterprise Server 10.0 SP1 for IBM System z v SUSE Linux Enterprise Server 11.1 (AS and ES) for IBM System z v SUSE Linux Enterprise Server 9.0 (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 9.0 SP1 (32-bit) v SUSE Linux Enterprise Server 11.1 FP6 v Red Hat Enterprise Linux v4 (AS and ES update 4) (64-bit Intel) v Red Hat Enterprise Linux v5.0 SP4 for IBM System z v SUSE Linux Enterprise Server 10.0 SP1 (64-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 (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.

rte must be 9. Oracle patch set 3 (10.aix50. xlC.6 or 11.0.rte must be 9.3 TL 6 (64-bit kernel) IBM C++ runtime environment .0.1.rte 9.5 requires IBM C++ Run time Environment Components for AIX which includes xlC.com/systems/p/support/ index.html.1.0.1 TL 01 SP2 (64-bit kernel) IBM C++ runtime environment .1.0. Preparing to install Maximo Asset Management 27 .1 TL 01 SP2 (Manual installation only) AIX 6.1 TL 01 SP2 only supports Oracle 10g Rel2 v Oracle 11g at level 11.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). v AIX 6. Use the following commands to determine the C++ run time level for your system: lslpp -l | grep xlC. xlC.3 TL 6 (Manual installation only) IBM AIX 5.1.0.0.Software Operating System v AIX 5.0.3) must be installed. It is available at http://www. v IBM AIX 5.xlC.2.rte lslpp -l | grep xlC.aix61. v Oracle 10g Rel1 or Oracle 10g Rel2 at level 10.rte.1 or greater DB2 9. The lslpp command is used to display information about installed filesets or file set updates. Oracle patch set 3 (10. (Manual installation only) Red Hat Enterprise Linux v4 only supports Oracle 10g Rel1 or Oracle 10g Rel2 For Oracle 10G Rel1 .rte v Oracle 9i v2.1.0.7 Chapter 3.3) must be installed.rte lslpp -l | grep xlC.0.3 TL 6 only supports Oracle 10g Rel1 or Oracle 10g Rel2 For Oracle 10G Rel1 installed on a 64-bit systems.xlC.0.ibm.aix61.1 or greater v AIX 6.rte.aix50.0.

4) v HP-UX 11i v2 (PA-RISC only) v HP-UX 11i v3 (PA-RISC only) v Sun Solaris 10.2.1 (AS and ES) (IBM System z) (Manual installation only) (Oracle 10g Rel2 only with patch set 10.0.0 SP$ (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 10. v SUSE Linux Enterprise Server 11.0 SP1 for IBM System z (Manual installation only) SUSE Linux Enterprise Server only supports Oracle 10g Rel1 or Oracle 10g Rel2.0 (32-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 (32-bit) (Manual installation only) v SUSE Linux Enterprise Server 11.0 28 Installation Guide: .Software Operating System v SUSE Linux Enterprise Server 9.0 (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 9.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.0 SP4 (32-bit) (Manual installation only) v SUSE Linux Enterprise Server 10.0 SP1 (64-bit) (Manual installation only) v SUSE Linux Enterprise Server 11.

Preparing to install Maximo Asset Management 29 . SP 1 Standard or Enterprise version. SP 1 Standard or Enterprise version. Standard or Enterprise version. Operating System Microsoft SQL Server 2005 SP2. v Microsoft SQL Server 2008. v Microsoft SQL Server 2005. SP 2 Standard or Enterprise version. v Microsoft SQL Server 2008. 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.Software v Microsoft SQL Server 2005. This is where Maximo Asset Management runs. Chapter 3.1 deployment.

Software v WebSphere Application Server Network Deployment v6.1 (AS and ES) for IBM System z 30 Installation Guide: .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) (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) (32-bit Intel) v Red Hat Enterprise Linux v4 (AS and ES update 4) (64-bit Intel) v Red Hat Enterprise Linux v5.

0.xlC.1.0 SP1 (64-bit) v SUSE Linux Enterprise Server 11.0 SP1 for IBM System z v SUSE Linux Enterprise Server 11.Software Operating System v SUSE Linux Enterprise Server 9. xlC.0.0.29) v SUSE Linux Enterprise Server 9.3 TL 6 (64-bit kernel) IBM C++ runtime environment . 6.0 SP1 (32-bit) v SUSE Linux Enterprise Server 11.0 (32-bit) (Manual installation only) (requires fix pack 29.1 TL 01 SP2 (64-bit kernel) IBM C++ runtime environment .29) v AIX 5.0 for IBM System z (Manual installation only) (requires fix pack 29.0 SP4 (64-bit) v SUSE Linux Enterprise Server 10.rte must be 9.rte.0 SP1 (64-bit) (Manual installation only) (requires fix pack 29.0 SP4 (32-bit) v SUSE Linux Enterprise Server 10.aix50.1.xlC.1 or greater Chapter 3.aix61.rte must be 9.0.0 SP4 for IBM System z v SUSE Linux Enterprise Server 10.0.rte.0. 6.1 or greater v AIX 6. xlC. Preparing to install Maximo Asset Management 31 .0.1.29) v SUSE Linux Enterprise Server 9. 6.

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 TL 01 SP2 (64-bit kernel) (Manual installation only) v Sun Solaris 10. It can run on the following platforms.3 TL 6 (64-bit kernel) (Manual installation only) v AIX 6. 32 Installation Guide: .1 (AS and ES) (32-bit Intel) (Manual installation only) v AIX 5.Software Oracle WebLogic Server 9.0 Administrative system The administrative system is a required component of Maximo Asset Management.

Ultimate) (32-bit) v Windows Microsoft Windows XP Professional SP2 (32-bit. Enterprise. 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.1 deployment.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. Chapter 3. Preparing to install Maximo Asset Management 33 . but they are optional. HTTP server The following product can serve as the HTTP server component of a Maximo Asset Management 7.

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.0 SP3 for IBM System z v SUSE Linux Enterprise Server 10.1 (AS and ES) for IBM System z v SUSE Linux Enterprise Server 9.0 SP3 (64-bit) v SUSE Linux Enterprise Server 10.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.0 (32-bit) v SUSE Linux Enterprise Server 9.Software v IBM HTTP Server v6.0 SP3 for IBM System z 34 Installation Guide: .0 SP1 (64-bit) v SUSE Linux Enterprise Server 9.0 SP2 (32-bit) v SUSE Linux Enterprise Server 10.

to provide security for Maximo Asset Management.Software Operating System v AIX 5. Chapter 3.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.2 Interim Fix 2 (installed by the middleware installation program) and IBM Tivoli Directory Server v6. 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.1 deployment. Software v IBM Tivoli Directory Server v6.1 FP1 Operating System When WebSphere Application Server is the application server. Preparing to install Maximo Asset Management 35 . within WebSphere Application Server Network Deployment. IBM Tivoli Directory Server is configured to synchronize user information with Virtual Member Manager.

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

to provide security for Maximo Asset Management. so you do not need an SSH client to remotely configure middleware on Linux or UNIX systems. Maximo Asset Management does not support Active Directory on Windows Server 2008. by choosing to use port 139. without NetBIOS. Refer to the product documentation for Microsoft Windows Server 2003 Active Directory for support details. or for hosting 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. you must enable a remote access protocol for each system on which you intend to install the middleware. Remote configuration enablement If you plan to use Maximo Asset Management to automatically configure middleware. Windows SMB is a Windows protocol. Preparing for the installation You must prepare the environment before you install middleware or Maximo Asset Management. Note that while Windows Server 2008 is supported as a platform for the administrative workstation. Port 139 is used if Chapter 3. Alternatively. using SSH protocol. To perform any of the steps. you can configure SMB to use TCP/IP as the transport protocol. 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. The IBM JRE on the administrative workstation includes SSH. Operating System When Oracle WebLogic Server is the application server. Before you start the installation program. including ports 137 and 139. Preparing to install Maximo Asset Management 37 . within WebSphere Application Server Network Deployment. v Ensure that any ports that you use for remote protocols are not blocked by firewalls or security policies. 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. you must be logged in as a user with administrator privileges on Windows or as root on UNIX. Microsoft Active Directory can be optionally configured to synchronize user information with Virtual Member Manager. For remote Windows systems. by configuring it to use port 445. 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. But you must install OpenSSH on remote non-Windows workstations so that you can log on to them.Software v Microsoft Windows Server 2003 SP2 Active Directory Microsoft Active Directory Application Mode (ADAM) is not supported.

4.conf configuration file of the IBM HTTP Server. Handling SSL client authentication restrictions If you plan to install IBM HTTP Server. root) on the remote machines. v The Windows administrative share (C$) and the interprocess communications (IPC$) folder must be shared. Do not use OpenSSH 4. Shares must be shared for the Guest or Everyone accounts. the remote access protocols require the use of internal shell scripts that must be run within the korn (ksh) shell. disable client authentication before you start the installation Maximo Asset Management. Remote configuration does not support accessing network drives on the local or remote system. v For Windows systems that have User Account Control (UAC) enabled. 5. ensure that SSH is installed. 3. 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. even if the user ID that you use to log on to the remote system is configured to use a different shell. start Windows Explorer. 38 Installation Guide: . or if you change a deployment. Perform a backup of the deployment engine database before and after installing new applications.conf configuration file of the IBM HTTP Server. Stop and restart the IBM HTTP Server. disable password-protection. 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. and configure it to use SSL/TLS (https). and deselect the Use Simple File Sharing check box. Install Maximo Asset Management. v Ensure that a current version of OpenSSH is installed and running. v For Solaris systems. Solaris systems must have the ksh environment installed and properly configured. Procedure 1. Click Tools → Folder Options.5302. For remote Linux or UNIX systems. The installation programs fail if client authentication is enabled. v For Windows 2008 Server systems that support password-protected sharing. Add the SSLClientAuth Required directive back to the httpd. without NetBIOS. Consequently.SMB is configured to run on NetBIOS over TCP/IP. and port 445 is used if SMB is run directly on TCP/IP. The methods need ksh. Remove the SSLClientAuth Required directive in the httpd. v If you plan to remotely configure software on remote Linux or UNIX computers.0. 2.7. Stop and restart the IBM HTTP Server. 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. v To disable simple file sharing.

Preparing Linux and UNIX systems for Maximo Asset Management middleware If you intend to install middleware components on Linux or UNIX systems. About this task The product installation programs require read. Run the command to back up the Deployment Engine registry: Windows OS c:\Program Files\IBM\Common\acsi\bin\backupdb. A corrupted deployment engine database might prevent you from later installing a product that you need.cmd Linux or UNIX OS cd /var/ibm/common/acsi . Procedure 1. when it actually was not. /products/home. prepare the system environment before the middleware installation. Copy the backup file to your hard disk to restore the registry to an uncorrupted state. For example. but not completely. Procedure 1. the deployment engine database might record (register) that a product was installed.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. Log in to the system as a user with administrative authority on the system.sh 2. 2./setenv. after successfully installing Maximo Asset Management. and execute permissions for the /tmp and /home directories.cmd backup_file_name Linux or UNIX OS cd /usr/ibm/common/acsi/bin .About this task The backup can help you recover from partial installation attempts. Preparing to install Maximo Asset Management 39 . ensure that symbolic link directory also has the proper access. Set up the environment using the following command: Windows OS c:\Program Files\IBM\Common\acsi\setenv. for example. name the backup file DEBackupAfterMAMInstall. If one of these directories uses a symbolic link. Enter the following commands: #chmod 777 /tmp #chmod 777 /home Chapter 3. Accessing system directories Before using the middleware installation directory. write. where middleware or process manager components were partially installed. assign access permission to the /tmp and /home. Certain system parameters must be set to specific values to create an environment on the system that can accommodate Maximo Asset Management middleware. If an installation does fail./backupdb.

Edit the /etc/security/limits file by opening it in a text editor. so that the installation files can be extracted. If you have set a symbolic link to overwrite the native UNIX tar command with the GNU tar command. and also set the maximum allowable file size to unlimited. Because the native utility does not support long file names. root: fsize = -1 nofiles = 8192 3. A value of -1 for the fsize parameter indicates no limit. 2.14 or higher is installed. 5. you need to increase the default number of file descriptors allowed for the root user. you will encounter an error. You must log out as root and log back in for these changes to take effect. and then make changes to the parameters below using the values listed. the total amount of physical memory in the system. Verify that the system path variable contains both native UNIX tar and GNU tar paths. or.AIX tar command requirements The middleware installation program requires both the native UNIX tar command and the GNU version of the tar command. 40 Installation Guide: . the native tar utility is installed in /usr/bin and the GNU tar utility is installed in /opt/freeware/bin/tar. Procedure 1. For example.com/systems/p/os/aix/linux/ toolbox/download. with the GNU tar path being defined before the native UNIX tar path. About this task For Maximo Asset Management to function correctly. 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.html. 4. 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. preferably. You can download GNU tar from http://www. Save and exit the file. ensure that GNU tar version 1. Locate the section for the root user.ibm.

2. 6. To determine the current amount of paging space available to the server. and you can perform this task at any time before full operation of the product. Procedure 1. Click OK. 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. DB2 and Oracle database instances cannot be started successfully.Procedure 1. 5. 3. chps -s 10 hd6 adds 10 logical partitions to the logical volume hd6. Log into the system as a root (administrative) user. About this task This requirement is an operational requirement. Without asynchronous I/O. Open a terminal and run the following command: smit chgaio 3. 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. Enabling asynchronous I/O on AIX Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems. To increase paging space. Exit SMIT. 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. From the System Management Interface Tool (SMIT) dialog box. with a total of 5632 Mb of paging space available to the system. Preparing to install Maximo Asset Management 41 . To determine the size of a logical partition. You only need to perform this step if the system will host the IBM Tivoli Directory Server. there are a total of 44 logical partitions that are each 128 Mb in size. change STATE to be configured at system restart from defined to available. Run the following command from the command line: smit aio Chapter 3. For example. which results in adding 1280 Mb to the paging space. 4.

7. check the /usr/lib/ directory to determine if you have the libstdc+. Run rpm -qa | grep build 2. the rpm-build package is installed. In another failure scenario.so. verify that the rpm-build package is installed About this task To verify that the rpm-build package is installed. implement one of the following solutions: v Temporarily disable SELinux by using the setenforce 0 command. If the command returns a value. If this is the case. If you cannot locate this library on your system. the packcage is on disk 3 (of 5) of the Red Hat Enterprise Advanced Server version 4 installation CDs. If you receive this error. If nothing is returned. From the System Management Interface Tool (SMIT) dialog box. v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled.3. This solution. For Red Hat Enterprise Advanced Server.so. the package is on disk x of the SUSE Linux installation CDs.3. or other systems with SELinux enabled.5 system library is present on a Linux system. install the rpm-build package. For SUSE Linux. the Tivoli middleware installer will fail on RHEL 5 systems. you receive an error indicating that the Maximo Asset Management middleware installation program is unable to run in graphical mode. such as rpm-build-4. Restart the system to enable the changes.-18_nonptl. Checking for required libraries on Linux The Maximo Asset Management middleware installation program requires that the libstdc+. perform the following tasks: Procedure 1. select Configure Defined Asynchronous I/O. 8. About this task If this library is not installed. and then re-enable SELinux by using the setenforce 1command. run the install. Use the rpm tool with the -i option to install the package. Configuring the JRE in Linux About this task In some cases. Tivoli middleware installer will fail with an error message stating that the Java™ Runtime Environment (JRE) could not be found on the system. however.5 library installed. 42 Installation Guide: . implement one of the following solutions: v Manually issue the chcon -R -t textrel_shlib_t <install_dir/jvm/jre> command. Tivoli middleware installer will fail stating that it cannot find the VM. affects the level of security for the entire system. In one failure scenario. Verifying the required rpm-build package is installed Before you install the Maximo Asset Management middleware on a Linux system. If this is the case. and then click Enter. locate the RPM package for your system that contains this library and install the package.

set a minimum shared memory value for the system prior to installing the Maximo Asset Management middleware. From a command line. About this task For Linux systems. 3.shmmax and determine if the value is less than 268. type sysctl -w kernel. type ulimit -f unlimited 2. About this task Typically.435.conf Chapter 3. from a command line. From a command line. Update the value in /etc/sysctl. 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.456 bytes (256Mb). 2. type sysctl -w kernel.shmmax=268435456. Setting shared memory Set a minimum shared memory value in Linux systems to improve performance of Maximo Asset Management. to define user system and process resource limits.v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled.profile for the root user so that the ulimit setting will apply to all processes. Preparing to install Maximo Asset Management 43 . Procedure 1. This solution. Set the ulimit in the. About this task For Linux systems. Setting the ulimit Set the ulimit in Linux. set the ulimit for the system prior to installing Maximo Asset Management middleware. the swap size set for Linux systems must be the equivalent of twice the amount of physical RAM in the machine. 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. affects the level of security for the entire system. however. Procedure 1. If you want to increase the value.

The launchpad application assists you in choosing which product installation programs to install and indicates the order in which to install them. On Linux systems. Install language packs. or if your system does not 44 Installation Guide: . This step is necessary only if you need to support languages other than English. 2. Insert the launchpad DVD into a DVD drive.. The installation programs for these components are started from the launchpad. 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. the Firefox properties need to be modified. The DVD contains an autorun file. 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. 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. To complete an installation. Install and configure 3. Domain user logins are not supported. who has administrative privileges on the computer where Maximo Asset Management components are to be installed. 4. complete the following steps: Procedure 1. which can cause the launchpad program to start when you insert the launchpad DVD. perform the following tasks: 1. Log on as a local user. the launchpad runs in the Korn shell (ksh). If you are using Firefox. 2. where you can also access product information. Configure optional Maximo Asset Management middleware software products.Maximo Asset Management installation overview The installation process consists of several tasks that must be performed in sequence. To start the launchpad. If the autorun feature is disabled. Install and configure the required middleware.

If you have downloaded the product images. you must start the launchpad program. v AIX: The launchpad program uses the system default browser to run. before you start the launchpad program: typeset +r LOGNAME 2>/dev/null LOGNAME=lp_user_$$.support autorun. a.sh and remove the following lines. follow these steps to modify Firefox.exe (Windows systems) or launchpad. The launchpad. /user_dir). If the default browser on your system is Firefox. Modify /user_dir/launchpad/Firefox. b. rather than using physical media. Copy all of the files from disk 1 to a local directory (for example.sh (non-Windows systems) is in the root directory of the launchpad DVD. Preparing to install Maximo Asset Management 45 . download and extract the launchpad images as described in the download document. export LOGNAME Chapter 3. 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.

46 Installation Guide: .

2007 . the Maximo Asset Management installation program performs additional configuration tasks to complete the deployment. use one of the alternative deployment scenario. In this scenario. IBM Tivoli Directory Server. To deploy Maximo Asset Management with existing middleware. After these installations. Before you begin Ensure that you understand the system architecture and components and perform the planning and preparation tasks outlined in this guide.Chapter 4. the middleware installation program installs new instances of DB2. © Copyright IBM Corp. 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.2010 47 . and WebSphere Application Server Network Deployment that are provided with the product. Install and configure middleware using the middleware installation program. This deployment scenario is the simplest to implement. 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. 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.

choose one of the other deployment scenarios.5.5. If you want to install a new or existing SQL Server or Oracle database. 3. If you want to use Oracle WebLogic Server as your J2EE server. This scenario installs a new instance of IBM Tivoli Directory Server 6. – IBM HTTP Server Plugin 48 Installation Guide: . Verify the installation. This scenario installs a new instance of IBM WebSphere Network Deployment 6. 4. A directory server can be configured to secure the J2EE server deployment. v J2EE server The J2EE server is the application server that serves and manages the Maximo Asset Management application. follow the instructions in the manual deployment chapter. The Tivoli middleware installation wizard records the deployment and configuration parameters that you select in each screen. you can optionally perform the following tasks: v Install additional languages. follow the instructions in the manual deployment chapter.2. DB2 UDB 9. 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.2. The Tivoli middleware installer provides a set of IBM middleware products that you can install to deploy a Maximo Asset Management system. Complete post-installation tasks. What to do next After you complete the deployment. v Directory server Optional: You can use a directory server to secure the Maximo Asset Management J2EE application.2 with a new instance of DB2. and then installs and deploys the middleware based on this information. To install an existing instance of DB2 UDB 8.1. follow the instructions in the next chapter. 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 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. The Tivoli middleware installer installs a new instance of DB2 UDB 9. Install Maximo Asset Management and perform additional middleware configuration tasks. If you want to use Active Directory Server as your directory server.1. or DB2 UDB 9.

By default. Deployment of Maximo Asset Management with automatic configuration of new middleware 49 .You can install a new instance of IBM HTTP Server Plug-in to provide communications between IBM HTTP Server and the J2EE server. this file will have to be copied to the workspace of each machine where Maximo Asset Management middleware is being deployed. The deployment plan configuration files contain information about the deployment plan itself. This file is created and then updated after every deployment or undeployment. Chapter 4. and then configure the components selected as a single deployed application. Middleware installer workspace The middleware installer is designed to record the options you select during install in a directory referred to as the workspace. 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. which includes reconfiguring existing deployment choices. The workspace contains the following items: Deployment Plan The deployment plan is a collection of installation steps. The contents of this file can be used by the Maximo Asset Management installation program to populate its panels with meaningful default values. as well as any logs generated by the middleware installer process are located in the workspace. 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 deployment plan configuration files will be deleted and regenerated when the deployment plan is redeployed. the middleware installer cannot subsequently deploy additional features and products onto the machine at a later time. It is generated through the middleware installer and it resides in the workspace directory. Whenever a deployment plan is modified. choose an alternative deployment scenario. The composition and details of the deployment. 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. To deploy middleware on multiple computers. configuration parameters for those steps. the middleware installer deploys software on a single computer. the existing deployment plan is deleted and replaced with the new deployment plan. When deployment steps are changed. Once a plan has been deployed. and target machine information. The existing plan must first be completely undeployed through the middleware installer before a different set of features and products can be deployed. In this scenario. Topology File The topology file is a properties file that describes the configuration parameters of the Maximo Asset Management middleware deployment.

Ant is an open source software tool used to automate the software build process. Logs Log files that contain information about the deployment can be found in the workspace directory.6.5 JRE installed in order to execute a deployment plan outside of the Tivoli middleware installer. You must have Ant 1.5 and the Java 1. 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. log files native to the Maximo Asset Management middleware itself are also contained in this directory. This method of executing the deployment plan is recommended in most instances. When deployment choices are changed. Middleware deployment plan overview The deployment plan resides in the workspace directory and is generated from deployment choices selected in the Tivoli middleware installer. 50 Installation Guide: . 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. Activating the deployment plan After you generate the deployment plan using the information you entered in the Tivoli middleware installer.xml. Each step is responsible for installing and uninstalling one portion of the middleware. the existing deployment plan is deleted and replaced with the new deployment plan. you have several options for executing it. 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. 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.This file is saved in <workspace>/topology. In addition. you have the option to have the Tivoli middleware installer execute it. Ant uses XML to describe build tasks and dependencies. The plan is a series of deployment steps and configuration parameters. 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. Once the deployment plan has been generated using the information you entered in the Tivoli middleware installer. Create the plan using the Tivoli middleware installer and then have it execute the plan by installing and configuring the middleware selected.

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

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

#. The middleware installation program does not check for accented characters in user name values. % characters on Linux and UNIX OS. Values must begin with characters A through Z or a through z. $. The administrator name cannot contain leading and trailing spaces. Do not use: USERS. In most cases. The administrator password must consist of eight characters. Passwords cannnot contain the following special characters: ` ' \ " | WebSphere Application Server Network Deployment The administrator name cannot contain the following characters: / \ * . or SYS. or !.: . Values can include characters A through Z. Failing to escape special characters in an LDAP string used with Maximo Asset Management can cause errors. GUESTS. a through z. in LDIF files. Therefore.=+?|< > & % '"] [> # $ ~ ( ) ! The administrator name cannot begin with a period. Important: When entering LDAP values in the Maximo Asset Management installation wizard.Table 11. Ensure that the password values you provide are valid for your environment. SQL. Values must not include accented characters. if you mistakenly enter an LDAP string that Chapter 4. Middleware installation program The middleware installation program does not validate that your password is compliant with the operating system of the target host. The use of accented characters can cause errors. databases. Values cannot begin with IBM. Middleware object naming conventions (continued) Middleware object IBM Tivoli Directory Server conventions for users. and instances Description Do not use values that are longer than eight characters. You cannot use the '%' character on Windows OS. or idsldap as values. follow the product-specific syntax rules for using special characters in an LDAP string. you must precede special characters with an escape character in order to make it readable by the directory server. Do not use double-byte characters in administrator passwords. LOCAL. or into the directory server. groups. ADMINS. Deployment of Maximo Asset Management with automatic configuration of new middleware 53 . Many directory server products consider a blank space as a special character that is part of the LDAP string. PUBLIC. and 0 through 9.

and run the following command: launchpad. follow these steps: About this task 1. See the product documentation for your directory server for more information on special characters in LDAP strings. you must be logged in as a user with administrative authority (root).1”. Start the launchpad: Windows OS On the DVD titled “Maximo Asset Management 7.exe. or allow the middleware installation program to create a new user ID. If you run the middleware installation program from a Linux or UNIX terminal window. If you encounter the following error. If you are logged in as another user. you are prompted for user IDs to initiate the installation of DB2. navigate to the root directory of the product disc or the downloaded installation image.1”. Alternatively. and then restart the middleware installation program. You can either supply an existing system user ID. Login as a user with administrative authority. Linux or UNIX OS On the DVD titled “Maximo Asset Management 7. navigate to the root directory of the product disc or the downloaded installation image. and you do not precede the blank character with an escape character. 2.exe. WebSphere Application Server Network Deployment. at the end of a field value. and IBM Tivoli Directory Server. 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.contains a blank. you will encounter errors during the installation ofIBM Tivoli Directory Server.bat /l To install the prerequisite middleware products for Maximo Asset Management.exe) on a 32-bit Windows system. you will encounter Maximo Asset Management errors that will be difficult to troubleshoot. run the following command to automatically select the appropriate executable for the system: setupwin.sh. If the middleware installation program reports that you have insufficient disk space to install middleware. and plan to use the su command in order to use the shell of the administrative user. Launch the Tivoli middleware installer from the launchpad. and run the following command: launchpad. 54 Installation Guide: . When you run the middleware installation program. 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. During installation. a. it indicates that you are attempting to use the 64-bit middleware installation program executable (mwi-AMD64. the middleware installation program sets environmental variables that must be set for the administrative user. you must increase the available disk space on the system. for example.

The middleware installation program or one of the middleware products requires a fully-qualified host name defined. 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.Typically. Chapter 4. the middleware installation program files are copied from the media to a temp directory on the system.bat /l Linux or UNIX OS \mam_launchpad\Install\MWI\setupUNIX. The middleware installation program or one of the middleware products is not supported on this Linux kernel. 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. Windows OS \mam_launchpad\Install\MWI\setupwin. Check to ensure the specified file exists in the current directory. Deployment of Maximo Asset Management with automatic configuration of new middleware 55 . 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. Table 12. 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.sh -l The following errors can occur when using the setup scripts. 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. Currently only Red Hat and SuSE are supported. when you launch the middleware installation program from the launchpad.

so. 5. click Install the Product. 56 Installation Guide: . This topology file can be manually copied by the user to the workspace of the next machine in the topology. Select a language for the installation and click OK.so. Install the middleware. click Next to install the IBM Autonomic Deployment Engine. specify the directory you will use as the Tivoli middleware installer workspace. 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++.5. If no previous workspace location exists in the middleware user preferences node.so. If the selected directory does not exist. Click Next. If the system does not have this library installed. From the Choose Workspace panel. search for an RPM package (64-bit) compatible with system that contains this library and install it. It should be located in /usr/lib/libstdc++. Click the Middleware link under 1.so. search for an RPM package compatible with system that contains this library and install it. The installer requires libstdc++. Read the license information and select I accept both the IBM and the non-IBM terms if you agree with the terms. 34 The library libstdc++. 3. From the Welcome panel. click Next. The installer requires libstdc++.5 is not installed. it will be created. If the system does not have this library installed.5 (64-bit) is not installed. then the default location for the workspace will be C:\ibm\tivoli\mwi\ workspace for Windows and /ibm/tivoli/mwi/workspace for UNIX. After deployment. the Tivoli middleware installer also generates a topology file in this directory. From the Install IBM Autonomic Deployment Engine panel. The Tivoli middleware installer license agreement window is displayed.so. The default location for the workspace will be the last workspace location used by this user. In the launchpad navigation pane.5 (64-bit) It should be located in /usr/lib64/libstdc++.Table 12. 7. b. and then click Next. as specified in the middleware user preferences node. 6.5.5. so that information about the deployment of middleware will be available to the Tivoli middleware installer when it is executed on the next machine. 4. c.so.

or it is configured to support virtual IP addresses. In the Configurable Host Name panel. select the features to deploy on this machine. This feature should be selected to either install a new directory server locally or reuse a local directory server. The deployment plan is generated and you will be provided details about the plan. An IP address will result in an error message. If you elect to opt out of maintaining J2EE server through the use of the directory server. Deployment of Maximo Asset Management with automatic configuration of new middleware 57 . 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. Once this option has been selected. 9. When this option is selected. however. From the Deployment Plan Summary window. You cannot deselect this option once it has been selected. Directory Server The directory server is used to secure the J2EE Server. you will be unable to install the directory server through the Maximo Asset Management Middleware installation program. By default this option is selected. or an existing instance of Microsoft Active Directory. such as in cases where a system has more than one network interface. you will be able to change the value of the Hostname field. then you will be required to provide an alphanumeric value in the Hostname field. which will allow you to use the same password as the default user Chapter 4. See the Deployment of Maximo Asset Management with manual configuration of middleware for instructions. enter a password value. you can optionally select Use this password as the value for all subsequent passwords. you can supply the directory server you will use to secure it. you can change the value you enter in the Hostname field. 11. However. if you want to manually specify the host name of the machine you are running the installation from. to use it as your J2EE server you must install it manually. It must remain selected in order for you to enable the Directory Server option. From the Deployment Choices panel. Secure the J2EE Server using the Directory Server. If you choose to only install the J2EE server portion of the Maximo Asset Management middleware. Your choices are to secure with an existing instance of IBM Tivoli Directory Server. If you launched the middleware installation program from the command line using the forceHostname=true parameter. The Tivoli Middleware Installer does not install WebLogic Server. This option is useful when there is more than a single host name assigned to the system.8. you will not be able to deselect it. and then click Next. enter a value in the Hostname field. select the Override the local machine hostname option. Choices include: Database Server The Database Server stores information about the attributes and history of each asset and about the relationships between assets. click Next to configure the parameters displayed. In the password reuse panel. 10. This option allows you to use a directory server to secure the J2EE server. you are required to provide a resolvable host name. and then click Next. and then click Next. J2EE Server The J2EE server is the application server used to serve and manage the application.

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

14.2 Linux or UNIX OS: Default is /opt/IBM/ldap/V6. Default for all platforms is 50005. Enter information about the DB2 user groups: DB2 administrators group Enter the name of the DB2 administrators group. and then click Next. Enter the following configuration parameters for IBM Tivoli Directory Server. Chapter 4. Default for all platforms is ctginst1 Port Enter the port that the Maximo Asset Management database instance will use. 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.2 Administrator distinguished name Enter the distinguished name of the IBM Tivoli Directory Server administrator. Default for all platforms is cn=root. 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. Instance username Enter the user name for the Maximo Asset Management database instance. and then click Next. Windows OS: Default is C:\Program Files\IBM\LDAP\V6. Deployment of Maximo Asset Management with automatic configuration of new middleware 59 . Default is DB2USERS 16. Install location Enter the location to install IBM Tivoli Directory Server. Enter the following configuration parameters for the Maximo Asset Management database instance.Linux or UNIX OS: Default is db2inst1 Default Instance Username Password Enter the password for the default database instance user name. Instance name Enter the name of the Maximo Asset Management database instance. 15.

Default for all platforms is 50006.Administrator password Enter the password for the IBM Tivoli Directory Server administrator. 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. Administration secure port Enter the secure administration port number of the IBM Tivoli Directory Server. 18. Instance user password Enter the password for the instance user ID. Default for all platforms is o=IBM. and then click Next. Default for all platforms is 3539. Database name Enter the name of the DB2 database you are using to hold IBM Tivoli Directory Server data. Instance name Enter the name of the IBM Tivoli Directory Server database instance. Enter the following configuration parameters for WebSphere Application Server security. and then click Next. Default for all platforms is 3538. 19. LDAP Host Name Enter the host name of the system hosting the LDAP instance to use for WebSphere security. 60 Installation Guide: . Enter the following configuration parameters for IBM Tivoli Directory Server database instance. Organization and country suffix Enter the name of the IBM Tivoli Directory Server organization and country suffix to use with Maximo Asset Management. Directory server port Enter the port number of the IBM Tivoli Directory Server. Administration port Enter the administration port number of the IBM Tivoli Directory Server. Default for all platforms is 636.c=US. Default for all platforms is ou=SWG. Default for all platforms is idsccmdb. Directory server secure port Enter the secure port number of the IBM Tivoli Directory Server. Default for all platforms is 389. 17. Default for all platforms is security. Port Enter the port number used by the IBM Tivoli Directory Server database instance.

ou=SWG.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. and then click Next.ou=SWG. Deployment of Maximo Asset Management with automatic configuration of new middleware 61 . 22. Default for all platforms is wasadmin. Default is ou=users. Default is cn=root Bind password Enter the password for the bind distinguished name. LDAP base entry Enter the LDAP base entity of the LDAP instance to use for WebSphere security. Enter the following configuration parameters for WebSphere Application Server Version.o=IBM.c=US 20.Directory server port Enter the port number used by the LDAP server to use for WebSphere security.o=IBM. Default is ou=SWG. Default is 389. WebSphere Administrator password Enter the password for the WebSphere administrative account. Default is ou=groups. 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. Enter the following configuration parameters for WebSphere Application Server security. and then click Next.o=IBM.c=US Group suffix Enter the group suffix of the LDAP instance to use for WebSphere security. 21. Bind distinguished name Enter the bind distinguished name for binding to the LDAP instance. Chapter 4. and then click Next. Install location Enter the location to install WebSphere. Enter the following configuration parameters for WebSphere Application Server.c=US User suffix Enter the user suffix of the LDAP instance to use for WebSphere security.

Default for all platforms is MXServer Update Installer install location Enter the location where the WebSphere update installer will be installed. Enter the following configuration parameters for WebSphere Application Server. Default for all platforms is ctgNode01. and then click Next. Deployment Manager node name Enter the name of the WebSphere deployment manager node. 23. 62 Installation Guide: . and then click Next. Default for all platforms is ctgDmgr01. Application server node name Enter the name of the WebSphere application server node. Application server name Enter the name of the WebSphere application 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. Install location Enter the location to install IBM HTTP Server. 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. Default for all platforms is 80. Enter the following configuration parameters for IBM HTTP Server.Deployment Manager profile name Enter the WebSphere profile name of the deployment manager server. Default for all platforms is ctgCellManager01. Application server profile name Enter the WebSphere profile name of the application server. Admin Server port Enter the port to use to administer IBM HTTP Server. Default for all platforms is ctgAppSrv01. Cell name Enter the WebSphere Cell name. Default for all platforms is ctgCell01.

mwi. 27.log file is the high-level log file that was generated by the most recent invocation of the Tivoli middleware installer. the default profile name is ctgAppSvr01. If an error occurs. 28. You can also elect to make changes to the deployment plan or parameters you have previously configured from this panel. When the deployment completes successfully. From the Deployment Plan Operation panel. mwi. specify that directory. where X is a number. If you selected the option to specify a directory that already contained the middleware images. select Deploy the plan. and then click Next. review the contents of the summary. specify the source and destination directories. Middleware installer logs Tivoli middleware installer log files are located in the workspace directory that was defined in the Tivoli middleware installer. and then click Deploy to initiate the installation and configuration of the middleware you selected. click Next. and then click Next. examine this log file first.logX. Logs for steps run by the user interface In addition to collecting input from the user. Deployment of Maximo Asset Management with automatic configuration of new middleware 63 .log file from earlier invocations of the Tivoli middleware installer So. An entry in this log file may direct you to a lower-level log file. and then click Next. and so on. User interface logs The logs generated by the Tivoli middleware installer user interface are located in the workspace directory. 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. Log files named mwi. 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.log0 is produced after the first invocation of Tivoli middleware installer. 26. To accept the value. Specify a directory to use for Tivoli middleware installer temporary files and extracted middleware installation images. are copies of the mwi. for example. From the Deployment Plan and Parameter Configuration summary panel. The mwi.log1 is produced after the second invocation of Tivoli middleware installer. click Finish to exit the installation wizard.Default for all platforms is 8008. and then click Next. the user interface of the Tivoli middleware installer also performs several system checks. If you selected the option to copy install images from the source media. 31. In the Configuration Parameters for WebSphere Application Server plugin for the IBM HTTP Server. Specify the location of the Maximo Asset Management middleware images. 25. 30. Examples of system checks run by the user interface runs include: Chapter 4. and then click Next. 29. You cannot change this value. The different types of log files are described below.

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. where hostname is the hostname of the current system. The log files for the deployment plan are located in the subdirectory logs/processID.log. Each time the deployment plan is used to install or uninstall middleware products. a high-level log file that lists the steps invoked as part of the deployment plan. uninstall and checking work for the Tivoli middleware installer. The substeps perform the actual install. substepNum is the sequence number of this substep in the processing order of the step. The log files for the machine plan are located in the logs subdirectory. and substepID identifies the substep. 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. The primary log files for the machine plan are named MachinePlan_hostname_processID. where operation is the ANT target in the step ANT script that invokes this substep. usually including information about the input parameters and the substeps invoked. and check. Some steps may provide a message log file named stepID_processID. Logs for the deployment plan The deployment plan is located in the directory <Workspace Directory>/hostname/deploymentPlan. where stepNum is the sequence number of this step in install processing order of the deployment plan and stepID identifies the step.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 for the step are located in the logs subdirectory. which contains a few entries that summarize the result of invoking the step. The log files for the substep are usually located in a subdirectory named processID/logs. Logs for the machine plan The machine plan is located in the directory <Workspace Directory>/hostname/deploymentPlan/MachinePlan_hostname. uninstall. Logs for substeps Each step contains one or more substeps. These log files contain the output generated by ANT when running the machine plan ANT script. The primary log file for the deployment plan is DeploymentPlan.message. Typical values for operation are install. 64 Installation Guide: . All steps will provide a trace log file named stepID_processID.log. a process ID is assigned and log files are generated. Each substep is located in the directory <Workspace Directory>/hostname/ deploymentPlan/MachinePlan_hostname/stepNum_stepID/operation/ substepNum_substepID. which contains many entries.

Values that you supply to the IBM Maximo installation program are stored in the maximo. You can install middleware on any platform. used for first paragraph and abstract.Log files generated by the native middleware installation programs will also be kept here. To restore the defaults for a fresh installation. The program records deployment and configuration parameters that you select in each screen. the following values are set. Simple install path values Put your short description here.properties file. You will be able to provide values where indicated. Table 13. delete the old maximo. Installing Maximo Asset Management and automatically configuring middleware To automatically configure middleware when you install Maximo Asset Management follow these instructions. but you must run the IBM Maximo installation program from the administrative workstation which must be installed on a supported Windows system.properties file and the install. the install. You must also delete the information in the MAXTEMP table in the database. Deployment of Maximo Asset Management with automatic configuration of new middleware 65 . The IBM Maximo installation wizard guides you through the product installation. If you cancel the installation program after entering values in several screens. and in the Maximo database. 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. These values are retrieved and populated into installation screen fields if you run the installation program again. Values that are not reused are the installation directory and the shortcut option you chose for a previous installation.properties file.properties file which are stored in the MAM_HOME/maximo/ applications/maximo/properties/ directory. and then installs and deploys the product based on this information. If you elect to install Maximo Asset Management using the simple install path. the installation program reuses most of those values the next time you start the installation program.

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.

using default values. 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 . Before you begin Before you start the installation program. ensure that the system meets the following conditions: v On the administrative workstation. Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware 67 .Table 13. Running the Maximo Asset Management installation program Use these instructions to install Maximo Asset Management and automatically configure middleware on multiple servers. 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. such as anti-virus software. temporarily shut down any non-critical processes that could have a negative effect on the installation.

On a 32-bit Windows system. navigate to the directory where the Maximo Asset Management files are extracted. rexec. ensure that the Cell and all related nodes are actively running. and you intend to install the product on the same system. To create a maxdemo database. You can create a maxdemo database. 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. SSH and Windows SMB. If the remote system is a Windows server. See the DB2 product documentation for information about creating a user with SYSADM (administration) authority on the DB2 server.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes v When you are running the installation wizard. including sample data. – To avoid high system memory usage by DB2. during the installation. run the following command: install. you must configure remote execution and access to use SMB. Remote access protocols include rsh. manually configure the database. Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server. you must create the instance user and the home directory for the user on the DB2 server. Change to the install\MAM\Install\new folder. Automatic configuraton creates an empty Maximo database on the system. you must either run the Maximo Asset Management installation program in English. v Enable a remote execution and access service on every system with middleware installed. See the Troubleshooting chapter for instructions on restarting middleware if you need to do so. redefine these variables before you begin the product installation. 3. – If you are plan to install Maximo Asset Management in a language other than English. complete either of following two procedures: v Enter a command to create a maxdemo database: 1. run the following command: install_win64.v The middleware environment is installed and running properly. create a maxdemo database by performing the following tasks: 68 Installation Guide: . v Perform the following tasks to prepare the DB2 database: – If DB2 is installed on a Linux or UNIX system. – The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. v The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed into that location. 2. – The user ID for the DB2 instance administrator must have SYSADM (administration) authority. 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.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes d On a 64-bit Windows system. In the command line. or modify the table space sizes after installation. You enter this user ID on the DB2 Administration screen and on the Remote Access Authorization screen of the Maximo Asset Management installation program. If you want to customize the table space sizes. v For WebSphere Application Server Network Deployment.

Rename the ibm\smp\maximo\tools\maximo\en\maximo file. Click Maximo Asset Management. To avoid this problem. directory server. In the launchpad navigation screen.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. 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. Start the launchpad. where en is the language folder and dbtype is ora/sqs/db2. 2. and application server services are running. If you are installing on a system using a system ID that contains Russian language characters. Log in as Administrator on the Maximo Asset Management administrative system. 6. review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. Ensure the database server. r 7. When taskrunner successfully completes.. Chapter 4. Deployment of Maximo Asset Management with automatic configuration of new middleware 69 . Copy the ibm\smp\maximo\tools\maximo\en\maxdemo file to ibm\smp\maximo\tools\maximo\en\maximo. click Install the Product. 3. 3. a. 4. Start the Maximo Asset Management installation program from the launchpad. select the Copy files now. 5. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations. exit the installation wizard. When you are installing the product. See the troubleshooting chapter for information about errors that occur during the installation. From a command prompt navigate to ibm\smp\scripts and run the following command: taskrunner. c. Navigate to the root directory of the product DVD or the downloaded installation image. When taskrunner finishes running. 2. In the Run Configuration Step screen in the installation wizard (Step 31 in the procedure).exe b. About this task To install Maximo Asset Management. follow these steps: Procedure 1. install the product using a user ID with administrative authority that contains only English language characters. Perform installation configuration later option. When the installation finishes. This circumstance causes a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E.1. and run the following command: launchpad. rename the files back to their original names. the installation fails with error message CTGIN2289E when attempting to install language packages. specify the fully-qualified host name of the system for all host name values.

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

this user must be a member of the DB2ADMNS group. 12. For example. 14. enter authorization information for the automatic database configuration feature. Host name Enter the fully-qualified host name of the server hosting DB2. Instance Enter the name of the database instance to be used with Maximo. In the Database screen. enter configuration information about the database. C:\ibm\tivoli\mwi\workspace for Windows and /root/ibm/tivoli/mwi/workspace for UNIX. The default is 50005.Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. This instance is created if it does not exist. and then click Next. This user ID is created if it does not exist. The default instance name is ctginst1. In the Remote Access Authorization screen. In the Database Type screen. select Automate database creation and configuration. In the Automate Database Configuration screen. The database is created if it does not exist. Database User ID Enter the user ID used for Maximo to access DB2. 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. After you enter configuration information for the database. and then click Next. the Maximo Asset Management installation program connects to the database server to validate the information you have entered. For Windows OS. The default database name is maxdb71. Chapter 4. and then click Next. the user and its associated home directory must exist on the DB2 server. select the DB2 database. Database Name Enter the name of the database to use with Maximo. and then click Next. This user ID cannot be the same one used as the instance administrator user ID. Port Enter the port being used by DB2 instance. 13. 11. This file is found in the workspace that was defined during the middleware installation task. Database Password Enter the password for the user ID used to access DB2. This user ID must have administrative rights on the server you are accessing. Deployment of Maximo Asset Management with automatic configuration of new middleware 71 . however. Default for all platforms is maximo.

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

20. and then click Next. In the WebSphere Deployment Manager Configuration panel. In the Automate WebSphere configuration panel. you can provide the IP address for the system. The Maximo Asset Management installation program now connects to the database server and validates the information you entered. Host name Enter the fully-qualified host name of the system hosting WebSphere Application Server Network Deployment. 21. and then click Next. and then click Next. WebSphere installation directory Enter the directory where WebSphere Application Server Network Deployment is installed on the host system. for the index table space. For all platforms. In the WebSphere Remote Access Authorization panel. In the WebSphere Connectivity panel. 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. 18. The default value for this field is 8879. enter values for the following fields. select WebSphere Application Server Network Deployment as the application server to use. the default is MAXDATA. enter authorization information for WebSphere Application Server Network Deployment configuration. in megabytes. Alternatively. The default value is 1000 Mb.Temporary tablespace size (Mb) Enter a size for the temporary table space. Operating system password Enter the password for the system user ID. 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. Index tablespace size Enter a size. and then click Next. SOAP port Enter the SOAP port of the WebSphere Application Server Network Deployment system. in the Application Server Type panel. select Automate WebSphere configuration. Deployment of Maximo Asset Management with automatic configuration of new middleware 73 . When the database validation is completed. 19. This user ID should have administrative rights on the server you are accessing. and then click Next. 17. Index tablespace name Enter a name for the index table space. enter host information about the 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 ctgNode01. Default for all platforms is wasadmin. The application server is created if it does not exist. 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. This option requires application security to already be enabled in WebSphere Application Server Network Deployment. 23. Application server Enter the name of the WebSphere Application Server Network Deployment application server to associate with Maximo Asset Management. 22. but you manage their membership in security groups in the base services Security Groups application. Default for all platforms is ctgDmgr01. Default for all platforms is MXServer. This value can be customized. enter the following information. In the WebSphere Application Server Configuration panel. This option requires application security to already be enabled in WebSphere Application Server Network Deployment.User ID Enter the administrative user ID used to access the WebSphere Application Server Network Deployment Server. With this option. Web server port Enter the Web server port used by WebSphere Application Server Network Deployment. Profile name Enter the name of the WebSphere Application Server Network Deployment profile. 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. select a method for authenticating and authorizing users and groups. 74 Installation Guide: . Default for all platforms is webserver1 Node name Enter the name of the WebSphere Application Server Network Deployment node containing the application server. you create all your users in your directory server. and then click Next. Password Enter the password for the administrative user ID used to access the WebSphere Application Server Network Deployment Server. In the Security panel. and then click Next.

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

c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm. enter the following information. and then click Next.o=IBM.ou=SWG.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin.ou=users.ou=SWG.ou=SWG. In the Integration Adapter JMS Configuration screen.ou=users. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask.ou=SWG. o=ibm. JMS Data Source name Enter intjmsds as the name of the data source to be used by JMS.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin.ou=users.o=IBM. o=ibm.If you do not want to have the users created by the Maximo Asset Management installation program.c=US member: uid=maxreg.ou=users. Select whether the JMS data store should be persisted.ou=users.o=IBM. you must create it yourself before advancing beyond this panel.ou=users.c=US member: uid=mxintadm.ou=SWG. 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.ou=users. dn: uid=maxadmin.c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg dn: cn=maxadmin. o=ibm.ou=SWG.ou=SWG. 76 Installation Guide: .c=US cn: maxadmin dn: cn=maximousers. A JMS server requires a DB2 data repository to be configured to maintain messages.c=US cn: maximousers 26.ou=SWG.ou=SWG.o=IBM.ou=SWG.ou=groups. you will have to create them manually before continuing the Maximo Asset Management installation from this point. o=ibm. If you are not using the default LDAP schema provided with Maximo Asset Management.c=US member: uid=mxintadm.o=IBM.ou=groups.ou=users.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg. o=ibm.

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

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

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. copying files to your local system. See the instructions for manually configuring WebSphere Application Server in the Deployment of . 32.Maximo Asset Management with manual configuration of middleware.The Maximo Asset Management installation program is used to complete three tasks: gathering information about your Maximo Asset Management deployment and configuration. Files can be deployed once all products have added their own functions to the application files. Deployment of Maximo Asset Management with automatic configuration of new middleware 79 . If you intend to use the taskrunner utility. Chapter 4. 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. In the Choose Shortcut Folder panel. 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. and then click Next. and performing configuration tasks using the values you have specified. b. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. By selecting this option. located in the <MAM_HOME>\scripts directory. If you run taskrunner with the NOSTOPONERROR parameter. and then allow you to run the configuration step at a later date. the taskrunner continues despite errors.properties file to configure Maximo Asset Management. Deploy application files manually later Select this option to defer the deployment of application files. <MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR> Note: If you reboot the system. Taskrunner data stores are not persisted. Run the taskrunner utility from the command line. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. In the case of an installation failure. The configuration values that you enter are stored in the <MAM_HOME>maximo\applications\maximo\properties\ maximo. select the type of shortcut you would like to arrange for Maximo Asset Management. the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. you are not able to use the taskrunner utility to run configuration scripts. 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. You can run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility. and it uses the configuration values stored in the maximo. Choose how to deploy application files.properties file. do not reboot your system.

install the language pack before performing other configuration tasks. and then click Install. it will exit. review the installation information presented. In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. click Done. The chapter also describes how to install process solution packages. Completing post-installation tasks To complete the deployment. Use the Previous button to return to previous panels to make changes. In the Pre-Installation Summary panel.. and then click Next. Other Select this option and use the Choose. 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. 34. Progress can be monitored by viewing messages displayed above the progress bar. review the information you have provided to the Maximo Asset Management installation program. In the Install Complete panel.In an existing Program Group Select this option and choose the name of an existing program group to store Maximo Asset Management shortcuts. 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. See the Deployment of optional packages chapter for language pack installation instructions. The installation task begins. The Post-installation configuration chapter describes the configuration tasks to complete within the product user interface. In order to use the Start Menu shortcut with Internet Explorer. In the Input Summary panel. 35. In the Quick Launch Bar This option must not be used. If you intend to support multiple languages in Maximo Asset Management. Selecting this option does not create a shortcut in the Quick Launch bar. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. Do not select this option. including process manager products and integration modules. 80 Installation Guide: . you must perform several additional tasks after the installation. 33. On the Desktop Select this option to create shortcuts for Maximo Asset Management on the desktop. What to do next When the Maximo Asset Management installation program has completed installation and configuration tasks.. button to select another location to create Maximo Asset Management shortcuts.

bat <WASDeploymentManagerHostName> <WASRemoteAccessUserName> <WASRemoteAccesspassword> "<MaximoInstallLocation>\applications\maximohelp \helpweb\webmodule\WEB-INF\confhelp. Before you begin About this task To deploy the confhelp. or a health check. Deployment of Maximo Asset Management with automatic configuration of new middleware 81 . where XX is a two digit number such as 00.log file.properties" Verifying the installation After you have exited the Maximo Asset Management installation program without encountering any errors.log file for success messages. by logging into the product before exiting the installation. The product installation program returns a success message if all installation steps. Run the following command: <MAM_HOME>\jacl\solutions\Sendfile. refer to “Troubleshooting the product installation program” on page 239.Deploying the confhelp. you can further verify that the installation completed successfully by locating key artifacts and performing a few simple tasks. complete the following steps: Procedure 1.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.properties file must be deployed to enable the help system for the product. are successful. 2.properties" "<WASInstallLocation>\properties" "confhelp. The following success messages are found in the CTGInstallTrace00. If the health check task is unsuccessful. including the product log in task.properties file The confhelp. For more information about log files and troubleshooting errors encountered during the installation. Examine the CTGInstallTrace00. Before you begin The product installation program performs installation verification.properties file. perform the following verification procedures: Procedure 1. a HealthCheckFailed error thrown for the getUrlContentString function will be found in the <MAM_HOME>\logs\CTGInstallTraceXX. About this task To further verify that the Maximo Asset Management installation was completed successfully. Ensure you are logged into the administrative workstation.

maxinst.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. indicate the configuration was successful: <symptom>CTGIN2228I. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages that will be installed.bat -action showInstalled -all The resulting list should match the packages listed in the Package Summary panel.bat <MAM_HOME>\bin\solutionInstaller.*client</symptom> <symptom>CTGIN2230I. 3. found in the CTGInstallTrace00.*security</symptom> Search the CTGInstallTrace00. the following messages.*node</symptom> <symptom>CTGIN2232I.*NodeAgent</symptom> <symptom>CTGIN2240I. Use the solutioninstaller command to list installed packages: <MAM_HOME>\bin\setupPSIenv.*completed 2.*server</symptom> <symptom>CTGIN2238I. navigate through the GoTo menu to verify that it has been populated with the applications you expect. 82 Installation Guide: .log file for the following message. Once you have logged in.) 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. which indicates that the maxinst task completed successfully: CTGIN2079I. You can compare the contents of that panel with a listing of what was actually installed on the system. Log into the product and verify applications are present.log file.v CTGIN2079I: Base services database configuration completed successfully (This message indicates that maxinst finished successfully. Being able to log into the product manually is a good indicator that the installation was successful. Compare the packages chosen for installation with the packages that were installed.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMO was successful v CTGIN2253I: buildhelpear.

2007 . 3. Deploying Maximo Asset Management reusing existing middleware Procedure 1. 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.2010 83 . 2. 4. About this task In this scenario. Install Maximo Asset Management and perform additional middleware configuration tasks. Complete post-installation tasks © Copyright IBM Corp. Verify the installation. Before you begin Review the information in the planning and preparation chapters. including completing the planning worksheets. Install and configure middleware using the middleware installation program. you use the middleware installation program and the Maximo Asset Management installation program to automatically configure existing middleware resources before deploying the product itself. 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.Chapter 5.

See the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions. With the Tivoli middleware installer. or a Microsoft Active Directory server and configure them automatically 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. 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. you can reuse an existing DB2 server. such as an Oracle Database. for example. or a Microsoft SQL Server. If you want to reuse other middleware components. an Oracle WebLogic Server. Before using the middleware installation program to configure an existing DB2 server. You can manually configure these components.DB2 8. an IBM Tivoli Directory Server. you must configure them before you run the Maximo Asset Management installation program. See the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions. you must configure them manually. The middleware installation program can identify components that exist on the system that are compatible with Maximo Asset Management.2. you must create a set of users and groups that are used by the middleware installation program during configuration.2 in your deployment. if your enterprise has security policies that prohibit automatic configuration. You must use a later version of DB2 if you want to use IBM Tivoli Directory Server 6.2 is incompatible with the IBM Tivoli Directory Server 6. 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: . Reusing DB2 You can use the Tivoli middleware installer to configure an existingDB2 server for use with Maximo Asset Management.What to do next After you complete the deployment. and can configure them for use with Maximo Asset Management If you intend to reuse middleware servers. you can optionally perform the following tasks: v Install additional languages.

select onlyDatabase Server. v The IBM Tivoli Directory Server is running. you must create it before running the middleware installer. In the Deployment Choices screen. LDAP BASE DN. To reuse an existing instance of IBM Tivoli Directory Server. Complete the installation by navigating the remaining screens in the installation wizard. 3. About this task To use the middleware installation program to configure an existing instance of DB2 for reuse with Maximo Asset Management. Login as a user with administrative authority. the database instance is restarted.v dbgrp1 ((Linux or UNIX OS) v db2fgrp1 ((Linux or UNIX OS) These are default values which you can customize. Launch the middleware installation program from the launchpad. v The Base DN information that you supply in the middleware installer screens is present in the IBM Tivoli Directory Server you are using. Reusing IBM Tivoli Directory Server If you want to reuse an existing IBM Tivoli Directory Server installation with Maximo Asset Management. Navigate the screens of the installation wizard until you reach the Deployment Choices screen. The middleware installation program displays any instances of DB2 that it finds on the system. The middleware installer does not create a new instance of IBM Tivoli Directory Server for use with Maximo Asset Management. If these users do not exist on the system. which could disrupt the availability of IBM Tivoli Directory Server in your enterprise. If you are using the automated installers. 6. and then click Next. separate instances are created for use by Maximo Asset Management and IBM Tivoli Directory Server. ensure that you provide matching values when you run the middleware installation program. Deployment of Maximo Asset Management with automatic configuration of existing middleware 85 . From the Installation drop-down menu. and then click Next. and the administration port information for that instance on the middleware installer panels when prompted. 2. you must create them before running the installation program. If you use different values. To host a new instance on your existing IBM Tivoli Directory Server. it is not a recommended practice. 4. supply the correct Administrator Distinguished Name and password. Chapter 5. you can verify that it will work with Maximo Asset Management using the middleware installer. 5. About this task The middleware installer validates the following items: v The version of IBM Tivoli Directory Server is compatible with Maximo Asset Management. complete the following steps: Procedure 1. Note: While you can technically share a DB2 instance between Maximo Asset Management and the one required by IBM Tivoli Directory Server. During the installation. select the instance you want to reuse. directory server port.

Navigate the installation wizard screens until you reach the Deployment Choices screen. 3. In the Installation drop-down menu. Select this option only if you want to manually 86 Installation Guide: . In the Deployment Plan Summary screen. Launch the middleware installer from the product launchpad. In the Deployment Choices screen. To use an existing Microsoft Active Directory instance to secure WebSphere Application Server Network Deployment. Login as a user with administrative authority. select Directory Server. 5. 6. and then click Next. and then click Next. Navigate the screens of the installation wizard until you reach the Deployment Choices screen. and then click Next. select the Override the local machine hostname option and enter a host name value in the Hostname field. complete the following steps. Complete the installation by navigating the remaining installation wizard screens. you must manually create the necessary users and groups. Before you begin Before running the Maximo Asset Management installation program. select the instance that you want to reuse. 4. In the Deployment Choices panel. 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 verify an existing instance of IBM Tivoli Directory Server for reuse with Maximo Asset Management. The middleware installer displays any instances of IBM Tivoli Directory Server it finds on the system. 2. In the next screen. The deployment plan is generated and details of the plan are provided. if you want to manually specify the host name of the machine you are running the installation from. 3. You can perform this task after you run the middleware installation program. click Next to configure the parameters. 5. Optional: In the Configurable Host Name screen. select the Microsoft Active Directory to secure WebSphere Application Server Network Deployment option. complete the following steps: Procedure 1. PreparingMicrosoft Active Directory for reuse If you have an existing instance of Microsoft Active Directory. 2. Procedure 1. select only the Directory Server deployment option. Log into the system as a user with administrative authority. you can use it to secure WebSphere Application Server Network Deployment when you install it on the system. 4. 6. Launch the middleware installation program from the launchpad. and then click Next.

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

When the user interface runs a step.log. for example. it copies the step into a subdirectory of the workspace directory. a process ID is assigned and log files are generated. If an error occurs. where X is a number. Log files named mwi. 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. 88 Installation Guide: . Logs for the deployment plan The deployment plan is located in the directory <Workspace Directory>/hostname/deploymentPlan. The log files for the machine plan are located in the logs subdirectory. An entry in this log file may direct you to a lower-level log file. are copies of the mwi. The primary log file for the deployment plan is DeploymentPlan. User interface logs The logs generated by the Tivoli middleware installer user interface are located in the workspace directory. Logs for the machine plan The machine plan is located in the directory <Workspace Directory>/hostname/deploymentPlan/MachinePlan_hostname. where hostname is the hostname of the current system. a high-level log file that lists the steps invoked as part of the deployment plan. examine this log file first.logX. The mwi. mwi. 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.log1 is produced after the second invocation of Tivoli middleware installer.Middleware installer logs Tivoli middleware installer log files are located in the workspace directory that was defined in the Tivoli middleware installer. the user interface of the Tivoli middleware installer also performs several system checks.log0 is produced after the first invocation of Tivoli middleware installer. The log files for the deployment plan are located in the subdirectory logs/processID. and so on.log file from earlier invocations of the Tivoli middleware installer So. Logs for steps run by the user interface In addition to collecting input from the user. Each time the deployment plan is used to install or uninstall middleware products. 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. The different types of log files are described below.log file is the high-level log file that was generated by the most recent invocation of the Tivoli middleware installer. mwi.

and check. substepNum is the sequence number of this substep in the processing order of the step. Some steps may provide a message log file named stepID_processID. v Enable a remote execution and access service on every system with middleware installed. Reusing middleware with the Maximo Asset Management installation program Use these instructions to install Maximo Asset Management and automatically configure middleware on multiple servers. usually including information about the input parameters and the substeps invoked. v If you experience problems with the user interface of the installation program when installing on AIX 6 systems remotely. temporarily shut down any non-critical processes that could have a negative effect on the installation. where operation is the ANT target in the step ANT script that invokes this substep. Before you begin Before you start the installation program. and substepID identifies the substep. See the Troubleshooting chapter for instructions on restarting middleware if you need to do so. Typical values for operation are install. Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server. ensure that the system meets the following conditions: v On the administrative workstation. Each substep is located in the directory <Workspace Directory>/hostname/ deploymentPlan/MachinePlan_hostname/stepNum_stepID/operation/ substepNum_substepID. Logs for substeps Each step contains one or more substeps. The log files for the substep are usually located in a subdirectory named processID/logs.log. reattempt the installation locally on the system through the console or an x terminal. The log files for the step are located in the logs subdirectory. v The middleware environment is installed and running properly. consult the documentation for your operating system to ensure this. Log files generated by the native middleware installation programs will also be kept here. Deployment of Maximo Asset Management with automatic configuration of existing middleware 89 . such as anti-virus software.message. If necessary.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. All steps will provide a trace log file named stepID_processID. uninstall and checking work for the Tivoli middleware installer. uninstall. The substeps perform the actual install. which contains many entries. using default values. v For Linux or UNIX systems with middleware installed. which contains a few entries that summarize the result of invoking the step. where stepNum is the sequence number of this step in install processing order of the deployment plan and stepID identifies the step. Chapter 5. the command hostname -f must return a fully-qualified host name.

redefine these variables before you begin the product installation. ensure that the Oracle 10gR2 patch 3 is installed. 90 Installation Guide: . v If you are using Oracle 10 with Maximo Asset Management. When you are installing the product. or modify the table space sizes after installation. – Enable port 1433 which is the port used by Maximo Asset Management when configured with Microsoft SQL Server. v Perform the following tasks to prepare Microsoft SQL Server 2005: – Ensure that the Microsoft SQL Server 2005 service pack 2 is installed. you must configure remote execution and access to use SMB. 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. you must configure SSL and manually create users on the Microsoft Active Directory instance. – The user ID for the DB2 instance administrator must have SYSADM (administration) authority. v Perform the following tasks to prepare the DB2 database: – If DB2 is installed on a Linux or UNIX system. – To avoid high system memory usage by DB2. Automatic configuration of Oracle 9 is not supported. If you plan to use Oracle 9 in the Maximo Asset Management system. 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. you must create the instance user and the home directory for the user on the DB2 server. and you intend to install the product on the same system. manually configure the database. If the remote system is a Windows server. v If you plan to use Microsoft Active Directory to secure WebSphere Application Server Network Deployment. follow the instructions in the Deployment of Maximo Asset Management with manual configuration of middleware chapter. By default. SSH and Windows SMB. – If you are plan to install Maximo Asset Management in a language other than English. Consult the Microsoft SQL Server for information on enabling the port. rexec.. specify the fully-qualified host name of the system for all host name values. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations. you must either run the Maximo Asset Management installation program in English. this port is not enabled. – The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. If you intend to perform multiple installations of the product using the same administrative workstation.Remote access protocols include rsh. review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. 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. ensure that the Cell and all related nodes are actively running. If you want to customize the table space sizes. 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.

this value is C:\IBM\SMP. Click Maximo Asset Management. 7. and then click Next.If you are installing on a system using a system ID that contains Russian language characters.exe b. To avoid this problem. click Install the Product. By default. This circumstance causes a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E. The path you specify must not contain spaces. and then click Next. A simple installation does not support reuse of middleware. proof-of-concept. select the Custom option. you can start the Maximo Asset Management installation program directly. Select a language for the installation and click OK. Start the Maximo Asset Management installation program from the launchpad. See the troubleshooting chapter for information about errors that occur during the installation. a. and then click Next. In the launchpad navigation screen. click Next. Deployment of Maximo Asset Management with automatic configuration of existing middleware 91 . install the product using a user ID with administrative authority that contains only English language characters. In the Choose Install Folder screen. 3. or training purposes only. About this task To install Maximo Asset Management. read the license information and select I accept both the IBM and the non-IBM terms. In the Choose Deployment screen. and run the following command: launchpad. This deployment option is typically used for demonstration. Simple A simple installation deploys all Maximo Asset Management components on a single system. In the software license agreement screen. c. the installation fails with error message CTGIN2289E when attempting to install language packages. 5. specify the install directory for Maximo Asset Management. 8.exe v install_win64. In the Package Summary screen. In the Introduction screen. follow these steps: Procedure 1. Custom A custom installation can deploy Maximo Asset Management Chapter 5. and then click Next. Navigate to \\Install\MAM\ on the product DVD or on the downloaded installation image and run one of the following commands: v install. Where Would You Like to Install? Enter the path to install Maximo Asset Management. 2. 6. if you agree with the terms. directory server. review the package deployment actions. Ensure the database server. Navigate to the root directory of the product DVD or the downloaded installation image. Alternatively. and application server services are running.exe 4. Start the launchpad. Log in as Administrator on the Maximo Asset Management administrative system. 9.

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:

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

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

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

ou=SWG.c=US member: uid=mxintadm.ou=users.o=IBM.ou=SWG.o=IBM. this field is pre-populated. 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. you will have to configure the JMS implementation manually. If you select this option.o=IBM. In the Integration Adapter JMS Configuration screen. enter the following information.ou=users. If you later decide that you would like to persist JMS messages.o=IBM. If you are using another database type. o=ibm.ou=SWG. If it is not. A JMS server requires a DB2 data repository to be configured to maintain messages. enter intjmsds.ou=users. Select whether the JMS data store should be persisted. 100 Installation Guide: . where you configure SMTP.ou=users. If you select this option. the installation wizard skips to Step 30.ou=users.ou=SWG.ou=groups. If you are using Microsoft SQL Server or Oracle. o=ibm.ou=users.ou=SWG. the installation wizard guides you through additional JMS configuration screens.userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin.c=US cn: maximousers 26.c=US member: uid=mxintadm.ou=groups.o=IBM.c=US cn: maxadmin dn: cn=maximousers.ou=SWG. you must manually configure message persistence.ou=SWG.c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg dn: cn=maxadmin. and then click Next.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin. 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.ou=SWG. JMS Data Source name Enter the name of the data source to be used by JMS. o=ibm.c=US member: uid=maxreg.

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

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

In the case of an installation failure. Note: Shortcuts are created for Windows systems only. 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 the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. Choose how to deploy application files. Files can be deployed once all products have added their own functions to the application files. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. 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.Note: If you reboot the system. do not reboot your system. Deploy application files manually later Select this option to defer the deployment of application files. See the Deployment of Maximo Asset Management with manual configuration of middleware chapter for instructions to manually deploy WebSphere Application Server. you are not able to use the taskrunner utility to run configuration scripts. 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. Note: Because deployment on WebLogic Server systems is a manual process. If you intend to use the taskrunner utility. the taskrunner continues despite errors. select the type of shortcut you would like to arrange for Maximo Asset Management. Chapter 5. 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. b. Taskrunner data stores are not persisted. 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. In order to use the Start Menu shortcut with Internet Explorer. If you run taskrunner with the NOSTOPONERROR parameter. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. 32. the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. In the Choose Shortcut Folder screen. In an existing Program Group Select this option and choose the name of an existing program group to store Maximo Asset Management shortcuts. Deployment of Maximo Asset Management with automatic configuration of existing middleware 103 .

Table 14. and then click Next.. the following values are set. 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. In the Input Summary screen. button to select another location to create Maximo Asset Management shortcuts. The installation task begins.. In the Install Complete screen. review the installation information presented. 35. Use the Previous button to return to previous screens to make changes. Selecting this option does not create a shortcut in the Quick Launch bar. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. 34. Progress can be monitored by viewing messages displayed above the progress bar. click Done. What to do next When the installation has completed the installation wizard closes. If you elect to install Maximo Asset Management using the simple install path. In the Quick Launch Bar This option must not be used. Do not select this option. 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: . and then click Install. review the information you have provided to the Maximo Asset Management installation program. In the Pre-Installation Summary screens. You will be able to provide values where indicated. 33. used for first paragraph and abstract.On the Desktop Select this option to create shortcuts for Maximo Asset Management on the desktop. Other Select this option and use the Choose. Simple install path values Put your short description here.

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.Table 14. Deployment of Maximo Asset Management with automatic configuration of existing middleware 105 . 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.

such as anti-virus software. temporarily shut down any non-critical processes that could have a negative effect on the installation. Running the Maximo Asset Management installation program Use these instructions to install Maximo Asset Management and automatically configure middleware on multiple servers. Before you begin Before you start the installation program. 106 Installation Guide: . ensure that the system meets the following conditions: v On the administrative workstation. using default values. 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 . 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.Table 14.

Each remote system must support a remote access protocol and accept remote logins from a user name and password configured on the target server. run the following command: install_win64. and you intend to install the product on the same system. v The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed into that location. If you want to customize the table space sizes. during the installation. you must create the instance user and the home directory for the user on the DB2 server. you must either run the Maximo Asset Management installation program in English. 2. In the command line. You enter this user ID on the DB2 Administration screen and on the Remote Access Authorization screen of the Maximo Asset Management installation program. you must configure remote execution and access to use SMB. Deployment of Maximo Asset Management with automatic configuration of existing middleware 107 .exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes d On a 64-bit Windows system. v Perform the following tasks to prepare the DB2 database: – If DB2 is installed on a Linux or UNIX system. – The user ID for the DB2 instance administrator must have SYSADM (administration) authority. See the Troubleshooting chapter for instructions on restarting middleware if you need to do so. If the remote system is a Windows server. See the DB2 product documentation for information about creating a user with SYSADM (administration) authority on the DB2 server. 3. On a 32-bit Windows system. 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. You can create a maxdemo database. – To avoid high system memory usage by DB2. run the following command: install. navigate to the directory where the Maximo Asset Management files are extracted.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes v When you are running the installation wizard. create a maxdemo database by performing the following tasks: Chapter 5. – If you are plan to install Maximo Asset Management in a language other than English. complete either of following two procedures: v Enter a command to create a maxdemo database: 1. Automatic configuraton creates an empty Maximo database on the system. including sample data. redefine these variables before you begin the product installation. 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. To create a maxdemo database. rexec. Change to the install\MAM\Install\new folder. v For WebSphere Application Server Network Deployment. manually configure the database. or modify the table space sizes after installation. v Enable a remote execution and access service on every system with middleware installed. SSH and Windows SMB. Remote access protocols include rsh.v The middleware environment is installed and running properly. – The database instance owner home directory must have 8 GB of space available regardless of whether a database is installed in that location. ensure that the Cell and all related nodes are actively running.

r 7. About this task To install Maximo Asset Management. where en is the language folder and dbtype is ora/sqs/db2. click Install the Product. In the launchpad navigation screen. To avoid this problem. In the Run Configuration Step screen in the installation wizard (Step 31 in the procedure). Ensure the database server. 6.1. 2. See the troubleshooting chapter for information about errors that occur during the installation.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. This circumstance causes a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E.exe b. select the Copy files now. 3. and run the following command: launchpad. specify the fully-qualified host name of the system for all host name values. directory server. When taskrunner finishes running. Log in as Administrator on the Maximo Asset Management administrative system. When the installation finishes. exit the installation wizard. Start the launchpad. Click Maximo Asset Management. Copy the ibm\smp\maximo\tools\maximo\en\maxdemo file to ibm\smp\maximo\tools\maximo\en\maximo. When taskrunner successfully completes. and application server services are running. install the product using a user ID with administrative authority that contains only English language characters. 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. When you are installing the product. 2. Rename the ibm\smp\maximo\tools\maximo\en\maximo file. From a command prompt navigate to ibm\smp\scripts and run the following command: taskrunner. rename the files back to their original names. a. If you are installing on a system using a system ID that contains Russian language characters. 3. Start the Maximo Asset Management installation program from the launchpad. 5. Perform installation configuration later option. follow these steps: Procedure 1. Navigate to the root directory of the product DVD or the downloaded installation image. c. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations. the installation fails with error message CTGIN2289E when attempting to install language packages. 108 Installation Guide: . 4. review this information in the Planning to install Maximo Asset Management chapter before you begin the installation..

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

13. 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. Database Password Enter the password for the user ID used to access DB2. and then click Next. This file is found in the workspace that was defined during the middleware installation task. This user ID is created if it does not exist. The default instance name is ctginst1. This user ID must have administrative rights on the server you are accessing. 11. In the Database screen. Database User ID Enter the user ID used for Maximo to access DB2. C:\ibm\tivoli\mwi\workspace for Windows and /root/ibm/tivoli/mwi/workspace for UNIX. In the Database Type screen. however. For Windows OS. In the Remote Access Authorization screen. For example. Port Enter the port being used by DB2 instance. The default is 50005. 14. select the DB2 database. and then click Next. the Maximo Asset Management installation program connects to the database server to validate the information you have entered. The database is created if it does not exist. 12. Database Name Enter the name of the database to use with Maximo. enter configuration information about the database. this user must be a member of the DB2ADMNS group.Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. The default database name is maxdb71. In the Automate Database Configuration screen. and then click Next. and then click Next. This instance is created if it does not exist. enter authorization information for the automatic database configuration feature. This user ID cannot be the same one used as the instance administrator user ID. select Automate database creation and configuration. Host name Enter the fully-qualified host name of the server hosting DB2. After you enter configuration information for the database. Instance Enter the name of the database instance to be used with Maximo. the user and its associated home directory must exist on the DB2 server. Default for all platforms is maximo. 110 Installation Guide: .

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

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

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

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

o=IBM.ou=SWG.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask. and then click Next.ou=SWG.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg.c=US member: uid=mxintadm.c=US cn: maxadmin dn: cn=maximousers. enter the following information.ou=users.o=IBM.c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm. 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.ou=users.c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg dn: cn=maxadmin.ou=SWG.o=IBM. you must create it yourself before advancing beyond this panel. o=ibm.ou=SWG. Deployment of Maximo Asset Management with automatic configuration of existing middleware 115 . A JMS server requires a DB2 data repository to be configured to maintain messages.ou=users.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin. JMS Data Source name Enter intjmsds as the name of the data source to be used by JMS. Chapter 5.ou=users.ou=users.ou=SWG.ou=groups.c=US member: uid=mxintadm.ou=SWG. dn: uid=maxadmin.ou=SWG. If you are not using the default LDAP schema provided with Maximo Asset Management. Select whether the JMS data store should be persisted.ou=SWG. you will have to create them manually before continuing the Maximo Asset Management installation from this point. o=ibm.ou=SWG. o=ibm.ou=groups.If you do not want to have the users created by the Maximo Asset Management installation program.ou=users.c=US member: uid=maxreg. In the Integration Adapter JMS Configuration screen.ou=users.o=IBM. o=ibm.ou=SWG.c=US cn: maximousers 26.ou=users. o=ibm.o=IBM.

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

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

and it uses the configuration values stored in the maximo. 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. 118 Installation Guide: . b. Taskrunner data stores are not persisted. In the case of an installation failure. located in the <MAM_HOME>\scripts directory.properties file. the taskrunner continues despite errors. and then click Next. select the type of shortcut you would like to arrange for Maximo Asset Management. By selecting this option. See the instructions for manually configuring WebSphere Application Server in the Deployment of . you are not able to use the taskrunner utility to run configuration scripts.properties file to configure Maximo Asset Management. do not reboot your system. If you run taskrunner with the NOSTOPONERROR parameter. If you intend to use the taskrunner utility. Run the taskrunner utility from the command line. The configuration values that you enter are stored in the <MAM_HOME>maximo\applications\maximo\properties\ maximo. Deploy application files automatically Select this option to have the installation program perform application file deployment automatically during the installation. <MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR> Note: If you reboot the system. and performing configuration tasks using the values you have specified. Choose how to deploy application files. 32. The taskrunner utility resumes the installation at the point where the last successfully completed task was recorded in the previous attempt. Deploy application files manually later Select this option to defer the deployment of application files. You can run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility. 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. Files can be deployed once all products have added their own functions to the application files. In the Choose Shortcut Folder panel. the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. and then allow you to run the configuration step at a later date.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.Maximo Asset Management with manual configuration of middleware. 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. 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.

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. and then click Next. Selecting this option does not create a shortcut in the Quick Launch bar. review the information you have provided to the Maximo Asset Management installation program.. Deployment of Maximo Asset Management with automatic configuration of existing middleware 119 . In the Pre-Installation Summary panel. If you intend to support multiple languages in Maximo Asset Management. In the Input Summary panel. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. Other Select this option and use the Choose. Progress can be monitored by viewing messages displayed above the progress bar. What to do next When the Maximo Asset Management installation program has completed installation and configuration tasks. Use the Previous button to return to previous panels to make changes.. The chapter also describes how to install process solution packages. you must perform several additional tasks after the installation. 34. The installation task begins. On the Desktop Select this option to create shortcuts for Maximo Asset Management on the desktop. The Post-installation configuration chapter describes the configuration tasks to complete within the product user interface. In the Install Complete panel. 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. it will exit. Do not select this option. Chapter 5. In the Quick Launch Bar This option must not be used. including process manager products and integration modules. and then click Install. 35. click Done. 33. Completing post-installation tasks To complete the deployment. In order to use the Start Menu shortcut with Internet Explorer. In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. See the Deployment of optional packages chapter for language pack installation instructions. review the installation information presented. button to select another location to create Maximo Asset Management shortcuts.In an existing Program Group Select this option and choose the name of an existing program group to store Maximo Asset Management shortcuts. install the language pack before performing other configuration tasks.

perform the following verification procedures: Procedure 1.properties" Verifying the installation After you have exited the Maximo Asset Management installation program without encountering any errors. Before you begin The product installation program performs installation verification. The following success messages are found in the CTGInstallTrace00. Run the following command: <MAM_HOME>\jacl\solutions\Sendfile. you can further verify that the installation completed successfully by locating key artifacts and performing a few simple tasks.Deploying the confhelp. Ensure you are logged into the administrative workstation. refer to “Troubleshooting the product installation program” on page 239. Examine the CTGInstallTrace00.properties file must be deployed to enable the help system for the product.properties file The confhelp.log file.properties file. are successful. Before you begin About this task To deploy the confhelp. where XX is a two digit number such as 00.properties" "<WASInstallLocation>\properties" "confhelp. 2. including the product log in task. If the health check task is unsuccessful. The product installation program returns a success message if all installation steps. For more information about log files and troubleshooting errors encountered during the installation. About this task To further verify that the Maximo Asset Management installation was completed successfully.log file for success messages. a HealthCheckFailed error thrown for the getUrlContentString function will be found in the <MAM_HOME>\logs\CTGInstallTraceXX.bat <WASDeploymentManagerHostName> <WASRemoteAccessUserName> <WASRemoteAccesspassword> "<MaximoInstallLocation>\applications\maximohelp \helpweb\webmodule\WEB-INF\confhelp. complete the following steps: Procedure 1.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: . or a health check. by logging into the product before exiting the installation.

indicate the configuration was successful: <symptom>CTGIN2228I.*node</symptom> <symptom>CTGIN2232I.log file.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMO was successful v CTGIN2253I: buildhelpear.*security</symptom> Search the CTGInstallTrace00.*client</symptom> <symptom>CTGIN2230I.v CTGIN2079I: Base services database configuration completed successfully (This message indicates that maxinst finished successfully.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. Deployment of Maximo Asset Management with automatic configuration of existing middleware 121 . Use the solutioninstaller command to list installed packages: <MAM_HOME>\bin\setupPSIenv. Chapter 5.log file for the following message.*server</symptom> <symptom>CTGIN2238I. You can compare the contents of that panel with a listing of what was actually installed on the system. maxinst. Being able to log into the product manually is a good indicator that the installation was successful. found in the CTGInstallTrace00.*NodeAgent</symptom> <symptom>CTGIN2240I. Once you have logged in. navigate through the GoTo menu to verify that it has been populated with the applications you expect. Log into the product and verify applications are present. the following messages. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages that will be installed.bat <MAM_HOME>\bin\solutionInstaller. which indicates that the maxinst task completed successfully: CTGIN2079I. Compare the packages chosen for installation with the packages that were installed. 3.*completed 2.) 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.bat -action showInstalled -all The resulting list should match the packages listed in the Package Summary panel.

122 Installation Guide: .

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. 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.Chapter 6.2010 123 . 2007 . To deploy Maximo Asset Management manually. © Copyright IBM Corp. using middleware already established in your enterprise. use this roadmap to perform the tasks in the correct order.

4. 3. 2. Run the Maximo Asset Management installation program and select the options that indicate that the middleware is already configured. Configure the J2EE server.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. Configure the database following the instructions for the database you plan to use. Deploying Maximo Asset Management with manual middleware configuration You must install middleware before you install Maximo Asset Management. 124 Installation Guide: . Optional: Configure the directory server. Perform the installation in the following order: 1.

the directory server.5. Before you begin. Ensure that all of your middleware is at the level described in “Prerequisite hardware and software” on page 19. Manually configured installations involve configuring middleware components.x server for use with Maximo Asset Management. ensure that the Cell and all related nodes are active.x About this task To configure an existing DB2 9. 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. perform manual configuration tasks to configure process managers. 6. Alternatively. Complete post-installation tasks to verify the deployment and perform initial system configuration. For DB2 on Linux or UNIX systems. 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. Optional: If you did not automatically configure the J2EE server during the Maximo Asset Management installation. Deployment of Maximo Asset Management with manual configuration of middleware 125 . Manually configuring the database server If you choose to not have the Maximo Asset Management installation program automatically configure the database server. to work with Maximo Asset Management prior to using the Maximo Asset Management installation program. complete the following steps prior to launching the Maximo Asset Management installation program. 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. 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. 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. you can choose to manually configure one or more of the middleware servers to work with Maximo Asset Management. you must complete the manual configuration before you use the Maximo Asset Management installation program . v For IBM WebSphere Network Deployment. the database server. and the J2EE server. For DB2 on a Windows system. Chapter 6. Manually configuring DB2 9. ensure you have a minimum of 8 GB of free space in the DB2 installation directory. 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.

it is not necessary to assign a specific group. Create a database a. You can use these user and group name values. Set the listening port for the instance Windows OS db2 update dbm cfg using svcename 50005 c. The middleware installer creates a ctginst1 user that will own the database instance and assigns that user to a group called db2iadm1. b. you can add this information to your PATH.1. a. Create system users. Alternatively.5/instance directory. log into the system using the user IDs and change the password for each account. For the maximo user. Use the following command to create the DB2 instance: Windows OS db2icrt -s ese -u db2admin.password -r 50005. 126 Installation Guide: . but be sure to substitute them where appropriate in this procedure. 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. Set instance service to start automatically Windows OS sc config ctginst1-0 start= auto d. or use custom values of your own. Log into the system as a user that has administrative permissions on the system. you need to create users and groups manually using user management tools available on the system. Start the ctginst1 database instance: Windows OS db2start Linux or UNIX OS su . you might have to run this command from the /opt/ibm/db2/V9. After the user IDs have been created. For AIX.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. Create a system group and system users. 2. b. Create the DB2 instance: a.ctginst1 db2start 3. use SMIT to add the users. Create users named ctginst1 and maximo and assign the ctginst1 user to a group named db2iadm1. If you are configuring DB2 manually.

f. g. i.) in the Value column. specify a different directory.3 systems.. select the LOCKLIST value and click the button labeled with the ellipsis (. j.. Chapter 6. right-click the Databases folder located below the instance name. select the LOGSECOND value and click the button labeled with the ellipsis (. From the Select your maintenance strategy panel.. click Next. From the Database Configuration panel. select the APP_CTL_HEAP_SZ value and click the button labeled with the ellipsis (.. review the choices you have made. Click Next. From the Database Configuration panel. Right-click the maxdb71 database created in the previous step.) in the Value column. and then click OK. and then select Create Database? With Automatic Maintenance. From the Provide a valid SMTP server panel. Enter 4096. and choose Configure Parameters. b. e. if you do not want to use the database path as the storage path. Alternatively. and then click Next. g. j.) in the Value column.. e. From the DB2 Control Center. d. and then click Next. From the Database Configuration panel. 3) Type the following command: db2cc b. d. From the Specify a name for your new database panel. Enter 16384. From the Review the actions that will take place when you click Finish panel. The database is then created. Configure the database. provide scheduling details for offline maintenance. su to ctginst1 and use the following command: db2 create database maxdb71 using codeset UTF-8 territory us pagesize 32 K 4. and then click OK. For AIX 5.2) Source the instance you plan to use. i. I can specify an offline maintenance window of at least an hour when the database is inaccessible. From the Specify when offline automatic maintenance activities can run. h... 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. From the Database Configuration panel.) in the Value column. enter the name of the SMTP server that is used to communicate DB2 messages concerning this database. and then click OK. From the Specify where to store your data panel. Enable the Enable database for XML option to create a Unicode database with a code set of UTF-8. h.. a. and then click OK.. select the LOGFILSIZ value and click the button labeled with the ellipsis (. and then click Finish.. Enter 30000.) in the Value column. If you specify a path. the directory must exist. select the APPLHEAPSZ value and click the button labeled with the ellipsis (. From the Database Configuration panel. f. c. select Yes. and then click Next. Enter 2048. enter maxdb71 for both the Database name and Alias fields. c. Deployment of Maximo Asset Management with manual configuration of middleware 127 .

3 systems. click Add User. From the DB2 Control Center.3 systems is to configure it remotely from a system that can run the DB2 Control Center. and then click OK. select Create. For AIX 5. Define a hard drive specification by choosing Server (SCSI). Enter 15.k. and leave Extent size as 32. and then clicking Start. c. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. Highlight the user. you cannot launch the DB2 Control Center locally. From the right-click menu. a. Ensure the Create buffer pool immediately choice is selected. From the Specify the extent and prefetch sizes for this table space panel. and then click Next. l. g. Select Regular as the type of table space and then click Next. 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. f. b. using the DB2 client. and then click Next. and then click Next. in the Database Authorities window. and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. c. Add users to the database. k. Create table space. e. Restart the database by right-clicking the ctginst1 instance.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. j. h. and then click OK. and then click OK. Highlight the newly created buffer pool and click Next. d. clicking Stop. and then click Next. e. 6. 128 Installation Guide: . and click Grant All. right-click it and select Authorities. b. i. choose the Between 200 MB and 2 GB option. maximo.tb_reorg_req set thresholdschecked yes update alert cfg for database on maxdb71 using db. d. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option. The best way to configure the database on AIX 5. Click OK. From the User tab of the Database Authorities window. Click Create to create a buffer pool for the table space. Specify MAXBUFPOOL as your new buffer pool. select the user maximo. Specify MAXDATA as your new table space. From the Add User dialog. After the database is restarted. a.db_backup_req set thresholdschecked yes update alert cfg for database on maxdb71 using db.

From the DB2 Control Center. Select the user maximo. a. Create a schema. 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.dropin. Deployment of Maximo Asset Management with manual configuration of middleware 129 . c. select No Grant. and then click OK. From the DB2 Control Center. and then select the maximo user. select Yes. a. b. index data is stored in the data table space.alterin on schema maximo to user maximo 9. From the right-click menu. locate and right-click the MAXDATA Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. h. Alternatively. If you would rather create a separate index table space. Specify MAXTEMP for your new table space. g. you could create one at this point. Specify a name for your new schema. e. d.67 prefetchsize 16 transferrate 0. select Privileges. a. 8. you will have to grant permissions for it at this time. 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. Alternatively. Click Finish. From the Privileges drop-down menu. e. Click OK. From the DB2 Control Center. and click Next. Chapter 6. and then click OK. c. Alternatively. select Create.18 bufferpool maxbufpool dropped table recovery on By default. d. 7. Grant permissions for the table space. Select System temporary as the type of table space and then click Next. Select the previously created bufferpool (MAXBUFPOOL). From the right-click menu. and then click OK. and then click OK. Right-click on the new schema name and select Privileges. select Add User. Create a temporary table space. From the right-click menu. select Create.l. From the Privileges drop-down menus. b. locate and right-click the Schema entry under the DB2 database that you created for use with Maximo Asset Management. e. you can use the following commands to complete the steps from the command line: create schema maximo authorization administrator grant createin. and then click Next. Select the maximo user and then click Grant all. This name must be the same as was used for the Database User ID. b. f. From the dialog box. Click Add User. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. d. c.

50005 ctginst1 Linux or UNIX OS db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1 130 Installation Guide: . a. For AIX. Use the following command to create the DB2 instance: Windows OS db2icrt -s ese -u db2admin. Create operating system users named ctginst1 and maximo.2 About this task To configure an existing DB2 8.. h. Create system users. From the Specify the extent and prefetch sizes for this table space panel. Create the DB2 instance: a. 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. Install the appropriate fix pack indicated in the prerequisites topic in the chapter that describes how to prepare for the installation. Specify the dropped table recovery option for the table space by enabling the Enable dropped table recovery option. Also run the db2iupdt command to update the DB2 instance. After the user IDs have been created.67 prefetchsize 16 transferrate 0. using user management tools available on the system. and then click Next. assign the primary group as db2grp1 and secondary groups of staff and dasadm1. and leave Extent size as 32. Alternatively. DB2 requires user accounts that are operating system user accounts. b. use SMIT to add the users.password -r 50005. complete the following steps prior to launching the Maximo Asset Management installation program: 1. 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. Define a hard drive specification by choosing Server (SCSI). After you have installed the fix pack.2 server for use with Maximo Asset Management. it is not necessary to assign a specific group. For the maximo user. and then click Next. and then click Next. Start by first stopping all processes that are running for the database instance (ctginst1). Click Finish. 2. For the ctginst1 user. choose the Between 200 MB and 2 GB option. g.18 bufferpool maxbufpool connect reset 10.f. run the dasupdt command to update the DB2 Administration Server to the applied fix pack. log into the system using the user IDs and change the password for each account. i. Log into the system as a user that has administrative permissions on the system.

d. Open a command window and type the following command: su .. From the DB2 Command Window. Set instance service to start automatically Windows OS sc config ctginst1-0 start= auto d. Enter 30000.. and then click OK. From the Database Configuration panel. and then click OK.) in the Value column..) in the Value column. and then click OK. Enter 4096. f. Chapter 6. h.. j.ctginst1 b. Right-click the maxdb71 database and choose Configure Parameters. From the Database Configuration panel.AIX 64-bit system db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1 b. i. g. Enter 1024.) in the Value column. type the following command: db2cc 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. Open a command window and type the following command: set DB2INSTANCE=ctginst1 b.ctginst1 db2start 3. k. navigate to All Systems → DB2_server→Instances→CTGINST1→Databases→MAXDB71 c... select the LOGFILSIZ value and click the button labeled with the ellipsis (. Set the listening port for the instance Windows OS db2 update dbm cfg using svcename 50005 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. a. select the LOCKLIST value and click the button labeled with the ellipsis (. e.. From the Database Configuration panel. Enter 1024. Start the ctginst1 database instance: Windows OS db2start Linux or UNIX OS su . From the DB2 Control Center. Deployment of Maximo Asset Management with manual configuration of middleware 131 . Now type db2cmd to open the DB2 Command Window: c. Create the database: Windows OS a. and then click OK. Configure the database. select the APPLHEAPSZ value and click the button labeled with the ellipsis (. select the APP_CTL_HEAP_SZ value and click the button labeled with the ellipsis (.) in the Value column. From the Database Configuration panel.

and then click OK. and then click Next. k. click Add. Specify MAXBUFPOOL as your new buffer pool. a. From the Space management panel. d. Click OK. right-click it and select Authorities. From the Database Configuration panel. and then click OK.. n. and click Grant All. a. h. and File name to CTGDAT. b. and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. click Finish. and then clicking Start. c. p. From the Add User dialog. a. From the Database Configuration panel. From the User tab of the Database Authorities window. select the user maximo. g. Size to 5000 Mb. Select System temporary as the type of tablespace and then click Next. i. From the right-click menu. From the right-click menu. From the Containers panel. Click Close. e. 7. 132 Installation Guide: . l. m. For UNIX. o.) in the Value column. n. j. and then click Next. c. Select Regular as the type of tablespace and then click Next. Specify MAXDATA as your new tablespace. Create a temporary table space. clicking Stop. specify Database-managed space and click Next. 6. select the LOGSECOND value and click the button labeled with the ellipsis (. From the Specify the extent and prefetch sizes for this table space panel. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option. Define a hard drive specification by choosing Server (SCSI). f. Create tablespace. o. Restart the database by right-clicking the ctginst1 instance. b. b. Click Create to create a new buffer pool for the tablespace. From the DB2 Control Center. maximo in the Database Authorities window. d. enter /home/ctginst1 as the location of the file. click Next. click OK. From the DB2 Control Center. Enter 4. c. 5. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. Once the database has restarted. Highlight the user. select Create. m.. click Add User. From the Summary panel.l. select Create. Ensure the Create buffer pool immediately choice is selected. e. p. Set the Type to File. Click OK. Highlight the newly created buffer pool and click Next. and then click Next. Add users to the database. and then click Next. and then click OK. and then click Next. d. Specify MAXTEMP for your new tablespace.

From the right-click menu. click Finish. Click Add User. Right-click on the new schema name and select Privileges. specify Database-managed space. 8. and then click OK.e. For UNIX. d. g. select Privileges. select Add User. d. 10. From the Privileges drop-down menus. Grant permissions for the table space. enter /home/ctginst1 as the location of the file. locate and right-click the MAXDATA Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. a. Set the Type to File. and then select the maximo user. Click OK. From the Space management panel. Install the appropriate fix pack listed in the prerequisites topic in the chapter that describes how to prepare for the installation. From the Containers panel. a. From the DB2 Control Center. b. From the DB2 Control Center. g. click Next. c. select No Grant. b. select Create. From the Privileges drop-down menu. and then click Next. you will also need to run the db2iupdt command to update the DB2 instance. Deployment of Maximo Asset Management with manual configuration of middleware 133 . Select the user maximo. f. l. and then click OK. Specify a name for your new schema. e. and then click Next. From the right-click menu. i. From the dialog box. Create a schema. h. f. j. and then click Next. locate and right-click the Schema entry under the DB2 database that you created for use with Maximo Asset Management. Size to 3000Mb. 9. From the Specify the extent and prefetch sizes for this table space panel. From the Summary panel. select Yes. Select the previously created bufferpool (MAXBUFPOOL). Define a hard drive specification by choosing Server (SCSI). k. click Add. run the dasupdt command to update the DB2 Administration Server to the applied fix pack. and click Next. e. and then click OK. After you have installed a fix pack. Start by first stopping all processes that are running for the database instance (ctginst1). c. This name should be the same as was used for the Database User ID. and File name to CTGTMP. Select the maximo user and then click Grant all h. Click OK. and then click OK. If you installed a fix pack. 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.

and then click Next. k. and then click Next. Click Next. Open the Oracle Network Configuration Assistant application. 3. 134 Installation Guide: . Click Finish. Create a database for use by Maximo Asset Management. complete the following steps before launching the Maximo Asset Management installation program: Procedure 1. j. a. d. Open the Oracle Database Configuration Assistant. From the memory allocation panel. l. enter a password for Oracle users. Select Create a Database. and then click Next h. h. Select General Purpose or Transaction Processing. and then click Next. e. g. and then click Next. i. click Next. c. and then click Next. Log in as the Oracle software user. and then click Next. c. d. Leave defaults selected for the database recovery options panel. provide the following values (measured in Mb). i.Manually configuring Oracle 11g Use the following instructions to manually configure Oracle 11g for use with Maximo Asset Management. click Next. Enter a name for the listener or accept the default value. and then click Next. select Use the standard port of 1521. Ensure Use the Same Administrative Password for All Accounts is selected. g. From the Sample Schemas panel. and then click Next. Ensure File System is selected as the storage mechanism to use for the database. From the Listener Configuration Done panel. About this task To configure an existing Oracle 11g server for use with Maximo Asset Management. and then click Next. Select No to indicate that you are finished configuring listeners. Accept the default Selected Protocols listed by clicking Next. and click Next. f. e. The listener manages requests to connect to the database. From the Welcome panel. From the port panel. f. 2. Memory Management Set this value to Manual Shared Memory Management. b. select Custom. From the action panel. select Listener configuration. Leave the defaults selected. and then click Next. Typically this user is named oracle. a. select Add. Ensure Use Database File Locations from Template is selected as the value to use for database file location. Create the database listener. This step is only required if you do not already have an existing listener in place. and then click Next. Enter ctginst1 for both the Global Database Name value and the SID value. b. and then click Next.

click Finish. n. q. and then click Next. From the Creation Options panel. shared_pool_reserved_size Leave set to the default value. nls_length_semantics Change this value to CHAR. u. this command will fail. change them to the values indicated.dbf' size 1000M autoextend on maxsize unlimited..0\db_1\dbs\maxdata.Shared Pool Set this value to 251.1. Create a table space using the following command in SQL*Plus: Create tablespace maxdata datafile 'C:\oracle\product\11. Buffer Cache Set this value to 755. Click All Initialization Parameters. PGA Size Set this value to 380. click Next.. accept the defaults.sql script as part of the configuration of the CTXSYS user. From the Automatic Maintenance Tasks panel. and then click Close. Change the directory specified in the example to the location where the database will reside. From the Security Settings panel. The database has been successfully created. Click Exit to exit the Database Configuration Assistant. m. p. accept the defaults. Locate the following parameters. s. From the Database Storage panel. Java Pool Set this value to 20 Large Pool Set this value to 114. From the Initialization Parameters panel.dbf' size 1000M autoextend on. Deployment of Maximo Asset Management with manual configuration of middleware 135 .. and then click Next. Chapter 6. v. click Next. open_cursors Change this value to 1000. Create a temporary table space using the following command in SQL*Plus create temporary tablespace maxtemp tempfile 'C:\oracle\product\11. 4. t. 5. If the directory does not already exist. Note: The Oracle Database Configuration Assistant executes the ORACLE_HOME/ctx/admin/defaults/drdefus. r. select Use Unicode (AL32UTF8). o.0\db_1\dbs\maxtemp. From the Character Sets tab.1. You must execute this script manually if the Oracle Database Configuration Assistant is not used. cursor_sharing Set this value to FORCE. Click Show Advanced Parameters.

if you do not by default grant a role such as the select_catalog_role role to user IDs connecting to the database. 6. grant create trigger to maximo. grant connect to maximo.ctx_ddl to maximo. this command will fail. and then click Next. From the action panel. If the directory does not already exist. Open the Oracle Network Configuration Assistant application. Typically this user is named oracle. From the port panel. 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. d. grant create view to maximo. and then click Next. and then click Next. select Use the standard port of 1521. Log in as the Oracle software user. in order to deploy Maximo Asset Management successfully. 136 Installation Guide: . Create the database listener. and then click Next. you must also grant access to that index table space to the maximo user. Create the maximo user and grant permissions using the following command in SQL*Plus: create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp. grant create synonym to maximo. If you created a separate table space for indexing. So. grant create table to maximo. you must explicitly grant them to the maximo user. select Listener configuration. c. grant create job to maximo. grant create procedure to maximo. grant create sequence to maximo. alter user maximo quota unlimited on maxdata. 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. grant create session to maximo. If you restricted the default privileges granted to user IDs.": 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. Enter a name for the listener or accept the default value. b. complete the following steps before launching the Maximo Asset Management installation program: 1. grant execute on ctxsys. grant alter session to maximo. e. for example. For example. execute the following command if you created a separate table space for indexing called TSI_MAM_OWN. a. select Add. From the Welcome panel. 2.Change the directory specified in the example to the location where the database will reside. The listener manages requests to connect to the database. Accept the default Selected Protocols listed by clicking Next. f.

Locate the following parameters. f. Ensure Use Database File Locations from Template is selected as the value to use for database file location. and then click Next. i. and then click Next. Ensure File System is selected as the storage mechanism to use for the database.. l. i. c. Click Show Advanced Parameters. b. Create a database for use by Maximo Asset Management. h. a. m. Leave the defaults selected.. Deployment of Maximo Asset Management with manual configuration of middleware 137 . From the Character Sets tab. k. Click Next. click Next. Large Pool Set this value to 8. cursor_sharing Set this value to FORCE. and then click Next. Enter ctginst1 for both the Global Database Name value and the SID value. j. select Custom. Leave defaults selected for the database recovery options panel. p. and then click Next. From the Sample Schemas panel. Click Finish. o. Ensure Use the Same Password for All Accounts is selected. and then click Next. provide the following values (measured in MB). g. From the Listener Configuration Done panel. and then click Next. Buffer Cache Set this value to 275. select Use Unicode (AL32UTF8).. Shared Memory Management Set this value to Manual. Select Create a Database. d. Java Pool Set this value to 32. From the memory allocation panel. and then click Next. change them to the values indicated. h. 3. and then click Close. Select No to indicate that you are finished configuring listeners. and then click Next. and click Next. Click All Initialization Parameters. nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000. n. enter a password for Oracle users. Chapter 6. and then click Next. Open the Oracle Database Configuration Assistant. Select General Purpose. PGA Size Set this value to 36. click Next. Shared Pool Set this value to 150.g. e.

sql script as part of the configuration of the CTXSYS user. if you do not by default grant a role such as the select_catalog_role role to user IDs connecting to the database. If the directory does not exist. this command will fail. Create a temporary table space using the following command in SQL*Plus: Create temporary tablespace maxtemp tempfile 'C:\oracle\product\10. click Next. Click Exit to exit the Database Configuration Assistant. enter a password for the account. 5. u. The Oracle Database Configuration Assistant executes the ORACLE_HOME/ctx/ admin/defaults/drdefus.0\oradata\ctginst1\maxdata. 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. grant create job to maximo. Change the directory specified in the example to the location where the database will reside. grant create table to maximo. click Finish.2. 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: . From the Creation Options panel. you must also grant access to that index table space to the maximo user.2. click Password Management Unlock the CTXSYS account by clearing the check mark in the Lock Account? column for that entry. grant create view to maximo. From the Database Storage panel. grant create session to maximo. s. grant create sequence to maximo. click Next.From the Initialization Parameters panel. The database has been successfully created. t. r. You must execute this script manually if the Oracle Database Configuration Assistant is not used. 6. Change the directory specified in the example to the location where the database will reside. If the directory does not exist. grant execute on ctxsys. grant create synonym to maximo.dbf' size 1000M autoextend on maxsize unlimited. grant create trigger to maximo. for example. you must explicitly grant them to the maximo user. in order to deploy Maximo Asset Management successfully. alter user maximo quota unlimited on maxdata. 4. So. When the database is successfully created. Create tablespace maxdata datafile 'C:\oracle\product\10. Create a table space using the following command in SQL*Plus: q. and then click OK.dbf' size 1000M autoextend on. If you created a separate table space for indexing. If you restricted the default privileges granted to user IDs. grant connect to maximo. grant create procedure to maximo. 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.ctx_ddl to maximo. v. For example. this command will fail. grant alter session to maximo.0\oradata\ctginst1\maxtemp.

and click Next. From the Confirmation panel. k. Locate the following parameters. Once the database has been successfully created. Select Create a database. click OK. nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000 cursor_sharing Set this value to FORCE. ensure Oracle 9.8 is installed To configure an existing Oracle Oracle9i Rel2 server for use with Maximo Asset Management. c. and then click Next. Chapter 6. From the Database Storage panel. and then click Close. b. a. Shared Pool Set this value to 150. and then click Next. Click Next. click Password Management. f. enter the following values (M Bytes). From the Memory tab. and click Finish. Open the Oracle Database Configuration Assistant. select Custom. o. PGA Size Set this value to 36. Click Next. Java Pool Set this value to 32.2.Manually configuring Oracle9i Rel2 About this task If you are using Oracle9i Rel2. d. i. Click All Initialization Parameters. j. select the Create Database option. click Next. l. and then click Next. Select the Character Sets tab and select Use Unicode (AL32UTF8) as the Database Character Set. m. Buffer Cache Set this value to 36. complete the following steps prior to launching the Maximo Asset Management installation program: 1. Enter ctginst1 for both the Global Database Name value and the SID value. Deployment of Maximo Asset Management with manual configuration of middleware 139 . n.0. Leave the default of Dedicated Server Mode selected. and then click Next. change them to the values indicated. e. Select General Purpose. From the Creation Options panel. Large Pool Set this value to 8. h. Create a new database for use by Maximo Asset Management. g.

grant create table to maximo. Create a temporary tablespace using the following command in SQL*Plus: create temporary tablespace maxtemp tempfile 'C:\oracle\oradata\maxtemp\maxtemp. b. 2. using user management tools available on the system. What to do next Manually configuring DB2 8. grant create sequence to maximo. grant create trigger to maximo. 3. complete the following steps prior to launching the Maximo Asset Management installation program: 1. enter a password for the account. After 140 Installation Guide: . and then click OK.dbf' size 1000M autoextend on. 4. grant create view to maximo. Click Exit to exit the Database Configuration Assistant. grant create job to maximo. grant connect to maximo. DB2 requires user accounts that are operating system user accounts. Log into the system as a user that has administrative permissions on the system. For AIX. q. The database has been successfully created. Create the maximo user and grant permissions using the following command in SQL*Plus: create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp. grant create session to maximo. grant create procedure to maximo. For the maximo user. it is not necessary to assign a specific group. use SMIT to add the users. alter user maximo quota unlimited on maxdata.dbf' size 1000M autoextend on maxsize unlimited. Create a tablespace using the following command in SQL*Plus: Create tablespace maxdata datafile 'C:\oracle\oradata\maxdata\maxdata. 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. grant alter session to maximo. assign the primary group as db2grp1 and secondary groups of staff and dasadm1. Create system users. grant execute on ctxsys. For the ctginst1 user.2 server for use with Maximo Asset Management. The directory specified in the example should be changed to the location where the database will reside. Create operating system users named ctginst1 and maximo.2 About this task To configure an existing DB2 8. The directory specified in the example should be changed to the location where the database will reside.p.ctx_ddl to maximo. Unlock the CTXSYS account by removing the check mark in the Lock Account? column for that entry. grant create synonym to maximo. a. The database has been successfully created.

navigate to All Systems → DB2_server→Instances→CTGINST1→Databases→MAXDB71 c. From the DB2 Control Center. Deployment of Maximo Asset Management with manual configuration of middleware 141 . Create the DB2 instance: a. Open a command window and type the following command: su . Configure the database. e. Start the ctginst1 database instance: Windows OS db2start Linux or UNIX OS su .password -r 50005. Chapter 6. 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. log into the system using the user IDs and change the password for each account.. From the new instance window issue the following commands: db2start db2 create db maxdb71 using codeset utf-8 territory us pagesize 32 k 4.the user IDs have been created. d. Use the following command to create the DB2 instance: Windows OS db2icrt -s ese -u db2admin.ctginst1 b.) in the Value column. From the Database Configuration panel. select the LOGFILSIZ value and click the button labeled with the ellipsis (. and then click OK.ctginst1 db2start 3.. a. 2. Set the listening port for the instance Windows OS db2 update dbm cfg using svcename 50005 c.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. Right-click the maxdb71 database and choose Configure Parameters. Enter 4096. Create the database: Windows OS a. Set instance service to start automatically Windows OS sc config ctginst1-0 start= auto d. From the DB2 Command Window. Now type db2cmd to open the DB2 Command Window: c. type the following command: db2cc b. Open a command window and type the following command: set DB2INSTANCE=ctginst1 b.

and File name to CTGDAT. Highlight the newly created buffer pool and click Next. o. o. Select Regular as the type of tablespace and then click Next. Highlight the user. Enter 1024. and then click OK. click Add. b. g. click OK. 6. Size to 5000 Mb.) in the Value column. click Next.) in the Value column. m. m. b. d. and then clicking Start. Create tablespace.f. g. and then click Next. and then click Next. select the user maximo.. Once the database has restarted. From the DB2 Control Center. k. and then click OK. c. right-click it and select Authorities. i. Define a hard drive specification by choosing Server (SCSI). a. From the Database Configuration panel. clicking Stop. e. click Add User. and click Grant All. enter /home/ctginst1 as the location of the file. j.. For UNIX. and then click Next. Ensure the Create buffer pool immediately choice is selected. and then click Next. Specify MAXDATA as your new tablespace. d.. Click Create to create a new buffer pool for the tablespace. From the Database Configuration panel. 5. c. l. select the APP_CTL_HEAP_SZ value and click the button labeled with the ellipsis (. From the Containers panel. Enter 1024. 142 Installation Guide: . Enter 4. select the LOCKLIST value and click the button labeled with the ellipsis (. Enter 30000. Restart the database by right-clicking the ctginst1 instance. and then click OK. select the APPLHEAPSZ value and click the button labeled with the ellipsis (. Click OK. specify Database-managed space and click Next. and then click OK. From the Database Configuration panel. From the User tab of the Database Authorities window.) in the Value column. n. h. and then click OK. and then click OK. From the Add User dialog. i. and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. From the Database Configuration panel. Click OK.. From the right-click menu. k. f..) in the Value column. h. a. From the Specify the extent and prefetch sizes for this table space panel. select the LOGSECOND value and click the button labeled with the ellipsis (. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option. Specify MAXBUFPOOL as your new buffer pool. j.. n. Add users to the database. From the Database Configuration panel. Set the Type to File. Click Close.. select Create. p. maximo in the Database Authorities window. From the Space management panel. l. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. e..

Define a hard drive specification by choosing Server (SCSI). From the right-click menu. a. b. and then click Next. d. From the DB2 Control Center. and then click Next. Select the maximo user and then click Grant all h. c. select Privileges. From the Summary panel. From the Space management panel. Specify MAXTEMP for your new tablespace. Create a schema. 7. k. and then click OK. and then click OK. locate and right-click the Schema entry under the DB2 database that you created for use with Maximo Asset Management. If you installed a fix pack. select No Grant. and then click OK. a. e. j. run the dasupdt command to update the DB2 Administration Server to the applied fix pack. select Create. From the Privileges drop-down menus. Right-click on the new schema name and select Privileges. Select the user maximo. a. c. specify Database-managed space. From the Privileges drop-down menu. This name should be the same as was used for the Database User ID. select Yes. e. 8. click Next. f. 10. click Finish. 9. f. click Finish. and then select the maximo user. Click OK. From the right-click menu. Chapter 6. Grant permissions for the table space. and then click Next. From the Specify the extent and prefetch sizes for this table space panel. Size to 3000Mb. b. and click Next. Click Add User. g. enter /home/ctginst1 as the location of the file. Deployment of Maximo Asset Management with manual configuration of middleware 143 . Click OK. i. and then click Next. Set the Type to File. h. locate and right-click the MAXDATA Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. d. c. Specify a name for your new schema. g. select Create. From the DB2 Control Center. From the right-click menu. l. For UNIX. Select System temporary as the type of tablespace and then click Next. Install the appropriate fix pack listed in the prerequisites topic in the chapter that describes how to prepare for the installation. Select the previously created bufferpool (MAXBUFPOOL). Create a temporary table space. select Add User. d. and then click OK. From the DB2 Control Center. e. b. From the dialog box.p. From the Containers panel. click Add. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Maximo Asset Management. and File name to CTGTMP. From the Summary panel.

a. Before you begin Microsoft SQL Server provides limited multilingual support. this field must be blank. substituting 2005 for 2008 in directory paths. 144 Installation Guide: . complete the following steps before launching the Maximo Asset Management installation program: This procedure describes an installation of Microsoft SQL Server 2008. Open Programs → Microsoft SQL Server 2008 → Configuration Tools → SQL Server Configuration Manager b. expand SQL Server Network Configuration → Protocols for <instance name>. and then double-click TCP/IP. Configure the listener port. Follow the same procedure to install Microsoft SQL Server 2005. Start by first stopping all processes that are running for the database instance (ctginst1). If the TCP Dynamic Ports field contains a value of 0. d. click the IP Addresses tab. ensure that the TCP Dynamic Ports field is blank. that IP address is using dynamic ports. From the Microsoft SQL Server Configuration Manager navigation pane. French. For each IP address listed. In the TCP/IP Properties dialog box.After you have installed a fix pack. a database instance can support English. You can support multiple languages on one database instance only if they share the same character set. 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. to open this port in the firewall. c. If enabled. For each IP address listed. e. 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. For example. and Portuguese which use the same character set but does not support Portuguese and Chinese because they have different character sets. you will also need to run the db2iupdt command to update the DB2 instance. Procedure 1. the default instance of the Microsoft SQL Server Database Engine listens on TCP port 1433. 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. enter 1433 for the TCP Port field. Since Maximo Asset Management requires Microsoft SQL Server to listen on a static port. When connecting to a named instance across a firewall. configure the Database Engine to listen on a specific port.

and then close SQL Server Configuration Manager. and select New Database. Click New Query. Open Microsoft SQL Server Management Studio (Start → Programs → Microsoft SQL Server 2008 → SQL Server Management Studio) b. Select the Maximo Asset Management database (maxdb71) from the Available Databases drop-down menu. to stop and restart Microsoft SQL Server. Enter the following script to change the database owner to maximo. a. Deployment of Maximo Asset Management with manual configuration of middleware 145 . Right-click SQL Server (<instance name>) and then click Restart. Create a Microsoft SQL Server Database. restart the server. To determine if Full-text Search is installed on your existing Microsoft SQL Server database. f. 4. Click OK. f. To install Full-text Search. 3. Enter the following script to create the Microsoft SQL user ID MAXIMO with a password of MAXIMO. click SQL Server Services. and enter the credentials for the sa user ID. modify the log settings to accommodate your production environment. d. Verify the Microsoft SQL Server instance is running. 2. choose SQL Server Authentication as the authentication type. In the Database name field. To finish the installation process. Right-click the Databases folder from the tree view. change the Initial Size (MB) attribute to 500 (MB).f. e. c. sp_changedbowner MAXIMO go Chapter 6. Navigate through the wizard and enable the Full-Text Search option located on the Custom portion of the Setup Type dialog box. Open SQL Server Management Studio (Start → Programs → Microsoft SQL Server 2008 → SQL Server Management Studio) b. sp_addlogin MAXIMO. g. you must do so at this time. c. Open SQL Server Management Studio. From the SQL Server Configuration Manager navigation pane. c. specify a unique database name (for example maxdb71) d. and then click Connect. Type the following command: select FULLTEXTSERVICEPROPERTY ( 'IsFulltextInstalled' ) If you did not install Full-text Search (the resulting value is zero). Create the Maximo User for Microsoft SQL Server. a. b. h. e. For the maxdb71 Logical Name. perform the following steps: a. If you prefer. Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server 2008. unrestricted growth. i. insert the Microsoft SQL Server 2008 product media into the system and launch the installation wizard. Click Execute. Click OK. and set the Autogrowth value to By 1MB. Click New Query.MAXIMO go This value is case sensitive.

be aware of the product-specific syntax rules for using special characters in an LDAP string. for example.DataFilegroupName=<your logical name> 3. 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. entries in LDIF files. Manually configuring IBM Tivoli Directory Server Use the following instructions to manually configure IBM Tivoli Directory Server for use with Maximo Asset Management. Note: While you can technically share a DB2 instance between Maximo Asset Management and the one needed by IBM Tivoli Directory Server. Important: When entering LDAP values for Maximo Asset Management installation panel fields. or values you enter directly into an directory instance using the directory server's own tools. you must create a new instance of IBM Tivoli Directory Server. special characters must be preceded by an escape character in order to make it readable by the directory server.properties file: Database. you must complete the following steps after you set up the database and create the Maximo user: 1. and you do not precede the blank character with an escape character. Refer to the product documentation for your directory server for more information on special characters in LDAP strings. located in the <MAM_HOME>\scripts directory. Run the Maximo Asset Management installation program and choose the Do not run the configuration step now option. Therefore. 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. 2. Click Execute. Run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility.g. Failing to escape special characters contained in an LDAP string used with Maximo Asset Management will result in Maximo Asset Management errors.SQL. Add the following property to the <Maximo_Home>\applications\maximo\ properties\maximo. About this task To configure IBM Tivoli Directory Server before launching the Maximo Asset Management installation program. it is not a 146 Installation Guide: . 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 will encounter Maximo Asset Management errors that will be difficult to troubleshoot. if you mistakenly enter an LDAP string that contains a blank. Many directory server products consider a blank space as a special character that is part of the LDAP string. at the end of a field value. In most cases.

Using your preferred method. In the TCP/IP settings for multihomed hosts panel. During the installation. create a user on the system and assign it to the appropriate group. db2iadm1. separate instances are created for use by Maximo Asset Management and IBM Tivoli Directory Server. select Listen on all configured IP addresses. Procedure 1. From the Instance details window. and then click Next. If the Instance Administration Tool is not already started. In the Create a new instance window. User name Select idsccmdb as the system user ID of the user who will own the instance. and then click Next. This name will also be the name of the instance. click Create an instance.2/sbin/idsxinst at the command line. Install location Enter the location where the instance files will be stored. 6. complete the following fields. click Create a new directory server instance. If you are using the automated installation programs./opt/IBM/ldap/V6. In the Instance Administration Tool. 2. enter idsccmdb as the value for the DB2 instance name field. 7. ensure you are logged in as an administrator on the system. In the DB2 instance details panel. the database instance restarts.recommended practice. This value must be a minimum of 12 characters. which can disrupt the availability of IBM Tivoli Directory Server to your enterprise.2 → Instance Administration Tool. and then click Next. 8. In the TCP/IP port settings panel. Deployment of Maximo Asset Management with manual configuration of middleware 147 . Server port number Enter 389 as the contact port for the server. and then start the tool Windows OS Select Programs → IBM Tivoli Directory Server 6. Encryption seed string Type a string of characters that will be used as an encryption seed. 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. Chapter 6. 5. and then click Next. and then click Next. 4. 3. The user idsccmdb must have root assigned as its primary group. Linux or UNIX OS Type . Instance description Enter a brief description of the instance. and idsldap groups. complete the following fields.

Database name Enter idsccmdb as the database to be used with this directory instance. and then click Next. and then click Next. this must be a drive letter. Admin daemon secure port number Enter 3539 as the administration daemon secure port. the location must be a directory name. 11. 12. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected. In the Database options panel. Administrator DN Enter cn=root for the administrator distinguished name. Database user name Enter idsccmdb as the database user. In the Verify settings panel. and then click Next. Click Close to close the window and return to the main window of the Instance Administration Tool. In the Configure administrator DN and password window panel. and then click Next. 9. Admin daemon port number Enter 3538 as the administration daemon port. such as /home/ldapdb. Linux or UNIX OS For non-Windows platforms. 16. 14. Click Close to exit the Instance Administration Tool. Administrator Password Enter a password for the Administrator DN. complete the following fields. 10. leave the following options selected. 148 Installation Guide: . complete the following fields. Password Enter the password for the idsccmdb user.Server secure port number Enter 636 as the secure port for the server. Database install location Type the location for the database in the Database install location field Windows OS For Windows platforms. Configure admin DN and password Configure the administrator DN and password for the instance now. complete the following fields. review the instance creation details provided. 15. Launch the IBM Tivoli Directory Server Configuration Tool: 13. In the Option steps panel. 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. Configure database Configure the database for the directory server now. From the Configure database panel. and then click Finish to create the idsccmdb instance.

Important: Before you begin this procedure.c=US 19.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. Base Maximo Asset Management required users User wasadmin maxadmin mxintadm maxreg Here is an example of the default base ldif data: dn: o=ibm. Define the following users and groups and their positions within the ou=users and ou=groups DN's you created. Add the DN information.o=IBM.c=us ou: users Chapter 6.2/sbin/idsxcfg at the command line. DC=IBM and DC=COM would indicate a domain forest of ibm.2 → Instance Administration Tool.com®. In the Manage suffixes panel. o=IBM. 20. for example: v ou=SWG.c=US v ou=users v ou=groups Note: ou=SWG. o=ibm. Deployment of Maximo Asset Management with manual configuration of middleware 149 .ou=SWG. Create and save an LDIF file. You can replace the example shown above with the directory structure of your own organization.Windows OS SelectPrograms → IBM Tivoli Directory Server 6. o=ibm. 18. 17.c=us objectClass: top objectClass: organization o: IBM dn: ou=SWG. Select Manage suffixes./opt/IBM/ldap/V6.ou=SWG. Click OK.c=us ou: groups objectClass: top objectClass: organizationalUnit dn: ou=users. These users and groups are defined in order for Virtual Member Manager to be used to secure Maximo Asset Management. ensure you have the following users and groups created in your LDAP repository: Table 15.o=IBM. type the following suffix. o=ibm. and then click Add.c=us ou: SWG objectClass: top objectClass: organizationalUnit dn: ou=groups. Linux or UNIX OS Type .

Use the browse button to locate the LDIF file.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 uid: wasadmin userpassword: wasadmin objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: person objectclass: top title: WebSphere Administrator sn: wasadmin cn: wasadmin dn: uid=maxadmin. In the IBM Tivoli Directory Server Configuration Tool. o=ibm. Click Import. Note: Before you can import an LDIF file on UNIX systems.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.ou=users. click Import LDIF data.ou=SWG. ensure that you remove the ^M characters from the file before using. o=ibm. Manually configuring Microsoft Active Directory You can manually configure Microsoft Active Directory for use with Maximo Asset Management. o=ibm.ou=users. Close the IBM Tivoli Directory Server Configuration Tool and restart the server.ou=SWG. you must run the dos2unix command to format the file. 21.ou=SWG.objectClass: top objectClass: organizationalUnit dn: cn=wasadmin. 24.ou=users.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg. 23. 22. 150 Installation Guide: .

click OK. Click OK. and then click Raise. 5.Before you begin Use this procedure to manually create users and groups within Microsoft Active Directory. When the domain raise task has completed. You can create these users and groups automatically if you configure SSL communication between Microsoft Active Directory and WebSphere Application Server Network Deployment. Enter Groups as the name for the new OU then click OK. An alert dialog box will appear.User dialog. you can change these default passwords to conform to a stricter security policy. Enter Users as the name for the new OU then click OK. and then click OK. complete the following steps before running the Maximo Asset Management installation program: Procedure 1. It is sometimes necessary to temporarily alter theMicrosoft Active Directory security policy to create these accounts in the required format. 8. Create a groups object under the SWG organizational unit: a. b. and select New → Organizational Unit. 6. b. and select New → Organizational Unit. Deployment of Maximo Asset Management with manual configuration of middleware 151 . Important: The users and passwords you create in the following steps must match this exact configuration for the deployment to succeed. Right-click the SWG OU. right-click the domain you want to work with and select New → Organizational Unit. Edit the functional level of the domain by selecting Action → Raise Domain Functional Level. 7. Create the wasadmin user: a. Right click the Users OU and select New → User. enter the following values. 2. 10. for example. About this task If you choose to manually configure a Microsoft Active Directory resource for use with Maximo Asset Management. 9. 3. After installation. Select Start → Control Panel → Administrative Tools → Microsoft Active Directory Users and Computers and then select the domain that you will be working with. b. In the Microsoft Active Directory Users and Computers user interface. Although you can use Windows Server 2008 as a platform for the administrative workstation. Enter a name for the new Organizational Unit (OU). Instructions for configuring SSL are provided following this section. Right-click the SWG OU. The Raise Domain Functional Level dialog box will appear. or to host middleware. From the New Object . SWG. Maximo Asset Management does not support Active Directory on Windows Server 2008. 4. Select Microsoft Windows Server 2003 from the Select an available domain functional level dropdown menu. and then click Next: Chapter 6. Create a users object under the SWG organizational unit: a.

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

12.properties file and provide the desired value for the mxe. Chapter 6. 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. Last name Leave this field blank.User dialog.properties file and provide the same password value for the maximo. and then click Next: First name Enter mxintadm. and then click Next: Password Enter maxadmin as the password for the maxadmin user. Complete the following steps if you choose to use a different value for the maxadmin password: 1) Complete middleware installation and configuration. Right click the Users OU and select New → User. enter the following values. If you must use a different password value for this user. From the New Object . Enter values that comply with the password policy of your organization. Review the password settings in the summary panel. The preceding values are examples. Create the mxintadm user: a. enter the following information. you must defer the configuration step of the Maximo Asset Management installation. Deployment of Maximo Asset Management with manual configuration of middleware 153 . providing a password value other than maxadmin for the maxadmin user. Complete the installation. and perform installation configuration later. This password value is required and expected by the Maximo Asset Management installation program.password property. modify property values. d. User must change password at next logon Ensure this check box is deselected.report. and complete the configuration using the taskrunner utility. 4) Edit the <MAM_HOME>\etc\install. 3) Proceed with the installation and select the option Copy files now.adminPasswd property.c. b. Password never expires Ensure this check box is selected. 2) Begin the Maximo Asset Management installation. From the next panel. including the manual Microsoft Active Directory configuration tasks described in this topic. Account is disabled Ensure this check box is deselected. Initials Leave this field blank. User cannot change password Ensure this check box is selected. manually .birt. and click Finish.

User must change password at next logon Ensure this check box is deselected. b. Leave the default value of the second field. and click Finish. Initials Leave this field blank. User cannot change password Ensure this check box is selected. enter the following values. From the next panel. User login name Enter mxintadm in the first field. Last name Leave this field blank. d. Leave the default value of the second field.Full name Enter mxintadm. User login name (pre-Microsoft Windows 2000) This field is filled with the same value (maxreg) entered for the User login name. User login name (pre-Microsoft Windows 2000) This field will be filled with the same value (mxintadm) entered for the User login name. Account is disabled Ensure this check box is deselected. and then click Next: First name Enter maxreg. 13. enter the following information. and then click Next: Password Enter a 7 character value as the password for the mxintadm user. Password never expires Ensure this check box is selected. You should set these fields to values that comply with the password policy of your organization. c. enter the following information. Review the password settings in the summary panel. From the next panel.User dialog. From the New Object . and then click Next: Password Enter a 7 character value as the password for the maxreg user. c. Right click the Users OU and select New → User. The preceding values are examples. User login name Enter maxreg in the first field. 154 Installation Guide: . User must change password at next logon Ensure this check box is deselected. Create the maxreg user: a. Full name Enter maxreg.

or Groups dialog. On the Advanced panel. 14. From the MAXADMIN properties dialog. click Find Now. click Find Now. The preceding values are examples. From the Search results list. b. Double-click the MAXIMOUSERS group listed in the Groups pane. Account is disabled Ensure this check box is deselected. From the Select Users. 16. Password never expires Ensure this check box is selected. From the MAXIMOUSERS properties dialog. Add users to the MAXIMOUSERS group: a. Click on the Groups object under the SWG OU. g. Click on the Groups object under the SWG OU. Click OK to add the users. d. Deployment of Maximo Asset Management with manual configuration of middleware 155 . or Groups dialog. e. f. and then click OK. Ensure you are selecting the maxadmin user and not the maxadmin group from this list. e. On the Advanced panel. Contacts. b. Double-click the MAXADMIN group listed in the Groups pane. Computers. Chapter 6. and click Finish. d. 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. maxreg. Review the password settings in the summary panel. 15. and then click OK. and mxintadm users. Click OK to add the users. g. select the Members tab and then click Add. d. Enter values that comply with the password policy of your organization. From the Search results list.User cannot change password Ensure this check box is selected. 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. select the Members tab and then click Add. Ensure you are selecting the maxadmin user and not the maxadmin group from this list. select the maxadmin and mxintadm users. Computers. Contacts. c. click Advanced. click Advanced. You can now exit the Microsoft Active Directory Users and Computers user interface. f. select the maxadmin. From the Select Users. c. Add users to the MAXADMIN group: a.

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

From the Download a CA Certificate. From the Download CA Certificate. enter the fully qualified name of the machine hosting Microsoft Active Directory.8. enter the following information and then click Submit. 18. or CRL.com/ certsrv From the Certificate Services page. From the Advanced Certificate Request page.cer file. From the Certificate Store panel.com/certsrv.COM. click advanced certificate request.ism71. 31.ism71. 16. browse to the location of your serverRootCA. click the back button. Launch Internet Explorer. click Add. 13. enter http://mymachine. Restart the system. From the Advanced Certificate Request page. or CRL page select Current for the CA certificate value. 32. 27. Select Computer account and then click Next. 29. Click OK on the Add/Remove Snap-in dialog box to close it. navigate to http://mymachine. From the Trusted Sites dialog box. Deployment of Maximo Asset Management with manual configuration of middleware 157 . 33. select Certification Authority and then click Add.cer. 26. 28. 21. 9. click Create and submit a request to this CA. select Certificates and then click Add. 19. Select Local computer: (the computer this console is running on) and click Finish.com in the Add this Web site to the zone: field. From the Add Standalone Snap-in dialog box. 17. In the Microsoft Management Console. 25. 24. Launch the Microsoft Management Console. 11. Select File → Add/Remove Snap-in. From the File to Import panel of the Certificate Import wizard. Using Internet Explorer. 10. or CRL page. This value must be capitalized. Certificate Chain. Right-click Certificates and select All Tasks → Import. From the Add/Remove Snap-in dialog box. When prompted. and then click Download a CA Certificate. From the Request a Certificate page. Certificate Chain. 20. select it. 23. Select Local computer: (the computer this console is running on) and click Finish. and then click Next. Click Close to close the Add Standalone Snap-in dialog box. for example MYMACHINE. 14. 15. From the Add Standalone Snap-in dialog box. and then click Close.ISM71. 34. click install this CA certificate chain. choose Base 64 for the Encoding method. select Place all certificates in the following store. When the task has completed successfully. navigate to Console Root → Certificates (Local Computer) → Third-Party Root Certification Authorities. Enter the following address in the browser: http://mymachine.ism71. Select Tools → Internet Options → Security and click Sites. click Add. Identifying Information For the Name field. click Request a certificate. 22. click Next. click Download a CA certificate. Certificate Chain. From the Certificate Services page. and then click Finish. 12. Chapter 6. 30. specify the type as Security Certificate and save the security certificate file as serverRootCA.

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

cer. From the WebSphere Application Server Network Deployment administrative console. 64. 56. Click Add. select Base-64 encoded X. Deployment of Maximo Asset Management with manual configuration of middleware 159 . Use specific SSL alias Ensure that this option is selected with a value of CellDefaultSSLSettings.CER).cer file in the File name field. From the WebSphere Application Server Network Deployment administrative console. and then click Finish. Update the following properties and then click OK. export the certificate as serverAuthCert. If it is not set to cn. and then click OK. and then click OK. From the Certificate Export Wizard Welcome panel. select Security → SSL certificate and key management. Chapter 6. 61. Port Update this value to 636. 63. 73. 65. select No.cer file in the File name field. Enter MSADServerAuthCert for the Alias.cer. From the File to Export panel. 62. 76. and then click Next. Click Keystores and certificates. click Next. Copy serverRootCA. click Next. 75. 60.cer and serverAuthCert. From the Add signer certificate page. applications. select Security → Secure administration. enter the path (including the file name) to the serverRootCA. and then click Finish. From the File to Export panel.55. Restart the domain manager. 74. From the Available realm definitions drop-down list.CER). 72. enter the path (including the file name) to the serverAuthCert. Requires SSL communications Ensure that this option is selected. 57. From the Export File Format panel.cer to the WebSphere Application Server Network Deployment system. From the Export Private Key panel. Invoke the WebSphere Application Server Network Deployment administrative console. 67. 69. 71. enter MSADServerRootCA for the Alias.509(. Click Signer certificates and then click Add. do not export private key. 70. and then click Configure. click Next. select Base-64 encoded X. From the Export File Format panel. click the PersonAccount entity type and set it and then save the changes. and then click Next. Login properties Set this value to cn. and then click Next.509(. and infrastructure. export the certificate as serverRootCA. Click Supported entity types and verify that the PersonAccount entity type is set to cn. 66. Right-click the lowercase certificate entry and select All Tasks → Export 58. Click CellDefaultTrustStore. select Federated repositories. Click the repository identifier for Microsoft Active Directory listed in Repositories in the realm table. 68. 59.

Click Next in the Welcome dialog box. Click Next. For 64-bit platforms. Host name. Select the create a deployment manager option. Click Next. Click Next. 6.Manually configure the J2EE server This section contains instructions for manually configuring an existing J2EE server for use by Maximo Asset Management. 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. 7. you must configure it manually. To configure the J2EE server prior to launching the Maximo Asset Management installation program. Creating WebSphere Application Server Network Deployment profiles: If you are manually configuring WebSphere Application Server Network Deployment.com/support/docview. 4.ibm. Accept the default value or specify a Profile name. and Cell name. If you want to deploy Maximo Asset Management using Oracle WebLogic Server. Note the Administrative port number. You will use this context when invoking the console through a browser. A supported JDEE server must be installed and configured before you install Maximo Asset Management. Accept the default values or specify the Node name. 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. Accept the default installation location.p12 2. you can perform a manual configuration if automatic configuration does not meet your requirements. 8. Review the assigned port numbers. follow these steps: IBM WebSphere Network Deployment 1. Manually configuring Websphere You can configure Websphere manually to work with Maximo Asset Management. 5. If you want to deploy Maximo Asset Management with WebSphere Application Server Network Deployment. Click Next. 160 Installation Guide: . 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. Click Next. see Creating IBM WebSphere Application Server profiles at http://www-01. Launch the profile creation wizard.wss?rs=0&q1=7015423 &uid=swg27015423&loc=en_CA&cs=utf-8&cc=ca&lang=en. 3.

11. in the case of LDAP. perform Virtual Member Manager (VMM) configuration for you. 24. which is a starting point within the hierarchical namespace of the virtual realm. 23.9. After Installation Verification completes. If VMM is configured to use SSL with a federated LDAP repository prior to completing the Maximo Asset Management installation. Review the port number listings. 22. Click Next in the Welcome dialog box. Click Next. Click Next in the Profile summary dialog box. Click Next in the Profile summary dialog box. 16. 17. close it. Click Finish. The federated repository consists of a single named realm. it must be done only after a successful Maximo Asset Management installation. Accept the default directory path. 12. Do not configure a WebSphere VMM LDAP federated repository to use Chapter 6. 10. Click Next. 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. close the output window. 14. Note that if you intend to configure VMM to use SSL with a federated LDAP repository. which is a set of independent user repositories. and federate that data into a single virtual repository. Select the Launch the First steps console check box. The root of each repository is mapped to a base entry within the federated repository. Select the Run the Application Server as a Windows service and log on as a local system account. Click Finish. If another First steps window is open. Click the Installation verification link. If you elected to manually configure Maximo Asset Management middleware for use with Maximo Asset Management. Deployment of Maximo Asset Management with manual configuration of middleware 161 . Use the launchpad command and click the Profile creation wizard to open the First Steps window (if not open already) . VMM provides you with the ability to access and maintain user data in multiple repositories. Accept the default values or specify the appropriate information. Each repository may be an entire external repository or. you will have to manually configure VMM. Click Next. then it will. the Maximo Asset Management installation program provided you with the option of automatically configuring Maximo Asset Management middleware. 13. 19. among other tasks. Specify a unique Profile name and select the Make this profile the default check box. About this task During the installation process. 21.. 15. Select the Launch the First steps console option. 20. 18. the installation will fail. Select Create a custom profile. Click Next. a subtree within that repository. Click Exit. Click Next. If you elected to have the Maximo Asset Management installation program automatically configure Maximo Asset Management middleware. Specify a unique node name and the computer name (or IP address) of the machine where you are performing this installation. Click Next. Click Next.

Locate the User account repository section and select Federated repositories from Available realm definition. and then clicking Configure. 4. selecting Federated repositories from the Available realm definitions drop-down list. Login to the admin console. applications. located under Related Items. applications. substitute the values you used when you configured Microsoft Active Directory where appropriate in this procedure. Support referrals to other LDAP servers Set this to ignore. Click Add to create new repository definition under the current default realm. Certificate mapping Select EXACT_DN 6. 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. To configure VMM to use Microsoft Active Directory. Configure SSL after the Maximo Asset Management installation program has completed successfully. These instructions are for IBM Tivoli Directory Server. Directory type Select the directory type. and infrastructure. Return to the Federated repositories page by clicking Security ? Secure administration. You must also modify the VMM cron task.SSL with an LDAP directory prior to installing Maximo Asset Management. Repository identifier Enter ISMITDS. then navigate to Security > Secure administration. Bind distinguished name Enter cn=root Bind password Enter the password for the bind distinguished name. 162 Installation Guide: . 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. Multiple base entries can be added with different search bases for a single LDAP directory. 3. ensure you have a wasadmin user created in your LDAP repository. and infrastructure. Login properties Leave this value blank. Click Manage repositories. 5. To add the IBM Tivoli Directory Server to VMM. Enter the following values. complete the following steps: 1. To add an LDAP directory to the VMM virtual repository. 2. and then click Apply and the click Save. Important: Before you begin this procedure. Port Enter 389. and then click Configure. in this example.

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

Leave Queue checked as the destination type. 11. From the WebSphere Application Server Network Deployment Administrative Console. 10. Click Save. 168 Installation Guide: . is a virtual place within a service integration bus where applications can attach and exchange messages. Before you begin About this task To add a logical address for the sequential inbound bus destination queue (SQINBD) within the service integration bus. 6.Before you begin About this task To add a logical address for the continuous inbound bus destination queue (CQINBD) within the JMS bus. A bus destination. then click Next to open the Create a new queue for point-to-point messaging dialog box. 3. then click Finish to complete the creation of the CQINBD bus destination queue. 13. 9. complete the following steps: Procedure 1. 7. Click None as the Exception destination value. Type CQINBD in the Identifier field and Continuous Queue Inbound in the Description field. 4. Click Destinations under Destination resources to open the Buses → intjmsbus → Destinations dialog box. 2. click Service Integration → Buses to open the Buses dialog box. Click Apply. for example CQINBD. 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. Review your selections. Click Next to open the Confirm queue creation dialog box. 8. 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. 5. From the WebSphere Application Server Network Deployment Administrative Console. 2. 12. then click CQINBD to open the configuration dialog box. Navigate the path Buses → intjmsbus → Destinations. Click intjmsbus to open the Buses → intjmsbus dialog box. Click New to open the Create new destination dialog box. and click Next to open the Create new queue dialog box. complete the following steps: Procedure 1. Click intjmsbus to open the Buses → intjmsbus dialog box. click Service Integration → Buses to open the Buses dialog box.

Click Save. 2. Click Next to open the Confirm queue creation dialog box. for example SQOUTBD. 6. 6. Note that you must use this value and it must contain only uppercase letters. From the WebSphere Application Server Network Deployment Administrative Console. 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. A bus destination. Leave Queue checked as the destination type. Review your selections. then click Next to open the Create a new queue for point-to-point messaging dialog box. Click Destinations under Destination resources to open the Buses → intjmsbus → Destinations dialog box. Chapter 6. Before you begin About this task To add a logical address for the sequential outbound bus destination queue (SQOUTBD) within the service integration bus. 13. 10.3. Click New to open the Create new destination dialog box. click Service Integration → Buses to open the Buses dialog box. then click Finish to complete the creation of the SQINBD bus destination queue. 9. then click Next to open the Create a new queue for point-to-point messaging dialog box. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. 5. Note that you must use this value and it must contain only uppercase letters. then click SQINBD to open the configuration dialog box. 12. 4. 4. Click New to open the Create new destination dialog box. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the Description field. 5. complete the following steps: Procedure 1. and click Next to open the Create new queue dialog box. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the Description field. 3. Click Apply. Click None as the Exception destination value. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer 8. and click Next to open the Create new queue dialog box. 7. is a virtual place within a service integration bus where applications can attach and exchange messages. Deployment of Maximo Asset Management with manual configuration of middleware 169 . Click intjmsbus to open the Buses → intjmsbus dialog box. Click Destinations under Destination resources to open the Buses → intjmsbus → Destinations dialog box. Navigate the path Buses → intjmsbus → Destinations. 11. Leave Queue checked as the destination type.

10. 170 Installation Guide: . 8. 3. Click New. Click Save. Click None as the Exception destination value. Click Next to open the Confirm queue creation dialog box. 13. 2. 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. 7. Verify that the Default Messaging Provider is selected and click OK. Navigate the path Buses → intjmsbus → Destinations. Review your selections. 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. From the Scope drop-down list select Cell=ctgCell01. and then click Apply.7. 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. then click Finish to complete the creation of the queue. 4. Enter the following information: Name Enter intjmsconfact. 6. From the WebSphere Application Server Network Deployment Administrative Console. 9. click Resources → JMS → Connection factories. Click Apply. 8. complete the following steps: Procedure 1. Bus name Select intjmsbus. 12. Click Apply. JNDI name Enter jms/maximo/int/cf/intcf. Before you begin About this task To create the JMS connection factory. 5. Click Save. Click OK. then click SQOUTBD to open the configuration dialog box where you must make the following changes: 11.

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

6. Verify that the Default Messaging Provider is selected and click OK. Click Save. From the Scope drop-down list. 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. 6. 4. Procedure 1. 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. JNDI name Enter jms/maximo/int/queues/sqout Bus name Select intjmsbus. Click OK. Click New. click Resources → JMS → Queues. Name Enter SQOUT. Click Save. 2. Enter the following information. Note that this value must contain only uppercase letters. 5. 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. 7. From the WebSphere Application Server Network Deployment Administrative Console. 7. Click OK. and click OK. 3. select Cell=ctgCell01. 172 Installation Guide: . Queue name Select SQOUTBD.Queue name Select SQINBD.

Click intjmsbus to open the Buses → intjmsbus dialog box. click Service Integration → Buses to open the Buses dialog box. 9. 17. Click Destinations under Destination resources to open the Buses → intjmsbus → Destinations dialog box. Click Save. 13. Chapter 6. Click Destinations under Destination resources to open the Buses → intjmsbus → Destinations dialog box. then click Finish to complete the creation of the CQINERRBD bus destination queue.Before you begin About this task Complete the following steps: Procedure 1. Click Specify and enter CQINERRBD as the exception destination value. 18. From the WebSphere Application Server Network Deployment Administrative Console. 19. 7. Specify CQINERRBD as the exception destination. . 2. 12. Set the Maximum failed deliveries value to 5. 16. Deployment of Maximo Asset Management with manual configuration of middleware 173 . then click Next to open the Create a new queue for point-to-point messaging dialog box. Navigate the path Buses → intjmsbus → Destinations. From the WebSphere Application Server Network Deployment Administrative Console. 3. click Service Integration → Buses to open the Buses dialog box. Click New to open the Create new destination dialog box. you create the Error queue. Select CQINBD. Review your selections. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. then click CQINERRBD to open the configuration dialog box where you must make the following changes: a. What to do next Creating the error (CQINERR) JMS queue: After creating the Error Queue Bus Destination. Click intjmsbus to open the Buses → intjmsbus dialog box. 11. Leave Queue checked as the destination type. 14. 5. Click Next to open the Confirm queue creation dialog box. 4. 10. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer 8. 6. 15. Click Apply. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. b. Note that you must use this value and it must contain only uppercase letters. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the Description field. and click Next to open the Create new queue dialog box. Click Save. Change the Maximum failed deliveries value to 5. Click OK.

This value must be lowercase. JNDI name Enter jms/maximo/int/queues/cqinerr Bus name Select intjmsbus. 4. 2. Click OK. Click OK. Note that this value must contain only uppercase letters. 2. From the Scope drop-down list. Enter the following information. Name Enter CQINERR. 7. 5. and then click Apply. select Cell=ctgCell01. 5. and click OK. click Resources → JMS → Queues. 4. and then click OK. Enter the following information. From the WebSphere Application Server Network Deployment Administrative Console. From the WebSphere Application Server Network Deployment Administrative Console. Procedure 1. Click New. 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. complete the following steps. 3. click Resources → JMS → Activation Specifications.Before you begin About this task To create the Error queue. Click Save. JNDI name intjmsact 174 Installation Guide: . Queue name Select CQINERRBD. Verify that the Default Messaging Provider is selected and click OK. From the Scope drop-down list. 3. 6. Before you begin About this task Complete the following steps to activate the CQIN queue: Procedure 1. Name intjmsact This value is case-sensitive. select Cell=ctgCell01. Click New to complete the General Properties section for the new JMS activation specification.

Click Save. 4. 6. 8. Before you begin About this task Complete the following steps to activate the CQINERR queue: Procedure 1. From the Scope drop-down list. and click OK. Chapter 6. Name Enter intjmsacterr. JNDI name Enter intjmsacterr. Enter the following information. This value must only contain lowercase letters. Destination type Enter Queue. Click New to complete the General Properties section for the new JMS activation specification.Destination type Queue Destination JNDI name jms/maximo/int/queues/cqin Bus name intjmsbus Maximum concurrent endpoints 10 6. select Cell=ctgCell01. 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. Destination JNDI name jms/maximo/int/queues/cqinerr Bus name intjmsbus Maximum concurrent endpoints 10 Click OK. This value must be the same as the one used for the Name field. Deployment of Maximo Asset Management with manual configuration of middleware 175 . From the WebSphere Application Server Network Deployment Administrative Console. 5. 7. Ensure you stop all IBM-related processes and daemons. click Resources → JMS → Activation Specifications. Click OK. 3. and then click Apply. You must now restart these processes for the update to take effect. 2. Click OK. and then click Save. 9.

Select mxsibusr from the User drop-down list. Start the bus member for the ctgNode MXServer intjmsbus if it is not started.nd. b. a. j. 3. Open DB2 Control Center. including the usage of products other than DB2. c.websphere. a user named mxsibusr with a password of mxsibusr.ibm. Click Apply. For more information about WebSphere Application Server Network Deployment message storage.jsp?topic=/ com. Navigate down to the Databases folder listed under your system. Right-click DB Users and select Add. Configure J2C authentication data and JDBC provider in WebSphere Application Server Network Deployment. Once the database has been created. About this task You have the option of having WebSphere Application Server Network Deployment use a DB2 database to store JMS messages. c. complete the following steps: Procedure 1. Open and login to the WebSphere Application Server Network Deployment Administrative Console. g.boulder. Create a database named maxsibdb using default settings. Under the Authentication header. Complete the following fields in the User identity form. b. you will need to create a data source in order to store JMS messages in a DB2 database.ibm. i. What to do next Manually creating a data source for the persistent store: If you chose to manually configure WebSphere Application Server Network Deployment. d. Navigate to Security → Secure administration. Click New. a. For example. 176 Installation Guide: .boulder. restart MXServer under Servers → Application servers.nd. refer to http:// publib. expand the maxsibdb database and select User and Group objects. d.html and http:// publib.websphere.com/infocenter/wasinfo/v6r1/index.10. click on Java Authentication and Authorization Service → J2C authentication data.doc/info/welcome_nd. applications.ibm.ibm.jsp?topic=/ com. Right-click the Databases folder and select Create Database → Standard. and infrastructure. Create a system user and password on the server hosting the database server.html To create a data source for the persistent store. Create and configure the database. If you cannot start ctgNode MXServer intjmsbus. 2. e. h. Verify that you can connect to the database using the mxsibusr user by right-clicking maxsibdb and selecting Connect. f. Grant all authorities to the mxsibusr with the exception of Security administrator authority.pmc.com/infocenter/wasinfo/v6r1/index. e.doc/tasks/tjm0035_.

g. Click New. i. Configure WebSphere Application Server: a.jar and <DB2_HOME>/java/db2jcc_license_cu. Click Save. Specify the following values: Data source name intjmsds JNDI name jdbc/intjmsds e. Click Scope and then select Cell=ctgCell01. d. 177 . Click Next. Description SIB database user alias. Click New. navigate to Resources → JDBC → Data sources. n. l. o.jar to the <WAS_HOME>\ctgMX\lib directory. and then click Save. From the Component-managed authentication alias and XA recovery authentication alias drop-down list.jar and db2jcc_license_cu. Specify the following values. j.Alias maxJaasAlias User ID mxsibusr Password Password you created for mxsibusr. Deployment of Maximo Asset Management with manual configuration of middleware f. Click Finish. 4. b. and then click Apply: Database type DB2 Provider type DB2 Universal JDBC Driver Provider Implementation type XA data source Name maxJdbcProvider k. C:\Program Files\IBM\WebSphere\ AppServer\ctgMX\lib. c. From the WebSphere Application Server Network Deployment Console. Complete the WebSphere Application Server variable ${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of <WAS_HOME>ctgMX\lib. Click Next. Click Next. select maxJaasAlias f. and then click Apply. Chapter 6. From the WebSphere Application Server Administrative Console navigation pane. For example. Go back to Resources → JDBC → JDBC Providers → maxJdbcProvider. Click Scope and then select Cell=ctgCell01. h. Open a command prompt and copy <DB2_HOME>/java/db2jcc.jar. and correct the Class path if required for both db2jcc. Ensure that each jar file has the full path from ${DB2UNIVERSAL_JDBC_DRIVER_PATH} 5. navigate to Resources → JDBC → JDBC Providers. Click Apply. m.

Ensure the Use this data source in container managed persistence (CMP) option is enabled. 178 Installation Guide: . Verify the data source by selecting intjmsds.2. Before you begin If you do not have Oracle WebLogic Server 9. follow these steps: Procedure 1. 6.2 installed. Click Finish. Click Next. 4.sh UNIX 2. h. From the Welcome window. About this task To configure the WebLogic server prior to launching the Maximo Asset Management installation program.g. k. Platform Windows Command From the Start menu: Start > All Programs > BEA Products > Tools > Configuration Wizard. follow the instructions that come with WebLogic Server to install it. accept the default to create a WebLogic domain and then click Next. Ensure that you do not install the Node Manager Service. and then click Next. j. Click Save. From the Select Domain Source window. Enter an administrator user name and a password and then click Next. cd to /<product_installation_dir>/common/ bin and type sh config. 3. 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. Port number Specify the DB2 port number. 50005. i. Specify the following values: Database name maxsibdb Driver type 4 Server name Specify the DB2 server host name. and then clicking Test Connection. accept the default value to generate a domain configured automatically and click Next. l. For example. and then select maxJdbcProvider from the drop-down list. Launch the Configuration Wizard. Choose Select an existing JDBC provider.

jar (Windows) PRE_CLASSPATH={WL_HOME}/server/lib/oraclethin. 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. c. 7. Using your text editor. Set the parameter as follows: set PRE_CLASSPATH=%WL_HOME%\server\lib\oraclethin.com. From the Customize Environment and Services settings window. Two instances must be replaced. From the Create WebLogic Domain window. Click Done. b. On Windows.0. From the Configure Server Start Mode and JDK window.0_04 in the Oracle Supplied JDKs section. d. Change the installation destination path to be within your Oracle Home folder. 8. About this task 1. 2. for example. JDK 1. b. If you select Yes. and Sun JDK 1. Accept any additional prompts to install the Sun JRE so that the installation process can complete successfully. What to do next You then must install the updated Sun JDK 1. Right-click and edit (do not double-click) setDomainEnv.5.cmd (Windows) or setDomainEnv.5.sun.exe c.5. Accept the license agreement. Start the installation program.5. 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. select Production Mode in the WebLogic Domain Startup Mode section. Install the updated Sun JDK 1. accept the default value or specify a different domain name and then click the Create button. The domain is created in a minute. a.5. Click Next. d.0 program. Windows: Navigate to C:\bea\user_projects\domains\mydomain\bin. for example. configure JMS options after you finish configuring the WebLogic Server. a.0_14.sh (UNIX). Obtain the latest Sun JDK 1. Performing post installation tasks for the WebLogic Server: Use this procedure to perform post installation steps for the WebLogic Server.5. e. and click OK then Next. Deployment of Maximo Asset Management with manual configuration of middleware 179 . Do not select the checkbox for Start Admin Server. it is jdk-1_5_0_14–windowsi586–p. Edit the domain configuration file for proper Java settings.0. 6.jar (UNIX) Note: This step is required for connecting to Oracle databases from the WebLogic Server. (Oracle only) Search for PRE_CLASSPATH. c:\bea\jdk150_14. from this URL: http://java. UNIX: Navigate to <home_directory>/bea/user_projects/domains/mydomain/ bin. select Yes if you plan to implement the integration framework. search for and replace jdk150_04 with jdk150_14 to point WebLogic to use the updated Sun JDK.

cmd file. Verify settings by Starting the WebLogic Server. Procedure 1. 4. define the required Java Message Service (JMS) Options at this time. Configuring JMS Options for the WebLogic Server: This procedure provides details on steps to configure JMS queues.sun. This procedure stores the user name and password in an encrypted format.0 -Dwlw.properties file.useCompatibleSerialVersionUID=1. To ensure that the edits that you made to the previous WebLogic files were accurate. If you save the file as boot.testConsole=%testConsoleFlag% -Dwlw.useCompatibleSerialVersionUID=1. If you have received the MEA Product Enabler and plan to implement the MEA.xml. Start the Server without being prompted for user name and password. the server reads the file and then overwrites it with an encrypted version of the User Name and password. start the WebLogic Server.QName.These parameters are case sensitive. See your Oracle WebLogic documentation on how to navigate through the Weblogic Server Administration Console. 2.logErrorsToConsole=%logErrorsToConsoleFlag% f. Before you begin You must be familiar with the Oracle WebLogic Server Administration Console to complete the following procedure. If you are working in Production mode and do not want to be prompted for the WebLogic user name and password. Ensure to include the minus (-) sign before each parameter and to include the m after each value. the server automatically uses this file during its subsequent startup cycles.QName. 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.0 The entry will look like this when complete: set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -Dcom.namespace. Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Create three persistent file stores with the following configuration parameters: Parameter File Store Name Value sqinstore sqoutstore cqinstore 180 Installation Guide: .iterativeDev=%iterativeDevFlag% -Dwlw. Insert an option right after this string as follows: -Dcom.properties and locate it in the mydomain folder (for example: c:\bea\user_projects\domains\mydomain).namespace. Launch Internet Explorer and open the MAXIMOSERVER Admin Console by typing the following URL: http://<host name>:7001/console. create a boot.sun. e. Sign in by entering your User ID and password. The first time you use this file to start a server.xml. Save and close the setDomainEnv. 3. 3.

Set the Maximum Messages per Session to -1. Add a connection factory resource to the JMS module: Parameter Name JNDI Name Target Value intjmsconfact jms/maximo/int/cf/intcf MAXIMOSERVER 7. From the Transactions tab. 6. Create a JMS system module named intjmsmodule with MAXIMOSERVER as the target server. b. Save and activate the changes. Create a new subdeployment with the same name as the queue. Assign the <subdeployment_name>server server target to the subdeployment. consult your WebLogic documentation. you can choose to create database-based stores. To choose between file stores and database-based stores.Parameter File Store Target File Store Directory Value MAXIMOSERVER C:\bea92 or another directory of your choice File stores have better performance in general. 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. Create the queue resource type. c. Chapter 6. check the XA Connection Factory Enabled checkbox. 4. Select the intjmsconfact link. Add three queue resources to the JMS Module: a. Enable the JMS connection factory for MEA: a. c. b. Deployment of Maximo Asset Management with manual configuration of middleware 181 . 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. 5. However. 9.

properties file. for example. If you cancel the installation program after entering values in several screens. do not use the following special characters when entering passwords for users. !. The program records deployment and configuration parameters that you select in each screen. The IBM Maximo installation wizard guides you through the product installation. database instances. how you create databases. ^. You can install middleware on any platform. Values that you supply to the IBM Maximo installation program are stored in the maximo. #. Installing Maximo Asset Management and manually configuring middleware After manual configuration of middleware you can install Maximo Asset Management. (. such as wasadmin: &. You must also delete the information in the MAXTEMP table in the database. the installation program reuses most of those values the next time you start the installation program.properties file which are stored in the MAM_HOME/maximo/ applications/maximo/properties/ directory. % 182 Installation Guide: .What to do next You must now stop and restart the MAXIMOSERVER application server for the update to take effect. Values that are not reused are the installation directory and the shortcut option you chose for a previous installation.properties file. you must add root to a group with SYSADM authority for the database instance before starting the Maximo Asset Management installation program. $.properties file and the install. but you must run the IBM Maximo installation program from the administrative workstation which must be installed on a supported Windows system. Installing Maximo Asset Management without automatic middleware configuration You can install Maximo Asset Management without automatic middleware configuration. |. If you intend to use DB2 on a Linux or UNIX system. ). and in the Maximo database. '. >. These values are retrieved and populated into installation screen fields if you run the installation program again. <. Before you begin Ensure that all middleware servers and services are started and active. and then installs and deploys the product based on this information. If you are installing WebSphere Application Server Network Deployment. You might choose manual configuration of middleware if your organization has policies and procedures that restrict. the install. To restore the defaults for a fresh installation. delete the old maximo. and users. ".

To avoid this problem. rename the files back to their original names. If you intend to perform multiple installations of the product using the same administrative workstation. Restart the installation program to continue with the license enablement The troubleshooting chapter describes errors that occur during theMaximo Asset Management installation. 4. 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.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes d On a 64-bit Windows system. exit the installation wizard. install the product using a user ID with administrative authority that contains only English language characters.exe -DPLATFORMONLY=yes -DLOADSAMPDATA=yes v When you are running the installation wizard. 6. where en is the language folder and dbtype is ora/sqs/db2. To create a maxdemo database. run the following command: install_win64. in turn. navigate to the directory where the Maximo Asset Management files are extracted. cause a WebSphere Application Server Network Deployment connection failure reporting error CTGIN0158E. This failure will. 3. From a command prompt navigate to ibm\smp\scripts and run the following command: taskrunner. Deployment of Maximo Asset Management with manual configuration of middleware 183 . 2. r 7. If you do not follow those instructions it may not be possible to use the same adminstrative workstation for multiple installations.. select the Copy files now. When the installation finishes. 3. review this information in the Planning to install Maximo Asset Management chapter before you begin the installation. 5. Perform installation configuration later option. On a 32-bit Windows system. When taskrunner successfully completes. Change to the install\MAM\Install\new folder. Copy the ibm\smp\maximo\tools\maximo\en\maxdemo file to ibm\smp\maximo\tools\maximo\en\maximo.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. run the following command: install. When taskrunner finishes running. Chapter 6. the installation fails with error message CTGIN2289E when attempting to install language packages. In the command line.If you plan to use Microsoft Active Directory to secure WebSphere Application Server Network Deployment. In the Run Configuration Step screen in the installation wizard (Step 31 in the procedure). Rename the ibm\smp\maximo\tools\maximo\en\maximo file. 2. create a maxdemo database by performing the following tasks: 1. complete either of the following two procedures: v Enter a command to create a maxdemo database: 1.

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

Instance Enter the name of the database instance to be used with Maximo. 11. The default instance name is ctginst1. The host name must be fully qualified. The default is 50005. Password Enter the password of the user ID that was used to run the middleware installation program. SQL Server Select this choice to use Microsoft SQL Server as the Maximo database. User ID Enter the user ID that was used to run the middleware installation program. Schema name Enter the schema name for the database. The default database name is maxdb71. DB2 Host name Enter the host name of the server hosting DB2. DB2 Select this choice to use DB2 as the Maximo database. and then click Next. select the product that you are using for the Maximo database.Host name Enter the host name of the system where the middleware installation program was run. C:\ibm\tivoli\mwi\workspace for Windows OS and /root/ibm/tivoli/mwi/workspace for Linux or UNIX OS. enter configuration information about the database. for example. 10. Workspace location Enter the location of the topology file that contains the values entered for the middleware installation program. Each database has its own unique set of configurable parameters and values. maximo. In the Database Type panel. the user and its associated home directory must exist on the DB2 server. Oracle Select this choice to use Oracle as the Maximo database. however. and then click Next. The name of the database schema is required to be the same value as the owner of the table spaces defined. Database Name Enter the name of the database to use with Maximo. Port Enter the port being used by DB2 instance. For example. The database is created if it does not exist. In the Database panel. This file is found in the workspace that was defined during the middleware installation task. Chapter 6. This instance is created if it does not exist. Deployment of Maximo Asset Management with manual configuration of middleware 185 .

Database User ID Enter the user ID used to access Microsoft SQL Server. The default is 1433 Database Name Enter the name of the database to use with Maximo. Database Password Enter the password for the user ID used 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 Microsoft SQL Server.Database User ID Enter the user ID used for Maximo to access DB2. The default is 1521 Instance Enter the name of the database instance to be used with Maximo. Microsoft SQL Server Host name Enter the host name of the server hosting Microsoft SQL Server. The default database name is maxdb71. This user ID cannot be the same one used as the instance administrator user ID. 186 Installation Guide: . Oracle Host name Enter the host name of the server hosting Oracle. This user ID is created if it does not exist. Database User ID Enter the user ID used for Maximo to access Oracle. Database Password Enter the password for the user ID used to access DB2. Default for all platforms is maximo. The default instance name is ctginst1. Default for all platforms is maximo. Port Enter the port being used by Oracle. The host name must be fully qualified. The host name must be fully qualified. Port Enter the port being used by Microsoft SQL Server. This user ID is created if it does not exist.

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

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

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

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

ou=SWG. 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.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. o=ibm. dn: uid=maxadmin. o=ibm.c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg dn: cn=maxadmin. you must have already created the schema when you configured Microsoft Active Directory.ou=groups. you must create them manually before continuing the installation from this point.ou=users. If you do not want to have the users created by the Maximo Asset Management installation program.ou=users. The values entered for User and Group base entry fields are used to configure the VMMSYNC crontask.c=us objectClass: groupofnames Chapter 6.ou=users.Group base entry If you do not plan to use the default LDAP schema provided with Maximo Asset Management.c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm. enter the group base entry you intend to use in this field. The default LDAP schema group base entry is ou=groups.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg. If you customize the schema. If you are not using the default LDAP schema provided with Maximo Asset Management.ou=SWG. you must have created it yourself before advancing beyond this panel. perform the tasks to synchronize users and groups that are described in the Post-installation tasks chapter.o=IBM. This operation requires write access to Virtual Member Manager. If you do not want the installation program to create users and groups automatically in Microsoft Active Directory. o=ibm.ou=SWG. o=ibm.ou=SWG.ou=SWG. Deployment of Maximo Asset Management with manual configuration of middleware 191 .

If you are using another database type.ou=SWG. Default for all platforms is 50000. Select this option if you are deploying Maximo Asset Management with Oracle or Microsoft SQL Server. Default for all platforms is mxsibusr. you cannot have the installation program configure message persistence. and then click Next. the installation wizard skips to step 26. Password Enter the password for the user ID used to access the database server. and you do not see this screen.o=IBM.ou=users.ou=users. Database name Enter the name of the database serving as the JMS data store. o=ibm. where you configure SMTP. Default for all platforms is maxsibdb.o=IBM. 23. the wizard skips to step 26.ou=SWG.ou=SWG. Port Enter the port used to access the database server. If you chose to persist JMS messages. In the Integration Adapter JMS Configuration panel. If you chose not to persist JMS messages.c=US cn: maximousers 22. JMS Data Source name Enter the name of the data source to be used by JMS.c=US member: uid=mxintadm. A JMS server requires a DB2 data repository to be configured to maintain messages.c=US member: uid=mxintadm. If you select this option. in the DB2 Database Server Configuration panel.o=IBM. 192 Installation Guide: . and then click Next. Host name Enter the fully qualified host name of the server hosting the JMS data store. User ID Enter the user ID used to access the database server.ou=SWG.objectClass: top member: uid=maxadmin.o=IBM. enter the following information. Note: The JMS data store can only be created as a DB2 database.ou=groups.ou=users. Select whether the JMS data store should be persisted.c=us objectClass: groupofnames objectClass: top member: uid=maxadmin. enter the following information.ou=SWG. 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.ou=SWG.c=US member: uid=maxreg. when you click Next.ou=users.ou=users.c=US cn: maxadmin dn: cn=maximousers.o=IBM. 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.

<MAM_HOME>\scripts\taskrunner CONTINUE <STOPONERROR|NOSTOPONERROR> Note: If you reboot the system. If you intend to use the taskrunner utility. and then allow you to run the configuration step at a later date. a. and performing configuration tasks using the values you have specified. Taskrunner data stores are not persisted. 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. 25. If you chose to persist JMS messages. in the WebSphere Application Server Network Deployment keystore file panel. Perform installation configuration later. If you chose not to persist JMS messages.properties file to configure Maximo Asset Management. the taskrunner utility can be run again after the error conditions have been rectified if it was run with the STOPONERROR parameter. and you do not see this screen. Run the taskrunner utility from the command line. The taskrunner utility resumes the installation at the point where the last successfully completed task Chapter 6. and then click Next.24. Deployment of Maximo Asset Management with manual configuration of middleware 193 . By selecting this option.properties file. see the Configuring SMTP topic in the Post-installation tasks chapter. Copy files now. copying files to your local system. do not reboot your system. specify SMTP information for use by workflows to communicate with workflow participants. decide how you would like to perform the configuration step of the installation. you can configure these parameters later. located in the <MAM_HOME>\scripts directory. 26. The Maximo Asset Management installation program is used to complete three tasks: gathering information about your Maximo Asset Management deployment and configuration. 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. If the installation fails. From the Run Configuration Step panel. navigate to where you copied the trust. and then click Next.p12 keystore. For instructions. and then click Next. In the SMTP Configuration panel. If you do not enter any information at this point. 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. the wizard skips to step 26. Select this option to have the installation program copy files to the system only. and it uses the configuration values stored in the maximo. You can run the configuration steps outside of the Maximo Asset Management installation program by using the taskrunner utility. The configuration values that you enter are stored in the <Maximo_Home>\applications\maximo\properties\ maximo. This address is used to send messages. you are not able to use the taskrunner utility to run configuration scripts.

In the Start Menu Select this option to create shortcuts for Maximo Asset Management in the Start menu. 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. the taskrunner continues despite errors. select the type of shortcut you would like to arrange for Maximo Asset Management. Deploy application files manually later Select this option to defer the deployment of application files. If you run taskrunner with the NOSTOPONERROR parameter. 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. 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 order to use the Start menu shortcut with Internet Explorer. If you chose to deploy Maximo Asset Management with WebLogic Server. 27. Deploy application files automatically Select this option to have the installation program perform EAR file deployment automatically during the installation. b. In the Choose Shortcut Folder panel. Do not select this option. 194 Installation Guide: . these options are not available from this panel. 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. On the Desktop Select this option to create shortcuts for Maximo Asset Management on the desktop. Choose how to deploy application files.was recorded in the previous attempt. and then click Next. Selecting this option does not create a shortcut in the Quick Launch bar. See the Deployment of Maximo Asset Management with manual configuration of middleware for instructions. In an existing Program Group Select this option and choose the name of an existing program group to store Maximo Asset Management shortcuts. Files can be deployed once all products have added their own functions to the application 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. Note: Shortcuts are created for Windows systems only. In the Quick Launch Bar This option must not be used.

The Post-installation configuration chapter describes the configuration tasks to complete within the product user interface. you must perform several additional tasks after the installation. or outside the Maximo Asset Management installation program by using the taskrunner utility. Post product installation process manager tasks If you have chosen WebLogic Server as your J2EE server. Use the Previous button to return to previous panels to change values. In the Install Complete panel. Deployment of Maximo Asset Management with manual configuration of middleware 195 . The installation task begins. Progress can be monitored by viewing messages displayed above the progress bar.. The chapter also describes how to install process solution packages. 30.Other Select this option and use the Choose. it exits. and then click Install. Chapter 6. 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. button to select another location to create Maximo Asset Management shortcuts. or you have chosen to not automate the configuration of your WebSphere Application Server Network Deployment server during the Maximo Asset Management installation process. Ensure that you have run the configuration step portion of the Maximo Asset Management installation either by performing it during installation. Completing post-installation tasks To complete the deployment. and then click Next. In the Input Summary panel. 29. review the information you have provided to the Maximo Asset Management installation program. or you have chosen to not automate the configuration of your WebSphere Application Server Network Deployment server. click Done. certain package tasks will not be performed and must be completed manually. See the Deployment of optional packages chapter for language pack installation instructions. including process manager products and integration modules. The product installation program invokes the process solution installer and deploys product PSI packages.. In the Pre-Installation Summary panel. 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. What to do next Once the Maximo Asset Management installation program has completed installation and configuration tasks. there are several post-installation tasks that must be performed for product PSI packages. review the installation information presented. Don't create icons Select this option if you do not want any Maximo Asset Management shortcuts created. 28. If you intend to support multiple languages in Maximo Asset Management. If you have chosen WebLogic Server as your J2EE server. install the language pack before performing other configuration tasks.

If using WebSphere Application Server Network Deployment for application server security.bat wasadmin wasadminpwd PMREQUESTER 2.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.zip IBM Tivoli Maximo Common PMP common_pmp_7.1.war Manually configuring PSI packages A process solution package. or PSI package.1. Some of the PSI packages must be configured manually if you have chosen WebLogic Server as your J2EE server.5. “Manually configuring PSI packages” 2..1.1. is a self-contained archive file of installation artifacts and deployment logic that can be deployed using the process solution installation program. 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.5. use the createVMMGroup script to create the PMREQUESTER group. If using application server security. create a new group called PMREQUESTER in your LDAP repository. for example.5.1. If using WebSphere Application Server Network Deployment for application server security.zip package: 1. Use the following syntax with the createVMMGroup script: <MAM_HOME>\jacl\solutions\createVMMGroup. Use the following syntax with the addMemberToVMMGroup script: 196 Installation Guide: .bat <WASAdminUserID> <WASAdminPassword> <VMMGroupName> So. complete the following steps: Procedure Configure the common_pmp_7.1. If using application server security.Post product installation PSI package tasks include the following steps: 1. <MAM_HOME>\jacl\solutions\createVMMGroup. add the user maxadmin to the PMREQUESTER group you created. Add users to a group within LDAP (if using application server security) Deploy WAR files to ISC (WebSphere Application Server Network Deployment only) isccommontasks. use the addMemberToVMMGroup script to add the user maxadmin to the PMREQUESTER group. Post-installation PSI package tasks Create groups within LDAP (if using application server security) base services Package base_services_7. “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.

1. Procedure Configure the base_services_7.5. 2.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. for example. 2.com" "remoteuser" "remoteuserpassword" "<MAM_HOME>\temp\files\isccommontasks. Deployment of Maximo Asset Management with manual configuration of middleware 197 . Extract the isccommontasks.1.ou=users.war" "<Remote WAS Home>" "<WASAdminUserID>" "<WASAdminPassword>" "isccommontasks.zip package: 1.1. <MAM_HOME>\jacl\solutions\ISCHandler.zip file to <MAM_HOME>\temp. <MAM_HOME>\jacl\solutions\ISCHandler. Deploy the file.ou=SWG.<MAM_HOME>\jacl\solutions\addMemberToVMMGroup.o=IBM.war file located in the FILES directory of the <MAM_HOME>\pmp\base_services_7. complete the following steps: Procedure 1. Ensure you are logged into the administrative workstation.o=IBM. Run the following command: <MAM_HOME>\jacl\solutions\Sendfile.bat "myremotemachine.war" "isccommontasks" Deploying the confhelp.bat "<Remote System>" "<Remote Execution and Access User>" "<Remote Execution and Access Password>" "<MAM_HOME>\temp\files\isccommontasks.5.1.ou=groups.war" "isccommontasks" So.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.mydomain.ou=SWG.properties file.war" "/opt/IBM/WebSphere/AppServer" "wasadmin" "wasadminpwd" "isccommontasks.c=US" "cn=PMREQUESTER.bat <WASAdminUserID> <WASAdminPassword> "uid=maxadmin.bat <WASDeploymentManagerHostName> <WASRemoteAccessUserName> Chapter 6.

refer to “Troubleshooting the product installation program” on page 239.<WASRemoteAccesspassword> "<MaximoInstallLocation>\applications\maximohelp \helpweb\webmodule\WEB-INF\confhelp. Examine the CTGInstallTrace00.properties" "<WASInstallLocation>\properties" "confhelp. The following success messages are found in the CTGInstallTrace00.cmd completed successfully Deployment of application MAXIMOHELP was successful runConfigurationStep completed successfully The installation finished successfully 198 Installation Guide: . The product installation program returns a success message if all installation steps.log file.) 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.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. Before you begin The product installation program performs installation verification. you can further verify that the installation completed successfully by locating key artifacts and performing a few simple tasks. For more information about log files and troubleshooting errors encountered during the installation.properties" Verifying the installation After you have exited the Maximo Asset Management installation program without encountering any errors. a HealthCheckFailed error thrown for the getUrlContentString function will be found in the <MAM_HOME>\logs\CTGInstallTraceXX. by logging into the product before exiting the installation. perform the following verification procedures: Procedure 1. are successful.log file for success messages. About this task To further verify that the Maximo Asset Management installation was completed successfully. including the product log in task. or a health check.cmd completed successfully v v v v v CTGIN2224I: CTGIN2253I: CTGIN2224I: CTGIN2208I: CTGIN2370I: Deployment of application MAXIMO was successful buildhelpear. If the health check task is unsuccessful. where XX is a two digit number such as 00.

log file.*completed 2. navigate through the GoTo menu to verify that it has been populated with the applications you expect. Deployment of Maximo Asset Management with manual configuration of middleware 199 . Chapter 6.log file for the following message. Being able to log into the product manually is a good indicator that the installation was successful.*client</symptom> <symptom>CTGIN2230I.*security</symptom> Search the CTGInstallTrace00. which indicates that the maxinst task completed successfully: CTGIN2079I. the following messages. found in the CTGInstallTrace00. Use the solutioninstaller command to list installed packages: <MAM_HOME>\bin\setupPSIenv.bat -action showInstalled -all The resulting list should match the packages listed in the Package Summary panel.*server</symptom> <symptom>CTGIN2238I. You can compare the contents of that panel with a listing of what was actually installed on the system. 3. Compare the packages chosen for installation with the packages that were installed.bat <MAM_HOME>\bin\solutionInstaller. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages that will be installed. indicate the configuration was successful: <symptom>CTGIN2228I. maxinst.*node</symptom> <symptom>CTGIN2232I.If you chose the option of having the installation program automatically configure WebSphere Application Server Network Deployment. Log into the product and verify applications are present.*NodeAgent</symptom> <symptom>CTGIN2240I. Once you have logged in.

200 Installation Guide: .

for Maximo Asset Management users. must be started before you install additional languages. use the Maximo Asset Management language pack installation program before you perform the tasks described in the Post installation configruation tasks chapter. to the Maximo Asset Management user interface The Maximo Asset Management server. other than English. the default base language is English. and install Brazilian Portuguese. and you can also specify additional languages to install. and French as additional languages. other than the base language. Optional deployment of Maximo Asset Management language packages You can install optional language packages to provide support for additional languages. other than English. To minimize installation time. © Copyright IBM Corp. Important: If you plan to add additional languages Maximo Asset Management. After you have successfully installed Maximo Asset Management. so Maximo Asset Management users can browse the user interface and see information in a language that is appropriate for their own locale. The product DVD or installation images include optional language procuess solution packages. Currently. add language support and process solutions as required. in the Maximo Asset Management user interface. Turkish language is not supported. select only the languages that you have a need for at this time. Users in Brazil.. you might specify English as the base language. typically called MXServer on WebSphere Application Server and MAXIMOSERVER on WebLogic Server. 2007 . You can use the language pack installation program to change the base language to something other than English. Spanish.2010 201 . and not in English. If you want to support additional languages. Spain. Complete these installations before you configure the system. and France can have text in the Maximo Asset Management interface displayed in their own languages. you can add support for languages. Before you begin When you run the language pack installation program. For example. Deployment of optional packages After you install Maximo Asset Management before you perform initial configuration tasks. It can take several hours to install additional languages. Installing the language pack This procedure provides task information for installing support for languages. you have an opportunity to select your “base language”. install language packages before you complete the post installation configuration tasks.Chapter 7. 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.

only display in the base language that you select. Login as Administrator on the Maximo Asset Management administrative system. From the Additional language selection panel. complete the following steps: 1. This is the only opportunity you can select a base language. From the Introduction panel. 2. select 0 or more additional languages to be supported. doing so is redundant and simply increases the time needed to install the additional languages. shortcut elements appearing in the Maximo Asset Management interface. and then click OK. 3. From the language selection summary panel. The language pack installation program first uninstalls the base and additional languages installed by the process solution installation wizard from the failed installation attempt. click Next. review the information and then click Next. 9. 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. and you set the locale of your machine to a language that was installed as an additional language. and then click Next. 6. 5. and then click Next. 4.Do not add your base language to the list of additional languages to install . From the Base language Selection panel. You cannot change the base language at a later time. On the launchpad. This problem is a known limitation and does not indicate that the Maximo Asset Management language pack installation failed. Do not specify the base language as an additional language. If you encounter a failure resulting from an inactive Maximo Asset Management middleware server or service. start that server or service. In some cases. 202 Installation Guide: . and perform a reinstall. for example. Select a language for the install. and then rerun the language pack installation program. Even if you added additional languages through the language pack installation program. From the summary panels and click Install. Install Additional Languages. click the Maximo Asset Management Language Pack installer link under 3. 8. This choice is only for use during the installation and its selection will not affect the languages being installed. menu choices. About this task To use the Maximo Asset Management language pack installation program to install the Maximo Asset Management language pack. Ensure that all Maximo Asset Management middleware servers and services are running. select a base language that is to be used for Maximo Asset Management. 7.

accessible from the launchpad. Deployment of optional packages 203 . If the application server is not stopped. Note: Separately deploying a process solution package is only needed if you run the PSI install outside the launchpad. Chapter 7. Process solution packages can be installed and deployed through the process solution installation (PSI) wizard. 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. when you install directly from the product DVD. The process solution installation program ensures that any required login information is specified before continuing with the deployment operation. database. you are running actions that modify the configuration and content of your J2EE. database. Before using the process solution installation program When you perform a deployment operation using the process solution installation program. and adding users and groups for security. Additionally. for instance. and directory middleware servers. Wait 1–2 minutes before starting the process solution installation program. the process solution installation stops and issues a message prompting you to stop the application server. The deployment logic are the actions that are carried out in order to deploy the process solution into the Maximo Asset Management environment. Typically. Ensure the application server (MAXIMOSERVER) is stopped Stop the application server if it is running. and directory servers before you deploy a process solution package using the process solution installation program. The actual middleware servers whose login information is required depend on the process solution package being installed. You must know the administrative user IDs and passwords for the impacted middleware servers. running database scripts that load the process solution content into the Maximo database. optional sample data can be installed. these actions include building and deploying J2EE applications. 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. 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.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. Backup Middleware Servers and Administrative Workstation Create backups for impacted J2EE. Review the following steps before invoking the process solution installation program.

5. The launch script is deployed and configured by the Maximo Asset Management installation program. The process solution installation program performs a series of validation checks to verify that the package you selected is valid. and executing solutionInstallerGUI. 9. In this case.1 package. a package options panel is displayed that details the deployment options that the package supports. A progress panel informs you of the deployment progress of the installation. 6. from the Package Successfully Deployed panel. Launch the process solution installation program by navigating to the <MAM_HOME>\bin directory of your Maximo Asset Management installation. 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. review and verify the information displayed. After the credentials have been verified. 2.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. From the Middleware Login Information panel. If there is a package failure. a message is displayed for the step that failed. the PSI package selected is a base install of the Maximo Asset Management 7. click Done to exit the process solution installation wizard. From the Pre-Install Summary panel. and then click Next. The system is checked to insure that the package has not already been deployed. Select a language for your installation. the process solution installation wizard validates the credentials by connecting to the middleware servers using the supplied credentials. and then click OK. The Process Solution Installation Install Anywhere Installer executes on the Maximo administrative workstation. Click Next to advance. The Process Solution Installation Wizard is actually terminating and no installation activities are being performed. 204 Installation Guide: . 7. From the Package Validation Results panel. 8. No post-installation configuration is required. and then click Next. In some cases. The process solution installation program begins the package installation process. you see an installation progress bar displayed briefly after you click Done. The deployment of the Process Solution Package you were installing has already completed and the progress bar can be safely ignored. 3. Click Next. Once you have entered the requested user IDs and passwords. Read the license information and select I accept the terms in the license agreement if you agree with the terms. The process solution installation program license agreement window is displayed. When the installation has completed successfully. 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. enter the credentials for which you are being prompted. 4.bat. review and verify the information displayed. and then click Next.

PSI utilizes the IBM technology as the means to install and keep track of installed packages.log Chapter 7. the logs would be found under: C:\Program Files\IBM\Common\acsi\ logs\Administrator\ de_msg.err files contain the contents of the Standard Error stream. .err" file. 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. It is normal for one to be blank. logs will have two parts. refer to the log files kept in the following locations: Table 17. a ". . C:\Program Files\IBM\Common\acsi\ logs\<USERNAME>\ de_msg.out files contain the contents of the Standard Output stream as output by the external command. This runtime has its own logging system. if you installed under the user name "Administrator". both with the same pre-extension filename.log C:\Program Files\IBM\Common\acsi\ logs\<USERNAME>\ de_trace. Deployment of optional packages 205 . These log files are typically vital to the proper debugging of package issues. Solution Install/Deployment Engine Logs These are logs kept by the IBM Solution Installer/Deployment engine runtime.Process solution installation logs If you experience any problems or encounter any error messages during the use of the process solution installation program. In general. 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.out" and ".log So for instance.

you would provide the following logs:: C:\IBM\WebSphere\ AppServer\profiles\ AppSrv01\logs\ AboutThisProfile. and other failures experienced by the WebSphere Application Server Network Deployment in its day-to-day running. Location <WAS_HOME>\profiles\ <PROFILE>\logs\ AboutThisProfile.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.txt <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ startServer. Process solution installation logs (continued) Log type Maximo Asset Management Logs Description There are also a few logs kept by Maximo Asset Management.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ SystemErr. These are useful in tracking the progress.log Table 18. Location <MAM_HOME>\maximo\ tools\maximo\log\ updatedb<TIMESTAMP>. and failure of a few back-end commands provided by Maximo Asset Management. and your server name was "server1".log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ SystemOut.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ stopServer. if your WebSphere Application Server Network Deployment was installed in "C:\IBM\WebSphere\ AppServer\". These logs are often helpful in the diagnosis of errors in particular EAR files or other back-end operations. exceptions. WebSphere Application Server Network Deployment logs Log type WebSphere Application Server Network Deployment Logs Description These are logs kept of connections. success. your profile name was "AppSrv01". the logging information would be written to the file: C:\IBM\SMP\maximo\ tools\maximo\log\ updatedb20070419170607. such as database connections.Table 17.log So for instance.txt 206 Installation Guide: .

Table 18. Chapter 7. the exact actions the Thin Client took and the associated responses from the WebSphere Application Server Network Deployment are stored in logs.traceout C:\IBM\SMP\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. If this automated deployment happens to fail. 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.traceout <MAM_HOME>\wasclient\ logs\wsadmin. Deployment of optional packages 207 .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. Location <MAM_HOME>\wasclient\ logs\ CTGIN_wsadmin.traceout C:\IBM\SMP\wasclient\ logs\wsadmin.

208 Installation Guide: .

Chapter 8. Some of these tasks. 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. See “Optional deployment of Maximo Asset Management language packages” on page 201 for more information about the language pack installation. This section also provides information about configuring the WebSphere server. as your business needs dictate. if you have changed security groups Initial data configuration Once you have successfully installed and configured Maximo Asset Management components. If you specified a different name for the default user ID. additional steps are necessary to prepare it for use. use that account name to log on to the application. You need both a valid user name and password to log © Copyright IBM Corp.2010 209 . may have already been performed for you when the product was installed. Before you begin The installation program provides a default user ID (maxadmin) but it does not supply a default password. Post installation steps After you have installed the product. You can create additional IDs and roles. The post installation steps can include the following tasks. 2007 . you must perform the language pack installation before you perform the post-installation tasks. 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. such as configuring SMTP. there are several data configuration tasks you must complete prior to using Maximo Asset Management. you must perform some initial application configuration. If you want to add support for additional languages. Post-installation configuration After you complete the Maximo Asset Management installation.

adminEmail property and set the Global Value attribute to your e-mail address. Click New Row. 210 Installation Guide: . click OK.adminEmail Property Name. 11. About this task To define a currency code for an organization. Procedure 1. Using the Filter feature. Click the Live Refresh icon in the toolbar. User names and passwords are context-sensitive. Click the Live Refresh icon in the toolbar. Specify the default user name. you can use the Maximo Asset Management interface to configure SMTP parameters. Procedure 1. 2. Navigate to Go To → System Configuration → Platform Configuration → System Properties 3. Expand the mail. 6. e-mail notifications of system events. From the Live Refresh dialog. About this task To configure SMTP for Maximo Asset Management. Select the mxe. or other users.host property and set the Global Value attribute to your SMTP host. complete the following steps: 1. log in to the console as maxadmin. 7.com:9081 2. Using the Filter feature. Open a browser session to the IBM Maximo web service interface. and the port number of the application. If you skip these panels when you install Maximo Asset Management. 12. 3. 8. 4. Specify the default password. click OK. search for the mxe. search for the mail.smtp. 10.smtp. Expand the mxe. Configuring SMTP Installation panels provide an opportunity to configure an SMTP server to send an administrator.host Property Name.on. Creating currency codes A currency code must be defined for each organization. Open the Currency Code application for Users by selecting Goto > Financial > Currency Code 2. Click Sign In. For example: http://my_server_example.smtp. Select the mail. 9. 4.host record check box. The default port number is 9081. complete the following steps.adminEmail record check box. 5. Before you begin This task must be completed before you begin the tasks described in “Applying changes to the database” on page 212. You need the hostname or IP address. From the Live Refresh dialog.

2. For example. IT Companies. IT Items. Create an organization About this task You must define at least one organization for Maximo Asset Management. For example. ENGLENA. About this task To create a general ledger account component. 6. Create item and company sets About this task You must define item and company sets for an organization. Enter a site name in the Site field. Post-installation configuration 211 . Click New Row. complete the following steps: 1. 6. for example. Creating a general ledger account component You must create a general ledger account component for Maximo Asset Management. USD. 10. Enter an item set name. Open the Sets application for Users by selecting Goto > Administration > Sets Click New Row. 11. Enter the item set you defined in the Item Set field. For example. Click New Row. 3. complete the following steps: 1. 8. For example. Enter an organization name in the Organization field. IT Items. Enter ITEM in the Type field. 4. 7. Click the New Organization icon in the toolbar. 4. 5. Enter COMPANY in the Type field. For example.3. To define item and company sets. USD. Enter the base currency you defined in the Base Currency 1 field. 3. Enter the company set you defined in the Company Set field. Enter a company set name. 5. B901. for example. Click Save. Click Save. Enter the default item status of PENDING in the Default Item Status field. To define an organization. Click Sites tab. IT Comps. complete the following steps: 1. 4. Open the Database Configuration application by selecting Goto > System Configuration > Platform Configuration > Database Configuration Chapter 8. 7. Open the Organizations application by selecting Goto >Administration >Organizations 2. 9. 8. for example. Enter a currency name. Click Save.

From the Select Action drop-down list. Enter a type for the component. Create a general ledger account About this task You must create a general ledger account for Maximo Asset Management. 5. Applying changes to the database When you create a general ledger account component. Log in to the Maximo console as maxadmin 2. 1234. 5. MYCOMPONENT 5. and then click OK when prompted. ALN.2. select Manage Admin Mode. Failing to turn off Admin Mode within the application causes cron tasks to fail. Open the Chart of Accounts application by selecting Goto > Financials > Chart of Accounts 2. To create a general ledger account. 7. c. For example. 5. click ENGLENA. Procedure 1. Enter a component name in the Component field. For example. to apply the changes to the Maximo database. 6. Click New Row. Select GL Component Maintenance from the Select Action drop-down menu. Click Turn Admin Mode ON. Click Turn Admin Mode OFF. 6. 6. complete the following steps: 1. 3. Enter a numerical length for the component. Select GL Account Configuration from the Select Action drop-down menu. 4. Navigate to Go To → System Configuration → Platform Configuration → Database Configuration. This task takes several minutes to complete. Once Admin Mode has been successfully enabled. 212 Installation Guide: . For example. For example. it must be applied to the Maximo database. About this task To apply configuration changes to the Maximo database. select Apply Configuration Changes. Add a GL Component value and then click OK. On the Select Action drop-down list. a. Every object that must be updated in the Maximo database has a status of To Be Added. 4. Click New Row. b. Turn Admin Mode OFF. Click New Row. Click OK. You can use the Refresh Status button to view progress. Click the name of your organization to select it. 3. Navigate to Go To → System Configuration → Platform Configuration → Database Configuration. To Be Changed should not appear in the status column for objects listed. 4. 3. complete the following steps. select Manage Admin Mode. and then click OK when prompted. For example.

5. Click the GL Components tab. Post-installation configuration 213 . To authorize a Security Group to change a general ledge component type. Click Save. 8. ENGLENA. Click Save Update Company-Related Accounts About this task You must update the company related accounts for Maximo Asset Management. Click OK. 11. To update the company related accounts. 3. Select company type 'C'. Chapter 8. 7. complete the following steps: Procedure 1. AP Suspense Account and AP Control Account to the components you created. 5. From the action dropdown box. select Update Database. Select Active. Open the Security Groups application by selecting Go To → Security → Security Groups. On the dialog click New Row. From the action dropdown box. select Company-Related Accounts. Open the Chart of Accounts application by selecting Go To → Financials → Chart of Accounts. Update General Ledger Component Type Authorization About this task You must update the general ledger component type authorization for Maximo Asset Management. 9. For example. 2. Open the Organizations application by selecting Goto > Administration > Organizations 10. select the General Ledger Account you just created. Set the RBNI Account. Click the Authorized checkbox for each GL Component. 2. Select the Group that will be provided authorization (for example. 4. Click the organization name you created. 12. Select your General Ledger Account. 13. Click OK. 4. 6. From the Clearing Account field. Click Save. SCHEDULING). 8. 3.7. complete the following steps: Procedure 1.

For example. Select PMCFGWO as the Work Order class. Enter the site you created earlier in the Default Insert Site field. To create a default insert site. Select Work Order Options > Work Type from the Select Action drop-down menu. complete the following steps: 1. Enter the site you created earlier in the Storeroom Site for Self Service Requisitions field. Select PMCFGWO as the Work Order class. 5. 9. 2. Search for the organization you created. 8. 3. log out as MAXADMIN and then log back in. for example. 14. If you encounter an error message that indicates that the record is being updated by another user. 6. 214 Installation Guide: . 16. 10. 15. complete the following steps: 1. For example. 11.Create default insert site About this task You must create a default insert site for Maximo Asset Management. Set Complete Status as COMP. Click New Row. Open the Users application by selecting Goto > Security > Users 2. Click OK. Search for maxadmin and then select it to open the record for maxadmin. 7. Open the Organizations application by selecting Goto > Administration > Organizations. 3. B901. 4. B901. 4. Set Complete Status as COMP. 12. 5. Open the WebSphereWebLogic Server Admin Console and restart the MXServerMAXIMOSERVER application server. Create a Work Type About this task You must create a Work Type for Maximo Asset Management. Click New Row. Set Start Status as INPRG. ENGLENA. Click Save. Set Start Status as INPRG. To create a Work Type. Click the name of the organization to open the record for that organization. 13. Set the Work Type as UR. Set the Work Type as AR. Click Save. 6.

and press Enter. 2. Sign out as MAXADMIN. In this case. To configure the synchronization schedule between the directonry server and Maximo Asset Management. and click it. Post-installation configuration 215 . 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. sign out and sign in again in order to see the changes. From the Maximo Asset Management interface. Sign in as MAXADMIN. navigate to Go To → System Configuration → Platform Configuration → Cron Task Setup. 2. Configure the following values: Active? Enable the Active? option by selecting the check box. The manual procedure is required only if you need to change the existing configuration of the cron task. 5. 6. This cron task is set up automatically during installation. 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. For example. even though you have granted the MAXADMIN group permission to create start center templates. 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. 1. the actions are not visible until you sign in again. Credential This should be the password used for the Principal account. Locate the VMMSYNC cron task. complete the following steps: Procedure 1. To synchronize users and groups between a directory server and Maximo Asset Management. Open a Web browser and point to http://host name/maximo.Signing out and signing in About this task When you change a security group that your user ID is a member of. Log in to Maximo Asset Management using the maxadmin user ID. enter the password for wasadmin. GroupMapping This field contains XML mapping files that map LDAP object attributes Chapter 8. Type VMM in the Cron Task field. 4. follow the instructions for the application server in your system. 3.

Filter This is the Virtual Member Manager object class that the service uses to search for group objects in LDAP. 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. cn. UserSearchAttribute This value is the LDAP user object attribute used to search for users under configured directory sub-tree.c=US. Filter PersonAccount This is the Virtual Member Manager object class that the service uses to search for user objects in LDAP. 216 Installation Guide: .vmm.o=IBM.ou=SWG.ou=SWG. Group GroupSearchAttribute This value is the LDAP group object attribute used to search for groups under the configured directory sub-tree. For example.o=IBM. cn.ou=SWG. SynchClass psdi. UserMapping This field contains XML mapping files that map LDAP object attributes to database repository table columns.c=US. SynchAdapter psdi. For example. 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. ou=users.o=IBM.c=US .VMMSynchronizer This value is the Java class that connects to the Virtual Member Manager local service to search for required objects. 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.ou=users. For example. Change the following object entries to use the organizational unit ou value you defined for your organization when setting up Maximo Asset Management middleware. cn=wasadmin.security. ou=groups.vmm. Basedn This defines the LDAP sub-tree under which the Virtual Member Manager Crontask will search for user objects.DefaultVMMSyncAdapter This value is the Java class that writes LDAP data to the database. For example.to database repository table columns.security. For example.

Updating the port for the information center Some of the documentation for Maximo Asset Management is provided in an Eclipse-based information center. for example in a clustered environment. The updated parameters are used at the next scheduled synchronization. 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. If you have Maximo Asset Management installed on several J2EE servers. on a Windows workstation. update the port number. For example. a cron task synchronizes users and groups between an LDAP directory server and the Maximo Asset Management server. Make changes to the Schedule field of the crontask if you want to change the interval. 3. Click the save icon. it might be in C:\Program Files\IBM\WebSphere\AppServer\properties. 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. Chapter 8. the crontask will perform its task every 5 minutes. 2. 9060. 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. It should be in the properties directory of the WebSphere Application Server installation. you must supply the correct port number so that the links to the information center will connect properly. Procedure 1. If you did not choose the default value. and save the file. Edit the file. 7. Locate the confhelp. Post-installation configuration 217 . you must copy the updated file to each J2EE server you add to the cluster. Results By default.You must click the arrow located in the header of the Cron Task Parameters table to view all parameters. 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.properties file on your J2EE server. Manually configuring directory services for Oracle WebLogic Server When you use Oracle WebLogic Server as the application 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.

Tuning DB2 This section details how to tune DB2 after you have completed installation.cmd [ dbName [ dbInstance ] ] Linux and UNIX OS db2tuning. The use of these scripts is strictly optional and contain configuation parameters that might not be ideal for all environments. it will default to MAXDB71. you should make a backup copy of the original script. and must be run by a user with database administration authority. Windows db2tuning.sh [ dbName [ dbInstance ] ] If the dbName is not provided. you can modify these scripts to suit your particular configuration and workload. 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. However. 218 Installation Guide: .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. Before modifying these scripts. About this task Maximo Asset Management provides scripts that can be used to tune DB2.

HP-UX. you can use the following command from the command line to start the domain manager: <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. Start the Deployment Manager: Linux.ctgCellManager01. Solaris.sh webserver1 -username <username> -pas <WAS_HOME>profiles\ctgAppSrv01\bin\startServer.com/infocenter/wasinfo/v6r1/index. consult the product information at ??? WebSphere Application Server configuration IBM provides comprehensive information on running and administering WebSphere at this URL: http://publib. the dbName must also be provided. AIX <WAS_HOME>/AppServer/profiles/ctgDmgr01/bin/startManager. c. and click Start the service. Solaris.bat webserver1 -username <username> -pas <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer. HP-UX. complete the following steps: 1. b. To start the MXServer application .bat MXServer -username <username> -pass Chapter 8. Start the App Server : Linux. Solaris.jsp Starting the WebSphere Application Server About this task An application server named MXServer was created during installation. For detailed information about using WebSphere. Solaris. Select IBMWAS61Service . and select Run.boulder. AIX Windows 4. Alternatively. Type services.sh MXServer -username <username> -passw <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.ibm. Start the Node: Linux. HP-UX.sh Windows a. Click Start. WebSphere configuration This section describes how to configure WebSphere to work with Maximo Asset Management.bat 2. Post-installation configuration 219 . Start the web server: Linux. AIX <WAS_HOME>r/profiles/ctgAppSrv01/bin/startNode. AIX Windows <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.msc.If the dbInstance is not provided it will default to ctginst1. and click OK.bat 3. HP-UX. If a database instance other than the default is needed.sh Windows <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.

4. AIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode. the name of the WebSphere Application Server. Before you start the Administrative console. click Stop. Click Start.sh 220 Installation Guide: . HP-UX. click Servers → Application Servers. 3. From the administrative console navigation pane.Alternatively you can start MXServer from the WebSphere Application Server administrative console: 1.sh <WAS_HOME>/profiles/ctgDmgr01/bin/stopManager. if one is required. Select the check box next to MXServer.bat Linux. Solaris.sh <WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode. Solaris. AIX <HTTP_SERVER_HOME>/bin/apachectl start <HTTP_SERVER_HOME>/bin/apachectl stop Deployment Manager Windows <WAS_HOME> \profiles\ctgDmgr01\bin\startManager. Where <machine_name> is the host name of the WebSphere Application Server and 9060 is the default port number for the Administrative Console. open a browser window and enter the following URL: http://<machine_name>:9060/ibm/console 2.bat <WAS_HOME> \profiles\ctgDmgr01\bin\stopManager.sh Node Agent Windows <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode. Enter an administrative user ID and password to login. Solaris. AIX <WAS_HOME>/profiles/ctgDmgr01/bin/startManager. Server processes Server HTTP Server Go To Windows <HTTP_SERVER_HOME>\bin\apache -k start <HTTP_SERVER_HOME>\bin\apache -k stop Linux. verify that these server processes are running. Notice that the icon in the Status column changes to running To stop the WebSphere Application Server. Table 19. To start the administrative console. HP-UX. 5. HP-UX.bat Linux. 6. Notice that the icon in the Status column changes to stopped.bat <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode.

Type services.DB2COPY1 . Enter the WebSphere Application Server administrator user ID and password to login. Simply click Chapter 8.msc. . After enabling security. and click OK. HP-UX. Click Start. Click Start. Linux. Open a browser window.idsccmdb. 3.1 . 2. 2. The roles determine the administrative actions that a user can perform. First you identify users (or groups) that are defined in the active user registry. and select Run. you perform several steps to secure the console. Type services.idsccmdb -c db2start To start the Administrative Console. Select IBM Tivoli Directory Server Instance V6. and click Start the service.msc. you can determine their level of access by assigning roles. Once you have enabled VMM for WebSphere Application Server Network Deployment security. Post-installation configuration 221 . You can use the Administrative Group Roles page to give groups specific authority to administer application servers through the administrative console. 3. AIX /ldap/V6. complete the following steps: 1. After you decide which users you want to access the console. VMM must have been configured on the WebSphere Application Server Network Deployment server before securing the console. Linux. Solaris. Select DB2 . 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. and select Run. and click OK. 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. Server processes (continued) Server ITDS Instance Go To Windows 1. AIX su . HP-UX.Table 19. 2. Solaris. and click Start the service. a user must enter a valid administrator user ID and password to access the console.CTGINST1-0.1/sbin/ibmslapd -I idsccmdb Directory Server Database Windows 1.

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. 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. Administrative group roles Admin Role Administrator Operator Configurator Monitor deployer adminsecuritymanager Description Has operator permissions. Select the role and click either Look up users or Look up groups Different roles can have different security authorizations. This role primarily confines the user to viewing the application server configuration and current state. applications. click Security role to user/group mapping. complete the following steps: 1. For example. you can assign users and groups to the adminsecuritymanager role on the cell level through wsadmin scripts and the administrative console. you can assign users and groups to the administrative user roles and administrative group roles. Has administrator privileges for managing users and groups from within the administrative console only. 3. However. an administrator cannot assign users and groups to the administrative user roles and administrative group roles including the adminsecuritymanager role. However. configurator permissions. Fine-grained administrative security is available using wsadmin only. iscadmins Note: To manage users and groups. Table 20. the operator can start or stop services. Select Applications → Enterprise applications → application_name.Security → Secure administration. click Users and Groups in the console navigation tree and then click either Manage Users or Manage Groups. and infrastructure → Administrative Group Roles to view the available administrative group roles. Has monitor permissions and can change the run-time state. Click >> to add users from the Available list to the Selected list. Has the least permissions. Mapping users or groups to a role authorizes those users or groups to access applications defined by the role. Users granted this role can perform both configuration actions and runtime operations on applications. Restart all the application servers. Start the WebSphere Administrative Console by opening a browser window and entering the following URL 222 Installation Guide: . 2. Under Detail properties. Complete the following steps to map users and groups to security roles: 1. Using the adminsecuritymanager role. and the permission that is required to access sensitive data. Has monitor permissions and can change the application server configuration. 4.

C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 wasHome Home folder for MXServer. 7. Enter an administrative user ID and password. for example.log restart Restarts the existing service automatically if the service fails when set to true. Post-installation configuration 223 . and you will see a confirmation message. Then perform the following actions: a. c. For example: C:\IBM\WebSphere\AppServer\bin 8. 5. C:\IBM\WebSphere\AppServer logRoot Folder location of MXServer log file. 9. Change the Startup type field value to Automatic. Open a command prompt window. for example. Chapter 8. 6. Select MXServer. Click Start to start the service. C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\ logs\MXServer logFile Log file name for MXServer. In the Application Servers pane. Click OK. C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs \MXServer\startServer. for example. 3. Navigate to the bin folder where you installed the Maximo application server. Open a Services window and double-click MXServer. 4. and click Stop. 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. Click Servers → Application Servers in the navigation pane. profilePath The profile directory of the server. MXServer.log" -restart true 10. Run the WASService command with the following parameters: serverName Name of Maximo application server. select MXServer and click Start. b. This action creates a server log folder used by the WASService command. for example.http://<machine_name>:9060/ibm/console 2. Press <Enter> after you type the WASService command. 11.

for example. Navigate to the bin folder where you installed the Node Agent. 3. select the name of the Node Agent (for example. profilePath The profile directory of the server. nodeagent). and you will see a confirmation message. 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. Enter an administrative user ID and password. and click Stop. 224 Installation Guide: . 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 true 10. Click System Administration in the navigation pane. It performs administrative functions. Press <Enter> after you type the WASService command. C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 wasHome Home folder for MXServer.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. nodeAgent. complete the following steps: 1. select nodeagent in the Administration pane. Run the WASService command with the following parameters: serverName Name of node agent. 7. Open a command prompt window.1 Administrative Console by opening a browser window and entering the following URL: http://<machine_name>:9060/ibm/console 2. C:\IBM\WebSphere\AppServer logRoot Folder location of node agent log file. For example: C:\IBM\WebSphere\AppServer\bin 8. for example. 6. for example. 9. and click Start. In the System Administration pane. Start the WebSphere 6. 5. Before you run the WASService command. To configure the WebSphere node agent to run as a Windows service. 4.log restart Restarts the existing service automatically if the service fails when set to true.

b. nodeAgent. Open a Services window and double-click the Node Agent service. Then perform the following actions: a. Change the Startup type field value to Automatic. Click Start to start the service. for example. Click OK. Chapter 8. Post-installation configuration 225 .11. c.

226 Installation Guide: .

54]\logs 2.req. 2007 . In order to troubleshoot this error. you might encounter error CTGIN9042E which occurs during the install step for WebSphere Application Server Network Deployment 6.id is created as a date_timestamp.2010 WAS-ND_AIXppc64_Custom_v61023.tar. review the troubleshooting information for answers to common problems.1. if the workspace is located at: C:\ibm\tivoli\workspace.log file can be found at: <workspace>\<machine name>\deploymentPlan\MachinePlan_<machine shortname> \00009_WAS_ND_6. for example. complete the following steps: Procedure 1.id>]/logs/ de_processreq. First check de_processreq. and the processing. Troubleshooting If you encounter issues using the product or middleware installation programs. it might be related to stale entries in the CEI registry. check for any stale WebSphere Application Server Network Deployment entries: a.1\install\01_BASE\ [INSTALL_1130_06.Chapter 9. The de_processreq. the machine name is mymachine.log So.1\install\01_BASE/[INSTALL_<processing.log would be located in: C:\ibm\tivoli\mwi\workspace\mymachine.tar.ibm. Extract the native image of WebSphere Application Server Network Deployment: Windows WAS-ND_WindowsIA32_Custom_v61023 Linux WAS-ND_LinuxIA32_Custom_v61023. Before you begin Maximo Asset Management About this task If you encounter error CTGIN9042E through the normal use of the middleware installation program. then the de_processreq.gz AIX © Copyright IBM Corp. Troubleshooting the middleware installer Use the information contained in this section to troubleshoot errors encountered when using the middleware installer. Next.com\deploymentPlan\ MachinePlan_mymachine\00009_WAS_ND_6. 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.gz 227 .req.log for failures related to VerifyLogsInInstallLogs Action.

3. remove any WebSphere Application Server Network Deployment entries.bat -listProducts Linux installRegistryUtils. and then save the file. ACUINI0044E Failed to register and start Deployment Engine IBM ADE Service In order to troubleshoot this error. c. List registry entries: Windows installRegistryUtils. run the middleware installation program again and Restart the plan. Clean WebSphere Application Server Network Deployment entries from the registry: installRegistryUtils -cleanProduct -offeringID ND -installLocation <WAS installation location path> b. Please try to manually start the Deployment Engine and restart the installer.sh -listProducts e. Before you begin About this task If you encounter error ACUINI0044E through the normal use of the middleware installation program. even if you have successfully uninstalled WebSphere Application Server Network Deployment. 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. WebSphere Application Server Network Deployment will now be successfully installed in the default location. Edit the vpd. complete the following steps: 228 Installation Guide: . If any WebSphere Application Server Network Deployment entries are listed. you might encounter error ACUINI0044E which occurs during the install step for the deployment engine. Open the console window. Check for WebSphere Application Server Network Deployment related entries. Navigate to the bin folder of extracted image.properties file. Encountering error ACUINI0044E During middleware installation using the middleware installer. it might be related to a failure of the deployment engine to be installed or started. for example. you will need to clean the registry entry.sh -listProducts AIX installRegistryUtils. C:\Program Files\IBM\WebSphere\AppServer for Windows. The following messages will be displayed after a failure to deploy the deployment engine is encountered: Deployment Engine did not start successfully. For example: \WAS\installRegistryUtils\bin d. Clean the registry entries: a. After cleaning the registry.b.

2.ap.log file for an error similar to the following: <errorMessages> <errorMessage>[com.common.id>]/logs/ db2_91_inst.ibm. it might be related to the fact that there is an existing user named db2admin on the system.txt]. Incorrect db2admin password If you encounter error CTGIN9042E Errors were encountered during the execution of the step DB2 Enterprise Server Edition Version 9. The db2_91_inst.hosts. for example. /l. through the normal use of the middleware installation program.32]\ logs Check the de_processreq.32]/ Decrypted_ResponseFile.sh -start AIX /usr/ibm/common/acsi/bin/acsisrv.1. Check the db2_91_inst.ac. /f.hosts.sh -start If the deployment engine is started successfully.log file is located at: <Workspace>\<machine name>\ deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9.ExternalCommandActionException: ACUOSI0050E External command action failed with return code 87.req. Troubleshooting 229 .CreationFailedException: : ]</errorMessage> <errorMessage>[com.id is created as a date_timestamp.log So. you will have to manually uninstall the deployment engine as described in “Common deployment failures” on page 243.32]/db2_91_inst. and the processing.exe. If the deployment engine fails to start.ibm. if the workspace is located at: C:\ibm\tivoli\workspace.ibm.common. Restart the deployment engine using the following commands: Windows net start "IBM ADE Service" Linux /usr/ibm/common/acsi/bin/acsisrv.Procedure 1. Note that this will also eliminate the deployment engine registry information for other products installed on the system. Enter a valid password.ac.req. then the db2_91_inst.1\install\ 01_BASE\[INSTALL_<processing.CreationFailedException: : ] </errorMessage> </errorMessages> <actionErrorEvents> <actionErrorEvent actionID="InstallProduct" actionName="externalCommand"> ACUCME1100E </actionErrorEvent> </actionErrorEvents> Chapter 9. Invocation string: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1/DB2-ESE_9.log file for an error similar to the following: ERROR:The password specified is invalid. so use caution when uninstalling the deployment engine.4.com\deploymentPlan\ MachinePlan_mymachine\00004_DB2_9.log. but with a different password than the one entered in the middleware installation program. /u. C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09.1. com.action.1\install\01_BASE\[INSTALL_0424_09. the machine name is mymachine.si.0/ESE/setup.log file would be located in:C:\ibm\tivoli\mwi\workspace\mymachine.ibm. Exit the middleware installation program.ac. C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\[INSTALL_0424_09. restart the middleware installation program and resume middleware deployment.

click Deploy to start the install.1\install\01_BASE\[INSTALL_0424_09. Navigate to the directory containing the middleware installation program DVD image and restart the middleware installation program.1\install\ 01_BASE\[INSTALL_<processing. Expand Local Users and Groups and then select Users d.32]\ logs These errors indicate that the existing system user db2admin has different password than the one entered in the middleware installation program. confirm it. follow these steps a.id is created as a date_timestamp. complete the following steps: 1. 2. Right-click the db2admin user and then click Set password. After install completes click Finish to exit the wizard. c. you encounter the error message CTGIN9042E. Click OK once again. for example. 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. and then click OK f. then the de_processreq. b. Right click the My Computer icon and select Manage. Specify the directory for the middleware install images and click Next. After disk space checks are completed. 230 Installation Guide: . 4. 8.log file is located at:<Workspace>\<machine name>\deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9. From the Computer Management console. Select Restart the Plan and click Next. click Finish to exit out of the of the middleware installation program install wizard. Enter the password. For Linux and AIX.log file would be located in: C:\ibm\tivoli\mwi\workspace\mymachine. 7. the machine name is mymachine. To set the password for Windows. 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.The de_processreq.com\deploymentPlan\ MachinePlan_mymachine\00004_DB2_9.log So. 6. and the processing.req. select Local Users and Groups in System Tools. v You can delete the user db2admin and restart the middleware installation program . To resolve this issue. v You can set or change the password for existing DB2 user db2admin.ibm. e. which relates to a failure to properly configure DB2 or IBM Tivoli Directory Server.req. if the workspace is located at: C:\ibm\tivoli\workspace. Specify the temporary directory and click Next. If you have not done so.id>]/logs/ de_processreq. Improper configuration of DB2 or IBM Tivoli Directory Server While running the middleware installation program on an AIX system. 5.

Proceed through the panels to complete the uninstall and click Finish to exit the installer.log file located within the workspace directory (for example:/ibm/tivoli/mwi/workspace). you can create your own copies of these files. 7. Select Undeploy the Plan.wss?uid=swg21304976. Download to your local system the mwi_db2instance.sh and add the following content: #!/bin/ksh port1=0 var1=3 if [ -f /etc/services ] then if [ $# -eq 0 ] Chapter 9. Create a text file named mwi_db2instance. Select Partial uninstall. and then click Next. Finally. you should check the following log files to determine the precise cause of the error: Check the mwi.id>]/ logs/createinstance. check the startInstanceTool. 6.log file at <workspace>/<machine name>/deploymentPlan/MachinePlan_<machine shortname>/ 00008_ITDS_Configuration/install/02_CONFIG/[INSTALL_<processing. 2. 4. Alternatively.log file at <workspace>/<machine name>/deploymentPlan/MachinePlan_<machine shortname>/ 00005_DB2_Configuration/install/02_CONFIG/[INSTALL_<processing.xml:173: Failed to create database instance ctginsxy. Select only the Configuration for DB2 Enterprise Server Edition option.req. Click Finish to exit out of the middleware installation program install wizard.xml:173: Failed to create itds database instance itdsccmxy. 5.sh files attached to the technote located at http://www.id>]/ logs/startInstanceTool. and then click Next.If you encounter error CTGIN9042E through the normal use of the middleware installation program on an AIX machine.sh and mwi_itdsinstance.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.com/support/docview. To resolve this issue. 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.req. Troubleshooting 231 .ibm. a. and then click Next. Also check the createinstance. 3.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. Restart the middleware installation program and proceed through the wizard until you reach the Restart or Undeploy the Plan panel. complete the following steps: 1.

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

/mwi_itdsinstance.ibm. Troubleshooting 233 .ibm.log would be located in: /ibm/tivoli/mwi/workspace/mymachine. if the workspace is located at: C:\ibm\tivoli\workspace.ibm. 2. Chapter 9.com\deploymentPlan\MachinePlan_mymachine\ 00008_ITDS_Configuration\install\02_CONFIG\logs Linux In Linux.log file would be located in: C:\ibm\tivoli\mwi\workspace\ mymachine. if the workspace is located at: /ibm/tivoli/mwi/workspace. 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 set or change the password for existing IBM Tivoli Directory Server user idsccmdb .sh and pass values for the instance name and the port number in the following order as shown below: . the machine name is mymachine. if the workspace is located at: /root/ibm/tivoli/mwi/workspace. then the configureDB. 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. the machine name is mymachine. The configureDB.parameters. it might be related to the fact that there is an existing user named idsccmdb on the system.log file is located at: <Workspace>\<machine name>\ deploymentPlan\MachinePlan_<machine shortname>\00008_ITDS_Configuration\ install\02_CONFIG\logs\configureDB.ibm.log file for an error similar to the following: GLPCDB018E The DB2 administrator ID or password you specified is not valid.ibm. This would indicate that the existing IBM Tivoli Directory Server user idsccmdb has different password in the system .com/ deploymentPlan/MachinePlan_mymachine.log would be located in: /root/ibm/tivoli/mwi/workspace/mymachine. If you want to use custom values run mwi_itdsinstance. v You can delete the user idsccmdb and restart the middleware installation program .com/ 00008_ITDS_Configuration/install/02_CONFIG/logs AIX In AIX. for example in Windows. complete the following steps: 1. Incorrect idsccmdb user password If you encounter error CTGIN9042E through the normal use of the middleware installation program. but with a different password than the one entered in the middleware installation program.com/deploymentPlan/ MachinePlan_mymachine.sh itdsccmxy 60007 where itdsccmxy and 60007 are the values entered in middleware installation program IBM Tivoli Directory Server DB2 instance Configuration Panel. click Finish to exit out of the of the middleware installation program install wizard. then the configureDB. If you have not done so.com/00008_ITDS_Configuration/install/ 02_CONFIG/logs To resolve this issue.log Windows So. then the configureDB. the machine name is mymachine.

This message is shown when the cited service pack level is incorrect. 4. c. When you encounter error CTGIN9061E. For example: "CTGIN9042E: Errors were 234 Installation Guide: . where <step_name> can be any of a number of middleware installation steps. Incorrect service pack requirement for AIX When running the middleware installation program on AIX platforms. Run the following command at terminal: # passwd idsccmdb c. 3. After install completes click Finish to exit the wizard. Enter the new password and confirm it. OS Technology Level should be 06 or greater and SP level 02 or greater. After install completes click Finish to exit the wizard. From the Computer Management console. 5. 7. Specify the directory for the middleware install images and click Next. 11. select Local Users and Groups in System Tools. Right-click on the idsccmdb user and then click the set password menu item. Failure when system directories cannot be renamed During middleware installation you encounter CTGIN9042E during the execution of a number of installation steps. 10. Select Configuration for IBM Tivoli Directory Server and click Next. Select Restart the Plan and click Next. After disk space checks are completed. Navigate to the directory containing the middleware installation program DVD image and restart the middleware installation program. 9. b. Click Undeploy to start the uninstall. Log in as root and open command prompt. Select Partial Uninstall and click Next. confirm it. 8.To set the password we have to follow the below steps Windows a. Right click on My Computer icon and click Manage menu item. Navigate to the directory containing the middleware installation program DVD image and restart the middleware installation program. Expand Local Users and Groups and then select Users d. 13. you might encounter the following message: CTGIN9061E: Unsupported Technology Level. Enter the password. note that while the error message indicates SP level 02 or greater is a prerequisite. b. Select Undeploy the Plan and click Next. SP level 01 or greater is the actual middleware installation program prerequisite. click Deploy to start the install. e. 14. If you encounter error message: “CTGIN9042E: Errors were encountered during the execution of step <step_name>”. 12. This can occur during the execution of any of the middleware steps where renaming of the product install directories has failed. 6. Linux AND AIX a. Specify the temporary directory and click Next. Click OK once again. and then click OK f.

1. This renaming of existing directories can fail in certain situations.log_utf8 for the following error text: <errorMessage>[com.1/install/ 01_BASE/[INSTALL_1215_04.1_<date_time_stamp>. Check the location and the logs indicated by the error message from step #1: Check de_processreq. if you are installing to /opt/IBM/db2/V9. 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.595 : Failed: Deployment Step: step_00004_DB2_9.log_utf8 at /ibm/tivoli/mwi/workspace/<host name>/deploymentPlan/MachinePlan_<host name>/00004_DB2_9. the middleware installer will attempt to rename it to /opt/IBM/db2/ V9.ibm. and <Machine_name> is the host name of the machine on which you are installing.00 ]/logs/de_processreq.1. 2.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/install/01_BASE/ [INSTALL_1215_04.1" Also check the DeploymentPlan.action.1/common/Utils.00 ]/logs/de_processreq.si.00]/logs. if it has been previously created as a filesystem (instead of a directory within a defined filesystem) 2. Troubleshooting 235 . Check the DeploymentPlan.log This log file is located at /ibm/tivoli/mwi/workspace/<Machine_name>/ deploymentPlan/logs/[INSTALL_<date_time_stamp>]/DeploymentPlan.log.err For example. where /ibm/tivoli/mwi/workspace is the default middleware workspace or the path you specified on the installer workspace panel.log at /ibm/tivoli/mwi/workspace/<host name>/ deploymentPlan/MachinePlan_<host name>/00004_DB2_9.log_utf8 Check de_trace. and this directory already exists from a previous installation or it has been previously created.4".1/install/ 01_BASE/[INSTALL_1215_04. Check the de_processReq output file at /ibm/tivoli/mwi/works pace/<host name>/deploymentPlan/MachinePlan_<host name>/00004_DB2_9.ExternalCommandActionException: ACUOSI0050E External command action failed with return code 1.x ml:544: Deployment Engine command de_processReq reported an error. Chapter 9.ac. For example: 1.com The failed step in this case is "step_00004_DB2_9.ap.1 2008-12-15 04:07:44.mydomain. the middleware installer attempts to save any existing product install directories by renaming them.595 : Machine Plan: MachinePlan_mymachine. For example. For example: 2008-12-15 04:07:44.encountered during the execution of step DB2 Enterprise Server Edition Version 9. check for the existence of the following error file that might contain additional information: <Product_Name>_RenameExistingInstallLocation_Unix_<Date_Time_stamp>. <actionErrorEvent actionID=RenameExistingInstallLocation_Unix actionName="externalCommand">ACUCME1100E</actionErrorEvent> If this error is found in de_processreq. Prior to installing the specific middleware product.log_utf8. Locate the step name that has failed.

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.com\deploymentPlan\MachinePlan_mymachine\00009_WAS_ND_6. If this is a filesystem or directory with Read Only access.req.1 configuration or authentication service configuration steps. run the middleware installer again to deploy the plan.1\ install\01_BASE\[INSTALL_1130_06. log files would be located in:C:\ibm\tivoli\mwi\workspace\ mymachine. the machine name is mymachine.req. if the workspace is located at: C:\ibm\tivoli\workspace. To resolve the problem: a.id>]/logs So. give write permission for the user or owner of the filesystem (directory) and the user performing the installation.req. 4) Deploy the plan b.00.1\install\01_CONFIG\ [INSTALL_<processing. 2) Restart the middleware installer and select Edit the configuration parameters. If this is a filesystem.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. it might be caused by a SOAP connector performance issue. In this case /db2 is the name of the existing filesystem or directory and /db2_20081215_040712GMT-05.err . To resolve this issue when you encounter it. 3) Specify a directory (for example.00 is the new name the middleware installer is using for the mv command to rename the filesystem or directory. 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. complete the following steps: 236 Installation Guide: .54]\logs Also check log files for the following error: Unable to connect to the process dmgr on node ctgCellManager01 using SOAP connector.1) within the filesystem for the install location of the product that previously failed. Then. 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.ibm. /db2/V9.00: The requested resource is busy. for example. This error occurs during the execution of the WebSphere Application Server ND 6.DB2_Enterprise_Server_Edition_RenameExistingInstallLocation_ Unix_20081215_040712GMT-05. and the processing.id is created as a date_timestamp. Choose Complete Uninstall and click Undeploy. rerun the installer and specify a new directory within the filesystem: 1) Restart the middleware installer. and select Undeploy the plan.

The db2_91_inst.req.ibm. Proceed through the wizard until you reach the panel that gives you the choices of Restart the Plan or Undeploy the Plan.TXT" is not valid. Invocation string: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1/DB2-ESE_9.si. then the db2_91_inst.ac. Open a system prompt and launch the Tivoli middleware installation program again from within the cd_image directory using the RMI option.ibm.exe.0/ ESE/setup.log. Restart the Tivoli middleware installation program. /u.hosts.ap. 1: ERROR:The response file specified "C:\WINNT\TEMP\2\_INSTA~1.id is created as a date_timestamp. 4.log file for an error similar to the following: <errorMessages> <errorMessage>[com. for example.ibm.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. Click Undeploy.common.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\install\ 01_BASE\[INSTALL_<processing.txt]. 8.1. 3.ac.log would be located in:C:\ibm\tivoli\mwi\ workspace\mymachine.log So. Check the db2_91_inst.CreationFailedException: : ]</errorMessage> <errorMessage>[com. Manually delete the workspace folder (for example C:\ibm\tivoli\mwi\ workspace). and the processing. Select Undeploy the Plan and click Next.req.CreationFailedException: : ] </errorMessage> Chapter 9. 6. com. C:\DOCUME~1\ADMINI~1\LOCALS~1\ Temp\1\[INSTALL_0424_09. click Finish to exit the Tivoli middleware installation program installation program. Troubleshooting 237 .32]\logs.32]/Decrypted_ResponseFile. 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. the machine name is mymachine. Also check the de_processreq.id>]/logs/ db2_91_inst. 7. Once the uninstall is complete.32]/db2_91_inst.18_/DECRYP~1.exe -V USE_RMI_FOR_IPV6=yes These steps will resolve the SOAP connection problem with the process deployment manager.com\deploymentPlan\MachinePlan_mymachine\ 00004_DB2_9. /f.common. if the workspace is located at: C:\ibm\tivoli\workspace.ExternalCommandActionException: ACUOSI0050E External command action failed with return code 87.1.action. /l. Click Finish to exit out of the Tivoli middleware installation program. C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\ [INSTALL_0424_09.hosts. 2.ac. mwi. 5.1\install\01_BASE\[INSTALL_0424_09.log file is located at: <Workspace>\<machine name>\ deploymentPlan\MachinePlan_<machine shortname>\00004_DB2_9.ibm.

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

you must exit the installation program. Taskrunner data stores are not persisted.properties The install. the License directory must also be copied. do not reboot your system. Common deployment failures Refer to this section for general troubleshooting information about common deployment failures. 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. If you experience an error after the configuration step. Troubleshooting 243 . examine the trace.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.bat CONTINUE STOPONERROR Note: If you reboot the system. If you intend to use the taskrunner utility. 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 run taskrunner with the NOSTOPONERROR parameter. the taskrunner will continue despite errors. it might be caused by obsolete property values. 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. resolve the issue. 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. and then complete the installation using the taskrunner utility by invoking it from the command line: C:\IBM\SMP\scripts\taskRunner. and then proceed through the rest of the install wizard.install. The taskrunner utility will resume the installation at the point where the last successfully completed task was recorded in the previous attempt. License files License files are located on the media and are not packaged with the installation executable. resolve the issue. investigate the trace logs. If you copy the installation program from the product media to the file system. Chapter 9. the next installation action will fetch the outdated value from the property file and a failure will occur. and Maximo logs. you will not be able to use the taskrunner utility to run configuration scripts. If you experience errors related to an inability to connect or authenticate to middleware servers during an upgrade or fix pack installation. If you experience this sort of error. solution install.

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. If you plan to install the product on a drive other than the one hosting Windows. you must enable a remote access protocol for each system hosting a middleware server. Port 139 is used for TCP NetBIOS connections.com/) and use the issue search facility to locate the article on how to manage remote access to the registry. Remote access to the registry is determined by the HKLM\System\CurrentControlSet\Control\ SecurePipeServers\winreg registry key entry. you should not start the installer from Windows Explorer. 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.microsoft. For example. Visit the Microsoft help and support web site (http://support. 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.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. Connection exceptions Remote access connection exceptions typically manifest themselves as 244 Installation Guide: . This behavior occurs when invoking the installer directly or though the product launchpad. So. if your installer was located on the d: drive the command might look like the following: g:\> d:\temp\install. If that is the target drive of the product install you can start the installer or launchpad from Windows Explorer.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. start the installer or launchpad application from the drive where you will install the product. the installation will fail. To resolve this problem. open a command prompt and switch to the g: drive prior to invoking the installer. Messages with the prefix CTGRI found in the CTGInstallTrace. Refer to “Remote configuration enablement” on page 37 for more information. Ensure the following ports are accessible on servers that will be hosting middleware: 445 139 Port 445 is used for SMB over TCP. 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. Invoke the installer from the command line as described earlier. if you want to install the product on the g: drive.

Troubleshooting 245 .getOSType (CmnInstallAnywhereUtils.actions.ear or maximohelp. This error typically looks similar to the following example: RemoteSystem can't be reached using Supported RXA protocols. RemoteAccessAuthException: CTGRI0000E Could not establish a connection to the target machine with the authorization credentials that were provided.tivoli..install (FndWasRemoteActions.RxaHost. and Trace.ear file..log file and also the SystemOut.util.ccmdb.ibm.log file to determine the cause of the connection exception. you can continue to use the Maximo Asset Management installation program.either an authorization failure or as a host connection failure.init(RxaHost. Search the CTGInstallTrace.CmnInstallAnywhereUtils. the WebSphere Application Server Network Deployment may be unable to service requests to deploy the maximo or maximohelp applications and will display a SOAPException.java:303) at com.RxaHost.<init>(RxaHost. Under certain conditions. The following CTGInstallTrace00.installSelf(DashoA10*.tivoli. Once you have resolved these errors.BaseProtocol.install.zerog.remoteaccess.remoteaccess. at com. java:78) at com. including the CTGInstallTrace00.ear and maximohelp.log. Refer to the troubleshooting section of the information center for more information regarding log files generated by middleware.ibm. Application server SOAP errors Details for errors resulting from the failure to deploy the maximo. ----.install.tivoli. or inadequate space on the WebSphere Application Server Network Deployment server to either transfer or deploy the maximo.ibm. Errors for this type of exception typically look similar to the following example: SEVERE: EXIT ^RxaConnectFailure:^o^{{com.START OF LOG FILE INFORMATION Exception caught during installation of Chapter 9.installer.rxa.appsvr. An authorization error is triggered by an incorrect user ID or password value supplied to the Maximo Asset Management installation program.log files hosted on the WebSphere Application Server Network Deployment deployment manager.ia.install.CustomAction.common.) 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.log log information is an example of the error information that is displayed when such an exception is encountered.ibm.ccmdb.java:237) at com.install. Typical EAR file deployment failures can include SOAP connection errors where the SOAP port (8879) is not available.ear from the administrative system to the WebSphere Application Server Network Deployment.rxa.util.ia.foundation. java:130) at com.tivoli.log.ccmdb.ibm.ccmdb.common. You might encounter a SOAPException error during deployment of the maximo.) at ZeroGab8.common.ibm.beginSession(BaseProtocol. java:522) at com. SystemError.FndWasRemoteActions.ear files can be found in several places.tivoli.run(DashoA10*.tivoli.

<MAMInstallLocation>\jacl\solutions\DeployApplication.ear.net.bat script follows. Review JVM logs in WebSphere.exception. for example: C:\IBM\SMP\jacl\solutions\DeployApplication. This health check consists of logging into the application.ConnectorException org.ibm.ScriptingException: com.ws.IllegalArgumentException: Error opening socket: java.bat <WASAdminUserName> <WASAdminPassword> <ApplicationName> Either MAXIMO or MAXIMOHELP <WASNodeName> <WASApplicationServerName> <path-to-EAR-file> <WASVirtualHost> <WASWebServerName> So.exception.management.websphere. the filepath of the EAR file is C:/IBM/SMP/maximo/deployment/default/maximo. The syntax for the deployApplication. 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 able to successfully log in. The file names of the log files will include the words Deploy and EAR as part of the filename. Syntax elements in brackets <> need to be replaced with the values for those properties in your environment. 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.SocketException: Operation timed out: connect:could be due to invalid address. review the WebSphere Application Server Network Deployment log files to determine the nature of the failure.C:/IBM/SMP/maximo/deployment/default/maximo. you will see the following error: CTGIn2252IW: Cannot connect to base services web app 246 Installation Guide: .lang. the Maximo Asset Management installation program performs a health check to ensure the deployment was successful.ConfigServiceException com.scripting.ibm.net. targetException=java. If it fails.ibm.ear .ear maximo_host webserver1 Connecting to the application Near the end of the installation process.SocketException: Operation timed out: connect:could be due to invalid address] ----.management. In the above example.apache. If you are unable to successfully log in. The conditions that trigger this problem are often temporary in nature.ibm.websphere.scripting.out for more information Exception Type: com.bat" wasadmin <waspassword> MAXIMO ctgNode01 MXServer C:\IBM\SMP\maximo\deployment\default\maximo.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. msg=Error opening socket: java.ws.ScriptingException Value: com.soap.bat script. install trace logs and wsadmintrace.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client. You should take note of the filepath of the EAR file that was unable to be successfully deployed.

This likely means that either the JVM or the HTTP server is not functional and routing requests. You might also find the following errors within the mxserver logs: Chapter 9. then use the port that it is bound to. Once you have performed corrective measures.bat did not complete successfully. If it is not.webclient.null java. a time-stamped log file is generated in the <MAM_HOME>\maximo\tools\maximo\log directory. MAXPRESENTATION update error While installing Maximo Asset Management. you might encounter a MAXPRESENTATION error.null at psdi. You should attempt to log into the application directly after exiting the installer. it indicates the presence of database values that are not synchronized.upgrade. Note: Port 80 is the HTTPServer port and should be the value used during installation. Database Updatedb The updatedb command is run several times during Maximo Asset Management installation. you can complete the deployment using the taskrunner utility as described in “General troubleshooting of the product installation program” on page 239. the port is saved in the Maximo database table maxpropvalue and can be updated to match your environment once the installation has completed. Error: (RECONLINK) Unable to update MAXPRESENTATION .saveApplicationDocument(Unknown Source) If you encounter these errors. complete the steps below to work around the problem. you did not specify the correct port for your environment during the installation. assuming you have installed the HTTPServer. Troubleshooting 247 . For future use. HTTP server. or the application was not started correctly. If the HTTPServer is installed but not bound to port 80. execute the following SQL statement to correct it. Microsoft SQL Server and MEA registration failure When installing Maximo Asset Management on an upgraded Microsoft SQL Server database.lang. execute the following SQL statements against the database to verify the cause: select maxreserved from maxsequence where tbname = 'MAXPRESENTATION'. If that fails. Each time updatedb is run. check the logs of the JVM. If you receive the following errors when installing. If you encounter an error attributed to updatedb. if the error CTGIN2254I: The C:\IBM\SMP\jacl\ solutions\MEAReg. MXApplyTransactions. refer to the updatedb log with the most recent timestamp for details. The maxreserved value should be greater than or equal to the max(maxpresentationid) value. is displayed.Exception Error: (RECONLINK) Unable to update MAXPRESENTATION . update maxsequence set maxreserved = (select max(maxpresentationid) from maxpresentation) where tbname='MAXPRESENTATION' and name='MAXPRESENTATIONID'. select max(maxpresentationid) from maxpresentation. and MXServer located on the WebSphere Application Server Network Deployment server to verify they are up and running.

at: Msg 208.f(Unknown Source) at com. Microsoft SQL Server and ICfgConfigurationStep When you attempt to install the product using Microsoft SQL Server.tds. CmnEncryptPropertiesUtil init() SEVERE: NOTE ^^T^[ITAMBVT-WIN]Invalid object name 'MaxPropValue'.log file: 248 Installation Guide: . State 1.ibm.ibm. 1. use the steps below to resolve it. The origin of this error can be confirmed by examining the CTGInstallTrace00.tds. you will see errors similar to the following in the CTGInstallTrace.inet. refer to the user documentation provided with the software.tds.init(CmnEncryptPropertiesUtil. modify the MAXSESSION.b(Unknown Source) at com.install.tds.aq. Run the following SQL statements against the database: update maxattribute set maxtype='YORN' where objectname='MAXSESSION' and attributename='ACTIVE'.inet.tds.b. If maxinst fails when attempting to create text indices for an Oracle database.k.b(Unknown Source) at com.inet.u.install.b.inet.ACTIVE data type to be an integer.common.tivoli. For ISM products. From the Microsoft SQL Server Control Center.a(Unknown Source) at com. go to the MAXUSER table.tds.u.inet.Not a valid data type.ccmdb. 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. Oracle Text indexing Maximo Asset Management requires a series of text indices to improve performance of text searches. at com.b.util. 1.common.inet.java:192) This error is caused by the collation settings for your Microsoft SQL Server. 2.Not a Valid Data Type. and modify the SCREENREADER column name null attribute to not allow nulls (required) 2. update maxattributecfg set maxtype='YORN' where objectname='MAXSESSION' and attributename='ACTIVE'.an@7ba07ba0 Sep 17. Line 1.a(Unknown Source) at com.inet.BMXAA5228E .inet.tds.ccmdb. From the DB2 Command Center. Sqlstate S0002 [ITAMBVT-WIN]Invalid object name 'MaxPropValue'.executeQuery(Unknown Source) at com.inet.a(Unknown Source) at com. Execute the following SQL statement: alter table maxuser alter column screenreader smallint.log for the following details: FINE: ENTER^ENTER^S^Using Connection: com. if you encounter error CTGIN2252I: Cannot connect to base services web application or BMXAA415E .tds. Level 16.CmnEncryptProperties Util.k. BMXAA4156E . Invalid data type While installing Maximo Asset Management.Could not register event listeners for all active Migration Manager change packages.a(Unknown Source) at com.tds.tivoli. com. These are created when the maxinst command is run as part of the installation.tds. 2008 4:21:14 PM com.util. you might also encounter the following error message: CTGIN2074E: Exception caught creating ICfgConfigurationStep object.inet.

and then continue with the installation. SQL> ALTER USER MDSYS ACCOUNT LOCK. MAXIMOUSERS:mxintadm. Connect to the database instance specifying AS SYSDBA. 'MAXADMIN:mxintadm. Troubleshooting 249 . you select the option to have the installer create the required users. 'MAXIMOUSERS:mxintadm. with arguments:['MAXADMIN:mxintadm.sql 4.ORA-01031 ORA-04045 with MDSYS.maxreg'] MAXADMIN:mxintadm. Create the MDSYS user with a command in the following format: SQL> CREATE USER MDSYS IDENTIFIED BY <password>.sql 6. you will receive an error similar to the following example: Aug 4.maxadmin. 5.was.maxadmin.maxreg]" wasundm2Cell case:vmmUsersAndGroupsExist. 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.CfgConfigWebSphere runJythonScript INFO: EXIT ^^o^{{ReturnCode: 1 CompletionMessage: CTGIN2255I: The script D:\TCCMDB711TEMP\scripts\was\DeploymentManager.ibm. as described in “Manually configuring Microsoft Active Directory” on page 150. Grant the required privileges to the MDSYS user by running the following procedure: SQL> @ORACLE_HOME/md/admin/mdprivs.sql 0 Directory server If you create users and groups manually in Microsoft Active Directory.maxadmin. deselect the Create the required users option shown on the security panel of the Maximo Asset Management installation program.maxadmin group MAXADMIN doesn't exist EXIT:vmmUsersAndGroupsExist RC= 1 StandardError: To correct this error. but. Connect as SYS and lock the MDSYS user account to prevent unauthorized use. you must install Oracle Spatial: 1. MAXADMIN:mxintadm.maxadmin'.maxadmin'.install.ccmdb. Connect as MDSYS. StandardOutput: WASX7209I: Connected to process "dmgr" on node wasundm2Manager using SOAP connector.py completed with returncode 1. 3.maxreg'] ENTER:vmmUsersAndGroupsExist args passed ['vmmUsersAndGroupsExist'. 'MAXIMOUSERS:mxintadm.config.common. 7. Rebuild the triggers by running the following: @/<oracle_home>/rdbms/admin/utlprp.SDO_GEOR_TRUNC_TABLE To resolve the issue. Install Spatial by running the following procedure: SQL> @ORACLE_HOME/md/admin/catmd.tivoli. 2. during the Maximo Asset Management installation. 2008 2:17:26 PM com.maxadmin. Chapter 9.

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

2008 4:51:25 AM com. 2008 4:51:25 AM com. While installing the product. and the password in the maximo. you will encounter an error message. 2008 4:51:25 AM com.ibm. the database user created by the installation program is an operating system user.log for the following message: The password does not meet the password policy requirements. and then complete the deployment using the taskrunner utility as described in “General troubleshooting of the product installation program” on page 239.log and DE logs for additional information.log log file to determine the nature of the deployment engine errors that have occurred.ccmdb.Return code: 3 Failure: DE in use or general failure See the CCMDB si_inst. Dec 2.pub. This messages indicate that the deployment engine was not installed correctly or otherwise failed to start. password complexity and password history requirements. More help is available by typing NET HELPMSG 2245. Having backups allows you to recover from partial installation attempts where middleware or process manager components were partially installed.ccmdb.foundation.ccmdb. Dec 2.tivoli.InstallerProxy@6ac06ac0. 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. then you did not create a user with the right password length. Prohibited property values System users created by the installation programs must adhere to the requirements of the system.foundation. For example.tivoli.ccmdb.ccmdb. prior to clicking Install. Check the minimum password length.}} Dec 2.ibm.properties file before continuing with the installation program. Troubleshooting 251 .tivoli. You will need to fix the operating system user password. If it does not. update properties as described in and then “Updating environment data” on page 280.FndDEHealthAction handleInstall FINE: NOTE ^** ERROR: Autonomic Deployment Engine installation/upgrade failure. If this message is present.foundation.install. search the CTGInstallTrace00.FndDEHealthAction Chapter 9. Deployment Engine The deployment engine is a runtime environment that includes a database of information about software installed on the system.api. To verify the password you entered for the database user is the appropriate length. you might encounter an error message CTGIN2389E.install.FndDEHealthAction handleInstall FINE: ENTER^^o^{{com.To correct these errors. The password you provide for that user needs to match the operating system password rules.zerog.ia.install.ibm. Examine the CTGInstallTrace00.ccmdb. Ensure that you enter a password of the appropriate length on the installation panel for the DB2 user that will be created.

you can manually install it using the following command: <MAM_HOME>\scripts\si_inst_wrapper. If you receive an exception when running the command.ibm.tivoli.} Sep 5. lock files (files with . verify that it can be used by the process solution installer by running the solutionInstaller command once again.ccmdb. For Windows systems.install. 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. If these locked files continue to exist on the system due to an install action that ended abnormally. When a normal installation completes. 2008 4:51:25 AM com.failInstall FINE: ENTER^^n^Dec 2.CfgProcessManagerPackageConfig runConfigurationStep FINE: EXIT ^^o^{ReturnCode: -1CompletionMessage: DE Database backup failed.FndDEHealthAction failInstall FINE: NOTE ^Setting flags to opt-out of configuration due to DE installation failure. check that the IBM ADE service is currently running.config. the deployment engine is not operational.ac.iuregistry.CfgProcessManagerPackageConfig runConfigurationStep SEVERE: EXIT ^ Output of error during PMPs Installation : ^S^java.tivoli. 2008 1:19:45 PM com. 2008 11:10:43 AM com.^n^Sep 24.lock extensions are generated in the C:\Program Files\IBM\common\acsi and C:\Program Files\IBM\common\acsi\logs directories. This will sometimes prevent the product installation program from working correctly. but not operational.IURegException: IURegistryServiceUnavailable The return code of 3 indicates that the deployment engine is in use or cannot be used at this time.config. Use this information only when you have experienced a failure during installation or uninstallation or a new deployment related to the 252 Installation Guide: .bat -action showInstalled -type all If the deployment engine is operational.pmp.bat After successfully installing the deployment engine.lang. start the service.install.ibm.install.ibm.ccmdb. When the deployment engine is active.log file. You can verify that the version of deployment engine is valid and functional by examining the <MAM_HOME>\logs\si_inst. You can then complete the deployment using the taskrunner utility as described in “General troubleshooting of the product installation program” on page 239.ccmdb.common. Use caution when removing lock files for products unrelated to the Maximo Asset Management deployment. If the deployment engine failed to install.common. they must be deleted before you run the product installation program.ccmdb. this command will produce a list of all process solution installer packages that are currently deployed and their version. If it is not. see trace for detail.RuntimeException: com.pmp. Ensure the deployment engine service is up and running.StandardOutput:StandardError:.tivoli. If the deployment engine was installed.lck and .foundation.si. these lock files are removed.ibm. there are two primary recovery scenarios.bat <MAM_HOME>\bin\solutionInstaller. The deployment engine also generates lock files when in use.

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. If no PMPs have been installed. the action you will take will depend on whether there are other non-PMP components registered in the deployment engine registry. you do not need to and should not uninstall deployment engine or restore a previous backup. 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. then you need to determine if there are other non-PMP components registered in the deployment engine registry. Deployment engine uninstall operations can result in loss of registration information about installed software components. the installation failure occurred before PMPs were installed and registered in the deployment engine registry. 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. This will cause the deployment engine registry to not accurately reflect the state of the system. which includes both Maximo Asset Management and non-Maximo Asset Management components. Note that if you used the Maximo Asset Management middleware installation program to deploy middleware to the Maximo administration workstation. 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. created using the procedure described in “Backing up the deployment engine database” on page 38. Restore the deployment engine database backup after completing the steps to remove the Process Manager configuration.deployment engine database in cases where you want to remove the product from the system completely. If no PMPs are installed. Troubleshooting 253 . 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. You should not uninstall deployment engine before reinstalling Maximo Asset Management. then you do indeed have non-PMP components in the deployment engine registry. Within this case. The current deployment engine registry should be preserved and will not prohibit installation of the PMPs during the subsequent installation. 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. You can list the contents of the deployment engine registry using the following command: Chapter 9.

You also will not be able to uninstall. your only recourse is to reinstall Maximo Asset Management after reimaging your system. click End Process.acsi_<user_name> directory. then only Maximo Asset Management components have been registered in the deployment engine registry. you do not have a deployment engine backup available. Windows 1. You can safely uninstall the Deployment engine. Global deployment engine installations Remove the C:\Program Files\IBM\Common directory. and then click OK. 3. or apply fixes to any non-PMP software that was installed using the deployment engine. 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. 254 Installation Guide: .3.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. you will not be able to use it to uninstall the middleware deployed.1 IU UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment Engine IU Version: 1. If the only other entries displayed are those associated with the PMPs shown in the showinstalled output. Remove the deployment engine home directory. If non-PMP registry entries are present.3. but be advised that if you used the Maximo Asset Management middleware installation program to deploy middleware to the Maximo administration workstation. If.1 IU RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA Name: Install IU Version: 1. Clean up the system %TEMP% directory.1 These entries are internal to deployment engine and do not have to be considered when evaluating which components are currently registered. you can use the following instructions to delete the deployment engine database. you will still need to uninstall the deployment engine to proceed with Maximo Asset Management recovery. upgrade. 2.3. complete the following steps to manually delete the deployment engine.exe process. Select the jservice. or the only entries registered in the deployment engine registry are related to the Maximo Asset Management deployment. Local deployment engine installations Remove the C:\Documents and Settings\<user_name>\My Documents\. If this is an unacceptable alternative.

5. Log in as a user with Administrative permissions.msc.Global deployment engine installations Remove the %TEMP%\acu_de. Restarting middleware on Windows This procedure describes how to restart middleware on Windows. b. Type services. c. and click Start the service. ensure the IBM ADE Service or ACSI Service services are stopped. Alternatively. Open the Windows Services panel. where <user_name> is the ID of the user that installed the deployment engine. for example following a power failure or after a maintenance shutdown. delete the acsisrv entry found in the HKEY_LOCAL_MACHINE/SYSTEM/ CurrentControlSet/Services key of the Windows registry. Type services. and click Start the service.log file. Start ITDS Admin Daemon a. If they exist. and click OK. perform the following steps: Procedure 1. you can use the following command from the command line to start the ITDS admin daemon: Chapter 9. 4.CTGINST1-0. Remove the %TEMP% \<user_name> directory. Start servers by executing the following scripts in the order in which they are listed: Start ctginst1 a. Select IBM Tivoli Directory Admin Daemon V6. Reboot the machine. Restarting middleware During the Maximo Asset Management installation. Local deployment engine installations Remove the %TEMP% \acsitempLogs_<user_name> directory. and select Run. b.msc. if you wish to remove them. and select Run. To restart middleware services.DB2COPY1 . Alternatively. you can use the db2start command from a command line to start CTGINST1. 2. if it exists.idsccmdb. It can be necessary to restart middleware services. c. Click Start. for example. While stopping these services is satisfactory. follow the instructions relevant to your environment. Select DB2 .1 . and click OK. Remove the %TEMP% \acsiTemp_<user_name> directory. Click Start. About this task To properly start middleware products on Windows. Administrator. middleware starts automatically. if you need to restart any middleware services. Troubleshooting 255 .

Alternatively. and select Run. Click Start. and select Run.1 . 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. Select IBMWAS61Service .msc. Alternatively. you can use the following command from the command line to start the node: <WAS_HOME>\profiles\ctgAppSvr01\bin\startNode.idsdiradm -I idsccmdb Start the ITDS instance: a. and click OK. c. you can use the following command from the command line to start the domain manager: <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. and click Start the service.msc. if you need to restart any middleware services.bat Start MXServer If you have chosen to create a service for starting the MXServer application server. b. b.bat Start Node a. It must be started manually in order to synchronize correctly with the database in the context of Maximo Asset Management. Type services.msc. and click Start the service. 256 Installation Guide: . Alternatively. Click Start. Click Start and select Run b. and select Run. you can use the following command from the command line to start the application server: <WAS_HOME>\profiles\ctgAppSrv01\bin\startServer.msc. and click OK. Type services. Select IBM Tivoli Directory Server Instance V6. and click OK.nodeagent. you can type apache from the command line to start the HTTP Server . Start Domain Manager a. c. b.ctgCellManager01. Alternatively. Select IBM HTTP Server 6. Select IBMWAS61Service . c. and click Start the service. you can use the Services control panel to start and stop it.idsccmdb. Alternatively. c. and click Start the service.bat MXServer Restarting middleware on UNIX This procedure describes how to restart middleware on Linux and UNIX platforms. Type services. Type services. Click Start. and click OK.1. Start HTTP Server and webserver1 a.

if you chose to deploy using a directory server. Do not uninstall the directory server until the J2EE server has been uninstalled.sh MXServer -username <username> -password <password> Uninstall the product or middleware To uninstall the product or any associated middleware.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.About this task To properly start middleware products on Linux and UNIX systems. follow the procedures in this section. Log in as root. Start servers by executing the following scripts in the order in which they are listed: Start ctginst1 instance su . ensure IBM Tivoli Directory Server or Microsoft Active Directory is active. Chapter 9. Before you begin To uninstall the J2EE server. 2.sh Start Node <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode. 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. Troubleshooting 257 .sh webserver1 -username <username> -password <password> Start MXServer <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer. for example to perform an upgrade. perform the following steps: Procedure 1.sh Start webserver1 <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.

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

Login as Administrator on Windows and root on Linux and AIX.sh. click Next. 8.exe. Start the launchpad: Windows On the DVD titled “ <IBM Maximo Asset Management V7. 3. The default location for the workspace will be the last workspace location specified. On UNIX systems. and run the following command: launchpad. and run the following command: launchpad. Select a language for the installation and click OK. From the successful undeployment panel. 7. Troubleshooting middleware uninstall Use the information contained in this section to troubleshoot middleware uninstall issues. 9. such as redeploying components. Reboot the system if you intend to reinstall middleware on this system using the middleware installation program. c. 10. The middleware installation program license agreement window is displayed. In the launchpad navigation pane. and then click Next. click Next to select a new operation. Uninstallation of WebSphere Application Server Network Deployment fails after unsuccessful binding to the LDAP directory: Chapter 9. Launch the middleware installation program from the launchpad. remove all DB2 references from the /etc/services file. b. Linux On the DVD titled “ IBM Maximo Asset Management V7. a.1 Launchpad for all Platforms”. navigate to the root directory of the product disc or the downloaded installation image. Use the information contained in this section to troubleshoot errors encountered uninstalling middleware installed through the middleware installation program. Click Next. From the Welcome panel. 2. 6. click Install the product. and then click Next. navigate to the root directory of the product disc or the downloaded installation image.1 Launchpad for all Platforms”. The default location for the workspace is c:\ibm\tivoli\mwi\workspace 5. select Undeploy the plan. and run the following command: launchpad. 4. From the undeployment preview panel.sh. or click Cancel to exit the middleware installation program. navigate to the root directory of the product disc or the downloaded installation image. In the Select Operation panel. Troubleshooting 259 . In the Middleware section. From the Choose Workspace panel.1 Launchpad for all Platforms”. specify the workspace directory containing the currently deployed plan. AIX On the DVD titled “ IBM Maximo Asset Management V7.Procedure 1. click Install the middleware. click Next to undeploy the plan. The entries that need to be removed are: v db2c_db2insxy 50001/tcp v db2c_db2inst1 50000/tcp 11. Read the license information and select I accept both the IBM and the non-IBM terms if you agree with the terms.

For Windows systems. If you provide the middleware installation program with the wrong credentials.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. Restart the middleware installation program to undeploy the plan. the installation will fail at the WebSphere Application Server Network Deployment configuration step. The remote LDAP directory can be hosted by either Microsoft Active Directory or by IBM Tivoli Directory Server. complete the following steps: a. you need to provide the credentials to access the remote LDAP server. you encounter the option to configure WebSphere Application Server Network Deployment security with an existing remote LDAP directory.lang.1 . Locate the process-id of the Java thread: <WebSphere Install Location>/java/bin/java and then kill the process. This will result in the following error: SECJ0305I: The role-based authorization check failed for admin-authz operation Server:stop:java. complete the following steps: a. change the startup type of the following WebSphere Application Server Network Deployment entries from Automatic to Manual.Integer. IBM WebSphere Application Server V6.Boolean:java. In order to configure WebSphere Application Server Network Deployment successfully.1 . administrator. For UNIX systems. 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.ctgCellManager01 IBM WebSphere Application Server V6. WebSphere Application Server Network Deployment will not be able to issue the stopManager command in order to stop the ctgDmgr01 profile.nodeagent 260 Installation Guide: . 2. In Services control panel. 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. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: operator. List Java processes.lang. 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. kill -9 <process-id> c. ps -ef | grep -i java b. Before you begin About this task When using the middleware installation program. complete the following steps as a workaround: Procedure 1. If you encounter the error described above.

Maximo Asset Management deployments will fall into one of the following categories: Fully-automated configuration In this scenario. Uninstalling the product This section contains information about uninstalling Maximo Asset Management 7. For uninstallation purposes. such as using the Add/Remove Programs panel. Maximo Asset Management uninstallation is a comprehensive procedure and does not support partial removal of individual components or process managers. you selected the option to allow the Maximo Asset Management installation program to automatically configure middleware during deployment. You did not allow the Maximo Asset Management installation program to automatically configure middleware during deployment. Manual configuration In this scenario.b. messages are generated that indicate conditions that you must resolve manually before attempting a reinstall. Chapter 9. If you have deployed a product that includes process managers before you deployed Maximo Asset Management. Note that you will only run the Maximo Asset Management uninstallation program once. Restart the middleware installation program to undeploy the plan. you selected the option to manually configure middleware. 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. Refer to “Uninstalling a manually configured deployment” on page 263 for information about uninstalling Maximo Asset Management for this type of deployment. Refer to “Uninstalling an automatically configured deployment” on page 262 for information about uninstalling Maximo Asset Management for this type of deployment. you can reinstall Maximo Asset Management by restarting the Maximo Asset Management installation program. After the Maximo Asset Management uninstall process is complete. The uninstall procedure you follow depends on the type of Maximo Asset Management deployment you are uninstalling. If there are errors. Restart the system.1. be advised that you will also be removing the process managers deployed with the other product. 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. Troubleshooting 261 . and you want to uninstall Maximo Asset Management. This also includes manually removing files from the administrative workstation. c. including those deployed by other products.

Password Enter the password for the application server administrator user ID.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. you will not be prompted to input them again. About this task Procedure 1. User ID Enter the password for the application server administrator. 3. 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. enter the following information and then click Next. 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. To run the Maximo Asset Management uninstall program. enter the following information and then click Next. The remote user ID must be able to access the server using the remote access protocol enabled on that system. from the administrative workstation. Remote user ID Enter a user ID in order to access the system hosting the application server. From the database administration panel. Before you begin Ensure all applicable services are running and all middleware servers are accessible. corrupt. If the Maximo Asset Management uninstall program cannot access the database because it is unavailable. for example. From the application server information panel. The uninstall program will use values entered during the initial installation during uninstall. for DB2. If the uninstall program is unable to validate these credentials. if you updated passwords since the original installation. Remote password Enter a password for the remote user ID. or otherwise inaccessible. you will be prompted to supply the updated information. If credentials used to access the database and J2EE server are still valid. 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.bat 2. 262 Installation Guide: . open a command prompt and issue the following command: Windows <MAM_HOME>\_uninstall\uninstall.

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. Chapter 9. you will have to remove it manually before you proceed to the reinstallation process. and click Done to exit the program. For Oracle databases. 5. the Maximo Asset Management uninstall program might not remove the Maximo Asset Management installation directory. you can supply the SQL Server administrator user ID and password. Uninstalling a manually configured Maximo Asset Management deployment consists of running the Maximo Asset Management uninstallation program. 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. c:\ibm\smp. and then click Uninstall. Check to ensure the uninstall program removed the Maximo Asset Management installation directory. or otherwise inaccessible. you can supply the credentials for the Administrator user ID and the Oracle software owner ID. Troubleshooting 263 . 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. 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. If the Maximo Asset Management installation failed early in the process. for example. After the uninstall process has completed. Remote password Enter a password for the remote user ID. specify whether you want to restart the computer now or later. For Microsoft SQL Server databases.Remote user ID Enter a user ID in order to access the system hosting the database. 4. 6. If the Maximo Asset Management uninstall program cannot access the database because it is unavailable. and then manually dropping and recreating the database you intend to use with the reinstall process. Review the components that are listed in the uninstall summary panel. If this directory still exists after you have completed the uninstall process. The remote user ID must be able to access the server using the remote access protocol enabled on that system. Before you begin Ensure all applicable services are running and all middleware servers are accessible. corrupt.

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. 4. you must drop the Maximo Asset Management database and recreate it. c:\ibm\smp. Check to ensure the uninstall program removed the Maximo Asset Management installation directory. To run the Maximo Asset Management uninstall program. and then click Uninstall.bat 2. User ID Enter the password for the application server administrator. you will be prompted to supply the updated information. From the Introduction panel. you will not be prompted to input them again. the Maximo Asset Management uninstall program might not remove the Maximo Asset Management installation directory. enter the following information and then click Next. After the uninstall process has completed. 6. open a command prompt and issue the following command: Windows <MAM_HOME>\_uninstall\uninstall. 5. for example. if you updated passwords since the original installation. From the application server information panel. 3. for example. Review the components that are listed in the uninstall summary panel. What to do next You can now proceed with recovery of your manually configured database. If the uninstall program is unable to validate these credentials. If the Maximo Asset Management installation failed early in the process. you will have to remove it manually before you proceed to the reinstallation process. If credentials used to access the database and J2EE server are still valid. If this directory still exists after you have completed the uninstall process. read the introductory information and then click Next. The uninstall program will use values entered during the initial installation during uninstall. click Done to exit the program. Before rerunning the Maximo Asset Management installation program. Password Enter the password for the application server administrator user ID. Restoring the DB2 database server: 264 Installation Guide: . About this task Procedure 1. from the administrative workstation. 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.

506.ctginst1. Manually recreate the maxdb71 database. 3. To list applications. complete the following steps: Procedure 1. Start a DB2 command session or run db2cmd from the command prompt.504 )' 4. If any connections exist. Chapter 9. Refer to “Manually configuring DB2 9. Before you begin Ensure that the MXServer application server on WebSphere Application Server Network Deployment is stopped before deleting the database. by default): db2 drop database MAXDB71 5. you must first restore the DB2 database server to the same state as before Maximo Asset Management was installed.DB2.071113150234 MAXDB71 # of Agents ----1 1 1 b. Log onto the system hosting the DB2 server. Before you begin Ensure that the MXServer application server on the WebSphere Application Server is stopped before dropping the database. To restore the Maximo Asset Management database. 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. 2.x” on page 125 or “Manually configuring DB2 8.------*LOCAL.071113150237 MAXDB71 *LOCAL.DB2.071113150236 MAXDB71 *LOCAL. Troubleshooting 265 .2” on page 130 for more information. 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. Restoring the Oracle database: In order to rerun the Maximo Asset Management installation program. First list and then force all applications connected to the database to close using the following commands: a. Handle ------507 506 504 Application Id DB Name ---------------------------.In order to rerun the Maximo Asset Management installation program. Drop the Maximo Asset Management database (MAXDB71. close the connect application using a command similar to the following sample command: db2 force application '( 507. you must first restore the Oracle database server to the same state as before Maximo Asset Management was installed. About this task Restoring the DB2 database server to the same state as before Maximo Asset Management was installed.

Linux. Manually recreate the database. Delete the Maximo Asset Management database user (maximo. issue the following SQL commands and then try the SQL drop command again: shutdown immediate. Invoke SQLPlus from the command line: sqlplus /nolog c. you must first restore the Microsoft SQL Server database server to the same state as before Maximo Asset Management was installed. Log into the Oracle instance using SQLPlus as a DBA user: Note that the Oracle SID for a clean install is ctginst1.About this task Restoring the Oracle database server to the same state as before Maximo Asset Management was installed. Set the environment variable from the command line: set ORACLE_SID=<your sid> b. by default) using an SQL command similar to the following sample command: drop user maximo cascade. complete the following steps: Procedure 1. If you are using an existing Oracle instance with Maximo Asset Management. Restoring the Microsoft SQL Server database: In order to rerun the Maximo Asset Management installation program. If you receive an error when issuing this command that you cannot drop a currently connected user. 4. startup. To restore the Maximo Asset Management database. Set the environment variable from the command line: ORACLE_SID=<your sid> export ORACLE_SID b. use the Oracle SID associated with the existing instance. 2. Do not disconnect from the database. Log into SQLPlus as a DBA user: connect sys/<sys password> as sysdba Windows a. requires you to drop the Maximo Asset Management database schema user before rerunning the Maximo Asset Management installation program. Solaris a. AIX. 266 Installation Guide: . HP-UX. Invoke SQLPlus from the command line: sqlplus /nolog c. Log into SQLPlus as a DBA user: connect sys/<sys password> as sysdba 3. Log into the Oracle database server as the Oracle software owner. Refer to “Manually configuring Oracle 10g” on page 136 or “Manually configuring Oracle9i Rel2” on page 139 for more information.

between the time of the initial product deployment and a subsequent installation action. Listed in the table below are installation properties that are found in the install.db.properties files. To delete the database. Open the Microsoft SQL Server Management Studio. If there are any updates made to installation properties. Refer to “Updating environment data” on page 280 for more information. Manually recreate the maxdb71 database. Chapter 9.InstallLocation Definition Install location of the maximo directory. maximo mxe. and then click Connect. complete the following steps: Procedure 1. In the Delete Object window. To restore the Maximo Asset Management database. For example. and then click Delete. 2. Refer to “Manually configuring SQL Server” on page 144 more information. 3. 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. right-click the database name you created during installation (MAXDB71 for example). a password or host name change. and then click OK. 4.user Database user that the server uses to attach to the database server.properties and maximo. such as applying a fix pack or performing an upgrade. maximo. Log into the instance of Microsoft SQL Server that is used by Maximo Asset Management install using the sa user ID. the corresponding properties must be updated in these files.Before you begin Ensure that the MXServer application server on WebSphere Application Server Network Deployment is stopped before deleting the database. For example. Installation properties Category MAXIMO Properties Property Maximo.schemaowner Owner of the database schema. About this task Restoring the Microsoft SQL Server database server to the same state as before Maximo Asset Management was installed. expand the instance tree down to the databases category. Installation properties Installation properties are recorded in properties files during a deployment and are used as input by future install-related actions. select Delete backup and restore history information for databases and Close existing connections. This value must be dbo for Microsoft SQL Server. Table 21.db. Troubleshooting 267 . For example. C:\\IBM\\SMP\\maximo mxe. for example. 5.

MLCacheLazyLoad mxe.adminuserid 268 Installation Guide: . For example. The RMI registry is started by the first instance of the maximo application to run. the multi-language metadata cache loads one object at a time. The default is false. You can select another available port number.hostname mxe. Installation properties (continued) Category Property mxe.admin mxe. mxe.registry. SMTP host server.workflow.name Definition Password for the database user name. Name to bind the MXServer server object to in the RMI registry.smtp. There is a single central RMI registry server. Valid E-mail address used by workflows to communicate with workflow participants.rmi. mxe. For example. Set this flag to 1 to load all objects simultaneously for one language. If set at zero.Table 21. Setting this value to 1 indicates you are using LDAP for security. or for custom applications.adminEmail mxe. If the product enabler changes this value must be updated. The administrative user.host mxe. E-mail account of the workflow administrator. RMI communication port. mxe. RMI uses any available port.password mail. This user must have access to all Sites in the system. This is the port available for the other application instances to communicate with the central server. 13400.allowLocalObjects Set to true in production environments. Used by the server for administrative tasks and to run cron tasks.port mxe. The port number used to bind RMI/JRMP communications. Set to false for development work.db. A WebSphere Application Server Network Deployment environment could have multiple instances of the product application running at one time. This registry coordinates these instances. mxserver. By default.useAppServerSecurity Indicates whether to use LDAP or native authentication.port Name of the machine and port hosting MXServer. The product enabler (license key) is used during installation. mxe. to improve system performance.UserLicenseKey mxe.

The default value is 30 minutes. When this property is defined.sun. mxe.mbocount Displays the number of business objects created by the server. The character set for e-mail notifications sent from the product.regpassword User registration login password.reguser. mxe.db. mxe. To use a different provider. it is the charset that is used to encode the subject and message when an e-mail notification is sent. The default value is true.charset mxe.email.system. The default is 1.. Self registration user.Table 21. Property used by the application to determine if property files are encrypted. mxe.system.provider. mxe. you can specify a value for this parameter. Installation properties (continued) Category Property mxe. You can change the value to 0 which will disable this feature. mxe.security. This value is set to true if the file is encrypted. maximo.required.reorder. This is the password for the user listed for mxe. mxe.encrypted Chapter 9. This user is responsible for the process by which users can cerate their own accounts. Troubleshooting 269 .adminuserloginid user. An example value would be 7100.previewtimeout The reorder preview time out period (in minutes).provider The security provider is obtained from the policy file.min. which should be similar to the Web server session time out.SunJCE. The default value is maxadmin.adminuserloginid Definition Defines the default login user ID for the product application.defaultuserid Set this flag to true if you want the Esignature login dialog to default to the login ID.crypto.adminPasswd mxe. which is normally com.esig.version Defines what the minimum level of database is required for an upgrade.system. The default value is maxreg.reguser The password for the mxe.

CCMDB.userAppServerSecurity = 1. C:\\IBM\\SMP.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. For example. false.. Install. upgrade.UserShortcuts Location of the shortcut menu items for the process solution installer and the product console.AdditionalLanguages CCMDB. For example.PMP CCMDB. Type of installation. Binary value that determines whether sample data is to be loaded during the installation.DeploySampleData Additional languages installed for the product. For example.BaseLanguage Base language that was set for the product. For example. For example. C:\\IBM\\SMP\\SDK. CCMDB.LDAPUserMgmt Definition Indicates whether LDAP owns user management when mxe.JREInstallLocation JRE install location. which includes fix pack. CCMDB. Installation properties (continued) Category Property mxe. CCMDB. For example. en. or new installation. true.InstallLocation Product install location. The locale setting of the administrative workstation system.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. CCMDB. Base Services specific Properties BASE. C:\\IBM\\SMP\\JRE. For example. en. For example. CCMDB. CCMDB specific Properties CCMDB.SDKInstallLocation SDK install location. CCMDB. The default value is 1.InstallType 270 Installation Guide: .Table 21. CCMDB. true.Locale Unused property.

ThinClientFullyAutomatedConfig Binary value that indicates if the installation program will download the keystore from the WebSphere Application Server Network Deployment deployment manager.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. For example. This value will be used for all future upgrades and fix packs. once set. is a fixed value and cannot be changed. C:\\IBM\\WebSphere\\ AppServer BASE.AutomateConfig Server Network Deployment specific properties Binary value that indicates if WebSphere Application Server Network Deployment will be automatically configured by the installation program. WAS. C:\\ibm\\WebSphere\\ AppServer\\profiles\\ctgDmgr02\\etc\\ trust.ThinClientLocalKeystore Location of the keystore file.DeployOptionalContentSet Definition Indicates whether or not you selected to deploy optional content during the initial upgrade. For example. WAS.ThinClientInstallLocation Chapter 9.Location Location of scripts used by the installation program. The previous version of base services that was installed. For example. Needed when using IPV6 WebSphere Application WAS. This value.p12. If this value is set to false. WebSphere Application Server Network Deployment thin client install location. WAS. WAS. 8879.Scripts.VersionUpgradingFrom WAS Thin Client specific Properties WAS. Troubleshooting 271 . For example. the user will have to copy it manually. For example. WAS.InstallLocation Installation location for WebSphere Application Server Network Deployment. C:\\IBM\\SMP WebSphere Application WAS.SOAPConnectorPort SOAP port of the WebSphere Application Server Network Deployment deployment manager. A value of false indicates that the user manually configured the WebSphere Application Server Network Deployment server before running the installation program.Table 21. Installation properties (continued) Category Property BASE. C:\\IBM\\SMP\\WASClient.

RemoteAccessUserName WebSphere Application Server Network Deployment administrator password. C:/IBM/WebSphere/AppServer/ profiles/ctgDmgr01 WAS. WAS. For example. For example. For example. For example. maximo_host. For example. ctgNode01 WAS. WebSphere Application Server Network Deployment deployment manager system user ID used for tasks such as copying ISC WAR files and fetching the keystore. Installation properties (continued) Category Property WAS.DeploymentManagerProfileRoot Location of the WebSphere Application Server Network Deployment profile.ClusterName WebSphere Application Server Network Deployment cluster name. WebSphere Application Server Network Deployment CELL name. ctgCell01 WAS. For example. WAS.AdminUserName WebSphere Application Server Network Deployment administrator name.ApplicationServerName WebSphere Application Server Network Deployment application server name.NodeName WebSphere Application Server Network Deployment node name.Table 21. MXServer WAS. WebSphere Application Server Network Deployment deployment manager system user password.VirtualHost 272 Installation Guide: .RemoteAccessPassword WAS.DeploymentManagerProfileName WebSphere Application Server Network Deployment profile name.CellName WAS.ServerProfileName WebSphere Application Server Network Deployment application server profile name. This property is designated for future use. Name of the WebSphere Application Server Network Deployment virtual host.AdminPassword WAS. MAXIMOCLUSTER.DeploymentManagerHostName Definition Host name of the WebSphere Application Server Network Deployment deployment manager. ctgDmgr01 WAS. ctgAppSrv01 WAS. For example. For example. wasadmin WAS. For example.

Table 21. Server name of the system hosting the service integration bus message database. For example. intjmsds. WAS. intjmsbus.VirtualHostPort Definition Port for virtual host for listening for HTTP server.SibName Name of the service integration bus.SibHiMsg Service integration bus high message count. WAS. Used to manage HTTP server from within WebSphere Application Server Network Deployment.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. Instance name of the service integration bus database.SibDBServerName Name of the service integration bus messages database. WAS.SibDBInstance WAS. For example. For example. WAS. 1024. 512. DB2. 500000. For example. webserver1. For example.AppServerJvmHeapMax Maximum heap size setting for the application server JVM.SibDBName WAS. WAS. For example. Chapter 9. Minimum heap size setting for the application server JVM.SibDSName Service integration bus data source name created to access the service integration bus persistence store. Installation properties (continued) Category Property WAS. 80. WAS. Troubleshooting 273 .SibDBType Database type where the service integration bus messages are being stored.AppServerJvmHeapMin Host name where the HTTP server is located. For example. WAS. WAS. For example.WebServerName Name of the WebSphere Application Server Network Deployment web server.WebServerHostName WAS. WAS.

ou=SWG. Where the service integration bus database is installed. WAS.SibDBUserName User ID used to access the persistence datastore database for service integration bus messages.VmmFullyAutomatedConfig 274 Installation Guide: . db2fenc1. For example. WAS. Administrator distinguished name.VmmUserRDN LDAP tree where users are stored.SibDBInstallDir WAS.VmmGroupRDN LDAP tree where groups are stored. 50005.Table 21.SibDbRemoteAccessUser Instance owner for the service integration bus database.SibDbInstanceAdminUser WAS.SibDbRemoteAccessUser. Password for the instance owner of the service integration bus database. For example. Host name of the LDAP system host. Unused property. ou=users.Vendor LDAP. For example. This property is only used for databases hosted on UNIX systems.SibDBUserPass WAS. true. Installation properties (continued) Category Property WAS. WAS. For example.SibDbRemoteAccessPassword WAS.UseDefaultVmmSchema WAS.AutomateConfig Binary value that indicates whether the installation program will automatically configure the directory server.SibDbInstanceAdminPassword WAS.o=IBM. For example.SibDBUserName. For example.ServerHostName LDAP. LDAP Server specific Properties LDAP. ou=groups. For example.SibDbFencedUser Fenced user ID for the service integration bus database. Database server system user used to configure the service integration bus remotely. c=US. true. LDAP. C:\Program Files\IBM\SQLLIB. cn=root. For example.AdminDN The type of LDAP repository. Password for user ID named in WAS. c=US. Binary value that indicates if the installation program will create users and directories.ou=SWG. WAS. WAS. Password for user ID named in WAS.o=IBM. WAS.SibDBServerPort Definition Database server port for the database containing the service integration bus messages.

RemoteAccessUserName Database.db.com:50005/maxdb71.TdsDriver.db. Port listening for connection requests. 8.initialConnections Number of database connections to create when the application server is started.RemoteAccessPassword mxe. jdbc:db2:// mymachine.AutomateConfig Binary value that indicates whether the installation program will automatically configure the database.tds.RemoteAccessUserName. For example.jdbc.ServerPort Definition Password for user ID named in LDAP. com.DB2Driver.Table 21. mxe. C:\Program Files\IBM\LDAP\V6.jcc. jdbc:inetdae7a:mymachine. mxe.AdminPassword LDAP. Installation properties (continued) Category Property LDAP.com:1433?database=max or jdbc:oracle:thin:@mymachine.inet. For example. 8. Troubleshooting 275 .Vendor Database type. 3. Database specific Properties Database.maxFreeConnections Maximum number of free database connections available in the connection pool.OracleDriver. Database.newConnectionCount Number of new connections to be created when the minimum free connections are available in the connection pool.minFreeConnections Minimum number of free database connections needed in the connection pool in order for more connections to be allocated. oracle. 5.ibm. Password for user ID named in Database. LDAP. Database. For example.db. 389. For example. For example. mxe.db.db2.mydomain. true. For example.driver Database server system user ID that is used for configure the database remotely. mxe.url JDBC URL of the database.InstallLocation Install location of the directory server.2. For example.db. For example.com:1521:ctginst1.mydomain. or com. For example.mydomain. For example.db. Javaclass name of the JDBC driver. mxe. Chapter 9. DB2.AdminDN.

To disable.db. mxe. Optimal setting is 200 rows.db.format. For SQL Server.db. This value cannot be modified. For Oracle.sqlserverPrefetchRows Setting to reduce lock contention.logSQLTimeLimit The system logs the SQL statements that take longer than the specified time limit. The default value is 0. the value is current timestamp.db. and the default value cannot be edited. the value is sysdate.db.db. The default value is 1000 milliseconds. mxe.format. The time is measured in milliseconds (thousandths of a second). mxe. mxe.db. mxe. mxe. This value cannot be modified.logSQLTimeLimit=0. The value for Oracle is NVL. the value is getdate(). For IBM DB2. This value is only valid for SQL Server. Installation properties (continued) Category Property mxe. 276 Installation Guide: . Can be either true or false.Table 21.nullvalue The database-specific format of the nullvalue function. This value cannot be modified. For IBM DB2 the value is COALESCE.upper This value defines the database uppercase function for the system. The value for SQL Server must be set to ISNULL.systemdateformat System date format.db.transaction_isolation Definition The system install sets the value to: TRANSACTION_READ_COMMITTED. The default is false. and the default value cannot be edited. edit the file to read: mxe.autocommit This value sets the autocommit mode used for the Write connections. and the default value cannot be edited. Setting a value larger than 500 can degrade performance.

/opt/app/oracle/ product/10.TempTablespaceLocation Database.IndexTablespaceName Index tablespace name. Oracle DB Properties Database. For example. For example.SoftwareOwner. Installation properties (continued) Category Property mxe.0/db_1.Oracle. measured in Mb. Database. For example. Oracle installation location.Oracle.db. The default is 200 rows.Oracle.DataTablespaceLocation Database. Tablespace size. For example. For example. 1000. measured in Mb.Oracle. 8000. For example. /opt/app/oracle/product/10. measured in Mb. Database.Oracle. To disable.Oracle. Database. 8000.2.db.Oracle. maxdata. Temporary tablespace size.TempTablespaceName Temporary tablespace name.DataTablespaceMaxSize Maximum size of the tablespace.SoftwareOwner Oracle instance name. Chapter 9. Database.IndexTablespaceLocation Database. For example. For example. Index tablespace size. oracle. Database. Troubleshooting 277 . Owner of the software installation. Oracle tablespace name for the product database.SoftwareOwnerPassword Database. Database. Database. 1000.TempTablespaceMaxSize Maximum size of the temporary tablespace.InstanceName Database. 1000.DataTablespaceSize Location of Oracle database tablespace.Oracle. The stack trace log is also repeated for every multiple of such fetches. For example.0/db_1.InstanceLocation Oracle instance location.Oracle.2.InstallLocation Database. For example.Oracle. edit the file to read: mxe.Oracle. measured in Mb. maxdata. For example.Oracle.Oracle.TempTablespaceSize Location of temporary tablespace. maxtemp.IndexTablespaceSize Location of index tablespace. measured in Mb. a stack trace is printed in the log for every business object set that fetches beyond the set limit of rows.Oracle. Database.fetchResultLogLimit Definition When this setting is enabled.Table 21.Oracle. Database.Oracle.DataTablespaceName Password for the user ID listed in Database.fetchResultLogLimit=0.Oracle.

Hostname of the DB2 server. 1024 Database. For example.schemaowner Database.DBAUserName. Password for Database.DB2.DB2. Password for user listed in mxe. Database.schemaowner.DB2. Host name of the Oracle server. mymachine.Oracle.DBAUserName Oracle DBA user name.5 Database. For example.ServerHostName Password for user ID listed for Database. For example.LogSecond Number of secondary log files allowed. Database. mxe.DB2.AppCtlHeapSize Application control heap size. 50005.ServiceUser. For example.db.Table 21.DB2.ServerHostName Database.DB2.ServiceUser Database. 4096 Database. 30000 Database.Oracle.db.ServerPort Database server port. For example. 278 Installation Guide: .DB2. Port number used by Oracle.InstanceName Name of the database instance. 8000.DB2.SchemaPassword Database.Oracle.DatabaseName Name of the database. 1521.DB2. For example. For example. Database. maxdb71.ApplHeapSize Application heap size.DB2. /opt/IBM/db2/V9.DBAPassword DB2 DB Properties mxe.DB2. ctginst1.DB2. For example.Oracle.ServicePassword User ID used to autostart. For example. Database. For example. sys. Database.mydomain. For example.com. Database. For example. For example.LogFileSize Set the size for transaction logs. measured in Mb. 1024 Database.DB2. Installation properties (continued) Category Property Database.ServerPort Owner of the database schema.schemaowner Database.db.IndexTablespaceMaxSize Definition Maximum size of the index tablespace. 4 Database.InstallLocation Install location of the database.LockListSize Size allocated to the lock list. Owner of the database schema.

Database. Database.TempTablespaceSize Location of temporary tablespace. For example. Troubleshooting 279 . Database.DB2. 1000. Database. measured in Mb.FencedUser System user used as the fenced user ID for DB2 on UNIX systems. For example.BufferPoolLocation Database.DB2. measured in Mb.DataTablespaceSize Location of DB2 database tablespace. Tablespace size.DB2.DB2. For example. 8000. For example.Table 21. Temporary tablespace size. Database. maxtemp. 32 Database.DataTablespaceName DB2 tablespace name for the product database.TempTablespaceName Temporary tablespace name. Installation properties (continued) Category Property Database. db2fenc1. Database.IndexTablespaceSize Location of index tablespace.DB2. maxdata. measured in Mb. For example.DB2. Chapter 9.AuthType Method DB2 uses to authenticate users. For example. For example.DB2.DB2.DB2. For example.BufferPoolSize Location of the buffer pool. Database. 32 Database. 8000. 1000. For example. 1000. measured in Mb. For example. server.BufferPoolName DB2 buffer pool name. Size of the buffer pool.TempTablespaceMaxSize Maximum size of the tablespace. Temporary tablespace size.DB2.DB2. maxdata. For example. Database.DataTablespaceLocation Database. For example.DB2. For example. 32 Database. Database. MAXBUFPOOL. Database.DataTablespaceMaxSize Maximum size of the tablespace.DB2.IndexTablespaceName Index tablespace name.DB2.DB2.PageSize Definition Page size setting.DB2. measured in Mb.DB2.ExtentSize Number of pages per extent (group of pages).IndexTablespaceLocation Database.DB2. For example. Measured in kb.TempTablespaceLocation Database.

and modifying the database. Indicates which application server was chosen during installation. Initial size for data file for database. Administrative user for the SQL Server instance. For example. For example.SQL. For example.InstallLocation SQL Server installation location.db. creating database user.InstanceAdminPassword SQL Server DB Properties mxe. A way to specify the name for the database transaction log file. Password for the user ID specified for Database.ServerPort Database. maxdb71_log. C:\\Program Files (x86)\\IBM\\Common\\acsi.SQL.SQL. 8000. WebSphere. This value must be dbo for Microsoft SQL Server. Database.DataFilegroupName Database. For example.ServerHostName Database.SQL.schemaowner Administrative user or the database instance. For example. If you have made any environmental changes to any of 280 Installation Guide: .SQL. maxdb71_dat.DataFileLocation Database.SQL.Table 21.InstanceAdminPassword ADE (DE) Properties DE. Location of the deployment engine. Location for database data file A way to specify the name of the data file used for the database. myhost. For example.properties and maximo.com.SQL.DatabaseName Name of the database. used during install for creating database. For example. Administrative users password.SQL. maxdb71.SQL.InstanceAdminUserName Owner of the database schema. SQLServer Database transaction log file size.InstanceAdminUserName Database.InstanceAdminUserName Database.DataFileSize Database.DataFileMaxSize Database.DB2. measured in Mb.DB2.IndexTablespaceMaxSize Definition Maximum size of the index tablespace. Host name of the database server. Database. Maximum size for data file for database.SQL. Database server port. Database logical name file group.DB2. Database.InstalllLocation Application Server Type Properties ApplicationServer. For example.DB2. For example. the installation program uses values recorded from the previous deployment.LogFileSize Database. Database. These values are stored on the administrative system in the install.C:\\Program Files\\Microsoft SQL Server\\90. Installation properties (continued) Category Property Database. For example.SQL.properties files.SQL. PRIMARY.DataFileName Database.mydomain.LogFileName Database.SQL. 1433.Vendor Updating environment data When you install a fix pack or otherwise upgrade an existing ISM product.

properties file: The install. Edit the maximo.properties file to <Product_Home>\maximo\applications\ maximo\properties\ h.properties file and update the credential or connection information for the database server.properties file: a.the systems used for the original deployment. This method of updating credential information in property files has one exception.properties file.properties file before you upgrade.properties_orig to maximo. you will not be prompted to provide them again. i. Complete the following steps to update database properties within the maximo. j. These values must be up to date before you apply a fix pack or other upgrade operation. you will be prompted to supply the correct information. it will attempt to use values found in the install. Make a backup of the maximo. pending successful use of these credentials. c. Make a backup of the maximo. Run the encryptproperties. Copy the maximo.properties and maximo. Troubleshooting 281 .properties g. Complete the following steps to update properties within the install.properties and maximo. If these values have changed from the previous deployment. they must be recorded in the install. when the product installation program is run for an upgrade task. Change directory to <Product_Home>\etc\ Chapter 9. you must first manually update them. if you have not updated the user name or password for a system used in the previous deployment. Save the file. Any changes to this information from the time of the original deployment must be manually recorded in the maximo. d. for example.properties_orig found in the directory. These values will then be written to the appropriate property file. Database connection and credential information must always be current before you attempt an upgrade operation. Delete the maximo. and. If the installation program is unsuccessful in its attempt to log into a system using the credentials found in the properties files. Database connection and credential information is stored in the maximo. the installation program will use the credentials found in the properties files. Before you begin As previously stated.bat file located in <Product_Home>\maximo\ tools\maximo\ directory against the file to encrypt it.properties file. 2. a.properties file contains the majority of properties used by the installation program. Rename the unencrypted file named maximo.properties files to complete the upgrade. Change directory to <Product_Home>\maximo\applications\maximo\ properties\ b. Change directory to <Product_Home>\etc e. During the upgrade operation. About this task Procedure 1. including non-connection related properties for the database. such as changing a host name or updating a password.properties file. f.properties files. This backup should be a permanent backup that can be copied from when you need to update properties in the future.

you will be able to upgrade. host name of the WebSphere Application Server Network Deployment server. 282 Installation Guide: .properties file and make updates. or install another ISM product using the corrected values.DeploymentManagerHostName value in the install.properties file. Edit the C:\IBM\SMP\WASClient\thinwasadmin. Save the file. Edit the install. c. c.host=<fully-qualified host name> d.b.DeploymentManagerHostName).ws.properties file. you must also update a property for the WebSphere Application Server Network Deployment thin client in the thinwasadmin.bat file. fully-qualified. complete the following steps: a. Update the following line of the file with the new. There is one important exception to this procedure. in addition to updating this property value in the install. When changing the value of the WebSphere Application Server Network Deployment host name (WAS.bat -username <domain manager user name> -password <password> e.properties file. Results After you have completed these updates. as described in the previous procedure. set wsadminHost=-Dcom. To update the WebSphere Application Server Network Deployment host name that was used in the previous deployment. Update the WAS. 3.bat file and then run that file. Run thinwasadmin.scripting. thinwsadmin. These values will then be written to the install. install a fix pack. Do not make changes to encrypted properties (prefixed by [enc]). b. indicate that you do want to download the truststore file.ibm. When prompted. You will be prompted for updated values during the update operation.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any reference to an IBM product. This information could include technical inaccuracies or typographical errors. The furnishing of this document does not grant you any license to these patents. therefore. Any functionally equivalent product. in writing.A. to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome. Changes are periodically made to the information herein. INCLUDING. or service that does not infringe any IBM intellectual property right may be used instead. 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 make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. or service is not intended to state or imply that only that IBM product. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. IBM may have patents or pending patent applications covering subject matter described in this document.S. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. this statement may not apply to you. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. services. contact the IBM Intellectual Property Department in your country or send inquiries. IBM may not offer the products. program. © Copyright IBM Corp. BUT NOT LIMITED TO. You can send license inquiries. program.2010 283 . program. EITHER EXPRESS OR IMPLIED. 2007 .A.Notices This information was developed for products and services offered in the U. Minato-ku Tokyo 106-0032. program. or service. Some states do not allow disclaimer of express or implied warranties in certain transactions. these changes will be incorporated in new editions of the publication. 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. 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. For license inquiries regarding double-byte (DBCS) information. or features discussed in this document in other countries. NY 10504-1785 U. Consult your local IBM representative for information on the products and services currently available in your area. it is the user's responsibility to evaluate and verify the operation of any non-IBM product. in writing. However.S. or service may be used.

some measurements may have been estimated through extrapolation. The information herein is subject to change before the products described become available. MN 55901 U. and products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice. To illustrate them as completely as possible. compatibility or any other claims related to non-IBM products. the results obtained in other operating environments may vary significantly.A. payment of a fee. are current and are subject to change without notice. IBM International Program License Agreement. their published announcements or other publicly available sources. and distribute these sample programs in any form without payment to IBM. including in some cases. modify.S. for the purposes of developing. Actual results may vary. or any equivalent agreement between us. which illustrate programming techniques on various operating platforms. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Therefore. IBM has not tested those products and cannot confirm the accuracy of performance. Furthermore. Users of this document should verify the applicable data for their specific environment. Dealer prices may vary. marketing or distributing application programs conforming to the application programming interface for the operating 284 Installation Guide: . All IBM prices shown are IBM's suggested retail prices. brands. the examples include the names of individuals. You may copy. Department 49XA 3605 Highway 52 N Rochester. This information contains examples of data and reports used in daily business operations. This information is for planning purposes only. 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. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. using. Any performance data contained herein was determined in a controlled environment. COPYRIGHT LICENSE: This information contains sample application programs in source language. should contact: IBM Corporation Software Interoperability Coordinator. Information concerning non-IBM products was obtained from the suppliers of those products. 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. and represent goals and objectives only. Such information may be available. subject to appropriate terms and conditions. companies.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.

the IBM logo. or both: IBM. Intel. AIX. and Pentium are trademarks of Intel Corporation in the United States. These examples have not been thoroughly tested under all conditions. other countries. Microsoft. and Internet Explorer are trademarks of Microsoft Corporation in the United States. therefore. Notices 285 . serviceability. Tivoli.com/legal/us/) The following terms are trademarks of International Business Machines Corporation in the United States. other countries. other countries. and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States.ibm. must include a copyright notice as follows: © (your company name) (year). or function of these programs. visit the IBM Terms of Use Web site (http://www. _enter the year or years_. All rights reserved. other countries.platform for which the sample programs are written. Each copy or any portion of these sample programs or any derivative work. UNIX is a registered trademark of The Open Group in the United States and other countries. Inc. other countries. the Tivoli logo. Linux is a trademark of Linus Torvalds in the United States. Sample Programs. in the United States and other countries. and service names may be trademarks or service marks of others. cannot guarantee or imply reliability. Trademarks For trademark attribution. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems. Other company. Portions of this code are derived from IBM Corp. the Intel logo. product. IBM. or both. the photographs and color illustrations may not appear. © Copyright IBM Corp. the Windows logo. or both. If you are viewing this information softcopy. Windows. or both. or both.

286 Installation Guide: .

212. 43 Process solution packages before installing 203 installation logs 205 installing 204 overview 203 3 I Installation language pack 201 Maximo Asset Management 65.2010 287 . 211. 8. 88 middleware installer workspace 49 overview 44 post installation tasks 209. 214.x 125 Deployment environments clustered environment 3 distributed environment 3 stand-alone environment 3 O Oracle manual configuration. 140 manual configuration. 9i 139 P Planning Maximo Asset Management Preparation Maximo Asset Management installation 19 prerequisite 51 Prerequisites procedures 42.Index Numerics 220829 237 middleware 51 Middleware 49 auto-configuration 7 installer logs 63. 2007 . 210. 9. 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. 10g 136 manual configuration. 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.2 130. 182 middleware installer logs 63.

288 Installation Guide: .

.

Printed in USA .