Installation

Action Center is available for on-premises installation, allowing you to manage actions from a dedicated user interface, other than the Actions tab in the corresponding Orchestrator instance.

Although Action Center relies on an existing Orchestrator instance, it can be installed on a separate server or the same server as Orchestrator.

The authentication and authorization aspects are managed through a corresponding Identity Server instance and Orchestrator instance, as provided during the Action Center installation procedure.

Compatibility

Orchestrator

Customers using Actions Center within Orchestrator do not have to perform any additional steps other than pointing the Action Center instance to an existing Orchestrator 2021.10 instance. All the existing actions will be reflected to end-users in the new Action Center portal as per the access control defined in a corresponding Orchestrator tenant.

Supported topologies

Single Node Scenarios

• Action Center running on the same server as Orchestrator (different port).
• Action Center running on a single node server pointing to a separate single node Orchestrator instance.

Multi-Node Scenarios

• Multi-node Orchestrator behind a load balancer:

  • A single Action Center instance installed on a different server pointing to the Orchestrator load balancer URL.
  • Action Center installed on all Orchestrator nodes, each pointing to the Orchestrator load balancer URL.
  • Business users exposed to a load-balanced Action Center URL.

Orchestrator settings to accept storage bucket requests from Action Center

Features within Action Center that rely on Orchestrator storage buckets (Images & PDF rendering on Form actions, Document Classification & Document Validation actions) require the following configuration changes in Orchestrator to function as expected:

1. Accept Action Center requests to Orchestrator
   1. Go to the Orchestrator installation folder.
   2. Open the UiPath.Orchestrator.dll.config file with administrative permissions.
   3. Under the <appSettings> tag, locate the following key: <add key="AcceptedRootUrls" value="http://{your_localhost_name}:{port_number}" />. If you can't locate the key inside the file, manually add the key yourself.
   4. Append the Action Center URL to the previously located or manually added key (e.g., "https://{Action_Center_host}:{port_number}"). Replace the values in the brackets with your own. For example: <add key="AcceptedRootUrls" value="http://localhost:1234,https://laptop-batman:555" />.
      Important:

      • Make sure the value of the AcceptedRootUrls key does not include space characters.
      • Only add the port value if it is different than 80 or 443 (default ports).
2. Check if the OPTIONS verb is allowed in IIS for the Orchestrator website:
   1. Navigate to IIS.
   2. Select UiPath Orchestrator from the Sites list.
   3. Double click Request Filtering to open the Request Filtering window.

   4. Navigate to the HTTP Verbs tab and search for the OPTIONS verb in the displayed list.

      In case the OPTIONS verb is not present in the list:

      1. Right-click in the window and select Allow Verb.
         
         

         

         
         
      2. Enter OPTIONS and click OK.
         
         

         

         
         
3. Reset IIS for the changes to take effect.

   For other storage buckets like Amazon S3 and Azure, see CORS/CSP Configuration for details on how to configure CORS and CSP settings.

Command line parameters

It is possible to install or update the entire UiPath suite using the command line, provided you have the UiPath Action Center Windows installer (UiPathActionCenter.msi). The table below lists all the available parameters you can use with Orchestrator, paired with some examples.

Parameter	Description
/q	Helps you install the specified UiPath features silently, without displaying the user interface.
/L*V <LogFile>	Generates an installer log file at the specified path. You can send the file further to our support team if, for any reason, you encounter difficulties during the installation process.
HOST_NAME	The hostname of the device on which Action Center is installed.
WEBSITE_PORT	An unused port on the server. Use a different port than Orchestrator, if installed on the same server. If not specified, the default value (443) is used to enable HTTPS.
CERTIFICATE_SUBJECT	The name of the SSL certificate you want to use to secure connections with Action Center. If not specified, by default, the full computer name is used. Please specify thumbprint if there are multiple certificates with the same subject.
INSTALLDIR	Enables you to install Action Center at a custom location. By default, it is installed at C:\Program Files (x86)\UiPath\ActionCenter. Warning: You need Read and Write permissions on the installation directory.
PORT_FIREWALL	Enables you to select if firewall rules are automatically added for this port. The available options are: 0 - Firewall rules are not added. 1 - Firewall rules are added.
PORT_DO_VALIDATE	Enables you to select if validation of the website port availability is performed. The available options are: 0 - No validation is performed. 1 - A validation is performed. The default value is 1.
APPPOOL_IDENTITY_TYPE	The type of application pool you are using for Action Center. The available options are: SpecificUser and ApplicationPoolIdentity.
APPPOOL_USER_NAME	The username running the application pool. This parameter needs to be included only if APPPOOL_IDENTITY_TYPE was set to USER.
APPPOOL_USER_PASSWORD	The password of the user running the application pool. This parameter needs to be included only if APPPOOL_IDENTITY_TYPE was set to USER.
ORCHESTRATOR_URL	The URL of the Orchestrator instance. Used by Action Center for all communication with Orchestrator.
IDENTITY_URL	The URL of the Identity Server instance.
ACTION_CENTER_URL	The Base URL of Action Center.
IDENTITY_INSTALLATION_TOKEN	The access token taken from the Identity Management Portal. See Accessing Identity Management Portal for details.
REGISTER_APP_URL	The flag used to update the Action Center URL. By default, it is set to true.

