3. Upgrading from 7.3.1 to 7.7.0

See Important: How to Use this Guide, if you haven’t already.

The following sections describe how to upgrade from Connext 7.3.1 to Connext 7.7.0.

• 3.1. General Compatibility 7.7.0
  • 3.1.1. Wire Compatibility
    • 3.1.1.1. RTPS Versions
    • 3.1.1.2. Best-effort DataReader from before 6.1.0 cannot receive MultiChannel RTPS fragmented data from synchronous DataWriter in 7.7.0
    • 3.1.1.3. DataReader in 7.7.0 may not interoperate with DataWriter in previous release when using XCDR and mutable unions
    • 3.1.1.4. Configure compatibility with Java keyhash calculation in previous releases
    • 3.1.1.5. RTPS Header Extension timestamp clock has changed
    • 3.1.1.6. Wire interoperability issue related to new discovery protocol APIs for RPC and Request-Reply
  • 3.1.2. Type System Compatibility
    • 3.1.2.1. Assignability of 8-bit types
    • 3.1.2.2. Incompatibility between Python API and other APIs when using int8 type
    • 3.1.2.3. Union discriminator initialization change
    • 3.1.2.4. Recursive Type Support
    • 3.1.2.5. TypeObject v1 no longer propagated by default
    • 3.1.2.6. Multiple Calls to Builtin Listeners
    • 3.1.2.7. Requirement for request_types_filter
  • 3.1.3. Transport Compatibility
    • 3.1.3.1. Real-Time WAN Transport updated message_size_max value may cause messages to be dropped from previous versions
• 3.2. Product-Specific Compatibility 7.7.0
  • 3.2.1. RTI Connext Core Libraries
    • 3.2.1.1. API Compatibility
    • 3.2.1.2. Configuration Changes
    • 3.2.1.3. Logging Changes
    • 3.2.1.4. Utilities Changes
    • 3.2.1.5. Library Size
    • 3.2.1.6. Memory Consumption
  • 3.2.2. RTI Code Generator
    • 3.2.2.1. Changed default mapping for Modern C++ to “IDL4 to C++”
  • 3.2.3. RTI Security Plugins
    • 3.2.3.1. Wire Compatibility
    • 3.2.3.2. Changes to Building an Application
    • 3.2.3.3. Configuration Changes
    • 3.2.3.4. Key Revision Changes
    • 3.2.3.5. API Changes
    • 3.2.3.6. Logging Changes
    • 3.2.3.7. Deprecation and Removal Changes
    • 3.2.3.8. SDK Changes
  • 3.2.4. RTI Infrastructure Services
    • 3.2.4.1. RTI Persistence Service
    • 3.2.4.2. Routing Service
    • 3.2.4.3. Web Integration Service
  • 3.2.5. RTI Connext Observability Framework
    • 3.2.5.1. Monitoring Library 2.0 incompatible with earlier Collector Service versions
    • 3.2.5.2. Changes to domain ID and domain tag for observability traffic
    • 3.2.5.3. Monitoring Library 2.0 security now enforced when using RTI Security plugins
    • 3.2.5.4. Setting monitoring.telemetry_data.metrics in a derived profile or using an XML snippet now behaves differently
    • 3.2.5.5. Default metrics reduction in Monitoring Library 2.0
    • 3.2.5.6. Disallow unrealistic values of polling_period
    • 3.2.5.7. Monitoring Library 2.0 may require increasing participant_property_string_max_length with LM bundles