tivoli web services analyzer - ibmpublib.boulder.ibm.com/...userguide/.../twsamst.pdf · tivoli web...

Tivoli Web Services AnalyzerVersion 1.7 User’s Guide GC32-0743-00

Tivoli Web Services Analyzer User’s Guide

Copyright Notice

© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. Nopart of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without priorwritten permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductionsof any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporationcopyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The documentis not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, TivoliEnterprise, Tivoli Enterprise Console, Tivoli Ready, and TME are trademarks or registered trademarks of International BusinessMachines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, othercountries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Pentium is a trademark of Intel Corpration in the United States and other countries.

Oracle is a trademark of the Oracle Corporation.

Netscape and the Netscape N and Ship’s Wheel logos are registered trademarks of Netscape Communications Corporation in theUnited States and other countries.

Sun, Sun Microsystems, the Sun Logo, Sun™ workstation, Solaris Operating Environment™, software, SPARCstation™ 20 system,Java™ technology, iPlanet™ software, and Sun RPC are trademarks or registered trademarks of Sun Microsystems, Inc. in theUnited States and other countries.

This product includes software developed by the Apache Software Foundtion (http://www.apache.org/). Copyright © 1999 TheApache Software Foundation.

VeriSign is a trademark of VeriSign, Inc. Copyright © 1998 VeriSign, Inc. All rights reserved.

Contains RSA technology. Copyright © 1991 RSA Laboratories, a division of RSA Data Security, Inc. All rights reserved.

Other company, product, and service names may be trademarks or service marks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patentsor pending patent applications covering subject matter in this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, NorthCastle Drive, Armonk, New York 10504-1785, U.S.A.

© Copyright International Business Machines Corporation 2001. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWhat’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Tivoli Web Solutions Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Conventions Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Typeface Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Tivoli Web Services Analyzer Overview. . . . . . . . . . . . . . . . . . . . . . . . 1What is Tivoli Web Services Analyzer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

How are Log Files Collected? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Configuring Web Server Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Configuring Web Log Files for Microsoft Internet Information Server (IIS) Web Servers . . . . . . 3

Configuring Web Log Files for Apache Web Servers on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 5

Configuring Web Log Files for NES/iPlanet Web Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2. GUI Overview and Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Starting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Areas of the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Greenwich Mean Time Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Help Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Work Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3. Using the Scheduler for Web Log File Collection . . . . . . . . . . . . 15Creating a Job to Collect Web Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Editing a Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Unscheduling a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Deleting a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring Web Services Analyzer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

To configure a Tivoli Web Services Analyzer event:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Examining the Web Services Analyzer Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

iiiTivoli Web Services Analyzer Version 1.7 User’s Guide

Tivoli Web Data Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Restart and Recovery of the Web Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4. Managing Events and Event Responses. . . . . . . . . . . . . . . . . . . . . . 21Creating Event Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Forwarding Events to the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Forwarding Events to an SNMP Management Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Forwarding Events to an E-mail Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Forwarding Events to the EXEC Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Forwarding Event Data Using the EXEC Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Event Severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5. Managing Data in the Management Repository . . . . . . . . . . . . . . 33Usage of the ims_purgedb Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Deleting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 6. Internet Management Server Administration . . . . . . . . . . . . . . . . . 37Managing the Event Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Forwarding Events to the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Forwarding Events to an SNMP Management Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Forwarding Events to an E-mail Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Starting and Stopping the Internet Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Starting and Stopping on Windows Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Starting and Stopping on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Stopping and Starting an Endpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 7. Tivoli Decision Support Guide for Tivoli Web ServicesAnalyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Building Cubes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Scheduling the Cube Build Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Topics and Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Tivoli Decision Support Guide for Web Services Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Tivoli Decision Support Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Solving Cube-Building Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Solving Report Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 8. Scheduling Application Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Run Continuously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

iv

Run Once . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Run Repeatedly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 9. General Tasks and System Administration . . . . . . . . . . . . . . . . . . . 55Global Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

View all Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

View Global Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

View All Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

System Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configure System Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

View the System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Create Event Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Manage Application Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Manage Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Viewing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

View TIMS Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Change Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 10. Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Providing Feedback About Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

User Interface Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Adjusting Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Message IDs for the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Database Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Reporting Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Support Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

vTivoli Web Services Analyzer Version 1.7 User’s Guide

Preface

Tivoli Web Services Analyzer provides you with a clear picture of the overall health of youre-business infrastructure. It consolidates globally distributed Web server log files into asingle data warehouse. It then uses powerful online analytical processing (OLAP)technology, through Tivoli Decision Support, to create detailed reports on Web serveractivity and visitor statistics. In addition, Tivoli Web Services Analyzer goes beyond simplelog file analysis by integrating the information about the end user’s experience. This isaccomplished by correlating Web usage information with performance and availabilitymetrics from Tivoli Web Services Manager.

Using only standard Internet security protocols, Tivoli Web Services Analyzer extends thereach of Tivoli management expertise outside of the firewall. No additional firewall portshave to be opened to transfer data. The information generated by Tivoli Web ServicesAnalyzer provides you with a deeper understanding of both your users’ Web experiences andthe performance of your e-business. As a result, you can accurately evaluate trends andmake proactive decisions on managing your e-business infrastructure.

Tivoli Web Services Analyzer includes the following components:

¶ Internet Management Server — Maintains the log file collection schedule and sendsperformance and availability data to the Web Services Courier.

¶ Web Services Courier — Retrieves Web server log files and new availability andperformance data from the Internet Management Server.

¶ Web Data Warehouse — Stores all of the Tivoli Web Services Analyzer data processedby Tivoli Decision Support for analysis and reporting.

What’s in This GuideThis guide details the features of Tivoli Web Services Analyzer, version 1.7. The purpose ofthe guide is to deliver all of the information you need to gain the utmost benefit from thisproduct. The guide provides a variety of user scenarios for each of the applications, followedby detailed procedures for using the applications and administering the Tivoli InternetManagement Server. The new browser-based graphical user interface (GUI) is alsodescribed. The guide provides information on using the Tivoli Web Services Analyzer onlinehelp system and contains an index and glossary.

Who Should Read This GuideThe target audience for this guide is system and Web administrators. The guide assumes thatreaders are familiar with maintaining operating systems, administering Web servers,maintaining databases, and general information technology (IT) procedures. Specifically,users of the guide should have some knowledge of the following software:

¶ Solaris, NT, and AIX operating systems

¶ Web servers and Internet protocols such as HTTP and TCP/IP; for secure Web servers,you must also be familiar with digital certificates and SSL

¶ Oracle and/or DB2

viiTivoli Web Services Analyzer Version 1.7 User’s Guide

Users of the guide should also have some knowledge of the applications listed in the nextsection if they intend to use the Tivoli Enterprise integration. Tivoli Web Services Analyzerprovides integration with the Tivoli Enterprise Console and Tivoli NetView products, forevent forwarding.

PublicationsThis section lists publications in the Tivoli Web Solutions library and other relateddocuments. It also describes how to access Tivoli publications online, how to order Tivolipublications, and how to make comments on Tivoli publications.

Tivoli Web Solutions LibraryThe following documents are available in the Tivoli Web Solutions library:

¶ Tivoli Web Solutions Installation Guide, GC32-0659

¶ Tivoli Web Services Manager User’s Guide, GC32-0742-00

Provides a variety of user scenarios for each of the Tivoli Web Services Managerapplications, followed by detailed procedures for using the applications. Thebrowser-based graphical user interface (GUI) and help system is also described. Achapter describes how Tivoli Decision Support works with Tivoli Web ServicesManager, if you have installed the Tivoli Web Services Analyzer.

¶ Tivoli Web Services Analyzer User’s Guide, GC32-0743

Provides details on the features of the Tivoli Web Services Analyzer. The book alsoprovides detailed procedures for using the application. The browser-based graphical userinterface (GUI) and help system is also described. A chapter describes how TivoliDecision Support works with Tivoli Web Services Analyzer.

¶ Tivoli Web Component Manager User’s Guide, GC32-0734

¶ Tivoli Web Services Manager/Tivoli Web Services Analyzer Release Notes, GI11-0775

The release notes provide the most up-to-date information about known defects and theirworkarounds. Be sure to read this document before installing and using these products.

¶ Tivoli Web Component Manager Release Notes, GI11-0853

The release notes provide the most up-to-date information about known defects and theirworkarounds. Be sure to read this document before installing and using this product.

The documents that comprise the Tivoli Web Solutions Library are updated from time totime as necessary. Users should check the Tivoli Customer Support Web site for the latestversions of the documents.

Accessing Publications OnlineYou can access many Tivoli publications online at the Tivoli Customer Support Web site athttp://www.tivoli.com/support/documents

These publications are available in PDF or HTML format, or both. Translated documents arealso available for some products.

Ordering PublicationsYou can order many Tivoli publications online at the following Web site:

http://www.ibm.com/shop/publications/order

Preface

viii

http://www.tivoli.com/support

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

http://www.ibm.com/shop/publications/order

You can also order by telephone by calling one of these numbers:

¶ In the United States: 800-879-2755

¶ In Canada: 800-426-4968

¶ In other countries, for a list of telephone numbers, see the following Web site:

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

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:

¶ Send an e-mail to [email protected].

¶ Complete our customer feedback survey at the following Web site:

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

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact Tivoli Customer Support.See the Tivoli Customer Support Handbook at the following Web site:

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

The handbook provides information about how to contact Tivoli Customer Support,depending on the severity of your problem, and the following information:

¶ Registration and eligibility

¶ Telephone numbers and e-mail addresses, depending on the country you are in

¶ What information you should gather before contacting support

Conventions Used in This BookThis book uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

Typeface ConventionsThe following typeface conventions are used in this book:

Bold Commands, keywords, file names, authorization roles, URLs, or otherinformation that you must use literally appear like this, in bold type.

Names of windows, dialogs, and other controls also appear like this, in boldtype.

Italic Variables and values that you must provide appear like this, in italic type.

Words and phrases that are emphasized also appear like this, in italic type.

Monospace Code examples, output, and system messages appear like this, inmonospace type.

Preface

ixTivoli Web Services Analyzer Version 1.7 User’s Guide

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

[email protected]

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

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

Preface

x

Tivoli Web Services Analyzer Overview

The following sections provide you with information about what Tivoli Web ServicesAnalyzer is, and how to set up your Web servers to log necessary data.

What is Tivoli Web Services Analyzer?Tivoli Web Services Analyzer is a tool that allows IT managers to analyze their Web siteusage, to better manage their resources.

Tivoli Web Services Analyzer gathers log files from Web servers, processes that informationinto a useful format, and places it into a data warehouse. This data warehouse can then beused by Tivoli Decision Support to create different views of the data, from which you cancreate reports using the Tivoli Decision Support Guide for Web Services Analyzer.

The work flow associated with Web analysis using Tivoli Web Services Analyzer and TivoliDecision Support is as follows:

1. Configure your Web servers to log their Web traffic, and rotate their Web log files on atimely basis.

2. Schedule Tivoli Web Services Analyzer to collect the Web log files that have beenrotated.

3. Using Tivoli Discovery Administrator, build “cubes” from the data collected by TivoliWeb Services Analyzer. Cubes, also called multidimensional cubes, are the datacontainers used by Tivoli Decision Support to generate multidimensional views of yourdata.

4. View the cube data with the Tivoli Discovery Interface.

Tivoli Web Services Analyzer allows you to correlate the transaction data from Web log fileswith availability and performance data from Tivoli Web Services Manager. By combiningusage statistics with customers’ quality of experience statistics, you gain a deeperunderstanding of your e-business health. The following graphic illustrates how data flows

1

1Tivoli Web Services Analyzer Version 1.7 User’s Guide

1.Tivo

liW

ebS

ervicesA

nalyzer

Overview

through this system.

DataWarehouse

TivoliDecisionSupport

Sta

gin

g

Pro

du

ctio

nhistoricaldata collection

Web ServicesCourier Endpointlog files

log files

TivoliWeb Services

Analyzer

TivoliWeb Services

Manager

Tivoli Web SolutionsGUI

Tivoli Decision SupportGUI

Web Server

historicaldata collection

Internet ManagementServer

Web ServicesAnalyzer

In the illustration above, theWeb Services Courier endpoint gathers Web log data from Webservers, along with data from Tivoli Web Services Manager (if installed), and places it intothe data warehouse. Tivoli Decision Support then processes the information from the Webdata warehouse, along with data from WebSphere Site Analyzer, into multidimensionalcubes. You can then create different views of the cube data using the Tivoli DecisionSupport Guide for Web Services Analyzer.

How are Log Files Collected?Web servers must be configured such that the log files are accessible to Tivoli Web ServicesAnalyzer through a Uniform Resource Identifier (URI). To do this, you must create a virtuallink to the directory that contains the log files from the last log rotation. To be able to viewthe most current information, the log files should be rotated and collected frequently.

For security, the administrator can allow only certain IP addresses to access the directory.Furthermore, the particular log file or directory should be password-protected.

Configuring Web Server Log FilesThe following sections describe how to set up log files and how to set up rotation schedulesfor successful log file collection by Tivoli Web Services Analyzer.

Overview

2

Configuring Web Log Files for Microsoft Internet Information Server(IIS) Web Servers

To enable Tivoli Web Services Analyzer to collect and process the rolled Web log files, youhave to properly configure the Web server. To configure the IIS Web server for Tivoli WebServices Analyzer, perform the following steps, which are further explained in the sectionsfollowing this list:

1. Configure how the Web server logs its information (page 3).

2. Verify that the log files rotate on a timely basis (page 4).

3. Create an NT user on the Web server. The Tivoli Web Services Analyzer will use thisuser account to log into the Web server to retrieve the log files (page 4).

4. Create a virtual directory that points to the directory where the log files reside (page 4).

5. Set up security for the virtual directory so that it can only be accessed by the WebServices Courier (page 4).

Configure What the Server LogsFor the best results in reports and views within the Tivoli Decision Support Guide for TivoliWeb Services Analyzer, you must configure the Web server to collect the necessaryinformation in the correct format. Complete these steps to configure the Web server:

1. Open the Internet Service Manager.

2. Right click on the Web server whose logging you wish to configure, and selectProperties.

3. Click the Enable Logging checkbox, and choose W3C Extended Log File Formatfrom the pull-down list.

4. Next to the pull-down list, click on the Properties button.

5. Select the General Properties tab and set the New Log Time Period to Daily.Please note that the rotation frequency you choose will determine the schedule for logfile collection you set up using the Tivoli Web Services Analyzer interface. (Forexample, it would not make sense to collect log files on a daily basis when they are onlyrotated once a week.)

Note: Do not select the Unlimited File Size or When File Size Reaches options.

6. Select the Extended Properties tab.

7. To log the necessary Web information for use with Tivoli Web Services Analyzer, selectthe following checkboxes in Extended Logging Options:

¶ Date

¶ Time

¶ Client IP Address

¶ User Name

¶ Method

¶ URI Stem

¶ URI Query

¶ Http Status

Overview


1.Tivo

liW

ebS

ervicesA

nalyzer

Overview

¶ Bytes Sent

¶ User Agent

¶ Referrer

8. Click OK twice to save the settings.

Verify the Time of Log File RotationThe W3C Extended Log File Format log file on your Web server may rotate at eithermidnight GMT or midnight local time. If you have the latest service pack installed, the Weblog file should rotate at midnight local time (the desired behavior). If you have been runningthe Web server with this log file format, you can look at your log files to determine whenthe log file is rotating.

Note that the day and time reported in the log file is in GMT time. Therefore, if the last logfile entries for a given log file are just before midnight and the first log file entries in thenext log file are just after midnight, then the log file is rotating at midnight GMT and mustbe fixed. If the entries indicate that the log file is rotating at some time offset from GMT,the files are being rotated at midnight local time, and nothing else needs to be done. Tocorrect the rotation to local midnight, visit the following Web site:http://support.microsoft.com/support/kb/articles/Q193/6/12.ASP

Create a User Account for the Log File CollectorTivoli Web Services Analyzer must have a user account on the Web server to have access tothe log files for collection. To create a user on the Web server, complete these steps:

1. From the Start menu, click Programs →Administrative Tools (Common) →UserManager for Domains.

2. Select User →New User, and enter the following information in the resulting dialog box:

¶ Username: WSC_USER

¶ Full Name: Web Service Courier User

¶ Description: account for WSC log file retrieval

3. Select the User Cannot Change Password checkbox and Password Never Expirescheckbox.

4. Click the Groups button, and remove the user from all groups.

5. Click Add.

6. Exit User Manager for Domains.

Create a Virtual Directory for the Rotated Log FilesTo create a virtual directory from which the collector can access the rotated log file, performthe following steps:

1. Open the Internet Service Manager.

2. Right click on the Web server for which you are configuring log file retrieval, and selectNew →Virtual Directory. This starts the New Virtual Directory Wizard.

3. Enter an alias for the virtual directory, and click Next.

4. Browse to or enter the path of the directory containing the rotated log files, and clickNext.

Overview

4

http://support.microsoft.com/support/kb/articles/Q193/6/12.ASP

5. Check the boxes next to Allow Read Access and Allow Directory Browsing, and thenclick Finish.

Set Up Security for the Virtual DirectoryTo secure the virtual directory for access only by Tivoli Web Services Analyzer, completethese steps:

1. In the Microsoft Management Console, right click on the virtual directory you createdfor the log file retrieval and click Properties.

2. Select the Directory Security tab.

3. Under the heading Anonymous Access and Authentication Control, click Edit.

4. Place a check in the box next to Basic Authentication, and uncheck any other optionsthat might be checked.

5. A password encryption warning dialog will appear. Click Yes.

6. Click the Edit button next to the Basic Authentication checkbox.

7. Enter or browse to the domain to be used for authentication and click OK twice.

8. Under the heading IP Address and Domain Name Restrictions, click Edit.

9. Select Denied Access, and click the Add button.

10. Enter the IP address of the server that has the Tivoli Web Services Analyzer endpointinstalled on it, and click OK.

11. Click OK on the Domain Name Restrictions dialog and the Properties dialog to closethem.

Configuring Web Log Files for Apache Web Servers on SolarisFor Tivoli Web Services Analyzer to process Apache log files, you must properly configurethe Apache server. The basic steps are as follows:

1. Configure your Web server’s logging so that it writes everything needed for TivoliDecision Support reporting to its log files. Refer to the list in step 7 on page 3.

2. Create a virtual directory that points to the directory containing your rotated log files.

3. Set up security for the virtual directory so that it can only be accessed from the TivoliWeb Services Analyzer endpoint, and so that any attempt to access it requires logging in.

Refer to the following sections for explicit instructions on the steps above.

Configure the Apache Log FileFor the best results in reports and views within the Tivoli Decision Support Guide for TivoliWeb Services Analyzer, you must configure the Web server to collect the necessaryinformation in the correct format. Complete these steps to configure the Web server:

1. Add something similar to the following to Apache’s httpd.conf file:

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combinedCustomLog logs/access.log combined

This will cause Apache to create a log file called access.log in the logs directory, whichcontains all of the fields needed for Tivoli Decision Support reporting.

Overview


1.Tivo

liW

ebS

ervicesA

nalyzer

Overview

2. Create a mechanism that rotates log files and moves rotated log files from the default logdirectory to a directory of your choice.

3. The Tivoli Web Services Analyzer requires that rotated log files are stored in a directorydifferent from that of the active log file. So, whatever means you are using to rotate logfiles should place the old log files in a different directory from the active log file.

4. Use Apache’s htpasswd utility to create a password file, and add a user that can retrievelog files from the Web server. The htpasswd command can be found in Apache’s bindirectory.

For example, to create a password file called apache_pw, and add the user “wsc_user”, enterthis command:

htpasswd -c <$INSTALL_DIR>/apache_pw wsc_user

where <$INSTALL_DIR> is the directory where your Apache Web server is installed.When prompted, enter a password and confirm it by entering it again.

Create a Virtual DirectoryCreate a virtual directory that points to the directory containing your rotated log files byperforming the following steps:

1. Add something similar to the following to Apache’s httpd.conf file:

Alias /logs/ "<$INSTALL_DIR>/Apache Group/Apache/rotated_logs/"

where <$INSTALL_DIR> is the directory where your Apache Web server is installed.

2. After adding this line and restarting Apache, you should be able to go tohttp://yourWebserver/logs/, and see a list of the files contained in<$INSTALL_DIR>/Apache Group/Apache/rotated_logs/.

Set Up Security for the Virtual DirectoryOnce you have created a virtual directory for the Web log files, you will have to set upaccess and security for it. To set up access to it, you will need to configure the Web serverto generate an “index” of the files in the rotated_logs directory. Next, you should configurethe Web server to restrict virtual directory access to the IP address of the machine on whichyou have installed Tivoli Web Services Analyzer. Then, you need to configure the Webserver to require logging in to access the contents of the virtual directory.

Add something similar to the following to Apache’s httpd.conf file:

<Directory "<$INSTALL_DIR>/Apache Group/Apache/rotated_logs/">

Options Indexesorder deny,allowdeny from allallow from XXX.XXX.XXX.XXXAuthType BasicAuthName logsAuthUserFile <$INSTALL_DIR>/apache_pwrequire user wsc_user</Directory>

where <$INSTALL_DIR> is the directory where your Apache Web server is installed.

Overview

6

You should change apache_pw to the name of the password file you created earlier.

UNIX Platforms Only: Apache Web Log File RotationFor Tivoli Web Services Analyzer to be able to collect Web log files from an Apache Webserver on a Solaris system, you must enable Web log file rotation, and copy the rotated fileto a directory where TivoliWeb Services Analyzer can access it.

The following procedure shows one way to enable Web log file rotation and copy the rotatedfile to a valid directory:

1. Enable server Web log file rotation by using the Apache utility. rotatelogs, located inthis directory:

src/support/directory

2. Add the following line to the httpd.conf file to activate log rotation:

TransferLog "| /path/to/rotatelogs/path/to/logs/logname time"where:/path/to/rotatelogs = path where rotatelogs is located/path/to/logs/logname = full path of log file that needs to be rotatedtime = time interval between log rotations, in seconds

After each rotation, the logname is saved in format logname.timestamp and a new lognameis created.

3. The following is an example of a script that copies rotated logs to a different directory:

#! /bin/sh -xSAVE_FILE=.lastlogcopiedFILE_PATTERN=access_logSRC_DIR=.DEST_DIR=../logsoutLAST_FILE_COPIED=vcat $SAVE_FILEvfor FILE in vls $FILE_PATTERN*vdoif [[ $FILE > $LAST_FILE_COPIED ]]thencp -p $FILE $DEST_DIRecho $FILE > $SAVE_FILE

fidone

Use the crontab utility to schedule this script to run automatically.

Configuring Web Log Files for NES/iPlanet Web ServersFor Tivoli Web Services Analyzer to process NES/iPlanet log files, you must properlyconfigure the NES/iPlanet server. There are two methods of accomplishing this task:

¶ The first method involves enabling indexing on your Web server.

¶ The second method involves creating another Web server instance on a different portsolely for the purpose of retrieving log files, and indexing only this Web server. Thisrequires opening a new port in any firewalls between the Web Services Courier and theWeb server from which it is attempting to collect Web log files. The benefit is that youdo not have to enable indexing on your Web site server.

Overview


1.Tivo

liW

ebS

ervicesA

nalyzer

Overview

If you are willing to enable indexing on your Web site, the basic steps are:

1. Configure your Web server’s logging so that it writes everything needed for TivoliDecision Support reporting to its log files.

2. Configure the rotation of the Web log files and create a mechanism that moves therotated log files from the default log directory to a directory of your choice.

3. Create a virtual directory that points to the directory containing your rotated log files.

4. Set up security for the virtual directory so that it can only be accessed from the TivoliWeb Services Analyzer endpoint, and so that any attempt to access it requires logging in.

Refer to the following sections for explicit instructions on the steps above.

Configure What the Server Logs:For the best results in reports and views within the Tivoli Decision Support Guide for TivoliWeb Services Analyzer, you must configure the Web server to collect the necessaryinformation in the correct format. Complete these steps to configure the Web server:

1. Access the NES/iPlanet Administration Server through your Web browser.

2. Select the Web server to configure.

3. Click on the Server Status tab, and then on Log Preferences in the left-hand side of thenavigation window.

4. Under Format, select Only Log, and select the following check boxes:

¶ Client hostname

¶ Authenticate user name

¶ System date

¶ Full request

¶ Status

¶ Content Length

¶ HTTP header, “referrer”

¶ HTTP header, ″user-agent″

5. Click OK.

Configuring the Rotation of the Log FilesYou must configure the Web server to generate an “index” of the files in the rotated_logsdirectory.

1. Click on the Server Status tab, and then on Archive Log in the left-hand side of thenavigation window.

2. Choose the Internal daemon or cron-based rotation, select a time, and click OK.

3. Create a mechanism to move the active log file(s) to a “rolled log” directory. Note thatyour mechanism for moving the logs should do so after the rotation time.

Create a Virtual DirectoryCreate a virtual directory that points to the rolled log files directory, as follows:

1. Click on the Content Mgmt tab, and click Additional Document Directories in theleft-hand side of the navigation window.

Overview

8

2. Enter a URL prefix (such as “logfiles”) and the full path on the rolled log files directory.

3. For Apply Style, select NONE.

4. Click OK.

Set Up Security for the Virtual DirectoryWhen you have created a virtual directory for the Web log files, you have to set up accessand security for it. You need to configure the Web server to restrict access the virtualdirectory to the IP address of your Tivoli Web Services Analyzer. Then, you must configurethe Web server to require logging in to access the contents of the virtual directory.

Overview


1.Tivo

liW

ebS

ervicesA

nalyzer

Overview

GUI Overview and Navigation

The Tivoli Web Services Manager graphical user interface (GUI) is the interface you use tomanage your Tivoli Web Services Manager implementation. The GUI is the main windowinto the Tivoli Web Services Manager services and applications.

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

Tivoli Web Services Manager’s management information and applications are displayed andaccessible from a drop-down list of applications. An expandable navigation tree enables youto access and run the applications, view information, and perform system administrationtasks. The GUI’s design makes it easy to learn and easy to use. There is a commonparadigm for accomplishing tasks used throughout the console. After you have learned thesteps for accomplishing one task, other tasks are easier to learn and perform.

The GUI is the Tivoli Web Services Manager desktop; it is the user interface on which youperform basic system operations. The GUI displays and organizes the resources, jobs, events,and reports of the different Tivoli Web Services Manager applications.

Starting the GUIYou can start the GUI from any location, as long as you have HTTP or HTTPS access. Youcan view the GUI through a Netscape Navigator or Microsoft Internet Explorer browser.

Note: Before accessing a Tivoli Internet Management server, be sure your browser isconfigured to accept cookies. Refer to your browser’s help system for procedures toenable cookies.

To start the Tivoli Web Services Manager GUI, complete the following steps.

1. Start a browser.

2. Enter the URL and port number for the management server in your browser’s Locationor Address bar. Use the following syntax:

http(s)://<management server name>.<domain name>:<port>/

The GUI is displayed.

2


2.G

UI

Overview

and

Navig

ation

Areas of the GUIThe GUI is divided into three main parts: the Portfolio (or navigation tree), the banner, andthe work area.

Work Area

GMT OffsetHelp

Button

Portfolio

Navigation Tree

Banner

Logoff

Application DropDown

The left side of the GUI is the Portfolio. The Portfolio contains a drop-down box with linksto each of the Tivoli Web Solutions products: Tivoli Web Services Manager, Tivoli WebServices Analyzer, Tivoli Web Component Manager, and links to General Tasks, which areproduct-independent or administrative activities. When you first log in to Tivoli WebServices Manager, the Portfolio view shows the unexpanded navigation tree for Tivoli WebServices Manager.

To expand the tree and view the functions available for a product, select the product fromthe application drop-down box. An expandable list of options indicated by arrow icons to theleft of a selection is displayed. When you click a selection from the expanded list in thePortfolio, the contents of the work area changes to reflect your selection. Note also that asyou move your mouse over the choices in the Portfolio, a short definition of the choice isdisplayed in your browser’s status bar at the bottom of the GUI.

To expand the tree and view choices pertaining to Tivoli Web Services Manager, click TivoliWeb Services Manager in the application drop-down list.

To expand the tree and view choices pertaining to Tivoli Web Services Analyzer, click TivoliWeb Services Analyzer in the application drop-down list.

To expand the tree and view choices pertaining to Tivoli Web Component Manager, clickTivoli Web Component Manager in the application drop-down list.


12

To expand the tree and view the choices pertaining to system administration activities andproduct-independent functions such as viewing logs and setting user preferences, clickGeneral Tasks in the application drop-down list.

To log off the Internet Management Server, click Logoff, which is located at the top-leftcorner of the Portfolio.

Greenwich Mean Time OffsetThe Portfolio area contains a Greenwich Mean Time (GMT) offset. The GMT offsetindicates the difference between GMT and the local time of the browser. All job schedulingis done in Greenwich Mean Time (GMT); refer to the GMT offset to schedule jobs with thecorrect GMT offset for your locale.

Help ButtonThe question mark icon in the upper-right corner of the work area is the Help button. Thehelp system provides overview and context-sensitive information to assist you while youperform Tivoli Web Services Manager tasks or management activities. If you click the Helpbutton before you have opened any of the applications, the help system’s table of contents isdisplayed. If you click the Help button while you are in an application or performingadministrative tasks, context-sensitive information is displayed.

Work AreaThe work area is where you perform all of the Tivoli Web Services Manager tasks. Theactivities you perform in the work area include:

¶ creating and scheduling application jobs

¶ configuring events and creating event responses

¶ examining job and event logs

¶ viewing reports

NavigationWhen you open one of the applications to create or edit a job, a set of tabs is displayedacross the top of the work area. The tabs identify the subtasks that make up the applicationtask. You can move from one subtask to another by clicking on the tabs. You can use thetabs to go back to review a subtask you have completed. A check mark (U) appears on atab when the options for that tab are valid entries for scheduling a job. In addition tonavigation using the tabs, application subtask views contain a Next button that, whenclicked, moves you to the next subtask.

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



2.G

UI

Overview

and

Navig

ation

Now that you are familiar with the Tivoli Web Services Manager GUI and its operationalconcepts, you are ready to examine the applications. If you plan to immediately beginconfiguring jobs in the applications, you should first configure events and event responses.For information on how the event system operates, see “Managing Events and EventResponses” on page 21.

Note: The contents of the Portfolio area vary depending on the authorization granted toyour user ID. In general, only the Portfolio tasks for which you have authorizationappear in the Portfolio view. Authorization is described in “Manage Accounts” onpage 60.


14

Using the Scheduler for Web Log FileCollection

Before Tivoli Web Services Analyzer can collect Web log files from your Web servers, youhave to tell it when to do so and where to find the Web log files.

To complete the steps in this chapter, you must log into the browser console. Complete thesesteps to do so:

1. Start up a Web browser and enter the domain name of the computer where you haveinstalled the Management Server.

2. Log on by entering a valid user ID and password. The default value for both is adminwhen you first access the console after installation.

The following sections describe how to create and manage Tivoli Web Services Analyzerjobs.

Creating a Job to Collect Web LogsTo make use of Web log data with the Tivoli Decision Support Guide for Web ServiceAnalyzer, you must first collect the logs and transfer their data to the Tivoli Web DataWarehouse.

Use the browser console to create Web log file collection jobs as detailed in the followingsteps:

1. In the Portfolio, choose Tivoli Web Services Analyzer from the drop down list ofinstalled applications.

2. Click Create Data Collection Job.

3. From the drop-down list in the workspace, choose the Web Services Courier endpointfor which you wish to create this job, and click Next.

Note: All schedule times are Greenwich Mean Time (GMT).

4. If you have created and named a job with a schedule that you would like to use again,choose it from the Existing Configurations drop-down list and click Populate. Thisautomatically populates the rest of the fields on the page, which you can then modify ifyou choose. Click Next to continue with parameter configuration (skip to step 5).

If you would rather create a schedule from scratch, perform the following steps:

a. If you want the job to start immediately, select Start the job immediately.Otherwise, select Start the job later at, and choose the start date and time usingthe drop-down lists. Please note that jobs start or stop on the quarters of the hour.

3


3.U

sing

the

Sch

edu

lerfo

rW

ebL

og

File

Co

llection

b. To run a job repeatedly, select Run job every, enter a value, and choose the unit ofmeasure from the drop-down list. Otherwise, choose Run job once.

Note: To repeat a job with a frequency of less than once a week, enter the numberof hours that make up that period. For example, if you want a job to repeatevery 10 days, you would enter 240 hours (10 days x 24 hours).

c. If you want the job to repeat continuously at the indicated frequency until the jobterminates, select Continuously.

d. If you want the job to repeat only during certain hours, on certain days, selectBetween hours of and use the drop-down lists to specify the day and times duringwhich you want the job to run.

e. If you want the job to never terminate, select Never terminate the job. Otherwise,select Terminate the job at, and use the drop-down lists to select the date and timeyou want the job to terminate.

f. Click Next to continue to the parameter configuration page.

5. Configure the parameters.

a. If you have created and named a job with a set of parameters that you would like touse again, choose it from the drop-down list and click Apply. This automaticallypopulates the rest of the fields on the page, which you can then modify if youchoose.

b. Enter the hostname of the Web server in the Server Host Name field.

c. Enter the IP address of the Web server in the Server IP Address field.

d. Enter the hardware platform of the Web server in the Server Hardware Platformfield.

e. From the Server Operating System drop-down list, select the operating system(OS) of the Web server for which this job is being created. If the operating systemis not included in the list, type it into the field labeled Other next to the drop-downlist.

f. From the Web Server Software drop-down list, select the type of Web server forwhich this job is being created. If the Web server software is not included in the list,enter it into the field labeled Other next to the drop-down list.

g. Enter the logical server cluster of the Web server in the Logical Server Clusterfield.

h. Enter the server cluster domain name of the Web server in the Server ClusterDomain Name field.

i. In the Log File URI field, type in the URI of the Web log file that this job is tocollect. An example URI might look like the following:https://mysite/logs/

j. From the Log File Descriptor drop-down list, select the type of log file descriptorfor which this job is being created. If the log file descriptor of the Web server is notin the list, type it into the Custom field next to the drop-down list.

k. If the Web server requires a user name to access the Web log files, type it into theUsername field.

Using the Scheduler

16

l. If the Web server requires a password to access the Web log files, type it into thePassword field.

m. Click Next to name the job.

6. Assign a name to the job.

a. Enter a unique name for the job in the Job field.

b. Enter a description of the job in the Description field.

c. Click Save to complete scheduling the data collection job. This will register theschedule with the Internet Management Server.

7. In the menu tree on the left, click Historical Data Collection.

8. Under Historical Data Collection, click Configure Stage to Production.

9. From the drop-down list, select a Web Services Courier endpoint.

10. Using the drop-down lists under Begin Collection, select a time for the collection tobegin. The time is Greenwich Mean Time (GMT).

Note: You must schedule the historical data collection time to start after the lastscheduled Web log file collection job begins. For example, if the last scheduledWeb log file collection begins at 3 a.m., you should schedule the historical datacollection for 3:15 a.m. or later. Although it appears that the jobs will overlap,the historical data collection job does not start until all Web log collection jobshave completed.

11. Make sure that the Disable checkbox is not checked. If the box is checked, thehistorical data collection job will not run, and the Web log file data will not be madeavailable for Tivoli Decision Support.

12. Click Save.

13. Restart the Web Services Courier endpoint.

Note: When you create or otherwise alter an historical data collection, this change is notregistered with the endpoint until you restart the endpoint. This also means that if youdecide to move the collection task from one collection endpoint to another, you mustrestart both of them to register the change with each endpoint.

Editing a JobTo edit a job, perform the following steps:

1. In the Portfolio under Tivoli Web Services Analyzer, click Edit Data Collection Job.

2. Select a job from the job list by clicking the radio button to its left.

3. Click the Next button.

4. Select the endpoint on which you want this edited job to run, and click Next.

5. Using the Edit WSA Job tabs at the top of the window, select the aspect of the job youwish to edit, such as the schedule or constraints.

6. From the drop-down list on each aspect that you wish to edit, make sure the job name ofthe job you are wanting to edit is selected, and then click Populate.

Using the Scheduler


3.U

sing

the

Sch

edu

lerfo

rW

ebL

og

File

Co

llection

7. Make any changes to the settings, and click Next, or if this is the only change you wantto make, click the Save tab at the top of the window.

8. Verify that the name displayed in the job name field is the same as the one you areediting, then click Save.

9. Click OK to save the edited job under the old job name, or click Cancel to save the jobunder a new name. A confirmation message will display once the job is savedsuccessfully.

Managing JobsYou can view the status of all scheduled jobs through the Manage Jobs function. The joblog displays the job name, what kind of job it is, what its current state is, and whichendpoint it is on.

By clicking the radio buttons labeled Show scheduled jobs and Show complete andincomplete jobs, you can toggle the list between those jobs that are scheduled (yet to run orare running), those that are incomplete (failed or unscheduled), and those that are complete(ran successfully).

You can also delete jobs using this interface using the following procedure:

1. While viewing the list of jobs, select the jobs to delete by clicking the box to the left ofthe job name.

2. Verify that the jobs you have selected are the ones you wish to delete, removing thecheck from any that you wish to keep.

3. Click Delete checked jobs.

Unscheduling a JobYou can unschedule jobs using the following procedure:

1. While viewing the list of scheduled jobs, select the jobs to unschedule by clicking thebox to the left of the job name.

2. Verify that the jobs you have selected are the ones you wish to unschedule, removing thecheck from any that you wish to keep.

3. Click Unschedule checked jobs.

Deleting a JobOnce a job has been unscheduled, you can delete the job using the following procedure:

1. While viewing the list of complete and incomplete jobs, select the jobs to delete byclicking the box to the left of the job name.

2. Verify that the jobs you have selected are the ones you wish to delete, removing thecheck from any that you wish to keep.

3. Click Delete checked jobs.

Using the Scheduler

18

Configuring Web Services Analyzer EventsTivoli Web Services Analyzer can generate a WSA Task Status system event any time thereis task activity. You can specify the severity, or importance, of this event type. The severitylevels of this event correspond to Tivoli Enterprise Console (TEC) events as follows:

Event Number Definition

10 Unknown

20 Harmless

30 Warning

40 Error

50 Critical

60 Fatal

When you specify a severity level to an event, you also assign an event response (which isconfigured in the System Administration area of the GUI). The event response is the actionthat occurs when the particular event is generated, such as sending notification to an e-mailaddress or forwarding the event to the Tivoli Enterprise Console (TEC).

The severity level associated with the event will trigger any event responses associated withlower severity levels. For example, the default event response for all Web Services Analyzerevents is to log them. If you configure an event with a severity of Critical and assign aresponse that causes an e-mail notification to be sent to the Information Services manager,the event will also be logged. If any other severity levels lower than Critical have beenassigned, the responses associated with them will occur as well.

To configure a Tivoli Web Services Analyzer event:1. From the Portfolio, click Tivoli Web Services Analyzer, then click Configure Events.

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

3. Select an event response from the Event Response drop-down list. If the desiredresponse is not on the list, see “Creating Event Responses” on page 22.

4. Click Add to Table. The Event Table displays Tivoli Web Services Analyzer eventtypes. Using the radio buttons below the table, you can display all Tivoli Web ServicesAnalyzer event types or only a selected event type. When you are satisfied with theevent configuration, return to the main browser.

Examining the Web Services Analyzer Event LogEvents for the Tivoli Web Services Analyzer are stored in the management repository anddisplayed in the application’s event log. They are also displayed on the global event log,which is viewable from the System Administration portion of the GUI. You can use theTivoli Web Services Analyzer log to view a list of only the most recent events generated bythe Tivoli Web Services Analyzer. This is a real-time log of events. To view the Tivoli WebServices Analyzer event log from the Portfolio, click Tivoli Web Services Analyzer, thenclick Examine Event Log.

Using the Scheduler


3.U

sing

the

Sch

edu

lerfo

rW

ebL

og

File

Co

llection

Tivoli Web Data WarehouseThe Tivoli Web Services Analyzer data warehouse is the centralized repository for datacollected or generated by Tivoli Web Services Manager and Tivoli Web Services Analyzer.The Tivoli Decision Support Guides for Tivoli Web Services Analyzer and Tivoli WebServices Manager create reports from the data in this warehouse.

Restart and Recovery of the Web Data WarehouseTo restart and recover data entry into the Web data warehouse, there are two approaches:

¶ Wait until the next scheduled collection runs; each time the collection runs, the datawarehouse is reset.

¶ Create a new schedule to run a log file collection immediately, and allow it to run.

Using the Scheduler

20

Managing Events and Event Responses

Tivoli Web Services Analyzer and the Internet Management Server generate events. An eventcan be any warning, error message, or status message. Application events are typicallygenerated when application constraints are exceeded, which usually occurs during theexecution of a job. System events are typically generated by authentication problems, eventhandler failures, or endpoint communication problems. The events generated by Tivoli WebServices Analyzer are stored in the management repository.

An event response is the preconfigured action that is initiated when an event is generated.There are five response options that can be configured for any event. These options enableyou to forward each event to one or more of the following destinations using one of theevent handlers on the management server:

¶ System event log, through the log handler

¶ One of more e-mail addresses, through the Simple Mail Transfer Protocol (SMTP)handler

¶ Scripts that initiate an action, such as a remedial response to an event, through theEXEC handler

By forwarding events, you can ensure that the appropriate people are notified of each typeof event.

Each application, and the management server, has a unique set of event types. You canconfigure any event by assigning a severity (priority) level and an event response. There aresix event severity levels:

¶ Unknown

¶ Harmless

¶ Warning

¶ Error

¶ Critical

¶ Fatal

By default, all application events are assigned a severity level of warning and are logged(the event response). System events are also logged, by default. However, the severity levelsfor system events are hard-coded (as shown in the following table) and cannot be altered.

Event Type Severity Level

Endpoint Uninstalled Error

Heartbeat Missing Unknown

4


4.M

anag

ing

Even

tsan

dE

vent

Resp

on

ses

Event Type Severity Level

Authorization Failure Warning; Error

Authorization Service Succeeded Harmless

Authorization Service Failed Error; Fatal

Server Authentication Failed Critical

Mail Service Failed Critical

Mail Service Failed Critical

SNMP Service Failed Critical

TEC Service Failed Critical

EXEC Service Failed Critical

Endpoint Installed Harmless

EXEC Status Failed The priority of the original event received.

EXEC Failed The priority of the original event received.

Unknown Endpoint Not used

Event Forwarded to TEC Missing Data The priority of the original event received.

EXEC Complete The priority of the original event received.

Generic Event Not used

TESM Service Failed Critical

Event subsystem exception The priority of the original event received.

An endpoint has started the auto-update process Error

An endpoint auto-update process has completedsuccessfully

Error

An endpoint auto-update process has failed dueto an error

Error

Recovery: Heartbeat no longer missing fromendpoint

Error

You should configure event responses before you configure events and you should completeboth tasks before you begin using Tivoli Web Services Analyzer. Configuring eventresponses first makes all the response options available when you configure the events.Configuring events before you begin creating jobs with the applications ensures that you willnot lose any event information when the jobs begin to run.

Creating Event ResponsesYou should configure event responses before you configure events and you should completeboth activities before you begin using Tivoli Web Services Analyzer applications.Configuring event responses first makes all the response options available when youconfigure the events. Configuring events before you begin creating jobs with the applicationsensures that you will not lose any event information when the jobs begin to run.

The five event response types are configured in different ways:

¶ Sending event information to the application and system logs is the default. All eventsare logged; no further configuration is required for this action.


22

¶ Forwarding events to the Tivoli Enterprise Console or to SNMP applications is done byconfiguring the management server.

¶ Forwarding events to e-mail accounts and to the EXEC handler is done through theCreate Event Responses view under General Tasks → System Administration.However, the e-mail option requires that you also configure the management server first.

When you have configured the TEC and SNMP event response options on the managementserver, they appear as choices in the Event Response drop-down list on the application andsystem event configuration views. The e-mail option is displayed after you configure themanagement server and create an e-mail event response. The EXEC option is displayed afteryou create a script execution event response.

Forwarding Events to the Tivoli Enterprise ConsoleYou can configure events to be forwarded to the Tivoli Enterprise Console (TEC). The TECevent handler translates an event from Internet Management Server format to TEC format.The formatted event is queued on the management server. The Tivoli Web Services Courierendpoint polls the management server every 60 seconds for TEC events. Whenever there areany in the queue, they are forwarded to TEC.

In order for the Internet Management Server to forward events to a TEC server, you mustinstall the Tivoli Web Services Courier (WSC) endpoint according to the instructions in yourinstallation guide.

To configure system events for TEC forwarding, complete the following steps:

1. On the Portfolio, click General Tasks → System Administration → Configure SystemEvents.

2. For each event type that you want forwarded to an TEC application:

a. Click the arrow on the right of the Event Type drop-down list. Select an event type.

b. Click the arrow on the right of the Event Severity drop-down list. Select an eventseverity.

c. Click the arrow on the right of the Event Response drop-down list. Select TECForwarding.

3. Continue this procedure until you have configured all TEC forwarding events.



4.M

anag

ing

Even

tsan

dE

vent

Resp

on

ses

Forwarding Events to an SNMP Management ApplicationYou can configure events to be forwarded to a Simple Network Management Protocol(SNMP) management application such as Tivoli NetView. The SNMP handler creates amessage from event data, then creates and sends an SNMP trap.

To forward Tivoli Web Services Analyzer events to an SNMP management application, youmust have an SNMP management application installed. Tivoli recommends that you contactthat application’s administrator before forwarding events to the SNMP managementapplication. You must also configure the management server for SNMP forwarding beforeconfiguring events.

To configure system events to be forwarded to an SNMP management application, completethe following steps from the Tivoli Web Services Analyzer GUI.


2. For each event type that you want forwarded to an SNMP application:

a. Click the arrow on the right of the Event Type drop-down list. Select an event type.

b. Click the arrow on the right of the Event Severity drop-down list. Select an eventseverity.

c. Click the arrow on the right of the Event Response drop-down list. Select SNMPTrap.

Forwarding Events to an E-mail AccountYou can configure the event service to forward events to one or more e-mail addresses,using the Simple Mail Transfer Protocol (SMTP) handler. Use the SMTP forwarding featureto ensure that the appropriate individuals are notified for each type of event generated.Automatic e-mail notification is a simple and efficient way to communicate that an issueneeds to be addressed. The e-mail forwarding option also forwards notification to pagers andhand-held devices if the receiving devices are configured properly

You can forward event notification via e-mail to individuals or groups. To forward all eventsof a particular type to e-mail addresses, complete the following steps from the Tivoli WebServices Analyzer GUI:

1. Click General Tasks → System Administration → Create Event Responses.


24

2. Select Send E-mail from the event response type from the drop-down list. Click Next.

3. To create a new recipient, enter a name and description (optional). The name can be of asingle individual, or it can be the name of a group of individuals who will each receivenotification of the event. Enter an address and click Add. Repeat the process until youhave entered all the necessary recipients. Click Create/Modify.

4. To modify an existing e-mail event response:

a. Select the e-mail response name from the drop-down list on the Create E-mailEvent Response view.

b. Click Populate to view the details.

c. Modify the response:

1) Select existing entries and remove them by clicking Remove- OR -

