Rational Asset Manager (RAM) improves on some of the features we delivered in September:

  • Supports OSLC based linking, and Eclipse client integration with RTC 3.0
  • Enhances our OSLC for Requirements Management support to include linking Assets with Requirements in Rational DOORS
  • Supports Rational Insight data warehousing and ETL for uber reporting!
  • You can use a policy on your assets to launch an automation project in Rational Build Forge, e.g: when a deploy-able asset such as an EAR get approved, it can automatically invoke an automation project to get it deployed
  • The “modify reviewer” policy has been improved to support configuring collaboration options, and adding user groups dynamically based on your asset attribute
  • Copy attributes between assets
  • … and more!

You learn more about this release on the Rational Asset Manager New and Noteworthy page!

On behalf of the entire team, Happy New Year!

-Derek Baron

Another cup of ALE

May 21, 2010

As promised, here is part II in this mini-series on SOA Governance. In this video, I talk about customizable workflows and demonstrate how it works between Rational Asset Manager and WSRR.

IBM Innovate 2010 Jam

March 26, 2010

I look forward to seeing all of you on March 30, through April 1st at the first annual IBM Innovate 2010 Jam.  At this Jam, you’ll have the chance to tell us how you use IBM solutions to drive innovation.  We want to hear from you!

Register at this link

Today, we released RAM version!

In addition to bug fixes and enhancements, we used this fix pack to begin a new era of transparent community-oriented development for RAM. I’m thrilled to announce Rational Asset Manager (RAM) has joined the Jazz community on jazz.net.

You can learn all about what’s new, and download the product. We invite you to track our progress – your direct feedback is invaluable.

There’s a new article on developerWorks that gives a quick look at the IBM Cloud offering for developers and testers. What caught my eye was the mention of Rational Asset Manager as part of the infrastructure for the cloud environment. I”ll just add that RAM is also available as an image in the cloud environment!

RAM on the Cloud

I just listened to a good podcast from Grant Larsen. He is our Chief Architect for asset management standards and strategies. He was instrumental in creating the Reusable Asset Specification from the Object Management Group, and has been helping Dr. Gili Mendel craft the specification for the “asset management” domain in the OSLC.

Grant has worked with many of our customers, and shares some lessons learned:

  1. Never roll out as a big bang
  2. Use an on-boarding server, a sandbox
  3. Configure RAM with the perspective of the asset consumer rather than the producer
  4. Content doesn’t have to be managed within RAM (link to it, rather than copy it)
  5. Top-down support critical, while allowing for bottom-up acceptance

He goes on to talk about reusable services, approved open source components, and purchased commercial assets. Check it out here!

An image of the Rational talks to you program

This document discusses step by step instructions on how to migrate your development environment to the test environment using IBM Rational Asset Manager to help ensure the quality of your software development.


Agenda for Migrations

  1. Information that needs to be captured from Rational Asset Manager Development Environment before you can start your migration process.
  2. How to capture the Rational Team Concert Development Environment Workflow from Development Environment
  3. How to recreate your Rational Asset Manager v7.2 Development Environment on the Test environment
  4. How to import Library from Development environment to the Test environment

Last month I presented at our Rational Voice Event.   The session covered how to establish an asset governance process in your organization and how to configure Rational Asset Manager to implement that governance process.  This material is intended for an architect, developer, manager or administrator who is implementing Rational Asset Manager, communities, policies and asset life cycles to manage software assets. I thought the presentation would be valuable to other customers who weren’t able to attend the event, so I am publishing it here  RAMDeepDive-Voice

This was the last customer facing session that I have done as the product manager for Rational Asset Manager.   I am pleased and thankful to have brought Rational Asset Manager to market and participated in the product’s and customer’s successes.  The last three years have been a great and rewarding experience.  I  have enjoyed working with the RAM customers and product team.   I have a new  role in IBM.  Derek Baron is the new product manager who will soon be posting articles on the RAM Insider Blog and working with you.

We have been getting lots of questions around how developers and architects can reference open source components, WSDLs or other binaries that are under governance in their workspace?    Dr Gili Mendel recently wrote an explanation on this that I wanted to share with you below.   By referencing the artifacts in the DSL you prevent teams from having to repeatedly copy asset artifacts around or version the same component multiple times in different SCM systems.   This has the added benefit of allowing you to control access to these components and shut them off when licenses expire or the asset artifacts are no longer supported.

“How does the workspace know how to consume one of these linked artifacts, such as an open source component”

Workspace Link to a RAM artifact

When you “drag” an artifact from a RAM repository into your workspace, the RAM plugin brings down the  file to your workspace (so that you can use it disconnected as well), but it marks it as a derived resource.  A derived resource will not be checked in/out a SCM by Eclipse…. similar to a compiled .class file.


The RAM plugin will also create a link (an entry for that artifact in a control file see image below).   This control file (or changes to this control file) will be checked into the SCM.   When another user checks out this file (or changes to this file), the RAM plugin will parse it, and will bring down the artifacts to that users as well.


The build process can use RAM provided Ant scripts, Ant lib. calls, or Java Calls to bring down “linked” artifacts.   These calls look for the rambuildercontrol.xml file and act on it in a headless environment

Traceability when publishing an artifact into RAM

The Eclipse client provides an asset packaging editor that allow you to provide information about the asset (name, description, version….) as well as a collection of resources from your workspace.   When press the submit/update button, the editor will baseline the projects involved (if it is a TEAM based project, like CVS, Rational Team Concert, Subversion, ClearCase….) and publish the asset annotating (the server, baseline id and such) the artifact with the origin’s information.   The build process, as I noted in the demo,  annotated the .ear with a the build id, and a link back to the BuildForge job or other build automation software.

When a user consumes an asset in Eclipse, the Rational Asset Manager plugin will look for these traceability annotation on the artifacts.   If they exist, the plugin will give you the option to attach to the baseline, or the latest stream level.

This week we had the Rational Voice event, where we meet with a select group of customers to discuss our product road maps and do a deep dive on product capabilities.   I wanted to share the slides we presented at the deep dive session on how to define an asset governance model in Rational Asset Manager v7.2 .  In the session we covered what the governance constructs were in Rational Asset Manager and what the best practices are for establishing a definitive software library.   Here are the slides. If you are interested in participating in future Rational Voice events send me an email and I can get you added to our select group of customers that are invited to the event.  carlos.ferreira at us.ibm.com