How to integrate IBM Integration Bus with WebSphere Service Registry and Repository: Part 3: Endpoint lookup scenarios
Marisa Lopez de Silanes 060000JMJ2 Visits (1292)
IBM Integration Bus (IIB) provides out-of-the-box integration with WebSphere Service Registry and Repository (WSRR) through the Endpoint Lookup and Registry Lookup nodes. This article 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.
It is generally accepted that you should never allow direct access to a service provider in a SOA environment. Instead, you should deploy a new virtual service to the Enterprise Service Bus (ESB) which acts as a proxy to the real back end service. Introducing a controlled point of access to the back end service provides several benefits. In its most basic form it achieves loose coupling between the service consumer and the service provider, allowing you to relocate the back end service or modify its interface without necessarily impacting the service consumer. This pattern is commonly referred to as a simple service proxy. It also enables you to introduce service management functionality, for example error handling and alerting, logging, security configuration, traffic management, service charging and performance measurement. These are extensions to the simple service proxy pattern.
This article describes three sample message flows. The first is an implementation of the simple service proxy pattern that dynamically retrieves the endpoint for the real back end service from WSRR at run time. The second extends this pattern to allow for selection between different provider endpoints. The final pattern is another extension that allows service requests to be routed to alternative endpoints in the event of failures when invoking the endpoint originally selected.
To access the full article, see Inte