12/15/2018

Automation Anywhere Enterprise Control

Room Installation Guide, Version 11.3.1
Contents

Installing Control Room.............................................................................................................................. 3

Upgrading to Version 11.3.1............................................................................................................... 3
First Time Installation.......................................................................................................................... 3
Automation Anywhere Control Room Express Installation................................................................. 4
Custom Installation............................................................................................................................ 12
Install Automation Anywhere Enterprise on Microsoft Azure............................................................ 28
Prerequisite configuration for Automation Anywhere Enterprise on Azure clusters................28
Begin Control Room installation on Azure............................................................................. 30
Customize Control Room installation on Azure clusters........................................................ 31
Configure Azure clusters for the Control Room..................................................................... 40
Prerequisites...................................................................................................................................... 43
Silent Installation............................................................................................................................... 45
Remove or Repair Installation...........................................................................................................50
First Time Control Room Configuration............................................................................................ 51
Express Control Room Configuration.....................................................................................52
Custom First Time Control Room Configuration.................................................................... 53
Configure Control Room for Single Sign-On..........................................................................58
Post-upgrade configuration of Active Directory...................................................................... 59
Working with SQL Servers................................................................................................................60
Automation Anywhere Windows Services.........................................................................................61
Configure Control Room for HTTPS Self-Signed Certificate............................................................ 63
Import Certificate for HTTPS..................................................................................................64
Import a CA Certificate...........................................................................................................65
Index............................................................................................................................................................ 67
 Automation Anywhere - Installing Control Room

Installing Control Room

Reference the topics below to install Control Room.

Upgrading to Version 11.3.1

To upgrade to 11.3.1 from an existing 11.x Control Room version do not uninstall the previous 11.x Control
Room.
Follow the steps mentioned below:
1. Run the 11.3.1 Control Room installer.

Note: If you are using LDAP authentication on multiple nodes stop the Control Room Service and
Control Room Caching services on all the nodes in the cluster environment prior to running the
installer.

2. Follow the steps for installing 11.3.1 as mentioned in First Time Installation.
3. Provide the configuration parameters on each screen of the installer.
Ensure that the configuration parameters are the same as provided in the previous 11.x installation. If
you are not sure on the exact configuration parameter values, refer to the ‘aae-installsummary.html’
file available in the 11.x installation folder.

Note: If you provided incorrect parameters not matching the previous 11.x installation, the upgrade
will not be successful and you have to uninstall 11.3.1 and reinstall with the correct parameters.

If you are using LDAP authentication on multiple nodes, refer to Post-upgrade configuration of Active
Directory for steps to change the active directory configuration.

First Time Installation

To install Version 11.3.1 , simply run the Version 11.3.1 Control Room set-up as detailed here.

Installing Automation Anywhere Enterprise Control Room

Use the Automation Anywhere Enterprise setup file to install Automation Anywhere Control Room. During
the installation process, any software dependencies or prerequisites that might be missing, are also
installed.

Note: Run the setup and install Automation Anywhere Control Room in Run as administrator mode.

There are two modes of installing Control Room:

Express Express mode automatically installs all components

with the default settings.
Custom Custom mode allows administrator to configure and
install as per specific requirements.

© 2018 Automation Anywhere. All rights reserved. 3

 Automation Anywhere - Installing Control Room

Express Installation

The Express installation sets up Control Room using default values and automatically configures the
required parameters for different components, such as the database, services, PostgreSQL (metadata
database), and Bot Insight components. Express installation enables Control Room administrator to create
Non-Active Directory users.

Note:
1. Express install can be performed quickly for showcasing a demo to customers as it allows the
installation quickly as possible.
2. This method of installation is recommended for a non-production environments only.
3. Before installation, save all work and close all open applications.

Default Parameters

Note: The database defaults to SQL Server for both Control Room and Bot Insight. Oracle Database is
allowed only for Custom Installation.

The following parameters are installed by default:

• SQL Server
Parameter Default value

SQL database instance SQLEXPRESS

Authentication type Windows authentication
Control Room database CRDB-NEW
Bot Insight databases BIVisualization, BIVisualization-keyset, BIVisualization-
scheduler, BIVisualization-upload, and BotInsight
Port 1433

Automation Anywhere Control Room Express Installation

Install Automation Anywhere Control Room in Express mode.
To install Automation Anywhere Control Room in Express mode, perform the following steps:
1. Extract all files from Automation Anywhere Enterprise_Setup.zip file.
2. Run the AAE_MSSQL_Express_2014SP1.exe to install the default SQL Server instance that is
required for Express mode of installation.

Note: This is a pre-requisite to run Version 11.3.1 Control Room installer. The database defaults to
SQL Server for both Control Room and Bot Insight if installed in express mode.

© 2018 Automation Anywhere. All rights reserved. 4

 Automation Anywhere - Installing Control Room

3. Double click the Automation Anywhere Enterprise setup file.

a. The installer first checks whether Visual C++ 2013 Redistributable is installed or not. If not, the
installer prompts you to install the same:

• Click Install. This automatically installs the component.

b. The installer then checks whether Microsoft OLEDB Driver for SQL Server is installed. If not, the
following message is displayed:

• Click Install. This automatically installs the component.

• Once complete, the Automation Anywhere Enterprise setup wizard Welcome page is
displayed.

c. If the installer detects an unsupported Operating System version, the following message is shown:

© 2018 Automation Anywhere. All rights reserved. 5

 Automation Anywhere - Installing Control Room

• Click Yes to continue with the installation. This launches the Welcome page.
• Click No to exit the installation. This launches the Finish page.

d. The installer now checks whether another version of Control Room is installed.
• If the installer detects another version of Control Room, the following message is shown:

• Click OK.
• This launches the Finish page. Uninstall the previous version and run the setup again.

4. Click Next.
The License Agreement page is displayed.

© 2018 Automation Anywhere. All rights reserved. 6

 Automation Anywhere - Installing Control Room

5. Accept the licensing agreement and click Next.

The Installation Type Preference page is displayed.

6. Select the Express option and click Next.

The Database Server page is displayed:

7. Optional: Set the database port

By default, this is set to 1433.

Note: To connect to the database on the custom port, specify the value in the Database Port text-
box.

8. Set connection, authentication, and databases.

Windows authentication This option is selected by default. This allows for
connecting to the SQL Server using Windows
authentication.

Note: If user selects Windows Authentication, then the user running the installer is used to test that
the database exists, and create it if necessary, and grant db_owner to the service account user (NT
Authority/System).

SQL Server authentication Select this option to use SQL server

Authentication to connect to the database.

© 2018 Automation Anywhere. All rights reserved. 7

 Automation Anywhere - Installing Control Room

Provide correct username and password for SQL

Authentication.

Note: On invalid credentials, following message is shown:

Name of Control Room database The default name is CRDBNEW. Alternatively,

type the name for the Control Room database.
Name of Bot Insight database The default name is BotInsight. Alternatively,
type the name for the Bot Insight database. This
database is used to store the Bot Insight data.
If the database (Control Room and or Bot Insight)
does not exist, the installer will create one
automatically.

Attention:
• If the database names are blank, have spaces, or include % (percent character), you are
shown an error:

Hence, for SQL Server database names it is recommended to restrict the names to
alphanumeric, period (.), dash (-), and underscore (_).

9. Click Next
The Ready to Install the Program page is displayed.

© 2018 Automation Anywhere. All rights reserved. 8

 Automation Anywhere - Installing Control Room

10. Click Install

Allow the installation to process complete.

© 2018 Automation Anywhere. All rights reserved. 9

 Automation Anywhere - Installing Control Room

11. Click Finish

Once the installation is complete, the installation wizard provides you with the following options:
• Launch Automation Anywhere Enterprise
Launches Control Room in your default browser with the Configure Control Room settings page
displayed. For more information, refer Automation Anywhere Control Room User guide.
• Show the installer settings
Select this option to open the aae-installsummary.html file. By default, this is located at C:
\Program Files\Automation Anywhere\Enterprise\. Use this file to view a summary of
the installation. It provides the following details:

© 2018 Automation Anywhere. All rights reserved. 10

 Automation Anywhere - Installing Control Room

© 2018 Automation Anywhere. All rights reserved. 11

 Automation Anywhere - Installing Control Room

Custom Installation
Install Automation Anywhere Control Room in Custom mode.
Custom Installation allows choice of settings. The customizations that can be made using this setup
method include:
• Select a destination folder to install the application.
• Type the system IP addresses for cluster configuration.

