RTI Routing Service - Community RTI Connext Users
Contents
1. Server 10 04 2 6 kernel i x64Linux2 6gcc4 4 3 i i86Win32VS2005 Windows 7 i86Win32VS2008 Windows Server 2008 R2 i i86Win32VS2010 Windows Windows 2003 x64Win64VS2005 Windows Vista 2 i x64Win64VS2008 Windows XP Professional x64Win64VS2010 RTI Routing Service is built on top of and intended for use with RTI Data Distribution Service 4 5d Release Notes 2 1 2 2 Compatibility RTI Data Distribution Service Compatibility With the built in DDS adapter this RTI Routing Service release can be used to forward and transform data between DDS applications built with RTI Data Distribution Service 4 5d 4 5c 4 5b 4 4d 4 3e and 4 2e RTI Data Distribution Service 4 2e Compatibility If the applications data types contain 8 byte or larger primitive types double long long unsigned long long or long double RTI Routing Service will have to be run with the command line option use42eAlignment in order to be compatible with RTI Data Distribution Service 4 2e If the applications use large data RTI Routing Service must be configured with the fol lowing properties set to 1 in order to be compatible with RTI Data Distribution Service 4 2e L dds data_writer protocol use_43_large_data_format L dds data_reader protocol use_43_large_data_format RTI Data Distribution Service 4 3e Compatibility If the applications use large data RTI Routing Service must be configured with the fol2. fits of using RTI Routing Service l Users Manual RTI_Routing_Service_UsersManual pdf Describes how to con figure RTI Routing Service and use it remotely 8 Custom Supported Platform RTI Routing Service is also supported on the platform listed in Table 8 1 this is a target platform for which RTI offers custom support If you are interested in this platform please contact your local RTI representative or email sales rti com Table 8 1 Custom Supported Platforms RTI Architecture Operating System CPU Compiler Abbreviation Sourcery G Lite Mistral Linux Kernel 2 6 32 ARMv7 2009q3 67 gcc 4 4 1 armv7 leLinux2 6gcc4 4 1
3. 1 1 What s Fixed in Release 2 0 2 Error Parsing XML File with lt query_condition_allocation gt In the previous release if you used an XML configuration file that included a lt query_condition_allocation gt tag RTI Routing Service reported the following error RTIXMLParser_onStartTag Parse error at line 435 Unexpected tag query_condition_allocation This problem has been resolved the lt query_condition_allocation gt tag is now sup ported RTI Bug 13704 Possible Error in DataWriters with Durable Writer History after Restart If the property dds data_writer history odbc_plugin in_memory_state was set to 1 and you restarted a durable DataWriter you may have seen the following error after new samples were published PERSISTENCEServiceTopic_onDataAvailable write This problem has been resolved RTI Bug 13551 Previous Releases What s New in Release 2 0 1 New Example Adapters in C and Java To support integration with non DDS systems RTI Routing Service provides an API to develop custom adapters There is an API for C adapters and an API for Java adapters An adapter is a pluggable component that allows RTI Routing Service to consume and produce data for different data domains By default RTI Routing Service is distributed with a built in DDS adapter To serve as examples and to provide a base for building your own custom adapters the source code for three other adapters is provided with t
4. RTI Routing Service for RTI Data Distribution Service Release Notes Version 2 0 2 RT The Global Leader in DDS 2011 Real Time Innovations Inc All rights reserved Printed in U S A First printing re TI Jan 2011 Trademarks Real Time Innovations and RTI are 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 385 Moffett Park Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website https support rti com Contents T Supported Platt LIONS isisasesensxcesussscscenasasseavsssasieavsssssassauaiscuaacusvesnsucesasonsguveeddacasconnasesssyens 1 2 re ARNE AY seas ccscued iets etc thctoenaen siesta ean etaesiat one hawt eeamniii ea iveretatiieuns 2 2 1 RTI Data Distribution Service Compatibility cccccccccsceseeseseeneteeceeecesssestaneesesesneeeseeeenes 2 2 2 Command Line Options Compatibility 0 0 cece ce
5. apters see Chapter 7 in the RTI Routing Service User s Manual Publication with Original Timestamp There is a new tag called lt publish_with_original_timestamp gt under lt route gt lt topic_route gt lt auto_route gt and lt auto_topic_route gt This tag allows RTI Routing Ser vice to publish samples with their original timestamp For more details see Chapter 2 in the RTI Routing Service User s Manual What s Fixed in Release 2 0 0 RTI Routing Service Crashed if lt registered_type_name gt Missing in lt topic_route gt If the tag lt registered_type_name gt is missing within lt topic_route gt RTI Routing Service should report an error However in the previous release it resulted in a crash This problem has been resolved RTI Bug 13245 6 Known Issues 6 1 6 2 6 3 6 4 Known Issues Limitations in Adapter API In the Adapter API Connection get_attributes and update operations are currently not supported Sequences of Transformations in a Route are Not Supported The tag lt transformation_sequence gt within a lt topic_route gt is not supported In this version only one transformation per route is supported Assignment Data Transformation only Supports Assignment of Primitive Fields Not Part of Arrays or Sequences The data transformation library distributed with RTI Routing Service only supports the assignment of primitive fields including strings that are not part of arrays or
6. csssescsesscessesscssuscecesssceseeseesssseeeesesesessseasseees 10 6 Known ISSUEG cccccccccccececececccccecececccececececeeececececececescecscscscscsesesesesescsesesescscseseeescecs 11 6 1 Limitationsin Adapter AP Iic ceccsecscsedscsscrevecentsberedvecsgsessgeeedsessesersdieususisecdevessarsdbnedincsesebsieveasvessess 11 6 2 Sequences of Transformations in a Route are Not Supported cccceeseneseeeeeesteneneees 11 6 3 Assignment Data Transformation only Supports Assignment of Primitive Fields Not Part of Arrays or Sequences cceseeecesseeseseesenesesesesesseseseseseeeeesees 11 6 4 Asymmetric Communication Scenarios Not Supported with TCP Transport 000 11 7 Available Documentation ssooesssoossssoossssesesesesssssssoosssoossssooesssoosesssseoesssoossssoosee 12 8 Custom Supported PlatforM ss isissssssisssssssscseosssesressssesossssssisstasasesesiseroresssssinnsiis 12 Release Notes 1 Supported Platforms RTI Routing Service is currently supported on these platforms Table 1 0 Supported Platforms Platform Operating System Architecture i86Linux2 6gcc4 1 2 CentOS 5 4 5 5 2 6 kernel i x64Linux2 6gcc4 1 2 Red Hat Ent ise Li 40 i86Linux2 6gcc3 4 3 a mesa x64Linux2 6gcc3 4 5 Linux Red Hat Ent ise Li 50 i86Linux2 6gcc4 1 1 DS D a a x64Linux2 6gcc4 1 1 Red Hat Ent ise Li 5152 54 55 i86Linux2 6gcc4 1 2 Seer E E dereree x64Linux2 6gcc4 1 2 i86Linux2 6gcc4 4 3 Ubuntu
7. efault is DDS_LENGTH_UNLIMITED no dynamic memory the max sample size is pre allocated L sample_buffer_trim_to_size If set to true after allocating dynamic memory for big samples that memory will be release when possible If false that memory will not be released but kept for future samples if needed The default is false This new feature is useful when a data type has a very high maximum size e g mega bytes but most of the samples sent are much smaller than the maximum possible size e g kilobytes In this case the memory footprint is reduced dramatically while still correctly handling the rare cases in which very large samples are published Support for Comma Separated Filters in Auto Routes This release adds support for comma separated filters in auto routes Previously you could only enter one filter name per tag such as lt allow_topic_name_filter gt MyTopic lt allow_topic_name_filter gt Now you can enter multiple filter names separated by commas For example lt allow_topic_name_filter gt MyTopic AnotherTopic lt allow_topic_name_filter gt Comma separated lists of filters are now supported in the following tags I lt allow_topic_name_filter gt L lt deny_topic_name_filter gt I lt allow_registered_topic_name_filter gt L lt deny_registered_topic_name_filter gt I lt allow_stream_name_filter gt L lt deny_stream_name_filter gt RTI Bug 13699 Release Notes 4 1 4 2 5 1 5
8. his release l A file adapter implemented in C 5 Previous Releases 5 2 5 2 1 5 2 2 5 2 3 L A TCP socket adapter implemented in C 1 A JMS adapter implemented in Java For more details about adapters see Chapter 7 in the RTI Routing Service User s Manual To start compiling and using the distributed adapters see the RTI Routing Service Getting Started Guide Ability to Execute RTI Routing Service Shell Commands from a File In addition to reading commands from the prompt the remote shell can read and exe cute commands from a file To specify such a file use the new command line option cmdName A command file may contain any number of commands one per line exactly as they would be entered in the shell prompt For convenience a new command has been introduced to sleep between the execution of other commands sleep lt seconds gt What s Fixed in Release 2 0 1 Topic Routes May Fail to Start when TypeCode was not propagated In the previous release if the matching publications or subscriptions of a topic route did not propagate their typecode and that topic route was configured with the ON_DOMAIN_MATCH creation mode it would never start even if the type was defined in the XML file This problem has been resolved now the propagation of the typecode is not strictly required when the type is defined in XML RTI Bug 13177 Field Assignment Transformation did not Support Typedefs The transforma
9. igher I Starting with RTI Routing Service 2 0 0 the way to register and configure transfor mations in the configuration file has changed e The tag lt transformation_class_library gt has been replaced with lt transformation_library gt e The tag lt transformation_class gt has been replaced with lt transformation_plugin gt e The content of these tags has also changed With the new configuration there is only a single entry point to the library For example lt transformation_library name MyTransfLib gt lt transformation_plugin name MyTransfPlugin gt lt dll gt mytransformation lt dll gt lt create_function gt lt Entry point gt MyTransfPlugin_create lt create_function gt lt transformation_plugin gt lt transformation_library gt e The configuration of a transformation within lt route gt is done using prop erties instead of the lt expression gt and lt parameter gt tags For example lt transformation plugin_name TransformationLib Assignment gt lt property gt lt value gt lt element gt lt name gt X lt name gt lt value gt Y lt value gt lt element gt Release Notes lt element gt lt name gt Y lt name gt lt value gt X lt value gt lt element gt lt value gt lt property gt lt transformation gt e The configuration of the assignment transformation distributed with RTI Routing Service is now done with properties For example Before 2 0 0 lt
10. lowing properties set to 1 in order to be compatible with RTI Data Distribution Service 4 3e L dds data_writer protocol use_43_large_data_format L dds data_reader protocol use_43_large_data_format Mixing Different RTI Data Distribution Service Versions This RTI Routing Service version can be used simultaneously with applications built using RTI Data Distribution Service 4 5d 4 5c 4 5b 4 4d 4 3e and 4 2e unless special con figuration is required as described above Command Line Options Compatibility Starting with RTI Routing Service 1 1 0 the command line parameter srvName has been replaced with cfgName to select a configuration and appName to name the service execution In previous RTI Routing Service versions the srvName parameter was not required However in this version the equivalent parameter cfgName is required 2 Compatibility Also starting with RTI Routing Service 1 1 0 the allowed values for the verbosity com mand line option changed The new verbosity option coalesces the old verbosity and ddsVerbosity options into a single parameter For additional information about command line options see Chapter 3 in the RTI Rout ing Service Getting Started Guide 2 3 XML Compatibility I Starting with RTI Routing Service 1 1 0 the attribute name in the lt routing_service gt tag is now required Old XML files without the name attri bute will not be parsed by RTI Routing Service 1 1 0 and h
11. sequences For example lt transformation className TestTransformationLib FieldMapping gt lt expression gt lt expression gt lt parameter gt position x position y lt parameter gt lt This is supported gt lt parameter gt x y lt parameter gt lt This is supported gt lt parameter gt x 0 y 0 lt parameters gt lt This is not supported gt lt parameter gt position position lt parameter gt lt This is not supported gt lt transformation gt For additional details about data transformation see Chapter 3 in the RTI Routing Ser vice User s Manual Asymmetric Communication Scenarios Not Supported with TCP Transport This version of RTI Routing Service does not support the TCP transport modes NDDS_TRANSPORT_TCPV4_TRANSPORT_MODE_CLIENT and NDDS_TRANSPORT_TCPV4_TRANSPORT_MODE_SERVER For additional details about asymmetric communication scenarios see Chapter 6 in the RTI Routing Service User s Manual Release Notes 7 Available Documentation RTI Routing Service documentation includes L Release Notes RTI_Routing_Service_ReleaseNotes pdf Describes system requirements and compatibility as well as any version specific changes and known issues L Getting Started Guide RTI_Routing_Service_GettingStarted pdf Highlights the benefits of RTI Routing Service It provides installation and startup instruc tions and walks you through several examples so you can quickly see the bene
12. sessseeeeeceeneesesescsessesesesessseseseneseeneseseess 2 239 MMU COMP ati Oia tyccessieccectsveeesccnstvcssecsnscvesiedtesgsatatve sas cossdnsuansutestedensaselescestanessecestviisdesssbvtaesacendssesven 3 2A TranstormiatiOr A Pl sccssisc ssid isa2 oshcsieazeesic a A A E E e aN EEEE ENAA AEAEE nieas 4 3 Whats New in Release 2 0 2 eeessooessooesssooesssooesesesosesssoosessoossssooesesoosessseossssooesssoosse 6 3 1 Configurable Memory Management c cccccsccsssesssesseeeececesesescsnansnesesesceeseseeceenesesnsneeeneness 6 3 2 Support for Comma Separated Filters in Auto Routes ccccescesesceesseesestenetesesceesescseanenenees 7 4 What s Fixed in Release 2 0 2 ssooesssooesssooesssooeeessscsesssooesssoossssooesesoosesssoossssoossssooese 8 4 1 Error Parsing XML File with lt query_condition_allocation gt cccccceee cesses tseeeeeeeeees 8 4 2 Possible Error in DataWriters with Durable Writer History after Restart cccceee 8 5 Previous ROlCAGCS saisiseviasecostisdetesunssuseancevssszoeisseveieeikes eases ecatusreennminion Gaines 8 5 1 What s New in Release 2 0 1 ccccccceccccsssccccsssccsssscecsssccscesseceeceseesseceesssessessecsesesesesseseeeesesneseeuass 8 52 What s Fixed in Release 2 00 avissem deii eie daii iea a 9 53 Whats New in Release 2 00 vice cic inccec cssteesvenslacedandeeskescosBeeauescddeedariecneveds EEE ETEC aae E SEEE EEEE 10 54 What s Fixed in Release 2 0 0 w ccecccccccsscssssssscssescssssse
13. t lt transformation_plugin gt lt transformation_library gt The following table shows how deprecated functions map to the new API 2 0 0 API rti_routingservice h 2 0 1 and Higher API routingservice_ transformation h Comments RTITransformationClass_ loadFnc RTI_RoutingServiceTransformation Plugin_CreateFcn This is the entry point function RTITransformationClass_ unloadFnc Function declaration RTI_RoutingServiceTransformation Plugin_DeleteFcn Member in Plugin struct transformation_plugin_delete RTITransformationClass_ createFnc Function declaration RTI_RoutingServiceTransformation Plugin_CreateTransformationFcn Member in Plugin struct transformation_plugin_create_ transformation RTITransformationClass_ deleteFnc Function declaration RTI_RoutingServiceTransformation Plugin_DeleteTransformationFcn Member in Plugin struct transformation_plugin_delete_ transformation Release Notes 2 0 0 API rti_routingservice h 2 0 1 and Higher API routingservice_ transformation h Comments RTITransformationClass_ modifyFnc Function declaration RTI_RoutingServiceTransformation_ UpdateFcn Member in Plugin struct transformation_update RTITransformationClass_ Function declaration RTI_RoutingServiceTransformation_ TransformFcn In the new API the transform function accept multiple samples In addition
14. the output Member in Plugin structure transformation_return_loan transformEnc samples must be created Member in Plugin struct by the transformation transformation_transform instead of being passed in by RTI Routing Service Function declaration ae RTI_RoutingServiceTransformation_ This function is used to none ReturnLoanFcn return the loan on the samples returned by the transform function What s New in Release 2 0 2 3 1 Configurable Memory Management This release adds support for a new configuration tag lt memory_management gt This tag allows you to configure certain DDS internal memory allocation aspects The config uration is per domain_route s participant and therefore affects all the contained DDS readers and DDS writers For example lt domain_route name test gt lt participant_1 gt lt domain_id gt 0 lt domain_id gt lt memory_management gt lt sample_buffer_min_size gt X lt sample_buffer_min_size gt 3 What s New in Release 2 0 2 3 2 lt sample_buffer_trim_to_size gt true lt sample_buffer_trim_to_size gt lt memory_management gt lt participant_1 gt L sample_buffer_min_size For all DDS readers writers the way DDS allocates memory for samples is as follows DDS preallocates space for samples up to size X in the reader and writer queues If a sample has an actual size greater than X then for that sample the memory is allocated dynamically The d
15. tion that assigns fields from one sample to another sample did not sup port fields of a typedef d type This problem has been resolved RTI Bug 13286 Parsing Failure in USER_ROUTING_SERVICE xml file May Have Lead to Segmentation Fault If a parsing error was found in USER_ROUTING_SERVICE xml RTI Routing Service would report warning about the parsing error and continue This lead to errors during execution that sometimes resulted in a segmentation fault In this release parsing errors in USER_ROUTING_SERVICE xml are considered a failure condition instead of a warn ing and execution will not continue Release Notes 5 2 4 5 3 5 3 1 5 3 2 5 4 5 4 1 RTI Bug 13407 Using Multiple lt participant_1 2 gt Tags not Reported as an Error In the previous release RTI Routing Service s XML parser did not report the use of multi ple lt participant_1 gt lt connection_1 gt or lt participant_2 gt lt connection_2 gt tags in the same lt domain_route gt as a configuration error These errors will now be caught by the parser RTI Bug 13463 Whats New in Release 2 0 0 Adapter API To support integration with non DDS systems RTI Routing Service provides an API to develop custom adapters An adapter is a pluggable component that allows RTI Routing Service to consume and produce data for different data domains By default RTI Routing Service is distributed with a built in DDS adapter For more details about ad
16. transformation className TransformationLib Assignment gt lt expression gt lt expression gt lt parameter gt position x position y lt parameter gt lt parameter gt x 10 lt parameter gt lt transformation gt In 2 0 0 and higher lt transformation plugin_name TransformationLib Assignment gt lt property gt lt value gt lt element gt lt name gt position x lt name gt lt value gt position y lt name gt lt element gt lt element gt lt name gt x lt name gt lt value gt 10 lt name gt lt element gt lt value gt lt property gt lt transformation gt 2 4 Transformation API The transformation API of RTI Routing Service 2 0 1 and higher is not compatible with the API of previous releases 2 0 0 and lower The new API follows the same model as the adapter API see Section 5 3 1 which intro duced the concept of a Plugin as a C structure that contains all the function pointers that implement the interface The registration of a transformation plugin with the new model requires a single entry point to the shared library the entry point is a function that creates the Plugin structure which contains the implementation 2 Compatibility For example lt transformation_library name MyTransfLib gt lt transformation plugin name MyTransfPlugin gt lt dll gt mytransformation lt dll1 gt lt create_function gt lt Entry point gt MyTransfPlugin_create lt create_function g
Download Pdf Manuals
Related Search