Upgrading Infoworks from 5.0 to 5.5.0 for VM
To upgrade to 5.5.0, you need a newly generated license that enables the supported environments on the installation. For more information, contact support@infoworks.io.
Assuming IW_HOME=/opt/infoworks, use the command: export IW_HOME=/opt/infoworks.
Assuming IW_USER=infoworks, use the command: export IW_USER=infoworks.
Prerequisites
Ensure that all files in ${IW_HOME} are owned by the Infoworks user.
Ensure that all the services are up and running in ${IW_HOME}/bin/status.sh.
Ensure that you have the new license key to use the version of Infoworks to be upgraded to. If you do not have it, you may contact support@infoworks.io to receive the same.
Make sure openssl11-libs is installed on the VM
- sudo yum install openssl11-libs
Before proceeding with upgrade, please ensure to take a back-up of
${IW_HOME}/conf/emr_defaults.json.
Upgrade Procedure
Back Up Infoworks
You must take a backup of ${IW_HOME} before starting the upgrade process.
To back up Infoworks services, perform the following steps:
Step 1: Stop Infoworks service by executing the following command via IW_USER:
xxxxxxxxxx${IW_HOME}/bin/stop.sh all mongoStep 2: Switch to root user.
xxxxxxxxxxsudo su -Step 3: Take a backup of the Infoworks by executing the following command:
xxxxxxxxxxcp -r ${IW_HOME}/../infoworks ${IW_HOME}/../infoworks.bkpStep 4: Switch back to IW_USER.
xxxxxxxxxxsudo su - ${IW_USER}Step 5: Start Infoworks service by executing the following command:
xxxxxxxxxx${IW_HOME}/bin/start.sh mongo allBefore you upgrade, it is recommended to take a backup of Mongo Atlas Infoworks DBs, if any.
Step 1: Install/Download MongoDB tool, if needed.
Step 2: Create a directory to store the database backup dump using the below command
xxxxxxxxxxmkdir -p $IW_HOME/mongo_bkpcd $IW_HOME/mongo_bkpStep 3: Use the below command to take a dump (backup) of the databases from the MongoDB server.
If MongoDB is hosted on Atlas
xxxxxxxxxxmongodump "mongodb+srv://<username>:<password>@<mongodb_server_hostname>/<db_name>"If MongoDB is installed with Infoworks on the same VM
xxxxxxxxxxmongodump "mongodb://infoworks:IN11**rk@localhost:27017/infoworks-new"Internet-based Upgrade
${IW_HOME} with the location where your Infoworks instance is installed. For example, /opt/infoworks.
Before you upgrade, it is recommended to take a backup of Mongo Atlas Infoworks DBs, if any.
Perform the following steps for internet-based upgrade:
Step 1: Download the upgrade script using the following commands:
xxxxxxxxxxcd ${IW_HOME}/scriptswget https://iw-saas-setup.s3-us-west-2.amazonaws.com/5.5/update.sh --no-check-certificateStep 2: Provide execute permission to the script using the following command.
xxxxxxxxxxchmod +x update.shStep 3: Execute the following script to source the env.sh file. This sources the Infoworks environment variables, such as path variables.
xxxxxxxxxxsource ${IW_HOME}/bin/env.shStep 4: Export the following environment variables:
| Field | Description | Details |
|---|---|---|
| METADB_MANAGED | This flag indicates whether the Mongo Installation is managed by Infoworks | Enter Y (default) for Infoworks Managed, or N for an external mongo. export METADB_MANAGED= |
| METADB_USE_SRV | This flag indicates whether the MONGO_HOST corresponds to a DNS SRV record | Enter N(default) for No (prefix “mongodb://”), or Y for Yes (prefix “mongodb+srv://”) export METADB_USE_SRV= |
For Non-managed Mongo (only):
| Field | Description | Details |
|---|---|---|
| METADB_FORCE_DROP | This flag indicates whether the Installer should overwrite any existing Databases. | Enter N (default) for No (the provided databases must be empty), or Y to allow the dropping of databases. export METADB_FORCE_DROP=N |
| MONGO_HOST | This flag indicates the Mongo host URL to connect to | Enter the Mongo Server or Seed DNS hostname (without prefix) export MONGO_HOST= |
| MONGO_USER | The Mongo user that is used to authenticate into Infoworks DBs | Enter a user that has at least read/write permissions over the databases mentioned. (defaults to Infoworks). export MONGO_USER= |
| MONGO_PASS | The Password of the aforementioned MONGO_USER | Enter the Password of the MONGO_USER (defaults to Infoworks Mongo Password) export MONGO_PASS= |
| MONGO_DB | The Database Name that will store Infoworks MetaData. | Enter a valid database name. export MONGO_DB= |
| MONGO_QUARTZDB | The Database Name that will store Quartzio MetaData. | Enter a valid database name. export MONGO_QUARTZDB= |
Step 5: Execute the following script:
xxxxxxxxxx./update.sh -v {{version}}For example, to upgrade to version 5.5.0, use the following script:
For Amazon Linux 2, perform the following command:
xxxxxxxxxx./update.sh -v 5.5.0-amazonlinux2Step 6: Upgrade the license after logging into the UI.
As a part of the upgrade/install for a non-managed mongo setup, the following MongoDB artifacts are deleted from the local machine:
- Binaries
- Data
- Configurations
As a part of the upgrade, MongoDB dumps are taken on the local machine at iw_home/temp/backup-5.0.0/mongo__. After upgradation, it is recommended to test the migration to MongoDB Atlas thoroughly by running Infoworks Ingestion and Pipeline Jobs. These dumps can be deleted after the tests are complete. __
As a part of the upgrade, Postgres backup is taken on the local machine at iw_home/resources/postgres/pgsql.old__. After upgrading, it is recommended to test the migration to Postgres thoroughly by running Infoworks Workflow Jobs. These dumps can be deleted after the tests are complete.
You must perform the following steps after upgrading to 5.5.0:
Step 1: Ensure that you download the Teradata JDBC driver from the Teradata portal.
Step 2: Extract the compressed file (.zip or .tar), and copy the drivers namely, tdgssconfig.jar, terajdbc4.jar from the extracted file.
Step 3: Create lib/dist-jobs directory under the $IW_HOME/lib/ingestion/connectors/teradata folder, so that the directory structure becomes $IW_HOME/lib/ingestion/connectors/teradata/lib/dist-jobs, and place the downloaded drivers inside it.