Striim

Welcome to the Striim Help Center and Community Site

3.10.1 Installing Striim

Follow

This section describes how to install Striim in various environments for various purposes.

Configuring a DBMS to host Striim's metadata repository

You may host Striim's metadata repository on Derby, Oracle, or PostgreSQL. By default, Striim uses the integrated, preconfigured Derby instance. To use Oracle or PostgreSQL instead, follow the instructions in this section.

Caution

When using the integrated Derby instance in a production environment, we strongly recommend Changing the Derby password.

See also Changing metadata repository connection retry settings.

Caution

When Striim is processing very large amounts of data at high velocity, Derby may fail to reclaim the unused space in the metadata repository, resulting in it eventually filling all available disk space and crashing. In this situation, Striim will crash and restart will fail. To work around this issue, we recommend hosting the metadata repository on Oracle or PostgreSQL instead.

As a short-term workaround for Derby, use the following command to compress the metadata repository tables:

striim/bin/derbyTools.sh -A compressDb

This uses a lot of Derby resources, so it should be performed when Striim is not busy.

Configuring Oracle to host the metadata repository
  1. Copy the SQL script /opt/striim/conf/DefineMetadataReposOracle.sql to the Oracle host.

  2. Using sqlplus, log in to Oracle as an administrator and create the user Striim will use to create, write to, and read from the repository tables (replace ****** with a strong password):

    create user striimrepo identified by ******;
    grant connect, resource to striimrepo;
  3. Log out of sqlplus, log in again as the user you just created, and run the DefineMetadataReposOracle.sql script.

Configuring PostgreSQL to host the metadata repository
  1. Copy the SQL script /opt/striim/conf/DefineMetadataReposPostgres.sql to the PostgreSQL host.

  2. Using psql, connect to PostgreSQL as an administrator and create the user Striim will use to create, write to, and read from the repository tables (replace ****** with a strong password):

    sudo -u postgres psql
    create user striim with password '******';
    create database striimrepo;
    grant all on database striimrepo to striim;
    \q
    
  3. Connect again as the user you just created, create a schema, set the search path, and run the DefineMetadataReposPostgres.sql script:

    psql -U striim -d striimrepo;
    create schema striim;
    alter role striim set search_path to striim;
    \q
    psql -U striim -d striimrepo -f DefineMetadataReposPostgres.sql
    
Moving the metadata repository to Oracle or PostgreSQL

To move the metadata repository from the Striim internal Derby instance to Oracle or PostgreSQL, do the following. This will require bringing down the Striim cluster, so you should schedule it for a maintenance window.

  1. Follow the instructions in Configuring Oracle to host the metadata repository or Configuring PostgreSQL to host the metadata repository.

  2. Stop the Derby instance (striim-dbms) and all servers in the Striim cluster (see Starting and stopping Striim).

  3. On the server running Derby, export the metadata:

    cd /opt/striim
    sudo bin/tools.sh -A export -F export.json
    
  4. Follow the instructions in Configuring Oracle to host the metadata repository or Configuring PostgreSQL to host the metadata repository.

  5. Make a backup copy of startUp.properties:

    cd /opt/striim/conf
    cp startUp.properties *.bak
  6. On each server in the cluster, update startUp.properties to reflect the new repository host:

    For Oracle:

    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>:<port>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:1521:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>:<port>/<service name>, for example, jdbc:oracle:thin:@192.0.2.01521:/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.)

    For PostgreSQL:

    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.

  7. On each server in the cluster, update the metadata repository user's password in the Striim keystore:

    cd /opt/striim
    sudo su - striim bin/sksConfig.sh -p
  8. On the server where you exported the metadata, import it.

    For Oracle:

    cd /opt/striim
    sudo bin/tools.sh -A import -F export.json -f 3.10.1 -r oracle
    

    For PostgreSQL:

    cd /opt/striim
    sudo bin/tools.sh -A import -F export.json -f 3.10.1 -r postgres
    
  9. Stop Derby from starting automatically.

    sudo systemctl disable striim-dbms

    If you are Running Striim as a process, set NO_DERBY=true as an environment variable before running server.sh.

  10. Restart the Striim cluster (see Starting and stopping Striim).

