Unity - Manual Update

Owned by Kevin Vogle, created
Last updated: Dec 10, 2024
3 min read

Overview

These are the steps to update Unity manually which is to copy/paste over the current files on the customer’s Unity server. All Unity instances for commerce are set up to auto-deploy but we still manually update/deploy Unity for the scanning app and sometimes for the Unity instance resort tools is using.

Detailed Guide

  1. Get correct version of Unity files

    1. To verify the version, check the build.json file

  2. Connect to customer’s Unity server (connections are in Last Pass) and upload files (I typically put in Downloads directory but it can go anywhere).

  3. Open IIS (Internet Information Services) and locate the instance that needs to be updated.

  4. Stop the Application Pool being used by the Unity instance

    1. Click the entry under Sites (i.e. UnityTestEldora below) and select Basic Settings to see which App Pool is being used

    2. From the main IIS window, click Application Pools and find the entry on the right and click Stop (or right click to select Stop)

  5. Navigate to main IIS page and right click on Site (i.e. UnityTestEldora) and select Explore to go to the location of the Unity files.

  6. Unzip uploaded Unity files

  7. Backup existing files. I usually copy files and put in Downloads directory (i.e. UnityProd_backup_20210318) but they can be copied anywhere.

  8. Copy all new files except:

    1. Config directory - not used so no need to copy over

    2. Logs directory

    3. appsettings.json - contains customer specific values

    4. identity-config.json - contains customer specific values

    5. rtp-config.json - contains customer specific values

    6. siriusware-config.json - contains customer specific values (only exists for SW customers)

  9. Start app pool.

  10. Test updated Unity instance in Swagger (Doc: How to Test Unity in Swagger )

  11. Test logging into site (if applicable)

 

Versions

As of 12/10/2024, the min version of Unity needed for the scanning app v1.1.29 (or greater), is v3.47 which is attached below. This attachment does not include the config files, rtp-config.json, appsettings.json or identity-config.json (so therefore this cannot be used for a new install).