Supported Configurations

This topic describes the hardware and software configurations supported in StreamBase 6.0.1.2 .

Supported Configurations

In the following table, the term x86_32 refers to the 32-bit Intel Pentium architecture, while x86_64 refers to the AMD64 architecture (including Opteron and Athlon 64 processors) and the Intel64 architecture (including EM64T, Xeon, and Core 2 processors).

Note

StreamBase Developer Edition is available for Microsoft® Windows™ and Red Hat™ Enterprise Linux only. For details, see Comparison of Developer and Enterprise Editions.

Operating systems

StreamBase Server plus StreamBase Studio authoring environment:

  • Red Hat Enterprise Linux AS 4.0 (32-bit), with the latest updates installed, on x86_32 or x86_64 processors.

  • Red Hat Enterprise Linux AS 4.0 and 5.0 (64-bit), with the latest updates installed, on x86_64 processors.

  • Novell SUSE Linux Enterprise Server 9 and 10 (64-bit), with the latest updates installed, on x86_64 processors.

  • Microsoft Windows XP Professional or Windows Server 2003 (32-bit), with the latest service packs installed, on x86_32 processors.

  • Microsoft Windows Server 2003 (64-bit), with the latest service packs installed, on x86_64 processors.

StreamBase Studio only:

  • Windows Vista, with the latest service packs installed, on x86_32 processors.

StreamBase Server only:

  • Sun Solaris 10 (64-bit) with the latest updates installed, on supported SPARC processors.

Also see the Illustrations of the Supported Local and Remote Connection Configurations.

Note for Windows XP SP3. StreamBase's support for Windows XP includes SP3, and the bundled JDK shipped with StreamBase is compatible with XP SP3. If you use an external JDK, it must be 1.5.0_15 or newer to work with XP SP3.

Processor Architectures

For all Intel processors, hyperthreading is supported. For Intel and AMD processors, multiple CPU cores are supported and encouraged.

For Red Hat Enterprise Linux machines:

  • x86_64

  • x86_32

For Novell SUSE Linux Enterprise Server machines:

  • x86_64

For 32-bit Windows machines:

  • x86_32

For 64-bit Windows Server 2003 machines:

  • x86_64

For Solaris SPARC machines:

  • 64-bit SPARC, single or multiple processors

CPU clock speed
Minimum Recommended
1 GHz 2 GHz or faster
RAM
  Minimum Recommended
For development:  512 MB 1 GB or more
For staging:  512 MB 2 GB or more
For production:  Determined value*  Determined value* 

* For production servers, determine the appropriate RAM amount from peak-load and volume testing on your staging servers.

On x86_32 hardware with 4 GB of physical RAM installed, the effective maximum RAM available to any operating system ranges between 3.0 and 3.6 GB, depending on hardware configuration. If this maximum is insufficient for running your StreamBase applications, consider migrating to one of the supported 64-bit architectures.

Disk capacity Disk use is highly dependent on the volume of data that you store. A 40 GB disk should be sufficient for development purposes. Installation of StreamBase, including kit size plus installed files, requires approximately 500 MB.
JDK

To run StreamBase applications, you must have a Sun JDK (not just a JRE). StreamBase supports:

  • Sun JDK 1.5.0_15 or later

  • Sun JDK 1.6.0_03

There is a reported bug in Sun JDK versions 1.6.0_04, 1.6.0_05, and 1.6.0_06 that potentially interferes with the operation of StreamBase. StreamBase Systems does not recommend using those JDK versions with the current release.

To compile your own StreamBase Java clients and custom functions with the StreamBase Java API, you must have Sun JDK 1.5.0 or 1.6.0 installed. StreamBase Systems recommends that you compile with the same minimum JDK versions as listed above.

JDK notes:

  • A JRE is not sufficient to run StreamBase applications; you must have a JDK.

  • On all supported operating systems, the StreamBase kits install the runtime components of Sun JDK 1.6.0_03 for you in a subdirectory of the installed StreamBase directory. 64-bit systems get a 64-bit JDK. The 64-bit Windows overlay installer adds a 64-bit JDK to the base kit's 32-bit JDK.

  • You can configure StreamBase Enterprise Edition to use another supported JDK instead, as described in Using an External JDK.

Network A TCP/IP network is needed for the following configurations:
  • StreamBase Studio and applications on Windows connecting to a Linux or Solaris machine where StreamBase Server is installed. This type of connection requires SSH.

  • StreamBase Studio and applications on Linux connecting to a remote Linux or Solaris machine where StreamBase Server is installed. This type of connection also requires SSH.

The host UNIX machine must have an SSH daemon running with both TCP port forwarding and password authentication enabled. Make sure your /etc/ssh/sshd_config file does not contain the following lines:

AllowTcpForwarding No
PasswordAuthentication No

If you update the sshd_config file, remember to restart the SSH daemon before any users launch StreamBase Studio.

Important