Running Striim in Amazon EC2

The fastest and easiest way to run Striim in Amazon EC2 is to get it from the AWS Marketplace (see Deploying Striim from the AWS Marketplace). If you prefer to run Striim in your own EC2 VM, contact Striim support for assistance.

Striim currently offers the following AWS EC2 solutions:

  • Striim - BYOL Platform: the full Striim platform using a free trial license or a license purchased from Striim (BYOL = "bring your own license")

  • Striim for Amazon Web Services - Metered Platform: the full Striim platform with an initial free trial

  • Striim for Amazon Redshift: licensed for MySQL, Oracle, SQL Server sources and RedshiftWriter and FileWriter targets. (FileWriter can be useful for debugging and testing.)

With the BYOL solution, you will be billed monthly by Amazon for virtual machine usage and purchase your license directly from Striim. After the trial period, you must Contact Striim support to purchase a license.

With the other solutions, you will be billed by Amazon monthly according to usage. See the individual solutions for pricing details.

Deploying Striim from the AWS Marketplace

To deploy a Striim AWS Marketplace solution:

  1. Go to the appropriate page in the AWS Marketplace.

  2. Click Continue to Subscribe > Continue to Configuration.

  3. Select the desired region, then click Continue to Launch.

  4. Optionally, change the EC2 Instance Type.

  5. Under Security Group Settings, click Create New Based on Seller Settings, enter a name and description, and click Save.

  6. Under Key Pair Settings, select the key pair to use with Striim.

    If you do not have a key pair in the selected region, click Create a key pair in EC2, change the region to the one you selected previously, click Create Key Pair, enter a name, click Create, save the .pem file, and return to the Launch page, and refresh the key pair list. If the new key pair is not selected automatically, select it.

  7. Click Launch.

  8. Click EC2 Console.

    EC2_Console_link.png
  9. Make note of the Instance ID, then in the left-side menu click Elastic IPs.

  10. Click Allocate new address. If you see a choice of options, select VPC. Then click Allocate > Close. Make note of the IP address as you will use it to access Striim.

  11. Select Actions > Associate address, select the EC2 instance ID, select its private IP, and click Associate > Close.

  12. In the left-side menu, click Instances.

  13. If you have more than one instance, select the one you just created. Copy its Public DNS (IPv4) string (at the top if the right column on the Description tab at the bottom of the page).

    public_IP_string.png
  14. Paste the public DNS string in your browser's address bar, add :9070 (for example, ec2-3-91-177-185.compute-1.amazonaws.com:9070), and press Enter. You should see this message:

    congratulations.png
  15. Click OK to allow cookies, then click Accept Striim EULA and Continue to accept the license agreement.

  16. For Striim BYOL only, enter your name, email, company name, and email address. If you already have a license, be sure that the company name exactly matches the name associated with your license.

  17. Enter a name for the Striim cluster and sys, admin, and keystore passwords. Be sure to remember the cluster name and passwords, since you will need them to log in to Striim and run the Striim console or Forwarding Agent.

  18. Click Save and Continue.

  19. For the BYOL Platform only, provide a license key if you have one. Otherwise, leave the license key field blank to proceed with a trial license, then click Continue.

  20. Click Launch.

  21. When launch has completed, click Log In. (You can return to the login page using the View Instances > Access Software link on the Your Software page.)

  22. Log in as admin with the admin password you provided above.

If you are new to Striim, see Getting started with Striim.

Installing Striim from an Amazon EC2 AMI

To create a multi-server Striim cluster in EC2, you must install it from an AMI. Contact Striim support for assistance.

Using ssh to run the Striim console in EC2

To access the Striim instance's command line, use ssh. On Windows, you can get ssh by installing the Windows Subsystem for Linux or, if your Windows version does not support that, you can install Cygwin or the third-party utilities WinSCP and Putty, or use the AWS Command Line Interface (AWS CLI).

The syntax is:

ssh -i <private key file name> centos@<Public DNS string>
  • The private key file is the .pem file specified in the "Select an existing key pair or create a key pair" step above. Before using ssh, you must run this command on the private key file once: chmod 400 <private key file name>

  • centos is the Linux user name used by the Striim server.

  • You can find the Public DNS string for the Striim instance on the AWS Instances page. The format of this string is ec2-<Public IP>.<EC2 region>.compute.amazon.com.

Putting all these together, the command would look something like this (assuming you ran it from the same directory where the .pem file is stored):

ssh -i MyStriimUser.pem centos@ec2-203.0.113.23.us-west-1.compute.amazonaws.com

When ssh connects to the Striim instance, you will see something like this:

TIBCO Silver -  CentOS 6.5 x86_64 AMI
Bootstrap complete. Visit http://silver.tibco.com for more information.
us-west-1b-i-07e1133b674e72aed
[centos:~]$

To run the console, enter:

sudo /opt/Striim/bin/console.sh -c StriimCluster

Running Striim in Azure

Striim currently offers the following Azure Marketplace solutions:

  • Striim: the full Striim platform with an initial free trial

  • Striim for Real-Time Integration to Azure Storage: licensed for all sources and Azure Blob Storage targets

  • Striim for Real-Time Data Integration to Cosmos DB: licensed for all sources and CosmosDBWriter targets

  • Striim for Real-Time Integration to PostgreSQL: licensed for all sources and PostgreSQL targets

  • Striim for Data Integration to SQL Data Warehouse: licensed for all sources and Azure SQL Data Warehouse targets

  • Striim for Real-Time Integration to SQL Database: licensed for all sources and Azure SQL Database targets

You will be billed by Microsoft monthly according to usage. See the individual solutions for pricing details.

Deploying Striim Using an Azure Marketplace Solution

First, create, purchase, and deploy your solution:

  1. Go to the Azure Marketplace and search for Striim.

  2. Click the solution you want.

  3. Click Get It Now.

  4. At the bottom of the page, click Create.

  5. Enter the VM user name, VM user password (make note of the user name and password as you will need them to access the Striim server via ssh), and resource group name. You may use the same name for the VM user, resource group, and Striim cluster name. If you select one of your existing resource groups, you will need to open the ports required by Striim (see System requirements).

  6. Optionally, change the location, then click OK.

  7. If you want to create multiple Striim servers, change Standalone to Cluster, set the number of servers, and optionally choose a larger VM.

  8. Enter the Striim cluster name (required to connect the Forwarding Agent).

  9. Optionally, select your own VNET, then click OK.

  10. Enter the domain name and Striim admin and sys passwords (make note of the admin password as you will need it to log into the Striim web UI), then click OK.

  11. When validation is complete, click OK.

  12. Click Create. Deployment may take several minutes.

  13.  When deployment is complete, click <cluster name>-masternode (the VM hosting the master Striim server) and make note of the the DNS name (<domain name>:<Azure region>.cloudapp.azure.com) as you will need it to perform the remaining steps.

Install JDBC drivers

When deployment is complete, install any JDBC drivers that will be required by your sources and, if you deployed the Azure SQL Database and SQL Data Warehouse solutions, the Microsoft JDBC Driver 4.0 for SQL Server. This requires the Linux utilities scp and ssh. On Windows, you can get scp and ssh by installing the Windows Subsystem for Linux or, if your Windows version does not support that, you can install Cygwin or the third-party utilities WinSCP and Putty, or use Azure Cloud Shell.

The following instructions are for the SQL Server driver but the procedure is the same for the other drivers discussed in Installing third-party drivers.

  1. Download the Microsoft JDBC Driver 7.2 for SQL Server .gz package from https://www.microsoft.com/en-us/download/details.aspx?id=57782 and extract it.

  2. Open a terminal, switch to the directory that was extracted, and enter the following command to copy the driver to Striim:

    scp enu/mssql-jdbc-7.2.2.jre8 <VM user name>@<DNS name>:/home/<VM user name>
  3. When prompted, enter the VM password.

  4. Enter the following command to log into the Striim VM:

    ssh <VM user name>@<DNS name>
    
  5. When prompted, enter the VM password.

  6. Enter the following to install the driver in Striim and restart the Striim server:

    sudo su
    <VM user password>
    cp mssql-jdbc-7.2.2.jre8 /opt/striim/lib
    systemctl stop striim-node
    systemctl start striim-node
    exit
    exit

