V11-X installation Prerequisite check list

summary
Jun 1, 2019•Knowledge
Article Number
000001458
Title
V11-X installation Prerequisite check list summary
Summary
This article provides a summary of V11-X-Installation-Prerequisites
Instructions

*Applicable for AAE v11.x

Prerequisite:
• Product requirements/Prerequisites for installation: Please refer to Installation Guide

Hardware and OS Requirements:

https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/aae-architecture-
implementation/deployment-planning/requirements-server-hardware.html
https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/aae-architecture-
implementation/deployment-planning/requirements-operating-system-compatibility.html

User/Accounts:
• For installation, an account with local admin privileges is required. These credentials would be
used for CR & BI service logon. It can be either your local account (for non-AD control room)
or domain account (for AD control room) where the Web Server shall be hosted.
• Automation Anywhere now supports Multi-Forest Multi-Domain AD Integration provided
Transitive Trust is established for using AD users (Applicable from v11.3 onward)
• Identify the machines on which Control room and Client is to be installed
• Identify the service account to be used for AD authentication (recommended to have password never expire)
• Identify the users who will be using the clients - please make sure the machine login is possible
with the user accounts/service accounts to be used

Permissions:

Installation User
• Read/Write Permissions on the Installation location
• Read/Write Permissions on Public Documents (for Client) & ProgramData (for Control room)
• Read/Write Permissions on Application path (for client)
• Automation Anywhere Services should have full access rights to the Automation Anywhere
Folder (installation path)

• If any Antivirus is being used, we need to make sure the Automation Anywhere exe files are as an allowed file

Service Logon User

• Account used to run AAE services should have “Logon as Service”, “Allow Log on locally” and local Admin
(during install) rights during installation.
• If SQL connection is configured with Windows authentication, Service login account, and Installer user account need
to have db_owner rights for CR and BI database for pre-created DB, if DB’s for CR and BI are to be created by
Installer then Install user account needs to have Sysadmin rights on DB server instance and Sysadmin can be
revoked post installation.

Note: Its highly recommend to use a service account for service logon user since a password can set as never
expired. If a user account is used and password got changed/expired, Control Room services will be stopped and
need to change the password in all AAE services manually.

Ports:
• All ports to be opened as specified in Technical Specification Document (verify the ports are
open using Telnet command)
- 80 & 443: Web Server for Hosting Control Room (Jetty-based)
>To be opened on Client and Control Room machine
- 1433: MS SQL Server
>To be opened on a machine having the SQL Server
- 5432: PostgreSQL Server
>To be opened on a machine hosting Postgres database for Zoomdata
- 5672: Web Server for hosting v11 Website – for Multinode cluster
>To be opened on a machine having v11 Control Room
- 47500-47600: Web Server for hosting v11 Website – for Multi-node cluster
>To be opened on a machine having v11 Control Room
- 47100-47200: Web Server for hosting v11 Website – for Multi-node cluster
>To be opened on a machine having v11 Control Room
- 8091: Web Server for hosting v11 Website
>To be opened on a machine having v11 Control Room (BotInsight)
- 4530: AA Proxy Server used to communicate between client to respected plugins via TCP
socket for AAE Client, Editor or Player
>To be opened on Client machines
-3268 and 3269: If you are selecting the Active directory Authentication the 3268 port will use for LDAP connection. If
you have LDAPS then 3269 port will use for LDAPS
>To be opened on Control Room machines

1. LDAP or LDAPS URL should be of Global CatLog domain Controller of Forest root domain (URL with GC
FQHN – Global CatLog Fully qualified hostname)
2. Communication on port "3268 and 389" or "3269 and 636" should be allowed bidirectionally between
Control room server and the same global catalog domain controller server.
3. Username you provide should have at least read access on the domain.
4. Password should be set to never expire else there would downtime for every password expiration to
Credential in Credential Vault.

For detailed requirements, you can refer to below.

https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/aae-architecture-
implementation/firewall-rules.html
SQL Database:
• Require static port in SQL
• For Windows Authentication: Ensure the database has Sysadmin rights to create a database and its tables.
• If you are creating a dedicated SQL user or using an existing SQL user, provide the user Sysadmin privileges to
Control Room & BotInsight database.
• If databases are pre-created then account (Windows or SQL) need to have db_owner rights for both Control Room
& BotInsight.

PostgreSQL Database: (If applicable)

AA Control Room installer can install/create the PostgreSQL database during the Control Room installation process.
However, if you want to point the Control Room installation to remote PostgreSQL database then make sure the
below-given points
• Require static port in PostgreSQL
• AA Control Room installer will create the database on a remote PostgreSQL server. Make sure the user which you
will use to authentication the remote PostgreSQL that user should have full rights on full rights/ DB creator right so
the installer can establish the connection with remote PostgreSQL and create the database itself.

Note: PostgreSQL database should be created by the installer only. Manually created
PostgreSQL database will not work with Control Room installation.

Browser Settings:
• Add the web server URL to trusted sites in Internet Explorer
• In the browser, prompt for user credentials for Logon should be enabled (for testing purpose, in case there is an
issue while launching control room)

SVN:
• Automation Anywhere supports Visual SVN for Subversion

For HTTPS installation:

• You must have .pfx certificate (with passcode) to import certificate during installation
• Automation Anywhere supports .pfx certificate from a trusted authority with the private key in the format: ’[WS
Machine Host Name].[DomainName].com’
• Allowed host name (FQDN) in certificate file should be used during installation
• For multiple nodes (during HA), need to have certificate issues to Load Balancer DNS name and if individual URL to
be access need to have all nodes added to “Subject Alternative Name” field for a certificate.

Additional tools to have for troubleshooting and Management:

SQL Server Management studio (to access SQL database and manage)
PGAdmin 3 (to access Zoomdata and manage – for BI Dashboard)

Oracle: (Only applicable for AAE 11.3.1 onwards and supports Oracle 12C)

 DB and user (SID) should be pre-created before installation.

 Grant All System privileges to the user.
 JDBC driver “ojdbc7-12.1.0.2.0.jar” should be downloaded on CR machine.
  Port 1521 (default) or customer port used should be open for communication between CR and Oracle
server.

Authentication method:

 AD Authentication: For users and groups from one or more Active Directory forests/domains, to access the
Control Room, use a fully qualified host-name of Global Catalog (GC) server, listening on port 3268 - LDAP
(3269 in case of SSL - LDAPS).
o e.g. ldap://<GC_hostname>.<domainname>.com
o For LDAPs, need to gain Root domain certificate and to be installed on CR via command line.
 SSO Authentication: SAML2 IDP is required, the assertion URL should get the launch on CR servers.
 Hardware requirements
Updated 11/11/2019

EnterpriseExplore11.3.x

The Enterprise Control Room is deployed on servers in data centers. The Enterprise
client is deployed on any device that runs the supported operating system. The
minimum Automation Anywhere hardware requirements include: server, machine,
processor, RAM, disk storage, and network.

Note: Automation Anywhere does not provide any monitoring functions for repository such disk
space usage, memory or other alert mechanisms related to repository. There are commercial
tools available from other third party independent software vendors (ISV) who provide such
tools.

The installation wizard requires, for every server or machine their:

 IP addresses. Identify all the nodes (servers) IP addresses in the data center cluster
before installation. You provide these IP addresses during Enterprise Control
Room installation.
 Access hardware. To enable viewing the Automation Anywhere interface, provide:
o keyboard
o mouse or other pointing device
o monitor with 1366 x 768 or higher resolution
Enterprise Control Room server requirements
Enterprise Control Room must be installed on a server level machine. The server can
be a physical machine in your data center or an instance on a cloud platform.

