Saurabh.Tyagi 270005CY2K Visits (2016)
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
Saurabh.Tyagi 270005CY2K Visits (2154)
I am sure you have seen multiple download buttons after adding Rational Tokens to existing Token server using the License Key Center, wondering why – please find the details below.
IBM Rational License Key Center captures the activity with the date history. When more tokens are added to the existing server on different intervals, Rational License Key Center records the number of Tokens assigned to the server and the date when it was generated.
This helps you to determine the total number of token to be used during the import of the license key on the server.
For Example: Screen shot 1 will show you how the download page looks on license key center when initially100 Tokens are generated for a given server on the July 3rd 2014.
Now, as and when the requirement for Tokens increases the License key center administrator logs in to the center to add more Tokens
Example: 100 more on a 8th of July, I see 2 download buttons.
What is important here is the date that the key center captures to maintain history of number of Tokens used on different dates. So on the July 8th the license key was generated for 200 Tokens irrespective of which Download button you choose.
Note: The license keys get appended when more tokens are added to the existing server, so ideally there is no difference in quantity between the two download buttons.
Author: Saurabh Tyagi, co-author Edwin Premnath
Saurabh.Tyagi 270005CY2K Visits (4689)
IBM Rational Jazz token license configuration on Jazz team server
Token based licensing is an option, along with floating and authorized user licensing, within the Rational portfolio. Technically, the basis of token licensing is on the traditional floating license mechanism and process. However, when it comes to how the license check out (consumption) works, it has a different behavior.
In a token environment, each product consumes a predefined token value, not a predefined quantity as it does in a traditional floating licensing environment. The license key has a pool of tokens from which the license server automatically calculates the tokens being checked in and out across users and products.
Lets discuss how a token based licensing model can be implemented for Jazz-based products.
Jazz-based products use IBM Rational Common Licensing (RCL) token service provider, which is an extension of the Jazz Team Server (JTS) that forwards token requests to an IBM Rational License Key Server (RLKS). Jazz-based products and non Jazz-based products can share tokens from same pool of tokens.
How to generate Jazz tokens?
Log into the Rational license key center and follow the below steps to get the required Jazz tokens
You can also refer to the technote links below which will guide you in accomplishing this task:
To configure these Jazz based licenses, from a licensing perspective pre-requisites are:
The following picture shows a high level single server topology deployment of RTC using token licensing.
Once you have successfully configured your flexlm license server with token file, you downloaded from IBM Rational license key center (license.dat), Import the Jazz Keys (Jazz.Token.zip file) on the Jazz team server.
Post successful import of Jazz keys on the Jazz team server you will find an entry very similar to the below diagram
The above screen confirms that the Jazz tokens are successfully imported on the Jazz team server and we can now proceed to configure this Jazz Team Server to communicate with the Rational License Key Server that you installed and configured earlier.
In the Floating License Server section of the License Key Management page of your Jazz team server click the radio button next to IBM Rational Common Licensing Token Service to enable the service.
Hover over the icon in the Actions column until you see the edit hover. Click the icon to view the Server Configuration dialogs shown in following picture.
Configure the following two properties in the above dialog:
If the Jazz Team Server is able to connect to the Rational License Key Server, you'll see a green checkmark on the IBM Rational Common Licensing Token Service line as shown in following picture.
Saurabh.Tyagi 270005CY2K Visits (6838)
Most IBM Rational software products require specific license keys in order to use them. They can be downloaded from the License Key Center, Authorized user fixed term license (FTL) Currently, this license type is not available for Rational products based on the Eclipse framework. Note: Licenses generated since October 2010 do not contain FEATURE lines. INCREMENT lines are used. Floating licenses allow anyone on your network to use Rational products while a license is available. The number of licenses that you purchase and register in License Key Center determines the maximum number of users who can use Rational products concurrently. Named-User Floating
Authorized user fixed term license (FTL)
Currently, this license type is not available for Rational products based on the Eclipse framework.
Note: Licenses generated since October 2010 do not contain FEATURE lines. INCREMENT lines are used.
Floating licenses allow anyone on your network to use Rational products while a license is available. The number of licenses that you purchase and register in License Key Center determines the maximum number of users who can use Rational products concurrently.
Named-user license keys act as floating license keys, except during the import process. IBM Rational® License Key Administrator (LKAD) gives you the opportunity to specify a user for each license key. You assign a user to a key by editing the options file ibmratl.opt. The options file locks the floating license key to the user; allowing the user to use IBM Rational products on multiple clients.
How to Import an Activation kit, Please see below,
The Token based license model allows you to buy a certain number of Tokens (or token-based licenses) for a group of entitled products in an organization. If you use a Rational tool that utilizes a token-based licensing model, then the FEATURE/INCREMENT line in the license file will specify the number of Tokens for check out in total. Tokens do not tie to a product. When the applications are closed, the tokens return to the pool for other end users with any token enabled application to use them.
Note: Mixing tokens-based and non-token-based licenses is not a recommended practice. However, you can mix tokens with traditional product floating licenses. The consuming occurs with floating licenses first, followed by the tokens. You can specify the floating licenses and tokens in the same license file for a single license server. You can also separate into different license files or license servers. The floating licenses must precede the token licenses in the license.dat file.
Author: Saurabh Tyagi