StreamBase 3.5 Release History

Oracle 9i

IBM DB2 v9

Microsoft SQL Server 2005

Sybase ASE V12

The SQL-like logical operators AND and OR can be used in place of && and ||. The SQL-like equality operator = can be used in place of ==. These are documented in the StreamBase Expression Language and Functions topic.

The separately installed StreamBase Adapter for EMS/JMS adds support for wildcards. Background information: EMS supports the notion of wildcarding. In EMS you can subscribe to many different destinations. For example, you might create a destination for each stock symbol and subscribe to them all. Also, destinations can be given a hierarchical organization, such as MyCompany.application.symbol. In EMS, you can subscribe to many destinations at once by using a wildcard. For example: MyCompany.application.*, so that you do not have to subscribe to each symbol individually.

StreamBase support this with the EMS enqueue and dequeue features of the external StreamBase Adapter for EMS/JMS. However, this support means different things in each instance. On the enqueue side, we comply with EMS wildcarding. A wildcarded destination (MyCompany.application.*) can be subscribed to by including it in the configuration file. However, EMS wildcarding does not apply in the same way on the dequeue side. Including a wildcarded destination in the dequeue config file will not cause a message to be broadcast to each destination encompassed by the wildcard. On the dequeue side, 'wildcarding' is used to refer to the fact that messages can be sent to individual destinations without having to configure each destination. If an application uses many destinations, then configuring each destination my prove to be onerous. If a destination is not configured in the dequeue adapter, and StreamBase routes a message to it, its configuration is created at runtime using a default configuration. The default values that are specified in the configuration file are used to configure any new destinations. For related information, see this external adapter's documentation, which is installed (by the separate StreamBase Adapter for EMS/JMS kit) in streambase-install-dir/doc/adapter/ems-adapter.html.

StreamSQL, a new text-based language, can be used to query streaming data and create StreamBase applications. StreamSQL applications, which have the file extension, .ssql, can be reused as modules in combination with traditional, graphically designed application diagrams (.sbapp files). StreamBase Studio includes a new document editor for creating StreamSQL applications.

StreamSQL is documented primarily in the new StreamSQL Guide, and in the section entitled Building StreamSQL Applications, in the StreamBase Terms and Components topic of the Getting Started Guide.

A new Java API, com.streambase.sb.adapter.Adapter, can be extended to write custom embedded adapters. Embedded adapters are included in your StreamBase application, and run in the same StreamBase Server (sbd) process. This configuration reduces the client/server communication overhead that is seen with external adapters. Also, embedded adapters start and stop automatically with the StreamBase application, simplifying administration tasks.

This release of StreamBase includes embedded input adapters to get data from CSV files and Regular Expression files, and output adapters to send data as E-mails, or to CSV or XML files.

For more information, start in the new Adapters Guide It contains topics about both the embedded adapters and the external adapters, which have separate installation kits and documentation. Be sure to also see the new API Guide topic, Using the Embedded Adapter API

StreamBase applications can get data from and send data to an external JDBC 2.0 (or later) compliant data source, such as DB2. In application diagrams, a Query operator can be connected to a JDBC Table data construct. Then SQL statements such as SELECT, INSERT, UPDATE, and DELETE can be sent to an external datasource defined in the sbd.sbconf file. In StreamSQL applications, APPLY JDBC statements can be used to query tables in a datasource.

The StreamBase Server configuration file, sbd.sbconf, includes a new data-sources section that provides configuration and critical run-time parameters for application interaction with external JDBC datasources. The data-sources section is documented in the java-vm section of the StreamBase Server Configuration XML topic.

C++ custom functions used in StreamBase applications must now be declared in the StreamBase Server configuration file, .sbconf. For more information, see the Configuration Steps section in Creating Custom C++ Functions, in the API Guide.

There are some API differences between StreamBase 3.5 and earlier releases.

As noted elsewhere in the documentation, you will need to recompile and relink any existing, pre-3.5 C++ client to work with StreamBase 3.5. If you do not, you will see a "protocol mismatch" error when your client tries to connect to a 3.5 StreamBase Server.

In the Tuple class, the methods getStringBytes, getBoolean, getDouble, getInt, getString, getTimestamp all can throw NullValueException in 3.5. In pre-3.5 clients, these methods could only throw TupleException. Existing, pre-3.5 clients that use these methods will need to accommodate this new exception.

The StreamBase adapter for EMS/JMS has the following enhancements:

Three new demos have been added to the Demo perspective, which was introduced in the previous release. Each demo showcases StreamBase capabilities in a different field of interest:

Click Window → Open Perspective → Menu to open the Demo perspective.