Contents
- Before You Install
- Back Up Existing Streaming Workspace
- Maintaining Multiple Streaming Releases
- Uninstalling a Previous Release of Streaming
- Installation Procedure
- 64-Bit Windows Considerations
- Installing Additional Features
- Using the StreamBase Command Prompt
- Allow Connection If Your Firewall Prompts
- Using Cygwin or Other Alternate Shells
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 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. |
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 SB-workspace-10-03-00.zip
.
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.
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.
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.
To install Streaming on Windows, follow these steps:
-
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.
-
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.1_win_x86_64.msi
. -
Follow the instructions on screen to accept the Streaming license agreement.
-
Accept the default Streaming installation location or browse to a different location. However, NEVER try to overwrite an existing previous Streaming installation.
-
Click
to begin the installation process. -
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.
-
Click the
button.
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.
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.
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.
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.
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.