Search
Close this search box.

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 Server Web Interface Passwords v15.1 – v15.2

Overview Beginning with RLM v15.1 it is mandatory to configure a password file to use the RLM Web Interface. RLM will generate a default password file if there isn’t already a password file present at startup.   Previous versions RLM versions 10.0 to 15.0 allowed users to create a password file (rlm.pw), but this was […]

Floating License Timeouts

Overview RLM server administrators can configure a license timeout if a client computer has not returned the license, and if RLM is no longer able to check the license status on the client computer. This means that a Timeout will not return a license that is in use (say a user keeps an application checked […]

Using SSL Certificates (HTTPS) with RLM

Overview Starting with RLM version 15.1, License Administrators are now able to run the RLM web server with SSL certificates. When setup to use SSL certificates RLM’s web server will run with the HTTPS protocol. RLM does not come with pre-configured SSL certificates. You will either need to procure your own certificates from a Certificate […]

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.