Titan migration utility
The Titan DB Migration utility is used to populate a new (blank) Security Commander database with data from up to 16 Challenger panels in a Titan
system consisting of:
• Control panel programming settings only, or
• Control panel programming settings and users
The Titan DB Migration utility migrates data from a .zip file created from Titan’s System Maintenance Utility (Export tab).
• Titan Photo ID is not migrated to Security Commander.
• Titan DB Migration may only be used with Titan version 3.2 (or later) installed on the Security Commander server PC.
If there is already an earlier version of Titan installed, then you must upgrade it before you can use this utility.
•You can download Titan from http://www.interlogix.com.au/downloads (it does not need to be registered in order for Titan DB Migration utility to work).
Importing a Titan system
Security Commander must have been started at least one time before you run Titan DB Migration, otherwise you will receive an error message.
To use Titan DB Migration to populate a Security Commander database:
1. Run Titan DB Migration via the Start > All Programs > Tecom > Security
2. Click Browse to find the .zip file, and then click Open. All of the Challenger control panels contained in the .zip file are listed in the “Challengers to import”
3. Click to select the Challenger control panels to be migrated (from one system only). The migration process can be performed only one time because you can only
migrate into a blank Security Commander database.
4. Click the Options button if you want to modify some of the imported panels’ data.
•Type the name of the Challenger control panel in the Description field, or leave blank to use the name assigned in Titan.
• If one or more Facility records have been created in Security Commander, you can pre-assign a facility to the migrated Challenger control panel and
all of its applicable programming settings. Click the Facility arrow, and then select the required facility.
• Type a prefix text label that will be added to the start of a device label (and followed by a space), or leave blank to not prefix the device name used in Titan.
Security Commander Administration Manual and Operation Guide 109
• Type a postfix text label that will be added to the end of a device label (and preceded by a space), or leave blank to not postfix the device name used in Titan.
Click OK when finished defining options.
5.Click to select one of the following import options for all selected Challenger control panels to be migrated:
• Click to select “Challenger” to migrate only Challenger control panel programming settings
• Click to select “User/Badges” to migrate Challenger control panel programming settings and users
6. If you are migrating users/badges, select the following user options to apply to all migrated users:
• Click the User type arrow and select a personnel type. All migrated uses will be assigned the selected type.
• If one or more Facility records have been created in Security Commander, you can pre-assign a facility to the migrated users. Click the User Facility
arrow, and then select the required facility.
• Optionally apply a common name for any migrated users that don’t have names in Titan. The common name is applied to any blank name fields. For example, if the
common name is “Empty”, then a user with no first or last name would be migrated as “Empty Empty”.
• Select the “Use panel user number” radio button to use the Challenger control panel’s user numbers as the Security Commander’s employee numbers.
• Select the “Auto generate” radio button to create new employee numbers in Security Commander. You must also specify a starting number.
7. Click Start when finished defining import options and user options. For each Challenger control panel in sequence, Titan DB Migration displays a confirmation message after migrating’s the panel’s programming, and a second confirmation message after migrating’s the panel’s users until complete.
If any part of the migration fails, then the entire migration fails. After a failed migration, click the Logs tab to check for error messages.
Note: If you need to save the log for investigation, copy and paste the contents of the log into Wordpad (for example).