Manual: Installing Automation Suite

The following table lists the steps you must perform for single-node and multi-node installations:

Steps	Single-node installation	Multi-node installation
Step 1: Accepting the license agreement
Step 2: Installing the Infrastructure on the first server machine

Step 1: Accepting the license agreement

Before running the installation, make sure to read the license agreement.

To accept the license agreement, choose one of the following methods:

• Option 1 (Environment variable) - Set the LICENSE_AGREEMENT environment variable to accept by running the following command:

  export LICENSE_AGREEMENT=accept

• Option 2 (Inline parameter) - Append --accept-license-agreement to every execution of install-uipath.sh.

Step 2: Installing the infrastructure on the first server machine

To install the infrastructure on the first server machine, navigate to the installer folder and run the following command:

cd /opt/UiPathAutomationSuite/<version>/installer

./install-uipath.sh -i /opt/UiPathAutomationSuite/cluster_config.json -o ./output.json -k --accept-license-agreement

Note:

• The -k parameter installs the infrastructure on the first server machine.

• Once the infrastructure is installed, the server machine becomes a node in the Automation Suite cluster.

Step 3: Installing the infrastructure on the other server machines

To expand the Automation Suite cluster, install the infrastructure on the additional server machines.

To do that, run the following command on all the additional server machines:

cd /opt/UiPathAutomationSuite/<version>/installer
 
 ./install-uipath.sh -i /opt/UiPathAutomationSuite/cluster_config.json -o ./output.json -k -j server --accept-license-agreement

Note: The -j server parameter adds the machines as server nodes to the existing Automation Suite cluster. The fixed_rke_address flag in the cluster_config.json file connects the exiting Automation Suite cluster.

Step 4: Installing the infrastructure on all the agent machines

If you have additional agent machines, you must install the infrastructure on those machines and add them as agent nodes to the Automation Suite cluster.

To to that, run the following command on all the agents machines:

cd /opt/UiPathAutomationSuite/<version>/installer
 
 ./install-uipath.sh -i /opt/UiPathAutomationSuite/cluster_config.json -o ./output.json -k -j agent --accept-license-agreement

Note: The -j agent parameter adds the machines as agent nodes to the existing Automation Suite cluster. The fixed_rke_address flag in the cluster_config.json file connects the exiting Automation Suite cluster.

Step 5: Completing the installation

At this point, all the nodes should be interconnected to establish the infrastructure for installing Automation Suite. To verify if all nodes are available on the first server node and to complete the installation, run the following command:

export KUBECONFIG=/etc/rancher/rke2/rke2.yaml 
export PATH=$PATH:/var/lib/rancher/rke2/bin 

kubectl get nodes

The output of the aforementioned command should look similar to the one shown in the following image. Note that the total number of nodes must match the sum of server and agent nodes.

After verifying the infrastructure, install the fabric and the services by running the following command:

./install-uipath.sh -i /opt/UiPathAutomationSuite/cluster_config.json -o ./output.json -f -s --accept-license-agreement