Upgrade Through a Pilot Database

On this page

A pilot upgrade lets you test the new version while your production system stays in use, and switch to production when the pilot is ready. The Database Management wizard offers this scenario as Pilot Upgrade: "Test-drive the new version in a pilot environment and switch to production when ready."

The pilot route runs in three wizard steps:

  • Create Pilot Database restores a backup of the production database into a new database, the pilot, and brings it to the new version. The production database is left as it was.
  • Update Pilot Data copies the current production data onto the pilot again and keeps the pilot's own configuration. You can repeat it.
  • Switch to Production is the final run, which makes the pilot your production database.

The pilot route accepts an Alloy Navigator database of version 6.0 or later. For a database of version 7 or earlier it is the only route, because the in-place production upgrade accepts a database of version 8.0.0 or later; see Upgrade a Production Installation. The pilot steps are not available on Azure SQL, where the Upgrade Scenario page hides Pilot Upgrade and selects Production Upgrade. To move an Alloy Navigator Express database, see Migrate from Alloy Navigator Express.

Production stays in use while you test because Create Pilot Database leaves the production database as it was, and the pilot runs with every job turned off except the business rules and with sending from its notification queue paused. The production system is taken down only when the switchover begins.

The pilot upgrade in order

  1. Install: install the new Alloy Navigator server components, create the pilot database with Create Pilot Database, and install and configure the web applications for the pilot.
  2. Test: start the Automation Server and the Inventory Server for the pilot, test the pilot database, and, optionally, run Update Pilot Data.
  3. Switch to production: stop the production Automation Server and Inventory Server, force the users to log off, and stop the Automation Server and Inventory Server of the pilot. Upgrade the Alloy Navigator server components, run Switch to Production, and upgrade the web applications. Reconfigure the web applications, and point Alloy Discovery Synchronization at the production Alloy Discovery database and the Mail Connector at the support mailbox. Delete the test notifications and resume the notification queue, start the production Automation Server and Inventory Server, and upgrade the client components.
  4. Additional steps: optionally, update the archive databases, uninstall the previous version, and remove the SQL Server accounts you no longer need.

Alloy Navigator does not enforce this order. Forcing the users to log off and stopping the servers are your steps: the Database Management wizard performs neither.

Before you begin

  • Your SQL Server login must be a member of the sysadmin fixed server role. Otherwise the wizard stops at the Target Database page with "You must be a member of the sysadmin role on the specified SQL Server instance. Please contact your system administrator."
  • The wizard creates the pilot database on the SQL Server instance that hosts the production database, and opens it with the login you give on the Source Database page.
  • Unlike the in-place production upgrade, the pilot steps do not refuse a database that takes part in SQL Server replication.

Install the server components for the pilot

In the Installer

Install the new Alloy Navigator server components with the Alloy Navigator setup program; see Install the Server Components.

Create the pilot database

In the Database Management wizard

IMPORTANT: Choosing Install Default Workflow replaces the workflow configuration: it clears every configuration record that is not a system record. The version-by-version configuration updates do not run with this choice.

  1. Start the Database Management wizard. On the Task page, Upgrade your existing database, the button above the Manage Existing Database label, is preselected.
  2. On the Source Database page, specify the production database.
  3. If the Upgrade Scenario page appears, choose Pilot Upgrade. The page appears for a database of version 8.0.0 or later that is older than the wizard. For a database of an earlier version, or one already at the wizard's version, the wizard goes straight to the pilot page.
  4. On the Pilot Upgrade page, click Create Pilot Database. The page is titled Pilot Testing when the production database is already at the wizard's version.
  5. On the Target Database page, enter a name for the pilot database in Database. The wizard rejects an empty or invalid name. If a database of that name already exists, the wizard asks "The database '<name>' already exists. Delete the database?" and deletes it only when you click Yes.
  6. Complete the additional pilot-creation pages that apply to your choices.
  7. On the Ready to Proceed page, start the run. The wizard shows the Progress Status page and, after the run, the Summary page.
  8. On the Summary page, click Finish.

Additional pilot-creation pages

  • Database Files, when you use the advanced options on the Target Database page.
  • Workflow Upgrade, where you can choose Install Default Workflow. For what it replaces, see Upgrade Considerations.
  • New Permissions, shown only when permissions were introduced after the production database's version. The page lists Existing Roles: against New Permissions:; grant each new permission to roles with its check box. Five permissions are never on the list, and the wizard neither grants nor denies them.
  • Backup Location, where you enter the backup file of the production database in Back up the production database to:. The file is created on the computer where SQL Server runs. This backup cannot be turned off: an empty field is refused with "Please enter the name of the backup file.", and the wizard asks for confirmation when the file already exists.
  • Database Account and Database Access Key.

