The silent mode installation, also known as unattended installation, uses a customized script with parameters specific to your business requirements. The installation process runs in the background without requiring user interaction or displaying messages. This installation resembles the silent mode Control Room installation on an on-premises Linux machine.

Create the following customized scripts with required parameters and execute the script to install the Control Room on a Linux EC2 instance:
  • LinuxInstaller.sh: This script contains the installation parameters you want to apply during installation.
  • CallLinuxScript.sh: This script executes the LinuxInstaller.sh script.

Use the following parameter table to customize the LinuxInstaller.sh script:

Control Room installation parameters
Installation parameter Description Script response options
Checking Installation Prerequisite The installer analyzes your system and notifies you if it does not meet the prerequisites. Choose an option to continue with the installation.
  • 1 = Continue.
  • 2 = Cancel
Introduction The installer displays an introduction and offers options:
  • Enter back to return to a previous step.
  • Enter quit to cancel the installation

Press Enter to continue the installation.

\n
License Agreement The installer displays the License Agreement. The following options are available in silent mode:
  • Press any key to continue reading the agreement.
  • Press 0 to advance to the end of the license agreement.
0
Accept License Agreement The installer displays the prompt to accept the license agreement to continue with the installation.
  • Y = Accept the license agreement.
  • N = Decline the license agreement
HTTP Port Control Room Enter the web server port that you must use to access the Control Room with HTTP. The default port number is 80. 80

Replace the number 80 in the sample script to use a different port.

Control Room HTTPS Port Enter the web server port that you must use to access the Control Room with HTTPS. The default port number is 443. 443

Replace the number 443 in the sample script to use a different port.

Self-Signed Certificate Choose an option to enable or disable self-signed certificate. The default is 1 (Enable).
  • 1 = Enable
  • 2 = Disable
Force HTTP traffic to HTTPS Choose an option to force traffic from HTTP to HTTPS. The default is 1 (Disable).
  • 1 = Disable
  • 2 = Enable
Cluster Setup Choose an option to disable or enable clustering. The default is 1 (Disable).
  • 1 = Disable
  • 2 = Enable
Service Startup Options Choose an option to configure the services that must start during startup. The default option is 1 (Start All Services).
  • 1 - Start All Services
  • 2 - Choose Startup Options (Custom)
Automation Anywhere Control Room Robotic Interface Service Choose an option to start the Automation Anywhere Control Room Robotic Interface Service automatically during startup. The default option is 1 (Automatic).
  • 1 - Automatic
  • 2 - Manual
Automation Anywhere Control Room IQ Bot Service Choose an option to start the Automation Anywhere Control Room IQ Bot Service automatically during startup. The default option is 1 (Automatic).
  • 1 - Automatic
  • 2 - Manual
Automation Anywhere Control Room Storage Service Choose an option to start the Automation Anywhere Control Room Storage Service automatically during startup. The default option is 1 (Automatic).
  • 1 - Automatic
  • 2 - Manual
Automation Anywhere Control Room Connector Builder Choose an option to start the Automation Anywhere Control Room Connector Builder Service automatically during startup. The default option is 2 (Manual).
  • 1 - Automatic
  • 2 - Manual
Automation Anywhere Cloud Service Choose an option to configure the Automation Anywhere Cloud Service. The default option is 2 (Do Not Install).
  • 1 - Configure and Install
  • 2 - Do Not Install
AWS Account ID Enter your 12 digit AWS account ID without the hyphens. 12 digit AWS account ID
AWS Region Enter the region in which the AWS account is hosted. Ensure that you enter the region as per AWS naming standards. AWS region
Database Server Enter the URL of the server where the database resides. The default option is localhost server1.yourcompany.com
Database Port Enter the server port for the database. The default port is 1433 1433
Database Name Enter the Control Room database name. The default database name is localhost. localhost. If the database is on a separate server, enter the host name.
SQL Server Login ID Enter the database system administrator login ID. The default is sa. sa.
SQL Server Password Enter the database system administrator password. The password to log in to your database as system administrator user.
Secure Connection Choose an option to disable or enable the secure connection to the database. The default is 1 (Disable).
  • 1 = Disable
  • 2 = Enable
OpenSearch Password Enter the OpenSearch password. The password that must be used to log into OpenSearch portal. For more information, see Add OpenSearch credentials.
OpenSearch Certificates Choose an option to upload custom certificates.
  • 1: Use this option to upload custom certificates with a trusted Certificate Authority (CA) . For more information, see OpenSearch custom certificate.
    Note: If you use 1, ensure that you upload the .zip file for the custom certificates.
  • 2: This is the default setting and the system generates unique internal certificates.
Pre-Installation Summary The installer displays the summary of features selected and whether the prerequisites are met. Press Enter to proceed. \n
Ready To Install Confirm to proceed with the installation. Press Enter to start the installation. \n

Procedure

  1. Log in as an administrator on the Linux EC2 instance.
  2. Create the LinuxInstaller.sh script in the installation server, substituting values for your own environment.
    Refer to the following sample script for enabling Automation Anywhere Cloud Service and binding the Control Room to your AWS account:
    echo "Starting Installation"
    
    # Variables to simplify customization
    INSTALLER_PATH=""                                			# Change to the path of your installer
    INSTALL_SERVER="" 						        # Change to your Automation Anywhere install server
    SQL_PORT=""                                     			# Change to your SQL Server port if different
    DATABASE_NAME=""            			                        # Replace with your database name
    SQL_ADMIN=""                                     			# Replace with your SQL Server admin ID
    SQL_PASSWORD=""                      			                # Replace with your SQL Server admin password
    
    ES_Password=""                                                          # ES_CustomCertificatePath="/home/ec2-user/Latest-escustomcerts.zip"
    AWS_Accountid=""                                                        # Replace with your AWS account ID
    AWS_Accountregion=""                                                    # Replace with your AWS region
    # Ensure the installer is executable
    sudo chmod a+x "$INSTALLER_PATH"
    
    # Run the installer
    sudo "$INSTALLER_PATH" << EOF
    1
    \n
    0
    Y
    80                                                     
    443
    1
    1
    1
    2
    1
    1
    1
    2
    1
    $AWS_Accountid
    $AWS_Accountregion
    $INSTALL_SERVER
    $SQL_PORT
    $DATABASE_NAME
    $SQL_ADMIN
    $SQL_PASSWORD
    1
    $ES_Password
    2
    \n
    \n
    \n
    EOF
    
  3. Create the script CallLinuxscript.sh to execute Linuxinstaller.sh.
    This script writes the installation results to /home/Installlog. Change the path to the install log file, if required.
    echo "Starting Linux installation"
    sudo ./LinuxInstaller.sh >> /home/Installlog
    echo "Installation Completed Successfully"
  4. Run the following commands to execute the scripts:
    • $ sudo chmod a+x LinuxInstaller.sh
    • $ sudo chmod a+x CallLinuxscript.sh
    • $ sudo ./CallLinuxscript.sh
The Control Room installs successfully on the Linux EC2 instance. You can go to /home/Installlog and review the installation log file to confirm there are no errors.

Next steps

Complete the post-installation procedures listed in Configuring post installation settings.