If you created multiple Striim servers, repeat the above steps on each one. The VM user names and DNS names for the other servers are the same as the master's but with digits, starting with 0, appended to the server name. For example, if the master's name was mycluster, the first additional server's name would be mycluster0 and its DNS name would be mycluster0.westus.cloudapp.azure.com.

Log in to the Striim web UI

Using a compatible Web browser (we recommend Chrome), go to http://<DNS name>:9080, enter admin as the user name, enter the Striim admin password, and click Log In. At this point, if you are new to Striim, see Getting started with Striim. See also  Creating apps using templates.

Accessing Striim in Azure via ssh

Enter the following command to log into the Striim VM:

ssh <VM user name>@<DNS name>
Hosting Striim's metadata repository on Azure Database for PostgreSQL

When running Striim in Azure, you may host the metadata repository on Azure Database for PostgreSQL. Follow the instructions for PostgreSQL in Moving the metadata repository to Oracle or PostgreSQL, except in step 6 specify the values in startUp.properties as follows:

MetadataDb=azurepostgres
MetaDataRepositoryLocation=<server name>:5432/striimrepo
MetaDataRepositoryDBname=striimrepo
MetaDataRepositoryUname=striim@<hostname>

You can find the Server name on the database's Overview page:

AzureDB4PGSQLOverview.png

The hostname is the first element of the server name. So, for example:

MetadataDb=azurepostgres
MetaDataRepositoryLocation=striimtest1.postgres.database.azure.com:5432/striimrepo
MetaDataRepositoryDBname=striimrepo
MetaDataRepositoryUname=striim@striimtest1

Running Striim in CentOS

To create a Striim cluster in CentOS, install the first server as described in Creating a cluster in CentOS. To add additional servers to the cluster, follow the instructions in Adding a server to a cluster in CentOS.

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. Verify that the system meets the System requirements.

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

  3. Download striim-node-3.10.1-Linux.rpm.

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

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

  4. Install the node package:

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

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

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

  6. Optionally, install the sample application package:

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

  7. Run sudo su - striim /opt/striim/bin/sksConfig.sh 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: , . _ + : @ % / -

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

  9. 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)

    • 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>:<port>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:1521:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>:<port>/<service name>, for example, jdbc:oracle:thin:@192.0.2.01521:/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.

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

    • 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 sudo 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
sudo rm -rf /etc/systemd/system/multi-user.target.wants/striim-node.service
Adding a server to a cluster in CentOS

Note

All servers in a cluster must run the same version of Striim. You cannot create a multi-server cluster using a trial license.

The following steps require that you have created the first server in the cluster as described above and that it is running.

  1. Verify that the system meets the System requirements.

  2. Log in to Linux and download striim-node-3.10.1-Linux.rpm.

  3. Install that package:

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

  4. Copy sks.jks, sksKsy.pwd, and startUp.properties from /opt/striim/conf/ on the first server to /opt/striim/conf/ on the new server.

  5. Assign ownership of the keystore files to Striim:

    sudo chown striim sks.jks
    sudo chown striim sksKey.pwd
  6. If you are using the internal Derby instance to host the metadata repository, edit startUp.properties and specify values for the following, replacing ###.###.#.# with the IP address of the server hosting Derby.

    MetaDataRepositoryLocation=###.###.#.#\:1527
    MetaDataRepositoryUname=waction
    MetaDataRepositoryDBname=wactionrepos
    

    Be sure to uncomment those properties (remove from the beginning of the line).

  7. If Interfaces is specified in startUp.properties, change its value to an IP address of the current system.

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

    Alternatively:

    • For CentOS 6, enter sudo start striim-node.

    • For CentOS 7, enter:

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

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

  9. Log in as admin and check the Monitor page to verify that the server has been added to the cluster (see Monitoring using the web UI).

To uninstall:

sudo rpm -e striim-node

Running Striim using Docker