2) Add new entries and click Add.

d. When you have finished, click Create/Modify to change the response.

All new events of the specified type are sent to the e-mail addresses specified.

Forwarding Events to the EXEC ServiceYou can configure the event service to forward events to the EXEC service where receipt ofthe event runs one or more user-created programs. You can use the EXEC forwarding featureto initiate remedial actions instead of, or in addition to, human intervention.

To forward all events of a particular type to the EXEC service, complete the following steps:

1. From the Portfolio, click General Tasks → System Administration → Create EventResponses.

2. Select Run a Script from the Event Response Type from the drop-down list. ClickNext.

3. To create a new response:



4.M

anag

ing

Even

tsan

dE

vent

Resp

on

ses

a. Enter a name (required) and description (optional).

b. Provide the command path, error path, and output path for the script you want to run.

c. Click Create/Modify.

4. To modify an existing script execution event response:

a. Select the script response name from the drop-down list on the Create ScriptExecution Event Response view.

b. Click Populate to view the details.

c. Modify the response by selecting entries and removing them by clicking Remove orby adding new entries and clicking Add.

d. When you have finished, click Create/Modify to change the response.

All new events of the specified type will initiate the specified script.

Forwarding Event Data Using the EXEC ServiceThe EXEC service passes event field value data to the executing program or script you haveconfigured via command line arguments. The arguments use a name-value pair format, inwhich the value is always enclosed in double quotes. The syntax is shown in the followingtable.

Command Argument Syntax

1 event_id=”event_id_value”

2 event_priority=”event_priority_value”

3 endpointID=”endpointID_value”

4 endpointName=”endpointName_value”

5 eventSource=”eventSource_value”

6 eventTime=”eventTime_value”

7 recordID=”recordID_value”


26

Command Argument Syntax

8 constraintID=”constraintID_value”

9 annotation=”annotation_value”

The syntax works on the Unix platform and most environments on NT. However, if youcreate a *.cmd or *.bat script, NT’s cmd.exe will not receive the arguments properly andwill only return the name portion of the pair. To remedy this, use the pattern in thefollowing example script:@echo offecho Example Script!echo Param 1 = %1echo Param 2 = %2echo Param 3 = %3echo Param 4 = %4echo Param 5 = %5echo Param 6 = %6echo Param 7 = %7echo Param 8 = %8echo Param 9 = %9shift /8echo Param 10 = %9shift /8echo Param 11 = %9shift /8echo Param 12 = %9shift /8echo Param 13 = %9shift /8echo Param 14 = %9shift /8echo Param 15 = %9shift /8echo Param 16 = %9shift /8echo Param 17 = %9shift /8echo Param 18 = %9

The output presents the name-value information in a different format:Example ScriptParam 1 = eventIDParam 2 = “<value>”Param 3 = eventPriorityParam 4 = “<value>”Param 5 = endpointIDParam 6 = “<value>”Param 7 = endpointNameParam 8 = “<value>”Param 9 = eventSourceParam 10 = “<value>”Param 11 = eventTimeParam 12 = “<value>”Param 13 = recordIDParam 14 = “<value>”Param 15 = constraintIDParam 16 = “<value>”Param 17 = annotationParam 18 = “<value>”



4.M

anag

ing

Even

tsan

dE

vent

Resp

on

ses

Configuring EventsEach application has a unique set of event types, as does the management server (systemevents). Tables listing all the event types are provided at the end of this chapter in “EventSeverity”.

