8. Release Notes

8.1. Supported Platforms

RTI Web Integration Service is supported on the platforms in Table 8.1.

Table 8.1 Supported Platforms
Platform Operating System
Linux® (Intel® CPU) All Linux platforms on x86/x64 CPUs in the RTI Connext DDS Core Libraries Release Notes for the same version number, except SUSE® Linux Enterprise Server 11 and Wind River® Linux 7 systems.
Linux (Arm® CPU) Ubuntu® 16.04 LTS on Arm v8 (64-bit) CPU
macOS® All macOS platforms in the RTI Connext DDS Core Libraries Release Notes with the same version number.
Windows® All Windows platforms in the RTI Connext DDS Core Libraries Release Notes for the same version number.

Web Integration Service is also supported on the platforms in Table 8.2; 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.

Table 8.2 Custom Supported Platforms
Operating System CPU Compiler RTI Architecture Abbreviation
RedHawk™ Linux 6.5 PPC x86 gcc 4.9.2 i86RedHawk6.5gcc4.9.2
RedHawk Linux 6.5 PPC x64 gcc 4.9.2 x64RedHawk6.5gcc4.9.2

8.2. Compatibility

For backward compatibility information between Web Integration Service 6.0.1 and previous releases, please see the Migration Guide on the RTI Community portal.

8.3. What’s New in 6.0.1

8.3.1. New platforms

Web Integration Service now includes support for these platforms:

  • macOS 10.14 (x64)
  • Red Hat® Enterprise Linux 8 (x64)
  • Windows 10 (x86, x64) with Visual Studio® 2019
  • Windows Server 2016 (x86, x64) with Visual Studio 2019

For more information on these platforms, see the RTI Connext DDS Core Libraries Platform Notes for this release.

8.3.2. Removed platforms

These platforms are no longer supported:

  • macOS 10.11
  • Windows 7
  • Windows Server 2008 R2

8.3.3. Added Support for Max Objects Per Thread Configuration

The SystemResourceLimitsQosPolicy of the DomainParticipantFactoryQos provides users with a mechanism to configure the maximum number of objects that can be stored per thread for a DDSDomainParticipantFactory. However, due to a limitation of the Connext DDS core libraries, SystemResourceLimitsQosPolicy may not be modified via XML. To overcome this limitation, Web Integration Service has introduced a new command-line argument called -maxObjectsPerThread that enables you to configure the number of objects per thread at startup time.

8.4. Previous Releases

8.4.1. What’s New in 6.0.0 New Platforms

This release adds support for:
  • SUSE Linux Enterprise Server 12 on x64 (x64Linux2.6gcc4.3.4)
  • Ubuntu 16.04 LTS on ARM v8 (armv8Linux4.4gcc5.4.0)
  • Ubuntu 18.04 LTS on x64 (x64Linux4gcc7.3.0) Ability to Enable Topics

Like any other Entity, a DDS Topic can be created in enabled or disabled mode. This version of Web Integration Service introduces an option to enable Topics that were created in disabled mode. This option was already available for other DDS entities (i.e., DomainParticipants, Publishers, Subscribers, DataWriters, and DataReaders). For more information on this new functionality, please see the API Reference section of this document. Upgraded to CivetWeb v1.11

Web Integration Service has upgraded the version of its embedded web server, CivetWeb, to v1.11. For more information on CivetWeb, please see its Release Notes on GitHub.

8.4.2. What’s Fixed in 6.0.0 Attempt to create invalid application not reported as error

Web Integration Service failed to return an error upon the creation of invalid applications that tried to register previously undefined types. This problem has been resolved.

[RTI Issue ID WEBINT-129]

8.5. Known Issues

8.5.1. Configurations and their applications cannot use same name

Due to current limitations in Connext DDS’s XML Parser, the name of the Web Integration Service configuration tag and the name of the applications within that configuration cannot be the same. For example:

<web_integration_service name="ShapesDemo">
    <application name="ShapesDemo"/>

To workaround this limitation, use different names for the service configuration tag and the applications within. For example:

<web_integration_service name="ShapesDemo">
    <application name="ShapesDemoApplication"/>

[RTI Issue ID CORE-3542]