Installation Guide Oracle

Release 4.1.1
Copyright 2001, MRO Software, Inc.

This document and its publication do not constitute or create a contract. MRO Software, Inc. makes no warranties, express or implied, regarding the accuracy or completeness of this document or of the related program material. 2001 MRO Software, Inc. All rights reserved. Contains Trade Secret Information of MRO Software, Inc. Use, transfer, disclosure, or copying without MRO Software, Inc.s express written permission is strictly forbidden. Restricted Rights Legend: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subdivision (b)(3)(ii) of the Rights in Technical Data and Computer Software clause at DFAR 252.227-7013. Trademarks: MAXIMO, INTERMAT, Struxure, MAXIMO Enterprise, MAXIMO Extended Enterprise, MAXIMO for Integrated Supply, MAXIMO Scheduler, MAXIMO Workflow, MAXIMO Analyzer, MAXIMO Buyer, MAXIMO Fleet Manager, MAXIMO Aviation Manager, mroManufacturer, mroDistributor, mroConnect, mroRFQ, mroHosting CenterSM, Illustrated Parts Catalogue, Standard Modifier Dictionary, and Autocon are trademarks of MRO Software, Inc. Other products and brand names are trademarks or registered trademarks of their respective companies; some are noted below. Third Party Technology: Certain MRO Software, Inc. products contain technology provided under license from third parties, as noted below:
MRO Software Products MAXIMO All MAXIMO AutoVue Analyzer MAXIMO 4i Scheduler MAXIMO Workflow Crystal Report Writer MAXIMO Buyer All products MAXIMO mroRFQ mroDistributor & mroManufacturer Third Party Technology Information Portions 2000 Brio Technology Brio.Report Builder provided by Brio Technology, Inc. Portions 1995-2000 BroadVision, Inc. BroadVision Business Commerce, BroadVision Oneto-One Enterprise, BroadVision One-to-One Publishing, BroadVision Tools provided by BroadVision, Inc. Portions 1996 by Centura Software Corporation. Portions 1989-1998 Cimmetry Systems, Inc. AutoVue , AutoVue Professional provided by Cimmetry Systems, Inc. Portions 1999 Cognos Incorporated. Portions 1994-1999 Citrix Systems, Inc. MetaFrame, Citrix WinView and WinFrame provided by Citrix Systems, Inc. Portions 1999 MERANT ODBC DataDirect provided by MERANT Portions 1998, 1999 NETRONIC Software GmbH. Portions 1999 Seagate Software Information Management Group Holdings, Inc. Seagate Crystal Reports provided by Seagate Software. Portions 2000 Verity, Inc. Verity Search provided by Verity, Inc. Portions 2000 webMethods, Inc. webMethods B2B Developer, webMethods B2B Integration Server provided by webMethods, Inc. Portions 1995-2000 Actuate Corporation. Portions 1998-2000 Moai Technologies, Inc. Moai LiveExchange provided by Moai Technologies, Inc. Portions TAXWARE International, Inc. TAXWARE VERAZIP Sales/User, STEP provided by TAXWARE International, Inc.

MAXIMO RELEASE 4.1.1 INSTALLATION WORKSHEET (ORACLE PLATFORM)

If you are not connecting to the mroHosting Center, skip this section and continue directly to Running the MAXIMO Application Installation Program on page ii. Prior to running the MAXIMO Installation for the Oracle platform, please review the following list to be sure that you have gathered all of the information requested.

NOTE: The following two worksheet sections (Connecting to the mroHosting Center and Configuring the mroBuyer package in the webMethods B2B server) can only be completed by calling the MRO Software Communications Department. The telephone number is (519) 642-6055.

Connecting to the mroHosting Center

When installing MAXIMO Self-Service Applications, the following information in bold type must be added in order to use the mroHosting Center. (page 43) 1. Catalog Name The Catalog Name is the user-defined name of the company or catalog that you want to appear in the marketplace catalog selection drop-down list. ______________________________________________________________ 2. Vendor Code The Vendor Code must be entered as part of the Company record in the MAXIMO database through the companies application. If the company record does not exist, create it and then add the Vendor Code that you receive as part of the Company Record. The vendor code will be also be used in creating the marketplace vendor.

The mroHosting Center vendor (in addition to the vendor code) must also contain a company name, mnet company ID, buyer company and mroHosting Center ID. These will be entered in your MAXIMO database through the Companies table and are available by contacting the MRO Software Communications Department. ______________________________________________________________ 3. Customer Company ID (page 43) ___________________________________

Configuring the mroBuyer Package in the webMethods B2B Server

1. The remote B2B Server connection URL. (page 58) __________________ 2. The remote B2B Server's incoming interface name. (page 61) __________ 3. The remote B2B Server's incoming service name. (page 61) ____________ 4. Remote FTP Server for document attachments. (page 61) _____________

Running the MAXIMO Application Installation Program

1. Name of person and company to which the product should be registered. (page 26) _____________________________________________________ 2. Setup Type: Network, Local, or Client (page 26) ______________________ 3. Location of folder for installing MAXIMO applications. The default location is C:\Program Files\MAX411. (page 27) _______________________ 4. Type of installation mode: Full or Custom (page 27) ____________________ 5. Folder for installing and running Brio.Reports The default is C:\SQR6. (page 27) ______________________________________________________ 6. Oracle Configuration:

ii

Database alias for users to enter when connecting to MAXIMO. This is a user-defined name users will enter as the database name when connecting to MAXIMO. (page 27) ___________________________________________ Oracle connect string to establish the connection to the Oracle database. This is the connect string defined through Net8 Easy Config. (page 27) ______________________________________________________________ 7. Database information (for Workflow only) (page 27): Name of database. This information should be the same as the first part of the Oracle Configuration step. ________________________________________ Server name of your server running the Application Server for Business Components.____________________________________________________ 8. For Workflow only: Select a method, either URL or mapped drive, that will allow your clients to connect to your application server. If you select URL, the address would be: http://appsrvr where appsrvr is the name of the server running the Application Server. (page 27) ____________________________

Running the MAXINST Program

1. Database alias name specified during MAXIMO installation. This should agree with your database alias specified during Oracle configuration as defined in Step 6 of the previous section. (page 34) _____________________ 2. User name and password of the schema owner specified in the CREATMAX.SQL file. You must enter the user name created from running this file. The default is MAXIMO. (page 34) __________________________ 3. Oracle SYS password. (page 35) ____________________________________ 4. Tablespace in which to create tables and indexes. (page 35) ______________ 5. Specify whether you want to create a demo database (MAXDEMO) or an empty database (MAXIMO). (page 36) _____________________________

iii

Running MAXIMO Self-Service Applications Installation

1. Location to install MAXIMO Self-Service Applications. The default location is C:\MXSERVER. (page 40)________________________________ 2. Oracle host name. This is the server name of the server running Oracle. (page 41) ______________________________________________________ 3. Oracle listener port. The is the port Oracle is using. The default is 1521. (page 41) ______________________________________________________ 4. Oracle Instance. This is the Oracle System Identifier (SID) of the database. (page 41) ______________________________________________________ 5. Schema owner of the database. Default schema owner is MAXIMO. (page 41) ______________________________________________________________ 6. Username and password of the MAXIMO database owner (schema owner). (page 41) ______________________________________________________ 7. E-mail address of the administrator who should receive error messages. (page 42) ______________________________________________________ 8. If you selected e-Commerce Adapter (page 42): B2B Server Host The name of the server where webMethods B2B server is installed. _______________________________________________________ B2B Server Port Number The default is 5555. ________________________ E-mail address of the person who should receive error messages when there are problems communicating with the marketplace. _____________________ 9. Administrator user name and password for connecting to the B2B server. The default is Administrator. (page 43) _____________________________ 10. Name of your SMTP (Simple Mail Transfer Protocol) server. This is your mail gateway server. (page 43) ____________________________________

iv

INSTALLATION GUIDE ORACLE

OVERVIEW
MAXIMO Release 4.1.1 for Oracle runs on a personal computer running Microsoft Windows, Centura Software Corporations SQLRouter, IBM's Java Runtime Environment (JRE), and Oracle Corporations Networking Software. Together with MAXIMO application files developed by MRO Software and Oracle, these software components make up the MAXIMO applications. This installation guide provides guidelines on what type of hardware configuration you need to run MAXIMO Release 4.1.1 for Oracle, and how to install the MAXIMO software. It also covers how to install Java software components and how to install and manage the Application Server for Business Components (hereafter referred to as Application Server throughout this guide) that is used with those components. This guide also documents the changes that are made to your system files after you install the software. NOTE: This installation guide is only for new installations of MAXIMO using the Oracle database platform.

Installation Qualifications
To perform the installation, you should be familiar with the following:

PC installation tasks such as creating folders, editing files, and running scripts Oracle utilities such as Enterprise Manager or SQL*Plus Oracle system administration MAXIMO System Administration

To complete the installation, you need Oracle database administration privileges.

1

Release 4.1.1

Installation Outline
The main sections of the installation guide, to be completed in sequence, are listed below. In addition, there are several installation appendixes. Page Overview................................................................................................................ 1 Installation Qualifications .................................................................................. 1 Installation Outline............................................................................................. 2 Hardware Configurations....................................................................................... 5 Software Configurations ........................................................................................ 9 Installation Guidelines ......................................................................................... 11 MAXIMO in a Standard Network Environment .............................................. 12 MAXIMO in a Thin Client Environment......................................................... 14 Pre-Installation Procedures .................................................................................. 16 Oracle Checklist ............................................................................................... 16 Configuring Oracle on the Server ........................................................................ 18 MAXIMO Release 4.1.1 Installation ................................................................... 22 Pre-Installation Procedures............................................................................... 23 Installing MAXIMO Application in a Subfolder ............................................. 23 Running the MAXIMO Application Installation Program............................... 24 Setting Up Additional Client Workstations ......................................................... 29 How SETUP.EXE Works................................................................................. 29 Running Setup .................................................................................................. 29 Running the CREATMAX.SQL Script ............................................................... 31 The MAXINST Database Utility ......................................................................... 33 Creating Users for Use with the MAXDEMO Database.................................. 33 Running the MAXINST Program .................................................................... 33 Installation of the MAXIMO Release 4.1.1 Self-service Applications................ 37 Pre-Installation Procedures............................................................................... 37 Running the MAXIMO Self-Service Applications Installation ....................... 38 B2BMessage Service Setup ................................................................................. 46 Configuring the e-Commerce Server ................................................................... 46 webMethods B2B Server Installation and Setup ................................................. 47
2

Installation Guide

Installing the mroBuyer Package in the webMethods B2B Server .................. 48 Configuring the mroBuyer Package in the webMethods B2B Server.............. 51 Reloading mroBuyer Package.............................................................................. 66 search Engine Integration .................................................................................... 67 Verity Configuration............................................................................................ 68 Building Collections......................................................................................... 68 Adding new fields to the Item Collection......................................................... 69 Running Verity as a Windows NT Service ...................................................... 70 Updating the Collections .................................................................................. 70 Managing the Application Server ........................................................................ 72 Application Server Configuration File MXSERVER.PROPERTIES ........... 73 Setting File Security for MXSERVER.PROPERTIES .................................... 80 Final System Setup Checks.................................................................................. 81 Configuring Tomcat to Run With Internet Information Server (IIS) ............... 81 Establishing a Base Currency........................................................................... 81 Accessing Self-Service Applications ............................................................... 82 Editing System Files......................................................................................... 82 Appendix A: Sample Database Configurations .................................................. 99 Appendix B: Identifying the Schema at Login ................................................. 101 Identifying the Schema via the MAXIMO.INI File ....................................... 101 Displaying the Schema Field on the Login Screen ........................................ 102 Identifying the Schema via the Desktop Shortcut .......................................... 103 Appendix C: Running Multiple Instances of the Application Server ............... 105 Starting multiple instances of Application Server using MXSERVER.BAT file................................................................................... 105 Starting the JSP Server using Windows NT Services .................................... 107 Starting multiple instances of the Application Server using Windows NT Services .......................................................................................................... 107 Appendix D: Microsoft Windows NT Server, Terminal Server or Windows 2000 Terminal Services, and Citrix Metaframe................................. 109 Microsoft Windows NT 4.0 Server, Terminal Server Edition and Citrix MetaFrame ......................................................................................................... 109 Recommendations .......................................................................................... 109 Considerations................................................................................................ 110
3

Release 4.1.1

Appendix E: Installation of Online RFQ .......................................................... 113 Running the Online RFQ Setup Program....................................................... 113 Setting Up Additional Client Workstations.................................................... 115 Editing System File ........................................................................................ 115

Installation Guide

HARDWARE CONFIGURATIONS
Before installing MAXIMO Release 4.1.1 for Oracle, make sure that your system hardware is properly configured. MAXIMO Release 4.1.1 for Oracle is designed to run on a local area network (LAN). We recommend that the LAN consist of a file server machine, database server machine, a dedicated Application Server, and a dedicated e-Commerce Server. This configuration offers the best performance. The minimum and recommended requirements for each of the hardware components are: Client Workstation Minimum desktop computer configuration:

Intel-based Pentium 450 MHz processor 64MB of memory for Windows 95/98 or Windows NT Workstation 4.0. For Windows 2000 Professional, the memory requirement is 128MB. 300MB of free space for the application files on a local drive SVGA 1024 x 768 High Color 16-bit color display CD-ROM drive (for initial software installation)

Recommended desktop computer configuration:

Intel-based Pentium 600 MHz processor or greater 96MB of memory for Windows 95/98 or Windows NT Workstation 4.0. For Windows 2000 Professional, the memory recommendation is 128MB. 300MB of free space for the application files on a local drive SVGA 1024 x 768 High Color 16-bit color display CD-ROM drive (for initial software installation)

Minimum laptop computer configuration:

Intel-based Pentium 400 MHz processor

Release 4.1.1

