Deployment Guide Series IBM Tivoli Composite Application Manager For Web Resources V6.2 Sg247485

Front cover
Deployment Guide Series: IBM Tivoli Composite Application Manager for Web Resources V6.2
Manage Web application server resource performance Extensive deployment and usage scenarios Solution development guide included
Budi Darmawan Andri Firtiyan Ronaldo Pires
ibm.com/redbooks
International Technical Support Organization Deployment Guide Series: ITCAM for Web Resources V6.2 January 2008
SG24-7485-00
Note: Before using this information and the product it supports, read the information in Notices on page vii.
First Edition (January 2008) This edition applies to Version 6, Release 2, Modification 0 of IBM Tivoli Composite Application Manager for Web Resources (product number 5724-S32).
Copyright International Business Machines Corporation 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Part 1. Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Solution introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Application server monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 ITCAM for Web Resources features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 ITCAM for Web Resources value propositions . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Architecture and interconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4.1 J2EE and WebSphere data collectors . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4.2 Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Chapter 2. Solution environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1 Hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2 Software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2.1 WebSphere agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.2 J2EE agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.3 Web server agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3 Sizing consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.4 Typical deployment environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.4.1 Demonstration or proof of concept . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.4.2 Small and medium environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4.3 Large and very large environment . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Chapter 3. Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.1 Required skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.2 Solution description and assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.3 Task breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.1 Project kick off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.2 Environment preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.3 IBM Tivoli Monitoring setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.4 Application support files installation . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.3.5 Agents and data collectors setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Copyright IBM Corp. 2008. All rights reserved.
iii
3.3.6 Customizing the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.3.7 Demonstrating the solution and skill transfer . . . . . . . . . . . . . . . . . . 29 Part 2. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Chapter 4. Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.2 Installing application support files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.3 Installing the Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . . . . 44 4.4 Installing the data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 4.4.1 Setting up the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.4.2 Installing the base data collector version 6.1 . . . . . . . . . . . . . . . . . . 54 4.4.3 Applying Fix Pack 1 and interim Fix 4 . . . . . . . . . . . . . . . . . . . . . . . . 61 4.4.4 Configuring data collectors in the application servers . . . . . . . . . . . . 62 4.5 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Chapter 5. Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 5.1 Usage scenario overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 5.2 Using the workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 5.3 Defining application health and baseline. . . . . . . . . . . . . . . . . . . . . . . . . . 84 5.4 Working with situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Chapter 6. Troubleshooting hints and tips . . . . . . . . . . . . . . . . . . . . . . . . 101 6.1 IBM Tivoli Monitoring logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 6.2 ITCAM for Web Resources logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Part 3. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Appendix A. The Trader application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Application components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Front-end J2EE Web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Back end implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Back end J2EE server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Initial setup for the demonstration server . . . . . . . . . . . . . . . . . . . . . . . . . 114 DB2 database creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 WebSphere server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 WebSphere client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Appendix B. Sample statement of work . . . . . . . . . . . . . . . . . . . . . . . . . . 117 ITCAM for Web Resources implementation service. . . . . . . . . . . . . . . . . . . . 118 Executive summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Solution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
iv
Deployment Guide Series: ITCAM for Web Resources V6.2
Business partner responsibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Client responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Staffing estimate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Project schedule and milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Testing methodology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Completion criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Appendix C. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 System requirements for downloading the Web material . . . . . . . . . . . . . 122 How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Contents
vi
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
vii
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Redbooks (logo) developerWorks z/OS AIX CICS DB2 Universal Database DB2 IBM IMS MVS Netcool OMEGAMON Redbooks System p System x System z Tivoli Enterprise Tivoli WebSphere Workplace
The following terms are trademarks of other companies: SAP NetWeaver, SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries. Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its affiliates. EJB, Java, Java Naming and Directory Interface, JDBC, JDK, JMX, JSP, JVM, J2EE, J2SE, Solaris, Sun, Sun Java, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Itanium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
viii
Preface
This book is written as part of the deployment guide series. It provides a step-by-step guide for deploying IBM Tivoli Composite Application Manager (ITCAM) for Web Resources V6.2. This deployment guide will help an IBM Business Partner or service person plan and perform the deployment of the product. The discussion on ITCAM for Web Resources describes product architecture and components, planning and sizing considerations, and guidelines on setting up service engagements. Although the information is highly relevant for larger deployment engagements, it is also suitable for a small deployment system. The extensive deployment and usage scenarios can also help you demonstrate the product.
The team that wrote this book

This book was produced by a team of specialists from around the world working at the International Technical Support Organization, Austin Center, Texas. Budi Darmawan is a Project Leader at the International Technical Support Organization, Austin Center. He writes extensively and teaches IBM classes worldwide on all areas of systems management, primarily application management, business service management, and workload scheduling. Before joining the ITSO in 1999, Budi worked in IBM Indonesia as a lead implementor and solution architect. His current interests are J2EE and service-oriented architecture (SOA) application management, z/OS integration, and business service management. Andri Firtiyan is a Solution Architect at Software Lab Services based in IBM Indonesia. He has 11 years experience in IT. He holds a Masters degree in Computer Science from the University of Indonesia. He was involved in the first SOA Offering Roadmap project in the ASEAN region. He is an IBM Certified SOA Solution Designer. His current focus is Tivoli Best Practice, Tivoli Business Automation, and SOA. Ronaldo Pires is an IBM IT Specialist. He joined IBM in 2004 and has been working on Global Technology Services Delivery in So Paulo, Brazil, supporting the systems management infrastructure for IBM outsourcing customers. His skills include IBM Tivoli Framework , IBM Tivoli Monitoring, IBM Tivoli Storage
ix
Manager, IBM Tivoli Identity Manager, Altiris Client Management Suite, BMC Control-M for z/OS, and BMC Control-D for z/OS. He holds a Bachelors degree in Mathematics from Faculdade de Filosofia Cincias e Letras de Santo Andr. He is Tivoli Certified Consultant for Tivoli Storage Manager and IBM Certified Deployment Professional for Tivoli Monitoring V5.1.2. Thanks to the following people for their contributions to this project: Dorothy Wu IBM developerWorks, Silicon Valley Lab Terry Copeland IBM Software Group
Become a published author

Join us for a two- to six-week residency program! Help write a book dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will have the opportunity to team with IBM technical professionals, Business Partners, and Clients. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us! We want our books to be as helpful as possible. Send us your comments about this book or other IBM Redbooks publications in one of the following ways: Use the online Contact us review form found at: ibm.com/redbooks Send your comments in an e-mail to: redbooks@us.ibm.com
Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
Preface
xi
xii
Part 1
Part
Planning
This part discusses planning information for deploying IBM Tivoli Composite Application Manager (ITCAM) for Web Resources V6.2.
Chapter 1.
Solution introduction
This chapter introduces the solution based on IBM Tivoli Composite Application Manager (ITCAM) for Web Resources V6.2. This chapter includes the following topics: Application server monitoring on page 4 ITCAM for Web Resources features on page 4 ITCAM for Web Resources value propositions on page 5 Architecture and interconnection on page 5
1.1 Application server monitoring

Businesses are relying more on a Web-based application environment. This environment is based on J2EE application servers that serve Web browser requests or Web services requests. J2EE application servers are monolithic Java Virtual Machines (JVM) that have limited performance management function. Typical interfaces for performance management of J2EE servers are Performance Monitoring Infrastructure (PMI) and Java Management eXtension (JMX). Performance management of Web-based applications covers: J2EE application server resource analysis and understanding CPU and memory usage of an application server related to its activities, such as request rate and active processing. J2EE application individual performance with applications that are deployed in J2EE servers. These applications are not typically understood by users. Their performance must be monitored to pinpoint potential resource problems. Web server sessions and error statistics to identify the request mix and statistics for the Web servers. This helps understand access pattern of the static part of the Web site.
1.2 ITCAM for Web Resources features

ITCAM for Web Resources V6.2 allows simple monitoring of a Web applications resources, including Web servers, WebSphere servers, and other J2EE application servers. It proactively monitors health and availability of Web servers, application servers, and J2EE applications. J2EE application problems are viewed in context of the application so you can quickly drill down for problem determination. This allows for a quick identification and potentially fixing the problem before it impacts the users. ITCAM for Web Resources can dynamically monitor the threshold. This also allows to set a baseline threshold for a normal behavior of the application. The set baseline allows fewer situations to be fired as the settings are set from the application itself. With the IBM Tivoli Monitoring integrated environment, ITCAM for Web Resources allows correlation of situations from various resources with automated actions and expert advice. This provides a quicker resolution of problems and reduces event storms.
ITCAM for Web Resources uses Tivoli Enterprise Portal as its primary interface. This allows a common user interface for data and events integration with other Tivoli Enterprise Portal-based solutions from IBM Tivoli Composite Application Manager, IBM Tivoli Monitoring, and IBM Tivoli OMEGAMON to provide comprehensive management of business applications.
1.3 ITCAM for Web Resources value propositions

ITCAM for Web Resources provides the following business values: Increased operational efficiency: Training is minimized as the product does not require programming expertise. Solution is highly scalable and helps manage large environments. Automated troubleshooting helps deliver fast time-to-resolution. Achieve rapid return on investment. Product deploys quickly and easily. Heterogeneous environments support manages a complex mix of tools. Improved customer satisfaction: Developing application and service problems are detected before they result in brownouts and blackouts. Enhance service visibility. Operators can discern the service and business-level impact of events. Users gain cross-platform visibility and impact analysis capabilities needed to prioritize responses and improve service availability. Real time status of an applications health.
1.4 Architecture and interconnection

ITCAM for Web Resources monitors the applications performance for J2EE application servers. It collects performance metric using a data collector and forwards the information by using the IBM Tivoli Monitoring V6.1 infrastructure.
Chapter 1. Solution introduction
The application servers run the data collector, which is a collecting agent that runs in the application server and sends monitoring information, using Tivoli Enterprise Monitoring Agent, to the Tivoli Enterprise Monitoring Server. These data collectors operate independently of each other. Figure 1-1 shows the overall architecture of ITCAM for Web Resources.
Tivoli Enterprise Monitoring Agent
Application servers with Data collectors
Tivoli Enterprise Management Server and Tivoli Enterprise Portal Server
Figure 1-1 ITCAM for Web Resources architecture
The product consists of two main parts: the data collectors and the Tivoli Enterprise Monitoring Agents. A data collector agent runs on each monitored J2EE application servers and communicates with the Tivoli Enterprise Monitoring Agent. The Tivoli Enterprise Monitoring Agent sends the performance information to Tivoli Enterprise Monitoring Server for display on Tivoli Enterprise Portal.
1.4.1 J2EE and WebSphere data collectors

The data collectors run inside the application servers. They use native system services. They are tailored for particular environments where they are executed.
Data collectors are configured as a multi-threaded process. They consist of the following agents: Command agent: The command agent collects requests from other components for information about EJB invocations, database connection pools, thread pools, stack traces, memory analyses, and heap dumps. Event agent: The event agent provides data to the publish servers according to polling frequencies. This data includes system initialization data, application request-level data, and application method-level data. Collector process: The collector provides the monitoring data for Tivoli Enterprise Portal. It collects WebSphere Application Server and other J2EE application server performance metrics. This component communicates with Tivoli Enterprise Monitoring Agent using a TCP/IP port. The data collectors send probes into the application servers to analyze the applications performance. The probes collect monitoring data and feed it to transport routines for Tivoli Enterprise Monitoring Agent. This relieves the processing burden of ITCAM for Web Resources from the application servers as much as possible. The data collectors and probes are not designed to analyze or interpret data. They collect and route such data to Tivoli Enterprise Monitoring Agent. The data sources used by the ITCAM for Web Resources data collector are: JVMTI garbage collection data, method trace, stack trace, CPU time, and heap dump. jJMX system resources. PMI system resources (WebSphere only). OS services, platform CPU, and its environment. Byte Code Instrumentation (BCI) for some classes.
Chapter 1. Solution introduction
The data collector in the J2EE server runs as a custom service called am. Figure 1-2 shows the WebSphere data collector structure.
WebSphere
JVMTI JMX PMI
BCI
Custom Service am
Tivoli Enterprise Monitoring Agent
KYN
To TEMS
Figure 1-2 Data collector structure
1.4.2 Tivoli Enterprise Monitoring Agent

