[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Requirements for Management of Web Services
Hi WSDM-TC Members, As indicated in my previous mail, the writeup on for "Management of Web Services" requirements is attached in this mail. Heather, Winston, Please add this one also to the TC agenda. <<MOWS-Req.txt>> Best Regards, Pankaj Kumar Web Services Management Organization, HP OpenView, HP. Tel: 1-408-447-4571
Requirements -- Management Of Web Services ========================================== This writeup explains the need to have a standard for Management Of Web Services, refereed to as MOWS, and lists basic requirements that should be met by such a standrd. Ref: "Requirements -- management Using Web Services" Why A New Standard for Management of Web Services ------------------------------------------------- Web services use a common middleware layer (Internet) across diverse domains for allowing various parties to exchange data. The most prevalent use of Web services today is between businesses or inside enterprises to carry business processes and transactions. Any such environment should be managed in order to provide the security, usability, and reliability needed in today’s business environment. Hence, use of tools and standards for security, collaborations, process flows, and management are necessary. Currently there is no standard approach to managing Web services. What management vendors can offer is instrumentation at the SOAP end points and intermediaries (e.g. SOAP servers, UDDI servers, etc.). This will provide information about the Web services as they use these applications. However, this management view is incomplete and lacks critical information on the state of the Web service as it is executing and messages are traveling between various end points. For such information, Web services need to become much more manageable. It is quite normal for Web services to span enterprise boundaries. Existing technologies are designed for management of components within an enterprise and are not suitable for Internet wide management. In contrast, Web services present a very good platform for inter-enterprise interaction. Hence, it is only natural to use Web services for managing Web Services. In this light, the requirements for Managing Web Services are essentially requirements for management of web services using web services and hence assume the framework being specified under the requirements of "Management Using Web Services". Requirements ------------ 1. Web Services should be managed using Web Services technology. This implies support for all the relevant requirements from "Requirements -- management Using Web Services" writeup. 2. Should be independnet of any particular middleware implementation to support Web Services. 3. Should allow management of Web Services, Web Services Execution Environment (WSEE), Conversation and Intermediaries as Managed Resources. + It should be possible to query conversations engaged in by a Web Service. + It should be possible to get all Web Services participating in a particular Conversation. + It should be possible to get the WSEE of a Web Service. + It should be possible to get all the Web Services of a WSEE. + It should be possible to get Messages of a conversation. 4. Should allow access to following metrics: + messages (total, successful, failed) processed since a specified time. + response time (average, minumum, maximum) per operation. 5. Should allow start, stop and restart of a Web Service by a Manager with appropriate access rights. 5. Should allow tracking of processing overhead as a message travels from client to intermediaries, from there to the Web Service and back to the client. It should be possible to get information on processing time at each stage. 6. Should support processing of a Ping message by the Web Service for testing purposes. This should also allow estimate of response time for no-processing message time. 7. Support for the Web Services management standard should not introduce large performance overheads in normal processing of requests. 8. It should be possible to support management of Web services that process signed, encrypted, or signed and encrypted messages. 9. It should be possible to manage normal Web Services without requiring additional infrastructure (such as GRID). 10. It should be possible to support management of a Web Service without having a separate Agent. 11. It should support subscription of Web services. ------- xox --------
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]