Home

RTI Routing Service

1. Parameters to a content filter are optional This issue did not affect the execution of Routing Service It only affected users that included the XSD file in their XML editors RTI Issue ID ROUTING 64 Bug 13848 Compiler Errors for Java Applications using Remote Administration Topics Because the Java keyword final was used as a field name in the topics for remote administra tion RoutingServiceAdministration idl Java applications that used these topics to remotely administer Routing Service failed to compile This problem has been resolved by changing the field name to is_final RTI Issue ID ROUTING 61 Bug 13486 Save Command did not Save Configurations in RTI ROUTING _SERVICE xml The remote command save did not save the lt routing_service gt configuration tags in the file RTI_LROUTING_SERVICE xml and may have generated a configuration file that was empty except for lt dds gt tags This problem has been resolved now when a tag in RTI_LROUTING_SERVICE xml is being used it will be saved when Routing Service receives a save command RTI Issue ID ROUTING 82 Monitoring Failed in Routing Service if lt memory_management gt Tag Used When enabling Monitoring in Routing Service Connext would fail to publish information about a DataWriter if the tag lt memory_management gt was included in the same participant where mon itoring was enabled This problem has been resolved RTI Issue ID ROUTING 90 Using disa
2. name in the lt routing_service gt tag is now required Old XML files without the name attribute will not be parsed by Routing Service 1 1 0 and higher LI Starting with Routing Service 2 0 0 the way to register and configure transformations 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 d11 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 properties 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 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 a
3. 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 2 0 0 API 2 0 1 and Higher API rti_routingservice h routingservice_transformation h COMME RTITransformationClass_ RTI_RoutingServiceTransformation loadEnc Plugin_CreateFen This is the entry point function Function declaration RTI_RoutingServiceTransformation RTITransformationClass_ Plugin_DeleteFcn unloadFnc Member in Plugin struct transformation_plugin_delete Function declaration RTI_RoutingServiceTransformation RTITransformationClass_ Plugin_CreateTransformationFcn createFnc Member in Plugin struct transformation_plugin_create_ transformation Function declaration RTI_RoutingServiceTransformation RTITransformationClass_ Plugin_DeleteTransformationFcn deleteFnc Member in Plugin struct transformation_plugin_delete_ transformation What s New in 5 0 0 4 1 4 2 4 3 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_RoutingServi
4. rti routing_service administration command_request and rti routing_service administration command_response can now act as requests and replies respectively The new Requester object makes it extremely simple to write a user application that remotely controls Routing Service See the Routing Service User s Manual Section 5 3 Accessing Routing Service from a Connext Application for example code Integrated Support for Distributed Logger The RTI Distributed Logger library is now included with RTI Routing Service When you enable the Distributed Logger library Routing Service will publish its log messages to Connext Then you can visualize the log message data with RTI Monitor a separate GUI applica tion 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 visualization tool For details on how to enable the Distributed Logger library see the chapter on Configuring Routing Service in the RTI Routing Service User s Manual as well as the RTI Distributed Logger Getting Started Guide These documents will show you how to use the new XML configuration tag lt distributed_logger gt New paused Field for Route Description Topics The topics published by Routing Service to describe a route or an auto route rti routing_service monitoring route_data and rti routing_service monitoring auto_route_data have a new boole
5. Connext Messaging See the Core Libraries and Utilities Release Notes and User s Manual for details There are new fields in the Samplelnfo and WriteParams structures related to the new Request Reply communication pattern Routing Service has been updated so it can propagate these new fields When lt publish_with_original_info gt is set to TRUE in a routing service route with Connext out put the Connext output will publish samples with a related_sample_identity equal to that of the received Samplelnfo What s New in 5 0 0 4 4 4 5 4 6 4 7 4 8 Note There is currently a scalability limitation Repliers that communicate directly with multi ple Requesters can efficiently minimize network traffic by sending a reply only to the one Requester that requested it However when they communicate through a routing service route Routing Service receives all the replies even for Requesters that are not on the other side of the route Remote Administration of Routing Service by Applications using a Requester RTI Connext 5 0 0 includes a new API that supports a Request Reply communication pattern only available in Connext Messaging see the Core Libraries and Utilities Release Notes and User s Manual for details Connext Requesters and Repliers can communicate through Routing Service The remote administration server in Routing Service has been updated to act as a Replier The pre existing administration topics in Routing Service
6. I is available in C and Java Compatibility 3 2 Compatibility Connext Compatibility RTI Routing Service is built on top of and intended for use with RTI Connext with the same version number With the built in Connext adapter Routing Service can be used to forward and transform data between Connext applications built with Connext as well as RTI Data Distribution Service 4 5 b el 44d 4 3e and 4 2e Note RTI Routing Service is not compatible with applications built with RTI Data Distribution Service 4 5e and earlier releases when communicating over shared memory For more informa tion please see the Transport Compatibility section in the RTI Core Libraries and Utilities Release Notes 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 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 Routing Service must be configured with the following proper ties set to 1 in order to be compatible with RTI Data Distribution Service 4 2e I 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 Routing Service must be configur
7. RTI Routing Service Release Notes Version 5 0 0 t 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 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 Contents Lis Supported Platforms ss eee re nt dE dns tira tentes tient ide 1 2 Supported Languages ss nn ne MR se sereine ete nie ent deh 1 Be Compan Dalit PES Re TT Ann e a mena range Pan de Pet de rares einen E S 2 3 1 Connext Compatibility esc ttes nn i a e e e RE ent R De E T 2 3 2 Command Line Options Compatibility ss 2 3 3 XML Compatibility issis ia ia aa oae Air ni a a e E itech dress dates 3 3 4 Jransfomat
8. 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 Routing Service User s Man ual Available Documentation Routing Service documentation includes L Release Notes RTI Routing Service_ReleaseNotes pdf Describes system require ments and compatibility as well as any version specific changes and known issues L Getting Started Guide RTI_Routing_Service_GettingStarted pdf Highlights the bene fits of Routing Service It provides installation and startup instructions and walks you through several examples so you can quickly see the benefits of using Routing Service L Users Manual RTI Routing Service_UsersManual pdf Describes how to configure Routing Service and use it remotely Custom Supported Platform Routing Service is also supported on the platforms listed in Table 8 1 these are target platforms for which RTI offers custom support If you are interested in these platforms please contact your local RTI representative or email sales rti com Custom Supported Platform Table 8 1 Custom Supported Platforms Operating System CPU Compiler RTI Architecture Abbreviation Mistral Linux Kernel 2 6 32 ARMv7 Sourcery G Lite 2009q3 67 gcc 4 4 1 armv7leLinux2 6gcc4 4 1
9. an field paused This field indicates if a route or auto route has been paused with the remote command pause Monitoring Topic Now Publishes System Level CPU and Memory Information In addition to publishing its own process CPU and memory usage Routing Service now also publishes the CPU and memory usage for the host on which it is running This information is in the rti routing_service monitoring routing_service_status_set topic Support for Extensible Types Routing Service includes partial support for the Extensible and Dynamic Topic Types for DDS specification from the Object Management Group OMG See Section 2 7 in the Routing Service User s Manual for details What s Fixed in 5 0 0 4 9 5 1 5 2 5 3 5 4 5 5 Propagation of Service Version as a DomainParticipant Property In this release the Routing 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 What s Fixed in 5 0 0 Configuration XML Schema Incorrectly Required Content Filter Parameters There was an error in the XSD file used in XML editors for syntax validation Because of this error when using an XML editor you were required to have at least one child lt parameter gt when specifying a lt content_filter gt
10. ble Command after Unloading a Configuration Resulted in Crash Routing Service could have crashed after a disable remote command if an XML configuration was not loaded at that moment e g after sending the unload command or after a parsing fail ure when issuing the load command This problem has been resolved Now the disable com mand will be safely ignored if there is no current configuration loaded RTI Issue ID ROUTING 127 Known Issues 6 2 6 3 Known Issues Limitations in Adapter API In the Adapter API Connection get_attributes and update operations are currently not sup ported 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 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 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
11. ceTransformation_ TransformFcn In the new API the transform function accept multiple samples In addition the output samples transformFnc must be created by the Member in Plugin struct f g f transformation instead of being transformation_transform passed in by Routing Service Function declaration RTI_RoutingServiceTransformation_ This function is used to return the none ReturnLoanFcn loan on the samples returned by Member in Plugin structure the transform function transformation_return_loan What s New in 5 0 0 New Remote Command to Get Current Configuration There is a new remote command get lt target_routing_service gt which retrieves the currently configuration and provides it in string format Support for 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 Ability to Propagate Related Sample Identity for Applications Using New Request Reply Communication Pattern RTI Connext 5 0 0 includes a new API that supports a Request Reply communication pattern Only available in
12. ed with the following proper ties 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 Routing Service version can be used simultaneously with applications built using compati ble versions of Connext and RTI Data Distribution Service see Connext Compatibility Section 3 1 unless special configuration is required as described above Command Line Options Compatibility Starting with 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 pre vious Routing Service versions the srvName parameter was not required However in this ver sion the equivalent parameter cfgName is required Also starting with Routing Service 1 1 0 the allowed values for the verbosity command 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 Routing Service Getting Started Guide 1 See lt Connext installation directory gt ndds lt version gt doc pdf RTI_CoreLibrariesAndUtilities_ReleaseNotes pdf Compatibility 3 3 XML Compatibility I Starting with Routing Service 1 1 0 the attribute
13. innes sine initie tirent 8 6 2 Sequences of Transformations in a Route are Not Supported cccccccssccesescenetesesesneneneseeees 8 6 3 Assignment Data Transformation only Supports Assignment of Primitive Fields Not Partof Atrays of SQquenices vss en nn nn n e ia ne tan ni ee ne dre 8 Available Documentatii musyssoisn ene re ner nt tintin iris 8 8 Custom Supported Platfofm nn en em en ner ERAS 8 ili Release Notes 1 Supported Platforms RTI Routing Service is supported on these platforms Table 1 0 Supported Platforms Platform Operating System Architecture INTEGRITY INTEGRITY 10 pentiumInty10 0 0 0 pcx86 i86Linux2 6gcc4 1 2 CentOS 5 4 5 5 2 6 kernel X6ALinux2 6gcc4 1 2 i86Linux2 6gcc4 1 1 Red Hat Enterprise Linux 5 0 x64Linux2 6gcc4 1 1 i86Linux2 6gcc4 1 2 Linux Red Hat Enterprise Linux 5 1 5 2 5 4 5 5 X6ALinux2 6gcc4 1 2 Red Hat Ent se Li 60 64 i86Linux2 6gcc4 4 5 n i H ue x64Linux2 6gcc4 4 5 i86Linux2 6gcc4 4 3 Ubuntu Server 10 04 2 6 kernel X6ALinux2 6gcc4 4 3 Solaris Solaris 2 10 i865012 10gcc3 4 4 i86Win32VS2005 Windows 7 Windows Server 2008 R2 aie Windows Windows 2003 Wind Vista x64Win64VS2005 dE oe x6AWin64VS2008 ORNE ee x64Win64VS2010 1 Does not include TCP IPv4 transport plugin implemented as a static library 2 Supported Languages LJ The transformation plugin API is only available in C _J The adapter plugin AP
14. ion ALES SR Re aes tas heen nn becca A Re HE ALES goat et 4 A What s Newin oO 02525 SRE nt A nt a nent Menara Rues 5 4 1 New Remote Command to Get Current Configuration 5 4 2 Support for Environment Variables in XML Configuration Files ccccccsescceteseeseeteteens 5 4 3 Ability to Propagate Related Sample Identity for Applications Using New Request Reply Communication Pattern sus 5 4 4 Remote Administration of Routing Service by Applications using a Requester 6 4 5 Integrated Support for Distributed Logger ss 6 4 6 New paused Field for Route Description Topics ss 6 4 7 Monitoring Topic Now Publishes System Level CPU and Memory Information 6 4 8 Support for Extensible Types stesso n ini PaE A TE aei eE 6 4 9 Propagation of Service Version as a DomainParticipant Property 7 5 Whats Fixed if5 00 insensible a a apa aE E daduasoatona s 7 5 1 Configuration XML Schema Incorrectly Required Content Filter Parameters ss15 1 7 5 2 Compiler Errors for Java Applications using Remote Administration Topics 0006 7 5 3 Save Command did not Save Configurations in RTI_ROUTING_SERVICE xml 7 5 4 Monitoring Failed in Routing Service if lt memory_management gt Tag Used cee 7 5 5 Using disable Command after Unloading a Configuration Resulted in Crash 7 2 KNOW ISSUES ER Re anne AT NE E rentre names der E EE entiers een 8 6 1 Limitations in Adapter APT u
15. ssignment transformation distributed with Routing Ser vice is now done with properties For example Before 2 0 0 lt 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 Compatibility 3 4 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 Transformation API The transformation API of Routing Service 2 0 1 and higher is not compatible with the API of pre vious releases 2 0 0 and lower The new API follows the same model as the adapter API which introduced the concept of a Plu gin 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 lt transformation_library name MyTransfLib gt lt transformation_plugin name MyTransfPlugin gt lt dll gt mytransformation lt d11

RTI Routing Service

Contents

Download Pdf Manuals

Related Search

Related Contents