Live Datamart New and Noteworthy Archive

Services-only servers deployed from 1.6.5 and earlier, or from 2.0.0 through 2.0.4 installations cannot interact with LiveView 2.1.x full servers. However, services-only servers from a 1.6.6 or later installation, or a 2.0.5 or later installation, can interact with a 2.1.x full server.

When StreamBase Studio 7.4.4 or later is used with a new workspace, LiveView project folders, including LiveView sample project folders, now show the lv-systemdata folder by default. This folder contains a database file that contains data automatically loaded into LiveView Server at each launch, including information such as LiveView Server alert rules and LiveView Desktop workspaces. The folder is now visible by default so that customers with version control integrated into Studio can check in this folder as part of each LiveView project folder check-in.

You can disable the visibility of this folder for all projects in the workspace by invoking the system menu in the Package Explorer view (the down-pointing triangle icon), and selecting Filters. In the resulting dialog, select the check box for TIBCO LiveView Server System Database Folder.

Table Actions you can configure in LiveView Desktop include an Open URL in Browser action. In previous releases, when this action was configured, and LiveView Desktop was stopped and restarted, the last seen URL was not refreshed. Starting with this release, such URLs are remembered between LiveView Desktop sessions and automatically re-opened. However, be aware that the underlying data on the referenced URL may have changed, which may have invalidated a parameterized URL. On Desktop restart, make sure any reopened URLs are still valid for your use case.

LiveView Desktop charting was upgraded to use the DataWatch (formerly Panopticon) library version 12.4.3.

This release includes new OS X installation instructions for the base StreamBase kit and its Live Datamart add-on package, and for LiveView Desktop, including special instructions to work around an issue when installing on OS X 10.10 Yosemite.

This release includes a behavior change made to avoid an error message that could be seen when LiveView was compiling an application: compilation error in <field-rules>: the field "current" is not available from any stream. As of release 1.6.3, table column variables with no explicitly specified namespace are considered to be prefixed with input.

In previous releases, the lvconf configuration file could specify either a primary key or the generation of custom IDs. This restriction was lifted such that both features can now be used in the same lvconf specification.

This release includes support for a new mixed mode method of generating the unique row IDs used internally by LiveView Server. Mixed mode ID generation is an advanced feature that combines aspects of the previously available ID generation methods. Contact TIBCO LiveView Support for details on using this feature.

LiveView Desktop charting was upgraded to use the DataWatch (formerly Panopticon) library version 12.4.2.

The lv-client command now accepts a -p option with which you can specify the TCP port on which the LiveView Data Mart server of interest is running on localhost.

This release adds support for adding CORS access control headers to the response messages sent by the LiveView web server. These access control headers allow the use of resources from another website, such as a third-party JavaScript library, to be securely used. This support takes the form of two Java system properties, one for requested files with the .json extension, and another for files with the .xml extension. Note that .json files served by LiveView might contain either JSON data or XML data; by contrast, .xml files contain only XML data. Set the system property appropriate for the extension of the file requested, not its contents. The two new system properties are:

You can specify either property with the -D option for the Java command that starts LiveView Server, or with the <sysproperty> element in your project's sbd.sbconf file. Both properties take a sequence of one or more CORS headers that LiveView is to prepend to all service calls that end with .json or .xml, respectively. Enter your arguments as a sequence of colon-delimited header-value pairs, where each pair is delimited by a comma. That is, enter header1 : value1 , header2 : value2, and so on. White space around the delimiters is optional, but can be clarifying.

The following example shows the use of this feature in a <sysproperty> element:

<sysproperty name="liveview.response.header.json"
   value="Access-Control-Allow-Origin: * , 
   Access-Control-Allow-Credentials: true" />

The LiveView sample provided as lv-sample-javascript now demonstrates an additional new feature in the dashboard display, a horizon chart powered by the Cubism.js library from Square, Inc.

LiveView 1.6.2 adds a web front end to the contrib-query-summary project that provides a visual representation of the query performance statistics gathered by that project. To see this feature, run that project as a StreamBase LiveView Project, then open a web browser on http://localhost:10080/jsapisample.

This release adds a set of predefined condition format strings for the Edit Conditional Formatting Rule dialog, described in the new LiveView Desktop Conditional Formatting page in the LiveView Desktop User's Guide.

When you specify formatting for numeric values, you can still directly enter a formatting string that follows the java.text.DecimalFormat standard. But starting with release 1.6.2, format string fields also serve as drop-down lists that offer a selection of predefined formats, such as ###,##0 and $###,##0. See the LiveView Desktop Conditional Formatting page for the complete list.

The list provides currency format strings for dollars, pounds, yen, as well as providing a placeholder symbol (¤) that is automatically replaced with the currency symbol for the current locale.

If you are formatting a timestamp field, the drop-down offers you a selection of format strings that use the syntax of the java.text.SimpleDateFormat standard, including HH:mm:ss.SSS and yy/dd/MM HH:mm:ss. Again, see the LiveView Desktop Conditional Formatting page for the complete list.

You can select any suggested format, then edit it to your needs in the format string field. Select the Edit Recommendations link in any drop-down list to open a dialog that lets you reorder the list to put your favorites at the top, or to add your own entries.

The same Edit Recommendations dialogs, and same drop-down list functionality, are shared by the LiveView Desktop Preferences dialog, when setting the default formatting strings for all numeric and timestamp types. Any format strings or reordering of the list persists and is visible both to conditional formatting dialogs and to the Preferences dialog. Your customized set of formatting strings is stored in the current Desktop workspace.

You can now configure LiveView Desktop to automatically reconnect to one or more failover servers in the event the primary LiveView Server becomes unavailable. The failover LiveView servers must be running a compatible LiveView release and have a substantially similar LiveView application, with the same tables, table names, and schemas.

Connecting to a failover server is not attempted unless your initial connection to your primary server succeeds. That is, you must be connected at least once to your primary server before the failover mechanism becomes available. The new Automatically Reconnecting to LiveView Server page in the LiveView Desktop User's Guide describes this new feature in detail.

