220 likes | 373 Views
Web Services Navigator: Visualizing the Execution of Web Services. Gerett Commeford & Dariusz Grabka M.Sc. Candidates, University of Guelph Tuesday March 6 th , 2007. Outline. Part 1: Presentation Purpose What is Web Service Navigator? Data Collector Main Components Architecture
E N D
Web Services Navigator: Visualizing the Execution of Web Services Gerett Commeford & Dariusz Grabka M.Sc. Candidates, University of Guelph Tuesday March 6th, 2007
Outline • Part 1: Presentation • Purpose • What is Web Service Navigator? • Data Collector • Main Components • Architecture • The Interactive Viewers • Practical Implications of the Technology • Conclusions • Part 2: Discussion Web Services Navigator
Purpose • To allow developers and managers to understand, debug, and optimize web services • Componentized vs. Service-Based • Vertical vs. Horizontal • How can we deal with this horizontal complexity? Web Services Navigator
Web Services Navigator • Relies on Data Collector for IBM Web Services to capture events • Correlates events • Models transactions • Extracts patterns • Produces visual abstractions • More meaningful to humans Web Services Navigator
Data Collector • The heart of Web Services Navigator • Logs the content and context of SOAP messages sent and received by applications • All logs can then be imported into Web Services Navigator • Web services transaction flows are reconstructed • Recurring patterns are identified • Explored using 5 interactive views Web Services Navigator
Web Services Navigator • Three main components • The log parser • The event analyzer • The interactive viewers • Service topology view • Transaction flows view • Flow patterns view • Statistics table view • Message content view Web Services Navigator
Architecture Source: De Pauw et al. Web Services Navigator: Visualizing the Execution of Web Services Web Services Navigator
Service Topology View Source: De Pauw et al. Web Services Navigator: Visualizing the Execution of Web Services Web Services Navigator
Transaction Flows View Source: De Pauw et al. Web Services Navigator: Visualizing the Execution of Web Services Web Services Navigator
Flow Patterns View Source: De Pauw et al. Web Services Navigator: Visualizing the Execution of Web Services Web Services Navigator
Statistics Table View Source: De Pauw et al. Web Services Navigator: Visualizing the Execution of Web Services Web Services Navigator
Message Content View Source: De Pauw et al. Web Services Navigator: Visualizing the Execution of Web Services Web Services Navigator
Practical Implications • Visualizing problems in business logic • Verifying workflow choreography • Detecting incorrect implementation of business rules • Detecting excessively chatty communications • Verifying application cost structure Web Services Navigator
Practical Implications • Visualizing problems in IT layers • Semantic errors • Transaction bottlenecks • Unavailable resources • Syntax errors Web Services Navigator
Conclusions • Bridge conceptual gaps between business and IT specialists • Five linked views cut through horizontal complexity • Visualizing without modifying • Improved communication between user groups Web Services Navigator
Part 2: Discussion • The Paper • The Application • Visualization Techniques • Statistical Information • Product Testing Web Services Navigator
Discussion: The Paper • Exploratory research based on single tool • Loose focus of many elements of work • Development, rather than research • Structure of paper • No clearly defined hypothesis • Background information too late in paper • More information on competing products • Too light identifying flaws • Diagrams do not focus on a single example Web Services Navigator
Discussion: The Application • The application itself • Plug-in for Eclipse • A tool for developers • Run time integration not detailed • Support for other development platforms? • Clock skew methods are well-worked • Light on the pattern extraction details • Assumptions about execution patterns of WS Web Services Navigator
Discussion: Visualizations • Visualization techniques • Five views seem very complete • Transaction Flows view impractical • Further development required • Isolating “exceptions” to patterns • Execution view that visualizes time information • Time key to identifying performance issues Web Services Navigator
Discussion: Information • Statistical information • Visualizing other information: averages, standard deviations, etc. • Function usage, parameter usage • Filtering transactions out of views Web Services Navigator
Discussion: Testing • Testing techniques • Usability analysis? • Expert vs. Non-expert Usage • Usability of edge-based view Web Services Navigator
References De Pauw, W., Lei, M., Pring, E., Villard, L., Arnold, M., and Morar, J. F. 2005. Web services navigator: visualizing the execution of web services. IBM Syst. J. 44, 4 (Oct. 2005), 821-845. De Pauw, W., Krasikov, S., and Morar, J. F. 2006. Execution patterns for visualizing web services. In Proceedings of the 2006 ACM Symposium on Software Visualization (Brighton, United Kingdom, September 04 - 05, 2006). SoftVis '06. ACM Press, New York, NY, 37-45. DOI= http://doi.acm.org/10.1145/1148493.1148499 Web Services Navigator