The ITCAM for Web Resources Tivoli Enterprise Monitoring Agent forwards information to the Tivoli Enterprise Monitoring Server for monitoring the use of Tivoli Enterprise Portal. For monitoring Web servers, you can also use Tivoli Enterprise Monitoring Agent for Web Servers. You do not need a data collector to monitor Web servers.
Chapter 2.
Solution environment
This chapter discusses the required environment for implementing ITCAM for Web Resources V6.2. The topics are: Hardware prerequisites on page 10 Software prerequisites on page 11 Sizing consideration on page 14 Typical deployment environments on page 20
2.1 Hardware prerequisites

The hardware requirement for ITCAM for Web Resources relates to the requirement of IBM Tivoli Monitoring V6.1. For IBM Tivoli Monitoring servers, such as Tivoli Enterprise Monitoring Server or Tivoli Enterprise Portal Server, the recommended processor speeds are at minimum of 1 GHz for RISC architectures and 2 GHz for Intel architectures. A single processor is suitable when the components are installed on separate computers. Table 2-1 lists the memory and disk requirements for IBM Tivoli Monitoring servers.
Table 2-1 IBM Tivoli Monitoring memory and disk requirements Component Hub monitoring server Remote monitoring server Tivoli Enterprise Portal server Tivoli Enterprise Portal client Tivoli data warehouse Warehouse proxy agent Summarization and pruning agent Memory requirementa 70 MB - 100 MB 100 MB - 300 MB 100 MB - 300 MB 150 MB - 300 MB 2 GB - 8 GB 50 MB - 100 MB 150 MB - 300 MB Disk space requirement 650 MB 250 MB 800 MB 150 MB Must be calculatedb 150 MB 150 MB
a. Memory requirement is range based on the processing needs. The low end is for around 100-200 monitoring agents, while the high end is for around 500-1000 monitoring agents. b. The data size of Tivoli Data Warehouse depends on the size of data for each attribute groups. For each attribute groups, you need the number of detailed records per day, the data size per record, and the aggregation policy. See the Tivoli Monitoring Information Center at: http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm. itm.doc/itm_install65.htm#estimate
The hardware requirement for IBM Tivoli Monitoring servers is discussed in detail at: http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.i tm.doc/itm_install61.htm#hardware
10
For more information about configuring IBM Tivoli Monitoring servers, see Deployment Guide Series: IBM Tivoli Monitoring 6.1, SG24-7188. Specifically for ITCAM for Web Resources, the agents have additional requirements for memory and disk spaces. These additional requirements are on top of any existing hardware requirement for the supported monitored environment. These monitored environments are listed in section 2.2, Software prerequisites on page 11. Table 2-2 lists the minimum and recommended memory and disk requirements.
Table 2-2 Requirements Resource Additional memory Additional disk space (monitoring agent) 100 MB 512 MB 100 MB Additional disk space (data collector) 330 MB 1 GB -
WebSphere agent J2EE agent Web server agent
128 MB 512 MB -
For the most up-to-date prerequisites, see the following Information Centers: For WebSphere agents: http://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HT ML/itcam6.html For J2EE agents: http://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTM L/itcam6.html For Web server agents: http://publib.boulder.ibm.com/tividd/td/ITCAMWRWServers/prereq62/en_ US/HTML/itcam6.html
2.2 Software prerequisites

ITCAM for Web Resources V6.2 requires the implementation of IBM Tivoli Monitoring V6.1 with Fix Pack 5 or later. Additional software requirements for ITCAM for Web Resources V6.2 are discussed in the following sections: Section 2.2.1, WebSphere agent on page 12 Section 2.2.2, J2EE agents on page 12 Section 2.2.3, Web server agents on page 13
Chapter 2. Solution environment
11
2.2.1 WebSphere agent

The WebSphere agent is supported on the following operating systems: Windows 2000 Server and Advanced Server with Service Pack 4 or later Windows Server 2003 Standard, Enterprise, and Data Center editions AIX 5.2 or 5.3 Solaris 8, Solaris 9 cluster, and Solaris 10 HP-UX 11.iv1 32-bit on PA-RISC platform HP-UX 11.iv2 (32bit and 64-bit) on PA-RISC and Itanium RHEL 4.0 and 5.0 on System x, System p, and System z SLES 9 and SLES 10 on System x, System p, and System z Note: For operating system specific requirement and WebSphere levels, see the prerequisites page at: http://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HT ML/itcam6.html The supported WebSphere software levels are: WebSphere Application Server 5.1.0 and 5.1.1.14 with JDK 1.4.2_7, Base and Network Deployment versions WebSphere Application Server 6.0.x Base and Network Deployment version (all except 6.0.0.1) WebSphere Application Server 6.1 Base and Network Deployment version; verbose class loading is only supported in version 6.1.0.1 or later WebSphere Application Server Community Edition 1.0 (only with Windows 2003 Server SP1) WebSphere Portal Server 5.1.x WebSphere Portal Server 6.x WebSphere Process Server 6.0 and 6.0.1 Workplace Collaboration Services Mail Server 2.6.x (only the Mail Server component of this application server is monitored, in Windows and AIX platforms) WebSphere Enterprise Service Bus 6.0.1
2.2.2 J2EE agents

The J2EE agents are supported on the following operating systems: Windows 2000 Server and Advanced Server with Service Pack 4 or later Windows Server 2003 Standard, Enterprise, and Data Center editions
12
AIX 5.2 or 5.3 Solaris 8, Solaris 9 cluster, and Solaris 10 HP-UX 11.iv1 32-bit on PA-RISC platform HP-UX 11.iv2 (32-bit and 64-bit) on PA-RISC and Itanium RHEL 4.0 and 5.0 on System x and System p SLES 9 and SLES 10 on System x and System p Note: For operating system specific requirements and J2EE application server levels and Java Runtime Environment versions, see the prerequisites page at: http://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTM L/itcam6.html The following J2EE container servers are supported: SAP NetWeaver 04 SR1 Oracle 9i Application Server R2 (9.0.3) - 32bit only Oracle 10i Application Server R2 (10.1.2) - 32bit only J2SE (standalone Java applications) WebLogic Server 8.1 SP5 (32-bit only) WebLogic Server 9.1 (64-bit support for only AMD64 and EM64/T) JBoss Application Server 3.2.7 JBoss Application Server 4.0.3 SP1 TomCat 5.0.28 TomCat 5.5.12
2.2.3 Web server agents

The combination of the supported Web servers are: Apache Web Server 2.2, on the following operating systems: Windows Server 2003 (Standard) AIX 5.2 and 5.3 (32-bit and 64-bit) Solaris 9 and 10 (32-bit and 64-bit) HP-UX 11iv1 (32-bit and 64-bit) for PA-RISC and Itanium 2 only Linux on System x: RHEL 4.0 update 3 and later Linux on System x: SLES 9
Microsoft Internet Information Server Web Server 6.0 on Windows Server 2003 (Standard) SP1 Sun Java System Web Server 6.1 on the following operating systems: Windows Server 2003 (Standard) AIX 5.2 (32-bit and 64-bit) Solaris 9 (32-bit and 64-bit) must apply SP6 on the Web server
13
HP-UX 11iv1 (32-bit and 64-bit), only for PA-RISC and Itanium 2
2.3 Sizing consideration

The size for data warehouse tables for ITCAM for Web Resources V6.2 is explained in Appendix A of the agent installation guide manuals. We provide those sizes in Table 2-3 for easy reference.
Table 2-3 Historical data sizing information for WebSphere agents Table name Object name Size in bytes 616 968 1068 772 880 1040 812 1060 1320 812 588 952 972 1064 864 Recording frequency
KYNPREV KYNAPSST KYNLOGANAL KYNAPSRV KYNCONTNR KYNEJB KYNCNTROP KYNAPP KYNSERVLT KYNTRANS KYNCACHE KYNCACHT KYNJ2C KYNSERVS KYNTHRDP
WebSphere Agent Events Application Server Status Log Analysis Application Server EJB Containers Enterprise Java Beans Container Object Pools Web applications Servlets and JSPs Container Transactions Dynamic Cache Dynamic Cache Templates J2C Connection Pools Servlet Sessions Thread Pools
1 record for each product event. These records are written when problems occur. 1 record per interval per server instance 1 record per interval for each entry written into the application server log stream or file 1 record per interval per application server 1 record per interval per application server, plus 1 record per interval per EJB container 1 record per interval for each EJB method 1 record per interval per application server, plus 1 record per interval per EJB container 1 record per interval per Web application 1 record per interval per servlet 1 record per interval per application server plus 1 record per interval per EJB container 1 record per cache per cycle 1 record per cache template per cycle 1 record per J2EE connection pool per cycle 1 record per servlet session per interval 1 record per thread pool per interval
14
Table name
Object name
Size in bytes 592 632 732 616 656 1468 1240 1156 852 976 1096 1388
Recording frequency
KYNWLMCL KYNWLMSR KYNGCACT KYNGCAF KYNGCCYC KYNREQUEST KYNREQSEL KYNDATAS KYNJMSSUM KYNREQHIS KYNDBCONP KYNDCMSG
Workload Management Client Workload Management Server Garbage Collection Analysis Allocation Failure Garbage Collection Cycle Request Analysis Selected Request Datasources JMS Summary Request times and rates DB Connection Pools Data Collector (DC) Messages WebSphere Distribution and Consistency Services (DCS) Stack High Availability Manager Web Services Gateway
1 record per Workload Management (WLM) client per interval 1 record per WLM server per interval 1 record per interval per application server 1 record per interval for each allocation failure block 1 record per garbage-collection cycle per interval 1 record per interval for each workload in each application server 1 record per interval for each workload degradation in each application server 1 record per interval per data source in each application server 1 record per interval per MQ queue in each application server 1 record per interval per WebSphere Application Server 1 record per datasource per interval plus 1 record per application server per interval 1 record per each entry written into DC log message file 1 record per DCS stack per interval plus 1 record per application server per interval 1 record per application server per interval 1 record per Web Services Gateway per interval plus 1 record per application server per interval
KYNDCSSTK
1032
KYNHAMGMT KYNWEBSGW
724 968
15
Table name
Object name
Size in bytes 1004 980 1000 1220 1504 1004 972 1040 1752
Recording frequency
KYNWEBSVC KYNALARMM KYNSCHED KYNCLICOM KYNDURSUB KYNMECOM KYNMSGENG KYNMSGQUE KYNSVCOMEL
Web Services Alarm Manager Scheduler Client Communications Durable Subscriptions Messaging Engine Communications Messaging Engines Queue Service Component Elements Service Components Topic Spaces WMQ Client Link Communications WMQ Link Communications Workplace Mail Service Workplace Mail Queues Workplace Mail IMAP/POP Portal Summary Portal Page Summary
1 record per Web Service per interval plus 1 record per application server per interval 1 record per Work Manager per interval plus 1 record per application server per interval 1 record per Scheduler per interval plus 1 record per application server per interval 1 record per application server per interval 1 record per Durable Subscription per interval 1 record per application server per interval 1 record per Messaging Engine per interval plus 1 record per application server per interval 1 record per Queue per interval 1 record per Service Component Element per interval plus 1 record per application server per interval 1 record per Service Component plus 1 record per application server 1 record per Topic Space per interval 1 record per application server per interval 1 record per application server per interval 1 record per application server per interval 1 record per Mail Queue per interval 1 record per protocol (IMAP/POP) per interval 1 record per application server per interval 1 record per Portal Page per interval plus 1 record per application server
KYNSVCCOMP KYNTOPICSP KYNWMQCL KYNWMQLINK KYNWPMSV KYNWPMQM KYNWPMIP KYNWPTALS KYNWPPAGE
704 1288 988 1004 776 712 720 760 832
16
Table name
Object name
Size in bytes 836 1008 n/a n/a n/a
Recording frequency
KYNWPLETS KYNAPHLTH KYNAPMONCF KYNRQMONCF KYNBASELN
Portlet Summary Application Health Status Application Monitoring Configuration Requests Monitoring Configuration Baseline
1 record per portlet per interval plus 1 record per application server 1 record per interval per application for each application server Not historical table Not historical table Not historical table
Table 2-4 shows the sizing list for J2EE agents.

Table 2-4 Historical data sizing information for J2EE agent Table name KYJAPHLTH KYJAPMONCF KYJAPSRV KYJAPSST KYJBASELN KYJDATAS KYJDCMSG KYJEJB KYJGCACT KYJGCAF Object name Application Health Status Application Monitoring Configuration Application Server J2EE Application Server Status - J2EE Baseline Datasources - J2EE DC Message - J2EE Enterprise Java Bean Modules - J2EE Garbage Collection Analysis - J2EE Allocation Failure J2EE Size 1008 n/a 764 968 n/a 1284 1388 1020 736 744 Recording frequency 1 record per interval per application for each application server Not historical table 1 record per interval per application server 1 record per interval per server instance Not historical table 1 record per interval per data source in each application server 1 record per each entry written into DC log message file. 1 record per JSR77 EJB module per interval plus 1 record per application server 1 record per interval per application server 1 record per interval for each allocation failure block
17
Table name KYJGCCYC KYJJCACP KYJJDKJVM KYJJDKMEM KYJJDKOS KYJJDKTHR KYJJMSSUM KYJJTARES KYJLOGANAL KYJPREV KYJREQHIS KYJREQSEL KYJREQUEST KYJRQMONCF KYJSDBCON KYJSEJB KYJSERVLT KYJSJTASUM
Object name Garbage Collection Cycle - J2EE JCA Connection Pools J2EE JDK - JVM JDK - Memory JDK - Operation System JDK - Threading JMS Summary - J2EE JTA Resources - J2EE Log Analysis - J2EE J2EE Agent Events Request times and rates - J2EE Selected Request J2EE Request Analysis J2EE Requests Monitoring Configuration DB Connection Pools NetWeaver Enterprise Java Bean Service - NetWeaver Servlets and JSPs J2EE JTA Summary NetWeaver
Size 784 1016 1732 724 1484 1224 960 960 1068 704 976 1368 1184 n/a 972 1152 972 708
Recording frequency 1 record per garbage collection cycle per interval 1 record per JSR77 JCA resource per interval plus 1 record per application server 1 record per interval for each application server 1 record per interval for each application server 1 record per interval for each application server 1 record per interval for each application server 1 record per interval per MQ queue in each application server 1 record per JSR 77 JTA Resource per interval plus 1 record per application server 1 record per interval for each entry written into the application server log stream or file 1 record for each product event. These records are written when problems occur. 1 record per interval per J2EE server 1 record per interval for each workload degradation in each application server 1 record per interval for each workload in each application server Not historical table 1 record per DB connection pool per interval plus 1 record per application server 1 record per EJB per interval plus 1 record per application server 1 record per interval per servlet 1 record per application server per interval
18
Table name KYJSWEBCNT KYJWEBAPP KYJWLCCPL
Object name Web Container NetWeaver Web applications J2EE J2EE Connector Connection Pools WebLogic JDBC Connection Pools - WebLogic Enterprise Java Beans - WebLogic Enterprise Java Bean Components WebLogic JMS Sessions WebLogic Java Transaction Service - WebLogic Servlets and JSPs WebLogic Web Applications WebLogic
Size 716 836 884
Recording frequency 1 record per application server per interval 1 record per interval per Web application 1 record per J2C connection pool per interval plus 1 record per application server 1 record per JDBC connection pool per interval plus 1 record per application server 1 record per EJB per interval plus 1 record per EJB component, plus 1 record per application server 1 record per EJB component per interval plus 1 record per application server 1 record per JMS session per interval plus 1 record per application server 1 record per application server per interval 1 record per Servlet or JSP per interval plus 1 record per Web Application, plus 1 record per application server 1 record per Web Application per interval plus 1 record per application server
KYJWLDBCON KYJWLEJB
900 1176
KYJWLEJBC
968
KYJWLJMSS KYJWLJTA KYJWLSRVLT
1088 900 1628
KYJWLWEBAP
1296
Table 2-5 lists the sizing list for Web server agents.
Table 2-5 Historical data sizing information for Web server agent Table name KHTAWEBSR KHTAWEBST KHTEVNT KHTIWEBSR KHTIWEBST Object name Apache Web server Apache Web sites Web Servers Agent Events Web server Web sites Size 1056 984 616 928 1528 Recording frequency 1 per interval per server 1 per interval per site Depends on messages count from Tivoli Enterprise Monitoring Agent (TEMA) 1 per interval per server 1 per interval per site
19
Table name KHTSWEBSR KHTSWEBST KHTWSRS
Object name Sun Web server Sun Web sites Web Servers status
Size 2704 1168 1028
Recording frequency 1 per interval per server 1 per interval per site 1 per interval
2.4 Typical deployment environments

This section discusses deployment considerations for ITCAM for Web Resources V6.2. These considerations are related to the structure of IBM Tivoli Monitoring servers and the connection for ITCAM for Web Resources agents that connect to Tivoli Enterprise Monitoring Server. See also Deployment Guide Series: IBM Tivoli Monitoring 6.1, SG24-7188. We also discuss the following scenarios: Section 2.4.1, Demonstration or proof of concept on page 20 Section 2.4.2, Small and medium environment on page 21 Section 2.4.3, Large and very large environment on page 22
2.4.1 Demonstration or proof of concept

The demonstration or proof of concept deployment focuses on speed for bringing the system up and showing the functions. It does not consider performance and load of the servers nor system reliability. A typical configuration is shown in Figure 2-1 on page 21.
20
DB2 Data Warehouse Monitoring Server Portal Server Warehouse Proxy Sumarization and Pruning
TEMA
TEMA
TEMA
TEMA
Figure 2-1 Demonstration or proof of concept
The configuration in Figure 2-1 consists of: A single server running DB2 Universal Database for Tivoli Data Warehouse and Tivoli Enterprise Portal Server database, End-user Response Time Dashboard agent, Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Warehouse Proxy. The Summarization and Pruning agent is not configured because the system is not around for a long period of time. Various agents, such Tivoli Enterprise Monitoring Agent (TEMA), running on application server machines to monitor application server performance.
2.4.2 Small and medium environment

A small and medium scale environment accommodates a larger number of agents with consideration on system performance. This environment has more specialization for the servers and allows load balance to remote Tivoli Enterprise Monitoring Server. This environment is applicable for one to five sites with less than 1000 monitored clients. A typical configuration is shown in Figure 2-2 on page 22. Each remote Tivoli Enterprise Monitoring Server is capable of handling up to 1000 agents. A client can run multiple agents.
21
DB2 (for Portal Server) Hub Monitoring Server Portal Server
DB2 Data Warehouse Warehouse Proxy Sumarization and Pruning
Remote TEMS
Remote TEMS
Remote TEMS
TEMA TEMA TEMA
TEMA
TEMA
TEMA
TEMA
TEMA
TEMA
Figure 2-2 Small and medium environment
The small and medium environment shown in Figure 2-2 includes: A specialized hub Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server. A separate machine for handling Tivoli Data Warehouse with Warehouse Proxy, Summarization and Pruning Agent. Remote Tivoli Enterprise Monitoring Server handling agent communication from different sites, instead of directly from the hub Tivoli Enterprise Monitoring Server.
2.4.3 Large and very large environment

For a larger environment, redundancy and performance are critical. This design includes multiple levels of Tivoli Enterprise Monitoring Server structure with failover capability. All major central functions are running on separate servers with their required redundancy. Figure 2-3 on page 23 shows an example of a large system deployment.
22
DB2 database
Portal Server
Warehouse Proxy Sumarization and Pruning
Failover Hub Monitoring Servers
Remote TEMS
Remote TEMS
Remote TEMS
TEMA TEMA TEMA
TEMA
TEMA
TEMA
TEMA
TEMA
TEMA
Figure 2-3 Large system deployment
In Figure 2-3, the configuration includes: Separate servers for: Tivoli Data Warehouse database Hub Tivoli Enterprise Monitoring Server (2 servers) Tivoli Enterprise Portal Server Warehouse proxy and Summarization and Pruning agent
Separate remote Tivoli Enterprise Monitoring Server for each site.
23
24
Chapter 3.
Project planning
This chapter discusses project planning information to help you deploy ITCAM for Web Resources V6.2. The topics are: Required skills on page 26 Solution description and assumptions on page 26 Task breakdown on page 27
25
3.1 Required skills

To implement ITCAM for Web Resources V6.2, you need the following prerequisite skills: IBM Tivoli Monitoring architecture WebSphere or other J2EE application server skill Application environments Database skill Networking and Web transaction Working with Tivoli Enterprise Portal Apart from the above requirements, you need to know the ITCAM for Web Resources V6.2 itself. This includes the following topics: Using workspaces Configuring the data collector Navigating ITCAM for Web Resources workspaces
3.2 Solution description and assumptions

The solution monitors servers and application server performance. First establish a monitoring methodology by using a series of planning session with the customer. In these sessions, address the following items: The applications or IT services to be included in the implementation, which server hosts those applications, the location of these servers, and what connectivity options are available. The Web servers and application servers software level and the user ID for accessing them. The applications running on the application servers. Based on the above requirements from the customer, you can start developing the solution configuration and implementation methods. The configuration involved defines where to put critical components, such as Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server. The implementation method includes deployment of the agents and data collectors. You can perform only a sub-set of the identified final configuration. The complete configuration is up to the customer to implement. You must predetermine the initial subset to implement the final configuration.
26
3.3 Task breakdown

The detailed tasks for ITCAM for Web Resources implementation is divided into the sections: Section 3.3.1, Project kick off on page 27 Section 3.3.2, Environment preparation on page 27 Section 3.3.3, IBM Tivoli Monitoring setup on page 27 Section 3.3.4, Application support files installation on page 28 Section 3.3.5, Agents and data collectors setup on page 28 Section 3.3.6, Customizing the product on page 29 Section 3.3.7, Demonstrating the solution and skill transfer on page 29
3.3.1 Project kick off

The start of the project is a critical task that allows all participant to be identified. This initiation allows roles and responsibilities to be presented and a generic project plan to be laid out. The kick off is also an important milestone to promote the project to the customers user base and generate interest for the project.
3.3.2 Environment preparation

The initial environment preparation has the following objectives: Installing and preparing the new server machines with the appropriate operating system and network connectivity. This applies to machines that run Tivoli Enterprise Monitoring Server, Tivoli Data Warehouse, and other servers. Identifying machines on which Tivoli Enterprise Monitoring Agent is installed. This includes tabulating their IP addresses, host name, owner, access to the machine, and other relevant information Collecting installation media and required software for the installation. Depending on the size of the implementation and the readiness of the environment, this task can take several hours or several days.
3.3.3 IBM Tivoli Monitoring setup

After the environment preparation is done, you can install IBM Tivoli Monitoring V6.1. This includes installing DB2 Universal Database V8.2 for Tivoli Enterprise Portal Server and possibly Tivoli Data Warehouse.
Chapter 3. Project planning
27
For IBM Tivoli Monitoring, you must install the following components: Tivoli Enterprise Monitoring Server Tivoli Enterprise Portal Server Warehouse Proxy Summarization and Pruning Agent (not needed for demonstration or proof of concept installation) For more information, see Deployment Guide Series: IBM Tivoli Monitoring 6.1, SG24-7188.
3.3.4 Application support files installation

Before ITCAM for Web Resources components is installed, you must install the application support files on Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal desktop client, and Tivoli Enterprise Portal Server machines. Depending on the configuration of the IBM Tivoli Monitoring environment, you might need to install these files on one or more machines. During installation, you must restart Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server. You should schedule for minimal interruption of the operation. See section 4.2, Installing application support files on page 35 for more information. You must install the application support files before the agent.
3.3.5 Agents and data collectors setup