What Create Pilot Database does:

  • It restores the backup of the production database into the pilot database and leaves the production database as it was.
  • It turns off every job of the pilot except the business rules (Trigger On Condition jobs): Recurrent Ticket, Mail Connector, Active Directory Import, Reporting, Alloy Discovery Connector, Archiving, Scheduled Task, and AlloyScan jobs are turned off. Apart from being turned off, the jobs keep the settings they had in production, such as their mailboxes and inventory connections. The wizard does not turn any job on again.
  • It pauses sending from the pilot's notification queue.
  • When the pilot database is not activated, Finish starts the Settings App on it, logging in automatically when the saved startup login uses Windows authentication or names a user. For an activated pilot, Finish starts nothing.

A database of an earlier version gets the one-time conversions of the older upgrade steps; see Upgrade Overview.

Install the web applications for the pilot

The recommended place for the pilot web applications depends on the version you upgrade from:

  • From version 8 or later: install the Web App, the Self Service Portal, and the API on a virtual machine or a separate computer dedicated to testing, different from the IIS server that hosts the production web applications. To go to production later, you install them again on the production web server, as an upgrade of the existing ones.
  • From version 7 or earlier: install them on the production web server, but in a new, different web site that serves as the pilot site, with a temporary name such as "Alloy Navigator Pilot Site", and put each application instance in its own virtual directory. To go to production later, you reconfigure the new applications onto the URLs that users already access.

In the Installer

Install the Web App, the Self Service Portal, and the API from the Advanced Installation page of the installer. The order of installation does not matter. On the finish page of each setup, keep Run the Web Configuration selected when the setup offers it. A setup does not offer it when the package is already installed or when the setup upgrades an earlier installation. See Install the Server Components.

In the Web Configuration tool

Configure each instance against the pilot database:

  1. On the Database page, import the pilot database's Database Access Key with Import Key....
  2. For a pilot site on the production web server, choose Install into a virtual directory and select the pilot site.

The Web Configuration tool refuses a virtual directory whose folder overlaps the folder of another instance. For the tool's pages, see Publish the Web Applications.

Test the pilot

While you test, the pilot runs with its jobs turned off, except the business rules, and with sending from its notification queue paused: the notifications that the pilot creates are queued but not sent. If you turn a job on in the pilot, remember that it still has its production settings, such as its mailbox and inventory connection.

In the Automation Server Manager

Start an Automation Server for the pilot. The Automation Server connects only to a database whose version matches its own, so the Automation Server for the pilot is one of the new version. To connect it to the pilot database and start it, see Configure the Automation Server. While sending from the pilot's notification queue is paused, the Automation Server sends nothing from it.

In the Inventory Server Manager

The Inventory Server loads network inventory information into Alloy Discovery. On the computer that runs the Inventory Server for the pilot, open the Inventory Server Manager from the Alloy Control Panel. Its Connection group shows Key:, SQL Server:, and Database:, with the Import Key... and Test Connection buttons; the form has no user name or password field. When the manager finds no valid key, it shows "Unable to find a valid Database Access Key. Please import your Database Access Key before configuring the Inventory Server." and opens the key import. If your account cannot manage the service, the manager warns "You do not have enough permissions to manage the Alloy Inventory Server." For the manager's Import Key..., Test Connection, and Start commands, see Upgrade a Production Installation.

In the Database Management wizard

Run Update Pilot Data to refresh the pilot with the current production data. You can repeat it.

  1. Start the wizard, keep Upgrade your existing database, and specify the production database on the Source Database page.
  2. If the Upgrade Scenario page appears, choose Pilot Upgrade.
  3. On the Pilot Upgrade page, click Update Pilot Data.
  4. On the Target Database page, select the pilot database. Keep Enable backup selected (it is preselected) if you want the wizard to back up the pilot first, and enter the backup file in Back up the pilot database to:. While Enable backup is selected, an empty backup file field is refused with "Please enter the name of the backup file.", and the wizard asks before it overwrites an existing backup file.
  5. On the Backup Location page, enter the backup file of the production database in Back up the production database to:.
  6. On the Ready to Proceed page, start the run.

What Update Pilot Data does:

  • It refuses to run unless the pilot database is already at the wizard's own version.
  • It saves the pilot's configuration, backs up the production database to the file named on the Backup Location page, restores that backup over the pilot, upgrades the data, and then puts the pilot's configuration back. Configuration you change in production after you created the pilot is not carried over. The pilot's jobs come back as they were on the pilot.
  • It disconnects everyone who is working in the pilot when it restores the production data over the pilot.
  • It deletes the Workflow Log entries that come with the production data.
  • It pauses sending from the pilot's notification queue again.

Take the production system down

When the pilot is ready, take the production system down in this order: stop the production Automation Server and Inventory Server, force the users to log off, and then stop the Automation Server and Inventory Server of the pilot. A server left running reconnects and retries on its connect interval once the database version changes, and Switch and Flip disconnects it rather than waiting.

In the Automation Server Manager

The Automation Server runs as a Windows service. Stop the production Automation Server, and later the pilot's; see Upgrade a Production Installation.

In the Inventory Server Manager

The Inventory Server runs as a Windows service. On every Inventory Server computer, stop the production Inventory Server, and later the pilot's; see Upgrade a Production Installation.