96MB of memory for Windows 95/98 or Windows NT Workstation 4.0. For Windows 2000 Professional, the memory requirement is 128MB. 300MB of free space for the application files on a local drive SVGA 1024 x 768 High Color 16-bit color display CD-ROM drive (for initial software installation)

Recommended laptop computer configuration:

Intel-based Pentium 600 MHz processor or greater 128MB of memory for Windows 95/98 or Windows NT Workstation 4.0. For Windows 2000 Professional, the memory recommendation is 192MB. 300MB of free space for the application files on a local drive SVGA 1024 x 768 High Color 16-bit color display CD-ROM drive (for initial software installation)

Database Server MAXIMO Release 4.1.1 for Oracle can use any database server that supports the following versions: Database Oracle 8.0.6 Oracle 8.1.6, 8.1.7 Supports Net8 version 8.0.6 Net8 version 8.1.6, 8.1.7

Oracle 8.0.6 and Oracle 8.1.6, 8.1.7 are collectively referred to as Oracle 8.0.6 or higher throughout this guide. TCP/IP and SPX protocols are supported. The Oracle Server runs on a wide array of platforms. Contact your Oracle representative for more information. Contact MRO Software for a list of validated Oracle versions. File Server (Optional) You can install the MAXIMO application files on a network file server or on each client workstations local drive. The systems or network administrator can
6

Installation Guide

make this decision. You can use any network operating system that provides a DOS path, partition, or shared volume to the network drive. Application Server The Application Server provides business logic and framework for the MAXIMO Self-Service Applications. We recommend using a dedicated machine running Microsoft Windows NT Server 4.0, with Service Pack 6a, Windows 2000 Server, or Windows 2000 Advanced Server. MAXIMO uses The Apache Software Foundation Tomcat JSP Server for the Java Server Pages (JSP) technology. This webserver is used for accepting HTTP requests from client programs (Web Browsers) and for responding in HTML content. Whenever there is a client request for a JSP page, the JSP page is processed by the webserver and the result of the JSP page is sent back to the client in HTML content. Please refer to the http://java.sun.com/products/jsp/ index.html link for more information on Java Server Pages Technology. The current version of Tomcat JSP Server used by MAXIMO can operate in conjunction with Microsofts Internet Information Server (IIS). This setup is recommended if more than 40 users will be concurrently running self-service applications. For information on setting up your Tomcat JSP Server with IIS, refer to the MAXIMO System Administrators Guide. The current version of MAXIMO supports SSL (Secured Socket Layer). If you use SSL, it must be done in conjunction with IIS. Configuration requirements will vary according to site-specific variables such as Self-Service Applications employed, database platform, number of connecting client workstations, and desired performance levels. While MRO Software does not make any formal requirements relative to hardware/software specifications of the Application Server, we recommend at minimum employing a dedicated, Intel-based Pentium 600 MHz dual processor with 1 GB RAM.

Release 4.1.1

e-Commerce Server (for e-commerce transactions only) The e-Commerce Server complements the Application Server to provide e-commerce business-to-business communication. The e-Commerce Server uses the webMethods B2B Server, version 3.6. It is recommended that the webMethods B2B Server run on a separate dedicated machine. Minimum system requirements:

Intel-based Pentium 450 MHz processor 512 MB RAM

Recommended system requirements:

Intel-based Pentium 600 MHz processor or greater 1 GB RAM

Installation Guide

SOFTWARE CONFIGURATIONS
The following sections list software requirements for MAXIMO Release 4.1.1 for Oracle. MRO Software has tested and validated the versions listed in this section. Client Workstation

Microsoft Windows 95/98, Windows NT Workstation 4.0, Windows 2000 Professional LAN workstation software MAXIMO Release 4.1.1 software Net8 version 8.0.6 or higher Vendor-supplied TCP/IP software (if using TCP/IP protocol)

Oracle supports several TCP/IP software vendors. Contact your Oracle representative for a complete list of supported vendors and versions.

Internet Explorer 5.0, 5.5 or Netscape Communicator 4.7x

Database Server

Oracle8 Server or Oracle 8i including: Procedural Database Option (PL/SQL) Oracle Server Utilities Export Import Net8 version 8.0.6 or higher

Network transport protocol software TCP/IP (supplied with operating system) and/or SPX (supplied with operating system)
9

Release 4.1.1

Application Server

Windows NT Server 4.0 Service Pack 6a, Windows 2000 Server Service Pack 1, Windows 2000 Advanced Server TCP/IP software, supplied with Windows NT Java version 1.3 JDBC version 2.0 drivers

In order to have client workstations communicate with the Application Server using Javas Remote Method Invocation (RMI), you must have TCP/IP installed on the Application Server and the client workstations. Please refer to your Windows documentation for TCP/IP installation, configuration, and management information. Service Packs At release time for MAXIMO Release 4.1.1, MRO Software has certified the following Service Packs: Windows NT (server and workstation): Service Pack 6a Windows NT Server 4.0, Terminal Server Edition: Terminal Server Service Pack 5 Windows 2000: Service Pack 1

NOTE: MRO Software will support MAXIMO with later Service Packs as they are released by third-party vendors. It is the policy of MRO Software to validate its products with the latest possible Service Pack at time of release certification.

10

Installation Guide

INSTALLATION GUIDELINES
NOTE: In addition to these guidelines, you should consult the MAXIMO Release 4.1.1 Release Notes prior to installation. The installation organizes the files on your disk(s) as follows:

MAXIMO Application Files

Component MAXIMO Release 4.1.1 Centura SQLRouter Brio Reports Total MB (complete system) Folder Name MAX411 MAX411 SQR6 Size (MB) 227 38 9 274

Self-Service Application Files

Component Application Server Self-Service Applications e-Commerce Adapter Total MB (complete system) Folder Name MXSERVER MXSERVER MXSERVER Size (MB) 138 15 13 166

We strongly recommend that you use the default folder names shown above (MAX411, etc.). These names are displayed as the defaults during installation and using them helps us to provide better quality support.

11

Release 4.1.1

MAXIMO in a Standard Network Environment

A typical multi-user configuration might appear as follows:

(optional)
Client Workstation(s) Running Windows 95/ 98, Windows NT 4.0, or Windows 2000 Professional File Server Running Network OS Database Server Oracle Server Application Server Running Windows NT 4.0 Server, Windows 2000 Server , or Windows 2000 Advanced Server The Apache Software Foundation Tomcat JSP Server Self-Service Application Server Components e-Commerce Server Running Windows NT 4.0 Server

SPL folder

MAXIMO Release 4.1.1 Brio.Report

MAXIMO database MAXDEMO database Other databases

webMethods B2B Server

12

Installation Guide

In this configuration you have several client workstations, a file server, a database server, an Application Server, and an e-Commerce Server. The client workstation logs into the file server, runs MAXIMO, and accesses data from the database server and/or accesses the Application Server, which accesses data from the database server. The e-Commerce Server communicates to the marketplace. In this example, the file server, database server, Application Server, and the e-Commerce Server are installed on separate machines for optimum performance.

13

Release 4.1.1

MAXIMO in a Thin Client Environment

A typical thin client configuration might appear as follows:
Windows Terminal Server or Windows 2000 Terminal Services, MAXIMO Database Server, Protocols, Thin Clients, Application Server, and e-Commerce Server

MAXIMO Database Server Oracle

MS Windows NT 4.0, Terminal Server Edition (Citrix Metaframe 1.8 optional) OR Windows 2000 Terminal Services MAXIMO Release 4.1.1 Application

Application Server Windows NT Server 4.0 Oracle e-Commerce Server

Wide Area Network RDP and/or ICA Protocols

mroHosting Center

REMOTE SITES
MAXIMO Thin Clients Citrix ICA RDP MAXIMO Thin Clients Citrix ICA RDP

Figure 1 Typical Thin Client Configuration

14

Installation Guide

Users who prefer a thin client solution can implement MAXIMO with Microsofts Windows NT Server 4.0, Terminal Server Edition (WTS) and Citrixs MetaFrame version 1.8 add-on or Windows 2000 Server/Advanced Server via Terminal Services,. This configuration can provide improved performance over Wide Area Networks and remote locations. Workstations that do not meet MAXIMO hardware requirements can benefit in a WTS environment. Microsofts Terminal Server and Windows 2000 Terminal Services allow you to implement server-based computing, where all MAXIMO application processing is executed on the server. Windows NT Workstation desktops and/or Windows 2000 Professional are distributed and displayed to client machines. The MAXIMO application can then communicate with a database located on a separate server box. In terminal server-based computing, only the users keystrokes and mouse clicks travel the network. MetaFrame, from Citrix Systems, Inc, is an add-on to Microsofts Terminal Server. Along with its efficiency over Wide Area Networks, MetaFrame also provides many important features, including load balancing, application publishing, and Application Launching and Embedding (ALE). MetaFrame does not require a 32-bit Windows client environment. Supported clients include DOS, Windows 3.x, Windows 95/98, NT Workstation, and Windows 2000 Professional. Thus, using thin client technology, you can run MAXIMO from clients that do not meet MAXIMO Release 4.1.1 hardware and software minimums. MAXIMO installation procedures may be different under Terminal Server and Windows 2000 Terminal Services. Throughout this guide, you will find Terminal Server notations whenever appropriate and Windows 2000 Terminal Services notations whenever appropriate. For further information on MAXIMO Release 4.1.1 in a thin client environment, please contact the Systems Support group at 1-800-243-7734.

15

Release 4.1.1

PRE-INSTALLATION PROCEDURES
Before you begin the MAXIMO Release 4.1.1 application files installation, perform the following procedures on your client workstation(s).

Make sure you have at least 300MB of free disk space available. The 300MB are required either on the local hard drive or a network drive for application files. We recommend that you use the standard SVGA 1024 x 768 High Color 16-bit display driver in Windows Setup. Other third-party drivers may not be compatible with MAXIMO application software. Close down all Windows programs except Windows Explorer. Install Internet Explorer 5.0, 5.5 or Netscape Communicator 4.7x.

Oracle Checklist
The following tasks must be performed before you can begin the Release 4.1.1 installation. These steps will verify that your client(s) can communicate with the Oracle server using Net8 version 8.0.6 or higher. This is an outline of recommended tasks; consult your Oracle documentation for more detailed information.

Database Server
1. Install the Oracle8 Server RDBMS on your database server machine. You must install the Procedural Option (PL/SQL) when you install the Oracle software. 2. Select PL/SQL from the Oracle installation menu.

16

Installation Guide

3. Create an Oracle database with the following minimum tablespace sizes: all small SYSTEM (system data) TEMP (temporary) RBS (rollback segments) 10MB more than default 15MB 15MB 50MB 100MB 100MB 200MB

medium TEMP (temporary) RBS (rollback segments) large TEMP (temporary) RBS (rollback segments)

Oracles database creation utilities provide a minimum size for the SYSTEM tablespace. Adding 10MB to this minimum will provide the requirements for MAXIMO. Oracle on some operating systems (Windows NT or NOVELL platforms) uses the names TEMPORARY_DATA and ROLLBACK_DATA for the temporary and rollback tablespaces, respectively. A sample database configuration is provided in Appendix A at the end of this guide. 4. Start the Oracle database. 5. Verify that the procedural option is installed. Run the Oracle utility SQLPLUS. If the procedural option is installed, the PL/SQL version is displayed in the banner. If it is not installed, you must re-install the Oracle software. To ensure that the Procedural Option Catalog has been created, connect as user SYSTEM with the SQLPLUS utility and run the following command: SELECT COUNT(*) FROM USER_TRIGGERS;

17

Release 4.1.1

If you get this message: ORA-00942: TABLE OR VIEW DOES NOT EXIST you should run the CATPROC.SQL script (found in the Oracle rdbms/admin folder). In order to run this script, you must connect as SYS or INTERNAL. NOTE: This process may take 5 to 15 minutes to complete. 6. Start the TNS listener process on the server.

CONFIGURING ORACLE ON THE SERVER

In the next step you modify a database on the server to hold your data. The following series of commands is given as a guideline for configuration changes. Please refer to Oracle documentation for more details on these commands. The parameters are suggested parameters only; you may need to adjust them depending on server disk space and site requirements. If you have an existing database you may not need to perform each of the steps shown below.

Altering the System Tablespace

Connect to Oracle using Oracles Enterprise Manager or SQL*Plus utilities (located on the server or the workstation). You must connect to an account with DBA authority (e.g., the SYSTEM account): CONNECT SYSTEM/password Increase the size of the SYSTEM tablespace if the free space in the SYSTEM tablespace is less than 10MB. You can view the amount of free space by running the following statement: SELECT TABLESPACE_NAME, SUM (BYTES) FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME;

18

Installation Guide

You can view the existing data files by running the following statement: SELECT * FROM DBA_DATA_FILES WHERE TABLESPACE_NAME = SYSTEM; You can use the AUTOEXTEND feature to permit the SYSTEM tablespace datafile to expand. The following statement would permit expansion up to 150 MB: ALTER DATABASE DATAFILE system datafile name AUTOEXTEND ON MAXSIZE 150M; If you choose not to use the AUTOEXTEND feature, you will need to add a file to the SYSTEM tablespace. To determine your naming convention, query the DBA_DATA_FILES table; for example: SELECT * FROM DBA_DATA_FILES ALTER TABLESPACE SYSTEM ADD DATAFILE filename SIZE 10M; where filename is the name of the data file. For example: D:\ORANT\DATABASES\ORCL\ORCLDATA.ORA where D: is the local drive on the server and not the network drive of the client performing database alteration.

Creating MAXIMO Tablespaces

With Release 4.1.1 of MAXIMO, there is an option called multi-schema. This feature enables the application tables to be owned by a user other than MAXIMO, thus permitting multiple MAXIMO schemas to reside in a single Oracle instance.

19

Release 4.1.1

In addition, the MAXIMO schema can be split so that all tables reside in one tablespace and all indexes in a second. The MAXIMO schema to which a user connects is determined either by:

modifying the SCHEMA=ORACLE_USERID line in the System section of the MAXIMO.INI file or

