IBM Maximo Spatial Asset Management Version 7 Release 5. Installation Guide

Transcription

1 IBM Maximo Spatial Asset Management Version 7 Release 5 Installation Guide

2 Note Before using this information and the product it supports, read the information in Notices on page 9. This edition applies to version 7, release 5, modification 0 of IBM Spatial Maximo Asset Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2009, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Installing Maximo Spatial Asset Management Updating environment data Updating database properties Updating installation properties Updating the WebSphere Application Server Network Deployment host name Preparing for the installation Running the installation program Deploying the EAR files on WebLogic Server... 6 Deploying the EAR files on WebSphere Application Server Command syntax for deploying EAR files on WebSphere Application Server Notices Trademarks Copyright IBM Corp. 2009, 2011 iii

4 iv Installation Guide

5 Installing Maximo Spatial Asset Management The installation of IBM Spatial Maximo Asset Management Version involves installing the product, deploying the Enterprise Application Archive (EAR) files, and configuring the software. You start the installation programs from the launchpad. Before you begin IBM Maximo Asset Management version must be installed on the same Windows administrative workstation where you plan to install Maximo Spatial Asset Management Version , and in the same language as Maximo Spatial Asset Management Version Additionally, before you install Maximo Spatial Asset Management, you must update the Maximo database during the Maximo Asset Management installation. For information about installing Maximo Asset Management, see the IBM Maximo Asset Management 7.5 Installation Guide in the Maximo Asset Management Information Center (opens in a new browser window or tab). For information about upgrading to version 7.5, see the Upgrade Guide, IBM Maximo Products V7.1 to V7.5 on the Maximo Upgrade Resources (opens in a new browser window or tab) web site. For information about the hardware, software, and network requirements for your product, see the Overview and Planning (opens in a new browser window or tab) page on the Maximo Asset Management wiki. About this task You must install Maximo Spatial Asset Management on a Microsoft Windows administrative workstation. The Maximo Spatial Asset Management EAR files are built on the Windows workstation and later deployed to the application server. Maximo Spatial Asset Management integrates with ESRI ArcGIS Server for enterprise deployment. Maximo Spatial Asset Management is not designed to support mixed database environments, for example, Maximo running on Oracle while the Geographic Information System (GIS) is running on SQL Server. Maximo Spatial Asset Management does support different versions of the same systems, such as, Maximo running on Oracle 10g and GIS running on Oracle 11g. Procedure 1. If you are upgrading to Maximo Spatial Asset Management Version from an earlier version of Maximo Spatial Asset Management (Version 7.1, 7.1.1, or 7.1.2), update your environment data. 2. Prepare to install. 3. Install Maximo Spatial Asset Management. 4. If you use Oracle WebLogic Server, deploy the EAR files. Copyright IBM Corp. 2009,

6 Updating environment data 5. For IBM WebSphere Application Server environments: The EAR files were installed during the IBM Maximo Asset Management installation. If this task was deferred during the Maximo Asset Management installation, deploy the EAR files. 6. If a license for IBM Maximo Spatial Asset Management is installed and enabled, add spatial features to Maximo Spatial Asset Management records. When you install a fix pack or upgrade an existing installation, the installation program uses values that are recorded from the previous deployment. If anything in your environment changed since the original deployment, you must record these changes in properties files before you can install Maximo Spatial Asset Management. About this task If you made environmental changes to any of the systems in the original deployment, such as changing a host name or updating a password, the changes must be recorded. To record the environmental changes, you update the install.properties and maximo.properties files on the administrative system. When the product installation program runs an upgrade task, it attempts to use values in the install.properties file and the maximo.properties file. During the upgrade process, if the user name or password for a system is not updated, the installation program uses the credentials in the properties files. If the installation program cannot log on to a system with the credentials found in the properties files, you are prompted to supply the correct information. Updated values are written to the appropriate property file. Updating credential information in property files has one exception: database connection and credential information must always be current before you attempt an upgrade operation. Database connection information and credential information are stored in the maximo.properties file. Any changes to this information from the time of the original deployment must be manually recorded in the maximo.properties file before you begin an upgrade from version 7.1, 7.1.1, or to version When you change the property value of the IBM WebSphere Application Server Network Deployment host name (WAS.DeploymentManagerHostName) in the install.properties file, you must also update a property for the WebSphere Application Server Network Deployment thin client in the thinwasadmin.bat file and then run that file. For information about upgrading to version 7.5, see the Upgrade Guide, IBM Maximo Products V7.1 to V7.5 on the Maximo Upgrade Resources (opens in a new browser window or tab) web site. Updating database properties Before you can upgrade your version of Maximo Spatial Asset Management, you must record any database changes that have been made in your environment since the original deployment. You update the database properties in the maximo.properties file. 2 Installation Guide

