Streaming 11.0.0 Release Notes

TIBCO® Streaming and TIBCO® Data Streams now install in default locations that include their product codes, str and sfire-sfds respectively. For this product, the default install locations are /opt/tibco/sfire-sfds/11.1 on Linux and C:\tibco\sfire-sfds\11.1 on Windows.

The tar.gz files from the unpack action of the archive-bin installers for these products and the StreamBase High Performance Fix Pack are now rooted at the product install root with no fixed prefix, so any destination you choose no longer must contain str/10.x.

Windows Server 2019 is now a supported operating system for development and deployment.

AlmaLinux is now a supported operating system for deployment, and is the recommended migration path for applications deployed on CentOS Linux 8.

On all supported operating systems, the TIBCO Data Streams installation kit provides the runtime components of Oracle JDK version 11.0.14 in a subdirectory of the StreamBase installation directory, for private use to run StreamBase program fragments and applications from within StreamBase Studio. As before, StreamBase detects and prefers a system-installed JDK, and uses the bundled JDK as a fallback. See further details about the JDK requirements of this release in the JDK entry of the Supported Configurations page.

StreamBase Studio and StreamBase Manager are now based on Eclipse 4.21.

As with every major release, TIBCO strongly recommends using File>Import to import your projects from previous releases into a new, unused Studio 11.0 workspace. Be sure to use the Copy projects into workspace option.

Once imported and updated to 11.0 format, do not reopen a 11.0 project with an earlier release of Studio.

A quick fix has been added to the HOCON editor to insert a default value for missing substitution variables in order to remove validation errors. For details refer to Default Substitution Variable Value Example section of the HOCON Substitution Variables page.

Eclipse Docker Tooling 5.4 version has been bundled with the StreamBase 11.0 version. This allows management of Docker images and Containers from within Studio. For more details on this open source software refer to Linux Tools Project/Docker Tooling/User Guide.

Logback 1.2.8 and higher is now a supported logging framework.

Cluster-wide alerting is now more robust in ensuring alerts are not missed when an alert master fails. See the Cluster-wide Alert Configuration page for more information.

Postgres 12.2 is now supported for LiveView Metadata server to store its metadata. For supported version details, refer to Supported Configurations.

The LiveView adapters now have two new features available. The first feature supports 'Runtime URLs', meaning you can set the LiveView URL any time during the life of the server. You can also change the LiveView URL to connect to at any time.

The second feature provides the option to use a 'compressed' LiveView connection. This can be very helpful for connections transferring large amounts of data and which have limited or metered bandwidth.

The LiveView client has been modernized with auto completion and command history.

The LiveView Python client lets you query, publish, and monitor data from a LiveView server with Python.

The LiveView now publishes 7 new metrics. All existing LiveView metrics are now deprecated.

PyDev is now a supported feature, which can help create python projects.

Data Science operators were accessible through Operators menu within the Insert tab. They can now be accessed using the palette drawer.

Starting with this release, macOS Studio ID has changed from studio.product to com.streambase.sb.studio.product and Manager Bundle ID has changed from manager.product to com.tibco.ep.sb as per Apple guidelines. Check all default installation directories.

Starting with this release, StreamBase Studio's Support wizard (in the Help menu) can now also capture and save a thread dump of the Studio JVM to assist in troubleshooting.

The Target Router Path field has been added to the Distributed Router Operator to specify the fully-qualified path of the Distributed Router to which tuples are routed. This field is optional. The default value is the path of the Distributed Router Operator.

The Decision Table operator field now allows you to enable Control and Status ports so that they can be incorporated into the EventFlow. The Enable Control Port and Enable Status Port properties can be used to specify if these ports should be enabled.

The Warm Start-Up feature allows engines running EventFlow fragments to be restarted without recompiling the fragment's EventFlow source code (e.g. sbapp files). Warm Start-Up is disabled by default and needs to be enabled in a StreamBase engine configuration by setting the "recompileBehavior" field to "REUSE" in the "streambase" section of the configuration.

This release comes with new parallel region queue config settings in Studio that can be defined per-operator. These settings can already be defined globally in the HOCON configuration but this new feature allows each operator to have its own settings.

Starting with release 11.0.0, TIBCO® Streaming Web Server supports HTTP/2 when SSL is configured.

