Web Services Control

What are the functions required of a Web services control architecture? The diagram just below provides an architectural overview of a solution that meets the requirements described in the Web Services Platform for Management tutorial, while the diagram immediately below that shows an alternate deployment scenario.

Functions Required of a Web Services Control Architecture: Service brokers sit in the message flow between Web service providers monitoring activity and enforcing centrally managed policy.

Web Services Control Architecture: Alternate deployment option placing Active Agent on Web service provider.

This architecture combines the power of centralized visibility and policy management with distributed monitoring and policy enforcement. In this approach, active components live in the enterprise service network, logically positioned between the providers and consumers of Web services. These are called “in-network” components. A centralized management and policy server, working in concert with service registries and identity management solutions, communicates with these in-network components both receiving and sending information. Information received from in-network components includes service performance statistics, alerts and service interdependency information. Policy, in the form of rule sets, is sent to the in-network components. These rules define in-network component behavior – when to raise alerts, how to process transiting message traffic, where to route messages, how to enforce security policy.

The following table summarizes the functionality required of the Web services control architecture:

For More Information

Find out more about how a Web services management solution works with in-network monitoring and policy-enforcement components. Learn more about the essential components of a Web services control architecture. What is SOA governance? Download the free webinar, Runtime Governance