Installation Guide Microsoft SQL Server. Release 5.1 July 2002

Transcription

1 Installation Guide Microsoft SQL Server Release 5.1 July 2002

2 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 MRO Software, Inc. All rights reserved. Contains confidential and trade secret information of MRO Software, Inc. Use, transfer, disclosure, or copying without MRO Software, Inc. s express written permission is strictly forbidden. United States Patent No. 6,325,522 B2, and foreign patents pending (Online Commerce Services). United States and foreign patents pending (MAXIMO). Restricted Rights - Use, duplication, and disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS (OCT 1988). 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, MRO Online Commerce Services SM, MRO Software Operations Center SM, Supplier e-commerce Adapter, Illustrated Parts Catalog, Collego Catalog Manager, 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 Products AutoVue MAXIMO Workflow Illustrated Parts Catalog Online Commerce Services Third-Party Technology Information Portions 1996 Centura Software Corporation. Portions Actuate Corporation. Portions BEA WebLogic Server. BEA WebLogic Server provided by BEA Systems, Inc. Portions BroadVision, Inc. BroadVision Business Commerce, BroadVision One-to-One Enterprise, BroadVision One-to-One Publishing, BroadVision Tools provided by BroadVision, Inc. Portions 2000 webmethods, Inc. webmethods B2B Integrator, webmethods B2B Integration Server provided by webmethods, Inc. Portions Cimmetry Systems, Inc. AutoVue. AutoVue Professional provided by Cimmetry Systems, Inc. Portions 1998, 1999 NETRONIC Software GmbH. Portions Snowbound Software Corporation. RasterMaster raster imaging technology provided by Snowbound Software Corporation. Portions TAXWARE International, Inc. TAXWARE VERAZIP Sales/User, STEP provided by TAXWARE International, Inc.

3 Contents Chapter 1: What is MAXIMO 5.1? MAXIMO Application Server Verity Search Engine Actuate Server Database Server Transaction Server (optional) Typical MAXIMO 5.1 Network Configuration Diagram Chapter 2: Hardware/Software Considerations Competency Level Hardware and Software Configurations Client Workstation Setting for Internet Explorer Application Server Using BEA WebLogic 6.1 Service Pack Transaction Server (for Optional Components) Database Server Service Packs Chapter 3: Installing BEA WebLogic 6.1 Service Pack Starting the Setup Installation Program for BEA WebLogic 6.1 Service Pack Setup Installation Program Screens and Dialog Boxes Chapter 4: Installing the MAXIMO 5.1 Application Running the MAXIMO 5.1 Application Installation Starting the Setup Installation Program Setup Installation Program Screens and Dialog Boxes Configuration of MXSERVER.PROPERTIES File Database Related Properties Workflow Related Properties Actuate Report Server Properties MRO Integration Properties B2B Server Properties Work Order Generation Property Setting File Security for MXSERVER.PROPERTIES Release 5.1, 07/2002 iii

4 Contents Chapter 5: Verity Configuration Verity Configuration Building Collections Running Verity Chapter 6: Multisite Setup Accessing Multisite from the MRO Software Control Center Defining an Organization Defining Sites Creating a New Site Chapter 7: Installing Actuate Report Server Chapter 8: MAXIMO Adapter Add-Ons Chapter 9: Configuring Multiple MAXIMO 5 Environments Reporting Production vs Development/Testing Configuration Appendix A: Starting and Shutting Down the Application Server as a Windows Service Starting the Application Server Starting the WebLogic Administration Console to Manage the Application Server Stopping the Application Server Stopping the Application Server from the Administration Console. 52 Appendix B: MXSERVER. PROPERTIES File Descriptions MXServer Properties Database Properties Workflow Properties (also see the Workflow Designer s Manual for additional information) MRO Software Operations Center Properties B2B Server Properties Verity Search Properties Actuate Report Server Properties Preventive Maintenance (PM) Work Order Generation Property MEA (MAXIMO Enterprise Adapter) Properties webmethods B2B Server Catalog Properties Appendix C: DOCLINK.PROPERTY File Description DOCLINK Property Appendix D: MAXIMO Installation Worksheet Appendix E: Configuring Multiple MXServer.Properties Files. 69 iv Release 5.1, 07/2002

5 Contents Appendix F: Adding SQL Server Security Privileges Adding SQL Server Security Rights to a User Appendix G: Creating CMD files in the BEA Product Folder Index Release 5.1, 07/2002 v

6 Contents vi Release 5.1, 07/2002

7 Chapter 1: What is MAXIMO 5.1? Overview With the introduction of MAXIMO 5.1 MRO Software, Inc. introduces a new generation of MAXIMO based on web architecture. As a web application, you will run MAXIMO through an internet browser (Microsoft Internet Explorer). The different MAXIMO components are contained on several servers. Depending upon your installation, some or all of the following may be required: Application Server (containing MAXIMO Application-specific business components and Java Server Pages (JSP)-based Web Applications) and the Verity Search Engine Actuate Server Database Server Transaction Server (optional) More information about each of these servers is described in this chapter. Included in this chapter is a diagram of a typical MAXIMO 5.1 server configuration. The MRO Software Control Center houses the administrative applications that will be used in the setup and maintenance of MAXIMO 5.1. IMPORTANT Prior to running the MAXIMO 5.1 install, you must perform the following: Install the MRO Software Control Center Create the MAXIMO Database Install WebLogic 6.1 Service Pack 2 Additional Information For product and documentation updates, you can check Support online at Release 5.1, 07/2002 1

8 MAXIMO 5.1 MAXIMO 5.1 Application Server Verity Search Engine Actuate Server MAXIMO is built using J2EE (Java 2 Enterprise Edition) technology. This requires the use of a commercial application server. MAXIMO Release 5.1 uses BEA WebLogic as its application server. The Application Server consists of MAXIMO Applications using Java Server Pages (JSP), MAXIMO application specific business components, and BEA WebLogic Server. JavaServer Pages technology allows web developers and designers to rapidly develop and easily maintain information-rich, dynamic web pages that leverage existing business systems. The Application Server utilizes Java Runtime Environment (JRE) version 1.3. The Verity Search Engine, a product from Verity, Inc., used to perform fast text-based searches against vast amounts of data. Verity Search Engine has been very tightly integrated with the Application Server to search against a vast spectrum of inventory items. For more information on the Verity Search Engine, see Chapter 5: Verity Configuration. Actuate is the reporting tool for MAXIMO 5.1. The Actuate Server consists of two components: Report Cast Server - provides integration to the other servers in MAXIMO e-report Server - creates custom reports and modifies existing reports 2 Release 5.1, 07/2002

9 What is MAXIMO 5.1? Database Server MAXIMO Release 5.1 supports the Microsoft SQL Server 2000 database platform. For more information on the database, see Chapter 2: Hardware/ Software Considerations. Transaction Server (optional) The Transaction Server complements the Application Server to provide Transaction Server business-to-business communications. The Transaction Server uses the webmethods B2B Server, version Release 5.1, 07/2002 3

10 Typical MAXIMO 5.1 Network Configuration Diagram Typical MAXIMO 5.1 Network Configuration Diagram Client Side Client Machine with Internet Explorer 5.5 or 6.0 Server Side Transaction Server (optional) Application Server Components MAXIMO Applications MAXIMO Business Components BEA WebLogic Server Verity Search Engine Actuate Server Report Cast Server e-report Server Database Microsoft SQL Server 4 Release 5.1, 07/2002

11 Chapter 2: Hardware/Software Considerations This chapter provides the following information: Competency Level requisite skills and knowledge necessary for installing MAXIMO Release 5.1 Hardware Configurations detailed description of system hardware and configuration Software Configurations software requirements for MAXIMO Release 5.1 Competency Level To perform the installation, you should be familiar with the following: Microsoft SQL Server utilities such as SQL Query Analyzer Microsoft SQL Server system administration MAXIMO System Administration Release 5.1, 07/2002 5

12 Hardware and Software Configurations Hardware and Software Configurations Before installing MAXIMO Release 5.1 for Microsoft SQL Server, make sure that your system hardware is properly configured. For best performance, we recommend: Microsoft SQL Server database server Dedicated Application Server Dedicated Actuate Server Dedicated Transaction Server (optional) Client Workstation Minimum desktop computer configuration: Intel-based Pentium 450 MHz processor 64 MB of memory for Windows 98 or Windows NT Workstation 4.0. For Windows 2000 Professional and Windows XP Professional, the memory requirement is 128MB. SVGA 1024 x 768 High Color 16-bit color display Internet Explorer 5.5 or 6.0. For Windows XP Professional, MRO Software has tested and validated only Internet Explorer 6.0. Recommended desktop computer configuration: Intel-based Pentium 600 MHz processor or greater 96MB of memory for Windows 98 or Windows NT Workstation 4.0. For Windows 2000 Professional and Windows XP Professional, the memory recommendation is 256MB. SVGA 1024 x 768 High Color 16-bit color display Internet Explorer 5.5 or 6.0. For Windows XP Professional, MRO Software has tested and validated only Internet Explorer 6.0. The software requirements for the client workstation are listed below. Windows 98, Windows NT Workstation 4.0, Windows 2000 Professional, Windows XP Professional Internet Explorer 5.5 for all certified Windows versions except Windows XP Professional, Internet Explorer 6.0 for all certified Windows versions 6 Release 5.1, 07/2002

13 Hardware/Software Considerations Setting for Internet Explorer Follow the instructions in this section to verify your Internet Explorer settings. 1. Through your Control Panel, select Internet Options. On the Internet Properties Dialog Box. Internet Properties Dialog Box 2. Click the Settings button. Release 5.1, 07/2002 7

14 Hardware and Software Configurations 3. Click the Automatically button as shown in the Settings Dialog Box. Settings Dialog Box NOTE Users who need to punchout to OCS with Internet Explorer 6 have to specifically set the browser to accept third party cookies. 1. Click on Tools/Internet Options. 2. Click on Privacy Tab. 3. Click the Advanced Button. 4. Check Override Automatic Cookie Handling. 5. Click Accept under Third Party Cookies. 6. Click OK to save the settings. Restart the browser. 8 Release 5.1, 07/2002

15 Hardware/Software Considerations Application Server Configuration requirements will vary according to site-specific variables such as: MAXIMO applications employed database platform number of connecting client workstations desired performance levels Recommended Application Server configuration: 2 4 dedicated, Intel-based Pentium 600 MHz dual processors 1 GB RAM per processor The Application Server provides business logic and framework for the MAXIMO applications. The software requirements for the Application Server are listed below. Microsoft Windows NT Server 4.0 Service Pack 6a, Windows 2000 Server Service Pack 2, Windows 2000 Advanced Server Service Pack 2 WebLogic 6.1 Service Pack 2 (provided by MRO Software, Inc.) IBM JRE 1.3 (supplied) In order to have client workstations communicate with the Application Server using Java s Remote Method Invocation (RMI), you must have TCP/IP installed on the Application Server and the client workstations. Please refer to your NT/2000 documentation for TCP/IP installation, configuration, and management information. MAXIMO applications use JSP technology. A web server, such as the BEA WebLogic server, is used for accepting HTTP requests from client programs (web browsers) and for responding in HTML content. Whenever a client requests a JSP page, the web server processes the JSP page, and the web server sends the result of the JSP page in HTML content back to the client. Please refer to the java.sun.com/products/jsp/ index.html link for more information on JSP Technology. Release 5.1, 07/2002 9

16 Hardware and Software Configurations Using BEA WebLogic 6.1 Service Pack 2 You must have BEA WebLogic Application Server 6.1 Service Pack 2 installed on your machine in order to successfully install MAXIMO. This version of BEA WebLogic Application Server is supplied to you with MAXIMO. If this version and service pack of BEA WebLogic is not already on your machine, you must install it as described in Chapter 3: Installing BEA WebLogic 6.1 Service Pack 2, on page 13. The following statement pertains to the licensing of BEA WebLogic: Licensee is granted a Limited Use license to use the BEA Weblogic product(s). "Limited Use" means that the BEA Weblogic product(s) can be used by Licensee solely in conjunction with the contemporaneous use of MAXIMO. Licensee may not use the BEA Weblogic(s) product in a standalone fashion or with software or data not incorporated into or integrated with MAXIMO. 10 Release 5.1, 07/2002

17 Hardware/Software Considerations Transaction Server (for Optional Components) The Transaction Server complements the Application Server to provide e-commerce business-to-business communication. The Transaction Server uses webmethods B2B Server version 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 The software requirements for the Transaction Server are listed below. Windows NT Server 4.0 Service Pack 6a, Windows 2000 Server Service Pack 2, Windows 2000 Advanced Server Service Pack 2 Release 5.1, 07/

18 Database Server Database Server Service Packs The software requirements for the Database Server are listed below. MAXIMO Release 5.1 for Microsoft SQL Server will run on any Microsoft Windows server that supports the Microsoft SQL Server 2000 database platform. We recommend installing the latest Microsoft SQL Server Service Pack. The TCP/IP network library is the only SQL Server network library that MRO Software certifies and supports. At release time for MAXIMO Release 5.1, MRO Software had certified the following Service Packs: Windows NT (server and workstation): Service Pack 6a Windows 2000: Service Pack 2 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. 12 Release 5.1, 07/2002

19 Chapter 3: Installing BEA WebLogic 6.1 Service Pack 2 This chapter contains the information necessary for installing BEA WebLogic Service Pack 2. In order to successfully complete this installation, the BEA WebLogic 6.1 Service Pack 2 Installation Program requires that you have 300MB of free disk space on your system. Release 5.1, 07/

20 Starting the Setup Installation Program for BEA WebLogic 6.1 Service Pack 2 Starting the Setup Installation Program for BEA WebLogic 6.1 Service Pack 2 1. Log in to NT/2000 as Administrator or a user with administrative rights.. 2. Insert the CD labeled MAXIMO Release 5.1 into the CD-ROM drive. 3. To start the installation program, use Windows Explorer to open your CD-ROM drive folder, then double-click weblogic610sp2_win.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. On screen Instructions Welcome Click Next to begin. License Information Select Yes to accept the License Agreement. Click Next to continue. Click Next. Choose Install Set Select Server Only as the installation set to be installed. BEA Home Directory Selection If you have already installed any version of BEA WebLogic or any BEA product, select the Use Existing BEA Home option. If you have not previously installed any BEA products, select Create a New BEA Home (for example, c:\bea). BEA Product Installation Directory You must accept the default of wlserver6.1 for the product folder. Important Note Do not change the default. If you choose anything other than the installation default, you will have to manually configure MAXIMO according to the instructions in Appendix F. Click Next to continue. 14 Release 5.1, 07/2002

21 Installing BEA WebLogic 6.1 Service Pack 2 Default Server Configuration You may accept the default values in the WebLogic Admin Domain Name, Server Name, Listen Port, Secure (SSL) Listen Port fields, or change these value. Windows Service When prompted to install WebLogic Server as a Windows Service, select No. System Password Creation Specify a password that will be used to start the WebLogic Server and to manage the server from the browser through a console application. This password will also be requested when you install MAXIMO. Installing BEA WebLogic Server The installation process starts here. The screen displays the installation as it progresses. Release 5.1, 07/

22 Starting the Setup Installation Program for BEA WebLogic 6.1 Service Pack 2 Install Complete Dialog Box Install Complete The setup is complete once the Install Complete dialog box is displayed. NOTE You will receive a fully licensed BEA WebLogic product when you install MAXIMO 5.1. As noted on the Install Complete dialog box, the copy installed at this time is a temporary evaluation copy, only. 16 Release 5.1, 07/2002

23 Chapter 4: Installing the MAXIMO 5.1 Application This chapter contains the information necessary for installing MAXIMO 5.1. This chapter contains the following: Instructions for installing MAXIMO 5.1 Configuring the MXSERVER.PROPERTIES file Setting File Security for the MXSERVER.PROPERTIES file This document contains a worksheet to assist you in gathering the information you need prior to running this installation program. See Appendix D: MAXIMO Installation Worksheet, on page 67. Release 5.1, 07/

