Four types of data that the TEMA collects.

Answer

Among the 4 Types of data* that TEMA collects for the workspaces in the TEP to display, this document provides "setting" information for Resource Data and Request Data.

I. The TEP workspaces that display Resource data are:
Web Applications, Web Applications: Servlets/JSP, Web Applications: Sessions,
EJB Containers, EJB Containers:Enterprise Java Beans, EJB Containers:Container Transactions,
EJB Containers:Container Object Pools, Web Applications: Servlets/JSPs ,
DB Connection Pools, J2C Connection Pools, Thread Pools,
Cache Analysis: Dynamic Cache, Cache Analysis: Dynamic Cache Templates,
Workload Management: Workload Management Server,
Workload Management: Workload Management Client,
Scheduler, Web Services Gateway, Messaging Engines,
Client Communications, Messaging Engine Communications,
WMQ Client Link Statistics, WMQ Link Statistics

II. The TEP workspaces that display Request data are:
Request Analysis
Request Analysis : Datasources, JMS Queues, Resrouce Adapters,
Data Sources, JMS Summary,

III. What to check if Resource Type or Request Type Categories of data are not displayed:
A. Resource Data -
** The data availability in these workspaces depends on
** - the enablement of PMI* in WAS*
** - on the level of PMI* data collection that is turned on.

To view the Resource data in the TEP workspaces, you will need to:
1. Have the appropriate resources defined. (ex: JDBC providers defined
with connection pools to see data in DB Connection pools, Schedulers
defined to see any data in the Schedulers workspace, etc. )
2. Turn on the PMI monitoring in the WAS
(either through admin console, wsadmin or custom scripts)
3. Select the appropriate level of PMI data collection based on the
desired data that needs to be monitored.

B. Request Data -
** There are 2 parameters that determines the amount of data collected.
** - Request Data Monitoring.
** - Request Data Sampling Rate

1. The Request Data Monitoring Level - Default :"Level 1"
The “Level 2” collects more detailed data and incurs additional overhead
in terms of memory and processing time.
The value can be changed using the “Start Request Monitoring” Take Action command
and supplying the desired value in the argument field (1 or 2).

2. The Request Data Sampling Rate - Default : 2% (i.e. only 2 out of every 100 requests
tracked). If the load on your system is very low (for example, in a test system you
apply a 10 user load), then it is likely that you will not see data in the Request Data
workspaces with the default setting of 2% since the probability of tracking one of the 10
requests will be very low. Hence, you will need to increase the sampling rate in
systems with low load. This can be done by using the “Set_Request_Sampling_Rate”
Take Action command and supplying the sampling percentage (a value of 100 will track
all the user requests).


C. There are no specific setting for Log Analysis and Pool analysis.
1. Log Analysis - Reports WAS and DC errors, so it's valid that to be empty
2. Pool Analysis - It's mostly the same data as Thread Pools. One can use Thread Pools
for information of Pool Analysis. Pool Analysis depends on the same PMI setting as
Thread Pools, which is the same setting as (Resource Data).

*footnote :
- 4 Types of Data :
Resource Data, Request Data, Data from WebSphere log files,
Process data from the Operating System
- WAS : WebSphere Application Server
- TEP : Tivoli Enterprise Portal