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:

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.  
  • See Activate a License on the Target Node.

The file HttpLicenseRequestConfiguration.json should be created in RT-LAB's root folder:

C:\OPAL-RT\licserver

/usr/opalrt/license

The file HttpLicenseRequestConfiguration.json should provide the following contents:

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 

Users should receive the following files:

• Extract the files from the ZIP or TAR archive.

• On Linux, use the command: 

  tar -xvf <tarfilename.tar>

In the License server folder, edit the OpLicenseServer.config with a text editor and adjust the following settings:

• If you are using a floating license: Place the opallicense.bin file you received from OPAL-RT Support in this folder.
• This step is not required for the time measurement license type. Skip to Step 3 if you are using this license type.
• Start the oplicenseserver (.exe) application.

• Make sure the firewall allows use of the port selected in the configuration file.

Example of OpLicenseServer.config

{
	"ConfigReloadDelay": 1,
	"Port": 9461,
	"LogFile": "OpLicenseServer.log",
	"ReadTimeout": 10,
	"WriteTimeout": 10,
	"RepoPath": "idb",
	"CloseInactiveSessionAfter": 10,
	"CleanUpInterval": 15,
	"OpalLicenseFile": "opallicense.bin",
	"RequestFolder": "requestlogs",
	"RequestLogQueueSize": 100000,
	"OpalLicenseReloadInterval": 0.5
}

Step 3: Configure Opal-RT's license bridge

In the License server folder, edit the OpLicenseBridge.config with a text editor and adjust the following settings so they match your particular case:

• Start the oplicensebridge (.exe) application
• Make sure the firewall allows use of the port selected in the configuration file.

Example of OpLicenseBridge.config

{
	"ServerURL": "http://localhost:9461",
	"ToleranceNoSrv": 15.0,
	"TransmitDelay": 1,
	"RemainingTimeDelay": 5.0,
	"MsgQueueSize": 100000,
	"ConfigReloadDelay": 1,
	"Port": 9365,
	"LogFile": "OpLicenseBridge.log",
	"ReadTimeout": 10,
	"WriteTimeout": 10,
	"MaxBurstMsgCount": 3
}

Step 4: Submit a product key (for Simulation Time Measurement license type ONLY)

• This step is not needed for floating licenses. Skip this step if you are using a floating license.
• A product key was provided with your licensed product. It is usually contained in a file named <license ID>.productkey
• To submit the product key to the license server, start a Python console (Tools > Python > Open Console) in RT-LAB:

Insert the following code:

import requests
r = requests.post('http://<server name or IP>:<server port>/useraccountv1', json={"Version":1,"Request":{"Action": "submitproductkey","ProductKey":"<contents of the product key file>"}})
print r.content
print r.status_code

If the submission was successful, the status code should be 200. Otherwise, r.content provides details about the failure.
Assuming the OPAL-RT product is properly configured to access the bridge, the licensed product is ready for use.

Licensing Troubleshooting