Installing and Configuring Tivoli Monitoring for Maximo

Transcription

1 Installing and Configuring Tivoli Monitoring for Maximo 1. Introduction This purpose of this paper is to help you install and configure the IBM Tivoli Monitoring agent for Maximo. The document serves as a supplement to the information posted at this URL: a181d6155e3a/entry/ibm_tivoli_monitoring_for_maximo1?lang=en 2. Environment Tivoli Service Request Manager is installed in a distributed configuration on Redhat bit as shown in the figure below: VM3 Redhat bit WebSphere 6.1 Maximo TSRM VM4 Windows bit ITM for Maximo Agent On ITM FP5 VM1 Redhat bit TSRM Remote Deployment VM2 Redhat bit IBM Directory Server (LDAP) 6.1/ DB2 9.5 Figure 1: ICOC TSRM stack 1

2 TSRM and Maximo are administered through remote deployment on VM1. You will need to rebuild and redeploy the Maximo EAR files in order for the Maximo agent to communicate with WebSphere; this will be described in a later section below. VM2 contains the database instance for TSRM and the user repository for LDAP which is installed on VM2. VM4 contains the remote agent which monitors Maximo on VM3. The ITM agent is part of an ITM FP5 infrastructure. 3. Installing the ITM for Maximo Agent and Support Files In this section, we cover some of the details on installing the agent and its support files on the Tivoli Portal server and Tivoli Enterprise Management server. 3.1 Installing the agent: In our test cases, we installed the agent to remotely monitor TSRM. Note that the agent is only available for Windows. After extracting the agent archive to a temporary location, change directory to: <TEMPORARY SUBDIRECTORY>\ITM Agent for Maximo\agentbuilder\install\agents\maximo Ensure that CANDLE_HOME is set. For example, CANDLE_HOME=C:\IBM\ITM. Then run the following command: installiraagent.bat C:\IBM\ITM The command will indicate success or failure. 3.2 Installing the Support Files: The support files for the Maximo agent are available for all ITM supported platforms including non- Windows. On the TEPS and TEMS machine, extract the agent archive to a temp location, and change directory to: <TEMPORARY SUBDIRECTORY>\ITM Agent for Maximo\agentbuilder\install\agents\maximo In order to successfully run the TEMS and/or TEPS support scripts, you will need to make sure environment variable CANDLE_HOME is defined (e.g. /opt/ibm/itm) and ensure the PATH environment variable includes $CANDLE_HOME/<arch>/ms/bin. For example: export PATH=/opt/IBM/ITM/li6263/ms/bin:$PATH 2

3 To install TEMS support, run the following command: installiraagenttems.sh /opt/ibm/itm Then recycle the TEMS. To install TEPS support, run the following command: installiraagentteps.sh /opt/ibm/itm Now, recycle the TEPS. 4. Configuring the ITM for Maximo Agent In this section, we explain how to configure the agent and how to work-around some of the issues. 4.1 Create the Instance: After installing the agent and support files, create an instance of the agent. Do not use the word maximo in the name; this will cause some serious agent anomalies. We used SRM as the name of our instance during our tests. 4.2 Configure the Agent: After configuring the ITM base parameters (TEMS host and port), configure the Maximo specific parameters. In the figure below, we show the parameters that we used in our tests: 3

4 Figure 2a: Log Configuration tab The Log file directory should contain the logs directory for MXServer in application server profile (e.g. ctgappsrv01) as shown. 4

5 My.maximo.com Figure 2b: Maximo Configuration tab Choose HTTP or HTTPS protocol. In our tests we used HTTP. The host should contain the hostname where WebSphere is running. The default port for the agent (7001) is the default port for Weblogic. If using WebSphere, use the HTTP or HTTPS port (depending on what you selected as protocol). In our tests, we used the default HTTP WebSphere port If using WebSphere with HTTPS, then the default port is In our tests for the user, we used maxadmin. This user will be used to remotely access Maximo and requires at least Maximo read-only authorization (e.g. maximouser). Note: user wasadmin will not work unless it s assigned to role maximouser. The Java home directory should be the java directory on the Maximo agent machine (not the remote WAS server). The java version can be IBM or Sun Java 1.5 or greater. 5

