v5.5.1.6

Date of Release: August 2024

Enhancement

$inline[badge,NOTE,primary] The "*" symbol next to ID refers to the issues that have been resolved in the current release.

Resolved Issues

$inline[badge,NOTE,primary] The "*" symbol next to ID refers to the issues that have been resolved in the current release.

Upgrade

Assuming IW_HOME variable is set to /opt/infoworks

Prerequisite

To support rollback after metadata migration, you need to take backup of metadata. Following are the steps:

Step 1: Install/Download MongoDB tool: mongodump. (if needed).

Step 2: Create a directory to store the database backup dump using the below command.

Step 3: Use the below command to take a dump (backup) of the databases from the mongodb server.

If MongoDB is hosted on Atlas

If MongoDB is installed with Infoworks on the same VM

Procedure

For upgrading from 5.5.1/5.5.1.x to 5.5.1.6, execute the following commands:

Step 1: Use the deployer to upgrade from 5.5.1 to 5.5.1.6.

Step 2: Go to $IW_HOME/scripts folder of the machine.

Step 3: To ensure that there is no pre-existing update script, execute the following command:

Step 4: Download the update_5.5.1.6.sh

wget https://iw-saas-setup.s3.us-west-2.amazonaws.com/5.5/update_5.5.1.6.sh

Step 5: Give update.sh executable permission

chmod +x update_5.5.1.6.sh

Step 6 (Optional): If the patch requires Mongo Metadata to be migrated, run export METADB_MIGRATION=Y. This ensures that the metadata will be migrated, else run export METADB_MIGRATION=N.

Alternatively, you can enter it in the prompt while running the script.

Step 7: Update the package to the hotfix

You will receive a "Please select whether metadb migration needs to be done([Y]/N)" message. If you need to perform metadb migration, enter Y, else, enter N.

Step 8: (Applicable only for EMR Persistent Clusters)

After successfully upgrading the environment, it is required to restart the Job Submission Driver running on the EMR cluster. This step ensures that the jobs utilize the updated JAR files.

Rollback

Prerequisite

To rollback the migrated metadata:

Step 1: Install/Download MongoDB tool: mongorestore. (if needed)

Step 2: Switch to the directory where the backup is saved on the local system.

Step 3: Use the below command to restore the dump (backup) of the databases to the Mongodb Server.

If MongoDB is hosted on Atlas

If MongoDB is installed with Infoworks on the same VM

Procedure

To go back to previous checkpoint version:

Step 1: In a web browser, go to your Infoworks system, scroll-down to the bottom, and click the Infoworks icon.

Step 2: The Infoworks Manifest Information page opens in a new tab. Scroll down and check the Last Checkpoint Version.

Step 3: ssh to Infoworks VM and switch to {{IW_USER}}.

Step 4: Initialise the variables in the bash shell.

Step 5: Download the required deployer for the current applied patch.

https://iw-saas-setup.s3-us-west-2.amazonaws.com/${major_version}/deploy_${full_version}.tar.gz

Step 6: Execute the SCP command for the above mentioned files to the following path.

$inline[badge,NOTE,primary] Remove the previously downloaded copy of deploy_${full_version}.tar.gz file in ${IW_HOME}/scripts/ directory.

${IW_HOME}/scripts/.

Step 7: Extract the deployed tar file in case it does not exist.

Step 8: Initialise the environment variables.

Step 9: Run the Rollback command.