Previous releases of LiveView Desktop allowed you to set both text color and background color for individual cells based on matches of a conditional formatting specification. This release adds the ability to set text and background colors for an entire row. The Edit Conditional Formatting Rule dialog now has an Apply to control with Cell and Row options. When you select Row, only the two color formatting options are available.

As before, to avoid formatting conflicts when two different format conditions apply to the same row or field, use the Up and Down buttons in the Edit Conditional Formatting Rule dialog to organize the rules. The following algorithm is used to determine which rules win if there is a conflict:

This rule scanning order allows you to add different color settings for a cell that matches a condition, and also for the row that contains that cell when matching the same condition. Set the row rule first, then the cell rule for the same condition. This is useful for tables with wide schemas, where a portion of the table is always offscreen in LiveView Desktop's grid view. In such cases, a color-change alert might be missed if a cell is colorized offscreen. When you color the entire row, perhaps with a background color, it serves as a reminder to scroll left or right to locate the cell or cells that caused that row to change.

The drop-down list of comparison options in the Edit Conditional Formatting Rule dialog now includes both is equal to or greater than and is equal to or less than.

LiveView Desktop now has a menu option, Window → Show Error Log View.

This release adds a new chart type to the Configure Charting View, a time series scatter plot where the size of the dots representing data points can themselves be sized based on values in another plot axis. For example, a stock symbol's price over time can be shown with each dot representing a stock symbol, and the size of the dot representing the volume of trades at each time point. This new feature is implemented as a new option in the Size/Height control group in the Configure Charting view, Timeseries Scatter Plot Dot-size Field. This new option is only active when the selected Visualization method is Timeseries Scatter Plot.

In previous LiveView Desktop releases, when you used New Send Tuple View to connect to a LiveView Server table configured with fields of type tuple that contained sub-fields, the resulting Send view showed only the top-level tuple field names, and none of their sub-fields. This required you to send a tuple to such fields using StreamBase tuple notation as used with the sbc command. Starting with LiveView 1.6.2, the Send Tuple view shows a flattened view of such a table's sub-fields.

Federated LiveView server instances can now pass through StreamBase Query Tables as their own. This means that any LiveView server instance (either full or services only) can be configured to exchange data and queries with a StreamBase Query Table in a running StreamBase application. See Using LiveView as a Front-End for more information.

The LiveView Configuration File wizard now has an option to import a named schema with the import-schema tag.

LiveView 1.6 adds additional useful configuration files to the lv-contrib directory. The directory previously contained the following:

The following was added in LiveView 1.6:

LiveView Desktop charting view now allows the stepped linegraph option.

The Advanced Alerting sample, lv-sample-alerting, now includes a configured Send Tuple alert action that can optionally forward alerts to TIBCO Enterprise Message Server™, Twitter, or TIBCO Rendezvous®. See the sample's README for full information.

The JavaScript API sample, lv-sample-javascript, now has an iPad browser UI in addition to the existing UI. See the sample's README for full information.

A LiveView server instance can now stand in front of multiple other LiveView instances, present their tables as its own and send and receive data from those tables.

LiveView server can stand in front of multiple back ends. In addition to the previously released JDBC capability, LiveView 1.6 can view spaces and metaspaces with TIBCO ActiveSpaces 2.1.2 HF 14.

See Using LiveView as a Front-End for important information on ActiveSpaces usage.

The following aggreation functions are now supported in LiveView dynamic (query-based) aggregation:

You can now reference any existing named schema to any lvconf file using the import-schema element.

LiveView can now be configured to verify the identity of clients (authentication) and ensure that authenticated clients have permission to access the requested LiveView resources (authorization).

LiveView data-table internal fields have changed. A table's source data-stream, DataOut, now contains a CQSDelete field for improved row delete capabilities.

StreamBase Studio allows you to choose which port the LiveView services layer listens on so that LiveView can be configured to listen to an SSL port.

Alerts now have a configurable option where after alert action execution, subsequent alert action executions are suppressed for a given period of time.

In previous releases, SNAPSHOT queries that reached a configured limit would terminate without an error. Now, when a SNAPSHOT query with a configured row limit reaches the limit, LiveView server will return a SNAPSHOT_OVER_LIMIT error.

In lvconf files, a new attribute of the root element for all table types, snapshot-concurrency, lets you set the number of tasks such as table scans that can run simultaneously for that table. You can also specify this setting in a Table Space type table, then specify that Table Space in a <table-space-ref> element in the lvconf for other tables in your project.

A new option in lvconf files, custom-id-generation, lets you create a custom value for a table field that is assigned to every row.

You can now start LiveView server in services-only mode. This option will not start the data layer and so will allow the server instance to start faster.

You can now create a table action that consists of executing one or more other table actions. See Execute Multiple Table Actions for more information.

In addition, you can now copy table actions into other table actions. The Table Action configuration dialog now offers a Copy From option that lets you select from all available configured actions.

In previous releases, the alert action for deleting table rows was disabled by default. The Delete Rows action is now enabled by default.

In earlier versions of LiveView the default row limit for queries was 10000. The default row limit for queries issued from LiveView Desktop is now 2000.

The names of chart types as displayed in the drop-down window for charting configuration are updated to be more descriptive. See LiveView Desktop Charting View for more information on LiveView charting options.

LiveView Desktop's grid view has three new options for pattern matching in conditional formatting:

You can now open a browser directly from LiveView Desktop's Window menu, in addition to the previously existing method to open a browser by configuring a table action.

When you execute an Open in Browser table action, if there is a saved view in the Workspace, the action will re-use the saved view.

The LiveView adapters have a new property, Log Level, that allows you to set the adapter's log level independently of LiveView server's log level.

The LiveView JavaScript sample has been reworked to be simpler and cleaner. It now shows how to display LiveView data onto HTML tables. In addition, it contains several visualizations from the D3 JavaScript library.