modifying the MAXIMO Database Login dialog box by changing the Schema field from hidden to unhidden so that the user can enter the schema owner.

If omitted, the default schema owner is MAXIMO. See Appendix B for information on using schemas other than MAXIMO. The size of a MAXIMO tablespace is determined by the expected size of your database. If you are installing the MAXDEMO database, create a MAXIMO tablespace of size 30MB. If you are creating a live database, use the estimated size of the database, for example, 100MB. You can use the AUTOEXTEND option of the CREATE TABLESPACE command to permit growth, or add another datafile to the tablespace later on. We recommend using related names for MAXIMO schemas and tablespaces. For example, if you wished 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. (There is only one tablespace name for MAXDEMO as there is no benefit to splitting a small demo database.) Some general guidelines for estimating tablespace size are:

small database medium database large database

100MB 200MB 400MB

20

Installation Guide

To create a tablespace: CREATE TABLESPACE tablespace_name DATAFILE filename SIZE filesize AUTOEXTEND ON MAXSIZE maximum DEFAULT STORAGE (INITIAL 40960 NEXT 40960 PCTINCREASE 20); where tablespace_name is the name for this MAXIMO tablespace, filename is the name of the data file, filesize is the initial size of the data file, and maximum is the maximum size to which it can grow. Both filesize and maximum can be expressed as a number of megabytes, when followed by the letter M (e.g., 100M). Storage parameters may be customized for the particular database instance. NOTE: The file name is the full path of the server. This includes the local drive of the server and path location to the data files. For example: D:\ORANT\DATABASES\ORCL\ORCLDATA.ORA where D: is the local drive on the server and not the network drive of the client performing database alteration. You will need 150K of free rollback segment space to perform the MAXIMO database installation.

21

Release 4.1.1

MAXIMO RELEASE 4.1.1 INSTALLATION

Installing MAXIMO software requires system administrator rights and authorities and should be performed by the LAN or systems administrator. NOTE: If you purchased the Citrix MetaFrame option from MRO Software, please refer to the Citrix MetaFrame Option Installation Guide for installation of MAXIMO and the Citrix MetaFrame Option. Before you begin the MAXIMO Release 4.1.1 installation, make sure you have completed the pre-installation procedures (page 16). NOTE: If you are using a file server, the installation should be run from a client workstation that is logged into the network file server. If you have Windows Terminal Server or Windows 2000 Terminal Services, the installation should be run from either Windows Terminal Server or Windows 2000 Server/Advanced Server in install mode. During the installation process you are required to provide the Oracle connect string. Refer to the earlier section, Oracle Checklist (page 16), if you do not know the Oracle connect string.

22

Installation Guide

Pre-Installation Procedures
If you purchased Workflow, before installing MAXIMO Release 4.1.1 you must determine the method you will use for all client machines to connect to the Application Server: via HTTP (the default), or via a mapped drive. In general, we recommend using HTTP. If you choose to connect via mapped drive, all client machines must be mapped identically. For example, all client machines could be mapped as F:\MXSERVER. If you choose to connect via HTTP, an example would be http:\\appsrvr. NOTE: If you are using Workflow, you will be prompted for the Application Server URL or network address during the MAXIMO installation program. The URL or network address that you enter is written to the MAXIMO.INI file. You might not know the URL or drive mapping of the Application Server since it is not yet installed. You can edit the MAXIMO.INI file after the Application Server is installed to specify the correct URL or drive mapping. For more information, see MAXIMO.INI Application Server Settings, page 84. When youve determined how you will connect all client machines to the server, you are ready to install MAXIMO Release 4.1.1. You need at least 300MB of free disk space for the MAXIMO Release 4.1.1 Application files.

Installing MAXIMO Application in a Subfolder

NOTE: If you are using Windows Terminal Server or Windows 2000 Terminal Services, install MAXIMO locally on the Windows Terminal Server or on Windows 2000 Server/Advanced Server, respectively. If you want to install the MAXIMO software in a subfolder on a network drive for example, MAXAPPwe recommend that you create a subfolder first, share
23

Release 4.1.1

the folder, assign a drive letter for that subfolder, and connect that network drive as the root. Then run the installation program. Indicate that drive letter followed by the path (if necessary) when prompted by the installation program. You should also use this drive letter in the future when referencing any path that is related to MAXIMO.

Examples

Drives can be mapped in a variety of ways depending on your operating system. Refer to your operating systems documentation for more information. To set up Drive X as the MAXIMO drive, enter: NET USE X: \\FSNAME\MAXAPP

Windows NT LANs

Novell NetWare

To set up Drive X as the MAXIMO drive, from DOS enter: MAP ROOT X:=FSNAME\VOL:MAXAPP

Running the MAXIMO Application Installation Program

Installing MAXIMO should take about 10 minutes. To run the MAXIMO installation program, perform the following steps: NOTE: We recommend that you exit all other Windows programs (e.g., Word, Excel) before continuing. You may leave Windows Explorer open. 1. Insert the License Disk into drive A. 2. Insert the MAXIMO Release 4.1.1 Application CD into the CD-ROM drive. Autorun.exe will start the installation process. 3. If the installation does not start automatically, choose Start/Run. Type: d:\Autorun (where d is your CD-ROM drive) and select OK or press Enter. or Using Windows Explorer, open your CD-ROM drive folder and double-click AUTORUN.EXE.
24

Installation Guide

NOTE: If you have already installed some components of the MAXIMO Release 4.1.1 Application, Autorun.exe may not launch setup. You will need to run Setup.exe from the SETUP folder. 4. From the MAXIMO Release 4.1.1 dialog box, select Start to begin the installation process. NOTE: If the installation program detects that you are installing to Windows Terminal Server or Windows 2000 Terminal Services, continue to step 5. If the program does not detect Windows Terminal Server or Windows 2000 Terminal Services, go to step 11. 5. A dialog box asks if you purchased the Citrix MetaFrame option for Windows Terminal Server from MRO Software. Choose Yes if you purchased this option. If you did not purchase this option, select No and go to step 10. 6. A dialog box asks if you want to install the Citrix MetaFrame option with MAXIMO on this machine. Choose Yes to install this option. If you did not want to install this option, select No and go to step 10. 7. Insert your Citrix MetaFrame CD, then select OK. If the setup does not start automatically, choose Run from the Start menu and Browse to SETUP.EXE. NOTE: Refer to your Citrix MetaFrame documentation for instructions on how to install Citrix MetaFrame. 8. After the Citrix MetaFrame setup is complete, restart your machine and reinsert the MAXIMO Release 4.1.1, Application CD into the CD-ROM drive. Autorun.exe will start the installation process. 9. If the installation does not start automatically, choose Start/Run. Type: d:\Autorun (where d is your CD-ROM drive) and select OK or press Enter. or Using Windows Explorer, open your CD-ROM drive folder and double-click AUTORUN.EXE.

25

Release 4.1.1

10. Before the MAXIMO Setup installation starts, the Windows Terminal Server or Windows 2000 Terminal Services user mode is checked. If the user mode is not in install, you will be prompted to change to install mode or exit the install. Choose install mode to continue the MAXIMO Setup installation. 11. The MAXIMO Setup installation program displays a series of screens and dialog boxes. Most of these are listed below, along with comments that may be relevant to some of your choices. Follow the on-screen instructions. Welcome Note that it is recommended that you exit all other Windows programs (e.g., Word, Excel) before continuing. You may leave Windows Explorer open. Specify License Location The License Location should be the drive into which you placed the License Diskette. The default is A:\. Specify another drive if appropriate. Product Registration Register your name and company for this installation of MAXIMO. Choose the default or enter new information. Choose Setup Type

Network Installs all MAXIMO components on the network server. This method does not set up this machine to run the MAXIMO applications. Local Installs all MAXIMO components on this workstation. Sets up this workstation to run the MAXIMO applications from the local hard drive to the network database server. Client Configures this workstation to run the MAXIMO applications. MAXIMO components must already be installed on the network server.

NOTE: If you have Windows Terminal Server or Windows 2000 Terminal Services, choose Local installation on the Windows Terminal Server or Windows 2000 Server/Advanced Server, respectively.

26

Installation Guide

Choose Location Enter the location where you want to install the MAXIMO applications. The default location is the local drive in the Program Files\MAX411 folder. Use the Browse option to select a different drive or path. You also specify the Installation Mode here:

Full Installs all MAXIMO components. Custom Lets you choose which MAXIMO components to install.

We recommend you choose Full, the default. Choose Reports Destination Location Enter the destination location of the folder to which the installation program should install reports and the files necessary to run reports. Choose the default (SQR6) or enter another folder. Oracle Configuration Enter the database alias and the Oracle connect string. The database alias is any character string, up to eight characters, that MAXIMO users will enter as the database name when connecting to MAXIMO. The Oracle connect string is the string used to establish the connection to the database (see page 16 for more information). Database Information (This dialog box is displayed only if you purchased Workflow.) Enter the database alias you will be using and the host name of the Application Server. Choose Server Connection (This dialog box is displayed only if you purchased Workflow.) Specify the server connection type. Select the method you will be using for all clients to connect to the Application Server (see page 23). Enter the URL if you select HTTP; specify the mapped folder on the server if you select Mapped Drive. NOTE: If you purchased Workflow and do not know the URL or drive mapping, or it later changes, you can edit the MAXIMO.INI file to

27

Release 4.1.1

specify the path to the Application Server. See MAXIMO.INI Application Server settings, page 84. Modifying File (This dialog box is displayed only if you have Windows 95/98.) Indicates the lines that need to be added to your AUTOEXEC.BAT file. You may select to have these lines added automatically through the installation, save the changes to AUTOEXEC.SAV to add later on, or not to make any changes to AUTOEXEC.BAT at this time. Select Program Folder Creates a new MAXIMO Release 4.1.1 folder (unless you specify otherwise) for containing all the icons. This dialog box is not displayed if installing to a subfolder on a network drive. MAXIMO Release 4.1.1 The actual installation process occurs here. The screen displays the status of the installation as it progresses. Setup Complete This dialog box informs you that Setup has finished copying files to your computer. If the Setup program determines that it is necessary, it prompts you to reboot your computer prior to running MAXIMO. Remove disks from the disk drives before you restart your computer. Click Finish to exit the Setup program. NOTE: Windows 95/98 and Windows 2000 users using Microsofts version of IPX/SPX to connect to a NetWare database server may experience problems. We recommend that Windows 95/98 and Windows 2000 users utilizing IPX/SPX install the NetWare client connectivity files. NOTE: If you have Windows Terminal Server, Windows 2000 Terminal Services, or have installed MAXIMO locally, see the section Running the CREATMAX.SQL Script (page 31) as no MAXIMO client setup is necessary.

28

Installation Guide

SETTING UP ADDITIONAL CLIENT WORKSTATIONS

If you chose the Network setup option during the MAXIMO Release 4.1.1 installation, you need to set up the system files on any client workstations that will be running MAXIMO. To do this, go to each client workstation and run the client installation program, SETUP.EXE from the MAX411\CLIENT folder. This automatically edits the client system files and creates the program group.

How SETUP.EXE Works

During the MAXIMO installation an M:\MAX411\CLIENT folder is created (where M is the name of the drive on which you installed MAXIMO). It contains a complete client workstation setup program called SETUP.EXE. The client installation program performs the following tasks:

Copies the files LIBSTI.INI and SQR.INI into the Windows or WINNT folder on the client workstation; this enables the client workstation to run reports using Brio.Report. Updates the path and registry of client workstation Creates a local spool folder (C:\SPL). Creates a MAXIMO Release 4.1.1 program folder group and a MAXIMO Release 4.1.1 icon on the desktop.

Running Setup
To run the client installation program, perform the following tasks from each additional client workstation connected to the network: 1. Run Windows Explorer. Go to the CLIENT subfolder of the MAX411 folder and double-click on SETUP.EXE.

29

Release 4.1.1

NOTE: You can also access the Client Setup program from the MAXIMO Release 4.1.1, Application CD. Execute SETUP.EXE and choose Client Setup from the Choose Setup Type screen. Note that if you choose this method, you must specify the network location of the MAXMAST.OUT license file; the Setup program will fail if you specify the license diskette as the license file location. 2. The Setup program displays a series of screens. Respond to the on-screen instructions. 3. Restart your computer. 4. Repeat the procedure for each additional client workstation. To run MAXIMO Release 4.1.1, the MAXIMO Release 4.1.1 folder must be in the path of the workstation. For a client installation on a Windows 95/98 workstation using the NetWare 32 client, the system login scripts will need to be edited to add the MAX411 folder to the workstation's configuration.

30

Installation Guide

RUNNING THE CREATMAX.SQL SCRIPT

The CREATMAX.SQL script is used to create the schema (userid) and the standard userids SYSADM, SYSSQL, and DEFLT. This file is initially set to use MAXIMO as both the schema and as the name for the tablespace where tables and indexes will be created. If you want to use different schema or tablespace names, then you must edit CREATMAX.SQL and substitute the names you have chosen for the italicized words in the example below. Schema Datats The schema (userid) that will own the tables. The name of the tablespace to hold the MAXIMO tables (and indexes if the optional index tablespace is not used). The name of the tablespace to hold MAXIMO indexes (optional).

Indexts

grant connect, resource, DBA to SYSADM identified by SYSADM; grant connect to SYSSQL identified by SYSSQL; grant connect to DEFLT identified by DEFLT; alter user SYSADM default tablespace datats; alter user SYSSQL default tablespace datats; alter user DEFLT default tablespace datats; grant connect, resource to schema identified by schema password; grant DBA to schema; revoke unlimited tablespace from schema; alter user schema default tablespace datats quota unlimited on datats; alter user schema temporary tablespace temp; grant create public synonym to schema; grant drop public synonym to schema; grant create user to schema; grant drop user to schema; Important: Ensure that the alter user schema temporary tablespace temp line reflects your temporary tablespace name.
31

Release 4.1.1

Add the following line if you are using a separate index tablespace: alter user schema quota unlimited on indexts; Connect to the database as SYSTEM. Then:

From SQL*Plus, enter: @C:\PROGRAM FILES\MAX411\MAXINST\CREATMAX.SQL OR

From SQLTalk, enter: run C:\PROGRAM FILES\MAX411\MAXINST\CREATMAX.SQL; where C in both of these commands is your drive letter.

When the script is finished running, exit SQL*Plus or SQLTalk.

32

Installation Guide

THE MAXINST DATABASE UTILITY

The MAXINST program automates the process of installing the MAXIMO or MAXDEMO database to an existing Oracle instance. This program loads either the MAXDEMO or MAXIMO database; creates database views; creates MAXIMO demo tables, indexes, and grants; creates and populates the rowstamp column in the Oracle tables; creates database triggers; and sets the initial database password. Do not change the initial password until after installation is complete, and then only via the Signature Security application.

Creating Users for Use with the MAXDEMO Database

If you plan to install the MAXDEMO database, you need to create three demo database users prior to running MAXINST. Via SQL*Plus, create the users with the following commands. grant connect to SMITH identified by SMITH1; grant connect to LIBERI identified by LIBERI; grant connect to WINSTON identified by WINSTON;

Running the MAXINST Program

IMPORTANT: NOTE: The MAXINST Program MUST be executed from a client workstation.

If you are using Windows Terminal Server or Windows 2000 Terminal Services, run the MAXINST program directly on the Windows Terminal Server console or on the Windows 2000 Server/Advanced Server console, respectively.

To run the MAXINST program, the MAXIMO Release 4.1.1 folder must be in the path of the workstation used to create the database and all other workstations. For a Windows 95/98 workstation, you should modify the AUTOEXEC.BAT file and append the path environment variable to include the MAX411 folder. For
33

Release 4.1.1

Windows NT 4.0, append the path environment variable via the Control Panel/ System/Environment tab. For Windows 2000 Professional, append the path environment variable via the Control Panel/System/Advanced tab and click the Environment Variables button. A NetWare 32 client will need to edit the system login script to add the MAX411 folder to the workstations configuration. These steps need only be performed on the workstation that will be used to create the database and can be removed upon completion of the program. Run the MAXINST program as described below to build the MAXDEMO or MAXIMO database schema. 1. Select Start/Run and run the MAXINST program, by default located in the folder listed below; or use Windows Explorer to open the folder and doubleclick MAXINST.EXE. X:\PROGRAM FILES\MAX411\MAXINST\MAXINST.EXE where X is the drive letter. 2. In the Connect dialog box, enter the database alias name you specified during the MAXIMO installation. Enter the user name and password of the schema owner that you specified in the CREATMAX.SQL file. Click OK.

Figure 2 Connect Dialog Box

34

Installation Guide

3. Enter the SYS password in the Oracle SYS Connect dialog box.

Figure 3 Oracle SYS Connect Dialog Box

4. Specify the tablespace names for the tables and indexes to be created, or accept the defaults.

Figure 4 Database Objects Storage Dialog Box

35

Release 4.1.1

5. In the MAXIMO Database Installation Utility dialog box, click MAXDEMO to create a demo database, or MAXIMO to create an empty database.

Figure 5 MAXIMO Database Installation Utility Dialog Box

The process of installing the database generally takes about 15 to 30 minutes. It can take longer, depending on the server configuration. The program displays a message when the database is successfully built.

36

Installation Guide

INSTALLATION OF THE MAXIMO RELEASE 4.1.1 SELF-SERVICE APPLICATIONS

There are two self-service application installation programs:

Self-Service Work Requests (Enterprise only) Self-Service Requisitions (Extended Enterprise which includes e-Commerce Adapter and all of its components)

If you purchased Extended Enterprise, be certain to insert the correct CD as indicated in the instructions below. We strongly recommend that you install the MAXIMO Self-Service Applications on a dedicated machine. MAXIMO Self-Service Applications should not be installed to Windows NT Terminal Server or Windows 2000 Server with Terminal Services.

Pre-Installation Procedures
Before you begin the MAXIMO Release 4.1.1 Self-Service Applications and component installation(s), perform the following procedures: On your Application Server:

Install Windows NT 4.0 Service Pack 6, Windows 2000 Server, or Windows 2000 Advanced Server

Make sure you have at least 200 MB of free disk space on your computer.

37

Release 4.1.1

On your network:

Make sure you have configured your database server and completed installation of the database connectivity software.

You do not need to have MAXIMO installed on the computer. Finally, make sure you know where your license file is located.

Running the MAXIMO Self-Service Applications Installation

The MAXIMO Self-Service Applications installation program contains all the files necessary to run the Application Server. The number of components you receive will be dependent upon whether you purchased Enterprise (the Self-Service Work Requests Installation) or Extended Enterprise (the Self-Service Requisitions Installation). Each component contains all the files necessary for that component. For Self-Service Work Requests, the components are:

Application Server Self-Service Applications (Work Requests, Java Inbox)

For Self-Service Requisitions, the components are:

Application Server e-Commerce Adapter Self-Service Applications (Work Requests, Java Inbox, Self-Service Requisitions)

Installing the MAXIMO Self-Service Applications should take about 15 minutes.

38

Installation Guide

Starting the Setup Installation Program

1. Log in to Windows NT as Administrator. 2. Insert license diskette into drive A:\. 3. If you purchased Extended Enterprise or one or more of its components, insert the CD labeled MAXIMO Release 4.1.1 Self Service Requisitions into the CD-ROM drive. If you did not purchase Extended Enterprise or one or more of its components, insert the CD labeled MAXIMO Release 4.1.1 Self Service Work Requests into the CD-ROM drive. 4. To start the installation program, choose Start/Run then type d:\Setup (where d is your CD-ROM drive), then click OK or press Enter. or Use Windows Explorer to open your CD-ROM drive folder, then double-click SETUP.EXE.

Setup Installation Program Screens and Dialog Boxes

The Setup installation program starts and displays a series of screens and dialog boxes. Most of these are listed below, along with comments that may be relevant to some of your choices. NOTE: The installation program asks questions and uses your answers to some of the questions to update the MXSERVER.PROPERTIES initialization file. The Application Server and components use this file. You can edit the MXSERVER.PROPERTIES file with Notepad if you need to change some of these values later. Refer to the Application Server configuration file section on page 73 for more information on the MXSERVER.PROPERTIES file.

39

Release 4.1.1

On-Screen Instructions: Welcome You should close all other Windows programs (e.g., Word, Excel) before continuing. You may leave Windows Explorer open. Specify License Location The default location of the license file (MAXMAST.OUT) is the A:\> drive. Your license file may not necessarily be on that drive. If necessary, use the Browse option to specify another location. Choose Destination Location Enter the location where you want to install the MAXIMO Self-Service Applications. The default location is the local drive in the MXSERVER folder. Use the Browse option to select a different drive or path. Select Components Select the components that you want to install.

Figure 6 Select Components (for Self-Service Requisitions) Dialog Box

40

Installation Guide

Figure 7 Select Components (for Self-Service Work Requests) Dialog Box

The Application Server option installs the base Application Server. This option must be selected for the initial installation. The Self-Service Applications option installs all associated Self-Service files including Work Requests and the Workflow Inbox. If you purchased Extended Enterprise, the Self-Service Application component will also install all self-service requisitions. The e-Commerce Adapter option should only be selected if you plan on connecting to the mroHosting Center. Do not select this option if you are not connecting to the mroHosting Center or if you are installing Self-Service Work Requests. Database Information Enter the Oracle host name (database server name) Oracle Listener Port (Port Number), Oracle Instance (SID) and the schema owner of the database. The default schema owner is MAXIMO. The installation program uses this value to update the mxe.db.url and the mxe.db.schemaowner properties.

41

Release 4.1.1

Database User Information Enter the username and password of the user that owns the MAXIMO database tables. The installation program uses these values to update the mxe.db.user and mxe.db.password properties. E-mail Notification Information Enter the e-mail address of the administrator. The installation program uses this value to update the mxe.workflow.admin property. B2B Server Connection Information (This dialog box is displayed only if you have selected e-Commerce Adapter.)

Figure 8 B2B Server Connection Information Dialog Box

42

Installation Guide

Enter the local webMethods B2B Server host name. This is the name of the local host server where webMethods B2B server is installed (your e-Commerce Server). Enter the B2B Server Port Number, the default is usually OK. Enter the e-mail address of the person who should receive error messages when there are problems communicating with the marketplace. B2B Server User Information (This is displayed only if you have selected e-Commerce Adapter.) Enter the administrator user name and password required for connecting to the B2B Server. SMTP Host Information Enter the SMTP host name (the mail server). This install program uses this name to update the mail.smtp.host property.

Figure 9 New Catalog Provider Dialog Box

New Catalog Provider (This dialog box is displayed only if you have selected e-Commerce Adapter.)

43

Release 4.1.1

Enter the Customer Company ID, Catalog Name, and Vendor Code. For detailed information on these, refer to the Catalog Properties section for the webMethods B2B Server, page 80. The Reply URL field is not currently used. Select Program Folder The installation program creates an entry in the Start Program Group with items for starting the MAXIMO Self-Service Applications. Windows NT Service (This dialog box is displayed only if you have selected the Application Server to be installed.) You can choose to have the Application Server and the Verity Search Engine run as a Windows NT service. A Windows NT service automatically starts as the server is started. The service runs without requiring that a user be logged into Windows NT. Start Copying Files The installation process starts here. The screen displays the status of the installation as it progresses. Setup Complete The setup is complete once the program has copied the files. The installation program displays a message asking if you would like to reboot your computer only if you have elected to install the Application Server as a Windows NT service. NOTE: If you are using Workflow, you need to verify that the MAXIMO.INI file has the correct entry for the path to that server. See MAXIMO.INI Application Server settings, page 84. NOTE: When the Application Server is running, and if you selected e-Commerce Adapter and completed all the mro prompts, the mro administrator will receive outbound transaction e-mail error messages until webMethods B2B Server is installed and configured.

44

Installation Guide

If the MXServer is configured to connect to the webMethods B2B Server but the webMethods B2B Server is not running, then an error message, Error connecting to B2B Server, is displayed. However, if MXServer is running as a Service, this error message is not displayed as this error message can only be viewed from the Command Prompt. When the Process PO Cron is turned on but the B2BMessage Service is not loaded or configured then an error message, Unable to find B2Bmessage service, is displayed. NOTE: If the e-Commerce Adapter component was not purchased, then you should proceed directly to Search Engine Integration (page 67).

45

Release 4.1.1

B2BMESSAGE SERVICE SETUP

If you installed the e-Commerce Adapter component, the B2BMessage Service must be loaded for communication to the e-Commerce Server. The B2BMessage Service is added to the MAXSERVICE table during the installation of MXServer and a connection is made to the database. If your database did not yet exist during MXServer installation or the MXServer could not connect during this installation, then the B2BMessage Service has not been added to the B2BMessage Service table. This can be done through the ADDB2B batch file located in the <MXSERVER ROOT> folder. After running the ADDB2B batch file, a successfully run message is displayed. If the B2BMessage Service has already been added to the MAXSERVICE table, you will get a duplicate data message screen.

CONFIGURING THE E-COMMERCE SERVER

If you have e-Commerce Adapter, you need to have webMethods B2B Server installed in order to connect to mroHosting Center for ordering via the Internet. webMethods B2B Server must be installed on the e-Commerce Server.

46

Installation Guide

WEBMETHODS B2B SERVER INSTALLATION AND SETUP

To install webMethods, perform the following tasks on the e-Commerce Server: 1. Insert the MAXIMO Release 4.1.1 Self-Service Requisitions CD into the CD-ROM drive. 2. Print the INSTALL.DOC which resides in the webMethods subfolder. 3. Run Windows Explorer. Go to the webMethods subfolder and double-click on the executable file (B2BSSSL36.EXE). 4. The setup program displays a series of screens. Respond to the on-screen instructions. 5. When prompted, enter the valid webMethods license key supplied with this release as noted in the INSTALL.DOC. 6. Note whether or not you are installing the B2B Integration Server as a Windows NT Service. You will need this information to complete the next section. 7. Once the installation has been successfully completed, a screen is displayed saying the same. 8. Open the SERVER.BAT file located in the SERVER3\BIN subfolder. Modify this file to run in the Java 1.2.2 environment as follows: Set the following two parameters:
a. SET JDKDIR=C:\webMethods\Server3\jvm b. SET SUNCMD=JAVA (your path to the java machine)

Remove the following text: c. From the classpath, delete: %JDKDIR%\LIB\RT.JAR 9. Restart your computer.

47

Release 4.1.1

Installing the mroBuyer Package in the webMethods B2B Server

The mroBuyer Package is a combination of services that enable MAXIMO and the e-Commerce Adapter to communicate with each other. 1. On the e-Commerce Server, map a network drive to the Application Server. 2. Copy the file MXSERVER\WM\MROBUYER.ZIP located on the Application Server to the folder WEBMETHODS\SERVER3\REPLICATE\ INBOUND. The REPLICATE folder and INBOUND subfolder will need to be created on your computer. 3. If you installed the B2B Integration Server as a Windows NT Service, continue to the next step. If you did not install the B2B Integration Server as a Windows NT Service, from your Command Prompt you must run the SERVER.BAT file located in the following subfolder: WEBMETHODS\SERVER3\BIN 4. Open your browser and type the URL: http://<host name of the webMethods B2B Server>:5555. For example http://comsrv:5555. 5. Enter the username and password. By default, the username is Administrator and the password is manage. 6. Select Packages and then select Package Management. The Package Management Functions screen is displayed.

48

Installation Guide

Figure 10 Package Management Functions

7. Use Install Inbound Packages and select mroBuyer.zip from the Package name drop-down. Check the Enable Upon Installation box and click Install. The following message should be displayed at the top of the screen. mroBuyer package installed and activated. 8. Go back to the Packages screen and check if the Loaded and Enabled buttons for the mroBuyer Package are green in color.

