(r5) EnablingCLMServerMonitoring < Deployment

~~EditAttach~~Printable

r5 - 2014-02-21 - 14:36:47 - Main.kuschelYou are here: TWiki >

Deployment Web > CLMServerMonitoring > EnablingCLMServerMonitoring

<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%">
---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> Enabling CLM Server Monitoring
%DKGRAY% Authors: Main.BorisKuschel <br>
Build basis: CLM 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>
By default, the CLM Server Monitoring feature is not enabled after installation. To enable the feature, you use JConsole. If you have not done so already, ensure that it is possible to connect with JConsole as described in [[https://jazz.net/wiki/bin/view/Deployment/JazzMonitoringThroughJMX][Jazz monitoring through JMX]].
Depending on what method was used to connect to JConsole, the configuration is located in slightly different information.

For [[https://jazz.net/wiki/bin/view/Deployment/JazzMonitoringThroughJMX#Using_JSR160RMI_Connector_for_JC][WebSphere Application Server production systems]], the !WebSphere Application Server configuration should be followed; otherwise, follow the standard [[https://jazz.net/wiki/bin/view/Deployment/JazzMonitoringThroughJMX#Setting_up_your_Jazz_Team_Server][Enabling CLM Server Monitoring]] instructions.

---++ Enabling CLM Server Monitoring for !WebSphere Application Server

When connecting with JConsole, one or more domains should be listed that correspond to the applications that are installed on !WebSphere Application Server:
<IMAGE>

In all the domains you want to enable for monitoring, navigate to this location:
<verbatim>
team.server.* > Monitoring > {WebSphere Application Server cell} > Configuration > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
</verbatim>
  <img src="%ATTACHURLPATH%/Selection_408.png" alt="Selection_408.png" width="664" height="277" /><br/>
Ensure that the parameters are correct. Specifically, ensure that the =CacheDiskStoreDirectory= contains enough space to accommodate both the =CacheMaxBytesLocalDisk= and =ProblemCacheMaxBytesLocalDisk=. This determines how much information is retained by the CLM Server Monitoring before being evicted.

To collect all user activities, not just those that are problems (this can be memory intensive), set =RegisterActivitywithSession= to =true=. 

To turn on all monitors, set =AllMonitorsEnabled= to =true= and =DiagnosticsEnabled= to =true=.

To enable monitors on a monitor-by-monitor basis, you must navigate to each monitor. (=AllMonitorsEnabled= can be left =false= in this case.)
For each monitor, set =Enabled= to =true= to enable it. You can set the =Threshold= (the default is 10s, an L is required after the number when setting a new value, for example, =5000L= for 5 seconds), which determines how long an execution should take before a problem is created and whether aggregates should be collected. Set =RollupEnabled= to =true=.

These attributes can be found in the monitors in these locations:
<verbatim>
team.server.* > CORBA > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > Cache > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > DB Statement > {WebSphere Application Server cell} > {!WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > HTTP Client Request > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > Pool > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > Request > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > SPARQL > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
team.server.* > Service > {WebSphere Application Server cell} > {WebSphere Application Server node} > {WebSphere Application Server name} > Attributes
</verbatim>
<img src="%ATTACHURLPATH%/Selection_407.png" alt="Selection_407.png" width="213" height="120" /><br/>
---++Enabling CLM Server Monitoring
When you connect with JConsole, one or more domains should be listed that correspond to the applications installed on the application server.
<IMAGE>

In all the domains to enable for monitoring, navigate to this location:
<verbatim>
team.server.*  > Monitoring > Configuration > Attributes
</verbatim>
 <img src="%ATTACHURLPATH%/Selection_410.png" alt="Selection_410.png" width="783" height="314" /><br/>
Ensure that the parameters are correct. Specifically, ensure that the =CacheDiskStoreDirectory= contains enough space to accommodate both the =CacheMaxBytesLocalDisk= and =ProblemCacheMaxBytesLocalDisk=. This determines how much information is retained by the CLM Server Monitoring before being evicted.

To collect all user activities, not just those that are problems (this can be memory intensive), set =RegisterActivitywithSession= to =true=. 

To turn on all monitors, set =AllMonitorsEnabled= to =true= and =DiagnosticsEnabled= to =true=.

To enable monitors on a monitor-by-monitor basis, you must navigate to each monitor (=AllMonitorsEnabled= can be left =false= in this case).
For each monitor, set =Enabled= to =true= to enable. You can set the =Threshold= (the default is 10s, an L is required after the number when setting a new value, for example, =5000L= for 5 seconds), which determines how long an execution should take before a problem is created and whether aggregates should be collected. Set =RollupEnabled= to =true=.

These attributes can be found in the monitors in these locations:
<verbatim>
team.server.* > CORBA > Attributes
team.server.* > Cache > Attributes
team.server.* > DB Statement > Attributes
team.server.* > HTTP Client Request > Attributes
team.server.* > Pool > Attributes
team.server.* > Request > Attributes
team.server.* > SPARQL > Attributes
team.server.* > Service > Attributes
</verbatim>
<img src="%ATTACHURLPATH%/Selection_411.png" alt="Selection_411.png" width="257" height="153" /><br/>

---+++++!! 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>

Attachments

Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
png	Selection_407.png	manage	2.6 K	2013-10-27 - 16:12	UnknownUser	WebSphere MBean Monitor Configuration
png	Selection_408.png	manage	11.1 K	2013-10-27 - 16:10	UnknownUser	WebSphere MBean CLM Server Configuration
png	Selection_410.png	manage	50.2 K	2013-10-27 - 16:11	UnknownUser	MBean CLM Server Configuration
png	Selection_411.png	manage	8.5 K	2013-10-27 - 16:13	UnknownUser	MBean Monitor Configuration

Deployment

Community information and contribution guidelines

Status icon key:

To do
Under construction
New
Updated
Constant change
None - stable page

Smaller versions of status icons for inline text:

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.