Striim 3.9.7 documentation

Creating a cluster in CentOS

Follow these instructions to set up the first server in a Striim cluster. Installation will create the system account striim and all files installed will be owned by that account.

  1. If you will host the metadata repository in Oracle or PostgreSQL, follow the instructions in Configuring a DBMS to host Striim's metadata repository.

  2. Download striim-node-3.9.7-Linux.rpm.

    If you plan to host the metadata repository on the internal Derby instance, download striim-dbms-3.9.7-Linux.rpm.

    Optionally, download the sample applications, striim-samples-3.9.7-Linux.rpm.

  3. Install the node package:

    sudo rpm -ivh striim-node-3.9.7-Linux.rpm

  4. If using Derby to host the metadata repository, install its package:

    sudo rpm -ivh striim-dbms-3.9.7-Linux.rpm

  5. Optionally, install the sample application package:

    sudo rpm -ivh striim-samples-3.9.7-Linux.rpm

  6. Use  striim/bin/ <plaintext password> 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: , . _ + : @ % / -

  7. 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 Derby and Derby is not running on port 1527, set the following properties:

      MetaDataRepositoryLocation=<IP address>:<port>
    • 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:@ In a high availability active-standby or RAC environment, specify all servers, for example, MetaDataRepositoryLocation=jdbc:oracle:thin:@(DESCRIPTION_LIST=(LOAD_BALANCE=off)(FAILOVER=on)(DESCRIPTION= (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= (see Features Specific to JDBC Thin for more information.)

      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 In a high availability environment, specify the IP addresses of both the primary and standby servers, separated by a comma, for example,,

  8. Optionally, perform additional tasks described in Configuring Striim, such as Changing the Derby password and increasing the maximum amount of memory the server can use.

  9. Reboot the system and verify that Striim has restarted automatically.


    • For CentOS 6, enter sudo start striim-dbms, wait ten seconds, then enter sudo start striim-node.

    • For CentOS 7, enter:

      sudo systemctl enable striim-dbms
      sudo systemctl start striim-dbms 

      Wait ten seconds, then enter:

      sudo systemctl enable striim-node
      sudo systemctl start striim-node

    Then tail -F /opt/striim/logs/striim-node.log and wait for the message Please go to ... to administer, or use console.

To uninstall:

sudo rpm -e striim-node
sudo rpm -e striim-dbms
sudo rpm -e striim-samples