Get a License#
A license is required to use and run POLARIS. Licenses are managed by the Vehicle and Mobility Systems Department. You can initiate a license request directly using the below buttons.
Use this if you work for a federal or state government agency.
Use this if you work in the private sector.
License Files#
Once the license application is finalized, you will recieve an email from the licensing team with the license file needed to run POLARIS. Typically, we prefer to distribute node-locked licenses, which tie the license to a single machine. These are the simplest licenses for the end user, as the POLARIS executable will simply ask for the location of the license file on the first launch.
However, in situations where this style of license is not sufficient, we can also provide a floating license, which will allow the user to run on multiple machines at the cost of a bit more setup and maintenance. This requires the end-user to setup a local license server to communicate with our own license server, and when POLARIS is run, the executable will checkout a license from your local server, and check the license back in when POLARIS closes. Below are detailed instructions for setting up a license server; if a floating license is requested, you will be sent another copy of these instructions in a folder containing the required files for setup.
Floating License Server Details#
Floating licenses for POLARIS require a license server to be run by the user. When a POLARIS instance on the network is started, it will check for its own individual license file, which will point to your license server and request to check out a license to run. This allows your users to see and control who is running POLARIS.
The recommended way to set up the floating license server is with the lmadmin utility:
Further documentation and more detailed instructions here
When installing, you can choose to run as an OS service (which requires admin privilege) or manually (this can be changed later). The installer will also want you to choose a config path different from the installation path. Keep track of both of these! The installer will also want a port to use for the web interface (8090 by default).
After installing, you can start the server manually with “lmadmin.exe -configDir <conf_path>” and you can login to the control panel from a browser at http://
In order to run the server, you will need to keep three ports open:
One for the web interface, which is 8090 by default and can be changed during installation
One for the license communication with the other systems (27001 by default). This is the “ServerPort” required in the user license file.
One for Vendor Daemon communication with other systems. This is randomly assigned at startup by default, but can be changed to a fixed address when we set up the vendor daemon. If you want to use a specific port for this, you can give us this information when we generate the server license file. The last two ports are needed to communicate between client and server, so not only will they need to be open on both machines, they will also need to be authorized in the network level firewalls.
To generate a license file for this server, you will have to send Dynasty the hostid and hostname of the server it will run on. You can use the lmutil.exe utility in the Box folder to find these: lmutil.exe hostid lmutil.exe hostid -hostname After receiving the license file, you can configure the Vendor Daemon.
To do this first copy the AUTONOMI.exe file from Box to your lmadmin install directory. Next, open the lmadmin web interface and look for “Vendor Daemon Configuration” under the “Administration” tab. From here you can select the license file you received, and you should be free to start serving licenses!
If you want to specify the port for Vendor Daemon communication, this can be done at the Vendor Daemon Configuration page, after clicking “Administer” on the Vendor you want to change (AUTONOMI).
To let your users check out a license from your server, give them a license file with this format (using the hostname of your server and the second port, by default 27001):
SERVER