7 Procedure 1. Change to the product_home\maximo\applications\maximo\properties directory. The default location is C:\IBM\SMP\maximo\applications\maximo\ properties. 2. Make a copy of the maximo.properties file, and rename the file. 3. Delete the maximo.properties file. 4. Change to the product_home\etc directory. 5. Back up the maximo.properties_orig file. Save this backup copy permanently. 6. Rename the unencrypted maximo.properties_orig file to maximo.properties. 7. Copy the maximo.properties file to the product_home\maximo\applications\ maximo\properties\ directory. 8. Edit the maximo.properties file and update the credential or connection information for the database server. 9. Save the maximo.properties file. 10. Run the encryptproperties.bat file in the product_home\maximo\tools\ maximo\ directory on the file to encrypt it. What to do next Update the installation properties in the install.properties file. Updating installation properties Before you can upgrade your version of Maximo Spatial Asset Management, you must record any installation program properties changes that have been made in your environment since the original deployment. You update the installation properties in the install.properties file. Before you begin Update the database properties in the maximo.properties file, as described in the previous topic. Procedure 1. Change to the product_home\etc directory. 2. Edit the install.properties file. Do not change encrypted properties that are prefixed by [enc]. You are prompted for updated values during the update operation. These values are written to the install.properties file. 3. Save the file. What to do next If you use WebSphere Application Server, you must update the WebSphere Application Server Network Deployment host name. Updating the WebSphere Application Server Network Deployment host name Before you can upgrade your version of Maximo Spatial Asset Management, you must update the WebSphere Application Server Network Deployment host name that was used in the previous deployment. Installing Maximo Spatial Asset Management 3

8 Before you begin Preparing for the installation Update the installation properties in the install.properties file, as described in the previous topic. Procedure 1. Update the WAS.DeploymentManagerHostName value in the install.properties file. 2. Edit the C:\IBM\SMP\WASClient\thinwasadmin.bat file. 3. Update the following line with the new, fully qualified host name of the WebSphere Application Server Network Deployment server: set wsadminhost=-dcom.ibm.ws.scripting.host=fully_qualified_host_name. 4. Run the thinwasadmin.bat file with these values: thinwasadmin.bat -domain manager user name -password. 5. When prompted, indicate that you do want to download the truststore file. Before you install Maximo Spatial Asset Management, you must complete tasks on the middleware servers and on your administrative workstation. Before you begin The installation program requires access to the middleware servers that are installed with Maximo Asset Management to complete the installation. You need the administrative user IDs and passwords for the middleware servers. About this task When you install Maximo Spatial Asset Management, you modify the configuration and content of your application server, database server, and directory server. These servers are referred to as the middleware servers. Procedure 1. Install IBM Maximo Asset Management 7.5 on the same administrative workstation where you install Maximo Spatial Asset Management, and in the same language as Maximo Spatial Asset Management. Be sure to update the Maximo database during the Maximo Asset Management installation. 2. Back up the middleware servers and the administrative workstation. 3. Prepare the application server. Application server WebSphere Application Server WebLogic Server What to do Ensure that the middleware servers are started. The installation program connects to the middleware servers by using the middleware login information that you specify during the product installation. Ensure that the application server (MAXIMOSERVER) is stopped. If the application server is running, stop the server and wait a few minutes before you start the installation program. If the application server is not stopped, the installation process stops. 4 Installation Guide

9 4. If you run the installation program in a double-byte language or an Eastern European language, set the workstation regional settings to that language. You can reset your regional settings after you complete the installation. Running the installation program You can start the installation program for Maximo Spatial Asset Management from the launchpad. About this task You access the product software either from IBM Passport Advantage or from the product DVD if you requested one. To download your product from IBM Passport Advantage, follow the instructions in the download document. The launchpad is automatically started when you run the product DVD. If the Windows autorun feature is disabled, you can start the launchpad by running the launchpad.exe program from the root directory of the product DVD. If you run 64-bit applications, use launchpad64.exe. Procedure 1. Start the launchpad. 2. Select a language for the installation program, and click OK. 3. Click Install from the menu of options. 4. Select the installation path for Maximo Asset Management from the drop-down menu. 5. Click IBM Spatial Maximo Asset Management. 6. Follow the steps in the installation program. 7. If the Package Options window opens, ensure that the check box to defer updating the Maximo database is cleared, and the checkbox to defer redeploying the Maximo applications is cleared. If you are installing additional products, you can choose to defer the Maximo application redeployment option. If the package options were specified during the Maximo Asset Management installation, the Package Options window might not open. 8. Continue the installation program until the Pre-Install Summary window opens. If the system check passes successfully, no error messages appear under System Check Messages. 9. If any error messages are shown, make a note of the message identifiers, and stop the installation. Contact your system administrator. 10. When the installation is complete, from the Package Successfully Deployed window, click Done. 11. For non-english environments only: If you use WebSphere Application Server, restart the application server. What to do next Download and install the latest hot fix to ensure that you have the most current build with all recent fixes. The latest hot fixes and release notes are on the IBM Support Portal for Maximo Spatial Asset Management (opens in a new browser window or tab). Installing Maximo Spatial Asset Management 5

