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

7/31/2019 Deployment Guide Series IBM Tivoli Composite Application Manager for Web Resources V6.2 Sg247485

1/150

ibm.com/redbooks

Deployment Guide Series: IBMTivoli Composite ApplicationManager for Web Resources V6.2

Budi Darmawan

Andri Firtiyan

Ronaldo Pires

Manage Web application server

resource performance

Extensive deployment and

usage scenarios

Solution development

guide included

Front cover
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/150


3/150

Deployment Guide Series: ITCAM for WebResources V6.2

January 2008

International Technical Support Organization

SG24-7485-00


4/150

Copyright International Business Machines Corporation 2008. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

First Edition (January 2008)

This edition applies to Version 6, Release 2, Modification 0 of IBM Tivoli Composite ApplicationManager for Web Resources (product number 5724-S32).

Note: Before using this information and the product it supports, read the information inNotices on page vii.


5/150

Copyright IBM Corp. 2008. All rights reserved. iii

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Part 1. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Solution introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Application server monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 ITCAM for Web Resources features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 ITCAM for Web Resources value propositions . . . . . . . . . . . . . . . . . . . . . . 51.4 Architecture and interconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.4.1 J2EE and WebSphere data collectors . . . . . . . . . . . . . . . . . . . . . . . . 61.4.2 Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. Solution environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.1 WebSphere agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.2 J2EE agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.3 Web server agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.3 Sizing consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4 Typical deployment environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.4.1 Demonstration or proof of concept . . . . . . . . . . . . . . . . . . . . . . . . . . 202.4.2 Small and medium environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4.3 Large and very large environment . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3. Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1 Required skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2 Solution description and assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3 Task breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.3.1 Project kick off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.3.2 Environment preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.3 IBM Tivoli Monitoring setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.4 Application support files installation . . . . . . . . . . . . . . . . . . . . . . . . . 283.3.5 Agents and data collectors setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


6/150

iv Deployment Guide Series: ITCAM for Web Resources V6.2

3.3.6 Customizing the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3.7 Demonstrating the solution and skill transfer . . . . . . . . . . . . . . . . . . 29

Part 2. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 4. Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2 Installing application support files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.3 Installing the Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . . . . 444.4 Installing the data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.4.1 Setting up the application server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4.2 Installing the base data collector version 6.1 . . . . . . . . . . . . . . . . . . 544.4.3 Applying Fix Pack 1 and interim Fix 4 . . . . . . . . . . . . . . . . . . . . . . . . 61

4.4.4 Configuring data collectors in the application servers. . . . . . . . . . . . 624.5 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 5. Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.1 Usage scenario overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.2 Using the workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

5.3 Defining application health and baseline. . . . . . . . . . . . . . . . . . . . . . . . . . 845.4 Working with situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 6. Troubleshooting hints and tips . . . . . . . . . . . . . . . . . . . . . . . . 1016.1 IBM Tivoli Monitoring logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026.2 ITCAM for Web Resources logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Part 3. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Appendix A. The Trader application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Application components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Front-end J2EE Web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Back end implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Back end J2EE server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Initial setup for the demonstration server . . . . . . . . . . . . . . . . . . . . . . . . . 114DB2 database creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114WebSphere server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114WebSphere client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Appendix B. Sample statement of work. . . . . . . . . . . . . . . . . . . . . . . . . . 117ITCAM for Web Resources implementation service. . . . . . . . . . . . . . . . . . . . 118Executive summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Solution description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119


7/150

Contents v

Business partner responsibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Client responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Staffing estimate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Project schedule and milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Testing methodology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Completion criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Appendix C. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

System requirements for downloading the Web material . . . . . . . . . . . . . 122How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129


8/150

vi Deployment Guide Series: ITCAM for Web Resources V6.2


9/150

Copyright IBM Corp. 2008. All rights reserved. vii

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. Consultyour 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 IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility 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 suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof 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 madeto 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 atany time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials 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 withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements 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 onthe 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 themas 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 businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques 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 applicationprograms conforming to the application programming interface for the operating platform for which thesample 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.


10/150

viii Deployment Guide Series: ITCAM for Web Resources V6.2

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

Redbooks (logo) developerWorksz/OSAIXCICSDB2 Universal DatabaseDB2

IBMIMSMVSNetcoolOMEGAMONRedbooksSystem p

System xSystem zTivoli EnterpriseTivoliWebSphereWorkplace

The following terms are trademarks of other companies:

SAP NetWeaver, SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany andin several other countries.

Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporationand/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 theUnited States, other countries, or both.

Intel, Itanium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks ofIntel 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.


11/150

Copyright IBM Corp. 2008. All rights reserved. ix

Preface

This book is written as part of the deployment guide series. It provides astep-by-step guide for deploying IBM Tivoli Composite Application Manager(ITCAM) for Web Resources V6.2. This deployment guide will help an IBMBusiness Partner or service person plan and perform the deployment of theproduct.

The discussion on ITCAM for Web Resources describes product architecture andcomponents, planning and sizing considerations, and guidelines on setting upservice engagements.

Although the information is highly relevant for larger deployment engagements, itis also suitable for a small deployment system. The extensive deployment andusage 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 workingat the International Technical Support Organization, Austin Center, Texas.

Budi Darmawan is a Project Leader at the International Technical SupportOrganization, Austin Center. He writes extensively and teaches IBM classesworldwide on all areas of systems management, primarily applicationmanagement, business service management, and workload scheduling. Before

joining the ITSO in 1999, Budi worked in IBM Indonesia as a lead implementorand solution architect. His current interests are J2EE and service-oriented

architecture (SOA) application management, z/OS integration, and businessservice management.

Andri Firtiyan is a Solution Architect at Software Lab Services based in IBMIndonesia. He has 11 years experience in IT. He holds a Masters degree inComputer Science from the University of Indonesia. He was involved in the firstSOA Offering Roadmap project in the ASEAN region. He is an IBM Certified SOASolution Designer. His current focus is Tivoli Best Practice, Tivoli BusinessAutomation, and SOA.

Ronaldo Pires is an IBM IT Specialist. He joined IBM in 2004 and has beenworking on Global Technology Services Delivery in So Paulo, Brazil, supportingthe systems management infrastructure for IBM outsourcing customers. His skillsinclude IBM Tivoli Framework , IBM Tivoli Monitoring, IBM Tivoli Storage


12/150

x Deployment Guide Series: ITCAM for Web Resources V6.2

Manager, IBM Tivoli Identity Manager, Altiris Client Management Suite, BMCControl-M for z/OS, and BMC Control-D for z/OS. He holds a Bachelors degreein Mathematics from Faculdade de Filosofia Cincias e Letras de Santo Andr.He is Tivoli Certified Consultant for Tivoli Storage Manager and IBM CertifiedDeployment Professional for Tivoli Monitoring V5.1.2.

Thanks to the following people for their contributions to this project:

Dorothy WuIBM developerWorks, Silicon Valley Lab

Terry CopelandIBM Software Group

Become a published author

Join us for a two- to six-week residency program! Help write a book dealing withspecific products or solutions, while getting hands-on experience withleading-edge technologies. You will have the opportunity to team with IBMtechnical professionals, Business Partners, and Clients.

Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you will develop a network of contacts in IBM development labs andincrease your productivity and marketability.

Find out more about the residency program, browse the residency index, andapply 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 aboutthis 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:

[email protected]
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


13/150

Preface xi

Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South Road

Poughkeepsie, NY 12601-5400


14/150

xii Deployment Guide Series: ITCAM for Web Resources V6.2


15/150

Copyright IBM Corp. 2008. All rights reserved. 1

Part 1 Planning

This part discusses planning information for deploying IBM Tivoli CompositeApplication Manager (ITCAM) for Web Resources V6.2.

Part 1


16/150

2 Deployment Guide Series: ITCAM for Web Resources V6.2


17/150


Chapter 1. Solution introduction

This chapter introduces the solution based on IBM Tivoli Composite ApplicationManager (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


18/150


1.1 Application server monitoring

Businesses are relying more on a Web-based application environment. Thisenvironment is based on J2EE application servers that serve Web browser

requests or Web services requests. J2EE application servers are monolithicJava Virtual Machines (JVM) that have limited performance managementfunction. Typical interfaces for performance management of J2EE servers arePerformance Monitoring Infrastructure (PMI) and Java Management eXtension(JMX).

Performance management of Web-based applications covers:

J2EE application server resource analysis and understanding CPU andmemory usage of an application server related to its activities, such asrequest rate and active processing.

J2EE application individual performance with applications that are deployedin J2EE servers. These applications are not typically understood by users.Their performance must be monitored to pinpoint potential resourceproblems.

Web server sessions and error statistics to identify the request mix andstatistics for the Web servers. This helps understand access pattern of thestatic part of the Web site.

1.2 ITCAM for Web Resources features

ITCAM for Web Resources V6.2 allows simple monitoring of a Web applicationsresources, including Web servers, WebSphere servers, and other J2EEapplication 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 problemdetermination. This allows for a quick identification and potentially fixing theproblem before it impacts the users.

ITCAM for Web Resources can dynamically monitor the threshold. This alsoallows to set a baseline threshold for a normal behavior of the application. Theset baseline allows fewer situations to be fired as the settings are set from theapplication itself.

With the IBM Tivoli Monitoring integrated environment, ITCAM for WebResources allows correlation of situations from various resources withautomated actions and expert advice. This provides a quicker resolution ofproblems and reduces event storms.


19/150

Chapter 1. Solution introduction 5

ITCAM for Web Resources uses Tivoli Enterprise Portal as its primary interface.This allows a common user interface for data and events integration with otherTivoli Enterprise Portal-based solutions from IBM Tivoli Composite ApplicationManager, IBM Tivoli Monitoring, and IBM Tivoli OMEGAMON to providecomprehensive 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 theyresult 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 capabilitiesneeded 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 J2EEapplication servers. It collects performance metric using a data collector andforwards the information by using the IBM Tivoli Monitoring V6.1 infrastructure.


20/150


The application servers run the data collector, which is a collecting agent thatruns in the application server and sends monitoring information, using TivoliEnterprise Monitoring Agent, to the Tivoli Enterprise Monitoring Server. Thesedata collectors operate independently of each other. Figure 1-1 shows the overallarchitecture of ITCAM for Web Resources.

Figure 1-1 ITCAM for Web Resources architecture

The product consists of two main parts: the data collectors and the TivoliEnterprise Monitoring Agents. A data collector agent runs on each monitoredJ2EE application servers and communicates with the Tivoli Enterprise MonitoringAgent. The Tivoli Enterprise Monitoring Agent sends the performanceinformation 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 systemservices. They are tailored for particular environments where they are executed.

Tivoli Enterprise

Management Server

and

Tivoli Enterprise

Portal Server

I

Application servers with

Data collectors

Tivoli Enterprise

Monitoring Agent


21/150

Chapter 1. Solution introduction 7

Data collectors are configured as a multi-threaded process. They consist of thefollowing agents:

Command agent:

The command agent collects requests from other components for information

about EJB invocations, database connection pools, thread pools, stacktraces, memory analyses, and heap dumps.

Event agent:

The event agent provides data to the publish servers according to pollingfrequencies. This data includes system initialization data, applicationrequest-level data, and application method-level data.

Collector process:

The collector provides the monitoring data for Tivoli Enterprise Portal. Itcollects WebSphere Application Server and other J2EE application serverperformance metrics. This component communicates with Tivoli EnterpriseMonitoring Agent using a TCP/IP port.

The data collectors send probes into the application servers to analyze theapplications performance. The probes collect monitoring data and feed it totransport routines for Tivoli Enterprise Monitoring Agent. This relieves theprocessing burden of ITCAM for Web Resources from the application servers asmuch as possible. The data collectors and probes are not designed to analyze orinterpret data. They collect and route such data to Tivoli Enterprise MonitoringAgent.

The data sources used by the ITCAM for Web Resources data collector are:

JVMTI garbage collection data, method trace, stack trace, CPU time, andheap dump.

jJMX system resources.

PMI system resources (WebSphere only). OS services, platform CPU, and its environment.

Byte Code Instrumentation (BCI) for some classes.


22/150


The data collector in the J2EE server runs as a custom service called am.Figure 1-2 shows the WebSphere data collector structure.

Figure 1-2 Data collector structure

1.4.2 Tivoli Enterprise Monitoring Agent

The ITCAM for Web Resources Tivoli Enterprise Monitoring Agent forwardsinformation to the Tivoli Enterprise Monitoring Server for monitoring the use ofTivoli Enterprise Portal. For monitoring Web servers, you can also use TivoliEnterprise Monitoring Agent for Web Servers. You do not need a data collector tomonitor Web servers.

WebSphere

Custom Service

amBCI

JVMTI PMIJMX

Tivoli Enterprise

Monitoring Agent

KYN

To TEMS


23/150


Chapter 2. Solution environment

This chapter discusses the required environment for implementing ITCAM forWeb 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


24/150


2.1 Hardware prerequisites

The hardware requirement for ITCAM for Web Resources relates to therequirement of IBM Tivoli Monitoring V6.1. For IBM Tivoli Monitoring servers,

such as Tivoli Enterprise Monitoring Server or Tivoli Enterprise Portal Server, therecommended processor speeds are at minimum of 1 GHz for RISCarchitectures and 2 GHz for Intel architectures. A single processor is suitablewhen the components are installed on separate computers.

Table 2-1 lists the memory and disk requirements for IBM Tivoli Monitoringservers.

Table 2-1 IBM Tivoli Monitoring memory and disk requirements

The hardware requirement for IBM Tivoli Monitoring servers is discussed in detailat:

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install61.htm#hardware

Component Memory requirementa

a. Memory requirement is range based on the processing needs. The low end is foraround 100-200 monitoring agents, while the high end is for around 500-1000monitoring agents.

Disk space requirement

Hub monitoring server 70 MB - 100 MB 650 MB

Remote monitoring server 100 MB - 300 MB 250 MB

Tivoli Enterprise Portalserver

100 MB - 300 MB 800 MB

Tivoli Enterprise Portalclient

150 MB - 300 MB 150 MB

Tivoli data warehouse 2 GB - 8 GB Must be calculatedb

b. The data size of Tivoli Data Warehouse depends on the size of data for eachattribute groups. For each attribute groups, you need the number of detailedrecords per day, the data size per record, and the aggregation policy. See theTivoli Monitoring Information Center at:http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install65.htm#estimate

Warehouse proxy agent 50 MB - 100 MB 150 MB

Summarization andpruning agent

150 MB - 300 MB 150 MB
http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install61.htm#hardwarehttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install61.htm#hardwarehttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install65.htm#estimatehttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install65.htm#estimatehttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install61.htm#hardwarehttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install61.htm#hardwarehttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc/itm_install65.htm#estimate


25/150

Chapter 2. Solution environment 11

For more information about configuring IBM Tivoli Monitoring servers, seeDeployment Guide Series: IBM Tivoli Monitoring 6.1, SG24-7188.

Specifically for ITCAM for Web Resources, the agents have additionalrequirements for memory and disk spaces. These additional requirements are on

top of any existing hardware requirement for the supported monitoredenvironment. These monitored environments are listed in section 2.2, Softwareprerequisites on page 11. Table 2-2 lists the minimum and recommendedmemory and disk requirements.

Table 2-2 Requirements

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/HTML/itcam6.html

For J2EE agents:

http://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/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 TivoliMonitoring V6.1 with Fix Pack 5 or later. Additional software requirements forITCAM 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

Resource Additional memory Additional disk

space

(monitoring agent)

Additional disk

space

(data collector)

WebSphere agent 128 MB 100 MB 330 MB

J2EE agent 512 MB 512 MB 1 GB

Web server agent - 100 MB -
http://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWServers/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWServers/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWServers/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.html


26/150


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

The supported WebSphere software levels are:

WebSphere Application Server 5.1.0 and 5.1.1.14 with JDK 1.4.2_7, Baseand 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 Windows2003 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 Servercomponent of this application server is monitored, in Windows and AIXplatforms)

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

Note: For operating system specific requirement and WebSphere levels, seethe prerequisites page at:

http://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.html
http://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRWAS/prereq62/en_US/HTML/itcam6.html


