publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/itmftp/sc23-4802-00/en... · 2003-10-04 ·...

IBM Tivoli Monitoring for Transaction PerformanceWeb Transaction Performance

User’s GuideVersion 5.1.0

SC23-4802-00

��

NoteBefore using this information and the product it supports, read the information in Appendix F, “Notices” on page 151.

First Edition (November 2002)

This edition applies to Version 5.1.0 of IBM Tivoli® Monitoring for Transaction Performance and to all subsequentreleases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2002. All rights reserved. US Government UsersRestricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

About this guide . . . . . . . . . . . xiWho should read this guide . . . . . . . . . xiPublications . . . . . . . . . . . . . . xii

IBM Tivoli Monitoring for TransactionPerformance library . . . . . . . . . . xiiPrerequisite publications . . . . . . . . . xiiiRelated Publications . . . . . . . . . . xvAccessing softcopy publications . . . . . . xvOrdering publications . . . . . . . . . . xvProviding feedback about publications . . . . xv

Accessibility . . . . . . . . . . . . . . xviContacting Customer Support . . . . . . . . xviTypeface conventions used in this guide . . . . xvi

Chapter 1. Introducing Web TransactionPerformance . . . . . . . . . . . . . 1The Web Transaction Performance applications . . . 1

Quality of Service. . . . . . . . . . . . 1Site Investigator . . . . . . . . . . . . 1Synthetic Transaction Investigator . . . . . . 2STI Player capabilities . . . . . . . . . . 2

Installable components . . . . . . . . . . . 4Internet Management Server . . . . . . . . 6Internet Management Endpoints . . . . . . . 6The STI Recorder . . . . . . . . . . . . 8Tivoli Decision Support for Web TransactionPerformance . . . . . . . . . . . . . 8

Managing the Web services environment . . . . . 8Creating and scheduling jobs . . . . . . . . 8Handling events . . . . . . . . . . . . 9Collecting historical data . . . . . . . . . 9Viewing results . . . . . . . . . . . . 10

Integration with enterprise products . . . . . . 10IBM Tivoli Enterprise Console . . . . . . . 11Tivoli Enterprise Data Warehouse . . . . . . 11Tivoli Decision Support . . . . . . . . . 11IBM WebSphere Site Analyzer . . . . . . . 12IBM WebSphere Application Server . . . . . 12

System configuration example . . . . . . . . 12Collecting ARM data from IBM WebSphere. . . . 16

ARM concepts . . . . . . . . . . . . 17ARM support in IBM WebSphere . . . . . . 17Collecting WebSphere ARM data in EnterpriseTransaction Performance . . . . . . . . . 19Collecting WebSphere ARM data in WebTransaction Performance . . . . . . . . . 21

Chapter 2. GUI Overview andNavigation . . . . . . . . . . . . . 25Starting the GUI . . . . . . . . . . . . . 25

Areas of the GUI . . . . . . . . . . . . 26Help Button . . . . . . . . . . . . . 26Work Area. . . . . . . . . . . . . . 27Navigation . . . . . . . . . . . . . 27

Chapter 3. Quality of Serviceapplication . . . . . . . . . . . . . 29User scenarios . . . . . . . . . . . . . 30Configuring QoS jobs . . . . . . . . . . . 30

Selecting a QoS endpoint . . . . . . . . . 31Creating a QoS job schedule . . . . . . . . 31Configuring parameters for a QoS job . . . . 33Configuring constraints for a QoS job. . . . . 35Naming a QoS job . . . . . . . . . . . 37

QoS Administration . . . . . . . . . . . 38Editing a QoS job . . . . . . . . . . . 38Managing QoS jobs . . . . . . . . . . . 38Configuring events . . . . . . . . . . . 40Examining the event log . . . . . . . . . 42Viewing QoS reports . . . . . . . . . . 43

Chapter 4. Site Investigator application 45User scenarios . . . . . . . . . . . . . 45Configuring a Site Investigator job. . . . . . . 46

Selecting a Site Investigator endpoint . . . . . 47Configuring a schedule for a Site Investigator job 47Configuring parameters for a Site Investigator job 48Configuring proxies for a Site Investigator job . . 50Configuring constraints for a Site Investigator job 50Naming a Site Investigator job . . . . . . . 53

Site Investigator Administration . . . . . . . 53Editing a Site Investigator job . . . . . . . 53Managing Site Investigator jobs. . . . . . . 53Configuring Site Investigator events . . . . . 54Examining the Site Investigator event log . . . 55Reviewing investigation results . . . . . . . 55

Chapter 5. Synthetic TransactionInvestigator application . . . . . . . 57User scenarios . . . . . . . . . . . . . 58Downloading the STI recorder . . . . . . . . 58Installing the STI Recorder . . . . . . . . . 59Using the STI recorder. . . . . . . . . . . 62Editing a transaction . . . . . . . . . . . 66Deleting a transaction . . . . . . . . . . . 66Creating a transaction playback. . . . . . . . 67

Choosing an endpoint . . . . . . . . . . 67Configuring a schedule . . . . . . . . . 67Choosing a Transaction . . . . . . . . . 68Configuring proxy information . . . . . . . 68Configuring constraints . . . . . . . . . 69Assigning a job name . . . . . . . . . . 70Playback endpoint configuration . . . . . . 70ARM correlation. . . . . . . . . . . . 71

STI administration . . . . . . . . . . . . 72

iii

Editing transaction playbacks . . . . . . . 72Managing STI jobs . . . . . . . . . . . 72Configuring STI events . . . . . . . . . 73Viewing Synthetic Transaction Investigator events 74Event drill down . . . . . . . . . . . 75Synthetic Transaction Investigator reports . . . 76Viewing ARM correlation data through STIreports . . . . . . . . . . . . . . . 79Viewing the Page Analyzer Viewer reportthrough the STI event log . . . . . . . . 80Viewing the Page Analyzer Viewer reportthrough STI reports. . . . . . . . . . . 80The Page Analyzer Viewer display window . . 80The Page Analyzer Viewer tree . . . . . . . 81The Page Analyzer Viewer chart . . . . . . 81The Legend window . . . . . . . . . . 83Tree display icons . . . . . . . . . . . 84Properties displays . . . . . . . . . . . 86

Chapter 6. General SystemAdministration . . . . . . . . . . . 89Historical data collection . . . . . . . . . . 89

Configuring an historical data collection job . . 90Viewing the historical data collection event log 90

Global views . . . . . . . . . . . . . . 90Managing jobs . . . . . . . . . . . . 90Viewing the global event log . . . . . . . 90Viewing all endpoints . . . . . . . . . . 91

System administration . . . . . . . . . . . 92Configuring event severities . . . . . . . . 92Configuring system events . . . . . . . . 92Viewing the system event log . . . . . . . 94Creating event responses . . . . . . . . . 94Archiving Offline Endpoints . . . . . . . . 95Managing application data . . . . . . . . 95Managing accounts . . . . . . . . . . . 95Viewing log files. . . . . . . . . . . . 97Viewing TIMS details . . . . . . . . . . 97

User preferences . . . . . . . . . . . . . 97Changing passwords . . . . . . . . . . 97Changing the time zone . . . . . . . . . 97

Chapter 7. Tivoli Decision SupportGuide for Web TransactionPerformance . . . . . . . . . . . . 99Building cubes . . . . . . . . . . . . . 99Scheduling the cube build task . . . . . . . 100Topics and views . . . . . . . . . . . . 101Tivoli Decision Support problem determination . . 102

Solving cube building problems . . . . . . 102Solving report problems . . . . . . . . . 104

Chapter 8. Managing events and eventresponses . . . . . . . . . . . . . 105Creating event responses . . . . . . . . . 106

Forwarding events to the Tivoli EnterpriseConsole . . . . . . . . . . . . . . 106Forwarding events to an SNMP managementapplication . . . . . . . . . . . . . 107

Forwarding events to an e-mail account . . . 108Forwarding events to the EXEC service. . . . 109Forwarding event data using the EXEC service 110Configuring events . . . . . . . . . . 112Event severity . . . . . . . . . . . . 112Event types . . . . . . . . . . . . . 113

Chapter 9. Managing the event service 119Forwarding events to the Tivoli Enterprise Console 119Forwarding events to an SNMP ManagementApplication . . . . . . . . . . . . . . 120Configuring the Web Transaction Performance andSNMP Servers . . . . . . . . . . . . . 120Forwarding events to an e-mail account . . . . 121Configuring the Web Transaction PerformanceServer . . . . . . . . . . . . . . . . 121

Appendix A. Stopping and starting 123Stopping and starting the Internet ManagementServer . . . . . . . . . . . . . . . . 123

Stopping and starting on Windows systems . . 123Stopping and starting on UNIX systems . . . 123

Stopping and starting an Internet ManagementEndpoint . . . . . . . . . . . . . . . 124

Stopping and starting on Windows systems . . 124Stopping and starting on UNIX systems . . . 124

Stopping and starting the Quality of Service proxyserver . . . . . . . . . . . . . . . . 125

Appendix B. Accessibility . . . . . . 127Navigating the interface using the keyboard . . . 127Magnifying what is displayed on the screen . . . 128Using Home Page Reader version 3.02 with WebTransaction Performance. . . . . . . . . . 128

Appendix C. Problem Determination 129User Interface Logging . . . . . . . . . . 129

Adjusting Log File Settings . . . . . . . . 129Tracing . . . . . . . . . . . . . . . 131Running Synthetic Transaction Investigator invisible mode. . . . . . . . . . . . . . 131Historical collection tasks . . . . . . . . . 132

Historical collections are not running . . . . 134Synthetic Transaction Investigator . . . . . . 134

Internet Explorer process stays up in memory. Iftransaction is played back in visible mode, thedialog displays.. . . . . . . . . . . . 134The endpoint generates a URL not available(Navigation canceled) event and displays red barsin the real time graph. . . . . . . . . . 134The endpoint generates URL Not Available(timeout) events and displays red bars in the realtime graph. . . . . . . . . . . . . . 135The endpoint generates a URL not available(Navigation canceled) event and displays red barsin the real time graph. . . . . . . . . . 135The endpoint generates URL not available eventsand displays red bars in the real time graph. . . 135The endpoint generates URL not available eventsand displays red bars in the real time graph. . . 136

iv Web Transaction Performance User’s Guide

Every attempt to run a transaction results in aNavigation Cancel event and red bars display inthe transaction graph. . . . . . . . . . 136

Web Services Courier and Tivoli Decision Supporthistorical data collection . . . . . . . . . . 138

The event log in the Web TransactionPerformance server web interface indicates ahistorical collection failure with at least oneapplication task (Synthetic TransactionInvestigator, SI, or QoSM). . . . . . . . . 138The event log in the web interface does notindicate a problem and the historical datacollection tasks completed, but there is no newdata displayed in the reports. . . . . . . . 138The Tivoli Decision Support reports display nodata for a specific time period but thecollections ran successfully. . . . . . . . . 138

Quality of Service endpoint . . . . . . . . 139An installation of QOS or TIMS altersfunctionality on a machine with the GSK5package already installed. . . . . . . . . 139QOS is configured to be secure-in/secure-out,but does not connect to the origin server andreturns a 502 Proxy error. . . . . . . . . 139A 502 Proxy error is returned . . . . . . . 140How do I keep QOS from logging imagerequests? . . . . . . . . . . . . . . 140The Web site code includes port numbers in theURL that are not the QOS ports. The loadbalancer is not set up so that all servers operatethe same. . . . . . . . . . . . . . . 140

QOS seems to redirect forhttp://mysite.com:82/, but not forhttp://mysite.com/. . . . . . . . . . . 140QOS does not work with host headers . . . . 141QOS setup that uses SSL does not connect to theorigin server and SSL-related errors display inthe proxy-error.log. . . . . . . . . . . 141The javascript inserted into the HTML includesa URL that contains the name of the QOS serveritself is not accessible to the outside world. . . 142

Appendix D. Messages . . . . . . . 143Message format . . . . . . . . . . . . 143User interface message number ranges . . . . . 143Message descriptions . . . . . . . . . . . 144

Appendix E. HTTP status codes . . . 149

Appendix F. Notices . . . . . . . . 151Trademarks . . . . . . . . . . . . . . 153

Glossary . . . . . . . . . . . . . 155

Index . . . . . . . . . . . . . . . 163

Contents v

vi Web Transaction Performance User’s Guide

Figures

1. STI Player capabilities . . . . . . . . . 32. Installable Web Transaction Performance

components . . . . . . . . . . . . . 53. Internet Management Endpoint types . . . . 74. Historical data collection . . . . . . . . 105. Sample Web services environment before Web

Transaction Performance components areinstalled. . . . . . . . . . . . . . 13

6. Sample Web services environment with WebTransaction Performance components installed . 14

7. ARM data collection in IBM WebSphere 198. Collection of WebSphere ARM data by

Enterprise Transaction Performance . . . . 209. Collecting and viewing WebSphere ARM data

in an STI Player job . . . . . . . . . . 2310. Choosing a QoS Endpoint. . . . . . . . 3111. Using an existing schedule when creating a job 3212. Choosing a start time for a new job schedule 3213. Choosing a termination time for a new job

schedule . . . . . . . . . . . . . 3314. Choosing an existing Parameter configuration

for a new QoS job . . . . . . . . . . 3315. Choosing a frequency of requests to consider

for a new QoS job . . . . . . . . . . 3416. Enabling the Back-end Service time only check

box . . . . . . . . . . . . . . . 3417. Choosing multiple or single conditions

parameter settings . . . . . . . . . . 3418. Configuring the parent directory condition 3519. Configuring the IP address condition . . . . 3520. Configuring the URI condition . . . . . . 3521. Choosing an existing constraint configuration 3622. Creating a new QoS job constraint set . . . . 36

23. Assigning a name to a job. . . . . . . . 3724. Selecting a QoS job to edit . . . . . . . 3825. Unscheduling QoS jobs . . . . . . . . 3926. Showing all QoS jobs . . . . . . . . . 4027. Selecting an event type to configure . . . . 4128. Selecting an event severity . . . . . . . 4129. Selecting an event response . . . . . . . 4130. QoS event table of configured events . . . . 4231. How Quality of Service measures the user

experience . . . . . . . . . . . . . 4432. Using an existing job’s schedule to create a

new Site Investigator job . . . . . . . . 4733. Typing realm information for an investigation 4934. Removing a realm name from the list of those

to be investigated . . . . . . . . . . 4935. Configuring the page size constraint for a site

investigation . . . . . . . . . . . . 5136. Configuring the desired content constraint for

a site investigation . . . . . . . . . . 5137. Configuring the undesired content constraint

for a site investigation . . . . . . . . . 5238. Configuring HTTP response code constraints

for a site investigation . . . . . . . . . 5239. Choosing a termination time for a new job

schedule . . . . . . . . . . . . . 6840. How Synthetic Transaction Investigator

measures round trip time . . . . . . . . 7641. How Page Analyzer Viewer monitors sub

document transactions . . . . . . . . . 7942. Page Analyzer Viewer display . . . . . . 8143. Legend window . . . . . . . . . . . 8444. Page Properties display . . . . . . . . 8645. Item Properties display . . . . . . . . 87

vii

viii Web Transaction Performance User’s Guide

Tables

1. Summary of topics covered in this chapter 292. Quality of Service event types . . . . . . 403. Valid values for the qoscolumns key in the

ReportConfig.properties file . . . . . . . 434. Summary of topics covered in this chapter 45

5. Site Investigator event types . . . . . . . 546. Summary of topics covered in this chapter 577. Synthetic Transaction Investigator event types 738. Keyboard shortcuts for the product . . . . 127

ix

x Web Transaction Performance User’s Guide

About this guide

IBM Tivoli Monitoring for Transaction Performance enables you to manage theavailability and performance of your Web and enterprise application environment.It gathers the detailed information you need to track and improve transactiontimes, with the goal of ensuring optimal responsiveness to users whether inside oroutside the enterprise. The product consists of two components, each with adifferent emphasis:v The IBM Tivoli Monitoring for Transaction Performance component provides

functionality and features that help you provide optimal service to users of youre-business Web sites.

v The Enterprise Transaction Performance component provides functionality andfeatures that help you analyze and improve the performance of your businessapplications.

Each of the product components, in turn, consists of a separate set of installablecomponents (server, endpoint, and reporting software). This guide providesprerequisite information and instructions for installing the IBM Tivoli Monitoringfor Transaction Performance components of the product. For information on howto install the Enterprise Transaction Performance components of IBM TivoliMonitoring for Transaction Performance, see the IBM Tivoli Monitoring forTransaction Performance: Enterprise Transaction Performance User’s Guide.

Version 5.1.0 succeeds Version 1.7 of IBM Tivoli Monitoring for TransactionPerformance. Version 1.7 consolidated the following products:v Tivoli Web Services Manager, Version 1.7. This product is the predecessor to the

Web Transaction Performance component of IBM Tivoli Monitoring forTransaction Performance, Version 5.1.0.

v Tivoli Application Performance Management, Version 2.1. This product is thepredecessor to the Enterprise Transaction Performance component of IBM TivoliMonitoring for Transaction Performance, Version 5.1.0.

Who should read this guideThis guide is for system and Web administrators who want to install the WebTransaction Performance components of IBM Tivoli Monitoring for TransactionPerformance. The guide assumes that readers are familiar with maintainingoperating systems, administering Web servers, maintaining databases, and generalinformation technology (IT) procedures. Specifically, readers of this guide shouldhave some knowledge of the following software:v The operating systems on which you intend to install IBM Tivoli Monitoring for

Transaction Performance components. Supported operating systems includeWindows NT®, Windows® 2000, Windows XP, AIX®, Solaris OperatingEnvironment (referred to as Solaris in this document), Red Hat Linux, SuSELinux, and TurboLinux.

v Web servers, such as IBM® HTTP Server, Apache HTTP Server, and Microsoft®

Internet Information Server.v Web application servers, such as IBM WebSphere™ Application Server.v Internet protocols such as HTTP, HTTPS, TCP/IP, Secure Sockets Layer (SSL),

and Transport Layer Security (TLS).v Digital certificates for secure communication.

xi

v Oracle or IBM DB2® database management systems.

IBM Tivoli Monitoring for Transaction Performance provides optional integrationwith the IBM Tivoli Enterprise Console® and IBM Tivoli NetView® products.Readers must have some knowledge of these products to decide whether to usethem in conjunction with Web Transaction Performance.

PublicationsThis section lists publications in the IBM Tivoli Monitoring for TransactionPerformance library and other related documents. It also describes where to accesssoftcopy publications, how to order Tivoli publications, and how to makecomments on Tivoli publications.

IBM Tivoli Monitoring for Transaction Performance libraryThe following documents provide information about the Web TransactionPerformance component of the IBM Tivoli Monitoring for Transaction Performanceproduct.v IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance

Installation Guide, GC23–4801Provides prerequisite information and instructions for installing the WebTransaction Performance component. This guide also contains information thatyou might find useful after installing the product, such as uninstallationinstructions and reference information about digital certificates.

v IBM Tivoli Monitoring for Transaction Performance: Web Transaction PerformanceUser’s Guide, SC23–4802Provides detailed procedures for using each of the Web Transaction Performanceapplications. The guide also describes the browser-based graphical user interface(GUI), the help system, and how to use Tivoli Decision Support to producegraphical reports from Web Transaction Performance data.

v IBM Tivoli Monitoring for Transaction Performance: Web Transaction PerformanceRelease Notes, GI11–0939Describes the features of the Web Transaction Performance component.

v IBM Tivoli Monitoring for Transaction Performance: Web Transaction PerformanceLimitations and Workarounds Supplement, SC23–4800Provides the latest information about known product limitations andworkarounds for the Web Transaction Performance component. To ensure thatthe information is the latest available, this document is provided only on theWeb, where it is updated as needed. You can access the Limitations andWorkarounds Supplement through the Tivoli Monitoring for TransactionPerformance link on the Tivoli Information Center Web site:

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

v IBM Tivoli Monitoring for Transaction Performance: Web Transaction PerformanceWarehouse Enablement Pack Implementation Guide, SC09–7793Describes how to install and configure the warehouse enablement pack for theWeb Transaction Performance component. This document also describes the dataflow and data structures used by the warehouse pack. The warehouse packenables Web Transaction Performance to transfer data to the Tivoli EnterpriseData Warehouse.

xii Web Transaction Performance User’s Guide



The following documents provide information about the Enterprise TransactionPerformance component of the IBM Tivoli Monitoring for Transaction Performanceproduct.v IBM Tivoli Monitoring for Transaction Performance: Enterprise Transaction

Performance User’s Guide, GC23–4803Provides information about how to install and use the Enterprise TransactionPerformance component.

v Tivoli Decision Support for Enterprise Transaction Performance User’s Guide,GC23–4805Describes how to use Tivoli Decision Support to produce graphical reports fromEnterprise Transaction Performance data.

v IBM Tivoli Monitoring for Transaction Performance: Enterprise TransactionPerformance Release Notes, GI11–0940Describes the features of the Enterprise Transaction Performance component.

v IBM Tivoli Monitoring for Transaction Performance: Enterprise TransactionPerformance Limitations and Workarounds Supplement, SC23–4804Provides the latest information about known product limitations andworkarounds for the Enterprise Transaction Performance component. To ensurethat the information is the latest available, this document is provided only onthe Web, where it is updated as needed. You can access the Limitations andWorkarounds Supplement through the Tivoli Monitoring for TransactionPerformance link on the Tivoli Information Center Web site:


v IBM Tivoli Monitoring for Transaction Performance: Enterprise TransactionPerformance Warehouse Enablement Pack Implementation Guide, SC09–7791Describes how to install and configure the warehouse enablement pack for theEnterprise Transaction Performance component. This document also describesthe data flow and data structures used by the warehouse pack. The warehousepack enables Enterprise Transaction Performance to transfer data to the TivoliEnterprise Data Warehouse.

Prerequisite publicationsWeb Transaction Performance can optionally be integrated with a number ofenterprise products to provide more advanced capabilities. Following is a list ofthese products and some of the publications provided by each product. For adescription of the products and a summary of how they are used by WebTransaction Performance, see “Integration with enterprise products” on page 10.v IBM Tivoli Enterprise Console

– Tivoli Enterprise Installation Guide, GC32-0395Explains how to install and upgrade Tivoli Enterprise™ software within aTivoli management region using the available installation mechanismsprovided by Tivoli Software Installation Service and Tivoli ManagementFramework. Tivoli Enterprise software includes the Tivoli management regionserver, managed nodes, gateways, endpoints, and RDBMS Interface Module(RIM) objects. This guide also provides information about troubleshootinginstallation problems.

– IBM Tivoli Enterprise Console Installation Guide, GC32–0823Discusses how to install, upgrade, and remove IBM Tivoli Enterprise Consolecomponents and provides details about using the event database installationassistant.

About this guide xiii



– IBM Tivoli Enterprise Console User’s Guide, GC32–0667Provides information needed to understand and set up the IBM TivoliEnterprise Console and describes procedures for using all components of theproduct.

– IBM Tivoli Enterprise Console Rule Builder’s Guide, GC32–0669Provides information about developing rules for automating the managementof IBM Tivoli Enterprise Console events received by the IBM Tivoli EnterpriseConsole event server.

v Tivoli Enterprise Data Warehouse

– Tivoli Enterprise Data Warehouse Release Notes, GI11-0857Provides late-breaking information about Tivoli Enterprise Data Warehouseand lists hardware requirements and software prerequisites.

– Installing and Configuring Tivoli Enterprise Data Warehouse, GC32-0744Describes how Tivoli Enterprise Data Warehouse fits into your enterprise,explains how to plan for its deployment, and gives installation andconfiguration instructions. It provides an introduction to the built-in programfor creating and running reports, and contains maintenance procedures andtroubleshooting information.

– Enabling an Application for Tivoli Enterprise Data Warehouse, GC32-0745Provides information about connecting an application to Tivoli EnterpriseData Warehouse. This book is for application programmers who use TivoliEnterprise Data Warehouse to store and report on their application’s data,data warehousing experts who import Tivoli Enterprise Data Warehouse datainto business intelligence applications, and customers who use their local datain the warehouse.

v Tivoli Decision Support

– Tivoli Decision Support Installation Guide

Provides step-by-step procedures for installing the components of TivoliDecision Support. This guide also lists system requirements for TivoliDecision Support.

– Tivoli Decision Support Administrator Guide

Describes the features of the Tivoli Discovery Administrator, including suchtopics as how to connect a data source, how to create cubes, and how toschedule tasks to automatically build cubes and publish views.

– Tivoli Decision Support User’s Guide

Describes the basic features and concepts of Tivoli Decision Support for endusers. This guide introduces the Discovery Interface, explains how to openand work with different types of views, and explains how to configure TivoliDecision Support to display data in the desired format.

v IBM WebSphere Site Analyzer

All information about IBM WebSphere Site Analyzer is provided on thefollowing Web site:

http://www-3.ibm.com/software/webservers/siteanalyzer/library.htmlv IBM WebSphere Application Server, Version 5.0

All information about the IBM WebSphere Application Server Version 5.0 isprovided on the following Web site:

http://wasinfo.raleigh.ibm.com:9080/infocenter/index.jsp

xiv Web Transaction Performance User’s Guide

http://www-3.ibm.com/software/webservers/siteanalyzer/library.html

http://wasinfo.raleigh.ibm.com:9080/infocenter/index.jsp

Related PublicationsThe Tivoli Glossary includes definitions for many of the technical terms related toTivoli software. The Tivoli Glossary is available, in English only, at the followingWeb site:

http://www.tivoli.com/support/documents/glossary/termsm03.htm

Accessing softcopy publicationsThe publications for this product are available in PDF and HTML formats throughthe following media:v IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: Documentation CD,

LK3T-8519–00The Documentation CD contains all of the English language publications for thisproduct, except for the Web-only Limitations and Workarounds supplements. Toaccess the publications, use a Web browser to open the start.html file, which islocated in the root directory of the CD.

v IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: NLS DocumentationCD, LK3T-8616–00The NLS (national language support) Documentation CD contains both Englishand non-English language publications for this product, except for the Web-onlyLimitations and Workarounds supplements. To access the publications, use aWeb browser to open the start.html file, which is located in the root directoryof the CD.

v Tivoli Information CenterIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Information Center Website. The Tivoli Information Center is located at the following Web address:


Click the Tivoli Monitoring for Transaction Performance link to access theproduct library.

Ordering publicationsYou can order hardcopy publications online from the IBM Publications Center:

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-2755v In Canada: 800-426-4968v In other countries, see the following Web site for a list of telephone numbers:

http://www.tivoli.com/inside/store/lit_order.html

Providing feedback about publicationsIf you have comments or suggestions about Tivoli products and documentation,complete the customer feedback survey at the following Web site:

http://www.tivoli.com/support/survey/

About this guide xv

http://www.tivoli.com/support/documents/glossary/termsm03.htm





http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey/

AccessibilityAccessibility features help users who have physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

For additional information, see the Accessibility Appendix in this manual.

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact IBM CustomerSupport for Tivoli products. See the Tivoli Customer Support Handbook at thefollowing Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Customer Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv The information you should gather before contacting Customer Support

Typeface conventions used in this guideThe following typeface conventions are used in this book:

Bold Graphical user interface elements (except for titles of windows anddialogs) and names of keys also appear like this, in bold type.

Italic Variables, values you must provide, new terms, and words andphrases that are emphasized appear like this, in italic type.

Monospace Commands, command options, and code examples appear likethis, in monospace type.

Names of files and directories, text strings you must type, whenthey appear within text, and names of code objects also appear likethis, in monospace type.

xvi Web Transaction Performance User’s Guide

http://www.tivoli.com/support/handbook/

Chapter 1. Introducing Web Transaction Performance

The Web Transaction Performance component of IBM Tivoli Monitoring forTransaction Performance is a centrally managed suite of applications that monitorthe availability and performance of Web-based services. Web TransactionPerformance measures how users experience your Web sites by monitoringresponse times and availability under different conditions and by traversing thesites to ensure properly functioning links and accurate content. Collected data canbe passed to enterprise management applications, which provide additionalcapability for analysis and corrective action. The centralized managementcapability of Web Transaction Performance is a key feature that helps you keepyour Web services available and performing optimally.

This chapter describes the major features and components of Web TransactionPerformance and how they work together. It also provides information to help youplan your environment and prepare for installation. It is recommended that youread this chapter sequentially. Each topic builds on concepts described in precedingtopics.

The Web Transaction Performance applicationsThe IBM Tivoli Monitoring for Transaction Performance component provides thefollowing primary applications:v Quality of Servicev Site Investigatorv Synthetic Transaction Investigator

Each application measures a different aspect of how well a Web site is meeting thegoal of providing effective service to its users.

Quality of ServiceThe Quality of Service application samples HTTP transactions against a Web serverand measures various time intervals involved in completing each transaction. AnHTTP transaction consists of a single HTTP request and response. A sample oftransactions might consist of every tenth transaction from a specific collection ofusers over a peak time period. The sampling typically occurs by statisticallymultiplexing through a load balancer. The Quality of Service application canapproximately measure the following time intervals for each transaction:v Round trip time (also called user experience time). This is the time it takes to

complete the entire transaction, from the moment the user initiates the request(by clicking on a link, for example) until the request is fulfilled. The round triptime includes the page display time.

v Service time (also called back-end service time). This is the time it takes a Webserver to receive the request, process it, and respond to it.

v Page display time (also called page render time). This is the time it takes to render aWeb page on the requestor’s browser, from the time the rendering begins until itis complete.

Site InvestigatorThe Site Investigator application crawls a Web site for missing and damaged links.It can also scan for specified content. For example, it can verify that a corporate

1

logo is on every page or that the site contains no references to discontinuedproducts. The Site Investigator application is useful for testing Web sites or Webpages under development as well as those already in operation.

Synthetic Transaction InvestigatorThe Synthetic Transaction Investigator (STI) application measures how users mightexperience a Web site in the course of performing a specific transaction, such assearching for information, enrolling in a class, or viewing an account. Theapplication consists of two components: the STI recorder and the STI player.v The STI Recorder records as you perform the sequence of steps that make up the

transaction. For example, you might perform the following steps to view anaccount: log on, click to display the main menu, click to view an accountsummary, log off. The mechanism for recording is to save all HTTP requestinformation in an XML document.

v The STI Player replays the recorded transaction. You can schedule the playbackto repeat at different times and from different locations in order to evaluateperformance and availability under varying conditions. During playback, the STIPlayer can measure response times, check for missing or damaged links, andscan for specified content.

The Synthetic Transaction Investigator provides information similar to thatprovided by the Quality of Service and Site Investigator applications, but in thecontext of specific transactions. The Quality of Service and Site Investigatorapplications help you evaluate the overall performance and availability of a Website by sampling response times, exhaustively crawling the site, and scanning allpages for desired or undesired content. The Synthetic Transaction Investigatorsimulates the experience of an individual user by measuring a related sequence ofresponse times and investigating only those Web pages involved in the transaction.

STI Player capabilitiesThe STI Player can work alone or in combination with various applications andfeatures that extend its capability to collect response time measurements. Figure 1on page 3 shows the STI Player with the applications and features that extend its

measurement capability, how they are distributed across the network, and thekinds of time measurements collected. The numbered items in the diagramcorrespond to the numbered sections in the discussion that follows.

2 Web Transaction Performance User’s Guide

1 STI Player alone

A running STI playback job simulates a user peforming some business transactionfrom a Web browser (the client). During the course of the transaction, the clientmakes a number of requests to a Web server. The STI Player measures theround-trip time for each request. This is the time interval from the moment therequest leaves the client until a response arrives back at the client, including thetime it takes to render a new Web page on the browser. Besides the individualround-trip times, the STI Player provides an overall round-trip time for the entireplayback session.

By itself, the STI Player provides only round-trip time measurements. While thisinformation is an important aid for evaluating performance and narrowing thesearch for causes of performance problems, it is even more useful to know what ishappening along the path of each request. The STI Player provides more detailedinformation when working in conjunction with the applications and featuresdiscussed in the following sections.

2 STI Player with Page Analyzer Viewer

Page Analyzer Viewer is a feature of the STI Player that you can enable or disablebefore running a playback job. When enabled, Page Analyzer Viewer measureshow long it takes to retrieve the various sub-documents (such as java script, stylesheets, and images) that make up a Web page to be rendered. You can use thisinformation to assess the performance impact of having several sub-documents ina Web page. If a document contains sub-documents from other servers, you canexamine how the additional DNS resolutions required for each host affect the totalresponse time.

STI

STI + PAV

STI + QOS

STI + ARM

(browser) Web Server back-endservices

WebSphereServer

1

2

3

4

PageAnalyzerViewer

STIPlayer

Qualityof

Service

ARM

round-trip time

sub-document times

service time

ARM measurements

Figure 1. STI Player capabilities

Chapter 1. Introducing Web Transaction Performance 3

While the sub-document times measured by Page Analyzer Viewer can involveback-end services, the primary area of focus is between the browser and the Webserver, as shown in Figure 1 on page 3.

3 STI Player with Quality of Service

If the Quality of Service application is installed on the Web server, or on a proxyserver that communicates with the Web server, the STI Player can provide servicetime measurements (overall and for each request) in addition to the round-trip timemeasurements.

Note: The definitions of round-trip time and service time for a request are the sameas those listed previously. (See “Quality of Service” on page 1.) However, thetechnique for measuring round-trip times (but not service times) differsbetween the two applications. Therefore, the round-trip time for a request asmeasured in a Quality of Service job might differ slightly from theround-trip time as measured in an STI playback job for the same request.

4 STI Player with ARM data collection in IBM WebSphere Application Server,Version 5.0

The Application Response Measurement (ARM) API is a set of interfaces that facilitatethe collection of application and transaction performance data, especially forapplications distributed across a network. The ARM API is published as aTechnical Standard by The Open Group, a vendor-neutral organization thatsupports the development of industry standards to facilitate the interoperability ofinformation systems.

IBM WebSphere Application Server Version 5.0 works with Version 2.0 of the ARMAPI to collect information about the performance of applications that reside onWebSphere servers. An STI playback job can retrieve the performance data (ARMdata) collected by WebSphere for individual requests in the job that involve anapplication on a WebSphere 5.0 server. (For example, a request to display accountinformation might involve a banking application on the WebSphere server.) TheARM data can provide a detailed breakdown of back-end service times as well asrelated performance data (for example, the number of records processed in arequest).

The ability to retrieve WebSphere ARM data during STI playback jobs depends ona system configuration that includes the Enterprise Transaction Performancecomponent of IBM Tivoli Monitoring for Transaction Performance. See “CollectingARM data from IBM WebSphere” on page 16 for detailed information about howWeb Transaction Performance, Enterprise Transaction Performance, and WebSpherework together to enable the collection of ARM data in STI playback jobs.

Installable componentsThe Web Transaction Performance system for monitoring the performance andavailability of Web services consists of a set of installable product components.Except for the STI Recorder, the applications described in the preceding sectionsare not installable by themselves, but are included as part of this componentsystem. Figure 2 on page 5 depicts the installable Web Transaction Performancecomponents and their relationship to the applications.


The installable Web Transaction Performance components are as follows:v The Internet Management Server

The Internet Management Server (also called the management server) provides theservices and user interface needed for centralized management. You can accessthe user interface provided by the management server—called the TivoliMonitoring for Transaction Performance user interface—through a Web browser.From the Tivoli Monitoring for Transaction Performance user interface, you canschedule jobs, define event thresholds and responses, view real-time data, andperform other management tasks.

v The Internet Management EndpointsInternet Management Endpoints (also called endpoints) are installed on machinesacross the Web services environment. There are different types of InternetManagement Endpoints. When you install a particular type of endpoint, one ormore applications associated with that type is also installed.All of the Internet Management Endpoints poll the Internet Management Serverat a configurable interval (60 seconds is the default) for scheduled jobs.Applications associated with the endpoints run the jobs at the scheduled times.The one-way arrows in Figure 2 indicate that the endpoints initiate the processof obtaining jobs to run by polling the management server. The managementserver does not request that an endpoint run a job. The arrows also indicate thatany events generated during a job are sent to the management server.

v The STI RecorderUnlike the other applications, the STI Recorder is not installed as part of anInternet Management Endpoint. You cannot schedule jobs on the STI Recorder.

v Tivoli Decision Support for Web Transaction PerformanceTivoli Decision Support for Web Transaction Performance (also called the WebTransaction Performance discovery guide) is software that analyzes data

STIRecorder

applicationapplication

application

application

TivoliDecision Support

forWeb Transaction

Performance

InternetManagement

Server

Internet Management Endpoints

Figure 2. Installable Web Transaction Performance components


collected over a period of time (called historical data) by the Web TransactionPerformance applications, and presents the data in the form of tables or graphs(historical reports).

The following sections describe the installable components in more detail.

Internet Management ServerThe Internet Management Server is shared by all IBM Tivoli Monitoring forTransaction Performance applications. It is the control center of a IBM TivoliMonitoring for Transaction Performance installation. It collects information fromthe endpoints in the installation and provides services to those endpoints. TheInternet Management Server and the endpoints registered to it together comprisethe IBM Tivoli Monitoring for Transaction Performance administrative domain.

