RTI Persistence Service - Community RTI Connext Users
Contents
1. Environment Variables in XML Configuration Files This new feature allows you to refer to an environment variable within an XML tag When the Connext XML parser parses the configuration file it will expand the environment variable To refer to an environment variable use the format MY_VARIABLE For example lt element gt lt name gt The name is MY_NAME lt name gt lt value gt The value is MY_VALUE lt value gt lt element gt Attribute is_default_qos No Longer Supported The is_default_qos attribute is no longer supported in Persistence Service For more information please see Section 4 1 Support for Extensible Types Persistence Service includes partial support for the Extensible and Dynamic Topic Types for DDS specification from the Object Management Group OMG See Section 27 13 in the RTI Core Libraries and Utilities User s Manual for details Integrated Support for Distributed Logger The RTI Distributed Logger library is now included with Persistence Service When you enable the Distributed Logger library Persistence Service will publish its log messages to a Connext domain Then you can visualize the log message data with RTI Monitor a separate GUI application that can run on the same host as your application or on a different host Since the data is provided in a Connext topic you can also use rtiddsspy or even write your own visual ization tool For details on how to enable the D2. persistence_group gt For additional information on Durable Subscriptions see the RTI Persistence Service documenta tion in the RTI Core Libraries and Utilities User s Manual Delegated Reliability Support The delegated reliability feature offloads the reliability protocol tasks processing of NACK traffic and HB sending from the original DataWriter to one or more Persistence Service instances This feature is useful in slow consumers scenarios where a DataWriter should not slow down due to the presence of a matching slow DataReader in the system With delegated reliability a RELIABLE DataWriter configured with TRANSIENT or PERSIS TENT durability will communicate using BEST EFFORT channels with matching RELIABLE DataReaders Lost samples will be repaired by one or more instances of Persistence Service For additional information on Delegated Reliability see the RTI Persistence Service documenta tion in the RTI Core Libraries and Utilities User s Manual Sample Logging Support Sample logging allows you to decouple a PRSTDataReader from the corresponding PRSTDataW riter by buffering the read samples onto disk before they get persisted into the PRSTDataWriter queue Using the sample logging feature in combination with delegated reliability addresses slow consumers scenarios where you do not want to slow down the original DataWriter The sample logging feature is only supported on Linux and Windows platforms Related XML configurati
3. 00 i86Win32VS2005 Executable Windows Windows 2003 i86Win32VS2005 Executable i86Win32VS2005 Windows Vista 86Win32VS2008 Executable i i86Win32VS2005 Windows XP Professional Executable i86Win32VS2008 Command Line Options Compatibility Starting with version 4 5b the command line parameter srvName has been replaced with cfgName which is a required parameter Library API Compatibility The following fields in the RTI_PersistenceServiceProperty structure have new names starting in 4 5d Rev 12 L app name has been replaced with application name I stack_size has been replaced with thread_stack_size Persistent Storage When Persistence Service is configured in PERSISTENT mode you may choose between storing the topic data in files or in an external relational database In principle you can use any database that provides an ODBC driver since ODBC is a standard However not all ODBC databases support the same feature set Therefore there is no guarantee that the persistent durability features will work with an arbitrary ODBC driver Persistence Service has been tested with the MySQL 5 1 44 with MySQL ODBC 5 1 6 The usage of MySQL requires the separate installation of the MySQL ODBC 5 1 6 or higher driver For non Windows platforms the installation of UnixODBC 2 2 12 or higher is also required Persistence Service Synchronization Starting with version 5 0 0 the format of the lt sync
4. RTI Persistence Service Release Notes Version 5 0 0 t i Your systems Working as one 2012 Real Time Innovations Inc All rights reserved Printed in U S A First printing August 2012 Trademarks Real Time Innovations RTI DataBus and Connext are trademarks or registered trademarks of Real Time Innovations Inc All other trademarks used in this document are the property of their respective owners Copy and Use Restrictions No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc The software described in this document is furnished under and subject to the RTI software license agreement The software may be used or copied only under the terms of the license agreement Technical Support Real Time Innovations Inc 232 E Java Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website https support rti com Release Notes Table 1 1 Compatibility RTI Persistence Service is included with RTI Connext Professional Edition If you choose to use it it must be installed on top of RTI Connext formerly RTI Data Distribution Service with the same version number Persistence Service is compatible with Connext as well as RTI Data Distribution Service 4 5 b e 4 4d 4 3e and 4 2e it is supported on the archit
5. ectures listed in Table 1 1 Note Persistence Service is not compatible with applications built with RTI Data Distribution Ser vice 4 5e and earlier releases when communicating over shared memory For more information please see the Transport Compatibility section in the RTI Core Libraries and Utilities Release Notes Supported Architectures Platforms Operating System Architecture Format AIX 5 3 poAIX5 3xl1c9 0 al no external database support 64p5AIX5 3x1c9 0 Executable INTEGRITY INTEGRITY 10 0 0 pentiumInty10 0 0 pcx86 Library i86Linux2 6gcc4 1 2 CentOS 5 4 5 5 2 6 kernel x64Linwx2 6gcc4 1 2 Executable F i86Linux2 6gcc4 1 1 Red Hat Enterprise Linux 5 0 x64Linux2 6gcc4 1 1 Executable i i86Linux2 6gcc4 1 2 Linux Red Hat Enterprise Linux 5 1 5 2 5 4 5 5 x64Linux2 6gcc4 1 2 Executable Red Hat Enterprise Linux 6 0 6 1 i86Linux2 6gcc4 4 5 E tabl no external database support x64Linux2 6gcc4 4 5 xecutable Ubuntu Server 10 04 2 6 kernel i86Linux2 6gcc4 4 3 E tabl no external database support x64Linux2 6gcc4 4 3 eer i Solaris 2 10 sparcSol2 10gcc3 4 2 TM Solaris no external database support sparc64Sol2 10gcc3 4 2 Executable Table 1 1 1 2 1 3 1 4 Supported Architectures Platforms Operating System Architecture Format i86Win32VS2010 Windows 7 x64Win64VS2010 Executable Windows Server 2008 R2 x64Win64VS2010 Executable Windows 20
6. hronization gt tag value under lt persistence_service gt tag has changed Before 5 0 0 the value of the tag was a boolean indicating whether or not sample synchroniza tion was enabled Starting in 5 0 0 there are two different kinds of information that can be synchronized indepen dently data samples and durable subscription state The lt synchronization gt tag value is no lon ger a boolean now it is a complex value that may contain up to three new tags L lt synchronize_data gt I lt synchronize_durable_subscriptions gt I lt durable_subscription_synchronization_period gt Available Documentation 3 1 Any existing XML configuration files that use the old lt synchronization gt tag as follows lt dds gt lt persistence_service gt lt synchronization gt true lt synchronization gt lt persistence_service gt must be changed to lt dds gt lt persistence_service gt lt synchronization gt lt synchronize_data gt true lt synchronize_data gt lt synchronization gt lt persistence_service gt For additional information on Persistence Service synchronization see the RTI Persistence Service chapters in the RTI Core Libraries and Utilities User s Manual Available Documentation The following documentation is provided with the Persistence Service distribution The paths show where the files are located after Persistence Service has been installed in lt NDDSHOME gt 4 Installation ins
7. istributed Logger library see the chapter on Configuring Persis tence Service in the RTI Core Libraries and Utilities User s Manual as well as the RTI Distributed Log ger Getting Started Guide These documents will show you how to use the new XML configuration tag lt distributed_logger gt Propagation of Service Version as a DomainParticipant Property In this release the Persistence Service version number is propagated as a DomainParticipant prop erty called rti service version The format of the value is as follows lt major gt lt minor gt lt release gt rev lt revision gt The version property is set in all the DomainParticipants created by the service 4 1 5 2 5 3 What s Fixed in 5 0 0 Remote Administration Commands not Received Persistence Service did not ignore the is_default_qos setting in input XML files As a conse quence you may have seen unexpected behavior For example if remote administration was enabled you may have run into a scenario where the DataWriter and DataReader created by Per sistence Service to receive administration commands had PERSISTENT Durability This could have occurred when running Persistence Service from a directory that contained a file called USER_QOS_PROFILES xml with is_default_qos set to TRUE in a profile where the DataWriter and DataReader QoS had PERSISTENT durability Your original intention may have been to use USER_QOS_PROFILES xml to configure your application H
8. on tags L sample logging under lt persistence_group gt For additional information on using sample logging see the RTI Persistence Service documenta tion in the RTI Core Libraries and Utilities User s Manual Performance Improvements The following new XML tags can be used to improve the performance of RTI Persistence Service when it runs in PERSISTENT mode M lt late_joiner_read_batch gt L lt writer_ack_period gt I lt writer_checkpoint_period gt I lt writer_checkpoint_volume gt For additional information on these tags see the RTI Persistence Service documentation in the RTI Core Libraries and Utilities User s Manual Waitset Support RTI Persistence Service can be configured to use waitsets to read data from the PRSTDataReader using the new XML tag lt use_wait_set gt For additional information on this tag see the RTI Persistence Service documentation in RTI Core Libraries and Utilities User s Manual What s New in 5 0 0 3 6 3 7 3 8 3 9 3 10 3 11 Application Level Acknowledgment Starting with release 5 0 0 you can configure the PRSTDataWriters and PRSTDataReaders cre ated by RTI Persistence Service to do application level acknowledgment using the existing QoS tags lt datawriter_qos gt and lt datareader_qos gt under lt persistence_group gt For additional information on application level acknowledgment see the RTI Core Libraries and Utilities User s Manual Support for
9. owever because Persistence Ser vice runs from the same directory as the entities that it creates it used the application default profile as well To be consistent with RTI Routing Service and a provide a better out of the box experience the is_default_qos attribute is no longer supported in Persistence Service RTI Issue ID PERSISTENCE 56 Known Issues TCP Transport not Supported Persistence Service does not support the TCP transport Coherent Changes are Not Propagated as a Coherent Set Persistence Service will propagate the samples inside a coherent change However it will propa gate these samples individually not as a coherent set BLOBs Not Supported by OBDC Storage The ODBC storage does not support BLOBs The maximum size for a serialized sample is 65535 bytes in MySQL
10. tructions RTI Persistence Service Installation Guide lt NDDSHOME gt doc pdf RTI_Persistence_Service_InstallationGuide pdf also avail able for download from RTI s Self Service Portal L General information on RTI Persistence Service Open lt NDDSHOME gt ReadMe html then select RTI Persistence Service L Example code lt NDDSHOME gt example lt language gt helloWorldPersistence Additional documentation is provided with Connext E Configuration use cases and execution of Persistence Service RTI Core Libraries and Utilities User s Manual lt NDDSHOME gt doc pdf RTI_CoreLibrariesAndUtilities_UsersManual pdf Overview of persistence and durability features Open lt NDDSHOME gt ReadMe html choose your desired API C C or Java then select Modules Connext API Reference Durability and Persistence What s New in 5 0 0 Durable Subscriptions Support With the Durable Subscriptions feature you can configure Persistence Service to keep samples in memory or persistent storage until they are received by a set of named subscriptions Related XML configuration tags 1 lt durable_subscriptions gt under lt participant gt L lt purge_samples_after_acknowledgment gt under lt persistence_service gt 3 2 3 3 3 4 3 5 I lt synchronize_durable_subscriptions gt and lt durable_ subscription synchronization_ period gt under lt synchronization gt I lt allow_durable_subscriptions gt under lt
Download Pdf Manuals
Related Search