RTI Routing Service - Community RTI Connext Users
Contents
1. 2 0 1 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 Previous API rti_routingservice h 2 0 1 API routingservice_ transformation h Comments modifyFnc RTITransformationClass_ 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 the output transformFnc Member in Plugin struct safples must be created f on anslo by the transformation transiormation instead of being passed in by RTI Routing Service2. Release Notes
3. 5 3 1 5 3 2 5 4 5 4 1 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 What s New in Release 1 1 0 Command Line Options RTI Routing Service 1 1 0 introduces the following command line options L cfgName Selects a routing service configuration This option is required except when remoteAdministrationDomainId and noAutoStart are used appName Assigns a name to the execution of the RTI Routing Service The new command line options cfgName and srvName replace the now deprecated srvName option of previous releases The deprecated option is still functional to preserve backwards compatibility However it should not be used as it may not be available in future releases The allowed values for the verbosity command line option have 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 New Ways to Load Configuration Files This RTI Routing Service release can load its configuration from one additional location L lt working directory gt
4. Function declaration f RTI_RoutingServiceTransformation_ This function is used to none ReturnLoanFen return the loan on the samples returned by the Member in Plugin structure transform function transformation_return_loan 3 What s New in Release 2 0 1 This section describes what s new since the previous release 2 0 0 3 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 this release LL A file adapter implemented in C 4 What s Fixed in Release 2 0 1 3 2 4 1 4 2 L A TCP socket adapter implemented in C L 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 fil
5. gt lt parameter gt x 10 lt parameter gt lt transformation gt In this release 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 this RTI Routing Service release is not compatible with the API of previous releases The new API follows the same model as the adapter API see Section 5 1 1 where we introduced the concept of 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 For example 2 Compatibility 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 gt lt transformation_plugin gt lt transformation_library gt The following table shows how deprecated functions map to the new API Previous API rti_routingservice h
6. 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 this release lt transformation className TransformationLib Assignment gt lt expression gt lt expression gt lt parameter gt position x position y lt parameter
7. RTI Routing Service for RTI Data Distribution Service Release Notes Version 2 0 1 RTD 2010 Real Time Innovations Inc All rights reserved Printed in U S A First printing re TI June 2010 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 http www rti com support 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 cesessseeeeeceeneesesesc
8. USER_ROUTING_SERVICE xml This file is loaded automatically if it exists For additional information about configuration loading see Section 2 2 in the RTI Rout ing Service User s Manual What s Fixed in Release 1 1 0 RTI Routing Service May Not Discover DDS Entities if Domain Route Disabled then Enabled In the previous release if a Domain Route was disabled and then re enabled RTI Rout ing Service did not always discover all the DDS entities In this situation topic routes may not have been created This problem has been resolved RTI Bug 13187 Release Notes 6 1 6 2 6 3 6 4 Known Issues Short term Limitations This issue will be fixed in the next release I In the Adapter API Connection get_attributes and update operations are 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 sequences For example lt transformation className TestTransformationLib FieldMapping gt lt expression gt lt expression gt lt parameter gt position x positio
9. e 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 This section describes bugs that have been fixed since the previous release 2 0 0 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 transformation 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 Release Notes 4 3 4 4 5 1 5 1 1 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 sometime
10. e 2 0 0 cc ic icocdsvasche lt aies gee sles cach iapetccdas cedecegussniaesetarsecsvancstseaesaeedesdeedestecenve 9 53 What s New in Released 100 6 2 ictiaiie tia estcsiasciddin ciated ahead 9 5 4 What s Fixed in Release 1 1 0 ccccecccsscsesssessecsecsecsecsecsssesesesessesescsseeeseeseecseeseesaeceeesaseeeseeseneeaee 9 G Rito Wit FSS EET apse ET east eta 10 6 1 Short term Limitations eiiis a i a a E a ea aaa RA 10 6 2 Sequences of Transformations in a Route are Not Supported ss sssssriisrssesrtssterstsssserstsnte 10 6 3 Assignment Data Transformation only Supports Assignment of Primitive Fields Not Partof Arrays 0r Sequences lt ciscsiccseusssssossetsesecbaseutictsdedeteuestibseseudcatestssessaatevscacvacestuvseseoes iai 10 6 4 Asymmetric Communication Scenarios Not Supported with TCP Transport 0 10 7 Available Documentation sesesesssssesocssesesscesescescesescesoeccscescecessesessesseseesosseseesseeess 11 Release Notes 1 Supported Platforms RTI Routing Service is currently supported on these platforms Table 1 0 Supported Platforms Platform Operating System Architecture i86Linux2 6gcc3 4 3 Red Hat Enterprise Linux 4 0 2 6 kernel i x64Linux2 6gcc3 4 5 i86Linux2 6gcc4 1 1 Linux Red Hat Enterprise Linux 5 0 2 6 kernel x64Linux2 6gcc4 1 1 i86Linux2 6gcc4 1 2 Red Hat Enterprise Linux 5 1 5 2 2 6 kernel x64Linux2 6gcc4 1 2 i86Win32VS2005 Window
11. n 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 7 Available Documentation 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 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 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
12. rotocol 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 5c 4 5b 4 4d 4 3e and 4 2e unless special configu ration 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 The allowed values for the verbosity command line option have changed The new verbosity option coalesces the old verbosity and ddsVerbosity options into a single parameter For additional information about the new command line options see Chapter 3 in the RTI Routing 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 higher 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
13. s 7 nod s mane i86Win32VS2008 tees eens a i86Win32VS2010 meee Os x64Win64V 2005 Windows Vista x64Win64VS2008 Windows XP Professional x64Win64VS2010 RTI Routing Service is built on top of and intended for use with RTI Data Distribution Service 4 5c 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 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 fol lowing properties set to 1 in order to be compatible with RTI Data Distribution Service 4 3e L dds data_writer p
14. s 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 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 Previous Releases 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 adapters 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 5 Previous Releases 5 2 5 2 1 5 3
15. sessesesesessseseseneseeneseseess 2 239 KMUCOMpati Oia tysccassiesccctsceeesccestvcasecsnsctesedtesgsotatve sas cotsdnsuansutestedensaselescestanessecestvits dessstvtietacendssesven 3 2A Transformation APD esseci scn levee dacs aaa aeai aa iiae orir aiaei iai 4 3 What s New in Release 2 0 1 seesosseoossescescssesessossesecssescescesescesoeseeccsceccssesessosseseesssse 6 3 1 New Example Adapters in C and Java c ceccsccsceccsescesescsnsnseseseseesesescecensseseseanenesescecenssessseaanenens 6 3 2 Ability to Execute RTI Routing Service Shell Commands from a File cccccee eee 7 4 What s Fixed in Release 2 0 1 o sccceccvecseaderssscoscueasontiscausexturstentevestesucwectocssewestentonsaucoxers 7 4 1 Topic Routes May Fail to Start when TypeCode was not propagated cccceeeeseteseeees 7 4 2 Field Assignment Transformation did not Support Typedefs cccccceeesescsssesesescseneseeeeees 7 4 3 Parsing Failure in USER_ROUTING_SERVICE xml file May Have Lead to DESMEMCALON Paultre EAEE EEEn E EEEO ETE ERS e EEE EEEE AEE 8 4 4 Using Multiple lt participant_1 2 gt Tags not Reported as an Error sssssssssseisssessesiesissreseesses 8 5 PREVIOUS ROLCASES sects oe eccconssnctincincceiocuend deste ckustatontensc tzondvetvaed cdusshodevacuenieeveecenttbndiaacens 8 5 1 What s New ini Release 2 0 0 vssecsczscescaceisncseedsevescexiecsstesevsveveaessaceevetvesvestvectesacescesveteieedecua tease besotents 8 5 2 What s Fixed ar Releas
Download Pdf Manuals
Related Search