The Internet Management Server installation provides the following functions:v The management server software, including the IBM HTTP Server, Version 1.3.19

(a Web server powered by Apache)v The management repository, a set of database tables used by the management

server to store job information, events, and other information.v Core services including job scheduling, the event subsystem, and security

(authorization and authentication).v The Tivoli Monitoring for Transaction Performance user interface (referred to in

this book as the Web Transaction Performance user interface or GUI) for domainadministration. Users access the user interface by entering the Web address ofthe Internet Management Server from a browser and logging on.

Note on naming: IBM Tivoli Monitoring for Transaction Performance is the titledisplayed on two separate graphical user interfaces, one provided with the WebTransaction Performance component and the other provided with the EnterpriseTransaction Performance component. For clarity, this book uses the terms WebTransaction Performance user interface (or GUI) and Enterprise Transaction Performanceuser interface (or GUI). Both user interfaces are accessible from a browser. TheEnterprise Transaction Performance user interface is provided by the EnterpriseTransaction Performance server.

Internet Management EndpointsThere are three types of Internet Management Endpoint, each identified by aspecific name:v Quality of Servicev Web Services Investigatorv Web Services Courier

You can install one Internet Management Endpoint per machine. To install anendpoint means to install a software package that includes the endpoint softwareand one or more applications associated with the endpoint type. Figure 3 on page 7shows the software associated with each endpoint type and, for the Web ServicesCourier endpoint, optional features that you can enable during installation.


Following is a description of the software and features provided with each type ofendpoint.v The Quality of Service endpoint includes the following software:

– The Quality of Service application– The Quality of Service proxy server. The Quality of Service proxy server is an

IBM HTTP Server (Version 1.3.19) that acts as a proxy for the Web server tobe monitored. The server to be monitored is called the origin server.

v The Web Services Investigator endpoint includes the following software:– The Site Investigator application– The STI Player– The Page Analyzer Viewer engine. The Page Analyzer Viewer engine (also

called Web Detailer) collects data on behalf of the STI Player when the PageAnalyzer Viewer feature is enabled.

Note that the STI Player and the Page Analyzer Viewer engine are included onWindows systems only. If you install a Web Services Investigator Endpoint on aUNIX-based system, only the Site Investigator application is included.

v The Web Services Courier endpoint includes the following software and features:– (optional) The Tivoli Enterprise Console (TEC) event-forwarding feature. You

can optionally enable this feature during installation. If the Tivoli EnterpriseConsole event-forwarding feature is enabled, a Web Transaction Performanceadministrator can arrange for events of specified types to be automaticallyforwarded to the IBM Tivoli Enterprise Console. Events are forwarded to theTivoli Enterprise Console through the Web Services Courier endpoint.

– (optional) The Web Services Courier data warehouse feature. You canoptionally enable this feature during installation. The Web Services Courierdata warehouse is space in a database management system (such as Oracletablespace or a DB2 database instance) that stores data generated by WebTransaction Performance applications. The data is used for creating historicalreports. The data warehouse can exist on the Web Services Courier endpointor on another machine within the enterprise.. The database tables areinitialized during installation of the Web Services Courier endpoint.

Quality of ServiceEndpoint

Web ServicesInvestigator

Endpoint

Web ServicesCourier

Endpoint

Quality of Service

Quality of Serviceproxy server

TEC eventforwarding(optional)

Historical datacollection

Web Services CourierData Warehouse(optional)

STI Player(Windows systemsonly)

Page AnalyzerViewer engine(Windows systemsonly)

Site Investigator

Figure 3. Internet Management Endpoint types


Data in the Web Services Courier data warehouse can be transferred atregular intervals to the Tivoli Enterprise Data Warehouse. See “Integrationwith enterprise products” on page 10 for more information.

– Historical data collection software. The historical data collection software onthe Web Services Courier endpoint moves data generated by Web TransactionPerformance jobs from its initial storage location to the Web Services Courierdata warehouse.

Note: Although Tivoli Enterprise Console event-forwarding and the WebServices Courier data warehouse are both optional, you must enable atleast one of these features when installing a Web Services Courierendpoint.

The STI RecorderThe STI Recorder is normally installed on a separate machine from any endpoint, asindicated by the box at the bottom of Figure 3 on page 7. Like the STI Player, theSTI Recorder is installed on Windows systems only. After you record a Webtransaction using the STI Recorder, you can upload the transaction document tothe management server. The management server sends the recorded transaction toWeb Services Investigator endpoints that are scheduled to run STI playback jobs.

Tivoli Decision Support for Web Transaction PerformanceTivoli Decision Support is software that analyzes and consolidates historical datacollected by other Tivoli or IBM products and produces reports in the form oftables and graphs. The base product works in conjunction with add-on softwaremodules, called discovery guides, which produce reports for specific products. IBMTivoli Monitoring for Transaction Performance provides the following discoveryguide (included on the IBM Tivoli Monitoring for Transaction Performance, Version5.1.0: Web Transaction Performance Component Software CD):v Tivoli Decision Support for Web Transaction Performance (also called the Web

Transaction Performance discovery guide)

This discovery guide produces reports from data collected by the Web TransactionPerformance applications—Quality of Service, Site Investigator, and SyntheticTransaction Investigator. Some reports correlate data collected by Quality of Servicewith data collected by WebSphere Site Analyzer. You can prepare and view thereports through the user interfaces provided by Tivoli Decision Support.

Managing the Web services environmentThis section describes how the Web Transaction Performance administrator andsystem collaborate to achieve the principal functions of centralized management.The administrator monitors the performance and availability of the Web servicesenvironment by scheduling application jobs on endpoint machines, defining eventthresholds, setting up automatic responses to events, viewing real-time andhistorical data, and performing related tasks. The components of the WebTransaction Performance system run the requested jobs, handle events, and collect,analyze, and store data.

Creating and scheduling jobsOne of the principal tasks you can perform from the Tivoli Monitoring forTransaction Performance user interface is to create and schedule jobs. Jobs are run


by applications on endpoints at the scheduled times. When you create a job, youspecify the endpoint to run the job. You specify an endpoint by name. Names areassigned to endpoints during installation.

Example: The name of one of the products featured on your Web site has changed.To verify that the old product name no longer appears on any Web page, youcreate and schedule a Site Investigator job. When creating the job, you specify thename of the particular Web Services Investigator endpoint where the job will run.At the scheduled time, the job is performed by the Site Investigator application onthat endpoint. Because the time of the job does not affect the information you arecollecting, you can schedule the job to run at any time.

Handling eventsAn event is a warning, error, or status message generated either by themanagement server (a system event) or by an application (an application event).System events are typically generated by authentication problems, event handlingfailures, or endpoint communication problems. An application generates an eventwhen a specified constraint is exceeded or violated during job execution.

Example: One of the metrics collected by the Quality of Service application is theback-end service time. This is the time that it takes for a Web server to getinformation requested by an end-user. When creating a job to run on a Quality ofService endpoint, you specify a constraint of three seconds for the back-end servicetime. An event is generated whenever the back-end service time exceeds threeseconds during the time that the job is running.

Endpoints send application events to the management server. The managementserver logs all application and system events to event logs, which reside in themanagement repository. You can view the event logs through the Tivoli Monitoringfor Transaction Performance user interface.

The action of logging an event is an example of an event response. You canconfigure one or more additional responses to specific event types. The responsesare carried out by the event subsystem on the management server. The additionalevent responses include any of the following actions:v Notify an individual or group by e-mail that the event has occurredv Send the event to a Simple Network Management Protocol (SNMP) application

such as Tivoli NetViewv Forward the event to the IBM Tivoli Enterprise Consolev Launch a program or script.

You can choose to forward selected event types to the IBM Tivoli EnterpriseConsole only if the Tivoli Enterprise Console event forwarding feature is enabledduring installation of the Web Services Courier endpoint.

Collecting historical dataAs scheduled jobs are running, data is collected and stored. At scheduled intervals,in a process known as historical data collection, the data is moved from its initialstorage location and processed into a format useful for generating reports. Thedetails of this process are summarized in Figure 4 on page 10.


Data collected by Web Transaction Performance jobs (that is, jobs executed byQuality of Service, Site Investigator, and the STI Player) is initially stored in logfiles on the management server A . At a scheduled time, once each day, historicaldata collection software on the Web Services Courier endpoint B moves this data

to the Web Services Courier data warehouse C —first to the staging side and thento the production side. During the transfer from staging to production, someformatting takes place to prepare the data for viewing.

Tivoli Decision Support software D retrieves the data from the data warehouse.You can view reports for any time period you choose from the user interface

provided by Tivoli Decision Support E .

Viewing resultsThe preceding section described one way to view the collected data from WebTransaction Performance jobs: historical reports. In addition, you can viewreal-time reports for Quality of Service and the STI Player. Real-time reportsdisplay the data in graphic form as it is being collected, that is, as the job isrunning. For Site Investigator, you can view the results just after the job iscompleted. Real-time reports and Site Investigator reports are available through theTivoli Monitoring for Transaction Performance user interface.

To view and work with event logs, you can use the Tivoli Monitoring forTransaction Performance user interface or you can use enterprise products such asIBM Tivoli NetView or the IBM Tivoli Enterprise Console.

Integration with enterprise productsThis chapter has referred to several IBM and Tivoli enterprise software productsthat can optionally be used in conjunction with Web Transaction Performance toprovide more advanced capabilities. This section provides a summary. Forinformation about publications for each of these products, see “Prerequisitepublications” on page xiii.

Web Services Courierdata warehouse

CE

D

BA

TivoliDecisionSupport

Sta

gin

g

Pro

du

ctio

n

historicaldata collection

Web ServicesCourier Endpoint

log files

Tivoli Decision SupportGUI

Internet ManagementServer

Figure 4. Historical data collection


IBM Tivoli Enterprise ConsoleIBM Tivoli Enterprise Console is a rules-based event management application thatacts as a central collection point for alarms and events from across the computingenterprise, such as a database server that is not responding, a lost networkconnection, or a successfully completed batch processing job. It enables you toprioritize, filter, and correlate events, determine who should handle specific events,and initiate automatic corrective actions when appropriate. By providing a meansto organize and respond to a high volume of events, Tivoli Enterprise Consoleensures the high availability of application and computing resources.

When you install a Web Services Courier endpoint, you can enable the forwardingof events generated by Web Transaction Performance applications to the TivoliEnterprise Console. You can enable forwarding of events either through a Tivolienvironment, which enables you to take advantage of multiple Tivoli EnterpriseConsole servers, or directly to a specific Tivoli Enterprise Console server..

Tivoli Enterprise Data WarehouseThe Tivoli Enterprise Data Warehouse is a central data store where historical datafrom management applications can be aggregated and correlated for use byreporting and third-party online analytical processing (OLAP) tools as well asplanning, trending, analysis, accounting, and data mining tools. The TivoliEnterprise Data Warehouse also provides a report interface that can be used togenerate simple Web-based historical reports.

Tivoli management applications support the Tivoli Enterprise Data Warehouse byproviding a separately installable software module called a warehouse enablementpack or warehouse pack. The warehouse packs are installed with Tivoli EnterpriseData Warehouse. The warehouse pack provides extract, transform, and load (ETL)utilities that gather the data from the source applications and disperse it intospecific data marts that serve as customized sources of data for reporting and othertools. Specifically, there are two ETL types:v The central data warehouse ETL reads the data from the data store used by the

application (for example, the Web Services Courier data warehouse), verifies thedata, makes the data conform to the Tivoli Enterprise Data Warehouse schema,and copies the modified data to the central data warehouse. The central datawarehouse is the common receiving area of the Tivoli Enterprise DataWarehouse.

v The data mart ETL extracts data from the central data warehouse, transforms it,and loads it into one or more star schemas. The star schemas can then beincluded in data marts.

IBM Tivoli Monitoring for Transaction Performance provides two warehouse packs,one for the Web Transaction Performance component and one for the EnterpriseTransaction Performance component. For this release, each of these warehousepacks provides a central data warehouse ETL only. For Web TransactionPerformance, the central data warehouse ETL transfers data at regular intervalsfrom the Web Services Courier data warehouse to the Tivoli Enterprise DataWarehouse.

Tivoli Decision SupportTivoli Decision Support is the base software on which the Web TransactionPerformance discovery guide is installed. You must install Tivoli Decision Supportin order to create and view historical reports from data collected by the WebTransaction Performance applications.


IBM WebSphere Site AnalyzerIBM WebSphere Site Analyzer provides tools that analyze and report Web siteactivity and content. Some of the reports generated by Tivoli Decision Support forWeb Transaction Performance correlate data collected by Quality of Service withdata collected by WebSphere Site Analyzer.

IBM WebSphere Application ServerThe IBM WebSphere Application Server facilitates the integration of core enterprisesystems with the Internet by providing a deployment environment for Javaapplications that use enterprise data to generate dynamic content for Web pages.The STI Player can be enabled to retrieve ARM measurement data collected byIBM WebSphere 5.0 servers. For detailed information, see the following sections ofthis chapter:v “STI Player capabilities” on page 2v “Collecting ARM data from IBM WebSphere” on page 16

System configuration exampleThis section describes the IBM Tivoli Monitoring for Transaction Performanceinstallable components in terms of where they are located in the Web servicesenvironment and how they communicate.

Figure 5 on page 13 illustrates a sample Web services environment as it mightappear before any Web Transaction Performance components are installed.


The Web services environment shown in the diagram is divided into three zonesseparated by firewalls—the Internet, the DMZ, and the enterprise or intranet.v Internet users communicate through a firewall to Web servers located in the

DMZ. The firewall establishes a security perimeter for services that interfacewith the Internet.

v The DMZ (Demilitarized Zone) is a screened network between the enterprise(intranet) and the Internet. The double firewall architecture provides an extralayer of protection for sensitive data located inside the enterprise.Communication between Web servers in the DMZ and machines inside theenterprise takes place only under strictly controlled conditions.In the diagram, Web servers in the DMZ communicate across a firewall to a Webapplication server inside the enterprise. Web application servers typicallyconnect to legacy applications that store and manage enterprise data. Webapplication servers can also reside in the DMZ, typically on the same machinesthat host Web servers.

v In addition to the Web application server, the Enterprise portion of the diagramincludes a machine with a Tivoli management agent installed. The Tivolimanagement agent is part of a Tivoli Enterprise installation.

ToTivoli

EnterpriseConsole

WebServer

WebApplication

Server

WebServer

LoadBalancer

InternetUsers

Internet DMZ Enterprise/Intranet

Fire

Wal

l

Fire

Wal

l

Fire

Wal

l

Fire

Wal

l

TivoliManagement

Agent

Figure 5. Sample Web services environment before Web Transaction Performancecomponents are installed


Figure 6 superimposes a sample IBM Tivoli Monitoring for TransactionPerformance installation on the network configuration of the preceding diagram.

In the following discussion, numbered product components correspond to thenumbers on the diagram. In some cases, the same number might appear onmultiple objects in the diagram.

1 Internet Management Server

The Internet Management Server is typically set up in the DMZ. From thislocation, it is accessible to all registered endpoints in the DMZ, on the internet, orwithin an enterprise’s intranet. There is one Internet Management Server in a WebTransaction Performance installation.

The underlying relational database management system (RDBMS) for themanagement repository can be installed on the same machine as the managementserver or on a separate database server machine within the DMZ.

Communications between the Internet Management Server and its registeredendpoints can be either secure (HTTPS) or non-secure (HTTP). Web TransactionPerformance uses the Secure Sockets Layer (SSL) security protocol to enable secure

ToTivoli

EnterpriseConsole

DataWarehouse

ManagementRepository

InternetManagement

Server

WebServices

Investigator

Qualityof

Service

Qualityof

Service

WebServer

WebApplication

Server

WebServer

LoadBalancer

InternetUsers


Fire

Wal

l

Fire

Wal

l

Fire

Wal

l

Fire

Wal

l

TivoliManagement

Agent

TivoliDecisionSupport

WebServicesCourier

Endpoint

STIRecorder

2

1

5

23

3

4

Figure 6. Sample Web services environment with Web Transaction Performance componentsinstalled


communications. You specify the type of communication you want duringinstallation of the management server and endpoints. All endpoints registered tothe management server must communicate with the same protocol.

2 Quality of Service endpoints

Quality of Service endpoints must be installed in the DMZ. A Quality of Serviceendpoint includes an IBM HTTP server that is used as a proxy server (sometimescalled a reverse proxy) for a target Web server. The target Web server, also calledthe origin server, is the server to be monitored by the Quality of Service endpoint.Each Quality of Service endpoint monitors just one Web server. A monitored Webserver is usually located in the DMZ, but it can also be located on the Internet.

In the diagram, the Quality of Service endpoints are installed on the target Webserver machines. The endpoints could also be installed on separate machines. Thekey requirement is that the endpoint be able to act as a proxy for incomingrequests to the target Web server. By intercepting incoming requests and outgoingreplies, the Quality of Service application is able to get the information it needs tocalculate response times.

The load balancer in this example allocates incoming requests to the two Webservers, duplicate servers that serve a single Web site. The Web servers in thisexample should run on a non-standard port, such as port 81. This enables you toassign the Quality of Service proxy server and load balancer to the standard ports(80 for non-SSL or 443 for SSL) in order to handle communication through thefirewall.

3 STI Recorder and Web Services Investigator endpoints

The STI Recorder is a stand-alone application that can be installed on any machinewith access to the management server. The diagram shows an STI Recorderinstalled on a machine in the enterprise. The user at this machine can record abrowser session, upload the recorded data to the management server, and thenschedule playback jobs to be run on one or more Web Services Investigatorendpoints, located on the Internet. The user can view the playback results in areal-time or historical report. The following scenario describes the data flow andcomponents involved in these activities.1. The user records a transaction from a browser and uploads the recorded

transaction document to the management server from the user interfaceprovided with the STI Recorder. The user can record a session on any Web site,but for this scenario, assume that the Web site is the one served by the Webservers in the diagram—that is, the company’s own Web site.

2. The user schedules playback jobs on one or more Web Services Investigatorendpoints using the Tivoli Monitoring for Transaction Performance userinterface.

3. Web Services Investigator endpoints on the Internet (only one is shown in thediagram) poll the management server for playback and other jobs. Whenpolled, the management server downloads the recorded transaction documentto the Web Services Investigator endpoints that the user specified whencreating the playback jobs.

4. At the scheduled times, the STI Player applications on the Web ServicesInvestigator endpoints replay the transaction, accessing the Web site throughthe load balancer as shown in Figure 6 on page 14.


5. When the playback is finished, the Web Services Investigator endpoint uploadsthe collected data to the management server, where it is stored in log files onthe server.

4 Web Services Courier endpoint

Figure 6 on page 14 shows part of the setup required to forward events to the IBMTivoli Enterprise Console through a Tivoli environment. To enable eventforwarding through a Tivoli environment, the Web Services Courier endpoint mustbe installed on a machine within the enterprise where a Tivoli management agentis already installed.

The Web Services Courier endpoint polls the management server at a configurableinterval (60 seconds is the default) for any events cached during the interval by themanagement server. The management server caches all events generated within thedomain that are re-configured as Tivoli Enterprise Console events. (These areevents that fall into an event category (event type) for which the administrator hasconfigured an event response of forwarding to the Tivoli Enterprise Console.) Thisincludes events generated by the Internet Management Endpoints and by themanagement server itself. When polled, the management server sends the cachedevents to the Web Services Courier endpoint. The Tivoli management agent on theendpoint machine forwards the event through a Tivoli management gateway to theTivoli Enterprise Console.

5 Tivoli Decision Support for Web Transaction Performance

Tivoli Decision Support for Web Transaction Performance (also called the WebTransaction Performance discovery guide) is installed on the machine of a TivoliDecision Support administrator. This machine is located in the enterprise where ithas access to the Web Services Courier data warehouse, the source of data used toprepare historical reports.

To enable access to the Web Services Courier data warehouse, you must install adatabase client on the Tivoli Decision Support administrator’s machine andconfigure an ODBC connection to the data warehouse.

Collecting ARM data from IBM WebSphereWhen you install the Internet Management Server, you can optionally enable theSynthetic Transaction Investigator application to retrieve performance data fromARM-instrumented IBM WebSphere 5.0 application servers. If the SyntheticTransaction Investigator application is enabled, the Web Transaction Performanceadministrator can specify which requests in an STI playback job should trigger thecollection of ARM performance data. The actual collection of the data is done bythe Enterprise Transaction Performance component of IBM Tivoli Monitoring forTransaction Performance. Marking an STI playback request for ARM data retrievaldoes not guarantee that any ARM data will be collected. Whether or not data iscollected for a particular request also depends on how WebSphere is configured.

This section describes how Web Transaction Performance uses IBM WebSphere andthe Enterprise Transaction Performance infrastructure to collect and display ARMperformance data for selected requests in STI playback jobs. The following topicsare discussed in the order listed, reflecting the hierarchy of dependencies:v Basic concepts of the ARM APIv How WebSphere uses the ARM API


v How Enterprise Transaction Performance collects WebSphere ARM datav How Web Transaction Performance depends on Enterprise Transaction

Performance to collect and report WebSphere ARM data

Note on terminology: In this section, the term transaction is used in the followingways:v To refer to an overall business transaction on the Web, such as viewing an

account balance.v To refer to each of the individual requests for service involved in carrying out

the overall transaction. The performance of a business transaction generallyinvolves a hierarchical chain of service requests. For example, to display anaccount balance, the client browser makes a request to a Web server, which inturn might send a request to a business application on a WebSphere applicationserver. Within the business application, a Java Server page (JSP) might requestinformation from a servlet. Because of the hierarchial relationship, each requestor transaction is usually both a parent transaction and a sub-transaction.

v To refer to a banking transaction, that is, a deposit or withdrawal.

ARM conceptsThe Application Response Measurement (ARM) API was developed to meet thechallenge of tracking performance through complex, distributed computingnetworks. The ARM API provides a way for business applications to passinformation about the sub-transactions they initiate in response to service requeststhat flow across a network. Application management software can use thisinformation to calculate response times, identify sub-transactions, and provideadditional data to help an administrator determine the cause of performanceproblems.

To use ARM, a developer instruments an application with calls to the ARM API.The most important ARM API calls are start and stop calls, placed just before atransaction starts and just after a transaction ends. A measurement agent, called anARM agent, clocks the ARM start and stop calls in order to calculate transactiontimes. In general, the role of the ARM agent is to capture the data from the ARMcalls, process the data, and make the results available to higher-level managementapplications.

An important capability of the ARM API, and the ARM agent, is the tracking ofhierarchical relationships among transactions, a process known as correlation. Theability to associate (correlate) transactions with their nested sub-transactionsdepends on the passing of a trace object, called a correlator, on ARM start calls.Knowledge of the parent-child relationships among transactions and the responsetimes for each transaction enables an administrator to determine whichtransactions are delaying other transactions. The administrator can then take stepsto improve the response times of services or transactions that contribute the mostto slow performance.

ARM support in IBM WebSphereVersion 5.0 of IBM WebSphere Application Server provides ARM support forenterprise or business applications that reside on WebSphere servers. IBMWebSphere servers host business applications that interact with core IT systemsand generate content for dynamic Web pages. The ability to perform theseoperations quickly is critical to the quality of service experienced by end users. The


use of ARM to monitor transaction performance in this environment is animportant aid to diagnosing and correcting the causes of bottlenecks andslowdowns.

It is not necessary for a programmer to instrument the applications that reside onthe WebSphere server with ARM function calls. Instead, a WebSphere administratorconfigures WebSphere to make ARM calls on behalf of the applications. This ispossible because each application is composed of discrete components—Java serverpages (JSP), servlets, and Enterprise JavaBeans (EJB)—that can be wrapped withARM start and stop calls. Each instance of a JSP, servlet, or EJB, when executing,can be considered a transaction and therefore a candidate for ARM measurement.The administrator need only identify to WebSphere which JSPs, servlets, or EJBs tomonitor with ARM.

Figure 7 on page 19 is a close-up view of how a home banking service residing ona WebSphere server might satisfy a user request for recent account history. TheAccount Detail JSP at left represents the parent transaction, driving thesub-transactions carried out by the servlets and EJBs. The right arrows representremote calls. The left arrows represent returns.

For example, the Account Detail JSP calls a Balance servlet to get the currentbalance in the account. The servlet calls EJBs to get the available balance and theledger balance. The EJBs retrieve the data from a database and return it to theBalance servlet. The Balance servlet processes and returns the results to theAccount Detail JSP.


Figure 7 shows that the WebSphere administrator has configured WebSphere tomake ARM start and stop calls for the transactions involved in satisfying therequest for account details. For example, WebSphere makes an arm_start( ) calljust before the Balance servlet is invoked and an arm_stop( ) call after it isfinished running. Sample response times are shown (in seconds) for alltransactions.

Collecting WebSphere ARM data in Enterprise TransactionPerformance

The Enterprise Transaction Performance component of Tivoli Monitoring forTransaction Performance, Version 5.1, can collect ARM data generated byapplications on WebSphere servers that have IBM WebSphere Application Server,Version 5.0 installed. The Enterprise Transaction Performance component collectsARM data independently of the STI Player. However, as shown later, the STIPlayer can trigger the collection of ARM data by Enterprise TransactionPerformance on its behalf. This section describes the collection of ARM data as afeature of Enterprise Transaction Performance, independent of the STI Player.

To enable this feature, a WebSphere administrator must configure WebSphere toaccept a plug-in ARM agent provided by Enterprise Transaction Performance. The

AccountDetailJSP

BalanceServlet

RecentTransactions

Servlet

ATMTransactions

Servlet

AvailableBalance

EJBDB2

Server

DB2Server

CreditCard

Service

ATMServer

LedgerBalance

EJB

Get and SortTransactions

EJB

DatabaseQueryEJB

arm_start ( ) arm_start ( ) arm_start ( )

arm_start ( )

arm_start ( )

arm_start ( )

arm_start ( )

arm_start ( )

arm_stop ( )

arm_stop ( )

arm_stop ( )

arm_stop ( )

arm_stop ( )

arm_stop ( )

arm_stop ( )

(15 seconds) (3 seconds)

(8 seconds)

(3 seconds)

(1 second)

(1.5 seconds)

(6 seconds)

(2.5 seconds)

arm_stop ( )

Figure 7. ARM data collection in IBM WebSphere


ARM agent records and processes the ARM data and uploads it to a database atregular intervals as scheduled by the Enterprise Transaction Performanceadministrator. The administrator can access the data by accessing the EnterpriseTransaction Performance user interface from a browser. The Enterprise TransactionPerformance user interface is provided by the Enterprise Transaction Performanceserver.

Figure 8 shows the relationship of the IBM WebSphere server to the EnterpriseTransaction Performance ARM Agent and the Enterprise Transaction Performanceserver. Note that the WebSphere server must also be a Tivoli managed endpoint.

Figure 8 includes a higher-level view of the home banking application discussedpreviously, showing some examples of transactions at the JSP level that might beconfigured for ARM data collection. The Enterprise Transaction Performanceadministrator cannot specify that the Enterprise Transaction Performancecomponent retrieve ARM data for some transactions and not others. EnterpriseTransaction Performance uploads all the ARM data from all the transactions withinan application that have been configured in WebSphere. However, theadministrator can turn data collection on or off at the application level.

securityserver

databaseserver

databaseserver

Tivolienvironment

Enterprise TransactionPerformance

Server

Enterprise TransactionPerformanceArm Agent

arm_start ( )

arm_start ( )

arm_start ( )

arm_stop ( )

arm_stop ( )

arm_stop ( )

LoginJSP

AccountSummary

JSP

AccountDetailJSP

OtherApplications

Home Banking Application

IBM WebSphereApplication Server

Version 5.0

Tivoli managed endpoint

Figure 8. Collection of WebSphere ARM data by Enterprise Transaction Performance


Collecting WebSphere ARM data in Web TransactionPerformance

You can use the STI Recorder to record a Web transaction (such as viewing anaccount or making a purchase) that includes requests to applications running on aWebSphere server. When setting up the corresponding STI Player job, you canenable the collection of ARM data for some or all of those requests(sub-transactions). When you run the playback job, the Enterprise TransactionPerformance ARM agent on the WebSphere server collects the ARM data for thesub-transactions that you specified when setting up the job. You can view theresults through a link to the Enterprise Transaction Performance server.

You can collect ARM data for specific requests in an STI Player job if the followingconditions are met:v IBM WebSphere Application Server Version 5.0 must be installed and configured

to use the Enterprise Transaction Performance ARM agent.v When you set up the STI playback job, you must mark the requests for which

you want ARM data collected. (There is a check box.)v The requests that you mark for ARM data collection must be requests to

applications on the WebSphere server.v The requests that you specify must already be configured in WebSphere for

ARM data collection.v You must specify the URL of the Enterprise Transaction Performance server

during installation of the Web Services Investigator endpoint from which the STIPlayer job runs.

As an example, you might use the STI Recorder to record a Web transaction thatincludes the three requests shown in Figure 8 on page 20: log in, view accountsummary, view account detail. All three transactions use arm_start( ) andarm_stop( ) calls in WebSphere, so ARM data collection is possible. When settingup the STI Player job, you might mark only the Account Detail transaction forARM data collection. When you run the STI Player job, the ARM agent measuresthat transaction and all of its instrumented sub-transactions, such as the AvailableBalance and Ledger Balance transactions shown in Figure 7 on page 19. Whenviewing the results of the STI Player job, you can view the collected ARM data forall sub-transactions through a link to the Enterprise Transaction Performanceserver. If you run the STI Player job from multiple Web Services Investigatorendpoints at various locations, you can see the results from all locations in a singleview.

An application hosted by WebSphere might be implemented as a distributedapplication across several Web application servers. In this case, performance data isnot available for sub-transactions that are processed on remote hosts beyond theinitial WebSphere server. For example, if the Available Balance EJB and LedgerBalance EJB shown in Figure 7 on page 19 are processed on a separate server, theindividual results (1 second and 1.5 seconds) are not presented for viewing. Only asingle round-trip measurement is shown for the parent transaction, the BalanceServlet.

The underlying mechanism that triggers ARM data collection for an STI Player jobis the passing of an ARM correlator in the HTTP header for each request(sub-transaction) that you marked when you created the job. WebSphere isdesigned to accept external correlators such as this one that are passed onincoming requests. For purposes of ARM correlation, each request that is marked


when you create the STI Player job becomes the parent transaction to thedownstream JSPs, servlets, and EJBs in its path.

Figure 9 on page 23 shows the components involved in collecting and viewingARM data for an STI Player job. The following steps describe the details of thisprocess.

1. From the user interface provided with the STI Recorder, the user A records abrowser session with the bank’s Web site, which is served by the Web server B

shown in the DMZ area of the diagram. During the recording session, the usersigns in to the bank’s online services, links to a menu of services, views theaccount balance, and views recent account history.

2. The user connects to the Internet Management Server C from a browser. Thisaction displays the IBM Tivoli Monitoring for Transaction Performance userinterface for the Web Transaction Performance component. After logging on, theuser creates and schedules a playback job for the business transaction recorded

previously, selecting one or more Web Services Investigator endpoints D fromwhich to run the job. The user also selects the ARM correlation checkbox forone or more of the HTTP requests listed for the job, such as the request to viewaccount history. Only dynamic data requests should be selected for ARMcorrelation.

3. The STI Player on each selected Web Services Investigator endpoint D runs theplayback job at the scheduled time. An ARM correlator is included in theheader of each HTTP request that the user selected for ARM correlation. Whenthe bank’s Web server B receives each request, it forwards the ARM correlator

to the WebSphere server E .4. When the playback job is finished, the Web Services Investigator endpoint

uploads the collected data to the Internet Management Server C . This is datacollected by the STI Player only, such as the total time it takes to successfullysign in to the bank’s online services. It does not include the back-end servicetimes (ARM measurements) collected by WebSphere.

5. The Enterprise Transaction Performance ARM agent on the WebSphere servercollects ARM data for the requests that were selected for ARM correlation. TheARM agent uploads the data to a repository that can be accessed by theEnterprise Transaction Performance server F . The uploading of ARM datatakes place at a scheduled interval configured by the Enterprise TransactionPerformance administrator.

6. The user views the results G collected by the STI Player from the WebTransaction Performance user interface (the user interface provided by theInternet Management Server). From this interface, the user can link directly tothe Enterprise Transaction Performance server to view the collected ARM dataH .

Note that without ARM correlation, the STI playback job can only collect, for eachHTTP transaction, the round-trip time from the Web Services Investigator endpointD and the round-trip time from the Web server B . It can collect the round-triptime from the Web server (that is, the total back-end service time) provided aQuality of Service endpoint is installed on the Web server, as shown in Figure 9 onpage 23, or on a proxy server. ARM correlation extends the capability of the STI

Player by providing a view into the black box between the application server E

and back-end services.


WebSphereTransaction

Details

G

E

InternetManagement

Server

EnterpriseTransactionPerformance

Server

STIPlayer

Web ServicesInvestigator

Endpoint

Web Server

C

ARMagent

WebSphere5.0

Qualityof

Service

WebSphereServer

Back-endSystem

Tivolienvironment


Fire

Wal

l

Fire

Wal

l

Fire

Wal

l

Fire

Wal

l

STI TransactionDetails

Webbrowser

D

A

F

BH

Figure 9. Collecting and viewing WebSphere ARM data in an STI Player job


Chapter 2. GUI Overview and Navigation

The Web Transaction Performance graphical user interface (GUI) is the interfaceyou use to manage your Web Transaction Performance implementation. The GUI isthe main window into the Web Transaction Performance services and applications.

The GUI is Web-based; you can view it through a Netscape Navigator or MicrosoftInternet Explorer browser. As a result, you can manage the management serverand applications from any location, as long as you have HTTP or HTTPS access.

Web Transaction Performance’s management information and applications aredisplayed and accessible from an expandable navigation tree that enables you toaccess and run the applications, view information, and perform systemadministration tasks. The GUI’s design makes it easy to learn and easy to use.There is a common paradigm for accomplishing tasks used throughout the console.After you have learned the steps for accomplishing one task, other tasks are easierto learn and perform.

The GUI is the Web Transaction Performance desktop; it is the user interface onwhich you perform basic system operations. The GUI displays and organizes theresources, jobs, events, and reports of the different Web Transaction Performanceapplications.

Starting the GUIYou can start the GUI from any location, as long as you have HTTP or HTTPSaccess. You can view the GUI through a Netscape Navigator 6.2+ or MicrosoftInternet Explorer 6.0+ browser.

Note: Before accessing an Internet Management Server, be sure to configure yourbrowser to accept cookies, and to enable Javascript. Refer to your browser’shelp system for procedures to enable cookies and Javascript.

To start the Web Transaction Performance GUI, complete the following steps.1. Start a browser.2. Type the URL and port number for the management server in your browser’s

Location or Address bar. Use the following syntax:http(s)://<management server name>.<domain name>:<port>/

Your browser displays the GUI.

25

Areas of the GUIThe GUI is divided into three main parts: the navigation tree, the banner, and thework area.

The left side of the GUI is the navigation tree. The navigation tree contains links toeach of the Web Transaction Performance products and links to general tasks,which are product-independent or administrative activities. When you first log into Web Transaction Performance, the desktop view shows an unexpandednavigation tree.

To expand the tree and view the functions available for a product, select theproduct from the navigation tree. An expandable list of options indicated by arrowicons to the left of a selection is displayed. When you click a selection from theexpanded list in the navigation tree, the contents of the work area change to reflectyour selection.

To expand the tree and view choices pertaining to Web Transaction Performanceapplications or generalized functions, click the name of each application orfunction to expand its menu.

To log off the Internet Management Server, click Log Off, which is located at thetop-right corner of the menu tree.

Help ButtonThe Help button appears as question mark icon in the upper-right corner of thework area. The help system provides overview and context-sensitive information toassist you while you perform Web Transaction Performance tasks or managementactivities. If you click the Help button before opening any of the applications, the


help system displays the table of contents. If you click the Help button while youare in an application or performing administrative tasks, the help system displayscontext-sensitive information.

Work AreaThe work area is where you perform all of the Web Transaction Performance tasks.The activities you perform in the work area include:v creating and scheduling application jobsv configuring events and creating event responsesv examining job and event logsv viewing reports

NavigationWhen you open one of the applications to create or edit a job, the system displaysa set of tabs across the top of the work area. The tabs identify the subtasks thatmake up a job. You can move from one subtask to another by clicking on the tabs.You can use the tabs to go back to review a subtask you have completed. A checkmark (U) appears on a tab when the options for that tab are valid entries forscheduling a job. In addition to navigation using the tabs, application subtaskviews contain a Next button that, when clicked, moves you to the next subtask.

Note: Do not use the browser’s Back function to navigate to a previous tab.

Now that you are familiar with the Web Transaction Performance GUI and itsoperational concepts, you are ready to examine the applications. If you plan toimmediately begin configuring jobs in the applications, you must first configureevents and event responses. For information on how the event system operates, seeChapter 8, “Managing events and event responses” on page 105.

Chapter 2. GUI Overview and Navigation 27

Note: The contents of the navigation tree area vary depending on theauthorization granted to your user ID. In general, only the navigation treetasks for which you have authorization appear in the navigation tree view.Authorization is described in “Managing accounts” on page 95.


