MAM71 Manual Install Whitepaper

Installing and Configuring MAM 7.
1 Component by Component
White Paper
Armen Pischdotchian, Stephen Hochstetler
April 2008
Copyright Notice
Copyright © 2008 IBM Corporation, including this documentation and all software. All rights
reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Soft-
ware License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any computer language, in any form or by any means, electronic, mechanical,
magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corpora-
tion. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any
machine-readable documentation for your own use, provided that each such reproduction shall carry
the IBM Corporation copyright notice. No other rights under copyright are granted without prior writ-
ten permission of IBM Corporation. The document is not intended for production and is furnished “as
is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the
warranties of merchantability and fitness for a particular purpose.
Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or
disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.
Trademarks
The following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site,
NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Den-
mark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in
the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.
Lotus is a registered trademark of Lotus Development Corporation.
PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or
both and is used by IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the
United States, other countries, or both.
SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For fur-
ther information, see http://www.setco.org/aboutmark.html.
Other company, product, and service names may be trademarks or service marks of others.
Notices
References in this publication to Tivoli Systems or IBM products, programs, or services do not imply
that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to
these products, programs, or services is not intended to imply that only Tivoli Systems or IBM prod-
ucts, programs, or services can be used. Subject to valid intellectual property or other legally pro-
tectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can
be used instead of the referenced product, program, or service. The evaluation and verification of
operation in conjunction with other products, except those expressly designated by Tivoli Systems or
IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent
applications covering subject matter in this document. The furnishing of this document does not give
you any license to these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.
Printed in Ireland.
Table of Contents
Introduction
About This Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IV
White Paper
Installing DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Creating an Operating System User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Obtaining the DB2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Creating the DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Binding the DB2 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Obtaining the IBM WebSphere Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Installing the WAS Network Deployment 6.1.0.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installing the IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Backing Up Deployment Manager and Custom Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installing the WebSphere Update Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Starting the WebSphere Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Creating the MAM 7.1 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Obtaining the Maximo Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installing MAM 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Running Maxinst Against DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Building the EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Deploying the EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Deploying the MAXIMO and MAXIMOHELP EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Accessing the MAM 7.1 Start Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Conclusion
Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
•
•
• I
•
•
Table of Contents
•
•
II • Installing and Configuring MAM 7.1 Component by Component ©Copyright IBM Corp. 2008
•
•
Introduction
About This Paper

This white paper serves as a comprehensive installation guide for Maximo Asset Manager
7.1 (MAM). It is different from other IBM® product installation guides in the following
ways:
• It does not use the middleware installation program. This installation requires
manual installation and configuration, which instills a greater understanding of
the events that occur behind the scenes. The middleware installation program is a
powerful tool enabling you to install multiple independent-vendor and IBM
programs. It also takes advantage of numerous scripts to configure connectivity
settings, create users, populate the database with records, and so forth.
This white paper uncovers the underlying activities that the middleware installer
performs, enabling you to manually install and configure each component as
required.
• It is a lite installation. The installation uses the minimum software requirements

and programs to install a full-fledged enterprise application, in this case, MAM
7.1. In this paper you do not install LDAP, Rational® Agent Controller, or the
embedded security server (ESS).
• You install the MAM beta code from the build tree. You do not have a
convenient executable program or an installation wizard to install MAM 7.1. You
must copy and paste or extract the build tree structure onto your local drive. Then
you can begin editing and configuring files in the same way an installation wizard
would execute.
• It is a flexible installation. You can install another application server, such as

BEA WebLogic, along with WebSphere® and point MAM (maximo.properties
file) to another application server. You can also create other database instances
and, by changing certain parameters in the MAM installation files, you can use a
new database instance.
This type of an installation also gives you the flexibility to remove a specific build
of MAM driver and replace it with another driver or build (or version). At a
minimum, you might need to run a new script to update the database (maxinst).
Or, you can remove the MAM root installation folder and unzip a new one in its
place.
• You can use MAM before eGA. Why wait for a product to become available to
the general public so that you can use it too? By uncovering the activities of the
•
•
• III
•
•
Introduction
middleware installer, you can begin demonstrating or creating lab exercises from
a stable beta code. You get a head start in test-driving a product before it is
released.
Audience
The audience for this white paper includes IBM professional services personnel or any IBM
employee who would like to install, demonstrate, and use MAM 7.1.
•
•
IV • Installing and Configuring MAM 7.1 Component by Component ©Copyright IBM Corp. 2008
•
•
White Paper
This white paper describes in detail how to complete the following installation and
configuration tasks:
• Installing DB2®
• Installing IBM WebSphere Application Server
• Creating the MAM 7.1 AppServer
• Installing MAM 7.1
• Deploying the EAR files and accessing the Start Center
This white paper does not provide information on where you can gain access to the required
software. In some cases, it will make recommendations. For the most part, you are
responsible for obtaining the required software. As a general approach, if you have access
to the CCMDB or MAM middleware installer folder, you can then use the individual
executable programs from the appropriate folder. These programs are under the /windows
folder of the middleware installation root folder.
1 Installing DB2
In this section, you complete the following tasks:
• Create an operating system user account with Local Administrative privileges.
• Install DB2 Version 9.
• Apply the DB2 Development license file.
• Create the DB2 database to host MAM 7.1.
• Bind the DB2 schema to prepare for data.
1.1 Creating an Operating System User Account

DB2 requires user accounts to be operating system user accounts. This document suggests
that you create a MAXIMO account (user name) on your system.
•
•
• 1
•
•
White Paper
1. From the Control Panel, navigate to Administrative Tools > Computer

Management.
2. Click and open the Local Users and Groups folder and open the Users subfolder.
3. Right-click the Users subfolder and select New User.
4. Enter maximo for the user name and maximodb2 for the password.
5. To add MAXIMO to the Administrators group, complete the following steps:
a. Open the Groups folder.
b. Select the Administrator Group name and right-click it.
c. Click Add to Group.
d. Select the MAXIMO user and click Add.
6. Click OK and close any related dialog box.
It is common practice to log out of the system as the user that you had logged in as earlier
(as yourself), log back in as user maximo and password maximodb2, and then complete
the DB2 installation steps. This is not necessary. However, later in the installation when
you select Authorities from the DB2 Control Center to Grant All permissions to
Maximo, you will not see the user MAXIMO in the DB2 panel. You will see
Administrator and db2admin. This is okay. You can easily add the user MAXIMO at that
time to the list (it already exists in the operating system level) and grant privileges.
1.2 Obtaining the DB2 Software

You are not using the middleware installer program to complete the MAM 7.1 installation.
However, you still need the individual installation programs that reside under the
/windows folder of the /middleware root installation folder.
After you gain access to a CCMDB or MAM middleware installation directory, you can
begin installing DB2 Version 9.
•
•
2 • Installing and Configuring MAM 7.1 Component by Component ©Copyright IBM Corp. 2008
•
•
White Paper
1. From the DB2-ESE_9.1.0 folder, click

DB2_Enterprise_Svr_Ed_Windows_x86.exe.
2. From the Information Management Software window, click Install Now.
3. Click Next in the Welcome window.
4. Accept the license agreement and click Next.
5. Select Typical as your installation type and click Next.
6. Select the third option, Install DB2 Enterprise Edition on this computer and
save the settings in a response file. Select a location on your local drive and click
Next.
7. Remove Program Files from the suggested directory, leaving c:\IBM\SQLLIB

as your root installation directory, and click Next.
8. Accept the user name db2admin in the Set user information dialog box.
a. Specify maximodb2 as the password and confirm it.
b. Select the Use the same user name and password for the remaining DB2
services check box.
c. Click Next.
For the purposes of this installation, the same password is used for all settings.
You can choose a different approach.
9. Click Next in the Configure DB2 instances dialog box. Alternatively, you can
click Configure and select startup type Manual. You can also change this setting
from the Windows Services panel.
10. Accept defaults in the Prepare the DB2 tools catalog and click Next.
11. Click Next in the Set up notifications dialog box (with the notifications box
cleared).
12. Check the Enable operating systems security option and click Next.
13. Click Finish. The progress bar is displayed.
14. In the Setup is complete dialog box, clear the Automatically Launch the
installation of Visual Studio check box. Click Finish. Click Exit to close the
First Steps Launchpad.
You are now ready to apply the license file.
•
•
©Copyright IBM Corp. 2008 Installing and Configuring MAM 7.1 Component by Component • 3
•
•
White Paper
15. You have access to the middleware installation programs, so open the
middleware/windows/DB2-ESE_9.1.0 folder and extract the DB2-
Enterp_Srv_CPU_Activation.zip file to a temporary location. The file you will
need is db2ese_c.lic.
16. Launch the DB2 Control Center by right-clicking the DB2 system tray icon and
selecting DB2 Control Center.
17. When the Control Center View dialog box opens, select Advanced and then
clear the Show this window at startup time check box. Click OK to continue.
18. From the Tools menu of the Control Center, select License Center.
19. Select your system from the drop-down box on the left labeled System name.
20. From the drop-down box on the right, make sure that DB2 Enterprise Server
Edition is displayed.
21. From the License menu, select Add.
22. Browse to the location where you copied the db2ese_c.lic file and click OK. The
permanent license for DB2 Enterprise Edition will be applied.
23. At this point you can start your DB2 server by right-clicking the DB2 system tray
icon and selecting Start (DB2). You will notice that the red square on the icon will
disappear when the database engine is started.
•
•
•
•
White Paper
1.3 Creating the DB2 Database

To create a local directory to hold the DB2 tablespace files and index files, complete the
following steps:
1. For the purposes of this exercise, create the directory c:\db2data.
2. Launch the DB2 Control Center by right-clicking the DB2 system tray icon and
selecting DB2 Control Center.
3. From the All Systems folder, expand the plus (+) signs to go down the chain until
you see the Databases folder, which is currently empty.
4. Select the Databases folder. From the Tools menu of the Control Center, select
Command Editor.
•
•
•
•
White Paper
5. Type or paste the following SQL code into the top pane of the Command Editor tool to create
a database named UDB01.
CREATE DATABASE UDB01 ON C: ALIAS UDB01 WITH "UDB01 Database";

