Striim 3.9.8 documentation

Creating a cluster in Microsoft Windows
  1. Download Striim_3.9.8.zip, extract it, and move the extracted striim directory to an appropriate location.

  2. Start Windows PowerShell as administrator (right-click the Windows Powershell icon and select Run as administrator), change to the striim/conf/windowsService directory, and enter .\setupWindowsService.ps1.

  3. Run striim\bin\sksConfig.bat and enter passwords for the Striim keystore and the admin and sys users. If hosting the metadata repository on Oracle or PostgreSQL, enter that password as well (see 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: , . _ + : @ % / -

  4. If hosting the metadata repository on Derby, change its password as described in Changing the Derby password.

  5. Edit 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)

    • CompanyName: If you specify keys, this must exactly match the associated company name. If you are using a trial license, any name will work.

    • 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>
      DERBY_PORT=<port>
    • If hosting the metadata repository on Oracle, set the following properties:

      MetadataDb=oracle
      MetaDataRepositoryLocation=<connection URL>
      MetaDataRepositoryDBname=striimrepo
      MetaDataRepositoryUname=striimrepo

      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. 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= 192.0.2.100)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=racdb.localdomain)))(DESCRIPTION= (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= 192.0.2.101)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=racdb.localdomain)))) (see Features Specific to JDBC Thin for more information.)

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

      MetadataDb=postgres
      MetaDataRepositoryLocation=<connection URL>
      MetaDataRepositoryDBname=striimrepo
      MetaDataRepositoryUname=striim

      The PostgreSQL connection URL has the format <IP address>:<port>/striimrepo, for example 192.0.2.100:5432/striimrepo. In a high availability environment, specify the IP addresses of both the primary and standby servers, separated by a comma, for example, 192.0.2.100,192.0.2.101:5432/striimrepo.

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

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

To uninstall the services, stop them, open a command prompt as administrator (the sc delete commands do not work in PowerShell), change to the striim\conf\windowsService\yajsw\bat\ directory, and enter the following commands:

uninstallService
sc delete Derby
sc delete com.webaction.runtime.Server