WILY, Managing Critical Applications With Wily Introscope, Robert Dring

Wily | CA
Application Performance Monitoring (APM)

Managing Critical Applications (JEE & .NET) with Wily Introscope
The Key to Application Performance Management and Customer Success
Robert Dring Senior Consultant Northern EMEA Webmedia User Conference, Tallin, Estonia. 7th December 2006 eMail : robert.dring@ca.com Tel : +44-7917-046945
Agenda
Why Application Performance Monitoring/Management ? Introscope & Application Performance Management Architecture / How / What Introscopes Blame Technology An Introduction To .NET Monitoring Customer Experience Manager (CEM) Summary / Q & A
Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.
tere tulemast Tallinna!
Why Application Performance Monitoring/Management ?
Todays IT Challenges
Web-Tier Application-Tier Database-Tier Mainframe-Tier
Shift to web based apps Quick time to market, increased importance and reliance Increased complexity N-tier environments, access from anywhere anytime Seas of data Overwhelmed by various alarms and health information Customer satisfaction, IT reports all is well, yet users are complaining how do you know Wasting resources Constant mis-diagnosis, false positives, finger-pointing, rework Do more with less Pressure to reduce operating costs and improve quality of service PROBLEM Inconsistent performance of business applications PROBLEM Lack of understanding of the business impact of an incident PROBLEM The time & resources to identify, isolate, and solve customer incidents
When Theres a Problem, IT Needs to Know Where the Transaction is Failing

Is authentication server slow? Are customers affected?
Network Firewall Load Balancer Identity Manager SAP
Are business apps slow?

PSFT
Can I find the problem? Did we record everything?

Portal
Whats
Siebel mainframe
Mainframe
response time?
Router End User
Switch Web Servers Applications
Web services down?
Database
Are transactions failing?
What about the web servers?
Web Services
Databases
Are 3rd parties meeting SLAs?
How is database 3rd Party response? Applications
Where are Transactions Processed?

End-to-End, Always-On Transaction Visibility
Drill Down: End User Experience Drill Down: Application and App Server Availability and Performance Drill Down: Back-End Availability and Performance
PSFT Siebel Network Load Balancer
SAP
Firewall
Portal
Mainframe
Router
Database
Web Services
Most web applications are made up on three tiers: Most web-based Front end client applications do NOT process much of the transaction, only presentation. When Middleware monitoring the (databases, client and the clients network it is Back ends transaction systems, and critical to focus on problems to you CAN control legacy systems) -- your own systems andinclude network. SOA architectures which Enterprise Services Bus (ESB) and Web Service layers, complicate the picture.
Identity Manager
Databases
3rd Party Applications
Traditional Management Approach:

Monitor the Infrastructure Necessary but not sufficient
Identity Manager
SAP
PSFT
Siebel Network Load Balancer
Firewall
Portal
Mainframe
Router End User
Database
Web Services
Databases
Introscope & Application Performance Management
Types of Performance Problems

Database
To solve this
Too Many EJB Calls?
HTTP Server
App Server Web Configuration?
Application Server
Is it JDBC?
More Traffic Than Expected?
Which One is the Cause?
Transactions Too Slow?
Transaction Server
Application Not Scaling?
CPU Overloaded?
Security Server Bottleneck?

Security Authorization Server
requires a multidimensional approach

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved. 10
Why Application Performance Monitoring?

Customer complaining!
Web Servers
Wheres the Problem? Application code? Hardware? Web App Server? Database Servers? Mainframes? Security Systems? Internet traffic? MQSeries
App Server
Database Servers CICS Backend Systems Security Servers

Wilys Business is Web Application Management (not just Java App Management)
Our goal is to manage all business-critical transaction-oriented
web applications for our customers

Focused on Java initially because of its adoption Now extending to Microsoft .NET because of its rising popularity
amongst our existing customers & future prospects
Managing heterogeneous application environment will be our specialty

Introscope product line

Enterprise Application Management solution for mission critical
production applications used by Global 3500 companies

Monitors Java apps from
inside the JVM inside the Managed CLR outside
Monitors Microsoft .NET apps from
environment
Also monitors non-Java/.NET systems from the
V1.0 shipped in 1999 Currently shipping version V7.0 (GA in May 2006) 600+ worldwide customers
Wilys Customer Success Management Solution is supported by Introscope & CEM

Customers Transactions Customer Experience Management Application Platforms and Middleware Databases Business Processes Applications Application Performance Management
Authentication
Network, Systems and Servers
Real time monitoring from end-to-end for ALL transactions Correlate actual user experience with application performance Predict problems before customers are impacted Quickly triage problems to improve availability & performance Monitor and document SLA performance Collaborate across IT and the Business to insure customer success
Customer Benefits
End-to-end transaction visibility into all transactions,
across the web infrastructure (Java or .NET)

Proactive notification before SLAs are compromised Automatic discovery, monitoring, and triage for the
application environment
Deep visibility into each transaction across processes Capture 100% of performance data for SLA
management, trend analysis, capacity planning

Manage heterogeneous .NET and J2EE environments
15
Pitfalls without 360 Stakeholder Management

Lack of 24x7 in-depth visibility into the Application Reactive Management - using a crank when
problems occur
Overhead issues affect end-user performance Single console is not appropriate for collaborative
management
Require usage of different tools throughout the life
cycle
Generally require a framework with many
components
Introscope provides a common Language for Various IT Stakeholders to Manage and Solve Problems Together
Business-Facing Application Owner
Negotiate SLAs with Business Measure customer satisfaction and business processes Provide reports to Bus and Operations Management
Operations 24x7 live views of application P&A SLA monitoring Proactive incident detection
App Developer Deep views into web application Component-level blame Pinpoint root cause
Application Support Consistent, end-to-end view Evidence collection based on hard data Route problem to right person for fix
17
What kind of customer problems do we solve?

Are business apps slow?
PSFT
Is authentication server slow? Are customers affected?

Network Firewall Load Balancer
Identity Manager
SAP
Can I find the problem? Did we record everything?

Portal
Whats
Siebel mainframe
Mainframe
response time?
Router End User
Web services down?
Database
Are transactions failing?
What about the web servers?
Web Services
Databases
Are parties meeting SLAs?
3rd
How is database 3rd Party response? Applications
This picture applies to both Java-only & .NET-only environments except the Java environments are probably slightly more complex
And if you were to look inside the Java app SOA-based Java Web Apps are Complex
Highly componentized, distributed across your enterprise and connected to multiple back-end systems
Login JSP JNDI LDAP Server Account Info Servlet Account EJB Account Transaction Servlet WebSphere BI SAP, Siebel, PeopleSoft Database CICS/TuxedoConnector WebSphere MQ Connector CICS/IMS/Tuxedo
Login
Request Response
MQ Series
Sessions
JDBC Driver
APPLICATION
Request Response
Threads APPLICATION SERVER Memory JVM
Pools
Transaction
File and Network I/O

AIX HP-UX Linux OS/390 OS/400 Solaris Windows z/OS
19
so are SOA-based .NET Web Applications
Login ASP.NET Check Quote ASP .NET
ASP.NET
SQL Server
Browser
Enterprises Services
Web Service Consumer Directory Server Messaging Server
Web Services
ASMX Web Service Producer
Directory Service
.NET Messaging Transaction
APPLICATION DOMAIN CLR WINDOWS
and imagine what happens when you have a heterogeneous environment with BOTH Java and .NET Web Apps
Heterogeneous App Environment is Exponentially More Complex

Mainframe
MQ Web Services Web Services DB2
.NET APP
J2EE APP
J2EE Web Services
SQL Server
.NET APP Databases

