StreamBase 10.4.0 Release Notes

TIBCO Streaming is the full set of streaming technologies, and includes TIBCO StreamBase®, TIBCO LiveView™, and the TIBCO StreamBase Studio™ development environment. See What is TIBCO Streaming for a complete list of included technologies.

TIBCO Spotfire Data Streams is a subset of the TIBCO® Streaming package, configured as an add-on for TIBCO Spotfire® users, and licensed for the sole purpose of serving live data to TIBCO Spotfire. See What is TIBCO Spotfire Data Streams for the contents of this package.

StreamBase Studio now provides a new right-click menu option for a selected application or fragment project, StreamBase>Manage Project Dependencies. Invoke this option:

This option presents an information dialog, and then it:

See Add a Dependency for instructions on the application project case.

You can now stop, remove, and forcefully remove multiple running nodes using the context menu by Ctrl+clicking nodes in the Clusters view.

A new StreamBase Expression Language Function was added, getResourceAbsolutePath(). This function returns the absolute file system path for a specified resource in a Studio project's src/main/resources folder.

By default, attempting to override the transaction isolation of a parent module in a child module generates a typecheck warning, because transaction isolation cannot be overridden by child modules. This warning can now be optionally disabled, as described on the Typechecking preferences page.

The StreamBase Application Archive Wizard was enhanced and now provides the options to:

If Studio fails to connect to a fragment during a launch because the fragment has authentication requirements, a new error dialog notifies you that Studio does not currently support such attachments.

A (commented out) example of how to load a configuration file is now included in generated unit test cases.

This release includes the following adapter suite:

See the Protobuf page for adapter details and the sample page for the adapter sample.

The TIBCO StreamBase® Web Input Response Adapter allows a StreamBase application to respond to a REST call that was handled by a linked Web Input Adapter.

Three new WITSML operators were added that allow for generic operations on any parent-child object structure such as logs, log rigs, rig wells, well, and so on. See The WITSML operator documentation for details regarding the new WITSML read, write, and delete operators.

In addition, the WITSML operator suite now includes an option to specify which WITSML version is used when performing operations against the server.

The eFTL Input Subscribe and Output Publish adapters now include new properties, including a Unique Id property that appends a unique ID to a client ID. See the links above for additional property details.

The MQTT adapters now include two new options to control MQTT connections: maxInFlight and automaticReconnect. For details, see:

The TIBCO StreamBase® Database Change Data Capture Input adapter now includes options to disable the startup of the SQL Server agent, as well as to disable the adapter on a table, at startup, if not already enabled.

The TIBCO StreamBase® Operator For H2O Model Evaluator was enhanced to include:

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

Starting with TIBCO Streaming release 10.4.0, StreamBase Studio detects and prefers a system-installed Oracle JDK 8 over its own bundled JDK. Using a system-installed JDK allows you to take advantage of cryptography features of the JDK that TIBCO is not licensed to include with TIBCO Data Streams, and allows you to manage your JDK installation independent of StreamBase. See Installing a JDK for details on this new feature.

StreamBase Studio, StreamBase Manager, and LiveView Desktop are now based on Eclipse 4.9 (2018-09). This version includes changes to the Eclipse workspace format.

StreamBase Studio silently updates the workspace format. However, TIBCO strongly recommends importing your projects from previous releases into a new, unused Studio 10.4 workspace rather than trying to reuse a previous release's workspace.

LiveView Desktop users may be prompted to upgrade their workspaces.

See the Eclipse documentation for additional details on Eclipse 4.9 capabilities.

The Maven version bundled with StreamBase is now 3.5.4.

The RPM installer for the streambase-server-*.rpm now includes the RPM Requires clause that works on all supported Linux operating systems. Also, if you unpack the RPMs and use the client and server RPMs independently with yum install, the required dependencies are installed.

In StreamBase Studio, the Jetty web server version was upgraded to 9.3.25. The upgrade applies to, for example, the TIBCO StreamBase® Web Server Request adapter and the TIBCO StreamBase® Web Server Response adapter, as well as for developing your own applications that require Jetty.

A new epadmin command target, dynvar, was added to set and get dynamic variables. See epadmin-dynvar(1).

A suspend command was added to the engine administration target to support stopping an engine in a suspended state for debugging. See this page for an overview of the engine lifecycle.

A reset authentication command was added to restore the initial authentication characteristics of a node.

The epadmin generate and list commands were added to generate and list HOCON configuration files, respectively. See this page for details.

The epadmin operator target now has the following new commands to support operator properties:

epadmin get operator [--engine=string] [--path=string] [--property=string]
epadmin set operator --property=string --value=string [--engine=string] [--path=string]
epadmin display operator [--engine=string] [--path=string] [--property=string] 

The epadmin display container command now includes a --detailed option. When set to true, the command output includes container content details.

The epadmin display user command now includes the following additional fields in its output. This information comes from the authentication realm with which the specified user is associated:

See this page for more information regarding security management.

The epadmin display cluster command now displays addresses of all distribution instances on the node.

The display stream command adds the --detailed option to display additional input and output stream information. Also, the command's --schema option is now deprecated.

For the epadmin display adapter command, the output has a new field named Adapter, which contains the full output name of the adapter.

A new option was added to support starting playback on a specific container:

[--path=string] container name to target the command. If unset, defaults to the default container. Default: none

The export artifact command now requires a file parameter, which specifies a client-side file for the exported data. The file is overwritten if it already exists.

The epadmin operator target now comes with four new state management commands:

This release adds administration target support for creating client-side output files via these commands:

Multiple independent TrustedHosts configuration files are now supported within a node's security configuration (with one active at a time still enforced).

TrustedHosts configuration files configuration files now support IPv6 CIDR block notation.

If a StreamBase client connection does not specify the username, a default username is obtained by calling System.getProperty("user.name"). This is used as a convenience, albeit a potentially unsafe one. For default security information, see this page.

The API was updated for service discovery and publishing. This API is used to support service discovery in existing Java APIs and also to allow applications to publish their own service records.

New API methods were added to the StreamBase API to support quorum notification and partition notification:

The Artifact Distribution Service (ADS) now includes the following enhancements:

The streambase.codegen.broken-method-names system property, used for refactoring all or individually generated methods, now supports simple (as well as fully qualified) method names. See this page for use-cases and details.

An engine.shutdownTimerSeconds parameter was added, which you can apply to StreamBase, LiveView, and Java engines.

A default availability zone default-cluster-wide-availability-zone and an associated default data distribution policy default-dynamic-data-distribution-policy were added to expedite fragment launches by saving configuration time. These are selected by default in:

See this page for the default availability zone and data distribution policy settings.

The File>New>StreamBase Project wizard is more streamlined, with fewer decisions to make when creating a Docker image to contain your StreamBase or LiveView application. When creating a project for a StreamBase Application, a single check box now selects the option to create your application as a Docker image. See Creating and Running Docker Images for newly written instructions for this procedure.

As of release 10.4.0, when starting your Studio-generated Docker container with the docker run command, you must now explicitly specify a node name for the StreamBase Runtime node in your container, by using the -e NODENAME=node.cluster or --env NODENAME=node.cluster options. The following shows a complete command:

docker run -d --name firstapp -e NODENAME=A.cluster -p 2000:2000 sample/docker_1st

See Creating and Running Docker Images for updated Docker image creation instructions.

In previous releases, the StreamBase Studio Configuration Directory was named with a three-position version number, such as 10.2.0. This meant that every maintenance release, such as 10.2.1, got a separate configuration directory. For customers who added Eclipse plug-ins to Studio, this convention required them to reinstall those plug-ins with each maintenance release.

Starting with release 10.4.0, the configuration directory is named with a two-position version number such as 10.4. This means that all maintenance releases for each major.minor release can share the same Studio configuration settings, including Eclipse plug-ins added to Studio.

This change does not refer to the Studio workspace directory, whose default location naming syntax has not changed. TIBCO does still recommend using a new, empty workspace for each major.minor release, and importing your projects from the previous release to the new workspace.

Generation of LiveView projects using the Maven archetype now, by default, now includes the LiveView Web WAR file as a dependency. You can disable this by setting the archetype property lvweb to false.

The Node is not running message that is returned when a node is started, but no target engines are available was improved to distinguish between the node that has not been started, compared to when there are no running engines.

Logging Now Supports Transaction ID as a Pattern Element in Logs. The keyword %transaction in a Logback configuration file places the current transaction ID, if any, into the log record for the current event. If no transaction is active, none is inserted; if there is an active transaction, but the identifier cannot be determined, unavailable is inserted. See StreamBase Logback Extensions for further information.

Additionally, when the default duplicate suppression filter is in place, the suppressed-message log event uses the same category and level as that of the suppressed messages. See Default Logging for default logging information.

Also note that duplicate message filtering is always in place. If you specify a filter, the filter is used. Otherwise the default is used.

Legacy log level integer settings used in StreamBase releases before 10.2.0 were removed in the Advanced tab of the EventFlow Fragment launch configuration.

Docker container logging is now supported.

Round-robin data mappers specified in StreamBase Runtime Application configuration files now support dynamic data distribution policies, in addition to static ones.

The HOCON Configuration File Editor now includes the option to search by HOCON property name to assist in locating the configuration file type to use.

The TIBCO StreamBase® Web Input adapter's ResponseId field is renamed to SB_ResponseId. For more about the property, see Web Input Adapter.

Additionally, the adapter now handles HTTP metadata such as headers and cookies.

This release removes the forcelocal option from the load configuration command. Providing a configuration file to the configuration target is always local to where the administration client is running, which may or may not be the same as the node.

Also removed from the command is the debug option. Use normal logging support to enable debug tracing in HOCON.