Installing on Windows

This page describes the installation of the Spotfire Streaming base kit on Windows platforms. The base kit for Windows includes the StreamBase Studio authoring environment, the Streaming Runtime, and support files for the StreamBase and LiveView Client APIs.

Before You Install

Before you install Spotfire Streaming, use the following checklist to make sure each target machine matches the prerequisites.

    Read through the Release Notes for the current release to look for any late-breaking information about installing on Windows.
    If you have used StreamBase Studio on the target machine, back up your existing Studio workspace and configuration, as described below.
    Confirm that the target machine is running a supported version of Windows with the latest updates. See Supported Configurations.
    Confirm that the target machine's RAM and disk space requirements meet or exceed the minimums listed on Supported Configurations. This is especially important when running on virtual machines.
    Depending on the target machine's configuration, you may need administrator rights to install into the default location.

Back Up Existing Streaming Workspace

If you used a previous release of StreamBase Studio on the target machine, create backup copies of your existing Studio workspace directories, before using StreamBase Studio in the current release. Save the backup copy with filenames that indicate the version number of the release you are archiving. For example, save

The default location of the StreamBase Studio workspace directory is described in Default Installation Directories. You may have specified a different directory the first time you ran StreamBase Studio.

Maintaining Multiple Streaming Releases

You can install more than one release of Spotfire Streaming on the same Windows computer, with specific limitations outlined below.

  • Maintenance releases are always installed in the parent release's directory. For example, release 10.6.2 would be installed in the Streaming 10.6 directory. If you also have a 11.0.x release on the same machine, it would not be affected by installing 10.6.2, because 11.0.x would be located in the C:\TIBCO\str\11.0 directory.

  • New maintenance releases replace any previously installed release for the same major.minor version on your system, which means you must uninstall the existing release in the same major.minor series.

  • Installing new releases of the same major.minor series does not impact existing Streaming deployments. Your Studio workspaces persist independently of the installed software.

Uninstalling a Previous Release of Streaming

To install a maintenance release, you must first uninstall any existing version of the same major.minor release. If you do not, the Streaming installer prompts you to uninstall the existing one.

Do not remove the Streaming installation directory manually. That is, do not drag it to the Recycle Bin or select it and press Delete, or remove it at a command prompt. Instead, to uninstall a previous Streaming release, use the Uninstall a program page in the Windows Control Panel.

Uninstalling a previous Streaming release does not affect any Streaming application files you created in that release. The Streaming uninstaller only removes files that the installer placed on your disk, and deliberately leaves certain files in place:

  • Your Streaming Studio workspace and configuration directories are preserved.

  • Any Eclipse plug-ins you downloaded and installed into StreamBase Studio are left behind, including any data, log files, and directories they use.

Installation Procedure

To install Streaming on Windows, follow these steps:

  1. If you are installing a maintenance release for an existing installation, first uninstall the existing Streaming release, as described in Uninstalling a Previous Release of Streaming.

  2. Launch the Spotfire Streaming installer by running the .msi installer file that you downloaded from the TIBCO distribution site.

    The installer is named SPOT_str_11.1.0_win_x86_64.msi.

  3. Follow the instructions on screen to accept the Streaming license agreement.

  4. Accept the default Streaming installation location or browse to a different location. However, NEVER try to overwrite an existing previous Streaming installation.

  5. Click Install to begin the installation process.

  6. On the installer's final screen, select the checkbox to open the post-installation README in your Web browser to see important information. The README describes the entries installed in the Windows Start menu for this release.

  7. Click the Finish button.

64-Bit Windows Considerations

Streaming is only supported on 64-bit Windows. This gives rise to the following considerations:

  • Microsoft does not support loading 32-bit shared libraries or DLLs into 64-bit processes. Thus, if you have any StreamBase plug-ins such as custom clients written in C++ with a previous Streaming release, they must be recompiled for 64-bit operation.

  • The 64-bit Streaming installation includes 64-bit link libraries for C++ and .NET, which allows you to rebuild any custom client applications for 64-bit operation.

  • Any embedded adapter that calls Windows-native libraries for underlying support must be adjusted to load the 64-bit version of those shared libraries, if available.

Windows Start Menu Considerations

This section describes Windows Start menu changes made by the StreamBase and LiveView installers.

Start Menu for Windows 10

On Windows 10, Start menu entries for Spotfire Streaming are placed in a single TIBCO folder.

Windows 10 does not allow subfolders to appear in the Start menu. That is, in Windows 7, the Start menu was organized with a top-level TIBCO folder that contained subfolders for various Streaming components. However, Windows 10 now allows only the top-level TIBCO folder in the Start menu, which means the contents of the previous release subfolders are concatenated into a single folder.

If you have a single TIBCO product installed, the Windows 10 Start menu organization works well. However, if you have more than one TIBCO product installed, all Start menu entries from all products appear together in one long TIBCO menu.

Of course, the installers for existing products cannot be retroactively reconfigured to install each TIBCO product into its own top-level Start menu folder. Eventually, newer releases of TIBCO product installers, including installers for Spotfire Streaming, will catch up with the new restrictions imposed by Windows 10.

In the meantime, you can manually reorganize your Start menu to place the menu entries for each TIBCO product into their own top-level, product-specific Start menu folder. Follow these steps:

  1. Use one the following Windows 10 key combinations:

    • Enter Windows-key+R and type shell:common start menu. Use this method if you installed your TIBCO product in a system-controlled folder such as C:\TIBCO or C:\Program Files. (By default, Spotfire Streaming is installed in C:\TIBCO.)

    • Enter Windows-key+R and type shell:start menu. Use this method if you installed your TIBCO product in a personal folder as part of your Windows home directory.

  2. This opens a new Explorer window to the top of the System or Personal Start menu, respectively. Double-click Programs to enter the Start menu folder itself.

  3. Look for a folder named TIBCO. If not found, use the other key combination and look again. (It is also possible to have a TIBCO folder in both Start menu locations.)

  4. Look inside the TIBCO folder. If it contains subfolders for the product of interest, move each entire subfolder, one at a time, one level up to become a sibling of the TIBCO folder.

  5. Rename each moved subfolder so that it begins with "TIBCO". This keeps all TIBCO products alphabetically together in the Start menu. For example, move StreamBase 11.1 up parallel to its containing TIBCO folder, and rename it Spotfire StreamBase 11.1. Do the same for any Live Datamart 11.1 subfolder you may have.

  6. If you have other TIBCO products installed, including other versions of Streaming, move their subfolders or move their individual menu entries for each product in turn.

    1. If your TIBCO folder contains individual menu entries instead of, or alongside subfolders, create new top-level folders, parallel to TIBCO, to contain the Start menu entries for each product of interest.

    2. Move the appropriate menu entries from the TIBCO folder to the newly created top-level folder.

  7. When the TIBCO folder is empty — that is, when all of its contents have been moved up to new top-level folders — you can delete the empty TIBCO folder.

Installing Additional Features

TIBCO provides separate installer files for add-in products such as the High-Performance FIX Engine and StreamBase Manager.

As downloaded from the TIBCO distribution site, the installers are delivered in a single file named with the following pattern: SPOT_productid_major.minor.servicepack_win_arch.msi

where productid identifies the add-in or adapter, major, minor and servicepack identify the specific release, and arch identifies the targeted CPU architecture, either x86 for 32-bit or x86_64 for 64-bit.

After completing the installation of Streaming on Windows, you can next install any external adapter or add-in product for which you have a license, using its separate installer.

The installers for most add-in products look for a matching Streaming base release, and only allow installation of the product into that base release's directory. By contrast, external adapters can be installed on a machine that does not have a Streaming installation.

Using the StreamBase Command Prompt

On Windows, the Streaming Runtime and all Streaming command-line utilities must be run from a StreamBase Command Prompt that you invoke from the Windows Start menu or from a shortcut on the Windows Desktop. Do not use the standard Windows command prompt. The StreamBase Command Prompt has its environment and PATH preconfigured for running Streaming commands and utilities.

See Environment Settings for a table of the environment variables set by the StreamBase Command Prompt.

Allow Connection If Your Firewall Prompts

When you run a Streaming application in StreamBase Studio (for example, by launching one of the demos in the SB Demos perspective), StreamBase Studio makes a local network connection to a Streaming Server instance. When this connection is first attempted, your firewall or Internet security software may issue a warning message. Always select the Allow or Unblock option that allows Streaming to make the connection.

In StreamBase Studio, the connection cannot proceed until you allow the firewall or Internet security software to let Streaming make the connection.

The message may refer to Streaming Server, or sbstudio.exe (StreamBase Studio), or javaw.exe (Java). You may see separate messages for internal programs epadmin.exe, swcoord.exe, and DTMengine.exe. In all cases, allow StreamBase Studio to make the connection. Streaming is not performing an outgoing connection of any kind.

You may see similar messages if you select options on the StreamBase Studio Welcome page that access an external website.

Using Cygwin or Other Alternate Shells

You are welcome to use a third-party command-line environment such as the Linux-like environment provided by Cygwin, as long as you are comfortable configuring that environment. Streaming formally supports using Streaming command and the mvn command using the StreamBase Command Prompt.

The primary caution about using Cygwin, MSys, or the Windows 10 Ubuntu subsystem is to make sure the subsystem has the same sense of home directory as the StreamBase Command Prompt or as Windows command prompts in general.

StreamBase Studio's embedded Maven subsystem writes to a critically important local repository stored by default in your Windows home directory, in a folder named .m2. If your Linux-like subsystem has a different meaning for your home directory, then it might try to create and use a different and competing .m2 directory in a different location.

You can set environment variables to reconcile the meaning of HOME in the various systems. As an alternative, you can set up custom settings.xml files for your different Maven installations to make sure they use the same local repository directory. See the online Maven documentation for further details.