Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

These are the steps to update Unity manually which is a copy/paste over the current files on the customer’s Unity server. The majority of customers are setup to auto-deploy Unity but Sugarbush and Killington still need to be done manually and sometimes new customers may not be setup for auto-deploy yet. Also sometimes the auto-deploy fails for various reasons. Typically dev ops will ask us to manually update Unity.

Instructions

  1. Download Unity_drop.zip from file share. You may need to be granted access to this Azure location.

    1. https://portal.azure.com/#blade/Microsoft_Azure_Storage/ContainerMenuBlade/overview/storageAccountId/%2Fsubscriptions%2F34c7ba34-f99c-4fc6-ad3b-2c242a94701a%2FresourceGroups%2FAspenwareUnity%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Funityfileshare/path/aspenwareunityappliance/etag/"0x8D77EB0014413B1"

  2. Newest Unity build ends up in one of these two folders:

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

    2. To verify which version was downloaded (if needed), navigate into downloaded zip file and open Build.json to see version after downloading the zip file locally.

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

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

  5. 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)

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

  7. Unzip Unity_drop.zip file

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

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

    1. UnityAPI.Web - File Type: Application

    2. All .dll’s - File Type: Application Extension

    3. UnityAPI.Web.exe - File Type: CONFIG File

    4. build - File Type: JSON File

    5. UnityAPI.Web - File Type: XML Document

  10. Restart IIS App Pools

  11. Test logging into site

  • No labels