Install the monitoring agents for ITCAM for Web Resources on the appropriate machines. This deployment must be done with the least interruption to the application running on these servers. See section 4.3, Installing the Tivoli Enterprise Monitoring Agent on page 44 for more information. Data collector installation and configuration must be performed on the J2EE application server. This requires modification on the application server environment and a restart of the application server. This process is potentially disruptive to the application processing and must be scheduled accordingly. See section 4.4, Installing the data collector on page 53 for more information. Depending on the environment, the following are a few ideas on installing Tivoli Enterprise Monitoring Agent: Installation with an existing software distribution mechanism, such as IBM Tivoli Configuration Manager.
28
Remote deployment of agent using the operating system agent that is already installed. Or, if there is no other option, you can also run the GUI installation wizard on the machine.
3.3.6 Customizing the product

For ITCAM for Web Resources, the workspaces have been provided with adequate function to start monitoring the servers. The customization includes defining an application performance baseline as the base for generating events. Additional situations might also be defined to provide more specific event-based monitoring using ITCAM for Web Resources.
3.3.7 Demonstrating the solution and skill transfer

After completing the customization and with the solution in place, you can demonstrate the result to the customer. This demonstration can signify your completion milestone. You must also perform skill transfer so that the customers personnel can operate and maintain the solution on a day-to-day basis. This is an important task that ensures smooth hand over of the overall project. A sample demonstration of the product usage is described in Chapter 5, Scenarios on page 77.
Chapter 3. Project planning
29
30
Part 2
Part
Deployment
This part describes scenarios related to the actual deployment and usage of ITCAM for Web Resources V6.2.
31
32
Chapter 4.
Installation and configuration

This chapter provides step-by-step instructions for installing ITCAM for Web Resources V6.2. It consists of the following sections: Installation overview on page 34 Installing application support files on page 35 Installing the data collector on page 53
33
4.1 Installation overview

ITCAM for Web Resources is a solution that is based on the IBM Tivoli Monitoring V6.1 platform. It monitors and manages applications running on commonly available application servers and Web servers. The application server platforms include IBM WebSphere, WebLogic, SAP, Oracle, JBoss, Tomcat, J2SE, and WebSphere Application Server Community Edition. The supported Web servers are Microsoft IIS, SUN, and Apache Web Servers. As discussed in section 1.4, Architecture and interconnection on page 5, the product consists of the data collector and the Tivoli Enterprise Monitoring Agent that connect to the Tivoli Enterprise Monitoring Server. The installation process consists of: Section 4.2, Installing application support files on page 35 is a prerequisite for using the agents. The Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server need the information about the agent to be pre-populated. Section 4.3, Installing the Tivoli Enterprise Monitoring Agent on page 44 discusses the installation of Tivoli Enterprise Monitoring Agent for WebSphere. Section 4.4, Installing the data collector on page 53 describes the necessary installation process for the data collector. This data collector is the same code for both IBM Tivoli Composite Application Manager for WebSphere and ITCAM for Web Resources. Note: The installation media contains the Netcool ASM agent. This is an optional component that you can use to integrate with the Micromuse Netcool solution. Our installation process does not cover this component. For more information about IBM Tivoli Monitoring, see Deployment Guide Series: IBM Tivoli Monitoring V6.1, SG24-7188. It is a step-by-step deployment guide for IBM Tivoli Monitoring V6.1 which covers small to large environments and discusses best practices for a deployment plan. Figure 4-1 on page 35 shows our sample deployment environment. We have the application server node on srv177 and the IBM Tivoli Monitoring server in srv178. In this configuration, all the IBM Tivoli Monitoring components are running on the same machine, which is best suited for a demonstration or proof of concept environment.
34
srv177
WebSphere Application Server ITCAM for Web Resource data collector ITCAM for Web Resource WebSphere TEMA
srv178
Tivoli Enterprise Monitoring Server Tivoli Enterprise Portal Server Tivoli Enterprise Portal
Figure 4-1 Sample deployment environment
4.2 Installing application support files

This section describes the installation of the application support files for Tivoli Enterprise Monitoring Agent for WebSphere on a Windows platform. Before you view data collected by monitoring agents, you must install and enable application support for the agents. The application support files provide agent-specific information for workspaces, helps, situations, template, and other data. All monitoring agents require that application support are configured on all instances of the following infrastructure components: Tivoli Enterprise Monitoring Server (both hub and remote monitoring servers) Tivoli Enterprise Portal Server Tivoli Enterprise Portal Desktop Client You must first install application support files on Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal desktop client. You must acquire the appropriate IBM Tivoli Monitoring environment information, including the host names and communication protocols for the appropriate components listed above. In our sample deployment environment, we have a single server running Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal, and Tivoli Enterprise Portal Server. Note: We assume that IBM Tivoli Monitoring server has been installed properly. The monitoring server will be stopped during this process. You can also use the launchpad to install the application support files. The steps are: 1. Stop the Tivoli Enterprise Monitoring Server, or the installation process automatically stops the Tivoli Enterprise Monitoring Server. 2. Run setup.exe from the Windows subdirectory of the installation media.
Chapter 4. Installation and configuration
35
3. Click Next on the Welcome window. 4. ITCAM for Web Resources requires a specific version of IBM GSKit and IBM Java. Verify if the required versions of IBM GSKit and IBM JAVA are installed and click Next, as shown in Figure 4-2.
Figure 4-2 Install prerequisites
5. Click Accept on the software license agreement. 6. In the Select Features window (Figure 4-3 on page 37), uncheck Tivoli Enterprise Monitoring Agents because you are not installing the agent on this server, just the application support files, expand and check Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop Client. Click Next.
36
Figure 4-3 Select features
7. The agent deployment windows opens as shown in Figure 4-4 on page 38. IBM Tivoli Monitoring provides the ability to deploy resource monitoring across your environment from the monitoring server. Assuming you already have the Operating System monitoring agent on the server, you can remotely deploy and configure monitoring agents. Put a check for Monitoring Agent for WebSphere to add the agent to the deployment depot and click Next.
37
Figure 4-4 Agent deployment dialog
38
8. After the application support files installation is complete, a configuration window is displayed with all the components you just selected for configuration. Click Next as shown in Figure 4-5.
Figure 4-5 Configuration options
39
9. The Tivoli Enterprise Portal configuration starts. Select the host name of the machine where Tivoli Enterprise Portal Server resides. Click Next as shown in Figure 4-6.
Figure 4-6 Tivoli Enterprise Portal Server host name
10.The next steps configure application support files for Tivoli Enterprise Monitoring Server: a. Ensure the communication protocol to Tivoli Enterprise Monitoring Server are correct and click OK, as shown in Figure 4-7 on page 41.
40
Figure 4-7 Tivoli Enterprise Monitoring Server communication protocol
b. Set the parameters for the communication protocol. For the IP.PIPE: protocol, provide the host name and port of the Tivoli Enterprise Monitoring Server. Click OK as shown in Figure 4-8.
Figure 4-8 Tivoli Enterprise Monitoring Server IP.PIPE parameters
c. Specify the location of the monitoring server as shown in Figure 4-9 on page 42 and click OK.
41
Figure 4-9 Selecting Tivoli Enterprise Monitoring Server
d. Select the application support file to add. The Tivoli Enterprise Monitoring Server windows opens. This window lists the application support packages that you selected in Step 7. Click OK to begin configuring Tivoli Enterprise Monitoring Server using the SQL files listed on this window, as shown in Figure 4-10.
Figure 4-10 Selecting application support to be added
e. Figure 4-11 shows that the application support addition has been completed with return code of 0. Click Next.
Figure 4-11 Application support addition complete
42
11.The next steps configure the agent defaults connection to the Tivoli Enterprise Monitoring Server: a. Specify the default communication protocol for the agent to communicate with Tivoli Enterprise Monitoring Server and click OK, as shown in Figure 4-12.
Figure 4-12 Communication protocol defaults
b. Define the communications parameters between the agents and Tivoli Enterprise Monitoring Server and click OK, as shown in Figure 4-13.
Figure 4-13 Communication defaults for IP.PIPE
43
12.Figure 4-14 shows that the installation has been completed. Click Finish.
Figure 4-14 Installation finished
4.3 Installing the Tivoli Enterprise Monitoring Agent

You must install the ITCAM for Web Resources Tivoli Enterprise Monitoring Agent to facilitate communication from the data collector to the Tivoli Enterprise Monitoring Server. The Tivoli Enterprise Monitoring Agent installation is not required for the data collector machine, but we highly recommend installing the Tivoli Enterprise Monitoring Agent on the same machine as the data collector to ensure display clarity in Tivoli Enterprise Portal. The installation for Tivoli Enterprise Monitoring Agent is using the same wizard as the application support files in section 4.2, Installing application support files on page 35. The Tivoli Enterprise Monitoring Agent for ITCAM for Web Resources uses the same product code as IBM Tivoli Composite Application Manager for WebSphere or IBM Tivoli Composite Application Manager for J2EE. Therefore, an installation of ITCAM for Web Resources removes the previous IBM Tivoli Composite Application Manager for WebSphere Tivoli Enterprise Monitoring
44
Agent or IBM Tivoli Composite Application Manager for J2EE Tivoli Enterprise Monitoring Agent. 1. Run setup.exe from the WINDOWS sub directory of the installation media. 2. Click Next on the Welcome window as shown in Figure 4-15.
Figure 4-15 Welcome dialog
45
3. Accept the product prerequisite as shown in Figure 4-16 and click Next.
Figure 4-16 Installation requirements
46
4. ITCAM for Web Resources requires a specific version of IBM GSKit and IBM Java. Verify if the required versions of IBM GSKit and IBM JAVA are installed and click Next, as shown in Figure 4-17.
Figure 4-17 Install prerequisites
5. Click Accept on the software license agreement.
47
6. Select the installation path as shown in Figure 4-18. Click Next.
Figure 4-18 Installation path
48
7. In the Select Features window (Figure 4-19), check only the Tivoli Enterprise Monitoring Agent option. Click Next.
Figure 4-19 Select features
49
8. The installation summary dialog is shown in Figure 4-20. Click Next to begin installation.
Figure 4-20 Installation summary dialog
50
9. After the installation is completed, the configuration options window appears as shown in Figure 4-21.
Figure 4-21 Configuration options
51
10.From the configuration option dialog, configure the communication protocol defaults to connect to Tivoli Enterprise Monitoring Server, as shown in Figure 4-22.
Figure 4-22 Communication to Tivoli Enterprise Monitoring Server
52
11.The WebSphere agent configuration dialogs is a tabbed window shown in Figure 4-23. You can accept all the defaults and click OK.
Figure 4-23 Configuration for WebSphere agent
4.4 Installing the data collector

The data collector runs on each monitored application server, and relays monitoring information to IBM Tivoli Monitoring agent. You must install the data collector components from IBM Tivoli Composite Application Manager for WebSphere with a specific level. This includes the data collector version 6.1 using Fix Pack 1 and interim Fix 4. The installation is performed from both the data collector installation image and the launch pad CD, on which the required fixes are distributed. The installation is performed in the following order: 1. Section 4.4.1, Setting up the application server on page 54 lists prerequisite steps for the data collector installation. 2. Section 4.4.2, Installing the base data collector version 6.1 on page 54 includes the installation of the IBM Tivoli Composite Application Manager for J2EE V6.1 or IBM Tivoli Composite Application Manager for WebSphere V6.1 data collector. 3. Section 4.4.3, Applying Fix Pack 1 and interim Fix 4 on page 61 lists the required patches for ITCAM for Web Resources V6.2.
53
4. Section 4.4.4, Configuring data collectors in the application servers on page 62 describes how to configure the data collector after all the required patches are installed.
4.4.1 Setting up the application server

