KEMBAR78
Automation Suite PPT (2).pptx
Automation Suite Installation
Multi-nodeAir-Gapped – v2022.10.6
22 Aug 2023
2
Speakers
Ramkrishna Kadiya
Technical Account Manager
UiPath
https://www.linkedin.com/in/ramkrishna-kadiya-a5386315/
Srikirti Raj
Technical Account Manager
UiPath
https://www.linkedin.com/in/srikirti-raj/
3
Q & A
4
Events in the Series
❍ Standalone UiPath Orchestrator Upgrade (IaaS/PaaS) [2022.4 to 2023.4]
❍ UiPath Insights (Looker) Upgrade
❍ Test Manager and Action Center Upgrade
☞ Automation Suite (Installation)
❍ Automation Suite (Upgrade)
5
Agenda
❖ Automation Suite - Introduction
❖ Automation Suite - Products
❖ Automation Suite - HW/SW Requirements
❖ Automation Suite - Pre-Configuration (Machine, DNS, SQL, Certificates )
❖ Automation Suite - Installation
❖ Automation Suite - Post Installation Activities
❖ Q&A
6
The Cloud Native UiPath
Platform delivered as SaaS
from UiPath
Automation Cloud
The Cloud Native UiPath Platform delivered as a single installation
UiPath Platform products
individually installed and
managed
Individual Products
Automation Suite
7
Individual Products
UiPath Platform products
individually installed
and managed
Automation Cloud
The cloud native UiPath
Platform delivered as SaaS
from UiPath
No installation required – start
instantly, scale infinitely
One-package install on-prem (including
air-gapped) or in public cloud Linux VM,
or in existing AKS/EKS cluster
Available products installed on
supported operating systems and
physical/virtual hardware
Automation Suite
The cloud native UiPath
Platform delivered as a single
installation
7
All the products*
Integrated High Availability, backup and scale management
Integrated UiPath Portal suite experience, and shared suite functionality
Unified admin experience for organization, tenant, user and license management
*All server products except Integration Service which is planned for future updates
The UiPath Automation Suite
Enterprise-ready Suite
Flexible Installation,
Easy Update
Integrated Infrastructure
& Cluster Management
9
9
Enterprise-ready Suite
All UiPath Platform server products
Multiple tenants per organization sharing a common user set
and authentication setting
Portal-based access to services and product availability parity
with Automation Cloud
Integration with other enterprise systems:
Azure AD, AD and CyberArk
RPA governance and security built in
Support for multiple organizations on the same infrastructure
Platform level host administration console built in
Unified user, tenant and license management at the
organization level
01
02
03
04
05
06
*All server products except Integration Service which is planned for future updates
10
10
Flexible Installation,
Easy Update
Install in cloud/on-prem Linux VM’s
or on-prem bare metal servers
Install all or any part of the UiPath automation platform*
Supported configurations include from air-gapped on-prem to
multi-organization hosting
Single, unified CLI-based install: Containerized UiPath
products, infrastructure, and software dependencies
“Kubernetes Inside” - K8s configured and optimized for
UiPath, with full UiPath end-to-end support.
01
02
03
*All server products except Integration Service which is planned for future updates
“Your AKS/EKS” – Leverage the standardized Kubernetes
distribution (AKS / EKS) in your IT environment
OR
11
Automation Suite Products
 Action Center (Actions and Processes)
 AI Center
 Apps
 Automation Hub
 Automation Ops
 Data Service
 Document Understanding
 Computer Vision
 Insights
 Orchestrator
 Automation Suite Robots
 Process Mining
 Task Mining
 Test Manager
Cross-product dependencies: https://docs.uipath.com/automation-suite/automation-suite/2022.10/installation-guide/cross-product-dependencies
12
Automation Suite – HW/SW Requirements
• Linux VMs:
• Minimum 3 VMs (Recommended number of nodes are n/2 + 1)
• OS : RHEL v8.3 to 8.8 (Root access required)
• CPU : 32
• RAM: 16 GiB RAM
• Disk: 2 TiB
• Microsoft SQL Server
• Version : 2016 to 2019.
• Standard or Enterprise editions
• CPU: 8
• RAM: 32 GiB
• Disk: 256 GiB
• Azure SQL Database, Azure SQL Managed Instance and Amazon Relational Database Service
• Load Balancer
• DNS
• TLS 1.2+
• Trusted TLS, token-signing and SQL connection encryption certificates
Capacity Planning: https://docs.uipath.com/automation-suite/automation-suite/2022.10/installation-guide/capacity-planning
13
Automation Suite – HW/SW Requirements Continued..
• Install tmux to access interrupted SSH session and observe the on-going installation process.
• Installation command: sudo yum install tmux
• Create as session: tmux new -s uipath_install
• List all session: tmux ls
• Connect to a specific session by name: tmux attach -t uipath_install
• RPM Packages on all nodes:
14
Automation Suite – HW/SW Requirements Cont..
Disk partitioning – Offline/Air-gapped
15
Automation Suite Pre-Configuration - Machine configuration
Check created disk
lsblk --all --list --output KNAME,SIZE,TYPE,PKNAME,NAME
Get disk mapping
LUN=0
echo "/dev/$(tree /dev/disk/azure/ | grep -w "slun${LUN}s" | awk -F/ '{print $NF}')"
(Repeat for all mounted disk)
Get Configuration scripts (Run on Machine with internet access and move to AS Node)
Linux: wget -O ~/configureUiPathDisks.sh https://download.uipath.com/automation-suite/2022.10.6/configureUiPathDisks.sh
Windows: https://download.uipath.com/automation-suite/2022.10.6/configureUiPathDisks.sh
Configure Disk on First Server
./configureUiPathDisks.sh --cluster-disk-name /dev/sda --etcd-disk-name /dev/sdc --data-disk-name /dev/sdb --
bundle-disk-name /dev/sdd --primary-server --install-type offline
Configure Disk on Other Servers
sudo ./configureUiPathDisks.sh --cluster-disk-name /dev/sda --etcd-disk-name /dev/sdc --data-disk-name /dev/sdb --
install-type offline
Configure the Objectstore Disk – On all nodes
./configureUiPathDisks.sh –install-type offline --ceph-raw-disk-name /dev/sdg (Explain - Azure SSD Issue for Objectstore &
Datadisk)
Ports
Open Port 22 for SSH & port 443 for accessing Automation Suite over Https. More details can be found at here.
16
Automation Suite Pre-Configuration – DNS Configuration
Configure the DNS for the common FQDN and the subdomains specific to each tool
Create privates DNS:
• Add 2 record sets as below:
• Name should be * & @
• IP Address should be IP of the NLB.
• Add virtual network link to the private DNS zone as below
• Name - communitysession.automationsuite.eastus.cloudapp.azure.com
• Subscription – Your_Subscription_Name
• Virtual Network should be the one used for NLB.
17
Automation Suite Pre-Configuration – SQL Database
By default, there is an option for the installer to create all the databases for you in the installation process. Below snapshot on DB
default names & corresponding connections –
SQL server user-id & password with db creator role is required.
18
Automation Suite Pre-Configuration – Certificates
The installation process generates self-signed certificates which is valid for 90 days. But it is recommended to update them with CA
certificates after installation.
Automation Suite requires three files at the time of installation-
• Server / TLS certificate file — the server’s public certificate file.
• Server / TLS key file — private key file for the server certificate.
• Certificate Authority Bundle — this is the Public Certificate of CA which is used to sign or issue the server certificate.
Server Certificates
• File format should be .pem, i.e., Base64 encoded DER certificate;
• Private key length should be at least 2048;
• Certificate key must be decrypted. If the key is encrypted, run the following command to decrypt it:
openssl rsa -in /path/to/encrypted/cert/key -out /path/to/decrypt/cert/key
• Certificate should have Subject Alternative Name (SAN) for all the DNS entries required for installing Automation Suite. Either a
wildcard certificate e.g. “*. communitysession.automationsuite.eastus.cloudapp.azure.com” or provide all DNS names in the
certificate.
References:
Manage server certificates
19
Demo Time!
Automation Suite Installation – Multi-Node Air-gapped
20
Automation Suite - Installation
• Connect to separate machine with internet access and download below required packages and move to first node of AS cluster:
Files: installUiPathAS.sh, sf-installer.zip, sf.tar.gz, sf-infra.tar.gz
Command: scp ~/installUiPathAS.sh ~/sf-installer.zip ~/sf-infra.tar.gz <username>@<node dns>:/uipath/tmp
• Create the installation folders and provide permissions
mkdir -p /opt/UiPathAutomationSuite/
chmod -R 777 /opt/UiPathAutomationSuite
• On main/first machine of the cluster:
mv /uipath/tmp/installUiPathAS.sh /uipath/tmp/sf-installer.zip /uipath/tmp/sf-infra.tar.gz
/opt/UiPathAutomationSuite
cd /opt/UiPathAutomationSuite
unzip ./sf-installer.zip -d .
chmod +x ./bin/jq
export PATH=${PATH}:/opt/UiPathAutomationSuite/bin
chmod -R 755 /opt/UiPathAutomationSuite
• Run the interactive installer to configure the installation options: (Creates the cluster_config.json file)
export BUNDLE_FILE="/opt/UiPathAutomationSuite/sf-installer.zip"
chmod +x ./installUiPathAS.sh
./installUiPathAS.sh
• At this stage cluster_config.json will be created with details provided by you.
• Copy the /opt/UiPathAutomationSuite folder from first node to all other nodes by running the following command:
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt
21
Automation Suite Installation – Cluster_Config.Json
Below snapshot on Cluster_Config file where the product components needs to be enabled as true.
22
Automation Suite Installation – Continued..
• Create and join all the machines to cluster:
Set up the First Machine:
> 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
Join the rest of the servers to the cluster:
> 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 /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-
agreement
• Finishing the installation: (Run on First/Primary node)
Check if the nodes were added properly to cluster:
sudo su
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes
Finish the installation by running below command:
cd /opt/UiPathAutomationSuite
./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --offline-bundle
/uipath/tmp/sf.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement
23
Automation Suite – Post Installation Activities
Enable kubectl
sudo su
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin
Accessing host administration: https://{CONFIG_CLUSTER_FQDN}
Organization: Host
Username: admin
Password: [Run the below command]
kubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity.hostAdminPassword}' |
base64 -d
Accessing Automation Suite: https://{CONFIG_CLUSTER_FQDN}
Organization: Default
Username: orgadmin
Password: [Run the below command]
kubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity.hostAdminPassword}' |
base64 -d
Accessing ArgoCD: https://alm.{CONFIG_CLUSTER_FQDN}
Username: admin
Password: [Run the below command]
kubectl get secrets/argocd-admin-password -n argocd -o "jsonpath={.data['password']}" | echo $(base64 -d)
24
Automation Suite – Post Installation Activities
Accessing Rancher: https://monitoring.{CONFIG_CLUSTER_FQDN}
Username: admin
Password: [Run the below command]
kubectl get secrets/rancher-admin-password -n cattle-system -o "jsonpath={.data['password']}" | echo $(base64 -d)
Accessing service database connection strings
• kubectl -n uipath get secret aicenter-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
• kubectl -n uipath get secret orchestrator-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
• kubectl -n uipath get secret automation-hub-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
• kubectl -n uipath get secret automation-ops-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
• kubectl -n uipath get secret insights-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
• kubectl -n uipath get secret platform-service-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
• kubectl -n uipath get secret test-manager-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
Configuring a client machine to access the cluster: This is mandatory to perform for all deployments, both evaluation/test and production.
Windows:
Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 communitysession.automationsuite.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 alm.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 objectstore.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 registry.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 monitoring.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force
Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 insights.communitysession.automationsuite.eastus.cloudapp.azure.com" –Force
MacOS or Linux:
sudo bash -c "echo "20.232.37.49 {FQDN}" >> /etc/hosts“
sudo bash -c "echo "20.232.37.49 alm.{FQDN}" >> /etc/hosts"
Similar to other sub-domains like objectstore, registry, monitoring & insights.
Thank You
26
Configure Disk on First Server
./configureUiPathDisks.sh --cluster-disk-name /dev/sda --etcd-disk-name /dev/sdc --data-disk-name /dev/sdb --
bundle-disk-name /dev/sdd --primary-server --install-type offline
27
Run the interactive installer to configure the installation options: (Creates cluster_config.json file)
./installUiPathAS.sh
28
Run the interactive installer to configure the installation options: (Creates cluster_config.json file)
./installUiPathAS.sh
29
Run the interactive installer to configure the installation options: (Creates cluster_config.json file)
./installUiPathAS.sh
30
Run the interactive installer to configure the installation options: (Creates cluster_config.json file)
./installUiPathAS.sh
31
Run the interactive installer to configure the installation options: (Creates cluster_config.json file)
./installUiPathAS.sh
32
Run the interactive installer to configure the installation options: (Creates cluster_config.json file)
./installUiPathAS.sh
33
Set up the first machine:
./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
34
Join the rest of the servers to the cluster:
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz
--offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement
35
Check if the nodes were added properly to cluster:
sudo su
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes
36
Finish the installation by running below command :
./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --offline-bundle /uipath/tmp/sf.tar.gz --
offline-tmp-folder /uipath/tmp --accept-license-agreement

Automation Suite PPT (2).pptx

  • 1.
  • 2.
    2 Speakers Ramkrishna Kadiya Technical AccountManager UiPath https://www.linkedin.com/in/ramkrishna-kadiya-a5386315/ Srikirti Raj Technical Account Manager UiPath https://www.linkedin.com/in/srikirti-raj/
  • 3.
  • 4.
    4 Events in theSeries ❍ Standalone UiPath Orchestrator Upgrade (IaaS/PaaS) [2022.4 to 2023.4] ❍ UiPath Insights (Looker) Upgrade ❍ Test Manager and Action Center Upgrade ☞ Automation Suite (Installation) ❍ Automation Suite (Upgrade)
  • 5.
    5 Agenda ❖ Automation Suite- Introduction ❖ Automation Suite - Products ❖ Automation Suite - HW/SW Requirements ❖ Automation Suite - Pre-Configuration (Machine, DNS, SQL, Certificates ) ❖ Automation Suite - Installation ❖ Automation Suite - Post Installation Activities ❖ Q&A
  • 6.
    6 The Cloud NativeUiPath Platform delivered as SaaS from UiPath Automation Cloud The Cloud Native UiPath Platform delivered as a single installation UiPath Platform products individually installed and managed Individual Products Automation Suite
  • 7.
    7 Individual Products UiPath Platformproducts individually installed and managed Automation Cloud The cloud native UiPath Platform delivered as SaaS from UiPath No installation required – start instantly, scale infinitely One-package install on-prem (including air-gapped) or in public cloud Linux VM, or in existing AKS/EKS cluster Available products installed on supported operating systems and physical/virtual hardware Automation Suite The cloud native UiPath Platform delivered as a single installation 7 All the products* Integrated High Availability, backup and scale management Integrated UiPath Portal suite experience, and shared suite functionality Unified admin experience for organization, tenant, user and license management *All server products except Integration Service which is planned for future updates
  • 8.
    The UiPath AutomationSuite Enterprise-ready Suite Flexible Installation, Easy Update Integrated Infrastructure & Cluster Management
  • 9.
    9 9 Enterprise-ready Suite All UiPathPlatform server products Multiple tenants per organization sharing a common user set and authentication setting Portal-based access to services and product availability parity with Automation Cloud Integration with other enterprise systems: Azure AD, AD and CyberArk RPA governance and security built in Support for multiple organizations on the same infrastructure Platform level host administration console built in Unified user, tenant and license management at the organization level 01 02 03 04 05 06 *All server products except Integration Service which is planned for future updates
  • 10.
    10 10 Flexible Installation, Easy Update Installin cloud/on-prem Linux VM’s or on-prem bare metal servers Install all or any part of the UiPath automation platform* Supported configurations include from air-gapped on-prem to multi-organization hosting Single, unified CLI-based install: Containerized UiPath products, infrastructure, and software dependencies “Kubernetes Inside” - K8s configured and optimized for UiPath, with full UiPath end-to-end support. 01 02 03 *All server products except Integration Service which is planned for future updates “Your AKS/EKS” – Leverage the standardized Kubernetes distribution (AKS / EKS) in your IT environment OR
  • 11.
    11 Automation Suite Products Action Center (Actions and Processes)  AI Center  Apps  Automation Hub  Automation Ops  Data Service  Document Understanding  Computer Vision  Insights  Orchestrator  Automation Suite Robots  Process Mining  Task Mining  Test Manager Cross-product dependencies: https://docs.uipath.com/automation-suite/automation-suite/2022.10/installation-guide/cross-product-dependencies
  • 12.
    12 Automation Suite –HW/SW Requirements • Linux VMs: • Minimum 3 VMs (Recommended number of nodes are n/2 + 1) • OS : RHEL v8.3 to 8.8 (Root access required) • CPU : 32 • RAM: 16 GiB RAM • Disk: 2 TiB • Microsoft SQL Server • Version : 2016 to 2019. • Standard or Enterprise editions • CPU: 8 • RAM: 32 GiB • Disk: 256 GiB • Azure SQL Database, Azure SQL Managed Instance and Amazon Relational Database Service • Load Balancer • DNS • TLS 1.2+ • Trusted TLS, token-signing and SQL connection encryption certificates Capacity Planning: https://docs.uipath.com/automation-suite/automation-suite/2022.10/installation-guide/capacity-planning
  • 13.
    13 Automation Suite –HW/SW Requirements Continued.. • Install tmux to access interrupted SSH session and observe the on-going installation process. • Installation command: sudo yum install tmux • Create as session: tmux new -s uipath_install • List all session: tmux ls • Connect to a specific session by name: tmux attach -t uipath_install • RPM Packages on all nodes:
  • 14.
    14 Automation Suite –HW/SW Requirements Cont.. Disk partitioning – Offline/Air-gapped
  • 15.
    15 Automation Suite Pre-Configuration- Machine configuration Check created disk lsblk --all --list --output KNAME,SIZE,TYPE,PKNAME,NAME Get disk mapping LUN=0 echo "/dev/$(tree /dev/disk/azure/ | grep -w "slun${LUN}s" | awk -F/ '{print $NF}')" (Repeat for all mounted disk) Get Configuration scripts (Run on Machine with internet access and move to AS Node) Linux: wget -O ~/configureUiPathDisks.sh https://download.uipath.com/automation-suite/2022.10.6/configureUiPathDisks.sh Windows: https://download.uipath.com/automation-suite/2022.10.6/configureUiPathDisks.sh Configure Disk on First Server ./configureUiPathDisks.sh --cluster-disk-name /dev/sda --etcd-disk-name /dev/sdc --data-disk-name /dev/sdb -- bundle-disk-name /dev/sdd --primary-server --install-type offline Configure Disk on Other Servers sudo ./configureUiPathDisks.sh --cluster-disk-name /dev/sda --etcd-disk-name /dev/sdc --data-disk-name /dev/sdb -- install-type offline Configure the Objectstore Disk – On all nodes ./configureUiPathDisks.sh –install-type offline --ceph-raw-disk-name /dev/sdg (Explain - Azure SSD Issue for Objectstore & Datadisk) Ports Open Port 22 for SSH & port 443 for accessing Automation Suite over Https. More details can be found at here.
  • 16.
    16 Automation Suite Pre-Configuration– DNS Configuration Configure the DNS for the common FQDN and the subdomains specific to each tool Create privates DNS: • Add 2 record sets as below: • Name should be * & @ • IP Address should be IP of the NLB. • Add virtual network link to the private DNS zone as below • Name - communitysession.automationsuite.eastus.cloudapp.azure.com • Subscription – Your_Subscription_Name • Virtual Network should be the one used for NLB.
  • 17.
    17 Automation Suite Pre-Configuration– SQL Database By default, there is an option for the installer to create all the databases for you in the installation process. Below snapshot on DB default names & corresponding connections – SQL server user-id & password with db creator role is required.
  • 18.
    18 Automation Suite Pre-Configuration– Certificates The installation process generates self-signed certificates which is valid for 90 days. But it is recommended to update them with CA certificates after installation. Automation Suite requires three files at the time of installation- • Server / TLS certificate file — the server’s public certificate file. • Server / TLS key file — private key file for the server certificate. • Certificate Authority Bundle — this is the Public Certificate of CA which is used to sign or issue the server certificate. Server Certificates • File format should be .pem, i.e., Base64 encoded DER certificate; • Private key length should be at least 2048; • Certificate key must be decrypted. If the key is encrypted, run the following command to decrypt it: openssl rsa -in /path/to/encrypted/cert/key -out /path/to/decrypt/cert/key • Certificate should have Subject Alternative Name (SAN) for all the DNS entries required for installing Automation Suite. Either a wildcard certificate e.g. “*. communitysession.automationsuite.eastus.cloudapp.azure.com” or provide all DNS names in the certificate. References: Manage server certificates
  • 19.
    19 Demo Time! Automation SuiteInstallation – Multi-Node Air-gapped
  • 20.
    20 Automation Suite -Installation • Connect to separate machine with internet access and download below required packages and move to first node of AS cluster: Files: installUiPathAS.sh, sf-installer.zip, sf.tar.gz, sf-infra.tar.gz Command: scp ~/installUiPathAS.sh ~/sf-installer.zip ~/sf-infra.tar.gz <username>@<node dns>:/uipath/tmp • Create the installation folders and provide permissions mkdir -p /opt/UiPathAutomationSuite/ chmod -R 777 /opt/UiPathAutomationSuite • On main/first machine of the cluster: mv /uipath/tmp/installUiPathAS.sh /uipath/tmp/sf-installer.zip /uipath/tmp/sf-infra.tar.gz /opt/UiPathAutomationSuite cd /opt/UiPathAutomationSuite unzip ./sf-installer.zip -d . chmod +x ./bin/jq export PATH=${PATH}:/opt/UiPathAutomationSuite/bin chmod -R 755 /opt/UiPathAutomationSuite • Run the interactive installer to configure the installation options: (Creates the cluster_config.json file) export BUNDLE_FILE="/opt/UiPathAutomationSuite/sf-installer.zip" chmod +x ./installUiPathAS.sh ./installUiPathAS.sh • At this stage cluster_config.json will be created with details provided by you. • Copy the /opt/UiPathAutomationSuite folder from first node to all other nodes by running the following command: scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt
  • 21.
    21 Automation Suite Installation– Cluster_Config.Json Below snapshot on Cluster_Config file where the product components needs to be enabled as true.
  • 22.
    22 Automation Suite Installation– Continued.. • Create and join all the machines to cluster: Set up the First Machine: > 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 Join the rest of the servers to the cluster: > 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 /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license- agreement • Finishing the installation: (Run on First/Primary node) Check if the nodes were added properly to cluster: sudo su export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin kubectl get nodes Finish the installation by running below command: cd /opt/UiPathAutomationSuite ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --offline-bundle /uipath/tmp/sf.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement
  • 23.
    23 Automation Suite –Post Installation Activities Enable kubectl sudo su export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin Accessing host administration: https://{CONFIG_CLUSTER_FQDN} Organization: Host Username: admin Password: [Run the below command] kubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity.hostAdminPassword}' | base64 -d Accessing Automation Suite: https://{CONFIG_CLUSTER_FQDN} Organization: Default Username: orgadmin Password: [Run the below command] kubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity.hostAdminPassword}' | base64 -d Accessing ArgoCD: https://alm.{CONFIG_CLUSTER_FQDN} Username: admin Password: [Run the below command] kubectl get secrets/argocd-admin-password -n argocd -o "jsonpath={.data['password']}" | echo $(base64 -d)
  • 24.
    24 Automation Suite –Post Installation Activities Accessing Rancher: https://monitoring.{CONFIG_CLUSTER_FQDN} Username: admin Password: [Run the below command] kubectl get secrets/rancher-admin-password -n cattle-system -o "jsonpath={.data['password']}" | echo $(base64 -d) Accessing service database connection strings • kubectl -n uipath get secret aicenter-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode • kubectl -n uipath get secret orchestrator-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode • kubectl -n uipath get secret automation-hub-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode • kubectl -n uipath get secret automation-ops-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode • kubectl -n uipath get secret insights-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode • kubectl -n uipath get secret platform-service-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode • kubectl -n uipath get secret test-manager-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode Configuring a client machine to access the cluster: This is mandatory to perform for all deployments, both evaluation/test and production. Windows: Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 communitysession.automationsuite.eastus.cloudapp.azure.com" -Force Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 alm.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 objectstore.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 registry.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 monitoring.communitysession.automationsuite.eastus.cloudapp.azure.com" -Force Add-Content -Path $env:windirSystem32driversetchosts -Value "`n20.232.37.49 insights.communitysession.automationsuite.eastus.cloudapp.azure.com" –Force MacOS or Linux: sudo bash -c "echo "20.232.37.49 {FQDN}" >> /etc/hosts“ sudo bash -c "echo "20.232.37.49 alm.{FQDN}" >> /etc/hosts" Similar to other sub-domains like objectstore, registry, monitoring & insights.
  • 25.
  • 26.
    26 Configure Disk onFirst Server ./configureUiPathDisks.sh --cluster-disk-name /dev/sda --etcd-disk-name /dev/sdc --data-disk-name /dev/sdb -- bundle-disk-name /dev/sdd --primary-server --install-type offline
  • 27.
    27 Run the interactiveinstaller to configure the installation options: (Creates cluster_config.json file) ./installUiPathAS.sh
  • 28.
    28 Run the interactiveinstaller to configure the installation options: (Creates cluster_config.json file) ./installUiPathAS.sh
  • 29.
    29 Run the interactiveinstaller to configure the installation options: (Creates cluster_config.json file) ./installUiPathAS.sh
  • 30.
    30 Run the interactiveinstaller to configure the installation options: (Creates cluster_config.json file) ./installUiPathAS.sh
  • 31.
    31 Run the interactiveinstaller to configure the installation options: (Creates cluster_config.json file) ./installUiPathAS.sh
  • 32.
    32 Run the interactiveinstaller to configure the installation options: (Creates cluster_config.json file) ./installUiPathAS.sh
  • 33.
    33 Set up thefirst machine: ./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
  • 34.
    34 Join the restof the servers to the cluster: sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement
  • 35.
    35 Check if thenodes were added properly to cluster: sudo su export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin kubectl get nodes
  • 36.
    36 Finish the installationby running below command : ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --offline-bundle /uipath/tmp/sf.tar.gz -- offline-tmp-folder /uipath/tmp --accept-license-agreement