StreamBase 10.4.1 Release Notes

This release adds the following two adapters, which when used together, allow a StreamBase application to monitor changes to an Oracle 12c and later database using Oracle LogMiner:

These adapters are illustrated in a sample.

The WITSML Log Data Converter operator now has an Output Type option to output data as a list of key-value pair tuples. This new option is designed to enable more generic data use.

The Web Server Request and Response adapters were updated to support SSL for both HTTPS and wss.

The TIBCO StreamBase® Read Adapter for WebSocket Client now includes an Advanced tab to support wss configuration.

The Python operators were enhanced as follows:

The number of log messages generated when the default availability zone is initialized are both significantly reduced and made clearer.

When a node stop is requested, but some of its configuration cannot be deactivated, the error message that appears now includes the path of the engine log relative to the node directory.

Three new clean-related arguments and the maven-home option were added to the epdev command for Maven artifact management and cleanup. See the epdev reference page or epdev --help for further information.

The Oracle JDK version bundled with StreamBase and Live Datamart is now JDK 1.8.0_u191.

The StreamBase Runtime now supports the Amazon Linux 2 operating system. For StreamBase support details, see this page.

Studio now supports macOS 10.14 Mojave as a development environment. However, Mojave's dark mode is not supported because of Eclipse compatibility issues. When first selecting the Open StreamBase Command Terminal Here feature in Studio, you are prompted for permission to control the terminal.

StreamBase Runtime deployments are now support Oracle VM VirtualBox 5.2 as a Docker environment.

When Studio opens a workspace, several system checks occur that previously could briefly show a blank EventFlow Editor canvas, depending on how many projects are being checked. Studio now displays a message at the top-left of the canvas that reads Verifying project dependencies. Clicking the message brings up the progress view to show details about the ongoing operation.

Studio now checks the version information for Java fragment projects, to make sure it matches the currently installed version of StreamBase. An Eclipse Quick Fix is offered to bring the versions up to date when necessary. (This check was formerly performed only for EventFlow and LiveView fragment projects.)

The epadmin add container command was integrated with ADS so that the container's operators now receive artifact notifications when the container is added via epadmin.

Prior to this release, a default availability zone was not created until a fragment was launched. Now, the availability zone is created when the node starts; a fragment launch is not required. This behavior change is expected to improve stop and restart performance on slower machines.

Studio no longer automatically widens the Manual Input view to accommodate the longest text in the Fragment drop-down list. Prior to 10.4.1, the Manual Input view in the SB Test/Debug perspective could become too wide if its Fragment drop-down list contained long text, which could possibly push nearby buttons out of sight to the right or down.

Hover over the drop-down list to display all the text in a tooltip.

For convenience, in the Clusters view, the Confirm Node Stop Dialog now includes a Do Not Show This Again check box.

By design, the Kafka Consumer adapter does not output the fully qualified adapter name with each tuple. Now, the Kafka Consumer Commit adapter can optionally take in that fully qualified name to link back to the Kafka Consumer adapter to perform the commit.

Previously, the XML parser could not handle dates such as 2018-12-09T07:59:27.3057523Z because it used the SimpleDateFormat from Java. The WITSML Input adapters as well as the XML2Tuple operator now use a revised date format.

For example, this change replaces a string format such as 2018-12-09T07:59:27.3057523Z with one that looks like 2018-12-09T07:59:27.305+0000 before a parse is attempted.

The TIBCO StreamBase® Cluster Publisher and Subscriber Adapter suite is now deprecated and is expected to be removed in a future release.

The TIBCO StreamBase® SBD-to-SBD Input (Downstream) Adapter and the TIBCO StreamBase® SBD-to-SBD Output (Upstream) Adapter were previously announced as deprecated. As of this release, these adapters are removed from deprecation.

User Streams, Site Streams, and Direct Message endpoints are deprecated and longer available from Twitter. As a result, when trying to use those deprecated functions in the Twitter input or output adapters, the respective Status port now generates information regarding the deprecated API. For adapter configuration, see Twitter Input Adapter and Twitter Output Adapter.

StreamBase Studio from release 10.4.1 will open your 10.4.0 workspace without requiring any conversion or upgrade. Thus, there should never be a need to return to using Studio from release 10.4.0 after installing 10.4.1.

This is not an issue on Windows, where maintenance releases replace the base major.minor release. That is, you cannot have StreamBase 10.4.0 and 10.4.1 on the same Windows machine using standard installation procedures. On macOS, however, multiple StreamBase maintenance releases can easily coexist. Therefore, it is important on the Mac to not open Studio 10.4.0 once you have installed and used 10.4.1. And never open both Studio 10.4.0 and Studio 10.4.1 at the same time.

The reason is the shared configuration directory. Starting with release 10.4.0, StreamBase Studio maintenance releases use the same configuration directory as the primary release. That is, releases 10.4.1, 10.4.2, and so on, all use the same Studio configuration directory as the one initially configured for 10.4.0. This feature allows Eclipse plug-ins that you added to Studio in the base release to still be present when you install and use a maintenance release.

The configuration directory is not the Studio workspace, but is a separate storage location for Studio metadata. See Default Installation Directories .