How to integrate IBM Integration Bus with WebSphere Service Registry and Repository: Part 8: SLA checking using the HTTPRequest node
Marisa Lopez de Silanes 060000JMJ2 Visits (1327)
When a service is offered for reuse within an organization, the provider of the service typically provides a number of artifacts that consumers of the service can use in order to implement client applications or services. These artifacts usually include one or more WSDL or XML schema documents. While these artifacts provide the information required by the developers of a service consumer, they do not provide any information regarding the non-functional, or quality of service (QoS), characteristics that the service consumer can expect from the service.
The Governance Enablement Profile (GEP) provided with IBM WebSphere Service Registry and Repository (hereafter called WSRR) is a complete WSRR configuration profile that contains all of the business models, life cycles, ontologies, and governance policies, that you need in order to quickly get up and running with Service Oriented Architecture (SOA) governance. It enables a service provider to capture the QoS characteristics for a service using Service Level Definitions (SLDs). It also enables the agreements that exist between service providers and service consumers to be represented using Service Level Agreements (SLAs).
The article describes a sample message flow that enforces SLAs defined in WSRR at runtime, to ensure that the service consumer is authorised to invoke the target service. While it achieves the same results as the message flow described in part 5 of this series, Perf
To access the full article, see Integrating IBM Integration Bus with WebSphere Service Registry and Repository: Part 8: SLA checking using the HTTPRequest node