Read and Review Automation Anywhere Documentation

Automation Anywhere Version 11.3

Close Contents

Contents

Open Contents

Connect to source Bot Insight database

  • Updated: 4/15/2020
    • 11.3.x
    • Explore
    • Bot Insight

Connect to source Bot Insight database

If installed, provide the source Control Room Bot Insight database setting and configuration details.

Prerequisites

The Connect to source Control Room database task must be completed successfully before you can complete this task.
Connect to the source Bot Insight database by doing the following steps:

Procedure

  1. In the Database tab of the Migration wizard, select Connect to 10.x Bot Insight database.
    All fields for the Bot Insight database connection are enabled.
  2. Select the Use secure connection option if the SQL instance hosting the source Bot Insight database is configured with a secure connection.
  3. Provide the host name and port number of the SQL Server on which the source Bot Insight database is hosted.
  4. Depending on the configured authentication method for SQL Server, do the following:
    1. Microsoft Windows: Keep the Use Windows authentication selected if the source SQL Server is configured using Microsoft Windows authentication.
    2. SQL Server: Clear the selection and provide the Username and Password, if the SQL Server is configured with SQL authentication.
  5. Type the source Control Room Bot Insight database name.
  6. Type the Server URL where the Bot Insight Visualization Server Port is configured.
    For example: http://productlt.example.com:82/analytics.
  7. Click Save to connect to the database.
    After you click Save, the Control Room verifies the data provided in the preceding steps.
    • If a connection to the SQL server cannot be established, a message is shown suggesting the following:
      • The secure connection is not set correctly.
      • The server host name, port, or database name is incorrect.
      • The Use Windows authentication option is not selected.
      • The username or password is incorrect.
    • If the Master key is invalid, a message instructs you to retry.
    • If the Repository path is incorrect, not shared, or inaccessible, a message advises you to verify that the path is correct and mapped to a shared drive with the required permissions.
  8. Click Next to select migration of data based on roles, users, or bots.
Send Feedback