Our very own Grant Larsen and Dr. Gili Mendel joined forces to deliver a great webcast on Nov 16th, called “Asset Management powered by Jazz”

The topic is oriented around collaborative lifecycle management (CLM) processes and how to use RAM to effectively share or reference CLM assets throughout the organization. Dr. Gili does a free-wheeling demo, so check it out!

Governing, and Tracking the development of Services end to end is not a simple task.

In this movie, Dr. Gili Mendel extends the ALE series (by Derek Baron) and provides a technical perspective on the development of service specification and implementation.

Recently, I’ve received a number of questions about how to enforce Asset Categorization. For example, you may want to require the following categorization before the asset can be approved:

NOTE: If the images appear fuzzy, just click on them to get a clearer view.

The first place you might look is the Asset Type Constraints :

And since there is no section on categorization constraints, there appears to be no control.

You may have noticed the tab supporting automatic categorization, which is a cool topic I will cover another time.

However, back to the point of this post. RAM provides lifecycle policies to help enforce rules for categorization. These are managed as part of the Lifecycle configuration:

There are two related to Categorization:

These can be set to run at specific states and at certain times, such as when the asset enters a state. Yet while policies might prevent you from changing the state of an asset, they do not prevent you from submitting a new asset to the repository.

The first one can add/remove categories explicitly:

The second can help enforce the rule that a category is selected:

So now, when an asset is created, it can be enforced that categorization must be applied before it can transition to the next state:

1. Someone submits an Asset (the policy doesn’t stop this)

2. When they try to move the state, the policy fails:

You can View results to see why the policy failed:

Lifecycle policies can be very powerful, and with a little creativity you can automate many of your business rules.

In this third installment you’ll learn a little about the Impact Analysis available in ALE, enjoy!

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.

Of course I’m not talking about beer, but rather WSRR ALE (Advanced Lifecycle Edition).

Having just returned from IMPACT 2010, I thought you might enjoy a little mini-series on SOA Governance with our bundle of RAM and WSRR.

Here’s the introduction and part 1, which includes a demo. I’ll continue the series with parts 2-4 so keep an eye out here!

This tutorial covers 2 topics.   The first is XML searching of assets.  Many of the assets customers manage often contain XML artifacts.  RAM indexes a variety of artifacts so you that can search for them based on their contents.   Some examples of the supported artifact types are XML, Microsoft PPT, Visio, Excel, Adobe PDF and many more.  In the versions prior to RAM v7.1.1, you could search on a term like “carlos” and select the search option”within artifacts” and RAM would return all assets that had artifacts that include the term “carlos”.  The challenge is what if there were 100’s of assets that had “carlos”?  In RAM V7.1.1 you can add index rules that will allow you to search by providing additional criteria like find “support person”=”carlos”  where support person is an XML element or attribute that is in the xml artifacts and has the value carlos.    This doesn’t require you to specify an asset attribute but rather an XML element value in the an asset attribute that RAM will look for in an asset artifact.  This is a very powerful feature especially for customers who are using RAM to manage their software models or other XML based assets. This ensures you find the assets you are looking for.

The second topic covered in this tutorial is how to share assets with your supply chain or more broadly.   Most people share assets by sharing the component or document.  What this approach lacks is the context, understanding or common language for how these assets are used, work together or the level of quality or compliance the assets have.  By being able to share the asset governance model that defines how these assets can be used and work together, you add another level of usability and value to the individual assets.  This ensures the assets you provide and receive are consumable and provide value.    RAM v7.1.1 added the ability to create asset libraries.

Watch this tutorial on the Rational Asset Manager Exchange to see how to create XML search rules and package or create asset libraries and their corresponding governance models.  Our hope is customers will begin to create their own asset governance models for different domains like the previous one we have shared for Maven.   Customers can share these asset libraries on the Rational Asset Manager Exchange so that others can jump start their asset management initiatives for different domains within their organization.  We use Maven as an example since this is domain where we have some customers using RAM to visualize and govern their maven component dependencies .