CONNECT TO UDB01;
UPDATE DB CFG FOR UDB01 USING AUTO_MAINT ON;
UPDATE DB CFG FOR UDB01 USING AUTO_TBL_MAINT ON;
UPDATE DB CFG FOR UDB01 USING AUTO_RUNSTATS ON;
UPDATE DB CFG FOR UDB01 USING AUTO_REORG ON;
UPDATE DB CFG FOR UDB01 USING AUTO_DB_BACKUP ON;
UPDATE ALERT CFG FOR DATABASE ON UDB01 USING db.db_backup_req SET
THRESHOLDSCHECKED YES;
UPDATE ALERT CFG FOR DATABASE ON UDB01 USING db.tb_reorg_req SET
UPDATE ALERT CFG FOR DATABASE ON UDB01 USING db.tb_runstats_req SET
CONNECT TO UDB01;
GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,
IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON
DATABASE TO USER DB2ADMIN;
CREATE BUFFERPOOL UDB01BUFFERPOOL IMMEDIATE SIZE 4096 PAGESIZE 32 K ;
CREATE REGULAR TABLESPACE UDB01 PAGESIZE 32 K MANAGED BY SYSTEM
USING ('c:\db2data\UDB01\tablespace' ) EXTENTSIZE 16 OVERHEAD 10.67
PREFETCHSIZE 16 TRANSFERRATE 0.04 BUFFERPOOL UDB01BUFFERPOOL
DROPPED TABLE RECOVERY OFF;
GRANT USE OF TABLESPACE UDB01 TO USER DB2ADMIN WITH GRANT OPTION;
CREATE SCHEMA MAXIMO AUTHORIZATION maximodb2;
CREATE SYSTEM TEMPORARY TABLESPACE UDB01SYSTEMP PAGESIZE 32 K
MANAGED BY SYSTEM USING ('c:\db2data\UDB01\systemp' ) EXTENTSIZE 8
OVERHEAD 10.67 PREFETCHSIZE 8 TRANSFERRATE 0.04 BUFFERPOOL
UDB01BUFFERPOOL ;
UPDATE DATABASE CONFIGURATION USING APPLHEAPSZ 1024 DEFERRED ;
UPDATE DATABASE CONFIGURATION USING LOGSECOND 3 IMMEDIATE ;
UPDATE DATABASE CONFIGURATION USING LOGFILSIZ 4096 DEFERRED ;
UPDATE DATABASE CONFIGURATION USING APP_CTL_HEAP_SZ 1024 DEFERRED ;
UPDATE DATABASE CONFIGURATION USING LOCKLIST 30000 IMMEDIATE ;
UPDATE DATABASE CONFIGURATION USING MAXLOCKS 75 IMMEDIATE;
CONNECT RESET;
•
•
•
•
White Paper
maximodb2
6. Click the green triangle on the Commands tool bar to execute the query. This
process will take from 2 to 5 minutes to complete, depending on the performance
capabilities of your hardware.
7. When the database creation process is completed, Exit the Command Editor.
8. Refresh the Control Center view and expand the All Systems folder. Drill down to
the Databases folder.
9. Right-click the UDB01 database and select Stop to stop the database
(acknowledge the warning dialog box).
10. Click Start to restart the database.
11. Right-click the UDB01 database and select Authorities.
If you performed this installation logged in as MAXIMO, then you should see two
users in the list: DB2ADMIN and MAXIMO. This is confirmation that your
database was created and configured successfully. Minimize the DB2 Control
Center.
If you performed the installation logged in as yourself, then you must add the user
MAXIMO, which already exists as an operating system level user.
a. From the Database Authorities dialog box, click Add User.

•
•
•
•
White Paper
b. Select MAXIMO and click OK.
c. Highlight the MAXIMO user and click Grant All.
1.4 Binding the DB2 Schema

To optimize DB2 for interaction with Maximo®, you tune it using configuration
parameters. Before tuning it, you must bind the database, which formats DB2 metadata and
structures the database with a security access template. Complete the following DB2 bind
procedures against the DB2 database that you plan to connect to Maximo.
1. Launch a Windows Command Prompt and enter the following commands:
cd \IBM\SQLLIB\BND
set DB2DBDFT=UDB01
db2cmd db2 connect to UDB01
2. The DB2 command-line processor tool is launched. Enter the following

commands:
db2 bind db2schema.bnd

db2 bind @db2cli.lst clipkg 4
•
•
•
•
White Paper
When these commands are completed, your database is ready for you to begin the
maxinst process. You will perform this process toward the end of this white paper.
•
•
•
•
White Paper
2 Installing IBM WebSphere

• Install WebSphere 6.1 (the main Network Deployment).
• Verify the installation of the Deployment Manager.
• Create the custom profile.
• Install the HTTP Server and Plug-in.
• Back up the Deployment Manager and custom profile.
• Install the WebSphere Update Installer.
• Apply the WebSphere 6.1 Fix Pack 9.
• Start WebSphere 6.1.0.9.
2.1 Obtaining the IBM WebSphere Software

The WAS installation program is in the WS-WAS_ND_6.1.0.9_Custom_ISCAE71
folder.
After you gain access to a CCMDB or MAM middleware installation directory, you can
begin installing DB2 Version 9.
From the middleware/windows/WS-WAS_ND_6.1.0.9_Custom_ISCAE71 folder,

