Quest PerformaSure 3.0 “J2EE Power Diagnostics”

1. Quest PerformaSure 3.0 “J2EE Power Diagnostics” Quest Application Performance Management for the J2EE platform Rini Gahir, Product Manager Mark Gowdy, J2EE SC

2. Agenda • Current market trends • What is PerformaSure • What’s new in 3.0 • DEMO • Q&A

3. J2EE Performance in the Market • Customers demand performance and scalability from your J2EE systems • 80% of production J2EE applications don’t meet their performance requirements • This can jeopardize your business through lost revenue from e-business sales or lost confidence (and partnerships) from B2B site failures

4. FACT #1: Bad code is a big problem • A recent industry survey showed that bad code, server configurations and database connectivity were the largest contributors to app downtime and bad performance Causes for application downtime and poor performance Gartner: 2004

5. FACT #2: Developers are still pulled into production problems • Developers are still pulled into firefight and diagnose application issues. This is very costly and has an impact on current projects. Who is responsible for application management in your organization? Gartner: 2004

6. Why Developers? IT Application Administrators lack experience with J2EE systems. • They do not understand the inner workings of application servers • They don’t have control of the code • They pull-in and rely on development experts to assist in detailed diagnosis and resolution

7. FACT #3: Frequent updates to J2EE apps • J2EE applications undergo constant updates and change yet still experience a high rate of application roll-backs. This is costly to any organization. How frequent are changes made to your deployed J2EE applications

8. Summarized Problem Impact • Development gets involved impacting their project deliveries – costly delays • Application roll-backs mean downtime • Late stage performance bugs – costly to fix Problem Statement: Performance problems found later in production cost almost 10x more to fix. “Test early-test often”

9. Our Goal: • Minimize Investigation and Repair times • Maximize our uptime Problem Impact • How frequently does this happen? • Persistent – every week • Intermittent – random/unpredictable

10. Addressing Key Concerns • Ensure that J2EE applications are optimized prior to production • Getting real-time visibility into performance & availability of production J2EE applications • Quickly triage & isolate problems across all tiers • Drill down to identify intermittent problems such as specific instances of slow methods, memory leaks, synchronization problems, cross JVM’s

11. The Challenge: Ensuring Application Performance • A systematic approach to detect the problem, correctly diagnose the root cause and resolve the issue in a timely manner • An integrated tool set to provide detection of performance problems, power diagnostic capabilities, and quick resolution of problems once diagnosed Requires two things:

12. Introducing PerformaSure 3.0J2EE Power Diagnostics • What transactions are slow? • Where are my transactions spending their time? • Web server, App Server, Database?? • What SQL calls are performing poorly? • What component is the root-cause of the problem? PerformaSure provides a correlated transaction-centric analysis of the application across the J2EE stack. On-Demand Diagnostics works in production and pre-production environments.

13. What’s New in 3.0 Enhanced Workstation • Better visualization for faster root cause analysis • Easier correlation and interpretation of data • Increased diagnostic capability • Improved runtime manageability

14. Enhanced Time Browser View the performance of an individual service request View each request broken down by time spent in each tier Further analyze a specific request by tier, component or server and then drill down deeper into the Tree or Metrics Browsers.

15. The New SQL Browser • View the most expensive SQL call from the Java app by: • Execute • Prepare • Retrieve • Correlated with the end-user transaction • Integrate with QC database diagnostics

16. Power Diagnostics: Prune & Isolate • Focus on the parts of the transaction that matter by pruning out the unwanted branches and isolating the offending component.

17. Statistical Metrics – adding meaning to the data • Look for trends and exceptions in the data • Improved interpretation and analysis • Faster root-cause resolution

18. Improved Manageability • New recording console allows you to control all aspects of recording for an easy to use interface • Multiple Agent management – turn on/off agents right from the console • Sampling, filtering and request separation now managed through the console – no need to bounce servers!

19. Introducing the ‘X-Agent’ • Extend application visibility for ANY Java application! • JBoss • JRun • Tomcat • ATG Dynamo • Any J2SE application • Requires Quest J2EE professional services to configure for your app

20. Oracle9i Application Server Agent • New Oracle 9iAS Application Server Agent (versions 9.0.2, 9.0.3)

21. Support for BEA JRockit • PerformaSure continues to expand platform support as the market dictates. BEA WebLogic JRockit is a high-performance JVM for the WebLogic platform. Unlike other JVMs, BEA WebLogic JRockit is designed to power demanding server-side Java applications —delivering superior performance, manageability, and reliability for enterprise applications.

22. DEMO

23. More information • Quest APM for the J2EE platform • http://www.quest.com/apm_j2ee/ • Weekly J2EE Webcasts • http://java.quest.com/webinars/performasure/ • PerformaSure Discovery Demo • http://www.quest.com/performasure/discovery.asp • J2EE HealthCheck using PerformaSure • http://www.quest.com/j2ee_healthcheck/

24. Q&Arini.gahir@quest.com

25. THANK YOU FOR LISTENING