It's an RTC love-fest today! Hot off the reporting presses here in Rational Support, here are the top fifteen technotes used in March to help solve the Rational Team Concert PMRs you reported. As always, these are taken directly from our PMR reports and tabulated to help you solve the same issues which you may be encountering:
Jazz LICENSING : Exploring Rational Team Concert
Rational Team Concert has a simple set of defined roles to enable key solutions for your organization. With Rational Team Concert you simply acquire licenses to support the roles and solutions that you are interested in. This provides you with an unprecedented level of flexibility and cost efficiency to choose and use only what you are interested in to support your needs. Rational Team Concert allows you to implement individual components of RTC now and others later simply through licensing - and without your typical deployment and integration headaches and risks.
When you purchase a role-based license for IBM Rational Team Concert you will have read, write, and comment access to some or all of the capabilities of the Change and Configuration Management application. In addition, there are three types of Developer client access licenses.
Client access licenses:
With a role-based licensing scheme, when you purchase a client access license for a particular role you will have read, write, and comment access to some or all of the capabilities of the Change and Configuration Management application.
You install the client access license activation kits in the License Key Management section in the Administration page of the Jazz Team Server. You assign the licenses to users in the Client Access License Management section of Jazz User Administration. See Installing and managing license keys for instructions.
Role-based client access licenses:
Configuration Management application.
Functional user licenses:
Developer Client Access Licenses:
Once a Jazz Team Server is installed, you may install additional license keys in the License Key Management section in the Administration page of the Jazz Team Server
Author: Saurabh Tyagi
Author: Saurabh Tyagi
Jazz.net is live with a completely reworked and improved website
The new Jazz.net site includes the addition of Rational Requirements Composer, Quality Manager, and Focal Point for Project Management. We have done what you asked for and made much more of our Jazz Development open and transparent. Now clients and community members will be able to enjoy the benefits of transparent development but no longer just for Rational Team Concert. Now you can participate with us in shaping plans, prioritizing fixes, and interacting directly with our expanding Jazz Development Team for three new Jazz Products. See http://jazz.net/ for the complete details
eGuide now on Jazz.net
IBM Rational support has taken all the best links from our RSDC eGuide mini-CD and posted them online at http
Check it out!
Rational Team Concert education modules in IBM Education Assistant.
IBM Education Assistant is a collection of multimedia educational modules designed to help you gain a better understanding of IBM software products and use them more effectively to meet your business requirements.
Please check them out and let us know what you think ... either via the feedback mechanism at IEA or by leaving a comment here.
Many thanks to Steven Jin and Pam Barnard!
Arun K Sriramaiah 2700076GE8 Visits (416)
This article explains how to reduce the number of Rational Team Concert component flow displays in the pending changes window.
By default, all components in a Repository workspace (RWS) use the current flow target. You can use the Repository workspace editor to add flow targets or change their scope so that not all components use them. Refer to Flow targets for further details.
For example, you can specify in flow targets for some of the components in a Repository workspace (RWS) display, or decide that a specific component must display in pending changes window.
Note: You can use the Flow Only components checked below option in RWS\Stream Flow Target to make the Pending Changes view more manageable. This helps more when streams or workspace have 10++ and which might not be all needed in the pending changes window.
You can use the above scenario where in you can avoid unwanted components display in the pending changes.