Solution deployment guide for ibm tivoli composite application manager for web sphere sg247293

Front cover

Solution Deployment Guide for
IBM Tivoli Composite Application
Manager for WebSphere

Quickly start a services engagement
with ITCAM for WebSphere

Statement of work samples and
scope development assistance

Includes sample code and
installation instructions

Budi Darmawan

ibm.com/redbooks

International Technical Support Organization

Solution Deployment Guide for IBM Tivoli
Composite Application Manager for WebSphere

December 2006

SG24-7293-00

Note: Before using this information and the product it supports, read the information in
“Notices” on page vii.

First Edition (December 2006)

This edition applies to Version 6, Release 0 of IBM Tivoli Composite Application Manager for
WebSphere (product number 5724-L62).

© Copyright International Business Machines Corporation 2006. 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

Chapter 1. IBM Tivoli Composite Application Manager for WebSphere
solution offering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Services solution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 ITCAM for WebSphere concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.2 Supported platform overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 ITCAM for WebSphere solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3.1 Solution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.2 Software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.3 Suggested hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Document organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2. Planning for customer engagement . . . . . . . . . . . . . . . . . . . . . 13
2.1 Services engagement preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.1 Implementation skills. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.2 Available resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 Solution scope and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.1 Basic solution definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.2 Cross-sell and up-sell opportunities . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Services engagement overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1 Executive Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2 Demonstration system setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.3 Analyze solution tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.4 Creating a contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4 Defining solution timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.1 Environment analysis tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.2 WebSphere application management tasks . . . . . . . . . . . . . . . . . . . 26
2.5 Statement of work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.5.1 Environment analysis service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.5.2 WebSphere application management service. . . . . . . . . . . . . . . . . . 33

© Copyright IBM Corp. 2006. All rights reserved. iii

Chapter 3. Demonstration of ITCAM for WebSphere . . . . . . . . . . . . . . . . . 37
3.1 Demonstration system setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.1.1 Installing application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.1.2 Installing ITCAM for WebSphere environment . . . . . . . . . . . . . . . . . 41
3.1.3 Setting up management resources . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.4 Running the application load generator . . . . . . . . . . . . . . . . . . . . . . 43
3.2 WebSphere Application Server monitoring . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3 Generating performance report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4. Implementation of ITCAM for WebSphere service. . . . . . . . . . 47
4.1 Install the managing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2 Modify the managing server for the other site . . . . . . . . . . . . . . . . . . . . . . 61
4.3 Install data collectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4 Customize the management environment. . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.1 IBM Tivoli Composite Application Manager for WebSphere . . . . . . 71
4.4.2 Activating data collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.4.3 Defining server groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.4.4 Defining operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.5 Run initial data collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.6 Collect performance reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.7 Run detailed data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.7.1 Scheduling monitoring level changes . . . . . . . . . . . . . . . . . . . . . . . . 85
4.7.2 Getting transaction trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.7.3 Performing lock analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.7.4 Performing memory leak analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.8 Develop the finding report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.9 Remove the data collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 5. Complementary solutions for ITCAM for WebSphere
engagement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.1 Cross-sell and up-sell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.2 Additional solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.2.1 Managing and analyzing response time . . . . . . . . . . . . . . . . . . . . . 106
5.2.2 Working with messaging infrastructure . . . . . . . . . . . . . . . . . . . . . . 107
5.2.3 Managing Web Services and SOA infrastructure . . . . . . . . . . . . . . 108
5.3 Enhancement solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.3.1 Enabling a split server for load balancing and reliability . . . . . . . . . 109
5.3.2 Security enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.3.3 Integrating performance monitoring with the portal solution . . . . . . 110
5.3.4 Collecting performance information in Tivoli Data Warehouse . . . . 110

Appendix A. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

iv Solution Deployment Guide for IBM Tivoli Composite Application Manager for WebSphere

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

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Contents v

vi Solution Deployment Guide for IBM Tivoli Composite Application Manager for WebSphere

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.

© Copyright IBM Corp. 2006. All rights reserved. vii

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

AIX® Monitoring On Demand® Tivoli Enterprise™
CICS® MVS™ Tivoli Enterprise Console®
Database 2™ OMEGAMON® Tivoli®
DB2 Universal Database™ OS/400® VTAM®
DB2® PartnerWorld® WebSphere®
IBM® Redbooks™ z/OS®
IMS™ Redbooks (logo) ™

The following terms are trademarks of other companies:

Enterprise JavaBeans, EJB, Java, JavaBeans, JavaServer, JavaServer Pages, JDBC, JMX, JSP, JVM,
J2EE, Solaris, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.

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

Intel, Pentium, 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 Solution Deployment Guide for IBM Tivoli Composite Application Manager for WebSphere

Preface

This IBM® Redbook is written for services professionals who are responsible for
developing, selling, and implementing customer-based service engagements.
The book focuses on implementation services for IBM Tivoli® Composite
Application Manager for WebSphere® V6.0.

IBM Tivoli Composite Application Manager for WebSphere is a performance
management solution for WebSphere Application Server-based applications. It
enables monitoring of various performance aspects of WebSphere Application
Servers and provides valuable assistance in finding and removing application
bottlenecks. This implementation service for IBM Tivoli Composite Application
Manager for WebSphere is suitable for customers with multiple mission-critical
applications deployed on WebSphere Application Server.

This book explains the fundamental aspects of services engagement and
Statement of Work creation. We explore in detail how to analyze the effort
required for implementing the solution. We also provide several additional
add-ons that you might be able to package in the implementation service.

This book is meant to be used in conjunction with Deployment Guide Series: IBM
Tivoli Composite Application Manager for WebSphere V6.0, SG24-7252. We will
not cover deployment in detail; we are more focused on building the service
engagement package.

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, Poughkeepsie Center.

Budi Darmawan is a Consulting IT Specialist at the International Technical
Support Organization, Austin Center. He writes extensively and teaches IBM
classes worldwide about all areas of systems management and Tivoli solutions.
Before joining the ITSO in 1999, Budi worked as lead implementer and solution
architect in IBM Indonesia Integrated Technology Services, IBM Global Services.
His current interests include availability management, z/OS® administration, and
Java™ programming.

© Copyright IBM Corp. 2006. All rights reserved. ix

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

Betsy Thaggard
International Technical Support Organization, Poughkeepsie Center