Chapter 3. Quality of Service application

This chapter describes the Quality of Service (QoS) application, how to create jobsfor it, and how to view the results of those jobs.Table 1 provides an overview ofthe topics covered in this chapter.

Table 1. Summary of topics covered in this chapter

Goal Refer to

Create a QoS job. “Configuring QoS jobs” on page 30

Select a QoS endpoint for which to create ajob.

“Selecting a QoS endpoint” on page 31

Create a job schedule. “Creating a QoS job schedule” on page 31

Configure parameters for a QoS job. “Configuring parameters for a QoS job” onpage 33

Configure constraints for a QoS job. “Configuring constraints for a QoS job” onpage 35

Name a QoS job. “Naming a QoS job” on page 37

Edit a QoS job. “Editing a QoS job” on page 38

Manage QoS jobs. “Managing QoS jobs” on page 38

Configure events for QoS jobs “Configuring events” on page 40

Examine the QoS event log. “Examining the event log” on page 42

View QoS reports. “Viewing QoS reports” on page 43

Quality of Service provides a means for measuring end-user experience on yourWeb environment. It provides three different metrics and can capture these metricsfor a specific collection of users, a request sample, or all requests made to the Webservers.

QoS enables you to measure the user experience (round-trip) time, back-endservice time, and page display (render) time from HTTP requests directed at yourWeb sites.

Note: QoS cannot measure user experience time, page display time for browsersthat have JavaScript disabled.

v User experience time is the span from the time the user clicks on a link toinitiate a Web transaction until the request is fulfilled.

v Back-end service time is the amount of time it takes a Web server to receive arequest, process it, and respond to it.

v Page display time is the amount of time it takes to render a requested Web pageon the requestor’s browser, from the time the rendering begins until it iscomplete.

QoS does not require you to install any software on client machines. Theapplication employs the QoS endpoint, which you must install on a machine inyour DMZ. The QoS endpoint is made up of the QoS controller and an IBM HTTPserver configured as a reverse proxy. A reverse proxy server provides access tointernal content for external clients through a firewall.

29

At startup, the QoS endpoint invokes the endpoint controller, which commands thereverse proxy to begin capturing transaction data. The QoS application provides arecord for each transaction. The endpoint controller retrieves logged transactionsand periodically uploads data and constraint events to the log file in themanagement repository.

QoS also includes historical and real-time reports that produces the followinggraphs:v User Experience graph, which shows user experience timev Back-end Service graph, which shows service timev Page Display graph, which shows page render time

The real-time reports display averages for each metric that QoS captures over acontinuously moving span of time that you can define when generating the report.Historical reports display averages for each metric that QoS captures over aspecific time range that you specify when generating the report.

Transaction and event data from QoS jobs is uploaded to the Internet ManagementServer. In addition, the data can be downloaded to a data warehouse where it canbe used for reporting and analysis through the Tivoli Decision Support software.

User scenariosYou can use the Quality of Service application in a variety of scenarios, includingthe following:

Scenario 1: Company A wants to monitor its business relationship with a partnerby measuring the Web server’s performance in handling requests from thepartner’s domain. Using QoS, the Web administrator for Company A creates a jobthat runs from 9:00 a.m. to 5:00 p.m. daily and measures the user experience timeof every 50th request from the partner’s gateway IP to the Company A Web serverbeing monitored.

Scenario 2: Company A wants to measure request service time from itse-commerce customers who use one of several ISPs (with addresses 192.168.1.10,192.168.1.11, and 192.168.1.12). Company A’s Web administrator creates a job thatruns continuously and measures every 100th request from each of the specifiedISPs.

Scenario 3: Company A wants to measure page display times during a peakperiod. To achieve this, Company A’s Web administrator creates a QoS job thatmonitors every request from IPs 192.168.1.10, 192.168.1.11, and 192.168.1.12 duringthe peak period. This results in a job that runs from 9:00 a.m. to 12:00 p.m. everyMonday from November 15 through December 15.

Configuring QoS jobsThe following paragraphs explain how to configure Quality of Service jobs. Anoverview of the procedure is presented first, followed by detailed informationabout the configuration components.

To create a QoS job, you complete the following steps:1. From the navigation tree, click Create Quality of Service Job.2. Choose a QoS endpoint or virtual host.


3. Create a schedule for the job.4. Configure the parameters for the job.5. Configure the constraints for the job.6. Save (assign a name) to the job.

Before you begin configuring QoS jobs, especially the first time, you shouldconfigure QoS events and event responses. The QoS event types are discussed laterin this chapter; configuring events and event responses are discussed later in themanual.

Selecting a QoS endpointThe first step in configuring a QoS job is to select the QoS endpoint, or endpoints,from which to run the job. You can also select endpoints by which virtual host theymonitor.

To select a QoS endpoint:1. In the navigation tree, click Create Quality of Service Job.

2. Select if you want to choose endpoints by virtual host or from a list of allinstalled endpoints.To see an example of how to set up QoS to work with virtual hosts, openinstalldir\programfiles\tivoli\internet\managementserver\ibmhttpserver\qos.conf in a texteditor and reference the virtual hosting example.

3. Select the check box next to the name of one or more endpoints for which youwish to create this job, and click Next.

Note: Endpoint choice configurations are not saved until you complete the jobcreation process by naming the job.

If there are no QoS endpoints listed in this view, you must install one. Consult theIBM Tivoli Monitoring for Transaction Performance Web Transaction PerformanceInstallation Guide for more information.

Creating a QoS job scheduleThe scheduling view provides a variety of options for running QoS jobs. Typically,you want to schedule QoS jobs to run continuously.

Figure 10. Choosing a QoS Endpoint

Chapter 3. Quality of Service application 31

You can configure a schedule for a Quality of Service (QoS) job in one of twoways: use an existing schedule or create a new one.

Note: Job schedule configurations are not saved until you complete the jobcreation process by naming the job.

To use an existing schedule:1. Click Create Quality of Service Job.2. Click the Schedule tab.3. In the Schedule view, click the down arrow to the right of the Existing

configurations drop-down list.

4. Select a schedule from the list. Click Populate to view the values for theschedule you have selected.

5. Click Next to use this schedule for the job that you are configuring.

Configuring a new schedule:1. Click Create Quality of Service Job.2. Click the Schedule tab.3. Determine whether you want the job to start as soon as possible or at a later

date or time.

v To start the job immediately, select Start the job as soon as possible.—or—v To start the job at a later date or time, select Start the job later at and specify

the time and date for the job to start using the choices you made in thedrop-down boxes.

4. Choose how often you want to run this job.v Click Run the job only once to run the job once.—or—

Figure 11. Using an existing schedule when creating a job

Figure 12. Choosing a start time for a new job schedule


v Click Run the job and use the drop-down lists to specify the start time, endtime, and days of the week during for which you want the job to runcontinuously:a. To run the job between selected hours, select a Start time and End time

using the drop down boxes.b. Select one or more days of the week on which the job will run.

5. Decide whether this job should terminate, and if so, when.

v Select Never terminate this job if you want the job to run without everterminating.

v If you want the job to stop at a certain time on a specific date, clickTerminate job at and specify the stop time and stop date using thecorresponding drop-down boxes.

6. Click Next. If you need to begin again without saving the values you haveentered, click Clear.

Configuring parameters for a QoS jobIn QoS, the parameters enable you to throttle and filter requests. You can configurethe parameter set for a QoS job in one of two ways: use an existing parameter setor create a new one.

Note: Parameter configurations are not saved until you complete the job creationprocess by naming the job.

To use an existing parameter set:1. Click Create Quality of Service Job.2. Click the Parameters tab.3. In the Configure Quality of Service Parameters view, click the arrow to the

right of the Existing configurations drop-down list.

4. Select the parameter set you want to use and click Populate.

Figure 13. Choosing a termination time for a new job schedule

Figure 14. Choosing an existing Parameter configuration for a new QoS job


5. Review the displayed parameter details.6. If you have selected the correct parameter set, click Next; if not, select another

set.

Configuring a new parameter set:1. Click Create Quality of Service Job.2. Click the Parameters tab. Type the new parameter values in the Configure

Quality of Service Parameters view.3. Type a Request Interval.

Specifying a request interval of 10 means that the application will considerevery tenth request that meets all other configured criteria. The system defaultis to consider every request (a request interval of 1) that meets all otherconfigured criteria.

4. If you want only Back-end Service time metrics reported, click the check boxmarked Back-end Service time only.Selecting Back-end Service time only omits metrics for user experience andpage display times. If Back-end Service time only is selected here,specifications for Page Display Time and User Experience Time on theConstraints tab are ignored.

Note: If you choose to measure all metrics (back-end service, user experience,and page display times), no metrics of any kind will be returned(including back-end service time) for browsers the have JavaScriptdisabled. However, if you choose to measure back-end service time only,the metrics for back-end service time will be returned regardless ofwhether the browser has JavaScript enabled or disabled.

5. Set the conditions if you want to limit monitoring to include, for example,requests from a certain IP address or requests for specific pages. Leave allconditions blank to monitor all requests.a. Using the radio buttons, choose multiple conditions (AND) or a single (OR)

condition.

b. Type the path of the URL in the All pages whose parent directory is field.This condition measures all requests originating from Web pages that aresubordinate in the Web site’s hierarchy to the specified URL path. QoS doesnot recognize wildcards.

c. Click Add.

Figure 15. Choosing a frequency of requests to consider for a new QoS job

Figure 16. Enabling the Back-end Service time only check box

Figure 17. Choosing multiple or single conditions parameter settings


d. Specify an IP address in the All requests from IP address field.This condition monitors requests from the IP address specified. QoS doesnot recognize wildcard characters in an IP address.

e. To monitor requests from a specific page, type the fully-qualified path of thepage in the All pages with the URI field.This condition monitors requests originating from specific pages on a Website. QoS does not recognize wildcard characters.

Note: To exclude one or more specific pages from being monitored, precedethe URL to be ignored with an exclamation point (!) character. Forexample, if you want to monitor all pages except/mydir/somepage.html, type the string:!/mydir/somepage.html

You can include and exclude pages in the same task.f. If any of the list boxes contains entries you want to eliminate, select the

entries and click Remove.6. Review your selections and click Next. If you need to begin again, click Clear.

Configuring constraints for a QoS jobYou can configure the constraint set for a QoS job in one of two ways: use anexisting constraint set or create a new one.

Figure 18. Configuring the parent directory condition

Figure 19. Configuring the IP address condition

Figure 20. Configuring the URI condition


Note: Constraint configurations are not saved until you complete the job creationprocess by naming the job.

To use an existing constraints set:1. Click Create Quality of Service Job.2. Click the Constraints tab.3. In the Configure Quality of Service Constraints view, click the arrow to the

right of the Existing configurations drop-down list.

4. Select the constraint set you want to use and click Populate. Review thedisplayed constraint values. If you have selected the correct constraint set, clickNext; if not, click Clear and select another set.

Configuring a new constraints set:1. Click Create Quality of Service Job.2. Click the Constraints tab, and type the new constraint values in the Configure

Quality of Service Constraints view.

3. In the Time Frame field, type the number of minutes to use as the time frameduring which threshold violations would trigger an event. The default value isset to 1.

4. In the Trigger event after field, type the number of violations required totrigger an event during the specified time frame. The default is one.

5. Set constraints and their corresponding event severity levels.a. When the time limit specified by an Upper Threshold value is exceeded, the

selected Event Violation is triggered and forwarded to the InternetManagement Server.

b. When the time limit drops below the Upper Threshold value, the selectedrecovery event is triggered.

6. Set the upper threshold time limit (in seconds) and violation and recoveryevent types for back-end service time, page display time, and user experiencetime.

Figure 21. Choosing an existing constraint configuration

Figure 22. Creating a new QoS job constraint set


Leave the threshold fields blank if you do not want to set a constraint and acorresponding violation and recovery event type.

Back-end Service TimeThe amount of time it takes a Web server to receive a request from thereverse proxy, process it, and respond to it. If the specified threshold isexceeded, the selected violation event is triggered.

Page Display TimeThe amount of time it takes to render a requested Web page on therequestor’s browser, from the time the rendering begins until it iscompleted. If the specified threshold is exceeded, the selected event istriggered. If Back-end Service time only was selected as a jobparameter, page display time cannot be specified.

User Experience TimeThe interval between the time a user clicks on a link to initiate a Webtransaction until the request is fulfilled. If the specified threshold isexceeded, the selected event is triggered. If Service time only wasselected as a job parameter, page display time cannot be specified.

Note: The system only sends violation and recovery events when they signal astate change. When a constraint violation occurs, a single event isrecorded. When recovery occurs, another event is recorded. There are norecurring events for the same threshold violation until the recovery eventis received by the Internet Management Server. Also, recovery events arenot time frame dependent; every recovery triggers an event.

7. Review your selections and click Next.8. If you need to begin again, click Clear.

Naming a QoS jobAssigning a job name, or saving the job, is the final step you perform whenconfiguring a QoS job. The job name is used to identify the set of parameters andconstraints associated with one or more endpoints. The name can consist of up to255 characters and should be meaningful to you. Remember, however, that ″Name″is the first column in the job log; if you make the name too long, it makes the tabledifficult to read.

To assign a name to a QoS job:1. In the Assign Job Name view, type the name of the job. This is a required field.

Note: All names must be unique.

2. Type a description of the job if you wish. This is optional.

Figure 23. Assigning a name to a job


3. Click Save. A message is displayed, informing you that the job has beenconfigured.

QoS AdministrationIn addition to configuring QoS jobs, you can perform other tasks from the WebTransaction Performance GUI.

Editing a QoS jobIf you want to change some of the values associated with a particular job, you canedit the job if it is not currently scheduled (incomplete or complete). To unschedulea job, see “Unscheduling Jobs” on page 39.1. Click Edit QoS Job in the navigation tree.2. In the Quality of Service Jobs view, select the job you want to edit by clicking

the radio button next to the job name.3. Click Next.

4. Make necessary changes to the job.5. Click Save.

Managing QoS jobsYou can view the status of all scheduled and unscheduled QoS jobs through the joblog. From the navigation tree, click Quality of Service, then click Manage Jobs.Clicking any of the column headings (Job, Application, State, or Endpoint) enablesyou to sort the log by category. Clicking a heading reverses the order of thecolumn entries.

Figure 24. Selecting a QoS job to edit


The job log enables you to view scheduled, completed, or incomplete QoS jobs.

Unscheduling JobsYou can unschedule jobs before they are run or while they are running.1. From the navigation tree, click Manage Jobs. A table of QoS jobs (running or

scheduled) is displayed.2. Select each job that you want to unschedule by clicking the check box to the

left of the label in the Job column.

Note: You can sort jobs by name, creator, state, and so on, by clicking theheadings in the job table.

3. After you select all the jobs you want to unschedule, click Unschedule checkedjobs.

Deleting Unscheduled JobsYou can also delete jobs that you have unscheduled. This action deletes the jobsfrom the database and they cannot be viewed or run again.1. From the navigation tree, click Manage Jobs. A table of QoS jobs (running or

scheduled) is displayed.2. Click the Show complete and incomplete jobs radio button.

Figure 25. Unscheduling QoS jobs


3. Select each job you want to delete by clicking the check box to the left of theJob column.


4. After you select all the jobs you want to delete, click Delete Selected.

Configuring eventsYou can configure QoS events listed in the following table from the application orthrough System Administration → Configure System Events in the navigation tree.See Chapter 8, “Managing events and event responses” on page 105 for a completeexplanation of how to configure events.

Table 2. Quality of Service event types

Quality of Service Event Types

Type Definition

QoS Task Status The scheduled job started, completed, failed, aborted, and soon.

QoS Average UserExperience Time Violation

The user experience time exceeds the constraint specified forthe user experience time parameter.

QoS Average UserExperience Time Recovery

The user experience time no longer exceeds the userexperience time parameter constraint.

QoS Average Back-endService Time Violation

The amount of time it took for the origin server to servicethe request, and respond, exceeds the constraint specified forthe service time parameter.

Figure 26. Showing all QoS jobs


Table 2. Quality of Service event types (continued)


Type Definition

QoS Average Back-endService Time Recovery

The amount of time it took for the origin server to servicethe request, and respond, no longer exceeds the constraintspecified for the service time parameter.

QoS Average Page DisplayTime Violation

The amount of time it took for the document to displaywithin the browser exceeds the constraint specified for thedisplay time parameter.

QoS Average Page DisplayTime Recovery

The amount of time it took for the document to displaywithin the browser no longer exceeds the constraintspecified for the display time parameter.

To configure a QoS event from the application:1. In the navigation tree, click Quality of Service.2. Click Configure Events.3. Select an event type from the Event Type drop-down list.

4. Select a severity level from the Event Severity drop-down list.

5. Select an event response from the Event Response drop-down list. If thedesired response is not on the list, see “Creating event responses” on page 106

Figure 27. Selecting an event type to configure

Figure 28. Selecting an event severity

Figure 29. Selecting an event response


6. Click Add to Table. The Event Table displays QoS event types.

7. Using the radio buttons below the table, you can display all QoS event typesor only a selected event type.

8. To delete any events you might have configured previously, click the checkbox next to the event type name.

9. Click Delete Selected.10. When you are satisfied with the event configuration, click OK to return to

the main browser.

Examining the event logEvents for the Quality of Service (QoS) application are stored in the managementrepository and displayed in the application’s event log. They are also displayed onthe global event log, which you can view through the System Administrationportion of the GUI. You can use the QoS log to view a list of only the most recentevents generated by QoS. This is a real-time log of events.

Viewing QoS eventsTo view the QoS event log, click Quality of Service, then click View Event Log.

While viewing the event log, you can manipulate the display in the followingways:v You can sort the log by clicking on any of the headings in the table. Clicking

again on the same table header reverses the sort order.v You can view events logged during a particular time period by selecting a start

and end data using the drop-down lists, and then clicking the Refresh button.

Figure 30. QoS event table of configured events


Event drill downYou can drill down into an event in the event log to view the records that causedthe event. Events that can provide such information are indicated by an icon at theleft of the entry.

To view the information, click the icon to the left of the event.

The report that is displayed when you click the drill-down icon depends uponhow you have configured the ReportConfig.properties file. In this file, you specifywhich columns are included (and excluded) from the reports. The values areentered in the file as a comma-separated lists of column IDs following theqoscolumns key.

Note: Only commas, not spaces, can separate the IDs. Also, you must restart theInternet Management Server (IMS) to save your selections.

The valid values and their definitions for the qoscolumns key are as follows:

Table 3. Valid values for the qoscolumns key in the ReportConfig.properties file

Value Definition

recordID Unique identifier for this record

taskInfoID Task-specific ID

requestIP IP address of the request source

userName User name for the request

userAuth User authority for the request (hostname usually does notexist)

dateStamp CLF-format date stamp

gmtOffset GMT offset

method Method, such as POST, GET

uri URI requested

protocolVersion Protocol and version; for example, HTTP/1.0

statusCode HTTP status code

contentLength Total number of bytes returned in the request

serverIP IP address of the origin server

rtt User experience time, in milliseconds

st Back-end service time, in milliseconds

prt Page display time, in milliseconds

For example, if you configure the ReportConfig.properties file asqoscolumns=uri,rtt,st,prt, your QoS Event Detail reports are formatted with theURI in the first column, user experience time in the second column, service time inthe third column, and page display time in the fourth column.

Viewing QoS reportsQuality of Service helps you to understand what kind of service your end usersare experiencing on your Web site. Figure 31 on page 44 and the followingdiscussion describe how Quality of Service measures user experience.


QoS provides graphs of current or historical activity. Three plots display averageservice time (back-end service time), average page render time, and average userexperience time (round trip time).

Service time (back-end service time)Back-end service time is the time it takes to get the requested document from theorigin server. After the QoS reverse proxy receives the Web browser’s request (1), itthen routes the request to the appropriate origin server (2). The QoS reverse proxyapplies a time stamp (t1) to the request as it sends the request to the origin server.When the origin server returns the requested document to the QoS reverse proxy(3), the QoS reverse proxy applies another time stamp to the returned document(t2). QoS then subtracts t1 from t2 to calculate the back-end service time.

Page render timePage Render Time is the time it takes the Web browser to display the overalldocument. This time is measured from the first JavaScript parse of the overallHTML document on the Web browser (t3) to the final page rendering when theJavaScript page handler calls the ″onload()″ handler (t4), including the time to getall subdocuments (images, style sheets, and so on) loaded and displayed.

User experience time (round trip time)Round trip time is the overall time that elapses between the time that the QoSreverse proxy first timestamps the initial Web browser request (t1), and when itreceives the ″onload()″ call from the Web browser (t5), signaling that the documenthas been received and displayed in the browser.

To view the graphs, use the following procedure:1. In the Quality of Service section of the navigation tree, click View Quality of

Service Report.2. Select whether you want to view the reports by endpoint or job, and click Next.3. Whether you selected job or endpoint, use the check boxes to select the jobs or

endpoints for which you wish to view reports, and click Next.Only jobs that have collected data are available for viewing in reports.

4. Select the endpoint and job (or job and endpoint) combination for which tocreate the report and click Select Time Interval.

5. Select whether you want a real time report or a specific time range for thereport, and then click View Reports.There must be traffic on the monitored site for there to be any change in the graph.

Figure 31. How Quality of Service measures the user experience


Chapter 4. Site Investigator application

This chapter describes the Site Investigator (SI) application, how to create jobs forit, and how to view the results of those jobs. Table 4 provides an overview of thetopics covered in this chapter.


Goal Refer to

Create an SI job. “Configuring a Site Investigator job” onpage 46

Select an SI endpoint for which to create ajob.

“Selecting a Site Investigator endpoint” onpage 47

Create a job schedule. “Configuring a schedule for a SiteInvestigator job” on page 47

Configure parameters for an SI job. “Configuring parameters for a SiteInvestigator job” on page 48

Configure proxies for an SI job. “Configuring proxies for a Site Investigatorjob” on page 50

Configure constraints for an SI job. “Configuring constraints for a SiteInvestigator job” on page 50

Name an SI job. “Naming a Site Investigator job” on page 53

Edit an SI job. “Editing a Site Investigator job” on page 53

Manage SI jobs. “Managing Site Investigator jobs” on page 53

Configure events for SI jobs “Configuring Site Investigator events” onpage 54

Examine the SI event log. “Examining the Site Investigator event log”on page 55

View SI reports. “Reviewing investigation results” on page 55

The Site Investigator application enables you to monitor the health of your Website and verify the integrity of the content. You can use Site Investigator to:v crawl through your site to check for any missing or damaged linksv verify that certain content (such as your corporate logo or copyright) appears on

every pagev search for content that does not belong anywhere on your site (such as

references to discontinued products or outdated URLs)v test the links and contents of those pages as you develop them

Site Investigator jobs are launched from the Tivoli Web Services Investigator (WSI)endpoint. You provide the URL that you want investigated, configure theparameters of the job (node depth, node limit, domain aliases, for example)configure the constraints, and launch the job. It runs until complete, at which timeyou can view the results of the investigation.

User scenariosYou can use the Site Investigator application in a variety of scenarios, including thefollowing:

45

