15
1 TUTORIAL: WHITE PAPER VERITAS i 3 for Web-based Applications APPLICATION PERFORMA NCE MANAGEMENT – VERITAS i 3 FOR WEB-BASED APPLICATIO NS

TUTORIAL: WHITE PAPER

  • Upload
    others

  • View
    6

  • Download
    0

Embed Size (px)

Citation preview

1

T U T O R I A L : W H I T E P A P E R

VERITAS i3 for Web-based Applications

APPLICATION PERFORMANCE MANAGEMENT – VERITAS i3 FOR WEB-BASED APPLICATIONS

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

2

1. Executive Summary ......................................................................................................................................... 3 2. Introduction ..................................................................................................................................................... 3 3. The Typical Environment .................................................................................................................................. 4 4. Challenges Managing the Environment ............................................................................................................. 4 5. The VERITAS i3 Methodology ........................................................................................................................... 5 6. VERITAS i3 for Web-based Applications’ Features ............................................................................................. 8 8. Benefits of VERITAS i3 for Web-based Applications ..........................................................................................13 9. Summary ........................................................................................................................................................14

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

3

1. EXECUTIVE SUMMARY The deployment of web-based applications has dramatically changed the fundamental economics of service delivery, competitiveness, and user interaction. Web-based applications are quickly replacing more expensive, traditional “people-assisted” services. This new generation of applications has given businesses the unique opportunity to leverage legacy systems, distribute applications between multiple service ‘tiers’, and take advantage of newer computing technologies. Even though these web-based applications are offering businesses unsurpassed flexibility; they are taxing the very infrastructure on which they exist. The result is a high application rejection rate, because of negative user experience. Those implementing effective web-based applications know they need to include best practices to ensure success throughout the entire application life cycle – from development to deployment and operation. Unfortunately, this new generation of applications is even more demanding than their less complex predecessor applications. Users now expect to access a web site at any time from any location around the world. If an application’s user community sees that it takes too long for the blue bar on the bottom of their screen to creep from left to right, they simply leave and, frequently, won’t return to that web site. Likewise, if the service level provided doesn’t meet expectations, existing clients often revert back to more traditional and expensive interfaces to deal with that business or start looking at alternative vendors or services. Prospects simply move on. Thus, information technologists are struggling to find a repeatable and understandable way to measure the service level of each tier within the application – “URL to SQL metrics”. VERITAS i3 for Web-based Applications is the industry’s first software solution that quickly, efficiently, and unobtrusively captures the metrics necessary to appropriately tune the current generation of applications. It presents these important metrics in a manner that enables crisp communication, rapid detection, correction, and verification throughout the application life cycle; from development, to QA, to production, and back. This paper describes VERITAS i3 for Web-based Applications’ unique approach.

2. INTRODUCTION The internet, along with its supporting technologies, has enabled companies to design, develop and deploy web-based applications both within and outside the enterprise. The application functionality spans the spectrum from customer self-service, supply chain management, and beyond. The result is that companies are able to realize significant operational cost reductions, while improving service availability and expanding the company’s reach. This is accomplished by allowing customers, clients, partners, and prospects direct access to core systems, removing the extra “human-assisted” step required by the legacy system. The resulting “self service”, multi-tier, multi-server distributed processing systems running web-based applications have become the cornerstone of global electronic business. The combination of multiple tiers, disparate technologies, and often a reliance on the public infrastructure (or at best third party controlled infrastructure) makes the diagnosis of problems a very complex task. The current generation of applications requires a solution, which can be proactive as well as reactive in problem recognition. As a result of these complexities, organizations and owners of web-based applications are searching for performance management solutions that address their production monitoring needs and can be readily used in the staging, quality assurance, and performance/stress testing in a development environment.

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

4

3. THE TYPICAL ENVIRONMENT A typical, less complex, web-based application environment might look like this:

The management of a multi-tiered application demands both a comprehensive and straightforward method to measure the user experience. The detection of service level deviations or the ability to detect, alert, and document any perceived performance issues is paramount to managing any mission critical application. For web-based applications, primary consideration should be given to the service level provided and the optimum configuration(s) to deliver the required service level with “just-in-time” capacity. It is important to recognize that this new generation of web-based applications introduces several new performance considerations over traditional in-house applications operating on a client server or mainframe infrastructure: • The user community can not easily be trained on application usage • System response time is less predictable as usage patterns are have become less predictable • Multi-tier architecture makes it hard to pinpoint the source of performance problems • Multi-tier architecture often adds overhead to the response time • Inter-dependence between tiers can result in cascading problems • Third party software packages and their interfaces increase the complexity of the overall environment • The J2EE application environment inherently uses more “moving parts” • The J2EE applications are designed to run in parallel and in multi-processing configurations Key performance management requirements for this environment include the ability to: • Identify performance problems and elements that require monitoring • See the affect (impact) of performance delivered in the various tiers on the service level delivered to the end-user • Compare performance to baselines along with component specific service level agreements (SLAs) • Identify problematic characteristics and patterns before the end user is affected • Isolate, identify and analyze the symptom(s) and root cause of a problem • Verify that the solution has the expected result • Proactively and automatically analyze trends, detect problems and predict future performance

4. CHALLENGES MANAGING THE ENVIRONMENT IT organizations faced with these configurations typically have systems in place to monitor availability of the various infrastructure elements. These systems typically use agents deployed in the network and servers to gather systems usage data about the various monitored components. If a component’s use or average response time exceeds established thresholds or becomes unavailable, an alarm is triggered. While this is effective at detecting system level and network concerns (such as—unusually high server and application usage, packet rates, and retries), this level of detail is not effective in providing a view of the true end user experience.

Web Clients Web Clients Branch Office Branch Office

Web Web Server Server s s

J2EE J2EE Application Application Servers Servers

Oracle Oracle Database Database Servers Servers

Storage Storage Units Units

Tuxedo Tuxedo Servers Servers

Internet Internet

Web Client Web Client Home Office Home Office

Web Client Web Client On Road On Road

Web Clients Web Clients Customer Network Customer Network

Mainframe Mainframe

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

5

Metrics for end-to-end application analysis must be captured with agents having application knowledge and visibility – those that reflect the users experience. Today, typical approaches to isolate end-to-end problems use stovepipe detail snapshots of the performance of the various servers along a path outlined by the application specialist and data from geographically deployed robots. The robots initiate synthetic transactions to approximate what users might experience if they were to access the service using specific network connectivity (e.g., 100Mbit LAN) from that same location. While the system level and representative user information helps with monitoring and detecting deviations from the baseline, it does not provide sufficient detail or coverage to identify or account for individual or groups of users’ experience at the application, transaction or page level. Without the critical correlated data, the only option is to employ highly skilled diagnosticians over a lengthy time period.

Without this critical information, even the best diagnosticians rely on educated guesses along with the process of elimination to determine and resolve problems (e.g. a server has dropped from the configuration). Yet even with the identification of a failed component within a clustered environment, it may take extended time to isolate the component due to the granularity and amount of activity.

Companies using VERITAS i3 for Web-based Applications no longer have to rely on educated guesses, because the VERITAS i3 solution proactively detects emerging bottlenecks and isolates hotspots in minutes to avoid performance problems during all phases of the application life cycle. This enables IT organizations to effectively isolate the source(s) of problems by identifying and prioritizing root causes and offering corrective recommendations based on best practices. Additionally, VERITAS i3 will verify that the corrective action had the desired effect.

Because VERITAS i3 for Web-based Applications focuses on integrated application performance, it provides the actual end user experience and fills the end-to-end application performance-monitoring gap. It provides a “view” of how applications are performing as seen and reacted to by the end users. As such, VERITAS i3 for Web-based Applications identifies “the why” a web-based application isn’t meeting its goals. This is the question that every web-based application owner is asking, whether it be for ROI or simply to account for the high rate of click-aways from user frustration.

