I3 - for Web & J2EE

APMSymantec i3 for Web Applications

2 Symantec Corporation, All Rights Reserved 2005

The Web Applications Environment

Multi-tier Applications that can include:– Client (Web Browser)– Web Server

– J2EE Application Server– Interfaces to external systems– Database

Worldwide, around-the-clock user access

Usage patterns are not controlled

Management requires expertise of multiple IT teams


Architecture

WebClients

WebClients

Web Servers

J2EE Server

Oracle Databases Legacy System

ExternalSystem


Symantec i3

Symantec iSymantec i33 is an is an integratedintegrated solution that is solution that is end-user focusedend-user focused. .

Symantec iSymantec i33 provides a built-in provides a built-in methodologymethodology that enables that enables you to effectively manage the you to effectively manage the AvailabilityAvailability and and PerformancePerformance

of business applications.of business applications.


Why an Integrated Solution?

With a multi-tier architecture, IT must:

Software packages and their interfaces increase the complexity of the overall environment

Analyze exceptions in their transaction context

Identify and verify solutions

Implement proactive & preventative performance tuning


Case Study

Enterprise web application running on a 4-tier architecture.

Gourmet food inventory management system serves offices worldwide

– each country specializes in marketing its local foods– the system is critical to ongoing sales and support activities.






Conclusions – symptoms detected Conclusions – symptoms detected

• A service problem is affecting French users

Next Steps – find the sourceNext Steps – find the source

• Define the problem more specifically

Status





Conclusions – source foundConclusions – source found

• SLA breach only for URL

/verify/control/country/details.jsp for French users

Next Steps – focus on the reasonNext Steps – focus on the reason

• Investigate server side to pinpoint the problematic tier

Status





Interim Conclusions – focus on the reasonInterim Conclusions – focus on the reason

• The problematic Method is

verify_control_country_details._jspService

• Resource Consumption is primarily constrained to 1 of

the 3 JVMs

Next StepsNext Steps

• Further investigation is needed in the J2EE tier

Status




Interim Conclusions – focus on the reasonInterim Conclusions – focus on the reason

• Smartune ranked JDBC Access Major Time as the

main problem


• Seek more details and advice

Status





Interim Conclusions Interim Conclusions • The problem is not in the database tier, but rather in

accessing the database frequently .• Due to the unusually high number of db queries, time

spent in the JSP is long.


• Compare France’s JVM behavior to other JVMs.

Status




ConclusionsConclusions• France’s behavior differs from all other countries due to

the exceptionally long list of gourmet items, with each incurring a separate SQL statements

Next Steps – improve the situation & verify the solutionNext Steps – improve the situation & verify the solution

• Instead of querying each gourmet item individually, we should execute one query to return all the items.

Status



Summary

We have successfully completed the methodology cycle:

DetectDetect

SLA breach problem was detected for users in France

FindFindA specific JSP is responsible for the slow response time, but only in France.

FocusFocus

The unusually long item list in France caused an exceptional number of connections, resulting in lengthy JDBC access time

ImproveImproveRestructure queries and results pages

VerifyVerifyThe SLA problem has disappeared


&ANSWERS

QUESTIONS

Business

I3 - for Web & J2EE