Combining IBM Integration Bus with WSRR (WebSphere Service Registry and Repository) enables message flows running in IBM Integration Bus to access the metadata associated with services registered in WSRR. This enables dynamic connectivity between service consumers and service providers.
IBM Integration Bus can also dynamically retrieve resources from WSRR at runtime to be used in message flow processing. This lets you defer decisions about which artifacts you want to use within a message flow until runtime, rather than making the decision at deployment time, avoiding the need to build and redeploy the message flow if the artifacts change.
For example, you do not need to predefine target endpoints in your message flow, because they can be retrieved dynamically from WSRR at runtime. Therefore you can deploy a message flow and govern its routing and transformations dynamically by updating the service metadata in WSRR.
For more information about combining IBM Integration Bus with WebSphere Service Registry and Repository (WSRR), see the following article series on IBM developerWorks. This article series shows you how to integrate the two products, and provides samples that address several significant business problems.
Part 1 describes a number of IIB/WSRR integration scenarios, shows you how to configure IIB to communicate with WSRR using a number of different nodes, and describes resources that will be used in Parts 2 through 9 to demonstrate IIB/WSRR integration capabilities.
Part 2 describes the Endpoint Lookup and Registry Lookup nodes in detail.
Part 3 shows you how to use the Endpoint Lookup node to dynamically retrieve service metadata from WSRR and use this metadata to route service requests at run time, including the ability to route around problem endpoints when an error occurs.
Part 4 shows you how to use the Registry Lookup node to dynamically retrieve XSL transforms from WSRR and apply them to messages in a flow at runtime.
Part 5 shows you how to use the Registry Lookup node to dynamically retrieve service metadata from WSRR, and use this metadata to check that a service consumer is authorized to invoke the target service.
Part 6 shows you how to use the Endpoint Lookup and Registry Lookup nodes to implement a message flow that can act as a service gateway in your SOA environment, analyzing the service request and then querying WSRR to determine how to route the request to the correct service provider.
Part 7 describes the configuration and behavior of the cache used by the Endpoint Lookup and Registry Lookup nodes, including how the cache supports efficient look-up of previously retrieved WSRR artifacts, and how to make this data available to production systems.
Part 8 shows you how to use the HTTP Request node to dynamically retrieve service metadata from WSRR and use it to check that a service consumer is authorized to invoke the target service.
Part 9 shows you how to create and manage IIB Workload Management (WLM) policies in WSRR, and how to use the JMS Input node in a message flow to automatically synchronize policy changes with IIB.