The fundamental proposition is that VERITAS i3 for Web-based Applications delivers the hard-to-get -at critical information needed to fine tune web-based applications; pinpoints friction points in the end-to-end path from the browser to physical storage media; provides the ability to drill down into hot spots to identify the application-specific concerns; offers best practices recommendations; and enables the easy validation of the effectiveness of any corrective action taken. And, VERITAS i3 for Web-based Applications complements and seamlessly interfaces with existing framework and infrastructure investments.

5. THE VERITAS i3 METHODOLOGY It is vital for all organizations to understand the importance of a holistic approach to coping with performance problems, and to realize the inherent ineffectiveness of ad-hoc fixes and problem solving. The foundation of the VERITAS i3 for Web-based Applications solution is a methodology designed to facilitate the rapid isolation, analysis, corrective action, and verification of application performance problems. All organizations can benefit from the discipline that VERITAS i3 brings to the performance management process. The VERITAS performance management methodology uses a proven process, as well as proven supporting solutions, to implement effective performance management within an organization. The VERITAS performance management methodology is comprised of five stages: 1. Detect –Identify the symptoms that could indicate a performance problem 2. Find – Identify the source of the problem 3. Focus – Discover the root cause of the problem 4. Improve – Take the steps required to improve performance 5. Verify – Make sure the steps taken have achieved the desired goal

These stages combine to form a process that provides a systematic approach to finding and resolving all kinds of performance issues, both predictable and unforeseen.

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

6

For example, the methodology begins with automated proactive and/or reactive detection (DETECT) using the product’s alert capabilities. This alert can be directed at the appropriate infrastructure framework, organization, or person based on what was detected. Alternatively, the appropriate person in your performance organization could periodically detect some long service times while reviewing the performance trends of elements such as EJBs, URLs, etc. Depending on the issue detected the diagnostician can view the application, end-to-end, and isolate (FIND) the source of the degradation or service time. The end-to-end service time and response time contributions enables the diagnostician to either identify the isolated symptom and pass the diagnosis to the appropriate support or development diagnostician that will FOCUS on the root cause. In turn the assigned diagnostician identifies the source of the degradation and either corrects it or passes the diagnosis to the responsible organization or person that will IMPROVE it (fix it). Once the change has been prepared it is tested in the appropriate environment using the appropriate VERITAS i3 for Web-based Applications components to VERIFY that the desired or expected result materializes. This VERIFY step may be applied at the various stages of the change promotion. VERITAS i3 for Web-based Applications focuses on providing your organization with the ability to measure and monitor your application performance end-to-end from the browser, the J2EE application server, and through the database right into the physical storage. VERITAS i3 for Web-based Applications is an integrated application performance manage-ment solution that is focused on identifying the service level experienced by the user and identifying the end-to-end path contributions. VERITAS i3 delivers a unique methodology that minimizes end user response times and simplifies the Application Performance Management of complex IT infrastructures. Conceptually, VERITAS i3 is comprised of Insight, Indepth, and Inform products. The products are seamlessly integrated and work in concert to focus on vital application components – this offers a complete end-to-end performance management solution. Alternatively, each VERITAS i3 component can be utilized as a separate product and run independently to meet specific environmental and application needs. The graphic below depicts the architectural components of VERITAS i3.

Application InfrastructureTier

InternetFirewall

Web Tier Database Tier

WebClient

Application InfrastructureTier

InternetFirewall

Web Tier Database Tier

WebClient

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

7

