How to bind license keys based on unique strings on Rational License Key Server

Technote (FAQ)


Question

How do you bind license keys based on unique strings on IBM Rational License Key Server?

Cause

Named User/ User based/ authorized, user Floating and Token type of licenses can be bind using RESERVE and INCLUDE features through Option file. To bind a license key for a user or group, you need to add a unique string with RESERVE keyword that distinguish its INCREMENT line from all the other INCREMENT lines of that same license feature.

Answer

Procedure:

Create an Option file with name ibmratl.opt under the Installation directory of Rational License Key Server( ..\Program Files\IBM\RationalRLKS\common) to bind licenses for a user or for a group.

In case of IBM Rational products(Example: IBM Rational Clearcase, IBM Rational RequisitePro, IBM Rational ClearQuest etc) binding the licenses based on the unique stings are as follows :-

- VENDOR_STRING
- NOTICE
- VERSION
- KEY


For example:-

To bind a floating ClearQuest license key for a specific user or group using any of the unique strings follow the steps mentioned below:

GROUP Testgrp test1
RESERVE 1 ClearQuest:NOTICE="Sales Order Number:XXXXXXX" USER test1


OR

GROUP Testgrp test3
RESERVE 1 ClearQuest:VERSION=1.10000 USER test3


OR

GROUP Testgrp test4
RESERVE 1 ClearQuest:KEY=2AFCC7D30885 USER test4


OR

GROUP Testgrp test2 test4 test6 test8 test10
RESERVE 5 ClearQuest:VENDOR_STRING="0|Floating|0| ClearQuest:1.1" GROUP Testgrp



Following are the content of the license file being used above :-

SERVER Hostname  123456123456 27000
VENDOR ibmratl
INCREMENT ClearQuest rational 1.10000 15-jan-2014 5 2AFCC7D30885 \
VENDOR_STRING="0|Floating|0| ClearQuest:1.1" DUP_GROUP=UH \
vendor_info="0|IBM Rational ClearQuest Floating License Key|0" \
ISSUED=21-jan-2013 NOTICE="Sales Order Number:XXXXXXX" ck=127 SN=5903080



In case of IBM Rational Telelogic family of products(IBM Rational DOORS, IBM Rational Synergy, IBM Rational Change etc), binding the licenses based on the unique stings are as follows :-

- SIGN
- VENDOR_STRING


For example:-

To bind a floating Change-Base feature license key for a specific user or group using any of the unique strings follow the steps mentioned below:-

GROUP Testgrp test1
RESERVE 1 Change-Base:SIGN="0159 8AB0 3229 AD20 7A6F 43ED 802D 58A4 2420 CD27 591C 5807 F766 9862 D03A 097C 6972 4AE0 1D39 E8CD 4992 E715 074F 9D39 F39F 1C25 2D73 C168 AB7F 4ED8" USER test1


OR

GROUP Testgrp test2
RESERVE 1 DOORS:VENDOR_STRING="T10-999999" USER test2


Following are the content of the license file being used in above example:-

SERVER Hostname  123456123456 27000
VENDOR ibmratl
INCREMENT Change-Base telelogic 2014.0115 15-jan-2014 2 \
VENDOR_STRING=T10-999999 ISSUED=13-Dec-2012 SIGN2="0159 8AB0 \
3229 AD20 7A6F 43ED 802D 58A4 2420 CD27 591C 5807 F766 9862 \
D03A 097C 6972 4AE0 1D39 E8CD 4992 E715 074F 9D39 F39F 1C25 \
2D73 C168 AB7F 4ED8"

In a similar manner, Token license key binding based on the unique stings are as follows:

- VERSION
- NOTICE


For example:-

GROUP GroupN test2 test1
RESERVE 1 TLSTOK:VERSION=2.0 USER test1
RESERVE 10 TLSTOK:NOTICE="Sales Order Number:XXXXXXXXXXX" USER test2


Following are the content of the license file being used :-

SERVER IBM-BBRHILBJH5D 0021CC72C839 27000
VENDOR ibmratl
INCREMENT TLSTOK ibmratl 2.0 15-jan-2014 50 vendor_info="0|IBM \
Rational Main Token Feature|0" ISSUED=13-Mar-2013 \
NOTICE="Sales Order Number:XXXXXXXXXXXXXXXXXXX" \
AUTH={ rational=( LK=169C07203A4A) ibmratl=( SIGN="004D 05E3 \
B206 4A36 163B FEB2 D93C 4300 41E3 BD26 D55C 3D47 BA10 957E \
2825") telelogic=( LK=F2447618DF0302F4FB9E SIGN2="179D C4CC \
A72A C0E8 388C 9A45 6B2A 15FD E765 12EB 9CAC 07E1 3D1A 3E8F \
230B 0FB6 F9E3 649E 8044 EB5F 919E 5C7A EB1D 7220 599B 6880 \
E996 E474 B01E AA7E") }


Rate this page:

(0 users)Average rating

Document information


More support for:

Rational License Key Server
Configuration

Software version:

All Versions

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1628501

Modified date:

2013-03-19

Translate my page

Machine Translation

Content navigation