publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/itmftp/gc23-4801... · contents figures...

IBM Tivoli Monitoring for Transaction PerformanceWeb Transaction Performance

Installation GuideVersion 5.1.0

GC23-4801-00

��

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

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 . . . . . . 11IBM Tivoli Enterprise Console . . . . . . . 11Tivoli Enterprise Data Warehouse . . . . . . 11Tivoli Decision Support . . . . . . . . . 12IBM 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 . . . . . . 18Collecting WebSphere ARM data in EnterpriseTransaction Performance . . . . . . . . . 19Collecting WebSphere ARM data in WebTransaction Performance . . . . . . . . . 21

Chapter 2. System and softwarerequirements . . . . . . . . . . . . 25Supported operating systems . . . . . . . . 26

System requirements for the Internet ManagementServer . . . . . . . . . . . . . . . . 27Prerequisite software for the Internet ManagementServer . . . . . . . . . . . . . . . . 28System requirements for Internet ManagementEndpoints and the STI Recorder . . . . . . . 29Prerequisite software for Internet ManagementEndpoints and the STI Recorder . . . . . . . 30Requirements for Tivoli Enterprise Console eventforwarding . . . . . . . . . . . . . . 32

Importing the BAROC file . . . . . . . . 32Additional requirements for forwarding eventsthrough a Tivoli environment . . . . . . . 33

Browser requirements for the IBM Tivoli Monitoringfor Transaction Performance GUI . . . . . . . 34Supported languages . . . . . . . . . . . 35

Chapter 3. RDBMS requirements . . . 37Supported relational database management systems 37Oracle configuration . . . . . . . . . . . 38

Sample SQL script for creating fixed tablespace 39Sample SQL script for creating flexible tablespace 40

DB2 configuration . . . . . . . . . . . . 41Creating the database . . . . . . . . . . 42Creating the database user . . . . . . . . 42Creating a bufferpool . . . . . . . . . . 43Creating tablespace . . . . . . . . . . . 44Assigning permissions to the database user. . . 44Optimizing the DB2 database configuration . . 45Setting up a DB2 client connection. . . . . . 45Sample shell script for DB2 configuration . . . 46

Chapter 4. Installation overview androad map. . . . . . . . . . . . . . 49Installation, upgrade, and uninstall programs . . . 49Installation overview . . . . . . . . . . . 50

Interactive and silent mode . . . . . . . . 51Native launchers . . . . . . . . . . . 51Command line options . . . . . . . . . 52Default installation directories . . . . . . . 52Specifying a location for temporary files . . . . 53

Installation road map . . . . . . . . . . . 54

Chapter 5. Upgrading existinginstallations . . . . . . . . . . . . 55Upgrade programs . . . . . . . . . . . . 56Planning for the upgrade . . . . . . . . . . 56Upgrading the management server and mostendpoints . . . . . . . . . . . . . . . 57Upgrading the data warehouses . . . . . . . 62Upgrading Web Services Investigator endpoints onWindows . . . . . . . . . . . . . . . 63

iii

Chapter 6. Installing the InternetManagement Server . . . . . . . . . 65Before you install the Internet Management Server 65Installing the Internet Management Server . . . . 66Post-installation procedures . . . . . . . . . 71

Creating a self-signed certificate . . . . . . 71Rebooting the host machine . . . . . . . . 74Changing the default User ID and password forthe management server . . . . . . . . . 74

Chapter 7. Installing InternetManagement Endpoints . . . . . . . 77Before you install an Internet Management Endpoint 77Starting the installation . . . . . . . . . . 82Web Services Investigator information . . . . . 84Quality of Service information . . . . . . . . 85Web Services Courier information . . . . . . . 88Completing the installation . . . . . . . . . 91Post-installation procedures . . . . . . . . . 92

Post-installation procedures for Web ServicesInvestigator endpoints on Windows systems . . 92Post-installation procedure for secure Quality ofService proxy servers . . . . . . . . . . 94

Chapter 8. Installing the STI Recorder 97Before you install the STI Recorder . . . . . . 97Installing the recorder . . . . . . . . . . . 98

Chapter 9. Installing the WebTransaction Performance discoveryguide . . . . . . . . . . . . . . . 101Requirements summary . . . . . . . . . . 102Setting up Tivoli Decision Support . . . . . . 102Configuring a data source . . . . . . . . . 103

Setting up an ODBC data source connection forOracle . . . . . . . . . . . . . . . 103Setting up an ODBC data source connection forDB2 . . . . . . . . . . . . . . . 104Identifying data sources to Tivoli DecisionSupport . . . . . . . . . . . . . . 104

Configuring the shared data files . . . . . . . 105Setting up the Web Transaction Performancediscovery guide . . . . . . . . . . . . 105

Uninstalling the Tivoli Web Services Managerdiscovery guide . . . . . . . . . . . 106Installing the Web Transaction Performancediscovery guide . . . . . . . . . . . 106Importing the discovery guide. . . . . . . 106Assigning data sources . . . . . . . . . 106

Chapter 10. Uninstalling WebTransaction Performance components 109Uninstall file names and locations . . . . . . 109Uninstalling an Internet Management Endpoint onWindows . . . . . . . . . . . . . . . 111Uninstalling the Internet Management Server onWindows . . . . . . . . . . . . . . . 113Uninstalling an Internet Management Endpoint onUNIX . . . . . . . . . . . . . . . . 114

Uninstalling the Internet Management Server onUNIX . . . . . . . . . . . . . . . . 115Uninstalling the STI Recorder . . . . . . . . 116

Chapter 11. Using silent mode . . . . 117Overview. . . . . . . . . . . . . . . 117

The -silent option . . . . . . . . . . . 117Data options. . . . . . . . . . . . . 117Option files . . . . . . . . . . . . . 118Option files provided by Web TransactionPerformance . . . . . . . . . . . . . 119

Procedures and commands . . . . . . . . . 120Installing the Internet Management Server. . . 122Installing an Internet Management Endpoint 126Installing the STI Recorder . . . . . . . . 138Uninstalling Web Transaction Performancecomponents . . . . . . . . . . . . . 141

Chapter 12. All about certificates . . . 145Overview of keys and certificates. . . . . . . 145Types of certificates . . . . . . . . . . . 146Key files installed with Web TransactionPerformance. . . . . . . . . . . . . . 148IBM Key Management Utility . . . . . . . . 148

Starting the IBM Key Management Utility . . . 148Opening an existing key database file . . . . 149Specifying a password for a key database file 149Creating a new key database file . . . . . . 150Stashing a password for an existing keydatabase file . . . . . . . . . . . . . 150Changing the password for a key database file 150Displaying the default key in a key database file 150Creating a new key pair and certificate request 151Displaying a list of certificate authorities . . . 151Storing a certificate . . . . . . . . . . 151Receiving a CA-signed certificate . . . . . . 152Exporting keys . . . . . . . . . . . . 152Importing keys . . . . . . . . . . . . 153

References . . . . . . . . . . . . . . 153Organizations . . . . . . . . . . . . 153Standards . . . . . . . . . . . . . 154PKI vendors of commercial CA software . . . 154PKI vendors of enterprise CA software . . . . 154

Appendix A. Installing anduninstalling language packs . . . . . 155What is a language pack? . . . . . . . . . 155Language pack installation programs . . . . . 155Locations of language pack installation programs 156Language pack installation procedure . . . . . 157Uninstalling language packs . . . . . . . . 160

Language pack uninstallation procedure . . . 161

Appendix B. Stopping and starting 163Stopping and starting the Internet ManagementServer . . . . . . . . . . . . . . . . 163

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

Stopping and starting an Internet ManagementEndpoint . . . . . . . . . . . . . . . 164

iv Web Transaction Performance Installation Guide

Stopping and starting on Windows systems . . 164Stopping and starting on UNIX systems . . . 165

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

Appendix C. Problem determination 167Error and message logs . . . . . . . . . . 167

Trace levels . . . . . . . . . . . . . 168Command line options . . . . . . . . . . 169

-W options . . . . . . . . . . . . . 169-is options . . . . . . . . . . . . . 169

Recovery procedures . . . . . . . . . . . 170Recovery on Windows . . . . . . . . . 170

Recovery on UNIX: management server . . . 173Recovery on UNIX: endpoints . . . . . . . 176

Appendix D. Messages . . . . . . . 181Message Descriptions. . . . . . . . . . . 181

Appendix E. Notices . . . . . . . . 199Trademarks . . . . . . . . . . . . . . 201

Glossary . . . . . . . . . . . . . 203

Index . . . . . . . . . . . . . . . 211

Contents v

vi Web Transaction Performance Installation 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. Configuration for forwarding events to the

Tivoli Enterprise Console through a Tivolienvironment . . . . . . . . . . . . 34

11. Configuration for ARM Data Retrieval dialog(Windows) . . . . . . . . . . . . . 60

12. Internet Management Server Configurationdialog (AIX) . . . . . . . . . . . . 68

13. Database Configuration dialog (AIX) . . . . 6914. Configuration for ARM Data Retrieval dialog

(Windows) . . . . . . . . . . . . . 7015. Create New Self-signed Certificate dialog (IBM

Key Management Utility) . . . . . . . . 7316. Configuration of Windows User dialog

(Windows) . . . . . . . . . . . . . 8417. Quality of Service HTTP Proxy Server

Configuration dialog (Solaris) . . . . . . 8518. Origin HTTP Server Configuration dialog

(Windows) . . . . . . . . . . . . . 8619. Tivoli Enterprise Console Forwarding Options

dialog (Windows) . . . . . . . . . . 8820. Database Configuration dialog (AIX) . . . . 8921. Internet Management Server Information

dialog (Windows) . . . . . . . . . . 9122. Instructions for downloading the STI Recorder 9823. Internet Management Server Information

dialog (STI Recorder installation) . . . . . 9924. Processes for the Internet Management Server

(Solaris) . . . . . . . . . . . . . 17425. Processes for a Quality of Service endpoint 177

vii

viii Web Transaction Performance Installation Guide

Tables

1. Supported operating systems for WebTransaction Performance components . . . . 26

2. Minimum system requirements for the InternetManagement Server . . . . . . . . . . 27

3. Prerequisite software for the InternetManagement Server . . . . . . . . . . 28

4. Minimum system requirements for InternetManagement Endpoints and the STI Recorder . 29

5. Prerequisite software for Internet ManagementEndpoints and the STI Recorder. . . . . . 30

6. Information about requirements to enableevent forwarding. . . . . . . . . . . 32

7. Supported relational database managementsystems for the management repository . . . 38

8. Supported relational database managementsystems for the Web Services Courier datawarehouse . . . . . . . . . . . . . 38

9. Configuration tasks and requirements for aDB2 database . . . . . . . . . . . . 41

10. Summary of topics covered in this chapter 4911. Installation Files . . . . . . . . . . . 5112. Default installation directories . . . . . . 5213. Installation tasks . . . . . . . . . . . 5414. Upgrade programs . . . . . . . . . . 5615. Internet Management endpoint installation

tasks . . . . . . . . . . . . . . . 77

16. Tasks required to install the Web TransactionPerformance discovery guide . . . . . . 101

17. System and software requirements for theWeb Transaction Performance discovery guide 102

18. Web Transaction Performance components 10919. Uninstall File Locations . . . . . . . . 11020. Sample option files provided by Web

Transaction Performance . . . . . . . . 11921. Uninstall File Names and Locations . . . . 14122. . . . . . . . . . . . . . . . . 14823. Locations and names of native launchers for

language pack installation programs . . . . 15624. Installation logs . . . . . . . . . . . 16725. Uninstall logs . . . . . . . . . . . 16726. Trace level settings for traceBWAinstall.log 16827. Services for Web Transaction Performance

components . . . . . . . . . . . . 17128. Registry keys for Web Transaction

Performance components . . . . . . . 17229. Locations of reboot files and links to reboot

files for the Internet Management Server . . 17530. Scripts for stopping Internet Management

Endpoint processes . . . . . . . . . 17631. Locations of reboot files and links to reboot

files for Internet Management Endpoints . . 179

ix

x Web Transaction Performance Installation 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 Web Transaction Performance component provides functionality and features

that help you provide optimal service to users of your e-business Web sites.v The Enterprise Transaction Performance component provides functionality and

features 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 Web TransactionPerformance components of the product. For information on how to install theEnterprise Transaction Performance components of IBM Tivoli Monitoring forTransaction Performance, see the IBM Tivoli Monitoring for Transaction 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 Web Transaction

Performance components. Supported operating systems include Windows NT®,Windows® 2000, Windows XP, AIX®, Solaris Operating Environment (referred toas Solaris in this document), Red Hat Linux, SuSE Linux, 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.v Oracle or IBM DB2® database management systems.

xi

Web Transaction Performance provides optional integration with the IBM TivoliEnterprise Console® and IBM Tivoli NetView® products. Readers must have someknowledge of these products to decide whether to use them in conjunction withWeb 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.

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

xii Web Transaction Performance Installation Guide



v IBM Tivoli Monitoring for Transaction Performance: Enterprise TransactionPerformance 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 11.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.

– IBM Tivoli Enterprise Console User’s Guide, GC32-0667

About this guide xiii



Provides 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 Installation 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 the IBM TivoliMonitoring for Transaction Performance: Web Transaction Performance User’s Guide.

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 Installation 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 Web Transaction Performance component provides the following primaryapplications: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 Installation 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 IBM TivoliMonitoring for Transaction Performance user interface—through a Web browser.From the IBM Tivoli Monitoring for Transaction Performance user interface, youcan schedule jobs, define event thresholds and responses, view real-time data,and perform 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 Web Transaction Performanceapplications. It is the control center of a Web Transaction Performance installation.It collects information from the endpoints in the installation and provides servicesto those endpoints. The Internet Management Server and the endpoints registeredto it together comprise the Web 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 IBM Tivoli Monitoring for Transaction Performance user interface (referred

to in this book as the Web Transaction Performance user interface or GUI) fordomain administration. Users access the user interface by entering the Webaddress of the 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 11 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. WebTransaction Performance provides the following discovery guide (included on theIBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: Web TransactionPerformance 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 IBM 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 IBM TivoliMonitoring for 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 . See Chapter 9, “Installing the WebTransaction Performance discovery guide” for information about setting up TivoliDecision Support to create and view historical reports.

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 theIBM Tivoli Monitoring for Transaction Performance user interface.

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

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


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.

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. Forinformation about requirements needed to set up event forwarding, see“Requirements for Tivoli Enterprise Console event forwarding” on page 32.

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 warehouse


packs 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. For information about the installationrequirements for Tivoli Decision Support, see Chapter 9, “Installing the WebTransaction Performance discovery guide”.

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 Web Transaction Performance installable components interms of where they are located in the Web services environment and how theycommunicate.

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 Web Transaction Performance installation on thenetwork 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 IBM 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.

For more information on configuration requirements for event forwarding to theTivoli Enterprise Console, see “Requirements for Tivoli Enterprise Console eventforwarding” on page 32.

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. See Chapter 9, “Installingthe Web Transaction Performance discovery guide” for information on this andother requirements for using the Web Transaction Performance discovery guide.

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 APIv 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 often both a parent transaction and a sub-transaction.

v To refer to a banking transaction, for example 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. Theuse 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 check box 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


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. System and software requirements

This chapter describes the system requirements and prerequisite software for theWeb Transaction Performance product components—the Internet ManagementServer, Internet Management Endpoints, and the STI Recorder application.v System requirements include the operating system software and system resources,

such as disk space and memory, needed to support the product component onthe machine where it is installed.

v Prerequisite software is software that you must install prior to installing theproduct component. You must install prerequisite software on the same machineas the product component, except for RDBMS software, which you can install ona separate database server.

In addition, this chapter covers the following topics:v Requirements for Tivoli Enterprise Console event forwardingv Requirements for browsers used to access the Web Transaction Performance

graphical user interface (GUI)v Supported languages

The following chapters describe additional requirements for Web TransactionPerformance:v Chapter 3, “RDBMS requirements” provides information about setting up

databases to support the management repository and the Web Services Courierdata warehouse.

v Chapter 9, “Installing the Web Transaction Performance discovery guide”describes requirements for setting up Tivoli Decision Support and installing theWeb Transaction Performance discovery guide.

25

Supported operating systemsTable 1 lists the supported operating systems for Web Transaction Performanceproduct components. Note the following restrictions:v Web Transaction Performance supports both both 32-bit and 64-bit architectures

on Solaris and AIX 5.1. All other systems are supported on 32-bit architecturesonly.

v Web Transaction Performance supports Linux systems with Kernel 2.4 only.v STI record and playback functions are supported on Windows systems only.

Table 1. Supported operating systems for Web Transaction Performance components

Productcomponent

Operating system

Windows platforms UNIX platforms

InternetManagementServer

v Windows NT 4.0 Server SP6+

v Windows 2000 Server SP2+

v Windows 2000 Advanced Server SP2+

v Solaris 2.7 and 2.8 (SunOS 5.7 and 5.8)

v AIX 4.3.3

v AIX 5.1

Quality ofServiceEndpoint





v AIX 4.3.3

v AIX 5.1

v Red Hat Linux 7.1 and 7.2 (ix86)

v TurboLinux 7 Server (ix86)

v SuSE Linux 7.3 (ix86)

v Red Hat Linux 7.1 for zSeries (S/390)

v TurboLinux Server 7 for zSeries (S/390)

v SuSE Linux Enterprise Server 7.0 for zSeries (S/390)

Web ServicesInvestigator1


v Windows NT 4.0 Workstation SP6+



v Windows 2000 Professional SP2+

v Windows XP Professional


v AIX 4.3.3

v AIX 5.1


v TurboLinux 7 Server (ix86)

v SuSE Linux 7.3 (ix86)

Web ServicesCourier





v AIX 4.3.3

v AIX 5.1


STI Recorderv Windows NT 4.0 Server SP6+

v Windows NT 4.0 Workstation SP6+



v Windows 2000 Professional SP2+

v Windows XP Professional

Not supported


Table 1. Supported operating systems for Web Transaction Performance components (continued)

Productcomponent

Operating system

Windows platforms UNIX platforms

Notes:

1. On Windows systems, the Web Services Investigator Endpoint includes both the Site Investigator and STI Playerapplications. On UNIX systems, the Web Services Investigator Endpoint includes only the Site Investigatorapplication.

Abbreviations:

v SP: Service Pack

v +: or later

System requirements for the Internet Management ServerTable 2 specifies minimum system requirements for computers on which theInternet Management Server is installed.

Table 2. Minimum system requirements for the Internet Management Server

Requirement Windows platforms1 Unix platforms

Operating System See Table 1 on page 26 for a list of supported operating systems for the Internet ManagementServer.

Processor Intel-compatible, ix86 Solaris: Sun UltraSparcAIX: any AIX-compatible machine

Disk Space2, 3 135 MB 90 MB

Disk Space fortemporary files4

100 MB 105 MB

Memory 256 MB 256 MB

Swap Space 400 MB 400 MB

Notes:

1. Emulated ix86 environments or environments where Windows is not the initially loaded operating system (slaveix86 processor cards or mixed processor environments) are not supported.

2. (Solaris) You must install the management server on a volume (file system) that has sufficient physical space.That is, you cannot create a symbolic link from a volume that is too small to a path on a volume that hassufficient disk space. For example, if you do not have enough space to install on the /opt volume and want toinstall on the /usr volume, do not create a symbolic link from the /opt volume to a path on the /usr volume.Install directly on the /usr volume itself.

3. Disk space requirements are starting requirements only. Additional space is needed as log files grow.

4. The installation program places temporary files in the /tmp directory on AIX or the /var/tmp directory onSolaris. You can specify a different location when you start installation. For Windows systems, the installationprogram places temporary files in the location specified by the TEMP environment variable setting.

Chapter 2. System and software requirements 27

Prerequisite software for the Internet Management ServerTable 3 describes software that must be installed before you install the InternetManagement Server.

Table 3. Prerequisite software for the Internet Management Server

RequirementWindows platforms UNIX platforms

Windows NT Windows 2000 Solaris AIX

Java™

DevelopmentKit (JDK)

Bundled JDK1 Sun JDK 1.3.1 SE orhigher2

IBM JDK 1.3.1 SE orhigher3

RDBMSSupport3

A relational database management system is required to support the management repository. Thefollowing relational database management systems work with a management server that isinstalled on a supported platform.

v Oracle 8.1.6 or higher

v Oracle 9i

v DB2 7.1 or 7.2, Enterprise Edition or Extended Enterprise Edition (supports a management serveron any platform except Solaris)

See Chapter 3, “RDBMS requirements” for further information.

Notes:

1. IBM Developer Kit for the Java Platform, Standard Edition, Version 1.3.1, Service Release 2 is bundled withinstallation of the management server on Windows systems. Installation of the IBM JDK has no effect on anyJDK already installed on the machine.

2. Sun Java Development Kit, Standard Edition, Version 1.3.1 is a minimum requirement for Solaris systems.Version 1.3.1_04 or higher is preferred. This software is available from Sun Microsystems, Inc.

3. IBM Developer Kit for the Java Platform, Standard Edition, Version 1.3.1 is a minimum requirement for AIXSystems. Version 1.3.1 Service Release 2 or higher is preferred. The preferred version is provided on the IBMTivoli Monitoring for Transaction Performance, Version 5.1.0: Web Transaction Performance Component Software CD.

4. You can install the RDBMS on the same machine as the management server or on a separate database server.


System requirements for Internet Management Endpoints and the STIRecorder

Table 4 specifies minimum system requirements for computers on which anInternet Management Endpoint or the STI Recorder is installed.

Table 4. Minimum system requirements for Internet Management Endpoints and the STI Recorder

Requirement Windows platforms1 UNIX platforms

OperatingSystem

See Table 1 on page 26 for a list of supported operating systems for Internet ManagementEndpoints and the STI Recorder.

Processor Intel-compatible, ix86 v Solaris: Sun UltraSparc

v AIX: any AIX-compatible machine

v Linux (ix86): Intel-compatible, ix86

v Linux (S/390): S/390 zSeries

Disk Space2 Windows Platforms UNIX Platforms

Quality of Service 125 MB 55 MB


100 MB 15 MB

Web ServicesCourier

100 MB 15 MB

STI Recorder 10 MB Not supported

Disk Space fortemporary files(endpoints)3

120 MB 120 MB

Memory 128 MB 128 MB

Notes:

1. Emulated ix86 environments or environments where Windows is not the initially loaded operating system (slaveix86 processor cards or mixed processor environments) are not supported.

2. (Solaris) You must install an endpoint on a volume (file system) that has sufficient physical space. That is, youcannot create a symbolic link from a volume that is too small to a path on a volume that has sufficient diskspace. For example, if you do not have enough space to install on the /opt volume and want to install on the/usr volume, do not create a symbolic link from the /opt volume to a path on the /usr volume. Install directlyon the /usr volume itself.

3. The installation program places temporary files in the /tmp directory on AIX and Linux systems, and in the/var/tmp directory on Solaris. You can specify a different location when you start installation. For Windowssystems, the installation program places temporary files in the location specified by the TEMP environmentvariable setting.


Prerequisite software for Internet Management Endpoints and the STIRecorder

In Table 5, the top row specifies software required for any endpoint. The remainingrows describe additional software required for specific endpoints and the STIRecorder. No additional prerequisite software is required for components notspecifically listed in the table.

Table 5. Prerequisite software for Internet Management Endpoints and the STI Recorder

Component Windows platforms UNIX platforms

Windows NT Windows 2000 Windows XP1 Solaris AIX Linux

AnyEndpoint

Bundled JRE2 v Sun JRE 1.3.1 SE or higher on Solaris 3

v IBM JRE 1.3.1 SE or higher on AIX and Linux4

v Korn shell on all Linux systems

WebServicesInvestigator

STIRecorder

Internet Explorer 6 with patch Q316059 must beinstalled to support STI recording or playback.

STI recording and playback are not supported onUNIX platforms.

Quality ofService

Not applicable. v /usr/lib/libstdc++-libc6.1-2.so.3 file onLinux S/390 systems

v Patches for Solaris 2.7 (SunOS 5.7):

– (32-bit) 106327-09

– (64-bit) 106300-12

v Patches for Solaris 2.8 (SunOS 5.8):

– (32-bit) 108434-04

– (64-bit) 108435-04

WebServicesCourier

v Specific software is required to support event forwarding to the Tivoli Enterprise Console if eventsare forwarded through a Tivoli environment. See “Requirements for Tivoli Enterprise Consoleevent forwarding” on page 32 for information.

v A relational database management system is required to support the Web Services Courier datawarehouse. The following relational database management systems work with a Web ServicesCourier endpoint that is installed on a supported platform:5

– Oracle 8.1.6 or higher

– Oracle 9i

– DB2 7.1 or 7.2, Enterprise Edition or Extended Enterprise Edition (supports a Web ServicesCourier endpoint on Windows NT, Windows 2000, or AIX only)

See Chapter 3, “RDBMS requirements” for further information.


Table 5. Prerequisite software for Internet Management Endpoints and the STI Recorder (continued)

Component Windows platforms UNIX platforms

Windows NT Windows 2000 Windows XP1 Solaris AIX Linux

Notes:

1. Windows XP is supported for the Web Services Investigator endpoint and STI Recorder only.

2. IBM Runtime Environment for the Java Platform, Standard Edition, Version 1.3.1, Service Release 2 is bundledwith the installation of endpoints on Windows systems. Installation of the IBM JRE has no effect on any JREalready installed on the machine.

3. Sun Java Runtime Environment, Standard Edition, Version 1.3.1 is a minimum requirement for Solaris systems.Version 1.3.1_04 or higher is preferred. This software is available from Sun Microsystems, Inc.

4. IBM Runtime Environment for the Java Platform, Standard Edition, Version 1.3.1 is a minimum requirement forAIX and Linux Systems. Version 1.3.1 Service Release 2 or higher is preferred. The preferred version is providedon the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: Web Transaction Performance ComponentSoftware CD.

5. You can install the RDBMS on the Web Services Courier endpoint machine or on a separate database server inthe enterprise.


Requirements for Tivoli Enterprise Console event forwardingWhen you install a Web Services Courier endpoint, you can optionally enable theTivoli Enterprise Console event forwarding feature. When this feature is enabled,the Web Transaction Performance administrator can specify that events of selectedtypes be forwarded to the Tivoli Enterprise Console for analysis. The events areforwarded to the Tivoli Enterprise Console through the Web Services Courierendpoint.

You can enable forwarding of events to the Tivoli Enterprise Console in either ofthe following ways.v Through a Tivoli environment. The term Tivoli environment refers to the collection

of resources and applications, based on the Tivoli Management Framework, thatare installed at a specific customer location and that address network computingmanagement issues across many platforms. To enable forwarding of events tothe Tivoli Enterprise Console through a Tivoli environment, the machine onwhich you install the Web Services Courier endpoint must also be an endpointof a Tivoli management region server.This option has the following advantages:– A Tivoli environment provides a secure connection to Tivoli Enterprise

Console servers. A secure connection prevents anyone from sending falseevents, gathering information, or otherwise compromising your network.

– The Tivoli Management Framework guarantees delivery of events to theTivoli Enterprise Console by reattempting transmissions in case of failure.

– In a Tivoli environment with multiple Tivoli Enterprise Console servers, if aserver goes down, events are forwarded to an available server.

v Directly to a specific Tivoli Enterprise Console server. To enable forwarding of eventsdirectly to a Tivoli Enterprise Console server, you specify the host name andport of the server when you install the Web Services Courier endpoint. Thisoption is useful if you do not have a Tivoli environment. However, there is noway to provide for a secure connection. In addition, occasional loss of data ispossible because delivery is both connectionless and dependent on a singleTivoli Enterprise Console server. Connectionless delivery means that there is noattempt to retransmit data in case of failure.

To enable event forwarding, verify that the Web Services Courier endpoint meetsthe system requirements and software prerequisites for Internet ManagementEndpoints. For information about the additional setup required, refer to thesections listed in Table 6.

Table 6. Information about requirements to enable event forwarding

Option Refer to:

Enable forwarding of events through a Tivolienvironment

“Importing the BAROC file”

“Additional requirements for forwardingevents through a Tivoli environment” onpage 33

Enable forwarding of events to a specificTivoli Enterprise Console server

“Importing the BAROC file”

Importing the BAROC fileWeb Transaction Performance provides a BAROC file, TranPerf.baroc, whichcontains class definitions for events generated within the Web Transaction


Performance domain. The TranPerf.baroc file is located in the following directoryon the machine where the Internet Management Server is installed:install_dir/ManagementServer/TIMS/lib/

where install_dir is the installation directory for the Internet Management Server.The default installation directory is as follows:

C:\Program Files\Tivoli\Internet on Windows systems/usr/Tivoli/Internet on AIX/opt/Tivoli/Internet on Solaris

To enable event integration between Web Transaction Performance and a TivoliEnterprise Console event server, a Tivoli Enterprise Console administrator must dothe following:1. Create a new rule base2. Import the TranPerf.baroc file into the rule base3. Compile the rule base4. Load and activate the rule base

The Tivoli Event Console Rule Builder’s Guide describes procedures for working withrule bases and importing BAROC files. (See “Prerequisite publications” on page xiiifor more information.)

Additional requirements for forwarding events through a Tivolienvironment

Besides importing the BAROC file, the following additional setup is required toenable forwarding of events to the Tivoli Enterprise Console through a Tivolienvironment.v You must install the Web Services Courier endpoint on a machine within the

enterprise that has a Tivoli management agent already installed. The Tivolimanagement agent must use Tivoli Management Framework, Version 3.7.1(internationalized) or higher.

v Before installing the Web Services Courier endpoint on a machine with a Tivolimanagement agent, verify that the Adapter Configuration Facility (part of theTivoli Enterprise Console product) is installed on the Tivoli managementgateway for that Tivoli management agent. Also verify that the AdapterConfiguration Facility is installed on the Tivoli management region server.

Figure 10 on page 34 depicts the logical configuration needed to forward eventsthrough a Tivoli environment.v The Internet Management Server collects all events generated within the Web

Transaction Performance installation and sends them at a configurable interval tothe Web Services Courier endpoint.

v The Web Services Courier endpoint forwards the events through the Tivolimanagement gateway and the Tivoli management region server to the TivoliEnterprise Console.


Browser requirements for the IBM Tivoli Monitoring for TransactionPerformance GUI

You can initiate Web Transaction Performance management and reporting tasksthrough the browser-based IBM Tivoli Monitoring for Transaction Performancegraphical user interface (GUI) provided with the Internet Management Server. Youcan access and use the GUI from any machine on which a supported browser isinstalled. Web Transaction Performance is compatible with the following browserversions.

For Windows platforms:

v Microsoft Internet Explorer 5.5, Service Pack 2 or higher

v Microsoft Internet Explorer 6

v Netscape Communicator 6.2 or higher

For UNIX platforms:

v Netscape Communicator 6.2 or higher

Tivoli Management RegionServer

Tivoli ManagementGateway

Tivoli ManagementAgent

Adapter ConfigurationFacility

Adapter ConfigurationFacility

TivoliEnterpriseConsole

Web Services CourierEndpoint

To InternetManagement

Server(in the DMZ)

Tivoli Management Region (Enterprise/Intranet)

Figure 10. Configuration for forwarding events to the Tivoli Enterprise Console through a Tivoli environment


Note the following special requirements for browsers:v You must enable cookies on your browser.v For Microsoft Internet Explorer, you must download Microsoft Virtual Machine.v Required display settings are 256 colors, 800 x 600 pixels.

Supported languagesIBM Tivoli Monitoring for Transaction Performance, Version 5.1, is available in thefollowing languages:

Brazilian PortugueseChinese (Traditional)Chinese (Simplified)FrenchGerman

ItalianJapaneseKoreanSpanish


Chapter 3. RDBMS requirements

To store and manage data, Web Transaction Performance uses space in a relationaldatabase management system (RDBMS). There are two relational databasemanagement systems associated with Web Transaction Performance:v An RDBMS must be installed in the DMZ to support the Internet Management

Server. The Internet Management Server uses space (called the managementrepository) in the RDBMS to store job information, events, and other information.The Internet Management Server (the RDBMS client) and the RDBMS server canbe on the same machine, or the RDBMS server can be on a separate machine.

v An RDBMS must be installed in the enterprise (intranet) to support the historicaldata collection software on the Web Services Courier endpoint. The historicaldata collection software on the Web Services Courier endpoint uses space (calledthe Web Services Courier data warehouse) in the RDBMS to store data collected bythe Web Transaction Performance applications. The Web TransactionPerformance discovery guide retrieves data from the data warehouse and uses itto create historical reports.The Web Services Courier endpoint (the RDBMS client) and the RDBMS servercan be on the same machine, or the RDBMS server can be on a separatemachine.

Note: The Web Services Courier data warehouse is an optional feature. If you donot plan to use historical reports, an RDBMS is not needed to support theWeb Services Courier endpoint.

The RDBMS client (the Internet Management Server or the Web Services Courierendpoint) and the RDBMS server (which contains the management repository ordata warehouse) can be on the same machine or on separate machines. For a DB2RDBMS, you must configure a connection between client and server if they are onseparate machines. This step is not necessary for an Oracle RDBMS.

You must install and configure the relational database management systems usedby Web Transaction Performance before installing the Internet Management Serverand Web Services Courier endpoint. The installation programs for the managementserver and endpoint create and initialize the tables in the RDBMS.

This chapter lists the supported relational database management systems anddescribes how to configure them for use by Web Transaction Performance. It isrecommended that a database administrator perform most of these activities. Thischapter does not address installation of the RDBMS itself. For information on howto install an RDBMS, consult the appropriate database documentation.

Supported relational database management systemsWeb Transaction Performance support for a particular RDBMS is dependent on theplatform used by the client—the Internet Management Server or Web ServicesCourier endpoint. The tables in this section list both the supported client platformsand the relational database management systems that support each client platform.v Table 7 on page 38 lists the supported relational database management systems

for the management repository. The RDBMS used for the managementrepository is dependent on the Internet Management Server platform. For

37

example, if the Internet Management Server is installed on a Solaris platform, anOracle RDBMS must be used for the management repository.

Table 7. Supported relational database management systems for the managementrepository

Internet Management Server RDBMS for management repository

Operating system Oracle DB2

Windows NT 4.0 Server SP6+Windows 2000 Server SP2+Windows 2000 Advanced Server SP2+

8.1.6+, 9i 7.1, 7.2

AIX 4.3.3 (32-bit only)AIX 5.1

8.1.6+, 9i 7.1, 7.2

Solaris 2.7 or 2.8 (SunOS 5.7 or 5.8) 8.1.6+, 9i Not supported

v Table 8 lists the supported relational database management systems for the WebServices Courier data warehouse. The RDBMS used for the data warehouse isdependent on the Web Services Courier endpoint platform. For example, if theWeb Services Courier endpoint is installed on a Solaris or Red Hat Linuxplatform, an Oracle RDBMS must be used for the data warehouse.

Table 8. Supported relational database management systems for the Web Services Courierdata warehouse

Web Services Courier endpoint RDBMS for data warehouse

Operating system Oracle DB2

Windows NT 4.0 Server SP6+Windows 2000 Server SP2+Windows 2000 Advanced Server SP2+

8.1.6+, 9i 7.1, 7.2

AIX 4.3.3 (32-bit only)AIX 5.1

8.1.6+, 9i 7.1, 7.2

Solaris 2.7 or 2.8 (SunOS 5.7 or 5.8) 8.1.6+, 9i Not supported

Red Hat Linux 7.1 or 7.2 (2.4 kernal, ix86only)

8.1.6+, 9iNot supported

Table abbreviations:

SP: Service Pack +: or later

Oracle configurationComplete the following configuration tasks for an Oracle RDBMS used to supporteither the management repository or the Web Services Courier data warehouse.v Create sufficient tablespace for the management repository or data warehouse.

Observe the following tablespace estimates for one month of operational data.Space requirements might vary, however, depending on your environment andWeb Transaction Performance configuration.– 10 GB minimum for the management repository.– 20 GB minimum for the data warehouse.

Note: For test purposes, a smaller database (300 MB to 400 MB) is sufficient.v Create a user ID and password for the tablespace. The user must have authority

to create and edit tables.


v Configure a rollback segment.– For the management repository, you can use the Oracle default size for

rollback segments.– For the data warehouse, use a rollback segment approximately half the size of

the tablespace. The rollback segment should be auto-extensible andconfigured for a large number of maximum extents. During system operation,you should periodically shrink the rollback segment to conserve space on thefile system where the database is installed.

You can use either of the following sample SQL scripts to quickly configure amanagement repository or Web Services Courier data warehouse when setting up aWeb Transaction Performance system for evaluation in a test environment. Do notuse these scripts in a production environment.

Sample SQL script for creating fixed tablespaceThe following sample script creates a tablespace of fixed size. It does the following:v Creates tablespaces called tims_main_ts and tims_temp_ts

v Assumes that the Oracle installation directory is /data/home/oracle/dbs

v Creates a tablespace user named tims, with the password tims

v Uses path names in UNIX format. If your Oracle installation is on a Windowsmachine, use path names in Windows format. That is, use backslash characters(\) instead of forward slash (/) characters.

create tablespace tims_main_tsdatafile ’/data/home/oracle/dbs/tims_main.dbf’ size 300Mdefault storage (initial 4Mnext 4Mminextents 2maxextents unlimitedpctincrease 0)offline;commit;

create tablespace tims_temp_tstemporary datafile ’/data/home/oracle/dbs/tims_temp.dbf’ size 100Mdefault storage (initial 1Mnext 1Mminextents 2maxextents unlimitedpctincrease 0)offline;commit;

alter tablespace tims_main_ts online;commit;

alter tablespace tims_temp_ts online;commit;

create profile tims_profile limitsessions_per_user 50cpu_per_session unlimitedcpu_per_call 6000logical_reads_per_session unlimitedlogical_reads_per_call 100idle_time 30connect_time 480;commit;

Chapter 3. RDBMS requirements 39

create user timsidentified by timsdefault tablespace tims_main_tstemporary tablespace tims_temp_tsquota unlimited on tims_main_tsprofile tims_profile;commit;

GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TOtims identified by tims;commit;

Sample SQL script for creating flexible tablespaceInstead of setting permanently fixed sizes for the tablespace and temporarydatafile, the following sample script uses AUTOEXTEND to enlarge these items asneeded. It autoextends the tablespace (named $username) 5 MB at a time, and thetemporary datafile 100 KB at a time.

#!/bin/ksh

if [ $# -ne 1 ]then

echo "Usage: create_users.sh <username>"exit 1

fi

username=$1

echo "Creating SQL file: /dbs1/create/"$username"_create.sql"

cat << E_O_F > /dbs1/create/"$username"_create.sqlREMREM Execute the following SQL fragment as Oracle RDBMS user "sys":REM

create tablespace ts_$usernamedatafile ’/dbs1/ts_$username.dbf’ size 30Mdefault storage (initial 100Knext 50Kminextents 2maxextents 120)offline;

commit;

create tablespace tmp_ts_$usernamedatafile ’/dbs1/tmp_ts_$username.dbf’ size 3Mdefault storage (initial 100Knext 50Kminextents 2maxextents 20)TEMPORARYoffline;

commit;

alter tablespace ts_$username online;

commit;

alter tablespace tmp_ts_$username online;


commit;

create profile profile_$username limitsessions_per_user 10cpu_per_session unlimitedcpu_per_call 6000logical_reads_per_session unlimitedlogical_reads_per_call 100idle_time 30connect_time 480;

commit;

create user $usernameidentified by $usernamedefault tablespace ts_$usernametemporary tablespace tmp_ts_$usernamequota unlimited on ts_$usernameprofile profile_$username;

commit;

GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO$username identified by $username;

commit;

ALTER DATABASE DATAFILE ’/dbs1/ts_$username.dbf’ AUTOEXTEND ON NEXT 5M;

commit;

ALTER DATABASE DATAFILE ’/dbs1/tmp_ts_$username.dbf’ AUTOEXTEND ON NEXT 100K;

commit;E_O_F

DB2 configurationThis section describes configuration tasks and requirements for setting up a DB2database that can be used to support either the management repository or the WebServices Courier data warehouse. The DB2 configuration tasks described in thischapter are meant to serve as a general guide to the basic requirements for settingup the database, not as compehensive instructions. As a database administrator,your approach might differ from the one outlined here. For detailed informationon DB2 architecture, commands, and procedures, consult your DB2 documentation.

Table 9 summarizes the tasks and requirements for setting up the database aspresented in this chapter.

Table 9. Configuration tasks and requirements for a DB2 database

Task / Requirement Section

1. Create the database to be used for the managementrepository or the Web Services Courier data warehouse.

“Creating the database” onpage 42

2. Create the database user, a system user account that theInternet Management Server or Web Services Courierendpoint can use to access the database.

“Creating the database user” onpage 42


Table 9. Configuration tasks and requirements for a DB2 database (continued)

Task / Requirement Section

3. Create a bufferpool.

The default bufferpool and pagesize for DB2 are smallerthan required for optimal performance by applicationsusing the management repository or data warehouse. Use abufferpool size of at least 1000, with a pagesize of 32K (themaximum pagesize allowed).

“Creating a bufferpool” onpage 43

4. Create sufficient tablespace for the management repositoryor data warehouse and associate it with the bufferpool.

Observe the following tablespace estimates for one monthof operational data. Space requirements might vary,however, depending on your environment and WebTransaction Performance configuration.

v 10 GB minimum for the management repository.

v 20 GB minimum for the data warehouse.

“Creating tablespace” on page 44

5. Grant the database user authority to the database and tothe tablespace. The database user must have authority tocreate and edit tables.

“Assigning permissions to thedatabase user” on page 44

6. Optimize the DB2 database configuration by increasing thenumber of log primaries and by turning on the log retainfunction.

“Optimizing the DB2 databaseconfiguration” on page 45

7. If the database server is installed on a separate machinefrom the client (the Internet Management Server or the WebServices Courier endpoint), install the DB2 ClientApplication Enabler on the client machine and set upconnectivity to the database.

“Setting up a DB2 clientconnection” on page 45

Creating the databaseYou must install the DB2 client on the machine to be used for the InternetManagement Server or Web Services Courier endpoint. You must create thedatabase to be used for the management repository or Web Services Courier datawarehouse under a DB2 Instance associated with that client. To create the database,you can log on as any authorized user of the DB2 Instance or you can log on asthe user under which the DB2 client was installed. (The user under which the DB2client was installed has access to all DB2 Instances associated with the client.)

Use the following command to create the database:db2 "create database databasename"

where databasename is the name of the database.

Example: If DB2Admin is the user name under which the DB2 database client wasinstalled on the Internet Management Server machine, you can log on as DB2Adminand create a database named TIMSDB to support the management repository.db2 "create database TIMSDB"

Creating the database userAfter you create the database, create a database user on the operating system ofthe DB2 server machine. (You can do this directly on the server or from within theDB2 client.) The term database user, as used here, refers to either of the following:


v The system user account that the Internet Management Server uses to access theDB2 database that supports the management repository.

v The system user account that the Web Services Courier endpoint uses to accessthe DB2 database that supports the Web Services Courier data warehouse.

Example: If the DB2 server is installed on a Windows NT machine, you can enterthe following command at a DOS prompt on that machine to create a databaseuser account that the Internet Management Server can use to access themanagement repository. This command creates a user named TIMS with passwordTIMS. (The password is the second TIMS entry.)net user TIMS TIMS /add

Creating a bufferpoolThe following sample procedure creates and implements a bufferpool. Toimplement a bufferpool, you must disconnect all applications currently connectedto the database. This procedure is an example only. Actual commands and valuesmight differ for your environment.1. Create a large bufferpool. Make the size as large as possible without using

operating system paging. For example, to create a bufferpool of size 1000, withpagesize of 32K, enter the following command in DB2:create bufferpool bp32k size 1000 pagesize 32 k

2. Enter the following command to view the new bufferpool:select * from syscat.bufferpools

3. List all applications currently connected to the database. Use the followingcommand:db2 list applications

A list of appications similar to the following is displayed:Auth ID Appl. Appl. Application ID DB #of

Name Handle Name Agents-------- ---- ------ --------------------------- ---- ------DB2INST1 java 14 *LOCAL.db2instl.000918161203 CSWA 1DB2INST1 java 15 *LOCAL.db2instl.000918161204 CSWA 1

4. Close all connections to the database. Repeat the following command for eachapplication currently connected:db2 force application (applicationhandle)

where applicationhandle is the application handle number listed in the Appl.Handle column of the list of applications (see Step 3).

5. Reconnect to the database in one of the following ways:v If you are logged on as a user authorized to the DB2 Instance under which

the database was created, enter a command similar to the following:db2 "connect to databasename"

where databasename is the name of the database to be used for themanagement repository or Web Services Courier data warehouse.

—OR—v If you are not logged on as a user authorized to the DB2 Instance under

which the database was created, enter a command similar to the following:db2 "connect to databasename user InstUser using InstUserPasswd"

where:


databasename is the name of the database to be used for the managementrepository or Web Services Courier data warehouse.InstUser and InstUserPasswd are the userID and password of a userauthorized to the DB2 Instance under which the database was created.

Information is displayed similar to the following:$db2 connect to cswa

Database Connection InformationDatabase server = DB2/6000 7.1.0SQL authorization ID = DB2INST1Local database alias = CSWA

Creating tablespaceThe following sample procedure creates a new tablespace and associates it with abufferpool of size 1000 and page size 32K. You must first create the user tablespaceand then create the system temporary tablespace. This procedure is an exampleonly. Actual commands and values might differ for your environment.1. Drop the default user tablespace (userspace1), using the following command:

drop tablespace userspace1

2. Recreate the default user tablespace by entering commands similar to thefollowing:create tablespace userspace1 pagesize 32 k managed by systemusing (’/data2/tablespace1’ 1000)bufferpool bp32k

3. To create the system temporary tablespace, enter commands similar to thefollowing:create temporary tablespace tempspace pagesize 32 k managed by systemusing (’/data2/temp32k’)bufferpool bp32k

4. To view the changes, enter the following command:db2 list tablespaces show detail

Assigning permissions to the database userThe following commands grant the permissions required by the database user (theuser account that the management server or Web Services Courier endpoint uses toaccess the database). These commands grant DBADM authority to the database and tothe tablespace. To issue these commands, you must be logged on as a userauthorized to the DB2 Instance under which the database was created.db2 "grant dbadm on database to user user"db2 "grant use of tablespace tablespace to user user"

where:user is the user ID of the database usertablespace is the name of the tablespace to be created for the managementrepository or Web Services Courier data warehouse.

Example: If you created a database user named TIMS for the Internet ManagementServer to use (as in the example under “Creating the database user” on page 42)and a tablespace named userspace1 (as in the example under “Creatingtablespace”), use the following commands to grant authority to the database and tothe tablespace.db2 "grant dbadm on database to user TIMS"db2 "grant use of tablespace userspace1 to user TIMS"


Optimizing the DB2 database configurationThe following sample procedure optimizes database configuration for use withWeb Transaction Performance applications by increasing the number of logprimaries and then turning on the log retain function. This procedure is anexample only. Actual commands and values might differ for your environment.1. List the database configuration information by entering a command similar to

the following:db2 "get db cfg for databasename"

2. Increase the number of log primaries by entering a command similar to thefollowing:db2 "update db cfg for databasename using logprimary number"

3. Turn on the log retain function by entering a command similar to the following:db2 "update db cfg for databasename using logretain on"

4. List all applications currently connected to the database. Use the followingcommand:db2 list applications

A list of appications similar to the following is displayed:Auth ID Appl. Appl. Application ID DB #of

Name Handle Name Agents-------- ---- ------ --------------------------- ---- ------DB2INST1 java 14 *LOCAL.db2instl.000918161203 CSWA 1DB2INST1 java 15 *LOCAL.db2instl.000918161204 CSWA 1

5. Close all connections to the database. Repeat the following command for eachapplication currently connected:db2 force application (applicationhandle)

where applicationhandle is the application handle number listed in the Appl.Handle column of the list of applications (see Step 4).

6. Make an offline backup and apply db logs to roll forward. Enter a commandsimilar to the following:db2 "backup db databasename to backupdirectory"

7. Repeat Step 4.

Setting up a DB2 client connectionIf the DB2 RDBMS is installed on a separate machine from the client (the InternetManagement Server or the Web Services Courier endpoint), you must install theDB2 Client Application Enabler on the client machine and set up connectivity tothe database. This procedure is not necessary if the RDBMS server is installed onthe same machine as the Internet Management Server or Web Services Courierendpoint.

Follow these guidelines when installing and configuring the DB2 ClientApplication Enabler:v Ensure that there is no DB2 Client Application Enabler installation (either

complete or partial) on the system. If an installation already exists, uninstall it.v Customize the options to select Java database connectivity (JDBC). A JDBC

driver is installed as part of the DB2 Client Application Enabler installation.v Ensure that approximately 2 MB are available in the selected home directory to

accommodate the DB2 Client Application Enabler.v (AIX only) Source the db2profile file (for the Korn or Bourne shell) or the

db2cshrc file (for the C shell) to be able to run DB2 commands and utilities such


as catalog and connect. This is necessary even if the DB2 Client ApplicationEnabler is using a Network File System (NFS).The db2profile and db2cshrc files are located in the home directory of the DB2instance owner, under the sqllib subdirectory. Source the appropriate file in the.profile or .cshrc file of each account that needs to use the DB2 environmentand tools.

v (AIX only) To verify the setup of the RDBMS and of the DB2 client, ensure thatthe following environment variables are set correctly. (If you have sourced thedb2profile or db2cshrc file, these variables are correct.)– DB2DIR must point to the directory where the DB2 Client Application Enabler

is installed.– DB2INSTANCE must be set to the database instance name. This is set during

installation of the database.

After the DB2 Client Application Enabler is installed, you must set up connectivityboth to the RDBMS server and to the database. DB2 commands for setting upconnectivity are issued from the client system.v The following example command connects the client with an RDBMS server

named ghost, which has the node name or alias ims_db2 and uses port 50000:db2 "catalog tcpip node ims_db2 remote ghost server 50000"

v The following example command connects the client to a database namedtimsdev with the alias ims_dev, located on the server whose node name or aliasis ims_db2:db2 "catalog database timsdev as ims_dev at node ims_db2"

Sample shell script for DB2 configurationYou can use the following sample shell script to quickly configure a DB2 databaseto support the management repository or Web Services Courier data warehouse ina test environment. Do not use this script in a production environment.#! /usr/bin/ksh

if [ $# -ne 2 ]then

echo "Usage: $0 <database> <rootdir>

where <database> is the name of the databaseto be created and <rootdir> is the rootlocation of the database files."

exit 1

fi

OS=$(uname)

if [ $OS != "Windows_NT" ];then

if [ -f /data/home/db2inst1/sqllib/db2profile ]; then. /data/home/db2inst1/sqllib/db2profile

fi

fi

if [ $OS = "Windows_NT" ]then

database=$1rootdir=$2\\user=$3


databasedir=${rootdir}${database}tempfile=${databasedir}\\${database}_temp.datdatafile=${databasedir}\\${database}.dat

elsedatabase=$1rootdir=$2user=$3databasedir=${rootdir}/${database}tempfile=${databasedir}/${database}_temp.datdatafile=${databasedir}/${database}.dat

fi

buffer=${database}_bptempspace=${database}_temp

if [ ! -d "${rootdir}" ]; thenecho "Root directory specified does not exist...exiting!"exit 1

fi

if [ ! -d "$rootdir/$database" ]; thenecho "Creating database directory $databasedir and setting permissions..."mkdir $databasedir

fi

if [ $OS != "Windows_NT" ];thenchmod 777 $databasedir

fi

# The meat of the program...all DB2 calls are done here

echo "Creating default database..."db2 "create database $database"

echo "Connecting to new database..."db2 "connect to $database"

echo "Dropping default tablespace..."db2 "drop tablespace userspace1"

echo "Creating new 32k bufferpool..."db2 "create bufferpool $buffer size 1000 pagesize 32 k"

echo "Disconnecting from database..."db2 "disconnect $database"

echo "Reconnecting..."db2 "connect to $database"

echo "Creating new default 32k tablespace..."db2 "create tablespace userspace1 pagesize 32 k managed by systemusing (’$datafile’) extentsize 64 prefetchsize 32 bufferpool $buffer"

echo "Creating new temporary 32k tablespace..."db2 "create temporary tablespace $tempspace pagesize 32 k managed by systemusing (’$tempfile’) extentsize 64 prefetchsize 32 bufferpool $buffer"

echo "Disconnecting..."db2 "disconnect $database"

echo "Reconnecting..."db2 "connect to $database"

echo "Granting DBADM permissions to user $user..."db2 "grant dbadm on database to user $user"db2 "grant use of tablespace userspace1 to user $user"


echo "Optimizing database for maximum transactional performance..."db2 "update db config for $database using SORTHEAP 512"db2 "update db config for $database using APP_CTL_HEAP_SZ 512"db2 "update db cfg for $database using STMTHEAP 16384"db2 "update db cfg for $database using AVG_APPLS 5"db2 "update db cfg for $database using CATALOGCACHE_SZ 100"db2 "update db cfg for $database using DBHEAP 3300"db2 "update db cfg for $database using NUM_IOCLEANERS 5"db2 "update db cfg for $database using NUM_IOSERVERS 10"db2 "update db cfg for $database using LOGFILSIZ 2000"db2 "update db cfg for $database using LOGPRIMARY 20"db2 "update db cfg for $database using LOGSECOND 40"

db2 "disconnect $database"

if [ $OS != "Windows_NT" ];thenchmod -R 777 $databasedir

fi

echo "Done..."


Chapter 4. Installation overview and road map

This chapter contains important background information about the installation,upgrade, and uninstall programs provided by Web Transaction Performance, withan emphasis on details pertaining to installation. Table 10 lists the main sections inthis chapter and what is covered.

Table 10. Summary of topics covered in this chapter

Section Description

“Installation, upgrade, anduninstall programs”

Describes the component and language packprograms provided by Web Transaction Performanceand where they are located.

“Installation overview” on page 50 v Introduces the concepts of interactive and silentmode, native launchers, and command line optionsfor troubleshooting

v Lists native launchers for installation

v Lists default installation directories

v Describes how to specify an alternative location fortemporary files.

“Installation road map” on page 54 Lists in order the main steps required to install a WebTransaction Performance component.

Installation, upgrade, and uninstall programsWeb Transaction Performance provides the following installation, upgrade, anduninstall programs:

New component installationsWeb Transaction Performance provides separate programs for newinstallations of the following components:v The Internet Management Serverv Internet Management Endpoints

There is a single installation program for installing any of the InternetManagement Endpoint types: Web Services Investigator, Quality ofService, and Web Services Courier. You can install one type each timeyou run the installation program. You cannot install more than one typeon a single computer.

v The STI Recorder

The installation programs are provided on the IBM Tivoli Monitoring forTransaction Performance, Version 5.1.0: Web Transaction Performance ComponentSoftware CD.

Component upgradesYou can use the upgrade programs to upgrade an Internet ManagementServer and Internet Management Endpoints from the predecessor product,Tivoli Web Services Manager Version 1.7. To use the upgrade programs,you must have Tivoli Software Fix 1.7–WSM-U482086 installed on allcomponents to be upgraded. Most Internet Management Endpoints areautomatically upgraded when you upgrade the management server.

49

There is no upgrade program for the STI Recorder. To upgrade an STIRecorder to the current release, you must uninstall the old recorder andthen perform a new installation.

The upgrade programs are provided on the IBM Tivoli Monitoring forTransaction Performance, Version 5.1.0: Web Transaction Performance ComponentSoftware CD.

Language pack installationsYou can use the language pack installation programs to install languagepacks on the computers where Web Transaction Performance componentsare installed. A language pack is a set of files that, when installed with aWeb Transaction Performance component, enables you to view the GUI orlog files in a specific language other than English. You can install languagepacks for some or all of the supported languages in a single installation.There are separate language pack installation programs for the followingcomponents. There is no language pack upgrade program.v The Internet Management Server and Internet Management Endpoints

A single program installs language packs for both the InternetManagement Server and all Internet Management Endpoints that areregistered to the management server. When you install language packson the management server, they are automatically downloaded andinstalled on the endpoints.

v The STI RecorderA separate program installs language packs for the STI Recorder.

The language pack installation programs are provided on the IBM TivoliMonitoring for Transaction Performance, Version 5.1.0: Web TransactionPerformance Language Support CD.

Component uninstallationsWeb Transaction Performance provides separate uninstall programs for theInternet Management Server, Internet Management Endpoints, and the STIRecorder. You can use the Web Transaction Performance uninstall programsto uninstall components at the current release level.

The uninstall programs are not provided on any of the product CDs. Whenyou perform a new installation or upgrade, the installation program placesthe uninstall files in a subdirectory.

Language pack uninstallationsWeb Transaction Performance provides a language pack uninstall programthat you can use to remove one or more language packs from the InternetManagement Server, an Internet Management Endpoint, or the STIRecorder. You can use this program to uninstall language packs at thecurrent release level.

The language pack uninstall program is not provided on any of theproduct CDs. When you install language packs on a component, theinstallation program places the uninstall files in a subdirectory.

Installation overviewThis section introduces concepts that apply to installation, upgrade, anduninstallation programs as well as background details that apply specifically tocomponent installation. Details for uninstallation programs and language packs areprovided in other chapters.


Interactive and silent modeYou can install or uninstall the Web Transaction Performance components usingeither interactive mode or silent mode. (You cannot use silent mode for upgradesor to install or uninstall language packs.)v Interactive mode refers to interaction with a GUI. You enter information on the

dialogs presented by the upgrade, installation, or uninstall program.v Silent mode means there is no interaction with a GUI. You enter the information

needed by the installation or uninstall program on the command line or in a file.Silent mode installations and uninstallations have the advantage of being easilyand rapidly repeatable.

Native launchersA native launcher is an .exe or .bin file that starts an installation, upgrade, oruninstallation program for a particular platform. Web Transaction Performanceprovides native launchers for each supported platform for both component andlanguage pack programs. To start an installation, upgrade, or uninstallationprogram, you enter the name of the launcher on the command line or, in Windows,you can double-click on the launcher file name. The file names of componentinstallation and upgrade launchers identify the type of Web TransactionPerformance component and the target system. (For language packs, the targetsystem is identified by the name of the directory that contains the native launcher.)For example, the following command starts the installation of an endpoint on anAIX system:setup_Endpoint_aix.bin

Each native launcher runs a Java Archive (JAR) file. Both native launchers and JARfiles are included on the product CD. You can start an installation, upgrade, oruninstallation by using the java command with the name of the JAR file, instead ofusing a native launcher. For example, the following command starts the installationof an endpoint on any system:java -jar setup_Endpoint.jar

IBM Tivoli Monitoring for Transaction Performance provides the native launchersand Java Archive (JAR) files listed in Table 11. All files are located in the rootdirectory of the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: WebTransaction Performance Component Software CD.

Table 11. Installation Files

Component Native launcher JAR files

Internet Management Server setup_TIMS_w32.exesetup_TIMS_aix.binsetup_TIMS_sol.bin

setup_TIMS.jar

Internet ManagementEndpoint

setup_Endpoint_w32.exesetup_Endpoint_aix.binsetup_Endpoint_sol.binsetup_Endpoint_lin.binsetup_Endpoint_390.bin

setup_Endpoint.jar

STI Recorder setup_sti_recorder.exe Not applicable

Chapter 4. Installation overview and road map 51

Table 11. Installation Files (continued)

Component Native launcher JAR files

Notes:

v File name conventions. Each native launcher is intended for use on the system indicatedby the three-character identifier at the end of the file name. The following list pairs theidentifiers with the target systems:

_w32 Windows NT or Windows 2000_aix AIX_sol Solaris_lin Linux (ix86)_390 Linux (S/390)

v JAR files. The native launchers for the management server and endpoints run the JARfiles listed in the right-hand column. The native launcher must be in the same directoryas the JAR file that it runs. Therefore, if you copy a launcher file to another location,copy the corresponding JAR file to the same location.

Native launchers and their locations for upgrade, uninstallation, and languagepack programs are described in the following chapters:v See Chapter 5 for descriptions of upgrade launchers.v See Chapter 10 for descriptions of component uninstall launchers.v See Appendix A, “Installing and uninstalling language packs” on page 155 for

descriptions of language pack installation and uninstall launchers.

Command line optionsIn this book, the commands for starting an installation, upgrade, or uninstallationare shown in the following format:native_launcher [cmd_line_option...]

The variable cmd_line_option refers to one of a specific set of command line optionsthat are useful for troubleshooting a failure or to prevent problems ahead of time.You can enter zero or more of these options on the command line when usingeither interactive or silent mode. The complete list of options is described under“Command line options” on page 169. This chapter introduces one of the commandline options, an option to specify a different location for temporary files when thedefault location is too small or inconvenient. See “Specifying a location fortemporary files” on page 53.

Default installation directoriesThe component installation and upgrade programs install Web TransactionPerformance components by default to the directories listed in Table 12. Thedefault installation directories for a particular platform are the same for anyinstallable component: the Internet Management Server, an Internet ManagementEndpoint, or the STI Recorder.

Table 12. Default installation directories

Platform Default installation directory

Windows C:\Program Files\Tivoli\Internet

AIX /usr/Tivoli/Internet

TurboLinux (S/390) /Tivoli/Internet


Table 12. Default installation directories (continued)

Platform Default installation directory

All other UNIX systems /opt/Tivoli/Internet

During installation, you can specify a different installation directory. Languagepacks must be installed to the directory where the component resides.

Specifying a location for temporary filesThe installation, upgrade, and uninstall programs for Web Transaction Performancecomponents place temporary files in the following locations.v On Windows systems, the location specified by the TEMP environment variable

settingv On AIX and Linux, the /tmp directoryv On Solaris, the /var/tmp directory

You can specify a different location for temporary files in the following situations:v You do not want the installation, upgrade, or uninstall program to place

temporary files in the default location.v The default location does not have enough space for temporary files. (The

required space is 120 MB for installing the management server or an endpoint,and 20 MB for uninstallation.)

v The default location on your UNIX system is read-only.

You can specify a location for temporary files using one of the following methods:v (Any system) Specify the -is:tempdir option on the command linev (Windows systems only) Change the TEMP environment variable setting before

installing or uninstalling a Web Transaction Performance component

Using the -is:tempdir optionThe -is:tempdir option is one of several command line options that you canspecify when starting the installation, upgrade, or uninstall program. (See“Command line options” on page 169 for a complete list.) The format of this optionis as follows:-is:tempdir temp_dir

where temp_dir is the full path location for temporary files.

The following example installs the Quality of Service endpoint on a Solaris system.It places temporary files in the /usr/tmp directory.setup_Endpoint_sol.bin -is:tempdir /usr/tmp

Note: If the directory you specify does not exist, or is not a directory, the install oruninstall program writes temporary files to the default directory. No errormessage is issued.

Setting the TEMP environment variable (Windows only)On Windows systems, you can change the location for temporary files by settingthe TEMP environment variable before installing, upgrading, or uninstalling a WebTransaction Performance component. Follow these steps to set the TEMPenvironment variable:1. Right-click the My Computer icon.2. Select Properties. The System Properties dialog is displayed.

Chapter 4. Installation overview and road map 53

3. Click the Environment tab.4. Enter TEMP in the Variable: field.5. Enter a full path location for temporary files in the Value: field. For example:

D:\temp.6. Click OK.

Installation road mapFor new installations, perform the tasks listed in Table 13 in the order indicated.Refer to the listed chapters for details.

Table 13. Installation tasks

Task Refer to

1. Set up the Oracle or DB2 database for the managementrepository.

Chapter 3, “RDBMS requirements”

2. If you want the capability of creating and viewing historicalreports, do the following:

v Set up the Oracle or DB2 database for the Web ServicesCourier data warehouse. For large installations, you mightwant to set up multiple databases.

v Install Tivoli Decision Support and the Web TransactionPerformance discovery guide.

v Chapter 3, “RDBMS requirements”

v Chapter 9, “Installing the WebTransaction Performance discoveryguide”

3. If you want to enable forwarding of events to the IBM TivoliEnterprise Console, perform the required setup.

“Requirements for Tivoli EnterpriseConsole event forwarding” on page 32

4. Install the Internet Management Server. v For interactive installations, seeChapter 6, “Installing the InternetManagement Server”

v For silent installations, see Chapter 11,“Using silent mode”

5. Install the Internet Management Endpoints. Chapter 11, “Using silent mode”

v For interactive installations, see“Setting up the Web TransactionPerformance discovery guide” onpage 105


6. Install the STI Recorder. v For interactive installations, seeChapter 8, “Installing the STIRecorder”


7. Install language packs. Appendix A, “Installing and uninstallinglanguage packs”


Chapter 5. Upgrading existing installations

The Web Transaction Performance component of IBM Tivoli Monitoring forTransaction Performance, Version 5.1.0, is the successor to Tivoli Web ServicesManager, Version 1.7. This chapter describes how to upgrade Tivoli Web ServicesManager Version 1.7 installations to the current product. You can only upgradeVersion 1.7 installations that have Tivoli Software Fix 1.7-WSM-U482086 installedon all components.

When you upgrade the Internet Management Server, the Internet ManagementEndpoints that are registered to the management server and supported in thisrelease are automatically upgraded, with one exception. Web Services Investigatorendpoints on Windows systems require a separate upgrade procedure.

The upgrade procedures have the following restrictions:v You cannot perform an upgrade in silent mode.v There is no upgrade program for the STI Recorder. To bring the STI Recorder to

the current level, you must uninstall the old recorder and perform a newinstallation. See Chapter 8, “Installing the STI Recorder” on page 97 forinstructions.

v You must upgrade an entire installation. Web Transaction Performance does notsupport back-level endpoints with an upgraded management server or aback-level management server with upgraded endpoints. Similarly, the STIRecorder and the management server must be at the same level.

55

Upgrade programsIBM Tivoli Monitoring for Transaction Performance provides the upgradelaunchers and Java Archive (JAR) files listed in Table 14. All files are located in theroot directory of the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0:Web Transaction Performance Component Software CD.

Table 14. Upgrade programs

Native launcher JAR file Description

setup_TIMS_w32.exesetup_TIMS_aix.binsetup_TIMS_sol.bin

setup_TIMS.jar Upgrades the managementserver and most endpoints

upgrade_STI.exe upgrade_STI.jar Upgrades a Web ServicesInvestigator endpoint (withSTI Player) on Windows

Notes:

v File name conventions. The native launchers for upgrading the management server andmost endpoints are intended for use on the system indicated by the three-characteridentifier at the end of the file name. The following list pairs the identifiers with thetarget systems:

_w32 Windows NT or Windows 2000_aix AIX_sol Solaris

v JAR files. The native launchers run the JAR files listed in the JAR File column. Thenative launcher must be in the same directory as the JAR file that it runs. Therefore, ifyou copy a launcher file to another location, copy the corresponding JAR file to the samelocation.

Planning for the upgradeThe upgrade procedure causes temporary service interruptions that affect theoperation of the management server, endpoints, and monitored Web servers. Thefollowing items describe how an upgrade can impact administrators or customersand some steps that you can take to minimize or prevent problems.v STI playback jobs that were scheduled or running when the upgrade procedure

begins must be rescheduled when the upgrade is complete. Quality of Service orSite Investigator jobs automatically resume operation when the upgrade iscomplete. In some cases, these jobs might also need to be rescheduled. Jobscannot run until all endpoints have been upgraded, including manual upgradesof Web Services Investigator endpoints on Windows.

v When you run the upgrade program for the management server, the endpointsare automatically upgraded at a randomly scheduled time during a configurableautoupdate interval. You can shorten this interval, and therefore the time it takesto complete the upgrade, by changing a setting in a properties file on eachendpoint. See Step 5 on page 58.

v During the autoupdate interval, the operation of the watchdog service onQuality of Service endpoints on UNIX systems can cause automatic stoppingand restarting of the Quality of Service proxy server. (This problem does notoccur on endpoints that are installed on Windows systems.) The result isinterrupted customer access to monitored Web servers (origin servers). You canprevent this behavior by replacing the startEP file on each endpoint with a newstartEP file provided on the product CD. See Step 6 on page 58.


Upgrading the management server and most endpoints

The procedure described in this section upgrades the Internet Management Server,the management repository, and the following types of Internet ManagementEndpoints registered to the management server:v Quality of Service endpoints on all supported systemsv Web Services Courier endpoints on all supported systemsv Web Services Investigator endpoints on UNIX systems only

You must separately upgrade the following:v The data warehouses associated with the upgraded Web Services Courier

endpoints, if any. See Upgrading the data warehouses on page 62 forinstructions.

v Web Services Investigator endpoints on Windows systems. See Upgrading WebServices Investigator endpoints on Windows on page 63 for instructions.

Before You Begin1. Verify that the version of the management server to be upgraded is Tivoli Web

Services Manager Version 1.7 with Tivoli Software Fix 1.7-WSM-U482086installed. Make sure that all endpoints are also at this fixpack level.

2. Verify that the operating systems on which the management server andendpoints are installed meet the current requirements listed in Table 1 onpage 26. The upgrade program does not check the operating system level onendpoints that are automatically upgraded.

3. You must install JDK 1.3.1 SE or higher on the management server if themanagement server is installed on a UNIX system. The upgrade programautomatically installs the appropriate level of the JDK on Windows systems.v Sun Java Development Kit, Standard Edition, Version 1.3.1 is a minimum

requirement for Solaris systems. Version 1.3.1_04 or higher is recommended.This software is available from Sun Systems, Inc.

v IBM Developer Kit for the Java Platform, Standard Edition, Version 1.3.1 is aminimum requirement for AIX Systems. Version 1.3.1 Service Release 2 orhigher is recommended. The recommended version is provided on the IBMTivoli Monitoring for Transaction Performance, Version 5.1.0: Web TransactionPerformance Component Software CD.

4. You must install JRE 1.3.1 SE or higher on all endpoints that are automaticallyupgraded.v Sun Java Runtime Environment, Standard Edition, Version 1.3.1 is a

minimum requirement for Solaris systems. Version 1.3.1_04 or higher isrecommended. This software is available from Sun Systems, Inc.

v IBM Runtime Environment for the Java Platform, Standard Edition, Version1.3.1 is a minimum requirement for Windows, AIX, and Linux Systems.Version 1.3.1 Service Release 2 or higher is recommended. The recommendedversion is provided on the IBM Tivoli Monitoring for Transaction Performance,Version 5.1.0: Web Transaction Performance Component Software CD.

On Windows, install the JRE in the following directory:install_dir\Endpoint\oem\jre

where install_dir is the directory where the Version 1.7 endpoint is installed.The default directory is C:\Program Files\Tivoli\Internet.

Chapter 5. Upgrading existing installations 57

5. Change the autoupdate interval for endpoints if you do not want to accept theexisting setting.The automatic upgrade process applies the upgrade to all registered endpointsduring an autoupdate interval, configurable on each endpoint. Each endpointqueries the management server once during each interval to determine if anupdate is available. If an update is available, it is automatically downloadedand installed to the endpoint at a randomly scheduled time during the nextautoupdate interval. This means that an individual endpoint might beupgraded as much as two autoupdate intervals beyond the time you upgradethe management server.The upgrade program uses the autoupdate interval that is currently set in theendpoint.properties file on the endpoint. To change the autoupdate interval,follow these steps:a. Stop the endpoint service.b. Open the endpoint.properties file on the endpoint. This file is located in

the following directory:install_dir/Endpoint/configuration

where install_dir is the directory where the Version 1.7 endpoint is installed.c. Edit the endpoint.autoupdateInterval entry to change the autoupdate

interval.d. Restart the endpoint.

See “Stopping and starting an Internet Management Endpoint” on page 164 forinstructions on how to stop and start an endpoint.

6. If you want to prevent automatic stopping and restarting of the Quality ofService proxy server on UNIX endpoints (see “Planning for the upgrade” onpage 56), replace the startEP file on each endpoint. Replacement files areprovided on the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0:Web Transaction Performance Component Software CD in the following directories:51Updates/aix51Updates/solaris51Updates/linux-i86

Copy the new startEP file from the appropriate directory to the followingdirectory on each Quality of Service endpoint:install_dir/Endpoint/bin

where install_dir is the directory for the Version 1.7 endpoint is installed.7. If you want to save information stored in the management repository, back up

or export the database. The upgrade program for the management serverchanges the tables in the management repository to a new schema and removesall statistical and event data from the database. Consult your databasedocumentation for information on how to back up or export a database.

8. If you want the upgrade program to enable the STI Player to collect WebSphereARM data, note the URL of the Enterprise Transaction Performance server thatcollects the data. (The STI Player relies on the Enterprise TransactionPerformance component to collect the ARM data initially.) The URL includesthe protocol (http or https), fully qualified host name, and optionally, the portnumber. Example: https://etpserver.it.company.com:443

You do not need to enable this feature during installation. You can enable theSTI Player to collect WebSphere ARM data by changing a properties file afterinstallation.

9. Verify that the management server and endpoints are running.


Procedure1. Log on to the host machine for the Internet Management Server and start the

upgrade program:v For Windows systems:

a. Log on as Administrator or as a user with administrator privileges.b. Close all running applications.c. Navigate to the local or network location of the setup_TIMS_w32.exe file.

If you are installing from the IBM Tivoli Monitoring for TransactionPerformance, Version 5.1.0: Web Transaction Performance Component SoftwareCD, this file is located in the root directory of the CD.

d. Double-click the setup_TIMS_w32.exe file.—OR—

If you are using a command window, enter the following command:setup_TIMS_w32 [cmd_line_option ...]

where cmd_line_option is one of a set of options you can use for logging,troubleshooting, and other purposes. You can enter zero or more ofthese options on the command line. See “Command line options” onpage 169 for a complete list.

v For UNIX systems:

a. Log on as the root user.b. Enter the following command from the root directory:

For AIX: file_path/setup_TIMS_aix.bin [cmd_line_option ...]For Solaris: file_path/setup_TIMS_sol.bin [cmd_line_option ...]

where:file_path is the full directory path to the local or network location ofthe setup_TIMS_aix.bin or setup_TIMS_sol.bin file. If you areinstalling from the IBM Tivoli Monitoring for Transaction Performance,Version 5.1.0: Web Transaction Performance Component Software CD, thisfile is located in the root directory of the CD.Example: /cdrom/setup_TIMS_aix.bin

cmd_line_option is one of a set of options you can use for logging,troubleshooting, and other purposes. You can enter zero or more ofthese options on the command line. See “Command line options” onpage 169 for a complete list.

2. Click Next on the upgrade message dialog. The upgrade message informs youthat an Internet Management Server is already installed on this computer.

3. Click Next on the Welcome screen.4. On the Software License Agreement dialog, select the radio button to accept

the terms of the license agreement.5. Click Next.

The Destination Directory dialog displays the directory where the Version 1.7Internet Management Server is currently installed. Do not change thisdirectory unless you know it is incorrect. The Version 5.1.0 managementserver must be installed to the same directory.

6. Click Next. The Configuration for ARM Data Retrieval dialog is displayed.


7. If you do not want to enable the collection of WebSphere ARM data, go toStep 8. Do the following to enable STI playback jobs to collect WebSphereARM data:a. Click the Enable ARM Data Retrieval check box.b. Enter the URL of the Enterprise Transaction Performance server that

collects the ARM data in the URL of Enterprise Transaction PerformanceServer field. The URL must be specified in the following format:protocol://hostname:portnumber

where:v protocol is one of the following:

– http if the Enterprise Transaction Performance server is not a secureserver

– https if the Enterprise Transaction Performance server is a secureserver

v hostname is the fully qualified name of the host machine for theEnterprise Transaction Performance server

v portnumber is a valid port number that the Enterprise TransactionPerformance server can use to communicate with the InternetManagement Server.

Example: https://etpserver.it.company.com:443

8. Click Next. An information screen specifies the destination directory and theamount of disk space for the management server installation.

9. Click Next to proceed with the upgrade.

Figure 11. Configuration for ARM Data Retrieval dialog (Windows)


When the upgrade is complete, an information dialog is displayed. This dialogdescribes activities to perform after you exit the upgrade program.

10. Click Next.11. Click Finish to exit.

When You Finish1. If you upgraded a secure management server, the management server does not

automatically start when the upgrade is complete. You must manually restart asecure management server. See “Stopping and starting the InternetManagement Server” on page 163 for instructions.

2. Perform the following procedure on each upgraded Quality of Service endpointthat is installed on a Windows system. This procedure upgrades the Quality ofService proxy server and restarts the endpoint.a. Verify that the Internet Management Endpoint service is stopped. If not,

stop the endpoint.b. Run the updateQos_51.bat file. This file is located in the following directory:

install_dir\Endpoint

The updateQos_51.bat file upgrades the Quality of Service proxy server onthe endpoint. In the process, it momentarily stops and restarts the server.

c. Restart the endpoint.


3. Perform the following procedure on each upgrade Quality of Service endpointon a UNIX system where you installed a new startEP file. (See Step 6 onpage 58.) Omit this procedure on endpoints where you did not replace thestartEP file.a. Verify that the Internet Management Endpoint service is stopped. If not,

stop the endpoint.b. Stop the Quality of Service proxy server (the Tivoli Endpoint HTTP Server

process).c. Restart the Quality of Service proxy server (the Tivoli Endpoint HTTP

Server process).d. Restart the endpoint.

See “Stopping and starting an Internet Management Endpoint” on page 164 and“Stopping and starting the Quality of Service proxy server” on page 165 forinstructions on how to stop and start the endpoint and the server.

4. You must upgrade each data warehouse associated with the Web ServicesCourier endpoints that you upgraded. See Upgrading the data warehouses onpage 62 for instructions.


Upgrading the data warehouses

The upgrade program for the management server automatically upgrades WebServices Courier endpoints, but it does not automatically upgrade the datawarehouse or data warehouses, if any, associated with those endpoints. To upgradea data warehouse, you must run a script on one of the Web Services Courierendpoints that shares the data warehouse.

There might be more than one group of Web Services Courier endpoints, eachgroup sharing a different data warehouse. In a case like this, run the script fromone Web Services Courier endpoint in each group.

Before You BeginA data warehouse upgrade includes database schema changes as well as theremoval of all existing historical and event data. You might want to preserve thedata so that you can create cubes and historical reports based on the data. If youwant to preserve this data, back up or export the database prior to running thescript. Consult your database documentation for information on how to back up orexport a database.

ProcedureComplete the following procedure to run the script:v For Windows systems:

1. Navigate to the following directory on the Web Services Courier endpoint:install_dir\Endpoint\bin

where install_dir is the directory where the endpoint is installed. Thedefault installation directory on a supported Windows system is thefollowing:C:\Program Files\Tivoli\Internet

2. Double-click the wsadbpatch51.bat file or enter wsadbpatch51 from acommand window.

v For UNIX systems:1. Change to the following directory on the Web Services Courier endpoint:

install_dir/Endpoint/bin

where install_dir is the directory where the endpoint is installed. Thedefault installation directory on a supported UNIX system is the following:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris or Linux)

2. Enter the following command:./wsadbpatch51.sh

When You FinishNot applicable.


Upgrading Web Services Investigator endpoints on Windows

Before You Begin1. Upgrade the management server before upgrading a Web Services Investigator

endpoint registered to the management server.2. Verify that the endpoint is installed on a Windows sytem.3. Verify that the version of the endpoint to be upgraded is Tivoli Web Services

Manager Version 1.7 with Tivoli Software Fix 1.7-WSM-U482086 installed.4. Note the password of the user account that the existing STI Player uses to

access Microsoft Internet Explorer. You must supply this password duringinstallation. If this account was automatically created when the Version 1.7endpoint was installed, the user name is TivoliStiPlayback.

Procedure1. Log on to the host machine for the Web Services Investigator endpoint and

start the installation program:a. Log on as Administrator or as a user with administrator privileges.b. Close all running applications.c. Navigate to the local or network location of the upgrade_STI.exe file. If

you are installing from the IBM Tivoli Monitoring for TransactionPerformance, Version 5.1.0: Web Transaction Performance Component SoftwareCD, this file is located in the root directory of the CD.

d. Double-click the upgrade_STI.exe file.—OR—

If you are using a command window, enter the following command:upgrade_STI [cmd_line_option ...]

where cmd_line_option is one of a set of options you can use for logging,troubleshooting, and other purposes. You can enter zero or more of theseoptions on the command line. See “Command line options” on page 169for a complete list.


the terms of the license agreement.4. Click Next.

The Destination Directory dialog displays the directory where the Version 1.7Web Services Investigator endpoint is currently installed. Do not change thisdirectory unless you know it is incorrect. The Version 5.1.0 endpoint must beinstalled to the same directory.

5. Click Next to display the Configuration of Windows User dialog.The User field displays the user name that the existing STI Player on thisendpoint uses to access Microsoft Internet Explorer. Do not change this userunless you know it is incorrect.

6. In the Password field, enter the password for the user name displayed in theUser field.

7. Enter the same password in the Verify Password field.8. Click Next. An information dialog specifies the destination directory and the

amount of disk space for the installation.9. Click Next to proceed with the upgrade.


10. When the upgrade completes, click Finish to exit.

When You FinishReboot the computer.


Chapter 6. Installing the Internet Management Server

This chapter describes how to install the Internet Management Server on asupported Windows or UNIX system. It includes the actions you must take andthe information you must gather prior to installation, the installation steps, and thefollow-up procedures. The entire process from pre-installation to post-installation isthe same, with minor variations, for all supported operating systems.

Note: This chapter describes how to perform an interactive installation of theInternet Management Server (installation with a GUI). You can also installthe Internet Management Server silently from the command line with noGUI. See Chapter 11, “Using silent mode” for information on silentinstallations.

Before you install the Internet Management ServerTo ensure a quick, trouble-free installation of the Internet Management Server,complete the following activities before you begin the installation process. Foractivities that involve creating data or collecting information to be entered duringinstallation, you can instead elect to use the default, if any, supplied by theinstallation program. This section specifies default values where available.1. Verify that the system on which you are installing the Internet Management

Server meets the system requirements and software prerequisites listed inChapter 2.

2. Verify that no Internet Management Server is already installed on the machinewhere you intend to install the new Internet Management Server, unless youare upgrading from the previous release. See Chapter 5, “Upgrading existinginstallations” on page 55 for information about upgrading from the previousrelease.

3. Verify that no files are left from a previously failed installation in the directorywhere you plan to install the Internet Management Server. See Appendix C forinstructions on how to clean up after a failed installation or uninstallation.

4. Verify that the database for the management repository meets the requirementsdescribed in Chapter 3.

5. (UNIX systems only) Create a user and group for the management server or planto use an existing one. The user and group name must not have spaces. Theinstallation program enters the default user name nobody and the default groupname nobody.

Note: The management server cannot run as the root user.6. Collect the following information about the management server. You must

supply this information during installation.v The fully qualified host name or the IP address of the host machine for the

Internet Management Server.v The fully qualified name of the domain in which the host machine for the

Internet Management Server resides. For example, if the host machine isservername.it.company.com, the fully qualified domain name isit.company.com.

v The protocol to be used for communication between the management serverand its registered endpoints. Your choices are:

65

– https for secure (SSL-enabled) communication. This is the default.– http for non-secure communication.

v The port number to be used for communication between the managementserver and its registered endpoints.– The default port number for secure (SSL-enabled) communication is 443.– The default port number for non-secure communication is 80.

v (UNIX systems only) The user and group name for the management server.(See Step 5.)

7. Collect the following information about the database to be used for themanagement repository. You must supply this information during installationof the management server. The installation process checks the connection to thedatabase and then creates tables in the database for the management repository.v For an Oracle database, collect the following information:

– The fully qualified host name or the IP address of the host machine forthe Oracle database.

– The port number used by the Oracle listener. The default port is 1521.– The SID name for the Oracle database.– The user ID and password for the tablespace to be used for the

management repository.v For a DB2 database, collect the following information:

– (AIX only) The name of a user authorized to the DB2 Instance underwhich the database for the management repository was created. This canbe the name of the user under which the DB2 client was installed on themanagement server machine. (See “Creating the database” on page 42.)

– The full path to the home directory of the owner of the DB2 Instanceunder which the DB2 database for the management repository wascreated.- On AIX systems, specify the path name up to, but not including, the

sqllib subdirectory. The default supplied by the installation program is/usr/db2inst1.

- On Windows systems, include the sqllib subdirectory. The defaultsupplied by the installation program is C:\Program Files\IBM\Sqllib).

– The alias used on the management server to refer to the DB2 database forthe management repository.

– The user ID and password for the database to be used for themanagement repository. (See “Creating the database user” on page 42.)

8. If you want to enable the STI playback jobs to collect WebSphere ARM data,note the URL of the Enterprise Transaction Performance server. (The STI Playerrelies on the Enterprise Transaction Performance component to collect the ARMdata initially.) The URL includes the protocol (http or https), fully qualifiedhost name, and optionally, the port number.Example: https://etpserver.it.company.com:443

Installing the Internet Management ServerWhile you are installing the Internet Management Server, note the following:v The installation program displays a message (either on an installation dialog or

in a separate popup window) when an error condition exists, such as missingprerequisite software. Each message is preceded by a message identifier (forexample, BWMIS0103E). Appendix C, “Problem determination” contains a list of


all installation error messages, ordered by message identifier, with instructionson what corrective action to take before proceeding with the installation.

v Whenever the installation procedure requires a host name, do not include aprotocol. For example, enter timsserver.ibm.tivoli.com, nothttps://timsserver.ibm.tivoli.com

v Do not enter special characters in a text field.v Each installation dialog displays default values in some fields. The installation

dialogs pictured in this chapter have default values displayed.

To install the Internet Management Server on any of the supported operatingsystems, complete the following steps:1. Log on to the host machine for the Internet Management Server and start the

installation program:v For Windows systems:

a. Log on as Administrator or as a user with administrator privileges.b. Close all running applications.c. Navigate to the local or network location of the setup_TIMS_w32.exe file.

If you are installing from the IBM Tivoli Monitoring for TransactionPerformance, Version 5.1.0: Web Transaction Performance Component SoftwareCD, this file is located in the root directory of the CD.

d. Double-click the setup_TIMS_w32.exe file.—OR—

If you are using a command window, enter the following command:setup_TIMS_w32 [cmd_line_option ...]

where cmd_line_option is one of a set of options you can use for logging,troubleshooting, and other purposes. You can enter zero or more ofthese options on the command line. See “Command line options” onpage 169 for a complete list.

v For UNIX systems:


For AIX: file_path/setup_TIMS_aix.bin [cmd_line_option ...]For Solaris: file_path/setup_TIMS_sol.bin [cmd_line_option ...]

where:file_path is the full directory path to the local or network location ofthe setup_TIMS_aix.bin or setup_TIMS_sol.bin file. If you areinstalling from the IBM Tivoli Monitoring for Transaction Performance,Version 5.1.0: Web Transaction Performance Component Software CD, thisfile is located in the root directory of the CD.Example: /cdrom/setup_TIMS_aix.bin



the terms of the license agreement.4. Click Next to display the Destination Directory dialog.5. Do one of the following:

Chapter 6. Installing the Internet Management Server 67

v Accept the default installation directory that is displayed in the Directoryname field.

v Use the Browse button to select a different installation directory.v Enter a different installation directory in the Directory name field.

6. Click Next. The installation program creates the installation directory youspecified if it does not already exist.The Internet Management Server Configuration dialog appears.

7. Enter information in the following text fields or accept the defaults:

Host Name The fully qualified host name or the IP address of the hostmachine for the Internet Management Server.

Domain NameThe fully qualified name of the domain in which the hostmachine for the Internet Management Server resides. Forexample, if the host machine is servername.it.company.com,the fully qualified domain name is it.company.com.

8. Select a protocol from the drop-down list or accept the default. Your choicesare:v https for secure (SSL-enabled) communication between the management

server and its registered endpoints.v http for non-secure communication between the management server and its

registered endpoints.

The Port Number field displays a default value corresponding to the selectedprotocol: 443 for a secure management server or 80 for a non-secure server.

9. Enter a different port number in the Port Number field if you do not want toaccept the default.

10. (UNIX systems only) Enter information in the following text fields or accept thedefaults:

User The user name under which the Internet Management Server will run.

Group The group name under which the Internet Management Server willrun.

Figure 12. Internet Management Server Configuration dialog (AIX)


11. Click Next to display the Database Configuration dialog.

12. From the drop-down list, select the kind of database to be used for creatingthe management repository: Oracle or DB2.The installation program activates text fields appropriate to the database youselected.

13. Enter information about the database.v For an Oracle database, enter the following information in the text fields:

Oracle Host NameThe fully qualified host name or the IP address of the hostmachine for the Oracle database

Oracle Port NumberThe port number being used by the Oracle listener

Oracle SID The SID name for the Oracle database

Database User IDThe user ID for the tablespace to be used for themanagement repository

Database PasswordThe password associated with the user ID specified in theDatabase User ID field

v For a DB2 database, enter the following information in the text fields:

DB2 Instance (AIX only) The name of a user authorized to the DB2Instance under which the database for the managementrepository was created. This can be the name of the userunder which the DB2 client was installed on themanagement server machine. (See “Creating the database”on page 42.)

Figure 13. Database Configuration dialog (AIX)


DB2 Installation DirectoryThe full path to the home directory of the owner of the DB2Instance under which the DB2 database for the managementrepository was created.– On AIX systems, specify the path name up to, but not

including, the sqllib subdirectory. For example, thedefault entered by the installation program is/usr/db2inst1.

– On Windows systems, include the sqllib subdirectory.For example, the default entered by the installationprogram is C:\Program Files\IBM\Sqllib.

DB2 Database NameThe alias used on the management server to refer to theDB2 database for the management repository

Database User IDThe user ID for the database to be used for the managementrepository. (See “Creating the database user” on page 42.)


14. Click Next. The Configuration for ARM Data Retrieval dialog is displayed.

15. If you do not want to enable the retrieval of WebSphere ARM data, go to Step16. If you want to enable ARM data retrieval, do the following:a. Click the Enable ARM Data Retrieval check box.

Figure 14. Configuration for ARM Data Retrieval dialog (Windows)


b. Enter the URL of the Enterprise Transaction Performance server thatcollects the ARM data in the URL of Enterprise Transaction PerformanceServer field. The URL must be specified in the following format:protocol://hostname:portnumber

where:v protocol is one of the following:

– http if the Enterprise Transaction Performance server is not a secureserver

– https if the Enterprise Transaction Performance server is a secureserver

v hostname is the fully qualified name of the host machine for theEnterprise Transaction Performance server

v portnumber is a valid port number that the Enterprise TransactionPerformance server can use to communicate with the InternetManagement Server.


16. Click Next. An information screen specifies the destination directory and theamount of disk space for the management server installation.

17. Click Next to proceed with the installation.18. When the installation program completes, click Finish to exit.

Post-installation proceduresAfter you exit the installation setup program, perform the following tasks (in theorder shown) to complete and verify the installation. Complete only the tasks thatapply to your installation. For example, if you are installing a secure server onSolaris, complete tasks 1 and 3. If you are installing a non-secure server, completeonly task 3.1. (secure server on any operating system) Create a self-signed certificate. See

“Creating a self-signed certificate”.2. (secure server on Windows systems only) Reboot the host machine for the

management server. The management server starts automatically afterrebooting. See “Rebooting the host machine” on page 74.

3. (all servers) Change the default user ID and password for the managementserver. See “Changing the default User ID and password for the managementserver” on page 74.

The following sections contain detailed information for each of these tasks.

Creating a self-signed certificateTo establish a secure network connection between the Internet Management Serverand its registered endpoints, you need to obtain a digital certificate issued by acertificate authority (CA) that is designated as a trusted CA on your server. Toobtain a certificate from a trusted CA, you can use the IBM Key ManagementUtility, a program that is installed with the management server. See Chapter 12,“All about certificates” for instructions on using the IBM Key Management Utilityto obtain and store a CA-issued certificate. Chapter 12 also contains generalbackground information about digital certificates and certificate keys.

Because it can take several weeks for a certificate authority to issue a certificate,the IBM Key Management Utility also provides a way for you to create a self-signed


certificate. A self-signed certificate enables Secure Sockets Layer (SSL) transactions.However, it does not provide the same level of security as a certificate issued by aCA. Therefore, unless you are administering a private network, also obtain one ormore certificates from a CA.

The following sections show you how to start the IBM Key Management Utility,create a self-signed certificate, and then change the default password for thecertificate key file.

Starting the IBM Key Management UtilityTo start the IBM Key Management Utility, do the following:v On Windows systems, select Programs → Tivoli → Start Key Management Utility

from the Start menu.v On UNIX systems, follow these steps:

1. Change to the following directory:install_dir/ManagementServer/IBMHTTPSERVER/platform/gsk5/bin/

where:– install_dir is the directory where the management server is installed. The

default installation directory for the management server on a supportedUNIX system is as follows:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris)

– platform is one of the following:- solaris2 if the management server is installed on a Solaris system- aix4-r3 if the management server is installed on an AIX system

2. Enter ./gsk5ikm.

Creating the certificateAfter starting the IBM Key Management Utility, follow these steps to create theself-signed certificate:1. On the IBM Key Management window, select Open from the Key Database

File menu.2. Browse to the following directory:

install_dir/ManagementServer/IBMHTTPSERVER/platform/ssl

where:v install_dir is the directory where the management server is installed.

– On Windows systems, the default installation directory is the following:C:\Program Files\Tivoli\Internet

– On UNIX systems, the default installation directory is the following:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris)

v platform is one of the following:– w32-ix86 if the management server is installed on a Windows system– solaris2 if the management server is installed on a Solaris system– aix4-r3 if the management server is installed on an AIX system

3. Select the key database file, key.kdb, and click Open.4. On the Password Prompt dialog, enter the password for the key.kdb file. The

default password is: admin


The IBM Key Management Utility displays the list of IBM-supported signercertificates contained in the key.kdb file.

5. Select New Self-Signed Certificate from the Create menu.The Create New Self-signed Certificate dialog is displayed.

6. On the Self-Signed Certificate dialog, fill in the following required text fields:

Key Label Enter a name for the certificate (up to 256 characters).

Common NameEnter the fully qualified host name of the machine on whichyou installed the Internet Management Server software.

Organization Enter the name of your company or organization (up to 256characters).

7. If your installation is outside the United States, change the default in theCountry drop-down list.

8. You can leave the optional fields blank and accept the defaults for theremaining fields on this dialog. Click OK to create the certificate and add it tothe key.kdb file.The certificate name is displayed in the Personal Certificates list.If this is the first self-signed certificate you created, the IBM Key ManagementUtility sets it as the default certificate for the management server. If you createanother self-signed certificate, the utility prompts you to confirm whether ornot the new certificate should be set as the default.

Changing the password for the key database fileBefore you exit the IBM Key Management Utility, you should change the defaultpassword for the key database file (key.kdb). Follow these steps to change thepassword:1. Select Change Password from the Key Database File menu.

Figure 15. Create New Self-signed Certificate dialog (IBM Key Management Utility)


2. Enter a password in the New Password field, and then enter the samepassword in the Confirm New Password field.

3. To change the default expiration time of 60 days, check the Set expiration timecheck box, and then enter a number of days in the adjacent field.

4. Check the Stash the password to a file check box to store the new password inthe encrypted password file, keys.sth, which is located in the same directory asthe key.kdb file.

Note: You must check this box for the Internet Management Server to run.5. Click OK to change the password.6. Select Exit from the Key Database File menu to close the IBM Key

Management Utility.

Rebooting the host machineYou need to reboot the host machine for the management server only for secureinstallations on Windows systems.

Reboot only after you have created a self-signed digital certificate for themanagement server. When you restart the machine, the management server codelooks for the certificate in the key database file (key.kdb) shipped with the product.If it does not find the certificate, the management server fails.

If you rebooted the host machine before creating the certificate, you must createthe certificate and then start the management server manually. To manually startthe management server (and the IBM HTTP Web server) select Programs → Tivoli →Start Internet Management Server from the Windows Start menu.

Changing the default User ID and password for themanagement server

As a final step in completing the installation of the Internet Management Server,you can optionally change the default user ID and password needed to access theserver. To change the default user ID and password, follow these steps.1. Open a Web browser and enter one of the following URLs to display the Web

Transaction Performance logon window.v For a secure management server, enter the following Web address:

https://hostname:port

v For a non-secure management server, enter the following Web address:http://hostname:port

where:hostname is the fully qualified host name for the management serverport is the listener port you specified during installation of the managementserver. The default port for a secure server is 443. The default port for anon-secure server is 80.

2. Type admin in both the User Name and Password fields. (This is the defaultuser ID and password for the management server.)

3. Click Log On.4. Select General Tasks from the drop-down list.5. Select User Preferences in the Portfolio.6. Select Change Password.


7. Enter the old password, the new password, and then the new password againin the specified fields.

8. Click Change Password.9. When the browser returns to the main IBM Tivoli Monitoring for Transaction

Performance window, select the Logoff option in the Portfolio to log out.


Chapter 7. Installing Internet Management Endpoints

This chapter describes how to install an Internet Management Endpoint onsupported versions of Windows or UNIX-based systems. It includes the actionsyou must take and the information you must gather prior to installation as well asthe actual installation steps. The installation procedure is the same, with minorvariations, on all supported operating systems.

Note: This chapter describes how to perform interactive installations of endpoints(installations with a GUI). You can also install endpoints silently from thecommand line with no GUI. See Chapter 11, “Using silent mode” forinformation on silent installations.

There is a single installation program for installing any of the InternetManagement Endpoint types. You can install one of the following types each timeyou run the installation program. You cannot install more than one type on asingle machine.v Web Services Investigatorv Quality of Servicev Web Services Courier

You can install either a Quality of Service or a Web Services Courier endpoint, butnot both, on the same machine as the Internet Management Server. You cannotinstall a Web Services Investigator endpoint on the same machine as the InternetManagement Server.

Table 15 outlines the endpoint installation process as presented in this chapter.

Table 15. Internet Management endpoint installation tasks

Task Section of chapter

1. Perform prerequisite activities and gather theinformation you need to enter on the installationdialogs before you start the installation.

“Before you install an Internet ManagementEndpoint”

2. Start the installation. Select the endpoint type that youwant to install.

“Starting the installation” on page 82

3. Continue the installation by providing specificinformation for the endpoint type that you selected toinstall.

Omit the sections of the chapter pertaining to endpoint typesthat you did not select.

v “Web Services Investigator information” onpage 84

v “Quality of Service information” on page 85

v “Web Services Courier information” on page 88

4. Finish the installation. “Completing the installation” on page 91

Before you install an Internet Management EndpointTo ensure a quick, trouble-free installation of an endpoint, complete the activitiesin this section before you begin the installation process. For activities that involvecreating data or collecting information to be entered during installation, you caninstead elect to use the default, if any, supplied by the installation program. Thissection specifies default values where available.

77

ALL ENDPOINT TYPES

1. Verify that the system on which you are installing the endpoint meets thesystem requirements and software prerequisites listed in Chapter 2.

2. Verify that the Internet Management Server is up and running. The installationprocess registers the endpoint with the management server.

3. Verify that no Internet Management Endpoint is already installed on themachine where you intend to install the new Internet Management Endpoint.

4. Verify that no files are left from a previously failed installation in the directorywhere you plan to install the Internet Management Endpoint. See Appendix Cfor instructions on how to clean up after a failed installation or uninstallation.

5. Collect the following information about the management server to which theendpoint will connect.v The fully qualified host name or the IP address of the host machine for the

Internet Management Server.v The user ID and password of a user authorized to log on to the management

server. The default user ID is admin and the default password is admin.v The type of communication—secure (SSL-enabled) or non-secure—to be used

between the management server and the endpoints. This was specifiedduring installation of the management server. You must specify the sametype of communication during installation of the endpoint.

v The port number on the management server to be used for communicationwith the endpoints. This was specified during installation of the managementserver.

6. If your network will use a proxy server to access the Internet ManagementServer, collect the following information about the proxy server:v The type of proxy: socks or HTTPSv The fully qualified host name or IP address of the proxy serverv The port number of the proxy server

WEB SERVICES INVESTIGATOR

If you install a Web Services Investigator endpoint on a Windows system, youmust specify a user account on the endpoint machine that the Tivoli InternetManagement Endpoint service can use to access Microsoft Internet Explorer. This isnecessary so that the STI Player on the endpoint can use the Internet Explorerbrowser on that machine to replay recorded Web transactions. You can specify auser account in one of two ways:v You can specify a user account that already exists on the endpoint machine, such

as Administrator. If you select this method, you must identify any futurepassword changes to the Tivoli Internet Management Endpoint Service.

v You can let the installation program create a new user account (calledTivoliStiPlayback) on the endpoint machine to be used exclusively for runningthe STI playback function. The password that you specify for theTivoliStiPlayback account is set to never expire.

If you want to use an existing user account, make sure the account meets thefollowing conditions:v The account must be part of the Administrators group.v The account must be local to the machine. Do not choose an account (user name

and password) that is used to log on through a remote server.


v The account must have the following user rights policies:– Act as part of the operating system– Log on as a service

v The Microsoft Internet Explorer browser on this account must be configured tosuccessfully connect to the Internet.

QUALITY OF SERVICE

1. (UNIX systems only) Create a user and group for the Quality of Service proxyserver or plan to use an existing one. The user and group name must not havespaces. The installation program enters the default user name nobody and thedefault group name nobody.

Note: The Quality of Service proxy server cannot run as the root user.2. Collect the following information about the Quality of Service proxy server. The

Quality of Service proxy server is an IBM HTTP Server, installed with theQuality of Service endpoint, that acts as a proxy for the Web server (called theorigin server) that you want to monitor.v The fully qualified host name or the IP address of the host machine for the

Quality of Service proxy server. This is the machine where you will installthe Quality of Service endpoint. It is possible for the same machine to hostboth the endpoint and the origin server.

v The type of communication protocol—secure (SSL-enabled) ornon-secure—that you want the proxy server to use for communication withthe Internet.

v The port number to be used by the proxy server for communication with theInternet.

v (UNIX systems only) The user and group name for the Quality of Serviceproxy server. (See Step 1.)

v For a secure (SSL-enabled) Quality of Service proxy server, the full pathname of a key database file—if one exists on this machine—that contains adigital certificate for authenticating this server to the Internet. A stash file,containing the password to the key database file, must also exist in the samedirectory. These files must have been created using the IBM Key ManagementUtility. The installation program needs these files in order to start the serverimmediately following installation.If these files do not exist, the installation program installs a keys.kdb filecontaining a self-signed certificate, and a keys.sth file, to the followingdirectory:install_dir/Endpoint/IBMHTTPServer/ssl/keys

where install_dir is the directory where the Quality of Service endpoint isinstalled.

The self-signed certificate is used for authentication to the Internet until youcreate a keys.kdb file containing a permanent certificate. Perform thisprocedure following installation. See “Post-installation procedure for secureQuality of Service proxy servers” on page 94.

v For a secure (SSL-enabled) Quality of Service proxy server, the installationprogram requires the following information only if you specify a keydatabase file, created with the IBM Key Management Utility, that containsmore than one certificate:– The name of the certificate that will be used to authenticate the Quality of

Service proxy server to the Internet.

Chapter 7. Installing Internet Management Endpoints 79

– The name of the certificate that will be used for secure communicationbetween the Quality of Service proxy server and the origin Web server(the server to be monitored by the Quality of Service endpoint). Securecommunication between the two servers is not required if they areinstalled on the same machine.

3. Collect the following information about the origin Web server. This is the serverto be monitored by the Quality of Service endpoint.v The fully qualified host name or the IP address of the host machine for the

origin server. The installation program enters as a default the name of themachine on which you are installing the Quality of Service endpoint.

v The type of protocol—secure (SSL-enabled) or non-secure—to be used forcommunication between the Quality of Service proxy server and the originserver.

v The port number on the origin server that the Quality of Service proxy serverwill contact.

4. (Solaris only) Add the following to /etc/system if it is not already present or ifthe quantities are not high enough:# Increase the number of undo’s allowed within the system.set semsys:seminfo_semmnu=1024

# Increase the maximum size of a shared memory segment to 4 MB (minimum):set shmsys:shminfo_shmmax=4194304

You can verify the two values by entering sysdef on the command line andsearching for SEMMNU and SHMMAX near the bottom of the output.

WEB SERVICES COURIER

1. Decide which features of the Web Services Courier endpoint you want toenable. You must enable at least one of the following features duringinstallation of the endpoint.v The Web Services Courier data warehouse feature. Enable this feature if you plan

to use Tivoli Decision Support to view historical reports of data collected byWeb Transaction Performance applications.

v The Tivoli Enterprise Console event forwarding feature. Enable this feature if youwant the Web Transaction Performance administrator to have the option offorwarding events generated within the Web Transaction Performancedomain to the Tivoli Enterprise Console. You can enable forwarding ofevents to the Tivoli Enterprise Console in either of two ways:– Through a Tivoli environment (resources and applications based on the

Tivoli Management Framework). To use this option, the machine on whichyou are installing the Web Services Courier endpoint must be an endpointof a Tivoli management region server.

—OR—– Directly to a specific Tivoli Enterprise Console server.

2. If you plan to enable event forwarding to the Tivoli Enterprise Console througha Tivoli environment, do the following:v Verify the system setup required to forward events through a Tivoli

environment. See “Requirements for Tivoli Enterprise Console eventforwarding” on page 32.


v Make note of the absolute path to the LCF file (lcf_env.cmd on Windowssystems or lcf_env.sh on UNIX systems) on the machine where you plan toinstall the Web Services Courier endpoint. This file represents the Tivolimanagement agent software.– On Windows systems, the path to the LCF file is typically as follows:

C:\SystemRoot\Tivoli\lcf\1\

where SystemRoot is the drive and directory where Windows is installed(for example, C:\WINNT or C:\WINNT40).

– On UNIX systems, the path to the LCF file is typically as follows:/etc/Tivoli/lcf/1/

3. If you plan to enable forwarding of events directly to a specific TivoliEnterprise Console server, make note of the following information about theserver:v The fully qualified host name or IP address of the host machine for this

Tivoli Enterprise Console server.v The port used by this Tivoli Enterprise Console server.

4. If you plan to enable the Web Services Courier data warehouse feature, do thefollowing:v Verify that the database to be used for the Web Services Courier data

warehouse meets the requirements described in Chapter 3. The Web ServicesCourier endpoint can share an existing data warehouse, if available, with oneor more previously installed Web Services Courier endpoints. The installationprocess creates data warehouse tables if they do not exist.

v For an Oracle database, collect the following information:– The fully qualified host name or the IP address of the host machine for

the Oracle RDBMS.– The port number used by the Oracle listener. The default listener port is

1521.– The SID name for the Oracle database.– The user ID and password for the tablespace to be used for the Web

Services Courier data warehouse.v For a DB2 database, collect the following information:

– (AIX only) The name of a user authorized to the DB2 Instance underwhich the DB2 database for the Web Services Courier data warehouse wascreated. This can be the name of the user under which the DB2 client wasinstalled on the Web Services Courier machine. (See “Creating thedatabase” on page 42.)

– The full path to the home directory of the owner of the DB2 instanceunder which the DB2 database for the Web Services Courier datawarehouse was created.- On AIX, specify the path name up to, but not including, the sqllib

subdirectory. The default supplied by the installation program is/usr/db2inst1.

- On Windows systems, include the sqllib subdirectory. The defaultsupplied by the installation program is C:\Program Files\IBM\Sqllib.

– The alias used on the Web Services Courier endpoint machine to refer tothe DB2 database for the data warehouse. (See “Creating the databaseuser” on page 42.)

– A user ID and password that the Web Services Courier endpoint can useto access the DB2 database for the data warehouse.


Starting the installationWhile you are installing an Internet Management Endpoint, note the following:v The installation program displays a message (either on an installation dialog or

in a separate popup window) when an error condition exists, such as missingprerequisite software. Each message is preceded by a message identifier (forexample, BWMIS0103E). Appendix C, “Problem determination” contains a list ofall installation error messages, ordered by message identifier, with instructionson what corrective action to take before proceeding with the installation.

v Whenever the installation procedure requires a host name, do not include aprotocol. For example, enter timsserver.ibm.tivoli.com, nothttps://timsserver.ibm.tivoli.com

v Do not enter special characters in a text field.v Each installation dialog displays default values in some fields. The installation

dialogs pictured in this chapter have default values displayed.

This section lists the steps needed to start the installation, select the endpoint typeto install, specify where to install the endpoint, and give the endpoint a name.These steps are common to the installation of any endpoint type.1. Log on to the host machine for the endpoint and start the installation program:

v For Windows systems:

a. Log on as Administrator or as a user with administrator privileges.b. Close all running applications.c. Navigate to the local or network location of the setup_Endpoint_w32.exe

file. If you are installing from the IBM Tivoli Monitoring for TransactionPerformance, Version 5.1.0: Web Transaction Performance Component SoftwareCD, this file is located in the root directory of the CD.

d. Double-click the setup_Endpoint_w32.exe file.—OR—

If you are using a command window, enter the following command:setup_Endpoint_w32 [cmd_line_option ...]

where cmd_line_option is one of a set of options you can use for logging,troubleshooting, and other purposes. You can enter zero or more of theseoptions on the command line. See “Command line options” on page 169for a complete list.

v For UNIX systems:


For AIX: file_path/setup_Endpoint_aix.bin [cmd_line_option]For Solaris: file_path/setup_Endpoint_sol.bin [cmd_line_option]For Linux (ix86): file_path/setup_Endpoint_lin.bin [cmd_line_option]For Linux (S/390): file_path/setup_Endpoint_390.bin [cmd_line_option]

where:file_path is the full directory path to the local or network location ofthe setup_Endpoint_aix.bin, setup_Endpoint_sol.bin,setup_Endpoint_lin.bin, or setup_Endpoint_390.bin file. If you areinstalling from the IBM Tivoli Monitoring for Transaction Performance,Version 5.1.0: Web Transaction Performance Component Software CD, thisfile is located in the root directory of the CD.Example: /cdrom/setup_Endpoint_aix.bin



2. Click Next on the Welcome screen.3. On the Software License Agreement dialog, select the radio button to accept the

terms of the license agreement.4. Click Next.5. Click one check box to select one endpoint type to install.6. Click Next to display the Destination Directory dialog.7. Do one of the following:



8. Click Next. The installation program creates the installation directory youspecified if it does not already exist.

9. On the Endpoint Name and Description dialog, enter a name for the endpointin the Endpoint Name field and a description in the Endpoint Descriptionfield.


Web Services Investigator informationContinue the installation by completing the following steps if you are installing aWeb Services Investigator endpoint.1. Click Next to display the Configuration of Windows User dialog.

2. (Windows only) Specify a user account on the endpoint machine that the TivoliInternet Management Endpoint Service can use to access Microsoft InternetExplorer. Do one of the following:v Specify an existing user account:

a. Select the Specify Existing Microsoft Internet Explorer User radiobutton.

b. Enter the user name for this account in the User field.c. Enter the password for this account in the Password and Verify

Password fields.

—OR—v Let the installation program create a new user account (named

TivoliStiPlayback):a. Select the Create TivoliStiPlayback User radio button.

The user name TivoliStiPlayback is displayed in the User field.b. Enter a password for this user in the Password and Verify Password

fields.The installation program creates the TivoliStiPlayback user accountunder the Administrators group on this machine.

3. Complete the installation of the Web Services Investigator endpoint byfollowing the instructions under “Completing the installation” on page 91.

Figure 16. Configuration of Windows User dialog (Windows)


Quality of Service informationContinue the installation by completing the following steps if you are installing aQuality of Service endpoint.1. Click Next to display the Quality of Service HTTP Proxy Server Configuration

dialog.

2. Specify information in the following fields for the Quality of Service proxyserver that is installed with the Quality of Service endpoint. The Quality ofService proxy server is an IBM HTTP Server that acts as a proxy for the Webserver (called the origin server) that you want to monitor.

Host Name Enter the fully qualified host name or the IP address of the hostmachine for the Quality of Service proxy server.

SSL Enabled Check this box if you want the Quality of Service proxy serverto use a secure (SSL-enabled) protocol for communication withthe Internet.

Port Number Enter the port number that the Quality of Service proxy serverwill use for communication with the Internet.

User (UNIX systems only) Enter the user name under which theQuality of Service proxy server will run.

Group (UNIX systems only) Enter the group name under which theQuality of Service proxy server will run.

The following fields are enabled only if you checked the SSL Enabled checkbox to specify secure communication for the Quality of Service proxy server.

Key database (.kdb) file pathEnter the full path name of a key database file that contains a digitalcertificate, signed by a trusted certificate authority, that will be used to

Figure 17. Quality of Service HTTP Proxy Server Configuration dialog (Solaris)


authenticate the Quality of Service proxy server to the Internet. The keydatabase file and an associated stash (.sth) file must have been createdusing the IBM Key Management Utility. The key database file and stashfile must be located in the same directory. If a key database file doesnot exist, leave this field blank.

Key Name (optional)If the key database file that you specified in the Key database (.kdb)file path field contains more than one certificate, optionally enter thename of the certificate that will be used for secure communications tothe Internet. If you do not enter a certificate name, the default namewill be used. If you did not specify a key database file, leave this fieldblank.

3. Click Next to display the Origin HTTP Server Configuration dialog.

4. Specify information in the following fields about the origin server. This is theWeb server to be monitored by the Quality of Service application.

Host Name Enter the fully qualified host name or the IP address of the hostmachine where the origin server is running.

SSL Enabled Check this box to enable secure communication between theQuality of Service proxy server and the origin server.

Port Number Enter the port number on the origin server that the Quality ofService proxy server will contact.

The following field is enabled only if you checked the SSL Enabled check boxon this dialog to indicate secure communication between the Quality of Serviceproxy server and the origin server.

Key Name (optional)If you specified a key database file in the Key database (.kdb) file pathon the Quality of Service HTTP proxy server dialog (step 2), and if this

Figure 18. Origin HTTP Server Configuration dialog (Windows)


file contains more than one certificate, optionally enter the name of thecertificate that will be used for secure communication between theQuality of Service proxy server and the origin server. If you do notenter a certificate name, the default name will be used.

5. Complete the installation of the Quality of Service endpoint by following theinstructions in “Completing the installation” on page 91.


Web Services Courier informationContinue the installation by completing the following steps if you are installing aWeb Services Courier endpoint.1. Click Next to display the Web Services Courier Options dialog.2. Click the radio button for the features that you want to enable. You must

enable at least one of the following:v The Web Services Courier data warehouse feature. Enable this feature if you

plan to use Tivoli Decision Support to view historical reports of datacollected by Web Transaction Performance applications.

v The Tivoli Enterprise Console event forwarding feature. Enable this featureis you want the Web Transaction Performance administrator to have theoption of forwarding events to the Tivoli Enterprise Console.

3. If you enabled the Tivoli Event Console forwarding feature, go to Step 4. Ifyou enabled only the Web Services Courier data warehouse feature, go to Step7.

4. Click Next to display the Tivoli Enterprise Console Event Forwarding Optionsdialog.

5. Do one of the following:v Enable forwarding of events to the Tivoli Enterprise Console through a

Tivoli environment. (To use this option, the machine on which you areinstalling the Web Services Courier endpoint must already be an endpointof a Tivoli management region server.)a. Select the radio button labeled Forward events through a Tivoli

environment.

Figure 19. Tivoli Enterprise Console Forwarding Options dialog (Windows)


b. Enter the absolute path to the LCF file on this computer (lcf_env.cmdon Windows systems or lcf_env.sh on UNIX systems) in the lcf_envFile Path field. Do not include the LCF file name in the path.

—OR—v Enable forwarding of events to a specified Tivoli Enterprise Console server.

a. Enter the fully qualified name of the host machine for the TivoliEnterprise Console server in the Tivoli Enterprise Console Server HostName field.

b. Enter a valid port number on the Tivoli Enterprise Console server in theTivoli Enterprise Console Server Port field.

6. If you enabled the data warehouse feature, go to Step 7. If you did not enablethe data warehouse feature, go to “Completing the installation” on page 91.

7. Click Next to display the Database Configuration dialog.

8. From the drop-down list, select the kind of database to be used for creatingthe Web Services Courier data warehouse: Oracle or DB2.The installation program activates text fields appropriate to the database youselected.

9. Enter information about the database.v For an Oracle database, enter the following information in the text fields:

Oracle Host NameThe fully qualified host name or the IP address of the hostmachine for the Oracle database

Oracle Port NumberThe port number being used by the Oracle listener

Oracle SID The SID name for the Oracle database

Database User IDThe user ID for the tablespace to be used for the WebServices Courier data warehouse

Figure 20. Database Configuration dialog (AIX)



v For a DB2 database, enter the following information in the text fields:

DB2 Instance (AIX only) The name of a user authorized to the DB2instance under which the database for the Web ServicesCourier data warehouse was created. This can be the nameof the user under which the DB2 client was installed on theWeb Services Courier endpoint machine. (See “Creating thedatabase” on page 42.)

DB2 Installation DirectoryThe full path to the home directory of the owner of the DB2instance under which the DB2 database for the WebServices Courier data warehouse was created.– On AIX systems, specify the path name up to, but not

including, the sqllib subdirectory. For example, thedefault entered by the installation program is/usr/db2inst1.

– On Windows systems, include the sqllib subdirectory.For example, the default entered by the installationprogram is C:\Program Files\IBM\Sqllib.

DB2 Database NameThe alias used on the Web Services Courier endpoint torefer to the DB2 database for the data warehouse

Database User IDThe user ID to be used by the Web Services Courierendpoint to access the DB2 database for the datawarehouse. (See “Creating the database user” on page 42.)


10. Click Next.If the database that you specified in Step 9 is not empty, a pop-up dialog isdisplayed. Go to Step 11.If the database that you specified in Step 9 is empty, the Internet ManagementServer Information dialog is displayed. Go to Step 2 under “Completing theinstallation” on page 91.

Note: If the database is empty, the installation program creates and initializesa Web Services Courier data warehouse. The Web Services Courier datawarehouse is a set of database tables that will be used by this WebServices Courier endpoint and possibly shared by other Web ServicesCourier endpoints yet to be installed.

11. Do the following on the pop-up dialog:a. Select one of the following items from the drop-down list:

v Data warehouse tables already exist. This is a shared database.

Select this item if the database that you specified in Step 9 containstables that support one or more previously installed Web ServicesCourier endpoints.

v Data warehouse tables do not exist on this database. Create allnecessary tables.


Select this item if the database that you specified in Step 9 containstables that support WebSphere Site Analyzer or some other application,but does not contain Web Services Courier data warehouse tables. Theinstallation program will create and initialize the Web Services Courierdata warehouse—a set of database tables to be used by this WebServices Courier endpoint and possibly shared by other Web ServicesCourier endpoints yet to be installed.

b. Click OK.12. Complete the installation of the Web Services Courier endpoint by following

the instructions under “Completing the installation”.

Completing the installationFinish the installation by completing the following steps.1. Click Next to display the Internet Management Server Information dialog. The

Internet Management Server Information dialog collects information about theInternet Management Server to which the endpoint will be registered. It alsocollects information about the proxy server, if any, for the management server.

2. Use the following fields to specify information about the Internet ManagementServer to which the endpoint will be registered.

Host Name Enter the fully qualified host name or the IP address of the hostmachine for the Internet Management Server.

User Name Enter the user ID of any user authorized to log on to themanagement server.

Password Enter the password for the user specified in the User Namefield.

SSL Enabled Check this box to enable secure communication between theendpoint and the management server.

Figure 21. Internet Management Server Information dialog (Windows)


Note: The type of communication (secure or non-secure) mustmatch the type specified during installation of themanagement server.

Use Default Port Number?Specify whether the management server uses the port numberdisplayed in the Port Number field. By default, the Yes radiobutton is selected. To specify a different port, click the No radiobutton and enter the correct port number in the Port Numberfield.

Port Number Enter the port number used by the management server. Thisfield is active only if the Use Default Port Number? radiobutton is set to No.

3. Enter information about the proxy server, if any, used to access the InternetManagement Server. Do one of the following:a. Accept the No Proxy default if there is no proxy server.

—OR—b. Provide information about the proxy server:

1) Click either the Socks or HTTPS radio button to indicate the type ofcommunication used by the proxy server.

2) Enter the fully qualified host name and the port number for the proxyserver in the designated fields.

4. Click Next. An information screen specifies the destination directory and theamount of disk space for the endpoint installation.


When you finish the installation program, the endpoint runs immediately on thehost machine.

Post-installation proceduresIf you installed a Web Services Investigator or Quality of Service endpoint,complete the post-installation procedures described in this section.

Post-installation procedures for Web Services Investigatorendpoints on Windows systems

For each Web Services Investigator endpoint that you installed on a Windowssystem, you specified a user account for the STI Player (called the STI Playeraccount). The Tivoli Internet Management Endpoint service uses this account toaccess the Microsoft Internet Explorer browser so that the STI Player can replayrecorded Web transactions from the endpoint. During installation, you eitherselected an existing account or you let the installation program create a newaccount named TivoliSTIPlayback. You must perform the following proceduresrelated to the STI Player account on each computer where the STI Player isinstalled:v Add the STI Player account to the access and launch permissions of the OLE

server.v If you let the installation program create the TivoliSTIPlayback account, test the

operation of Internet Explorer.v (As needed) Whenever you change the password for the STI Player account,

identify the password change to the services used by the STI Player.


Adding OLE server permissions for the STI PlayerThe default access and launch permissions of the OLE server do not give the STIPlayer account permission to launch Microsoft Internet Explorer. You can add theSTI Player account to the OLE server’s launch and access permissions by using theDCOMCNFG.EXE utility. This utility is located in the following directory:SystemRoot\system32

where SystemRoot is the drive and directory where the Windows system is installed(for example, C:\Winnt).

Complete the following procedure:1. Using Windows Explorer, navigate to the directory where the DCOMCNFG.EXE

file is located.2. Double-click the DCOMCNFG.EXE file.3. Click the Default Security tab.4. Click the Edit Default button in the Default Access Permissions group.5. Click the Add button on the Registry Value Permissions dialog.6. Select the computer name from the List Names From drop-down list.7. Click the Show Users button.8. Select the STI playback user (for example, TivoliSTIPlayback) from the list of

names.9. Click Add.

10. Click OK on the Add Users and Groups dialog.11. Click OK on the Registry Value Permissions dialog.12. Click Apply.13. Click the Edit Default button in the Default Launch Permissions group.14. Repeat Steps 5 through 11.

Testing Internet Explorer for the TivoliSTIPlayback accountIf you let the installation program create the TivoliSTIPlayback account, use thefollowing procedure to test the operation of Internet Explorer on each endpointmachine where a Web Services Investigator endpoint is installed.1. Reboot the computer.2. Log on as the TivoliSTIPlayback user.3. Start Internet Explorer.4. If the Welcome to the Internet Wizard dialog is displayed, follow the

instructions on the Internet Connection Wizard to set up your Internetconnection.

5. Restart the endpoint as follows:a. Select Start → Programs → Tivoli → Stop Internet Management Endpoint.b. Select Start → Programs → Tivoli → Start Internet Management Endpoint.

When you are finished with this procedure, you can log off and then log on againunder the account normally used to log on to the endpoint machine (for example,Administrator).

Making password changesWhenever you change the password for the STI Player account, you must identifythe password change to the following services:v Tivoli Internet Management Endpointv Web Detailer Agent


v Web Detailer Proxy

Complete the following procedure whenever there is a password change for theaccount:v For Windows NT:

1. Display the list of services.– For Windows NT:

a. Select Settings from the Windows Start menu.b. Select Control Panel.c. Double-click the Services icon.

– For Windows 2000:

a. Select Control Panel from the Windows Start menu.b. Select Administrative Tools.c. Select Services.

– For Windows XP:

a. Select Settings from the Windows Start menu.b. Select Control Panel.c. Double-click the Component Services icon.d. Double-click Services (Local).

2. Repeat the following steps for each of the services listed previously:– For Windows NT:

a. Select the service from the list of services.b. Click Startup....c. Select the This Account radio button on the Service dialog.d. Enter the password in the Password field.e. Enter the same password in the Confirm Password field.f. Click OK.

– For Windows 2000 or Windows XP:

a. Right-click the name of the service in the list of services.b. Select Properties from the pop-up menu.c. Select the Log On tab.d. Select the This Account radio button.e. Enter the password in the Password field.f. Enter the same password in the Confirm Password field.g. Click OK.

Post-installation procedure for secure Quality of Service proxyservers

For proper authentication to the Internet, a secure (SSL-enabled) Quality of Serviceproxy server requires a key database file, created with the IBM Key ManagementUtility, that contains a digital certificate issued by a trusted certificate authority(CA). If this file does not exist prior to installation, the installation program installsa key database file (named keys.kdb) containing a self-signed certificate. It alsoinstalls the IBM Key Management Utility. You can use this program to create a newkeys.kdb file, request a certificate from a trusted CA if you do not already haveone, and store the certificate in the keys.kdb file.


Follow these steps to obtain and install a keys.kdb file with a trusted certificate onthe Quality of Service endpoint machine. Bulleted items reference the proceduresrequired to perform each step.1. Start the IBM Key Management Utility on the Quality of Service endpoint

machine.v “Starting the IBM Key Management Utility” on page 148.

2. Create a new key database file. Name the file keys.kdb. When creating the keydatabase file, check the Stash the password to a file option.v “Creating a new key database file” on page 150.v See also “Specifying a password for a key database file” on page 149 for

guidelines on creating a password for the key database file.3. If you do not already have a certificate signed by a trusted CA, create a new

key pair and certificate request using the keys.kdb file that you created in Step2. If you already have a trusted certificate, go to Step 4.v “Creating a new key pair and certificate request” on page 151.v See also “Key files installed with Web Transaction Performance” on page 148

for a list of trusted certificate authorities recognized by IBM.4. Follow these steps to store the CA-signed certificate in the keys.kdb file and to

copy the key files to the appropriate location on the machine.a. Stop the Quality of Service proxy server.

v “Stopping and starting the Quality of Service proxy server” on page 165.b. Store the CA-signed certificate in the keys.kdb file.

v “Receiving a CA-signed certificate” on page 152.c. Copy the keys.kdb and keys.sth files to the following directory:

install_dir/Endpoint/IBMHTTPServer/ssl/keys

where install_dir is the full path name of the directory where the Quality ofService endpoint was installed. These files replace the keys.kdb filecontaining the self-signed certificate, and the associated keys.sth file, thatwas created during installation.

d. Restart the Quality of Service proxy server.v “Stopping and starting the Quality of Service proxy server” on page 165.


Chapter 8. Installing the STI Recorder

The STI Recorder is a separately installable program that operates on supportedWindows platforms. You do not need to install the recorder on any endpointmachine. Follow the instructions in this chapter to obtain and install the recorder.

Note: This chapter describes how to perform interactive installations of the STIRecorder (installations with a GUI). You can also install the STI Recordersilently from the command line with no GUI. See Chapter 11, “Using silentmode” for information on silent installations.

Before you install the STI RecorderComplete the following activites before you install the STI Recorder.1. Verify that the system on which you are installing the STI Recorder meets the

system requirements and software prerequisites listed in Chapter 2.2. Verify that the Internet Management Server is up and running. The installation

process registers the STI Recorder with the management server.3. Collect the following information about the management server. You will need

to provide this information during installation of the STI Recorder.v The fully qualified host name or the IP address of the host machine for the

management server.v The type of communication—secure (SSL-enabled) or non-secure—used by

the management server. (If you specify https:// in the Web address for themanagement server when accessing it from a Web browser, it is a secureserver.)

v The port number used by the management server for communication. Thedefault port number for non-secure communication is 80. The default portnumber for secure communication is 443.

4. If the STI Recorder needs to connect to the Internet Management Serverthrough a proxy server, verify that the proxy is configured in the connectionsettings of Internet Explorer. (Microsoft Internet Explorer Version 6.0 must beinstalled on the machine where you are installing the STI Recorder.) Followthese steps to configure the proxy settings:a. Open the Internet Explorer browser.b. Select Internet Options from the Tools menu.c. Select the Connections tab.d. Click the LAN Settings... button.e. Click the check box labeled Use a proxy server for your LAN.f. Enter the fully qualified name of the host machine for the proxy server in

the Address field.g. Enter the port number used by the proxy server in the Port field.

5. Obtain the installation file, setup_sti_recorder.exe, from the product CD ordownload it from the Internet Management Server.v The installation file is located in the root directory of the IBM Tivoli

Monitoring for Transaction Performance, Version 5.1.0: Web TransactionPerformance Component Software CD.

97

v You can download the installation file from the Internet Management Serverby following these steps:a. Log on to the Internet Management Server from a supported browser.b. From the Portfolio, click Synthetic Transaction Investigator.c. Click Download Transaction Recorder.d. Follow the instructions in the work area to download the software to a

local or network-accessible drive.

Installing the recorderTo install the STI Recorder, perform the following steps:1. Navigate to the setup_sti_recorder.exe file on your local or

network-accessible drive.2. Double-click the file name or enter setup_sti_recorder in a command window

to begin the installation process.3. Click Next on the Welcome screen to display the Destination Directory dialog.4. Do one of the following:



5. Click Next. The installation program creates the installation directory youspecified if it does not already exist.

Figure 22. Instructions for downloading the STI Recorder


The Internet Management Server Information dialog appears.

6. Enter information in the following fields about the Internet Management Serverto which the STI Recorder will be registered.

Host Name Enter the fully qualified host name or the IP address of the hostmachine for the Internet Management Server. (Do not include aprotocol. For example, enter imsserver.it.yourcompany.com,not https://imsserver.it.yourcompany.com.)

SSL Enabled Select this box if the management server is using Secure SocketsLayer (SSL) communications. If you specify https:// in theWeb address for the management server when accessing it froma Web browser, select this option.

Use Default Port Number?Specify whether the management server uses the port numberdisplayed in the Port Number field. By default, the Yes radiobutton is selected. To specify a different port, click the No radiobutton and enter the correct port number in the Port Numberfield.

Port Number Enter the port number used by the management server. Thisfield is active only if the Use Default Port Number? radiobutton is set to No.

Proxy ProtocolAccept the No Proxy default or click the appropriate radiobutton (Socks or HTTPS) to indicate the type ofcommunication that the proxy server will use to connect to theInternet Management Server.

Figure 23. Internet Management Server Information dialog (STI Recorder installation)

Chapter 8. Installing the STI Recorder 99

7. Click Next. An information screen displays the installation path and theamount of disk space that is needed for the installation.



Chapter 9. Installing the Web Transaction Performancediscovery guide

Tivoli Decision Support discovery guides are add-on software modules, installedon top of Tivoli Decision Support, that turn raw data gathered by Tivoli or otherIBM applications into viewable reports. Web Transaction Performance provides thefollowing Tivoli Decision Support discovery guide:v Tivoli Decision Support for Web Transaction Performance

(also called the Web Transaction Performance discovery guide)

The Web Transaction Performance discovery guide produces historical reports thatcontain performance and availability data collected from the Web servicesenvironment in which the Web Transaction Performance applications operate.

This chapter describes the activities needed to set up Tivoli Decision Support sothat users can view and work with data collected by the Web TransactionPerformance applications. To learn more about Tivoli Decision Support, refer to theTivoli Decision Support documentation listed under “Prerequisite publications” onpage xiii.

Table 16 summarizes the tasks you must perform to prepare for and install the WebTransaction Performance discovery guide.

Table 16. Tasks required to install the Web Transaction Performance discovery guide

Task Refer to

1. Review the system and prerequisite softwarerequirements for the Web Transaction Performancediscovery guide.

“Requirementssummary” on page 102

2. Set up Tivoli Decision Support to work in a WebTransaction Performance environment.

“Setting up TivoliDecision Support” onpage 102

3. Set up connectivity to the data sources used by the WebTransaction Performance discovery guide and identifythe data sources to Tivoli Decision Support.

“Configuring a datasource” on page 103

4. Make the Shared Data component accessible to all usersif you are running Tivoli Decision Support over anetwork.

“Configuring the shareddata files” on page 105

5. Install and import the Web Transaction Performancediscovery guide. Assign data sources to the queriesprovided with the Web Transaction Performancediscovery guide.

“Setting up the WebTransaction Performancediscovery guide” onpage 105

101

Requirements summaryTable 17 summarizes the system and prerequisite software requirements for theWeb Transaction Performance discovery guide:

Table 17. System and software requirements for the Web Transaction Performancediscovery guide

Requirement Detail

Tivoli Decision Support Tivoli Decision Support 2.1.1 with Patch 7

Tivoli Decision Support components must be installed onWindows NT 4.0 systems with Service Pack 5 or higher oron Windows 2000 systems. Refer to the Tivoli DecisionSupport Installation Guide for detailed system requirementsfor Tivoli Decision Support.

Database Client You must install a database client on the machine wherethe Tivoli Discovery Administrator is installed. Thedatabase client must connect to the Web Services Courierdata warehouse, which is the source of the data used bythe Web Transaction Performance discovery guide.

The supported database clients for the Web TransactionPerformance discovery guide are as follows:

v Oracle 8.1.6 or higher

v Oracle 9i

v DB2 7.1 or higher

ODBC Drivers Use the ODBC drivers provided by your database clientsoftware to configure an ODBC connection for TivoliDiscovery Administrator to the Web Services Courier datawarehouse.

Disk Space for the WebTransaction Performancediscovery guide

10 MB

Setting up Tivoli Decision SupportTo set up Tivoli Decision Support to work with Web Transaction Performance, youmust install at least one machine in the enterprise for a Tivoli Decision Supportadministrator. Install the following software on this machine:v The Discovery Administrator component

This is a separately installable Tivoli Decision Support component that includesseveral applications. The principal application is the Tivoli DiscoveryAdministrator, a program that the administrator uses to set up connections todata sources, import discovery guides, generate reports, and perform otheradministrative functions. When you install the Discovery Administratorcomponent, select the option to install Cognos Powerplay and CognosTransformer.

v (optional) The Discovery Client componentThis is a separately installable Tivoli Decision Support component. TheDiscovery Client component contains the Tivoli Discovery Interface, thegraphical user interface that provides the functionality needed to view and workwith reports.

v (stand-alone installation only) The Shared Data Component


The Shared Data component (or shared data files) is a set of files that includes thedata required to build cubes, schedule tasks, and generate and explore views. Ifyou install Tivoli Decision Support in standalone mode (all components on onemachine), you must install the Shared Data component on the administrator’smachine. If you install Tivoli Decision Support in network mode (a networkconfiguration for multiple users), performance can be improved if the SharedData component be installed on a separate network file server. The administratorand all other users must specify a network share to the folder containing theshared data files before building or working with reports.

v An Oracle or DB2 database clientYou can use the ODBC drivers provided with the database client to set upconnectivity to the Web Services Courier data warehouse.

v The Web Transaction Performance discovery guideAfter installing the discovery guide, use the Tivoli Discovery Administrator toimport it into Tivoli Decision Support and assign it to a data source.

In a multiple user environment, users other than the administrator need onlyinstall the Discovery Client on their machines. These machines do not contain theDiscovery Administrator, discovery guides, or a database client.

Configuring a data sourceThe data source for the Web Transaction Performance discovery guide is the WebServices Courier data warehouse. The Web Services Courier data warehouse isspace in an RDBMS that is installed either on the Web Services Courier endpointor on a separate RDBMS server machine. In order to use the Web Services Courierdata warehouse as a data source, you must complete the following procedures:

Note: Some of the reports provided by the Web Transaction Performance discoveryguide use data provided by WebSphere Site Analyzer. In order to run thesereports, the WebSphere Site Analyzer data must be in the same tablespace asthe Web Services Courier data warehouse. The WebSphere Site Analyzertables must exist in the tablespace before you install the Web ServicesCourier endpoint.

1. Install a database client on the administrator’s machine. Refer to your databasedocumentation for information about installing a database client.

2. Set up an ODBC connection to the data source (the Web Services Courier datawarehouse). The procedure for setting up a connection to an Oracle data sourceis different from the procedure for DB2.

3. Identify the data source to Tivoli Decision Support by using the TivoliDiscovery Administrator graphical user interface.

Setting up an ODBC data source connection for OracleFollow these steps to set up an ODBC data source connection if the Web ServicesCourier data warehouse uses an Oracle RDBMS.1. Display the ODBC Data Source Administrator dialog:

v For Windows NT:a. Select Settings from the Windows Start menu.b. Select Control Panel.c. Double-click the Data Sources (ODBC) icon.

v For Windows 2000:a. Select Control Panel from the Windows Start menu.b. Select Data Sources (ODBC).

Chapter 9. Installing the Web Transaction Performance discovery guide 103

2. Select the System DSN tab.3. Click Add.4. Select the ODBC driver that was installed with the Oracle database client.5. Click Finish.6. Enter the name of the database in the Data Source Name field.

The name you enter in this field will be used to identify this data source toTivoli Discovery Administrator. This name can be the same as, or differentfrom, the name you specified in the Net Service Name field when you installedand configured the database client.

7. Enter a description for the data source in the Description field.8. Enter the fully qualified name of the host machine for the RDBMS server in the

Server Name field.9. Click OK.

Setting up an ODBC data source connection for DB2Follow these steps to set up an ODBC data source connection if the Web ServicesCourier data warehouse uses a DB2 RDBMS.1. Display the Client Configuration Assistant dialog:

a. Select Programs from the Windows Start menu.b. Select DB2 for Windows NT or DB2 for Windows 2000.c. Select Client Configuration Assistant.

2. Click Add to display the Add Database SmartGuide dialog, a set of tabbedpages.

3. On the Source page, select the radio button for manually configuring aconnection to a DB2 database.

4. Click Next.5. On the Protocol page, select the TCP/IP radio button.6. Click Next.7. On the TCP/IP page, enter the fully qualified host name and the port number

of the RDBMS server. (The default port number is 50000.)8. Click Next.9. On the Database page, enter the DB2 database name and alias in the

appropriate fields. The database alias is the name that will be used to identifythis data source to Tivoli Discovery Administrator.

10. Click Done. A confirmation window is displayed.11. Click Test Connection. The Connect to DB2 Database dialog is displayed.12. Enter a valid user ID and password for the database.13. Click OK.

If the connection is valid, the database is displayed in the Available DB2Databases list on the Client Configuration Assistant dialog.

Identifying data sources to Tivoli Decision SupportFollow these steps to identify the data source (the Web Services Courier datawarehouse) to the Tivoli Discovery Administrator.1. Open the Tivoli Discovery Administrator:

a. Select Programs from the Windows Start menu.b. Select TDS 2.1.c. Select Tivoli Discovery Administrator.


2. Select Add from the Data Sources menu. The Add Data Source Wizard dialogis displayed.

3. Select a data source name from the drop-down list.The data source name is the database name or alias that you specified whenyou configured an ODBC data source connection for the database. See Step 6 onpage 104 under Setting up an ODBC data source connection for Oracle or Step9 on page 104 under Setting up an ODBC data source connection for DB2.

4. Click Next.5. Enter a valid user ID and password for the database.6. Click Next.7. Enter the database qualifier in the Qualifier field. The database qualifier is

used to reference tables in the database. The database qualifier is normally thesame as the user ID, except that the database qualifer must be all uppercase.For example, if the user ID is user1 the database qualifier must be USER1.

8. Click Next.9. Confirm the options you selected. Click Finish to add this data source.

Configuring the shared data filesIf you installed Tivoli Decision Support in network mode, the DiscoveryAdministrator and all Discovery Client components must be able to find theshared data files (the files of the Shared Data component). This is necessary beforethe administrator and other users can build or work with reports.

If you are an administrator, complete the following procedure to set upconnections to the shared data files.

Note: This procedure is not necessary if you installed Tivoli Decision Supportusing the stand-alone installation option.

1. Use Windows Explorer to navigate to the folder in which you installed theShared Data Component (by default, \Program Files\TDS 2.1). Create a sharedfolder and grant full access rights to all Tivoli Decision Support users. Thename of the share must not contain the space character.

2. Specify the path to the shared data files:a. Open the Tivoli Discovery Administrator:

1) Select Programs from the Windows Start menu.2) Select TDS 2.1.3) Select Tivoli Discovery Administrator.

b. Select Options from the View menu. The Options dialog is displayed.c. Click the General tab.d. In the Network field, enter the name of the drive (and folder, if necessary)

that contains the Data and Reports folders.e. Click OK to close the Options dialog.

3. If the Discovery Client component is also installed on this machine, open theTivoli Discovery Interface and repeat the procedure in Step 2.

4. Tell all other users where the shared data files are located and instruct them toconfigure the path using the Tivoli Discovery Interface.

Setting up the Web Transaction Performance discovery guideTo use the Web Transaction Performance discovery guide, you must perform thefollowing procedures:


1. Uninstall the Tivoli Decision Support for Tivoli Web Services Managerdiscovery guide if it exists on the machine where you want to install the WebTransaction Performance discovery guide.

2. Install the Web Transaction Performance discovery guide.3. Import the discovery guide into Tivoli Decision Support.4. Assign a data source to each query associated with the discovery guide. You

must perform this step before you can build cubes from the data provided bythe data source.

Uninstalling the Tivoli Web Services Manager discovery guideFollow these steps to uninstall the Tivoli Web Services Manager discovery guide:1. Open the Tivoli Discovery Administrator:


2. Click the Decision Support Guides folder in the directory tree.3. Select Tivoli Web Services Manager from the list of discovery guides in the

properties pane.4. Select Delete from the Decision Support Guides menu.

Installing the Web Transaction Performance discovery guideFollow these steps to install the Web Transaction Performance discovery guidefrom the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: WebTransaction Performance Component Software CD.1. Insert the CD into the drive.2. Navigate to the following directory on the CD:

D:\tds_guides\Web Transaction Performance

where D is the CD-ROM drive letter.3. Double-click the setup.exe file or enter setup in a command window to begin

the installation process.4. Follow the instructions on the installation dialogs to complete the installation.

Importing the discovery guideFollow these steps to import the Web Transaction Performance discovery guide.1. Open the Tivoli Discovery Administrator.


2. Select Import from the Decision Support Guides menu.3. Select Web Transaction Performance from the list of discovery guides on the

Import Decision Support Guides dialog.4. Click OK.

Assigning data sourcesFollow these steps to assign a data source to the queries for building cubes.1. Open the Tivoli Discovery Administrator:



2. Select Assign Data Source from the Data Source menu. The Assign Data Sourcedialog is displayed. This dialog displays a list of query names and theirassociated cube names.

3. Select one or more query names from the Query Names column.4. Select a data source name from the Data Source drop-down list.

The data source name is the database name or alias that you specified whenyou configured an ODBC data source connection to the database. See Step 6 onpage 104 under Setting up an ODBC data source connection for Oracle or Step9 on page 104 under Setting up an ODBC data source connection for DB2.

5. Click OK to assign the data source to the selected queries.6. Test connectivity as follows:

a. Right-click the data source name in the content pane (right side).b. Click Test Connectivity.


Chapter 10. Uninstalling Web Transaction Performancecomponents

This chapter describes how to uninstall the Web Transaction Performancecomponents. It includes the actions you must take prior to uninstallation, theuninstallation steps, and the follow-up procedures.

Note: This chapter describes how to perform interactive uninstallations(uninstallations with a GUI). You can also uninstall Web TransactionPerformance product components silently from the command line with noGUI. See Chapter 11, “Using silent mode”for information on silentuninstallations.

Table 18 lists the Web Transaction Performance components, grouped according tothe type of system on which they are installed. The organization of this chapter,which parallels the ordering of components in the table, is meant to emphasize thefollowing dependencies:v You can remove an individual Internet Management Endpoint at any time,

provided the Internet Management Server is running.v To remove the Internet Management Server, you must first remove all endpoints

one by one. Then uninstall the Internet Management Server as the last step.v Uninstallation of the STI Recorder is not dependent on any other component.

Note that the STI Recorder is supported only on Windows sytems.

Table 18. Web Transaction Performance components

System Component To uninstall, refer to:

Windows Internet Management Endpoint Uninstalling an InternetManagement Endpoint on Windowson page 111

Internet Management Server Uninstalling the InternetManagement Server on Windows onpage 113

UNIX Internet Management Endpoint Uninstalling an InternetManagement Endpoint on UNIX onpage 114

Internet Management Server Uninstalling the InternetManagement Server on UNIX onpage 115

Windows STI Recorder Uninstalling the STI Recorder onpage 116

Uninstall file names and locationsWhen a Web Transaction Performance component is installed, the installationprogram creates the following uninstall files and places them in a subdirectory.v uninstall.bin, the uninstall native launcher created when the management

server or an endpoint is installed on a UNIX-based system. (Exception: A nativelauncher is not available for S/390 Linux.)

109

v uninstall.exe, the uninstall native launcher created when any Web TransactionPerformance component is installed on a Windows system.

v uninstall.opt, the sample uninstall option file created when any WebTransaction Performance component is installed on any system. This file is usedfor silent uninstallations.

v uninstall.jar, the JAR file created when the management server or an endpointis installed on any system. The uninstall native launchers run the uninstall.jarfile.

The subdirectory in which these files are placed varies according to the WebTransaction Performance component. Table 19 shows the uninstall subdirectory foreach component.

Table 19. Uninstall File Locations

Component Uninstall subdirectory

Internet Management Server inst_dir/ManagementServer/_uninst51

Internet Management Endpoint inst_dir/Endpoint/_uninst

STI Recorder inst_dir/STI-Recorder/_uninst

where inst_dir is the installation directory for the component. The default installationdirectory for any Web Transaction Performance component is as follows:

Windows Systems: C:\Program Files\Tivoli\Internet

UNIX Systems: /usr/Tivoli/Internet (on AIX)/Tivoli/Internet (on S/390 TurboLinux)

/opt/Tivoli/Internet (on other UNIX-based systems)

Note: Table 19 shows the uninstall directories in UNIX format only. For Windowsformat, replace the forward slashes (/) in the directory name with backwardslashes (\).


Uninstalling an Internet Management Endpoint on Windows

Repeat the steps in this section for each Internet Management Endpoint that youwant to uninstall from a Windows system.

Before You BeginVerify that the Internet Management Server is up and running. The uninstallprocess un-registers the endpoint from the management server.

Procedure1. Log on as Administrator or as a user with administrator privileges to the host

machine for the endpoint.2. Select Start → Programs → Tivoli → Uninstall Internet Management Endpoint.3. Click Next to begin uninstalling the endpoint.4. If you are uninstalling a Web Services Courier endpoint that uses a Web

Services Courier data warehouse, do the following on the Data WarehouseUninstall Action dialog:a. Select one of the following radio buttons:

v Preserve data warehouse information, if you want to leave the WebServices Courier data warehouse tables intact.

v Remove all data warehouse information, if you want the uninstallprogram to remove all tables in the Web Services Courier datawarehouse.

Note: This option removes all tables in the data warehouse even if theyare shared by another Web Services Courier endpoint.

b. Click Next.5. When the uninstall program completes, click Finish to exit.

When You Finish1. If you are uninstalling a Web Services Investigator endpoint, you must

manually remove some files from the Windows system directory. Follow thesesteps to remove the files:a. Navigate to the following directory:

SystemRoot\system32

where SystemRoot is the drive and directory where Windows is installed (forexample, C:\WINNT or C:\WINNT40).

b. Delete the following files:wd_WS2i.exewd_lspi.dllsporder.dllwd_sdk.dllwd_ete.dllibmts.dllwd_WS2s.lsp

2. (optional) Follow these steps to delete any additional files remaining on thesystem that the uninstall program did not remove. The uninstall program doesnot remove any files that the installation program did not originally place onthe system. These include log files and files placed on the system by the user.a. Open a Windows Explorer session.

Chapter 10. Uninstalling Web Transaction Performance components 111

b. Navigate to the installation directory for the endpoint. The defaultinstallation directory is the following:C:\Program Files\Tivoli\Internet

c. Select the Endpoint folder and the log files (*_log.txt files) on the rightside of the Explorer window.

d. Press the Delete key.3. Reboot the computer.4. (recommended) If you are uninstalling a Web Services Investigator endpoint with

a TivoliStiPlayback user account, follow these steps to delete the account. Seethe Web Services Investigator section under “Before you install an InternetManagement Endpoint” on page 77 for information about the TivoliStiPlaybackaccount.v For Windows NT:

a. Select Programs from the Start menu.b. Select Administrative Tools (Common).c. Select User Manager.d. Select TivoliStiPlayback from the list of user names.e. Select Delete from the User menu.

v For Windows 2000:a. Right-click the My Computer icon on the Windows 2000 desktop.b. Select Manage.

The Computer Management window is displayed.c. Click Users under Local Users and Groups.d. Right-click

TivoliStiPlayback in the list on the right side of the Users window.e. Select Delete.


Uninstalling the Internet Management Server on Windows

Follow the instructions in this section to uninstall the Internet Management Serverfrom a Windows system.

Before You BeginUninstall all endpoints registered to the Internet Management Server.

Procedure1. Log on as Administrator or as a user with administrator privileges to the host

machine for the Internet Management Server.2. Select Start → Programs → Tivoli → Uninstall Internet Management Server.3. Click Next to begin uninstalling the Internet Management Server.4. When the uninstall program completes, click Finish to exit.

When You Finish1. (optional) Follow these steps to delete any files remaining on the system that the

uninstall program did not remove. The uninstall program does not remove anyfiles that the installation program did not originally place on the system. Theseinclude log files and files placed on the system by the user.a. Open a Windows Explorer session.b. Navigate to the installation directory for the management server. The

default installation directory is the following:C:\Program Files\Tivoli\Internet

c. Select the ManagementServer folder and the log files (*_log.txt files) onthe right side of the Explorer window.

d. Press the Delete key.2. Reboot the computer.


Uninstalling an Internet Management Endpoint on UNIX

Repeat the steps in this section for each Internet Management Endpoint that youwant to uninstall from a UNIX-based system.

Before You Begin1. Verify that the Internet Management Server is up and running. The uninstall

process unregisters the endpoint from the management server.2. Note the installation directory for the endpoint (referred to as inst_dir in this

procedure). See Table 11 on page 51 for a list of default installation directories.

Procedure1. Log on as the root user.2. Enter one of the following commands from the root directory:

v For any UNIX system except S/390 TurboLinux:inst_dir/Endpoint/_uninst/uninstall.bin

—OR—v For any UNIX system, including S/390 TurboLinux:

java -jar inst_dir/Endpoint/_uninst/uninstall.jar

where inst_dir is the installation directory for the endpoint.3. Click Next to begin uninstalling the endpoint.4. If you are uninstalling a Web Services Courier endpoint that uses a Web

Services Courier data warehouse, do the following on the Data WarehouseUninstall Action dialog:a. Select one of the following radio buttons:

v Preserve data warehouse information, if you want to leave the WebServices Courier data warehouse tables intact.

v Remove all data warehouse information, if you want the uninstallprogram to remove all tables in the Web Services Courier datawarehouse.

Note: This option removes all tables in the data warehouse even if theyare shared by another Web Services Courier endpoint.

b. Click Next.5. When the uninstall program completes, click Finish to exit.

When You Finish(optional) Enter the following commands from the root directory to delete any filesremaining on the system that the uninstall program did not remove. The uninstallprogram does not remove any files that the installation program did not originallyplace on the system. These include log files and files placed on the system by theuser.rm -rf inst_dir/Endpointrm - rf inst_dir/*_log.txt

where inst_dir is the installation directory for the endpoint.


Uninstalling the Internet Management Server on UNIX

Follow the instructions in this section to uninstall the Internet Management Serverfrom a UNIX-based system.

Before You Begin1. Uninstall all endpoints registered to the Internet Management Server.2. Note the installation directory for the management server (referred to as

inst_dir in this procedure). See Table 11 on page 51 for a list of defaultinstallation directories.

Procedure1. Log on as the root user.2. Enter the following command from the root directory:

inst_dir/ManagementServer/_uninst/uninstall.bin

where inst_dir is the installation directory for the management server.3. Click Next to begin uninstalling the Internet Management Server.4. When the uninstall program completes, click Finish to exit.

When You Finish(optional) Enter the following commands from the root directory to delete any filesremaining on the system that the uninstall program did not remove. The uninstallprogram does not remove any files that the installation program did not originallyplace on the system. These include log files and files placed on the system by theuser.rm -rf inst_dir/ManagementServerrm - rf inst_dir/*_log.txt

where inst_dir is the installation directory for the management server.


Uninstalling the STI Recorder

Follow the instructions in this section to uninstall the STI Recorder.

Before You BeginNot applicable.

Procedure1. Log on to the machine where the STI Recorder is installed.2. Select Start → Programs → Tivoli → Uninstall Synthetic Transaction Investigator

Recorder.3. Click Next to begin uninstalling the STI Recorder.

An information dialog indicates the location of the STI Recorder.4. Click Next.5. Click Finish to exit.

When You FinishNot applicable.


Chapter 11. Using silent mode

You can install or uninstall a Web Transaction Performance component (InternetManagement Server, Internet Management Endpoint, or STI Recorder) in silentmode from the command line. (You cannot upgrade in silent mode.) Silent modemeans there is no interaction with a GUI. Instead of using a GUI to enter the dataneeded by the install or uninstall program, you specify the data directly on thecommand line or in a file (called an option file).

Silent mode installations or uninstallations with an option file have the advantageof being easily and rapidly repeatable. The option file also serves as a record thatyou can consult whenever the need arises to verify the exact data used for aninstallation.

OverviewThis overview section is organized as a tutorial, introducing concepts, examples,and product information under discrete topics. For specific install procedures,uninstall procedures, and command reference information, refer to “Proceduresand commands” on page 120.

The -silent optionTo install or uninstall a Web Transaction Performance component silently, use the-silent command line option. For example, you can use the following commandformat to install the Internet Management Server to an AIX system:setup_TIMS_aix.bin -silent dataOption...

where dataOption... is the list of data options for this command. A data optionsupplies Web Transaction Performance data needed by the install or uninstallprogram.

Data optionsThis book uses the term data option to refer to command line options that specifythe same information that you provide on a dialog when installing or uninstallinga Web Transaction Performance component in interactive mode. Data options standin contrast to other options (such as -silent) that have no counterpart on theinstall or uninstall program GUI.

Data options are specified using the following formats:

-P entity_ID.dataItem="value"-W entity_ID.dataItem="value"-G globalResponseType="value"

-P and -W optionsThe installation programs collect information about the various entities involved ina Web Transaction Performance installation, such as the management server,database servers, Web servers, and endpoints. The -P and -W options specifyinformation for each entity. For example, the following options specify informationabout the management server—identified by the entity_ID tims and httpserver:

117

-P tims.installLocation="C:\Program Files\Tivoli\Internet"-W httpserver.hostName="wtp.dev.tivoli.com"-W httpserver.port="80"

The distinction between the -P and -W options is that a -P option (product option)involves the addition of files or features to the system. A -W option (wizard paneloption) specifies data needed by the installation program. This distinction is moremeaningful at the program level than from an installation perspective.

-G optionsThe -G options specify responses to pop-up confirmation windows that might bedisplayed when the install or uninstall program is about to install or remove filesor directories. For example, some confirmation windows ask if you want to replacea file that already exists. To suppress all windows with this message, you canspecify your response ahead of time with the replaceExistingResponse option. Forexample:-G replaceExistingResponse="yesToAll"

Other -G options specify global responses to other types of confirmation queriessuch as whether you want to remove an existing file. The full set of -G optionsused by Web Transaction Performance is as follows:-G replaceExistingResponse="yesToAll | yes | noToAll | no"-G replaceNewerResponse="yesToAll | yes | noToAll | no"-G removeExistingResponse="yesToAll | yes | noToAll | no"-G removeModifiedResponse="yesToAll | yes | noToAll | no"

Note that the value for a -G option is one of a fixed set of choices. For anexplanation of the meaning of each of the -G options, see “Data Options” onpage 123.

Command line exampleThe first line below shows the format of the command for silently installing theInternet Management Server on an AIX system from the command line with nooption file. Beneath that is an example with a partial list of data options.setup_TIMS_aix.bin -silent dataOption...

setup_TIMS_aix.bin -silent -P tims.installLocation="/opt/usr/Tivoli"-W httpserver.hostname="wtp.dev.tivoli.com" -W httpserver.port="80"-G replaceExistingResponse="yesToAll" ...

Just a few data options are shown in this example. The actual list of required dataoptions for installing the Internet Management Server is much longer. (See “DataOptions” on page 123 for the complete list.) You can enter data options on thecommand line in any order. Include a space between each option.

Option filesInstead of specifying multiple data options on the command line, you can placesome or all data options in a plain text file called an option file. To specify theoption file on the command line, use the -options option, as in the followingexample. This example uses the setup_Endpoint_w32.exe native launcher to installa Quality of Service endpoint on a Windows system. The setup_QOS.opt file is theoption file.setup_Endpoint_w32 -silent -options setup_QOS.opt

In this example, all data options (options beginning with -P, -W, and -G) areincluded in the option file. Include only data options in an option file. Do notinclude the -silent option or the -options option.


You must enter each option in an option file on a separate line. You can list optionsin any order. The following listing shows what a portion of the setup_QOS.opt fileused in the preceding command might look like.

NoteComment lines and blank lines in option files can cause the installation oruninstallation to fail. Comments and blank lines are included in the examplesin this chapter for the sake of clarity.

# Sample option file for installing Quality of Service endpoint-W feature.qos=true-W feature.baseInstallDir="D:\Program Files\Tivoli\Internet"-W endpoint.name="QOS_ENDPOINT"-W endpoint.description="Quality of Service endpoint"

.

.# Information about the Internet Management Server to which this endpoint# will be registered-W tims.hostName="wtp.dev.tivoli.com"-W tims.userName="admin"-W tims.password="admin"

.

.

It is possible to divide options between the command line and the option file. Inthe preceding example, you could add a measure of security by removing themanagement server password from the option file and entering it on the commandline:setup_Endpoint_w32 -silent -W tims.password="admin" -options setup_QOS.opt

Option files provided by Web Transaction PerformanceWeb Transaction Performance provides the sample option files shown in Table 20on the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: WebTransaction Performance Component Software CD.

Table 20. Sample option files provided by Web Transaction Performance

Component Option file name Description

Internet ManagementServer

setup_TIMS.opt Lists data options to accomplish the following results:

v Install the Internet Management Server on a Solarissystem

v Specify a DB2 database for the managementrepository

Web ServicesInvestigator endpoint

setup_WSI.opt Lists data options for installing a Web ServicesInvestigator endpoint on a Windows system.

Chapter 11. Using silent mode 119

Table 20. Sample option files provided by Web Transaction Performance (continued)

Web Services Courierendpoint

setup_WSC_dw_tec_tme.opt Lists data options to accomplish the following results:

v Install a Web Services Courier endpoint on aWindows system.

v Enable the Web Services Courier data warehousefeature

v Specify an Oracle database for the data warehouse

v Enable forwarding of events to the Tivoli EnterpriseConsole through a Tivoli environment.

setup_WSC_dw_tec_nontme.opt Lists data options to accomplish the following results:

v Install a Web Services Courier endpoint on aWindows system.

v Enable the Web Services Courier data warehousefeature

v Specify an Oracle database for the data warehouse

v Enable forwarding of events directly to a TivoliEnterprise Console server.

Quality of Serviceendpoint

setup_QOS.opt Lists data options for installing a Quality of Serviceendpoint on a Windows system.

STI Recorder setup_STIR.opt Lists data options for installing the STI Recorder. TheSTI Recorder is supported on Windows only.

Procedures and commandsThis section describes the procedures for silently installing and uninstalling WebTransaction Performance components. It also provides detailed descriptions andexamples of the silent mode commands in a formal command reference format.

The information for each component is divided into the following sections:v Procedure provides step-by-step instructions for installing or uninstalling a

component, including preparatory and follow-up activities.v Command specifies the format of the command for installing or uninstalling a

component, followed by a description of the command variables.The command formats are based on the following assumptions:– Commands are entered from the root directory.– Setup launcher files (and the JAR files that they run) are located in the root

directory.– Uninstall launcher files are located in the uninstall directory.

v Data Options lists and describes the data options (options beginning with -P,-W, or -G) for the commands specified in the Command section.

v Examples provides examples that you can literally type on the command line orin an option file.

This section uses the following special characters for commands or options:

[ ] Encloses an optional option or an optional part of a command.When there is a series of optional options pertaining to the sameitem, you must include either all or none of the options.

< > Encloses an option that is required.

... Indicates that you can repeat the preceding variable multiple times.


| Separates mutually exclusive values. You can choose only onevalue in a set of values separated by vertical bars.

Note: Literal character strings in a command or option format are case-sensitive.For example, an option based on the following format would include thecharacter strings -P, tims and installLocation in the exact case shown:-P tims.installLocation="install_dir"


Installing the Internet Management Server

Use the procedure and command described in this section to silently install theInternet Management Server.

Procedure1. Perform the tasks listed under “Before you install the Internet Management

Server” on page 65.2. If you want to use an option file, do one of the following:

v Create the option file. The data options for the Internet Management Serverare listed under “Data Options” on page 123.

v Modify the setup_TIMS.opt file, provided on the IBM Tivoli Monitoring forTransaction Performance, Version 5.1.0: Web Transaction Performance ComponentSoftware CD.

3. Log on to the host machine for the Internet Management Server:v On Windows systems, log on as Administrator, or a user with Administrator

privileges.v On UNIX systems, log on as the root user.

4. Enter the command specified under Command.5. To complete the installation, perform the tasks described under

“Post-installation procedures” on page 71.

CommandUse the following command to silently install the Internet Management Server:setup_launcher [cmd_line_option...] -silent [dataOption...] [-options optionFile]

where:

setup_launcherSpecifies the setup launcher command for the system on which you areinstalling the management server. The launcher commands and targetsystems are as follows:

setup_TIMS_w32 Windows NT or Windows 2000setup_TIMS_aix.bin AIXsetup_TIMS_sol.bin Solaris

cmd_line_optionSpecifies one of a set of options that you can use for logging,troubleshooting, and other purposes. You can enter zero or more of theseoptions on the command line. See “Command line options” on page 169 fora complete list.

dataOption...Specifies one or more data options not included in the option file. Youmust enter a required data option either on the command line or in theoption file.

optionFileSpecifies an option file. The option file is a plain text file that contains oneor more data options, each listed on a separate line.


Data OptionsFollowing is the complete list of data options for installing the InternetManagement Server. Each line is a single option. Include a space between optionswhen entering on the command line. Begin each option on a separate line whenentering in an option file.[-P tims.installLocation="install_dir"]<-W httpserver.hostName="hostname"><-W httpserver.domain="domain_name"><-W httpserver.protocol="http | https"><-W httpserver.port="portnumber"><-W httpserver.user="username"><-W httpserver.group="groupname"><-W database.database_type="Oracle | DB2">

# Options for Oracle<-W database.server="hostname"><-W database.port="portnumber"><-W database.sid="SID_name">

# Options for DB2<-W database.dB2Instance="db2instance"><-W database.db2path="db2path"><-W database.databaseName="db2_database_name">

# Options for both Oracle and DB2<-W database.user="username"><-W database.password="password">

<-W arm_panel.protocolHostPortUri="protocol://hostname:portnumber">

<-G replaceExistingResponse="yesToAll | yes | noToAll | no"><-G replaceNewerResponse="yesToAll | yes | noToAll | no"><-G removeExistingResponse="yesToAll | yes | noToAll | no"><-G removeModifiedResponse="yesToAll | yes | noToAll | no">

[-W logSettings.level="trace_level"][-W logSettings.consoleOut="true | false"]

where:-P tims.installLocation="install_dir"

Specifies the full path name of the directory where you want to install theInternet Management Server.

-W httpserver.hostname="hostname"

Specifies the fully qualified host name or the IP address of the host machine forthe Internet Management Server.

-W httpserver.domain="domain_name"

Specifies the fully qualified name of the domain in which the host machine forthe Internet Management Server resides. For example, if the host machine isservername.it.company.com, the fully qualified domain name isit.company.com.

-W httpserver.protocol="https | http"

Specifies the type of communication to be used between the managementserver and its registered endpoints. Specify https for secure (SSL-enabled)communication. Specify http for non-secure communication.

-W httpserver.port="portnumber"

Specifies the port number on the management server to be used forcommunication with the endpoints. Typically, port 443 is used for securecommunication, port 80 for non-secure.

-W httpserver.user="username"


(UNIX only) Specifies the user name under which the management server willrun.

-W httpserver.group="group_name"

(UNIX only) Specifies the group name under which the management server willrun.

-W database.database_type="Oracle | DB2"

Specifies the type of RDBMS to be used for creating the managementrepository: Oracle or DB2.

-W database.server="hostname"

(Oracle only) Specifies the fully qualified host name or the IP address of the hostmachine for the Oracle database which contains tablespace for the managementrepository.

-W database.port="portnumber"

(Oracle only) Specifies the port number used by the Oracle listener. Include thisoption only if the management repository uses an Oracle database.

-W database.sid="SID_name"

(Oracle only) Specifies the SID name for the Oracle database.-W database.dB2Instance="db2Instance"

(DB2, AIX only) Specifies the name of a user authorized to the DB2 Instanceunder which the database for the management repository was created. This canbe the name of the user under which the DB2 client was installed on themanagement server machine. (See “Creating the database” on page 42.)

-W database.db2Path="db2Path"

(DB2 only) Specifies the full path to the home directory of the owner of the DB2Instance under which the DB2 database for the management repository wascreated.– On AIX systems, specify the path name up to, but not including, the sqllib

subdirectory (for example, /usr/dbinst1).– On Windows systems, include the sqllib subdirectory (for example,

C:\Program Files\IBM\Sqllib).-W database.databaseName="db2_database_name"

(DB2 only) Specifies the alias used on the management server to refer to theDB2 database for the management repository.

-W database.user="username"

Specifies the user ID for the Oracle tablespace or DB2 database to be used forthe management respository.

-W database.password="password"

Specifies the password associated with the user ID specified with the -Wdatabase.user option.

-W arm_panel.protocolHostPortUri="protocol://hostname:portnumber"

Specifies the URL of the Enterprise Transaction Performance server that collectsARM data on behalf of the STI Player application. The URL must be specifiedin the following format:protocol://hostname:portnumber

where:– protocol is one of the following:

- http if the Enterprise Transaction Performance server is not a secure server- https if the Enterprise Transaction Performance server is a secure server


– hostname is the fully qualified name of the host machine for the EnterpriseTransaction Performance server

– (optional) portnumber is a valid port number that the Enterprise TransactionPerformance server can use to communicate with the Internet ManagementServer.

Example: https://etpserver.it.company.com:443-G replaceExistingResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to replace a file that already exists.-G replaceNewerResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to replace an existing file if that file is newer thanthe file being installed.

-G removeExistingResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to remove an existing file.-G removeModifiedResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to remove a file that has been modified sinceinstallation.

-W logSettings.level="trace_level"

Specifies the trace level setting for the traceBWAInstall.log file. This log filelists error, warning, informational, and debug messages that are issued by theinstallation program. See “Trace levels” on page 168 for a complete list of tracelevel settings.

-W logSettings.consoleOut="true | false"

Specifies whether to display messages issued by installation program on theconsole.

Examples1. The following command installs the Internet Management Server on a

Windows system. The command line includes data options that specify whereto install the management server and the user name and password for theOracle or DB2 database. All other data options are included in the option file,setup_TIMS.opt.setup_TIMS_w32 -silent -P tims.installLocation="C:\Tivoli\IMS"-W database.user="tims" -W database.password="timsadmin"-options setup_TIMS.opt

2. The following command installs the Internet Management Server on a Solarissystem. It uses the -is.tempdir option to specify a location for temporaryinstallation files that is different from the default location. All data options areincluded in the option file, setup_TIMS.opt.setup_TIMS_sol.bin -silent -is.tempdir /usr/tmp -options setup_TIMS.opt


Installing an Internet Management EndpointUse the procedure and command described in this section to silently install anInternet Management Endpoint.

Procedure1. Perform the tasks listed under “Before you install an Internet Management

Endpoint” on page 77.2. If you want to use an option file, do one of the following:

v Create the option file. The data options for each endpoint type are listed inthe following sections:– “Data options for Web Services Investigator” on page 127– “Data options for Quality of Service” on page 129– “Data options for Web Services Courier” on page 133

v Modify one of the option files for Internet Management Endpoints providedon the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: WebTransaction Performance Component Software CD. The endpoint types and theircorresponding option file names are listed in Table 20 on page 119.

3. Log on to the host machine for the endpoint:v On Windows systems, log on as Administrator, or a user with Administrator


4. Enter the command specified under Command.5. After the installation is complete, do the following as applicable:

v If you installed a Web Services Investigator endpoint on a Windows system,follow the instructions described under “Post-installation procedures for WebServices Investigator endpoints on Windows systems” on page 92.

v If you installed a secure Quality of Service proxy server, complete theprocedure described under “Post-installation procedure for secure Quality ofService proxy servers” on page 94.

CommandUse the following command to silently install an Internet Management Endpoint:setup_launcher [cmd_line_option...] -silent [dataOption...] [-options optionFile]

where:

setup_launcherSpecifies the setup launcher command for the system on which you areinstalling the endpoint. The launcher commands and target systems are asfollows:

setup_Endpoint_w32 Windowssetup_Endpoint_aix.bin AIXsetup_Endpoint_sol.bin Solarissetup_Endpoint_lin.bin Linux (ix86)setup_Endpoint_390.bin Linux (S/390)





Data options for Web Services InvestigatorFollowing is the complete list of data options for installing the Web ServicesInvestigator endpoint. Each line is a single option. Include a space between optionswhen entering on the command line. Begin each option on a separate line whenentering text in an option file.<-W feature.wsi="true">[-W feature.baseInstallDir="install_dir"]<-W endpoint.name="name"><-W endpoint.description="description"><-W wsiwin32.user="user"><-W wsiwin32.password="password"><-W tims.hostname="hostname"><-W tims.userName="username"><-W tims.password="password"><-W tims.protocol="http | https"><-W tims.portNumber="portnumber">[-W tims.proxyProtocol="noproxy | socks | https"][-W tims.proxyHostName="proxyhostname"][-W tims.proxyPortNumber="proxyportnumber"]<-G replaceExistingResponse="yesToAll | yes | noToAll | no"><-G replaceNewerResponse="yesToAll | yes | noToAll | no"><-G removeExistingResponse="yesToAll | yes | noToAll | no"><-G removeModifiedResponse="yesToAll | yes | noToAll | no">[-W logSettings.level="trace_level"][-W logSettings.consoleOut="true | false"]

where:-W feature.wsi="true"

Specifies that the endpoint being installed is a Web Services Investigatorendpoint.

-W feature.baseInstallDir="install_dir"

Specifies the full path name of the directory where you want to install the WebServices Investigator endpoint.

-W endpoint.name="name"

Specifies a name for the endpoint.-W endpoint.description="description"

Specifies a description for the endpoint.-W wsiwin32.user="user"

(Windows only) Specifies a user on the Web Services Investigator endpointmachine that the Tivoli Internet Management Endpoint Service can use toaccess Microsoft Internet Explorer. This is necessary so that the STI Player onthe endpoint can use the Internet Explorer browser on this machine to replayrecorded Web transactions. Do one of the following:– Specify an existing user, such as Administrator. An existing user account

must meet the conditions described in the Web Services Investigator sectionunder “Before you install an Internet Management Endpoint” on page 77.


– Specify TivoliStiPlayback. The installation program creates theTivoliStiPlayback user under the Administrators group on this machine. Youcan use this account exclusively for running the STI playback function.

-W wsiwin32.password="password"

(Windows only) Specifies the password for the user identified by thewsiwin32.user option. If you specified wsiwin32.user="TivoliStiPlayback", thepassword you specify is set to never expire.

-W tims.hostname="hostname"

Specifies the fully qualified host name or the IP address of the host machine forthe management server to which this endpoint will be registered.

-W tims.username="username"

Specifies the user ID of any user authorized to log on to the managementserver.

-W tims.password="password"

Specifies the password for the user specified by tims.userName.-W tims.protocol="https | http"

Specifies the type of communication used by the management server. Specifyhttps for secure (SSL-enabled) communication. Specify http for non-securecommunication. The type specified here must match the type that was specifiedfor installation of the management server.

-W tims.portnumber="portnumber"

Specifies the port number on the management server used for communicationwith the endpoints.

-W tims.proxyProtocol="noproxy | socks | https"

Specifies whether there is a proxy server for the management server and, if so,what type.

-W tims.proxyHostName="proxyhostname"

Specifies the fully qualified host name for the proxy server (if any).-W tims.proxyPortNumber="proxyportnumber"

Specifies the port number for the proxy server (if any).-G replaceExistingResponse="yesToAll | yes | noToAll | no"





Specifies whether you want to remove a file that has been modified sinceinstallation.

-W logSettings.level="trace_level"

Specifies the trace level setting for the traceBWAInstall.log file. This log filelists error, warning, informational, and debug messages that are issued by theinstallation program. See “Trace levels” on page 168 for a complete list of tracelevel settings.




Examples for Web Services Investigator1. The following command installs a Web Services Investigator endpoint on an

AIX system. All data options, except for the user ID and password to theInternet Management Server, are included in the setup_WSI.opt option file.setup_Endpoint_aix.bin -silent -W tims.userName="admin" -W tims.password="admin"-options setup_WSI.opt

2. The following listing is the complete setup_WSI.opt file specified in Example 1.

NoteComment lines and blank lines in option files can cause the installation oruninstallation to fail. Comments and blank lines are included in theexamples in this chapter for the sake of clarity.

# setup_WSI.opt#-W feature.wsi="true"## Destination directory for the Web Services Investigator endpoint-W feature.baseInstallDir="/usr/Tivoli/Internet"## Endpoint name and description-W endpoint.name="WSI_ENDPOINT"-W endpoint.description="WEB SERVICES INVESTIGATOR"## Information about the Internet Management Server to which this# Web Services Investigator endpoint will be registered-W tims.hostName="wtp.dev.tivoli.com-W tims.protocol="https"-W tims.portNumber="443"## No proxy server will be used to connect to the Internet Management Server#-G replaceExistingResponse="yesToAll"-G replaceNewerResponse="yesToAll"-G removeExistingResponse="yesToAll"-G removeModifiedResponse="yesToAll"# End of File

Data options for Quality of ServiceFollowing is the complete list of data options for installing the Quality of Serviceendpoint. Each line is a single option. Include a space between options whenentering on the command line. Begin each option on a separate line when enteringin an option file.<-W feature.qos="true">[-W feature.baseInstallDir="install_dir"]<-W endpoint.name="name"><-W endpoint.description="description">

# Options for the Quality of Service proxy server<-W qosep.hostName="hostname"<-W qosep.protocol="http | https"><-W qosep.portNumber="portnumber"><-W qosep.user="user"><-W qosep.group="group">[-W qosep.keyFile="full_path_name_of_key_file"][-W qosep.keyFileSth="full_path_name_of_stash_file"]<-W qosep.keyName="keyname">

# Options for the origin server<-W originServer.hostName="hostname"<-W originServer.protocol="http | https">


<-W originServer.portNumber="portnumber"><-W originServer.keyName="keyname">

<-W tims.hostName="hostname"><-W tims.userName="username"><-W tims.password="password"><-W tims.protocol="http | https"><-W tims.portNumber="portnumber">[-W tims.proxyProtocol="noproxy | socks | https"][-W tims.proxyHostName="proxyhostname"][-W tims.proxyPortNumber="proxyportnumber"]<-G replaceExistingResponse="yesToAll | yes | noToAll | no"><-G replaceNewerResponse="yesToAll | yes | noToAll | no"><-G removeExistingResponse="yesToAll | yes | noToAll | no"><-G removeModifiedResponse="yesToAll | yes | noToAll | no">[-W logSettings.level="trace_level"][-W logSettings.consoleOut="true | false"]

where:-W feature.qos="true"

Specifies that the endpoint being installed is a Quality of Service endpoint.-W feature.baseInstallDir="install_dir"

Specifies the full path name of the directory where you want to install theQuality of Service endpoint.



Specifies a description for the endpoint.-W qosep.hostname="hostname"

Specifies the fully qualified host name or the IP address of the host machine forthe Quality of Service proxy server. The Quality of Service proxy server is anIBM HTTP Server, installed with the endpoint, that acts as a proxy for the Webserver (called the origin server) that you want to monitor.

-W qosep.protocol="https | http"

Specifies the type of communication that you want the Quality of Service proxyserver to use for communication with the Internet. Specify https if you wantthe server to use secure (SSL-enabled) communication. Specify http fornon-secure communication.

-W qosep.portnumber="portnumber"

Specifies the port number that the Quality of Service proxy server will use forcommunication with the Internet. A secure server typically uses port 443. Anon-secure server typically uses port 80.

-W qosep.user="user"

(UNIX systems only) Specifies the user name under which the Quality of Serviceproxy server will run.

-W qosep.group="group"

(UNIX systems only) Specifies the group name under which the Quality ofService proxy server will run.

-W qosep.keyFile="full_path_name_of_key_file"

(secure Quality of Service proxy server only) Specifies the full path name of a keydatabase file (.kdb file) that contains a digital certificate, signed by a trustedcertificate authority, that will be used to authenticate the Quality of Serviceproxy server to the Internet. The key database file must have been createdusing the IBM Key Management Utility. Omit this option if the key databasefile does not exist.


-W qosep.keyFileSth="full_path_name_of_stash_file"

(secure Quality of Service proxy server only) Specifies the full path name of thestash file (.sth file) associated with the key database file specified by theqosep.keyFile option. The stash file must have been created using the IBM KeyManagement Utility. It must be located in the same directory as the keydatabase file. Omit this option if you did not specify a key database file.

-W qosep.keyName="keyname"

Specifies the name of the certificate, contained in the key database file specifiedby the qosep.keyFile option, that is used for secure communications betweenthe Quality of Service proxy server and the Internet. Specify null for thekeyname value in either of the following situations:– You are installing a secure Quality of Service proxy server

(qosep.protocol="https") and there is no certificate name available.– You are installing a non-secure Quality of Service proxy server

(qosep.protocol="http").-W originServer.hostname="hostname"

Specifies the fully qualified host name or the IP address of the host machinewhere the origin server is running. The origin server is the Web server to bemonitored by the Quality of Service application.

-W originServer.protocol="https | http"

Specifies the type of communication used between the Quality of Service proxyserver and the origin server. Specify https for secure (SSL-enabled)communication. Specify http for non-secure communication.

-W originServer.portnumber="portnumber"

Specifies the port number on the origin server that the Quality of Service proxyserver will contact.

-W originServer.keyName="keyname"

(secure origin server only) Specifies the name of the digital certificate, containedin the key database file specified by the qosep.keyFile option, that is used forsecure communication between the Quality of Service proxy server and theorigin server. Specify null for the keyname value in either of the followingsituations:– The origin server is a secure server (originServer.protocol="https") and

there is no certificate name available.– The original server is a non-secure server (originServer.protocol="http").


Specifies the fully qualified host name or the IP address of the host machine forthe management server to which this endpoint is registered.













Specifies the port number for the proxy server (if any).-G replaceExistingResponse="yesToAll | yes | noToAll | no"





Specifies whether you want to remove a file that has been modified sinceinstallation.Specifies the trace level setting for the traceBWAInstall.log file. This log filelists error, warning, informational, and debug messages that are issued by theinstallation program. See “Trace levels” on page 168 for a complete list of tracelevel settings.



Examples for Quality of Service1. The following command installs a Quality of Service endpoint on an ix86 Linux

system. All data options are included in the setup_QOS.opt option file.setup_Endpoint_lin.bin -silent -options setup_QOS.opt

2. The following listing shows what a portion of the setup_QOS.opt file specifiedin Example 1 might look like. This listing shows the data options that specifyinformation for the Quality of Service proxy server and the origin server. In thisexample, the proxy and origin servers are not secure servers so there is no keydatabase file.

.

.-W qosep.hostname="qos1.dev.tivoli.com"-W qosep.protocol=http"-W qosep.portnumber="80"-W qosep.user="nobody"-W qosep.group="nobody"-W originServer.hostname="origin1.dev.tivoli.com"-W originServer.protocol="http"-W originServer.portnumber="81"

.

.

3. The following listing shows the same data options as in Example 2, but in thisexample there is secure communication between the Quality of Service proxyserver and the Internet and between the Quality of Service proxy server andthe origin server. Because a key database file is not specified, the installationprogram installs a key database file with a self-signed certificate on the Qualityof Service endpoint machine.


.

.-W qosep.hostname="qos1.dev.tivoli.com"-W qosep.protocol=https"-W qosep.portnumber="443"-W qosep.user="nobody"-W qosep.group="nobody"-W originServer.hostname="origin1.dev.tivoli.com"-W originServer.protocol="https"-W originServer.portnumber="443"

.

.

Data options for Web Services CourierFollowing is the complete list of data options for installing the Web ServicesCourier endpoint. Each line is a single option. Include a space between optionswhen entering on the command line. Begin each option on a separate line whenentering in an option file.<-W feature.wsc=true>[-W feature.baseInstallDir="install_dir"]<-W endpoint.name="name"><-W endpoint.description="description">

# Options to enable the Web Services Courier data warehouse feature# and the Tivoli Enterprise Console event forwarding feature<-W wscOption.dw_enabled="true | false"><-W wscOption.tec_enabled="true | false">

# Option to forward events to the Tivoli Enterprise Console through a# Tivoli environment or directly to a specified Tivoli Enterprise Console server<-W tme.tme_enabled="true | false">

# Include the following option if forwarding events through a Tivoli environment<-W tme.path="path_to_LCF">

# Include the following options if forwarding events to a specified# Tivoli Enterprise Console server<-W tme.tECHostname="hostname"><-W tme.tECPort="portnumber">

<-W database.database_type="Oracle | DB2">

# Options for Oracle<-W database.server="hostname"><-W database.port="portnumber"><-W database.sid="SID_name">

# Options for DB2<-W database.dB2Instance="db2instance"><-W database.db2path="db2path"><-W database.databaseName="db2_database_name">

# Options for both Oracle and DB2<-W database.user="username"><-W database.password="password"><-P database.isSharedDatabase="true | false">

<-W tims.hostname="hostname"><-W tims.userName="username"><-W tims.password="password"><-W tims.protocol="http | https"><-W tims.portNumber="portnumber">[-W tims.proxyProtocol="noproxy | socks | https"][-W tims.proxyHostName="proxyhostname"][-W tims.proxyPortNumber="proxyportnumber"]<-G replaceExistingResponse="yesToAll | yes | noToAll | no">


<-G replaceNewerResponse="yesToAll | yes | noToAll | no"><-G removeExistingResponse="yesToAll | yes | noToAll | no"><-G removeModifiedResponse="yesToAll | yes | noToAll | no">[-W logSettings.level="trace_level"][-W logSettings.consoleOut="true | false"]

where:-W feature.wsc="true"

Specifies that the endpoint being installed is a Web Services Courier endpoint.-W feature.baseInstallDir="install_dir"

Specifies the full path name of the directory where you want to install the WebServices Courier endpoint.



Specifies a description for the endpoint.-W wscOption.dw_enabled="true | false"

Specifies whether or not to enable the Web Services Courier data warehousefeature. Enable this feature if you plan to use Tivoli Decision Support to createhistorical reports of data collected by Web Transaction Performanceapplications.If you specify a value of false (do not enable the data warehouse feature), dothe following:– (required) Set the wscOption.tec_enabled option to true.– Omit all database.xxxx options.

-W wscOption.tec_enabled="true | false"

Specifies whether or not to enable the Tivoli Enterprise Console eventforwarding feature. Enable this feature if you want the Web TransactionPerformance administrator to have the option of forwarding events to the TivoliEnterprise Console.If you specify a value of false (do not enable the Tivoli Enterprise Consoleevent forwarding feature), do the following:– (required) Set the wsiOption.dw_enabled option to true.– Omit the remaining tec.xxxx options.

-W tme.tme_enabled="true | false"

Specifies whether to enable forwarding of events to the Tivoli EnterpriseConsole through a Tivoli environment or directly to a Tivoli Enterprise Consoleserver.– Specify true if you want to enable forwarding of events to the Tivoli

Enterprise Console through a Tivoli environment. If you set the value of thisoption to true, do the following:- Verify that the machine on which you are installing the Web Services

Courier endpoint is already an endpoint of a Tivoli management regionserver.

- Specify the location of the LCF file on this computer by using thetme.path option.

- Omit the tme.tECHostname and tme.tECPort options.– Specify false if you want to enable forwarding of events directly to a

specified Tivoli Enterprise Console server. If you set the value of this optionto false, do the following:- Omit the tme.path option.


- Specify the host name and port of the Tivoli Enterprise Console server byusing the tme.tECHostname and tme.tECPort options.

-W tme.path="path_to_LCF"

Specifies the absolute path to the LCF file (lcf_env.cmd on Windows systems orlcf_env.sh on UNIX systems). Do not include the LCF file name in the path.Omit this option if the tec.tme option is set to false.The LCF file represents the Tivoli management agent software, which is part ofthe configuration needed to enable forwarding of events to the Tivoli EnterpriseConsole through a Tivoli environment.– On Windows systems, the path to the LCF file is typically as follows:

C:\SystemRoot\Tivoli\lcf\1\

where SystemRoot is the drive and directory where Windows is installed (forexample, C:\WINNT or C:\WINNT40).

– On UNIX systems, the path to the LCF file is typically as follows:/etc/Tivoli/lcf/1/

-W tme.tECHostname="hostname"

Specifies the fully qualified name of the host machine for the Tivoli EnterpriseConsole server to which events will be forwarded. Omit this option if thetme.tme_enabled option is set to true.

-W tme.tECPort="portnumber"

Specifies the port number on the Tivoli Enterprise Console server to whichevents will be forwarded. Omit this option if the tme.tme_enabled option is setto true.

-W database.database_type="Oracle | DB2"

Specifies the type of RDBMS to be used for creating the Web Services Courierdata warehouse: Oracle or DB2. Omit this option and all of the followingdatabase.xxxx options if the wscOption.dw_enabled option is set to false.


Specifies the user ID for the Oracle tablespace or DB2 database instance to beused for the data warehouse.



-W database.server="hostname"

(Oracle only) Specifies the fully qualified host name or the IP address of the hostmachine for the Oracle database which contains tablespace for the Web ServicesCourier data warehouse.

-W database.port="portnumber"

(Oracle only) Specifies the port number used by the Oracle listener.-W database.sid="SID_name"

(Oracle only) Specifies the SID name for the Oracle database.-W database.dB2Instance="db2Instance"

(DB2, AIX only) Specifies the name of a user authorized to the DB2 instanceunder which the database for the Web Services Courier data warehouse wascreated. This can be the name of the user under which the DB2 client wasinstalled on the Web Services Courier endpoint machine. (See “Creating thedatabase” on page 42.)

-W database.db2Path="db2Path"


(DB2 only) Specifies the full path to the home directory of the owner of the DB2instance under which the DB2 database for the Web Services Courier datawarehouse was created.– On AIX systems, specify the path name up to, but not including, the sqllib

subdirectory (for example, /usr/dbinst1).– On Windows systems, include the sqllib subdirectory (for example,

C:\Program Files\IBM\Sqllib).-W database.databaseName="db2_database_name"

(DB2 only) Specifies the alias used on the Web Services Courier endpoint torefer to the DB2 database for the data warehouse.


Specifies the user ID for the Oracle tablespace or DB2 database to be used forthe data warehouse.



-P database.isSharedDatabase="true | false"

Specifies whether or not this Web Services Courier endpoint will share anexisting Web Services Courier data warehouse..– Specify false if the database described by the preceding database.xxxx

options does not contain data warehouse tables. The installation programcreates and initializes the data warehouse, a set of database tables to be usedby this Web Services Courier endpoint and possibly shared by other WebServices Courier endpoints yet to be installed.

– Specify true if the database described by the preceding database.xxxxoptions already contains data warehouse tables that support one or morepreviously installed Web Services Courier endpoints.














Specifies the port number for the proxy server (if any).


-G replaceExistingResponse="yesToAll | yes | noToAll | no"








Examples for Web Services Courier1. The following command installs a Web Services Courier endpoint on a

Windows system. All data options are included in the option file,setup_WSC.opt.setup_Endpoint_w32 -silent -options setup_WSC.opt

2. Following is an example of a setup_WSC.opt option file.


# setup_WSC.opt#-W feature.wsc=true## Destination directory for the Web Services Courier endpoint-W feature.baseInstallDir="C:\Program Files\Tivoli\Internet"## Endpoint name and description-W endpoint.name="WSC_ENDPOINT"-W endpoint.description="WEB SERVICES COURIER"#

# Enable forwarding of events to the Tivoli Enterprise Console through# a Tivoli environment.-W wscOption.tec_enabled="true"-W tme.tme_enabled="true"-W tme.path="C:\Program Files\Tivoli\TEC"## Enable the Web Services Courier data warehouse feature-W wscOption.dw_enabled="true"-W database.databasetype="Oracle"-W database.server="shaolin.dev.tivoli.com"-W database.port="1521"-W database.sid="NBN"-W database.user="corp"-W database.password="corp"

# Do not create a new Web Services Courier data warehouse.


# Share an existing data warehouse that supports a previously installed# Web Services Courier endpoint.database.isSharedDatabase="true"

# Information about the Internet Management Server to which this# Web Services Courier endpoint will be registered-W tims.hostName="wtp.dev.tivoli.com"-W tims.protocol="https"-W tims.userName="admin"-W tims.password="admin"-W tims.portNumber="443"## No proxy server will be used to connect to the Internet Management Server

-G replaceExistingResponse="yesToAll"-G replaceNewerResponse="yesToAll"-G removeExistingResponse="yesToAll"-G removeModifiedResponse="yesToAll"# End of File

Installing the STI RecorderUse the procedure and command described in this section to silently install the STIRecorder.

Procedure1. Perform the tasks listed under “Before you install the STI Recorder” on page 97.2. If you want to use an option file, do one of the following:

v Create the option file. See “Data options for the STI Recorder” on page 139for the list of data options.

v Modify the setup_STIR.opt file, provided on the IBM Tivoli Monitoring forTransaction Performance, Version 5.1.0: Web Transaction Performance ComponentSoftware CD.

3. Log on to the Windows machine where you want to install the STI Recorder.Log on as Administrator, or a user with Administrator privileges.

Note: The STI Recorder is supported on Windows sytems only.4. Enter the command specified under Command.

CommandUse the following command to silently install the STI Recorder:setup_sti_recorder [cmd_line_option...] -silent [dataOption...][-options optionFile]

where:





Data options for the STI RecorderFollowing is the complete list of data options for installing the STI Recorder. Eachline is a single option. Include a space between options when entering on thecommand line. Begin each option on a separate line when entering in an optionfile.[-P STIR.installLocation="install_dir"]<-W tims.hostname="hostname"><-W tims.protocol="http | https"><-W tims.portNumber="portnumber"><-G replaceExistingResponse="yesToAll | yes | noToAll | no"><-G replaceNewerResponse="yesToAll | yes | noToAll | no"><-G removeExistingResponse="yesToAll | yes | noToAll | no"><-G removeModifiedResponse="yesToAll | yes | noToAll | no">[-W logSettings.level="trace_level"][-W logSettings.consoleOut="true | false"]

where:-P STIR.installLocation="install_dir"

Specifies the full path name of the directory where the STI Recorder is installed.-W tims.hostname="hostname"


-W tims.protocol="https | http"












Examples for the STI Recorder1. The following command silently installs the STI Recorder. All data options are

included in the option file, setup_STIR.opt.setup_sti_recorder -silent -options setup_STIR.opt


2. The following listing shows the complete setup_STIR.opt file specified inExample 1.


# setup_STIR.opt## Destination directory for the STI Recorder-P STIR.installLocation="C:\Program Files\Tivoli\Internet"## Information about the Internet Management Server to which# the STI Recorder will be registered-W tims.hostName="wtp.dev.tivoli.com"-W tims.protocol="https"-W tims.portNumber="443"#-G replaceExistingResponse="yesToAll"-G replaceNewerResponse="yesToAll"-G removeExistingResponse="yesToAll"-G removeModifiedResponse="yesToAll"

# End of File


Uninstalling Web Transaction Performance components

When a Web Transaction Performance component is installed, the installationprogram creates the following uninstall files and places them in a subdirectory.v uninstall.bin, the uninstall native launcher created when the management

server or an endpoint is installed on a UNIX-based system. (Exception: A nativelauncher is not available for S/390 Linux.)

v uninstall.exe, the uninstall native launcher created when any Web TransactionPerformance component is installed on a Windows system.

v uninstall.opt, the uninstall option file created when any Web TransactionPerformance component is installed on any system. The uninstall data optionsare the same for all components.

v uninstall.jar, the JAR file created when the management server or an endpointis installed on any system. The uninstall native launcher runs the uninstall.jarfile.

The subdirectory in which these files are placed varies according to the WebTransaction Performance component. Table 21 shows the uninstall subdirectory foreach component.

Table 21. Uninstall File Names and Locations

Component Uninstall subdirectory

Internet Management Server inst_dir/ManagementServer/_uninst51

Internet Management Endpoint inst_dir/Endpoint/_uninst

STI Recorder inst_dir/STI-Recorder/_uninst

where inst_dir is the installation directory for the component. The default installationdirectory for any Web Transaction Performance component is as follows:




Note: Table 21 shows the uninstall directories in UNIX format only. For Windowsformat, replace the forward slashes (/) in the directory name with backwardslashes (\).

Procedure1. If you are uninstalling an endpoint, verify that the management server is up

and running. The uninstall process un-registers the endpoint from themanagement server.

2. If you are uninstalling the management server, verify that there are noendpoints currently registered to the management server.

3. If you want to use an option file, do one of the following:v Create the option file. The data options for uninstalling a Web Transaction

Performance component are listed under “Data Options” on page 142.v Modify the uninstall.opt file, located in the uninstall directory. The

uninstall directory varies according to component. See Table 21 for a list ofuninstall directories.


4. Log on to the host machine for the Web Transaction Performance componentthat you want to uninstall:v On Windows systems, log on as Administrator, or a user with Administrator


5. From the root directory, enter one of the commands listed under Command.6. When the uninstall program is finished, complete the appropriate When You

Finish procedure in Chapter 10.v If you are uninstalling an Internet Management Endpoint on Windows,

complete the procedure described under “When You Finish” on page 111v If you are uninstalling the Internet Management Server on Windows,

complete the procedure described under “When You Finish” on page 113v If you are uninstalling an Internet Management Endpoint on UNIX, complete

the procedure described under “When You Finish” on page 114v If you are uninstalling the Internet Management Server on UNIX, complete

the procedure described under “When You Finish” on page 115

CommandUse one of the following commands to silently uninstall a Web TransactionPerformance component:v For Windows:

uninst_dir\uninstall [cmd_line_option...] -silent [dataOption...][-options uninst_dir\optionFile]

v For any UNIX system except S/390 TurboLinux:uninst_dir/uninstall.bin [cmd_line_option...] -silent [dataOption...][-options uninst_dir/optionFile]

v For any UNIX system, including S/390 TurboLinux:java -jar uninst_dir/uninstall.jar [cmd_line_option...] -silent [dataOption...][-options uninst_dir/optionFile]

where:

uninst_dirSpecifies the directory that contains the uninstall files (native launcher, JARand option file). The uninstall directories are listed in Table 21 on page 141.




Data OptionsFollowing is the complete list of data options for uninstalling a Web TransactionPerformance component. Each line is a single option. Include a space betweenoptions when entering on the command line. Begin each option on a separate linewhen entering in an option file.


[-P uninstallWSCdw.active="true | false"]<-G replaceExistingResponse="yesToAll | yes | noToAll | no"><-G replaceNewerResponse="yesToAll | yes | noToAll | no"><-G removeExistingResponse="yesToAll | yes | noToAll | no"><-G removeModifiedResponse="yesToAll | yes | noToAll | no">[-W logSettings.level="trace_level"][-W logSettings.consoleOut="true | false"]

where:-P uninstallWSCdw.active="true | false"

(Web Services Courier endpoint only) Specifies whether or not you want to removethe Web Services Courier data warehouse. Use this option only if you areuninstalling a Web Services Courier endpoint that uses a data warehouse.– Specify true if you want the uninstall program to remove the data

warehouse. This option removes all tables in the data warehouse even if theyare shared by another Web Services Courier endpoint. This is the default.

– Specify false if you want the uninstall program to leave the data warehousetables intact.









Examples1. The following command uninstalls any Internet Management Endpoint from a

Windows system. This example assumes that the endpoint was installed in thedefault installation directory. All data options are included in the option file,uninstall.opt.C:\> \Program Files\Tivoli\Internet\Endpoint\_uninst\uninstall -silent-options \Program Files\Tivoli\Internet\Endpoint\_uninst\uninstall.opt

2. Following is an example of an uninstall.opt option file. You can use thisoption file with the command in the preceding example to uninstall a WebServices Courier endpoint that uses a data warehouse. TheuninstallWSCdw.active option in this example is set to false, causing theuninstall program to leave the data warehouse intact.-P uninstallWSCdw.active="false"-G replaceExistingResponse="yesToAll"-G replaceNewerResponse="yesToAll"-G removeExistingResponse="yesToAll"-G removeModifiedResponse="yesToAll"


Chapter 12. All about certificates

A digital certificate, or certificate, is a digital document obtained from a certificateauthority (CA) that establishes the identity of a user or system component. Acertificate enables you to sign, or encrypt, data. For example, you can install aserver certificate on a Web server to enable Secure Sockets Layer (SSL). Thatcertificate enables the Web server to encrypt, or secure, transactions to clients (suchas Web browsers). A certificate contains the following data, which is encrypted:v The name of the owner and company (if applicable), and the addressv The public key of the ownerv The serial number of the certificatev The validity dates for the certificate (indicating when the certificate will expire)v The public key of the certificate authorityv The digital signature of the certificate authority

A certificate authority is a trusted, third-party organization that issues and signscertificates. When you request a certificate from a CA, the CA authenticates youridentity and the services that you are authorized to use. It also issues and renewscertificates, and revokes certificates belonging to users who are no longerauthorized to use them. A certificate authority signs certificates that it issues withits root certificate. This signifies that, because the CA is a trusted organization, thecertificate that it issued (and its holder) can also be trusted.

This chapter provides an introduction to keys and certificates and how to use theIBM Key Management Utility to manage certificates.

Overview of keys and certificatesKeys are used to enable encryption. Two keys are used: a public key and a privatekey. The keys are contained in a key-pair file on the server. When a client browsermakes a connection to a Web server, the Web server presents a signed digitalcertificate to the client. The certificate contains the server’s public key, ensuring theidentity of the server. When the browser receives this key, it generates a symmetrickey, encrypting it with the server’s public key. The server, which possesses thematching private key, is the only entity that can decode this request. When theserver reads the key, it encrypts the response, using the symmetric key and theserver’s private key. This ensures the integrity of the response while allowing theclient to verify the identity of the server. The HTTP transaction can now take placein this secure channel.

Keys are also used when generating certificates. If you want to obtain a servercertificate, you first generate a key-pair. You then generate a certificate signingrequest, which contains the public key (from the key-pair) and the name of yourorganization. You then send the certificate signing request to the CA from whichyou are requesting the certificate. The CA signs your public key with its privatekey, which it includes along with the signature in the certificate.

The following are the high-level steps that describe how servers and clients usecertificates and keys:1. A client connects to the server, requesting data.

145

2. The server digitally signs its certificate and sends it to the client. The serversigns the certificate using its private key.

3. Using the public key included in the certificate, the client verifies that theowner of the certificate is the same one who signed it.

4. If the client knows the certificate’s CA, it accepts the certificate. If not, the clientinforms its user that the certificate was issued by an unknown CA and givesthe user the choice to accept or refuse the connection.

5. The client compares the information in the certificate to the information it justreceived about the server. If all the information matches, the client accepts thesite as authenticated, or trusted.

These steps outline server authentication. Client authentication is very similar. Youcan obtain a client-side certificate to use for signing content, such as e-mail. Afterthe certificate is installed on the client, the client sends the certificate to the serverin a transaction. Using the client’s public key that is included in the certificate, theserver verifies that the owner of the certificate is the same as the sender. If it is, theclient is authenticated to the server.

Certificates are used for the following reasons:v To verify that the owner is truly the entity identifying itself in a transaction.

Certificates are used to digitally sign a message so that the recipient knows thata message really came from the sender.

v To ensure the integrity of the message sent in the transaction. A certificateencrypts the message so that the intended recipient can decrypt and read themessage contents and attachments. A certificate also guarantees that the contentof the message and the transaction are protected from tampering, impersonation,and eavesdropping while being routed to the recipient.

v To establish a trust relationship between the sender and the recipient. Each partyin the transaction must hold a key-pair file. A key-pair file contains the privateand public keys. Those keys were used in creating the certificate and are used toencrypt and decrypt messages that are signed with the certificate.

Types of certificatesCertificate authorities offer an array of certificates. You can use a certificate for anyof the following purposes:v To secure Web transactions between Web servers and Web browsers. These

transactions are secured through the following measures:– Web server authentication and content confidentiality, by enabling Secure

Socket Layer (SSL) and Transport Layer Security transactions– Browser (client-side) authentication and secure form submissions using a

client-side certificate (the certificates are implemented in the browsers)– Digital signature verification of distributed code, such as signed applets,

ActiveX components, and so onv To secure e-mail, as implemented by QUALCOMM, Eudora, Netscape

Messenger, Microsoft Outlook, and other Simple Mail Transfer Protocol (SMTP)servers.

v To secure online financial settlements and Secure Electronic Transactions (SET).v To secure networks, virtual private networks (VPNs), IP Security Protocol

(IPSEC), IPv6, and products such as Point-to-Point Tunneling Protocol (PPTP),Windows 2000, Network Associates, Data Fellows, and so on.


v To secure custom applications, such as Entrust PKI-based applications, BaltimorePKI-based applications, E-Lock, or any public key infrastructure (PKI) vendorthat offers an API toolkit.

You can purchase different types of certificates based on your needs. The followinglist describes the certificates you can purchase from a CA:

Root certificateIdentifies a certificate authority as an issuer of certificates. These are oftenself-signed and are used to validate other kinds of certificates. A CA mightuse different root certificates for different certificate applications to signifythat different criteria were used to approve different certificates. The termsroot certificate and root authority are often used synonymously.

Server certificateIdentifies a server and includes a digitally signed version of the server’spublic key, Internet host name, the name of the organization that owns theserver, and the public key of the issuing certificate authority. Use a servercertificate to secure a Web server, by enabling SSL. This certificate validatesthe server to the client and establishes an encrypted session with the client.A server certificate is sometimes referred to as a site certificate or an SSLcertificate.

Personal certificateIdentifies a person and includes a digitally signed version of the person’sname, organization, and public key. These certificates come in a variety ofsecurity levels based on the security policy used to obtain them. The levelof trust granted to a certificate varies according to the security policy ofeach secure server.

Software publisher certificateIdentifies a software developer and includes a digitally signed version ofthe developer’s name, organization, and public key within the code. Adeveloper uses this certificate to sign a software application for Internetdistribution.

Content signing certificateIdentifies the owner of the content and includes a digitally signed versionof the owner’s name, organization, and public key in the content. Use thiscertificate to sign content that is distributed, such as channels. Thiscertificate authenticates the owner of the content to the end user whosubscribes to the content.

In addition to the different types of certificates, certificate authorities issue differentlevels of certificates based on how thoroughly they investigate the requestor. Whilenames of security levels can vary among CAs, the purpose and function of levels isthe same. For example, VeriSign’s certificate levels are as follows.

Class 1VeriSign checks to see that the user can receive e-mail at the given addressand that no other certificate has been issued for that e-mail address.

Class 2VeriSign checks a user’s identity by checking personal information againstinformation stored in online databases.

Class 3VeriSign validates the identity of the user who is applying for thecertificate by using background checks and investigative services.

Chapter 12. All about certificates 147

Class 4VeriSign validates the user’s identity though a stringent investigation and,sometimes, a personal interview.

Key files installed with Web Transaction PerformanceWhen you install a secure (SSL-enabled) Internet Management Server or a secureQuality of Service proxy server (installed with the Quality of Service endpoint), theinstallation program stores the key files shown in Table 22 on the host machine.

Table 22.

File nameDescription

Management Server Quality of Service

key.kdb keys.kdb The key database file, also called the key database.This file contains the default root certificatessupported by IBM.

key.sth keys.sth The stash file. This file stores the encryptedpassword for the key database file. Thepassword protects the private key for the keyfile. The server uses the stash file to decrypt theprivate key.

The key database file (key.kdb or keys.kdb) installed with the server contains thefollowing list of trusted certificates:v IBM World Registry™ CAv Integrion CA Root (from IBM World Registry)v VeriSign Class 1 Public Primary CAv VeriSign Class 2 Public Primary CAv VeriSign Class 3 Public Primary CAv VeriSign Class 4 Public Primary CAv VeriSign Test CAv RSA Secure Server CA (from VeriSign)v Thawte Personal Basic CAv Thawte Personal Freemail CAv Thawte Personal Premium CAv Thawte Premium Server CAv Thawte Server CA

IBM Key Management UtilityWhen you install the Internet Management Server or Quality of Service proxyserver, the installation program installs the IBM Key Management Utility, asoftware program with a graphical user interface for managing certificate keys.

This section describes how to use the IBM Key Management Utility to performcommon tasks associated with keys and certificates.

Starting the IBM Key Management UtilityTo start the IBM Key Management Utility, do the following:


v On Windows systems, select Programs → Tivoli → Start Key Management Utilityfrom the Start menu.

v On UNIX-based systems, follow these steps:1. If you are using the IBM Key Management Utility on the Internet

Management Server, change to the following directory:install_dir/ManagementServer/IBMHTTPSERVER/platform/gsk5/bin/

where:– install_dir is the directory where the management server is installed.– platform is one of the following:

- solaris2 if the management server is installed on a Solaris system- aix4-r3 if the management server is installed on an AIX system

2. If you are using the IBM Key Management Utility on the Quality of Serviceendpoint, change to the following directory:install_dir/Endpoint/IBMHTTPSERVER/gsk5/bin/

where install_dir is the directory where the Quality of Service endpoint isinstalled.

3. Enter ./gsk5ikm.

Note: The default installation directory for the management server or Quality ofService endpoint on UNIX-based systems is the following:/usr/Tivoli/Internet (on AIX)/opt/Tivoli/Internet (on Solaris or Linux)

Opening an existing key database fileTo open an existing key database:1. Select Open from the Key Database File menu.2. In the Open dialog box, enter the key database file name and location in the

designated fields.3. Click OK to display the Password Prompt dialog box.4. Enter the password for the key database file in the Password field.5. Click OK. The key database file name appears in the File Name text box.

Specifying a password for a key database fileWhen you create a new key database file, you specify a key database password.This password is important because it protects the private key. The private key isthe only key that can sign documents or decrypt messages encrypted with thepublic key. It is a good practice to change the key database password frequently.

Use the following guidelines when specifying the password:v The password must be from the U.S. English character set.v The password should be at least six characters and contain at least two

nonconsecutive numbers. Make sure the password doesn’t consist of publiclyobtainable information about you, such as the initials and birth date for you,your spouse, or children.

Note: If you specify an expiration date for the password, keep track of when tochange it. If the password expires before you change it, a message is writtento the error log. The server starts, but there is no secure network connectionif the password has expired.


Creating a new key database fileThe server stores one or more key pairs and certificates in a key database file. Youcan create one key database file for all of your key pairs and certificates or you cancreate multiple key database files.

To create a new key database file:1. Select New from the Key Database File menu.2. In the New dialog box, enter the key database file name (for example,

keys.kdb) and location in the designated fields.3. Click OK to display the Password Prompt dialog box.4. Enter a password for the key database file in the Password and Confirm

Password fields.5. To change the default expiration time of 60 days, check the Set expiration time

checkbox, and then enter a number of days in the adjacent field.6. Check the Stash the password to a file checkbox to store the new password in

an encrypted password file called the stash file.The stash file has the same name as the key database file but with a differentfile extension, .sth. It is stored in the same directory as the key database file.

Note: For a secure network connection, you must store the encrypted databasepassword in a stash file.

7. Click OK.

Stashing a password for an existing key database fileTo stash a password for an existing key database file:1. Open the key database file.2. Select Stash Password from the Key Database File menu.3. Click OK.

Changing the password for a key database fileTo change the password for a key database file:1. Open the key database file.2. Select Change Password from the Key Database File menu.3. Enter a password for the key database file in the Password and Confirm

Password fields.4. To change the default expiration time of 60 days, check the Set expiration time

checkbox, and then enter a number of days in the adjacent field.5. Check the Stash the password to a file checkbox to store the new password in

an encrypted password file called the stash file.The stash file has the same name as the key database file but with a differentfile extension, .sth. It is stored in the same directory as the key database file.

Note: For a secure network connection, you must store the encrypted databasepassword in a stash file.

6. Click OK.

Displaying the default key in a key database fileTo display the default key entry:1. Open the key database file.


2. Select Personal Certificates in the Key Database content frame, and then selectthe CA certificate label name.

3. Click View/Edit and view the certificate default key information in the KeyInformation window.

Creating a new key pair and certificate requestTo create a public-private key pair and certificate request:1. Open the key database file that you want to use for creating the key pair and

certificate request.2. Select New Certificate Request from the Create menu.3. Enter information in the following required fields on the New Key and

Certificate Request dialog:

Key Label Enter a description that identifies the key and certificate in thekey database file.

Common NameEnter the host name of the machine for which you arerequesting a new key pair and certificate. For example, enterthe host name of the machine for the Quality of Service proxyserver (installed with the Quality of Service endpoint).

Organization NameEnter the name of your organization

Country Select a country code.4. Enter the name of a file in which to store the certificate request in the field at

the bottom of the dialog. This file contains the public key.5. Click OK.6. Click OK on the Information dialog. You are reminded to send the certificate

file to a certificate authority.

Displaying a list of certificate authoritiesTo display a list of trusted certificate authorities (CAs) in a key database:1. Open the key database file.2. Select Signer Certificates in the Key Database content frame.3. Click either Signer Certificates, Personal Certificates or Certificate Requests

to view the list of CAs in the Key Information window.

Storing a certificateTo store a certificate from a CA who is not a recognized as a trusted CA in the keydatabase:1. Open the key database file.2. Select Signer Certificates in the Key Database content frame.3. Click Add. The Add CA’s Certificate from a File dialog box is displayed.4. Select the certificate file name, or use the Browse option. The certificate file

must be a Base64-encoded ASCII data file.5. Click OK. The Label dialog box is displayed.6. Enter a label name and click OK.


Receiving a CA-signed certificateUse this procedure to receive a certificate that is electronically mailed to you froma certificate authority (CA) who is designated as a trusted CA on your server.

The Certificate Authority might send more than one certificate. In addition to thecertificate for your server, the CA might also send additional Signing certificates orIntermediate CA Certificates. For example, Verisign includes an Intermediate CACertificate when it sends a Global Server ID certificate. Before receiving the servercertificate, you will first need to receive any additional Intermediate CAcertificates. Follow the instructions in “Storing a certificate” on page 151 to receiveIntermediate CA Certificates.

To receive a certificate from a trusted CA:1. Open the key database file.2. Select Personal Certificates in the Key Database content frame.3. Click Receive. The Receive Certificate from a File dialog box is displayed.4. Enter the name of the certificate file that you received from the certificate

authority in the Certificate file name field. This must be a validBase64-encoded file.

5. Click OK to store the certificate in the key database file.

Exporting keysTo export keys to another key database:1. Open the key database file from which you want to export keys.2. Select Personal Certificates in the Key Database content frame.3. Click Export/Import on the label.4. In the Export/Import Key window:

a. Select Export Key.b. Select the target database type.c. Enter the file name or use the Browse option.d. Enter the correct location.

5. Click OK.6. Cllick OK in the Password Prompt dialog box to export the selected key to

another key database.

To export keys to a PKCS12 file:1. Open the key database file from which you want to export keys.2. Select Personal Certificates in the Key Database content frame.3. Click Export/Import on the label.4. In the Export/Import Key window:

a. Select Export Key.b. Select the PKCS12 database file type.c. Enter the file name or use the Browse option.d. Enter the correct location.

5. Click OK.6. Enter the correct password in the Password Prompt dialog box.7. Click OK to export the selected key to a PKCS12 file.


Importing keysTo import keys from another key database:1. Open the key database file to which you want to import keys.2. Select Personal Certificates in the Key Database content frame.3. Click Export/Import on the label.4. In the Export/Import Key window:

a. Select Import Key.b. Select the key database file type.c. Enter the file name or use the Browse option.d. Select the correct location.

5. Click OK.6. Enter the correct password in the Password Prompt dialog box.7. Click OK.8. Select the correct label name from the Select from Key Label list.9. Click OK.

To import keys from a PKCS12 file:1. Open the key database file to which you want to import keys.2. Select Personal Certificates in the Key Database content frame.3. Click Export/Import on the label.4. In the Export/Import Key window:

a. Select Import Key.b. Select the PKCS12 database file type.c. Enter the file name or use the Browse option.d. Select the correct location.

5. Click OK.6. Enter the correct password in the Password Prompt dialog box.7. Click OK.

ReferencesIf you want to find out more about certificates and the public key infrastructure(PKI), refer to the following organizations, standards, and PKI vendors:

Organizationsv American National Standards Institute (ANSI)

www.ansi.orgv Institute of Electronic and Electrical Engineers (IEEE)

www.standards.ieee.orgv Internet Engineering Task Force (IETF)

www.ietf.orgv International Standards Organization (ISO)

www.iso.chv International Telecommunications Union (ITU)

www.itu.org


Standardsv Public Key Cryptography Standards (PKCS), developed by RSA Data Security

http://www.rsasecurity.com/rsalabs/pkcs/v IETF Public Key Infrastructure and Interoperability (PKIX)

http://www.ietf.org/html.charters/pkix-charter.htmlv Secure Sockets Layer (SSL) 3.0, developed by Netscape Communications

http://home.netscape.com/eng/ssl3/v TLS 1.0 (SSL 3.0 in standards form)

http://www.ietf.org/html.charters/tls-charter.htmlv X.509

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-X.509

PKI vendors of commercial CA softwarev Sun One Certificate Server

http://wwws.sun.com/software/products/certificate_srvr/home_certificate.htmlv Microsoft Certificate Server (included in Windows NT Option Pack 4; formerly

included in Microsoft BackOffice)http://www.microsoft.com/ntserver/web/exec/overview/ WebFeat.asp

PKI vendors of enterprise CA softwarev Entrust Technologies

http://www.entrust.com/v Baltimore Technologies

http://www.baltimore.com/v Entegrity Solutions

http://www.entegrity.com/


Appendix A. Installing and uninstalling language packs

This appendix describes the available language packs for Web TransactionPerformance components and provides instructions for installing and uninstallinglanguage packs.

What is a language pack?A language pack is a set of files that, when installed with a Web TransactionPerformance component, enables you to view the GUI or log files in a specificlanguage other than English. For example, when a Spanish language pack isinstalled on the host machine for the Internet Management Server, you can viewthe Tivoli Monitoring for Transaction Performance GUI in Spanish from anybrowser that is set to display in Spanish. Besides the management server, languagepacks are also available for Internet Management Endpoints and the STI Recorder.

Web Transaction Performance provides language packs in the following languages:

Brazilian PortugueseChinese (Traditional)Chinese (Simplified)FrenchGerman

ItalianJapaneseKoreanSpanish

You can install language packs for some or all of the supported languages in asingle installation. The ability to install multiple language packs makes itconvenient to manage Web-based services in an international environment. Forexample, when multiple language packs are installed on the management server,administrators from around the world can view the Web Transaction PerformanceGUI through a browser set to display in any of the supported languages.

Language pack installation programsWeb Transaction Performance provides the following language pack installationprograms. Each installation program enables you to select all supported languagesor just specific languages.

Internet Management Server and Internet Management EndpointsThis language pack installation program provides language packs for theInternet Management Server and Internet Management Endpointsregistered to the management server. When you install language packs onthe management server, they are automatically downloaded and installedon the endpoints.v Language packs on the management server enable users to view the

Web Transaction Performance GUI in any of the installed languages.v Language packs on an endpoint enable users to view log files in any of

the installed languages.In an international environment, the operating system locale of differentendpoint machines can vary. To enable viewing of log files in the

155

language of a particular endpoint machine, you must select the languagepack that matches the operating system locale of the machine.

STI RecorderThe language pack installation program for the STI Recorder provideslanguage packs for the STI Recorder. By installing language packs on theSTI Recorder machine, you enable users to view the STI Recorder GUI inany of the installed languages.

Locations of language pack installation programsThe language pack installation programs are provided on the IBM Tivoli Monitoringfor Transaction Performance, Version 5.1.0: Web Transaction Performance LanguageSupport CD (referred to in this chapter as the Language Support CD). Table 23 liststhe language pack installation programs, the supported platforms, and thelocations and names of the native launcher files.

A native launcher is an .exe or .bin file that starts the installation program for aparticular platform. The directories or folders that contain the native launchers(known as platform directories, listed in the Platform Directory column of the table)are located in the root directory of the Language Support CD.

To run a language pack installation program, use the native launcher contained inthe directory or folder that matches the platform on which the management serveror STI Recorder is installed. Note that when you install language packs from themanagement server, they are automatically installed to endpoints on anysupported platform.

For example, to install language packs from an Internet Management Server that isinstalled on AIX, run the TIMSLP.bin file located in the aix_power directory. Thelanguage packs are automatically installed on endpoints that might exist onsupported Windows, AIX, Solaris, or Linux platforms.

Table 23. Locations and names of native launchers for language pack installation programs

Language packinstallation program

Platform Platform directory Native launcher

Internet ManagementServer and InternetManagementEndpoints

Windows w32-ix86 TIMSLP.exe

AIXSolaris

aix_powersolaris2

TIMSLP.bin

STI Recorder Windows w32-ix86 STIRLP.exe


Language pack installation procedure

Follow the instructions in this section to install one or more language packs on asupported Windows or UNIX-based operating system. While it is possible to installlanguage packs for a Web Transaction Performance component before you installthe component itself, this section assumes that the component is already installed.

Before You Begin1. Verify the installation directory of the Web Transaction Performance component

(Internet Management Server or STI Recorder) on the machine where you planto run the language pack installation program. You must install the languagepacks to the same directory.For example, if are installing language packs for the management server andendpoints, and the management server is installed in the /opt/Tivoli/Internetdirectory, you must install the language packs to the /opt/Tivoli/Internetdirectory. The language packs are automatically installed to the installationdirectories of registered endpoints.

2. Verify that there is sufficient space for temporary files. The language packinstallation programs require a minimum of 64 MB for temporary files.The language pack installation programs place temporary files by default in thefollowing locations:v On Windows systems, the location specified by the TEMP environment

variable settingv On AIX and Linux, the /tmp directoryv On Solaris, the /var/tmp directory

You can change the location for temporary files by using the -is:tempdiroption when you start the installation program, as shown in the Proceduresection.

3. If you are installing language packs for the Internet Management Server andendpoints, stop the management server before starting the installation. See“Stopping and starting the Internet Management Server” on page 163 forinstructions to stop the management server.

4. Change the autoupdate interval for endpoints if you do not want to accept theexisting setting.Language packs are automatically installed to endpoints using an autoupdateprocess. Each endpoint queries the management server once during anautoupdate interval to determine if an update is available. (In this case, theupdate is a bundle of language packs.) If an update is available, it isautomatically downloaded and installed to the endpoint at a randomlyscheduled time during the next autoupdate interval. This means that anindividual endpoint might be updated as many as two autoupdate intervalsbeyond the time you update the management server.The autoupdate process uses the autoupdate interval that is currently set in theendpoint.properties file on the endpoint. To change the autoupdate interval,follow these steps:a. Stop the endpoint service if it is running.b. Open the endpoint.properties file on the endpoint. This file is located in

the following directory:install_dir/Endpoint/configuration

where install_dir is the directory where the endpoint is installed.

Appendix A. Language Packs 157

c. Edit the endpoint.autoupdateInterval entry to change the autoupdateinterval.

d. Restart the endpoint.


Procedure1. Start the installation program:

v For Windows systems:

a. Follow the instructions for UNIX systems if you want to start theinstallation program from the command line. When you start theinstallation program from the command line, you can specify a locationfor temporary files.—OR—

b. Do the following:1) Navigate to the local or network location of the w32-ix86 directory.2) Double-click the native launcher file (TIMSLP.exe or STIRLP.exe).

v For UNIX systems:

Enter the following command from the root directory:filepath/platform_dir/launcher.bin [-is:tempdir temp_dir]

where:filepath is the full directory path to the local or network location of theplatform directory.platform_dir is the platform directory.launcher is the name of the native launcher file.tempdir is the directory where you want the installation program to placetemporary files. This is an optional specification.

Refer to Table 23 on page 156 to determine the platform directory and nativelauncher for the language pack installation program that you want to use.

Examples:

– Enter the following command to start installing language packs on themanagement server and endpoints if the management server is on aSolaris system and you are installing from the Language Support CD. Inthis example, the CD is mounted on the /cdrom directory and you wantthe installation program to place temporary files in the /mytemp) directoryon the management server./cdrom/solaris2/TIMSLP.bin -is:tempdir /mytemp

– Enter the following command to start installing language packs on themanagement server and endpoints if the management server is on anAIX system and you are installing from a network directory namedlanguagepacks. In this example, the installation program placestemporary files in the default location (/tmp)./languagepacks/aix-power/TIMSLP.bin

2. Click Next on the Welcome screen.3. Read the software license agreement. Select the radio button to accept the

terms of the agreement.4. Click Next.


5. Click Next to install the language pack to the directory displayed in theDirectory name field. Use the Browse button to select a different directory.Notes:

v You must install the language pack to the same directory where the InternetManagement Server or STI Recorder is installed. The Directory name fielddisplays the default installation directory for the component.

v On UNIX systems, do not install to a directory with special characters inthe directory name.

6. Click Next.7. On the customization dialog, clear the check boxes for the language packs that

you do not want to install:8. Click Next.

The installation program displays a dialog that shows the location, features,and size of the language packs to be installed.

9. Click Next to start installation of the language packs.10. When the installation is complete, click Finish to exit.

When You Finish1. If you installed language packs for the Internet Management Server and

endpoints, restart the management server. See “Stopping and starting theInternet Management Server” on page 163 for instructions to start themanagement server.

2. Verify the installation by using a browser to log on to the management serveror to access the GUI for the STI Recorder. Browsers are set to display by defaultin the language of the operating system of the machine where the browser isinstalled. To verify the installation of multiple language packs, do the followingin the browser:a. If necessary, add more languages to the language setting of the browser.b. Each time you want to display the GUI in a different language, move that

language to the top of the priority list.3. If you want to view log files in multiple languages on an endpoint machine,

you must reset the locale of the operating system each time you want to switchlanguages.


Uninstalling language packsYou might want to remove language packs when they are no longer needed or aspart of an upgrade. Web Transaction Performance provides an uninstall programthat enables you to remove some or all language packs from the component(Internet Management Server, Internet Management Endpoint, or STI Recorder)where they are installed.

When you install language packs, the installation program creates anuninstall.jar file and places it in the following directory:install_dir/_uninst

where install_dir is the installation directory of the Web Transaction Performancecomponent (Internet Management Server, Internet Management Endpoint, or STIRecorder).

You can use the uninstall.jar file to start the uninstall program. Note that there isno automatic uninstallation for endpoints. You must start the uninstall programfrom each endpoint where you want to remove language packs.


Language pack uninstallation procedure

Follow the instructions in this section to remove one or more language packs fromthe machine where they are installed.

Before You BeginStop the Internet Management Server or Internet Management Endpoint beforeuninstalling language packs for either of these Web Transaction Performancecomponents.v See “Stopping and starting the Internet Management Server” on page 163 for

instructions to stop the management server.v See “Stopping and starting an Internet Management Endpoint” on page 164 for

instructions to stop an Internet Management Endpoint.

ProcedureFollow these steps to remove one or more language packs for a Web TransactionPerformance component (Internet Management Server, Internet ManagementEndpoint, or STI Recorder). If you want to remove language packs for more thanone component on the same machine, repeat the steps for each component.1. Enter the following command from the root directory to start the uninstall

program:java -jar install_dir/_uninst/uninstall.jar

where install_dir is the directory where the Web Transaction Performancecomponent is installed. (See Table 12 on page 52 for a list of default installationdirectories.)

2. Click Next on the Welcome screen.The uninstallation program displays a list of all supported language packs withchecked boxes next to the language packs that are installed on the machine.

3. Click the checked box next to each language pack that you do not want toremove. The uninstall program removes only the language packs that remainchecked.

4. Click Next to start the uninstallation.5. When the uninstallation is complete, click Finish to exit.

When You FinishIf you uninstalled language packs for the Internet Management Server or anInternet Management Endpoint, restart the management server or endpoint.v See “Stopping and starting the Internet Management Server” on page 163 for

instructions to start the Internet Management Server.v See “Stopping and starting an Internet Management Endpoint” on page 164 for

instructions to start an Internet Management Endpoint.


Appendix B. 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 problem determination, maintenance, and emergencyrecovery, 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 Stop to stop the management server.– Click Start 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:

– Select Stop from the pop-up menu to stop the management server.– Select Start from the pop-up menu 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)

163

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 165.

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 Stop to stop the endpoint.– Click Start 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:

– Select Stop from the pop-up menu to stop the endpoint.– Select Start from the pop-up menu to start the endpoint.

v To stop or start an Internet Management Endpoint from the Control Panel onWindows XP:For Windows XP:

1. Select Settings → Control Panel from the Start menu.2. Double-click the Component Services icon.3. Double-click Services (Local).4. Right-click Tivoli Internet Management Endpoint in the list of services.5. Do one of the following:

– Select Stop from the pop-up menu to stop the endpoint.– Select Start from the pop-up menu 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 Stop to stop the Quality of Service proxy server.– Click Start 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:

– Select Stop from the pop-up menu to stop the Quality of Service proxyserver.

– Select Startfrom the pop-up menu to start the Quality of Service proxyserver.

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 B. Stopping and Starting 165

Appendix C. Problem determination

This appendix provides information that is useful for troubleshooting andrecovering from a failed installation, upgrade, or uninstallation of a WebTransaction Performance component.

Error and message logsThe following tables describe the error and message logs used by the installation,upgrade, and uninstall programs. If you need help, contact the IBM CustomerSupport staff and send the log file. (See “Contacting Customer Support” onpage xvi.) Because entries are appended to a log file as the program runs, the lastentry in the file often describes the cause of an error.

Note: All logs are English-only except for the msgTMTPinstall.log file. Themessages in this file are displayed in the same language as the installation,upgrade, or uninstall program.

Table 24. Installation logs

Log file name Description

traceBWAinstall.log Lists error, warning, informational, and debug messages thatare issued by the installation or upgrade program. The tracelevel setting determines which types of messages are logged tothis file. See “Trace levels” on page 168 for a list of settings.

TIMS_install_log.txt Lists messages that result from failures of InstallShieldMultiPlatform during installation or upgrade of the InternetManagement Server.

Endpoint_install.log Lists messages that result from failures of InstallShieldMultiPlatform during installation or upgrade of an InternetManagement Endpoint.

msgTMTPinstall.log Lists error, warning, and informational messages that theinstallation or upgrade program displays to the user. (Most ofthese messages are also listed in the traceBWAinstall.log fileif the default trace level is set for that file.)

The installation logs are located in the base installation directory. The default installationdirectory for any Web Transaction Performance component is as follows:




Table 25. Uninstall logs


traceBWAinstall.log Lists error, warning, informational, and debug messages thatare issued by the uninstall program. The trace level settingdetermines which types of messages are logged to this file. See“Trace levels” on page 168 for a list of settings.

167

Table 25. Uninstall logs (continued)


msgTMTPinstall.log Lists error, warning, and informational messages that theuninstall program displays to the user. (Most of thesemessages are also listed in the traceBWAinstall.log file if thedefault trace level is set for that file.)

The uninstall logs are placed in the following temporary directories:

v On Windows systems, in the location specified by the TEMP environment variable setting.(See “Setting the TEMP environment variable (Windows only)” on page 53 for moreinformation.)

v On UNIX systems, in the /tmp directory

Trace levelsTable 26 describes the trace levels that you can set for the traceBWAinstall.log file.The trace levels are cumulative from the top to the bottom of the table. Forexample, if you set the trace level to INFO, the traceBWAinstall.log file logs fatal,error, and warning messages as well as information messages, but does not log anydebug messages.

The debug settings (DEBUG_MIN, DEBUG_MID, and DEBUG_MAX) are used by developersand support personnel to diagnose software problems. DEBUG_MIN is the defaultsetting for the traceBWAinstall.log file.

To set trace levels, use the command option shown in the left column of the tablewhen starting an installation, upgrade, or uninstallation. For example, thefollowing command starts installation of the management server on an AIX systemand sets the trace level to DEBUG_MAX:/cdrom/setup_TIMS_aix.bin -W logSettings.level=DEBUG_MAX

Table 26. Trace level settings for traceBWAinstall.log

Trace level Description

-W logSettings.level="FATAL" Log fatal messages. A fatal message reports an errorfrom which the program cannot recover. A fatalmessage is the most severe message.

-W logSettings.level="ERROR" Log error messages. An error message reports aserious failure. An error message is less severe thana fatal message.

-W logSettings.level="WARNING" Log warning messages. A warning message reportsthat an abnormal condition has occurred. Thecondition might or might not require the user totake action.

-W logSettings.level="INFO" Log information messages. An information messageindicates a condition that is worth noting but doesnot require the user to take action.

-W logSettings.level="DEBUG_MIN" Log debug messages that provide minimal detail.DEBUG_MIN is appropriate for a software trace that isalways running. It provides some information aboutthe program state with only minimal impact toperformance. This is the default setting.


Table 26. Trace level settings for traceBWAinstall.log (continued)

-W logSettings.level="DEBUG_MID" Log debug messages that provide a medium amountof detail. The DEBUG_MID setting produces a level ofdetail between DEBUG_MIN and DEBUG_MAX.

-W logSettings.level="DEBUG_MAX" Log debug messages that provide the most detailabout program execution. Program performance isusually not an issue when debugging in this mode.

-W logSettings.level="ALL" Enable all message logging.

Command line optionsThis section describes a set of options that are useful for troubleshooting a failureor to prevent problems before they occur. This is the set of options denoted incommands used in this book by the variable [cmd_line_option...]. You can enter zeroor more of these options on the command line when starting an installation,upgrade, or uninstallation.

The command line options are divided into two groups:v –W options can be entered either on the command line or, if you are using silent

mode, in an option file.v –is options can be used only on the command line, not in an option file.

-W optionsThe following list describes the –W options.

-W logSettings="trace_level"

Specifies a trace level setting for the traceBWAinstall.log file. This file logserror, warning, informational, and debug messages issued by the installation,upgrade, or uninstall program. See Table 26 on page 168 for a list of trace levelsettings and their descriptions. The installation and upgrade programs placethis file in the base installation directory. The uninstall program places this filein a temporary directory. See Table 24 on page 167 and Table 25 on page 167 forfurther information about the location of this file.


Specifies whether to display messages issued by installation, upgrade, oruninstall program on the console. If you use this option with a native launcher,it must be used in combination with the -is:javaconsole option.

-is optionsThe -is options have the following format:-is:option_name parameter

where:option_name is the name of the optionparameter is a required parameter, if present. Not all –is options haveparameters.

The following list describes the –is options.

-is:tempdir temp_dir

Appendix C. Problem determination 169

Specifies a directory for storing temporary files. If the directory you specifydoes not exist, or is not a directory, the installation, upgrade, or uninstallprogram writes temporary files to the default temporary directory. No errormessage is issued.

-is:log log_file_name

Specifies the name of a file for logging error messages issued by InstallShieldduring launcher initialization. You can specify a fully qualified or a relativepath name. If you specify only the file name, the program creates the file in thecurrent directory. This option is especially useful for determining problemswhen the installation, upgrade, or uninstall program fails just after starting.

-is:javaconsole

Specifies that error messages are to be displayed to a console window as wellas logged. The displayed error messages are not necessarily the same as theerror messages logged by the -is:log option.

-is:silent

Suppresses the InstallShield Wizard message window that is displayed at thestart of an installation, upgrade, or uninstallation. The -silent option, used forsilent installations or uninstallations, does not suppress this window.

-is:javahome JVM_home_directory

Specifies the home directory of the Java Virtual Machine (JVM). This optionimproves performance, especially in cases where the JVM is not in a defaultlocation. This option is not needed if you are installing on Windows becausethe installation program provides a JVM for Windows installations.

Recovery proceduresA failed installation, upgrade, or uninstallation often leaves files and, on Windowssystems, registry keys that you need to remove before attempting to run theprogram again. This section describes the cleanup procedures. When following thecleanup instructions, you might not find every listed file or registry key on yoursystem. Whether or not a particular file exists on the system depends on the pointat which the failure occurred.

Recovery on WindowsThe procedure for cleaning up a Windows sytem after a failed installation,uninstallation, or upgrade consists of the following main steps:1. Stop services.2. Remove registry keys.3. Remove installation directories and files.4. Reboot the computer.5. If applicable, delete the database tables used for the management repository or

Web Services Courier data warehouse.

Stopping servicesTable 27 on page 171 lists the services you must stop for each Web TransactionPerformance component. For example, if you are recovering from a failedinstallation, uninstallation, or upgrade of the Internet Management Server, youmust stop the TIMS HTTP Server and Tomcat services.


Table 27. Services for Web Transaction Performance components

Component Names of services

Internet Management Server TIMS HTTP ServerTomcat

Quality of Service endpoint Tivoli Internet Management EndpointTivoli Endpoint HTTP Server

Web Services Investigator endpoint Tivoli Internet Management Endpoint

(Windows only)Web Detailer AgentWeb Detailer Proxy

Web Services Courier endpoint Tivoli Internet Management Endpoint

Follow these steps to stop the services:v For Windows NT:

1. Display the list of services:a. Select Settings from the Windows Start menu.b. Select Control Panel.c. Double-click the Services icon.

2. Repeat the following steps for each service to be stopped:a. Select the service from the list of services.b. Click the Stop button.

v For Windows 2000 or Windows XP:1. Display the list of services:

a. Select Control Panel from the Windows Start menu.b. Select Administrative Tools.c. Select Services.

2. Repeat the following steps for each service to be stopped:a. Right-click the service to be stopped.b. Select Stop from the pop-up menu.

Removing registry keysThe Windows Registry Editor displays the hierarchy of registry keys in anavigation pane similar to the one used for Windows Explorer. Each of the registrykeys to be removed is a subkey in a key path whose root isHKEY_LOCAL_MACHINE. Table 28 on page 172 lists the key paths for the WebTransaction Performance components.


Table 28. Registry keys for Web Transaction Performance components

Internet Management ServerHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TIMSHTTPServerHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TomcatHKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Internet Management Server

Quality of Service endpointHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tivoli Internet Management EndpointHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tivoli Endpoint HTTP ServerHKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\TWxMHKEY_LOCAL_MACHINE\SOFTWARE\IBM\GSK5

Web Services Investigator endpointHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tivoli Internet Management EndpointHKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\TWxMHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Web Detailer ProxyHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Web Detailer Agent

Web Services Courier endpointHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tivoli Internet Management EndpointHKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\TWxM

For each key path, you must remove the subkey at the end of the path. Forexample, if you are recovering from a failed installation, uninstallation, or upgradeof the Internet Management Server, you must remove the TIMSHTTPServer,Tomcat, and Internet Management Server subkeys. Do not remove keys above the lastsubkey in each path.

Note that each subkey to be removed corresponds to a service that you stopped(see Table 27 on page 171). The action of removing the key deletes the service.

Follow these steps to remove the registry keys:1. Display the Registry Editor:

a. Select Run... from the Start menu.b. Enter regedit in the Open field on the Run dialog.c. Click OK.

2. Repeat the following steps for each registry key to be removed:a. In the navigation pane on the left side, expand the hierarchy of keys down

to the subkey to be removed.b. Select the subkey.c. Press the Delete key on the keyboard.d. Click Yes in the confirmation pop-up window.

Removing directories and filesYou must remove directories and files left on the system as a result of the failedinstallation, uninstallation, or upgrade. Follow these steps to remove directoriesand files. Before starting this procedure, you might need to reboot if files arelocked.1. Using Windows Explorer, open the last subfolder within the base installation

directory of the component. For example, if the component is installed in thefollowing directory (the default base installation directory), open the Internetfolder.C:\Program Files\Tivoli\Internet


The content pane (right side) displays the folder where the component isinstalled as well as log files.

2. Delete the folder where the component is installed.v For the management server, delete the ManagementServer folder.v For an endpoint, delete the Endpoint folder.

3. Delete the log files associated with the component.v For the management server, delete the following files:

traceBWAinstall.logTIMS_install_log.txt

v For an endpoint, delete the following files:traceBWAinstall.logEndpoint_install.log

Completing the recoveryTo complete the recovery, perform the following tasks:v Reboot the computer on which you performed the preceding cleanup

procedures.v If you are recovering from a failed installation of the Internet Management

Server, remove the database tables that were created for the managementrepository.

v If you are recovering from a failed installation of a Web Services Courierendpoint, remove the database tables in the associated Web Services Courierdata warehouse, unless these tables are currently shared by other Web ServicesCourier endpoints.

Recovery on UNIX: management serverThis section describes the procedure for cleaning up a supported UNIX system(AIX or Solaris) after a failed installation, uninstallation, or upgrade of the InternetManagement Server. The recovery procedure consists of the following main steps:1. Stop the processes for the management server. You can stop processes using

one of the following methods:v Use a script, if available, to stop all processes automatically.

—OR—v Stop the processes manually.

2. Remove installation directories and files.

Stopping processes by using a scriptYou can stop all processes for the management server by using the stop.ms script,if available.

Enter the following command from the root directory to stop all processes for themanagement server:install_dir/ManagementServer/TIMS/bin/stopms.sh

where install_dir is the installation directory of the management server. The defaultinstallation directory is opt/Tivoli/Internet.

Stopping processes manuallyIf a script is not available, or if it fails, you must stop the processes manually. Youmust stop the following processes for the management server:v The management server processv The IBM HTTP Server processes


Follow these steps to stop processes manually for the management server:1. Enter the following command from any directory:

ps -ef

The system displays a list of processes similar to the list shown in Figure 24.

2. Search for the process ID (PID) of the management server process. This processID is listed in the PID column when the UID column displays root and the CMDcolumn displays a line that includes the following information:jdk_install_dir . . . . tomcat.home=install_dir

where:jdk_install_dir is the directory where the JDK is installedinstall_dir is the base installation directory of the management server (forexample, opt/Tivoli/Internet).

For the example shown in Figure 24, the process ID (PID) of the managementserver process is 7730, displayed in the PID column on the first line listed

3. Enter the following command to stop the management server process:kill PID

where PID is the process ID of the management server process.4. Search for the process ID (PID) of the parent IBM HTTP Server process. This

process ID is listed in the PID column when the UID column displays root andthe CMD column displays the following:install_dir/ManagementServer/IBMHTTPSERVER/platform/bin/httpd

where:platform is one of the following values, representing the operating systemon which the management server is installed:aixsolaris2

install_dir is the base installation directory of the management server (forexample, opt/Tivoli/Internet)

For the example shown in Figure 24, the process ID (PID) of the parent IBMHTTP Server process is 8795, displayed in the PID column on the last line

UID PID PPID C STIME TTY TIME CMD..

root 7730 1 1 13:01:29 - 4:43 /usr/java131/bin/java -mx192m -Dfile.encoding=UTF-8 -Dtomcat.home..

nobody 8819 8795 0 13:55:52 ? 0:02 /opt/Tivoli/Internet/ManagementServer/IBMHTTPSERVER/solaris2/bin/nobody 8832 8795 0 15:48:48 ? 0:01 /opt/Tivoli/Internet/ManagementServer/IBMHTTPSERVER/solaris2/bin/nobody 8831 8795 0 15:41:00 ? 0:01 /opt/Tivoli/Internet/ManagementServer/IBMHTTPSERVER/solaris2/bin/

.

.root 8795 1 0 13:52:29 ? 0:02 /opt/Tivoli/Internet/ManagementServer/IBMHTTPSERVER/solaris2/bin/

.

.

Figure 24. Processes for the Internet Management Server (Solaris)


listed. Note that this process ID is also listed several times in the PPID (parentprocess ID) column, indicating that is it the parent of other IBM HTTP Serverprocesses.

5. Enter the following command to stop the parent IBM HTTP Server process andits child processes.kill PPID

where PPID is the process ID of the parent IBM HTTP Server process.

While this command is intended to stop all IBM HTTP Server processes, theremight be additional, orphaned processes that are not children of this processID.

6. Repeat the following command for each orphaned IBM HTTP Server process, ifany.kill PID

where PID is the process ID of the orphaned process. This process ID is listedin the PID column when the CMD column displays the string shown in Step 2 onpage 174.

Removing directories and filesYou must remove directories and files left on the system as a result of the failedinstallation, uninstallation, or upgrade. Follow these steps to remove directoriesand files for the Internet Management Server.1. Enter the following command to remove the directory tree where the

management server is installed:rm -rf install_dir/ManagementServer

where install_dir is the installation directory for the management server.2. Enter the following commands to remove log files:

rm -rf install_dir/*.logrm -rf install_dir/*.txt

where install_dir is the installation directory for the management server.3. Remove the reboot files and links to the reboot files that the installation,

upgrade, or uninstall program placed on the system. Table 29 lists the rebootfiles and links on each supported operating system. Use the followingcommand for each reboot file and link to be removed:rm filepath

where filepath is the full directory path of the reboot file or link. See theexample at the bottom of the table.

Table 29. Locations of reboot files and links to reboot files for the Internet ManagementServer

System Reboot files Links

AIX /etc/rc.d/TivoliIms.rc /etc/rc.d/rc2.d/S99TivoliIms/etc/rc.d/rc2.d/K99TivoliIms

Solaris /etc/init.d/TivoliIms.rc /etc/rc2.d/S99TivoliIms/etc/rc2.d/K99TivoliIms


Table 29. Locations of reboot files and links to reboot files for the Internet ManagementServer (continued)

Example: Enter the following commands to remove reboot files and links for amanagement server installed on Solaris:

rm /etc/rc.d/TivoliIms.rcrm /etc/rc.d/rc2.d/S99TivoliImsrm /etc/rc.d/rc2.d/K99TivoliIms

4. (AIX only) Remove all instances of the following entry in the /etc/inittab file:startms . . . . install_dir/TIMS/bin/start/tms.sh

where install_dir is the base installation directory of the management server.The default installation directory on AIX is /usr/Tivoli/Internet.

5. Enter the following commands to remove inventory files that were placed onthe system by the installation, upgrade, or uninstall program:rm -rf /var/sadm/pkg/IS*rm -rf /var/sadm/pkg/TIMSmsvr*

6. (optional) Enter the following commands to remove InstallShield MultiPlatformfiles left on the system:rm /Undefname_Undefpurpose.*rm -rf /var/tmp/is*

Recovery on UNIX: endpointsThis section describes the procedure for cleaning up a supported UNIX system(AIX, Solaris, or Linux) after a failed installation, uninstallation, or upgrade of anInternet Management Endpoint. The recovery procedure consists of the followingmain steps:1. Stop the processes for the endpoint. You can stop processes using one of the

following methods:v Use a script, if available, to stop all processes automatically.

—OR—v Stop the processes manually.

2. Remove installation directories and files.

Stopping processes by using a scriptYou can stop all processes for an endpoint by using the scripts shown in Table 30,if available.

Table 30. Scripts for stopping Internet Management Endpoint processes

Component Script

Quality of Service endpoint stopep.shstopserver.sh

Web Services Investigator or WebServices Courier endpoint

stopep.sh

Enter the following command or commands from the root directory to stop allprocesses for the endpoint. In each command, install_dir is the installation directoryof the endpoint.v For a Quality of Service endpoint:


install_dir/Endpoint/bin/stopep.shinstall_dir/Endpoint/bin/stopserver.sh

v For a Web Services Investigator or Web Services Courier endpoint:install_dir/Endpoint/bin/stopep.sh

Stopping processes manuallyIf a script is not available, or if it fails, you must stop the processes manually. Youmust stop the following processes for an Internet Management Endpoint:v The endpoint processv The IBM HTTP Server processes (Quality of Service endpoint only)

Follow these steps to stop processes manually for an endpoint:1. Enter the following command from any directory:

ps -ef

The system displays a list of processes similar to the list shown in Figure 25.

2. Search for the process ID (PID) of the endpoint process. This process ID islisted in the PID column when the UID column displays root and the CMDcolumn displays a line that includes the following information:jre_install_dir . . . . xs.user.dir=install_dir

where:jre_install_dir is the directory where the JRE is installedinstall_dir is the base installation directory of the endpoint (for example,opt/Tivoli/Internet).

For the example shown in Figure 24 on page 174, the process ID (PID) of theendpoint process is 19138, displayed in the PID column on the first line listed.

3. Enter the following command to stop the endpoint process:kill PID

where PID is the process ID of the endpoint process.4. Complete the following steps for Quality of Service endpoints only.

a. Search for the process ID (PID) of the parent IBM HTTP Server process.This process ID is listed in the PID column when the UID column displaysroot and the CMD column displays the following:

UID PID PPID C STIME TTY TIME CMD..

root 19138 1 1 13:07:50 pts/3 0:18 /usr/java131/jre/bin/../bin/sparc/native_threads/java..

nobody 27100 35134 0 14:15:50 - 0:00 /opt/Tivoli/Internet/Endpoint/IBMHTTPSERVER/bin/httpdnobody 27616 35134 0 14:15:50 - 0:00 /opt/Tivoli/Internet/Endpoint/IBMHTTPSERVER/bin/httpdnobody 27874 35134 0 14:15:50 - 0:00 /opt/Tivoli/Internet/Endpoint/IBMHTTPSERVER/bin/httpd

.

.root 35134 1 0 14:15:33 - 0:01 /opt/Tivoli/Internet/Endpoint/IBMHTTPSERVER/bin/httpd

.

.

Figure 25. Processes for a Quality of Service endpoint


install_dir/Endpoint/IBMHTTPSERVER/bin/httpd

where install_dir is the base installation directory of the endpoint (forexample, opt/Tivoli/Internet).

For the example shown in Figure 25 on page 177, the process ID (PID) of theparent IBM HTTP Server process is 35134, displayed in the PID column onthe last line listed. Note that this process ID is also listed several times inthe PPID (parent process ID) column, indicating that is it the parent processof other IBM HTTP Server processes.

b. Enter the following command to stop the parent IBM HTTP Server processand its child processes.kill PPID

where PPID is the process ID of the parent IBM HTTP Server process.

While this command is intended to stop all IBM HTTP Server processes,there might be additional, orphaned processes that are not children of thisprocess ID.

c. Repeat the following command for each orphaned IBM HTTP Serverprocess, if any.kill PID

where PID is the process ID of the orphaned process. This process ID islisted in the PID column when the CMD column displays the string shown inStep 2 on page 177.

Removing directories and filesYou must remove directories and files left on the system as a result of the failedinstallation, uninstallation, or upgrade. Follow these steps to remove directoriesand files for an Internet Management Endpoint.1. Enter the following command to remove the directory tree where the endpoint

is installed:rm -rf install_dir/Endpoint

where install_dir is the installation directory for the management server.2. Enter the following commands to remove log files:

rm -rf install_dir/*.logrm -rf install_dir/*.txt

where install_dir is the installation directory for the management server.3. Remove the reboot files and links to the reboot files that the installation,

upgrade, or uninstall program placed on the system. Table 31 on page 179 liststhe reboot files and links on each supported operating system. Use thefollowing command for each reboot file and link to be removed:rm filepath

where filepath is the full directory path of the reboot file or link. See theexample at the bottom of the table.


Table 31. Locations of reboot files and links to reboot files for Internet ManagementEndpoints

System Reboot filesa Linksa

AIX /etc/rc.d/TIME.rc/etc/rc.d/TIMEqhttp.rc

/etc/rc.d/rc2.d/S99TIME/etc/rc.d/rc2.d/K99TIME/etc/rc.d/rc2.d/S99TIMEqhttp/etc/rc.d/rc2.d/K99TIMEqhttp

Solaris

Red HatLinux

/etc/init.d/TIME.rc/etc/init.d/TIMEqhttp.rc

/etc/rc2.d/S99TIME/etc/rc2.d/K99TIME/etc/rc2.d/S99TIMEqhttp/etc/rc2.d/K99TIMEqhttp

SuSE Linuxb/etc/init.d/TIME.rc/etc/init.d/TIMEqhttp.rc

/etc/init.d/rc2.d/S99TIME/etc/init.d/rc2.d/K99TIME/etc/init.d/rc2.d/S99TIMEqhttp/etc/init.d/rc2.d/K99TIMEqhttp

TurboLinuxb/etc/init.d/TIME.rc/etc/init.d/TIMEqhttp.rc

/etc/rc.d/rc2.d/S99TIME/etc/rc.d/rc2.d/K99TIME/etc/rc.d/rc2.d/S99TIMEqhttp/etc/rc.d/rc2.d/K99TIMEqhttp

Notes:

a. File or directory names that include the string qhttp apply to Quality of Serviceendpoints only.

b. SuSELinux and TurboLinux are not supported on Web Services Courier endpoints.

Example: Enter the following commands to remove reboot files and links for a WebServices Investigator or Web Services Courier endpoint installed on AIX:

rm /etc/rc.d/TIME.rcrm /etc/rc.d/rc2.d/S99TIMErm /etc/rc.d/rc2.d/K99TIME

4. Enter the following commands to remove inventory files placed on the systemby the installation, uninstallation, or upgrade program:rm -rf /var/sadm/pkg/IS*rm -rf /var/sadm/pkg/TIMSmsvr*

5. (optional) Enter the following commands to remove InstallShield MultiPlatformfiles left on the system:rm /Undefname_Undefpurpose.*rm -rf /var/tmp/is*


Appendix D. Messages

This appendix describes recovery actions you can take in response to the errormessages displayed by the installation, upgrade, or uninstall programs. Messagesare displayed either on a dialog or in a separate popup window. Each message ispreceded by a message identifier. The message identifiers are arranged innumerical order in this appendix.

The message identifiers conform to the Tivoli message standard. Each messageidentifier takes the form XXXYY####Z, where:

XXX Identifies the product. The product identifier used for Web TransactionPerformance installation messages is BWM.

YY Identifies an application within the product. The application identifier usedfor Web Transaction Performance installation, upgrade, and unintallmessages is IS.

#### Specifies the error message number.

Z Specifies a severity code for the message. The severity code is one of thefollowing:

I (informational)Specifies an informational message. An informational messageprovides feedback about normal events.

W (warning)Specifies a warning message. A warning message indicates thatpotentially undesirable conditions exist.

E (error)Specifies an error message. An error message indicates problemsthat require intervention or correction before the program canproceed. In some cases, you might need to leave the program andcorrect the condition before restarting.

Message Descriptions

BWMIS0103E Unable to connect to the database:

Explanation: The installation program cannot connect to the database that you specified on the DatabaseConfiguration dialog. This error occurs if you specified incorrect information about the database, or if the databasebecame disconnected or shut down.

Operator Response:

v Verify that all the information that you entered on the Database Configuration dialog is correct.

v Consult the traceBWAinstall.log file for more information about the cause of the failure. This file is located in thebase installation directory. This is the directory that you specified on the Destination Directory dialog or, in thecase of a silent installation, with the tims.InstallLocation or feature.baseInstallDir option. The defaultinstallation directory is one of the following:

– For Windows, C:\Program Files\Tivoli\Internet

– For AIX, /usr/Tivoli/Internet

– For S/390 TurboLinx, /Tivoli/Internet

– For other supported UNIX systems, /opt/Tivoli/Internet

181

BWMIS0105E You must enter a fully qualified domain name (such as it.yourcompany.com)

Explanation: This error occurs when you enter a domain name with no delimiter characters.

Operator Response: In the Domain Name field, enter the fully qualified name of the domain in which the hostmachine for the Internet Management Server (specified in the Host Name field) resides. For example, if you enterservername.it.yourcompany.com in the Host Name field, you must enter it.yourcompany.com in the Domain Namefield.

BWMIS0107E You must enter a fully qualified host name (such as servername.it.yourcompany.com)

Explanation: This error occurs when you enter a host name with no delimiter characters.

Operator Response: Enter a fully qualified host name in the Host Name field. For example, enterservername.it.yourcompany.com, instead of only servername.

BWMIS0109E Cannot access the lcf_env file. The directory name is incorrect or read permission is denied.

Explanation: The lcf_env file (lcf_env.cmd on Windows systems or lcf_env.sh on UNIX systems) is part of theTivoli management agent software. A Tivoli management agent must be present on the Web Services Courierendpoint machine if you are forwarding Web Transaction Performance events to a Tivoli Enterprise Console serverthrough a Tivoli management region server. This error occurs if the Tivoli management agent is not installed, if youentered an incorrect path name to the lcf_env file, if the file is hidden, or if you do not have read permission to thefile.

Operator Response:

v If a Tivoli management agent is not installed on this machine, do the following:

1. Install the Tivoli management agent. The Tivoli management agent must use Tivoli Management Framework,Version 3.7.1 (internationalized) or higher.

2. Verify that the Adapter Configuration Facility (part of the Tivoli Enterprise Console product) is installed on theTivoli management gateway for this Tivoli management agent.

3. Verify that the Adapter Configuration Facility is also installed on the Tivoli management region server.

v Enter the absolute path to the lcf_env file, not including the file name, in the lcf_env FilePath field. If there aremultiple Tivoli management agents installed on the endpoint, specify the lcf_env file that connects to the TivoliEnterprise Console server to which you want to forward Web Transaction Performance events.

– On Windows systems, a typical location for the lcf_env.cmd file is SystemRoot\Tivoli\lcf\1\, where SystemRootis the drive and directory where Windows is installed (for example, C:\WINNT or C:\WINNT40).

– On UNIX systems, a typical location for the lcf_env.sh file is /etc/Tivoli/lcf/1/.

v On Windows systems, verify that the Administrator, or a user with administrator privileges, has read permission tothe lcf_env.cmd file and that it is not a hidden file.

v On UNIX systems, verify that the root user has read permission to the lcf_env.sh file.

BWMIS0111E The Java version on this computer is not supported. You must exit the installation.

Explanation: A supported version of the Java Development Kit (JDK) or Java Runtime Environment (JRE) isprerequisite software for the Internet Management Server or an Internet Management Endpoint on UNIX systems.

Operator Response: Exit the installation program and install or upgrade to the required Java version.

v The following are minimum and preferred versions if you are installing on a Solaris system. This software isavailable from Sun Microsystems, Inc.

– For the management server, install Sun JDK 1.3.1 or higher. Version 1.3.1_04 or higher is preferred.

– For an endpoint, install Sun JRE (or JDK) 1.3.1 or higher. Version 1.3.1_04 or higher is preferred.

v For AIX or Linux installations, use the Java software provided on the IBM Tivoli Monitoring for TransactionPerformance, Version 5.1.0: Web Transaction Performance Component Software CD:

– For the management server, install the IBM Developer Kit for the Java Platform, Standard Edition, Version 1.3.1,SR 2.

– For an endpoint, install the IBM Runtime Environment for the Java Platform, Version 1.3.1, SR 2.

BWMIS0105E • BWMIS0111E


BWMIS0115E Internet Management Server installation error. The operating system on this computer is notsupported. You must exit the installation.

Explanation: This error occurs when you attempt to install the Internet Management Server on an unsupportedoperating system.

Operator Response: Exit the installation. Install the management server on one of the following operating systems.Web Transaction Performance supports both 32-bit and 64-bit architectures on UNIX-based platforms unlessotherwise noted.

v Windows NT 4.0 Server, Service Pack 6 or higher

v Windows 2000 Server, Service Pack 2 or higher

v Windows 2000 Advanced Server, Service Pack 2 or higher

v Solaris 2.7 or 2.8 (Sun OS 5.7 or 5.8)

v AIX 4.3.3 (32-bit only)

v AIX 5.1

BWMIS0119E Both a name and description are required.

Explanation: This error occurs if you do not enter text in the Endpoint Name field, the Endpoint Description field,or both.

Operator Response: Enter a name for the endpoint in the Endpoint Name field and a description in the EndpointDescription field. Do not enter more than 255 characters in each field.

BWMIS0121E An Internet Management Server is already installed on this computer or there are files remainingfrom a previous installation or uninstallation. Click Next to upgrade this installation. If youupgrade, verify that all operating systems and databases meet current requirements. If you do nothave an Internet Management Server installed, click Cancel to exit. Check for and remove thefollowing files:

Explanation: The installation program has detected files indicating the presence of an earlier version of the InternetManagement Server that can be automatically upgraded. The files are listed in the message. However, the files mightremain from a previous installation or uninstallation that failed. In that case, a complete version of the InternetManagement Server does not exist on this computer and therefore the installation cannot be upgraded.

Operator Response:

v If there are files remaining from a failed installation or uninstallation of the management server, click Cancel toexit the installation. Remove all remaining files before attempting to reinstall. Follow the instructions inAppendix C for recovering from a failed installation or uninstallation.

v If a fully installed Internet Management Server exists on this computer and you want to upgrade this installation,click Next to proceed with the upgrade.

BWMIS0123E The user is not defined on this computer.

Explanation: The installation program does not recognize the name that you entered in the User field. OnUNIX-based systems, the Internet Management Server or the Quality of Service proxy server must run under existinguser and group names on this computer.

Operator Response: Do one of the following:

v Enter a valid name of an existing user in the User field. The user name must not contain spaces.

v Create a new user for the product component (Internet Management Server or Quality of Service proxy server).Add the new user to an existing group or create both a new user and a new group. The user and group namesmust not contain spaces.

Note:

v You do not need to exit the installation program to create a user or group. When you are finished, enter the newuser name in the User field.

v To work with users and groups, you can use the admintool on Solaris, smit on AIX, or linuxconf on Linux.


Appendix D. Messages 183

BWMIS0125E The group is not defined on this computer.

Explanation: The installation program does not recognize the name that you entered in the Group field. OnUNIX-based systems, the Internet Management Server or the Quality of Service proxy server must run under existinguser and group names on this computer.


v Enter a valid name of an existing group in the Group field. The group name must not contain spaces.

v Create a new group (and optionally, a new user) for the product component (Internet Management Server orQuality of Service proxy server). The user and group names must not contain spaces.

Note:

v The group must be associated with the user name that you enter in the User field.

v You do not need to exit the installation program to create a user or group. When you are finished, enter the newname in the User or Group field.


BWMIS0131E The user is not root. This installation can only be run as the root user.

Explanation: This message is displayed if you did not log on as the root user before starting the installationprogram.

Operator Response: Click Cancel to exit the installation program. Log on as the root user and restart theinstallation.

BWMIS0133E The port number must be an integer value.

Explanation: This message is displayed when you enter a non-numeric character in the Port Number field.

Operator Response: Enter a numeric value in the Port Number field, for example, 80.

BWMIS0138E The host name must not contain spaces.

Explanation: The name you entered in the Host Name field contains spaces, as in the following example:

servername.it.your company.com

Operator Response: Enter a valid host name with no spaces in the Host Name field.

BWMIS0139E The domain name must not contain spaces.

Explanation: The name you entered in the Domain Name field contains spaces, as in the following example:

it.your company.com

Operator Response: Enter a valid domain name with no spaces in the Domain Name field.

BWMIS0140E The user name must not contain spaces.

Explanation: On UNIX-based systems, the Internet Management Server or the Quality of Service proxy server mustrun under existing user and group names on this computer. The user and group names must not contain spaces. Thismessage is displayed if the name you entered in the User field contains spaces, for example, Internet ManagementServer.


v Enter a valid name in the User field with no spaces.

v Modify an existing user name so that it does not contain spaces.


Note:





BWMIS0141E The group name must not contain spaces.

Explanation: On UNIX-based systems, the Internet Management Server or the Quality of Service proxy server mustrun under existing user and group names on this computer. The user and group names must not contain spaces. Thismessage is displayed if the name you entered in the Group field contains spaces, for example, Web TransactionPerformance.


v Enter a valid name in the Group field with no spaces.

v Modify an existing group name so that it does not contain spaces.

v Create a new group (and optionally, a new user) for the product component (Internet Management Server orQuality of Service proxy server). The user and group names must not contain spaces.

Note:

v The group must be associated with the user name that you enter in the User field.

v You do not need to exit the installation program to create a user or group. When you are finished, enter the newname in the User or Group field.


BWMIS0146E Cannot install the endpoint. An endpoint is already installed on this computer or there are files orregistry keys remaining from a previous installation or uninstallation. If you do not have anendpoint installed, check for and remove the following files or registry keys:

Explanation: The installation program does not allow you to install an Internet Management Endpoint on acomputer that has any version of an Internet Management Endpoint already installed. This message is displayed if anendpoint is installed. It might also be displayed if there are files or registry keys remaining from a failed installationor uninstallation of an endpoint. The files or registry keys are listed in the message.

Operator Response:

v Click Cancel to exit the installation.

v If there are files or registry keys remaining on the computer from a failed installation or uninstallation, removethem before restarting the installation. Follow the instructions in Appendix C for recovering from a failedinstallation or uninstallation.

v If a fully installed endpoint exists on this computer from a previous version of the product, uninstall it beforeinstalling the current version. For uninstalling instructions, refer to the installation guide for the version that youare uninstalling.

BWMIS0148E You must have Administrator privileges to install this software.

Explanation: No additional information is available for this message.

BWMIS0152E An error occurred while writing to the database. See the traceBWAinstall.log file in the baseinstallation directory.

Explanation: The installation program cannot initialize the database tables for the management repository or WebServices Courier data warehouse. This error occurs if there is insufficient tablespace or if the database becomesdisconnected or shut down.

Operator Response: Consult the traceBWAinstall.log file for the error message returned by the database. This fileis located in the base installation directory. This is the directory that you specified on the Destination Directory dialogor, in the case of a silent installation, with the tims.InstallLocation or feature.baseInstallDir option. The defaultinstallation directory is one of the following:

v For Windows, C:\Program Files\Tivoli\Internet

v For AIX, /usr/Tivoli/Internet



v For S/390 TurboLinx, /Tivoli/Internet

v For other supported UNIX systems, /opt/Tivoli/Internet

BWMIS0153E Cannot find the specified host.

Explanation: The installation program cannot find a computer with the host name that you entered in the HostName field.

Operator Response: Check the spelling of the host name or verify the correct name of the machine. Enter the correctname in the Host Name field.

BWMIS0154E The port is busy.

Explanation: An application is currently using the port that you specified in the Port Number field.

Operator Response: Stop the application that is currently using the port you specified, or specify a different port.

BWMIS0155E The local host IP address does not match the host name.

Explanation: You specified a host name that does not correspond to the IP address on this computer. You must belogged on to the computer to which you are installing the Internet Management Server or Quality of Service proxyserver and you must specify the correct host name of this machine.

Operator Response: Verify the correct name of the machine. Enter this name in the Host Name (fully qualified)field.

BWMIS0156E The user name cannot be root.

Explanation: You entered root in the User field. The Internet Management Server or Quality of Service proxy servercannot run as the root user. Installing the server under root creates a security risk.


v Enter the name of an existing user on this computer, other than root, under which the product component (InternetManagement Server or Quality of Service proxy server) can run. The user name must not contain spaces.


Note:



BWMIS0157E The host name cannot contain a protocol. Remove the protocol (http:// or https://) from the HostName field.

Explanation: This message is displayed when you enter a URL with http:// or https:// in the Host Name field, asin the following example:

https://imsserver.it.yourcompany.com

Operator Response: Enter a host name without the http:// or https:// protocol. For example, enterimsserver.it.yourcompany.com.

BWMIS0158E An earlier version of the Internet Management Server is already installed on this computer. Theversion that is installed cannot be automatically upgraded. The installation cannot proceed. ClickCancel to exit.

Explanation: The installation program has detected files or registry keys indicating the presence of an earlier versionof the Internet Management Server that cannot be automatically upgraded. The files or registry keys might remainfrom a previous installation or uninstallation that failed.



Operator Response:


v If there are files or registry keys remaining from a failed installation or uninstallation of the management server,remove them before restarting the installation. Follow the instructions in Appendix C for recovering from a failedinstallation or uninstallation.

v If a fully installed Internet Management Server exists on this computer, uninstall it before installing the currentversion. Uninstall all endpoints before uninstalling the server. For uninstalling instructions, refer to the installationguide for the version that you are uninstalling.

BWMIS0159E This version of the Internet Management Server is already installed on this computer. Theinstallation cannot proceed. Click Cancel to exit.

Explanation: The installation program has detected files or registry keys indicating that the current version of theInternet Management Server is already installed on this computer. The files or registry keys might remain from aprevious installation or uninstallation that failed.

Operator Response:



BWMIS0160E A more recent version of the Internet Management Server is already installed on this computer.The installation cannot proceed. Click Cancel to exit.

Explanation: The installation program has detected files or registry keys indicating that a newer version of theInternet Management Server is already installed on this computer. The files or registry keys might remain from aprevious installation or uninstallation that failed.

Operator Response:



v If a fully installed Internet Management Server exists on this computer, and you want to install an older version,first uninstall the existing server. Uninstall all endpoints before uninstalling the server. For instructions, refer to theinstallation guide for the version that you are uninstalling.

BWMIS0161E The Internet Management Server does not have the correct fixpack installed. The InternetManagement Server cannot be automatically upgraded. The installation cannot proceed. ClickCancel to exit.

Explanation: The installation program has detected evidence of an earlier version of the Internet ManagementServer that does not have the 1.7-WSM-U482086 Tivoli Software Fix applied. This software patch must be appliedbefore you can upgrade the installation.

Operator Response:


v Install the 1.7-WSM-U482086 Tivoli Software Fix. This software patch is available at the following Web address:

ftp://ftp.tivoli.com/support/patches/patches_1.7/1.7-WSM-U482086

For instructions on how to install the patch, refer to the 1.7-WSM-U482086.README document, available from thesame location.

BWMIS0162E No endpoint was found on this machine. You must have a Web Services Investigator endpointinstalled in order to apply this upgrade.

Explanation: To apply this upgrade, you must have a Web Services Investigator endpoint installed on this machinewith Tivoli Software Fix 1.7-WSM-U482086.



Operator Response: Use the setup_Endpoint_w32.exe launcher if you want to install the current version of the WebServices Investigator endpoint on this machine. This file is provided on the IBM Tivoli Monitoring for TransactionPerformance, Version 5.1.0: Web Transaction Performance Component Software CD.

BWMIS0163E Java was not found in the system path. The installation cannot proceed. Click Cancel to exit.

Explanation: The PATH environment variable must specify the location of the Java binary files on this machine.

Operator Response: Click Cancel to exit the installation program. While logged on as the root user, add the locationof the Java binary files to the PATH environment variable. The form of the PATH setting is as follows:

PATH=${PATH}:/usr/java/bin

BWMIS0164E Prerequisite patches were not found on this machine. Solaris 2.7 requires 106327-11 (32-bit) or106300-12 (64-bit). Solaris 2.8 requires 108434-04 (32-bit) or 108435-04 (64-bit). The installation cannotproceed. Click Cancel to exit.

Explanation: The specified patches are pre-requisite software for installing a Quality of Service endpoint on a Solarissystem.

Operator Response: Click Cancel to exit the installation program. Install one of the following patches beforerestarting the installation:

v For Solaris 2.7 (SunOS 5.7), 32-bit, install patch 106327-11.




BWMIS0175E The user does not have authority to create tables in this database.

Explanation: The user that you entered in the Database User ID field must have authority to create tables in thespecified DB2 or Oracle database.

v If you are installing the Internet Management Server, this message is displayed if the user does not have authorityto create tables in the tablespace that the database administrator created for the management repository.

v If you are installing a Web Services Courier endpoint, this message is displayed if the user does not have authorityto create tables in the tablespace that the database administrator created for the Web Services Courier datawarehouse.


v Enter the user ID and password of a user that has authority to create tables in the tablespace that will be used forthe management repository or Web Services Courier data warehouse.

v Use your database client software to grant authority to the database user specified in the Database User ID andDatabase Password fields. Grant the permission needed to create tables in the tablespace to be used for themanagement repository or Web Services Courier data warehouse.

BWMIS0505E An error occurred while initializing system services.

Explanation: This error indicates a failure of the InstallShield MultiPlatform installation software.

Operator Response: Check one of the follow log files to determine the exact reason for the failure.

v If you are installing the Internet Management Server, check the TIMS_install_log.txt file. This file is located inthe install_dir/ManagementServer/logs directory, where install_dir is the installation directory for the endpoint.

v If you are installing an Internet Management Endpoint, check the Endpoint_install.log file. This file is located inthe install_dir/Endpoint/logs directory, where install_dir is the installation directory for the endpoint.

BWMIS0524E The endpoint registration failed. Verify the management server information and connectivity.

Explanation: The endpoint installation program attempts to register the endpoint with the management serverwhose information you specified on the Internet Management Server Information dialog. This message is displayed ifthe endpoint cannot register with the management server. Possible causes for this failure are that the managementserver is down or that you specified incorrect information on the Internet Management Server Information dialog.



Operator Response:

v Check the Endpoint_install.log file to determine the exact reason for the failure. This file is located in theinstall_dir/Endpoint/logs directory, where install_dir is the installation directory for the endpoint.

v Verify all information that you entered on the Internet Management Server Information dialog. For example, verifythat you entered the user ID and password of a user authorized to log on to the management server machine thatis specified in the Host Name field. Also check that the security information (whether SSL-enabled or not) and portnumber are correct.

v Verify connectivity to the management server that you specified. Try logging on to the management server from abrowser on this computer.

BWMIS0525E The endpoint cannot unregister from the Internet Management Server.

Explanation: The uninstallation program is unable to unregister the endpoint from the Internet Management Server.Possible causes for this failure are that the management server is down, cannot be contacted, or was uninstalled.

Operator Response: Continue with the uninstallation of the endpoint. If you use the Internet Management Serveragain, the endpoint still appears in the list of registered endpoints.

BWMIS0528E A command used by the installation program failed:

Explanation: A command used by the installation program failed (for example, a command to start or stop aserver). The command that failed is specified in the message.

Operator Response: Consult the traceBWAinstall.log file for more information about the cause of the failure. Thisfile is located in the base installation directory. This is the directory that you specified on the Destination Directorydialog or, in the case of a silent installation, with the tims.InstallLocation or feature.baseInstallDir option. Thedefault installation directory is one of the following:

v For Windows, C:\Program Files\Tivoli\Internet

v For AIX, /usr/Tivoli/Internet

v For S/390 TurboLinx, /Tivoli/Internet

v For other supported UNIX systems, /opt/Tivoli/Internet

BWMIS0533E The following file must be installed: /usr/lib/libstdc++-libc6.1-2.so.3

Explanation: The specified file is prerequisite software if you are installing on a Linux for zSeries (S/390) operatingsystem.

Operator Response: Exit the installation program. Obtain the /usr/lib/libstdc++-libc6.1-2.so.3 file from theprovider of the Linux distribution that is installed on this computer. Install the file before restarting the installation.

BWMIS0541E The key database (.kdb) file cannot be found or is not accessible by the installation program.

Explanation: The installation program cannot find or cannot access the key database (.kdb) file that you specified inthe Key database (.kdb) file path field. This field requires the full path name of a key database file (if one exists onthis computer) that contains a digital certificate for authenticating a secure Quality of Service proxy server to theInternet. A stash (.sth) file containing the password to the key database file must also exist in the same directory.These files must be created using the IBM Key Management Utility.

Operator Response:

v If no key database file exists on this computer, clear the Key database (.kdb) file path field.

When the Key database (.kdb) file path field is left blank, the installation program creates a key database file(named keys.kdb) that contains a self-signed certificate, and a stash file (keys.sth). The self-signed certificate isused for authentication to the Internet until you create a key database file that contains a permanent certificate.The installation program places the keys.kdb and keys.sth files in the following directory:

install_dir/Endpoint/IBMHTTPServer/ssl/keys

where install_dir is the directory where the Quality of Service endpoint is installed.



v If a key database file exists on this computer, verify its location and verify that the installation program has readaccess to the file. The installation program runs as Administrator (or a user with administrator privileges) onWindows systems or as the root user on UNIX systems. Enter the full path name of the file. The following is anexample for a Windows machine:

C:\Program Files\Tivoli\Internet\Endpoint\IBMHTTPServer\ssl\keys\keys.kdb

BWMIS0542E The stash (.sth) file cannot be found in the same location as the key database (.kdb) file or is notaccessible by the installation program.

Explanation: The installation program cannot find a stash (.sth) file for the key database file that you specified inthe Key database (.kdb) file path field. The stash file must be located in the same directory as the key database file.The files must have matching file names.

Operator Response:

v Click Cancel to exit the installation program.

v If the stash file exists, do the following as appropriate:

– Move the stash file to the same directory as the key database file.

– Rename the stash file to match the key database file. For example, if the key database file is named keys.kdb,the stash file must be named keys.sth.

– Verify that the installation program has read access to the file. The installation program runs as Administrator(or a user with administrator privileges) on Windows systems or as the root user on UNIX systems.

v If a stash file does not exist, use the IBM Key Management Utility to create one. For instructions, see the All AboutCertificates chapter.

BWMIS0544E The installation program has detected ISMP packages from a previous installation oruninstallation. Exit and remove the packages before restarting the installation.

Explanation: The installation program has detected InstallShield MultiPlatform (ISMP) packages remaining on thesystem from a previous, partial installation or uninstallation of this or a predecessor product. Leaving these files on aSolaris system can cause erratically unpredictable behavior of ISMP.

Operator Response:

1. Click Cancel to exit the installation program.

2. Remove the following ISMP package directories:

v /var/sadm/pkg/ISTWxM*

v /var/sadm/pkg/ISTivoli_

v /var/sadm/pkg/ISTranPer

3. Restart the installation.

BWMIS0546E The Internet Management Server does not recognize the specified user or password.

Explanation: The installation program cannot connect to the Internet Management Server by using the specified userID and password.

Operator Response:

v Verify that you accurately entered the user ID and password.

v Verify the authorization of the user ID and password by using them to log on to the management server through abrowser.

1. In the address field of the browser, enter the URL of the management server, using the protocol and host namethat you specified on the Internet Management Server Information dialog. (If the SSL Enabled check box isselected, specify https for the protocol. If this box is not selected, specify http for the protocol.) Example:https://servername.it.yourcompany.com.

2. Enter the user ID and password in the appropriate fields.

If there is an ″Unauthorized access attempted″ message, contact the administrator of the management server for anauthorized user ID and password. You might be able to use the default user ID and password (Admin for both).



BWMIS0548E The computer identified in the Host Name field cannot be contacted at the specified port.

Explanation: The installation program cannot connect to the computer specified in the Host Name field because theport is unavailable. Possible reasons for this failure are that the host computer is down, the server software on thespecified port is down, or the server software does not use the specified port. Depending on where the message isissued, the server software could be the management server, the Quality of Service origin server, or a TivoliEnterprise Console server.

Operator Response:

v Verify that you accurately entered the host name and port number.






v Make sure that the host name is the name of a computer that has the server software installed.

v Test connectivity to the network. If the network is down, retry the installation at a later time.

v Try connecting to the server directly through a browser. In the address field of the browser, enter the URL of theserver, using the host name and port number that you specified on the installation dialog. Example:https://servername.it.yourcompany.com:443.

BWMIS0550E An unexpected error occurred while validating connectivity to the Internet Management Server.

Explanation: After verifying that the specified port number is available, and that the user and password informationis valid, the installation program verifies that it can connect to and use the internal processes of the InternetManagement Server. This message is displayed if unusual conditions occur during the brief time it takes for theinstallation program to perform this validation. For example, the management server might have gone down duringthis interval.

Operator Response: Consult the Endpoint_install.log file that is written to the temporary space used by theinstallation program. The installation program places temporary files by default in the /tmp directory on AIX andLinux, and in the /var/tmp directory on Solaris. For Windows systems, the installation program places temporaryfiles in the location specified by the TEMP environment variable setting.

BWMIS0551E The temporary directory is too small or does not have write permission.

Explanation: The installation and uninstallation programs place files by default in one of the following temporarydirectories:

v On Windows systems, the location specified by the TEMP environment variable setting

v On AIX and Linux, the /tmp directory

v On Solaris, the /var/tmp directory

This message is displayed if the default temporary directory, or a temporary directory that you specified whenstarting the installation or uninstallation program, does not have enough space or does not have write permissionassigned. The required space is 120 MB for installing the management server or an endpoint, and 20 MB foruninstallation.

Operator Response:

v Exit the installation or uninstallation program.

v Verify that the default temporary directory, or the temporary directory that you specified, has write permissionassigned to it and that it contains enough space. You might be able to create enough space by removing alltemporary files.

v Specify a different temporary directory (with enough space) by using one of the following methods:

– (Windows systems only) Change the TEMP environment variable setting before restarting the installation oruninstallation.



– (Any system) Specify the -is:tempdir option on the command line when starting the installation oruninstallation. For example, the following command installs the management server on an AIX system andspecifies /usr/tmp as the temporary directory:

setup_TIMS_aix.bin -is:tempdir /usr/tmp

BWMIS0552E The Host Name field is either empty or contains more than 256 characters.

Explanation: Either the Host Name field is empty or contains a name that is too long. The DNS limitation for afully qualified host name is 256 characters.

Operator Response: Verify the correct host name and enter it in the Host Name field.

BWMIS0556E The specified port number is out of range. Valid TCP/IP port numbers are positive integers in therange 1 - 65535.

Explanation: The Port Number field contains a port number that is not within the accepted range of 1 to 65535.

Operator Response: Enter a port number in the Port Number field that is not less than 1 and not greater than65535.

BWMIS0559E Invalid URL format:

Explanation: The URL of the Enterprise Transaction Performance server must be specified in the following format:

protocol://hostname:portnumber

where:

v protocol is one of the following:

– http if the Enterprise Transaction Performance server is not a secure server

– https if the Enterprise Transaction Performance server is a secure server

v hostname is the fully qualified name of the host machine for the Enterprise Transaction Performance server

v portnumber is a valid port number that the Enterprise Transaction Performance server can use to communicate withthe Internet Management Server.


Operator Response: Enter the URL of the Enterprise Transaction Performance server in the correct format.

BWMIS0562E Cannot access file:

Explanation: The installation program cannot read or write to the specified file. The message specifies the full pathto the file and an exception trace that helps determine the cause of the failure. Possible causes are that the file ismissing or locked, the file system is full, or the installation program does not have write access to the file.

Operator Response:

v Verify that the installation program has write permission to the file.

– On Windows systems, the installation program runs as Administrator or a user with administrator privileges.

– On UNIX systems, the installation program runs as the root user.

v Verify that there is sufficient disk space and increase it if necessary.

v Advanced users: Consult the traceBWAinstall.log file for more detail about the exception trace.

BWMIS0563E Error retrieving system variable:

Explanation: The installation program encountered an error while retrieving a system variable. The messagespecifies the system variable and an exception trace that helps determine the cause of the failure.

Operator Response:

v Advanced users: Consult the traceBWAinstall.log file for more detail about the exception trace.



BWMIS0564E The specified name or description (or both) is longer than 254 characters.

Explanation: The Name or Description field, or both, contains more than 254 characters.

Operator Response: Enter no more than 254 characters in each field.

BWMIS0565E The specified DB2 installation directory does not exist or is not accessible.

Explanation: The directory specified in the DB2 Installation Directory field does not exist or the installationprogram does not have read permission to the directory.

Operator Response:

v Verify that the DB2 Installation Directory field contains the full path to the home directory of the owner of theDB2 Instance under which the DB2 database for the management server or Web Services Courier data warehousewas created. The directory must exist on this computer.

– On AIX, specify the path name up to, but not including, the sqllib subdirectory (for example, /data/dbinstl).

– On Windows systems, include the sqllib subdirectory (for example, C:\Program Files\Sqllib).

v On AIX, do the following to find the home directory of the DB2 instance owner:

1. Enter su - db2InstanceOwner, where db2InstanceOwner is the name of the DB2 instance owner, for example,dbinst1. This places you in the home directory of the DB2 instance owner.

2. Enter pwd to display the name of the home directory.

v If the directory name is valid, verify that the installation program has read access to the directory.


– On AIX, the installation program runs as the root user.

BWMIS0566E The specified path to the DB2 installation directory corresponds to a file, not a directory.

Explanation: The Path to DB2 Installation Directory field contains a file name or a directory path with a file nameat the end. The installation program expects a directory path without the file name.

Operator Response: In the Path to DB2 Installation Directory field, enter the full path to the home directory of theowner of the DB2 Instance under which the DB2 database for the management server or Web Services Courier datawarehouse was created. Enter a valid directory path with no file name.

v On UNIX systems, specify the path name up to, but not including, the sqllib subdirectory (for example,/data/dbinstl).

v On Windows systems, include the sqllib subdirectory (for example, C:\Program Files\Sqllib).

BWMIS0567E Cannot access the db2java.zip file.

Explanation: The DB2 client on this computer must be installed with Java support. The installation programrequires access to the db2java.zip file, which should be located in the directory specified in the Path to DB2Installation Directory field. Either the file is missing or the installation program does not have read access to the file.

Operator Response:

v If the db2java.zip file exists in the specified directory, verify that the installation program has read access to thefile.


– On UNIX systems, the installation program runs as the root user.

v If the db2java.zip file is missing, the DB2 client was installed without Java support. Consult your DB2administrator.

BWMIS0568E The specified path corresponds to a directory, not a file.

Explanation: You entered a directory name or a directory path without a file name.

Operator Response: Enter the name of a directory or directory path that includes a file name.



BWMIS0569E Cannot contact proxy server at the specified port.

Explanation: The installation program cannot connect to the computer specified in the Proxy Port field because theport is unavailable. Possible reasons for this failure are that the proxy computer is down, the server software on thespecified port is down, or the server software does not use the specified port.

Operator Response:

v Verify that you accurately entered the host name and port number of the proxy server. Make sure that the proxyhost name is the name of a computer that has the proxy server software installed.






v Verify that the proxy host computer is running.

v Test connectivity to the network. If the network is down, retry the installation at a later time.

v Try connecting to the server directly through a browser. In the address field of the browser, enter the URL of theserver, using the host name and port number that you specified on the installation dialog.Example: https://servername.it.yourcompany.com:443.

BWMIS0570E A problem was encountered while uninstalling Web Detailer services. Refer to the message helpin the Web Transaction Performance Installation Guide for instructions on how to complete thisuninstallation.

Explanation: The uninstall program failed to remove the Web Detailer Proxy and Web Detailer Agent services fromthe Web Services Investigator endpoint.

Operator Response:

v Click Finish to complete the uninstall program.

v Remove the following keys from the Windows registry by following the instructions in Appendix C for recoveringfrom a failed installation or uninstallation.

– HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Web Detailer Proxy

– HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Web Detailer Agent

BWMIS0571E A problem was encountered while uninstalling Web Detailer Layered Service Provider. Refer tothe message help in the Web Transaction Performance Installation Guide for instructions on how tocomplete this uninstallation.

Explanation: The uninstall program failed to run wd_ws2i.exe, an executable file that removes the Web DetailerLayered Service Provider from the Web Services Investigator endpoint. Web Detailer Layered Service Provider is anapplication that checks for TCP/IP and UDP packets going to and from the network. Failure to remove thisapplication could result in a loss of network access.

Operator Response:

1. Click Finish to complete the uninstall program.

2. Follow these steps to manually run wd_ws2i.exe:

a. From a command prompt, change to the following directory:

SystemRoot\system32

where SystemRoot is the drive and directory where Windows is installed (for example, C:\WINNT orC:\WINNT40).

b. Enter the following command to remove the Web Detailer Layered Service Provider:

wd_ws2i /uninstall

c. To ensure that the removal was successful, enter the following command and verify that there are no WebDetailer entries:



wd_ws2i /enum

BWMIS0572E A problem was encountered while uninstalling Web Detailer autoproxy configuration (PAC) files.Refer to the message help in the Web Transaction Performance Installation Guide for instructions onhow to complete this uninstallation.

Explanation: During uninstallation of the Web Services Investigator endpoint, the uninstall program failed toremove LAN configuration settings from Internet Explorer and also failed to remove the Web Detailer autoproxyconfiguration (PAC) files. The LAN configuration settings are automatically added to Internet Explorer when a WebServices Investigator endpoint is installed.

Operator Response:

1. Click Finish to complete the uninstall program.

2. Log on to this machine as the STI Playback user. This is the user that was specified during installation of the WebServices Investigator endpoint. If the installation program created the user, the user name is TivoliSTIPlayback.

3. Follow these steps to remove the LAN configuration settings from Internet Explorer:

a. Open the Internet Explorer browser.

b. Select Internet Options from the Tools menu.

c. Select the Connections tab.

d. Click LAN Settings....

e. Clear the check box labeled Use automatic configuration script.

f. Delete the contents of the Address field just below this check box.

4. Remove the following Web Detailer PAC configuration files:

v install_dir\Endpoint\bin\w32-ix86\wd_PROXYgenerated.pac

v install_dir\Endpoint\bin\w32-ix86\wd_PROXYfunction.pac

v SystemRoot\wd_PROXY.ini

where:

v install_dir is the drive and directory where the Web Services Investigator endpoint is installed.

v SystemRoot is the drive and directory where Windows is installed (for example, C:\WINNT or C:\WINNT40).

BWMIS0573E A problem was encountered while trying to install Web Detailer services. The installation cannotcontinue.

Explanation: The installation program failed to install the Web Detailer Proxy and the Web Detailer Agent serviceson the Web Services Investigator endpoint. Files or registry keys remain on the computer as a result of the failedinstallation.

Operator Response:


v Remove the remaining files or registry keys and then restart the installation. Follow the instructions in Appendix Cfor recovering from a failed installation or uninstallation.

BWMIS0574E A problem was encountered while trying to install Web Detailer Layered Service Provider. Theinstallation cannot continue.

Explanation: The installation program failed to install the Web Detailer Layered Service Provider on the WebServices Investigator endpoint. Files or registry keys remain on the computer as a result of the failed installation.

Operator Response:


v Remove the remaining files or registry keys and then restart the installation. Follow the instructions in Appendix Cfor recovering from a failed installation or uninstallation.



BWMIS0575E A problem was encountered while starting Web Detailer services. The services must be startedmanually.

Explanation: The installation program successfully installed, but failed to start, the Web Detailer Proxy service andthe Web Detailer Agent service on the Web Services Investigator endpoint.

Operator Response: Use one of the following methods to start the services:

v To start the services from the Control Panel on Windows NT:

1. Display the list of services:

a. Select Settings from the Windows Start menu.

b. Select Control Panel.

c. Double-click the Services icon.

2. Select Web Detailer Proxy from the list of services.

3. Click Start to start the Web Detailer Proxy service.

4. Select Web Detailer Agent from the list of services.

5. Click Start to start the Web Detailer Agent service.

v To start the services from the Control Panel on Windows 2000:


a. Select Control Panel from the Windows Start menu.

b. Select Administrative Tools.

c. Select Services.

2. Right-click Web Detailer Proxy in the list of services.

3. Select Start from the pop-up menu to start the Web Detailer Proxy service.

4. Right-click Web Detailer Agent in the list of services.

5. Select Start from the pop-up menu to start the Web Detailer Agent service.

v To start the services from the Control Panel on Windows XP:


a. Select Settings from the Windows Start menu.

b. Select Control Panel.

c. Double-click the Component Services icon.

d. Double-click Services (Local).

2. Right-click Web Detailer Proxy in the list of services.

3. Select Start from the pop-up menu to start the Web Detailer Proxy service.

4. Right-click Web Detailer Agent in the list of services.

5. Select Start from the pop-up menu to start the Web Detailer Agent service.

v To start the services from a command prompt on Windows NT, Windows 2000, or Windows XP, enter thefollowing commands:

– net start "Web Detailer Proxy"

– net start "Web Detailer Agent"

BWMIS0576E An Internet Management Server is already installed on this computer or there are Windowsregistry keys remaining from a previous installation or uninstallation. Click Next to upgrade thisinstallation. If you choose to upgrade be sure that the operating systems and database versions ofthe TIMS and endpoints meet the current requirements. If you do not have an Internet ManagementServer installed, click Cancel to exit. Check for and remove the following registry keys:

Explanation: The installation program has detected Windows registry keys indicating the presence of an earlierversion of the Internet Management Server that can be automatically upgraded. The registry keys are listed in themessage. However, the keys might remain from a previous installation or uninstallation that failed. In that case, acomplete version of the Internet Management Server does not exist on this computer and therefore cannot beupgraded.

Operator Response:



v If there are registry keys and files remaining from a failed installation or uninstallation of the management server,click Cancel to exit the installation. Remove all remaining registry keys and files before attempting to reinstall.Follow the instructions in Appendix C for recovering from a failed installation or uninstallation.

v If a fully installed Internet Management Server exists on this computer and you want to upgrade to the currentversion, click Next to proceed with the upgrade.

BWMIS0576E


Appendix E. 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.

199

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 E. Notices 201

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 Web TransactionPerformance applications. These services include theevent service, scheduler, data manager, and frameworksecurity.

cube. A particular kind of data container used byCognos PowerPlay for multidimensional reporting.

203



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. Web Transaction Performanceapplications use 128-bit encryption for maximumsecurity.

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 Web Transaction Performance,software that converts events into a format that theTivoli Enterprise Console can use and then forwardsthe events to the Tivoli Enterprise Console 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 Web TransactionPerformance application or the Internet ManagementServer. The Web Transaction Performance administratorcan configure one or more responses to specific eventtypes. The possible event responses include logging theevent, notifying an individual or group by e-mail thatthe event has occurred, sending the event to an SNMPapplication, forwarding the event to the TivoliEnterprise Console, and initiating a program 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 Web TransactionPerformance, an application that retrieves informationstored in a database so that it can be formatted andpresented 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 Web Transaction Performanceapplications and resources. An Internet ManagementServer and the Internet Management Endpointsregistered to it together comprise a Web TransactionPerformance administrative domain. Also known as themanagement server and in some of the product code asthe TIMS (Tivoli Internet Management Server).

Glossary 205

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 Web Transaction Performance, theprogram-specific task that you create through the IBMTivoli Monitoring for Transaction Performance userinterface, 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 207

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 209

Index

Special characters-G option 118-is:tempdir option 53, 157-jar option 161-P (product) option 117-silent option

using to install or uninstall WebTransaction Performancecomponents silently 117

-W (wizard panel) option 117/etc/init.d/TIME.rc file 179/etc/init.d/TIMEqhttp.rc file 179/etc/init.d/TivoliIms.rc file 175/etc/inittab 176/etc/rc.d/TIME.rc file 179/etc/rc.d/TIMEqhttp.rc file 179/etc/rc.d/TivoliIms.rc file 175/opt/Tivoli/Internet directory 157/tmp directory 157/var/tmp directory 157./gsk5ikm command 149./startserver.sh command 165./stopserver.sh command 165./wsadbpatch51.sh command 62.bin files 156.cshrc file 46.exe files 156.profile file 46.sth files 150–is command line option 169

about 169–W command line option 169

about 169

Aaccessibility

about xviAdapter Configuration Facility

prerequisite software for Web ServicesCourier endpoints 33

Add Database SmartGuide dialog 104administrator

functions in the Web servicesenvironment 8

AIX operating systemssupported for Internet Management

Server 26supported for Web Services

Courier 26supported for Web Services

Investigator 26supported for Web Transaction

Performance 26application events

defined 9Application Response Measurement

(ARM) APISee ARM 17

Application Response Measurement APISeeARM 4

ARMcollecting data for specific requests in

an STI Player job 21defined 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 18

ARM agentdefined 17

ARM API callsdefined 17

arm_start( ) calls 19arm_stop( ) calls 19assigning data sources

for building cubes 106authentication

using certificates for 145using with certificates 145

autoupdate intervalabout 58about adjusting when upgrading

management server endpoints 56about problems caused when

upgrading Quality of Serviceendpoints 56

defined 157autoupdate process

defined 157

Bback-end service time

defined in Quality of Serviceapplication 1

example in Quality of Serviceapplication 9

BAROC filesabout importing 32

booksonline xiiordering xiiproviding feedback xii

browser requirementsfor IBM Tivoli Monitoring for

Transaction Performance GUI 34for Internet Explorer 35for UNIX platform GUIs 34for Windows NT GUIs 34

bufferpoolscreating for DB2 RDBMS 43

CCA

See certificate authority 145CA-signed certificates

receiving electronically mailed 152catalog program utility 45central data warehouse ETL

defined 11certificate authorities

displaying a list of 151receiving electronically mailed 152

certificate authorityauthenticating user identities and

services 145certificate authority (CA)

defined 145certificate signing requests

defined 145certificates

content signing type defined 147creating new requests for 151creating self-signed 71, 72defined 145displaying default keys in a key

database files 150enabling Secure Sockets Layer

(SSL) 145IBM-supported signer 72list of trusted for key database

files 148organizations for information on 153overview 145personal types defined 147procedure for storing from an

unrecognized CA 151Public Key Infrastructure (PKI)

vendors for 154public key infrastructure (PKI)

vendors for enterprise CAsoftware 154

reasons for using 146reference information for 153root 147security levels of 147self-signed, defined 71server types defined 147software publisher types defined 147standards organizations for

information on 154types of 146, 147using for server and client

authentication 145Client Configuration Assistant

dialog 104command line option

–is 169–W 169

command line options-is:tempdir 53–is 169–W 169

211

command line options (continued)about 52using for troubleshooting and

problem determination 169using to set trace levels 168

commands./gsk5ikm 149./startserver.sh 165./stopserver.sh 165./wsadbpatch51.sh 62file name conventions for native

launcher 52java 51, 161setup_Endpoint_390.bin Linux (S/390)

setup launcher 126setup_Endpoint_390.bin native

launcher 51setup_Endpoint_aix.bin 129setup_Endpoint_aix.bin AIX setup

launcher 126setup_Endpoint_aix.bin native

launcher 51setup_Endpoint_lin.bin 132setup_Endpoint_lin.bin Linux (ix86)

setup launcher 126setup_Endpoint_lin.bin native

launcher 51setup_Endpoint_sol.bin 53setup_Endpoint_sol.bin native

launcher 51setup_Endpoint_sol.bin Solaris setup

launcher 126setup_Endpoint_w32 119setup_Endpoint_w32 Windows setup

launcher 126setup_Endpoint_w32.exe 118setup_Endpoint_w32.exe native

launcher 51setup_launcher 126setup_sti_recorder.exe native

launcher 51setup_TIMS_aix.bin 117, 118, 122setup_TIMS_aix.bin native

launcher 51setup_TIMS_sol.bin 122, 125setup_TIMS_sol.bin native

launcher 51setup_TIMS_w32 122, 125setup_TIMS_w32.exe native

launcher 51startep.sh 165startms.sh 164stopep.sh 165stopms.sh 164sysdef 80uninstall.bin 114, 115wsadbpatch 62

communications protocolsHTTPS, HTTP 14

Configuration for ARM Data Retrievaldialog (Windows) 59, 70

Configuration of Windows User dialog(Windows) 84

connect program utility 45content signing certificates

defined 147

conventionsfor native launcher file names 52

core servicesused by Internet Management

Server 6correlate

defined 17correlations

defined 17correlators

defined 17Create New Self-signed Certificate

dialog 73cubes

assigning data sources forbuilding 106

Customer SupportWeb site for contacting xvi

Ddata mart ETL

defined 11data marts

defined 11data options

for installing Internet ManagementServer in silent mode 123

for silent mode installation of WebServices Investigator endpoints 127

including in option files 118qosep.keyFile 131silent mode installation for Quality of

Service endpoints 129tme.path 134tme.tECHostname 134tme.tECPort 134using silent mode to install Web

Services Courier endpoints 133using with install or uninstall

commands 117data source

configuring Web Services Courier datawarehouse for the discoveryguide 103

data sourcesassigning 106identifying to Tivoli Decision

Support 104identifying to Tivoli Decision Support

Discovery Administrator 104data warehouse

Web Services Courier 7data warehouse, Web Services Courier

software prerequisites for 30data warehouses

upgrading 62Database Configuration dialog (AIX) 69,

89database requirements

for management repository 25for Web Services Courier data

warehouse 25for Web Transaction Performance 25

databasesdisplaying default keys for key 150key, defined 148

DB2 Client Application Enablerrequirement for separate DB2 RDBMS

computer 45using JDBC drivers when

installing 45DB2 database

required information for installingInternet Management Server 66

setting up an ODBC data sourcefor 104

DB2 database clientTivoli Decision

Supportcomponent 103DB2 RDBMS

assigning permissions to users 44configuration tasks for 41creating bufferpools for 43creating tablespace for 44creating the database 42creating the database user 42DB2 Client Application Enabler

requirement for separate DB2RDBMS computer 45

increasing log primaries to optimizeconfiguration 45

sample shell scrpt for configuring 46db2cshrc file 46db2profile file 45, 46DCOMCNFG.EXEutility file 93Demilitarized Zone

See DMZ 13dialogs

Add Database SmartGuide 104Client Configuration Assistant 104Configuration for ARM Data

Retrieval 59Configuration for ARM Data Retrieval

(Windows) 70Configuration of Windows User

(Windows) 84Create New Self-signed Certificate 73Database Configuration (AIX) 69Database Configuration dialog

(AIX) 89Internet Management Server

Configuration (AIX) 68Internet Management Server

Information (STI Recorderinstallation) 98

Internet Management ServerInformation (Windows) 91

ODBC Data SourceAdministrator 103

Origin HTTP Server Configuration(Windows) 86

Quality of Service HTTP Proxy ServerConfiguration (Solaris) 85

Software License Agreement 67Tivoli Enterprise Console Event

Forwarding Options (Windows) 88Web Services Courier Options 88

digital certificatesSee certificates 145

directories/opt/Tivoli/Internet 157/tmp 157/var/tmp 157


directories (continued)languagepacks 158

Discovery Administratorconfiguring shared data files for Tivoli

Decision Support 105identifying data sources to Tivoli

Decision Support 104Tivoli Decision Support

component 102Discovery Client

configuring shared data files for TivoliDecision Support 105

Tivoli Decision Supportcomponent 102

discovery guide 8configuring Web Services Courier data

warehouse as data source for 103importing the Web Transaction

Performance 106installation requirements for Web

Transaction Performance 25installing the Web Transaction

Performance 106setting up the Web Transaction

Performance 105system and software prerequisites

for 102Tivoli Decision Support

component 103uninstalling the Tivoli Web Services

Manager 106using WebSphere Site Analyzer to run

data reports for 103discovery guides

about 101defined 8installing 101

disk space requirementsfor Internet Management

Endpoints 29for Internet Management Server 27for STI Recorder 29

DMZdefined 13

EEJBs

as components of transactionperformance applications 18

Endpoint_install.log file 167, 173endpoint.properties file 58, 157endpoints

as serviced by Internet ManagementServer 6

defined 5supported operating systems for

Quality of Service 26endpoints, Internet Management

installation tasks for 77prerequisites for installing all types

of 78prerequisites for installing Quality of

Service types of 79prerequisites for installing Web

Services Courier types of 80

endpoints, Internet Management(continued)

prerequisites for installing WebServices Investigator types of 78

enterprise CA softwarepublic key infrastructure (PKI)

vendors for 154Enterprise JavaBeans

See EJB 18Enterprise Transaction Performance

component of IBM Tivoli Monitoringfor Transaction Performance,about xi

environment variable, TEMPsetting 157

environment variablesDB2DIR 46DB2INSTANCE 46setting TEMP for Windows only 53

error and message log filesinstallation 167uninstallation 167

event forwarding 16enabling for a Web Services Courier

endpoint 32software support for 30system requirements and prerequisite

software for enabling 32Tivoli Enterprise Console

requirements for 25event integration

enabling 33event responses

defined 9events

defined 9examples

ARM data collection in WebSphereApplication Server 18

ARM support in IBM WebSphereApplication Server 18

collecting ARM data for specificrequests in an STI Player job 21

command to start installing anendpoint 51

installing with -G option in silentmode 118

installing with -P and -W options insilent mode 117

language pack installationprocedures 158

of removing reboot files and links fora management server installed onSolaris 176

option file for installing Quality ofService endpoint 119

removing reboot files and links for aWeb Services Investigator or WebServices Courier endpoint installedon AIX 179

silent mode command-lineinstallation 118

STI Recorder and Web ServicesInvestigator endpoint componentsand data flow 15

examples (continued)system configuration of Web

Transaction Performancecomponents 12

using silent mode installation of WebServices Courier endpoints onWindows systems 137

using silent mode to install a Qualityof Service endpoint on a Linuxsystem 132

using silent mode to install InternetManagement Server on Solaris 125

using silent mode to install InternetManagement Server onWindows 125

using silent mode to install WebServices Investigator endpoint on anAIX system 129

using the command to install Qualityof Service endpoint on a Solarissystem 53

using the setup_Endpoint_w32.exenative launcher to install Quality ofService endpoints 118

Ffile

PKCS12 database 152TranPerf.baroc 33

file name conventionsfor native launcher commands 52for native launchers 56

files/etc/init.d/TIME.rc 179/etc/init.d/TIMEqhttp.rc 179/etc/init.d/TivoliIms.rc 175/etc/inittab 176/etc/rc.d/TIME.rc 179/etc/rc.d/TIMEqhttp.rc 179/etc/rc.d/TivoliIms.rc 175.bin 156.exe 156.profile

.cshrc 46.sth 150about native launcher 156about specifying locations for

temporary installation, upgrade, anduninstall program 53

BAROC 32db2cshrc 46db2profile 45, 46DCOMCNFG.EXE utility 93Endpoint_install.log 167, 173endpoint.properties 58, 157, 158ibmts.dll 111installation error and message

log 167installation files for Web Transaction

Performance components 51JAR 52key database 149key database (.kdb) 85key database, changing passwords

for 150key database, defined 148

Index 213

files (continued)key-pair 145key.kdb 72, 73, 74, 148key.sth 148keys.kdb 79, 94, 95, 148keys.sth 79, 95, 148LCF 88, 135lcf_env.cmd 80, 88, 135lcf_env.sh 80msgTMTPinstall.log 167PKCS12 database 153setup_Endpoint_390.bin 82setup_Endpoint_aix.bin 82setup_Endpoint_lin.bin 82setup_Endpoint_sol.bin 82setup_Endpoint.exe 137setup_QOS.opt 118, 119, 132setup_QOS.opt option 118setup_sti_recorder.exe 97, 98setup_TIMS_aix.bin 56, 59, 67setup_TIMS_sol.bin 56, 59, 67setup_TIMS_w32.exe 56setup_TIMS.jar 56setup_TIMS.opt 119, 122, 125setup_WSC_dw_tec_nontme.opt 119setup_WSC_dw_tec_tme.opt 119setup_WSC.opt 137setup_WSI.opt 119, 129setup.exe 106sporder.dll 111startEP 56stash 148stash files 150TIMS_install_log.txt 167, 173TIMSLP.bin 156, 158TIMSLP.exe 156traceBWAinstall.log 167, 168, 169,

173traceBWAInstall.log 125, 128, 137TranPerf.baroc 32uninstall.bin native launcher 109uninstall.cmd 141uninstall.exe native launcher 109uninstall.jar 109, 141, 160, 161uninstall.opt 109, 141, 143uninstallation error and message

log 167updateQos_51.bat 61upgrade_STI.jar 56wd_ete.dll 111wd_Ispi.dll 111wd_sdk.dll 111wd_W32s.lsp 111wd_WS21i.exe 111wsadbpatch51.bat 62

firewall zonesin Web services environment 13

GGUI installations

defined as interactive installation 77GUI uninstallation

defined as interactive 109GUIs

about product naming in 6

GUIs (continued)browser requirements for IBM Tivoli

Monitoring for TransactionPerformance 34

browser requirements for UNIXplatform 34

browser requirements for WebTransaction Performance 25

browser requirements for WindowsNT 34

Enterprise Transaction Performance 6Web Transaction Performance 6

Hhandbook

Customer Support, Web site for xvihistorical data collection

defined 9for Web Transaction Performance

jobs 10viewing results from Web Transaction

Performance jobs 10historical data collection software

about using with Web ServicesCourier data warehouse 7

RDBMS support requirement for 37HKEY_LOCAL_MACHINE

root of registry key paths 171HTTP

nonsecure communicationsprotocol 14

http protocol 68http protocols 65HTTP transaction

defined 1HTTPS

secure communications protocol 14https protocol 68https protocols 65

IIBM Developer Kit for the Java Platform

prerequisite for upgrading 57prerequisite software for Internet

Management Server 28IBM HTTP Server

as Quality of Service endpoint proxyserver 7

management server software 6IBM JRE

prerequisite software for InternetManagement Endpoints 30

prerequisite software for STIRecorder 30

supported for Web ServicesInvestigator endpoint and STIRecorder 31

IBM Key Management Utilitydefined 148starting 148starting the 72using to authenticate Quality of

Service proxy servers 130

IBM Key Management Utility (continued)using to change the key database file

password 73using to create self-signed

certificates 72using to display IBM-supported signer

certificates 72using to install a keys.kdb file for

Quality of Service proxy servers 94using to obtain certificate

authority 71using to perform key and certificate

tasks 148IBM WebSphere Site Analyzer

prerequisite publications for WebTransaction Performance xiv

ibmts.dll file 111importing

the Web Transaction Performancediscovery guide 106

installationabout installable Web Transaction

Performance components 4about interactive 65about language pack 50about language packs for Internet

Management Server and InternetManagement endpoints 50

about Quality of Service type ofInternet Management endpoint 77

about specifying locations fortemporary installation, upgrade, anduninstall program files 53

about using interactive mode with aGUI 51

about using silent mode 51about using the GUI interactive

mode 77about Web Services Courier type of

Internet Management endpoint 77about Web Services Investigator type

of Internet Managementendpoint 77

CD-ROM locations of language packprograms 156

changing the Internet ManagementServer user ID and password 74

completing for the InternetManagement Server endpoints 91

creating self-signed certificates for theInternet Management Server 71

creating TivoliStiPlayback useraccount for Internet Managementendpoint 78

creating TivoliStiPlayback useraccount for Web ServicesInvestigator Internet Managementendpoint 84

default directories 52error and message log files 167example command to start installing

an endpoint 51example option file for Quality of

Service endpoint 119example using silent mode for

Internet Management Server onSolaris 125


installation (continued)example using silent mode for

Internet Management Server onWindows 125

example using silent mode to installWeb Services Investigator endpointon an AIX system 129

examples examples using silent modeinstallation of endpoints onWindows systems 137

examples of language packprocedures 158

examples using silent modecommand-line 118

failed, recovery procedures for 170failed, recovery procedures on

Windows systems 170installation silent mode procedures

and commands for InternetManagement endpoints 126

interactive prerequisites for theInternet Management Server 65

language pack installation parametersfor UNIX systems 158

language pack installation parametersfor Windows systems 158

language pack programs for STIPlayer 156

location of language pack nativelauncher files and programs 156

of Internet Management endpoints,about 77

of Web Transaction Performancediscovery guide 106

overview 49overview of new Web Transaction

Performance component installation,upgrade, and uninstallprograms 49

post-installation procedures for theInternet Management Server 71

prerequisites for all InternetManagement endpoint types 78

prerequisites for Quality of ServiceInternet Management endpointtypes 79

prerequisites for Web Services CourierInternet Management endpointtypes 80

prerequisites for Web ServicesInvestigator Internet Managementendpoint types 78

procedure for language packs 157procedure for Quality of Service

endpoint 85procedure for starting on all endpoint

types 82procedure for Web Services

Courier 88procedures and commands using

silent mode 120procedures for Internet Management

Server 66programs for Web Transaction

Performance language packs 155programs, messages displayed

by 181

installation (continued)recovery procedures for cleaning up

supported UNIX systemendpoints 176

recovery procedures, locations ofreboot files and links to reboot filesfor the Internet ManagementServer 175

recovery procedures, removingdirectories and files on UNIX-basedsystems 175

recovery procedures, stoppingprocesses on UNIX-basedsystems 173

recovery procedures, stopping serviceson Windows systems 170

recovery procedures,removingdirectories and files on UNIX-basedendpoints 178

requirement to reboot the hostmachine 74

road map of tasks for 54silent mode data options for Web

Services Investigator endpoints 127starting the IBM Key Management

Utility to create a keys.kdb file 94tasks for Internet Management

endpoints 77typical 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 15using -G option in silent mode 118using -P and -W options in silent

mode 117using data options with silent

mode 117using options files in silent mode 118using silent mode command for

Internet Management Server 122using silent mode data options for

Internet Management Server 123using silent mode data options for

Quality of Service endpoints 129using silent mode data options to

install Web Services Courierendpoints 133

using silent mode from the commandline 117

using silent mode procedures forInternet Management Server 122

using special characters for commandsand data options in silentmode 120

using the IBM Key ManagementUtility 71

using the setup_TIMS_aix.bincommand 117

verifying space required for languagepacks 157

installation (continued)Web Transaction Performance

discovery guide 101Web Transaction Performance

discovery guide tasks 101installation requirements

for Web Transaction Performancediscovery guide 25

installations 55about upgrading existing 55restriction for upgrading STI Recorder

installations 55restriction for upgrading using silent

mode 55installing

interactive method, defined 97STI Recorder, about 97STI Recorder, preparing for 97

InstallShield data optionsusing with silent mode installation

and uninstallation commands 117interactive installation

defined 65interactive installations

defined as GUI installation 77interactive mode

about installing Web TransactionPerformance components using aGUI 51

interactive uninstallationdefined as GUI uninstallation 109

Internet Explorerbrowser requirements for 35testing when using TivoliSTIPlayback

on Web Services Investigatorendpoints 93

Internet Management endpointcreating TivoliStiPlayback user

account at installation 78Internet Management endpoints

about installation of 77about installing language packs

for 50installation tasks for 77parameters for uninstalling on

Windows systems 111prerequisites for installing all types

of 78prerequisites for installing Quality of

Service types of 79prerequisites for installing Web

Services Courier types of 80prerequisites for installing Web

Services Investigator types of 78recovery procedures for cleaning up

failed installations, uninstallations,or upgrades on supported UNIXsystems 176

recovery procedures, locations ofUNIX-based reboot files and links toreboot files 179

recovery procedures, removingdirectories and filesUNIX-based 178

recovery procedures, stoppingprocesses manually 177

Index 215

Internet Management endpoints(continued)

uninstalling on UNIX -basedsystems 114

using silent mode commands forinstalling 126

using silent mode installationprocedures and commands for 126

Internet Management Endpointsdefined 5disk space requirements for 29prerequisite software for 30Quality of Service type 6system requirement for 29Web Services Courier type 6Web Services Investigator type 6

Internet Management Serverabout installing language packs

for 50as installable Web Transaction

Performance component 6changing the user ID and

password 74component overview 5creating self-signed certificates for 71disk space requirements for 27IBM Developer Kit for the Java

Platform prerequisite softwarefor 28

installation procedures for 66installation programs for language

packs 155installing 65Java Development Kit (JDK)

prerequisite software for 28post-installation procedures 71prerequisite software for 28

RDBMS 28prerequisites for interactive

installation 65proxy server installation prerequisite

if using to access 78RDBMS requirements for 37recovery procedures, locations of

reboot files and links to reboot filesfor 175

required DB2 database installationinformation 66

required Oracle database installationinformation 66

silent mode installation example onSolaris 125

silent mode installation example onWindows 125

starting and stopping on UNIXsystems 163, 165

starting and stopping on Windowssystems 163, 164

Sun Java Runtime Environmentsoftware prerequisite for 28

supported operating systems for 26system requirements for 27typical setup of 14uninstalling from Windows

systems 113using silent mode command for

installing 122

Internet Management Server (continued)using silent mode data options for

installing 123using silent mode installatiion

procedures for 122Internet Management Server

Configuration dialog 68Internet Management Server Information

dialog (STI Recorder installation) 98Internet Management Server Information

dialog (Windows) 91Internet Management Servers

uninstalling on UNIX-basedsystems 115

ix86, emulated environments 29

JJAR files 52java command 51, 161Java Development Kit (JDK)

prerequisite software for InternetManagement Server 28

Java server pagesSee JSP 18

Java servletsas components of transaction

performance applications 18JDBC drivers

using as part of DB2 ClientApplication Enabler installation 45

JDK 1.3.1 SEprerequisite for upgrading 57

jobscreating and scheduling in the Web

services environment userinterface 8

JRE, IBMsupported for Web Services

Investigator endpoint and STIRecorder 31

JRE, Sunprerequisite software for Internet

Management Endpoints 30prerequisite software for STI

Recorder 30supported for Web Services


JRE, Windows Bundledprerequisite software for Internet


Recorder 30JSP

as components of transactionperformance applications 18

Kkey database (.kdb) file 85key database (.kdb) file path 86key database file

changing the password for 73Key Database File menu 72

key database fileschanging passwords for 150creating new 150opening existing 149specifying a password when

creating 149stashing passwords for existing 150trusted certificates for 148using to authenticate Quality of

Service proxy servers 130key databases

displaying default keys for files 150key files

installed with Web TransactionPerformance 148

key pairscreating new requests for 151

key-pair filesdefined 145

key-pairsusing to obtain server certificates 145

key.kdb file 72, 73, 74, 148key.sth file 148keys

exporting to other key databases 152importing from a PKCS12 file 153importing to other key databases 153organizations for information on 153overview of public and private 145Public Key Information (PKI) vendors

for 154public key infrastructure (PKI)

vendors for enterprise CAsoftware 154

reference information for 153standards organizations for

information on 154using with server and client

certificates 145keys.kdb file 79, 94, 95, 148keys.sth file 79, 95

Llanguage packs

about 155about installation of 50about installing for Internet

Management Server and InternetManagement endpoints 50

available for Web TransactionPerformance 155

CD-ROM locations of installationprograms for 156

examples of installationprocedures 158

installation parameters for installingon UNIX systems 158

installation parameters for installingon Windows systems 158

installation procedure for 157installation programs for 155installation programs for Internet

Management Server 155installation programs for STI

Recorder 156


language packs (continued)location of installation programs

for 156location of programs for

uninstalling 160uninstallation procedure 161uninstalling 160verifying space required for

installing 157languagepacks directory 158languages, national

supported in Tivoli Web Solutions 35LCF file 88, 135lcf_env.cmd file 80, 88, 135lcf_env.sh file 80Linux operating systems

supported for Quality of ServiceEndpoint 26

supported for Web ServicesCourier 26

supported for Web ServicesInvestigator 26

supported for Web TransactionPerformance 26

log filesinstallation error and message 167uninstallation error and message 167

log primariesincreasing to optimize DB2 RDBMS

configuration 45log retain function

for DB2 RDBMS configuration 45

Mmanagement repository

database requirements for 25defined 6, 37RDBMS supported for 37

management server 6defined 5secure, manually restarting when

upgrading on UNIX systems 61secure, manually restarting when

upgrading on Windows systems 61user interface 5

manualsonline xiiordering xiiproviding feedback xii

menusKey Database File 72

messagesdisplayed by installation, upgrade, or

uninstall programs 181Microsoft Virtual Machine

browser requirement for InternetExplorer 35

mod_ibm_ssl patch 80msgTMTPinstall.log file 167

Nnaming

about product in the GUIs 6

national languagessupported in Tivoli Web Solutions 35

native launcherdefined 51

native launcher fileslocation of language pack files and

programs 156native launcher files, about 156native launchers

file name conventions for 56setup_Endpoint_aix.bin 51

network modedefined 102

OODBC data source

setting up a connection for DB2 104setting up a connection for

Oracle 103ODBC Data Source Administrator

dialog 103OLE server

endpoint post-installation procedurefor adding STI Player account 92

procedure for adding permissions forthe STI Player 93

onlineaccessing publications xv

Open GroupApplication Response Measurement

(ARM) API a Technical Standard 4operating systems

supported for Internet ManagementServer 26


supported for Web ServicesCourier 26


supported for Web ServicesInvestigator endpoint and STIRecorder 31


supported for Web TransactionPerformance components xi

supportedfor STI Recorder 26option files

about using -silent for installing oruninstalling 117

including -P, -W, and -G data optionsin 118

provided by Web TransactionPerformance 119

setup_QOS.opt 118silent mode installation 118

options-is:tempdir 157-is:tempdir command line 53-jar 161about command line 52using -G when installing Web

Transaction Performancecomponents 118

options (continued)using -P (product) and -W (wizard

panel) when installing WebTransaction Performancecomponents 117

Oracle databaserequired information for installing

Internet Management Server 66setting up an ODBC data source

for 103Oracle database client


Oracle RDBMSconfiguration tasks 38sample scripts for configuration

tasks 39Origin HTTP Server Configuration dialog

(Windows) 86origin server

defined 7origin servers

defined 15gathering information for installing on

Quality of Service InternetManagement endpoints 79, 80

PPage Analyzer Viewer

about using with STI Player 3engine for Web Services Investigator

endpoint 7Page display time

defined in Quality of Serviceapplication 1

page render timedefined in Quality of Service

application 1parameters

for upgrading on UNIX systems 59for upgrading on Windows

systems 59parent transactions

defined 17passwords

changing for key database files 150stashing for existing key database

files 150patches

mod_ibm_ssl 80Tivoli Software Fix

1.7-WSM-U48208 57Tivoli Software Fix

1.7-WSM-U482086 63personal certificates

defined 147PKCS12 database files 152

importing keys from 153PKI

See public key insfrastructure 153platform directories

location of native launcher files 156post-installation

procedure for adding permissions forthe STI Player on OLE server 93

Index 217

post-installation (continued)procedure for secure Quality of

Service proxy servers 94procedure for Web Services

Investigator endpoints 92procedures for making password

changes for Web ServicesInvestigator endpoints on Windowssystems 93

procedures for STI Playeraccounts 92

testing Internet Explorer on WebServices Investigator endpoints 93

prerequisite softwareAdapter Configuration Facility for

Web Services Courier endpoints 33for enabling event forwarding in

Tivoli Enterprise Console 32for Internet Management

Endpoints 30for Internet Management Server 28

RDBMS 28for RDBMS support 28for STI Recorder 30for Tivoli Enterprise Console event

forwarding 33for Web Services Courier 30for Web Services Investigator 30IBM Developer Kit for the Java

Platform for Internet ManagementServer 28

Java Development Kit (JDK) forInternet Management Server 28

Sun Java Runtime Environment forInternet Management Server 28

prerequisitesfor installing all Internet Management

endpoint types 78for installing Quality of Service

Internet Management endpointtypes 79

for installing Web Services CourierInternet Management endpointtypes 80

for installing Web ServicesInvestigator endpoint types 78

using proxy server if accessingInternet Management Server 78

Web Transaction Performancediscovery guide system andsoftware 102

prerequisites, software, defined 25problem determination

using command line options for 169program utilities

catalog and connect 45protocols

http 68https 68https and http 65

proxy serverfor Quality of Service endpoint 7verifying settings for installing the STI

Recorder 97

proxy serversabout possible problems caused when

upgrading Quality of Serviceendpoints 56

creating and using installation userand group accounts for Quality ofService Internet Managementendpoints 79

defined 15for Quality of Service 130gathering information for installing on

Quality of Service InternetManagement endpoints 79, 80

installation prerequisite if using toaccess Internet ManagementServer 78

key files installed for Quality ofService 148

procedure for secure Quality ofService 94

Quality of Service, procedures forstopping and starting onUNIX-based systems 165

Quality of Service, procedures forstopping and starting on Windows2000 systems 165

Quality of Service, procedures forstopping and starting on WindowsNT systems 165

Public Key Information (PKI)vendors for commercial CA

software 154vendors for enterprise CA

software 154public key insfrastructure (PKI)

organizations for information on 153standards organizations for

information on 154public key insfrastructure (PKI)

references 153publications

accessing online xvcustomer feedback survey for xvfor IBM WebSphere Site

Analyzer xivIBM Tivoli Enterprise Console,

prerequisite for Web TransactionPerformance xiii

IBM WebSphere Application Server,prerequisite for Web TransactionPerformance xiv

online xiiordering xii, xvproviding feedback xiiproviding feedback about xvTivoli Decision Support, prerequisite

for Web TransactionPerformance xiv

Tivoli Enterprise Data Warehouse,prerequisite for Web TransactionPerformance xiv

Qqosep.keyFile

data option 131

Quality of Serviceabout possible proxy server problems

caused when upgradingendpoints 56

about round trip time in 1about using with STI Player 4application, about 1back-end service time example in 9endpoint, about installation of 77endpoint, software included for 7endpoints, upgrading 57example option file for installing

endpoint for 119examples using silent mode to install

endpoints for on a Linuxsystem 132

IBM HTTP Server as proxy server forthe endpoint 7

key files installed for proxyservers 148

planning tasks for jobs whenupgrading 56

post-installation procedure for secureproxy servers 94

prerequisites for installing InternetManagement endpoint types 79

proxy server 130proxy server for endpoint 7proxy servers, procedures for stopping

and starting on UNIX-basedsystems 165

proxy servers, procedures for stoppingand starting on Windows 2000systems 165

proxy servers, procedures for stoppingand starting on Windows NTsystems 165

storing the CA-signed certificate for aproxy server 95

type of Internet ManagementEndpoint 6

typical installation setup ofendpoints 15

using key database files toauthenticate proxy servers for 130

Web Transaction Performanceapplication, about 1

Quality of Service applicationback-end service time defined in 1

Quality of Service Endpointsupported operating systems for 26

Quality of Service endpointsusing silent mode installation data

options for 129Quality of Service HTTP Proxy Server

Configuration dialog (Solaris) 85

RRDBMS

about installing 14client, defined 37prerequisite software

for Internet ManagementServer 28

requirements for Internet ManagementServer 37


RDBMS (continued)software prerequisite for Web Services

Courier data warehouse 30supported for management

repository 37supported for Web Services Courier

data warehouse 38RDBMS support

prerequisite software for 28reboot files

example for removing reboot files andlinks for a Web Services Investigatoror Web Services Courier endpointinstalled on AIX 179

example of removing reboot files andlinks for a management serverinstalled on Solaris 176

locations of UNIX-based InternetManagement endpoint 179


rebooting the host machineinstallation requirement 74

Recorder, STIsupported operating systems for 26

recovery proceduresexample of removing reboot files and

links for a management serverinstalled on Solaris 176

for cleaning up supported UNIXsystem endpoints 176

for failed installation, upgrade, oruninstallation 170

for failed installation, upgrade, oruninstallation on Windowssystems 170

locations of reboot files and links toreboot files for the InternetManagement Server 175

locations of reboot files and links toUNIX-based reboot files for InternetManagement endpoints 179

removing directories and files fromfailed installation, uninstallation, orupgrade 172

removing directories and files onUNIX-based endpoints 178

removing directories and files onUNIX-based systems 175

stopping processes manually forInternet Managementendpoints 177

stopping processes on UNIX-basedsystems 173

stopping processes with a script 176stopping services on Windows

systems 170registry keys

about 171HKEY_LOCAL_MACHINE key path

root 171removing from Windows Registry

Editor 172

relational database management systemsoftware prerequisite for Web Services

Courier data warehouse 30reverse proxy servers

defined 15road map of installation tasks 54rollback segments

requirements for Oracle configurationtasks 39

root authorityroot certificates 147

root certificatesroot authority 147

round trip timedefined 1

round-trip timeabout measuring using STI Player 4using STI Player to measure 3

Sscripts

stopep.sh 176stopserver.sh 176

Secure Sockets Layer (SSL)enabling with certificates 145Tivoli Web Component Manager

security protocol 14security levels

of certificates 147self-signed certificates

using to install Quality of ServiceInternet Management endpoints 79

server certificatesdefined 147

service timedefined in Quality of Service

application 1using STI Player to provide

measurements of 4setup requirements

for Tivoli Decision Support 25setup_Endpoint_390.bin file 82setup_Endpoint_390.bin Linux (S/390)

setup launcher command 126setup_Endpoint_390.bin native launcher

command 51setup_Endpoint_aix.bin AIX setup

launcher command 126setup_Endpoint_aix.bin command 129setup_Endpoint_aix.bin file 82setup_Endpoint_aix.bin native

launcher 51setup_Endpoint_aix.bin native launcher

command 51setup_Endpoint_lin.bin command 132setup_Endpoint_lin.bin file 82setup_Endpoint_lin.bin Linux (ix86) setup

launcher command 126setup_Endpoint_lin.bin native launcher

command 51setup_Endpoint_sol.bin command 53setup_Endpoint_sol.bin file 82setup_Endpoint_sol.bin native launcher

command 51setup_Endpoint_sol.bin Solaris setup

launcher command 126

setup_Endpoint_w32 command 119setup_Endpoint_w32 Windows setup

launcher command 126setup_Endpoint_w32.exe command 118setup_Endpoint_w32.exe native launcher

command 51setup_Endpoint.exe file 137setup_QOS.opt file 118, 119, 132setup_QOS.opt option file 118setup_sti_recorder.exe file 97, 98setup_sti_recorder.exe native launcher

command 51setup_STIR.opt file

filessetup_STIR.opt file 138

setup_TIMS_aix.bin command 51, 117,118

setup_TIMS_aix.bin file 59, 67setup_TIMS_aix.bin native launcher

file 56setup_TIMS_aix.bin setup launcher

command 122setup_TIMS_sol.bin command 51, 125setup_TIMS_sol.bin file 59, 67setup_TIMS_sol.bin native launcher

file 56setup_TIMS_sol.bin setup launcher

command 122setup_TIMS_w32 command 125setup_TIMS_w32 setup launcher

command 122setup_TIMS_w32.exe command 51setup_TIMS_w32.exe native launcher

file 56setup_TIMS.jar file 56setup_TIMS.opt file 119, 122, 125setup_WSC_dw_tec_nontme.opt file 119setup_WSC_dw_tec_tme.opt file 119setup_WSC.opt file 137setup_WSI.opt file 119, 129setup.exe file 106Shared Data


shared data filesconfiguring for Tivoli Decision

Support 105configuring for Tivoli Decision

Support Discovery Administratorand Discovery Clients 105

defined 102silent installation

STI Recordercommands for 138data options for 139procedures for 138

silent installation and uninstallationSee silent mode 117

silent modeabout installing Web Transaction

Performance components using 51command-line examples of installation

using 118commands to install Internet

Management endpoints 126data options for installing Internet

Management Server in 123

Index 219

silent mode (continued)example option file for installing

Quality of Service endpoint in 119example using -P and -W

options 117example using to install Web Services

Courier endpoints on Windowssystems 137

example using to install Web ServicesInvestigator endpoint on an AIXsystem 129

examples using to install a Quality ofService endpoint on a Linuxsystem 132

examplse using -G option 118installation command for Internet

Management Server 122installation data options for Web

Services Investigator endpoints 127installation example for Internet

Management Server on Solaris 125installation example for Internet

Management Server onWindows 125

installation option files 118installation procedures and commands

for Internet Managementendpoints 126

Internet Management Serverinstallation procedures 122

overview of using for installation anduninstallation 117

procedures and commands forinstallation and uninstallationusing 120

using -G option when installing WebTransaction Performancecomponents 118

using -P and -W options wheninstalling Web TransactionPerformance components 117

using data options to install Qualityof Service endpoints 129

using data options to install WebServices Courier endpoints 133

using InstallShield data options 117using special characters in installation

and uninstallation commands anddata options 120

using to install, uninstall, or upgradeWeb Transaction Performancecomponents 117

silent uninstallationWeb Solutions product components

commands for 142data options for 142examples for 143

Site Investigatorabout 1planning tasks for jobs when

upgrading 56Web Transaction Performance

application, about 1Software License Agreement dialog 67software prerequisites

Web Services Courier datawarehouse 30

software prerequisites, defined 25software publisher certificates

defined 147software, prerequisite

for Internet Management Server 28IBM Developer Kit for the Java

Platform for Internet ManagementServer 28

Sun Java Runtime Environment forInternet Management Server 28

solaris environments 29Solaris operating systems



supported for WebServicesCourier 26


special charactersfor silent mode installation and

uninstallation commands and dataoptions 120

sporder.dll file 111SQL scripts

for Oracle configuration tasks 39SSL

See Secure Sockets Layer 145Secure Sockets Layer security

protocol 14standalone mode

defined 102startEP file 56startep.sh command 165startms.sh command 164stash file 148stash files 150stash passwords

for existing key database files 150STI

See Synthetic TransactionInvestigator 2

STI Playerabout 2about playback jobs 3account used for Web Services

Investigator endpointpost-installation procedure 92

capabilities 2collecting ARM data for specific

requests in a job 21endpoint post-installation procedure

for adding account to OLEserver 92

measuring round-trip time 3planning tasks for playback jobs when

upgrading 56procedure for adding OLE server

permissions 93using the TivoliStiPlayback user

account when uninstalling 112using the TivoliStiPlayback user

account when upgrading 63using with ARM data collection 4with Page Analyzer Viewer 3with Quality of Service 4

STI Recorderabout 2about installing language packs

for 50disk space requirements for 29endpoints, 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

installing, about 97Internet Management Server

Information dialog for installationof 98

language pack installation programsfor 156

preparing for installing 97prerequisite software for 30silent installation

commands for 138data options for 139procedures for 138

supported operating systems for 26system requirements for 29uninstalling 116verifying proxy server connections for

installing 97STIRLP.exe file 158stopep.sh command 165stopep.sh script 176stopms.sh command 164stopserver.sh script 176sub-transactions

defined 17Sun Java Development Kit

prerequisite for upgrading 57Sun Java Runtime Environment

prerequisite software for InternetManagement Server 28

Sun JREprerequisite software for Internet


Recorder 30supported for Web Services


Synthetic Transaction InvestigatorWeb Transaction Performance

application, about 1Synthetic Transaction Investigator (STI)

about 2sysdef command 80system requirements

for enabling event forwarding inTivoli Enterprise Console 32

for Internet ManagementEndpoints 29

for Internet Management Server 27for STI Recorder 29

system requirements, defined 25


Ttablespace

creating for DB2 RDBMS 44requirements for Oracle configuration

tasks 38TEMP environment variable

setting 157setting for Windows only 53

TIMS_install_log.txt file 167, 173TIMSLP.bin 156TIMSLP.bin file 158TIMSLP.bin files 156TIMSLP.exe 156TIMSLP.exe file 158Tivoli Decision Support

about 8as Web Transaction Performance

discovery guide 5configuring shared data files for 105DB2 database client component

of 103Discovery Administrator component

of 102Discovery Client component of 102discovery guide component of 103identifying data sources to 104Oracle database client component

of 103prerequisite publications for Web

Transaction Performance xivsetting up 102setup requirements for 25Shared Data component of 102Web Transaction Performance

discovery guide 8Tivoli Decision Support discovery guides

typical installation setup 16Tivoli Enterprise Console

event forwarding from Web ServicesCourier endpoint 16

event forwarding requirementsfor 25

event forwarding software supportfor 30

event forwarding system requirementsand prerequisite software forenabling 32

prerequisite publications for WebTransaction Performance xiii

summary of integration with WebTransaction Performance 11

using to enable event forwarding for aWeb Services Courier endpoint 32

Tivoli Enterprise Console (TEC)event-forwarding feature of Web

Services Courier endpoint 7Tivoli Enterprise Console Event

Forwarding Options dialog(Windows) 88

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 11

Tivoli Internet Management EndpointService

specifying user account for 84using to identify password

changes 78Tivoli management agent

as part of a Tivoli Enterpriseinstallation 13

prerequisite software for Web ServicesCourier endpoints 33

using to forward events from WebServices Courier endpoints 16

Tivoli Software Fix 1.7-WSM-U482086patch 63

Tivoli Web Component ManagerSSL security protocol 14

Tivoli Web Solutionssupported national languages for 35

TivoliStiPlaybackuser account when uninstalling STI

Player 112user account when upgrading STI

Player 63TivoliSTIPlayback

account used for Web ServicesInvestigator endpointpost-installation procedure 92

testing Internet Explorer on WebServices Investigator endpoints 93

TivoliStiPlayback user accountcreating for use by Internet

Management endpointinstallation 78

creating for use by Web ServicesInvestigator Internet Managementendpoint installation 84

tme.path data option 134tme.tECHostname data option 134tme.tECPort data option 134trace levels

command line options for setting 168settings for traceBWAinstall.log

file 168using command line options to set for

traceBWAinstall.log 168traceBWAinstall.log file 167, 169, 173

setting trace levels for 168settings for 168

traceBWAInstall.log file 125, 128, 137TranPerf.baroc file 32, 33transactions

defined 17troubleshooting

using command line options for 169trusted certificates

for key database files 148typeface conventions xvi

Uuninstall.bin command 114, 115uninstall.bin native launcher file 109uninstall.cmd file 141uninstall.exe native launcher file 109uninstall.jar file 109, 141, 160uninstall.jar files 161uninstall.opt file 109, 141, 143

uninstallationabout specifying locations for

temporary installation, upgrade, anduninstall program files 53

about Web Transaction Performancelanguage pack programs 50

about Web Transaction Performanceprograms 50

dependencies 109error and message log files 167failed, recovery procedures for 170failed, recovery procedures on

Windows systems 170file locations 110interactive, defined 109location of programs for language

packs 160of Internet Management Server from

Windows systems 113of language packs 160of Tivoli Web Services Manager

discovery guide 106overview of new Web Transaction


parameters for Internet Managementendpoints on Windows systems 111

procedure for language packs 161procedures and commands using

silent mode 120programs, messages displayed

by 181recovery procedures for cleaning up



recovery procedures, removingdirectories and files on UNIX-basedendpoints 178

recovery procedures, removingdirectories and filess onUNIX-baseds systems 175

recovery procedures, stoppingprocesses on UNIX-basedssystems 173

recovery procedures, stopping serviceson Windows systems 170

using data options with silentmode 117

using silent mode from the commandline 117

using special characters for commandsand data options in silentmode 120

using the setup_TIMS_aix.bincommand 117

using the TivoliStiPlayback useraccount for STI Player 112

uninstallingInternet Management Servers on

UNIX-based systems 115STI Recorder 116

Index 221

uninstallionof Internet Management endpoints on

UNIX-based systems 114UNIX

GUI browser requirements for 34systems, language pack installation

parameters for installing on 158updateQos_51.bat file 61upgrade_STI.jar file 56upgrading

about 55about specifying locations for

temporary installation, upgrade, anduninstall program files 53

about the automatic upgrade processfor 58, 157

data warehouses 62failed, recovery procedures for 170failed, recovery procedures on

Windows systems 170location of programs for 56management server and most

endpoints, about 57management server, JDK 1.3.1 SE

prerequisites 57manually restarting a secure

management server onUNIXsystems 61

manually restarting a securemanagement server on Windowssystems 61

on UNIX systems, parameters for 59on Windows systems, parameters

for 59overview of new Web Transaction


planning for 56planning tasks for management server

endpoints 56planning tasks for Quality of Service

endpoints 56planning tasks for STI playback,

Quality of Service, and SiteInvestigator jobs 56

procedures, restrictions for 55programs, messages displayed

by 181Quality of Service endpoints 57recovery procedures for cleaning up



recovery procedures, removingdirectories and files on UNIX-basedendpoints 178

recovery procedures, removingdirectories and files on UNIX-basedsystems 175

recovery procedures, stoppingprocesses on UNIX-basedsystems 173

upgrading (continued)recovery procedures, stopping services

on Windows systems 170restriction for silent mode

installations 55restriction for STI Recorder

installations 55Web Services Courier endpoints 57Web Services Investigator endpoint

registered to the managementserver 63

Web Services Investigatorendpoints 57

Web Transaction Performancecomponents 49

Web Transaction Performancecomponents, about not using silentmode for 117

user experience timedefined 1

user interfacefor Web Transaction Performance 6in the Web services environment 8

Vvariables

setting TEMP environment forWindows only 53

setting the TEMP environment 157variables, environment

DB2DIR 46DB2INSTANCE 46

VeriSign checkscertificate levels of 147

Wwarehouse enablement packs

defined 11warehouse packs

defined 11wd_ete.dll file 111wd_Ispi.dll file 111wd_sdk.dll file 111wd_W32s.lsp file 111wd_WS21i.exe file 111Web Detailer

defined 7Web Services Courier

endpoint, about installation of 77endpoints, typical installation setup

of 16endpoints, upgrading 57endpoints, using to forward events to

Tivoli Enterprise Console 16example for removing reboot files and

links on AIX 179examples using silent mode

installation of endpoints onWindows systems 137

prerequisite software for 30prerequisites for installing Internet

Management endpoint types 80supported operating systems for 26

Web Services Courier (continued)type of Internet Management

Endpoint 6Web Services Courier data warehouse

about transferring data to TivoliEnterprise Data Warehouse 7

about using historical data collectionsoftware with 7

configuring as data source for thediscovery guide 103

database requirements for 25defined 37feature of Web Services Courier

endpoint 7identifying as data source to Tivoli

Decision Support 104identifying as data source to Tivoli

Decision Support DiscoveryAdministrator 104

RDBMS supported for 38software prerequisites for 30

Web Services Courier endpointAdapter Configuration Facility

prerequisite software for 33software included with 7Tivoli Enterprise Console (TEC)

event-forwarding feature of 7Web Services Courier data warehouse

feature of 7Web Services Courier endpoints

prerequisite software for TivoliEnterprise Console eventforwarding 33

prerequisite software for Tivolimanagement agent 33

using silent mode data options toinstall 133

Web Services Courier Options dialog 88Web services environment

firewall zones 13Web Services Investigator

creating TivoliStiPlayback useraccount when installing 84

endpoint post-installationprocedure 92

endpoint, about installation of 77endpoint, upgrading on Windows

systems when registered to themanagement server 63

endpoints, testing Internet Explorerwhen using TivoliSTIPlayback 93

endpoints, typical installation setupof 15

endpoints, upgrading 57example for removing reboot files and

links on AIX 179example using silent mode to install

Web Services Investigator endpointon an AIX system 129

example with STI Recordercomponent and data flow 15

prerequisite software for 30prerequisites for installing Internet

Management endpoint types 78procedures for making password

changes on Windows systems 93supported operating systems for 26


Web Services Investigator (continued)type of Internet Management

Endpoint 6Web Services Investigator endpoint

Page Analyzer Viewer engine for 7Site Investigator application for 7software included with 7

Web Services Investigator endpointssilent mode installation data options

for 127Web Solutions product components

silent uninstallationcommands for 142data options for 142examples for 143

Web Transaction Performanceabout installable components in 4available language packs for 155browser requirements for 25component of IBM Tivoli Monitoring

for Transaction Performance,about xi

components, operating systemssupported for xi

database requirements for 25IBM Tivoli Enterprise Console

publications prerequisite xiiiIBM WebSphere Application Server

publications prerequisite xivIBM WebSphere Site Analyzer

publications prerequisite xivinstallation programs for language

packs in 155location of installation programs for

language packs 156location of language pack native

launcher files and programs 156messages displayed by installation,

upgrade, or uninstall programs 181overview 1Quality of Service application,

about 1Site Investigator application, about 1supported operating systems for 26Synthetic Transaction Investigator

application, about 1Tivoli Decision Support publications

prerequisite xivTivoli Enterprise Data Warehouse

publications prerequisite xivusing the silent mode to install,

uninstall, or upgrade componentsof 117

Web Transaction Performance discoveryguide

installation requirements for 25WebSphere Application Server

ARM support in 18enabling 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 xiv

WebSphere Site Analyzerabout 12using to run discovery guide data

reports 103WebSphereApplication Server

about 12Windows

systems, language pack installationparameters for installing on 158

Windows Bundled JREprerequisite software for Internet


Recorder 30Windows NT

GUI browser requirements for 34Windows operating systems



supported for STI Recorder 26supported for Web Services

Courier 26supported for Web Services

Investigator 26Windows XP

supported operating system for WebServices Investigator endpoint andSTI Recorder 31

wsadbpatch command 62wsadbpatch51.bat file 62

Index 223

��

Printed in U.S.A.

GC23-4801-00

publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/itmftp/gc23-4801... · contents figures...

Documents