1. Copyright 2005 OpTier Inc. All rights reserved. Contents subject to change without notice. 1 SOA Monitoring & Performance Management Challenges Fernando Pereira Developer, Senior Technical Consultant fernando@OpTier.com

2. 2 SOA Monitoring & Performance Management Challenges ABSTRACT The internal workings of a service, including any dependencies on system components and performance metrics are hidden by design. Obscures the transaction's invocation chain Presents a plethora of management challenges Successful deployment of SOA requires effective management of SOA. Requirements: A business-context-driven view of a service's components How the components function and interact among themselves in the SOA How the components function across its borders to legacy environments This presentation will cover: The challenges in managing a production SOA How business transaction tracking helps you get the most of your move to SOA How to go beyond monitoring hardware and software application performance, and actively maintain service level agreements based on business priorities

3. 3 Agenda Intro SOA Drivers and Momentum SOA Management Suites SOA Deployment Challenges Business Transaction Workload Management to meet these challenges Q&A

4. 4 IT Infrastructure End User Business Transactions Cross Tier Business Transactions Applications Businesses depend on IT services Transaction flow Transaction context Business Context Application components (programs, EJBs, SQLs, …) Servers, Databases, OSs, Networks…

5. 5 IT Infrastructure End User Business Transactions Cross Tier Business Transactions Applications Businesses depend on IT services Transaction flow Transaction context Business Context Application components (programs, EJBs, SQLs, …) Servers, Databases, OSs, Networks… Increasing, varied demand Increasing complexity (SOA, ESB, Integration) Consolidation, Virtualization No visibility No control

6. 6 SOA – Service Oriented Architecture Helps IT support business needs for Flexibility Changeability Smaller reusable units of service Easily combine to create new services Package legacy systems for integration Implement service Assembly and wire to execute a (business) process Distinct separation between service and implementation A management challenge Gradual change

7. 7 SOA Drivers and Momentum Enterprises faced with major changes relevant to SOA: Volatility of markets Global competition Business and IT need to be more agile and dynamic Web services – enabling technology for SOAs SOA gaining momentum A November 2004, Forrester survey shows that large enterprises are overwhelmingly adopting service-oriented architecture (SOA): More than 70% of large enterprises report using SOA now. Beyond simply adopting SOA, 29% of large enterprises have an enterprise-level commitment to SOA, and 19% are using SOA for strategic business transformation. A March 2005 survey of 100 CIOs by Smith Barney found that service-oriented architecture was their number one priority in the area of emerging technologies.

8. 8 SOA Management Suites Monitoring manage service capacity thresholds, faults, errors, and other conditions Performance monitor service throughput and capacity as well as aggregating performance data and creating input for service- level agreement (SLA) reporting Security Authentication and authorization Routing arbitration, fail over, load balancing, dynamic routing, data/protocol/XML transformation, and scheduling Catalog Support discovery and integration capability including authentication, authorization, provisioning, and configuration services

9. 9 SOA monitoring & performance management challenges Performance metrics are hidden by design Challenges SLA compliance is NOT guaranteed Limited visibility beyond SOA borders Limited performance management Banking example: Two customer positions Logon – time sensitive Browsing info – hooked Both get account details – implemented as a service or transaction component No transactional context means both get the same resource allocation at execution time

10. 10 Customer account inquiry Account Info Back-office daily analytics query Analytics WU-Work Unit Infrastructure Service Indicators Transactions lose original Identity /context Transactions with different business priorities receive same treatment ! ! Install Collectors/agents Fails to meet SLA Performs better than SLA The root cause - inherent flaws Web serverApp server1 App server2 DB server

11. 11 Customer account inquiry Account Info Back-office daily analytics query Analytics Fails to meet SLA Performs better than SLA tracking transactions WU-Work Unit Infrastructure Service Indicators Transactions lose original Identity /context Transactions with different business priorities receive same treatment ! ! Auto-Discover & Track transactions Transaction identity maintained Web serverApp server1 App server2 DB server

12. 12 Meeting the challenges End-to-End view across all tiers Guaranteed SLA Compliance End-to-End Visibility Beyond the SOA Border Fine-tuned Performance Management Topology - understand Platform availability – measure and manage Local Service availability - measure End-to-end service availability SLA Trending Capacity planning

13. 13 Assured SLA Compliance Service definition includes policies covering Security Performance Contracts Existing tools are stateless and without context In production it is necessary to maintain business context at all tiers Even better to actively reallocate resources by pre- assigned levels of priority Provides ongoing guarantee of QoS SLAs

14. 14 Accelerated problem resolution and end-to- end visibility beyond SOA borders Need to monitor the performance of business processes and their discrete functions Need to understand business impact of service disruptions New and expanded uses of legacy systems There is a gap between what SOA tools can see and do and what needs to be done What is needed is the ability to look into service components and maintain business context

15. 15 Improved TCO and Accelerated ROI for SOA Deployment Existing tools lack information – deployment metrics Their solution is to overprovision Wasted resources It is necessary to expose deployment metrics at all levels and then actively prioritize execution to guarantee SLAs without over-provisioning Efficient use of resources providing better performance

16. 16 Business tracking of transactions fills the gap in SOA management solutions

17. 17 Business tracking of transactions fills the gap in SOA management solutions (cont.)

18. 18 Common performance problems Getting the right DATA Capacity planning, trending Various workload Different business services using same infrastructure Difficulty understanding per workload – which services/tiers are used Multi step execution path Difficulty tracking transaction/service resource usage, per tier. Complex business impact Difficulty knowing which users/transactions/geographies are served per machine/tier.

19. 19 Common performance problems Common problems and how to detect them Application architecture issues Chattiness (across transaction’s whole path) Flow (concurrency) (*) Configuration issues Wrong topology Resource bandwidth allocation (resource pools: CPU, IO, connections…) Code issues Wait time, cause (*) Inefficient memory (i.e. string) management Poor use of system resources: JNDI, JDBC, JMS/ CLR W3WP dllhost Iterations of CPU bound logic Thread monitoring issues: poor usage of synchronized blocks Resource spent, what, where, bottlenecks Increase activity or increased resource consumption

20. 20 Solution architecture guidelines Architecture goals Production grade overhead (<%5) Track all transactions all the time, across all tiers. Keep both contexts: business (WWW) and physical (tiers and resources) Quick time to value (auto discovery, minimal dev involvement) Active capability Solution architecture Lightweight stateless collector (DTE) Smart context agent Single repository, single management server Federated policy management. Analysis and heuristics based on historical data. Keep business and physical contexts.

21. 21 Web serverJ2EE Web App server1 J2EE EJB App server2 DB server Production grade - solution architecture Proactive, Cross-tier, Transaction Workload Management Management Server single repository analysis tools Web GUI Workload Profiling, Policy Management, Dashboard DTE User Request Transaction Profiles Collected

22. 22 Summary – Business Transaction Tracking is a Necessary Tool for SOA Provides most effective performance management Addresses need for flexibility and change Responds to real-time fluctuations in usage regardless of crunch on resources Help identify new trends in usage and focus IT staff Provides cross-section view by business/transaction Provides most comprehensive performance management Visibility across all tiers Visibility beyond SOA borders

23. 23 Q&A OpTier is an innovator in Transaction Workload Management solutions that assure IT business service levels and optimize resources for the enterprise fernando@Optier.com www.optier.com