LiveView Data Mart 1.5.7 requires the 64-bit version of StreamBase 7.3.7 or higher.

New options for charting were added to LiveView Desktop. The Shapes option allows you to chart densities over a geospatial area. See LiveView Desktop Charting View for more information on charting.

The LiveView Publish adapter has a new option to attempt to connect to the configured server when a tuple is sent. Applications that use a LiveView Ready adapter or another indicator that the LiveView server is up but do not wish to wait for the specified Publish adapter reconnector thread to retry and complete connecting may use this option.

LiveView Desktop now allows users familiar with the Eclipse User Interface and Eclipse RCP development to build custom views by creating an Eclipse plug-in. A new product sample, LiveView Desktop Custom View sample, demonstrates a simple custom view.

The LiveView .NET Client API sample now has sample charts that demonstrate some of the available charting capabilities of the .NET Client API.

The use of DataWatch Desktop 12 (previously Panopticon 6) has changed in LiveView 1.5.5. Workbooks are now loaded and executed by using the settings for any StreamBase and StreamBase LiveView data tables and sources configured directly in the workbook. Workbooks now stream data from a running server to the workbook, rather than executing a full snapshot query periodically.

The LiveViewStatistics table has a new column, TotalTuplesPublished, that counts both inserts and updates sent to a table.

LiveView 1.5.5 requires StreamBase 7.3.7 or higher.

The format of LiveView restore files for persisted tables was changed in LiveView 1.5.5. Restore files created with previous releases of LiveView are not compatible with LiveView 1.5.5. If you have restore files from earlier versions of LiveView, you must delete these files before you upgrade.

You can now populate the fields of a lvconf file by copying fields directly from an EventFlow application element in StreamBase Studio using the StreamBase LiveView Table Configuration wizard. To use the wizard:

In previous releases, you used the console stop button to stop a running LiveView server. Starting with LiveView 1.5.4, you can use the LiveView server stop button in the top-level toolbar:

You can also access the new LiveView stop button these ways:

If you have more than one application running on the same machine, StreamBase Studio opens a dialog that lets you choose which process you want to stop.

LiveView 1.5.4 uses better placement of LiveView launch configurations. In previous releases, the configurations were stored as external tools and accessed from the Run → External Tools menu. They are now stored in native configurations and accessed from the Run → Run Configurations menu. This means that you can use the default launch configuration to start LiveView server.

Any launch configurations that you have created with earlier versions of LiveView are compatible with LiveView 1.5.4. You do not need to update old launch configurations.

The .NET API now includes support for queries that includes updates without an initial snapshot, named UPDATES_ONLY. The complete list of supported query types, as defined in the StreamBase.LiveView.API.QueryConfig.QueryTypes enumeration, are listed here:

You can now create alerts and configure alert actions from the StreamBase Command Prompt with the lv-client tool.

You can now populate the fields of a lvconf file by copying fields directly from a schema table in StreamBase Studio. If you copy the contents of a schema table and paste them into an existing lvconf file, StreamBase Studio will automatically format the clipboard contents if it detects schema fields.

In previous releases, LiveView Server required all LiveView data tables to reference a default table space. This is now optional; a LiveView data table that uses all system defaults does not need a configured table space. In addition, the lvconf files for tables no longer require a table space to be referenced in the attributes of the table's data-table tag.

In previous releases, if you used a custom lvconf file to override the default settings for a LiveView system table, LiveView Server would silently provide a default table space for the custom lvconf file. Since the default table space is no longer required, LiveView Server no longer provides a default table space. If you have configured custom lvconf files that have a table-space-ref attribute set and you do not add a default table space, remove the table-space-ref attribute that calls the default table space from the data-table tag.

The LiveView Publish Output adapter now has two new options:

LiveView Desktop charting was upgraded to use Panopticon 6.3.1.

In previous releases, the interface generator created all schemas necessary for configuring data-source, preprocessor, transform, and publisher applications. In LiveView 1.5.2, the interfaces generated from either the lv-server generate command or the File → New → EventFlow Application menu item contain an additional schema that contains the user-defined fields from the LiveView source table.

In previous releases, the EventFlow applications created with the EventFlow application wizard has access level set to private. In LiveView 1.5.2, the default access is public. This means that in a generated EventFlow application, the check box "Always expose Stream for Dequeue" on the General tab of the Properties view in Studio will be selected by default.

The performance of large row-delete operations against LiveView data tables is significantly improved.

The table action for Send Tuple now takes a fully qualified stream name as input for the send tuple target.

The LiveView Desktop preferences now have an option for null string formatting. The field Null string now appears in the StreamBase LiveView screen of the Preferences dialog.

The lv-client tool now has a -c option for emitting query results in CSV format.

LiveView 1.5 provides dynamic (query-based) aggregation. In dynamic aggregation, you can issue a query with an aggregate function against a configured LiveView data table. This allows you to aggregate data on the fly, rather than configure an aggregate table.

See Aggregation in LiveView for more information on LiveView aggregation queries and Aggregation Function Reference for more information on individual aggregate functions.

LiveView 1.5 lets you save and edit the perspectives for a given workspace. A LiveView perspective contains all the views (which can include table grids, charting, or query views) for a given workspace.

See LiveView Desktop Guide for more information on using perspectives in LiveView Desktop.

LiveView Desktop offers a new alert rule action, delete rows, that allows you to delete rows from a LiveView data table when alert conditions are met.

See Using LiveView Alerts for more information on configuring delete row alert actions.

The Tables View of LiveView Desktop now includes a Recent Queries node for every LiveView table. When you issue a query from LiveView Desktop, that query is immediately added to the Recent Queries node. If you close a query view without saving the query, you can reissue the query by selecting it from the Recent Queries node.

See Querying Your Data for more information on using the Recent Queries node.

LiveView Desktop now has additional query capabilities that let you refine results.

The connection protocol sb:// for connecting to the LiveView services layer was removed in LiveView 1.5.

Connections made by data publishers, that talk directly to the LiveView data layer, must continue to use the StreamBase client protocol sb://.

The LiveViewConnection API now provides a deleteRow method to remove rows from a table based on a supplied predicate.

When you start LiveView Desktop, you can download custom saved workspaces from a LiveView Server.

In LiveView 1.4, the default value for the query row limit is 10,000. In LiveView 1.3 and earlier, the default value was 30,000 and this limit was automatically invoked if you entered an ORDER BY clause without a LIMIT clause in a query. In LiveView 1.4, a query with an ORDER BY clause but no LIMIT clause will return an error.

The contextual menu for a table has additional options in the default menu. You can now designate a column as the default sort column and choose the sort to be ascending or descending when you open that table in a grid view.

LiveView Desktop's Edit Query dialog now presents any syntax or parse errors immediately, so you can correct the query easily.

LiveView Desktop now has a redesigned splash screen and program icon:

LiveView 1.4 features upgrades to the Panopticon libraries. Panopticon Workbooks versions 6.1 and earlier are fully supported by LiveView Desktop's Workbook Viewer view.

Panopticon workbooks may now be copied into the local workspace when the workbook view is configured. The copied workbook files can now be shipped through to the LiveView Server as part of a workspace upload with LiveView Workspace Manager. See LiveView Workspace Manager for more information on uploading workspaces.

LiveView Desktop's Workbook View now handles Panopticon Workbook URL Actions.

Formatting for double-precision numbers in LiveView Desktop's native charting view will now use the double formatting string as configured in the LiveView preference page. Workbook views are not affected by this change, and will still use the formatting configured by the underlying Panopticon workbook.

You can now easily duplicate a previously saved query. To create a duplicate of a saved query, right-click on the query name in the Tables pane and choose Duplicate.

Conditional formatting for numerical values now works with integers, in addition to floating-point numbers. Choose the Windows → Preferences → StreamBaseLiveView dialog to provide a formatting string for integers, doubles, and longs.

LiveView Desktop 1.4 has a new option that allows you to switch the server connection from LiveView Desktop. The File → Switch Server option will restart LiveView Desktop so that you can connect to a different LiveView Server instance.

In previous versions of LiveView Desktop, the Connect to LiveView dialog had an Automatically connect to this server on startup check box. The new Connect to LiveView dialog is designed to make it easier for you to choose multiple servers from which to download workspaces, so this option was removed.

You can now configure table actions to refer to fields that are in JSON payloads. For example, ${Payload.sku} will return the payload value of a table field called sku.

The Samples option in the charting aggregator option for Size/Height Configuration is now named Count.

The LiveView Web UI now offers a LiveView Monitor page that you can now use to view key LiveView system tables. In addition to Alert Rule management functionality, you can now use the Web UI to monitor LiveView Server activity. On a new landing page for the Web UI, tabs display live-updating view of server tables that track statistics about LiveView tables, active client sessions, and active queries.

When you install LiveView 1.4 on Windows, the StreamBase LiveView 1.4 Windows Start Menu item contains an entry for Getting Started with LiveView Server that opens the Getting Started documentation.

Before you upgrade LiveView, make sure that all LiveView Server instances on the machine you are upgrading are stopped. You must upgrade to StreamBase 7.3.4 or higher before installing LiveView 1.4.

LiveView Desktop and LiveView Server are not required to be the same version to work together. Although running an older client or server means that you might not have certain functionality, you can connect different versions of LiveView Desktop and LiveView Server.

The connection protocol sb:// for connecting to a LiveView services layer is no longer supported in LiveView 1.3. Although you can still use this protocol to connect to running LiveView services layer, you will not have access to many LiveView features. The supported protocol is lv://. For best results, always use the lv:// protocol for connections to LiveView services layer.

Connections made by data publishers, that talk directly to the LiveView data layer, must continue to use the StreamBase client protocol sb://.

The lvconf tag <alert-table> is deprecated. Update your configuration to use the <data-table> configuration with LiveView alerting functionality.

The setQuery method of the QueryConfig class no longer takes the String table argument. If you have saved code using this method and argument, update your code to use the setTable method instead.

The LiveView 1.3.6 release of LiveView Desktop provides support for Panopticon 6.1 Workbooks.

LiveView now supports FIX-style ID chaining based only on a client key. You can configure FIX-style ID chaining based only on a client key, as in this example:

<fixed-order-id-chaining>
   <server-key primary-field-ref="null"/>
   <client-key secondary-field-ref="OrigClOrdID" primary-field-ref="ClOrdID"/>
</fixed-order-id-chaining>

You can now create a Windows service for LiveView Server, set it to run automatically when Windows is booted, and have it remain running as a background process. See Running LiveView Server as a Windows Service or the lv-server reference page for information.

The JVM heap size for the lv-server process that launches LiveView Server is now capped at 2 GB.

You can now see the version number of the running LiveView Server to which a LiveView Desktop session is connected. If you hover over the Connected icon the in the lower-right corner of the LiveView Desktop, a pop-up widget will display information about the active LiveView Server connection.

You can now configure table-level rules that update content in LiveView tables. In previous releases, you had to configure rules for every individual field of a table that you wanted to update. The new <field-rules> tag allows you to configure insert, update, and delete rules to modify field content on the fly.

The sample project sample_lv-alerting-advanced demonstrates how to use table-level rules. See Using LiveView Alerts for how to load and run this sample.

In previous releases, if you created a project sub-folder for data sources, you had to manually add that folder to the resource search path for the project. In LiveView 1.3, project sub-folders that contain data sources, such as feed simulations, are automatically added to to path.

LiveView 1.3 supports installing LiveView in locations other than the default %STREAMBASE_HOME% location.

New fields AlertRule.Predicate and AlertRule.Delay are now available for use in configuring alert rules. See Using LiveView Alerts for how to use text substitution in alert configuration.

Enhancements to the sample project sample_lv-publisher make it easier to use this sample to create your own embedded publisher. In particular, you can now easily modify the sample to have it publish to additional tables. To migrate to the updated version of this sample, follow these steps:

See EventFlow Publish Applications for the full embedded publisher documentation.

The sample project sample_lv-alerting-advanced now contains a preprocessor that sets alerts based on the configured alert conditions and clears them when those conditions are not met.

See Using LiveView Alerts for how to load and run this sample.

You can now edit a query predicate on the fly while viewing query results. The Save button () on the top-left toolbar in query views now is enabled for unsaved, ad-hoc queries. It dims once the query has been saved; saved queries are always automatically saved as changes are made.

The Save button has a keyboard binding of CTRL+S on Windows and Cmd+S on Mac OS.

The F2 key is now a keyboard shortcut for the Edit Query menu item. It allows you to edit the predicate and restarts the query if necessary to reflect the changes.

The command-line client lv-client now has a --version option that returns the installed version of the LiveView Client library.

LiveView 1.3.0 Java clients, including the LiveView Desktop, could not issue queries to LiveView 1.1 and 1.2 servers. Starting with LiveView 1.3.1, Java clients can issue queries to LiveView 1.1 and 1.2 servers.

Release 1.3.0 adds Macintosh OS X 10.6 Snow Leopard, 10.7 Lion, and 10.8 Mountain Lion to the list of formally supported platforms.

StreamBase Studio is provided on OS X as a client application to allow users to develop, debug, and test StreamBase applications and client applications. StreamBase installations on OS X do include a local copy of StreamBase Server for running and testing your applications locally, on the same Macintosh computer as Studio. However, StreamBase Server is explicitly not supported for deployment on Apple Macintosh machines.

A new view can be opened from the top-level menu Window → New Send Tuple View. When configured, it opens a view that will create tuples from user input and send them to a StreamBase Server.

Charting view now has new options OHLC (Open, High, Low, Close) and Candlestick. These graphs require the table being queried to have four numeric fields: open, high, low, and close (case is ignored).

You can now execute table actions by keystroke. Click anywhere in the grid view of a table and press F3 to open a Run Action pop-up window that displays a numbered list actions. You can select actions by clicking on them or by typing the number of the action you want to execute. You can also open the Run Action pop-up window by right-clicking a table row and selecting Actions → Chooser from the drop-down menu.

You can now use the time ruler for interactive filtering on time-series charts. The time ruler allows you to dynamically adjust the time axis of your chart to zoom in or out of time intervals. To show a time ruler in charting view, click the Show Time Ruler button () in the top-right corner of the charting view.

Charting configuration now allows you to specify the order of breakdown fields. The ordering that you configure is preserved across view saves.

The LiveView Web UI has significant new capabilities for browsing, querying, and filtering alert information. See Using LiveView Alerts for full documentation.

Before you upgrade LiveView, make sure that all LiveView Server instances on the machine you are upgrading are stopped. If you are using StreamBase 7.2.x, you must upgrade to StreamBase 7.3.0 or higher before installing LiveView 1.3. See the StreamBase Installation Guide for how to install the correct version of StreamBase.

The connection protocol sb:// for connecting to a LiveView services layer is no longer supported in LiveView 1.3. Although you can still use this protocol to connect to running LiveView services layer, you will not have access to many LiveView features. The supported protocol is lv://. For best results, always use the lv:// protocol for connections to LiveView services layer.

Connections made by data publishers, that talk directly to the LiveView data layer, must continue to use the StreamBase client protocol sb://.

LiveView query language now allows the full features of StreamBase expression language. Update any code that uses the LiveView 1.2 or previous query language syntax.

The fixed-order-id-chaining tag has been changed. In previous releases, the fixed-order-id-chaining tag had to have exactly two key children, where the first key child had a primary-field-ref attribute only and the second had both a primary-field-ref and a secondary-field-ref. In LiveView 1.3, the child tags for fixed-order-id-chaining are as follows:

<fixed-order-id-chaining>
   <server-key primary-field-ref="FieldName"/>
   <client-key primary-field-ref="AnotherFieldName" secondary-field-ref="DifferentFieldName"/>
</fixed-order-id-chaining>

If you have legacy lvconf files that use fixed-order-id-chaining, you will need to update them to use the new syntax.

LiveView 1.2.2 includes a new table action that allows you to send a tuple to an existing public Input Stream in a StreamBase application. Note that a StreamBase application that is hosted by LiveView must have the Always expose Stream for Dequeue checkbox selected. You configure this table action from the Actions menu in LiveView Desktop.

You can now add short descriptions to saved queries. When you edit a previously saved query by right-clicking the query name in the Tables pane, you can add a description:

The description will also be visible when you hover over the query name in the Tables pane and as part of the query's header in grid or charting view:

You can now set axis limits as part of configuring a query charting view. In the Query Configure dialog, open the Axes Options menu. The default setting is Automatic, which means that axis limits will be configured by the data being charted. Select the Fixed option if you want to manually enter maximum and minimum limits on a chart's axes.

The LiveView charting query view now contains a new option for the LineGraph (timeseries) charts. When using LineGraph (timeseries), there is a new Advanced Visualization Option to shade the area below the line:

LiveView Desktop query views now have additional options for pausing a query (grid or chart). The new query pause button () has a pull-down menu that allows you to choose the option Pause when not visible after 10s.

When a query (grid or chart) is hidden from view (behind another view or not on screen after a perspective switch) for 10 seconds, and this option is selected, that query is paused to save client and server resources. You can set the pause length as follows:

The LiveView Desktop preferences now allow you to set numeric column alignment in the table query view. From LiveView Desktop, select Window → Preferences. This opens the Preferences dialog:

Select TIBCO StreamBase LiveView in the left-hand navigation pane and set Numeric Column Alignment to the desired value.

You can now rename a query as part of editing the query predicate. Right-clicking the saved query name in the Tables pane of LiveView Desktop opens the following options:

The Rename option was removed. The Edit Saved Query dialog now has a Name field:

A configured alert rule action will now display in the Alert Action dialog with information about the specific action.

LiveView 1.2 supports real-time alerts that provide timely notification of critical conditions. When you configure an alert, you request real-time notification that specific alert conditions are occurring. LiveView alert rules can be configured through a browser with the new LiveView WebUI or through LiveView Desktop. You can see how to configure an alert at LiveView Alerts.

Two new sample projects, sample_lv-alerting and sample_lv-alerting-advanced, show you how to configure alerts. To load these samples from StreamBase Studio, select File → Load StreamBase Sample. The README files in the project directories provide more information on how these samples work.

LiveView 1.2 supports full-active table joins. A full-active table join is a join of two LiveView tables, a local table and a foreign table, whereby join processing occurs when a row in the either the local or the foreign table is inserted or updated. As in a half-active join, when a row in the local table is inserted or updated, a lookup of a row in the foreign table is performed based on the join keys, and the lookup results update the data in the local row. Additionally, when a row in the foreign table is inserted or updated, all rows in the local table that match the join keys are updated.

You can now perform dynamic aggregation on your data. Dynamic aggregation is performed on the fly by a query against a LiveView table. LiveView 1.2 supports dynamic aggregation through the two client APIs:

The sample project sample_lv-java-clientapi contains an example query, DynamicAggregation.java, that performs dynamic aggregation.

LiveView product documentation is now available as an Eclipse Help plug-in for StreamBase Studio. When you install LiveView Server, Studio Help that you access with the Help → Help Contents menu now contains both StreamBase and LiveView documentation.

If your default browser is Internet Explorer 9 or 10, see LiveView .NET Client API Documentation for important browser configuration information regarding LiveView .NET Client documentation.

LiveView 1.2 has new aggregate functions Min, Max, and LastVal.

In previous releases, StreamBase Studio would, by default, display generated project directories in the Package Explorer view. This means that when you compiled and ran a LiveView project, the lv-bin and lv-systemdata directories would appear in the project folders. These directories are created for generated files only, and should not be edited in the normal use of LiveView projects. Since these files are not usually edited by users, these directories are no longer displayed by default.

To re-enable the view of generated project directories in the Package Explorer view, follow these steps:

In previous releases, when you compiled a LiveView Project, LiveView stored all generated files in the project's lv-bin directory. You can now customize the project setting to store generated files in any directory.

On Linux systems, you can use the lv-server define-service --service-user option to configure LiveView Server to run as an automatically starting service using the credentials of a specific user. See the lv-server reference page.

The %STREAMBASE_HOME%\liveview\tools directory is now on the system environment's PATH by default. Note: this path shown here is no longer accurate as of release 2.0.0.

When you run LiveView projects, the project uses both a LiveView (Jetty) port and a StreamBase (sb) port. The default values for these ports are 10080 and 10000, respectively. You can set the values for either port. Follow these steps:

LiveView does not support complex queries with nested parentheses.

This release contains a workaround that may be effective in some cases. By enclosing an entire predicate in double parentheses, as in (( predicate )), you can specify that the predicate is to be parsed as a StreamBase predicate, not a LiveView predicate, and you can use a more complex syntax. The predicate is parsed purely as StreamBase Expression Language, LiveView operators and syntax are not applicable, and the query is executed via table scan.

In a future release, LiveView queries may evolve to fully support the StreamBase Expression Language, extending the functionality and complexity available in queries while providing indexed query execution where possible. This evolution would require migration of existing queries and alert rule conditions from the LiveView Query Language to the StreamBase Expression Language.

The lv-client command-line tool has additional options and commands. See the lv-client reference page.

LiveView Server logging is by default set to a less verbose setting than in previous releases. To re-enable verbose logging in your LiveView project, edit your project-specific LiveView Server sbconf file, and add the following line to the <jvm-args> element:

<sysproperty name="logback.configurationFile" value="LVDebugLogback.xml"/>

To enable logging of all debugging, including all StreamBase debugging, add this line:

<sysproperty name="logback.configurationFile" value="LVSBDebugLogback.xml"/>

In previous releases, LiveView system tables and the fields for those tables used an all-lowercase, underscore-delimited naming convention (lv_table_name). The convention for system tables and field names is now CamelCasing (LVTableName).

The lv-server and lv-client tools have man page help on Linux systems. These files are found in the $STREAMBASE_HOME/man directory.

LiveView Desktop 1.2 has significant improvements to the table views.

The column chooser from the left pane has been replaced with a contextual menu item in the table query view. To customize table columns, right-click anywhere on the table in the table query view area and select Columns:

This will open the new Column Chooser dialog:

This dialog lets you select which table columns will be shown in the table query view. In addition, the Make Default button saves that view to your LiveView Desktop configuration so that the selected view persists across LiveView Desktop sessions.

Every table query view tab now has a Refresh every... menu item in the View Menu () that lets you choose the refresh rate of the table or query.

LiveView 1.2 Desktop now has quick query functionality. The top-right corner of your LiveView Desktop now has two windows. The first allows you to select a table name; the second allows you to type a query predicate to be executed. For example, this window shows a query against a field called quantityRemaining in a table called Items:

LiveView Desktop automatically opens the Connect to LiveView dialog at startup.

You can now save the result of a LiveView query directly to an Excel file. From the query tab, click the View Menu button () and select Export Data to Excel Spreadsheet:

LiveView 1.2 adds Panopticon chart options Linegraph and Needlegraph for display of time-based transactions.

You can add icons to table cells from the Conditional Formatting context menu. The Edit Conditional Formatting Rule dialog box now has a Set image option. Selecting this option and clicking Choose will open the Image Chooser box:

To see an example of icon use, load and run the sample_lv-alerting-advanced.

LiveView Desktop 1.2 supports pausing table updates or query updates. The table query view has a pause button ()that will pause the updates in your query view. The table or query is still being updated, but the view is paused.

You can now disconnect LiveView Desktop from a running LiveView Server instance without closing LiveView Desktop. The File → Disconnect option will shut the connection between your current LiveView Desktop session and the LiveView Server.

LiveView Desktop offers a logging view for troubleshooting purposes. To open logging when LiveView Desktop is active, press Ctrl+3 and type logging in the pop-up window.

LiveView Desktop Query Charting View now allows you to configure colors for non-numerical dimensions in your query results. For example, if you have a string dimension, you can map string values to specific colors from a color palette.

In previous LiveView releases, if you configured an action against a table, every time you executed that action, the action would either open a new view, or focus the view that corresponded to the previous execution of that action. You can now configure table actions to reuse the same view from the previous execution of that action. The Reuse views for all actions from this query that query the same table option of the Edit Table Action dialog allows you to associate a query and a table to a single view:

In previous releases, the row limit on queries was fixed. You can now change query row limits globally with LiveView Desktop Preferences. You can also set query row limits against individual tables. To set query row limits against a specific table, right-click the table name in the Tables pane of LiveView Desktop and choose Defaults → Query Row Limit.

The Tables view now shows table and field descriptions when those descriptions are present in the server configuration. These descriptions are drawn from the table's lvconf file. See LiveView Configuration XML Reference for more information about lvconf files.

Before you upgrade LiveView, make sure that all LiveView Server instances on the machine you are upgrading are stopped.

LiveView Server connections now use the lv:// protocol and default port 10080. This is different than earlier versions of LiveView, which used the sb:// protocol and default port 10000. When you upgrade LiveView Server and LiveView Desktop, the default URI is updated. If you have saved URIs that use other port numbers, you must edit the URI to use the lv:// protocol and the LiveView port number (which is generally the sbd port number plus 80).

The sb:// protocol for LiveView connections is deprecated and will be removed in a future release. In LiveView 1.2, you can still use the sb:// protocol to connect LiveView Desktop to LiveView Server, but you will not have access to many of the current LiveView features.

You can now include a username with connections from LiveView Desktop and LiveView Web UI to LiveView Server. For LiveView 1.2, this username field is not validated and can be any string or can be left empty. In future releases, this field may be used to create LiveView user profiles.

The required input stream for LiveView tables, DataIn, has an updated schema. The DataIn stream now requires four fields (instead of three):

The CQSDataUpdatePredicate field is new in LiveView 1.2. If you are running projects that you configured for LiveView 1.1, you might need to update your project.

LiveView Desktop now allows you to edit previously saved queries by right-clicking the name of the query in the Tables pane and selecting the menu item Edit Query Predicate:

LiveView 1.1 adds to StreamBase Studio the ability to start LiveView Server from the context menu of any lvconf file in a project, or from the project itself. This feature is described in Start Here, in Starting LiveView Server from StreamBase Studio. The same document describes how to start and stop LiveView Server from the command line.

This release adds support for building LiveView clients using a .NET language. The LiveView .NET Client Library requires StreamBase 7.2.6 or later on the development PC, and requires version 3.5 or later of the .NET framework, with version 4.0 recommended.

The .NET assembly is installed as %STREAMBASE_HOME%\sdk\bin\StreamBase.LiveView.API.dll. During development, use this reference path for Visual Studio projects that use the API. When you use this reference path, IntelliSense tips for the LiveView API are available in Visual Studio. API documentation is provided in HTML format, linked from the Start menu and from the LiveView documentation home page.

To deliver your client programs to a PC without StreamBase installed, you must:

To manage server configuration settings, place a StreamBase Server configuration file (an sbconf file) named sbd.sbconf at the root of your Studio project directory. When running LiveView Server from the command prompt, place the sbd.sbconf file at the root of your LiveView configuration file directory (which is usually the same as your Studio project directory). The project-specific sbconf file is automatically merged with the default LiveView Server sbconf file, which maintained internally.

If you have a need to run multiple LiveView Server instances on the same machine, you must change the ports on which they run to avoid conflicts. The default port for LiveView Server itself is 10000, while the default port for access to the services layer through a client API is 10080. Place a project-specific sbd.sbconf file, as described in the previous section, in the configuration directory of each LiveView configuration instance you want to run. Specify the LiveView Server port with the tcp-port parameter and the services layer ports with the liveview.port system property, as shown in the following example.

<?xml version="1.0" encoding="UTF-8"?>
<streambase-configuration xmlns:xi="http://www.w3.org/2001/XInclude"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="http://www.streambase.com/schemas/sbconf/">
  <server>
    <param name="tcp-port" value="12000"/>
  </server>
  <java-vm>
    <sysproperty name="liveview.port" value="12080" />
  </java-vm>
</streambase-configuration>

Logback logging is enabled by default when running LiveView Server, as when running StreamBase Server, as described in the StreamBase documentation. You can configure logging by specifying the location of a Logback configuration file, usually named logback.xml, in your project-specific sbconf file. Provide the full path to the logback.xml file. For example:

<streambase-configuration>
  <java-vm>
    <sysproperty name="logback.configurationFile" 
                 value="/path/to/logback.xml"/> 
  </java-vm>
</streambase-configuration>

The LiveView installation includes an example of a debugging Logback configuration file that provides for more verbose startup and operation log messages than the default configuration. This file is installed as $STREAMBASE_HOME/liveview/server/engine/LVDebugLogback.xml.

Table and charting actions that open an existing saved query can now optionally perform string substitution. When an action is executed against a row in a table, the predicate is assigned and the saved query is executed as a new unsaved query with the string substitution having taken place over the predicate string.

For example, a configured and saved query with predicate "color='$color'" running against a row where color is "blue", would run a new query with "color='blue'". The resulting query will have all the attributes from the original saved query.

LiveView Server is now supported using JDK 7, update 4 or later, as an alternative to the JDK 6 shipped with StreamBase. To use JDK 7, follow the instructions on Using an External JDK.

