Striim 3.9.4 / 3.9.5 documentation

Running Striim in Microsoft Windows

See System requirements.

To install Striim for evaluation purposes, see Evaluating on Microsoft Windows.

To run Striim as a process, see Running Striim as a process.

To run Striim as a service:

This requires Windows Server 2008 or later and Windows PowerShell 5.0 or later.

  1. If you have already installed Striim for evaluation purposes using one of the methods above, stop Striim (see Starting and stopping Striim) and skip to step 2.

    Otherwise, download Striim_3.9.4.tgz, then extract it and the .tar file it contains. 7‑Zip is a popular free open-source tool for extracting .tgz and .tar archives.

  2. Start Windows PowerShell as administrator and run the script conf\windowsService\setupWindowsService.ps1. Note that if you are in the windowsService directory, to run the script you must include the path: .\setupWindowsService.ps1.

    If you are installing in a multi-server cluster and this is not the server that will run Derby, or you are hosting the metadata repository on Oracle or PostgreSQL, use setupWindowsService.ps1 -noDerby.

  3. Edit /opt/striim/conf/startUp.properties, edit the following property values (removing any # characters and spaces from the beginning of the lines), and save the file:

    • WAClusterName: a name for the Striim cluster (note that if an existing Striim cluster on the network has this name, Striim will try to join it)

    • WAClusterPassword: the encrypted password for the cluster, which will be used by other servers to connect to the cluster and for other cluster-level operations

    • WAAdminPassword: the encrypted password for Striim's default admin user account

    • CompanyName: If you specify keys, this must exactly match the associated company name.

    • ProductKey and LIcenseKey: If you have keys, specify them, otherwise leave blank to run Striim on a trial license. Note that you cannot create a multi-server cluster using a trial license.

    • Interfaces: If the system has more than one IP address, specify the one you want Striim to use, otherwise leave blank and Striim will set this automatically.

    • If hosting the metadata repository on Oracle, set the following properties:

      MetadataDb=oracle
      MetaDataRepositoryLocation=<connection URL>
      MetaDataRepositoryDBname=striimrepo
      MetaDataRepositoryUname=striimrepo
      MetaDataRepositoryPass=<encrypted password for Oracle user>

      If you use an SID, the connection URL has the format jdbc:oracle:thin:@<IP address>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>/<service name>, for example, jdbc:oracle:thin:@192.0.2.0/orcl.

      If hosting the metadata repository on PostgreSQL, set the following properties:

      MetadataDb=postgres
      MetaDataRepositoryLocation=<connection URL>
      MetaDataRepositoryDBname=striimrepo
      MetaDataRepositoryUname=striim
      MetaDataRepositoryPass=<encrypted password for PostgreSQL user>

      The PostgreSQL connection URL has the format <IP address>:<port>/striimrepo, for example 192.0.2.100:5432/striimrepo.

  4. Optionally, perform additional tasks described in Configuring Striim, such as increasing the maximum amount of memory the server can use.

  5. Start the Derby and Striim services manually, or reboot to verify that they start automatically.

To uninstall the services, stop them, then run these two batch files:

Striim/conf/windowsService/yajsw_server/bat/uninstallService.bat
Striim/conf/windowsService/yajsw_derby/bat/uninstallService.bat