Server-Side Prerequisites and Requirements

The prerequisites differ depending on the Windows or Linux based system 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 2012 (R2), 2016 and 2019 RHEL 7.6 and RHEL 8.4
Database Setup SQL server 2012, 2016, 2017, 2019, Oracle server 12c, Oracle server 18c and Oracle server 19c SQL server 2012, 2016, Oracle server 12c and Oracle server 19c
 
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
Low Code

Microsoft JDBC Driver for SQL Server , Oracle JDBC Driver

 

Note: Refer AE-Engage Client Downloadable Software document (Automation use case specific pre-requisites section) for related details.

 NA

 

User Access and Configuration Prerequisites

Requirements     For Windows     For Linux
System Configuration Configure the machine as per the product guidelines document- AE-RPA-Engage Hardware Sizing.pdf, shared along with the product package.
  • 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> 
  • 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 Dir>/scripts/ae.sh
 Access Rights Windows Administrator rights of the given system on which server-side components are to be installed. NA
Network Configuration        
  • For clustered deployment, validate that all the required firewall rules are applied to allow communication on target ports for each component across systems. Refer AssistEdge 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. 
SQL Database 1433 Used for communication from UI-Backend server to Database server
Messaging 5672     Used for communication between UI-Backend server and Robot Farm
Messaging 25672, 4369 Used for communication from one to another UI-Backend server
TxnStore 9300 Used for communication from one to another UI-Backend server

 

 

Core Cognitive Engine/ML Prerequisites

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

 

NOTE: 

It is not applicable to Engage.

     

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 UIand Backend tier machines in cluster setup:
      • Open Command Prompt with Administrator rights and change the directory to AssistEdgeAutomation > scripts.
      • Run ae networkdrive mount command. Enter below required inputs:
        • Enter Drive Letter: <Mount drive letter>. Make sure that the drive letter is same on all the machines.
        • Enter Network Location: <Shared network drive path>
        • Enter Username: <Shared network username>
        • Enter Password: <Shared network password>
    • 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.x 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)

 

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 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. Refer Verify/_Save_Certificates_in_PEM/_Base_Format Format to know more.
  • 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 AssistEdgeAutomation > data > License folder.
  • Post installation, navigate to AESite > License Manager (refer License Manager section 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 a deployment instances 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.
 

EnterprisePersonal

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.
Engage Number of Named Users OR Number of Concurrent Users License
 

The Number of Named Users License enforces the number of users who have the Engage or Web Engage access accesses in the Configuration > Manage Role > Specify Role Access > Assisted Automation screen..

The Number of Concurrent Users License enforces the number of Engage 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.

Lowcode Number of Users The Number of Users License enforces the number of users who have the Lowcode Orchestrate access.
By default, 3 users get free trial licenses; however, if the number of users increases beyond 3, the Number of Users license is required.

 

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 3.19.80
    1. Download from here.
    2. Extract/unzip the downloaded package
    3. Access \lib\net40 folder, locate and copy Oracle.EntityFramework.dll file
    Oracle.ManagedDataAccess     2.19.80
    1. Download from here
    2. Extract/unzip the downloaded package
    3. Access \lib\net40 folder, locate and copy Oracle.ManagedDataAccess.dll file 

     

  2. Create a new folder named Oracle under data folder at AssistEdgeAutomation > data
    1. Save both the DLL files at AssistEdgeAutomation > data > Oracle folder that you created above.
  3. Download the Oracle Instant Client: 
    1. Extract/unzip the downloaded package 
    2. Access instantclient_19_12 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 (AssistEdgeAutomation > data > Oracle) created above.
    4. Place the copied content of the instantclient_19_12 folder at AssistEdgeAutomation > data > Oracle > instantclient folder.
   

 

NOTE: 

Refer AE Commands sections to know more about the AE commands.