Designtime SOA Governance

April 22, 2009

This web cast  by Bobby Pham demonstrates how services can be created and governed through their lifecycle using Rational Asset Manager (RAM) seemlessly working with other development tools and runtime tools.   The  service specification starts as work in progress using a source version control system like Subversion where there are many iterations and versions before it is published to RAM as a milestone asset.   Once published to RAM, governance includes asset reviews, notifications and policy validation.   Rational Asset Manager is seemlessly integrated into the tools used by the different roles.    This demonstration is 23 minutes long and includes the use of Rational Rational Software Architect for modeling the service,  Clearvision Subversion plugin for versioning the artifacts, WebLayers for providing policy libraries that plug into RAM and WebSphere Service Registry for service deployment capabilities.

Directions to watch the demonstration.

  1. Download the demonstration zip file.
  2. Extract the contents of the zip file.
  3. Open the file named RAMSOAGovernance.html in your browser

This is a question that customers using a definitive software library often don’t consider when they go to create a new asset.   They often will use what ever is most convenient way to get to an asset.  This posting is to help you realize the implications of choosing one approach or another when creating, modifying or duplicating assets.

Create a new asset version

Do this when you need another version of the asset and still keep older or existing  version of the asset.  For example,  you just released the new GA version of a product, application or jar component.   You create a new version because you don’t want to remove or replace the previous versions of the products that were released and in the repository.  You also want to keep governance, usage metrics and other metadata separate from version to version of each asset.

To create a new asset version:
create new asset version

By creating a new asset version you will get the following benefits. RAM will display and allow you to to navigate and browse to previous and new versions of assets from the asset details. You can also bookmark asset URLs and leave off the version number on the URL which will then always display the latest version of the asset. To get these nice capabilities you should create a new asset version instead of creating a new asset. When creating a new asset version all the previous meta data from the existing asset version will still be available and modifiable in the new asset version.

Create a new asset
Create a new asset when you truely want another asset. For example you aren’t creating a next version of RAM the product but you are creating a new product called RSA. You will get a clean / empty form when you create a new asset.

To create a new asset:
create new asset

Yes you can create a new asset version by clicking on the submit an asset button on the home page. This however should only be used when you are creating a new asset NOT when you are creating a new version of an existing asset.

Modify an existing asset
Modifying an asset will let you edit the existing contents of the asset. You typically modify an existing asset when you want that version of the asset to continue to exist but it requires some additional modifications. These modifications however will replace the existing asset version and not create a new asset version. Until your modifications are reviewed and approved there maybe 2 versions of the asset visible the existing published version and the one that is under review that will replace the published version once it is approved.

To modify an asset:
modifty asset version

Duplicate an asset
Do this when you need to create a new asset and you want to jump start the process of creating the asset by utilizing an existing asset that may already have many of the asset relationships, categories or artifacts you want in the new asset. Customers often create asset templates that can be duplicated by users to expedite asset submission. RAM will automatically create a link in the asset description describing where this asset was duplicated from.

To duplicate an asset:
duplicate asset

A very good article on how the Rational Asset Manager Rich Client can help you create, publish, search and reuse software assets.

A very good overview of the IBM SOA Registries and Repositories Portfolio Overview was recently published on Developerworks by Julie King.