61 mx install was60 win

8/12/2019 61 Mx Install Was60 Win

1/168

Installation GuideAugust 2006

MaximoRelease 6.1

Microsoft Windows | IBM WebSphere


2/168

This document and its publication do not constitute or create a contract. MRO Software, Inc. makes no warranties, express or

implied, as to the accuracy or completeness of this document or with respect to the related software.

2006 MRO Software, Inc. All rights reserved. This document contains confidential and trade secret information of MRO Software,

Inc. Use, transfer, disclosure, or copying without MRO Software, Inc.s express written permission is strictly forbidden.

Patents: United States Patent Nos. 6,324,522 B2, 6,519,588 B1, and Aust. Pat. No. 758001. Multiple foreign patents pending.

U.S. Restricted Rights: If Customer is a government agency, this constitutes notice that the Licensed Software is provided with

RESTRICTED RIGHTS. Subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at 252.227-7013 of

the Department of Defense FAR Supplement and FAR clause 52.227-19 entitled Commercial Computer Software Restricted Rights,

apply and use, duplication, or disclosure by the Government is subject to restrictions as set forth in the applicable license

agreement. The aforementioned restrictions shall prevail over any similar Rights provisions under the laws of any country.

Contractor/Manufacturer: MRO Software, Inc., 100 Crosby Drive, Bedford, MA 01730.

Trademarks: Maximo is a registered trademark, and MRO Software and MXES are trademarks, of MRO Software, Inc. The

following table contains a list of MRO Softwares other trademarks and service marks:

IBM and WebSphere are registered trademarks of IBM Corporation. BEA WEBLOGIC SERVER is a registered trademark of

BEA Systems, Inc. webMethods is a registered trademark of webMethods, Inc. Snowbound and RasterMaster are trademarks

of Snowbound Software Corporation. Syclo and Agentry are registered trademarks of Syclo, LLC.

Other products and brand names are trademarks or registered trademarks of their respective companies.

Third-Party Technology: Certain MRO Software, Inc. products contain technology provided under license from third parties, as

noted in the following table:

Open Source: Maximo contains computer software obtained from the public domain, known as Open Source. A complete listing of

all Open Source contained in Maximo may be viewed at http://www.mro.com/support/opensource ownership of which is attributed as

follows: Portions 2005, International Business Machines Corporation and others. Portions 2002, Steve Souza([email protected]). Portions 2000 by Jef Poskanzer ([email protected]). Portions 2000-2004 Jason Hunter & Brett

McLaughlin. Portions 2004-2005, The Apache Software Foundation (http://www.apache.org/).

MaximoEnterprise

MaximoEnterprise ITAM

MaximoService Desk

MaximoDiscovery

Maximo

NavigatorMaximoCalibration

MaximoSLA Manager

MaximoChange Manager

MaximoProject Manager

MaximoContract and Procurement Manager

MaximoIncident and Problem Manager

Maximo

OCS

SM

MaximoFusion

MaximoEnterprise Adapter

MaximoMobile Suite

MaximoMobile Auditor

MaximoMobile Inventory Manager

MaximoMobile Work Manager

Maximo

Mobile CalibrationMXESTMMobile Suite

MaximoMobile for Work Management

MaximoMobile for Inventory Management

MRO Software Products Third-Party Information

Maximo Portions 1995-2004 Actuate Corporation. Portions 2005 BEA Systems, Inc. BEA

WebLogic Serverprovided by BEA Systems, Inc. Portions 1996-2005 IBM

Corporation. All Right Reserved.

Portions 1996-2005,i-net software GmbH. J-Integra for COMv2.4 2004

Intrinsyc Software International, Inc.

All Products Portions 1996-2003 Visual Mining, Inc. Visual Mining NetCharts Server

provided by Visual Mining, Inc.

Maximo Discovery 1998-2005 Centennial Software Limited. MSDE Copyright Microsoft Corporation.

Maximo Navigator Portions 1993-2002 Snowbound Software Corporation. RasterMaster Raster

imaging technology provided by Snowbound Software Corporation. Portions 1991

Pegasus Imaging Corp.

Maximo Mobile Suite Portions 1996-2005 Syclo, LLC.

MXES Mobile Suite Portions 2005 DataMirror, Inc. Portions 2000-2005 Zaval Creative Engineering

Group.


3/168

Maximo 6, 08/2006 iii

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Why Read This Guide?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Who Should Read This Guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Notation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1: Introducing Maximo 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Overview of Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Internet Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Overview of Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

How Does Maximo Run in an Application Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Single Maximo Application Deployed in a Single Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Maximo Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Actuate Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Typical Maximo Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Hardware and Software Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Third-Party Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Java Virtual Machine (JVM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Chapter 2: Installing IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Installing the IBM WebSphere Application Server Network Deployment. . . . . . . . . . . . . . . . . . . . . . . .2-1

Creating the Deployment Manager Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Creating a Custom Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Installing the IBM HTTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Install the IBM HTTP Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Creating a Web Server Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Installing the IBM Refresh Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

IBM WebSphere Refresh Pack Installation RoadMap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

Install the Core IBM WebSphere Application Server Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

Install the IBM WebSphere Application HTTP Server Patch . . . . . . . . . . . . . . . . . . . . . . . . . .2-30

Install the IBM WebSphere Application HTTP Server Plugin Patch . . . . . . . . . . . . . . . . . . . .2-30

Installing the IBM WebSphere Fix Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32IBM WebSphere Fix Pack Installation RoadMap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

Install the core IBM WebSphere Application Server Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

Install the IBM WebSphere HTTP Server Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Install the IBM WebSphere Application HTTP Server Plugin Patch . . . . . . . . . . . . . . . . . . . .2-34

Install the IBM WebSphere JavaSDK Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Chapter 3: Installing The Actuate Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Pre-Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Oracle Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

MS SQL Server Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installing Actuate8 iServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Contents


4/168

Contents

iv Maximo 6, 08/2006

Chapter 4: Installing The Maximo 6 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Starting the Maximo Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Post Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Chapter 5: Installing The Language Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Chapter 6: Installing The Maximo Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

Chapter 7: Creating the Maximo Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1Preparing Microsoft SQL Server Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Setting up a SQL Server Database for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Preparing Oracle Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Database Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Verifying the Oracle Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Oracle Initialization Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Creating Maximo Tablespace(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Creating the Maximo User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Create the Maximo Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Chapter 8: Creating the Maximo Application Server and Deploying the EAR Files . . . . . . . . . . .8-1

Creating a Windows Service for the Node Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Creating the Maximo Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Editing JVM Memory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Adding a Redirect to IBM WebSphere 6.0.2.11 for Actuate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Identify the HTTP Transfer Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

Creating Virtual Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

Deploying the EAR Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

Chapter 9: Installing The Actuate Encyclopedia for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

Removing Corrupt Characters from the acserverconfig.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Starting the Actuate iServer for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Installing the Actuate Integration for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Importing the Encyclopedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Chapter 10: Logging Into Maximo Start Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Maximo Enterprise Adapter Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Appendix A: System Server Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Starting the Services from the Windows Services Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Starting the Services from a Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Starting the MAXIMO Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix B: Configuring JMS Options for Maximo Enterprise Adapter . . . . . . . . . . . . . . . . . . . . B-1

Adding Servers to the JMS Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Creating the JMS Bus Destination for the Continuous Inbound (cqinbd) Queue . . . . . . . . . . . . . . B-5

Creating the JMS Bus Destination for the Sequential Inbound (sqinbd) Queue . . . . . . . . . . . . . . . B-8Creating the JMS Bus Destination for the Sequential Outbound (sqoutbd) Queue. . . . . . . . . . . . . B-9

Creating the MEA Connection Factory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11

Creating the Continuous Inbound (cqin) JMS Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13

Creating the Sequential Inbound (sqin) JMS Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14

Creating the Sequential Outbound (sqout) JMS Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Creating JMS Activation for the Continuous Inbound Queue (cqin). . . . . . . . . . . . . . . . . . . . . . . . B-15

Appendix C: Adding Additional Maximo Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D: Enabling Reports to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1


5/168

Maximo 6, 08/2006 v

About This Guide

This section briefly summarizes this document and how it can help you as a

Maximo 6 user. It also provides information on other MRO resources available

to you, such as additional documentation and support.

Why Read This Guide?

This guide explains how to install the Maximo 6 system.

Who Should Read This Guide?

The guide is intended for the following people:

Implementation analysts

Support personnel

System administrators

How to Use This Guide

This guide explains prerequisites and procedures for installing Maximo 6.Review all the installation steps in this guide before you begin the installation

process.

Notation Conventions

The following notations have special meaning:

Notation Description

Bold text Denotes a button, check box,or field on a screen

Bulleted procedures Instructions that you can

perform in any sequence

CAUTION Precedes information that, ifignored, can result in loss of

data

NOTE Precedes information ofspecial importance


6/168

Chapter Contents

vi Maximo 6, 08/2006

Chapter Contents

The following table briefly describes each chapter in this document. Read the

chapters in the order they appear and perform the tasks in sequence as

written.

1 Numbered procedures Instructions that you mustperform in the numbered

sequence

> Denotes a navigation path

through menu items. For

example, File > Open

Notation Description

Chapter Name Chapter Contents

Chapter 1:

Introducing Maximo 6

Provides an overview of concepts and installation tasks.

Chapter 2:

Installing IBM WebSphere

Describes how to install the IBM WebSphereapplication

Server.

Chapter 3:

Installing the Actuate Application

Describes how to install the Actuate 8 iServer application.

Chapter 4:

Installing Maximo 6

Describes how to install Maximo 6 and complete certain post

installation tasks.

Chapter 5:

Installing the Language Utilities

Explains how to install language-specific Help files and

database scripts.

Chapter 6:

Installing Maximo Keys

Explains how to access applications that you are entitled to

use determined by your Maximo license purchase.

Chapter 7:

Creating the Maximo Schema

Explains how to prepare an Oracle instance and a Microsoft

SQL server database on the server to hold your data.

Chapter 8:

Creating the MAximo Application

Server and Deploying the EAR Files

Outlines how to create the MAXIMOSERVER Application

server and deploy the EAR files using IBM WebSphereconsole.

Chapter 9:

Installing the Actuate Encyclopedia for

Maximo

Describes how to install the Encyclopedia, which is a

collection of Maximo-specific reports, user profiles, and user

permissions. Also, explains how to import the ActuateEncyclopedia for Maximo

Chapter 10:

Logging Into Maximo Start Center

Describes how to invoke the Maximo Start Center.

Appendix A:

Server System Administration

Explains how to create, start, and stop the Maximo

application server as a MS Windows Service.

Appendix B:

Configuring the JMS Option for Maximo

Enterprise Adapter

Explains how to define JMS components such as Queues for

the MEA application.


7/168

About This Guide

Maximo 6, 08/2006 vii

Related Documentation

You can find more information regarding the Maximo Enterprise Adapter for

SAP R/3 in the following documents:.

Support

MRO Software, Inc. users with a valid Annual Customer Support Plan (ACSP)

can obtain product support online at

http://support.mro.com.

The Support Web site includes information about product releases, software

patches, and documentation updates. To find the most current version of a

document, refer to the Support Web sites Knowledge Base.

Appendix C:

Adding Additional Maximo Keys

Explains how to configure additional Maximo package files

that you may have purchased.

Appendix D:

Enabling Reports to run

Explains how to enable additional Actuate functionalities to

run Reports properly.

Chapter Name Chapter Contents

Document Description

Maximo online help Provides step by step

procedures for every action in

Maximo.

Maximo System

AdministratorsGuide

Explains how to customize the

system, manage the database,

set up accounting features of

the general ledger, and use

Maximo utilities.

MaximoUsers Guide Provides an overview of

Maximo features, and

describes relationships among

modules.


8/168

Support

viii Maximo 6, 08/2006


9/168

Maximo 6, 08/2006 1-1

Maximo 6 is a comprehensive suite of products all built on a single, common

platform. It combines enhanced Enterprise Asset Management functionality

with new service management capabilities that together improve the

effectiveness of asset management strategies.

Maximo 6 includes advanced IT asset management, service management, and

a full-featured service desk, all based on the IT Infrastructure Library (ITIL)

guidelines. Each product can be implemented separately as a stand-alone

solution or readily deployed together. The solution enhances asset

management and ensures service performance of production, facility,

transportation and IT assets.

Maximo 6 consists of multiple software servers that you can either install on

separate server machines or the same physical server. MRO Software

recommends the following dedicated servers: Application Server, ActuateReport Server and Database Server.

Overview of Installation

Use this guide to install Maximo 6. During this process you will complete the

following tasks in the order that they appear:

1 Install IBM WebSphere application server

2 Install the Actuate application server

3 Install Maximo 6

4 Install the language utilities program

5 Install the Maximo Keys (or packages)

6 Create the Maximo schema

7 Deploy the Enterprise Application Archive (EAR) files

Introducing Maximo 6

1

Maximo MaximoEnterprise

ximoDiscovery

ximo Service Center

ximo Asset Center

ximo Enterprise IT


10/168

Internet Connectivity

1-2 Maximo 6, 08/2006

8 Install the Actuate Encyclopedia for Maximo

9 Log into the Maximo Start Center

The following diagram illustrates the software components and the order in

which you must install these components to obtain a successful Maximo

system installation:

Internet Connectivity

The installation of Maximo and its various components require a valid and

active connection to the Internet. MRO Software stronglyrecommends that

you allow the online update of the MAXIMO Application Server to becompleted.

Overview of Concepts

Maximo applicationrefers to an instance of Maximo. Enterprise Application

Archive (EAR) files define what constitutes a Maximo application. You can

have multiple Maximo applications, in other words, multiple deployed EAR

files on one application server.

An EAR file represents a Java 2 Enterprise Edition (J2EE) application thatyou deploy in an application server. EAR files are standard Java archive files

and have the file extension .ear.

An EAR file can consist of: Web Application Archive (WAR) files that contain for example, JSP or

HTML pages

Java Enterprise Application (JAR) files that contain class files and other

programming code modules

Enterprise Java Bean (EJB) files that contain class files

Install IBM WebSphere

Configure the Maximo Application ServerInstall the Actuate 8

iServer application

Install the Maximo

Enterprise Suite

Install the Language

Utilities

Install Maximo Keys

(EAR files are builtDeploy the EAR

files

Install the Actuate

Encyclopedia for

Chapter 2 Chapter 3 Chapter 4

Chapter 5Chapter 6Chapter 8Chapter 9

Maximo

Log into Maximo Start Center

Chapter 10

at this time)

Perform post-installation tasks


11/168

Chapter 1: Introducing Maximo 6

Maximo 6, 08/2006 1-3

MRO Software uses the termapplication serverto refer to a J2EE container

that provides the infrastructure to run business applications such as Maximo.

IBM WebSphere is a commercial application server supported by Maximo.

When you install Maximo, you create a newapplication server (in the

container sense) for the Maximo application iteration within IBM WebSphere.

MRO Software refers to an application server running Maximo as the

Application Server(initial capital letters).

Contextis the name through which you access a specific web application, such

as Maximo deployed on an Application Server. Maximo 6 has the following

contexts:

/maximo Maximo user interface

/mbo Maximo business objects

/maximohelp Maximo help

/acweb Actuate

/meaweb Maximo Enterprise Adapter

You access Maximo from the browser using the /maximo context.

For example, http://:/maximo. The character

string maximo that appears after the port number, is the Maximo context.

How Does Maximo Run in an Application Server?

The following points summarize how Maximo is set up to run in an application

server:

The EAR files are created from the contents placed on your local drive as

part of the installation process The Maximo application consists of the following EAR files:

maximo.ear for the Maximo application

maximohelp.ear for the Maximo Help application

acweb.ear for the MRO Actuate Active Portal Integration

application

In order to run Maximo, you must deploy the Maximo application EAR

files in the application server.

When Maximo application EAR files are deployed in the Application

Server, the server maintains a copy of the EAR files internally.

The Maximo installation builds the EAR files based on the information

you provided during the installation. Any configuration changes require

you to rebuild and redeploy the EAR files.


12/168

Single Maximo Application Deployed in a Single Application Server

1-4 Maximo 6, 08/2006

Single Maximo Application Deployed in a SingleApplication Server

You use your application server software to deploythe EAR files that the

Maximo installation program builds. All three EAR filesmaximo.ear,

maximohelp.ear, acweb.ear, comprise a single Maximo application

(MAXIMOSERVER).

After you deploy the EAR files, a copy of each EAR file is saved in the

application server software folder structure. The application server uses this

copy when running and does not access the EAR files from the Maximo root

folder.

The following diagram depicts the Application Server MAXIMOSERVER

running Maximo in IBM WebSphere on a single physical machine

JSP Technology Maximo applications use JSP technology. An application server, such as theIBM WebSphere server, is used for accepting HTTP requests from client

programs (web browsers) and for responding in HTML content.

When a client requests a JSP page, the application server processes the JSP

page, and the web server sends the result of the JSP page in HTML content

back to the client. Refer to the

http://java.sun.com/products/jsp/ index.html link for more information about

JSP Technology.

XML Technology Maximo applications uses XML files to render the layout and creation of theuser interface.

EJB Technology EJB technology enables rapid and simplified development of distributed,transactional, secure and portable applications based on Java technology.

Additional Information If you have an active Annual Customer Service Plan (ACSP) agreement withMRO Software, you can access the Support Online Web site: http://

support.mro.com

The Support Web site includes information on product releases, software

patches, and documentation updates. To find the most current version of a

document, refer to the Support Web sites Knowledge Base.

To create a Support Online user account, you will need your MRO Software

product serial number.

WAR files

JAR files

EJB Files

WAR files

WAR files

JAR files

maximohelp.ear

acweb.ear

maximo.ear

The Maximo installation program

builds the necessary EAR files

MAXIMOSERVER

The deployed EAR files are now

accessed by IBM WebSphereDatabase

Actuate iServer
http://java.sun.com/products/jsp/%20index.htmlhttp://java.sun.com/products/jsp/%20index.htmlhttp://java.sun.com/products/jsp/%20index.htmlhttp://java.sun.com/products/jsp/%20index.htmlhttp://java.sun.com/products/jsp/%20index.htmlhttp://support.mro.com/http://support.mro.com/http://support.mro.com/http://support.mro.com/http://java.sun.com/products/jsp/%20index.html


13/168


Maximo 6, 08/2006 1-5

Maximo Components

The following section describes the server components in a typical Maximo

environment.

Application Server

Maximo is built using J2EE (Java 2 Enterprise Edition) technology, which

requires using a commercial application server. Maximo uses IBM WebSphere

6.0 as its application server.

The Application Server consists of Maximo Applications using JavaServer

Pages (JSP), XML, and Maximo application specific business components.

The Maximo Application also installs the Active Portal, which enables you to

use the Web to access reports in your Encyclopedia volume and the

Management Console. This web-based capability further enables you to

deploy and test reports on an Encyclopedia volume. You access reports by

using a Web browser (Internet Explorer) to access the Encyclopedia volume

through Active Portal.

Actuate Server

As part of Maximo, Actuate is offered as the embedded reporting tool.

Actuates Information Delivery Solution enables you to create, manage, and

deliver interactive, actionable content.

However, it is your option whether or not to use Actuate as your Maximo

Reporting tool. As you perform the Maximo installation (Chapter 4), if you do

not choose to use Actuate, you simply skip the Actuate references and

continue completing the Maximo installation program.

If you do choose to use Actuate, MRO Software recommends that you install

the Actuate iServer on a separate server on the network. It generates and

manages report documents and provides:

A server-based system to generate, manage, and deliver interactive,

actionable electronic reports

Information in multiple formats including DHTML, PDF, XLS

Open security folder integration to leverage existing e-business platformsecurity service

Database Server

Maximo Release 6.0 for IBM WebSphere supports:

Oracle 9.2.0.6 (9i), or 10.1.0.3 (Standard or Enterprise Edition)

Microsoft SQL Server 2000 SP3


14/168

Typical Maximo Configuration Diagram

1-6 Maximo 6, 08/2006

Typical Maximo Configuration Diagram

The following diagram depicts a typical Maximo configuration

Hardware and Software Considerations

For best performance, MRO Software recommends the following

configuration:

Dedicated Application Server

Dedicated Actuate Server

Dedicated Database Server

Factors affecting server configuration requirements are:

Maximo applications deployed

Number of connecting client workstations

Desired performance level

Doug is sending me a diagram

6.0

Maximo 6 end userInternet Explorer 6.0 Browser

Maximo 6

BEA WebLogic 8.1.4

Administration Workstation

UBDC or SQL Plus

telnet ftp


15/168


Maximo 6, 08/2006 1-7

Table 1 lists hardware and software recommendations (server andworkstation)

For additional tuning and configuration information, refer to the Maximo

System Administrators Guide.

Dedicated Servers Hardware Software

Application

Server: where you

install IBM

WebSphere

24 dedicated, Intel-based

processors

2GB RAM per processor

1.5GB of disk space

Microsoft Windows 2000 Server

Microsoft Server 2003

IBM WebSphere 6.0.2.11

Database Server: Refer to vendor specifications 9.2.0.6, 10.1.0.3, or 10.2.0.1 server

software (either Oracle Standard or

Enterprise)

MS SQL Server 2000 SP3

Actuate iServer:

the server you plan to

use for generating

reports

12 dedicated, Intel-based

processors

1GB RAM per processor

610MB of disk space

Microsoft Windows 2000 Server

Microsoft Server 2003

Actuate 8 iServer

Database client software:

Oracle Client Software (Oracle JDBC

drivers, SQL*Plus, Oracle

Networking) MS SQL Server 2000 Client (ODBC)

Administrative

Workstation

where you install

Maximo

Used for application

building, workflow

designer, Application

designer, and other

high-level functions

Intel-based Pentium

processor

512 MB RAM

SVGA 1024 x 768 resolution;

if used for Application

Designer 1280 x 1024

resolution

Microsoft Windows 2000/XP Professional

Internet Explorer 6.0

Maximo 6

Client Workstation Intel-based Pentium

processor

512 MB RAM

SVGA 1024 x 768 resolution

Microsoft Windows 2000/XP Professional

Internet Explorer 6.0


16/168

Hardware and Software Considerations

1-8 Maximo 6, 08/2006

Third-Party Product Updates

MRO Software supports Maximo with later product updates as they are

released by third-party vendors. Our policy is to validate products with the

latest third-party product updates at time of release certification. MRO

Software has certified the following third-party product updates:

Windows 2000 Server/Advanced Server Service Pack 4

Windows XP Professional Service Pack 2

Windows 2000 Professional Service Pack 4

Internet Explorer 6.0: Service Pack 1

IBM WebSphere 6.0.2.11

Oracle 10.2.0.1 (Oracle Standard or Enterprise)



Microsoft SQL Server 2000: SP3

Java Virtual Machine (JVM)

The Maximo 6 automatic update program used in the product installation,

requiresthat a Java Virtual Machine (JVM) to be installed and present on

the Maximo server. If no JVM is present, the install appears to start and the

load scroll bar climbs to 100% but the install does not launch. A tested JVM

can be downloaded from http://java.sun.com/products/archive/j2se/1.4.2_07/index.html. Once the JVM is installed, continue with the automatic update

process.
http://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.htmlhttp://java.sun.com/products/archive/j2se/1.4.2_07/index.html


17/168

Maximo 6, 08/2006 2-1

Installing IBM WebSphere 6.0.2.11 requires you to perform the following

tasks:

Install the IBM WebSphere Network Deployment (ND) product.

Create a Deployment Manager, and Custom Profile.

Install the IBM HTTP Server.

Install the Web server Plug-in for WebSphere Application Server.

Install the Refresh Pack for the application server, HTTP server, and the

Plugins.

Install the fix Pack for the application server, HTTP Server, the Plugins,

and the Java JDK.

In summary, in this chapter, you perform 11 installations from three CD-

ROMs.

Installing the IBM WebSphere Application Server

Network Deployment

Network Deployment (ND) can create deployment managers that provide

centralized administration of managed Application Server nodes and custom

nodes as a single cell. The deployment manager provides basic clustering and

caching support, including failover support and work balancing. For more

information about these capabilities, refer the Maximo Systems

Administrators Guide (SAG) included on your documentation CD-ROM.

You must log on as a member of the administrator group to install the product

successfully. Some steps of the installation on a Microsoft Windows platform

require the administrator group user to have the following advanced user

rights:

Act as part of the operating system

Log on as a service

For best performance, MRO Software recommends installing WebSphere

Application Server on a dedicated application server

To install IBM WebSphere 6.0.2.11, complete the following steps:

1 Log in to Windows as Administrator or a user with administrative rights.

Installing IBM WebSphere

2


18/168

Installing the IBM WebSphere Application Server Network Deployment

2-2 Maximo 6, 08/2006

2 Insert the CD for theWebSphere 6.0 Application Server Windowsinthe CD drive. If the installation does not start, double-click

launchpad.bat.

3 Click Launch the installation wizard for WebSphere ApplicationServer linkfrom the Launchpad window.

Leave this window open you will refer back to it to install the IBM

HTTP Server later in this chapter.

4 Click Nextin the Welcome dialog box.


19/168

Chapter 2: Installing IBM WebSphere

Maximo 6, 08/2006 2-3

5 Select the I accept the terms in the license agreement option. ClickNext.

6 Click Nextafter the system check completes..


20/168


2-4 Maximo 6, 08/2006

7 Change the installation location by removing the Program Filesdirectory. The default installation location is \Program

Files\IBM\WebSphere\AppServer. Click Next.

Important Spaces (such as the one in \Program Files) are not supported in the nameof the installation directory.

8 CleartheApplication Server Samplesand Javadocs check boxes.Click Next.

For better performance, do not install the Samples. By omitting the

Samples, you can improve application server startup time by 60 percent

and save 15 percent of disk space.

remove \Program Files

c:\WebSphere\Appserver

c:\IBMHttpServer


21/168


Maximo 6, 08/2006 2-5

9 Click Nextin the Installation summary dialog box.

Allow for all components to install.

10 Select the Launch the Profile creation wizardcheck box. Click Next.

c:\WebSphere\Appserver

c:\IBMHttpServer


22/168


2-6 Maximo 6, 08/2006

Creating the Deployment Manager Profile

The deployment manager provides centralized administration of managed

Application Server nodes and custom nodes as a single cell. The deployment

manager provides basic clustering and caching support, including failover

support and workload balancing.


2 Select the create a deployment manageroption. Click Next.


23/168


Maximo 6, 08/2006 2-7

3 Accept the default value or specify a Profile name. Click Next.

4 Accept the default installation location. Click Next.

5 Accept the default values or specify the Node name, Host name, andCell name. Click Next.


24/168


2-8 Maximo 6, 08/2006

6 Review the assigned port numbers. Click Next. Note the Administrativeport number. You will use this context when invoking the Console via a

browser (unless you specify another port number later in this chapter and

Chapter 8).

7 Select the Run the Application Server as a Windows service and logon as a local system account. Click Next.


25/168


Maximo 6, 08/2006 2-9

8 Click Nextin the Profile summary dialog box.

9 Select the Launch the First steps consoleoption. Click Finish.

10 Click the Installation verificationlink.


26/168


2-10 Maximo 6, 08/2006

11 After Installation Verification completes, close the output window.

12 Use the launchpad command and click the Profile creation wizard toopen the First Steps window (if not open already) .

You now can create a custom profile.


27/168


Maximo 6, 08/2006 2-11

Creating a Custom Profile

A custom node is an empty node until you add it to the deployment manager

cell for customization. Use the administrative console of the deployment

manager to create servers and clusters on the custom managed node. Consider

the custom node as a production-ready shell, ready for customization to

contain your production-level servers and applications.


2 Select Create a custom profile. Click Next.


28/168


2-12 Maximo 6, 08/2006

3 Accept the default values or specify the appropriate information. ClickNext.

4 Specify a unique Profile name and select the Make this profile thedefaultcheck box. Click Next.


29/168


Maximo 6, 08/2006 2-13

5 Accept the default directory path. Click Next.

6 Specify a unique node name and the computer name (or IP address) of the

machine where you are performing this installation. Click Next.

7 Review the port number listings. Click Next.


30/168


2-14 Maximo 6, 08/2006

8 Click Nextin the Profile summary dialog box.

9 Select the Launch the First steps consolecheck box. Click Finish.


31/168


Maximo 6, 08/2006 2-15

10 Click Exit. If another First steps window is open, close it.

Leave the Launchpad window open. You will need it in the next section.


32/168

Installing the IBM HTTP Server

2-16 Maximo 6, 08/2006


After you install the IBM WebSphere ND Application Server product, you

must install the IBM HTTP Server.

Install the IBM HTTP Server, on the same machine as the application server.

It provides a more robust Web server environment. Also, this type of

installation supports rigorous testing environment or production

environments that do not require a firewall.

To install the IBM HTTP Server on the same machine where you have

installed the Network Deployment product, complete the following steps:

1 From the Launchpad ND window open on your desktop, click Launch theinstallation wizard for IBM HTTP Server.

2 Click Next in the Welcome dialog box.


33/168


Maximo 6, 08/2006 2-17

3 Accept the license terms. Click Next.

4 Change the installation location by removing the Program Files

directory and the spaces in the IBM HTTP Server folder name. The defaultinstallation location is \Program Files\IBM HTTP Server. Click Next.

remove \Program Files

and remove the spaces

inIBM HTTP Server


34/168


2-18 Maximo 6, 08/2006

5 Select Typical. Click Next.

6 Select the following check boxes and options:

a Run IBM HTTP Server as a Windows Service.

b Run IBM HTTP Administration as a Windows Service.

c the Log on as Local system accountoption.

d Automaticas the Startup Typefrom the drop-down list.

7 Click Next.

username


35/168


Maximo 6, 08/2006 2-19

8 Click Nextin the summary dialog box.

9 Click Next.


36/168


2-20 Maximo 6, 08/2006

10 Ensure that the Launch the WebSphere Application Server Plugin Installcheck box is checked and click Finish.

The Plug-in installation wizard for version 6 opens. Continue with the

following section.


37/168


Maximo 6, 08/2006 2-21

Install the IBM HTTP Server Plug-in

After you install the IBM HTTP Server, you must install a binary module for

the Web server to enable it to communicate with WebSphere application

Server products. The Plugin software configures a new element in the

application server configuration called a Web server definition. You can then

manage application for the Web server using the administrative console.

To install the Plug-in, complete the following steps

1 Clearboth check boxes in the Welcome dialog box. Click Next.

2 Accept the License terms. Click Next.


38/168


2-22 Maximo 6, 08/2006

3 Click Nextin the System prerequisites check dialog box.

4 Select the IBM HTTP Server V6option. Click Next.

5 Select theWebSphere Application Server machine (local)option.Click Next.


39/168


Maximo 6, 08/2006 2-23

6 Change installation location by removing the Program Filesdirectory.The default installation location is \Program

Files\IBM\WebSphere\Plugins. Click Next.

7 Accept the default installation location as it appears(:\IBM\WebSphere\AppServer). Click Next.


40/168


2-24 Maximo 6, 08/2006

8 The Wizard does not default to the location of the httpd.conffile. Youmust click the Browsebutton to select the following location:

:\IBM HTTP Server\conf\httpd.conf

Accept the default Web server port number: 80. Click Next.

9 Accept the default name or specify a unique sever definition name. ClickNext.

C:\IBMHTTPSERVER\conf\httpd.conf


41/168


Maximo 6, 08/2006 2-25

10 Accept the default location of the plugin-cfg.xmlfile as it appears. ClickNext.

11 Click Next.

12 Click Next.

This is an example path


42/168


2-26 Maximo 6, 08/2006

13 Click Next.

14 Click Finish.

in step 15.


43/168


Maximo 6, 08/2006 2-27

Creating a Web Server Definition

You must now complete the plug-in installation by creating a Web server

definition.

1 Open a command prompt window.

2 Change directory to \IBM\WebSphere\Plugins\bin.

3 At the prompt, type configurewebserver1.bat.

4 Allow for the process to complete and close the command prompt window.

5 Close the command prompt, the Launchpad window, the IE session, andall other IBM-related windows that are open at this time.

6 Ensure to stop all IBM-related processes at this time:

See System Server Administration on page A-1.

Process name... How to stop it...

IBM WebSphere Application

Server V6 - Deployment Manager

From the Services panel, select the IBM Deployment Manager

service name, right click, and stopit.

Node Agent From a command prompt, change directory to:

C:\IBM\WebSphere\AppServer\profiles\Custom01\bin\ and run

stopNode.bat.


44/168

Installing the IBM Refresh Pack

2-28 Maximo 6, 08/2006


You use the IBM Refresh Pack CD to update IBM WebSphere 6.0.0.x software

to release 6.0.2. (This is an interim step to updating to release 6.0.2.11, which

is required with Maximo 6.1 software.)

To update to IBM WebSphere 6.0.2, you perform preparation steps, copy and

extract a platform-specific file from the Refresh Pack CD-ROM to the required

directory, run an executable file, and use the Install Wizard. You repeat this

process for each of the three Refresh-Pack files (listed below) needed for your

platform. Once completed, this process updates the core WebSphere

Application Server, the HTTP Server, and the HTTP Server Plugins to release

6.0.2.

Summary of IBM WebSphere Refresh Pack Files

IBM WebSphere Refresh Pack Installation RoadMap

Perform all Refresh Pack installation tasks in the order that they appear in

the following roadmap.

NOTE Do not start any of the IBM WebShpere services until you have completedall the steps in this chapter.

1 Install the Core IBM WebSphere Application Server Patch.

2 Install the IBM WebSphere Application HTTP Server.

3 Install the IBM WebSphere Application HTTP Server Plugin.

Install the Core IBM WebSphere Application Server Patch

To install the core IBM WebSphere Application Server Patch (6.0.2), completethe following steps:

1 Stop all IBM WebSphere Application Servers and HTTP Servers, ifrunning.

2 Insert the IBM WebSphere Refresh Pack CD-ROM.

3 From a command prompt, change directory to\AppServer\profiles\Dmgr01\bin .

4 Run the backupConfig.batfile.

The Files that You Extract from the IBMWebSphere Refresh Pack CD-ROM

The Directory where You unzipthe Refresh Pack Files

The Executable file thatYou Run

6.0-WS-WAS-WinX32-RP0000002.zip IBM\WebSphere\AppServer update.exe

6.0-WS-WASIHS-WinX32-RP0000002.zip IBMHTTPServer update.exe

6.0-WS-WASPlugIn-WinX32-

RP0000002.zip

IBM\WebSphere\Plugins update.exe


45/168


Maximo 6, 08/2006 2-29

5 From a command prompt, change directory to\AppServer\profiles\Custom01\bin .


7 Delete the updateinstallerfolder, if present, from the\IBM\WebSphere\AppServer directory.

8 Extract the 6.0-WS-WAS-WinX32-RP0000002.zip file into the:\IBM\WebSphere\AppServer directory.

NOTE The files unpack into an updateinstallerdirectory that is automatically

created in the AppServer directory during the extraction process.

9 Change directory to:\IBM\WebSphere\AppServer\updateinstaller.

10 Double click the update.exefile.

11 Click Nextin the IBM Update Installer for WebSphere Software Welcome

dialog box.

12 Accept the default installation location as it appears and click Next.

13 Select Install maintenance packageand click Next.

14 Accept the default path of the maintenance package and click Next.

15 Click Nextto copy the JDK. Allow for the JDK-copying process tocomplete.

16 Click Relaunchonce the JDK is completely loaded to relaunch the

Wizard.


18 Accept the default path of the maintenance package to install and clickNext.

19 Click Nextto begin the installation.

20 Allow the prereq.jdk component to finish copying.

21 Read the Wizard panel text to verify successful installation of 6.0.2.0 and

then click Finish. The Refresh Pack (6.0.2) Core Application Server Patchinstallation process is complete.

Now proceed to the next section to install the Refresh Pack for IBM

WebSphere HTTP Server Patch (6.0.2).


46/168


2-30 Maximo 6, 08/2006

Install the IBM WebSphere Application HTTP Server Patch

To install the IBM WebSphere HTTP Server Patch (6.0.2), complete the

following steps:

1 Delete the updateinstallerfolder, if present, from:\IBMHTTPServer.

2 Extract the 6.0-WS-WASIHS-WinX32-RP0000002.zip file into the:\IBMHTTPServerdirectory.

NOTE The files unpack into an updateinstallerdirectory that is automaticallycreated in the IBMHTTPServer directory during the extraction process.

3 Change directory to:\IBMHTTPServer\updateinstaller.


5 Click Nextin the IBM Update Installer for WebSphere Software Welcome

dialog box.



8 Accept the default path to the maintenance package file and click Next.

9 Read the Wizard panel text to verify you are installing the 6.0.2 RefreshPack for the IBM HTTP Server and click Nextto begin the installation.

10 Allow for the JDK-copying process to complete. (The panel displays the

message: Backing up component prereq.ihs.)

11 Read the Wizard panel text to verify successful installation of 6.0.2.0 andthen click Finish. The Refresh Pack (6.0.2) HTTP Server Patch

installation process is complete.

Now proceed to the next section to install the Refresh Pack for IBM

WebSphere Application Server Plugin Patch (6.0.2).

Install the IBM WebSphere Application HTTP Server Plugin Patch

To install the IBM WebSphere Application Server Plugin Patch (6.0.2),

complete the following steps:

1 Delete the updateinstallerfolder, if present, from:\IBM\WebSphere\Plugins.

2 Extract the 6.0-WS-WASPlugIn-WinX32-RP0000002.zip file into the:\\IBM\WebSphere\Pluginsdirectory.

NOTE The files unpack into an updateinstallerdirectory that is automaticallycreated in the Plugins directory during the extraction process.

3 Change directory to

:\IBM\WebSphere\Plugins\updateinstaller.


47/168


Maximo 6, 08/2006 2-31


5 Click Nextin the IBM Update Installer for WebSphere Software Welcomedialog box.




9 Click Nextto copy the JDK. Allow for the JDK-copying process tocomplete.

10 Click Relaunchonce the JDK is completely loaded.



13 Read the Wizard panel text to verify you are installing the 6.0.2.0 RefreshPack for the IBM HTTP Server Plugins patch and click Next to begin the

installation. The file-copying process starts.

14 Allow for the JDK to finish copying. Read the Wizard panel text to verifysuccessful installation of 6.0.2.0 and then click Finish. The Refresh Pack

(6.0.2) HTTP Server Plugin Patch installation process is complete.

NOTE Before you proceed to the fix pack installation procedure in the nextsection, delete all the updateinstallerfolders created in this process.


48/168

Installing the IBM WebSphere Fix Pack

2-32 Maximo 6, 08/2006


You use the IBM WebSphere Fix Pack CD to update IBM WebSphere 6.0.2

software to release 6.0.2.11.

When updating IBM WebSphere from 6.0.0.x, you cannot update directly to

6.0.2.11. You must first install the Refresh Pack to update to 6.0.2, as

described in the previous section.

For the 6.0.2.11 update, you perform preparation steps, copy and extract a

platform-specific file from the Fix-Pack CD to the required directory, run an

executable file, and interface with the Install Wizard, as described in this

section. You repeat this process for each of the four Fix-Pack files (listed

below) needed for your platform. Once completed, this process updates the

core WebSphere Application Server, HTTP Server, HTTP Server Plugins, and

the JavaSDK to release 6.0.2.11.

Summary of IBM WebSphere Fix Pack Files

IBM WebSphere Fix Pack Installation RoadMap

Perform all Fix Pack installation tasks in the exact order that they appear in

the following roadmap.

NOTE Do not start any of the IBM WebShpere services until you have completedall the steps in this chapter.

1 Install the core IBM WebSphere Application Server Patch

2 Install the IBM WebSphere HTTP Server Patch

3 Install the IBM WebSphere Application HTTP Server Plugin Patch

4 Install the IBM WebSphere JavaSDK Patch

Install the core IBM WebSphere Application Server Patch

To install the core IBM WebSphere Fix Pack (6.0.2.11) core Application Server

Patch, complete the following steps:

1 Stop all IBM Application Servers and HTTP Servers, if running.

2 From a command prompt, change directory toIBM\WebSphere\AppServer\profiles\Dmgr01\bin.

The Files that You Extract from the IBM WebSphereFix Pack CD-ROM

The Directory where You unzipthe Fix Pack Files

The Executable filethat You Run

6.0.2-WS-WAS-WinX32-FP0000011.zip IBM\WebSphere\AppServer update.exe

6.0.2-WS-WASIHS-WinX32-FP0000011.zip IBMHTTPServer update.exe

6.0.2-WS-WASPlugIn-WinX32-FP0000011.zip IBM\WebSphere\Plugins update.exe

6.0.2-WS-WASJavaSDK-WinX32-FP0000011.zip IBM\WebSphere\AppServer update.exe


49/168


Maximo 6, 08/2006 2-33


4 From a command prompt, change directory toIBM\WebSphere\AppServer\profiles\Custom01\bin.


6 Delete the updateinstallerfolder, if present, from

IBM\WebSphere\AppServer directory.

7 Extract the 6.0.2-WS-WAS-WinX32-FP0000011.zip file into the:\IBM\WebSphere\AppServer directory.

NOTE The files unpack into an updateinstallerdirectory that is automaticallycreated in the AppServer directory during the extraction process.







14 Read the Wizard panel text to verify that Fix Pack 6.0.2.11 (FP60211) isbeing installed and then click Nextto begin the installation.

15 Allow the JDK-copying process to complete. Read the Wizard panel text toverify successful installation of 6.0.2.11 and then click Finish. The Fix

Pack (6.0.2.11) core Application Server Patch installation process is

complete.

Now proceed to the next section to install the IBM WebSphere Fix Pack

(6.0.2.11) HTTP Server Patch.

Install the IBM WebSphere HTTP Server Patch

To install the IBM WebSphere Fix Pack (6.0.2.11) HTTP Server Patch,

complete the following steps:

1 Delete the updateinstallerfolder, if present, from the\IBM\HTTPServerdirectory.

2 Extract the 6.0.2-WS-WASIHS-WinX32-FP0000011.zip file into the:\IBMHTTPServerdirectory.

NOTE The files unpack into an updateinstallerdirectory that is automaticallycreated in the IBMHTTPServer directory during the extraction process.


50/168


2-34 Maximo 6, 08/2006

3 Change directory to:\IBMHTTPServer\updateinstaller.






9 Read the Wizard panel text to verify that Fix Pack 6.0.2.11 (FP60211) isbeing installed, and then click Nextto begin the installation.The file

copying process starts. (Wizard text reads: Backing up component:

prereq.ihs.)

10 Allow the JDK-copying process to complete. Read the Wizard panel text to

verify successful installation of 6.0.2.11 and then click Finish. The FixPack (6.0.2.11) HTTP Server Patch installation process is complete.

Now proceed to the next section to install the Fix Pack for IBM WebServer Fix

Pack (6.0.2.11) Application Server Plugin Patch.

Install the IBM WebSphere Application HTTP Server Plugin Patch

To install the IBM WebServer Fix Pack (6.0.2.11) Application Server Plugin

Patch, complete the following steps:

1 Delete the updateinstallerfolder, if present, from the

\IBM\WebSphere\Pluginsdirectory.

2 Extract the 6.0.2-WS-WASPlugIn-WinX32-FP0000011.zip file into the:\IBM\WebSphere\Pluginsdirectory.


3 Change directory to:\IBM\WebSphere\Plugins\updateinstaller.







51/168


Maximo 6, 08/2006 2-35

9 Read the Wizard panel text to verify that Fix Pack 6.0.2.11 (FP60211) forthe Plugin is about to be installed and then click Nextto begin the

installation.

10 Allow the file-copying process to complete. Read the Wizard panel text toverify successful installation of Plugin 6.0.2.11 and then click Finish. The

Fix Pack (6.0.2.11) HTTP Server Patch installation process is complete.

Now proceed to the next section to install the IBM WebSphere Fix Pack(6.0.2.11) JavaSDK Patch.

Install the IBM WebSphere JavaSDK Patch

To install the IBM WebSphere Fix Pack (6.0.2.11) JavaSDK Patch, complete

the following steps:

1 Delete the updateinstallerfolder, if present, from the\IBM\WebSphere\AppServerdirectory.

2 Extract the 6.0.2-WS-WASJavaSDK-WinX32-FP0000011.zip file into

the :\IBM\WebSphere\Pluginsdirectory.








9 Read the Wizard panel text to verify that Fix Pack 6.0.2.11 (FP60211) forthe JavaSDK is being installed and then click Nextto begin the

installation.

10 Allow the file-copying process to complete. Read the Wizard panel text to

verify that the JDK successfully copied and click ReLaunch.


12 Accept the default filename of the maintenance package as it appears andclick Next.

13 Read the Wizard panel text to verify that maintenance packageWASJAVASDKFP60211 is being installed and then click Nextto begin

the installation.


52/168


2-36 Maximo 6, 08/2006

14 Allow the file-copying process to complete. (The text reads: Backing upcomponent:prereq:jdk.)

15 Read the Wizard panel text to verify that maintenance packageWASJAVASDKFP60211 is about to be installed and then click Finish.

The fix pack (6.0.2.11) javasdk patch installation process is now complete,

which completes the ibm websphere 6.0.2.11 installation process.

You can now startup the IBM WebSphere and HTTP Servers to verify

successful installation. After which, proceed to the next chapter to install the

Actuate iServer application.


53/168

Maximo 6, 08/2006 3-1

If you are using Actuate for reporting in Maximo, this chapter explains how toinstall the Actuate 8 iServer application. If you are not going to use Actuate,skip to Chapter 4.

Pre-Installation Procedures

The following sections describe the pre-installation procedures.

Oracle Connectivity

You must install the following Oracle Client Software on your Actuate Server

before installing Actuate:

Oracle JDBC Drivers

SQL*Plus

Oracle Networking (in Oracle 9i or 10g)

You must setup and test Oracle Networking connectivity to the Maximo

database.

You must also create a TNS name for your Maximo connect string as you will

need this information in Step 10 on page 4-5.

Please review Oracle installation documentation for further details. Oracle

documentation is available online at

http://otn.oracle.com/documentation/content.html.

MS SQL Server Connectivity

If your Actuate application connects to Microsoft SQL Server, you must install

Microsoft SQL Server client software before installing Actuate.

You must also create a DNS name for your Maximo connect string as you will

need this information in Step 10 on page 4-5.

Install the following products:

Microsoft SQL Server ODBC Drivers

SQL Server Client Network Utility.

Installing The Actuate

Application 3
http://otn.oracle.com/documentation/content.htmlhttp://otn.oracle.com/documentation/content.htmlhttp://otn.oracle.com/documentation/content.htmlhttp://otn.oracle.com/documentation/content.html


54/168

Installing Actuate8 iServer

3-2 Maximo 6, 08/2006


This section describes how to install Actuate 8 iServer. For best performance,

MRO Software recommends installing Actuate iServer on a dedicated server.

1 Log in to Windows as a user with Administrative rights.

2 Insert the Actuate 8 iServer for Windows CD-ROM into the CD drive.From the \iserver folder on your CD double-click the setup.exe.


4 Accept the terms of the License Agreement and clickNext.


55/168

Chapter 3: Installing The Actuate Application

Maximo 6, 08/2006 3-3

5 Select Customand read the following warning before clicking Next.

WARNING Default value for the Destination Folder is \ProgramFiles\Actuate8\iserver; however, you must ensure that the Destination

Folder path does not have any spacesin the path name. For example

c:\Actuate8\iserver. Click Browseto select the new path.

6 Select all components exceptSample Volume and click Next.


56/168


3-4 Maximo 6, 08/2006

7 Select Stand-aloneand click Next.

8 Click the browse button and navigate to the location of the xml file, in thisexample:Actuate_key_18802.xml. This file resides under the root CD

folder on yourActuate Release 8 iServer for WindowsCD-ROM. Click

Next.

d:\Actuate_key_18802.xml


57/168


Maximo 6, 08/2006 3-5

9 Accept the default values that appear in your Locale Information dialogbox and click Next.

10 Enter a user that isin theAdministrator Groupand ensure that bothcheck-boxes in the Services Profile frame are checked. Click Next.

11 Enter the following values in the Server Configuration dialog box.

PMD Configuration. The Process Management Daemon enables you to

perform Administrative tasks within iServer, but does not connect to the

Maximo Encyclopedia Volume.

a The host name or the IP address of the machine where you areinstalling Actuate iServer.


58/168


3-6 Maximo 6, 08/2006

b Accept the default port number 8100.

c iServer Configuration. The iServer Configuration enables you toconnect to the Maximo Encyclopedia Volume.

d The host name or the IP address of the machine where you areinstalling Actuate iServer (same as above).

e Accept the default port number 8000.

f Click Next.

12 Specify a password for your Actuate administrator and click Next.


59/168


Maximo 6, 08/2006 3-7

13 Select Use the default volumeand type the computer name or IPaddress. Click Next.

14 Select Use the Actuate Encyclopedia volumeand click Next.

Actuate

host name host name


60/168


3-8 Maximo 6, 08/2006

15 Enter the computer name where requested and accept the default portnumbers. Click Next.

16 Accept the default HTTP port number (8900), or specify another portnumber and click Next.

You open the Actuate Administrative console via a browser, using this

port number. For example: http://:8900/acadmin


61/168


Maximo 6, 08/2006 3-9

17 Accept the default context path (/acadmin) or specify another contextname and click Next. You open the Actuate Administrative Console via a

browser, using this context.

For example: http://:8900/acadmin

Record the port number and the context path that you created. You will

need these to access the Web-based Actuate Administrative Console in

Step 12 on page 9-10.

The above two steps enable system administrators to access, generate, and

manage reports using Actuates web-based console.

18 Accept the default values for the program folder and click Next.


62/168


3-10 Maximo 6, 08/2006

19 Click Nextin the Summary dialog box.

20 Allow for the installation program to copy all the files.

21 Close the setup.txt file.


63/168


Maximo 6, 08/2006 3-11

22 Uncheck the ReadMe check-box and click Finish.

You are now ready to install Maximo 6.


64/168


3-12 Maximo 6, 08/2006


65/168

Maximo 6, 08/2006 4-1

This chapter explains how to install the Maximo 6 application.

Complete the following worksheet by recording certain names and values that

will help you during installation. The page and step numbers in the right

column of the worksheet indicate where you need the requested information.

Installing The Maximo 6

Application 4

Record the information here... Use the information here...

Maximo-related

Serial number Step 7 on page 4-3

Maximo install folder Step 8 on page 4-4

SMTP host name Step 11 on page 4-5

Work flow administrator email Step 12 on page 4-6

Maximo administrator email Step 12 on page 4-6

Application server name Step 13 on page 4-6

Listen Port number Default is 9080

or specify another: ___________________

You can either use thedefault port number orspecify another. Make a note

of it, you will need thisnumber in Chapter 8.

Database-related

Database server name Step 10 on page 4-5

Database port number Step 10 on page 4-5

Database Name Step 10 on page 4-5

Database/Schema owner Step 10 on page 4-5

Database owner name and

password

Step 10 on page 4-5

Actuate-related

Actuate iServer name Step 16 on page 4-8

iServer port number Step 16 on page 4-8

TNS (Oracle) or DNS (MS SQL

Server) on the Actuate iServer

Step 16 on page 4-8
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


66/168

Starting the Maximo Installation Program

4-2 Maximo 6, 08/2006


You install Maximo onto a Windows workstation designated as the Maximo 6

Administration Workstation. This is where the Enterprise Archive (EAR) files

are built and subsequently deployed to the application server.

You use the Administration Workstation to install program patches, product

upgrades, or just running Configure Database and similar utilities in which

case you must stop the application server from running.

To install the Maximo Application, complete the following steps:

1 Log in to Windows as Administrator or as a user with administrativerights.

2 Insert the Maximo 6 installation CD-ROM into the CD drive.

3 From the root CD drive, double-click maximo60.exe.

4 Select the appropriate language from the drop-down list. If your languageis not available from the list, select English; if it is Japanese or Chinese,

see Note 2 below. Click OK.

NOTE1 Selecting a language only changes the installation screens into that language

but does not affect the underlying files that gets installed.

NOTE2 The installation screens are translated into: Spanish, Portuguese, Japanese,and Simplified Chinese. In order to see Japanese or Chinese you must have

those fonts installed on your system.



67/168

Chapter 4: Installing The Maximo 6 Application

Maximo 6, 08/2006 4-3

6 Select the appropriate application server, in this case, IBM WebSphere.

7 Enter the serial number included in your Maximo license agreement andclick Next.


68/168


4-4 Maximo 6, 08/2006

8 Enter the name of the folder where the installation program will installMaximo. The default value is C:\Maximo. Click Next.

9 Select the appropriate database and click Next.

If you are connecting to an Oracle database... If you are connecting to a SQL Server Database...


69/168


Maximo 6, 08/2006 4-5

10 Depending on your database type, enter the following database-relatedinformation, and click Next.

11 Enter the host name of the machine running the SMTP server. ClickNext.

You must enter this in order to run reports. Contact your Network

Administrator if you dont know the host name of the machine running the

SMTP server.

Oracle SQL Server

Database server name Enter the Oracle host name Enter the SQL Server host name

Port number 1521 (Default) 1433 (default)

Database name Enter the Oracle system identifier Enter the SQL Server database name

Database owner Maximo (default) Maximo (default)

Database ownerspassword

Maximo (default) Maximo (default)



70/168


4-6 Maximo 6, 08/2006

12 Enter the following e-mail notification information.

a If you are using Workflow, enter the e-mail address of the WorkflowAdministrator, otherwise, leave it blank.

b Enter the e-mail address of the Maximo administrator.

c Click Next.

13 Enter the host name or IP address and the port number of the machinewhere your WebSphere server is installed. Click Next.

You may either use the default port 9080, and later in Chapter 8, specify

this port number in WebSphere as the default Maximo Port number; or

specify another port number and use that in Chapter 8.

[email protected]

[email protected]

copmuter_name


71/168


Maximo 6, 08/2006 4-7

14 If you have purchased the Maximo Enterprise Adapter Key, then checkthe Enable Maximo Enterprise Adapter check-box, otherwise accept

default (unchecked) and click Next.

NOTE If you selected the Enable Maximo Enterprise Adapter check-box, ensureto configure your JMS options detailed in Appendix B before deploying the

EAR files as detailed in Chapter 8: Deploying the EAR Files, on page 8-

23.

15 Accept the default Maximo Server name (MXServer) and click Next.


72/168


4-8 Maximo 6, 08/2006

16 Specify the following information:

a iServer Name: enter the Actuate iServer IP address or server name.

b iServer Port Number: accept default, 8000.

c TNS Name: Enter the database TNS name.

d Click Next

17 Enter the host name of the Actuate iServer. Click Next.



73/168


Maximo 6, 08/2006 4-9

18 Accept the default value that appears in the Actuate Encyclopedia rootname text box (rpt) and click Next.

19 Click Installin the Pre-Installation Summary dialog box.

20 Once the installation is complete, click Nextin the Install Complete dialogbox.

CAUTION Ensure that you have installed the required JVM as stated in Chapter 1.


74/168


4-10 Maximo 6, 08/2006

21 Check the Update check-box and click Next.

NOTE In order to complete the Maximo 6.1 installation, you mustrun theMaximo PowerUpdate utility.

a Click Nextin the Welcome dialog box.

Allow for the updates to complete.


75/168


Maximo 6, 08/2006 4-11

b Click Nextin the Update Available dialog box.

Once the update program retrieves all the necessary files, the following

dialog box opens.

c Click Nextin the Updater Retrieved dialog box.


76/168


4-12 Maximo 6, 08/2006

d Check Create a Support Online Account and click Done.

e From the MRO Software Support Online page, click Sign upand followthe online instructions

22 Choose the Maximo installation location (default c:\MAXIMO) and clickInstall.

23 Click Done.


77/168


78/168


4-14 Maximo 6, 08/2006


79/168

Maximo 6, 08/2006 5-1

This program installs language-specific Help files and database scripts. You

install the Language Utilities after Maximo 6 is installed.

1 Insert the Maximo Language Utilities CD-ROM into the CD drive.

2 From the root CD drive, double-click maxlangen.exe(or maxlang.exe).

3 Select the appropriate language from the drop-down list. If your languageis not available from the list, select English; if it is Japanese or Chinese,

see Note 2 below. Click OK.

NOTE1 Selecting a language only changes the installation screens into that languagebut does not affect the underlying files that gets installed.



Installing The Language

Utilities 5


80/168

5-2 Maximo 6, 08/2006

4 Click Nextin the Introduction dialog box.

5 Verify that the default value (c:\Maximo) is the MaximoHome Directory

and click Next.

6 Click Installin the Pre-Installation Summary dialog box.


81/168

Chapter 5: Installing The Language Utilities

Maximo 6, 08/2006 5-3

Allow the installation progress bar to complete.

7 If you are performing the steps in this Chapter because you are addingadditional languages to an existing Maximo installation, check theBuild

maximohelp.ear filecheck-box and click Next, otherwise accept default

(unchecked) and click Next.


82/168

5-4 Maximo 6, 08/2006

8 Click Done.

You are now ready to install the Maximo Keys program.


83/168

Maximo 6, 08/2006 6-1

Maximo keys enable access to applications that you are entitled to use

determined by your Maximo license purchase.

The EAR files are built at this time. Complete the following steps:

1 Insert the Maximo Key CD-ROM into the CD drive.

2 From the root CD drive, double-click setup.exe.

3 Select the appropriate language from the drop-down list. If your language

is not available from the list, select English; if it is Japanese or Chinese,see Note 2 below. Click OK.

NOTE1 Selecting a language only changes the installation screens into that languagebut does not affect the underlying files that gets installed.



Installing The Maximo

Keys 6


84/168

6-2 Maximo 6, 08/2006


5 Verify that the default value (c:\Maximo) is the MaximoHome Directoryand click Next.


85/168

Chapter 6: Installing The Maximo Keys

Maximo 6, 08/2006 6-3

6 Click Installin the Pre-Configuration Message box.

Allow the installation progress bar to complete.

7 If you are installing additional packages, you mustat this time selectYesand the program will exit allowing you to add the other Packages (or

Keys). See Adding Additional Maximo Keys, on page C-1.


86/168

6-4 Maximo 6, 08/2006

Once all packages are installed select Noand click Done.

Three message boxes appear indicating that the EAR files are being built:

8 Click Done.


87/168

Maximo 6, 08/2006 7-1

In this chapter, you prepare an Oracle instance or a Microsoft SQL Server

insta

61 mx install was60 win

Documents