Note: All nodes to be configured for Cluster IP should be available for configuration in advance of
installation. Also, provide the same list of IPs in all the nodes participating in the cluster when you install
Control Room in these nodes.
• Option to provide a custom certificate for configuring the application Transport Layer Security (TLS).
• Option to provide CA certificate for secure connection to , mail servers and LDAP servers.
• Option to configure service credentials using local system account or user account.
• Select the database server type - SQL or Oracle
• Select method of authentication – Windows or SQL Server Authentication.
• Option to use Microsoft SQL Server or Oracle Server as default database for Control Room and Bot
Insight databases.

Note: If selecting Oracle Server, ensure Oracle database users are created before running the Control
Room installation.
• Option to select SQL Database Server or PostgreSQL Server for Bot Insight metadata
• If PosgresQL Server selected for BI metadata, an option to install a new instance or connect to an
existing PostgreSQL server on another Control Room.

1. Extract all files from Automation Anywhere Enterprise_Setup.zip file.

© 2018 Automation Anywhere. All rights reserved. 12

 Automation Anywhere - Installing Control Room

2. Double click the Automation Anywhere Enterprise setup file.

a. The installer first checks whether Visual C++ 2013 Redistributable is installed or not. If not, the
installer prompts you to install the same:

• Click Install. This automatically installs the component.

b. The installer then checks whether Microsoft OLEDB Driver for SQL Server is installed. If not, the
following message is displayed:

• Click Install. This automatically installs the component.

• Once complete, the Automation Anywhere Enterprise setup wizard Welcome page is
displayed.

c. If the installer detects an unsupported Operating System version, the following message is shown:

© 2018 Automation Anywhere. All rights reserved. 13

 Automation Anywhere - Installing Control Room

• Click Yes to continue with the installation. This launches the Welcome page.
• Click No to exit the installation. This launches the Finish page.

d. The installer now checks whether another version of Control Room is installed.
• If the installer detects another version of Control Room, the following message is shown:

• Click OK.
• This launches the Finish page. Uninstall the previous version and run the setup again.

3. Click Next.
The License Agreement page is displayed.

© 2018 Automation Anywhere. All rights reserved. 14

 Automation Anywhere - Installing Control Room

4. Accept the licensing agreement and click Next.

The Installation Type Preference page is displayed.

5. Select the Custom option and click Next.

The Destination Folder page is displayed. By default, the destination folder is C:\Program Files
\Automation Anywhere\Enterprise\.

© 2018 Automation Anywhere. All rights reserved. 15

 Automation Anywhere - Installing Control Room

6. To make changes to the destination folder, click Change..., supply new destination folder name, and
click OK.

Note: It is NOT recommended to install the application directly in the root directory, for instance
C:\Automation Anywhere\Enterprise\. Create or select a folder for installation instead, for
instance C:\Program Files\Automation Anywhere\Enterprise\.

7. Click Next
The Cluster Configuration page is displayed.

8. Enable Cluster Setup

Note: The option is enabled only if the machine on which the setup is being run has local IP
addresses configured. If the machine does not have local IP addresses, it is disabled as shown:

© 2018 Automation Anywhere. All rights reserved. 16

 Automation Anywhere - Installing Control Room

9. Enter the IP addresses of the nodes for the cluster.

a. Use a comma (,) to specify more than one IP address. For example, 192.161.1.1, 192.161.1.2,
192.161.1.3 and so on.

1. If you Enable Cluster Setup and do not type an IP, the following message is shown:

2. If you supply invalid numbers or characters, the following message is shown:

b. On correct input of cluster IP's, you will be prompted to input the local ip:

c. Select the IP.

If multiple local IP's are configured on the machine, select the IP on which Control Room is
installed as it will be used to access the Control Room from other nodes.

Caution: Once configured, you cannot add or remove nodes from the list of IPs

Note: If you want to install the Control Room without a cluster, do not enable cluster setup.
10. Click Next.

© 2018 Automation Anywhere. All rights reserved. 17

 Automation Anywhere - Installing Control Room

11. The TLS Configuration page is displayed wherein you can either:
• Generate a Self-Signed Certificate
When the Self-Signed Certificate option is enabled the installer will generate a unique private key
and a self-signed certificate for the :

• Import a Certificate:
You must import a certificate if successful certificate validation is required for accessing the Control
Room.
To import a custom certificate, clear the Self-Signed Certificate option. This will enable Certificate
Path to browse and import certificate.

Note: The certificate file must be in PKCS12 format.

Supply the following:

• Certificate Path — Click the Browse button to import the certificate.
• Private Key Password — Type the password for the private key.

Warning: Password Limitation Any usage of special character "@" at the beginning of
the password will fail to import the certificate file. Do not use "@" in passwords.
• Webserver Port — Type the Webserver port – either HTTP or HTTPS. If the port is already
assigned, you are shown:

© 2018 Automation Anywhere. All rights reserved. 18

 Automation Anywhere - Installing Control Room

Attention: The port validation message is also displayed when you add 8080 for
Webserver and if that is already in use for Control Room license service. Use a different
unassigned port in above cases.
• Enable Force HTTP traffic to HTTPS — To redirect all HTTP port requests to HTTPS. To
access the Control Room via HTTPS using the generated self-signed certificate.
• Ensure the port number is different for both.

12. Click Next.

The Service Credentials page is displayed.

13. Clear the Local System Account option to add credentials manually to configure the domain account.
The Service Credentials page allows you to specify the account that will be used to run
all Windows services that are created by Automation Anywhere Enterprise installer.

By default, the Local System Account is selected. To run Automation Anywhere services as a different
user instead of a Local System account, clear the Local System Account check box and type the user
name and password for the domain account.

Note:
• If you do not enter the correct Windows domain credentials which shall not be validated on this
screen, the Automation Anywhere services will not run and the Control Room will fail to launch.
• The user running the installer needs system administrator role.
• The user credentials provided during install time for service could be restricted to launch
PowerShell scripts and database table creation could potentially fail.
• If using remote SQL server for creating database then, the combination of Local System Account
for Service Credentials and Use Windows Authentication for SQL Connection is not supported.
• A username and password must be specified for services instead of local system service
account when using a remote database server.
• The username and password specified is used to create tables and for the control room
processes to access the database.
• Refer Matrix for creating database, tables, and services in Working with SQL Servers

14. Click Next.

© 2018 Automation Anywhere. All rights reserved. 19

 Automation Anywhere - Installing Control Room

15.
Select the database type for Control Room and Bot Insight.
• Microsoft SQL Server
To select this database type, an instance of SQL Server should be already configured.

•
Oracle
To configure Control Room and Bot Insight database on Oracle instance, select this option and
browse the required JDBC driiver on your local machine.

Note: You cannot proceed with the installation without the JDBC Driver.

The Control Room and Bot Insight must use the same database type.
16. Click Next.
The Database Server page is displayed

© 2018 Automation Anywhere. All rights reserved. 20

 Automation Anywhere - Installing Control Room

17. Set connection, authentication, and databases.

• Database Server
This page is launched if you select SQL Server for configuring your database

Note:
• If possible, do not set the value for Database Server as localhost, or the Secure
Connection to the database does not work.
• For Azure installations, the database names for Control Room and Bot Insight must be the
same, or installation fails.
• Click the Browse button to select the SQL server instance where the Control Room database
will be created.

Alternately, type a database server name or select one from the list .

Database Port To connect to the database on custom port,

specify that as a value for the Database Port
The default database port is 1433.
Use Secure Connection Select Use Secure Connection to use CA
certificate as specified.

Note: The host name in certificate and

database connection must be same.

Certificate This option is enabled when you select secure

connection. Browse to select a CA certificate.
Refer section on Import a CA Certificate for
details on how to import this certificate using the
command line.

© 2018 Automation Anywhere. All rights reserved. 21

 Automation Anywhere - Installing Control Room

Windows authentication This option is selected by default. This allows

for connecting to the SQL Server using
Windows authentication.

Note: If user selects Windows Authentication,

then the user running the installer is used
to test that the database exists, and create
it if necessary, and grant db_owner to the
service account user (NT Authority/System).
Refer matrix for creating database, tables, and
services in Working with SQL Servers

SQL Server authentication Select this option to use SQL server

Authentication to connect to the database.
Provide correct username and password for
SQL Authentication.

Note: On invalid credentials, following

message is shown:

Name of Control Room database Enter the name for the Control Room database.
Name of Bot Insight database Type the name for the Bot Insight database.
This database is used to store the Bot Insight
data.

Note: If the database (Control Room and or

Bot Insight) does not exist, the installer will
create one automatically.

Attention: If the database names are blank, have spaces, or include % (percent
character), you are shown an error:

© 2018 Automation Anywhere. All rights reserved. 22

 Automation Anywhere - Installing Control Room

Hence, for SQL Server database names it is recommended to restrict the names to
alphanumeric, period (.), dash (-), and underscore (_).

•
Oracle Server
This page is launched if you select Oracle Server for configuring your database

Provide the following details,

Database Server Provide the server hostname details. The

users should have been created in the Oracle
database by the system admin before running
the installation.

Note: Refer article on how to create users in

Oracle

Database Port The default database port is 1521. You can

connect using a custom port as defined by the
system admin.
Control Room Database Username Control Roomdatabase username that was
created initially by the system admin.
Control Room Password Password of the Control Room database user.
Bot Insight Database Username Bot Insight database username that was
created initially by the system admin.
Bot Insight Password Password of the Bot Insight database user.
Use Secure Connection Select Use Secure Connection to use CA
certificate as specified.

Note: The host name in certificate and

database connection must be same.

Certificate This option is enabled when you select secure

connection. Browse to select a CA certificate.
Refer section on Import a CA Certificate for
details on how to import this certificate using the
command line.

18. Click Next.

© 2018 Automation Anywhere. All rights reserved. 23

 Automation Anywhere - Installing Control Room

19.
Opt for a database to store metadata for Bot Insight
• PostgreSQL Server
You can opt to select PostgreSQL Server if you want a separate database server for storing the
metadata:

• Microsoft SQL Server

Note: Microsoft SQL Server is selected as the default metadata database type

20. On the Bot Insight PostgreSQL Configurations page, select the check box to install PostgreSQL .
• Install PostgreSQL v9.5.10. By default, this check box is selected.
• Clear this option if the PostgreSQL is already installed and supply the following:
Hostname Enter the hostname for the PostgreSQL Server.
The default name is localhost.
Port Enter the port number for the PostgreSQL
Server. The default Port number is 5432.
Database Enter the database name that will be used for
Bot Insight. By default, the database name is
zoomdata.
Use Secure Connection Select this option if your PostgreSQL database
uses a secure connection.
Username Enter the user name for the PostgreSQL
database. The default username is postgres.

© 2018 Automation Anywhere. All rights reserved. 24

 Automation Anywhere - Installing Control Room

Password Enter the password for the PostgreSQL

database.
Confirm Password This is only visible when the Install Postgres
option is selected.

Note: If Install PostgreSQL option is selected, the Hostname and Use Secure Connection fields are
disabled and set to default values.

21. Click Next

The Ready to Install the Program page is displayed.

22. Click Install

Allow the installation to process complete.

© 2018 Automation Anywhere. All rights reserved. 25

 Automation Anywhere - Installing Control Room

23. Click Finish

Once the installation is complete, the installation wizard provides you with the following options:
• Launch Automation Anywhere Enterprise
Launches Control Room in your default browser with the Configure Control Room settings page
displayed. For more information, refer Automation Anywhere Control Room User guide.
• Show the installer settings
Select this option to open the aae-installsummary.html file. By default, this is located at C:
\Program Files\Automation Anywhere\Enterprise\. Use this file to view a summary of
the installation. It provides the following details:

© 2018 Automation Anywhere. All rights reserved. 26

 Automation Anywhere - Installing Control Room

© 2018 Automation Anywhere. All rights reserved. 27

 Automation Anywhere - Installing Control Room

Install Automation Anywhere Enterprise on Microsoft Azure

Installing Automation Anywhere Enterprise Version 11.3 on Microsoft Azure platform.
This document describes how to deploy Automation Anywhere Enterprise (AAE) 11.3 Control Room (CR)
in a Microsoft Azure cluster environment. Automation Anywhere Enterprise on all supported operating
systems listed in the following table.
The steps described in this document were QA certified using Automation Anywhere Enterprise Version
11.3 on a Microsoft Azure cluster environment.

Component Configuration Version

IaaS Windows 2016

IaaS Windows 2012 R2

PaaS Azure SQL Database

(Microsoft SQL Azure (RTM) -
12.0.2000.8)

PaaS Azure PostgreSQL (9.5 and

SSL Disabled)
PaaS (50 GB) Azure File Share
PaaS Azure Load Balancer (Not
Application Gateway)
PaaS Bitnami Subversion 1.10.0-0
(Linux)
IDaaS and IaaS Windows 2016 (for Iaas)

Prerequisite configuration for Automation Anywhere Enterprise on

Azure clusters
Configuration prerequisites for installing Automation Anywhere Enterprise on Azure clusters.
When you install Automation Anywhere Enterprise on Azure cluster environments certain third party
products must be configured prior to beginning installation. This topic lists those required configurations.

© 2018 Automation Anywhere. All rights reserved. 28

 Automation Anywhere - Installing Control Room

1. Confirm the installation environment meets the datacenter requirements and collect the related
information required about the components. For example gather credentials, IP addresses, port
addresses:
• Load balancer - IP address
• Microsoft SQL server - port credentials
• PostgreSQL server - port credentials
• SMB file share - address credentials
• Subversion server (optional) - port credentials
• Enterprise identify management system (optional)
If you have Active Directory (AD) - AD server domain credentials
• SMTP - host port HTTP/S ports for TLS (if using)
• Control Room servers - Have Windows credential manager installed

2. Configure the Network Security Group as per the recommended security policies for Inbound Port
rules:
Name Port Protocol

CR_Port/s 80, 443 Any

AD_Port/s 53, 389 Any
LDAP_Port/s 3268, 3269 Any
SMTP_Port/s 587 Any
SSH_Port/s 22 Any
RDP_Port/s 3389 TCP

3. Configure the AD server.

Ensure all users are part of the AD domain.
Ensure the AD server is setup in IaaS mode for Azure cluster environment installations.

To configure the AD server on Azure with IDaaS, refer to the Microsoft Azure documentation.

© 2018 Automation Anywhere. All rights reserved. 29

 Automation Anywhere - Installing Control Room

4. Ping control room servers.

Make sure the Control Room servers in the clustered environment can ping each other using a private
IP, as shown below:

Note: If the ping is not successful:

a. Enable the following below firewall rule:

b. Ping the Control Room after enableing the firewall rule change. The return is similar to the
following:

Proceed to Begin Control Room installation on Azure .

Begin Control Room installation on Azure

Initial steps for Control Room installation on Azure.
Ensure your environment meets the prerequisites listed in Prerequisite configuration for Automation
Anywhere Enterprise on Azure clusters.
The steps presented here describe how to begin the Control Room installation.
1. RDP to Control Room server.
RDP to one of the Control Room nodes/server and run the Control Room installer. Click Yes to initiate
installer.

© 2018 Automation Anywhere. All rights reserved. 30

 Automation Anywhere - Installing Control Room

2. Click Install on Microsoft OLE DB Driver for SQL Server, Microsoft Visual C++ Redistribution Package
dialog.

3. Click Next.
The License Agreement page is displayed.

Proceed to Customize Control Room installation on Azure clusters.

Customize Control Room installation on Azure clusters

Apply customized configuration required for the Control Room cluster.
This topic continues from the Control Room when you select Custom in the installation wizard. Complete
the initial installation steps in Begin Control Room installation on Azure .

© 2018 Automation Anywhere. All rights reserved. 31

 Automation Anywhere - Installing Control Room

In this task you provide the configuration information you gathered in the prerequisites stage. This includes
IP addresses, certificates, and credentials for the the Control Room servers, datacenter servers, and
databases.
1. Select the Custom option and click Next.

The Destination Folder page is displayed. By default, the destination folder is C:\Program Files
\Automation Anywhere\Enterprise\.

2. To make changes to the destination folder, click Change..., supply new destination folder name, and
click OK.

Note: It is NOT recommended to install the application directly in the root directory, for instance
C:\Automation Anywhere\Enterprise\. Create or select a folder for installation instead, for
instance C:\Program Files\Automation Anywhere\Enterprise\.

© 2018 Automation Anywhere. All rights reserved. 32

 Automation Anywhere - Installing Control Room

3. Click Next
The Cluster Configuration page is displayed.

4. Enable Cluster Setup