The following instructions assume you have already installed Docker (see https://docs.docker.com/engine/installation/). The Docker evalversion image does not include the sample files.

  1. Enter the following command:

    docker pull striim/evalversion
  2. Once all the pulls are complete, enter:

    docker run -d -p 80:9080 -e "STRIIM_ACCEPT_EULA=Y" striim/evalversion
  3. To verify that the container is running, enter:

    docker ps

    The output should look similar to:

    CONTAINER ID  IMAGE  COMMAND  CREATED 
    a7141958a08b  striim/evalversion "/opt/Striim/sbin/..." 2 minutes ago
     STATUS  PORTS  NAMES
     Up 2 minutes  1527/tcp, 0.0.0.0:80->9080/tcp practical_hoover

    You should now be able to access the web UI at http://localhost:80. Log in as admin with password admin.

To log into the Docker container to configure Striim or run the console, use the following command, replacing <container name> with the container name returned by the docker ps command (in the above example, practical_hoover):

docker exec -it <container name> /bin/bash

To stop Striim enter docker stop <container ID>, using the container ID from the docker ps output. To uninstall, stop Striim, then enter docker rm <container ID>.

Use the evalversion image only for testing and development. To create a production Striim cluster using Docker, contact support@striim.com.

Running Striim in the Google Cloud Platform

Striim currently offers the following Google Cloud Platform solutions:

  • Striim: the full Striim platform using a free trial license or a license purchased from Striim

  • Striim for Real-Time Integration to BigQuery: licensed for all sources and Google BigQuery targets

  • Striim for Real-Time Integration to Cloud Spanner: licensed for all sources and Spanner targets

  • Striim for Real-Time Integration to Cloud SQL for MySQL: licensed for all sources and MySQL targets

  • Striim for Real-Time Integration to Cloud SQL for PostgresSQL: licensed for all sources and PostgreSQL targets

  • Striim for Real-Time Integration to Google Cloud Storage: licensed for all sources and Google Cloud Storage targets

With the full Striim platform solution, you will be billed monthly by Google for virtual machine usage and purchase your license directly from Striim. After the trial period, you must Contact Striim support to purchase a license.

With the other solutions, you will be billed by Google monthly according to usage. See the individual solutions for pricing details.

Deploying Striim in the Google Cloud Platform
  1. If you have not done so already, sign up for the Google Cloud Platform and set up billing.

  2. If you do not already have a Google Cloud Platform project suitable for this deployment, create one (see Creating and Managing Projects).

  3. If you are deploying the BigQuery, Google Cloud Storage, or Spanner solution:

    • Create a service account in the project for use by Striim (see Creating and Managing Service Accounts).

    • Download the service account key, which you will later copy it to the virtual machine running Striim.

    • For BigQuery, give the service account write permission for the relevant tables (see Access Control). For Google Cloud Storage, assign the service account the Storage Legacy Bucket Writer role. For Spanner, give the service account the Cloud Spanner Database User or higher role for the instance (see Cloud Spanner Roles).

  4. Go to the Google Marketplace, search for Striim, click the desired solution, and click Launch on Compute Engine.

    launch_on_compute_engine.png
  5. At the top of the page, select the project to deploy in.

  6. Optionally, change the deployment name, region, and virtual machine settings. (This may affect your cost.)

    deploy.png
  7. Click Deploy. Deployment may take a few minutes.

  8. Click Visit the site.

If you deployed the BigQuery, Google Cloud Storage, MySQL, PostgreSQL, or Spanner solution, log in using the username admin and the password shown on the deployment preview page. If you do not get a login prompt, wait a few more minutes for Striim to complete startup and click Visit the site again. For discussion of the App Wizard page, which is the first thing you will see when you log in, see Creating apps using templates.

If you deployed the full Striim platform (Bring Your Own License) solution, continue with the following steps.

  1. Click Visit the site.

  2. You should see "Congratulations! You have successfully installed Striim." Click Accept Striim EULA and Continue.

  3. Enter your name, email address, company name (which must exactly match the company name associated with your license and product keys), a name for the Striim cluster, and sys, admin, and keystore passwords. Make note of the cluster name and both passwords as they are necessary for various tasks you may need to perform in the future. Click Save and Continue.

  4. Enter the license and product keys you received from Striim or leave the fields blank to use a trial license. Click Save and Continue.

  5. Click Launch.

  6. Click Log In, enter admin and the admin password you specified above, and click Log In.

    login.png
  7. If you are new to Striim, click Next to start the tutorial.

Additional steps required after deployment is complete

If the Google Deployment Manager preview page says you need to open any firewall ports, follow the instructions provided.

If you deployed the BigQuery, Google Cloud Storage, or Spanner solution, before using App Wizard templates or running any applications that write to BigQuery or GCS, copy the service account key .json file you downloaded above to the Striim server VM. Use one of the methods suitable for Linux discussed in Transferring Files to Instances. We recommend putting the file in /striim/conf but you may put it in any location. You will need to specify the fully-qualified file name in the ServiceAccountKey property of BigQueryWriter, GCSWriter, or SpannerWriter.

If you deployed the MySQL or PostgreSQL solution, before using App Wizard templates or running any applications that write to the target databases, copy the appropriate driver to the Striim server VM as described in Installing the MySQL JDBC driver and Installing the PostgreSQL JDBC driver. For step 3, use one of the methods suitable for Linux discussed in Transferring Files to Instances.

Install any JDBC drivers required by your sources (see Installing third-party drivers) using one of the methods suitable for Linux discussed in Transferring Files to Instances.

Recommended next steps

Change the VM's public IP address from Ephemeral to Static or it will change every time you restart the VM. See Promoting an ephemeral external IP address.

For an introduction to Striim, see Getting started with Striim.

Google will suggest changing the admin password. The randomly generated "temporary" password should be quite secure, but if you wish to change it, see Running the console in the Google Cloud Platform, and use the command ALTER USER admin SET ( password:"<new password>" );.

Running the console in the Google Cloud Platform
  1. Go to https://console.cloud.google.com/dm/deployments, select the project you deployed to, and click the name of the deployment. 

  2. Click SSH.

  3. Enter the following:

    sudo su
    /opt/striim/bin/console.sh -c <cluster name>

    If you are using the full Striim platform (Bring Your Own License) solution, you specified the cluster name when configuring Striim. If you are using another solution, the cluster name is Striim. Cluster names are case-sensitive.

Running Striim in Microsoft Windows

See System requirements.

To install Striim for evaluation purposes, see Evaluating on Mac OS X, Linux, or Windows 10.

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

To run Striim as a service:

Install the first server as described in Creating a cluster in Microsoft Windows. To add additional servers to the cluster, follow the instructions in Adding a server to a cluster in Microsoft Windows.

Creating a cluster in Microsoft Windows
  1. Verify that the system meets the System requirements.

  2. Download Striim_3.10.1.zip, extract it, and move the extracted striim directory to an appropriate location.

  3. 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.

  4. 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: , . _ + : @ % / -

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

  6. 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>:<port>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:1521:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>:<port>/<service name>, for example, jdbc:oracle:thin:@192.0.2.01521:/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.

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

  8. 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
Adding a server to a cluster in Microsoft Windows
  1. Verify that the system meets the System requirements.

  2. Download Striim_3.10.1.zip and extract it to the desired location.

  3. 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 -noderby
  4. Copy sks.jks, sksKsy.pwd, and startUp.properties from striim/conf/ from the first server to striim/conf/ on the new server.

  5. If you are using the internal Derby instance to host the metadata repository, edit startUp.properties and specify values for the following, replacing ###.###.#.# with the IP address of the server hosting Derby.

    MetaDataRepositoryLocation=###.###.#.#\:1527
    MetaDataRepositoryUname=waction
    MetaDataRepositoryDBname=wactionrepos
    

    Be sure to uncomment those properties (remove from the beginning of the line).

  6. If Interfaces is specified in startUp.properties, change its value to an IP address of the current system.

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

  8. Start the Striim service manually, or reboot to verify that it starts automatically.

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

uninstallService
sc delete com.webaction.runtime.Server

Running Striim in Snowflake

See Getting your free trial of Striim for Snowflake.

Running Striim in Ubuntu

To create a Striim cluster in Ubuntu, install the first server as described in Creating a cluster in Ubuntu. To add additional servers to the cluster, follow the instructions in Adding a server to a cluster in Ubuntu.

Creating a cluster in Ubuntu

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. Verify that the system meets the System requirements.

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

  3. Download striim-node-3.10.1-Linux.deb,.

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

    Optionally, download the sample applications, striim-samples-3.10.1-Linux.deb.

  4. Install the node package:

    sudo dpkg -i striim-node-3.10.1-Linux.deb

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

    sudo dpkg -i striim-dbms-3.10.1-Linux.deb

  6. Optionally, install the sample application package:

    sudo dpkg -i striim-samples-3.10.1-Linux.deb

  7. Run sudo su - striim /opt/striim/bin/sksConfig.sh 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: , . _ + : @ % / -

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

  9. 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)

    • 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>:<port>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:1521:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>:<port>/<service name>, for example, jdbc:oracle:thin:@192.0.2.01521:/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.

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

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

    Alternatively:

    • For Ubuntu 14.04, enter sudo start striim-dbms , wait ten seconds, then enter sudo start striim-node.

    • For Ubuntu 16.04 or later, 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 sudo tail -F /opt/striim/logs/striim-node.log and wait for the message Please go to ... to administer, or use console.

