How To Deploy Orchestrator Web Application Into The Storage Account For The Physical Path?

News Knowledge Base
1

How to deploy Orchestrator web application into the Storage Account for the physical path?

Resolution: Steps to perform,

  • As per UiPath official documentation, install the Orchestrator, Identity, resource catalog, and webhooks.

Below is the example,

  1. Install 2022.10 Orchestrator as per this documentation The Azure App Service Installation - Script
  2. Post installation then ensure the Orchestrator up and running
  3. Using some FTP tool like FileZilla and connect to the orchestrator FTP and copy the entire Orchestrator web application into the local system. Post moving entire file into the local system, delete entire files from the wwwroot directory.
  4. Then zip it from the root Directory do not zip the entire folder. If the entire folder is zipped, then update the same folder name in the app service configuration page this step will be mentioned in below.
1.jpg
  1. After the Orchestrator zip, then go ahead and create the Storage Account. If the storage account is already present, then use the existing one, also make sure both app service and storage location need to be in the same Location. If not, performance issue may be faced. The recommendation from Azure side also during the Storage Account creation, use the Premium option this will get faster instead of standard
  2. Refer this document for more info on the above point: Mount Azure Storage as a local share in App Service
  3. In the storage account create new container and upload the Orchestrator web app zip file like this below.

2.jpg

  1. Make sure this zip file need to have access to the Orchestrator Azure web app Vnet or public as per the network configuration that means this zip file should have to accessible in the app service to make the connection
  2. Create Shared Access tokens

3.jpg

  1. Copy the Blob SAS URL
  2. Go to the app service and Configuration page and add new Application Settings Name: WEBSITE_RUN_FROM_PACKAGE Value: Blob SAS URL
  3. More details refer this link Access a package in Azure Blob Storage using a managed identity

4.jpg

  1. Click on Save post saving the Web application auto restart by default
  2. As mentioned above, if root folder is zipped then update the root folder name in the Virtual applications and directories
  3. Go to Configuration page and Path Mappings Virtual applications and directories from here you should have to edit the Virtual Path

  1. Update the root folder name Ex: Orchestrator, for this update the root folder name.

  1. Click on Save then try to browser the URL it will work
  2. Basically the above scenario will load the Orchestrator web app from the storage account, and not from the app service
  3. In this type of deployment, it is possible to edit any files from the wwwroot director from kudo because it will be read only mode which means the zip file it just mount to the app service it would consume the storage location drive in the app service.

  1. This type of deployment will secure the web application
  2. To make any changes in the config files, download the zip file from the storage account and make the changes in the local machine and republish the same in the container.

The above steps for the Orchestrator, perform the same steps in the Identity, Webhooks, and resource catalog then try the same steps as per the above steps.