September 21, 2008

I have been getting lots of questions regarding what product integrations RAM v7.1 supports. Here is a screen shot that shows the integrations. We also have other services assets that provide integrations with Microsoft Excel and Lotus Notes to do batch asset loading of assets into RAM. The Subversion integration for versioning asset artifacts is provided by Clearvision. LDAP integrations include Microsoft Active Directory and Tivoli Directory Server. We include an embedded WebSphere application server with RAM, but also support Tomcat and clustered WebSphere Application servers.

September 21, 2008

We are targeting having a maintenance release v7.1.0.1 for Rational Asset Manager v7.1 by the end of this month. The release primarily targets defect fixes and improvements to performance. Check the support and downloads site for it. Let us know what you like or don’t like about RAM v7.1 and what you would like to see more of.

September 12, 2008

We packed so much capability into the RAM v7.1 which is the latest release of the product that I wasn’t able to squeeze all of it into the 1 hour demo that you can download in today’s post. This demonstration shows how you can create, manage and use both business intellectual assets and technical assets like SOA assets.

September 3, 2008

When people hear the word asset they often think physical assets. I surprisingly often get asked if RAM is primarily used to manage physical assets. While you could use RAM to do that, it isn’t RAM’s primary purpose. RAM’s primary purpose is to manage intellectual property assets related to the process of developing software. These assets are usually the work products from the software development process that you may need to reference or use again for a recurring business or technical need. So an asset could be as course grained as an application or the representation of the application server it is being deployed on. Or as fine grained as components, services, business processes, business rules, Eclipse Plugins, Open Source Jar files or any asset that you want to govern, search, reference or use.

Some good rules of thumb for choosing an asset

1. Is it something you think needs to be governed before others in the organization begin using it or having a dependency on it. Meaning you need role based access controls to the asset, review and approval and perhaps some reporting. Other examples of this include managing the definition and development of an asset across a supply chain. RAM can be used to broker assets between consumers and producers.

2. An asset is something that has some value and has a high likelyhood of being referenced or used for a recurring business or technical problem. Examples include a recent customer who has events that they monitor in their operations environment. They had application down event where their product application was unavailable for 3 days while they figured out how to get the application back up. To ensure that the problem didn’t happen again they wrote an best practice asset that described the process to get the application back up and running. Turns out the event happened again 2 years later but the person who wrote the document had retired. It took the company 1 day to get the system back up because they couldn’t find the asset. With RAM they could have found the asset immediately by searching on an asset with the event description and see all the related solution assets for it.

Some rules of thumb for level of granularity of an asset:

1. When parts of an asset change at different rates of change than the primary asset that the functionality resides in. For example. You may have a business application that doesn’t change that often by has a service which does change often. You would want the service to be it’s own asset with it’s own notification process.

2. Ownership. When parts of an asset are owned by more than one person and their needs to be clear lines of responsibility for funding business support and technical support.

3. Levels of review required. For example if there is a component that requires legal review you may want to separate it out from within the larger application. This simplifies the legal review process by making the asset reviewed 1 time by the lawyers and used many times by the product teams without requiring more review. Usually this implies different levels of review on different types of assets which RAM supports.

Example Assets We have built some very cool capabilities into RAM to allow you to govern all the types of assets I referenced above. I want to leave you with a couple of cool tips on how you can leverage some of the unique capabilities in RAM to manage both technical and business assets.

Eclipse Plugins

Did you know that you can manage your Eclipse Plugins with RAM? Here are the set of assets you would create and the URL you could use to update your Eclipse using a RAM asset. Thanks to Kevin Bauer on the team who documented this.

These steps show you how to create an asset which is the Eclipse Plugin Update site from an asset in RAM. This then allows you to govern Eclipse plugins, their dependencies and provision them right from with RAM.

Training Videos, Podcasts and Webcasts Did you know you can manage your Knowledge assets with RAM. The Rich text description in RAM supports embedding video including Flash Content right within the Asset Description. You simply copy and paste the video by highlighting it on a web page and then pasting it into the asset description. Or for YouTube videos you copy and paste the object code that is on the YouTube video usually immediately to the right of the video. Here is a screen shot of our internal on boarding RAM v7 server that shows an example asset. Notice how it has been customized with the intranet themes and skins.