Elizabeth Purzer
IBM Software Group

Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbook
dealing with specific products or solutions, while getting hands-on experience
with leading-edge technologies. You’ll team with IBM technical professionals,
Business Partners, and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As
a bonus, you’ll 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 Redbooks™ to be as helpful as possible. Send us your comments
about this or other IBM Redbooks in one of the following ways:
Use the online Contact us review redbook form found at:
ibm.com/redbooks
Send your comments in an e-mail to:
redbook@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

x Solution Deployment Guide for IBM Tivoli Composite Application Manager for WebSphere

1

Chapter 1. IBM Tivoli Composite
Application Manager for
WebSphere solution offering
This chapter discusses some initial concepts regarding the ITCAM for
WebSphere solution that you will be able to define, sell, and implement for your
customer environment. The discussion in this section includes:
1.1, “Services solution overview” on page 2
1.2, “ITCAM for WebSphere concepts” on page 2
1.3, “ITCAM for WebSphere solution” on page 9
1.4, “Document organization” on page 11

© Copyright IBM Corp. 2006. All rights reserved. 1

1.1 Services solution overview
This IBM Redbook provides a comprehensive guide to developing and deploying
a services solution offering based on ITCAM for WebSphere. The solution is
targeted for small and mid-market businesses (SMB). Because many of these
businesses do not have IT staffs, they rely on trusted advisors like you. Delivering
complete and working solutions from the start in a minimal amount of time can
help you establish long and prosperous relationships with these companies.

This services solution guide is developed specifically for Business Partners. It is
designed to help you reduce the time and investment that are necessary before
you can begin selling and implementing solutions.

Resellers face certain challenges in trying to exploit opportunities. Identifying and
assembling all of the relevant pieces that make up a meaningful solution
individually—hardware, software, networking installation, and configuration—can
be time-consuming and cumbersome tasks and might not be fully chargeable to
the customer. Solutions can be complex, and many demand high skill levels in
sales, service, and support.

The additional value-add for you consists of a set of offering-specific scenarios,
service offerings, documentation, and templates that enable you to provide a
high level of services and, therefore, increase the profitability of a solution sale. A
typical SMB relies on value-add resellers or consultants to provide a ready-to-go,
affordable, customized Web-based business solution to solve immediate
business problems.

Before we proceed into the offering itself, we spend some time defining ITCAM
for WebSphere.

1.2 ITCAM for WebSphere concepts
ITCAM for WebSphere is an application management tool that helps maintain the
availability and performance of on demand applications. It helps you quickly
pinpoint, in real time, the source of bottlenecks in application code, server
resources, and external system dependencies. This product also provides
detailed reports that you can use to enhance the performance of your
applications. ITCAM for WebSphere provides in-depth WebSphere-based
application performance analysis and tracing facilities.

ITCAM for WebSphere enables multiple levels of analysis in order to achieve a
complete view of the application, depending on the need. From the
production-level monitoring through detailed heap and method debugging, it digs

2 Solution Deployment Guide for IBM Tivoli Composite Application Manager for WebSphere

into SQL performance analysis without the need for database monitors. It can
provide SQL information and calls that were made through Java Database
Connectivity (JDBC™). ITCAM for WebSphere provides a composite status
correlation for transactions that use CICS® or IMS™ as the back-end system.

ITCAM for WebSphere V6.0 evolved from WebSphere Studio Application Monitor
and OMEGAMON® XE for WebSphere. ITCAM for WebSphere observes and
reports on the health of J2EE™-based applications. It tracks the progress of
applications as they traverse through J2EE application servers, middleware
adapters and transports, and database calls, and on to back-end systems such
as CICS or IMS to extract business data or to invoke mainframe business
processes. The tracking of applications produces request traces, where the
events in a request’s life are recorded and stored in a monitoring repository
database. ITCAM for WebSphere captures the CPU and the elapsed internal
times when events are called and when they are exited, measuring as far down
as the CPU times consumed and the elapsed internal times charged to individual
methods in J2EE classes. The methods or events taking the most time are
marked as an application’s parts that deserve attention for runtime improvement
studies and code optimizations.

ITCAM for WebSphere does not need modification of any application code. Java
Virtual Machine Tool Interface (JVMTI) interfaces and primitives, along with
WebSphere Performance Management Interface (PMI) and z/OS System
Measurement Facility (SMF) 120 records, are ITCAM for WebSphere’s principal
data sources. The monitoring data is collected and analyzed to offer a wealth of
information about the health of J2EE applications and their servers.

Many system-level performance metrics are collected and reported about J2EE
application servers. The status of the servers and their resources (particularly at
vital checkpoints such as CPU utilization), memory usage, and the status of
internal components such as database connection pools, JVM™ thread pools,
EJB™ usage, and request processing statistics can be very useful and important
for locating real-time problems with J2EE applications. ITCAM for WebSphere
brings attention to these critical indicators with real-time, graphical displays of
their values and their trends over time.

1.2.1 Components
ITCAM for WebSphere is a distributed performance monitoring application for
application servers. Its components are connected through TCP/IP
communication. The central component of ITCAM for WebSphere, the managing
server, is its heart and brain. It collects and displays various performance
information from application servers. The application servers run a component of
ITCAM for WebSphere called the data collector (DC), which is a collecting agent

Chapter 1. IBM Tivoli Composite Application Manager for WebSphere solution offering 3

that runs in the application server and sends monitoring information to the
management server. These data collectors operate independent of each other.

Figure 1-1 shows the overall architecture of ITCAM for WebSphere.

Browser interface
ITCAM
for WebSphere
Managing Server

I

Web Server Tivoli Enterprise
Management Server
and
Application servers with Tivoli Enterprise
ITCAM for WebSphere Portal Server
Data collectors

Figure 1-1 ITCAM for WebSphere architecture

ITCAM for WebSphere has the following components:
The managing server Acts as the central component that manages and
administers the data collectors. It stores that data in a relational database
repository. A Web-based application is provided to show the monitoring
results; this interface is also called the visualization engine. We discuss the
managing server in “The managing server” on page 5.
Data collectors run on the application servers that are being monitored. They
collect performance information for the managing server. These data
collectors operate independent of each other. They are discussed in
“WebSphere data collector” on page 6.
Tivoli Enterprise Monitoring Agent collects information that shows the status
of the WebSphere server and sends this information to the Tivoli Enterprise
Monitoring Server for display via the Tivoli Enterprise Portal. Tivoli Enterprise


Monitoring Agent is installed on the individual machines where the data
collector resides.

The managing server
ITCAM for WebSphere managing server (MS) controls and coordinates data
collectors for J2EE, CICS or IMS servers that run applications.

The managing server consists of the following software:
The X-Windows Virtual Frame Buffer (Xvfb) graphics package
Managing server database, DB2® UDB, or Oracle (on Sun™ Solaris™) for
storing data relationally
J2EE server to run the ITCAM for WebSphere graphical console application
An optional Apache Web server, such as IBM HTTP Server
ITCAM for WebSphere managing server overseer components, which are a
set of Java-based components

The ITCAM for WebSphere overseer components are the controlling logic for the
managing server:
The kernels control the managing server. There are always two copies of the
kernels running on an ITCAM for WebSphere managing server for
redundancy and failover. The kernels register components as they join the
managing server, periodically renew connections and registrations with
components and data collectors, and collect servers and component
availability information.
The publishing servers receive application and system event data from the
data collectors, gather and compute request-level information about
performance metrics such as response times, and implement the trap
monitoring and alerts features.
The archive agents receive monitoring data from the publishing servers, and
store the monitoring data in ITCAM for WebSphere’s repository.
The global publishing server collects information from the publishing servers,
and correlates all parts and pieces of multi-server requests, like requests from
J2EE servers to execute CICS or IMS programs.
The message dispatcher is a conduit for messages from ITCAM for
WebSphere using e-mail and SNMP facilities.
The polling agents collect data from Web Servers for Apache 2.0 and above.
The visualization engine is a Web-based GUI with access to graphics, ITCAM
for WebSphere performance reports, real-time views of different slices of
monitoring data, and access to ITCAM for WebSphere internal commands as


well as event-driven functions. The visualization engine runs on a J2EE
server, such as WebSphere Application Server.

Figure 1-2 shows the conceptual relationship between the components.

Snapshot traffic
Publish traffic
Global Publish
Server (SAM)

Publish Server (PS)
Kernel (KL) Visualization Engine
Message Dispatcher Provide services on: Provide services on:
(MD) - Lookup -Administration
- Registration -Availability
- Recovery -Problem Determination
Archive Agent (AA) - Configuration -Performance Management

Polling Agent (PA)

OCTIGATE
database

Figure 1-2 Kernel components

When it reaches the managing server, monitoring data is prepared for real-time
displays within the monitoring console and is inserted into the ITCAM for
WebSphere data repository. These are very resource-intensive operations;
moving them to a standalone distributed server (or servers) isolates them from
other enterprise activities, thus reducing ITCAM for WebSphere’s system
resource footprint in the monitored systems. This design also helps keep ITCAM
for WebSphere’s processing overhead at levels low enough for 24x7 production
system monitoring.

Data from the distributed data collectors is collected by the publishing server and
then stored in the OCTIGATE database by the archive agent. The Visualization
Engine reads the database in order to present data through the Web console,
while snapshot information such as lock analysis and in-flight transaction are
retrieved directly from the data collectors.

WebSphere data collector
Data collectors run inside the application servers. They use native system
services, and they are tailored for the particular environments where they
execute. The data collectors for z/OS systems are written to take advantage of
services on z/OS, such as MVS™ Cross-Memory Services and address space
fencing, which are not available on distributed systems.


Data collectors have two 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.

Collectively, these agents and other data collector routines unleash the probes,
package the monitoring data into Java formats for the managing server, and
deliver the data to the managing server.

The data collectors send the probes into the application servers to analyze the
applications’ performance. The probes collect monitoring data and feed it to
transport routines that in turn route the data to the managing server. The
managing server processes this data for appropriate display in the ITCAM for
WebSphere console and for storage in the OCTIGATE repository. This relieves
the processing burden of ITCAM for WebSphere from the application servers as
much as possible. The data collectors and probes are not designed to analyze or
interpret data, but to collect it and route it as quickly as possible to the managing
server where the analysis is performed.

The data sources employed by ITCAM for WebSphere are:
JVMTI garbage collection data, method trace, stack trace, CPU time, and
heap dump
JMX™ system resources
SMF system resources (z/OS only)
PMI system resources
OS services SCC, platform CPU, and its environment
Byte Code Modification (BCM) instrumentation of some classes

The data collector in a J2EE server runs as a custom service called am.
Figure 1-3 on page 8 shows the conceptual data collector structure.


WebSphere

JVMTI JMX PMI

Custom Service
bcm Publish data
am

KYN
Tivoli Enterprise
To TEMS
Monitoring Agent

Figure 1-3 J2EE data collector structure

Tivoli Enterprise Monitoring Agent
The Tivoli Enterprise Monitoring Agent enables WebSphere performance
information to be relayed to Tivoli Enterprise Monitoring Server and showed
using Tivoli Enterprise Portal. This facility replaces the data collector mechanism
employed by OMEGAMON for WebSphere Application Server. The Tivoli
Enterprise Monitoring Agent communicates to the data collector in the local
machine and retrieves performance information. Tivoli Enterprise Monitoring
Agent reports the information to Tivoli Enterprise Monitoring Server.

For more information about the Tivoli Enterprise Monitoring Server and IBM
Tivoli Monitoring V6.1 architecture, read Getting Started with IBM Tivoli
Monitoring V6.1, SG24-7143.

1.2.2 Supported platform overview
For a complete platform coverage list, refer to the following Web site:
http://publib.boulder.ibm.com/tividd/td/ITCAMWAS/prereq60/en_US/HTML/it
cam6.html

Table 1-1 on page 9 shows the supported platform overview for ITCAM for
WebSphere V6.


Table 1-1 ITCAM for WebSphere supported platform overview
Component Software

Managing server operating AIX® 5.2, 5.3
system Solaris 9 cluster, 10 cluster
HP-UX 11iv1
RHEL 3.0, RHEL 4.0, SLES 8, SLES 9
Windows® 2000 Server or Advanced Server with SP4
Windows 2003 Server SE/EE

Managing server database DB2 7.2 EE/EEE FP11
DB2 8.1 ESE FP6
DB2 8.2 ESE
Oracle 9i S/E R2 9.2+
Oracle 10g

Managing server WebSphere Application Server 5.1.1 and above or
WebSphere WebSphere Application Server 6.x

