Continue from the Control Room installer to the Database type wizard page. Use this page to configure the Microsoft SQL Server database for use with the Control Room.

This procedure applies only to Microsoft Windows Server based installations.

Linux users: See Installing Enterprise Control Room on Linux - Database configuration.

If you are installing Automation 360 as part of migration, this task includes the step to select the Enterprise 11 (cloned) database.

Procedure

  1. Select the Microsoft SQL Server database.
    An instance of the SQL Server should be already configured.
  2. Click Next.
    The Database Server page is displayed (if you selected SQL Server for configuring your database).
  3. Set the connection and authentication for the database server.
    To configure the Database Server for the Control Room instance, use the default Database Server port 1433. If multiple instances are running on the same database host on different ports, you can use the corresponding custom port for that instance (for example, 1435 or 1437).
    Note: The instance name is not supported in the Database Server field.
    Note:
    • If possible, do not set the value for Database Server as localhost. If you must use localhost, note that the Secure Connection to the database will not work.
    • Click Browse to select the SQL Server instance where the Control Room database will be created. Alternatively, enter a database server name or select one from the list.

    Migration task: If you are migrating from Enterprise 11 to Automation 360, browse to the restored Enterprise 11 database.

    Provide the following details:
    1. Database Port: Use the default port (1433) or specify a custom value.
      Configure default database port
    2. Use Secure Connection: Select to use a CA certificate as specified.
      Note: Use the same host name for certificate and database connections.
    3. Certificate: This option is enabled when you select Use Secure Connection.Browse to select a CA certificate.
      Import HTTPS SSL, intermediate, and CA certificates
    4. Select one of the following for database authentication:
      • Windows authentication: This option is selected by default and allows connection to the SQL Server using Windows authentication.
        Note: If you select Windows authentication, then the user running the installer is used to test that the database exists, create it if required, and grant db_owner to the service account user (NT Authority/System).
      • SQL Server authentication: (manually enter credential) Select this option to use SQL Server authentication to connect to the database. Provide the correct user name and password for SQL authentication.
        1. Enter username.
        2. Enter password.
      • SQL Server authentication: (retrieve credential from external key vault) Select this option to use SQL Server authentication to connect to the database.
        Note: SQL Server Authentication is required if you will retrieve the credentials for the database from an external key vault.
        1. If using CyberArk, enter the safe name and object name.
        2. If using AWS Secrets Manager, enter the secret name.
        3. If using HashiCorp Vault, enter the HashiCorp secret name.
      • AD Azure authentication: Select this option to use Microsoft Azure Active Directory credentials to connect to the database when you install the Control Room on Microsoft Azure.
      Use only supported characters for the user name and password. See Supported special characters in usernames and passwords. Do not use semicolons ( ; ) in the database password.
    5. Name of Control Room database: Enter the name of the Control Room database.
    The following sample illustration shows SQL Server authentication for database connection:Image with SQL Server authentication
  4. Click Next to provide the Elasticsearch credentials.
    Add OpenSearch credentials