LiveView New and Noteworthy Archive

In previous releases, LiveView servers were restricted to running one LiveView instance of the same project at a time. This was largely because the server metadata was silently stored in a local H2 database that was not shared between two instances of the same project.

Starting with release 10.3.0, multiple LiveView server instances of the same project can now be configured and run in a cluster. This is possible because Live Datamart now supports two new metadata storage methods: in a JDBC database, or in the shared transactional memory of the nodes hosting the servers.

This feature includes:

This release adds Single Sign-on support for LiveView clients connecting to LiveView servers through the following authentication realms:

The LiveView Query language was enhanced to support SQL-standard HAVING clauses. See LiveQL Reference for more information.

All LiveView System tables now support projections with simple expressions, including aliases.

A new sample demonstrates LiveView's high availability table group feature, which allows multiple LiveView instances to be in a high availability setup and allow recovery from failed servers or servers that were administratively taken down. See the sample's readme as well as Multiple Remote Data Layer Back Ends for more information about high availability table group configuration.

Java and .NET LiveView client APIs can now optionally identify when a set of continuous aggregate result set calculations are maximally consistent. Improved consistency is done by introducing two new client callbacks that indicate first when a result set is consistent and is not going to change, and second when the result set is no longer consistent and is going to change again. This feature helps improve consistency both with a single query, and also between multiple queries to the same table.

The feature is enabled when an optional client capability is set in the client connection configuration. Clients that do not set this option do not see a change in behavior; setting this option enables support for all aggregate queries on that connection to have the new callbacks.

This release adds the LiveView Alert Configuring Output Adapter that allows you to list, create, modify and remove alerts from LiveView servers. See LiveView Alert Configuring Output Adapter for more information. The LiveView Adapters sample was updated to include an example of this new adapter.

If Live Datamart is configured with authentication enabled, the user name associated with an alert is now forced to be the authenticated principal name from the session. If authentication is not enabled, the user name associated with the alert remains whatever the client sets in the user name of the AlertRule before sending it to the server.

The REST API for Live Datamart adds alert calls, as well as table permission checking for user interfaces. See LiveView Server REST API for more information.

The list of tested and supported LiveView samples that are available in StreamBase 10 Maven format now includes:

While these samples are not fully ready for Release 10.x, they are a starting point and are included for that reason.

You can now add system properties into your alerts via the liveview.alert.sysprop.whitelist, such as the LiveView server version. For white list details, see Using LiveView Alerts: Field Name System Properties.

This release includes a new Live Datamart server capability to support GUIDs in alert rules. GUIDs replaced long IDs for alert rules, to support optional JDBC and transactional memory data stores, (both data store types require GUIDs in lieu of long IDs; H2 supports both). For backward compatibility, 10.3.0 Live Datamart servers continue to support pre-10.3.0 clients and 10.3.0 Live Datamart clients continue to support pre-10.3.0 servers, with respect to alert rule IDs.

Alert GUIDs are now displayed in the LVAlerts and LVAlertRulesStatus system tables. See LiveView System Tables for examples.

The Live Datamart JDBC table provider would previously open one JDBC connection per table it discovered in the configured database. This was changed so that if the shareConnection option in a com.tibco.ep.streambase.configuration.jdbcdatasource file is true for a JDBC datasource, only one connection is opened for all tables the provider discovers and all queries go over this one long-lived connection. If shareConnection is not set, there are no long-lived JDBC connections and a new JDBC connection is opened and then closed for each new query made.

In the Java LiveView client's LiveViewConnection API, the following deprecated methods were removed. TIBCO now recommends using the LiveView client's Alert Manager API:

In the .NET LiveView client API, the following methods are now deprecated:

The above APIs are replaced by the following variants, which use a GUID instead of a long as an ID:

In the Java LiveView client's Alert Manager API, the following methods are now deprecated:

The above APIs are replaced by the following variants, which use a GUID instead of a long as an ID:

The following items were deprecated in Live Datamart 2.1 and are now removed from the LiveViewConnection API in 10.3.0:

Methods in TableAdminManager now replace the deprecated ones listed above.