Data collector platform Windows 2000 Pro SP4
Windows 2000 Server or Advanced Server with SP4
Windows 2003 Server SE/EE
AIX 5.2 and 5.3
RHEL 3.0 and 4.0
SLES 8 and 9
Solaris 8, 9, 10, Solaris 9 Cluster
HP-UX 11iv1
RFAS 4.0 and 4.1
OS/400® V5R2 and V5R3
z/OS 1.4, 1.5, 1.6, or 1.7

CICS CTG 5.0.1 or 5.1 and 1.3, 2.2, 2.3 or 3.1

IMS 7.1, 8.1 and 9.1

1.3 ITCAM for WebSphere solution
This section discusses the solutions that we present in this book. The discussion
is divided into:
1.3.1, “Solution overview” on page 10
1.3.2, “Software components” on page 10
1.3.3, “Suggested hardware configuration” on page 10


1.3.1 Solution overview
The solution provides a proactive monitoring on WebSphere Application Server
J2EE environment. The solution can be a turnkey solution or a diagnostic service
for the end user.
The turnkey solution has you, the Business Partner, install and configure
ITCAM for WebSphere on the customer hardware and leave it for the
customer to operate later. This solution is typical for an enterprise that has its
own IT personnel and want to manage their own environment.
The diagnostic service solution has you bring your hardware to analyze
customer environment and provide tuning recommendations for the customer.
This solution is typical for an enterprise that wants an occasional diagnostic
solution for its WebSphere environment but does not want to maintain the
management environment.

Both solution types include installation of ITCAM for WebSphere data collector
on the customer’s production servers. The data collector will feed the managing
server with necessary transaction information.

1.3.2 Software components
The solution consists of implementing ITCAM for WebSphere managing server
and data collector to analyze WebSphere Application Server. The distributed
platform product number for ITCAM for WebSphere is 5724-L62.

Passport advantage media pack part number for ITCAM for WebSphere V6.0
Multi Platform is BJ0G3ML, or use the Web download option.

1.3.3 Suggested hardware configuration
The following list is a suggested hardware configuration for use with ITCAM for
WebSphere managing server:
Intel® Pentium® or equivalent processor (733 MHz or higher)
3 GB RAM
20 GB available disk space

The recommended configuration for a production ITCAM for WebSphere
managing server could vary depending on your customer’s requirements.


1.4 Document organization
Farther into this book, you can find various information to help you build your
service offering regarding ITCAM for WebSphere solution. This book has the
following chapters:
Chapter 1, “IBM Tivoli Composite Application Manager for WebSphere
solution offering” on page 1
Chapter 2, “Planning for customer engagement” on page 13
Chapter 3, “Demonstration of ITCAM for WebSphere” on page 37
Chapter 4, “Implementation of ITCAM for WebSphere service” on page 47
Chapter 5, “Complementary solutions for ITCAM for WebSphere
engagement” on page 105


2

Chapter 2. Planning for customer
engagement
In this chapter, we discuss services engagement for ITCAM for WebSphere and
in general. The topics that we discuss includes:
2.1, “Services engagement preparation” on page 14
2.2, “Solution scope and components” on page 15
2.3, “Services engagement overview” on page 16
2.4, “Defining solution timing” on page 21
2.5, “Statement of work” on page 29

© Copyright IBM Corp. 2006. All rights reserved. 13

2.1 Services engagement preparation
This section describes resources that are available to help you successfully
deliver a solution. The discussion is divided into:
2.1.1, “Implementation skills” on page 14
2.1.2, “Available resources” on page 14

2.1.1 Implementation skills
To be able to successfully develop and deploy an ITCAM for WebSphere-based
solution, you must acquire some specialized skills. The following skills are
needed to implement and customize the solution:
General skills
– Operating system administration skills on Windows 2000 and
Linux®-based systems
– Connectivity and network administration skills on TCP/IP protocol
– Understanding of Java and J2EE-based applications
WebSphere Application Server skills
– Using WebSphere Application Server administration console
– Defining application resources in WebSphere Application Server
ITCAM for WebSphere skills
– Understanding of ITCAM for WebSphere components
– The ability to perform problem determination related to ITCAM for
WebSphere connectivity

Depending on the target environment, you might need additional skill sets to
understand the whole application environment, such as messaging platform,
database management, back-end processing server, and so on. You might be
able to acquire these skills from the resources listed in the next section.

2.1.2 Available resources
The prerequisite skills listed in the previous section are needed to customize or
develop the solution. For each of these skills, there is a variety of resources
available to help acquire the necessary skill level. Available educational
resources are as follows:
Online Help: IBM WebSphere Application Server and ITCAM for WebSphere
provide online help and product manuals on the Web.


Classroom Training: IBM PartnerWorld® provides current information about
available classes, their dates, locations, and registration. Additionally, check
the PartnerEducation Web site, which serves as a single point of contact for
all Business Partner education and training.
IBM Technical Education Services (ITES): ITES offers a variety of classes at
all knowledge levels to help you achieve any of the offering’s prerequisite skills.
IBM Redbooks: You can access various practical and architectural information
regarding IBM hardware and software platforms from these books. They are
available for download in the PDF format at http://ibm.com/redbooks.

2.2 Solution scope and components
You need to define the scope of the solution. The solution can be one of the two
basic offering types in 2.2.1, “Basic solution definition” on page 15 or you can
add additional components listed in 2.2.2, “Cross-sell and up-sell opportunities”
on page 16.

2.2.1 Basic solution definition
The solution enables an enterprise to manage and analyze effective performance
of a J2EE-based application to show a bottleneck and impending problems. The
solution also enables an enterprise to analyze and improve the performance of
its application.

There are several forms of the solution that can be presented to the customer:
Environment analysis solution: This enables you to perform analysis of an
enterprise application using a portable ITCAM for WebSphere managing
server. Typically you would leave the managing server running for a few days
and generate reports. You analyze the report and provide your
recommendations. Some adjustment of the monitoring level may have to be
performed during that time to collect additional information.
WebSphere application management solution: This solution implements the
full function of ITCAM for WebSphere in the customer environment and
enables customers to use and manage their own environment.

Chapter 2. Planning for customer engagement 15

2.2.2 Cross-sell and up-sell opportunities
Additional solutions can be performed to include:
Integration to IBM Tivoli Monitoring V6.1
Response time management with IBM Tivoli Composite Application Manager
for Response Time Tracking
End-to-end response time management with IBM Tivoli Composite
Application Manager for CICS Transactions or IBM Tivoli Composite
Application Manager for IMS Transactions
Enhancement to integrate with IBM Tivoli Enterprise™ Console or IBM Tivoli
Business Systems Manager
Collection of WebSphere performance information into IBM Tivoli Data
Warehouse

Note: Chapter 5, “Complementary solutions for ITCAM for WebSphere
engagement” on page 105 offers details about additional services opportunities.

2.3 Services engagement overview
You routinely rely on your skills and previous experience as a guide, but there are
always issues that require some educated guesswork. The goal of this section is
to help you minimize the guesswork involved in planning and implementing a
solution by providing a framework and time estimates for the major tasks.

A typical services engagement consists of:
Build an executive assessment (see 2.3.1, “Executive Assessment” on
page 17)
Set up a demonstration system or proof of technology (see 2.3.2,
“Demonstration system setup” on page 18)
Analyze solution tasks (2.3.3, “Analyze solution tasks” on page 19)
Create a contract or statement of work (see 2.3.4, “Creating a contract” on
page 20)

The representative tasks and the time involved for custom solution execution are
included in the following section. Each customer has a unique set of needs, so the
actual set of tasks to accomplish and the time involved might vary. However, this
list should help you understand implementation details, size the solution more
accurately for the customer, and ensure a profitable engagement for yourself.


It is important to work with your customers to understand their expectations. After
you have gathered this data, document the tasks, deliverables, and associated
costs in a statement of work. The statement of work acts as your contractual
agreement with the customer for the duration of the project; therefore, a detailed
and well-defined statement of work is advantageous both to you and your
customer.

A good overall understanding of the solution scope is a crucial prerequisite to
successfully selling, developing, and implementing it. As a solution provider, you
must understand what is involved in developing such a solution before you can
discuss it with your customer and size it for a cost estimate.

2.3.1 Executive Assessment
The Executive Assessment is a billable service that you can offer to your
prospective clients. It offers a process designed to help you evaluate the
business needs of a company that is planning to deploy a solution for Web-based
business. It was created for IBM Business Partners to help you close a higher
ratio of opportunities. It has been field-tested in markets all over North America
and Europe and has received enthusiastic feedback.

The benefits of using the Executive Assessment in your sales process include:
Earning additional service fees
More effectively qualifying prospective clients
Shortening the sales cycle
Streamlining the development process
Closing a much higher ratio of potential engagements

This toolset helps you ask the right people the right questions so that you get the
information you need to propose the appropriate solution. This assessment then
helps you create a compelling business case that will persuade your prospect to
buy the required hardware, software, and services from you in the shortest
possible time.

The complete Executive Assessment process should take approximately 10 to 16
hours. Table 2-1 shows the task breakdown.

Table 2-1 Solution task
Task Estimated time
(hours)

Initial fact-finding meeting, asking questions, and gathering 3
data

Review and analysis of competing solutions 2


Task Estimated time
(hours)

Preparation of a set of strategic recommendations 1

Creation of a demonstration prototype 3-9

Presentation of findings and close for a contract 1

Total 10-16

This is a business-case assessment, not a technical assessment, so your
audience should be business owners, line-of-business executives, marketing and
sales managers, and finally, the IT manager. The business owner or
line-of-business executive is likely to be the decision maker.

For their initial investment, your clients get:
A business assessment prepared by a professional (you)
A competitive analysis
A prototype solution for their review
A strategic and tactical proposal for justifying and implementing their solution
for Web-based business

Over the course of the Executive Assessment, you determine who will be
involved in the project, what they want to accomplish, when they plan to deploy,
where the Web plays a mission-critical role in their business, and how the project
will be funded. Armed with this information, a competitive analysis, and a
prototype solution, you will be able to justify their investment, build perceived
value, present your recommendations in a way that is almost irresistible, and
successfully close the contract.

Having the ability to recommend the correct course of action to your client has
tremendous value. In a market where it is difficult for companies to find qualified
Business Intelligence consultants, the Executive Assessment and resulting
presentation gives you a chance to prove conclusively that you have the right
technology and the right people to do the job.

2.3.2 Demonstration system setup
A demonstration system is typically set up in advance to show your customers
the attributes of the solution. The demonstration system can typically be set up
with a limited number of systems that are separate from the system that will be
used by the production system.


You can set up ITCAM for WebSphere demonstration system using a
two-machine environment: one running the managing server and the other
running the application client with the data collector. This demonstration system
is typically running a test application that you can load onto it so that you can use
ITCAM for WebSphere to show monitoring processes and collect results.

The demonstration system enables your customers to evaluate whether the
solution suits their particular needs. Table 2-2 shows the tasks and estimated
time for demonstrating the solution. Chapter 3, “Demonstration of ITCAM for
WebSphere” on page 37 suggests some demonstration ideas.

Table 2-2 Solution demonstration task
Task Estimated time (hours)

Set up hardware 1-2

Install and configure operating system 2-3

Install sample application 2-4

Install ITCAM for WebSphere 3-4

Install data collector 1

Run application load 1

Demonstrate to customer 2

Run reports 1

Total 13 - 18

2.3.3 Analyze solution tasks
After the customer agrees to use the solution in their environment, you must
decide how to implement it. These estimates would then be collected and
implemented into a contract or statement of work.

We discuss these tasks in detail in 2.4, “Defining solution timing” on page 21.
These are our suggested tasks and order; you may complete the tasks in a
different order or may omit or add tasks depending on the environment to which
you implement the solution. Overall solution time might be influenced by the
amount of skill and experience that you or your team have with the solution. The
estimate that we present is typically based on the following factors:
Has working knowledge of the operating system
Has good understanding of WebSphere Application Server and J2EE-based
environment


Understands J2EE application environment, with its components, such as
Enterprise JavaBeans™ (EJB), Servlets, Java 2 Connector (J2C), Java
Database Connectivity (JDBC), and Web Services.
Understands WebSphere security concepts, such as Secure Socket Layer
(SSL), LDAP authentication, and certificate usage
Has thorough knowledge of ITCAM for WebSphere

Depending on your skills and experience, the estimates we present might be too
high or too low. Table 2-3 illustrates one method of approximating more realistic
time estimates for your efforts, based on whether you or your team are new to
each skill area or could be considered experts. A novice is someone who has
completed training in the skill area but has no hands-on experience. An expert
has completed training in the skill area and has implemented ITCAM for
WebSphere projects.

Table 2-3 Skill adjustment
Skill Novice Expert
increase by reduce by

Experience with the operating system 25% 10%

Deep understanding of WebSphere 40% 20%
Application Server or J2EE environment