49

Release 4.1.1

Figure 11 Packages Screen

If the color is yellow, it indicates that some pieces of software are enabled and others are not. If the color is red, it indicates that either none of the services are loaded or the package is not enabled. Try enabling the package by clicking the Enabled button. To view reasons for the package not being properly installed, click on the Loaded button for the package to display error messages.

50

Installation Guide

Configuring the mroBuyer Package in the webMethods B2B Server

To configure the mroBuyer package, click the Home button of the mroBuyer package to display the mroBuyer Administration home page.

Figure 12 mroBuyer Administration Home Page

51

Release 4.1.1

Logging Administration
The Logging Administration option allows the user to log incoming or outgoing transactions. 1. Click Logging Administration to display the Logging Administration page.

Figure 13 Logging Administration

2. Select either of the two check boxes, Log outbound transactions to files? or Log inbound transactions to files? 3. Click Submit to create log files in the following subfolder: WEBMETHODS\SERVER\PACKAGES\MROBUYER\PUB\LOGS\INBOUND (or OUTBOUND) 4. To display outbound XML files, click on display in the Log outbound transactions to files? row. To display inbound XML files, click on display in the Log inbound transactions to files? row. The list of transactions in the respective folder is displayed.
52

Installation Guide

For example, a processed (PROCESS) purchase order (PO) that occurs during revision 5 (005) on May 31, 2000 (20000531) would be given the following file name and numbered in sequence beginning with 1 and assigned the extension XML. The file name would appear in the INBOUND or OUTBOUND folder as: PROCESS_PO_005_20000531-1.XML. 5. Choose the transaction that you want to display.

Inbound Connection Administration

The mroBuyer package takes the incoming transactions from mroHosting Center and starts inbound transactions in the Application Server. The MAXIMO transaction services require user name, password, and hostname parameters to connect to the Application Server. These values are read from the configuration file which contains the default values username=MAXIMO, password=MAXIMO and hostname =localhost/MXServer. If you need to change these values, go to the mroBuyer packages Inbound Connection Administration page and change the connection item MXServer. To configure the Inbound Connection Administration: 1. Select Inbound Connection Administration from the mroBuyer Administration home page to display the Inbound Connection Administration page.

53

Release 4.1.1

Figure 14 Inbound Connection Administration

2. Select the MXServer connection name to display the Modify Connection MXServer screen.

Figure 15 Modify Connection

54

Installation Guide

3. Modify the entry in the Host Server / URL field to reflect Application Server. For example, appsrv/MXServer, where appsrv is the Server on which the Application Server is running and MXServer is the name of the Application Server. 4. Change the username and password to the appropriate ones that are used for connecting to the Application Server. 5. Click Submit to save the changes. Select mroBuyer Home to return to the mroBuyer Administration Home page.

Outbound Connection Administration

To configure the Outbound Connection Administration, choose Outbound Communication Administration.

55

Release 4.1.1

Configuring webMethods B2B Server to a remote webMethods B2B Server Click Outbound Connection Administration to display the Outbound Connection Administration page.

Figure 16 Outbound Connection Administration

56

Installation Guide

1. Choose the RemoteB2B connection name entry to modify the outgoing connection between the local B2B Server and the remote B2B server. The Modify Connection RemoteB2B Server page is displayed.

Figure 17 Modify Connection RemoteB2B Server

2. In the Type field, select B2B Server.

57

Release 4.1.1

NOTE: The Host Server / URL field must be acquired from the RemoteB2B server's administrator. These values can only be completed by calling the MRO Software Communications Department as described in the worksheet at the beginning of this manual. The telephone number is (519) 642-6055. 3. In the Host Server / URL field, enter the remote B2B Server connection URL. For example, www.RemoteServer:port. 4. Check the Set as Default Remote Server? box if the B2B Server is the default outbound communication method. 5. Click Submit to save the changes. Click on mroBuyer Home to return to the configuration home page.

Service Administration
The Service Administration option is used to configure the Remote Server's incoming service.

58

Installation Guide

Figure 18 Service Administration

1. Click Service Administration to display the Service Administration page. NOTE: If you are adding a service, Figure 19 is displayed. If you are modifying an existing service, Figure 20 is displayed.

59

Release 4.1.1

Figure 19 Add New Service

Figure 20 Modify Service 'RemoteService'

60

Installation Guide

2. In the Service Name field, enter the name of a new service or accept the default. 3. In the Connection field, choose the connection type to use. The Connection type is defined through the Outbound Connection Administration option. The default for webMethods B2B communication is RemoteB2B. NOTE: The Interface and Service fields must be acquired from the RemoteB2B server's administrator. These values can only be completed by calling the MRO Software Communications Department as described in the worksheet at the beginning of this manual. The telephone number is

(519) 642-6055.
4. In the Interface field, enter the Remote B2B Server's incoming interface name. 5. In the Service field, enter the Remote B2B Server' s incoming service name. 6. In the Remote FTP Server (For document attachments) field, enter the URL of the destination webMethods service that receives the attached documents (e.g., PO attachments). If this URL is entered and document attachments exist, they will be transferred to the address indicated. If this field is left blank, no documents will be transferred. 7. Check the Set as Default Service? Box if the current service should be set as the default. 8. The DataKey field contains the keyname in which XML data is sent. If you are adding a new service, you should enter mrodata in this field. If you are modifying an existing service, the default is mrodate. This value should not be changed. 9. In the reply_route field, enter or modify the existing URL address displayed to point to your local B2B server's incoming transaction's interface and service. The default is your local B2B server.
61

Release 4.1.1

Transaction Administration
The Transaction Administration option is used to define which outgoing service to use for each outgoing XML transaction. By this method, different XML transactions can be sent to different remote servers. 1. Click Transaction Administration to display the Transaction Administration page.

Figure 21 Transaction Administration

2. To modify a transaction choose one from the screen displayed.

62

Installation Guide

Figure 22 Modify Transaction

NOTE: The fields that display on the Modify Transaction page (Figure 22) should not be changed. Accept the defaults values that are displayed. 3. In the Service field, choose the Service Name to use for communicating with the remote B2B server. This service was defined through the Service Name field in the Service Administration option.

Duplicating mroBuyer Package

This option is used for handling different transactions going to a different Application Server. 1. Click Duplicate mroBuyer Package. The Duplicate mroBuyer Package screen is displayed.

63

Release 4.1.1

Figure 23 Duplicate mroBuyer Package

2. Enter a new package name in the New Package Name field. For example, mroBuyer2. 3. Click Submit to save the changes. You should see the following message at the top of the screen. A duplicate copy of the mroBuyer named mroBuyer2 has been produced. Please restart the B2B Server and modify the new packages configuration through its administration page. 4. Restart the B2B Server.

Customization Handler
This option is used for handling different customizations.
64

Installation Guide

1. Click Customization Handler to display the Customization Handler Administration page.

Figure 24 Customization Handler Administration

2. Modify and compile a java class to customize an inbound or outbound transaction. Java class files and java source files are contained in the mroBuyer\code\classes\custom folder of the respective package. These files should be modified and compiled in the same folder.

65

Release 4.1.1

RELOADING MROBUYER PACKAGE

Return to the B2B home page. Select Packages to display the Packages screen.

Figure 25 Packages Screen

Check if the Loaded and Enabled buttons for mroBuyer package are green in color. If the color is yellow, it indicates that some pieces of the software are enabled and others are not. If the color is red, it indicates that either none of the services are loaded or the package is not enabled. Try enabling the package by clicking the Enabled button. To view reasons for the package not being properly installed, click on the Loaded button for the package to display error messages.

66

Installation Guide

SEARCH ENGINE INTEGRATION

The Verity Search Engine is a product from Verity, Inc. used for performing fast text based searches against vast amount of data. The Verity Search Engine product is independent of any database and maintains data that needs to be searched in Collections (the concept of a Collection is similar to a database). If there are any updates to the database, the Collection needs to be updated immediately to reflect the changes. Verity Search Engine has been very tightly integrated with the Application Server to search against a vast spectrum of inventory items. The integration process takes care of automatically updating the MAXIMO database information into the Verity Collections whenever any modification is made to the MAXIMO database. This results in the Verity Collections always being up to date. Application Server uses two Verity Collections to facilitate your search criteria:

Item Collection - used to search for items and to display the items found. Category Collection - used to search for items and to display a list of categories in which the items are found.

In the Verity Collections, each record is treated like a document. So most of the time, either new documents are being inserted, modified and/or deleted from the Collections. The Verity Search Engine product provides a program, k2server, to facilitate client programs to access information from the Collections. The Application Server makes use of this program to search against the Collections.

67

Release 4.1.1

VERITY CONFIGURATION
Once you have installed MAXIMO Release 4.1.1, a VERITY folder is automatically created under the MXSERVER folder along with other sub folders, namely, Collections, defaultstyles, and K2220. To start using the Verity Search Engine, you need to perform the following steps: 1. Build Collections 2. Run Verity as a Windows NT service. 3. Update the Collections.

Building Collections
Building a collection means copying all the data from the database into the Verity Collections. Whenever a collection needs to be created, Verity requires a set of style files to dictate the rules associated with the Collection. The default style files used for the Item and Category Collections are itemstyles (for item styles) and catstyles (for category styles) respectively and are kept under the <MXSERVER ROOT>\VERITY\DEFAULTSTYLES folder. We recommend that you do not make any modifications to the catstyle file as in most cases, it doesnt need any modifications. You may however modify the itemstyle file to include specific item fields that you would like to use for the search. For details on adding new styles, refer to the section titled Adding new fields to the Item Collection file. To build the Verity Collections, perform the following steps from the Command Prompt in the <MXSERVER ROOT> folder:

Run the BULKLOADITEMS.BAT file to build the item collection with data from the database.

68

Installation Guide

Run the BULKLOADCATEGORIES.BAT file to build the category collection with data from the database.

These two batch files reside in the <MXSERVER ROOT> folder and create the collections under <MXSERVER ROOT>\VERITY\COLLECTIONS folder, by default. If you want to create the Collections in a folder other than the default, then appropriate arguments should be passed to the batch files. Open the batch files using Notepad and take a look at the usage. Once you build the Collections, in order to access the Collections, you will need to stop the searchserverservice and restart it. This will apply only if Create Service was selected from the installation.

Adding new fields to the Item Collection

A GENERATEITEMSTYLES.BAT file is provided to add new fields to the item style file. Go to the Command Prompt in the <MXSERVER ROOT> folder and run the GENERATEITEMSTYLE.BAT file and pass the following three arguments: 1. Specify the path where the common item style files are present. The folder is PSDI/SEARCH/COMMON and the common item style files are the itemstyle (the item style files) and the catstyle (the category style files). 2. Specify the destination folder name where you want the new style files to be stored. 3. Specify the name of the properties file (in this case MXSERVER.PROPERTIES). The MXSERVER.PROPERTIES file contains information about the fields that you want in the Verity Collections. The property which needs to be modified is mxe.verity.bulkload.field1, followed by the values for the item name and the column name from the ITEM table in the database. You can keep adding new fields but all of them need to be in continuous incremental order. For example, mxe.verity.bulkload.field1, mxe.verity.bulkload.field2, etc. Once you have
69

Release 4.1.1

added the new item styles, mention the total number of new styles you created by entering the count in the property mxe.verity.bulkload.totalfieldcount=1. By default, it is 1. For example, if you have added 5 new item styles, the property should read mxe.verity.bulkload.totalfieldcount=5.

Running Verity as a Windows NT Service

To set up Verity as a Windows NT Service, from the Command Prompt in <MXSERVER ROOT> folder run searchserverservice -install. To start the service, go to the Control Panel, click on Services, select the Verity Service and click on Start. To start Verity without running it as a Windows NT service, go to the Command Prompt and run the K2SERVER.BAT file from the <MXSERVER ROOT> folder. The K2SERVER.BAT file takes information from the <MXSERVER ROOT>\K2SERVER.INI file. The K2SERVER.INI file provides the K2Server information about what collections need to be searched by the client programs. NOTE: Your screen will show the words "Pinging localhost:9900->Dead." This is not an error message, it indicates that the Verity server is running.

Updating the Collections

Once the Verity Collections are built, the Application Server maintains the Collections through a scheduled task. The scheduled task program keeps the Verity Collections up to date with the data present in the database. The following property in the MXSERVER.PROPERTIES file specifies the time interval at which the scheduled task should run. mxe.cronTask.psdi.server.VerityCollSubmitCronTask=10m

70

Installation Guide

For example, the above property indicates that the scheduled task should run every 10 minutes. You can specify any time interval at which you want the scheduled task to run. Whenever the Application Server is started, the Application Server program looks for this property in the property file and starts the appropriate scheduled task program. The scheduled program, checks for any updates done to the item table and appropriately changes the Verity Collections data. Whenever changes are made to the item table, the database triggers update the VERITYACTION table with the appropriate information. The scheduled task program reads information from the VERITYACTION table and appropriately updates the Verity Collections.

71

Release 4.1.1

MANAGING THE APPLICATION SERVER

The Application Server starts automatically if you install it as a Windows NT service. To stop the server, use the Windows NT Service Manager in the Control Panel. The Application Server automatically shuts down when Windows NT shuts down if it was installed as a service. You can also start the Application Server from the Program Menu item in the MAXIMO Applications program group. If you installed the Application Server as a service of Windows NT, you must first stop the service from the Windows NT Service Manager. A console is displayed when you start the Application Server from the Program Menu. Output messages from the Application Server are displayed to the console as shown below:

Figure 26 Output Messages from Application Server

The server is loaded and ready to be accessed by clients once the MXServer ready for client connections message is displayed. To stop the Application Server, close the console by pressing [Ctrl+C] and answer Yes to the prompt that is displayed.
72

Installation Guide

Application Server Configuration File MXSERVER.PROPERTIES