10 Review any existing release notes for this product at Release Notes for Maximo Spatial Asset Management 7.5 (opens in a new browser window or tab). Additionally, perform the following steps: v To check the results of the language package installation, review the language package installation log file, TDToolkitdate-time.log, in the Maximo_home\maximo\ tools\maximo\log directory. v If you use WebLogic Server, deploy the EAR files. v If you use WebSphere Application Server, the installation is complete. You can start Maximo Spatial Asset Management. However, if your environment requires you to deploy the EAR files manually, and this task was deferred during the Maximo Asset Management installation, deploy the EAR files. Deploying the EAR files on WebLogic Server If you use WebLogic Server, after you install Maximo Spatial Asset Management, you must deploy the EAR files from the WebLogic Server console. Deploying the EAR files starts the application server. Before you begin v The EAR files must be deployed after the Maximo database is updated. The Maximo database is updated as part of the installation process. However, if you manually update the database (by running the updatedb command), make sure that you do so before you deploy the EAR files. v On a Windows operating system: If the MAXIMOSERVER server is not running, start it from a command prompt. v On a UNIX operating system: Ensure that the WebLogic Server daemon is running. To view the WebLogic Server console, you must have a Java Virtual Machine installed. Procedure 1. Change to the mydomain directory. Operating system Windows UNIX Location From a command prompt, change the path to drive:\oracle_installation_location\ user_projects\domain\mydomain Open a command prompt, and change the path to /home/mxadmin/oracle/ user_projects/domains/mydomain 2. Start WebLogic Server. Operating system Windows UNIX Command startweblogic.cmd./startweblogic.sh 3. Type the WebLogic Server user name and password. 4. Start the MAXIMOSERVER administration console by typing the following address in the address bar of your browser: 5. Log on to the WebLogic Server console. 6 Installation Guide

11 6. Follow the instructions in the WebLogic Server console help to deploy the maximo.ear file and the maximoiehs.ear file. Results The installation is complete. You can start Maximo Spatial Asset Management. Deploying the EAR files on WebSphere Application Server You can manually deploy Maximo Spatial Asset Management EAR files on WebSphere Application Server. You perform this task if your organization has application deployment restrictions that require that you deploy application files manually. About this task The EAR files are installed on WebSphere Application Server during the Maximo Asset Management installation. If the deployment of the EAR files was deferred during the Maximo Asset Management installation, you can deploy the EAR files manually. Procedure 1. Deploy the Maximo EAR file: PRODUCT_HOME\jacl\solutions\DeployApplication.[bat sh] WASAdminUserName WASAdminPassword "MAXIMO" WASNodeName WASApplicationServerName "PRODUCT_HOME\maximo\deployment\default\maximo.ear" WASVirtualHost WASWebServerName 2. Deploy the Maximo help system EAR file: PRODUCT_HOME\jacl\solutions\DeployApplication.[bat sh] WASAdminUserName WASAdminPassword "MAXIMOIEHS" WASNodeName WASApplicationServerName "PRODUCT_HOME\maximo\deployment\default\maximoiehs.ear" WASVirtualHost WASWebServerName Related reference: Command syntax for deploying EAR files on WebSphere Application Server You use parameters in the command syntax when you manually deploy the EAR files on WebSphere Application Server. Command syntax for deploying EAR files on WebSphere Application Server You use parameters in the command syntax when you manually deploy the EAR files on WebSphere Application Server. Syntax of the commands to deploy EAR files The syntax of the commands for deploying the EAR files includes the following parameters. Parameters WASAdminUserName A WebSphere Application Server Network Deployment account with deployment privileges. Installing Maximo Spatial Asset Management 7

12 WASAdminPassword The password of the user who is specified in the WASAdminUserName parameter. WASNodeName The name of the WebSphere Application Server Network Deployment node. WASApplicationServerName The name of the WebSphere Application Server Network Deployment application server. WASVirtualHost The name of the WebSphere Application Server Network Deployment virtual host. WASWebServerName The name of the WebSphere Application Server Network Deployment web server. Related tasks: Deploying the EAR files on WebSphere Application Server on page 7 You can manually deploy Maximo Spatial Asset Management EAR files on WebSphere Application Server. You perform this task if your organization has application deployment restrictions that require that you deploy application files manually. 8 Installation Guide

13 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. Copyright IBM Corp. 2009,

14 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at 10 Installation Guide

15 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Notices 11

16 12 Installation Guide

17

18 Printed in USA