Experience in ITCAM for WebSphere 10% 20%
installation

Familiarity of ITCAM for WebSphere reports 25% 20%

For the detailed task breakdown, see 2.4, “Defining solution timing” on page 21.

2.3.4 Creating a contract
A contract or statement of work is a binding contractual agreement between you
and your customer that defines the service engagement that you must perform
and the result that the customer can expect from the engagement. The contract
should leave nothing in doubt.

A statement of work should include:
Executive summary of the solution, which is typically a short (less than a
page) summary of the solution and its benefit. You must specify any major
restrictions of the implementation, such as:
– The solution is only implemented for finance application servers.
– The solution will be implemented in phases.


Solution description, which contains the major components and solution
building blocks that will be implemented. It should cover conceptual
architecture of the solution and solution scope in general. This description is
aimed for technical personnel to understand the implementation scope.
Assumptions, which lists all of the assumptions that are used to prepare the
contract and provide task estimation. Any deviation to the assumptions that is
used will definitely affect the scope of engagement and must be managed
using the change management procedure. Typical changes include cost
changes or scope changes.
Business partner responsibilities, which lists all of the responsibilities or major
tasks that will be performed by you or your team to implement the solution.
Customer responsibilities, which lists all of the responsibilities or items that
the customer must provide for you or your team to perform the engagement. If
you cannot obtain any item in the customer responsibilities, then a change
management procedure may be invoked.
Staffing estimates, which lists the estimated personnel needed to implement
the solution.
Project schedule and milestones, which shows the major steps, schedule,
and achievement calendar that can be used to check the project progress.
Testing methodology, which lists the test cases to ensure that the project
implementation is successful.
Deliverables, which provides tangible items that the customer will get at the
end of the service engagement, including:
– Machine installation
– Documentation
– Training
Completion criteria, which lists the items that, when provided to the customer,
indicate that the engagement is successfully completed. For most services
engagements, this is probably the most delicate to define. Completion criteria
can be so general that you will be tied up providing the customer ongoing
support for life. On the other hand, an inadequate completion criteria is often
rejected by the customer fearing that you might back away from the
engagement in an incomplete state.

See 2.5, “Statement of work” on page 29 for a sample statement of work.

2.4 Defining solution timing
A profitable services engagement has to correctly identify the tasks that you must
perform and to adequately allocate the necessary time to perform them. This


section guides you on the tasks that you might need to perform for an ITCAM for
WebSphere solution implementation and the timing estimate. The estimate relies
largely on some basic assumptions:
Managed environment size: the number of data collectors that must be
implemented correspond directly with the load of the managing server and
the time needed for:
– Installing the data collectors
– Designing monitoring server group and assigning operators
– Analyzing performance information
Application complexity: the number of servlets, EJB resources, and
inter-server communication must be considered as they relate to the time
needed for:
– Analyzing performance information
– Determining performance bottlenecks
– Providing performance recommendations
Transaction rate of the application server would affect processing overhead
on the managing server and have an impact on the collected performance
data size. A higher transaction rate requires a smaller sample percentage, but
this might prevent some of important transaction data from being collected, so
you should lengthen the analysis of performance information.

Table 2-4 lists our sizing assumptions.

Table 2-4 Sizing assumptions
Assumption Simple Moderate Complex

Number of data collectors <5 5 - 10 10 - 20

Number of J2EE resources < 50 50 - 100 100 - 200

Inter-server communication N/A one to one interconnected

Transaction rate per data collector < 60/min 60 - 300/min 300 - 900/min

Important: You must be aware of any specific application problems or offending
transactions that the customer is experiencing. It is common for the customer to
assume that you can resolve this problem. Any such specific analysis must be
listed in the assumption and factored properly for the time estimation. Our
estimate does not cover analyzing existing or specific problems.


2.4.1 Environment analysis tasks
This section discusses the tasks for environment analysis engagement. Table 2-5
shows the timing estimate for the major components of the tasks for the
environment analysis solution.

Table 2-5 Environment analysis tasks

Simple Moderate Complex

Plan the solution 5-8 6-9 9-12

Implement the solution 14-21 21-30 31-43

Close the engagement 2 2-3 3-5

Total 21-31 29-42 43-60

Plan the solution
Planning the deployment of the ITCAM for WebSphere solution includes the
subtasks shown in Table 2-6.

Table 2-6 Estimated plan for the solution time


Gather detailed requirements 2-3 2-3 3-4

Design the solution 2-3 2-3 3-4

Perform gap analysis 1-2 2-3 3-4

Total 5-8 6-9 9-12

Gather requirements
At the beginning of your engagement, you should meet with your customers
to understand their proposed objectives and gather their requirements. First,
you have to determine the functional requirements, which define the business
functions that the Business Intelligence system is going to provide. You
determine your requirements by developing a good understanding of the
business needs and of what you hope to achieve. For example, look at issues
such as business goals, purpose, and usage questions, such as who the
users are and how they expect to interact. It is important to gather these
requirements early and discover any challenges that might lay ahead while


they can still be dealt with easily. When you have determined the functional
requirements, you can clarify the technical or system requirements.
The technical requirement involves spending time at the customer site to
determine and understand the available data sources. These data sources
might come in different formats, such as relational databases, spreadsheets,
text files, or even hard copies only. You need to be able to identify the fields or
data elements in these data sources and plan how these data elements will
be used in the target data mart. You also need to identify the schema or data
usage changes from the supplied sample scenario, which is based on the
non-customized products.
The system requirement will be determined from the number and size of the
data sources and the expected goals that the business questions will cover.
This information dictates the size and performance of the systems that will be
used in the solution.
Design the solution
Topics that should be addressed include scalability, functionality, and
performance of this solution.
Design involves understanding the customer’s environment including
hardware, software, data volumes, special requirements, and operational
procedures. It is necessary to identify and plan for any additional tuning of
software that might be required because of the customer’s environment or
special needs. In addition, an analysis of the modifications made to the
scenarios and reports must be performed. After you have designed the
proposed solution and reviewed it with your customer, you are ready to begin
development of the offering.
Perform gap analysis
This task involves performing a gap analysis to give the customer an estimate
of the development effort that is required to set up the solution. At its core, the
analysis seeks to determine what customizable components should be
extended, modified, or created. The number and complexity of customizable
components drives the size of the project and the required resources.

After you have designed the proposed solution and reviewed it with your
customer, you are ready to proceed.