Silo-Based Management Does Not Work
05:00 06:00 07:00 08:00 09:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00
% available
.NET App Java App Messaging Database Mainframe Trans Server
99% 99% 99.9% 99.9% 99.999% 99.9%
End-User App
Unavailable or Slow Available, Performant
80%
22
Wily Solution Overview
Only Wily Gives You Deep Visibility into Java/.NET Apps from the INSIDE to Predict, Diagnose and Record Performance in Real-Time
Introscope PowerPacks Databases, Web Services, Back-End Systems Availability, Performance, Errors, SLAs CA Network, Database, Systems, Workload, 3rd Party Applications
Identity Manager SAP
PSFT
Siebel Network Firewall Load Balancer Portal
Mainframe
Router End User
Switch
Database Web Servers Applications
Web Services
CEM Customer Experience, Transaction Success Rates, Failures, Errors, Defects, Scorecards, SLAs, Six Sigma Business Cost $$ and Impact
Introscope Availability, Performance, Failed TXs, Errors, SLAs Always-On Recording Transaction Tracing
Databases
3rd Party applications
23
Introscope Highlights
Wily is committed to enabling enterprises to put Java-based web applications into production quickly, and to keep them there
24 x 7 monitoring Incident detection & notification Rapid triage Root cause analysis Trend Analysis / Planning
Introscope Highlights 24 x 7 Monitoring: How is my system performing?
Real-time view of Application performance
25
Introscope Highlights Incident Detection & Notification: Tell me when theres

an issue
Online Purchasing
Early indications of a problem
26
Introscope Highlights Rapid Triage: Where exactly is the problem?

Determine the exact Online Purchasing problem component (e.g. slow DB call)
27
A complete breakdown of slow transactions:
Introscope Highlights Root-Cause Analysis: Whats causing the problem?
For example: Many small DB calls => Death by thousand paper cuts
28
Introscope Highlights
Trend Analysis / Planning: Are we performing as well as 6 months ago?
Online Purchasing
Historical views using live dashboards Every transaction is stored for review
29
How does Introscope Work An Introduction

24 x 7 Monitoring Like an aircraft flight recorder its always on. Operates in Production as well as QA testing and Dev environments with low single digit overhead. (1-3% in CPU Utilisation) Requires no changes to source code. Provides real-time and all historical performance data in the same interface. Works in any JVM and any J2EE Application Server.
30
How does Introscope Work What does it work with?

Core Application Servers
WebSphere Application Server (Versions 4.x to 6.x) Other Major Application Server Vendors And any others that use a JVM of JDK 1.2 or higher
Additional Components
Web Services MQ Series / Tuxedo Portals (WPS) 5.02 and above. Integration (WBI, WLI, SAP Enterprise Portal) Web Servers (Apache, IIS, etc.) And others including: (z/OS, Oracle Databases, etc.)
31
Inside to Outside
Internal JVM View with No Source Code Changes
CICS / IMS / Tuxedo
Connectors Workflow Authentication
Mainframe
Inside-to-Outside
Transaction Request MQ Series Third Parties
End-to-End
Response
SAP, Siebel, PSFT
PORTAL
Content
JAVA APPLICATION
APPLICATION SERVER
JVM AIX HP-UX Linux Solaris Windows OS/390
INTEGRATION
Web Services Databases
OS/400
z/OS
Fine-Grained Production Monitoring

Industry Standard Byte-Code Instrumentation Means Fast Time to Monitoring

Wily BCI Approach validated by
Java Community
Wily code adopted into J2SE 1.5
Instrumentation on the fly
Instrumented Code loaded into memory

Wily Does NOT modify source code!
means no coding required

Wily Agent compatible with ANY
JVM later than JDK 1.2
Sun, IBM, JRocket, etc.
Introscope AutoProbe Integration with JVM ClassLoader
Application Object Code (.jar files, etc.)