27/150


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

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 Server2003 (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

Note: For operating system specific requirements and J2EE applicationserver levels and Java Runtime Environment versions, see the prerequisitespage at:

http://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.html
http://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWRJ2/prereq62/en_US/HTML/itcam6.html


28/150


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 isexplained in Appendix A of the agent installation guide manuals. We providethose 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

Recording frequency

KYNPREV WebSphere AgentEvents

616 1 record for each product event. These recordsare written when problems occur.

KYNAPSST Application ServerStatus

968 1 record per interval per server instance

KYNLOGANAL Log Analysis 1068 1 record per interval for each entry written into theapplication server log stream or file

KYNAPSRV Application Server 772 1 record per interval per application server

KYNCONTNR EJB Containers 880 1 record per interval per application server, plus 1record per interval per EJB container

KYNEJB Enterprise Java Beans 1040 1 record per interval for each EJB method

KYNCNTROP Container Object Pools 812 1 record per interval per application server, plus 1record per interval per EJB container

KYNAPP Web applications 1060 1 record per interval per Web application

KYNSERVLT Servlets and JSPs 1320 1 record per interval per servlet

KYNTRANS Container Transactions 812 1 record per interval per application server plus 1record per interval per EJB container

KYNCACHE Dynamic Cache 588 1 record per cache per cycle

KYNCACHT Dynamic CacheTemplates

952 1 record per cache template per cycle

KYNJ2C J2C Connection Pools 972 1 record per J2EE connection pool per cycle

KYNSERVS Servlet Sessions 1064 1 record per servlet session per interval

KYNTHRDP Thread Pools 864 1 record per thread pool per interval


29/150


KYNWLMCL Workload Management

Client

592 1 record per Workload Management (WLM) client

per interval

KYNWLMSR Workload ManagementServer

632 1 record per WLM server per interval

KYNGCACT Garbage CollectionAnalysis

732 1 record per interval per application server

KYNGCAF Allocation Failure 616 1 record per interval for each allocation failureblock

KYNGCCYC Garbage CollectionCycle

656 1 record per garbage-collection cycle per interval

KYNREQUEST Request Analysis 1468 1 record per interval for each workload in eachapplication server

KYNREQSEL Selected Request 1240 1 record per interval for each workloaddegradation in each application server

KYNDATAS Datasources 1156 1 record per interval per data source in eachapplication server

KYNJMSSUM JMS Summary 852 1 record per interval per MQ queue in eachapplication server

KYNREQHIS Request times andrates

976 1 record per interval per WebSphere ApplicationServer

KYNDBCONP DB Connection Pools 1096 1 record per datasource per interval plus 1 recordper application server per interval

KYNDCMSG Data Collector (DC)Messages -WebSphere

1388 1 record per each entry written into DC logmessage file

KYNDCSSTK Distribution andConsistency Services(DCS) Stack

1032 1 record per DCS stack per interval plus 1 recordper application server per interval

KYNHAMGMT High AvailabilityManager

724 1 record per application server per interval

KYNWEBSGW Web Services Gateway 968 1 record per Web Services Gateway per intervalplus 1 record per application server per interval


in

bytes

Recording frequency


30/150


KYNWEBSVC Web Services 1004 1 record per Web Service per interval plus 1

record per application server per intervalKYNALARMM Alarm Manager 980 1 record per Work Manager per interval plus 1

record per application server per interval

KYNSCHED Scheduler 1000 1 record per Scheduler per interval plus 1 recordper application server per interval

KYNCLICOM Client Communications 1220 1 record per application server per interval

KYNDURSUB Durable Subscriptions 1504 1 record per Durable Subscription per interval

KYNMECOM Messaging EngineCommunications


KYNMSGENG Messaging Engines 972 1 record per Messaging Engine per interval plus 1record per application server per interval

KYNMSGQUE Queue 1040 1 record per Queue per interval

KYNSVCOMEL Service ComponentElements

1752 1 record per Service Component Element perinterval plus 1 record per application server per

interval

KYNSVCCOMP Service Components 704 1 record per Service Component plus 1 recordper application server

KYNTOPICSP Topic Spaces 1288 1 record per Topic Space per interval

KYNWMQCL WMQ Client LinkCommunications


KYNWMQLINK WMQ Link

Communications


KYNWPMSV Workplace Mail Service 776 1 record per application server per interval

KYNWPMQM Workplace MailQueues

712 1 record per Mail Queue per interval

KYNWPMIP Workplace MailIMAP/POP

720 1 record per protocol (IMAP/POP) per interval

KYNWPTALS Portal Summary 760 1 record per application server per interval

KYNWPPAGE Portal Page Summary 832 1 record per Portal Page per interval plus 1 recordper application server


in

bytes

Recording frequency


31/150


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

Table 2-4 Historical data sizing information for J2EE agent

KYNWPLETS Portlet Summary 836 1 record per portlet per interval plus 1 record per

application serverKYNAPHLTH Application Health

Status1008 1 record per interval per application for each

application server

KYNAPMONCF Application MonitoringConfiguration

n/a Not historical table

KYNRQMONCF Requests MonitoringConfiguration


KYNBASELN Baseline n/a Not historical table


in

bytes

Recording frequency

Table name Object name Size Recording frequency

KYJAPHLTH Application HealthStatus

1008 1 record per interval per application for eachapplication server

KYJAPMONCF Application MonitoringConfiguration


KYJAPSRV Application Server -J2EE


KYJAPSST Application ServerStatus - J2EE

968 1 record per interval per server instance

KYJBASELN Baseline n/a Not historical table

KYJDATAS Datasources - J2EE 1284 1 record per interval per data source in eachapplication server

KYJDCMSG DC Message - J2EE 1388 1 record per each entry written into DC logmessage file.

KYJEJB Enterprise Java BeanModules - J2EE

1020 1 record per JSR77 EJB module per interval plus1 record per application server

KYJGCACT Garbage Collection

Analysis - J2EE


KYJGCAF Allocation Failure -J2EE

744 1 record per interval for each allocation failureblock


32/150


KYJGCCYC Garbage CollectionCycle - J2EE

784 1 record per garbage collection cycle per interval

KYJJCACP JCA Connection Pools -J2EE

1016 1 record per JSR77 JCA resource per intervalplus 1 record per application server

KYJJDKJVM JDK - JVM 1732 1 record per interval for each application server

KYJJDKMEM JDK - Memory 724 1 record per interval for each application server

KYJJDKOS JDK - OperationSystem

1484 1 record per interval for each application server

KYJJDKTHR JDK - Threading 1224 1 record per interval for each application server

KYJJMSSUM JMS Summary - J2EE 960 1 record per interval per MQ queue in eachapplication server

KYJJTARES JTA Resources - J2EE 960 1 record per JSR 77 JTA Resource per intervalplus 1 record per application server

KYJLOGANAL Log Analysis - J2EE 1068 1 record per interval for each entry written into theapplication server log stream or file

KYJPREV J2EE Agent Events 704 1 record for each product event. These records

are written when problems occur.KYJREQHIS Request times and

rates - J2EE976 1 record per interval per J2EE server

KYJREQSEL Selected Request -J2EE

1368 1 record per interval for each workloaddegradation in each application server

KYJREQUEST Request Analysis -J2EE

1184 1 record per interval for each workload in eachapplication server

KYJRQMONCF Requests MonitoringConfiguration n/a Not historical table

KYJSDBCON DB Connection Pools -NetWeaver

972 1 record per DB connection pool per interval plus1 record per application server

KYJSEJB Enterprise Java BeanService - NetWeaver

1152 1 record per EJB per interval plus 1 record perapplication server

KYJSERVLT Servlets and JSPs -J2EE

972 1 record per interval per servlet

KYJSJTASUM JTA Summary -NetWeaver




33/150


Table 2-5 lists the sizing list for Web server agents.

Table 2-5 Historical data sizing information for Web server agent

KYJSWEBCNT Web Container -NetWeaver


KYJWEBAPP Web applications -

J2EE

836 1 record per interval per Web application

KYJWLCCPL J2EE ConnectorConnection Pools -WebLogic

884 1 record per J2C connection pool per interval plus1 record per application server

KYJWLDBCON JDBC ConnectionPools - WebLogic

900 1 record per JDBC connection pool per intervalplus 1 record per application server

KYJWLEJB Enterprise Java Beans

- WebLogic

1176 1 record per EJB per interval plus 1 record per

EJB component, plus 1 record per applicationserver

KYJWLEJBC Enterprise Java BeanComponents -WebLogic

968 1 record per EJB component per interval plus 1record per application server

KYJWLJMSS JMS Sessions -WebLogic

1088 1 record per JMS session per interval plus 1record per application server

KYJWLJTA Java Transaction

Service - WebLogic


KYJWLSRVLT Servlets and JSPs -WebLogic

1628 1 record per Servlet or JSP per interval plus 1record per Web Application, plus 1 record perapplication server

KYJWLWEBAP Web Applications -WebLogic

1296 1 record per Web Application per interval plus 1record per application server



KHTAWEBSR Apache Web server 1056 1 per interval per server

KHTAWEBST Apache Web sites 984 1 per interval per site

KHTEVNT Web Servers AgentEvents

616 Depends on messages count from TivoliEnterprise Monitoring Agent (TEMA)

KHTIWEBSR Web server 928 1 per interval per server

KHTIWEBST Web sites 1528 1 per interval per site


34/150


2.4 Typical deployment environments

This section discusses deployment considerations for ITCAM for Web ResourcesV6.2. These considerations are related to the structure of IBM Tivoli Monitoringservers and the connection for ITCAM for Web Resources agents that connect to

Tivoli Enterprise Monitoring Server. See also Deployment Guide Series: IBMTivoli 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 bringingthe system up and showing the functions. It does not consider performance andload of the servers nor system reliability. A typical configuration is shown inFigure 2-1 on page 21.

KHTSWEBSR Sun Web server 2704 1 per interval per server

KHTSWEBST Sun Web sites 1168 1 per interval per site

KHTWSRS Web Servers status 1028 1 per interval



35/150


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 DataWarehouse and Tivoli Enterprise Portal Server database, End-user Response

Time Dashboard agent, Tivoli Enterprise Monitoring Server, Tivoli EnterprisePortal Server, and Warehouse Proxy. The Summarization and Pruning agentis not configured because the system is not around for a long period of time.

Various agents, such Tivoli Enterprise Monitoring Agent (TEMA), running onapplication server machines to monitor application server performance.

2.4.2 Small and medium environment

A small and medium scale environment accommodates a larger number ofagents with consideration on system performance. This environment has morespecialization for the servers and allows load balance to remote Tivoli EnterpriseMonitoring Server. This environment is applicable for one to five sites with lessthan 1000 monitored clients. A typical configuration is shown in Figure 2-2 onpage 22. Each remote Tivoli Enterprise Monitoring Server is capable of handlingup to 1000 agents. A client can run multiple agents.

TEMA TEMATEMATEMA

DB2 Data WarehouseMonitoring Server

Portal Server

Warehouse Proxy

Sumarization and Pruning


36/150


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 WarehouseProxy, Summarization and Pruning Agent.

Remote Tivoli Enterprise Monitoring Server handling agent communicationfrom different sites, instead of directly from the hub Tivoli EnterpriseMonitoring Server.

2.4.3 Large and very large environment

For a larger environment, redundancy and performance are critical. This designincludes multiple levels of Tivoli Enterprise Monitoring Server structure withfailover capability. All major central functions are running on separate serverswith their required redundancy. Figure 2-3 on page 23 shows an example of alarge system deployment.

TEMA

TEMA

TEMA

TEMATEMA

TEMA

TEMATEMA

TEMA

RemoteTEMS

RemoteTEMS

RemoteTEMS

DB2 (for Portal Server)Hub Monitoring Server

Portal Server

DB2 Data Warehouse

Warehouse ProxySumarization and Pruning


37/150


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.

TEMA

TEMA

TEMA

TEMATEMA

TEMA

TEMATEMA

TEMA

Remote

TEMS

Remote

TEMS

Remote

TEMS

Warehouse Proxy

Sumarization and Pruning

Failover

Hub Monitoring Servers

Portal

Server

DB2

database


38/150



39/150


Chapter 3. Project planning

This chapter discusses project planning information to help you deploy ITCAM forWeb Resources V6.2. The topics are:

Required skills on page 26 Solution description and assumptions on page 26 Task breakdown on page 27

3

3.1 Required skills


40/150


3.1 Required skills

To implement ITCAM for Web Resources V6.2, you need the followingprerequisite 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 WebResources 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 thecustomer. In these sessions, address the following items:

The applications or IT services to be included in the implementation, whichserver hosts those applications, the location of these servers, and whatconnectivity options are available.

The Web servers and application servers software level and the user ID foraccessing them.

The applications running on the application servers.

Based on the above requirements from the customer, you can start developingthe solution configuration and implementation methods. The configurationinvolved defines where to put critical components, such as Tivoli EnterpriseMonitoring Server and Tivoli Enterprise Portal Server. The implementationmethod includes deployment of the agents and data collectors.

You can perform only a sub-set of the identified final configuration. The completeconfiguration is up to the customer to implement. You must predetermine the

initial subset to implement the final configuration.

3.3 Task breakdown


41/150

Chapter 3. Project planning 27

The detailed tasks for ITCAM for Web Resources implementation is divided intothe 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 genericproject plan to be laid out.

The kick off is also an important milestone to promote the project to thecustomers 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 appropriateoperating system and network connectivity. This applies to machines that runTivoli Enterprise Monitoring Server, Tivoli Data Warehouse, and otherservers.

Identifying machines on which Tivoli Enterprise Monitoring Agent is installed.

This includes tabulating their IP addresses, host name, owner, access to themachine, and other relevant information

Collecting installation media and required software for the installation.

Depending on the size of the implementation and the readiness of theenvironment, 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 MonitoringV6.1. This includes installing DB2 Universal Database V8.2 for Tivoli EnterprisePortal Server and possibly Tivoli Data Warehouse.

For IBM Tivoli Monitoring, you must install the following components:


42/150


Tivoli Enterprise Monitoring Server

Tivoli Enterprise Portal Server

Warehouse Proxy

Summarization and Pruning Agent (not needed for demonstration or proof ofconcept 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 theapplication support files on Tivoli Enterprise Monitoring Server, Tivoli EnterprisePortal desktop client, and Tivoli Enterprise Portal Server machines.

Depending on the configuration of the IBM Tivoli Monitoring environment, youmight need to install these files on one or more machines. During installation, youmust restart Tivoli Enterprise Monitoring Server and Tivoli Enterprise PortalServer. You should schedule for minimal interruption of the operation.

See section 4.2, Installing application support files on page 35 for moreinformation. 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 appropriatemachines. This deployment must be done with the least interruption to theapplication running on these servers. See section 4.3, Installing the TivoliEnterprise Monitoring Agent on page 44 for more information.

Data collector installation and configuration must be performed on the J2EEapplication server. This requires modification on the application serverenvironment and a restart of the application server. This process is potentiallydisruptive to the application processing and must be scheduled accordingly. Seesection 4.4, Installing the data collector on page 53 for more information.

Depending on the environment, the following are a few ideas on installing TivoliEnterprise Monitoring Agent:

Installation with an existing software distribution mechanism, such as IBMTivoli Configuration Manager.


43/150


44/150



45/150


Part 2 Deployment

This part describes scenarios related to the actual deployment and usage of

ITCAM for Web Resources V6.2.

Part 2


46/150


4


47/150


Chapter 4. Installation andconfiguration

This chapter provides step-by-step instructions for installing ITCAM for WebResources 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

4

4.1 Installation overview


48/150


ITCAM for Web Resources is a solution that is based on the IBM TivoliMonitoring V6.1 platform. It monitors and manages applications running oncommonly available application servers and Web servers. The application serverplatforms include IBM WebSphere, WebLogic, SAP, Oracle, JBoss, Tomcat,J2SE, and WebSphere Application Server Community Edition. The supportedWeb servers are Microsoft IIS, SUN, and Apache Web Servers.

As discussed in section 1.4, Architecture and interconnection on page 5, theproduct consists of the data collector and the Tivoli Enterprise Monitoring Agentthat connect to the Tivoli Enterprise Monitoring Server. The installation processconsists of:

Section 4.2, Installing application support files on page 35 is a prerequisitefor using the agents. The Tivoli Enterprise Monitoring Server and TivoliEnterprise Portal Server need the information about the agent to bepre-populated.

Section 4.3, Installing the Tivoli Enterprise Monitoring Agent on page 44discusses the installation of Tivoli Enterprise Monitoring Agent forWebSphere.

Section 4.4, Installing the data collector on page 53 describes the

necessary installation process for the data collector. This data collector is thesame code for both IBM Tivoli Composite Application Manager forWebSphere and ITCAM for Web Resources.

For more information about IBM Tivoli Monitoring, see Deployment Guide Series:IBMTivoli Monitoring V6.1, SG24-7188. It is a step-by-step deployment guide forIBM Tivoli Monitoring V6.1 which covers small to large environments anddiscusses best practices for a deployment plan.

Figure 4-1 on page 35 shows our sample deployment environment. We have theapplication server node on srv177 and the IBM Tivoli Monitoring server insrv178. In this configuration, all the IBM Tivoli Monitoring components arerunning on the same machine, which is best suited for a demonstration or proofof concept environment.

Note: The installation media contains the Netcool ASM agent. This is anoptional component that you can use to integrate with the Micromuse Netcoolsolution. Our installation process does notcover this component.


49/150

Chapter 4. Installation and configuration 35

Figure 4-1 Sample deployment environment

4.2 Installing application support files

This section describes the installation of the application support files for TivoliEnterprise Monitoring Agent for WebSphere on a Windows platform. Before you

view data collected by monitoring agents, you must install and enable applicationsupport for the agents. The application support files provide agent-specificinformation for workspaces, helps, situations, template, and other data.

All monitoring agents require that application support are configured on allinstances 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 MonitoringServer, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal desktopclient. You must acquire the appropriate IBM Tivoli Monitoring environmentinformation, including the host names and communication protocols for theappropriate components listed above.

In our sample deployment environment, we have a single server running TivoliEnterprise Monitoring Server, Tivoli Enterprise Portal, and Tivoli Enterprise

Portal Server.

The steps are:

1. Stop the Tivoli Enterprise Monitoring Server, or the installation processautomatically stops the Tivoli Enterprise Monitoring Server.

2. Run setup.exe from the Windows subdirectory of the installation media.

srv177WebSphere Application Server

ITCAM for Web Resource data collector

ITCAM for Web Resource WebSphere TEMA

srv178Tivoli Enterprise Monitoring Server

Tivoli Enterprise Portal Server

Tivoli Enterprise Portal

Note: We assume that IBM Tivoli Monitoring server has been installedproperly. The monitoring server will be stopped during this process. You canalso use the launchpad to install the application support files.


50/150


51/150


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 monitoringacross your environment from the monitoring server. Assuming you alreadyhave the Operating System monitoring agent on the server, you can remotelydeploy and configure monitoring agents. Put a check for Monitoring Agent forWebSphere to add the agent to the deployment depot and click Next.


52/150


Figure 4-4 Agent deployment dialog

8. After the application support files installation is complete, a configurationwindow is displayed with all the components you just selected forconfiguration. Click Next as shown in Figure 4-5.


53/150


Figure 4-5 Configuration options

9. The Tivoli Enterprise Portal configuration starts. Select the host name of themachine where Tivoli Enterprise Portal Server resides. Click Next as shownin Figure 4-6.


54/150


Figure 4-6 Tivoli Enterprise Portal Server host name

10.The next steps configure application support files for Tivoli EnterpriseMonitoring Server:

a. Ensure the communication protocol to Tivoli Enterprise Monitoring Serverare correct and click OK, as shown in Figure 4-7 on page 41.


55/150


56/150


Figure 4-9 Selecting Tivoli Enterprise Monitoring Server

d. Select the application support file to add. The Tivoli Enterprise MonitoringServer windows opens. This window lists the application supportpackages that you selected in Step 7. Click OK to begin configuring TivoliEnterprise Monitoring Server using the SQL files listed on this window, asshown in Figure 4-10.

Figure 4-10 Selecting application support to be added

e. Figure 4-11 shows that the application support addition has beencompleted with return code of 0. Click Next.

Figure 4-11 Application support addition complete

11.The next steps configure the agent defaults connection to the TivoliEnterprise Monitoring Server:

a. Specify the default communication protocol for the agent to communicate


57/150


with Tivoli Enterprise Monitoring Server and click OK, as shown inFigure 4-12.

Figure 4-12 Communication protocol defaults

b. Define the communications parameters between the agents and TivoliEnterprise Monitoring Server and click OK, as shown in Figure 4-13.

Figure 4-13 Communication defaults for IP.PIPE


58/150

Agent or IBM Tivoli Composite Application Manager for J2EE Tivoli EnterpriseMonitoring Agent.

1. Run setup.exe from the WINDOWS sub directory of the installation media.


59/150


2. Click Next on the Welcome window as shown in Figure 4-15.

Figure 4-15 Welcome dialog

3. Accept the product prerequisite as shown in Figure 4-16 and click Next.


60/150


Figure 4-16 Installation requirements

4. ITCAM for Web Resources requires a specific version of IBM GSKit and IBMJava. Verify if the required versions of IBM GSKit and IBM JAVA are installedand click Next,as shown in Figure 4-17.


61/150


Figure 4-17 Install prerequisites

5. Click Accept on the software license agreement.

6. Select the installation path as shown in Figure 4-18. Click Next.


62/150


Figure 4-18 Installation path


63/150

8. The installation summary dialog is shown in Figure 4-20. Click Next to begininstallation.


64/150


Figure 4-20 Installation summary dialog

9. After the installation is completed, the configuration options window appearsas shown in Figure 4-21.


65/150


Figure 4-21 Configuration options

10.From the configuration option dialog, configure the communication protocoldefaults to connect to Tivoli Enterprise Monitoring Server, as shown inFigure 4-22.


66/150


Figure 4-22 Communication to Tivoli Enterprise Monitoring Server

11.The WebSphere agent configuration dialogs is a tabbed window shown inFigure 4-23. You can accept all the defaults and click OK.


67/150


Figure 4-23 Configuration for WebSphere agent

4.4 Installing the data collector

The data collector runs on each monitored application server, and relaysmonitoring information to IBM Tivoli Monitoring agent. You must install the datacollector components from IBM Tivoli Composite Application Manager forWebSphere with a specific level. This includes the data collector version 6.1using Fix Pack 1 and interim Fix 4. The installation is performed from both thedata collector installation image and the launch pad CD, on which the requiredfixes are distributed.

The installation is performed in the following order:

1. Section 4.4.1, Setting up the application server on page 54 lists prerequisitesteps for the data collector installation.

2. Section 4.4.2, Installing the base data collector version 6.1 on page 54includes the installation of the IBM Tivoli Composite Application Manager forJ2EE V6.1 or IBM Tivoli Composite Application Manager for WebSphere V6.1data collector.

3. Section 4.4.3, Applying Fix Pack 1 and interim Fix 4 on page 61 lists therequired patches for ITCAM for Web Resources V6.2.


68/150


69/150


Figure 4-24 LaunchPad window

2. From the Install Products link, select the Install Data Collector for ITCAMfor WebSphere V6.1. When you click the Quick Launch column, this invokesthe setup_DC_w32.exe from the path specified in the list. Make sure you havethe 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 welcomedialog.


70/150


Figure 4-25 Welcome window

3. In the software license agreement dialog (Figure 4-26), accept the licenseagreement and click Next.


71/150


Figure 4-26 Software license agreement

4. Specify the installation directory for the data collector, as shown inFigure 4-27. We use the path C:\IBM\itcam\WebSphere\DC. Click Next. Thispath is created if it does not exist.


72/150


Figure 4-27 Installation directory

5. The next dialog in Figure 4-28 allows you to save a response file. This is anexcellent way of recording an installation script for a silent install. We save theresponse file in C:\ITCAMWR file. Click Next.

Note: If you install the data collector to the current machine, a response fileis only generated if the GUI installation completes successfully


73/150


Figure 4-28 Generate response file window

is only generated if the GUI installation completes successfully.

6. A window displays the summary information about the data collectorinstallation, as shown in Figure 4-29. Click Install to begin the installation.


74/150


Figure 4-29 Summary information window

7. In the dialog for launching the Configuration Tools, select the option to deferthe launching of the configuration tool as shown in Figure 4-30.


75/150


Figure 4-30 Launch data collector configuration window

8. Click Next to continue. A successful completion of the installation isdisplayed. Click Finish. See section 4.4.4, Configuring data collectors in theapplication 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. Therequired patches are supplied in the same CD image as the launch pad. Inthe install product page, ensure the correct Image Location is supplied for thepatches. The default is 6.1.0-TIV-ITCAMfWAS_MP-FP0001 and6.1.0.1-TIV-ITCAMfWAS_MP-IF0004. The directories contain the

silentUpdate.bat file. If you need to change the directory, click the link andbrowse to the correct directory as shown in Figure 4-31 on page 62.


76/150


Figure 4-31 Product Installation window

2. Click the icon under the column labeled Quick Launch. This launches theinstallation program for the fix pack for the data collector. Now launch the6.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 2003server, 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 theend of the installation process or by running the tool from the installation


77/150

3. Select Configure servers for data collection, as shown in Figure 4-33. ClickNext.


78/150


Figure 4-33 Configure window

4. For ITCAM for Web Resources, only configure the data collector for displayingdata on the Tivoli Enterprise Portal interface. The application managementinterface is provided if you use either IBM Tivoli Composite ApplicationManager for WebSphere or IBM Tivoli Composite Application Manager forJ2EE. See Figure 4-34. Click Next.


79/150


Figure 4-34 Choose data collector server type


80/150

6. A window indicating a selected IP address for the data collector displays asshown in Figure 4-36. This window appears when you have multiple networkcards and need to adjust the ports for an enabled firewall. This dialog is notused for ITCAM for Web Resources. Use the default information here. Thecommunication parameter is performed by the Tivoli Enterprise MonitoringAgent to the Tivoli Enterprise Monitoring Server. Click Next.


81/150


Figure 4-36 Data collector host window


82/150


83/150

9. Figure 4-39 shows information about the selected application server. Confirmthe information and click Next.


84/150


Figure 4-39 WebSphere information review window

10.The installation wizard communicates to the administration application of theapplication server. For the Network Deployment installation, this connects tothe deployment manager instance. In Figure 4-40, specify the correct hostname and port that are used for the administration application. Click Next.


85/150


Figure 4-40 WebSphere administration application connection window

11.The installation wizard connects to the administration application and displaysa tree of the application server as shown in Figure 4-41. Select the serversand click Next.


86/150


Figure 4-41 Choose server window

12.Figure 4-42 allows you to save a response file for performing a silent install forother data collectors. This is useful for deploying a large number of datacollector with minimal interaction with the machines. Cl

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

Documents

Transcript of Deployment Guide Series IBM Tivoli Composite Application Manager for Web Resources V6.2 Sg247485