Setting up historical data collection for Response Time

Suggested history data collection settings for Response Time

Table 1 gives suggested values for the fields in the History Collection Configuration window for the Response Time workspaces.

Table 1. Suggested history data collection settings for Response Time
Component	Attribute Group	Summarization	Pruning
Robotic Response Time	RRT Agent Messages	Not required	Detailed data keep 30 days
	RRT Application Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	RRT Robotic Playback Events	Not required	Detailed data keep 30 days
	RRT Robotic Playback Status	Not required	Detailed data keep 30 days
	RRT SubTransaction Instance	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 1 day
	RRT SubTransaction Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	RRT Transaction Instance	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 1 day
	RRT Transaction Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
Web Response Time	WRT Agent Messages	Not required	Detailed data keep 30 days
	WRT Application Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT Client Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT SSL Alert Current Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT Server Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT SubTransaction Instance	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 1 day
	WRT SubTransaction Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT TCP Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT Transaction Instance	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 1 day
	WRT Transaction Status	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days
	WRT User Sessions	Weekly Daily Hourly	Weekly keep 2 months Daily keep 14 days Hourly keep 7 days Detailed data keep 3 days

Verifying the setup

To verify the Tivoli Data Warehouse is collecting and storing historical data properly, examine the warehouse database, and verify that the tables are included in the database and that they contain data. The location of the warehouse database was specified during its installation, so ask the person who installed it where it is located.

Connect to the WAREHOUS.
Note: There is no E.
Type one of the following select statements, depending on which monitoring agent you want to check:
Note: Table and column names must have double quotation marks and exact capitalization.
- select count(*) from "WRT_Transaction_Status"
- select count(*) from "RRT_Transaction_Status"

Depending on the operating system, the software displays a response similar to the following example:

db2 => select count(*) from "WRT_Transaction_Status"
1
-----------
  351
  1 record(s) selected.

If the record count is greater than 0 (zero), then the data warehouse is collecting data properly.

Troubleshooting historical data collection

If ITMUser has insufficient privileges, Tivoli Data Warehouse cannot create the appropriate tables in the WAREHOUS database.

Symptom

If the WAREHOUS database does not have any tables created by ITMUSER, the Warehouse Proxy log (<hostname>_hd_nnnnnnnnnn.log) contains the following error:

"[IBM][CLI Driver][DB2/NT] SQL0552N 
"ITMUSER" does not have the 
privilege to perform operation "CREATE BUFFERPOOL". 
SQLSTATE=42502

Solution

When the ODBC data source, DB2® database, and DB2 user are created, the user is created as a member of the Windows® Administrator group. On some platforms (such as Windows XP), the user might not be created. Add the OS ITMUSER to the Administrator group and to the DB2ADMNS Windows group manually. If the DB2 database is remote, the user on the remote system must be a member of the DB2ADMIN group.

Customizing data collected for instance tables

In addition to setting history data collection, using the Application Management Configuration Editor you can customize the way in which instances are collected and therefore the default content of the WRT Transaction Instance table. For example, to customize instance collection for Web Response Time:

In the Application Management Configuration Editor, select Profiles in the drop-down list then select the default Web Response Time profile.
On the Transactions tab, select the Web Transactions profile.
On the Properties tab, select the required type of instance collection in the Collect instances list.
Click OK.

See Defining profiles for further information.