Lire et examiner la documentation Automation Anywhere

Automation Anywhere Version 11.3

Fermer les contenus

Contenus

Ouvrir les contenus

Installing Control Room using scripts

  • Mis à jour le : 2021/12/08
    • 11.3.x
    • Installer
    • Enterprise

Installing Control Room using scripts

Silent Control Room installation, also known as unattended installation, uses a customized PowerShell script for a full setup or the command line for a hot fix patch. Silent installation runs the entire installation process in the background without requiring user interaction or displaying messages.

Prerequisites

  • Create a PowerShell script.

    Refer to the installation parameters and sample scripts.

  • Run the script in PowerShell.

Procedure

  1. Review the parameters and identify the settings you require.
    Control Room installation parameters
    Variable name Description
    INSTALLDIR Installation directory
    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_CRSETLOCALSERVICECRED 1 if service log on as System

    0 if service log on as specific user

    AA_CRSERVICEUSERNAME if AA_CRSETLOCALSERVICECRED= 0 then domain\user name
    AA_CRSERVICEPASSWD if AA_CRSETLOCALSERVICECRED= 0 then password
    AA_CRSERVICECONFIRMPASSWD if AA_CRSETLOCALSERVICECRED= 0 then confirm password
    AA_CRDBPORT Control Room database port. Default value is 1433
    AA_SQLSERVERAUTHTYPE 1 for SQL Server and 0 for PostgreSQL Server in case of Bot Insight metadata
    AA_CRWCCERTPATH Certificate path
    AA_CRWCCERTPASSWD Certificate password
    AA_CRSELFSIGNCERT 1 for self-signed certificate
    IS_SQLSERVER_SERVER SQL Server name (host name)
    IS_SQLSERVER_AUTHENTICATION 0 for Windows authentication
    AA_SQLSERVERAUTHMODE 0 for Windows authentication
    IS_SQLSERVER_DATABASE SQL database name
    IS_SQLSERVER_DATABASE1 Bot Insight 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)
    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_ORCLEINSTANCETYPE Select the form used to identify each Oracle Database instance. Options are:
    • 0 = SID
    • 1 = Service
    Used with AA_ORCLINSTANCEVALUE
    AA_ORCLINSTANCEVALUE Specify the SID or service name for the Oracle Database instance.

    Used with AA_ORCLINSTANCETYPE

    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
    AA_ESPASSWD Password for Elasticsearch authentication

    Additional parameter for confirming the password is not available. The password must have a minimum of 6 characters.

    AA_ELASTICSEARCH_BACKUP 1
    AA_ELASTICSEARCH_BACKUP_FILE Path of the Elasticsearch certificates zipped file cert.zip file

    When certificates zip file is specified, the zip file name can be any valid file name. The zipped file containing the main Control Room Elasticsearch certificates must not contain any folders. Only the certificates from the primary Control Room node must be contained in the certificates zip file.

    BotInsight metadatatype parameters
    AA_BIMETADATADBTYPE <0 or 1> 0 is for SQL Server, 1 is for PostgreSQL Server. If Metadatadbype is 1, provide the Postgres related details. By default SQL Server Metadata is selected.
    • AA_ELASTICSEARCH_BACKUP and AA_ELASTICSEARCH_BACKUP_FILE parameters are used when you install an Control Room as a backup server.
    • If the Elasticsearch password does not exist in the ES_SETTINGS table of the database, you must provide the Elasticsearch authentication password in the installer parameter AA_ESPASSWD.
  2. Optional: Edit the sample script to use a Microsoft SQL Server database.
    Use the script to install the Control Room with the configuration options available in the installer.
    1. Correct values for variables such as: $service_username, $service_pwd, $db_server, $cr_port.
    2. Run the script with the credentials in Service log on, and a non-secure connection using Microsoft SQL Server authentication with a new database.
    Sample Microsoft SQL Server script:
    $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"
    $elastic_password="Test@123"
    $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_ESPASSWD=$elastic_password /vAA_CRWCHTTPPORT=80 /vAA_CRWCHTTPSPORT=443 /vAA_CRSELFSIGNCERT=1 
        /vAA_CRWCCERTPATH=$certpath /vAA_CRWCCERTPASSWD=$certpass /vLAUNCHPROGRAM=1 
        /v""/LIweamoruc! 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_2_0-07272018-10234948.exe"
    
    Write-Host $a
    Write-Host "Starting the installation. This could take some time..."
    $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
  3. Optional: Edit the sample script to use an Oracle Database database.
    Use the script to install the Control Room with the configuration options available in the installer.

    $AA_ORCLINSTANCETYPE="1" and $AA_ORCLINSTANCEVALUE="ORCL" replace $ORCLSID="ORCL"

    $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"
    
    $elastic_password="Test@123"
    
    $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_ESPASSWD=$elastic_password /vAA_CRWCHTTPPORT=$cr_port /vAA_CRWCHTTPSPORT=443 /vLAUNCHPROGRAM=1 
        /v""/LIweamoruc! 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
  4. Save the script you edit to the server for installation.
  5. On the installation server, logged on as an Administrator, open PowerShell in admin mode and execute:
    Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
  6. Start Powershell in admin mode and execute:
    .\install.ps1
    Note: The silent installation logs are stored in the folder from which the installation script is executed. For example, if you run the script from C:\Silent Install, the logs are stored in the C:\Silent Install folder.
  7. Optional: Install a hot fix patch of Control Room in silent mode.
    1. Ensure the PowerShell script is located in the same directory as the Control Room installer.
    2. Launch the Windows command window in administrator mode.
    3. Change to the directory where the installation files are stored.
    4. Run the Control Room installer.
      C:\Setup>./"Automation Anywhere Enterprise_Update_11.3.x.x.exe" /s /v/qn
    5. View the installation progress. From the Control Room, select Task Manager > > Background processes.
      The machine restarts when installation is complete.

Next steps

Complete Control Room configuration and validation.

Control Room post-installation configuration
After installing the Control Room, complete the configuration settings to ensure timely Automation Anywhere communications are specified, confirm Automation Anywhere services are running, configuring the Access Manager reverse proxy and Control Room authentication options, and installing a license.
Control Room post-installation validation
After installing the Enterprise Client and completing the post-installation tasks, validate the Enterprise Client by logging in to the Control Room and installing a license. First time access to the Control Room walks you through configuration for your authentication method.

Prepare for users.

User management overview
As a Control Room admin, you can create, view, edit, delete, and enable or disable user accounts. Creating user accounts depends on the non-Active Directory, Active Directory, or single sign-on (SSO) credentials from an IdP server.
Enterprise Client installation
Review the installation core tasks and topics for installing Enterprise Client on any machine running a supported operating system.
Envoyer le commentaire