Chapter 2. WebSphere ESB Registry Edition solution overview 23
WSRR adds value throughout all phases of the SOA life cycle:
Model and Assemble phases
WSRR is used to locate the copies of record of candidate service interaction
metadata or intermediaries and policies that govern the interactions. WSRR
can also be used to publish and govern service metadata about emerging,
to-be-deployed services.
Deployment phase
WSRR provides the system of record for metadata that describes service
interaction endpoints. It is populated with metadata as part of SOA solution
deployment or through the discovery of existing endpoints.
Manage phase
Operational management and resilience in the SOA is enhanced by sharing
the service metadata that exists in WSRR with operational data stores.
2.1.2 WSRR technical architecture overview
WSRR is a Java Platform, Enterprise Edition application based on the Java
platform and associated platform services that are provided by WebSphere
Application Server. WSRR uses a relational database as a store for service
metadata (for example, IBM DB2® or Oracle).
The registry and repository component provides basic service metadata storage.
It also provides update and retrieval functions that support Create, Retrieve,
Update, Delete, and Query capability for service metadata that is stored in the
database according to the WSRR content model.
24 Smart SOA Solutions with WebSphere Enterprise Service Bus Registry Edition V7.5
Figure 2-1 illustrates the key components of WSRR.
Figure 2-1 WSRR key components
The following sections describe the key components and functions of WSRR.
Registry and repository
WSRR functions as both a registry and a repository.
The repository allows users to store, manage, and query content of documents
that hold service metadata descriptions (WSDL, XSD, WS-Policy, SCDL, or XML
documents). The repository stores the documents that contain service metadata
and also provides a fine-grained representation of the content of those
documents (for example, ports, or portTypes in WSDL documents).
The repository also provides registry functions for populating registered service
declarations and elements of the derived content models with user-defined
properties, relationships, and classifiers. A rich query interface uses these
user-defined attributed when users want to find a service endpoint, interface
description, or other metadata about a service.
Chapter 2. WebSphere ESB Registry Edition solution overview 25
WSRR allows users to plug in validation, notification, and modification functions
that are run when changes are made to the repository content (for example,
checks for completeness of a service definition). It also provides notifications of
any changes to the content of the repository and allows users to register their
interest in consuming those notifications.
WSRR includes a default notification handler that publishes change events on a
JMS topic. The event specifies the type of event (create, update, delete, or
transform), the artifact impacted (identified by its URI), and a few more bits of
information about the artifact. To avoid access control issues, the content of the
artifact is not shipped with the event but is retrieved separately.
User interfaces
The following user interfaces are provided to access WebSphere Service
Registry and Repository:
A web user interface
An Eclipse plug-in
A Business Space user interface
The main interface is a web application that is deployed with the WSRR run time.
This servlet-based web user interface is the main way for users representing
different roles to interact with WSRR. It supports lookup and publish scenarios,
includes metadata management and analysis scenarios, and provides functions
that support SOA governance, including import/export and impact analysis.
The web user interface supports customization of the views on the WSRR
content that is represented to a user. A set of user interface definition files
describes content and layout of the various components that make up the WSRR
web interface. The concept of user-role-specific perspectives is supported.
WSRR comes with a set of predefined perspectives for the most common user
roles, but WSRR users can customize the predefined roles or create role-specific
perspectives.
The web user interface also provides administrative functions that allow users to
customize the components that control the configuration of the WSRR system,
manage access control, and create and modify classification systems.
A subset of this user interface is offered as WSRR Studio, an Eclipse plug-in, to
meet the needs of developer and analyst roles that use Eclipse-based tools. The
Eclipse plug-in is used primarily for performing lookup, browse, retrieve, and
publish tasks. The web-based user interface is used for performing service
metadata management and governance.
The Business Space user interface is a browser-based interface that provides
widgets that allow you to search, view details of items in the registry, perform key

Get Smart SOA Solutions with WebSphere Enterprise Service Bus Registry Edition V7.5 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.