Sharing with you this interesting note I got from Christophe Daly, who is a member of the IBM Install Manager team.
Christopher explains to my customer how to install the CLM 2011 solution on a Linux platform without the root privileges:
If you installing as a non-root user, you need to make sure the non-root (it’s typically called “non-Admin” in IM terminology) version of IM is used.
At the bottom of our launchpad is a checkbox with the label “Install in a shared location for multiple users (requires administrator privileges)“. When this checkbox is checked, we launch the Admin (root) IM and when unchecked we launch the non-Admin (non-root) IM.
If you are not using the launchpad, you can still start either the admin or non-admin IM directly:
- The admin IM executable is named “install” and
- the non-admin one is named “userinst“.
These are in a platform-specific directory under the “im” directory in the downloads.
I hope it will help…
My Jumpstart colleague, Jim Ruehlin, shared with us today some interesting wording rules regarding the Rational Solution for CLM.
I thought it could be good to share them:
The Rational Solution for CLM 2011 (or just CLM 2011) is a solution from Rational. There is no such thing as
A solution in this context refers to a collection of products delivered as applications that run on one or more Jazz Team Servers.
The three products that are part of the CLM 2011 solution are:
- Rational Team Concert 3.0.1
- Rational Quality Manager 3.0.1
- Rational Requirement Composer 3.0.1
Also part of CLM 2011 is a platform and technology initiative:
Each product or platform has one or more applications associated with it:
- Change and Configuration Management (CCM)
- Quality Management (QM)
- Requirement Management (RM)
- Jazz Team Server (JTS)
- Server Admin / Lifecycle Project Administration (ADMIN / LPA)
Each application provides capabilities to one or more products, and are the smallest units of functionality that can be enabled through licensing.
One of the key aspects of a Source Control Manager (SCM) system is to give the possibility to retrieve and restore a previous state of our application. For example, we must be able to rebuild our application to reproduce, understand and fix an issue met by a customer using 2 year old version of the application.
Unfortunately, having access to our 2 years old source code might not be enough to rebuild the application. Actually, today most applications reference frameworks coming from a tiered organization like Open Source projects or subcontractors. These frameworks are generally organized in a set of libraries, for example JAR files, containing the binary code and, sometimes, the source code or the API documentation.
Of course, each of these frameworks has its own life cycle. So, if we don’t recall at some point which version of the framework we were using when we built our application 2 years ago, it might be hard to rebuild the application 2 years later.
Manage framework versions
To fix such issue we have 2 main options:
- Store the framework version number in our own code with the hope that each time we will have to rebuild the application, all framework versions we used to build our application will be available and accessible either on the Internet or the Intranet.
- Store and baseline the framework library files with our source code into the SCM to be sure to retrieve those resources when it will be required.Read More »
If you are looking for some dedicated RTC precondition to check quality rules before delivering any code into a stream, may I encourage you to watch this video then check this page
This year I could not join my buddies at Innovate 2011 so I decided to quietly enjoy the event from my desk:
Watch Innovate 2011 at livestream.com