Subscribe

UiPath Installation and Upgrade

The UiPath Installation and Upgrade Guide

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 v2021.4 Orchestrator 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.

Learn more about the Backward and Forward Compatibility between Action Center and Orchestrator.

The Actions tab and functionality within Orchestrator continues to be supported until a future release. However, we recommend routing your users to the new Action Center interface for a better user experience and any net new features in future releases.

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.

Installation Steps


❗️

For upgrading processes:

Manually add the correct value of the Action_Center_URL key in the registry at Path Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\UiPath\UiPath Action Center.

To find the correct value of the Action_Center_URL from the env.json file:

  1. Navigate to the Installation Folder.
  2. Go to the ActionCenter/Actions/environments/env.json file path.
  3. From the PostLogoutRedirectUri key, retrieve the correct Action_Center_URL.

The format for the PostLogoutRedirectUri is "Action Center URL"/actions. For example, if the PostLogoutRedirectUri is https://action-center.loadbalancer.uipath.com:447/actions, then the corresponding Action Center URL is https://action-center.loadbalancer.uipath.com:447.

If the correct value of the Action_Center_URL is not provided before starting the upgrade process, then loading the Action Center portal will fail after upgrading, and you will need to manually update the env.json file. For step-by-step instructions on how to update the env.json file, check the last row from Action Center installation issues.

  1. Run the Windows Installer.
  2. Select the I accept the terms in the License Agreement checkbox to agree to the terms in the agreement, then click Next. The Action Center IIS Settings selection window is displayed.
885
  1. Change the IIS Settings as desired:
    • Installation Path - Change the default path as desired. Don't use a user-profile path (C:\Users) because the IIS AppPool<Apppoolname> doesn’t have adequate permissions on it. You need Read and Write permissions on the installation directory.
    • Host Name - Auto-populated with the hostname. For a server under a network domain, the discoverable machine name is read from the HKM registry key. If the installer does not find a registry value, the local hostname is displayed.
    • Port - An unused port on the server. Use a different port than Orchestrator, if installed on the same server.
    • SSL Certificate - The Subject or Thumbprint of the SSL certificate you want to secure connections with. By default, this is filled in with the full computer name. See Action Center Prerequisites for Installation for details about the SSL certificate you can use.
  2. Click Next. The Action Center Application Pool Settings window is displayed.
880
  1. Configure the editable options as desired:
    • Identity - enables you to choose the identity under which the UiPath Action Center website runs. The following options are available:
      • Application Pool Identity - runs the Action Center website under the default identity of the application pool.
      • Specific User - runs the Action Center website under an existing Windows or Domain identity. Selecting this option displays two fields, Username and Password, which enable you to specify the identity under which to run.

For more information on Application Pool Identities, please see Microsoft's official documentation.

  1. Click Next. The Action Center UiPath Identity Server window is displayed.
881
  1. Configure the editable options as desired:
    • Orchestrator URL - Specify port information in the URL only if it is not the default port (443 or 80).
    • Identity URL - Specify the Identity Server URL. Automatically populated with the Orchestrator URL plus the suffix /identity.
    • Action Center URL - Automatically populated based on hostname and port information provided. If the Action Center application is configured behind a reverse proxy or load balancer, provide the user-facing URL.
    • Identity Installation Token - The access token taken from the Identity Management Portal. See Accessing Identity Management Portal for details on how to access it.
      The token is valid for 7200 seconds (2 hours) after generating it.
  2. Click Next. The installation process starts. You can now use Action Center.

🚧

Important:

To prevent the The supplied identity JWT token is expired error:

  1. Make sure the Identity Installation Token is valid (step 7).
  2. Verify that the Date and Time on the Action Center and the corresponding Orchestrator hosting machines are synchronized.

Accessing Action Center

Business users can access Action Center by using the https://<actioncenterhost>:<port>/ URL. They can use their credentials to log in to a particular tenant through the UiPath Identity Server.
Upon logging in, they are redirected to the Actions page (https://<actioncenterhost>:<port>/actions/) from where they can navigate to Processes (https://<actioncenterhost>:<port>/processes/) using the left -hand menu. The Processes page can also be accessed directly using the https://<actioncenterhost>:<port>/processes URL.

Get started with Action Center.

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
    a. Go to the Orchestrator installation folder.
    b. Open the UiPath.Orchestrator.dll.config file with administrative permissions.
    c. Add the Action Center URL in the Authorization section using the AcceptedRootUrls parameter.
    For example: <add key="AcceptedRootUrls" value="http://localhost:6234,https://ACTION_CENTER_ROOT_URL:PORT" />.

🚧

Note

  1. Make sure the value of the AcceptedRootUrls key does not include space characters.
  2. Only add the PORT value if it is different than 80 or 443 (default ports).
  1. Allow the OPTIONS verb in IIS for the Orchestrator website:
    a. Navigate to IIS
    b. Select UiPath Orchestrator from the Sites list
    c. Click Request Filtering. The Request Filtering window is displayed.
    d. Right-click in the window and select Allow Verb
1230

e. Enter OPTIONS and click OK.

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

Updated 5 months ago


Installation


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.