Web Service Management Research Project Final Presentation Course

Web Service Management Research Project Final Presentation Course: CS 590 L Instructor: Lee Yugyung Project Team: Mungara Bhavana Venkata Naga Bhava Chaitanya Mallampati

Overview • • Introduction Problem Statement Related Work Proposed Solution Implementation Outcomes Future Work Conclusion

Introduction • What are Web services? – A service, any service, can be defined as a software component that can be: • Described in a formal language • Published to a registry of services • Discovered through standard mechanisms • Invoked over a network • Composed with other services • Need for the management of web services? • Is interaction necessary? • Web services are for B 2 B and Business to Consumer application deployment

Problem Description • Web service provide greater interoperability, among systems and among web services, it is difficult to achieve if they deployed inconsistently • Providing one management technology for all web services is not a practical issue. – May work well with. NET and may not with Java or C++ • Interaction between with web service and maintaining SLA is difficult.

Related Work Static / Dynamic Interactions Platform Compatibility Framework Query / Transaction Management Security Yes but failed to explain Yes NO Yes yes NO - Yes NO NO NO - CTO/CIO: web service management in action: customer usage scenario - - - Yes Yes yes Webservices: the new generation of application integration NO - Yes NO - NO NO yes NO Yes - - Yes yes yes Yes Two-Level Architecture WSM benefits from FLANENCO’s VANROOTS Management security in the world of web services Web Service Management Multiple Services Cost Effective

Proper Management Requirements • Identification – • Availability – • management-oriented or service specific and part of the business context. Configuration – – – • to indicate or calculate the health and performance of the service. Operations – • Accessibility, whether it can do work in valid and responsive way Metrics – • the static information that uniquely describes a manageable service. parameters that control how an application operates. can be static (not changeable while the service is available) or dynamic (can change while the service is available without service disruption) Events – Events are messages from the Web service to a management system.

Approach to management: Step-1 Separate Management Interface: • Define the business interface separately from the administration or management interface. • This approach will separate concerns with business interactions and management interactions with the service. • By providing separate service and port in the WSDL document for the management interface provides more targeted publishing of the business and management service ports in the WSDL. • How to achieve this? ? ?

How to Achieve? ? (Step-1) • Publish in Public UDDI registry – Service in WSDL should be categorized as “management” • Publish in Private UDDI registry – Here, management systems, administration utilities, or operator facilities can discover and locate manageable services.

Deployment of service. . • Application Web service publishes events, status, configuration, and metric data specific to its business logic. • Advertises a management object conforming to some management interface standard or to the requirement of a particular management system. • How we can achieve this practically? ?

Example for Java Web Service • Applications use JMX Management Bean which is called as MBean. – An MBean is an object that is accessible via standard JMX interfaces – Provides a developer with the ability to expose applicationspecific management interfaces – MBeans run in an MBean. Server in the local application environment (the JVM or server running the application). – The MBean. Server provides adapters to specific application managers and administration facilities and thus forms a bridge between the application and management system.

