New in DataPower 5.0 is the feature to attach DataPower mediation policies to things in WSRR, and have DataPower enforce these polices. What can such mediation policies say? They "...can express conditions based on traffic management requirements (for example, QoS or SLM policies), routing directives and schema validation, and invoking data translation stylesheet maps". For example, they can say a web service can only be invoked 5 times per second, and to reject any messages which come in over that. The dW article "SOA governance using WebSphere DataPower and WebSphere Service Registry and Repository, Part 1: Leveraging WS-MediationPolicy capabilities
" describes what is possible with mediation policies, how to author these policies in WSRR 8.0, IBM Integration Developer or the DataPower Web GUI.
What this article does not detail is that in WSRR V8.0 you can attach such mediation policies to objects in WSRR which represent the non-functional attributes of a service, either the Service Level Definition (SLD) which describes the service itself, or the Service Level Agreement (SLA) between a service and its consumer. The SLA represents how much of the service a consumer has agreed to use, and so you can add a policy which actually enforces this in DataPower. For example, that a service consumer can only use a service during 9am-5pm weekdays, or only send 10 messages a second.
The new parts of the article, specifically part 3, shows how to use the new WS-MediationPolicy capabilities in WSRR to author specific Service Level Agreements, which you can enforce on the DataPower appliance without manually creating the XSLT or processing rules and actions.
A practical demonstration of the policy enforcement integration is shown in "Using WebSphere Service Registry and Repository V8 and DataPower V5 for service level mediation policy enforcement" which provides a sample web service and instructions on how to register it in WSRR and DataPower, then steps to demonstrate policy enforcement.
This Redbook publication, will show how to create, apply, maintain, enforce, and monitor runtime policies for SOA services using the SOA Policy Pattern. By using an out of the box solution pattern for runtime policy, the user will be able to easily consume and install the products required with pre-packaged scripts for built-in integration between IBM WebSphere Service Registry and Repository (WSRR) as the Policy Administration Point (PAP), IBM WebSphere® DataPower® as the Policy Enforcement Point (PEP), and Tivoli® ITCAM for SOA® as the Policy Monitoring Point (PMP).