Installation Guide

Create a pilot Alloy Navigator database

Updated in 2021.2

NEXT STEP: Activate the pilot database and start the Automation Server of the latest version. For activation instructions, see Activating the product.

This step imports all Alloy Navigator data (i.e. the configuration information and data records) from your production database to a new database of the latest version. That new database will serve as the pilot database.

INFO: For details, see Pilot upgrade.

The pilot upgrade procedure requires a pilot database to reside on the same SQL Server instance where your existing production database resides.

To create a pilot database:

  1. Run the Database Management tool for Alloy Navigator and click Next to continue.

  2. On the Task page, select Manage Existing Database option and click Next. The Source Database page opens.

  3. Specify the information to connect to your production (source) database.

    1. Enter the name or IP address of the SQL server where your production database is hosted. The new database will be created on the same instance.

      NOTE: If you are connecting to a named SQL Server instance, it must be specified in the form Servername\Instancename; for example: SQLSERV001\SQLEXPRESS. If the server uses a non-standard port, add the port number, separating it with a comma; for example, SQLSERV001\SQLEXPRESS,5618.

    2. Provide your credentials to log on to the SQL Server using an account with the sysadmin role on the SQL Server:

      • To use your Windows account, choose Windows Authentication.

      • To use your SQL Server account, choose SQL Server Authentication and type your account name and password.

    3. Choose the name of the production (source) database from the drop-down list.

    Click Next. The Upgrade Scenario page opens.

  4. Select Pilot Upgrade and click Next. The Pilot Upgrade page opens.

  5. Select Create Pilot Database and click Next. The Target Database page opens.

  6. Enter a name for the pilot database.

    TIP: If you are going to follow our recommendations and "flip" the databases at the final step, choose a temporary name (for example, add _Pilot to your production database's name). If you plan to make your pilot database the production one, choose a meaningful name.

    Click Next. The Backup Location page opens.

  7. On the Workflow Upgrade page, choose the workflow migration option that suits your needs. Click Next.

    INFO: For details, see Workflow upgrade options.

  8. If the New Permissions page appears, view your existing security roles and permissions on new functionality and objects introduced in the new version.

    INFO: For details, see New permissions.

    To assign new permissions to all members of an existing security role:

    1. Select a role in the left hand pane.

    2. Click the plus icon (+) to expand object class nodes.

    3. Using available check boxes, select the new permissions this role should grant. To select or deselect all permissions in the list, click Select All or Deselect All, respectively.

    Click Next.

  9. On the Backup Location page, browse for a folder on the SQL server for the database backup file and specify its file name. The pilot upgrade will not affect your production (source) database, however, a backup copy is required for the upgrade process.

    Click Next. The Database Account page opens.

  10. Specify the account for accessing the database.

    INFO: For details, see Database Account.

    Provide the credentials for an existing SQL Server account that will serve as the Database Account. Alternatively, click Create SQL Server Account and create a new SQL Server account for this task.

    Click Next. The Database Access Key page opens.

  11. Once you specified the Database Account, the Database Management tool generates a unique Database Access Key. A registered copy of this key must exist on each computer that requires access to the pilot database.

    INFO: For details, see Distributing the Database Access Key.

    By default, the key is exported into the [KeyName].reg file on your desktop. To change the default path or name, click the ellipsis button and specify a new location.

    Click Next.

  12. If the Breaking Changes page appears, review the changes that may affect your system.

    INFO: For details, see Backward-incompatible changes.

    Click Next.

  13. On the Ready to Proceed page, click Next to proceed. Click Back if you need to make any changes. The process may take considerable time depending on the size of your production database.

  14. Once the pilot database is created, the Summary page opens. Review the details about your newly created pilot database and click Finish to complete the process.

  15. Now you need to activate the new database. The activation process starts immediately after you click Finish. The License Management window opens.