Before you install the data collector, perform the following actions: Set up permission for accessing the application server configuration. Add 128 MB of heap size for the data collector. If your application server does not have the heap size defined, the default heap size is 256 MB; therefore, set it to around 374 MB. If your Windows machine runs a Terminal Server, you must issue the command change user /install to enable installation mode.
4.4.2 Installing the base data collector version 6.1

Perform the following procedure to install the data collector: 1. You can install the data collector by using the launch pad for easy access or by directly invoking the installation wizard. Launch the launchpad.cmd file, as shown in Figure 4-24 on page 55.
54
Figure 4-24 LaunchPad window
2. From the Install Products link, select the Install Data Collector for ITCAM for WebSphere V6.1. When you click the Quick Launch column, this invokes the setup_DC_w32.exe from the path specified in the list. Make sure you have the correct directory. This launches the GUI installation program for the data collector as shown in Figure 4-25 on page 56. Click Next on the welcome dialog.
55
Figure 4-25 Welcome window
56
3. In the software license agreement dialog (Figure 4-26), accept the license agreement and click Next.
Figure 4-26 Software license agreement
57
4. Specify the installation directory for the data collector, as shown in Figure 4-27. We use the path C:\IBM\itcam\WebSphere\DC. Click Next. This path is created if it does not exist.
Figure 4-27 Installation directory
58
5. The next dialog in Figure 4-28 allows you to save a response file. This is an excellent way of recording an installation script for a silent install. We save the response file in C:\ITCAMWR file. Click Next. Note: If you install the data collector to the current machine, a response file is only generated if the GUI installation completes successfully.
Figure 4-28 Generate response file window
59
6. A window displays the summary information about the data collector installation, as shown in Figure 4-29. Click Install to begin the installation.
Figure 4-29 Summary information window
60
7. In the dialog for launching the Configuration Tools, select the option to defer the launching of the configuration tool as shown in Figure 4-30.
Figure 4-30 Launch data collector configuration window
8. Click Next to continue. A successful completion of the installation is displayed. Click Finish. See section 4.4.4, Configuring data collectors in the application servers on page 62 for the data collector configuration.
4.4.3 Applying Fix Pack 1 and interim Fix 4

To apply Fix Pack 1 and interim Fix 4, perform the following steps: 1. Install the data collector fix pack and interim pack using the LaunchPad. The required patches are supplied in the same CD image as the launch pad. In the install product page, ensure the correct Image Location is supplied for the patches. The default is 6.1.0-TIV-ITCAMfWAS_MP-FP0001 and 6.1.0.1-TIV-ITCAMfWAS_MP-IF0004. The directories contain the silentUpdate.bat file. If you need to change the directory, click the link and browse to the correct directory as shown in Figure 4-31 on page 62.
61
Figure 4-31 Product Installation window
2. Click the icon under the column labeled Quick Launch. This launches the installation program for the fix pack for the data collector. Now launch the 6.1.0-TIV-ITCAMfWAS_MP-FP0001 installation. 3. Run the installation for 6.1.0.1-TIV-ITCAMfWAS_MP-IF0004. 4. If Terminal Services are enabled on a Windows 2000 or Windows 2003 server, run the following command: change user /execute
4.4.4 Configuring data collectors in the application servers