extract the WAS-ND_WindowsIA32_Custom_v6109.zip file to a temporary location.
Note: The main Network Deployment is already patched up to Fix Pack 9. Later, you will
only need to apply the fix pack to the HTTP program and the plug-in.
•
•
•
•
White Paper
2.2 Installing the WAS Network Deployment 6.1.0.9

To install the WAS Network Deployment program, complete the following steps:
1. From the WAS folder, click Install.exe.
2. Click Next in the Welcome window.
4. Remove Program Files from the default installation path and click Next.
5. Select Deployment Manager and click Next.
6. Clear the Enable administrative security check box and click Next.
7. Click Next in the Installation Summary window.
8. Click Finish.
The First Steps window opens. Use this window to verify the deployment.
9. Click the Installation verification link.
When the process is completed successfully, close the child window.
10. From the First Steps screen, click Profile Management Tool and click Next.
•
•
•
•
White Paper
11. Select Custom Profile as the Environment and click Next.
12. Click Advanced profile creation and click Next.
13. Accept default values in the Profile Name and Location (if Program Files exists
in the default profile directory, remove it). Select the Make this profile the
default check box. Click Next.
14. Verify that the host name is correct and click Next.
15. Accept default values in the Federation dialog box and click Next.
16. Review the assigned port numbers and click Next.
17. Click Create.
18. In the Profile Creation Complete dialog box, clear all check boxes and click
Next.
2.3 Installing the IBM HTTP Server

You can install the HTTP Server from the WAS Application Server Launchpad window.
1. Click the IBM HTTP Server Installation link from the left pane of the
launchpad.
•
•
•
•
White Paper
3. If you get a Systems prerequisites error check, ignore the message and click
Next.
4. Remove the Program Files from the default installation location and click Next.
5. Accept the assigned port values and click Next.
6. Select both check boxes to run the IBM HTTP Server and the Administration
as a Windows service. Also select the Log on as a local system account option.
Click Next.
7. Clear the Create a user ID check box and click Next.
8. Accept defaults to install the IBM HTTP server Plug-in and click Next.
9. Click Next in the Installation Summary dialog box.
2.4 Backing Up Deployment Manager and Custom Profiles

Back up the profiles before applying the fix pack. This action also stops the profile
processes that are running, which is necessary before you apply the fix packs. Complete the
following steps:
1. Launch a Windows Command Prompt and change directory:
C:\IBM\WebSphere\AppServer\profiles\Custom01\bin
2. Type the following command to back up the Node Agent (Custom01) profile:
backupConfig.bat
•
•
•
•
White Paper
The process for backing up the profile will stop any AppServer that is started,
along with the Node Manager for this profile. You can observe the process of the
batch file in the Command Prompt window. A message is displayed when the
process is complete.
Perform the same backup process for the Dmgr01 profile.
3. Change directory to:
C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
4. Type the following command:
backupConfig.bat
When the backupConfig.bat process is completed for the Dmgr01 profile, you can close
the Command Prompt window.
2.5 Installing the WebSphere Update Installer

The IBM WebSphere 6.1 Fix Pack requires that you use the appropriate version of the IBM
Installer. If you use an earlier version of the Update Installer program, software prerequisite
check failures might occur.
1. Launch the WS-WAS_UpdateInstaller_6.1.0_FP9 from the Windows folder of

the middleware installer.
2. If the Program Files default path appears, remove it.
3. Leave the Launch IBM Update Installer selected to launch the Update Installer
on exit. Click Finish.
•
•
•
•
White Paper
Typically there are four required fix packs: WAS Network Deployment, WAS
SDK, the HTTP Server, and the plug-in. If you are using the software provided
with the middleware installer program, you need to apply only two fix packs: the
HTTP Server and the plug-in. The WAS ND and the Java™ SDK are already
updated.
The two fix packs that you must apply
The Update Installer
4. Create a directory on your C:\ drive named c:\updinstsource.
5. Extract the contents of the

\WS-WAS_UpdateInstaller_6.1.0_FP9\download.updii.6109.windows.ia32.zip
file into this newly created directory.
6. Click install.exe from the UpdateInstaller folder.
7. From the Welcome window, click Next.
If you did not have access to the fix pack, use the relevant links from the Welcome
window to launch the Maintenance Download Wizard page from IBM. Follow the
online directions to download the required fix packs.
•
•
•
•
White Paper
8. From the Directory Path drop-down list in the Product Selection window, select
the HTTP Server (the AppServer is already updated).
9. Click Install maintenance package and then click Next.
10. Select c:\IBM\WebSphere\UpdateInstaller\maintenance and click Next.
11. Select the available packages and click Next.
•
•
•
•
White Paper
12. When the HTTP Server installation is complete, click the Relaunch button to start
the process over again. Follow the same steps to update the HTTP Plug-in.
2.6 Starting the WebSphere Services

From a Windows® Command Prompt, start the Deployment Manager and the Node
Manager. Use the following table to locate and start the services.
Server Name Browse to... To Start, type... To Stop, type...
IBM WebSphere \IBM\WebSphere\AppServer\ startManager stopManager

Deployment Mgr profiles\Dmgr01\bin
IBM WebSphere \IBM\WebSphere\AppServer\ startNode stopNode