Scenario 1: The Web master at Company A wants to verify that all of the linkspresent in the Web site are unbroken. The Web master wants to do thisinvestigation at the beginning of each work week. To do so, the Web masterconfigures a site investigation of a single URL (http://www.mycompany.com) thatcollects data and provide real-time notification if any broken links are found byreturning a 404 Response Code violation. The site investigation session runs at 2:00am every Sunday.

Scenario 2: Company A has a dynamically generated Web site(www.dynamicmycompany.com) that uses an Application Service Provider (ASP)to talk to a database when it renders pages. Periodically, the database crashes forportions of www.dynamicmycompany.com. The Web master wants to gatherinformation weekly about which sections of the site are not working properly.

The original developers of the site did not set the response codes for whendatabase errors occur (so an error page generates a status code of 200, whichindicates that the request was performed successfully when, in fact, it was not).The Web master knows that an error message notifies the user in the event of adatabase failure. The message displayed is ″We’re sorry, but our databases arecurrently offline for routine maintenance. Please try again later.″

To collect weekly information on database failures on this site, the Web masterconfigures a site investigation with one root URL:http://www.dynamicmycompany.com

and a desired-content-found parameter of ″We’re sorry, but our databases arecurrently offline for routine maintenance. Please try again later.″ The Web masterruns the investigation at 9:00 am every Tuesday.

Scenario 3: The Web master at Company A is rebuilding part of the corporate Website and wants to verify that what has been built to date contains no broken links.To check, he configures a site investigation that begins with the URL of the newpart of the Web site and sets a low node-depth parameter and a low maximumnumber of nodes. The investigation is scheduled on a run-once, run-now basis andyou can initiate any time you want to check progress on the rebuilding effort.

Configuring a Site Investigator jobThe following paragraphs explain how to configure Site Investigator jobs. Anoverview of the procedure is presented first, followed by detailed informationabout the configuration components.

To create a Site Investigator job, you complete the following steps:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.3. Choose a Site Investigator endpoint.4. Choose a schedule for the job.5. Configure the parameters for the job.6. Configure any proxies through which the investigation might have to go.7. Configure the constraints for the job.8. Assign a name to the job.


Selecting a Site Investigator endpointThe first step in configuring a Site Investigator job is to select the endpoint, orendpoints, from which to run the job.

To select an endpoint for a Site Investigator job:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.

The Choose Endpoint(s) view displays, containing a table of all available SiteInvestigator endpoints.

3. Select the name of the endpoint you wish to use and click Next.4. If you want to review the endpoint information, click Global Views in the

navigation tree.5. Click View All Endpoints.

If there are no Site Investigator endpoints listed in this view, you must install one.Consult your installation manual for more information.

Configuring a schedule for a Site Investigator jobThe scheduling page provides a variety of options for running Site Investigatorjobs. The most likely choices for Site Investigator jobs are to run on a regular basisor run once immediately. Those options are discussed here. For more informationabout other options, see Scheduling Application Jobs on page 99.

You can configure a schedule for a Site Investigator job in one of two ways: use anexisting schedule or create a new one.

To use an existing schedule:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.3. Click the Schedule tab.4. In the Configure Schedule view, click the arrow to the right of the Existing

configurations drop-down.5. Select the schedule you want to use.6. Click Populate to view the details of the schedule. Click Next to use this

schedule for the investigation you are configuring.

To create a new schedule:1. From the navigation tree, click Site Investigator.2. Click Create Investigation

3. Click the Schedule tab.

Figure 32. Using an existing job’s schedule to create a new Site Investigator job

Chapter 4. Site Investigator application 47

4. In the Configure Schedule view, select whether you want to run the jobimmediately or have it start at a later time. If you want the job to start later,type a time and date. Note that the job start times are in 15-minute increments.

5. If you want the job to run once, select a termination time (when the job willstop running, regardless of whether or not it has finished) at the bottom of theview and click Next.

Note: In Site Investigator, there is no timeout parameter. If you want aninvestigation to end after a certain amount of time, you can determinethat by entering a termination time at the bottom of the schedule page.

6. If you want to run the job multiple times on a regular basis, select Run jobevery: and type 24 hours in the fields provided. Alternatively, you can selectstart and end times and mark the days of the week you want the job to run.If you want the job to run less frequently than once a week, for example, every10 days, you must select Run job every: and type 240 hours in the fieldsprovided.

7. Review your selections, then click Next. If you need to begin again, click Clear.

Configuring parameters for a Site Investigator jobYou can configure the parameter set for a Site Investigator job in one of two ways:use an existing parameter set or create a new one.

To use an existing parameter set:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.3. Click the Parameters tab.4. In the Configure Site Investigator Parameters view, click the arrow to the right

of the Existing parameters drop-down list.5. Select the parameter set you want to use and click Populate. Review the

displayed parameter details. If you have selected the correct parameter set,click Next; if not, select another set.

To create a new parameter set:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.3. Click the Parameters tab and type the new parameter values in the Configure

Site Investigator Parameters view.4. Type a root URL for the investigation. This is the only required field.5. Type a value for node depth. This parameter specifies the number of nested

links below the root URL that will be examined. The default node depth is500.

6. Type a maximum number of nodes to check with this job. The maximum thatcan be checked is 2147483647.

7. If you want the Site Investigator to report only exceptions, as opposed to allthe links it visits, check the Report Exceptions box. By making this selection,you reduce the amount of data sent to the log file.

8. Type realm information if authentication is required for any secure realmsexamined by Site Investigator. Realms are secured Web sites or secured areaswithin a Web site that require authentication to gain access. Secured Web sitesgenerally display realm information in a login screen.


In the example shown here, the realm name for this site is Enterprise Server. Typethe name of each realm that Site Investigator will investigate and supply theappropriate user name and corresponding password for each realm. Thisinformation is used to authenticate the crawler when it accesses a realm. Click Addto add the information for each realm to the Site Investigator parameter set for thisjob.9. If the list contains realm names you want to exclude from the current job,

select them from the list of added realm names and click Remove.

10. Type any domain alias information, if required. Some Web sites haveadditional URLs that are accessed by aliases to another domain name on avirtual host. If the Web site being investigated has aliases, you must includethem or the investigation will not complete because pages accessed by aliasedURLs will not be included in the investigation. Click Add for each alias. If thelist box contains aliases you want to exclude from the current job, select themand click Remove.

Figure 33. Typing realm information for an investigation

Figure 34. Removing a realm name from the list of those to be investigated


11. Type any relative URIs to be ignored. Click Add for each relative URI. If arelative URI is marked as ignored, the URI is not examined by SiteInvestigator. If the list box contains relative URIs you want to exclude fromthe current job, select them and click Remove.

Note: An entry for /qosm.html appears in the list by default. This is areserved URI used with the Quality of Service application, so if youalso use Quality of Service, do not remove this URI from the list.

12. Click Next.

Configuring proxies for a Site Investigator jobSite Investigator jobs can be run through proxies that are different than the proxyused to communicate with the Internet Management Server. To ensure that theproxy allows the SI endpoint to access its Web site, you must configure thenecessary proxy authentication first. To configure proxies, perform the followingsteps:1. From the Endpoint Name list, select the endpoint or endpoints on which you

intend to run playbacks that will encounter the proxy you are configuring.2. Type the name of the domain that the endpoint will access through the proxy

in theDomain field.3. Type the User ID and Password for the specified domain that will allow the

endpoint to access the site.4. Type the name of the Proxy Host through which the SI endpoint will access the

site to be investigated.5. Type the Proxy Port number through which the SI endpoint will access the site

to be investigated.6. Click Create/Modify to add this proxy information to the list of configured

proxies.7. Repeat Steps 1 through 6 for each additional proxy you wish to run this

playback through.8. Click Next.

To delete a proxy:1. Select the check box next to the name of that proxy in the Delete Proxies table.2. Click the Delete Selected button.

Configuring constraints for a Site Investigator jobYou can configure the constraint set for a Site Investigator job in one of two ways:use an existing constraint set or create a new one.

To use an existing constraints set:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.3. Click the Constraints tab.4. In the Configure Site Investigator Constraints view, click the arrow to the

right of the Existing constraints drop-down list.5. Select the constraint set you want to use and click Populate. Review the

displayed constraint values. If you have selected the correct constraint set, clickNext; if not, click Clear and select another set.


To create a new constraint set:1. From the navigation tree, click Site Investigator.2. Click Create Investigation.3. Click the Constraints tab.4. Type the new constraint values in the Configure Site Investigator Constraints

view.

5. Set a minimum page size (in bytes) for the investigation. Pages smaller thanthis value will trigger an event. The default is zero bytes (0).

6. Set a maximum page size (in bytes) for the investigation. Pages larger thanthis value will trigger an event. The default is 2147483647 (231-1)

7. Select a severity level for the event issued if a page does not fall within theminimum and maximum range.

8. Type any content you want found during the investigation in the DesiredContent field. Site Investigator searches every page during the investigationfor any text you type in this field.

Note: This constraint is case-sensitive. Type the content exactly as it would beencountered in the investigation. Also, if the content can be inserted inthe Web pages in more than one way, you should reduce the string to

Figure 35. Configuring the page size constraint for a site investigation

Figure 36. Configuring the desired content constraint for a site investigation


its essence to ensure it will be found. For example, if you are checkingto verify that the company logo appears on every page of your Website, it is better to type the name of the graphic instead of the entireinsertion command. For example, searching for logo.gif instead of<img src="../graphics/logo.gif" width="1" height="92"alt="company logo (161 bytes)"> will include files named logo.gifthat are not in the /graphics directory or have other attributes that donot match this instance of the img src string.

Click Add after each content entry. If the list box contains content you do not wishto search for, select it and click Remove.9. Select a severity level for the event issued if a page containing the content is

found.10. Type any content you do not want found during the investigation in the

Undesired Content field. (See the note in Step 8 for search recommendationsand case sensitivity.) Click Add after each content entry. If the list boxcontains content you do not wish to search for, select it and click Remove.

11. Select a severity level for the event issued if a page is found containing theundesired content.

12. Select the HTTP Response Codes that you want reported. A list of responsecodes is provided in Appendix E, “HTTP status codes” on page 149. Choosemultiple responses by keeping the Ctrl or Shift key pressed as you click yourselections in this drop-down list. Ctrl-select includes non-contiguous responsecodes and Shift-select includes contiguous response codes. The selections thatinclude asterisks enable you to make one selection that includes all codes ofthat level. For example, 3** includes all 300-level response codes.

13. Select an event severity level for the event issued if a configured responsecode is received.

14. Review your selections and click Next.

Figure 37. Configuring the undesired content constraint for a site investigation

Figure 38. Configuring HTTP response code constraints for a site investigation


Naming a Site Investigator jobAssigning a job name, or saving the job, is the final step you perform whenconfiguring a Site Investigator job. The name can consist of up to 255 charactersand should be meaningful to you. Remember, however, that ″Name″ is the firstcolumn in the job log; if you make the name too long, you make the table difficultto read.

To assign a name to a Site Investigator job:1. In the Assign Job Name view, type the name of the job.

Note: All names must be unique.2. Type a description of the job if you wish. This is optional.3. Click Next. A message informs you that the job has been scheduled

successfully.

Site Investigator AdministrationIn addition to configuring Site Investigator jobs, you can perform other SiteInvestigator tasks from the Web Transaction Performance GUI.

Editing a Site Investigator jobIf you want to change some of the values associated with a particular job, you canedit the job if it is not currently scheduled (unscheduled, incomplete, or complete).1. From the navigation tree, click Site Investigator.2. Click Edit Investigation on the navigation tree.3. In the Site Investigator Jobs view, select the job you want to edit by clicking

the radio button to the left of the table, then click Next.4. Make the necessary changes and click Save.

Managing Site Investigator jobsYou can view the status of all scheduled Site Investigator jobs through the job log.1. From the navigation tree, click Site Investigator.2. Click Manage Jobs.


The job log enables you to view scheduled, completed, or incomplete SiteInvestigator jobs.

Unscheduling jobsYou can unschedule jobs before they are run or while they are running.1. From the navigation tree, click Site Investigator.2. Click Manage Jobs. A table of jobs (running or scheduled) is displayed.


3. Click the Show scheduled jobs radio button.4. Select one or more jobs that you want to unschedule by clicking the check box

to the left of the job entry.


5. When you have selected all the jobs you want to delete, click Unschedulechecked jobs.

Deleting unscheduled jobsYou can also delete jobs that you have unscheduled. This action deletes the jobsfrom the database and they cannot be viewed or run again.1. From the navigation tree, click Site Investigator.2. Click Manage Jobs. A table of Site Investigator jobs (running or scheduled) is

displayed.


3. Click the Show complete or incomplete jobs radio button.4. Select each job you want to delete by clicking the check box to the left of the

job entry.5. When you have selected all the jobs you want to delete, click Delete checked

jobs.

Configuring Site Investigator eventsThere are two types of Site Investigator events, those that relate to Site Investigatorjobs, and those that relate to the functioning of the Site Investigator endpoint (SiteInvestigator system events). The following table lists those events related to SiteInvestigator jobs:

Table 5. Site Investigator event types

Site Investigator Event Types

Type Definition

SI Job Status The scheduled job either started, completed, failed, aborted,or could not start.

SI Aggregate Page SizeViolation

A page being investigated violates the constraint specifiedfor the page size parameters.

SI Response Code Violation An unexpected HTTP response code was returned.

SI Undesired Content Found A content string that is not supposed to be included on apage is found.

SI Desired Content NotFound

A content string that is supposed to be included on a page isnot found.

SI URL Connection TimedOut

The request sent by SI to the site timed out before a responsewas returned to SI.

Site Investigator related system events (functioning of the endpoint) are configuredthrough the System Administration section of the navigation tree. For moreinformation about configuring these Site Investigator related system events, refer to“Configuring events” on page 112.

To configure a Site Investigator event:1. From the navigation tree, click Site Investigator.2. Click Configure Events.3. Select an event type from the Event Type drop-down list.4. Select an event response from the Event Response drop-down list. If the

desired response is not on the list, see “Creating event responses” on page 106.5. Select a severity level from the Event Severity drop-down list.


6. Click Add to Table. The Event Table displays Site Investigator event types.Radio buttons below the table enable you to display all event types or aselected event type.

7. When you are satisfied with the event configuration, return to the mainbrowser view.

Examining the Site Investigator event logBecause there are two different types of Site Investigator events, these events arestored in the management repository and displayed separately in the application’sevent log and the system event log. You can use the Site Investigator event log toview a list of only the most recent events related to Site Investigator jobs. This is areal-time log of events.

To view the Site Investigator event log:1. Click Site Investigator.2. Click Examine Event Log.

To view the system events related to Site Investigator:1. Click System Administration.2. Click View System Event Log.

You can determine the maximum number of events to retrieve by entering a valuein the Maximum Number of Events Retrieved field. You can sort the log bycategory by clicking any of the column headings. Clicking again on the headingsreverses the order of the column entries.

To define the time period from which events are retrieved, select a start date andend date for the retrieval using the drop-down lists.

Reviewing investigation resultsYou can review the results of a completed site investigation. A table listing all thevalid links and all the exceptions (constraint violations) is available from the GUI.To view the completed results of an investigation:1. From the navigation tree, click Site Investigator.2. Click View Site Investigation Report.


Chapter 5. Synthetic Transaction Investigator application

This chapter describes the Synthetic Transaction Investigator (STI) application, howto create jobs for it, and how to view the results of those jobs. Table 6 provides anoverview of the topics covered in this chapter.


Goal Refer to

Download the STI recorder. “Downloading the STI recorder” on page 58

Install the STI recorder. “Installing the STI Recorder” on page 59

Use the STI recorder. “Using the STI recorder” on page 62

Edit a recorded transaction. “Editing a transaction” on page 66

Delete a recorded transaction. “Deleting a transaction” on page 66

Create a transaction playback job. “Creating a transaction playback” on page 67

Choose an STI endpoint on which toplayback a job.

“Choosing an endpoint” on page 67

Schedule a playback job. “Configuring a schedule” on page 67

Select a recorded transaction for a playbackjob.

“Choosing a Transaction” on page 68

Configure proxy information for a playbackjob.

“Configuring proxy information” on page 68

Configure constraints for a playback job. “Configuring constraints” on page 69

Assign a name to a playback job. “Assigning a job name” on page 70

Configure an STI playback endpoint. “Playback endpoint configuration” onpage 70

Edit a transaction playback job. “Editing transaction playbacks” on page 72

Manage STI jobs. “Managing STI jobs” on page 72

Configure STI events. “Configuring STI events” on page 73

View the STI event log. “Viewing Synthetic Transaction Investigatorevents” on page 74

Drill down into event data. “Event drill down” on page 75

View STI reports. “Synthetic Transaction Investigator reports”on page 76

View ARM correlation data “ARM correlation” on page 71

View Page Analyzer Viewer reports. “Page Analyzer Viewer report” on page 78

The Synthetic Transaction Investigator (STI) application provides another means formeasuring the availability and performance of your Web environment. With STI,you record (or create) the details of specific Web transactions and then play themback later (at scheduled times). This enables you to determine how your Web siteresponds to the activity: is the site available and what sort of performance does itdeliver?

The Synthetic Transaction Investigator measures availability, as well as two of themetrics also measured by the Quality of Service application:

57

v User experience time — the span from the time the user clicks on a link toinitiate a Web transaction until the request is fulfilled. User experience time issometimes referred to as round-trip time.

v Service time — the amount of time it takes a Web server to receive a request,process it, and respond to it.

Availability is measured by determining whether any of the STI parameterthresholds are exceeded during playback. Availability is expressed as a percentagebased upon the number of successful playbacks divided by the total number ofplaybacks attempted.

The transactions you record can be any type that characterizes common end-userinteraction on your Web site, such as searching for information, enrolling in a class,opening or checking on an account, or purchasing goods or services online. TheSTI application records all of the information that appears in an HTTP request,including URL, form data, and session data, that make up your transaction andcreates an XML document. When you have completed recording a transaction, youhave an opportunity to edit it if you wish (to eliminate false steps during therecording session or perhaps to shorten it). You can schedule this synthetictransaction to play back from one or more of the Web Services Investigatorendpoints at various times to see how your Web site handles the transaction underdifferent load situations.

User scenariosYou can use the Synthetic Transaction Investigator application in a variety ofscenarios, including the following:

Scenario 1: Company A wants to measure the availability and response time of itse-commerce Web environment. To do so, Company A’s Web master records asynthetic transaction that will be executed (played back) from a specific endpointto measure the Web server. The synthetic transaction will run repeatedly from theendpoint between 8:30 am and 10:00 am each day from January 15 through April15.

Scenario 2: Company A wants to determine if there are differences in availabilityand response time to user requests based on the source of the request. CompanyA’s Web master records a synthetic transaction that will play back from fourdifferent endpoints. The synthetic transactions will be scheduled to play backsimultaneously and repeatedly from 11:30 a.m. to 1:00 p.m. each day fromNovember 15 through December 24.

Downloading the STI recorderThe STI Recorder is a separately-installable program that operates only onMicrosoft Windows platforms. Before you can use the recorder, you mustdownload the installation file from the Internet Management Server and install therecorder on your Microsoft Windows client. To download and install the recorder,perform the following steps:1. Click Synthetic Transaction Investigator in the navigation tree to expand the

list of STI operations.2. Click Download Transaction Recorder.3. Click the link to the setup_sti_recorder.exe file in the work area.


4. Follow the instructions in the work area to download the software to a local ornetwork-accessible drive.

Installing the STI RecorderTo install the Synthetic Transaction Investigator Recorder (STI Recorder), performthe following steps:1. Locate the setup_sti_recorder.exe file on your local or network-accessible

drive.2. Double-click the file name, or type the file name in a command window to

begin the installation process.

Chapter 5. Synthetic Transaction Investigator application 59

3. Click Next to start installing the recorder.

4. Specify a drive and directory for the recorder software or accept the defaultpath. If the path specified does not exist, it will be created for you. Click Next.


5. Fill in the fields as required for your configuration.

Host Name Specify the host name of the InternetManagement Server (IMS), without aprotocol-qualified prefix. For example, use aname like terminator.dev.tivoli.com instead ofhttp://terminator.dev.tivoli.com.

SSL Enabled Select this box if the IMS is using securesocket layer (SSL) communications.

Use default port Specify which default Web server port (port 80for http or port 443 for https) to use whencommunicating Web server on the IMS. To usethe default, select the radio button indicatingYes, which is the default selection. To choose adifferent port, click the radio button for Noand type the alternate port number in the PortNumber field.

Port Number Specifies the non-default Web server port onthe IMS. This field is only active if Usedefault port is set to No.

Proxy Protocol Specifies the protocol used forcommunications with the proxy server, if aproxy server is used to cache web pages.Select No Proxy if your IMS does not accessweb sites through a proxy server.

6. Click Next.


7. A confirmation screen displays the installation path and the amount of diskspace that is needed for the installation.

8. To change any configuration option, click Back to return to the previousscreen.

9. To cancel the installation, click Cancel.10. Click Next to install the recorder. A progress bar is displayed as the software

installs.11. A completion screen indicates a successful installation. If errors occurred

during the installation, an error message telling you to examine the log file isdisplayed. Click Finish to close the installation program.

Using the STI recorderThis section explains how to start and configure Synthetic Transaction Investigatorjobs. The Synthetic Transaction Investigator application is different from theQuality of Service or Site Investigator applications, in that it is divided into twocomponents: recorder and player. The recorder component is a standaloneapplication. The player component is integrated with Web TransactionPerformance. Use the recorder component to capture all the components of a Webtransaction. Use the player component to run recorded transactions to developavailability metrics. Additionally, the process of configuring parameters andconstraints for STI is different from the processes used to configure other WebTransaction Performance applications.

The Synthetic Transaction Investigator recorder only works with Microsoft’sInternet Explorer Version 5.5 SP2, or higher. However, play back of recordedtransactions only works with Microsoft Internet Explorer Version 6 or higher. Ifyou are recording a transaction that goes through a proxy server, you mustconfigure the proxy server’s information in your browser before using the recorder.Refer to the browser’s help system for the specifics of configuring a proxy serverand accessing the settings in your browser using.

To start the recorder, perform the following steps:


1. Click Start.2. Click Programs.3. Click Tivoli Synthetic Transaction Investigator Recorder.

The STI recorder’s installation process does not create a desktop shortcut forthe STI recorder. If you want to create a desktop shortcut instead using of theStart menu, the default path to the the recorder’s executable file isdrive:\Program Files\Tivoli\Internet\STI-Recorder\bin\Recorder.exe

Access Microsoft Windows help topics for information about creatingshortcuts.

4. Specify realm authorization information. This step is optional and only neededif you are recording a transaction on a Web server that uses realms to providesecurity. Type the following information:

User Name Type the account name of the user accessing the realm.

Password Type the password required for the account to access therealm.

5. Specify proxy authorization information. This step is optional and onlyneeded if you are recording a transaction that will access URLs using a proxyserver. Type the following information:

User Name Type the account name of the user accessing the proxy server.

Password Type the password required for the account to access theproxy server.

6. Type the URL of a Web server in the Location field. If a protocol prefix is notprovided, http:// is assumed. To access a secured server (SSL), prefix the URL


with https://.

Buttons for common browser functions such as Back, Forward, and Refreshare accessible in the recorder. These buttons perform the same functions in therecorder as they do in any browser. Additional recorder buttons, SaveTransaction and Reset Transaction are also provided. A progress indicatorshows Done to indicate when a page has finished loading in the recorder.While recording transactions, wait for the Done indicator before clicking onanother link or navigating forward or backward. Failing to wait for the Doneindicator will create an invalid transaction.

Completion Time is the time the browser waits before considering itself donerendering a page. Most Web pages generate this ″done″ response when fullyrendered, but for those that do not, this completion time value automaticallygenerates the response. If the Web pages in your transaction do not need thisfeature, type 0 in this field to allow the page to send the ″done″ response.

The check box labeled Repaint allows you to enable the recorder browserwindow to resize successfully to accommodate JavaScript on web sites thatattempts to resize the browser window. This feature is off by default, so if youknow you will need it, enable it by checking the box labeled Repaint. If whenenabled this feature appears to interfere with a site’s ″action upon resize″code, disable it by removing the check from the Repaint check box. The checkbox resets each time you start the recorder.


7. Press Type or click the Location button to load the URL.

Navigate through the Web pages to record your clicks and entries as a transaction..8. When you finish, click Save Transaction to save the transaction.9. Saved transactions are uploaded to the Internet Management Server. When

Save Transaction is clicked, you are prompted for Internet ManagementServer account information. Provide a valid account name (user name) andpassword to save the transaction in the management repository.

10. Type a name for the transaction in the Transaction Name field.


11. Click Submit Query to upload the transaction to the Internet ManagementServer.

12. Click Reset Transaction to purge the session information and begin recordingfrom the same or different URL.

Note: Failure to click Reset Transaction before beginning a new recordingsession might result in transactions that cannot be saved.

Note: All other STI operations (editing transactions, deleting transactions,scheduling transactions, and so on), are performed through the WebTransaction Performance navigation tree by selecting Synthetic TransactionInvestigator.

Editing a transactionYou can edit your recorded transactions. You can delete URLs that are unnecessaryto the transaction or you can shorten the transaction.1. Click Synthetic Transaction Investigator.2. Click Edit Transaction.3. Select a transaction from the drop-down list. Click Load to begin loading the

transaction into the editable window in the work area.4. When you finish editing, click Save to save the revised transaction.

Deleting a transactionYou can delete an entire STI transaction document from the database using thefollowing procedure.1. From the navigation tree, click Synthetic Transaction Investigator.2. Click Delete Transaction.


3. From the drop-down list, select the transactions you want to delete.4. Click Delete.

Note: Any jobs that use this transaction must be edited to select anothertransaction, or they must be deleted using the Manage Jobs functionunder Synthetic Transaction Investigator.

Creating a transaction playbackThis section describes the process of creating a transaction playback.

Choosing an endpoint1. To play back a recorded transaction, click Create Transaction Playback from

the list of Synthetic Transaction Investigator options in the navigation tree.2. In the Choose Endpoint(s) view, select an endpoint to playback the transaction.3. Select whether you want to enable Page Analyzer Viewer by default for this job

by clicking on the Enable Page Analyzer Viewer by Default.4. Click Next.

Configuring a scheduleThe scheduling page provides a variety of options for running SyntheticTransaction Investigator jobs. The most likely choice for Synthetic TransactionInvestigator jobs is to run on a regular basis during a particular time period. Thatoption is discussed here.

You can configure a schedule for an Synthetic Transaction Investigator job in one oftwo ways: use an existing schedule or create a new one.

To use an existing schedule:1. From the Synthetic Transaction Investigator options in the navigation tree, click

Create Transaction Playback.2. Click the Schedule tab.3. In the Configure Schedule view, click the down arrow to the right of the

Existing configurations drop-down list.4. Select a schedule from the list. Click Populate to view the values for the

schedule you have selected.5. Review your selection, and click Next. If you need to begin again, click Clear.

To create a new schedule:1. Click the Create Transaction Playback Schedule tab.2. Determine whether you want the job to start as soon as possible or at a later

date or time.v To start the job immediately, select Start the job as soon as possible.v To start the job at a later date or time, select Start the job at and specify the

time and date for the job to start using the choices you made in thedrop-down boxes.

3. Choose the number of times to run this job.v Click Run job only once to run the job once.v Click Run job every and use the drop-down lists to specify the start time,

end time, and days of the week during which you want the job to runcontinuously:


– To run the job between selected hours, select a Start time and End timeusing the drop down boxes.

– Select one or more days of the week on which the job will run.4. Decide whether this job should terminate, and if so, when.

v Select Never terminate this job if you want the job to run without everterminating.

v If you want the job to stop at a certain time on a specific date, clickTerminate job at and specify the stop time and stop date using thecorresponding drop-down boxes.

5. Click Next. If you need to begin again without saving the values you haveentered, click Clear.

Choosing a Transaction1. From the Synthetic Transaction Investigator options in the navigation tree, click

Create Transaction Playback.2. Click the Transaction tab.3. Click on the down arrow to the right of the drop-down list to view the

transactions.4. If you wish to review the content of the transaction, click Populate. The

transaction and subtransactions will be displayed.5. To accurately measure transactions involving cookies or other code that is

cached by browsers, it might be necessary to clean the browser’s cache andcookie repository before repeating a transaction. Using the drop-down listsunder Cache Cleaning and Cookie Cleaning, select how you want each to beaccomplished:v None — no cleaning performedv Iteration — cleaning performed after each job is runv Request — cleaning performed as each HTTP request is processed

6. Click Next to continue.

Configuring proxy informationTo play back transactions on endpoints, you need to specify proxy authorizationinformation if the endpoint uses a proxy server. This includes identifying whichendpoint the proxy authorization is for, and the user names and passwords thatare used to access a given domain.1. From the Synthetic Transaction Investigator options in the navigation tree, click

Create Transaction Playback.2. Click the Configure Proxies tab.3. From the Endpoint Name list, select the endpoint or endpoints on which you

intend to run playbacks that will encounter the proxy you are configuring.4. Type the name of the realm that the endpoint will access through the proxy in

the Realm Name field.

Figure 39. Choosing a termination time for a new job schedule


5. Type the User name and Password for the specified realm that will allow theendpoint to run the playback through that realm.

6. Click Create/Modify to add this proxy information to the list of configuredproxies.

7. Repeat Steps 1 through 4 for each additional proxy you wish to run thisplayback through.

8. Click Next.

To delete a proxy, select the check box next to the name of that proxy in the DeleteProxies table, and click the Delete Selected button.

Configuring constraintsConfiguring the constraint set for a Synthetic Transaction Investigator job differsfrom the other Web Transaction Performance applications. You cannot use existingconstraint sets and you can configure the overall transaction or each of thesubtransactions.

Note: You must select a transaction before you configure the constraints.

To create a new constraint set:1. In the Number of Retries field, type the number of times you want the job to

retry each job or subtransaction before it sends a timeout event to themanagement server.

2. In the Retry Lag Time field, type the number of seconds you want the systemto wait before retrying a job or subtransaction.

3. In the Timeout Period field, type the number of seconds you want the systemto wait for a response to a subtransaction before timing out and retrying thesubtransaction.

4. Set a time limit (in seconds) for the global round-trip time and for the globalservice time. These times are for the overall transaction. You do not have to setthese limits.

5. Set the global event severities. Pick a severity level for both violation andrecovery for each of the six constraints. The levels for round-trip time andservice time are for both the overall transaction and the subtransactions. Thelevels for the other constraints are for subtransactions only.

6. Configure the constraints for the recorded subtransactions. You can setconstraints for each subtransaction or you can set a constraint for all thesubtransactions by configuring the constraints first and then clicking Apply toAll.a. Set round-trip time and service time limits.b. In the HTTP Response Codes field, select the response codes you want to

monitor (see Appendix E, “HTTP status codes” on page 149 for a list ofHTTP Response Codes). You can make multiple selections here. Hold theCtrl key as you click on your selections in this drop-down list.

c. In the Desired Content Not Found field, type any content that should befound during the transaction.

Note: You must type the HTML content exactly as it would be encounteredin the investigation. This means that you must include any tags andspaces that are part of the string for which you search. This constraintis case-sensitive.


Click Add after each content entry. If the list contains content you do notwish to search for, select it and click Remove.

d. In the Undesired Content Found field, type any content that should not befound during the investigation.

Note: You must type the HTML content exactly as it would be encounteredin the investigation. This means that you must include any tags andspaces that are part of the string for which you search. Thisconstraint is case-sensitive.

Click Add after each content entry. If the list contains content you do notwish to search for, select it and click Remove.

e. To enable ARM correlation, select the check box next to ARM Correlation.For more information about ARM correlation, see “ARM correlation” onpage 71.

7. Review your selections and click Next.

Assigning a job nameAssigning a job name is the final step you perform when configuring an SyntheticTransaction Investigator job. The name can consist of up to 255 characters andshould be meaningful to you. Remember, however, that ″Name″ is the first columnin the job log. If you make the name too long, you make the table difficult to read.

To assign a name to a Synthetic Transaction Investigator job:1. In the Assign Job Name view, type the name of the job (required).

Note: All names must be unique.2. Type a description of the job. This is optional.3. Click Next. A message is displayed, informing you that the job has been

configured successfully.

Playback endpoint configurationSynthetic Transaction Investigator playback jobs, running against secure Web sites,Web pages that include secure content, or through proxies, might time out whenthe browser prompts the user for security information. These browser promptsinclude:v Security certificates for serving secure contentv Mixed secure and non-secure page contentv Proxy authenticationv Realm authentication

To ensure that the browser does not present security certificate dialog boxes duringplayback, you must perform the following steps on each Synthetic TransactionInvestigator playback endpoint:1. Log in using the designated user account, usually TivoliStiPlayback.2. Open the Internet Explorer browser.3. Navigate to the secure URL.4. When the Security Alert dialog box appears, click the check box next to In the

future, do not show this warning, and then click the More Info button.5. Click the Content tab.6. Click the Certificates button.7. Click the Trusted Root Certification Authorities tab.


8. Click the Import button.9. Follow the Import Wizard instructions to import a certificate into the browser.

To ensure that the browser does not display a mixed security dialog box duringplayback, you must perform the following steps on each STI playback endpoint:1. Log in using the designated user account, usually TivoliStiPlayback.2. Open the Internet Explorer browser.3. Click Tools.4. Click Internet Options.5. Click the Security tab.6. Click the Internet Web content zone icon.7. Click Custom Level.8. Select Enable under Display Mixed Content in the Miscellaneous settings.9. Click OK.

10. Click Yes in the warning dialog box.11. Click the Local Intranet Web content zone icon.12. Repeat Steps 7–10 and click OK.

To ensure that the browser does not present proxy authentication dialog boxesduring playback, you must perform the following steps on each STI playbackendpoint:1. Log in using the designated user account, usually TivoliStiPlayback.2. Open the Internet Explorer browser.3. Navigate once to any URL through each authenticating proxy that playback

might encounter.4. When the browser displays an authentication dialog box for the proxy, select

the Save this password to your password list check box.5. Type the user name and password for the user account.6. Click OK.

To ensure that the browser does not present realm authentication dialog boxesduring playback, you must perform the following steps on each STI playbackendpoint:1. Log in using the designated user account, usually TivoliStiPlayback.2. Open the Internet Explorer browser.3. Navigate once to any URL in each authenticating realm that playback might

encounter.4. When the browser displays an authentication dialog box for the realm, select

the Save this password to your password list check box.5. Type the user name and password for the user account.6. Click OK.

ARM correlationThe Application Response Measurement (ARM) API was developed to meet thechallenge of tracking performance through complex, distributed computingnetworks.

To use ARM, an application is instrumented with calls to the ARM API. The mostimportant ARM API calls are start and stop calls, placed just before a transaction


starts and just after a transaction ends. A measurement agent, called an ARM agent,clocks the ARM start and stop calls in order to calculate transaction times.

You can use the STI Recorder to record a Web transaction (such as viewing anaccount or making a purchase) that includes requests to applications running on aWebSphere server. When setting up the corresponding STI Player job, you canenable the collection of ARM data for some or all of those requests(subtransactions). When you run the playback job, the Enterprise TransactionPerformance ARM agent on the WebSphere server collects the ARM data for thesubtransactions that you specified when setting up the job. You can view theresults through a link to the Enterprise Transaction Performance server.

You can collect ARM data for specific requests in an STI Player job provided thefollowing conditions are met:v IBM WebSphere Application Server Version 5.0 must be installed on the

WebSphere server. It must be configured to use the Enterprise TransactionPerformance ARM agent, also installed on the server.

v The requests that you mark for ARM data collection must be requests toapplications on the WebSphere server.

v The requests that you specify must already be configured in WebSphere forARM data collection.

v You must specify the URL of the Enterprise Transaction Performance serverduring installation of the Web Services Investigator endpoint from which the STIPlayer job runs.

STI administrationIn addition to recording and playing back STI transactions, you can perform otherSTI tasks from the Web Transaction Performance GUI.

Editing transaction playbacksTo edit a transaction playback:1. From the Synthetic Transaction Investigator options in the navigation tree, click

Edit Transaction Playback.2. Select a transaction playback to edit by clicking the radio button to the left of

the job name.

Managing STI jobsYou can view the status of all scheduled STI jobs through the job log. The job logenables you to view scheduled, completed, or incomplete jobs. From the navigationtree, click Synthetic Transaction Investigator, then click Manage Jobs. Clickingany of the column headings enables you to sort the log by category.Double-clicking the headings reverses the order of the column entries.

Unscheduling jobsYou can unschedule jobs before they are run or while they are running.1. From the Synthetic Transaction Investigator options in the navigation tree, click

Manage Jobs. A table of STI jobs (running or scheduled) is displayed.2. Click the Show scheduled jobs radio button.3. Select the jobs that you want to unschedule by clicking the check box to the left

of the job entry.4. When you have selected all the jobs you want to delete, click Unschedule

Selected.


Deleting unscheduled jobsYou can also delete jobs that you have unscheduled. This action deletes the jobsfrom the database; they cannot be viewed or run again.1. From the Synthetic Transaction Investigator options in the navigation tree, click

Manage Jobs. A table of STI jobs (running or scheduled) is displayed.2. Click the Show complete and incomplete jobs radio button.3. Select each job you want to delete by clicking the check box to the left of the

job entry.4. When you have selected all the jobs you want to delete, click Delete Selected.

Configuring STI eventsYou can configure STI events listed in the following table from the application orthrough the System Administration portion of the GUI. See “Configuring events”on page 112 for a complete explanation of how to configure events.

Table 7. Synthetic Transaction Investigator event types

Synthetic Transaction Investigator Event Types

Type Definition

STI Task Status The scheduled job has either started, completed, failed,aborted, or could not start.

STI Round Trip TimeViolation

The round-trip time exceeds the constraint specified for theround-trip time parameter.

STI Round Trip TimeRecovery

The round-trip time no longer exceeds the round-trip timeparameter constraint.

STI Service Time Violation The amount of time it took to service the request andrespond exceeds the constraint specified for the servicetime parameter.

STI Service Time Recovery The amount of time it took to service the request andrespond no longer exceeds the constraint specified for theservice time parameter.

STI Response Code Violation A specified HTTP response code was returned.

STI Response Code Recovery A specified HTTP response code is no longer returned.

STI Undesired Content Found A content string that is not supposed to be included on apage is found.

STI Undesired Content NotFound

A content string that is not supposed to be included on apage is not found.

STI Desired Content NotFound

A content string that is supposed to be included on a pagewas not found.

STI Desired Content Found A content string that is supposed to be included on a pagewas found.

STI URL Not Available The playback URL is not available (violation).

STI URL Available The playback URL is available (recovery).

STI Overall Transaction TimeViolation

The amount of time it took overall transaction to completeexceeds the constraint specified for the overall transactiontime parameter.

STI Overall Transaction TimeRecovery

The overall transaction time no longer exceeds theconstraint specified for the overall transaction timeparameter.


Table 7. Synthetic Transaction Investigator event types (continued)


Type Definition

STI Overall Service TimeViolation

The amount of time it took the overall service to completeexceeds the constraint specified for the overall service timeparameter.

STI Overall Service TimeRecovery

The overall service time no longer exceeds the constraintspecified for the overall service time parameter.

To configure an STI event from the application, complete these steps:1. From the Synthetic Transaction Investigator options in the navigation tree,

click Configure Events.2. Select an event type from the Event Type drop-down list.3. Select an event response from the Event Response drop-down list.

If the desired action is not on the list, you must create that response. See“Creating event responses” on page 106.

4. Select a severity level from the Event Severity drop-down list.5. Click Add to Table. The Event Table displays STI event types.6. Using the radio buttons below the table, you can choose to display all STI

event types or only a selected event type.7. To delete any previously configured events, select the check box next to their

event type names.8. Click Delete Selected.9. When you are satisfied with the event configuration, click OK to return to the

main browser.

Viewing Synthetic Transaction Investigator eventsEvents for the Synthetic Transaction Investigator (STI) are stored in themanagement repository and displayed in the application’s event log. They are alsodisplayed on the global event log. You can use the STI log to view a list of only themost recent events generated by the STI application. This is a real-time log ofevents.

From the Synthetic Transaction Investigator options in the navigation tree, clickView Event Log.

Note that you can determine the maximum number of events that are displayed inthe log by entering a value at the top of the log. In addition, you can sort the logby category by clicking any of the column headings. Clicking the headings again


reverses the order of the column entries.

You can identify the job that generated the event by looking in the Annotationcolumn of the event log. The job name is in the annotation data.

Event drill downIt is now possible to drill down into an event in the event log to view the recordsthat caused the event. Events that can provide such information are indicated byan icon at the left of the entry.

To view the information, click the icon to the left of the event.

The subsequent report that is displayed when you click the drill-down icondepends upon how you have configured the ReportConfig.properties file. In thisfile, you specify which columns are included (and excluded) from the reports. Thevalues are entered in the file as a comma-separated lists of column IDs followingthe sticolumns key.

Note: Only commas, not spaces, can separate the IDs. Also, you must restart theInternet Management Server (IMS) to save your selections.

The valid values and their definitions for the sticolumns key are as follows:

Value Definition

recordID Unique identifier for this record

taskInfoID Task-specific ID

requestIP IP address of the request source

userName User name for the request

userAuth User authority for the request (hostname usually does not exist)

dateStamp CLF-format date stamp

gmtOffset GMT offset

method The method, such as POST or GET


Value Definition

uri URI requested

protocolVersion Protocol and version; for example, HTTP/1.0

statusCode HTTP status code

contentLength Total number of bytes returned in the request

sid ID unique to this session

rtt User experience time, in milliseconds

st Back-end service time, in milliseconds

SSV Search-string violation list

SSA Search-string affirmation list

For example, if you configure the ReportConfig.properties file assticolumns=dateStamp,uri,rtt, your STI Event Detail reports will be formattedwith the date in the first column, the URI in the second column, and the roundtrip time (user experience time) in the third column.

Synthetic Transaction Investigator reportsThe Synthetic Transaction Investigator provides information similar to thatprovided by the Quality of Service, but in the context of specific transactions.Figure 40 and the following discussion describe how Synthetic TransactionInvestigator measures user experience.

Synthetic Transaction Investigator (STI) measures round trip time in a slightlydifferent way than Quality of Service does. As the STI player makes a request for adocument from the Web server, a time stamp is applied (t1). When the requesteddocument, including subdocuments, is returned to and rendered by the WebServices Investigator endpoint, another time stamp is applied (t2). STI thencalculates the round trip time by subtracting t1 from t2.

The Synthetic Transaction Investigator application provides six different reports tohelp you visualize the results of its jobs. A summary of each report follows:

Figure 40. How Synthetic Transaction Investigator measures round trip time


Round trip time graph for a single job on a single endpointThis report displays a graph of the round trip time for a particular job on aparticular endpoint over time. Each bar in the graph represents a single overalltransaction. Each bar is also a drilldown link to the STI Statistics Table for this joband endpoint pair and for this overall transaction record.

If the STI transaction is run against a server that is running a Quality of Serviceendpoint, the system will also display a service time graph for the job andendpoint pair.

The values in the summary table exclude the results of any job that encountered anavailability violation.

Round trip time graph for mulitple jobs and multiple endpointsThis report displays round trip times for multiple jobs and endpoints over aparticular time range. Each point on the graph represents a subset of the selectedtime range. Each subset contains the average of all overall transaction round triptimes measured during the selected time range.

The color and shape of the data points on the graph tell you at a glance what theoutcome of the jobs were:v A green circle indicates that there were no violations.v A yellow triangle indicates that there was only a performance violation.v A red square indicates that there was an availability violation, which most likely

includes a performance violation too. Availability violations take precedenceover performance violations for a single job.

Each point on the graph is also a drilldown link to a single job and endpoint pair’sgraph that displays the details of a particular job on a particular endpoint.

The values in the summary table exclude the results of any job that encountered anavailability violation.

Average response time graphThis report displays an area chart that represents an average overall transactionresponse time for one or all jobs on an endpoint (depending on your selection).

Each point on the graph represents a subset of the overall selected time range.Each subset contains the average of all overall transactions’ round trip times forjobs run during that subset’s time range. Round trip times for jobs that haveavailability violations are not included in the average.

Availability graphThis report displays an area graph that represents the overall percentage ofavailability of the sites investigated by the synthetic transaction job or jobs.

Each point on the graph represents a subset of data for the overall selected timerange. Each subset contains the availability status of all overall transactions runduring the subset’s time range.

The availability percentage is calculated by adding the number of successfuloverall transactions (a) to the number of overall transactions with performanceviolations (b), and dividing that number by the sum of that number added to thenumber of overall transactions with availability violations (c). Written as anequation, it looks like this:


(a+b) / (a+b+c)

Transaction Details tableThis report table details a collected transaction’s individual subtransactionstatistics. It lists each subtransaction in the order it was run, the number of times itwas run (executed), the number of times the it failed, the number of times it had aperformance violation (exceeded thresholds) without an availability violations, andits various round trip and service time metrics measured during the collectedtransaction’s time range.

Note: If a subtransaction exceeds both its round trip threshold and its service timethreshold, the Thresholds Exceeded count is only increased by one. Also,subtransactions with availability violations do not count toward theThresholds Exceeded total, nor are they included in the minimum,maximum, or average time statistics.

Overall transaction summary reportsThis is a series of reports related to overall transaction results. A summary of eachreport follows:

Overall transaction success rate: The overall transaction success rate report is atable that displays the number of overall transactions run and the number of thosethat were successful (even if they had a performance violation, but no availabilityviolations) across all endpoints.

The percentage is calculated by adding the # successful overall transactions (a) tothe # overall transactions with performance violations (b), and dividing thatnumber by the sum of that number plus the # overall transactions with availabilityviolations (c). Written as an equation, it looks like this:

(a+b) / (a+b+c)

Overall transaction performance: The overall transaction performance report fora single endpoint is a pie chart that displays the results of all overall transactionsrun on a particular endpoint. The chart displays sections that represent successfuloverall transactions, overall transactions with performance violations, and overalltransactions with availability violations.

The overall transaction performance report for all endpoints is a pie chart thatdisplays the results of all overall transactions run on all endpoints. The chartdisplays sections that represent successful overall transactions, overall transactionswith performance violations, and overall transactions with availability violations.

Note: In cases where both performance and availability violations occur during thesame overall transaction, availability violations take precedence overperformance violations. This means that overall transactions thatencountered both types of violation are only counted in the availabilityviolation count.

Top 5 slowest: This report displays the results of the five slowest overalltransactions for a particular collected transaction. Overall transaction times areaveraged using only those overall transactions that did not encounter availabilityviolations.

Page Analyzer Viewer report: When you have enabled Page Analyzer Viewer fora Synthetic Transaction Investigator job, Page Analyzer Viewer automaticallygathers information while the Synthetic Transaction Investigator Playback job runs.


As events are generated by Synthetic Transaction Investigator, transaction detailsfor each subdocument are collected for each Web page visited. You view thesedetails using the Page Analyzer Viewer display window.

Figure 41 shows how Page Analyzer Viewer, when enabled, monitors overalltransactions at the sub document level.

In Figure 41, (1) represents the initial request by the Web server for the overalldocument. The Web server response is represented by (2). Often, (2) is composedof numerous requests and responses for sub documents (a–d) of the overalldocument, such as graphics, forms, and so on. When enabled, Page AnalyzerViewer collects data on each of these sub document transactions, which you canview through the Page Analyzer Viewer display window.

There are two ways to access the Page Analyzer Viewer display window:v Through the Page Analyzer Viewer report under Synthetic Transaction

Investigator reportsv Through the Synthetic Transaction Investigator event log

Viewing ARM correlation data through STI reportsSynthetic Transaction Investigator playback jobs that have ARM correlation enabledhave a report link that takes you to the Enterprise Transaction Performance userinterface. Here you can view the data collected for that Synthetic TransactionInvestigator job as it was processed by the WebSphere server.

To access ARM correlation data for a particular STI playback job, perform thefollowing steps:1. In the navigation tree, click Synthetic Transaction Investigator.2. Click View Synthetic Transaction Investigator Report.3. In the report name table, click Round Trip Time Graph.4. Select Job to view the report by job.5. Click Next.6. Select an endpoint from the list of endpoint names on which the chosen job

has run.7. Click Select Time Interval.

Figure 41. How Page Analyzer Viewer monitors sub document transactions


8. Use the radio buttons and drop-down lists to select a time interval or choose areal time report.

9. Click View Reports.10. In the round trip time graph, click the bar of the bar graph that represents a

run of the job for which you want to view ARM correlation.The Round Trip Statistics Table is displayed.

11. Scroll to the far right of the table to view the ARM column.Each statistic with correlating ARM data has a link in this column.

12. Click the link to access the Enterprise Transaction Performance user interface.13. Enter your user name and password for the Enterprise Transaction

Performance management server.This user name and password is not necessarily the same as your WebTransaction Performance server user name and password.

Note: The Enterprise Transaction Performance database only uploads theinformation at a minimum of 1 hour. So if you create a job that takes 5minutes to run, then immediately look at the report and try to access thisARM link, Enterprise Transaction Performance will return an error since theinformation probably has not been uploaded to the database yet.

From the command line on the Enterprise Transaction Performancemanagement server, you can force Enterprise Transaction Performance toupload the data by issuing the Enterprise Transaction Performancecommand wmarsenddata -i <endpointname> where <endpointname> is theendpoint name from which Enterprise Transaction Performance collected theARM information. Once you run the wmarsenddata command you can viewthe report.

Viewing the Page Analyzer Viewer report through the STIevent log

1. In the navigation tree, click Synthetic Transaction Investigator, then ViewEvent Log.Events in the log that have drill-down data to explore have a small icon locatedto the left of the event severity.

2. Click the icon to view the drill-down data.3. If the event triggers Page Analyzer to collect more detailed information about

the transaction, a button titled Graphical Viewer is displayed. Click theGraphical Viewer button to access the Page Analyzer Viewer display window.

Viewing the Page Analyzer Viewer report through STI reports1. In the navigation tree, click Synthetic Transaction Investigator.2. Click View Synthetic Transaction Investigator Report.3. Select a job from the list of Synthetic Transaction Investigator jobs that had PAV

enabled and click Next.4. From the drop-down list, choose and endpoint on which the chosen job ran.5. From the table of PAV applet reports, click the name of a report to view it.

The Page Analyzer Viewer display windowThe Page Analyzer Viewer display window (pictured below) displays the resultsfrom the Web screens that were initiated since Page Analyzer Viewer was last


started. The information is displayed in two side-by-side panes: the Page AnalyzerViewer Tree that displays all items in a branching hierarchical format, and the PageAnalyzer Viewer Chart that displays activities in a series of color-coded bar chartsin a time progress manner.

The line between the panes can be dragged left or right to increase or decrease therelative size of the panes. Position the cursor on the line until a double-arrow (⇔)appears, hold down the left button of your mouse, drag the line where you wantit, and release the button.

The Page Analyzer Viewer treePage Analyzer Viewer lists each Web page that was opened since Page AnalyzerViewer was started and includes information on the following:v The amount of time it took to open the pagev The number of bytes required to load the pagev The number of unique items comprising the pagev The URL of the page.

The Page Analyzer Viewer chartAs shown in Figure 2, when any of the lines in the Tree panel are selected, agraphical display of the activities comprising that page is provided in theright-hand pane. All of the bars shown are scaled and proportional to the time ittook to load the complete page, working from left to right. The bar lengthsrepresent the amount of time spent in particular activities, and the colors representdifferent activities. The overall time spent to load an individual component isrepresented by all of the colors in the same horizontal bar. Vertical overlap showsitems that were loaded in parallel by the Web browser. Clicking on one of the barswith the right-hand mouse button displays detailed time information and providesa link to an extensive set of properties for that line.

Figure 42. Page Analyzer Viewer display


Each color in the chart has a distinct meaning, as shown in the legend window(Figure 3). Note: You need not memorize these or refer to a guide when using PageAnalyzer Viewer because as you roll the mouse pointer over the colors, aninformation window is displayed telling you what the color indicates and the totaltime spent on that activity:

PurplePage Analyzer Viewer uses a purple-colored bar at the top of the display torepresent Total Request Time, which is the amount of time required to load all ofthe items on a Web page.

CyanPage Analyzer Viewer uses a cyan-colored bar to represent the Host NameResolution Time, which is the amount of time required to resolve a host name intoa valid TCP/IP address.

YellowPage Analyzer Viewer uses a yellow-colored bar to represent Connection SetupTime, which is the amount of time required to open both ends of a socket. In somecases, additional operations might need to occur before the actual page contentinformation can begin to flow to the browser. For example, when a connection isrequested to a Web site that is outside of a SOCKS server, the Connection SetupTime actually reflects the amount of time it takes to open a socket between thebrowser and the SOCKS server (not the real destination). In Figure 2, we see thisoccurring at the beginning of several of the chart lines.

RedPage Analyzer Viewer uses a red-colored bar to represent SOCKS ConnectionSetup Time, which is the amount of time required for a SOCKS-enabled firewall toopen a socket between itself and the desired Web site, plus the round trip timerequired to re-deliver the external connection request. Therefore, the end of theSOCKS Connection Setup Time signals the completion of a connection from thebrowser through the SOCKS-enabled firewall to the enabled Web site. From theperspective of the Page Analyzer Viewer, you cannot tell if long SOCKSConnection Setup Times are caused by busy SOCKS servers, long network delaysto the destination site, lost packets, or a slow destination Web server. See Figure 2for these time variances.

PinkPage Analyzer Viewer uses a pink-colored bar to represent SSL Connection SetupTime, which is the amount of time required for the browser and the Web site toprotect the privacy of information exchanged on the network. The SSL ConnectionSetup Time is the time required to negotiate an encrypted connection between theWeb site and the browser after the normal socket connection is established. Thistime reflects the generation and exchange of key information for this connection,not the time required to encrypt and decrypt subsequent information packets at theserver and browser.

BluePage Analyzer Viewer uses a blue-colored bar to represent Server Response Time,which is the amount of time required for the browser to exchange requests forpage content information with the Web server over the connected socket. TheServer Response Time begins after all of the connection setup protocols arecompleted and the complete end-to-end connection is established. This timeusually starts with a request from the browser for an item based on the user’sinteraction with the browser. The server must reply to the request with initial dataor an error code. The Server Response Time reflects the amount of time from the


browser’s request through the receipt of this initial reply. See Figure 2 for anexample of how the time can vary significantly between request items.

GreenPage Analyzer Viewer uses a green-colored bar to represent Delivery Time, whichreflects delivery of all additional data needed to fulfill the browser’s request thatcould not be sent with the initial reply because of size constraints. See Figure 2 forexamples of Delivery Time.

BrownPage Analyzer Viewer uses a brown-colored bar to represent Connection AttemptFailed, which is the amount of time required for the system to tell the browser thata socket connection returned an error. A very short Connection Attempt Failedtime indicates that the client system was already aware of a problem with theconnection and returned the error condition very quickly to the browser. WhenConnection Attempt Failed time is longer, it can be inferred that the client systemwas unaware of a problem with the connection; the remote system subsequentlyreturned the error or timed out to create the error condition.

Total Information for a LinePlacing the cursor at the left of a line opens an information window identifying thename of the item and the number of bytes. Placing the cursor at the right of a lineopens an information window showing the total time it took for that item.

The Legend windowThe Legend window, available by clicking View Legend, displays the meaning ofthe tree display icons and chart display colors used. It can be scrolled to show allicons.


Tree display iconsThe Page Analyzer Viewer Tree displays page items with the following icons(Note: If Page Analyzer Viewer cannot determine the type of page item, the icon isleft blank):

Autoproxy A SOCKS server was located using the autoproxy feature

Blank The item does not have a request or reply header

Blank Item The MIME type in the reply header is not a known type

Cached Unknown An item that cannot be classified that was retrieved fromthe Cache

Cached HTML Uncompressed HTML information that was retrieved fromthe Cache

CachedCompressedHTML

Compressed HTML information that was retrieved fromthe Cache

Figure 43. Legend window


Cached CSS Cascading Style Sheet A style sheet that was retrieved fromthe Cache

Cached Javascript Javascript that was retrieved from the Cache

Cached UnknownText

Text of an unknown type that was retrieved from theCache

Cached Java™ Java code that was retrieved from the Cache

Cached Autoproxy A SOCKS server address, found using autoproxy, that wasretrieved from the Cache

Cached UnknownApplication

MIME type starts with Application\ but the rest of thetype is not

Cached GIF A GIF picture that was retrieved from the Cache

Cached JPEG A JPEG picture that was retrieved from the Cache

Cached UnknownImage

An image of an unknown type that was retrieved from theCache

Cached Blank Item When the server asks the browser to use the cachedversion of an item that does not match a known MIMEtype or extension

CompressedHTML

HTML information in a compressed form

CSS A style sheet was retrieved to use in formatting the page

DNS Time spent converting a host name into an IP address

Failed An item that was not retrieved correctly

Flash Not used at this time.

GIF An image in GIF format was retrieved

HTML An item consisting of Hypertext Markup Language

Java An applet written in Java was retrieved

Javascript An applet written in Javascript was retrieved

Jpeg An image in JPEG format was retrieved

Mail Not used at this time.

Non HTTP Not used at this time.


Redirect A resolved IP address was redirected to another address

Unknown An item of an unknown type was retrieved

Unknown Text Text of an unknown type was retrieved.

UnknownApplication

An application of an unknown type was retrieved

Unknown Image An image of an unknown type was retrieved

Request Indicates that a request for the page has been received

Properties displaysYou can open these displays by clicking one of the lines with the right mousebutton. This displays a menu, from which you must click Properties. This opens awindow for a page or for one of the items in a page. Clicking on another lineshows the properties for that line.

Page properties

Page Properties includes five pages (tabs):

Figure 44. Page Properties display


1. Summary (as shown): A summary of the number of items, connections,resolutions, servers contacted, total bytes sent and received, fastest responsetime (Server Response Time Low), slowest response time (Server ResponseTime High), and the ratio between them (used to evaluate connections)

2. Sizes: The total sizes in bytes sent and received, and the percentage of overheadfor the page

3. Events: A detailed listing of all events that occurred in creating the page4. Stats: A detailed listing of the duration values for connections5. Comments: An area for comments.

Item Properties

Item Properties includes six pages (tabs):1. Summary (as shown): A summary including the URI, content type, total bytes,

a breakdown of the connect time for all activities related to this item, the SocketID, and the IP address, if appropriate

2. Headers: A detailed description (characteristics) of each HTTP header, ifappropriate

3. Sizes: A detailed list of bytes sent and received in retrieving the item4. Timing: The exact date & time for all activities required to retrieve the item5. Events: A detailed chronological listing of the events required to retrieve the

item6. Comments: An area for user comments

Figure 45. Item Properties display


Chapter 6. General System Administration

The Web Transaction Performance GUI enables you to perform a number of tasksrelated to all of the applications. These general system administration functions areaccessible through the navigation tree.

The four major task categories are as follows:

Historical Data CollectionThis is where you go to set up the job that collects data from the endpointsand places it in the data warehouse for use by TDS or other externalreporting tools. This is also where you can view the log of events relatedspecifically to historical data collection.

Global ViewsFunctions in this category are generally accessible to all users, regardless ofthe authorizations granted in Managing accounts. This expandablecategory includes the following functions:v Manage jobs (from all applications)v View global event log (a log of all events from the Internet Management

Server, the endpoints registered to it, and all of the jobs for thoseendpoints)

v View all endpoints

System AdministrationFunctions in this category require authorization to perform administrativefunctions. This expandable category includes the following functions:v Configure Event Severitiesv Configure System Eventsv View System Event Logv Create Event Responsesv Archive Offline Endpointsv Manage Datav Manage Accountsv View Log Filesv View TIMS Details

User PreferencesFunctions in this category enable any user to modify account preferencesthat are applicable to their own user account. This expandable categoryincludes the following functions:v Change Password.v Change Time Zone.

Historical data collectionThis section describes how to configure historical data collection jobs and how toview the historical data collection logs.

89

Configuring an historical data collection jobWeb Transaction Performance applications gather information for loading into adata warehouse. Collection is performed by the Web Services Courier (WSC). Thedata is then used by Tivoli Decision Support software to create reports about thedata.

From the Web Transaction Performance GUI, you can configure the Tivoli WebServices Courier to collect data using the following procedure:1. Click Historical Data Collection to expand the list.2. Click Configure Data Collection.3. Select an endpoint from the Endpoint Name drop-down list.4. Type a time to begin data collection in the Begin Collection drop-down list.5. Remove the check from the Disable check box.6. Click Save.

Note: Failure to configure and enable historical data collection before you createapplication jobs will limit your application reporting capabilities to real-timeonly. Historical data will not be saved to the data warehouse, therebymaking it impossible to create historical reports. The Disable box is checkedby default so that data collection does not begin before you have configureda collection time.

Viewing the historical data collection event logYou can view historical data collection events by performing the following steps:1. From the navigation tree, click Historical Data Collection.2. Click View Event Log.

Global viewsUser accounts that include the System role can view all endpoints, event logs, andscheduled and completed jobs. Because user accounts with this role can makeglobal changes from these special views, the views are referred to as Global Views.

Managing jobsTo view all Quality of Service, Site Investigator, and Synthetic TransactionInvestigator jobs, perform the following procedure:1. From the navigation tree, click Global Views, then click Manage Jobs. A table

of jobs is displayed.


Viewing the global event logThe global event log displays all events generated by the Internet ManagementServer and all of the Web Transaction Performance applications. It is a real-time logand provides complete information about each event that is logged.

To view the global event log, click Global Views → View Global Event Log.

Note that you can determine the maximum number of events that are displayed inthe log by entering a value in the Maximum Number of Events Retrieved field atthe bottom of the log. In addition, you can sort the log by category by clicking on


any of the column headings. Clicking on the heading again reverses the order ofthe column entries.

Viewing all endpointsIf you want to determine whether or not all of the endpoints in your WebTransaction Performance installation are installed and available, you can view themfrom Global Views → View All Endpoints.

From the navigation tree, click Global Views, then click View All Endpoints. Theavailable endpoints are displayed in a table that includes the endpoint name andits description, endpoint type, hostname, and installation date. In the secondcolumn of the View All Endpoints table, there is a check box labeled HeartbeatEvent. A heartbeat event is an event that indicates the endpoint is not functional(the heartbeat is missing). Checking this box enables heartbeat missing events foran endpoint. For example, if this box is checked and a system is powered down orotherwise fails, a heartbeat missing event is recorded. Removing the check fromthis box disables heartbeat missing events. When an endpoint is installed,heartbeat missing events are enabled.

Chapter 6. General System Administration 91

System administrationThe Web Transaction Performance GUI enables you to perform a number of systemadministration functions. You access to these functions by clicking SystemAdministration.

Configuring event severitiesThis table enables you to configure event severities of events generated by theInternet Management Server without having to search through the individualapplications for each event. To change the severity of any event in the table, usethe drop-down list next to the event name to select the new severity, and click theCreate/Modify button.

Configuring system eventsYou can configure events for each application. You can also configure systemevents that are common in all applications under System Administration. Systemevents are listed in the following table. See “Configuring events” on page 112 for acomplete explanation of how to configure events.

System Event Types

Type Definition

Job Start Succeeded A scheduled job started successfully.

Job Start Failed A scheduled job failed to start.

Job Executed Caused Fatal Exception A scheduled job caused a fatal exceptionwhen it was run.

Job Stop Completed A scheduled job has run successfully to thecompletion of its schedule.

Job Abort Succeeded A job abort request succeeded.

Endpoint Uninstalled An endpoint has been uninstalled.

Heartbeat Missing The heartbeat has been missing from anendpoint for a number of minutes. Thisevent is generated if the management serverhas not received a heartbeat signal from theendpoint for a specified period of time (inminutes).

Authorization Failure The management server failed to authorize aclient request. Events of this type aregenerated when an invalid password isspecified, a user lacks permission to use therequested service, or if any otherauthorization request is invalid.

Authorization Service Succeeded The authorization or authenticationsucceeded. Events of this type are generated,for example, when a user is successfullycreated or if a management server isdefined.

Authorization Service Failed The authorization or authentication servicefailed. Events of this type are generated forexample, when an invalid password isspecified or if an attempt is made to delete auser.


System Event Types

Type Definition

Server Authentication Failed Authentication failed while defining aforeign management server (server-to-servercommunication).

Mail Service Failed The STMP service failed to start up due toan exception. This event is generated whenan internal error occurs or if the servicefinds an environmental or resourceconstraint while starting.

SNMP Service Failed The SNMP service failed to start up due toan exception. This event is generated whenan internal error occurs or if the servicefinds an environmental or resourceconstraint while starting.

Tivoli Enterprise Console Service Failed The Tivoli Enterprise Console forwardingservice (also known as the event handler)did not start or stop when the managementserver was started.

EXEC Service Failed The EXEC service failed to start up due toan exception. This event is generated whenan internal error occurs or if the servicefinds an environmental or resourceconstraint while starting.

Endpoint Installed A new endpoint has been installed andregistered with the management server.

EXEC Status Failed The user-supplied script or program ran andreturned a non-zero (error) status code. Thisevent is generated when the service runs auser-supplied script or program that returnsan error code.

EXEC Failed The user-supplied script or program failedto execute. This event is generated when theservice unsuccessfully attempts to run auser-supplied script or program.

Unknown Endpoint The management server has received a pingfrom an endpoint not registered to thatmanagement server.

Event Forwarded to Tivoli EnterpriseConsole Missing Data

Certain fields in the event forwarded to TECare missing information. This is an internalerror. TEC will not reject the event.

EXEC Complete User-supplied script or program completedsuccessfully.

Generic Event This is a generic event for general use.

Event Subsystem Exception The subsystem failed to generate an event.Turn on event tracing in theeven.properties file or contact IBMCustomer Support for Tivoli Software.

Endpoint Started Auto-Update Process An endpoint has started an auto-updateprocess.

Endpoint Auto-Update Process Succeeded An endpoint auto-update process hascompleted successfully.


System Event Types

Type Definition

Endpoint Auto-Update Process Failed An endpoint auto-update process has faileddue to an error.

Heartbeat No Long Missing Recovery: Heartbeat no long missing fromendpoint.

Endpoint Pinger Service Failed to Start An endoint pinger failed to start when theendpoint was started.

Event Annotation Incomplete The annotation portion of an event did notcompletely generate when an event occured.

To configure Web Transaction Performance system events, complete these steps:1. On the navigation tree, click System Administration.2. Click Configure System Events.3. Click the arrow to view the Event Type drop-down list.4. Select the event type you want to configure.5. Click the arrow to view the Event Severity drop-down list.6. Select the severity level you want to assign to the event.7. Click the arrow to view the Event Response drop-down list.8. Select the event response you want to associate with the event type. If you

require a response action not in the list, see “Creating event responses” onpage 106.

9. Click Add to Table. The Event Table displays system event types. Using theradio buttons below the table, you can display all event types or only a selectedevent type. You can also delete configured events by selecting each one’s checkbox in the table and then clicking Delete.

Viewing the system event logThe system event log is a real-time log that displays all events generated by theInternet Management Server. The system event log provides complete informationabout each event that is logged.

To view the system event log, click on System Administration and then ViewSystem Event Log.

Note that you can determine the maximum number of events that are displayed inthe log by entering a value in the Maximum Number of Events Retrieved field atthe bottom of the log. In addition, you can sort the log by category by clicking onany of the column headings. Clicking on the heading again reverses the order ofthe column entries.

Creating event responsesThe Internet Management Server (IMS) and the Web Transaction Performance tasksgenerate events that are stored in the management repository. By creating eventresponses, you can configure events to be forwarded to one of several destinationconsoles using one of the following event handlers on the management server:v The system log, through the log file handlerv One or more e-mail addresses, through the Simple Mail Transfer Protocol

(SMTP) handler


v A Simple Network Management Protocol (SNMP) management application,through the SNMP handler

v The Tivoli Enterprise Console (TEC) through the TEC handler and the WebServices Courier (WSC) endpoint

v A program that runs a customer-supplied script in response to the event,through the EXEC handler

You can select any of the responses for an event, but only the e-mail forwardingand EXEC options are configurable.

For a complete discussion of how to create event responses, see Chapter 8,“Managing events and event responses” on page 105.

Archiving Offline EndpointsArchiving an endpoint removes that endpoint from the list of installed endpointsregistered to an Internet Management Server. Any jobs associated with thearchived endpoint are automatically changed to the incomplete state.

Managing application dataCertain data in the management repository is expected to collect over time, therebyrequiring that you manage it. This data includes events, management data that isuploaded by Web Transaction Performance applications, and data generated byjobs. However, Web Transaction Performance does not monitor the managementrepository for space utilization and thresholds. It is your responsibility to monitorthe health of the management repository and to regularly purge events, unneededcollections, jobs, and so on.

How often you need to purge data depends upon the size of the database. Consultyour database administrator if you unfamiliar with database maintenance. Failureto monitor and maintain the management repository could result in the InternetManagement Server becoming unusable or ineffective because it cannot write tothe database.

To perform data management tasks using the GUI, use the following procedure:1. In the navigation tree, click System Administration.2. Click Manage Data.3. Mark the check box of the application or report category from which you want

to purge data. You can make more than one selection.4. Select the end date for the data purge.5. Click Delete All Before. All data collected before this date will be deleted by

this action.

This feature replaces the ims_purgedb utility that was part of earlier releases of theproduct.

Managing accountsThe Manage Accounts screen is used to grant or deny administrative privileges tousers. It is also used to add new user accounts or delete user accounts that are nolonger needed.

To perform any of these tasks, use the following procedure:1. Click System Administration.


2. Click Manage Accounts.

3. To add a user, type the required information in the Add Account table and clickAdd Account.

Note: By default, a new user is automatically given permission to access allfunctions. If you make any changes to the default settings, however, thenew settings do not become effective until the Modify Selected Accountsbutton is clicked. To restrict a user to a subset of administrativefunctions, see Step 5.

4. To delete a user, select the entry you wish to delete from the Delete Accountstable and click Delete Account.

5. To modify the applications, monitors, and navigation tree links that an existinguser is authorized to access, perform the following steps:v Select the ID of the user to modify by clicking in the box to the left of the

name of a user. A check mark in the box indicates the user ID has beenselected. Any modifications made in the Modify Administrative Roles forAccounts table will apply to all user IDs that are checked when you click theModify Selected Accounts button.

v Select the functions the selected user ID is allowed to access by clicking inthe box below an application name. A check mark in an application box


indicates the selected user ID can access links in the navigation tree area ofthe GUI to administer the application. Applications include QoS, SI, STIP,STIR, WCM, and Data Collection. For each application, there is acorresponding View selection, for example, QoS (View). Checking a Viewselection grants the user the authority to view application settings, but notchange them. Selecting the System box grants the selected user IDpermission to perform administrative functions accessible under the SystemAdministration link in the navigation tree.

v Click Modify Selected Accounts to apply the changes. If a selected user iscurrently logged on, any changes made do not take effect until the next timethe user logs on to the system.

Viewing log filesYou can view the management server log files (for example, timsui1.log) from theGUI:1. In the navigation tree, click System Administration.2. Click View Log Files.3. Click the log’s file name to begin viewing.

See “User Interface Logging” on page 129 for information about log file settings.

Viewing TIMS detailsYou can verify which of the Web Transaction Performance applications arecurrently enabled for your system from the GUI. In the navigation tree, clickSystem Administration and then click View TIMS Details. (TIMS stands for TivoliInternet Management Server.)

User preferencesAny user can change some personal preferences for their own account. Preferencesyou can set include the password associated with the user’s account, and the timezone shown for time stamps in the user interface.

Changing passwordsTo change your logon password, use the following procedure:1. Click User Preferences.2. Click Change Password.3. Type the old (current) password, type the new password, then re-type the new

password to confirm.4. Click Change Password.

Changing the time zoneTo change the time zone displayed in the user interface, use the followingprocedure:1. From the navigation tree, click User Preferences.2. Click Change Time Zone.


3. From the drop down list of time zones, select the time zone you wish to usewhen viewing the user interface.

4. To make the selected time zone the default time zone for event log views,endpoint views, and reports, click Change Time Zone.

Note: The time zone default only applies to the user account in which you arecurrently logged.


Chapter 7. Tivoli Decision Support Guide for Web TransactionPerformance

After the system completes a Historical Data Collection, you need to be able toeasily create reports and graphs of that data to look for trends and trouble spots.That is what the Tivoli Decision Support Guide for Web Transaction Performancehelps you to do.

After the data has been collected, it can be assembled in a special type of relationaldatabase called the Tivoli Web Data Warehouse. Tivoli Decision Support can thenextract and analyze the data by means of reports that are displayed in the TivoliDiscovery Interface.

Use Tivoli Discovery Administrator to define queries that extract data from thisdatabase into a comma-separated values (CSV) file. The Cognos Transformer buildsthe multidimensional cubes from this file, which can then be reported by CognosPowerPlay. A cube is a data container used by Cognos PowerPlay. PowerPlay is amultidimensional reporting and analysis package that you must install with TivoliDecision Support. A number of PowerPlay tools are embedded in Tivoli DecisionSupport. Before Tivoli Decision Support can operate properly, you must ensure thatthe Discovery Administrator is properly linked to the databases in yourorganization. Finally, use the Tivoli Discovery Interface to view these reports.

Building cubesCube building is a resource-intensive activity. Thus, while you should scheduleregular cube builds, schedule them during periods of decreased database activity.Adjust your cube date range to optimize the time required to build a cube.Perform this task through the Administrator panel of the Tivoli DiscoveryAdministrator console. Follow these steps to build a cube:1. Double-click Cubes on the Administrator panel.2. Right-click a cube, and then select Build. The Confirm Cube Build dialog

displays the date ranges.3. Click Yes.

Tivoli Decision Support connects to your database and retrieves the recordsspecified in your query. The size of your data and the network speed affect thetime required to retrieve all records. Use the status bar to check the status ofthe processing. The Cube Transform Status dialog displays processingmessages.

4. Review the processing messages for any errors. If an error generates an errordialog, review the error, and then click OK.

5. Click Close.

For more information about how to use the Tivoli Decision Support DiscoveryInterface, see the Tivoli Decision Support Users Guide, and Tivoli Decision Support:Using Decision Support Guides.

99

Scheduling the cube build taskYou must periodically rebuild the cube to update your cube data. The buildprocess can be scheduled to build automatically at regular intervals (for example,schedule nightly cube builds). Stagger the start times for your cube builds forimproved performance. Also, make sure the cube builds are scheduled after theHistorical Data Collection job completes, since this collection job must finish inorder to have updated data for the cubes.

The following procedure uses the Tivoli Discovery Administrator to create a cubebuilding schedule and to determine the schedule TaskID. The cube build is thenscheduled using the Cognos Scheduler. Use the following procedure to define acube building schedule:1. Start the Tivoli Discovery Administrator.2. Select Add → Cube Build from the Scheduled Task menu to display the Add

Schedule task guide.3. Type a name for the schedule you are creating in the Schedule Name box, and

then click Next.4. From the drop-down list, choose the cube for which this build is scheduled

and click Next.5. Choose how often you want to do this task, and click Next.6. Choose an interval of days to do this task, and click Next.7. Choose a time to start the this task.

Note: Ensure that the start time of this cube build occurs after the completionof the Web Transaction Performance Historical Data Collection job. Ifthe cube starts to build while data is still being collected, the datawithin the cube might be corrupted or inaccurate.

8. Click Next.9. In the Effective From date box, type or select a date that is prior to the

current date.10. Select the To check box to display the ending date box.11. In the Ending Date box, type or select the date that you want the schedule to

end, and then click Next.12. Click Finish.13. Click Scheduled Tasks in the Tivoli Discovery Administrator panel to display

the Properties panel.14. Right click the scheduled task you created, and then click Edit to display the

Edit Schedule dialog.15. On the Task tab, record the Schedule Task ID (used in a later step), and then

click OK.16. In the Windows NT Start Menu, click Programs.17. Click Cognos.18. Click Scheduler.19. From the Insert menu, select Recurring Task to display the Insert Task

dialog.20. Click the Identification tab, and then type the following command string in

the File Name box:<directory path>\EDAdmin.exe /TaskID=X


where <directory path> is the installation directory path for Tivoli DecisionSupport and X is the Schedule Task ID. You must enclose the directory pathand EDAdmin.exe in quotes as shown in the following example:c:\Program Files\TDS\EDAdmin.exe /TaskID=1

21. Type a brief description of the cube and the schedule in the Description box.22. Click the Timetable tab, and specify the cube building frequency, run time,

and span of calendar dates to run.23. Minimize Cognos Scheduler.

Note: Cognos Scheduler must be running for the cube to build at thescheduled time. Add the Cognos Scheduler to the startup folder of theTivoli Decision Support server.

Topics and viewsOn the Tivoli Discovery Interface, the data collected for the Guide for WebTransaction Performance is organized into topics and views. Selecting a viewwithin a topic displays a report showing the results of a database query based onthe topic and view selected. In addition to the report itself, each view displays aview description in the Hints panel at the bottom of the interface.

Data displayed in these reports can, in most cases, be further explored by drillingdown or up through the various levels of data aggregation that make up thereport. You can drill down through the data either by double-clicking an object inthe report, such as a bar in a bar graph or a section of a pie chart, or by choosingdifferent dimensions from the series of different dimension drop-down lists abovethe report. If the dimension line is not visible, select View → Dimension Line fromthe Tivoli Discovery Interface main menu while viewing a report.

The Guide for Web Transaction Performance provides the following topics andviews:

Topic: How is user response time being affected by Web site traffic?

Views: The views in this topic use information from the Quality of Serviceendpoint and IBM WebSphere Site Analyzer 4.0 Web loginformation. These views enable you to see how the load on yourWeb server is affecting the end user experience. These reports areCrystal Reports that use the WebSphere Site Analyzer 4.0 datastore as the source for the number of hits, kilobytes downloaded,and pageview metrics:

v User response time correlated by kilobytes downloaded andnumber of hits

v User response time correlated with pageviews for a given URI

Tivoli Decision Support retrieves information from the Web datawarehouse for reporting purposes. To run these new reports, yourWebSphere Site Analyzer data must be in the same database as theWeb data warehouse. If you are setting up WebSphere SiteAnalyzer, refer to that product documentation on how to configureyour database. Otherwise, you need to import the data manually.Consult your database administrator for instructions on importingdata.

Topic: What pages do not follow site guidelines?

Chapter 7. Tivoli Decision Support Guide for Web Transaction Performance 101

Views: These reports summarize the results of Web site investigationsperformed by Site Investigator on your Web site. These reportsenable you to see if your Web site is delivering the rightinformation, and if that information is delivered within the timestated in your service level agreement.

v Site Investigator Response Code Violation Details

v Site Investigator Response Code Violations

v Site Investigator Violation Trends

v Site Investigator Violations Summary

Topic: What quality of service are we providing?

Views: These reports show you what kind of experience you are providingyour customers, and help you target those areas that fail to meetyour expectations for customer experience.

v Quality of Service Customer Experience

v Quality of Service Exceptions

v Quality of Service Violations - Backend Service Time

v Quality of Service Violations - Page Render Time

v Quality of Service Violations Summary

v STI Transaction Availability

v STI Trends

Topic: Where is our quality of service impacted?

Views: These reports give you a quick view of where your site might notbe providing the level of service you require:

v Quality of Service Events

v Quality of Service Slowest Web Pages

v Site Investigator Events

v STI Availability

v STI Slowest Sub Transactions

v STI Transaction Failures

v STI Violations

Tivoli Decision Support problem determinationThis section includes the following topics:v Solving Cube Building Problemsv Solving Report Problems

Solving cube building problemsCube building has the following problems and possible solutions:v What do I do when the Tivoli Discovery Administrator message appears:

Error building cube.

and the Details information includes:Error 91 - Error getting query parameters;object variable or with block variable not set.

The data sources have not been assigned to the cube queries. Assign the datasources to the queries.


v During use of the Tivoli Discovery Interface, what does it mean when aCognos PowerPlay report icon appears with a Cannot Execute indicator, andreport cannot be opened?

The cube is unavailable. Contact the Tivoli Decision Support administrator andrequest that the cube be built.

v Why does the Tivoli Discovery Administrator report that a cube could not bebuilt?

The cube you are attempting to rebuild is currently in use, and Tivoli DecisionSupport cannot overwrite this cube with the new cube data. Close all copies ofthe Tivoli Discovery Interface that are running. Copy the CubeName.mdc filefrom the Tds\Cubes\Temp directory to the Tds\cubes directory, where Tds isthe Tivoli Decision Support installation directory.The queries returned insufficient data to build a cube. Verify your queries.

v If all the Tivoli Discovery Interface processes are closed, why doesn’t the cubebuild?

A copy of Cognos PowerPlay might still be running in the background. This canalso prevent cube builds from succeeding. Open the Task manager. If you findthe process pplay.exe, end the process and rebuild the cube.

v Why don’t the cubes build automatically overnight?

For scheduled cube builds to occur, the Cognos Scheduler must be running. Startthe Cognos Scheduler. Review the schedule definitions in the Cognos Schedulerand in the Tivoli Discovery Administrator.

v How are relative dates calculated in a report?

The Date Range parameter for a cube determines the time period that you wantto examine. This parameter uses explicit values, start and end dates, or acalculated value such as the last three months. The calculated values are relativeto the current date. Use the Date Range parameter and the CubeName_dt.txt toset the current period in the following cases:– Explicit Date Range

End dateCalculated Values

Calculated end dateNo Date Range parameter in cube

Date the cube is built– If you want to use the date in the CubeName_dt.txt as the current period,

create a new query in the cube model. This query must use theCubeName_dt.txt as a local data file. Also the set the current period optionmust be set only for this query.

– Use the Date Range parameter, but do not use the CubeName_dt.txt. Thisselects only records between the specific start date and end date, and sets thecurrent period to the most recent date in the data.

– Do not use either the Date Range parameter or the CubeName_dt.txt. Thisselects all the records, and sets the current period to the most recent date inthe data.

– Use the CubeName_dt.txt, but do not use the Date Range parameter. Thisselects all the records, and sets the current period to the date of the currentcube build.

For more information about how to set the current period and select records, referto the Tivoli Decision Support Administrator Guide.

Chapter 7. Tivoli Decision Support Guide for Web Transaction Performance 103

Solving report problemsThe following problems can occur:v What should I do when the following error message appears?

load_graph_from_powercube

The cube has not been built. Build the cube.v I tried to open a report, but the Tivoli Discovery Interface gets stuck at the

wait cursor.

The Tivoli Discovery Interface might have lost its connection to the CognosPowerPlay task. Close the Tivoli Discovery Interface and Cognos PowerPlay.Restart the Tivoli Discovery Interface and open the reports again.

v I opened a report, but it contained no data.

There might be data in the report, but there is no data in the drill-down. Thereport might be filtered on a dimension. Look at the dimension bar and check ifany of the values, especially the date dimension, are drilled down.For Crystal reports, you must specify a parameter. See the hint text at thebottom of the Tivoli Discovery Interface for information about entering theparameter.

v The tabular reports do not have a left margin.

The type of printer attached to a workstation influences the alignment of thereports. Try disconnecting the printer and restarting Tivoli Decision Support.

v I cannot open a Crystal report using the Tivoli Discovery Interface.

You might be addressing the wrong database. On the Tivoli Discovery Interfacetask bar, click View -> Options. On the Options dialog, examine the Databasetab to verify that the Data Source Settings section properly defines the DSN,Qualifier, Database Name, and Type fields.


Chapter 8. Managing events and event responses

The Web Transaction Performance applications and the Internet ManagementServer generate events. An event can be any warning, error message, or statusmessage. Application events are typically generated when application constraints areexceeded, which usually occurs during the execution of a job. System events aretypically generated by authentication problems, event handler failures, or endpointcommunication problems. The events generated by Web Transaction Performanceare stored in the management repository.

An event response is the preconfigured action that is initiated when an event isgenerated. You can configure five response options for any event. These optionsenable you to forward each event to one or more of the following destinationsusing one of the event handlers on the management server:v Management Server event log, through the log handlerv One or more e-mail addresses, through the Simple Mail Transfer Protocol

(SMTP) handlerv Scripts that initiate an action, such as a remedial response to an event, through

the EXEC handlerv To Tivoli Enterprise Console through the Tivoli Enterprise Console event handlerv One or more network management systems through the Simple Network

Management Protocol (SNMP) handler

By forwarding events, you can ensure that the appropriate people are notified ofeach type of event.

Each application, including the management server, has a unique set of eventtypes. You can configure any event by assigning a severity (priority) level and anevent response. There are six event severity levels:v Unknownv Harmlessv Warningv Errorv Criticalv Fatal

By default, all application events are assigned a severity level of warning and arelogged (the event response). System events are also logged, by default.

Configure event responses before you configure events, and complete both tasksbefore you begin using the Web Transaction Performance applications. Creatingevent responses first makes all the response options available when you configurethe events. Configuring events before you begin creating jobs with the applicationsensures that you do not lose any event information when the jobs begin to run.

105

Creating event responsesCreate event responses before you configure events. Complete both activities beforeyou begin using the Web Transaction Performance applications. Creating eventresponses first makes all the response options available when you configure theevents. Configuring events before you begin creating jobs with the applicationsensures that you do not lose any event information when the jobs begin to run.

The five event response types are configured in different ways:v Sending event information to the application and system logs is the default. All

events are logged; no further configuration is required for this action.v Forwarding events to the Tivoli Enterprise Console requires an installed Tivoli

Enterprise Console enabled endpoint.v Forwarding events to SNMP applications is done by configuring the

management server.v Forwarding events to e-mail accounts and to the EXEC handler is done through

the Create Event Responses view under System Administration. However, thee-mail option requires that you also configure the management server first.

The e-mail option is displayed after you configure the management server andcreate an e-mail event response. The EXEC option is displayed after you create ascript execution event response.

Forwarding events to the Tivoli Enterprise ConsoleYou can configure events to be forwarded to the Tivoli Enterprise Console (TEC).The Tivoli Enterprise Console event handler translates an event from InternetManagement Server format to Tivoli Enterprise Console format. The formattedevent is queued on the management server. The Tivoli Web Services Courierendpoint, with Tivoli Enterprise Console forwarding enabled, polls themanagement server every 60 seconds for Tivoli Enterprise Console events.Whenever there are any in the queue, they are forwarded to Tivoli EnterpriseConsole.

In order for the Internet Management Server to forward events to a TivoliEnterprise Console server, you must install the Tivoli Web Services Courier (WSC)endpoint according to the instructions in your installation guide so that thisfowarding is enabled.

To configure system events for Tivoli Enterprise Console forwarding, complete thefollowing steps:1. On the navigation tree, click System Administration.


2. Click Configure System Events.

3. For each event type that you want forwarded to an Tivoli Enterprise Consoleapplication:a. Click the arrow on the right of the Event Type drop-down list. Select an

event type.b. Click the arrow on the right of the Event Severity drop-down list. Select an

event severity.c. Click the arrow on the right of the Event Response drop-down list. Select

TEC Forwarding.4. Continue this procedure until you have configured all Tivoli Enterprise Console

forwarding events.

Forwarding events to an SNMP management applicationYou can configure events to be forwarded to a Simple Network ManagementProtocol (SNMP) management application such as Tivoli NetView. The SNMPhandler creates a message from event data, then creates and sends an SNMP trap.

To forward Web Transaction Performance events to an SNMP managementapplication, you must have an SNMP management application installed. Contactthat application’s administrator before forwarding events to the SNMPmanagement application. You must also configure the management server forSNMP forwarding before configuring events by using the following procedure:1. Edit the snmp.properties file in your

baseinstalldirectory/ManagementServer/TIMS/lib/properties directory toinclude your SNMP server information in the following section of thesnmp.properties file:#######################################################"# Location (IP address or hostname) of SNMP management platform.# e.g. snmp.yourdot.comServerLocation=

# SNMP management platform incoming SNMP trap port number.# e.g. default port is 162ServerPort=##########################################################

2. Save your changes and close the editor.

To configure system events to be forwarded to an SNMP management application,complete the following steps from the Web Transaction Performance GUI.1. On the navigation tree, click System Administration.

Chapter 8. Managing events and event responses 107

2. Click Configure System Events.

3. For each event type that you want forwarded to an SNMP application:a. Click the arrow on the right of the Event Type drop-down list. Select an

event type.b. Click the arrow on the right of the Event Severity drop-down list. Select an

event severity.c. Click the arrow on the right of the Event Response drop-down list. Select

SNMP Trap.

Forwarding events to an e-mail accountYou can configure the event service to forward events to one or more e-mailaddresses, using the Simple Mail Transfer Protocol (SMTP) handler. Use the SMTPforwarding feature to ensure that the appropriate individuals are notified for eachtype of event generated. Automatic e-mail notification is a simple and efficient wayto communicate that an issue needs attention. The e-mail forwarding option alsoforwards notification to pagers and hand-held devices if the receiving devices areconfigured properly

Before you can forward events using email, you must first modify theevent.properties file on the managment server to include the necessary SMTPsystem information. To do this, use the following procedure:1. Edit the event.properties file in your

baseinstalldirectory/ManagementServer/TIMS/lib/properties directory toinclude your SMTP server information in the following section of theevent.properties file:############################################################ SMTP (mail) hostname, e.g. mail.yourdot.commail.smtp.host=# If a socks proxy exists between your TIMS and your SMTP server# socksProxyHost, SOCKS firewall host, e.g. socks.yourdot.comsocksProxyHost=

# socksProxyPort, e.g. default SOCKS port is 1080socksProxyPort=################################################

where mail.smtp.host is the hostname of your mail server.2. Save your changes and close the editor.


You can forward event notification using e-mail to individuals or groups. Toforward all events of a particular type to e-mail addresses, complete the followingsteps from the Web Transaction Performance GUI:1. Click System Administration.2. Click Create Event Responses.3. Select Send E-mail from the event response type from the drop-down list. Click

Next.

4. To create a new recipient, type a name and description (optional). The namecan be of a single individual, or it can be the name of a group of individualswho will each receive notification of the event. Type an address and click Add.Repeat the process until you have entered all the necessary recipients. ClickCreate/Modify.

5. To modify an existing e-mail event response:a. Select the e-mail response name from the drop-down list on the Create

E-mail Event Response view.b. Click Populate to view the details.c. Modify the response:

v Select existing entries and remove them by clicking Remove- OR -v Add new entries and click Add.

d. When you have finished, click Create/Modify to change the response.

All new events of the specified type are sent to the e-mail addresses specified.

Forwarding events to the EXEC serviceYou can configure the event service to forward events to the EXEC service wherereceipt of the event runs one or more user-created programs. You can use theEXEC forwarding feature to initiate remedial actions instead of, or in addition to,human intervention.

Note: Any scripts used by the EXEC service must be placed in the TIMS/scriptsdirectory. Any stdout and stderr from any scripts run by the EXEC serviceare placed in the TIMS/scriptlogs directory.

To forward all events of a particular type to the EXEC service, complete thefollowing steps:1. From the navigation tree, click System Administration.2. Click Create Event Responses.3. Select Run a Script from the Event Response Type from the drop-down list.

Click Next.


4. To create a new response:a. Type a name (required) and description (optional).

b. Provide the command path, error path, and output path for the script youwant to run.

c. Click Create/Modify.5. To modify an existing script execution event response:

a. Select the script response name from the drop-down list on the CreateScript Execution Event Response view.

b. Click Populate to view the details.c. Modify the response by selecting entries and removing them by clicking

Remove or by adding new entries and clicking Add.d. When you have finished, click Create/Modify to change the response.

All new events of the specified type will initiate the specified script.

Forwarding event data using the EXEC serviceThe EXEC service passes event field value data to the executing program or scriptyou have configured via command line arguments. The arguments use aname-value pair format, in which the value is always enclosed in double quotes.The syntax is shown in the following table.

Command Argument Syntax

1 event_id=”event_id_value”

2 event_priority=”event_priority_value”

3 endpointID=”endpointID_value”

4 endpointName=”endpointName_value”

5 eventSource=”eventSource_value”

6 eventTime=”eventTime_value”

7 recordID=”recordID_value”


Command Argument Syntax

8 constraintID=”constraintID_value”

9 annotation=”annotation_value”

The syntax works on the UNIX platform and most environments on Windows NT.However, if you create a *.cmd or *.bat script, the cmd.exe for Windows NT willnot receive the arguments properly and will return only the name portion of thepair. To remedy this, use the pattern in the following example script:@echo offecho Example Script!echo Param 1 = %1echo Param 2 = %2echo Param 3 = %3echo Param 4 = %4echo Param 5 = %5echo Param 6 = %6echo Param 7 = %7echo Param 8 = %8echo Param 9 = %9shift /8echo Param 10 = %9shift /8echo Param 11 = %9shift /8echo Param 12 = %9shift /8echo Param 13 = %9shift /8echo Param 14 = %9shift /8echo Param 15 = %9shift /8echo Param 16 = %9shift /8echo Param 17 = %9shift /8echo Param 18 = %9

The output presents the name-value information in a different format:Example ScriptParam 1 = eventIDParam 2 = “<value>”Param 3 = eventPriorityParam 4 = “<value>”Param 5 = endpointIDParam 6 = “<value>”Param 7 = endpointNameParam 8 = “<value>”Param 9 = eventSourceParam 10 = “<value>”Param 11 = eventTimeParam 12 = “<value>”Param 13 = recordIDParam 14 = “<value>”Param 15 = constraintIDParam 16 = “<value>”Param 17 = annotationParam 18 = “<value>”


Configuring eventsEach application has a unique set of event types, as does the management server(system events). Tables listing all the event types are provided at the end of thischapter in “Event severity”.

You can configure any event (with the exception that system event type severitylevels cannot be changed), and you can configure each event multiple times. Thisenables you to tailor who is informed or what actions are taken, based on thesource or severity (priority) of the event. Configuring an event is the process ofassociating an event type and a severity level with an event response. See“Creating event responses” on page 106 and “Event severity”. The event responseis triggered when an event of the specified type and priority (or one of a specifiedtype and a higher priority) is received by the management server.

To configure a system event, complete the following steps:1. From the navigation tree, click System Administration → Configure System

Events.2. Select an event type from the Event Type drop-down list.3. Select an event response from the Event Response drop-down list. If the

desired response is not on the list, see “Creating event responses” on page 106.Select a severity level from the Event Severity drop-down list.

4. Click Add to Table. The Event Table displays system event types. Using theradio buttons below the table, you can display all system event types or only aselected event type. You also have the option of deleting any configured events,except those configured with the system defaults. Select the events you wish todelete and click Delete checked.

5. Configuration is applied immediately, so when you have finished configuring,you can move on to your next task

You can configure events from each application’s Configure Events view by usingthis procedure.

Event severityWhen you configure events, you associate a severity, or priority, level for eachevent type, and an event response. The severity levels are as follows:v Unknownv Harmlessv Warningv Errorv Criticalv Fatal

You can configure a given event type multiple times, each time changing theseverity and the event response. This enables you to generate different responsesbased on the source and significance of the event. An event type, configuredmultiple times, can generate multiple responses. For example, if, for a particularevent, you assign a severity of Error and an event response of sending an e-mail toyourself, any instance of that event with a severity level of Error causes anotification to be sent to your e-mail address and logs the event, since logging isthe default response for all events.


An event generates its configured response, the default response, and any otherconfigured responses of lower severity for that event type. For example, assumeyou are using Site Investigator to search for outdated content (for example,discontinued products or programs) on your Web site, on both the public pagesand the pages under construction. You configure the Undesired Content Foundevent twice: once with a severity of Error and a response of forwarding notificationto an SNMP application in your lab; the second time with a severity of Critical anda response that sends an e-mail to the Information Services vice-president.

When you create an Site Investigator job to search Web pages under construction,you choose the event type with Error severity. If an Undesired Content Foundevent is generated, it is logged (by default) and forwarded to the SNMPapplication. When you create an Site Investigator job to search your public Website, where undesired content can have more serious consequences, you choose theevent type with Critical severity. In this instance, an Undesired Content Foundevent results in the following actions:v e-mail notification is sent to the Information Services vice-presidentv notification is forwarded to your SNMP applicationv the event is logged.

In both cases, the system generates the configured event response and the defaultresponse, plus any other configured responses of lower severity for that event type.

Event typesThe following tables list and describe the event types for all the Web TransactionPerformance applications and the management server (system events).

System Event Types

Type Definition

Job Start Succeeded A scheduled job started successfully.

Job Start Failed A scheduled job failed to start.

Job Executed Caused Fatal Exception A scheduled job caused a fatal exceptionwhen it was run.

Job Stop Completed A scheduled job has run successfully to thecompletion of its schedule.

Job Abort Succeeded A job abort request succeeded.

Endpoint Uninstalled An endpoint has been uninstalled.

Heartbeat Missing The heartbeat has been missing from anendpoint for a number of minutes. Thisevent is generated if the management serverhas not received a heartbeat signal from theendpoint for a specified period of time (inminutes).

Authorization Failure The management server failed to authorize aclient request. Events of this type aregenerated when an invalid password isspecified, a user lacks permission to use therequested service, or if any otherauthorization request is invalid.


System Event Types

Type Definition

Authorization Service Succeeded The authorization or authenticationsucceeded. Events of this type are generated,for example, when a user is successfullycreated or if a management server isdefined.

Authorization Service Failed The authorization or authentication servicefailed. Events of this type are generated, forexample, when an invalid password issupplied by the user or if an attempt ismade to delete a user.

Server Authentication Failed Authentication failed while defining aforeign management server (server-to-servercommunication).

Mail Service Failed The SMTP service failed to start up due toan exception. This event is generated whenan internal error occurs or if the servicefinds an environmental or resourceconstraint while starting.

SNMP Service Failed The SNMP service failed to start up due toan exception. This event is generated whenan internal error occurs or if the servicefinds an environmental or resourceconstraint while starting.

Tivoli Enterprise Console Service Failed The Tivoli Enterprise Console forwardingservice (also known as the event handler)did not start or stop when the managementserver was started.

EXEC Service Failed The EXEC service failed to start up due toan exception. This event is generated whenan internal error occurs or if the servicefinds an environmental or resourceconstraint while starting.

Endpoint Installed A new endpoint has been installed andregistered with the management server.

EXEC Status Failed The user-supplied script or program ran andreturned a non-zero (error) status code. Thisevent is generated when the service runs auser-supplied script or program that returnsan error code.

EXEC Failed The user-supplied script or program failedto execute. This event is generated when theservice unsuccessfully attempts to run auser-supplied script or program.

Unknown Endpoint The management server has received a pingfrom an endpoint not registered to thatmanagement server.

Event Forwarded to Tivoli EnterpriseConsole Missing Data

Certain fields in the event forwarded toTivoli Enterprise Console are missinginformation. This is an internal error. TivoliEnterprise Console will not reject the event.

EXEC Complete User-supplied script or program completedsuccessfully.


System Event Types

Type Definition

Generic Event This is a generic event for general use.

Event Subsystem Exception The subsystem failed to generate an event.Turn on event tracing in theevent.properties file or contact IBMCustomer Support for Tivoli Software.

Endpoint Started Auto-Update Process An endpoint has started an auto-updateprocess.

Endpoint Auto-Update Process Succeeded An endpoint auto-update process hascompleted successfully.

Endpoint Auto-Update Process Failed An endpoint auto-update process has faileddue to an error.

Heartbeat No Long Missing Recovery: Heartbeat no long missing fromendpoint.

Endpoint Pinger Service Failed to Start An endoint pinger failed to start when theendpoint was started.

Event Annotation Incomplete The annotation portion of an event did notcompletely generate when an event occured.


Type Definition

QoS Task Status The scheduled job failed, aborted, or wasunable to start.

QoS Avg. User Experience Time Violation The user experience (round-trip) timeexceeds the constraint specified for theround-trip time parameter.

QoS Avg.User Experience Time Recovery The user experience (round-trip) time nolonger exceeds the round-trip timeparameter constraint.

QoS Avg. Back-end Service Time Violation The amount of time it took for the originserver to service the request and respondexceeds the constraint specified for theservice time parameter.

QoS Avg. Back-end Service Time Recovery The amount of time it took the origin serverto service the request and respond no longerexceeds the constraint specified for theservice time parameter.

QoS Avg. Page Display Time Violation The amount of time it took for the documentto display withing the browser exceeds theconstraint specified for the display timeparameter.

QoS Avg. Page Display Time Recovery The amount of time it took for the documentto display within the browser no longerexceeds the constraint specified for thedisplay time parameter.


Site Investigator Event Types

Type Definition

SI Task Status The scheduled job failed, aborted, or wasunable to start.

SI Aggregate Page Size Violation A page being investigated falls outside theprescribed range and exceeds the constraintspecified for the page size parameter.

SI Response Code Violation An unexpected HTTP response code wasreturned.

SI Undesired Content Found A content string that is not supposed to beincluded on a page is found.

SI Desired Content Not Found A content string that is supposed to beincluded on a page is not found.

SI URL Connection Timed Out The request sent by SI to the site timed outbefore a response was returned to SI.


Type Definition

STI Job Status The scheduled job failed, aborted, or wasunable to start.

STI Round Trip Time Violation The round-trip time exceeds the constraintspecified for the round-trip time parameter.

STI Round Trip Time Recovery The round-trip time no longer exceeds theround-trip time parameter constraint.

STI Service Time Violation The amount of time it took to service therequest and respond exceeds the constraintspecified for the service time parameter.

STI Service Time Recovery The amount of time it took to service therequest and respond no longer exceeds theconstraint specified for the service timeparameter.

STI Response Code Violation A specified HTTP response code wasreturned.

STI Response Code Recovery A specified HTTP response code is no longerreturned.

STI Undesired Content Found A content string that is not supposed to beincluded on a page is found.

STI Undesired Content Not Found A content string that is not supposed to beincluded on a page is not found.

STI Desired Content Not Found A content string that is supposed to beincluded on a page was not found.

STI Desired Content Found A content string that is supposed to beincluded on a page was found.

STI URL Not Available The playback URL is not available afterthree attempts to connect.(violation).

STI URL Available The playback URL is available (recovery).



Type Definition

STI Overall Transaction Time Violation The amount of time it took the overalltransaction to complete exceeds theconstraint for the overall transaction timeparameter.

STI Overall Transaction Time Recovery The amount of time it took the overalltransaction to complete no longer exceedsthe constraint for the overall transactiontime parameter.

STI Overall Service Time Violation The amount of overall service time exceedsthe constraint for the overall service timetime parameter.

STI Overall Service Time Recovery The amount of overall service time nolonger exceeds the constraint for the overallservice time time parameter.


Chapter 9. Managing the event service

The Web Transaction Performance applications and the management servergenerate events. Web Transaction Performance events are stored in themanagement repository. You can configure events to be forwarded to a destinationby one of the following event handlers on the management server:v System event log, through the log handlerv One or more e-mail addresses, through the Simple Mail Transfer Protocol

(SMTP) handlerv Simple Network Management Protocol (SNMP) management application,

through the SNMP handlerv Tivoli Enterprise Console (TEC), through the Tivoli Enterprise Console handler

and the Tivoli Web Services Courier endpointv Scripts that initiate an action, such as a remedial response to an event, through

the EXEC handler

The e-mail, SNMP, and Tivoli Enterprise Console event-forwarding responsesrequire configuration of the management server, as described in the followingpages.

Web Transaction Performance stores time in local time, which you should setbefore creating any jobs.. The event data receives a local timestamp. This ensuresthat all events are displayed on the Web Transaction Performance GUI in aconsistent manner.

You should configure event responses before you configure events and you shouldcomplete both tasks before you begin using the Web Transaction Performanceapplications. Configuring event responses first makes all the response optionsavailable when you configure the events. Configuring events before you begincreating jobs with the applications ensures that you will not lose any eventinformation when the jobs begin to run.

Forwarding events to the Tivoli Enterprise ConsoleYou can configure events to be forwarded to the Tivoli Enterprise Console (TEC).The Tivoli Enterprise Console event handler translates an event from InternetManagement Server format to Tivoli Enterprise Console format. The formattedevent is queued on the management server. The Tivoli Web Services Courierendpoint polls the management server every 60 seconds for Tivoli EnterpriseConsole events. Whenever there are any in the queue, they are forwarded to TivoliEnterprise Console.

Install the Tivoli Web Services Courier (WSC) endpoint according to theinstructions in your installation guide. Make sure that the TEC ForwardingEnabled check box is selected. The WSC endpoint must be installed on a TMAendpoint. After you complete installation of the WSC endpoint, TEC Forwarding isdisplayed as an option in the Event Response drop-down list in the applicationand system event configuration views.

To forward Web Transaction Performance events to the Tivoli Enterprise Console,you must have the Tivoli Framework and Tivoli Enterprise Console installed. Tivoli

119

also recommends that you contact the Tivoli Enterprise administrator beforeconfiguring the Tivoli Enterprise Console server.

Forwarding events to an SNMP Management ApplicationYou can configure events to be forwarded to a Simple Network ManagementProtocol (SNMP) management application such as Tivoli NetView. The SNMPhandler creates a message from event data, then creates and sends an SNMP trap.To forward Web Transaction Performance events to an SNMP managementapplication, you must have an SNMP management application installed. Contactthat application’s administrator before forwarding events to the SNMPmanagement application.

Configuring the Web Transaction Performance and SNMP ServersBefore the Web Transaction Performance server can forward events to an SNMPserver, you must configure the management server as follows:1. Using a text editor, edit the snmp.properties file, which is located in the

base_dir/TIMS/lib/properties directory. The base_dir variable represents theinstallation directory of the Web Transaction Performance server. The contentsof the file are as follows:# # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## Configuration file for Tivoli WSM/WSA to SNMP integration## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## Location (IP address or hostname) of SNMP management platform# e.g. snmp.yourdot.comServerLocation=# SNMP management platform incoming SNMP trap port number# e.g. default port is 162ServerPort=

2. Specify the fully qualified host name of the SNMP server with theServerLocation key. For example, if the SNMP server isfodder.mycompany.com, the key looks like this:ServerLocation=fodder.mycompany.com

3. Specify the port number of the SNMP server with the ServerPort key. Forexample, if the SNMP server’s port is 162, the key looks like this:ServerPort=162

4. Save and close the snmp.properties file.5. Restart the management server as described in “Stopping and starting the

Internet Management Server” on page 123.6. Copy the TWSM.mib file, which is located in the base_dir/TIMS/lib directory, to

the SNMP server. This file enables the SNMP server to understand the WebTransaction Performance events.

7. Load the TWSM.mib file on the SNMP server. Refer to the SNMP server’sdocumentation for instructions or contact that application’s administrator forassistance.

After you complete this procedure, SNMP Forwarding is displayed as an option inthe Event Response drop-down list in the application and system eventconfiguration views.


Forwarding events to an e-mail accountYou can configure the event service to forward events to one or more e-mailaddresses, using the Simple Mail Transfer Protocol (SMTP) handler. Use the SMTPforwarding feature to ensure that the appropriate people are notified for each typeof event generated. Automatic e-mail notification is a simple and efficient way tocommunicate that an issue needs attention.

Configuring the Web Transaction Performance ServerBefore the Internet Management Server can forward events to an SMTP server, youmust configure the management server as follows:1. Using a text editor, edit the event.properties file, which is located in the

base_dir/TIMS/lib/properties directory. The base_dir variable represents theinstallation directory of the management server. The contents of the file are asfollows:# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## Configuration file for SMTP & SOCKS## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #trace.service=com.tivoli.xtela.core.util.DefaultTraceServicetrace.switches=1-7.0# SMTP (mail) host name, e.g. mail.yourdot.commail.smtp.host=# socksProxyHost, SOCKS firewall host, e.g. socks.yourdot.comsocksProxyHost=# socksProxyPort, e.g. default SOCKS port is 1080socksProxyPort=

2. Specify the fully qualified host name of the SMTP server with themail.smtp.host key. For example, if the SMTP server is rabbit.mycompany.com,the key looks like this:mail.smtp.host=rabbit.mycompany.com

3. If your network uses a SOCKS server to access the SMTP server, specify thefully qualified name of the SOCKS server with the socksProxyHost key. Forexample, if the SOCKS server is socks23.mycompany.com, the key looks like this:socksProxyHost=socks23.mycompany.com

4. If your network uses a SOCKS server to access the SMTP server, specify theport number of the SOCKS server with the socksProxyPort key. For example, ifthe SOCKS server’s port is 144, the key looks like this:socksProxyPort=144

5. Save and close the event.properties file.6. Restart the management server as described in TBD.

After you complete this procedure, you must still configure e-mail forwarding inCreate Event Responses under System Administration on GUI. When you havecompleted that process, Send an E-mail is displayed as an option in the EventResponse drop-down list in the application and system event configuration views.

Chapter 9. Managing the event service 121

Appendix A. Stopping and starting

This appendix describes how to stop and start the Internet Management Server, anInternet Management Endpoint, and the Quality of Service proxy server. Manuallystopping and starting any of these Web Transaction Performance components isoccasionally necessary for troubleshooting, maintenance, and emergency recovery,or before and after an installation procedure.

Stopping and starting the Internet Management ServerFollow the instructions in this section to manually stop or start the managementserver. Stopping the management server also stops the IBM HTTP Server, which ispart of the management server software.

Stopping and starting on Windows systemsUse either of the following methods to stop or start the management server onsupported Windows systems:v To stop or start the management server from the Start menu:

– To stop the management server, select Start → Programs → Tivoli → StopInternet Management Server.

– To start the management server, select Start → Programs → Tivoli → StartInternet Management Server.

v To stop or start the management server from the Control Panel on Windows NT:1. Select Settings → Control Panel from the Start menu.2. Double-click the Services icon.3. Select TIMS HTTP Server from the list of services.4. Do one of the following:

– Click the Stop button to stop the management server.– Click the Start button to start the management server.

v To stop or start the management server from the Control Panel on Windows2000:1. Select Control Panel → Administrative Tools → Services from the Start menu.2. Right-click TIMS HTTP Server in the list of services.3. Do one of the following:

– Click the Stop button to stop the management server.– Click the Start button to start the management server.

Stopping and starting on UNIX systemsFollow these steps to stop or start the management server on supported UNIXsystems:1. Change to the following directory:

install_dir/ManagementServer/TIMS/bin/

where install_dir is the directory where the management server was installed.The default installation directory is as follows:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris)

123

2. Do one of the following:v Enter stopms.sh to stop the management server.v Enter startms.sh to start the management server.

Stopping and starting an Internet Management EndpointFollow the instructions in this section to manually stop or start an InternetManagement Endpoint.

Note: If you are stopping a Quality of Service endpoint, note that stopping theendpoint does not stop the Quality of Service proxy server on the endpoint.Stopping and starting the Quality of Service proxy server is a separateprocedure. See “Stopping and starting the Quality of Service proxy server”on page 125.

Stopping and starting on Windows systemsUse either of the following methods to stop or start an Internet ManagementEndpoint on supported Windows systems:v To stop or start an Internet Management Endpoint from the Start menu:

– To stop the management server, select Start → Programs → Tivoli → StopInternet Management Endpoint.

– To start the management server, select Start → Programs → Tivoli → StartInternet Management Endpoint.

v To stop or start an Internet Management Endpoint from the Control Panel onWindows NT:1. Select Settings → Control Panel from the Start menu.2. Double-click the Services icon.3. Select Tivoli Internet Management Endpoint from the list of services.4. Do one of the following:

– Click the Stop button to stop the endpoint.– Click the Start button to start the endpoint.

v To stop or start an Internet Management Endpoint from the Control Panel onWindows 2000:1. Select Control Panel → Administrative Tools → Services from the Start menu.2. Right-click Tivoli Internet Management Endpoint in the list of services.3. Do one of the following:

– Click the Stop button to stop the endpoint.– Click the Start button to start the endpoint.

Stopping and starting on UNIX systemsFollow these steps to stop or start an Internet Management Endpoint on supportedUNIX systems:1. Change to the following directory:

install_dir/Endpoint/bin/

where install_dir is the directory where the endpoint was installed. The defaultinstallation directory is as follows:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris or Red Hat Linux)

2. Do one of the following:


v Enter stopep.sh to stop the endpoint.v Enter startep.sh to start the endpoint.

Stopping and starting the Quality of Service proxy serverFollow these procedures to stop or start the Quality of Service proxy server that isinstalled with the Quality of Service endpoint.v To stop or start the Quality of Service proxy server on Windows NT:

1. Select Settings → Control Panel from the Start menu.2. Double-click the Services icon.3. Select Tivoli Endpoint HTTP Server from the list of services.4. Do one of the following:

– Click the Stop button to stop the Quality of Service proxy server.– Click the Start button to start the Quality of Service proxy server.

v To stop or start the Quality of Service proxy server on Windows 2000:1. Select Control Panel → Administrative Tools → Services from the Start menu.2. Right-click Tivoli Endpoint HTTP Server in the list of services.3. Do one of the following:

– Click the Stop button to stop the Quality of Service proxy server.– Click the Start button to start the Quality of Service proxy server.

v To stop or start the Quality of Service proxy server on UNIX-based systems:1. Change to the following directory:

install_dir/Endpoint/bin/

where install_dir is the directory where the Quality of Service endpoint wasinstalled. The default installation directory is as follows:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris or Linux)

2. Do one of the following:– Enter ./stopserver.sh to stop the Quality of Service proxy server.– Enter ./startserver.sh to start the Quality of Service proxy server.

Appendix A. Stopping and Starting 125

Appendix B. Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in this product enable users to do the following:v Use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Navigating the interface using the keyboardStandard shortcut and accelerator keys are used by the product and aredocumented by the operating system. Refer to the documentation provided byyour operating system for more information.

The following table lists the additional keyboard shortcuts that you can use tonavigate inside the windows of this product:

Table 8. Keyboard shortcuts for the product

Shortcut Function Performed

Alt + n Next button click

Alt + p Populate button click

Alt + l Clear button click

Alt + r Remove or Refresh button click

Alt + a Add or Add to Table button click

Alt + s Save button click

Alt + u Unschedule Selected button click

Alt + d Delete Selected button click

Alt + c Cancel button click

Alt + m Create/Modify button click

Alt + y Apply to All button click

TabMoves highlighting from screen object toscreen object during installation

Space BarSelects highlighted screen objects duringinstallation

127

Magnifying what is displayed on the screenYou can enlarge information on the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. Refer to the documentation provided by youroperating system for more information.

Using Home Page Reader version 3.02 with Web TransactionPerformance

Web Transaction Performance is compatible with Home Page Reader version 3.02and higher. To navigate the graphical user interface (GUI) using Home PageReader, perform the following steps:1. To start the GUI within Home Page Reader, press the Tab key twice to

highlight the menu frame.2. Use the Up and Down arrow keys only.

Note: If HomePageReader 3.02 is installed as an upgrade rather then a newinstall, you must use the Up and Down arrow keys while also pressingthe Alt or Ctrl keys.

3. Use the tab key to navigate the rest of the GUI as you normally would.


Appendix C. Problem Determination

This appendix provides information about resolving problems that might occurwhen you run Tivoli Monitor for Transaction Performance. The following types ofproblems might occur:v “Synthetic Transaction Investigator” on page 134v “Web Services Courier and Tivoli Decision Support historical data collection” on

page 138v “Quality of Service endpoint” on page 139

To aid you in problem determination, Web Transaction Performance has powerfullogging and tracing tools built into the product.

User Interface LoggingThe user interface log file, timsiu.log, is located in the TIMS/logs directory.Information is continually appended to this log file. Even if the InternetManagement Server is restarted, the information appends to the previoustimsiu.log file. You can view the log file by selecting SystemAdministration→View Log Files.

Note: The abbreviation TIMS appears in some of the product file names. It is anold abbreviation for the internet management server.

Attributes of logging are controlled by the uilogging.properties file located in theTIMS/lib/properties directory. Logging is the actual sending of information to thelog file; it includes both tracing and messaging. Tracing is the logging of stacktraces and other development and support tracing; these are not translated.Messaging is the user-understandable logging that is translated. See “Adjusting LogFile Settings” for more information.

Adjusting Log File SettingsThe uilogging.properties file controls the settings of the user interface tracingand should be placed in a management server path. At installation the file is in theTIMS/lib/properties directory. If invalid values are present or theuilogging.properties is not found, the default values will be used.

To change the attribute values, which are shown in the following table, edit theuilogging.properties file and restart the Internet Management Server.

Attribute Description Values Default

filename Specifies the name of the user interface log file any string timsui.log

loggingOn Specifies whether tracing and messaging is on or off. 0 = off

1 = on

1 — only errormessaging isturned on bydefault

129

severityLevel Specifies what types of error messages are logged.

0 and 1 correspond to error and warning, respectively.

2 includes the text traces in the code. These are nottranslated.

3 includes method in/out tracing. Currently, nomethod tracing is done so this level is not in use.

Since they are not translated, severityLevel 2 and 3are only viewable under 1 and 2 detailLevel.

Higher levels are inclusive of lower levels. Forexample severityLevel 2 includes severityLevel 0-2.

0 = error (messaging)

1 = warning(messaging)

2 = informational(tracing)

3 = detailed (tracing)

0

verboseLevel Specified the detail level of tracing to be logged.

Higher levels are inclusive of lower levels. Forexample severityLevel 2 includes severityLevel 0-2.

0 = user

1 = support

2 = development

0

handler Controls how the log file can be appended.

The 0 (zero or multiple) value takes into account thevalues of multipleMaxLength and multipleMaxFiles.With the defaults, the multiple attribute will appendto a log file named timsui1.log. When this logexceeds the multipleMaxLength value, it will berenamed timsui2.log. This process will continue untilthe multipleMaxFiles value is reached, at which timethe last log file will be deleted.

Note that timsui1.log will always be the most currentlog file.

0 = multiple files

1 = one file

0

multipleMaxLength

Applies only if handler = 0 Any integer; measuredin kilobytes

1000 K bytes

multipleMaxFiles

Applies only if handler = 0 Any integer 3

Note: The default values are used if the uilogging.properties file is not found orif it contains invalid values.

The severityLevel and verboseLevel values act as a grid for filtering. Eachcombination of the two provides different logging. The following are examples:

Example 1:(verboseLevel=1/support, severityLevel=2/detailed):2001.07.20 21:40:51:439com.tivoli.xtela.core.ui.bean.global.DisplayJobsBean

setJobs(Vector)UIBWAUG0002Ecom.tivoli.xtela.core.objectmodel.kernel.DBSyncException: This is anexample exception with text.at com.tivoli.xtela.core.ui.bean.global.DisplayJobsBean.setJobs\(DisplayJobsBean.java:148)at com.tivoli.xtela.core.ui.web.task.global.DisplayJobs.execute\ (DisplayJobs.java:171)at com.tivoli.xtela.core.ui.web.task.UITaskService.handlePost\ (UITaskService.java:76)at com.tivoli.xtela.core.ui.web.XtelaServlet.doPost\(XtelaServlet.java:62)at com.tivoli.xtela.core.ui.web.task.UITaskService.handleGet


\(UITaskService.java:39)at com.tivoli.xtela.core.ui.web.XtelaServlet.doGet(XtelaServlet.java:50)at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

Example 2:(verboseLevel=0/user, severityLevel=1/error):2001.07.20 22:04:15.037com.tivoli.xtela.core.ui.bean.global.DisplayJobsBean setJobs(Vector) UIBWAUG0002E An unexpected database error has occurred - unable to readthe specified records.

TracingTo turn on logging and tracing for debug purpose, do the following:1. Set trace=3 for sti-playback.properties

2. Extract logging.properties from /lib/properties.jar and set trace.components =sti

Various components that can be traced. Turn off all tracing to speed up the code.Uncomment the following line to turn on tracing:# trace.components = xform, controller, collector, aggregator,gui, #listener, wsmreport, sti trace.components = sti

Running Synthetic Transaction Investigator in visible modeBy default, the Synthetic Transaction Investigator application operates in headlessmode. In headless mode, Synthetic Transaction Investigator tasks, in the form ofrecorded transactions, are executed internally within registered endpoints. You canmonitor an Synthetic Transaction Investigator task through synthetic transactionreports from:v Web Transaction Performance user interface.

—OR—v Tivoli Decision Support

Web Transaction Performance events occur when a transaction does not perform asdefined by an Synthetic Transaction Investigator task. The event log, accessiblefrom the Web Transaction Performance user interface, includes the state ofviolation or other failures associated with an Synthetic Transaction Investigatortask. Additionally, the Web Transaction Performance synthetic transaction reportprovides a graphical depiction of the transaction state in real-time.

Web Transaction Performance and Tivoli Decision Support do not always provideenough information to correct an error. Enabling Synthetic Transaction Investigatorto expose the transaction running within a browser window might provideadditional information to determine the cause of the error.

The Synthetic Transaction Investigator application can operate in visible mode withthe following limitations:v You must start Synthetic Transaction Investigator from the command line. Make

sure the endpoint service is stopped before logging onto the machine.v You cannot access the browser application when the Synthetic Transaction

Investigator application controls the Internet Explorer browser.v You must stop Synthetic Transaction Investigator from the command line before

you resume normal Synthetic Transaction Investigator operations.

Appendix C. Problem Determination 131

v A separate Internet Explorer application window is created each time atransaction is called to execute. This window is deleted after the transactioncompletes.

To setup Synthetic Transaction Investigator to operate in visible mode perform thefollowing steps:1. Stop the endpoint service from the Windows Start menu as follows:

a. Click Start

b. Click Programs

c. Click Tivoli

d. Select Stop Internet Management Endpoint

2. Modify sti-playback.properties and add the visible=1 entry.3. Open a command window in the following directory:

<STIEndpointRoot>\Endpoint\bin\w32-ix86

4. Execute the lpwin32.exe command:

Note: The Tivoli Web Services splash screen displays momentarily.5. Schedule a transaction from the Web Transaction Performance user interface.

An Internet Explorer browser window displays on the desktop when thetransaction executes. All the steps in the transaction are executed in the InternetExplorer browser context.

Note: The Internet Explorer browser window closes when the transactioncompletes. Fast transactions might be difficult to detect.

6. Stop the application using the lphalt.exe command from the followingdirectory:<STIEndpointRoot>\Endpoint\bin\w32-ix86

Historical collection tasksThis section describes problems you might encounter with the historical collectiontasks for Tivoli Monitoring for Transaction 5.1. Understanding logging and tracingof the endpoint is helpful in determining problems with the historical collectiontasks.

The Tivoli Monitoring for Transaction web interface event logs provide generalinformation about historical data collections. For detailed information about thecollection, view existing logs produced by the endpoint in the <BASEDIR>/logsdirectory on the endpoint machine. You can also turn on extended trace logging inaddition to the other logging for more detailed information.

The following is a description of each type of trace logging.

twsa_1.logThe twsa_1.log file is produced when a historical task starts and isappended after each endpoint restart. The twsa_1.log file is located directlyunder the log directory in the endpoint base directory. It contains thefollowing information:v Historical collection start and completion with a timestamp for each

application.v Number of parsed records, blank records, and records that were thrown

out due to errors.v Any general fatal error (e.g. database errors, etc).


Each application is associated with one of the following task numbers:v Task 1: QoSv Task 2: WSIv Task 3: Synthetic Transaction Investigator

Note: If the twsa_1.log file is cluttered with information, you can deletethe file before the next collection. On Wintel systems, you must tostop the endpoint before you can delete it.

endpoint.logThe endpoint.log file is produced when the endpoint starts. It is locateddirectly under the log directory in the endpoint base directory and recycledwhen the next endpoint starts. By default, it contains messages statingwhether the endpoint started successfully or not. If a running collectiontask encounters a fatal error, such as a database exception, theendpoint.log contains the java stack trace output. This endpoint.log filedoes not provide a stack trace, which provides more detail, such as theclass, method, and line number.

error logsThe error logs files contain records excluded from the warehousepopulation due to errors. The error logs are generated during a historicalcollection task in the errors subdirectory within the endpoint log directory.These logs might help you debug parsing problems. Each application log isseparated into subdirectories labeled by the corresponding task number.

extended tracing (cswa tracing)Extended tracing extends the contents in the endpoint.log file. Changingtrace.switches parameter enables extended tracing (cswa tracing). Fordetailed information for all subsystems, turn on full tracing, which istrace.switches=1-13.1. You must extract the full tracing file from thecswaproperties.jar file in the base lib directory. Place the file in thelib/local subdirectory and change the parameter, then restart the endpoint.This tracing provides a stack trace containing the violating class, method,and even line number in the code.

parser tracingParser tracing provides more detailed messages about the log parsing inthe endpoint.log file. This tracing is useful for log parsing problems, but inmost cases, extended tracing is most useful. You can enable parser tracinglogging by extracting parser.properties from the properties.jar into thelib/local directory.

task tracingTask tracing indicates when the next historical collection task takes place.To enable task tracing, extract task.properties from properties.jar intolib/local. Modify the trace.switches=1-4.1. You can use task tracing to helpdebug timing issues. Consider the following schedules are involved in tasktracing:v Synthetic Transaction Investigatorv historical data collectionv Tivoli Decision Support cube build schedules


Historical collections are not runningIn general, if historical collections are not running you can enable task tracing andview the endpoint.log file for details. The following lists other reasons whyhistorical collections might not run.

