|
|||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||
 ABSTRACT
IT organizations that manage complex distributed systems are migrating to a service-oriented architecture (SOA) to reduce costs, increase business agility, and improve reliability. A common way to implement a SOA system is with a composition of web services that communicate with a common message format such as Simple Object Access Protocol (SOAP). In this environment, business processes are decomposed into a collection of services that each provide an atomic function. Eventually, these components are tested and proven enough to become reusable and they form the basis for future services or business processes. The collection of these reusable components forms the backbone of the ad-hoc executable service oriented architecture. Presently, a major challenge to operating in this environment is the management of web services throughout a large enterprise. Without a management protocol to control the communication between the services, the SOA system is chaotic and wasteful. To combat this problem, the Distributed Management Task Force (DMTF) created the Web Service Management (WS-MGMT) specification[2]. This paper will detail the WS-Management specification and cite industry best practices when using this specification to bind services and other manageable entities in the service-based architecture. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
The ACM Portal is published by the Association for Computing Machinery. Copyright © 2010 ACM, Inc.
Terms of Usage Privacy Policy Code of Ethics Contact Us Useful downloads:  Adobe Acrobat
 QuickTime
 Windows Media Player
 Real Player
|
|||||||||||||||||||||||||||||||||||||||||||||||||
Pdf