To uninstall:

sudo dpkg -r striim-node
sudo dpkg -r striim-dbms
sudo dpkg -r striim-samples
Adding a server to a cluster in Ubuntu

Note

All servers in a cluster must run the same version of Striim. You cannot create a multi-server cluster using a trial license.

The following steps require that you have created the first server in the cluster as described above and that it is running.

  1. Verify that the system meets the System requirements.

  2. Log in to Linux and download striim-node-3.10.1-Linux.deb.

  3. Install that package:

    sudo dpkg -i striim-node-3.10.1-Linux.deb

  4. Copy sks.jks, sksKsy.pwd, and startUp.properties from /opt/striim/conf/ on the first server to /opt/striim/conf/ on the new server.

  5. Assign ownership of the keystore files to Striim:

    sudo chown striim sks.jks
    sudo chown striim sksKey.pwd
  6. If you are using the internal Derby instance to host the metadata repository, edit startUp.properties and specify values for the following, replacing ###.###.#.# with the IP address of the server hosting Derby.

    MetaDataRepositoryLocation=###.###.#.#\:1527
    MetaDataRepositoryUname=waction
    MetaDataRepositoryDBname=wactionrepos
    

    Be sure to uncomment those properties (remove from the beginning of the line).

  7. If Interfaces is specified in startUp.properties, change its value to an IP address of the current system.

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

    Alternatively:

    • For Ubuntu 14.04, enter sudo start striim-node.

    • For Ubuntu 16.04 or later, enter:

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

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

  9. Log in as admin and check the Monitor page to verify that the server has been added to the cluster (see Monitoring using the web UI).

To uninstall:

sudo dpkg -r striim-node

Running Striim as a process

Note

Before installing Striim, verify that the system meets the System requirements.

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. We do not recommend running Striim as a process in a production environment. 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. Open a terminal or command prompt and change to the striim directory.

    • In CentOS or Ubuntu, enter sudo su - striim bin/sksConfig.sh

    • In OS X, enter bin/sksConfig.sh

    • In Windows, enter bin\sksConfig

    When prompted, 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: , . _ + : @ % / -

  2. 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)

    • 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>:<port>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:1521:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>:<port>/<service name>, for example, jdbc:oracle:thin:@192.0.2.01521:/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.

  3. If hosting the metadata repository on Derby in a production environment (not recommended), change its password (see Changing the Derby password).

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

  5. Save the file.

Once you have specified the necessary server properties, start the server with striim\bin\server.bat (for Windows) or striim/bin/server.sh (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) or striim/bin/console.sh -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 server.sh. 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.

Note

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.

3.10.1
Was this article helpful?
0 out of 0 found this helpful

Comments