IBM Maximo Installation Guide - Microsoft Windows | IBM ...publib.boulder.ibm.com/tividd/td/ITMax/621_mx_install_was60_win/en... · IBM WebSphere Fix Pack Installation RoadMap

Release 6.2.1

Installation Guide Microsoft Windows | IBM WebSphere

IBM Maximo

First Edition (January 2007)This edition applies to version 6, release 2, modification 1 of IBM Maximo and to all subsequent releases and modifications until otherwise indicated in new editions.

Third-Party Technology: Certain Maximo 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" ownership of which is attributed as follows: Portions © 2002, Steve Souza ([email protected]). Portions © 2000-2004, Jason Hunter & Brett McLaughlin. Portions © 2004-2005, The Apache Software Foundation (http://www.apache.org/).

© Copyright International Business Machines Corporation 2007. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM Product Third-Party Information

All Products Portions © 1996-2003 Visual Mining, Inc. Visual Mining™ NetCharts Server provided by Visual Mining, Inc.

IBM Maximo Portions © 1995-2004 Actuate Corporation.

Portions © 2005 BEA Systems, Inc. BEA WebLogic Server® provided by BEA Systems, Inc.

Portions © 1996-2005, i-net software GmbH. J-Integra for COM® v2.4. © 2004 Intrinsyc Software International, Inc.

Maximo Discovery MSDE Copyright © Microsoft® Corporation.

© 1998-2005 Centennial Software Limited.

IBM Maximo Asset Navigator Portions © 1993-2002 Snowbound™ Software Corporation. RasterMaster™ Raster imaging technology provided by Snowbound Software Corporation.

IBM Maximo Mobile Portions © 2005 DataMirror, Inc.

Portions © 2000-2005 Zaval Creative Engineering Group.

IBM Maximo Mobile SE Portions © 1996-2005 Syclo, LLC.

NoteBefore using this information and the product it supports, read the information in “Notices” on page Notices-1.

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiAudience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Typical Maximo Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Understanding the Maximo Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Maximo Application Instance and EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3How Does Maximo Run in an Application Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Single Maximo Application Deployed in a Single Application Server . . . . . . . . . . . . . . . . . . . . . 1-5

Actuate Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Hardware and Software Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7IBM Software Requirements for IBM Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Third-Party Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Java Virtual Machine (JVM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Installation Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

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

Creating the Deployment Manager Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Creating a Custom Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

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

Creating a Web Server Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Installing the IBM Refresh Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

IBM WebSphere Refresh Pack Installation RoadMap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Install the Core IBM WebSphere Application Server Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Install the IBM WebSphere Application HTTP Server Patch . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Install 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-32Install the IBM WebSphere HTTP Server Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Install the IBM WebSphere Application HTTP Server Plugin Patch . . . . . . . . . . . . . . . . . . . . 2-34Install the IBM WebSphere JavaSDK Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Chapter 3: Installing The Actuate Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Pre-Installation Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

DB2 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Oracle Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1MS SQL Server Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

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

Chapter 4: Installing Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Starting the Maximo Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

© Copyright IBM Corp. 2007 iii

Update Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Update charsets.jar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6How to Modify Language-specific JDBC Settings in Maximo for SQL Server Database . . . . . . 4-9

Installing the Language Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Installing the Product Enablers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Chapter 5: Creating the Maximo Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Schema-Creation Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Task 1: Specify a Character Set for the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Task 2: Verify the Oracle Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Task 3: Tune the Oracle Initialization Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Task 4: Create Maximo Tablespace(s) for Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3Task 5: Create the Maximo Userid (Schema Name) for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Task 6: Create the Maximo Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Task 1: Ensure Requirements and Gather Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Task 2: Specify a Character Set for the DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Task 3: Configure DB2 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Task 4: Create the Maximo Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9Troubleshooting the DB2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Task 1: Verify the Microsoft SQL Server Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Task 2: Create a SQL Server Database for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Task 3: Create the Maximo User for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Chapter 6: Creating the Maximo Application Server and Deploying the EAR Files . . . . . . . . . . . 6-1Creating a Windows Service for the Node Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Creating the Maximo Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Editing JVM Memory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Adding a Redirect to IBM WebSphere 6.0.2.17 for Actuate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Identify the HTTP Transfer Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Creating Virtual Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Deploying the EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23

Chapter 7: Installing The Actuate Encyclopedia for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Starting the Actuate iServer for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Installing the Actuate Integration for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Removing Corrupt Characters from the acserverconfig.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Importing the Encyclopedia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Chapter 8: Logging Into Maximo Start Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1MEA Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Appendix A: System Server Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Starting the Services from the Windows Services Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Starting the Services from a Command Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Starting the MAXIMO Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix B: Configuring JMS Options for MEA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C: Adding Additional Product Enablers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

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

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notices-1

iv IBM Maximo: Installation Guide

About This Guide

This section explains how this guide can help you to use IBM® Maximo®. It also provides information about other IBM Corporation resources available to you, such as additional documentation and support.

Audience

This guide is intended for implementation analysts, support personnel, and system administrators who are installing Maximo for the first time.

Related Documentation

For more information about Maximo, refer to the following documentation:

Document Description

IBM Maximo Finance Manager’s Guide

Describes how IBM Maximo completes financial transactions and how to set up general ledger accounts.

IBM Maximo Multisite Administrator’s Guide

Describes how to configure IBM Maximo for a Multisite implementation.

IBM Maximo Online Help Provides step-by-step procedures for Maximo applications.

IBM Maximo Reconciliation Module Implementation Guide

Describes how to use the IBM Maximo Reconciliation module to reconcile the two types of information that IBM Maximo maintains about information technology (IT) assets: IT asset data and deployed asset data.

IBM Maximo Report Administration and Development Guide

Describes how to use Actuate® to design and administer IBM Maximo reports.

IBM Maximo System Administrator’s Guide

Describes database configuration, security, and other administrative level applications and tasks.

© Copyright IBM Corp. 2007 vii

Support

Support

IBM Maximo users with a valid Annual Customer Support Plan (ACSP) can obtain product support online at Support Online: support.mro.com.

Support Online includes information about product releases, software patches, and documentation updates. To find the most current version of a document, refer to the Knowledge Base on this site.

IBM Maximo User’s Guide Provides an overview of the Maximo end user applications. It also describes how the IBM Maximo applications interact with each other.

IBM Maximo Workflow Implementation Guide

Provides information about how to use IBM Maximo to plan, design, build, test, implement, and manage Workflow processes.

IBM Maximo Enterprise Adapter (MEA) System Administrator's Guide

Describes how to configure and use the IBM MEA.

Document Description

viii IBM Maximo: Installation Guide

http://support.mro.com

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

This chapter describes Maximo components and concepts, and provides an installation roadmap to guide you through the Maximo installation process.

Introduction 1

© Copyright IBM Corp. 2007 1-1

Typical Maximo Configuration

Typical Maximo Configuration

Maximo requires multiple software servers that you can either install on separate, dedicated server machines (for best performance), or the same physical server. The following diagram depicts a typical Maximo configuration. For the system requirements for this configuration, see “Hardware and Software Considerations”, on page 7.

1-2 IBM Maximo: Installation Guide

Understanding the Maximo Components


A typical Maximo environment includes three main components:

Application ServerActuate® Report ServerDatabase Server

NOTE Installing Maximo and its components requires a valid and active connection to the Internet.

Application Server

Maximo is built using Java™ 2 Enterprise Edition (J2EE™) technology, which requires a commercial application server, such as IBM WebSphere. IBM Corporation uses the term application server to refer to a J2EE container that provides the infrastructure to run business applications such as Maximo. It uses the term Application Server (initial capital letters) to refer to an application server running Maximo.

The Application Server consists of Maximo applications using JavaServer Pages (JSP), XML, and Maximo-application-specific business components.

Maximo Application Instance and EAR Files

When you install Maximo, you create a new Application Server (in the container sense) for the Maximo application iteration within IBM WebSphere.

Maximo application refers to an instance of Maximo.

The Maximo application 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.

Enterprise 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 J2EE application that you 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 pagesJava Enterprise Application (JAR) files that contain class files and other programming code modulesEnterprise Java Bean (EJB) files that contain class files

Introduction 1-3


Context is the name through which you access a specific web application, such as Maximo deployed on an Application Server. Maximo 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://<host name>:<port number>/maximo. The character string maximo that appears after the port number, is the Maximo context.

How Does Maximo Run in an Application Server?

Maximo runs in an Application Server as follows:

Maximo creates three EAR files from the contents placed on your local drive as part of the Maximo installation process:

! maximo.ear – for the Maximo application! maximohelp.ear – for the Maximo Help application! acweb.ear – for the IBM Actuate Active Portal Integration application

All three EAR files comprise a single Maximo application (MAXIMOSERVER).

To run Maximo, you use your Application Server software (such as IBM WebSphere), to deploy the Maximo application EAR files in the Application Server.

After you deploy Maximo application EAR files in the Application Server, the server maintains its own copy of the EAR files 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.

To make configuration changes to Maximo, you must edit the EAR files, and then rebuild and redeploy them.



Single Maximo Application Deployed in a Single Application Server

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. The Application Server, such as the IBM WebSphere server, accepts HTTP requests from client programs (web browsers) and responds 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 the user 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 with IBM Corporation, you can access the Support Online Web site: 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 site’s Knowledge Base.

To create a Support Online user account, you will need your IBM Corporation product serial number.

Actuate Report Server

Actuate iServer is the embedded reporting tool for Maximo. The Actuate Information Delivery Solution enables you to create, manage, and deliver interactive, actionable content. Specifically, Actuate generates and manages report documents and provides the following features:

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

WAR files

JAR files

EJB Files

WAR files

WAR filesJAR files

maximohelp.ear

acweb.ear

maximo.ear

The Maximo installation programbuilds the necessary EAR files

MAXIMOSERVER

The deployed EAR files are nowaccessed by IBM WebSphere

Database

Actuate iServer

Introduction 1-5

http://java.sun.com/products/jsp/ index.html


Information in multiple formats including DHTML, PDF, XLSOpen security folder integration to leverage existing e-business platform security service

Maximo supports other reporting tools as well. (If you choose not to use Actuate, skip the Actuate references when you install Maximo in Chapter 4.)

If you choose Actuate, install the Actuate iServer on a separate, dedicated server on the network.

Database Server

A Maximo installation using IBM WebSphere application server software is compatible with the following database software: IBM DB2® Universal DataBase (UDB), Microsoft® SQL Server, and Oracle®. See “Hardware and Software Considerations”, on page 7 for a complete listing of supported hardware and software releases, and exceptions.


Hardware and Software Considerations


For best performance, adhere to the following configuration:

Dedicated Application ServerDedicated Actuate ServerDedicated Database Server

Factors affecting server configuration requirements are:

Maximo applications deployedNumber of connecting client workstationsDesired performance level

The following table lists supported hardware and software for Maximo release 6.2.1.

Dedicated Servers Hardware Software

Application Serverwhere you install IBM WebSphere and typically, where you deploy Maximo EAR files

2–4 dedicated, Intel®-based Pentium® processors2GB RAM per processor1.5GB or greater of disk space for Maximo and Java/Web Server components

Microsoft Windows® 2000 ServerMicrosoft Server 2003IBM WebSphere 6.0.2.17

Note: Use the IBM WebSphere Fix Packs and Refresh Packs (supplied by IBM Corporation) to upgrade WebSphere to version 6.0.2.17.

Database Server: Refer to vendor specifications IBM DB2 Universal Database 8.2.7 (configured for TCP/IP support)Oracle 9.2.0.6 or 10.2.0.2 server softwareMicrosoft SQL Server 2000 SP4Microsoft SQL Server 2005

Oracle and Microsoft database server software can be either Standard or Enterprise editions.

Actuate iServer: where you install Actuate reporting software used to create and manage your Maximo reports

1–2 dedicated, Intel-based Pentium processors1GB RAM per processor1GB of disk space for Actuate software components

Microsoft Windows 2000 ServerMicrosoft Server 2003Actuate iServer Release 8

Note: If you are not installing Actuate and DB2 on the same server, you must install and run DB2 UDB Administrative Client 8.2.7 on your Actuate server before you install Actuate. This software includes the IBM Type 4 JDBC driver that Maximo uses to connect with DB2.

Database client software: Oracle Client Software (Oracle JDBC drivers, SQL*Plus, Oracle Networking)MS SQL Server 2000 Client (ODBC)DB2 UDB Administration Client Version 8.2.7

Introduction 1-7


For additional tuning and configuration information, refer to the IBM Maximo System Administrator’s Guide.

Administrative Workstation

Where you install Maximo software and build EAR files before deploying them

Intel-based Pentium processor1GB RAM SVGA 1024 x 768 resolution; if used for Application Designer 1280 x 1024 resolution

Microsoft Windows 2000 or XP

Note: The Maximo Workflow Designer requires a Java Runtime Environment. JRE 1.4.2 – JRE1.5 are supported.

Microsoft Windows Internet Explorer® 6.0 or Microsoft Windows Internet Explorer 7Adobe® Acrobat® Reader® 6.0IBM Maximo (optional)

Client Workstation Intel-based Pentium processor512 MB RAM SVGA 1024 x 768 resolution

Microsoft Windows 2000 or XPMicrosoft Windows Internet Explorer 6.0 or Microsoft Windows Internet Explorer 7 browserAdobe Acrobat Reader 6.0

Dedicated Servers Hardware Software


Installation Roadmap

IBM Software Requirements for IBM Updates

IBM Corporation has certified the following IBM product updates:

IBM WebSphere 6.0.2.17

IBM DB2 8.2.7

Third-Party Product Updates

IBM Corporation 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. IBM Corporation has certified the following third-party product updates:

Windows 2003 Server/Advanced Server Service Pack 1

Windows XP Professional Service Pack 2

Windows 2000 Professional Service Pack 4

Internet Explorer 6.0 Service Pack 2 and Internet Explorer 7

Oracle 10.2.0.2 Service Pack 2

Oracle 9.2.0.6 Service Pack 6

Microsoft SQL Server 2000 Service Pack 4

MS SQL Server 2005 Service Pack 1

The Oracle and SQL Server items mentioned in the above list refer to either the Standard or Enterprise editions of the software.

Java Virtual Machine (JVM)

The Maximo automatic update program used in the product installation requires that you install a Java Virtual Machine (JVM) 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.


CAUTION Existing Maximo 6.x customers can overwrite files and data when following the standard installation procedures. If you are an existing Maximo 6.x customer, refer to the IBM Maximo 6.2.1 Release Notes on the Support Online Web site for your specific installation instructions.

Introduction 1-9

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

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


The Maximo installation process requires that you complete the procedures in the order they appear in the following roadmap:

1 Install the IBM WebSphere application server

2 Install the Actuate application server

3 Install the Maximo software

4 Install the language utilities program

5 Install the Maximo Product Enablers program

6 Create the Maximo schema

7 Deploy the Enterprise Archive (EAR) files

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 them for a successful Maximo system installation:

Install IBM WebSphereConfigure the Maximo Application Server

Install the Actuate 8 iServer application

Install Maximo and

Create the Maximo Encyclopedia for

Maximo

Log into MaximoStart Center

Chapter 2 Chapter 3 Chapter 4

Chapter 5Chapter 6Chapter 7Chapter 8

Perform post-installation tasksrelated software

SchemaInstall the Actuate

Deploy the EARfiles


Installing IBM WebSphere 6.0.2.17 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

CAUTION Existing Maximo 6.x customers can overwrite files and data when following the standard installation procedures. If you are an existing Maximo 6.x customer, refer to the IBM Maximo 6.2.1 Release Notes on the Support Online Web site for your specific installation instructions.

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 to the IBM Maximo System Administrator’s 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 systemLog on as a service

Installing IBM WebSphere 2



For best performance, install the WebSphere Application Server on a dedicated application server

To install IBM WebSphere 6.0.2.17, complete the following steps:

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

2 Insert the CD for the WebSphere 6.0 Application Server Windows in the CD drive. If the installation does not start, double-click launchpad.bat.

3 Click Launch the installation wizard for WebSphere Application Server link from 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 Next in the Welcome dialog box.



5 Select the I accept the terms in the license agreement option. Click Next.

6 Click Next after the system check completes..

Installing IBM WebSphere 2-3


7 Change the installation location by removing the Program Files directory. 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 name of the installation directory.

8 Clear the Application Server Samples and 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



9 Click Next in the Installation summary dialog box.

Allow for all components to install.

10 Select the Launch the Profile creation wizard check box. Click Next.

c:\WebSphere\Appserver

c:\IBMHttpServer

<Node_name>

<Host_name>



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 manager option. Click Next.



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, and Cell name. Click Next.



6 Review the assigned port numbers. Click Next. Note the Administrative port 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 log on as a local system account. Click Next.



8 Click Next in the Profile summary dialog box.

9 Select the Launch the First steps console option. Click Finish.

10 Click the Installation verification link.



11 After Installation Verification completes, close the output window.

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

You now can create a custom profile.



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.



3 Accept the default values or specify the appropriate information. Click Next.

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



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.



8 Click Next in the Profile summary dialog box.

9 Select the Launch the First steps console check box. Click Finish.



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.


Installing the IBM HTTP Server


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 the installation wizard for IBM HTTP Server.


<user_id>



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 default installation location is \Program Files\IBM HTTP Server. Click Next.

remove \Program Filesand remove the spacesin IBM HTTP Server



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

d Automatic as the Startup Type from the drop-down list.

7 Click Next.

username



8 Click Next in the summary dialog box.

9 Click Next.



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

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


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 Clear both check boxes in the Welcome dialog box. Click Next.

2 Accept the License terms. Click Next.



3 Click Next in the System prerequisites check dialog box.

4 Select the IBM HTTP Server V6 option. Click Next.

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



6 Change installation location by removing the Program Files directory. The default installation location is \Program Files\IBM\WebSphere\Plugins. Click Next.

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



8 The Wizard does not default to the location of the httpd.conf file. You must click the Browse button to select the following location: <drive_letter>:\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. Click Next.

C:\IBMHTTPSERVER\conf\httpd.conf



10 Accept the default location of the plugin-cfg.xml file as it appears. Click Next.

11 Click Next.

12 Click Next.

This is an example path



13 Click Next.

14 Click Finish.

in step 15.



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, and all 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 stop it.

Node Agent From a command prompt, change directory to: C:\IBM\WebSphere\AppServer\profiles\Custom01\bin\ and run stopNode.bat.


Installing the IBM Refresh Pack


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.17, which is required with Maximo 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 completed all 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), complete the following steps:

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

