Open topic with navigation
Most package types (Professional, Basic, and Evaluation) require a license file in order to run.
If your Connext DDS distribution requires a license file, you will receive one from RTI via email.
If you have more than one license file from RTI, you can concatenate them into one file.
A single license file can be used to run on any architecture and is not node-locked. You are not required to run a license server.
Save the license file in any location of your choice; the locations checked by the middleware are listed below.
You can also specify the location of your license file in RTI Launcher's Configuration tab. Then Launcher can copy the license file to the installation directory or to the user workspace.
Each time your Connext DDS application starts, it will look for the license file in the following locations until it finds a valid license:
<participant_qos> <property> <value> <element> <name>dds.license.license_string</name> <value>contents of license file</value> </element> </value> </property> </participant_qos>
If the content of the license file is in XML, special characters for XML need to be escaped in the license string.1Special characters include: quotation marks ("), apostrophes ('), greater-than (>) and less-than (<) signs, and ampersands (&).
Example XML to set dds.license.license_file:
<participant_qos> <property> <value> <element> <name>dds.license.license_file</name> <value>path to license file</value> </element> </value> </property> </participant_qos>
Note: When you run any of the scripts in the <NDDSHOME>/bin directory, this automatically sets the RTI_LICENSE_FILE environment variable (if it isn't already set) prior to calling the executable. It looks for the license file in two places: your rti_workspace directory and the installation directory (NDDSHOME). (See Paths Mentioned in Documentation.)
As Connext DDS attempts to locate and read your license file, you may (depending on the terms of the license) see a printed message with details about your license.
If the license file cannot be found or the license has expired, your application may be unable to initialize Connext DDS, depending on the terms of the license. If that is the case, your application’s call to DomainParticipantFactory.create_participant() will return null, preventing communication.
If you have any problems with your license file, please email firstname.lastname@example.org.
If you are using a package type that requires a license file and your license file changes—for example, you receive a new license for a longer term than your original license—you do not need to reinstall Connext DDS.
However, if you switch from a license-managed distribution of Connext DDS to one of the same version that does not require license management, or visa versa, RTI recommends that you first uninstall your original distribution before installing your new distribution. Doing so will prevent you from inadvertently using a mixture of libraries from multiple installations.
© 2015 RTI
Open topic with navigation