Note: The option is enabled only if the machine on which the setup is being run has local IP
addresses configured. If the machine does not have local IP addresses, it is disabled as shown:

© 2018 Automation Anywhere. All rights reserved. 33

 Automation Anywhere - Installing Control Room

5. Enter the IP addresses of the nodes for the cluster.

a. Use a comma (,) to specify more than one IP address. For example, 192.161.1.1, 192.161.1.2,
192.161.1.3 and so on.

1. If you Enable Cluster Setup and do not type an IP, the following message is shown:

2. If you supply invalid numbers or characters, the following message is shown:

b. On correct input of cluster IP's, you will be prompted to input the local ip:

c. Select the IP.

If multiple local IP's are configured on the machine, select the IP on which Control Room is
installed as it will be used to access the Control Room from other nodes.

Caution: Once configured, you cannot add or remove nodes from the list of IPs

Note: If you want to install the Control Room without a cluster, do not enable cluster setup.

© 2018 Automation Anywhere. All rights reserved. 34

 Automation Anywhere - Installing Control Room

6. The TLS Configuration page is displayed wherein you can either:

• Generate a Self-Signed Certificate
When the Self-Signed Certificate option is enabled the installer will generate a unique private key
and a self-signed certificate for the :

• Import a Certificate:
You must import a certificate if successful certificate validation is required for accessing the Control
Room.
To import a custom certificate, clear the Self-Signed Certificate option. This will enable Certificate
Path to browse and import certificate.

Note: The certificate file must be in PKCS12 format.

Supply the following:

• Certificate Path — Click the Browse button to import the certificate.
• Private Key Password — Type the password for the private key.

Warning: Password Limitation Any usage of special character "@" at the beginning of
the password will fail to import the certificate file. Do not use "@" in passwords.
• Webserver Port — Type the Webserver port – either HTTP or HTTPS. If the port is already
assigned, you are shown:

© 2018 Automation Anywhere. All rights reserved. 35

 Automation Anywhere - Installing Control Room

Attention: The port validation message is also displayed when you add 8080 for
Webserver and if that is already in use for Control Room license service. Use a different
unassigned port in above cases.
• Enable Force HTTP traffic to HTTPS — To redirect all HTTP port requests to HTTPS. To
access the Control Room via HTTPS using the generated self-signed certificate.
• Ensure the port number is different for both.

7. Click Next.
The Service Credentials page is displayed.

8. Clear the Local System Account option to add credentials manually to configure the domain account.
The Service Credentials page allows you to specify the account that will be used to run
all Windows services that are created by Automation Anywhere Enterprise installer.

By default, the Local System Account is selected. To run Automation Anywhere services as a different
user instead of a Local System account, clear the Local System Account check box and type the user
name and password for the domain account.

Note:
• If you do not enter the correct Windows domain credentials which shall not be validated on this
screen, the Automation Anywhere services will not run and the Control Room will fail to launch.
• The user running the installer needs system administrator role.
• The user credentials provided during install time for service could be restricted to launch
PowerShell scripts and database table creation could potentially fail.
• If using remote SQL server for creating database then, the combination of Local System Account
for Service Credentials and Use Windows Authentication for SQL Connection is not supported.
• A username and password must be specified for services instead of local system service
account when using a remote database server.
• The username and password specified is used to create tables and for the control room
processes to access the database.
• Refer Matrix for creating database, tables, and services in Working with SQL Servers

9. Click Next.

© 2018 Automation Anywhere. All rights reserved. 36

 Automation Anywhere - Installing Control Room

10. Set connection, authentication, and databases.

• Database Server
This page is launched if you select SQL Server for configuring your database

Note:
• If possible, do not set the value for Database Server as localhost, or the Secure
Connection to the database does not work.
• For Azure installations, the database names for Control Room and Bot Insight must be the
same, or installation fails.
• Click the Browse button to select the SQL server instance where the Control Room database
will be created.

Alternately, type a database server name or select one from the list .

Database Port To connect to the database on custom port,

specify that as a value for the Database Port
The default database port is 1433.
Use Secure Connection Select Use Secure Connection to use CA
certificate as specified.

Note: The host name in certificate and

database connection must be same.

Certificate This option is enabled when you select secure

connection. Browse to select a CA certificate.
Refer section on Import a CA Certificate for
details on how to import this certificate using the
command line.

© 2018 Automation Anywhere. All rights reserved. 37

 Automation Anywhere - Installing Control Room

Windows authentication This option is selected by default. This allows

for connecting to the SQL Server using
Windows authentication.

Note: If user selects Windows Authentication,

then the user running the installer is used
to test that the database exists, and create
it if necessary, and grant db_owner to the
service account user (NT Authority/System).
Refer matrix for creating database, tables, and
services in Working with SQL Servers

SQL Server authentication Select this option to use SQL server

Authentication to connect to the database.
Provide correct username and password for
SQL Authentication.

Note: On invalid credentials, following

message is shown:

Name of Control Room database Enter the name for the Control Room database.
Name of Bot Insight database Type the name for the Bot Insight database.
This database is used to store the Bot Insight
data.

Note: If the database (Control Room and or

Bot Insight) does not exist, the installer will
create one automatically.

Attention: If the database names are blank, have spaces, or include % (percent
character), you are shown an error:

© 2018 Automation Anywhere. All rights reserved. 38

 Automation Anywhere - Installing Control Room

Hence, for SQL Server database names it is recommended to restrict the names to
alphanumeric, period (.), dash (-), and underscore (_).

•
Oracle Server
This page is launched if you select Oracle Server for configuring your database

Provide the following details,

Database Server Provide the server hostname details. The

users should have been created in the Oracle
database by the system admin before running
the installation.

Note: Refer article on how to create users in

Oracle

Database Port The default database port is 1521. You can

connect using a custom port as defined by the
system admin.
Control Room Database Username Control Roomdatabase username that was
created initially by the system admin.
Control Room Password Password of the Control Room database user.
Bot Insight Database Username Bot Insight database username that was
created initially by the system admin.
Bot Insight Password Password of the Bot Insight database user.
Use Secure Connection Select Use Secure Connection to use CA
certificate as specified.

Note: The host name in certificate and

database connection must be same.

Certificate This option is enabled when you select secure

connection. Browse to select a CA certificate.
Refer section on Import a CA Certificate for
details on how to import this certificate using the
command line.

© 2018 Automation Anywhere. All rights reserved. 39

 Automation Anywhere - Installing Control Room

11. Click Next

The Ready to Install the Program page is displayed.

12. Click Install

Allow the installation to process complete.

13. Click Finish.
The Configure Control Room setting page is displayed.

Proceed to Configure Azure clusters for the Control Room.

Configure Azure clusters for the Control Room

After Control Room installation is complete, use the Azure Portal to configure the Azure clusters.
Complete the Control Room installation wizard on the Azure clusters. See Begin Control Room installation
on Azure and Customize Control Room installation on Azure clusters.

© 2018 Automation Anywhere. All rights reserved. 40

 Automation Anywhere - Installing Control Room

This topic describes the configuration steps required after the Control Room installation. Use the Azure
Portal to configure Widnows credentials, Control Room settings for repository and URL, master key for
Credential Vault, Active Directory authentication, and optionally, SVN and SMTP settings.
1. From the Azure Portal where SMB File Share is setup, get the Connection String to retrieve following
3parameters:
a. Internet or network address
b. User name
c. Password

2. Locate the Window Credential Manager on the control room server and click Add a Windows
Credential.
3. Enter the credential information.

Note: Adding a user under Windows Credential Manager needs to be repeated on all the servers
used for testing in the cluster environment (Control Room, Clients/Devices).

4. Enter information and click Save and Continue.

Repository path is extracted from SMB File Share and Control Room access URL in is a load balancer
Public IP.
5. Copy the Master Key and save it (it will be needed to restart the services).

6. Select Express mode and click Save and Continue.

7. Enter the Active Directory authentication configuration information, including URL, Domain username,
and password, then click Check Connection. If settings are correct, click Next.
8. Enter the AD user created previously and click Check name in Active Directory. Upon validation,
click Save and Log in.
Create additional users as needed and create corresponding users in the Control Room.

© 2018 Automation Anywhere. All rights reserved. 41

 Automation Anywhere - Installing Control Room

