Skip to main content

Importing the metadata and completing the upgrade

  1. Complete the steps in Upgrading in CentOS or Upgrading in Ubuntu.

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

  3. If the metadata repository is hosted on Derby, skip this step.

    If the metadata repository is hosted on Oracle, log in to sqlplus as the user created in Configuring Oracle to host the metadata repository and run the /opt/striim/conf/DefineMetadataReposOracle.sql and DefineMeteringReposOracle.sql scripts to create new repository tables.

    If the metadata repository is hosted on PostgreSQL, log in to psql as the user created in Configuring PostgreSQL to host the metadata repository and run the /opt/striim/conf/DefineMetadataReposPostgres.sql and DefineMeteringReposPostgres.sql scripts to create new repository tables.

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

    cp /opt/striim/conf-backup/startUp.properties /opt/striim/conf
cp /opt/striim/conf-backup/sks.jks /opt/striim/conf
cp /opt/striim/conf-backup/sksKey.pws /opt/striim/conf
sudo chown striim /opt/striim/conf/sks.jks
sudo chown striim /opt/striim/conf/sksKey.pwd

  5. Import the metadata. On the server where you exported the metadata when Preparing to upgrade and exporting the metadata, enter the following commands:

    If the metadata repository is hosted on Derby:

    cd /opt/striim
sudo bin/tools.sh -A import -F export.json -f <old version>

    For example, if upgrading from 4.2.0:

    sudo bin/tools.sh -A import -F export.json -f 4.2.0

    If the metadata repository is hosted on Oracle:

    cd /opt/striim
sudo bin/tools.sh -A import -F export.json -f <old version> -r oracle

    If the metadata repository is hosted on PostgreSQL:

    cd /opt/striim
sudo bin/tools.sh -A import -F export.json -f <old version> -r postgres

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

  7. Reboot that system to verify that Striim restarts automatically.

    Alternatively, to start without rebooting:

    For CentOS 6.x or Ubuntu 14.04, enter the following commands:

    • If the metadata repository is hosted on Derby, on the Derby host only: sudo start striim-dbms

    • Wait ten seconds, then enter:

      sudo start striim-node 
sudo tail -F /opt/striim/logs/striim-node.log 

    For CentOS 7.x or Ubuntu 16.04 or later, enter the following commands:

    • If the metadata repository is hosted on Derby, on the derby host only:

      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 
sudo tail -F /opt/striim/logs/striim-node.log 

    When you see the message Please go to ... to administer, or use console, Striim is running.

  8. Log in to verify that Striim is running, then reboot the other servers in the cluster, or start each server manually using the commands above.

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

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

  11. If the contents of striim/elasticsearch/data have been lost, restore them from the backup you made in step 1 of Preparing to upgrade and exporting the metadata.

  12. If the contents of striim/UploadedFiles have been lost, restore them from the backup you made in step 1 of Preparing to upgrade and exporting the metadata.