24 Running the MAXIMO 5.1 Application Installation Running the MAXIMO 5.1 Application Installation Installing the MAXIMO 5.1 Applications should take about 15 minutes. In order to successfully complete this installation, the MAXIMO Installation Program requires that you have 400MB of free disk space on your system. Starting the Setup Installation Program 1. Log in to NT/2000 as Administrator. 2. Insert the CD labeled MAXIMO Release 5.1 into the CD-ROM drive. 3. To start the installation program, choose Start/Run then type d:\maximo51.exe (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 maximo51.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 any text editor if you need to change some of these values as described later in this chapter. On screen Instructions Welcome It is strongly recommended that you close all other programs before continuing with this installation. 18 Release 5.1, 07/2002

25 Installing the MAXIMO 5.1 Application Serial Number Information This installation requests a serial number to continue. You should enter the serial number included in your MAXIMO license agreement. BEA WebLogic Check This screen is displayed only if you do not have BEA WebLogic 6.1 ServerPack 2 on your machine. If BEA WebLogic is not available on your machine, this dialog box indicates that you must have the version of BEA indicated. Confirm BEA WebLogic Installation Home Directory You must either verify the location where BEA WebLogic is be installed or accept the default value. If you have another version of BEA WebLogic on your machine, an error message dialog box displays which prompts you to install the correct version. Select BEA WebLogic Domain Setup requires that you select a BEA WebLogic Domain. Click on the Domain that you will be using with MAXIMO. Choose Install Folder Enter the destination location of the folder to which the installation program should install MAXIMO. Choose the default (C:\MAXIMO) or enter another folder by either typing it in or clicking Choose and using the Browse for Folder dialog box. Database Type Select Microsoft SQL Server as your database type. Database Login Information Enter or accept information in the following fields: Database Server Name Enter the host name of the server where SQL Server is installed. Port Number Enter the port number. The default is Database Name Enter the SQL Server database name. Database Owner Accept the default value. The default is dbo. DB Owner Password Enter a password for the Database Owner. Database Username Database owner username (i.e. MAXIMO). Release 5.1, 07/

26 Running the MAXIMO 5.1 Application Installation SMTP Host Information Enter the host name of the machine running the SMTP server. This is needed for facilities that make use of such as Workflow notifications and any error message notifications. Your administrator can provide this information. Notification Information If you are using Workflow, enter the address of the workflow administrator. The address entered should be in the form The installation program uses this value to update the mxe.workflow.admin property in the MXSERVER.PROPERTIES file. If you are not using Workflow, enter the address of the MAXIMO administrator. The installation program uses this value to update the mxe.admin property in the MXSERVER.PROPERTIES file. B2B Server Connection Information If you are using the B2B Server, you should enter information in the following fields: B2B Server Host B2B Server Port Number Address of the B2B Server administrator Enter Username Enter the username of the B2B administrator. Default is Administrator. Enter Password Enter the password of the B2B Administrator. Default is manage. If these values are not entered, the MXSERVER.PROPERTIES file will need to be modified later in order to use the B2B Server. Local Host Name Enter the name of the local host machine on which MAXIMO is being installed. Actuate ereport Server Information Enter the following fields to connect to the ereport Server: Report Server Name Report Server Port Number the default is 80 Actuate Administrator s Password the default is admin Any of these values may be entered or changed manually later on through the MXSERVER.PROPERTIES file. Windows Service Question The installation program defaults to add MAXIMO as a Windows Service. Click Next to continue or 20 Release 5.1, 07/2002

27 Installing the MAXIMO 5.1 Application uncheck this box if you do not want this application started automatically. BEA WebLogic Password If you selected to start MAXIMO as a Windows Service and want to include BEA WebLogic 6.1 Service Pack 2 as part of that service, enter the BEA Administrator Password on this screen. This is the same password that was entered during BEA WebLogic information. Port Information Please specify the port number to be used by the MAXIMO Application Server. The default is 80. Pre-Installation Summary A summary of your installation selections displays on this screen. Installing MAXIMO The installation process starts here. The screen displays the status of the installation as it progresses. Install Complete The setup is complete once the program has copied the files. If errors occurred, they may be viewed through the installation log (the install.log file) located in the C:\MAXIMO\UNINSTALLER DATA folder. Verify the user registration login user name and password in the MXSERVER.PROPERTIES file is set to dbo. Edit the file as needed. In order to run MAXIMO, you must reboot your machine. Also, if MAXIMO is not running as a Windows Service you must refer to Appendix A: Starting and Shutting Down the Application Server, on page 49 to manually start and stop MAXIMO. When MAXIMO is running, connect by opening your browser and typing the URL: name of the application server>:<port>. For example - Release 5.1, 07/

28 Configuration of MXSERVER.PROPERTIES File Configuration of MXSERVER.PROPERTIES File The following section describes the parts of the MXSERVER.PROPERTIES file for basic functions of MXSERVER. A table describing these properties, and many others, appears as an appendix to this manual. NOTE You MUST change the following property in the MXSERVER.PROPERTIES file to reflect the schemaowner username (i.e MAXIMO). User Registration Login Name - mxe.system.reguser Database Related Properties You must grant permission to the schemaowner to create new users. See Appendix F, Adding SQL Server Security Privileges. Property names and their values are case sensitive. After editing the file, be sure to save the changes. Schema Owner The owner of the database schema. If the owner of the database schema is MAXIMO, this value will appear as: mxe.db.schemaowner=dbo. Driver The driver name. The default driver is: mxe.db.driver=com.inet.tds.tdsdriver The Host Name, Port, and SID The Microsoft SQL Server driver defined in mxe.db.url. For example, if this value reads: mxe.db.driver=jdbc:inetdae7:servername:portnumber? database=databasename&language=us_english&nowarnings= true you would substitute your server name, port number, and database name, respectively, for the italicized variables. Database User The user that binds to the database when MXServer begins running. For example, if the schema owner is MAXIMO, this value reads: 22 Release 5.1, 07/2002

29 Installing the MAXIMO 5.1 Application mxe.db.user=maximo Password The password for the database user. For example, if the password is MAXIMO, this value reads: mxe.db.password=maximo User Registration Login Name The user registration login name when registering a new user. User name specified must have permission to create new users. (See Appendix F, Adding SQL Server Security Privileges.) With the default value as maximo, this value will read: mxe.system.reguser=maximo User Registration Login Password The user registration login password. With the default value as maximo, this value will read: mxe.system.regpassword=maximo SMTP Mail Server The host running the SMTP server. You need the host for facilities that make use of such as Workflow notifications and any error message notifications. Your network administrator can provide this address. This initially reads: Workflow Related Properties mail.smtp.host=mailhost.yourcompany.com. Administrator account account of the workflow administrator. For example, if the account of the administrator is admin@company.com name, this value would read: mxe.workflow.admin=admin@company.com If you are using Workflow, you may need to delete the comment marks from the following parameters:! mxe.crontask.psdi.workflow.autoaccept notification and frequency Release 5.1, 07/

30 Configuration of MXSERVER.PROPERTIES File Actuate Report Server Properties! mxe.crontask.psdi.workflow. notification notification and frequency! mxe.crontask.psdi.workflow.escalation Escalation facility and frequency! mxe.crontask.psdi.workflow.waitformaterial Auto assignment facility and frequency mxe.report.actuate.webserver URL address of the machine where MAXIMO is installed. If the web server is running on a port other than the default, the port number needs to be specified. mxe.report.actuate.reportserver The machine name of the report server that accesses the encyclopedia. mxe.report.actuate.rptserveradminpass The administrator s password for the Actuate Server. mxe.report.actuate.db.connectstring The data source name of the Actuate server that will run reports. If you are using Actuate Report Server, you must delete the comment marks from the following two parameters:! mxe.crontask.psdi.app.report.actuateupdatecronta sk The frequency with which MAXIMO attempts to create a new Actuate user from a newly created group which does not have a corresponding Actuate user. The default value is 5m (5 minutes).! mxe.report.actuate.acdocumentroot URL address of the machine where MAXIMO is installed. This address is used by report jsp pages to locate the jsp pages on the Actuate web server. The default address is WebServerMachine: Release 5.1, 07/2002

31 Installing the MAXIMO 5.1 Application MRO Integration Properties Edit this section, only if you are utilizing the MAXIMO e-commerce Adapter, by deleting the comment marks from the following parameters: mxe.crontask.psdi.mnet.processpocron This parameter searches the system database for POs and sends them to their destination. The default is 60s (60 seconds). mxe.mro.txn.timeout This parameter determines the timeout value for product search transactions. The default is 30s (30 seconds). B2B Server Properties IMPORTANT You must edit this section only if you are using the B2B Server. For more information on these properties, see B2B Server Properties on page 59. Work Order Generation Property If you are utilizing MAXIMO Preventive Maintenance records, delete the comment marks from the following parameter: mxe.crontask.psdi.app.pm.pmwogencrontask This parameter generates work orders from PM (Preventive Maintenance) records. The default is 14d (14 days). Release 5.1, 07/

32 Setting File Security for MXSERVER.PROPERTIES Setting File Security for MXSERVER.PROPERTIES The MXSERVER.PROPERTIES file contains clear text, nonencrypted system passwords. You must prevent users who are not system administrators from accessing this file by restricting the permissions. Each time, after starting the Application Server, do the following: 1. In Windows Explorer, select the MXSERVER.PROPERTIES file. 2. Right-click on the file and select the Properties. 3. In the Properties dialog box, select the Security tab. 4. Place a checkmark in the Deny Permissions box (this checkmarks all the boxes). All other files in the <MAXIMO ROOT> folder should be set to Read access for all users who are not system administrators. NOTE To enhance the protection of passwords in MXServer.properties, refer to the section titled "Protecting the MXServer.properties File," at the end of Chapter 14, Managing the Application Server. Continue on to Chapter 7: Verity Configuration to build the Verity Collections. 26 Release 5.1, 07/2002

33 Chapter 5: Verity Configuration This chapter gives an overview of the following topics related to the configuration of Verity: overview of the Verity Search Engine Verity configuration This section contains information on: building collections adding new fields to the item collection running Verity Overview The Verity Search Engine is a product from Verity, Inc. used to perform fast text-based searches against vast amounts of data. The Verity Search Engine product is independent of any database and maintains data that you need to search in Collections (the concept of a Collection is similar to a database). Verity Search Engine works with the Application Server to search against your inventory. As a result, the system updates the Verity collection automatically with the latest changes from the MAXIMO database. This process keeps your Verity Collections up to date. The Application Server uses two Verity Collections to facilitate your search criteria: Item Collection - searches for items and displays those found. Category Collection - searches for items and lists the categories where they reside In the Verity Collections, the system treats each record like a document. Most of the time, the system is either inserting, modifying, and/or deleting new documents from the collections. The Verity Search Engine product provides a program, k2server, to provide precision search and retrieval from the collections. Release 5.1, 07/

34 Verity Configuration Verity Configuration After you install MAXIMO Release 5.1, the system automatically creates a Verity folder under the MAXIMO folder along with other subfolders, namely, Collections, defaultstyles, and K2401. To use the Verity Search Engine, perform the following steps: 1. Build Collections 2. Run Verity Building Collections Building a collection is copying all the data from the database into the Verity Collections. Whenever the system must create a collection, 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). These files are in the folder <MAXIMO ROOT>\ VERITY\DEFAULTSTYLES folder. Do not modify the catstyle file, as in most cases, you do not need to change it. You can 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." To build the Verity Collections, perform the following steps from the Command Prompt in the <MAXIMO ROOT> folder: 1. Enable the verity triggers file by running the following batch file: enableveritytriggers.bat 2. Build the item collection from the database by running the following batch file: bulkloaditems.bat 28 Release 5.1, 07/2002

35 Running Verity Verity Configuration 3. Build the category collection with data from the database by running the following batch file: bulkloadcategories.bat The bulkloaditems.bat and bulkloadcategories.bat files reside in the <MAXIMO ROOT> folder. They create the collections in the <MAXIMO ROOT>/verity/collections folder. If you want to create the collections in another folder, open the script files using a text editor and review the usage. To set up Verity as a Windows Service: From the Command Prompt in the <MAXIMO ROOT> folder run searchserverservice -install. To start the service, go to the Control Panel and click on Services. Select searchbrokerservice.exe and click on Start. To start Verity manually: Go to the Command Prompt and run the K2SERVER.BAT file from the <MAXIMO ROOT> folder. The K2SERVER.BAT file takes information from the <MAXIMO ROOT>\ K2SERVER.INI file. The K2SERVER.INI file provides the K2SERVER information about what collections need to be searched by the client programs. NOTE NOTE Your screen will show the words "Pinging Broker:9900->Dead." This is not an error message, it indicates that the Verity server is running. After you build the Collections, to access the Collections you need to stop the Search Server process and restart it. Release 5.1, 07/

36 Verity Configuration 30 Release 5.1, 07/2002

37 Chapter 6: Multisite Setup Overview MAXIMO Sites and Organizations Multisite is an implementation of MAXIMO whereby different company sites can share data units from a single database. Rather than setting up multiple instances of MAXIMO, a company can now install MAXIMO once, and multiple sites can access the same database via a web browser. To use the Multisite implementation, there are two new concepts used to set up MAXIMO: sites and organizations. Sites and organizations are logical divisions of a company determined by what type of operations are performed at certain locations, and what data can be shared by certain locations. This chapter describes briefly how to: set up your initial organization set up your initial site Both an organization and site are required in order to utilize MAXIMO. For more complete information on multisite, see the Multisite Planning Guide. Creating Initial MAXIMO Users The users MAXIMO and SYSADM cannot run multisite, therefore you must create MAXIMO users via Signature Security in order to access the MAXIMO applications. Refer to Chapter 1, Signature Security of the MAXIMO System Administrator s Guide. Release 5.1, 07/

38 Accessing Multisite from the MRO Software Control Center Accessing Multisite from the MRO Software Control Center On the MRO Software Control Center Welcome screen, select Multisite setup from the Administrative Control Center. Welcome Screen 32 Release 5.1, 07/2002

39 Defining an Organization Multisite Setup This section describes how to define an initial organization. Multisite Setup Screen (Organization Tab) To create a new organization: 1. Click the insert button. 2. Type an organization name for the organization. The organization name must be unique. 3. Specify a base currency in the Base Currency 1 field. A base currency is required in order to define your organization. The other fields on this screen are optional and may be filled in later. Release 5.1, 07/

40 Defining Sites Defining Sites Creating a New Site You define Sites at the organization level. At least one site must be added in order to use the organization. To create a new Site, follow the steps below. 1. On the Search tab, locate the Organization for which you want to add sites. You can type the complete or partial organization name and click Find. 2. From the results list, click an organization. 3. Click the Sites tab in the main Multisite setup window. 4. Click New Row. The window expands. 5. Type a Site ID for the new site. You must enter a Site ID is required, and it must be unique within the database. 6. You can enter addresses for the Ship To: and Bill To: fields. These fields are optional. 7. Click Update to refresh the page. 8. Click Save in the toolbar to update the database. 34 Release 5.1, 07/2002

41 Chapter 7: Installing Actuate Report Server Overview With the introduction of MAXIMO 5.1, MRO Software, Inc. introduces Actuate as its new reporting tool. Actuate allows you to design and build reports to be published on the web through your Internet browser (Microsoft Internet Explorer). For information on installing Actuate, see the Actuate Installation Guide. Release 5.1, 07/

42 36 Release 5.1, 07/2002

43 Chapter 8: MAXIMO Adapter Add-Ons Overview MAXIMO 5.1 has many add-on components that allow you to connect to marketplaces and enterprise systems. The following is a list of components that are described in detail in the individual adapter installation guides. MAXIMO e-commerce Adapter MAXIMO e-commerce Adapter for Catalog Loading MAXIMO e-commerce Adapter for Ariba CSN MAXIMO e-commerce Adapter for Commerce One Marketsite MAXIMO Enterprise Adapter MAXIMO Enterprise Adapter for SAP R/3 MAXIMO Enterprise Adapter for Oracle Applications MAXIMO Enterprise Adapter for PeopleSoft Applications Prior to installing any of these adapters, you must first install webmethods B2B. Refer to your individual adapter guide for both webmethods installation and configuration instructions as well as adapter-specific information. Release 5.1, 07/

44 38 Release 5.1, 07/2002

45 Chapter 9: Configuring Multiple MAXIMO 5 Environments Overview A default MAXIMO Release 5 installation contains a standard folder structure allowing connectivity to a single database. MAXIMO 5, however, can be configured to allow for multiple environments and databases. NOTE MAXIMO uses an Application Server to provide access to the business components of the MAXIMO Application and to the MAXIMO Web Application. MAXIMO uses BEA WebLogic Server 6.1 SP2 as the Application Server. For topics regarding managing the Application Server in a Windows or Solaris environment, see Chapter 14: Managing the Application Server in the MAXIMO System Administrator s Guide. Common elements in the standard MAXIMO folder structure are: JSP Folder Structure The JSP folder contains the MAXIMO *.jsp files. These represent screen elements that can be modified. See the Design Studio for more information on customizing your MAXIMO screens. Class Files MAXIMO 5 gives you the ability to create custom class files to meet your business needs. For more information on creating custom class files, see the SDK (Software Developer s Kit) Actuate Reports The RPT folder(s) on the Actuate server contain the files for report modifications. See the reporting section in this chapter for more info on multiple report folders. The above elements will be referred to in the three common configuration types defined below. Most customers will fall into one of these 3 categories. If you plan to have multiple Release 5.1, 07/

