Building SOA portfolio Business Services, part 11th: Implementing the Subscriber authorization process

The previous article in this series provides an overview of how Ibm®websphere®service Registry and Repository and IBM WebSphere Process Server are used for service consumption governance. This article describes some implementation details to show you how to customize the WebSphere service Registry and Repository to support service consumption governance, how to implement the Subscriber authorization process using WebSphere process Server, and how to use The SOAP interface integrates it with the WebSphere Service Registry and Repository.

Overview

The WebSphere service Registry and Repository is a services Meta Data Registry and repository. It establishes a central point to find and manage service metadata that is obtained from the source. An example of service metadata is the cost and response time negotiated beforehand between the service provider (SP) and the service Subscriber (SS). The WebSphere service Registry and Repository has a large number of aspects that can be customized for service providers. For example, you can use the XML schema to define the WebSphere service Registry and Repository templates to represent service provider-specific contract information. Alternatively, you can use Web Ontology Language (OWL) to define classification levels to associate different WebSphere Service Registry and Repository entities. The WebSphere Service Registry and Repository also provides a wide range of customization capabilities for its UI. A perspective that corresponds to the user's organization role can be defined in the Web UI to provide a custom view of the service metadata. The WebSphere Service Registry and Repository provides the ability to add acknowledgement and notification plug-ins to implement custom behavior to respond to changes in the repository's content.

The WebSphere process Server is a container for Business process Execution Language (BPEL) workflows. A business process written in BPEL can be exported as a Web service and accessed by other applications; one example is the WebSphere service Registry and Repository that uses the SOAP interface. You can integrate the WebSphere process Server with the WebSphere service Registry and Repository to perform workflows in response to stored in the WebSphere service Registry and R The state change of the metadata in the epository. As shown in Figure 1, the BPEL process in the WebSphere process Server can be passed by the WebSphere service Registry and Repository through the WebSphere service Registry an D Repository the user-defined notification plug-in to invoke. The BPEL process can, in turn, create or update information in the WebSphere service Registry and Repository using the WebSphere service Registry and Repository SOAP APIs.

Figure 1. WebSphere Process Server and WebSphere Service Registry and Repository integration points

This article describes how to set up the WebSphere Service Registry and Repository and integrate it with the WebSphere process Server to implement the subscriber authorization process described in the previous article.

Set up WebSphere Service Registry and Repository

You can implement the following WebSphere service Registry and Repository customizations by adding templates, classifications, roles, or perspectives to the WebSphere service Registry and Repository. The following sections describe the customization details.