Skip to main content

Striim Platform 5.0 documentation

In-place upgrade

An in-place upgrade installs the new version of Striim while keeping the current repository database. You may do an in-place upgrade to Striim 5.x from version 4.1.0 or later. As part of this Striim upgrade you will upgrade to Java 11.

Important

Before following the instructions below, read the Release notes so you will be aware of any changes that may be required to your environment or applications before or after the upgrade.Release notes

Note

If any applications use OJet, you must install Oracle Instant Client 21.6. If OJet is running on the Striim server, see Install the Oracle Instant Client in a Striim server. If OJet is running on a Forwarding Agent, see Install the Oracle Instant Client in a Forwarding Agent.

  1. Back up the cluster as described in Backing up and restoring a cluster.

  2. Quiesce and undeploy all running applications with persisted streams. If upgrading from Striim 3.x, quiesce and undeploy all running applications with Spanner Writer targets. Stop and undeploy all other running and deployed applications.

  3. Stop all Forwarding Agents.

  4. Upgrade to Java 11 as described in Upgrading to JDK 11.

  5. Upgrade all servers.

    On each server in the cluster, move the Striim configuration file to /opt/striim/conf-backup (or, if you prefer, some other directory) so it will not be removed when you uninstall the old version of Striim:

    sudo mkdir /opt/striim/conf/conf-backup
sudo mv /opt/striim/conf/startUp.properties /opt/striim/conf/conf-backup/

    for Centos: on each server in the cluster, download striim-node-5.0.6-Linux.rpm and enter the following commands:

    sudo systemctl stop striim-node
sudo rpm -e striim-node
sudo rpm -ivh striim-node-5.0.6-Linux.rpm 

    for Ubuntu: on each server in the cluster, download striim-node-5.0.6-Linux.deb and enter the following commands (on Ubuntu 14.04, omit systemctl):

    sudo systemctl stop striim-node
sudo dpkg --remove striim-node
sudo dpkg -i striim-node-5.0.6-Linux. 

  6. On each server in the cluster, enter the following command to restore your Striim configuration (adjust as necessary if you backed up your files to a different location):

    sudo cp /opt/striim/conf/conf-backup/startUp.properties /opt/striim/conf/

  7. Update your metadata repository. On one server, run the following commands:

    sudo chmod +x /opt/striim/bin/upgrade.sh
sudo /opt/striim/bin/upgrade.sh -a forward

  8. If you are upgrading from 4.3.x or earlier and have configured the web UI to use HTTPS, follow the instructions in Upgrading your HTTPS configuration for Striim 5.x.

  9. Start all servers.

    sudo systemctl start striim-node

  10. Reload any open processors (see Loading and unloading open processors).

  11. Upgrade and start all Forwarding Agents (see Upgrading Forwarding Agents).

  12. If the contents of striim/elasticsearch/data have been lost, restore them from the backup you made in step 1.

  13. If the contents of striim/UploadedFiles have been lost, restore them from the backup you made in step 1.

In this section: