How to integrate IBM Integration Bus with WebSphere Service Registry and Repository: Part 9: Workload Management policy integration
Marisa Lopez de Silanes 060000JMJ2 Visits (1678)
IBM Integration Bus (IIB) version 9.0 introduced the ability to control the rate of processing within a message flow by attaching WLM policies to the flow. After a WLM policy is attached to a message flow, IIB modifies its behavior to ensure that it complies with the policy. This can be performed dynamically at runtime, enabling policies to be attached to and detached from message flows without restarting the execution group or the individual flows.
WSRR is a central point of reference for service metadata in your SOA, and is a key part of a successful SOA implementation. The service metadata that can be registered or stored in WSRR includes service definition documents such as WSDL, XSD and policy documents. By using WSRR to centrally manage and govern policies, as well as services, you can ensure that policies are applied consistently across your SOA.
The article Integrating IBM Integration Bus with WebSphere Service Registry and Repository: Part 9: Workload Management policy integration describes a sample message flow that uses JMS Input nodes to listen to policy related events from WSRR. It responds to these events by automatically synchronizing those policies with IIB, including attaching them to message flows in response to WLM policies being attached to services in WSRR. The message flow also makes use of an HTTP Request node to invoke the WSRR REST API in order to retrieve the WLM policies from WSRR. To demonstrate this flow working, this article also describes how to use the new WLM policy authoring capabilities that have been introduced in WSRR V8.5 to allow you to author IIB WLM policies directly in the Service Registry Dashboard.