Implement the solution
Table 2-7 on page 25 lists the tasks that are performed in the implementation of
the solution. Chapter 4, “Implementation of ITCAM for WebSphere service” on
page 47 offers a detailed implementation guide for the environment analysis
solution.


Table 2-7 Implementation tasks


Install managing server on site 1-2 1-2 1-2

Install data collector 2-3 3-4 4-6

Run initial data collection 1-2 2-4 4-7

Run detailed data collection 2-3 3-4 4-5

Collect performance reports 2-3 4-6 8-10

Develop finding report 4-5 5-6 6-7

Removal of data collector 2-3 3-4 4-6

Total 14-21 21-30 31-43

Detailed sub-tasks for the solution follow:
Installing managing server on site
Installing data collector
Run initial data collection
Run detailed data collection
Collect performance reports
Develop finding report
Removal of data collector

Close the engagement
Because this service engagement does not provide ITCAM for WebSphere for
the customer to operate, you do not have to provide training, so our next step is
to close the engagement. Table 2-8 lists the engagement close tasks.

Table 2-8 Engagement close tasks


Presentation of performance findings 1 1-2 2-4

Closing of services engagement 1 1 1

Total 2 2-3 3-5

Presentation of performance findings and recommendations
Closing of service engagement


2.4.2 WebSphere application management tasks
This section discusses the tasks for WebSphere application management
engagement. Table 2-9 shows the timing estimate for the major components of
the tasks for the WebSphere application management solution.

Table 2-9 WebSphere application management tasks
Task Simple Moderate Complex

Plan the solution 5-8 6-9 9-12

Implement the solution 15-23 22-34 34-50

Provide training 8-14 8-20 12-24

Close the engagement 2 2-3 3-5

Total 30-47 38-66 58-91

Plan the solution
Planning of the deployment of the ITCAM for WebSphere solution includes the
subtasks shown in Table 2-10.

Table 2-10 Estimated task time


Gather detailed requirements 2-3 2-3 3-4

Design the solution 2-3 2-3 3-4

Perform gap analysis 1-2 2-3 3-4

Total 5-8 6-9 9-12

Gather requirements
At the beginning of your engagement, you should meet with your customers
to understand their proposed objectives and gather their requirements. First,
you have to determine the functional requirements. Functional requirements
define the business functions that the Business Intelligence system will
provide. You determine your requirements by developing a good
understanding of the business needs and of what you hope to achieve. For
example, look at issues such as business goals, purpose, and usage
questions, such as who the users are and how they expect to interact. It is
important to gather these requirements early to discover any challenges that
might lie ahead while they can still be dealt with easily. When you have


determined the functional requirements, you can clarify the technical or
system requirements.
The technical requirement involves spending time at the customer site to
determine and understand the available data sources. These data sources
may come in different formats, such as relational databases, spreadsheets,
text files, or even hard copy only. You need to be able to identify the fields or
data elements in these data sources and plan how these data elements will
be used in the target data mart. You also need to identify the schema or data
usage changes from the supplied sample scenario, which is based on the
non-customized products.
The system requirement will be determined from the number and size of the
data sources and the expected goals that the business questions will cover.
This information dictates the size and performance of the systems that will be
used in the solution.
Design the solution
Topics that should be addressed include scalability, functionality, and
performance of this solution.
Design involves understanding the customer’s environment including
hardware, software, data volumes, special requirements, and operational
procedures. It is necessary to identify and plan for any additional tuning of
software that might be required because of the customer’s environment or
special needs. In addition, an analysis of the modifications to be made to the
scenarios and reports has be performed. After you have designed the
proposed solution and reviewed it with your customer, you can begin
development of the offering.
Perform gap analysis
This task involves performing a gap analysis to give the customer an estimate
of the development effort that is required to set up the solution. At its core, the
analysis seeks to determine what customizable components need to be
extended, modified, or created. The number and complexity of customizable
components drive the size of the project and the required resources.

After you have designed the proposed solution and reviewed it with your
customer, you are ready to proceed.

Implement the solution
The implementation of the solution is performed using the tasks described in
Table 2-7 on page 25. Chapter 4, “Implementation of ITCAM for WebSphere
service” on page 47 offers detailed implementation tasks for the WebSphere
application management solution.


Table 2-11 Implementation tasks


Install managing server 1-2 1-2 1-2

Install data collector 2-3 3-4 4-6

Customize management environment 1-2 2-4 4-7

Establish operation procedure 2-3 2-4 3-6

Run initial data collection 1-2 2-4 4-7

Run detailed data collection 2-3 4-6 8-10

Collect performance reports 2-3 3-4 4-5

Develop performance observation 4-5 5-6 6-7

Total 15-23 22-34 34-50

Detailed subtasks for the solution follow:
Install managing server
Install data collector
Customize management environment
Establish operation procedure
Run initial data collection
Run detailed data collection
Collect performance reports
Develop performance observation report

Provide training
Part of your implementation responsibilities can include training selected
customer staff to troubleshoot basic problems and perform other operational
tasks. This could involve some of the following topics:
Solution technical design
Problem Determination process
Look at application logs
Check software status
Back up/restore important files and databases
Develop a troubleshooting checklist
Establish a Frequently Asked Questions list
Administer the application
Generate performance reports


Technical training with your customer could take 16 hours or more, depending on
the technical depth of the discussions.

Provide training
Table 2-12 lists the training tasks.

Table 2-12 Training tasks


Administrator training 4-8 4-12 8-16

Operator training 4-6 4-8 4-8

Total 8-14 8-20 12-24

Close the engagement
Table 2-13 lists the engagement closing tasks.

Table 2-13 Close the engagement task


Presentation of performance findings 1 1-2 2-4

Closing of services engagement 1 1 1

Total 2 2-3 3-5

Removal of data collectors
Presentation of performance findings and recommendations
Closing of service engagement

2.5 Statement of work
This section provides some sample ideas for items that you can include in your
statement of work contract. We divide this section for each solution.

2.5.1 Environment analysis service
The environment analysis service statement of work can consist of the sections
listed here.


Executive summary
The environment analysis service provides a high-level assessment of
<customer> application environment. <You> provide an initial assessment of
<customer> application on the area of <application name>, which consists of the
following application servers: <lists>.

The monitoring of these application servers will be conducted over the period of
<date> for two weeks. At the end of the assessment period, <you> will present
the assessment finding, including:
Application server performance summary
Application highlight, such as load profile, and transaction rate
Performance highlights such as: potential bottleneck, excessive errors,
deadlock
Environment tuning recommendations

