All products previously known as Telelogic, are now known under the IBM Rational brand name.
On June 2, 2009, all 18 "Telelogic" products were renamed to "IBM Rational". You will see this change reflected on the various product support pages and in DCF. Please note the URLs have remained the same, so you can still obtain the support you need from the same locations on ibm.com.
IBM Rational Telelogic product-specific support pages on ibm.com
Visit our Telelogic support overview site - http
Saurabh.Tyagi 270005CY2K Visits (1781)
Depending on the complexity of work and projects associated with your organization, complexity of your environment also increases invariably. Your environment might include several tools to assist you in doing your daily job and this may include several products which fall under different category. For example : Change management, Requirements management, modeling tools, testing tools, development tools and so on.
These products may be Rational or Telelogic, Which falls under IBM Umbrella.
You might have to work with both Rational and the Telelogic products and you may very well be the license administrator and your areas of interest may include both Rational and Telelogic product licensing.
Though we have Rational and Telelogic products under the same Umbrella today IBM, there is a difference in the way the licensing works for Rational and Telelogic products.
We will unearth these differences in the working mechanism of the licenses for Rational and Telelogic products and try to understand how they work.
The following section briefs the working of Rational licenses and also throws some light on difference types of licenses available for Rational products
Floating licenses for Rational products are not tied to any version of the product. Floating licenses are always configured on a centralized Rational license key server and the clients are pointed to this license server to pick the licenses.
The scenarios where you are upgrading the client to a different version.
For example: If you are migrating the Rational software architect from version 7.0 to version 8.0 there is no need to update the license file as the floating licenses which you had configured to work with Rational software architect 7.0 will still work with Rational software architect version 8.0 as they are not specific to any version of the product.
But It is always recommended to have a version of the Rational license key server which was released post the release of the product.
Rational products also have authorized user licenses which are tied to a specific host and need no license server, Even authorized user licenses for a Rational product is not specific to any version.
Activation kits are available for SDP (software delivery platform) products (Rational) and only activation kits are specific to the version of the product and they need to be imported on the Installation manager.
Refer to the link below on how to configure an activation kit on Installation mana
Now as we have an understanding of how the licenses work for the Rational products, we will try to understand how the licenses work for the family of products previously known as Telelogic and what are the different Telelogic products which are available.
The below sections will give us a complete understanding of how the licenses for Telelogic products works.
Only for TELELOGIC family of products floating licenses and Authorized user licenses are not version independent and Telelogic products don't have the concept of activation kits.
Whenever the client or the product is upgraded we also have a need to update the license file to ensure that it has appropriate maintenance renewal to support the newer version of the product.
TELELOGIC family of products works on Date based concept of licensing and your license file will have a maintenance end date in it and only product versions released prior to that maintenance end date which is specified in your license file will work and any version of the product which was released post to the maintenance end date will not work.
For Example: If you have Rational Doors floating license file with an maintenance end date of 2010.01.01 (JAN-01-2010) this will not work with Rational Doors version 9.5 as Rational Doors version 9.5 was released post 2010.01.01 (JAN-01-2010).
To understand this concept of Date based concept of licensing in clear refer to the white paper link below on Understanding date based concept of licensing: http
Also refer to the link below on how to apply the maintenance renewals for the Telelogic family of products: http
Find the list of TELELOGIC products below and as mentioned they all work on date based concept of licensing.
→ IBM Rational Dashboard
→ IBM Rational DocExpress
→ IBM Rational DOORS
→ IBM Rational DOORS Analyst
→ IBM Rational DOORS Net
→ IBM Rational Focal Point
→ IBM Rational Logiscope
→ IBM Rational Rhapsody
→ IBM Rational SDL
→ IBM Rational Statemate
→ IBM Rational Synergy
→ IBM Rational System Architect
→ IBM Rational Tau
→ IBM Rational Tester
→ IBM Rational TTCN
→ IBM Rational Change
→ IBM Rational Software Architect
→ IBM Rational Publishing Engine
This blog post was Co-Authored by: Saurabh Tyagi and Karthik M.
Saurabh.Tyagi 270005CY2K Visits (3564)
Let's understand the concept of Telelogic based products licensing concepts.
Focal Point - System for management of product and project portfolios.
License types supported by Telelogic products:
Understanding of "TELELOGIC_ LICENSE_FILE variable":
On Synergy, the location of the file is also stored in license_data.txt file on the same router machine.
The value of TELE
Telelogic applications that use FLEXnet rely on the environment settings that FLEXnet uses to find licenses. The applications search for license servers and license files in the following order:
License Value Description:
Node-locked license-file-name The full path to the license file on your computer.
User based feature:
A user-based license is tied to one specific user. This is compared to a floating license which anyone can use. A license Feature for a user-based license is recognized by the attribute USER_BASED on the FEATURE/INCREMENT line. The user who can obtain a user-based license are specified in the FLEXnet options file for the license server.
FEATURE RPE_PUBLISH telelogic 2009.1230 30-oct-2009 4 \
SIGN2="1EAF 827F -"
The users must be defined in a separate configuration file. The configuration file must be explicitly set in the license file
DAEMON telelogic "C:\Program File
The configuration file must list the users for the user based feature
The version number from the configuration file must match the version number from the license file (see in bold)
For the same feature both user based and floating features can be present. The user based should be listed first in the license file.
Please see the top 10 Frequently Asked Questions on the Telelogic licensing concepts:
We all know (I do) how frustrating it can be to encounter an error message and not know what to do to fix it. Now, you can find troubleshooting information and collaborate with others to improve error messages in the Information Center at: http
Understanding the Date Based Licensing Concept of Telelogic Products:
How to configure Rational Telelogic based license keys in Rational License Server 8.1.x on Microsoft Windows:
Configuring Telelogic License Server and Rational License Server on the same system:
Steps for installing IBM Rational License Server Telelogic V2.0.0:
How to update Telelogic license file:
Mixing licence keys for Rational (formerly) Telelogic products and other Rational software:
How to assign a specific port to the Telelogic DAEMON:
Adding Telelogic License Server to Rational License Server:
Procedure needs to be followed to set-up the Telelogic license server on Microsoft Windows:
How to fetch information on USER based licenses for Telelogic Products:
IBM Telelogic legacy product downloads:
Installation and configuration of Telelogic license server with a floating license file:
How to set up the Rational License Server TL 2.0 on Windows:
Telelogic License Manager service crashes after server reboot:
How to use the Telelogic borrow tool to borrow licenses for products that support license borrowing:
Rational License server versions and the corresponding FLEXnet versions:
Article Author: Saurabh Tyagi
Saurabh.Tyagi 270005CY2K Visits (4652)
Introduction on renewals concepts:
For products using date based licensing version, you will see both the original license order plus any renewal order for that product. The License Key Center will list the Renewal Order as a separate line in your account. To apply this to your license key, select the Renewal Order and it will give you the licenses associated to choose from. You may then add the quantity of the renewal per product and regenerate the key. Note, only registered licenses show up in the list of licenses available for upgrades using the renewal order. Important! The Original License Order and the Associated Renewal Order have to be registered on the same IBM Site ID. To be able to apply the renewal order and upgrade the license keys the orders need to reside on the same License Key Center account ID which is the same as your IBM Site ID
The license key can be used with any software version released before the end date of the in built license version (S&S end date). To be able to use any new release, the license key needs to be updated with new S&S orders for each period of renewal.
Click on "Get Keys" in the left navigation bar as shown below:
Select the Product for which maintenance or S&S renewal needs to be applied, lets say DOORS, then select the product and follow the instructions ahead.
In the "Required Information" screen, ensure you check for the correct Hostname and Host ID:
In the Version column, drop the box and select the latest version of the product and check the Original Maintenance End Date to be the current one. Please see below, Taking an example of Doors, we can choose the latest version while applying the maintenance to the license file:
In the Usage Quantity, key in the number of the licenses that needs to be upgraded to the latest maintenance.
Click on "Generate" and then download the latest license file by clicking the button "Download License Keys".
Useful Links :
Author: Saurabh Tyagi
Saurabh.Tyagi 270005CY2K Visits (6839)
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