SSH is not needed or used when StreamBase Studio and Server are installed and running on the same Windows or Linux machine.

External JDBC-compliant databases

StreamBase supports interaction with JDBC-compliant (2.0 or later) external databases:

  • Oracle® 9i, 10g

  • IBM® DB2 v9

  • Microsoft SQL Server 2005

  • MySQL 5

  • Sybase® ASE V12

  • Sybase IQ V12.7

  • Vertica V1.3

  • Vertica V2.1

There are several ways of interacting with the supported external databases:

  • For StreamBase Enterprise Edition users, your applications can use the JDBC Table data construct in an EventFlow diagram, or APPLY JDBC statements in a StreamSQL application. For details, refer to Using JDBC Data Sources in the Authoring Guide.

  • You can also use the external StreamBase Adapter for JDBC, which is available in a separate kit. The documentation is provided in the StreamBase Adapters Guide.

Chronicle databases

StreamBase Chronicle is an optional feature that supports interaction with one the following external event-store databases:

  • IBM® DB2 Data Stream Engine v9

  • Sybase® RAP, the Traders Edition

  • Vertica 1.3

  • Vertica 2.1

  • Vhayu Velocity 6.4+ / Reuters RTCE 6.4+

For details on using Chronicle, refer to Using Chronicle Data Sources.

Building StreamBase C++ custom functions or clients on Windows To compile C++ custom functions on Windows, StreamBase supports Microsoft Visual Studio .NET 2003 (VC 7.1). Important details are provided in Creating Custom C++ Functions in the API Guide.

To compile C++ clients on Windows, StreamBase supports Microsoft Visual Studio .NET 2003 (Visual C++ 7.1) or Visual Studio .NET 2005 (Visual C++ 8.0). Important details are provided in Creating C++ Clients in the API Guide.

Building StreamBase C++ custom functions or clients on UNIX StreamBase requires GCC 3.4.x or later for building C++ clients and custom functions on UNIX. For further information, see Creating Custom C++ Functions and Creating C++ Clients in the API Guide.
Building .NET clients on Windows To develop .NET client applications, you must have Microsoft Visual Studio .NET 2005 (Visual C++ 8.0).

Embedded Adapters

(Some included, some available separately.)

Adapters are programs that convert data to and from the StreamBase tuple protocol.

Embedded adapters execute in the same StreamBase Server process that runs your StreamBase application. The base StreamBase installation includes a number of embedded adapters, and others are available in separate installation kits. For details, see the Adapters Guide.

External Adapters

(Available separately)

External adapters run in separate processes, and possibly on separate machines, from the StreamBase Server running your application.

The following list is subject to change. Version requirements of the associated third-party software is listed elsewhere in this table.

On 64-bit Linux:

  • StreamBase Adapter for JDBC

On 32-bit Linux:

  • StreamBase Adapter for JDBC

  • StreamBase Adapter for TIBCO® Rendezvous™

  • StreamBase Adapter for EMS/JMS

  • StreamBase Managed Publishing Adapter for Reuters RFA

  • StreamBase Adapter for Reuters SFC

On 32- and 64-bit Windows:

  • StreamBase Adapter for Microsoft® Excel

  • StreamBase Adapter for JDBC

  • StreamBase Adapter for TIBCO Rendezvous

  • StreamBase Adapter for EMS/JMS

  • StreamBase Managed Publishing Adapter for Reuters RFA

  • StreamBase Adapter for Reuters SFC

JDBC Note

See External Databases for more information about supported data sources.

64-bit Note

You can run a StreamBase Server process and its hosted StreamBase application on a 64-bit machine, with an external adapter running on and connecting from a supported 32-bit machine.

Spreadsheet software To use the external StreamBase Adapter for Microsoft Excel to view the output of a StreamBase application's processing, or to enqueue data from a spreadsheet into a StreamBase application, you must have Microsoft Excel 2002 (part of Office XP), 2003, or 2007. For more information, see the Adapters Guide and the documentation that accompanies the StreamBase Adapter for Microsoft Excel.
Rendezvous messages To use the StreamBase Adapter for TIBCO Rendezvous, you must have Rendezvous version 7.2 installed on your Windows or Linux machine. For more information, see the documentation that accompanies the StreamBase Adapter for TIBCO Rendezvous.

Reuters components

StreamBase Reuters adapters support RMDS 5 and RMDS 6 infrastructure components. Each Reuters adapter supports a separate Reuters API or combination of APIs.

Consult with your StreamBase Systems representative for the latest information on Reuters API support.

Screen resolution To use StreamBase Studio, your monitor's screen resolution should be at least 1024 x 768 pixels. Higher resolution settings are recommended.
HTML browser The StreamBase online documentation supports any of the following browsers:
  • Mozilla Firefox 2.0 or later

  • Microsoft Internet Explorer 6 or 7

Supported Local and Remote Connection Configurations

This section illustrates the local and remote connection configurations that are supported by StreamBase.