2 Insert the IBM WebSphere Refresh Pack CD-ROM.

3 From a command prompt, change directory to <drive_letter>\IBM\WebSphere\AppServer\profiles\Dmgr01\bin.

4 Run the backupConfig.bat file.

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

The Directory where You unzip the Refresh Pack Files

The Executable file that You 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



5 From a command prompt, change directory to <drive_letter>\IBM\WebSphere\AppServer\profiles\Custom01\bin.


7 Delete the updateinstaller folder, if present, from the <drive_letter>\IBM\WebSphere\AppServer directory.

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

NOTE The files unpack into an updateinstaller directory that is automatically created in the AppServer directory during the extraction process.

9 Change directory to <drive_letter>:\IBM\WebSphere\AppServer\updateinstaller.

10 Double click the update.exe file.

11 Click Next in 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 package and click Next.

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

15 Click Next to copy the JDK. Allow for the JDK-copying process to complete.

16 Click Relaunch once the JDK is completely loaded to relaunch the Wizard.


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

19 Click Next to 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 Patch installation process is complete.

Now proceed to the next section to install the Refresh Pack for IBM WebSphere HTTP Server Patch (6.0.2).



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 updateinstaller folder, if present, from <drive_letter>:\IBMHTTPServer.

2 Extract the 6.0-WS-WASIHS-WinX32-RP0000002.zip file into the <drive_letter>:\IBMHTTPServer directory.

NOTE The files unpack into an updateinstaller directory that is automatically created in the IBMHTTPServer directory during the extraction process.

3 Change directory to <drive_letter>:\IBMHTTPServer \updateinstaller.





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 Refresh Pack for the IBM HTTP Server and click Next to 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 and then 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 updateinstaller folder, if present, from <drive_letter>:\IBM\WebSphere\Plugins.

2 Extract the 6.0-WS-WASPlugIn-WinX32-RP0000002.zip file into the <drive_letter>:\\IBM\WebSphere\Plugins directory.

NOTE The files unpack into an updateinstaller directory that is automatically created in the Plugins directory during the extraction process.

3 Change directory to <drive_letter>:\IBM\WebSphere\Plugins\updateinstaller.








9 Click Next to copy the JDK. Allow for the JDK-copying process to complete.

10 Click Relaunch once the JDK is completely loaded.



13 Read the Wizard panel text to verify you are installing the 6.0.2.0 Refresh Pack 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 verify successful 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 next section, delete all the updateinstaller folders created in this process.


Installing the IBM WebSphere Fix Pack


You use the IBM WebSphere Fix Pack CD to update IBM WebSphere 6.0.2 software to release 6.0.2.17.

When updating IBM WebSphere from 6.0.0.x, you cannot update directly to 6.0.2.17. You must first install the Refresh Pack to update to 6.0.2, as described in the previous section.

For the 6.0.2.17 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.17.

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 completed all 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.17) 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 to IBM\WebSphere\AppServer\profiles\Dmgr01\bin.

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

The Directory where You unzip the Fix Pack Files

The Executable file that You Run

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

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

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

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




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


6 Delete the updateinstaller folder, if present, from IBM\WebSphere\AppServer directory.

7 Extract the 6.0.2-WS-WAS-WinX32-FP00000017.zip file into the <drive_letter>:\IBM\WebSphere\AppServer directory.

NOTE The files unpack into an updateinstaller directory that is automatically created in the AppServer directory during the extraction process.







14 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) is being installed and then click Next to begin the installation.

15 Allow the JDK-copying process to complete. Read the Wizard panel text to verify successful installation of 6.0.2.17 and then click Finish. The Fix Pack (6.0.2.17) core Application Server Patch installation process is complete.

Now proceed to the next section to install the IBM WebSphere Fix Pack (6.0.2.17) HTTP Server Patch.

Install the IBM WebSphere HTTP Server Patch

To install the IBM WebSphere Fix Pack (6.0.2.15) HTTP Server Patch, complete the following steps:

NOTE The IBM WebSphere Fix Pack 6.0.2.15 (for the HTTP Server patch) is forward compatible with all the other Fix Pack 6.0.2.17 installs.

1 Delete the updateinstaller folder, if present, from the \IBM\HTTPServer directory.

2 Extract the 6.0.2-WS-WASIHS-WinX32-FP00000015.zip file into the <drive_letter>:\IBMHTTPServer directory.



NOTE The files unpack into an updateinstaller directory that is automatically created in the IBMHTTPServer directory during the extraction process.

3 Change directory to <drive_letter>:\IBMHTTPServer\updateinstaller.






9 Read the Wizard panel text to verify that Fix Pack 6.0.2.15 (FP60215) is being installed, and then click Next to 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.15 and then click Finish. The Fix Pack (6.0.2.15) 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.17) Application Server Plugin Patch.

Install the IBM WebSphere Application HTTP Server Plugin Patch

To install the IBM WebServer Fix Pack (6.0.2.17) Application Server Plugin Patch, complete the following steps:

1 Delete the updateinstaller folder, if present, from the \IBM\WebSphere\Plugins directory.

2 Extract the 6.0.2-WS-WASPlugIn-WinX32-FP00000017.zip file into the <drive_letter>:\IBM\WebSphere\Plugins directory.


3 Change directory to <drive_letter>:\IBM\WebSphere\Plugins\updateinstaller.








9 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) for the Plugin is about to be installed and then click Next to begin the installation.

10 Allow the file-copying process to complete. Read the Wizard panel text to verify successful installation of Plugin 6.0.2.17 and then click Finish. The Fix Pack (6.0.2.17) HTTP Server Patch installation process is complete.

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

Install the IBM WebSphere JavaSDK Patch

To install the IBM WebSphere Fix Pack (6.0.2.17) JavaSDK Patch, complete the following steps:

1 Delete the updateinstaller folder, if present, from the \IBM\WebSphere\AppServer directory.

2 Extract the 6.0.2-WS-WASJavaSDK-WinX32-FP00000017.zip file into the <drive_letter>:\IBM\WebSphere\AppServer directory.








9 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) for the JavaSDK is being installed and then click Next to 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 and click Next.

13 Read the Wizard panel text to verify that maintenance package WASJAVASDKFP60217 is being installed and then click Next to begin the installation.



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

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

The fix pack (6.0.2.17) javasdk patch installation process is now complete, which completes the IBM WebSphere 6.0.2.17 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.


If you are using Actuate for reporting in Maximo, this chapter explains how to install 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.

DB2 Connectivity

Complete the following steps to ensure connectivity from DB2 to Actuate.

1 If you are installing Actuate on a server that is separate from the DB2 server, install the following DB2 client software on your Actuate Server before you install Actuate:

DB2 UDB Administrative Client 8.2.7

2 Create a Call Level Interface (CLI) connection to your Maximo database by using the DB2 Configuration Assistant. When complete, test your connectivity.

NOTE Do not use the Open Database Connectivity (ODBC) option.

Oracle Connectivity

Complete the following steps to ensure connectivity from Oracle to Actuate:

1 f you are installing Actuate on a server that is separate from the DB2 server, install the following DB2 client software on your Actuate Server before you install Actuate:

Oracle JDBC DriversSQL*PlusOracle Networking (in Oracle 9i or 10g)

2 Setup and test Oracle Networking connectivity to the Maximo database.

3 Create a TNS name for your Maximo connect string as you will need this information in Step 10 on page 4-2.

Installing The Actuate Application 3


Installing Actuate8 iServer

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.

NOTE If you are using Oracle 10 server software, you must install the Oracle 9 client on the Actuate iServer.

You must also create a DSN name for your Maximo connect string as you will need this information in Step 10 on page 4-2.

Install the following products:

Microsoft SQL Server ODBC DriversSQL Server Client Network Utility.


This section describes how to install Actuate 8 iServer. For best performance, install the 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.



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


4 Accept the terms of the License Agreement and click Next.

Installing The Actuate Application 3-3


5 Select Custom and read the following warning before clicking Next.

WARNING Default value for the Destination Folder is \Program Files\Actuate8\iserver; however, you must ensure that the Destination Folder path does not have any spaces in the path name. For example c:\Actuate8\iserver. Click Browse to select the new path.

6 Select all components except Sample Volume and click Next.



7 Select Stand-alone and click Next.

8 Click the browse button and navigate to the location of the xml file, in this example: Actuate_key_18802.xml. This file resides under the root CD folder on your Actuate Release 8 iServer for Windows CD-ROM. Click Next.

d:\Actuate_key_18802.xml



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

10 Enter a user that is in the Administrator Group and ensure that both check-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 are installing Actuate iServer.

<actuate_user>



b Accept the default port number 8100.

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

d The host name or the IP address of the machine where you are installing 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.



13 Select Use the default volume and type the computer name or IP address. Click Next.

14 Select Use the Actuate Encyclopedia volume and click Next.

Actuate

host name host name



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

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

You open the Actuate Administrative console via a browser, using this port number. For example: http://<actuate_computer>:8900/acadmin

<host name>



17 Accept the default context path (/acadmin) or specify another context name and click Next. You open the Actuate Administrative Console via a browser, using this context. For example: http://<actuate_computer>:8900/acadmin

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

The above two steps enable system administrators to access, generate, and manage reports using Actuate’s web-based console.

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



19 Click Next in the Summary dialog box.

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

21 Close the setup.txt file.



22 Uncheck the ReadMe check-box and click Finish.

You are now ready to install Maximo.


This chapter explains how to install the Maximo application, the Language Utilities, and the Product Enablers program.

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 Maximo 4Record the information here... Use the information here...

Maximo-related

Serial number Step 7 on page 4-2

Maximo install folder Step 8 on page 4-2

SMTP host name Step 11 on page 4-3

Work flow administrator email Step 12 on page 4-3

Maximo administrator email Step 12 on page 4-3

Application server name Step 13 on page 4-3

Listen Port number Default is 9080

or specify another: ___________________

You can either use the default port number or specify another. Make a note of it, you will need this number in Chapter 8.

Database-related

Database server name Step 10 on page 4-2

Database port number Step 10 on page 4-2

Database Name Step 10 on page 4-2

Database/Schema owner name Step 10 on page 4-2

Database/Schema password Step 10 on page 4-2

Actuate-related

Actuate iServer name Step 16 on page 4-3

iServer port number Step 16 on page 4-3

Datasource Name (DB2), TNS (Oracle), or DSN (MS SQL Server) on the Actuate iServer

Step 16 on page 4-3


Starting the Maximo Installation Program


You install Maximo onto a Windows workstation designated as the Maximo 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 administrative rights.

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

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

4 Select the desired language from the drop-down list. Selecting a language only changes the installation screens into that language but does not affect the underlying files that get installed.

If your language is not available from the list, select English, and click OK.If it is Japanese or Chinese you must have those fonts installed on your system.For any selected language other than English, that you are installing on a SQL Server database, you must perform certain post-installation tasks as described in “Post Installation Tasks” on page 7-5. This procedure does not apply if you are using an Oracle database.


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

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

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

9 Select the appropriate database and click Next.

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

DB2 Oracle SQL Server

Database server name

Enter the DB2 server host name

Enter the Oracle server host name

Enter the SQL Server host name

Port number 50000 1521 (Default) 1433 (default)



11 Enter the host name of the machine running the SMTP server. Click Next.

You must enter this in order to run reports. Contact your Network Administrator if you don’t know the host name of the machine running the SMTP server.

12 Enter the following e-mail notification information.

a If you are using Workflow, enter the e-mail address of the Workflow Administrator, 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 machine where your WebSphere application 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.

14 If you have purchased the MEA Product Enabler, then check the Enable Enterprise Adapter check-box, otherwise accept default (unchecked) and click Next.

NOTE If you selected the Enable Enterprise Adapter check-box, ensure to configure your JMS options detailed in Appendix B before deploying the EAR files as detailed in “Deploying the EAR Files” on page 6-23.

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

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 Depending on the database server you installed, enter one of the following values:

If DB2, enter Datasource name.If Oracle, enter TNS name.If SQL Server, enter DSN name.

Database name Enter the DB2 database name

Enter the Oracle system identifier

Enter the SQL Server database name

Database/Schema owner

Maximo (default) Maximo (default) Maximo (default)

Database/Schema password

Maximo Maximo Maximo

DB2 Oracle SQL Server

Installing Maximo 4-3


d Click Next

17 Enter the host name of the Actuate iServer in the Default Volume Name field. Click Next.

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

19 Click Install in the Pre-Installation Summary dialog box.

20 Once the installation is complete, click Next in the Install Complete dialog box.

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

21 Click inside the install dialog box. Select the Check for Updates... box and click Next.

22 Click Next in the Welcome to PowerUpdate! dialog box. You will see a Checking for Update dialog box while PowerUpdate searches for updates to Release 6.2.1.

If no updates are required, you will see the Your Software is Already Up to Date dialog box. Click Exit to close PowerUpdate.

If updates are available, click Next in the Update Available dialog box to retrieve the executable with updated files. The program displays a status message and the Updater Retrieved dialog box when finished.

23 To run the executable, click Next to open the Choose Install Folder dialog box.

24 Choose the Maximo installation location (default c:\MAXIMO). Now click Next and then Install.

25 Click Done.

NOTE If you are a new customer, the install program closes and you are taken to support.mro.com. You must create a Maximo support account. Complete the New Account Creation form, and click Submit.

26 Navigate to the following location:

<Maximo_root>\applications\activeportal\WEB-INF\classes\com\actuate\ExternalText

27 If you are running DB2, uncomment the following text string by removing the pound (#) sign:

actuate.externText.JDBCDriverName=com.ibm.db2.jcc.DB2Driver

Next, add the following database information:

actuate.externText.JDBCConnectionURL=jdbc:db2://<database_server_name>:<port_number>/<database_name>



If you are running Oracle, uncomment the following text string by removing the pound (#) sign:

actuate.externText.JDBCDriverName=oracle.jdbc.driver.OracleDriver\


actuate.externText.JDBCConnectionURL=jdbc:oracle:thin:@<database_server_name>:<port_number>:<tns_name>

If you are running SQL Server, uncomment the following text string by removing the pound (#) sign:

actuate.externText.JDBCDriverName=com.inet.tds.TdsDriver


actuate.externText.JDBCConnectionURL=jdbc:inetdae7a:<database_server_name>:<port_number>?database=<database_name>&language=us_english&nowarnings=true

28 Search for the following text string:

actuate.externText.username=

Enter the Database Schema owner name you used in Step 10. For example, enter Maximo.

Search for the following text string:

actuate.externText.password=

Enter the Database Schema password you used in Step 10. For example, enter Maximo.

actuate.externText.password=


l_reportlabel.columnwidth as width1 from .reportlabel

Enter the Schema Owner name you used in Step 10 after “from” and “.reportlabel.” For example, enter Maximo.

l_reportlabel.columnwidth as width1 from Maximo.reportlabel Maximo


actuate.externText.localeSQLString=select varvalue from

At the end of this string, enter the Schema Owner name you used in Step 10. For example, enter Maximo.

actuate.externText.localeSQLString=select varvalue from Maximo

31 Remove the CD-ROM from its drive.



Post Installation Tasks

In this section you perform the following general tasks:

Update help files.Update charsets.jar (if installing in a DB2 environment using a Korean locale).Modify language-specific JDBC settings in Maximo for SQL Server database users.

Update Help Files

You must now update your online help files by downloading en.zip from the product support online (http://support.mro.com) Knowledge Base website to the Maximo application server.

1 Unzip the en.zip file.

2 Copy the en folder to the following location: <maximo>\applications\maximohelp\helpweb\webmodule

Update charsets.jar

If you install Maximo in a DB2 environment using a Korean locale, you must complete the following steps before you build the Maximo schema.

Rename charsets.jar in Maximo JRE library to charsets_Sun.jar

Copy charsets.jar from the DB2 install directory to the Maximo JRE and application libraries

Edit buildmaximoear.xml and commonenv.bat to include charsets.jar in the classpath

Run maxinst from a DB2 Command Line Processor (CLP) window

NOTE To access the charsets.jar file, you must have already installed Maximo and the Language Utilities (See page 4-11).

Rename charsets.jar to charset_Sun.jar

Complete the following steps to rename the charsets.jar file:

1 Locate charsets.jar in your Maximo JRE library. For example:

c:\<maximo_root>\tools\java\jre\lib\charsets.jar

2 Rename charsets.jar to charsets_Sun.jar.

Copy charsets.jar from DB2 install directory to the Maximo JRE and Maximo application libraries

Complete the following steps to copy charsets.jar from the DB2 install directory to the Maximo JRE and application libraries:

1 Locate charsets.jar in your DB2 JRE library. For example:

c:\<DB2_install>\java\jdk\jre\lib\charsets.jar

2 Make a copy of charsets.jar and paste into the following locations:

c:\<maximo_root>\tools\java\jre\lib



c:\<maximo_root>\applications\maximo\lib

By completing the above steps, you have replaced the Sun charsets.jar with the IBM DB2 charasets.jar. You have also included a copy of this file in the Maximo application library.

Update the classpaths for buildmaximoear.xml and commonenv.bat files with charsets.jar

Complete the following steps to update the classpaths for buildmaximoear.xml and commonenv.bat.

1 Open buildmaximoear.xml in c:\<maximo_root>\deployment in a text editor.

2 Search for the first instance of the following text string:

value=”${maximo.propertiesjarfile}

3 Insert lib/charsets.jar after the text string. For example:

value=”${maximo.propertiesjarfile}lib/charsets.jar


value=”${maximo.propertiesjarfile} ${maximo.propertiesjarfile}

5 Insert lib/charsets.jar after the text string in Step 4.

6 Search for the second instance of the following text string:

value=”${maximo.propertiesjarfile} ${maximo.propertiesjarfile}

7 Insert lib/charsets.jar after the text string in Step 6.




9 Once you are in this section of buildmaximoear.xml, find <exclude name=”lib/weblogic.jar”/> and insert the following statement on the next line:

<exclude name=”lib/charsets.jar”/>

10 Save the changes you made to buildmaximoear.xml.

11 Open commonenv.bat in c:\<maximo_root>\tools\maximo in the text editor.


@rem MAXIMO_DB_LIBSset MAXIMO_DB_LIBS=%MAXIMO_LIB_PATH%\oraclethin.jar;

13 Insert the following text string after the equal (=) sign in Step 12:

%MAXIMO_LIB_PATH%\charsets.jar;

14 Save the changes you made to commonenv.bat in the Maximo tools directory.



15 Open commonEnv.bat in c:\<maximo_root>\tools\maximo\internal in the text editor.


@rem MAXIMO_DB_LIBSset MAXIMO_DB_LIBS=%MAXIMO_LIB_PATH%\oraclethin.jar;

17 Insert the following text string after the equal (=) sign in Step 16:

%MAXIMO_LIB_PATH%\charsets.jar;

18 Save the changes you made to commonEnv.bat in the internal Maximo tools directory.

Run maxinst from a DB2 Command Line Processor (CLP) window

After you finish editing the buildmaximoear.xml and commonenv.bat files, and install the product enablers (See page 4-12), you can run maxinst to build the Maximo schema. See page 5-8 for detailed information on building the Maximo schema using a DB2 database.

Complete the following steps to open a DB2 Command Line Processor (CLP) window. You must run maxinst from this window.

1 From your desktop, click Start > Run and type db2cmd to open a DB2 CLP window.

2 Change the directory path to c:\<maximo_root>\tools\maximo.

3 Run maxinst. See “Task 4: Create the Maximo Database Objects” on page 5-9 for detailed instructions.



How to Modify Language-specific JDBC Settings in Maximo for SQL Server Database

NOTE Perform the tasks outlined in this section only if you are installing a non-English language, and you are using SQL Server database; otherwise, ignore this section and the post-installation tasks outlined in “Post Installation Tasks” on page 7-5.

You must modify the JDBC settings in order for Maximo and Actuate Reporting to work properly with translated databases that contain special characters. For example: French, Swedish, or double-byte languages such as Chinese, Japanese and Korean.

There are a total of four files that you must edit. In this section you edit the maximo.properties file. If are using Actuate as your Reporting tool, then you must edit the remaining three Actuate-related files as described at the end of “Post Installation Tasks” on page 7-5.

Complete the following steps to modify the maximo.properties file.

1 Using Windows Explorer, navigate to <Maximo_root_directory>\applications\maximo\properties

2 Using a text editor, open the maximo.properties file.

NOTE If you have multiple instances of Maximo, you must modify all Maximo (or Actuate) properties files.

3 Search for the following string: mxe.db.url=jdbc:inetdae7a

Example of the mxe.db.url setting before making any changes.

4 Remove the last ’a’ from inetdae7a, leaving inetdae7.

Remove the aAdd &charset=<the code> after true



5 Add &charset=<charset code> immediately after the nowarnings=true.

<charset code> is the character set code and depends on the language that you are using.

Use the following character set codes in the JDBC setting for the primary languages supported in Maximo:

Chinese (Simplified) : GBKDutch : 8859_1French : 8859_1German : 8859_1Italian : 8859_1Japanese : Shift_JISKorean : euc-krPortuguese : 8859_1Spanish : 8859_1Swedish : 8859_1

For example if you have a Japanese database, type Shift_JIS for the character set.

6 Save and close the file.

Example of the mxe.db.url setting after making the changes.

Generally, modifying the maximo.properites file (or any *.properties files) requires that you rebuild and re-deploy the EAR files.

In this case, you do not need to rebuild and redeploy the maximo.ear file. The Product Enablers program builds all the necessary EAR files for you and so the changes that you made to the maximo.properties page in this section is incorporated in the resulting EAR files. Later in this guide, you are instructed on how to deploy the EAR files.

However, you must manually rebuild and re-deploy the acweb.ear file because you modify this file after having built and Deployed it. Therefore, any changes that you make to the actuate-related properties file in “Post Installation Tasks” on page 7-5 requires you to manually rebuild and re-deploy the acweb.ear file.


Installing the Language Utilities

Installing the Language Utilities

This program installs language-specific Help files and database scripts. You install the Language Utilities after Maximo is installed.

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

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


If your language is not available from the list, select English, and click OK.If it is Japanese or Chinese you must have those fonts installed on your system.For any selected language other than English, that you are installing on a SQL Server database, you must perform certain post-installation tasks as described in “Post Installation Tasks” on page 7-5. This procedure does not apply if you are using Oracle database.

4 Click Next in the Introduction dialog box.

5 Verify that the default value (c:\Maximo) is the Maximo Home Directory and click Next.

6 Click Install in the Pre-Installation Summary dialog box.

Allow the installation progress bar to complete.

7 If you are performing the steps in this Chapter because you are adding additional languages to an existing Maximo installation, check the Build maximohelp.ear file check-box and click Next, otherwise accept default (unchecked) and click Next.

8 Click Done.

You are now ready to install the Product Enablers program.


Installing the Product Enablers

Installing the Product Enablers

Product Enablers lets you access 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 IBM Maximo Product Enablers CD-ROM into the CD drive.

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





6 Click Install in the Pre-Configuration Message box.


7 If you are installing additional packages, you must at this time select Yes and the program will exit allowing you to add the other Product Enablers. See Appendix C, "Adding Additional Product Enablers."

Once all packages are installed select No and click Done.

Three message boxes appear indicating that the EAR files are being built. Click Done.


Schema-Creation Process Overview

To create the Maximo schema, you must first install and start a database instance (either Oracle, DB2, or Microsoft SQL Server) on the server that you have chosen as your database server and to which you plan to connect Maximo. This database serves to contain your Maximo data and must be created with the character set that supports the languages you intend to use.

After you install the database instance, you configure it (with commands) and tune it (with parameters) for optimal use with Maximo. The command examples provided herein are guidelines for changing the standard database configuration. For more details on Oracle, DB2, or SQL Server configuration commands, refer to your Oracle, DB2, or SQL Server documentation. The tuning-parameter examples provided herein are generally recommended by IBM Corporation, however, the actual parameters required for your environment might differ depending on server disk space and site requirements.

To complete the Maximo schema-creation process, you create the Maximo tablespace(s) and the Maximo userid (Oracle only), and the database objects needed to create the Maximo database.

The following section explains how to create the Maximo schema using an Oracle database. If you are using a DB2 database, begin at the section entitled “DB2”, on page 5-8. If you are using a Microsoft SQL Server database, begin at the section entitled “Microsoft SQL Server”, on page 5-12.

Oracle

To create the Maximo schema using an Oracle database, perform the following tasks as described in this section.

Creating the Maximo Schema 5

Task Task description and location

1. “Task 1: Specify a Character Set for the Oracle Database”, on page 5-2.

2. “Task 2: Verify the Oracle Instance Requirements”, on page 5-2.

3. “Task 3: Tune the Oracle Initialization Parameters”, on page 5-2.

4. “Task 4: Create Maximo Tablespace(s) for Oracle”, on page 5-3.


Oracle

Task 1: Specify a Character Set for the Oracle Database

Maximo supports multiple languages within a single schema. Create the Oracle instance (database) with the Database Character Set that supports the languages you intend to use. For example, for English, French, German, Spanish, Dutch, Portuguese, and Italian, use the Oracle character set WE8ISO8859P1.

If you plan to use a mix of languages that cannot use a single character set, such as English, Chinese, and Polish, create the database with the Unicode character set AL32UTF8, which is the only Unicode character set that can be used with Maximo.

If you create the database with AL32UTF8, or any multi-byte character set, you must also set the initialization parameter nls_length_semantics=CHAR.

NOTE You do not need to specify a National Character Set. Maximo only supports Database Character Sets.

Task 2: Verify the Oracle Instance Requirements

The Oracle instance for Maximo must have Oracle Text installed. Maximo uses Oracle Text for indexes on description fields. You can verify that Oracle Text is installed by checking for the CTXSYS userid, as follows:

From SQL Plus, run the following command:

select username from dba_users where username = ‘CTXSYS’;

If Oracle Text is installed, this command will return the name CTXSYS.

NOTE The instance for Maximo will need at least 100MB of temporary tablespace and 100MB of undo tablespace.

If Oracle Text is not installed, refer to Oracle installation documentation for more detail.

Task 3: Tune the Oracle Initialization Parameters

IBM Corporation does not provide detailed performance settings for Maximo because there are an infinite number of combinations of data sizes, user counts, module usages, add-on module usages, system configurations, and customizations possible in a Maximo system. You may want to take advantage of all the features of Oracle 9.2 and 10g tuning, such as:

Use locally managed tablespaces for Maximo tables and indexes.

5. “Task 5: Create the Maximo Userid (Schema Name) for Oracle”, on page 5-4.

6. “Task 6: Create the Maximo Database Objects”, on page 5-5.



Oracle

Use the new method of PGA management by setting WORKAREA_SIZE_POLICY=AUTO and PGA_AGGREGATE_TARGET=memory value.

Use the new method of SGA management by setting SGA_TARGET = memory value.

Control I/O cache via DB_CACHE_SIZE instead of DB_BLOCK_BUFFERS.

Reduce library latch contention by setting CURSOR_SHARING= SIMILAR or FORCE.

Ensure OPTIMIZER_FEATURES_ENABLE is set to your current Oracle version and not an older one.

OPEN_CURSORS = 1000 estimated; you may need more.

DBMS_JOBS_PROCESSES = 2 required for job that updates Oracle Text indexes.

In addition to using the tuning features above, you can determine optimal sizing for SGA, PGA, and optimal performance adjustments, by using the Oracle Enterprise Manager (or a third-party database monitoring and administration tool) to analyze the database under load.

CAUTION If you have created the database with AL32UTF8 or any multi-byte character set, you must also set the initialization parameter nls_length_semantics=CHAR.

Task 4: Create Maximo Tablespace(s) for Oracle

This section explains how to create the required Maximo tablespace(s) in the Oracle instance. Use the following guidelines when creating tablespaces:

Maximo offers a multi-schema option. This feature enables the application tables to be owned by a user other than Maximo, permitting multiple Maximo schemas to reside in a single Oracle instance.

Maximo tablespaces should be locally managed and not dictionary managed. (The instructions that follow create a locally managed tablespace by default.)

If you do not include a schema owner, the default owner is Maximo.

Use related names for Maximo schemas and tablespaces. For example, to set up a MAXDEMO database, a production database, and a test copy of the production database, you might choose MAXDEMO, MAXPROD, and MAXTEST as schema owners and MAXDEMO_DATA, MAXPROD_DATA, MAXPROD_INDEX, MAXTEST_DATA, and MAXTEST_INDEX as tablespace names (MAXDEMO has only one tablespace name as splitting a small demo database has no real advantage).

Creating the Maximo Schema 5-3

Oracle

Determining Maximo Tablespace Size

The expected size of your database determines the size of a Maximo tablespace, as shown in the following table.

If you plan to install the MAXDEMO schema, create a Maximo tablespace of size 600MB.

If you plan to create an empty Maximo schema, use the estimated size of the database, as listed in the previous table.

To permit growth, you can add another datafile later or use the AUTOEXTEND option of the CREATE TABLESPACE command.

Command to Create a Maximo Tablespace

To create a Maximo tablespace in an Oracle instance, use the following command:

CREATE TABLESPACE <tablespace_name> DATAFILE ‘<file_name>’ SIZE <file_size> AUTOEXTEND ON MAXSIZE <maximum>;

where:

<tablespace_name> is the name of the Maximo tablespace.

<file_name> is the name of the data file. Use the full path of the server on which the data file exists, including the local drive, and enclose the full path in single quotes (‘). For example: ‘C:\oracle\oradata\MXES\MAXIMO01.DBF’

<file_size> is the initial size of the data file (see previous table), expressed as a number of megabytes (nM). For example, 1000M.

MAXSIZE <maximum> is the maximum size allotted to the data file (see previous table), expressed as a number of megabytes (nM). For example, 1000M.

You can customize the storage parameters for the particular database.

Task 5: Create the Maximo Userid (Schema Name) for Oracle

The multi-schema feature enables the application tables to be owned by a user other than Maximo, thus permitting multiple schemas to reside in a single Oracle instance.

To use different schema or tablespace names, edit the following parameters in createMaximoES.sql.

schema — the schema (userid) to own the tables (same value that you specified in Step 10 on page 4-2)

Size of Database Tablespace Estimate (MB)

Initial Maximum

Small (1–2 users) 500 2000

Medium (20–100 users) 1000 5000

Large (100+ users) 5000+ 20000+


Oracle

data_ts — the name of the table space to hold the Maximo tables (and indexes if the optional index table space is not used)

index_ts — the name of the table space to hold the Maximo tables

An example of createMaximoES.sql is shown below:

NOTE Ensure that the alter user schema temporary tablespace temp line reflects your temporary tablespace name.

Add the following line if you use a separate index tablespace:

alter user <schema> quota unlimited on <index_ts>;

To create the Maximo user, complete the following steps:

1 Open SQL Plus.

2 Login as system administrator.

3 At the prompt, type:

@”<drive_letter>:\<Maximo_installation_location>\tools\Maximo\en\createMaximoES.sql”;

4 Press Enter.

5 Exit SQL Plus.

Task 6: Create the Maximo Database Objects

After you create the Maximo user, create the Maximo database, as follows:

create user maximo identified by maximo;

alter user maximo default tablespace maximo quota unlimited on maximo;

alter user maximo temporary tablespace temp;

grant create trigger to maximo;

grant create session to maximo;

grant create sequence to maximo;

grant create synonym to maximo;

grant create table to maximo;

grant create view to maximo;

grant create procedure to maximo;

grant alter session to maximo;

grant execute on ctxsys.ctx_ddl to maximo;

--To allow Maximo to give Database Access to Maximo Users in Sig. Security, run these:

--grant create user to MAXIMO;

--grant drop user to MAXIMO;

--grant create session to MAXIMO with ADMIN OPTION;

--grant alter user to MAXIMO;

schema namepassword

data_ts tablespace

replace with your temporarytablespace name


Oracle

1 Open a command prompt

2 Change directory path to: \maximo\tools\maximo

3 At the prompt, type maxinst

Maximo reads the maximo.properties file (In this example, c:\Maximo\applications\maximo\properties) for database connectivity information. It then connects to the database (via the JDBC connection) and creates a Maxdemo database.

If you would like to create an empty database, use the -imaximo flag. For example, at the command prompt, instead of just maxinst, type:

maxinst -imaximo

The following table lists the flags that you can use with maxinst.

CAUTION -S and -T PARAMETERS: 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.

Flag Description

-a database alias Database alias. If not specified, uses mxe.db.url property.

-d log file directory If using the -l parameter, it will output logfile to the specified directory; otherwise, it outputs to the MXServer log directory, which typically is tools\maximo\log.

-e none Causes Sql to be executed. Required. Already present in maxinst.bat.

-f file name Filename for properties file. If not specified, uses maximo.properties.

-i file name Filename of input file (without path or extension). The default filename is Unlcvt if the -i param is not provided.

-k prop. file directory

Directory for properties file.

-l none Outputs a detailed log file. Strongly recommended. Already in maxinst.bat.

-o file name If using the -l parameter, the filename for the logfile. If not specified, logfile is "Maxinst" + timestamp + ".log".

-p password Password for database connection. If not specified, uses mxe.db.password property, or MAXIMO (must be all capital letters).

-s index tablespace Tablespace for index storage.

-t table tablespace Tablespace for table storage.

-u user name Username for database connection. If not specified, uses mxe.db.user property, or MAXIMO (must be all capital letters).

-x doclink file separators

This parameter fixes the doclink (Attached Documents) file separators. If a UNIX environment is deployed without using this parameter, the doclinks will not work properly.


Oracle

The -X flag is required for UNIX environments.

CAUTION If MAXINST fails for any reason, you must drop and recreate the Maximo schema before re-running MAXINST.

NOTE Each flag must be followed by the parameters without a space, for example: -uMAXIMO.


DB2

DB2

To create the Maximo schema using a DB2 database, perform the following tasks as described in this section.

Task 1: Ensure Requirements and Gather Information

Maximo supports IBM DB2 UDB version 8.2 residing on any platform that supports connection from the DB2 clients, including: AIX, Microsoft Windows 2003, and RedHat Enterprise Linux 3. Ensure that the DB2 server is configured to support TCP/IP.

Determine and record the following information you need to connect DB2 to Maximo:

server host name or IP address

TCP/IP port number that DB2 is using to listen to inbound requests (default is 50000)

database name

DB2 schema and tablespace name (see your DB2 Database Administrator for the required names)

User ID and password that enables full read access to the database. (The user you use to connect Maximo to DB2 must have full access to the DB2 schema and the tablespaces used to store data.)

NOTE If you use Actuate as your reporting tool, enter the Maximo user ID and password in upper case.

Task 2: Specify a Character Set for the DB2 Database

Maximo supports multiple languages within a single schema. Create the DB2 database instance with the character set that supports the languages you intend to use. Maximo release 6.2.1 does not support the Unicode character set with DB2. Valid DB2 codepages (character sets) are as follows:

Task DB2 - Task description and location

1. “Task 1: Ensure Requirements and Gather Information”, on page 5-8.

2. “Task 2: Specify a Character Set for the DB2 Database”, on page 5-8.

3. “Task 3: Configure DB2 Parameters”, on page 5-9.

4. “Task 4: Create the Maximo Database Objects”, on page 5-9.

DB2 Codepages (character sets)

Chinese GBK


DB2

Task 3: Configure DB2 Parameters

To optimize DB2 for interaction with Maximo, you tune it using configuration parameters. Before so doing, 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 to which you plan to connect Maximo:

1 db2 bind db2schema.bnd

2 db2 bind @ db2cli.lst clipkg 4

NOTE Run the above bind commands from a DOS command prompt by navigating to the BND location. For example, C:\IBM\SQLLIB\BDN

Tuning DB2 Configuration Parameters

Note: IBM Maximo does not provide detailed configuration parameter settings for Maximo because there are infinite combinations of data sizes, user counts, module usages, add-on module usages, system configurations, and customizations possible in a Maximo system. Your DB2 System Administrator can help ensure proper tuning of the database configuration parameters: APP_CTL_HEAP_SZ, LOCKLIST and MAXLOCKS.

Task 4: Create the Maximo Database Objects

You create the Maximo database by running maxinst, which populates DB2 with the specific database objects Maximo requires. To do so, proceed as follows:

1 Open a command prompt.

2 Change directory path to: \maximo\tools\maximo

3 At the prompt, type maxinst -s -t

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 JDBC connection and then creates a Maxdemo

Dutch IBM-1252

French IBM-1252

German IBM-1252

Italian IBM-1252

Japanese IBM-943

Korean 1363

Portuguese IBM-1252

Spanish IBM-1252

Swedish IBM-1252

DB2 Codepages (character sets)


DB2

database. If you would like to create an empty database, use the -imaximo flag.

For example, at the command prompt, instead of just maxinst, type: maxinst -imaximo

The following depicts the various flags that you can use with maxinst.

CAUTION -S and -T PARAMETERS: 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.

The -X flag is required for UNIX environments.

CAUTION If MAXINST fails for any reason, you must drop and recreate the Maximo schema before re-running MAXINST.

NOTE Each flag must be followed by the parameters without a space, for example: -uMAXIMO.

Flag Description

-a database alias Database alias. If not specified, uses mxe.db.url property.

-d log file directory If using the -l parameter, it will output logfile to the specified directory; otherwise, it outputs to the MXServer log directory, which typically is tools\maximo\log.

-e none Causes Sql to be executed. Required. Already present in maxinst.bat.

-f file name Filename for properties file. If not specified, uses maximo.properties.

-i file name Filename of input file (without path or extension). The default filename is Unlcvt if the -i param is not provided.

-k prop. file directory

Directory for properties file.

-l none Outputs a detailed log file. Strongly recommended. Already in maxinst.bat.

-o file name If using the -l parameter, the filename for the logfile. If not specified, logfile is "Maxinst" + timestamp + ".log".

-p password Password for database connection. If not specified, uses mxe.db.password property, or MAXIMO (must be all capital letters).

-s index tablespace Tablespace for index storage.

-t table tablespace Tablespace for table storage.

-u user name Username for database connection. If not specified, uses mxe.db.user property, or MAXIMO (must be all capital letters).

-x doclink file separators

This parameter fixes the doclink (Attached Documents) file separators. If a UNIX environment is deployed without using this parameter, the doclinks will not work properly.


DB2

Troubleshooting the DB2 Configuration

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 located 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, IBM recommends you use a text editor other than Notepad to open the file.


Microsoft SQL Server


To create the Maximo schema using a SQL Server database, perform the following tasks as described in this section.

Task 1: Verify the Microsoft SQL Server Instance Requirements

Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server 2000. To determine if Full-text Search is installed on your existing Microsoft SQL Server database, perform the following steps:

1 Open SQL Query Analyzer from the Tools menu.

2 Type the following command:

select FULLTEXTSERVICEPROPERTY ( 'IsFulltextInstalled' )


1. “Task 1: Verify the Microsoft SQL Server Instance Requirements”, on page 5-12.

2. “Task 2: Create a SQL Server Database for Maximo”, on page 5-14.

3. “Task 3: Create the Maximo User for SQL Server”, on page 5-16.

0 = Full-text is not installed (in this example)1 = Full-text is installed



In the event that you did not install Full-text Search (the resulting value is zero), you must do so at this time. The following steps provide a general guideline describing how you can change this and other settings after having installed SQL Server.

1 Insert the Microsoft SQL Server 2000 CD-ROM onto the server where you had it installed originally.

2 Navigate through the installation dialog boxes and from the Setup Type dialog box, select Custom.

3 Check the Full-Text Search option.

4 Complete remaining installation steps. You finish the installation process by choosing to restart the server.



Task 2: Create a SQL Server Database for Maximo

Complete the following steps to create a SQL Server Database.

1 Open SQL Server Enterprise Manager (from Program Files >> Microsoft SQL Server).

2 Right Click the Databases folder from the tree view, and select New Database.

3 In the Database Properties dialog box, in the General tab, specify a unique database name (for example max602db).



4 From the Data Files tab, change the Space allocated size to 500 (MB) and check the Automatically grow file check box.

5 If you prefer, from the Transaction Log tab modify the settings to accommodate your production environment.

6 Click OK.



Task 3: Create the Maximo User for SQL Server

1 Open the Tools menu and select SQL Server Analyzer.

2 Select the correct database name from the drop-down menu. This is the value you entered in Step 3 on page 5-14.

3 Run the following scripts:

a To create the Maximo user, run the following script:

sp_addlogin MAXIMO,MAXIMOgo

If the maximo account is already present in the SQL Server installation, then you will get an error message “login maximo already exists.” You can ignore this error message.

b Change maximo to be the database owner by running the following script:

sp_changedbowner MAXIMOgo

c If you intend to use the Users app to add native database logins and users, then run the following script:

sp_addsrvrolemember MAXIMO, securityadmingo

Maximo01



4 You can now run the maxinst script from the <Maximo_home>\tools\Maximo folder from the machine where you installed Maximo.

To finish creating the Maximo schema using a SQL Server database, see “Task 4: Create the Maximo Database Objects”, on page 5-9.




This chapter describes how to create a new Maximo Application Server (MAXIMOSERVER) using IBM WebSphere 6.0.2.17 Administrative Console. An application server is a server that provides services required to run enterprise applications, such as Maximo.

Before creating the Maximo Application Server, you must create a Windows Service for the Node Agent.

Creating a Windows Service for the Node Agent

Complete the following steps:

1 Open a command prompt.

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

3 Type the following command with no line breaks (case-sensitive).

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\startServer.log" -restart true

4 Close the Command Prompt.

Creating the Maximo Application Server and Deploying the EAR Files

6


Creating the Maximo Application Server


Complete the following steps to create the MAXIMOSERVER Application Server.

1 Ensure that the WebSphere related services and processes are running. See “System Server Administration”, on page A-1.

1 Invoke a browser window (preferably from the machine where you have installed Maximo) and open the Administrative Console by typing in the browser address bar: http://<machine_name>:9060/admin

This URL address depicts the default port number (9060) and context (admin) for the Administrative Console.

2 Enter a username to login.

You can use any name to log in. Security is not enabled.

You can set security levels for various user privileges. See the IBM Maximo System Administrator’s Guide for more details.

9060



3 Expand the Servers link and click Application servers.

4 Click New.

5 Type MAXIMOSERVER (or specify a unique Server name) and click Next.

Creating the Maximo Application Server and Deploying the EAR Files 6-3


6 Accept all default settings and click Next.

7 Accept default settings and click Next.



8 Click Finish.

9 Check the MAXIMOSERVER check box and click save.



10 Check the Synchronize changes with Nodes check-box and click Save.

The main page appears:

You are now ready to configure the MAXIMOSERVER application server.



Editing JVM Memory Settings

In this section you set the initial and maximum JVM memory size.

Initial java heap size — 512

This setting specifies the initial memory size (in MB) required to start the server.

Maximum java heap size — 1024

This setting specifies the maximum memory size (in MB) for the server.

Do not set the java heap size so that it exceeds the physical memory (RAM) of your server. Complete the following steps:

1 From the Servers link in the tree view click Application servers.

2 Click MAXIMOSERVER in the main window.

3 From the Server Infrastructure group, expand the Java and Process Management link.



4 Click Process Definition.

5 Click Java Virtual Machine.



6 Scroll down and type 512 for Initial Heap Size and 1024 for Maximum Heap Size and click OK.

Specify the memory size



7 Click Save in the messages box.




Adding a Redirect to IBM WebSphere 6.0.2.17 for Actuate

Complete the following steps to add a redirect to IBM WebSphere 6.0.2.17 for Actuate.

1 From Application servers > MAXIMOSERVER > Java and Process Management > Process Definition > Java Virtual Machine, click the Custom Properties link.

2 Click New.



3 In the General Properties section, type the following values:

a Name: com.ibm.websphere.sendredirect.compliance

b Value: 1

c Description: Redirect for Actuate

d Click Apply.

4 Click Save in the message box.

5 Check Synchronize changes with Nodes and click Save.


Identify the HTTP Transfer Port Numbers


You must identify the default port that IBM assigns for you to access Maximo Start Center from a browser. You can also change that port number. Complete the following steps:

1 Expand Servers > Application servers, and click MAXIMOSERVER from the main window.

2 Open the Web Container Settings and click the Web container transport chains.



3 Note the default port number as it appears with WCInboundDefault (9080).

If you choose to use port number 9080, then continue with the next section: Creating Virtual Host. Otherwise, continue with the next step to create another port number. The same port number that you specified on page 4-1, other than 9080.

4 Click New in the Transport Chain window.

5 Specify a transport chain name. In this example: MAXIMOTRANSPORT. Click Next.



6 In the Create New Transport Chain, complete the following sub-steps:

a Specify a port name.

b Type * (star) for Host.

c Type the new port number (not the default 9080) that you specified on page 4-1.

d Click Next.

7 Click Finish.



8 Click Save.




Creating Virtual Host

Complete the following steps to create a virtual host.

1 Expand the Environment link from the tree view.

2 Click Virtual Hosts.

3 Click New.



4 In the General Properties section, type MAXIMOSERVER_host in the Name box.

5 Click Apply.

6 Click Save.




8 From the Virtual Hosts window, click MAXIMOSERVER_host.

9 Click the Host Aliases link.



10 Click New.

11 Type * (star) for Host Name and type the HTTP port number (by default 80).



12 Click OK.

13 Don’t save yet. Click New.

Type * (star) for Host Name and type the port number that you specified in Step 6 on page 6-15 for the HTTP port number.

14 Click Apply and then click OK. You must apply this setting before saving the settings in the next step.



15 Click Save in the message box.



Deploying the EAR Files


If you are a MEA customer and you selected the MEA option (Step 14 on page 4-3), you must first complete the steps in Appendix B, before deploying the EAR files.

Complete the following steps to deploy the EAR files.

1 Expand the Applications link and click Install New Applications. Depending whether the browser that you are using is on the same machine where you have installed Maximo (Local) or not, select the appropriate option and navigate to where the EAR files reside (/maximo/deployment/default). Click Next.



2 Check Generate Default Bindings and click Next.

3 Click Continue in the Applications Security Warnings window.




5 Complete the following steps:

a Select all Modules.

b Select both servers that appear in the Clusters and Servers box.

c Click Apply.

d Click Next.




If you are a MEA customer, you will see the following window. Accept the default settings and click Next to continue. If you are not a MEA customer you will not see the following screen. Continue with the following step.

Selected by default







9 Complete the following sub-steps:

a Select all Web Modules.

b From the Virtual host drop-down list, select MAXIMOSERVER_host for all modules.

c Click Next.





12 Accept default settings and click Finish.



13 Allow the process to complete and click Save to Master Configuration.




15 Repeat all the steps in this section (Deploying the EAR Files) to deploy maximohelp.ear and acweb.ear.

16 Expand the Servers link from the tree view and click Application servers.

17 Select MAXIMOSERVER and click Start. Allow for the Status to change to a green arrow.

18 Expand the Applications link and click Enterprise Applications.

19 Ensure that all three Applications (only Maximo shown here) are running.

20 You may log out of the console at this time and close the browser session.




If you installed Actuate in Chapter 3, then complete the steps outlined in this chapter to install the Actuate Encyclopedia for Maximo. The reason that you are installing an Actuate-related component at this time, is that, only now you can access the Actuate Administrative Console, after having deployed the acweb.ear file in the previous chapter.

The Encyclopedia is a collection of Maximo-specific reports, user roles, and user permissions that are copied during installation and placed in the Actuate8/iServer/encyc folder.

You must install the Actuate Encyclopedia for Maximo on the same machine where you installed the Actuate iServer. Before you install the Actuate Encyclopedia for Maximo, ensure:

To remove corrupted characters from the acserverconfig.xml file. This applies only to Chinese, Japanese, and Korean languages.

That the Actuate iServer application is running.

That the MAXIMOSERVER application server is running.

After installing the Actuate Encyclopedia for Maximo, if you selected any language other than English, and you are connecting to a SQL Server database, you must modify language-specific JDBC settings, similar to the procedure at the end of Chapter 4. You must also rebuild and re-deploy the acweb.ear file before Importing the Encyclopedia.

Starting the Actuate iServer for Maximo

By default the Actuate iServer starts automatically when your system reboots. If you did not choose to start the Actuate iServer automatically, use the Services panel to start the service. Complete the following steps:

1 From the Control Panel >> Administrative Tools, click Services.

2 Right-click the Actuate Process Management Daemon 8 service name.

3 Click Start.

The Process Management Daemon (PMD) starts automatically after the Actuate iServer installation. The PMD starts the Report Server services. You can also start the PMD from the command line.

Installing The Actuate Encyclopedia for Maximo 7


Starting the Actuate iServer for Maximo

1 From a command prompt change directory to the C:\ drive (or your root Actuate installation folder).

2 To start the PMD, type:

net start “Actuate Process Management Daemon 8”


Installing the Actuate Integration for Maximo


You are now ready to install the Actuate Integration for Maximo. Complete the following steps:

1 Insert the Actuate Reporting Release 8 English Encyclopedia for Windows CD-ROM into the CD drive.

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


If your language is not available from the list, select English, and click OK.If it is Japanese or Chinese you must have those fonts installed on your system.For any selected language other than English, that you are installing on a SQL Server database, you must perform certain post-installation tasks as described in this chapter. This procedure does not apply if you are using Oracle database.

4 Click Next in the Introduction dialog box.

5 Accept the default installation location (c:\Actuate8\iServer\ActuateIntegration) or select another location. Click Next.

6 Enter the required information. Ensure that the Administrator’s password is the same password you specified on Step 12 on page 3-7. Click Next.

7 Select the appropriate database and click Next.

8 Depending on your database type, enter the following database-related information, and click Next.

9 Enter the necessary information to connect to Maximo. Ensure that the Maximo Server Name is the same value as that in Step 15 on page 4-3 and click Next.

DB2 SQL Server Oracle

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

Enter the Oracle host name

Port number 50000 (default) 1433 (default) 1521 (default)

Database name Enter the Service name of the DB2 instance

Enter the SQL Server database name

Enter the Oracle system identifier

Database owner MAXIMO (default) MAXIMO (default) MAXIMO (default)

Database owner’s password

MAXIMO (default) MAXIMO (default) MAXIMO (default)

Installing The Actuate Encyclopedia for Maximo 7-3


10 Click Install.

11 Click Next to check for Actuate Updates.

12 Check the check box in the Update dialog box and click Done.

The PowerUpdate wizard opens. The computer where you are performing this installation from must be connected to the Internet.

13 Click Next in the Welcome to PowerUpdate dialog box.

The PowerUpdate program checks for available updates at this time.

14 There are no updates available for this release of the Actuate Encyclopedia. Click Done.




NOTE Perform the tasks outlined in this section only if you are installing a non-English language, and you are using SQL Server database; otherwise, ignore this section and the post-installation tasks in this chapter.

You must modify the JDBC settings in order for Maximo and Actuate Reporting to work properly with translated databases that contain special characters. For example: French, Swedish, or double-byte languages such as Chinese, Japanese and Korean.

In this section you edit three files: actuatei18ntext.properties, which resides in two separate locations (One is located in the Maximo directory and the other is located in the Actuate directory); plus, the rsse_properties.maximo file located in the Actuate directory structure. You can modify one of them and copy it to the second location.

Complete the following steps to modify the actuatei18ntext.properties file in the Maximo directory:

1 Using Windows Explorer, navigate to <Maximo_root_directory>\applications\activeportal\WEB-INF\classes\com\actuate\ExternalText

2 Using a text editor, open the actuatei18ntext.properties file.

3 Search for the following entry: actuate.externText.JDBCConnectionURL=jdbc:inetdae7a

Example of the actuate.externalText.JDBCConnectionURL setting before making changes





Chinese (Simplified) : GBKDutch : 8859_1French : 8859_1German : 8859_1Italian : 8859_1Japanese : Shift_JISKorean : euc-kr



Portuguese : 8859_1Spanish : 8859_1Swedish : 8859_1


6 Save the file (do not close it yet).

7 Copy the modified actuatei18ntext.properties file and then paste it in the following location under the Actuate directory:

<Actuate_root_directory>\iServer\bin\com\actuate\ExternalText

when prompted to replace the existing file, click OK.

NOTE If you have multiple instances of Maximo, complete the steps outlined in this section for each of the actuatei18ntext_rsseAlias.properties file that you have.

You must now modify the rsse_maximo.properties page, which resides in the Actuate directory. Complete the following steps:

1 Using Windows Explorer, navigate to <Actuate_root_directory>\iServer\etc

2 Using a text editor, open the rsse_maximo.properties file.

Search for the following string: jdbc.url=jdbc:inetdae7a

Example of the jdbc.url setting before making any changes.




Remove the aAdd &charset=<the code> after true


Removing Corrupt Characters from the acserverconfig.xml File


Chinese (Simplified) : GBKDutch : 8859_1French : 8859_1German : 8859_1Italian : 8859_1Japanese : Shift_JISKorean : euc-krPortuguese : 8859_1Spanish : 8859_1Swedish : 8859_1


5 Save and close the file.

NOTE If you have multiple instances of Maximo, complete the steps outlined in this section for each of the rsse_maximo.properties files that you have.

6 You must now rebuild and re-deploy the acweb.ear file. Refer to the IBM Maximo System Administrator’s guide for more details.

7 Restart the Actuate iServer and the Actuate Process Management Daemon. See “Starting the Actuate iServer for Maximo”, on page 7-1.

Removing Corrupt Characters from the acserverconfig.xml File

NOTE This section applies only to systems that use Chinese, Japanese, or Korean system locale.

If you are installing on systems that use Chinese, Japanese, or Korean system locale, the acserverconfig.xml file (located in the Actuate iServer directory) is saved improperly by the Actuate Encyclopedia installation program. The file name is appended with corrupted characters and a question mark at the beginning of the file. The result is that the Actuate iServer is unable to read the file or to startup properly. Complete the following steps to remedy this issue:

1 Shut down the Actuate application server.

2 Using a text editor, open the acserverconfig.xml file located in the <Actuate_iServer_root>\iServer\etc directory.

3 Note the corrupted character and a question mark at the beginning of the file. Remove them and save the file.

4 Re-start the Actuate application server.


Importing the Encyclopedia


Ensure that the Maximo Application Server is running while you are importing the encyclopedia. If at any point, the Maximo Application Server is re-started, the Actuate service must be restarted too.

1 Login to the Actuate Admin Console (http://<host_name>:8900/acadmin) from the machine where you have installed the Actuate iServer.

2 Change the Volume Name drop down to System Administration.

3 Login as Administrator.

4 Select the System tab (if not selected by default already).



5 Click the Stop button on the System tab.

6 Click OK in the ensuing message box. Wait 1 to 2 minutes for the Stop to take effect.

7 Using Windows Explorer, navigate to your Actuate installation location: <drive_letter>:\Actuate8\iServer.

8 Delete the encyc folder found under the \Actuate8\iServer folder.

9 Open a command prompt and change path to Actuate’s bin directory. For example: C:\actuate8\iServer\bin

10 Execute the acimport.bat script.

11 After importing the Encyclopedia, go back to the Actuate Admin Console and Start the Volume.




The final step in installing the Maximo system is opening the Maximo Start Center window.

Ensure that the Maximo Application Server is running.

1 To open Maximo login page, launch Internet Explorer and in the URL address bar type: http://<host_name>:<port_number>/maximo

where

<host_name> is the machine name or IP address of the application server

<port_number> is the Listen Port number value that you specified on page 4-1.

For example: http://computername:9080/maximo

NOTE The context path (maximo) is case-sensitive.

The Maximo login page opens.

Logging Into Maximo Start Center 8

9080


MEA Users

2 Login as maxadmin for both username and password. Newly installed Maximo databases contain maxadmin as a user ID with unlimited system access. You cannot use Maximo or SYSADM.

MEA Users

If you have obtained the MEA Product Enabler, you must complete additional integration steps that are detailed in Chapter 6 of the IBM Maximo Enterprise Adapter System Administrator’s Guide.


oo

This Appendix describes how to start and stop various services from the Services window and also from a command prompt.

Ensure that you have logged in as a user with Administrative rights to successfully start the IBM-related servers.

You must start the IBM HTTP Server prior to starting IBM WebSphere’s Network Deployment or the Node Agent servers.

Starting the Services from the Windows Services Panel

1 From Settings >> Control Panel >> Administrative Tools double click and open the Services panel.

2 Right-click on the desired name and select the appropriate action.

IBM HTTP Administration 6.0IBM HTTP Server 6.0IBM WebSphere Application Server V6 — ComputerNameIBM WebSphere Application Server V6 — Node Agent

System Server Administration A

© Copyright IBM Corp. 2007 A-1

Starting the Services from a Command Prompt

You can also start the following services from a command prompt. .

Starting the MAXIMO Application Server

The following steps describe how to start the MAXIMO Application Server from the IBM Network Deployment Administrative Console.

1 From your browser, invoke the IBM Network Deployment Administrative Console: http://<servername>:9060/console

2 From the tree view in the left pane, open the Servers link.

3 Under the Servers link, click Application servers.

4 Select the appropriate server (MAXIMOSERVER) by checking the box next to the server name.

5 Click Start.

The Status icon of the application server (MAXIMOSERVER) changes to an arrow ( ).

To stop the server from running, click Stop and the status icon changes to an x ( ).

Server Name Browse to... To Start, type... To Stop, type...

IBM HTTP Server \IBMHTTPServer\bin Apache.exe -k start

Apache.exe -k stop

IBM WebSphere Deployment Manager

\IBM\WebSphere\AppServer\profiles\Dmgr01\bin

startManager.bat stopManager.bat

IBM WebSphere Node Agent

\IBM\WebSphere\AppServer\profiles\Custom01\bin

startNode.bat stopNode.bat

1. Click Servers

3. Check box

4. Click Start

2. Click Application servers

2

A-2 IBM Maximo: Installation Guide

To configure the JMS queues, complete the following steps:

1 Start the WebSphere application server.

2 Launch Internet Explorer and open the WebSphere Administrative Console by typing the following URL:

http://<machine_name>:<port_number>/ibm/console

For example, enter a URL similar to the following:

http://localhost:9060/ibm/console

3 At the Welcome, please enter your information login screen, enter your User ID, then click Log in.

This action opens the Welcome screen for the WebSphere Administrative Console.

4 Click Service Integration > Buses to open the Buses dialog box as shown below:

The Buses Dialog Box

NOTE A bus is a group of interconnected servers and clusters that have been added as members of the bus.

5 Click New to open the Buses > New dialog box where you can add a new service integration bus.

Configuring JMS Options for MEA B

© Copyright IBM Corp. 2007 B-1

The Buses > New Dialog Box

6 To add a new service integration bus, enter the following information:

Text description of the new bus in the Name field, for example, meajmsbus.

Deselect the Secure check box. If you leave this box checked, meajmsbus inherits the Global Security setting of the cell.

Change the value of the High message threshold field to a minimum value of 500,000 messages.

Accept all other default settings.

If the number of messages awaiting processing exceeds the High Message Threshold you set, the application server will take action to limit the addition of new messages in the processing queues.

Depending on your message requirements, you may want to enter a higher message threshold value. You can determine an optimal message threshold setting by monitoring the messaging in/out queues and the impact of the message threshold setting on system performance. You might, for example, lower the threshold value if a higher value is degrading system performance.

NOTE If you decide to change the High message threshold setting after the initial configuration, you must open the Additional Properties menu in the Administrative Console and change the threshold value for each child configuration.

B-2 IBM Maximo: Installation Guide

ers to the JMS Bus

7 Click Apply to create the new service integration bus. This step propagates the JMS bus setup to the cluster configuration. Confirm that build completed screen displays the following:

Bus name, for example, meajmsbus.

Auto-generated, unique ID (UUID), for example, 4BCAC78E15820FED.

The Secure field is unchecked.

High Message Threshold field has a minimum value of 500,000.

Adding Servers to the JMS Bus

To add servers to the JMS bus, complete the following steps:

1 From the WebSphere Administrative Console, click Service Integration > Buses to open the Buses dialog box as shown below:

The Buses - meajmsbus

2 Click meajmsbus to open the Buses > meajms dialog box.

3 Under Topology, click Bus members.

4 In the Buses > meajmsbus > Bus members dialog box, click Add to open the Add a new bus member dialog box as shown in the following figure:

Adding Serv

Configuring JMS Options for MEA B-3

Adding Servers to the JMS Bus

The Buses - Add a New Bus Member

5 Click the Server drop-down arrow, and select a server name, for example QAERP7Node01.server1 to add to the bus.

6 Click Next.

7 Click Finish.

8 Click Save.

9 Ensure to check Synchronize changes with Nodes and click Save.


nd (cqinbd) Queue

The Configuration > General Properties dialog box for the new bus member, server QAERP7, appears similar to the following:

The Buses - General Properties for New Bus Member

Creating the JMS Bus Destination for the Continuous Inbound (cqinbd) Queue

To add a logical address for the continuous inbound bus destination queue (cqinbd) within the JMS bus, complete the following steps:

1 From the WebSphere Administrative Console, click Service Integration > Buses to open the Buses dialog box.


3 Click Destinations under Destination resources to open the Buses > meajmsbus > Destinations dialog box as shown in the following figure:

Creating the JMS Bus Destination for the Continuous Inbou


Creating the JMS Bus Destination for the Continuous Inbound (cqinbd) Queue

The Buses - Add a New Bus Destination

NOTE A bus destination, for example cqinbd, is a virtual place within a service integration bus where applications can attach and exchange messages.

4 Click New to open the Create new destination dialog box.

5 Leave Queue checked as the destination type, and click Next to open the Create new queue dialog box.

6 Type cqinbd in the Identifier field and Continuous Queue Inbound in the Description field, then click Next to open the Create a new queue for point-to-point messaging dialog box.

The Buses - Add the cqinbd Bus Destination Queue to a Bus Member

7 Select the Bus Member pull-down and choose a server, such as QAERP7... as the bus member that will store and process messages for the cqinbd bus destination queue.

8 Click Next to open the Confirm queue creation dialog box.


nd (cqinbd) Queue

The Buses - Confirm the Creation of the cqinbd Bus Destination Queue

9 Review your selections, then click Finish to complete the creation of the cqinbd bus destination queue.

10 Navigate the path Buses > meajmsbus > Destinations, then click cqinbd to open the configuration dialog box where you must make the following changes:

Change the Maximum failed deliveries value to 1.

This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination.

Click None as the Exception destination value.

The following figure is a partial snapshot of the cqinbd configuration dialog box.

The Buses - Configuration Changes to the cqinbd Bus Destination Queue

11 Click Apply.

Creating the JMS Bus Destination for the Continuous Inbou


12 Click Save.


Creating the JMS Bus Destination for the Sequential Inbound (sqinbd) Queue

To add a logical address for the sequential inbound bus destination queue (sqinbd) within the JMS bus, complete the following steps:



3 Click Destinations under Destination resources to open the Buses > meajmsbus > Destinations dialog box.

NOTE A bus destination, for example sqinbd, is a virtual place within a service integration bus where applications can attach and exchange messages.



6 Enter sqinbd in the Identifier field and Sequential Queue Inbound in the Description field, then click Next to open the Create a new queue for point-to-point messaging dialog box.

7 Select the Bus Member pull-down and choose a server, such as QAERP7... as the bus member that will store and process messages for the sqinbd bus destination queue.


9 Review your selections, then click Finish to complete the creation of the sqinbd bus destination queue.

10 Navigate the path Buses > meajmsbus > Destinations, then click sqinbd to open the configuration dialog box where you must make the following changes:




11 Click Apply.

Creating the JMS Bus Destination for the Sequential Inbound (sqinbd) Queue


d (sqoutbd) Queue

12 Click Save.


Creating the JMS Bus Destination for the Sequential Outbound (sqoutbd) Queue

To add a logical address for the sequential outbound bus destination queue (sqoutbd) within the JMS bus, complete the following steps:



3 Click Destinations under Destination resources to open the Buses > meajmsbus > Destinations dialog box.

NOTE A bus destination, for example sqoutbd, is a virtual place within a service integration bus where applications can attach and exchange messages.



6 Enter sqoutbd in the Identifier field and Sequential Queue Outbound in the Description field, then click Next to open the Create a new queue for point-to-point messaging dialog box.

7 Select the Bus Member pull-down and choose a server, such as QAERP7... as the bus member that will store and process messages for the sqoutbd bus destination queue.


9 Review your selections, then click Finish to complete the creation of the sqinbd queue.

10 Navigate the path Buses > meajmsbus > Destinations, then click sqoutbd to open the configuration dialog box where you must make the following changes:




11 Click Apply.

Creating the JMS Bus Destination for the Sequential Outboun


12 Click Save.


Creating the MEA Connection Factory

You add a connection factory for creating connections to the associated JMS provider of point-to-point messaging queues.

1 From the WebSphere Administrative Console, click Resources > JMS Providers > Default Messaging to open the Default messaging provider dialog box.

2 Click Browse Nodes.

Creating the MEA Connection Factory


onnection Factory

3 Select the Node, (not the cell Manager) and click OK.

4 Under Connection Factories, click JMS queue connection factory.

to open the following figure:

2

2

Creating the MEA C


5 Click New to complete the General Properties section for the new connection factory. For example, you minimally need to enter the information below as shown in the following figure:

Name – meaconfactJNDI name – jms/mro/int/qcf/intqcfBus name – meajmsbus

JMS Providers - Add general properties for new connection factory

6 Click OK to add meaconfact as a new JMS queue connection factory.

7 Click Save.


Creating the Continuous Inbound (cqin) JMS Queue

You must create a JMS queue (cqin) as the destination for continuous inbound point-to-point messages.


2 Under Destinations, click JMS queue to open the JMS queue dialog box where you can create a new queue for continuous inbound messages.

3 Click New to complete the General Properties section for the new continuous inbound messaging queue. For example, you minimally need to enter the information below as shown in the following figure:

Name – cqinJNDI name – jms/mro/int/queues/cqinBus name – meajmsbusQueue name – cqinbd

Creating the Continuous Inbound (cqin) JMS Queue


(sqin) JMS Queue

JMS Providers - Add General Properties for Continuous inbound Queue (cqin)

4 Click OK.

5 Click Save.


Creating the Sequential Inbound (sqin) JMS Queue

You must create a JMS queue (sqin) as the destination for sequential inbound point-to-point messages.


2 Under Destinations, click JMS queue to open the JMS queue dialog box where you can create a new queue for sequential inbound messages.

3 Click New to complete the General Properties section for the new sequential inbound messaging queue. For example, you minimally need to enter the following information:

Name – sqinJNDI name – jms/mro/int/queues/sqinBus name – meajmsbusQueue name – sqinbd

4 Click OK.

5 Click Save.


Creating the Sequential Inbound


Creating the Sequential Outbound (sqout) JMS Queue

You must create a JMS queue (sqout) as the destination for sequential outbound point-to-point messages.


2 Under Destinations, click JMS queue to open the JMS queue dialog box where you can create a new queue for sequential outbound messages.

3 Click New to complete the General Properties section for the new sequential outbound messaging queue. For example, you minimally need to enter the following information:

Name – sqoutJNDI name – jms/mro/int/queues/sqoutBus name – meajmsbusQueue name – sqoutbd

4 Click OK.

5 Click Save.


Creating JMS Activation for the Continuous Inbound Queue (cqin)

You must activate the continuous inbound queue (cqin) before it can receive messages. Complete the following steps to activate the cqin queue:


2 Under Activation Specifications, click JMS activation specification to open the JMS activation specification dialog box where you can create an activation configuration that will enable cqin to receive inbound messages.

3 Click New to complete the General Properties section for the new JMS activation specification. For example, you minimally need to enter the following information:

Name – meajmsactJNDI name – meajmsactDestination type – Queue (default)Destination JNDI name – jms/mro/int/queues/cqinBus name – meajmsbusMaximum batch size – 10Maximum concurrent endpoints – 5

Creating the Sequential Outbound (sqout) JMS Queue


ound Queue (cqin)

The following figure shows the General Properties dialog box (note that you have to scroll down in the dialog box to view Maximum batch size and Maximum concurrent endpoints):

JMS Providers - Add General Properties for JMS Activation of the cqin Queue

4 Click OK.

5 Click Save.


7 Ensure to stop all IBM-related processes and daemons. See Appendix A for more details.

8 You must now restart these processes for the update to take effect.

If Maximo is already installed on your application server, you must rebuild and deploy the Maximo.ear file. Refer to the IBM Maximo System Administrator’s Guide for detailed instructions.

Creating JMS Activation for the Continuous Inb


Creating JMS Activation for the Continuous Inbound Queue (cqin)


Ensure that Maximo is not running. At this time you must install the additional Product Enablers program you received. The EAR files are built at this time. Complete the following steps.

1 Stop the Maximo Application Server (MAXIMOSERVER) process.

2 Insert your Product Enabler CD-ROM into the CD drive.

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





7 Click Install in the Pre-Configuration Message box.


8 If you are installing additional Product Enablers, select Yes and the program exits. You must now insert other Product Enabler CD-ROM(s) that you may have obtained, otherwise select No and click Done.

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

9 Click Done in the Install Complete dialog box.

Adding Additional Product Enablers C

© Copyright IBM Corp. 2007 C-1

C-2 IBM Maximo: Installation Guide

As the Actuate Reports administrator, you must set up additional Actuate functionality to run Reports properly. Complete the following steps:

1 To enable reports to execute, sign into Maximo as someone with Admin Privileges.

2 Select the Report Administration Application.

3 Click Recreate all XML on the List tab.

4 Wait until the message The request page XML has been generated displays.

You can now run Reports properly.

Enabling Reports to Run D

© Copyright IBM Corp. 2007 D-1

D-2 IBM Maximo: Installation Guide

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those

© Copyright IBM Corp. 2007 Notices-1

Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

AIX, IBM, IBM Corporation, the IBM logo, Tivoli, and WebSphere are registered trademarks of the International Business Machines Corporation in the United States, other countries, or both.

Intel, the Intel logo, and Pentium are registered trademarks of the Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, and Internet Explorer are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Notices-2 IBM Maximo: Installation Guide

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks of Sun Microsystems, Inc.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Notices-3

Notices-4 IBM Maximo: Installation Guide