You can configure any event (with the exception that system event type severity levelscannot be changed) and you can configure each event multiple times. This allows you totailor who is informed or what actions are taken, based on the source or severity (priority) ofthe event. Configuring an event is the process of associating an event type and a severitylevel with an event response. See “Creating Event Responses” on page 22 and “EventSeverity”. The event response will be triggered when an event of the specified type andpriority (or one of a specified type and a higher priority) is received by the managementserver.

To configure a system event, complete the following steps:

1. From the Portfolio, click General Tasks → System Administration → Configure SystemEvents.

2. Select an event type from the Event Type drop-down list.

3. Select an event response from the Event Response drop-down list. If the desiredresponse is not on the list, see “Creating Event Responses” on page 22. Select a severitylevel from the Event Severity drop-down list.

4. Click Add to Table. The Event Table displays system event types. Using the radiobuttons below the table, you can display all system event types or only a selected eventtype. You also have the option of deleting any configured events, except those configuredwith the system defaults. Select the events you wish to delete and click Delete checked.

5. Configuration is applied immediately, so when you have finished configuring, you canmove on to your next task

You can configure events from each application’s Configure Events view by using thisprocedure.

Event SeverityWhen you configure events, you associate a severity, or priority, level for each event type,and an event response. The severity levels are as follows:

¶ Unknown

¶ Harmless

¶ Warning

¶ Error

¶ Critical

¶ Fatal

You can configure a given event type multiple times, each time changing the severity andthe event response. This enables you to generate different responses based on the source andsignificance of the event. An event type, configured multiple times, can generate multipleresponses. For example, if, for a particular event, you assign a severity of Error and an event


28

response of sending an e-mail to yourself, any instance of that event with a severity level ofError causes a notification to be sent to your e-mail address and logs the event, sincelogging is the default response for all events.

An event generates its configured response, the default response, and any other configuredresponses of lower severity for that event type. For example, assume you are using SiteInvestigator to search for outdated content (for example, discontinued products or programs)on your Web site, on both the public pages and the pages under construction. You configurethe Undesired Content Found event twice: once with a severity of Error and a response offorwarding notification to an SNMP application in your lab; the second time with a severityof Critical and a response that sends an e-mail to the Information Services vice-president.

When you create an Site Investigator job to search Web pages under construction, youchoose the event type with Error severity. If an Undesired Content Found event is generated,it is logged (by default) and forwarded to the SNMP application. When you create an SiteInvestigator job to search your public Web site, where undesired content can have moreserious consequences, you choose the event type with Critical severity. In this instance, anUndesired Content Found event results in the following actions:

¶ e-mail notification is sent to the Information Services vice-president

¶ notification is forwarded to your SNMP application

¶ the event is logged.

In both cases, the system generates the configured event response and the default response,plus any other configured responses of lower severity for that event type.

Event TypesThe following tables list and describe the event types for Tivoli Web Services Analyzer andthe management server (system events).

System Event Types

Type Definition

Endpoint Uninstalled An endpoint has been uninstalled.

Heartbeat Missing The heartbeat has been missing from an endpointfor a number of minutes. This event is generatedif the management server has not received aheartbeat signal from the endpoint for a specifiedperiod of time (in minutes).

Authorization Failure The management server failed to authorize aclient request. Events of this type are generatedwhen an invalid password is specified, a userlacks permission to use the requested service, orwhen/if any other authorization request is invalid.

Authorization Service Succeeded The authorization or authentication succeeded.Events of this type are generated, for example,when a user is successfully created or when/if amanagement server is defined.

Authorization Service Failed The authorization or authentication service failed.Events of this type are generated for example,when an invalid password is specified or when/ifan attempt is made to delete a user.



4.M

anag

ing

Even

tsan

dE

vent

Resp

on

ses

System Event Types

Type Definition

Server Authentication Failed Authentication failed while defining a foreignmanagement server (server-to-servercommunication).

Mail Service Failed The STMP service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

SNMP Service Failed The SNMP service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

TEC Service Failed The TEC service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

EXEC Service Failed The EXEC service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

Endpoint Installed A new endpoint has been installed and hasregistered with the management server.

EXEC Status Failed The user-supplied script or program ran andreturned a non-zero (error) status code. Thisevent is generated when the service runs auser-supplied script or program that returns anerror code.

EXEC Failed The user-supplied script or program failed toexecute. This event is generated when the serviceunsuccessfully attempts to run a user-suppliedscript or program.

Unknown Endpoint Unknown endpoint ping. The management serverhas been contacted by an endpoint that is notregistered.

Event Forwarded to TEC Missing Data Certain fields in the event forwarded to TEC aremissing information. This is an internal error.TEC will not reject the error.

EXEC Service User-supplied script or program completedsuccessfully.

Generic Event This is a generic event for general use.

TESM Service Failed The TESM service to start up due to anexception.

Event subsystem exception The subsystem failed to generate. This is aninternal problem. Turn on tracing or contactTivoli Customer Support.


30

System Event Types

Type Definition

An endpoint has started an auto-update process An endpoint has started an auto-update process.



An endpoint auto-update process has failed dueto an error.


Recovery: Heartbeat no longer missing fromendpoint.

Recovery: Heartbeat no longer missing fromendpoint.

Web Services Analyzer Event Types

Type Definition

WSA Task Status The scheduled job has been started, wascompleted, failed, aborted, or was unable to start.



4.M

anag

ing

Even

tsan

dE

vent

Resp

on

ses


32

Managing Data in the ManagementRepository

Certain data in the management repository is expected to collect over time, thereby requiringthat you manage it. This data includes events, management data that is uploaded by TivoliWeb Services Analyzer, and data generated by jobs. However, Tivoli Web Services Analyzerdoes not monitor the management repository for space utilization and thresholds. It is yourresponsibility to monitor the health of the management repository and to regularly purgeevents, unneeded collections, tasks, and so on.

Tivoli Web Services Analyzer provides a utility to perform this maintenance. Theims_purgedb command enables you to delete unwanted or outdated data from themanagement repository. The ims_purgedb command also enables you to view statisticsabout the amount of data stored in the management repository at any one time.

Of course, how often you need to purge data depends on the size of the database. Consultyour database administrator if you are unfamiliar with database maintenance. Failure tomonitor and maintain the management repository could result in the Internet ManagementServer becoming unusable or ineffective because it cannot write to the database.

Usage of the ims_purgedb CommandYou must log in to the machine on which the Internet Management Server is installed to usethe ims_purgedb command. The ims_purgedb command is located in the base_dir/TIMS/bindirectory, where base_dir is the base directory specified when the Tivoli Web ServicesAnalyzer server was installed. You can set the PATH environment variable to include thisdirectory, or you can run the command by specifying its full path.

The general syntax statement for the ims_purgedb command is as follows:

ims_purgedb [–user user_name –passwd password] [ STI ] [ QOSM ] [ SI ] [ TIMS ][WSA] { –stats | –delete [–before ”yyyy-mm-dd hh:MM:SS” ] | -help]

where:

–user user_name Specifies a Tivoli Web Services Analyzer user name. Thecommand uses this name to log in to the Tivoli WebServices Analyzer management server. If you do not specifythis argument, the command prompts you for a user name.

Note that this logon name must be assigned the admin role. Because this command enablesyou to delete potentially important Tivoli Web Services Analyzer data, you must have thisadministrative authority.

5


5.M

anag

ing

Data

inth

eM

anag

emen

tR

epo

sitory

–passwd password Specifies a Tivoli Web Services Analyzer password that isused by the command, along with the user name specified bythe –user argument, to log in to the Tivoli Web ServicesAnalyzer server. If you do not specify this argument, thecommand prompts you for a password.

–help Prints the usage statement of this command to the standardoutput.

–stats Prints the total number of data entries in the managementrepository to standard output. This statistical information isprinted to standard output by default if you do not specifythe –help, –stats, or –delete argument.

–delete [–before “yyyy-mm-dd hh:MM:SS”]Deletes all data in the management repository. The followingoptions are available with the –delete argument:

If you specify the –before argument, data stored in themanagement repository on and before the specified date andtime is purged. You must enclose the date and time in doublequotation marks and the format must be yyyy-mm-ddhh:MM:SS. The year must be a four-digit number and thetime must be specified as military time (Midnight is00:00:00, noon is 12:00:00, and so on).

Refer to the following sections for examples of this command. Each section also lists thesyntax statement for the ims_purgedb command that is specific to the type of data you aredeleting from the management repository.

Deleting DataThe Internet Management Server and applications continually generate events and other data,which are stored in the management repository. Data is generated by GUI operations, byjobs, when constraints are violated, and it is based on information from Tivoli Web ServicesAnalyzer endpoints. The data provides an audit trail that you can use to monitor dailyoperations; however, you might need to purge the data when it becomes outdated.

To delete data from the management repository, use this command:

ims_purgedb [–user user_name –passwd password] [ TIMS] [–help | –stats | –delete[–before “yyyy-mm-dd hh:MM:ss”] ]

Refer to “Usage of the ims_purgedb Command” on page 33 for a description of thearguments.

The following example purges all IMS data in the management repository that was receivedon and before October 11, 2000 at 7 pm. When used with the ims_purgedb command, theInternet Management Server (IMS) is represented by the acronym TIMS.ims_purgedb -user raghu -passwd clever!!TIMS -delete -before "2000-10-11 19:00:00"

The following example prints statistical information about the events in the managementrepository to standard output, but does not delete the events from the managementrepository:

Managing Data in the Management Repository

34

ims_purgedb -stats

Because the user name and password were not specified, the command prompts you forthem, as follows:User:Password:

The output of the command is as follows:STI Admin UtilityThere are x event entries.QOSM Admin UtilityThere are x event entries.SI Admin UtilityThere are x event entries.TIMS Admin UtilityThere are x event entries.WSA Admin UtilityThere are x event entries.

where x is the total number of events in the management repository.

To delete data from a Tivoli Web Services Analyzer, use the ims_purgedb command withonly the abbreviation of the application. You must use a separate command for eachapplication.

For example, to delete only Quality of Service data, use the following command:ims_purgedb [–user user_name –passwd password] [ QOSM][–delete [–before “yyyy-mm-dd hh:MM:ss”] ]



5.M

anag

ing

Data

inth

eM

anag

emen

tR

epo

sitory


36

Internet Management ServerAdministration

Managing the Event ServiceTivoli Web Services Analyzer and the management server generate events, which are storedin the management repository. You can configure events to be forwarded to a destination byone of the following event handlers on the management server:

¶ System event log, through the log handler

¶ One of more e-mail addresses, through the Simple Mail Transfer Protocol (SMTP)handler

¶ Simple Network Management Protocol (SNMP) management application, through theSNMP handler

¶ Tivoli Enterprise Console (TEC), through the TEC handler and the Web ServicesCourier endpoint

¶ Scripts that initiate an action, such as a remedial response to an event, through theEXEC handler

The e-mail, SNMP, and TEC event-forwarding responses require configuration of themanagement server, as described in the following pages.

Tivoli Web Services Analyzer stores time in Greenwich Mean Time (GMT). The event datareceives a GMT timestamp. This ensures that all events are displayed on the GUI in aconsistent manner.

Forwarding Events to the Tivoli Enterprise ConsoleYou can configure events to be forwarded to the Tivoli Enterprise Console (TEC). The TECevent handler translates an event from Internet Management Server format to TEC format.The formatted event is queued on the management server. The Web Services Courier (WSC)endpoint polls the management server every 60 seconds for TEC events. Whenever there areany in the queue, they are forwarded to TEC.

Install the Web Services Courier endpoint according to the instructions in your installationguide. Make sure that the TEC Forwarding Enabled check box is selected. The WSCendpoint must be installed on a TMA endpoint. After you complete installation of the WSCendpoint, TEC Forwarding is displayed as an option in the Event Response drop-down listin the application and system event configuration views.

To forward Tivoli Web Services Analyzer events to the Tivoli Enterprise Console, you musthave the Tivoli Framework and TEC installed. Tivoli also recommends that you contact theTivoli Enterprise administrator before configuring the TEC server.

6


6.In

ternet

Man

agem

ent

Server

Ad

min

istration

You should configure event responses before you configure events and you should completeboth tasks before you begin using Tivoli Web Services Analyzer. Configuring eventresponses first makes all the response options available when you configure the events.Configuring events before you begin creating jobs with the applications ensures that you willnot lose any event information when the jobs begin to run.

Forwarding Events to an SNMP Management ApplicationYou can configure events to be forwarded to a Simple Network Management Protocol(SNMP) management application such as Tivoli NetView. The SNMP handler creates amessage from event data, then creates and sends an SNMP trap.

To forward Tivoli Web Services Analyzer events to an SNMP management application, youmust have an SNMP management application installed. Tivoli recommends that you contactthat application’s administrator before forwarding events to the SNMP managementapplication.

Before the Tivoli Web Services Analyzer server can forward events to an SNMP server, youmust configure the management server as follows:

1. Using a text editor, edit the snmp.propertiesfile, which is located in thebase_dir/TIMS/lib/properties directory. The base_dirvariable represents theinstallation directory of the Tivoli Web Services Analyzer server. The contents of the fileare as follows:# # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## Configuration file for Tivoli WSM to SNMP Integration# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

# Location (IP address or hostname) of SNMP management platform# e.g. snmp.yourdot.comServerLocation=

#SNMP management platform incoming trap port number# e.g. default port is 162ServerPort=

2. Specify the fully qualified host name of the SNMP server with the ServerLocation key.For example, if the SNMP server is fodder.mycompany.com, the key looks like this:ServerLocation=fodder.mycompany.com

3. Specify the port number of the SNMP server with the ServerPort key. For example, ifthe SNMP server’s port is 162, the key looks like this:ServerPort=162

4. Save and close the snmp.properties file.

5. Restart the management server. See “Starting and Stopping the Internet ManagementServer” on page 40.

6. Copy the TWSM.mib file, which is located in the base_dir/TIMS/lib directory, to theSNMP server. This file enables the SNMP server to understand the Tivoli Web ServicesAnalyzer events.

7. Load the TWSM.mib file on the SNMP server. Refer to the SNMP server’s documentationfor instructions or contact that application’s administrator for assistance.

After you complete this procedure, SNMP Forwarding is displayed as an option in theEvent Response drop-down lists in the event configuration views.

Internet Management Server Administration

38

Forwarding Events to an E-mail AccountYou can configure the event service to forward events to one or more e-mail addresses,using the Simple Mail Transfer Protocol (SMTP) handler. Use the SMTP forwarding featureto ensure that the appropriate people are notified for each type of event generated. Automatice-mail notification is a simple and efficient way to communicate that an issue needs to beaddressed. The e-mail forwarding option also forwards notification to pagers and hand-helddevices if the receiving devices are configured properly.

Before you can forward events to an SMTP server, you must configure the InternetManagement Server as follows:

1. Using a text editor, edit the event.properties file, which is located inthebase_dir/TIMS/lib/properties directory. The base_dir variable represents theinstallation directory of the management server. The contents of the file are as follows:# # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## Configuration file for SMTP & SOCKS## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

trace.service=com.tivoli.xtela.core.util.DefaultTraceServicetrace.switches=1-7.0

# SMTP (mail) host name e.g. mail yourdot.commail.smtp.host=

# socksProxyHost, SOCKS firewall host, e.g. socks.yourdot.comsocksProxyHost=

# socksProxyPort, e.g. default SOCKS port is 1080socksProxyPort=

2. Specify the fully qualified host name of the SMTP server with the mail.smtp.host key.For example, if the SMTP server is rabbit.mycompany.com, the key looks like this:mail.smtp.host=rabbit.mycompany.com

3. If your network uses a SOCKS server to access the SMTP server, specify the fullyqualified name of the SOCKS server with the socksProxyHost key. For example, if theSOCKS server is socks23.mycompany.com, the key looks like this:socksProxyHost=socks23.mycompany.com

4. If your network uses a SOCKS server to access the SMTP server, specify the portnumber of the SOCKS server with the socksProxyPort key. For example, if the SOCKSserver’s port is 144, the key looks like this:socksProxyHost=144

5. Save and close the event.properties file.

6. Restart the management server. “Starting and Stopping the Internet Management Server”on page 40

After you complete this procedure, you must still configure e-mail forwarding in CreateEvent Responses under General Tasks → System Administration on the GUI. When youhave completed that process, Send an E-mail is displayed as an option in the EventResponse drop-down list in the event configuration views.



6.In

ternet

Man

agem

ent

Server

Ad

min

istration

Starting and Stopping the Internet Management ServerFor troubleshooting, maintenance, or emergency recovery, you might need to manually stopor restart the Internet Management Server. Use the following procedures to manually stop orstart the Internet Management Server.

Starting and Stopping on Windows SystemsUse any of the following methods to stop or start the management server on supportedWindows systems:

¶ To stop or start the management server from the Start menu: select Start → Programs →Tivoli → Internet Management Server Stop.

¶ To stop or start the management server from the Control Panel:

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:

v Click the Stop button to stop the management server.

v Click the Start button to start the management server.

¶ To stop or start the management server from a command prompt:

v Enter the following two commands to stop the management server:net stop "TIMS HTTP Server"

net stop "Tomcat"

v Enter the following two commands to stop the management server:net start "TIMS HTTP Server"

net start "Tomcat"

If you try to run the GUI immediately after restarting the server and it fails, wait a fewminutes and try again. The server might need time to complete its initialization.

Starting and Stopping on UNIX SystemsUse one of the following methods to start or stop the management server on the specifiedUNIX systems:

¶ To stop or start the management server on Solaris:

v Enter the following command from the root directory to stop the management server:/etc/inti.d/tivoliIMS.rc stop

v Enter the following command from the root directory to start the management server:/etc/init.d/tivoliIMS.rc start

¶ To stop or start the management server on Solaris or AIX:

1. Change to the following directory:install_dir/ManagementServer/TIMS/bin/

where install_dir is the directory when the management server was installed. Thedefault installation is /opt/Tivoli/Internet.

2. Do one of the following:


40

v Enter stopms.sh to stop the management server.

v Enter startms.sh to start the management server.

If you try to run the console immediately after restarting the server and it fails, wait a fewminutes and try again. The server may need time to complete its initialization.

Stopping and Starting an EndpointTo stop an endpoint, enter the following command on the specific endpoint you want tostop:install_dir/Tivoli/Internet/<endpoint_name>/bin/stopep.sh

To start an endpoint, enter the following command on the specific endpoint you want tostart:install_dir/Tivoli/Internet/<endpoint_name>/bin/startep.sh

where:

install_dirSpecifies the directory path to where the web server is installed.

<endpoint_name>Specifies an endpoint.

For endpoints that include a web server, use stopserver.sh to stop the web server, andstartserver.sh to restart the server.



6.In

ternet

Man

agem

ent

Server

Ad

min

istration

Tivoli Decision Support Guide for TivoliWeb Services Analyzer

When Tivoli Web Services Analyzer has collected data from your Web servers, you must beable to make sense of it all. That is where the Tivoli Decision Support Guide for WebServices Analyzer comes in.

When the data has been collected, it can be assembled in a special type of relationaldatabase called the Tivoli Web Data Warehouse. Tivoli Decision Support can then extractand analyze the data by means of reports that are displayed in the Tivoli DiscoveryInterface.

Use Tivoli Discovery Administrator to define queries that extract data from this databaseinto a comma-separated values (CSV) file. The Cognos Transformer builds themultidimensional cubes from this file, which can then be reported by Cognos PowerPlay. Acube is a data container used by Cognos PowerPlay. PowerPlay is a multidimensionalreporting and analysis package that you must install with Tivoli Decision Support. A numberof PowerPlay tools are embedded in Tivoli Decision Support. Before Tivoli DecisionSupport can operate properly, you must ensure that the Discovery Administrator is properlylinked to the databases in your organization. Finally, use the Tivoli Discovery Interface toview these reports.

Tivoli Decision Support (TDS) retrieves information from the web data warehouse forreporting purposes. In order to run these new reports, your WebSphere Site Analyzer datamust be in the same database as the web data warehouse. If you are setting up WebSphereSite Analyzer, refer to the that product documentation on how to configure your database.Otherwise, you will need to import the data manually. Consult with your databaseadministrator for how to do this.

For issues regarding Tivoli Decision Support installation and configuration, refer to theTivoli Decision Support documentation. All of the Tivoli Decision Support 2.1 manuals andRelease Notes cited in the Web Services Manager and Web Services Analyzer manuals arelocated on the Tivoli Decision Support 2.1 CD-ROM (\Docs\Pdf), or in theD:\<destdir>\TDS 2.1\Docs\Pdf directory, where D is the drive letter and <destdir> is thebase directory where Tivoli Decision Support Version 2.1 is installed.

Building CubesCube building is a resource-intensive activity. Thus, while you should schedule regular cubebuilds, schedule them during periods of decreased database activity. Adjust your cube daterange to optimize the time required to build a cube. This task is performed from theAdministrator panel of the Tivoli Discovery Administrator console.

7


7.G

uid

efo

rTivo

liW

ebS

ervicesA

nalyzer

Follow these steps to build a cube:

1. Double-click Cubes on the Administrator panel.

2. Right-click on a cube, and then select Build. The Confirm Cube Build dialog displaysthe date ranges.

3. Click Yes.Tivoli Decision Support connects to your database and retrieves the records specified in yourquery. The size of your data and the network speed affect the time required to retrieve allrecords. Use the status bar to check the status of the processing. The Cube Transform Statusdialog displays processing messages.

4. Review the processing messages for any errors. If an error generates an error dialog,review the error, and then click OK.

5. Click Close.

For more information about how to use the Tivoli Decision Support Discovery Interface, seethe Tivoli Decision Support User’s Guide, and the Tivoli Decision Support: Using DecisionSupport Guides.

Scheduling the Cube Build TaskYou must periodically rebuild the cube to update your cube data. The build process can bescheduled to build automatically at regular intervals (for example, schedule nightly cubebuilds). Stagger the start times for your cube builds for improved performance. Also, makesure the cube builds are scheduled after the Tivoli Web Services Analyzer job runs, sincethis job must finish in order to have updated data for the cubes.

The following procedure uses the Tivoli Discovery Administrator to create a cube buildingschedule and to determine the schedule TaskID. The cube build is then scheduled using theCognos Scheduler.

Use the following procedure to define a cube building schedule:

1. Start the Tivoli Discovery Administrator.

Guide for Tivoli Web Services Analyzer

44

2. Select Add→Cube Build from the Scheduled Task menu to display the Add Scheduletask guide.

3. Type a name for the schedule you are creating in the Schedule Name box, and thenclick Next.

4. From the drop-down list, choose the cube for which this build is scheduled and clickNext.

5. Choose how often you want to do this task, and click Next.

6. Choose an interval of days to do this task, and click Next.

7. Choose a time to start the this task.

Note: When scheduling a cube build, you must be sure that the Web log collectionsequence has completed before the cube build begins. Failure to enable Web logcollection to complete will cause the cube to build with incomplete data.

8. Click Next.

9. In the Effective From date box, type or select a date that is prior to the current date.

10. Select the To check box to display the ending date box.

11. In the Ending Date box, type or select the date that you want the schedule to end, andthen click Next.

12. Click Finish.

13. Click Scheduled Tasks in the Tivoli Discovery Administrator panel to display theProperties panel.

14. Right click on the scheduled task you created, and then click Edit to display the EditSchedule dialog.

15. On the Task tab, record the Schedule Task ID (used in a later step), and then click OK.

16. From the Windows NT Start Menu, select Programs→Cognos→ Scheduler to start theCognos Scheduler.

17. From the Insert menu, select Recurring Task to display the Insert Task dialog.

18. Click the Identification tab, and then type the following command string in the FileName box:



7.G

uid

efo

rTivo

liW

ebS

ervicesA

nalyzer

“<directory path>\EDAdmin.exe” /TaskID=X

where:

<directory path> is the installation directory path for Tivoli DecisionSupport

X is the Schedule Task ID.

Be sure to enclose the directory path and EDAdmin.exe in quotes as shown in thefollowing example:“c:\Program Files\TDS\EDAdmin.exe” /TaskID=1

19. Type a brief description of the cube and the schedule in the Description box.

20. Click the Timetable tab, and specify the cube building frequency, run time, and span ofcalendar dates to run.

21. Minimize the Cognos Scheduler.

Note: Cognos Scheduler must be running for the cube to build at the scheduled time. Itis recommended that you add the Cognos Scheduler to the startup folder of theTivoli Decision Support server.

Topics and ViewsOn the Tivoli Discovery Interface, the data collected for the Tivoli Decision Support Guidefor Web Services Analyzer is organized into topics and views. Selecting a view within atopic displays a report showing the results of a database query based on the topic and viewselected. In addition to the report itself, each view displays a view description in the Hintspanel at the bottom of the interface.

Additionally, the default views can be further modified by dragging other dimensions downfrom the dimension line into the view, and by drilling down certain measures for a finergrained view of the data.

Before running the reports for the first time, a database view must be created which containsthe correlated data. The view only needs to be created once. Logged in as the databaseadministrator, a user creates the view by executing one of the following commands from aDOS prompt. The command files are located in the TDS_guides subdirectory on the productCD:

¶ For DB2 database: The name of the warehouse database is provided as the only inputparameter.db2cmd create_tds_view_db2.bat nameofwarehousedatabase

¶ For Oracle database: The Oracle connect_string provides the db network service nameand is generally of the form OracleSID or OracleSID_OracleHostNamesqlplus user/pwd@connect_string < create_tds_view_oracle.sql

Tivoli Decision Support Guide for Web Services AnalyzerThe Tivoli Decision Support Guide for Web Services Analyzer provides the following topicsand views:

Topic: How is user response time being affected by Web site traffic?


46

Views: The views in this topic use information from the Quality of Serviceendpoint and IBM WebSphere Site Analyzer 4.0. With this data, you cancorrelate the quality of service you provided visitors during QOS testperiods with the volumes and types of traffic that were present on yoursite during those test periods. These reports are Crystal Reports.

¶ User response time correlated by kilobytes downloaded by URI

¶ User response time correlated by number of hits by URI

Topic: What are visitors doing on my site and where are they coming from?

Views: The views in this topic display information about who your users are, andwhere they come from. Views include:

¶ Browser breakdown

¶ Most Active Organizations

¶ Most Requested Pages

¶ Top Entry Page

¶ Top Referring Pages

¶ Top Unique Visitors by Date

¶ Top Unique Visitors by Server

¶ Visitors by Domain

Topic: What errors are visitors encountering on my site?

Views: The views in this topic display information about the number and kinds oferrors your users are encountering on your site. Views include:

¶ Error Breakdown

¶ Errors by Server

¶ Errors by URL

Topic: What is my data transfer activity?

Views: The views in this topic give you an overall look at the traffic on your site.Views include:

¶ Kilobytes Downloaded by Date

¶ Kilobytes Downloaded by Server

¶ Number of Document Views by Server

¶ Number of File Downloads by Date

¶ Number of File Downloads by Server

¶ Top Downloaded Files by Name

Topic: What is my overall site activity?

Views: This report gives you a high level view of the traffic your site is gettingas well as a look at how many visitors you are attracting. View includes:

¶ Statistics by reporting period

Topic: What is my Web site traffic?



7.G

uid

efo

rTivo

liW

ebS

ervicesA

nalyzer

Views: These reports give you information about who is hitting your site and howoften.

¶ Number of Unique Visitors by Date

¶ Number of Unique Visitors by Webserver

¶ Page Views by Date

¶ Page Views by Server

¶ Web Activity by Date

¶ Web Activity by Server

Tivoli Decision Support TroubleshootingThis section includes the following topics:

¶ Solving Cube-Building Problems

¶ Solving Report Problems

Solving Cube-Building ProblemsCube building has the following problems and possible solutions:

¶ What do I do when the Tivoli Discovery Administrator message appears:Error building cube.

and the Details information includes:Error 91 - Error getting query parameters;object variable or with block variable not set.

The data sources have not been assigned to the cube queries. Assign the data sources tothe queries.

¶ During use of the Tivoli Discovery Interface, what does it mean when a CognosPowerPlay report icon appears with a Cannot Execute indicator, and report cannotbe opened?

The cube is unavailable. Contact the Tivoli Decision Support administrator and request thatthe cube be built.

¶ Why does the Tivoli Discovery Administrator report that a cube could not be built?The cube you are attempting to rebuild is currently in use, and Tivoli Decision Supportcannot overwrite this cube with the new cube data. Close all copies of the Tivoli DiscoveryInterface that are running. Copy the CubeName.mdc file from the Tds\Cubes\Tempdirectory to the Tds\cubes directory, where Tds is the Tivoli Decision Support installationdirectory.The queries returned insufficient data to build a cube. Verify your queries.

¶ If all the Tivoli Discovery Interface processes are closed, why doesn’t the cubebuild?

A copy of Cognos PowerPlay might still be running in the background. This can alsoprevent cube builds from succeeding. Open the Task manager. If you find the processpplay.exe, end the process and rebuild the cube.


48

¶ Why don’t the cubes build automatically overnight?For scheduled cube builds to occur, the Cognos Scheduler must be running. Start the CognosScheduler. Review the schedule definitions in the Cognos Scheduler and in the TivoliDiscovery Administrator.

¶ How are relative dates calculated in a report?The Date Range parameter for a cube determines the time period that you want to examine.This parameter uses explicit values, start and end dates, or a calculated value such as the lastthree months. The calculated values are relative to the current date. Use the Date Rangeparameter and the CubeName_dt.txt file to set the current period in the following cases:

Explicit Date Range End date

Calculated Values Calculated end date

No Date Range parameter in cubeDate the cube is built

v If you want to use the date in the CubeName_dt.txt as the current period, create anew query in the cube model. This query must use the CubeName_dt.txt file as alocal data file. Also the set the current period option must be set only for this query.

v Use the Date Range parameter, but do not use the CubeName_dt.txt file. This selectsonly records between the specific start date and end date, and sets the current periodto the most recent date in the data.

v Do not use either the Date Range parameter or the CubeName_dt.txt file. Thisselects all the records, and sets the current period to the most recent date in the data.

v Use the CubeName_dt.txt file, but do not use the Date Range parameter. This selectsall the records, and sets the current period to the date of the current cube build.

For more information about how to set the current period and select records, refer to theTivoli Decision Support Administrator Guide.

Solving Report ProblemsThe following problems can occur:

¶ What should I do when the following error message appears?load_graph_from_powercube

The cube has not been built. Build the cube.

¶ I tried to open a report, but the Tivoli Discovery Interface gets stuck at the waitcursor.

The Tivoli Discovery Interface might have lost its connection to the Cognos PowerPlay task.Close the Tivoli Discovery Interface and Cognos PowerPlay. Restart the Tivoli DiscoveryInterface and open the reports again.

¶ I opened a report, but it contained no data.There might be data in the report, but there is no data in the drill-down. The report might befiltered on a dimension. Look at the dimension bar and check if any of the values, especiallythe date dimension, are drilled down.For Crystal reports, you must specify a parameter. See the hint text at the bottom of theTivoli Discovery Interface for information about entering the parameter.



7.G

uid

efo

rTivo

liW

ebS

ervicesA

nalyzer

¶ The tabular reports do not have a left margin.The type of printer attached to a workstation influences the alignment of the reports. Trydisconnecting the printer and restarting Tivoli Decision Support.

¶ I cannot open a Crystal Report using the Tivoli Discovery Interface.You might be addressing the wrong database. On the Tivoli Discovery Interface task bar,click View → Options. On the Options dialog, examine the Database tab to verify that theData Source Settings section properly defines the DSN, Qualifier, Database Name, and Typefields.


50

Scheduling Application Jobs

Tivoli Web Services Manager offers a variety of options for scheduling application jobs. Ineach of the application chapters, the most likely scheduling option was presented in the jobconfiguration discussion. In this chapter, those options are reviewed and other schedulingoptions are presented as well.

Run ContinuouslyJobs can be scheduled to run continuously. You can configure this option in one of twoways: use an existing schedule or create a new one.

To use an existing schedule:

1. Click the arrow to the right of the Existing configurations drop-down list. A list of allpreviously configured schedules is displayed.

2. Select the schedule you want to use and click Populate to view the details of theselected schedule. Click Next to accept the schedule. To choose another schedule, clickClear and make another selection.

To create a new schedule:

1. Click the application’s Schedule tab.

2. Select whether you want to run the job immediately or to have it start at a later time. Ifyou want the job to start later, enter a time and date. Note that the job start times are in15-minute increments.

3. Click the Continuously radio button.

4. Decide when you want the job to terminate or if you want it to terminate at all. If youwant it to terminate, enter a time and date.

5. Click Next. If you need to begin again, click Clear.

Note: Times entered are relative to GMT. The difference, in hours, between GMT andthe current browser is displayed in the Portfolio. Add or subtract the offset fromGMT to set the date and time the job is to run. For example, if your browsershows a GMT offset of -5, and you want the job to run on October 2nd at2:00AM local time, the start time would be 9:00 PM (21:00) on October 1st. Inlocales where the time changes from standard time to daylight-saving time, jobschedules need to be adjusted to reflect the local time change if the metricsproduced by the job are time sensitive.

8


8.S

ched

ulin

gA

pp

lication

Job

s

Run OnceJobs can be scheduled to run once, either immediately or at a later time. You can configurethis option in one of two ways: use an existing schedule or create a new one.





1. Click Clear to remove the values.

2. Select whether you want to run the job immediately or to have it start at a later time.

3. Select a termination time (when the job will stop running, regardless of whether or not ithas finished) at the bottom of the view and click Next. You can also choose to neverterminate the job.

Note: In Site Investigator, there is no timeout parameter. If you want an investigation to endafter a certain amount of time, you can determine that by entering a termination timeat the bottom of the schedule view.

Run RepeatedlyJobs can be scheduled to run during the same time frame on a regular basis. You canconfigure this option in one of two ways: use an existing schedule or create a new one.





1. Click Clear to remove the values.

2. Select whether you want to run the job immediately or start it at a later time.

