IBM Software Group

Accelerating Solutions

IBM Software Group2

Deployment KeyBank would like to modify RAM lifecycle to govern their process stages of Idea,

Pending, Active and Contained Want maximum automation to reduce manual steps Plan to use RAM lifecycle as governance owner and only have minimal

involvement in WSRR i.e. specification so WSRR is only used deployment Initially 3 roles – EA Governance, Developer, Business Analyst Will have a Web Service and Non-Web Service flow

WS review can be an automated review by validating WSDL etc Non-WS review will be a manual review since no WSDL

KeyBank would like to consolidate all information about a service in 1 tool for each type of user

A full production deployment consists of multiple registries They support the various stages of the service development and testing life cycle. You can keep the service metadata for your testing and staging environments in separate

registries to mirror more effectively what will happen when a service goes into production. All governance operations are performed on the service in the governance registry

The WSRR promotion feature is used to promote a copy of the service to the next runtime staging registry

IBM Software Group3

Registries Types

Registry Description

GovernanceDevelopment teams share access to the content in this registry, typically segregated according to department. All discovery, development, and governance operations are performed here

Runtime staging There is one registry for each staging environment; for example, integration, acceptance testing, pre-production. Runtime staging registries are described in more detail later in this topic.

Runtime production

A limited set of content from the governance registry is promoted to this registry as and when services are ready to go into production, using the WSRR promotion feature. Typically, users do not work directly with this registry, and content is mostly read-only, although additional metadata might be added to registry content, to support ITCAM for SOA for example. Instead, users work in the governance registry, and content is promoted automatically to the runtime production registry at the appropriate point in the governance life cycle.

This registry is used for business runtime access.

The registries are described in the following table:

IBM Software Group4

Deployment Option

RAM

Production

WASInfrastructure

IT

QV

App CodeDeployment

WSRRGovernanceServer

PromotionOption

Auto Sync

Manual

Manual

ITCAMsFor SOA

TAM/LDAP

Run TimeEnvironments

WSRRRuntimeServers

DataPower

IBM Software Group5

Thank You