Perform custom installation of Control Room on Google Cloud Platform

Install and apply the custom configurations required for the Control Room cluster on Google Cloud Platform after completing initial preparations.

Prerequisites

Ensure that you complete the preliminary installation steps: Prepare to install Control Room on Google Cloud Platform.

Procedure

  1. Log in to the first Google Cloud Platform instance as an administrator.
  2. Download the Automation Anywhere__<version>.exe file.
    A-People Downloads page (Login required)
  3. Run the installer file.
  4. Click Next on the Welcome to the Setup Wizard page.
  5. Accept the license agreement and click Next.
  6. Select the Custom option and click Next.
    The Destination Folder page appears. By default, the destination folder is C:\Program Files\Automation Anywhere\Enterprise\.
  7. Optional: To make changes to the destination folder, click Change, enter a new destination folder name, and click OK.
    Note: Do not install the application directly in the root directory (C:\). Ensure that you create a folder. For example, C:\Program Files\Automation Anywhere\Enterprise\.
  8. Click Next to configure the IP cluster.
  9. Select the Enable Cluster Setup check box.
    The check box is enabled by default if the machine on which the setup is being run has local IP address configured.
    To install the Control Room on a single node and not a cluster, clear the Enable Cluster Setup check box.
  10. Enter the IP addresses of the nodes in the cluster.
    • Enter IPv6 addresses if all the nodes in the network are using IPv6.
    • Enter IPv4 addresses if some nodes in the network are using a combination of IPv4 and IPv6 addresses.
    1. Use a comma (,) to specify more than one IP address.
      For example, to specify three IP addresses in the cluster, enter: 192.0.2.1,192.0.2.2,192.0.2.3
      Important: The first IP address in the list is used as the primary node. Ensure that you enter the IP addresses in the same order on all node configurations in subsequent installations. An incorrect order causes the application to configure the IP addresses as separate clusters, which will result in data loss when the issue is fixed after installation.
      You can install multiple nodes at the same time after installing the primary node.
      After installation, you can add a new IP address to the cluster at the end of the list.
    2. After you enter the cluster IP addresses correctly, select a valid address IP at the message prompt to provide network access to the machine.
  11. Click Next to configure the application Transport Layer Security (TLS).
  12. In the TLS Configuration page, select one of the following:
    • Generate a Self-Signed Certificate

      Enabling the Self-Signed Certificate option allows the installer to generate a unique private key and a self-signed certificate for the Control Room.

    • Import a Certificate

      To import a custom certificate, clear the Self Signed Certificate check box. This setting allows you to import a certificate using the Certificate Path field.

      Note: The certificate file must be a PKCS12 format.
      Provide the following information:
      • Certificate Path: Click Browse to import the certificate.
      • Private Key Password: Enter the password for the private key.
        Password limitation: Do not use the at sign (@) in passwords. Using the special character @ in the password causes the certificate file import to fail.
      • Webserver Port: Enter the web server port – either HTTP or HTTPS. If the port is already assigned, an error message is displayed.
        Important: The port validation message is also displayed when you add 8080 for the web server and if that port is already in use for a Control Room license service. Use a different unassigned port in these cases.
      • Enable Force HTTP traffic to HTTPS: This option redirects all HTTP port requests to HTTPS. To access to the Control Room through HTTPS using the generated self-signed certificate, ensure the port numbers are different for HTTP and HTTPS.
        To generate a custom certificate for HTTPS, ensure your custom certificate meets the following:
        • Create a .pfx certificate with a pass code from a CA trusted authority.
        • Combine Root, Intermediate, and Machine level certificates into a single certificate.
        • Use the format [WS Machine Host Name].[DomainName].com for the private key.
        • Include the host name as a fully qualified domain name (FQDN) in the certificate.

          You provide the host name during Control Room installation.

        • In multi-node HA clusters, issue certificates to the load balancer DNS name.
        • Add individual URLs, which require access to all nodes, to the Subject Alternative Name field in the certificate.

        For more information, see Automation Anywhere support site: Automation 360 On-Premises prerequisites (A-People login required).

  13. Click Next to configure the service credentials.
  14. In the Service Credentials screen, choose from the listed options.
    The Windows Service credentials include a user name and password. The user specified must meet these requirements:
    • A member of the local system administrator group.
    • Have permission to manage services, including Automation Anywhere services.
    • If you use Windows authentication to connect to the SQL database, ensure you grant the db_owner permission to the service credential user.

    These service credentials allow the Control Room processes to run the required services.

    • Local System Account—(default) The logged-on user performing the installation
    • Domain Account—Specify a user that is not the local system account user
      1. Clear the Local System Account check box.
      2. Enter the user name and password for the domain account.

        Use only supported characters for the user name and password. See Supported special characters.

      • Do not use the Windows domain credentials

        Enter credentials valid for running Automation Anywhere services. Without the valid credentials, the Control Room will fail to launch.

      • PowerShell script restrictions

        Specify a user with permissions to launch PowerShell scripts who is not a Windows domain user. Without the relevant permissions, database table creation can fail.

  15. Add the SQL Server and click Next.
    Select Microsoft SQL Server, enter the name, and click Next.
  16. On the InstallShield Wizard Completed page, click Finish.
    Launch Automation Anywhere is enabled by default.
    Enable Show installer settings 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.
The Control Room is opened in your default browser and displays the Configure Control Room settings page.

Next steps

Configure Google Cloud Platform settings after installation