Deploying Infrastructure Services

Submitted by rose on Fri, 07/24/2015 - 18:02

If you are using version 5.2.0 or higher and want to deploy one of RTI’s infrastructure services, such as Routing Service, Persistence Service or Recording Service, these are the files you need from inside your rti_connext_dds-<version> installation directory:

Required

  • Executables
    • resource/app/bin/<arch>/rti<service>[.exe]: The service application
  • Shared libraries used by the services
    • If the application you are deploying runs on your host platform: resource/app/lib/<arch>
    • If the application you are deploying runs on a target platform: lib/<arch>
  • Configure your library path to point to wherever you deploy the shared libraries (LD_LIBRARY_PATH or PATH).

Optional Configuration

  • resource/xml/<RTI_SERVICE_EXAMPLE>.xml: The default XML QoS configuration files used by the service

Optional scripts

Only available if you are deploying the same platform as your host.

  • bin/rtiserviceexample[.bat]: The script that sets up the environment variables for shared libraries is in the bin/ directory.  You can run the application without this script, but you will need to configure library paths.
  • resource/scripts/rticommon[.sh/.bat]: Called by the services’ scripts as a general way to set environment variables consistently.  If you are running using the scripts in bin/, those scripts expect this to be in a known relative path.
  • resource/scripts/rticommon_config[.sh/.bat]: If you deploy the script in bin/ and the rticommon script, you will also need to deploy this script, and you will have add the following line that disables copying the workspace:
    # resource/scripts/rticommon_config.sh
copy_workspace=false  
    @REM resource/scripts/rticommon_config.bat
set copyWorkspace=false

Note: To know which platforms are supported as Host or Target, take a look at the Platforms Notes of your RTI Connext version.

Product:
Keywords: