Broadcast Overview

RLM has a built in method where a client can locate an on premises RLM server by sending a broadcast request to the local network (this is a similar concept to how DHCP works). Broadcast is enabled by default, and is the last attempt the client will make to locate a license on the network. […]

Disable an Activation Pro license

You are optionally able to remotely disable a license issued by Activation Pro. Note that all methods will require an internet connection.   Floating licenses You will need to issue your customer an Alternate Server Hostid license from Activation Pro. The RLM server will contact the Activation Pro server on a schedule you define in […]

Creating a Windows service for the RLM server

Download an Admin bundle from our website Run the installer (Optional) Specify the RLM install location Open a command prompt (CMD) or PowerShell terminal Change Directories to the location where RLM was extracted in step #3. For example: cd C:\Users\[username]\Documents\Reprise\rlm.v16.1BL1-x64_w4.admin Determine which flags you will want to start RLM with. A full list of flags […]

Limit CPU cores

RLM doesn’t currently have a built-in way to limit an application to a specific number of CPU cores. But this can be implemented with logic in your application.   RLM LICENSE lines can be configured to include an options string. This string is up to 64 characters in length and is included in the license […]

Communication Troubleshooting

Sometimes in troubleshooting problems with client applications connecting to license servers, it’s useful to have a tool outside RLM which can tell you whether messages can get through to the server. If a firewall or anti-virus package or proxy is blocking communications, a separate tool will have the same problems connecting to the server as […]

License Server Administration for Multiple Software Providers

Note: In this article we will refer to software publisher as an ISV (Independent Software Vendor). Standard Setup (recommended) A single RLM License Server is able to manage floating licenses issued by multiple ISVs.  You will want to run the highest version of RLM provided to you by your ISV, or you can download the […]

Client Diagnostics

When troubleshooting you can generate an RLM client diagnostic report. Generating this report requires setting the “RLM_DIAGNOSTICS” environment variable. You can read more about setting environment variables here. When the RLM Client library is run (developers: specifically the rlm_init() API call), RLM will generate the diagnostic report to the file location specified in the environment […]

Activation Read Timeouts (Error -105)

On rare occasions, an activation request will get a read timeout status return (-105). If you can activate from some systems, then the first cause (server down) is unlikely.   More likely is that there is either a proxy/firewall/anti-virus package blocking the response or the system fails a reverse DNS lookup and is timing out. […]

How to Set Environment Variables

Environment variables are flags that you set outside an application that the application reacts to. Applications and libraries, like RLM, read environment variables that they define. You can find a list of the RLM environment variables in our documentation.   A characteristic of environment variables is that they are set in a process, like a […]

RLM Server Ports

Default Ports For a basic RLM server install with licenses from one Software Vendor (ISV), the server will use the following ports: 5053 – Default RLM server port 5054 – Default web administration port (embedded web server) A port between 1024 and 65353 – The ISV server port, dynamically assigned at startup.   Setting custom […]

RLM and RLM
Activation Pro

What’s the difference?

Reprise License Manager (RLM)

Software License Manager

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

As a Software publisher, you integrate RLM into your product, and RLM keeps track at runtime of who is using the licenses of your software.

RLM can do this entirely within the client library (linked into your application), or, more commonly, your application makes a request of the RLM Lincese Server to check out a license.

The lincese server runs either on your customers network, or in the cloud if you are using our RLMCloud™ service.

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

RLM Activation Pro

Software Activation Manager

Activation Pro is
used once when your customer purchases your software in order to retrieve the license which is specific to that customer.

Software Activation’s purpose in life is to get the licenses for your product to your customers with a minimum of fuss.

Activation Pro also has a server component wich we call the activation server.

Your application contacts the activation server and supplies a short text activation key, and in exchange, the activation server returns the license which enables your product.

Generally, this is done once, right after your customer purchases your software, not every time your software is invoked.