Running Striim in Azure
Striim currently offers the following Azure Marketplace solutions:
StreamShift by Striim: see the StreamShift for Azure documentation
Striim: the full Striim platform on a pay-as-you-go model with an initial free trial
Striim BYOL: the full Striim platform, requires license from Striim, you will be billed by Azure for virtual machine usage
Striim Cloud Enterprise: see the Striim Cloud documentation
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
Striim ROAR Real-Time Offloading Analytics & Reporting for Azure PostgreSQL: licensed for all sources and PostgreSQL targets
Striim VM Subscription: the full Striim platform with an annual license and Gold support
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:
Go to the Azure Marketplace and search for Striim.
Click the solution you want.
Click Get It Now > Continue > Create.
Enter the resource group name, VM user name, and VM user password (make note of the user name and password as you will need them to access the Striim server via ssh). If you select one of your existing resource groups, you will need to open the ports required by Striim (see System requirements).
Optionally, change the location, then click Next: Striim Cluster Settings.
If you want to create multiple Striim servers, change Standalone to Cluster, set the number of servers, and optionally choose a larger VM.
Enter the Striim cluster name (required to connect the Forwarding Agent) and password, then click Next: Striim Access Settings.
Enter the first part of the domain name for your Striim instance and the admin password (make note of the password as you will need it to log into Striim).
Optionally, select your own VNET, then click Next: Review + create.
Click Create. Deployment may take several minutes.
When deployment is complete, click Go to resource group.
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 in Striim Platform.
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.
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>
When prompted, enter the VM password.
Enter the following command to log into the Striim VM:
ssh <VM user name>@<DNS name>
When prompted, enter the VM password.
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. 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:
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