Server-Side Prerequisites and Requirements

The prerequisites differ depending on the Windows or Linux based server used for the installation. Below is the list of prerequisites required for the server-side configuration and installation:


Software Requirements

Requirements For Windows For Linux
Operating System Windows 2016 and 2019 RHEL 8.4
Database Setup SQL server, 2016, 2017, 2019, 2022, Oracle server 18c, Oracle server 19c and Oracle server 21c, Postgres 14.0 and 15.0 and Azure SQL Server enabled with System-Assigned Managed Identity
File Archiver

7-zip (any other archiver which supports extraction of long file paths)

CAUTION:  

 7-zip or similar archiver is required to perform extraction of installation folder on the Windows system as default decompression of Windows fails to properly unzip the files. Incorrect extraction leads to failure of installation.

NA

 

User Access and Configuration Prerequisites

Requirements     For Windows     For Linux
Server Configuration

Configure the machine as per the product guidelines in Hardware Sizing.

The server machine where the build is installed should be able to connect with the database server.
Server Configuration NA
  • In the /etc/security/limits.conf file, add the entry: 
    assistEdge – nofile 65535

    NOTE:

    		 You can set a higher nofile number based on your requirement.
  • In the /etc/sysctl.conf file, add/update the entry: 
    vm.max_map_count=262144
Configuration NA
  • Create new group – assistEdge:
    sudo groupadd assistEdge

    NOTE:

    		 assistEdge is case sensitive and must be used as mentioned in this document.
  • Assign the AssistEdge group to the user 
    sudo usermod -a -G assistEdge <username>
  • Change the installation directory group to:
    chgrp -R assistEdge <Installation Directory>/AssistEdgeAutomation
  • Create ae alias:
    • Create a file ae.sh (provide execute permission to this file) in the /etc/profile.d folder and add the entry:
      Alias ae=<Installation Directory>/AssistEdgeAutomation/scripts/ae.sh
Access Rights Windows Administrator rights of the given server on which server-side components are to be installed. NA
Component Specific Requirement NA Download libicu Linux package from here and install it.
Network Configuration      
  • For single server deployment, validate that the firewall rule is applied for default port 8443 to allow UI to backend server communication.
  • For clustered deployment, validate that all the required firewall rules are applied to allow communication on target ports for each component across servers. See AssistEdge RPA Deployment Model section for sample port configurations.
  • Following ports to remain open if you are using the default network configuration: 

 

Component      Port     Description
UI/Backend    8443 Used for communication with UI-Backend server. 
Database 1433/1521/5432 Used for communication from the AssistEdge server to the database server. Port 1433, 1521, 5432 are the default ports for SQL, Oracle, and Postgres database servers respectively.
Messaging 5672     Used for communication with the messaging component.
Messaging 25672, 4369 Used for communication with the messaging component between the servers.
TxnStore 9300 Used for communication with the txnstore component between the servers.
Cluster 8445 Used for communication between servers within the cluster

 

 

Core Cognitive Engine/ML Prerequisites

This section is relevant only if you wish to use Baked In ML use cases for running the AssistEdge RPA platform.

     

Requirements     Description 
Access to Shared Network Drive
  • In case of cluster setup, it is required to use network drive to store Baked In ML training data and model.
  • In case network drive is not present follow the below mentioned steps:
    • For Windows: It can be created using below steps. Below command creates network drive mount on all UI and Backend tier machines in cluster setup:
      • Open Command Prompt with Administrator rights and change the directory to <Installation Directory>/AssistEdgeAutomation > scripts.
      • Run ae networkdrive mount command. For more information, see Command Guide.
    • For Linux: Mount a shared drive at a common location on all servers in the cluster. The assistEdge group created above must have access to this drive. Refer Mounting Shared Drive section to know how to mount the shared drive in Linux.
  • Make sure that the mounted network drive folder has read/write permissions.
Tensorflow Support Core engine uses Tensorflow 2.9.1 which mandatorily requires AVX supported CPU. Check the version of CPU and validate if it supports AVX. 
  • If AVX is supported:
    • For Windows: Install Microsoft Visual C++ 2015 Redistributable Update 3 (if not already present).
    • For Linux: Not Applicable.
  • If AVX is not supported, get a CPU with AVX support irrespective of the type of OS you are using for the installation (Windows or Linux).

NOTE: 

 To verify if your CPU supports AVX, you need to visit the manufacturer’s website. With the help of model number, you can find out whether your CPU model supports AVX or not.

 

 

SSL Certificates and Licensing Prerequisites

Requirements   Description (For Windows and Linux)
SSL Certificates
  • To enable HTTPS protocol during installation, save the below mentioned key and certificates at <Installation Directory>/AssistEdgeAutomation > data > Certificates folder.
  • Required Commercial Certificates are:
    • rootCert.crt (CA/Root certificate)
    • server.key (Server key)
    • server.crt (Server certificate)
    • inter.crt (Intermediate certificate, if any)
  • .crt files should be stored in PEM/ Base64 format. For more information, see Verify/ Save Certificates in PEM/ Base64 Format.
  • In case you do not have the commercial certificates, you can generate self-signed certificate during installation itself. However, it is not recommended to use the self- signed certificates.
  • Refer SSL Certificates section to know more about certificates such as how to obtain certificates, how to save/update key and certificates post installation and so on.
 License
  • Post installation, copy the server license file provided by EdgeVerve to <Installation Directory>/AssistEdgeAutomation > data > License folder.
  • Post installation, navigate to Admin Module > License Manager (refer License Manager) setion to know how to upload License files) and upload below mentioned License file that are to be used as per the functionality:

 

Offering    License Required     Description
RPA  Number of Robots License OR
Number of Concurrent Robots License		 The Robots License enforces the number of robots that can be created in a deployment.
The Number of Concurrent Robots License enforces the number of robots that can be created in deployment servers that can be used at the same time. User can create multiple robots. However, they can run the robots only as per the number defined in the license.  The license term can be Perpetual or Time based. 
Either one of these licenses is required for using unattended robots. Combination of both the licenses is not allowed in same deployment.
 
LowCode Number of Users The Number of Users License enforces the number of users who have the LowCode Orchestrate access.
By default, 2 users get free trial licenses; however, if the number of users increases beyond 2, the Number of Users license is required.

Enterprise Personal Assistant

 Number of Named Users OR Number of Concurrent Users License The Number of Named Users License enforces the number of users who have the Enterprise Personal Assistant access in the Configuration > Manage Role > Specify Role Access > Assisted Automation screen.
The Number of Concurrent Users License enforces the number of Attended Automation instances that can be used at the same time.
Any of the above two licenses are required. Combination of both the licenses is not allowed in same deployment.
Decision Workbench Number of Named Users The Number of Named Users License enforces the number of users who have either or combination of the SME L1, SME L2, and Manager accesses in the Decision Workbench section of Configuration > Manage Role > Specify Role Access > Assisted Automation screen.

 

Oracle Database Prerequisites

Requirements    Description
Oracle Database Setup

Follow the below steps if Oracle database is used:

  1. Download the below listed DLL files from the link given below:
     
    Component      Version   Description
    Oracle.EntityFrameworkCore 6.21.90
    1. Download from here.
    2. Extract/unzip the downloaded package.
    3. Access \lib\net6.0 folder, locate and copy Oracle.EntityFramework.dll file.
    Oracle.ManagedDataAccess     3.21.100
    1. Download from here.
    2. Extract/unzip the downloaded package.
    3. Access \lib\net2.1 folder, locate and copy Oracle.ManagedDataAccess.dll file.

     

  2. Create a new folder named Oracle under data folder at <Installation Directory>/AssistEdgeAutomation > data.
  3. Save both the DLL files at <Installation Directory>/AssistEdgeAutomation > data > Oracle folder that you created above.
  4. Download the Oracle Instant Client: 
    1. For Windows: Download from here.
    2. For Linux: Download from here.
      1. Extract/unzip the downloaded package 
      2. Access instantclient_21_10 folder (the version of this folder can be different) and copy the entire content from within the folder.
      3. Create a new folder named instantclient under Oracle folder (<Installation Directory>/AssistEdgeAutomation > data > Oracle) created above.
      4. Place the copied content of the instantclient_21_10 folder at <Installation Directory>/AssistEdgeAutomation > data > Oracle > instantclient folder.

 

 

NOTE: 

Refer AE Commands to know more about the AE commands.