Insight – "Where is the performance slowdown originating from?" Today's applications leverage multi-tier architectures to deliver versatility but these architectures make it difficult to identify the origin of performance degradation. Insight, with TotalCorrelation™, helps solve this challenge by measuring response time across all architectural tiers from "URL to SQL" and segmenting the response time by tier. Insight identifies "where you should focus your efforts". Indepth – "What should be done to fix it?" Key Performance Indicators (KPIs) are captured from the entire IT infrastructure, 24x7, to ensure no matter where and when degradation starts, it never goes unrecognized. SmarTune™ is then leveraged to drill-down into the component level technology such as web servers, applications servers, middleware, databases, and storage to automatically identify the definitive root cause and generate expert tuning advice. Indepth identifies "why" there is a problem and "what" should be done to fix it. Inform – "Is there a performance problem right now? Was there one yesterday? Will there be one tomorrow?" Knowing "when" to focus on performance is just as important as knowing "what" to do to fix it. Without trends, baselines, exceptions, and alerts, it is difficult to efficiently manage application performance. Inform provides timely notification of the slightest degradation so maximum time is available to leverage the tuning advice offered by SmarTune. Whether the notification is the result of a service level violation or a performance metric starting to degrade, communication is sent to the right person at the right time. VERITAS i3 includes the VERITAS Performance Warehouse , which provides the common repository for the end-to-end correlated data history. This enables trend analysis and specific period performance reviews. The repository includes the ability to export for use by other analysis tools or to import metrics that should be included in the some of the reports for analysis. For example, let’s assume that you were interested in a web-based application that involves web servers, J2EE application servers, Tuxedo, and an Oracle database. You would select the VERITAS i3 for Web-based Applications solution. This would include all the functionality necessary to see the actual user’s response time, analyze the end-to-end path contributions including useful statistics for the web server the J2EE servers, the Tuxedo servers, and the database. You would be able to drill into the user response time, the performanc e contributions inside the J2EE JVM including all the application components running in it, as well as drilling down into the Oracle database and how it is serving the specific application and resolving contention from other applications.

Application Response Time SegmentationApplication Response Time SegmentationINSIGHTINSIGHT

Effective CommunicationEffective CommunicationINFORMINFORM

ReportingReporting

AlertingAlerting

Detailed Understanding of Technology ComponentsDetailed Understanding of Technology ComponentsINDEPTHINDEPTH

ClientClient NetworkNetwork Web SrvrsWeb Srvrs App SrvrsApp Srvrs DB SrvrsDB Srvrs StorageStorage

Application Response Time SegmentationApplication Response Time SegmentationINSIGHTINSIGHT

Effective CommunicationEffective CommunicationINFORMINFORM

ReportingReporting

AlertingAlerting

Detailed Understanding of Technology ComponentsDetailed Understanding of Technology ComponentsINDEPTHINDEPTH

ClientClient NetworkNetwork Web SrvrsWeb Srvrs App SrvrsApp Srvrs DB SrvrsDB Srvrs StorageStorage

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

8

6. VERITAS i3 FOR WEB-BASED APPLICATIONS’ FEATURES The VERITAS i3 software comes with a role controlled common interface that enables the appropriate organization to see the information they are entitled to see. This interface when fully exploited allows the authorized diagnostician to have a full end-to-end view and limits the others. In the example you can see the that the operator or diagnostician can elect to look at the Web Client, the Web Server, J2EE, Tuxedo, or Oracle database.

Using the methodology we can begin with an alert indicating that a web client service level threshold has been exceeded. This alert could be presented via your infrastructure framework or using the VERITAS Inform alert capabilities.

In this case we see that a service level threshold has been exceeded in France. Selecting the Web Client we can look at the details to determine the problem. Here we can see that 50% of the 598 page views from France are exceeding the service level threshold and 21% of these pages were abandoned before they completed downloading. We can drill further to see that response time appears to be problematic for all transactions from France. We are actually providing transactional detail on the performance of specific pages accessed by country. After analyzing this data we can conclude this is not a transaction specific problem.

We then look to see if there is a relationship between the performance and the network connectivity of those users that are experiencing the poor response time. We can quickly see that largest portion of pages viewed are from modem connections (510 views) and 50% of these are experiencing the problem while a much smaller percentage of degradation is experienced by those pages viewed via a LAN connection. In other words this is a performance degradation localized to France and associated with the bandwidth available. Providing a lighter weight page for France would fix the problem.

Threshold Alert

Countries France 50

Threshold Alert

Countries France 50

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

9

Now let’s look at a proactive example, in this case we are alerted with a Performance Trending and a Load Trending alert (not shown). We then look at the report, which reflects the reason for the alerts.

From the figures we can see where the URL service time has started climbing and has exceeded the exception threshold (red line). We can then also look to see the scope of the impact in terms of the number of pages that are above the SLA threshold (shaded red).

Having proactively detected a potential or real problem we can use VERITAS Insight to isolate the areas that require attention by looking at the performance contributors from an end-to-end standpoint. In this case we began by looking at service time.

50% of the page views are above

the threshold

All page views from Hungary are

performing the same

The bulk of the views

via modem

France

France

France

France

France

50% of the page views are above

the threshold

All page views from Hungary are

performing the same

The bulk of the views

via modem

France

France

France

France

France

ExceptionThreshold

SLAThreshold

ExceptionThreshold

SLAThreshold

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

10

Quickly scanning the end-to-end performance screen for the Web Server (previous screenshot) we see the Data Flow and the App Tiers – Total Time. From the Total Time chart we can see that Web Server and Oracle are the biggest contributors (the bars in this chart are accumulative). This tells us that the biggest performance improvements could be gained by looking at the Web Server and Oracle in that order. We can also see that a specific banner is the biggest contributor and most of the time is spent in server WS1 as was indicated by the load trending alert.

So let’s look at the server statistics.

We note that WS1 is running at 96% CPU, the most loaded when compared with the other two servers. Since all three servers service the user base we can quickly deduce that load balancing is not working. Correcting this bottleneck pre-empts a major performance exposure.

In this example the baseline offset threshold triggered our proactive attention and then working top down we were able to identify the end-to-end issue based on service time contributions. We were then able to zero in on one of the web servers. Then looking at how the entire server and the application was performing we were quickly able to determine the source of the problem.

Now let’s move on to see how we might analyze the J2EE contributions.

Web Server and Oracle

Biggest contributors

This banner contributed the

most time

Longest 5 IPs

Server where most time is

spent

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

11

Next, we use a feature called SmarTune that is used to correlate the data and provide detailed information about the specific problem in context. From this we can see that based on the Smartune correlated data .getDetails is the biggest contributor in the J2EE context and the biggest portion of it is wait time. You can also see that this there is only one JVM on EJBSRV1. Had there been multiple JVMs and multiple servers these would have been shown here. You will also notice that the Data Flow comes from the Web Server to J2EE and J2EE calls both Tuxedo and Oracle directly.

To isolate the problem we drill down into J2EE application using SmarTune. The J2EE SmarTune feature combines an in-depth knowledge of your J2EE application with expert system technology to instantly isolate the root cause of performance problems and recommend actionable advice on how to correct them. SmarTune automatically follows all the J2EE chained method calls to identify and rank the larger contributors. In this case the largest contributor is Tuxedo access time via the bea.jolt.JoltRemoteService.call (58%) followed by a database access (weblogic.jdbc.rmi.SerialStatement.executeQuery). By clicking on the “click here to see details: SmarTune also offers a best practices recommendation.

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

12

Looking at Tuxedo SmarTune Correlated Data we see that extensrv has excessive Queue Time. This could be achieved by adding another service process. See the following screenshot.

J2EE SmarTune also identified that weblogic.jdbc.rmi.SerialStatement.executeQuery was the second largest contributor to service time. The longest running select statement saw service time of over 3 seconds.

Analyzing this statement with VERITAS Indepth for Oracle we can see that a large portion of the time is using CPU. [Note: select e.name is being tracked as hash value 00811.06535.22991.04799]

In order to determine the source of the high CPU time we look at the execution plan for that statement as provided by plan for this statement. This enables us to see that the source of the problem is largely attributed to full table scans.

Excessive Queue time

Queue removed with second

server process

Longest SQL Statement

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

13

Reducing the statement’s execution time should help. We use the VERITAS Indepth for Oracle simulation facilities to test the effect of adding new indexes on other SQL statements before making the actual change. The following screen shot shows the dramatic impact to performance as a result of the change.

8. BENEFITS OF VERIT AS i3 FOR WEB-BASED APPLICATIONS To recap, we have seen the ability to: • Verify, validate, and isolate user response time complaints • Detect real-time and near service level deviations • Establish baselines and detect trend thresholds • Find service level friction points and identifying application dependencies on the Web Server, J2EE Server, Tuxedo,

and Oracle and identifying server specific configuration • Find specific J2EE performance considerations using SmarTune to identify the friction points within the JVM or