CLASS
10100101 11101010 10010010 10100101 00010110
Probes Inserted
33
Managing Heterogeneous Apps with 1 Single Tool and 1 Single User Interface
Swing or Browser Workstations
Real-time, Historical, and Performance Alerting J2EE Applications
Java Agent
Application Server
Introscope Enterprise Manager
Introscope Agents
JVM
.NET Agent Alerts, Events and Performance Data
.NET Applications
CLR
App Health, SLA and Capacity Planning reports
Agent
NonJava / .NET Systems
Historical Data
Introscope EPA
Monitors Java applications as soon as it is installed No coding is needed

Introscope automatically
detects and monitors any J2EE Components

EJBs Servlets JSPs JNDI JMS
Advanced Metrics
Concurrency Stalled Methods Instance Counts
35
From the Browser

- Browser Response Time Adaptor
Browser response time from a
user point of view

100% real transactions, not a
pinger
Associated customizable
dashboards
Answers these questions Is it our application or the network? Is the problem between the browser and the app server? What are average response times for this URL? This IP?
36
to the Database Tier

- SQL Agent
SQL Agent Monitoring SQL
Statement Performance from Javas point of view
Slow transaction
Oracle specific data
PowerPack for Oracle Database - Assessing Oracles health using Introscope

to the messaging tier

- For example: MQ Series
MQ Series Server MQ Series Connectors WBI Adapters
38
Analyze Failed Transactions with - ErrorDetector
View detailed information about errors as soon as they happen and improve end user experience
You need the ability to detect and diagnose the causes of serious errors, which can prevent individual users from completing web transactions
ChangeDetector:
What change affected my App?
Graphic visualization of change events

Files (text & binary) Archives & JAR files Classes loaded into the JVM System properties Oracle Database tables Configuration of connected subsystems (via EPA)
Detailed change event analysis

Change events visually displayed with
performance metrics Type of change (addition, deletion, modification) Time of change Difference between versions (for text files) Hierarchical and historical views of changes Customized reporting
Analyse Problematic Transactions

- Transaction Tracer
If Apps Average Response for Most Users is Fine
Isolate problematic individual transactions Analyze and pinpoint bottleneck for each Improve overall app performance From Browser to Back-end
How Do You Help the Isolated Incidents?
HELP HELP
41
Introscope gathers system resource information in addition to Java metrics

Introscope is designed to provide ALL the
data required to manage applications In addition to Java Code Performance, this includes:

Process monitoring Disk Utilization CPU Etc. Log File Message counts and monitoring
42
LeakHunter
- Eliminating Production Memory Problems
App is Down Again!!! Server Ran Out of Memory
Wily can help you

1. Identify potential leaks
Management By Forced Restarts
inside production apps 2. Pinpoint sources of leaks in app components and methods 3. Monitor life of all Java objects in memory 4. Isolate and remove leaks during stress testing
Restart App
24 Hours Later
43
Memory Leak Detection and Diagnosis

Introscope LeakHunter
Monitors the most common
production memory leaks

java.util.Collections
Instance Counts
Monitor the life of all Java
Objects in Memory
Number of instances in memory at any given time
44
Live AND Historical Views into Java Performance Data
Introscope SmartStore Historical Repository captures all Metrics all the time.
A Flight Recorder for your JVM
Analysis of Historical Data available in Workstation Client and via Reports Historical Data available for ANY Introscope Metrics

JVM Heap Usage CPU and other Resources AppServer Resources Java code performance
Records 100% of performance data for problem solving, trend analysis and capacity planning
IT to Business
Technical Data & Business Views
CICS / IMS / Tuxedo
Connectors Workflow Authentication
Mainframe
Transaction Request
MQ Series Third Parties
Response SAP, Siebel, PSFT
PORTAL
Content
JAVA APPLICATION
APPLICATION SERVER
JVM AIX HP-UX Linux Solaris Windows OS/390
INTEGRATION
Web Services Databases
OS/400
z/OS
IT to Business
Alerts and Framework Integration Aid in Collaborative Application Management

Flexible/Powerful Event Manager
Console Alert Message Alert Emails Events to Systems Framework Console Shell Script Actions Any combination of Events for either Threshold
Easily Configurable Thresholds

Caution and Danger Levels Configured in GUI Workstation Maximums or Minimums
Available for Any Metric in System

Response Times, Rates, Counts, Servlets, EJBs, Methods,
Where To Start ? At The Beginning ! :

Development, QA And Production.
Development Staging QA Understand load behavior Early detection of scaling issues

Certify for: Expected service levels Memory usage
Production Hosting
Ready-to-Use Dashboards Alerts that reflect real users
Characterise runtime
load
Establish problem
No surprise scaling bugs No out-of-memory restarts Fewer roll-backs
process
48
Introscopes Blame Technology
Introscope Performance Blame

Visualizing a Transaction
Blame Technology automatically discovers the interactions between components.
Flips Into Blame Drill Down

Relative Time Movement
+ +
Look for components down the hierarchy that are color coded according to weight. Drills down is used in many views, such as the Introscope Investigator and Transaction Tracer.
50

Visualizing a Transaction
Flips Into Blame Stack

Relative Time Movement
Look for the widest and deepest components when troubleshooting performance bottlenecks. This topographical view is the default Transaction Tracer view.

Visualizing a Transaction Client vs. Server
App Server Time End-to-End Transaction Time
Network Time
52

Visualizing a Transaction Multiple Servers
Remoting calls in separate servers
53

Visualizing a Transaction Back End DB
Transaction Tracer shows the whole transaction from front ends to back end SQL interaction.
54

Visualizing a Transaction Drill Down
Transaction Tracer provides multiple views of same data. Tree view provides quick drill down.
55
An Introduction To .NET Monitoring
Overview
The (Microsoft) .NET version
Browser Apps
ASP. NET
Rich Client Apps

Windows Forms Enterprise Services
ServiceOriented Apps
Other Apps
More
ASMX, WSE, etc
ADO. NET
.NET Framework Class Library Common Language Runtime (CLR) Windows

Product Architecture
Swing Or Browser Workstations

Real-time, Historical, & Performance Alerting
J2EE Applications
Agent
Application Server
Introscope Agents
JVM
.Net Agent
.NET apps
Alerts, Events & Performance Data
CLR
App Health, SLA and Capacity Planning reports
Agent
NonJava Systems
Historical Data
Introscope EPA
How The .NET Agent Works
.NET Agent
Web Application
Probes
.NET Agent
ASP.NET Worker Process CLR Window OS
59
Agents and Application Domains

In .NET framework,
applications run in domains

A separate Agent reports data for
.NET Agent .NET Agent .NET Agent .NET Agent
App Domain A
each domain Thus the total count of
App Domain B
reporting Agents equals:

the count of defined application
App Domain C Default Domain CLR Window OS
domains Agent in Default Domain does
not link to EM
60
IIS Architecture
Application A Request Client Tier Internet Information Server Window OS
Application A ASP.NET Worker Process
61
IIS Worker Process Configuration Options

Application A Application A Application B Application Pool App. A
Worker Process WP_1 Worker Process WP_2
62
The .NET Agent Instrumentation Process

CLR Runtime checks for presence of environment variables, Cor_Enable_Profiling and COR_PROFILER 2. This info used as lookup key in COM Registry to locate AutoProbeConnector 3. The AutoProbeConnector loads the AutoProbe, also via lookup in COM Registry
1.
.NET Applications COM Registry
6 2 3
Global Assembly Cache (GAC)
AutoProbe components
Environment Variables
5 1
AutoProbe locates the Agent in the GAC and loads it 5. The Agent finds its profile from environmental variables 6. Each application is instrumented according to PBDs
4.
.NET Agent
CLR Environment
Windows OS
63
.NET
Features Of The .NET Agent
64
The .NET Metric Set

