- Release notes
- Installation and upgrade
- Before you begin
- Getting started
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait For Job And Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Create Form Task
- Wait For Form Task And Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task And Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Add Task Comment
- Update Task Labels
- Actions
- Processes
- Audit
Action Center: Azure PaaS installation
The Azure installation script enables you to install Action Center on one or multiple nodes.
Make sure you have the following tools installed on your machine:
- PowerShell Web Deploy Snapin
- PowerShell AzureAZ Module version 7.0 or higher.
- Navigate to your Azure Portal and search for App Services.
-
Create a new app service and name it accordingly, for example
UiPathActionCenter
.Note: From the Runtime stack drop-down select .NET Core 3.1. - Open the previously created web app and navigate to Configuration > General settings from the left-side menu and set the Platform field to 64 Bit.
-
In the Azure portal, search for App registrations and create a new one, named accordingly.
Important: You need to assign the Contributor role to the app registration. See here how to do it. -
On your app's Overview page, copy the Application (client) ID and save it for later use. This is your Azure service principal ID.
-
On the Clients & secrets page of the previously created app registration, generate a new client secret. Copy its Value and save it for later use. This is your Azure service principal password.
Note: Optionally, you can ask your friendly DevOps team to provide you with an Azure service principal ID and password that can access the app service and its associated resource group.
-
Download the
UiPathActionCenter.zip
archive to your local machine. This contains all the necessary installation scripts. - Extract the content of the
.zip
file to a folder on your machine. -
Run the
Publish-ActionCenter-Azure.ps1
script in PowerShell, using these installation parameters.Check out this script example.
- Enjoy using Action Center on your Azure Portal.
The multi-node installation is similar to the single node installation, with an additional step between steps 6 and 7 of the single node procedure.
Therefore, after step 6, you need to perform the following actions:
- Open the newly created app service.
- Go to the Scale out (App Service plan) tab from the left-side menu.
- Select the Scale to a specific instance count option.
- Provide the desired Instance count.
Continue with step 7 of the single node procedure afterward.
true
:
IdentityServer.OAuth.Enabled
IdentityServer.S2SIntegration.Enabled
If you want to use a custom domain for your Action Center app service, please set the custom domain first and then use this domain name in the script parameters.
https://actioncenter.xyz.com
, use the same value for the actionCenterUrl
script parameter.
Parameter |
Description |
---|---|
|
Mandatory. The URL of the Orchestrator instance. |
|
Mandatory. The URL of the Identity Server instance. |
|
Mandatory. The URL of the ActionCenter instance. |
|
Mandatory. The access token from the Identity Management Portal. See Host authentication settings for details. |
|
Mandatory. The Azure subscription ID for the App Service that hosts Action Center. Note: Find it on the app service's Overview page, in your Azure Portal.
|
|
Mandatory. The Azure tenant ID. Note: Find it on the app registration's Overview page, in your Azure Portal.
|
|
Mandatory. The Azure service principal ID. Note: It's the one you copied and saved at step 5 of the Single Node Installation procedure.
|
|
Mandatory. The Azure service principal password. Note: It's the one you copied and saved at step 6 of the Single Node Installation procedure.
|
|
Mandatory. Indicate the full path or relative path of the
UiPath.ActionCenter.Web.zip archive.
Note: Find it in the
UiPath.Actioncenter.zip archive.
|
|
Mandatory. The name of the Azure resource group that contains the Action Center app service. |
|
Mandatory. The Action Center Azure app service name. |
|
Optional. If present, it stops the application before deployment and it starts it after the deployment is completed. |
|
Optional. If present, the deployment continues without any user confirmation. |
.\Publish-ActionCenter-Azure.ps1 `
-orchestratorUrl "https://<OrchestratorServiceURL>" `
-identityServerUrl "https://<IdentityServerURL>/identity" `
-actionCenterUrl "https://<ActionCenterServiceURL>" `
-identityInstallationAccessToken "abcdefgh ... MAxJeysh6IQFSabcd" `
-azureSubscriptionId "d12f123e-12ac-1da1-1234-ed1234d5cf4b" `
-azureAccountTenantId "d1234d2a-b123-1d12-1234-902c51f12345" `
-azureAccountApplicationId "12345678-67e1-123d-1234-1c6cd123b123" `
-azureAccountPassword "O.T5pX4bX89I3~Wi.clbM_u0-R5Aa-sRl~" `
-package "E:\)\)Work\)\)UiPathActionCenter\)\)UiPath.ActionCenter.Web.zip" `
-stopApplicationBeforePublish `
-resourceGroupName "<ResourceGroupName" `
-appServiceName "<ActionCenterServiceName>" `
-unattended
.\Publish-ActionCenter-Azure.ps1 `
-orchestratorUrl "https://<OrchestratorServiceURL>" `
-identityServerUrl "https://<IdentityServerURL>/identity" `
-actionCenterUrl "https://<ActionCenterServiceURL>" `
-identityInstallationAccessToken "abcdefgh ... MAxJeysh6IQFSabcd" `
-azureSubscriptionId "d12f123e-12ac-1da1-1234-ed1234d5cf4b" `
-azureAccountTenantId "d1234d2a-b123-1d12-1234-902c51f12345" `
-azureAccountApplicationId "12345678-67e1-123d-1234-1c6cd123b123" `
-azureAccountPassword "O.T5pX4bX89I3~Wi.clbM_u0-R5Aa-sRl~" `
-package "E:\)\)Work\)\)UiPathActionCenter\)\)UiPath.ActionCenter.Web.zip" `
-stopApplicationBeforePublish `
-resourceGroupName "<ResourceGroupName" `
-appServiceName "<ActionCenterServiceName>" `
-unattended
Action Center features that use the storage buckets inside Orchestrator, such as images & PDF rendering on Form actions, Document Classification, and Document Validation actions, require the following configuration in Orchestrator:
- Open the Orchestrator web app in your Azure Portal.
- Navigate to Configuration and select Application Settings.
-
Add a New application setting and input the following:
- Name -
AcceptedRootUrls
-
Value -
https://localhost:6234,https://<ActionCenterServiceURL>
Important: Make sure the value entered in the Value field has no empty spaces in it.Note: Replace<ActionCenterServiceURL>
with the corresponding URL of your Action Center Service.
- Name -
- Open the Orchestrator web app in your Azure Portal.
- Navigate to App Service Editor (Preview).
-
Edit the
web.config
file:- Navigate to the
<requestFiltering>
<verbs>
section. -
Append
<add verb="OPTIONS" allowed="true" />
at the end of the section.Note: Upgrading Orchestrator resets theweb.config
file, so you need to allow theOPTIONS
verb once again.For third party storage providers, read more details about the CORS/CSP Configuration.
- Navigate to the
To upgrade Azure PaaS Action Center, you need to install a new, higher version that replaces the current one.
- Before You Begin
- Single node installation
- Creating the Azure App Service for Action Center
- Creating the Azure Service Principal for Action Center
- Installing Action Center on Azure
- Multi-node installation
- Powershell installation script parameters
- PowerShell Script Example
- Storage buckets requests
- To accept Action Center requests to Orchestrator:
- To allow
OPTIONS
in theweb.config
file of the Orchestrator web app: - Upgrading
- Uninstalling