Examples

These examples have been written considering that you are already in the directory in which the UiPathActionCenter.msi installer is located. You can do this with the following command, for example: cd D:\UiPathActionCenter.msi.

Clean installing Action Center

msiexec /i UiPathActionCenter.msi^
HOST_NAME="ACTION_CENTER_HOSTNAME"^
WEBSITE_PORT="444"^
CERTIFICATE_SUBJECT="ACTION_CENTER_HOSTNAME"^
INSTALLDIR="C:\Program Files (x86)\UiPath\ActionCenter"^
APPPOOL_IDENTITY_TYPE="ApplicationPoolIdentity"^
PORT_FIREWALL="1"^
ORCHESTRATOR_URL="https://ORCHESTRATOR_URL"^
IDENTITY_URL="https://ORCHESTRATOR_URL/identity"^
ACTION_CENTER_URL="https://ACTION_CENTER_HOSTNAME:444/"^
IDENTITY_INSTALLATION_TOKEN="eyJhbGciOiJSUzI1NiIsImtpZCI6IkUyNjk3MDQzQjE1Q0QwRDlBMjBCQkZGODVGQjkyMTk2NkI4N0VFQTQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiI0bWx3UTdGYzBObWlDN180WDdraGxtdUg3cVEifQ.eyJuYmYiOjE1OTkwNjk0NTQsImV4cCI6MTU5OTA3MzA1NCwiaXNzIjoiaHR0cHM6Ly9ndXJwcmVldHVpcGF0aC9pZGVudGl0eSIsImNsaWVudF9pZCI6ImdlbmVyYXRlZENsaWVudCIsImF1ZCI6IklkZW50aXR5U2VydmVyQXBpIiwic2NvcGUiOlsiSWRlbnRpdHlTZXJ2ZXJDbGllbnRNYW5hZ2VtZW50Il19.MV9ehC8D5uBcg8PFRb8FPHv05oeFRwZgJURv2GUcmUxvQo3hzdjsxomMXoCHJiNQlqLxqsIzYrgfjwKcpVEchfyWl6HcqKvT_1s8eC3DP9qdrQJtuCrBJqgUcC99v3NaJ6UbdKYVtFDiPlIEetmqsl5ET2Dp0lNxxWle5Zp_p91U-I7SqRHz8lOm0oG0pyKeft53S7jM5Jj2Utr7bLb46ci2cmLgrwsH3Mu7rKOUCtfGHgaNvXoW5XZh9s2OYitZ-XRkCuncjXKoo9pSz7jq8MqVaLnxVRcFrpH2kDRfUew4CMeMJ-lx75maxWyElp9RnxDPykD6wXJAIPFsnuTqQA"^
/L*V "C:\InstallationLogs.log"^
/q

Upgrading an existing Action Center installation

The upgrade scenario requires you to pass two parameters in the command line, namely IDENTITY_INSTALLATION_TOKEN and REGISTER_APP_URL.

The following command line example silently upgrades your Action Center single-node installation and generates a log file.

msiexec /i UiPathActionCenter.msi^
REGISTER_APP_URL="true"^
IDENTITY_INSTALLATION_TOKEN="eyJhbGciOiJSUzI1NiIsImtpZCI6IkUyNjk3MDQzQjE1Q0QwRDlBMjBCQkZGODVGQjkyMTk2NkI4N0VFQTQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiI0bWx3UTdGYzBObWlDN180WDdraGxtdUg3cVEifQ.eyJuYmYiOjE1OTkwNjk0NTQsImV4cCI6MTU5OTA3MzA1NCwiaXNzIjoiaHR0cHM6Ly9ndXJwcmVldHVpcGF0aC9pZGVudGl0eSIsImNsaWVudF9pZCI6ImdlbmVyYXRlZENsaWVudCIsImF1ZCI6IklkZW50aXR5U2VydmVyQXBpIiwic2NvcGUiOlsiSWRlbnRpdHlTZXJ2ZXJDbGllbnRNYW5hZ2VtZW50Il19.MV9ehC8D5uBcg8PFRb8FPHv05oeFRwZgJURv2GUcmUxvQo3hzdjsxomMXoCHJiNQlqLxqsIzYrgfjwKcpVEchfyWl6HcqKvT_1s8eC3DP9qdrQJtuCrBJqgUcC99v3NaJ6UbdKYVtFDiPlIEetmqsl5ET2Dp0lNxxWle5Zp_p91U-I7SqRHz8lOm0oG0pyKeft53S7jM5Jj2Utr7bLb46ci2cmLgrwsH3Mu7rKOUCtfGHgaNvXoW5XZh9s2OYitZ-XRkCuncjXKoo9pSz7jq8MqVaLnxVRcFrpH2kDRfUew4CMeMJ-lx75maxWyElp9RnxDPykD6wXJAIPFsnuTqQA"^
/L*V "C:\InstallationLogs.log"^
/q

Note: In case of multi-node installations, the REGISTER_APP_URL parameter is optional for secondary nodes.

Turn off the flag for updating the Action Center URL for secondary nodes as follows:

• Silent upgrade — set the flag value to false (REGISTER_APP_URL="false").
• Interactive upgrade — uncheck the box for secondary nodes.

Uninstalling Action Center

msiexec /uninstall UiPathActionCenter.msi