Node Agent profiles\Custom01\bin
•
•
•
•
White Paper
3 Creating the MAM 7.1 Application Server

• Create a new application server named MAM71.
• Create a new Web container transport chain.
• Configure JVM settings.
• Create new virtual hosts.
Use the WebSphere console to complete the following steps:
1. Invoke a browser window (preferably from the machine where you have installed
Maximo). Open the Administrative console by typing
http://<machine_name>:9060/admin in the browser address bar.
This URL address uses the default port number (9060) and context (admin) for the
Administrative console.
2. Enter any user name to log in, or just press Enter.
3. Expand the Servers link and click Application servers.
4. Click New.
5. Type MAM71 (or specify a unique server name) and click Next.
6. Accept the defaults in Step 2 and click Next.
7. Accept the defaults in Step 3 and click Next.
8. Click Finish to confirm the new server.
9. Before you save the new application, click Preferences from the Messages
window. The goal is to synchronize changes with nodes.
You synchronize changes with nodes when you have one Deployment Manager
and multiple application server custom profiles. For example, if you have
WebSphere spread over four machines, you would have one Deployment Manager
and four custom profiles. If you make a change and select Synchronize changes
with Nodes, the change will be replicated out to all of the profiles.
•
•
•
•
White Paper
10. Select Synchronize changes with Nodes, click Apply, and then click Save.
11. Click OK when the save is complete.
12. Click the Servers >> Application Servers link on the left pane.
13. Click MAM71 in the middle pane.

•
•
•
•
White Paper
14. Under Container settings, expand Web Container Settings, then click Web
container transport chains.
15. Click New.
16. In Step 1 of the Select transport chain template, type MAM71TRANSPORT and
click Next.
17. In Step 2, specify Port name as MAM71, Host as * (asterisk), and Port as 9999.
Click Next.
18. In Step 3, click Finish.
•
•
•
•
White Paper
19. Click Save.
20. Click OK.
21. Click the Application servers link in the left pane.
22. Click MAM71.
23. Under the Server Infrastructure section, expand Java and Process
Management.
24. Click Process Definition.
25. Under the Additional Properties section, click Java Virtual Machine.
26. Specify the following settings.
Parameter name Enter this value...
Initial heap size 512
Maximum heap size 1024
Generic Java (or JVM) -Dsun.rmi.dgc.ackTimeout=10000

arguments –Djava.net.preferIPv4Stack=true
•
•
•
•
White Paper
There are no line breaks in the Generic Java argument settings. There is a space
after the 10000, followed by the dash (-) and so forth.
The value of this property represents the length of time (in milliseconds) that the
server-side RMI runtime will strongly refer to a remote object (or a reference to a
remote object). This elapsed time is returned from the current virtual machine as
part of the result of a remote method call. The time stops when it receives positive
acknowledgment from the client that the remote reference has been fully received
and processed. This time-out only applies to failure situations in which the client
fails to send the acknowledgment. Setting the value too low can increase the risk
of a remote object being prematurely garbage collected when the only known
reference to the remote object is the one in transit as part of the remote method
call result. The maximum value is Long.MAX_VALUE. The default value is 300
000 (5 minutes).
The second argument tells WebSphere to use the IPv4 stack as the default, rather
than both the IPv4 and the IPv6 stacks.
27. Click OK and then click Save.
28. Click OK to return to the main Administrative console.
29. In the left pane, expand Environment and then click Virtual Hosts.
30. Click New.
31. Type MAM71SERVER as the virtual host name, and click OK.
32. Click MAM71SERVER from the main Virtual Hosts pane.
33. From Additional Properties, click Host Aliases.
•
•
•
•
White Paper
34. Click New to create the first host alias.
35. Accept the default values (Host Name: * and Port: 80) and click OK.
36. Click New again to create a second host alias.
37. Change the port number to 9999 and then click OK.
Later in this paper, you will use port number 9999 in your browser to connect to
the MAM71 application.
38. Click Save to save these changes.
The first alias is usually the port that the IBM HTTP Server is running on. The
second one is for the Web container port.
You have completed your middleware installation and configuration manually, without
using the scripts that are available to the middleware installer.
In the next section you will install MAM71 (or Maximo).
•
•
•
•
White Paper
4 Installing Maximo
A notable feature of this installation is that you install Maximo or MAM71 without using
an installation program or a wizard. You can use this method to install any beta code of
Maximo onto existing middleware (which includes all the installation activities that you
have undertaken so far) before the Maximo program becomes available. This method also
reveals all the files that are edited and configured automatically by the middleware
program.
In this section you complete the following tasks:
• Extract or copy the installation directory to your local drive.
• Apply the non-expiring development license file to the product.
• Edit the properties file (maximo.properties) that is typically configured by the

installation wizard.
• Create new virtual hosts.
• Run the maxinst program to populate the database.
• Build the EAR files.
4.1 Obtaining the Maximo Installation Files