46 MAXIMO 5 environments, please refer to these types to determine which configuration best suits your business needs 40 Release 5.1, 07/2002

47 TYPE I Type I represents the default, out of the box configuration of MAXIMO Release 5. All users connect to a single MAXIMO database using one JSP folder, a common set of class files and one Actuate report folder as shown below. Release 5.1, 07/

48 TYPE II In Type II, you have the option of connecting to multiple databases. All users utilize one set of JSP screens, a common set of class files and Actuate reports, but can connect to multiple databases. In order to do this, you will need to make copies of the MXServer.properties file and rename according to your desired environment. Each MXServer.properties file will allow the MXServer process to connect to a specific database. See "Appendix E: Configuring Multiple MXServer.Properties Files," page 69 for more information. 42 Release 5.1, 07/2002

49 You will also need to modify the login.jsp file to add the servername field to the login screen. Users then specify the servername to connect the specific database. Modify the login.jsp file located in the maximo\jsp\common\system folder. Add the code (in bold) which will create the Server field on the login screen (as depicted above). <tr> <td width='30%' align=right>server: </td> <td width='30%'><input type='text' name='server' size='15' value='<%= lastloginserver %>' ></td> <td width='35%'></td> </tr> <tr> <td width='30%' align=right>user Name: </td> <td width='30%'><input type='text' name='username' size='15' value='<%= lastloginusername %>' ></td> <td width='35%'></td> </tr> Release 5.1, 07/

50 Type III In this example, you may want to make JSP screen and report customizations, as well as creating custom class files using the SDK. In this configuration you would have 3 separate iterations of MAXIMO, each with its own JSP folder. You will need to create a corresponding Actuate RPT folder for each MAXIMO instance (see the Reporting section for information on the Actuate foldernames) NOTE: CREATING ANY CUSTOM CLASS FILES REQUIRE YOU TO HAVE A FULL MAXIMO FOLDER STRUCTURE 44 Release 5.1, 07/2002

51 You will want to modify each login.jsp file located in the maximo1\jsp\common\system folder to change the servername from the default of MXServer to your specific server name. Search for the line below and add your server name in place of <%=lastloginserver %>"> <input type="hidden" name="server" size="15" value="<%=lastloginserver %>"> example: <input type="hidden" name="server" size="15" value="/mxservermax1"> Release 5.1, 07/

52 Reporting When configuring reports in a multiple MAXIMO environment, you must specify which report folder each MAXIMO instance will be using. This is accomplished by making a configuration change to the actuatefolder.jsp file, located under the maximo1\jsp\common\reports directory. Where maximo1 is the specific instance of MAXIMO you are modifying Within this file, you specify which root reports folder (rpt1, rpt2, etc ) will be used with each specific MAXIMO instance. Below are the default contents of this file: <% %> //Set this variable equal to the root directory name in the Actuate Encyclopedia String locale = /rpt ; For example, if MAXIMO1 was being utilized, an associated rpt1 folder will contain the reports. Thus, you would modify the actuatefolder.jsp file in the Maximo1\jsp\common\reports folder <% %> //Set this variable equal to the root directory name in the Actuate Encyclopedia String locale = /rpt1 ; 46 Release 5.1, 07/2002

53 Production vs Development/Testing Configuration MRO Software Product Support recommends that no development, testing or training be done on the Production server. Below we depict a common production and development configuration. This example shows a typical MAXIMO 5 production environment at the left. You have one production application server and one production report server connecting to a common database server. Secondary servers for development/testing are shown to the right. All MAXIMO customizations can be done on the dev/test servers and, when tested, migrated to the production servers. NOTE: The Development/Test servers shown do not have to be server class machines. Typically, there is a small number of developers and less stress on the system. Therefore these machines can be low-end servers or high-end desktops capable of handling your development needs. Release 5.1, 07/

54 48 Release 5.1, 07/2002

55 Appendix A: Starting and Shutting Down the Application Server as a Windows Service Overview This appendix describes how to: start the Application Server start the WebLogic Administration Console to manage the Application Server stop the Application Server stop the Application Server from the WebLogic Administration Console Release 5.1, 07/

56 Starting the Application Server Starting the Application Server If the Application Server is not configured as a Windows Service, perform the following to start the Application Server. Note for Users with Double-byte Requirements NOTE: FOR INSTALLATIONS WITH DOUBLE-BYTE REQUIREMENTS, OPEN THE STARTMAXIMOSERVER.CMD FILE FROM \\ 807; /42,3 AND VERIFY THAT THE MAXIMO FOLDER (I.E C:\MAXIMO) PRECEDES ORACLE THIN (I.E.C:\MAXIMO\LIB\ORACLETHIN.ZIP) IN THE CLASSPATH. Example: Set CLASSPATH=%MXSERVER_CLASSPATH%; C:\MAXIMO\lib\oraclethin.zip;%CLASSPATH% To start the Application Server, complete the following steps from the command prompt in the <APPLICATION SERVER> directory (the directory where BEA WebLogic is installed). 1. Enter the following command to change to location of the mydomain directory:./807; /42,3 2. Run the following command located in the directory specified in the previous step: startmaximoserver.cmd where MAXIMOSERVER is the name of your application server. If you configured a new instance of the Application Server, then you should run the appropriate script file for that instance. 3. The Application Server starts up and runs MAXIMO. 50 Release 5.1, 07/2002

57 Starting and Shutting Down the Application Server as a Windows Service Starting the WebLogic Administration Console to Manage the Application Server The following steps describe how to manage the Application Server from the Administration Console. 1. Check that the Application Server is already started and running. 2. Use Internet Explorer to access the Administration Console by specifying the URL as: where <machinename> is the name of the machine <port> is the port number where the Application Server is started The Application Server password is needed to access this URL. Release 5.1, 07/

58 Stopping the Application Server Stopping the Application Server To stop the Application Server when running from the command prompt, press [Ctrl+C]. Stopping the Application Server from the Administration Console The following steps describes how to stop the Application Server from the Administration Console. 1. From the Administration Console, identify the MAXIMO Application Server from the list of servers shown in the frame on the left side of the screen. 2. Right-click on the server name and select the Stop this Server option. 3. The Administration Console displays a message in the frame in the right side of the screen. 4. Click Yes to stop the server. The Administration Console sends a command to stop the Application Server. 52 Release 5.1, 07/2002

