< All Topics
Print

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 the license. You will also be able to specify a grace period – the number of times the RLM server can fail to contact Activation Pro before the license is disabled.

 

Subscription Licenses

When you issue a subscription type activation key, you will specify the renewal period – the time when the client will need to reach back out to the license server to renew the subscription. During subscription renewal the client will check the status of the activation key.

 

You can also have your application check in with Activation Pro before the renewal window to check the activation key status. Please see the next section.

 

Other nodelocked licenses

Your application will be able to query the Activation Pro server to see if the activation key is enabled or not. You have the flexibility in determining the frequency in which you contact the Activation Pro server, and the logic to perform if the client doesn’t receive a response.

 

To find the activation key to query, first call rlm_license_akey() (Note: In the product definition, you will need to set the “Include Activation Key in License:” option to “Yes,” or “2 licenses: one with and one without”).

 

You will then be able to query the Activation Pro server for the current status using the rlm_act_keyinfo() family of API calls.

 

Disabling an activation key

You can disable the activation key either by:

  1. Unchecking the “Enabled” checkbox in Activation Pro, and saving the activation key
    or
  2. Deleting the activation key in Activation Pro

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.