To use JDK 7's G1 garbage collector, add these parameters to the <jvm-args> element of the sbconf file used with LiveView Server:

Be sure to copy the entire <jvm-args> element from the default sbconf file, described above, and add these parameters to the list. At the same time, remove the following parameters, which configure the non-G1 garbage collector:

This release adds support for half-active joins of two LiveView tables, configured by using the <join> child element of the <preprocessor-chain> element in an lvconf configuration. This join is a join of two tables, a local table and a foreign table, whereby when a row in the local table is created or updated, a lookup of a row in the foreign table is performed based on the primary key, and the lookup results augment the data in the local row.

You can now load LiveView sample projects from the Load Sample Projects dialog box. Open the Load Sample Projects dialog box from the File → Load StreamBase Sample option in StreamBase Studio and select the sample project name.

In a <transform> configuration, publishing between two tables in a cycle is normally disallowed. There are rare cases when it makes sense to, for example, publish from table A to table B, with table B publishing back to table A. For these cases, you can specify a <transform> configuration with the allow-cycle="true" attribute. Use this setting with great care so that you do not create infinite loops.

The <aggregation> and <transform> child elements of the <data-source> element both now support a new attribute, use-snapshot-parallelism. When a table is configured with snapshot-parallelism, setting this attribute to true allows the aggregation or transform processing to run in the same parallel region as the query snapshot processing, for better performance.

The command lv-server --version returns version information on LiveView.

The LiveView Query Language now includes the NOTMATCH operator.

This release provides improved query performance in certain cases. To support this improved performance, the order of results returned by a query now depends on the query's predicate and the target table’s indexes. If any of the indexes (<primary-key> and <indices>) of the target table contain all fields in the predicate, then the results are ordered such that the most recent entry is first. Otherwise, the order of query results is not guaranteed.

Customers can override this behavior. Contact TIBCO Technical Support for further information.

On Windows, with StreamBase 7.2.5 as the companion installation, it is possible for startup of LiveView Server to fail with a message referring to an XML file and an error message stating "requested operation cannot be performed on a file with a user-mapped section open". The failure is timing-dependent; the workaround is to retry startup. When using StreamBase 7.2.6 as the companion installation, this issue is resolved.

In previous releases, LiveView Desktop would fail to start if StreamBase was not installed on the machine and Java was not found in the PATH. The LiveView Desktop installer now installs an embedded JRE for private use by LiveView Desktop.

In a chart workbook viewer, you can now execute table actions. For chart elements that correspond to one row in the underlying data table, right-click to see the data in that row.

The workbook viewer, when reading a Panopticon workbook file and the definitions contained within, now honors data source names over data table names when there is a table name match. This allows you to have a workbook that is issuing queries against more than one table, by using (for example) two data source names: Orders and Executions, which, as long as both are available as tables at the connected server, are used as the data source. When data source names do not match table names, the data table name is used. Since Panopticon often uses data source names based on filenames (such as Orders – Sheet 1.xls), LiveView Desktop tries various heuristics to match those names to tables.

You can now rename saved queries. If that query's view is open but obscured, the view's tab will not reflect the new name until you expose the tab.

In the Conditional Formatting dialog, there are now Up and Down buttons to reorder rules. The Preferences dialog, TIBCO LiveView panel, lets you specify default format strings for double, long, and timestamp data types. In addition, a new formatting operand, always, means to always apply the specified format string for the entire column, which allows per-column customized formatting. Format strings follow the patterns defined in java.text.DecimalFormat for longs and doubles, and in java.text.SimpleDateFormat for timestamps.

For example, if you want a column of doubles to look like a price field with dollar sign and two-position decimal place, colored green for values greater than or equal to 30 and colored red if under 30, specify the following three rules in this order:

The rules must follow this order or the >= 30 rule will fail. This is because all formatting accumulates over the conditionally formatted values, and $24.49 does not look like a number because of the dollar sign.

A new option added to LiveView Desktop's View menu allows you to temporarily disable all conditional formatting for the selected table. Open the View menu with the down-facing arrow () in the toolbar for each Table view window.

In addition to copying the selected row in a Table view, you can now click to select a cell, right-click, and from the context menu, copy the contents of the selected cell. The cell's column name shows in the context menu.

In a Table view with many columns, you can now type the first few letters of a column name to automatically scroll to the first column whose name begins with the typed letters. If you type a lowercase letter, it matches upper and lowercase column names; if you type an uppercase letter, it matches the first column with that uppercase letter.

In general, to distinguish similar column names, you can keep typing letters until the column name is uniquely specified. For example, consider a table with the following column names in this order:

apple channel Apple Customer Aardvark CardCode

The Preferences dialog for LiveView Desktop now has a Web Browser panel that lets you specify where to load URLs that occur in Table views. You can select between the internal web browser that is part of LiveView Desktop, or a system browser.

Clicking an alert not only brings the query view into focus, it now also sets the current selection to the rows that caused the alert.

The names of the files used to persist tables have changed in LiveView 1.1, and LiveView does not restore old data after an upgrade from a previous version of LiveView. If your LiveView configuration enables persistence, delete the old data directory (which you configured in your lvconf files) before you upgrade to 1.1.

If you are upgrading from an earlier version of LiveView, after upgrading but before you restart LiveView Server, you must delete the lv-bin directory and all of its contents to ensure recompilation of your LiveView configuration on restart.

In <expr-macro> elements that define expression macros in an lvconf configuration, the syntax for table fields has changed from :fieldname to $fieldname. If you have lvconf files that use the old syntax, replace all instances of :fieldname with $fieldname.

The shards attribute of the lvconf <table-space> element is now deprecated and replaced with the snapshot-parallelism attribute. Snapshot-parallelism means the same thing as shards: the number of parallel threads used to scan a table during the snapshot portion of a query.

The shards attribute is still supported, but may be removed in a future release.

The increment-on-update attribute of the lvconf <data-table> element is now removed.