2. Upgrading from 7.6.0 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.6.0 to Connext 7.7.0.

• 2.1. General Compatibility 760 to 7.7.0
  • 2.1.1. Wire Compatibility
    • 2.1.1.1. RTPS Header Extension timestamp clock has changed
  • 2.1.2. Type System Compatibility
    • 2.1.2.1. Assignability of 8-bit Types
    • 2.1.2.2. Recursive Type Support
    • 2.1.2.3. TypeObject v1 no longer propagated by default
    • 2.1.2.4. Multiple Calls to Builtin Listeners
    • 2.1.2.5. Requirement for request_types_filter
• 2.2. Product-Specific Compatibility 760 to 7.7.0
  • 2.2.1. RTI Connext Core Libraries
    • 2.2.1.1. Configuration Changes
    • 2.2.1.2. Utilities Changes
  • 2.2.2. RTI Security Plugins
    • 2.2.2.1. Wire Compatibility
    • 2.2.2.2. Changes to Building an Application
    • 2.2.2.3. Changes to Supported Cryptographic Algorithms
    • 2.2.2.4. Configuration Changes
    • 2.2.2.5. Logging Changes
    • 2.2.2.6. Security Plugins SDK
  • 2.2.3. RTI Infrastructure Services
    • 2.2.3.1. Routing Service
    • 2.2.3.2. Web Integration Service
  • 2.2.4. RTI TLS Support
    • 2.2.4.1. OpenSSL 3 upgrade
  • 2.2.5. RTI Connext Observability Framework
    • 2.2.5.1. Monitoring Library 2.0 incompatible with earlier Collector Service versions
    • 2.2.5.2. Remote Debugging incompatible between 7.6.0 and 7.7.0
    • 2.2.5.3. Changes to domain ID and domain tag for observability traffic
    • 2.2.5.4. Monitoring Library 2.0 security now enforced when using RTI Security plugins
    • 2.2.5.5. Setting monitoring.telemetry_data.metrics in a derived profile or using an XML snippet now behaves differently
    • 2.2.5.6. Default metrics reduction in Monitoring Library 2.0
    • 2.2.5.7. Disallow unrealistic values of polling_period
    • 2.2.5.8. Monitoring Library 2.0 may require increasing participant_property_string_max_length with LM bundles