Historical data collection is disabledEnable this setting in the Web Transaction Performance management serverweb interface.

Endpoint service or process is not runningEnsure that the endpoint service or process is running:

Windows NTCheck the process using the Windows NT services control panel

UNIX Check the process table (e.g. ps –ef | grep –i java).

TIMS server is not runningIf a historical data collection does not run as expected, make sure the TIMSis running. If TIMS is not running, then start the server and restart theWSC endpoint to reset the task scheduler.

Historical collection was incorrectlyCheck the endpoint.log if task tracing is enabled to view the current timein comparison to the next scheduled in time in your local time.

Warehouse database is downIf the warehouse database is down, the historical collection task will try toconnect to it until it times out. If the endpoint and server are running andscheduled correctly, check the database server to determine if it is down.Restart the database if it is down.

Synthetic Transaction InvestigatorThis section describes some symptoms you might experience with the SyntheticTransaction Investigator, some probable causes of the symptoms, and a remediesfor the symptoms.

Internet Explorer process stays up in memory. If transaction isplayed back in visible mode, the dialog displays.

The cookie is not cached into the Default User/LocalSettings/Cookies directory.Cookies saved using a manual browser to certain Web sites that present pop-upwindows based upon presence/no presence of cookies, are saved in the userprofile directory, not the Default User directory used by STIP. Manually browsethrough the transaction with Internet Explorer and click on the button on thepop-up window to store the cookie.

The endpoint generates a URL not available (Navigationcanceled) event and displays red bars in the real time graph.

The Web Services Investigator Endpoint failed to play back a transaction thatinvolves web server or proxy authentication due to Internet Explorer’s failure toobtain the correct user name and password. Do one of the following to correct theerror:1. Install the Synthetic Transaction Investigator recorder on the same host and the

same account as the Synthetic Transaction Investigator playback endpoint.2. If a dialog displays asking for user name and password, select Save this

password in your password list check box.


—OR—1. Before playback of the pre-recorded transaction, login to the Synthetic

Transaction Investigator endpoint host with the same account used duringinstallation

2. Open Internet Explorer browser.3. Play back the transaction manually.4. If a dialog display asking for user name and password, select Save this

password in your password list check box.

The endpoint generates URL Not Available (timeout) events anddisplays red bars in the real time graph.

Transactions do not play back successfully until Internet Explorer is initialized.1. Log onto the host machine using the new user account created to install the

endpoint.2. Activate Internet Explorer.

The endpoint generates a URL not available (Navigationcanceled) event and displays red bars in the real time graph.

The Recorder does not record redirected URLs to the trans.XML transactiondocument. Obtain the redirected URL.v Ask the Web Master for the URL

—OR—v Set a proxy that logs the Internet Explorer requests and responses. The proxy

catches redirections the server instructs the navigator to perform.

Do the following after you obtain the redirected URL:1. Record a new transaction, setting up the REALM credentials and domain

according to the host portion of the given URL2. Specify the authenticating URL as the first step of the transaction.

The user name and password must be cached to the local Internet Explorer.

The endpoint generates URL not available events and displaysred bars in the real time graph.

Web Services Investigator Endpoint can not playback a transaction that requires aclient side certificate with as-is trans.xml generated by the recorder. By default, theendpoint instructs Internet Explorer process to run in silent mode to suppresspopup windows. However, Internet Explorer does not send the required certificateback to the web server when it runs in silent mode. There is a defect open againstMicrosoft Internet Explorer.1. Install the required client certificate on the endpoint host with the account it

used during installation.2. Manually playback the transaction and determine which sub-transaction

requires a client side certificate.3. Select Edit transaction from the graphical user interface.4. Click Configure attributes on right hand corner5. Select the correct sub transaction6. Unchecking Silent to disable silent mode


STIP 1.7 and 5.1 does not support multiple client-side certificates installed on theendpoint machine.

The endpoint generates URL not available events and displaysred bars in the real time graph.

The Web Services Investigator Endpoint is not able to successfully playback atransaction in which the query portion of the URL contains nonstandard delimiters.The standard delimiters are & (group separator) and = (record separator); & isused to separate different sets of key/value pairs and = is used to separate theparameter’s key and its value. By default, Synthetic Transaction Investigator usesstandard delimiters to tokenize the URL’s query and post content. Havingnon-standard delimiters in these strings causes Synthetic Transaction Investigatorto unable to reassemble the correct dynamic request.

Manually playback the transaction and determine which sub-transaction hasnon-standard delimiters. Then go to the GUI, select Edit transaction, click onConfigure attributes on right hand corner, choose the right sub transaction, andtype its group separator and record separator.

Every attempt to run a transaction results in a NavigationCancel event and red bars display in the transaction graph.

A Web Services Investigator Endpoint is not able to playback a transactionauthenticated through a NT Lan Manager user unless the server and the localmachine recognize the user and password as a local or domain member. Each timeWeb Services Investigator visits the authenticated URL, Internet Explorer 6 requiresuser intervention in a pop-up a message to confirm the user name and passwordthat exists on the cache. The following is the pop-up window that displays whenyou manually browse the Web site. The following dialog does not appear when theendpoint successfully plays back the transaction.

Implement a configuration that identifies the user and password to the endpointand the server by doing one of the following:v Create the NT Lan Manager user into the Endpoint machine. This solution is

the least intrusive and more viable when the Web Transaction Performance Userdoesn’t have control over the NT Lan Manager server but has control on theEndpoint machine. The biggest security risk is that all authenticated users knowthe account on the endpoint machine. The endpoint can playback transactionsafter you complete the following steps:


1. Install the WSI Endpoint with the user name and password used toauthenticate the transaction against the NT Lan Manager Server. Forexample, you might authenticate the Web site with the user name NT LanManagerUser and password 1234.

2. Create a local user named NT Lan ManagerUser and set the password as1234.

3. Make NT Lan ManagerUser part of the Administrators group and setpermissions to Log in as a service and Act as part of the OS. (Refer to theInstallation Guide for additional details on how to setup the WSI account).

4. Log in as the NT Lan ManagerUser

5. Open an Internet Explorer session.6. Browse to the Web site.7. Install the security certificate if offered.8. Visit the authenticated URLs and save the password.

v Add the TivoliStiPlayback account to the NT Lan Manager Server. Thissolution is more viable whenever it is possible to create a local account into theNT Lan Manager server; preferably the TivoliStiPlayback is an exact replica ofthe NT Lan Manager user used to authenticate the transactions. There is nosecurity risk identified, other than those already existing for the NT LanManager user. Procedure. After completing these steps, the endpoint canplayback the transactions.1. Install the WSI Endpoint which creates the TivoliStiPlayback account.2. Create the TivoliStiPlayback user on the NT Lan Manager Server.3. Use same password as the one on entered on the Installation panel.4. Continue to setup the environment for the Synthetic Transaction Investigator

Playback as described on the TWS Installation Guide.v Install the WSI Endpoint using a domain account, recognized by the NT Lan

Manager Server and the Endpoint. This solution is viable when the WSIEndpoint and the NT Lan Manager Server are sharing the same domain.Although this configuration is not supported according to the productdocumentation, it is indeed possible to install the endpoint using a local accountand later switch the account associated to the NT service named Tivoli InternetManagement Endpoint. After completing the following steps, the NT servicecan start using the Domain account and the playback can perform jobs.1. Install the WSI endpoint using the Administrator account. Do not use a

domain account.2. After completing the installation, the NT service associated to the endpoint is

registered to Log On as Administrator. You must change this property of theService by visiting the Log On tag of the NT Services properties for TivoliInternet Management Endpoint and replacing the Administrator accountwith the NT-Domain\User account that you want to use.

3. Assign adequate permissions to the user.4. Authorize the user to Log On as a Service, Act as part of the OS and add it

to the Administrators group of users.5. Log in into the machine as the NT-Domain\User.6. Browse to the URLs that will be used to playback.7. Save all security certificates and passwords to the web pages used by the

Synthetic Transaction Investigator Playback.


Web Services Courier and Tivoli Decision Support historical datacollection

There are two separate stages in the historical data collection process:1. The first stage is to parse the log files and place them into the staging tables (ts

<name>).2. The second process is to migrate the staged data into the production tables. The

production tables consist of fact tables (tf<name>) and definition tables(td<name>).

Problems with partial data or no data are usually discovered in the Tivoli DecisionSupport process. The Tivoli Decision Support report data comes from thisproduction area in the courier warehouse. The behavior of the historical datacollection task or an event on the Web Transaction Performance server can indicateproblems. The following lists examples of problems with a possible solution.

The event log in the Web Transaction Performance server webinterface indicates a historical collection failure with at leastone application task (Synthetic Transaction Investigator, SI, orQoSM).

See the endpoint.log file for detailed information on the failure. The java exceptionprovides a more localized description of the failure. Database errors such asrollback segments and out of temporary space errors might indicate that yourcourier warehouse needs more space. Do one of the following to solve theproblem:v Provide database maintenancev Run the warehouse clean script (cleanDw.sh or cleanDW.bat) to purge data

from the database so you can acquire more space.

The event log in the web interface does not indicate aproblem and the historical data collection tasks completed,but there is no new data displayed in the reports.

The Web Transaction Performance management server machine is not generatingapplication logs. Make sure the endpoint tasks are running. If the endpoint task isnot running, no new data is uploaded to the TIMS. Synthetic TransactionInvestigator logs are found in <BASEDIR>/TIMS/STI/logs under the task IDsubdirectory, the name of which includes a number greater than 100. The filesbegin with the application type and a unique identifier appended to the filenamewith an extension of log (for example, STI1030137695756.log). If the date and timestamp do not reflect recent activity, this indicates that the IMS is not generatingnew logs for this application.

The Tivoli Decision Support reports display no data for aspecific time period but the collections ran successfully.

The dates in Tivoli Decision Support reports reflect the dates the endpoint obtainedthe data and do not reflect the dates the collection took place. For example, anSynthetic Transaction Investigator playback task ran last week, but the historicalcollections are disabled this week. If you collect and build cubes today, the reportdoes not include data for the rolling seven days.


Quality of Service endpoint

An installation of QOS or TIMS alters functionality on amachine with the GSK5 package already installed.

The current product requires an older or newer version of GSK. The installerpreappends the Web Transaction Performance GSK version to the environment. Doone of the following to correct the situation:v Context. The Web Transaction Performance installer backs up the existing

registry key of GSK under: HKLM\SOFTWARE\IBM\existing_GSK5 The newregistry key points to the Web Transaction Performance installation directory asfollows: <BASEDIR>/Endpoint|ManagementServer/IBMHTTPSERVER/w32-ix86/gsk5

The Web Transaction Performance installer prepends the GSK5/lib directory tothe PATH system environment variable.

v Manipulate the Windows registry using regedit32 using the following steps:1. Rename the current registry key HKLM\SOFTWARE\IBM\GSK5 as

HKLM\SOFTWARE\IBM\GSK5_TWSM

2. Rename the HKLM\SOFTWARE\IBM\existing_GSK5 toHKLM\SOFTWARE\IBM\GSK5

—OR—v Change the PATH environment variable using the following steps:

1. Click the Windows NT Start button.2. Select Setting

3. Select Control Panel

4. Select System

5. Select Advanced

6. Select Environment Variables

7. Select System Variables

8. Select PATH

9. Delete the reference to the<TWSM_BASEDIR>/Endpoint|ManagementServer/IBMHTTPSERVER/w32-ix86/gsk5/lib

—OR—v Restart the machine.

QOS is configured to be secure-in/secure-out, but does notconnect to the origin server and returns a 502 Proxy error.

Confirm the following:v The certificate on the origin server is validv The origin server certificate name identically matches the name of the origin

server.v QOS is configured to connect to the secure port that is being broadcast by the

origin server.v You can reach the desired Web site through a browser to contact the directly

origin server on those ports.


A 502 Proxy error is returnedThe following can cause a 502 Proxy error:v An invalid certificate if QOS is using SSL to communicate with the origin server.v Network trouble between QOS and the origin server.vConfirm the following to prevent 502 Proxy errorsv You can resolve the names used in the qos.conf file and the

apach-rproxy.conf-servers file from the QOS machine.v The host name used in the configuration files is the correct host to proxy.v The Web site on the origin server is up and running.

How do I keep QOS from logging image requests?Add the following lines to your httpd.conf file:v SetEnvIf Request_URI \.gif image-requestv SetEnvIf Request_URI \.jpg image-requestv SetEnvIf Request_URI \.png image-requestv CustomLog logs/access.log combined env=!image-request

Once you have done this, stop and restart your Tivoli QOS HTTP Server, and thenew changes will be in place.

The Web site code includes port numbers in the URL that arenot the QOS ports. The load balancer is not set up so that allservers operate the same.

The web server hard-codes a port number as part of the returned URL. When theclient receives this URL, it goes to the new port number rather than the QOS portnumber.

Make sure that your application is not specifically including hard-coded portnumbers. If this is not an option, the server farm must accommodate the newports. The load balancer must be able to load balance requests that come in on thenew ports, and the Firewall must also allow requests on the non-standard ports.Also, in the case of Windows Load Balancing Service, every server behind the loadbalancer must be able to serve pages on all of the available ports. Every servermust to be able to send back content on every port that might be requested fromthe application.

Consider the following example scenario: QOS is listening on http://mysite.com:80/and the origin server is listening at http://mysite.com:82/. Somewhere in theapplication, the http://mysite.com:82 URL is returned to the client. The client triesto make this request, and if the Firewall does not allow requests on port 82, or theload balancer does not load balance on port 82, the request will fail. Also, in thecase of non-QOS machines, they will have their Web sites running normally onport 80, and they will not be listening on port 82. Thus, if the load balancerforwards the request to one of those machines, they will not answer.

QOS seems to redirect for http://mysite.com:82/, but not forhttp://mysite.com/.

The ProxyPassReverse directive in the qos.conf file, located in<INSTALL_DIR>\Tivoli\Internet\Endpoint\IBMHTTPSERVER\conf is an exact


pattern match. By default, the QOS setup creates a directive that uses the hostnameand port of the origin server. When a request is made to http://mysite.com withoutthe trailing slash (\), some webservers append the port (IIS) and some do not(Apache, WebSphere, etc). Because the ProxyPassReverse is an exact pattern match,http://mysite.com fails. The solution is to add an additional line to qos.conf toaccount for the exact pattern match. The following are examples of theProxyPassReverse lines in the qos.conf file:

ProxyPassReverse / http://mysite.com:82/ProxyPassReverse / http://mysite.com/

Note: If the trailing slash is not included, the exact match fails and QOS does notproxy.

QOS does not work with host headersThe NameVirtualHost directive enables you to configure the qos.conf file for usinghost headers. For more information on the NameVirtualHost directive, seehttp://httpd.apache.org. For example, http://mysite.com is associated with the192.168.1.1 IP address on port 80. http://myothersite.com is also associated with(listening on) the same 192.168.1.1 IP address on port 80. If you add QOS to theconfiguration, the two sites listen on port 82. http://mysite.com/ is different fromhttp://myothersite.com/. The following steps describe an example of configuringthe qos.conf file for using host headers.1. Add the directive at the end of the qos.conf file. The following shows an

example what to add for the directive:NameVirutalHost 192.168.1.1:80

2. Add a virtual host for the first site, http://mysite.com. For more information onhow to create a standard VirtualHost directive, see the IBM Tivoli Web ServicesManager Redbook: Internet Management Made Easy. The following shows anexample of what to add for the first virtual host:<VirtualHost 192.168.1.1:80>

ServerName mysite.com{OTHER VHOST STUFF HERE}

?VirtualHost>

3. Add a virtual host for the other Web site with an entry similar to the first Website:<VirtualHost 192.168.1.1:80>

ServerName myothersite.com{ OTHER VHOST STUFF HERE }

</VirtualHost>

4. Repeat step 3 for each different host you want to monitor.

Note: The information is aggregated into one job, but allows you to monitor allrequests on all host headers supported by the origin server.

QOS setup that uses SSL does not connect to the originserver and SSL-related errors display in the proxy-error.log

Check the certificate on the origin server. Because QOS has underlying securitylibraries, the origin server must have a valid certificate. QOS can only connect tothe origin server if it has a valid certificate.

Note: A self-signed certificate can be valid.


The javascript inserted into the HTML includes a URL thatcontains the name of the QOS server itself is not accessibleto the outside world.

Perform the following steps to enable communication between QOS and the originserver and rewrite URLs with the correct external hostname.1. Make sure that http://www.mysite.com is available as resolving to the QOS IP

address.2. Edit the hosts file on the QOS machine.

Note: The host file is usually located in c:\winnt\system32\drivers\etc onWindows machines.

3. Make an entry that points www.mysite.com to the IP address of the originserver. This will force all requests that QOS makes to www.mysite.com to go tothe origin server.

4. Edit the server in EAAConfig.properties to<protocol>://www.mysite.com<port>/ to configure QOS to listen on and rewriterules for www.mysite.com

5. Make sure the HTTP server configuration points to www.mysite.com.


Appendix D. Messages

This appendix describes recovery actions you can take in response to the errormessages displayed by the product. Messages are displayed either in the userinterface or in a separate popup window. Each message is preceded by a messageidentifier. The message identifiers are arranged in numerical order in thisappendix.

Message formatThe message identifiers conform to the Tivoli message standard. Each messageidentifier takes the form XXXYY####Z, where:

XXX product prefix (BWM, BWA, BWC, BWAUG)

YY application prefix

The following are the codes within the user interface:

BWM UQ (Quality of Service), US (Site Investigator), UT (SyntheticTransaction Investigator), UI (Web Transaction Performanceinterface), IS (Installation)

BWA UW (Tivoli Web Services Courier), UI (Tivoli Web Services Courierinterface)

BWC UO (monitor), UA (management), UI (Tivoli Web ComponentManager interface)

BWAUGby convention, used as the user interface global error code (over allproducts) since no global product prefix is provided

#### error message number

Z severity code of the error

I (informational)feedback about normal events

W (warning)potentially undesirable conditions

E (error)indicates problems that require intervention or correction beforethe program can continue properly

The message ID is followed by the date and time of the message.

User interface message number rangesGenerally, user-visible errors are in the 0000–4999 error message number range. Allerrors above 5000 are either support exceptions/errors or validation errors. In bothsituations, the message IDs are only applicable for support or developmentpurposes.v Database exceptions (range 0001–0999): Under severityLevel=0 and

detailLevel=0display generic messages to the user. Under higher detailLevel,

143

the stack trace pinpoints the location. In many cases, the database exceptionmessage specifies the UUID causing the exception.

v Other exceptions and errors (range 1000–4999): Any exceptions and errors thatare appropriate for user understanding. These do not include validation errors.

v Support exceptions and errors (range 5000–8999): Any exceptions and errors thatdo not make sense to a typical user, but could help support. Support errors arelogged under the default user logging as Unexpected Exception, as in thefollowing example:BWAUG5001E 2001.09.27 10L:51:33.644 com.tivoli.xtela.logging.ui.LogExampleexception(Object, String, Throwable) UI An unexpected error has occurred.

In this example note that the message ID actually corresponds to a supportexception ID, but the text under user verboseLevel is always ″An unexpectederror has occurred.″ At a higher verboseLevel, the stack trace will reveal the rootproblem.

v Validation errors (range 9000–9999): Validation errors differ slightly from othererrors. Examples of validation errors are a negative value for integer fields or noinput for fields that are required. By user-interface design, validation errorsprohibit the user from continuing to the next view. Therefore, they are resolvedthrough user interaction and are negligible. Validation errors are not be helpfulfor support and clutter the log files. This special range allows them to be filteredand not logged.

Message descriptions

BWAUG0000E An unexpected error occurred.

Explanation: This message occurs when the error does not fall into any of the database error categories.

Operator Response: Contact customer support.

BWAUG0001E An unexpected database error occurred.

Explanation: This is the database error that might be produced by errors that fall into any of the database errorcategories.

Operator Response:

1. Ensure that the database computer is up and running.

2. Proceed through the operator responses for error numbers BWAUG0002 through BWAUG0005.

BWAUG0002E An unexpected database error occurred; cannot read the specified records.

Explanation: The Internet Management Server cannot read from the database.

Operator Response:

v Ensure that the database computer is up and running.

v Ensure that the user interface is displaying the most current data from the database. Manually adding or deletingentries from the database can cause invalid referential integrity. Refreshing the view corrects this in some cases. Inother cases, you have to manually delete or update the database so that there are no more references to recordsthat do not exist.