6 5. Configuring for WAS Security If only using Maximo security, you will see data in the agent workspaces. However, if your Maximo environment is configured with Application Server Security for authentication and authorization, you will not see data in your agent workspaces. There are extra steps needed to make the agent work with WAS security. 5.1 Modify the Maximo MBO web module: On the Maximo administration server (in Figure 1, VM1), change directory to: <SMP_DIR>/maximo/applications/maximo/mboweb/webmodule/WEB-INF. For example: cd /opt/ibm/smp/maximo/applications/maximo/mboweb/webmodule/web-inf Edit the file web.xml, and add the following in bold within the security-constraint block: <security-constraint> <web-resource-collection> <web-resource-name>maximo Report Tool</web-resource-name> <description>pages accessible by authorized users</description> <url-pattern>/reporttool/*</url-pattern> <http-method>get</http-method> <http-method>post</http-method> </web-resource-collection> <web-resource-collection> <web-resource-name>maximo Monitoring Agent</web-resource-name> <description>pages accessible by authorized users</description> <url-pattern>/toolclient/*</url-pattern> <http-method>get</http-method> <http-method>post</http-method> </web-resource-collection> <auth-constraint> 6

7 <description>roles that have access to MAXIMO Report Tool</description> <role-name>maximouser</role-name> </auth-constraint> <user-data-constraint> <description>data transmission guarantee</description> <transport-guarantee>none</transport-guarantee> </user-data-constraint> </security-constraint> Save the file, and now you will need to rebuild the EAR file and redeploy it. 5.2 Rebuild and Redeploy the Maximo EAR File Change directory to <SMP_DIR>/maximo/deployment. For example: cd /opt/ibm/smp/maximo/deployment Run the following command: buildmaximoear.sh After the ear file is built, now you must redeploy the EAR file to the WAS server. Change directory to <SMP_DIR>/ jacl/solutions. For example: cd /opt/ibm/smp/jacl/solutions Run the following command: DeployApplication.sh WASAdminUserName WASAdminPassword "MAXIMO" WASNodeName WASApplicationServerName <SMP_DIR>\maximo\deployment\default\maximo.ear WASVirtualHost WASWebServerName IMPORTANT NOTE: For WASVirtualHost do not use a real hostname. Use the literal string maximo host For example: 7

8 DeployApplication.sh wasadmin tvt2test MAXIMO ctgnode01 MXServer /opt/ibm/smp/maximo/deployment/default/maximo.ear maximo_host webserver1 After a successful deployment, recycle the MXServer on the WebSphere application server (e.g. VM3 in Figure 1). 6. Verifying the Agent In this section, we will validate the ITM for Maximo agent configuration. 6.1 Validate the Maximo Log Files: Start the ITM for Maximo agent from the MTEMS console. The agent will create a directory %CANDLE_HOME%\TMAITM6\logs\maximo. If this directory is not created after starting the agent, check the Java home parameter in the agent configuration. The MOSWOS log files are written to this sub-directory. If opening a PMR against the Maximo agent, then you will need to attach those log files to the PMR. 6.2 Validate the Agent Workspaces: Log into the TEPS console and navigate to the Maximo agent workspaces. Go to the Performance Object Status. The figure below shows the agent is running correctly with all objects status shown as active: Figure 3: Performance Object Status 8

9 Each workspace should look similar to figures below: Figure 4a: Background Processes (no escalations errors available on server) Figure 4b: System Information view 9

10 Figure 4c: User Information view (fly-over shows 3 users) Figure 4d: System Performance 10

11 Figure 4e: Maximo agent main view Figure 4e shows the line graph workspaces for the main view of the Maximo agent. If you re not getting data and receiving error KFWITM217E Request error: SQL_Open Request failed rc=300, please refer to the following technote: In summary, you will need to re-load the predefined queries. In addition to re-loading the query, you will also need to reselect the column in the filter tab for each workspace (Database connections, Free Memory, and User Sessions). The figure below shows the filter tab for the properties of the Database connections workspace. Check the ConnectionsUsed, Users, and FreeMemory for each workspace, respectively. 11

12 Figure 5: Check mark the column in filters tab 12

13 Appendix A. Acronyms Acronym ITCAM ITM TEP TEPS TEMS Definition IBM Tivoli Composite Application Monitoring IBM Tivoli Monitoring Tivoli Enterprise Portal Tivoli Enterprise Portal Server Tivoli Enterprise Management Server 13

14 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 give 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 might 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. 14

15 Any references in this information to non-ibm websites 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 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. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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. 15

16 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. 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 IBM s application programming interfaces. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed. 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 Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Windows is a trademark 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. Other company, product, and service names may be trademarks or service marks of others. 16