.NET Agent and Probe code ported over from Java
version:
Thus similar types of metrics measured for .NET applications
Average Response Time, Concurrent Invocations, Errors Per Interval, Responses per Interval and Stall Count Compatibility with Introscope 7 Frontend/Backend scheme: Data reported about frontends, application health tracked in Application Overview grid ADO.NET data layer tracked in Backends category .NET Agent supports tracking of Web Services layer
65
The .NET Metrics In Investigator Tree

Two types of Metrics:
System-level Metric for ASP.NET process and CLR Application Metrics for each deployed web app
Application-specific Metrics For a Particular ASP.NET Application. System-level Metrics (CPU, CLR, ASP.NET process, etc) reported in PerfMon, GC Heap and Sockets categories
{
Variations In The .NET Metric Categories

A number of differences between .NET and J2EE
resource categories:
J2EE Application
JSP, Servlets
.NET Application
ASP.NET
Notes ASPX user-facing components listed SQLAgent-reported data appears under Backends category All Windows-reported infrastructure metrics appear here
JDBC
Backends > <<.NET Datasource_Name >> PerfMon | Processor
CPU
67
Frontend Metrics In .NET

Listed under primary Frontends category
Application URLs set in IntroscopeAgent.profile, or auto-
discovered and placed under Default category
68
ASPX Metrics
Listed under ASP.NET category:
Metrics reported here represent user-facing aspects of page as well
as code-behind logic
69
SQLAgent Metrics Reported in .NET

Listed under primary Backends category
Also support Boundary Blame, listed under Frontends | Apps
| | Called Backends
70
Web Services Monitoring

Web Services activity
monitored by Agent:
Appears under Web Services
resource category Data gathered for both
Producers and Consumers

Aggregated data by category Individual performance of each
Web Services component
71
Transaction Traces Of .NET Applications

Sampled Transaction Traces/Manually-launched
Sessions fully supported
72
Application Monitoring Resources

Sample Management Module for
.NET monitoring ships with Solution Pack

Named .Net Sample Defines:
Triage-oriented Metric Groupings and Alerts Detection and Triage Dashboards, and Application and Database Detail Dashboards
73
Web Services Resources

.NET Sample
Management Module provides dashboards for Web Services monitoring

Overview Dashboard Triage Dashboards
Consumer Health Producer Health
74
The Introscope Solution Pack for .NET

An management solution for enterprise applications
running on the .NET platform

Supports .NET 1.1 and 2.0 Includes the following Introscope components: Introscope .NET Agent
Introscope .NET Probebuilder Introscope .NET Autoprobe
Introscope .NET SQL Agent Extension Introscope 7.0 System (Enterprise Manager, Workstation &
WebView) PowerPack for .NET CLR Web Services Manager for Microsoft .NET
Customer Experience Manager (CEM)
How is CEM Applied

Changing the way IT and Business manages to the customers point of view. Fact based management
Problem Identification and Resolution
Problem Identification Problem Prioritization Rapid Cause Isolation Earliest warning Resource optimization Time and cost reduction
Elimination of defects & variance
Continuous Improvement
Improve performance, consistency Reducing risk of changes Greatest benefit to the business
Before, during, after upgrades Where to focus resources
Executive Reports, Scorecards, and Decision Support
Actual customers experience Reports in business terms $ Unique customer information API
Accurate communication Improved alignment with business Analytics and custom reporting
77
What Problems Does CEM address

Web-Tier Application-Tier Database-Tier Mainframe-Tier
Shift to web based apps Quick time to market, increased importance and reliance Increased complexity N-tier environments, access from anywhere anytime Seas of data Overwhelmed by various alarms and health information Inaccurate, inconsistent data IT reports all is well, yet users are complaining Wasting resources Constant mis-diagnosis, false positives, finger-pointing, rework Do more with less Pressure to reduce operating costs and improve quality of service
PROBLEM Inconsistent performance of business applications PROBLEM Lack of understanding of the business impact of an incident PROBLEM The time & resources to identify, isolate, and solve customer
incidents
What does CEM do Customer Experience Manager (CEM)

Measures the success of customer transactions in real-time Customers = customers, employees, agents, etc. Transactions = login, acct summary, place order, etc. Success = 0 defects, meeting expectations
Performance and quality analysis Identifies defects and variance Correlation of defects into incidents Calculates the business impact $$ of incidents Triggers immediate action to isolate incident cause Creates unique customer information (current and historical)
CEM Real-time, Distributed Architecture
Transaction Event and Statistics Server
TESS
Transaction Impact Monitor(s)

(Transaction Impact AnalysisTM)
Web Tier
Intranet / Internet
App Tier
Routers
Firewalls
Switches
LDAP
Database Tier
80
CEM Architecture
Low Risk, Zero Overhead
Router Network
Firewall
Switch
Load Balancer
Web Tier Application Tier
Database Tier
Mainframe Tier
Customers
Production Out-of-path
Mirrored Port for XX Application Web VLAN (i.e. Cisco SPAN Port)
Monitor Interface No IP Address
Management Interface Requires IP Address
Management VLAN
Transaction Impact Monitor (TIM)
TI M
Management Interface Requires IP Address
Real-time copy of production customer traffic Mirrored port of the application VLAN Core Ethernet Switch, Load Balancer, Network TAP
Transaction Event and Statistics Server (TESS)
TE S
81
CEM - Deployed
Production
Bob Wright Process Order Slow Transaction Time = 22.8s 06.01.05 8:59:48am
Mirrored Port for XX Application Web VLAN (i.e. Cisco SPAN Port)
Out-of-path Monitor Interface No IP Address

CEM
Identifies and Measures Customer Transactions Behavior and Content Defect Detection Correlation of Defects into Incidents Business Prioritization and $$ Impact Analysis Evidence Collection of Infrastructure State (performance, utilization, configuration, logs) Incident Forwarding into Existing Systems and Procedures Unique Customer Transaction Repository (Current and Historical Reporting, Scorecards, Analytics)
CEM Incident: Process Order Slow Time > 5.0s 256 Customers, 22 Premier Time: 06.01.05 8:59am Duration: 35minutes Incident cost: $278,00 Evidence Collection: Network, Web, App, DB,MF
82
CEM - Features
Transaction Impact AnalysisTM
Production customer transactions Customer / user identity by name Business impact $$ analysis
Creates Unique Customer Information in Real-time
Zero insertion risk

Real-time analysis of copy of production traffic No agents, no app changes, no latency, no load
Simple deployment and operation

Appliance-like installation One-time setup for universal visibility
CE M
CEM Platform
Real-time, scalable to the largest environments

Distributed architecture available for global institutions Open API and gateways for integration with existing systems
Open API
CEM - Focus on What is Important

Get above the noise Define once, monitor everywhere Transaction discovery options
Standard transaction recorder (browser based) Advanced transaction recorder (TIM based)
Transaction Discovery
Script translation recorder(Convert Mercury scripts, packet captures, etc.)
Not impacted by application UI changes

C EM
Transaction order structure

Business Processes Business Transactions Transactions Components Group of Business Transactions Series of pages Page URLs Siebel Order Provisioning Login Execute Login (SWE) & 14 others JavaScript, style sheets, etc.
NOTE: In most J2EE applications a Business Transition and a Transaction are the same
CEM Transaction Discovery

Recorders
Used in the One Time Define process Record users executing transactions one time Create generalized signatures Deploy to TIM(s) to monitor all users Simple Recorder - IE browser helper object Advanced Recorder runs on TIM(s) Transaction Import Utility reads: HTTP packet capture files (no SSL) Mercury VuGen log files
Networking & Security

CEM secure platform
CEM has no IP address on the monitored network CEM only needs an IP address on the Management VLAN CEM stores copies of the web server SSL keys more securely than web
servers
No IP address on the monitored network Encrypted using AES Does NOT terminate sessions
CEM stores NO private information about customers

Gets packets, analyzes them for behavior and response, throws them away Stores meta data about transactions (time, size, throughput, etc.), NOT the
transactions
Stores NO personal information (passwords, SSN, account balances, etc.)
CEM monitors transaction performance and quality, NOT user behavior

86
CEM Real-time, Distributed Architecture
Transaction Event and Statistics Server
TESS
Transaction Impact Monitor(s)

Web Tier
Intranet / Internet
App Tier
Routers
Firewalls
Switches
LDAP
Database Tier
87
CEM - Focus on What is Important

Get above the noise Simple, easy, one-time definition Transaction discovery options
Standard transaction recorder
Transaction Recorder
Advanced transaction recorder Script import utility (Mercury, etc)

CEM Platform
Not impacted by changes Transaction order structure

Business Processes Business Transactions Transactions others
CEM
Siebel Order Provisioning Login Execute Login (SWE) & 14 Components Scripts
88
CEM Solution Components

Transaction Impact Monitor (TIM)
Runs Transaction Impact AnalysisTM
Transaction Impact Monitor
Transaction Events and Statistics Server (TESS)

Runs CEM software suite
TESS
Transaction Events and Statistics Server

Open API
CEM Software Suite

Customer Impact Module Incident Resolution Module Gateway Services Module Customer Analytics API Transaction Discovery
89
Moving to Proactive Management

Improve availability by solving problems fast and avoiding problems
Reactive Management
Customer Call HELP!
Firefighting: Wheres the problem?
Black Box
Proactive Management
Proactively Monitors Production Applications
Detects Problem and Notifies
Pinpoints bottlenecks in app, app server, backend systems and environment, and solves customer problem
Applications Back to Normal
Pinpoints Bottleneck and Solves Problem Before Customer Calls
90
Wily Product Demo
For The Introscope & CEM Demo, please visit our stand.
91
Q&A
Any Questions ?
92

WILY, Managing Critical Applications With Wily Introscope, Robert Dring

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WILY, Managing Critical Applications With Wily Introscope, Robert Dring

Uploaded by

Copyright:

Available Formats

Wily | CA

Application Performance Monitoring (APM)

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

tere tulemast Tallinna!

Why Application Performance Monitoring/Management ?

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

When Theres a Problem, IT Needs to Know Where the Transaction is Failing

Are business apps slow?

Can I find the problem? Did we record everything?

Router End User

Switch Web Servers Applications

Web services down?

Are transactions failing?

What about the web servers?

Are 3rd parties meeting SLAs?

How is database 3rd Party response? Applications

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

Where are Transactions Processed?

Switch Web Servers Applications

3rd Party Applications

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

Traditional Management Approach:

Siebel Network Load Balancer

Router End User

Switch Web Servers Applications

3rd Party Applications

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

Introscope & Application Performance Management

Types of Performance Problems

App Server Web Configuration?

More Traffic Than Expected?

Which One is the Cause?

Transactions Too Slow?

Application Not Scaling?

Security Server Bottleneck?

requires a multidimensional approach

Why Application Performance Monitoring?

Database Servers CICS Backend Systems Security Servers

web applications for our customers

amongst our existing customers & future prospects

Managing heterogeneous application environment will be our specialty

Introscope product line

production applications used by Global 3500 companies

inside the JVM inside the Managed CLR outside

Monitors Microsoft .NET apps from

Wilys Customer Success Management Solution is supported by Introscope & CEM

Network, Systems and Servers

across the web infrastructure (Java or .NET)

management, trend analysis, capacity planning

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

Pitfalls without 360 Stakeholder Management

Copyright 2006 CA and Wily Technology, Inc. All Rights Reserved.

What kind of customer problems do we solve?

Is authentication server slow? Are customers affected?

Can I find the problem? Did we record everything?

Router End User

Switch Web Servers Applications

Web services down?

Are transactions failing?

What about the web servers?

Are parties meeting SLAs?

How is database 3rd Party response? Applications

Threads APPLICATION SERVER Memory JVM

File and Network I/O