Storage
Component server Processor RAM
(free disk spac
Enterprise Control Room Servers 8 core Intel Xeon Processor 16 GB500 GB

Enterprise Control Room on Amazon Web Services 8 core Intel Xeon Processor 16 GB500 GB

Enterprise Control Room on Google Cloud Platform 8 core Intel Xeon Processor 16 GB500 GB

Enterprise Control Room on Microsoft Azure 8 core Intel Xeon Processor 16 GB500 GB

Note: Supported IQ Bot for server RAM.

 On 16 GB RAM Enterprise Control Room servers, install IQ Bot on separate 16 GB

servers.
 On 32 GB RAM Enterprise Control Room servers, install IQ Bot on the same 32 GB
server.
 Enterprise client machine requirements
Enterprise client can be installed on any machine that meets the listed requirements.
The values listed are for the specific corresponding component. Bot Creator and Bot
Runner requirements are included in the Enterprise client requirements.

Storage
Component server Processor RAM
(free disk space)
Enterprise client on 3.5 GHz+ with 4 multi-cores or higher 8 GB or more per machine8 GB 1G
hardware machines.

Enterprise client on virtual 8 GB

4 virtual CPU (vCPU) or Logical 8 GB per virtual machine 1G
machines. Processor with 1.2 to 1.5 GHz speed
per vCPU
Virtual machine options:

 Citrix XenDesktop1
 VMware Horizon
Client version 4.8.0 or
later
 Windows multi-user
terminal servers
2 CPU per Automation Anywhere instance
Enterprise client on cloud 8 GB per Automation 8 GB 1G
service. Anywhere instance

Cloud provider options:

 Amazon Web Services

 Google Cloud Platform
 Microsoft Azure
Additional users on a multi-
2 CPU per additional user 4 GB per additional user No additional storage needed No
user system. net

Bot Creator and Bot Runner

3.5 GHz+ with 4 multi-cores or higher 8 GB or more per machineAdd 100 through 150 KB 1G
per Automation Anywhere script

Add 40 through 50 GB per long-

term MetaBot project
Note 1
To install the Enterprise client on a Citrix XenDesktop, install Citrix Receiver on the local
machine that you use to login to the Citrix XenDesktop.
RAM on Enterprise client machines:
 Enterprise client is a 32-bit application and multi-threaded, and it executes
multiple tasks in parallel including running bots.
 Add additional RAM to account for applications and services running on
the Enterprise client server, for example:
o Microsoft Office applications. Example: Excel
o Browsers. Example: Google Chrome
o Enterprise applications. Example: CRM, Oracle EBS, and SAP
o VDI infrastructure applications
o Anti-virus software
Storage disk space on Enterprise client machines:

 Automation Anywhere scripts average approximately 100-150 KB. Additional free

disk space is required to develop automation projects, since creates temporary
files like screen shots, server logs, and audit files, during the execution of the
automation scripts.
 Free space required increases with the project size. It is recommended to have
at least 40-50 GB of free disk space for each long term project.
 Increase storage space configuration after installation, as needed, depending on
product usage. For example, in MetaBot Designer, generating log files and logic
creation, require additional disk space later.
 Operating system and platform compatibility
Updated 11/05/2019

EnterpriseExplore11.3.x

Enterprise Control Room and Enterprise client both are installed on machines with
supported operating systems. The Enterprise Control Room and Enterprise client tables
list the supported Windows versions.

Both 32-bit and 64-bit OS versions are supported.

Enterprise Control Room operating system compatibility

Enterprise Control Room can be installed on machines running the following operating
systems.

Windows version Windows edition Automation Anywhere Enterprise version added

Server 2019 Standard and Datacenter Version 11.3.3

Server 2016 Standard and Datacenter Version 11.3

Server 2012 R2 Standard and Datacenter Version 11.3

Enterprise Control Room platform compatibility

Enterprise Control Room versions support the listed operating systems on a variety of
platforms:

Servers
See Hardware requirements. All listed operating systems and Enterprise Control
Room versions.
Cloud servers
AWS, Google Chrome, Microsoft Azure. All listed operating systems. See the table for
which Enterprise Control Room versions.

Cloud

Enterprise Control Room Version Google Cloud Platform Amazon Web Services Microsoft A

Version 11.3.3.1 Y Y Y

Version 11.3.3 Y Y Y
 Cloud

Enterprise Control Room Version Google Cloud Platform Amazon Web Services Microsoft A

Version 11.3.2.3 N Y Y

Version 11.3.2.2 N Y Y

Version 11.3.2.1 N Y Y

Version 11.3.2 N Y Y

Version 11.3.1.4 N N Y

Version 11.3.1.3 N N Y

Version 11.3.1.2 N N Y

Version 11.3.1.1 N N N

Version 11.3.1 N N N

Version 11.3 N N N

Enterprise client operating system compatibility

Enterprise client can be installed on machines running the following
operating systems.

Windows version Windows editions Automation Anywhere Enterprise vers

Server 20191,3 Standard and Datacenter Version 11.3.3

Server 20161,3 Standard and Datacenter Version 11.3

Server 20121 Standard Version 11.3

Server 2008 R2 Standard Version 11.3

Windows 101,2 Professional and Enterprise Version 11.3

Windows 8.1 and 8 Professional and Enterprise Version 11.3

Windows 7 SP1 Professional Version 11.3

Enterprise client components

Bot Creator and Bot Runner are compatible with the same operating systems
as Enterprise client.
(1, 2) Windows 10

 Automation using Apache Flex technology is not supported.

 Microsoft Edge Automation and triggers are not supported.
 (1) Windows Server 2012:
Automation using Apache Flex technology is not supported.
(1, 3) Windows Server 2016 and Windows Server 2019:

 Automation using Apache Flex technology is not supported.

 As of Automation Anywhere Version 11.3.2, this is no longer a limitation
on Enterprise client with Windows Server 2016.

For Windows Server 2016 on Automation Anywhere versions older than Version
11.3.2:

When installing Enterprise client, to enable the AutoLogin feature for a Logoff
scenario, ensure that the lock screen appears and that
the CTRL+ALT+DEL action does not appear on the lock screen. To ensure this:
o Enable the Interactive logon: Do not require Ctrl+Alt+Del option available
under Local Security Policy > Local Policies > Security Options.
o Disable the 'Do not display the lock screen' option available under Local
Group Policy > Computer Configuration > Administrative
Templates > Control Panel > Personalization
Enterprise client platform compatibility

Enterprise client versions support the listed operating systems on a variety

of platforms:

Physical machines
See Hardware requirements. All listed operating systems and Enterprise client versions.
Terminal servers
Using remote desktop (RDP). All listed operating systems and Enterprise client versions.
Virtual machines
Using Citrix XenApp, VMware Horizon Client. All listed operating systems. See the table
for which Enterprise client versions.
Cloud servers
Using AWS, Google Chrome, Microsoft Azure. All listed operating systems. See the
table for which Enterprise client versions.

Cloud

Enterprise client Version

Google Cloud Platform
Amazon Web Services
Microsoft Azure
VMware

Version 11.3.3.1 Y Y Y Y

Version 11.3.3 Y Y Y Y
 Cloud

Enterprise client Version

Google Cloud Platform
Amazon Web Services
Microsoft Azure
VMware

Version 11.3.2.3 N Y Y Y

Version 11.3.2.2 N Y Y Y

Version 11.3.2.1 N Y Y Y

Version 11.3.2 N Y Y Y

Version 11.3.1.4 N N Y Y

Version 11.3.1.3 N N Y Y

Version 11.3.1.2 N N Y Y

Version 11.3.1.1 N N N N

Version 11.3.1 N N N N

Version 11.3 N N N N

Auto Login compatibilityBots can Auto Login to the listed

operating systems and environments.