Installing Control Room on Linux

You start installing the Automation Anywhere Control Room in the Linux environment and complete the installation in the Control Room.

Note: The installation steps do not list any specific configurations or requirements and therefore your setup might be different. Automation Anywhere does not provide any warranties that the installation steps conform with your system configurations or requirements.

This task applies to first-time installation and updates of Automation 360 On-Premises.

Prerequisites

Ensure the following:

The Microsoft SQL Server or Oracle Server database is installed and running.
The Automation 360 installation server is connected to the Microsoft SQL Server or Oracle Server database.
For Oracle Server, ensure that you have installed the appropriate JDBC driver for the Oracle version that is connected to the Control Room.
From Automation 360 Build 6463, ensure that Python 3.6 is installed.
For Oracle Server, only non-container database is supported.

Procedure

Verify the installation prerequisites.
1. Verify the Automation 360 On-Premises prerequisites.
2. Depending on the server you want to use, verify that the Microsoft SQL Server or Oracle Server is running, and execute the command:
  $ sudo systemctl status mssql-server
  If Microsoft SQL Server is not running, install it.
  Note: The Microsoft SQL Server or Oracle Server installation instructions refer to Red Hat Enterprise Linux version 8. For version 7, change the paths to /rhel/7 instead of /rhel/8.
  See Quickstart: Install SQL Server.
3. Ensure the following files are available:
  - SSL certificate
  - License file
4. Download the Automation360_el7_Build_<build_number>.bin installation file to the Linux server from A-People Downloads page (Login required)
  
  Note: We do not support the patch upgrades (upgrading between builds in the same release) in Linux. When you are performing a patch upgrade, we recommended that you always uninstall and do a fresh install for the patch upgrades.
5. Verify that the installation server has internet access in order to update Linux kernel files and OS libraries using Yum updates.
  Alternatively, configure /etc/yum.conf on the installation server to use a Yum repository local to its network. The Yum repository should be up to date before starting the installation.
6. Starting in Automation 360 Build 6463, Python 3.6 is required.
Log in to the installation server.
Run the installer command as a superuser from the Linux shell:
1. $ sudo chmod +x Automation360_el7_Build_<build_number>.bin
2. $ sudo ./Automation360_el7_Build_<build_number>.bin
The installation wizard verifies the installation requirements and proceeds with the installation.
Tip:
- Enter the back command to return to a previous command step.
- Press the return key to accept default values, or enter an alternate value and then press the return key.
To accept the license agreement, enter Y.
In the Transport Layer Security (TLS) screen, configure the following:
1. Control Room HTTP Port (Default: 80)
2. Control Room HTTPS Port (Default: 443)
3. To enable the Self Signed Certificate, enter 1 or enter 2 to disable it.
4. To Force HTTP Traffic to HTTPS, enter 1 to disable it or enter 2 to enable it.
Configure application Transport Layer Security
In the Cluster Configuration screen, enter 1 to disable it or enter 2 to enable it.
- If you choose to enable cluster configuration, enter the IP addresses of the cluster nodes. Use a comma (,) to specify more than one IP address. Do not add space between IP addresses. For example: 192.168.0.1,192.168.0.2,192.168.0.3
- The repository location should be a shared location accessible from all Control Room nodes in the cluster.
- Ensure that you select the IP address that is used to communicate with other nodes of the Control Room.
Configure IP cluster
In the Database Type screen, select one of the following servers:
- Microsoft SQL Server
- Oracle
In the Service Startup Options screen, select one of the following options:
- Default (Start All Services): Enables all Control Room services to automatically run at startup.
- Custom (Choose Startup Options): Enables you to select the Control Room services that you want to automatically run at startup. All the services will be installed on the device. However, only the selected services will automatically run at startup. If required, you can manually start the services that were set to Manual.
  For each service, select one of the following options:
  - Automatic: Enables to automatically run the selected service at startup.
  - Manual: Enables to manually enable the selected service when required.
Note:
- Depending on the database type you selected, some services might not be available for selection as some of the services might not yet be supported for the selected database type.
- For those services that you do not include to run at startup when installing the Automation 360 On-Premises Control Room, a products.notinstalled file is created in the config files directory that you can open using a text editor. This file includes the name of the services that were not selected when installing the Automation 360 On-Premises Control Room. For information about the directory structure, see Installed Control Room directories and files.

Depending on the database server you chose, configure the following settings the server:


Microsoft Databse Configuration	Oracle Databse Configuration
`Database Server address (default: localhost)`	`Database Server (default: localhost)`
`Database port (default: 1433)`	`Database port (default: 1521)`
`Control Room Database (default`: `Automation360-Database`) or enter a name.	`Connect with SID or Service Name` Note: The SID and Service Name entered in the text field provided is unique to your Oracle database.
`SQL Server Login credentials`: provide the login ID and SQL Server password.	`Database User/Schema Password`: provide the password.
`Password prompt for elasticsearch`: Enter or define any password.	(Optional) `Use Secure Connection`: Enable to use a CA certificate as specified and select a CA certificate. Note: Use the same host name for certificate and database connections. Import HTTPS and CA certificates

In the Database Configuration screen, configure the following:
Review the pre-installation summary.

Press Enter to install Automation 360 in the default directory.


Linux installer	Version	Default directory path
Installation file path	Version .22 and earlier versions	`/opt/automationanywhere/enterprise`
	Updating from earlier versions to version .22	`/opt/automationanywhere/enterprise`
	New installation of version .22 and later	`/opt/automationanywhere/automation360`

A message appears stating the installation is successfully completed. See Installed Control Room directories and files for the location of control room assets.

Configure the post-installation settings.
Configuring post-installation settings

Post-installation, a Control Room group controlroom is automatically created. Following users are a part of this group which run the respective Control Room services:

crkernel, traefik, ignite, activemq, crelasticsearch, criqbot, crbotinsight, craari, crdiscoverybot, crstorage, crdiscoverybotml.
Verify Automation 360 services started successfully.
Stop and start Control Room services on Linux
Set up Control Room access.
Configure Control Room database
Set up licenses.
Installing additional licenses

The log files for the Control Room installation are available at:


Linux installer	Version	Log file path
Log path	Version .22 and earlier versions	`/var/log/automationanywhere/enterprise`
	Updating from earlier versions to version .22	`/var/log/automationanywhere/enterprise`
	New installation of version .22 and later	`/var/log/automationanywhere/automation360`

Next steps

After the Control Room installation and configuration is complete, users can register their devices to create and run bots.

Install Bot Agent and register device

For more information on Out of Memory Management (OOM Killer), see Linux Automation 360 Control Room service stopped (A-People login required).