- Getting Started
- Network requirements
- Single-node requirements and installation
- Multi-node requirements and installation
- Post-installation
- Accessing AI Center
- Provision an AI Center tenant
- Updating Orchestrator and Identity Server certificates
- Resizing PVC
- Adding a new node to the cluster
- ML packages offline installation
- Configuring the Cluster
- Configuring the FQDN post-installation
- Backing up and Restoring the Cluster
- Using the Monitoring Stack
- Setting up a Kerberos Authentication
- Provisioning a GPU
- Using the configuration file
- Node scheduling
- Migration and Upgrade
- Basic Troubleshooting Guide
Procedure
This step needs to be run on a machine with internet access and access to the machines in the air-gapped environment where UiPath AI Center will be installed.
- Connect to a machine with internet access and run the following command to get the interactive wizard file:
ssh <user>@<dns_of_vm>
ssh <user>@<dns_of_vm> - If you used an SSH key, run the following command:
ssh -i <path/to/Key.pem> <user>@<dns_of_vm>
ssh -i <path/to/Key.pem> <user>@<dns_of_vm> - Download the following packages:
installUiPathAS.sh
- Mandatory. See installUiPath.as for download instructions.sf-installer.zip
- Mandatory. See sf-installer.zip for download instructions.sf.tar.gz
- Mandatory. See sf.tar.gz for download instructions.sf-infra.tar.gz
- Optional. Only needd if you want to join additional nodes, including Task Mining and GPU. See sf-infra.tar.gz for download instructions.du-ondemand.tar.gz
- Optional. Needed only for Document Understanding. See du-ondemand.tar.gz for download instructions.Note: Not following this optional step limits the functionality of the Document Understanding services.cv-ondemand.tar.gz
– Optional. Needed only for Computer Vision. See cv-ondemand.tar.gz for download instructions.Note: Not following this optional step prevents access to the Computer Vision services.
- Go to the first target machine for installation:
- Run the following command:
ssh <user>@<dns_of_vm>
ssh <user>@<dns_of_vm> - If you used an ssh key, run the following command:
ssh -i <path/to/Key.pem> <user>@<dns_of_vm>
ssh -i <path/to/Key.pem> <user>@<dns_of_vm>
- Run the following command:
Make sure to download the package suitable for your AI Center version and your operating system.
Make sure to take the following steps:
- Check that all files have finished downloading on the machine with internet access.
- Create the target folder on the machine.
- Copy the files from the online machine to the target machine.
sudo su -
mkdir -p /opt/UiPathAutomationSuite/
chmod -R 755 /opt/UiPathAutomationSuite
sudo su -
mkdir -p /opt/UiPathAutomationSuite/
chmod -R 755 /opt/UiPathAutomationSuite
- From the machine with internet access, copy the files to the installation folder on the target machine, and the offline bundle(s)
to the
/uipath/tmp
folder.scp ./installUiPathAS.sh ./sf-installer.zip ./sf-infra.tar.gz <username>@<node dns>:/uipath/tmp/ scp ~/sf.tar.gz <username>@<node dns>:/uipath/tmp/ scp ~/sf-infra.tar.gz <username>@<node dns>:/uipath/tmp/
scp ./installUiPathAS.sh ./sf-installer.zip ./sf-infra.tar.gz <username>@<node dns>:/uipath/tmp/ scp ~/sf.tar.gz <username>@<node dns>:/uipath/tmp/ scp ~/sf-infra.tar.gz <username>@<node dns>:/uipath/tmp/ - (Optional) To use Document Understanding, copy the following bundles to the
/uipath/tmp
folder.scp ~/du-ondemand.tar.gz <username>@<node dns>:/uipath/tmp/
scp ~/du-ondemand.tar.gz <username>@<node dns>:/uipath/tmp/Note: Not following this optional step prevents access to the Document Understanding services. - (Optional) To use Computer Vision, copy the following bundle to the
/uipath/tmp
folder.scp ~/cv-ondemand.tar.gz <username>@<node dns>:/uipath/tmp/
scp ~/cv-ondemand.tar.gz <username>@<node dns>:/uipath/tmp/Note: Not following this optional step prevents access to the Computer Vision services.
.cer
format. Copy the certificate to the virtual machine using the command below.
/opt/UiPathAutomationSuite
has the right permission for files to be copied over scp, or copy the file into your home directory and then move it to /opt/UiPathAutomationSuite
.
scp /path/to/orch.cer <username>@<node dns>:/opt/UiPathAutomationSuite
scp /path/to/orch.cer <username>@<node dns>:/opt/UiPathAutomationSuite
identityserver.cer
as well.
When using a domain-issued certificate, make sure to export the root certificate as follows:
- Open the certificate, go to the Certification Path tab and select the first certificate. Click on View certificate.
- Once the root certificate is displayed, go to the Details tab and click Copy to file.
- Make sure to select base64
cer
file format. - Save it with the name of your choice and then send it to AI Center machine.
The resulting file should be similar to the example below.
-----BEGIN CERTIFICATE-----
certificate
base64
encoded
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
certificate
base64
encoded
-----END CERTIFICATE-----
- Add the following prerequisites to the current PATH:
- The interactive installer requires
jq
and our offline bundles already includes it. Run the following commands to add it to PATH: (make sure you are still root)mv /uipath/tmp/installUiPathAS.sh /uipath/tmp/sf-installer.zip /opt/UiPathAutomationSuite cd /opt/UiPathAutomationSuite unzip ./sf-installer.zip -d . chmod +x ./bin/jq export PATH=${PATH}:/opt/UiPathAutomationSuite/bin
mv /uipath/tmp/installUiPathAS.sh /uipath/tmp/sf-installer.zip /opt/UiPathAutomationSuite cd /opt/UiPathAutomationSuite unzip ./sf-installer.zip -d . chmod +x ./bin/jq export PATH=${PATH}:/opt/UiPathAutomationSuite/bin
- The interactive installer requires
- Provide permissions to Installer Folder:
- It is required to give adequate permissions to the
/opt/UiPathAutomationSuite
folder where the install scripts are placed and going to be executed. Installer will also create some files (output.json
) after execution of each stage.Run the following command to provide the permissions:
chmod -R 755 /opt/UiPathAutomationSuite
chmod -R 755 /opt/UiPathAutomationSuite
- It is required to give adequate permissions to the
- Run the interactive install wizard to configure the installation options:
- Interactive wizard will guide through the configuration steps and generate the config file which can be then customized and used through the remaining install steps.
- Run the script the begin the interactive wizard by running the following command:
chmod +x ./installUiPathAS.sh ./installUiPathAS.sh
chmod +x ./installUiPathAS.sh ./installUiPathAS.sh - Follow the steps in the wizard
Upon starting the installation wizard, the main menu is displayed. From this menu you need to choose the desired deployment mode: single-node or multi-node. You are prompted with details about each mode once a choice is made. After that, you have the option to continue with the current choice or go back to the main menu.
- Accept the license agreement.
- Select the deployment mode: select the Multi-node deployment option.
- Select continue.
- Select Air-gapped installation.
- Select Complete installation.
- Enter the DNS hostname.
- Specify whether you want to use Kerberos Auth for SQL connections.
- Enter the SQL Server URL. Follow the prompt to enter the connection port, username, and password.
- Specify whether you want the installer to automatically create the necessary databases.
cluster_config.json
file is now generated. We will update this file to the purpose of the AI Center installation.
vi /opt/UiPathAutomationSuite/cluster_config.json
vi /opt/UiPathAutomationSuite/cluster_config.json
"aicenter": {
"enabled": "false"
},
"aicenter": {
"enabled": "false"
},
<>
with your values):"aicenter": {
"orchestrator_url":"<https://orchestrator-url.com>",
"identity_server_url": "<https://orchestrator-url.com/identity>",
"orchestrator_cert_file_path": "</opt/UiPathAutomationSuite/orch.cer or custom path>",
"identity_cert_file_path": "</opt/UiPathAutomationSuite/orch.cer or custom path>",
"identity_access_token": "<placeholder will be replaced later>"
},
"aicenter": {
"orchestrator_url":"<https://orchestrator-url.com>",
"identity_server_url": "<https://orchestrator-url.com/identity>",
"orchestrator_cert_file_path": "</opt/UiPathAutomationSuite/orch.cer or custom path>",
"identity_cert_file_path": "</opt/UiPathAutomationSuite/orch.cer or custom path>",
"identity_access_token": "<placeholder will be replaced later>"
},
cluster_config.json
file in the UiPathAutomationSuite
folder. You can use this file to configure your SQL DBs and their respective connection strings and certificates. You can
also enable proxy settings if you use a proxy for internet connection.
For advanced configuration, see Using the configuration file.
- Copy the
~/UiPathAutomationSuite
folder to all other nodes by running:scp -r ~/UiPathAutomationSuite <username>@<node dns>:/opt
scp -r ~/UiPathAutomationSuite <username>@<node dns>:/optNote: Since we are in an air-gapped environment, you might need to use the private IP of the target node. - Add
-i <cert.pem>
if you are using a certificate to login. If you copy the.pem
contents to a local file, the new file will need to have correct permissions. You can dochmod 400 <cert.pem>
for granting them.
- Run the infrastructure installer on all nodes:
- Set up the primary machine by executing the following commands on the primary server:
cd /opt/UiPathAutomationSuite ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement --install-standalone-aicenter
cd /opt/UiPathAutomationSuite ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement --install-standalone-aicenter - Join the rest of the servers to the cluster by executing the following commands on the rest of the server nodes:
mv /uipath/tmp/UiPathAutomationSuite /opt cd /opt/UiPathAutomationSuite sudo chmod -R 755 /opt/UiPathAutomationSuite sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement --install-standalone-aicenter
mv /uipath/tmp/UiPathAutomationSuite /opt cd /opt/UiPathAutomationSuite sudo chmod -R 755 /opt/UiPathAutomationSuite sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement --install-standalone-aicenter - Join the rest of the agents to the cluster by executing the following commands on the rest of the agent nodes:
mv /uipath/tmp/UiPathAutomationSuite /opt cd /opt/UiPathAutomationSuite sudo chmod -R 755 /opt/UiPathAutomationSuite sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j agent --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement --install-standalone-aicenter
mv /uipath/tmp/UiPathAutomationSuite /opt cd /opt/UiPathAutomationSuite sudo chmod -R 755 /opt/UiPathAutomationSuite sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j agent --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement --install-standalone-aicenter
- Set up the primary machine by executing the following commands on the primary server:
- Run the fabric installer on primary node
cd /opt/UiPathAutomationSuite export TMPDIR="/uipath/lib/containers/tmp" mkdir -p "/uipath/lib/containers/tmp" ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f --offline-bundle /uipath/tmp/sf.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement --install-standalone-aicenter
cd /opt/UiPathAutomationSuite export TMPDIR="/uipath/lib/containers/tmp" mkdir -p "/uipath/lib/containers/tmp" ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f --offline-bundle /uipath/tmp/sf.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement --install-standalone-aicenter - Run the software installer on primary node First you need to connect to identity server and retrieve an installation token. Then copy this token and paste it in placeholder
we had in step 3.2. (in the cluster_config.json file). Once the token is there, you can run the AI Center install.
./install-uipath.sh -i cluster_config.json -o output.json --offline-bundle /uipath/tmp/sf.tar.gz --accept-license-agreement --install-standalone-aicenter --offline-tmp-folder /uipath/tmp -s
./install-uipath.sh -i cluster_config.json -o output.json --offline-bundle /uipath/tmp/sf.tar.gz --accept-license-agreement --install-standalone-aicenter --offline-tmp-folder /uipath/tmp -s - Load the optional Document Understanding bundles commands. To load the optional bundles, execute the following command. Make
sure to use the bundle name that you need to load.
./install-uipath.sh -i ./cluster_config.json -o ./output.json --optional-offline-bundle "/uipath/tmp/du-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp" --accept-license-agreement
./install-uipath.sh -i ./cluster_config.json -o ./output.json --optional-offline-bundle "/uipath/tmp/du-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp" --accept-license-agreement - Load the optional Computer Vision bundle command. To load the optional Computer Vision bundle, execute the following command:
./install-uipath.sh -i ./cluster_config.json -o ./output.json --optional-offline-bundle "/uipath/tmp/cv-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp" --accept-license-agreement
./install-uipath.sh -i ./cluster_config.json -o ./output.json --optional-offline-bundle "/uipath/tmp/cv-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp" --accept-license-agreement
- Step 1: Download the Installation Script on the First Machine
- 1.1 Download the installation packages
- 1.2 Get all downloaded files on the first machine
- Step 2: Copy the Orchestrator certificate to the virtual machine
- Chain certificates
- Step 3: Configure the Installation
- Prerequisites
- 3.1 Use the interactive wizard to create base config file
- 3.2 Add AI Center-specific configuration
- 3.3 (Optional) Advanced configuration
- Step 4: Copy the installation files on all the other cluster machines
- Step 5: Running the Installation