Websphere Registry and Repository Overview

What is Governance?

Governance established a level of control over some set of procedures within an organization.

IT Governance:

-Establishes decision making rights associated with IT.

Start with SOA lifecycle – MADM (Model(Gather requirements, model and simulate, Design), Assemble (Discover, construct and test, compose), Deploy (People, Processes, Information), Manage (Manage Application and services, Manage identity and compliance, Monitor business metrics))

Governance & Best practises: Enforce financial transparency, Ensure business and IT alignment, Maintain process control.

What is governance – (first word govern) establishes measurement, policies, and standards that are used to measure and control the process and implementation of IT decisions.

IT governance:

– Establishes decision making rights associated with IT

– Establish measurements, policies and standards that are used to measure and control the process and implementation of IT decisions.

SOA governance:

-Is an extension of IT governance

-Focuses on the lifecycle of services to ensure the business value of SOA.

Governance has two roles:

1. Definition of decision, rights, policies, standards, and controls

2. Enforcement of those policies and standards.

Defining governance means:

-Identifying the processes and the artefacts to be governed

-Identifying the control points and the chain of responsibility

-Identifying the decision rights

-Stating the measurements to be taken

-Identifying the policies to apply and the standards to put into place.

Enforcing governance means:

-Assigning staff to roles

-Executing the processes that enforce policies and standards

-Documenting proper execution of decisions

-Maintaining and monitoring controls

-Tracking and responding the measurements

Governance lifecycle:

Plan – Establish the need for governance

Define – Define the governance approach

Enable – Deploy governance model incrementally, SOA governance manages challenges, Registry and repository needed to enable governance.

Measure – Monitor and manage the governance process

Governance challenges facing SOA adoption:

SOA brings the new emphasis to the governance challenges within organizations:

1. Eliminate “rogue services”

2. Govern services part of SOA

3. Increase service reuse

4. Configure Enterprise Service Bus to execute context

Nature of SOA environment:

Loose coupled, platform independent in an heterogeneous environment.

In well implemented SOA a firm governance environment the functional and non-functional requirements are well defined.

What is a registry?

A registry holds metadata associated with artefacts in the repository

– Documentation

– Application state data

– Development lifecycle state data

What is a repository?

– Store artefacts associated with services:



Governance lifecycle:

1. Plan

– Document and validate business strategy for SOA and IT

– Assess current IT and SOA capabilities

– Define and refine SOA vision and strategy

– Review governance capabilities

– Lay out governance plan

2. Define

– Define and modify governance processes

– Design policies and enforcement mechanisms

– Identify success factors and metrics

– Identify owners and funding model

– Charter/refine SOA Centre of Excellence

– Design governance IT infrastructure.

3. Enable

-Deploy governance mechanisms

-Deploy governance IT infrastructure

-Educate and deploy on expected behaviours

-Deploy policies

4. Monitor

– Document and validate business strategy for SOA and IT

– Assess current IT and SOA capabilities

Service Registry and Repository capabilities (WSRR)

1. Publish

2. Find

3. Enrich

4. Manage

5. Govern

Encourage reuse – Publish + Find

Enable governance – Govern

Enhance connectivity – Enrich

Optimize service performance – Manage

Publish and Find – Encourage reuse

– Find and reuse services for building blocks for new composite applications.

Publish and find the following info:

1. Services

2. Service capabilities

3. Service lifecycle stage

4. Service interactions

5. Service dependencies and redundancies

If a service does not exist:

Development Tool -> Search -> Create Artifacts -> Publish -> Validation -> WSRR -> Search/select service -> Assembly & administration tools -> Assemble -> Publish -> WSRR.

What is stored in WSRR:



-Monitoring data

-Runtime deployments


Service Description Entities:

Physical Documents (WSDL, XML Schema, SCDL. WS-Policy, XML)

Logical Documents (Interface, Operation, Message, Type, Service, Binding, Endpoint)

Concepts (Business apps, Business process, Governed collection, External reference, User-defined by classifications)

Service Description Metadata




RAD, RSA, WID you can Publish and retrieve all artefacts to WSRR. Download WSRR Plug-in.

Dynamic Service Management

– Enhance connectivity – dynamic and efficient interactions among services at runtime.

– Manage dynamic and efficient access to information on services at run time

– identify users and service metadata

– Notifying users of service metadata

– Notify users of change to service artefacts or metadata

– Securely track all the service interactions

Runtime select and invocation interaction:

1. Message

2. ESB invokes selection mediation

3. Mediation retrieves service description for the requested operation from WSRR

4. Mediation also retrieves description for candidate providers

5. Mediation executes.

Optimize service usage and performance

1. Manage service interactions, dependencies, relationships and redundancies

2. Classify services

3. Manage policies for service usage and governance

4. Manage change and versioning

6. Analyze service usage, history and business impact.

7. Promote and encourage optimal service usage.

Built-in relationship management

-WSRR automatically discover relationships between service artifacts and metadata

Manually define relationship between services.

1. Enter relationship name

2. Select query

3. Enter query details

4. Select target entity

5. Classifications link

Configure change notifications

1. Broadcast change notifications to subscribed users

– email


2. Extensible notification framework allow customize events and messages

3. Level of granularity of notifications

Operational monitoring interaction

1. Message

2. Mediation agent

3. Monitor/mediation retrieves the monitoring policy

4. Record operational data

5. ESB continues to work

6. Asynchronously, monitoring apps generate performance health alerts based on operational data.