A new StreamBase LDAP Auth Configuration Wizard is added in Studio, that assists users with LDAP configuration file generation. This wizard validates entered information with provided server and generates the config file based on this information. You can access this wizard by selecting File>New>Other...>StreamBase LDAP Auth Configuration or right-click on a project and selecting New>Other...>StreamBase LDAP Auth Configuration.

Starting from this release, the shared memory usage by a node for non-user data has been significantly reduced. Startup shared memory usage, in a 512 megabyte node, has dropped from 184 megabytes (36%) to 44 megabytes (8%).

Starting from this release, remote administration is supported from any client OS (Windows, Linux, Mac) to any server OS.

Starting with release 11.0.0, ep-maven-plugin will now consider eventflow sources from src/test/eventflows. These will be built and be available for local maven module testing. They will not get shipped in the eventflow fragment archive.

Starting with release 11.0.0, code refactoring is always enabled to avoid exceeding Java limits for generated module code.

Starting with release 11.0.0, an MQTT LV recovery sample is added. The recovery sample demonstrates elastic scaling with peer-based recovery for message buses that don't provide storage message ids. Both 'perfect' and 'imperfect' recovery is discussed.

Starting with release 11.0.0, as part of this migration, consuming events in WPF events are now no longer automatically threaded and need to be done by users. The LiveView .NET adapter now packages the StreamBase lite DLL, compared to the previous full StreamBase DLL. LiveView works with both DLL versions.

The lite DLL has the following changes:

The TCDS provides LiveView server URLs. Follow the steps to get the TCDS stream connectivity URL:

Get the authentication token from here.

The AMS client adapter always forced the content field to have an encoding of ENCODING_ZIP_BASE64 when sent. Starting in 11.0, the content field will have a default encoding of NONE. If zip compression is desired, the encoding field should be set to ENCODING_ZIP_BASE64.

Starting with TIBCO Streaming 11.0.0, samples with HTML READMEs no longer include a plain text README. Studio will pick the appropriate format for any sample.

Starting with TIBCO Streaming 11.0.0, support for using the C++ client API from Microsoft Visual Studio 2012 has been removed. Programs that use the C++ client API in Windows should use Microsoft Visual Stuio 2019.

The eFTL LV recovery sample is updated to use the new eFTL 6.5.0 storage message id. This sample demonstrates elastic scaling based on peer-based recovery. The delayed recovery operator is now improved. The previous delayed recovery eFTL sample is removed. The new MQTT sample demonstrates delayed peer recovery for message buses that do not have message ids.

Stream SQL is deprecated and will be removed in a future release.

Support for CentOS Linux 7 and 8 is deprecated as of Streaming 11. Because Red Hat has declared that CentOS Linux has reached end of life, there will be no security updates. Container or machine builds that relied on CentOS package repositories, such as Docker or Ansible, will not work and must be migrated to other compatible Streaming-supported Linux distributions.

For Streaming, the options are Red Hat Enterprise Linux, Oracle Linux, and AlmaLinux. AlmaLinux is the recommended option for container builds like Docker; use the image name almalinux:8.

Support for Red Hat Enterprise Linux 7 and Oracle Linux 7 is deprecated and is expected to be removed in a future release.

Support for Windows releases before 2016 is deprecated. Among currently supported Windows releases, Windows 7, 8.1, and Windows Server 2012 are thus deprecated. In Windows 10, support for builds before 1607 is deprecated.

Use of these versions of Visual Studio for Streaming .NET client and operator development is deprecated and expected to be removed in a future release. Migration to Visual Studio 2019 is recommended.

JDBC support for Oracle 11g, Microsoft SQL Server 2008, and all versions of Vertica are removed in 11.0.0.

The deprecated legacy HA support is removed in 11.0.0. Operators using the leadership property now report a typecheck error. Upgrade the module to remove this property by making a simple change in the module (e.g., operator name change) and save the module.

Loading EventFlow from the resources directory is deprecated and will be removed in a future release. Eventflow files should all be located into /src/main/eventflow or /src/test/eventflow. Use a qualified module name to reference the module in module references or extension points.

With this release, serialization of the com.streambase.sb.Tuple abstract class is deprecated.

Refactoring of codes is enabled by default. Users can not use system properties to force the failed codes to be refactored to work around the Java limits.

This release provides compatibility with application and fragment archives built with these versions: