Streaming 11.1.2 Release Notes

Customers must activate this release as part of an installation or upgrade. The release will not function unless it is activated with a license.

Generate a license to activate this product within the TIBCO Software Download site at http://www.tibco.com/downloads. Only customers with an active entitlement to this release can generate a license.

To activate this product by the recommended method of In-product Activation (local activation), refer to the documentation at Activation in Spotfire Streaming and https://docs.tibco.com/products/tibco-activation-service.

The Spotfire Streaming installation kit provides a copy of Eclipse Adoptium JDK 17.0.13 in a subdirectory of the Streaming installation directory, to run Streaming program fragments and applications from within StreamBase Studio and other Streaming development tools. Streaming detects and prefers a system-installed JDK, and uses this bundled JDK as a fallback. See further details about the JDK requirements of this release in the JDK entry of the Supported Configurations page.

Spotfire Streaming 11.1.2 includes a standalone installation of Maven 3.9.9 for customer command-line use as described in the Maven entry of the Supported Configurations page.

A new parameter javahome is added to the epadmin install systemservice command, specifying the location of the JRE or JDK to be used by the node.

Snapshot file created using epadmin create snapshot command is now written in the node install directory. Previously, it was written into the Operating System's working directory.

In version 10.3, a new build path entry called StreamBase Fragment Project Dependencies was added to the Project Explorer view. This entry contained all of the current project's dependencies to other fragment projects. It is no longer needed since the fragment dependencies are shown in the existing Maven Dependencies container.

The fragment dependencies container will no longer appear in the Project Explorer view, and it will appear empty if viewed from the Java Build Path preference page. In a future release, the entry for this container in the project's .classpath file will be removed.

In the Kubernetes and local environment, the root URL of the dtm server now always redirects to /admin-ui. Previously, it was redirected to /help-ui(swagger-ui) in the local environment.

Support added for pausing asynchronous replication when the replication queue for a remote node hits a configurable request depth. The queue depth is configured using the maximumReplicationQueueDepth property and is disabled by default. For more information, see ApplicationDefinition Properties.

The epadmin partition target commands define partition, disable partition, enable partition, migrate partition, and update partition are removed in this release. These commands were not exposed or documented.

Support for Windows 10 is deprecated and will be removed in a future release.

To upgrade to this version, clusters must be completely stopped and restarted. The node-to-node protocol changed in this release in a non-backward compatible fashion.

The Distributed Transactional Memory API changed between versions 10.x and 11.x, preventing an 11.x node from starting if there is an existing live 10.6 node already in the cluster. Instead, ensure that 10.x and 11.x nodes are in different clusters at all times.