Documentation Home Page ◇ RT-LAB Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.
Configuring the Floating License Server
Since RT-LAB v. 2020.1, users are able to deploy RT-LAB with cloud (floating) license features.
When this feature is implemented, each target must be activated with a valid cloud license to run a simulation.
The following steps enable cloud licensing in RT-LAB.
All licensing can be requested through the RT-LAB interface, but for questions please contact OPAL-RT Technical Support.
Before You Start
Before activating a target, users should ensure that their systems (both host and target) are correctly configured by following these steps:
RT-LAB must be installed on your Windows host computer. | |
Each target must be available in RT-LAB. | See Connecting your Host Computers to your Real-Time Target for an OPAL-RT chassis or Setting Up the Windows PC as a Target Node for Windows. |
RT-LAB must be installed on each target. | See Installing RT-LAB on the target Node for an OPAL-RT chassis. |
Currently, RT-LAB supports two distinct types of features regarding the floating license server:
Simulation Time Measurement: With this license, a user can have multiple instances of real-time targets where simulation time is measured as it elapses, and captured by the license server.
In this scenario, users can run simulations as long as they have remaining time on the license server.
Floating License for the Number of Cores: With this license, users can have multiple instances of real-time targets where the number of cores used in all stations combined is managed by the license server.
RT-LAB contacts Opal-RT's license server to reserve the number of the cores needed for simulation before it runs. If RT-LAB cannot retrieve the proper license information from the server, the simulation is ended.
Step 1: Request and install local licenses for RT-LAB targets
You should install proper local license files on all the targets you want to use with the license server.
Note: Users must specify the type of license they plan to use when contacting Technical Support to acquire license files. Users can request licenses from the RT-LAB menu through Help > Request a license.
The file HttpLicenseRequestConfiguration.json should be created in RT-LAB's root folder:
Windows | In RTLAB_ROOT at the path
|
Linux | In REDHAWK_OPALRT_ROOT at the path
|
The file HttpLicenseRequestConfiguration.json should provide the following contents:
bridge_ip | @ip of the host handling the bridge See the bridge_ip entry in the code block below. |
bridge_port | @port where the bridge should expect connections. See the bridge_port entry in the code block below. |
license_id | provided by the name of the file .productkey. See the license_id entry in the code block below. |
request_timeout | timeout used to wait for data from the bridge (String). See the request_timeout entry in the code block below. |
Example of HttpLicenseRequestConfiguration.json
{
"bridge_ip" : "127.0.0.1",
"bridge_port" : "9365",
"license_id" : "myLicenseId",
"request_timeout" : "15"
}Step 2: Configure Opal-RT's license server
Note:
No installer is provided, but the licensing software package is distributed as a simple archive (ZIP file for Windows or TAR file for Linux) extracted to a local folder.
Supported platforms are Windows and CentOS 7.6.
Users should receive the following files:
oplicensebridge.exe | (Windows)/oplicensebridge (CentOS 7.6) |
OpLicenseBridge.config |
|
oplicenseserver.exe | (Windows)/oplicenseserver (CentOS 7.6) |
OpLicenseServer.config |
|
Extract the files from the ZIP or TAR archive.
On Linux, use the command:
tar -xvf <tarfilename.tar>