The LiveView .NET API, which was previously available in Live Datamart 2.x but not Live Datamart 10.x, is now reinstated and fully supported on Windows platforms. See LiveView .NET Client API Location for more information regarding the API.

The version of LiveView Web Developer Edition included with Live Datamart was updated to release 1.3.2.

Two fields were added to the aggregation option to configure the Data Table lvconf file type:

See LVconf Type: Data Table for an explanation of field usage.

Live Datamart 10.2 supports the launching of more than one LiveView fragment in Studio, as reported for EventFlow fragments. The Studio features that support multiple launches are described on this page.

This release adds a REST API for Live Datamart in addition to the existing Java, JavaScript, and .NET Client APIs. See LiveView Server REST API for more information.

LiveQL statements to query Live Datamart servers can now use GROUP-BY modifiers that use a StreamBase expression, instead of just grouping by column names. See LiveQL Syntax Reference for more information. To support the enhancement, the QueryModel interface was changed. getOrderBy and getDirection are replaced with getOrderDefinition(). A new method, getQueryLanguage was also added.

When using the LVConf Editor, you must use the Source tab to manually add a GROUP BY modifier that uses an expression. When you return to a forms-based view, an error message displays that you can ignore. The Editor is expected to be updated in a future release.

This release adds a Python sample, which demonstrates the LiveView REST API using simple Python scripts.

See Migration and Compatibility, below.

When converting LiveView 2.x projects to 10.2.0, any sub-folder element in a 2.x lvconf file is now safely ignored and removed.

The security configuration HOCON type was significantly updated, with changes to better support LiveView and TIBCO LiveView™ Web security. As a result, you must update any LiveView 10.1.x projects configured for authentication to the new configuration format. See the Configuration Guide page for security, as well as:

The LiveView Authentication and LiveView Web samples were updated to use the new security configuration and can serve as references. See README files for those samples.

Live Datamart now includes TIBCO LiveView™ Web Standard Edition, which is licensed for limited use as described in License Considerations.

To configure LiveView Web 1.2.1 to work with Live Datamart 10.1.0, please consult the LiveView Web documentation.

Live Datamart now supports configuring Author-Time high-availability tables that are backed by multiple Live Datamart instances and that automatically reissue queries from fallen servers. This is configured by adding multiple remote URIs to the existing remote table feature. See Multiple Remote Data Layer Back Ends for more information.

With the re-introduction of Live Datamart into StreamBase 10.1.0, the following LiveView samples are now available in StreamBase 10 Maven format, and are known to work:

The following LiveView samples are also provided, but have not been fully tested:

The LVSessionQueries table has a new column named RemoteServer. This column provides table-specific information to help identify which remote server is running the query. This column is null for local LiveView tables.

The LiveView Publisher interface has changed. Publishers must now implement an output stream called PublisherStateOut that reports on publisher status during recovery.

Live Datamart now supports pivot queries to create pivot tables. See Pivot Queries to learn more. To illustrate this feature, the Hello LiveView sample was updated to include a Pivot Queries perspective, from which you can run pivot queries on the ItemSales table.

When authentication is enabled, Live Datamart now implements tighter control over listing tables. Therefore, you must provide list privileges to the table you are going to publish to. For more information about Live Datamart privileges, see Runtime Security Configuration.

The JDBC Table lvconf type is deprecated and was removed from the LiveView Configuration File Editor. Instead, use the External Server Connection lvconf file type and select JDBC from the drop-down list.

Compared to StreamBase 7, the XML structure in StreamBase 10.1.0 for the Application and Publisher lvconf types was changed as follows:

In addition, the legacy static aggregation implementation, which was deprecated as of Live Datamart 2.0, is now removed.

As announced in the Live Datamart 2.1.2 New and Noteworthy, the JQuery version of Atmosphere (jquery.atmosphere.js) was deprecated in favor of the pure JavaScript version, atmosphere.js. As of Live Datamart 10.1.0, the JQuery plugin is now removed.

In addition, the Atmosphere JavaScript library was upgraded on the client side to match the LiveView Server side, which is version 2.4.3.