164
Release 6.2.1 Installation Guide UNIX | IBM WebSphere IBM Maximo

IBM Maximo Installation Guide - UNIX | IBM WebSpherepublib.boulder.ibm.com/tividd/td/ITMax/621_mx_install_was60_unix/... · IBM WebSphere Fix Pack Installation RoadMap ... viii IBM

  • Upload
    hahanh

  • View
    277

  • Download
    6

Embed Size (px)

Citation preview

  • Release 6.2.1

    Installation GuideUNIX | IBM WebSphere

    IBM Maximo

  • First Edition (January 2007)This edition applies to version 6, release 2, modification 1 of IBM Maximo and 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-1Understanding the Maximo Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

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

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

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

    Installation Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

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

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

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

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

    IBM WebSphere Refresh Pack Installation RoadMap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Task 1: Install the Core IBM WebSphere Application Server Patch . . . . . . . . . . . . . . . . . . . . . 2-28Task 2: Install the IBM WebSphere Application HTTP Server Patch . . . . . . . . . . . . . . . . . . . . 2-30Task 3: Install the IBM WebSphere Application HTTP Server Plugin Patch . . . . . . . . . . . . . . 2-32

    Installing the IBM WebSphere Fix Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34IBM WebSphere Fix Pack Installation RoadMap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

    Task 1: Install the Core IBM WebSphere Application Server Patch . . . . . . . . . . . . . . . . . . . . . 2-35Task 2: Install the IBM WebSphere HTTP Server Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Task 3: Install the IBM WebSphere Application HTTP Server Plugin Patch . . . . . . . . . . . . . . 2-38Task 4: Install the IBM WebSphere JavaSDK Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

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

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

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

    Copyright IBM Corp. 2007 iii

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

    Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Installing the Language Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Installing Product Enablers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

    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

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

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

    Identify the HTTP Transfer Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Creating Virtual Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

    Deploying the EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

    Chapter 7: Installing The Actuate Encyclopedia for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Installing the Actuate Encyclopedia for Maximo on a Microsoft Windows Platform. . . . . . . . . . . . . . . . 7-1

    Starting the Actuate iServer for Maximo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Installing the Actuate Integration for Maximo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Remove Corrupt Characters from the acserverconfig.xml File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Importing the Encyclopedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

    Installing the Actuate Encyclopedia for Maximo on a UNIX Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Task 1: Complete the Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

    Apply the Required Oracle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Enable Open Security as Web Services, Remove encyc Folder, Restart Deamon . . . . . . . . . . . . 7-5

    Task 2: Install the Actuate Encyclopedia for Maximo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Remove Corrupt Characters from the acserverconfig.xml File . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Importing the Encyclopedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

    Task 3: Complete the Post Installation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

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

    Appendix A: System Server Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Starting the Maximo Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Starting the Actuate iServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Stopping the Actuate iServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Setting Up X-Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Mounting and Unmounting a CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

    iv IBM Maximo: Installation Guide

  • Appendix B: Configuring JMS Options for MEA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Adding Servers to the JMS Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Creating the JMS Bus Destination for the Continuous Inbound (cqinbd) Queue . . . . . . . . . . . . . . . . . B-5Creating the JMS Bus Destination for the Sequential Inbound (sqinbd) Queue . . . . . . . . . . . . . . . . . . B-8Creating the JMS Bus Destination for the Sequential Outbound (sqoutbd) Queue . . . . . . . . . . . . . . . B-9Creating the MEA Connection Factory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10Creating the Continuous Inbound (cqin) JMS Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12Creating the Sequential Inbound (sqin) JMS Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13Creating the Sequential Outbound (sqout) JMS Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14Creating JMS Activation for the Continuous Inbound Queue (cqin) . . . . . . . . . . . . . . . . . . . . . . . . . . B-14

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

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

    Appendix E: Installing Actuate iServer on a Microsoft Windows Platform . . . . . . . . . . . . . . . . . . E-1Pre-Installation Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

    DB2 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1Oracle Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

    Installing Actuate 8 iServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

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

    Contents v

  • vi 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 Managers Guide

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

    IBM Maximo Multisite Administrators 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 Administrators Guide

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

    Copyright IBM Corp. 2007 vii

  • Support

    Support

    IBM Corporation 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 Users 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 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.

    Typical Maximo Configuration

    Maximo requires multiple software servers that you can install on separate, dedicated server machines or the same physical server. For best performance, IBM Corporation recommends using three separate servers. The following diagram depicts a typical Maximo configuration.

    Introduction 1

    Copyright IBM Corp. 2007 1-1

  • Understanding the Maximo Components

    Understanding the Maximo Components

    This section defines the three main components of a typical Maximo environment:

    ! Application Server! Actuate Report Server! Database Server

    Installing Maximo and its components requires a valid and active connection to the Internet. For detailed Maximo system requirements, see Hardware and Software Considerations on page 6.

    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 (with 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 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 pages

    ! Java Enterprise Application (JAR) files that contain class files and other programming code modules

    ! Enterprise Java Bean (EJB) files that contain class files

    1-2 IBM Maximo: Installation Guide

  • Understanding the Maximo Components

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

    Introduction 1-3

  • Understanding the Maximo Components

    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 sites 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

    1-4 IBM Maximo: Installation Guide

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

  • Understanding the Maximo Components

    ! Information in multiple formats including DHTML, PDF, XLS! Open 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.

    Note: If you implement the Actuate Reporting tool with a Maximo instance running on Linux, install Actuate and the Actuate Encyclopedia on a Microsoft Windows platform. See Installing the Actuate Encyclopedia for Maximo on a Microsoft Windows Platform on page 7-1.

    Database Server

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

    Introduction 1-5

  • Hardware and Software Considerations

    Hardware and Software Considerations

    For best performance, adhere to the following configuration:

    ! Dedicated Application Server! Dedicated Actuate Server! Dedicated Database Server

    Factors affecting server configuration requirements are:

    ! Maximo applications deployed! Number of connecting client workstations! Desired performance level

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

    Dedicated Servers Hardware Software

    Application Server: where you install IBM WebSphere and typically, where you deploy Maximo EAR files.

    ! 24 dedicated, 800 MHz processors

    ! 2 GB RAM per processor! 1.5 GB of disk space for

    Maximo and the Java/Web Server components

    Web Application Server Software

    ! IBM WebSphere 6 (provided by IBM Corporation)

    Note: Use the IBM WebSphere Fix Packs and Refresh Packs (supplied by IBM Corporation) to upgrade WebSphere 6.0.x.to version 6.0.2.17, as described in Chapter 2.

    Operating System

    ! IBM AIX 5.2 or 5.3! Red Hat Enterprise Linux 3 (x86

    processor-based systems)

    Note: Although Maximo supports the following operating systems, if you are using an IBM DB2 Universal Database with Maximo release 6.2.1, you cannot use either of the following operating systems on your Application Server:

    ! HP-UX 11i or HP-UX 11i v2 (PA-RISC processor-based systems)

    ! Sun Solaris 9 or Sun Solaris 10 (SPARC-processor based systems)

    1-6 IBM Maximo: Installation Guide

  • Hardware and Software Considerations

    Database Server: where you install database software to create your Maximo database

    ! Refer to vendor specifications

    Database Software

    ! IBM DB2 Universal DataBase 8.2 (Workgroup or Enterprise Edition), configured for TCP/IP support

    ! Oracle 9.2.0.6, or 10.2.0.2 (Standard or Enterprise Edition)

    Note: If using Oracle 10, install the Oracle 9 client on the Actuate server (not the Oracle 10 client).

    Actuate Report Server: where you install Actuate reporting software; used to create and manage your Maximo reports

    ! 12 dedicated 800 MHz processors

    ! 1GB RAM per processor! 610MB of disk space

    Reporting Software

    ! Actuate iServer Release 81 (provided by IBM Corporation)

    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.

    Operating System

    ! Microsoft Windows 20001

    ! Microsoft Windows 20031

    ! HP-UX 11i (PA-RISC)2

    ! Sun Solaris SPARC version 93

    ! IBM AIX 5.2 or 5.3! Database client software: (IBM DB2

    UDB Administrative Client 8.2.7, Oracle Client Software (Oracle JDBC drivers, SQL*Plus, Oracle Networking)

    Dedicated Servers Hardware Software

    Introduction 1-7

  • Hardware and Software Considerations

    NOTE1 If implementing the Actuate iServer Release 8 Reporting tool with a Maximo instance running on Linux, you must install Actuate and the Actuate Encyclopedia on a server running the Microsoft Windows operating system.

    NOTE2 HP-UX 11v2 is not supported for the Actuate iServer reports server with Maximo release 6.2.1.

    NOTE3 Sun Solaris 10 is not supported for the Actuate iServer reports server with Maximo release 6.2.1.

    For additional tuning and configuration information, refer to the IBM Maximo System Administrators Guide.

    System Administrator Workstation:where you install the Maximo application and build the EAR files before deploying them. The Workstation is also used for designing custom Maximo applications, Maximo Workflows, and other high-level functions

    ! Intel-based Pentium processor

    ! I GB RAM ! SVGA 1024 x 768

    resolution; if used for Application Designer 1280 x 1024 resolution

    Operating System

    ! Microsoft Windows 2000! Microsoft Windows XP

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

    Browser

    ! Microsoft Windows Internet Explorer6.0

    ! Microsoft Windows Internet Explorer 7

    Documentation Support

    ! Adobe Reader 6.0

    Client Workstation: where end users work and remotely access and use Maximo.

    ! Intel-based Pentium processor

    ! 512 MB RAM memory or greater

    ! SVGA 1024 x 768 resolution

    Operating System

    ! Microsoft Windows 2000! Microsoft Windows XP

    Browser

    ! Microsoft Windows Internet Explorer 6.0

    ! Microsoft Windows Internet Explorer 7

    Documentation Support

    ! Adobe Reader 6.0

    Dedicated Servers Hardware Software

    1-8 IBM Maximo: Installation Guide

  • Hardware and Software Considerations

    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

    ! IBM AIX 5.2 and 5.3

    For AIX 5.2, set the kernel parameter tcp_nodelayack to 1 by using the following command:

    "no -o tcp nodelayack=1"

    Also for 5.2, ensure that Fix IY53254 is applied.More details are offered at:http://www-1.ibm.com/support/docview.wss?uid=isg1IY53254

    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.

    Note: IBM Corporation does not support the HP-UX or Sun Solaris operating systems on the application server for Maximo Release 6.2.1 with a DB2 database.

    IBM Corporation has certified the following third-party product updates:

    ! Microsoft Windows 2003/Advanced Server Service Pack 1

    ! Microsoft Windows XP Service Pack 2

    ! Microsoft Windows 2000 Service Pack 4

    ! Microsoft Internet Explorer 6.0 Service Pack 2

    ! Microsoft Internet Explorer 7

    ! Oracle 10.2.0.2 (Standard or Enterprise Edition) Service Pack 2

    ! Oracle 9.2.0.6 (Standard or Enterprise Edition) Service Pack 6

    ! HP-UX

    For HP-UX 11.11, Id(1) and linker tools cumulative patch PHSS_30049 (or higher) is required.

    For HP-UX 11.0, ANSI C++ runtime library component patches PHCP_20765, PHCO_19666, PHSS_16587, and PHSS_26559 (or higher) are required. General Release XSWGR1100 (i.e. B.11.00.47.05) or higher is required. File system library patches PHCO_22453, PHKL_22432, PHKL_20335, and PHKL_22440 or later are required. Actuate uses HP-UX 11.0 HP kernel threads and thus DCE Threads are not required.

    Introduction 1-9

  • Installation Roadmap

    For iServer on HP-UX, X Windows run-time library (X11.base.lib) is required in conjunction with running X Server.

    ! Sun Solaris

    On Solaris 8, Actuate iServer requires Sun patch #108434-01.

    For iServer on Solaris, X Windows run-time library (X11.base.lib) is required in conjunction with running X Server.

    Java Virtual Machine (JVM)

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

    Installation Roadmap

    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.

    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

    1-10 IBM Maximo: Installation Guide

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

  • Installation Roadmap

    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

    Introduction 1-11

  • Installation Roadmap

    1-12 IBM Maximo: Installation Guide

  • To install IBM WebSphere 6.0.2.17, complete the following tasks in the order listed:

    1 Install the IBM WebSphere Application Server Network Deployment product

    2 Create a Deployment Manager, and Custom Profile

    3 Install the IBM HTTP Server

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

    5 Install the IBM WebSphere Refresh Pack

    6 Install the IBM WebSphere Fix Pack

    Installing the IBM WebSphere Application Server Network Deployment Product

    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.

    The IBM WebSphere Application Server Network Deployment (ND) product creates 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, see the IBM Maximo System Administrators Guide included on your documentation CD-ROM. For best performance, install the IBM WebSphere Application Server on a dedicated application server.

    To install the IBM WebSphere Application Server Network Deployment Product, complete the following steps:

    1 IBM WebSphere requires that you perform this installation as root.

    2 Mount the WebSphere Application Server Network Deployment into the CD-ROM drive. See Appendix A for more details.

    Installing IBM WebSphere 2

    Copyright IBM Corp. 2007 2-1

  • Installing the IBM WebSphere Application Server Network Deployment Product

    3 Change to the appropriate directory and run the command to install the program (where cdrom represents your actual mount point):

    4 Click Next in the Welcome dialog box.

    5 Select I accept the terms in the license agreement and click Next.

    Platform Directory Command

    Sun Solaris /cdrom/WAS ./install

    IBM AIX /cdrom/WAS ./install

    HP-UX /cdrom ./server814_hpux.bin

    Red Hat Linux /cdrom ./install.sh

    2-2 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    6 Click Next once the system check is completed successfully.

    7 Accept default installation location and click Next.

    remove /Program Files

    Installing IBM WebSphere 2-3

  • Installing the IBM WebSphere Application Server Network Deployment Product

    8 Clear Application Server Samples and Javadocs. Click Next.

    For better performance in either a development or production environment, 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.

    9 Click Next in the installation summary dialog box.

    10 Once all components are installed, click Next.

    c:\WebSphere\Appserver

    c:\IBMHttpServer

    c:\WebSphere\Appserver

    c:\IBMHttpServer

    2-4 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    11 Check the Launch the Profile creation wizard option, and click Next.

    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.

    1 Click Profile creation wizard.

    NOTE If the First steps window does not open automatically, you can launch it with the ./launchpad.sh command.

    Installing IBM WebSphere 2-5

  • Installing the IBM WebSphere Application Server Network Deployment Product

    2 Click Next in the Welcome dialog box.

    3 Select Create a deployment manager option and click Next.

    4 Accept the default value or specify a Profile name.

    2-6 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    5 Accept the default installation location and click Next.

    6 Accept the default values or specify the Node name, Host name, and Cell name and click Next.

    Installing IBM WebSphere 2-7

  • Installing the IBM WebSphere Application Server Network Deployment Product

    7 Review the assigned port numbers and click Next.

    8 Click Next in the Profile summary dialog box.

    2-8 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    9 Ensure that the Launch the first steps console is checked and click Finish.

    10 Once the First Steps window opens, click Installation verification.

    Installing IBM WebSphere 2-9

  • Installing the IBM WebSphere Application Server Network Deployment Product

    11 Once Installation Verification is completed successfully, close the output window.

    12 Open the First Steps window (if not open already) using the ./launchpad.sh command and click the Profile creation wizard.

    You are now ready to create a custom profile.

    2-10 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    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.

    1 Click the Profile creation wizard link.

    2 Click Next in the Welcome dialog box.

    Installing IBM WebSphere 2-11

  • Installing the IBM WebSphere Application Server Network Deployment Product

    3 Scroll down and select Create a custom profile. Click Next.

    4 Accept the default values or specify the appropriate information and click Next.

    2-12 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    5 Specify a unique Profile name or accept the default value and check Make this profile the default. Click Next.

    6 Accept the default Profile directory path and click Next.

    Installing IBM WebSphere 2-13

  • Installing the IBM WebSphere Application Server Network Deployment Product

    7 Specify a unique node name or accept the default value and enter the computer name (or IP address) of the machine where you are performing this installation. Click Next.

    8 Review the port number listings and click Next.

    2-14 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Application Server Network Deployment Product

    9 Click Next in the Profile summary dialog box.

    10 Check the Launch the First steps console option and click Finish.

    11 Close all open dialog boxes and windows.

    Installing IBM WebSphere 2-15

  • Installing the IBM HTTP Server

    Installing the IBM HTTP Server

    After installing the IBM WebSphere ND Application Server product, you must install the IBM HTTP Server.

    Installing a Web server, such as IBM HTTP Server, on the same machine as the application server provides a more robust Web server environment. This type of installation supports rigorous testing environment or production environments that do not require a firewall.

    Complete the following steps to install the IBM HTTP Server on the same machine where you have installed the Network Deployment product.

    1 Invoke the Launchpad. (On the root on the CD, use the file launchpad.sh; Enter: ./launchpad.sh)

    2 Click IBM HTTPServer Installation.

    3 Click Launch the installation wizard for IBM HTTP Server. Alternatively, you can run the ./install.sh command from the /IHS directory.

    4 Click Next in the Welcome dialog box.

    2-16 IBM Maximo: Installation Guide

  • Installing the IBM HTTP Server

    5 Accept the license terms and click Next.

    6 Accept the default installation location and click Next.

    7 Select Typical and click Next.

    remove /Program Files

    Installing IBM WebSphere 2-17

  • Installing the IBM HTTP Server

    8 Click Next in the summary dialog box.

    9 Click Next.

    2-18 IBM Maximo: Installation Guide

  • Installing the IBM HTTP Server

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

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

    Installing IBM WebSphere 2-19

  • Install the IBM HTTP Server Plug-in

    Install the IBM HTTP Server Plug-in

    After installing 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.

    Complete the following steps to install the Plug-in.

    1 Stop the Node Agent and the Network Deployment processes:

    2 Clear both check boxes in the Welcome dialog box and click Next.

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

    Node Agent /../IBM/WebSphere/AppServer/profiles/Custom01/bin

    stopNode.sh

    IBM Network Deployment /../IBM/WebSphere/AppServer/profiles/Dmgr01/bin

    stopManager.sh

    2-20 IBM Maximo: Installation Guide

  • Install the IBM HTTP Server Plug-in

    3 Accept the License terms and click Next.

    4 Click Next in the System prerequisites check dialog box.

    5 Select the IBM HTTP Server V6 option and click Next.

    Installing IBM WebSphere 2-21

  • Install the IBM HTTP Server Plug-in

    6 Select the WebSphere Application Server machine (local) option and click Next.

    7 Accept the default installation location and click Next.

    8 Accept the default installation location and click Next.

    2-22 IBM Maximo: Installation Guide

  • Install the IBM HTTP Server Plug-in

    9 Complete the following sub-steps:

    a The Wizard does not default to the location of the httpd.conf file. You must use the browse button to navigate to the following location: /../IBMIHS/conf/httpd.conf.

    b Accept the default Web server port number: 80

    c Click Next.

    Installing IBM WebSphere 2-23

  • Install the IBM HTTP Server Plug-in

    10 Accept the default name or specify a unique sever definition name.

    11 Accept the default location of the plugin-cfg.xml file as it appears and click Next.

    12 Click Next.

    2-24 IBM Maximo: Installation Guide

  • Install the IBM HTTP Server Plug-in

    13 Click Next.

    14 Click Next.

    15 Click Finish.

    Installing IBM WebSphere 2-25

  • Install the IBM HTTP Server Plug-in

    16 Start the NodeAgent and the Deployment processes.

    Creating a Web Server Definition

    To complete the plug-in installation, create a Web server definition as follows:

    1 Open a new shell window.

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

    3 At the prompt, type configurewebserver1.sh.

    4 Allow for the process to complete: "Configuration save is complete." Close the shell window.

    5 Close all other screens and windows.

    6 Ensure to stop the NodeAgent and the Network Deployment processes at this time. Refer to Appendix A for more details.

    7 Unmount the CD-ROM.

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

    Node Agent /../IBM/WebSphere/AppServer/profiles/Custom01/bin

    startNode.sh

    IBM Network Deployment /../IBM/WebSphere/AppServer/profiles/Dmgr01/bin

    startManager.sh

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

    Node Agent /../IBM/WebSphere/AppServer/profiles/Custom01/bin

    startNode.sh stopNode.sh

    IBM Network Deployment /../IBM/WebSphere/AppServer/profiles/Dmgr01/bin

    startManager.sh stopManager.sh

    2-26 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Refresh Pack

    Installing the IBM WebSphere Refresh Pack

    You use the IBM Refresh Pack CD to update IBM WebSphere 6.0.0.x software to release 6.0.2, which is an interim step to updating to release 6.0.2.17, as required with Maximo 6.2.1 software. This section explains how to update IBM WebSphere to release 6.0.2.

    Note: Complete the 6.0.2 update before you use the Fix Pack (explained in the next section) to complete the update to 6.0.2.17.

    To update to IBM WebSphere 6.0.2, you perform preparation steps, copy and extract a platform-specific file from the IBM Refresh 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 three Refresh Pack files (listed below) for your platform. After completion, this process updates the core WebSphere Application Server, the HTTP Server, and the HTTP Server Plugins to release 6.0.2.

    Platform-Specific Files on the IBM WebSphere Refresh Pack CD

    B

    Unix Platform Files to Extract from the IBM WebSphere Refresh Pack CD

    Sun Solaris ! 6.0-WS-WAS-SolarisSparc-RP0000002.tar! 6.0-WS-WASIHS-SolarisSparc-RP0000002.tar! 6.0-WS-WASPlugIn-SolarisSparc-RP0000002.tar

    IBM AIX ! 6.0-WS-WAS-AixPPC32-RP0000002.tar! 6.0-WS-WASIHS-AixPPC32-RP0000002.tar! 6.0-WS-WASPlugIn-AixPPC32-RP0000002.tar

    HP-UX ! 6.0-WS-WAS-HpuxPaRISC-RP0000002.tar! 6.0-WS-WASIHS-HpuxPaRISC-RP0000002.tar! 6.0-WS-WASPlugIn-HpuxPaRISC-RP0000002.tar

    Red Hat Linux

    ! 6.0-WS-WAS-LinuxX32-RP0000002.tar! 6.0-WS-WASIHS-LinuxX32-RP0000002.tar! 6.0-WS-WASPlugIn-LinuxX32-RP0000002.tar

    Installing IBM WebSphere 2-27

  • Installing the IBM WebSphere Refresh Pack

    IBM WebSphere Refresh Pack Installation RoadMap

    Perform the three Refresh Pack installation tasks in the order that they appear in the roadmap below. Do not start any IBM processes until you have completed all three installation tasks.

    Task 1: Install the Core IBM WebSphere Application Server Patch

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

    1 Stop all IBM WebSphere Application Servers and HTTP Servers, if running, see Appendix A, "System Server Administration," on page A-1.

    2 If required by your platform, mount the CD-ROM, see Appendix A, "System Server Administration," on page A-4.

    3 From a shell prompt, change directory to the location where you installed the IBM WebSphere Application Server, and then navigate to AppServer/profiles/Dmgr01/bin directory, as shown in the following example:

    /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin

    4 Enter the following command to back up the configuration files in the current directory:

    ./backupConfig.sh

    5 From a shell prompt, change directory to the location where you installed the IBM WebSphere Application Server, and then navigate to /AppServer/profiles/Custom01/bin directory, as shown in the following below.

    /opt/IBM/WebSphere/AppServer/profiles/Custom01/bin

    6 Enter the following command to back up the configuration files in the current directory:

    ./backupConfig.sh

    7 Delete the updateinstaller directory, if present, from the/IBM/WebSphere/AppServer directory.

    /opt/IBM/WebSphere/AppServer

    Task Task description and location

    1. Task 1: Install the Core IBM WebSphere Application Server Patch on page 2-28

    2. Task 2: Install the IBM WebSphere Application HTTP Server Patch on page 2-30

    3. Task 3: Install the IBM WebSphere Application HTTP Server Plugin Patch on page 2-32

    2-28 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Refresh Pack

    8 Perform these three sub-steps to copy and extract the Refresh Pack (6.0.2) core Application Server Patch:

    a Change directory back to the CD-ROM .

    b Copy the platform-specific core Application Server Patch into the /IBM/WebSphere/AppServer directory.

    c Change directory to /IBM/WebSphere/AppServer and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE APPSERVER DIRECTORY DURING THE EXTRACTION PROCESS.

    9 From a shell prompt, change directory to the/updateinstaller directory, as shown in the following example.

    cd /opt/IBM/WebSphere/AppServer/updateinstaller

    10 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    11 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    12 Accept the default installation location and then click Next.

    13 Select Install maintenance package and then click Next.

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

    15 Click Next to begin copying the JDK.

    16 Allow for the JDK-copying process to complete.

    17 Click Relaunch after the JDK loads to relaunch the Wizard.

    18 Select Install maintenance package and then click Next.

    19 Accept the default path of the maintenance package and then click Next.

    20 Read the Wizard panel text to verify that Refresh Pack (6.0.2) for the core Application Server will be installed and then click Next to begin the installation.

    For this platform Copy this core Application Server Patch for 6.0.2

    Sun Solaris 6.0-WS-WAS-SolarisSparc-RP0000002.tar

    IBM AIX 6.0-WS-WAS-AixPPC32-RP0000002.tar

    HP-UX 6.0-WS-WAS-HpuxPaRISC-RP0000002.tar

    Red hat Linux 6.0-WS-WAS-LinuxX32-RP0000002.tar

    Installing IBM WebSphere 2-29

  • Installing the IBM WebSphere Refresh Pack

    21 Allow the prereq.jdk-component-copying process to complete.

    22 Read the Wizard panel text to verify successful installation of 6.0.2.0 and then click Finish.

    You have installed the Refresh Pack (6.0.2) core Application Server Patch. Next, proceed to Task 2 to install the Refresh Pack (6.0.2) HTTP Server Patch.

    Task 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 the/IBM/HTTPServer directory as shown in the following example:

    /opt/IBMHTTPServer

    2 Perform these three sub-steps to copy and extract the Refresh Pack (6.0.2) HTTP Server Patch:

    a Change directory back to the CD-ROM .

    b Copy the platform-specific HTTP Server Patch into the /IBMHTTPServer directory.

    c Change directory to /IBMHTTPServer and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE IBMHTTPSERVER DIRECTORY DURING THE EXTRACTION PROCESS.

    3 From a shell prompt, change directory to the/updateinstaller directory, as shown in the following example.

    cd /opt/IBMHTTPServer/updateinstaller

    4 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    5 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    6 Accept the default installation location and then click Next.

    7 Select Install maintenance package and then click Next.

    For this platform Copy this HTTP Server Patch for 6.0.2

    Sun Solaris 6.0-WS-WASIHS-SolarisSparc-RP0000002.tar

    IBM AIX 6.0-WS-WASIHS-AixPPC32-RP0000002.tar

    HP-UX 6.0-WS-WASIHS-HpuxPaRISC-RP0000002.tar

    Red hat Linux 6.0-WS-WASIHS-LinuxX32-RP0000002.tar

    2-30 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Refresh Pack

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

    9 Read the Wizard panel text to verify that Refresh Pack (6.0.2) for the IBM HTTP Server will be installed and then click Next to begin the installation.

    10 Allow for the JDK-copying process to complete. (The Wizard panel reads: Backing up component prereq.ihs.)

    11 Read the Wizard panel text to verify successful installation of 6.0.2.0 and then click Finish.

    You have installed the Refresh Pack (6.0.2) HTTP Server Patch. Next, proceed to Task 3 to install the Refresh Pack (6.0.2) HTTP Server PLUGIN Patch.

    Installing IBM WebSphere 2-31

  • Installing the IBM WebSphere Refresh Pack

    Task 3: 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 directory, if present, from the/IBM/WebSphere/Plugins directory as shown in the following example:

    /opt/IBM/WebSphere/AppServer/Plugins

    2 Perform these three sub-steps to copy and extract the Refresh Pack (6.0.2) Plugin Patch:

    a Change directory back to the CD-ROM .

    b Copy the platform-specific HTTP Server Plugin Patch into the/IBM/WebSphere/Plugins directory..

    c Change directory to /IBM/WebSphere/Plugins and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE PLUGINS DIRECTORY DURING THE EXTRACTION PROCESS.

    3 From a shell prompt, change directory to the/updateinstaller directory, as shown in the following example.

    cd /opt/IBM/WebSphere/Plugins/updateinstaller

    4 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    5 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    6 Accept the default installation location and then click Next.

    7 Select Install maintenance package and then click Next.

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

    9 Click Next to begin the installation and copying the JDK.

    10 Allow for the JDK-copying process to complete.

    For this platform Copy this HTTP Server Plugin Patch for 6.0.2

    Sun Solaris 6.0-WS-WASPlugIn-SolarisSparc-RP0000002.tar

    IBM AIX 6.0-WS-WASPlugIn-AixPPC32-RP0000002.tar

    HP-UX 6.0-WS-WASPlugIn-HpuxPaRISC-RP0000002.tar

    Red hat Linux 6.0-WS-WASPlugIn-LinuxX32-RP0000002.tar

    2-32 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Refresh Pack

    11 Click Relaunch once the JDK is completely loaded.

    12 Select Install maintenance package and then click Next.

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

    14 Read the Wizard panel text to verify that Refresh Pack (6.0.2.0) for the IBM HTTP Server Plugins will be installed and then click Next to begin the installation.

    15 Allow for the JDK-copying process to complete. 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. Before you proceed to the Fix Pack installation procedure in the next section, delete all the updateinstaller directories created in this process.

    Installing IBM WebSphere 2-33

  • Installing the IBM WebSphere Fix Pack

    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, as explained in this section.

    NOTE 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. After completion, this process updates the core WebSphere Application Server, the HTTP Server, the HTTP Server Plugins, and the JavaSDK to release 6.0.2.17.

    Platform-Specific Files on the IBM WebSphere Fix Pack CD

    Unix Platform Files to Extract from the IBM WebSphere Refresh Pack CD

    Sun Solaris ! 6.0.2-WS-WAS-SolarisSparc-FP00000017.tar! 6.0.2-WS-WASIHS-SolarisSparc-FP00000015.tar! 6.0.2-WS-WASPlugIn-SolarisSparc-FP00000017.tar! 6.0.2-WS-WASJavaSDK-SolarisSparc-FP00000017.tar

    IBM AIX ! 6.0.2-WS-WAS-AixPPC64-FP00000017.tar! 6.0.2-WS-WASIHS-AixPPC32-FP00000015.tar! 6.0.2-WS-WASPlugIn-AixPPC64-FP00000017.tar! 6.0.2-WS-WASJavaSDK-AixPPC64-FP00000017.tar

    HP-UX ! 6.0.2-WS-WAS-HpuxPaRISC-FP00000017.tar! 6.0.2-WS-WASIHS-HpuxPaRISC-FP00000015.tar! 6.0.2-WS-WASPlugIn-HpuxPaRISC-FP00000017.tar! 6.0.2-WS-WASJavaSDK-Hpux-FP00000017.tar

    Red Hat Linux

    ! 6.0.2-WS-WAS-LinuxX32-FP00000017.tar! 6.0.2-WS-WASIHS-LinuxX32-FP00000015.tar! 6.0.2-WS-WASPlugIn-LinuxX32-FP00000017.tar! 6.0.2-WS-WASJavaSDK-LinuxX32-FP00000017.tar

    2-34 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Fix Pack

    IBM WebSphere Fix Pack Installation RoadMap

    Perform the four Fix Pack installation tasks in the order that they appear in the roadmap below. Do not start any IBM processes until you have completed all four installation tasks.

    Task 1: 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, as described in Appendix A.

    2 If required by your platform, mount the CD-ROM, as described in Appendix F.

    3 From a shell prompt, change directory to the location where you installed the WebSphere Application Server, and then navigate to the/AppServer/profiles/Dmgr01/bin directory, as shown in the following example.

    /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin

    4 Enter the following command to back up the configuration files in the current directory:

    backupConfig.sh

    5 From a shell prompt, change directory to the location where you installed the WebSphere Application Server, and then navigate to the/AppServer/profiles/Custom01/bin directory, as shown in the following example.

    /opt/IBM/WebSphere/AppServer/profiles/Custom01/bin

    6 Back up the configuration files in the current directory. Enter:

    backupConfig.sh

    7 Delete the updateinstaller directory, if present, from the/IBM/WebSphere/AppServer directory as shown in the following example:

    /opt/IBM/WebSphere/AppServer

    Task Task description and location

    1. Task 1: Install the Core IBM WebSphere Application Server Patch on page 2-35

    2. Task 2: Install the IBM WebSphere HTTP Server Patch on page 2-36

    3. Task 3: Install the IBM WebSphere Application HTTP Server Plugin Patch on page 2-38

    4. Task 4: Install the IBM WebSphere JavaSDK Patch on page 2-39

    Installing IBM WebSphere 2-35

  • Installing the IBM WebSphere Fix Pack

    8 Perform these three sub-steps to copy and extract the Fix Pack (6.0.2.17) core Application Server Patch:

    a Change directory back to the CD-ROM .

    b Copy the platform-specific core Application Server Patch into the /IBM/WebSphere/AppServer directory.

    c Change directory to /IBM/WebSphere/AppServer and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE APPSERVER DIRECTORY DURING THE EXTRACTION PROCESS.

    9 From a shell prompt, change directory to the/updateinstaller directory, as shown in the following example.

    cd /opt/IBM/WebSphere/AppServer/updateinstaller

    10 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    11 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    12 Accept the default installation location and then click Next.

    13 Select Install maintenance package and then click Next.

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

    15 Read the Wizard panel text to verify Fix Pack 6.0.2.17 (FP60217) for the core Application Server will be installed. Ensure that you have backed up the curent configuration, and then click Next to begin the installation.

    16 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.

    You have installed the Fix Pack (6.0.2.17) core Application Server Patch. Next, proceed to Task 2 to install the Fix Pack (6.0.2.17) HTTP Server Patch.

    Task 2: Install the IBM WebSphere HTTP Server Patch

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

    For this platform Copy this core Application Server Patch for 6.0.2.17

    Sun Solaris 6.0.2-WS-WAS-SolarisSparc-FP00000017.tar

    IBM AIX 6.0.2-WS-WAS-AixPPC64-FP00000017.tar

    HP-UX 6.0.2-WS-WAS-HpuxPaRISC-FP00000017.tar

    Red hat Linux 6.0.2-WS-WAS-LinuxX32-FP00000017.tar

    2-36 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Fix Pack

    1 Delete the updateinstaller directory, if present, from the /IBMHTTPServer directory as shown in the following example:

    /opt/IBMHTTPServer

    2 Perform these three sub-steps to copy and extract the Fix Pack (6.0.2.17) HTTP Server Patch:

    a Change directory back to the CD-ROM .

    b Copy the platform-specific HTTP Server Patch into the directory/IBMHTTPServer.

    c Change directory to /IBM/IBMHTTPServer and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE IBMHTTPSERVER DIRECTORY DURING THE EXTRACTION PROCESS.

    3 From a shell prompt, change directory to the updateinstaller directory, as shown in the following example.

    cd /IBMHTTPServer/updateinstaller

    4 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    5 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    6 Accept the default installation location and then click Next.

    7 Select Install maintenance package and then click Next.

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

    9 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) for the HTTP Server will be 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.17 and then click Finish.

    You have installed the Fix Pack (6.0.2.17) HTTP Server Patch. Next, proceed to Task 3 to install the Fix Pack (6.0.2.17) HTTP Server PLUGIN Patch.

    For this platform Copy this HTTP Server Patch for 6.0.2.17

    Sun Solaris 6.0.2-WS-WASIHS-SolarisSparc-FP00000015.tar

    IBM AIX 6.0.2-WS-WASIHS-AixPPC32-FP00000015.tar

    HP-UX 6.0.2-WS-WASIHS-HpuxPaRISC-FP00000015.tar

    Red hat Linux 6.0.2-WS-WASIHS-LinuxX32-FP00000015.tar

    Installing IBM WebSphere 2-37

  • Installing the IBM WebSphere Fix Pack

    Task 3: 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 directory, if present, from the /IBM/WebSphere/Plugins directory as shown in the following example:

    /opt/IBM/WebSphere/Plugins

    2 Perform these three sub-steps to copy and extract the Fix Pack (6.0.2.17) Application Server Plugin patch.

    a Change directory back to the CD-ROM .

    b Copy the platform-specific HTTP Server Plugin Patch into the/IBM/WebSphere/Plugins directory.

    c Change directory to /IBM/WebSphere/Plugins and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE PLUGINS DIRECTORY DURING THE EXTRACTION PROCESS.

    3 From a shell prompt, change directory to the /updateinstaller directory, as shown in the following example:

    cd /opt/IBMWebSphere/Plugins/updateinstaller

    4 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    5 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    6 Accept the default installation location and then click Next.

    7 Select Install maintenance package and then click Next.

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

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

    For this platform Copy this HTTP Server Plugin Patch for 6.0.2.17

    Sun Solaris 6.0.2-WS-WASPlugIn-SolarisSparc-FP00000017.tar

    IBM AIX 6.0.2-WS-WASPlugIn-AixPPC64-FP00000017.tar

    HP-UX 6.0.2-WS-WASPlugIn-HpuxPaRISC-FP00000017.tar

    Red hat Linux 6.0.2-WS-WASPlugIn-LinuxX32-FP00000017.tar

    2-38 IBM Maximo: Installation Guide

  • Installing the IBM WebSphere Fix Pack

    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.

    You have installed the Fix Pack (6.0.2.17) HTTP Server Plugin Patch. Next, proceed to Task 4 to install the Fix Pack (6.0.2.17) JavaSDK Patch.

    Task 4: 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 directory, if present, from the/IBM/WebSphere/AppServer directory as shown in the following example:

    /opt/IBM/WebSphere/AppServer

    2 Perform these three sub-steps to copy and extract the Fix Pack (6.0.2.17) JavaSDK Patch:

    a Change directory back to the CD-ROM .

    b Copy the platform-specific JavaSDK Patch into the directory/IBM/WebSphere/AppServer..

    c Change directory to /IBM/WebSphere/AppServer and extract the files to the same location.

    NOTE: THE FILES UNPACK INTO THE UPDATEINSTALLER DIRECTORY THAT IS AUTOMATICALLY CREATED IN THE APPSERVER DIRECTORY DURING THE EXTRACTION PROCESS.

    3 From a shell prompt, change directory to the/updateinstaller directory, as shown in the following example.

    cd /opt/IBM/WebSphere/AppServer/updateinstaller

    4 Enter the following command to invoke the IBM Update Installer Wizard:

    ./update

    5 Click Next in the IBM Update Installer for WebSphere Software Welcome dialog box.

    6 Accept the default installation location and then click Next.

    7 Select Install maintenance package and then click Next.

    For this platform Copy this JavaSDK Patch for 6.0.2.17

    Sun Solaris 6.0.2-WS-WASJavaSDK-SolarisSparc-FP00000017.tar

    IBM AIX 6.0.2-WS-WASJavaSDK-AixPPC64-00000017.tar

    HP-UX 6.0.2-WS-WASJavaSDK-HpuxPaRISC-FP00000017.tar

    Red hat Linux 6.0.2-WS-WASJavaSDK-LinuxX32-FP00000017.tar

    Installing IBM WebSphere 2-39

  • Installing the IBM WebSphere Fix Pack

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

    9 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) for the JavaSDK will 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 that the JDK successfully copied and then click Relaunch.

    11 Select Install maintenance package and then click Next.

    12 Accept the default filename of the maintenance package and then click Next.

    13 Read the Wizard panel text to verify that maintenance package WASJAVASDKFP60217 will be 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 will be installed and then click Finish.

    You have installed the Fix Pack (6.0.2.17) JavaSDK Patch, which completes the IBM WebSphere 6.0.2.17 installation Process. To verify successful installation (optional), you can startup the IBM WebSphere and HTTP Servers. Next, proceed to the next chapter to install the Actuate Application.

    2-40 IBM Maximo: Installation Guide

  • This chapter explains how to install the Actuate 8 iServer application on a server running the IBM AIX or HP-UX operating system.

    Note: In an environment where your Maximo instance is running on a Linux platform, you must install Actuate and the Actuate Encyclopedia on a Microsoft Windows platform. See Installing Actuate iServer on a Microsoft Windows Platform on page E-1 for the procedure. When you have completed the procedure, proceed to Chapter 4 to continue with the Maximo installation.

    Pre-Installation Procedures

    The following sections describe the pre-installation procedures required to ensure database connectivity.

    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 If you are installing Actuate on a server that is separate from the Oracle server, install the following client software on your Actuate Server before you install Actuate:

    a Oracle JDBC Drivers

    b SQL*Plus

    Installing the Actuate iServer Application 3

    Copyright IBM Corp. 2007 3-1

  • Installing Actuate8 iServer

    c Oracle 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-3.

    Refer to your Oracle installation documentation for more information. Oracle documentation is available online at http://otn.oracle.com/documentation/content.html.

    Installing Actuate8 iServer

    This section describes how to install Actuate 8 iServer. For best performance, install the Actuate iServer on a separate, dedicated server.

    1 Preferably, create a group called mxe and a user login called mxadmin.

    2 Log in as mxadmin to run this installation.

    3 Mount the Actuate iServer into the CD-ROM drive.

    For information on manually mounting CDs (if your system is not running volume management software), see Appendix A, "System Server Administration," on page A-4.

    4 Change to the appropriate directory and run the command to install the program (where cdrom represents your actual mount point):

    5 Press the space bar to page through to the end of the License Agreement text, then press y to accept the license agreement

    6 Press the space bar to page through to the end of the Welcome text and press Enter.

    7 Accept the default directory location (in this example, /export/home/mxadmin) and press Enter.

    8 Type 1 to select Server with Management Console and press Enter.

    9 Type 2 to select Stand-alone Server and press Enter.

    10 Type 1 to choose the English (United States) option and press Enter

    Platform Directory Command

    Sun Solaris /cdrom/iserv8f5sol/iserver ./isinstall.sh

    HP UX /cdrom ./isinstall.sh

    AIX /cdrom/iserver ./isinstall.sh

    Linux Refer to Installing Actuate iServer on a Microsoft Windows Platform on page E-1

    3-2 IBM Maximo: Installation Guide

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

  • Installing Actuate8 iServer

    11 Select the value corresponding to the appropriate time zone where you are and press Enter.

    12 Enter the full path to the license file provided on the CD-ROM. For example: /cdrom/Actuate_key_18802.xml.

    13 Type the host name or the IP address of the machine where you are installing the Process Daemon Management. Typically, this is the same machine where you install the iServer Application.

    The Process Daemon Management configuration installs the Administrative functions of the Actuate iServer application. It does not make a connection to Maximo.

    14 Press Enter to accept the default port number (8100). If you would like to use another port number specify it now.

    15 Type the host name or the IP address of the machine where you are installing the iServer. Typically, this is the same where you the PMD.

    The iServer configuration enables the Actuate iServer application to connect to the Maximo Encyclopedia Volume.

    16 Press Enter to accept the default port number (8000).

    17 Type an Administrator password and press Enter.

    18 Type the same password from the previous step to confirm the Administrator password and press Enter.

    19 Accept the default value of y to use Volume Name for Encyclopedia.

    20 Type the host name or the IP address of the machine where you are installing the Actuate iServer.

    21 At the prompt press enter to select the default (y for yes) to enable the PMD process to automatically start the iServer process.

    22 Accept the default value of n (integrate LDAP with iServer) and press Enter.

    23 At the prompt type y for yes (default is n) for Database Drivers / Clients, and press Enter. The program prompts you whether you want to select Using DB2 Client.

    DB2 Only 24 Enter Y for Yes to install DB2 Client.

    DB2 Only 25 The program prompts you to enter the full path to the DB2 directory.

    DB2 Only 26 Enter the full path. For example: /user/opt/db2_008_01

    DB2 Only 27 The program prompts you to enter the DB2 instance.

    DB2 Only 28 Enter the DB2 instance. For example: db2inst1

    DB2 Only 29 The program prompts you to enter the home directory for the DB2 instance.

    Installing the Actuate iServer Application 3-3

  • Installing Actuate8 iServer

    DB2 Only 30 Enter the full path for the instance = for example /home/db2inst1

    31 Accept the default value of n for no and press Enter. The program prompts you whether you want to select Using INFORMIX Client.

    32 Accept the default value of n for no and press Enter. The program prompts you whether you want to select Using Oracle Client.

    Oracle Only 33 At the prompt type y for yes (default is n) and press Enter. The program prompts you whether you want to select Oracle Client Directory.

    Oracle Only 34 At the prompt type the full path to your Oracle Client directory and press Enter.

    For example: /export/home/oracle/product/9.2.0

    AIX Only 35 Accept the default value of y for JRE 1.2.x and press Enter.

    AIX Only 36 Select n for Sybase Client and Press Enter.

    37 Accept the default value of n for no and press Enter. The program prompts you whether you want to select Using PROGRESS Client.

    38 Accept the default value of n for no (default is n) and press Enter. The program prompts you whether you want to select Using ODBC Driver.

    39 Accept the default value of n for no and press Enter. The program prompts you whether you want to select Using SAP JCO Option.

    40 Accept the default value of n for no and press Enter. The program prompts you whether you want to use X-Frame Buffer for Graphics.

    41 Select option 1 and press Enter.

    42 Accept the default host name or type the IP address of the host machine.

    43 Accept the default port number 8100 and press Enter.

    44 Accept the default host name or type the IP address of the host machine.

    45 Accept the default port number (8000).

    46 Accept the default Encyclopedia volume name and press Enter.

    47 Accept the default context root, acadmin, and press Enter.

    48 Accept the default HTTP Port number, 8900, and press Enter.

    49 Review your settings and press Enter to accept the default value of y for yes. The program prompts you whether you want to select Start the iServer Immediately.

    This step may take a few minutes to complete.

    3-4 IBM Maximo: Installation Guide

  • Installing Actuate8 iServer

    50 Accept the default value of y for yes and press Enter. The program prompts you to enter the command for Starting the Actuate iServer Automatically.

    51 To enable iServer to start automatically, perform the following steps:

    a Log in as root user.

    b Change directory to: /AcServer/bin/

    c Run this platform-independent command: ./update_rclocal.sh

    d Press Enter.

    where the in this example is /export/home/mxadmin

    AIX with DB2 Only 52 To connect AIX to DB2, complete the following steps after the Actuate iServer installation process completes:

    a Shutdown the Actuate iServer.

    b Change directory to: /AcServer/operation

    c Rename the existing factsrvr8 file to factsrvr8.old, as follows:

    mv factsrvr8 factsrvr8.old

    d Copy the factsrvr.db2 file to factsrvr8, as follows:

    cp factsrvr.db2 factsrvr8

    e Restart the Actuate server.

    Installing the Actuate iServer Application 3-5

  • Installing Actuate8 iServer

    3-6 IBM Maximo: Installation Guide

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

    Complete the following worksheet to record the names and values required during installation. The page and step numbers in the right column of the worksheet indicate which point in the installation process you use the information.

    Installing Maximo 4Information Required Record the information here... Information used

    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-3

    Database port number Step 10 on page 4-3

    Database Name Step 10 on page 4-3

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

    Database/Schema password Step 10 on page 4-3

    Actuate-related

    Actuate iServer name Step 16 on page 4-3

    iServer port number Step 16 on page 4-3

    Datasource Name (DB2) or TNS (Oracle) on the Actuate iServer

    Step 16 on page 4-3

    Copyright IBM Corp. 2007 4-1

  • Starting the Maximo Installation Program

    Starting the Maximo Installation Program

    To install the Maximo Application, complete the following steps:

    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.

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

    2 Insert the Maximo software 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

    5 Click Next in the Welcome dialog box.

    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 installs Maximo (the default value is C:\Maximo) and then click Next.

    9 Select the appropriate database and click Next.

    4-2 IBM Maximo: Installation Guide

  • Starting the Maximo Installation Program

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

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

    NOTE The host name is required to run reports. Contact your Network Administrator if you dont 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 server is installed. Click Next.

    TIP 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 Maximo Enterprise Adapter check-box, otherwise accept default (unchecked) and click Next.

    NOTE If you selected the Enable Maximo Enterprise Adapter check-box, ensure to configure your JMS options detailed in Appendix B before deploying the EAR files as detailed in Chapter 8: , see Chapter 6, "Creating the Maximo Application Server and Deploying the EAR Files," on page 6-1.

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

    16 Specify the following information and then click Next:

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

    b iServer Port Number: accept default, 8000.

    DB2 Oracle

    Database server name

    Enter the DB2 server host name

    Enter the Oracle server host name

    Port number 50000 1521 (Default)

    Database name Enter the DB2 database name

    Enter the Oracle system identifier

    Database/Schema owners name

    MAXIMO (default) MAXIMO (default)

    Database/Schema owners password

    MAXIMO MAXIMO

    Installing Maximo 4-3

  • Starting the Maximo Installation Program

    c Depending on the database server you installed, enter one of the following values:

    ! If DB2, enter Datasource name.! If Oracle, enter TNS name.

    d Click Next

    17 Enter the host name of the Actuate iServ