Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Installing Control Room on Linux

  • Updated: 10/26/2021
    • Automation 360 v.x
    • Install
    • RPA Workspace

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 Automation 360 On-Premises updates.

Prerequisites

Ensure the following:

  • The Microsoft SQL Server database is installed and running.
  • The Automation 360 installation server is connected to the Microsoft SQL Server database.

Procedure

  1. Verify the installation prerequisites.
    1. Verify the Automation 360 On-Premises prerequisites.
    2. Verify the Microsoft SQL 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 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 in the Linux. It is always recommended to un-install 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 repository local to its network. The repository should be up to date before starting the installation.
    6. Starting in Automation 360 Build 6463, Python 3.6 is required.
  2. Log in to the installation server.
  3. 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.
  4. To accept the license agreement, enter Y.
  5. 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.
  6. 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.161.1.1,192.161.1.2
    • The repository location should be a shared location accessible from all Control Room nodes in the cluster.
    • If multiple local IP addresses are configured on the machine, select the IP address on which the Control Room is installed.
  7. In the Database Configuration screen, configure the following:
    1. Database Server address (default: localhost)
    2. Database port (default: 1433)
    3. Control Room Database (default: Automation360-Database) or enter a name.
    4. SQL Server Login credentials: provide the login ID and SQL Server password.
    5. Password prompt for elasticsearch: Enter or define any password.
  8. Review the pre-installation summary.
  9. Press Enter to install Automation 360 in the default directory.
    Linux installer Version Default directory path
    Installation file path Earlier to version .22 /opt/automationanywhere/enterprise
    Updated from earlier version to .22
    New installation of version .22 /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.
  10. Configure the 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.
  11. Verify Automation 360 services started successfully.
  12. Set up Control Room access.
  13. Set up licenses.
  14. The log files for the Control Room installation are available at:
    Linux installer Version Log file path
    Log path Earlier to version .22 /var/log/automationanywhere/enterprise
    Updated from earlier version to .22
    New installation of version .22 /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

Send Feedback