Symantec i 3 AVAILABILITY & PERFORMANCE
The Web Applications Environment <ul><li>Multi-tier applications that can include : </li></ul><ul><ul><li>Client (Web brow...
Architecture Web Clients Web Clients Web Servers J2EE Server Oracle Databases Legacy System External System
Symantec i 3 <ul><li>Symantec i 3  is an  integrated  solution that is </li></ul><ul><li>end-user focused .  </li></ul><ul...
Why an Integrated Solution? <ul><li>With a multi-tier architecture, IT must: </li></ul><ul><li>Align IT to business priori...
AVAILABILITY & PERFORMANCE
AVAILABILITY & PERFORMANCE
Case Study <ul><li>Enterprise web application running on a 4-tier architecture </li></ul><ul><li>International flower orde...
 
 
 
Status <ul><li>Conclusions – symptoms detected  </li></ul><ul><li>A problem was identified in the  check_my_order  busines...
 
 
Status <ul><li>Conclusions – source found </li></ul><ul><li>Java class  /verify/orders/country/orders_list.jsp  is the pro...
AVAILABILITY & PERFORMANCE
 
 
 
Status <ul><li>Interim Conclusions – focus on the reason </li></ul><ul><li>We have contrasted synthetic transactions vs. r...
 
 
Status <ul><li>Interim Conclusions – focus on the reason </li></ul><ul><li>The J2EE tier is dominating resource consumptio...
AVAILABILITY & PERFORMANCE
 
 
Status <ul><li>Interim Conclusions – focus on the reason </li></ul><ul><li>Smartune ranked JDBC Access Major Time as the m...
 
 
Status <ul><li>Conclusions  </li></ul><ul><li>The problem is not the database tier, but how frequently the database is acc...
 
Case Study Summary <ul><li>We have successfully completed the methodology cycle:   </li></ul><ul><li>Detect </li></ul><ul>...
Synthetic Transactions Versus Reality <ul><li>Synthetic transactions indicate availability </li></ul><ul><li>They should s...
 
 
 
Synthetic Transactions Versus Reality <ul><li>Summary  </li></ul><ul><li>Systematically analyzed changes in usage pattern ...
AVAILABILITY & PERFORMANCE
VCS Case Study <ul><li>Enterprise web application running on a 4-tier architecture  </li></ul><ul><li>Symantec Cluster Ser...
 
 
 
Status <ul><li>Interim Conclusions </li></ul><ul><li>Upon Oracle tier failure, VCS activated failover </li></ul><ul><li>Ne...
AVAILABILITY & PERFORMANCE
 
 
 
Status <ul><li>Conclusions </li></ul><ul><li>Oracle ran on sys1 </li></ul><ul><li>DiskGroup-oradg failed on sys1, hence VC...
 
Proactive & Preventive VCS Actions <ul><li>Implement a systematic review of resource consumption overtime to forecast util...
 
 
 
Proactive & Preventive VCS Actions <ul><li>Summary  </li></ul><ul><li>Discovered peak of CPU consumption on server SrvProd...
AVAILABILITY & PERFORMANCE
& ANSWERS QUESTIONS
Upcoming SlideShare
Loading in …5
×

Symantec I3 - Inquire & Cluster

2,467 views

Published on

Performance Management form synthetic transactions, Web, J2EE, OS and Cluster HW

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,467
On SlideShare
0
From Embeds
0
Number of Embeds
72
Actions
Shares
0
Downloads
64
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Symantec I3 - Inquire & Cluster

  1. 1. Symantec i 3 AVAILABILITY & PERFORMANCE
  2. 2. The Web Applications Environment <ul><li>Multi-tier applications that can include : </li></ul><ul><ul><li>Client (Web browser) </li></ul></ul><ul><ul><li>Web Server </li></ul></ul><ul><ul><li>J2EE Application Server </li></ul></ul><ul><ul><li>Interfaces to external systems </li></ul></ul><ul><ul><li>Database </li></ul></ul><ul><li>Worldwide, around-the-clock user access </li></ul><ul><li>Usage patterns are not controlled </li></ul><ul><li>Management requires the expertise of multiple IT teams </li></ul>
  3. 3. Architecture Web Clients Web Clients Web Servers J2EE Server Oracle Databases Legacy System External System
  4. 4. Symantec i 3 <ul><li>Symantec i 3 is an integrated solution that is </li></ul><ul><li>end-user focused . </li></ul><ul><li>Symantec i 3 provides a built-in methodology that enables you to effectively manage the Availability and Performance </li></ul><ul><li>of business applications. </li></ul>
  5. 5. Why an Integrated Solution? <ul><li>With a multi-tier architecture, IT must: </li></ul><ul><li>Align IT to business priorities </li></ul><ul><ul><li>Monitor the availability and performance of “business processes” </li></ul></ul><ul><ul><li>Monitor “business processes” 24x7 from multiple geographies </li></ul></ul><ul><ul><li>Constantly update the “business processes” by adjusting to real usage patterns initiated by real users </li></ul></ul><ul><li>Easily & rapidly detect problems, & analyze in context </li></ul><ul><li>Correlate application flow activities among technologies </li></ul><ul><li>Pinpoint & analyze their causes </li></ul><ul><li>Implement proactive tuning of your performance and availability </li></ul>
  6. 6. AVAILABILITY & PERFORMANCE
  7. 7. AVAILABILITY & PERFORMANCE
  8. 8. Case Study <ul><li>Enterprise web application running on a 4-tier architecture </li></ul><ul><li>International flower ordering service </li></ul><ul><ul><li>The system is critical to sales & support activities </li></ul></ul><ul><ul><li>The worldwide data center is located in NY </li></ul></ul><ul><ul><li>The central orders database is updated at 10:00pm NY time </li></ul></ul><ul><ul><li>Sales peak around local holidays, e.g. Mother’s Day on May 9 in Italy & USA </li></ul></ul>
  9. 12. Status <ul><li>Conclusions – symptoms detected </li></ul><ul><li>A problem was identified in the check_my_order business transaction from USA & Italy </li></ul><ul><li>A synthetic transaction identified the problem </li></ul><ul><li>The problem occurred after database update, at 10:05pm NY time (4:05am the next day in Italy) </li></ul><ul><li>Next Steps – find the source </li></ul><ul><li>Identify the problematic page component </li></ul>
  10. 15. Status <ul><li>Conclusions – source found </li></ul><ul><li>Java class /verify/orders/country/orders_list.jsp is the problematic component </li></ul><ul><li>Next Steps – focus on the reason </li></ul><ul><li>Identify whether this problem also occurs with real transactions </li></ul>
  11. 16. AVAILABILITY & PERFORMANCE
  12. 20. Status <ul><li>Interim Conclusions – focus on the reason </li></ul><ul><li>We have contrasted synthetic transactions vs. reality </li></ul><ul><li>The problem only occurs with synthetic transactions, due to timing (10:05pm NY / 4:05am Italy) </li></ul><ul><li>Real users will be affected once the next day starts - Mother’s Day in Italy, USA & some other countries </li></ul><ul><li>Next Steps </li></ul><ul><li>Investigate server side to pinpoint the problematic tier </li></ul>
  13. 23. Status <ul><li>Interim Conclusions – focus on the reason </li></ul><ul><li>The J2EE tier is dominating resource consumption </li></ul><ul><li>The problematic method is verify_orders_country_orders_list._jspService </li></ul><ul><li>Next Steps </li></ul><ul><li>Further investigation is needed in the J2EE tier </li></ul>
  14. 24. AVAILABILITY & PERFORMANCE
  15. 27. Status <ul><li>Interim Conclusions – focus on the reason </li></ul><ul><li>Smartune ranked JDBC Access Major Time as the main problem </li></ul><ul><li>Next Steps </li></ul><ul><li>Seek more details and advice </li></ul>
  16. 30. Status <ul><li>Conclusions </li></ul><ul><li>The problem is not the database tier, but how frequently the database is accessed </li></ul><ul><li>Due to the unusually high number of db queries, time spent in the JSP is too long </li></ul><ul><li>Italy and USA behavior differs from other countries’ due to the Mother’s Day high increase in orders </li></ul><ul><li>Next Steps – address the problem & verify the solution </li></ul><ul><li>Instead of querying each order item individually, a new single query that returns all items should be implemented </li></ul>
  17. 32. Case Study Summary <ul><li>We have successfully completed the methodology cycle: </li></ul><ul><li>Detect </li></ul><ul><ul><li>An SLA breach problem was detected by a synthetic transaction in Italy and USA, before the problem was experienced by real users </li></ul></ul><ul><li>Find </li></ul><ul><ul><li>A specific JSP is responsible for the slow response time, but only in specific countries </li></ul></ul><ul><li>Focus </li></ul><ul><ul><li>The unusually long order list in Italy & USA caused an exceptional number of connections, resulting in lengthy JDBC access time </li></ul></ul><ul><li>Improve </li></ul><ul><ul><li>Restructure queries and results pages </li></ul></ul><ul><li>Verify </li></ul><ul><ul><li>The SLA problem has disappeared without affecting real users </li></ul></ul>
  18. 33. Synthetic Transactions Versus Reality <ul><li>Synthetic transactions indicate availability </li></ul><ul><li>They should systematically reflect a dynamic real-world situation </li></ul><ul><ul><li>Identify application usage changes relating to both existing and new applications </li></ul></ul><ul><ul><li>Reflect new delivered functionality </li></ul></ul><ul><ul><li>Reflect trends regarding usage from new locations </li></ul></ul>
  19. 37. Synthetic Transactions Versus Reality <ul><li>Summary </li></ul><ul><li>Systematically analyzed changes in usage pattern </li></ul><ul><li>Identified new used functionality, change in usage patterns, and heavily used locations </li></ul><ul><li>Based on the findings, the user can now adjust the synthetic transactions to reflect the actual real-world situation </li></ul>
  20. 38. AVAILABILITY & PERFORMANCE
  21. 39. VCS Case Study <ul><li>Enterprise web application running on a 4-tier architecture </li></ul><ul><li>Symantec Cluster Server (VCS) is activated on two machines running Oracle </li></ul><ul><li>Each machine switches to the other upon failure </li></ul>
  22. 43. Status <ul><li>Interim Conclusions </li></ul><ul><li>Upon Oracle tier failure, VCS activated failover </li></ul><ul><li>Next Steps </li></ul><ul><li>Follow the Alerts advice and use the VRTS Cluster Manager to investigate further </li></ul>
  23. 44. AVAILABILITY & PERFORMANCE
  24. 48. Status <ul><li>Conclusions </li></ul><ul><li>Oracle ran on sys1 </li></ul><ul><li>DiskGroup-oradg failed on sys1, hence VCS switched Oracle to sys2 </li></ul><ul><li>Despite a major problem, the application remained available </li></ul><ul><li>But, to ensure availability over the long-term, the problematic resource must be repaired </li></ul>
  25. 50. Proactive & Preventive VCS Actions <ul><li>Implement a systematic review of resource consumption overtime to forecast utilization </li></ul><ul><li>Identify up coming over-consumption </li></ul><ul><li>Establish VCS failover policies and assign system resources, accordingly </li></ul>
  26. 54. Proactive & Preventive VCS Actions <ul><li>Summary </li></ul><ul><li>Discovered peak of CPU consumption on server SrvProdD at the end of each month </li></ul><ul><li>In the future, this increase will exceed the overall CPU capacities </li></ul><ul><li>Based on the findings, the user can now establish an appropriate VCS failover system </li></ul>
  27. 55. AVAILABILITY & PERFORMANCE
  28. 56. & ANSWERS QUESTIONS

×