Search is based on keyword.
Do not search with natural language
Ex: "How do I write a new procedure?"
These pages explain how to license your product over a network. Throughout this guide, we refer to machines that serve licenses as servers and machines that ask for licenses as clients.
There are three stages to setting up server, or floating, licenses:
|1.||Install the license on the server machine - See Installing Licenses.|
|2.||Install the server tools - See Installing the Server Tools.|
|3.||Direct the client machines to the server where the license is installed - See Telling the Client Machines Where to Find the Licenses.|
Note: The Foundry Licensing Tools’ default settings do not support RLM licensing on virtual machines (VMs). If you have any questions regarding licensing on VMs, please visit support.foundry.com for more information.
This guide should cover all the information you need to use RLM licenses for Foundry products. However, it is not meant to be an exhaustive exploration of all the features available with RLM licensing. For in-depth information on RLM Licensing, go to www.reprisesoftware.com.
About Server or Floating Licenses
A server license, sometimes known as floating license, running on a server enables one of our products to work on any networked client machine. Floating licenses are sometimes called counted licenses. Floating licenses are installed on a server and locked to the server's system ID. See Finding the System ID for more information.
Floating licenses on a server require additional software to be installed. This software manages those licenses on the server, giving licenses out to client workstations that want them. The software you need to manage these licenses is called the Foundry Licensing Tools (FLT), which is included with the Foundry Licensing Utility download and can be installed and uninstalled from within the application.
Floating licenses often declare a port number. This is required if you have an internet firewall on your license server so that you can permit license communication while blocking others. See Firewalls.
A floating license looks like this before installation. The <server_name> is replaced automatically with the machine name when you install the license.
HOST <server_name> d49a20b9be26 4101
LICENSE foundry mari_i 2017.1231 permanent 20 share=h start=4 oct-2010 issued=4-oct-2018 _ck=fa072c6a5a sig="60P0453JHKQBGTB1HH7E3HNW843UJ627TSF4CXR22H7KNMYHG1B99WBSNHS1UE7FCN2W3AY8KV"
For further information about the structure of the license key, see Floating License Syntax.
Sorry you didn't find this helpful
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
If you can't find what you're looking for or you have a workflow question, please try Foundry Support.
If you have any thoughts on how we can improve our learning content, please email the Documentation team using the button below.
Thanks for taking time to give us feedback.