9. Optional: Continue with installing other control room nodes in the cluster.
10. On the SVN server please change the repository path from “subversion” to “subversion/repo” in “/
opt/bitnami/apache2/conf/httpd.conf” file and make following changes:
a. Create new repository and update the path in httpd.conf # SVNPath sudo mkdir /opt/
bitnami/repositories sudo svnadmin
b. Create /opt/bitnami/repositories/aaerepo sudo chown -R bitnami:bitnami /
opt/bitnami/repositories
c. Create Users for basic authentication with below commands (httpd.conf for Apache
configuration with in Location Tag for subversion AuthType Basic):
• AuthName "Subversion repository"
• AuthUserFile /opt/bitnami/repository/users require valid-user
• SSLRequireSSL

d. Adding an individual user: sudo /opt/bitnami/apache2/bin/htpasswd -c /opt/

bitnami/repository/users aaeuser cd /opt/bitnami/apache2/conf Edit
httpd.conf and update the svn path <Location /subversion/repo> DAV svn
SVNPath "/opt/bitnami/repositories/aaerepo"
e. Save
f. Restart subversion and Apache
g. Make certain the repo has been added with write permissions.

Upon successful registration of SVN on Control Room, the following screen is displayed.

© 2018 Automation Anywhere. All rights reserved. 42

 Automation Anywhere - Installing Control Room

11. SMTP registration

Perform the SMTP registration as shown:

Note: A real SSL certificate is recommended for use with deployments.

This completes the Control Room installation on Azure clusters.

Prerequisites
Determine whether the system has the required hardware and software to install Automation Anywhere
Enterprise Control Room.

Software Requirements

Software Minimum requirements

Operating System Windows Server 2012 R2

.NET Framework Microsoft .NET 4.6
Database Management System • Microsoft SQL Server 2014 SP1 (Express Setup) Microsoft
SQL Server 2012 (Customer Setup)

OR
•
Oracle Database 12.1.0.2

Web Browser • Chrome versions 57 and above

• Internet Explorer versions 10 and 11
• Firefox version 52 and above

Note: Install the following separately if not previously installed:

© 2018 Automation Anywhere. All rights reserved. 43

 Automation Anywhere - Installing Control Room

• Microsoft .NET Framework 4.6

• Microsoft SQL Server 2014 SP1 (applies to Express installations only)
•
Oracle Database 12.1.0.2 (applies to Custom Installation only)

Note: Ensure that the machine on which you want to install the Control Room has a valid IP address
assigned. If the machine is connected to network, it will have a valid IP Address.

Supported Operating Systems

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

Operating System Edition

Microsoft Windows Server 2016 Standard and Datacenter Edition

Microsoft Windows Server 2012 R2 Standard and Datacenter Edition

Supported Microsoft SQL Servers

• Microsoft SQL Server 2017

• Microsoft SQL Server 2016
• Microsoft SQL Server 2014 SP1
• Microsoft SQL Server 2012

Supported Oracle Database Servers

• Oracle Database 12.1.0.2

Hardware Requirements

Hardware Minimum requirements

Processor 8 core Intel Xeon Processor

RAM 16 GB
Disk Space 500 GB

© 2018 Automation Anywhere. All rights reserved. 44

 Automation Anywhere - Installing Control Room

Version Control Integration (if enabled)

• Subversion is provided by the Apache Subversion software project.

Subversion SVN Server

Subversion 1.9.7 Visual SVN Server 3.6.x

Subversion 1.8.15 Visual SVN Server 3.3.x
Subversion 1.7.2 Visual SVN Server 2.5.2

Note: You can configure your own instance of Subversion, although Visual SVN recommended.
• SVN repository with an administrator account.

PostgreSQL Server

This component can be installed using the Automation Anywhere Enterprise installer, if not installed.
This can be installed if you want to store metadata related to analytics dashboards in PostgreSQL Server
instead of the default Microsoft SQL Server.

Component PostgreSQL Server

Configuration PaaS
Version Azure PostgreSQL (9.5 and SSL Enabled)

Silent Installation

Prerequisites

Open power shell in admin mode and execute:

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force

Custom Silent Installation

Start power shell in admin mode and execute:

.\install.ps1

Installation Parameters

Variable Name Description

INSTALLDIR Installation Directory

© 2018 Automation Anywhere. All rights reserved. 45

 Automation Anywhere - Installing Control Room

Variable Name Description

AA_SETUPTYPE Setup type Custom or Express

AA_SETCLUSTERMODE For cluster set 1 else 0

AA_CRCLUSTERCONFIG if AA_SETCLUSTERMODE=1 then cluster IP comma

separated

AA_CRLISTENPORT Web server port. Default value is 80

AA_CRFORCETOHTTPS="1" Force traefik from HTTP to HTTPS

AA_CRFORCEHTTPSCONFIG=" " -

AA_CRWCCERTPASSWD Certificate password

AA_CRSETLOCALSERVICECRED 1 if service logon as System

0 if service logon as specific user

AA_CRSERVICEUSERNAME if AA_CRSETLOCALSERVICECRED= 0 then domain\user

name

AA_CRSERVICEPASSWD if AA_CRSETLOCALSERVICECRED= 0 then password

AA_CRSERVICECONFIRMPASSWDif AA_CRSETLOCALSERVICECRED= 0 then confirm

password

AA_CRDBPORT Control Room database port. Default value is 1433

AA_SQLSERVERAUTHTYPE 0 for Windows Authentication and 1 for SQL Server

Authentication

AA_CRWCCERTPATH Certificate path

IS_SQLSERVER_SERVER SQL server name (host name)

IS_SQLSERVER_AUTHENTICATION0 for Windows authentication

AA_SQLSERVERAUTHMODE 0 for Windows authentication

IS_SQLSERVER_DATABASE SQL Database name

IS_SQLSERVER_DATABASE1 BotInsight database name

AA_BIPGINSTALL 1 if Install PostgreSQL else 0

AA_INSTALLPOSTGRES Install PostgreSQL Server

AA_BIPGDATABASE PostgreSQL database name

AA_BIPGHOSTNAME PostgreSQL hostname (Server name)

© 2018 Automation Anywhere. All rights reserved. 46

 Automation Anywhere - Installing Control Room

Variable Name Description

AA_BIPGUSERNAME PostgreSQL username

AA_BIPGPASSWORD PostgreSQL password

AA_BIPGCONFIRMPASSWORD PostgreSQL confirm password

AA_CRHTTPPORT CR HTTP port. Default is 5432

AA_CRHTTPSPORT CR HTTPS port

Oracle Related Parameters

AA_ENTERPRISEDBTYPE 1 for Oracle
AA_ORCLDATABASESERVER Oracle database server
AA_ORCLJDBCDRIVERLIB full path to oracle jdbc driver library
AA_ORCLDATABASEPORT Oracle Port number (default is 1521)
AA_ORCLSID System identifier that identifies each Oracle database
instance
AA_ORCLCRUSERNAME Oracle Control Room username
AA_ORCLCRPASSWORD Oracle Control Room password
AA_ORCLBIUSERNAME Oracle Bot Insight username
AA_ORCLBIPASSWORD Oracle Bot Insight password

Elasticsearch Related Parameters

AA_ELASTICSEARCHSYSIP valid IP

BotInsight Metadatatype Parameters

AA_BIMETADATADBTYPE <0 or 1> 0 is for SQL Server, 1 is for PostgresSQL. If
Metadatadbype is 1 provide the Postgres related details. By
default SQL Server Metadata is selected

Note: The silent install logs are stored in the folder from which the install script is executed. For example,
if you run the script from C:\Silent Install, the logs will be stored in C:\Silent Install folder.

Sample Powershell Script

Using the script, you can install the Control Room for various configurations available in the installer.
The following sample script can be executed to install the Control Room with Credentials in Service logon,
Non Secure connection using SQL Authentication using a new Database.

Tip: Edit the script with your configurations and save correct value for the variables like
$service_username, $service_pwd, $db_server, $cr_port, etc.

© 2018 Automation Anywhere. All rights reserved. 47

 Automation Anywhere - Installing Control Room