dependencies on other services such as Tuxedo and Oracle

These capabilities help IT organizations to: • Proactively detect friction before it impacts the user community • Manage and tune the application to effectively utilize the system resources required to provide the mandatory

service level • Use just-in-time capacity, deferring equipment and the associated software licenses and support costs until they are

required • Significantly reduce the amount of resources involved in the problem management process • Apply more energy to focus on correction and verification and less on data collection and meetings • Eliminate the “no problem found” response for frustrated web-based application users • Improve customer satisfaction with the application • More effectively communicate the service level achievements and improvements to the organization

Organizationally, VERITAS i3 for Web-based Applications helps Development, QA, Operations, Operations Support, and Capacity and Performance Management groups. The solution can be extremely helpful in a development environment for systems testing and understanding performance. Comprehensive data capture and automated data analysis provided by SmarTune will help application engineers effectively prioritize development efforts. Using VERITAS i3 for Web-based Applications in QA, Staging and Production environments assures the developer will spend more time to focus on application development and less time supporting problem resolution.

Very high CPU usage associated

with the SQL statement

After corrective

action

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

14

Because of the unique self-documenting features, Quality Assurance and Development organizations will save hundreds of hours in documentation, set-up and re-creation time. The browser-based user interface allows the QA specialist to copy the URL which encapsulates all the necessary information and pointers that the receiving support organization or development organization needs to immediately access the entire correlated environmental metrics that were associated with the reported problem.

System architects and capacity planning professionals can: • Catch design and architectural issues early before they affect end-users • Reduce the day-to-day tuning burden • Quickly and automatically identify baselines and performance trends

In summary, VERITAS i3 for Web-based Applications accelerates the deployment of web-based applications. It provides all the necessary mechanisms to realize significant resource savings, while assuring the service level objectives are being met. These capabilities ensure a greater ROI by reducing performance frustration that results in click-aways and customer loss.

9. SUMMARY Today, IT organizations are challenged with meeting the increasing demands from end-users for high performance. And, experience has shown that there is a direct correlation between service delivery and both internal productivity and revenue generation. VERITAS addresses these challenges by providing business performance management solutions that help identify the exact cause of performance problems and their impact on the entire system. Unfortunately, poor performance can result in loss of business, missed opportunities and failure to realize the ROI required to support operational expenses.

VERITAS i3 for Web-based Applications addresses these challenges and actually simplifies the development and deployment of high performance web-based applications. Using VERITAS i3 for Web-based Applications helps companies manage and improve their service level to end users, contain costs and maximize the efficiency of the operational investment.

VERITAS i3 for Web-based Applications is the industry’s first software offering that provides a way to quickly, efficiently and unobtrusively capture the hard to get URL-to-SQL application metrics and present these in a manner that enables crisp communication, rapid proactive or reactive detection, correction and verification through-out the application life cycle.

VERITAS i3 for Web-based Applications, sets a new milestone in web-based Application Performance Management by delivering a comprehensive integrated software solution that addresses the major service level challenges.

This solution: • Focuses on the application’s user response time • Provides a view of the actual service levels as seen by all the users at their desktop • Identifies the application end-to-end path • Presents end-to-end response time contribution • Isolates the hotspots from the browser to the SQL and the database • Identifies root cause right down to the J2EE method or systems configuration • Provides best practices corrective action recommendations with supporting data • Identifies the application service impacts of the service level • Operates in a production environment with minimal overhead • Requires no application changes or developer awareness • Fits all phases of the application lifecycle (e.g.Development, QA, Stress Testing, Staging, and Production) • Meets the detection, reporting, isolation and diagnostic needs of all organizations involved • Has a consistent method of presenting service level information • Interfaces with and complements existing infrastructure frameworks • Provides baselines and reports trends • Provides real-time deviation and trend-based alerts

Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

15

VERITAS Software Corporation Corporate Headquarters 350 Ellis Street Mountain View, CA 94043 650-527-8000 or 866-837-4827

For additional information about VERITAS Software, its products, or the location of an office near you, please call our corporate headquarters or visit our Web site at www.veritas.com.