Search
Close this search box.
Try RLM for Free
Search
Close this search box.

Reprise Blog

Reprise Software Blog – Your Hub for Licensing Solutions Insights
Stay informed about our products including Reprise License Manager (RLM), RLM Cloud, and Activation Pro. 

 

Learn from our customer success stories, understand the intricacies of different licensing models, and keep up with our ongoing service upgrades.

How to Set Environment Variables

  • By Reprise Staff
  • December 27, 2019

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.  Some RLM environment variables are RLM_ACT_TIMEOUT (adjusts the timeout to the activation server to the value supplied), RLM_QUEUE (enables queueing for a license), and RLM_ROAM (controls setting up, using, and returning roamed licenses).  This is not an exhaustive list, but gives you an idea of what environment variables can do.  In some situations, a Reprise Software support person may ask you to set a particular environment variable to some value and then run your application.  This article is about how to set environment variables, not which ones are available in RLM.

 

A characteristic of environment variables is that they are set in a process, like a Windows command window or a Unix/Linux shell, and are inherited by processes that are created by that process.  So if you create 2 command windows and you set an environment variable in window 1, it won’t be set in window 2.  But if you run an application in window 1, the environment variable will be set in that application.

 

The easiest way to use an environment variable with RLM is to set it in a command window or shell, then invoke the application from that window or shell.  For example, if you wanted to set RLM_DIAGNOSTICS to cause the application to write RLM diagnostic information to the file “diag.txt”

  • Windows: set RLM_DIAGNOSTICS=diag.txt
  • sh, bash : export RLM_DIAGNOSTICS=diag.txt
  • csh: setenv RLM_DIAGNOSTICS diag.txt

 

Then invoke the application from the window where you set RLM_ROAM.


But it’s inconvenient or sometimes impossible to invoke the application from a command window on Windows.  In that case you can set the environment variable via the Windows control panel:

  • Bring up the control panel.
  • Search for “environment” in the search box at the top right.
  • Click on “Edit environment variables for your account.
  • Enter the environment variable name and value.
  • Click on OK in both windows.

Other Posts

New RLM Release (v16.0)

The latest major release of RLM is finally here! Version 16.0 brings an all new web interface with many enhancements over the previous interface, and fixes multiple vulnerabilities related to the web interface. New Features Include: All-new Redesigned UI/UX Most server functions now available directly

Learn more

Dealing with Activation Read Timeouts (error -105)

On rare occasions, an activation request will get a read timeout status return (-105). There are several causes to the RLM_EH_NET_RERR (-105) error.   If you can activate from some systems, then the first cause (server down) is unlikely.   More likely is that there

Learn more
futuristic background with a cyber key in front

How to License Server-Based Software

We compare licensing options for server-based software including floating licensing and using a licensing manager.
Learn more
U-RENDER logo over their rendering of a red sportscar

U-RENDER Accelerates Time to Market using Reprise License Management

RLM stood out as a hassle-free and flexible solution for node-locked and floating licenses. When U-RENDER started evaluating different solutions for their own software product, RLM was already at the top of the list.
Learn more

A Kinder, Gentler Licensing Strategy

You need an implementation strategy for license management that provides customers with all the licensing system components. These parts enable customers to control their software usage without burdening those customers who don’t. Here is how to build a win-win strategy for end-users and software publishers.
Learn more
Photo of fossil in a rock

StrataData Consolidates its Licensing Around RLM

Using RLM, StrataData migrated to a more flexible licensing model which seamlessly integrated their existing dongles for those that wanted to retain them, as well as provide all the benefits of floating, server-based licensing.
Learn more

Building Your Software Pricing Model

Deciding how to price your software products is a challenge that does not a have “one-size-fits-all” solution. A software license manager, such as the Reprise License Manager (RLM), is an indispensable tool that can help you to design and enforce pricing models that are right
Learn more
See All

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.