Installing IBM Rational Rhapsody Licenses on Microsoft Windows; a practical guide

Introduction

First, it is necessary to verify which license you have, meaning, can you just save the license received to the system and launch Rhapsody, or do you need additional files or settings?

If you have a "node-locked" license or if the license server is already running and this is a client system, then it is a simple case of setting a system environment variable to locate the local license or license server and license.

If you have a server license, then FlexNET files will need to be installed and configured.

If you have a server license for a stand-alone installation, then FlexNET files will still need to be installed and configured as well the port@host specified in the system environment variable (which is the same as for client systems above).

Which License Type Do You Have?

Server licenses start with a SERVER line

SERVER HostName DISK_SERIAL_NUM 19353

DAEMON telelogic C:\Program Files\Telelogic\Tools\Licensing_11\Server\telelogic.exe

These will require the license manager (lmgrd) and Vendor Daemon (Telelogic.exe) running before Rhapsody invoked. You must install TLS Tools 1.5 flexnet files (see below).

Nodelocked licenses start with the DAEMON/VENDOR line:

VENDOR telelogic
PACKAGE rhapsody_lang_pack telelogic COMPONENTS=" dev_ed Rhapsody_C \
Rhapsody_Java" OPTIONS=SUITE SIGN2="XXXX DA97 B947 7EE5 3256 \
3CAF 670C 60F4 CCBF 6ECE C5B2 8876 6E40 E56D 7BBE 0032 D736 \
4B83 XXX 1011 8ADF XXX 11BF AAD6 635F 2266 A974 XXX CF5E \
6D2D"

Software can only be used on one machine.

Nodelocked License Setup & Clients

The environment variable TELELOGIC_LICENSE_FILE has to point to the local node locked license or if this is a client machine, then the server which will house the licenses.

How do you create this variable and set the path?

There are two ways. Manually, create a TELELOGIC_LICENSE_FILE system environment variable yourself and specify the location to your license file/server (This is recommended, if only setting up one or several systems) or download the Telelogic License Setup Utility and after installation, run the License Setup by way of the Start > Programs > Telelogic > Telelogic Lifecycle Solutions > Telelogic License Setup Utility

Both are shown below:

1 - The TELELOGIC_LICENSE_FILE system environment variable will be created\updated and set.

For Nodelocked licenses the utility should set the license path

Example:

TELELOGIC_LICENSE_FILE = C:\Rhapsody\Flexlm\license.dat

For Client systems accessing a server license

Example:

TELELOGIC_LICENSE_FILE = 19353@python

(port is specified in the first line of the server license and host is the server name)

Launch Rhapsody!

2 - Using the Windows License Setup Utility (download instructions can be found further down)

Launch the License Utility

Specify the type of licensing

Troubleshooting:

Check the launch path is valid

manually browse to

C:\Program Files\Telelogic\Tools\Telelogic Licensing 11\Client\License Setup.exe

If you are asked to specify which Telelogic product, and Rhapsody is not in the list, then you are launching an older version of the Telelogic Licensing Setup tool.

Server Licenses

Require the license manager (lmgrd) and Vendor Daemon (Telelogic.exe) running before Rhapsody invoked. Install TLS Tools 2.0 flexnet files

Make sure the server license is correctly edited to include on the first line, the server name (name of the machine), disk serial number and the port (19353 otherwise modify)

SERVER python DISK_SERIAL_NUM=6410bddb 19353

The DAEMON path may be absent (this is the default) since usually, the telelogic.exe is in the same location as the lmgrd.exe (also it is advised to put the license in the same directory too, then daemon path need not be specified in first place).

Recommendation: leave blank.

VENDOR telelogic

Otherwise, you could manually specify its location (after installing the TLS):

VENDOR telelogic "C:\Program Files\Telelogic\Tools\Licensing_11\Server\telelogic.exe"

Installing Telelogic License Server 2.0

Download the Telelogic License Server version 2.0 from Rational support (Downloads):

http://www.ibm.com/software/support/portal/try-it-now/?ibmsst=allSupport

Read the readme.htm in the TLS Installation Files

System Requirements

• Windows 2000
• Windows 2003 Server
• Windows XP
• Windows Vista
• Solaris 9 and 10
• HP HP-UX 11i
• Linux Red Hat Enterprise 3, 4 and 5
• IBM AIX 5.3

See Telelogic_licensing_guide.pdf

Start the installation from

../license_server/setup.exe

Any previous license manager should be uninstalled before installing this version.

The command lmhostid.bat can be used to find the hostid for the machine.

Accept the defaults and specify location of your license.

The paths in TELELOGIC_LICENSE_FILE will now be set.

Accept to register the service License Manager, otherwise the license manager will need to be started manually after each reboot (by using lmtools) and click Finish.

Without Rebooting you should be able to launch LMTOOLS and start the manager.

Check that you have a new Tools Entry in the Start > Programs > Telelogic menu.

Launch LMTOOLS.

Give the service a name and specify the license and license manager (lmgrd) paths (should be set by default). Check the start up boxes and save the service.

On the Start\Stop\ReRead, start the manager.

On the Config Services in lmtools, click View Log. Check the version and that all features are read.

Stand-Alone Server-Client Install

If the system is intended to be a stand-alone system containing both the server license and Rhapsody installation (as is the case in evaluation licenses for example) then one is required to also include the Client setup.

Manually add the port@host to the TELELOGIC_LICENSE_FILE variable (entries are separated by a semi-colon).

C:\flexlm\Rhapsody\license.dat;19353@python

So the first entry is specifying the server license path for the license manager, and the second is the path that will be called when invoking Rhapsody.

Launch Rhapsody!