3. If you want to run the job multiple times on a regular basis, select Run job every andthen choose your options. Review the following examples.

Note: Times entered are relative to GMT. The difference, in hours, between GMT andthe current browser is displayed in the Portfolio. Add or subtract the offset fromGMT to set the date and time the job is to run. For example, if your browsershows a GMT offset of -5, and you want the job to run on October 2nd at2:00AM local time, the start time would be 9:00 PM (21:00) on October 1st. In


52

locales where the time changes from standard time to daylight-saving time, jobschedules need to be adjusted to reflect the local time change if the metricsproduced by the job are time sensitive.

a. To run a job every 15 minutes, enter a value of 15 minutes and click Continuously.

b. To run a job once every day from 6:00 am until 9:00 am, enter a value of 24 hoursand enter the correct values in the Start Time and End Time fields.

c. To run a job once each weekday from 6:00 am until 9:00 am, enter a value of 24hours and mark the boxes in front of the days of the week.

d. To run a job every Monday at 6:00 am, enter a value of 240 hours, enter the correctvalues in the Start Time and End Time fields, and make certain that you have entereda Monday as the start Date.

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



8.S

ched

ulin

gA

pp

lication

Job

s


54

General Tasks and System Administration

The Tivoli Web Services Analyzer GUI enables you to perform a number of tasks related toall of the applications. These general tasks, as well as system administration functions, areaccessible by selecting the General Tasks drop down in the Portfolio.

When the General Tasks drop down is selected in the Portfolio, options are expanded in thePortfolio to reveal three major task categories:

Global ViewsFunctions in this category are generally accessible to all users, regardless of theauthorizations granted in Manage Accounts. This expandable category includes thefollowing functions:

¶ View all jobs

¶ View global event log

¶ View all endpoints

System AdministrationFunctions in this category require authorization to perform administrative functions.This expandable category includes the following functions:

¶ Configure System Events

¶ View System Event Log

¶ Create Event Responses

¶ Manage Application Data

¶ Manage Accounts

¶ View Log Files

¶ View TIMS Details

User PreferencesFunctions in this category enable any user to modify account preferences that areapplicable to their own user account. This expandable category includes thefollowing functions:

¶ Change Password.

¶ Change Time Zone. The time zone preference only applies to the event logviews, the endpoints view, and the reports. Greenwich Mean Time applies to allother settings.

9


9.G

eneral

Tasksan

dS

ystemA

dm

inistratio

n

Global ViewsAny user account can view endpoints, event logs, and scheduled and completed jobs.Because no special authorization is required for these activities, they are referred to asGlobal Views.

View all JobsTo view all Quality of Service, Site Investigator, and Synthetic Transaction Investigator jobs,perform the following procedure:

1. From the Portfolio, click Global Views, then click View All Jobs. A table of jobs isdisplayed.

Note: Jobs can be sorted by name, application, state, or endpoint name by clicking theheadings in the job table.

View Global Event LogThe global event log displays all events generated by the Internet Management Server andTivoli Web Services Analyzer. It is a real-time log and provides complete information abouteach event that is logged.

To view the global event log, click General Tasks → System Administration → ViewGlobal Event Log.

Note that you can determine the maximum number of events that are displayed in the log byentering a value at the top of the log. In addition, you can sort the log by category byclicking on any of the column headings. Double-clicking on the headings reverses the orderof the column entries.

Since the log can grow large very quickly, Tivoli Web Services Analyzer enables you topurge the log whenever you need to. At the bottom of the log, you can enter a date and clickDelete All Before to delete all events generated before that date.


56

View All EndpointsIf you want to determine whether or not all of the endpoints in your Tivoli Web ServicesAnalyzer installation are installed and available, you can view them from Global Views →View All Endpoints.

From the Portfolio, click Global Views, then click View All Endpoints. The availableendpoints are displayed in a table that includes the endpoint name and its description,endpoint type, hostname, and installation date. The far right side of the View All Endpointsscreen has a selectable box labelled Heartbeat Event. A heartbeat event is an event thatindicates the endpoint is not functional. Checking this box enables heartbeat events from anendpoint. For example, if this box is checked and a system is powered down or otherwisefails, a heartbeat event is recorded. Unchecking this box disables heartbeat events. When anendpoint is installed, heartbeat events are enabled.

System AdministrationThe Tivoli Web Services Analyzer GUI enables you to perform a number of systemadministration functions. You access to these functions by selecting General Tasks from thedrop-down list on the Portfolio, then clicking System Administration.

Configure System EventsYou can configure events for each application. You can also configure system events that arecommon in all applications under General Tasks → System Administration. System eventsare listed in the following table. See “Configuring Events” on page 28 for a completeexplanation of how to configure events.

System Event Types

Type Definition

Endpoint Uninstalled An endpoint has been uninstalled.

Heartbeat Missing The heartbeat has been missing from an endpointfor a number of minutes. This event is generatedif the management server has not received aheartbeat signal from the endpoint for a specifiedperiod of time (in minutes).

Authorization Failure The management server failed to authorize aclient request. Events of this type are generatedwhen an invalid password is specified, a userlacks permission to use the requested service, orwhen/if any other authorization request is invalid.



9.G

eneral

Tasksan

dS

ystemA

dm

inistratio

n

System Event Types

Type Definition

Authorization Service Succeeded The authorization or authentication succeeded.Events of this type are generated, for example,when a user is successfully created or when/if amanagement server is defined.

Authorization Service Failed The authorization or authentication service failed.Events of this type are generated for example,when an invalid password is specified or when/ifan attempt is made to delete a user.

Server Authentication Failed Authentication failed while defining a foreignmanagement server (server-to-servercommunication).

Mail Service Failed The STMP service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

SNMP Service Failed The SNMP service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

TEC Service Failed The TEC service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

EXEC Service Failed The EXEC service failed to start up due to anexception. This event is generated when aninternal error occurs or if the service finds anenvironmental or resource constraint whilestarting.

Endpoint Installed A new endpoint has been installed and registeredwith the management server.

EXEC Status Failed The user-supplied script or program ran andreturned a non-zero (error) status code. Thisevent is generated when the service runs auser-supplied script or program that returns anerror code.

EXEC Failed The user-supplied script or program failed toexecute. This event is generated when the serviceunsuccessfully attempts to run a user-suppliedscript or program.

Unknown Endpoint Unknown endpoint ping. The management serverhas been contacted by an endpoint that is notregistered.

Event Forwarded to TEC Missing Data Certain fields in the event forwarded to TEC aremissing information. This is an internal error.TEC will not reject the error.

An endpoint has started an auto-update process. An endpoint has started an auto-update process.


58

System Event Types

Type Definition

An endpoint auto-update process has completedsuccessfully.

An endpoint auto-update process has completedsuccessfully.



Recovery: Heartbeat no long missing fromendpoint.

Recovery: Heartbeat no long missing fromendpoint.

To configure Tivoli Web Services Analyzer system events, complete these steps:


2. Click the arrow to view the Event Type drop-down list.

3. Select the event type you want to configure. You can also choose to have the EventTable display only system events by checking the box at the right.

4. Click the arrow to view the Event Severity drop-down list.

5. Select the severity level you want to assign to the event.

6. Click the arrow to view the Event Response drop-down list.

7. Select the event response you want to associate with the event type. If you require aresponse action not in the list, see “Creating Event Responses” on page 22.

8. Click Add to Table. The Event Table displays system event types. Using the radiobuttons below the table, you can display all event types or only a selected event type.You can also delete configured events by highlighting them in the table and then clickingDelete.

9. When you are satisfied with the event configuration, click OK to return to the mainbrowser screen.

View the System Event LogThe system event log is a real-time log that displays all events generated by the InternetManagement Server. The system event log provides complete information about each eventthat is logged.

To view the system event log, select General Tasks from the drop-down list, then click onSystem Administration → View System Event Log.

You can determine the maximum number of events that are displayed in the log by enteringa value at the top of the log. In addition, you can click on any of the column headings tosort the log by category. Double-clicking on the headings reverses the order of the columnentries.

Since the log can grow large very quickly, Tivoli Web Services Analyzer enables you topurge the log whenever you need to. At the bottom of the log, you can enter a date and clickDelete All Before to delete all events generated before that date.



9.G

eneral

Tasksan

dS

ystemA

dm

inistratio

n

Create Event ResponsesThe Internet Management Server (IMS) and the Tivoli Web Services Analyzer tasks generateevents that are stored in the management repository. By creating event responses, you canconfigure events to be forwarded to one of several destination consoles using one of thefollowing event handlers on the management server:

¶ The system log, through the log file handler

¶ One or more e-mail addresses, through the Simple Mail Transfer Protocol (SMTP)handler

¶ A Simple Network Management Protocol (SNMP) management application, through theSNMP handler

¶ The Tivoli Enterprise Console (TEC) through the TEC handler and the Web ServicesCourier (WSC) endpoint

¶ A program that runs a customer-supplied script in response to the event, through theEXEC handler

You can select any of the responses for an event, but only the e-mail forwarding and EXECoptions are configurable.

For a complete discussion of how to create event responses, see “Managing Events andEvent Responses” on page 21.

Manage Application DataCertain data in the management repository is expected to collect over time, thereby requiringthat you manage it. This data includes events, management data that is uploaded by TivoliWeb Solutions applications, and data generated by jobs. However, Tivoli Web ServicesAnalyzer does not monitor the management repository for space utilization and thresholds. Itis your responsibility to monitor the health of the mangement repository and to regularlypurge events, unneeded collections, jobs, and so on.

How often you need to purge data depends upon the size of the database. Consult yourdatabase administrator if you unfamiliar with database maintenance. Failure to monitor andmaintain the management repository could result in the Internet Management Serverbecoming unusable or ineffective because it cannot write to the database.

To perform data management tasks using the GUI, use the following procedure:

1. In the Portfolio, select General Tasks from the drop-down line, then click SystemAdministration → Manage Application Data.

2. Mark the checkbox of the application or report category from which you want to purgedata. You can make more than one selection.

3. Select the end date for the data purge.

4. Click Delete All Before. All data collected before this date will be deleted by this action.

This feature replaces the ims_purgedb utility that was part of earlier releases of the product.

Manage AccountsThe Manage Accounts screen is used to grant or deny administrative privileges to users. It isalso used to add new user accounts or delete user accounts that are no longer needed.


60

To perform any of these tasks, use the following procedure:

1. Click General Tasks → System Administration → Manage Accounts.

2. To add a user, enter the required information in the Add Account table and click AddAccount.

Note: By default, a new user is automatically given permission to access all functions.However, these authorizations do not become effective until the Modify SelectedAccounts button is clicked. To restrict a user to a subset of administrativefunctions, see Step 4.

3. To delete a user, select the entry you wish to delete from the Delete Accounts table andclick Delete Account.

4. To modify the applications, monitors, and Portfolio links that an existing user isauthorized to access, perform the following steps:

¶ Select the ID of the user to be modified by clicking in the box to the left of thename of a user. A checkmark in the box indicates the user ID has been selected. Anymodifications made in the Modify Administrative Roles for Accounts table will beapplied to all user IDs that are checked when the Modify Selected Accounts buttonis clicked.



9.G

eneral

Tasksan

dS

ystemA

dm

inistratio

n

¶ Select the functions the selected user ID is allowed to access by clicking in the boxbelow an application name. A checkmark in an application box indicates the selecteduser ID can access links in the Portfolio area of the GUI to administer theapplication. Applications include QoS, SI, STIP, STIR, WCM, and DataCollection. For each application, there is a corresponding View selection, forexample, QoS (View). Checking a View selection grants the user the authority toview application settings, but not change them. Selecting the System box grants theselected user ID permission to perform administrative functions accessible under theGeneral Tasks → System Administration link in the Portfolio.

Note: In general, users cannot see Portfolio links to functions they are notauthorized to use. In some cases, links are visible in the Portfolio even if auser is not authorized to use them. If a user clicks on a Portfolio link to gainaccess to a function the user is not authorized to use, an error messageindicating access is not authorized is displayed in the work area of the user’sbrowser.

¶ Click Modify Selected Accounts to apply the changes. If a selected user is currentlylogged on, any changes made do not take effect until the next time the user logs onto the system.

Viewing Log FilesYou can view the management server log files (timsui1.log) from the GUI:

1. In the Portfolio, select General Tasks, then click System Administration → View LogFiles.

2. Click tims1.gui to begin viewing.

See “Problem Determination” on page 65 for information about log file settings.

View TIMS DetailsYou can verify which of the Tivoli Web Solutions applications are currently enabled for yoursystem from the GUI. In the Portfolio, select General Tasks, then click SystemAdministration → View TIMS Details. (TIMS stands for Tivoli Internet ManagementServer.)

User PreferencesAny user can change some personal preferences for their own account. Settable preferencesinclude the password associated with the user’s account, and the time zone shown in someviews and reports.

Change PasswordTo change your logon password, use the following procedure:

1. Click General Tasks → User Preferences → Change Password.

2. Enter the old (current) password, enter the new password, then re-enter the newpassword to confirm.

3. Click Change Password.

Change Time ZoneTo change the time zone displayed in the event log views, endpoints view, and reports toreflect the time in a different time zone, use the following procedure:


62

1. From the Portfolio, click General Tasks → User Preferences → Change Time Zone.

2. Select the time zone desired when viewing event logs, endpoints, and reports from thedrop down list of time zones.

Note: All other views contain GMT timestamps.

3. To make the selected time zone the default time zone for event log views, endpointviews, and reports, click Set As Default.

Note: The time zone default only applies to the currently-in-use user account.



9.G

eneral

Tasksan

dS

ystemA

dm

inistratio

n


64

Problem Determination

This chapter contains the most current information for Tivoli Web Solutions messages.

Customer SupportThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide tosupport services (the Customer Support Handbook); frequently asked questions (FAQs); andtechnical information, including release notes, user’s guides, redbooks, and white papers.You can access Tivoli publications online at http://www.tivoli.com/support/documents/.The documentation for some products is available in PDF and HTML formats. Translateddocuments are also available for some products.

To access most of the documentation, you need an ID and a password. To obtain an ID foruse on the support Web site, go to http://www.tivoli.com/support/getting/.

Resellers should refer to http://www.tivoli.com/support/smb/index.html for moreinformation about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” for more information aboutobtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of thefollowing telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

Providing Feedback About PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation. We welcome your suggestions for improvements. If you have comments orsuggestions about our products and documentation, contact us in one of the following ways:

¶ Send e-mail to [email protected].

—OR—

¶ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.

Contacting Customer SupportIf you need support for this or any Tivoli product, contact Tivoli Customer Support in one ofthe following ways:

10


10.P

rob

lemD

etermin

ation

¶ Submit a problem management record (PMR) electronically from our Web site athttp://www.tivoli.com/support/reporting/. For information about obtaining supportthrough the Tivoli Customer Support Web site, go tohttp://www.tivoli.com/support/getting/.

¶ Submit a PMR electronically through the IBMLink™ system. For information aboutIBMLink registration and access, refer to the IBM Web page athttp://www.ibmlink.ibm.com.

¶ Send e-mail to [email protected].

¶ Customers in the U.S. can call 1-800-TIVOLI8 (1-800-848-6548).

¶ Customers outside the U.S. should refer to the Tivoli Customer Support Web site athttp://www.tivoli.com/support/locations.html for customer support telephone numbers.

When you contact Tivoli Customer Support, be prepared to provide the customer number foryour company so that support personnel can assist you more readily.

User Interface LoggingThe user interface log file, timsiu.log, is located in the TIMS/logs directory. Informationis continually appended to this log file. Even if the Internet Management Server is restarted,the information appends to the previous timsiu.log file. You can view the log file byselecting General Tasks from the drop-down list in the Portfolio, then clicking on SystemAdministration→View Log Files.

Note: The abbreviation TIMS appears in some of the product file names. It is an oldabbreviation for the management server.

Attributes of logging are controlled by the uilogging.properties file located in theTIMS/lib/properties directory. Logging is the actual sending of information to the logfile; it includes both tracing and messaging. Tracing is the logging of stack traces and otherdevelopment and support tracing; these are not translated. Messaging is theuser-understandable logging that is translated. See “Adjusting Log File Settings” for moreinformation.

Adjusting Log File SettingsThe uilogging.properties file controls the settings of the user interface tracing andshould be placed in a management server path. At installation the file is in theTIMS/lib/properties directory. If invalid values are present or theuilogging.properties is not found, the default values will be used.

To change the attribute values, which are shown in the following table, edit theuilogging.properties file and restart the Internet Management Server.

Attribute Description Values Default

filename Specifies the name of the user interface log file any string timsui.log

loggingOn Specifies whether tracing and messaging is on or off. 0 = off

1 = on

1 — only errormessaging isturned on bydefault

66

severityLevel Specifies what types of error messages are logged.

0 and 1 correspond to error and warning, respectively.

2 includes the text traces in the code. These are nottranslated.

3 includes method in/out tracing. Currently, no methodtracing is done so this level is not in use.

Since they are not translated, severityLevel 2 and 3are only viewable under 1 and 2 detailLevel.

