Saurabh.Tyagi 270005CY2K Visits (2018)
IBM Rational Synergy is a task-based, software configuration management (SCM) solution that brings together global, distributed development teams on a unified platform. Rational Synergy provides capabilities that help software and systems development teams work and collaborate faster and easier.
Rational Synergy is licensed using IBM Rational Common Licensing. For information about Rational Common Licensing, see the Rational Common Licensing information center.
Rational Synergy supports the Floating, Named-User Floating, and Token license types. For a description of license types, see “License type definitions” in the Rational Common Licensing information center.
For Rational Synergy users, the login name is seen as the user of the token license. To reserve Named-User licenses for specific users, see “Setting up the options file” in the Rational Common Licensing information center. When configuring the options file for Rational Synergy and Rational Change, it is not necessary to put the default administrative users (ccm_root, ChangeAdmin, and csuser) in the INCLUDE list. The license file includes additional floating licenses for these users. Do not assign these licenses to other users because the products might fail.
How licensing works with Rational Synergy:
When you start Rational Synergy, it contacts the License Manager to request a license. Rational Synergy uses information that was provided during the server installation process to find the License Manager. The following example describes how licenses are configured during installation. The example assumes IBM Rational Common Licensing was installed before installing Rational Synergy.
-> When you install the Rational Synergy server, you are prompted for the host name and port number of the license manager. The information is recorded in the $CCM
-> When the Rational Synergy router process is started, it reads the license information from the $CCM
-> When a Rational Synergy session is started, the information about where to find the license manager is passed from the router to the Rational Synergy server. The Rational Synergy server also looks in the TELE
The Rational Synergy server contacts the license manager using the specified host and port, and requests a license on behalf of the user. The $CCM
Rational Synergy searches for license servers and license files in the following order:
If you move the license manager to a different system, you must edit the $CCM
Operations that consume Synergy license:
Starting a session does not consume a license. Only operations that update the underlying database consume a license, such as file check out, task creation, task completion, and so on.
Synergy license timeout
After a license is consumed by a user, that license is reserved for that user for 60 minutes after the last database update while the session is running. If the user exits the session, the license is released immediately.
License usage during integration:
Some Rational Synergy integrations hold a license for the duration of time the user is running the integration. Source-code related operations performed through the integration can then be updated in the database. In this case, the user can exit the visible session, but the integration is still running a session behind the scenes on behalf of the user
Rational Change supports the floating, named-user floating, and token license types.When you install Rational Change, the license server information (port@host) is requested and persisted to the file CHAN
There is a 30 minute minimum use time when Rational Change checks out a license. When a license is checked out, it stays checked out for at least 30 minutes, whether there is activity from the user. If the user exits or is inactive after that, the license is released.
Co-Authored by: Saurabh Tyagi and Pankaj Sharma
Different Types of reports in the RLKS Admin and reporting tool:
Reports display valuable statistics about how users are using the assets and repository.
Managing software assets goes beyond submitting them to a repository and managing them through consumption. Over time, looking at the changing elements, the models and trends of asset details, consumption use cases, and users information can help companies evaluate the needs of their current business strategies.
Lets understand the different types of reports available and the insights they provide...
Peak usage : This metric represents the maximum number of license requests that were granted by the selected license servers for the selected products. If more than one license type is selected in the report definition (floating and token as license type), the peak usage report shows multiple numbers in the bar graphs. The following example shows a peak distribution report with two counts per bar.
Peak denial : This metric represents the maximum number of license requests that selected license servers denied for the selected products during the specified time.
Note: In certain reporting scenarios, the tool can report inaccurate license denials. For more information, see the "Known limitation in license denial report" technical document.
License usage per user : This metric presents information about product usage by a user from a license server at a specified time. This list includes the user and the host server name for the selected products for the specified duration.
Available Licenses : This metric presents the total number of licenses for a product that are available in the license files that are used to start the license server.
License expiration : This metric presents the expiration date of licenses for each of the selected products. This information is collected from the license file.
Token distribution : This chart presents the number of token licenses that are issued in the specified time for various products in an organization.
Chargeback report : This metric represents a simple chargeback policy for product licenses that are used in an organization. The report for this metric is like an invoice, where the number of licenses that are used by each user during a specified time is listed. The number of license hours is multiplied by the unit costs that are associated with each license hour of that kind of license for that product. This product gives the value in currency to be charged for that user.
Note: For the Collaborative Lifecycle Management (CLM) products, the following metric types are supported:
Shijesh Velayudhan 270004VGUQ Visits (3332)
License Usage Order
IBM Rational products requests licenses in a specific order. In an organization we may have combination of authorized user, floating, suite, point-product licenses in the environment, it is essential that we understand the license usage order.
Now let’s try to understand the license usage order. An IBM Rational product that users IBM Rational Common Licensing will request the license in the following order.
For version 7.0 of IBM Rational products, the license key usage order has changed. In releases before 7.0, when a Suite product was being installed, the Rational License Key Administrator (LKAD) application would first try to find a license key corresponding to the Suite. If the Suite key was not available, LKAD would then look for a key corresponding to the product that was running.
The table below describes the license usage order for each IBM Rational Product that uses IBM Rational Common Licensing.
Now let’s check how to change the license usage order. Any changes made in the license usage order can be reversed to previous setting by clicking the "Restore to Defaults" in the license usage mapping window.
To change the license usage order:
The license usage order that you set on your computer is tied to your user ID. If different users log in to your computer with their own user IDs, the license usage order that you may have changed resets to the default order. The new users can set the license usage order for their user IDs. Their settings do not affect your settings.
Jazz team server has a detailed reporting mechanism for the floating license usage and these reports can be very helpful in managing the available floating licenses effectively. The reports give a picture of license consumption in a given time frame. This not only helps you to manage your licenses but also provides a big picture about your license requirements for a project.
There are two ways to collect data about the license usage on a license server:
* Historic usage snapshots - Data that tracks how many of each CAL were used concurrently over time.
* Full license usage log - Exactly which users used which CALs and for how long.
Historic usage snapshots
By default, the license server will collect basic license usage data and store the data as historic snapshots. The data collected is only how many of each Client Access License, CAL were used, and by which server. That data is used to generate the graphs provided by the admin web UI.
You can see the admin web UI graphs by going to this URL, http
Load the admin web UI of the license server, usually http
Three ways of monitoring the license usage on the web UI:
1. Click the server tab and in the licensing pane, Click reports.
2. On the floating license usage page, select a license type from the menu.
3. Optional : Enter values in the start date and end date fields.
4. Click on the "Reports" link in the "Floating License Usage" section of the left navigation area.
The page to obtain the floating license usage looks like this:
In below given scenario:
We are running the reports for the IBM Rational Quality Manager – Quality Professional – Token licenses from September 1st to September 10th.
Further the details about the license denial's if any also would be present in the logs.
In below provided image, It is clear that the consumption of the tokens is high from 09/09/2012 to 09/12/2012.
You can also get access to the raw data through the generic reporting UI by doing the following:
View the report UI in the web by going to http
Full license usage log
To use the full license log, you must first enable it through the admin web UI. You can do it through the following steps:
After the license log has been enabled a file will be generated for each license action that happens on the server. Here is an extract of a sample log:
The meaning of each column is: