|
RTI Persistence Service Version 7.6.0
|
This document contains:
For additional information, please see the following PDF documents:
Please do not hesitate to contact RTI with questions or comments about this release. We welcome any input on how to improve RTI Persistence Service to suit your needs.
RTI Persistence Service is an optional package that saves data samples so that they can be delivered to subscribing applications that join the system at a later time – even if the publishing application has already terminated.
RTI Persistence Service runs as a separate application; you can run it on the same node as the publishing application, the subscribing application, or some other node in the network.
When configured to run in PERSISTENT mode, RTI Persistence Service uses the filesystem to persist data samples. For each persistent topic, it collects all the data written by the corresponding persistent DataWriters and stores them into persistent storage.
When configured to run in TRANSIENT mode, RTI Persistence Service stores the data in memory.
To use RTI Persistence Service in your RTI Connext Messaging application, you need to modify the DURABILITY QosPolicy of the DataReader and/or DataWriter. You may optionally modify the DURABILITY_SERVICE QosPolicy, which can be used to configure RTI Persistence Service.
For more information, please see RTI Persistence Service, in the Core Libraries User's Manual.
You can run RTI Persistence Service on any node in the network; it does not have to be run on the same node as the publishing or subscribing applications for which it is saving/delivering data. If you run RTI Persistence Service on a separate node, however, make sure that the other applications can find it during the discovery process – that is, it must be in one of the NDDS_DISCOVERY_PEERS lists.
A script to run the RTI Persistence Service executable is located in $NDDSHOME/bin.
For details, see Running RTI Persistence Service, in the Core Libraries User's Manual.
A simple example is available to show the how data can be persisted with RTI Persistence Service.
C: See the example in <path to examples>/persistence_service/c/hello_world_persistence.
C++: See the example in <path to examples>/persistence_service/c++/hello_world_persistence.
Java: See the example in <path to examples>/persistence_service/java/hello_world_persistence.
"path to examples" is your rti_workspace directory, which is in your Windows documents folder, Linux home/<your user name> directory, or macOS Users/<your user name> directory.
See Configuring Persistence Service, in the Core Libraries User's Manual, for complete information.
Persistence can be deployed as a C library linked into your application in selected architectures.
Refer to the Platform Notes for the list of supported architectures.
You can configure, start, and stop the service using the API described here: