Striim 3.9.4 / 3.9.5 documentation

Running Striim as a process

For development and testing, it can be useful to run Striim as a process, so you can easily restart with different options or switch between various releases.

If you do not need to run Striim as a service, you can install simply by extracting a Striim-<version>.tgz or .zip archive. For example, to extract to the /opt directory (the typical location, though you may install wherever you like):

tar zxvf Striim-<version>.tgz -C /opt

Once you have extracted the package, set the server properties:

  1. Use striim\bin\passwordEncryptor.bat <plaintext password> (for Windows) or striim/bin/ <plaintext password> (for OS X or Linux) to encrypt the passwords for the Striim cluster and admin user. You may use the same password for both. If hosting the metadata repository on Oracle or PostgreSQL, also encrypt the password for the database user created as described in Configuring a DBMS to host Striim's metadata repository. If you are using a Bash or Bourne shell, characters other than letters, numbers, and the following punctuation marks must be escaped: , . _ + : @ % / -

  2. Edit /opt/striim/conf/, 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:

      MetaDataRepositoryLocation=<connection URL>
      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:@ If you use a service name, it has the format jdbc:oracle:thin:@<IP address>/<service name>, for example, jdbc:oracle:thin:@

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

      MetaDataRepositoryLocation=<connection URL>
      MetaDataRepositoryPass=<encrypted password for PostgreSQL user>

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

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

  4. Save the file.

Once you have specified the necessary server properties, start the server with striim\bin\server.bat (for Windows) or striim/bin/ (for OS X or Linux).

When the server has started, you will see a message indicating the URL where you can access its web UI.

When running as a process, SysOut output will be written to the terminal running the server process rather than to striim-node.log.

To start the console, enter striim\bin\console.bat -c <cluster name> (for Windows) striim/bin/ -c <cluster name> (for OS X or Linux).

To stop the server, press Ctrl-C in the terminal window.

To restart, run server.bat or Optionally you may specify a startup properties file as an argument, which can save time if you need to run Striim with various settings for testing or development purposes.


If installing a new release of Striim, delete the striim directory and empty the trash before extracting the new .tgz or .zip archive, and clear your browser cache before logging in to the web UI.