$cr_port=80
$service_username= ".\Administrator"
#e.g."mydomain\john.smith"
$service_pwd="astrongpassword"
#$certpath = "C:\SilentInstall\certificate.pfx"
#$certpass = "changeit"
$db_server="localhost\sqlexpress"
$cr_db_name="CRDB-NEW"
$bi_db_name="BotInsight"
$db_user="sa"
$db_pwd="Admin@123"
$AA_BIMETADATADBTYPE=0
$bi_pg_server="localhost"
$bi_pg_username="automation"
$bi_pg_pwd="Automation123"
$installation_path="C:\Program Files\Automation Anywhere"
#Install latest setup
$static_installation_path="\Enterprise\"""""
$silent_details=" /s ","v""" -join "/"
$installpath_details= "/qn INSTALLDIR=\"""
$custom_details=" /vAA_SETUPTYPE=Custom /vAA_CUSTOMMODETYPE=1"
$port_cluster_details=" /vAA_SETCLUSTERMODE=0 /vAA_CRLISTENPORT=$cr_port"
$service_details=" /vAA_CRSETLOCALSERVICECRED=0 /vAA_CRSERVICEUSERNAME=
$service_username /vAA_CRSERVICEPASSWD=$service_pwd /vAA_CRSERVICECONFIRMPASSWD=
$service_pwd"
$db_details=" /vAA_BIMETADATADBTYPE=$AA_BIMETADATADBTYPE /
vAA_SQLSERVERAUTHTYPE=true /vIS_SQLSERVER_SERVER=$db_server /
vIS_SQLSERVER_USERNAME=$db_user /vIS_SQLSERVER_PASSWORD=$db_pwd /
vIS_SQLSERVER_DATABASE1=$bi_db_name /vIS_SQLSERVER_DATABASE=$cr_db_name /
vIS_SQLSERVER_AUTHENTICATION=1 /vAA_SQLSERVERAUTHMODE=1"

$pg_details=" /vAA_BIPGINSTALL=1 /vAA_INSTALLPOSTGRES=0 /vAA_BIPGHOSTNAME=

$bi_pg_server /vAA_BIPGUSERNAME=$bi_pg_username /vAA_BIPGPASSWORD=$bi_pg_pwd /
vAA_BIPGCONFIRMPASSWORD=$bi_pg_pwd"
$other=" /vAA_CRWCHTTPPORT=80 /vAA_CRWCHTTPSPORT=443 /vAA_CRSELFSIGNCERT=1 /
vAA_CRWCCERTPATH=$certpath /vAA_CRWCCERTPASSWD=$certpass /vLAUNCHPROGRAM=1 /
v""/L*v log.txt"""
$final_commandline = -join($silent_details,$installpath_details,
$installation_path,$static_installation_path,$custom_details,
$port_cluster_details,$service_details,$db_details,$pg_details,$other)
Write-Host $final_commandline

© 2018 Automation Anywhere. All rights reserved. 48

 Automation Anywhere - Installing Control Room

$a=Get-ChildItem $PSScriptRoot\* -Include *.exe

#$a = "C:\Silent\AutomationAnywhereEnterprise_v11_2_0-07272018-10234948.exe"
Write-Host $a
Write-Host "Starting the installation please wait for sometime..."
$processdetail=(Start-Process -FilePath $a -ArgumentList $final_commandline -
Wait -PassThru).ExitCode
Write-Host $a.Name execution is done. If installation is not proper please
check msi logs in the temp folder.
pause

The following sample script can be executed to install the Control Room with Oracle as a database.

$cr_port=80

$service_username= ".\Administrator"
#e.g."mydomain\john.smith"
$service_pwd="astrongpassword"

$cr_db_name="CRDB-NEW"
$bi_db_name="BotInsight"

$OracleServer = "oracledb"
$OraclLib="..\Oracle\ojdbc7-12.1.0.2.0.jar"
$ORCLDATABASEPORT=1521
$ORCLSID="ORCL"
$ORCLCRUSERNAME="CR"
$ORCLBIUSERNAME="BI"
$ORCLPASSWORD="Abcd1234"
$AA_ENTERPRISEDBTYPE=1
$AA_BIMETADATADBTYPE=1

$bi_pg_server="localhost"
$bi_pg_username="automation"
$bi_pg_pwd="Automation@123"

$installation_path="C:\Program Files\Automation Anywhere"

$static_installation_path="\Enterprise\"""""
$silent_details=" /s ","v""" -join "/"
$installpath_details= "/qn INSTALLDIR=\"""
$custom_details=" /vAA_SETUPTYPE=Custom /vAA_CUSTOMMODETYPE=1" /vDONOTABORT=1
$port_cluster_details=" /vAA_SETCLUSTERMODE=0 /vAA_CRLISTENPORT=$cr_port"

© 2018 Automation Anywhere. All rights reserved. 49

 Automation Anywhere - Installing Control Room

$service_details=" /vAA_CRSETLOCALSERVICECRED=1"
#$service_details=" /vAA_CRSETLOCALSERVICECRED=0
/vAA_CRSERVICEUSERNAME=$service_username /vAA_CRSERVICEPASSWD=$service_pwd /
vAA_CRSERVICECONFIRMPASSWD=$service_pwd"

#$db_details=" /vAA_SQLSERVERAUTHTYPE=true /vIS_SQLSERVER_SERVER=$db_server

/vIS_SQLSERVER_DATABASE=$cr_db_name /vIS_SQLSERVER_DATABASE1=$bi_db_name /
vIS_SQLSERVER_AUTHENTICATION=1 /vAA_SQLSERVERAUTHMODE=1"
$db_details=" /vAA_ENTERPRISEDBTYPE=$AA_ENTERPRISEDBTYPE /vAA_BIMETADATADBTYPE=
$AA_BIMETADATADBTYPE /vAA_ORCLDATABASESERVER=$OracleServer /
vAA_ORCLJDBCDRIVERLIB=$OraclLib /vAA_ORCLDATABASEPORT=$ORCLDATABASEPORT /
vAA_ORCLSID=$ORCLSID /vAA_ORCLCRUSERNAME=$ORCLCRUSERNAME /vAA_ORCLCRPASSWORD=
$ORCLPASSWORD /vAA_ORCLBIUSERNAME=$ORCLBIUSERNAME /vAA_ORCLBIPASSWORD=
$ORCLPASSWORD"

$pg_details=" /vAA_BIPGINSTALL=1 /vAA_INSTALLPOSTGRES=0 /vAA_BIPGHOSTNAME=

$bi_pg_server /vAA_BIPGUSERNAME=$bi_pg_username /vAA_BIPGPASSWORD=$bi_pg_pwd /
vAA_BIPGCONFIRMPASSWORD=$bi_pg_pwd"

$other=" /vAA_CRWCHTTPPORT=$cr_port /vAA_CRWCHTTPSPORT=443 /vLAUNCHPROGRAM=1 /

v""/L*v log.txt"""
$final_commandline = -join($silent_details,$installpath_details,
$installation_path,$static_installation_path,$custom_details,
$port_cluster_details,$service_details,$db_details,$pg_details,$other)

Write-Host "$final_commandline"
#$a=Get-ChildItem $PSScriptRoot\* -Include *.exe
$a = "C:\Silent\AutomationAnywhereEnterprise_v11_3_1-11142018-06274507.exe"

Write-Host $a
Write-Host "Starting the installation please wait for sometime..."

$processdetail=(Start-Process -FilePath $a -ArgumentList $final_commandline -

Wait -PassThru).ExitCode
Write-host $final_commandline"
Write-host $processdetail"
Write-Host "$a.Name execution is done. If installation is not proper please
check msi logs in the temp folder"
pause

Remove or Repair Installation

The process to repair or uninstall the Automation Anywhere Enterprise Client.

© 2018 Automation Anywhere. All rights reserved. 50

 Automation Anywhere - Installing Control Room

Uninstall

To uninstall, go to Control Panel # Programs and Features. Select the desired Automation
Anywhere Enterprise Client file and click Uninstall.
Alternatively, choose to remove the Automation Anywhere Enterprise Client by launching the Setup
Wizard:
1. Select Remove.
2. Click Next.

Note: The uninstall process for the Automation Anywhere Enterprise Client will not remove all related
folders (e.g. Client Repository folder).

Repair

Use the repair option to re-install all the program features that were installed during the initial setup run.
1. Launch the Automation Anywhere Enterprise Setup Wizard and select the Repair option.
2. Click Next.

Caution: Do not delete the database tables as repair is possible only if the database tables
exist. If the database tables are deleted, the tables will not be re-created using this option.

First Time Control Room Configuration

Depending on them mode of installation, options may be different when launching the Control Room for the
first time.

© 2018 Automation Anywhere. All rights reserved. 51

 Automation Anywhere - Installing Control Room

Express Control Room Configuration

When Control Room is installed in Express mode, deploy the Getting Started Wizard.
1. Assign the first Control Room administrator to manage the overall RPA environment for your
organization.
2. Create three security questions for the password.
3. Set up the Credential Vault Master Key.

© 2018 Automation Anywhere. All rights reserved. 52

 Automation Anywhere - Installing Control Room

To configure Control Room for the first time for an express installation, perform the following steps:
1. Double-click the Automation Anywhere Control Room icon on the desktop. The getting started wizard
is displayed.
2. Supply the following information:
• Username Supply a user name.
• First name Enter the first name.
• Last name Enter the last name.
• Email Supply e-mail address.
• Password Enter a password.
• Confirm password Type the password again to confirm.

3. Click Next. The Create security questions page is displayed.

4. On the Create security questions page, type three security questions and an answer to each.
5. Click Next. The Credential settings page is displayed.
6. Select the Express mode or Manual mode options.
The Master Key is used to connect to the Credential Vault so that users can use the vault to secure
their credentials and access it in their TaskBot.

Warning: The administrator must copy the Master Key and save it in a secure place. This key
is required in the event that the Credential Vault is closed. If the Master Key is lost, access to
the Control Room is locked.

7. Click Save and log in. The first administrator user for the Control Room installation is created and can
now configure and manage the overall RPA environment with Control Room and clients.

Custom First Time Control Room Configuration

Custom mode installion of the Control Room using the getting started wizard.
The work flow for configuring Control Room installed in manual mode consists of the following:

© 2018 Automation Anywhere. All rights reserved. 53

 Automation Anywhere - Installing Control Room

Install Control Room in Custom mode using the getting started wizard to supply the following information:
1. Specifying the path of the repository - this is the location where the uploaded automation files, such as
MetaBots, IQ Bots, and TaskBots will be. stored.
2. Specifying the host name URL - this is the URL that users will use to access your installation of
Control Room.
3. Set up the Credential Vault Master Key.
4. Select the authentication type - , or Control Room database.
5. Assign the first Control Room administrator to manage the overall RPA environment for your
organization.
6. Create three security questions for the password.

To configure Control Room when you start it for the first time for a custom installation, perform the following
steps:
1. Double-click the Automation Anywhere Control Room icon on your desktop. The Configure Control
Room settings page is displayed.

2. On the Configure Control Room settings page, supply the following:

Repository Path Type the location where the uploaded automation

files will be stored.
For example, C:\ProgramData
\AutomationAnywhere\Server Files.

© 2018 Automation Anywhere. All rights reserved. 54

 Automation Anywhere - Installing Control Room

Control Room Access URL Type the URL that users will use to access the
Control Room.

Note: This URL refers to the that routes request to separate Control Room instances.

3. Click Save and continue. The Credential Vault setting page is displayed.

Important: The back button of your Web browser is automatically disabled after you type the
Repository path and Control Room access URL and click Save and continue. This is to ensure
that the Credential Vault Master Key that will be generated matches the repository path and Control
Room access URL. To go back to the Configure Control Room settings page, press Ctrl+F5 on your
keyboard and start over again.

Note: The Save and continue button is not enabled if the correct path or URL is not specified.

4. On the Credential Vault settings page, specify the following:

• Express mode: Select this option if you want the system to store your master key to connect to
Credential Vault.

Note: It is recommended that you do not use this option for a production environment.
• Manual mode: Select this option if you want to store the Master Key on your own. When you use
this mode, you must enter the Master Key if the Credential Vault is locked. The Master Key is used
to connect to the Credential Vault so that users can use the vault to secure their credentials and
access it in their TaskBots. Copy the Master Key to your Windows clipboard by clicking the Copy
button and save it in a secure location.

Important: The administrator must copy the Master Key and save it in a secure place. This key
is required in the event that the Credential Vault is closed. If it is lost, access to Control Room is
locked.

5. Click Save and Continue. The Authentication type for Control Room users page is displayed. Use this
page to specify the type of authentication your users will use to log on to Control Room.

Important: The back button of the Web browser is automatically disabled after initiating Save and
Continue on the Credential Vault settings page. No further changes to the Control Room configuration
or Credential Vault settings are allowed. To make changes, reinstall Control Room.

© 2018 Automation Anywhere. All rights reserved. 55

 Automation Anywhere - Installing Control Room

6. On the Authentication type for Control Room users page, select one of the following:

Authentication Type Description

Active Directory Select this option for Active Directory authentication. This allows users to
log on to Control Room with Active Directory credentials.
Starting from Version 11.3, Automation Anywhere Enterprise supports
Active Directory (AD) Multi-Forest authentication for the Control Room.
Prior to providing the Authentication Type, ensure the following:
• There is one-way or two-way trust set up between all forests. In case
of one way trust, it should be from Automation Anywhere Enterprise
Client forest to the Control Room forest (Control Room forest should
always be trusting forest).
• There is a two way trust set up for every domain in a forest.
• The root certificate of the LDAP server is imported using the provided
CertMgr tool via command.
• The provided LDAP URLs per forest must not be behind a load
balancer. Also, all LDAP URLs must point to the root (main) domain
controllers.
• The node that runs the Control Room is in the same domain network
where the AD runs.
•
The user is in the parent domain and also the URL is pointing to
the parent. This is because, when there are two or more forests, and
one of the forest has a sub-domain that has a different name space,
a user from the other forests may not have permission to access that
sub-domain.

URL Type the LDAP URL.

For example, ldap://
server01.domain.com.
To support users from a domain
belonging to a different forest, click
the icon to provide additional
LDAP URLs.

Note: For users and groups from

one or more Active Directory
domains, to access the Control
Room, use fully qualified host
name of Global Catalog (GC)
server, listening on port 3268 (3269
in case of SSL).

If you add a domain or a sub-

domain, the authentication will
fail. For example, use ldap://
Server01.ldap.com instead of
ldap://MyDomain/.

Starting with 11.3.1, you can

provide URLs of multiple Global
Catalog per forest so that if one

© 2018 Automation Anywhere. All rights reserved. 56

 Automation Anywhere - Installing Control Room

Authentication Type Description

Global Catalog in a forest goes
down the other can serve.

Note: This feature does not

provide support for load balanced
URL.

Domain Username Type the user name. Ensure you

use the UPN (userPrincipleName)
in the username@domain.com
format.
Domain Password Type the password for the user.
This must be a domain user in the
'Domain Users' group. However,
this user is not expected to use the
Control Room. Though you have
an option to update password,
the recommendation is to use an
Account with "password never
expires" option. If it expires then
it can be updated but with some
downtime.

• Click Check connection. If Control Room is unable to connect to the

Active Directory database, an error message is displayed.

Select this option to use IDP server for authenticaton.

Refer to Configure Control Room for Single Sign On for details.

Control Room database Select this option to use the Control Room database as the type of
authentication.

7. Click Next. The Create yourself as the first Control Room administrator page is displayed.

© 2018 Automation Anywhere. All rights reserved. 57

 Automation Anywhere - Installing Control Room

8. Supply the following information:

• Username Supply a user name.
• First name Enter the first name.
• Last name Enter the last name.
• Email Supply e-mail address.
• Password Enter a password.
• Confirm password Type the password again to confirm.

9. Click Next. The Create security questions page is displayed.

10. On the Create security questions page, type three security questions and an answer to each.
11. Click Save and log in. The first administrator user for the Control Room installation is created and can
now configure and manage the overall RPA environment with Control Room and clients.

Note: For a non-active directory environment, you will be directly logged on to Control Room. However, for
an active directory environment, a login dialog is displayed.

Configure Control Room for Single Sign-On

Configure Single Sign-On for Control Room login authentication.
Use the Single Sign-On option to allow the Control Room to connect to the authentication database
(Control Room) using SAML 2.0 protocol and log on using Single Sign-On.

Note: To setup your SAML application in Okta, refer Setting up a SAML application in Okta

1. From the Authentication type for Control Room users page, select the Single Sign-On (SAML 2.0)
option.
2. Check the connection to Control Room to provide SAML Metadata details.
3. Copy and paste the SAML Metadata from an XML file.
4. Provide the Unique Entity ID for Control Room.
This is basically a user who is the Control Room admin and also has been given an admin role in the
IdP Server.
5. Optional: Select Encrypt SAML Assertions for enhanced security.
This will be provided a public and private key by the system admin and must copy and paste from
relevant files.
6. Click Next.
The Registering Controls panel is displayed.

© 2018 Automation Anywhere. All rights reserved. 58

 Automation Anywhere - Installing Control Room

7. Register the Control Room as a service provider with the IdP.

a) Click to copy the Control Room metadata to the IdP manager.

b) Login to the IdP server as admin or a user with privilege to add a service provider.
c) Click Manage Metadata to add a service provider.
d) Select Attributes for assertion.
e) Paste the metadata that you copied.

a) Click Submit to import data.

8. Return to Control Room configuration page

9. Click
10. Leave the page to go to IdP login
11. Log on using credentials of the IdP user who provides the Control Room Service Provider credentials.
12. Once you are authenticated, log out of the IdP server. This will take you back to the Control Room
First Admin page wherein you can create your first Control Room admin.

Post-upgrade configuration of Active Directory

If you are using LDAP authentication on multiple nodes, post upgrade to Version 11.3, Active Directory
configuration is required.
Launch the Control Room after upgrading to Version 11.3, the updated page is displayed as shown below.

© 2018 Automation Anywhere. All rights reserved. 59

 Automation Anywhere - Installing Control Room

Provide the LDAP URL in the LDAP updated page. When using Multi-Forest authentication, use the +
option to add more URLs.

Note:
• Refer to the section on the Active Directory Authentication Type for prerequites to enable Multi-Forest
authentication.
• If the LDAP updated page did not display, clear your browser cache.
• The LDAP page will not be displayed in subsequent nodes as the data has been updated in the
database from the first node.

Working with SQL Servers

Configure Microsoft SQL Servers before setting up the for Control Room database.

Configuring SQL Server Settings

SQL Server settings can be configured in the SQL Server Configuration Manager.
1. Enable protocol for Named Pipes and TCP/IP in SQL Server Network Configuration#Protocols
for MSSQLSERVER as shown:

© 2018 Automation Anywhere. All rights reserved. 60

 Automation Anywhere - Installing Control Room

2. Right or double-click TCP/IP protocol and input the port number for IPAll in the IP Addresses tab of IP
Properties as shown:

Note: Restart the MSSQLSERVICE for the updates to take effect.

Database and Services

Service Credentials Windows Authentication SQL Authentication

Local System • Current logged in user account is • SQL User account is used to
Account used to create: create:
• • Databases
• Tables • Tables

• Installer gives db_owner

permission to NT AUTHORITY
\SYSTEM account.

Domain User • Current logged in user account is • SQL User account is used to
Account used to create database. create:
• Domain user account is used to • Databases
create tables.
• Tables
• Installer gives db_owner
permission to domain user
account.

Automation Anywhere Windows Services

Make sure that the following Windows services are set when installing the Automation Anywhere
Enterprise Control Room.

© 2018 Automation Anywhere. All rights reserved. 61

 Automation Anywhere - Installing Control Room

Service Name Description

Automation Anywhere Control

Receives and processes API requests for the Control Room.
Room Service

Automation Anywhere Control

Used for distributed cache storage.
Room Caching

Automation Anywhere Control Allows Control Room services to communicate

Room Messaging asynchronously.

Receives all incoming HTTP and HTTPS requests for

Automation Anywhere Control
Automation Anywhere products and forwards to the correct
Room Reverse Proxy
service.

Manages licensing information for Automation Anywhere

Automation Anywhere Licensing
products and services.

Automation Anywhere Bot Insight

Provides the ability for Bot Insight services to find each other.
Service Discovery

Automation Anywhere Bot Insight Used to extract data from Automation Anywhere databases to
EDC create dashboards.

Periodically updates Automation Anywhere dashboards. This

Automation Anywhere Bot Insight
service connects to the Bot Insight Visualization service to
Scheduler
update the database.

Automation Anywhere Bot Insight PostgreSQL database server for use by Automation
PostgreSQL Anywhere.

Renders service requests for dashboards within the Bot

Automation Anywhere Bot Insight
Insight application. Any request that pertains to adding,
Visualization
configuring, or deleting widgets goes through this service.

Automation Anywhere Bot Insight

Receives and processes API requests for Bot Insight.
Service

Automation AnywhereBot Insight Enterprise connector to pull data from Elasticsearch based
Elasticsearch data source into the dashboard.

Automation Anywhere Bot Insight Controls and manages queries, including all filtering and data
Query Engine manipulation on the dashboard.

Automation Anywhere
Stores all logs and related activities for search functionality.
Elasticsearch Service

Note: All the services can be configured either in Local System or Domain account when the Control
Room is installed in Custom mode. For a Control Room installed in Express mode, all the services are run
in Local System account.

© 2018 Automation Anywhere. All rights reserved. 62

 Automation Anywhere - Installing Control Room

Configure Control Room for HTTPS Self-Signed Certificate

Configure Enterprise Control Room for HTTPS mode using a self-signed certificate.
To configure the Control Room for HTTPS mode using a self-signed certificate, follow these steps:
1. Launch the Control Room instance in Internet Explorer browser.

Note: Applicable to Internet Explorer only.

© 2018 Automation Anywhere. All rights reserved. 63

 Automation Anywhere - Installing Control Room

2. Change the Control Room URL setting and port to HTTPS and port number to 443.
The website security warning page is launched:

3. Continue to this website to access the Control Room.

Import Certificate for HTTPS

Post installation, import a certificate for HTTPS for the Control Room through the command line.
To import a certificate for configuring the Control Room for secure connection, use the command line.
1. Run command prompt in administrator mode
2. Go to the Automation Anywhere Enterprise installation path - for example, C:\Program Files
\Automation Anywhere\Enterprise.
3. Type or paste the following command at the prompt:

jre\bin\java -jar certmgr.jar -appDir "C:\Program Files\Automation

Anywhere\Enterprise" -setServerCert
"C:\Users\cradmin\Desktop
\test_automationanywhere_com.pfx" -privateKeyPass

© 2018 Automation Anywhere. All rights reserved. 64

 Automation Anywhere - Installing Control Room

YhjR35@#Mkjde

Import a CA Certificate
Post installation, importing a CA certificate using the command line.
To import a CA certificate using the command line post installation:
1. Run command prompt in administrator mode
2. Go to the Automation Anywhere Enterprise installation path - for example, C:\Program Files
\Automation Anywhere\Enterprise.
3. Type or paste the following command at the prompt:

jre\bin\java -jar certmgr.jar -appDir "C:\Program Files\Automation

Anywhere\Enterprise" -importTrustCert "D:\<user name>\My Downloads
\CA31.cer"

© 2018 Automation Anywhere. All rights reserved. 65

 Automation Anywhere - Installing Control Room

4. Add the following parameters to the boot.db.properties file that if found in AAE installation path >
Config folder
C:\Program Files\Automation Anywhere\Enterprise\config
trustServerCertificate=false

© 2018 Automation Anywhere. All rights reserved. 66

 Automation Anywhere Index

Index
A I
active directory authentication 3, 3, 59 import certificate 64
active directory 53 install
administrator mode 64 on Azure cluster 28
asynchronous 61 installation 12
authentication 3, 3, 58, 59 installation path 64
Azure ipall 60
cluster configuration 40
customize cluster 31
Azure cluster environment 28
L
ldap 59
C login 58

cache storage 61
caching 61
M
cluster manual mode 53
Control Room on Azure 31 master key 52, 53
cluster setup 12 messaging 61
configuration 51 Microsoft SQL Server 43
configure Microsoft Windows Server 43
Azure cluster 40 multi-forest authentication 59
configuring 58 Multi-Forest authentication 3, 3
Control Room
Azure cluster configuration 40
Azure install 30 N
customize cluster 31
.NET Framework 43
custom install 3, 12
custom installation 53
custom launch cycle 53 P
custom mode 4, 53
password 52, 53
password limitation 12
D postgre 12
prerequisites
database authentication 3, 3, 59
Azure installation 28
database management system 43
disk space 43
domain user account 60 R
RAM 43
E reinstall 50
repair 50
express install 3
reverse proxy 61
express launch cycle 52
express mode 4, 52
S
F saml 58
security question 52, 53
first time configuration 51
self-signed 63
self-signed certificate 63
G setup 43
setup wizard 50
getting started 52, 53 single-sign on 12
single sign-on 3, 3, 53, 59
H Single Sign-On 58
sql 60
https 64 sql server 60
sql server configuration manager 60

© 2018 Automation Anywhere. All rights reserved. 67

 Automation Anywhere Index

subversion 43
SVN repository 43

U
uninstall 3, 3, 50
upgrade 3, 3, 59

W
windows services 61
windows authentication 60
wizard 52, 53

© 2018 Automation Anywhere. All rights reserved. 68