The build tree for Maximo 7.1 was obtained from the following location:
\\pokgsa.ibm.com\projects\m\maximodev\Builds\Harrier-
EAM\EAM-052b.20080502
If you have an account on GSA, you can use the IBM GSA mapper to connect to the
projects folder, where the “gold” eGA MAM71 (TPAP 7.1.1) build/driver resides.
•
•
•
•
White Paper
1. Navigate to the following location to obtain the MAM71 build files:
\\pokgsa.ibm.com\projects\m\maximodev\Builds\Harrier-
EAM\EAM-052b.20080502
2. Copy the Harrier.085.src.PATCH.052b.zip to a temporary location on the

computer where you are installing MAM71.
You must also copy the en.zip files (help files) to a temporary location
3. Navigate to the following location (one directory up) to obtain the Help files:
\\pokgsa.ibm.com\projects\m\maximodev\Builds\Harrier-EAM\
4. Copy the en.zip to a temporary location on the computer where you are installing
MAM71.
You are now ready to extract these zip files; a step that is performed by the launchpad
program.
4.2 Installing MAM 7.1

1. Create a root Maximo installation folder on your local drive (c:\).
2. Extract the Harrier.085.src.PATCH.052b.zip file into the c:\Maximo folder. If

you were to install this from the launchpad executable using the middleware
installer, the default installation location would be c:\IBM\SMP.
Typically, intermediate builds or drivers may require that you provide the license
file. You do not have to complete the following steps in this exercise, but it is
good to know where the license file resides and the required steps to enable it.
a. Navigate to the following location:
c:\maximo\applications\maximo\businessobjects\classes\
psdi\app\signature
b. Create a folder named apps under the signature folder (you are mimicking
what the installation scripts would accomplish).
c. Copy the ForInternalUseOnly.class file to the apps folder.
3. You must now obtain the Help files. Navigate to the following location:
c:\Maximo\applications\maximohelp\helpweb\webmodule
4. Extract the en.zip file inside the webmodule folder.
•
•
•
•
White Paper
5. Navigate to the following location:
c:\Maximo\applications\maximo\properties
6. With your text editor, open the maximo.properties file.
7. Edit the maximo.properties file as follows:
a. Remove the comment (//) tags from the DB2 connectivity parameter:
mxe.db.driver=com.ibm.db2.jcc.DB2Driver
b. Place the comment tags in front of both the Oracle connectivity string and the
Oracle thin driver:
•
•
•
•
White Paper
//mxe.db.driver=oracle.jdbc.driver.OracleDriver
//mxe.db.url=jdbc:oracle:thin:
c. Remove the comment tags and modify the DB2 connectivity string to reflect
the correct port and database instance name:
mxe.db.url=jdbc:db2://localhost:50000/UDB01
d. Change the database login password to maximodb2:
mxe.db.password=maximodb2
– This password must match the password that you specified in the Database
SQL command in Step 5. on page 6.
e. Add the following two lines:
mxe.db.systemdateformat=current timestamp
mxe.db.format.nullvalue=COALESCE
Remove comment tags (//) from this line.
Comment out this line.
Remove comment tags and specify the

DB2 JDBC connect string.
Comment out this line.
maximodb2 Specify the correct password.
Add these two lines.
8. Save and close the maximo.properties file.
•
•
•
•
White Paper
4.3 Running Maxinst Against DB2

You create the Maximo database by running maxinst, which populates DB2 with the
specific database objects Maximo requires. To do so, complete the following steps:
1. Open a command prompt.
2. Change directory path to \maximo\tools\maximo.
Ensure that you are using the correct MAM71 root installation directory.
c:\maximo is just an example used in these exercises.
3. Launch maxinst using the –t parameter (to specify tablespace) and the –s
parameter (to specify index storage area).
Maxinst –tUDB01 –sUDB01
This process will take approximately 30 minutes.
By default, Maximo reads the maximo.properties file (in this example,

c:\Maximo\applications\maximo\properties) for connectivity information to the
database. It connects using a JDBC connection and then creates a Maxdemo database. To
create an empty database, use the -imaximo -sUDB01 -tUDB01 flag.
For example, at the command prompt, instead of typing maxinst, type maxinst -imaximo.
The following screen capture shows a successful maxinst.
•
•
•
•
White Paper
4.4 Building the EAR Files

The middleware installer is responsible for running the batch files that create or build the
resulting EAR files. There are four batch files; each is responsible for building the
corresponding EAR files. The c:\Maximo\deployment folder lists these batch files, which
are described in the following table.
Batch File Description
Contains WAR, JAR, and EJB files. It is responsible

buildmaximoear.cmd for building the entire enterprise application
(Maximo).
Contains mostly HTML and style sheet files and is
buildhelpear.cmd
responsible for building the help files.
Builds the EAR file responsible for creating an
buildbocrystalwar integration between Maximo and a custom Crystal
Report Environment.
•
•
•
•
White Paper
Batch File Description
The new acweb.ear that was in Maximo Version 6.

buildportalear.cmd This is the Actuate Integration file that allows Actuate
reports to work in Version 7.
This file is used if you have multiple JVM instances; it
buildmiregwar.cmd allows a common RMI bind, which is useful if running
a cluster.
For the purposes of this exercise, you will build only the Maximo and the Maximo Help
EAR files.
1. From a Windows Command Prompt, change directory to \Maximo\deployment.
2. At the prompt, type buildmaximoear. After the maximo.ear file is built, type
buildhelpear.
Ignore the message that the tools.jar file was not found. It is of no consequence.
Note the newly built EAR files in the c:\Maximo\deployment\default directory.
In the next section you will deploy these EAR files using the IBM WebSphere
Administrative Console.
•
•
•
•
White Paper
5 Deploying the EAR Files

In this section you will complete the following tasks:
• Deploy maximo.ear.
• Deploy maximohelp.ear.
• Access the MAM 7.1 Start Center.
5.1 Deploying the MAXIMO and MAXIMOHELP EAR Files

1. From the WAS console, click Applications > Install New Application.
2. Browse to C:\Maximo\deployment\default. Both EAR files are displayed.
3. Select maximo.ear (order does not matter). Click Next.
4. From the Select Installation Options panel, accept the default values and click
Next.
5. From the Map modules to servers panel, select all four entries (only one of you
are working with the help EAR files) and click Next.
•
•
•
•
White Paper
6. From the Map virtual hosts for Web modules panel, select all three entries (just
one for the help EAR file).
7. Select MAM71SERVER from the Virtual host drop-down list.
•
•
•
•
White Paper
8. Click Finish to install the maximo.ear file.
9. Wait for the successful deployment message and then click Save.
10. Repeat these steps for the maximohelp.ear file.
11. From a Windows Command Prompt, start the node agent for WebSphere:
(\IBM\WebSphere\AppServer\profiles\Custom01\bin\startNode).
The ND Manager is a Windows service. It is running at this time.
To run the node agent as a Windows service, see the “Conclusion” section of this
white paper.
12. Return to the WebSphere Admin console.
13. From the Servers section, open the Application servers link.
14. Select the MAM71 (check box) and click Start. After 1 minute or so, the Status
icon will change from an X to an arrow.
•
•
•
•
White Paper
15. From the Applications section, open the Enterprise applications link. Note that
both the MAXIMO and the MAXIMOHELP applications are displaying green
arrows for their status icon.
If either or both of them are displaying an X status, start each application

individually from the Enterprise Applications link. See the “Conclusion” section
of this paper for troubleshooting tips.
•
•
•
•
White Paper
5.2 Accessing the MAM 7.1 Start Center

1. Open a new browser window.
2. For the URL, type http://<machine_name>:9999/maximo and press Enter.
3. Log in as user wilson with password wilson.
The Maximo Workflow Designer requires a Java runtime environment™ (JRE™) 1.5.
You can obtain JRE 1.5 from the following Web site:
http://java.sun.com/javase/downloads/index_jdk5.jsp
•
•
•
•
White Paper
•
•
•
•
Conclusion
The conclusion of this white paper is that by installing MAM 7.1 component by component,
you gain greater control over installation types and levels of configuration. You can also
adopt a modular approach to installing MAM 7.1. With a modular approach, you can
replace components and still be able to maintain the success of your application
deployments.
The following section provides troubleshooting tips.
Troubleshooting Tips
When Checking Database Authorities, the user MAXIMO does not appear on the
User tab.
Even if you added the user MAXIMO before installing Maximo as an operating system
level user, you might not have carried out the installation by logging out and logging back
in as MAXIMO.
You are likely to see the User Administrator and DB2ADMIN.
You can add the user MAXIMO from the Add User dialog box from the Database
Authorities panel.
I have applied my developers license file (db2ese.lic), but the License Center
information page says “License not Registered.”
Generally this is not an issue. Adding the license takes only a few seconds. If the system
seems hung, click Close in the Progress box. Apply the license again and you will see a
message that the license has been applied (added) successfully.
The SQL command that I ran in the DB2 Command Editor did not complete
successfully.
Ensure that the following parameters are set properly:
Create schema maximo authorization maximodb2
The default script that you can obtain is usually set to maximo. Change it to maximodb2.
•
•
• 37
•
•
Conclusion
How do I connect to the Maximo database from DB2?
1. Open the Command Editor from the DB2 Tools menu and type the following
statement:
connect to UDB01 user maximo using maximodb2
2. Click the green triangle in the top left corner to execute the command.
I applied the fix pack, but the Admin console displays Version 6.1.0, not 6.1.0.9.
It is important that you stop all WebSphere services, particularly the node agent
(stopNode.bat) and the ND Manager (stopManager.bat).
Running backupConfig.bat after creating your profile automatically stops all services.
The installation program does not provide for a Windows service for the node agent (it does
for the Managed Server).
How do I create a Windows service for the node agent?
1. Open a command prompt.
2. Change directory to \IBM\WebSphere\AppServer\bin.
3. Type the following case-sensitive command with no line breaks:
WASService -add NodeAgent -serverName nodeagent -profilePath

"C:\IBM\WebSphere\AppServer\profiles\Custom01" -wasHome
"C:\IBM\WebSphere\AppServer" -logRoot
"C:\IBM\WebSphere\AppServer\profiles\Custom01\logs\nodeagent" -
LogFile
"C:\IBM\WebSphere\AppServer\profiles\Custom01\logs\nodeagent\start
Server.log"
-restart true
The AppServer (MAM71) has started, but the Maximo application does not start.
Start the Maximo application from the Admin console. If it does not start, look for a
detailed error message in the following location:
C:\IBM\WebSphere\AppServer\profiles\Custom01\logs\nodeagent
If you are working on a laptop and you connect from your home and the office, ensure that
the hosts file C:\WINDOWS\system32\drivers\etc includes the same qualified IP used in
your ipconfig settings. See the following example.
•
•
•
•
Conclusion
Matches your ipconfig output
My Maxinst process failed.
Maxinst does not provide a default value for tablespace. The -S and the -T parameters are
required. You must always specify the data and index tablespace names. There is no default
value.
If maxinst fails for any reason, you must drop and re-create the Maximo schema before
rerunning maxinst.
Each flag must be followed by the parameters without a space, for example: -uMAXIMO
-sUDB01 -tUDB01.
If you encounter problems during the maxinst process, review the command prompt
window where you invoked maxinst. Errors there appear as a Java stack trace that can aid
in the troubleshooting process.
To research the stack-trace errors, inspect the maxinsttimestamp.log file in the

c:<Maximo\tools\maximo\log directory.
Note: The file, which contains output for each operation performed by the maxinst.bat file,
might be very large (up to 80 MB if the error occurred late in the maxinst process).
Therefore, you should use a text editor other than Notepad to open the file.
How is DB2 similar to and different from Oracle and Microsoft® SQL?
DB2 is similar to both Oracle and Microsoft SQL Server® in many ways, and different as
well. For example:
• DB2 Instance = Microsoft SQL Server “server”
• DB2 Instance <> Oracle Instance (totally different)
• DB2 Database = Microsoft SQL Server “database”
• DB2 Database = Oracle “user”
• For Maximo, a DB2 database is the container, similar to Microsoft SQL Server
• DB2 Control Center = Microsoft SQL Server Management Studio = Oracle

Enterprise Manager
• The command-line tool for DB2 is DB2CMD. For Oracle it is SQL*Plus. For
Microsoft SQL Server it is ISQL.
•
•
•
•
Conclusion
• DB2 uses OS security for its users and groups, similar to Microsoft SQL Server
“Integrated” security mode.
Resources
This installation was performed by actually doing it from scratch and consulting developers
when needed. No existing reference was used to accomplish this task.
•
•
•
•

MAM71 Manual Install Whitepaper

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MAM71 Manual Install Whitepaper

Caricato da

Copyright:

Formati disponibili

Installing and Configuring MAM 7.

About This Paper

• It is a lite installation. The installation uses the minimum software requirements

• It is a flexible installation. You can install another application server, such as

• Installing IBM WebSphere Application Server

• Creating the MAM 7.1 AppServer

• Installing MAM 7.1

• Deploying the EAR files and accessing the Start Center

• Create an operating system user account with Local Administrative privileges.

• Install DB2 Version 9.

• Apply the DB2 Development license file.

• Create the DB2 database to host MAM 7.1.

• Bind the DB2 schema to prepare for data.

1.1 Creating an Operating System User Account

1. From the Control Panel, navigate to Administrative Tools > Computer

3. Right-click the Users subfolder and select New User.

5. To add MAXIMO to the Administrators group, complete the following steps:

a. Open the Groups folder.

b. Select the Administrator Group name and right-click it.

c. Click Add to Group.

d. Select the MAXIMO user and click Add.

6. Click OK and close any related dialog box.

1.2 Obtaining the DB2 Software

1. From the DB2-ESE_9.1.0 folder, click

2. From the Information Management Software window, click Install Now.

3. Click Next in the Welcome window.

4. Accept the license agreement and click Next.

5. Select Typical as your installation type and click Next.

7. Remove Program Files from the suggested directory, leaving c:\IBM\SQLLIB

a. Specify maximodb2 as the password and confirm it.

13. Click Finish. The progress bar is displayed.

You are now ready to apply the license file.

21. From the License menu, select Add.

1.3 Creating the DB2 Database

1. For the purposes of this exercise, create the directory c:\db2data.

CREATE DATABASE UDB01 ON C: ALIAS UDB01 WITH "UDB01 Database";

10. Click Start to restart the database.

11. Right-click the UDB01 database and select Authorities.

a. From the Database Authorities dialog box, click Add User.

b. Select MAXIMO and click OK.

c. Highlight the MAXIMO user and click Grant All.

1.4 Binding the DB2 Schema

1. Launch a Windows Command Prompt and enter the following commands:

2. The DB2 command-line processor tool is launched. Enter the following

db2 bind db2schema.bnd

2 Installing IBM WebSphere

• Install WebSphere 6.1 (the main Network Deployment).

• Verify the installation of the Deployment Manager.

• Create the custom profile.

• Install the HTTP Server and Plug-in.

• Back up the Deployment Manager and custom profile.

• Install the WebSphere Update Installer.

• Apply the WebSphere 6.1 Fix Pack 9.

• Start WebSphere 6.1.0.9.

2.1 Obtaining the IBM WebSphere Software

From the middleware/windows/WS-WAS_ND_6.1.0.9_Custom_ISCAE71 folder,

2.2 Installing the WAS Network Deployment 6.1.0.9

1. From the WAS folder, click Install.exe.

2. Click Next in the Welcome window.

3. Accept the license agreement and click Next.

5. Select Deployment Manager and click Next.

7. Click Next in the Installation Summary window.

9. Click the Installation verification link.