v Advanced users: Turn on the jdbc tracing to trace all the calls to the database. In the dbconfig.properties file inthe TIMS/lib/properties directory, there is a property called dbmgmttrace.jdbc. Uncomment the jdbc property(remove the # before the property) and set it equal to the file name to which you want it to refer.

BWAUG0000E • BWAUG0002E


BWAUG0003E An unexpected database error occurred; the specified record does not exist.

Explanation: The database tables do not contain the specified record.

Operator Response:

v Ensure that the database machine is up and running.

v Ensure that the user interface is displaying the most current data from the database. Manually adding or deletingentries from the database can cause invalid referential integrity. Refreshing the view corrects this in some cases. Inother cases, you must manually delete or update the database so that there are no more references to records thatdo not exist.


BWAUG0004E An unexpected database error occurred; cannot delete the specified records.

Explanation: The specified record cannot be deleted from the database.

Operator Response:


v Ensure that the specified record is in the database.

v Deleted files are moved into a rollback segment that holds a certain amount of information so that an undo ofthese actions can be performed. Rollback segments are of a fixed size; if you try to delete too much at one timeand the rollback becomes full, then no records are deleted and this error occurs. Try deleting less information atone time, or refer to your database documentation for information on changing the size of rollback segments.


BWAUG0005E An unexpected database error occurred; cannot write the specified records.

Explanation: Cannot write to the database.

Operator Response:


v It is possible that you have run out of table space. Refer to your database documentation.


BWAUG1001W Cannot save the schedule. Please verify that all information is valid.

Explanation: The schedule contains invalid information.

Operator Response: Review the information you typed and make sure it is valid. For example, ensure that integersare not negative.

BWAUG1002E Unable to render view.

Explanation: This is an internal server error.

Operator Response: Refresh the view.

BWAUG1003E An error occurred verifying the task.

Explanation: The job was written to the database, but it cannot be verified.

Operator Response:


BWAUG0003E • BWAUG1003E

Appendix D. Messages 145

v Ensure that the user interface is displaying the most current data from the database. Manually adding or deletingentries from the database can cause invalid referential integrity. Refreshing the view corrects this in some cases. Inother cases, you must manually delete or update the database so that there are no more references to records thatdo not exist.

v Ensure that the database user account has read and write access to all Internet Management Server subdirectories.

v Advanced users: Turn on the jdbc tracing to trace all the calls to the database. In the dbconfig.properties file inthe TIMS/lib/properties directory, there is a property called dbmgmttrace.jdbc. Uncomment this property (removethe # before the property) and set it equal to the file name to which you want it to refer.

BWAUG1004E An unexpected database error occurred; cannot unschedule the specified jobs.

Explanation: This is a database write problem.

Operator Response:


v You might have run out of table space. Refer to your database manual.


BWAUG1005E Cannot delete specified records. Please verify that all information you typed is valid.

Explanation: No additional information is available for this message.

BWAUG1006E Job was not successfully scheduled.

Explanation: A database read or write error or some unexpected exception has occurred.

Operator Response: Ensure that the database computer is up and running.

BWAUG1007E Unauthorized access attempted.

Explanation: The user does not have the role required to perform the task he or she is attempting to perform.

Operator Response: The user must request the required role from the administrator.

BWAUG5010E Unable to load the specified license checker.

Explanation: A non-existent license checker was specified either because the UITree.xml file was edited incorrectlyor the class path cannot be loaded.

Operator Response: Ensure that no one has modified the file.

BWAUG5011E XML Parsing error.

Explanation: The edited transaction is either no longer valid or is not in well-formed XML.

Operator Response: Visually examine the XML document to ensure that it is valid, well-formed XML.

BWMUT1000W The transaction file cannot be deleted from the management server.

Explanation: The file cannot be deleted because it is write-protected, being used by another application, or does notexist.

Operator Response: Manually delete the transaction file from the ~/ManagementServer/TIMS/STI/trans/<transid >,where <transid> is the ID of the transaction that you must remove.

BWAUG1004E • BWMUT1000W


BWMUT1001E The selected transaction cannot be found.

Explanation: An IO Exception occurred while accessing a Synthetic Transaction Investigator transaction for editing.

Operator Response:

v Ensure that the database is up and running.

v Ensure that the user interface is displaying the most current data from the database. Determine if the directory orfile is in the database. If it is not, update the database to remove the entry for that task, and rerecord thetransaction.


BWMUT1001W The transaction directory cannot be deleted from the management server.

Explanation: The directory for the requested task ID cannot be deleted because it is write-protected, being used byanother application, or does not exist.

Operator Response:

v Manually delete the transaction file from the ~/ManagementServer/TIMS/STI/trans/<transid>, where <transid> is theID of the transaction that must be removed.


BWMUT1002E An error occurred while saving the transaction to disk.

Explanation: An IO Exception occurred while accessing a Synthetic Transaction Investigator transaction for editing.

Operator Response:

v Ensure that the database is up and running.


v Determine whether the transaction is read or write protected or otherwise corrupted.


BWMUT1004E The selected transaction part of a scheduled job.

Explanation: No additional information is available for this message.

BWAEP0001E Fatal error: Cannot authenticate with the Internet Management Server.

Explanation: This error indicates that an endpoint cannot establish authorization credentials with the InternetManagement Server. This error might occur for more than one reason. For example, the server could be down, therecould be a network failure preventing communication with the server, or the endpoint name does not match thename given to it when it was installed.

Operator Response:

v Ensure that the Internet Management Server computer is up and running.

v Verify that the network is available.

v Consult the traceBWAinstall.log file for the installed names of the endpoints. This file is located in the baseinstallation directory. The default base installation directory is one of the following:

– For Windows, C:\Program Files \Tivoli \Internet

– For AIX, /usr/Tivoli/Internet

– For other supported UNIX systems, /opt/Tivoli/Internet

BWMUT1001E • BWAEP0001E

Appendix D. Messages 147

BWAEP0002E Fatal error: Cannot access endpoint resource.

Explanation: This error indicates that there might be a database problem. An endpoint table database record cannotbe found.

Operator Response:


v If there has been any manual manipulation of the database recently, verify that the endpoint’s record has not beenaccidentally deleted from the endpoint table in the database.


BWAFW0001E Error occurred during retrieval of license information.

Explanation: The license service has been disabled, so this error should not occur.


BWAFW0002E Error starting "event log" service.

Explanation: This is a serious error. If the event log service cannot run, then, the only way to see event informationis to enable event tracing, or send SNMP traps, or e-mail as event responses. No logs will be available when usingthe web based user interface.


BWAFW0003E The application server is unable to start a web server.

Explanation: This is a serious error. If the web server component responsible for servicing the user and the endpointis not operational, the entire system is non-operational.


BWAFW0004E The database server is not responding to the close command request.

Explanation: This is a serious error. The database component must be operational for the management server tofunction properly. This error indicates an availability problem with the database caused by connectivity problems or aservice reliability problem on the database server.

Operator Response: Perform one or more of the following actions:




BWAEP0002E • BWAFW0004E


Appendix E. HTTP status codes

When you configure a Site Investigator or Synthetic Transaction Investigator job,you define the parameters for the investigation. One of those parameters enablesyou to identify the HTTP status codes for which you want events generated.

This section provides all HTTP status codes and their definitions. This informationis provided for your reference.

CODE INDICATION

2xx Success

200 OK; the request was fulfilled.

201 OK; following a POST command.

202 OK; accepted for processing, but processing is notcompleted.

203 OK; partial information—the returned information isonly partial.

204 OK; no response—request received but noinformation exists to send back.

3xx Redirection

301 Moved—the data requested has a new location andthe change is permanent.

302 Found—the data requested has a different URItemporarily.

303 See Other—response to the request can be foundunder another URI and should be retrieved using aGET method.

304 Not Modified—the document has not been modifiedas expected.

305 Use Proxy—requested resource must be accessedthrough the proxy provided in the location field.

306 Unused—no longer used; this code is reserved forfuture use.

4xx Error appears to be in the client

400 Bad request—syntax problem in the request or itcould not be satisfied.

401 Unauthorized—the client is not authorized to accessdata.

402 Payment required—indicates a charging scheme is ineffect.

403 Forbidden—access not required even withauthorization.

404 Not Found—server could not find the givenresource; the document does not exist.

407 Proxy Authentication Request—client must firstauthenticate itself with the proxy.

149

CODE INDICATION

415 Unsupported Media Type—server refusing to servicerequest because the request entity is in anunsupported format.

5xx Error appears to be in the server

500 Internal Error—the server could not fulfill therequest because of an unexpected condition.

501 Not implemented—the server does not support thefacility requested.

502 Bad Gateway—server received an invalid responsefrom an upstream server.

503 Service Unavailable—server unable to handlerequest due to temporary overload or maintenance.


Appendix F. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

151

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksIBM, the IBM logo, Tivoli, the Tivoli logo, AIX, DB2, Netview, Tivoli Enterprise,Tivoli Enterprise Console, WebSphere, and World Registry are trademarks orregistered trademarks of International Business Machines Corporation in theUnited States, other countries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation inthe United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Solaris Operating Environment, Java, and all Java-based trademarks are trademarksof Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marksof others.

Appendix F. Notices 153

Glossary

If you cannot find a term in this glossary, refer tothe IBM Dictionary of Computing that is locatedat the following Web site:

http://www.networking.ibm.com/nsg/nsgmain.htm

The IBM Dictionary of Computing definestechnical terms used in the documentation formany IBM products. It also includes IBM productterminology as well as selected terms anddefinitions from various industry sources.

A

access control. In computer security, the process ofensuring that the resources of a computer system canonly be accessed by authorized users in authorizedways. In Web Transaction Performance, access controlrestricts access to services and applications on theInternet Management Server.

access control list (ACL). A list associated with anobject that identifies all the subjects that can access theobject and their access rights; for example, a listassociated with a file that identifies users who canaccess the file and identifies their access rights to thatfile.

administrative domain. See domain.

administrator. A system or Web administrator who isauthorized to perform management tasks on the IBMTivoli Monitoring for Transaction Performance GUI.

application event. A warning, error, or status messagegenerated by a Web Transaction Performanceapplication. An application generates an event when aspecified constraint is exceeded or violated during jobexecution. See also event, system event.

authentication. Verification of the identity of a user orthe user’s eligibility to access an object.

authorization. The process of granting a user eithercomplete or restricted access to an object, resource, orfunction.

B

back-end service time. One of the time intervalsmeasured by the Quality of Service application. Theback-end service time is the time it takes for a Webserver to receive a requested transaction, process it, andrespond to it. See also transaction.

BAROC file (.baroc file). In the event server of theTivoli Enterprise Console, the internal representation ofthe defined event classes. Web Transaction Performanceprovides a BAROC (Basic Recorder of Objects in C) filefor event integration with the Tivoli Enterprise Console.

C

CA. See certificate authority.

certificate. A digital document obtained from aregistered certification authority (CA) that contains theidentity and public key for a user or systemcomponent. In Web Transaction Performance,certificates are used for securing the InternetManagement Server and the Quality of Service proxyserver.

certificate authority (CA). An organization that issuesand signs certificates. A CA authenticates the certificateowner’s identity, the services that the owner isauthorized to use, issues new certificates, renewsexisting certificates, and revokes certificates belongingto users who are no longer authorized to use them.

Cognos PowerPlay. A multidimensional reporting andanalysis package that is installed with Tivoli DecisionSupport. A number of PowerPlay tools are embeddedin Tivoli Decision Support.

constraint. A limit or boundary associated with aspecific application parameter. Constraints can includetime spans, activity totals, state changes, or contentfound or not found. When a constraint is exceeded orviolated, it creates an event, which is sent to themanagement server. The event is logged in theapplication and global event logs, then forwarded toany other configured recipients.

core services. Services provided by the InternetManagement Server that support the IBM TivoliMonitoring for Transaction Performance applications.These services include the event service, scheduler, datamanager, and framework security.

cube. A particular kind of data container used byCognos PowerPlay for multidimensional reporting.

155



D

data option. A command line option, used in silentinstallations or uninstallations, that specifies the sameinformation that you provide on a dialog wheninstalling or uninstalling a Web TransactionPerformance product component in interactive mode.For example, the data option -W tims.port="80"specifies that the Internet Management Server uses port80.

data warehouse. Space in a relational databasemanagement system (such as Oracle or DB2) that storesdata for use by an application. See also Tivoli EnterpriseData Warehouse, Web Services Courier data warehouse.

database. A collection of interrelated data organizedaccording to a database schema to serve one or moreapplications.

demilitarized zone (DMZ). In the world of softwareand computer networks, a screened network betweenthe enterprise (intranet) and the Internet.Communication between the DMZ and the intranet orInternet takes place under strictly controlled conditions.The DMZ is where Internet application servers (such asWeb, mail and ftp) are deployed.

DHCP. See Dynamic Host Configuration Protocol.

digital certificate. See certificate.

DMZ. See demilitarized zone.

DNS. See Domain Name System.

domain. On the Internet, that segment of an addressthat specifies an organization, its type, or its country oforigin. In general, the part of a computer network inwhich the data processing resources are under commoncontrol. The Web Transaction Performance domainconsists of all the elements that enable the core servicesand applications to function and that are managed bythe Internet Management Server. Also knownasadministrative domain.

domain name. In the Internet suite of protocols, aname of a host system. A domain name consists of asequence of subnames that are separated by a delimitercharacter. For example, if the fully qualified domainname (FQDN) of a host system is ralvm7.vnet.ibm.com,each of the following is a domain name:ralvm7.vnet.ibm.com, vnet.ibm.com, and ibm.com.

Domain Name System (DNS). The way that Internetdomain names are located and translated into Internetprotocol (IP) addresses. Because maintaining a centrallist of domain-name or IP-address correspondences isimpractical, the lists of domain names and IP addressesare distributed throughout the Internet in a hierarchy ofauthority.

Dynamic Host Configuration Protocol (DHCP). Aprotocol defined by the Internet Engineering Task Force(IETF) that is used for dynamically assigning IPaddresses to computers in a network.

E

encryption. A method of encoding messages toprovide privacy for communications as they move overintranets or the Internet. IBM Tivoli Monitoring forTransaction Performance applications use 128-bitencryption for maximum security.

endpoint. See Internet Management Endpoint.

Enterprise Transaction Performance. One of thecomponents of the IBM Tivoli Monitoring forTransaction Performance product. The EnterpriseTransaction Performance component providesfunctionality and features that help you analyze andimprove the performance of your business applications.See also Web Transaction Performance.

event. In Web Transaction Performance, a warning,error, or status message generated either by the InternetManagement Server (system event) or an application(application event). See also system event, application event.

event adapter. In IBM Tivoli Monitoring forTransaction Performance, software that converts eventsinto a format that the Tivoli Enterprise Console can useand then forwards the events to the Tivoli EnterpriseConsole event server.

event handler. In Web Transaction Performance,software that initiates an event response configured bythe Web Transaction Performance administrator.

event forwarding. See Tivoli Enterprise Console eventforwarding.

event response. A preconfigured action triggeredwhen an event is generated by a IBM Tivoli Monitoringfor Transaction Performance application or the InternetManagement Server. The Web Transaction Performanceadministrator can configure one or more responses tospecific event types. The possible event responsesinclude logging the event, notifying an individual orgroup by e-mail that the event has occurred, sendingthe event to an SNMP application, forwarding theevent to the Tivoli Enterprise Console, and initiating aprogram or script.

EXEC event handler. In Web Transaction Performance,an event handler that initiates a user-supplied script orprogram in response to an event.

extranet. A private, virtual network that uses accesscontrol and security features to restrict the usage of oneor more intranets attached to the Internet to selectedsubscribers (such as personnel from a sponsoringcompany and its business partners). See also intranet.


F

firewall. A gateway device that protects and controlsthe connection of one network to other networks. Thefirewall (a) prevents unwanted or unauthorizedcommunication traffic from entering the protectednetwork and (b) allows only selected communicationtraffic to leave the protected network.

framework services. See core services.

fully qualified domain name. In the Internet suite ofprotocols, the name of a host system that includes all ofthe subnames of the domain name. An example of afully qualified domain name is ralvm7.vnet.ibm.com.

G

Greenwich mean time (GMT). The mean solar time atthe prime meridian (0 degrees longitude) of Greenwich,England. Greenwich mean time is sometimes called Ztime or Zulu time. Although Greenwich mean time andcoordinated universal time are sometimes usedinterchangeably, they are not synonyms. Greenwichmean time is an approximate time. Because the secondis no longer defined in terms of astronomicalphenomena, the preferred name for this time scale iscoordinated universal time (UTC).

GUI. See Tivoli Web Solutions GUI

H

heartbeat. A signal that an endpoint sends to theInternet Management Server to convey that it is stillactive.

historical data collection. In IBM Tivoli Monitoringfor Transaction Performance, an application thatretrieves information stored in a database so that it canbe formatted and presented in reports to the user.

host name. In the Internet suite of protocols, the namethat is given to a machine. Sometimes, host name isused to mean fully qualified domain name. Other times, itis used to mean the most specific subname of a fullyqualified domain name. For example, ifrchland.vnet.ibm.com is the fully qualified domainname, either of the following can be considered thehostname: (a) rchland.vnet.ibm.com, or (b) rchland.

HTML. See Hypertext Markup Language.

HTTP. See Hypertext Transfer Protocol.

HTTP proxy server. An HTTP server that receivesrequests intended for another server and that acts onthe client’s behalf (as the client’s proxy) to obtain therequested service.

HTTPS. See Hypertext Transfer Protocol Secure.

HTTP transaction. A single HTTP request andresponse.

Hypertext Markup Language (HTML). A markuplanguage that is specified by an SGML document typedefinition (DTD) and is understood by all Web servers.

Hypertext Transfer Protocol (HTTP). The protocolthat is used to transfer and display hypertextdocuments. HTTP is the standard Web browserprotocol.

Hypertext Transfer Protocol Secure (HTTPS). Thestandard secure Web protocol. This protocol usesSecure Sockets Layer (SSL) encryption.

I

IBM HTTP Server. IBM’s Java servlet-basedapplication environment for building, displaying, andmanaging Web applications.

IBM Tivoli Monitoring for Transaction PerformanceGUI. The name applied to two separate graphical userinterfaces, one provided with the Enterprise TransactionPerformance component and the other provided withthe Web Transaction Performance component of theIBM Tivoli Monitoring for Transaction Performanceproduct. An administrator of a Web TransactionPerformance installation uses the IBM TivoliMonitoring for Transaction Performance GUI toschedule jobs, configure event responses, and performother activities required to measure the performanceand availability of Web services.

interactive mode. A method for installing oruninstalling a Web Transaction Performance productcomponent using a GUI. See also silent mode.

Internet Management Endpoint. A machine that isenabled, through installation of a specific softwarepackage, to perform work and provide information asdirected by the Internet Management Server. There arethree types of Internet Management Endpoint: Qualityof Service, Web Services Investigator, and Web ServicesCourier. The software package that defines eachendpoint type can include one or more primaryapplications (for example, the Quality of Serviceapplication is the primary application for the Quality ofService endpoint), the endpoint software, and any othersoftware required by the endpoint to perform its work.

Internet Management Server. A server that providesthe services and user interface required for centralizedmanagement of IBM Tivoli Monitoring for TransactionPerformance applications and resources. An InternetManagement Server and the Internet ManagementEndpoints registered to it together comprise a WebTransaction Performance administrative domain. Alsoknown as the management server and in some of theproduct code as the TIMS (Tivoli Internet ManagementServer).

Glossary 157

Internet protocol (IP) address. The unique 32-bitaddress that specifies the location of each device orworkstation on the Internet. For example, 9.67.97.103 isan IP address.

Internet service provider (ISP). An organization thatprovides access to the Internet.

intranet. A private network that integrates Internetstandards and applications (such as Web browsers)with an organization’s existing computer networkinginfrastructure. See also extranet.

ISP. See Internet service provider.

J

Java Database Connectivity (JDBC). An applicationprogramming interface (API) that has the samecharacteristics as Open Database Connectivity (ODBC)but is specifically designed for use by Java databaseapplications. For databases that do not have a JDBCdriver, JDBC includes a JDBC to ODBC bridge, which isa mechanism for converting JDBC to ODBC. JDBC wasdeveloped by Sun Microsystems, Inc., and variouspartners and vendors.

Java Development Kit (JDK). A software package thatcan be used to write, compile, debug, and run Javaapplets and applications.

Java Runtime Environment (JRE). A subset of theJava Development Kit (JDK) that contains the coreexecutables and files that constitute the standard Javaplatform. The JRE includes the Java Virtual Machine(JVM), core classes, and supporting files.

Java Virtual Machine (JVM). A softwareimplementation of a central processing unit (CPU) thatruns compiled Java code (applets and applications).

JDBC. See Java Database Connectivity.

JDK. See Java Development Kit.

job. In IBM Tivoli Monitoring for TransactionPerformance, the program-specific task that you createthrough the IBM Tivoli Monitoring for TransactionPerformance user interface, such as a site investigation.

JRE. See Java Runtime Environment.

JVM. See Java Virtual Machine.

K

key database file (keys.kdb file). A default controlfile that governs access to secure Web servers and theInternet Management Server. This file contains thedefault trusted root certificates supported by IBM,public keys, private keys, certificates, names of sites,and certificate authorities that are trusted and,

therefore, authorized for access. The InternetManagement Server and the Quality of Service proxyserver, when installed with secure communications,must be able to find a keys.kdb file in order to use acertificate from the file for authentication purposes.

key database password. The encrypted password to akey database file. The key database password is storedin a stash file. See also key database file, stash file.

L

language pack. A set of files that, when installed witha Web Transaction Performance product component,enables you to view the GUI or log files in a specificlanguage other than English.

log file descriptor. A list of objects, where each objectrepresents a Web log file entry. The log file descriptor isused to determine the order or format of the Web logfile entries.

logical server cluster. The logical name of a cluster ofWeb servers.

M

management repository. A collection of tables in arelational database management system (RDBMS) thatis used by the Internet Management Server to store jobinformation, events, and other data needed to supportWeb Transaction Performance functions. Themanagement repository is created in the RDBMSduring installation.

management server. See Internet Management Server.

N

native launcher. The executable file that starts aninstallation, upgrade, or uninstall program on aparticular platform. For example, setup_TIMS_w32.exeis the native launcher that starts the installationprogram for the Internet Management Server onWindows platforms.

NetView. See Tivoli NetView.

Network File System (NFS). A protocol that allowsany host in a network to mount another host’s filedirectories. When mounted, the file directory appearsto reside on the local host. The NFS protocol wasdeveloped by Sun Microsystems, Inc.

normalization. A mechanism that prevents triggeringan event when a numeric attribute crosses but remainsnear a threshold. The normalization mechanism worksby creating a buffer zone that the attribute must leavebefore the recovery event is triggered. The size of thebuffer is defined as a percentage of the threshold.


O

option file. A file, used in silent mode installations oruninstallations, that contains data required by theinstallation or uninstallation program. Also known as aresponse file. See also silent mode.

origin server. A Web server monitored by the Qualityof Service application. Also known as origin HTTPserver. See also Quality of Service proxy server.

P

Page Analyzer Viewer feature. A feature of the STIPlayer that measures how long it takes to retrieve thevarious sub-documents (such as java script, stylesheets, and images) that make up a Web page to berendered. Page Analyzer Viewer statistics are displayedon the Web Transaction Performance user interface. ThePage Analyzer Viewer engine resides with the STIPlayer on a Web Services Investigator endpoint. ThePage Analyzer Viewer engine is also called WebDetailer.

page display time. One of the time intervals measuredby the Quality of Service application. The page displaytime is the time it takes to render a Web page on therequestor’s browser, from the time the rendering beginsuntil it is complete.

PDF. See Portable Document Format (PDF)

Portable Document Format (PDF). A standardspecified by Adobe Systems, Inc., for the electronicdistribution of documents.

proxy server. A server that receives requests intendedfor another server and that acts on behalf of the client(as the client’s proxy) to obtain the requested service. Aproxy server is often used when the client and theserver are incompatible for direct connection (forexample, when the client is unable to meet the securityauthentication requirements of the server but should bepermitted some services).

Q

Quality of Service. One of the Web TransactionPerformance applications. The Quality of Serviceapplication samples HTTP transactions against a Webserver and measures various time intervals involved incompleting each transaction. The time intervals that theQuality of Service application measures include theuser experience time, back-end service time, and pagedisplay time.

Quality of Service endpoint. The InternetManagement Endpoint that runs Quality of Serviceapplication jobs. The software provided when you

install a Quality of Service endpoint includes theQuality of Service application and the Quality ofService proxy server.

Quality of Service proxy server. An IBM HTTPServer, installed with the Quality of Service endpoint,that acts as a proxy for a Web server (called the originserver) to be monitored by the Quality of Serviceapplication. See also origin server.

R

RDBMS. See relational database management system.

realm. A name used by a browser in correlation witha URL to save the password information you enter sothat it can authenticate automatically on the nextchallenge.

registered endpoint. An Internet ManagementEndpoint that is recognized by the InternetManagement Server. The Internet ManagementEndpoint installation program registers the endpoint tothe Internet Management Server specified on theInternet Management Server Information dialog.

relational database management system. A relationaldatabase program that contains all the necessaryprograms, programming tools, and documentationrequired to create, install, and maintain customdatabase applications.

Relative Uniform Resource Locator (RURL). A stringof characters that specifies the file name of a resourcebut not its absolute location. See also Uniform ResourceLocator (URL).

response file. See option file.

round-trip time. See user experience time.

RURL. See Relative Uniform Resource Locator (RURL).

S

secure server. In Web Transaction Performance, anInternet Management Server or Quality of Serviceproxy server that uses the Secure Sockets Layer (SSL) toenable secure communications.

Secure Sockets Layer (SSL). A secure protocol thatenables data to be encrypted and enables clients toauthenticate a server in client-server communication.

self-signed certificate. A digital certificate that is usedto establish secure communications temporarily untilreplaced by a permanent certificate issued by acertificate authority. See also certificate.

servlet. See Java servlet.

Glossary 159

setup launcher. The native launcher that starts aninstallation program.

severity level. Designates the importance assigned toan event. The severity level determines the action thatthe system takes in response to the event (the eventresponse). There are six severity levels, ranging fromUnknown (lowest) to Error (highest). See also eventresponse.

silent installation. See silent mode.

silent mode. A method for installing or uninstalling aWeb Transaction Performance product component fromthe command line with no GUI display. When usingsilent mode, you specify the data required by theinstallation or uninstallation program directly on thecommand line or in a file (called an option file orresponse file). See also interactive mode.

Simple Mail Transfer Protocol (SMTP). In theInternet suite of protocols, an application protocol fortransferring mail among users in the Internetenvironment. SMTP specifies the mail exchangesequences and message format. It assumes that theTransmission Control Protocol (TCP) is the underlyingprotocol.

Simple Network Management Protocol (SNMP). Inthe Internet suite of protocols, a network managementprotocol that is used to monitor routers and attachednetworks. SNMP is an application layer protocol.Information on managed devices is defined and storedin the application’s Management Information Base(MIB).

Site Investigator. One of the Web TransactionPerformance applications. The Site Investigatorapplication crawls a Web site for missing and damagedlinks, and scans for specified content.

SMTP. See Simple Mail Transfer Protocol (SMTP).

SNMP. See Simple Network Management Protocol(SNMP).

SOCKS server. A circuit-level gateway that provides asecure one-way connection through a firewall to serverapplications in a network that is not secure.

SSL. See Secure Sockets Layer (SSL).

stash file (keys.sth file). A file that contains a keydatabase password. A secure Internet ManagementServer or Quality of Service proxy server expects tofind the key database file and its corresponding stashfile in the same directory. See also key database file, keydatabase password.

STI Player. One of the components of the SyntheticTransaction Investigator application. The STI Playerreplays a Web transaction that was recorded by the STIRecorder. The STI Player is included when you install a

Web Services Investigator endpoint on a Windowssystem. You can schedule an STI playback job to repeatat different times and from different endpoints in orderto evaluate performance and availability under varyingconditions. Also known as STI Playback.

STI Recorder. One of the components of the SyntheticTransaction Investigator application. The STI Recorderrecords the sequence of steps that make up a specificWeb transaction, such as enrolling in a class or viewingan account. The mechanism for recording is to save allHTTP request information in an XML document. Youcan install the STI Recorder on any Windows machine.You do not need to install the STI Recorder on anInternet Management Endpoint.

Synthetic Transaction Investigator. One of the WebTransaction Performance applications. SyntheticTransaction Investigator measures how users mightexperience a Web site in the course of performing aspecific Web transaction. The Synthetic TransactionInvestigator application consists of two components:the STI Recorder, which records Web transactions, andthe STI Player, which plays back the recordedtransactions from one or more Web ServicesInvestigator endpoints. See also STI Recorder, STI Player.

system event. A warning, error, or status messagegenerated by the Internet Management Server. Systemevents are typically generated as a result ofauthentication problems, event handling failures, orendpoint communication problems. See also event,application event.

T

tablespace. In relational database managementsystems, an abstraction of a collection of containers inwhich database objects are stored.

TCP/IP. See Transmission Control Protocol/InternetProtocol (TCP/IP).

TEC. See Tivoli Enterprise Console (TEC).

timeout. A time interval allotted for certain operationsto complete; for example, the period of time allotted fora response before a system operation is interrupted andmust be restarted.

time stamp. The value on an object that is anindication of the system time at some critical point inthe history of the object.

Tivoli Enterprise Console (TEC). A Tivoli softwareproduct that collects, processes, and automaticallyinitiates corrective actions for system, application,network, and database events. The Tivoli EnterpriseConsole provides a centralized, global view of thenetwork computing environment; it uses distributedevent monitors to collect information, a central event


server to process information, and distributed eventconsoles to present information to systemadministrators.

Tivoli Enterprise Console event forwarding. In WebTransaction Performance, an optional feature thatenables a Web Transaction Performance administratorto arrange for events of specifiedtypes to be forwardedto the Tivoli Enterprise Console. Events are forwardedto the Tivoli Enterprise Console through the WebServices Courier endpoint.

Tivoli Enterprise Data Warehouse. A central datastore where historical data from many managementapplications can be aggregated and correlated for useby reporting and third-party online analyticalprocessing (OLAP) tools as well as planning, trending,analysis, accounting, and data mining tools. The TivoliEnterprise Data Warehouse provides a report interfacethat can be used to generate simple Web-basedhistorical reports.. Web Transaction Performance sendsdata collected by the STI Player and Quality of Serviceapplications to the Tivoli Enterprise Data Warehouse.

Tivoli NetView. A Tivoli product that enablesdistributed network management across multipleoperating systems and protocols.

topic. In Tivoli Decision Support, the overall questionfor which database views are created to answer.

transaction. (1) A typical activity that a user performson a Web site, such as searching for information,enrolling in a class, or ordering a product. (2) An HTTPtransaction.

Transmission Control Protocol/Internet Protocol(TCP/IP). (1) The Transmission Control Protocol andthe Internet Protocol, which together provide reliableend-to-end connections between applications overinterconnected networks of different types.

(2) The suite of transport and application protocols thatrun over the Internet Protocol.

trusted root. In the Secure Sockets Layer (SSL), thepublic key and associated distinguished name of acertificate authority (CA).

U

Uniform Resource Identifier (URI). In HTTP, a stringof characters that identifies an Internet resource. Thereare two types of URIs: Uniform Resource Locators(URLs) and relative URLs (RURLs).

Uniform Resource Locator (URL). A string ofcharacters that identifies the type and location of anInternet resource. A URL consists of a domain name, adescription of the resource’s location, and the name ofthe resource itself, separated by full stops andbackslashes.

URI. See Uniform Resource Identifier (URI).

URL. See Uniform Resource Locator (URL).

user experience time. One of the time intervalsmeasured by the Quality of Service application. Theuser experience time is the time it takes to complete asingle HTTP transaction. Also known as round-trip time.

UTC. See Greenwich Mean Time.

V

virtual host. A single computer system using Webserver software to host more than one IP address (ordomain) at a time.

W

Web Services Courier data warehouse. The datawarehouse where Web Transaction Performance storesdata that is used for creating historical reports. TheWeb Services Courier data warehouse is initializedwhen you install a Web Services Courier endpoint.

Web Services Courier endpoint. The InternetManagement Endpoint that collects data for historicalreports and forwards events to the Tivoli EnterpriseConsole. The historical data collection software on theendpoint uses the Web Services Courier datawarehouse to store the data for historical reports. Thedata is also forwarded to the Tivoli Enterprise DataWarehouse.

Web Services Investigator endpoint. The InternetManagement Endpoint that contains the SiteInvestigator application, and on Windows systems, theSTI Player and the Page Analyzer Viewer engine.

Web Transaction Performance. One of thecomponents of the IBM Tivoli Monitoring forTransaction Performance product. The Web TransactionPerformance component is a centrally managed suite ofapplications that monitors the availability andperformance of Web-based services. See also EnterpriseTransaction Performance.

Glossary 161

Index

Special characters/lib/properties.jar file 131/qosm.html file 50./startserver.sh command 125./stopserver.sh command 125

Aaccessibility 127

about xviadministrator

functions in the Web servicesenvironment 8

apach-rproxy.conf-servers file 140application data

managing 95application events

defined 9Application Response Measurement

(ARM) APISee ARM 17, 71

Application Response Measurement APISeeARM 4

archiving offline endpoints 95ARM

agent, about 71API, about 71collecting data for specific requests in

an STI Player job 21correlation, about 71defined 4, 17enabling ARM data collection for

WebSphere in Web TransactionPerformance 21

enabling data collection forWebSphere in Enterprise TransactionPerformance 19

example of data collection inWebSphere Application Server 18

example of support in IBMWebSphere Application Server 18

support in IBM WebSphereApplication Server 17

ARM agentdefined 17

ARM API callsdefined 17

arm_start( ) calls 19arm_stop( ) calls 19

Bback-end service time

defined 44defined for Quality of Service 29defined in Quality of Service 1example in Quality of Service 9

booksonline xiiordering xii

books (continued)providing feedback xii

Ccentral data warehouse ETL

defined 11cleanDW.bat command script 138cleanDw.sh command script 138cmd.exe command 111Cognos PowerPlay

about 99Cognos Transformer

about 99comma-separated values (CSV) file

defined 99commands

./startserver.sh 125

./stopserver.sh 125cleanDW.bat 138cleanDw.sh 138cmd.exe 111regedit32 139startep.sh 124startms.sh 124stopep.sh 124stopms.sh 124

communications protocolsHTTPS, HTTP 14

constraintsprocedure for configuring in Synthetic

Transaction Investigator 69core services

used by Internet ManagementServer 6

correlatedefined 17

correlationsdefined 17

correlatorsdefined 17

CSV filedefined 99

Cube Transform Status dialogusing to check status of cube-building

process 99CubeName_dt.txt

file 103cubes

adjusting date range for 99building for Tivoli Decision

Support 99Cube Transform Status dialog 99defined 99problem determination for

building 102procedure for scheduling builds 100using Tivoli Discovery Administrator

for building 99Customer Support

Web site for contacting xvi

Ddata mart ETL

defined 11data marts

defined 11data warehouse

Web Services Courier 7debugging

starting 131Demilitarized Zone

See DMZ 13Discovery Administrator

about linking to databases 99discovery guide

Web Transaction Performance topicsand views 101

discovery guidesdefined 8typical installation setup of Web

Transaction Performance 16Web Transaction Performance 5

Discovery Interfaceabout report viewing 99

DMZdefined 13installation requirement for Quality of

Service endpoint 29

Ee-mail accounts

forwarding events to 108EAAConfig.properties file 142EDAdmin.exe file 100EJBs

as components of transactionperformance applications 18

endpoint.log file 133, 134, 138endpoints

archiving offline 95as serviced by Internet Management

Server 6defined 5viewing all 91

Enterprise JavaBeansSee EJB 18

Enterprise Transaction Performancecomponent of IBM Tivoli Monitoring

for Transaction Performance,about xi

error logs file 133event forwarding 16

about managing in Web TransactionPerformance 119

to an SNMP managementapplication 120

to Tivoli Enterprise Console 119using SMTP to send to an e-mail

account 121

163

event logexamining Quality of Service 42Quality of Service, drilling down

into 43viewing Quality of Service 42

event logsviewing in Site Investigator 55

event responsesabout creating 94about managing 105creating 106defined 9, 105

event serviceabout managing in Web Transaction

Performance 119event types

for Quality of Service 40for Site Investigator 54Synthetic Transaction Investigator 73

event.properties file 108, 121events

configuring 112configuring for Site Investigator 54configuring severities 92configuring Synthetic Transaction

Investigator 73configuring system types 94configuring system types of 92defined 9, 105forwarding data using EXEC

service 110forwarding to an e-mail account 108forwarding to an SNMP management

application 107forwarding to the EXEC service 109forwarding to Tivoli Enterprise

Console 106procedure for configuring Synthetic

Transaction Investigator 74procedure for viewing Synthetic

Transaction Investigator 74Quality of Service types defined 115severity levels 105, 112Site Investigator types defined 116stored in management

respository 105Synthetic Transaction Investigator

event drill down 75Synthetic Transaction Investigator

types defined 116system types 94system types defined 92, 113types defined 113view global log 94viewing global log 90

examplesARM data collection in WebSphere

Application Server 18ARM support in IBM WebSphere

Application Server 18collecting ARM data for specific

requests in an STI Player job 21STI Recorder and Web Services

Investigator endpoint componentsand data flow 15

examples (continued)system configuration of IBM Tivoli

Monitoring for TransactionPerformance components 12

EXEC serviceforwarding event data to 110forwarding events to 109

extended tracing (cswa tracing) 133

Ffiles

/lib/properties.jar 131/qosm.html 50apach-rproxy.conf-servers 140CSV 99CubeName_dt.txt 103EAAConfig.properties 142EDAdmin.exe 100endpoint.log 133, 138error logs 133event.properties 121httpd.conf 140logging.properties 131mail.smtp.host 121parser.properties 133properties.jar 133qos.conf 140, 141ReportConfig.properties 43, 75, 76setup_sti_recorder.exe 58, 59snmp.properties 108, 120sti-playback.properties 131task.properties 133timsiu.log 129trace.components 131trans.XML 135twsa_1.log 132TWSM.mib 120uilogging.properties 129

firewall zonesin Web services environment 13

Gglobal event log

view 94viewing 90

global viewsabout 90GUI tasks for Web Transaction

Performance 89graphing

real-time for Quality of Service 30graphs

viewing Synthetic TransactionInvestigator availability 77

viewing Synthetic TransactionInvestigator average responsetime 77

viewing Synthetic TransactionInvestigator round trip time 77

GUIoverview 25parts defined 26procedure for starting 25viewing navigation tree choices 26

GUI (continued)Web Transaction Performance 89

GUIsabout product naming in 6Enterprise Transaction Performance 6Web Transaction Performance 6

Hhandbook

Customer Support, Web site for xviheadless mode

defined as default for SyntheticTransaction Investigator 131

Help buttonabout GUI 26

historical data collectionconfiguring jobs for 90defined 9for Web Transaction Performance 89for Web Transaction Performance

jobs 10problem determination for 132, 138viewing results from Web Transaction

Performance jobs 10viewing the event log 90

historical data collection softwareabout using with Web Services

Courier data warehouse 7historical data collections

problem determination for 134HTTP

nonsecure communicationsprotocol 14

HTTP status codesdefined 149

HTTP transactiondefined 1

httpd.conf file 140HTTPS

secure communications protocol 14

IIBM HTTP server

configured as reverse proxyserver 29

Quality of Service endpointrequirement 29

IBM HTTP Serveras Quality of Service endpoint proxy

server 7management server software 6

IBM Tivoli Monitoring for TransactionPerformance

component of IBM Tivoli Monitoringfor Transaction Performance,about xi

components, operating systemssupported for xi

installationabout installable Web Transaction

Performance components 4downloading STI Recorder 58STI Recorder in Synthetic Transaction

Investigator 59


installation (continued)typical setup for Tivoli Decision

Support discovery guides 16typical setup of Quality of Service

application endpoints 15typical setup of STI Recorder

endpoints 15typical setup of Web Services Courier

endpoints 16typical setup of Web Services

Investigator endpoints 15Internet Management Endpoints

defined 5Quality of Service type 6Web Services Courier type 6Web Services Investigator type 6

Internet Management Serveras installable IBM Tivoli Monitoring

for Transaction Performancecomponent 6

component overview 5starting and stopping on UNIX

systems 123, 124starting and stopping on Windows

systems 123, 124typical setup of 14

item properties windowin Page Analyzer Viewer 87

JJava server pages

See JSP 18Java servlets

as components of transactionperformance applications 18

jobsconfiguring schedules for Synthetic

Transaction Investigator 67creating and scheduling in the Web

services environment userinterface 8

deleting unscheduled SyntheticTransaction Investigator 73

managing Synthetic TransactionInvestigator 72

playback, about configuring inSynthetic TransactionInvestigator 70

playback, procedure for configuring inSynthetic TransactionInvestigator 70

procedure for assigning names inSynthetic TransactionInvestigator 70

unscheduling Synthetic TransactionInvestigator 72

JSPas components of transaction

performance applications 18

Kkeys

qoscolumns 43socksProxyHost 121

keys (continued)sticolumns 75values defined for qoscolumns 43

Llegend window

in Page Analyzer Viewer 83log files

viewing 97logging and tracing

starting 131logging.properties file 131

Mmail.smtp.host file 121management repository

defined 6used for storing events 105

management server 6defined 5user interface 5

manualsonline xiiordering xiiproviding feedback xii

messagesfor Web Transaction Performance 143

Nnaming

about product in the GUIs 6navigation tree

viewing choices 26

Oonline

accessing publications xvOpen Group

Application Response Measurement(ARM) API a Technical Standard 4

operating systemssupported for IBM Tivoli Monitoring

for Transaction Performancecomponents xi

origin serverdefined 7

origin serversdefined 15

PPage Analyzer Viewer

about transaction reports for SyntheticTransaction Investigator jobs 78

about using with STI Player 3chart 81connection setup time 82delivery time 83display window 80engine for Web Services Investigator

endpoint 7

Page Analyzer Viewer (continued)host name resolution time 82item properties window 87legend window 83navigation tree 81page properties window 86server response time 82SSL connection setup time 82sub document transactions monitoring

by 79total request time 82tree 84viewing Page Analyzer Viewer

report 80page display time

defined for Quality of Service 29Page display time

defined in Quality of Service 1page properties window

in Page Analyzer Viewer 86page render time

defined 44defined in Quality of Service 1

parent transactionsdefined 17

parser tracing 133parser.properties file 133problem determination

cube builds 102for historical data collection 132, 138for historical data collections 134for Quality of Service endpoints 139for Synthetic Transaction

Investigator 131, 134starting logging and tracing for 131Tivoli Decision Support 102Tivoli Decision Support report

problems 104properties.jar file 133proxy information

configuring in Synthetic TransactionInvestigator 68

proxy serverfor Quality of Service endpoint 7

proxy serversdefined 15Quality of Service, procedures for

stopping and starting onUNIX-based systems 125

Quality of Service, procedures forstopping and starting on Windows2000 systems 125

Quality of Service, procedures forstopping and starting on WindowsNT systems 125

publicationsaccessing online xvcustomer feedback survey for xvIBM Tivoli Enterprise Console,

prerequisite for Web TransactionPerformance xiii

IBM WebSphere Application Server,prerequisite for Web TransactionPerformance xiv

online xiiordering xii, xvproviding feedback xii

Index 165

publications (continued)providing feedback about xvTivoli Decision Support, prerequisite

for Web TransactionPerformance xiv

Tivoli Enterprise Data Warehouse,prerequisite for Web TransactionPerformance xiv

Qqos.conf file 140, 141qoscolumns key 43

values defined for 43Quality of Servic

about 29Quality of Service

about 1about using with STI Player 4back-end service time 44back-end service time defined 29back-end service time defined in 1back-end service time example in 9drilling down into event log 43endpoint defined 29endpoint, software included for 7endpoints, problem determination

for 139event types 40event types defined 115examining the event log in 42IBM HTTP Server as proxy server for

the endpoint 7page display time defined 29page render time in 44procedure for configuring events

in 40procedure for configuring job

constraints in 35procedure for configuring job

parameters for 33procedure for creating job schedules

for 31procedure for deleting unscheduled

jobs in 39procedure for editing jobs in 38procedure for managing jobs in 38procedure for naming jobs in 37procedure for scheduling jobs in 39procedure for selecting an endpoint

in 31procedures for configuring jobs 30proxy server for endpoint 7proxy servers, procedures for stopping

and starting on UNIX-basedsystems 125

proxy servers, procedures for stoppingand starting on Windows 2000systems 125

proxy servers, procedures for stoppingand starting on Windows NTsystems 125

real-time graphing component for 30round trip time defined in 1type of Internet Management

Endpoint 6

Quality of Service (continued)typical installation setup of

endpoints 15user experience time and round trip

time defined in 44user experience time defined 29user scenarios 30viewing report ins 43viewing the event log 42Web Transaction Performance

application, about 1

RRDBMS

about installing 14real-time graphing component

for Quality of Service 30regedit32 command 139ReportConfig.properties file 43, 75, 76reports

Page Analyzer Viewer 78Synthetic Transaction Investigator

event drill down 75Synthetic Transaction Investigator

overall transaction success rate 78viewing in Quality of Service 43viewing Page Analyzer Viewer 80

reverse proxy serverIBM HTTP server configured as 29

reverse proxy serversdefined 15

round trip timedefined 1defined as user experience time 44measuring in Synthetic Transaction

Investigator 76round-trip time

about measuring using STI Player 4defined for Synthetic Transaction

Investigator 58using STI Player to measure 3

SSecure Sockets Layer (SSL)

Tivoli Web Component Managersecurity protocol 14

service timedefined for Synthetic Transaction

Investigator 58defined in Quality of Service 1using STI Player to provide

measurements of 4setup_sti_recorder.exe file 58, 59severity levels

for events 112Site Investigator

about 1, 45event types 54event types defined 116examining event logs in 55procedure for configuring events

in 54procedure for configuring job

parameters in 48

Site Investigator (continued)procedure for configuring job

schedules in 47procedure for configuring jobs

constraints in 50procedure for configuring proxies for

jobs in 50procedure for creating new job

schedules in 47procedure for deleting unscheduled

jobs in 54procedure for editing jobs in 53procedure for managing jobs in 53procedure for naming jobs in 53procedure for selecting endpoints

in 47procedure for unscheduling jobs

in 53procedure for viewing results of

completed site investigations 55procedures for configuring jobs in 46user scenarios for 45Web Transaction Performance

application, about 1SMTP

using SOCKS server to access 121using to forward events to an e-mail

account 121SNMP

configuring servers 120event forwarding to 120forwarding events to 107

snmp.properties file 108, 120SOCKS server

using to access SMTP server 121socksProxyHost key 121SSL

Secure Sockets Layer securityprotocol 14

startep.sh command 124startms.sh command 124status codes

HTTP types defined 149STI

See Synthetic TransactionInvestigator 2

STI Playerabout 2about playback jobs 3capabilities 2collecting ARM data for specific

requests in a job 21measuring round-trip time 3using with ARM data collection 4with Page Analyzer Viewer 3with Quality of Service 4

STI Recorderabout 2endpoints, typical installation setup

of 15example with Web Services

Investigator endpoint componentand data flow 15

installable component of WebTransaction Performance 8

installable Web TransactionPerformance component 5


STI Recorder (continued)using 62

sti-playback.properties file 131sticolumns key 75

values defined for SyntheticTransaction Investigator 75

stopep.sh command 124stopms.sh command 124sub-transactions

defined 17Synthetic Transaction Investigator

about 2, 57about configuring playback jobs

in 70about monitoring tasks 131availability graphs 77average response time graphs 77configuring events 73configuring job schedules 67configuring proxy information 68deleting transactions 66deleting unscheduled jobs 73downloading the STI Recorder in 58editing recorded transactions 66editing transaction playbacks 72event drill down 75event types 73event types defined 116installing

STI Recorder for 59managing jobs 72measuring round trip (user

experience) time 76overall transaction success rate

report 78playback jobs 70problem determination for 131, 134procedure for assigning job names

in 70procedure for configuring

constraints 69procedure for configuring events 74procedure for creating transaction

playbacks in 67procedure for viewing events 74round trip time graphs 77round-trip time defined for 58running in visible mode 131service time defined for 58sticolumns key values defined 75Transaction Details table 78unscheduling jobs 72user scenarios 58using Page Analyzer Viewer to view

transactions in 78using the STI Recorder 62Web Transaction Performance

application, about 1system administration

GUI tasks for Web TransactionPerformance 89

system event logsviewing 94

system eventsconfiguring 92, 94defined 113types defined 92

Ttask tracing 133task.properties file 133timsiu.log

user interface log file 129Tivoli Decision Support

about 8as Web Transaction Performance

discovery guide 5cube build problem

determination 102cube building 99prerequisite publications for Web

Transaction Performance xivproblem determination for historical

data collection 138problem determination of report

problems 104topics and views 101troubleshooting 102typical installation setup of Web

Transaction Performance discoveryguides 16

using to monitor Synthetic TransactionInvestigator tasks 131

Web Transaction Performancediscovery guide 8

Tivoli Decision Support Guideoverview 99

Tivoli Discovery Administratorcube building using 99

Tivoli Discovery Interfaceusing topics and views 101

Tivoli Enterprise Consoleevent forwarding from Web Services

Courier endpoint 16event forwarding to 106prerequisite publications for Web

Transaction Performance xiiisummary of integration with Web

Transaction Performance 11Tivoli Enterprise Console (TEC)

event-forwarding feature of WebServices Courier endpoint 7

Tivoli Enterprise Data Warehouseabout transferring data from Web

Services Courier data warehouse 7prerequisite publications for Web

Transaction Performance xivsummary of integration with Web

Transaction Performance 11Tivoli Error Message Standard

about 143Tivoli management agent

as part of a Tivoli Enterpriseinstallation 13

using to forward events from WebServices Courier endpoints 16

Tivoli Web Component ManagerSSL security protocol 14

TivoliStiPlayback user accountusing for configuring playback jobs in

Synthetic TransactionInvestigator 70

topics and viewsusing in Tivoli Discovery

Interface 101

trace.components file 131tracing

extended tracing (cswa tracing) 133parser 133task 133

tracing and loggingstarting 131

trans.XML file 135Transaction Details table

viewing Synthetic TransactionInvestigator 78

transaction playbacksediting Synthetic Transaction

Investigator 72procedure for creating in Synthetic

Transaction Investigator 67transaction total request time

in Page Analyzer Viewer 82transactions

connection attempt failed in PageAnalyzer Viewer 83

defined 17host name resolution time in Page

Analyzer Viewer 82SOCKS connection setup time in Page

Analyzer Viewer 82SSL connection setup time in Page

Analyzer Viewer 82transaction delivery time in Page

Analyzer Viewer 83transaction server response time in

Page Analyzer Viewer 82transactions, sub document

how Page Analyzer Viewermonitors 79

troubleshootingTivoli Decision Support 102

twsa_1.log file 132TWSM.mib file 120typeface conventions xvi

Uuilogging.properties

user interface tracing file 129user accounts

managing 95user experience time

defined 1defined as round trip time 44defined for Quality of Service 29measuring in Synthetic Transaction

Investigator 76user interface

for Web Transaction Performance 6in the Web services environment 8

user interface log filetimsiu.log 129

user interface tracing fileuilogging.properties 129

user scenariosfor Quality of Service 30for Site Investigator 45for Synthetic Transaction

Investigator 58

Index 167

Wwarehouse enablement packs

defined 11warehouse packs

defined 11Web Detailer

defined 7Web Services Courier

endpoints, typical installation setupof 16

endpoints, using to forward events toTivoli Enterprise Console 16

problem determination for historicaldata collection 138

type of Internet ManagementEndpoint 6

Web Services Courier data warehouseabout transferring data to Tivoli

Enterprise Data Warehouse 7about using historical data collection

software with 7feature of Web Services Courier

endpoint 7Web Services Courier endpoint

software included with 7Tivoli Enterprise Console (TEC)

event-forwarding feature of 7Web Services Courier data warehouse

feature of 7Web services environment

firewall zones 13Web Services Investigator

endpoints, typical installation setupof 15

example with STI Recordercomponent and data flow 15

type of Internet ManagementEndpoint 6

Web Services Investigator endpointPage Analyzer Viewer engine for 7Site Investigator application for 7software included with 7

Web Transaction Performanceabout installable components in 4about managing event forwarding

in 119about managing the event service

in 119about the GUI 89configuring SNMP servers in 120discovery guide 8discovery guide topics and

views 101discovery guides 5event forwarding to an SNMP

management application 120event forwarding to Tivoli Enterprise

Console 119global views GUI tasks for 89GUI overview 25historical data collection GUI tasks

for 89IBM Tivoli Enterprise Console

publications prerequisite xiiiIBM WebSphere Application Server

publications prerequisite xivinstalling discovery guides 16

Web Transaction Performance (continued)navigation overview 25overview 1procedure for configuring the

server 121Quality of Service application,

about 1Site Investigator application, about 1Synthetic Transaction Investigator

application, about 1system administration GUI tasks

for 89Tivoli Decision Support publications

prerequisite xivTivoli Enterprise Data Warehouse

publications prerequisite xivuser preferences GUI tasks for 89using to monitor Synthetic Transaction

Investigator tasks 131WebSphere Application Server

ARM support in 17enabling ARM data collection for in

Web Transaction Performance 21enabling ARM data collection in

Enterprise TransactionPerformance 19

example of ARM support in 18prerequisite publications for Web

Transaction Performance xivWebSphere Site Analyzer

about 12WebSphereApplication Server

about 12


��

Printed in U.S.A.

SC23-4802-00

publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/itmftp/sc23-4802-00/en... · 2003-10-04 ·...

Documents