The MXSERVER.PROPERTIES file is a configuration file the Application Server accesses when it starts. You selected the folder location for this file during installation. The file contains property values, many of which you set during installation. The tables below list those properties from the file that you may want to edit, and describe their functions. To view the entire file with all the properties and their descriptions, or to change property settings in the file, you can use Notepad or another text editor to open MXSERVER.PROPERTIES. See important security information for this file on page 80. NOTE: Property names and the values are case sensitive.

General Server Properties

Property Name mxe.name mxe.rmi.port Description Name of the Application Server. Port used by RMI for communication, if left at 0 (the default), RMI will use any available port on the system. To use a specific port, set this parameter to an available port number. Verbosity of the diagnostic messages the server writes to the console. 1=low, 5=medium, 9=high mxe.msgLogFile File name to which messages are written. New messages are appended to the file. To write to the console, specify stdOut; to write to a file, specify a file name.

mxe.verbosity

73

Release 4.1.1

Property Name mxe.errLogFile

Description File name to which error messages are written. New messages are appended to the file. To write to the console, specify stdErr; to write to a file, specify a file name. Flag to indicate whether to start Tomcat JSP Server or not. Valid values are true or false. This is the owner of the database schema. For Oracle: mxe.db.driver=oracle.jdbc.driver.OracleDriver For Oracle: jdbc:oracle:thin:@host_name:port:sid Number of database connections that need to be kept open as soon as the Application Server is started. The default value is 15. Maximum number of free database connections available in the connection pool. The default value is 30. Minimum number of free database connections available in the connection pool for more connections to be allocated. The default value is 10. Number of new connections to be created when the minimum free connections are available in the connection pool. The default value is 5. Logs the SQL statements that take longer than the specified time limit. The time is in milliseconds. The default is 1000 milliseconds.

mxe.startJSPServer mxe.db.schemaowner mxe.db.driver mxe.db.url mxe.db.initialConnections

mxe.db.maxFreeConnections

mxe.db.minFreeConnections

mxe.db.newConnectionCount

mxe.db.logSQLTimeLimit

74

Installation Guide

Property Name mxe.db.user

Description Database user the server uses to attach to the database server. This user must be the schema owner. Password for the database user name. Name of the host that is running the SMTP server. This is needed for facilities that make use of e-mail such as Workflow notifications and any error message notifications. Your network administrator can provide this address. System date format. For Oracle: mxe.db.systemdateformat=sysdate

mxe.db.password mail.smtp.host

mxe.db.systemdateformat

Workflow Properties
Property Name mxe.workflow.admin mxe.cronTask.psdi.workflow.Em ailNotification mxe.cronTask.psdi.workflow.Esc alation mxe.cronTask.psdi.workflow.Wai tForMaterial Description E-mail account of the Workflow administrator. Whether the e-mail notification facility is enabled, and how often it is executed. Default value is 10m (10 minutes). Whether the escalation facility is enabled, and how often it is executed. Default value is 10m (10 minutes). When this facility is enabled, work orders waiting for materials will be moved to the next node when all materials are received. Default value is 5m (5 minutes).

75

Release 4.1.1

Property Name mxe.crontask.psdi.workflow.Auto accept

Description When this facility is enabled, accept actions found on assignments are automatically processed. In some cases, user AUTOACPT and labor code AUTOACPT may both need to be created.

Properties for mroHosting Center Integration

Property Name mxe.cronTask.psdi.mnet.Process POCron mxe.ecom.customerid.<package name> Description How often the database is to be polled for POs to be sent to their destination. The default is 60s, every 60 seconds. Customer company ID for e-commerce integration, used in process PO and other e-commerce transactions. <package name> is the name of the package on the webMethods B2B server used for e-commerce integration (e.g., mroBuyer for connecting to mroHosting center). There must be only one entry for each e-commerce integration package (e.g., mxe.ecom.customerid. mroBuyer). mxe.mro.txn.timeout The time out value for product search transaction; the default is 30 seconds.

76

Installation Guide

Properties for B2B Server

Property Name mxe.b2b.hostUrl mxe.b2b.username mxe.b2b.password mxe.b2b.interface mxe.b2b.service mxe.b2b.reply.service mxe.b2b.admin.email mxe.b2b.Ariba.interface mxe.catalog.ID Description The B2B server host name or TCP/IP address and port. The B2B connection username. The B2B server connection password. The interface name that provides the service. The service name that provides the outgoing communication. The reply service name to receive txn messages. The email address of the administrator Ariba integration package. This information is required for communication with Ariba. The property name that identifies each individual catalog provider (see page 80 for more information).

Properties for Verity Search

Property Name mxe.cronTask.psdi.server.Verity CollSubmitCronTask mxe.verity.collection.itemcollect ion Description Specifies the time interval for the Verity Collection Submit cronTask to run. The default is 10 minutes. Used by the Verity Collection Submit cronTask to update the item collection with the modified data from the database.

77

Release 4.1.1

Property Name mxe.verity.collection.categoryco llection mxe.verity.bulkload.totalfieldco unt

Description Used by the Verity Collection Submit cronTask to update the category collection with the modified data from the database. Specifies, for every field that should be included in the collection, the verity field name followed by a comma and by the database column name of the item table. n (the default) specifies the total number of user defined fields to be included in the Collections. mxe.verity.bulkload.field x=<verity field name>, <item column name>,where x is the index starting from 1 <verity field name> is the name of the field that refers to the Item column name in the Verity Collection <item column name> is the name of the column from the ITEM table. Some examples are: mxe.verity.bulkload.field1=ITEM_MSDSNUM, msdsnum, mxe.verity.bulkload.field1=ITEM_IN1, in1, mxe.verity.bulkload.field1=ITEM_IN1, in2

mxe.verity.bulkload.longdescript ion mxe.verity.server

Indicates whether item descriptions long description needs to be included in the collection or not. The default is true. Specifies the name of the machine on which the k2Server is running. The default value is localhost.

78

Installation Guide

Property Name mxe.verity.port

Description Specifies the port number of the machine on which the k2Server is running. The default port number is 9901. Specifies the maximum number of rows that the search result should return. The default is 200. The item collection alias specified in the k2server.ini file Where n is the index starting from 0 up to the total number of fields and <verity field name> is the field name in Verity that should be included in the Search result. Some examples: mxe.verity.collection.itemcollection.resultset.attribu te.0=ITEM_ID, mxe.verity.collection.itemcollection.resultset.attribu te.0=ITEM_DESCRIPTION

mxe.verity.maxrows mxe.verity.collection.itemcollect ion.eng mxe.verity.collection.itemcollect ion.resultset.attribute.n=<verity field name>

mxe.verity.collection.categoryco llection.eng

The category collection alias specified in the k2server.ini file

Catalog Properties for the webMethods B2B Server

The MXSERVER.PROPERTIES file contains a list of different vendor catalogs that the Application Server requires for direct catalog display. Each of these entries has a catalog provider name, a catalog provider company code, and a local B2B Server URL to receive reply from the remote B2B Server.

79

Release 4.1.1

Following is a catalog entry from the MXSERVER.PROPERTIES file: mxe.Catalog.ID=CATALOG_NAME, CUSTOMER_COMPANY_CODE, VENDOR_COMPANY_CODE,CUSTOMER_REPLY_URL mxe.Catalog.ID refers to the property name to identify each individual catalog provider. The ID should start from the number 1 and be in continuous incremental order. For example, mxe.catalog.1, mxe.catalog.2, etc. CATALOG_NAME refers to a user-defined vendor entered for self-service applications. In self-service requisitions this value is displayed in the catalog selection drop-down box. CUSTOMER_COMPANY_CODE refers to the customer company code (buying company). This information must be entered in the database from the Companies application in MAXIMO Release 4.1.1. VENDOR_COMPANY_CODE refers to the vendor company code. This information must be entered in the database from the Companies application in MAXIMO Release 4.1.1. CUSTOMER_REPLY_URL this parameter is currently not used.

Setting File Security for MXSERVER.PROPERTIES

The MXSERVER.PROPERTIES file contains non-encrypted system passwords. You must prevent users who are not system administrators from accessing this file by setting its Access Type to NO ACCESS. In Windows NT Explorer, select the MXSERVER.PROPERTIES file. Right-click on the file to select the Properties. In the Properties dialog box, select the Security tab, and click the Permissions button. In the Access Type box, select NO ACCESS. All other files in the MXSERVER folder should be set to Read access for all users who are not system administrators.

80

Installation Guide

FINAL SYSTEM SETUP CHECKS Configuring Tomcat to Run With Internet Information Server (IIS)
The current version of Tomcat JSP Server used by MAXIMO can operate in conjunction with Microsoft's Internet Information Server (IIS). This setup is recommended if more than 40 users will be concurrently running self-service applications or if additional security is desired. The procedure for doing this is described in the MAXIMO System Administrators Guide.

Establishing a Base Currency

Before you can use most of the MAXIMO end-user applications (those that contain the Currency field), you must establish a base currency, or, if you want, two base currencies (e.g., the French franc and the Euro). The Currency field is a required field in all applications it appears in, so must be filled with a currency code. If you use the empty MAXIMO database or a copy, currency codes will only be available to your MAXIMO applications after you create a code or codes. You should first create the currency record or records in the Currency Management application, then establish one of these as base one currency code via the Currency Options choice on the Actions menu in Application Setup. The procedure for doing this, and for creating multiple base currencies, is described in Chapter 6, Application Setup, in the MAXIMO System Administrators Guide.

81

Release 4.1.1

Accessing Self-Service Applications

To run the Self-Service Applications described in this guide, from your browser (Internet Explorer 5.0, 5.5 or Netscape Communicator 4.7x), enter the name of the Application Server as the URL. For example: http://appsrvr http://appsrvr:port (where appsrvr is the name of the server running the Application Server) (where appsrvr is the name of the server running the Application Server and port is the number of the port substituted for default port 80. The procedure for changing the default port number is described in the MAXIMO System Administrators Guide.)

Editing System Files

The installation procedure automatically edits your system files to allow MAXIMO application files to use them; however, you should check to make sure they are correct after installation. To do that you can manually edit the files. You also need to install the system files on any additional workstations that will be running MAXIMO.

SQL.INI
NOTE: The system file examples assume that drive C is your local drive. Substitute your actual network drive letter(s) for C if you have installed the software on other drives. The SQL.INI file is provided as part of the installation package. This file is located in the MAX411 folder by default. It serves three primary purposes:

Establishes a client/server configuration. Specifies client/server communications.

82

Installation Guide

Provides performance-tuning parameters for the database server and client applications.

The SQL.INI file for the Oracle database platform should contain the following sections: WIN32CLIENT.DLL, WIN32CLIENT.ORA32, ORAGTWY During the installation, the SQL.INI file is edited to fit appropriate parameters. Only one SQL.INI should be located in the search paths, and it should be in the MAX411 folder.

The [WIN32CLIENT.DLL] section specifies the SQLRouter (sqlora32.dll) for Oracle connectivity. The sqlora32 DLL is the only DLL required for Oracle routing. All other network communication is performed by Oracle and the underlying transport. An example from the SQL.INI file is: [WIN32CLIENT.DLL] comdll=sqlora32

The [WIN32CLIENT.ORA32] section allows you to generate an SQL log file that can assist in troubleshooting errors. [WIN32CLIENT.ORA32] log=c:\temp\max.log

The [ORAGTWY] section provides the database name for the server connection. The REMOTEDBNAME line associates the database name with the Oracle connect string. It contains the database alias name and the Oracle connection string. A line is automatically inserted from the installation. You can add any number of REMOTEDBNAME lines to your SQL.INI file. Please refer to Oracle documentation for more information on specifying the connection string. An example from the SQL.INI file is: [ORAGTWY]
83

Release 4.1.1

LONGBUFFER=900000 SUBSTITUTE=SYSSQL., FETCHROWS=20 REMOTEDBNAME=maxtest,@oratest REMOTEDBNAME=maxprod,@oraprod MAPERROR=OFF

MAXIMO.INI Application Server settings (only if you purchased Workflow)

NOTE: The system file examples assume that drive C is your local drive. Substitute your actual network drive letter(s) for C if you have installed the software on other drives. In order for clients to connect to the Application Server for Workflow, the correct URL or drive mapping, as well as the correct Application Server definition for your database, must be specified in your MAXIMO.INI file. Because you installed MAXIMO application files before you installed the Application Server, you might not have been able to specify the correct URL or drive mapping of the Application Server when prompted for it during MAXIMO installation. In the MAXIMO.INI file located in the MAX411 folder, check the [java] section and verify that the correct URL or the correct path to the folder containing the Application Server files is specified. If your path to the Application Server is via HTTP, in the javaparameters= line, make sure that codebase= is set to the actual URL of the server; keep the trailing slash (/) at the end of the URL.

Example

[java] javaparameters= Djava.rmi.server.codebase="http://appsrvr/ http://appsrvr/lib/jndi.jar" Djava.security.policy=maxlib.policy cp . where http://appsrvr/ is the URL of your Application Server, and appsrvr is the name of the server running the Application Server.

84

Installation Guide

If your path to the Application Server is via mapped drive, in the javaparameters= line, make sure that the correct drive letter and path are specified after -cp .;.

Example

[java] javaparameters=cp .;x:\appserver;x:\appserver\lib\jndi.jar<<??>> where x:\appsrvr is the drive and path of your Application Server.

In the [AppServer] section, check that the database alias and Application Server specification are correct: <database alias>=<appserver>/MXServer.
Example [AppServer] MAXIMO=appsrvr/MXServer where MAXIMO is the database alias, and appsrvr is the name of the server running the Application Server.

MAXIMO.INI Report Settings

