...
These are the steps to update Unity manually which is a to copy/paste over the current files on the customer’s Unity server. The majority of customers All Unity instances for commerce are set up to auto-deploy Unity but several (Sugarbush and Killington) still must be done manually. Occasionally, newly implemented customers may not be set up for auto-deploy yet. Also sometimes the auto-deploy fails for various reasons. Typically dev ops will ask Aspenware’s Service team to manually update Unitybut we still manually update/deploy Unity for the scanning app and sometimes for the Unity instance resort tools is using.
Detailed Guide
...
Download Unity_drop.zip from file share. You may need to be granted access to this Azure location.
Newest Unity build ends up in one of these two folders:
...
Look for the date/time that is closest to when dev ops kicks off the build. Sometimes it ends up in _develop and sometimes it ends up in _master.
...
Get correct version of Unity files
To verify the version, check the build.json file
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).
Open IIS (Internet Information Services) and locate the instance that needs to be updated.
Stop the Application Pool being used by the Unity instance
Click the entry under Sites (i.e. UnityTestEldora below) and select Basic Settings to see which App Pool is being used
From the main IIS window, click Application Pools and find the entry on the right and click Stop (or right click to select Stop)
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.
Unzip uploaded Unity
...
files
Backup existing files. I usually copy files and put in Downloads directory (i.e. UnityProd_backup_20210318) but they can be copied anywhere.
...
**For Unity 3.12 and below, use #9. For Unity 3.13 and greater, go to #10..** Copy the following files and paste into Unity directory. DO NOT COPY ALL FILES. Recommend sorting by the Type column and you can multi-select all these files at the same time
UnityAPI.Web - File Type: Application
All .dll’s - File Type: Application Extension
UnityAPI.Web.exe - File Type: CONFIG File
build - File Type: JSON File
UnityAPI.Web - File Type: XML Document
...
**For Unity 3.12 and below, use #9. For Unity 3.13 and greater, go to #10..**Copy the following files and paste into Unity directory. DO NOT COPY ALL FILES. Recommend sorting by the Type column and you can multi-select all these files at the same time
runtime and wwwroot folders (don’t need Config folder)
All .dll’s - File Type: Application Extension
UnityAPI.Web.exe - File Type: CONFIG File
build - File Type: JSON File
All ‘XML Document’ files types
...
Restart IIS App Pools
Copy all new files except:
Config directory - not used so no need to copy over
Logs directory
appsettings.json - contains customer specific values
identity-config.json - contains customer specific values
rtp-config.json - contains customer specific values
siriusware-config.json - contains customer specific values (only exists for SW customers)
Start app pool.
Test updated Unity instance in Swagger (Doc: How to Test Unity in Swagger )
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).
View file | ||
---|---|---|
|