Migrate from Alloy Navigator Express
On this page
Off Azure SQL, the Database Management wizard moves an Alloy Navigator Express database into a new Alloy Navigator database through the same three pilot steps that other migrations use: Create Pilot Database, Update Pilot Data, and Switch to Production. The migration accepts an Express database of version 6.2.0 or later.
Create Pilot Database restores a backup of the Express database into a new database and leaves the Express database in place. Update Pilot Data can be repeated, and Switch to Production is the final migration run.
On Azure SQL, the Database Management wizard offers Production Upgrade for an Express database: the Upgrade Scenario page has Production Upgrade selected and hides Pilot Upgrade, so the pilot steps are not available there. For the upgrade paths in general, see Upgrade Overview.
What the migration converts
The migration converts your Express data for use in Alloy Navigator:
- Work orders gain the Alloy Navigator organization link.
- The Express stock room is normalized.
- Class names are corrected.
- Two Tracked Software permission IDs are renumbered.
- The Express Work Order classification (lifecycle stages, statuses, impacts, and the rest) is copied onto the Incident class, skipping any name that already exists there.
For an Express database below version 8.3.0, the migration also gives every security role that holds a Person right to add, edit, view, or delete the matching Group right.
If your Express database is already at the current version, the wizard skips the version-by-version upgrade and still runs the data conversion.
What happens to the workflow configuration
In the new database, Create Pilot Database always replaces the workflow configuration that came from the Express database; the Express database itself is left as it was. It clears the workflow configuration of the new database and then loads the Default Workflow (see Default Workflow Configuration). The choice between Keep Existing Workflow and Install Default Workflow is offered only for a pilot made from an Alloy Navigator database, so a migration from Express has no way to keep the Express workflow. Update Pilot Data and Switch to Production do not load the Default Workflow again: they put the pilot's own configuration back.
The clear deletes the following from the new database:
- Every form and every ticket template.
- Every Recurrent Ticket job.
- Every workflow configuration parameter and parameter category.
- Every entry of the Workflow Log.
- The actions, triggers, scheduled tasks, functions, and macros, except the built-in ones.
- The entries of classification lists, such as lifecycle stages, statuses, types, categories, closure codes, urgency, impact, and priority values, personal titles, e-mail types, relationship types, and workspaces, except the built-in ones. Every entry of the list of voting methods is deleted.
The clear leaves dashboards and their role assignments, role memberships, and personal views in place. The load then writes the shared views, web views, dashboard views, and security roles of the Default Workflow into the database, replacing the matching records; shared views that were created in the Express database stay. The load does not update dashboards or widgets, and it leaves existing records such as services, groups, and announcements as they are.
After the load, the wizard still runs the configuration updates that an upgrade from the Express database's version includes, except the updates from versions before 7.0.0.
For an Express database below version 8.0.0, Create Pilot Database also points the Alloy Discovery Connector jobs at the actions New Person (Alloy Discovery Connector) (New 8.0.0), New Computer (Alloy Discovery Connector) (New 8.0.0), and Update Computer (Alloy Discovery Connector) (New 8.0.0) and at two Chromebook actions. It deletes the other Alloy Discovery Connector create and update actions, apart from New Hardware (Alloy Discovery Connector), Update Hardware (Alloy Discovery Connector), and the actions that a job's hardware options name, and it deletes every other Chromebook action. It does not change a job's inventory database connection.
For an Express database below version 8.0.0, Create Pilot Database also points each Active Directory Import job's person create and update actions, where the job names them, at New Person (Active Directory Sync) (New 8.0.0) and Update Person (Active Directory Sync) (New 8.0.0), and points the Self Service Portal's person-creation action setting at the first of them. It then deletes every other Active Directory create and update action.
For an Express database below version 7.0.0, Create Pilot Database also gives every product that has no status the Active status of the product class. Active is one of the product statuses of the Default Workflow.
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 Express database, and opens it with the login you give on the Source Database page.
In the Database Management wizard
Data loss when you migrate an Express database below version 8.3.0:
If the Express database you migrate is of a version below 8.3.0, the migration deletes the following in the new Alloy Navigator database:
- The History and Activity of every Change Request.
- The records of the Change Requests in the object index.
- Every entry of the Change Request classification lists: statuses, types, categories, closure codes, impacts, priorities, and urgencies.
- The History of computers, hardware, and assets.
The Express database itself stays in place, but that does not prevent this loss: the deletions happen in the new database. Back up the Express database before you migrate it, and check the result of the migration on a separate copy first.
Create the pilot database
- Start the Database Management wizard. On the Task page, Upgrade your existing database is selected.
- On the Source Database page, specify the connection in the Connection details group: SQL Server, Authentication (Windows Authentication or SQL Server Authentication), Login, and Password. Then select the Express database in Database. If the database's version is later than the wizard's, the wizard stops on the Execution Error page with "The database you are connecting to is not of the expected version."
- On the Pilot Upgrade page (titled Pilot Testing when the Express database is already at the wizard's version), click Create Pilot Database.
- On the Target Database page, enter a name for the new database. The wizard rejects an empty or invalid name. If a database of that name exists, the wizard asks "The database '<name>' already exists. Delete the database?", and deletes it only when you click Yes.
- Complete the pages the wizard shows next: Database Files (when you use advanced options), Backup Location for the backup of the Express database, Database Account, and Database Access Key. On Backup Location, an empty file field is refused with "Please enter the name of the backup file.", and the wizard asks for confirmation when the file already exists.
- On the Ready to Proceed page, click Next to start the run. The Progress Status page shows the progress of the run. If the run fails, the wizard shows the Execution Error page with "The wizard couldn't complete the requested action due to an error. Remove the cause of the error and restart the wizard."
- On the Summary page, click Finish.
What Create Pilot Database does:
- It restores a backup of the Express database into the new database.
- It disables 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. The wizard does not turn any job on again. Apart from being turned off, the jobs keep the settings they had in the Express database, such as their mailboxes and inventory connections, except where the workflow replacement changes them: the clear deletes every Recurrent Ticket job, and for an Express database below version 8.0.0 the Alloy Discovery Connector and Active Directory Import jobs are pointed at other actions (see What happens to the workflow configuration).
- It pauses sending from the pilot's notification queue.
- It removes the license from the new database, so a pilot made from an Express database always starts unactivated. When you click Finish, the wizard starts the Settings App on the new database. It logs you in automatically when the saved startup login uses Windows authentication or names a user. Activate the new database there (see Activate the pilot database).
The Workflow Upgrade, New Permissions, and Automatic Upgrade pages are not part of a migration from Express.
Update the pilot data
Update Pilot Data refreshes the pilot with the latest data of the Express database. You can repeat it.
- Start the wizard, keep Upgrade your existing database, and specify the Express database on the Source Database page.
- On the Pilot Upgrade page, click Update Pilot Data.
- On the Target Database page, select the pilot database. Keep Enable backup selected (the default) 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.
- Complete the remaining pages, including Backup Location for the backup of the Express database. On the Ready to Proceed page, click Next to run the step.
What Update Pilot Data does:
- It saves the pilot's configuration, backs up the Express 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 the Express database 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 Express data over the pilot.
- It deletes the Workflow Log entries that come with the Express data.
- It pauses sending from the pilot's notification queue again.
- It refuses to run unless the pilot database is already at the wizard's own version.
Switch to production
Before you switch, force users to log off and stop the Automation Server and Inventory Server services of the previous version. These are your steps; the wizard does not perform them.
- Start the wizard, keep Upgrade your existing database, and specify the Express database on the Source Database page.
- On the Pilot Upgrade page, click Switch to Production (the button reads Move To Production).
- On the Switchover Options page, choose Switch and Flip (selected by default) or Switch.
- On the Target Database page, select the pilot database, and keep or clear Enable backup as for Update Pilot Data.
- Complete the remaining pages, including Backup Location and, for Switch and Flip, Database Access Key. On the Ready to Proceed page, click Next to run the step.
Switch to Production refreshes the pilot the same way Update Pilot Data does, so the pilot keeps its own configuration and jobs. The two options differ as follows:
- Switch and Flip sets the Express database to single-user mode before it backs it up, so open sessions are disconnected and their transactions rolled back. After the refresh, it renames the Express database to
<name>_SAVE(or<name>_SAVE_2,<name>_SAVE_3, and so on, while the name is taken), gives the pilot the Express database's name, creates a Database Access Key for it, and takes the renamed Express database offline. It also turns sending from the notification queue back on. A component that still addresses the old database name now reaches the new Alloy Navigator database. - Switch leaves the Express database online under its own name and the pilot online under its own name. Nothing in the product stops the Express database from continuing to be used. Sending from the pilot's notification queue stays paused.
The wizard leaves the previous database, the backup files, and the SQL Server logins in place: after Switch and Flip, the <name>_SAVE database stays on the server offline. Removing them is up to you. Taking the Express system out of use involves no license step.
In the Settings App
Activate the pilot database
The license is stored in the database. It is activated either over the Internet, with an e-mail address and serial number, or from a license key file (*.dat). Activation over the Internet needs outbound Internet access; activation from a file does not.
The License Management page is under General. While the database has no valid license, the Settings App opens on this page alone, with the navigation tree hidden, so it is the page you see after Finish on Create Pilot Database. On a database with no license, the page's panel reads Activate followed by the product name, and its status line reads "Alloy Navigator needs to be activated before use."
- On the License Management page, select Over the Internet or From file, and click Activate.
- For Over the Internet, enter the E-mail address and Serial number in the Activation via Internet window, and click Activate. For From file, select the license key file in the Open License Key File... dialog.
A first activation ends with "You have successfully activated the <product>." A license key that fails the license checks is refused with "The specified license key is not valid. You cannot activate the product using this license." and the reason.
Delete the test notifications and resume sending
While the notification queue is paused, the Queue status group of the Notification Queue page reads Paused (notifications are being queued but not sent), and the page shows Paused by <person> at <date>.
- In the Settings App, go to Notifications > Notification Queue.
- To delete the test notifications that accumulated in the paused queue, select them in the grid, click Delete, and confirm.
- To resume sending, click Resume in the Queue status group.
After Switch and Flip, the wizard has already resumed sending, so there is nothing to resume. An Automation Server started before you resume the queue leaves the notifications queued.
Correct the link macros
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. Reconfiguring an existing web instance in the Web Configuration tool does not correct a link macro that already has a value. Correct them in the Settings App, in its Links group.