Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_middleware
-
Labels:
-
Team:Telescope and Site
-
Urgent?:No
Description
There are a few env vars that ADLink uses that aren't in the config file. Right now I am documenting them in ts_salobj but I think the information would be better in ts_ddsconfig. It might want to go in a separate subsection of the user guide than the ones supported in the config files, but if so, please check the existing entries for any that aren't actually in the config files, since they belong with these:
Here are the ones I know about. The information is from ts_salobj (with a few tweaks to OSPL_URI):
* ``ADLINK_LICENSE`` points to directory containing your `Vortex OpenSplice`_ license.
|
Required if using the licensed version of `Vortex OpenSplice`_; ignored otherwise.
|
Example value: ``/opt/ADLINK/Vortex_v2/Device/VortexOpenSplice/6.10.3/HDE/x86_64.linux/etc``
|
* ``OSPL_HOME`` (required) directory of the `Vortex OpenSplice`_ software.
|
This directory should contain subdirectories ``bin``, ``include``, ``lib``, etc.
|
Example: ``/opt/OpenSpliceDDS/V6.9.0/HDE/x86_64.linux``.
|
* ``OSPL_URI`` (required) a URI pointing to the main DDS configuration file
|
(one of the config files in this package). Example value:
|
file:///opt/OpenSpliceDDS/V6.9.0/HDE/x86_64.linux/etc/config/ospl.xml
|
Reviewed on github. The new information seems clear to me.