RLM License Server

In Maxwell Render V3 we started using the RLM License Server system (Reprise License Manager, in particular RLM version 10.1 bl2). This system is widely used by software vendors and will allow a much more robust license management. This has several advantages compared to the previous licensing system. One is that all the users on the computer will be able to run Maxwell. Furthermore, IT admins have much more flexibility in handling the licensing of Maxwell in larger corporate/education networks. You can for example launch a web browser to see how many licenses are in use and who is using them, or block specific seats by name depending on timezone etc. 

How does it work?

When you are using floating licenses, the RLM is in charge of counting and distributing the licenses to the computers that ask for them in the same local network.

You only have to activate the licenses on the computer running the RLM using the License Activator (first option) and the rest of the computers only have to know on which computer to look for the license; you set it using the second option of the License Activator (check here for more information)

 

RLM installation

All the products will include an installer for Maxwell Render along with Studio or the plugin you bought. The RLM installer is included inside the Maxwell Render installer. At the portal, you can also find a lighter standalone installer called RLM License Server in case you are installing it on a computer dedicated to this only and you don’t want to install Maxwell Render on it (this also includes the License Activator). For more information on the installation, check this link, at the Step 1.

 

It is only necessary to install ONE instance of RLM in your entire network and NOT on each of the computers that will run Maxwell. Installing several instances of the RLM License Server on your network will result in conflicts and possibly licensing errors.

 

Manual RLM installation on Mac and common issues

In some cases, the RLM installation on Mac systems is perturbed by its security measures and it requires to be installed manually. Here are some possible solutions depending on the point it fails.

  • The installation fails after double-clicking on it. The installer will try to store some files in this folder: /Users/Shared/NextLimit/rlm_nl/ If it doesn’t exist, manually create the folders and try using the installer again. Most probably it will now store several files in that folder: nextlimit.set, rlm, rlmutil and a licenses folder

If it looks like this on your computer, try restarting it and browse to the URL: http://localhost:5054 in a browser to check if you see the RLM administration page.

  • You have also found another file in that folder: com.nextlimit.maxwellrlm.plist. This file is in charge of launching the rlm service when the system boots. If you have found it in the folder above, it means the installer could not copy it into the right folder, which should be this one: /Library/LaunchDaemons/. Do it manually; you will be asked for the administrator password. After that, restart the computer to see if the RLM is finally active using the same method explained above. If it still refuses to launch, try issuing these commands through a Terminal:

    sudo chown root /Library/LaunchDaemons/com.nextlimit.maxwellrlm.plist

    sudo chmod 644 /Library/LaunchDaemons/com.nextlimit.maxwellrlm.plist

  • After the steps above, it keeps refusing to launch at boot time. Currently, all the files are where they should be, but sometimes this keeps happening. You can try to move the file com.nextlimit.maxwellrlm.plist to this folder instead: /Library/LaunchAgents/. In this case, the rlm service will try to launch when the user logs in instead of when booting.

  • The sturdy RLM keeps refusing to launch after logging in. The RLM does not start even when double-clicking on its executable file. These actions are already getting into the troubleshooting field, more than the manual installation, but, as this seems to be a quite common issue, let’s address it too.

    • When executing the RLM file manually it shows: “can't translate local hostname” and does not launch.

    • Open a Terminal and type hostname; it will show the hostname of the user.

    • Edit the file found in /etc/ called hosts

    • Add a line like this: 127.0.0.1 and the username as shown in the Terminal when using the hostname command; for example, if it was imac3.local the line would be 127.0.0.1 imac3.local

If you don’t feel comfortable with doing all this, please, write a case to the support department. Create a new support case from your portal account or use this contact form.

 

RLM License Server administration

You can check if the server is running by opening an internet browser window and typing the URL: http://localhost:5054 on the computer that's running the server. This will show you the RLM administration options, where you can for example check the status of a license, see which computers are using licenses, or stop/start the server etc.

For IT managers and wanting to know more about the RLM system, how to adjust it to specific needs, or how to make different RLM compatible applications run from the same license server, please check the RLM administration manual

How to change the default rlm license port if other applications are already using it

You may have another application installed which already uses the default port 5053 to communicate with rlm. In this case, you can change the port in your license files:

  • Locate the maxwell_suite_floating.lic file in the computer that's running the RLM License Server and open it in a text editor. For the location of this file, please see the Licensing page.

  • Edit the first line of the license to change the 5053 port to something else, such as 5055 (this port cannot be the same as the web administration port). Save and close the .lic file.

  • In case you also have a maxwell_license.lic file in this folder, open and edit the port nr in this file as well.

  • Reboot your computer for the RLM License Server to pick up the changes or perform a Reread/Restart command at the RLM administration website.

  • Now Maxwell should connect to the server using this new port.

  • You need to open the maxwell_license.lic file on all the computers that are running Maxwell and also edit the port nr in these files.

How to make Maxwell Render work with an already existing RLM License Server

Many applications use RLM for license management. If you are already running an RLM License Server you do not need to install an additional license server for Maxwell but you can reuse the existing one. In order to do so please follow these steps:

  • Download the file nextlimit.set (it's in a zip archive so unzip it after download) and copy it where the existent RLM executable ("rlm.exe" in Windows, just "rlm" in OSX and Linux) is located.

  • Copy the maxwell_suite_floating.lic file generated with the license activator to where the rest of the license files are located.

  • Send a reread command to the RLM License Server to load the Maxwell Render license file. You can do this by opening a browser window in the computer that's running the RLM License Server, typing in localhost:5054 and in the RLM interface that appears, press the Reread/Restart servers link from the left hand side, then the Reread/Restart button on the page that appears.



The RLM Licensing system cannot work in virtual environments, i.e VMARE, Amazon cloud, Parallels or other virtual environments unless it is specifically allowed for in the license.

It is only necessary to install ONE instance of RLM on your entire network and NOT on each of the computers that will run Maxwell. Installing several instances of the RLM License Server on your network can result in conflicts and possibly licensing errors.

RML can have problems handling IDs in conditions with many ID candidates, i.e. too many HDDs/SSDs and network adapters including virtual and pseudo ones, even if the ID assignation is correct. In those circumstances, removing some of those HDDs and/or network adapters not in use will avoid the high concurrency and make RLM work properly.