In the MAXIMO.INI file located in the MAX411 folder, check the [report] section and verify that the following lines have been entered. (Comments are set to the right in italics.) [report] REPORT_TYPE=SQRW (for Brio.Reports) SQR4_ORACLE_TNS:{Database Alias}={Oracle TNS} SQRW_PATH:ORACLE=C:\SQR6 SQRW_REPPATH:ORACLE=C:\SQR6\Reports SQRW_SPOOL=C:\SPL You need to edit the SQR4_ORACLE_TNS line to read: SQR4_ORACLE_TNS:MAXPROD=ORAPROD where MAXPROD is the database alias for your database, and ORAPROD is the SQL and net connect string.
85

Release 4.1.1

SQR.INI Settings
NOTE: The system file examples assume that drive C is your local drive. Substitute your actual network drive letter(s) for C if you have installed the software on other drives. In the SQR.INI located in the Windows or WINNT folder, check and verify that the correct entries have been made. (Comments are set to the right in italics.) [Default-Settings] Locale=SYSTEM Default-Numeric=V30 [Environment:Common] SQRDIR=C:\SQR6 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL (specifies the folder location) (required parameters)

[Environment:Oracle] SQRDIR=C:\SQR6 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD-MON-YYYY

SQR.INI Settings - English (UK version)

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD-MON-YYYY [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD-MON-YYYY
86

Installation Guide

SQR.INI Settings - Dutch

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD/MM/YYYY [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD/MM/YYYY

SQR.INI Settings - French

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=YYYY-MM-DD [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=YYYY-MM-DD

SQR.INI Settings - German

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD.MM.YYYY

87

Release 4.1.1

[Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD.MM.YYYY

SQR.INI Settings - Japanese

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=YYYY/MM/DD [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=YYYY/MM/DD

SQR.INI Settings - Portuguese

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD/MM/YYYY [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD/MM/YYYY

88

Installation Guide

SQR.INI Settings - Spanish

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD/MM/YYYY [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=DD/MM/YYYY

SQR.INI Settings - Swedish

[Environment:Common] SQRDIR=C:\SQR5 (specifies the folder location) SQRFLAGS=-KEEP -XCB (required parameters) SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=YYYY-MM-DD [Environment:Oracle] SQRDIR=C:\SQR5 SQRFLAGS=-KEEP -XCB SQRW_SPOOL=C:\SPL SQR_DB_DATE_FORMAT=YYYY-MM-DD The SQR.INI file is installed to the Windows or WINNT folder when you install Release 4.1.1. This file will also be edited upon installing Brio.Reports. Although SQR.INI is rather long, there are only a few sections to which attention should be paid. The main concern in this file is the SQRDIR setting, which is found in two locations. It appears first in the [Environment:Common] section; it also appears in the [Environment:Oracle] section. SQRDIR should be set to the folder in which Brio.Reports are found.
89

Release 4.1.1

An SQRFLAGS setting appears in the same two sections that SQRDIR does. This setting is required for MAXIMO Release 4.1.1 to run Brio.Reports. The command line flags found in SQRFlags function as follows: -KEEP: Forces Brio.Reports to save a copy of the report in SPF format, which allows it to be viewed using Brio.Reports (Preview Report in MAXIMO). -XCB: Prevents the large communication screen from being displayed. [Processing-Limits] ; QUERIES=60 ; QUERYARGS=240 ; VARIABLES=750 ; PROGLINES=2500 ; PROGLINEPARS=9000 ; STRINGSPACE=10000 ; POSITIONS=900 ; SQLSIZE=4000 SUBVARS=500 DYNAMICARGS=500 ; FORWARDREFS=200 ; EXPRESSIONSPACE=8192 ; BREAKS=100 ; WHENS=70 ; ONBREAKS=30 ; LONGSPACE=32766

[locale:MAXIMO] U.S. English

NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=$ MONEY-SIGN-LOCATION=Left THOUSAND-SEPARATOR=,

90

Installation Guide

DECIMAL-SEPARATOR=. EDIT-OPTION-NA=n/a DATE-EDIT-MASK=DD-MON-YYYY INPUT-DATE-EDIT-MASK=DD-MON-YYYY DATE-SEPARATOR=/ TIME-SEPARATOR=: EDIT-OPTION-AM=am EDIT-OPTION-PM=pm EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=Edit DAY-OF-WEEKFULL=('Sunday','Monday','Tuesday','Wednesday','Thursday','Friday','Saturday') DAY-OF-WEEK-SHORT=('Sun','Mon','Tue','Wed','Thu','Fri','Sat') MONTHS-CASE=Edit MONTHSFULL=('January','February','March','April','May','June','July','August','September' ,'October','November','December') MONTHSSHORT=('Jan','Feb','Mar','Apr','May','Jun','Jul','Aug','Sep','Oct','Nov','Dec')

[locale:MAXIMO] - Dutch
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=F MONEY-SIGN-LOCATION=Right THOUSAND-SEPARATOR=. DECIMAL-SEPARATOR=, EDIT-OPTION-NA=n/a DATE-EDIT-MASK=dd-mm-yyyy INPUT-DATE-EDIT-MASK=dd-mm-yyyy DATE-SEPARATOR=TIME-SEPARATOR=: EDIT-OPTION-AM=am
91

Release 4.1.1

EDIT-OPTION-PM=pm EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=NO-CHANGE DAY-OF-WEEKFULL=('Sonntag','Montag','Dienstag','Mittwoch','Donnerstag','Freitag','Samstag') DAY-OF-WEEK-SHORT=('Son','Mon','Die','Mit','Don','Fre','Sam') MONTHS-CASE=NO-CHANGE MONTHSFULL=('Januar','Februar','Mrz','April','Mai','Juni','Juli','August','September','Okt ober','November','Dezember') MONTHSSHORT=('Jan','Feb','Mr','Apr','Mai','Jun','Jul','Aug','Sept','Okt','Nov','Dez')

[locale:MAXIMO] French
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=F MONEY-SIGN-LOCATION=Right THOUSAND-SEPARATOR=. DECIMAL-SEPARATOR=, EDIT-OPTION-NA=n/a DATE-EDIT-MASK=yyyy-mm-dd INPUT-DATE-EDIT-MASK=yyyy-mm-dd DATE-SEPARATOR=TIME-SEPARATOR=: EDIT-OPTION-AM=am EDIT-OPTION-PM=pm EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=NO-CHANGE DAY-OF-WEEKFULL=('dimanche','lundi','mardi','mercredi','juedi','vendredi','samedi') DAY-OF-WEEK-SHORT=('dim','lun','mar','mer','jeu','ven','sam')
92

Installation Guide

MONTHS-CASE=NO-CHANGE MONTHSFULL=('janvier','fvrier','mars','avril','mai','juin','juillet','aot','septembre','octobre' ,'novembre','dcembre') MONTHS-SHORT=('jan','fv','mar','avr','mai','jun','jui','ao','sep','oct','nov','dc')

[locale:MAXIMO] German
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=DM MONEY-SIGN-LOCATION=Right THOUSAND-SEPARATOR=. DECIMAL-SEPARATOR=, EDIT-OPTION-NA=n/a DATE-EDIT-MASK=dd-mm-yyyy INPUT-DATE-EDIT-MASK=dd-mm-yyyy DATE-SEPARATOR=. TIME-SEPARATOR=. EDIT-OPTION-AM=am EDIT-OPTION-PM=pm EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=NO-CHANGE DAY-OF-WEEKFULL=('Sonntag','Montag','Dienstag','Mittwoch','Donnerstag','Freitag','Samstag') DAY-OF-WEEK-SHORT=('Son','Mon','Die','Mit','Don','Fre','Sam') MONTHS-CASE=NO-CHANGE MONTHSFULL=('Januar','Februar','Mrz','April','Mai','Juni','Juli','August','September','Okt ober','November','Dezember') MONTHSSHORT=('Jan','Feb','Mr','Apr','Mai','Jun','Jul','Aug','Sept','Okt','Nov','Dez')

93

Release 4.1.1

[locale:MAXIMO] - Japanese
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=\ MONEY-SIGN-LOCATION=Left THOUSAND-SEPARATOR=, DECIMAL-SEPARATOR=. EDIT-OPTION-NA=n/a DATE-EDIT-MASK=YYYY/MM/DD INPUT-DATE-EDIT-MASK=YYYY/MM/DD DATE-SEPARATOR=/ TIME-SEPARATOR=: EDIT-OPTION-AM=AM EDIT-OPTION-PM=PM EDIT-OPTION-BC=BC EDIT-OPTION-AD=AD DAY-OF-WEEK-CASE=Edit DAY-OF-WEEKFULL=('Sunday','Monday','Tuesday','Wednesday','Thursday','Friday','Saturday') DAY-OF-WEEK-SHORT==('Sun','Mon','Tue','Wed','Thu','Fri','Sat') MONTHS-CASE=Edit MONTHSFULL=('January','February','March','April','May','June','July','August','September' ,'October','November','December') MONTHSSHORT==('Jan','Feb','Mar','Apr','May','Jun','Jul','Aug','Sep','Oct','Nov','Dec')

[locale:MAXIMO] - Portuguese
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=R$ MONEY-SIGN-LOCATION=Left THOUSAND-SEPARATOR=.
94

Installation Guide

DECIMAL-SEPARATOR=, EDIT-OPTION-NA=n/a DATE-EDIT-MASK=DD/MM/YYYY INPUT-DATE-EDIT-MASK=DD/MM/YYYY DATE-SEPARATOR=/ TIME-SEPARATOR=: EDIT-OPTION-AM=am EDIT-OPTION-PM=pm EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=Edit DAY-OF-WEEK-FULL=('domingo','segunda-feira','tera-feira','quartafeira','quinta-feira','sexta-feira','sbado') DAY-OF-WEEK-SHORT=('dom','seg','ter','qua','qui','sex','sb') MONTHS-CASE=Edit MONTHSFULL=('janeiro','fevereiro','maro','abril','maio','junho','julho','agosto','setembro',' outubro','novembro','dezembro') MONTHS-SHORT=('jan','fev','mar','abr','mai','jun','jul','ago','set','out','nov','dez')

[locale:MAXIMO] Spanish
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=$$9,999,999.99 MONEY-SIGN=$ MONEY-SIGN-LOCATION=Left THOUSAND-SEPARATOR=, DECIMAL-SEPARATOR=. EDIT-OPTION-NA=n/a DATE-EDIT-MASK=DD-MM-YYYY INPUT-DATE-EDIT-MASK=DD-MM-YYYY DATE-SEPARATOR=/ TIME-SEPARATOR=: EDIT-OPTION-AM=am EDIT-OPTION-PM=pm
95

Release 4.1.1

EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=Edit DAY-OF-WEEKFULL=('Domingo','Lunes','Martes','Mircoles','Jueves','Viernes','Sbado') DAY-OF-WEEK-SHORT=('Dom','Lun','Mar','Mi','Jue','Vie','Sb') MONTHS-CASE=Edit MONTHSFULL=('Enero','Febrero','Marzo','Abril','Mayo','Junio','Julio','Agosto','Septiembre ','Octubre','Noviembre','Diciembre') MONTHSSHORT=('Ene','Feb','Mar','Abr','May','Jun','Jul','Ago','Sep','Oct','Nov','Dic')

[locale:MAXIMO] - Swedish
NUMBER-EDIT-MASK=999,999,999.99 MONEY-EDIT-MASK=9,999,999.99$$ MONEY-SIGN=SEK MONEY-SIGN-LOCATION=Right THOUSAND-SEPARATOR=. DECIMAL-SEPARATOR=, EDIT-OPTION-NA=n/a DATE-EDIT-MASK=YYYY/MM/DD INPUT-DATE-EDIT-MASK=YYYY/MM/DD DATE-SEPARATOR=TIME-SEPARATOR=: EDIT-OPTION-AM=am EDIT-OPTION-PM=pm EDIT-OPTION-BC=bc EDIT-OPTION-AD=ad DAY-OF-WEEK-CASE=NO-CHANGE DAY-OF-WEEKFULL=('sndag','mndag','tisdag','onsdag','torsdag','fredag','lrdag') DAY-OF-WEEK-SHORT=('sn','mn','tis','ons','tor','fre','lr') MONTHS-CASE=NO-CHANGE
96

Installation Guide

MONTHSFULL=('januari','februari','mars','april','maj','juni','juli','augusti','september','oktob er','november','december') MONTHS-SHORT=('jan','feb','mar','apr','maj','jun','jul','agu','sep','okt','nov','dec') The SQR.INI contains many other sections. Consult your SQR manual for more details.

97

Release 4.1.1

98

Installation Guide

Appendix A: Sample Database Configurations

The following is a sample configuration for a MAXIMO test database (on Unix) that includes six tablespaces. The MAXIMO tablespace holds data and indexes. The control files are placed on separate disk drives. The log files are on separate disk drives from the data. Two tablespaces are created to hold rollback segments. A large rollback segment is recommended for bulk loads and a number of smaller rollback segments are recommended for query/update purposes. A temporary tablespace is created to hold intermediate results of sorts and other database operations. The sizes of the MAXIMO tablespaces depend on the amount of data you expect to store. A tablespace consists of one or more data files. We recommend you allocate a tablespace that is large enough to hold all of the data. If the tablespace is not large enough to hold the data as the data grows, you can alter the tablespace and add new data files, or you can implement the AUTOEXTEND option of Oracle 7.3 or higher to permit the datafile to grow. Indexes are also stored in tablespaces. They may be stored in the MAXIMO tablespace or in a different tablespace (for example, a tablespace named INDEXES). Splitting data and indexes across physical disk drives is a recommended technique to improve performance. The trade-off is that more tablespaces require more database administration. If you are just starting out with Oracle, you can start with one tablespace and monitor the performance. You can always reorganize the database at a later point. system rbs rbsbig temp maxprod_data maxprod_index /u01/oracle/testdbs/systmax.dbf /u01/oracle/testdbs/rbsmax.dbf /u01/oracle/testdbs/rbsbigmax.dbf /u01/oracle/testdbs/tempmax.dbf /u03/oracle/testdbs/maxprod_data01.dbf /u04/oracle/testdbs/maxprod_index01.dbf 20MB 30MB 30MB 20MB 300MB 200MB
99

Release 4.1.1

logfiles

/u02/oracle/testdbs/log1max.dbf /u02/oracle/testdbs/log2max.dbf /u02/oracle/testdbs/log3max.dbf /u01/oracle/testdbs/ctrl1max.ctl /u02/oracle/testdbs/ctrl2max.ctl /u03/oracle/testdbs/ctrl3max.ctl

2MB 2MB 2MB

control_files

100

Installation Guide

Appendix B: Identifying the Schema at Login

There are three ways to identify the schema at login time. These methods are described below.

Identifying the Schema via the MAXIMO.INI File

By default, the MAXIMO schema owner is MAXIMO. To change this, add a line to the MAXIMO.INI file (in the MAX411 folder), under the [SYSTEM] paragraph, as shown below: [SYSTEM] schema=schemaowner

Note for Sites with Self-Service Applications

If you change the default schema owner of MAXIMO to another user name, you must also change the following files to reflect the new schemaowner username and password:

The user name and password in the LOGINHEADER.JSP file. This file is located in the JSP\APP\USERREG subfolder of the MXSERVER folder. In the following example, username and password have each replaced maximo: Authenticator.setUserName("username"); Authenticator.setPassword("password");

The mxe.db.user and mxe.db.password properties in the MXSERVER.PROPERTIES file.

101

Release 4.1.1

Displaying the Schema Field on the Login Screen

Make the Schema field visible to the user on the Database Login dialog box. This can be done using the Centura Object Nationalizer. (The Object Nationalizer is used for modifying non-Java screens and dialog boxes.) Follow the steps below to modify the two login screens so that a Schema field appears at the bottom. The field will be filled in with the value of the Schema parameter, if any, in the MAXIMO.INI file, and can then be changed by the user. 1. From Windows Explorer, go to the MAX411 folder and double-click on CNI15.EXE. 2. Click File/Open, and select MAXLOGIN.EXE. 3. From MAXLOGIN.EXE, select the following subfolders: Maxlogin, Windows, dlgLogin, then Child Windows. 4. Right-click on A Schema and click Properties. 5. Place the cursor on Visible and click Yes. 6. Right-click on ctlSchema, then select Properties. Place the cursor on Visible, and click Yes. 7. Select File/Save. Object Nationalizer will save the file and then reload it. 8. Repeat this procedure for MAXMAIN.EXE, also in the MAX411 folder. 9. Choose File/Exit.

102

Installation Guide

Identifying the Schema via the Desktop Shortcut

By default, the MAXIMO schema owner is MAXIMO. The schema parameter can be added to the command line to identify the schema. Add -S schemaowner to the command line. 1. Right-click on the MAXIMO Release 4.1.1 icon. 2. Click on Properties. 3. Click on Shortcut. 4. Add -sschemaowner to the command line in the Target field. For example: C:\Program Files\MAX411\MAXMAIN sMAXPROD.

103

Release 4.1.1

104

Installation Guide

Appendix C: Running Multiple Instances of the Application Server

You can start multiple instances of the Application Server on the same machine to connect to different databases using either the MXSERVER.BAT file or the Windows NT Services.

Starting multiple instances of Application Server using MXSERVER.BAT file

Multiple instances of Application Server can be started on the same machine to connect to different databases using the MXSERVER.BAT file. Before starting these instances, you need to do the following: 1. For each instance of Application Server that needs to be started separately, make separate copies of the MXSERVER.PROPERTIES file. For example, MXSERVER1.PROPERTIES. 2. Edit each and every copy of the MXSERVER.PROPERTIES file and change the mxe.name property to something unique. 3. Change the database-related properties in the MXSERVER.PROPERTIES files. 4. Turn-off the JSP Server for all Application Servers by making mxe.startJSPServer=false. There should be only one JSP Server running for all instances of the Application Server. 5. Change the Verity Collections used by the multiple instances of the Application Server appropriately using the keys in the MXSERVER.PROPERTIES files (These are the alias names specified in the K2SERVER.INI file).

105

Release 4.1.1

An example of how the alias names appear in the MXSERVER.PROPERTIES is shown in the next step.

mxe.verity.collection.itemcollection=itemcollection2 mxe.verity.collection.categorycollection=categorycollection2 mxe.verity.collection.itemcollection.eng=itemcollection2 mxe.verity.collection.categorycollection.eng=categorycollection2

Edit the K2SERVER.INI file and add additional collection details at the end of the file (follow the instructions present in the file). An example of how these will appear in that file is shown below. [Coll-2] collPath=.\verity\collections\itemcollection2 collAlias=itemcollection2 knowledgeBase=.\verity\thesaurus\mrothesaurus.kbm topicSet=.\verity\topics onLine=2 [Coll-3] collPath=.\verity\collections\categorycollection2 collAlias=categorycollection2 knowledgeBase=.\verity\thesaurus\mrothesaurus.kbm topicSet=.\verity\topics onLine=2 After following the above mentioned setup instructions, do the following for starting multiple instances of the Application Server. 1. Start the k2server program by running the K2SERVER.BAT file from the Command Prompt. 2. Start the JSP server program by running the JSPSERVER.BAT file from the Command Prompt.

106

Installation Guide

3. Start each and every instance of Application Server through the MXSERVER.BAT file by passing the appropriate MXSERVER.PROPERTIES file as an argument. For e.g., mxserver mxserver1.properties

Starting the JSP Server using Windows NT Services

To start the JSP Server as a Windows NT service, go to the Command Prompt from the MXServer folder and type the command JSPservice.exe install. To stop using it as a service, you would need to use the command JSPservice.exe remove.

Starting multiple instances of the Application Server using Windows NT Services

Multiple instances of the Application Server can be started to connect to different databases on the same machine using Windows NT Services, by following the instructions below: 1. Follow the setup instructions mentioned above for starting multiple instances of the Application Server using MXSERVER.BAT file. 2. For each instance of Application Server that needs to be started separately, make separate copies of the MXSERVICE.EXE and rename them. For example, MXSERVICE1.EXE, MXSERVICE2.EXE, etc. 3. Install each of the mxservice.exe programs using the command MXSERVICE1.EXE install propfile=MXSERVER1.PROPERTIES where: MXSERVICE 1.EXE is the installation program for the MXSERVER you want to install MXSERVER1.PROPERTIES is the specific properties file for the server you are starting.

4. Restart the services installed from the control panel or reboot the machine.
107

Release 4.1.1

108

Installation Guide

Appendix D: Microsoft Windows NT Server, Terminal Server or Windows 2000 Terminal Services, and Citrix Metaframe

MICROSOFT WINDOWS NT 4.0 SERVER, TERMINAL SERVER EDITION AND CITRIX METAFRAME
If you are running MAXIMO in a Microsoft Windows Terminal Server, Windows 2000 Terminal Services, or a Citrix MetaFrame environment, please be aware of the following recommendations and considerations.

Recommendations
Centura Object Nationalizer should not be used with Terminal Server or Windows 2000 Terminal Services. Screen design should be done on a workstation and then the modified executables should be copied to the MAXIMO folder on the Terminal Server or Windows 2000 Server/Advanced Server. MAXIMO add-on components, Brio.Report Builder, and Analyzer should not be installed onto Terminal Server or Windows 2000 Terminal Services, as these component install files are incompatible with Terminal Server or Windows 2000 Terminal Services. Brio.Report development and compilation should be done on a workstation and then the reports should be copied to the Terminal Server or Windows 2000 Server/Advanced Server. Running Centura Object Nationalizer, Brio.Report Builder, and Analyzer from Terminal Server or Windows 2000 Terminal Services can cause Dr. Watson errors; therefore, these applications should be run from a workstation.

109

Release 4.1.1

When installing the Scheduler or MAXIMO Crystal Integration add-on components, please be sure that the installations are done in install mode. This can be accomplished by running the component installation file, setup.exe, from the Control Panel, Add/Remove Programs icon. MAXIMO add-on component, Crystal Integration, needs the WTSRV\CRYSTAL folder in the path on the Terminal Server or WINNT\CRYSTAL folder in the path on Windows 2000 Server/Advanced Server. If not in the path you will receive the error Unable to load DLL. Workflow Designer should not run from Terminal Server or Windows 2000 Terminal Services. Workflow process design should be done on a workstation running MAXIMO connecting to the database in a LAN environment. Running the Workflow Designer on Terminal Server or Windows 2000 Terminal Services will cause the screen to repaint frequently.

Considerations
When linking documents to records you can not drag and drop a document from Windows Explorer into the Linked Document tab of an application. You need to create the link manually. To do this: From the Insert/Document Registration Menu item, register the document. From the Insert/Document link Menu item, link the document to a specific record. With Terminal Server or Windows 2000 Terminal Services the maximum color setting is 256 colors. The MRO Software-recommended color setting is 16-bit. With a 256-color setting MAXIMO will function correctly. If you receive Dr. Watson errors when printing verify that you have the most recent printer drivers for your printer. MRO Software testing has encountered problems when printing from Terminal Server or Windows 2000 Terminal Services with old print drivers.

110

Installation Guide

When exiting an application do not close the application using the X in the Window controls on the far upper right hand corner of the screen. Always exit the application from the File Menu option. Running Brio.Reports and Crystal reports uses an area to spool the output files. Sharing a common spool area for all users on the Terminal Server or Windows 2000 Terminal Services may cause conflicts with file names. To alleviate this problem each user can have a home directory on the Terminal Server or Windows 2000 Terminal Services. To create a home directory for each user and assign a drive letter to that home directory run CHKROOT.CMD from the following folder: WTSRV\APPLICATION COMPATABILITY SCRIPTS (Terminal Server) WINNT\APPLICATION COMPATABILITY SCRIPTS (Windows 2000 Terminal Services) This utility will launch Notepad with a document with an entry at the bottom that reads: SET DRIVE= Enter the drive letter you want to designate for the home directory (e.g., W). The SQRW_SPOOL and CRW_SPOOL settings in the MAXIMO.INI can be changed to reflect this new drive mapping (e.g., SQRW_SPOOL=W). The SQRW_SPOOL settings in the SQR.INI can be changed to reflect this new drive mapping (i.e., SQRW_SPOOL=W).

111

Release 4.1.1

112

Installation Guide

Appendix E: Installation of Online RFQ

Online RFQ gives you the ability to post requests for quotation (RFQs) to the MRO.COM web sites exchange page for competitive bidding. At the close of bidding on the RFQ line items, you can download the lowest bids to the Request for Quotation application. The Online RFQ Setup program can only be run on a machine to which MAXIMO has already been installed.

Running the Online RFQ Setup Program

The Online RFQ Setup program contains all the files necessary to run Online RFQ.

Starting the Online RFQ Setup Program

1. Insert MAXIMO Release 4.1.1 Application CD into the CD-ROM drive. 2. From your CD drive, go to the Setup/Online RFQ Path and click on SETUP.EXE. 3. The Online RFQ Setup installation program displays a series of screens and dialog boxes. All of these are listed below, along with comments that may be relevant to some of your choices. Follow the on-screen instructions. Welcome Note that it is recommended that you exit all other Windows programs (e.g., Word, Excel) before continuing. You may leave Windows Explorer open.

113

Release 4.1.1

Choose Setup Type

Network Installs all components on the network server. It does not set up this workstation to run Online RFQ. Local Installs all components on this workstation. Sets up this workstation to run Online RFQ. Client Configures this workstation to run Online RFQ. Online RFQ must already be installed on the network.

NOTE: If you have Windows Terminal Server or Windows 2000 Terminal Services, choose Local installation on the Windows Terminal Server or Windows 2000 Server/Advanced Server, respectively. Modifying File (This dialog box is displayed only if you have Windows 95/98.) Indicates the lines that need to be added to your AUTOEXEC.BAT file. You may select to have these lines added automatically through the installation, save the changes to AUTOEXEC.SAV to add later on, or not to make any changes to AUTOEXEC.BAT at this time. Start Copying Files The installation process starts here. The screen displays the status of the installation as it progresses. Setup Complete The setup is complete once the program has copied the files.

114

Installation Guide

Setting Up Additional Client Workstations

If you chose the Network setup option during the Online RFQ installation, you need to set up the system files on any client workstations that will be running Online RFQ. To do this, go to each client workstation and run the client installation program, SETUP.EXE from the MAX411\RFQCLIENT folder. This automatically edits the client system files and creates the program group. To run Online RFQ, the MAX411\jre_1.2.2\bin\classic folder must be in the path of the workstation. For a client installation on a Windows 95/98 workstation using the NetWare 32 client, the system login script will need to be edited to add this folder to the workstation's configuration.

Editing System File

The Online RFQ Setup program automatically edits your MAXIMO.INI file to allow you to run the Online RFQ application. However, you should check to make sure it is correct after installation.

MAXIMO.INI
Those sections of your MAXIMO.INI file that pertain to the auction application are shown below. NOTE: The system file examples assume that drive C is your local drive. Substitute your actual network drive letter(s) for C if you have installed the software on other drives. [system] MAIL=MAPI [report] MAILSPF=0

115

Release 4.1.1

[auction] FILEPATH=c:\Program Files\MAX411\auctionXML MAILSERVER=Mailserver Your mail server here. BROWSER=C:\Program Files\Internet Explorer\IExplore.exe LIBPATH=C:\Program Files\MAX411\jre_1.2.2\bin;c:\maximo\jre_1.2.2\lib;. OFFERINGNOTIFY=c:\Program Files\MAX411\AuctionClasses\ OfferingNotify.txt PRIVATENOTIFY=c:\Program Files\MAX411\AuctionClasses\ PrivateNotify.txt CLASSPATH=c:\Program\MAX411\jre_1.2.2\bin; c:\Program Files\MAX411\jre_1.2.2\lib; c:\Program Files\MAX411\jre_1.2.2\lib\rt.jar; c:\Program Files\MAX411\webmethods\client.zip; c:\Program Files\MAX411\Maximo\AuctionClasses;

116

MPD0694-411MAXORin-03-ENG-06/28/01