advertisement
▼
Scroll to page 2
of 700
Tivoli ITCAM for Application Diagnostics
®
Version 7.1
User Guide
SC27-2817-00
Tivoli ITCAM for Application Diagnostics
®
Version 7.1
User Guide
SC27-2817-00
Note
Before using this information and the product it supports, read the information in “Notices” on page 681.
Edition Notice
This December 2009 edition applies to Version 7.1 of ITCAM for Application Diagnostics and all subsequent releases
and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2006, 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this guide . . . . . . . . . . . ix
Who should read this guide .
Publications . . . . . .
Accessibility . . . . . .
Tivoli technical training . .
Supporting information . .
Conventions used in this guide
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ix
ix
xi
xi
xi
xi
Part 1. Part 1: Introduction to ITCAM
for Application Diagnostics . . . . . 1
Chapter 1. Overview of ITCAM for
Application Diagnostics . . . . . . . . 3
ITCAM for Application Diagnostics functionality . . 3
ITCAM for Application Diagnostics user interfaces . 4
Components used by the Tivoli Enterprise Portal user
interface . . . . . . . . . . . . . . . . 5
The Agents . . . . . . . . . . . . . . 5
IBM Tivoli Monitoring components . . . . . . 6
Components used by the MSVE user interface . . . 8
Tivoli Enterprise Portal interoperation with MSVE
10
What's new in the 7.1 release? . . . . . . . . 11
Getting Started with ITCAM for Application
Diagnostics . . . . . . . . . . . . . . 11
Chapter 2. Scenarios. . . . . . . . . 13
Scenario 1: Diagnosing a memory leak . . . .
Scenario 2: Diagnosing hanging transactions . .
Scenario 3: Diagnosing a WebSphere server
shutdown . . . . . . . . . . . . . .
Scenario 4: Determining if the WebSphere cluster
needs to be load balanced . . . . . . . .
Scenario 5: Determining the cause of high response
times . . . . . . . . . . . . . . .
Scenario 6: Determining the cause of connection
problems . . . . . . . . . . . . . .
Scenario 7: Determining if the Garbage Collection
policy needs to be adjusted . . . . . . . .
Scenario 8: Troubleshooting application response
time in an XD cell . . . . . . . . . . .
Scenario 9: Ensuring that jobs processed by
Compute Grid don't execute for longer than one
hour . . . . . . . . . . . . . . . .
. 13
. 15
. 19
. 20
. 23
. 28
. 29
. 31
. 34
Part 2. Part 2: Using ITCAM for
Application Diagnostics . . . . . . 37
Chapter 3. ITCAM for Application
Diagnostics Managing Server
Visualization Engine . . . . . . . . . 39
Access the Managing Server Visualization Engine
from Tivoli Enterprise Portal . . . . . . .
Account management . . . . . . . . . .
© Copyright IBM Corp. 2006, 2009
. 39
. 43
User Scenarios . . . . . . . . . . . . 43
User profiles . . . . . . . . . . . . . 44
Role configuration . . . . . . . . . . . 46
Server management . . . . . . . . . . . 49
User Scenarios . . . . . . . . . . . . 49
Server groups . . . . . . . . . . . . 49
Data Collector Configuration . . . . . . . 52
Data Collector Profiles . . . . . . . . . . 61
Monitoring on Demand (TM) . . . . . . . . 73
User Scenarios . . . . . . . . . . . . 74
MOD Console . . . . . . . . . . . . 74
Schedule Management. . . . . . . . . . 75
Creating a schedule. . . . . . . . . . . 75
Applying a schedule . . . . . . . . . . 76
Overriding a monitoring level . . . . . . . 77
Modifying a schedule . . . . . . . . . . 77
Deleting a schedule. . . . . . . . . . . 78
Duplicating a schedule . . . . . . . . . 78
Managing server. . . . . . . . . . . . . 78
System properties . . . . . . . . . . . 79
Self-diagnosis. . . . . . . . . . . . . 82
Systems overview . . . . . . . . . . . . 84
User Scenarios . . . . . . . . . . . . 84
User Scenarios . . . . . . . . . . . . 85
Enterprise Overview . . . . . . . . . . 85
Group Overview . . . . . . . . . . . 86
Server Overview. . . . . . . . . . . . 86
Portal Overview . . . . . . . . . . . . 88
Viewing the Portal Page Summary. . . . . . 88
Viewing the Portlet Summary . . . . . . . 89
WLM associated service class summary . . . . 90
WLM associated service class period detail . . . 91
Viewing a WLM enclave . . . . . . . . . 91
Server Statistics Overview . . . . . . . . . 92
Configuring the Server Statistics Overview page 93
Viewing the Server Statistics Overview . . . . 94
Recent Activity Display . . . . . . . . . . 95
User Scenarios . . . . . . . . . . . . 95
Creating a Recent Activity report . . . . . . 95
System resources . . . . . . . . . . . . 96
User Scenarios . . . . . . . . . . . . 96
Viewing the System Resources Browser . . . . 96
Resources Performance Metrics . . . . . . . 97
SMF data . . . . . . . . . . . . . . . 104
User Scenarios . . . . . . . . . . . . 105
Viewing SMF data. . . . . . . . . . . 105
Alerts and Events . . . . . . . . . . . . 106
Escalating alerts and events to the Problem
Center . . . . . . . . . . . . . . . 107
Problem Center. . . . . . . . . . . . . 107
Viewing the details of a problem . . . . . . 109
Adding a problem manually . . . . . . . 111
Closing a problem . . . . . . . . . . . 111
In-flight request search . . . . . . . . . . 112
User Scenarios . . . . . . . . . . . . 112
Searching for an Application Request . . . . 113
iii
Sorting search results . . . . . . . . .
Server Activity Display . . . . . . . . .
User Scenarios . . . . . . . . . . .
Server Activity Display - active requests . .
Server Activity Display - recent requests . .
Server Activity Display - lock contentions . .
Viewing request detail . . . . . . . .
Suspending a thread . . . . . . . . .
Activating a thread . . . . . . . . .
Canceling a request . . . . . . . . .
Changing a thread's priority . . . . . .
Viewing a Stack Trace . . . . . . . .
Viewing a Method/Component Trace - flow
view . . . . . . . . . . . . . .
Viewing a request object and session object .
Searching a Method/Component Trace . . .
E-mailing a PDF file - SAD . . . . . . .
Viewing a PDF file - SAD . . . . . . .
Exporting to a file - SAD . . . . . . .
Web Session Browser . . . . . . . . . .
Viewing the Web Session Browser . . . .
Memory diagnosis. . . . . . . . . . .
User Scenarios . . . . . . . . . . .
Heap Dump Management . . . . . . .
Memory Analysis . . . . . . . . . .
Heap Analysis . . . . . . . . . . .
Memory Leak . . . . . . . . . . .
JVM thread display . . . . . . . . . .
User Scenarios . . . . . . . . . . .
Changing a JVM thread's priority . . . .
Viewing a stack trace . . . . . . . . .
Canceling a thread . . . . . . . . .
Viewing a thread dump . . . . . . . .
Trap and alert management . . . . . . .
User Scenario . . . . . . . . . . .
Setting an Application trap . . . . . . .
Setting an Application trap using the Resident
Time - Misbehaving Transaction target type .
Setting a Server Resource trap . . . . . .
Activating a trap . . . . . . . . . .
Deactivating a trap . . . . . . . . .
Modifying a trap . . . . . . . . . .
Duplicating a trap . . . . . . . . . .
Deleting a trap . . . . . . . . . . .
Viewing the trap action history . . . . .
Setting alert actions and data actions . . .
Software consistency check . . . . . . . .
User Scenarios . . . . . . . . . . .
Installed Binary Comparison . . . . . .
Installed Binary Check . . . . . . . .
Runtime Environment Comparison . . . .
Runtime Environment Check . . . . . .
Performance analysis and reporting . . . . .
User Scenarios . . . . . . . . . . .
Defining reports . . . . . . . . . .
Report management . . . . . . . . .
Method Profiling . . . . . . . . . .
Daily Statistics . . . . . . . . . . . .
Viewing the Daily Statistics Overview . . .
Deleting Daily Statistics . . . . . . . .
Custom requests . . . . . . . . . . .
iv
ITCAM for Application Diagnostics: User Guide
.
.
.
.
.
.
.
.
.
.
.
.
113
114
114
115
117
118
119
120
120
121
121
122
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
122
123
123
124
125
125
125
126
126
127
127
131
131
132
135
136
137
137
138
138
139
140
140
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
143
145
147
148
148
149
149
150
150
152
152
152
154
154
155
155
155
156
169
175
176
176
177
177
Types of requests . . . . . . . . . .
Creating custom requests . . . . . . .
Viewing custom requests . . . . . . .
Composite requests . . . . . . . . . .
User Scenarios . . . . . . . . . . .
The scope of composite requests . . . . .
Composite requests involving CICS and IMS
systems . . . . . . . . . . . . .
Locate, view, and analyze composite requests
Viewing composite requests . . . . . .
Audit trails . . . . . . . . . . . . .
User Scenarios . . . . . . . . . . .
Accessing the user audit trail . . . . . .
Request Mapper . . . . . . . . . . .
Purpose . . . . . . . . . . . . .
Data used by the Request Mapper . . . .
Default request mapping behavior . . . .
Configuring a Request Mapper . . . . .
.
.
.
.
.
.
178
178
181
181
182
182
. 184
186
. 188
. 194
. 194
. 194
. 194
. 194
. 195
. 196
. 197
Chapter 4. ITCAM Agent for
WebSphere . . . . . . . . . . . . 201
About this publication . . . . . . . . . .
ITCAM for Application Diagnostics - WebSphere
Agent workspaces . . . . . . . . . . . .
Organization of the predefined workspaces . .
Summary workspaces . . . . . . . . .
Summary Workspace Views . . . . . . .
WebSphere Agent Summary workspace . . .
WebSphere Agent Summary Status workspace
Application Server Summary workspace . . .
Resources and Applications workspaces . . .
Situation Mapping and Summary Workspaces
Summary Workspaces error messages . . . .
Configuration workspaces . . . . . . . .
Workspace link to Managing Server
Visualization Engine . . . . . . . . . .
Alarm Manager workspace . . . . . . . .
Allocation Failures workspace . . . . . . .
Selected Application - Application Trend at L1
workspace . . . . . . . . . . . . .
Selected Application - Application Trend at
L2/L3 workspace . . . . . . . . . . .
Application Health workspace. . . . . . .
Application Registry workspace . . . . . .
Cache Analysis workspace . . . . . . . .
Client Communications workspace . . . . .
Container Object Pools workspace . . . . .
Container Transactions workspace . . . . .
Data sources workspace . . . . . . . . .
DB Connection Pools workspace . . . . . .
DCS Stacks workspace . . . . . . . . .
Destinations workspace . . . . . . . . .
Durable Subscriptions workspace. . . . . .
EJB Containers workspace . . . . . . . .
Enterprise Java Beans workspace . . . . . .
Garbage Collections - Selected Allocation Failure
workspace . . . . . . . . . . . . .
Garbage Collection Analysis workspace . . .
High Availability Manager workspace . . . .
IMAP/POP workspace . . . . . . . . .
J2C Connection Pools workspace . . . . . .
203
203
203
212
213
214
215
215
217
218
221
221
225
235
236
237
237
238
239
240
241
242
243
243
246
248
249
249
250
252
253
254
255
256
257
JMS Summary workspace . . . . . . . .
JVM Stack Trend workspace . . . . . . .
Log Analysis workspace . . . . . . . . .
Lotus Workplace Server workspace . . . . .
Messages Queues workspace . . . . . . .
Messaging Engine Communications workspace
Messaging Engines workspace. . . . . . .
OS Stack workspace . . . . . . . . . .
Pool Analysis workspace . . . . . . . .
Portal Pages Summary workspace . . . . .
Portal Summary workspace . . . . . . .
Portlet Summary workspace . . . . . . .
Request Analysis workspace . . . . . . .
Request Baseline workspace . . . . . . .
EJB Tier Analysis workspace . . . . . . .
Application Configuration workspace . . . .
Backend Tier Analysis workspace . . . . .
Application Health History workspace . . . .
Web Tier Analysis workspace . . . . . . .
Selected Datasources - Datasource Trend
workspace . . . . . . . . . . . . .
Selected Request - Data sources workspace . .
Selected Request - JMS Queues workspace . .
Selected Request - Portal Processing workspace
Selected Request - Resource Adapters
workspace . . . . . . . . . . . . .
Service Component Elements workspace . . .
Service Components workspace . . . . . .
Servlets/JSPs - Selected Enterprise Application
workspace . . . . . . . . . . . . .
Scheduler workspace . . . . . . . . . .
Sessions workspace . . . . . . . . . .
Thread Pools workspace. . . . . . . . .
Thread Pool Trend workspace . . . . . . .
Web Applications workspace . . . . . . .
Web Services workspace. . . . . . . . .
WebSphere Agent workspace . . . . . . .
WebSphere Application Server workspace . . .
WebSphere ESB Server workspace . . . . .
WebSphere Portal Server workspace . . . . .
WebSphere Process Server workspace . . . .
WMQ Client Link Communications workspace
WMQ Link Communications workspace . . .
Workload Management workspace . . . . .
Workplace Mail workspace . . . . . . . .
Region workspaces in a z/OS environment . .
ITCAM for Application Diagnostics- WebSphere
Agent attributes . . . . . . . . . . . .
Attribute groups used by the predefined
workspaces . . . . . . . . . . . . .
Alarm Manager attributes . . . . . . . .
Allocation Failure attributes . . . . . . .
Application Health Status attributes . . . . .
Application Monitoring Configuration attributes
Application Server Status attributes . . . . .
Application Server attributes . . . . . . .
Baseline attributes . . . . . . . . . . .
Client Communications attributes . . . . .
Container Object Pools attributes . . . . . .
Container Transactions attributes . . . . . .
Data sources attributes . . . . . . . . .
259
260
261
262
262
263
264
265
266
267
268
269
270
272
273
274
274
275
276
277
278
278
279
279
280
281
282
283
284
285
286
287
288
290
291
292
293
293
294
295
296
297
298
301
301
303
305
307
309
311
314
316
318
325
327
330
DB Connection Pools attributes . . . . . .
DC Messages attributes . . . . . . . . .
DCS Stack attributes . . . . . . . . . .
Durable Subscriptions attributes . . . . . .
Dynamic Cache attributes . . . . . . . .
Dynamic Cache Templates attributes . . . .
EJB Containers attributes . . . . . . . .
Enterprise Java Beans attributes . . . . . .
Garbage Collection Analysis attributes . . . .
Garbage Collection Cycle attributes . . . . .
High Availability Manager attributes . . . .
J2C Connection Pools attributes . . . . . .
JMS Summary attributes. . . . . . . . .
Log Analysis attributes . . . . . . . . .
Messaging Engine Communications attributes
Messaging Engines attributes . . . . . . .
Portal Page Summary attributes . . . . . .
Portal Summary attributes . . . . . . . .
Portlet Summary attributes . . . . . . . .
Queue attributes . . . . . . . . . . .
Remote Configuration Requests attributes . . .
Request Analysis attributes . . . . . . . .
Requests Monitoring Configuration attributes
Request Times and Rates attributes . . . . .
Selected Request attributes . . . . . . . .
Servlet Sessions attributes . . . . . . . .
Servlets JSPs attributes . . . . . . . . .
Scheduler attributes . . . . . . . . . .
Service Component Elements attributes. . . .
Service Components attributes. . . . . . .
Thread Pools attributes . . . . . . . . .
Topic Spaces attributes . . . . . . . . .
Web Applications attributes. . . . . . . .
Web Services attributes . . . . . . . . .
Web Services Gate Way attributes . . . . .
WebSphere Agent Events attributes . . . . .
WMQ Client Link Communications attributes
WMQ Link Communications attributes . . . .
Workload Management Client attributes . . .
Workload Management Server attributes . . .
Workplace Mail IMAP/POP attributes . . . .
Workplace Mail Queues attributes . . . . .
Workplace Mail Service attributes . . . . .
ITCAM for Application Diagnostics - WebSphere
Agent situations . . . . . . . . . . . .
Predefined situations-descriptions and formulas
(that run automatically) . . . . . . . . .
Predefined situations descriptions and formulas
(that run manually) . . . . . . . . . .
ITCAM for Application Diagnostics - WebSphere
Agent Take Action commands . . . . . . . .
Add_XD_Cell: Add an XD Cell to a WebSphere
agent . . . . . . . . . . . . . . .
Enable_Auto_Threshold: set threshold
parameters . . . . . . . . . . . . .
Override_Auto_Threshold: override threshold
values . . . . . . . . . . . . . . .
Remove_WebSphere_SubNode: Remove an
inactive WebSphere application server . . . .
Set_Application_Monitoring: Set monitoring . .
Contents
333
336
338
340
343
344
348
352
356
358
360
362
366
369
370
373
374
376
378
379
382
383
388
391
392
395
399
401
403
405
406
409
411
414
416
417
418
420
423
425
428
429
431
433
434
438
445
445
445
448
448
449
v
Set_Completion_Thresholds: Set completion
thresholds . . . . . . . . . . . . .
Set_Request_Sampling_Rate: Set the sampling
rate for request data . . . . . . . . . .
Start_Baselining: start the baselining process . .
Start_GC_Monitoring: Begin reporting
garbage-collection data . . . . . . . . .
Start_Request_Monitoring : Begin reporting
request data . . . . . . . . . . . . .
Start_Resource_Monitoring: Begin reporting PMI
data . . . . . . . . . . . . . . .
Start_WebSphere_Server: Start a WebSphere
application server . . . . . . . . . . .
Stop_Baselining: stop the baselining process . .
Stop_GC_Monitoring: Stop reporting
garbage-collection data . . . . . . . . .
Stop_Request_Monitoring: Stop reporting
request data . . . . . . . . . . . . .
Stop_Resource_Monitoring: Stop reporting PMI
data . . . . . . . . . . . . . . .
Stop_WebSphere_Server: Stop a WebSphere
application server . . . . . . . . . . .
Update_Baseline: trigger a baseline update . .
Threshold calculation detail . . . . . . .
ITCAM for Application Diagnostics - WebSphere
XD Overview . . . . . . . . . . . . .
WebSphere XD Cell Monitoring Prerequisites
Configure WebSphere XD Cell monitoring. . .
ITCAM for Application Diagnostics WebSphere XD Cell workspaces . . . . . .
ITCAM for Application Diagnostice WebSphere XD Cell Attributes. . . . . . .
Compute Grid Attributes . . . . . . . .
ITCAM for Application Diagnostics WebSphere XD Take Actions . . . . . . .
ITCAM for Application Diagnostics - XD Agent
situations . . . . . . . . . . . . . .
450
450
450
451
451
452
452
452
453
453
453
453
454
454
456
457
457
460
475
475
486
487
Chapter 5. ITCAM Agent for J2EE. . . 493
ITCAM for Application Diagnostics - Agent for
J2EE workspaces . . . . . . . . . . . .
Organization of the predefined workspaces . .
Allocation Failures workspace . . . . . . .
Application Health Summary workspace . . .
Application Registry workspace . . . . . .
BEA WebLogic Application Server workspace
Data sources workspace . . . . . . . . .
DB Connection Pools workspace . . . . . .
DC Message Events workspace . . . . . .
EJB Components workspace . . . . . . .
Enterprise Java Beans workspace . . . . . .
EJB Modules workspace . . . . . . . . .
EJBs - Selected Enterprise Application
workspace . . . . . . . . . . . . .
Garbage Collection Analysis workspace . . .
Garbage Collections - Selected Allocation Failure
workspace . . . . . . . . . . . . .
J2EE Agent workspace . . . . . . . . .
J2SE Application workspace . . . . . . .
JBoss App Server workspace . . . . . . .
JCA Connection Pools workspace. . . . . .
vi
ITCAM for Application Diagnostics: User Guide
495
495
500
501
502
503
503
504
505
506
507
508
509
509
510
510
511
512
513
JDBC Connection Pools workspace . . . . .
JMS Sessions workspace . . . . . . . . .
JMS Summary workspace . . . . . . . .
JTA Resources workspace . . . . . . . .
JTA Summary workspace . . . . . . . .
JVM Statistics workspace . . . . . . . .
Log Analysis workspace . . . . . . . . .
Oracle App Server workspace . . . . . . .
Request Analysis workspace . . . . . . .
Selected Request - Baseline workspace . . . .
Selected Application - Application Tier Analysis
workspace . . . . . . . . . . . . .
Selected Application - Configuration workspace
Selected Application - Backend Tier Analysis
workspace . . . . . . . . . . . . .
Selected Application - Health History workspace
Selected Application - Client Tier Analysis
workspace . . . . . . . . . . . . .
Selected Request - Data sources workspace . .
Selected Request - JMS Queues workspace . .
Selected Request - Resource Adapters
workspace . . . . . . . . . . . . .
SAP NetWeaver Server workspace . . . . .
Servlets/JSPs - Selected Enterprise Application
workspace . . . . . . . . . . . . .
Servlets/JSPs - Selected Web Application
workspace . . . . . . . . . . . . .
Tomcat Server workspace . . . . . . . .
Web Applications workspace . . . . . . .
Web Container workspace . . . . . . . .
WebSphere App Server CE workspace . . . .
ITCAM for Application Diagnostics - Agent for
J2EE attributes . . . . . . . . . . . . .
Attribute groups used by the predefined
workspaces . . . . . . . . . . . . .
Allocation Failure - J2EE attributes . . . . .
Application Health Status attributes . . . . .
Application Monitoring Configuration attributes
Application Server Status - J2EE attributes. . .
Application Server - J2EE attributes . . . . .
Baseline attributes . . . . . . . . . . .
Data sources - J2EE attributes . . . . . . .
DB Connection Pools - NetWeaver attributes
DC Messages - J2EE attributes. . . . . . .
Enterprise Java Bean Components - WebLogic
attributes . . . . . . . . . . . . . .
Enterprise Java Bean Modules - J2EE attributes
Enterprise Java Bean Service - NetWeaver
attributes . . . . . . . . . . . . . .
Enterprise Java Beans - WebLogic attributes . .
Garbage Collection Analysis - J2EE attributes
Garbage Collection Cycle - J2EE attributes. . .
J2EE Agent Events attributes . . . . . . .
J2EE Connector Connection Pools - WebLogic
attributes . . . . . . . . . . . . . .
JCA Connection Pools - J2EE attributes . . . .
JDBC Connection Pools - WebLogic attributes
JDK - Operation System attributes . . . . .
JDK - Memory attributes . . . . . . . .
JDK - JVM attributes . . . . . . . . . .
JDK - Threading attributes . . . . . . . .
514
515
515
516
517
517
518
519
519
520
521
522
522
523
524
525
525
526
526
527
528
528
529
530
531
531
532
533
535
537
540
541
543
545
547
548
550
551
553
555
557
559
562
563
565
566
568
570
571
573
JMS Sessions - WebLogic attributes . . . . .
JMS Summary - J2EE attributes . . . . . .
Java Transaction Service - WebLogic attributes
JTA Resources - J2EE attributes . . . . . .
JTA Summary - NetWeaver attributes . . . .
Log Analysis - J2EE attributes . . . . . . .
Request Analysis - J2EE attributes . . . . .
Requests Monitoring Configuration attributes
Request Times and Rates - J2EE attributes . . .
Selected Request - J2EE attributes . . . . .
Servlets JSPs - J2EE attributes . . . . . . .
Servlets and JSPs - WebLogic attributes. . . .
Web Container - NetWeaver attributes . . . .
Web Applications - J2EE attributes . . . . .
Web Applications - WebLogic attributes . . .
ITCAM for Application Diagnostics - Agent for
J2EE situations . . . . . . . . . . . . .
ITCAM for Application Diagnostics - Agent for
J2EE Take Action commands . . . . . . . .
Enable_Auto_Threshold: set threshold
parameters . . . . . . . . . . . . .
Override_Auto_Threshold: override threshold
values . . . . . . . . . . . . . . .
Recycle_Application_Server: Recycle a J2EE
application . . . . . . . . . . . . .
Remove_J2EE_Application: Remove a J2EE
Application . . . . . . . . . . . . .
Remove_J2EE_SubNode: Remove an inactive
J2EE application server . . . . . . . . .
Set_Application_Monitoring: Set monitoring . .
Set_Completion_Thresholds: Set completion
thresholds . . . . . . . . . . . . .
Set_Request_Sampling_Rate: Set the sampling
rate for request data . . . . . . . . . .
Start_Application_Server: Start a J2EE
application server . . . . . . . . . . .
Start_Baselining: start the baselining process . .
Start_GC_Monitoring: Begin reporting
garbage-collection data . . . . . . . . .
Start_Request_Monitoring : Begin reporting
request data . . . . . . . . . . . . .
Start_Resource_Monitoring: Begin reporting PMI
data . . . . . . . . . . . . . . .
Stop_Application_Server: Stop a J2EE
application server . . . . . . . . . . .
Stop_Baselining: stop the baselining process . .
Stop_GC_Monitoring: Stop reporting
garbage-collection data . . . . . . . . .
Stop_Request_Monitoring: Stop reporting
request data . . . . . . . . . . . . .
574
576
578
581
582
583
585
590
592
594
596
598
599
601
602
603
607
607
609
610
610
611
611
612
612
612
613
614
614
614
614
615
615
Stop_Resource_Monitoring: Stop reporting PMI
data . . . . . . . . . . . . . . . 615
Update_Baseline: trigger a baseline update . . 615
Threshold calculation detail . . . . . . . 616
Chapter 6. ITCAM Agent for HTTP
Servers . . . . . . . . . . . . . . 619
ITCAM for Application Diagnostics - Web Servers
Agent workspaces . . . . . . . . . . .
Organization of the predefined workspaces .
Apache Web Server workspace . . . . .
Apache Web Sites workspace . . . . . .
ASP Overview workspace . . . . . . .
IIS Web Sites workspace . . . . . . . .
Microsoft IIS Web Server workspace . . . .
Sun Java System Web Server workspace . .
Sun Web Sites workspace . . . . . . .
Web Server Agent workspace . . . . . .
ITCAM for Application Diagnostics - Agent for
HTTP Servers attributes . . . . . . . . .
Attribute groups used by the predefined
workspaces . . . . . . . . . . . .
Apache Web Server attributes . . . . . .
Apache Web Sites attributes . . . . . .
IIS Web Server attributes . . . . . . .
IIS Web Sites attributes . . . . . . . .
Sun Web Server attributes . . . . . . .
Sun Web Sites attributes . . . . . . . .
HTTP Servers Agent Events attributes . . .
Web Servers Status attributes . . . . . .
ITCAM for Application Diagnostics - Agent for
HTTP Servers situations . . . . . . . . .
ITCAM for Application Diagnostics - Agent for
HTTP Servers Take Action commands . . . .
.
.
.
.
.
.
.
.
.
.
619
620
620
621
622
622
623
624
625
625
. 626
.
.
.
.
.
.
.
.
.
626
627
628
630
633
636
639
642
643
. 644
. 651
Part 3. Appendixes . . . . . . . . 657
Appendix. Appendix A. WebSphere
PMI Attribute Mapping . . . . . . . 659
Index . . . . . . . . . . . . . . . 675
Trademarks . . . . . . . . . . . . 679
Notices . . . . . . . . . . . . . . 681
615
Contents
vii
viii
ITCAM for Application Diagnostics: User Guide
About this guide
This book provides a user guide for ITCAM for Application Diagnostics 7.1.
Who should read this guide
This user guide is intended for end users of ITCAM for Application Diagnostics.
Publications
This section lists publications in the ITCAM for Application Diagnostics library
and related documents.
ITCAM for Application Diagnostics library
The following publications are included in the ITCAM for Application Diagnostics
library, available at ITCAM for Application Diagnostics Information Center:
v IBM Tivoli Composite Application Manager for Application Diagnostics: Prerequisites
Provides the hardware and software requirements for installing ITCAM for
Application Diagnostics components.
v IBM Tivoli Composite Application Manager for Application Diagnostics: User's Guide
Provides the user overview, user scenarios, and Helps for every ITCAM for
Application Diagnostics component.
v IBM Tivoli Composite Application Manager for Application Diagnostics: Planning an
Installation
Provides the user with a first reference point for a new ITCAM for Application
Diagnostics installation or upgrade.
v ITCAM Agent for WebSphere® Applications Installation and Configuration
Guides:
– IBM Tivoli Composite Application Manager: Agent for WebSphere Applications
Installation and Configuration Guide
– IBM Tivoli Composite Application Manager: Agent for WebSphere Applications
Installation and Configuration Guide for z/OS
– IBM Tivoli Composite Application Manager: Agent for WebSphere Applications Data
Collector Installation and Configuration Guide for IBM i
Provide installation instructions for setting up and configuring ITCAM Agent for
WebSphere Applications on distributed, z/OS®, and IBM® i systems.
v ITCAM Agent for J2EE Applications Installation and Configuration Guides:
– IBM Tivoli Composite Application Manager: Agent for J2EE Data Collector
Installation and Configuration Guide
– IBM Tivoli Composite Application Manager: Agent for J2EE Monitoring Agent
Installation and Configuration Guide
Provide installation instructions for setting up and configuring ITCAM Agent for
J2EE.
v IBM Tivoli Composite Application Manager: Agent for HTTP Servers Installation and
Configuration Guide
Provides installation instructions for setting up and configuring ITCAM Agent
for HTTP Servers.
© Copyright IBM Corp. 2006, 2009
ix
v IBM Tivoli Composite Application Manager for Application Diagnostics Managing
Server Installation Guide
Provides installation instructions for setting up and configuring ITCAM for
Application Diagnostics Managing Server.
v IBM Tivoli® Composite Application Manager for Application Diagnostics:
Troubleshooting Guide
Provides instructions on problem determination and troubleshooting for ITCAM
for Application Diagnostics.
v IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging
Guide
Provides information about system messages received when installing and using
ITCAM for Application Diagnostics.
Accessing publications online
The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.
IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by viewing the Tivoli
software library at the following Web address:
http://www.ibm.com/software/tivoli/library/
Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that enables Adobe® Reader to print letter-sized pages
on your local paper.
The IBM Software Support Web site provides the latest information about known
product limitations and workarounds in the form of technotes for your product.
You can view this information at the following Web site:
http://www.ibm.com/software/support
Ordering publications
You can order many Tivoli publications online at the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/ publications/cgibin/
pbi.cgi
You can also order by telephone by calling one of these numbers:
v In the United States: 800-879-2755
v In Canada: 800-426-4968
In other countries, contact your software account representative to order Tivoli
publications. To locate the telephone number of your local representative, perform
the following steps:
1. Go to the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/
pbi.cgi
2. Select your country from the list and click Go.
x
ITCAM for Application Diagnostics: User Guide
3. Click About this site in the main panel to see an information page that
includes the telephone number of your local representative.
Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate most features of the graphical
user interface.
Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:
http://www.ibm.com/software/tivoli/education/
Supporting information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
v Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
v Obtaining fixes: You can locate the latest fixes that are already available for your
product.
v Contacting IBM Software Support: If you still cannot solve your problem, and
you need to work with someone from IBM, you can use a variety of ways to
contact IBM Software Support.
Conventions used in this guide
This guide uses several conventions for special terms and actions, and
operating-system-dependent commands and paths.
Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip, and Operating system considerations)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words (for example, "Use the word that to introduce a
restrictive clause.")
v New terms in text (except in a definition list)
v Variables and values you must provide
About this guide
xi
Monospace
v Code and other examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options
Operating-system-dependent variables and paths
The publications in this library use the UNIX® convention for specifying
environment variables and for directory notation.
When using the Windows® command line, replace $variable with %variable% for
environment variables and replace each forward slash (/) with a backslash (\) in
directory paths. The names of environment variables are not always the same in
Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in
UNIX.
Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.
Tivoli command syntax
The following special characters define Tivoli command syntax:
[]
Identifies elements that are optional. Required elements do not have
brackets around them.
...
Indicates that you can specify multiple values for the previous element.
Separate multiple values by a space, unless otherwise directed by
command information.
If the ellipsis for an element follows a closing bracket, use the syntax
within the brackets to specify multiple values. For example, to specify two
administrators for the option [–a admin]..., use –a admin1 –a admin2.
If the ellipsis for an element is within the brackets, use the syntax of the
last element to specify multiple values. For example, to specify two hosts
for the option [–h host...], use –h host1 host2.
|
Indicates mutually exclusive information. You can use the element on
either the left or right of the vertical bar.
{}
Delimits a set of mutually exclusive elements when a command requires
one of them. Brackets ([ ]) are around elements that are optional.
In addition to the special characters, Tivoli command syntax uses the typeface
conventions described in “Typeface conventions” on page xi. The following
examples illustrate the typeface conventions used in Tivoli command syntax:
v wcrtpr [–a admin]... [–s region] [–m resource]... name
The name argument is the only required element for the wcrtpr command. The
brackets around the options indicate they are optional. The ellipses after the –a
admin resource option means that you can specify multiple administrators
multiple times. The ellipses after the –m resource option means that you can
specify multiple resources multiple times.
v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}
xii
ITCAM for Application Diagnostics: User Guide
The –f, –i, and object elements are mutually exclusive. Braces that surround
elements indicate that you are including a required element. If you specify the
object argument, you can specify more than one object.
About this guide
xiii
xiv
ITCAM for Application Diagnostics: User Guide
Part 1. Part 1: Introduction to ITCAM for Application
Diagnostics
© Copyright IBM Corp. 2006, 2009
1
2
ITCAM for Application Diagnostics: User Guide
Chapter 1. Overview of ITCAM for Application Diagnostics
IBM Tivoli Composite Application Manager (ITCAM) for Application Diagnostics
is a monitoring, diagnostics, and management technology for WebSphere, J2EE,
and HTTP servers in a distributed environment. ITCAM for Application
Diagnostics also provides enhanced support for monitoring Virtual Enterprise and
Compute Grid products from the WebSphere XD (Extended Deployment) suite.
ITCAM for Application Diagnostics helps to maintain and improve the availability
and performance of on-demand applications in your environment. It helps you to
quickly locate in real time, the source of bottlenecks in application code, server
resources, and external system dependencies.
ITCAM for Application Diagnostics can monitor application servers and HTTP
servers at different levels. Monitoring applications incurs an unavoidable cost in
terms of processing time. To minimize this cost, there are multiple monitoring
levels available. A minimum amount of information is collected during standard
operations. As problems are encountered, the level of information that is collected
can be gradually increased until the problem is located and solved.
ITCAM for Application Diagnostics functionality
ITCAM for Application Diagnostics can perform monitoring, diagnostics, and
management functions for WebSphere, J2EE, and HTTP servers.
Monitoring
ITCAM for Application Diagnostics can monitor the following WebSphere, J2EE,
and HTTP servers:
v WebSphere servers
– WebSphere Application Server (Network Deployment)
– WebSphere Application Server (Extended Deployment)
– WebSphere Process Server
– WebSphere Portal Server
– WebSphere ESB Server
v J2EE servers
–
–
–
–
–
–
–
SAP Net Weaver
Oracle Application Server
JBoss Application Server
Apache Tomcat
BEA WebLogic Server
WebSphere Application Server CE
J2SE
– WebLogic Portal Server
– Sun Java™ System Application Server Enterprise Edition
v HTTP servers
– Apache Web Server
– IIS Web Server
– IBM HTTP Server
© Copyright IBM Corp. 2006, 2009
3
– Sun Java System Web Server
Diagnosing
Use ITCAM for Application Diagnostics to diagnose the following problems in
your On-Demand application environment:
v Hanging requests
v Lock contention problems
v Malfunctioning applications in a server farm
v Memory problems relating to garbage collection and JVM heap size
Managing
Use ITCAM for Application Diagnostics to perform the following management
functions in your On-Demand application environment:
v Start and stop monitored servers
v Manage servers using groups
v Configure Data Collectors
v Use roles to restrict access to features
v Use server groups to grant access to servers
v Adjust the monitoring level at specific times based on the current work load of
the server
ITCAM for Application Diagnostics user interfaces
ITCAM for Application Diagnostics functions can broadly be divided into two
areas: monitoring and diagnostics. Each of these functions uses different
combinations of components. Each function also uses a different user interface. The
two user interfaces are the Tivoli Enterprise Portal and the Managing Server
Visualization Engine (MSVE).
The Tivoli Enterprise Portal user interface
The Tivoli Enterprise Portal is part of the IBM Tivoli Monitoring architecture. The
Tivoli Enterprise Portal is the user interface into your ITCAM for Application
Diagnostics environment site and possibly other IBM Tivoli enterprise applications
if they are installed in your environment. For further information about the Tivoli
Monitoring architecture, see “Components used by the Tivoli Enterprise Portal user
interface” on page 5.
Using the Tivoli Enterprise Portal interface, you can easily monitor the health and
availability of production applications and application servers, and you can quickly
identify and isolate availability and response time problems. The Tivoli Enterprise
Portal provides monitoring information, such as memory usage, response time,
pool analysis, and data source analysis. The Tivoli Enterprise Portal enables you to
drill down from server level metrics to specific application and resource level
metrics.
MSVE user interface
The MSVE user interface provides users with management and monitoring
functions for application servers. In addition, the MSVE also provides a diagnostic
function. Here are some of the diagnostic activities you can perform in MSVE:
4
ITCAM for Application Diagnostics: User Guide
v
v
v
v
Detect transactions failing
Detect memory leaks
Examine detailed method traces, which help to detect application code hotspots
Generate reports to analyze historical information, such as application
performance and OS performance
Components used by the Tivoli Enterprise Portal user interface
A number of components work together to collect, analyze, and display monitoring
data in the Tivoli Enterprise Portal. These components are:
1. The Agents
2. IBM Tivoli Monitoring components
The Agents
There are separate agents for WebSphere, J2EE, and HTTP Servers. The agents
consist of the following components:
v Tivoli Enterprise Monitoring Agent (referred to as the Monitoring agent)
v Data Collector
Note: The exception is the HTTP Servers agent. The HTTP Servers agent does not
contain a Data Collector. Only the WebSphere and J2EE Agents contain Data
Collectors.
The Monitoring Agent: The Monitoring Agent is a component of the IBM Tivoli
Monitoring architecture. The purpose of the Monitoring Agent is to route
information to the Tivoli Enterprise Monitoring Server (monitoring server) where
the information is processed and presented in the Tivoli Enterprise Portal.
The Data Collector: The purpose of the Data Collector is to collect and route data
to the Monitoring Agent. It is not intended to analyze or interpret data.
On each WebSphere and J2EE server you are monitoring, an agent is installed, so
there is a Monitoring Agent and a Data Collector running on each server you are
monitoring.
For example, if you are monitoring a Tomcat server, a J2EE Agent is installed on
this server. If you are monitoring a WebSphere Portal server, a WebSphere Agent is
installed.
The WebSphere Agent
The WebSphere Agent consists of a Monitoring Agent and a Data Collector. The
WebSphere Monitoring Agent works with the WebSphere Data Collector. The
WebSphere Data Collector collects monitoring data from WebSphere servers and
communicates the data to the Monitoring Agent.
The WebSphere Agent collect data from four primary sources:
v Response time data for application service requests from the Data Collector
v Resource data from the WebSphere Performance Monitoring Infrastructure (PMI)
v WebSphere Application Server log messages
v Garbage-collector activity that is recorded in the JVM verbose GC trace
v Process data from the operating system
Chapter 1. Overview of ITCAM for Application Diagnostics
5
The J2EE Agent
The J2EE Agent is composed of a Monitoring Agent and a Data Collector. The J2EE
Agent works with the J2EE Data Collector to collect performance data from J2EE
application servers. The J2EE Data Collector collects monitoring data from J2EE
servers and communicates the data to the Monitoring Agent. The J2EE Agent
collects data from three primary sources:
v Response time data for application service requests from the data collector
v J2EE application server log messages
v Garbage collection activity that is recorded in the JVM verbose GC trace
The HTTP Agent
The HTTP Agent is composed of a Monitoring Agent only. The Monitoring Agent
can monitor the following HTTP servers:
v IIS Web Servers
v Apache Web Servers
v IBM HTTP Web Servers
v Sun Web Servers
The HTTP Monitoring Agent has three components that are used to collect
monitoring data from Web servers. There is an Apache, an IIS, and a Sun Web
servers component.
The HTTP Agent collects performance data about the Web servers and Web sites in
the following ways:
Apache Server and HTTP Server: The agent modifies the Apache server and IBM
HTTP server configuration files to include the monitoring module. The monitoring
module is loaded dynamically during Web server start up. The module receives all
HTTP requests and report data to the HTTP Agent. In addition, the HTTP Agent
parses static information from the configuration file.
IIS Web Server: The HTTP Agent collects monitoring data from IIS Servers in the
following two ways:
v For static information about server configuration, the agent issues queries to the
Admin Base Object (ABO) interface which provides access to the IIS metabase.
v For dynamic information about server availability and performance metrics, the
agent issues queries to the Microsoft Windows Management Instrumentation
(WMI) interface.
Sun Web Server: The HTTP Agent collects monitoring data from Sun Web Servers
by polling the SNMP service for Web server-related statistics. It also parses Web
server configuration files to get information that is not provided by the SNMP
service.
IBM Tivoli Monitoring components
IBM Tivoli Monitoring monitors the performance and availability of distributed
operating systems and applications. IBM Tivoli Monitoring products are based on a
set of common service components. These service components provide security,
data transfer and storage, notification mechanisms, user interface presentation, and
communication services in an agent-server-client architecture. Some of these service
6
ITCAM for Application Diagnostics: User Guide
components are shared by other products, including IBM Tivoli OMEGAMON® XE
mainframe monitoring products, ITCAM for Application Diagnostics, and ITCAM
for Applications.
The service components ITCAM for Application Diagnostics and IBM Tivoli
Monitoring share are:
v
v
v
v
Tivoli
Tivoli
Tivoli
Tivoli
Enterprise
Enterprise
Enterprise
Enterprise
Monitoring Server (referred to as the Monitoring Server)
Portal Server (referred to as the Portal Server)
Portal
Monitoring Agent (referred to as the Monitoring Agent)
ITCAM for Application Diagnostics uses the service components of IBM Tivoli
Monitoring. The ITCAM for Application Diagnostic Monitoring Agents integrate
with components in the IBM Tivoli Monitoring environment by retrieving data
from the Monitoring Agents and forwarding it to the Portal Server where it is
displayed in the Tivoli Enterprise Portal.
Here is some further information regarding the shared service components and
how they integrate with ITCAM for Application Diagnostics:
Tivoli Enterprise Monitoring Server: The Monitoring Server performs the
following functions:
v Acts as a collection and control point for alerts that are received from the
Monitoring Agents.
v Tracks the heartbeat request interval for all Monitoring Agents connected to it.
v Stores, initiates, and tracks all situations and policies, and is the central
repository for storing all active conditions on every Monitoring Agent.
v Initiates and tracks all generated actions that invoke a script or program on the
Monitoring Agent.
Tivoli Enterprise Portal Server: The Portal Server performs the following
functions:
v Acts as a repository for all graphical presentations of monitoring data.
v Provides the core presentation layer, which allows for the retrieval,
manipulation, analysis, and reformatting of data.
v Manages data access through user workspace consoles.
Tivoli Enterprise Portal: The Tivoli Enterprise Portal is a Java-based user interface
that connects to the Monitoring Server and displays monitoring data. The Tivoli
Enterprise Portal can be launched from an Internet Explorer browser, or can be
installed as a client application on a workstation. The Tivoli Enterprise Portal is
one of the user interfaces for ITCAM for Application Diagnostics, the other user
interface is the MSVE.
Tivoli Enterprise Monitoring Agent: The Monitoring Agents are responsible for
data gathering. The Monitoring Agents communicate monitoring data to the
Monitoring Server and the managing server. In ITCAM for Application
Diagnostics, the WebSphere, J2EE, and HTTP agents contain Monitoring Agents.
The following diagram displays the component used by the Tivoli Enterprise
Monitor:
Chapter 1. Overview of ITCAM for Application Diagnostics
7
For more information about the ITCAM for Application Diagnostics agents, see
“The Agents” on page 5. For more information about the IBM Tivoli Monitoring,
see ITM Information Center
Components used by the MSVE user interface
A number of components work together to collect, analyze, and present the
monitoring data in the MSVE. These components are:
v Managing Server
v Data Collector
The Managing Server is the central component of ITCAM for Application
Diagnostics. For every implementation of ITCAM for Application Diagnostics,
there is one Managing Server. The Managing Server is a powerful technology that
provides deep dive functions. The user interface for the Managing Server is the
MSVE. The Managing Server works with Data Collectors, for each server being
monitored there is one Data Collector installed. The Data Collector collects
performance data from the application servers and HTTP servers and forwards this
information to the Managing Server.
ITCAM for Application Diagnostics Managing Server provides deep dive diagnosis
capabilities. The Managing Server provides the following functions:
8
ITCAM for Application Diagnostics: User Guide
Table 1. Managing Server Functionality
Area
What you can do
Server and Account
management
v Manage servers using groups
v Configure Data Collectors
v MOD management
v Use roles to restrict access to features
Systems Overview
v Display the availability of application servers
v Provide comparisons between current response times and baseline
response times
v Provide application server-level statistics for quick assessment of
server activity and related platform data
v Provide system resources
Server Activity
v Use In-Flight Request Search and Server Activity Display – Active
Requests to locate malfunctioning applications
v View transactions in progress
v Evaluate the current performance of your applications
v Spot hanging transactions
v Troubleshoot and fix hanging transactions
v Solve lock contention problems
v Access JVM thread data
v Use memory diagnostic tools to allocate memory problems inside
applications
Recent Activity
v Investigate and fix potential memory problems relating to garbage
collection and the JVM heap size
v Tune the JVM parameters
v Find evidence of memory leaks
Performance
Analysis and
Reporting
v Generate reports
Problem Center
v View high priority trap alerts and Tivoli Enterprise Portal events
v Analyze historical data
v Use historic data to analyze performance problems found in traps
and Tivoli Enterprise Portal situation events
Composite
Transactions
v Monitor transactions and analyze the method flow using method
trace, stack trace, and request information
Monitoring on
Demand
v Create a schedule that alters the monitoring level based on a date
and time when a server needs more detailed monitoring
v Adjust the monitoring level at specific times based on the current
work load of the server
v Override the monitoring level or change the schedule for a
selected server
Managing Server components
The Managing Server is J2EE application that is configured within WebSphere
Application Server. The Managing Server works with a DB2® or Oracle database. It
is designed for scalability and load balancing, and there are many ways to
implement an installation across one or more servers. The Managing Server
consists of the following components:
Chapter 1. Overview of ITCAM for Application Diagnostics
9
Kernel: The kernel controls the Managing Server. The kernel registers components
as they join the Managing Server, it periodically renews connections and
registrations with components and Data Collectors and collects server and
component availability information.
Publish Server: The publish server receives data from the Data Collector and
aggregates it based on different needs.
Archive Agent: The archive agent collects data from the publish server and
archives it into the database for reporting.
Message Dispatcher: The message dispatcher sends out e-mails of performance
reports and trap actions from the Performance Analysis and Reporting and the
Trap and Alert Management features.
Global Publish Server (GPS): The global publish server tracks composite requests,
as they move from one server to another.
The following diagram displays the component used by the MSVE:
Tivoli Enterprise Portal interoperation with MSVE
The Tivoli Enterprise Portal and MSVE interoperate in a number of ways. When
monitoring and troubleshooting your application environment, you can move
easily between the Tivoli Enterprise Portal and MSVE as you can use links in the
Tivoli Enterprise Portal workspaces to launch in context into MSVE. In the MSVE
more detailed information is provided about individual transactions as they occur this assists you in diagnosing problems. The Tivoli Enterprise Portal provides
monitoring information, so in the Tivoli Enterprise Portal you are alerted that a
problem occurred with a server, an application, or a resource. If you need to
analyze problems in greater detail, you can link in context to MSVE.
10
ITCAM for Application Diagnostics: User Guide
Another way in which the Tivoli Enterprise Portal and the MSVE interoperate is
through situations in the Tivoli Enterprise Portal and alerts in the MSVE. When a
situation is triggered in the Tivoli Enterprise Portal, this is displayed as an alert in
the MSVE. Alerts and Events page. All situations can be escalated to problems and
then can be evaluated in the Problem Center.
For further information about configuring Single Sign on between Tivoli Enterprise
Portal and MSVE, see the ITCAM for Application Diagnostics: Installation and
Configuration Guide.
What's new in the 7.1 release?
A number of components work together to collect, analyze, and present monitoring
data in the Tivoli Enterprise Portal. These components are:
1. Ability to monitor WebSphere XD environment
2. Ability to launch in context from Tivoli Enterprise Portal workspaces into
MSVE, this enables users to examine individual transactions in more detail
3. Rephrased data table names in Server Activity Display in MSVE makes them
more clear to users
4. Improved MSVE menus to indicate if data is real-time data or historic data
5. In MSVE, ability to link from active requests to the Stack Trace page
6. New predefined situations in the Tivoli Enterprise Portal
7. Improved Summary Workspaces functionality in the Tivoli Enterprise Portal to
guide
Getting Started with ITCAM for Application Diagnostics
Depending on your requirements, when you use ITCAM for Application
Diagnostics, you use either the MSVE or the Tivoli Enterprise Portal user interfaces
or a combination of both. For further information about using and navigating the
Tivoli Enterprise Portal and the MSVE, see the ITCAM for Application Diagnostics:
User Guide.
For further information about installing ITCAM for Application Diagnostics, see
the following publications:
ITCAM for Application Diagnostics: WebSphere Monitoring Agent Installation and
Configuration Guide
ITCAM for Application Diagnostics: J2EE Monitoring Agent Installation and
Configuration Guide
ITCAM for Application Diagnostics: J2EE Data Collector Installation and Configuration
Guide
ITCAM for Application Diagnostics: HTTP Monitoring Agent Installation and
Configuration Guide
ITCAM for Application Diagnostics: Managing Server Installation and Configuration
Guide
Chapter 1. Overview of ITCAM for Application Diagnostics
11
12
ITCAM for Application Diagnostics: User Guide
Chapter 2. Scenarios
This following scenarios describe some usage scenarios using the Tivoli Enterprise
Portal and the Managing Server Visualization Engine in ITCAM for Application
Diagnostics to monitor and diagnose problems in your application environment.
These usage scenarios refer to the following fictitious personas that might reflect
typical positions in your organization:
Table 2. Personas
Persona
Description
Annette – Level 2 Operator
Her primary focus is to find which component
is down, which components are impacted, and
the location of the problem. In addition, she
follows procedures to correct the problem. If she
cannot fix the problem within a specified time
limit that her service level agreement (SLA)
stipulates, she produces a trouble ticket and
escalates the problem.
Jim – Middleware/Application Support
Subject Matter Expert (SME)
His primary focus is to ensure that the
middleware applications he is responsible for is
up and running at all times. If an application
should go down, then a line of business is
affected and has a direct impact on how his
team is rated against their SLA. He also works
with the systems monitoring and automation
group to define the appropriate monitors and
thresholds for his domain area of responsibility.
Dave – Application Developer
His primary focus is to develop in-house
applications. When a problem comes up in a
production application he is sent trace files so
he can analyze the problem, which he then tries
to simulate in his environment.
Simon - Operating System Specialist
His primary focus is to work with the systems
management team to define what are the base
OS services/daemons, ports, file systems, and
logs that must be monitored on every computer.
Simon is also a recognized expert in cluster
configurations.
Scenario 1: Diagnosing a memory leak
Users are reporting slow response times for an application. A user contacts the
help desk and raises a ticket for slow response time in relation to an application.
Annette, the level 2 operator, picks up the ticket.
1. Annette navigates to the Tivoli Enterprise Portal and notices that the Resources
icon is displaying a Critical symbol. On the Resources icon flyover, the GC
Active Time (ms) metric is displaying a high value and also the
WASHighGCTimePercent situation has triggered. This indicates that the JVM
garbage collection is taking too long.
© Copyright IBM Corp. 2006, 2009
13
2. In the Garbage Collection Analysis workspace, Annette observes, the
Percentage of Time Garbage Collector Running - History view displays an
increasing trend, which suggests that the heap is insufficient for the demand
that applications are putting on it. The Running - History graph, which
displays the percentage of real time that the garbage collector was running
during the current interval for each server region, is showing an increasing
trend. This suggests that either the heap size is insufficient for the demand that
applications are putting on it or else there is a memory leak.
3. Annette uses an external ticketing tool to route the ticket to Jim, the
Middleware/Application SME, for further observance and investigation.
4. Jim notices a problem ticket from Annette involving excessive garbage
collection times. Jim navigates to the Garbage Collection Analysis workspace
and confirms the problem. He requires more detailed information to diagnose
the cause of the problem. He clicks the Diagnostic Memory Leak link in the
Garbage Collection Analysis workspace. This opens the Memory Leak
Confirmation report page in Managing Server Visualization Engine (MSVE).
14
ITCAM for Application Diagnostics: User Guide
5. From examining the Memory Leak Confirmation report page in MSVE, Jim
suspects that there is a memory leak.
6. To fully determine if there is a memory leak, he sets the monitoring level to L3
and enables memory leak BCI by doing the following steps:
v Edits the file: $DC_HOME/runtime//custom/toolkit_custom.properties file and
sets the property
com.ibm.tivoli.itcam.toolkit.ai.enablememoryleakdiagnosis=true.
v Uncomments this line to enable Memory Leak Diagnosis:
am.camtoolkit.gpe.customxml.leak=/opt/IBM/itcam/WebSphere/DC/itcamdc/
etc/memory_leak_diagnosis.xml
v Restarts the Data Collector.
Jim forwards the problem to Dave, the Application Developer. Dave works to
resolve the problem. This action is outside the scope of ITCAM for Application
Diagnostics.
Scenario 2: Diagnosing hanging transactions
Annette, the level 2 operator, receives an e-mail indicating that a situation
triggered in the Tivoli Enterprise Portal. The situation is indicating that response
time is slow for an application.
1. In the Tivoli Enterprise Portal, Annette points to the application icon and sees
in the flyover that the WASHighResponseTime situation triggered.
Chapter 2. Scenarios
15
2. Annette double-clicks the application icon and the Application Trend is
displayed. In this workspace, the Application Summary report displays
information about response time, error rate, and request rate. Annette
double-clicks the Request Analysis workspace, which displays information
about worst average request response time and worst average request
completion rate. Annette observes that the average request response time is
high and that the average request completion rate is low (for some of the
requests).
3. For a more detailed analysis of requests, Annette navigates to the Request
Analysis workspace. The response times for some requests are displaying as
high.
16
ITCAM for Application Diagnostics: User Guide
4. Annette uses an external ticketing tool to route the ticket to Jim, the
Middleware/Application Support SME, for further observance and
investigation.
5. Jim notices a problem ticket from Annette indicating slow response times. Jim
navigates to the Request Analysis workspace in the Tivoli Enterprise Portal and
confirms the slow request response time for the application.
6. To see individual hanging transactions, Jim needs to open MSVE. He clicks the
Diagnostic In-Flight Request Search link, which displays the In-flight Request
Search page in the MSVE.
7. From here, Jim can diagnose hanging requests and see the stack trace for that
request by clicking the server activity display.
Chapter 2. Scenarios
17
8. Jim then forwards details to Dave, the Application Developer. Dave works to
resolve the problem. This action is outside the scope of ITCAM for Application
Diagnostics.
18
ITCAM for Application Diagnostics: User Guide
Scenario 3: Diagnosing a WebSphere server shutdown
Annette, the level 2 operator, receives a severity 1 ticket indicating that users
cannot access an application.
1. Annette navigates to the Tivoli Enterprise Portal where (in the WebSphere
Agent Summary Status workspace) the Applications icon is displaying a critical
symbol. The flyover on the Application icon shows that a WasNotConnected
situation triggered. The application server summary also shows the server
status as “Disconnected”.
2. Annette navigates to the Log Analysis workspace. This workspace reports
application server errors and exception conditions that are recorded in the
SystemOut.log WebSphere Application Server log file. The information in this
workspace includes the exception severity of errors, and the ID and text of the
associated message.
3. Annette observes that in the Log Analysis report, the Process ID value is
displayed as -1. This value indicates that the Data Collector is disconnected. If a
WebSphere server shutdown occurs, the connection between the data collector
and Tivoli Enterprise Monitoring Agent is closed. However, the data collector
continues to write to log files and Tivoli Enterprise Monitoring Agent processes
these records but sets the PID value to -1.
Chapter 2. Scenarios
19
4. Annette uses an external ticketing team to forward the ticket to Jim the
Middleware/Application Support SME. Jim investigates the cause of the
WebSphere server shutdown and initiates a restart of the WebSphere
Application Server.
Scenario 4: Determining if the WebSphere cluster needs to be load
balanced
Annette, the level 2 operator, is getting a number of tickets relating to slow
response time for an application. Annette receives an e-mail indicating that the
WASHighCPUPercentUsed situation triggered on the WebSphere Application
Server where the application is hosted.
1. Annette navigates to the Tivoli Enterprise Portal and observes that on the
WebSphere Agent Summary workspace the Application icon is displaying a
warning symbol. The Resources icon is displaying the critical symbol. The
Resource icon flyover is displaying high JVM CPU%.
20
ITCAM for Application Diagnostics: User Guide
2. Annette double-clicks the Resources icon and sees that the OS icon and JVM
icon are both displaying the critical symbol. The OS icon flyover is displaying
System CPU (ms) as high. It also has the JVM icon displaying JVM CPU% as
high.
3. Annette double-clicks the Application icon. The Application Trend at L2/L3
workspace is displayed. The Selected Application Summary report displays the
application name, average request response time, average request completion
rate, and error rate. The average request response time is high. The Request
Rate Trend chart displays the number of requests that are completed per
second for the application. Again, this value is displaying as high.
Chapter 2. Scenarios
21
4. Before Annette escalates this problem, she needs to determine if this problem is
recent or if it has been occurring for some time. Annette checks the trend by
taking the following steps in the Request Rate Trend chart:
a. In the Application Trend at L2/L3 workspace, she selects the Specify time
span for query icon. The Select the Time Span window is displayed.
b. In the Custom Parameters section, she enters the required values in the
Start Time and End Time fields. and she clicks OK.
5. Annette observes that there was an increase in client requests a few days ago
and that this value has remained high throughout the week. Further
investigation reveals that a surge of new customers caused a large increase in
new users on the system. As a result, the load on the system is high.
6. Annette uses an external ticketing tool to forward the ticket with all details to
Jim, the Middleware/Application Support SME.
22
ITCAM for Application Diagnostics: User Guide
7. Jim immediately sees from what Annette has reported that the system is
over-burdened as a result of a significant increase in new users, and that the
number of servers that are available in the cluster needs to be increased. Jim
forwards the ticket to Simon, the OS SME.
8. Simon needs to determine if the Application is running on a static or a
dynamic WebSphere cluster. If the application is running on a static cluster, he
adds additional application servers. If the application is running on a dynamic
cluster; he increases the number of servers allowed. These actions are outside
the scope of ITCAM for Application Diagnostics.
Scenario 5: Determining the cause of high response times
Annette, the level 2 operator, receives an e-mail to indicate that the
WASHighResponseTime situation has triggered for an application.
1. Annette navigates to the Tivoli Enterprise Portal and notices in the Application
Server Summary workspace, the icon for the application is displaying a critical
icon. The flyover for the application indicates that the Average Response time
(ms) is high. Annette needs to determine how long the response time has been
high.
2. Annette double clicks the Application icon, the Application Trend at L1
workspace is displayed. Annette requests historical data by taking the
following steps:
a. In the Requests - Current Interval View, she clicks the Specify time span for
query icon. The Select the Time Span window is displayed.
b. In the Custom Parameters section, she enters the required values in the
Start Time and End Time fields and she clicks OK.
c. She sorts by the Average Response Time column.
Chapter 2. Scenarios
23
3. Annette uses an external ticketing tool to forward the trend details to Jim, the
Middleware/Application Support SME.
4. Jim, receives this problem ticket about high response times for a particular
application. Jim navigates to the Request Analysis workspace and confirms the
problem Annette described.
5. To further investigate the problem Jim needs to open MSVE. Jim clicks the
Diagnostic Recent Completed Requests link to open the MSVE Server Activity –
Recent Requests page. Only requests that contain the URI information from the
24
ITCAM for Application Diagnostics: User Guide
Request Analysis workspace are displayed. Jim notices that there are a number
of client requests with high response times.
6. Jim decides to further analyze the transactions by setting a Resident Time –
In-Flight trap. This trap activates the moment an in-flight request takes longer
than a specified amount of time (minimum 15 seconds). To set up this trap, Jim
must do the following steps:
a. Select the trap type.
b. Set the trap alerts.
Chapter 2. Scenarios
25
c. Activate the trap.
d. Jim then sets an action type of Stack Trace and waits for a problem request
to trigger the trap.
7. After a little while, the problem request triggers the trap.
26
ITCAM for Application Diagnostics: User Guide
8. This trap also produces a stack trace.
Jim forwards the trouble ticket to Dave, the application developer. Dave works
to resolve the problem. This action is outside the scope of ITCAM for
Application Diagnostics.
Chapter 2. Scenarios
27
Scenario 6: Determining the cause of connection problems
Annette, the level 2 operator, receives notification that the
WASJ2CCPAvgWaitTimeHigh situation triggered. This error is critical. This
situation indicates that the average wait time until a connection is granted is
longer than 2 seconds.
1. Annette navigates to the J2C Connections Pools workspace. This workspace
reports information about resource adapters and connectors that adhere to J2EE
Connector Architecture (J2C). J2C is the WebSphere Application Server
implementation of the Java EE Connector Architecture (JCA). Data counters for
this category contain usage information about the J2C connection pools that
enable enterprise beans to connect to, and interact with, Enterprise Information
Systems.
2. In this workspace Annette observes in the Worst Wait Times view that some
wait times for connections are above 2 seconds. The Highest Average Pool Sizes
bar chart shows the largest average number of managed connections for each
J2C connection pool. Typically, a connection takes no longer than 2 seconds.
28
ITCAM for Application Diagnostics: User Guide
3. Annette uses an external ticketing tool to forward the ticket with details to Jim,
the Middleware/Application Support SME.
4. Jim navigates to the J2C Connections Pools workspace and compares the
average pools size with the maximum pool size to establish the ideal maximum
value. Jim establishes that the connection pool size needs to be adjusted, which
is outside the scope of ITCAM for Application Diagnostics.
Scenario 7: Determining if the Garbage Collection policy needs to be
adjusted
Annette, the level 2 operator is monitoring the Tivoli Enterprise Portal. Annette
notices a critical symbol on the JVM icon in the Application Server Summary
workspace. The flyover for JVM icons shows a high metric for JVM CPU% and GC
Active Time (ms).
Chapter 2. Scenarios
29
1. Annette double-clicks the JVM icon. The JVM Stack Trend workspace is
displayed. The Percent GC Time Used view displays a high value. The heap
usage trend is also high.
2. Annette uses an external ticketing tool to forward the ticket with details to Jim,
the Middleware/Application Support SME.
30
ITCAM for Application Diagnostics: User Guide
3. Jim reviews the information and determines that the heap size parameters in
the JVM are not set correctly. This incorrect setting affects application
performance. Jim sets the appropriate GC policy.
Scenario 8: Troubleshooting application response time in an XD cell
Due to external resource the response time for one of applications in the XD cell
degrades below the service policy goal. Annette the level 2 operator, receives an
e-mail to indicate that the Application Requests Above Goal situation triggered.
This situation triggers when the rate of requests above goal is greater than 0.5%.
1. In the Tivoli Enterprise Portal navigation tree, Annette follows the workspace
link for the triggered situation. The XDVEAppReqAboveGoalPercentHigh
Event workspace is displayed.
2. Annette navigates by a link from the XDVEAppReqAboveGoalPercentHigh
Event workspace to the Application workspace.
3. The Application workspace displays On Demand Router Statistics (ODR) for
the selected application module, transaction, class, and protocol summarized
over all ODRs in the cell.
4. From the Application workspace, Annette observes that the average overall
response time is 20 seconds and the average server service time is also 20
seconds. This indicates, that some problem is occurring with the handling
requests by this application.
5. To see the deployment targets hosting the application and ascertain which of
the deployment targets is contributing to the slow response time, Annette
drills down to the Deployment Targets workspace using the Per Deployment
Targets link.
Chapter 2. Scenarios
31
6. The Deployment Targets workspace displays a single deployment target for
this application: DynCluster. Annette drills down to this dynamic cluster using
the link and then to servers belong to the dynamic cluster.
7. The servers for the dynamic cluster performance are displayed. From this
view, Annette observes that both servers in the dynamic cluster have similar
loading. Annette drills down to each server and observes that both have
requests higher than the set goal of 10 seconds.
8. Annette drill downs to Server Diagnostic for one of servers using the link,
which opens the Data Collector workspace for that server. Annette observes in
the workspace that the “sleeperEAR” application is displaying a critical red
symbol.
32
ITCAM for Application Diagnostics: User Guide
9. Annette double-clicks the application, this opens the Request Analysis
workspace.
10. From the Request Analysis workspace, Annette navigates to the MSVE using
the Diagnostic In-Flight Request Search link. From the MSVE, Annette can
navigate to the thread for the selected request and view the request call stack.
Chapter 2. Scenarios
33
11. Annette uses an external ticketing tool to forward the ticket with details to
Jim, the Middleware/Application Support SME.
12. Jim reviews the information and determines that the application waits for
response from an external system. Jim researches and resolves the external
system issue and restores the application response time before it impacted the
majority of the users.
Scenario 9: Ensuring that jobs processed by Compute Grid don't
execute for longer than one hour
Annette, the level 2 operator, needs to ensure that jobs processed by Compute Grid
do not execute for longer than one hour. If a job executes for longer, then Annette
needs to capture the job information and forward to the Middleware/Application
Support SME.
1. Middleware/Application Support SME configure jobs as custom requests via
Data Collector configuration files.
2. Annette edits the predefined XDCGJobExcessiveTotalTime situation to trigger if
the total job time is greater than 60 minutes.
34
ITCAM for Application Diagnostics: User Guide
3. At some point in time, Annette observes that the situation has triggered.
4. Annette clicks the event link and the event workspace is displayed.
Chapter 2. Scenarios
35
5. Annette opens the Job workspace by using the link from event workspace.
6. The Job workspace shows all the details about the job. From the job
notifications, Annette observes that the job is executing for a long time, she
clicks the Diagnostic in-Flight Request Search link, this opens the MSVE
in-flight workspace, from here she clicks the link to see the request call stack.
7. Annette captures the call stack and provides to Jim, the Middleware/
Application Support SME.
8. Jim determines that job is waiting for database lock and resolves it
appropriately.
36
ITCAM for Application Diagnostics: User Guide
Part 2. Part 2: Using ITCAM for Application Diagnostics
© Copyright IBM Corp. 2006, 2009
37
38
ITCAM for Application Diagnostics: User Guide
Chapter 3. ITCAM for Application Diagnostics Managing
Server Visualization Engine
The Managing Server Visualization Engine (MSVE) user interface provides users
with management and monitoring functions for application servers. In addition,
the MSVE also provides a diagnostic function. Here are some of the diagnostic
activities you can perform in MSVE:
v Detect transactions failing
v Detect memory leaks
v Examine detailed method traces, which help to detect application code hotspots
v Generate reports to analyze historical information, such as application
performance and OS performance
Access the Managing Server Visualization Engine from Tivoli
Enterprise Portal
You can access the Managing Server Visualization Engine from links in ITCAM
Agent for WebSphere Applications workspaces.
When you access the Managing Server Visualization Engine in this way, the
Managing Server Visualization Engine displays in a browser view inside a
workspace. The Tivoli Enterprise Portal navigation tree is automatically hidden in
the workspace. To show or hide the Tivoli Enterprise Portal navigation tree, click
the small black arrow on the left side of the window.
The following table displays a list of Tivoli Enterprise Portal workspaces that have
links to the Managing Server Visualization Engine.
Table 3. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine
Workspace: Table
View Name
Number of
links to
Managing
Server
Visualization
Engine
Link Name
WebSphere Agent 2
Summary Status >
Application
Servers
v Diagnostic
Server
Activity
Display
WebSphere Agent
Summary Status >
Application
Servers
v Diagnostic
In-Flight
Request
Search
Link Target
Pages Managing
Server
Visualization
Engine
v Server
Activity
Display –
Active
Requests
v In-Flight
Request
Search
Pre-populated
information in
the link page to
Managing Server
Visualization
Engine
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
WebSphere Agent
Configuration>
Application
Servers
© Copyright IBM Corp. 2006, 2009
39
Table 3. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine (continued)
Workspace: Table
View Name
OS Stack >
Current OS Stack
Summary
Number of
links to
Managing
Server
Visualization
Engine
Link Name
3
v Diagnostic
Server
Activity
Display
v Diagnostic
In-Flight
Request
Search
JVM Stack Trend 1
>JVM Stack Trend
40
ITCAM for Application Diagnostics: User Guide
Link Target
Pages Managing
Server
Visualization
Engine
v Server
Activity
Display –
Active
Requests
v In-Flight
Request
Search
v <platform
OS>
<platform> is
one of the
following
operating
systems:
Linux, UNIX,
Windows or
z/OS
v Using the
dynamic
workspace
link to link to
the
corresponding
OS agent
workspace.
For z/OS, the
link is to
OMEGAMON
XE for z/OS.
Diagnostic
Memory Leak
Memory Leak
Analysis
Pre-populated
information in
the link page to
Managing Server
Visualization
Engine
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
Table 3. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine (continued)
Workspace: Table
View Name
Request Analysis
> Requests –
Current Interval
Number of
links to
Managing
Server
Visualization
Engine
Link Name
3
v Diagnostic
Recent
Completed
Requests
v Diagnostic
In-Flight
Request
Search
v Diagnostic
SMF Data
(z/OS only)
Link Target
Pages Managing
Server
Visualization
Engine
Pre-populated
information in
the link page to
Managing Server
Visualization
Engine
v The Group
Server
dropdown
menu is
pre-populated
based on data
v In-Flight
collector
Requests
information
v SMF Data (for
from Tivoli
z/OS data
Enterprise
collectors
workspace.
only)
v Content in
Request Detail
column of
Requests table
view in Tivoli
Enterprise
Portal is
pre-populated
in the following
fields:
v Server
Activity
Display –
Recent
Requests
– Recent
Requests:
Client
Request
– In-Flight
Request
Search:
Search
Request/
Transaction
field
1
Garbage
Collection
Analysis >Garbage
Collection
Analysis
Thread Pools
>Thread Pools
1
Diagnostic
Memory Leak
Memory Leak
Analysis
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
Diagnostic JVM
Thread Display
JVM Thread
Display
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
41
Table 3. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine (continued)
Workspace: Table
View Name
Datasources >
Datasources –
Current Interval
Number of
links to
Managing
Server
Visualization
Engine
Link Name
1
Web Applications
>Web
Applications
EJB Containers
>EJB Containers
Diagnostic
Server Activity
Display
Link Target
Pages Managing
Server
Visualization
Engine
Pre-populated
information in
the link page to
Managing Server
Visualization
Engine
Server Activity
The Group Server
Display – Active dropdown menu
Requests
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
JMS Summary
>JMS Summary –
Current Interval
DB Connection
Pools > DB
Connection Pools
J2C Connection
Pools > J2C
Connection Pools
The Server Group feature that displays at the top of these pages applies to the
Managing Server Visualization Engine. When you access any Managing Server
Visualization Engine page from the Tivoli Enterprise Portal, the information in the
Groups and Servers fields is automatically populated with the data collector
associated with the link and workspace you selected in the Tivoli Enterprise Portal.
Groups are a set of application servers which have similar functionality. All
configured data collectors are automatically assigned to the Unassigned Servers
Group. The relationship between Server Group and data collector is many to
many. A data collector can belong to one or more server groups. A server group
can have one or more data collectors. You can add data collectors to groups using
the Server Management functionality in the Managing Server Visualization Engine.
For more information about adding data collectors to Server Groups, refer to the
Composite Application Manager Help in the Managing Server Visualization Engine
interface.
The Server Activity Display section has three tabs.
v Active Requests: provides real-time request or transaction data for an
application server at the time the page displays.
v Recent Requests: displays the last 100 or less completed request or transaction
data for an application server.
v Lock Contentions: displays requests that are hanging because they are waiting
on a lock. The data shows data that is currently locked and the item that is
waiting to be locked.
42
ITCAM for Application Diagnostics: User Guide
The Active Requests tab and the Recent Requests tab have a toolbox icon
You can click this toolbox icon to access direct links to the following features:
v JVM Thread Display
v System Resources
v Monitoring On Demand®
v Data Collector Profiles
v Trap and Alert Management
.
You can use this information to analyze the details and identify the areas where
the issues occur. To return to the Tivoli Enterprise Portal interface at any time click
back on your web browser.
For more detailed information see:
v “Server Activity Display - recent requests” on page 117
v “Server Activity Display - active requests” on page 115
v “Server Activity Display - lock contentions” on page 118
v “JVM thread display” on page 135
v “System resources” on page 96
v “Monitoring on Demand (TM)” on page 73
v “Data Collector Profiles” on page 61
v “Trap and alert management” on page 139
Account management
Control access to features and servers.
Account management enables you to control users' access to features and servers.
Use roles to restrict access to features, and use server groups to grant access to
servers.
User Scenarios
Scenario 1: Granting members of Team XYZ access to ITCAM for Application
Diagnostics
Team XYZ has asked for access to ITCAM for Application Diagnostics for, but only
needs access to features that use historical data. Since the existing roles provide
access to features that use both real time and historical data, create a role for them
called team XYZ. When you define this role, provide access to features that use
only historical data, for example PAR. Assign role team_XYZ to each user account
belonging to members of team XYZ.
Scenario 2: Creating an account for a new employee
Employee John Smith is an operator that just joined your company. John needs to
use ITCAM for Application Diagnostics for to monitor QA systems. As the ITCAM
for Application Diagnostics for administrator, you create John's account with access
granted to QA server groups but not Production server groups. Furthermore, you
restrict John's access to features by assigning the Operator role to his account.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
43
User profiles
The User Profiles page shows a table of all user accounts in the Visualization
Engine. From this page, you can create, modify, and delete user accounts.
To view the User Profiles page, from the top navigation, click Administration >
Account Management > User Profiles.
For every account, the table shows the account name, first name, last name, and a
Delete button.
To sort by any column, click its heading.
To modify the information for an account (including access rights), click the
account name. See “Modifying a user account” on page 45.
To delete a user account, click the Delete button in its row. See “Deleting a user
account” on page 46.
To create a user account, in the left navigation pane, click Create User Account.
See “Creating a user account.”
Creating a user account
About this task
Add new user accounts to the application monitor on the Create User Account
page. Limit the rights of your user accounts to the groups of servers you select. A
valid WebSphere Global Security user name is required to create an account. The
user name can be different from the operating system user ID, but it must be at
least three alpha characters and no more than 255. To enable single sign-on,
configure the Managing Server and the WebSphere application server that the
Managing Server Visualization Engine runs on. Then, add every user who needs to
access single sign-on. For more information about single sign-on, refer to
Appendix N Setting Up Single Sign on for Tivoli Enterprise Portal Users in the
ITCAM for Application Diagnostics 7.1 Managing Server Installation and Customization
Guide
To create a user account:
1. From the top navigation, click Administration > Account Management >
User Profiles. The User Profiles page opens.
2. In the left navigation pane, click Create User Account. The Create User
Account page opens.
3. Enter the first name (required).
4. Enter the last name (required).
5. Enter the user name (required).
6. Enter the OS/LDAP user name (required). ITCAM uses WebSphere Global
Security system for user authentication, therefore a valid WebSphere Global
Security user name is required to create an account.
7. Select the role you want to assign to the user account from the list box.
8. Select Active or Suspended for the account status. A user account is not ready
for use if its status is not marked Active.
9. Enter the user's e-mail address (optional).
10. Enter remarks in the available fields (optional).
11. To save the user account setup, click Save.
44
ITCAM for Application Diagnostics: User Guide
Results
To grant group access rights:
1. Click to select the group name in the All Groups box.
2. Click Add to grant the user account rights to the selected groups. The group
name appears in the Granted box.
To select multiple groups, hold down the Ctrl key during your selection.
To remove group access rights:
1. Click to select the group name in the Granted box.
2. Click Remove to remove the user account rights from the selected groups. The
group name disappears from the Granted box.
3. To select multiple groups, hold down the Ctrl key during your selection.
Related topics
Assigning a role
Creating a role
Modifying a user account
About this task
Modify existing user accounts in the application monitor on the Modify User
Account page. Limit the rights of your user accounts to the groups you select.
To modify a user account:
1. From the top navigation, click Administration > Account Management > User
Profiles. The User Profiles page opens.
2. Click the user name to select the user account you want to modify. The Modify
User Account page opens.
3. Select the field you want to edit, and enter the new information.
4. After entering your changes, click Save. You might want to suspend the user
accounts when the operators are on leave. When they return, select Active to
turn their user accounts back on.
Results
To grant group access rights:
1.
2.
Click to select the group name in the All Groups box.
Click Add to grant the user account rights to the selected groups. The group
name appears in the Granted box.
To remove group access rights:
1. Click to select the group name in the Granted box.
2. Click Remove to remove the user account rights from the selected groups. The
group name disappears from the Granted box.
Related topics
Assigning a role
Creating a group
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
45
Deleting a user account
About this task
Manage your accounts by keeping them up-to-date. Delete existing user accounts
from the application monitor on the User Profiles page.
To delete a user account:
1. From the top navigation, click Administration > Account Management > User
Profiles. The User Profiles page opens.
2. Click X or Delete on the last column of the user account that you want to
delete from the application monitor. A confirmation box displays.
3. Click OK in the confirmation box to delete the user account, or click Cancel to
return to the User Profiles page.
4. If you select OK, the system deletes the user account and the User Profiles
page no longer displays the deleted account.
5. To sort by heading, click the heading you want to sort. Only underlined
headings can be sorted. The page displays the results sorted by the selected
heading.
Related topics
Creating a role
Creating a user account
Deleting a role
Role configuration
The Role configuration page shows a table of permissions for security roles defined
in the Visualization Engine. From this page, you can create, modify, and delete
security roles.
To view the Role Configuration page, from the top navigation, click
Administration > Account Management > Role Configuration.
To control user account access to the product functions, each user account is
assigned a security role. The role grants access to specific product functions. A user
account can have only one role; the same role can be assigned to many accounts.
The rows in the table represent product functions; columns represent security roles.
Every cell of the table shows whether function (row) is allowed for the role
(column).
The Administrator, Operator, and User roles are predefined and cannot be
changed; you can change, add, and delete other roles.
To change permissions for a role, check or clear the boxes in its column. To save
changes, click the Save button; to undo changes before they are saved, click the
Reset button. (You might need to scroll the page down to reach these buttons). See
“Modifying a role” on page 47.
To delete a role, click the X button next to its name. See “Deleting a role” on page
48.
To create a role with blank permissions, in the left navigation pane, click Create
Role. See “Creating a role” on page 47.
46
ITCAM for Application Diagnostics: User Guide
To create a role with permissions copied from another role, in the left navigation
pane, click Duplicate Role. See “Duplicating a role” on page 48.
Creating a role
About this task
The Create Role page provides the functionality to create a custom role for your
environment. Design the custom role to restrict and grant privileges specific to the
needs for your environment.
To open the Create Role page:
1. From the top navigation, click Administration > Account Management > Role
Configuration. The Role Configuration page opens.
2. On the left navigation pane, click Create Role. The Create Role page opens.
3. Type in the name of the new role.
4. Click OK. The new role displays on the Role Configuration page.
5. Click to select the privileges user accounts can access in the application
monitor.
6. Click Save.
7. Click Reset to revert to the pre-modified settings.
Related topics
Assigning a role
Creating a user account
Assigning a role
About this task
After creating a role on the Role Configuration page, assign the role to user
accounts on the Modify User Account page. Modify user accounts to assign
appropriate privileges to them.
To assign a role:
1. From the top navigation, click Administration > Account Management > User
Profiles. The User Profiles page opens.
2. Click the user name that you want to assign a role. The Modify User Account
page opens.
3. On the Modify User Account page, from the Role list box, select the role to
assign to the user account.
4. Click Save.
Related topics
Creating a role
Deleting a role
Modifying a role
Modifying a role
About this task
The Role Configuration page provides the functionality to modify your custom
roles. Update and delete custom roles based on the needs of your environment.
To modify a role:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
47
1. From the top navigation, click Administration > Account Management > Role
Configuration. The Role Configuration page opens.
2. Click to check and clear the permissions you want to assign this role. Changing
the custom role privileges in the user accounts grants access in the application
monitor.
3. Click Save.
4. Click Reset to revert to the pre-modified settings.
Related topics
Assigning a role
Creating a role
Duplicating a role
About this task
To easily customize a new role, you can duplicate a role that uses a similar set of
permissions rather than checking or clearing the boxes one by one repeatedly.
To duplicate a role:
1. From the top navigation, click Administration > Account Management > Role
Configuration. The Role Configuration page opens.
2. On the left navigation pane, click Duplicate Role. The Duplicate Role page
opens.
3. Select a role name for the duplicated role from the Role Name list box.
4. Enter a new name for the duplicated role.
5. Click Save. The new duplicated role displays on the Role Configuration page.
6. Click to select the privileges user accounts can access in the Application
Monitor.
7. Click Save.
8. Click Reset to revert to the pre-modified settings. The duplicated role does not
have any users since its user-to-role relationship is not duplicated.
Related topics
Assigning a role
Creating a user account
Modifying a role
Deleting a role
About this task
The Role Configuration page provides the functionality to delete your custom
roles. Manage your custom roles based on the needs of your environment. You
cannot delete a role while the system associates a user account with it.
To delete a role not assigned to a user account:
1. From the top navigation, click Administration > Account Management > Role
Configuration. The Role Configuration page opens.
2. Click the X next to the role you want to delete.
3. At the confirmation box, click OK.
Results
To delete a role still assigned to a user account:
48
ITCAM for Application Diagnostics: User Guide
From the top navigation, click Administration > Account Management > Role
Configuration. The Role Configuration page opens.
2. Click X next to the role you want to delete. A confirmation box displays.
3. Click OK at the confirmation box. A list of the user accounts assigned to the
role appears. Since the system assigned the role to a user account, you have to
change the role of the user account on the Update Role page.
1.
4. Click the link to select the user account. The Modify User Account page opens.
5. Click to select a role for the user account from the Role list box.
6. Click Save. The system displays the Role Configuration page without the
deleted role.
Related topics
Creating a role
Creating a user account
Deleting a user account
Server management
Manage your servers with the server group management page.
Add and delete server groups, while associating groups with individual account.
You can restrict user access to data and operations on a specific group of servers.
User Scenarios
Scenario 1: Separating server groups according to applications
As the ITCAM for Application Diagnostics administrator, you want to distinguish
the group of servers that process trading requests from the group of servers that
process quote requests. You create two server groups: Trading and Quotes. In the
Trading server group, you include only those servers that deal with trading, and in
the Quotes server group you include only those servers that deal with quotes.
Grant users access to the appropriate server group(s).
Scenario 2: Grouping servers by authority structure
As the ITCAM for Application Diagnostics administrator, you want to separate the
servers in your environment by the authority structure present in the company.
The current Support team is separated into smaller groups that control individual
groups of servers. You create server groups that contain these servers such as
Support A controls servers 1 through 29, Support B controls servers 30 through 59
and Support C controls servers 60 through 90.
Server groups
The Server Groups page shows a table of all server groups. From this page, you
can create, modify, and delete server groups.
Groups are a set of application servers which have similar functionality. All
configured data collectors are in the Unassigned Servers Group. The relationship
between Server Group and data collector is many to many. A data collector can
belong to one or more server groups. A server group can have one or more data
collectors. You can add data collectors to groups using the Server Management
functionality in the Managing Server Visualization Engine. For more information
about adding data collectors to Server Groups, refer to the Composite Application
Manager Help in the Managing Server Visualization Engine interface.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
49
To view the Server Groups page, from the top navigation, click Administration >
Server Management > Server Groups.
Server groups are used for convenient grouping of information in the Managing
Server Visualization Engine. Every group includes one or several servers. In a
number of Managing Server Visualization Engine pages, you can view information
by server group. Each user can be granted access to information for some server
groups but not others. A server can be a member of several groups.
When you access pages from the Tivoli Enterprise Portal, the information in the
Groups and Servers fields is automatically populated with the group and data
collector associated with the link and workspace you selected in the Tivoli
Enterprise Portal.
For every server group, the table shows the group name, description, and a Delete
button.
To modify a server group (including list of member servers and access rights for
users), click the group name. See “Modifying a group” on page 51.
To delete a server group, click the Delete button in its row. See “Deleting a group”
on page 51.
To create a server group with default settings, no member servers and no user
access rights, in the left navigation pane, click Create Group. See “Creating a
group.”
To create a server group with settings, member servers and user access rights
copied from another server group, in the left navigation pane, click Duplicate
Group. See “Duplicating a group” on page 52.
Creating a group
About this task
Combine servers into groups to streamline daily server maintenance. The Create
Group page provides the functionality to create groups of servers and grant users
access to those groups.
To create a group:
1. From the top navigation, click Administration > Server Management >
Server Groups. The Server Group Management page opens.
2. On the left navigation pane, click Create Group. The Create Group page
opens.
3. Enter a unique group name in the text box.
4. Enter a description in the text box.
5. Enter the Server Group Response Time Thresholds.
6. Enter the Portal Response Time Thresholds. (If you have a portal server,
configure the thresholds for portal.) Optional.
7. Click to select a baseline definition and fill out the information. Steps 5
through 7 are all default settings based on the settings on the System
Properties page under Configuring the Enterprise Overview Display section.
8. Click to select the server name in the All Servers box.
50
ITCAM for Application Diagnostics: User Guide
9. Click Add to select the server for the group. The server name appears in the
Servers in Group box. To select multiple servers, hold down the shift key
during your selection. To add multiple servers non-continuously, Ctrl + click
the servers for selection.
10. In the Servers In Group box, select the server you want to remove and click
Remove to delete the server from the group. The server name disappears from
the Servers in Group box.
11. Select the user and click Add to grant users access to the group. The user
name appears in the Granted Access box.
12. Click Remove to remove the user's access to the group. The user name
disappears from the Granted Access box.
13. Click Save to save the group's settings.
Related topics
Configuring a data collector
Configuring the Enterprise Overview display
Creating a configuration
Modifying a group
About this task
Maintain your groups with the most updated information. The Modify Group page
provides the functionality to modify your groups and grant users access to those
groups.
To modify a group:
1. From the top navigation, click Administration > Server Management > Server
Groups. The Server Group Management page opens.
2. Click the group name of the group you want to modify. The Modify Group
page opens populated with the selected group's information.
3. Select the field you want to edit and enter the new information.
4. Click Save to save the group's settings. Changes made to the server-to-group
assignments and user-to-group grants occur immediately. Also, if an
administrator removes a server from a group anyone logged in will notice the
change.
Related topics
Configuring the Enterprise Overview display
Creating a group
Deleting a group
About this task
Delete outdated groups from the system. You can delete existing groups on the
Server Group Management page.
To delete a group:
1. From the top navigation, click Administration > Server Management > Server
Groups. The Server Group Management page opens.
2. Click X or Delete next to the group name you want to delete from the
application monitor.
3. Click OK in the confirmation box to delete the group, or click Cancel to return
to the Server Group Management page.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
51
4.
If you select OK, the application monitor deletes the group and the Server
Group Management page no longer displays the deleted group. Before deleting
a group from the application monitor database, delete all reports attached to
that group in order to maintain data integrity. To delete each report, click the
report's link. The group will be deleted after all reports are deleted.
Once a group is deleted, the records in the application monitor database that
belong to the group via the server relationship will no longer be accessible
through the group. However, the records can still be accessed either via the
server name or another group which contains the servers. You can also
re-assign the servers to other groups on the Modify Group page.
Related topics
Deleting a configuration
Modifying a group
Duplicating a group
About this task
Save time by duplicating groups. Duplicating a group allows you to quickly create
a new group based on the settings of an existing group.
To duplicate a group:
1. From the top navigation, click Administration > Server Management > Server
Groups. The Server Group Management page opens.
2. On the left navigation pane, click Duplicate Group. The Duplicate Group page
opens.
3. From the Group Name list box, select the group name you want to duplicate.
4. Enter a new name for the duplicated group.
5. Click Save to duplicate the group. The Duplicate Group link does not display
when there is no group in the system.
Related topics
Creating a group
Deleting a group
Modifying a group
Data Collector Configuration
In the Data Collector Configuration pages, you can configure Data Collectors,
disable, enable, and unconfigure them, and also enable/disable TTAPI support.
To view the Data Collector Configuration page, from the top navigation, click
Administration > Server Management > Data Collector Configuration.
A Data Collector is software that runs within the same JVM as the application
server and captures information regarding the applications running inside the
application server. The Data Collector communicates this information to the
Managing Server and/or to the Tivoli Enterprise Monitoring Agent.
To work with the Managing Server, a Data Collector must first be configured using
its own configuration utility. After this, you also need to configure the Data
Collector through the Visualization Engine. To do this, you need to apply one of
the defined configurations to this Data Collector.
52
ITCAM for Application Diagnostics: User Guide
You might also need to unconfigure a Data Collector. When you have
unconfigured a Data Collector, you can apply a different configuration, or if you
want to remove the Data Collector, you can unconfigure it and then uninstall it.
To view the configured Data Collectors, enable, disable, and unconfigure them,
select Configured Data Collectors in the left navigation pane. See “Configured
Data Collectors.”
To view the unconfigured Data Collectors and configure them, select Unconfigured
Data Collectors in the left navigation pane. See “Unconfigured Data Collectors” on
page 54.
To view the existing Data Collector configurations, modify, duplicate and delete
them, select Configuration Library in the left navigation pane. See “Configuration
Library” on page 54.
To create a new Data Collector configuration, select Create a Configuration in the
left navigation pane. See “Creating a configuration” on page 58.
Configured Data Collectors
The Configured Data Collectors page shows a table of all Data Collectors that are
configured in the Visualization Engine. You can view their configuration, enable,
disable, and unconfigure them.
For every configured Data Collector, the table shows:
v Admin Server name
v Application Server name
v Cluster name
v Configuration name
v Platform that is monitored (type of application server)
v Status change button (Disable if the Data Collector is enabled, or Enable if it is
disabled)
v Unconfigure check box.
v Join Time - if a Data Collector is not available because the Data Collector
connection to the Managing Server was unconfigured, then the value for Join
Time is displayed as N/A.
To disable an enabled Data Collector, click the Disable button. See “Disabling a
data collector” on page 57.
To enable a disabled Data Collector, click the Enable button. See “Enabling a data
collector” on page 56.
To unconfigure a Data Collector, check the Unconfigure box and click the Apply
button at the bottom of the table. See “Unconfiguring a data collector” on page 56.
To view the details of a Data Collector configuration, click the configuration name.
The “Configuration Library” on page 54 page will open, showing this
configuration.
You can use the left navigation pane to view unconfigured Data Collectors, view
existing Data Collector configurations, create a configuration, and enable TTAPI.
See “Data Collector Configuration” on page 52.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
53
Unconfigured Data Collectors
The Unconfigured Data Collectors page shows a table of all Data Collectors that
communicate with the Managing Server but are not configured in the Visualization
Engine. You can configure them.
For every unconfigured Data Collector, the table shows:
v Admin Server name
v Application Server name
v Cluster Name
v Platform that is monitored (type of application server)
v Apply a configuration check box
To configure a Data Collector, check the Apply a configuration box, select the
configuration name in the pull down control at the top of the table, and click the
Apply button at the bottom of the table. See “Configuring a data collector” on
page 55.
You can use the left navigation pane to view configured Data Collectors, view
existing Data Collector configurations, create a configuration, and enable TTAPI.
See “Data Collector Configuration” on page 52.
Configuration Library
The Configuration library page shows a table of all Data Collector configurations.
You can apply configurations to Data Collectors, modify them, delete them, and
create new configurations as copies of existing ones.
For every Data Collector configuration, the table shows:
v Configuration name.
v Class names that are to be excluded from monitoring.
v Class names that are to be included in monitoring, even if they would fit the
exclude list.
v Associated Server names, that is, names of servers to which the configuration is
presently applied
v Modify, Duplicate, Apply, and Delete buttons.
To modify a configuration, click the Modify button. See “Modifying a
configuration” on page 59.
To create a new configuration as a copy of an existing one, click the Duplicate
button. See “Duplicating a configuration” on page 59.
To apply a configuration to Data Collectors, click the Apply button. Note that you
can configure a previously unconfigured Data Collector or change the
configuration of an already configured Data Collector in this way. See “Applying a
configuration” on page 58.
To delete a configuration, click the Delete button. See “Deleting a configuration”
on page 60.
You can use the left navigation pane to view configured and unconfigured Data
Collectors, create a configuration, and enable TTAPI. See “Data Collector
Configuration” on page 52.
54
ITCAM for Application Diagnostics: User Guide
Enable TTAPI for JDBC
The Enable TTAPI for JDBC page shows tables of Data Collectors that support
TTAPI for JDBC and do not currently have it enabled, and those that have TTAPI
for JDBC enabled. You can enable and disable TTAPI for JDBC for these Data
Collectors.
The TTAPI JDBC disabled Data Collectors table shows the Data Collectors that
support TTAPI for JDBC and do not currently have it enabled. For every Data
Collector, the server name and the Enable check box are shown.
To enable TTAPI for JDBC for a Data Collector, check the Enable box and click the
Apply button at the bottom of the table. See “Enabling TTAPI for JDBC for a Data
Collector” on page 60.
The TTAPI JDBC enabled Data Collectors table shows the Data Collectors that
support TTAPI for JDBC and do not currently have it enabled. For every Data
Collector, the server name and the Enable check box are shown.
To enable TTAPI for JDBC for a Data Collector, check the Enable box and click the
Apply button at the bottom of the table. See “Disabling TTAPI for JDBC for a Data
Collector” on page 60.
Configuring a data collector
About this task
When a new data collector connects to a managing server for the first time, it is
automatically configured.
If there are data collectors that you want to manually configure, you need to
ensure that for those data collectors, the dc.autoconfigure property in the
dc.properties file is set to false.
For Data Collectors that you wish to manually configure, you can assign an initial
configuration using the Data Collector Configuration page in MSVE. When the
data collector acknowledges the new configuration, the managing server then lists
it as a "configured" data collector. You can also return a currently configured data
collector to an unconfigured state. If this is done, all data and reports concerning
the data collector are lost. After a data collector has been configured, you can
enable or disable it at any time.
For WebSphere v6, the data collector name is formed from the admin server name
(node name) and the application server instance name, the data collector
application server name also includes the profile name.
Here is an example of a WebSphere v6 profile name:
jupiterCell01.jupiterNode01.server1(default).
In many places, an additional field is appended to the end of the data collector
name that indicates whether the data collector is associated with a currently
running application server instance or not. When the application server instance
and data collector are running, this field is the process or address space identifier:
jupiterCell01.jupiterNode01.server1.12345. When the data collector is not running
and there is no process or address space identifier, two dashes (--) are used, for
example: jupiterNode01.server1.-To configure a data collector:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
55
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Unconfigured Data Collectors on the left navigation pane.
3. Select a configuration from the Apply a Configuration list box.
4. Click Select All or click in the check box of the unconfigured data collector you
want to configure.
5. Click Apply.
The apply procedure can take a minute or two for the data collector to receive,
successfully apply, and acknowledge its success back to the managing server.
You will need to refresh your page every 10-20 seconds until the data collector
disappears from the Unconfigured Data Collector's table.
Related topics
Applying a configuration
Modifying a configuration
Unconfiguring a data collector
Unconfiguring a data collector
About this task
Use the Data Collector Overview page to unconfigure the data collectors. When
you unconfigure a data collector, the system removes it from the configured data
collectors list and displays it with the unconfigured data collectors.
The name of the Data Collector is a combination of the admin server name and the
application server name i.e., admin_server.application_server. The name cannot be
changed.
To unconfigure a data collector:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Place a check in the Unconfigure check box next to the data collector you want
to unconfigure.
3. Click Apply. The Unconfigured Data Collector Overview page displays.
Related topics
Applying a configuration
Configuring a data collector
Enabling a data collector
Enabling a data collector
About this task
Enable your data collectors on the Configured Data Collector Overview page.
Manage monitoring on your system by enabling and disabling data collectors as
needed.
To enable a data collector:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Enable next to the data collector you want to enable.
3. The system enables the data collector and the button face changes to Disable. If
you stopped the data collector from sending and receiving data by disabling it,
56
ITCAM for Application Diagnostics: User Guide
you can enable the data collector again when you are ready. Since a disabled
data collector doesn't lose settings, you can simply turn it back on without any
reconfiguration.
Related topics
Configuring a data collector
Disabling a data collector
Modifying a configuration
Disabling a data collector
About this task
Disable your data collectors on the Configured Data Collector Overview page.
Manage monitoring on your system by enabling and disabling data collectors as
needed.
To disable a data collector:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Disable next to the data collector you want to disable.
3. The system disables the data collector and the button face changes to Enable.
Results
Disabling a Data Collector in the Visualization Engine only disables monitoring
with the Managing Server; IBM Tivoli Monitoring is not affected. You can also use
the Data Collector configuration to disable communication between the Data
Collector and the Managing Server. The following table provides a comparison
between these two ways of disabling Data Collector communication to the
Managing Server:
Table 4. Comparison of ways to disable Data Collector communication to the Managing
Server.
Disable Data Collector communication to
the Managing Server using Data Collector
configuration
Disable Data Collector communication to
the Managing Server using the
Visualization Engine
The application server instance is not listed
in the Visualization Engine.
The application server instance remains
listed in the Visualization Engine.
The Visualization Engine shows no
information on the application server
instance.
The Visualization Engine shows whether the
application server instance is up or down;
monitoring information is not available.
No system or network resources are used for Some system and network resources are
Managing Server communication.
used to maintain Managing Server
communication.
You do not need to apply maintenance fixes
for the Agent that only impact Managing
Server communication.
You need to apply maintenance fixes for the
Agent that only impact Managing Server
communication.
In order to re-enable communication, you
need to perform Data Collector
configuration again, and restart the
application server.
In order to re-enable communication using
the Visualization Engine, you do not need to
restart the application server.
Related topics
Configuring a data collector
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
57
Enabling a data collector
Modifying a configuration
Creating a configuration
About this task
Use this page to create a configuration and name it for your data collectors. Create
multiple configurations that monitor different classes.
The system assigns a name to the data collector. The name of the Data Collector is
a combination of the Admin Server name and the Application Server name. The
name cannot be changed.
To create a configuration:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Create a Configuration on the left navigation pane. The Create page
opens.
3. Enter the names of classes you want to ignore into the Exclude (Classname) list.
You can use an asterisk (*) as a wildcard. In this case it means exclude all.
4. Enter the names of classes you want to monitor into the Exclude Override
(Classname) list.
5. Select the check box if you want to enable MQ. This will provide you with an
Exclude and Exclude Override box specifically for configuring MQ.
6. Enter a name for the configuration. (Required field)
7. Click Save to create the configuration or Save & Apply to create the
configuration and apply it to a data collector. You can configure or change
these options at any time.
Related topics
Applying a configuration
Configuring a data collector
Applying a configuration
About this task
Use the Apply page to apply the configuration to a data collector. After you create
a configuration, you must apply it to a data collector in order to start monitoring.
To apply a configuration:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Configuration Library on the left navigation. The Data Collector
Configuration List page opens.
3. Click the Apply icon next to the configuration you want to apply. The Apply
page opens.
4. Click to select the data collectors' name from the All Data Collectors box. To
select a range of contiguous data collectors, hold the shift key down during
your selection. To add multiple servers non-contiguously, Ctrl + click the
servers for selection.
5. Click Add to apply the configuration to the data collector. The Data Collector's
names displays in the Applied box.
6. Select Enable from the Status list box to set the status of the configuration.
58
ITCAM for Application Diagnostics: User Guide
7. Click Apply.
Related topics
Disabling a data collector
Enabling a data collector
Unconfiguring a data collector
Modifying a configuration
About this task
You can modify an existing configuration for your data collectors by updating the
list of classes you monitor. Remove and add classes to the Exclude (Classname) list
and Exclude Override (Classname) list to change what you monitor.
To modify a configuration:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Configuration Library on the left navigation pane. The Data Collector
Configuration List page opens.
3. Click the Modify icon next to the configuration you want to modify. The
Modify page opens.
4. Enter the names of classes you want to ignore into the Exclude (Classname) list.
5. Enter the names of classes you want to monitor into the Exclude Override
(Classname) list.
6. Select the check box to enable MQ list.
7. Click Save to save your modifications to the configuration. The Configured
Data Collector Configuration List displays with the updated information.
Related topics
Applying a configuration
Configuring a data collector
Enabling a data collector
Duplicating a configuration
About this task
Create a new configuration using an existing configuration from your data
collectors.
To duplicate a configuration:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Configuration Library on the left navigation pane. The Configured Data
Collector Configuration List page opens.
3. Click the Duplicate icon next to the configuration you want to duplicate. The
Duplicate Configuration page opens.
4. Select an existing configuration from the list box.
5. Enter a new name for the configuration.
6. Click Save. The new configuration displays in the Configuration List.
Related topics
Applying a configuration
Configuring a data collector
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
59
Enabling a data collector
Deleting a configuration
About this task
You can delete outdated configurations from the list to keep your list current.
To delete a configuration:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Configuration Library on the left navigation pane. The Data Collector
Configuration List page opens.
3. Click the Delete icon next to the configuration you want to delete. A
confirmation box appears to warn you that deleting this configuration will
unconfigure all the associated servers.
4. Click OK to delete the configuration. The Configuration List displays without
the deleted configuration. Remember to apply a new configuration to the
servers you unconfigured while deleting the configuration.
Related topics
Applying a configuration
Configuring a data collector
Enabling a data collector
Modifying a configuration
Enabling TTAPI for JDBC for a Data Collector
About this task
For Data Collectors that support TTAPI for JDBC, enable it on the Enable TTAPI
for JDBC page.
To enable TTAPI for JDBC for a Data Collector:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Enable TTAPI for JDBC on the left navigation menu.
3. Click in the Enable check box next to the data collector for which you want to
enable TTAPI for JDBC.
4. Click the Apply button at the bottom of the table.
Related tasks
“Disabling TTAPI for JDBC for a Data Collector”
Related topics
Disabling TTAPI for JDBC for a Data Collector
About this task
For Data Collectors that have TTAPI for JDBC enabled, disable it on the Enable
TTAPI for JDBC page.
To disable TTAPI for JDBC for a Data Collector:
1. From the top navigation, click Administration > Server Management > Data
Collector Configuration. The Configured Data Collector Overview page opens.
2. Click Enable TTAPI for JDBC on the left navigation menu.
60
ITCAM for Application Diagnostics: User Guide
Click in the Disable check box next to the data collector for which you want
to enable TTAPI for JDBC.
4. Click the Apply button at the bottom of the table.
Related tasks
“Enabling TTAPI for JDBC for a Data Collector” on page 60
Related topics
3.
Data Collector Profiles
A data collector profile is a collection of multiple configuration changes that can be
stored together and applied to a data collector. You can use the Data Collector
profiles feature to modify the data collector properties file and toolkit files on a
data collector, from the Managing Server Visualization Engine. It is still possible to
modify these files when configuring a data collector. Data Collector profiles can be
installed on monitored application servers running ITCAM for WebSphere/J2EE
Data Collector 6.1 FP4 or higher. For more information, refer to the ITCAM for
Application Diagnostics - Agent for WebSphere Installation and Configuration Guide.
From the Managing Server Visualization Engine, you can check which data
collector profiles are installed on which data collector. You can add and remove
profiles to and from data collectors. You can also import and export data collector
profiles from other managing servers. If you change a data collector profile it must
be reinstalled on the data collector and the data collector needs to be restarted for
the changes to take effect.
You can access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The Data Collector profiles page displays a list of existing profiles if profiles have
been created already. Click a profile name to view which data collectors are using
that profile. The DC Profiles Menu contains a list of configurable items that you
can modify on each profile.
For more information see:
v “Viewing and editing data collector profiles”
v “Exporting a data collector profile” on page 64
v “Importing a data collector profile” on page 63
v
v
v
v
“Adding and removing data collector profiles” on page 62
“Configuring a data collector profile” on page 64
“Installing a profile on a data collector” on page 71
“Uninstalling a data collector profile” on page 72
Viewing and editing data collector profiles
You can view and edit profiles at any stage. You can also edit data collector
profiles while they are assigned to a data collector.
Access the Data Collector Profiles using one of the following methods:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
61
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
on the Active Requests tab or the Recent Requests
Click the toolbox icon
tab.
1. The Data Collector profiles page displays a list of existing profiles if profiles
have been created already.
2. Click a profile name to view which data collectors are using that profile.
3. In the DC Profiles Menu, click the individual configuration items to view the
details of each item.
4. For more information about the configuration items and how to edit them see
“Configuring a data collector profile” on page 64.
5. In the DC Profiles Menu, you can click Data Collectors to view a list of data
collectors available.
6. When you click on a data collector name you can also click Profiles Installed
to view the profiles assigned to the data collector.
7. If you are editing a profile, select a configuration item from the Profiles list in
DC Profiles Menu, click Apply then click Save to add the changes to the
profile.
When you edit a profile that is assigned to a data collector, the status of the profile
changes to Outdated in the Profiles Installed list. To implement the updated
profile changes on the data collector you need to reinstall the profile on the data
collector. For more information see “Installing a profile on a data collector” on
page 71. Then the Data Collector needs to be restarted for the changes to take
effect.
See also:
v “Data Collector Profiles” on page 61
v “Exporting a data collector profile” on page 64
v “Importing a data collector profile” on page 63
v “Adding and removing data collector profiles”
v “Uninstalling a data collector profile” on page 72
Note: If you click refresh or F5 on your browser from any page in Data Collector
Profiles, you will return to the main Data Collector Profiles page.
Adding and removing data collector profiles
You can add or remove data collector profiles at any stage.
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The page has two main areas; the DC Profiles Menu and the Profiles area of the
page. You can use the DC Profiles Menu to edit, add, and remove configurable
items from profiles. You can use the Profiles area of the page to add, edit, and
remove data collector profiles.
62
ITCAM for Application Diagnostics: User Guide
v Click Profiles to view a list of existing profiles.
v Click DC Profiles Menu to view a list of available data collectors.
1. To add a profile, click New.
2. In the Name field, type the name you want to give the profile.
3. Click Apply.
4. In the DC Profiles Menu, click the items you want to configure to add to this
profile.
5. For more information see “Configuring a data collector profile” on page 64.
6. Then click Save to add the profile to the list of Data collector profiles.
7. To delete a profile select the check box then click Delete.
When you delete a profile that is assigned to a data collector the status of the
profile changes to Outdated in the Profiles Installed list. The Data Collector needs
to be restarted for the changes to take effect.
See also:
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v “Exporting a data collector profile” on page 64
v “Importing a data collector profile”
v “Configuring a data collector profile” on page 64
v “Installing a profile on a data collector” on page 71
v “Uninstalling a data collector profile” on page 72
Importing a data collector profile
You can import a data collector profile from other locations for use on other
managing servers.
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
on the Active Requests tab or the Recent Requests
Click the toolbox icon
tab.
1. The Data Collector profiles page displays a list of existing profiles if profiles
have been created already.
2. Click Browse to locate the .xml file you want to import.
3. Select the .xml file and click Open.
4. Select the profile you want to overwrite by selecting the check box in the Select
column.
5. Click Import.
6. If you are importing a file with the same profile name a message displays.
Click OK to overwrite the existing profile.
7. If you are importing a new file, then a new profile is created.
See also:
v “Installing a profile on a data collector” on page 71
v “Uninstalling a data collector profile” on page 72
v “Data Collector Profiles” on page 61
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
63
v
v
v
v
“Viewing and editing data collector profiles” on page 61
“Exporting a data collector profile”
“Adding and removing data collector profiles” on page 62
“Configuring a data collector profile”
Exporting a data collector profile
You can export data collector profiles to other locations for use on other managing
servers.
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
on the Active Requests tab or the Recent Requests
Click the toolbox icon
tab.
1. The Data Collector profiles page displays a list of existing profiles if profiles
have been created already.
2. Select the profile by selecting the check box in the Select column.
3. Click Export to launch an .xml version of the profile in your browser.
4. From the browser menu, click File> Save as and select the location you want to
export the file to.
5. Then close the browser.
See also:
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v “Importing a data collector profile” on page 63
v
v
v
v
“Adding and removing data collector profiles” on page 62
“Configuring a data collector profile”
“Installing a profile on a data collector” on page 71
“Uninstalling a data collector profile” on page 72
Configuring a data collector profile
When you are creating a profile there are a number of items you can configure.
You can select the items you want to configure, not all items are required to be
configured. You can also modify existing items. When you have configured a
profile you can install it on one or more data collectors.
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The Data Collector profiles page displays a list of existing profiles if profiles have
been created already. Click on the Profile, a list of configurable items displays in
the DC Profiles Menu.
64
ITCAM for Application Diagnostics: User Guide
Click on the following links for more details on configuring each item in a data
collector profile.
v “PMI” (WebSphere products only)
v “Custom Request” on page 66
v “Custom L2” on page 67
v “Method Entry and Exit” on page 68
v “Lock Analysis” on page 69
v “Memory Diagnosis” on page 69
v “Custom MBeans” on page 70
v “Tuning Parameters” on page 71
See also:
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v
v
v
v
v
“Adding and removing data collector profiles” on page 62
“Importing a data collector profile” on page 63
“Exporting a data collector profile” on page 64
“Installing a profile on a data collector” on page 71
“Uninstalling a data collector profile” on page 72
PMI:
This feature is available for WebSphere products only. Standard WebSphere
Application Server PMI modules are automatically included in monitored JVM and
are rendered on the Managing Server Visualization Engine. If your environment is
using WebSphere Process Server or WebSphere Commerce, the PMI modules
associated with these products are not rendered to the Managing Server
Visualization Engine. You can use this feature to add the PMI module names for
these products to data collector profiles.
For information about the PMI module names for these products, refer to the
following documentation links:
v WebSphere Commerce http://publib.boulder.ibm.com/infocenter/wchelp/
v6r0m0/index.jsp
v WebSphere Process Server http://publib.boulder.ibm.com/infocenter/
dmndhelp/v6r2mx/topic/com.ibm.websphere.wps.620.doc/welcome_wps.html
To add a PMI module to a data collector profile, choose one of the following
options to access the PMI feature:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The Data Collector profiles page displays a list of existing profiles if profiles have
been created already.
1. Click the profile Name.
2. In the DC Profiles Menu, click PMI.
3. In the PMI Module Name field, type the module name add a custom PMI
module.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
65
Note:
This information applies to WebSphere products only.
4. Click Apply or Save to implement the changes to the profile.
When the PMI module name is added to the profile, the next step is to install the
profile on a data collector. When the Managing Server is restarted, the PMI module
displays on the Managing Server Visualization Engine System Resource page,
when the corresponding data collector is selected.
See also:
v “Custom Request”
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v “Adding and removing data collector profiles” on page 62
v “Installing a profile on a data collector” on page 71
v “Uninstalling a data collector profile” on page 72
Custom Request:
A custom request is an application class and method that you designate as an edge
or nested request. This feature defines custom request methods and classes that are
included in L2 Method Trace.
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The Data Collector profiles page displays a list of existing profiles if profiles have
been created already.
1. Click the profile Name.
2. In the DC Profiles Menu, click Custom Request.
3. Click New.
4. Complete the following fields:
v Request Name: Identifies the unique name for this request. The request
name is displayed in the L1 or L2 trace entry that is produced when one of
the methods identified by this custom request runs.
v Class Name: Identifies the name of the class.
v Method Name: Identifies the names of the methods within one of the classes
that are to be Byte-Code-Instrumented for custom request processing.
5. Select the Type by clicking one of the following options:
a. Class
b. Superclass
c. Interface
6. Click OK to save the Custom Request.
7. To edit a custom request, click Custom Request and edit the fields on display,
click Save to implement the changes to the profile.
66
ITCAM for Application Diagnostics: User Guide
8. To delete a custom request from a data collector profile, on the Profile Custom Requests page select the check box in the select column, then click
Delete.
See also:
v “Custom L2”
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v “Adding and removing data collector profiles” on page 62
v “Installing a profile on a data collector” on page 71
v “Uninstalling a data collector profile” on page 72
Custom L2:
The data collector uses a technique called Byte Code Instrumentation (BCI) to
collect data from various types of J2EE APIs that typically operate as nested
requests. BCI is automatically enabled for these types of APIs. You can use Custom
L2 to enable and disable L2 instrumentation components if you want to lower the
monitoring workload on the data collector. You can also define new L2 events
using the Custom L2 events option.
1. Click the profile Name.
2. In the DC Profiles Menu, click Custom L2. You can enable or disable the
following events:
v SERVLET
v
v
v
v
v
v
v
v
v
v
v
3.
4.
5.
6.
JDBC (Java Database Connectivity)
JMS (Java Message Service)
HTTP Session Count
CTG (CICS® Transaction Gateway)
JDO ( Java Data Objects)
MQI (Message Queue Interface)
EJB (Enterprise Java Beans)
JNDI (Java Naming and Directory Interface)
JCA (Java Connector Architecture)
Axis Web Service (JBoss and Weblogic)
IMS
v RMI (Resource Manager Interface)
Select the check box to enable an event.
Clear the check box to disable an event.
To add Custom L2 events In the Custom L2 event area of the page click New.
In the Event Type drop down menu, select one of the following options to
enable or disable the instrumentation:
v SERVLET
v EntityBean
v SessionBean
v Message Driven Bean
7. Type the Class Name.
8. Select the Enabled check box to save the event.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
67
9. On the main page select the check box to assign the custom event to the
profile.
10. Click Apply, click Save.
v To edit an L2 custom event, click the Event Type, add the changes click Apply,
click Save.
v To delete an L2 custom event, select the check box for the Event Type, click
Delete.
See also:
v “Method Entry and Exit”
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v “Adding and removing data collector profiles” on page 62
v “Installing a profile on a data collector” on page 71
v “Uninstalling a data collector profile” on page 72
Method Entry and Exit:
You can use this item to select classes to include or exclude on the monitored JVM
used for classes and methods in L3 methods traces.
1.
2.
3.
4.
In the DC Profiles Menu, click Method Entry/Exit.
A list of existing classes assigned to the profile display.
Click New to add a new class to the profile.
From the Lookup Sever drop-down menu, select the server.
5.
6.
7.
8.
A list of available classes display.
Click a file to expand the view and see the classes.
Select the check boxes associated with the classes you want to add click Add.
Click Save to add the classes to Method Trace Entry and Exit.
9. To remove a class, select the check box for the class you want to remove then
click Apply and Save.
To create a class to add to Method Entry/Exit.
Type Class Name.
Type the New Method Name.
Click Add to display the class.
Select the check box then click Apply to add the class to the list of existing
classes for Method Exit Entry.
5. From the list select the check boxes for the classes that you want to add.
6. Click Save.
v To edit a class, in the Method Entry/Exit page, click the Class Name, add the
changes then click Apply.
v To remove a class, select the check box for the class then click Delete then click
Save.
1.
2.
3.
4.
See also:
v “Lock Analysis” on page 69
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
68
ITCAM for Application Diagnostics: User Guide
v
v
v
v
“Viewing and editing data collector profiles” on page 61
“Adding and removing data collector profiles” on page 62
“Installing a profile on a data collector” on page 71
“Uninstalling a data collector profile” on page 72
Lock Analysis:
You can use this feature to probe classes for lock analysis. All application classes
are included by default. You can access these classes from the Lookup Server. Use
the add option to add new entries containing classes or methods to be included or
excluded for lock analysis.
1. In the DC Profiles Menu, click Lock Analysis.
2. From the Lookup Sever drop-down menu, select the server.
3. A list of available classes display.
4. Click a file to expand the view and see the classes.
5. Select the check boxes associated with the classes you want to add click Add.
6. Click Save to add the classes to Lock Analysis.
Use the following steps to add a class:
1. To add a class, in the DC Profiles menu, click Lock Analysis.
2. Type New Class Name.
3. Click Add.
4. In theClasses to Monitor list, select the check box then click Apply and then
Save to add the class to Lock Analysis.
5. To remove a class, select the check box for the class you want to remove then
click Delete then click Apply and Save.
See also:
v “Memory Diagnosis”
v “Configuring a data collector profile” on page 64
v
v
v
v
v
“Data Collector Profiles” on page 61
“Viewing and editing data collector profiles” on page 61
“Adding and removing data collector profiles” on page 62
“Installing a profile on a data collector” on page 71
“Uninstalling a data collector profile” on page 72
Memory Diagnosis:
You can use this feature to select classes to use in Memory diagnosis. All memory
classes are included for memory leak diagnosis in L3 mode by default. Memory
diagnosis can be restricted to a selected combination of allocating and allocated
classes.
1. In the DC Profiles Menu, click Memory Diagnostic.
2. To add heap allocation classes click New.
3. In the New Allocating Class Name field, type the name of the class that
allocates objects to Memory Diagnosis. New Allocating Class Name identifies
the name of a class or classes to be modified.
4. In the New Allocated Class Name field, type the name of the class allocated to
include in the Memory Diagnosis. The New Allocated Class Name identifies
the specific heap allocation requests within the class or classes.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
69
5. Click Add to add the class to the Allocated Classes to monitor list.
6. In the Allocated classes to monitor list, select the check box for the class name
you want to add to the Allocating classes.
7. Click Apply and Save to save the class to the Heap Allocations list.
8. To remove a class from theAllocated Classes to monitor list, select the check
box then click Delete then click Apply and Save to implement the changes.
v To edit a class, from the Heap Allocations list, click the class name, make the
necessary changes then click Apply and Save.
v To delete a class from the Heap Allocations list, select the check box then click
Delete then click Apply and Save to implement the changes.
See also:
v “Custom MBeans”
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v “Adding and removing data collector profiles” on page 62
v “Installing a profile on a data collector” on page 71
v “Uninstalling a data collector profile” on page 72
Custom MBeans:
You can include MBeans to be rendered on the System resource page on the
Managing Server Visualization Engine. You can add new entries or use the lookup
server drop down menu to query existing beans and select attributes.
1. In the DC Profiles Menu, click Custom MBeans to display the Profile Custom
MBean page.
2. Use the following steps to manually add Custom MBeans to the Managing
Server.
3. Domain: Type the Domain name.
4. Object Name; Type the MBean Object Name.
5. Category: Type the unique Category Name (used by ITCAM).
6. Select the Retrieve all Attributes check box if you want to add all attributes
associated with the MBean.
7. Attribute Name: Type the name of the attribute.
8. Mapped Key Name: Type the unique key string to map the attribute (used by
ITCAM).
9. Object Name Pattern: Type the MBean pattern to search in the form.
10. Click Add to add the MBean to the list.
To add MBeans from the Look up Server drop-down menu use the following
steps:
1. From the Look up Server drop-down menu, select the application server.
2. From the Select MBean drop-down menu, select the MBean you want to add.
3. From the Select Attributes drop-down menu, select the attribute you want to
add.
4. Click Apply to add the Custom MBeans to the list.
5. From the Custom MBeans list, select the check boxes for the Custom MBeans
you want to add to the data collector profile.
70
ITCAM for Application Diagnostics: User Guide
6. Click Apply then click Save.
v To edit a Custom MBeans from the Custom MBeans list, click the MBean
Object name, make the necessary changes then click Apply and Save.
v To delete a Custom MBeans from the Custom MBeans list, select the check box
then click Delete then click Apply and Save to implement the changes.
See also:
v “Tuning Parameters”
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v
v
v
v
“Viewing and editing data collector profiles” on page 61
“Adding and removing data collector profiles” on page 62
“Installing a profile on a data collector”
“Uninstalling a data collector profile” on page 72
Tuning Parameters:
You can configure tuning parameters and apply then to the data collector profiles
on the data collectors.
Note: Data Collector Tuning parameters cannot be reversed by uninstalling the
profile, However, they can be modified back to the original value.
1. In the DC Profiles Menu, click Tuning Parameters.
2. From the Tuning Parameters drop-down menu, select the parameter you want
to add.
3. Repeat this process for each parameter you want to add.
4. Detailed information relating to each parameter you select displays in the
Selected Tuning Parameters page.
5. When a selected parameter displays in the list, type a value in the Value
column for each parameter.
6. Click Apply and then click Save to add the parameters to the data collector
profile.
7. Select the check box to add a parameter to the data collector profile. Click
Apply then Save.
8. To remove a parameter, select the check box then click delete and then Save to
remove a parameter from the profile.
See also:
v “Configuring a data collector profile” on page 64
v
v
v
v
v
“Data Collector Profiles” on page 61
“Viewing and editing data collector profiles” on page 61
“Adding and removing data collector profiles” on page 62
“Installing a profile on a data collector”
“Uninstalling a data collector profile” on page 72
Installing a profile on a data collector
When you create a data collector profile, the next step is to add it to a data
collector. You then need to restart the managing server for the changes to take
effect.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
71
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The Data Collector profiles page displays a list of existing profiles if profiles have
been created already.
1. Click the profile name to view the list of data collectors assigned to that profile.
2. If you want to view details of the profile, from the DC Profiles Menu, click the
configurable items.
3. To assign a profile to a Data Collector, from the DC Profiles Menu, click Data
Collectors to view all the available data collectors.
4. Select the check box in the Select column of each data collector you want to
add a new profile to.
5. Click Install to display the list of data collector profiles available.
6. Select the check box in the Select column of the profile you want to add.
7. Click Merge if you want to retain any manual entries made by manually
editing the xml and the properties file as well as the changes made to the
profile.
8. Click Overwrite to remove all manual changes and to replace them with the
changes in the data collector profile.
9. If you are reinstalling an updated version of an existing profile, click Overwrite
to update the profile on the data collector. You will need to restart the
managing server for all changes to take effect.
See also:
v “Uninstalling a data collector profile”
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v
v
v
v
v
“Viewing and editing data collector profiles” on page 61
“Adding and removing data collector profiles” on page 62
“Importing a data collector profile” on page 63
“Exporting a data collector profile” on page 64
“Uninstalling a data collector profile”
Uninstalling a data collector profile
You can uninstall a data collector profile from a data collector at any stage. You
then need to restart the managing server for the changes to take effect.
Access the Data Collector Profiles using one of the following methods:
v From the main menu, click Administration > Server Management > Data
Collector Profiles.
v From the main menu, click Problem Determination > Server Activity Display.
Click the toolbox icon
tab.
on the Active Requests tab or the Recent Requests
The Data Collector profiles page displays a list of existing profiles if profiles have
been created already.
72
ITCAM for Application Diagnostics: User Guide
1. From the DC Profiles Menu, click Data Collectors to view all the available
data collectors. Click Refresh list update the current list of available data
collectors
2. Click a data collector name to view the list of profiles assigned to the data
collector.
3. Select the check box in the Select column of the profile you want to remove.
4. Click Uninstall to remove the profile from the data collector.
5. You then need to restart the managing server for the changes to take effect.
See also:
v “Configuring a data collector profile” on page 64
v “Data Collector Profiles” on page 61
v “Viewing and editing data collector profiles” on page 61
v
v
v
v
“Adding and removing data collector profiles” on page 62
“Importing a data collector profile” on page 63
“Exporting a data collector profile” on page 64
“Installing a profile on a data collector” on page 71
Monitoring on Demand (TM)
In the Monitoring on Demand (MOD) pages, you can view and adjust the
monitoring level for all servers, and schedule adjustment of this level at fixed
times.
To view the Monitoring on Demand page, from the top navigation, click
Administration > Monitoring on Demand. You can also access this page from the
toolbox icon
on the Server Activity Display page.
The Modify Server Settings page is displayed. You can use this page to change
the selected Data Collector's monitoring level, select a different schedule, or change
the current sampling rate. Overriding a monitoring level lasts until the next
monitoring level begins, as determined by the schedule.
Selected Group/Server displays the server the changes are applied to.
1. Select the Schedule Selection from the drop-down menu.
2. Select the Override Monitoring Level from the drop-down menu.
v System Default
v L1 Production Mode
v L2 Problem Determination Mode
v L3 Tracing Mode
3. Select the Enable Method Profiling check box and type the number of minutes
that you want to use.
4. Select the Sampling Rate for the monitoring level you select.
5. Override Transaction CPUMON Level (CICS only) Select the level from the
drop-down menu.
The monitoring level for a server defines the amount of data collected for it. The
higher the monitoring level, the more details are collected and the larger
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
73
performance overhead is introduced by the Data Collector. The available
Monitoring Levels are L1 (Production mode), L2 (Problem Determination mode),
and L3 (Tracing mode).
You can create schedules that defines preset times at which the monitoring level is
to be changed, then apply different schedules to different servers. You can also set
(override) the monitoring level manually for any server at any time.
To view the monitoring level for all servers, adjust it manually and assign
schedules for its adjustment, select MOD Console in the left navigation pane. See
“MOD Console.”
To view the schedules and modify them, select Schedule Management in the left
navigation pane. See “Schedule Management” on page 75.
To create a new blank schedule, select Create Schedule in the left navigation pane.
See “Creating a schedule” on page 75.
To create a schedule as a copy of an existing schedule, select Duplicate Schedule
in the left navigation pane. See “Duplicating a schedule” on page 78.
Tip: To change the default monitoring level, used when no schedule or override is
applied, see “Configuring the Data Collection settings” on page 79.
Related topics
“Configuring the Data Collection settings” on page 79
User Scenarios
Scenario 1: Setting a schedule for detailed monitoring at night
Your manager wants you to monitor your servers at Level 3 during off hours
because that's when the load is the lightest. As the ITCAM for Application
Diagnostics administrator, you set a schedule to monitor the servers during
business hours at Level 1 and at night at Level 3.
Scenario 2: Overriding the monitoring level during an emergency
An emergency arises that requires Level 3 monitoring to locate a problem. As the
ITCAM for Application Diagnostics administrator, you override the current
schedule and set the monitoring level to Level 3. After fixing the problem, you can
reset the monitoring level or wait until the next schedule change.
MOD Console
The MOD Console page shows a table of all servers and the monitoring level set
for them. You can manually set (override) this level and assign a schedule for
automatically changing it as preset times.
If you want to only see servers in a particular server group, use the All Groups
pull down control at the top of the table to select the group.
For every server, the table shows:
v Group and Server name.
v Platform (operating system) the server uses.
v The name of the Schedule currently applied to it. If a Schedule is applied, it
determines automatic adjustment of server monitoring level at preset times.
74
ITCAM for Application Diagnostics: User Guide
v
v
v
v
Current monitoring level.
Current sampling rate.
Current CPU load.
Schedule Change/Override button.
To set (override) the monitoring level for a server or to assign a schedule for
automatically changing it as preset times, click the Schedule Change/Override
button. See “Overriding a monitoring level” on page 77 and “Applying a
schedule” on page 76.
To view or modify a schedule, click the schedule name. See “Modifying a
schedule” on page 77.
You can use the left navigation pane to view the existing schedules and create a
new schedule. See “Monitoring on Demand (TM)” on page 73.
Schedule Management
The Schedule Management page shows a table of all schedules. A schedule defines
preset times at which the monitoring level for a server should be changed. You can
modify and delete the schedules, and set the monitoring level or change the
schedule for servers.
For every schedule, the table shows the schedule name, the server name, and a
Delete button.
To modify a schedule, click the schedule name. See “Modifying a schedule” on
page 77.
To set (override) the monitoring level or change the schedule for a server, click the
server name. See “Overriding a monitoring level” on page 77 and “Applying a
schedule” on page 76.
To delete a schedule, click the Delete button. See “Deleting a schedule” on page
78.
You can use the left navigation pane to view the monitoring levels for all servers
and create a new schedule. See “Monitoring on Demand (TM)” on page 73.
Creating a schedule
About this task
At times a server might need more detailed monitoring, you can create a schedule
that changes the monitoring level based on a specified date and time. Using the
schedule, modulate the monitoring level at different times based on the anticipated
load on the server.
To create a schedule:
1. From the top navigation, click Administration > Monitoring on Demand TM.
The Monitoring on Demand TM (MOD) Console page opens.
2. Click Create Schedule on the left navigation pane. The Schedule Detail page
opens where you can create a new schedule.
3. Enter a Schedule Name for the new schedule.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
75
4. Select the Day of the Month or the Day of the Week when you want your
schedule to take effect; for example, you might want the schedule to start on
the 5th of every month or on every Monday.
5. Select the Hour and Minute when the schedule starts.
6. Select the Monitoring Level that best suits your needs: L1, L2, or L3.
7. Click Add to insert the settings into the schedule. Each schedule can include
multiple monitoring level changes; to save each change, click Add.
8. To save the schedule, click Save. The Schedule Management page opens with
the new schedule displayed. In the event of a schedule conflict, the most
recently entered item will take precedence.
Do not create an overly complicated schedule or else you will never know at
what level of monitoring your servers are running. Keep the rules simple. L1
has the smallest overhead, while L3 is heavier. When L2 applies, it has
optimum overhead and allows you to switch to L3 without the need to restart.
You might want minimum one or maximum 5% of your servers running at L3,
either as dedicated servers, or only during non-peak hours. This arrangement
will give you good quality data for workload tracing and application sizing. In
the case of the z/OS environment, you might want to create a server instance
that runs at L3.
Related topics
Applying a schedule
Overriding a monitoring level
“Overriding a monitoring level” on page 77
Applying a schedule
About this task
After creating a schedule, you can apply it to a server that needs monitoring. You
may also apply other existing schedules to a server.
To apply a schedule:
1. From the top navigation, click Administration > Monitoring on Demand. The
Monitoring on Demand (MOD) Console page opens.
2. Click Schedule Change/Override for the server where you want to apply a
schedule. The Modify Server Settings page opens.
3. Click to select a schedule from the schedule selection list box for the server.
4. Enter a percentage in the boxes for sampling setting or choose the default
setting by checking the system default box.
5. Click OK. The MOD Console page displays the server with the schedule
applied in the table.
Note: A schedule can be applied at the group level and the all servers level as
well.
Related topics
Creating a schedule
Deleting a schedule
Modifying a schedule
76
ITCAM for Application Diagnostics: User Guide
Overriding a monitoring level
About this task
In case you need to collect more or less detailed data in a particular period of time,
you can override the current monitoring level until the next scheduled monitoring
level occurs.
To override a monitoring level:
1. From the top navigation, click Administration > Monitoring on Demand. The
Monitoring on Demand (MOD) Console page opens.
2. Click Schedule Change/Override for the server or group that you want to
override its current monitoring level. The Modify Server settings page opens.
3. Click to select a monitoring level from the override monitoring level drop
down box. If you select L2, you will be given the option to check MP for
Method Profiling. The time interval setting in Enable Method Profiling is for
how often the Data Collector should aggregate method data and push the data
to the Managing Server. For example, if the interval setting is 60 minutes, then
it means, every 60 minutes, the Data Collector aggregates the method data and
push the data to the Managing Server. To disable the Method Profiling feature,
clear "Enable Method Profiling". You can view the method profile reports on
the Method Profiling Management page. If you override the system default
monitoring level, the request sampling setting will also be changed according
to the default monitoring level that the server is running on.
4. Click OK. Due to overhead when collecting transaction CPU in CICS,
Application Diagnostics 7.1 offers the option to specify the level for collecting
CICS CPU. Called the Transaction CPUMON Level, this option is available on
the Monitoring on Demand Override page (accessed via Administration >
Monitoring on Demand, click Schedule Change/Override) and on the System
Properties page (accessed via Administration > Managing Server > System
Properties). In both cases, the options include:
v Do Not Collect
v Collect at Monitoring Level L1, L2, and L3
v Collect at Monitoring Level L2 and L3
v Collect at Monitoring Level L3 only
With these alternatives, you can plan to collect transaction CPU when the load
on your system is not overwhelming. Collect at Monitoring Level L3 only is the
default.
Modifying a schedule
About this task
If you find that an existing schedule is not providing the correct level of
monitoring, modify the schedule to reflect your needs. Keep your schedules
current based on the ever fluctuating needs of your data center.
To modify a schedule:
1. From the top navigation, click Administration > Monitoring on Demand. The
Monitoring on Demand (MOD) Console page opens.
2. Click the schedule name for the schedule you want to modify on the console
page or the Schedule Management page. The View MOD Schedule page opens.
3. Click Modify Schedule. The Schedule Detail page opens.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
77
4. Enter the information to modify the schedule setting.
5. Click Add to insert the settings into the schedule. Each schedule can include
multiple monitoring level changes; to save each change, click Add.
6. To save the schedule, click Save.
Note: Changes take effect immediately.
Related topics
Applying a schedule
Configuring the Data Collection settings
Deleting a schedule
About this task
Keep your schedules updated by deleting schedules from the system that are no
longer in use.
To delete a schedule:
1. From the top navigation, click Administration > Monitoring on Demand TM.
The Monitoring on Demand TM (MOD) Console page opens.
2. Click Schedule Management on the left navigation pane. The Schedule
Management page opens.
3. Click X or Delete next to the schedule you want to remove.
4. At the confirmation box, click OK to delete the schedule. The Schedule
Management page displays without the deleted schedule.
If a schedule is currently being used by a server, you have to apply another
schedule to that server or it will automatically apply the system default after
you delete the schedule.
Duplicating a schedule
About this task
Save time by duplicating schedules. Duplicating a schedule allows you to quickly
create a new schedule based on the settings of an existing schedule.
To duplicate a schedule:
1. From the top navigation, click Administration > Monitoring on Demand TM.
The Monitoring on Demand TM (MOD) Console page opens.
2. Click Duplicate Schedule on the left navigation pane. The Duplicate Schedule
page opens.
3. From the Schedule list box, select the schedule you want to duplicate.
4. Enter a new name for the duplicated schedule.
5. Click Save. The Schedule Management page opens displaying the duplicated
schedule.
Related topics
Applying a schedule
Modifying a schedule
Managing server
Tune and debug the managing server.
78
ITCAM for Application Diagnostics: User Guide
The managing server section is separated into two categories: system properties
and self-diagnosis. System properties enable you to tune ITCAM, while
self-diagnosis provides you with a method for debugging the managing server
when problems arise.
System properties
In the System Properties pages, you can set defaults for server data collection,
baseline settings for the Enterprise Overview display in the Visualization Engine,
and SNMP settings.
To view the System Properties pages, from the top navigation, click
Administration > Monitoring Server > System Properties.
To set default values for server data collection, select Data Collection Settings in
the left navigation pane. See “Configuring the Data Collection settings.”
To set the values for baseline indication in the Enterprise Overview display, select
Enterprise Overview Display in the left navigation pane. See “Configuring the
Enterprise Overview display” on page 80.
To configure the SNMP network, select SNMP in the left navigation pane. See
“Configuring the SNMP network” on page 81.
Configuring the Data Collection settings
About this task
Use the Data Collection settings to set and modify the system settings for the
managing server to regulate the frequency of data collection, the percentage of data
stored and the level of monitoring. The default data collection settings can be
established at the managing server level, then overridden by configuration settings
specific to each configured data collector.
To configure the Data Collection settings:
1. From the top navigation, click Administration > Managing Server > System
Properties. The System Properties page opens.
2. Enter the appropriate value for the following properties:
v System Resources Polling Frequency - Set how often the system resources
requests information from your application server. The default setting is 60
seconds.
v Request Sampling Rate - The percentage of requests stored in the database
for reporting and analysis. The default request sampling rate is 2%.
v Default Monitoring Level - The currently set default monitoring level for all
servers connected to the application monitor. This is the case when
configuring a server for the first time and bringing up the server under the
management of the application monitor. The default monitoring level for the
non z/OS platform is L2 (Problem Determination). As for the z/OS platform,
the default monitoring level is L1 (Production Mode). The monitoring levels
are as follows:
– L1 (Production mode) – this monitoring level provides availability
management, system resources and basic request-level data. This
monitoring level least affects the CPU overhead per transaction and is
appropriate for servers that are not malfunctioning.
– L2 (Problem determination mode) – this monitoring level provides
production level monitoring plus advanced request data, including
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
79
external component and CPU information, as well as additional
monitoring fields and functions. Under problem determination mode you
can view component traces. These are traces that show J2EE
request-related events that are made to external services. Use this level
when you suspect a problem or need to capture data about external events
but do not need all the method-level data. When you select L2, you will
be given the option to check MP for Method Profiling. This feature allows
you to determine how often the data collector will aggregate method data
and send the data to the managing server: 1-999 minutes. You can view
the method profile reports on the Method Profiling Management page.
– L3 (Tracing Mode) – this is the most powerful monitoring level, therefore
only this level utilizes all reporting elements available. For example, in L3
the server activity display shows additional data for the following
columns: Accumulated CPU, Last Known Class Name, Last Known
Method, and Last Known action. In addition, on the Request Detail page,
the method trace with SQL statements are also available. L3 has inherently
higher overhead than the other monitoring levels. Use this level for
servers that have been selected for diagnostics and detailed workload
characterization.
v Transaction CPU Time (CICS only) - This field indicates whether the CPU
times for a CICS transaction will be collected or not. The CPU times for CICS
tasks are reported, but if you want to avoid overhead from the data capture,
adjust these settings as necessary. Select one of the following four options for
collecting transaction CPU:
– Do Not Collect
– Collect at Monitoring Level L1, L2, and L3
– Collect at Monitoring Level L2 and L3
– Collect at Monitoring Level L3 only
v Maximum Method Records - The maximum number of method trace
records. The records will be cycled through, showing the 10,000 (or
Maximum Method Records value) most recent methods in the system. The
default value is 10,000.
v Maximum IMS™ Message Data Length - The maximum length of the IMS
message data. The default is 256.
3. Click Save.
Related topics
Configuring the Enterprise Overview display
Configuring the SNMP network
Configuring the Enterprise Overview display
About this task
Use the Enterprise Overview Display settings to set the response time Baseline
Indicators and Baseline Definitions. The Baseline Indicator is the percentage above
the baseline that you determine to indicate slow or very slow response. The
Baseline Definition determines how the baseline is calculated. These thresholds
apply to the average of average response times for all servers in the group.
To configure the Enterprise Overview display:
1. From the top navigation, click Administration > Managing Server > System
Properties. The System Properties page opens.
2. On the left navigation pane, click Enterprise Overview Display. The Enterprise
Overview Display page opens.
80
ITCAM for Application Diagnostics: User Guide
3. Enter the appropriate value for the following properties:
v Baseline Indicator Settings - The percentage above the baseline that
indicates slow or very slow response time. Slow response means the present
response time is between 26% and 50% of the baseline; very slow response
means the present response time exceeds 50% of the baseline. All averages
are over 5 minute intervals. For example: if Indicator 1 is set to 25%, and
Indicator 2 is set to 50%, average response times between 125% and 150% of
the baseline are considered slow response. Average response times above
150% of the baseline are considered very slow response.
v Baseline Definition Settings - The method to be used for determining the
response time baseline.
– Rolling Date - Historical response time data for this number of days is
averaged to determine the baseline.
– Fixed Date - Baseline is the average response time over the time interval
midnight on the start date to 11:59PM on the end date.
– Fixed Response Time - The response time entered in this field will
become the response time against which your current response times on
the enterprise overview page will be compared.
4. Click Save. These properties are actually defined at the group level for the
servers once they are added to a group. The group properties take precedence
over the system properties. When the response time reaches Indicator 1, an
orange indicator will display on the Enterprise Overview page; a red indicator
means the response time has exceeded Indicator 2.
Related topics
Configuring the Data Collection settings
Configuring the SNMP network
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
Configuring the SNMP network
About this task
Use the SNMP network settings to indicate the configuration for the SNMP server.
A test message will be sent to the SNMP network manager to test for an open
connection.
Note: Consult the Installation and Customization Guide for further instructions on
the setup required to configure the SNMP network.
To configure the SNMP network:
1. From the top navigation, click Administration > Managing Server > System
Properties. The System Properties page opens.
2. On the left navigation pane, click SNMP. The SNMP Network Configuration
page opens.
3. Click the Add SNMP Configuration button. Enter the appropriate value for the
following properties:
v Device Host Name or IP Address - The name or address of your SNMP
Network Manager, to which SNMP messages will be sent.
v Port Number - The port number of your SNMP Network Managers.
v Community - A string that is part of the SNMP protocol.
4. Click Test and Save to send a test message to the SNMP Network Manager.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
81
5. Click Save to save your settings.
Related topics
Configuring the Data Collection settings
Configuring the Enterprise Overview display
Self-diagnosis
In the Self-diagnosis pages, you can view details of ITCAM operation. This
information can be useful for debugging.
To view the Self-diagnosis page, from the top navigation, click Administration >
Managing Server > Self-Diagnosis.
These pages are designed for the Support staff to service ITCAM. The
self-diagnosis provides a view of all the components currently running, their states
and attributes. Since ITCAM is designed to run in a loosely-coupled, dynamic
environment, individual components can be up or down without affecting the
integrity of the whole system.
Use the left navigation pane to select the Managing Server components for which
debugging information will be shown.
Viewing the Self-diagnosis for the kernel
About this task
The Self-diagnosis provides a view of all the components on the kernel currently
running and their attributes. Since the application monitor is a dynamic
environment, the components can be up or down without affecting the integrity of
the whole system.
To view the Self-diagnosis for the kernel:
1. From the top navigation, click Administration > Managing Server >
Self-diagnosis. The Self-diagnosis page opens displaying the kernel's data.
2. In the left navigation pane, click the + Kernel Instances.
3. Click to select the kernel link you want to view. The kernel runtime
environment detail displays.
Related topics
Viewing the Self-diagnosis for the archive agent
Viewing the Self-diagnosis for the publish server
Viewing the Self-diagnosis for the global publish server
Viewing the Self-diagnosis for the data collector controller
Viewing the Self-diagnosis for the message dispatcher
Viewing the Self-diagnosis for the archive agent
About this task
The archive agent aggregates the data from the publish server and archives it into
the database for reporting. The Self-diagnosis provides a view of all the
components on the archive agent currently running and their attributes.
To view the Self-diagnosis for the archive agent:
1. From the top navigation, click Administration > Managing Server >
Self-diagnosis. The Self-diagnosis page opens.
82
ITCAM for Application Diagnostics: User Guide
2. In the left navigation pane, click + Archive Agents.
3. Click to select the archive agent you want to view. The data for the selected
archive agent displays.
Related topics
Viewing the Self-diagnosis for the kernel
Viewing the Self-diagnosis for the publish server
Viewing the Self-diagnosis for the global publish server
Viewing the Self-diagnosis for the data collector controller
Viewing the Self-diagnosis for the message dispatcher
Viewing the Self-diagnosis for the publish server
About this task
The publish server retrieves data from the data collector and aggregates it based
on different needs. The Self-diagnosis provides a view of all the components on the
publish server currently running and their attributes.
To view the Self-diagnosis for the publish server:
1. From the top navigation, click Administration > Managing Server >
Self-diagnosis. The Self-diagnosis page opens.
2. In the left navigation pane, click + Publish Servers.
3. Click to select the publish server you want to view. The data for the selected
publish server displays.
Related topics
Viewing the Self-diagnosis
Viewing the Self-diagnosis
Viewing the Self-diagnosis
Viewing the Self-diagnosis
Viewing the Self-diagnosis
for
for
for
for
for
the
the
the
the
the
kernel
archive agent
global publish server
data collector controller
message dispatcher
Viewing the Self-diagnosis for the global publish server
About this task
The global publish server keeps track of composite requests, as they move from
one server to another. The Self-diagnosis provides a view of the global publish
server's attributes, as well as all the components with which the global publish
server has relationships.
To view the Self-diagnosis for the global publish server:
1. From the top navigation, click Administration > Managing Server >
Self-diagnosis. The Self-diagnosis page opens.
2. In the left navigation pane, click + Global Publish Servers.
3. Click to select the global publish server you want to view. The data for the
selected global publish server displays.
Related topics
Viewing the Self-diagnosis for the kernel
Viewing the Self-diagnosis for the archive agent
Viewing the Self-diagnosis for the publish server
Viewing the Self-diagnosis for the data collector controller
Viewing the Self-diagnosis for the message dispatcher
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
83
Viewing the Self-diagnosis for the data collector controller
About this task
The data collector controller regulates the behavior of a data collector, including
the monitoring level, filter list, and enable or disable status. The Self-diagnosis
provides a view of all the components on the data collector controller currently
running and their attributes.
To view the Self-diagnosis for the data collector controller:
1. From the top navigation, click Administration > Managing Server >
Self-diagnosis. The Self-diagnosis page opens.
2. In the left navigation pane, click the Data Collector Controllers' link.
3. Click to select the data collectors you want to view. The data for the selected
data collector controller displays.
Related topics
Viewing the Self-diagnosis for the kernel
Viewing the Self-diagnosis for the archive agent
Viewing the Self-diagnosis for the publish server
Viewing the Self-diagnosis for the global publish server
Viewing the Self-Diagnosis for the message dispatcher
Viewing the Self-diagnosis for the message dispatcher
About this task
The message dispatcher sends out e-mails of performance reports and trap results
from the Performance Analysis and Reporting and the Trap and Alert Management
applications. The Self-diagnosis shows all the attributes of the message dispatcher
currently running such as total number of e-mails sent.
To view the Self-diagnosis for the message dispatcher:
1. From the top navigation, click Administration > Managing Server >
Self-diagnosis. The Self-diagnosis page opens.
2. In the left navigation pane, click + Message Dispatchers.
3. Click to select the message dispatcher link you want to view. The message
dispatcher runtime environment detail displays.
Related topics
Viewing the Self-diagnosis for the kernel
Viewing the Self-diagnosis for the archive agent
Viewing the Self-diagnosis for the publish server
Viewing the Self-diagnosis for the global publish server
Viewing the Self-diagnosis for the data collector controller
Systems overview
Assess your entire system.
Systems overview allows you to evaluate the availability of your entire system by
looking at recent performance trends.
User Scenarios
Scenario 1: Investigating an unresponsive system
84
ITCAM for Application Diagnostics: User Guide
Your first line of support receives calls that some parts of the system are not
responding. The support team goes to the Server Statistics Overview page and
immediately sees that one server displays the red icon representing the
“unavailable” status. The support team determines the unavailable server needs to
be restarted, which will return the system to full functionality.
Scenario 2: Monitoring proactively
As the administrator of production systems, you have set appropriate thresholds
for the fields displayed on the Server Statistics Overview page. During your
regular monitoring you see that the Paging Rate threshold is being crossed. You
know that the increase in paging rate probably means an increase in overhead. You
can now increase memory, add servers, or take some similar course of action to
keep production running smoothly.
User Scenarios
Scenario 1: Verifying customer response time complaints
Customer service has been receiving complaints that your company's Web sites
have been responding slowly. As one of the administrators of the servers, the
inquiry has come to your attention. Upon opening the Enterprise Overview page,
you immediately see that three of your production servers are no longer available.
You also verify that the response time has degraded.
Scenario 2: Diagnosing an application problem
Customers have been complaining that they cannot place orders. As one of your
company's administrators, you go to the Enterprise Overview page and see that all
the servers are up. You find the group that appears to have the highest response
time and drill down to the Server Overview page where you see that a database
connection pool is saturated.
Enterprise Overview
The Enterprise Overview page shows a table of summary availability information
for each server group.
To view the Enterprise Overview page, from the top navigation, click Availability
> Systems Overview > Enterprise.
For every server group ("ALL" is a group consisting of all servers communicating
to the Managing Server) the table shows:
v A "traffic-light" indicator. Green means good availability, orange means
problematic availability, and red means an alert. The indicator is set based on
comparing the current response time with a baseline time determined from the
average for a certain time.
v Number of available servers, total number of servers in the group, and the
percentage of servers that are available.
v A Maintenance Mode column displays if a server group has one or more
WebSphere Dynamic Cluster members. It shows the number of clusters in
maintenance mode compared to the total number of servers in the group.
v A graph showing throughput (requests per 5 minutes) for the last hour.
v A graph showing the average response times, in milliseconds, over every 5
minutes for the last hour.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
85
v A tool button.
To see availability information for individual servers in a group, click the name of
the group. The “Group Overview” page will open.
To see the activity for a group, click the tool button and select Server Activity
Display. See “Server Activity Display” on page 114.
To find a specific request for this group, click the tool button to select In-flight
Request Search. The “In-flight request search” on page 112 page will open.
To set the Enterprise Overview as the default page when you open the
Visualization Engine, click Set as My Default page at the top right of the page.
To switch to the “Group Overview,” “Server Overview,” “Alerts and Events” on
page 106, “Problem Center” on page 107, and “Portal Overview” on page 88 use
the tabs at the top of the page.
Group Overview
The Group Overview page shows a table of availability information for each server
in a server group.
To view the Group Overview page, from the top navigation, click Availability >
Systems Overview > Group.
To change the group, select the new group in the Servers In pull down control.
("ALL" is a group consisting of all servers communicating to the Managing Server).
For every server in the group the table shows:
v A "traffic-light" indicator. Green means good availability, orange means
problematic availability, and red means an alert. The indicator is set based on
comparing the current response time with a baseline time determined from the
average for a certain time.
v Server name
v Status of the server
v Total volume of requests processed by this server in the last hour
v A graph showing throughput (requests per 5 minutes) for the last hour.
v A graph showing the average response times, in milliseconds, over every 5
minutes for the last hour.
To see detailed information for a server, click the server name. The “Server
Overview” page will open.
To set the Group Overview as the default page when you open the Visualization
Engine, click Set as My Default page at the top right of the page.
To switch to the “Enterprise Overview” on page 85, “Server Overview,” “Alerts
and Events” on page 106, “Problem Center” on page 107, and “Portal Overview”
on page 88 use the tabs at the top of the page.
Server Overview
The Server Overview page displays information and activity graphs for a server.
86
ITCAM for Application Diagnostics: User Guide
To view the Server Overview page, from the top navigation, click Availability >
Systems Overview > Server.
To select a server for displaying information, select the group and server names
from the pull down controls at the top of the page.
The following information is displayed for the server under Server Information:
v Server name.
v Group name.
v
v
v
v
v
Platform (operating system).
IP Address.
Start time.
Current monitoring level for this server.
Number of problems detected on this server.
The following information is displayed for the server under Server Statistics:
v A graph showing JVM CPU utilization for the last hour.
v
v
v
v
v
A graph showing JVM memory utilization for the last hour.
The throughput (total volume of requests) for the last hour.
The uptime of the server, that is, the time since it was last rebooted.
The names of the applications currently running on the server.
Platform (operating system).
v IP Address.
v Start time.
v Current monitoring level for this server.
v Number of problems detected on this server.
The following information is displayed for the server under Activity (Last Hour):
v A graph showing average response time, in milliseconds, for every minute in the
last hour.
v A graph showing the throughput, or number of requests, for every minute in the
last hour.
v A graph showing the number of open sessions, or logged on users, for every
minute in the last hour.
To switch to the “Runtime Environment Check” on page 155, “Runtime
Environment Comparison” on page 154, and “Server Statistics Overview” on page
92 for this server, mouse over the tool button at Server Information and select the
needed link.
To switch to following items for this server, mouse over the tool button at Activity
and select the needed link
v “Server Statistics Overview” on page 92
v
v
v
v
“Server Activity Display” on page 114
“Memory Analysis” on page 131
“Heap Analysis” on page 131
“Memory Leak” on page 132
v “System resources” on page 96
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
87
To view WLM Associated Service Classes for a z/OS server, mouse over the tool
button at Server Information and select Workload Management. The “WLM
associated service class summary” on page 90 page opens.
To switch to the “Enterprise Overview” on page 85,“Group Overview” on page 86,
“Alerts and Events” on page 106, “Problem Center” on page 107, and “Portal
Overview” use the tabs at the top of the page.
Portal Overview
The Portal Overview page shows availability information specific for IBM
WebSphere Portal Server. You can access detailed portal statistics from this page.
To view the Portal Overview page, from the top navigation, click Availability >
Systems Overview > Portal.
To select a server for displaying information, select the group and server names
from the pull down controls at the top of the page. Only servers running IBM
WebSphere Portal Server are listed.
The page shows graphs of average response time, in milliseconds, for every minute
in the last hour for the following portal components:
v
v
v
v
v
v
Portal Pages and Gateway servlets
Portlets
Model Building
Page Loading
Authentication
Authorization
To view detailed statistics (response time and access count) for portal pages, click
the Portal Pages/Gateway Servlet link. You will see statistics for the pages that
were slowest and most popular in the last hour; to view statistics for all pages,
click View All Portal Pages at the bottom of the table. See “Viewing the Portal
Page Summary.”
To view detailed statistics (response time and access count) for portlets, click the
Portlets link. You will see statistics for the portlets that were slowest and most
popular in the last hour; to view statistics for all pages, click View All Portlets at
the bottom of the table. See “Viewing the Portlet Summary” on page 89.
To switch to the “Enterprise Overview” on page 85, “Group Overview” on page
86, “Server Overview” on page 86, “Alerts and Events” on page 106, and “Problem
Center” on page 107 use the tabs at the top of the page.
Viewing the Portal Page Summary
About this task
The Portal Page Summary offers a view of the portals in your system and how
they are operating. You can monitor the status of your portals from the slowest
portals to the most popular portals for the last hour. In addition, view the metrics
for the portals including Average Response Time and Count for authentication and
authorization, and credential and content access metrics as well.
To open the Portal Page Summary for the slowest and most popular portals:
88
ITCAM for Application Diagnostics: User Guide
1. From the top navigation, click Availability > Systems Overview > Portal.
2. Select a group and a server from the list boxes. The Portal Overview page
displays the portal trends for the last hour.
3. Click the Portal Pages link. The portal page summary data for the slowest and
the most popular portals displays.
Results
To open the Portal Page Summary for all portals from the last hour:
1. From the top navigation, click Availability > Systems Overview > Portal.
2. Select a group and a server from the list boxes. The Portal Overview page
displays the portal trends for the last hour.
3. Click the Portal Pages link. The portal page summary data for the slowest and
the most popular portals displays.
4. The portal page summary data for all the portals from the last hour displays.
5. Click the View all Portal Pages link.
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
“Portal Overview” on page 88
The Portal Overview page shows availability information specific for IBM
WebSphere Portal Server. You can access detailed portal statistics from this
page.
Viewing the Portlet Summary
About this task
The Portlet Summary offers a view of the portlets in your system and how they
are operating. You can monitor the status of your portlets from the slowest portlets
to the most popular portlets for the last hour. In addition, view the metrics for the
portlets including Average Response Time and Count for authentication and
authorization, and credential and content access metrics as well.
To open the Portlet Summary page for the slowest and most popular portlets:
1. From the top navigation, click Availability > Systems Overview > Portal.
2. Select a group and a server from the list boxes. The Portal Overview page
displays the response times for the portals.
3. Click the Portlets link. The Portlet Summary page displays the slowest and the
most popular portlets.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
89
Results
To open the Portlet Summary page for all the portlets for the last hour:
1. From the top navigation, click Availability > Systems Overview > Portal.
2. Select a group and a server from the list boxes. The Portal Overview page
displays the portal trends for the last hour.
3. Click the Portlets link. The Portlet Summary page displays the slowest and the
most popular portlets.
4. Click the View All Portlets link. The Portlet Summary page displays all the
portlets for the last hour.
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
“Portal Overview” on page 88
The Portal Overview page shows availability information specific for IBM
WebSphere Portal Server. You can access detailed portal statistics from this
page.
WLM associated service class summary
About this task
The WLM Associated Service Class Summary page offers a way to view selected
data from the Workload Manager (WLM) for z/OS and OS/390®, for the address
space associated with a particular server, as well as its associated service class data
and service class period data.
This feature is only available for z/OS servers.
To open the WLM Associated Service Class Summary:
1. From the top navigation, click Availability > Systems Overview > Server. The
Server Overview selection page opens.
2. Select a group and a server from the list boxes. The Server Overview page
opens displaying data for the selected server.
3. Click Workload Management from the tools button at Server Information. The
WLM Associated Service Class Summary page opens.
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
90
ITCAM for Application Diagnostics: User Guide
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
WLM associated service class period detail
About this task
The WLM Associated Service Class Period Detail page offers a way to view
selected data from the Workload Manager (WLM) for z/OS and OS/390, for a
selected service class period. This includes the response time distribution detail
and delay detail information about each subsystem work manager.
To open the WLM Associated Service Class Period Details page:
1. From the top navigation, click Availability > Systems Overview > Server. The
Server Overview selection page opens.
2. Select a group and a server from the list boxes. The Server Overview page
opens displaying data for the selected server.
3. Click Workload Management from the tools button. The WLM Associated
Service Class Summary page opens.
4. Click the name of one of the associated service class periods. The WLM
Associated Service Class Period Detail page opens.
Results
To view the details for one of the associated service class periods, click its name.
The “WLM associated service class period detail” page opens.
To view the WLM Enclave, click the Enclave tab. The WLM Enclave page opens.
See “Viewing a WLM enclave.”
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
Viewing a WLM enclave
About this task
The WLM Enclave page offers a way to view selected data from the Workload
Manager (WLM) for z/OS and OS/390, for an enclave.
For z/OS 1.2, all tokens in the Enclave are shown. There is no filtering on the basis
of server instance; for z/OS 1.3 and above, only the tokens in the Enclave initiated
by the server instance are shown.
To open the WLM Enclave page:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
91
1. From the top navigation, click Availability > Systems Overview > Server. The
Server Overview selection page opens.
2. Select a group and a server from the list boxes. The Server Overview page
opens displaying data for the selected server.
3. Click Workload Management from the tools button. The WLM Associated
Service Class Summary page opens.
4. Click the Enclave tab. The WLM Enclave page opens.
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
Server Statistics Overview
The Server Statistics Overview page shows a configurable set of application server
level statistics. You can show the statistics for several servers on one page, and
access other pages to view additional details for any server.
To view the Server Statistics Overview page, from the top navigation, click
Availability > Server Statistics Overview.
To view statistics for an application server, select the server group and server name
from the Server Selection pull down controls, and click the Add Server(s) button.
You can add more than one server; every server will be represented by a line in
the table. You can also select All Servers in the server name control to view
information for all servers in a server group.
To remove a server from the page, click the X icon next to the server name.
Note: For servers running the z/OS platform, when you remove a server instance
from the Server Statistics Overview page, the system removes all the server regions
belonging to that server instance from the display since the system treats them as a
group of clones.
To remove all servers from the page, click Clear All at the bottom of the list.
For every server, the table shows the configured statistics.
The statistics are refreshed periodically. To pause refreshing, click the Pause button.
To resume refreshing (if it was paused) and force an immediate refresh, click the
Refresh button.
To configure the statistics in the table, click Customize.... See “Configuring the
Server Statistics Overview page” on page 93.
92
ITCAM for Application Diagnostics: User Guide
Configuring the Server Statistics Overview page
About this task
Configure the Server Statistics Overview page by selecting the resources to display
on the detail page. In addition, set the warning threshold for certain resources by
selecting the desired function from the list box.
To configure the Server Statistics Overview page:
1. From the top navigation, click Availability > Server Statistics Overview. The
Server Statistics Overview page opens.
2. Click Customize. The Server Statistics Configuration window opens.
3. Click Select All or click the individual check boxes to select the resource you
want to display.
4. If you want to show a warning (color the table cell yellow) when a statistic is
above or below a certain threshold, select an operator from the list box, and
enter the threshold limit in the field next to it.
5. Click Save. For each data element on the Server Statistics Configuration page,
set the range between 0-99999.
Results
You can select the following statistics:
v Volume Delta.
v Total Volume.
v Group name: the name of the group to which the server belongs
v Uptime: the time since the server was last rebooted
v Start Time: the time when server monitoring was started; this is usually the time
the server was started
v
v
v
v
v
v
v
v
v
Paging Rate
Total CPU%: the current CPU load on the server
Platform: the operating system that the server runs
Live Sessions: the number of sessions currently open on the server
Platform CPU Delta: the amount of CPU time spent since the last sample
Application Server Platform
Volume Delta per Second (If this value is >.5, it is rounded up to 1.)
JVM/Region CPU Delta
JVM/Region CPU%
v IP Address
v Average Response Time (1 min).
v Data Collector Uptime: the time since the Data Collector was started or
restarted.
v JVM/Region (DSA,EDSA) Memory Usage.
v Delta Normal CP time: for z/OS servers, the amount of normal central processor
time spent since last sample.
v Delta zAAP time: for z/OS servers, the amount of zAAP (additional CPU used
exclusively for Java applications including WebSphere; requires z/OS 1.6 or
above) time spent since last sample.
v Delta zAAP-eligible time on CP: for z/OS servers, the amount of normal central
processor time since last sample that was spent on tasks eligible for a zAAP; this
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
93
happens when a zAAP is not present or busy. High values of this statistic can
mean that an additional zAAP would be beneficial.
v Delta zAAP-eligible time: for z/OS servers, the amount of processor time
(regardless of processor type) since last sample that was spent on tasks eligible
for a zAAP. This is a sum of Delta zAAP time and Delta zAAP-eligible time on
CP.
Related topics
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
Viewing the Server Statistics Overview
About this task
The Server Statistics Overview page provides application server-level statistics for
quick assessment of server activity and related platform data. For thread data or
system data on a server, or system data across a server group, click the tools
button to view the information on the Server Activity Display page, the System
Resources page, or the System Resources Comparison page respectively.
To open the Server Statistics Overview page:
1. From the top navigation, click Availability > Server Statistics Overview or by
selecting from the Tools button on the Server Overview page.
2. The Server Statistics Overview page opens. The zAAP (zSeries® Application
Assist processor) is a new hardware feature for zSeries. It is an additional CPU
used exclusively for Java applications like WebSphere. zAAP requires z/OS 1.6
or above. ITCAM for WAS provides the following utilization statistics for the
zAAP processors:
v Delta zAAP time is the amount of CPU time spent on zAAP since the last
sample.
v Delta Normal CP time is the regular CP time for the address space.
v Delta zAAP-eligible time on CP is the amount of time that could have been
executed on zAAP but wasn't because it was already busy. High eligible time
could mean that an additional zAAP processor could be needed.
v Delta zAAP-eligible time is the total amount of time that could have been
executed on zAAP, i.e., delta zAAP + delta zAAP on CP.
Results
To remove a server from the Server Statistics Overview display:
1. Click the X icon next to the server. The server disappears from the display.
2. If you want to clear all the servers from the display, click Clear All at the
bottom of the list. The page refreshes clear of any servers or information.
For the z/OS platform, when you remove a server instance from the detail
page, the system removes all the server regions belonging to that server
instance from the display since the system treats them as a group of clones.
94
ITCAM for Application Diagnostics: User Guide
Related topics
Configuring the Server Statistics Overview
Enterprise Overview
The Enterprise Overview page shows a table of summary availability
information for each server group.
Recent Activity Display
In the Recent Activity Display page, you can create a report that can help you to
discover problems related to memory or other resources.
To create the report, see “Creating a Recent Activity report.”
User Scenarios
Scenario 1: Evaluating the impact of garbage collection
You suspect that frequent garbage collection calls are affecting the performance of
a server, so you go into Recent Activity and set up the first graph to display the
Number of Garbage Collections metric for the last 48 hours. In the second graph,
you roll through the different metrics possibly affected by frequent garbage
collection.
The Garbage Collection option is not supported for either CICS or IMS.
Creating a Recent Activity report
About this task
Use Recent Activity when you need to investigate potential memory problems
relating to garbage collection and the JVM heap size. At times garbage collection
might not cleanup properly or the heap may have too little memory allocated.
To create a Recent Activity report:
1. From the top navigation, click Availability > Recent Activity Display. The
Recent Activity Display page opens.
2. Select a group and a server from the list boxes.
3. For Metric 1 and Metric 2, select the two metrics you want to compare from the
list boxes. The available metrics are as follows:
v # of Requests
v Avg. Response Time
v Live Sessions
v System Paging Rate
v JVM CPU
v JVM Heap Size
v # of GCs
v Total GC Time
v Avg. Heap Size after GC
Note: The Garbage Collection options are not supported for either CICS or
IMS.
When the date range is Last 48 Hours, the Avg. Response Time value equals
the result of the summary of AVG_RES_TIME in this hour divided by the
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
95
summary counts of AVG_RES_TIME in this hour. If no AVG_RES_TIME occurs
within the hour then the result is 0. When the date range is Last 60 Minutes,
the Avg. Response Time value equals the result of the summary of
AVG_RES_TIME in this minutes divided by the summary count of
AVG_RES_TIME in this minute. If no AVG_RES_TIME occurs within the
minute then the result is 0.
4. For Time, select the time when you want the system to extract the data.
5. Click the OK button. A new report displays based on your selection. You can
click on the bars in the graph for further details.
6. Using the Recent Activity Options, you can select a different group or server,
compare two different metrics, or view a different time increment.
Results
Either heap size or garbage collection can cause a slow down in your server's
performance. Find out if your heap size is too small for the number of users using
the system or too small for the current workload on the system. At times, garbage
collection can cause high JVM CPU usage, slow transaction response time, or a
delay that impacts throughput. Analyze the memory in your system using the
Recent Activity Display and then make the necessary adjustments.
Related topics
Creating a Memory Analysis report
Creating a Memory Leak Candidate Finder report
Setting up a Heap Analysis
System resources
The System Resources pages provide views of system, resource metrics available
for an application server. You can use this information to tune the application
server.
Select the group and server names to view the System Resources Browser. See
“Viewing the System Resources Browser.”
This feature is not available for CICS or IMS.
User Scenarios
Scenario 1: Eliminating bottlenecks
The response time of application A becomes unacceptable once the server is
experiencing modest throughput. You see that much of the resident time is spent
idle. To see if the cause is a bottleneck in the application server pools, use System
Resources during these times to view the percentage of threads used in the
Database Connection Pools, Thread Pools, and JCA Connection Pools. If any pool
is at or near 100%, it is likely that demand for application A is saturating those
resources. You might be able to fix the problem by creating more or larger pools.
Viewing the System Resources Browser
About this task
The System Resources Browser displays summary information for all the resources
on the selected application server. You can view data, such as EJBs, Database/JCA
96
ITCAM for Application Diagnostics: User Guide
Connection Pools, Servlet/Session Manager, Thread Pools, JTA Transactions, Web
Applications, SQL Data, JCA-CICS, ORB, and JVM/System.
To open the System Resources Browser:
1. From the top navigation, click Availability > System Resources. The System
Resources Overview page opens. The right side of the page is the System
Resources Overview page while the left side is the navigation for the System
on
Resources Browser. You can also access this page from the toolbox icon
the Server Activity Display page.
2. Select a group and a server from the list box on the left navigation panel. The
System Resources Browser opens displaying the information for the selected
group and server. If you access this page from the Tivoli Enterprise Portal and
from the Server Activity Display page, the server group name and server name
display automatically.
3. Mouse over the question mark icon next to each of the following items; EJB
Activity, Servlet JSP Activity EJB Coverage and Servlet JSP Coverage, for
additional information.
Results
Use the Resource Categories left navigation pane to select the category of resources
that you need to view. For the available resource categories, see “Resources
Performance Metrics.”
To change the application server:
1. On the left navigation pane, select a group from the list box.
2. On the left navigation pane, select a server from the list box.
Note: In the Current Snapshot view, if more that 50 objects are retrieved, then
sorting is disabled. You can view 5, 10 or 15 rows per page.
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
Resources Performance Metrics
About this task
You can drill down into different pages of the resources to view detailed
information. The following information provides the metrics for various metric
categories and the application servers that support them.
WebSphere 5.x
v Servlet
v EJB Module
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
97
v
v
v
v
v
Entity Bean
Stateful Session Bean
Message Driven Bean
J2EE Server
J2EE Application
v
v
v
v
v
v
v
Web Module
JDBC Provider
Data Source
RAR Module
Resource Adapter
Thread Pool
Orb
v
v
v
v
v
v
JVM
Dynamic Cache
JMS Provider
JMS Server
Listener Port
Mail Provider
v Session Manager
v J2C Connection Factory
v Transaction Service
v
v
v
v
Trace Service
URL Provider
Web Services Service
System Metrics
v WLM Module
v WSGW Module
v Object Pool Module
v SQL
v CTG
v MQI
WebSphere 5.x\Lotus Mail Services
v Bean Module
v
v
v
v
v
v
v
v
Cache Module
Connection Pool Module
JVM Runtime Module
Orb Module
Servlet Session Module
System Module
Thread Pool Module
Transaction Module
v Web Application Module
v Mail Service Module
v IMAP Service Module
98
ITCAM for Application Diagnostics: User Guide
v
v
v
v
v
Queue Manager Module
POP Service Module
SQL
CTG
MQI
WebSphere 6
v Servlet
v JVM
v J2EE Domain
v J2EE Server
v J2EE Application
v EJB Module
v
v
v
v
v
Web Module
RAR Module
Entity Bean
Stateful Session Bean
Stateless Session Bean
v Message Driven Bean
v Resource Adapter
v JDBC Resource
v
v
v
v
JDBC Data Source
JDBC Driver
JCA Resource
JCA Connection Factory
v
v
v
v
JCA Managed Connection Factory
JNDI Resource
JMS Resource
JTA Resource
v RMIIIOP Resource
v Thread Pool
v Orb
v Dynamic Cache
v Servlet Session Manager
v
v
v
v
v
v
v
v
Transaction Service
HA Manager Module
System Module
J2C Module
Web Services Module
WLM Module
WSGW Module
Object Pool Module
v Alarm Manager Module
v Schedulers Module
v DCS Statistics Module
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
99
v
v
v
v
SQL
CTG
MQI
SIB (System Integration Bus)
– Message Store
– Mediation Framework
– Message Processor
– Communications
WebSphere ESB (Enterprise Service Bus) 6.x
v Servlet
v JVM
v J2EE Domain
v
v
v
v
v
J2EE Server
J2EE Application
EJB Module
Web Module
RAR Module
v Entity Bean
v Stateful Session Bean
v Stateless Session Bean
v
v
v
v
Message Driven Bean
Resource Adapter
JDBC Resource
JDBC Data Source
v
v
v
v
JDBC Driver
JCA Resource
JCA Connection Factory
JCA Managed Connection Factory
v JNDI Resource
v JMS Resource
v JTA Resource
v RMIIIOP Resource
v Thread Pool
v
v
v
v
v
v
v
v
Orb
Dynamic Cache
Servlet Session Manager
Transaction Service
HA Manager Module
System Module
J2C Module
Web Services Module
v WLM Module
v WSGW Module
v Object Pool Module
100
ITCAM for Application Diagnostics: User Guide
v
v
v
v
v
Alarm Manager Module
Schedulers Module
DCS Statistics Module
SIB Service
SQL
v CTG
v MQI
v SIB (System Integration Bus)
– MessageStore
– Mediation Framework
– Message Processor
– Communications
WebSphere Process Server 6.x
v Servlet
v JVM
v J2EE Domain
v J2EE Server
v J2EE Application
v EJB Module
v Web Module
v
v
v
v
RAR Module
Entity Bean
Stateful Session Bean
StatelessSession Bean
v
v
v
v
Message Driven Bean
Resource Adapter
JDBC Resource
JDBC Data Source
v JDBC Driver
v JCA Resource
v JCA Connection Factory
v JCA Managed Connection Factory
v JNDI Resource
v
v
v
v
v
v
v
v
JMS Resource
JTA Resource
RMIIIOP Resource
Threadpool
Orb
Dynamic Cache
Servlet Session Manager
Transaction Service
v HA Manager Module
v System Module
v J2C Module
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
101
v
v
v
v
v
Web Services Module
WLM Module
WSGW Module
Objectpool Module
Alarm Manager Module
v
v
v
v
v
v
v
Schedulers Module
DCS Statistics Module
SIB Service
SQL
CTG
MQI
SIB (System Integration Bus)
–
–
–
–
MessageStore
Mediation Framework
Message Processor
Communications
J2EE
WebLogic 8
v Web module
v
v
v
v
Servlet
Entity EJB
Stateless EJB
Stateful EJB
v Message Driven EJB
v Message Driven EJB Destination
v JDBC Connection Pool Resource
v
v
v
v
v
JCA Connection Pool
JMS Session
JTA Resources
JVM System
JVM System Server
v Execute Queue
v Execute Queue Runtime
WebLogic 9.1
v Web module
v Servlet
v Entity EJB
v Stateless EJB
v
v
v
v
v
102
Stateful EJB
Message Driven EJB
Message Driven EJB Destination
JDBC Connection Pool Resource
JCA Connection Pool
ITCAM for Application Diagnostics: User Guide
v
v
v
v
v
JMS Session
JTA Resources
JVM System Server
Execute Queue
Thread Pool
JBOSS 3 and 4
v Web module
v Servlet
v EJB Module
v Entity EJB
v Stateless EJB
v Stateful EJB
v
v
v
v
v
Message Driven EJB
JDBC Connection Pool
JCA Connection Pool
JMS Session
JTA Resources
v JVM/System
Tomcat 5.0 and 5.5
v
v
v
v
Web module
Servlet
Cache
Thread Pool
v Session Manager
Oracle Application Server 9.x
v Operating System
Oracle Application Server 10.x
v Web module
v Servlet
v EJB Module
v Entity EJB
v
v
v
v
v
Stateful Session Bean
Stateless Session Bean
Message Driven Bean
JDBC Data Source
JVM
Netweaver 6
v Component Performance
v Request Performance
v Performance Summary
v Thread Pool
v Web Container
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
103
v
v
v
v
v
Entity EJB
Stateless EJB
Stateful EJB
Message EJB
Transaction
v
v
v
v
v
v
Memory
JVM
System
Web Service Performance
Web Service Request
HTTP
WebSphere Community Edition
v
v
v
v
v
Web Module
Servlet
EJB Module
Entity Bean
JCA Connection
v JVM
J2SE - IBM and Sun
v
v
v
v
OS
Memory
JVM
Threading
General
The following performance metrics are supported on any application server which
supports the underlying call interface. The following categories are available:
v CICS transactions
v Queue manager
v SQL
Related topics
Configuring the Enterprise Overview
“Enterprise Overview” on page 85
The Enterprise Overview page shows a table of summary availability
information for each server group.
“Group Overview” on page 86
The Group Overview page shows a table of availability information for each
server in a server group.
“Server Overview” on page 86
The Server Overview page displays information and activity graphs for a
server.
SMF data
The SMF data pages show the information collected by the System Management
Facilities (SMF) on z/OS servers.
104
ITCAM for Application Diagnostics: User Guide
In these pages, you can view detailed information on Server, EJBs, Servlet Session
Manager, Web Applications, and Server Regions. The source of the data comes
primarily from the SMF records published periodically by WebSphere. As these
records are published, the Application Monitor intercepts the transfer of the
records and makes a copy in real time before writing it to the SMF dataset.
To view SMF data, select the group name and server name. (SMF data is only
provided for z/OS servers). See “Viewing SMF data.”
User Scenarios
Scenario 1: Pinpointing problems
Application A's response time slows to unusable when the server experiences even
moderate throughput, while resident time is idle. Using SMF data, view the
percentage of threads used in the Database Connection Pools, Thread Pools, and
JCA Connection Pools; this will tell you if there is a bottleneck in the application
server pools. Any pool that is at or near 100% is most likely being overwhelmed
by application A's requests for those resources. To fix the problem, you can create
more or larger pools.
Viewing SMF data
About this task
The following information provides the metrics for the SMF data type and the
application servers it supports.
WebSphere 5 and 6
v Overview
v
v
v
v
v
v
Server
EJBs
Servlet Session Manager
Web Applications
SQL
JCA-CICS
z/WebSphere only
The following information provides the metrics for the z/WAS only data type and
the application servers it supports.
WebSphere 5
Server Regions
To view the SMF data page:
1. From the top navigation, click Availability > SMF Data. The SMF Data page
opens.
2. Select a group and a server from the list box on the left navigation panel. The
SMF Data page opens displaying the information for the selected group and
server. If you have come to this page directly from the Tivoli Enterprise Portal,
the group name and server name display automatically.
Related topics
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
105
Viewing the Server Statistics Overview
Alerts and Events
In the Alerts and Events page, you can view the alerts and events generated by
Managing Server traps and by the Tivoli Enterprise Portal, and escalate these
events into the Problem Center for diagnosis and tracking.
To display ITCAM situations in Alerts and Events, complete the following setup:
1. Go to the Managing Server Visualization Engine host.
2. Open the file $MS_HOME/etc/dal/dal.properties set the correct values for the
following properties:
dal.itmsoap.hostName=
dal.itmsoap.port=1920
dal.itmsoap.useHttps=false
For UNIX and Linux platforms, $MS_HOME is by default /opt/IBM/itcam/
WebSphere/MS.
For Windows platforms, $MS_HOME is by default C:\Program
Files\IBM\itcam\WebSphere\MS.
3. Restart the Managing Server Visualization Engine server instance.
To view the Alerts and Events page, from the top navigation, click Problem
Determination > Alerts and Events.
The page shows a table of all high-priority trap alerts and Tivoli Enterprise Portal
events for the last 24 hours for a selected server.
To change the server, select the group and server names from the pull down
controls, and click the OK button.
To show only alerts or only events, select Alerts or Events from the Status control,
and click the OK button.
To filter the displayed alerts and events by date and time, click Show Advanced
Filters, check the Date Range box, then select the date and time range in the From
and To controls and click the OK button.
For every alert or event, the table shows:
v
v
v
v
v
Date and Time of the alert or event.
Server group name.
Server name.
Name of alert or event.
Origin of the event (trap or Tivoli Enterprise Portal).
v Escalate button.
To escalate an alert or event, adding it to the Problem Center, click the Escalate
button. See “Escalating alerts and events to the Problem Center” on page 107.
106
ITCAM for Application Diagnostics: User Guide
Escalating alerts and events to the Problem Center
About this task
When you need to diagnose an alert in order to resolve it, you can escalate it as a
problem in the Problem Center. This will allow you to keep track of the data
related to the alert and provide further information that might help you resolve the
issue. If you escalate an alert to a problem, your actions will be recorded in the
audit trail.
To open the Alerts and Events page:
1. From the top navigation, click Problem Determination > Alerts and Events.
The Alerts and Events page opens.
2. Select a group and a server from the list box. This will limit the alerts to the
server and group you specify.
3. If you want to escalate an alert to a problem for tracking, click Escalate.
4. Type in a description of the problem in the text box. (A description is not
required.)
5. Select the Category from the list box. The available categories are as follows:
v Unknown–The category could not be determined by the system.
v Application Performance–Under capacity, hanging or waiting incomplete
transaction, CPU hogging, poor load balancing, slow completed transaction,
slow JDBC call, slow, LDAP look-up, slow JMS call, and slow method call.
v Application Outage–exception, incorrect output, intermittent outage, binaries
discrepancies within a group/cluster, and properties discrepancies across a
group/cluster.
v Resource Consumption–JCBC connection leak, JMS connection leak, heap
usage, heap/object lead, excessive JVM CPU%, high garbage collection
frequency, high garbage collection time, and fragmentation.
6. Click OK to save as a problem. The problem displays in the Problem Center.
7. Click the Problem Center tab to view your problem.
Results
Using the advanced filters:
1. Click the Show Advanced Filters link.
2. Click the check box to set the advanced filters.
3. Select the dates and times you want to use to limit your list of problems.
4. Click OK. The list displays based on the filtering you selected.
Related topics
“Problem Center”
The Problem Center page shows problems that were previously escalated from
actions or events or added manually. You can investigate problems, close them,
and add new problems.
Problem Center
The Problem Center page shows problems that were previously escalated from
actions or events or added manually. You can investigate problems, close them,
and add new problems.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
107
To view the Problem Center, from the top navigation, click Problem Determination
> Problem Center.
Escalated problems are normally high-priority trap alerts and Tivoli Enterprise
Portal events, escalated from the “Alerts and Events” on page 106 page. The details
of each problem, including a snapshot of the problem details and the state of the
application server at the time the problem occurred, are available for review.
A problem has a status value:
v New: the status assigned by the system to newly created problems.
v Open: the status assigned by the system after a user opens a problem.
v Closed: the status assigned by the user when he closes a problem. Closed
problems are deleted from the system after 30 days.
Initially, all problems are shown in the Problem Center table.
To show only the problems for a particular server, select the group and server
names from the Filter controls, and click the OK button.
To show only the problems with a particular status, select the status from the
status control, and click the OK button.
To show only problems that occurred in a limited date/time range, click Show
Advanced Filters, check the Date Range box, then select the date and time range
in the From and To controls and click the OK button.
For every problem, the table shows:
v
v
v
v
Date and Time the problem occurred.
Server group name.
Server name.
Problem category, set when the problem was escalated. See “Escalating alerts
and events to the Problem Center” on page 107.
v Origin of the problem (trap, Tivoli Enterprise Portal, or manual creation).
v Name of the problem.
v Description of the problem, entered when the problem was escalated. See
“Escalating alerts and events to the Problem Center” on page 107.
v Closing comment, entered when the problem is closed. The field is empty for
new or open problems.
v Problem status (New, Open, or Closed).
v Delete button.
To view the details of a problem, click its date/time. See “Viewing the details of a
problem” on page 109.
To close a problem, select Closed in the Problem status control in the table row.
See “Closing a problem” on page 111.
To delete a problem, click the Delete button.
To add a problem manually, click the Add Problem Manually button at the bottom
of the table. See “Adding a problem manually” on page 111.
108
ITCAM for Application Diagnostics: User Guide
Viewing the details of a problem
About this task
The Problem Center displays a list of all the high-priority trap alerts and Tivoli
Enterprise Portal events that were escalated to problems as well as problems
entered manually. You can view further details on each problem by selecting the
Date/Time link for the problem. This will enable you to access the tabs that
furnish further diagnostic information.
To view the details of a problem:
1. From the top navigation, click Problem Determination > Problem Center. The
Problem Center opens.
2. Select the Date/Time link for the problem. The details for the problem open to
the Problem tab. Several tabs provide further problem details including
memory, transactions, resources, traps, logs, and configuration. The information
provided by each tab is useful in diagnosing the problem. The function of each
tab is described in the following section:
v Problem - displays an analysis based on the user-defined category of the
problem assigned when the problem was escalated from Alerts and Events.
Each category contains a set of contributing factors. The system will analyze
whether there was a positive result or not and suggest a solution based on
the data. You can change the status of a problem, edit the problem's
description, and change the problem's category.
v Memory - displays information related to the event or alert, identification for
the server, status of the server, filter to display previous hours of data (1, 2,
6, 12, 24, or 48 hours), actions to perform (Heap dump and Thread dump), a
snapshot of the current memory usage information, a graph for the Average
Heap Usage after Garbage Collection (GC), and trends for the Heap Size,
Number of Requests, Number of Sessions, Response time, Number of GCs,
CPU usage, GC time, and Paging rate.
v Transactions - displays information related to the event or alert,
identification for the server, status of the server, filter to display previous
hours of data (1, 2, 6, 12, 24, or 48 hours), action to perform (Thread dump),
a snapshot of the current transaction usage information, trends for the
Response time, JVM CPU Usage, Number of Sessions, Number of Requests,
and Heap Usage, ranks the slowest transactions in a list, and provides a
Transaction Snapshot of all the transactions.
v Resources - displays information related to the event or alert, identification
for the server, and opens the JMX browser page. In the Current Snapshot
table, the list displays based on the filtering you select. If more that 50
objects are retrieved, then sorting is disabled. You can view 5, 10 or 15 rows
per page.
Complete the following setup steps to see data in the TEMA data snapshot
section.
a. Go to the Managing Server Visualization Engine host.
b. Open the file $MS_HOME/etc/dal/dal.properties set the correct values for
the following properties:
dal.itmsoap.hostName=
dal.itmsoap.port=1920
dal.itmsoap.useHttps=false
For UNIX and Linux platforms, $MS_HOME is by default
/opt/IBM/itcam/WebSphere/MS.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
109
For Windows platforms, $MS_HOME is by default C:\Program
Files\IBM\itcam\WebSphere\MS.
c. Restart the Managing Server Visualization Engine server instance.
Monitoring Console - the Monitoring Console button launches the Tivoli
Enterprise Portal browser client from the Managing Server Visualization
Engine. Complete the following steps to enable this feature:
a. Go to the Managing Server Visualization Engine host.
b. Open the file $MS_HOME/etc/ve.properties set the correct values for the
following properties:
tep.hostname=
tep.port=1920
tep.baseurl=///cnp/kdh/lib/cnp.html
tep.userid=
For UNIX and Linux platforms, $MS_HOME is by default
/opt/IBM/itcam/WebSphere/MS.
For Windows platforms, $MS_HOME is by default C:\Program
Files\IBM\itcam\WebSphere\MS.
c. Restart the Managing Server Visualization Engine server instance.
v Traps - displays information related to the event or alert, identification for
the server, action to perform (New Trap), and Trap Action History, which
provides the date the trap occurred, name of the trap, server name, severity,
and the action taken. From the Action Taken, you can access the results of
the action. For example, if a method trace was taken, you can click this link
to go to the properties page for this method trace. In addition, you can delete
the history of a trap you no longer need.
v Logs - displays information related to the event or alert, identification for the
server, filter to display by entry type (All, Warning, or Error), and a scrape of
the log files.
Viewing log data. Data under the Logs tab comes from the ITCAM TEMA
agents. Complete the following setup steps to view this data:
a. Go to the Managing Server Visualization Engine host.
b. Open the file $MS_HOME/etc/dal/dal.properties set the correct values for
the following properties:
dal.itmsoap.hostName=
dal.itmsoap.port=1920
dal.itmsoap.useHttps=false
tep.userid=
For UNIX and Linux platforms, $MS_HOME is by default
/opt/IBM/itcam/WebSphere/MS.
For Windows platforms, $MS_HOME is by default C:\Program
Files\IBM\itcam\WebSphere\MS.
c. Restart the Managing Server Visualization Engine server instance.
v Configuration - displays information related to the event or alert,
identification for the server, and a filter to display previous hours of data (1,
2, 6, 12, 24, or 48 hours).
3. You can add a description, change the problem's status, or change the category
for a problem by clicking the Edit button in the Event box. See the
Contributing Factors section for more information about the problem.
Related topics
110
ITCAM for Application Diagnostics: User Guide
Adding a problem manually
Closing a problem
Adding a problem manually
About this task
You might need to add a problem to the Problem Center manually, for example, if
your monitoring software does not interface with ITCAM or if you discover a
problem that does not have a trap associated with it. You can do this in the
Problem Center using the Add Problem Manually button. As a result, you will be
able to access the problem details after creating the problem.
To add a problem manually:
1. From the top navigation, click Problem Determination > Problem Center. The
Problem Center opens.
2. At the bottom of the page, click the Add Problem Manually button.
3. Select the group and server where the problem exists from the list boxes.
4. Select the date from the list box and enter a time in the text box.
5. Enter a name and description for the problem in the text box.
6. Select the Category from the list box. The available categories are as follows:
v Unknown–The category could not be determined by the system.
v Application Performance–Under capacity, hanging or waiting incomplete
transaction, CPU hogging, poor load balancing, slow completed transaction,
slow JDBC call, slow, LDAP look-up, slow JMS call, and slow method call.
v Application Outage–Exception, incorrect output, intermittent outage, binaries
discrepancies within a group/cluster, and properties discrepancies across a
group/cluster.
v Resource Consumption–JCBC connection leak, JMS connection leak, heap
usage, heap/object lead, excessive JVM CPU%, high garbage collection
frequency, high garbage collection time, and fragmentation.
7. Click OK to save as a problem. The problem displays in the list in the Problem
Center with the status as new.
8. Additional details on the problem are available when you select the Date/Time
link for the problem. See “Viewing the details of a problem” on page 109 for
more information.
Related topics
“Problem Center” on page 107
The Problem Center page shows problems that were previously escalated from
actions or events or added manually. You can investigate problems, close them,
and add new problems.
Viewing the details of a problem
Closing a problem
Closing a problem
About this task
Close a problem in the Problem Center when the issue is resolved. After you close
a problem, you are given the option to delete it from the Problem Center. If you
elect not to delete a problem, your closed problem will be deleted from the system
after 30 days.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
111
To close a problem:
1. From the top navigation, click Problem Determination > Problem Center. The
Problem Center opens.
2. View all Open problems by selecting Open from the Status list box and click
OK. Find the problem you want to close.
3. To change the status of an open problem to closed, select Closed from the list
box in the Status column. A Closing Comment text box opens.
4. Add your final notes to the problem in the Enter Closing Comment text box
and click OK. Your notes will display in the Closing Comment column and the
problem's status will change to Closed.
Related topics
Adding a problem manually
Viewing the details of a problem
In-flight request search
In the In-flight request search page, you can search for requests that are currently
open on an application server. As a request normally closes relatively quickly, this
search is useful for locating hanging transactions, which result from an application
malfunction.
To search for a request in a server group, select the group name in the Group
control.
To search for a request in an individual server, select the group name in the Group
control and the server name in the Server control.
If you have come to this page directly from the Tivoli Enterprise Portal, the group
name and server name display automatically.
To search for a request that has a substring in the URL string (for Web requests) or
class name (for EJB requests), enter the substring in the Search
Request/Transaction control.
Click the OK button to perform the search and view the results. See “Searching for
an Application Request” on page 113.
User Scenarios
Scenario 1: Investigating a hanging transaction
Customers call and complain they are having trouble completing transactions. You
go to In-flight Request Search to locate a hanging transaction and, upon finding
one, view a method trace for the transaction. You can see that the transaction is
waiting for the return of a specific SQL call. You forward the method trace to a
database administrator for further analysis.
Scenario 2: Isolating a problem with CPU utilization
After looking at the Server Statistics Overview page, you notice that CPU
utilization is very high. You go to the In-flight Request Search to see if a
transaction is present. It appears the system is churning on a transaction. Through
a method trace, you suspect the transaction is looping. You forward the method
trace to a developer for further analysis.
112
ITCAM for Application Diagnostics: User Guide
Searching for an Application Request
About this task
The In-flight Request Search page lets you search for open, troubled requests in
your server farm.
From the search results you can follow any request's Thread/Task ID link to view
the Request Detail for that request. Click on any column heading to sort the search
results by that column. Click the column heading again to reverse the sort. In
addition, click the Tools button to view the Server Activity Display page or the
System Resources page for that server.
The In-flight Request Search is not case sensitive.
To search for a request:
1. From the top navigation, click Problem Determination > In-Flight Request
Search. The In-flight Request Search page opens.
2. Select a group or server from the list box.
Note: If you do not select a group or server, requests from all servers will
display.
3. Enter a string in the Search Request box.
Note: The system will search all active URL strings (for Web requests) and
active class names (for remote EJB requests) for the string entered in step 2. If
any request contains the string, (Web requests or remote EJB requests), the
results page will display those requests. In addition, if you leave the search
request box empty, all active requests will display.
4. Click OK. All the active requests associated with your search display in the
order of descending Total Resident Time. To change the order, see “Sorting
search results.”
Related topics
Activating a thread
Cancelling a request
Changing a thread's priority
E-mailing a PDF file - SAD
Exporting to a file - SAD
Searching a Method Trace
Suspending a thread
Viewing a Method/Component Trace - Flow View
Viewing a PDF file - SAD
Viewing a Stack Trace
Viewing Request detail
Viewing the request object and session object
Sorting search results
About this task
You can sort your search results in alphabetical order according to the Server
Names, by Client Request / Transaction, or in numeric order with Start Date /
Time, Total Resident Time and User ID.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
113
To sort the search results:
1. Click a column heading to sort the results. You can only sort by columns with
underlined headings.
2. When the page refreshes, the results display sorted by the selected heading.
3. Click the column heading a second time to sort the results in reverse order.
Related topics
Searching for an Application Request
Viewing a Composite Method Trace - In-flight Request Search
Viewing a Composite Request Detail - In-flight Request Search
Viewing a Composite Stack Trace - In-flight Request Search
Server Activity Display
The Server Activity Display page shows a table of request activity on an
application server. This page can help you troubleshoot and fix hanging requests
and evaluate the current performance of your applications.
You can access the Server Display using one of the following options:
v From the top navigation, click Problem Determination > Server Activity
Display to display the Server Activity Display page.
v If you have logged in from the Tivoli Enterprise Portal the information about the
sever group name and server name files is already complete.
For more information see “Access the Managing Server Visualization Engine from
Tivoli Enterprise Portal” on page 39.
To set the server for which the activity is displayed, select the server group name
and server name.
To show requests currently being processed by the server, click the Active
Requests tab. See “Server Activity Display - active requests” on page 115.
To show requests recently processed by the server, click the Recent Requests tab.
See “Server Activity Display - recent requests” on page 117.
To show requests that are hanging because they are waiting on a lock, click the
Lock Contentions tab. See “Server Activity Display - lock contentions” on page
118.
User Scenarios
Scenario 1: Troubleshooting an application that hangs.
Several users of application Z have reported that they can't update their user
preferences: Application Z times out after a minute of not responding. You look for
the application Z requests that have long resident times in the Active Requests tab
of the Server Activity Display. View the Request Detail for one of these requests to
determine why or where it is hanging.
Scenario 2: Understanding immediate workload.
While performing normal monitoring of your servers, you notice that a server's
average response time has recently increased, with no appreciable change in
throughput. You begin by looking at the Recent Requests tab of the Server Activity
114
ITCAM for Application Diagnostics: User Guide
Display to see what the most recently completed requests have been on that server.
You can see whether the requests are uniformly slow, or if there is variation among
requests; this can help you isolate whether it is a problem with the server
(uniformly slow), or with an application (certain requests are slow). You can see
whether the slow requests are CPU-heavy, or if they are spending too many
moments idle.
Server Activity Display - active requests
About this task
The Active Requests tab displays thread data for an application server at a specific
point in time.
Data in this section is constantly fluctuating. Active requests display a snapshot of
the data at a specific point in time. As a result, requests can be completed and
disappear from the display on refresh, or by the time you drill down.
To open the Server Activity Display (active requests) page:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list box. If you have come to this page
directly from the Tivoli Enterprise Portal, the group name and server name
display automatically.
Results
The Active Requests tab has three main sections
v Server Information
v Recent Activity (Last Minute)
v Active Requests (In JVM Memory Now)
Server Information provides details relating to the server. It also has a toolbox icon
. You can click this toolbox icon to access direct links to the following features.
The feature you select displays information specific to the group sever and server
name you select.
v JVM Display
v
v
v
v
System Resources
Monitoring On Demand
Data Collector Profiles
Trap and Alert Management
Recent Activity (Last Minute) displays the following features. You can click a link
to create a Recent Activity Report for the item you want to select.
v JVM CPU
v JVM Heap Size (MB)
v # of Requests
v # of live Sessions
v Average Response Time (MS)
Active Requests (In JVM Memory Now) you can use this section of the page to
view information about thread types and to view request details.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
115
To filter the active requests data:
1. You can filter active request by selecting the options available on the Thread
Type and Thread Status drop-down menus.
2. Click Thread Type, select one of the following options from the drop-down
menu:
v Any
v EJB
v Servlet
v JSP
v CICS
3. Click Thread Status, select one of the following options from the drop-down
menu:
v Any
v Active
v Suspended
v Waiting
4. Click Refresh. The active requests data displays based on the selected filter.
To sort the active requests data:
1. Click a heading link:
v Client Requests
v Client Requests Start
v
v
v
v
Thread ID
Resident Time (ms)
Accumulated CPU (ms)
Idle Time (ms)
v Thread Status
v Last Known Class
v Last Known Method
v Last Known Action
v User ID
The data refreshes sorted by the selected heading.
2. Click the heading link a second time to invert the sorting.
To view request detail, click the link in the Client Requests column. From the
request detail view, you can investigate further details, suspend and reactivate the
request thread, and change its priority.
Related topics
Activating a thread
Canceling a request
Server Activity Display - recent requests
Viewing the request detail
116
ITCAM for Application Diagnostics: User Guide
Server Activity Display - recent requests
About this task
The Recent Requests page displays list of the recently completed requests for the
user to review the recent activity data on a per-server basis. The default maximum
number of recent activity data is 100. The maximum number of recent activity data
applies to each server. When the queue is full, the newest request data replaces the
oldest data.
To open the Server Activity Display (recent requests) page:
If you have logged in from the Tivoli Enterprise Portal page, all the relevant
information including the sever group name and server name display
automatically.
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. If you have come to this page
directly from the Tivoli Enterprise Portal, the group name and server name
display automatically. The Server Activity Display (active requests) page opens.
The information for the selected server group displays.
3. Click Recent Requests. The Recent Requests tab opens displaying the 100 most
recently completed requests.
Results
The Recent Requests tab has three main sections
v Server Information
v Recent Activity (Last Minute)
v Recent Requests (Last 100 Completed Requests)
Server Information provides details relating to the server. It also has a toolbox icon
. You can click this toolbox icon to access direct links to the following features.
The feature you select displays information specific to the group sever and server
name you select.
v JVM Display
v System Resources
v Monitoring On Demand
v Data Collector Profiles
v Trap and Alert Management
Recent Activity (Last Minute) displays the following features. You can click a link
to create a Recent Activity Report for the selected item.
v JVM CPU
v JVM Heap Size (MB)
v # of Requests
v # of live Sessions
v Average Response Time (MS)
Recent Requests (Last 100 Completed Requests) displays completed requests you
can filter this information by Thread Type. To filter the recent request data:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
117
You can filter recent requests by selecting the options available on the Thread
Type drop-down menu and then clicking Refresh to display the results.
2. Click Thread Type, select one of the following options from the drop-down
menu:
v Any
v EJB
v Servlet
v JSP
v CICS
3. Click Refresh. The active requests data displays based on the selected filter.
1.
To sort the recent request data:
1. Click a heading link:
v Client Requests
v Client Requests Start
v Response Time (ms)
v Accumulated CPU (ms)
v Idle Time (ms)
v Thread Type
v User ID
2. The data refreshes sorted by the selected heading.
To view request detail, click the link in the Client Requests column.
Related topics
Activating a thread
Server Activity Display - active requests
Viewing the request detail
Server Activity Display - lock contentions
About this task
Use the Lock Contentions tab when a request is taking too long to process and you
want to know why. The Lock Contentions tab displays any requests that are
hanging because they are waiting on a lock. The data shows both the object that
has the lock and the one that is waiting for a lock.
To open the Server Activity Display (lock contentions) page:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list box. The Server Activity Display
(active requests) page opens. The information for the selected server group
displays. If you have come to this page directly from the Tivoli Enterprise
Portal, the group name and server name display automatically.
3. Click Lock Contentions. The Lock Contentions tab opens displaying the active
locks. If no locks have occurred, the system message says, "There are no classes
instrumented for lock analysis."
118
ITCAM for Application Diagnostics: User Guide
Results
If there are any Active Locks (For active requests) the information displays under
the following column headings:
v Locked Object Class
v Owners Request/Transaction Name
v Owners Request/Transaction Type
v Owner Class
v Owner Method
v
v
v
v
v
Waiting Time (ms)
Waiting Class
Waiting Method
Waiting Request/Transaction Name
Waiting Workload Type
Related topics
Activating a thread
Canceling a request
Server Activity Display - active requests
Server Activity Display - recent requests
Viewing the request detail
Viewing request detail
About this task
The Request Detail page provides data for one request only. Typically you arrive
on this page by clicking a Client Request's link on the Server Activity Display (in
the Active Requests tab) page.
Through the left navigation of the Request Detail page, you can obtain a Stack
Trace or Method/Component Trace, or view the Request/Session Object. If
necessary, you can cancel a request, and change the thread's priority or status.
To open the Request Detail page:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(active requests) page opens. The information for the selected server group
displays unfiltered.
3. Click the link in the Client Requests' column.
4. The Request Detail page for that request opens. This page displays data for that
request only.
Results
If the request is not yet completed, you can perform the following additional
actions on it:
v To suspend the request thread, select Suspend from the Change Thread Status
control. See “Suspending a thread” on page 120.
v To re-activate a suspended thread, select Active from the Change Thread Status
control. See “Activating a thread” on page 120.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
119
v To cancel the request, click the Cancel Request button. See “Canceling a
request” on page 121.
v To change the priority of the request thread, select a priority from the Change
Priority control. See “Changing a thread's priority” on page 121.
v To view a Stack Trace, showing which methods were called to reach the current
state of the request thread, click Stack Trace on the left navigation pane. See
“Viewing a Stack Trace” on page 122.
v To view a request object and session object, click Request/Session Object on the
left navigation pane. See “Viewing a request object and session object” on page
123.
v To view a Method/Component Trace, click Method/Component Trace on the left
navigation pane. From this view, you can search the trace and export it to a file.
See “Viewing a Method/Component Trace - flow view” on page 122.
Related topics
Canceling a request
Changing a thread's priority
Suspending a thread
About this task
An executing thread is active, and a paused thread is suspended. Suspend a thread
if there is a problem with it and you want to uncover the cause.
To suspend a thread:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click the link in the Client Request column. The Request Detail page for that
request opens.
4. From the Change Thread Status list box, select Suspend.
5. Click OK.
Results
When suspending a thread, there is a danger that the request might hold database
locks or system resources. After you suspend the request, any other requests that
require the removal of those locks or monitors will also be suspended. Any locks
in the application server and database server will not be released after the system
suspends a thread. This can cause other applications to fail or hang.
Related topics
Activating a thread
Canceling a request
Changing a thread's priority
Activating a thread
About this task
A thread is executing if it is active, and the thread is paused when it is suspended.
Select Active status to re-activate a suspended thread.
120
ITCAM for Application Diagnostics: User Guide
To activate a thread:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click the link in the Client Request column. The Request Detail page for that
request opens.
4. From the Change Thread Status list box, select Active.
5. Click OK.
Related topics
Canceling a request
Changing a thread priority
Suspending a thread
Canceling a request
About this task
If an application request from the system is looping or abusing resources, it might
be necessary to cancel the request. This will terminate the request by throwing a
run-time exception.
To cancel a request:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click on the link in the Client Requests' column of the request that is hanging.
A Request Detail page opens, where you can click the Cancel Request button.
4. Click Cancel Request. A confirmation box displays.
5. At the confirmation box, click OK. Canceling a thread can cause JVM and
application server instability. Use the Cancel Thread function only when
absolutely necessary, and with careful consideration of the consequences.
Related topics
Activating a thread
Changing a thread's priority
Suspending a thread
Changing a thread's priority
About this task
If a thread is executing too slowly, you can increase the thread's priority. This will
move the thread up in the stack so it will execute more quickly. (Alternatively, you
can decrease a thread's priority to allow other threads to execute more quickly.)
To change a thread's priority:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
121
3. Click the link in the Client Request column. The Request Detail page for that
request opens.
4. From the Change Priority list box, select a priority. Priority 1 is the lowest and
priority 10 is the highest.
5. Click Save.
Related topics
Activating a thread
Canceling a request
Suspending a thread
Viewing a request detail
Viewing a Stack Trace
Viewing a Stack Trace
About this task
The Stack Trace page displays a list of method calls, starting with the method
being executed when the stack trace was requested, in last in first out order. For
each method, the list includes the Class Name, Method Name and (optionally) a
line number.
To view a Stack Trace:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click the link in the Client Request column. The Request Detail page for that
request opens.
4. Click Stack Trace from the left navigation pane. The Stack Trace page opens.
The most recently executed method displays first in the Stack Trace.
Related topics
Canceling a request
Changing a thread's priority
Viewing a Method/Component Trace - flow view
About this task
The Flow View lists the method flow of the current request, in terms of the
method/component entry and exit events in last in first out order.
To view the flow view of a Method/Component Trace:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click the link in the Client Request column. The Request Detail page for that
request opens.
4. Click Method/Component Trace on the left navigation pane. The
Method/Component Trace (flow view) page opens. The last executed method
displays first in the Method/Component Trace.
122
ITCAM for Application Diagnostics: User Guide
5. Enter the Delta Elapsed Time and the Delta CPU Time value under the
Threshold Highlighter table to highlight the data with the features that you
want to view throughout the whole trace.
6. Click Apply. The Complete Flow View table displays the method flow list with
the highlighted data that you selected to view.
7. Click Reset to Default for using the default threshold highlighter value, if
necessary.
8. Click to select the number of rows of data that you want to view per page from
the Pagination list box. The Flow View tab refreshes displaying the number of
rows of data you selected to view on each page.
Results
To export the method/component trace to a comma-delimited file, click the Export
to File button. See “Exporting to a file - SAD” on page 125.
To export the method/component trace to a PDF file and view or save this file,
click the View PDF button. See “Viewing a PDF file - SAD” on page 125.
To export the method/component trace to a PDF file and e-mail this file, click the
E-Mail button. See “E-mailing a PDF file - SAD” on page 124.
Related topics
Canceling a request
Changing a thread's priority
Viewing a request object and session object
About this task
The Request Object and Session Object page lists information for the current
request object and session object.
To view the request object and session object trace:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display server selection page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
page opens.
3. Click the link in the Client Requests' column. The Request Detail page for that
thread opens.
4. Click Request/Session Object from the left navigation pane. The Request
Object and Session Object page opens.
Related topics
Canceling a request
Changing a thread's priority
Searching a Method/Component Trace
About this task
The search allows you to specify any of the columns available in the Flow View
(Elapsed Time, CPU Time, Delta Elapsed Time, Delta CPU Time, Event Type or
Event Data), together with a numerical threshold (or a string, ) and presents a list
of events from the method trace whose metrics cross the threshold (or match the
string). The Event Type and Event Data searches are case sensitive.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
123
To search a Method/Component Trace:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display page opens.
2. Select a server from the Server list box. The Server Activity Display (Active
Requests) page opens.
3. Click the link in the Client Request column. The Request Detail page for that
request opens.
4. Click Method/Component Trace from the left navigation pane. The
Method/Component Trace (Flow View) page opens. The last executed method
displays first in the Method Trace.
5. Click the Search tab. The Search tab opens.
6. Enter the search criteria and the search value.
7. Click Search. The Method Trace page refreshes displaying the method trace
that suits your search criteria and value. Clicking the result in the Event Data
column opens the Flow View tab to the corresponding line. For example, if the
first result in the Search tab is the twentieth method on the Flow View page,
then clicking the Event Data link of the first result will bring up the Flow View
tab starting with the page that includes that twentieth record.
Related topics
Viewing a Composite Method Trace - SAD
Viewing a Method/Component Trace - Flow View
E-mailing a PDF file - SAD
About this task
You can e-mail a PDF file of the Method Trace/Component Trace to one or a group
of the application monitor users. Separate multiple addresses with a comma.
Recipients must have valid user accounts and proper permissions in order to view
the report.
To e-mail a PDF file:
1. From the top navigation, click Problem Determination >Server Activity
Display. The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. To view the detail, click the link in the Client Requests' column. The Request
Detail page for that thread opens.
4. Click Method/Component Trace. The Method/Component Trace page opens.
5. Click the E-mail button. The E-mail page opens.
6. Enter the e-mail address of the recipient. Separate multiple addresses with a
comma.
7. Click OK.
Related topics
Exporting to a file - SAD
Viewing a PDF file - SAD
124
ITCAM for Application Diagnostics: User Guide
Viewing a PDF file - SAD
About this task
Before e-mailing a PDF file, view the file by downloading it.
To view a PDF file:
1. From the top navigation, click Problem Determination > Server Activity
Display . The Server Activity Display page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click the link in the Client Requests' column. The Request Detail page for that
thread opens.
4. Click Method/Component Trace. The Method/Component Trace page opens.
5. Click the View PDF button.
6. From the File Download window, click either Open to view the file
immediately or click Save to download the file.
Related topics
Exporting to a file - SAD
E-mailing a PDF file - SAD
Exporting to a file - SAD
About this task
You can export the trace data to a comma-delimited file format.
To export to a file:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display server selection page opens.
2. Select a group and a server from the list boxes. The Server Activity Display
(Active Requests) page opens.
3. Click the link in the Client Requests' column. The Request Detail page for that
thread opens.
4. Click Method/Component Trace. The Method/Component Trace page opens.
5. Click the Export to File button.
6. Click either Open to view the file immediately or click Save to download the
file.
Related topics
E-mailing a PDF file - SAD
Viewing a PDF file - SAD
Web Session Browser
The Web Session Browser page provides information on open HTTP sessions. You
can search a server, a group, or all servers and groups for all sessions or sessions
with a specific username.
Visualization Engine will only show sessions on servers that have the monitoring
level set to L2 or L3.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
125
To search for Web Sessions on all servers, select "All Groups" in the Group control
and "All Servers" in the Server control.
To search for Web Sessions on all servers in a group, select the group name in the
Group control and "All Servers" in the Server control.
To search for Web Sessions on a specific servers, select the group name in the
Group control and the server name in the Server control.
If you need to search for sessions with a specific username, enter it in the
Username control.
To launch the search, click the OK button. The search results will be displayed. See
“Viewing the Web Session Browser.”
Viewing the Web Session Browser
About this task
Use the Web Session Browser to find information on HTTP sessions. Search a
server, a group, or all servers and groups for a specific session. After activating the
search, the system will take a snapshot of the server(s) and return a list of sessions.
Using a wildcard (*) indicates that all data will be searched. Blank fields are
disallowed in the search. The Data Collector must be at L2 or higher monitoring
level to provide the data for this display page.
To view the Web Session Browser:
1. From the top navigation, click Problem Determination > Web Session
Browser. The Web Session Browser page opens.
2. Select a group and server and enter the user name that you want to search for.
The Web Session Browser page opens showing the sessions that match your
search criteria. After the system returns your search results, you can review the
attributes of a session by clicking the View link in the Attributes field.
Many different kinds of Java objects, including customized objects, can be in a
session; sometimes in the form of binary data. ITCAM cannot display this data
on the front-end in a useful way. In order to display the data correctly, define
the toString() method. ITCAM will invoke this method and display the data
returned in the Web Session Browser. If the toString() method is not defined,
ITCAM will publish the content of the Java objects as-is, which might not
contain useful data.
Related topics
Memory Diagnosis
View heap and memory information.
Server activity
The Server Activity Display page shows a table of request activity on an
application server. This page can help you troubleshoot and fix hanging
requests and evaluate the current performance of your applications.
Memory diagnosis
View heap and memory information.
126
ITCAM for Application Diagnostics: User Guide
Memory Diagnosis includes the following features: Memory Analysis, Heap
Analysis, Memory Leak, and Heap Dump Management. Gain insight into the
JVM's heap and memory information through memory diagnosis. Use this
information to tune the JVM parameters, assess your resources, and find evidence
of memory leaks.
The Memory Analysis (Garbage Collection) option is not supported for CICS or
IMS. The Memory Analysis (Java Heap Size option) is not available for IMS. The
Heap Analysis and Memory Leak features are not available for CICS or IMS. Heap
Dump files can be viewed using Memory Dump Diagnostic for Java (MDD4J).
User Scenarios
Scenario 1: Detecting a memory leak
After creating a Memory Analysis report that compares JVM Heap Size to Average
Response Time, you think there is a memory leak. Access the Memory Leak feature
to see if the amount of uncollected memory is increasing. You set up a candidate
for the server in question. This tells the system to collect heap data now and again
after a specified amount of time. Then you can compare the heap data for the two
periods of time to determine if there is evidence of a memory leak.
Scenario 2: Supporting your claim that the purchase of new servers is necessary
The year end budget is due and you need to project whether you will need to buy
more servers for your environment. You create a Memory Analysis report during
peak usage and compare JVM Heap Size to the Number of Sessions. The number
of servers is close to maxing out the current environment. As a capacity planner,
you recommend that the company increase the number of servers currently
servicing the environment.
Heap Dump Management
Use the Heap Dump Management pages to view and schedule heap dumps for the
monitored servers.
To access Heap Dump Management, from the top navigation click Problem
Determination > Memory Diagnosis > Heap Dump Management.
To create heap dumps, you need to install IBM Support Assistant and Memory
Dump Diagnostic for Java on the monitored servers. See “Downloading Memory
Dump Diagnostic for Java from IBM Support Assistant” on page 128.
To view information on existing heap dumps and delete the heap dumps you no
longer want to store, select Heap Dumps in the left navigation pane. See “Heap
Dumps” on page 129.
To view all scheduled heap dumps, modify and delete the schedules, select Heap
Dump Schedule in the left navigation pane. See “Heap Dump Schedule” on page
130.
To schedule a new heap dump, select Schedule a Heap Dump in the left
navigation pane. See “Scheduling a heap dump” on page 130.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
127
Downloading Memory Dump Diagnostic for Java from IBM
Support Assistant
About this task
In order to download Memory Dump Diagnostic for Java (MDD for Java), you will
need to first download IBM Support Assistant (ISA). ISA provides extra help with
diagnosing problems and provides extra tools and components for troubleshooting
as well as providing a place to write problems (PMR). MDD for Java analyzes
either a single heap dump or analyzes and compares two heap dumps and
searches for evidence of a memory leak. You can either manually take a heap
dump or schedule a heap dump using the Heap Dump Management tool and then
download the heap dump to your PC and analyze it using MDD for Java.
MDD for Java only analyzes heap dumps from IBM JDKs. For non-IBM JDKs use
ITCAM Heap Analysis features.
Searching capabilities are not supported for ITCAM for WebSphere in ISA.
To download ISA:
1. Go to the URL https://www14.software.ibm.com/webapp/iwm/web/
preLogin.do?source=isa
2. If you do not have a universal IBM user ID, you will need to click register now
and fill in the required information. Upon completion, you can return to this
page and sign in to download ISA.
3. After signing in, select the radio button to download IBM Support Assistant
Version 3.0.0.1.
4. Click Continue.
5. Select View license. After reading the license, click the I agree check box and
then click I confirm to continue with the download.
6. Click Download now next to the correct platform. We suggest you download
to the server on which the data collector is installed. Do not download to the
server that has the managing server.
7. Click Save to download ISA to your hard drive.
Results
To install ISA:
1. Go to the directory on your hard drive where you saved the ISA zip file.
2.
3.
4.
5.
Extract the files.
Double-click the setupwin32.exe file.
Follow the installation instructions to install ISA.
Open the ISA program.
To install MDD for Java:
Double-click Updater to open.
Select the New Products and Tools tab.
Open the WebSphere directory by clicking the + sign.
Click the check box to select WebSphere Application Server. (The version you
select does not matter.)
5. Click Install.
6. Select the feature under Features to Install and review the license.
1.
2.
3.
4.
128
ITCAM for Application Diagnostics: User Guide
7. Click Yes to accept the license.
8. Click OK to accept the message that displays, "New product plug-ins or tool
plug-ins were installed successfully. Please make sure to restart IBM Support
Assistant for these changes to take effect."
9. Click the + sign next to the Common Component Tools directory.
10. Click the check box to select Memory Dump Diagnostic for Java (MDD4J)
version 3 or above.
11. Click Install.
12. Click OK to accept the message that displays, "Reminder–You are installing a
common component tool. After installation, you might not see the common
component tool in the Tools component. Common component tools only
display in the Tools component if a product is added that uses them." This is
why you need to install a version of WebSphere.
13. Select Memory Dump Diagnostic for Java under the Features to Install and
review the license.
14. Click Yes to accept the license.
15. Click OK at the restart IBM Support Assistant message.
16. Close ISA and restart.
Related topics
Scheduling a heap dump
“Heap Dump Schedule” on page 130
The Heap Dump Schedule page shows a table of scheduled heap dumps on the
monitored servers. From this page, you can modify and delete the schedules.
Heap Dumps
The Heap Dumps page shows a table of existing heap dumps on the monitored
servers. From this page, you can delete the heap dumps you no longer want to
store.
To view the Heap Dumps page, from the top navigation click Problem
Determination > Memory Diagnosis > Heap Dump Management.
In the table, heap dumps are grouped by server. You can hide the heap dumps for
a server by clicking - next to the server name, and show them again by clicking +.
To view heap dumps for servers in a server group, select the group name in the
Group list box; to view heap dumps for a single server, select the server name in
the Server list box.
For every heap dump, the table shows:
v The fully qualified file name. (The file is located on the monitored server).
v The date and time when the heap dump was created.
v The origin of its creation ("Schedule" for normal scheduled heap dumps).
v Whether garbage collection was forced before creation of the heap dump. This
option can be set in the heap dump schedule.
v A Delete button.
To delete a heap dump, click the Delete button.
You can use the left navigation pane to view scheduled heap dumps and schedule
a new heap dump. See “Heap Dump Management” on page 127.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
129
Heap Dump Schedule
The Heap Dump Schedule page shows a table of scheduled heap dumps on the
monitored servers. From this page, you can modify and delete the schedules.
To view the Heap Dump Schedule page, from the top navigation click Problem
Determination > Memory Diagnosis > Heap Dump Management. Then from the
left navigation pane, Select Heap Dump Schedule
In the table, scheduled heap dumps are grouped by server. You can hide the heap
dumps for a server by clicking - next to the server name, and show them again by
clicking +.
To view heap dump schedules for servers in a server group, select the group name
in the Group list box; to view heap dumps for a single server, select the server
name in the Server list box.
For every heap dump schedule, the table shows:
v The date and time when the heap dump is to be created.
v Whether garbage collection is to be forced before creation of the heap dump.
v A Modify button.
v A Delete button.
To modify a heap dump schedule, click the Modify button. This will open the
Schedule a Heap Dump page (see “Scheduling a heap dump”); you will be able to
modify the settings. To save the changes, click OK
To delete a heap dump schedule, click the Delete button.
You can use the left navigation pane to view existing heap dumps and schedule a
new heap dump. See “Heap Dump Management” on page 127.
Scheduling a heap dump
About this task
You have the flexibility to schedule a heap dump to take place now or in the
future.
To schedule a heap dump:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Heap Dump Management. The Heap Dump Management page opens.
2. Click the Schedule a Heap Dump link.
3. Select a group and a server from the list boxes.
4. Under Heap Dump Schedule, select Now to schedule a heap dump to take
place immediately, or select your own date and time in the future.
5. Under Garbage Collector Before Heap Dump, select yes or no based on
whether you want a garbage collection performed prior to the heap dump.
6. Click OK to save the schedule for the heap dump.
Related topics
Downloading Memory Dump Diagnostic for Java from IBM Support Assistant
“Heap Dump Schedule”
The Heap Dump Schedule page shows a table of scheduled heap dumps on the
monitored servers. From this page, you can modify and delete the schedules.
130
ITCAM for Application Diagnostics: User Guide
Memory Analysis
Use the Memory Analysis page to create a memory analysis report, to help
investigate potential memory problems related to garbage collection and the JVM
heap size.
To access the Memory Analysis page, from the top navigation click Problem
Determination > Memory Diagnosis > Memory Analysis.
To create a Memory Analysis report, select the server group name in the Group list
box, select the server name in the Server list box, select the analysis type (Garbage
Collection or Java Heap Size), and click the Next button. In the Metric Selection,
select the option that contains the two metrics you want to compare, and click the
View Results button. See “Creating a Memory Analysis report.”
Creating a Memory Analysis report
About this task
Investigate potential memory problems related to garbage collection and the JVM
heap size by using the Memory Analysis. When there is over 24 hours of data,
your reports will show the last 48 hours; in all other cases, the last 60 minutes of
data will display.
To create a Memory Analysis report:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Memory Analysis. The Memory Analysis page opens.
2. Select a group and a server or all servers from the list boxes.
3. Select the Analysis Type: Garbage Collection or Java Heap Size.
4. Click Next.
5. In the Metric Selection, select the option that contains the two metrics you want
to compare.
6. Click View Results. The Memory Analysis report displays.
7. Using the Memory Analysis Options, you can select a different group or server,
compare two different metrics, or view a different time increment. A new report
displays based on your new selections. If there is over 24 hours of data
available, your report will show the last 48 hours. Otherwise your report will
display the last 60 minutes.
Related topics
Creating a Memory Leak Candidate Finder report
Creating a Memory Leak Confirmation report
Setting up a Heap Analysis
Heap Analysis
Use the Heap Analysis page to set up a heap analysis, which captures the runtime
heap of an application server, breaks it down by class names of objects in the heap,
and provides the number of instances and the size they occupy.
To access the Heap Analysis page, from the top navigation click Problem
Determination > Memory Diagnosis > Heap Analysis.
To set up a heap analysis, select the server group name in the Group list box,
select the server name in the Server list box, select whether a Garbage Collection
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
131
should be forced before taking the heap snapshot, and click the OK button. See
“Setting up a Heap Analysis.”
Setting up a Heap Analysis
About this task
The Heap Analysis captures the runtime heap of an application server and breaks
it down by the class names of the objects residing in the heap at the time of the
snapshot, while providing the number of instances and the size they occupy.
To set up a Heap Analysis:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Heap Analysis. The Heap Analysis page opens.
2. Select a group and a server.
3. Select Yes or No to perform a garbage collection on the heap prior to the Heap
Analysis snapshot.
4. Click OK. The Heap Analysis results display in the same window.
5. If you want to narrow the results, enter the names of the classes you want to
ignore into the Exclude (Class name) list. If you specify regular expressions in
the Exclude list, but want to monitor a subset of these, enter the names of
classes you want to monitor into the Exclude Override (Class name) list.
6. Click Apply. The new Heap Analysis displays.
7. Click Reset to return the class name filters to their original settings.
Related topics
Creating a Memory Analysis report
Creating a Memory Leak Candidate Finder report
Creating a Memory Leak Confirmation report
Viewing a Memory Leak Candidate Finder report
Memory Leak
Use the Memory Leak page to create a Memory Leak Confirmation report, which
might help determine whether a memory leak is occurring in one of the
applications on a server. You can also use this report to create Memory Leak
Diagnosis and Memory Leak Candidate Finder report, which might help diagnose
the source of a memory leak.
To access the Memory Leak page, from the top navigation click Problem
Determination > Memory Diagnosis > Memory Leak.
To create a Memory Leak Confirmation report, select the server group name in the
Group list box, select the server name in the Server list box, and click the OK
button. See “Creating a Memory Leak Confirmation report.”
Creating a Memory Leak Confirmation report
About this task
Uncover a memory leak trend using the Memory Leak Confirmation report.
Compare heap size to several load-oriented metrics to determine that there is in
fact a leak, not just a change in workload. The system highlights a leak trend by
comparing the average heap size after a garbage collection with a memory
increase, increase in users, or increase in volume.
To create a Memory Leak Confirmation report:
132
ITCAM for Application Diagnostics: User Guide
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Memory Leak. The Select a server page opens.
2. Select a group and a server from the list boxes and click OK. The Memory
Leak Confirmation report displays.
3. Use the list boxes in the Report Control box to select a new group, server, date
range, metric 1, 2, or 3 and click OK to rerun the report. If there is over 24
hours of data available, your report will show the last 48 hours. Otherwise
your report will display the last 60 minutes.
Results
To get further information, you can view Memory Leak Diagnosis and Memory
Leak Candidate Finder reports.
A Memory Leak Diagnosis report provides application diagnostic details. To create
and view a Memory Leak Diagnosis report, click Memory Leak Diagnosis in the
left navigation pane. See “Creating a Memory Leak Diagnosis report.”
A Memory Leak Candidate Finder report creates a heap snapshot, waits a specified
time, and creates another snapshot; comparison of these snapshots can help reveal
memory leaks in applications. To start the creation of a Memory Leak Candidate
Finder report, click Create New Candidate in the left navigation pane, see
“Creating a Memory Leak Candidate Finder report” on page 134. After the
specified time has elapsed, view the report by clicking View Existing Candidates
in the left navigation pane, see “Viewing a Memory Leak Candidate Finder report”
on page 134.
Related topics
Creating a Memory Analysis report
Creating a Memory Leak Candidate Finder report
Setting up a Heap Analysis
Creating a Memory Leak Diagnosis report
About this task
In the Memory Leak Diagnosis report each row in the Suspected Memory Leaks
table represents an allocation pattern for which memory allocation data has been
collected. When a memory leak occurs objects accumulate on the heap and increase
over time. The growth data informs you as to what is growing on the heap.
To create a Memory Leak Diagnosis report:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Memory Leak. The Select a server page opens.
2. Select a group and a server from the list boxes and click OK. The Memory
Leak Confirmation report displays.
3. From the Additional Tools box, click the Memory Leak Diagnosis link. The
Memory Leak Diagnosis report page displays, showing the server and group
you selected, as well as essential server information and the date and time this
report was generated. The list of suspected memory leaks follows.
If you receive the error CYNVE0746E: This server not instrumented for detail heap
data collection. This might indicate that the application server has not received
any requests yet. Run Memory Leak Diagnosis again when you know requests
are in the system. Check that the Level 3 monitoring mode and the heap
analysis flag on the Data Collector have been enabled. If you still receive this
error, contact the system administrator.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
133
4. Click the Class Name link to view references to live objects on the heap. See
“Viewing References to Live Objects on the Heap” on page 135.
Related topics
Creating a Memory Analysis report
Creating a Memory Leak Confirmation report
Viewing a Memory Leak Candidate Finder report
Viewing References to Live Objects on the Heap
Creating a Memory Leak Candidate Finder report
About this task
The Memory Leak Candidate Finder report lets you create a comparison report of
two heap snapshots. Taking two heap snapshots will show if, over time, the
number of instances of a specific class is increasing. In cases, where the number of
instances of a class continues to rise over a period of time, the report will
demonstrate this leak candidate.
To create a Memory Leak Candidate Finder Report:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Memory Leak. The Select a server page opens.
2. Select a group and a server from the list boxes and click OK. The Memory
Leak Confirmation report displays.
3. From the Additional Tools box, click Create New Candidate link. The Create
New Candidate page opens.
4. Select a group and a server.
5. Enter the Wait Time and select hours or minutes from the list box. (There is a
48 hour maximum.) The Wait Time is the amount of time the system must wait
before taking the second heap snapshot.
6. Click Save. The Memory Leak Candidate Finder Management page displays
the report with a waiting status. Check the report for results after your wait
time elapses. If you receive a failed status on your Memory Leak Candidate
Finder report this indicates that either the data collector restarted, the
managing server is down, or there is not enough memory to run the report.
Related topics
Creating a Memory Analysis report
Creating a Memory Leak Confirmation report
Viewing a Memory Leak Candidate Finder report
Viewing a Memory Leak Candidate Finder report
About this task
The Memory Leak Candidate Finder report displays the data comparison between
two heap snapshots. The heap results display unfiltered. You can filter the heap
results by class name using the Exclude (Class name) and Exclude Override (Class
name) lists. Use this data to evaluate whether a memory leak is in progress on
your system.
To view a Memory Leak Candidate Finder report:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Memory Leak. The Select a server page opens.
2. Select a group and a server from the list boxes and click OK. The Memory
Leak Confirmation report displays.
134
ITCAM for Application Diagnostics: User Guide
3. From the Additional Tools box, click View Existing Candidates link. The
Memory Leak Candidate Finder Management page opens.
4. The status for your report will be completed. Click the Server Name's link to
open your previously created report. The Memory Leak Candidate Finder
report opens.
5. Click Comparison Data on the left navigation pane. The comparison data
displays with the data for each heap snapshot.
6. To view each heap individually, click either Heap 1 or Heap 2 on the left
navigation pane. This gives you another view of the heap analysis for your
current data.
7. To filter your data more precisely, enter the classes you don't want to analyze
into the Exclude (Class name) list. If you specify regular expressions in the
Exclude list, but want to monitor a subset of these classes, enter the classes you
want to monitor into the Exclude Override (Class name) list. The report will
refresh and display with the current data. When the comparison for the
Memory Leak Candidate Finder report displays the heap snapshot data, the
data includes the class name, the change in the number of instances, and the
change in total size. Watch the change in the number of instances; increasing
numbers are an indicator of a memory leak in your system.
Related topics
Creating a Memory Leak Candidate Finder report
Creating a Memory Analysis report
Viewing References to Live Objects on the Heap
About this task
Occasionally objects on the heap do not get garbage collected because another
object has a reference to the original object. After clicking the Class Name link, the
data displays which object is linked to the object that is growing.
To view the References to Live Objects on the Heap:
1. From the top navigation, click Problem Determination > Memory Diagnosis >
Memory Leak. The Memory Leak Overview page opens.
2. From step three, select a group and a server and click View Diagnosis. The
Memory Leak Diagnosis page opens.
3. Select the Class Name link. The References to Live Objects on the Heap page
displays.
Related topics
Creating a Memory Analysis report
Creating a Memory Leak Confirmation report
Creating a Memory Leak Diagnosis report
Viewing a Memory Leak Candidate Finder report
JVM thread display
Use the JVM thread display page to view all threads running within the JVM of an
application server.
To view the JVM thread display page, from the top navigation click Problem
Determination > JVM Thread Display. You can also access this page from the
toolbox icon
on the Server Activity Display page.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
135
Select the server group name in the Group list box, and the server name in the
Server list box. If you access this page from the Tivoli Enterprise Portal and from
the Server Activity Display page, the server group name and server name display
automatically.
At the top of the page, the snapshot date and time and the server name and IP
address are displayed. The timestamp for Snapshot Date and Snapshot Time is
collected from the Data Collector and converted to the time zone of the managing
server.
The page initially displays a list of top-level thread groups and active threads.
To view thread groups and active threads within a thread group, click the name of
the thread group. A Thread Group Properties pane displays on the right of the
page, showing information for the current thread group. To return to an upper
level thread group, click ...
To view information for a thread, click its name. A Thread properties pane
displays on the right of the page, showing information for the thread.
To change priority for the thread, in the Thread properties pane select the new
priority in the Priority list box and click the Change Priority button. See
“Changing a JVM thread's priority” on page 137.
Important: The new priority remains for the life of the thread. As a result, any
requests assigned to that thread after the change hold that priority.
To view a stack trace for the thread, in the Thread properties pane click the View
Stack Trace button. See “Viewing a stack trace” on page 137.
CAUTION:
Canceling a thread might cause JVM and application server instability. Use the
cancel thread function only when absolutely necessary, and with careful
consideration of the consequences.
To cancel the thread, in the Thread properties pane click the Cancel Thread
button. See “Canceling a thread” on page 138.
To troubleshoot a multithreaded application, you might need to view the thread
dump, which includes detailed information about memory allocation of all threads
in the JVM. To view the thread dump, click the Thread Dump button, located in
Server Properties at the top of the page. See “Viewing a thread dump” on page
138.
User Scenarios
Scenario 1: How to alleviate high server response time
You are asked to investigate server A where response time and JVM CPU% are
higher than expected, but throughput is normal. You don't see any active requests
in the In-flight Request Search, so you suspect there might be threads running
outside the application server. You access the JVM Thread Display and notice a
couple of suspect threads. After taking a thread dump for the JVM, find the details
of the current thread that is misbehaving and either re-prioritize or cancel the
thread.
136
ITCAM for Application Diagnostics: User Guide
Changing a JVM thread's priority
About this task
If a thread is executing too slowly, you can change its priority by moving it up in
the stack, so that it can process a request quickly.
To change a thread's priority:
1. From the top navigation, click Problem Determination > JVM Thread Display.
The JVM Thread Display Server selection page opens.
2. Select a group and a server to view the running threads. The JVM Thread
Display page opens showing all top level thread group running in the selected
server.
3. Select and click to the right of the thread for detailed information.
4. From the priority list box in the Thread Properties table, select a number.
Priority 1 is the lowest and priority 10 is the highest.
5. Click Change Priority. The priority list box displays the priority you selected
for the thread to execute request. When changing a thread's priority, be aware
that the new priority remains for the life of the thread. As a result, any requests
assigned to that thread after the change will hold that priority during that
request's lifetime.
Related topics
Canceling a thread
Viewing a stack trace
Viewing a stack trace
About this task
The Stack Trace page displays the sequence of method execution and in last in first
out order. The last executed method will be displayed first in the stack trace.
To view a stack trace:
1. From the top navigation, click Problem Determination > JVM Thread Display.
The JVM Thread Display Server selection page opens.
2. Select a group and a server to view the running threads. The JVM Thread
Display page opens showing all top level thread group running in the selected
server.
3. Select and click a thread for detailed information. The Thread Properties table
displays the detailed information of the thread that you selected.
4. Click View Stack Trace The Stack Trace page opens.
The stack trace shows the outstanding methods waiting to execute as a result of
the request. This trace reports the data unfiltered, so you will see every class. In
a normal environment, a request executes quickly so it might be difficult to
catch a stack trace before completion.
Related topics
Changing a JVM thread's priority
Canceling a thread
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
137
Canceling a thread
About this task
If a thread is misbehaving, for example looping, sleeping or abusing resources, it
might be necessary to cancel the thread and terminate the executing Java thread to
let other threads to proceed. By default, only "Administrator" role will have access
to the canceling a thread functionality
To cancel a thread:
1. From the top navigation, click Problem Determination > JVM Thread Display.
The JVM Thread Display Server selection page opens.
2. Select a group and a server to view the running threads. The JVM Thread
Display page opens showing all top level thread group running in the selected
server.
3. Select and click a thread that you want to view its detailed information. The
Thread Properties table displays the detailed information of the thread that you
selected.
4. Click Cancel Thread.
5. Click OK in the confirmation box. The JVM Thread Display page refreshed
displaying without the canceled thread.
Canceling a thread might cause JVM and application server instability. Use the
cancel thread function only when absolutely necessary, and with careful
consideration of the consequences.
Related topics
Changing a JVM thread priority
Viewing a stack trace
Viewing a thread dump
About this task
To troubleshoot a problematic multithreading application with a hung thread or
looping thread, you might need to view the Thread Dump page for detailed
information about memory allocation of threads in a JVM.
When a user clicks thread dump on the JVM Thread Display page, a snapshot will
be taken showing the data about all threads. You can view the Thread Dump page
for detailed information about memory allocation of threads in a JVM.
To view the Thread Dump page:
1. From the top navigation, click Problem Determination > JVM Thread Display.
The JVM Thread Display Server selection page opens.
2. Select a group and a server to view the running threads. The JVM Thread
Display page opens showing all top level thread group running in the selected
server.
3. Click Thread Dump. The Thread Dump page opens.
Related topics
Changing a JVM thread's priority
Canceling a thread
138
ITCAM for Application Diagnostics: User Guide
Trap and alert management
Use the Trap and alert management page to define and modify traps and alerts
that monitor server health and determine problems with applications, and to view
the history of triggered traps and alerts.
To access trap and alert management, from the top navigation, click Problem
Determination > Trap & Alert Management.
You can also access this page from the toolbox icon
Display page.
on the Server Activity
Use trap and alert management to monitor server health and determine problems
with applications. Prevent disruptions in service by receiving alerts before
problems arise. Gather data that helps you pinpoint the root cause of
difficult-to-reproduce problems.
The page shows a table of active traps and another table of defined trap profiles.
(You can activate a trap based on a trap profile).
For each active trap the table shows:
v The name of the trap.
v The name of the server that the trap applies to. If the trap applies to multiple
servers, you can click + to view the list.
v The number of minutes for which the trap will be suppressed before triggering,
if applicable. This avoids triggering a trap on a short load spike.
v The duration of the trap; the trap will be deactivated when this duration expires.
Traps can also have an infinite duration.
v Time left until the duration expires (N/A if the duration is infinite).
v The time when this trap was activated.
v The user who has activated the trap.
v A Deactivate button.
To deactivate a trap, click the Deactivate button. See “Deactivating a trap” on page
148.
For each trap profile the table shows:
v The name of the trap profile.
v The description.
v The user who has created the profile.
v Activate, Modify, Modify, and Delete buttons.
To activate a trap based on the profile, click the Activate button. See “Activating a
trap” on page 147.
To modify a trap profile, click the Modify button. See “Modifying a trap” on page
148.
To create a trap profile as a copy of an existing profile, click the Duplicate button.
See “Duplicating a trap” on page 149.
To delete a trap profile, click the Delete button. See “Deleting a trap” on page 149.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
139
To create a new trap profile, click Create trap in the left navigation pane, and
select the trap type and target type. See:
v “Setting an Application trap”
v “Setting an Application trap using the Resident Time - Misbehaving Transaction
target type” on page 143
v “Setting a Server Resource trap” on page 145
To view the history of triggered traps, click Trap Action History in the left
navigation pane. See “Viewing the trap action history” on page 150.
User Scenario
Scenario 1: Debugging complex applications
You are monitoring application A, which has a J2EE component on server S and a
legacy CRM back end. The Java component of application A frequently exhibits
idle times of several seconds, even when there is not much load on server S. You
do not wish to run at L3, but you want to see in what methods the Java
application is waiting. You set an Application Trap for Wait Time with a Threshold
of 2,000 ms, by Request for application A, choose the Stack Trace Data Action and
apply this trap to server S. The next time a request for application A takes longer
than two seconds, the system will take a stack trace of server S. Look in the Trap
Action History to obtain the stack trace, to determine where application A is
waiting.
Setting an Application trap
About this task
An Application trap detects metrics in a request, method, or SQL or MQI call. The
system triggers the trap after the monitored server exceeds the threshold for the
metric you set. When the trap is triggered, and when the action conditions are met,
then any alerts you have activated (whose conditions have been met) will be sent,
and any actions you have specified (whose conditions have been met) will be
performed.
To set an Application trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. On the left navigation pane, click Create Trap. The Trap Type selection page
opens.
3. Select Application Trap as the trap type.
4. Select one of the Target Types from the list box. Based on the target type you
select, the system will dynamically generate the trap definition options in the
next step. The following is a list of the Target Types:
v Occurrence - The number of times the specified unit occurred. The
Occurrence trap has three available filters; By Request; By Method, and By
SQL.
v CPU Time - The amount of time the CPU is executing instructions. The
CPU Time trap has two available filters, By Request and By Method.
v Wait Time - The amount of time the CPU is idle. The Wait Time trap has
two available filters, By Request and By Method.
v Resident Time - In-flight - Based on the resident in-flight time of a
transaction, the Publish Server keeps track of all the active (in-flight)
140
ITCAM for Application Diagnostics: User Guide
requests and their resident times and triggers the trap if the resident time of
the request exceeds the time configured in the trap condition. The Resident
Time - In-flight trap has one available filter, the By Request filter.
v Resident Time - Completed - The wall clock time for when the unit of a
transaction, method, etc. ends, minus the wall clock time when it started.
The Resident Time - Completed trap has three available filters; By Request;
By Method, and By SQL.
v Resident Time - Misbehaving Transaction - This trap has one available
filter, the By Request filter. With this target type, when the complete
response request time violates the threshold in the trap definition, the
monitoring level for the request switches from L1/L2 to L3 and
component/method trace detail is captured. As switching from L1/L2 to L3
has a performance impact on the Data Collector, there are 2 fields you can
use to deactivate the trap and return to the original L1/L2 monitoring level
once the required detail has been captured:
– Number of occurrences of every request after which the trap will be
deactivated - The purpose of this field is to prevent the Data Collector
from running at L3 indefinitely. The value in this field determines the
number of times you want every request to reach the threshold before
the trap is deactivated. Using this field enables you to capture
component/method trace detail at L3 when the threshold is exceeded,
and to then automatically revert to the original monitoring level, thereby
reducing the performance cost to the server.
– Number of occurrences of every request that doesn't violate this trap
after which mod level is reverted back and trap is deactivated - Once
L3 is enabled, after the trap condition is violated the first time, it remains
at L3 until the request violates for the predetermined number of times as
set in the Number of occurrences of every request after which the trap
will be deactivated field. As a result, the request in the Data Collector
will remain at L3 if the request doesn't violate for the predetermined
number of times, resulting in performance cost to the Data Collector. To
prevent this, use this field - Number of occurrences of every request
that doesn't violate this trap after which mod level is reverted back
and trap is deactivated.
Once the trap triggers and the monitoring level switches to L3, if the
number of requests that does not reach the threshold is equal to the
value in this field, then the trap is deactivated. For further detail on this
target type, see “Setting an Application trap using the Resident Time Misbehaving Transaction target type” on page 143
v Uncaught Exception - Capture exceptions that occur in applications and
data about the failure. The Uncaught Exception trap has three available
filters; By Request, Exception or Error Class Name.
v Lock Acquisition Time - In-flight - The in-flight transaction has not
completed and might be hanging, using this type will provide data on how
to fix the problem. What is being measured is the amount of time taken to
obtain an acquisition. The acquisition clock starts when the class/method
begins trying to acquire the lock, and ends when the lock is acquired. The
Lock Acquisition Time - In-flight trap has two available filters, By Request
and By Method.
v Lock Acquisition Time - Completed - The amount of time taken to obtain
an acquisition. The acquisition clock starts when the class/method begins
trying to acquire the lock, and ends when the lock is acquired. The Lock
Acquisition Time - Complete trap has two available filters, By Request and
By Method.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
141
Traps are now supported in CICS. CICS has the following trap types available:
Occurrence, CPU time, Resident Time - Completed, Resident Time - In-flight,
and Wait Time.
Note: By default, the Publish Server does not process requests which run
longer than 5 minutes. Therefore, if an application trap's threshold is greater
than or equal to 300 seconds, the trap will not be triggered. To change this
default setting in the Publish Server, in the psX.properties file, change the
TIMEOUT_LIMIT property to greater than 5 minutes as required. The
properties files for the Publish Servers are located here: MS_HOME/etc/. They
are named with the convention psX.properties, where X is an integer. By
default, there are 2 files, ps1.properties and ps2.properties, if you add
another Publish Server instance, the properties file will be called
ps3.properties and for all additional instances of the Publish Server, the
integer value in the properties file name will increment by 1.
5. Click Next. The Step 2 - Define Trap page opens.
6. Complete the rest of the fields in the Trap Definition section, which restrict
which events will trigger the trap to fire.
7. Click Next. The Set Trap Alerts page opens.
8. For the Trap Alert settings, under Condition enter the number of times the
trap will occur before the system takes an action. Specify the amount of time
under Time Interval to monitor how many times the trap met its conditions.
9. Click to select the severity level from the list box. The application monitor has
three severity levels. Since the application monitor provides SNMP integration
with Tivoli, map the three severity levels of the application monitor to the
warning levels of Tivoli listed in the following table:
ITCAM severity level
Tivoli warning level
Low
Harmless
Medium
Minor
High
Critical
10. Select an action or multiple actions, such as sending an e-mail or SNMP
message, for the system to take when the condition is met.
11. Select one or all Data Actions, such as Component/Method Trace, Stack Trace,
or Thread Dump (not applicable to the Windows platform), to get detailed
information. We recommend that you select Component/Method Trace as the
data action, since a request executes quickly and it is difficult to catch before
completion. Make sure that you have selected L3 monitoring level if you
choose to collect Component/Method Trace as the Data Action. When setting
a trap, you can select multiple trigger conditions and alerts for each action set.
Each trap is required to have at least one action but may have multiple actions
set. Thread Dump is not available for CICS.
12. Click Add to add the alert to your trap. If you select Component/Method
Trace as the Data Action for an In-flight-based trap, the method trace might
contain a "-1" for Depth on some events in the method trace. In-flight
transactions, by definition, are incomplete transactions, so the request stacks of
those transactions will be incomplete.
13. Set the Default Suppression settings by entering the amount of time you want
to delay alerts after the first alert is sent.
14. Click Next to proceed. The Name Trap page opens.
15. Enter a name and descriptive text for your trap.
142
ITCAM for Application Diagnostics: User Guide
16. Click either Save or Save & Activate.
17. If you click Save, the Trap and Alert Management page opens displaying your
new trap.
18. If you click Save & Activate, the Activate page opens. To activate a trap, see
Activating a Trap.
Related topics
Activating a trap
Setting a Server Resource trap
Setting an Application trap using the Resident Time Misbehaving Transaction target type
About this task
A Resident Time - Misbehaving Transaction is a target type for an Application
Trap. With this target type, when the resident time of a request violates the
specified level in the trap definition, the monitoring level for that specified request
switches from L1/L2 to L3. For all the subsequent resident time violations for that
request, method trace detail is captured.
This target type provides an efficient means of collecting method trace detail at L3
as you can configure the data collector to return to L1/L2 after the threshold is
reached a certain number of times within a given time period, thereby reducing
the performance cost to the data collector. This target type also provides a dynamic
means of collecting method trace detail as detail is collected at the time the
problem is occurring.
To set an Application trap with a Resident Time - Misbehaving Transaction
target type:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. On the left navigation pane, click Create Trap. The Trap Type selection page
opens.
3. Select Application Trap as the trap type.
4. Select Resident Time - Misbehaving Transaction as the target type.
5. Click Next. The Step 2 - Define Trap page is displayed. In the Threshold field,
enter a value. This value is the complete request response time expressed in
milliseconds. When a transaction reaches this value, the trap is triggered.
6. In the By Request field, choose Request Contains and then enter the value *.
When the By Request field contains the value *, the Resident Time Misbehaving Transaction trap will deactivate after every request has reached
the specified number of occurrences as specified in the Number of
occurrences of every request after which the trap will be deactivated field.
7. Click Next. The Step 3 - Set Trap Alerts page is displayed. In the Severity
field, select a severity level. The application monitor has three severity levels.
Since the application monitor provides SNMP integration with Tivoli, map the
three severity levels of the application monitor to the warning levels of Tivoli
listed in the following table:
ITCAM severity level
Tivoli warning level
Low
Harmless
Medium
Minor
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
143
High
Critical
8. In the Alert Action(s) section, choose how and to whom you wish to
communicate details of the trap threshold being reached. You can choose
e-mail, SNMP or both.
9. Select Collect Component/Method Trace.
10. Click Add to add the alert to your trap. In the Name section, enter a name
and a description for the trap. Click Save & Activate. The Activate page is
displayed
11. In the Server Selection section, select the servers you wish to monitor for this
trap.
12. In the Alert Suppression Settings section, enter the amount of time you want
to delay alerts after the first alert is sent. Click the Trap Default radio button
to use the default suppression for the trap, or click the Override Default radio
button to set a specific suppression duration for this particular trap
activation. If you do not want to suppress any alerts, enter a value of 0, or
leave the field blank.
13. In the Deactivation Settings section, there are 2 fields. Here is a description of
each field:
v Number of occurrences of every request after which the trap will be
deactivated - The purpose of this field is to prevent the Data Collector from
running at L3 indefinitely. The value in this field determines the number of
times you want every request to reach the threshold before the trap is
deactivated. Using this field enables you to capture component/method
trace detail at L3 when the threshold is exceeded, and to then automatically
revert to the original monitoring level, thereby reducing the performance
cost to the server.
A problem can occur if this value is not reached. If the Number of
occurrences of every request after which the trap will be deactivated
value is not reached, then the server will remain at L3 resulting in a
continuous performance cost. To prevent this from happening use the field Number of consecutive non-violating requests after which mod level is
reverted back and trap deactivated.
v Number of consecutive non-violating requests after which mod level is
reverted back and trap deactivated - Once L3 is enabled, after the trap
condition is violated the first time, it remains at L3 until the request violates
for the predetermined number of times as set in the Number of occurrences
of every request after which the trap will be deactivated field. As a result,
the request in the Data Collector will remain at L3 if the request doesn't
violate for the predetermined number of times, resulting in performance
cost to the Data Collector. To prevent this, use this field - Number of
consecutive non-violating requests after which mod level is reverted back
and trap deactivated. Once the trap triggers and the monitoring level
switches to L3, if the number of requests that does not reach the threshold
is equal to the value in this field, then the trap is deactivated. A field for
this value is also displayed in the Active Traps table in the Trap and Alert
Management page. The field is Non Violating Requests Left, it indicates
the number of occurrences of non violating requests before the trap is
deactivated.
14. Click Activate to activate the trap.
144
ITCAM for Application Diagnostics: User Guide
Results
Related topics
Activating a trap
Setting a Server Resource trap
Setting an Application Trap
Setting a Server Resource trap
About this task
A Server Resource trap measures a variety of target types. The system will trigger
a trap after exceeding the threshold for the metric you set. When the system
meets the definition of the trap an alert occurs. For example, set a trap to alert you
when a server is unavailable 2 times, and after a server is unavailable you can
select to receive an e-mail.
To set a Server Resource trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. On the left navigation pane, click Create Trap. The Trap Type selection page
opens.
3. Select Server Resource trap as the Trap Type.
4. Select one of the following target types from the list box.
v CPU: Average Platform CPU % Usage - Based on the average platform
CPU usage over five minutes, the Publish Server retrieves CPU usage at
regular intervals (60 seconds by default) and calculates the average platform
CPU over five minutes.
v Average JVM CPU % Usage - Based on the average JVM CPU usage over
five minutes, the Publish Server retrieves CPU usage at regular intervals (60
seconds by default) and calculates the average JVM CPU over five minutes.
v Memory:
v JVM Heap Size - Based on the JVM Heap Size of the data collector, the
Publish Server retrieves JVM Heap Size from the data collector at regular
intervals (60 seconds by default) and checks the heap size from that
measure.
v Garbage Collection Frequency - Garbage Collection is calculated over one
minute (supported in ITCAM J2EE WebLogic).
v Average JVM Heap Size after Garbage Collection - The trap triggers when
the average JVM Heap size exceeds the size configured in the trap
(supported in ITCAM J2EE WebLogic)
v Application Capacity:
Number of Sessions - Based on the number of user sessions that are
currently in use by the application server.
v Average Response Time - Publish Server triggers the trap if the average
response time exceeds the time configured in the trap condition (supported
in ITCAM J2EE WebLogic).
v Server available - Publish server triggers the trap when the Server (Data
Collector) becomes available (supported in ITCAM J2EE WebLogic).
v Server unavailable - The Publish server triggers the trap if the Server (Data
Collector) goes down or becomes unavailable (supported in ITCAM J2EE
WebLogic).
v
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
145
5.
6.
7.
8.
v Uncaught Java Exceptions - Based on the rate of the Java exceptions that
occur in applications and includes data about the failure. It is calculated
over 60 seconds. Publish server triggers the trap if the Servlet error rates
exceed the number configured in the trap condition.
v Request Frequency - Number of requests per minute.
v Resource Pool :
v Thread Pool % Usage - Publish Server triggers the trap if the Thread Pool
% Usage of a particular server exceeds the threshold that is specified in the
trap condition (supported in ITCAM J2EE WebLogic).
v JCA Pool % Usage - Publish Server triggers the trap if the JCA Pool %
Usage of a particular server exceeds the threshold that is specified in the
trap condition (supported in ITCAM J2EE WebLogic).
v JDBC Pool % Usage - Publish Server triggers the trap if the JDBC Pool %
Usage of a particular server exceeds the threshold that is specified in the
trap condition (supported in ITCAM J2EE WebLogic).
Click Next. The Define Trap page opens.
Enter a threshold that will send out an alert when it triggers the trap after
meeting the condition.
Click Next. The Set Trap Alerts page opens.
For the Trap Alert settings, under Condition enter the number of times the
trap occurs before the system takes an action. Specify the amount of time
under Time Interval to monitor how many times the trap met its conditions.
Click to select the severity level from the list box.
9.
Note: The application monitor has three severity levels. Since the application
monitor provides SNMP integration with Tivoli, map the three severity levels
of the application monitor to the warning levels of Tivoli listed in the
following table:
ITCAM severity level
Tivoli warning level
Low
Harmless
Medium
Minor
High
Critical
10. Select an action or multiple actions, such as sending an e-mail or SNMP
message, for the system to take when the condition is met.
11. The Data Action–Heap Dump is only available if you select JVM Heap Size or
Average JVM Heap Size after Garbage Collection as your Target type.
12. Click Add to add the alert to your trap.
13. Set the Default Suppression settings by entering the amount of time you want
to delay alerts after the first alert is sent.
14. Click Next to proceed. The Name Trap page opens.
15. Enter a name and descriptive text for your trap.
16. Click either Save or Save & Activate.
17. If you click Save, the Trap and Alert Management page opens displaying your
new trap.
18. If you click Save & Activate, the Activate page opens. To activate a trap, see
Activating a Trap .
146
ITCAM for Application Diagnostics: User Guide
Results
If you select the <= operator while creating or modifying the Request Frequency
target type, then the following sequence of events occurs:
1. The trap action does not trigger if no transactions are received by the Publish
Server after activating the trap.
2. Trap threshold checking begins after the first transaction received by the
Publish Server activates the trap.
Note: When setting a trap, you can select multiple trigger conditions and alerts for
each action set. Each trap is required to have at least one action but can have
multiple actions set.
Related topics
Activating a trap
Activating a trap
About this task
You can turn traps off and on by activating and deactivating them. Traps use
resources on the managing server, including database storage, and generate
network traffic, so make sure the thresholds you set to trigger your traps are
realistic.
To activate a trap:
1. A trap is activated at the end of the trap creation dialog by clicking the Save &
Activate button on the Name Trap panel; see “Setting an Application trap” on
page 140 or “Setting a Server Resource trap” on page 145 to start from the
beginning of the trap creation process. To activate an existing trap, from the top
navigation, click Problem Determination > Trap & Alert Management. The
Trap and Alert Management page opens.
2. In the Trap Profiles list, click Activate next to the trap you want to activate. The
Activate page opens.
3. Select a group and a server.
Note: If you select all servers the trap will be applied to all servers assigned to
the group (whether currently available or unavailable) at the time the trap is
activated. Any new servers assigned to the group will not use the trap.
4. Set the Alert Suppression settings by entering the amount of time you want to
delay alerts after the first alert is sent. Click the Trap Default radio button to
use the default suppression for the trap, or click the Override Default radio
button to set a specific suppression duration for this particular trap
activation. If you do not want to suppress any alerts, enter a value of 0, or
leave the field blank.
5. If you want the trap to run indefinitely, do not check either of the check boxes
in the deactivation settings section. If you want the trap to deactivate, click one
or both of the check boxes for deactivation, and fill in the value(s) for minutes
or occurrences. If both deactivation settings are selected, the trap will deactivate
when the first of the two deactivation conditions is met.
6. Click Activate. The Trap and Alert Management page displays the trap in the
Active Traps table at the top of the page.
Related topics
Deactivating a trap
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
147
Duplicating a trap
Modifying a trap
Setting a Server Resource trap
Setting an Application trap
Deactivating a trap
About this task
Deactivate your traps when they are no longer required since they can add
overhead to the system. The traps in the Trap Profiles table are not active.
To deactivate a trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. In Active Traps table, click Deactivate next to the trap you want to deactivate.
3. Click OK at the confirmation box. The trap displays in the Trap Profiles table
as deactivated.
Results
Note: A trap must be deactivated prior to modification.
Related topics
Activating a trap
Modifying a trap
Setting a Server Resource trap
Setting an Application trap
Modifying a trap
About this task
After creating a trap, you can modify any of the parameters of a trap. Change the
Group, Server, Trap Type, Target Type, Alert Conditions, and the Action that occurs
when the system meets the conditions. Using this method, you can reuse and
modify old traps for different servers.
Note: A trap must be deactivated prior to modification. (See “Deactivating a
trap.”)
To modify a trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. In the Trap Profiles, click Modify next to the trap you want to modify. The
Modify page opens.
3. If you want to change the Trap Definition, enter a new threshold that will
trigger the trap after meeting the condition.
4. If you want to change the Trap Alert settings, under Condition enter the
number of times the trap occurs before the system takes any action, including
sending an e-mail or sending an SNMP message. Specify the amount of time
under Time Interval to monitor how many times the trap met its conditions. In
addition, set the Alert Suppression settings by entering the amount of time you
want to delay alerts after the first alert is sent.
148
ITCAM for Application Diagnostics: User Guide
5. Select one or all Data Actions to get detailed information (not applicable to the
Windows platform), such as Component/Method Trace, Stack Trace, and
Thread Dump. Data Action is not applicable to Server Resource trap.
6. Click Add to add a new alert to your trap. If you select Component/Method
Trace as the Data Action for an In-flight-based trap, the method trace might
contain a "-1" for Depth on some events in the method trace. In-flight
transactions, by definition, are incomplete transactions, so the request stacks of
those transactions will be incomplete.
7. If you want to change the name, enter a new name and descriptive text for
your trap. This will replace the old name when saved.
8. Click Save. The Trap and Alert Management page opens displaying your
modified trap.
Related topics
Activating a trap
Setting a Server Resource trap
Setting an Application trap
Duplicating a trap
About this task
Save time by duplicating traps. Duplicating a trap allows you to quickly create a
new trap based on the settings of an existing trap.
To duplicate a trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. In the Trap Profiles table, click Duplicate next to the trap you want to
duplicate. The Duplicate page opens.
3. Select the trap you want to duplicate from the list box.
4. Enter a name for the new trap.
5. Click Save. The new trap displays in the Trap and Alert Management page.
Related topics
Activating a trap
Deactivating a trap
Modifying a trap
Deleting a trap
About this task
Manage your traps by keeping them up-to-date. Delete existing traps from the
system that are no longer in use.
To delete a trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
Note: A trap must be deactivated prior to deletion. (See “Deactivating a trap”
on page 148)
2. In the Trap Profiles table list, click Delete next to the trap you want to delete.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
149
3. Click OK at the confirmation box. The Trap and Alert Management page opens
displaying without the deleted trap.
Related topics
Activating a trap
Modifying a trap
Setting a Server Resource trap
Setting an Application trap
Viewing the trap action history
About this task
The Trap Action History page provides a record of traps that met the set
conditions. You can view the trap history such as the date and time that the action
was taken, trap properties, server name, severity, and the type of action that was
taken.
To view a fired trap:
1. From the top navigation, click Problem Determination > Trap & Alert
Management. The Trap and Alert Management page opens.
2. On the left navigation pane, click Trap Action History. The Trap Action History
opens displaying the information for the fired traps.
3. Click Show Filters. You may either filter the information by server or by server
and trap name but not by the trap name only.
4. Click to select the group name and the server name, and a trap name (if
applicable), then click Filter. The Trap Action History page refreshes displaying
the filtered trap information that you selected.
The history of a method trace for an in-flight transaction may show -1 for the
Depth. In-flight transactions, by definition, are incomplete transactions, so the
request stacks of those transactions would be incomplete which makes
calculating depth for partial events (a start without an end event) impossible.
The Trap Action History page now displays the Data Collector process ID
information.
5. To delete a fired trap history, check the Delete box next to the trap that you
want to delete and click Delete. The Trap Action History page refreshes
displaying without the deleted trap history.
Related topics
Activating a trap
Setting alert actions and data actions
Setting alert actions and data actions
About this task
Regardless of the trap type, you must specify trap actions as part of the trap
definition.
Trap actions include alerts and data actions. Alerts include messages sent by e-mail
or SNMP, whereas data actions capture Method Traces, Stack Traces or Thread
Dumps.
Trap actions occur when a trap triggers. You can configure alert actions to be
suppressed, to avoid getting spammed by alerts.
150
ITCAM for Application Diagnostics: User Guide
To set alert actions and data actions:
1. You can set trap alerts on the Step 3 - Set Trap Alerts page, which is part of
the trap creation process. To arrive at this page, see “Setting an Application
trap” on page 140 or “Setting a Server Resource trap” on page 145.
2. For the Trap Alert settings, in the condition field, enter the number of times
the trap will trigger before the action is taken.
Note: This value will be applied to all the trap actions defined in the next two
steps. If you want to define multiple actions, each with a different condition,
repeat steps 2-4 once for each distinct condition.
3. Click to select the severity level from the list box.
Note: The application monitor has three severity levels. Since the application
monitor provides SNMP integration with Tivoli, the three severity levels of the
application monitor are mapped to the warning levels of Tivoli listed in the
following table:
ITCAM severity level
Tivoli warning level
Low
Harmless
Medium
Minor
High
Critical
4. Add at least one action, either an alert action (e-mail or SNMP message) or a
data action (Method Trace, Stack Trace or Thread Dump.) (The Thread Dump
is not available on the Windows platform.)
5. To select an action, click its check box. For the e-mail action, also enter the list
of e-mail addresses to which the message will be sent.
6. Click Add to add the actions to your trap. Repeat this step until you have
added all the actions you want. You can change the values of the condition
and severity fields (steps 2 and 3) each time you add a new action. If you
select Component/Method Trace as the Data Action for an In-flight-based
trap, the method trace may contain a "-1" for Depth on some events in the
method trace. In-flight transactions, by definition, are incomplete transactions,
so the request stacks of those transactions will be incomplete.
7. Set the Default Suppression setting if you want to avoid getting spammed by
Alert Actions that might occur close together in time.
8. Click Next to proceed. The Name Trap page opens.
9. Enter a name and descriptive text for your trap.
10. Click either Save or Save & Activate. If you click Save, the Trap and Alert
Management page opens displaying your new trap. If you click Save &
Activate, the Activate page opens. To activate a trap, see "Activating a Trap".
Results
You can configure the Time Interval in the Trap Alert Settings page to milliseconds,
seconds, minutes, hours, days or weeks. The smallest available time interval unit is
milliseconds, certain trap types might not be able to use milliseconds as the time
unit. Use the following table as a guideline for setting the Time Interval value with
default Managing Server and Data Collector settings.
Trap Type
Target Type
Minimum Time Interval
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
151
Server Resource Trap
Average Platform CPU %
Usage
5 (min)
Average JVM CPU % Usage
5 (min)
JVM Heap Size
1 (min)
Average JVM Heap Size after 1 (min)
GC
Application Trap
Request Frequency
1 (min)
Number of Sessions
1 (min)
Occurrence
1 (ms)
CPU Time
1 (ms)
Wait Time
1 (ms)
Resident Time – In-Flight
1 (ms)
Resident Time – Complete
1 (ms)
Resident Time – Misbehaving 1 (ms)
Transaction
Uncaught Exceptions
1 (ms)
Lock Acquisition Time –
In-Flight
1 (ms)
Lock Acquisition Time –
Completed
1 (ms)
Related topics
Activating a trap
Software consistency check
Identify irregular servers.
Use the software consistency check to troubleshoot aberrant servers in an
otherwise homogenous server group.
This feature is not available for CICS or IMS.
User Scenarios
Scenario 1: Comparing a non-functioning server with working servers
After an upgrade to Application B, which is deployed on multiple servers, requests
on Server D are occasionally hanging while all the other servers are working fine.
As an Operator, you check the Runtime Environment and compare the server
having problems with one of the properly functioning servers. Go to the Installed
Binary Check to see if the files on both servers are the same. You find that one of
the files on Server D is not the same as the file on the server that is properly
functioning. Install the proper file to correct the problem.
Installed Binary Comparison
Use the Installed Binary Comparison page to compare the installed binaries on a
chosen server (the Authoritative Server) with up to 10 additional servers (the
Comparison Servers).
152
ITCAM for Application Diagnostics: User Guide
To set up the installed binary comparison, select the authoritative servers and the
comparison servers. See “Setting up an Installed Binary Comparison.”
Setting up an Installed Binary Comparison
About this task
Analyze the data from the Installed Binary Comparison to find out whether your
servers contain the same installed binaries. The Installed Binary Comparison allows
you to compare the installed binaries on a chosen server (the Authoritative Server)
with up to 10 additional servers (the Comparison Servers). The comparison
describes whether or not your servers contain the same installed binaries.
To setup an Installed Binary Comparison:
1. From the top navigation, click Problem Determination > Software Consistency
Check > Installed Binary Comparison. The Installed Binary Comparison page
opens.
2. Under the Authoritative Server, select a group and a server.
3. Under the Comparison Servers, select a group and a server, or select multiple
servers within that group by clicking Ctrl + the server name.
4. Click Next to continue. The File selection page opens.
5. Click to select the File Source (EAR file or class path) and the File Types (JAR,
Web, class, or image files).
6. Click OK. The Installed Binary Comparison results page displays the overview
data first with the results of the comparison.
Results
See “Viewing the results of the Installed Binary Comparison.”
Related topics
Viewing the results of the Installed Binary Comparison
Viewing the results of the Installed Binary Comparison
About this task
Review the comparison to find the differences among installed binaries on your
servers. Differences in the installed binaries in a server farm can cause unexplained
behavior.
To view the results of the Installed Binary Comparison:
1. Navigate the results of the binary comparison by clicking the expansion icon
next to the server name on the left navigation pane.
2. To view further details, click the server name and select either the Matched or
Unmatched folders.
3. To view the folder contents, in the Matched folders: select Full Match, File
Name/Path/Size Match, or File Name Match, and in the Unmatched folders:
select either Authoritative Only or Comparison Only.
4. To perform an MD5 on a file, click Perform MD5. You can only perform an
MD5 on files that are a Full Match or a File Name/Path/Size Match. The
results display whether the files matched or not at the MD5 level.
Results
The files in the Matched folders contain files that match to varying degrees:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
153
v Full Match - indicates that everything matched, including the file name and
path, size, and file system timestamp. These files are likely to be identical to
each other. However, the user can opt to further perform a MD5 operation on
the files. An MD5 is a unique numeric signature that is different for each file
when the contents of the files are different, even if the creation date and the file
names coincide.
v File Name/Path/Size Match - includes the files with matched file name and
path, and size, but not timestamp. These files are likely to be the same. A user
can opt to perform an MD5 on the files.
v File Name Match - indicates that only the file names matched. The files are
unlikely to be the same.
The files in the Unmatched folders contain files that exist on either the
Authoritative Server or the Comparison Server but not on both:
v An Authoritative Only indicates that the file only exists on the Authoritative
Server.
v A Comparison Only indicates that the file only exists on the Comparison Server.
Related topics
Setting up an Installed Binary Comparison
Installed Binary Check
The Installed Binary Check page provides a list of the installed binaries deployed
to the selected server.
To access the Installed Binary Check page, from the top navigation, click Problem
Determination > Software Consistency Check > Installed Binary Check.
Select the server group name in the Group list box, and the server name in the
Server list box, and click the Refresh button to view the binary information for the
server.
The page shows a table of all application binaries installed on the server; the type,
fully qualified name, modification time, and size are displayed.
In the Name column, click on directory names (these files display DIR in the Type
column) to view details on binaries within the directories.
Click on JAR and EAR file names to view a list of the file contents.
Runtime Environment Comparison
Use the Runtime Environment Comparison page to compare the runtime
environments on a chosen server (the Authoritative Server) with up to 10
additional servers (the Comparison Servers).
To set up the runtime environment comparison, select the authoritative servers and
the comparison servers. See “Setting up a Runtime Environment Comparison.”
Setting up a Runtime Environment Comparison
About this task
Analyze the data in the Runtime Environment Comparison and find out if the
runtime environments on all your clone servers are setup the same.
To set up a Runtime Environment Comparison:
154
ITCAM for Application Diagnostics: User Guide
1. From the top navigation, click Problem Determination > Software Consistency
Check > Runtime Environment Comparison. The Runtime Environment
Comparison page opens.
2. Under the Authoritative Server, select a group and a server.
3. Under the Comparison Servers, select a group, and then select multiple servers
within that group by clicking Ctrl + the server name.
4. Click Next to continue. The Runtime Environment Comparison results page
displays the data.
5. For specific data on the server, click any of the options in the left navigation
under System Runtime Environment, Java Runtime Environment, and the App
Server Runtime Environment.
6. For a complete detail report on a particular server, click the server's name. The
Runtime Environment Check page displays all the available data on the system
runtime environment, Java runtime environment, and the appserver runtime
environment for the selected server.
7. Click Change Comparison to set up another runtime environment comparison.
Related topics
Viewing the results of the Installed Binary Comparison
Runtime Environment Check
The Runtime Environment Check page provides runtime environment details for
the selected server, including host computer, JVM and application server
information.
To access the Installed Binary Check page, from the top navigation, click Problem
Determination > Software Consistency Check > Runtime Environment Check.
Select the server group name in the Group list box, and the server name in the
Server list box in the left pane.
Note: If you have a WebSphere Stack Product, such as WebSphere Process Server,
WebSphere Portal Server, WebSphere Enterprise Service Bus, etc., which runs on an
IBM WebSphere Application Server, the name of the application server is displayed
when you Run the Runtime Environment Check.
Note: After configuring data source with the administration web application
provided by Tomcat, the MBean from MBeanServer cannot be retrieved. As the
result, the JDBC Connection Pools column will always be 0 on the page Runtime
Environment Check. This is a Tomcat 5.0 bug (latest version Tomcat 5.0.28) and
only occurs in the Tomcat 5.0 series. Tomcat 5.5 series does not have the problem.
Performance analysis and reporting
Analyze applications and servers.
Use performance analysis and reporting to analyze historical data. This helps you
understand the performance of your applications and the utilization of your
servers.
User Scenarios
Scenario 1: Investigating poor response time claims
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
155
Customers have been complaining about poor performance on Application A. As a
performance analyst, you go into ITCAM for Application Diagnostics and draw up
a response Trend Report for Application A for the last week to verify the
customers' claims. Once you are able to see that there indeed are instances of poor
response time, you decompose the problematic period to see how different requests
impact the response time. Drill down to a method trace of an actual instance of a
slow transaction, and e-mail this Trace Report to the developers so they can
determine why the transaction was slow.
Scenario 2: Predicting how your servers will handle a new workload
Marketing is going to launch a new campaign to bring more visitors to your site.
Your manager wants to make sure that there is enough capacity to handle the
projected workload without degrading response times. As a capacity planner, you
need to project how well your current servers will perform under the new
workload. You create a Capacity Analysis report to compare throughput versus
response time. You can use the trend line to estimate at what throughput the
response time will be unacceptable.
Defining reports
Set report requirements.
Set different requirements for generating reports to analyze the performance of
application servers.
Defining a Request/Transaction Analysis report
About this task
The Request/Transaction Analysis report provides a whole picture about the
behavior on the application server. After defining the request/transaction analysis,
several reports become available: Trend report, Decomposition report, Request
report detail, and Trace report. Each of these reports provides more specific data
for understanding the application's performance at every level.
To define a Request/Transaction Analysis report:
1. From the top navigation, click Performance Analysis> Create Application
Reports > Request/Transaction. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
v Metric - Throughput per Hour, Throughput per Second, Throughput per
Minute, Response Time, and CPU Time.
v Request Type - All, EJB, JSP, Servlet, CICS, Web Service, OTMA, VTAM®,
BTAM, APPC, Portal, and RMI-IIOP.
v Request Name - Unless you know the exact request string, always leave the
field blank to return all requests or type in the specific request name.
6. Click Next to continue creating the report. The Date Range settings page
opens.
156
ITCAM for Application Diagnostics: User Guide
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report. If you want to get a second data set for
comparative analysis, click Next to open the Report Comparison page. The
Report Comparison page opens.
9. Select a report comparison type and view the comparison report by clicking
View Report.
10. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a Method/Program Analysis report
About this task
The Method/Program Analysis report shows you the performance of the methods
in the requests that have been processed by the application servers. After defining
the Method/Program Analysis report, a Trend report, Decomposition report, and
detailed Method/Program report are available.
To define a Method/Program Analysis report:
1. From the top navigation, click Performance Analysis> Create Application
Reports > Method/Program. The Create reports page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
v Metric - Throughput per Second, Throughput per Minute, Throughput per
Hour, Response Time (ms), and CPU Time (ms).
v Method/Component Trace - Unless you know the exact string, always leave
the field blank to return all traces or type in the specific
method/program/component name.
Note: The name of this field represents the names used in J2/WAS and
z/OS. Method name is used in the J2/WAS environments, and Program
and component name are used in the z/OS environments.
v Request Type - ALL, EJB, JSP, Servlet, CICS, Web Service, and Portal.
v Request Name - Unless you know the exact request string, always leave the
field blank to return all requests or type in the specific request name.
6. Click Next to continue creating the report. The Date Range settings page
opens.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
157
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report. If you want to get a second data set for
comparative analysis, click Next to open the Report Comparison page. The
Report Comparison page opens.
9. Select a report comparison type and view the comparison report by clicking
View Report.
10. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a SQL Analysis report
About this task
The SQL Analysis report provides the information for the SQL calls' performance
in the requests that have been processed by the application server. You can also
view the Trend report, Decomposition report, and detailed SQL report after
defining the SQL Analysis report.
To define a SQL Analysis report:
1. From the top navigation, click Performance Analysis> Create Application
Reports > SQL. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting No. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server on which you want to report from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
v Metric - Throughput per Second, Throughput per Minute, Throughput per
Hour and Response Time.
v SQL Call - All, Insert, Delete, Update, Execute, Select, Lock, Unlock, Open,
Close and Fetch.
v Table Name - Leave blank for all table names or type in the specific table
name.
v Request Type - All, EJB, JSP, Servlet, CICS, Web Service, and Portal.
v Request Name - Unless you know exactly what the request string is,
otherwise always leave the field blank to return all requests or type in the
specific request name.
v Method/Component Trace - Leave blank for all methods or type in the
specific name.
6. Click Next to continue creating the report. The Date Range settings page
opens.
158
ITCAM for Application Diagnostics: User Guide
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report. If you want to get a second data set for
comparative analysis, click Next to open the Report Comparison page. The
Report Comparison page opens.
9. Select a report comparison type and view the comparison report by clicking
View Report.
10. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining an MQI Analysis report
About this task
The MQI Analysis report provides the information for the MQI calls' performance
in the requests that have been processed by the application server. You can also
view the Trend report, Decomposition report, and detailed MQI report after
defining the MQI Analysis report.
To define a MQI Analysis report:
1. From the top navigation, click Performance Analysis > Create Application
Reports > MQI. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server on which you want to report from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
v Metric - Throughput per Second, Throughput per Minute, Throughput per
Hour, and Response Time (ms).
v MQI Call- BACK, BEGIN, CLOSE, CMIT CONN, CONNX, DISC, GET,
INQ, OPEN, PUT, PUT1, and SET.
v Queue Manager - manager of the queue.
v Queue Name - Name of the queue.
v Request Type/Transaction Type - All, EJB, JSP, Servlet, CICS, Web Service,
OTMA, VTAM, BTAM, APPC, Portal, and RMI-IIOP
v Request/Transaction Name - Unless you know the exact request string,
always leave the field blank to return all requests or type in the specific
request name.
v Method/Program/Component Trace - Leave the field blank to return all
methods. Type in the specific method name if you know the method name
you are looking for.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
159
6. Click Next to continue creating the report. The Date Range settings page
opens.
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report. If you want to get a second data set for
comparative analysis, click Next to open the Report Comparison page. The
Report Comparison page opens.
9. Select a report comparison type and view the comparison report by clicking
View Report.
10. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Lock Analysis report
About this task
If you suspect that you have lock contention issues with a specific application, you
can run a lock analysis report. This will give you the history of locking in the
application and show whether there is a trend. The lock reports will show you the
difference between the total locks and the ones that are contentious.
To define a Lock Analysis report:
1. From the top navigation, click Performance Analysis > Create Application
Reports > Lock Analysis. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
6.
7.
8.
9.
v Metric - The item you want to measure: Number of Lock Acquisitions,
Number of Lock Contentions and Total Acquisition Time.
v Request Type - All, EJB, JSP, Servlet, Web Service, and Portal.
v Request Name - Unless you know the exact request string, always leave the
field blank to return all requests or type in the specific request name.
v Method/Component Trace - Leave the field blank to return all methods or
type in the specific method name.
Click Next to continue creating the report. The Date Range settings page opens.
Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
Click View Report to view the report.
Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
160
ITCAM for Application Diagnostics: User Guide
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a Portal Page report
About this task
The Portal Page report provides a picture of the behavior within the Portal Page
requests. Once you isolate the problem requests, the portal-specific nested requests
allow you to quickly get a high-level picture of where your problem is taking
place. After defining the portal page report, several reports become available:
Trend report, Decomposition report and Portal Page Detail report.
To define a Portal Page report:
1. From the top navigation, click Performance Analysis > Create Application
Reports > Portal. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
v Metric - The item you want to measure: Throughput per hour, Throughput
per minute, Throughput per second, Response Time and CPU Time.
v Nested Request Type - Portal page and Portlet. You must set this to Portal
Page for a Portal Page report.
v Portal Page Name - Limits the requests that are being reported on to include
only those whose name matches the string you enter.
v Portlet Name - Type in a specific portlet name to show only those portal
pages that contain the portlet name specified.
6. Click Next to continue creating the report. The Date Range settings page opens.
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report.
9. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
161
Defining a Portlet report
About this task
If you want to compare the response time of a portlet across multiple pages, or
debug an application rather than the entire portal server, you can run a portlet
report. This will show the performance of a portlet and not the whole request.
Then you can see if the same portlet has different response times on different
pages. Drilling down allows you to get detailed performance information on a
per-portlet basis. You can see how a portlet performs across the different pages
that it's used on, which can help determine whether the problem you are
encountering is caused by the portlet itself or by the things surrounding it on the
page.
To define a Portlet report:
1. From the top navigation, click Performance Analysis > Create Application
Reports > Portal. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Schedule report.
3. Select the group and the server from the list box.
4. Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
5. Set the following options to filter the records returned in the report:
v Metric - The item you want to measure: Throughput per hour, Throughput
per minute, Throughput per second, Response Time and CPU Time.
v Nested Request Type - Portal page and Portlet. You must set this to Portlet
for a Portlet report.
v Portal Page Name - Type in a specific portal page name to show only those
portlets which are contained in the portal pages whose name matches the
one you specified.
v Portlet Name - Type in a specific portlet name to show only those portlets
that contain the portlet name specified.
6. Click Next to continue creating the report. The Date Range settings page opens.
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report.
9. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
162
ITCAM for Application Diagnostics: User Guide
Defining Top reports
About this task
Top reports are a quick and convenient way to run a report for request, method, or
SQL data. Top reports provide the top 100 results records for the selected metric.
To define a Top report:
1. From the top navigation, click Performance Analysis> Create Application
Reports > Top Reports. The Recurrence report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
instructions on scheduling reports, refer to Defining a Scheduled report.
3. Select the group and the server from the list boxes. The Report and Data Range
selection page opens.
4. Select the type of Top report you want to run and set the date range using the
list boxes. If applicable, set the Advanced Filtering to extract the data of a
specific time period. For detailed instructions, see step two of Understanding
the Date Range settings.
5. Click View Report to open the report. The Top report opens.
6. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Results
Note: The Top Slowest Request Report calculates the average response time by
(sum of the response time)/(total # of requests) given the selected group/server
and time period. This might cause the data in the Slowest Request Report to vary
for the group report and server report for the same time span.
Related topics
Defining a Scheduled report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a System Resource Analysis report
About this task
The System Resource Analysis report gives you the information of the utilization of
the memory, and the connection pool for the application servers. You can also view
a Trend report and Decomposition report after defining the System Resource
Analysis report.
Note: This feature does not apply to the z/OS platform.
To define a System Resource Analysis report:
1. From the top navigation, click Performance Analysis > Create Server Reports
> System Resource. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting no. If you want further
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
163
3.
4.
5.
6.
instructions on scheduling reports, refer to Defining a Schedule report. The
Server and Report Type selection page opens.
Select the group and the server on which you want to report from the list box.
Click Next to continue creating the report. The Report Filtering options page
opens. It displays the options based on the Report Type you select.
Set the following options to filter the records returned in the report: Metric Amount of memory used, JVM/Region CPU %, System CPU %, Average % of
Pool in Use (supported in ITCAM J2EE WebLogic), JDBC Connection Pool
Size (supported in ITCAM J2EE WebLogic), and Live Sessions.
Click Next to continue creating the report. The Date Range settings page
opens.
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
8. Click View Report to view the report. If you want to get a second data set for
comparative analysis, click Next to open the Report Comparison page. The
Report Comparison page opens.
9. Select a report comparison type and view the comparison report by clicking
View Report.
10. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a Server Availability Analysis report
About this task
The Server Availability Analysis report shows the percentage of the server
availability. In the group situation, availability is defined as the total amount of
time when one or more servers in the group are up, divided by the total elapsed
time.
To define a Server Availability Analysis report:
1. From the top navigation, click Performance Analysis > Create Server Reports
> Server Availability. The Create report page opens.
2. Select yes or no to decide if you want the report to recur and click Next. For
the purpose of these instructions we are selecting No. If you want further
instructions on scheduling reports, see Defining a Schedule report.
3. Select the group and the server on which you want to report from the list box.
4. Click Next to continue creating the report. The Date Range settings page opens.
5. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range settings.
6. Click View Report to view the report. If you want to get a second data set for
comparative analysis, click Next to open the Report Comparison page. The
Report Comparison page opens.
164
ITCAM for Application Diagnostics: User Guide
7. Select a report comparison type and view the comparison report by clicking
View Report .
8. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a Capacity Analysis report
About this task
The Capacity Analysis report provides you with the necessary information to
evaluate the capacity of your system using supply and demand metrics.
To define a Capacity Analysis report:
1. From the top navigation, click Performance Analysis > Create Server Reports
> Capacity Analysis. The Server Selection page opens.
2. Select the group and the server on which you want to report from the list box.
3. Click Next to continue creating the report.
4. Set the following options to filter the records returned in the report:
v X - Axis - Throughput per Minute and Users.
v
Y - Axis - System CPU (%), JVM/Process CPU (%), JVM/Process Memory
(MB), and Response Time (ms).
5. Click the check box to select Set Y-axis Max and enter the value you want to
be set to the maximum.
6. Click Next to continue creating the report. The Date Range settings page
opens.
7. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range Settings.
8. Click View Report.
9. Click Save to save the report.
10. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172.
Related topics
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
165
Defining a Schedule report
About this task
Scheduling reports allows you to create a time for your reports to automatically
activate at a time you preselect.
To define a Scheduled report:
1. From the top navigation, click Performance Analysis> Create Application
Reports > Method/Program.
Note: We will use the Method/Program report as an example. You can create
a Scheduled report from a selection of the available reports.
2. Select Yes to have the report recur and click Next. The Server Selection page
opens.
3. Select the group and the server on which you want to report from the list
boxes. Select the Create a separate report for each server check box to create
one report for each server without repeating the steps for each one. If you
don't select the check box, the report provides all the data aggregated across
all servers.
4. Click Next to continue creating the report.
5. Set the following options to filter the records returned in the report:
v Metric - Throughput per Second, Throughput per Minute, Throughput per
Hour, Response Time (ms), and CPU Time (ms).
v Method/Component Trace - Unless you know the exact string, always leave
the field blank to return all traces or type in the specific
method/program/component name.
Note: The name of this field represents the names used in J2/WAS and
z/OS. Method name is used in the J2/WAS environments, and Program
and component name are used in the z/OS environments.
v Request Type - ALL, EJB, JSP, Servlet, CICS, Portal, and Web Service.
v Request Name - Unless you know the exact request string, always leave the
field blank to return all requests or type in the specific request name.
6. Click Next to continue creating the report. The Date Range settings page
opens.
7. Set the parameters to restrict the data returned in your report. For detailed
instructions on setting the parameters, see Understanding the Date Range
settings.
8. To view the report, click Preview. To set a schedule for the report, click
Schedule.
9. Set the schedule for the report and setup an e-mail distribution list of the
people you want the report sent to when it is completed. Unlike a saved
report, you can not click Run Report to view the report at anytime. For a
scheduled report, you can only view the e-mailed PDF of the report. Click
Next.
10. Enter the name of the report. Click Save or Save & Activate. For more
information see “Viewing saved reports” on page 172.
Note: You can either save the report now and activate it later or you can save
and activate the report at the same time.
11. The Scheduled reports page opens displaying your report in the list.
Related topics
166
ITCAM for Application Diagnostics: User Guide
E-mailing a report
Exporting a file
Modifying a report
Understanding the Date Range settings
Viewing a PDF file
Understanding the Date Range settings
About this task
The Date Range settings allow you to set the parameters that restrict the data you
want to capture for a report. You will be given the option to modify these settings
while creating a report. The Date Range settings contain three main sections: Date
Range, Advanced Filtering (optional) and Graphing Option.
This section is not applicable to defining a Top report.
To set the Date Range settings:
1. From the Date Range section, click to select a preset date range or enter a
custom start date and end date for extracting only the data for the time period
specified.
2. To extract the data of a specific time period, define your custom data set in the
Advanced Filtering section:
v Uncheck the hours of the day when you do not want data to display. For
example, to select only data occurring between 9:00am and 5:00pm, uncheck
00:00-08:00 hours and 18:00-23:00 hours.
v Uncheck the days of the week when you do not want data to display. For
example, to select only data occurring Monday through Friday, uncheck
Sunday and Saturday.
v Uncheck the days of the month when you do not want data to display.
v Uncheck the months of the year when you do not want data to display.
By default, the Advanced Filtering section automatically selects all the options.
3. Select any of the following options in the Graphing option for analyzing certain
patterns in the data based on time characteristics, or compiling large amounts
of data over a long period and plotting all the points:
v Time series in minutes
v Time series in hour
v Time series in day
v Time series in week
v Time series in month
v Aggregate minute of the hour
v Aggregate hour of the day
v Aggregate day of the week
v Aggregate month of the year
Results
On the Trend report, if the date range selected is <= 60 minutes, both the graph
and data table will display. If the date range selected is > 60 minutes, only the data
table will display.
Related topics
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
167
Defining a Schedule report
E-mailing a report
Exporting a file
Viewing a PDF file
Viewing the Detail report
About this task
The Detail report allows you to drill down into the data for more information
about the requests. Each detail report provides detail, summary, worst performers,
and locks information for your review.
To
1.
2.
3.
view the detail report:
Create a report.
View the report.
Access the Trend report and click any part of the graph/chart to go to the
Decomposition report.
4. From the Decomposition report, drill down into the detail report.
5. The Detail report has four tabs: detail, summary, worst performers, and locks.
v The Detail tab provides information about each request that made up the
data point selected from the decomposition report.
v The Summary tab provides information about requests across all requests
breaking it down by nested requests so you can view the data component by
component.
v The Worst Performers tab provides information about the requests
containing the worst-performing nested requests based on the selected
metrics.
v The Lock tab provides detailed lock information with the ability to toggle
between the lock acquisition and contention information. Lock Tab is only
available for the Lock Analysis report. This data is the average for all the
requests on the Detail tab of the Detail report.
Note: The following reports can be viewed in PDF format: Trend report,
Decomposition report, Detail report, and Flow View in Trace report. All these
reports can be mailed to users in PDF format and also these reports can be
exported to a file in CSV format.
Note: Detail report is available for all application reports except Top reports.
Related topics
Defining a Schedule report
Understanding the Date Range settings
Defining a Schedule report
E-mailing a report
Exporting a file
Modifying a report
Viewing a PDF file
Defining a Lock Analysis report
Defining a Method/Program Analysis report
Defining a Portlal report
Defining a Request/Transaction Analysis report
168
ITCAM for Application Diagnostics: User Guide
Defining a SQL Analysis report
Defining an MQI Analysis report
Viewing the Trace Report
About this task
The Trace report allows you to drill down into the method flow of a selected
request from the Detail report, in terms of the method/component entry and exit
events. Each trace report provides the following options, Nesting Summary,
Drilldown View, Flow View, and Search tabs to view method trace data in different
formats.
To view the trace report:
1. Create a report.
2. View the report.
3. Access the Trend report and click any part of the graph/chart to go to the
Decomposition report.
4. From the Decomposition report, drill down into the detail report.
5. The Detail report, Detail tab, click Request/Transaction Name, drill down into
the trace report.
6. Inside the Trace report, there are four tabs: Nesting Summary, Drilldown View,
Flow View, and Search.
v The Nesting Summary tab provides information about the top 10 slowest
components. It also provides the total number of calls, the average response
time, and the average CPU time for each component in the selected request.
v The Drilldown tab provides information about method trace at each level.
v The Flow View tab provides the complete method flow of the selected
request.
v The Search tab allows you to specify any of the following types, together
with a numerical threshold (or a string) and presents a list of events from the
method trace whose metrics cross the threshold (or match the string). The
Event Type and Event Data searches are case sensitive.
– Elapsed Time
– CPU Time
– Delta Elapsed Time
–
–
–
–
Delta CPU Time
Event Type
Event Data
Total Acquisition Time
Note: Trace report is available for Request/Transaction report, Lock Analysis
report, and Portal report.
Related topics
Defining a Lock Analysis report
Defining a Portal report
Defining a Request/Transaction Analysis report
Report management
Manage saved reports.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
169
Manage the reports you save on your system: view the reports (click the Report
Name) or run the reports (click Run Report).
Modifying a report
About this task
After creating a report, you can modify the parameters of the report to suit your
changing needs. Change the settings in the Server and Report Type Selection page,
the Report Filtering Options page, the Date Range Settings page, and the Report
Comparison page. Using this method, you can reuse, duplicate, and modify old
reports for different application servers.
To modify a report:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Modify next to the report you want to change. The Recurrence page
opens. Select Yes to have the report recur.
3. Change the group or server, and click Next. The Report Filtering options page
displays different options based on the report type you select.
While you are choosing a server by navigating through the groups, note that
the final group name does not affect the data to be extracted for the
preparation of the report. The group name is immaterial to the selection process
when data is gathered. The report will compile all records that are generated by
the chosen server regardless which group it belongs to.
4. Select the filtering options for your report to examine and limit the type of
records to include in the report.
5. Click Next to continue creating the report. The Date Range Settings page opens.
6. Set the parameters to restrict the data returned in your report. For detailed
instructions, see Understanding the Date Range Settings.
7. Click View Report to view the report. If you want to get a second data set,
click Next to open the Report Comparison page. The Report Comparison page
opens.
8. Select a report comparison type and view the comparison report by clicking
View Report. The Trend report opens.
9. Click Save if you want to save the report. For more information see “Viewing
saved reports” on page 172
Related topics
Understanding the Date Range settings
Defining a Schedule report
Running a report
Modifying a Top report
About this task
After creating a Top report, you can modify its parameters to suit your changing
needs. Change the settings in the Server and Report Type selection page, and the
Report and Date Range selection page. Using this method, you can reuse, duplicate
and modify old reports for different application servers.
To modify a Top report:
1. From the top navigation, click Performance Analysis > View Saved Reports .
The Reports page opens.
170
ITCAM for Application Diagnostics: User Guide
2. Click Modify next to the top report you want to change. The Recurrence page
opens. Select Yes to have the report recur.
3. Change the group or server, and click Next. While you are choosing a server by
navigating through the groups, note that the final group name does not affect
the data to be extracted for the preparation of the report. The group name is
immaterial to the selection process when data is gathered. The report will
compile all records that are generated by the chosen server regardless which
group it belongs to.
4. Click Next to modify the report type, date range, and the filtering options. The
Report and Date Range selection page opens.
5. Select a Top report type from the list box.
6. Set the Start Date, End Date, Start Time, and End Time. If applicable, set the
Advanced Filtering to extract the data of a specific time period. For detailed
instructions, see step 2 of Understanding the Date Range Settings.
7. Click Finish to create the report. The Top report opens.
Related topics
Understanding the Date Range settings
E-mailing a report
Exporting a file
Running a report
Viewing a PDF file
Running a report
About this task
Return to the Performance Analysis and Reporting Management page to run a
saved report and retrieve the current data. Additionally, you can save a report,
e-mail a link or PDF of a report, or view PDF report, export a PDF report to a
comma delimited file format. If you e-mail a link, remember that the recipient
must be a user of the application monitor with the appropriate rights to view the
servers to where the report runs.
To run a report:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. All previously defined and saved reports (except Scheduled reports) display on
the Reports Management page.
3. Click Run Report next to the report you want to run.
Note: The report opens displaying data based on the Metric selected on the
Report Filtering options page. The type of report and metric selected display in
the page heading, for example, Trend report - Throughput per Second Request
Analysis.
Related topics
E-mailing a report
Exporting a file
Viewing a PDF file
Viewing the reports
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
171
Duplicating a report
About this task
Save time creating new reports by duplicating an existing report.
To duplicate a report:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Duplicate next to the report you want to duplicate.
3. Enter a name for the duplicated report, and click Save. The Reports page
displays with the new duplicated report.
Related topics
E-mailing a report
Exporting a file
Viewing a PDF file
Viewing saved reports
About this task
After defining a report other than a Top report, there are six different reports that
display various levels of detail: Trend report, Decomposition report, Method report,
Request report, SQL report, and Trace report. The reports that you have access to
will vary depending on the criteria you select while creating your report. For
example, on the Server and Report Type Selection page, depending on the Report
Type you select, the following reports are available:
v Request/Transaction - displays Trend, Decomposition, Request Detail, and Trace
reports.
v Method/Program - displays Trend, Decomposition, and Method Detail reports.
v SQL - displays Trend, Decomposition, and SQL Detail reports.
v MQI - displays Trend, Decomposition, and MQI Detail reports.
v Lock Analysis - displays Trend, Decomposition, and Lock Analysis Detail
reports.
v Portal - displays Trend, Decomposition, and Portal Page and Portlet Detail
reports.
v Server Availability - displays the Trend report.
v System Resources - displays Trend, and Decomposition reports.
v Capacity Analysis - displays Capacity Analysis Detail report.
To view the reports:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Run Report next to the report you want to run. The Trend report opens
first.
Note: Use the left navigation to return to the Saved Reports page, Modify
reports, or Save a report.
3. Select an option from the Additional Details list box to decompose the Trend
report.
4. Click the bar displayed in the graph or a data point in the table to view more
details. The Decomposition report opens.
172
ITCAM for Application Diagnostics: User Guide
5. Click on a section of the chart or a data point in the table to view more details.
The Request/Transaction Report Detail page opens displaying the Detail data,
the Summary and the Worst Performers.
Results
If you selected Request/Transaction Analysis as the Report Type, to access the
Trace report:
1. Click the Request Name to view the Trace report.
2. The Trace report page - Nesting Summary page opens. For more information
see “Viewing the Nesting Summary” on page 192.
Note: These instructions apply to all the report types available. However,
remember that the reports available depend on the Report Type selected. Top
reports have no additional detail.
Related topics
Defining a Capacity Analysis report
Defining a Request/Transaction Analysis report
Defining Top reports
Deleting a report
About this task
Manage your reports by keeping them up-to-date. Delete existing reports from the
system that are no longer in use.
To delete a report:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click X next to the report you want to remove.
3. At the confirmation box, click OK to delete the report. The Reports page
displays without the deleted report.
Related topics
E-mailing a report
Exporting a file
Viewing a PDF file
E-mailing a report
About this task
You can e-mail a PDF file of a report to either the application monitor users or non
application monitor users. You can also e-mail a link of a report to a group of
application monitor users. The recipient will be brought to a particular page by the
link after logging in. You can e-mail a PDF of the following reports: Trend report,
Decomposition report, Detail report, and Flow View in Trace report
To e-mail a report/PDF:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Run Report next to the report you want to run. The selected report
opens.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
173
3. Click the E-mail PDF icon to e-mail a PDF file of a report. The E-mail page
opens.
4. On the E-mail page, enter the e-mail address of the recipient. Separate multiple
addresses with a comma.
5. Click OK to e-mail the report.
Results
To e-mail a link:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Run Report next to the report you want to run.
The selected report opens.
3. Click the E-mail Link to e-mail a link of a report.
The E-mail page opens.
4. On the E-mail page, enter the e-mail address of the recipient. Separate multiple
addresses with a comma.
5. Click OK to e-mail the link of the report. When you e-mail a link, the recipient
must be a user of the application monitor with the appropriate rights to view
the servers in the report.
Related topics
Exporting a file
Viewing a PDF file
Viewing a PDF file
About this task
You can view a PDF file of a report before you send out the file to another
recipients.
You can view a PDF of the following reports: Trend report, Decomposition report,
Detail report, and Flow View in Trace report
To view a PDF file:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Run Report next to the report you want to run. The selected report
opens.
3. Click View PDF to download a PDF file of a report.
4. From the File Download window, click either Open to view the file
immediately or click Save to save the file.
Related topics
E-mailing a report
Exporting a file
Exporting a file
About this task
You can export a report to a comma delimited file format, if necessary. You can
e-export a PDF of the following reports: Trend report, Decomposition report, Detail
report, and Flow View in Trace report
174
ITCAM for Application Diagnostics: User Guide
To export to a file:
1. From the top navigation, click Performance Analysis > View Saved Reports.
The Reports page opens.
2. Click Run Report next to the report you want to run. The selected report
opens.
3. Click Export to File.
4. Click either Open to view the file immediately or click Save to download the
file. The exported file downloads into the location you specify.
Related topics
E-mailing a report
Viewing a PDF file
Method Profiling
Use the Method profiling pages to create, view and delete method profile reports.
View the method profile reports that have been run and view their details. Delete
reports you no longer want to save.
See “Viewing Method Profiling Management.”
Viewing Method Profiling Management
About this task
The Method Profiling Management page provides a list of all the method profiles
collected and stored in the method profile reports generated as a result. From this
page, you can delete method profile reports and view data about the reports.
To collect method profiles you are required to use L2 and select method profiling,
see “Overriding a monitoring level” on page 77.
To open Method Profiling Management:
1. From the top navigation, click Performance Analysis > Method Profiling. The
Method Profiling Management page opens.
2. Select the group and the server whose method profile you want to view. If
there are no method profiles on that server "Data not available." will display.
3. Click the Date/Time link to view the data for the report. The report opens and
displays the method names contained in the method profile as well as the Total
CPU Time, Total Elapsed Time, Total Hits, Avg. CPU Time, and Avg. Elapsed
Time.
4. To delete the report, click Delete
5. Click OK to finish deleting the report.
Related topics
Activating Method Profiling
“Monitoring on Demand (TM)” on page 73
In the Monitoring on Demand (MOD) pages, you can view and adjust the
monitoring level for all servers, and schedule adjustment of this level at fixed
times.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
175
Activating method profiling
About this task
Method profiling is a new feature that is part of L2 monitoring. You can activate
L2 with method profiling by selecting the monitoring level, overriding the
monitoring level, or creating a schedule that selects the monitoring level. Links to
the instructions to perform these actions are available in the following related
topics.
1. To activate method profiling by creating a schedule, see “Creating a schedule”
on page 75 for more information.
2. To activate method profiling by overriding the monitoring level, see
“Overriding a monitoring level” on page 77 for more information.
3. To activate method profiling by configuring the data collection settings, see
“Configuring the Data Collection settings” on page 79 for more information.
Related topics
“Monitoring on Demand (TM)” on page 73
In the Monitoring on Demand (MOD) pages, you can view and adjust the
monitoring level for all servers, and schedule adjustment of this level at fixed
times.
Viewing Method Profiling Management
Daily Statistics
The Daily Statistics pages provide daily SMF information snapshots for z/OS
WebSphere servers.
The Daily Statistics page provides a list of daily SMF statistics reports available for
a date. Initially, it shows the server reports for the previous day.
To view a report, click the server name. See “Viewing the Daily Statistics
Overview.”
To view reports for a different date, change the date in the Enter Report Date
controls and click the Go button.
To delete all daily statistics report created before a certain date, set this date in the
Delete Reports Older Than controls and click the Delete button. See “Deleting
Daily Statistics” on page 177.
Viewing the Daily Statistics Overview
About this task
The Daily Statistics Overview pages provides daily SMF information snapshots for
z/OS WebSphere servers only. This data is shown for the server selected on the
Daily Statistics page.
To open the Daily Statistics Overview page:
1. From the top navigation, click Performance Analysis > Daily Statistics. The
Daily Statistics selection page opens with the previous day's data.
2. If the snapshots from a different date are desired, from the left navigation pane,
select a month, day, and year under the Enter Report Date heading and click
Go.
176
ITCAM for Application Diagnostics: User Guide
3. Click on a server name to view the Daily Statistics Overview, where the
snapshot data will be presented.
Results
Note: The side navigation can be used to find out more information regarding:
Server, EJBs, Servlet Session Manager, Server Regions, SQL, JCA-CICS, and Web
Applications.
To
1.
2.
3.
4.
change the date of the report:
On the left navigation pane, select a month from the list box.
On the left navigation pane, select a date from the list box.
On the left navigation pane, select a year from the list box.
Click Go.
Related topics
System Resources Metrics
Viewing the System Resources Browser
Deleting Daily Statistics
About this task
You can permanently delete daily statistics by purging the system.
To open the Daily Statistics page:
1. From the top navigation, click Performance Analysis > Daily Statistics. The
Daily Statistics page opens.
2. Use the left navigation to select a month, day, and year under the Delete
Reports Older Than heading.
3. Click Delete.
4. Click Yes in the confirmation box. The system deletes all reports created earlier
than the date you select.
Related topics
System Resources Metrics
Viewing the Daily Statistics Overview
Custom requests
Custom requests are defined for application-specific operations that do not fall
under the normal pre-defined J2EE operations. Use custom requests to track
specific application operations as separate requests. For example, if the application
is performing some well-defined processing like parsing documents, or
CPU-intensive numeric calculation, it might be useful to track this operation as a
separate request.
When you use custom requests, you can set the monitoring level to L2 rather than
L3. L3 generally applies to a large set of methods, typically every application
method, as a result L3 monitoring overhead is high. Custom requests are defined
for specific application methods, and the overhead is much lower. Also, custom
request definitions are not limited to application methods, you can define specific
system methods as custom requests.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
177
Types of requests
Request
A request is a call made to a component that performs a service. For example, a
call to execute a SQL statement through a JDBC driver or a data source. The
following list provides some of the typical J2EE requests that are interesting to
monitor, they are all standard J2EE requests that are monitored by the Data
Collector, with no extra custom definitions required:
v Invoking a Servlet through the doGet() or doPost() methods
v EJB create() and other business methods
v JDBC API invocations like getConnection() or executeQuery()
v JMS operations to send and receive messages
v JNDI operations like lookup() used to find objects stored in the registry
v JCA resource adapter operations like getManagedConnection()
Edge request
The outermost request that needs to be monitored is called an edge request. This
involves a request that enters the application server from an outside client, for
example invoking a Servlet/JSP or a call to an EJB business method through the
Object Request Brokers (ORB). However, sometimes this request might not be of
interest as it might be a generic call like when Apache Struts applications are
involved. In such cases, a custom request might be defined to act as an edge
request. In ITCAM for Application Diagnostics, edge requests are tracked starting
at L1 monitoring level.
Nested request
A request that is invoked within another request is called a nested request. For
example, a JDBC call like getConnection() invoked from within an EJB business
method is a nested request. In ITCAM for Application Diagnostics, nested requests
are tracked starting at L2 monitoring level.
Custom request
Custom requests are defined for application-specific operations that do not fall
under the normal pre-defined J2EE operations. A custom request defines a
user-specified class and method as the start and end point of a request. If it is
enclosed in another request like a Servlet or EJB request, then it becomes a custom
nested request.
Creating custom requests
To create a custom request, complete the following steps:
1. Edit the DC_home/runtime/app_server_version.node_name.server_name/custom/
toolkit_custom.properties file and uncomment the following line:
am.camtoolkit.gpe.customxml.custom=/opt/IBM/itcam/WebSphere/DC/itcamdc
/etc/custom_requests.xml
You can specify a different location and file name.
178
ITCAM for Application Diagnostics: User Guide
Note: If the custom_request.xml file resides in the DC_home/runtime/
app_server_version.node_name.server_home/custom/ directory, then you can
simply specify the simple file name, without having to specify the fully
qualified path.
2. Create or edit the custom_requests.xml - it is typically easier to make a copy of
the file and edit it to add the custom request definitions. The following
example shows an XML specification for a custom request:
<gpe>
<bci>
<customEdgeRequests>
<edgeRequest>
<requestName>MonteCarlo</requestName>
<Matches>com.myco.investment.modeler.Simulator</Matches>
<type>application</type>
<methodName>executeMonteCarlo</methodName>
</edgeRequest>
</customEdgeRequests>
</bci>
</gpe>
The following table explains the XML elements in the custom_requests.xml file.
Table 5. XML elements in custom_requests.xml
Tag Name
Description
edgeRequest
Identifies one or more application methods that are to be monitored for
custom request processing. By modifying the requestName, Matches, type,
and methodName tags within the edgeRequest tag, you can customize the
selection. Each edgeRequest tag must contain exactly one methodName tag,
and one or more Matches tags. Multiple edgeRequest tags can be specified.
requestName
Defines a unique name for this request. The request name appears in the
L1 or L2 trace entry that is produced when one of the methods identified
by this custom request runs.
Matches
Identifies a class or classes that contain the methods that are to be defined
as custom requests. Multiple Matches tags can be present within a single
edgeRequest tag.
type
Indicates whether the classes specified are loaded by system or application
class loader. If the classes are present within an application EAR file, then
the type is “application”. However, in rare cases, the classes might be
present in JAR files specified in ws.ext.dir, system classpath or even in
bootstrap classpath. In such cases the type is “system”.
methodName
Identifies the names of the methods within one of the classes identified by
the Matches tag that are to be monitored for custom request processing.
One methodName tag can be specified in each edgeRequest tag.
The Matches and the methodName tags can include wildcard characters. The
following list is a summary of the wildcard functionality:
v Asterisk (*) stands for zero or more occurrences of any character when used
by itself. When embedded within a sequence of characters, for example,
java.*.String, it matches zero or more occurrences of any character except the
package separator (.).
v Two periods (..) can be used to specify all sub-packages, for example,
java..String matches java.lang.String. It matches any sequence of characters
that starts and ends with the package separator (.).
3. After defining the custom requests, the application server JVM needs to be
recycled for them to take effect.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
179
Making a custom request invoke an edge request
If the class and method defined in a custom request definition are invoked from
within another request, then the custom request becomes a nested request. It is
necessary to turn on the L2 monitoring to view these requests in the ITCAM MSVE
console.
For example, in Model-View-Controller(MVC) architectures, the controller receives
all the requests from the clients. Based on the content of the request, it then
redirects to the appropriate model. A well-known implementation of the MVC
architecture is the Apache Struts framework that is widely used in the J2EE
applications.
In Apache Struts, the controller is the ActionServlet and it receives all the requests.
The ActionServlet interprets the URL and based on the Apache Struts configuration
files, it gives the handling to one of the Action classes written by the user. When
monitoring Apache Struts applications, the user is interested in making these
Action classes the edge request instead of the ActionServlet which receives all the
requests so that different types of URLs used by the application can be tracked.
This can be done by defining each of the Action classes as a custom request.
However, since the ActionServlet is invoked first, these action classes are inside an
already created edge request and hence can only be tracked as nested requests.
To make the Action classes an edge request, it in necessary to prevent the Apache
Struts ActionServlet from creating the edge request. This is done by preventing the
normal Struts action servlet from being considered an edge request by the Data
Collector, by excluding the action servlet class from instrumentation.
Excluding classes from instrumentation
Complete the following steps:
1. Edit the configuration file DC_home/runtime/
app_server_version.node_name.server_name/custom/
toolkit_custom.properties to add the following new property:
am.camtoolkit.gpe.customxml.exclude=excludes.xml
2. Create the file excludes.xml in the same custom directory with the following
content:
<gpe>
<bci>
<classExcludes>
<exclude>org.apache.struts.action.ActionServlet</exclude>
<exclude>com.company.package.*</exclude>
</classExcludes>
</bci>
</gpe>
3. Add as many classes as needed.
4. Restart the application server.
5. To verify that the class has been excluded, look in toolkit.xml. It appears as
follows:
<classExcludes>
<include>*</include>
<include>org.eclipse.osgi.framework.adaptor.core.*</include>
<exclude>com.company.class</exclude>
<exclude>com.company.package.*</exclude>
<exclude>com.sun.net.ssl.internal.ssl.JSA_RSAKeyFactory</exclude>
<exclude>COM.rsa.jsafe*</exclude>
<exclude>org.eclipse.osgi.*</exclude>
</classExcludes>
180
ITCAM for Application Diagnostics: User Guide
Note: The toolkit.xml file contains runtime settings and it is refreshed every
time the application server is restarted
Viewing custom requests
Viewing recent custom edge request
1. From the top navigation, select Problem Determination - > Server Activity
Display.
2. Select the Recent Requests tab. Custom edge requests are identified in the
ThreadType field.
Viewing Active Custom Requests and Nested Custom Requests
1. From the top navigation, select Problem Determination - > Server Activity
Display.
2. Select the Active Requests tab. Custom edge requests are identified in the Last
Know Action field.
3. To view nested custom requests, click the edge request link name and select
Method/Component Trace.
4. In the Complete Flow View, details of the nested custom request are displayed.
Viewing custom requests in reports
Custom requests can be seen in the following reports:
v Custom edge requests are displayed in the Decomposition report, in the
Decomposition Data Table section.
v Nested custom requests are displayed in the Trace report in the Nesting
Summary tab, see “Viewing the Nesting Summary” on page 192
Composite requests
Use the Composite Request features in MSVE to monitor transactions that use
resources on more than one server.
The Composite Request features help you to:
v Determine if the reason a top-level request is hanging is its use of resources on a
different application server.
v Identify the origin (the application server and top-level request) that invoked a
hanging request.
v Discover the inter-application architecture of complex workflows.
There are a number of areas of MSVE that enable you to locate, view, and analyze
composite requests.
Table 6. Composite Request functionality
Area of functionality
Description of functionality
Server Activity Display
View active requests/transactions on a
specific server
In-Flight Request Search
Search for active requests/transactions on all
servers, a group of servers, or a specific
server
Performance Analysis and Reporting
Locate completed requests/transactions
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
181
Table 6. Composite Request functionality (continued)
Area of functionality
Description of functionality
Composite Method Trace
Display the method traces of all
requests/transactions in the composite
request
Composite Stack Trace
Display the stack traces of all servers
involved in the composite request that are
still actively processing the
request/transaction
Each of these features produces a list of requests/transactions which might
participate in a composite request. The presence of the composite request icon
indicates that a request/transaction participates in a composite request:
User Scenarios
Scenario 1: Discovering application architecture
Your manager asks you to provide an example of a complete transaction of an
airline reservation application. This involves a Web-based Java application, a CICS
credit card processing application, a CICS ticket reservation application, and a
frequent-flyer account, which is also a CICS system.
You look in Performance Analysis and Reporting for examples of the airline
reservation application, some of which have the composite request indicator.
Clicking the indicator brings you to the composite request view of the Method
Trace, which lets you navigate among these requests, so you can see which
application calls which one, and by what mechanism (MQ, CTG, or DPL). You can
e-mail a PDF of each request involved in the composite transaction to your
manager.
The scope of composite requests
To understand the scope of what ITCAM for Application Diagnostics can monitor,
it is important to understand two terms: managed space and composite request
space.
v Managed space is the entire scope of what ITCAM for Application Diagnostics
can monitor. Since ITCAM for Application Diagnostics can monitor servers and
application servers, along with applications and J2EE components like EJB, the
managed space has many dimensions.
v Composite request space is a subset of the managed space. Composite requests
are requests that conform to an Enterprise Application Integration (EAI)
architecture.
Managed space
The basic model of ITCAM for Application Diagnostics is to have a single
Managing Server and many Data Collectors. The Data Collectors are dynamically
controlled through the Managing Server. The Data Collectors deliver their collected
data to the Managing Server.
The Managing Server is the heart and brain of ITCAM for Application Diagnostics.
It is the entity to which each of the many Data Collectors communicate, and
provides the ITCAM for Application Diagnostics User Interface.
182
ITCAM for Application Diagnostics: User Guide
The Data Collectors are the eyes and ears of ITCAM for Application Diagnostics.
For each Application Server being monitored, a Data Collector is deployed on the
computer hosting the Application Server. (If a server has two application servers,
then you must configure two Data Collectors on the server in order to monitor
both application servers.)
The following table describes what is in the managed space:
Table 7. Components of the managed space
Component
Description
Servers
Any server on which a Data Collector is
installed is in the managed space. For z/OS
systems, a server is considered to be
equivalent to an LPAR.
Application Servers
Any application server running in a JVM in
which a Data Collector is configured is in
the managed space. CICS and IMS regions
are considered to be application servers.
The architecture of WebSphere running on
z/OS consists of a single application server
definition with a control region and one or
more servant regions. The definition and the
regions are called an application server
instance. What ITCAM for Application
Diagnostics considers to be the application
server depends on the context. In a few
cases, the application server is either the
entire application server instance (as in the
case of MOD schedules), but in most cases,
the application server is an individual
application servant region.
Resources
ITCAM for Application Diagnostics monitors
common resources that are made available
through the application server and the J2EE
APIs, such as EJB, JMS, JNDI, JDBC, and
JCA. If an application server is in the
managed space, then the resources it
provides are also in the managed space.
Application
ITCAM for Application Diagnostics supports
monitoring of any application which is
served by an application server. If the
application server is in the managed space,
then the applications it serves is in the
managed space. As a corollary, standalone
applications, which are not served through
an application server, are not in the
managed space.
Composite request space
Although the managed space includes servers, application servers, requests, and
resources, the composite request space includes only a subset of the requests in the
managed space.
In order to define the composite request space and understand how requests
interact, it is important to understand EAI architecture.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
183
EAI is the term used to describe the integration of the computer applications in an
enterprise to maximize their utility throughout the enterprise. Typically, an
enterprise has earlier single purpose applications and databases and wants to
continue to use them while adding or migrating to a new set of applications that
use the Internet, e-commerce, extranet, and other new technologies. EAI might
involve developing a new total view of an the applications in an enterprise, seeing
how existing applications fit into the new view, and then devising ways to
efficiently reuse what exists while adding new applications and data. From the
J2EE perspective, this means that an initial request, served by a J2EE application
server might invoke a resource on an earlier single purpose system through the
JCA API.
When describing EAI transactions, the name used for the initial J2EE request is the
home request, and the server on which the transaction occurs is called the home
server. The transaction on the earlier single purpose system is called a participating
request, and the server is called a participating server. There might be more than one
participating request if the earlier single purpose application invokes resources on
other single purpose applications.
In ITCAM for Application Diagnostics operations, both the home request and the
participating requests are displayed. However, without the composite request
enhancement, these requests appear independently, and there is no explicit
indication that they are part of the same transaction. Not only does the composite
request enhancement make this relationship explicit, it also provides diagnostic
tools, like Method Trace and Stack Trace, that you can apply across all requests in
the composite request.
Composite requests involving CICS and IMS systems
If a participating server is a CICS server, and a CICS data collector has been
installed, then this system is in the managed space. Similarly, if a participating
server system is IMS, and an IMS data collector has been installed, then the system
is in the managed space. The J2EE application server is in the managed space if a
data collector is installed.
Monitoring CICS transactions
The CICS data collector monitors all program invocations on the managed CICS
region, whether they come through a dumb terminal, Distributed Program Link
(DPL), EXEC CICS START, or through the CICS Transaction Gateway (CTG).
Furthermore, for transactions invoked through CTG, it does not matter how CTG
was accessed, which can include various interfaces. However, ITCAM for
Application Diagnostics does not track all such transactions as composite requests.
CICS and IMS transactions in composite requests
Even though all transactions on a CICS or IMS region in the managed space
appear in ITCAM for Application Diagnostics, they are not necessarily treated as
part of a composite request, even if they invoke programs on other regions.
A transaction on a CICS or IMS region is part of a composite request if it meets the
following criteria:
v The CICS or IMS region is in the managed space.
v The Home Server is in the managed space.
v The application server that serves the Home Request is a J2EE application server,
and is in the managed space.
184
ITCAM for Application Diagnostics: User Guide
v For CICS: The application on the Home Server uses ECI to access CTG. (This
includes applications that use CCI as their JCA resource adapter, since CCI uses
ECI.)
v The ECI invocation is synchronous.
v The COMMAREA of the CICS program invocation has at least 11 bytes of
available space.
v For IMS: The application on the Home Server uses IMS Connect for Java (IC4J)
to access IMS connect.
If any of these criteria are not met for an EAI request, then ITCAM for Application
Diagnostics does not identify the request as being part of a composite request.
However, the core ITCAM for Application Diagnostics features are still available
for whatever parts of the transaction are in the managed space.
For example, if an application in C++ invokes a CICS program on a CICS region in
the managed space through CTG, the CICS program is displayed as a request
within ITCAM for Application Diagnostics, but the C++ application request is not
displayed in ITCAM for Application Diagnostics. The reason is,ITCAM for
Application Diagnostics does not monitor C++ applications. In this case, ITCAM
for Application Diagnostics does not identify the CICS transaction as part of a
composite request.
Likewise, if a Java application uses EPI to access CTG, ITCAM for Application
Diagnostics does not track the EAI as a composite request, even if the application
is in the managed space. In this case, the requests on both the J2EE application
server and in the CICS region are displayed in ITCAM for Application Diagnostics,
but are displayed independently, and are not identified as a composite request.
The final condition, based on the application's use of the COMMAREA, is due to
the methodology of tracking composite requests, which involves use of the
COMMAREA. In practice, it is rare that program invocations use so much of the
COMMAREA that there is not room for this correlation information. In these
exceptional cases, ITCAM for Application Diagnostics does not attempt to identify
the EAI as a composite request, and the individual requests are displayed in
ITCAM for Application Diagnostics as independent requests.
Multiple hops
Composite requests are not restricted to single-hop transactions.
In particular, composite requests include cases where CICS programs make DPL
calls to other CICS Regions. When such a call is made, we say that the depth of
the composite request increases. ITCAM for Application Diagnostics can track
requests with no limit to the depth of transaction "hops."
For IMS, any events with the same message tag from any IMS region in an IMS
Network appear as a single transaction.
In addition, composite requests can include up to 100 participating requests made
directly by each home or participating request. Although composite requests can
include an unlimited depth of "hops," composite requests place a limit on the
number of calls that can be tacked by any single request.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
185
Configuring data collectors that use WebSphere MQ
If you are monitoring composite requests for applications that use WebSphere MQ
as a mechanism to bridge J2EE and CICS or IMS, then you must configure each
participating data collector to monitor WebSphere MQ.
Note: These instructions assume that your data collectors have already been
configured.
To enable WebSphere MQ monitoring on a data collector within the Application
Monitor:
1. Open the Application Monitor.
2. Click the Administration tab on the top navigation.
3. Select Server Management > Data Collector Configuration.
4. Click the Configuration Library link in the left navigation.
5. Locate the application server in the Associated Server column of the
Configuration Library table and click the Modify icon for that row.
Note: You cannot modify ITCAM for Application Diagnostics supplied default
configurations. You can only modify configurations you have created.
6. Select Enable MQ.
7. Enter the queues you want to monitor in the Exclude (Classname) and Exclude
Override (Classname).
8. Click the Save button.
Locate, view, and analyze composite requests
There are a number of areas of ITCAM for Application Diagnostics' functionality
that enable you to locate, view, and analyze composite requests.
Table 8. Composite Request functionality
Area of functionality
Description of functionality
Server Activity Display
View active requests/transactions on a
specific server
In-Flight Request Search
Search for active requests/transactions on all
servers, a group of servers, or a specific
server
Performance Analysis and Reporting
Locate completed requests/transactions
Composite Method Trace
Display the method traces of all
requests/transactions in the composite
request
Composite Stack Trace
Display the stack traces of all servers
involved in the composite request that are
still actively processing the
request/transaction
Each of these features produces a list of requests/transactions which might
participate in a composite request. The presence of the composite request icon
indicates that a request/transaction participates in a composite request:
186
ITCAM for Application Diagnostics: User Guide
In-Flight Request Search
To search for in-flight requests/transactions that participate in composite requests,
use the In-Flight Request Search. See “In-flight request search” on page 112
The results will display: Server Name, Client Request/Transaction, Start Date Time,
Thread ID, and Total Resident Time. In addition, ITCAM for Application
Diagnostics identifies requests/transactions that are part of a composite request by
displaying the composite request icon.
Server Activity Display
To search a server for resident requests/transactions that participate in composite
requests, use the Server Activity Display. See “Server Activity Display” on page 114
The results display: Client Requests, Client Requests Start, Thread ID, Resident
Time, Accumulated CPU, Idle Time, Thread Status, Last Known Class, Last Known
Method, Last Known Action, and User ID. In addition, ITCAM for Application
Diagnostics identifies those requests/transactions that are part of a composite
request by displaying the composite request icon.
Performance Analysis and Reporting
To search for completed requests/transactions that participated in composite
requests, use Performance Analysis and Reporting. Start by creating a Trend
Report, then drill down to a Decomposition Report, and then to a Detail report in
order to find individual requests/transactions that are part of composite requests.
Note: Performance Analysis and Reporting displays the Composite Request
Indicator only for home requests, and not for the other participating
requests/transactions. For details on participating requests and home requests, see
“The scope of composite requests” on page 182
The following procedure describes how to locate composite requests using
Performance Analysis and Reporting.
To locate composite requests using the Performance Analysis and Reporting:
1. View a Request/Transaction Analysis Trend Report for servers that you believe
might have served home requests of composite requests. Choose appropriate
Report Filtering Options and Date Range Settings.
A Trend Report is displayed.
2. Choose an appropriate Decomposition option (Additional Detail selection) and
time period.
A Decomposition Report is displayed.
3. View the requests/transactions that comprise the Decomposition Report by
selecting an appropriate segment of the Decomposition Report.
A Detail Report is displayed.
The resulting Detail Report displays a list of the requests/transactions included in
the segment of the Decomposition Report you selected.
The results display: Request/Transaction Name, Request/Transaction Type,
Response Time, CPU Time, Server Name, Timestamp, and Number of Records. In
addition, ITCAM for Application Diagnostics identifies that a request was a home
request of a composite request by displaying the composite request icon next to its
Request/Transaction Name.
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
187
Viewing composite requests
To access the composite request details of requests/transactions, click the
Composite Request Indicator for that request/transaction.
Composite requests have the following features:
v Composite Method Trace: Displays the interrelated method traces across all
requests involved in the composite request.
v Composite Stack Trace: Displays a continuous stack trace of all servers involved
in the composite request which are still actively processing the
request/transaction.
The availability of method-level data is contingent upon the configuration of the
data collectors; they must be at L3 monitoring level in order to provide full
method-level data. To provide Nested Request data, the Data Collector needs to at
L2 monitoring level.
Since the monitoring levels of data collectors are independent, it is possible that
method-level data is available for some, but not all, servers participating in a
composite request. The Composite Method Trace presents all data it has, which
means that the level of data presented from server to server might vary.
Authorization and composite requests
Authorization is enforced in ITCAM for Application Diagnostics in two ways: by
feature and by server. Feature-based authorization limits access to top-level
features based on the role assigned to a user. Assuming that a user has access to a
feature, the server-based authorization might further limit access to data about
servers based on which group a server is assigned to, and which groups the user
has authority to view.
Since composite requests involve more than one server, the effects of server-based
authorization play out in the following scenario.
A composite request's home request is on server A (which is in group A) and
invokes a participating request on server B (which is in group B). There are two
users who need to investigate this composite request: User A has access to servers
in group A but not group B, and user B has access to servers in group B but not
group A.
Assuming that each user uses In-Flight Request Search to locate the requests, the
results for each user will differ, since the In-Flight Request Search limits results to
those requests executing on servers in groups the user has access to. This means
that user A will see only request A and user B will see only request B.
In both cases, the Composite Request Indicator will appear next to the request, and
will link to a similar Composite Request Detail page. However, the contents of the
Composite Request Detail page will be different for each user.
Both users will see the complete composite request, including the Home Request
on server A and the Participating Request on server B. However, the users will not
have access to the Request Detail pages of all requests: User A will have access to
the Home Request on server A (the request name will be linked), but not to the
Participating Request on server B (the request name will not be linked). User B will
not have access to the Home Request on server A (the request name will not be
linked) but will have access to the Participating Request on server B (the request
name will be linked).
188
ITCAM for Application Diagnostics: User Guide
Viewing a Composite Method Trace - SAD
About this task
The Composite Method Trace page displays the method flow of the composite
transaction, including the method traces of each individual request participating in
the composite transaction.
To view a Composite Method Trace:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display selection page opens.
2. Select a group from the group list box.
3. Select a server from the server list box. The Server Activity Display page opens.
The Server Activity Display page opens.
4. Click the composite transaction indicator next to the request that you want to
view. The Composite Request Detail for that composite transaction opens.
5. On the left navigation pane, click Composite Method Trace. The Composite
Method Trace page opens.
For CICS, the line numbers and response codes have been added to the
Composite Method Trace. The return code is from the method call and the line
number is of the CICS method call. You will find their information in the Event
Data field on the Flow View tab.
Results
Related topics
Canceling a request
Changing a thread's priority
Viewing a Composite Stack Trace - SAD
About this task
The Composite Stack Trace page displays the stack traces of each server involved
in the composite transactions that are actively processing their request/transaction.
Note: The Composite Stack Trace is primarily useful for debugging composite
transactions that are hanging, since there will be no stack trace data available if a
composite transaction has completed by the time you access it.
To view a Composite Stack Trace:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display selection page opens.
2. Select a group from the group list box.
3. Select a server from the server list box.
4. Click the composite transaction indicator next to the request that you want to
view. The Composite Request Detail for that composite transaction opens.
5. On the left navigation pane, click Composite Stack Trace. The Composite Stack
Trace page opens and displays the stack traces of the servers that are actively
executing participating requests.
Related topics
Canceling a request
Changing a thread's priority
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
189
Viewing a Composite Request Detail - SAD
About this task
The Composite Request Detail page summarizes a composite transaction, in terms
of the individual requests that participate in it.
To view Composite Request Detail:
1. From the top navigation, click Problem Determination > Server Activity
Display. The Server Activity Display selection page opens.
2. Select a group from the group list box.
3. Select a server from the server list box.
4. Click the composite transaction indicator next to the request that you want to
view. The Composite Request Detail for that composite transaction opens.
5. Click the Request Name's link to drill down and view the detailed information.
Related topics
Canceling a request
Changing a thread's priority
Viewing a Composite Request Detail - In-flight Request Search
About this task
The Composite Request Detail page summarizes a composite transaction, in terms
of the individual requests that participate in it.
To view Composite Request Detail:
1. From the top navigation, click Problem Determination > In-flight Request
Search. The In-flight Request Search page opens displaying active requests
participated in composite transactions that are identified by the composite
transaction indicator.
2. Click the composite transaction indicator next to the request that you want to
view its Composite Request Detail information. The Composite Request Detail
for that composite transaction opens.
3. Click the Request Name's link to drill down and view the detailed information.
Related topics
Canceling a request
Changing a thread's priority
Viewing a Composite Stack Trace - In-flight Request Search
About this task
The Composite Stack Trace page displays the stack traces of each server involved
in the composite transaction that are actively processing their request/transaction.
Note: The Composite Stack Trace is primarily useful for debugging composite
transactions that are hanging, since there will be no stack trace data available if a
composite transaction has completed by the time you access it.
To view a Composite Stack Trace:
190
ITCAM for Application Diagnostics: User Guide
1. From the top navigation, click Problem Determination > In-Flight Request
Search. The In-Flight Request Search page opens displaying active
requests/transactions.
2. To view the Composite Method Trace for a request/transaction that is
participating in a composite transaction, click that request/transaction's
composite transaction indicator. The Composite Method Trace page for that
composite transaction opens.
3. Click Composite Stack Trace in the left navigation pane.
4. The Composite Stack Trace page opens and displays the stack traces of the
servers that are actively executing participating requests/transactions.
Related topics
Canceling a request
Changing a thread's priority
Viewing a Composite Method Trace - In-flight Request Search
About this task
The Composite Method Trace page displays the method flow of the composite
transaction, including the method traces of each individual request participating in
the composite transaction.
To view a Composite Method Trace:
1. From the top navigation, click Problem Determination > In-flight Request
Search. The In-flight Request Search page opens displaying active requests
participated in composite transactions that are identified by the composite
transaction indicator.
2. Click the composite transaction indicator next to the request that you want to
view its Composite Request Detail information. The Composite Request Detail
for that composite transaction opens.
3. On the left navigation pane, click Composite Method Trace. The Composite
Method Trace page opens.
Related topics
Canceling a request
Changing a thread's priority
Viewing a Composite Request Detail - PAR
About this task
The Composite Request Detail page summarizes a composite transaction, in terms
of the individual requests that participate in it.
To view Composite Request Detail:
1. From the top navigation, click Performance Analysis> Create Application
Reports > select an application report type. For more information see
“Performance analysis and reporting” on page 155. After creating the report,
click View Report and the Trend report will open.
2. Click the data in the graph that you are interested in viewing more information
on. The Decomposition report opens.
3. Click the data in the Decomposition report that you want more information
about. The Request Report Detail opens.
Related topics
Viewing the Detail report
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
191
Canceling a request
Changing a thread's priority
Viewing a Composite Method Trace - PAR
About this task
The Composite Method Trace page displays the method flow of the composite
transaction, including the method traces of each individual request participating in
the composite transaction.
To view a Composite Method Trace:
1. From the top navigation, click Performance Analysis> Create Application
Reports > select an application report type. For more information see
“Performance analysis and reporting” on page 155. After creating the report,
click View Report and the Trend report will open.
2. Click the data in the graph that you are interested in viewing more information
on. The Decomposition report opens.
3. Click the data in the Decomposition report that you want more information
about. The Request Report Detail opens.
4. Click the item in the detail of the report that you need more information on.
The Trace report opens.
Related topics
Viewing the nesting summary
Viewing the method/component tract - depth drilldown detail
Viewing the method/component tract - depth drilldown report
Viewing a method/component trace - flow view
Viewing the Nesting Summary
About this task
The Nesting Summary can help you to quickly identify problems with external
resources used by a request.
To view the Nesting Summary page:
1. From the top navigation, click Performance Analysis > Create Application
Reports. Select an application report type. For more information see
“Performance analysis and reporting” on page 155.
2. Click the data in the graph that you are interested in viewing more information
about. The Decomposition report opens.
3. Click the data in the Decomposition report that you want more information
about. The Request Report Detail opens.
4. Click the item in the detail of the report that you need more information about
The Trace Report opens.
5. Click the Nesting Summary tab. The Nesting Summary page opens. You need
to set the monitoring level of the data collector to at least L2 or L3 to capture
data for the Nesting Summary.
Related topics
Defining a Capacity Analysis report
Defining a Request/Transaction Analysis report
Defining Top reports
192
ITCAM for Application Diagnostics: User Guide
Viewing a Method/Component Trace - Depth Drilldown detail
About this task
Navigate through the trace one level at a time using the Depth Drilldown detail.
To view the Depth Drilldown detail of a method trace:
1. From the top navigation, click Performance Analysis > Create Application
Reports. Select an application report type. For more information, see
“Performance analysis and reporting” on page 155.
2. Click the data in the graph that you are interested in viewing more
information about. The Decomposition report opens.
3. Click the data in the Decomposition report that you want more information
about. The Request Report Detail opens.
4. Click the item in the detail of the report that you need more information about
The Trace Report opens.
5. Click the Drilldown View tab. The Drilldown View page opens and displays
the Depth Drilldown Detail.
Results
To view the Depth Drilldown report, choose Depth Report from the list box. See
“Viewing a Method/Component Trace - Depth Drilldown report.”
Related topics
Canceling a request
Changing a thread's priority
Viewing a Method/Component Trace - Depth Drilldown report
About this task
Use the Depth Drilldown report to quickly identify problems with categories of
nested request components used by a method and its children, by comparing the
number of calls, Average Response Time, and Average CPU Time.
To view the Depth Drilldown report of a method trace:
1. From the top navigation, click Performance Analysis > Create Application
Reports. Select an application report type. For more information see
“Performance analysis and reporting” on page 155.
2. Click the data in the graph that you are interested in viewing more
information about. The Decomposition report opens.
3. Click the data in the Decomposition report that you want more information
about. The Request Report Detail opens.
4. Click the item in the detail of the report that you need more information about
The Trace Report opens.
5. Click the Drilldown View tab. The Drilldown View page opens to the Depth
Drilldown Detail.
6. Choose Depth Report from the list box. The Depth Drilldown Report opens.
Related topics
Canceling a request
Changing a thread's priority
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
193
Audit trails
Trace user actions.
Audit trails provide a means for tracing user actions in the system. This helps with
both accountability and troubleshooting.
User Scenarios
Scenario 1: Verifying high server response time
Upon returning from vacation, you see that response time is higher than usual for
one of the servers in group ABC. You notice from the Heap Dump Management
page that the server is performing heap dumps regularly which is causing the
slowness in the response time. You enter the audit trail to find out who scheduled
the heap dump. You contact that person and learn that the heap dumps are
scheduled for troubleshooting a suspected memory leak in the application.
Scenario 2: Verifying MOD level change
In your role as a production support engineer you observe that the MOD level of a
data collector in the production environment has been set to L2 instead of the
expected MOD L1. You ask the Administrator to search the audit trail and find out
who changed the MOD level, and find that an application support engineer is
troubleshooting a production issue in the application.
Accessing the user audit trail
About this task
The user audit trail is a text file that contains a record of user activity, including
Date, Time, User Name for Login, Failed Login, Log Out, Time Out,
Authentication, and Account Status changes.
To open the user audit trail:
1. Depending on your platform, navigate to the logs directory where you
installed the Managing Server, for example, /var/ibm/tivoli/common/CYN/
logs.
2. In a text editor appropriate to your platform, open the audit-ms-Compound.log
file.
Request Mapper
Purpose
Use the Request Mapper to customize how requests are named within the
Application Monitor. Also, use the Request Mapper to display user names
associated with requests.
Usage Overview
This feature helps you:
v Distinguish among requests that otherwise would have the same request name.
v Aggregate requests which otherwise would have distinct request names.
v Identify the User IDs under which requests run.
194
ITCAM for Application Diagnostics: User Guide
User Scenarios
Scenario 1: Aggregating Across Distinct Original Request String (ORS)
The application you are monitoring uses a distinct URI to represent each specific
application function, such as log in, check out, or log out. You wish to analyze all
these requests as a single application. Use the Request Mapper to populate the
Request Name field with a common application name.
Scenario 2: Differentiating a Uniform ORS
You are monitoring an application that uses session variables to represent the
underlying function, while using the same request name throughout these different
interactions. You want to compare the performance of different application
functions, such as log in, check out, or log out, so you use the Request Mapper to
assign each function a distinct request name.
Note: This feature is not available for IMS.
Data used by the Request Mapper
Request name
The Request Name enables the user to assign alternate request identifiers that are
more meaningful and appropriate to the chosen programming model of the
application.
The Request Name is provided because the Request String is just one way of
identifying requests. There is data that is within the request that is not represented
by the Request String. Furthermore, requests can be rather cryptic, so mapping
them to something more immediately recognizable or understandable is useful.
For example, a Web request can be mapped by:
v URI: /account/login
v Servlet Class Name: com.cyanea.web.AccountServlet
v Struts Class Name:
http://www.cyanea.com/account/execute/login.do -->
com.cyanea.web.account.LoginAction
v Custom Naming Scheme: account.login
When the installed Request Mapper is invoked, data is passed into this plug-in
class to assist the custom code developer to make a decision. This includes the
Request Object and the Session Object in the case of a URL based request.
Application Name
The Application Name enables you to assign request identifiers that classify their
requests into different applications. It is a means to aggregate different ORS into an
application label.
The Application Name enables you to analyze their historical data from an
application perspective.
For example, requests can be mapped to the following names:
v Account Management
v Web Trading
v Order Management
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
195
User IDs
The Application Monitor has the ability to capture, display, and store the user ID
of a request that comes into the application server. By default, the user ID is
captured by calling the following method:
javax.servlet.http.HttpServletRequest.getRemoteUser()
If your application stores user IDs in the session, configuration will be required.
User IDs are defined as Web-side identifiers of who initiated the
transaction/request.
To capture the user ID from the session, you need to enable the data gathering
from the session, and specify the attribute in the session that contains the user ID.
To enable the data gathering from the session, update the data collector properties
as follows:
com.cyanea.mapper.http.userid.source=session
To capture the attribute called account name from the session, update the data
collector properties as follows:
com.cyanea.mapper.http.userid.attributename=accountname
Default request mapping behavior
From the application server perspective, there are two major types of requests: JSP
and Servlet. These calls come either from a Web server, or from an application
server other than itself.
We call this request, generally expressed in the form of a string, the ORS. The ORS
is composed of the URI plus the query string.
While a unique ORS can be used to represent a specific application function such
as log in, check out, and log out, this might not always be the case. Other styles of
application design utilize different programming techniques to represent the
underlying function, while still maintaining a simple, uniform ORS throughout a
series of interactions. When monitoring applications that use such a design, you
can use the Request Mapper to distinguish among these different interactions that
use the same ORS.
In addition, when performing workload characterization and understanding
resource consumption, an analyst might sometimes find that it is neither possible
nor effective to break down consumption simply by ORS, especially if there are too
many of them. Aggregation of consumptions based on classification of ORS is more
desirable.
The Request Mapper functionality is designed to resolve these types of problems.
When an application server receives a request (ORS), the Request Mapper will
enable the ORS to be rewritten into two other strings before it is passed on to
ITCAM for Application Diagnostics:
v Request Name
v Application Name
If no request mapper is used, the Application Monitor will map the incoming ORS
onto a Request Name and an Application Name using the following rule:
Request Name
= ORS without the host nameApplication Name
= URI of ORS
196
ITCAM for Application Diagnostics: User Guide
In-flight Request Search is conducted on the Request Name. Server Activity
Display uses Request Name for the display. Performance Analysis and Reporting
performs decomposition by Application Name.
Configuring a Request Mapper
Request Mapper is highly sensitive to performance since it is frequently invoked. A
poor-performing Request Mapper can have an adverse effect on the overall
performance of the application server in terms of Servlet response time as well as
CPU costs.
WebSphere 6.1 uses a different class loading mechanism than WebSphere 6.0 or
WebSphere 5.1.1, therefore complete the following steps to configure the Request
Mapper for WebSphere 6.1:
1. Stop the WebSphere server.
2. To configure a Request Mapper, complete the following steps:
a. Assuming the requestmapper classes are packaged in requestmapper.jar,
create the Request Mapper class plugins and package them into the jar file.
b. In the datacollector_custom.properties file located in the
DC_home/runtime/app_server_version.node_name.server_name/custom/
directory, set the am.requestmapper property as follows:
am.requestmapper= <fully qualified requestmapper class name>
where fully qualified requestmapper class name is the Request Mapper class
that implements the ITCAM Request Mapper interface and is packaged in
requestmapper.jar.
c. Put the library requestmapper.jar in DC_home/itcamdc/lib/ext
3. (Optional) The following steps are optional, they provide an example of how to
configure a Request Mapper and avoid mixing the Request Mapper specific
properties with other JVM system properties. This is done by creating a
separate Request Mapper properties file and including all the Request Mapper
properties in this file. In this way, if you need to add additional Request
Mapper properties, you can do so without exposing them to other code either
in the data collector or in the application server. The following steps provide an
example of this optional approach:
a. Create a property file called requestmapper.properties and put all the
Request Mapper specific properties in this file. Put the
requestmapper.properties file in DC_home/runtime/DC_specific dir.
b. In the datacollector_custom.properties file located in the
DC_home/runtime/app_server_version.node_name.server_name/custom/
directory, set the customer.reqestmapper.file property as follows:
customer.requestmapper.file=
DC_home/runtime/DC_specific dir/requestmapper.properties
c. In the RequestMapper code, get the location of requestmapper.properties file
by doing System.getProperty("customer.requestmapper.file")
4. Restart the WebSphere server.
Java docs and an example follow:
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
197
Package com.cyanea.mapper
Table 9. Interface Summary
Interface Summary
MappedRequest
Interface used for providing the ITCAM for
Application Diagnostics system with a
Distinguishable Request String (DRS) and a
Collapsible Request String (CRS) about a
particular Servlet request.
RequestMapper
ITCAM for Application Diagnostics
recognizes JSP and Servlet requests on an
application server.
Interface mapped request
public interface MappedRequest
Interface used for providing the ITCAM for Application Diagnostics system with a
DRS and a CRS about a particular servlet request.
Table 10. Method Summary
Method Summary
java.lang.String
getCRS ( )
java.lang.String
getDRS( )
Interface Request Mapper
public interface RequestMapper
ITCAM for Application Diagnostics recognizes JSP and servlet requests on an
application server. These requests are normally identified throughout the ITCAM
for Application Diagnostics system using the URI of the request. In some
situations, such as when a Struts design paradigm is used, a particular URI will be
used to handle different types of business requests.
ITCAM for Application Diagnostics provides this interface as a mechanism for
modifying ITCAM for Application Diagnostics default behavior of using the URI to
describe the request. An implementation of this interface can be installed by
registering the classname with the Java executable as a system property.
To install, specify the system property "am.requestmapper" with the implementing
class as the value.
For example:
-Dam.requestmapper=com.cyanea.mapper.RequestMapperExample
198
ITCAM for Application Diagnostics: User Guide
Table 11. Method Summary
Method Summary
MappedRequest
mapRequest
(java.lang.String servletClassName,
javax.servlet.http.HttpServletRequest
request)
This stateless method translates a servlet
classname and a URL into a MappedRequest
object.
Sample Request Mapper - mapRequest
public MappedRequest mapRequest(
java.lang.String servletClassName,
javax.servlet.http.HttpServletRequest request)
This stateless method translates a servlet classname and a URL into a
MappedRequest object. Any RequestMapper class should attempt to execute this
method as quickly as possible, due to the fact that it lies directly in the path of the
application server thread execution.
v Parameters:
– ServletClassName - the name of the ServletClass handling this request.
– request - the HttpServletRequest object for this request.
v Returns: An instance of MappedRequest indicating the DRS and CRS to be used
by the ITCAM for Application Diagnostics system.
Request Mapper Example (1):
package com.cyanea.mapper;
public class MappedRequestExample implements MappedRequest {
private String CRS;
private String DRS;
/** Creates a new instance of MappedRequestExample */
public MappedRequestExample(String myCRS,String myDRS) {
CRS = myCRS;
DRS = myDRS;
}
public String getCRS() {
return CRS;
}
public String getDRS() {
return DRS;
}
}
Request Mapper Example (2):
package com.cyanea.mapper;
import javax.servlet.http.HttpServletRequest;
public class RequestMapperExample implements RequestMapper {
/** static MappedRequest instance for welcome page requests
*/
private static final MappedRequest welcomeRequest;
/** static MappedRequest instance for quote page requests
*/
private static final MappedRequest quoteRequest;
/** static MappedRequest instance for buy page requests
*/
private static final MappedRequest buyRequest;
/** static MappedRequest instance for sell page requests
*/
Chapter 3. ITCAM for Application Diagnostics Managing Server Visualization Engine
199
private static final MappedRequest sellRequest;
/** static MappedRequest instance for portfolio page requests
*/
private static final MappedRequest portfolioRequest;
/** static MappedRequest instance for account page requests
*/
private static final MappedRequest accountRequest;
/** static MappedRequest instance for update page requests
*/
private static final MappedRequest updateRequest;
/**
* Static class variables are used to avoid continuous object creation
* of redundant information on a per-client-request basis. An
* unsynchronized, read-only HashMap can also be used for looking up
* MappedRequest instances to gain a performance increase.
**/
static {
welcomeRequest
= new MappedRequestExample("Welcome Page","welcome");
quoteRequest
= new MappedRequestExample("quote","quote");
buyRequest
= new MappedRequestExample("trade","buy");
sellRequest
= new MappedRequestExample("trade","sell");
portfolioRequest = new MappedRequestExample("overview","portfolio");
accountRequest
= new MappedRequestExample("account","account");
updateRequest
= new MappedRequestExample("account","updateAccount");
}
/** Creates a new instance of RequestMapperExample */
public RequestMapperExample() {
}
/**
* This example checks the HttpServletRequest object for the GET or POST
* parameter "map". If the parameter "map" is not found, "action" is
* used. This "action" string, is then used to look up the corresponding
* MappedRequest object. If no MappedRequest object is found, a new
* object is created and returned. This should be avoided, as it can be
* an expensive operation.
*/
public MappedRequest mapRequest(String servletClassName,
HttpServletRequest request) {
String action = request.getParameter("map");
if ( action == null) {
action = request.getParameter("action");
if ( action == null )
return welcomeRequest;
}
/* A HashMap lookup could also be performed here instead of iterating
* a list of string comparisons. If a list of strings comparison are
* used, it is desirable to list the most common action first.
*/
if ( "quote".equals(action) )
return quoteRequest;
else if ( "buy".equals(action) )
return buyRequest;
else if( "sell".equals(action) )
return sellRequest;
else if( "portfolio".equals(action) )
return portfolioRequest;
else if( "account".equals(action) )
return accountRequest;
else if( "updateAccount".equals(action) )
return updateRequest;
else
return new MappedRequestExample(action,action);
}
}
200
ITCAM for Application Diagnostics: User Guide
Chapter 4. ITCAM Agent for WebSphere
IBM Tivoli Composite Application Manager for Application Diagnostics WebSphere Agent provides a systems-management solution for the WebSphere
Application Server Versions 6, and 7 . Using the WebSphere agent, you can
monitor multiple WebSphere application servers running on the same physical
node. Each application server must have been configured with its own ITCAM for
WebSphere Data Collector.
IBM Tivoli Composite Application Manager Agent for WebSphere is a component
of ITCAM for Application Diagnostics, Version 7.1. It is also a component of
ITCAM for Applications Version 6.2.3. If you are using ITCAM for Applications the
Managing Server (deep dive) functionality is not available; please ignore all
references to this functionality in this document.
The Tivoli Enterprise Monitoring Agent collects four types of data through the data
collector embedded in the WebSphere Application server process:
v Data for application server requests from the ITCAM for WebSphere Data
Collector
v Resource data from WebSphere Performance Monitoring Infrastructure (PMI)
v Data from WebSphere log files
v Process data from the operating system
Initiating data collection and reporting of data
Because of high overhead, some data items are not automatically collected and
reported. The collection of some data and statistics depends upon the setting of
instrumentation levels for certain attributes. If the instrumentation levels are not
set appropriately, certain information will not be collected and displayed in the
workspaces. Similarly, those attributes that collect request and application trace
data require you to complete several configuration steps. If you need to collect
these data, use one of these methods to reconfigure data collection:
v Complete configuration steps (as explained in the ITCAM for Application
Diagnostics - WebSphere Agent installation and customization guide).
v Issue Take Action commands to take specific action against your WebSphere
application server or the monitoring product using the Tivoli Enterprise Portal.
v Use Manage Tivoli Enterprise Services (as explained in the various IBM Tivoli
Monitoring installation manuals and the ITCAM for Application Diagnostics WebSphere Agent installation and customization guide).
Automatic baselining
To display application health status, ITCAM monitors request response times
(averaged over a sampling interval, by default 60 seconds) for every application.
Every top level request available in an application is monitored separately.
For every request, two thresholds are set, known as fair and bad. When at least one
average request response time for an application rises over the fair threshold, a
health warning (yellow) for this application is reported. In the same way, when at
least one average request response time rises over the bad threshold, an
application health alarm (red) is reported.
© Copyright IBM Corp. 2006, 2009
201
ITCAM also monitors the "nested" requests (for example, database calls) within
every top level request. In the event of a warning or alarm, it checks which of the
nested requests is taking more than its usual share of time. Depending on the type
of such nested requests, ITCAM shows whether the client, application, or backend
tier is the likely cause of the warning/alarm. Servlet and Portal request types are
assigned to the client tier; EJB and User (Custom) request types, to the application
tier; all other request types (JNDI, JDBC, JCA, JMS) to the backend tier.
When ITCAM starts to monitor a new application, it automatically starts a
baselining process. In this process, which normally runs for 7 days but provides
updated information every hour from the beginning, ITCAM collects statistical
data for all requests in this application. Once the data is collected, ITCAM sets the
thresholds automatically; it also records the typical share of response time for each
nested request type.
In most cases, this automatic setting is adequate. When the 7 days are past, the
alarms/warnings will correspond to real problems. There is no need to adjust
baselining settings when things are working normally. (The automatic thresholds
usually become usable earlier, after the application has been observed through its
typical load patterns). If you need to acquire thresholds, based on whatever data is
available, before the hourly automatic update, you can manually update
baselining.
However, in some situations the threshold levels can become inadequate. This
results in either too many false alarms/warnings, or in real problems going
undetected. Such situations can be broadly split into two categories:
v If some time has passed since the baselining process for an application, its
response times might have changed because of configuration alteration, database
growth, changing load patterns, and so on. In this case, you may need to run the
baselining process again. It is good practice to do it after any configuration or
infrastructure change.
v If the thresholds are incorrect immediately after the baselining process has been
completed, you may need to adjust the auto threshold settings.
As a last resort, you can also override the thresholds with fixed values. However,
do not do this unless you know a lot about the monitored application, or unless
instructed by IBM Level 3 Support.
If you need to have the thresholds set before they are updated automatically for
the first time, you can trigger a baseline update. This will immediately set the
thresholds based on the request data collected so far.
Additional information
For additional usage information about this agent, see:
202
v
v
Workspaces
Attributes
v
v
Situations
Take Action commands
ITCAM for Application Diagnostics: User Guide
About this publication
Welcome to the online help system available from inside the IBM Tivoli Composite
Application Manager for WebSphere agent product. (C) Copyright IBM®
Corporation 2006, 2009. All Rights Reserved.
For the latest version of this Help, see the ITCAM for Application Diagnostics User
Guide, here: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml
ITCAM for Application Diagnostics - WebSphere Agent workspaces
As part of the IBM Tivoli Composite Application Manager for Application
Diagnostics - WebSphere Agent product's integration with the Tivoli Enterprise
Portal, workspaces offer views of monitoring data that provide detailed current
data about the Version 6 and 7 WebSphere application servers running on your
site's Linux, UNIX, and Windows and z/OS platforms. In addition to reports and
graphs, a workspace can contain other views (that is, windows), such as a Notepad
editor session, a browser session, a telnet session, an event console, or a Take
Action view from which you can issue commands.
Several views of high-level information
Several workspaces provide high-level information to help you meet your site's
monitoring and administrative needs. These workspaces report current status and
availability for both the WebSphere administrative server and its application server
instances. They let you easily monitor the availability of your enterprise, the
WebSphere Application Server, and application server instances.
Primary and secondary workspaces
The workspaces listed in the Navigator are directly accessible and are thus termed
primary workspaces. Some of these also contain secondary workspaces, which are not
accessible directly from the Navigator. Instead you must select and display the
primary workspace, then use either a menu option or a special link icon in the
primary workspace's views to reach the secondary workspaces (sometimes called
subsidiary workspaces).
Workspaces with historical data links
Several workspaces provide secondary workspaces that display historical data. You
can specify a time span over which to collect historical data, which accumulates
and summarizes the data in the primary workspaces that generate them. (The
default setting is 15 minutes; you can modify this setting to suit your needs.) The
descriptions of the historical workspaces follow the descriptions of the primary
workspaces that generate them in the workspace helps.
Available Tivoli Enterprise Portal workspaces
For an overview of the organization of the available workspaces, see Organization
of the predefined workspaces.
Organization of the predefined workspaces
The IBM Tivoli Composite Application Manager for Application Diagnostics WebSphere Agent workspaces for the Tivoli Enterprise Portal define data displays
Chapter 4. ITCAM Agent for WebSphere
203
that appear in the Navigator's Physical view. In addition to the workspaces that
the Navigator lists, you can reach their subsidiary (that is, secondary) workspaces
from the primary workspaces (those listed in the Navigator).
Accessing the subsidiary workspaces
You can access a primary workspace's subsidiary workspaces by using one or more
of the following methods:
From the Navigator:
1.
2.
3.
4.
Select the primary workspace.
Right-click the name of the selected workspace in the Navigator.
Select Workspaces from the context menu.
Select the desired subsidiary workspace.
From the View menu:
1. Select the primary workspace.
2. In the menu bar at the top of the Tivoli Enterprise Portal, select View >
Workspaces.
3. Select the desired subsidiary workspace.
From a report:
1. Select the primary workspace.
2. If the workspace's report (which displays by default at the bottom of the
workspace) contains a link icon to the left of each row, you can either click the
icon to navigate to the default subsidiary workspace pertaining to the selected
row or right-click the icon and select a subsidiary workspace from the context
menu.
From a chart view:
The data displayed in some bar charts and plot charts is linked to subsidiary
workspaces. To search for a link, right-click a bar or data point in the chart. If Link
to displays in the context menu, you can select a subsidiary workspace pertaining
to the data in the chart.
Workspace organization
The hierarchy levels shown in the Navigator depend on how your enterprise
customizes the Tivoli Enterprise Portal. However, ITCAM for Application
Diagnostics - WebSphere Agent does provide a set of predefined workspaces,
which do not require customization. The following list shows the order and
hierarchy of the predefined workspaces provided by the IBM Tivoli Composite
Application Manager for Application Diagnostics - WebSphere Agent Tivoli
204
ITCAM for Application Diagnostics: User Guide
Enterprise Monitoring Agent. It is a representation of how the predefined
workspaces are organized in the Navigator. For more detailed information about a
workspace, click its name in the table.
operating system [for example, Windows]
v system [that is, node name]
– WebSphere Agent
- “WebSphere Agent Summary workspace” on page 214
- “WebSphere Agent Summary Status workspace” on page 215
- “Application Server Summary workspace” on page 215
- “Configuration workspaces” on page 221
v “WebSphere Application Server workspace” on page 291
v “Resources and Applications workspaces” on page 217
v “High Availability Manager workspace” on page 255
v “DCS Stacks workspace” on page 248
v “Configuration workspaces” on page 221
v
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Websphere App Server Servant Regions, and Selected Region - Application Server Summary.
For more information, see “Region workspaces in a z/OS environment”
on page 298.
v Application Health
– Application Registry
– Application Trend at L1
– Application Trend at L2/L3
– OS Stack
– JVM Stack Trend
–
–
–
–
–
“Web Tier Analysis workspace” on page 276
“Backend Tier Analysis workspace” on page 274
“Request Baseline workspace” on page 272
“Application Configuration workspace” on page 274
“EJB Tier Analysis workspace” on page 273
– “Application Health History workspace” on page 275
–
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Selected Application Servant Regions , and Selected Region - Application Health Status.
For more information, see “Region workspaces in a z/OS
environment” on page 298.
v Request Analysis
– Selected Request - Datasources
– Selected Request JMS Queues
– Selected Request Resource Adapters
– Selected Request - History
Chapter 4. ITCAM Agent for WebSphere
205
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Selected Region - Request
Analysis , and Selected Request - Servant Regions. For more
information, see “Region workspaces in a z/OS environment” on page
298.
v Garbage Collection Analysis
– Allocation Failures
– Garbage Collections - Selected Allocation Failure
–
Note: The following workspace is only available when running a
monitoring agent in a z/OS environment, Selected Region - History,
and Garbage Collection Analysis - Servant Regions. For more
information, see “Region workspaces in a z/OS environment” on page
298.
v Log Analysis
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Selected Region - Log
Analysis. For more information see, “Region workspaces in a z/OS
environment” on page 298.
v Pool Analysis
v Datasources
– “Data sources workspace” on page 243
– “Selected Datasources - Datasource Trend workspace” on page 277
Note: The following workspace is only available when running a
monitoring agent in a z/OS environment, Data Sources- Servant
Regions, and Selected Regions - Datasources. For more information
see, “Region workspaces in a z/OS environment” on page 298.
v JMS Summary
–
Note: The following workspace is only available when running a
monitoring agent in a z/OS environment, Selected JMS - Servant
Regions, and Selected Region - JMS Summary. For more information
see, “Region workspaces in a z/OS environment” on page 298.
v Web Applications
– Sessions
– Servlets / JSPs - Selected Enterprise Application
v EJB Containers
– Container Object Pools
– Container Transactions
– Enterprise Java Beans
v DB Connection Pools
– Selected DB Connection Pool - History
v J2C Connection Pools
v Thread Pools
– “Thread Pool Trend workspace” on page 286
– Alarm Manager
206
ITCAM for Application Diagnostics: User Guide
v Cache Analysis
– “Thread Pool Trend workspace” on page 286
–
v Workload Management
v Scheduler
v Web Services
– Selected Web Services - History
v Messaging Engines
– Client Communications
– Messaging Engine Communications
– WMQ Client Link Communications
– WMQ Link Communications
– Destinations
- Durable Subscriptions
- WebSphere Portal Server
v “Application Server Summary workspace” on page 215
v “Configuration workspaces” on page 221
– “WebSphere Application Server workspace” on page 291
– “Resources and Applications workspaces” on page 217
– “High Availability Manager workspace” on page 255
– “DCS Stacks workspace” on page 248
– “Configuration workspaces” on page 221
–
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Websphere App Server Servant Regions, and Selected Region - Application Server
Summary. For more information, see “Region workspaces in a z/OS
environment” on page 298.
v Portal Summary
v
– Portlet Summary
- Selected Portlet - History
– Portal Pages Summary
- Selected Portal Page - History
–
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Selected Region - Portal
Summary, Selected Region - Portlet Summary , and Selected Region
- Portal Page Summary. For more information, see “Region
workspaces in a z/OS environment” on page 298.
v Request Analysis
– Selected Request - Datasources
– Selected Request JMS Queues
– Selected Request Resource Adapters
– Selected Request - History
Chapter 4. ITCAM Agent for WebSphere
207
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Selected Region - Request
Analysis , and Selected Request - Servant Regions. For more
information, see “Region workspaces in a z/OS environment” on page
298.
v Garbage Collection Analysis
– Allocation Failures
– Garbage Collections - Selected Allocation Failure
–
Note: The following workspace is only available when running a
monitoring agent in a z/OS environment, Selected Region - History,
and Garbage Collection Analysis - Servant Regions. For more
information, see “Region workspaces in a z/OS environment” on page
298.
v Log Analysis
Note: The following workspaces are only available when running a
monitoring agent in a z/OS environment, Selected Region - Log
Analysis. For more information see, “Region workspaces in a z/OS
environment” on page 298.
v Pool Analysis
v Datasources
– “Data sources workspace” on page 243
– “Selected Datasources - Datasource Trend workspace” on page 277
–
Note: The following workspace is only available when running a
monitoring agent in a z/OS environment, Data Sources- Servant
Regions, and Selected Regions - Datasources. For more information
see, “Region workspaces in a z/OS environment” on page 298.
v JMS Summary
Note: The following workspace is only available when running a
monitoring agent in a z/OS environment, Selected JMS - Servant
Regions,and Selected Region - JMS Summary. For more information
see, “Region workspaces in a z/OS environment” on page 298.
v Web Applications
– Sessions
– Servlets / JSPs - Selected Enterprise Application
v EJB Containers
– Container Object Pools
– Container Transactions
– Enterprise Java Beans
v DB Connection Pools
– Selected DB Connection Pool - History
v J2C Connection Pools
v Thread Pools
– Alarm Manager
v Cache Analysis
208
ITCAM for Application Diagnostics: User Guide
v Workload Management
v Scheduler
v Web Services
– Selected Web Services - History
- WebSphere ESB Server
v Application Health Summary
– Selected Application - Application Tier Analysis
– Selected Application - Configuration
– Selected Application - Backend Tier Analysis
– Selected Application - Health History
– Selected Application - Client Tier Analysis
– Application Registry
- Selected Request - Baseline
v High Availability Manager
v DCS Stacks
v Request Analysis
– Selected Request - Datasources
– Selected Request JMS Queues
– Selected Request Resource Adapters
– Selected Request - History
v Garbage Collection Analysis
– Allocation Failures
– Garbage Collections - Selected Allocation Failure
v Log Analysis
v Pool Analysis
v Datasources
– Selected Datasource - History
v JMS Summary
v Web Applications
– Sessions
– Servlets / JSPs - Selected Enterprise Application
v EJB Containers
– Container Object Pools
– Container Transactions
– Enterprise Java Beans
v DB Connection Pools
– Selected DB Connection Pool - History
v J2C Connection Pools
v Thread Pools
– Alarm Manager
v Cache Analysis
v Workload Management
v Scheduler
v Web Services
– Selected Web Services - History
Chapter 4. ITCAM Agent for WebSphere
209
v Messaging Engines
– Client Communications
– Messaging Engine Communications
– WMQ Client Link Communications
– WMQ Link Communications
– Destinations
- Durable Subscriptions
v Service Components
– Service Component Elements
- WebSphere Process Server
v Application Health Summary
– Selected Application - Application Tier Analysis
–
–
–
–
–
Selected Application - Configuration
Selected Application - Backend Tier Analysis
Selected Application - Health History
Selected Application - Client Tier Analysis
Application Registry
- Selected Request - Baseline
v High Availability Manager
v DCS Stacks
v Request Analysis
–
–
–
–
Selected
Selected
Selected
Selected
Request
Request
Request
Request
- Datasources
JMS Queues
Resource Adapters
- History
v Garbage Collection Analysis
– Allocation Failures
– Garbage Collections - Selected Allocation Failure
v Log Analysis
v Pool Analysis
v Datasources
– Selected Datasource - History
v JMS Summary
v Web Applications
– Sessions
– Servlets / JSPs - Selected Enterprise Application
v EJB Containers
– Container Object Pools
– Container Transactions
– Enterprise Java Beans
v DB Connection Pools
– Selected DB Connection Pool - History
v J2C Connection Pools
v Thread Pools
– Alarm Manager
210
ITCAM for Application Diagnostics: User Guide
v
v
v
v
Cache Analysis
Workload Management
Scheduler
Web Services
– Selected Web Services - History
v Messaging Engines
– Client Communications
– Messaging Engine Communications
– WMQ Client Link Communications
– WMQ Link Communications
– Destinations
- Durable Subscriptions
v Service Components
– Service Component Elements
- Lotus® Workplace Server
v Application Health Summary
–
–
–
–
–
Selected Application
Selected Application
Selected Application
Selected Application
Selected Application
- Application Tier Analysis
- Configuration
- Backend Tier Analysis
- Health History
- Client Tier Analysis
– Application Registry
- Selected Request - Baseline
v High Availability Manager
v DCS Stacks
v Workplace Mail
– IMAP/POP
– Messages Queues
v Portal Summary
– Portlet Summary
- Selected Portlet - History
– Portal Pages Summary
- Selected Portal Page - History
v Request Analysis
– Selected Request - Datasources
– Selected Request JMS Queues
– Selected Request Resource Adapters
– Selected Request - History
v Garbage Collection Analysis
– Allocation Failures
– Garbage Collections - Selected Allocation Failure
v Log Analysis
v Pool Analysis
v Datasources
– Selected Datasource - History
Chapter 4. ITCAM Agent for WebSphere
211
v JMS Summary
v Web Applications
– Sessions
– Servlets / JSPs - Selected Enterprise Application
v EJB Containers
– Container Object Pools
– Container Transactions
– Enterprise Java Beans
v DB Connection Pools
– Selected DB Connection Pool - History
v J2C Connection Pools
v Thread Pools
v
v
v
v
– Alarm Manager
Cache Analysis
Workload Management
Scheduler
Web Services
– Selected Web Services - History
For additional information, see: Attribute groups used by the predefined
workspaces
Summary workspaces
You can use summary workspaces to quickly see the status of WebSphere
application servers and applications in your enterprise.
About Summary Workspaces
Summary workspaces provide a way to quickly monitor the status of application
servers and applications. ITCAM for Application Diagnosticsprovides predefined
situations that you can use to monitor WebSphere application servers in your
enterprise. Summary workspaces enable you to quickly determine the status of
these situations. User defined and predefined situations are mapped to various
colored icons in the summary workspaces. The icon color indicates status which
enables you to quickly determine the overall health of applications servers and
applications. The following organization chart shows the structure of the icons in
the summary workspaces:
212
ITCAM for Application Diagnostics: User Guide
Summary Workspace Icons
In summary workspaces, the each icon displays as one of the following statuses:
Critical, Warning, Normal or Unknown. The status is calculated based on the
status of the underlying situations being monitored. Each icon also displays the
metrics for the first two situations shown on the flyover. The following table shows
the possible status of icons:
Table 12. Status Icons
Status Icon
Status
Critical
Warning
Normal
Unknown or Application Stopped
Summary Workspace Flyovers
The icons indicate the status of the WebSphere application servers and applications
in your enterprise. To access more detailed information from the summary
workspaces, point to the icon and a flyover is displayed. The flyover provides
relevant metrics pertaining to the icon. Also, it shows the top 10 situations that are
linked with the icon. You can go directly to the situation event result workspace by
in the flyover.
clicking on the situation link icon
Drill Down on Summary Workspaces
You can drill down on the icons to see further information. When you double-click
on an icon, further workspace views showing more detailed monitoring data are
displayed.
See also
“ITCAM for Application Diagnostics - WebSphere Agent situations” on page 433
Summary Workspace Views
You can use summary workspaces to quickly see the status of WebSphere
application servers and applications in your enterprise. Each workspace can
contain one or more views.
There are five summary workspaces. The following table describes the summary
workspaces:
Chapter 4. ITCAM Agent for WebSphere
213
Table 13. Summary Workspace Table
Workspace Name
Level in TEP
Views Available
WebSphere Agent Summary
Agent level
v Application Servers Status
Table
v Application Servers
Summary
WebSphere Agent Summary
Status
Agent level
v Application Servers Status
v Application Servers
Summary
Application Server Summary Application Server Level
v Application Server Resources
v Application Server Applications
Resources
Application Server Level
v Application Server Resources
v Situation Event Console
Applications
Application Server Level
v Application Server Applications
v Situation Event Console
WebSphere Agent Summary workspace
The WebSphere Agent Summary Workspace provides summary monitoring
information for WebSphere application servers in your enterprise. It contains two
views, the Application Servers Status Table view and the Application Servers
Summary view.
Application Servers Status Table view
Two icons are displayed in this view - the Application and the Resources icons.
The flyover for the Applications icon displays the following metrics:
v Application Server Name
v Average Response Time (ms)
v
v
v
v
Request Rate (Req/Sec)
Error Rate (Errors/sec)
Number of problem Situations
List of top 10 situations
The flyover for the Resources icon displays the following metrics:
v Application Server Name
v JVM CPU%
v GC Active Time (ms)
v Number of problem Situations
v List of top 10 situations
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
214
ITCAM for Application Diagnostics: User Guide
WebSphere Agent Summary Status workspace
The WebSphere Agent Summary Status workspace is an alternative summary
workspace available at the WebSphere agent level. The WebSphere Agent Summary
Status workspace provides summary monitoring information for WebSphere
Application servers.
To switch to the WebSphere Agent Summary Status workspace, right-click the
WebSphere Agent in the Tivoli Enterprise Portal navigator and select Workspace
and then select WebSphere Agent Summary Status.
The WebSphere Agent Summary Status workspace contains two views, the
Application Servers Status view and Applications Servers Summary view.
Application Servers Status View
In this view, there is one icon which indicates the status of both applications and
resources - this is the Server icon. The flyover for the Server icon displays the
following metrics:
v Average Response Time (ms)
v Request Rate (Req/Sec)
v
v
v
v
v
Error Rate (Errors/sec)
JVM CPU%
GC Active Time (ms)
WAS Node Name
WAS Cell Name
v WAS Cluster Name
v Number of Problem Situations
v List of top 10 situations
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Server Summary workspace
The Application Server Summary workspace provides summary monitoring
information for applications running on WebSphere application servers in your
enterprise. It contains two views - the Application Server- Resources view and the
Applications Server - Applications view.
Application Server - Resources View
The Application Server - Resources view contains the following icons:
v OS
v JVM
v Datasource
v Threadpool
v Services
Chapter 4. ITCAM Agent for WebSphere
215
OS icon
The OS icon provides summary metrics for machine CPU and paging metrics. The
flyover for the OS icon displays the following metrics:
v System CPU (ms)
v System Paging Rate (Kbytes/sec)
v Number of problem situations
v List of top 10 situations
When you double-click the OS icon, the following subsidiary views display in the
OS Stack workspace:
v Current OS stack summary
v CPU used
v System Paging
For further information about the OS Stack workspace, see OS Stack
JVM icon
The JVM icon flyover provides summary metrics for: CPU for the JVM process,
garbage collection, and heap metrics. The flyover information for the JVM icon
displays the following metrics:
v JVM CPU%
v GC Active Time (ms)
v List of top 10 situations
When you double-click the JVM icon, the following subsidiary views display in the
JVM Stack Trend workspace:
v JVM CPU Trend
v Percent GC time used
v Heap Usage trend
For further information about the JVM Stack Trend workspace, see JVM Stack
Trend
Datasources icon
The Datasources icon flyover provides summary metrics for JDBC, JMS, JCA and
JTA, it also indicates the number of problem situations. When you double-click the
Datasource icon, the following subsidiary views display in the Datasources
workspace:
v Worst Datasource Query Times
v Worst Datasource Update Times
v Datasources - Current Interval
Threadpool icon
The Threadpool icon flyover provides summary metrics for threadpool information
including the number of problem situations. When you double-click the
Threadpool icon, the following subsidiary views display in the Threadpools
workspace:
v Highest Average Pool Sizes
v Average thread pool usage
216
ITCAM for Application Diagnostics: User Guide
v Threadpools table
Services icon
The Services icon flyover provides summary metrics for Web Services, Workload
Management and System Integration Bus. When you double-click the Services icon:
v for Portal, Services icon will take you to Web Services which has the following
views:
– Worst Response Times
– Most Popular
– Web Services
– Web Service Gateway
v for Lotus, Services icon will take you to Workload Management which has these
views:
– WLM Server Incoming Requests
– WLM Client Outgoing Requests
– Workload Management Server
– Workload Management Client
Application Server - Applications View
In this view, there is an icon per application. The flyover for an Application icon
displays the following metrics:
v Average Response Time (ms)
v Request Rate (Req/Sec)
v Error Rate (Errors/sec)
v Monitoring Level
v Number of problem Situations
v List of top 10 situations
When you double click an Application icon, the following subsidiary views display
in either the Application Trend at L1 or Application Trend at L2/L3 workspace:
v Response Time Trend
v Error Rate Trend
v Request Rate Trend
v Selected Application Summary: Application Name
For further information about the Application Trend workspace, see “Selected
Application - Application Trend at L1 workspace” on page 237, and “Selected
Application - Application Trend at L2/L3 workspace” on page 237
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Resources and Applications workspaces
The Resources and Applications workspaces provides monitoring data for your
application server.
Chapter 4. ITCAM Agent for WebSphere
217
Resources Workspace
To access the Resources workspace, right-click the Application Server node in the
Tivoli Enterprise Portal navigator and select Workspace and then select Resources.
The Resources workspace contains the following views:
v Application Servers Resources
v Situation Event Console
For information about the Application Servers Resources view, see “Application
Server Summary workspace” on page 215. The Situation Event Console displays
additional detail for all open situations. For details on how to perform filtering on
open situations, see Tivoli Monitoring help.
Applications Workspaces
To access the Applications workspace, right-click the Application Server node in
the Tivoli Enterprise Portal navigator and select Workspace and then select
Applications. The Applications workspace contains the following views:
v Application Servers Applications
v Situation Event Console
For information about the Application Servers Applications view, see “Application
Server Summary workspace” on page 215. The Situation Event Console displays
additional detail for all open situations. For details on how to perform filtering on
open situations, see Tivoli Monitoring help.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Situation Mapping and Summary Workspaces
User defined situations are mapped to icons in summary workspaces. When you
create a new situation, if the situation then triggers an alert, detail of the situation
is displayed in one of the summary workspaces icon flyovers.
When you create a situation, the attribute group you base the situation on
determines which summary workspace icon flyover the situation will display in.
The following table shows which attribute groups map to which icons and
predefined situations :
TEMA Attribute
Group Name
218
Icons
Predefined Situations
Applications
Monitoring
Configuration
N/A
WASAppDiscovered
Requests Monitoring
Configuration
N/A
Baseline
N/A
Applications Health
Status
Applications
Applications Server
Status
JVM
Log Analysis
JVM
ITCAM for Application Diagnostics: User Guide
WASApplicationBad, WASApplicationFair,
WASApplicationGood
WASError
TEMA Attribute
Group Name
Icons
KYN Command
N/A
WebSphere Agent
Events
N/A
DC Messages
WebSphere
JVM
Dynamic Cache
Services
Dynamic Cache
Templates
Services
Predefined Situations
Workload Management Services
Client
Workload Management Services
Server
DB Connection Pools
Datasources
WASDBConnectionPoolThrdTimeout
WASDBConnectionPoolUsageMaxed
WASDBConPAverageUsageTimeHigh
WASDBConPAvgWaitTimeHigh
Container Object Pools Threadpools
Enterprise Java beans
Applications
WASEJBCreateTimeHigh
WASEJBMethodResponseTimeHigh
WASEJBRemoveTimeHigh
Web Applications
Applications
WASWebApplicationError
Web Applications Sessions
Applications
WASSrvlSessAvgActiveSessionHigh
WASSrvlSessExtReadTimeHigh
WASSrvlSessExtWriteTimeHigh
Applications Server
JVM, OS
WASHighCPUPercentUsed
EJB Containers
Applications
Servlets JSPs
Applications
Servlet Sessions
Applications
Thread Pools
Threadpools
WASThreadPoolPercentMaxed
WASThreadFreeLow
Container Transactions
Datasources
WASContainerTransactionRollback
WASCTGlbTransDurationHigh
WASCTLclTransDurationHigh
J2C Connection Pools
Datasources
WASJ2CConnectionPoolUsageMaxed
WASJ2CCPAverageUsageTimeHigh
WASJ2CCPAvgWaitTimeHigh
WASServletsJSPError
DCS Stack
High Availability
Manager
Web Services Gateway
Web Services
Alarm Manager
Scheduler
Services
Client Communications Services
Durable Subscriptions
Services
Chapter 4. ITCAM Agent for WebSphere
219
TEMA Attribute
Group Name
Icons
Messaging Engine
Communications
Services
Messaging Engines
Services
Queue
Services
Service Component
Elements
Services
Service Components
Services
Topic Spaces
Services
WMQ Client Link
Communications
Services
WMQ Link
Communications
Services
Predefined Situations
Workplace Mail Service Datasources
Workplace Mail
Queues
Datasources
Workplace Mail
IMAP/POP
Services
Portal Summary
Services
Portal Page Summary
Services
WASPortalPageResponseTime
Portlet Summary
Services
WASPortletResponseTime
Datasources
Services
WASDataSrcConWaitTimeHigh
Request Times and
Rates
Applications
WASHighResponseTime
Request Analysis
Applications
WASReqSQLExecuteTimePercentHigh
WASReqSQLQueryTimePercentHigh
WASReqSQLUpdateTimePercentHigh
JMS Summary
Datasources
Selected Request
Applications
Garbage Collection
Analysis
JVM
Allocation Failure
JVM
Garbage Collection
Cycle
JVM
WASHighGCTimePercent
WASAvgHeapSizeAfterGCHigh
WASOutofHeapSpace
WebSphere Agent
WASNotConnected
WebSphere App Server
WASHighCPUPercentUsed
WASHighResponseTime
Where NA is indicated for the icon, it means that situations created based on these
attribute groups are not reported in the summary workspaces. This is because
these tables are strictly related to TEMA configuration parameters which do not
reflect the application or application server health.
For additional information, see:
WebSphere Agent situations
WebSphere Agent attributes
220
ITCAM for Application Diagnostics: User Guide
Summary Workspaces error messages
Four possible error messages can be displayed in the summary workspace status
bar.
The following table lists and explains the error messages:
Error Message
Explanation
Internal
Communication Error
This message indicates a communication problem between the
summary workspaces front end and the summary workspaces
back end code (called evaluator) running inside the embedded
WebSphere server on the TEPS server. There are two reasons this
error displays:
1. If this messages is displayed for all the summary workspaces,
there is an installation error. Summary workspaces require
code to run inside ITM eWAS. Ensure the following
installation steps have been taken:
a. For ITM 6.1, install the ITM TEP Server Extensions - this
installs eWAS. Install ITCAM for Application Diagnostics.
After installation, reconfigure the TEPS.
b. For ITM 6.2, eWAS is already installed. Install ITCAM for
Application Diagnostics. After installation, reconfigure the
TEPS.
If you don't reconfigure the TEPS, the Summary Workspace
status bar will display ''Internal Communication Error". For
further information about installation, see the ITCAM for Web
Application Diagnostics: WebSphere Tivoli Enterprise Monitoring
Agent Installation Guide publication in the Tivoli information
center: http://publib.boulder.ibm.com/infocenter/tivihelp/
v3r1/topic/com.ibm.itcamwas_wr.doc_6.2/welcome.htm
2. If this error messages is displayed for only some of the
summary workspaces, turn up tracing and send to IBM
support for review.
Invalid Data
This message indicates that data being sent from the summary
workspaces back end code (called evaluator) running inside the
embedded WebSphere server on the TEPS server is malformed.
Turn on the tracing, collect the logs and send to IBM support for
further analysis. For further information about logs and tracing,
see the ITCAM for Application Diagnostics: WebSphere Agent
Problem Determination Guide publication in the Tivoli information
center: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
topic/com.ibm.itcamwas_wr.doc_6.2/welcome.htm
No Applications
Configured
This message indicates that no applications are configured on the
WebSphere server. This message also displays if the WebSphere
server is not connected to the TEMA. The message will no longer
display when the WebSphere server is back online. No user
action is needed.
No Applications Servers This message indicates that no WebSphere servers are connected
Connected
to the TEMA. The message will no longer display when the
WebSphere server is back online. No user action is needed.
Configuration workspaces
Monitoring Agent configuration and tuning is facilitated in the Tivoli Enterprise
Portal through configuration workspaces. There are two configuration workspaces,
one for the Monitoring Agent level and one for the server level:
Chapter 4. ITCAM Agent for WebSphere
221
v WebSphere Agent Configuration workspace
v Application Server Configuration workspace
Both configuration workspaces have the same tabs and configuration settings.
The WebSphere Agent Configuration workspace settings are initial settings applied
to all data collectors managed by the Monitoring Agent. For example, when a Data
Collector connects to the Monitoring Agent for the first time or if the Data
Collector configuration was deleted. In both these examples, the configuration
settings specified in the WebSphere Agent Configuration workspace are applied.
The Application Server Configuration workspace contains individual server
settings and the settings in this workspace override settings in the WebSphere
Agent Configuration workspace.
Settings for the WebSphere Agent Configuration and Application Server
Configuration workspaces are saved in the following files:
Table 14. Workspace configuration files
Workspace
Configuration file
WebSphere
Agent
Configuration
workspace in
windows:
CANDLE_HOME\TMAITM6\hostname_productcode.xml
Application
Server
Configuration
workspace in
windows:
CANDLE_HOME\TMAITM6\
hostname_productcode_servervendor.servernode.server name.xml
CANDLE_HOME/config/hostname_productcode.xml
WebSphere
Agent
Configuration
workspace in
other platforms:
CANDLE_HOME/config/
Application
hostname_productcode_servervendor.servernode.server name.xml
Server
Configuration
workspace in
other platforms:
The WebSphere Agent Configuration workspace configuration settings are initial
settings which are applied to all data collectors managed by the selected
WebSphere agent. The Application Server Configuration workspace configuration
settings override agent level configuration settings.
Both configuration workspaces have the following two views:
v Application Diagnostics Configuration view - this view has the following four
tabs
– Collection (Basic)
– Collection (Advanced)
– Application Dashboard (Basic)
– Application Dashboard (Auto Threshold)
222
ITCAM for Application Diagnostics: User Guide
v Application Servers view - this view has one tab which lists all application
servers monitored by the selected WebSphere agent, for each application server,
there is a link to Application Server Configuration workspace.
Application Diagnostics Configuration - Basic Tab
The Basic tab contains the following fields:
v Request Data Monitoring - in this field, specify the monitoring level for request
data from connected Data Collectors. The following values can be entered into
this field:
– Disable - request data is not monitored and is not displayed
– Level 1 - only monitors edge request data, for example, servlets, JSPs, and
EJBs
– Level 2 - monitors nested request data in addition to edge request data, for
example, JNDI, JMS, JDBC, and JCA requests
v Request Data Monitoring Method - in this field, specify the monitoring method
used by the Monitoring Agent to govern when it uploads request and garbage
collection data from connected Data Collectors. The following values can be
entered into this field:
– On Demand - when the monitoring method is set to On Demand, data is
uploaded only when requested by the user. The exception to this is if the
cache of data is still current - whether or not this data is current is
determined by the Request Data On Demand Maximum Sample Age (sec)
field in the Collection Advanced tab. With On Demand monitoring, the Tivoli
Enterprise Portal response time is slower as the data is collected as requested
but the retrieved data will be the most current available. CPU and memory
usage on the monitored systems is lower for On Demand monitoring.
– Fixed Interval - when the monitoring method is set to Fixed Interval, the
Monitoring Agent will upload sample data from the data collectors at regular
fixed intervals, and respond to a user request using the latest cache of sample
data gathered at the last interval. With Fixed Interval monitoring, CPU and
memory usage can be higher because more data is collected more frequently
but Tivoli Enterprise Portal response time is faster as the data is more readily
available. Data samples are calculated for the same time interval and as a
result are more consistent.
v Resource Data Monitoring - in this field, specify whether resource data is
monitored from connected Data Collectors. The following values can be entered
in this field:
– Disable - resource data is not collected by the Monitoring Agent and is not
displayed in the Tivoli Enterprise Portal.
– Enable - resource data is collected by the Monitoring Agent and is displayed
in the Tivoli Enterprise Portal.
v Resource Data Monitoring Method - in this field, specify the monitoring
methodology used by the agent to govern when it uploads resource data from
connected Data Collectors. The following values can be entered into this field
– On Demand - when the monitoring method is set to On Demand, data is
uploaded only when requested by the user. The exception to this is if the
cache of data is still current - whether this data is current is determined by
the Resource Data On Demand Maximum Sample Age (sec) field in the
Collection Advanced tab. With On Demand monitoring, the Tivoli Enterprise
Portal response time is slower as the data is collected as requested but the
retrieved data is the most current available. CPU and memory usage on the
monitored systems is lower for On Demand monitoring.
Chapter 4. ITCAM Agent for WebSphere
223
– Fixed Interval - when the monitoring method is set to Fixed Interval, the
Monitoring Agent will upload sample data from the data collectors at regular
fixed intervals, and respond to a user request using the latest cache of sample
data gathered at the last interval. With Fixed Interval monitoring, CPU and
memory usage can be higher because more data is collected more frequently
but Tivoli Enterprise Portal response time is faster as the data is more readily
available. Data samples are calculated for the same time interval and as a
result are more consistent.
v Garbage Collection Monitoring - in this field, specify if verbose garbage
collection output monitoring is enabled. The following values can be entered in
this field:
–
Disable - verbose garbage collection output data is not collected by the
Monitoring Agent and is not displayed in the Tivoli Enterprise Portal.
– Enable - verbose garbage collection output data is collected by the
Monitoring Agent and is displayed in the Tivoli Enterprise Portal.
Application Dashboard (Basic) tab
The Application Dashboard (Basic) tab contains the following fields:
v Application Fair Completion Rate Threshold (%) - Defines the default
completion percentage for application fair availability threshold.
v Application Bad Completion Rate Threshold (%) - Defines the default
completion percentage for application bad availability threshold.
v Application Fair Resource Usage Threshold (%) - Defines the threshold
percentage for fair usage level of an application resource.
v Application Bad Resource Usage Threshold (%) - Defines the threshold
percentage for bad usage level of an application resource.
v Application Resource Usage Monitoring Cutoff Threshold (%) - Defines the
cutoff threshold percentage for application resources usage monitoring.
v Request Monitoring Control Level - Specifies the request monitoring control
level for the server. The following entries can be entered to this field:
– Application Request monitoring settings are defined for each application
independently.
– Server Request monitoring settings are defined on the server level and
override the settings defined for applications.
The Request Monitoring Control Level option gives you more control over request
monitoring settings. In certain sequences, you can benefit from "locking" the
request monitoring control on the server level, because you can change data
collector monitoring level in one place.
In ITCAM For Application Diagnostics 7.1, the request data monitoring level
(Level1 or Level2) that displays on the Tivoli Enterprise Portal depends on the
Request Monitoring Control Level setting you choose.
v If you select the Request Monitoring Control Level as Application (the default
setting), only Level2 data displays in the Tivoli Enterprise Portal when the
Request Data Monitoring Level for the application is Level2.
v If you select the Request Monitoring Control Level as Server, and then set the
Request Data Monitoring Level at Level2 using take action
Start_Request_Monitoring, the Request Data Monitoring Level for all the
applications in this server is Level2. You can set Request Data Monitoring Level
back to Level1 for any application in the server by using the take action,
Set_Application_Monitoring and selecting Level1. However, in the Tivoli
Enterprise Portal, the Request Data Monitoring Level still displays as Level2.
224
ITCAM for Application Diagnostics: User Guide
This is because the Tivoli Enterprise Portal displays the effective request
monitoring control level. When you change the Request Monitoring Control
Level to Application, the Request Data Monitoring Level in the Application
Configuration workspace becomes Level1 for that application.
Collection Advanced tab
The Collection Advanced tab contains the following fields:
v Request Data On Demand Maximum Sample Age (sec) - The maximum
allowed age of sample request data in seconds before collecting a new sample of
data. If the monitoring method is set to On Demand, when a user request is
received, and the current sample cache is older than the value specified, then the
Monitoring Agent uploads a new sample before servicing the request. Two
successive on-demand requests received from users within the period specified
by the maximum sample age return the same results without incurring the CPU
and memory cost of a new data sample.
v Request Data Fixed Interval between Collections (sec) - The amount of time in
seconds between uploads of sample request data from the data collectors to the
Monitoring Agent when the monitoring method is set to Fixed Interval. When a
user request is received, it is serviced from the latest uploaded sample.
v Request Data Sampling Rate (%) - The percentage of requests that are sampled
for request data monitoring.
v Resource Data On Demand Maximum Sample Age (sec) - The maximum
allowed age of sample resource data in seconds before collecting a new sample
of data. If the monitoring method is set to On Demand, when a user request is
received and the current sample cache is older than the value specified in this
field, then the Monitoring Agent uploads a new sample before servicing the
request. Two successive on-demand requests received from a user within the
period specified by the maximum sample age return the same results without
incurring the CPU and memory cost of a new data sample.
v Resource Data Fixed Interval between Collections (sec) - The amount of time
in seconds between uploads of sample resource data from the data collectors to
the agent. When a Tivoli Enterprise Portal request is received, it is serviced from
the latest uploaded sample.
v Garbage Collection Polling Interval (sec) - The interval in seconds between the
Monitoring Agent scanning the verbose Garbage Collection output.
v Log Scan Polling Interval (sec) - The interval in seconds between the Agent
scanning the Application Server standard output log for changes.
Application Dashboard (Auto Threshold) tab
The Application Dashboard (Auto Threshold) tab contains the fields:
v Response Time Selection (%) - Defines the percentage from baseline to be used
for response time auto-thresholding.
v Response Time Deviation (%) - Defines the deviation for baseline selection to
be used for response times auto-thresholding.
v Fair Response Time Projection (%) - Defines the percentage to derive the fair
response time threshold from the baseline selection.
v Bad Response Time Projection (%) - Defines the percentage to derive the bad
response time threshold from the baseline selection.
Workspace link to Managing Server Visualization Engine
With the appropriate configuration and permissions, you can access the Managing
Server Visualization Engine from specific workspaces in the WebSphere Tivoli
Enterprise Portal. Instead of opening another browser and clicking the relevant
Chapter 4. ITCAM Agent for WebSphere
225
link, you can access the Managing Server Visualization Engine from Tivoli
Enterprise Portal using a link called Diagnostic Server Activity Display. Some of
the workspaces have additional links you can use to access the Managing Server
Visualization Engine. All these links begin with the word Diagnostic. When you
log in to the Welcome to the Application Monitor page, the information displayed
is specific to the content in the Tivoli Enterprise Portal workspace you selected.
You also have the option to manually create your own links to the Managing
Server Visualization Engine using the Link Wizard which is available on all
workspaces.
You can access the Managing Server Visualization Engine from the following
workspaces.
v WebSphere Agent
v Request Analysis
v Garbage Collection Analysis
v Datasources
v JMS Summary
v Web Applications
v
v
v
v
EJB Containers
DB Connection Pools
J2C Connection Pools
Thread Pools
This is a list of the Managing Server Visualization Engine links available from the
workspaces:
v Diagnostic Server Activity display. Use this link to diagnose application
problems, for example, slow transactions or high response times. This link is
available from all workspaces except Request Analysis and Garbage Collection
Analysis.
v Diagnostic In-Flight Request Search. Use this link to identify any hanging
transactions. This feature is only available from the WebSphere Agent and
Request Analysis workspaces.
v Diagnostic Recent Completed Requests. The Recent Requests tab displays data
regarding recently completed server requests. This feature is only available from
the Request Analysis workspace.
v Diagnostic SMF Data. This feature is only available you are using a z/OS Data
Collector and in the Request Analysis workspace. The SMF Overview displays
summary information for all the resources on the selected application server.
v Diagnostic JVM Thread Display Use this link to diagnose application problems,
for example, slow transactions by examining threads running in JVM. This link
is available from the Thread Pools workspace.
v Diagnostic Memory Leak Use this link to diagnose memory leak problems. This
link is available from the Garbage Collection Analysis workspace.
For information about accessing workspaces, see “Accessing the Managing Server
Visualization Engine from Tivoli Enterprise Portal workspaces” on page 228.
Prerequisites for access
The following conditions must be met to gain access to the Managing Server
Visualization Engine through the Tivoli Enterprise Portal.
226
ITCAM for Application Diagnostics: User Guide
v ITCAM for Application Diagnostics Managing Server version 7.1 and ITCAM for
WebSphere Data Collector version 7.1. must be installed in your environment.
v Tivoli Enterprise Portal users must be members of the Diagnostic Users Group
within the Tivoli Enterprise Portal. For more information see “Granting Users
access to Managing Server Visualization Engine from Tivoli Enterprise Portal.”
v During the installation of the Managing Server, kernel properties in the
Managing Server must be set up accordingly with the correct host name and
port number. This action is completed by the user installing the Managing
Server.
You can also create your own links to the Managing Server Visualization Engine
using the Link Wizard.
For more information see “Creating links to the Managing Server Visualization
Engine using the Link Wizard” on page 233
Kernel Settings to access the Managing Server Visualization
Engine through the Tivoli Enterprise Portal
If users are to access the Managing Server Visualization Engine through the Tivoli
Enterprise Portal, the kernel properties in the Managing Server must be set up
accordingly with the correct host name and port number.
The following properties need to be added to kl1.properties and kl2.properties
(By default, the Managing Server installer replaces @{HOST_VE} and
@{PORT_VE_HTTP} at Managing Server installation time) :
v ve.host=@{HOST_VE}
v ve.port=@{PORT_VE_HTTP}
At kernel startup time, the kernel needs to read these two properties, and set them
as part of properties in PROBE_CONFIG.PROPS. If a user changes the VE host
name or port number, then the kernel needs to be restarted. Use the following
steps to start and stop the kernel In $MS_HOME/bin:
1. To start kernel, issue:./amctl.sh wd<kernel count> start
2. To stop kernel, issue: ./amctl.sh wd<kernel count> stop
where <kernel count> is 1 by default.
Granting Users access to Managing Server Visualization Engine
from Tivoli Enterprise Portal
As a user you must be set up as a member of the DIAGNOSTIC USERS group in
the Tivoli Enterprise Portal, otherwise you will not have access to the Visualization
Engine from the Tivoli Enterprise Portal. The default administration user
Sysadmin is automatically a member of this group. Any user with administrator
permissions can add or remove additional users to the DIAGNOSTIC USERS
group.
Before you begin
To complete this task you must be a user with administrator permissions to add or
remove additional users to the DIAGNOSTIC USERS group. For more
information about access see “Prerequisites for access” on page 226.
1. From the Tivoli Enterprise Portal main menu, click Edit > Administer Users.
2. In the Administer Users window, in the top half of the window, click the Users
Groups tab.
Chapter 4. ITCAM Agent for WebSphere
227
3. Click the group name, in this case DIAGNOSTIC USERS.
4. In the bottom half of the window click the Members tab to view existing
members of this group and to assign additional users.
5. To add users, in the Available Members section select the users you want to
assign to the Group.
6. Click the left arrow to move the selected users to the Assigned Members
section of the window.
7. Click Apply and OK to implement the changes.
8. If you want to remove a user from the group click the Assigned Members tab,
select the users you want to remove.
9. Click the right arrow to move the selected users to the Available Members tab.
Then click Apply and OK.
What to do next
Users who are members of this group can access the Managing Server
Visualization Engine from the Tivoli Enterprise Portal. See “Accessing the
Managing Server Visualization Engine from Tivoli Enterprise Portal workspaces.”
Adding the LDAP user to Tivoli Enterprise Portal user accounts:
About this task
To add the LDAP user to Tivoli Enterprise Portal user accounts, use Tivoli
Enterprise Portal user administration.
1. In the Tivoli Enterprise Portal main menu, select Administer Users.
Click Create New User to create a user profile from defaults, or Create
Another User to create a user profile as a copy of an existing one.
3. In the Modify User window, enter the user name for the new user in the User
ID field.
4. In the Distinguished Name field, enter the following string:
2.
uid=username,cn=users,dc=ibm,dc=com
This string registers the LDAP user with Tivoli Enterprise Portal. If you are
using an existing LDAP configuration, use the applicable distinguished name.
Note: For more information about Single sign on refer to Appendix N Setting Up
single sign on for Tivoli Enterprise Portal Users in the ITCAM for Application
Diagnostics 7.1 Managing Server Installation and Customization Guide.
Accessing the Managing Server Visualization Engine from Tivoli
Enterprise Portal workspaces
Use the following links for information about how to access the Managing Server
Visualization Engine from the Tivoli Enterprise Portal workspaces.
To ensure you have access to the Managing Server Visualization Engine see
“Prerequisites for access” on page 226 before you begin.
v “Accessing the Managing Server Visualization Engine from the WebSphere
Agent workspace” on page 290
v “Accessing the Managing Server Visualization Engine from the Request Analysis
workspace” on page 271
v “Accessing the Managing Server Visualization Engine from the Garbage
Collection Analysis workspace” on page 254
228
ITCAM for Application Diagnostics: User Guide
v “Accessing the Managing Server Visualization Engine from the Datasources
workspace” on page 245
v “Accessing the Managing Server Visualization Engine from the JMS Summary
workspace” on page 260
v “Accessing the Managing Server Visualization Engine from the Web Applications
workspace” on page 288
v “Accessing the Managing Server
workspace ” on page 251
v “Accessing the Managing Server
Pools workspace” on page 247
v “Accessing the Managing Server
Pools workspace” on page 258
v “Accessing the Managing Server
workspace” on page 286
Visualization Engine from the EJB Containers
Visualization Engine from the DB Connection
Visualization Engine from the J2C Connection
Visualization Engine from the Thread Pools
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal”
Access the Managing Server Visualization Engine from the Tivoli
Enterprise Portal
You can access the Managing Server Visualization Engine from links in the ITCAM
Agent for WebSphere Applications workspaces.
When you access the Managing Server Visualization Engine in this way, the
Managing Server Visualization Engine displays in a browser view inside a
workspace. The Tivoli Enterprise Portal navigation tree is automatically hidden in
the workspace. To show or hide the Tivoli Enterprise Portal navigation tree, click
the small black arrow on the left side of the window.
The following table displays a list of Tivoli Enterprise Portal workspaces that have
links to the Managing Server Visualization Engine.
Table 15. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine
Workspace: Table
View Name
WebSphere Agent
Summary Status >
Application Servers
WebSphere Agent
Summary Status >
Application Servers
WebSphere Agent
Configuration >
Application Servers
Number of
links to
Managing
Server
Visualization
Engine
Link Name
Link Target
Pages
Managing
Server
Visualization
Engine
Pre-populated
information in the
link page to
Managing Server
Visualization
Engine
2
v Server
Activity
Display –
Active
Requests
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
v Diagnostic
Server
Activity
Display
v Diagnostic
In-Flight
Request
Search
v In-Flight
Request
Search
Chapter 4. ITCAM Agent for WebSphere
229
Table 15. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine (continued)
Workspace: Table
View Name
OS Stack > Current
OS Stack Summary
Number of
links to
Managing
Server
Visualization
Engine
Link Name
Link Target
Pages
Managing
Server
Visualization
Engine
Pre-populated
information in the
link page to
Managing Server
Visualization
Engine
3
v Server
Activity
Display –
Active
Requests
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
v Diagnostic
Server
Activity
Display
v Diagnostic
In-Flight
Request
Search
v In-Flight
Request
Search
v Using the
v <platform
dynamic
OS>
workspace
<platform>
link to the
is one of
corresponding
the
OS agent
following
workspace.
operating
For z/OS, the
systems:
link is to
Linux,
OMEGAMON
UNIX,
XE for z/OS.
Windows or
z/OS
JVM Stack Trend
>JVM Stack Trend
230
1
ITCAM for Application Diagnostics: User Guide
Diagnostic
Memory Leak
Memory Leak Analysis
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
Table 15. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine (continued)
Workspace: Table
View Name
Request Analysis >
Requests – Current
Interval
Number of
links to
Managing
Server
Visualization
Engine
Link Name
Link Target
Pages
Managing
Server
Visualization
Engine
3
v Server
Activity
Display –
Recent
Requests
Pre-populated
information in the
link page to
Managing Server
Visualization
Engine
v The Group
Server
dropdown
menu is
pre-populated
v Diagnostic
based on data
v In-Flight
In-Flight
collector
Requests
Request
information
Search
v SMF Data (for
from Tivoli
z/OS data
v Diagnostic
Enterprise
collectors
SMF Data
workspace.
only)
(z/OS only)
v Content in
Request Detail
column of
Requests table
view in Tivoli
Enterprise
Portal is
pre-populated
in the following
fields:
v Diagnostic
Recent
Completed
Requests
– Recent
Requests:
Client
Request
– In-Flight
Request
Search:
Search
Request/
Transaction
field
Garbage Collection
Analysis >Garbage
Collection Analysis
1
Diagnostic
Memory Leak
Memory Leak Analysis
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
Thread Pools
>Thread Pools
1
Diagnostic
JVM Thread
Display
The Group Server
dropdown menu
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
JVM Thread
Display
Chapter 4. ITCAM Agent for WebSphere
231
Table 15. Tivoli Enterprise Portal workspaces that have links to Managing Server
Visualization Engine (continued)
Workspace: Table
View Name
Datasources >
Datasources –
Current Interval
Number of
links to
Managing
Server
Visualization
Engine
Link Name
Link Target
Pages
Managing
Server
Visualization
Engine
1
Server Activity
The Group Server
Display – Active dropdown menu
Requests
is pre-populated
based on data
collector
information from
Tivoli Enterprise
workspace.
Web Applications
>Web Applications
EJB Containers >EJB
Containers
Diagnostic
Server
Activity
Display
Pre-populated
information in the
link page to
Managing Server
Visualization
Engine
JMS Summary >JMS
Summary – Current
Interval
DB Connection
Pools > DB
Connection Pools
J2C Connection
Pools > J2C
Connection Pools
The Server Group feature that displays at the top of these pages applies to the
Managing Server Visualization Engine. When you access any of these pages this
page from the Tivoli Enterprise Portal the information in the Groups and Servers
fields is automatically populated with the data collector associated with the link
and workspace you selected in the Tivoli Enterprise Portal.
Groups are a set of application servers which have similar functionality. All
configured data collectors are automatically in the Unassigned Servers Group. The
relationship between Server Group and data collector is many to many. A data
collector can belong to one or more server groups. A server group can have one or
more data collectors. You can add data collectors to groups using the Server
Management functionality in the Managing Server Visualization Engine. For more
information about adding data collectors to Server Groups, refer to the Composite
Application Manager Help in the Managing Server Visualization Engine interface.
The Server Activity Display section has three tabs.
v Active Requests: provides real time request or transaction data for an
application server at the time the page displays.
v Recent Requests: displays the last 100 or less completed request or transaction
data for an application server.
v Lock Contentions: displays requests that are hanging because they are waiting
on a lock. The data shows data that is currently locked and the item that is
waiting to be locked.
The Active Requests tab and the Recent Requests tab have a toolbox icon
You can click this icon to access direct links to the following features:
232
ITCAM for Application Diagnostics: User Guide
.
v
v
v
v
v
JVM Display
System Resources
Monitoring On Demand
Data Collector Properties
Trap and Alert Management
When you access the Managing Server Visualization Engine in this way, the
Managing Server Visualization Engine displays in a browser view inside a
workspace. The Tivoli Enterprise Portal navigation tree is automatically hidden in
the workspace. To show or hide the Tivoli Enterprise Portal navigation tree, click
the small black arrow on the left side of the window.
Creating links to the Managing Server Visualization Engine using
the Link Wizard
Throughout the Tivoli Enterprise Portal, you can use the Link Wizard to manually
create links to the Managing Server Visualization Engine.
Creating links
You can access the Link Wizard feature from other views and workspaces in the
Tivoli Enterprise Portal.
1. To access the Link Wizard, from any of the tables or views, right click the link
and click Link Wizard.
icon
2. Follow the steps in the wizard to do one of the following actions:
v Create a new link.
v Modify an existing link.
v Delete one or more links.
3. Type the name and description of the link.
4. Choose one to the following options with the aid of the descriptions in the
Link Wizard.
v Dynamic
v Absolute
v Relative
5. Choose the option you want to use. Follow the instructions in the help within
the application until you get to the Workspace Link Wizard Parameters page.
Adding parameters to the Link Wizard
When you get to the Workspace Link Wizard Parameters page in the Link Wizard
you will need to manually add these two symbols VEHOSTPORT and VEPATH
and add information to these parameters. There are two predefined workspaces
which have an embedded browser as its only view.
v Diagnostic Link for Agent. Choose this workspace if the link is from the agent
level workspaces.
v Diagnostic Link. Choose this workspace if the link is from the server level
workspace.
1.
2.
3.
4.
To add Symbols to the Link Wizard. Click Symbol and type VEHOSTPORT.
Click OK to add the Symbol.
To add an expression select VEHOSTPORT click Modify Expression.
Basic Setup: In the text field, type the expression you want to add. The value
for the VEHOSTPORT is <your ve host>:<your ve port>. For example, if in
Chapter 4. ITCAM Agent for WebSphere
233
your environment, the Managing Server Visualization Engine is installed on
host1, with port 9080, then the VEHOSTPORT value is: “host1:9080”.
Note:
v Double quotation marks are required in the expression.
v If your Managing Server Visualization Engine host or port information
changes, then you need to update the link you defined and correct the
VEHOSTPORT information manually.
Advanced Setup: In the text field, type the expression you want to add. The
value for the VEHOSTPORT value is CALL(candle.kwj.ve.ITCAMLinkHelper,
getVehostportForWASServer, null, null,
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$). To get the expression:
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$, in the Expression
Editor, click Symbol.
5. Click Origin Node and click OK to get
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$.
When using the Advanced set up option, if your Managing Server Visualization
Engine host or port information changes, ITCAM for Application Diagnostics
custom code updates the changes automatically, you do not need to modify the
links you defined manually to correct the information.
6. To add an expression, Basic Setup: the VEPATH value can be set as
“am/ve/sad/threadList?mappingTEPUrl=true”
Note:
v Double quotation marks are required in the expression.
v When you use the Basic Setup option, you need to select the server group
and the server in the Managing Server Visualization Engine yourself when
you log in to Managing Server Visualization Engine.
To add an expression, Advanced Setup: Set the VEPATH value in the
Expression Editor as:"am/ve/sad/threadList?mappingTEPUrl=true&server=" +
CALL(candle.kwj.ve.ITCAMLinkHelper, getServerIdForWASServer, null, null,
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$)
Where the correct expression of
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$ can be found by using
Symbols view under Expression Editor:
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$ (Symbol: Origin Node).
7. Review the details in the Workspace Link Wizard - Summary. Click Finish.
8. If you use the Advanced Setup options in Step 4 and Step 6, modify the
linkIsEnabled parameter in the Workspace Link Wizard Parameters view with
expression: CALL(candle.kwj.ve.ITCAMLinkHelper, isEnabledForWASServer, null,
null, $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$) &&
$kfw.TableRow:ATTRIBUTE.<table_name>.ASID$ != -3. In the Expression Editor,
use the Symbols view to find expressions of
$kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$ (Symbol: Origin
Node)and $kfw.TableRow:ATTRIBUTE.<table_name>.ASID$ (Symbol: ASID).
234
ITCAM for Application Diagnostics: User Guide
Manually adding your own links to the Link Wizard
The minimum settings are VEHOSTPORT and VEPATH. If you need to link to a
different page, you need to change this value to corresponding URL path. Here is a
list of frequently used Managing Server Visualization Engine Paths page URL
paths:
v Enterprise Overview: am/home
v Server Overview: am/ve/serverOverview
v
v
v
v
v
v
v
Server Statistics Overview : am/avm/main
Server Activity Display: am/ve/sad/threadList
Memory Leak: am/ve/memory/leakReport
JVM Thread Display: am/ve/jtd/threadGroupList
Monitoring On Demand: am/ve/mod/console
Trap and Alert Management: am/trap
System Resources:am/ve/jmxbrowser
Note: If you change the host port number at any point. You need to modify these
two properties again and the kernel properties on the MS install will need to be
restarted to identify the changes.
Link anchor
You can use the Link anchor option to access the Link anchor properties window.
You can use the Link anchor properties window to display visual indicators on
tables where customized links have been defined, and to establish a default link
that opens when the user clicks the indicator.
and click Link
1. From any of the tables, right click the choose link icon
Anchor to display the Link anchor properties window.
2. Depending on the area of the table item you select, the window displays the
following information:
v Default no link
v Show Link indicator
v Link indicator always enabled.
3. For more information about the uses of these items refer to the help within the
Link anchor properties window.
“Workspace link to Managing Server Visualization Engine” on page 225
Alarm Manager workspace
This workspace displays aggregated information about the alarms for each work
manager.
This workspace displays data provided by the Alarm Manager attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
Chapter 4. ITCAM Agent for WebSphere
235
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains:
v Highest Alarm Rate bar chart, which displays the five highest number of alarms
fired per second
v Work Manager Alarms report, which displays detailed information about the
alarms for each work manager
Accessing the Alarm Manager workspace
To access this workspace from the Thread Pools workspace, use one of the
following procedures:
v Within the Navigator, right-click the Thread Pools entry; then from the pop-up
menu, select Workspace > Alarm Manager.
v From the primary Tivoli Enterprise Portal menu, pull down the View menu, and
select Workspace > Alarm Manager.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Allocation Failures workspace
This workspace summarizes all the heap-allocation failures that occurred within
the Java Virtual Machine (JVM) over the current interval and that caused the JVM
to initiate garbage collection.
This workspace displays data provided by the Allocation Failure attributes.
Note to Solaris and HP-UX users: Allocation-failure information is not recorded on
these platforms; hence this workspace is always empty.
The predefined workspace contains the following items:
v Allocation Failure Elapsed Times bar chart, which displays the number of
allocation failures during the current interval
v Heap Usage bar chart, which displays the heap usage for this JVM. The bar's fail
over gives the allocation-failure ID number followed by a range of recording
times. This allocation-failure number displays in the Allocation Failures report
and associates each bar with that particular row within the report
v Allocation Failures report, which displays information about the heap-allocation
failure that caused the Java Virtual Machine hosting the application server to
invoke its garbage-collection routine. The Allocation Failures report includes the
ASID field.
Accessing the Allocation Failures workspace
To access this workspace from the Garbage Collector Activity workspace, complete
the following steps:
236
ITCAM for Application Diagnostics: User Guide
v From the Garbage Collection Analysis report, right-click the link icon to the left
of any row; then, from the pop-up menu, click Allocation Failures. Note that in
the Allocation Failure workspace, the ASID is displayed in the Allocation
Failures report.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Selected Application - Application Trend at L1 workspace
This workspace displays access trends for individual applications. It provides trend
information for request and response times. It also provides trend information for
application errors. This workspace provides a broad overview of the health of an
application and draws data from multiple attribute groups.
This workspace displays data provided by the Request Analysis and Request Times
and Rates attribute groups.
The predefined workspace contains:
v Selected Application Summary report displays application name, average request
response time, average request completion rate, error rate, and ASID. For TEMA
running on z/OS, region ID can be found in the ASID column.
v Response Time Trend chart displays summary trend times for the overall
response time for the selected application.
v Error Rate Trend chart displays the error rate for the application.
v Request Rate Trend chart displays the number of requests completed per second
for the application.
Accessing the Selected Application - Configuration workspace
Access this workspace using one of the following methods:
v Double click any application in the Application Server Summary workspace.
v Right-click on application icon in the Application Server Summary workspace
and select Link To, then select Application Trend at L1.
For additional information, see:
v Application Server Summary Workspace
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Selected Application - Application Trend at L2/L3 workspace
This workspace displays access trends for individual applications. It provides trend
information for request and response times. It also provides trend information for
application errors. This workspace provides a broad overview of the health of an
application and draws data from multiple attribute groups.
This workspace displays data provided by the Request Analysis and Request Times
and Rates attribute groups.
The predefined workspace contains:
Chapter 4. ITCAM Agent for WebSphere
237
v Selected Application Summary report displays application name, average request
response time, average request completion rate, error rate, and ASID. For TEMA
running on z/OS, region ID can be found in the ASID column.
v Response Time Trend chart displays trend times for the following different
elements in milliseconds: JNDI, JMS, Application, JCA, Servlet and EJB.
v Error Rate Trend chart displays the error rate for the application.
v Request Rate Trend chart displays the number of requests completed per second
for the application.
Accessing the Selected Application - Configuration workspace
Access this workspace using one of the following methods:
v Double click any application in the Application Server Summary workspace.
v Right-click on application icon in the Application Server Summary workspace
and select Link To, then select Application Trend at L2/L3.
For additional information, see:
v Application Server Summary Workspace
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Health workspace
The workspace displays the information about the real-time health status of
applications monitored by the Tivoli Enterprise Monitoring Agent.
The health status information is collected from the following sources.
v Request Metrics - performance data that measures request execution time
collected from the ITCAM instrumentation points in the application code.
v Resource Metrics - pool usage and container performance statistics collected
from the corresponding PMI modules or MBeans.
v GC Metrics - metrics on garbage collection frequency and performance collected
from parsing of the GC verbose log file when it is enabled for the application
server JVM.
v OS metrics - metrics collected about the JVM process and the whole system
execution, such as CPU used percentage, paging rate, etc.
Additionally, the monitoring agent uses thresholds, called Application Health
Indicators, to determine the quality of the application service. For request response
times, thresholds are assigned automatically during baselining. You can also
manually customize the thresholds. There are three monitored application tiers
evaluated for health status.
v Client Tier provides performance data and status of application execution in
servlets/JSPs or portal containers as well as corresponding thread pools
servicing these containers.
v Application Tier provides application execution metrics of EJB containers and
custom requests.
v Backend Tier provides application execution in JDBC, JCA, JMS, JNDI API calls.
This workspace displays data provided by the Application Health Status attributes.
By default, the predefined workspace has the following views:
238
ITCAM for Application Diagnostics: User Guide
v Situation Event console view, which shows the event console with activity
associated with the Application Health Summary Navigator item and any other
workspaces in the group, as well as linked workspaces. The Navigator will
display an event icon overlaid on the Application Health Summary node when a
situation becomes true. The report is useful when multiple alerts are raised as
you can see them all in a single filtered view.
v Application Health Summary report, which shows the report of the application
name, status, and health indicator for client, application, and backend tiers
health status.
Note: Due to the runtime MBeans configuration, the Tivoli Enterprise Monitoring
Agent (TEMA) can only find composition units of business-level applications that
associate with either web or EJB modules.
Accessing the Application Health Summary workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux® Systems, z/OS
Systems or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the note you want to
select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere Application server
entry of your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Application Health entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Registry workspace
This workspace displays the information about the server configuration for the
application.
This workspace displays data provided by the Application Monitoring
Configuration attributes.
The predefined workspace contains:
v Situation Event Console report, which shows the event activity for situations
associated with the current Navigator item. The Navigator alerts you when a
situation becomes true by overlaying the Navigator item with an event indicator.
This report is useful when multiple alerts are raised and you might not know
newly arrived alerts just by looking at the indicator.
v Application Configuration report, which shows the configurations that are
discovered, stored and managed for WebSphere applications running within that
application server.
Accessing the Application Registry workspace
To access this workspace from the Application Health Summary workspace, use
one of the following procedures:
Chapter 4. ITCAM Agent for WebSphere
239
v Within the Navigator, right-click the Application Health entry; then, from the
pop-up menu, click Workspace > Application Registry.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Application Registry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Cache Analysis workspace
This workspace reports information about the dynamic cache.
WebSphere Application Server consolidates several caching activities, including
servlets, Web services, and WebSphere commands, into one service called the
dynamic cache. These caching activities work together to improve application
performance. The activities share many configuration parameters, which are set in
an application server's dynamic cache service. The dynamic cache works within an
application server's Java Virtual Machine (JVM), intercepting calls to cacheable
objects, for example, through a servlet's service method or a command's execute
method. The dynamic cache either stores the object's output to or serves the
object's content from the dynamic cache.
This workspace displays data provided by both the Dynamic Cache attributes and
the Dynamic Cache Templates attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides
on-demand sampling by default. To activate PMI monitoring, you must first
select this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v In-memory Cache Sizes - History graph, which shows the sizes of in-memory
cache entries for the specified interval
v Highest Miss Rates bar chart, which shows the most frequent cache entry misses
(per second). The Y-axis headings correspond to the row number of the Dynamic
Cache Templates report
v Dynamic Cache report, which displays information about the dynamic cache,
including cache sizes and timeout rates
v Dynamic Cache Templates report, which displays information about the cache
template data. A cache template is an object type defined by a cache policy
specified in WebSphere Application Server file cachespec.xml. A cache policy,
which is specified the caching rules and indicates what will be cached, the
invalidation and timeout conditions, and other data
240
ITCAM for Application Diagnostics: User Guide
Accessing the Cache Analysis workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems
or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Cache Analysis entry.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Client Communications workspace
This workspace provides overall Service Integration Bus communication
performance data and counters for all clients connected to this application server.
WebSphere Application Server 5.1 based products do not support this workspace.
This workspace displays data provided by the Client Communications attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Connection Count - History graph, which shows the number of API sessions
used by clients that were network connected to this application server
v Error Count - History graph, which shows the communication errors that
occurred and that resulted in the disconnection of a network connection to a
client
v Communication Statistics report, which displays information about client
communications, including API connections, errors, reads, writes, sent priority,
received priority, MessageSent priority, and MessageReceived priority
Accessing the Client Communications workspace
To access this workspace from the Platform Messaging workspace, use one of the
following procedures:
Chapter 4. ITCAM Agent for WebSphere
241
v Within the Navigator, right-click the Platform Messaging entry; then from the
pop-up menu, click Workspace > Client Communications.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Client Communications.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Container Object Pools workspace
This workspace displays aggregate information about the object pools associated
with Enterprise Java Beans (EJBs). It provides a view of pool performance for all
Enterprise Java Beans deployed to each container.
This workspace displays data provided by the Container Object Pools attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Object Pool Rates - History graphs, which show the retrieval, return, discard,
and drain rates for the EJBs in each EJB container
v Container Object Pools report, which displays:
– Aggregated information for each defined EJB container that aggregates bean
object pool performance for all Enterprise beans deployed to that container
– Aggregated information for the application server that aggregates bean object
pool performance data for all Enterprise beans deployed to the application
server
Accessing the Container Object Pools workspace
To access this workspace from the EJB Containers workspace, use one of the
following procedures:
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Container Object Pools.
v Within the Navigator, right-click the EJB Containers entry; then, from the
pop-up menu, click Workspace > Container Object Pools.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
242
ITCAM for Application Diagnostics: User Guide
Container Transactions workspace
This workspace displays data about the activities and transactions running in each
application server.
This workspace displays data provided by the Container Transactions attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Transaction Rates - History graph, which shows the per-second begin, commit,
and rollback rates over time for local and global transactions
v Transaction Durations - History graph, which shows the amount of time it takes
to complete local and global transactions
v Container Transactions report, which displays performance information for
global and local transactions that run in each defined EJB container and an
aggregated value for all transactions that run in the application server
Accessing the Container Transactions workspace
To access this workspace from the EJB Containers workspace, use one of the
following procedures:
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Container Transactions.
v Within the Navigator, right-click the EJB Containers entry; then, from the
pop-up menu, click Workspace > Container Transactions.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Data sources workspace
The data sources workspace displays statistical data for the data sources that your
applications reference when accessing databases.
This workspace displays data provided by the Datasources attributes.
The predefined workspace contains the following items:
v Worst Datasource Query Times bar chart, which shows the longest times (in
milliseconds) the application spent waiting to retrieve data from the database
during the specified interval
Chapter 4. ITCAM Agent for WebSphere
243
v Worst Datasource Update Times bar chart, which shows the longest times (in
milliseconds) the application spent updating data within the database during the
specified interval
v Datasources - Current Interval report, which displays database usage
information. For example, this report shows traffic information such as the time
the application spent trying to connect to the database and total and average
processing times for database queries and updates.
Accessing the Data sources workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Datasources entry.
Selected Data source - History workspace
The Selected Datasource - History workspace displays the historical information
that corresponds to the information in the Datasource workspace for a selected
data source. Historical information is collected over a specific time span. See the
online help for Tivoli Enterprise Portal for a detailed explanation of historical
reporting.
Accessing the Selected Data source - History workspace
To access this workspace from the Datasource workspace, use one of the following
procedures:
v From the Datasources - Current Interval report, right-click the link icon to the
left of any row; then, from the pop-up menu, click Selected Datasource History.
v From Worst Datasource Query Times bar chart or the Worst Datasource Update
Times bar chart, right-click any bar; then, from the pop-up menu, click Link To
> Selected Datasource - History.
Selected Data source - Datasource Trend workspace
The Datasources Trend workspace displays information about datasource
connections. This workspace displays data provided by the Datasources attributes.
This predefined workspace contains the following items:
v Current Datasources report displays datasource name, total wait time,
connection rate, connection average wait time and connection max wait time.
For TEMA running on z/OS, region ID can be found in the ASID column.
v Total Wait Time chart displays the total time that applications had to wait for a
connection to the data source.
244
ITCAM for Application Diagnostics: User Guide
v Connection Rate Trend chart displays the number of connection requests created
for the data source per second.
v Connection Average and Max Time Trend chart display the average time in
milliseconds and the worst-case time in milliseconds that applications had to
wait for a connection.
Accessing the Selected Data source - Datasource Trend
workspace
Right-click the Datasources workspace, select Workspace and then Datasource
Trend workspace
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
Datasources workspace
In the Tivoli Enterprise Portal, access the Datasources workspace. You can use the
Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
1. In the Datasources - Current Interval window, right click the choose link icon
then click Diagnostic Server Activity Display.
2. If this is your first time to access the Managing server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session. Click OK to display the Server Activity Display
page in the Managing Server Visualization engine. You can use this page to
diagnose application problems, for example, slow transactions or high response
times.
4. In a z/OS environment, right click the link icon on a row where the ASID
column displays Summary.
a. Click Selected Datasource- Servant Regions.
b. In the Selected Datasource - Servant Regions table, right click the link icon
on a row.
c. Click Diagnostic Server Activity Display.
5. For more information about the options available in a z/OS environment, refer
to “Region workspaces in a z/OS environment” on page 298 and “Accessing a
Region workspace” on page 300.
6. The results in this page relate directly to the context from where you launched
the link in the Tivoli Enterprise Portal. For more information about using the
Server Activity Display page, and additional features refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
7. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
Chapter 4. ITCAM Agent for WebSphere
245
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v
v
“Workspace link to Managing Server Visualization Engine” on page 225.
“Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
DB Connection Pools workspace
This workspace displays information about the database connection pools
associated with each application server.
You can use this workspace to monitor Java Database Connectivity (JDBC)
performance for WebSphere Application Server applications. This workspace
displays data provided by the DB Connection Pools attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of the high overhead, the Tivoli Enterprise Monitoring Agent provides
on demand sampling by default. To activate PMI monitoring, you must first
select this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Highest Average Pool Sizes bar chart, which shows the largest average size (that
is, number of connections) for each database connection pool
v Worst Wait Times bar chart, which shows the worst wait times (in milliseconds)
for each database connection pool
v Highest Allocation Rates bar chart, which shows the rate at which database
connections are being made for each connection pool
v DB Connection Pools report, which displays information about the database
connection pool for each defined data source. The report also displays an
aggregated value that aggregates over all data sources. For example, this report
displays the number of threads waiting for a connection and the number of
connections created and released
Accessing the DB Connection Pools workspace
To access this workspace, complete the following steps:
1. In the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or
UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server
entry of your choice.
246
ITCAM for Application Diagnostics: User Guide
5. Within that server list of available WebSphere Application Server workspaces,
click the DB Connection Pools entry.
Selected DB Connection Pool - History workspace
The Selected DB Connection Pool - History workspace displays historical
information that corresponds to the information in the DB Connection Pools
workspace for a selected connection pool. Historical information is collected over a
specific time span. See the online help for Tivoli Enterprise Portal for a detailed
explanation of historical reporting.
Accessing the Selected DB Connection Pool - History workspace
To access this workspace from the DB Connection Pools workspace, use one of the
following procedures:
v From the DB Connection Pools report, right-click the link icon to the left of any
row; then, from the pop-up menu, click Selected DB Connection Pool - History.
v From the Highest Average Pool Sizes bar chart, the Worst Wait Times bar chart,
or the Highest Allocation Rates bar chart, right-click any bar; then, from the
pop-up menu, click Link To > Selected DB Connection Pool - History.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
DB Connection Pools workspace
In the Tivoli Enterprise Portal access the DB Connection Pools workspace. You can
use the Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
1. In the DB Connection Pools window, right click the choose link icon
then click Diagnostic Server Activity Display.
2. If this is your first time to access the Managing Server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
4. Click OK to display the Server Activity Display page in the Managing Server
Visualization engine. You can use link to diagnose application problems, for
example, slow transactions or high response times.
5. The results relate directly to the context from where you launched the link in
the Tivoli Enterprise Portal. For more information about using the Server
Activity Display page and additional features, refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
6. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
Chapter 4. ITCAM Agent for WebSphere
247
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
DCS Stacks workspace
This workspace displays aggregated information about each DCS stack within the
entire WebSphere Application Server domain, including multiple nodes and
servers.
This workspace displays data provided by the DCS Stack attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Highest Message Buffer Reallocations bar chart, which displays the highest
number of message buffer reallocations that occurred as a result of inadequate
buffer size
v Most Sent Messages bar chart, which shows most frequent number of message
buffer reallocations that occurred as a result of inadequate buffer size
v High Severity Congestion Events bar chart, which shows the number of times
that a high severity congestion event for outgoing messages was raised
v DCS Statistics report, which displays information for the DCS stack data,
including incoming and outgoing message size, sent messages, and high severity
congestion events
Accessing the DCS Stacks workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the DCS Stacks entry.
248
ITCAM for Application Diagnostics: User Guide
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Destinations workspace
In this workspace, you can view performance data and counters for the
destinations of a selected messaging engine.
A destination is a virtual location within a service integration bus, to which
applications attach as producers, consumers, or both, to exchange messages. There
are two types of destinations, queues and topic spaces. WebSphere Application
Server 5.1 based products do not support this workspace. This workspace displays
data provided by both the Topic Spaces attributes and the Queue attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains:
v Queue report, which displays information about the queue data. A queue is a
destination for point-to-point messaging
v Topic Spaces report, which displays information about the topic space data. A
topic space is a destination for publish/subscribe messaging
Accessing the Destinations workspace
To access this workspace from the “Messaging Engines workspace” on page 264,
complete one of the following steps:
v From the Messaging Engines report, right-click the link icon to the left of any
row; then, from the pop-up menu, click Destinations.
v From Average Local Wait Time - History graph, Expired Messages - History
graph, Incomplete Topic Publications - History graph, or Total Published History graph, right-click any bar; then, from the pop-up menu, click Link To >
Destinations.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Durable Subscriptions workspace
In this workspace, you can view statistic counters for the durable subscriptions of
a selected topic.
Chapter 4. ITCAM Agent for WebSphere
249
The default messaging provider supports the use of durable subscriptions to
topics. This enables a subscriber to receive a copy of all messages published to a
topic, even messages published during periods of time when the subscriber is not
connected to the server. WebSphere Application Server 5.1 based products do not
support this workspace. This workspace displays data provided by the Durable
Subscriptions attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Durable Subscriptions report, which displays information about durable
subscriptions that pertain to a selected topic, including the number of messages
consumed, and message wait time
Accessing the Durable Subscriptions workspace
To access this workspace from the Destinations workspace, complete the following
step:
v From the Topic Spaces report, right-click the link icon to the left of any row;
then, from the pop-up menu, click Durable Subscriptions.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
EJB Containers workspace
This workspace displays aggregated information about each defined EJB.
This workspace displays aggregated bean performance data for all Enterprise
beans deployed to an EJB container. It also displays aggregated information for the
application server that aggregates bean performance data for all Enterprise beans
deployed on the application server. This workspace displays data provided by the
EJB Containers attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
250
ITCAM for Application Diagnostics: User Guide
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides
on-demand sampling by default. To activate PMI monitoring, you must first
select this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Method Average Response Time - History graph, which shows the average
response time for methods invoked by the EJBs in the container
v Method Invocation Rate - History graph, which shows the rate at which an EJB
container's methods were invoked
v EJB Containers report, which displays aggregated information for each defined
EJB container that aggregates bean performance data for all Enterprise beans
deployed to that container. The report also displays aggregated information for
the application server that aggregates bean performance data for all Enterprise
beans deployed to the application server. For example, this report displays load
values, response times, and lifecycle activities for Enterprise beans
Accessing the EJB Containers workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems
or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the EJB Containers entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
EJB Containers workspace
In The Tivoli Enterprise Portal access the EJB Containers workspace. You can use
the Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
then click
1. In the EJB Containers window, right click the choose link icon
Diagnostic Server Activity Display.
2. If this is your first time to access the Managing Server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
Chapter 4. ITCAM Agent for WebSphere
251
4. Click OK to display the Server Activity Display page in the Managing Server
Visualization engine. You can use link to diagnose application problems, for
example, slow transactions or high response times.
5. The results relate directly to the context from where you launched the link in
the Tivoli Enterprise Portal. For more information about using the Server
Activity Display page and additional features, refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
6. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
Enterprise Java Beans workspace
This workspace reports information about the each Enterprise Java Bean (EJB)
defined for an EJB container.
The workspace provides information about these beans that relates to their identity,
instrumentation level settings, creation and destruction of bean objects, response
times, invocations, calls, and rates for retrievals, returns, and discards. This
workspace displays data provided by the Enterprise Java Beans attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Worst Method Response Times bar chart, which shows the worst response times
(in milliseconds) for methods invoked by each bean instance
v Highest Method Invocation Rates bar chart, which shows the methods that are
invoked most often by each bean instance
v Enterprise Java Beans report, which shows performance information about each
EJB deployed to the application server. This report displays information about
bean activity, including the rates at which beans are being instantiated and
destroyed
252
ITCAM for Application Diagnostics: User Guide
Accessing the Enterprise Java Beans workspace
You access this workspace from the EJB Containers workspace. To list the EJBs for
all containers, use one of the following procedures:
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Enterprise Java Beans.
v Within the Navigator, right-click the EJB Containers entry; then, from the
pop-up menu, click Workspace > Enterprise Java Beans.
To see the EJBs referenced by a specific EJB container, complete the following step:
v From the EJB Containers report, right-click the link icon to the left of any row;
then, from the pop-up menu, click Enterprise Java Beans.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Garbage Collections - Selected Allocation Failure workspace
This workspace provides detailed information about the garbage-collection cycles
that occurred in response to a specific heap-allocation failure that occurred within
the Java Virtual Machine.
This workspace displays data provided by the Garbage Collection Cycle attributes.
Note to Solaris and HP-UX users: Allocation-failure information is not recorded on
these platforms. Consequently, this workspace is always empty.
The predefined workspace contains the following items:
v GC Elapsed Times bar chart, which breaks down the mark, sweep, and compact
times (in milliseconds) for each garbage-collection cycle that occurred for the
selected allocation failure
v Heap Usage bar chart, which displays the JVM's heap usage (kilobytes in use,
freed, and free at start of garbage collection) for each garbage-collection cycle
v Garbage Collections - Selected Allocation Failure report, which displays
information about a single garbage-collection cycle that the JVM hosting the
application server performed. For example, this report displays the free heap
space both before and after garbage collection, the heap space freed, and the
number of objects moved during garbage collection. For TEMA running on
z/OS, region ID can be found in the ASID column.
Accessing the Garbage Collections - Selected Allocation Failure
workspace
To access this workspace from the Allocation Failures workspace, use one of the
following procedures:
v From the Allocation Failures report, right-click the link icon to the left of any
row; then, from the pop-up menu, click Garbage Collections - Selected
Allocation Failure.
v From the Allocation Failure Elapsed Times bar chart or the Heap Usage History bar chart, right-click any bar; then, from the pop-up menu, click Link To
> Garbage Collections - Selected Allocation Failure.
For additional information, see:
Chapter 4. ITCAM Agent for WebSphere
253
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Garbage Collection Analysis workspace
This workspace summarizes all the Java Virtual Machine's (JVM) garbage-collector
activity over a user-defined interval.
The JVM generates detailed garbage collection logs for an application server when
started with the verbose:gc runtime parameter. This workspace displays data
provided by the Garbage Collection Analysis attributes.
The predefined workspace contains the following items:
v Garbage Collection Rate - History graph, which displays the rate at which the
garbage-collection algorithm is being invoked
v Heap Usage - History bar chart, which displays the high-water mark of free
storage (in kilobytes) available in the heap after each garbage-collector run
v Percentage of Time Garbage Collector Running - History graph, which displays
the percentage of real time the garbage collector was running during the current
interval, for each server region
v Garbage Collection Analysis report, which displays information about the
garbage-collection activities within the Java Virtual Machine that is hosting the
application server. For example, this report displays the number of times the
collector ran during the interval and the resulting number of objects that the
collector freed
Accessing the Garbage Collection Analysis workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the name of the
node you want to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Garbage Collection Analysis entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
Garbage Collection Analysis workspace
In the Tivoli Enterprise Portal navigate to the Garbage Collection Analysis
workspace. You can use the Diagnostic Server Activity Display link to access the
Managing Server Visualization Engine. For information about access requirements
see “Prerequisites for access” on page 226.
1. In the Garbage Collection Analysis window, right click the choose link icon
then click Diagnostic Memory Leak.
254
ITCAM for Application Diagnostics: User Guide
2. If this is the first time you access the Managing Server Visualization Engine
you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
4. Click OK to display the Memory Leak Confirmation report page in the
Managing Server Visualization Engine. You can use this page to diagnose
memory leak problems.
5. In a z/OS environment, right click the link icon on a row where the ASID
column displays Summary.
a. Click Garbage Collection Analysis Servant Regions.
b. In the Garbage Collection Analysis - Servant Regions table, right click the
link icon on a row.
c. Click Diagnostic Memory Leak.
For information about Creating a Memory Leak Confirmation report in this
page, and additional features refer to the Composite Application Manager help
within the Managing Server Visualization Engine Interface.
7. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
6.
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v
v
“Workspace link to Managing Server Visualization Engine” on page 225.
“Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
High Availability Manager workspace
The High Availability Manager workspace provides aggregated information about
high availability managers.
This workspace displays data provided by the High Availability Manager
attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set the
Resource Data Collection Method configuration value to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Local Group - History graph, which shows the number of local groups.
Chapter 4. ITCAM Agent for WebSphere
255
v Group State Rebuild Time - History graph, which shows the time taken to
rebuild the global group state in milliseconds.
v High Availability Manager report, which displays information about the high
availability manager, including group state rebuild time, bulletin-board subjects,
bulletin-board subscriptions, bulletin-board rebuild time, and local bulletin-board
subjects
Accessing the High Availability Manager workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the note you want to
select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the High Availability Manager entry.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
IMAP/POP workspace
This workspace provides aggregated statistics of the usage information about the
IMAP service and the POP3 service connectivity, especially for the
performance-related connectivity.
This workspace displays data provided by the Workplace Mail IMAP/POP
attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support the IMAP/POP workspace: configuration and links to the Managing
Server Visualization Engine from the Tivoli Enterprise Portal.
The predefined workspace contains the following items:
v Active Sessions bar chart, which displays the number of active sessions during
the sampling interval
256
ITCAM for Application Diagnostics: User Guide
v Authentication Failures bar chart, which displays the number of authentications
failures during the sampling interval
v Workplace Mail report, which displays detailed information about the workplace
mail for each protocol
Accessing the IMAP/POP workspace
To access this workspace from the Workplace Mail workspace, use one of the
following procedures:
v Within the Navigator, right-click the Workplace Mail entry; then from the
pop-up menu, click Workspace > IMAP/POP.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
IMAP/POP.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
J2C Connection Pools workspace
This workspace reports information about resource adapters and connectors that
adhere to J2C, the WebSphere Application Server implementation of the J2EE
Connector Architecture (JCA).
Data counters for this category contain usage information about the J2C connection
pools that enable enterprise beans to connect to and interact with systems such as
the Customer Information Control System (CICS) and the Information
Management System (IMS). This workspace displays data provided by the J2C
Connection Pools attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Highest Average Pool Sizes bar chart, which shows the largest average number
of managed connections for each J2C connection pool. The Y-axis headings
correspond to the row number of the J2C Connection Pools report
v Worst Wait Times bar chart, which shows the worst wait time (in milliseconds)
for each of the J2C connection pools. The y-axis headings correspond to the row
number of the J2C Connection Pools report
v Highest Allocation Rates bar chart, which displays the highest
managed-connection creation, destruction, and allocation rates (in events per
second)
Chapter 4. ITCAM Agent for WebSphere
257
v J2C Connection Pools report, which displays information about connectors that
adhere to J2C. For example, this report displays the number of managed
connections or physical connections and the total number of connections or
connection handles
Accessing the J2C Connection Pools workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the J2C Connection Pools entry.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
J2C Connection Pools workspace
In The Tivoli Enterprise Portal access the J2C connection pools workspace. You can
use the Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
1. In the J2C connection pools window, right click the choose link icon
then click Diagnostic Server Activity Display.
2. If this is your first time to access the Managing Server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
4. Click OK to display the Server Activity Display page in the Managing Server
Visualization engine. You can use link to diagnose application problems, for
example, slow transactions or high response times.
5. The results relate directly to the context from where you launched the link in
the Tivoli Enterprise Portal. For more information about using the Server
Activity Display page and additional features, refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
6. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
258
ITCAM for Application Diagnostics: User Guide
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
JMS Summary workspace
The JMS Summary workspace displays information about queues being used by
your applications using the Java Message Service (JMS) interface.
The JMS Summary workspace also provides information about how WebSphere
Application Server applications are using WebSphere MQ. It displays such
information as the number of messages read and written and which queue
managers and queues were used during the interval.
This workspace displays data provided by the JMS Summary attributes.
The predefined workspace contains the following items:
v Worst JMS Send Times bar chart, which displays the longest times (in
milliseconds) your application spent putting messages onto a queue during the
interval
v Worst JMS Receive Times bar chart, which displays the longest times (in
milliseconds) your application spent getting messages from a queue during the
interval
v Worst JMS Browse Times bar chart, which displays the longest times (in
milliseconds) your application spent browsing messages on a queue during the
interval
v JMS Summary - Current Interval report, which displays detailed information
about how the WebSphere Application Server uses messaging middleware (that
is, WebSphere MQ) using JMS. Details include the send, receive, browse, and
publish times for your application. It also includes such information as, which
queue managers and queues are being used and how many messages are being
read and written
Accessing the JMS Summary workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the JMS Summary entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
259
Accessing the Managing Server Visualization Engine from the
JMS Summary workspace
In The Tivoli Enterprise Portal access the JMS Summary workspace. You can use
the Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
1. In the JMS Summary - Current interval window, right click the choose link
then click Diagnostic Server Activity Display.
icon
2. If this is your first time to access the Managing Server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
4. Click OK to display the Server Activity Display page in the Managing Server
Visualization engine. You can use this link to diagnose application problems,
for example, slow transactions or high response times.
5. In a z/OS environment, right click the link icon on a row where the ASID
column displays Summary.
a. Click Selected JMS - Servant Regions.
b. In the Selected JMS - Servant Regions table, right click the link icon on a
row.
c. Click Diagnostic Server Activity Display.
6. For more information about the options available in a z/OS environment, refer
to “Region workspaces in a z/OS environment” on page 298 and “Accessing a
Region workspace” on page 300.
7. The results in this page relate directly to the context from where you launched
the link in the Tivoli Enterprise Portal. For more information about using the
Server Activity Display page, and additional features refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
8. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225.
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
JVM Stack Trend workspace
This workspace displays trend data regarding JVM CPU usage, JVM garbage
collection, and JVM heap usage.
This workspace displays data provided by the Application Server and Garbage
Collection Analysis attribute groups.
The predefined workspace contains:
260
ITCAM for Application Diagnostics: User Guide
v JVM CPU Trend chart indicates the percentage of the JVM CPU used.
v Percent GC Time Used chart
v Heap Usage Trend chart
Accessing the Selected Application - Configuration workspace
Access this workspace using one of the following methods:
v Double click the JVM icon in Resources workspace.
v Right click the JVM icon in the Resources workspace and select Link To, then
select JVM Stack Trend.
For additional information see:
v Resources and Applications workspaces
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Log Analysis workspace
This workspace reports application server error and exception conditions as
recorded in the application server's log file.
This workspace displays data provided by both the Log Analysis attributes and
DC Messages attributes.
The predefined workspace contains the following items:
v DC Message Events, which displays aggregated information about the messages
from WebSphere Data Collector
v Log Analysis report, which displays application server error and exception
conditions as recorded in the application server log file, SystemOut.log. This
information includes the exception severity as well as the ID and text of the
associated message. In the Log Analysis report, if the PID value is displayed as
-1, it indicates that the data collector is disconnected. If a WebSphere server
shutdown occurs the connection between the data collector and TEMA is closed
but the data collector continues to write to log files and TEMA processes these
records but sets the PID value to -1.
Accessing the Log Analysis workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Log Analysis entry.
For additional information, see:
v Organization of the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
261
v
Attribute groups used by the predefined workspaces
Lotus Workplace Server workspace
The Lotus Workplace Server workspace displays overall statistics for each
application server being monitored by the Tivoli Enterprise Monitoring Agent.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support Lotus Workplace Server: configuration and links to the Managing Server
Visualization Engine from the Tivoli Enterprise Portal.
The predefined workspace contains the following items:
v Heap Usage - History bar chart, which displays free memory size and used
memory size (in kilo bytes) within the WebSphere Application Server's heap
over time. The chart's flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
v Response Time - History graph, which shows the server response time to
requests over time
This view displays data provided by the Request Times and Rates attributes.
v Request Rate - History graph, which shows the rate at which requests have been
received by this server over time
This view displays data provided by the Request Times and Rates attributes.
v Percent CPU Used - History graph, which shows the percentage of the CPU that
this server consumed over time
This view displays data provided by the Application Server attributes.
v Application Server Summary report, which displays overall information about
this WebSphere application server, including JVM statistics and CPU usage
statistics
This view displays data provided by the Application Server attributes.
Accessing the Lotus Workplace Server workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, or UNIX
Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, click the Lotus Workplace Server entry of
your choice.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Messages Queues workspace
This workspace provides aggregated statistics about the usage information about
the message delivery.
This workspace displays data provided by the Workplace Mail Queues attributes.
262
ITCAM for Application Diagnostics: User Guide
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support the Messages Queues workspace: configuration and links to the Managing
Server Visualization Engine from the Tivoli Enterprise Portal.
The predefined workspace contains the following items:
v Queue Messages bar chart, which displays the number of message in the ready,
retry, unprocessed, and dead state in the queue during the sampling interval
v Workplace Mail Message Queues report, which displays detailed information
about the state of messages in each queue
Accessing the Messages Queues workspace
To access this workspace from the Workplace Mail workspace, use one of the
following procedures:
v Within the Navigator, right-click the Workplace Mail entry; then from the
pop-up menu, click Workspace > Messages Queues.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Messages Queues.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Messaging Engine Communications workspace
This workspace provides aggregated counter statistics for all the messaging
engines being hosted by the current application server. WebSphere Application
Server 5.1 based products do not support this workspace.
This workspace displays data provided by the Messaging Engine Communications
attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
Chapter 4. ITCAM Agent for WebSphere
263
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Situation Event Console report, which shows the event activity for situations
associated with the current Navigator item and any items within the branch. The
Navigator alerts you when a situation becomes true by overlaying the Navigator
item with an event indicator. This report is useful when multiple alerts are
raised and you might not know newly arrived alerts just by looking at the
indicator.
v Messaging Engine Communications report, which displays information about
the messaging engine communications, including API connections, errors, reads,
writes, message written and message read.
Accessing the Messaging Engine Communications workspace
To access this workspace from the Platform Messaging workspace, use one of the
following procedures:
v Within the Navigator, right-click the Platform Messaging entry; then, from the
pop-up menu, click Workspace > Messaging Engine Communications.
v From the primary Tivoli Enterprise Portal menu, click View >Workspace >
Messaging Engine Communications.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Messaging Engines workspace
In this workspace, you can view of performance counters of the Messaging
Engines supported by a server. WebSphere Application Server 5.1 based products
do not support this workspace.
This workspace displays data provided by the Messaging Engines attributes.
Note:
v This workspace reports zeros for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Average Local Wait Time - History graph, which shows the historical time spent
by messages on this durable subscription on consumption
264
ITCAM for Application Diagnostics: User Guide
v Expired Messages - History graph, which shows the number of report-enabled
messages that expired while on this queue
v Incomplete Topic Publications - History graph, which shows the number of
publications not yet received by all historical subscribers.
v Total Published - History graph, which shows the historical number of
publications to the message engines
v Messaging Engines report, which displays the aggregated information about
each messaging engine. A messaging engine is a server component that provides
the core messaging functionality of a service integration bus. A messaging
engine manages bus resources and provides a connection point for applications
Accessing the Messaging Engines workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Platform Messaging entry.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
OS Stack workspace
This workspace displays information about the operating system performance.
This workspace displays data provided by the Application Server attribute group.
The predefined workspace contains:
v Current OS Stack Summary report which displays:
– Server name
– Platform CPU Used (ms)
– System Paging
Note: The feature Platform CPU Used (ms) does not apply the z/OS platform.
v CPU Used chart
v System Paging chart
Accessing the Selected Application - Configuration workspace
Access this workspace using one of the following methods:
v Double click the OS icon in Resources workspace.
v Right click the OS icon in the Resources workspace and select Link To, then
select OS Stack Trend.
Chapter 4. ITCAM Agent for WebSphere
265
For additional information see:
v Resources and Applications workspaces
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Pool Analysis workspace
This workspace displays information about the usage of several types of pools
associated with each application server, including Web container pools, ORB pools,
J2C connection pools, and database connection pools. This workspace helps you
detect resource constraints and potential performance congestion.
Note:
v This workspace reports zeros for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Web Container Pool Usage - History graph, which shows the configured
maximum number of Web container pooled threads and the average active
threads in the Web container pool
This view displays data provided by the Thread Pools attributes.
v ORB Pool Usage - History graph, which shows the configured maximum
number of ORB pooled threads and the average active threads in the ORB pool
This view displays data provided by the Thread Pools attributes.
v Web Container Pool % at Max - History bar chart, which shows the maximum
usage percentage for the Web container's pooled threads over time
This view displays data provided by the Thread Pools attributes.
v ORB Pool % at Max - History bar chart, which shows the maximum usage
percentage for the ORB's pooled threads over time
This view displays data provided by the Thread Pools attributes.
v Percent CPU Used - History graph, which shows the percentage of the CPU
used over time
This view displays data provided by the Application Server attributes.
v DB Connection % at Max - Current Interval bar chart, which shows the
maximum usage percentage for a database connection pool over time
This view displays data provided by the DB Connection Pools attributes.
v J2C Connection % at Max - Current® Interval bar chart, which shows the
maximum usage percentage for a J2C connection pool over time
This view displays data provided by the J2C Connection Pools attributes.
Accessing the Pool Analysis workspace
To access this workspace, complete the following steps:
266
ITCAM for Application Diagnostics: User Guide
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Pool Analysis entry.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Portal Pages Summary workspace
This workspace reports performances statistics about WebSphere Portal page
response times completed on the interval. A historical version of this workspace
provides a long-term view of a single portal page that you select.
The following workspace displays only if the request monitoring control level,
monitoring level is set to Level2. For more information about the request
monitoring control level, see “Application Dashboard (Basic) tab” on page 224.
This workspace displays data provided by the Portal Page Summary attributes.
The predefined workspace contains the following items:
v Worst Response Times bar chart, which displays the worst average response
times (in milliseconds) for portlet during the current interval
v Most Popular Portal Pages bar chart, which shows the number of requests for
portlet
v Portal Pages report, which displays aggregated information about portal pages,
including average response time and request count
Accessing the Portal Pages Summary workspace
To access this workspace from the Portal Summary workspace, use one of the
following procedures:
v Within the Navigator, right-click the Portal Summary entry; then, from the
pop-up menu, click Workspace > Portal Pages Summary.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Portal Pages Summary.
Selected Portal Page - History workspace
The Selected Portal Page - History workspace displays the historical information
that corresponds to the information in the Portal Pages Summary workspace for a
selected portal page. Historical information is collected over a specific time span.
See the online help for Tivoli Enterprise Portal for a detailed explanation of
historical reporting.
Chapter 4. ITCAM Agent for WebSphere
267
Accessing the Selected Portal Page - History workspace
To access this workspace from the Portal Pages Summary workspace, use one of
the following procedures:
v From the Portal Pages report, right-click the link icon to the left of any row;
then, from the pop-up menu, click Selected Portal Page - History.
v From the Worst Response Times bar chart, or the Most Popular Portal Pages bar
chart, right-click any bar; then, from the pop-up menu, click Link To > Selected
Portal Page - History.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Portal Summary workspace
The workspace reports summarized statistics about response times and functional
decomposition of additional requests collected for WebSphere Portal applications.
These include statistics about Portal Pages/Gateway Servlet aggregated response
times collected on the interval, and more find grained statistics about Portlet,
Model Building, Page Loading, Authentication and Authorization requests
response times collected on the same interval. By default, this workspace is
configured for long-term historical interval reporting.
The following workspace displays only if the request monitoring control level,
monitoring level is set to Level2. For more information about the request
monitoring control level, see “Application Dashboard (Basic) tab” on page 224.
This workspace displays data provided by the Portal Summary attributes.
The predefined workspace contains the following items:
v Portal Pages/Gateway Servlet - History graph, which shows the historical
average response time (in milliseconds) of portal pages/Gateway Servlet
v Portlet - History graph, which shows the historical average response time (in
milliseconds) of portlets
v Model Building - History graph, which shows the historical response time (in
milliseconds) of model building
v Page Loading - History graph, which shows the historical response time (in
milliseconds) of page loading
v Authentication - History graph, which shows the historical response time (in
milliseconds) of authentication
v Authorization - History graph, which shows the historical response time (in
Milliseconds) of authorization
Accessing the Portal Summary workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
268
ITCAM for Application Diagnostics: User Guide
4. Within the list of available agents, expand the WebSphere Portal server of your
choice.
5. Within that server list of available WebSphere Portal Server workspaces, click
the Portal Summary entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Portlet Summary workspace
This workspace reports performances statistics about WebSphere Portal portlet
response times completed on the interval.
The following workspace displays only if the request monitoring control level,
monitoring level is set to Level2. For more information about the request
monitoring control level, see “Application Dashboard (Basic) tab” on page 224.
A historical version of this workspace provides a long-term view of a single portlet
that you select. This workspace displays data provided by the Portlet Summary
attributes.
The predefined workspace contains the following items:
v Worst Response Times bar chart, which displays the worst average response
times (in milliseconds) for portlet in the current interval
v Most Popular Portlets bar chart, which shows the exception and request rates (in
events per second) for portlet
v Portlets report, which displays aggregated information about portlets, including
average response time, request count and request rate
Accessing the Portlet Summary workspace
To access this workspace from the Portal Summary workspace, use one of the
following procedures:
v Within the Navigator, right-click the Portal Summary entry; then, from the
pop-up menu, click Workspace > Portlet Summary.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Portlet Summary.
Selected Portlet - History workspace
The Selected Portlet - History workspace displays the historical information that
corresponds to the information in the Portal Summary workspace for a selected
portlet. Historical information is collected over a particular measured time span.
See the online help for Tivoli Enterprise Portal for a detailed explanation of
historical reporting.
Accessing the Selected Portlet - History workspace
To access this workspace from the Portlet Summary workspace, use one of the
following procedures:
v From the Portlets report, right-click the link icon to the left of any row; then,
from the pop-up menu, click Selected Portlet - History.
Chapter 4. ITCAM Agent for WebSphere
269
v From the Worst Response Time bar chart, or the Most Popular Portlets bar chart,
right-click any bar; then, from the pop-up menu, click Link To > Selected
Portlet - History.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Request Analysis workspace
The workspace reports response times and functional decomposition information
about requests (including servlets, JSPs, and EJB methods) that completed during
the interval.
A historical version of this workspace provides a long-term view of a single
request that you select. This workspace displays data provided by the Request
Analysis attributes.
The predefined workspace contains the following items:
v Worst Average Response Times bar chart, which displays the five worst response
times for requests processed during the current interval
v Worst Completion Rates bar chart, which displays the 10 requests that have the
worst completion rates
v Requests - Current Interval report, which displays detailed information about
the response times recorded for each request
Accessing the Request Analysis workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Request Analysis entry.
Selected Request - History workspace
The Selected Request - History workspace displays the historical information that
corresponds to the information in the Request Analysis workspace for a single
request type that you select. Historical information is collected over a specific time
span. See the online help for Tivoli Enterprise Portal for a detailed explanation of
historical reporting.
Accessing the Selected Request - History workspace
To access this workspace from the Request Analysis workspace, use one of the
following procedures:
v From the Requests - Current Interval report, right-click the link icon to the left of
any row; then, from the pop-up menu, click Selected Request - History.
270
ITCAM for Application Diagnostics: User Guide
v From the Worst Average Response Times bar chart, right-click any bar; then,
from the pop-up menu, click Link To > Selected Request - History.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
The following workspaces display only if the request monitoring control level,
monitoring level is set to Level2. For more information about the request
monitoring control level, see “Application Dashboard (Basic) tab” on page 224.
v Selected Request - Datasource
v Selected Request - JMS Queues
v Selected Request - Resource Adapters
Accessing the Managing Server Visualization Engine from the
Request Analysis workspace
In the Tivoli Enterprise Portal access the request analysis workspace see “Accessing
the Request Analysis workspace” on page 270. You can use you can use the
following links to access the Managing Server Visualization Engine.
v Diagnostic Recent Completed Requests
v Diagnostic In-flight Request Search
v Diagnostic SMF Data (This option is only available if the Tivoli Enterprise
Portal is connected to a z/OS data controller.)
For information about access requirements, see “Prerequisites for access” on page
226.
1. In the Requests - Current Interval window, right click the choose link icon
then click one of the following options:
v Diagnostic Recent Completed Requests
v Diagnostic In-flight Request Search
2. To view Diagnostic Recent Completed Requests or Diagnostic In-flight Request
Search in a z/OS environment, right click the link icon on a row where the
ASID column displays Summary.
a. Click Selected Request Servant Regions .
b. In the Selected Requests - Servant Regions Current Interval table, right
click the link icon on a row.
c. Click Diagnostic Recent Completed Requests or Diagnostic In-flight
Request Search.
3. To view Diagnostic SMF Data (z/OS data collector only) right click the link
icon on a row where the ASID column displays Summary.
a. Click Selected Request Servant Regions.
b. In the Selected Requests - Servant Regions Current Interval table, right
click the link icon on a row.
c. Click Diagnostic SMF.
For information about the options available in a z/OS environment, refer to
“Region workspaces in a z/OS environment” on page 298 and “Accessing a
Region workspace” on page 300
4. If this is your first time to access the Managing Server Visualization Engine
during the session you see a Welcome to the Application Monitor page.
Chapter 4. ITCAM Agent for WebSphere
271
5. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
6. Click OK to display the relevant page in the Managing Server Visualization
Engine.
v If you click Diagnostic Recent Completed Requests you see the Server
Activity Display page.
v If you click Diagnostic In-flight Request Search you see the In-Flight
Request Search page.
v If you click Diagnostic SMF Data you see the SMF Overview page.
7. The information in these pages relates directly to the context from where you
launched the link in the Tivoli Enterprise Portal.
8. To return to the Tivoli Enterprise Portal interface at any time click back on your
web browser.
For additional information, see:
v
v
“Workspace link to Managing Server Visualization Engine” on page 225.
“Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
Request Baseline workspace
This workspace displays aggregated information about the request baseline.
The baselining collects statistical information about an application requests
completion times and uses this information to assign fair and bad thresholds on
the application requests. The product divides the whole request response times
into buckets and collects individual hits into each bucket. Use these attributes to
get statistics from individual requests collected during baselining interval.
This workspace displays data provided by the Baseline attributes.
The predefined workspace contains:
v Baseline Data report, which shows lower and upper boundaries for each bucket
request as well as the breakdown of nested request types in percentage.
v Request Label report, which shows the monitoring configuration settings for
selected requests, including auto-threshold settings and actual thresholds
calculated from the baseline data.
v Nested Delays Distribution bar chart, which displays a bar for each bucket of
response times across the different nested types (JDBC, JCA, JMS, etc.). This
chart provides you with additional hints and insight about how to interpret
response times distribution displayed in the distribution chart.
v Response Time Distribution bar chart, which displays the distribution of the
servlet response times on the baselining interval, also called zones.
You can use the bar charts to customize automatic request time thresholds. See
“Enable_Auto_Threshold: set threshold parameters” on page 445.
Accessing the Request Baseline workspace
Complete the following steps to access this workspace from the Application
Registry:
272
ITCAM for Application Diagnostics: User Guide
1. Click Application Configuration report.
2. Right click the link icon to the left of any row to display a pop-up menu.
3. Click Request Baseline.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
EJB Tier Analysis workspace
The workspace displays detailed information about application tier health for a
selected WebSphere application.
The application tier health is derived from the following performance statistics:
v Calculated application request delays in EJB container or custom requests delays
compared against corresponding thresholds assigned in application
configuration.
v Completion rates for application edge EJB requests.
v Application server ORB thread pool utilization level.
v PMI statistics for application EJB container transactions begin, commit, and
rollback rates.
This workspace displays data provided by the Application Health Status attributes.
The predefined workspace contains:
v Application Tier Analysis report, which shows the overall health status of the
Application tier for a selected application. For TEMA running on z/OS, region
ID can be found in the ASID column.
v Container Pool Usage bar chart, which displays the average number of
concurrently active threads and the average number of free threads in the pool.
This view displays data provided by the Thread Pools attributes.
v Worst Application Tier Delays - Top 10 bar chart, which displays the top ten
delayed requests in the application tier. This view displays data provided by the
Request Analysis attributes.
v Worst Application Tier Completion Rates - Top 10 bar chart, which displays the
top ten worst requests in the application tier. This view displays data provided
by the Request Analysis attributes.
v Container Transactions bar chart, which displays the counts of global and local
transactions that were started, committed, and undone during the interval. This
view displays data provided by the Container Transactions attributes.
v JVM Health - CPU Used % graph, which displays the percentage of the CPU
used by the Java Virtual Machine (JVM) during the interval. This view displays
data provided by the Application Server attributes.
v JVM Health - Heap Used % graph, which displays the current heap usage for
the monitored JVM. This view displays data provided by the Garbage Collection
Analysis attributes.
v JVM Health - GC Time % graph, which displays the percentage of real time that
the garbage collector was active during the interval. This view displays data
provided by the Garbage Collection Analysis attributes.
Chapter 4. ITCAM Agent for WebSphere
273
Accessing the EJB Tier Analysis workspace
To access this workspace from the Application Health Summary workspace, use
the following procedures:
v From the Application Health Summary report, right-click the link icon to the left
of any row; then, from the pop-up menu, click EJB Tier Analysis.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Configuration workspace
This workspace displays the information about the configuration details of the
selected application.
The workspace contains information about application requests and the
corresponding thresholds assigned to them, as well as about status and
configuration for application baselining activity. An entry is created for each
application in the configuration report when a WebSphere application is discovered
by the monitoring agent. The data is also stored in a context file local to
monitoring agent where it can persist between monitoring agent restarts.
This workspace displays data provided by the Application Monitoring
Configuration attributes.
The predefined workspace contains:
v Longest Request Thresholds - Top 10 bar chart, which displays the ten longest
(in time) request thresholds configured for the given application (Servlet/JSP
URL or EJB class/method call).
v Application Requests report, which shows the discovered application requests
and thresholds assigned to them. Click the link in the Application Request
Configuration report or right-click and select Selected Request - Baseline to go to
the Request Baseline Workspace. The link to the Selected Request - Baseline is
disabled when the baseline request count is less than or equal to 0.
v Application report, which shows the common details about application
configuration, including custom requests monitoring levels for application and
current baselining status.
Accessing the Application Configuration workspace
To access this workspace from the Application Health Summary workspace, use
the following procedures:
v From the Application Health Summary report, right-click the link icon to the left
of any row; then, from the pop-up menu, click Application Configuration.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Backend Tier Analysis workspace
This workspace displays the information about the details of the backend tier for a
selected application.
274
ITCAM for Application Diagnostics: User Guide
This workspace displays data provided by the Application Health Status attributes.
The predefined workspace contains:
v Backend Tier Analysis report, which shows he overall health status of the
backend tier for a selected application. For TEMA running on z/OS, region ID
can be found in the ASID column.
v Worst Backend Tier Delays - Top 10 bar chart, which displays the top ten
delayed requests in the backend tier. This view displays data provided by the
Request Analysis attributes.
v Most Used Datasources - Top 10 bar chart, which displays the average time per
request used by queries and updates to the data source. This view displays data
provided by the Datasources attributes.
v Most Used JMS Resources - Top 10 bar chart, which displays the longest times
your application spent in getting messages from a queue, putting messages onto
a queue, publishing messages to a queue, or browsing messages on a queue
during the interval. This view displays data provided by the JMS Summary
attributes.
v Most Used JDBC Pools - Top 10 bar chart, which displays the average
percentage of the connection pool in use during the interval. This view displays
data provided by the DB Connection Pools attributes.
v Most Used JCA Pools - Top 10 bar chart, which displays the average percent of
the pool that is in use for the interval. This view displays data provided by the
J2C Connection Pools attributes.
v JVM Health - CPU Used % graph, which displays the percentage of the CPU
used by the Java Virtual Machine (JVM) during the interval. This view displays
data provided by the Application Server attributes.
v JVM Health - Heap Used % graph, which displays the current heap usage for
the monitored JVM. This view displays data provided by the Garbage Collection
Analysis attributes.
v JVM Health - GC Time % graph, which displays the percentage of real time that
the garbage collector was active during the interval. This view displays data
provided by the Garbage Collection Analysis attributes.
Accessing the Backend Tier Analysis workspace
To access this workspace from the Application Health Summary workspace, use
the following procedures:
v From the Application Health Summary report, right-click the link icon to the left
of any row; then, from the pop-up menu, click Backend Tier Analysis.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Health History workspace
The workspace displays the information about the historical health status of a
selected application. By default, the history data is collected for the last 24 hours.
The workspace displays data provided by the Application Health Status attributes.
The predefined workspace contains:
Chapter 4. ITCAM Agent for WebSphere
275
v Availability/Throughput - History graph, which displays average request
processing rate by application over the time. This view displays data provided
by the Request Times and Rates attributes.
v Availability/Completion Rate - History graph, which displays the average
request completion rate by application over the time; Completion rate is defined
as ratio of successfully completed requests count to the total count of requests
processed by application on the interval. This view displays data provided by
the Request Times and Rates attributes.
v Availability/Average Load- History graph, which displays the average number
of concurrent application requests over the time. This view displays data
provided by the Request Times and Rates attributes.
v Response Time - History graph, which displays the average application response
time over the time. This view displays data provided by the Request Times and
Rates attributes.
v Server Resources/CPU Used - History graph, which displays the percent of CPU
time used by the application JVM process over the time. This view displays data
provided by the Application Server attributes.
v Server Resources/Paging Rate - History graph, which displays the system
paging rate in kilobytes per second over the time. This view displays data
provided by the Application Server attributes.
v Server Resources/GC Active Time - History graph, which displays the
percentage of total CPU time for which the garbage collector was active over the
time. This view displays data provided by the Garbage Collection Analysis
attributes.
Accessing the Application Health History workspace
Complete the following steps to access this workspace from the Application Health
Summary:
1. Click Application Health Summary report.
2. Right-click the link icon to the left of any row to display the pop-up menu.
3. Click Application Health history.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Web Tier Analysis workspace
This workspace displays detailed information about the client tier health for a
selected WebSphere application.
The client tier health indicator is derived from the following performance statistics:
v Calculated application request delays inside Servlet/JSP or Portal container
compared against corresponding thresholds assigned in application
configuration.
v Completion rates for edge Servlet/JSP and Portal application requests.
v Application server WebContainer thread pool utilization level.
v PMI statistics for HTTP session counts by application.
This workspace displays data provided by the Application Health Status attributes.
The predefined workspace contains:
276
ITCAM for Application Diagnostics: User Guide
v Client Tier Analysis report, which shows the overall health status of application
execution in Web or portal containers. For TEMA running on z/OS, region ID
can be found in the ASID column.
v Web Contain bar chart, which displays the current utilization level of the Web
Container thread pool. This view displays data provided by the Thread Pools
attributes.
v HTTP Sessions bar chart, which displays the average number of concurrently
active and live HTTP session numbers for the selected application during the
interval. This view displays data provided by the Servlet Sessions attributes.
v Worst Client Tier Delays - Top 10 bar chart, which displays the top ten requests
with biggest delays (threshold violations) in the client tier. This view displays
data provided by the Request Analysis attributes.
v Worst Client Tier Completion Rates - Top 10 bar chart, which displays the top
ten Servlet/JSP/Portal edge requests with the worst completion rates. This view
displays data provided by the Request Analysis attributes.
v JVM Health - CPU Used % graph, which displays the percentage of the CPU
used by the Java Virtual Machine (JVM) during the interval. This view displays
data provided by the Application Server attributes.
v JVM Health - Heap Used % graph, which displays the current heap usage for
the monitored JVM. This view displays data provided by the Garbage Collection
Analysis attributes.
v JVM Health - GC Time % graph, which displays the percentage of real time that
the garbage collector was active during the interval. This view displays data
provided by the Garbage Collection Analysis attributes.
Accessing the Web Tier Analysis workspace
Complete the following steps to access this workspace from the Application Health
Summary:
1. Click Application Health Summary report.
2. Right-click the link icon to the left of any row to display the pop-up menu.
3. Click Web Tier Analysis.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Selected Datasources - Datasource Trend workspace
The Datasources Trend workspace displays information about datasource
connections.
This workspace displays data provided by the Datasources attributes.
The predefined workspace contains the following items:
v Current Datasources report displays datasource name, total wait time,
connection rate, connection average wait time and connection max wait time.
v Total Wait Time Trend line chart displays the total time that applications had to
wait for a connection to the data source.
v Connection Rate Trend bar chart displays the number of connection requests
(per second) created for the data source.
Chapter 4. ITCAM Agent for WebSphere
277
v Connection Average and Max Time Trend line chart displays the average time
(in milliseconds) and the worst-case time (in milliseconds) that applications had
to wait for a connection.
Selected Request - Data sources workspace
The Selected Request - Data sources workspace displays information about JDBC
activity performed by the request you selected in the primary Request Analysis
workspace.
This workspace displays data provided by the Selected Request attributes.
The predefined workspace contains the following items:
v Worst Datasources Response Times bar chart, which shows the worst response
times (in milliseconds) for data sources accessed by this request
v Selected Request - Datasources report, which displays detailed information about
the data sources accessed for the selected request. For TEMA running on z/OS,
region ID can be found in the ASID column.
Accessing the Selected Request - Data sources workspace
To access this workspace from the Request Analysis workspace, use one of the
following procedures:
v From the Requests - Current Interval report, right-click the link icon to the left of
any row; then, from the pop-up menu, click Selected Request - Datasources.
v From Worst Average Response Times bar chart, right-click any bar; then, from
the pop-up menu, click Link To > Selected Request - Datasources.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Selected Request - JMS Queues workspace
The Selected Request - JMS Queues workspace displays information about message
queues owned by messaging middleware and accessed by the request that you
selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
The predefined workspace contains the following items:
v Worst JMS Queues Response Times bar chart, which shows the worst response
times (in milliseconds) for JMS resources accessed by this request
v Selected Request - JMS Queues report, which displays detailed information
about the JMS resources accessed by the selected request. For TEMA running on
z/OS, region ID can be found in the ASID column.
Accessing the Selected Request - JMS Queues workspace
To access this workspace from the Request Analysis workspace, use one of the
following procedures:
v From the Requests - Current Interval report, right-click the link icon to the left of
any row; then, from the pop-up menu, click Selected Request - JMS Queues.
278
ITCAM for Application Diagnostics: User Guide
v From Worst Average Response Times bar chart, right-click any bar; then, from
the pop-up menu, click Link To > Selected Request - JMS Queues.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Selected Request - Portal Processing workspace
The Selected Request - Portal Processing workspace displays information about
portlet and/or portal page response times referenced by the request you selected in
the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Note: This workspace will appear under all WebSphere application servers, but it
will have data only under the WebSphere Portal Server.
The predefined workspace contains the following items:
v Worst Portal Processing Response Times bar chart, which shows the worst
response times (in milliseconds) for portal sources accessed by this request
v Selected Request - Portal Processing report, which displays detailed information
about the portal sources accessed for the selected request. For TEMA running on
z/OS, region ID can be found in the ASID column.
Accessing the Selected Request - Portal Processing workspace
To access this workspace from the Request Analysis workspace, use one of the
following procedures:
v From the Requests - Current Interval report, right-click the link icon to the left of
any row; then, from the pop-up menu, click Selected Request - Portal
Processing.
v From Worst Average Response Times bar chart, right-click any bar; then, from
the pop-up menu, click Link To > Selected Request - Portal Processing.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Selected Request - Resource Adapters workspace
The Selected Request - Resource Adapters workspace displays response-time
information about the J2C resources adapters referenced by the request you
selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
The predefined workspace contains the following items:
v Worst Average Response Times bar chart, which shows the worst-performing J2C
resource adapter's nested requests, in milliseconds
v Selected Request - Resource Adapters report, which displays detailed
information about each J2C resource adapter that was accessed by the selected
request. For TEMA running on z/OS, region ID can be found in the ASID
column.
Chapter 4. ITCAM Agent for WebSphere
279
Accessing the Selected Request - Resource Adapters workspace
To access this workspace from the Request Analysis workspace, use one of the
following procedures:
v From the Requests - Current Interval report, right-click the link icon to the left of
any row; then, from the pop-up menu, click Selected Request - Resource
Adapters.
v From Worst Average Response Times bar chart, right-click any bar; then, from
the pop-up menu, click Link To > Selected Request - Resource Adapters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Service Component Elements workspace
This workspace lists performance metrics for all the service components and their
elements. Service components contain one or more elements, which are sets of
different steps processed in each service component. In turn, each element has its
own set of event natures, which are key points that are reached when processing a
service component element.
This workspace displays data provided by the Service Component Elements
attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Worst Service Times bar chart, which shows the numbers of the Average
Response Time in milliseconds
v Most Invocations bar chart, which shows the numbers of the invocations per
second
v Most Failures bar chart, which shows the numbers of the failed invocation
counts
v Service Component Elements report, which shows aggregated data about the
average response time, failed count, success count, error rate, and request rate.
Accessing the Service Component Elements workspace
To access this workspace from the Service Components workspace, use one of the
following procedures:
v Within the Navigator, right-click the Service Components entry; then, from the
pop-up menu, click Workspace > Service Component Elements.
280
ITCAM for Application Diagnostics: User Guide
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Service Component Elements.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Service Components workspace
This workspace provides overview performance of the key service components.
WebSphere servers feature their own service components, and each of these
components has its own set of event points that can be monitored.
This workspace displays data provided by both the Service Components attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Service Component Architecture - History graph, which shows historical bad
request count, the instrumentation level, set instrumentation level type, and
summary, when the component name of the service is Service Component
Architecture
v Business Rules - History graph, which shows historical bad request count, the
instrumentation level, set instrumentation level type, and summary, when the
name is Business Rules
v Map - History graph, which shows historical bad request count, the
instrumentation level, set instrumentation level type, and summary, when the
name is Map
v Mediation - History graph, which shows historical bad request count, the
instrumentation level, set instrumentation level type, and summary, when the
name is Mediation
v Business State Machine - History graph, which shows historical bad request
count, the instrumentation level, set instrumentation level type, and summary,
when the name is Business State Machine
v Selector - History graph, which shows historical bad request count, the
instrumentation level, set instrumentation level type, and summary, when the
name is Selector
v Bad Requests report, which displays a summary of the bad request counts
Accessing the Service Components workspace
To access this workspace, complete the following steps:
Chapter 4. ITCAM Agent for WebSphere
281
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Service Components entry.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Servlets/JSPs - Selected Enterprise Application workspace
This workspace displays statistical data regarding the servlets and JSPs invoked by
a single Enterprise application.
This workspace displays data provided by the Servlets JSPs attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Worst Servlet/JSP Response Times bar chart, which displays the worst average
response times (in milliseconds) for servlets and JSP invoked by the selected
Web application
v Most Popular Servlet/JSP bar chart, which shows the servlet and JSP exception
and request rates (in events per second) for the selected application
v Worst Servlet/JSP Error Rates bar chart, which shows the worst servlet and JSP
error rates for the selected application during the interval
v Servlets/JSPs - Selected Web Application report, which displays performance
information about the servlets and JSPs invoked by the application. For example,
this report displays the average number of concurrent requests for a servlet and
the amount of time it takes a servlet to respond to a request
Accessing the Servlets/JSPs - Selected Enterprise Application
workspace
To access this workspace from the Web Applications workspace, use one of the
following procedures:
282
ITCAM for Application Diagnostics: User Guide
v From the Web Applications report, right-click the link icon to the left of any row;
then, from the pop-up menu, click Servlets/JSPs - Selected Enterprise
Application.
v From the Worst Response Times bar chart, the Most Popular Web Applications
bar chart, or the Worst Error Rates bar chart, right-click any bar; then, from the
pop-up menu, click Link To > Servlets/JSPs - Selected Enterprise Application.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Scheduler workspace
The Scheduler workspace contains data for the Scheduler service. The scheduler
service schedules and tracks the starting and stopping of applications.
This workspace displays data provided by the Scheduler attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Highest Task Failures bar chart, which shows the number of the task failure
count. The y-axis headings correspond to the row number of the Scheduler
report
v Highest Completed Tasks bar chart, which shows the number of the task
finished count. The y-axis headings correspond to the row number of the
Scheduler report
v Scheduler report, which displays information about the scheduler data,
including task finish count, task failure count, task expiration rate, task finish
rate, and task run rate
Accessing the Scheduler workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
Chapter 4. ITCAM Agent for WebSphere
283
5. Within that server list of available WebSphere Application Server workspaces,
click the Scheduler entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Sessions workspace
This workspace displays information about servlet sessions.
A session is a series of requests to a servlet, originating from the same user at the
same browser. Applications running in a Web container can use these sessions to
keep track of individual users. This workspace displays data provided by the
Servlet Sessions attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Most Active Sessions bar chart, which shows the most frequently referenced
servlet sessions for each listed Web application
v Largest Total Session Object Sizes bar chart, which shows the total session object
sizes (in bytes) and the associated Web applications
v Servlet Sessions report, which shows usage data about the servlet sessions,
including the rates as which sessions are created and destroyed and their read
and write times
Accessing the Sessions workspace
To access this workspace from the Web Applications workspace, use one of the
following procedures:
v Within the Navigator, right-click the Web Applications entry; then, from the
pop-up menu, click Workspace > Servlet Sessions.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
Servlet Sessions.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
284
ITCAM for Application Diagnostics: User Guide
Thread Pools workspace
This workspace reports information about the various thread pools that support
the applications running in your Java Virtual Machine (JVM).
This workspace displays data provided by the Thread Pools attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides
on-demand sampling by default. To activate PMI monitoring, you must first
select this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Highest Average Pool Sizes bar chart, which shows the largest thread pools in
the JVM
v Average Thread Pool Usage bar chart, which shows the average active and free
threads for each thread pool
v Thread Pools report, which shows information about the usage statistics for
thread pools that belong to a WebSphere Application Server, such as average
and maximum pool sizes and creation and destruction rates
Accessing the Thread Pools workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Thread Pools entry.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
285
Accessing the Managing Server Visualization Engine from the
Thread Pools workspace
In The Tivoli Enterprise Portal access the Thread Pools workspace. You can use the
Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
then click
1. In the Thread Pools window, right click the choose link icon
Diagnostic JVM Thread Display.
2. If this is your first time to access the Managing Server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
4. Click OK to display the Diagnostic JVM Thread Display page in the
Managing Server Visualization engine. You can use link to diagnose application
problems, for example, slow transactions or high response times.
5. The results relate directly to the context from where you launched the link in
the Tivoli Enterprise Portal. For more information about using the Diagnostic
JVM Thread Display page and additional features, refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
6. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
Thread Pool Trend workspace
The Thread Pool Trend workspace displays information about thread pool size and
usage.
This workspace displays data provided by the Selected Request attributes.
This predefined workspace contains the following items:
v Current Thread Pool report displays thread pool name, average active threads,
average pool size, percentage of time pool at max and average free threads.
v Average Pool Size Trend bar chart displays the average number of threads in the
pool.
v Average Thread Pool Usage Trend bar chart displays the average percentage of
time that all threads were in use during the sampling interval.
v Percent of Time Pool Size at Max Trend bar chart displays the percentage of time
the pool size is running at the maximum value.
286
ITCAM for Application Diagnostics: User Guide
Accessing the Threadpool Trend workspace
Select the Thread Pools workspace, in the Thread Pools report displayed at the
bottom of the workspace, click the link icon and select Thread Pool Trend.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Web Applications workspace
This workspace displays information about the Web applications running in J2EE
application servers.
This workspace displays data provided by the Web Applications attributes.
Note:
v The Web Applications workspace reports blanks for resource data on the first
invocation if PMI data collection is configured for on-demand sampling (that is,
if your site set configuration value Resource Data Collection Method to On
Demand) or if you have not yet run applications that generate PMI resource
data. To report resource data in this workspace after installing and configuring
the Data Collector, use the WebSphere administrative console to set the
appropriate PMI instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v Worse Response Times bar chart, which shows the worst servlet response times
(in milliseconds) during the interval
v Most Popular Web Applications bar chart, which shows the servlet exception
and request rates (in events per second)
v Worse Error Rates bar chart, which shows the worst servlet error rates during
the interval
v Web Applications report, which displays aggregated performance data for each
Web application, about all servlets and JSPs deployed to that Web application,
including response and error rates and response times.
Accessing the Web Applications workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Web Applications entry.
Chapter 4. ITCAM Agent for WebSphere
287
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
Web Applications workspace
In the Tivoli Enterprise Portal access the WebSphere Agent workspace. You can
use the Diagnostic Server Activity Display link to access the Managing Server
Visualization Engine. For information about access requirements see “Prerequisites
for access” on page 226.
then
1. In the Web Applications window, right click the choose link icon
click Diagnostic Server Activity Display.
2. If this is your first time to access the Managing Server Visualization Engine
during a session, you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
4. Click OK to display the Server Activity Display page in the Managing Server
Visualization engine. You can use link to diagnose application problems, for
example, slow transactions or high response times.
5. The results in this page relate directly to the context from where you launched
the link in the Tivoli Enterprise Portal. For more information about using the
Server Activity Display page and additional features, refer to the Composite
Application Manager help within the Managing Server Visualization Engine
Interface.
6. To return to the previous workspace in the Tivoli Enterprise Portal interface at
any time choose from the following options:
v from the Tivoli Enterprise Portal desktop client, click the back arrow on your
web browser.
v from the Tivoli Enterprise Portal browser client, click the browser back arrow.
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
Web Services workspace
The Web Services workspace displays information about the data counters of the
Web services.
The examples of the information include the number of loaded Web services, the
number of requests delivered and processed, the request response time, and the
average size of requests. This workspace displays data provided by both the Web
Services attributes and the Web Services Gate Way attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
288
ITCAM for Application Diagnostics: User Guide
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains:
v Worst Response Times bar chart, which displays the worst average response
times (in milliseconds) for the selected Web services
v Most Popular bar chart, which shows the exception and request rates (in events
per second) for the selected services
v Web Services report, which displays aggregated performance data for each Web
service, including requests, response times, and payload sizes
v Web Service Gateway report, which displays aggregated performance data for
each Web service gateway, including the number of synchronous and
asynchronous requests and responses
Accessing the Web Services workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Web Services entry.
Selected Web Services - History workspace
The Selected Web Services - History workspace displays the historical information
that corresponds to the information in the Web Services workspace for a selected
Web service. Historical information is collected over a particular measured time
span. See the online help for Tivoli Enterprise Portal for a detailed explanation of
historical reporting.
Accessing the Selected Web Services - History workspace
To access this workspace from the Web Services workspace, use one of the
following procedures:
v From the Web Services report, right-click the link icon to the left of any row;
then, from the pop-up menu, click Selected Web Services - History.
v From the Worst Response Times bar chart, or the Most Popular bar chart,
right-click any bar; then, from the pop-up menu, click Link To > Selected Web
Services - History.
For additional information, see:
v Organization of the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
289
v
Attribute groups used by the predefined workspaces
WebSphere Agent workspace
This workspace displays product events that affect the ability of the WebSphere
Application Server agent to collect data.
This workspace displays events occurring within the WebSphere Application
Server agent and WebSphere application servers that are installed on the host
computer. It also displays the status of the Tivoli Enterprise Monitoring Agent. The
predefined workspace contains the following items:
v Agent Events report, which displays information about agent-level events that
affect the ability of the Tivoli Enterprise Monitoring Agent to collect data for the
WebSphere application server. You can use this view to see exception and error
messages, their IDs, and their severity.
The Agent Events report also shows the result of issuing a Take Action
command. Place your cursor over a truncated message to display the text of the
complete message
This report displays data reported by the WebSphere Agent Events attributes.
v Application Servers Summary report displays information about status of the
WebSphere server.
This report displays data reported by the Application Server Status attributes.
Accessing the WebSphere Agent workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of available Tivoli Enterprise Monitoring Agents, click the
WebSphere Agent entry.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Accessing the Managing Server Visualization Engine from the
WebSphere Agent workspace
In the Tivoli Enterprise Portal access the WebSphere agent workspace. You can use
the Diagnostic Server Activity Display or the Diagnostic In-flight Request
Search link to access the Managing Server Visualization Engine. For information
about access requirements see “Prerequisites for access” on page 226.
1. In the Applications Server Summary window, right click the choose link icon
then click Diagnostic Server Activity Display or Diagnostic In-flight
Request Search.
2. If this is your first time to access the Managing Server Visualization Engine
during the session you see a Welcome to the Application Monitor page.
3. Depending on the user setup configuration in your environment you may or
may not have to type your Managing Server Visualization Engine User Name
and Password. If you do, you only need to log in using your User Name and
Password once per session.
290
ITCAM for Application Diagnostics: User Guide
4. Click OK to display the relevant page in the Managing Server Visualization
engine.
v If you click Diagnostic In-flight Request Search you see the In-Flight
Request Search page in Managing Server Visualization Engine.
v If you click Diagnostic Server Activity Display you see the Server Activity
Display page in the Managing Server Visualization Engine.
The information in both of these pages relates directly to the context from
where you launched the link in the Tivoli Enterprise Portal.
6. To return to the Tivoli Enterprise Portal interface at any time click back on your
web browser.
5.
For additional information, see:
v “Workspace link to Managing Server Visualization Engine” on page 225
v “Access the Managing Server Visualization Engine from the Tivoli Enterprise
Portal” on page 229
WebSphere Application Server workspace
The WebSphere Application Server workspace displays overall statistics for each
application server being monitored by the Tivoli Enterprise Monitoring Agent.
The predefined workspace contains the following items:
v Heap Usage - History bar chart, which displays free memory size and used
memory size (in kilobytes) within the WebSphere Application Server's heap over
time. The chart's flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
v Response Time - History graph, which shows the server response time to
requests over time
This view displays data provided by the Request Times and Rates attributes.
v Request Rate - History graph, which shows the rate at which requests have been
received by this server over time
This view displays data provided by the Request Times and Rates attributes.
v Percent CPU Used - History graph, which shows the percentage of the CPU that
this server used over time
This view displays data provided by the Application Server attributes.
v Application Server Summary report, which displays overall information about
this WebSphere application server, including JVM statistics and CPU usage
statistics
This view displays data provided by the Application Server attributes. In the
Application Server Summary report, each row represents a different region.
When you right-click the link for a row, you can choose to go to Selected Region
- Application Server Summary, Selected Region - Request Analysis, Selected
Region - Application Health Status, Selected Region - Datasources, Selected
Region - Log Analysis or Selected Region - JMS Summary. All these links are
disabled when TEMA is running on Distributed data collector and enabled when
TEMA is running on z/OS data collector.
Accessing the WebSphere Application Server workspace
Complete the following steps to access this workspace:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you're monitoring.
Chapter 4. ITCAM Agent for WebSphere
291
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, click the WebSphere App Server entry of
your choice.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
WebSphere ESB Server workspace
The WebSphere ESB Server workspace displays overall statistics for each
application server being monitored by the Tivoli Enterprise Monitoring Agent.
The predefined workspace contains the following items:
v Heap Usage - History bar chart, which displays free memory size and used
memory size (in kilo bytes) within the WebSphere Application Server's heap
over time. The chart's flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
v Response Time - History graph, which shows the server response time to
requests over time
This view displays data provided by the Request Times and Rates attributes.
v Request Rate - History graph, which shows the rate at which requests have been
received by this server over time
This view displays data provided by the Request Times and Rates attributes.
v Percent CPU Used - History graph, which shows the percentage of the CPU that
this server consumed over time
This view displays data provided by the Application Server attributes.
v Application Server Summary report, which displays overall information about
this WebSphere application server, including JVM statistics and CPU usage
statistics
This view displays data provided by the Application Server attributes.
Accessing the WebSphere ESB Server workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, click the WebSphere ESB Server entry of
your choice.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
292
ITCAM for Application Diagnostics: User Guide
WebSphere Portal Server workspace
The WebSphere Portal Server workspace displays overall statistics for each
application server being monitored by the Tivoli Enterprise Monitoring Agent.
The predefined workspace contains the following items:
v Heap Usage - History bar chart, which displays free memory size and used
memory size (in kilo bytes) within the WebSphere Application Server's heap
over time. The chart's flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
v Response Time - History graph, which shows the server response time to
requests over time
This view displays data provided by the Request Times and Rates attributes.
v Request Rate - History graph, which shows the rate at which requests have been
received by this server over time
This view displays data provided by the Request Times and Rates attributes.
v Percent CPU Used - History graph, which shows the percentage of the CPU that
this server consumed over time
This view displays data provided by the Application Server attributes.
v Application Server Summary report, which displays overall information about
this WebSphere application server, including JVM statistics and CPU usage
statistics
This view displays data provided by the Application Server attributes. In the
Application Server Summary report, each row represents a different region.
When you right-click the link for a row, you can choose to go to Selected Region
- Application Server Summary, Selected Region - Request Analysis, Selected
Region - Application Health Status, Selected Region - Datasources, Selected
Region - Log Analysis, Selected Region - JMS Summary, Selected Region - Portal
Summary, Selected Region - Portlet Summary. All these links are disabled when
TEMA is running on Distributed data collector and enabled when TEMA is
running on z/OS data collector.
Accessing the WebSphere Portal Server workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems
or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, click the WebSphere Portal Server entry of
your choice.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
WebSphere Process Server workspace
The WebSphere Process Server workspace displays overall statistics for each
application server being monitored by the Tivoli Enterprise Monitoring Agent.
Chapter 4. ITCAM Agent for WebSphere
293
The predefined workspace contains the following items:
v Heap Usage - History bar chart, which displays free memory size and used
memory size (in kilo bytes) within the WebSphere Application Server's heap
over time. The chart's flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
v Response Time - History graph, which shows the server response time to
requests over time
This view displays data provided by the Request Times and Rates attributes.
v Request Rate - History graph, which shows the rate at which requests have been
received by this server over time
This view displays data provided by the Request Times and Rates attributes.
v Percent CPU Used - History graph, which shows the percentage of the CPU that
this server consumed over time
This view displays data provided by the Application Server attributes.
v Application Server Summary report, which displays overall information about
this WebSphere application server, including JVM statistics and CPU usage
statistics
This view displays data provided by the Application Server attributes.
Accessing the WebSphere Process Server workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, z/OS
Systems, or UNIX Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, click the WebSphere Process Server entry of
your choice.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
WMQ Client Link Communications workspace
This workspace provides aggregated counter statistics for all of the clients of WMQ
Queue Managers that are or have been connected to this application server.
WebSphere Application Server 5.1 based products do not support this workspace.
This workspace displays data provided by the WMQ Client Link Communications
attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
294
ITCAM for Application Diagnostics: User Guide
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it later. Each time you select the workspace, it
displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v WMQ Client Link Communication Errors - History graph, which shows the
number of errors that have caused connections to WMQ JMS clients to be
dropped
v WMQ Client Link Statistics report, which displays information about the
messaging engine communications, including batch sent, message sent, message
received, comm errors, writes blocked, and reads blocked
Accessing the WMQ Client Link Communications workspace
To access this workspace from the Platform Messaging workspace, use one of the
following procedures:
v Within the Navigator, right-click the Platform Messaging entry; then, from the
pop-up menu, click Workspace > WMQ Client Link Communications.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
WMQ Client Link Communications.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
WMQ Link Communications workspace
This workspace provides aggregated counter statistics for all of the WMQ Queue
Managers that are or have been connected to this application server. WebSphere
Application Server 5.1 based products do not support this workspace.
This workspace displays data provided by the WMQ Link Communications
attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v WMQ Link Communication Errors - History graph, which shows the historical
number of communication errors that resulted in the disconnection of a network
connection to a WMQ Queue Manager
Chapter 4. ITCAM Agent for WebSphere
295
v WMQ Link Statistics report, which displays information about the messaging
engine communications, including batches sent, batches received, message sent,
message received, and comm errors
Accessing the WMQ Link Communications workspace
To access this workspace from the Platform Messaging workspace, use one of the
following procedures:
v Within the Navigator, right-click the Platform Messaging entry; then, from the
pop-up menu, click Workspace > WMQ Link Communications.
v From the primary Tivoli Enterprise Portal menu, click View > Workspace >
WMQ Link Communications.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Workload Management workspace
This workspace displays information about the Workload Management (WLM)
server and about the WLM client that initiates workload requests to that server.
Workload management optimizes the distribution of client processing tasks.
Incoming work requests are distributed to the application servers, enterprise beans,
servlets, and other objects that can most effectively process the requests. Workload
management also provides failover protection when servers are not available,
improving application availability. In a WebSphere Application Server
environment, you implement workload management using clusters, transports, and
replication domains.
This workspace displays data provided by both the Workload Management Server
attributes and the Workload Management Client attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
The predefined workspace contains the following items:
v WLM Server Incoming Requests bar chart, which shows the incoming strong
affinity requests and the incoming nonaffinity requests (per second)
v WLM Client Outgoing Requests bar chart, which shows the outgoing requests
(per second)
v Workload Management Server report, which shows detailed information about
the WLM server, such as incoming requests and clients served
296
ITCAM for Application Diagnostics: User Guide
v Workload Management Client report, which shows information about the clients
that initiate workload requests, such as outgoing requests and response times
Accessing the Workload Management workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, or UNIX
Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Workload Management entry.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Workplace Mail workspace
This workspace provides aggregated statistics of the usage information about the
incoming message traffic.
This workspace displays data provided by the Workplace Mail Service attributes.
Note:
v This workspace reports blanks for resource data on the first invocation if PMI
data collection is configured for on-demand sampling (that is, if your site set
configuration value Resource Data Collection Method to On Demand) or if you
have not yet run applications that generate PMI resource data. To report
resource data in this workspace after installing and configuring the Data
Collector, use the WebSphere administrative console to set the appropriate PMI
instrumentation level.
v Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on
demand sampling by default. To activate PMI monitoring, you must first select
this workspace and then select it again later. Each time you select the
workspace, it displays the data collected during the interval between selections.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support the Workplace Mail workspace: configuration and links to the Managing
Server Visualization Engine from the Tivoli Enterprise Portal.
The predefined workspace contains the following items:
v Connections bar chart, which displays the number of connections to the SMTP
server, SMTP client connections, and the maximum number of concurrent LDAP
connections during the sampling interval
v Workplace Mail report, which displays detailed information about the workplace
mail connections
Chapter 4. ITCAM Agent for WebSphere
297
Accessing the Workplace Mail workspace
To access this workspace, complete the following steps:
1. Within the Navigator, expand Windows Systems, Linux Systems, or UNIX
Systems, as appropriate for the node you are monitoring.
2. Within the node list, expand the entry that corresponds to the node you want
to select.
3. Within that node list of monitored applications, expand the list of WebSphere
agents.
4. Within the list of available agents, expand the WebSphere application server of
your choice.
5. Within that server list of available WebSphere Application Server workspaces,
click the Workplace Mail entry.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Region workspaces in a z/OS environment
For z/OS installations workspace tables report data at both a region and server
instance level.
The advantage is that you can view metrics collected at both levels and switch
between server instance lever and region level. The following table lists the
workspaces that show information and both a region and server level.
All workspaces except the Garbage Collection Analysis workspace report data on
both levels. The Garbage collection analysis workspace does not have links to the
top-level workspaces.
Table 16. Workspaces and the Servant and Selected Regions in a z/OS environment
Workspace Table Name
Link Name
Description
WebSphere App Server Application Server
Summary
WebSphere App Server Application Server
Summary - Selected
Region - Application
Server Summary
Application Server Summary
workspace. This workspace
displays data at regional level.
Click the Selected Region links to
access region-specific links to other
top-level workspaces. When a
workspace is linked from the
application server summary you
can view specific drill-down
metrics. To view a report for an
individual region, see “Accessing a
Region workspace” on page 300
Selected Region Application Health Status
Selected Region - Request
Analysis
Selected Region - Log
Analysis
Selected Region - Data
Sources
Selected Region - JMS Summary
298
ITCAM for Application Diagnostics: User Guide
Table 16. Workspaces and the Servant and Selected Regions in a z/OS
environment (continued)
Workspace Table Name
Link Name
Description
Application Health Application Health
Summary
Selected Application Servant regions
In an z/OS environment, the
Application Health Summary
report displays the total results for
the server instances. To view
report results by region, Click the
WebSphere App Server Application Server Summary table
and right click a link icon in the
table to view the available options.
Selected Application Health History
Selected Application- Web
Tier Analysis
Selected Application - EJB
Tier Analysis
Selected Application Backend Tier Analysis
Selected Application Request Analysis
Selected Application Configuration
Request Analysis Selected Request Requests Current Interval Datasource
Selected Request - JMS
Queues
Selected Request Resource Adaptors
In an z/OS environment, when
you select Request Analysis Requests Current Interval, this
report displays the total results for
the server instances. To view a
report for an individual Request
Analysis region, see “Accessing a
Region workspace” on page 300.
Selected Request - History
Selected Request - Servant
Regions
Garbage Collection
Analysis - Garbage
Collection Analysis
Selected Region - History
Log Analysis - Log
Analysis
Selected Region - Log
Analysis
Garbage Collection
Analysis - Servant Region
(only available when you
click a [Summary] row)
Data sources - Data
Selected Datasource
sources - Current Interval
Selected Datasource History
When you click Garbage Collection
Analysis the results of the report
display in the table at the bottom
of the screen. There is a summary
report of all regions and there are
also reports by individual region.
Log Analysis workspace. In a
z/OS environment, the log analysis
workspace reports data in two
ways. When you select the Log
analysis workspace the report
displays JVM Log Analysis and
DC message events from all
regions. To view a report for an
individual log analysis region, see
“Accessing a Region workspace”
on page 300.
In an z/OS environment, this
report displays the total results for
the server instances. To view a
report for an individual Data
source region, see, “Accessing a
Region workspace” on page 300.
Chapter 4. ITCAM Agent for WebSphere
299
Table 16. Workspaces and the Servant and Selected Regions in a z/OS
environment (continued)
Workspace Table Name
Link Name
Description
JMS Summary - JMS
Summary - Current
Interval JMS
Selected JMS - Servant
Regions
In an z/OS environment, this
report displays the total results for
the server instances. To view a
report for an individual JMS
Summary region, see“Accessing a
Region workspace.”
WebSphere Portal Server
Selected Region - Portal
Server Summary
In an z/OS environment, this
report displays the total results for
the server instances. To view a
report for an individual Portal
Server summary, see “Accessing a
Region workspace”
Portal Summary
Selected Region - Portal
Summary
In an z/OS environment report
displays the total results for the
server instances. To view a report
for an individual region see
“Accessing a Region workspace”
Selected Region - Portlet
Summary
Selected Portal Page History
Selected Portlet - History
Selected Region - Portal
Page Summary
Accessing a Region workspace
To access this workspace, complete the following steps:
1. In the Navigator, expand z/OS system, as appropriate for the node you are
monitoring.
2. In the node list, expand the entry that corresponds to the node you want to
select.
3. In that node list of monitored agents, expand the list of the servers.
4. In the list of available servers, click the WebSphere agent of your choice.
5. In the list of available Servers select the Server of your choice.
6. Right click the selected Server node and select WebSphere App Server
workspace.
7. Right click a link icon in the Application Server Summary table to display all
the available workspaces connected with current region.
8. Select the workspace of your choice from the following list:
v Selected Region Application Server Summary
v Selected Region - Application Health Status
v
v
v
v
Selected
Selected
Selected
Selected
Region
Region
Region
Region
-
Request Analysis
Log Analysis
Data Sources
JMS - Summary
For additional information, see:
300
ITCAM for Application Diagnostics: User Guide
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
ITCAM for Application Diagnostics- WebSphere Agent attributes
IBM Tivoli Composite Application Manager for Application Diagnostics WebSphere Agent is a Tivoli Enterprise Management Agent that resides within
your distributed systems. This agent gathers data about running WebSphere
Application Server processes that have been collected and stored by the ITCAM for
WebSphere data collector, and stores those data in elements called attributes. Each
attribute is a characteristic of an object. For example, the Receive Count attribute in
the JMS Summary attribute group counts the number of messages your
applications have retrieved from JMS messages queues.
Attribute groups
The IBM Tivoli Composite Application Manager for Application Diagnostics WebSphere Agent attributes are organized into groups of related items. These
attribute groups comprise the attribute tables for this agent. For example, the
Garbage Collection Analysis attribute group provides information about the
frequency with which the Java Virtual Machine (JVM) invokes its garbage collector.
Attributes and workspaces
Within the Tivoli Enterprise Portal workspaces, these attributes get displayed in,
and correspond to, the columns in the reports and the items in the graphic
displays for charts and graphs. You can use the collected data to analyze and
monitor the performance of your WebSphere application servers and the
applications running within them. For an overview of the correlations between the
predefined workspaces and the attribute groups, see Attribute Groups Used by the
Predefined Workspaces.
Attributes and situations
Various attributes are referenced by the product's predefined situations. You can
also use the IBM Tivoli Composite Application Manager for Application
Diagnostics - WebSphere Agent attributes to create your own situations to monitor
the performance of your WebSphere application servers and their applications.
These situations can monitor your WebSphere Application Server resources or
correlate multiple conditions to alert you to problems that may have occurred
when attribute values exceed thresholds that you define.
Attribute groups used by the predefined workspaces
A workspace contains graphical data or report columns that correspond directly to
particular attributes in an attribute group. The following table shows the
correlations between the predefined workspaces and the attribute groups. The
workspaces, primary and secondary, are listed alphabetically, not in the order in
which they appear in the Navigator.
Table 17. Workspaces and the attribute groups they reference
Workspace
Related Attribute Groups
Application Health Summary
Application Health Status
Application Registry
Application Monitoring Configuration
Allocation Failures
Allocation Failure
Chapter 4. ITCAM Agent for WebSphere
301
Table 17. Workspaces and the attribute groups they reference (continued)
Workspace
Related Attribute Groups
Cache Analysis
Dynamic Cache
Dynamic Cache Templates
Client Communications
Client Communications
Container Object Pools
Container Object Pools
Container Transactions
Container Transactions
Datasources
Selected Datasource - History
Datasources
DB Connection Pools
Selected DB Connection Pool - History
DB Connection Pools
DCS Stacks
DCS Stack Counter
Destinations
Topic Spaces
Queue
Durable Subscriptions
Durable Subscriptions
EJB Containers
EJB Containers
Enterprise Java Beans
Enterprise Java Beans
Garbage Collections - Selected Allocation Garbage Collection Cycle
Failure
302
Garbage Collector Analysis
Garbage Collection Analysis
High Availability Manager
High Availability Manager
IMAP/POP
Workplace Mail IMAP/POP
J2C Connection Pools
J2C Connection Pools
JMS Summary
JMS Summary
Log Analysis
Log Analysis
Lotus
Application Server
Request Times and Rates
Garbage Collection Analysis
Messages Queues
Workplace Mail Queues
Messaging Engine Communications
Messaging Engine Communications
Platform Messaging
Messaging Engines
Pool Analysis
Thread Pools
DB Connection Pools
J2C Connection Pools
Application Server
Portal Pages Summary
Selected Portal Page - History
Portal Page Summary
Portal Summary
Portal Summary
Portlet Summary
Selected Portlet - History
Portlet Summary
Request Analysis
Selected Request - History
Request Analysis
Selected Request - Baseline
Baseline
Scheduler
Scheduler
ITCAM for Application Diagnostics: User Guide
Table 17. Workspaces and the attribute groups they reference (continued)
Workspace
Selected Application
Analysis
Selected Application
Analysis
Selected Application
Selected Application
Analysis
Related Attribute Groups
- Application Tier
Application Health Status
- Backend Tier
- Health History
- Client Tier
Selected Application - Configuration
Application Monitoring Configuration
Selected Request - Datasources
Selected Request
Selected Request - JMS Queues
Selected Request
Selected Request - Resource Adapters
Selected Request
Servlets/JSPs - Selected Web Application Servlets JSPs
Sessions
Servlet Sessions
Thread Pools
Thread Pools
Web Applications
Web Applications
Web Services
Selected Web Services - History
Web Services Counters
Web Services Gateway Counters
WebSphere Agent
WebSphere Agent Events
Application Server Status
“Remote Configuration Requests attributes” on
page 382
WebSphere App Server
Application Server
Request Times and Rates
Garbage Collection Analysis
WebSphere ESB Server
Application Server
Request Times and Rates
Garbage Collection Analysis
WebSphere Portal Server
Application Server
Request Times and Rates
Garbage Collection Analysis
WebSphere Process Server
Application Server
Request Times and Rates
Garbage Collection Analysis
WMQ Client Link Communications
WMQ Client Link Communications
WMQ Link Communications
WMQ Link Communications
Workload Management
Workload Management Client
Workload Management Server
Workplace Mail
Workplace Mail Service
Alarm Manager attributes
The Alarm Manager attributes provide information for the alarm management.
Use these attributes to manage alarms fired by the application for each work
manager.
The attributes within this group are used to build the Alarm Manager workspace.
Note:
Chapter 4. ITCAM Agent for WebSphere
303
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Alarms Canceled The number of alarms canceled by the application. The valid
format is a positive integer.
Alarms Created The total number of alarms created by all asynchronous scopes for
the current Work Manager. The valid format is a positive integer.
Alarms Fired The number of alarms fired. The valid format is a decimal (formatted
to 3 decimal places).
Alarms Latency Duration The latency of alarms fired in milliseconds. The valid
format is a decimal (formatted to 3 decimal places). This value is an average of
several values collected over an interval. The interval can be either between this
time and the previous time you activated this workspace, or fixed (normally 60
seconds), depending on the configuration of the Monitoring Agent.
Alarms Pending Size The number of alarms waiting to fire. The valid format is a
decimal (formatted to 3 decimal places). This value is an average of several values
collected over an interval. The interval can be either between this time and the
previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Alarms Rate The number of alarms firing per second. The valid format is a
decimal (formatted to 3 decimal places). This value is an average of several values
collected over an interval. The interval can be either between this time and the
previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Instrumentation Level For WebSphere 6 or higher, the valid values are None,
Basic, Extended, All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Row Number The row number. The valid format is a positive integer.
304
ITCAM for Application Diagnostics: User Guide
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 18. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Work Manager Name The name of the work manager. The value format is an
alphanumeric string, with a maximum of 256 characters.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Allocation Failure attributes
The Allocation Failure attribute group provides information about the
heap-allocation failure that caused the Java Virtual Machine hosting the application
server to invoke its garbage-collection routine.
You can use the Allocation Failure attributes in situations to determine the events
that caused the JVM to invoke garbage collection. The attributes within this group
are used to build the Allocation Failures workspace.
Allocation Failure Number The identifier assigned to the current allocation-failure
block, which is associated with a bar in the Heap Usage - History bar chart. The
valid format is a positive integer.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Bytes Needed The number of bytes needed on the heap when this allocation
failure occurred. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
305
GC Cycle Count The number of garbage-collection cycles caused by this allocation
failure. The valid format is a positive integer.
Heap Expanded The total number of kilobytes by which the heap expanded or
contracted as a result of garbage collection. The valid format is a positive integer.
Heap Free (%) after GC The percentage of heap space that is available after
garbage collection. The valid format is a positive integer.
Heap Status Whether the out-of-heap-space alert has been raised. Valid values are
Normal and Out_of_heap_space.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Kbytes Free at Start of GC The number of kilobytes available in the heap before
garbage collection began in response to this allocation failure. The valid format is a
positive integer.
Kbytes Freed by GC The number of kilobytes freed by the garbage collector for
this allocation failure. The valid format is a positive integer.
Kbytes Used The number of kilobytes in the heap that were in use when this
allocation failure occurred. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Objects Moved The number of objects the garbage collector moved during
compaction. The valid format is a positive integer.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 19. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
306
ITCAM for Application Diagnostics: User Guide
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Time since Last Failure (ms) The time (in milliseconds) since the previous
allocation failure. The valid format is a positive integer.
Time to Complete (ms) The time (in milliseconds) required to complete the action
that resulted from this allocation failure. The valid format is a positive integer.
Total Kbytes Freed by GC The total number of kilobytes freed by the garbage
collector in response to this allocation failure. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Application Health Status attributes
The Application Health Status attributes provide information for real-time and
historical application health status.
The attributes within this group are used to build the Application Health Summary
workspace.
Application Health The combined application health level. Valid values are
Unknown, Good, Fair, and Bad.
Application ID The unique identifier that is assigned automatically when the
application is first configured and is preserved during the whole application life
cycle. The valid format is a positive integer or -1 which means that Application ID
is aggregated statistic for all applications.
Application Name The name of the application to which the request belongs. The
valid format is an alphanumeric string, with a maximum of 256 characters.
Application Status The current status of the monitored application. Valid values
are Standby, Discovered, Unknown, Starting, Running, Stopping, Stopped, and
Failed.
Application Tier Health The health level of the application tier. Valid values are
Unknown, Good, Fair, and Bad. Application tier health indicator is determined
from EJB or custom request delays collected on the interval and compared against
thresholds configured for application requests.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Backend Tier Health The health level of the backend tier. Backend tier health
indicator is determined from JDBC, JCA, JNDI, JMS delays collected on the interval
and compared against thresholds configured for application requests. Valid values
are Unknown, Good, Fair, and Bad.
Chapter 4. ITCAM Agent for WebSphere
307
Client Tier Health The health level of the client tier. Valid values are Unknown,
Good, Fair, and Bad. Client tier health indicator is determined from servlet/JSP or
portal delays collected on the interval and compared against thresholds configured
for application requests.
Completion Level The completion level of the requests during the interval. Valid
values are Unknown, Good, Fair, and Bad. This attribute is determined from
request data as the percentage of number of failed requests to the total number of
application requests on the interval.
Custom Requests The availability indicator of the custom requests. Valid values
are Unknown, Good, Fair, and Bad.
EJB Container The health level of the EJB container. Valid values are Unknown,
Good, Fair, and Bad. This attribute is determined from EJB delay types collected
during the interval and compared against application thresholds.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
JCA The overall health status of J2EE Connector Architecture (JCA) resources used
by applications. Valid values are Unknown, Good, Fair, and Bad. This attribute is
determined from JCA delay types collected during the interval and compared
against application thresholds.
JDBC The overall health status of Java DataBase Connectivity (JDBC) resources
used by applications. Valid values are Unknown, Good, Fair, and Bad. This
attribute is determined from JDBC delay types collected during the interval and
compared against application thresholds.
JNDI The overall health status of Java Naming and Directory Interface (JNDI)
resources used by applications. Valid values are Unknown, Good, Fair, and Bad.
This attribute is determined from JNDI delay types collected during the interval
and compared against application thresholds.
JMS The overall health status of Java Message Service (JMS) resources used by
applications. Valid values are Unknown, Good, Fair, and Bad. This attribute is
determined from JMS delay types collected during the interval and compared
against application thresholds.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Portal Container The health level of the portal container. Valid values are
Unknown, Good, Fair, and Bad. This attribute is determined from portal delay
types collected during the interval and compared against application thresholds.
Response Level The health level of the response time for the requests. Valid values
are Unknown, Good, Fair, and Bad. This attribute is determined from application
requests response times collected during the interval and compared against
application thresholds.
308
ITCAM for Application Diagnostics: User Guide
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 20. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Web Container The health level of the Web container. Valid values are Unknown,
Good, Fair, and Bad.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Monitoring Configuration attributes
The Application Monitoring Configuration attributes provide information for the
Application Monitoring Configuration.
Use these attributes to monitor different WebSphere applications running within an
application server. The attributes within this group are used to build the Selected
Application - Configuration workspace.
Application Alias The alias name that you can optionally assign for the
application. In practice, this attribute enables you to combine multiple applications
under the same common alias and report their request in the Tivoli Enterprise
Portal as it would come from same application. This attribute is blank by default.
You can assign the value to it from Take Actions at any time in the application
monitoring life cycle. The valid format is an alphanumeric string, with a maximum
of 256 characters.
App ID The unique identifier that is assigned automatically when the application
is first configured and is preserved during the whole application life cycle. The
valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
309
Application Name The name of the application to which the request belongs. You
can define the pattern of this name in the Application Registry workspace. The
valid format is an alphanumeric string, with a maximum of 256 characters.
Bad Completion Rate (%) The bad completion rate threshold for the requests. The
valid format is an alphanumeric string, with a maximum of 256 characters.
Baselining Elapsed Time The number of seconds during which the application
baselining has been running. The valid format is a positive integer.
Baselining Status The current status of the application baselining process. Valid
values are Idle, Running, and Standby.
Baselining Scheduled Stop Time The date and time baselining is scheduled to
finish. The valid format is a 12-character timestamp. For the STR and SCAN
functions, the format is MM/DD/YY HH:MM:SS; the following table shows the
values contained in this character string:
Table 21. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Baselining Start Time The date and time when the application baselining was
started. The valid format is a 12-character timestamp. For the STR and SCAN
functions, the format is MM/DD/YY HH:MM:SS; the following table shows the
values contained in this character string:
Table 22. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Baselining Update Interval The number of seconds that defines how often active
baselining data is incrementally updated to the monitoring agent. The valid format
is a positive integer.
Fair Completion Rate (%) The fair completion rate threshold for the requests. The
valid format is an alphanumeric string, with a maximum of 256 characters.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
310
ITCAM for Application Diagnostics: User Guide
Monitoring Status The current application monitoring status. Valid values are
Discovered, Enabled, Disabled, and Standby.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Request Data Monitoring Level The custom request aggregation level for all
application requests. Valid values are Default, Disabled, Level1, and Level2. This
attribute is set to Default when the application is first discovered.
Request Data Sampling Rate The custom request aggregation rate for all
application requests. The valid format is a positive integer.
Reflex Automation Mode When reflex automation mode is enabled, application
monitoring level is automatically updated on WASAppHealth* situation event.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 23. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Application Server Status attributes
The Application Server Status attributes provide status information for all
WebSphere application servers (and the WebSphere administrative server) being
monitored by the agent.
Chapter 4. ITCAM Agent for WebSphere
311
The attributes within this group are used to build the WebSphere Agent
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Cluster Name The name of the server group (cluster) that this application server
belongs to. The valid format is an alphanumeric string, with a maximum of 128
characters.
Cluster Type Indicates the type of the server group (cluster) the application server
belongs to.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 128 characters.
Process ID The process identifier of the Java virtual machine. The valid format is a
positive integer.
Regions Number The number of z/OS regions connected. This applies to z/OS
environments only.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 24. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Mode The mode of the WebSphere Application Server.
312
ITCAM for Application Diagnostics: User Guide
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Server Origin Node Name Indicates the origin node name of the server
subnode.The valid format is an alphanumeric string, with a maximum of 128
characters.
Server Subnode Name The name of the server node in the navigation tree. The
valid format is an alphanumeric string, with a maximum of 32 characters.
Server Type The type of server process. The valid values are:
Table 25. Types of server processes
Server Type
Definition
Unknown
The server type cannot be determined
AppServer
A process that executes applications
AdminServer
The administrative server that one uses when
configuring WebSphere Application Server environments
NodeAgent
The WebSphere Application Server node agent
JMSServer
The WebSphere Application Server JMS server
DeploymentMgr
The WebSphere Application Server deployment (cell)
manager
ManagedProcess
A standalone WebSphere Application Server process
UnManagedProcess
A WebSphere Application Server process that is managed
by a WebSphere Application Server deployment manager
through a node agent
Start Date and Time The date and time when the WebSphere application server
started. The valid format is a timestamp. This attribute was designed for logging
and reporting data-collection times rather than for creating situations. To specify a
time and date for comparison and testing, use attributes from the Universal Time
or Local Time groups.
Status The status of the WebSphere application server. Valid values are Connected
and Disconnected.
WAS Cell Name The name of the WebSphere Application Server cell to which this
application server belongs. The valid format is an alphanumeric string, with a
maximum of 64 characters.
WAS Configuration Repository Directory Name The name of the WebSphere
Application Server configuration repository directory, which normally resides in
the config subdirectory of the product installation root directory. The valid format
is an alphanumeric string, with a maximum of 128 characters.
WAS Node Name The name of the WebSphere Application Server node group to
which this application server belongs. The valid format is an alphanumeric string,
with a maximum of 64 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
313
Application Server attributes
The Application Server attributes provide the status and summary data for a
specific WebSphere Application Server instance.
The attributes provide performance data for the WebSphere Application Server
runtime (JVM memory), thread pools, HTTP sessions, and configuration
parameters. They also provide some information from other attribute groups to
give an overall view of the WebSphere application server. Use the Application
Server attributes in situations to monitor the health and performance of a
WebSphere application server.
The attributes within this group are used to build the WebSphere Application
Server and the Pool Analysis Workspace workspaces.
Note:
v The attributes in this attribute group contain zeros for performance data if your
site sets the configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes when
you have installed and configured the Data Collector, use the WebSphere
administrative console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; this means the attributes in this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
ASID The identifier (decimal) assigned to the address space running this servant
region.
CPU Used (ms) Indicates the number of milliseconds the JVM CPU used during
the interval. The valid format is a positive integer.
CPU Used (%) Indicates the percentage of the JVM CPU used during the interval.
For UNIX users, this attribute has a meaningful value only if the Tivoli Enterprise
Monitoring Agent is running with superuser authority. The valid format is a
decimal (formatted to 1 decimal place).
Platform CPU Used (ms) Indicates the number of milliseconds the host platform
(OS) CPU used during the interval. This feature does not apply to the z/OS
platform.
Garbage Collection Monitoring The monitoring level for garbage-collection data.
Valid values are Disabled and Enabled.
Instrumentation Level The JVM instrumentation level. For WebSphere 6 or higher,
the valid values are None, Basic, Extended, All, Custom. Blank if no
instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
314
ITCAM for Application Diagnostics: User Guide
JVM Memory Free (Kbytes) The JVM free memory size in Kbytes.
JVM Memory Total (Kbytes) The JVM total memory size in Kbytes.
JVM Memory Used (Kbytes) The JVM used memory size in Kbytes.
JVM Memory Free (bytes) The JVM free memory size (in bytes). The valid format
is a positive integer.
JVM Memory Total (bytes) The JVM total memory size (in bytes). The valid
format is a positive integer.
JVM Memory Used (bytes) The JVM used memory size (in bytes). The valid
format is a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The process identifier of the Java virtual machine. The valid format is a
positive integer.
Request Data Monitoring Level The monitoring level for request data stored by
the Data Collector. Valid values are Disabled, Level1 edge request data, such as
servlets and JSPs are displayed), and Level2 (nested request data such as JDBC and
JMS requests are also displayed).
Request Data Sampling Rate (%) The percentage of Level1 requests (that is, edge
requests) being sampled. The valid format is a positive integer.
Resource Data Monitoring The monitoring level for resource (that is, PMI) data
stored by the Data Collector. Valid values are Disabled and Enabled.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12 character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 26. Format of the 12 character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
Chapter 4. ITCAM Agent for WebSphere
315
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Instance Name The name of the WebSphere application server. This is a
logical grouping of one or more server instances (called a "generic server" or
"cluster") any one of which can run an application. The valid format is an
alphanumeric string, with a maximum of eight characters.
Server Mode Indicates the mode of the WebSphere Application Server.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Server Type The type of the WebSphere application server. Valid values are
Unknown, AppServer, AdminServer, NodeAgent, JMSServer, DeploymentManager,
ManagedProcess, and UnManagedProcess.
Server Subnode Name Indicates the sub node name of the application server.
Start Date and Time The date and time when the WebSphere application server
started. The valid format is a timestamp. This attribute was designed for logging
and reporting data-collection times rather than for creating situations. To specify a
time and date for comparison and testing, use attributes from the Universal Time
or Local Time groups.
Status The status of the WebSphere application server. Valid values are Connected
and Disconnected.
Summary Indicates that this row is a summary row of statistical totals for all rows.
System Paging Rate (Kbytes/sec) The system paging rate in kilobytes per second
during the interval. The valid format is a positive integer.
Version The version of WebSphere Application Server. The valid format is an
alphanumeric string, with a maximum of 8 characters.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Baseline attributes
The Baseline attributes provide information for baseline extract data for the given
application.
The baselining collects statistical information about an application requests
completion times and uses this information to assign fair and bad thresholds on
the application requests. The product divides the whole request response times
into buckets and collects individual hits into each bucket. Use these attributes to
get statistics from individual requests collected during baselining interval.
The attributes within this group are used to build the Selected Request - Baseline
workspace.
316
ITCAM for Application Diagnostics: User Guide
Application ID The unique identifier that is assigned automatically when the
application is first configured and is preserved during the whole application life
cycle. The valid format is a positive integer.
Bad Hits (%) The percentage of bucket hits in the metric bad value zone. The valid
format is a positive integer.
Bucket Number The bucket number of the baselining data. The valid format is a
positive integer.
EJB (%) The average percent of time that bucket requests were executed inside EJB
container. The valid format is a positive integer.
Fair Hits (%) The percentage of bucket hits in the metric fair value zone. The valid
format is a positive integer.
Good Hits (%) The percentage of bucket hits in the metric good value zone. The
valid format is a positive integer.
Hits (%) The percentage of hits for the bucket during the baselining. The valid
format is a positive integer.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
JCA (%) The average percent of time that bucket requests spent for JCA access.
The valid format is a positive integer.
JDBC (%) The average percent of time that bucket requests spent for JDBC access.
The valid format is a positive integer.
JMS (%) The average percent of time that bucket requests spent for JMS access.
The valid format is a positive integer.
JNDI (%) The average percent of time that bucket requests spent for JNDI access.
The valid format is a positive integer.
Lower Boundary (msec) The lower boundary of bucket response times in
milliseconds. The valid format is a positive integer.
Metric ID The metric identifier of the baselining data. The valid format is a
positive integer.
Metric Type The metric type of the baselining data. Valid formats are Request,
Error, and Resource.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Portal (%) The average percent of time that bucket requests were executed inside
portal container. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
317
Response Time Mean (msec) The mean time of bucket response times. The valid
format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 27. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Selection Hits (%) The percentage of bucket hits in the metric selection value zone.
The valid format is a positive integer.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Servlet JSP (%) The average percent of time that bucket requests were executed
inside the servlet container. The valid format is a positive integer.
Total Hits The total hits number for the bucket during the baselining. The valid
format is a positive integer.
Upper Boundary (msec) The upper boundary of bucket response times. The valid
format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Client Communications attributes
The Client Communications attributes display overall statistics about server-side
monitoring and a client-side API to retrieve performance data.
The attributes within this group are used to build the Client Communications
workspace.
Note: Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
318
ITCAM for Application Diagnostics: User Guide
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
API Connections The number of API sessions being used by clients that are
currently network connected to this application server. Some of these API
connections might be being by internal system processes on behalf of a client. The
valid format is a positive integer.
Buffered Read (bytes) The number of bytes of data that have been received from
the network and are held pending further processing. Large values might indicate
that the application server is unable to process data fast enough to keep up with
the clients attached. The valid format is a positive integer.
Buffered Write (bytes) The number of bytes of data being held pending
transmission. Large values might indicate network congestion or clients which are
unable to process data fast enough to keep up with the application server. The
valid format is a positive integer.
Clients Attached The number of distinct client processes currently network
connected to this application server. The valid format is a positive integer.
Errors The communication errors that have occurred and resulted in a network
connection to a client being disconnected. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the client communications.
For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum;
for WebSphere 6 or higher, the valid values are None, Basic, Extended, All,
Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Message Read (bytes) The number of bytes of message data received from client
processes over network connections. This does not include data used to negotiate
the transmission of messages. The valid format is a positive integer.
Messages Received at JMS 0 Priority (bytes) The number of messages received at
JMS priority 0. The valid format is a positive integer.
Messages Received at JMS 1 Priority (bytes) The number of messages received at
JMS priority 1. The valid format is a positive integer.
Messages Received at JMS 2 Priority (bytes) The number of messages received at
JMS priority 2. The valid format is a positive integer.
Messages Received at JMS 3 Priority (bytes) The number of messages received at
JMS priority 3. The valid format is a positive integer.
Messages Received at JMS 4 Priority (bytes) The number of messages received at
JMS priority 4. The valid format is a positive integer.
Messages Received at JMS 5 Priority (bytes) The number of messages received at
JMS priority 5. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
319
Messages Received at JMS 6 Priority (bytes) The number of messages received at
JMS priority 6. The valid format is a positive integer.
Messages Received at JMS 7 Priority (bytes) The number of messages received at
JMS priority 7. The valid format is a positive integer.
Messages Received at JMS 8 Priority (bytes) The number of messages received at
JMS priority 8. The valid format is a positive integer.
Messages Received at JMS 9 Priority (bytes) The number of messages received at
JMS priority 9. The valid format is a positive integer.
Messages Sent at JMS 0 Priority (bytes) The number of messages transmitted at
JMS priority 0. The valid format is a positive integer.
Messages Sent at JMS 1 Priority (bytes) The number of messages transmitted at
JMS priority 1. The valid format is a positive integer.
Messages Sent at JMS 2 Priority (bytes) The number of messages transmitted at
JMS priority 2. The valid format is a positive integer.
Messages Sent at JMS 3 Priority (bytes) The number of messages transmitted at
JMS priority 3. The valid format is a positive integer.
Messages Sent at JMS 4 Priority (bytes) The number of messages transmitted at
JMS priority 4. The valid format is a positive integer.
Messages Sent at JMS 5 Priority (bytes) The number of messages transmitted at
JMS priority 5. The valid format is a positive integer.
Messages Sent at JMS 6 Priority (bytes) The number of messages transmitted at
JMS priority 6. The valid format is a positive integer.
Messages Sent at JMS 7 Priority (bytes) The number of messages transmitted at
JMS priority 7. The valid format is a positive integer.
Messages Sent at JMS 8 Priority (bytes) The number of messages transmitted at
JMS priority 8. The valid format is a positive integer.
Messages Sent at JMS 9 Priority (bytes) The number of messages transmitted at
JMS priority 9. The valid format is a positive integer.
Message Written (bytes) The number of bytes of message data sent to client
processes over network connections. This does not include data used to negotiate
the transmission of messages. The valid format is a positive integer.
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
Multicast Send Messages The number of messages transmitted using multicast
protocols. The valid format is a positive integer.
Multicast Write The number of bytes transmitted using multicast protocols. The
valid format is a positive integer.
320
ITCAM for Application Diagnostics: User Guide
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Reads The number of read operations used to receive data from client processes
through network connections. The valid format is a positive integer.
Reads Blocked The number of read operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with client processes. The valid format is a positive integer.
Received at High Priority (bytes) The number of bytes of data received at a high
priority. Message data cannot be transmitted with this priority, so typically these
bytes of data will comprise control transmissions used to negotiate the flow of
messages. The valid format is a positive integer.
Received at Highest Priority (bytes) The number of bytes of data received at the
highest possible priority. Message data cannot be transmitted with this priority, so
typically these bytes of data will comprise control transmissions used to negotiate
the flow of messages. The valid format is a positive integer.
Received at JMS 0 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 0 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 1 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 1 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 2 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 2 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 3 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 3 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 4 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 4 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 5 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 5 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
Chapter 4. ITCAM Agent for WebSphere
321
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 6 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 6 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 7 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 7 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 8 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 8 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at JMS 9 Priority (bytes) The number of bytes of data received at the
priority used by JMS priority 9 messages. Typically this is an accurate measure of
the number of bytes of message data received at this priority level. However, from
time to time, control transmissions used to negotiate the flow of messages might be
transmitted at this priority level. The valid format is a positive integer.
Received at Low Priority (bytes) The number of bytes of data received at a low
priority. Message data cannot be transmitted with this priority, so typically these
bytes of data will comprise control transmissions used to negotiate the flow of
messages. The valid format is a positive integer.
Received at Lowest Priority (bytes) The number of bytes of data received at the
lowest possible priority. Message data cannot be transmitted with this priority, so
typically these bytes of data will comprise control transmissions used to negotiate
the flow of messages. The valid format is a positive integer.
Received at Very High Priority (bytes) The number of bytes of data received at a
very high priority. Message data cannot be transmitted with this priority, so
typically these bytes of data will comprise control transmissions used to negotiate
the flow of messages. The valid format is a positive integer.
Received at Very Low Priority (bytes) The number of bytes of data received at a
very low priority. Message data cannot be transmitted with this priority, so
typically these bytes of data will comprise control transmissions used to negotiate
the flow of messages. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 28. Format of the 12-character timestamp
Character String
Meaning
MM
Month
322
ITCAM for Application Diagnostics: User Guide
Table 28. Format of the 12-character timestamp (continued)
Character String
Meaning
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Sent at High Priority (bytes) The number of bytes of data transmitted at a high
priority. Message data cannot be transmitted with this priority, so typically these
bytes of data will comprise control transmissions used to negotiate the flow of
messages. The valid format is a positive integer.
Sent at Highest Priority (bytes) The number of bytes of data transmitted at the
highest possible priority for transmission. Message data cannot be transmitted with
this priority, so typically these bytes of data will comprise control transmissions
used to negotiate the flow of messages. The valid format is a positive integer.
Sent at JMS 0 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 0 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 1 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 1 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 2 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 2 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 3 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 3 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 4 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 4 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
Chapter 4. ITCAM Agent for WebSphere
323
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 5 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 5 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 6 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 6 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 7 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 7 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 8 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 8 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at JMS 9 Priority (bytes) The number of bytes of data transmitted at the
priority used by JMS priority 9 messages. Typically this is an accurate measure of
the number of bytes of message data transmitted at this priority level. However,
from time to time, control transmissions used to negotiate the flow of messages
might be transmitted at this priority level. The valid format is a positive integer.
Sent at Low Priority (bytes) The number of bytes of data transmitted at a low
priority. Message data cannot be transmitted with this priority, so typically these
bytes of data will comprise control transmissions used to negotiate the flow of
messages. The valid format is a positive integer.
Sent at Lowest Priority (bytes) The number of bytes of data transmitted at the
lowest priority. Message data cannot be transmitted with this priority, so typically
these bytes of data will comprise control transmissions used to negotiate the flow
of messages. The valid format is a positive integer.
Sent at Very High Priority (bytes) The number of bytes of data transmitted at a
very high priority. Message data cannot be transmitted with this priority, so
typically these bytes of data will comprise control transmissions used to negotiate
the flow of messages. The valid format is a positive integer.
Sent at Very Low Priority (bytes) The number of bytes of data transmitted at a
very low priority. Message data cannot be transmitted with this priority, so
typically these bytes of data will comprise control transmissions used to negotiate
the flow of messages. The valid format is a positive integer.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
324
ITCAM for Application Diagnostics: User Guide
Summary Whether this row is a summary row of statistical totals for all messaging
engines. Valid values are No and yes.
Total Read (bytes) The number of bytes of data received from client processes.
This includes both message data and data used to negotiate the transmission of
messages. The valid format is a positive integer.
Total Written (bytes) The number of bytes of data sent to client processes. This
includes both message data and data used to negotiate the transmission of
messages. The valid format is a positive integer.
Writes The number of write operations used to transmit data to client processes
via network connections. The valid format is a positive integer.
Writes Blocked The number of write operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with client processes. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Container Object Pools attributes
Use the Container Object Pools attributes in situations to monitor the effectiveness
of the object cache and of resource usage.
These attributes provide aggregated information for each defined EJB container
that aggregates bean object pool performance for all Enterprise beans deployed to
that container and aggregated information for the application server that
aggregates bean object pool performance data for all Enterprise beans deployed to
the application server. The attributes within this group are used to build the
Container Object Pools workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Average Objects Discarded The average number of objects discarded each time the
bean object pool was emptied of idle objects during the interval. The valid format
is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
325
Average Objects in Pool The average number of objects in the bean object pool
during the interval. The valid format is a decimal (formatted to 3 decimal places).
This value is an average of several values collected over an interval. The interval
can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Discard Count The number of times the object returned to the bean-object pool
was discarded because the bean object pool was already full during the interval.
The valid format is a positive integer.
Discard Rate (per sec) The bean object pool discard rate (per second) for the
interval since the previous sample. The valid format is a decimal (formatted to 3
decimal places).
Drain Count The number of times the bean object pool was found idle and an
attempt was made to remove idle objects during the interval. The valid format is a
positive integer.
Drain Rate (per sec) The number of times (per second) that the bean object pool
was found idle during the interval since the previous sample. The valid format is a
decimal (formatted to 3 decimal places).
Find Count The number of times a retrieval call found an available object in the
bean object pool during the interval. The valid format is a positive integer.
Find Rate (per sec) The availability of bean object pool retrievals (per second) for
the interval since the previous sample. The valid format is a decimal (formatted to
3 decimal places).
Get Count The number of calls retrieving an object from the bean object pool
during the interval. The valid format is a positive integer.
Get Rate (per sec) The number of bean objects retrieved (per second) for the
interval since the previous sample. The valid format is a decimal (formatted to 3
decimal places).
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
Instrumentation Level The instrumentation level for this container. For WebSphere
6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no
instrumentation level is set.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Return Count The number of calls returning an object to the bean object pool
during the interval. The valid format is a positive integer.
Return Rate (per sec) The bean objects returned (per second) for the interval since
the previous sample. The valid format is a decimal (formatted to 3 decimal places).
326
ITCAM for Application Diagnostics: User Guide
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 29. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of All Containers Whether this row is a summary row of statistical
totals aggregated over all bean object pools in the application server. Valid values
are No and Yes.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Container Transactions attributes
The Container Transactions attribute group provides performance information
about transactions that run in each defined EJB container and an aggregated value
for all transactions that run in the application server.
Use the Container Transactions attributes in situations to monitor transaction
activity for each EJB container and for the application server. The attributes within
this group are used to build the Container Transactions workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
Chapter 4. ITCAM Agent for WebSphere
327
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Global Transaction before Completion Duration (ms) The average duration before
completion for global transactions during the interval. The valid format is a
decimal (formatted to 3 decimal places).
Global Transaction Commit Duration (ms) The time (in milliseconds) that the
transaction required for its resolution phase during the interval. The valid format is
a decimal (formatted to 3 decimal places).
Global Transaction Commit Rate (per sec) The number of times (per second)
global transactions were committed during the interval. The valid format is a
decimal (formatted to 3 decimal places).
Global Transaction Duration (ms) The average duration (in milliseconds) for
global transactions during the interval. The valid format is a decimal (formatted to
3 decimal places).
Global Transaction Optimize Rate (per sec) The number of times (per second) that
global transactions were converted to single phase since the previous sample. The
valid format is a decimal (formatted to 3 decimal places).
Global Transaction Prepare Duration (ms) The average preparation duration (in
milliseconds) for global transactions during the interval. . The valid format is a
decimal (formatted to 3 decimal places).
Global Transaction Rollback Rate (per sec) The number of times (per second) that
global transactions were undone because they could not complete during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Global Transaction Timeout Rate (per sec) The number of global transaction
timeouts (per second) since the previous sample. The valid format is a decimal
(formatted to 3 decimal places).
Global Transaction Timeouts The number of global transactions that timed out
during the interval. The valid format is a positive integer.
Global Transactions Active The number of concurrently active global transactions
running in the container during the interval. Global transactions involve multiple
resource managers. The valid format is a decimal (formatted to 3 decimal places).
Global Transactions Begin Rate (per sec) The number of times global transactions
were started (per second) during the interval. The valid format is a decimal
(formatted to 3 decimal places).
Global Transactions Begun The total number of global transactions that the server
began during the interval. The valid format is a positive integer.
328
ITCAM for Application Diagnostics: User Guide
Global Transactions Committed The number of global transactions that were
completed during the interval. The valid format is a positive integer.
Global Transactions Involve Rate (per sec) The number of times (per second)
global transactions were involved during the interval. The valid format is a
positive integer.
Global Transactions Involved The number of global transactions that were
involved at the server during the interval, including those that were begun or
imported. The valid format is a positive integer.
Global Transactions Rolled Back The total number of global transactions that
were undone because they could not complete during the interval. The valid
format is a positive integer.
Global Transactions Optimized The number of global transactions converted to
single phase for optimization since the previous sample. The valid format is a
positive integer.
Instrumentation Level The instrumentation level for this container. For WebSphere
6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no
instrumentation level is set.
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
Local Transaction before Completion Duration (ms) The average duration before
completion for local transactions during the interval. The valid format is a decimal
(formatted to 3 decimal places).
Local Transaction Commit Duration (ms) The average duration for commit for
local transactions during the interval. The valid format is a decimal (formatted to 3
decimal places).
Local Transaction Commit Rate (per sec) The number of local transactions (per
second) committed during the interval. The valid format is a decimal (formatted to
3 decimal places).
Local Transaction Duration (ms) The average duration (in milliseconds) of local
transactions during the interval. The valid format is a decimal (formatted to 3
decimal places).
Local Transaction Rollback Rate (per sec) The number of times (per second) that
local transactions were undone because they could not be completed during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Local Transaction Timeout Rate (per sec) The number of local transactions that
timed out per second during the interval. The valid format is a decimal (formatted
to 3 decimal places).
Local Transaction Timeouts The number of local transactions that timed out
during the interval. The valid format is a positive integer.
Local Transactions Active The number of concurrently active local transactions
running in the container during the interval. Local transactions involve a single
resource manager. The valid format is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
329
Local Transactions Begin Rate (per sec) The number of times (per second) local
transactions were started during the interval. The valid format is a positive integer.
Local Transactions Begun The number of local transactions begun at the server
since the previous sample. The valid format is a positive integer.
Local Transactions Committed The number of local transactions committed during
the interval. The valid format is a positive integer.
Local Transactions Rolled Back The number of local transactions that were
undone during the interval. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 30. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Data sources attributes
The Data sources attributes provide database usage information.
330
ITCAM for Application Diagnostics: User Guide
These attributes provide traffic information such as, response times for database
requests, the frequencies at which database connections are created and destroyed,
and how often databases are being accessed. The attributes within this group are
used to build the Datasources workspace.
Note: The attributes within this attribute group contain meaningful values only if
your site has set the request data monitoring level to Level2 to collect data on data
source requests.
Application ID The unique identifier that is assigned automatically when the
application is first configured and is preserved during the whole application life
cycle. The valid format is a positive integer or -1 which means that Application ID
is aggregated statistic for all applications.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Average Processing Time (ms) The total average processing time (in milliseconds)
that the data source is used by an application. The valid format is a decimal
(formatted to 3 decimal places).
Average Query Processing Time (ms) The average time (in milliseconds) per
request used by queries to the data source. The valid format is a decimal
(formatted to 3 decimal places).
Average Update Processing Time (ms) The average time (in milliseconds) per
request used by updates to the data source. The valid format is a decimal
(formatted to 3 decimal places).
Connection Average Wait Time (ms) The average time (in milliseconds) that
applications had to wait for a connection. The valid format is a decimal (formatted
to 3 decimal places).
Connection Count The number of connections to the data source. The valid format
is a positive integer.
Connection Max Wait Time (ms) The worst-case time (in milliseconds) that
applications had to wait for a connection. The valid format is a positive integer.
Connection Rate (per sec) The number of connection requests (per second) created
for the data source. The valid format is a decimal (formatted to 3 decimal places).
Connection Total Wait Time (ms) The total time (in milliseconds) that applications
had to wait for a connection to the data source. The valid format is a positive
integer.
Database Product The name of the database product. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Database Product Version The version of the database product. The valid format is
an alphanumeric string, with a maximum of 128 characters.
Datasource Name The name of the data source. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Chapter 4. ITCAM Agent for WebSphere
331
Datasource Label A shortened version of Datasource Name, used to display the
data source name in the chart view. The valid format is an alphanumeric string,
with a maximum of 12 characters.
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the application server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The unique identifier of the process running the Java Virtual Machine
(JVM). The valid format is a positive integer.
Query Count The number of queries performed against the data source. The valid
format is a positive integer.
Query Rate (per sec) The number of queries (per second) being made to the data
source. The valid format is a decimal (formatted to 3 decimal places).
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 31. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Sampling Rate (%) The percentage of edge requests-such as servlets and JSPs-that
were sampled for data source requests during the interval. The valid format is a
positive integer.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
332
ITCAM for Application Diagnostics: User Guide
Total Query Processing Time (ms) The total time (in milliseconds) used to process
queries made to the data source. The valid format is a positive integer.
Total Update Processing Time (ms) The total time (in milliseconds) used to update
the data source. The valid format is a positive integer.
Total Wait Time (ms) The time (in milliseconds) that applications had to wait for
connections to the data source. The valid format is a positive integer.
Update Count The number of updates performed against the data source. The
valid format is a positive integer.
Update Rate (per sec) The number of updates (per second) made to the data
source. The valid format is a decimal (formatted to 3 decimal places).
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
DB Connection Pools attributes
The DB Connection Pools attributes provide information about the database
connection pool for each defined data source, and an aggregated value that
aggregates over all data sources.
Examples of DB Connection Pools include; the number of threads waiting for a
connection and the number of connections created and released. Use the DB
Connection Pools attributes to analyze JDBC performance for WebSphere
Application Server applications. The attributes within this group are used to build
the DB Connection Pools and the Pool Analysis workspaces.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Application ID Indicates J2EE application ID.
Average Free Pool Size Indicates the average size of the pool based upon the
number of free connections.
Average Pool Size The average size of the pool (based upon the number of
connections) during the interval. The valid format is a decimal (formatted to 3
Chapter 4. ITCAM Agent for WebSphere
333
decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Average Usage Time (ms) The average time (in milliseconds) a connection was in
use; blank if no transactions are completed during the interval. The valid format is
a decimal (formatted to 3 decimal places).
Average Wait Time (ms) The average time (in milliseconds) a client waited for a
connection; blank if no transactions are completed during the interval. The valid
format is a decimal (formatted to 3 decimal places).
Average Waiting Threads The average number of threads waiting for a connection
during the interval. The valid format is a decimal (formatted to 3 decimal places).
This value is an average of several values collected over an interval. The interval
can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Connection Allocation Rate (per sec) The connections allocated (per second) for
the interval since the previous sample. The valid format is a decimal (formatted to
3 decimal places).
Connection Creation Rate (per sec) The connections created (per second) during
the interval. The valid format is a decimal (formatted to 3 decimal places).
Connection Destruction Rate (per sec) The connections released (per second)
during the interval. The valid format is a positive integer.
Connection Handle Indicates the number of Connection objects in use for a
particular connection pool.
Connection Used The number of managed connection objects in use for a
particular EIS product name. The valid format is a positive integer.
Connections Allocated The number of connections allocated during the interval.
The valid format is a positive integer.
Connections Created The number of connections created during the interval. The
valid format is a positive integer.
Connections Destroyed The number of connections released during the interval.
The valid format is a positive integer.
Connections Granted The sum of connections allocated and connections created
during the interval. The valid format is a positive integer.
Datasource Label The abbreviated name of the data source. The valid format is an
alphanumeric string, with a maximum of 32 characters.
Datasource Name The name of the data source. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Instrumentation Level The instrumentation level for the database connection pool
for the data source. For WebSphere 5, the valid values are None, Low, Medium,
334
ITCAM for Application Diagnostics: User Guide
High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic,
Extended, All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
JDBC Time (ms) Indicates the amount of time spent running in the JDBC driver
which includes time spent in the JDBC driver, network, and database.
Maximum Pool Size The maximum number of connections that can be created in
this connection pool. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Pool Size Indicates the size of the connection pool.
Percent of Time Pool at Max The average percentage of time the number of
connections in the pool reached the maximum number during the interval. The
valid format is a decimal (formatted to 3 decimal places). This value is an average
of several values collected over an interval. The interval can be either between this
time and the previous time you activated this workspace, or fixed (normally 60
seconds), depending on the configuration of the Monitoring Agent.
Percent Used The average percentage of the connection pool in use during the
interval. The valid format is a decimal (formatted to 3 decimal places). This value
is an average of several values collected over an interval. The interval can be either
between this time and the previous time you activated this workspace, or fixed
(normally 60 seconds), depending on the configuration of the Monitoring Agent.
Percent Used Bad The bad percent of pool usage by application. The valid format
is a positive integer.
Percent Used Fair The fair percent of pool usage by application. The valid format
is a positive integer.
Percent Used Good The good percent of pool usage by application. The valid
format is a positive integer.
Prep Statement Cache Discard Rate (per sec) The cache discards (per second) of
prepared statements during the interval. The valid format is a decimal (formatted
to 3 decimal places).
Prep Statement Cache Discards The number of prepared statements discarded
from the cache during the interval. The valid format is a positive integer.
Pool Size Indicates the size of the connection pool.
Return Count The number of connections that applications returned to the pool
during the interval. The valid format is a positive integer.
Return Rate (per sec) The number of connections (per second) returned since the
previous sample. The valid format is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
335
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 32. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of All DB Connections Whether this row is a summary row of
statistical totals collected for all the DB connection pools. Valid values are No and
Yes.
Thread Timeout Rate (per sec) The number of threads (per second) that timed out
during the interval. The valid format is a decimal (formatted to 3 decimal places).
Threads Timed Out The number of threads that timed out while waiting for a
connection during the interval. The valid format is a positive integer.
Total Usage (ms) The total time (in milliseconds) the connection object used. The
valid format is a decimal (formatted to 3 decimal places).
Total Wait (ms) The total time (in milliseconds) the connection object waited. The
valid format is a decimal (formatted to 3 decimal places).
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
DC Messages attributes
The DC Messages attributes provide message information from WebSphere Data
Collector.
336
ITCAM for Application Diagnostics: User Guide
The attributes within this group are used to build the Log Analysis workspace.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Component The name of the component that caused the error. The value format is
an alphanumeric string, with a maximum of 32 characters.
Event Date and Time The date and time the event occurred. The valid format is a
12-character timestamp. For the STR and SCAN functions, the format is
MM/DD/YY HH:MM:SS; the following table shows the values contained in this
character string:
Table 33. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
File Name The name of the file. The valid format is an alphanumeric string, with a
maximum of 256 characters.
Message Description The description of the message. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Message ID The unique identifier of the message. The valid format is an
alphanumeric string, with a maximum of 8 characters.
Method Name The name of the method. The valid format is an alphanumeric
string, with a maximum of 256 characters.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID Indicates the process ID of the JVM.
Sequence Number The sequence number in the JMX notifications stream. The
valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
337
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Severity The severity of the message. Valid values are Info, Warning, Error, and
Severe.
Thread ID The identifier of the thread where the event occurred. The valid format
is an alphanumeric string, with a maximum of 16 characters.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
DCS Stack attributes
The DCS Stack attributes reports information about the statistical data within the
entire WebSphere Application Server domain, including multiple nodes and
servers.
Examples of DCS Stack attributes include; the incoming and outgoing message
size, the number of incoming and outgoing messages, congestion events, and
message buffer reallocations. The attributes within this group are used to build the
DCS Stacks workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Average Incoming Message Size The average size (in bytes) of the messages that
were received by the DCS stack. The valid format is a positive integer.
Average Outgoing Message Size The average size (in bytes) of the messages that
were sent through the DCS stack. The valid format is a positive integer.
Coalesce Time The amount of time it actually takes to coalesce a view. The valid
format is a decimal (formatted to 3 decimal places).
DCS Stack Name The name of the Topic Space. The value format is an
alphanumeric string, with a maximum of 256 characters.
Group Size The size of the group the local member belongs to. The valid format is
a positive integer.
338
ITCAM for Application Diagnostics: User Guide
High Severity Congestion Events The number of times that a high severity
congestion event for outgoing messages was raised. The valid format is a positive
integer.
Incoming Messages The number of messages received by the DCS stack. The valid
format is a decimal (formatted to 3 decimal places).
Instrumentation Level The instrumentation level for the DCS stack. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Join View Change Time The time to do a merge view change. The DCS stack is
blocked during this time. The valid format is a decimal (formatted to 3 decimal
places).
Maximum Incoming Message Size The maximal size (in bytes) of the messages
that were received by the DCS stack. The valid format is a positive integer.
Maximum Outgoing Message Size The maximal size (in bytes) of the messages
that were sent through the DCS stack. The valid format is a positive integer.
Message Buffer Reallocations The number of message buffer reallocations due to
inadequate buffer size. If this number is larger than 20 percent of the number of
sent messages, contact IBM Support. The valid format is a positive integer.
Minimum Incoming Message Size The minimal size (in bytes) of the messages
that were received by the DCS stack. The valid format is a positive integer.
Minimum Outgoing Message Size The minimal size (in bytes) of the messages
that were sent through the DCS stack. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Outgoing Messages The number of messages sent through the DCS stack. The
valid format is a positive integer.
Remove View Change Time The time to do a split view change. The DCS stack is
blocked during this time. The valid format is a decimal (formatted to 3 decimal
places).
Row Number The row number. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Chapter 4. ITCAM Agent for WebSphere
339
Table 34. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Sent Messages The number of messages sent through the DCS stack. The valid
format is a positive integer.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and yes.
Suspicions The number of times that the local member suspected other members.
The valid format is a positive integer.
Synchronization Completion Time The amount of time needed to guarantee that
all view members are synchronized. The valid format is a decimal (formatted to 3
decimal places).
Synchronization Timeouts The number of times that the synchronization
procedure timed out. The valid format is a positive integer.
View Changes The number of times that this member underwent view changes.
The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Durable Subscriptions attributes
The Durable Subscriptions attributes display overall statistics about the durable
subscriptions of a selected topic.
A durable subscription can be used to preserve messages published on a topic
while the subscriber is not active. The attributes within this group are used to
build the Durable Subscriptions workspace.
Note:
340
ITCAM for Application Diagnostics: User Guide
v The attributes in this attribute group contain zeros for performance data if your
site set configuration value Resource Data Collection Method to On Demand (for
on-demand sampling) and you have not yet run applications that generate
performance data. To report performance data in these attributes after installing
and configuring the Data Collector, use the WebSphere administrative console to
set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Aggregate Message Wait Time The time spent by messages in the bus at
consumption. If this time is not what was expected, view the message using the
admin console to decide what action needs to be taken. The valid format is a
positive integer.
Assured Persistent Messages Consumed The number of Assured Persistent
messages consumed, for the lifetime of this messaging engine. The valid format is
a positive integer.
Available Message The number of messages waiting to be consumed. The valid
format is a positive integer.
Best Effort Non-persistent Messages Consumed The number of best effort
non-persistent messages consumed, for the lifetime of this messaging engine. The
valid format is a positive integer.
Express Non-persistent Messages Consumed The number of express
non-persistent messages consumed, for the lifetime of this messaging engine. The
valid format is a positive integer.
Instrumentation Level The instrumentation level for the Durable Subscriptions.
For WebSphere 6 or higher, the valid values are None, Basic, Extended, All,
Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Local Oldest Message Age The longest time any message has spent on this
subscription. If this time is not what was expected, view the message using the
admin console to decide what action needs to be taken. The valid format is a
positive integer.
Local Message Wait Time The time spent by messages on this durable
subscription at consumption. If this time is not what was expected, view the
message using the admin console to decide what action needs to be taken. The
valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
341
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Reliable Non-persistent Messages Consumed The number of reliable
non-persistent messages consumed, for the lifetime of this messaging engine. The
valid format is a positive integer.
Reliable Persistent Messages Consumed The number of Reliable Persistent
messages consumed, for the lifetime of this messaging engine. The valid format is
a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 35. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Subscription Name The name of the subscriptions. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Topic Space Name The name of the topic space. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Total Messages Consumed The total number of messages consumed from this
durable subscription. The valid format is a positive integer.
342
ITCAM for Application Diagnostics: User Guide
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Dynamic Cache attributes
The Dynamic Cache attribute group provides information about the dynamic
cache.
WebSphere Application Server consolidates several caching activities, including
servlets, Web services, and WebSphere commands, into one service called the
dynamic cache. These caching activities work together to improve application
performance and share many configuration parameters, which are set in an
application server's dynamic cache service. The dynamic cache works within an
application server Java Virtual Machine (JVM), intercepting calls to cacheable
objects, for example, through a servlet's service method or a command's execute
method. It either stores the object's output to, or serves the object's content from,
the dynamic cache.
The attributes within this group are used to build the Cache Analysis workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Cache Instance Name Indicates the cache instance name.
Cache Instance Type Indicates Cache instance type.
Current In-Memory Cache Size The number of cache entries currently in memory.
The valid format is a positive integer.
In-Memory and Disk Timeout Rate (per sec) The rate (per second) of total
in-memory and disk timeouts for the sampling interval. The valid format is a
decimal (formatted to 3 decimal places).
In-Memory and Disk Timeouts The total number of in-memory and disk timeouts
during the sampling interval. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the dynamic cache. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Chapter 4. ITCAM Agent for WebSphere
343
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Maximum In-Memory Cache Size The maximum number of cache entries in
memory. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 36. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of Cache Indicates that this row is a summary row of statistical totals
collected for all the cache object types.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Dynamic Cache Templates attributes
The Dynamic Cache Templates attribute group provides information about the
cache template data.
344
ITCAM for Application Diagnostics: User Guide
A cache template is an object type defined by a cache policy specified in the
WebSphere Application Server cachespec.xml file. A cache policy specifies the
cache rules indicating what will be cached, the invalidation, timeout conditions,
and other data. The attributes within this group are used to build the Cache
Analysis workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Cache Instance Name The cache instance name.
Cache Instance Type The cache instance type.
Cache Miss Rate (per sec) The rate (per second) of requests for this cacheable
object type that were not found in the cache during the sampling interval. The
valid format is a decimal (formatted to 3 decimal places).
Cache Misses The number of requests for this cacheable object type that were not
found in the cache (in memory, on disk or on other cooperating caches); this would
have caused the underlying servlet or command to be executed in order to obtain
the results. The valid format is a positive integer.
Cache Object Type The name of the object type specified in the cache policy of the
cache spec XML file. The valid format is an alphanumeric string, with a maximum
of 256 characters.
Client Request Rate (per sec) The request rate (per second) for this cacheable
object type made by clients directly accessing this application server. The valid
format is a decimal (formatted to 3 decimal places).
Client Requests The number of requests for this cacheable object type made by
clients directly accessing this application server. The valid format is a positive
integer.
Cluster Request Rate (per sec) The request rate (per second) for this cacheable
object type made by cooperating caches in this cluster. The valid format is a
decimal (formatted to 3 decimal places).
Cluster Requests The number of requests for this cacheable object type made by
cooperating caches in this cluster. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
345
Current Cache Size The current number of entries for this cacheable object type
present in the dynamic cache. The valid format is a positive integer.
Disk Hit Rate (per sec) The rate (per second) of the requests for this cacheable
object type served from disk during the sampling interval. The valid format is a
decimal (formatted to 3 decimal places).
Disk Hits The number of requests for this cacheable object type that were served
from disk; this is applicable only when the disk offload is turned on for the
dynamic cache. The valid format is a positive integer.
Explicit Disk Invalidations Rate (per sec) The rate at which the entries of this
cacheable object type were removed from disk due to explicit invalidations issued
by the clients. The valid format is a decimal (formatted to 3 decimal places).
Explicit Disk Invalidations The number of entries of this cacheable object type
that were removed from disk due to explicit invalidations issued by the clients
(directly accessing the application server and by remote JVMs in the cluster). The
valid format is a positive integer.
Explicit Local Invalidation Rate (per sec) The rate at which the explicit
invalidations were received for this cacheable object type from clients accessing the
application server directly, either programmatically or by a cache policy. The valid
format is a decimal (formatted to 3 decimal places).
Explicit Local Invalidations The number of explicit invalidations received for this
cacheable object type from clients accessing the application server directly, either
programmatically or by a cache policy. The valid format is a positive integer.
Explicit Memory Invalidation Rate (per sec) The rate at which the entries of this
cacheable object type were removed from memory due to explicit invalidations
issued by the clients. The valid format is a decimal (formatted to 3 decimal places).
Explicit Memory Invalidations The number of entries of this cacheable object type
that were removed from memory due to explicit invalidations issued by the clients
(directly accessing the application server and by remote JVMs in the cluster). The
valid format is a positive integer.
Explicit Remote Invalidation Rate (per sec) The rate at which explicit
invalidations were received for this cacheable object type from cooperating JVMs in
the cluster. The valid format is a decimal (formatted to 3 decimal places).
Explicit Remote Invalidations The number of explicit invalidations received for
this cacheable object type from cooperating JVMs in the cluster. The valid format is
a positive integer.
Instrumentation Level The PMI instrumentation level set for collecting dynamic
cache data. For WebSphere 6 or higher, the valid values are None, Basic, Extended,
All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
346
ITCAM for Application Diagnostics: User Guide
Least Recently Used Invalidation Rate (per sec) The rate (per second) at which
entries of this cacheable object type were evicted from memory by a
least-recently-used algorithm. The valid format is a decimal (formatted to 3
decimal places).
Least Recently Used Invalidations The number of entries of this cacheable object
type that were evicted from memory by a least-recently-used algorithm. This
happens when the in-memory cache becomes full and subsequent requests for new
entries have to be accommodated. The entries removed from memory are
passivated to disk if disk overflow is enabled. If this number is high, consider
increasing the in-memory cache size. The valid format is a positive integer.
Memory Hit Rate (per sec) The rate (per second) of the requests for this cacheable
object type served from memory during the sampling interval. The valid format is
a decimal (formatted to 3 decimal places).
Memory Hits The number of requests for this cacheable object type served from
memory. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Remote Cache Entries Received The number of entries received from cooperating
dynamic caches in this cluster. The valid format is a positive integer.
Remote Cache Entry Receive Rate (per sec) The rate (per second) of entries
received from cooperating dynamic caches in this cluster for the sampling interval.
The valid format is a decimal (formatted to 3 decimal places).
Remote Hit Rate (per sec) The rate (per second) of the requests for this cacheable
object type served from other JVMs in the cluster during the sampling interval.
The valid format is a decimal (formatted to 3 decimal places).
Remote Hits The requests for this cacheable object type served from other JVMs in
the cluster. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 37. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Chapter 4. ITCAM Agent for WebSphere
347
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of Cache Templates Whether this row is a summary row of statistical
totals collected for all the cache object types. The valid values are No and Yes.
Template Row Number The number of the row in the report that displays in the
workspace, which is associated with a bar in the Ten Worst Hits Rate bar chart.
The valid format is an integer.
Timeout Invalidation Rate (per sec) The rate (per second) at which entries are
removed from the cache (memory or disk) because their timeout has expired. The
valid format is a decimal (formatted to 3 decimal places).
Timeout Invalidations The number of entries of this cacheable object type that
were removed from memory or disk because their timeout (as specified in the
cache spec XMLfile) has expired. The valid format is a positive integer.
Total Explicit Invalidation Rate (per sec) The rate at which invalidations were
issued for entries for this cacheable object type explicitly by the clients. The valid
format is a decimal (formatted to 3 decimal places).
Total Explicit Invalidations The number of invalidations issued for entries of this
cacheable object type explicitly by the clients (directly accessing the application
server and by remote JVMs in this cluster). The valid format is a positive integer.
Total Hit Rate (per sec) The total hit rate per second. The valid format is a decimal
(formatted to 3 decimal places).
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
EJB Containers attributes
The EJB Containers attributes provide aggregated information for each defined EJB
container that aggregates bean performance data for all Enterprise beans deployed
to that container.
The attributes also provide aggregated information for the application server that
aggregates bean performance data for all Enterprise beans deployed to the
application server. These attributes provide load values, response times, and
lifecycle activities for Enterprise beans. Use the EJB Containers attributes in
situations to monitor application server load and resource usage.
348
ITCAM for Application Diagnostics: User Guide
The attributes within this group are used to build the EJB Containers workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Activate Count The number of times a bean instance was activated during the
interval. The valid format is a positive integer.
Activation Rate (per sec) The bean activations (per second) during the interval.
The valid format is a decimal (formatted to 3 decimal places).
Active Method Count The average number of bean methods concurrently active
during the interval. The valid format is a decimal (formatted to 3 decimal places).
This value is an average of several values collected over an interval. The interval
can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Average Concurrently Live Beans The average number of bean objects
concurrently live during the sampling interval. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Average Concurrently Ready Beans The average number of beans concurrently
active during the last interval. The valid format is a decimal (formatted to 3
decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Create Average Time (ms) The average method response time for creates during
the interval. The valid format is a decimal (formatted to 3 decimal places).
Create Count The number of bean create calls during the interval. The valid
format is a positive integer.
Creation Rate (per sec) The bean create calls (per second) during the interval. The
valid format is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
349
Destroy Count The number of times bean objects were destroyed by garbage
collection during the interval. The valid format is a positive integer.
Destruction Rate (per sec) The beans destroyed by garbage collection (per second)
during the interval. The valid format is a decimal (formatted to 3 decimal places).
Entity Bean Load Count The number of times an entity bean data was loaded
during the interval. The valid format is a positive integer.
Entity Bean Load Rate (per sec) The number of entity beans (per second) that
were loaded during the interval. The valid format is a decimal (formatted to 3
decimal places).
Entity Bean Store Count The number of times entity bean data was written to the
database during the interval. The valid format is a positive integer.
Entity Bean Store Rate (per sec) The entity bean stores (per second) during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Instantiate Count The number of times bean objects were instantiated during the
interval. The valid format is a positive integer.
Instantiation Rate (per sec) The number of times bean objects were instantiated
(per second) during the interval. The valid format is a decimal (formatted to 3
decimal places).
Instrumentation Level The instrumentation level for this EJB container. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
Method Average Response Time (ms) The average response time (in milliseconds)
on remote interface methods for all beans during the interval. The valid format is a
decimal (formatted to 3 decimal places).
Method Invocation Count The number of method invocations during the interval.
The valid format is a positive integer.
Method Invocation Rate (per sec) The rate of invocations (per second) during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Passivate Count The number of times a bean instance was passivated during the
interval. The valid format is a positive integer.
Passivation Rate (per sec) The bean passivations (per second) during the interval.
The valid format is a decimal (formatted to 3 decimal places).
350
ITCAM for Application Diagnostics: User Guide
Removal Rate (per sec) The bean remove calls (per second) during the interval.
The valid format is a decimal (formatted to 3 decimal places).
Remove Average Time (ms) The average method response time for removes
during the interval. The valid format is a decimal (formatted to 3 decimal places).
Remove Count The number of bean remove calls during the interval. The valid
format is a positive integer.
Request Count The number of requests during the interval. The valid format is a
positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 38. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of All Containers Whether this row is a summary row of statistical
totals collected for all EJB containers. The valid values are No and Yes.
Total (ms) The total time used during the interval. The valid format is a decimal
(formatted to 3 decimal places).
Total Create (ms) The total time (in milliseconds) of bean create calls during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Total Method Invocation (ms) The total time (in milliseconds) of method
invocations during the interval. The valid format is a decimal (formatted to 3
decimal places).
Chapter 4. ITCAM Agent for WebSphere
351
Total Remove (ms) The total time (in milliseconds) of bean remove calls during the
interval. The valid format is a decimal (formatted to 3 decimal places).
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Enterprise Java Beans attributes
The Enterprise Java Beans attributes provide performance information about each
Enterprise Java Bean (EJB) deployed to the application server.
These attributes provide information about bean activity and bean object pool
activity. Use the Enterprise Java Beans attributes in situations to monitor
performance and problems for an individual bean. The attributes within this group
are used to build the Enterprise Java Beans workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then reselect it later. Each time you reselect
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Activate Count The number of times a bean instance was activated during the
interval. The valid format is a positive integer.
Activation Rate (per sec) The bean instance activations (per second) during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Active Method Count The average number of invocations being processed
concurrently for all the methods during the interval. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Application EJB Module Name The name of the Web Application or EJB Module.
The valid format is an alphanumeric string, with a maximum of 64 characters.
Average Concurrently Live Beans The average number of live bean objects during
the interval, which include objects that were instantiated but not yet destroyed.
This is a load value providing data on the average level as a function of time. It is
the average number of bean objects that exist in the run time, whether active or
pooled. This is a measure of how many resources the home interface is consuming.
352
ITCAM for Application Diagnostics: User Guide
The valid format is a decimal (formatted to 3 decimal places). This value is an
average of several values collected over an interval. The interval can be either
between this time and the previous time you activated this workspace, or fixed
(normally 60 seconds), depending on the configuration of the Monitoring Agent.
Average Concurrently Ready Beans The average number of active beans during
the interval. This is a load value providing data on the average level as a function
of time. It is the average number of bean instances of the home that are in the
ready state. This is a measure of how busy the server is. The valid format is a
decimal (formatted to 3 decimal places). This value is an average of several values
collected over an interval. The interval can be either between this time and the
previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Average Objects Discarded The average number of objects that were discarded
each time the bean object pool was emptied of idle objects during the interval. The
valid format is a decimal (formatted to 3 decimal places).
Average Objects in Pool The average number of objects in the bean object pool
during the interval. The valid format is a decimal (formatted to 3 decimal places).
This value is an average of several values collected over an interval. The interval
can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Bean Name The name of the Enterprise JavaBean (EJB). This name prefixes the
application name and the EJB jar name. The valid format is an alphanumeric
string, with a maximum of 128 characters.
Bean Type The type of bean. Valid values are Stateless, Stateful, Entity, and
Message Driven.
Create Average Time (ms) The average method response time to create bean
objects during the interval. The valid format is a decimal (formatted to 3 decimal
places).
Create Count The number of create calls during the interval. The valid format is a
positive integer.
Creation Rate (per sec) The create calls (per second) during the interval. The valid
format is a decimal (formatted to 3 decimal places).
Destroy Count The average number of times bean objects were destroyed by
garbage collection during the interval. The valid format is a positive integer.
Destruction Rate The rate of destructions (per second) for bean objects by the
garbage collector during the interval. The valid format is a decimal (formatted to 3
decimal places).
Discard Count The number of times the returned object to the bean object pool
was discarded because the bean object pool was already full during the interval.
The valid format is a positive integer.
Discard Rate (per sec) The bean object pool discards (per second) during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
353
Drain Count The number of times the bean object pool was found idle and an
attempt was made to remove idle objects during the interval. The valid format is a
positive integer.
Drain Rate (per sec) The drain rate (per second) for the bean object pool during
the interval. The valid format is a decimal (formatted to 3 decimal places).
Entity Bean Load Count The number of times bean data was loaded during the
interval. The valid format is a positive integer.
Entity Bean Load Rate (per sec) The bean data loads (per second) during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Entity Bean Store Count The number of times bean data was written to the
database during the interval. The valid format is a positive integer.
Entity Bean Store Rate (per sec) The rate at which data was written (per second)
to the database for the interval since the previous sample. The valid format is a
decimal (formatted to 3 decimal places).
Find Count The number of times a retrieval call found an object available in the
bean object pool during the interval. The valid format is a positive integer.
Find Rate (per sec) The bean object pool retrieve availability (per second) for the
interval since the previous sample. The valid format is a decimal (formatted to 3
decimal places).
Get Count The number of calls that retrieved an object from the bean object pool
during the interval. The valid format is a positive integer.
Get Rate (per sec) The number of times bean objects were retrieved (per second)
during the interval. The valid format is a decimal (formatted to 3 decimal places).
Instantiate Count The number of times bean objects were created during the
interval. The valid format is a positive integer.
Instantiation Rate (per sec) The bean objects created (per second) for the interval
since the previous sample. The valid format is a decimal (formatted to 3 decimal
places).
Instrumentation Level The instrumentation level of this enterprise bean. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
Method Average Response Time (ms) The average response time (in milliseconds)
for all methods of the remote interface for this bean during the interval. The valid
format is a decimal (formatted to 3 decimal places).
Method Invocation Rate (per sec) The invocations (per second) for all methods
during the sampling interval. This is a load value that provides data on the
average level as a function of time. This is a measure of how busy the server is.
The valid format is a decimal (formatted to 3 decimal places).
354
ITCAM for Application Diagnostics: User Guide
Method Invocations The total number of remote interface method invocations
during the interval. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Passivate Count The number of times a bean instance was passivated during the
interval. The valid format is a positive integer.
Passivation Rate (per sec) The number of passivations (per second) during the
interval since the previous sample. The valid format is a decimal (formatted to 3
decimal places).
Removal Rate (per sec) The remove calls (per second) for the interval since the
previous sample. The valid format is a decimal (formatted to 3 decimal places).
Remove Average Time (ms) The average method response time to remove bean
objects during the interval. The valid format is a decimal (formatted to 3 decimal
places).
Remove Count The number of remove calls during the interval. The valid format
is a positive integer.
Return Count The number of calls that returned an object to the bean object pool
during the interval. The valid format is a positive integer.
Return Rate (per sec) The bean object pool returns (per second) for the interval
since the previous sample. The valid format is a decimal (formatted to 3 decimal
places).
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 39. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Chapter 4. ITCAM Agent for WebSphere
355
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Garbage Collection Analysis attributes
The Garbage Collection Analysis attribute group provides information about the
garbage collector in the Java Virtual Machine that is hosting the application server.
The garbage collection attributes report the number of times the collector ran
during the interval and the resulting number of objects that the collector freed. Use
the Garbage Collection Analysis attributes in situations to monitor
garbage-collection performance and possible problems. The attributes within this
group are used to build the Garbage Collection Analysis and the WebSphere
Application Server workspaces.
ASID The identifier (decimal) assigned to the address space running this servant
region.
GC Rate (per min) The rate (per minute) at which the Java Virtual Machine is
invoking its garbage-collection routine. The valid format is a decimal (formatted to
3 decimal places).
Heap Used (%) The percentage of heap used at the end of the interval. The valid
format is a decimal (formatted to 1 decimal places).
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Kbytes Free The total number of free kilobytes in the heap at the end of the last
garbage-collection cycle during the interval. The valid format is a positive integer.
Kbytes Total Freed by GC The total number of kilobytes freed by the garbage
collector during the interval. The valid format is a positive integer.
Kbytes Used The number of kilobytes in the heap that were in use at the end of
the last garbage collection cycle during the interval. The valid format is a positive
integer.
Kbytes Used Delta The difference between the Kbytes Used value for this interval
and the Kbytes Used value for the prior interval. The valid format is a positive or
negative integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
356
ITCAM for Application Diagnostics: User Guide
Objects Freed The number of objects the garbage collector freed during the
interval (only supported for IBM JDK). The valid format is a positive integer. Not
monitored on non-IBM Java Virtual Machines, including those commonly used on
HP-UX and Solaris platforms.
Objects Moved The number of objects the garbage collector moved during the
interval (only supported for IBM JDK). The valid format is a positive integer. Not
monitored on non-IBM Java Virtual Machines, including those commonly used on
HP-UX and Solaris platforms.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Real Time (ms) The total real time (in milliseconds) the garbage collector required
during the most recent cycle. The valid format is a positive integer.
Real Time (%) The percentage of real time that the garbage collector was active
during the interval. The valid format is a decimal (formatted to 1 decimal place).
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 40. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Times Run The number of times the garbage collector ran during the interval. The
valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
357
v
Attribute groups used by the predefined workspaces
Garbage Collection Cycle attributes
The Garbage Collection Cycle attribute group provides information about a single
garbage-collection cycle that the Java Virtual Machine hosting the application
server performed.
The Garbage Collection Cycle attributes report the free heap space both before and
after garbage collection, the heap space freed, and the number of objects moved
during garbage collection. Use the Garbage Collection Cycle attributes in situations
to examine the results of a particular garbage collection.
The attributes within this group are used to build the Garbage Collections Selected Allocation Failure workspace.
Allocation Failure Number The identifier assigned to the allocation-failure block
for which the JVM ran the current garbage-collection cycle, which is associated
with a bar in the Heap Usage - History bar chart. If your Java code called
System.gc to invoke garbage collection, this number is 0. The valid format is a
positive integer.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Compact (ms) The time (in milliseconds) required for the compaction phase of the
garbage-collection cycle. The valid format is a positive integer.
Compaction Reason The code describing the reason garbage collection was
initiated. The valid format is a positive integer. The compaction codes are:
Table 41. Reasons for initiating garbage collection
Compaction Code
Definition
1
Insufficient free space for the allocation request following
the mark and sweep phases.
2
The heap is fragmented and will benefit from a
compaction.
3
Less than 15% free space available.
4
A call to System.gc requested garbage collection.
5
Less than 5% free space available.
6
Less than 128K free space available.
7
Parameter Xcompactgc specified.
8
The transient heap has less than 5% free space available.
9
The heap is fragmented (this code marks additional
reasons for compaction apart from compaction code 2).
Final References The number of final reference objects collected during this
garbage-collection cycle. The valid format is a positive integer.
Garbage Collection Date and Time The date and time the Java Virtual Machine
invoked the garbage collector. The valid format is a 16-character timestamp. This
attribute was designed for logging and reporting data-collection times rather than
358
ITCAM for Application Diagnostics: User Guide
for creating situations. To specify a time and date for comparison and testing, use
attributes from the Universal Time or Local Time groups.
Note to Solaris and HP-UX users: Since allocation-failure information is not recorded
on these platforms, this column is always empty on these platforms.
Garbage Collection Number The number of this garbage-collection cycle. The
valid format is a positive integer.
Heap Capacity (Kbytes) The total number of kilobytes allocated to the main heap
after this garbage-collection cycle. The valid format is a positive integer.
Heap Free (%) after GC The percentage of heap space that is available after this
garbage-collection cycle. The valid format is a decimal (formatted to 1 decimal
place).
Heap Space Free (Kbytes) The number of kilobytes available within the heap after
this garbage-collection cycle. The valid format is a positive integer.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
KBytes Free at Start of GC The number of kilobytes available in the heap before
garbage collection began. The valid format is a positive integer.
Kbytes Freed The number of kilobytes freed by the garbage collector. The valid
format is a positive integer.
Kbytes Moved The number of kilobytes moved on the heap during this
compaction. The valid format is a positive integer.
Kbytes Used The number of kilobytes in the heap that were in use after this
garbage-collection cycle. The valid format is a positive integer.
Mark (ms) The time (in milliseconds) required for the mark phase of the
garbage-collection cycle. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Objects Moved The number of objects the garbage collector moved during this
compaction. The valid format is a positive integer.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Phantom References The number of phantom reference objects collected during
this garbage-collection cycle. "Phantom" refers to a specific Java class that defines
object reachability. The valid format is a positive integer.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
Chapter 4. ITCAM Agent for WebSphere
359
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 42. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Soft References The number of soft reference objects collected during this
garbage-collection cycle. "Soft" refers to a specific Java class that defines object
reachability. The valid format is a positive integer.
Sweep (ms) The time (in milliseconds) required for the sweep phase of the
garbage-collection cycle. The valid format is a positive integer.
Time to Complete (ms) The time (in milliseconds) required to complete this
garbage-collection cycle. The valid format is a positive integer.
Weak References The number of weak reference objects collected during this
garbage-collection cycle. "Weak" refers to a specific Java class that defines object
reachability. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
High Availability Manager attributes
The High Availability Manager attributes provide aggregated information about
the high availability managers.
The attributes within this group are used to build the High Availability Manager
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
360
ITCAM for Application Diagnostics: User Guide
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Bulletin-Board Rebuild Time The time taken (in milliseconds) to rebuild the
global state of the bulletin-board. During this time no messages will be received by
the subscribers. If this time is too high, and is unacceptable, you may want to
increase the number of coordinators. The valid format is a decimal (formatted to 3
decimal places).
Bulletin-Board Subjects The total number of subjects managed. The valid format
is a positive integer. This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Bulletin-Board Subscriptions The total number of bulletin-board subscriptions.
The valid format is a positive integer. This value is an average of several values
collected over an interval. The interval can be either between this time and the
previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Group State Rebuild Time The time taken (in milliseconds) to rebuild the global
group state. During the rebuild time, no fail-over can happen. If this time is too
high and is unacceptable for the desired availability, you may want to increase the
number of coordinators. For proper operation of this counter, you must host the
active coordinator in an application server other than the deployment manager.
The valid format is a decimal (formatted to 3 decimal places).
Instrumentation Level The instrumentation level for availability manager counters.
For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum;
for WebSphere 6 or higher, the valid values are None, Basic, Extended, All,
Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Local Bulletin-Board Subjects The total number of subjects being posted to locally.
The number includes the proxy postings (if any) done by the core group bridge
service on behalf of servers belonging to different WebSphere cells. The valid
format is a positive integer. This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Local Bulletin-Board Subscriptions Indicates the total number of bulletin-board
subscriptions being posted to locally.
Chapter 4. ITCAM Agent for WebSphere
361
Local Groups The total number of local groups. The valid format is a positive
integer. This value is an average of several values collected over an interval. The
interval can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Row Number The row number. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 43. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
J2C Connection Pools attributes
The J2C Connection Pools attribute group provides information about connectors
that adhere to J2C, the WebSphere Application Server implementation of the J2C
architecture.
Data counters for this category contain usage information about the J2C
architecture that enables enterprise beans to connect and interact with procedural
362
ITCAM for Application Diagnostics: User Guide
backend systems, such as Customer Information Control System (CICS) and
Information Management System (IMS). Examples include the number of managed
connections or physical connections and the total number of connections or
connection handles.
The attributes within this group are used to build the J2C Connection Pools
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Application ID Indicates J2EE application ID.
Average Free Connections The average number of free Managed Connections for
the interval. The valid format is a decimal (formatted to 3 decimal places). This
value is an average of several values collected over an interval. The interval can be
either between this time and the previous time you activated this workspace, or
fixed (normally 60 seconds), depending on the configuration of the Monitoring
Agent.
Average Pool Size The average number of Managed Connections for the interval.
The valid format is a decimal (formatted to 3 decimal places). This value is an
average of several values collected over an interval. The interval can be either
between this time and the previous time you activated this workspace, or fixed
(normally 60 seconds), depending on the configuration of the Monitoring Agent.
Average Usage Time (ms) The average time (in milliseconds) that connections are
in use (measured from when the connection is allocated to when it is returned).
The valid format is a decimal (formatted to 3 decimal places).
Average Wait Time (ms) The average waiting time (in milliseconds) until a
connection is granted for the interval. The valid format is a decimal (formatted to 3
decimal places).
Concurrent Waiting Threads The average number of threads concurrently waiting
for a connection for the interval. The valid format is a positive integer. This value
is an average of several values collected over an interval. The interval can be either
between this time and the previous time you activated this workspace, or fixed
(normally 60 seconds), depending on the configuration of the Monitoring Agent.
Chapter 4. ITCAM Agent for WebSphere
363
Connection Allocation Rate (per sec) The rate (per second) of application
connections allocated from Managed Connections for the sampling interval. The
valid format is a decimal (formatted to 3 decimal places).
Connection Creation Rate (per sec) The rate (per second) of Managed Connections
created for the sampling interval. The valid format is a decimal (formatted to 3
decimal places).
Connection Destruction Rate (per sec) The rate (per second) of Managed
Connections destroyed for the sampling interval. The valid format is a decimal
(formatted to 3 decimal places).
Connection Factory Name The name of the connection factory. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Connection Handles The number of open application connections that have been
allocated from the managed connections. The valid format is a positive integer.
Connection Pool Timeout Rate (per sec) The rate (per second) of connection pool
timeouts for the sampling interval. The valid format is a decimal (formatted to 3
decimal places).
Connection Pool Timeouts The number of faults, such as timeouts, in connection
pools for the sampling interval. The valid format is a positive integer.
Connection Return Rate (per sec) The rate (per second) of allocated application
connections that have been returned for the sampling interval. The valid format is
a decimal (formatted to 3 decimal places).
Connections Allocated The number of application connections allocated from
Managed Connections. The valid format is a positive integer.
Connections Created The total number of Managed Connections created during
the sampling interval. The valid format is a positive integer.
Connections Destroyed The number of Managed Connections destroyed during
the sampling interval. The valid format is a positive integer.
Connections Granted The number of Managed Connections granted during the
interval. The valid format is a positive integer.
Connections Returned The number of allocated application connections that have
been returned (closed) during the sampling interval. The valid format is a positive
integer.
Connections Used The number of Managed Connection objects available in a
particular connection pool; this number includes all Managed Connection objects
that have been created but not destroyed. The valid format is a positive integer.
Factory Label The abbreviated name of the connection factory. The valid format is
an alphanumeric string, with a maximum of 32 characters.
Instrumentation Level The instrumentation level for the J2C connection pools. For
WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
364
ITCAM for Application Diagnostics: User Guide
Interval Time The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Maximum Pool Size The maximum number of managed connections that can be
created in this connection pool (blank for each individual managed connection).
The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Percent of Time Pool at Max The average percent of the time that all connections
are in use for the interval. The valid format is a decimal (formatted to 3 decimal
places). This value is an average of several values collected over an interval. The
interval can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Percent Used Bad The bad percent of pool usage by application. The valid format
is a positive integer.
Percent Used Fair The fair percent of pool usage by application. The valid format
is a positive integer.
Percent Used Good The good percent of pool usage by application. The valid
format is a positive integer.
Pool Used (%) The average percent of the pool that is in use for the interval. The
valid format is a decimal (formatted to 3 decimal places). This value is an average
of several values collected over an interval. The interval can be either between this
time and the previous time you activated this workspace, or fixed (normally 60
seconds), depending on the configuration of the Monitoring Agent.
Row Number The number of the row within the report, which corresponds to a
bar in the Highest Miss Rates bar chart. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 44. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Chapter 4. ITCAM Agent for WebSphere
365
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of J2C Connections Whether this row is a summary row of statistical
totals collected for all the J2C connection pools. Valid values are No and Yes.
Total Usage (ms) The total time (in milliseconds) the connection object used. The
valid format is a decimal (formatted to 3 decimal places).
Total Wait (ms) The total time (in milliseconds) the connection object waited. The
valid format is a decimal (formatted to 3 decimal places).
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
JMS Summary attributes
The JMS Summary attributes provide information about how WebSphere
Application Server applications are interacting with messaging middleware
(WebSphere MQ) using the Java Messaging Service (JMS). It provides such
information as which queue managers and queues are being used and how many
messages are being read and written.
The attributes within this group are used to build the JMS Summary workspace.
Note: The attributes within this attribute group contain meaningful values only if
your site has set the request data monitoring level to Level2 to collect data on JMS
requests.
Application ID The unique identifier that is assigned automatically when the
application is first configured and is preserved during the whole application life
cycle. The valid format is a positive integer or -1 which means that Application ID
is aggregated statistic for all applications.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Average Processing Time (ms) The average time (in milliseconds) per request
using the JMS. The valid format is a decimal (formatted to 3 decimal places).
Browse Average Time (ms) The average time (in milliseconds) for each browse
request from the queue. The valid format is a decimal (formatted to 3 decimal
places).
366
ITCAM for Application Diagnostics: User Guide
Browse Count The number of messages browsed from the queue. The valid format
is a positive integer.
Browse Rate (per sec) The number of messages (per second) browsed from a JMS
queue. The valid format is a decimal (formatted to 3 decimal places).
Browse Total Time (ms) The total time (in milliseconds) consumed by browse
requests from the queue. The valid format is a positive integer.
Full Name The complete name of the message queue, which consists of the queue
manager name concatenated to the queue name and separated by a slash. The
valid format is an alphanumeric string, with a maximum of 100 characters.
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
JMS Connection Label A shortened version of the full name. The valid format is
an alphanumeric string, with a maximum of 12 characters.
Manager Name The name of the WebSphere MQ queue manager. This attribute is
blank if WebSphere MQ is not being used. The valid format is an alphanumeric
string, with a maximum of 48 characters.
Name The name of the WebSphere MQ queue. The valid format is an
alphanumeric string, with a maximum of 48 characters.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the application server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Publish Average Time (ms) The average time (in milliseconds) for each publish
request to be sent to the queue. The valid format is a decimal (formatted to 3
decimal places).
Publish Count The number of publish requests sent to the queue. The valid format
is a positive integer.
Publish Rate (per sec) The number of publish requests (per second) sent to a JMS
queue. The valid format is a decimal (formatted to 3 decimal places).
Publish Total Time (ms) The total time (in milliseconds) consumed by all publish
requests for the queue. The valid format is a positive integer.
Receive Average Time (ms) The average time (in milliseconds) for each get from
the queue. The valid format is a decimal (formatted to 3 decimal places).
Receive Count The number of destructive gets from the queue. The valid format is
a positive integer.
Receive Rate (per sec) The number of destructive gets (per second) made from the
queue. The valid format is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
367
Receive Total Time (ms) The total time (in milliseconds) consumed by gets from
the queue. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 45. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Send Average Time (ms) The average time (in milliseconds) for each put to the
queue. The valid format is a decimal (formatted to 3 decimal places).
Send Count The number of messages put to the queue. The valid format is a
positive integer.
Send Rate (per sec) The number of messages (per second) put to the queue. The
valid format is a decimal (formatted to 3 decimal places).
Send Total Time (ms) The total time (in milliseconds) consumed by puts to the
queue. The valid format is a positive integer.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Total Time (ms) The total time (in milliseconds) spent accessing the queue. The
valid format is a positive integer.
Type The type of message manager. the valid values are Queue and Topic.
For additional information, see:
v
v
368
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
ITCAM for Application Diagnostics: User Guide
Log Analysis attributes
The Log Analysis attributes provide application server error and exception
conditions which are recorded in the application server log files.
The log files are SystemOut.log and SystemErr.log. Use the Log Analysis attributes
in situations to monitor errors and exception conditions and their severity.
The attributes within this group are used to build the Log Analysis workspace.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Component The name of the component that caused the error. The valid format is
an alphanumeric string, with a maximum of 32 characters.
Error Date and Time The date and time the event occurred. The valid format is a
timestamp. This attribute was designed for logging and reporting data-collection
times rather than for creating situations. To specify a time and date for comparison
and testing, use attributes from the Universal Time or Local Time groups.
Job ASID The identifier (hexadecimal) assigned to the address space running this
servant region. The valid format is an alphanumeric string, with a maximum of 4
characters.
Job Name The job name assigned to this servant region. The valid format is an
alphanumeric string, with a maximum of 8 characters.
Message ID The identifier assigned to the message. The valid format is an
alphanumeric string, with a maximum of 12 characters.
Message Origin Where the message originates; that is, the log file name and line
number. The valid format is an alphanumeric string, with a maximum of 32
characters. This field is not empty only on the z/OS system.
Message Text The text of the message. The valid format is alphanumeric string,
with a maximum of 256 characters. All error message text data that goes beyond
256 characters are truncated and are not shown in the portal.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The process identifier of the Java virtual machine. The valid format is
an alphanumeric string, with a maximum of 8 characters. In a z/OS system, this
field displays in hexadecimal format.
Sequence Number The sequence number in the JMX notifications stream. The
valid format is positive integer.
Server Instance Name The name of the application server instance. This is the
name of a single address space that can run application code (called a "specific
server" or simply a "server"). The valid format is an alphanumeric string, with a
maximum of 8 characters.
Chapter 4. ITCAM Agent for WebSphere
369
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Severity The severity of the message. The valid values are:
Table 46. Message severities and their meanings
Severity
Definition
Informational
A message intended to convey only user information
Unconditional
A message of type Unconditional
Dump
A message of type Dump
SystemOut
A message written directly to System.out by the user
application or internal components
SystemError
A message written directly to System.err by the user
application or internal components
User
A message of type User
EntryMethod
A message written upon entry to a method
ExitMethod
A message written upon exit from a method
Event
A message of type Event
Debug
A message of type Debug
Audit
An audit message
Warning
A warning message
Error
An error message
Terminate
A message of type Terminate (exit process)
Fatal
A fatal message
Unknown
A placeholder that indicates the message type was not
recognized
Thread ID The unique identifier of the thread where the event occurred. The valid
format is an alphanumeric string, with a maximum of 16 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Messaging Engine Communications attributes
The Messaging Engine Communications attributes display statistics for all the
messaging engines being hosted by the current application server.
The attributes within this group are used to build the Messaging Engine
Communications workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
370
ITCAM for Application Diagnostics: User Guide
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
API Connections The number of sessions being used by messaging engines that
are currently network connected to this application server. The valid format is a
positive integer.
Buffered Reads (bytes) The number of bytes of data that have been received from
the network and are held pending further processing. Large values might indicate
that the application server is unable to process data fast enough to keep up with
the other application server processes hosting messaging engines that it is network
attached. The valid format is a positive integer.
Buffered Writes (bytes) The number of bytes of data being held pending
transmission. Large values might indicate network congestion or application server
processes hosting messaging engines which are unable to process data fast enough
to keep up with the application server. The valid format is a positive integer.
Errors The communication errors that have occurred and resulted in a network
connection to a messaging engine being disconnected. The valid format is a
positive integer.
Instrumentation Level The instrumentation level for the Messaging Engine
Communications. For WebSphere 6 or higher, the valid values are None, Basic,
Extended, All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Message Read (bytes) The number of bytes of message data received from
application server processes hosting messaging engines over network connections.
This does not include data used to negotiate the transmission of messages. The
valid format is a positive integer.
Message Written (bytes) The number of bytes of message data sent to application
server processes hosting messaging engines over network connections. This does
not include data used to negotiate the transmission of messages. The valid format
is a positive integer.
Messaging Engine Attached The number of distinct application server processes
hosting messaging engines currently network connected to this application server.
The valid format is a positive integer.
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
Chapter 4. ITCAM Agent for WebSphere
371
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Reads The number of read operations used to receive data from application server
processes hosting messaging engines via network connections. The valid format is
a positive integer.
Reads Blocked The number of read operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with application server processes hosting messaging engines. The
valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 47. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all messaging
engine communications. Valid values are No and Yes.
Total Read (bytes) The Number of bytes of data received from application server
processes hosting messaging engines. The valid format is a positive integer.
Total Written (bytes) The Number of bytes of data sent to application server
processes hosting messaging engines. The valid format is a positive integer.
Writes The number of write operations used to transmit data to application server
processes hosting messaging engines via network connections. The valid format is
a positive integer.
372
ITCAM for Application Diagnostics: User Guide
Writes Blocked The number of write operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with application server processes hosting messaging engines. The
valid format is a positive integer.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Messaging Engines attributes
The Messaging Engines attributes display aggregated information about the
performance of the messaging engines supported by WebSphere server.
The attributes within this group are used to build the Messaging Engines
workspace.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Note: Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Average Local Wait Time (ms) The time spent by messages on this durable
subscription at consumption. If this time is not what was expected, view the
message using the admin console to decide what action needs to be taken. The
valid format is a positive integer.
Expired Messages The number of report enabled messages that expired while on
this queue. The valid format is a positive integer.
Incomplete Topic Publications The number of publications not yet received by all
current subscribers. If this number is unexpected, view the publication using the
admin console to take any actions. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the messaging engines. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Messaging Engine Name The name of the message engine. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
Chapter 4. ITCAM Agent for WebSphere
373
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 48. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Status The status of the message engine. The valid format is a positive integer.
Summary of All Applications Whether this row is a summary row of statistical
totals for all messaging engines. Valid values are No and Yes.
Total Published The total number of publications to the message engines. The
valid format is a positive integer.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Portal Page Summary attributes
The Portal Page Summary attributes provide information about response times
statistics for all portal page requests that completed on monitored WebSphere
Portal server during the interval.
The attributes within this group are used to build the Portal Pages Summary
workspace.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Average Response Time (ms) The average response time (in milliseconds) of
requests processed by the portal pages during the current interval. The valid
format is a decimal (formatted to 3 decimal places).
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
374
ITCAM for Application Diagnostics: User Guide
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Portal Page Name The name of the portal page. The value format is an
alphanumeric string, with a maximum of 128 characters.
Request Count The count of requests processed by the portlet page during the
current interval. The valid format is a positive integer.
Row Number The number of the row. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 49. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Total Response (ms) The total time (in milliseconds) of responses. The valid format
is a decimal (formatted to 3 decimal places).
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
375
Portal Summary attributes
The Portal Summary attributes provide aggregated response times statistics about
all portal pages and portlet requests that completed on monitored WebSphere
Portal server during the interval.
The attributes within this group are used to build the Portal Summary workspace.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Authentication Request Count The number of authentication requests during the
interval. The valid format is a positive integer.
Authentication Total (ms) The total time (in milliseconds) of authentication
requests completed during the interval. The valid format is a decimal (formatted to
3 decimal places).
Authorization Request Count The number of authorization requests during the
interval. The valid format is a positive integer.
Authorization Total (ms) The total time (in milliseconds) of authorization requests
completed during the interval. The valid format is a decimal (formatted to 3
decimal places).
Average Response Time of Portal Pages (ms) The average response time (in
milliseconds) of all portal pages/Gateway Servlet requests completed during the
interval. The valid format is a decimal (formatted to 3 decimal places).
Average Response Time of Portlets (ms) The average response time (in
milliseconds) of all portlets requests completed during the interval. The valid
format is a decimal (formatted to 3 decimal places).
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Model Building Request Count The number of model building requests during
the interval. The valid format is a positive integer.
Model Building Total (ms) The total time (in milliseconds) of model building
requests completed during the interval. The valid format is a decimal (formatted to
3 decimal places).
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Page Loading Request Count The number of page loading requests during the
interval. The valid format is a positive integer.
Page Loading Total (ms) The total time (in milliseconds) of page loading requests
completed during the interval. The valid format is a decimal (formatted to 3
decimal places).
376
ITCAM for Application Diagnostics: User Guide
Portal Page Request Count The number of portal page requests during the
interval. The valid format is a positive integer.
Portal Pages Total Response (ms) The total response time (in milliseconds) of all
portal pages/Gateway Servlet requests completed during the interval. The valid
format is a decimal (formatted to 3 decimal places).
Portlets Request Count The number of portlets requests during the interval. The
valid format is a positive integer.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Portlets Total Response(ms) The total response time (in milliseconds) of all
portlets requests completed during the interval. The valid format is a decimal
(formatted to 3 decimal places).
Response Time of Authentication (ms) The response time (in milliseconds) of
authentication. The valid format is a positive integer.
Response Time of Authorization (ms) The response time (in milliseconds) of
authorization. The valid format is a positive integer.
Response Time of Model Building (ms) The response time (in milliseconds) of
model building. The valid format is a positive integer.
Response Time of Page loading (ms) The response time (in milliseconds) of page
loading. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 50. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Chapter 4. ITCAM Agent for WebSphere
377
Summary Indicates that this row is a summary row of statistical totals for all rows.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Portlet Summary attributes
The Portlet Summary attributes provide information about response times of all
portlet requests that completed on monitored WebSphere Portal.
The attributes within this group are used to build the Portlet Summary workspace.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Average Response Time (ms) The average response time for portlet during the
current interval. The valid format is a decimal (formatted to 3 decimal places).
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Portlet Name The name of the portlet. The value format is an alphanumeric string,
with a maximum of 256 characters.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Request Count The count of requests for portlet during the current interval. The
valid format is a positive integer.
Request Rate The rate at which the requests processed by portlet during the
current interval. The valid format is a decimal (formatted to 3 decimal places).
Row Number The number of the row. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 51. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
378
ITCAM for Application Diagnostics: User Guide
Table 51. Format of the 12-character timestamp (continued)
Character String
Meaning
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Total Response (ms) The total response time for portlet during the current interval.
The valid format is a decimal (formatted to 3 decimal places).
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Queue attributes
The Queue attributes provide aggregated information about the point to point
messaging.
The attributes within this group are used to build the Destinations workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Aggregate Message Wait Time The time spent by messages in the bus at
consumption. If this time is not what was expected, view the message using the
admin console to decide what action needs to be taken. The valid format is a
positive integer.
Assured Persistent Messages Consumed The number of assured persistent
messages consumed, for the lifetime of this messaging engine. The valid format is
a positive integer.
Chapter 4. ITCAM Agent for WebSphere
379
Assured Persistent Messages Produced The number of assured persistent
messages produced, for the lifetime of this messaging engine. The valid format is a
positive integer.
Available Message The number of messages available for a queue for
consumption. If this number is close to the destination high messages value,
review the high messages value. The valid format is a positive integer.
Best Effort Non-persistent Messages Consumed The number of best effort
non-persistent messages consumed, for the lifetime of this messaging engine. The
valid format is a positive integer.
Best Effort Non-persistent Messages Produced The number of best effort
non-persistent messages produced, for the lifetime of this messaging engine. The
valid format is a positive integer.
Express Non-persistent Messages Consumed The number of express
non-persistent messages consumed, for the lifetime of this messaging engine. The
valid format is a positive integer.
Express Non-persistent Messages Produced The number of express non-persistent
messages produced, for the lifetime of this messaging engine. The valid format is a
positive integer.
Instrumentation Level The instrumentation level for the database connection pool
for the data source. Valid values are None, Low, Medium, High, Basic, Extended,
All, Custom, and Maximum. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Local Consumer The number of currently attached local consumers. The valid
format is a positive integer.
Local Consumer Attaches The number of times an attachment has been made to
this queue by local consumers. The lifetime of this value is the lifetime of the
messaging engine. The valid format is a positive integer.
Local Message Wait Time The time spent by messages on this queue at
consumption. If this time is not what was expected, view the message using the
admin console to decide what action needs to be taken. The valid format is a
positive integer.
Local Oldest Message Age The longest time any message has spent on this queue.
If this time is not what was expected, view the message using the admin console
to decide what action needs to be taken. The valid format is a positive integer.
Local Producer The number of currently attached local producers. The valid format
is a positive integer.
Local Producer Attaches The number of times an attachment has been made to
this queue by local producers. The lifetime of this value is the lifetime of the
messaging engine. The valid format is a positive integer.
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
380
ITCAM for Application Diagnostics: User Guide
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Queue Name The name of the queue. The value format is an alphanumeric string,
with a maximum of 256 characters.
Reliable Non-persistent Messages Consumed The number of reliable
non-persistent messages consumed, for the lifetime of this messaging engine. The
valid format is a positive integer.
Reliable Non-persistent Messages Produced The number of reliable non-persistent
messages produced, for the lifetime of this messaging engine. The valid format is a
positive integer.
Reliable Persistent Messages Consumed The number of reliable persistent
messages consumed, for the lifetime of this messaging engine. The valid format is
a positive integer.
Reliable Persistent Messages Produced The number of reliable persistent
messages produced, for the lifetime of this messaging engine. The valid format is a
positive integer.
Report Enabled Messages Expired The number of report enabled messages that
expired while on this queue. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 52. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Chapter 4. ITCAM Agent for WebSphere
381
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Total Messages Consumed The total number of messages consumed from this
queue, for the lifetime of this messaging engine. The valid format is a positive
integer.
Total Messages Produced The total number of messages produced to this queue,
for the lifetime of this messaging engine. The valid format is a positive integer.
Unavailable Message The number of messages locked or uncommitted. This
means messages that have been added or removed but the transaction has not
been committed yet. If this number is high, check which messages are locked and
why.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Remote Configuration Requests attributes
The Remote Configuration Requests attributes provide information about remote
configuration.
The attributes within this group are used to build the WebSphere Agent
workspace.
Command Indicates the Command of the request.
Node Name The system on which the server is running. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Origin Node Indicates the server name subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Package Count Indicates the package count for this request/response.
Package Index Indicates the current index of the packages.
Request Context Indicates the request context.
Response Context Indicates the response context.
Request Identifier Indicates Request ID.
Return Value Indicates the return value of the request.
Target Agent Code Two-letter agent product code that specifies information about
the product being configured.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
382
ITCAM for Application Diagnostics: User Guide
Request Analysis attributes
The Request Analysis attributes provide response times and functional
decomposition information about requests (servlets, JSPs, and EJB methods) that
ran on the application server.
The attributes within this group are used to build the Request Analysis workspace.
Application Name The name of the application to which the request belongs. The
valid format is an alphanumeric string, with a maximum of 256 characters.
Application Time (ms) The average time (in milliseconds) this request spent
processing application requests other than JCA, JMS, JNDI, and JDBC requests; this
field can have a zero value if the total time is less than the number of requests,
due to truncation. The valid format is a positive integer.
Application Time (% of Average Response) The percentage of time this request
spent processing application requests other than JCA, JMS, JNDI, and JDBC
requests. The valid format is a decimal (formatted to 1 decimal place).
Application Bad Delay (msec) The delay time (in milliseconds) in the application
tier collected during the interval. This column is non-zero value when application
delay exceeds the bad threshold configured for it. The valid format is a positive
integer.
Application Fair Delay (msec) The delay time (in milliseconds) in the application
tier collected during the interval. This column is non-zero value when application
delay exceeds the fair threshold configured for it. The valid format is a positive
integer.
Application Good Delay (msec) The delay time (in milliseconds) in the application
tier collected during the interval. This column is non-zero when application delay
is less than fair threshold configured for it. The valid format is a positive integer.
Application Tier Delay Type This attribute defines the request type based on its
delay time in the application tier. Valid values are Unknown, Good, Fair, and Bad.
Application Tier Response (msec) The actual response time in milliseconds in the
application tier collected during the interval. The valid format is a positive integer.
Average Response (ms) The average time (in milliseconds) required each time this
request ran during the interval. The valid format is a positive integer.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Backend Bad Delay (msec) The delay time (in milliseconds) in the backend tier
collected during the interval. This column is non-zero value when backend delay
exceeds the bad threshold configured for it. The valid format is a positive integer.
Backend Fair Delay (msec) The delay time (in milliseconds) in the backend tier
collected during the interval. This column is non-zero value when backend delay
exceeds the fair threshold configured for it. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
383
Backend Good Delay (msec) The delay time (in milliseconds) in the backend tier
collected during the interval. This column is non-zero when backend delay is less
than fair threshold configured for it. The valid format is a positive integer.
Backend Tier Delay Type This attribute defines the request type based on its delay
time in the backend tier. Valid values are Unknown, Good, Fair, and Bad.
Backend Tier Response (msec) The actual response time in milliseconds in the
backend tier collected during the interval. The valid format is a positive integer.
Client Bad Delay (msec) The delay time (in milliseconds) in the client tier
collected during the interval. This column is non-zero value when client delay
exceeds the bad threshold configured for it. The valid format is a positive integer.
Client Fair Delay (msec) The delay time (in milliseconds) in the client tier
collected during the interval. This column is non-zero value when client delay
exceeds the fair threshold configured for it. The valid format is a positive integer.
Client Good Delay (msec) The delay time (in milliseconds) in the client tier
collected during the interval. This column is non-zero when client delay is less
than fair threshold configured for it. The valid format is a positive integer.
Client Tier Delay Type This attribute defines the request type based on its delay
time in the client tier. Valid values are Unknown, Good, Fair, and Bad.
Client Tier Response (msec) The actual response time in milliseconds in the client
tier collected during the interval. The valid format is a positive integer.
Completion Count The number of requests that successfully completed during the
interval. The valid format is a positive integer.
Custom Request Count The number of custom requests. The valid format is a
positive integer.
Custom Request Time (ms) The average time (in milliseconds) the custom requests
spent. The valid format is a positive integer.
Custom Request Time (%) The percentage of time the custom requests spent. The
valid format is a decimal (formatted to 1 decimal place).
EJB Count The number of times this request invoked an Enterprise Java Bean (EJB)
request. The valid format is a positive integer.
EJB Time (ms) The average time (in milliseconds) this request spent processing
Enterprise Java Bean (EJB) requests; this field can have a zero value if the total
time is less than the number of requests, due to truncation. The valid format is a
positive integer.
EJB Time (%) The percentage of time this request spent processing Enterprise Java
Bean (EJB) requests. The valid format is a decimal (formatted to 1 decimal place).
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
JCA Count The number of times this request invoked a J2EE Connector
Architecture (JCA) request. The valid format is a positive integer.
384
ITCAM for Application Diagnostics: User Guide
JCA Time (ms) The average time (in milliseconds) this request spent processing
J2EE Connector Architecture (JCA) requests; this field can have a zero value if the
total time is less than the number of requests, due to truncation. The valid format
is a positive integer.
JCA Time (%) The percentage of time this request spent processing J2EE Connector
Architecture (JCA) requests. The valid format is a decimal (formatted to 1 decimal
place).
JMS Count The number of times this request invoked a Java Message Service
(JMS) request. The valid format is a positive integer.
JMS Time (ms) The average time (in milliseconds) this request spent processing
Java Message Service (JMS) requests; this field can have a zero value if the total
time is less than the number of requests, due to truncation. The valid format is a
positive integer.
JMS Time (%) The percentage of time this request spent processing Java Message
Service (JMS) requests. The valid format is a decimal (formatted to 1 decimal
place).
JNDI Count The number of times this request invoked a Java Naming and
Directory Interface (JNDI) request. The valid format is a positive integer.
JNDI Time (ms) The average time (in milliseconds) this request spent processing
Java Naming and Directory Interface (JNDI) requests; this field can have a zero
value if the total time is less than the number of requests, due to truncation. The
valid format is a positive integer.
JNDI Time (%) The percentage of time this request spent processing Java Naming
and Directory Interface (JNDI) requests. The valid format is a decimal (formatted
to 1 decimal place).
Level 2 Request Count The number of times this request was run with Mod Level
2 turned on. The valid format is a positive integer.
Level 2 Total Time (ms) The total time (in milliseconds) this request was run with
Mod Level 2 turned on. The valid format is a positive integer.
Longest Response (ms) The maximum time (in milliseconds) it took this request to
run during the interval. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the application server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Portal Processing Count The number of times the request invoked a WebSphere
Portal page or portlet request. The valid format is a positive integer.
Portal Processing Time (ms) The average time (in milliseconds) the request spent
in processing WebSphere Portal page or portlet requests. This field can have a zero
value if the total time is less than the number of requests. The valid format is a
positive integer.
Chapter 4. ITCAM Agent for WebSphere
385
Portal Processing Time (%) The percentage of time the request spent in processing
WebSphere Portal page or portlet requests. The valid format is a decimal
(formatted to 1 decimal place).
Process ID The process identifier of the Java virtual machine. The valid format is a
positive integer.
Request Bad Response Threshold (msec) The threshold that defines the bad
requests. A request that spends more time to complete than this threshold to
complete is a bad request. The valid format is a positive integer.
Request Completion (%) The percentage of the requests that completed
successfully during the interval. The valid format is a positive integer.
Request Completion Level The completion level of the requests during the
interval. Valid values are Unknown, Good, Fair, and Bad.
Request Count The number of times this request ran during the interval. The valid
format is a positive integer.
Request Detail The URI for servlet requests, or the method name for EJBs. The
valid format is an alphanumeric string, with a maximum of 128 characters.
Request Fair Response Threshold (msec) The threshold that defines the fair
requests. A request that spends more time than this threshold and less time than
the Request Bad Response Threshold (msec) attribute to complete is a fair request. The
valid format is a positive integer.
Request Bad Delay (msec) The delay time (in milliseconds) collected during the
interval. This column is non-zero value when the whole request response time
exceeds the bad threshold configured for it. The valid format is a positive integer.
Request Fair Delay (msec) The delay time (in milliseconds) collected during the
interval. This column is non-zero value when the whole request response time
exceeds the fair threshold configured for it. The valid format is a positive integer.
Request Good Delay (msec) The delay time (in milliseconds) collected during the
interval. This column is non-zero value when the whole request response time is
less than fair threshold configured for it. The valid format is a positive integer.
Request Delay Type The type of the request delay. Valid values are Unknown,
Good, Fair, and Bad.
Request Label A shortened version of Request Name, used to display the request
name in the chart view. The valid format is an alphanumeric string, with a
maximum of 32 characters.
Request Name The URL for servlet requests, or the fully qualified class name for
EJBs. The valid format is an alphanumeric string, with a maximum of 128
characters.
Request Rate (per sec) The number of requests completed per second during the
interval. If the sampling rate is less than 100%, this number is extrapolated to
estimate 100% of completed requests. The valid format is a decimal (formatted to 3
decimal places).
386
ITCAM for Application Diagnostics: User Guide
Request Type The type of request being run. Valid values are Servlet, EJB_Method,
Custom, All_Workloads, Unknown, and Portlet.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 53. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Sampling Rate (%) The percentage of requests being sampled. The valid format is
a positive integer.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Servlet Count The number of times this request invoked a Servlet request. The
valid format is a positive integer.
Servlet Time (ms) The average time (in milliseconds) this request spent processing
Servlet requests; this field can have a zero value if the total time is less than the
number of requests, due to truncation. The valid format is a positive integer.
Servlet Time (%) The percentage of time this request spent processing Servlet
requests. The valid format is a decimal (formatted to 1 decimal place).
SQL Connect Count The number of times this request connected to a JDBC
database. The valid format is a positive integer.
SQL Connect Time (ms) The average time (in milliseconds) this request spent
connecting to a JDBC database; this field can have a zero value if the total time is
less than the number of requests, due to truncation. The valid format is a positive
integer.
SQL Connect Time (%) The percentage of time this request spent connecting to a
JDBC database. The valid format is a decimal (formatted to 1 decimal place).
SQL Execute Count The number of times this request executed a JDBC database.
The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
387
SQL Execute Time (ms) The average time (in milliseconds) this request spent
executing a JDBC database; this field can have a zero value if the total time is less
than the number of requests, due to truncation. The valid format is a positive
integer.
SQL Execute Time (%) The percentage of time this request spent executing a JDBC
database. The valid format is a decimal (formatted to 1 decimal place).
SQL Query Count The number of times this request queried a JDBC database. The
valid format is a positive integer.
SQL Query Time (ms) The average time (in milliseconds) this request spent
querying a JDBC database; this field can have a zero value if the total time is less
than the number of requests, due to truncation. The valid format is a positive
integer.
SQL Query Time (%) The percentage of time this request spent querying a JDBC
database. The valid format is a decimal (formatted to 1 decimal place).
SQL Update Count The number of times this request updated a JDBC database.
The valid format is a positive integer.
SQL Update Time (ms) The average time (in milliseconds) this request spent
updating a JDBC database; this field can have a zero value if the total time is less
than the number of requests, due to truncation. The valid format is a positive
integer.
SQL Update Time (%) The percentage of time this request spent updating a JDBC
database. The valid format is a decimal (formatted to 1 decimal place).
Summary Indicates that this row is a summary row of statistical totals for all rows.
Total Time (ms) The total CPU time (in milliseconds) this request consumed
during the interval. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Requests Monitoring Configuration attributes
The Requests Monitoring Configuration attributes provide information for all
requests monitored in application. Use these attributes to monitor application edge
requests. The agent supports three types of edge requests, Servlet/JSP, EJB, and
Portal.
The attributes within this group are used to build the Request Baseline workspace.
Application Name The name of the application to which the request belongs. The
valid format is an alphanumeric string, with a maximum of 256 characters.
Application ID The unique identifier that is assigned automatically when the
application is first configured and is preserved during the whole application life
cycle. The valid format is a positive integer.
388
ITCAM for Application Diagnostics: User Guide
Application Tier Threshold (msec) The response time threshold in the application
tier in milliseconds. The valid format is a positive integer.
Auto Threshold Bad Projection (%) The bad response time projection used for
auto threshold. The valid format is a positive integer.
Auto Threshold Fair Ratio The percentage to derive the fair response time
threshold from the baseline selection. The valid format is a positive integer.
Auto Threshold Fair Projection (%) The fair response time projection used for
auto threshold. The valid format is a positive integer.
Auto Threshold Mode The request auto threshold mode. Valid values are Default,
Custom, and Disabled.
Auto Threshold Deviation (%) The maximum allowed deviation of requests
baseline data used for auto threshold. The valid format is a positive integer.
Auto Threshold Percent (%) The minimum percent of requests baseline data used
for auto threshold. The valid format is a positive integer.
Backend Tier Threshold (msec) The response time threshold in the backend tier in
milliseconds. The valid format is a positive integer.
Bad Response Threshold (msec) The time (in milliseconds) that defines the bad
requests. A request that spends more time than this threshold to complete is a bad
request. Use this attribute with Fair Response Threshold (msec) attribute and Fair
Response Zone (msec) attribute. The valid format is a positive integer.
Bad Errors Rate Threshold The value of bad error rate percentage. The valid
format is a positive integer.
Baselined Request Count The total number of requests accumulated in the
baseline. This counter shows the data since the baseline starts. The valid format is
a positive integer.
Client Tier Threshold (msec) The response time threshold in the client tier in
milliseconds. The valid format is a positive integer.
Fair Response Threshold (msec) The time (in milliseconds) that defines the fair
requests. A request that spends less time than this threshold to complete is a good
request. Use this attribute with Fair Response Zone (msec) attribute and Bad
Response Threshold (msec) attribute. The valid format is a positive integer.
Fair Response Zone (msec) The time span (in milliseconds) that defines the fair
requests. This time span is between the fair response time threshold and the bad
time threshold. If the response time of a request falls into this time span, the
request is a fair request. Use this attribute with Fair Response Threshold (msec)
attribute and Bad Response Threshold (msec) attribute. The valid format is a
positive integer.
Fair Errors Rate Threshold The value of fair error rate percentage. The valid
format is a positive integer.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Chapter 4. ITCAM Agent for WebSphere
389
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Request Detail The request detail name. The valid format is an alphanumeric
string, with a maximum of 256 characters.
Request ID The unique identifier of the request that belongs to the application.
The valid format is a positive integer.
Request Label A shortened version of Request Name, used to display the request
name in the chart view. The valid format is an alphanumeric string, with a
maximum of 24 characters.
Request Name The URL for servlet requests, or the fully qualified class name for
EJBs. The valid format is an alphanumeric string, with a maximum of 256
characters.
Request Type The type of request being run. Valid values are All, Servlet/JSP, EJB,
and Portal.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 54. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
390
ITCAM for Application Diagnostics: User Guide
Request Times and Rates attributes
The Request Times and Rates attribute group provides information about
historical request throughput and average response time for a particular
application server.
The attributes within this group are used to build the WebSphere App Server
workspace.
Application Name The name of the application to which the request belongs. The
valid formats are as follows:
v An alphanumeric string, with a maximum of 256 characters.
v An empty string means that this sample is aggregated data for all applications
v It does not support application level monitoring at all and only shows server
level statistics when the agent is TEMA 6.1.
ASID The identifier (decimal) assigned to the address space running this servant
region.
Average Load The average number of concurrent requests during the interval. The
valid format is a decimal (formatted to 3 decimal places).
Average Request Completion Rate The average request completion rate (that is,
the request throughput). If the sampling rate is less than 100%, this number is
extrapolated to estimate 100% of completed requests. The valid format is a positive
integer.
Average Request Response Time The average request response time, in
milliseconds. The valid format is a positive integer.
Error Rate (%) The error rate of the request during the interval. The valid format is
a decimal (formatted to 3 decimal places).
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID Indicates the process ID of the JVM.
Request Count The number of requests processed during the current interval. The
valid format is a positive integer.
Request Data Monitoring Level Indicates request data monitoring level for
application.
Request Type The type of request being run. Valid values are Servlet, EJB_Method,
Custom, All_Workloads, Unknown, and Portlet.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
Chapter 4. ITCAM Agent for WebSphere
391
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 55. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Sampling Rate (%) The percentage of edge requests-such as servlets and JSPs-that
were sampled during the interval. The valid format is a positive integer.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Total (ms) The total time used (in milliseconds) during the interval. The valid
format is a decimal (formatted to 3 decimal places).
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Selected Request attributes
The Selected Request attribute group provides detailed information about
transactions' requests for database (that is, JDBC), messaging (that is, JMS), or EIS
(that is, J2C) services.
The attributes within this group are used to build these workspaces:
v Selected Request - Datasources
v Selected Request - JMS Queues
v Selected Request - Resource Adapters
v Selected Request - Portal Processing
Note: The attributes within this attribute group contain meaningful values only if
your site has set the request data monitoring level to Level2 to collect data on
nested requests.
Activity Category The type of request. Valid values are n/a (not applicable), JDBC,
JMS, JCA, and Unknown.
392
ITCAM for Application Diagnostics: User Guide
Activity Detail Detailed information about the activity performed by the selected
request, for example, the SQL statement being processed. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Activity Label An abbreviated version of Activity Name, used to display the
activity name in the chart view. The valid format is an alphanumeric string, with a
maximum of 32 characters.
Activity Name The resource that the request is accessing, for example, the data
source name. The valid format is an alphanumeric string, with a maximum of 128
characters.
Activity Type The type of the resource being requested. Valid values are:
Table 56. Activity types
Type
Definition
n/a
not applicable
Servlet
A call to a servlet's doGet or doPost methods
EJB_Method_Call
A call to a business method for an EJB class
Obtain_SQL_Connection_from_Datasource
A call to obtain a connection from a JDBC data source
SQL_Query
A Query request to a JDBC data source
SQL_Update
An Update request to a JDBC data source
SQL_Other
Any other request to a JDBC data source
JMS_Message_Browse
A call to browse a message from a JMS queue
JMS_Message_Get
A call to receive a message from a JMS queue (that is, a
destructive get)
JMS_Message_Put
A call to put a message from a JMS queue
JMS_Publish_Message
A call to publish a publication to a JMS queue
JCA_CCI_Execute_interaction
A request by a J2EE application to execute a JCA
interaction (a JDBC, JMS, or other JCA-supported
operation) against a backend system
JNDI_Lookup
A call to JNDI to build an InitialContext or to perform a
lookup
Unknown
The activity type cannot be determined
Portlet_Processing
A call for portlet processing request
Portlet_Authorization
A call for portlet authorization request
Portal_Authentication
A call for portal authentication request
Portal_Model_Building
A call for portal page model building request
Portal_Page_Loading
A call for portal page loading request
Portal_Page_Rendering
A call for portal page rendering request
Portal_Legacy_Action
A call for portal legacy action request
Portal_Standard_Action
A call for portal standard action (JSR-88) request
ASID The identifier (decimal) assigned to the address space running this servant
region.
Average Response (ms) The average time (in milliseconds) executing this request,
per occurrence. The valid format is a decimal (formatted to 1 decimal place).
Chapter 4. ITCAM Agent for WebSphere
393
Delay (%) The percentage of execution time this activity consumed on average
when processing this request. The valid format is a decimal (formatted to 1
decimal place).
Interval (sec) The length (in seconds) of the interval. The valid format is a positive
integer.
Longest Response (ms) The worst-case response time (in milliseconds) experienced
by this request. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Occurrences The number of times this request was executing during the interval.
The valid format is a positive integer.
Origin Node The name of the application server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Process ID The unique identifier of the JVM process (the class ID of the JVM). The
valid format is a positive integer.
Request Detail The URI for servlet requests, or the method name for EJBs. The
valid format is an alphanumeric string, with a maximum of 128 characters.
Request Name The URL for servlet requests, or the fully qualified class name for
EJBs. The valid format is an alphanumeric string, with a maximum of 128
characters.
Request Type The type of transaction being run. Valid values are Servlet,
EJB_Method, Custom, All_Workloads, Unknown, and Portlet.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 57. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
394
ITCAM for Application Diagnostics: User Guide
Sampling Rate (%) The percentage of edge requests-such as servlets and JSPs-that
were sampled for nested requests during the interval. The valid format is a
positive integer.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Summary Indicates that this row is a summary row of statistical totals for all rows.
Total Time (ms) The total CPU time (in milliseconds) consumed by this request.
The valid format is a positive integer.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Servlet Sessions attributes
The Servlet Sessions attribute group provides information about servlet sessions.
A session is a series of requests to a servlet, originating from the same user at the
same browser. Applications running in a Web container use Sessions to monitor the
actions of individual users. The attributes within this group are used to build the
Sessions workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Average Concurrently Active Sessions The average number of concurrently active
sessions during the sampling interval. A session is active if WebSphere Application
Server is currently processing a request that uses the session. The valid format is a
decimal (formatted to 3 decimal places). This value is an average of several values
collected over an interval. The interval can be either between this time and the
previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Average Concurrently Live Sessions The average number of sessions cached in
memory during the sampling interval. The valid format is a decimal (formatted to
3 decimal places). This value is an average of several values collected over an
Chapter 4. ITCAM Agent for WebSphere
395
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Average Serializable Session Object Size (bytes) The average size (in bytes) of the
serializable attributes of in-memory sessions. This number is at a session level only
and includes only session objects that contain at least one serializable attribute
object (a session may contain some attributes that are serializable and some that
are not). This value is a measurement of the data at the end of the PMI sampling
interval, not of the data in the entire sampling interval. The valid format is a
positive integer.
Average Session Lifetime (ms) The average session lifetime (in milliseconds),
calculated by subtracting the time the session was created from the time it was
invalidated. The valid format is a decimal (formatted to 3 decimal places).
Broken Session Affinities The number of HTTP session affinities that broke, not
counting WebSphere Application Server intentional breaks of session affinity. This
is the number of requests received for sessions that were last accessed from
another Web application and can indicate failover processing or a corrupted
plug-in configuration. The valid format is a positive integer.
Broken Session Affinity Rate (per sec) The rate (per second) of the number of
HTTP session affinities that break, not counting the WebSphere Application Server
intentional breaks of session affinity, during the sampling interval. The valid
format is a decimal (formatted to 3 decimal places).
Cache Discard Rate (per sec) The rate (per second) at which session objects have
been forced out of the cache during the sampling interval. The valid format is a
decimal (formatted to 3 decimal places).
Cache Discards The number of session objects that have been forced out of the
cache. An LRU algorithm removes old entries to make room for new sessions and
cache misses (this applies only to persistent sessions). The valid format is a
positive integer.
Enterprise Application Name The name of the Enterprise application running the
servlet. The valid format is an alphanumeric string, with a maximum of 256
characters.
External Read Size (bytes) The size (in bytes) of the session data read from the
persistent store (applicable only to serialized, persistent sessions). The valid format
is a decimal (formatted to 3 decimal places).
External Read Time (ms) The time (in milliseconds) taken to read the session data
from the persistent store (applicable only to persistent sessions). For multirow
sessions, the metrics are for the attributes; for single-row sessions, the metrics are
for the whole session. When using a JMS persistent store, the user has the choice of
whether to serialize the data being replicated; if the data are not serialized, this
counter is not available. The valid format is a decimal (formatted to 3 decimal
places).
External Write Size (bytes) The size (in bytes) of session data written to the
persistent store (applicable only to serialized, persistent sessions). The valid format
is a decimal (formatted to 3 decimal places).
396
ITCAM for Application Diagnostics: User Guide
External Write Time (ms) The time (in milliseconds) taken to write the session data
from the persistent store (applicable only to serialized, persistent sessions). The
valid format is a decimal (formatted to 3 decimal places).
Failed Session Request Rate (per sec) The rate (per second) that a request for a
new session could not be handled because it would exceed the maximum session
count for the sampling interval. The valid format is a decimal (formatted to 3
decimal places).
Failed Session Requests This attribute collects data from the
NoRoomForNewSessionCount metric in the Servlet Sessions Counters PMI module.
The number of times a request for a new session could not be handled because it
would exceed the maximum session count; this applies only to a session in
memory with AllowOverflow=false. The valid format is a positive integer.
Instrumentation Level The Web instrumentation level for this Web application. For
WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Max Serializable Session Object Size (bytes) The maximum size (in bytes) of the
serializable attributes of in-memory sessions. This number is at a session level only
and includes only session objects that contain at least one serializable attribute
object (a session may contain some attributes that are serializable and some that
are not). This value is a measurement of the data at the end of the PMI sampling
interval, not of the data in the entire sampling interval. The valid format is a
positive integer.
Min Serializable Session Object Size (bytes) The minimum size (in bytes) of the
serializable attributes of in-memory sessions. This number is at a session level and
includes only session objects that contain at least one serializable attribute object (a
session may contain some attributes that are serializable and some that are not).
This value is a measurement of the data at the end of the PMI sampling interval,
not of the data in the entire sampling interval. The valid format is a positive
integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Nonexistent Session Request Rate (per sec) The rate (per second) of requests for a
session that no longer exists (presumably because the session timed out) during the
sampling interval. The valid format is a decimal (formatted to 3 decimal places).
Nonexistent Session Requests The number of requests for a session that no longer
exists (presumably because the session timed out). Use this counter to determine if
the timeout is too short. The valid format is a positive integer.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
Chapter 4. ITCAM Agent for WebSphere
397
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 58. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Session Creation Rate (per sec) The rate (per second) of sessions created during
the sampling interval. The valid format is a decimal (formatted to 3 decimal
places).
Session Invalidation Rate (per sec) The rate (per second) at which sessions were
invalidated during the sampling interval. The valid format is a decimal (formatted
to 3 decimal places).
Sessions Created The number of sessions created during the sampling interval.
The valid format is a positive integer.
Sessions Invalidated The number of sessions invalidated during the sampling
interval. The valid format is a positive integer.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of Servlet Sessions Whether this row is a summary row of statistical
totals collected for the servlet sessions. The valid values are No and Yes.
Time since Last Activated The time difference (in hh:mm:ss:msecs format) between
the previous and current access timestamps. Does not include session timeouts.
The valid format is a timestamp.
Total Serializable Session Object Size (bytes) The total size (in bytes) of all the
in-memory session objects. This includes only the serializable attributes in the
session object; at least one such attribute must be present to be included in this
total. This value is a measurement of the data at the end of the PMI sampling
interval, not of the data in the entire sampling interval. The valid format is a
positive integer.
398
ITCAM for Application Diagnostics: User Guide
Web Application Archive The name of the Web application WAR file. The valid
format is an alphanumeric string, with a maximum of 128 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Servlets JSPs attributes
The Servlets JSPs attributes provide performance information for servlets and Java
server pages (JSPs).
Examples of Servlets JSPs attributes include the average number of concurrent
requests for a servlet and the amount of time it takes for a servlet to perform a
request. Use the Servlets JSPs attributes in situations to monitor performance and
the usage of servlets and JSPs.
The attributes within this group are used to build the Servlets/JSPs - Selected Web
Application workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Average Concurrent Requests The average number of concurrent requests for the
servlet or JSP during the interval. The valid format is a decimal (formatted to 3
decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Average Response Time (ms) The time (in milliseconds) it took the servlet to
perform a task during the interval. The valid format is a decimal (formatted to 3
decimal places).
Enterprise Application Name The name of the Enterprise application. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Error Count The number of errors or exceptions that have occurred in the servlet
during the interval. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
399
Error Rate (per sec) The servlet exceptions or errors (per second) since the
previous sample. The valid format is a decimal (formatted to 3 decimal places).
Instrumentation Level The instrumentation level for this servlet. For WebSphere 6
or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no
instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Request Count The number of total requests for the servlet during the interval.
The valid format is a positive integer.
Request Rate (per sec) The servlet requests (per second) since the previous sample.
The valid format is a decimal (formatted to 3 decimal places).
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 59. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Servlet/JSP Name The name of the current servlet or JSP. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Total (ms) The total time (in milliseconds) used during the interval. The valid
format is a decimal (formatted to 3 decimal places).
400
ITCAM for Application Diagnostics: User Guide
Type Whether this entry represents a servlet or Java server page (JSP). The valid
values are Servlet and JSP.
Web Application Archive The name of the Web application WAR file. The valid
format is an alphanumeric string, with a maximum of 128 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Scheduler attributes
The Scheduler attributes display data for the Scheduler service.
The attributes within this group are used to build the Scheduler workspace.
Instrumentation Level The instrumentation level for the Scheduler. For WebSphere
6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no
instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Poll Count The number of polls which are collected on the intervals. The valid
format is a positive integer.
Poll Duration The average alarms during the latency. The valid format is a
decimal (formatted to 3 decimal places). This value is an average of several values
collected over an interval. The interval can be either between this time and the
previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Poll Query Duration The duration of poll query. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Row Number The row number. The valid format is a positive integer.
Run Duration The run duration. The valid format is a decimal (formatted to 3
decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Chapter 4. ITCAM Agent for WebSphere
401
Table 60. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Scheduler Name The name of the scheduler. The valid format is an alphanumeric
string, with a maximum of 256 characters.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Task Collision Rate The rate of the task collision. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Task Delay Duration The duration of the task delay. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Task Expiration Rate The rate of the task expiration. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Task Failure Count The number of the failed tasks. The valid format is a positive
integer.
Task Finish Count The number of the finished tasks which are collected on the
intervals. The valid format is a positive integer.
Task Finish Rate The rate of the finished tasks. The valid format is a decimal
(formatted to 3 decimal places). This value is an average of several values collected
over an interval. The interval can be either between this time and the previous
402
ITCAM for Application Diagnostics: User Guide
time you activated this workspace, or fixed (normally 60 seconds), depending on
the configuration of the Monitoring Agent.
Task Run Rate The rate of the run tasks. The valid format is a decimal (formatted
to 3 decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Service Component Elements attributes
The Service Component Elements attributes provide aggregated information about
the performance data for all the service components and their elements.
The attributes within this group are used to build the Service Component Elements
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Average Response Time (ms) The average response time (in milliseconds) in the
current interval. The valid format is a decimal (formatted to 3 decimal places).
Component The type of the component. The value format is an alphanumeric
string, with a maximum of 256 characters.
Component Name The component name of the service. The value format is an
alphanumeric string, with a maximum of 256 characters.
Element The type of the element. The valid format is a positive integer.
Element Name The name of the element. The value format is an alphanumeric
string, with a maximum of 256 characters.
Chapter 4. ITCAM Agent for WebSphere
403
Error Rate (per sec) The computed error rate. The valid format is a decimal
(formatted to 3 decimal places).
Failed Count The failed invocations. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the service component
elements. For WebSphere 6 or higher, the valid values are None, Basic, Extended,
All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Request Count The number of requests during the interval. The valid format is a
positive integer.
Request Rate (per sec) The rate of requests during the interval per second. The
valid format is a decimal (formatted to 3 decimal places).
Row Number The row number. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 61. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Success Count The successful invocations. The valid format is a positive integer.
404
ITCAM for Application Diagnostics: User Guide
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Total (ms) The total time used (in milliseconds) during the interval. The valid
format is a decimal (formatted to 3 decimal places).
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Service Components attributes
The Service Components attributes provide aggregated information about the
overview performance of the key service components.
The attributes within this group are used to build the Service Components
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Count The bad request count. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the service components. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Name The component name of the service. Valid values are
Service_Component_Architecture, Business Rules, Map, Mediation, Business State
Machine, and Selector.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Chapter 4. ITCAM Agent for WebSphere
405
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 62. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Thread Pools attributes
The Thread Pools attribute group provides information about the data source, as
well as connection statistics, for database connection pools in a WebSphere
Application Server. Use it to monitor pools activity and to spot potential throttling.
The attributes within this group are used to build the Pool Analysis and Thread
Pools workspaces.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
406
ITCAM for Application Diagnostics: User Guide
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Application ID Indicates J2EE application ID.
Average Active Threads The average number of concurrently active threads during
the sampling interval. The valid format is a decimal (formatted to 3 decimal
places). This value is an average of several values collected over an interval. The
interval can be either between this time and the previous time you activated this
workspace, or fixed (normally 60 seconds), depending on the configuration of the
Monitoring Agent.
Average Free Threads The average number of free threads in the pool. The valid
format is a decimal (formatted to 3 decimal places). This value is an average of
several values collected over an interval. The interval can be either between this
time and the previous time you activated this workspace, or fixed (normally 60
seconds), depending on the configuration of the Monitoring Agent.
Average Pool Size The average number of threads in the pool. The valid format is
a decimal (formatted to 3 decimal places). This value is an average of several
values collected over an interval. The interval can be either between this time and
the previous time you activated this workspace, or fixed (normally 60 seconds),
depending on the configuration of the Monitoring Agent.
Note: This value may exceed Maximum Pool Size in certain configurations where
the pool is enabled to grow beyond the specified maximum size.
Instrumentation Level The instrumentation level for the thread pools. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Maximum Pool Size The configured maximum number of threads allowed in the
pool. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Percent of Time Pool at Max The average percentage of time that all threads were
in use during the sampling interval. The valid format is a decimal (formatted to 3
decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Percent Used Bad The bad percent of pool usage by application. The valid format
is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
407
Percent Used Fair The fair percent of pool usage by application. The valid format
is a positive integer.
Percent Used Good The good percent of pool usage by application. The valid
format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 63. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Summary of Thread Pools Whether this row is a summary row of statistical totals
collected for all thread pools. The valid values are No and Yes.
Thread Creation Rate (per sec) The rate (per second) at which threads were
created during the sampling interval. The valid format is a decimal (formatted to 3
decimal places).
Thread Destruction Rate (per sec) The rate (per second) at which threads were
destroyed during the sampling interval. The valid format is a decimal (formatted
to 3 decimal places).
Thread Pool Name The name of the thread pool. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Threads Created The number of threads created during the sampling interval. The
valid format is a positive integer.
Threads Destroyed The number of threads destroyed during the sampling interval.
The valid format is a positive integer.
408
ITCAM for Application Diagnostics: User Guide
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Topic Spaces attributes
The Topic Spaces attributes provide aggregated information about
publish/subscribe messaging.
The attributes within this group are used to build the Destinations workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Assured Persistent Local Subscription Hits The cumulative total of subscriptions
which have matched assured persistent publications. The valid format is a positive
integer.
Assured Persistent Messages Published The number of Assured Persistent
messages published. The valid format is a positive integer.
Best Effort Non-persistent Local Subscription Hits The cumulative total of
subscriptions which have matched best effort non-persistent publications. The valid
format is a positive integer.
Best Effort Non-persistent Messages Published The number of best effort
non-persistent messages published. The valid format is a positive integer.
Durable Local Subscription The number of durable subscriptions. The valid
format is a positive integer.
Express Non-persistent Local Subscription Hits The cumulative total of
subscriptions which have matched express non-persistent publications. The valid
format is a positive integer.
Express Non-persistent Messages Published The number of express non-persistent
messages published. The valid format is a positive integer.
Chapter 4. ITCAM Agent for WebSphere
409
Incomplete Publication The number of publications not yet received by all current
subscribers. If this number is unexpected, view the publication using the admin
console to take any actions. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the topic spaces. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Local Oldest Publication The longest time any publication has spent on this topic
space. If this time is not what was expected, view the message using the admin
console to decide what action needs to be taken. The valid format is a positive
integer.
Local Publisher The number of local publishers to topics in this topic space. The
valid format is a positive integer.
Local Publisher Attaches The number of times an attachment has been made to
this topic space by local producers. The lifetime of this value is the lifetime of the
messaging engine. The valid format is a positive integer.
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Non-Durable Local Subscription The number of non-durable subscriptions. The
valid format is a positive integer.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Reliable Non-persistent Local Subscription Hits The cumulative total of
subscriptions which have matched reliable non-persistent publications. The valid
format is a positive integer.
Reliable Non-persistent Messages Published The number of reliable
non-persistent messages published. The valid format is a positive integer.
Reliable Persistent Local Subscription Hits The cumulative total of subscriptions
which have matched reliable persistent publications. The valid format is a positive
integer.
Reliable Persistent Messages Published The number of reliable persistent
messages published. The valid format is a positive integer.
Report Enabled Publication Expired The number of report enabled incomplete
publications that expired while on this topic space. The valid format is a positive
integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
410
ITCAM for Application Diagnostics: User Guide
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 64. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Topic Space Name The name of the topic space. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Total Local Subscription The number of local subscriptions to topics in this topic
space. Each subscription is ed once, even if the topic includes wildcards. The valid
format is a positive integer.
Total Local Subscription Hits The cumulative total of subscriptions which have
matched topic space publications. The valid format is a positive integer.
Total Messages Published The total number of publications to this topic space.
The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
Web Applications attributes
Use the Web Applications attributes to create situations that monitor Web
application performance and application server loads.
The Web Applications attributes provide aggregated information for each Web
application and for the application server running that application. These
performance data describe all servlets and JSPs deployed to that Web application
as well as performance data for all servlets and JSPs running in the application
Chapter 4. ITCAM Agent for WebSphere
411
server. Examples include the number of loaded servlets and JSPs and total
requests. The attributes within this group are used to build the Web Applications
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Average Concurrent Requests The average number of concurrent requests for
servlets and JSPs during the interval. The valid format is a decimal (formatted to 3
decimal places). This value is an average of several values collected over an
interval. The interval can be either between this time and the previous time you
activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.
Average Response Time (ms) The average time (in milliseconds) required for a
servlet to perform a task during the interval. Calculated by dividing the total
responses by Request Count; if Request Count is zero, this value is set to blank.
The valid format is a decimal (formatted to 3 decimal places).
Enterprise Application Name The name of the Enterprise application. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Error Count The number of errors or exceptions that have occurred in the servlet.
The valid format is a positive integer.
Error Rate (per sec) The servlet exceptions or errors (per second) for the interval
since the previous sample. The valid format is a decimal (formatted to 3 decimal
places).
Instrumentation Level The Web instrumentation level for this Web application. For
WebSphere 5, the valid values are None, Low, Medium, High and Maximum; for
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 256 characters.
412
ITCAM for Application Diagnostics: User Guide
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Request Count The number of total requests for the servlet during the interval.
The valid format is a positive integer.
Request Rate (per sec) The servlet requests (per second) for the interval since the
previous sample. The valid format is a decimal (formatted to 3 decimal places).
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 65. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Servlets Loaded The number of servlets loaded during the interval. The valid
format is a positive integer.
Servlets Reloaded The number of servlets reloaded during the interval. The valid
format a positive integer.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
Subinstrumentation Level The subinstrumentation level for the Web application's
servlet submodule. For WebSphere Application Server 5 the valid values are None,
Low, Medium, High, and Maximum.
Note: Subinstrumentation Level is not supported in WebSphere Application Server
6.0 or higher. The Tivoli Enterprise Monitoring agent uses the Instrumentation
Level instead.
Chapter 4. ITCAM Agent for WebSphere
413
Summary of All Applications Whether this row is a summary row of statistical
totals for all Web applications executed during the interval. The valid values are
Yes and No.
Total (ms) The total time used during the interval. The valid format is a decimal
(formatted to 3 decimal places).
Web Application Archive The name of the Web application WAR file. The valid
format is an alphanumeric string, with a maximum of 128 characters.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Web Services attributes
The Web Services attributes display aggregated information about the Web
services, including the number of loaded Web services, the number of requests
delivered and processed, the request response time, and the average size of
requests.
The attributes within this group are used to build the Web Services workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Dispatched Requests The number of requests the service dispatched or delivered.
The valid format is a positive integer.
Dispatch Response Time The average response time, in milliseconds, to dispatch a
request. The valid format is a decimal (formatted to 3 decimal places).
Instrumentation Level The instrumentation level for the web services counters. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
414
ITCAM for Application Diagnostics: User Guide
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Payload Size The average payload size in bytes of a received request or reply. The
valid format is a positive integer.
Processed Requests The number of requests the service successfully processed.
Valid format is a positive integer.
Received Requests The number of requests the service received. The valid format
is a positive integer.
Reply Payload Size The average payload size (in bytes) of a reply. The valid
format is a positive integer.
Reply Response Time The average response time, in milliseconds, to prepare a
reply after dispatch. The valid format is a decimal (formatted to 3 decimal places).
Request Payload Size The average payload size, in bytes, of a request. The valid
format is a positive integer.
Request Response Time The average response time, in milliseconds, to prepare a
request for dispatch. The valid format is a decimal (formatted to 3 decimal places).
Response Time The average response time (in milliseconds) for a successful
request. The valid format is a decimal (formatted to 3 decimal places).
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 66. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Chapter 4. ITCAM Agent for WebSphere
415
Total Dispatch (ms) The total time (in milliseconds) the service dispatches
requests. The valid format is a decimal (formatted to 3 decimal places).
Total Prepare (ms) The total time (in milliseconds) the service prepares requests.
The valid format is a decimal (formatted to 3 decimal places).
Total Processing (ms) The total time (in milliseconds) the service processes
requests. The valid format is a decimal (formatted to 3 decimal places).
Web Service The name of the Web service. The valid format is an alphanumeric
string, with a maximum of 256 characters.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Web Services Gate Way attributes
The Web Services Gate Way attributes display aggregated information about the
Web Services Gateway, including synchronous requests, asynchronous requests,
synchronous responses, and asynchronous responses.
The attributes within this group are used to build the Web Services workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Asynchronous Requests The number of asynchronous requests made. The valid
format is a positive integer.
Asynchronous Responses The number of asynchronous responses made. The valid
format is a positive integer.
Instrumentation Level The instrumentation level for the Web Services Gateway
counters. For WebSphere 6 or higher, the valid values are None, Basic, Extended,
All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
416
ITCAM for Application Diagnostics: User Guide
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 67. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Summary Whether this row is a summary row of statistical totals for all rows.
Valid values are No and Yes.
Synchronous Requests The number of synchronous requests made. The valid
format is a positive integer.
Synchronous Responses The number of synchronous responses made. The valid
format is a positive integer.
Web Service The name of the Web service. The valid format is an alphanumeric
string, with a maximum of 256 characters.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
WebSphere Agent Events attributes
The WebSphere Agent Events attributes provide information about agent-level
events that affect the ability of the Tivoli Enterprise Monitoring Agent to collect
data about WebSphere Application Server. These attributes provide exception and
error messages, their IDs, and their severities.
Chapter 4. ITCAM Agent for WebSphere
417
The attributes within this group are used to build the WebSphere Agent
workspace.
Event Date and Time The date and time the event occurred. The valid format is a
12-character timestamp. For the STR and SCAN functions, the format is
MM/DD/YY HH:MM:SS; the following table shows the values contained in this
character string:
Table 68. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Message Description The message description. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Message ID The message ID. The valid format is an alphanumeric string, with a
maximum of 8 characters.
Node Name The system on which the server is running. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sequence Number The sequence number of the message. The valid format is a
positive integer.
Severity The severity of the event. Valid values are Info, Warning, Error, and
Severe.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
WMQ Client Link Communications attributes
The WMQ Client Link Communications attributes display aggregated information
for all the clients of WMQ Queue Managers that are or have been connected to this
application server.
418
ITCAM for Application Diagnostics: User Guide
The attributes within this group are used to build the WMQ Client Link
Communications workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then reselect it later. Each time you reselect
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
API Calls Serviced The number of MQ API call requests serviced on behalf of
WMQ JMS clients. The valid format is a positive integer.
Batches Sent The number of batches of messages sent to network attached WMQ
JMS clients. The valid format is a positive integer.
Clients Attached The current number of WMQ JMS clients attached to this
application server. The valid format is a positive integer.
Comms Errors The number of errors that have caused connections to WMQ JMS
clients to be dropped. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the WMQ client link
communications. For WebSphere 6 or higher, the valid values are None, Basic,
Extended, All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Messages Received The number of messages received from network attached
WMQ JMS clients. The valid format is a positive integer.
Messages Sent The number of messages sent to network attached WMQ JMS
clients. The valid format is a positive integer.
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Chapter 4. ITCAM Agent for WebSphere
419
Reads Blocked The number of read operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with WMQ JMS clients. The valid format is a positive integer.
Received (bytes) The number of bytes of data received from network attached
WMQ JMS clients. This includes bytes of message data as well as bytes of data
used to control the flow of messages. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 69. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Sent (bytes) The number of bytes of data sent to network attached WMQ JMS
clients. This includes bytes of message data as well as bytes of data used to control
the flow of messages. The valid format is a positive integer.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Writes Blocked The number of write operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with WMQ JMS clients. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
WMQ Link Communications attributes
The WMQ Link Communications attributes display aggregated information for all
the WMQ Queue Managers that are or have been connected to this application
server.
The attributes within this group are used to build the WMQ Link Communications
workspace.
420
ITCAM for Application Diagnostics: User Guide
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
v Attributes in this group are only provided for IBM WebSphere Application
Server version 6.0 or later.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Batches Received The number of batches of messages received from network
attached WMQ Queue Managers. The valid format is a positive integer.
Batches Sent The number of batches of messages sent to network attached WMQ
Queue Managers. The valid format is a positive integer.
Comms Errors The number of communication errors that resulted in a network
connection to a WMQ Queue Manager being disconnected. The valid format is a
positive integer.
Instrumentation Level The instrumentation level for the WMQ link
communications. For WebSphere 6 or higher, the valid values are None, Basic,
Extended, All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Long Retries The number of long retries. This indicates the number of times
channels were disconnected and could not be re-established for longer periods of
time. The valid format is a positive integer.
Messages Received The number of messages received from network attached
WMQ Queue Managers. The valid format is a positive integer.
Messages Sent The number of messages sent to network attached WMQ Queue
Managers. The valid format is a positive integer.
Messaging Engine Name The name of the message engine. The value format is an
alphanumeric string, with a maximum of 256 characters.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Chapter 4. ITCAM Agent for WebSphere
421
QM Attached The total number of WMQ Queue Managers currently network
attached to this application server. The valid format is a positive integer.
Reads Blocked The number of read operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with WMQ Queue Managers. The valid format is a positive
integer.
Receiver Received (bytes) The number of bytes of data received by receiver
channels from network attached WMQ Queue Managers. The valid format is a
positive integer.
Receiver Sent (bytes) The number of bytes data sent by receiver channels to
network attached WMQ Queue Managers. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 70. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Sender Received (bytes) The number of bytes of data received by sender channels
from network attached WMQ Queue Managers. The valid format is a positive
integer.
Sender Sent (bytes) The number of bytes of data sent by sender channels to
network attached WMQ Queue Managers. The valid format is a positive integer.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Short Retries The number of short retries. This indicates the number of times
channels were disconnected and could not be re-established for short periods of
time. The valid format is a positive integer.
422
ITCAM for Application Diagnostics: User Guide
Writes Blocked The number of write operations that could not be completed
immediately. This number can be used as an indicator of network congestion when
communicating with WMQ Queue Managers. The valid format is a positive
integer.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Workload Management Client attributes
The Workload Management Client attribute group provides information about the
client that initiates workload requests.
Workload management (WLM) optimizes the distribution of client processing tasks.
Incoming work requests are distributed to the application servers, enterprise beans,
servlets, and other objects that can most effectively process their requests.
Workload management also provides failover when servers are not available,
improving application availability. In a WebSphere Application Server
environment, you implement workload management by using clusters, transports,
and replication domains.
The attributes within this group are used to build the Workload Management
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it later. Each time you select the
workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Client Cluster Update Rate (per sec) The rate (per second) at which times this
client has received new server cluster information during the sampling interval.
Use this metric to determine how often cluster information is being propagated.
The valid format is a decimal (formatted to 3 decimal places).
Client Cluster Updates The number of times initial or updated server cluster data
is sent to a WLM-enabled client from a server cluster member. Use this metric to
determine how often cluster information is being propagated. The valid format is a
positive integer.
Chapter 4. ITCAM Agent for WebSphere
423
Client Response Time (ms) The response time (in milliseconds) for IIOP requests
sent by a client. This response time is calculated based on the time the client sends
the request to the time the server sends the reply. The valid format is a decimal
(formatted to 3 decimal places).
Instrumentation Level The instrumentation level for the WLM client. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Outgoing Request Rate (per sec) The rate (per second) at which outgoing IIOP
requests were being sent from this client to an application server during the
sampling interval. The valid format is a decimal (formatted to 3 decimal places).
Outgoing Requests The number of outgoing IIOP requests being sent from this
client to an application server. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 71. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
424
ITCAM for Application Diagnostics: User Guide
Total Client Response (ms) The total response time (in milliseconds) for IIOP
requests sent by a client. The valid format is a decimal (formatted to 3 decimal
places).
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Workload Management Server attributes
The Workload Management Server attribute group provides information about the
workload management server.
Workload management (WLM) optimizes the distribution of client processing tasks.
Incoming work requests are distributed to the application servers, enterprise beans,
servlets, and other objects that can most effectively process those requests.
Workload management also provides failover when servers are not available,
improving application availability. In a WebSphere Application Server
environment, you implement workload management by using clusters, transports,
and replication domains.
The attributes within this group are used to build the Workload Management
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Concurrent Requests The number of remote IIOP requests being processed by this
server. The valid format is a decimal (formatted to 3 decimal places). This value is
an average of several values collected over an interval. The interval can be either
between this time and the previous time you activated this workspace, or fixed
(normally 60 seconds), depending on the configuration of the Monitoring Agent.
Incoming Non-WLM Object Request Rate (per sec) The rate (per second) of
incoming IIOP requests from an application running on a non-WLM client during
the sampling interval. This type of client either does not have the WLM runtime
present, or the client's object reference was flagged not to participate in workload
management. The valid format is a decimal (formatted to 3 decimal places).
Chapter 4. ITCAM Agent for WebSphere
425
Incoming Non-WLM Object Requests The number of incoming IIOP requests to
an application from a client that does not have the WLM runtime present or whose
object reference was flagged not to participate in workload management. The valid
format is a positive integer.
Incoming Nonaffinity Request Rate (per sec) The rate (per second) of incoming
IIOP requests to an application server based on no affinity during the sampling
interval. The valid format is a decimal (formatted to 3 decimal places).
Incoming Nonaffinity Requests The number of incoming IIOP requests to an
application server based on no affinity. This request was sent to this server based
on workload management selection policies that were decided in the client's WLM
runtime. The valid format is a positive integer.
Incoming Request Rate (per sec) The rate (per second) of incoming IIOP requests
to an application server during the sampling interval. The valid format is a
decimal (formatted to 3 decimal places).
Incoming Requests The number of incoming IIOP requests to an application
server during the sampling interval. The valid format is a positive integer.
Incoming Strong Affinity Request Rate (per sec) The rate (per second) of
incoming IIOP requests to an application server that are based on a strong affinity
during the sampling interval. The valid format is a decimal (formatted to 3 decimal
places).
Incoming Strong Affinity Requests The number of incoming IIOP requests to an
application server that are based on a strong affinity. A strong affinity request is
one that must be serviced by this application server because of a dependency that
resides on the server. This request could not successfully be serviced by another
member of the server cluster. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the WLM server. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The valid
format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 72. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
426
ITCAM for Application Diagnostics: User Guide
Table 72. Format of the 12-character timestamp (continued)
Character String
Meaning
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Cluster Update Rate (per sec) The rate (per second) at which this server
received new server cluster information during the sampling interval. The valid
format is a decimal (formatted to 3 decimal places).
Server Cluster Updates The number of times initial or updated server cluster data
are sent to a server member from the deployment manager. This metric determines
how often cluster information is being propagated. The valid format is a positive
integer.
Server Name The name of the WebSphere application server. The valid format is
an alphanumeric string, with a maximum of 256 characters.
Server Response Time (ms) The response time (in milliseconds) at which IIOP
requests were serviced by an application server, calculated based on the time the
request is received versus the time the reply is sent. The valid format is a decimal
(formatted to 3 decimal places).
Total Server Response (ms) The total response time (in milliseconds) at which
IIOP requests were serviced by an application server. The valid format is a decimal
(formatted to 3 decimal places).
Set Instrumentation Level Type Indicates the WebSphere resource category, which
is used by the agent to modify the Instrumentation Level for transaction data
collection.
WLM Clients Serviced The number of WLM-enabled clients this application server
has serviced during the interval. The valid format is a positive integer.
WLM Clients Serviced Rate (per sec) The rate (per second) at which this server
has serviced WLM-enabled clients during the sampling interval. The valid format
is a decimal (formatted to 3 decimal places).
WLM Server Weight A control for work directed to the application server: if the
server's weight value is greater than the weight values assigned to other servers in
the cluster, then the server receives a larger share of the cluster's workload. The
valid format is a positive integer.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Chapter 4. ITCAM Agent for WebSphere
427
Workplace Mail IMAP/POP attributes
The Workplace Mail IMAP/POP attributes displays the usage information for the
IMAP service and POP3 service connectivity.
The attributes within this group are used to build the IMAP/POP workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support the IMAP/POP workspace: configuration and links to the Managing
Server Visualization Engine from the Tivoli Enterprise Portal.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Active Sessions The number of active sessions during the sampling interval. The
valid format is a positive integer.
Active SSL Sessions The number of active, secure sessions during the sampling
interval. The valid format is a positive integer.
Authentication Failures The number of authentications failures during the
sampling interval. The valid format is a positive integer.
Connection (ms) The time (in milliseconds) spent connected to clients during the
sampling interval. The valid format is a positive integer.
IMAP Instrumentation Level The instrumentation level for IMAP PMI module.
Valid values are None, Low, Medium, High, Basic, Extended, All, Custom, and
Maximum. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Peak Session load The maximum number of concurrent sessions during the
sampling interval. The valid format is a positive integer.
428
ITCAM for Application Diagnostics: User Guide
POP Instrumentation Level The instrumentation level for POP PMI module. Valid
values are None, Low, Medium, High, Basic, Extended, All, Custom, and
Maximum. Blank if no instrumentation level is set.
Protocol The protocol type of the workplace mail. Valid values are IMAP and POP.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 73. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Successful Authentications The number of successful authentications during the
sampling interval. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v Attribute groups used by the predefined workspaces
Workplace Mail Queues attributes
The Workplace Mail Queues attributes display information about the message
delivery state, including ready retry, unprocessed, and dead.
The attributes within this group are used to build the Messages Queues
workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
Chapter 4. ITCAM Agent for WebSphere
429
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select again it later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support the Message Queues workspace: configuration and links to the Managing
Server Visualization Engine from the Tivoli Enterprise Portal.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Dead The number of message in the dead state in the queue during the sampling
interval. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the service components. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Queue The Lotus Workplace Mail queue name. Valid values are A, B, C, D, E, F, G,
H, and Summary.
Ready The number of message in the ready state in the queue during the sampling
interval. The valid format is a positive integer.
Retry The number of message in the retry state in the queue during the sampling
interval. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
Table 74. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
430
ITCAM for Application Diagnostics: User Guide
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Unprocessed The number of message in the unprocessed state in the queue during
the sampling interval. The valid format is a positive integer.
For additional information, see:
v
v
Organization of the predefined workspaces
Attribute groups used by the predefined workspaces
Workplace Mail Service attributes
The Workplace Mail Service attributes display aggregated usage information
about the incoming mail message traffic.
The attributes within this group are used to build the Workplace Mail workspace.
Note:
v The attributes within this attribute group contain zeros for performance data if
your site set configuration value Resource Data Collection Method to On
Demand (for on-demand sampling) and you have not yet run applications that
generate performance data. To report performance data in these attributes after
installing and configuring the Data Collector, use the WebSphere administrative
console to set the appropriate PMI instrumentation level.
v The Tivoli Enterprise Monitoring Agent is set by default to provide on-demand
sampling; thus the attributes within this attribute group initially contain zeros
until you select the workspace and then select it again later. Each time you select
the workspace, these attributes are updated with the latest data.
Note: The following WebSphere Application Diagnostics 7.1 features do not
support Workplace Mail Service: configuration and links to the Managing Server
Visualization Engine from the Tivoli Enterprise Portal.
Note: For information about WebSphere PMI metrics, refer to Appendix A.
WebSphere PMI Attribute Mapping ITCAM for Application Diagnostics User Guide,
available from: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml.
Active LDAP Connections The number of active LDAP connections during the
sampling interval. The valid format is a positive integer.
Delivered Messages The total number of delivered messages during the sampling
interval. The valid format is a positive integer.
Deliverer Dropped Messages The total number of messages rejected by the SMTP
outbound server during the sampling interval. The valid format is a positive
integer.
Chapter 4. ITCAM Agent for WebSphere
431
Deliverer Message (ms) The total time in milliseconds taken by SMTP outbound
server to process messages during the sampling interval. The valid format is a
decimal (formatted to 3 decimal places).
Dropped SMTP Connections The total number of the dropped SMTP connections
during the sampling interval. The valid format is a positive integer.
DSN Failure Messages The total number of failure DSNs sent during the sampling
interval. The valid format is a positive integer.
Handled Messages The total number of messages processed by the mail handler
server during the sampling interval. The valid format is a positive integer.
Handler Dropped Messages The total number of messages rejected by the mail
handler server during the sampling interval. The valid format is a positive integer.
Instrumentation Level The instrumentation level for the service components. For
WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom.
Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is
a positive integer.
Live SMTP Server Connections The number of live SMTP server connections
during the sampling interval. The valid format is a positive integer.
Live SMTP Client Connections The number of live SMTP client connections
during the sampling interval. The valid format is a positive integer.
Lost SMTP Client Connections The total number of lost SMTP client connections
during the sampling interval. The valid format is a positive integer.
Lost SMTP Connections The total number of the lost SMTP connections during
the sampling interval. The valid format is a positive integer.
Message Delivery (ms) The total time in milliseconds taken to deliver messages
during the sampling interval. The valid format is a decimal (formatted to 3 decimal
places).
Messages Handling (ms) The total time in milliseconds taken to handle messages
during the sampling interval. The valid format is a decimal (formatted to 3 decimal
places).
Node Name The name of the system on which the server is running. The value
format is an alphanumeric string, with a maximum of 256 characters.
Origin Node The name of the server subnode. The valid format is an
alphanumeric string, with a maximum of 128 characters.
Peak LDAP Connections The maximum number of concurrent LDAP connections
during the sampling interval. The valid format is a positive integer.
Sample Date and Time The date and time the Tivoli Enterprise Management
Agent collected the data. The valid format is a 12-character timestamp. For the STR
and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table
shows the values contained in this character string:
432
ITCAM for Application Diagnostics: User Guide
Table 75. Format of the 12-character timestamp
Character String
Meaning
MM
Month
DD
Day
YY
Year
HH
Hour
MM
Minute
SS
Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006,
at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather
than for creating situations. To specify a time and date for comparison and testing,
use attributes from the Universal Time or Local Time groups.
Server Name The name of the application server. The valid format is an
alphanumeric string, with a maximum of 256 characters.
Smarthost Messages The total number of messages sent to the Smarthost during
the sampling interval. The valid format is a positive integer.
SMTP Client Connections The total number of SMTP client connections during
the sampling interval. The valid format is a positive integer.
SMTP Client (ms) The total time in milliseconds taken to deliver messages during
the sampling interval. The valid format is a decimal (formatted to 3 decimal
places).
SMTP Connections The total number of connections to the SMTP server during
the sampling interval. The valid format is a positive integer.
SMTP (ms) The total time in milliseconds that SMTP has conversed during the
sampling interval. The valid format is a decimal (formatted to 3 decimal places).
SMTP Server Threads The number of active SMTP outbound server threads
during the sampling interval. The valid format is a positive integer.
For additional information, see:
v Organization of the predefined workspaces
v
Attribute groups used by the predefined workspaces
ITCAM for Application Diagnostics - WebSphere Agent situations
IBM Tivoli Composite Application Manager for Application Diagnostics WebSphere Agent has a number of predefined situations that you can use to
complete the following tasks:
v Monitor your WebSphere application servers
v Monitor and manage widely dispersed WebSphere Application Server resources
through localized automation
v Create your own situations using the predefined situations as examples
Chapter 4. ITCAM Agent for WebSphere
433
These predefined situations display an alert status. When these situations trigger
an alert, you can investigate the event by opening its workspace. For example, you
can use these situations to monitor a WebSphere application server for errors
occurring within it or Web applications based at your site.
How the situations work
Situations are tests expressed in IF-TRUE format of system conditions that you
want to monitor; the tested value is an ITCAM for Application Diagnostics WebSphere Agent attribute expressed in the form attribute-group.attribute-name. If
the specified condition occurs or exists, the situation is true, and an alert is issued.
Avoid using negative values
If you define situations that use a counter or a range of numbers, always provide a
threshold or use values in a positive range of numbers. For example, use a
greater-than-or-equal-to-zero expression as shown in some of the following
predefined situations. This practice prevents a situation from falsely tripping. If the
ITCAM for Application Diagnostics - WebSphere Agent Tivoli Enterprise
Management Agent encounters an undefined attribute value, it interprets this value
as a negative number and will erroneously fire a situation that specifies a negative
number.
Note: For the following situations; WASDBConPAvgWaitTimeHigh,
DB_Connection_Pools, J2C_Connection_Pools, and Thread_PoolsApplication the
Application ID column is not supported and always displays -1 by default.
Accessing the situations
A number of the predefined situations run by default from the WebSphere Agent,
for the situations that do not run automatically you need to start these situations
manually. To start these situations access the situations in the Tivoli Enterprise
Portal using one of the following methods:
v In the WebSphere agent, right click the specific server. Right click Enterprise
then, click Manage Situations to display all the managed situations available on
the server. If you want to start, stop edit or model a situation right click the
situation and select the option you want.
v From the toolbar on the main menu click the Situation Editor icon
scroll to the situation you want to view.
and
For information on predefined situations and formulas see “Predefined
situations-descriptions and formulas (that run automatically)” and “Predefined
situations descriptions and formulas (that run manually)” on page 438. See also
“ITCAM for Application Diagnostics- WebSphere Agent attributes” on page 301.
Predefined situations-descriptions and formulas (that run
automatically)
The following predefined situations run automatically from the WebSphere Agent
and support the following applications servers unless stated otherwise.
v WebSphere Application Server
v WebSphere Application Server portal
v WebSphere Application Server Process
434
ITCAM for Application Diagnostics: User Guide
v WebSphere Application Server ESB
v Lotus Workplace server
Note:
v If you want to start, stop or edit any of these situations see “Accessing the
situations” on page 434.
v For information about situations that run manually see “Predefined situations
descriptions and formulas (that run manually)” on page 438.
WASAppDiscovered monitors WebSphere applications deployed in the application
server and issues an Informational alert when a new application is discovered. The
monitoring agent checks for new applications each time it connects to the Data
Collector or when an application is deployed when the Data Collector is already
active. The formula is:
If
Application_Monitoring_Configuration.Monitoring_Status equals 0
then
the situation WASAppDiscovered is true.
Note: This situation does not support Lotus Workplace server.
The predefined Take Action command Start_Baselining associated with the
WASAppDiscovered situation enables you to automate the baselining of newly
discovered applications.
WASAppHealthBad monitors the overall application health and issues a Critical
alert when the application health is bad. The formula is:
If
Application_Health_Status.Web_Tier_Health equals 3
then
the situation WASAppHealthBad is true.
The predefined Take Action command Set_Appliction_Monitoring associated with
WASAppHealthBad situation increases the request monitoring rate for applications
generated alert. This command enables you to collect more detailed performance
data and helps to collect the most precise data about each application tier health
level.
WASAppHealthFair monitors the overall application health and issues a warning
alert when application health is fair. The formula is:
If
Application_Health_Status.Application_Health equals 2
then
Chapter 4. ITCAM Agent for WebSphere
435
the situation WASAppHealthFair is true.
The predefined Take Action command Set_Appliction_Monitoring associated with
WASAppHealthFair situation raises the request monitoring level for applications
generated alert. This command enables you to collect detailed performance data
that helps to pinpoint a bottleneck down to particular application tiers.
WASAppHealthGood monitors the overall application health and issues an
Informational alert when application health is good. The formula is:
If
Application_Health_Status.Application_Health equals 1
then
the situation WASAppHealthGood is true.
The predefined Take Action command Set_Appliction_Monitoring associated with
the WASAppHealthGood situation lowers the request monitoring level for
applications generated alert, and reduces the monitoring workload.
WASError monitors the error severity for a single WebSphere Application Server
and issues a Critical condition whenever that severity is greater than 21. Its
formula is:
If
Log_Analysis.Severity is greater than 21
then
the situation WASError is true.
WASHighCPUPercentUsed monitors the percentage of the CPU being consumed
and issues a Critical condition whenever that time exceeds 80%. The formula is:
If
Application_Server.CPU_Used_Percent is greater than 80
then
the situation WASHighCPUPercentUsed is true.
WASHighGCTimePercent monitors the percentage of time being spent by the
garage collector and issues a Critical condition whenever that time exceeds 80%.
The formula is:
If
Garbage_Collection_Analysis.Real_Time_Percent is greater than 80
then
the situation WASHighGCTimePercent is true.
436
ITCAM for Application Diagnostics: User Guide
WASHighResponseTime monitors the average request response time and issues a
Critical condition whenever that time exceeds 2 seconds. The formula is:
If
Request_Times_and_Rates.Average_Request_Response_Time is greater than 2000
then
the situation WASHighResponseTime is true.
WASNotConnected monitors the connection between the ITCAM for WebSphere
Data Collector running in an application server and the ITCAM for Application
Diagnostics - WebSphere Agent monitoring agent to ensure that the monitoring
agent is connected and issues a Critical condition whenever it is not. Its formula is:
If
Application_Server_Status.Status equals 0
then
the situation WASNotConnected is true.
WASOutofHeapSpace monitors the heap allocation status and issues a Critical
condition whenever heap space is exhausted. The formula is:
If
Allocation_Failure.Heap_Status equals 1
then
the situation WASOutofHeapSpace is true.
Note: This situation is not available when monitoring non-IBM Java Virtual
Machines, including machines commonly used on HP-UX and Solaris platforms.
WASAvgHeapSizeAfterGCHigh monitors the average heap size free percentage
after garbage collection. This situation issues a Critical alert if the average heap
size free percentage after garbage collection is greater than 80%. Its formula is:
If
Garbage_Collection_Cycle.Heap_Free_Percent_after_GC is greater than 80
then
the situation WASAvgHeapSizeAfterGCHigh is true.
Note: This situation does not support Lotus Workplace server.
WASJ2CConnectionPoolUsageMaxed monitors the J2C pool percentage usage and
issues a Warning alert if the pool usage is greater than or equal to 100%. Its
formula is:
Chapter 4. ITCAM Agent for WebSphere
437
If
J2C_Connection_Pools.Pool_Used_Percent is greater than or equal to 100%
then
the situation WASJ2CConnectionPoolUsageMaxed is true.
Note: This situation does not support Lotus Workplace server.
WASDBConnectionPoolUsageMaxed monitors the JDBC pool usage and issues a
Critical alert if the pool usage is greater than or equal to 100%. Its formula is:
If
DB_Connection_Pools.Percent_Used is greater than or equal to 100%
then
the situation WASDBConnectionPoolUsageMaxed is true.
Note: This situation does not support Lotus Workplace server.
See also “ITCAM for Application Diagnostics- WebSphere Agent attributes” on
page 301.
Predefined situations descriptions and formulas (that run
manually)
Situations that are run manually
The following situations do not run automatically, to run them you need to access
them from the Manage Situations view. These situations support the following
application servers unless stated otherwise:
v WebSphere Application Server
v WebSphere Application Server portal
v WebSphere Application Server Process
v WebSphere Application Server ESB
v Lotus Workplace server
Note:
v If you want to start, stop or edit any of these situations see “Accessing the
situations” on page 434.
v For information about situations that run automatically see “Predefined
situations-descriptions and formulas (that run automatically)” on page 434.
WASDBConnectionPoolThreadTimeout monitors the thread timeout count. This
situation issues a Critical condition whenever the timeout count is greater than
zero. Its formula is:
If
DB_Connection_Pools.Threads_Timed_Out is greater than 0
438
ITCAM for Application Diagnostics: User Guide
then
the situation WASDBConnectionPoolThreadTimeout is true.
WASContainerTransactionRollback monitors the rollback count of the WebSphere
Application Server. This situation issues a Critical alert whenever the count
becomes nonzero. Its formula is:
If
Container_Transactions.Global_Transactions_Rolled_Back is greater than 0
or
Container_Transactions.Local_Transactions_Rolled_Back is greater than 0
or
Container_Transactions.Transactions_Rolled_Back is greater than 0
then
the situation WASContainerTransactionRollBack is true.
WASEJBCreateTimeHigh monitors the average time of a bean create call and
issues a Critical alert when the time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Create_Average_Time is greater than 2000
then
the situation WASEJBCreateTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASEJBRemoveTimeHigh monitors the average time of a bean remove call and
issues a Critical alert when the time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Remove_Average_Time is greater than 2000
then
the situation WASEJBRemoveTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASEJBMethodResponseTimeHigh monitors the average response time on
remote interface methods for all beans. This situation issues a Critical alert if the
response time is longer than 2 seconds. Its formula is:
If
Chapter 4. ITCAM Agent for WebSphere
439
Enterprise_Java_Beans.Method_Average_Response_Time is greater than 2000
then
the situation WASEJBMethodResponseTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASThreadFreeLow monitors the average free threads in the pool and issues a
Critical alert if the number of threads is less than 200. Its formula is:
If
Thread_Pools.Average_Free_Threads is less than 200
then
the situation WASThreadFreeLow is true.
Note: This situation does not support Lotus Workplace server.
WASDataSrcConWaitTimeHigh monitors the average time an application has to
wait for a connection. This situation issues a Critical alert if the wait time is longer
than 2 seconds. Its formula is:
If
Datasources_Connection_Average_Wait_Time is greater than 2000
then
the situation WASDataSrcConWaitTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASReqSQLExecuteTimePercentHigh monitors the percentage of time the request
spends executing a JDBC database. This situation issues a Critical alert if the
percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Execute_Time_Percent is greater than 80
then
the situation WASReqSQLExecuteTimePercentHigh is true.
Note: This situation does not support Lotus Workplace server.
WASReqSQLQueryTimePercentHigh monitors the percentage of time the request
spends querying a JDBC database. This situation issues a Critical Alert if the
percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Query_Time_Percent is greater than 80
440
ITCAM for Application Diagnostics: User Guide
then
the situation WASReqSQLQueryTimePercentHigh is true.
Note: This situation does not support Lotus Workplace server.
WASReqSQLUpdateTimePercentHigh monitors the percentage of time the request
spends updating a JDBC database. This situation issues a Critical Alert if the
percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Update_Time_Percent is greater than 80
then
the situation WASReqSQLUpdateTimePercentHigh is true.
Note: This situation does not support Lotus Workplace server.
WASDBConPAverageTimeHigh monitors the average time that a connection in
use is high. This situation issues a Critical alert if the average time the connection
in use is longer than 2 seconds. Its formula is:
If
DB_Connection_Pools.Average_Usage_Time is greater than 2000
then
the situation WASDBConPAverageTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASDBConPPercentUsedTimeHigh monitors the average percentage of time the
connection pool in use is high. This situation issues a Critical alert if the average
percentage of time the connection pool in use is higher than 80%. Its formula is:
If
DB_Connection_Pools.Percent_Used is greater than 80
then
the situation WASDBConPPercentUsedTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASDBConPAvgWaitTimeHigh monitors the average time that a client has to
wait for a connection. This situation issues a Critical alert when the time period is
longer than 2 seconds. Its formula is:
If
DB_Connection_Pools.Average_Wait_Time is greater than 2000
Chapter 4. ITCAM Agent for WebSphere
441
then
the situation WASDBConPAvgWaitTimeHigh is true.
Note: This situation does not support Lotus Workplace server.
WASJ2CCPAverageUsageTimeHigh monitors the average time that connections
are in use (it measures from when the connection is allocated to when it is
returned). This situation issues a Critical alert when the combined conne
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
Download PDF
advertisement