Software License Management for Multiple Publishers

Software License Management for Multiple Publishers – 2 strategies

When you have licensed software from multiple publishers, you must decide how you want to configure your software license management installation.   You have two choices for configuring rlm and the ISV servers when running them on a single license server system.

The first choice is to keep them entirely separate, using separate installation directories and port numbers, for example:

Software License Management for Multiple Publishers

Advantages:

  • conceptually simple

Disadvantages:

  • The two rlm client connection ports and web server ports will have to be managed so that they don’t collide.
  • Users of the rlm web interface will have to remember which port number goes with which.
  • The default rlm client port numbers as established by the publishers (in the license files or environments on all the client machines) will need to be changed, for at least 1 publisher.

The second choice is to  run a single instance rlm, which manages two (or more) ISV servers.  This is the method recommended by Reprise Software. For example:

Recommended Strategy for software license management from multiple publishers

Advantages:

  • Only a single RLM port need be managed.  If a new ISV server is added with a new port, the single copy of rlm adds this port to the list of ports it listens to.
  • A single web interface is used for all publishers/ISV servers.
  • No client-side changes need to be made for any publisher.
  • Simple, straightforward method to add a new publisher/ISV server, when the time comes.

Disadvantages:

  • You must be sure to always select the newest version of rlm (rlm.exe) and the utilities that any of your publishers use.

The simple way to accomplish this is to copy one publisher’s server-side files to the other
publisher’s server directory.  Or create a central repository of rlm server side files. The files necessary are:

  • rlm[.exe]. Use the latest version from all the publishers involved, or better yet, get
    the latest from http://www.reprisesoftware.com/enduser_kits/end-useragreement.php
  • <ISV>[.exe] or <ISV>.set from all vendors
  • *.lic from all vendors
  • Command line utilities such as rlmstat[.exe], rlmdown[.exe], etc. As with rlm[.exe] use the latest from the vendors involved, or download from:  http://www.reprisesoftware.com/license_admin_kits/license-admin-agreement.php

4 comments

  1. James O'Shea says:

    We have run into the problem where another vendor also uses Reprise License Manager and both can not run on it. This blog seems to address this issue. However, I have no clue what the instructions mean. Can a more detailed and simply explained set of instructions be written?

  2. Richard Hagen says:

    Please address a strategy on how to make the single RLM work when the vendor locks the RLM license with a custom HASH file. Once the vendor generates the HASH, you may incur fees to have the HASH changed. Unfortunately, the HASH file is calculated using the port number as one of the variables so you cannot change anything. RedGiant currently do this.

    The only way I can think of is to rename all the other vendors to use the port that is in the redgiant license… or just be forced to run more than one RLM server again.

  3. admin says:

    I’m not sure what you mean by a “custom hash”, but in any event, this is something you should take up with Red Giant. It seems unlikely to me that they include the port # in any encrypted value, and if they do, this is (to my thinking) not a good thing to do. If they do this, you are correct, you will have to put all your other vendors on the same port #. You should be able to modify the ISV server’s port number with the “port=…” parameter on the ISV line.

Leave a Reply

Your email address will not be published. Required fields are marked *