Higher levels are inclusive of lower levels. Forexample severityLevel 2 includes severityLevel0-2.

0 = error (messaging)

1 = warning(messaging)

2 = informational(tracing)

3 = detailed (tracing)

0

verboseLevel Specified the detail level of tracing to be logged.

Higher levels are inclusive of lower levels. Forexample severityLevel 2 includes severityLevel0-2.

0 = user

1 = support

2 = development

0

handler Controls how the log file can be appended.

The 0 (zero or multiple) value takes into account thevalues of multipleMaxLength and multipleMaxFiles.With the defaults, the multiple attribute will append toa log file named timsui1.log. When this log exceedsthe multipleMaxLength value, it will be renamedtimsui2.log. This process will continue until themultipleMaxFiles value is reached, at which time thelast log file will be deleted.

Note that timsui1.log will always be the most currentlog file.

0 = multiple files

1 = one file

0

multipleMaxLength

Applies only if handler = 0 Any integer; measuredin kilobytes

1000 K bytes

multipleMaxFiles

Applies only if handler = 0 Any integer 3

Note: The default values are used if the uilogging.properties file is not found or if itcontains invalid values.

The severityLevel and verboseLevel values act as a grid for filtering. Each combination ofthe two provides different logging. The following are examples:

Example 1:(verboseLevel=1/support, severityLevel=2/detailed):2001.07.20 21:40:51:439 com.tivoli.xtela.core.ui.bean.global.DisplayJobsBean setJobs(Vector)UIBWAUG0002Ecom.tivoli.xtela.core.objectmodel.kernel.DBSyncException: This is an example exception with text.at com.tivoli.xtela.core.ui.bean.global.DisplayJobsBean.setJobs \(DisplayJobsBean.java:148)at com.tivoli.xtela.core.ui.web.task.global.DisplayJobs.execute \ (DisplayJobs.java:171)at com.tivoli.xtela.core.ui.web.task.UITaskService.handlePost \ (UITaskService.java:76)at com.tivoli.xtela.core.ui.web.XtelaServlet.doPost \(XtelaServlet.java:62)


10.P

rob

lemD

etermin

ation

at com.tivoli.xtela.core.ui.web.task.UITaskService.handleGet \(UITaskService.java:39)at com.tivoli.xtela.core.ui.web.XtelaServlet.doGet(XtelaServlet.java:50)at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

Example 2:(verboseLevel=0/user, severityLevel=1/error):2001.07.20 22:04:15.037 com.tivoli.xtela.core.ui.bean.global.DisplayJobsBean setJobs(Vector) UIBWAUG0002E An unexpected database error has occurred - unable to read the specified records.

Message IDs for the User InterfaceThis section describes the Tivoli Web Solutions error messages.

Tivoli Error Message FormatThe Tivoli error message format takes the form XXXYY####Z, where:

XXX product prefix (BWM, BWA, BWC, BWAUG)

YY application prefix

The following are the codes within the user interface:

BWM UQ (Quality of Service), US (Site Investigator), UT (Synthetic TransactionInvestigator), UI (Tivoli Web Services Manager interface), IS (Installation)

BWA UW (Tivoli Web Services Analyzer), UI (Tivoli Web Services Analyzerinterface)

BWC UO (monitor), UA (management), UI (Tivoli Web Component Managerinterface)

BWAUGby convention, used as the user interface global error code (over allproducts) since no global product prefix is provided

#### error message number

Z severity code of the error

I (informational)feedback about normal events

W (warning)potentially undesirable conditions

E (error)indicates problems that require intervention or correction before the programcan continue properly

The message ID is followed by the date and time of the message.

User Interface Error Message Number RangesGenerally, user-visible errors are in the 0000–4999 error message number range. All errorsabove 5000 are either support exceptions/errors or validation errors. In both situations, themessage IDs are only applicable for support or development purposes.

¶ Database exceptions (range 0001–0999): Under severityLevel=0 anddetailLevel=0display generic messages to the user. Under higher detailLevel, thestack trace pinpoints the location. In many cases, the database exception messagespecifies the UUID causing the exception.

68

¶ Other exceptions and errors (range 1000–4999): Any exceptions and errors that areappropriate for user understanding. These do not include validation errors.

¶ Support exceptions and errors (range 5000–8999): Any exceptions and errors that do notmake sense to a typical user, but could help support. Support errors are logged under thedefault user logging as Unexpected Exception, as in the following example:BWAUG5001E 2001.09.27 10L:51:33.644 com.tivoli.xtela.logging.ui.LogExample exception(Object, String, Throwable) UI An unexpected error has occurred.

In this example note that the message ID actually corresponds to a support exception ID,but the text under user verboseLevel is always ″An unexpected error has occurred.″ At ahigher verboseLevel, the stack trace will reveal the root problem.

¶ Validation errors (range 9000–9999): Validation errors differ slightly from other errors.Examples of validation errors are a negative value for integer fields or no input forfields that are required. By user-interface design, validation errors prohibit the user fromcontinuing to the next view. Therefore, they are resolved through user interaction and arenegligible. Validation errors are not be helpful for support and clutter the log files. Thisspecial range allows them to be filtered and not logged.

Error MessagesThis document lists and describes Tivoli Web Services Analyzer messages and codes andlists corrective actions for solving the conditions identified in each code. For each code, thisdocument lists the following information:

¶ Message number

¶ Description

¶ Operator response

Database Error Messages

BWAUG0000E An unexpected error has occurred.

Explanation: This message occurs when the error does not fall into any of the database error categories.

Operator Response: Contact Tivoli support.

BWAUG0001E An unexpected database error has occurred.

Explanation: This is the catchall database error that can be produced by errors that fall into any of the databaseerror categories.

Operator Response:

¶ Ensure that the database machine is up and running.

¶ Proceed through the operator responses for error numbers BWAUG0002 through BWAUG0005.


10.P

rob

lemD

etermin

ation

BWAUG0002E An unexpected database error has occurred - unable to read the specified records.

Explanation: The Internet Management Server cannot read from the database.

Operator Response:


¶ Ensure that the database and user interface are in sync. Manually adding or deleting entries from the databasecan cause invalid referential integrity. Refreshing the view corrects this in some cases. In other cases, youhave to manually delete or update the database so that there are no more references to records that do notexist.