Use the Configuration Tool to configure the application server for monitoring by the data collector. It can be launched either from the installer program during the end of the installation process or by running the tool from the installation
62
directory. Run the data collectors Configuration Tool for each application server instance you want to configure: 1. Browse the installation directory for the data collector and change to the config_dc sub directory. 2. Run config_dc.bat. Figure 4-32 shows the Welcome window for the Configuration Tool. Click Next.
Figure 4-32 Welcome window
63
3. Select Configure servers for data collection, as shown in Figure 4-33. Click Next.
Figure 4-33 Configure window
64
4. For ITCAM for Web Resources, only configure the data collector for displaying data on the Tivoli Enterprise Portal interface. The application management interface is provided if you use either IBM Tivoli Composite Application Manager for WebSphere or IBM Tivoli Composite Application Manager for J2EE. See Figure 4-34. Click Next.
Figure 4-34 Choose data collector server type
65
5. In Figure 4-35, specify the fully qualified host name and port for the Tivoli Enterprise Monitoring Agent. This dialog checks whether the Tivoli Enterprise Monitoring Agent is available or not. You can still continue installing the data collector, even if the Tivoli Enterprise Monitoring Agent is not available at this time. We use the default values. Click Next. Note: If you need to change these values, the configuration is recorded in the $DC_home/runtimes/<ver>.<node>.<server>/*.kwjdc.properties file.
Figure 4-35 Tivoli Enterprise Monitoring Agent window
66
6. A window indicating a selected IP address for the data collector displays as shown in Figure 4-36. This window appears when you have multiple network cards and need to adjust the ports for an enabled firewall. This dialog is not used for ITCAM for Web Resources. Use the default information here. The communication parameter is performed by the Tivoli Enterprise Monitoring Agent to the Tivoli Enterprise Monitoring Server. Click Next.
Figure 4-36 Data collector host window
67
7. Figure 4-37 shows the application server selection. In our case, we are installing this to a standard WebSphere Application Server. Click Next.
Figure 4-37 Application server type window
68
8. The installation wizard searches for installations of that type of application server and then displays a list as shown in Figure 4-38. Select the application server that the data collector will monitor and click Next. Note: For WebSphere Application Server V6: If there are several existing profiles for the installed application server, make sure the selected profile is the one that contains the application server you are instrumenting.
Figure 4-38 WebSphere option dialog
69
9. Figure 4-39 shows information about the selected application server. Confirm the information and click Next.
Figure 4-39 WebSphere information review window
70
10.The installation wizard communicates to the administration application of the application server. For the Network Deployment installation, this connects to the deployment manager instance. In Figure 4-40, specify the correct host name and port that are used for the administration application. Click Next.
Figure 4-40 WebSphere administration application connection window
71
11.The installation wizard connects to the administration application and displays a tree of the application server as shown in Figure 4-41. Select the servers and click Next.
Figure 4-41 Choose server window
72
12.Figure 4-42 allows you to save a response file for performing a silent install for other data collectors. This is useful for deploying a large number of data collector with minimal interaction with the machines. Click Next.
Figure 4-42 Generate response file window
13.The Configuration Tool applies the configuration to the data collector, then a panel indicating the results of the configuration displays, as shown in Figure 4-43 on page 74.
73
Figure 4-43 Successful application server configuration window
14.Click Finish. 15.Restart all affected application servers.
4.5 Verifying the installation

You can perform installation verification from several different aspects: Verify communication between the configured data collector to the Tivoli Enterprise Monitoring Agent on port 63335. Using the netstat -all command, you can see all active communication. See Figure 4-44 on page 75. If you have Microsoft Services for UNIX (SFU) or Cygwin, then you can also use the grep command.
74
C:\> netstat -all | grep 63335

Figure 4-44 Communication with Tivoli Enterprise Monitoring Agent
Verify that the appropriate agent and workspaces are shown in Tivoli Enterprise Portal. The sample workspace that we have for srv177 is shown in Figure 4-45.
Figure 4-45 Tivoli Enterprise Portal workspace structure
75
76
Chapter 5.
Scenarios
This chapter describes how to use ITCAM for Web Resources. It discusses the following topics: Usage scenario overview on page 78 Using the workspaces on page 78 Defining application health and baseline on page 84 Working with situations on page 90
77
5.1 Usage scenario overview

Using ITCAM for Web Resources is based on monitoring our Trader application environment. The application runs on a set of two WebSphere Application Servers. See Appendix A, The Trader application on page 107 for more detail on this application. The monitoring environment is shown in Figure 5-1.
srv177
WebSphere Application Server ITCAM for Web Resource data collector ITCAM for Web Resource WebSphere TEMA
srv178
Tivoli Enterprise Monitoring Server Tivoli Enterprise Portal Server Tivoli Enterprise Portal
Figure 5-1 Application environment
We use the following two servers: The monitored application server in srv177 The IBM Tivoli Monitoring server in srv178 This chapter is divided into the following sections: Section 5.2, Using the workspaces on page 78 describes the available workspaces that come with ITCAM for Web Resources. Section 5.3, Defining application health and baseline on page 84 discusses defining a generic application health and defining a baseline for this health indicator. Section 5.4, Working with situations on page 90 provides a scenario for event-based monitoring.
5.2 Using the workspaces

The workspace for ITCAM for Web Resources is created under the Tivoli Enterprise Monitoring Agent machine that the data collector is connected to, not the machine on which the data collector resides. It is a good practice to always have the Tivoli Enterprise Monitoring Agent running on the same machine as the data collector.
78
The workspace is structured by the agent host and then each application server nodes. Individual workspaces that collect certain performance information are available under the application server node. See Figure 5-2.
Figure 5-2 Workspace structure
Lets evaluate these workspaces: The primary agent workspace contains all situation events from the agent and the health summary of the application servers that it monitors. Figure 5-3 on page 80 shows an example of this workspace.
Chapter 5. Scenarios
79
Figure 5-3 Agent summary workspace
The application server summary workspace provides a summary of the important metrics of the application server. This workspace is shown in Figure 5-4 on page 81.
80
Figure 5-4 Application server summary workspace
Under the application servers, there is a set of workspaces: Application health Request analysis Garbage collection analysis Log analysis Pool analysis Data source JMS summary Web application EJB containers DB connection pool J2C connection pool Thread pool Cache analysis
81
Workload management Scheduler Web services Platform messaging
We do not cover all of these workspaces. The following are a few examples of the workspaces: Request analysis workspace shown in Figure 5-5.
Figure 5-5 Request analysis workspace
82
The log analysis workspace summarizes WebSphere errors and exceptions and ITCAM for Web Resources data collector messages in the WebSphere log. Figure 5-6 shows the workspace.
Figure 5-6 Log analysis workspace
83
Web application workspace that lists the available Web application and its performance is shown in Figure 5-7.
Figure 5-7 Web application workspace
5.3 Defining application health and baseline

ITCAM for Web Resources has a unique feature that provides application health workspace. The application is represented by the installed enterprise application (EAR) file. Initially, all application health in the Application Health workspace is unknown, as shown in Figure 5-8 on page 85.
84
Figure 5-8 Tivoli Enterprise Portal window
The health is calculated against an internally stored baseline threshold. This baseline process uses mathematical and statistical method to automatically calculate the threshold based on response time information that is collected over a period of time. The baseline data collection is usually a long running activity that can last for hours or days. Note: The recommended period to create a baseline is when the application is running under a typical load. The performance of the application under this load is considered good. Deviation from this performance indicates a degrading health of the application. The following procedure creates an application baseline: 1. Open Tivoli Enterprise Portal and select the application server you want to work on. Open the application health workspace. 2. From the Application Health Summary table, select and right-click one of the application names as shown Figure 5-9.
Figure 5-9 Application Health Summary window
3. Select Selected Application - Configuration and Application Request Configuration window opens as shown in Figure 5-10 on page 86.
85
Figure 5-10 Application Request Configuration window
4. In the application request configuration workspace, select the request type you want to define and right-click. Select Take Action Select as shown in Figure 5-11 on page 87.
86
Figure 5-11 Invoking an action
5. In the take action dialog in Figure 5-12, select the Start_Baselining action.
Figure 5-12 Take Action selection
87
6. Enter the arguments as shown in Figure 5-13. Some of the values have been prefilled from the application that you selected. Click OK.
Figure 5-13 Edit argument values
7. Back in the Take Action window, click OK to invoke the action. The arguments and destination system have been preselected based on your invocation context.
Figure 5-14 Take Action window
8. When the command has been invoked successfully, a completion message appears as shown in Figure 5-15 on page 89. Click OK.
88
Figure 5-15 Action status command
9. Perform some transactions on the application and the you can invoke the Stop_Baselining action using the same mechanism. 10.You can start getting the result on the application health workspace.
Application configuration
The application configuration: Displays information about all requests monitored for a given application. Displays baselining status. Provides a table and bar chart views to report the essential configuration properties associated with monitored request: Request ID (correlates with other requests IDs reported throughout the product). Parameters for auto-thresholding. Actual thresholds values (assigned automatically or customized by the user). Uses the Take Action function, user can control monitoring, baseline, and thresholds configuration. Provides a link to the request configuration workspace where you can visualize baseline data or threshold settings with more detail.
Request baselining
The product collects and keeps the baseline data for each application request: Baseline data is collected in prolonged intervals (for days, weeks or months). Baseline is a statistical distribution of application requests response times. Baseline is used to facilitate the auto-thresholding feature of the product: Assigns fair and bad response time thresholds for each application request.
89
Additionally assigns each tier (client, application, or backend) the share (in percent) from the whole application request delay time. At runtime the fair or bad response time thresholds are used to determine the overall health status for the request. The share percent is used to determine which tier contributes more to a delayed request and brings up the users focus for that request.
The request baseline workspace provides table and bar charts to bring the baseline distribution stats and threshold settings for a request in the same views.
5.4 Working with situations

To define a situation using the situation editor and to configure the baseline thresholds, use this sample from the IBM Tivoli Open Process Automation Library at: http://catalog.lotus.com/tcam?NavCode=1TW10CP0S IBM Tivoli Composite Application Manager for Web Resources - WebSphere Agent provides some predefined situations that you can use: To immediately begin monitoring your WebSphere application servers. To monitor and manage widely dispersed WebSphere Application Server resources through localized automation. As models for creating your own situations. These predefined situations have an alert status of critical. When these situations trigger an alert, you can investigate the event by opening its workspace. For example, you can use these situations to monitor a WebSphere Application Server for errors occurring within it or your sites Web applications. Situations are tests expressed in IF-TRUE format of system conditions that you want to monitor. The tested value is an ITCAM for Web Resources - WebSphere Agent attribute expressed in the form of attribute-group.attribute-name. Thus, if the specified condition occurs or exists, the situation is true and an alert is issued. If you define situations that use a counter or a range of numbers, always provide a threshold or use values in a positive range of numbers. For example, use a greater-than-or-equal-to-zero expression as shown in some of the predefined situations described below. This practice prevents a situation from falsely tripping. If the ITCAM for Web Resources - WebSphere Agent Tivoli Enterprise Management Agent encounters an undefined attribute value, it interprets this as
90
a negative number and erroneously fire a situation that specified a negative number as shown in Figure 5-16 and Figure 5-16.
Figure 5-16 Situation Editor for WebSphere Application Server
New situations added

ITCAM for Web Resources V6.2 has four new situations: WASAppDiscovered: This situation fires when a new application is discovered. This happens when the application server connects to TEMA the first time. In this case, all deployed applications on that server are marked as discovered, or when a new application has been deployed to the monitored application server. WASAppHealthGood: This situation fires when TEMA detects an application running at a good health level. It has an automated response to drop the monitoring level to L1 and the sampling rate to 2%.
91
WASAppHealthFair: This situation fires when TEMA detects an application running at a fair health level. It has an automated response to drop the monitoring level to L2 and the sampling rate to 2%. WASAppHealthBad: This situation fires when TEMA detects an application running at a fair health level. It has an automated response to drop the monitoring level to L2 and the sampling rate to 10%. Table 5-1 describes all situations from the situation editor.
Table 5-1 Predefines situations-description and formulas Situation WASWebApplicationError Description Monitors the status of the WebSphere servers error log and issues a critical condition when an error occurs. Monitors the error count for servlets and JSPs invoked by a WebSphere Application Server application and issues a critical condition when the count becomes nonzero. Monitors the thread timeout count and issues a critical condition when the timeout count is greater than zero. Monitors the WebSphere Application Servers rollback count and issues a critical alert when the count becomes nonzero. Formulas If Web_Applications.Error_Count is greater than 0, then the situation WASWebApplicationError is true. If Servlets_JSPs.Error_Count is greater than 0, then the situation WASServletsJSPsError is true.
WASServletsJSPsError
WASDBConnectionPoolTh readTimeout
If DB_Connection_Pools.Threads_Timed_O ut is greater than 0, then the situation WASDBConPoolThreadTimeOut is true. If Container_Transactions.Global_Transacti ons_Rolled_Back is greater than 0, or Container_Transactions.Local_Transactio ns_Rolled_Back is greater than 0, or Container_Transactions.Transactions_Roll ed_Back is greater than 0, then the situation WASContainerTransactionRollBack is true.
WASContainerTransaction Rollback
92
Situation WASError
Description Monitors the error severity for a single WebSphere Application Server and issues a critical condition when that severity is greater than 21. Monitors the connection between the ITCAM for WebSphere Data Collector running in an application server and the ITCAM for Web Resources - WebSphere Agent TEMA to ensure the monitoring agent is connected and issues a critical condition when it is not. Monitors the heap allocation status and issues a critical condition when the heap space is exhausted. Monitors the average request response time and issues a critical condition when that time exceeds two seconds. Monitors the percentage of the CPU being consumed and issues a critical condition when that time exceeds 80%. Monitors the percentage of time being spent by the garage collector and issues a critical condition when that time exceeds 80%. Monitors the average usage time of all threads, and issues a critical condition when that time exceeds 80%.
Formulas If Log_Analysis.Severity is greater than 21, then the situation WASError is true.
WASNotConnected
If Application_Server_Status.Status equals 0, then the situation WASNotConnected is true.
WASOutofHeapSpace
If Allocation_Failure.Heap_Status equals 1, then the situation WASOutofHeapSpace is true. If Request_Times_and_Rates.Average_Re quest_Response_Time is greater than 2000, then the situation WASHighResponseTime is true. If Application_Server.CPU_Used_Percent is greater than 80, then the situation WASHighCPUPercentUsed is true. If Garbage_Collection_Analysis.Real_Time _Percent is greater than 80, then the situation WASHighGCTimePercent is true. If Thread_Pools.Percent_of_Time_Pool_at_ Max is greater than 80, then the situation WASThreadPoolPercentMaxed is true.
WASHighResponseTime
WASHighCPUPercentUse d
WASHighGCTimePercent
WASThreadPoolPercentM axed
93
Situation WASAppDiscovered
Description Monitors WebSphere applications deployed in the application server and issues an informational alert when a new application is discovered. The TEMA checks for new applications each time when it connects to the data collector or when an application is deployed when the data collector is already active. Monitors the overall application health and issues an informational alert when application health is good. Monitors the overall application health and issues a warning alert when application health is fair. Monitors the overall application health and issues a critical alert when the application health is bad. Monitors the portal page response time and issues a critical alert when the average request response time is higher than 2 seconds. Monitors the portlet response time and issues a critical alert when the average request response time is higher than 2 seconds.
Formulas If Application_Monitoring_Configuration.Mo nitoring_Status equals 0, then the situation WASAppDiscovered is true.
WASAppHealthGood
If Application_Health_Status.Application_H ealth equals 1, then the situation WASAppHealthGood is true. If Application_Health_Status.Application_H ealth equals 2, then the situation WASAppHealthFair is true. If Application_Health_Status.Web_Tier_Hea lth equals 3, then the situation WASAppHealthBad is true. If Portal_Page_Summary.Average_Respons e_Time is greater than 2000, then the situation WASPortalPageResponseTime is true. If Portlet_Summary.Average_Response_Ti me is greater than 2000, then the situation WASPortletResponseTime is true.
WASAppHealthFair
WASAppHealthBad
WASPortalPageResponse Time
WASPortletResponseTime
Defining situations
Situations are defined using the situation editor that is invoked using the button from Tivoli Enterprise Portal workspace. To open Tivoli Enterprise Portal Server, type http://hostname:1920/ in your browser as shown in Figure 5-17 on page 95.
94
Tivoli Enterprise Portal is the common user interface for real-time information and historical data collected by Tivoli Enterprise Monitoring Server. Products from the various Tivoli families integrate with it to provide a flexible and customizable repository and linked information.
Figure 5-17 Tivoli Enterprise Portal Physical view example
95
From the situation editor main window, we create a new situation by right-clicking the appropriate category and selecting Create New as shown in Figure 5-18.
Figure 5-18 Situation Editor window
96
If you want to create another situation from the list of situation editor, right-click the appropriate situation you want and select Create Another as shown in Figure 5-19.
Figure 5-19 Create another situation from the situation list
97
When the Create Situation window opens, as shown in Figure 5-20, enter the name. and click Ok.
Figure 5-20 New situation window
You can show the formula by clicking as shown in Figure 5-21.
and the Show Formula window opens
Figure 5-21 Show Formula window
98
The next window lets you select the attribute group and attributes that you want to use for the situation as shown in Figure 5-22. Select the attributes that you want to evaluate.
Figure 5-22 Selecting attribute group and attributes
99
When the attributes have been selected, click OK to see the situation formula definition. You must specify your condition here and select the distribution list on the next tab. The distribution list represents the Tivoli Enterprise Monitoring Agent that the situation will run on, as shown in Figure 5-23.
Figure 5-23 Formula window
100
Chapter 6.
Troubleshooting hints and tips

This chapter discusses collecting log files and defining traces on the product. The topics are: IBM Tivoli Monitoring logging on page 102 ITCAM for Web Resources logs on page 102
101
6.1 IBM Tivoli Monitoring logging

ITCAM for Web Resources V6.2 is based on IBM Tivoli Monitoring V6.1 architecture. The troubleshooting process is in the framework of IBM Tivoli Monitoring. Problems on the client side involve the Tivoli Enterprise Portal desktop client or Tivoli Enterprise Portal Web client. The desktop client logs are: <ITM_home>\CNP\logs\kcjras1.log <ITM_home>\CNP\logs\kcj.log The Tivoli Enterprise Portal Web client stores information in plugin131_0x.trace, which is stored in the user home directory. It is typically under C:\Document and Settings\<username>. The Tivoli Enterprise Portal Server consists of two processes, each of these generate different log files. The files are: <ITM_home>\CNP\logs\kfwras1.log <ITM_home>\CNP\logs\cmwras1.log If you have installation problems, check the following log files: Common installation logs: <ITM_home>/InstallITM/plugin/executionEvents/logs/YYYYMMDD-HHMMSS /trace_install_plugin.trc Platform-specific trace information: <ITM_home>/logs/install_plugin_trace.log Other agent logs: <ITM_home>/tmaitm6/logs/*.log
6.2 ITCAM for Web Resources logs

The log files for ITCAM for Web Resources that you must collect in case of a problem are located in different areas, the data collector, Tivoli Enterprise Monitoring Agent logs and WebSphere or other J2EE server logs. The following lists the directory for these log files: Tivoli Enterprise Monitoring Agent log files: <ITM_home>\logs\*yn*.log <ITM_home>\logs\kyn-tema-*.log <ITM_home>\logs\*yj*.log <ITM_home>\logs\kyj-tema-*.log
102
<ITM_home>\TMAITM6\logs\*.log Data collector log files, located in the Tivoli common directory (C:\Program Files\ibm\tivoli\common or /var/ibm/tivoli/common): $common_dir\CYN\logs\trace-dc-native.log $common_dir\CYN\logs\msg-dc-native.log $common_dir\CYN\<platfrom.node.server>\trace-dc-native.log $common_dir\CYN\<platform.node.server>\msg-dc-native.log
WebSphere Application Server SystemOut.log and SystemErr.log files in $WAS_HOME/profiles/<profile>/logs/<server>. This section discusses various log and trace settings for ITCAM for Web Resources: You can set Tivoli Enterprise Monitoring Agent Java trace levels the file kynjlog.properties or kyjjlog.properties. Set the following parameters: TEMA.trc.itcam.level=DEBUG_MIN TEMA.trc.itcam.websphere.level=DEBUG_MID You can find the data collector trace under the runtime directory of the data collector installation path in the cynlogging.properties file. The following are for setting basic traces for Tivoli Enterprise Monitoring Agent interface: CYN.trc.temadc.level=DEBUG_MID CYN.trc.jmxconnector.level=DEBUG_MIN Table 6-1 lists possible debug and trace levels in Tivoli Enterprise Monitoring Agent.
Table 6-1 Trace Levels of TEMA Level Minimum (DEBUG_MIN) Description Displays interactions with external interfaces, such as processes, DC, file, take action commands, ITM. In addition, state changes are recorded. Also included are the startup versions and configurations being used by the TEMA. Displays method entry or exit. This level of debugging is extensive and should not be run for an extended period of time. Displays logic flow and important loops in the code. This level of debugging might be excessive and should not be run for an extended period of time.
Medium (DEBUG_MID)
Maximum (DEBUG_MAX)
Chapter 6. Troubleshooting hints and tips
103
104
Part 3
Part
Appendixes
105
106
Appendix A.
The Trader application

This appendix explains the Trader application. The discussion is divided into the following sections: Application components on page 108 Software requirements on page 113 Installation procedure on page 113
107
Application components
The Trader application is a multi-components composite application that runs on heterogeneous platforms and in an execution environment. It is a simple stock trading application that allows the user to list companies, get a quote, and trade stocks of the listed companies. Figure A-1 shows the Trader application conceptual interface.
DB2
Trader DB2
Trader Server applications
Trader Web Client
Figure A-1 The Trader application
You can view the Trader application as having a three-layer (three tiers) structure: The Trader application for this book has a Web interface. It connects to the server application that provides the business logic. The connection to the server applications are based on Web services calls. The server application uses DB2 for its data storage. The application is a J2EE-based application that serves as Web services providers. The back end data storage for this book is a DB2 database. The DB2 database can reside on the same or different server.
108
We discuss the components in the following sections: Front-end J2EE Web application on page 109 Back end implementation on page 112 Back end J2EE server on page 112
Front-end J2EE Web application

The front-end Web application is developed using the Web services client wizard and the Trader*Services projects. The application consists of: Initial login page in login.html (Figure A-2).
Figure A-2 Login page
Note: The DB2, IMS, and CICS radio check boxes shown in Figure A-2 are not normally available to users. They are included in our sample application to highlight possible back-end systems. Similarly, a typical application does not select a target host, but this is shown here as part of our lab environment.
Appendix A. The Trader application
109
ListCompanyServlet (Figure A-3): Invokes the back end ListCompany Web services.
Figure A-3 List Company page
110
GetQuotesServlet (Figure A-4): Invokes the back-end GetQuote Web services.
Figure A-4 Quotes window
BuySellServlet: Invokes either the Buy or Sell Web services. LogoutServlet: Clears up the session bean. We provides three types of enterprise application archive (ear) files for the client interface: TraderClientEAR: This ear file runs the TraderClientWeb application that provides the basic Trader application functionality. TraderClientMemEAR: This ear file runs the TraderClientMem application that has a memory leak in the logic for testing a memory leak situation. TraderClientLckEAR: This ear file runs the TraderClientLck application that has a lock problem injected for testing dead lock situation.
111
Back end implementation

The back end systems consists of two entities: the company and the customer. The company has quotes definitions, and the customer database has the customers name and its stock ownership. Figure A-5 shows the conceptual data structure.
COMPANY
Company Name Stock price Price history 7 days Commission
CUSTOMER
Customer Name Company name Stock owned
List company
GetQuote
Buy/Sell Stock
Figure A-5 Entity diagram
The back end system is implemented in DB2. The DB2 implementation is represented in two tables: the CUSTOMER table and the COMPANY table.
Back end J2EE server

The back end J2EE servers runs on a WebSphere server for DB2 access. The WebSphere-based Web services server has the TraderDBServices.ear modules deployed into it. This program accesses DB2 data. It consists of the following modules: TraderDBWeb: This is the direct front end for the Trader DB. This is useful for validating that the Trader DB application is running. TraderDBServices: This is the Web module that provides Web services provider implementation. Trader_DB: This contains the database access module.
112
Software requirements
This section discusses the software required for running the Trader application. We use the following software for running the Trader components. Other versions of the software are acceptable. Figure A-6 shows the detailed configuration of the Trader application.
DB2 UDB V8.2 FP15 TRADER
WebSphere Application Server ND V6.1 TraderDBSvc.ear
WebSphere Application Server ND V6.1 TraderClient.ear TraderClientMem.ear TraderClientLck.ear
Figure A-6 Trader application detail
The detailed software levels of each components are: TraderClient.ear, TraderClientMem.ear, TraderClientLck.ear TraderDBSvc.ear DB2 databases
Installation procedure
This section discusses the guideline for installing the Trader application in our environment. Perform the installation based on additional material. See Appendix C, Additional material on page 121 on how to get access to the additional material. The installation is discussed in the following sections: DB2 database creation on page 114 WebSphere server installation on page 114
113
WebSphere client installation on page 115
Initial setup for the demonstration server

The additional material is supplied as SG247485.zip file. Extract this file to a temporary directory. In this book, we assume that the file is extracted to the C:\Temp directory. You must install DB2 Universal Database and WebSphere Application Server. We do not discuss the installation of DB2 and WebSphere in this book. Set up WebSphere two application servers. We assume that you are building a network deployment environment. Create two application servers called ClientSvc and ServerSvc.
DB2 database creation

The DB2 databases are created from C:\Temp\trader.zip file. Perform the following steps: 1. Open a DB2 command window. 2. Extract the trader.zip file to C:\Temp\Trader. 3. Open a DB2 command window by executing the command db2cmd. 4. Navigate to C:\Temp\Trader. 5. Create the TRADER database using the following command: db2 create database TRADER 6. Populate the trader database using the following command: db2move TRADER import 7. Verify that you can connect to the database using the following command: db2 connect to TRADER Run the following SQL command: db2 select * from TRADER.COMPANY You should get 4 rows of data.
WebSphere server installation

The server part is installed on the ServerSvc application server. The installation is performed using the WebSphere administration console: 1. Extract the ear files from C:\Temp\WASear.zip file into the C:\Temp\applear directory.
114
2. Modify the WebSphere variables for DB2_UNIVERSAL_JDBC_NATIVEPATH and DB2_UNIVERSAL_JDBC_DRIVERPATH to point to the DB2 installation directories. 3. Create the JDBC data source for the Trader database. The JNDI name is jdbc/Trader. 4. Create an JAAS authentication user to access the database. Make sure you map the JDBC data source to use the authentication method. 5. Create a virtual host that matches the default port for the ServerSvc application server. 6. Install C:\Temp\applear\TraderDBSvc.ear to the ServerSvc. Make sure you map the Web module to the appropriate virtual host that you defined. 7. Save the configuration and restart the application server.
WebSphere client installation

The server part is installed on the ClientSvc application server. The installation is performed using the WebSphere administration console: 1. Extract the ear files from C:\Temp\WASear.zip file into the C:\Temp\applear directory. 2. Create a virtual host that matches the default port for the ClientSvc application server. 3. Install C:\Temp\applear\TraderClient.ear to the ClientSvc. Make sure you map the Web module to the appropriate virtual host that you defined. 4. Install C:\Temp\applear\TraderClientMem.ear to the ClientSvc. Make sure you map the Web module to the appropriate virtual host that you defined. 5. Install C:\Temp\applear\TraderClientLck.ear to the ClientSvc. Make sure you map the Web module to the appropriate virtual host that you defined. 6. Save the configuration and restart the application server.
115
116
Appendix B.
Sample statement of work

This appendix provides a sample statement of work for the ITCAM for Web Resources implementation service. You can use this sample as a template to customize a statement of work based on client requirements.
117
ITCAM for Web Resources implementation service

The ITCAM for Web Resources implementation service statement of work consists of the sections listed here.
Executive summary
The ITCAM for Web Resources implementation service monitors the Web resources performance using the Tivoli Enterprise Portal. The display allows a proactive anticipation of an impending performance problem. The monitoring collects the individual application performance. The implementation of ITCAM for Web Resources starts at <a designated date> for two weeks. At the end of this period, <your name or companys name> will present the implementation highlight, including: Current application server performance summary. Application highlight, such as load profile and transaction rate. Performance highlights, such as potential bottleneck, excessive errors, and deadlock. Environment tuning recommendations.
Solution description
In the ITCAM for Web Resources implementation service, you implement IBM Tivoli Monitoring environment to host the ITCAM for Web Resources V6.2 environment. ITCAM for Web Resources data collectors will be installed on <the clients name> production servers for assessment. The data collector mainly runs in level 1 monitoring, which has limited impact on your servers. Lab testing shows a typical increase of 2%-3% of CPU usage for the J2EE application server. The solution assumes that the IBM Tivoli Monitoring server connection to the data collectors do not go through a firewall. After implementation, performance information is collected into Tivoli Data Warehouse for analysis and presentation. <Your name or companys name> will analyze the collected performance information and possibly perform monitoring with additional detail as needed. The analysis is performed dynamically and does not need a restart of the application servers.
118
Assumptions
Assumptions for this statement of work are: Number of data collectors to be configured Transaction rate of each application server Transaction mix of each application server Note: Insert any additional assumptions about specific performance or transaction problems for the client.
Business partner responsibilities

<Your name or companys name> will have the following responsibilities: Install and configure IBM Tivoli Monitoring V6.1 servers. Install and configure ITCAM for Web Resources V6.2 agents on the appropriate application servers as indicated in the solution configuration. Provide an operation document to use and maintain the ITCAM for Web Resources solution. Present the result of the solution implementation.
Client responsibilities
This section describes the clients responsibilities for IBM or Business Partners: Designate a representative who will be the focal point for all communication with IBM or Business Partner. The representative will have the authority to act on the clients behalf. Designate operations personnel to work with IBM or Business Partner as appropriate. Provide all required Web site content in digital form, as specified by IBM or Business Partner. Provide all product data in a format as requested. Provide all data and information required for implementation. Provide suitable workspace with telephone access for the services specialists while working on the client premises. Provide user IDs, passwords, and IP addresses as required, enabling IBM or Business Partner to perform the service. Provide information to allow estimates on current and future system workload and performance expectations.
Appendix B. Sample statement of work
119
Staffing estimate
The project will be performed with one ITCAM for Web Resources specialist, who will be on site as required by the project schedule. The project is estimated to be performed within two weeks.
Project schedule and milestones

Because this is a short project, we do not need a milestone. Figure B-1 shows a sample project schedule.
Jun 18 2006 Jun 25 2006 21 22 23 24 25 26 27 28 29 30 1 Jul 2 2006 2 3 4 5
ID 1 2 3
Task Name Plan the solution Implement the solution Close the engagement
Start 6/19/2006 6/22/2006 7/4/2006
Finish 6/21/2006 7/3/2006 7/5/2006
Duration
19 20
3d 8d 2d
Figure B-1 Project schedule
Testing methodology
The solution is demonstrated using workspaces and events generated by ITCAM for Web Resources within the Tivoli Enterprise Portal. The monitoring shows critical events for the list of applications, such as: Response time Transaction rate Deadlock problem Memory usage
Deliverables
The project deliverables are: ITCAM for Web Resources workspaces and events Performance assessment and recommendation presentation by <your name or companys name>
Completion criteria
Completion criteria for this project are: Acceptance of performance findings and recommendations All deliverables have been received by the client All testing performed successfully
120
Appendix C.
Additional material
The Web material associated with this book is available in softcopy on the Internet from the IBM Redbooks publications Web server at: ftp://www.redbooks.ibm.com/redbooks/SG247485 Alternatively, you can go to the IBM Redbooks publications Web site at: ibm.com/redbooks Select Additional materials and open the directory that corresponds with the IBM Redbooks publications form number, SG247485.
Using the Web material

The additional Web material that accompanies this book includes the following files: File name SG247485.zip Description Zipped code samples
This file contains the following files: File name Trader.zip WASear.zip Description Zipped database source WebSphere ear files
121
System requirements for downloading the Web material

The Web material is to be run in an Intel server that is capable of running WebSphere Application Server and DB2 Universal Database. The configuration requires the following system requirements: Hard disk space: Memory: 8GB 1.5 GB
How to use the Web material

Create a subdirectory (folder) on your workstation and unzip the contents of the Web material zip file into this folder. See also Appendix A, The Trader application on page 107 for more installation instructions.
122
Abbreviations and acronyms

AIX API BCI CPU EAR EJB GB GUI IBM IIS IP IT ITCAM ITSO JAAS JDBC JDK JMS JMX JNDI JVMTI JVM MVS OS Advanced Interactive eXecutive Application Programming Interface Byte Code Instrumentation Central Processing Unit Enterprise Application Archive Enterprise Java Beans Giga Bytes Graphical User Interface International Business Machines Corporation Internet Information Server Internet Protocol Information Technology IBM Tivoli Composite Application Manager International Technical Support Organization Java Authorization and Authentication Service Java Database Connectivity Java Development Kit Java Messaging Service Java Management eXtensions Java Naming and Directory Interface Java Virtual Machine Tools Interface Java Virtual Machine Multiple Virtual Storage Operating systems SFU SLES SOA SQL TCP/IP TEMA PDF PMI RHEL RISC Portable Document Format Performance Management Infrastructure Red Hat Enterprise Linux Reduced Instruction Set Computer Services for UNIX Suse Linux Enterprise Server Service-oriented architecture Structured Query Language Transmission Control Protocol, Internet Protocol Tivoli Enterprise Monitoring Agent
123
124
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.
IBM Redbooks publications

For information about ordering these publications, see How to get IBM Redbooks publications on page 127. Note that some of the documents referenced here may be available in softcopy only. IBM Tivoli Composite Application Manager Family Installation, Configuration and Basic Usage, SG24-7151 Deployment Guide Series: IBM Tivoli Monitoring V6.1, SG24-7188
Other publications
These publications are also relevant as further information sources: IBM Tivoli Composite Application Manager for Web Resources publications: IBM Tivoli Composite Application Manager for Web Resources: J2EE Data Collector Installation Guide, GC23-6179 IBM Tivoli Composite Application Manager for Web Resources: WebSphere Distributed Data Collector Installation Guide, GC23-6180 IBM Tivoli Composite Application Manager for Web Resources: J2EE Agent Installation Guide, GC23-6181 IBM Tivoli Composite Application Manager for Web Resources: WebSphere Agent Installation Guide, GC23-6182 IBM Tivoli Composite Application Manager for Web Resources: Web Servers Agent Installation Guide, GC23-6183 IBM Tivoli Composite Application Manager for Web Resources: Community Edition Data Collector Installation Guide, GC23-6184 IBM Tivoli Composite Application Manager for Web Resources: Quick Start Guide, GC23-6185
125
IBM Tivoli Composite Application Manager for Web Resources: J2EE Agent Problem Determination Guide, GI11-8160 IBM Tivoli Composite Application Manager for Web Resources: WebSphere Agent Problem Determination Guide, GI11-8161 IBM Tivoli Composite Application Manager for Web Resources: Web Servers Agent Problem Determination Guide, GI11-8162 IBM Tivoli Monitoring publications: Exploring IBM Tivoli Monitoring, SC32-1803 IBM Tivoli Monitoring Administrator's Guide, SC32-9408 IBM Tivoli Monitoring: Configuring IBM Tivoli Enterprise Monitoring Server on z/OS, SC32-9463 IBM Tivoli Monitoring Installation and Setup Guide, GC32-9407 IBM Tivoli Monitoring Problem Determination Guide, GC32-9458 IBM Tivoli Monitoring User's Guide, SC32-9409 IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring, GC32-9462 IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461 IBM Tivoli Monitoring Universal Agent User's Guide, SC32-9459 Introducing IBM Tivoli Monitoring, GI11-4071
Online resources
These Web sites are also relevant as further information sources: ITCAM for Web Resources Web page: http://www-306.ibm.com/software/tivoli/products/composite-applicatio n-mgr-web-resources/index.html ITCAM for Web Resources product manuals: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?top ic=/com.ibm.itcamwas_wr.doc_6.2/welcome.htm
126
How to get IBM Redbooks publications

You can search for, view, or download IBM Redbooks publications, Redpapers, Technotes, draft publications and Additional materials, as well as order hardcopy IBM Redbooks publications, at this Web site: ibm.com/redbooks
Help from IBM

IBM Support and downloads: ibm.com/support IBM Global Services: ibm.com/services
Related publications
127
128
Index
Numerics
520188088CaptionFigColumn 8 installation task 28 WebSphere 8 data collector installation 53 data sources 7 data warehouse tables 14 db2 command 114 db2cmd command 114 db2move command 114 debug and trace 103 deployment large environment 22 medium scale 21 proof of concept 20 deployment configuration 20 disk requirement 10
A
am 8 application environment 4 application server resource analysis 4 application support files 28 installation process 35 installation task 28
B
back-end system 112 BCI 7 Byte Code Instrumentaiton, see BCI
E
EAR 84 enterprise application archive, see EAR environment 20 environment preparation 27 error statistics 4 event agent 7
C
cmwras1.log 102 collector process 7 command agent 7 commands config_dc.bat 63 db2 114 db2cmd 114 db2move 114 launchpad.cmd 54 netstat 74 setup.exe 35, 45 setup_DC_w32.exe 55 config_dc 63 config_dc.bat command 63 CPU usage 4 custom service 8
G
garbage collection data 7
H
hardware requirement 10
I
IBM Tivoli Monitoring installation 27 level 11 log files 102 workspace 78 install_plugin_trace.log 102 ITCAM for Web Resources architecture 5 customization task 29 data collector installation 53 disk requirement 11
D
data collector 67 command agent 7 configuration task 28 data sources 7 event agent 7
129
features 4 hardware requirement 10 installation overview 34 interconnection 5 J2EE agents 12 log files 101 memory requirement 11 monitoring agent 44 skills 26 software requirement 11 value propositions 5 Web servers requirements 13 WebSphere agent requirement 12 ITCAM for WebSphere data collector 6
installation 44 msg-dc-native.log 103 multithreaded process 7
N
native system services 6 netstat command 74
P
performance management 4 Performance Monitoring Infrastructure, see PMI PMI 4 processor speeds 10 project initiation 27
J
J2EE agents 12 J2EE application problems 4 Java Management eXtension, see JMX Java Virtual Machines, see JVM JMX 4 system resources 7 JVM 4
R
Redbooks publications Web site 127 Contact us x required skill 26 resource analysis 4
S
sample deployment environment 34 sample statement of work 117 setup.exe command 35, 45 setup_DC_w32.exe command 55 SFU 74 single processor 10 sizing data warehouse 14 skill pre-requisites 26 skill transfer 29 software requirement 11 solution demonstration task 29 Summarization and Pruning agent 23 supported J2EE agents 12
K
kcj.log 102 kcjras1.log 102 kfwras1.log 102 kick off 27 kyjjlog.properties 103 kyj-tema-*.log 102 kynjlog.properties 103 kyn-tema-*.log 102
L
large environment 22 launch pad 54 launchpad.cmd command 54 log files 101
T
Tivoli common directory 103 Tivoli Data Warehouse 23 Tivoli Enterprise Monitoring Agent 6 Tivoli Enterprise Portal 5 trace_install_plugin.trc 102 trace-dc-native.log 103 Trader application 113 BuySellServlet 111 company database 112 customer 112
M
memory requirement 10 memory usage 4 method trace 7 Microsoft Services for UNIX, see SFU monitoring agent
130
customer database 112 GetQuotesServlet 111 ListCompanyServlet 110 login.html 109 LogoutServlet 111 trader.zip file 114
W
Warehouse proxy 23 Web application performance management 4 Web server 13 monitoring 8 Web server sessions 4 WebSphere custom service 8 workspace 78
Index
131
132
(0.2spine) 0.17<->0.473 90<->249 pages
Back cover
Deployment Guide Series: IBM Tivoli Composite Application Manager for Web Resources V6.2
Manage Web application server resource performance Extensive deployment and usage scenarios Solution development guide included
This book is written as part of the deployment guide series. It provides a step-by-step guide for deploying IBM Tivoli Composite Application Manager (ITCAM) for Web Resources V6.2. This deployment guide will help an IBM Business Partner or service person plan and perform the deployment of the product. The discussion on ITCAM for Web Resources describes product architecture and components, planning and sizing considerations, and guidelines on setting up service engagements. Although the information is highly relevant for larger deployment engagements, it is also suitable for a small deployment system. The extensive deployment and usage scenarios can also help you demonstrate the product.
INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.
For more information: ibm.com/redbooks

SG24-7485-00 ISBN 0738486647

Deployment Guide Series IBM Tivoli Composite Application Manager For Web Resources V6.2 Sg247485

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deployment Guide Series IBM Tivoli Composite Application Manager For Web Resources V6.2 Sg247485

Uploaded by

Copyright:

Available Formats

Front cover

Budi Darmawan Andri Firtiyan Ronaldo Pires

Copyright IBM Corp. 2008. All rights reserved.

Deployment Guide Series: ITCAM for Web Resources V6.2

Deployment Guide Series: ITCAM for Web Resources V6.2

Copyright IBM Corp. 2008. All rights reserved.

Deployment Guide Series: ITCAM for Web Resources V6.2

The team that wrote this book

Copyright IBM Corp. 2008. All rights reserved.

Become a published author

Deployment Guide Series: ITCAM for Web Resources V6.2

Deployment Guide Series: ITCAM for Web Resources V6.2

Copyright IBM Corp. 2008. All rights reserved.

Deployment Guide Series: ITCAM for Web Resources V6.2

Copyright IBM Corp. 2008. All rights reserved.

1.1 Application server monitoring

1.2 ITCAM for Web Resources features

Deployment Guide Series: ITCAM for Web Resources V6.2

1.3 ITCAM for Web Resources value propositions

1.4 Architecture and interconnection

Chapter 1. Solution introduction

Tivoli Enterprise Monitoring Agent

Application servers with Data collectors

Tivoli Enterprise Management Server and Tivoli Enterprise Portal Server

Figure 1-1 ITCAM for Web Resources architecture

1.4.1 J2EE and WebSphere data collectors

Deployment Guide Series: ITCAM for Web Resources V6.2

Chapter 1. Solution introduction

Tivoli Enterprise Monitoring Agent

Figure 1-2 Data collector structure

1.4.2 Tivoli Enterprise Monitoring Agent

Deployment Guide Series: ITCAM for Web Resources V6.2

Copyright IBM Corp. 2008. All rights reserved.

2.1 Hardware prerequisites

Deployment Guide Series: ITCAM for Web Resources V6.2

WebSphere agent J2EE agent Web server agent

2.2 Software prerequisites

Chapter 2. Solution environment

2.2.1 WebSphere agent

2.2.2 J2EE agents

Deployment Guide Series: ITCAM for Web Resources V6.2

2.2.3 Web server agents

Chapter 2. Solution environment

2.3 Sizing consideration

Deployment Guide Series: ITCAM for Web Resources V6.2

Chapter 2. Solution environment

KYNWEBSVC KYNALARMM KYNSCHED KYNCLICOM KYNDURSUB KYNMECOM KYNMSGENG KYNMSGQUE KYNSVCOMEL

KYNSVCCOMP KYNTOPICSP KYNWMQCL KYNWMQLINK KYNWPMSV KYNWPMQM KYNWPMIP KYNWPTALS KYNWPPAGE

704 1288 988 1004 776 712 720 760 832

Deployment Guide Series: ITCAM for Web Resources V6.2

Size in bytes 836 1008 n/a n/a n/a

KYNWPLETS KYNAPHLTH KYNAPMONCF KYNRQMONCF KYNBASELN

Table 2-4 shows the sizing list for J2EE agents.

Chapter 2. Solution environment

Deployment Guide Series: ITCAM for Web Resources V6.2

Table name KYJSWEBCNT KYJWEBAPP KYJWLCCPL

Size 716 836 884

KYJWLJMSS KYJWLJTA KYJWLSRVLT

1088 900 1628

Chapter 2. Solution environment

Table name KHTSWEBSR KHTSWEBST KHTWSRS

Size 2704 1168 1028