Solution description
In the environment analysis service, <you> will provide a managing server
hardware that runs ITCAM for WebSphere managing server. ITCAM for
WebSphere data collectors will be installed on <customer>’s production servers
for assessment. The data collector will mainly run in level 1 monitoring, which will
have 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 managing server connection to the data collectors
would not go through a firewall.

During the assessment period, transaction performance information and
application server performance information will be collected and stored in the
ITCAM for WebSphere managing server database.

<You> will analyze the collected performance information and possibly perform
monitoring with additional detail as needed. The analysis is performed
dynamically and will not need a restart of the application servers.

At the end of the assessment period, <you> will remove the data collectors from
<customer> application servers and present the performance finding.


Assumptions
These are possible assumptions that can be used in the environment analysis
service:
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 problem that the customer has.

Business partner responsibilities
In addition to the solution implementation tasks described in Chapter 4,
“Implementation of ITCAM for WebSphere service” on page 47, you also might
be responsible for tasks such as project management, purchasing software and
hardware, general consulting, and negotiating financing options with the
customer.

Customer responsibilities
This section describes the responsibilities the customer has to the Business
Partner; for example:
Designating a representative who will be the focal point for all communication
with the Business Partner relative to this project and who will have the
authority to act on the customer’s behalf in matters regarding this project
Designating operations personnel to work with the Business Partner as
appropriate
Providing all required Web site content in digital form, as specified by the
Business Partner
Providing all product data in a format as requested
Providing all data and information required for implementation
Providing suitable workspace with telephone access for the services
specialists while working on customer premises
Providing user IDs, passwords, and IP addresses as required, enabling the
Business Partner to perform the service
Providing information to allow estimates on current and future system
workload and performance expectations


Staffing estimates
The project will be performed using one ITCAM for WebSphere specialist who
will be on site as required by the project schedule. The project is estimated to be
performed within three weeks.

Project schedule and milestones
Because this is a short project, we would not really need a milestone. Figure 2-1
on page 32 shows a sample project schedule.

Jun 18 2006 Jun 25 2006 Jul 2 2006
ID Task Name Start Finish Duration
19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5

1 Plan the solution 6/19/2006 6/21/2006 3d

2 Implement the solution 6/22/2006 7/3/2006 8d

3 Close the engagement 7/4/2006 7/5/2006 2d

Figure 2-1 Project schedule

Testing methodology
The testing of the solution is demonstrated using the reports generated by
ITCAM for WebSphere in PDF format. <You> will generate the following reports
during the assessment period:
Top CPU user reports (daily)
Top transaction usage (daily)
Top response time report (daily)
Transaction hourly profile on a day for top five transactions (weekly)
Memory analysis report on the application server (once)

Deliverables
The deliverable of this project can be in the following form:
ITCAM for WebSphere reports that are used for testing the solution
Performance assessment and recommendation presentation by you

Completion criteria
The completion criteria should be listed here. You have to engage with the
customer to get a proper signoff of the project with an appropriate completion
criteria. Some ideas for the completion criteria are:
Acceptance of the performance finding and recommendations.
Data collectors and managing server have been removed from the customer
environment.


Specific performance problems or offending transaction resolutions may be
included explicitly in the completion criteria. You have to be aware of these
additional specific completion criteria for your customer.

2.5.2 WebSphere application management service
The WebSphere application management service statement of work can
consists of the sections listed here.

Executive summary
The WebSphere application management service implements ITCAM for
WebSphere in <customer> environment. ITCAM for WebSphere enables
proactive monitoring of WebSphere Application Server and transaction
performance. The implementation covers the application servers in <lists>.

The initial monitoring of these application servers will be conducted over the
period of <date range> for two weeks. At the end of the assessment period,
<you> will present the assessment finding, including:
Application server performance summary
Application highlight, such as load profile, and transaction rate
Performance highlights such as: potential bottleneck, excessive errors,
deadlock
Environment tuning recommendations

<You> will also train <customer> for using ITCAM for WebSphere to manage
your own environment.

Solution description
In the WebSphere application management service, <you> will install ITCAM for
WebSphere managing server on your hardware platform. ITCAM for WebSphere
data collectors will be installed on <customer>’s production servers for
assessment. The data collector will mainly run in level 1 monitoring, which will
have 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 managing server would not have to connect to the
data collector through a firewall.

During the assessment period, transaction performance information and
application server performance information will be collected and stored in the
ITCAM for WebSphere managing server database.


<You> will analyze the collected performance information and possibly perform
monitoring with additional detail as needed. The analysis is performed
dynamically and will not require a restart of the application servers.

<You> will provide training for <customer> personnel to use and maintain the
ITCAM for WebSphere solution that has been implemented.

Assumptions
Possible assumptions that can be used in the environment analysis service
include:
Number of data collectors to be configured
Transaction rate of each application server
Transaction mix of each application server

Note: Insert any additional assumption about specific performance or
transaction problem that the customer has.

Business Partner responsibilities
Business Partner responsibilities are described in Chapter 4, “Implementation of
ITCAM for WebSphere service” on page 47. In addition to the solution
development tasks described in this chapter, you also might be responsible for
tasks such as project management, purchasing software and hardware, general
consulting, and negotiating financing options with the customer.

Customer responsibilities
This section describes the responsibilities the customer has to the Business
Partner, such as:
Designating a representative who will be the focal point for all communication
with the Business Partner relative to this project and who will have the
authority to act on the customer’s behalf in matters regarding this project
Designating operations personnel to work with the Business Partner as
appropriate
Providing all required Web site content in digital form, as specified by the
Business Partner
Providing all product data in a format as requested
Providing all data and information required for implementation
Providing suitable workspace with telephone access for the services
specialists while working on customer premises
Providing user IDs, passwords, and IP addresses as required, enabling the
Business Partner to perform the service


Solution deployment guide for ibm tivoli composite application manager for web sphere sg247293

Solution deployment guide for ibm tivoli composite application manager for web sphere sg247293

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (16)

Destaque

Destaque (7)

Semelhante a Solution deployment guide for ibm tivoli composite application manager for web sphere sg247293

Semelhante a Solution deployment guide for ibm tivoli composite application manager for web sphere sg247293 (20)

Mais de Banking at Ho Chi Minh city

Mais de Banking at Ho Chi Minh city (20)

Último

Último (20)

Solution deployment guide for ibm tivoli composite application manager for web sphere sg247293