Example Code: (Step-1) public interface Manageable. Service { // return an ID string for the service being managed public String get. Service. ID; // return an array of metric names and a corresponding array of values public String[ ][ ] get. Metrics; // return an array of config property names and a corresponding array of values public String[ ][ ] get. Configuration; // return the WSDL document that describes this interface public String get. Admin. Interface; // return true to indicate that the service is able to respond to requests // return false if the service is experiencing out-of-range delays public Boolean is. Available; public String create. New. User; public String get. New. Vendor; …. }

Approach to management: Step-2 Data Collection At Run Time: • Collect data dynamically from execution environment for management. • What type of data need to be collected? ? – – – • Identification Information Availability Metrics Operations Configuration Information Events Information How to collect & send? ? – Using SOAP we can invoke a web service and we can send data

Runtime Data Collection (Step-2) Web Service Application SOAP Processor Web Service Agent ADAPTER Management Application

Approach to management: Step-3 Signal Occurrence of Significant Events: • Collect the events and pass them to management service • Management service handles the event. • Event collector is a reusable service

public interface Event. Collector { public void deliver. Event (String id, String source, String type, String severity, String text); } Web Service Application Event Collector Web Service Agent ADAPTER Management Application

Architecture: Manageable Service Registry Management Application Business Service Registry WSDL Management Interface Service Business Interface Client

Management Service should be. . • • • Queryable Operational Able to generate events Handle Events Within SLA

Challenges Faced: • There are very few papers on web service management when we started. • Understanding management mechanism • Applying general management to web services • Implementing Interface

Outcomes • • A Complete Webservice Management System Capable of “Management with SLA” Suitable for dynamic management Platform compatibility and transaction management capability • More organized architecture

Conclusion & Future Work • • • Assures reliable service Provides automated service Reduces cost Complete Implementation of management system Resource management Management if combined with Grid

References 1. Managing flexible interaction with Web Services, Giovanna Petrone, Dipartimento di Informatica, Universit `a di Torino Corso Svizzera 18510149 Torino, Italy. http: //www. agentus. com/WSABE 2003/program/petrone. pdf 2. Managing Interaction Concerns in Web-Service Systems Mary Stearns, HP Software & Solutions Operation, Cupertino, CA – USA, Mary_Stearns@HP. com Giacomo Piccinelli, Hewlett-Packard Laboratories, Bristol, UK, Giacomo_Piccinelli@HP. com http: //aopdcs. enst-bretagne. fr/piccinelli-g-webservices 1. pdf 3. A Steve Vinoski Toward Integration Column from IEEE Internet Computing Web Services Interaction Models, Part 1: Current Practice Copyright © 2002 Institute of Electrical and Electronics Engineers. http: //www. iona. com/hyplan/vinoski/pdfs/IEEE-Web_Services_Interaction_Models_Part_1. pdf 4. A Steve Vinoski Toward Integration Column from IEEE Internet Computing Web Services Interaction Models, Part 2: Current Practice Copyright © 2002 Institute of Electrical and Electronics Engineers. http: //www. iona. com/hyplan/vinoski/pdfs/IEEE-Web_Services_Interaction_Models_Part_2. pdf 5. Using Model-Integrated Computing to Compose. Web Services for Distributed Real-time and Embedded Applications Nanbor Wang Douglas C. Schmidt Aniruddha Gokhale Balachandran Natarajan fnanbor, balag@cs. wustl. edu schmidt@uci. edu a. gokhale@vanderbilt. edu Dept. of Computer Science Dept. of Electrical Institute for Software and Computer Engineering Integrated Systems Washington University of California Vanderbilt University One Brookings Drive 616 E Engineering Tower P O Box 36, Peabody St. Louis, MO 63130 Irvine, CA 92697 Nashville, TN 37203 http: //www. cs. wustl. edu/~schmidt/PDF/webservices. pdf 6. Implementations of a Service-Oriented Architecture on top of Jini, JXTA and OGSA, Nathalie Furmento Jeffrey Hau William Lee Steven Newhouse John Darlington, London e-Science Centre, Imperial College London, South Kensington Campus, London SW 7 2 AZ, UK, Email: lesc-staff@doc. ic. ac. uk 7. http: //www. doc. ic. ac. uk/~nfur/iceni/AHM 2003/soa. pdf 8. http: //java. sun. com/blueprints/webservices/using/webservbp 3. html 9. http: //www. infoworld. com/article/04/01/20/HNgridspecs_1. html? standards 10. http: //www. w 3. org/2001/03/WSWS-popa/paper 49 11. http: //www. infoworld. com/article/04/01/09/02 TCflamenco_1. html? web 12. http: //www 3. ca. com/Solutions/Collateral. asp? CID=52362&ID=3339 13. Web Services: The New Generation of Application Integration – Pervasive Solution Sheet 14. Management and Security in the World of Web Services By Dmitri Tcherevik Office of the CTO, July 14, 2003 15. Web services management approaches by J. A. Farrell H. Kreger IBM Corporation, 16. CTO/CIO : Web Service Management in Action: Customer Usage Scenario[13] 17. An architectural pattern to extend the interaction model between Web-services By P. Álvarez, J. A. Bañares, P. R. Muro-Medrano Trento, 15 -18 december 2003 http: //www. unitn. it/convegni/download/icsoc 03/papers/P_Pedro_Alvarez. pdf

Thank you