In the Settings App

Force the users to log off with the User Sessions manager: terminate their sessions. Each client sees the termination, shows "Your Alloy Navigator session has been terminated by the administrator." and closes. See User Sessions.

Switch to production

In the Installer

Upgrade the Alloy Navigator server components; see Upgrade a Production Installation.

In the Database Management wizard

  1. Start the wizard, keep Upgrade your existing database, and specify the production database on the Source Database page.
  2. If the Upgrade Scenario page appears, choose Pilot Upgrade.
  3. On the Pilot Upgrade page, click Switch to Production (the button reads Move To Production).
  4. On the Switchover Options page, choose Switch and Flip (preselected) or Switch.
  5. On the Target Database page, select the pilot database, and keep or clear Enable backup as for Update Pilot Data.
  6. Complete the pages the wizard shows next:
    • Backup Location, for the backup of the production database.
    • Database Access Key, for Switch and Flip.
    • Automatic Upgrade, when the production database is at version 7.2.0 or later and older than the wizard; there you can store the client setup program in the database. When a valid setup program is already at the page's default location, the wizard skips the page and uses that one. See Upgrade Clients Automatically.
  7. On the Ready to Proceed page, start the run. After the run, click Finish on the Summary page.

Switch to Production shows no Database Account page. It refreshes the pilot the same way Update Pilot Data does, so the pilot keeps its own configuration and jobs, and the Workflow Log entries that come with the production data are deleted. The two options differ as follows:

  • Switch and Flip sets the production database to single-user mode first, so open sessions are disconnected and their transactions rolled back rather than waited for. After the refresh, it renames the production database to <name>_SAVE (or <name>_SAVE_2, <name>_SAVE_3, and so on, while the name is taken), gives the pilot the production database's name, creates a Database Access Key for it, and takes the renamed production database offline. It also turns sending from the notification queue back on.
  • Switch leaves the production database online under its own name and the pilot online under its own name. Sending from the pilot's notification queue stays paused.

The wizard does not turn any job on again: after Switch to Production, the jobs are as they were on the pilot.

Move the web applications to production

In the Installer

From version 8 or later, where the pilot web applications ran on a separate computer, install the Web App, the Self Service Portal, and the API again on the production web server, as an upgrade of the existing ones; see Upgrade a Production Installation.

In the Web Configuration tool

From version 7 or earlier, where the pilot web applications ran in a pilot site on the production web server, reconfigure the new applications onto the URLs that users already access.

After Switch and Flip, the pilot has the production database's name, so an instance's stored connection reaches the new database without change. After Switch, every instance still addresses the previous database. To point an instance at the new production database:

  1. In the instance tree, right-click the instance and click Configure > Database.
  2. On the Database page, choose the key in the Key: list, or import it with Import Key....
  3. On the Ready to Apply Settings page, apply the settings. The tool restarts the web application.

Configure > Full adds the web pages to the Database page; Configure > Web leaves the Database page out. No reconfiguring of an existing instance corrects a link macro that already has a value.

In the Settings App

After Switch to Production, the link macros that workflow notifications use to address the web instances, Web Portal Link, Self Service Portal Link, and API Link, hold whatever the pilot database held. Correct them in the Links group of the Settings App.

Finish the switchover

Point Alloy Discovery Synchronization at the production Alloy Discovery database and the Mail Connector at the support mailbox; see Alloy Discovery Synchronization and Mail Connector Jobs. Then delete the test notifications and resume sending, start the production servers, and, last, upgrade the client components; see Upgrade Clients Automatically.

In the Settings App

Open Notifications > Notification Queue. While sending is paused, the status reads Paused (notifications are being queued but not sent) and shows Paused by <person> at <date>.

  1. Select the test notifications that accumulated in the paused queue and click Delete.
  2. Click Resume to resume automatic sending.

After Switch and Flip, the wizard has already turned sending back on, so there is nothing to resume. See Notification Queue.

In the Automation Server Manager

Start the production Automation Server; see Upgrade a Production Installation. Start it after you resume sending: an Automation Server sends nothing from the queue while sending is paused, so the notifications stay queued.

In the Inventory Server Manager

Start the production Inventory Server; see Upgrade a Production Installation.

Additional steps

The wizard leaves the previous database, the backup files it wrote, and the SQL Server logins in place: after Switch and Flip, the <name>_SAVE database stays on the server offline, and after Switch, both databases stay online. Removing them is up to you.

In the Settings App

Archive databases are not converted by the Database Management wizard. The Settings App converts an archive database of a version earlier than 8.0.0 when you select it in the archived databases manager: it asks "To view this archive database, you must update it to the latest format. The update process may take considerable time." and converts it only when you click Yes.

In the Installer

The previous version is uninstalled by the installers. An unattended run of the Alloy Navigator setup program uninstalls an installed Alloy Navigator 6 or 7 by itself unless OLD_PRODUCT=Keep is also passed; see Unattended Installation.