Upload
denis-jones
View
215
Download
0
Tags:
Embed Size (px)
Citation preview
Web Service Management
Course: CS590LInstructor: Lee Yugyung
Project Team:
Mungara Bhavana Venkata Naga Bhava Chaitanya Mallampati
Research Project Final Presentation
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 B2B 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
FrameworkQuery / Transaction Management
SecurityMultiple Services
Platform Compatibility
Cost
Effective
Two-Level Architecture
Yes but failed to explain
Yes Yes NO Yes yes yes
WSM benefits from FLANENCO’s VANROOTS
NO - Yes NO NO NO -CTO/CIO:
web service management in action: customer usage scenario
- - - Yes Yes Yes yes
Webservices: the new generation of application integration
NO - Yes Yes NO - NO
Management security in the world of web services NO yes NO Yes - - Yes
Web Service Management
yes yes yes Yes Yes yes Yes
Proper Management Requirements
• Identification– the static information that uniquely describes a manageable service.
• Availability– Accessibility, whether it can do work in valid and responsive way
• Metrics– to indicate or calculate the health and performance of the service.
• Operations– management-oriented or service specific and part of the business context.
• Configuration– 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 application-
specific management interfaces – MBeans run in an MBeanServer in the local application
environment (the JVM or server running the application). – The MBeanServer 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 ManageableService {
// return an ID string for the service beingmanagedpublic String getServiceID;// return an array of metric names and acorresponding array of valuespublic String[ ][ ] getMetrics;// return an array of config property namesand a corresponding array of valuespublic String[ ][ ] getConfiguration;// return the WSDL document that describesthis interfacepublic String getAdminInterface;// return true to indicate that the service is ableto respond to requests// return false if the service is experiencingout-of-range delayspublic Boolean isAvailable;public String createNewUser;public String getNewVendor;….
}
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
Approach to management: Step-2
Runtime Data Collection (Step-2)
Management Application
Web Service Agent
Web Service Application
ADAPTERSOAP
Processor
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
Approach to management: Step-3
public interface EventCollector {public void deliverEvent (String id, String source, String type,
String severity, String text);
}
Management Application
Web Service Agent
Web Service Application
ADAPTEREvent Collector
Architecture:
Manageable Service Registry
Management Application
Business Service Registry
ClientWSDLWSDL
Management Interface
Business Interface
Service
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/WSABE2003/program/petrone.pdf2. Managing Interaction Concerns in Web-Service Systems Mary Stearns, HP Software & Solutions Operation, Cupertino, CA – USA, [email protected] Piccinelli, Hewlett-Packard Laboratories, Bristol, UK, [email protected]://aopdcs.enst-bretagne.fr/piccinelli-g-webservices1.pdf3. 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.pdf4. 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.pdf5. Using Model-Integrated Computing to ComposeWeb Services for Distributed Real-time and Embedded Applications Nanbor Wang Douglas C. Schmidt
Aniruddha Gokhale Balachandran Natarajan fnanbor,[email protected] [email protected] [email protected] Dept. of Computer Science Dept. of Electrical Institute for Software and Computer Engineering Integrated Systems Washington University University of California Vanderbilt University One Brookings Drive 616E 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.pdf6. 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 SW7 2AZ, UK, Email: [email protected]. http://www.doc.ic.ac.uk/~nfur/iceni/AHM2003/soa.pdf8.http://java.sun.com/blueprints/webservices/using/webservbp3.html9. http://www.infoworld.com/article/04/01/20/HNgridspecs_1.html?standards10.http://www.w3.org/2001/03/WSWS-popa/paper4911. http://www.infoworld.com/article/04/01/09/02TCflamenco_1.html?web12. http://www3.ca.com/Solutions/Collateral.asp?CID=52362&ID=333913. Web Services: The New Generation of Application Integration – Pervasive Solution Sheet14. Management and Security in the World of Web Services By Dmitri Tcherevik Office of the CTO, July 14, 200315. 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 2003http://www.unitn.it/convegni/download/icsoc03/papers/P_Pedro_Alvarez.pdf
Thank you