StreamBase 10.6.0 Release Notes

Starting with release 10.6.0, TIBCO Streaming 10.6 runs only with and requires an installation of Oracle JDK 11.0.7 or a later JDK 11 version.

On all supported operating systems, the TIBCO Streaming installation kit provides the runtime components of Oracle JDK version 11.0.7 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 Configuratons page.

The StreamBase Runtime has had long-standing support for its own node-based discovery service that uses communication over UDP ports as its hallmark.

To better integrate TIBCO Streaming applications in Cloud environments, where UDP broadcasts and firewall management is restricted, release 10.6.0 introduces support for industry-standard Kubernetes as an alternative discovery service and Docker container deployment manager. This release also adds support for Helm as a package manager for Kubernetes configurations.

This release of Studio builds on its Maven-based automation for generating Studio projects that are ready to build and load into a Docker environment. The File>New>StreamBase Project wizard now has check boxes that extend its Docker support with two new options:

Select the Kubernetes check box to have Kubernetes support files generated into the project folder for the new project. Select the Helm check box to generate the additional Helm support files.

You can run and test your Docker containers with Kubernetes management on your development workstation by installing Docker Desktop for Mac or Windows. Docker Desktop is required for Studio's Docker integration; install the latest version available. See the Docker section of the StreamBase Administration Guide for instructions on building a containerized StreamBase Application in StreamBase Studio.

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

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

StreamBase Studio silently updates the workspace format of older projects. Once imported and updated to 10.6 format, do not reopen a 10.6 project with an earlier release of Studio.

TIBCO Streaming 10.6.0 introduces support for Microsoft Visual Studio 2019, which TIBCO recommends for building C++ or .NET clients for Windows.

Other Visual Studio support changes are described in Deprecated and Removed Features below.

Release 10.6.0 includes a standalone installation of Maven 3.6.3 for customer command-line use as described in the Maven entry of the Supported Configurations page.

StreamBase now supports CentOS 8 as a staging and deployment server platform.

As part of 10.6.0's adoption of Eclipse 4.15, Studio now supports Eclipse Dark themes. To configure a Dark theme, see Changing Studio's Appearance. All Studio perspectives, views, and editors are affected by the theme change, with the exception of the Palette view.

Studio now includes a LiveView perspective that opens automatically when you run a LiveView fragment in Studio. The perspective has many features of the TIBCO LiveView Desktop™ utility, but now integrated with Studio. This provides developers with an automatic and convenient way to view the tables of one or more running LiveView fragments, and to perform queries against them.

The Palette view now includes a search field in its title bar where you can narrow the display in the view by specifying a few letters of the name of an operator, stream, or data construct of interest. This works best when you pin open all three drawers of the view, to see the effects of the search in all drawers at once.

The Apache Kafka option for Studio's LiveView Connectivity Wizard now supports creating Kafka projects with basic and advanced authentication options. Click the Generate Security Settings link at the bottom of the Advanced Options grid to open the following dialog. You can select Basic-only by clearing the Use SSL Encryption check box, or select the combination of Authentication and Encryption settings appropriate for your Kafka cluster.

The TIBCO Cloud Messaging option for Studio's LiveView Connectivity Wizard was enhanced with UI support for constructing a text matcher string in the Content Matcher field. The dialog now has an Assist Me link next to the Content Matcher field. When selected, a dialog appears showing messages seen on the TCM channel, as well as a chooser for selecting fields of interest.

In previous releases without the assisting dialog, you had to type a raw content matcher string into the Content Matcher text field, such as {"topic":"sales","department":"widgets"}.

You can specify a prerequisite for a HOCON configuration file in a Run Configuration dialog for EventFlow or LiveView fragments. This feature lets you specify one configuration file (say, B) as a prerequisite for another, A. In this case, when Studio runs the fragment, it loads B before A, independent of other load order considerations. See Configuration Settings for more information.

For every rule that you define, Studio loads the prerequisite HOCON file before the file of interest. The ordering of the remaining HOCON files remains as described in HOCON Configuration Load Order. If you define an illogical set of rules, then all rules are ignored.

Docker containers can now include the Cluster Monitor application. See this page for configuration details.

StreamBase Studio now includes a Markdown viewer much like the one on GitHub, which provides an HTML-like view of Markdown format files in general, including those pulled into Studio as part of the community samples and online versions of supported samples.

The viewer supports Markdown format cross-reference links to tags in the same document, but links to a separate document opens it in text editor view.

When typechecking EventFlow modules, Studio now looks for container-scoped variable definitions in EventFlowDeployment and/or ParameterSettingsGroup configuration files.

Tooltips in the Run and Debug Configuration dialogs were updated to provide more comprehensive messages for port selections.

The REST API introduced in 10.5.0 now includes engine metrics. Enhancements include:

Security for web services was enhanced to support:

A new root object com.tibco.ep.dtm.configuration.security.PrivilegeSettingsGroup allows a security role to include any number of named privilege settings. Privilege settings can include other settings, allowing greater flexibility and reuse.

The pageSize property for Client Listener configuration increased to a maximum of 16384 bytes.

The local authentication realm now includes the following properties:

See Number of Login Attempts for a discussion of using this feature in a non-default Local Authentication Realm.

Release 10.6.0 includes the following enhancements to the Artifact Distribution Service:

The Artifact Distribution Service (ADS) was updated so that the name of the artifact service record no longer exceeds the maximum service name length of 255 characters.

ADS now updates the Last Model Request Time property in the node service record to signal to the (separately installed) Artifact Management Server (AMS) that artifacts are required. Further, the artifact service record was deprecated as the means to signal AMS, but, ADS still publishes the artifact service record for compatibility with previous AMS versions.

ADS configuration now fails activation if another active ADS configuration on the node defines the same artifact but with different data. Previously, the configuration activation succeeded and an INFO message was raised at fragment start time. At fragment startup, it is still possible to get the artifact already loaded with different data error if a different node in the cluster has defined the artifact with different data. In this case a WARN message is raised.

ADS now logs a message if fragment startup fails because required at startup artifacts were not received within the artifact-wait timeout period and the Artifact Management Server did not contact the node to get the list of artifacts that the fragment requested. This message is in addition to the existing message that specifies that the fragment failed because artifacts were not received (which can apply to several use-cases).

The TIBCO Streaming EP Command Reference now provides a detailed page for every epadmin target, with each of that target's commands explained, along with its command parameters.

The epadmin display web type=webservice command now includes the --detailed parameter to display additional web service information such as any failed requests, to identify possible denial-of-service attacks on endpoints.

The epadmin command target, metric, which was introduced in 10.5.0 for future use, can now be used to display metrics such as CPU utilization for nodes running EventFlow and LiveView applications. Note also that the target name changed in 10.6.0 from metrics to metric.

The start engine command no longer waits for the engine to be fully started before returning. Also, the stop engine command now does not return until the engine has stopped.

The epadmin display authentication and update authentication commands were added to retrieve and update the local authentication realms for a running node, respectively.

The epadmin create snapshot command now creates the snapshot archive on the local file system. By default, the snapshot archive is placed in the current working directory of the epadmin command, or you can specify an alternate location with the destination parameter, using an absolute path or one relative to the current directory.

In previous releases, the command created the snapshot archive in a directory named snapshots/nodename, parallel to the node directory, and you could use the destination parameter to specify a directory relative to that location.

This release includes the TIBCO StreamBase® Short Message Peer-to-Peer Protocol (SMPP) Adapter. The adapter enables sending and receiving of short text messages (SMS) over the Internet. See the sample page to learn how to demonstrate the adapter's features.

This release includes a trio of adapters to support connectivity to and from the Slack Technologies messaging platform:

See the sample page to learn how to demonstrate the adapter's features.

The TIBCO StreamBase® Adapter for ETP allows StreamBase to interact with data from an ETP (Energistics Transfer Protocol) v1.1 server. The adapters in this set include:

See the sample page to learn how to demonstrate the adapter's features.

The new TIBCO StreamBase® HTTP Client adapter performs HTTP requests and emits the contents via a Data output port. This adapter replaces the Web Reader Input adapter, which is now deprecated.

The Diameter adapters include the following enhancements:

The TIBCO StreamBase Rendezvous output adapter can now convert underscore (_) numeric field names to pure numeric field names in TIBCO Rendezvous and back again on the subscribe side.

The TIBCO StreamBase Rendezvous input and output adapters now unsubscribe and disconnect from the Rendezvous message bus when they suspend, and reconnect when they resume. Current subscriptions are saved for when resume is called. More specifically, both adapters now support multiple options to connect at startup, auto-reconnect, reconnect wait, and also a control port to connect and disconnect manually.

Previously when suspended, the input adapter:

A new option was added for OSIsoft PI adapters built on the PI SDK to specify the authentication type to perform — currently either Windows Authentication or PI Authentication.

Release 10.6.0 now supports Solace JMS's SOL_CLIENT_ACKNOWLEDGE as a value to the JMS/EMS operators' acknowledge-mode configuration setting.

The operators also now accept an integer value for this setting. For example, SOL_CLIENT_ACKNOWLEDGE is defined as 4 in the Solace JMS API; you can now use either the constant name or its integer value interchangeably.

The StreamBase Runtime audit process now rejects a configuration activation/replacement if an engine affinity configuration does not have explicit or implicit affinity with at least one engine.

As a configuration copy-and-paste convenience, the default node deploy configuration for the supplied Cluster Monitor application is now shipped (next to the Cluster Monitor application zip file) in distrib/tibco/sb/applications/cluster-monitor-node.conf. The file was also renamed from node.conf to cluster-monitor-node.conf.

In previous releases, four Guides that help you understand and configure the StreamBase Runtime were only available offsite in an older format. Starting with release 10.6.0, these four Guides are now integrated into the TIBCO Streaming documentation:

In addition to the four Guides described above, an all new TIBCO Streaming EP Command Reference was carved out of an appendix in the former Runtime Administration Guide, then significantly enhanced and extended to become a top-level book of its own.

The Default Security Configuration and Trusted Hosts pages were extended and clarified. The Local Authentication Realm page was clarified throughout with a new Account Lock Features section added.

Instructions for installing and using an alternate TERR installation were re-tested and re-wrtitten.

The Concepts Guide has a new page, Finding the adminport for a Node.

The Using Docker section of the StreamBase Administration Guide was modernized, corrected, and extended to include this release's Kubernetes support.