CLMMonitoringThroughITM < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

TWiki > Deployment Web > CLMServerMonitoring > CLMMonitoringThroughITM

Revision 9 - 2020-06-02 - 15:31:21 - TimFeeney

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!!  CLM Server Monitoring with IBM Tivoli Monitoring %RED%(DEPRECATED: CLM Server Monitoring is no longer supported and was dropped in version 6.0.3.)%ENDCOLOR%
%DKGRAY% Authors: Main.BorisKuschel, Main.GeraldMitchell <br>
Build basis: CLM 4.0.5, ITM 6.2.1+, Monitoring Agent for CLM Server Monitoring 4.0.5, Monitoring Agent for CLM Server Monitoring for !WebSphere Application Server 4.0.5
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

*UNDER CONSTRUCTION*
This page gives the instructions on how to set up the IBM Tivoli Monitoring Agents for CLM Server Monitoring so that the performance data can be consumed by IBM Tivoli Monitoring components, namely Tivoli Enterprise Monitoring Server (hereby referred to as TEMS) and Tivoli Enterprise Portal Server (hereby referred to as TEPS).

%RED%
*This page and these instructions have not been tried nor verified on supported versions of CLM Server Monitoring plugin(4.0.6 or later), and so should not be interpreted as neither instructions nor best practices at this time. This page is a general explanation and example reference only*
%ENDCOLOR%

The following server host names are assumed:

   * itm.jazz.net - Server hosting an instance of TEMS and TEPS
   * clmjts.jazz.net - instance of the JTS Server application fin which the Tivoli OS agent is installed and the Monitoring Agent for CLM Server Monitoring is installed.

These instructions will cover both the installation on CLM applications hosted !WebSphere Application Server  and/or Tomcat, in either case the application server is installed on clmjts.jazz.net. 

It is recommended to set up the agent on the same machine as the application server it is monitoring and to ensure that the JConsole tool is able to connect cleanly to the CLM Server Monitoring JMX interface.

---++ Tivoli Agent Setup

This section assumes that the machine on which the agent is installed is able to connect cleanly to the CLM Server Monitoring interface using JConsole.

In order for Agent metadata and configuration to appear as available datasets in Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server, the appropriate support files need to be installed on those servers.

---+++ Preparing TEMS and TEPS

On the TEMS and TEPS machines (itm.jazz.net), unzip the installation package for the application servers you have CLM application deployed on. 
If your environment contains !WebSphere and Tomcat then the following instructions will need to be performed for both. 

The package of !WebSphere is KCH.zip while for Tomcat it's KCD.zip. Unzip the one which you wish to install and run the following script for TEPS (ensure TEMS and TEPS are started):
   * =installIraAgentTEPS.(bat || sh) <ITM Installation directory> (eg. C:\IBM\ITM)=
and for TEMS:
   * =installIraAgentTEMS.(bat || sh) <ITM Installation directory> (eg. C:\IBM\ITM)=

---+++ Installing agent
   1. On each machine  (clmjts.jazz.net) with an application server hosting the CLM applications you wish to monitor, ensure that an ITM OS Agent is installed on the machine and then run the following script from the package corresponding to the application server type:
   * =installIraAgent.(bat || sh) <ITM Installation directory> (eg. C:\IBM\ITM)=
   1. Once the agent is installed it needs to be configured. We will follow the graphical setup of the agent, there is also a possibility to run the configuration from the command like. Please follow the Tivoli documentation on how to do this and substitute the same values as specified in the ITM manager GUI instructions.
      1. Run the “Manage Tivoli Monitoring Service” either from Programs on Windows or “itcmd manage” command on Unix. (Make sure to launch as administrator on windows)<img src="%ATTACHURLPATH%/Selection_390.png" alt="Selection_390.png" width="419" height="138" />
      1. Right click on the newly installed template and navigate to Advanced->Configure Advanced... <img src="%ATTACHURLPATH%/Selection_404.png" alt="Selection_404.png" width="829" height="357" />
   1. When configuring the agent, ensure to follow the general configuration information regarding the default configuration settings for the agents.

---++ Configuring the Monitoring Agent for CLM Server Monitoring for !WebSphere Application Server (KCH)

It is possible to create an instance of the agent for each application server on the machine. 
We will configure one for the !WebSphere Application Server hosted locally. 
   1. Double click on the template entry for the agent. <img src="%ATTACHURLPATH%/Selection_390.png" alt="Selection_390.png" width="419" height="138" />
   1. Assign a name to the new instance. Put name of !WebSphere server being monitored here. <img src="%ATTACHURLPATH%/Selection_392.png" alt="Selection_392.png" width="351" height="127" />
   1. In the Java configuration window, use the JDK included with the !WebSphere Application Server: eg. C:\Program Files\IBM\WebSphere\AppServer\java
      1. In the JVM Arguments, allocate a maximum of 1G to the agent. ( -Xmx1024) <img src="%ATTACHURLPATH%/Selection_393.png" alt="Selection_393.png" width="709" height="192" />
      1. Click next.
   1. In the !WebSphere Application Server Configuration window, enter the parameters used in the JConsole connection script from the previous section.
   1. Ensure that the WAS base paths include the !WebSphere Application server directory. 
   1. Also ensure that the WAS class path has the correct version of the var for the version of !WebSphere Application Server begin used (look for the version of the file in <WAS_HOME>. 
      * For example: runtimes/com.ibm.ws.admin.client_8.0.0.jar;plugins/com.ibm.ws.security.crypto.jar <img src="%ATTACHURLPATH%/Selection_395.png" alt="Selection_395.png" width="773" height="458" />
   1. Click next.
   1. Add a monitored Application for each domain found in the MBeans tab of JConsole. (ie. team.server.*). The name of the monitored application should be something recognizable for the application being monitored.<img src="%ATTACHURLPATH%/Selection_396.png" alt="Selection_396.png" width="773" height="459" /><img src="%ATTACHURLPATH%/Selection_398.png" alt="Selection_398.png" width="426" height="151" />

---++ Configuring the Monitoring Agent for CLM Server Monitoring (KCD)

It is possible to create an instance of the agent for each application server on the machine. 
We will configure one for the a Tomcat instance hosted locally. 
   1. Double click on the template entry for the agent.<img src="%ATTACHURLPATH%/Selection_399.png" alt="Selection_399.png" width="519" height="131" />
   1. Assign a name to the new instance. Put name of the server being monitored here.<img src="%ATTACHURLPATH%/Selection_392.png" alt="Selection_392.png" width="351" height="127" />
   1. In the Java configuration window, use the jdk used by the Tomcat server: <img src="%ATTACHURLPATH%/Selection_400.png" alt="Selection_400.png" width="755" height="180" />
   1. In the JVM Arguments, allocate a maximum of 1G to the agent. (-Xmx1024) <img src="%ATTACHURLPATH%/Selection_400.png" alt="Selection_400.png" width="755" height="180" />
   1. Click next.
   1. In the “JSR-160-Compliant Server” Configuration window, enter the parameters used when connecting using !JConsole from the previous section. Include any paths or jars required for a secure connection. <img src="%ATTACHURLPATH%/Selection_401.png" alt="Selection_401.png" width="754" height="418" />
   1. Click next.
   1. Add a monitored Application for each domain found in the !MBeans tab of !JConsole. (ie. team.server.*). The name of the monitored application should be something recognizable for the application being monitored. <img src="%ATTACHURLPATH%/Selection_402.png" alt="Selection_402.png" width="754" height="233" /> <img src="%ATTACHURLPATH%/Selection_403.png" alt="Selection_403.png" width="516" height="152" />

---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]], [[DeploymentWebHome][Deployment web home]]

---+++++!! External links:          

   * [[https://www.ibm.com][IBM]]

---+++++!! Additional contributors: Main.TWikiUser, Main.TWikiUser

<sticky></div></sticky>

   * [[%ATTACHURL%/KCH.zip][KCH.zip]]: Configuring the Monitoring Agent for CLM Server Monitoring for !WebSphere Application Server (KCH) (zip)

   * [[%ATTACHURL%/KCH.tgz][KCH.tgz]]: Configuring the Monitoring Agent for CLM Server Monitoring for !WebSphere Application Server (KCH) (tgz)

   * [[%ATTACHURL%/KCD.zip][KCD.zip]]: Configuring the Monitoring Agent for CLM Server Monitoring (KCD) (zip)

Attachments

Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
zip	KCD.zip	manage	23877.6 K	2013-11-15 - 20:34	UnknownUser	Configuring the Monitoring Agent for CLM Server Monitoring (KCD) (zip)
tgz	KCH.tgz	manage	23680.5 K	2013-11-15 - 20:31	UnknownUser	Configuring the Monitoring Agent for CLM Server Monitoring for WebSphere Application Server (KCH) (tgz)
zip	KCH.zip	manage	23895.8 K	2013-11-15 - 20:29	UnknownUser	Configuring the Monitoring Agent for CLM Server Monitoring for WebSphere Application Server (KCH) (zip)
png	Selection_387.png	manage	1.0 K	2013-11-05 - 15:10	UnknownUser	Manage Tivoli Monitoring Service
png	Selection_390.png	manage	3.6 K	2013-11-05 - 15:13	UnknownUser	Agent Installed
png	Selection_392.png	manage	1.7 K	2013-11-05 - 15:14	UnknownUser	Create Instance
png	Selection_393.png	manage	5.3 K	2013-11-05 - 15:15	UnknownUser	WebSphere Java Settings
png	Selection_395.png	manage	13.7 K	2013-11-05 - 15:17	UnknownUser	WebSphere Server Settings
png	Selection_396.png	manage	6.9 K	2013-11-05 - 15:18	UnknownUser	WebSPhere Create Domain
png	Selection_398.png	manage	4.5 K	2013-11-05 - 15:19	UnknownUser	WebSphere Started Instance
png	Selection_399.png	manage	3.7 K	2013-11-05 - 15:19	UnknownUser	JMX Agent INstalled
png	Selection_400.png	manage	5.1 K	2013-11-05 - 15:20	UnknownUser	Java Settings
png	Selection_401.png	manage	9.4 K	2013-11-05 - 15:20	UnknownUser	JSR160 Settings
png	Selection_402.png	manage	6.0 K	2013-11-05 - 15:21	UnknownUser	Create Domain
png	Selection_403.png	manage	4.1 K	2013-11-05 - 15:22	UnknownUser	Started Instance
png	Selection_404.png	manage	8.8 K	2013-11-05 - 15:22	UnknownUser	ITM Config

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.