¶ Advanced users: Turn on the jdbc tracing to trace all the calls to the database. In the dbconfig.propertiesfile in the TIMS/lib/properties directory, there is a variable called dgmgmttrace.jdbc . Uncomment thejdbc variable (remove the # before the variable) and set it equal to the file name to which you want it torefer.

BWAUG0003E An unexpected database error has occurred - the specified record does not exist.

Explanation: The database does not contain the specified record in its tables.

Operator Response:


¶ Ensure that the database and user interface are in sync. Manually adding or deleting entries from the databasecan cause invalid referential integrity. Refreshing the view will correct this in some cases. In other cases, youhave to manually delete or update the database so that there are no more references to records that do notexist.


BWAUG0004E An unexpected database error has occurred - unable to delete the specified records.

Explanation: The specified record could not be deleted from the database.

Operator Response:


¶ Ensure that the specified record is in the database.

¶ Deleted files are moved into a rollback segment that holds a certain amount of information so that an undoof these actions can be performed. Rollback segments are of a fixed size; if you try to delete too much at onetime and the rollback becomes full, then no records are deleted and this error occurs. Try deleting lessinformation at a time.


70

BWAUG0005E An unexpected database error has occurred - unable to write the specified records.

Explanation: Could not write to the database

Operator Response:


¶ It is possible that you have run out of table space. Refer to your database manual.


BWAUG1001E Could not save the schedule. Please verify that all inputs are valid.

Explanation: The schedule has some invalid information that the validation did not catch.

Operator Response: Review the inputs and make sure they are valid. For example, ensure that integers are notnegative and are numeric.

BWAUG1002E Unable to render view

Explanation: This is an internal server error.

Operator Response: Refresh the view.

BWAUG1003E An error occurred verifying the job.

Explanation: This means that the job has been written to the database, but cannot be read back (verified).

Operator Response:



¶ Advanced users: Turn on the jdbc tracing to trace all the calls to the database. In thedbconfig.propertiesfile in the TIMS/lib/properties directory, there is a variablecalled dgmgmttrace.jdbc. Uncomment this variable (remove the # before the variable) and set it equal tothe file name to which you want it to refer.

BWAUG1004E An unexpected database error has occurred - could not unschedule the specified jobs.

Explanation: This is a database write problem.

Operator Response:


¶ It is possible that you have run out of table space. Refer to your database manual.



10.P

rob

lemD

etermin

ation

BWAUG1005E Cannot delete the specified records. Please verify that all inputs are valid.

Explanation: The combination of input entered is invalid.

Operator Response: Check the input values and try again.

BWAUG1006E Job was not successfully scheduled.

Explanation: A database read or write error or some unexpected exception has occurred.

Operator Response: Ensure that the database machine is up and running.

BWAUG1007E Unauthorized access attempted.

Explanation: The user does not have the role needed to perform the task he is attempting to perform.

Operator Response: The user must request the required role from the administrator.

BWMUT1000W The transaction file could not be deleted from the management server.

Explanation: The file could not be deleted because it is write-protected, being used by another application, ordoes not exist.

Operator Response: Manually delete the transaction file from thex/ManagementServer/TIMS/STI/trans/<transid>, where <transids> is the ID of the transaction that needsto be removed.

BWMUT1001W The transaction directory could not be deleted from the management server.

Explanation: The directory for that task ID could not be deleted because it is write-protected, being used byanother application, or does not exist.

Operator Response: Manually delete the transaction file from thex/ManagementServer/TIMS/STI/trans/<transid>, where <transid> is the ID of the transaction that needs tobe removed.

BWMUT1001I The selected transaction could not be found.

Explanation: An IO Exception occurred while trying to access an STI transaction for editing.

Operator Response:

¶ Ensure that the database is up and running.

¶ Ensure that the database and user interface are in sync. Determine if the directory or file are actually in thedatabase. If not, update the database to remove the entry for that task, then rerecord the transaction.

BWMUT1002E An error occurred saving the transaction to disk.

Explanation: An IO Exception occurred while trying to access an STI transaction for editing.

Operator Response:



¶ Determine whether the transaction has become read/write protected or otherwise corrupted.

72

BWMUT1003E An error occurred loading the transaction from disk.

Explanation: An IO Exception occurred while trying to access the an STI transaction for editing.

Operator Response:



¶ Determine whether the transaction has become read/write protected or otherwise corrupted.

Reporting Error Messages

BWCRT1000E Task Start failure

Explanation: A task on an endpoint could not start. Logged when there is an exception in the start call to atask.

Operator Response: Please refer to the appropriate section on problem determination in your user’s guideand/or contact Tivoli Customer Support for further diagnosis.

BWCRT1100E Task Execute exception.

Explanation: A task execute exception occurred on the endpoint while uploading monitoring data. Loggedwhen there is an exception in the execute call to a task.

Operator Response: Please refer to the appropriate section on problem determination in your user’s guideand/or contact Tivoli Customer Support for further diagnosis.

Support Errors

BWAUG5000E–BWAUG8999E

Explanation: Please call Tivoli Customer Support for more assistance.

BWAUG5000E Invalid number format error.

BWAUG5001E Class Cast error.

BWAUG5002E Null error.

BWAUG5003E Missing resource error.

BWAUG5004E Could not retrieve the view.

BWAUG5005E Could not create the task.


10.P

rob

lemD

etermin

ation

BWAUG5006E Servlet error.

BWAUG5007E Input-output error.

BWAUG5008E No element found error.

BWAUG5010E Unable to load specified license checker.

Explanation: A non-existent license checker was specified either because the UITree.xml file was editedincorrectly or the classpath cannot be loaded.

Operator Response: Ensure that no one has modified the file. Ensure that the file is the class path and isaccessible.

BWAUG5011E XML parsing error.

Explanation: The edited transaction is either no longer valid or is not in well-formed XML.

Operator Response: Visually examine the XML document to ensure that it is well-formed.

74

Glossary

If you cannot find a term in this glossary, refer to the IBM Dictionary of Computing, whichis located at the following URL:http://www.networking.ibm.com/nsg/nsgmain.htm

It defines technical terms used in the documentation for many IBM products. It also includesIBM product terminology as well as selected terms and definitions from various industrysources.

A

access controlIn computer security, the process of ensuring that the resources of a computer system can only be accessed byauthorized users in authorized ways. In Tivoli Web Component Manager, access control restricts access toservices and applications on the Internet Management Server.

access control list (ACL)A list associated with an object that identifies all the subjects that can access the object and their access rights;for example, a list associated with a file that identifies users who can access the file and identifies their accessrights to that file.

administratorA system or web administrator who is authorized to perform management tasks on the Tivoli Web ComponentManager GUI.

authenticationVerification of the identity of a user or the user’s eligibility to access an object.

authorizationThe process of granting a user either complete or restricted access to an object, resource, or function

B

BAROC file (.baroc file)In the event server of the Tivoli Enterprise Console, the internal representation of the defined event classes.Tivoli Web Services Manager and Tivoli Web Component Manager provide a BAROC (Basic Recorder ofObjects in C) file for event integration with the TEC.

C

CASee certificate authority.

certificateA digital document obtained from a registered certification authority (CA) that contains the identity and publickey for a user or system component. In Tivoli Web Component Manager, certificates are used for securing theInternet Managment Server (using root certificates). See also foreign certificate.

certificate authority (CA)An organization that issues and signs certificates. A CA authenticates the certificate owner’s identity, the servicesthat the owner is authorized to use, issues new certificates, renews existing certificates, and revokes certificatesbelonging to users who are no longer authorized to use them.

Cognos PowerPlayA multidimensional reporting and analysis package that is installed with Tivoli Decision Support. A number ofPowerPlay tools are embedded in Tivoli Decision Support.


Glo

ssary

constraintA limit or boundary associated with a specific application parameter. Constraints can include time spans, activitytotals, state changes, or content found or not found. When a constraint is exceeded or violated, it creates anevent, which is sent to the management server. The event is logged in the application and global event logs, thenforwarded to any other configured recipients.

core servicesServices provided by the Internet Management Server that support the Tivoli Web Solutions applications. Theseservices include the event service, scheduler, data manager, and framework security.

cubeA particular kind of data container used by Cognos PowerPlay for multidimensional reporting.

D

databaseA collection of interrelated data organized according to a database schema to serve one or more applications.

demilitarized zone (DMZ)In the world of software and computer networks, an untrusted network between the enterprise (intranet) and theInternet, and has controlled access restrictions. The DMZ is where Internet application servers (such as web, mailand ftp) are deployed.

DHCPSee Dynamic Host Configuration Protocol.

digital certificateSee certificate.

DMZSee demilitarized zone.

DNSSee Domain Name System.

domainOn the Internet, that segment of an address that specifies an organization, its type, or its country of origin. Ingeneral, the part of a computer network in which the data processing resources are under common control. InTivoli Web Solutions, it is all the elements that enable the core services and applications to function and that aremanaged by an Internet Management Server. This can also be referred to as an administrative domain.

domain nameOn the Web, a domain name is the part of the URL that tells a server using Domain Name System (DNS) whereto forward a request for a web page. A domain name consists of a sequence (at least two) of sub-domain namesseparated by a delineator character. For example, if the fully qualified domain name (FQDN) of a host system isralvm7.vnet.ibm.com, each of the following is a domain name: ralvm7.vnet.ibm.com, vnet.ibm.com, andibm.com.

Domain Name System (DNS)The way that Internet domain names are located and translated into Internet protocol (IP) addresses. Becausemaintaining a central list of domain-name or IP-address correspondences would be impractical, the lists ofdomain names and IP addresses are distributed throughout the Internet in a hierarchy of authority.

Dynamic Host Configuration Protocol (DHCP)A protocol defined by the Internet Engineering Task Force (IETF) that is used for dynamically assigning IPaddresses to computers in a network.

76

E

encryptionA method of encoding messages to provide privacy for communications as they move over intranets or theInternet. Some methods of encrypting, such as 128-bit encryption, are so difficult to break that until veryrecently, US export laws permitted them to be used only within the United States. Tivoli Web Solutions productsuse 128-bit encryption for maximum security.

endpointA specific machine upon which software is installed for the purpose of running applications.

eventIn Tivoli Web Component Manager, an alert, error, or status message generated by management server andapplication operations and displayed on the console. An event informs you when a service or application isfunctioning and notifies you when a constraint has been violated.

event adapterIn a Tivoli Web Solutions environment, software that converts events into a format that the Tivoli EnterpriseConsole (TEC) can use and forwards the events to the TEC event server.

event handlerIn Tivoli Web Solutions products, program code designed to forward the messages generated when events occurto one or more destinations.

event responseThe preconfigured action triggered when an event is generated by a Tivoli Web Solutions application or theInternet Management Server. Event responses can include sending an event to a log file, forwarding notificationto e-mail addresses, or initiating a script.

EXEC event handlerIn Tivoli Web Solutions, the EXEC event handler initiates a user-supplied script or program in response to anevent.

extranetA private, virtual network that uses access control and security features to restrict the usage of one or moreintranets attached to the Internet to selected subscribers (such as personnel from a sponsoring company and itsbusiness partners). See also intranet.

F

firewallA gateway device that protects and controls the connection of one network to other networks. The firewall (a)prevents unwanted or unauthorized communication traffic from entering the protected network and (b) allowsonly selected communication traffic to leave the protected network.

framework servicesSee core services.

fully qualified domain nameIn the Internet suite of protocols, the name of a host system that includes all of the subnames of the domainname. An example of a fully qualified domain name is ralvm7.vnet.ibm.com.

G

Greenwich mean time (GMT)The mean solar time at the prime meridian (0 degrees longitude) of Greenwich, England. Greenwich mean timeis sometimes called Z time or Zulu time. Although Greenwich mean time and coordinated universal time aresometimes used interchangeably, they are not synonyms. Greenwich mean time is an approximate time. Becausethe second is no longer defined in terms of astronomical phenomena, the preferred name for this time scale iscoordinated universal time (UTC).


Glo

ssary

GUISee Tivoli Web Solutions GUI

H

heartbeatA signal that an endpoint sends to the Internet Managment Server to convey that it is still active.

historical data collectionIn the Tivoli Web Solutions products, an application that retrieves information stored in a database so that it canbe formatted and presented in reports to the user.

host nameSee fully qualified domain name.

HTMLSee Hypertext Markup Language.

HTTPSee Hypertext Transfer Protocol.

HTTP proxy serverAn HTTP server that receives requests intended for another server and that acts on the clients behalf (as theclients proxy) to obtain the requested service.

HTTPSSee Hypertext Transfer Protocol Secure.

Hypertext Markup Language (HTML)A markup language that is specified by an SGML document type definition (DTD) and is understood by all webservers

Hypertext Transfer Protocol (HTTP)The protocol that is used to transfer and display hypertext documents. HTTP is the standard web browserprotocol.

Hypertext Transfer Protocol Secure (HTTPS)The standard secure web protocol. This protocol uses Secure Sockets Layer (SSL) encryption.

I

IBM HTTP ServerIBM’s Java servlet-based application environment for building, displaying, and managing web applications.

Internet Management EndpointIn the Tivoli Web Solutions environment, an endpoint consisting of the application it is associated with, theendpoint software, and any additional software the endpoint needs to function. In Tivoli Web Solutions, there arefour endpoint types: Quality of Service (QoS), Web Services Investigator (WSI), Web Services Courier (WSC),and WCM (Web Component Manager).collective term for four different endpoints:

Internet Management ServerIn the Tivoli Web Solutions environment, a server that hosts all of the resources and provides services to all ofthe Tivoli Web Solutions applications. The Internet Management Server works in conjunction with endpoints,web servers, and database servers to provide services to the Tivoli Web Solutions applications and GUI. Alsoknown as the management server and in some of the product code at the TIMS.

Internet protocol (IP) addressThe unique 32-bit address that specifies the location of each device or workstation on the Internet. For example,9.67.97.103 is an IP address.

Internet service provider (ISP)An organization that provides access to the Internet

78

intranetA private network that integrates Internet standards and applications (such as web browsers) with anorganizations existing computer networking infrastructure. See also extranet.

ISPSee Internet service provider.

J

Java Database Connectivity (JDBC)An application programming interface (API) that has the same characteristics as Open Database Connectivity(ODBC) but is specifically designed for use by Java database applications. Also, for databases that do not have aJDBC driver, JDBC includes a JDBC to ODBC bridge, which is a mechanism for converting JDBC to ODBC; itpresents the JDBC API to Java database applications and converts this to ODBC. JDBC was developed by SunMicrosystems, Inc. and various partners and vendors.

Java Development Kit (JDK)A software package that can be used to write compile, debug, and run Java applets and applications.

Java Runtime Environment (JRE)A subset of the Java Development Kit (JDK) that contains the core executables and files that constitute thestandard Java platform. The JRE includes the Java Virtual Machine (JVM), core classes, and supporting files.

Java Virtual Machine (JVM)A software implementation of a central processing unit (CPU) that runs compiled Java code (applets andapplications)

JDBCSee Java Database Connectivity.

JDKSee Java Development Kit.

jobIn Tivoli Web Solutions products, the program-specific task you create through the browser console, such as asite investigation or a web log file collection.

JRESee Java Runtime Environment.

JVMSee Java Virtual Machine.

K

key database file (key.kdb file)A default control file that governs access to secure web servers and the Internet Managment Server. This filecontains the default trusted root certificates supported by IBM, public keys, private keys, certificates, names ofsites, and CAs that are trusted and, therefore, authorized for access. The Internet Managment Server and webservers for the STI Recorder or QoS Monitor endpoint, when installed with secure communications, must be ableto find the key.kdb file so that they can use a certificate from the file for authentication purposes. Alternately, aweb server can be authenticated by a certificate in the KeyRing.class file.

key file passwordThe password for the web servers key file that secures a server. This password is chosen when a certificate ispurchased from a CA and is needed when you start the (secure) web server


Glo

ssary

KeyRing.classA special alternate that has the same properties and content as the key.kdb file. You can create this file bycopying the key.kdb file to the KeyRing.class file name, and then modifying or importing certificates in the file.You can specify that a secure web server installed with either the QoS Monitor or STI Recorder use the alternateKeyRing.class file.

L

log file descriptorA list of object, where each object represents a web log file entry, such that the order and/or format of the logcan be determined.

logical server clusterThe logical name of a cluster of web servers.

M

management repositoryA collection of tables and data that support Tivoli Web Solutions functions in a relational database managementsystem (RDBMS). The management repository is created in the RDBMS during installation.

management serverSee Internet Management Server.

N

NetViewSee Tivoli NetView.

Network File System (NFS)A protocol developed by Sun Microsystems Incorporated, that allows any host in a network to mount anotherhost’s file directories. Once mounted, the file directory appears to reside on the local host.

normalizationA mechanism that prevents spurious threshold events when a numeric attribute crosses and remains near athreshold by creating a buffer zone as a percentage of the threshold that the attribute must leave before therecovery event is triggered.

P

parameterA value or option that is specified to a job so that the job accomplishes its tasks in the way you want.

password stash fileThis file (the key.sth file) stores the encrypted password for the key database file (key.kdb file). You create thefile, also referred to as the stash file, when you first create or (in the case of NT systems) open the key.kdb file.The Internet Managment Server expects to find the encrypted password for the key database in the key.sth file,and it looks for this file in the same directory where the key.kdb file resides. If the management server does notfind the stash file, the server will not work.

PDFSee portable document format.

Portable Document Format (PDF)A standard specified by Adobe Systems, Incorporated, for the electronic distribution of documents. PDF files arecompact; can be distributed globally via e-mail, the Web, intranets, or CD-ROM; and can be viewed with theAcrobat Reader, which is software from Adobe Systems that can be downloaded at no cost from the AdobeSystems home page, which is located at the following URL:http://www.adobe.com

80

proxy serverA server that receives requests intended for another server and acts on the clien’s behalf to access the requestedserver. A proxy server is often used when a client and the server are incompatible for direct connection. Forexample, when the client is unable to meet the security authentication requirements of a server but should bepermitted some service, a proxy with the appropriate access is used. See also HTTP proxy server and SOCKSserver.

Q

Quality of ServiceOne of the applications that make up Tivoli Web Services Manager. It enables users to measure user experienceof a Web site.

QoS endpointThe endpoint used to run Quality of Service jobs.

R

RDBMSSee relational database management system.

realmA name used by a browser in correlation with a URL to save the password information you enter so that it canauthenticate automatically on the next challenge.

relational database management systemA relational database program that contains all the necessary programs, programming tools, and documentationneeded to create, install, and maintain custom database applications.

RURLRelative Uniform Resource Locator. A string of characters that gives a resources file name, but does not specifyits exact location. See URL.

S

Secure Sockets Layer (SSL)A secure protocol that allows data to be encrypted and enables clients to authenticate a server in client-servercommunication.

servletSee Java servlet.

severity levelDesignates the importance assigned to an event. It determines the event response, or action, that the system willtake, from logging the event to forwarding notification of the event to an e-mail address. There are six levels,ranging from Unknown (lowest) to Error (highest).

Simple Mail Transfer Protocol (SMTP)In the Internet suite of protocols, an application protocol for transferring mail among users in the Internetenvironment. SMTP specifies the mail exchange sequences and message format. It assumes that the TransmissionControl Protocol (TCP) is the underlying protocol.

Simple Network Management Protocol (SNMP)In the Internet suite of protocols, a network management protocol that is used to monitor routers and attachednetworks. SNMP is an application layer protocol. Information on devices managed is defined and stored in theapplications Management Information Base (MIB).

Site InvestigatorOne of the applications that make up Tivoli Web Services Manager. It enables users to verify the thealth andcontent of their Web sites.


Glo

ssary

SMTPSee Simple Mail Transfer Protocol.

SNMPSee Simple Network Management Protocol.

SOCKS serverA circuit-level gateway that provides a secure one-way connection through a firewall to server applications innetwork that is not secure.

SSLSee Secure Sockets Layer.

stash fileSee password stash file.

STI Playback (STIP)See Synthetic Transaction Investigator

STI Recorder (STIR)See Synthetic Transaction Investigator

Synthetic Transaction InvestigatorOne of the applications that make up Tivoli Web Services Manager. It enables users to measure Web transactionsfrom the user’s perspective. The Synthetic Transaction Investigator is made up of two parts: the SyntheticTransaction Investigator Recorder, which records Web transactions, and the Synthetic Transaction InvestigatorPlayback, which plays the recorded transactions back from various endpoints.

T

tablespaceIn relational database management systems, an abstraction of a collection of containers in which database objectsare stored.

TCP/IPSee Transmission Control Protocol/Internet Protocol.

TECSee Tivoli Enterprise Console.

timeoutA time interval allotted for certain operations to complete; for example, the period of time allotted for a responsebefore a system operation is interrupted and must be restarted.

time stampThe value on an object that is an indication of the system time at some critical point in the history of the object.

Tivoli Enterprise Console (TEC)A Tivoli Enterprise product that collects, processes, and automatically initiates corrective actions for system,application, network, and database events; it is the central control point for events from all sources. The TivoliEnterprise Console provides a centralized, global view of the network computing environment; it uses distributedevent monitors to collect information, a central event server to process information, and distributed eventconsoles to present information to system administrators.

Tivoli NetViewA Tivoli product that enables distributed network management across multiple operating systems and protocols.Unlike Tivoli NetView for OS/390, Tivoli NetView does not provide centralized management from an OS/390host.

Tivoli Web Component ManagerOne of the Tivoli Web Solutions products. It monitors and manages the software and machines that provideweb-based services.

82

Tivoli Web Services ManagerA product suite containing three applications: Quality of Service, Site Investigator, and Synthetic TransactionInvestigator. It provides users with tools to measure the availability and performance of their Web sites.

Tivoli Web Servics AnalyzerA companion application to Tivoli Web Services Manager. It enables the downloading of log data to the datawarehouse so that the data can be used to create Tivoli Decision Support reports.

Tivoli Web Solutions GUIThe Tivoli Web Solutions desktop. The GUI is the graphical user interface where basic operations to manage theenvironment are performed. The GUI displays and organizes applications, jobs, events, and logs.

topicIn Tivoli Decision Support, the overall question for which database views are created to answer.

Transmission Control Protocol/Internet Protocol (TCP/IP)(1) The Transmission Control Protocol and the Internet Protocol, which together provide reliable end-to-endconnections between applications over interconnected networks of different types.(2) The suite of transport and application protocols that run over the Internet Protocol.

trusted rootIn the Secure Sockets Layer (SSL), the public key and associated distinguished name of a certificate authority(CA).

U

Uniform Resource IdentifierIn HTTP, a string of characters that identifies an Internet resource, including the resource type and its location.There are two types of URIs: Uniform Resource Locators and relative URLs (RURLs).

Uniform Resource LocatorA string of characters that precisely identifies and Internet resources type and location. Every URL consists of adomain name, a description of the resources location, and the name of the resource itself, separated by full stopsand backslashes.

URISee Uniform Resource Identifier.

URLSee Uniform Resource Locator.

UTCSee Greenwich Mean Time.

W

Web Component Manager (WCM) endpointThe endpoint from which Tivoli Web Component Manager monitoring and management jobs are run.

Web Services Courier (WSC) endpointThe endpoint from which Tivoli Web Services Manager TEC forwarding and historical reporting jobs, as well asTivoli Web Services Analyzer jobs are run.

Web Services Investigator (WSI) endpointThe endpoint from which Tivoli Web Services Manager site investigations and Synthetic Transaction Investigatorplayback jobs are run.


Glo

ssary

Index

Aapplication data

managingin Web Services Manager 60

application jobsconfiguring to run continuously 51configuring to run once 52configuring to run repeatedly 52scheduling 51

Bbooks

feedback viiionline viiiordering viii

Ccommands

ims_purgedb 33using ims_purgedb 33

Configuring Web Log Files for NES/iPlanet Servers 6, 7correlating data 1cubes 1Customer Support ix

Ddata

deleting from management repository 34data management

using the data management repository 33Data Warehouse 2database

error messages 69

Ee-mail account

forwarding events to 39e-mail accounts

forwarding events to 24e-mail contact ix

endpointsviewing all

in global view 57event forwarding

configure the management server for 37event responses

about creating 60about managing 21creating 22defined 21options

defined 21event service

manage 37event.properties

files 39events

about managing 21application

defined 21configuring 28configuring system types of

in Web Services Manager 57defined 21forwarding data using EXEC service 26forwarding to an e-mail account 24, 39forwarding to an SNMP management application 24, 38forwarding to the EXEC service 25forwarding to the Tivoli Enterprise Console 37forwarding to Tivoli Enterprise Console 23severity levels 28

defined 21stored in management respository 21system

defined 21, 29, 30, 31system types

configuring for Web Services Manager 59viewing in Web Services Manager 59

system types definedfor Web Services Manager 57, 58, 59

types defined 21, 22, 29view global log 59viewing all global

in global view 56Web Services Analyzer types

defined 31EXEC service

forwarding event data to 26forwarding events to 25


Ind

ex

Ffeedback about publications ixfiles

event.properties 39ims_purgedb command 33

using 33timsiu.log 66uilogging.properties 66

forwarding eventsto an e-mail account 39to an SNMP management applicatione 38to the Tivoli Enterprise Console 37

Gglobal event log

view 59global view

viewing all endpoints 57viewing all jobs 56viewing global event log 56

global viewsin portfolio

defined 55GUI

overview 11parts defined 12procedure for starting 11viewing navigation tree choices 12Web Services Manager

about 55

Iims_purgedb command file 33

using 33

Jjobs

configuring application types to run repeatedly 52configuring to run continuously for applications 51scheduling application types to run once 52scheduling for applications 51viewing all in global view 56

Mmanagement repository

deleting data from 34used for storing events 21using to manage data 33

manualsfeedback viiionline viiiordering viii

messagesdatabase error 69reporting error 73Tivoli Web Console Manager 69

Nnavigation tree

viewing choices from GUI 12

Oonline publications viiiordering publications viii

Pportfolio

global view categorydefined 55

system administration categorydefined 55

user preferences categorydefined 55

publicationsfeedback viiionline viiiordering viii

Rreporting

error messages 73

Sserver types

SOCKS 39severity levels

for events 28SMTP handler

using to forward events 39SNMP

forwarding events to 24SNMP management application

forwarding events to 38

86

SOCKSserver types 39

Solarisusing the command line to stop and restart the Internet

Management Server 40system administration

in portfoliodefined 55

system event logsviewing

in Web Services Manager 59system event types

defined 29, 30, 31system events

configuringfor Web Services Manager 59

configuring in Web Services Manager 57types defined

for Web Services Manager 57, 58, 59

Ttimsiu.log

user interface log file 66Tivoli Customer Support ixTivoli Decision Support 2Tivoli Discovery Administrator 1Tivoli Discovery Interface 1Tivoli Enterprise Console

event forwarding to 23forwarding events to 37

Tivoli Error Message Standardabout 68

Tivoli Web Console Managermessages 69

Tivoli Web Services Analyzer 1Tivoli Web Services Manager 1

Uuilogging.properties

user interface tracing file 66user accounts

managingin Web Services Manager 60

user interface log filetimsiu.log 66

user interface tracing fileuilogging.properties 66

user preferencesin portfolio

defined 55

Wweb log files

Apache 5collecting 2configuring 2IIS 3

Web Services Analyzerevent types

defined 31Web Services Courier 2Web Services Manager

configuring system event types 59configuring system events 57GUI

overview 11managing application data 60managing user accounts 60navigation

overview 11system events

defined 57, 58, 59viewing system event types 59

Web Services Manager GUIabout 55

Windows NTusing to stop and restart the Internet Management

Server 40


Ind

ex

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0743-00

tivoli web services analyzer - ibmpublib.boulder.ibm.com/...userguide/.../twsamst.pdf · tivoli web...

Documents