.. include:: ../../../router.1.0/srcDoc/vars.rst .. _section-Product-Routing: RTI Routing Service ******************* The following issues affect backward compatibility in |RS|. Application Binary Interface ============================ Service Library --------------- The |RS| Library does not provide ABI compatibility. Applications and libraries that linked against previous versions of this library are not guaranteed to work in |version|. Applications and libraries that linked against this library will need to be recompiled. See :numref:`section-Product-ABI`. Infrastructure Library ---------------------- The |RS| Infrastructure Library does not provide ABI compatibility. Applications and libraries (usually Adapters and Transformation plug-ins) that linked against previous versions of this library are not guaranteed to work in |version|. Applications and libraries that linked against this library will need to be recompiled. See :numref:`section-Product-ABI`. APIs ==== Adapter API ----------- The |RS| Adapter C API has changed, and existing implementations are required to be recompiled. These changes are minimal and should not affect the API interface. Therefore, existing Adapter implementation code should recompile with no additional changes. Service API ----------- The |RS| Service C API has changed, and existing applications that use this API are required to be recompiled. These changes are minimal and should not affect the API interface. Therefore, existing applications and libraries using the Service API should recompile with no additional changes. Configuration ============= .. _section-Product-Routing_XSD: XSD compatibility ----------------- The |RS| XSD definition no longer allows the use of tags ````, ````, ````, and ```` that could appear within ````. Instead, these tags should be replaced with the ``` and ```` tags, which now receive a name. For example the following legacy XML is no longer valid: .. code-block:: xml ... ... Instead, the equivalent and compatible XML code is shown as follows: .. code-block:: xml ... ... The command-line version of |RS| incorporates an option to convert legacy XML configuration files to their equivalent compliant version. Look for the option ``-convertLegacyXml`` in the command-line help. For example, the following command will convert an existing legacy file with name ``routerLegacy.xml`` and generate a new file with the name ``routerConverted.xml`` in the same directory: .. code-block:: bash [NDDSHOME]/bin/rtiroutingservice \ -cfgFile routerLegacy.xml -convertLegacyXml routerConverted.xml XML Validation -------------- |RS| incorporates builtin XSD validation of XML configuration files. |RS| will fail to load non-compliant XML configuration files. You will need to update your XML configuration files (see :numref:`section-Product-Routing_XSD`) to be compliant with the new definitions. .. note:: As a temporary workaround, you can disable XSD validation by using the option ``-ignoreXsdValidation`` in the command-line version of |RS| or by setting ``enforce_xsd_validation`` to false in the library version of |RS|. This workaround is not recommended and should be used only for testing purposes during the migration process. Administration and Monitoring ============================= New models ---------- The |RS| remote administration and monitoring interfaces (including DDS topics and command-syntax) have been redesigned. They are no longer compatible with the interfaces from previous releases. Any applications that used the legacy interfaces to administer or monitor |RS| will no longer communicate and will need to be updated to use the new interfaces. See :link_connext_router_admin_usersman:`Remote Administration in the Routing Service User's Manual <>`. See :link_connext_router_mon_usersman:`Monitoring in the Routing Service User's Manual <>`. .. note:: *RTI Administration Console* has been updated to use the new administration and monitoring interfaces, so it will use the new DDS model and commands to communicate with |RS|. .. _section-Product-Routing_ignore: "Ignore" warnings ----------------- If WARNINGs are enabled, you may receive the following warning in |RS| saying that you are ignoring a participant even though you are not ignoring it: .. code-block:: bash DISCParticipantDiscoveryPlugin_assertRemoteParticipant:remote entity ignored by user: 0X1017E82,0XD1817B1C,0X80642BE7,0X1C1 This warning is reported when the administration/monitoring participant uses the same domain ID as one of the |RS| participants. In this case, the administration/monitoring participant will not communicate with the |RS| participant. This warning is intended (new) behavior in 6.0.0. You may see this warning if you are migrating to 6.0.0 using the same domain ID configuration as in 5.3.1. If you change the domain ID of the administration/monitoring participant, the warning will not occur and the participant will not be ignored. QoS === |RS| has not made any changes to the entities' QoS with regards to previous versions. See :numref:`section-General-Qos` for QoS changes in the Core Libraries that may affect |RS|. Performance =========== For very small data sizes (between 1-64 bytes), |RS| throughput is ~10% worse and latency is ~3% higher. Library Size ============ A comparison of |RS| libraries sizes for the architecture ``x64Linux3gcc4.8.2`` is shown in :numref:`TableRouterLibrarySize`. .. list-table:: Library Size Comparison for x64Linux3gcc4.8.2 in MBs :name: TableRouterLibrarySize :widths: 70 10 10 10 :header-rows: 1 :class: longtable * - - 5.3.1 - 6.0.0 - Change (%) * - ritroutingsevice.so - 3.9 - 6.35 - +38.58 * - rtiroutingservicez.a - 6.15 - 9.77 - +37.05 * - rtirsinfrastructure.so - 0.023 - 0.028 - +17.8 * - rtirsinfrastructurez.a - 0.025 - 0.028 - +10.7 Documentation ============= The |RS| *Release Notes*, *Getting Started Guide*, and *User's Manual* have been consolidated into a single document, which is available in HTML and PDF formats. You can find them in your |CONNEXT| installation in the following locations: - HTML main page: ``[NDDSHOME]/doc/manuals/routing_service/index.html`` - PDF: ``[NDDSHOME]/doc/manuals/routing_service/RTI_RoutingService_UsersManual.pdf``