Q100260: How to upgrade the version of RLM in the Foundry Licensing Tools

Follow

SUMMARY


This article explains how you can upgrade the version of RLM used in the Foundry Licensing Tools.  This can be useful if you need access to features available in a newer build of RLM than the version included in the Foundry Licensing Tools.

MORE INFORMATION


The Foundry Licensing Tools (FLT) 7.1v1 includes RLM version 9.4bl4.  If you wish to use a newer version of RLM to float your Foundry RLM licenses then you can manually update the version of RLM by following the steps below.  

NOTE: These instructions assume that you have already installed the Foundry Licensing Tools (FLT) 7.1v1 on your server and are successfully floating licenses on your network.  Instructions on how to do this are available in the following article: Q100027: How to install a floating license?


  1. Download the latest build of RLM from the Reprise Website
    Go to http://www.reprisesoftware.com/admin/software-licensing-download.php and download the RLM bundle for your operating system.

  2. Fully stop the Foundry RLM server
    You'll need to stop it either from the Foundry License Utility or with an 'rlmutil rlmdown' command - if you stop the server from the RLM webserver then the RLM server process won't completely shutdown because part of it remains up to run the webserver.

    OSX:
    - Run the Foundry License Utility (FLU) from /Applications/TheFoundry/LicensingTools7.1
    - Go to the RLM Server tab and click on Stop Server

    Windows:
    - Right click on the Foundry License Utility (FLU) in 'C:\Program Files\The Foundry\LicensingTools7.1' and select 'Run As Administrator'
    - Go to the RLM Server tab and click on Stop Server 

    Linux:
    - Run either of the following commands as root or with sudo

    cd /usr/local/foundry/LicensingTools7.1/
    ./FoundryLicenseUtility -s stop -t RLM

    or
    cd /usr/local/foundry/LicensingTools7.1/bin/RLM/
    ./rlmutil rlmdown -c 4101@serverName

    (where serverName is the hostname of your license server)


  3. Save copies of the current RLM server files in case you need to revert to RLM 9.4bl4
    Make a directory within the RLM bin directory of the FLT install and call it 'RLM_9.4bl4'

    OSX: /Applications/TheFoundry/LicensingTools7.1/bin/RLM/
    Windows: C:\Program Files\The Foundry\LicensingTools7.1v1\
    Linux: /usr/local/foundry/LicensingTools7.1/bin/RLM /

    Then move the 'rlm.foundry' and 'rlmutil' files from the RLM bin directory into the new 'RLM_9.4bl4' sub-directory.  Note: On Windows the files are 'rlm.foundry.exe' and 'rlmutil.exe'.


  4. Manually install the new RLM server files
    Extract the 'rlm' and 'rlmutil' files from the new RLM download (on Windows you'll need to run the RLM installer and choose a location to store the files) and copy them into the RLM binary directory from step 3.

    Rename the new 'rlm' file to 'rlm.foundry' so that it is picked up by the RLM server startup scripts and the Foundry License Utility (on Windows, rename the new 'rlm.exe' file to 'rlm.foundry.exe')


  5. Start up the RLM Server again with the new version of RLM
    OSX:
    - Run the Foundry License Utility (FLU) from /Applications/TheFoundry/LicensingTools7.1
    - Go to the RLM Server tab and click on Start Server

    Windows:
    - Right click on the Foundry License Utility (FLU) in 'C:\Program Files\The Foundry\LicensingTools7.1' and select 'Run As Administrator'
    - Go to the RLM Server tab and click on Start Server 

    Linux:
    - Run the following commands as root or with sudo
     cd /usr/local/foundry/LicensingTools7.1/
    ./FoundryLicenseUtility -s start -t RLM


The Foundry RLM server should now be running with the new version of RLM.  You can check on the server status by viewing the RLM Webserver at http://serverName:4102 (where 'serverName' is the hostname of your license server).

MORE INFORMATION
If you encounter any problems with your license server then please follow the instructions in the following article to generate a license diagnostic file and open a Support ticket. Q100105: Diagnosing License Problems
Was this article helpful?
0 out of 0 found this helpful