59 Appendix B: MXSERVER. PROPERTIES File Descriptions The MXSERVER.PROPERTIES file is a configuration file the Application Server accesses when it starts. You selected the folder location for this file, and property values, during installation. The tables below list those properties from the file that you may want to edit and describes 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. For more information on setting file security for MXSERVER. PROPERTIES, see Setting File Security for MXSERVER.PROPERTIES on page 26. Release 5.1, 07/

60 MXServer Properties MXServer Properties Property Name mxe.name mxe.home Description Name of the Application Server that binds it to the RMI registry. The default name is MXServer. The home directory where MAXIMO is installed. NOTE: MUST HAVE DOUBLE \ BETWEEN THE DIRECTORY NAMES (I.E. MXE.HOME = C:\\MAXIMO) mxe.rmi.port mxe.verbosity mxe.msglogfile mxe.errlogfile mxe.allowlocalobjects mxe.userlicensekey Port used by RMI for communication, if left at 0 RMI will use any available port on the system. To use a specific port, set this parameter to an available port number. The default value is 0. Wordiness of the diagnostic messages the server writes to the console. Values range from 1 (least wordy) to 10 (most wordy). The default value is 3. File name to which system messages are appended. To write to the console, enter stdout. To write to a file, specify a file name. The default file name is stdout. File name to which error messages are appended. To write to the console, specify stderr. To write to a file, specify a file name. The default file name is stderr. If the MAXIMO web application is configured to run along with MAXIMO business components in the same application server instance (which is the recommended default configuration for MAXIMO), then setting this option to true will enhance the performance of the system. The setting of this option to either true or false does not affect system functionality. The default value is true. The user license key. 54 Release 5.1, 07/2002

61 Database Properties Property Name mxe.db.schemaowner mxe.db.driver mxe.db.url Description Owner of the database schema. Default owner name is dbo. For a Microsoft SQL Server database, the default driver name is: mxe.db.driver=com.inet.tds.tdsdriver The host name, port, and SID. The default is: mxe.db.driver=jdbc:inetdae7:servername: portnumber?database=databasename&language=us_e nglish&nowarnings= true. where you would substitute your server name, port number, and database name for the italicized values. mxe.db.initialconnections Number of database connections that need to be kept open as soon as the Application Server is started. The default value is 15. NOTE: IF THE VALUE IS SET LOWER THAN 15, MXSERVER CANNOT CONNECT TO THE DATABASE. mxe.db.maxfreeconnections mxe.db.minfreeconnections mxe.db.newconnectioncount mxe.db.logsqltimelimit mxe.db.user mxe.db.password Maximum number of free database connections available in connection pool. The default value is 30. Minimum number of free database connections needed in the connection pool in order 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. Database user the server uses to attach to the database server. This user must be the schema owner. Password for the database schema owner user name. Release 5.1, 07/

62 Database Properties Property Name mxe.system.reguser mxe.system.regpassword mail.smtp.host mxe.db.systemdateformat mxe.admin Description User registration login name when registering a new user. User name specified must have permission to create new users. The default is maximo. User registration login password. The default is maximo. Name of the host running the SMTP server. This name is needed for facilities that make use of such as Workflow notifications, Actuate ing, and any error message notifications. Your network administrator can provide this address. System date format. For SQL Server, the value is: mxe.db.systemdateformat=getdate() address used if the MAXIMO user has not specified an address in the labor record. The default is mailhost.yourcompany.com. 56 Release 5.1, 07/2002

63 Workflow Properties (also see the Workflow Designer s Manual for additional information) Property Name mxe.workflow.admin mxe.crontask.psdi.workflow. Notification mxe.crontask.psdi.workflow. Escalation mxe.crontask.psdi.workflow. WaitForMaterial mxe.crontask.psdi.workflow. AutoAccept Description account of the Workflow administrator. Determines whether the notification facility is enabled and how often it is executed. Default value is 5m (5 minutes). Determines whether the escalation facility is enabled and how often it is executed. Default value is 5m (5 minutes). After a task is build into a work order and that work order is waiting for material (WAITMATL), this property periodically checks to see if the material has been received so the status can be changed to approved. Default value is 5m (5 minutes). When this facility is enabled, accept actions found on assignments are automatically processed. Default value is 5m (5 minutes) In some cases, user AUTOACPT and labor code AUTOACPT may both need to be created. Release 5.1, 07/

64 MRO Software Operations Center Properties MRO Software Operations Center Properties Property Name mxe.crontask.psdi.mnet. ProcessPOCron mxe.mro.txn.timeout Description The frequency with which the database is to be polled for purchase orders to be sent to their destination. The default is 60s, every 60 seconds. The time out value for product search and other electronic commerce transactions. The default value is 30 seconds. 58 Release 5.1, 07/2002

65 B2B Server Properties Property Name mxe.b2b.hosturl mxe.b2b.username mxe.b2b.password mxe.b2b.interface mxe.b2b.service mxe.b2b.reply.service mxe.b2b.admin. mxe.b2b.ariba.interface Description The B2B server host name or TCP/IP address and port. The B2B server 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 address of the administrator The name of the Ariba integration package. This information is required for communication with Ariba. Release 5.1, 07/

66 Verity Search Properties Verity Search Properties Property Name mxe.crontask.psdi.server. VerityCollSubmitCronTask mxe.verity.collection. itemcollection mxe.verity.collection. categorycollection mxe.verity.bulkload. totalfieldcount Description Specifies the time interval for the Verity Collection Submit crontask to run. The default is 5 minutes. Updates the item collection with modified data from the database. This property is used by the Verity Collection Submit CronTask. Updates the category collection with modified data from the database. This property is used by the Verity Collection Submit CronTask. 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. The default value specifies the total number of userdefined fields to be included in the Collections as in the following example: mxe.verity.bulkload.fieldx=<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.field2=item_in1, in1 mxe.verity.bulkload.field3=item_in1, in2 mxe.verity.bulkload. longdescription mxe.verity.server mxe.verity.port Indicates whether an item s long description should be included in the collection or not. The default is true (include long description). Specifies the name of the machine which runs the k2server. The default value is localhost. Specifies the port number of the machine which runs the k2server. The default port number is Release 5.1, 07/2002

67 Property Name mxe.verity.maxrows mxe.verity.collection. itemcollection.en mxe.verity.collection.item collection.resultset.attribute.n Description Specifies the maximum number of rows that are returned in the search results. The default value is 200. Specifies the item collection alias name in the k2server.ini file. Specifies the attributes that should be included in the resultset of the search. n is the number of attribute fields, starting from 0 and increasing by one for each of the attribute fields. Some examples are: mxe.verity.collection.itemcollection.resultset.attribute.0 =ITEM_ID, mxe.verity.collection.itemcollection.resultset.attribute.1 =ITEM_DESCRIPTION mxe.verity.collection.category collection.en mxe.verity.usecommodity Restriction Specifies the category collection alias in the k2server.ini file Indicates whether or not commodity restrictions need to be enabled for item and category collections. Default value is false (do not include commodity restrictions). Release 5.1, 07/

68 Actuate Report Server Properties Actuate Report Server Properties Property Name mxe.report.actuate.webserver Description URL address of the web server that runs the web interface to the report encyclopedia. If the web server is running on a port other than the default, the port number needs to be specified. The default value is where: WebServerMachine is the machine where MAXIMO is installed 8080 is the port number mxe.report.actuate. reportserver mxe.report.actuate. rptserveradminpass mxe.report.actuate.db. connectstring mxe.report.actuate. acdocumentroot mxe.crontask.psdi.app.report. ActuateUpdateCronTask The machine name of the report server that accesses the encyclopedia. The administrator s password for the Actuate Server. The data source name of the Actuate server that will run reports. The default value is maximo. URL address of the machine where MAXIMO is installed. This address is used by report jsp pages to locate the jsp pages on the Actuate web server. The default address is The frequency with which MAXIMO attempts to create a new Actuate user from a newly created group which does not have a corresponding Actuate user. The default value is 5m (5 minutes) 62 Release 5.1, 07/2002

69 Preventive Maintenance (PM) Work Order Generation Property Property Name mxe.crontask.psdi.app.pm. PMWoGenCronTask Description When the PM Work Order Generation Facility is enabled, Work Orders will be generated from PM records. Default value is 14d (14 days). MEA (MAXIMO Enterprise Adapter) Properties Property Name mea.db.user mea.db.password Description The internal username that MEA uses to process data. The username must be a valid MAXIMO username and the user s profile information (for example, purchasing limit) must agree with the type of data received through MEA. The default is maximo. The password for mea.db.user. The default is maximo. webmethods B2B Server Catalog Properties For information about defining company catalogs, see the MAXIMO System Administrator s Guide. This information is being stored in the company s record. Release 5.1, 07/

70 webmethods B2B Server Catalog Properties 64 Release 5.1, 07/2002

71 Appendix C: DOCLINK.PROPERTY File Description DOCLINK Property. The DOCLINK.PROPERTY file, contained in <MAXIMO ROOT>, defines where newly created documents will be placed and allows users to view these documents when clicking onto a hyperlink Property Name mxe.doclink.doctypes.defpath Description The default folder for newly created files. After the file is created, the system looks in the DOCLINK. PROPERTY file to see the default folder location where it should store the newly created file. One examples is: C:\\DOCLINKS\\default Note the location of double backslashes. Release 5.1, 07/

72 DOCLINK Property. 66 Release 5.1, 07/2002

73 Appendix D: MAXIMO Installation Worksheet Prior to running the MAXIMO Installation program, please review the following list to be sure that you have gathered all of the information requested. The page numbers after each entry indicate the corresponding location in the text. 1. Serial Number Information. The serial number included with your MAXIMO License Agreement. (page 19) 2. Choose Install Folder for installing MAXIMO. The default is C:\MAXIMO. (page 19) 3. Database Login Information. The Database Server Name, Database Name, and password. (page 19) 4. SMTP Host Information. Name of your SMTP (Simple Mail Transfer Protocol) server. This is your mail gateway server. (page 20) 5. Notification Information. The address of the Workflow Administrator or MAXIMO Administrator. (page 20) 6. B2B Server Connection Information. The user name and password for connecting to the B2B server. (page 20) 7. Actuate e-report Server Information. The Actuate Report Server Name. (page 20) 8. BEA WebLogic Folder. The folder to which BEA WebLogic should be installed. (page 21) Release 5.1, 07/

74 68 Release 5.1, 07/2002

75 Appendix E: Configuring Multiple MXServer.Properties Files To connect to multiple MAXIMO databases, you must have an MXServer.properties files for each database. To perform this task, do the following: Make copies of the MXServer.properties file and rename them according to your desired environment. Modify each properties file with the appropriate database schema information, schema username and password. Modify the mxe.name property so each MXServer has a unique name. Example 1 MAX1srvr.properties file // MXServer.properties : Configuration file for MXServer // // Name to bind the MXServer server object to in the RMI registry mxe.name=max1srvr // Database Schema Owner mxe.db.schemaowner=dbo // Database login name -- depends on driver, e.g. sometimes it's name= mxe.db.user=max1 // This user must have sysadmin role, as defined via sp_addsrvrolemember. // Database login password -- depends on driver, e.g. sometimes it's passwd= mxe.db.password=maximo Release 5.1, 07/

76 Example 2 MAX2srvr.properties file // MXServer.properties : Configuration file for MXServer // // Name to bind the MXServer server object to in the RMI registry mxe.name=max2srvr // Database Schema Owner mxe.db.schemaowner=dbo // Database login name -- depends on driver, e.g. sometimes it's name= mxe.db.user=max2 // This user must have sysadmin role, as defined via sp_addsrvrolemember. // Database login password -- depends on driver, e.g. sometimes it's passwd= mxe.db.password=maximo Example 3 MAX3srvr.properties file // MXServer.properties : Configuration file for MXServer // // Name to bind the MXServer server object to in the RMI registry mxe.name=max3srvr // Database Schema Owner mxe.db.schemaowner=dbo // Database login name -- depends on driver, e.g. sometimes it's name= mxe.db.user=max3 // This user must have sysadmin role, as defined via sp_addsrvrolemember. // Database login password -- depends on driver, e.g. sometimes it's passwd= mxe.db.password=maximo 70 Release 5.1, 07/2002

77 Appendix F: Adding SQL Server Security Privileges To register a new MAXIMO user from the MAXIMO Login Screen, SQL Server Security Administrator privileges must be granted to the schema owner (i.e. MAXIMO). Release 5.1, 07/

78 Adding SQL Server Security Rights to a User Adding SQL Server Security Rights to a User SQL Server Security Administrator privileges need to be granted to the database owner of the MAXIMO database. To add security privileges, do the following: 1. Launch SQL Server Enterprise Manager and connect to the SQL Server. 2. Select Security/Logins from the left pane, and highlight the MAXIMO Login in the right pane. 3. Right-click and select Properties. 72 Release 5.1, 07/2002

79 Adding SQL Server Security Privileges 4. From the SQL Server Login Properties - MAXIMO dialog box, click the Server Roles tab. SQL Server Login Properties Dialog Box: General Tab Release 5.1, 07/

80 Adding SQL Server Security Rights to a User 5. Click the Security Administrators checkbox, then click Properties. SQL Server Login Properties Dialog Box: Server Roles Tab 74 Release 5.1, 07/2002

81 Adding SQL Server Security Privileges 6. From the Server Role Properties - securityadmin dialog box click Add. Server Role Properties - securityadmin Dialog Box 7. From the Add Members dialog box highlight MAXIMO and click OK. Add Members Dialog Box Release 5.1, 07/