C•CURE Database Migration Guide

Access Control and Event Management 8200-2102-38

C•CURE v3.00 Rev. A

www.swhouse.com April 2022

C•CURE and Software House are registered trademarks of Johnson Controls.

The trademarks, logos, and service marks displayed on this document are registered in the United States [or other countries].
Any misuse of the trademarks is strictly prohibited and Johnson Controls will aggressively enforce its intellectual property
rights to the fullest extent of the law, including pursuit of criminal prosecution wherever necessary. All trademarks not owned
by Johnson Controls are the property of their respective owners, and are used with permission or allowed under applicable
laws.

Product offerings and specifications are subject to change without notice. Actual products may vary from photos. Not all
products include all features. Availability varies by region; contact your regional sales manager. This manual is proprietary
information of Johnson Controls. Unauthorized reproduction of any portion of this manual is prohibited. The material in this
manual is for information purposes only. It is subject to change without notice. Johnson Controls assumes no responsibility for
incorrect information this manual may contain.

© 2022 Johnson Controls. All rights reserved. JOHNSON CONTROLS, TYCO and Software House are trademarks of
Johnson Controls.

C•CURE Database Migration Guide 2

 Table of Contents

Preface 5
Finding More Information 6
Conventions 7
Software House Customer Support Center 8

Chapter 1 - C•CURE 9000 Database Migration Utility Overview and Installation 10

C•CURE 9000 Database Migration Utility Overview 11
Installation 12
Installation Requirements 12
Installing the C•CURE 9000 Database Migration Utility 12
Configuring the ODBC Connection for C•CURE 800 Environments 14

Chapter 2 - C•CURE 9000 Database Migration for C•CURE 800 Databases 17

Overview and General Requirements 18
The Migration Process 18
Records Migrated from C•CURE 800 Databases 19
Prerequisites for Migrating C•CURE 800 Databases 27
Obtaining an Activation Key for C•CURE 800 Database Migration 27
Accessing the C•CURE 9000 Database Migration Utility 27
Verifying Personnel Records 28
Migrating Records from C•CURE 800 Databases 30
Special Considerations When Migrating Records from C•CURE 800 30
Performing the Migration from C•CURE 800 32
Post-Export/Pre-Import Configuration Steps 35
Configuring System Variables in C•CURE 9000 35
Preparing Card Formats 36
Preparing CHUID Formats 37
Importing C•CURE 800 Records into the C•CURE 9000 System 38
Preparation for Importing C•CURE 800 Records into C•CURE 9000 38
The Import Process 38
The Import Sequence for C•CURE 800 Records 39
Post-Import Steps for C•CURE 800 Records 41
Resetting apC and iSTAR Controllers 41
Re-configuring Card Formats 41
Re-configuring/Importing Badge Layouts 41
Renaming Customer Field Labels 41
User-Defined Field Names 42
Reconfiguring Tour Stop Inputs 42

C•CURE Database Migration Guide 3

 Assigning Guards to Guard Tours 42
CCURE.INI Entries/System Variables Imported to C•CURE 9000 43

Appendix A - Importing Records into C•CURE 9000 44

Importing Records into C•CURE 9000 Overview 45
Creating an Import Definition in C•CURE 9000 46
Data Source Configuration 47
Specifying Matching Fields 49
Running Imports 50
Running an Import by Listening on Data from the Import Watcher 50
Running an Import Manually 52
Completed Imports 52
Viewing Import Results History 54

C•CURE Database Migration Guide 4

 Preface

The C•CURE 9000 Database Migration Guide is for new and experienced security system users responsible for installing the
C•CURE 9000 Database Migration Utility and migrating database records into a C•CURE 9000 system database.

In this preface

Finding More Information 6

Conventions 7
Software House Customer Support Center 8

C•CURE Database Migration Guide 5

Finding More Information
You can access C•CURE 9000 manuals and online Help for more information about C•CURE 9000.

Manuals
C•CURE 9000 software manuals are available in Adobe PDF format on the C•CURE 9000 install media.

You can access the manuals if you copy the appropriate PDF files from the C•CURE 9000 Installation install media
Manuals\CCURE folder.

The available C•CURE 9000 and Software House manuals are listed in the C•CURE 9000 Installation and Upgrade Guide, and
appear as hyperlinks in the online.pdf file on the C•CURE 9000 install media Manuals\CCURE folder.

These manuals are also available from the Software House Member Center website
(http://www.swhouse.com/TechnicalLibrary/TechLibSW.aspx).

Online Help
You can access C•CURE 9000 Help by pressing F1 or clicking Help from the menu bar in the Administration/Monitoring
Station applications.

C•CURE Database Migration Guide 6

Conventions
This manual uses the following text formats and symbols.

Convention Meaning

Bold This font indicates screen elements, and also indicates when you should take a direct action in a procedure.
Bold font describes one of the following items:
• A command or character to type, or
• A button or option on the screen to press, or
• A key on the keyboard to press
• A screen element or name

blue color text Indicates a hyperlink to a URL, or a cross-reference to a figure, table, or section in this guide.

Regular italic font Indicates a new term.

<text> Indicates a variable.

The following items are used to indicate important information.

Indicates a note. Notes call attention to any item of information that may be of special importance.
NOTE

Indicates an alternate method of performing a task.

TIP

Indicates a caution. A caution contains information essential to avoid damage to the system. A caution can
pertain to hardware or software.

Indicates a warning. A warning contains information that advises users that failure to avoid a specific action
could result in physical harm to the user or to the hardware.

Indicates a danger. A danger contains information that users must know to avoid death or serious injury.

C•CURE Database Migration Guide 7

Software House Customer Support Center

Telephone Technical Support

During the period of the Agreement, the following guidelines apply:
■ Software House accepts service calls only from employees of the Systems Integrator of Record for the installation
associated with the support inquiry.

Before Calling
Ensure that you:
■ Are the Dealer of record for this account.
■ Are certified by Software House for this product.
■ Have a valid license and current Software Support Agreement (SSA) for the system.
■ Have your system serial number available.
■ Have your certification number available.

Hours Normal Support Hours Monday through Friday, 8:00 a.m. to 8:00 p.m., EST. Except holidays.

Emergency Support Hours 24 hours/day, seven days a week, 365 days/year.

Requires Enhanced SSA “7 x 24” Standby Telephone Support
(emergency) provided to Certified Technicians.
For all other customers, billable on time and materials basis.
Minimum charges apply – See MSRP.

Phone For telephone support contact numbers for all regions, see http://www.swhouse.com/support/contact_technical_support.aspx.

EMEA
Hours: 8am to 6pm CET
■ Toll Free: +800 CALLTYCO or +800-2255 8926
■ Direct: +31 475 352 722

Local Direct Dial Numbers:

■ UK: +44 330 777 1300
■ Israel: +972-772 201 350
■ Spain: 900 99 31 61
■ Denmark: +45-4494 9001
■ France: 0800 90 79 72
■ Germany: 0800 1806 757
■ Italy: +39-0230 510 112
■ Belgium: 0800 76 452
■ Ireland: 1800943570
■ Nordic: 04494 9001
■ Greece: 00800-312 294 53

C•CURE Database Migration Guide 8

 ■ South Africa: +27-211 003 882
■ Russia: 81080020521031
■ Turkey: 00800-31923007
■ UAE: 800-03107123
■ Bahrain: 800-04127

Asia Pacific
Hours: 9am to 5pm CST
■ Toll Free: +800 CALLTYCO or (+800-2255 8926)
■ Direct: +86 21 61916510
■ China only Hotline: 4006711528
■ India only Hotline: 1-800-1082-008
■ Australia: 02-9684-3980

Latin America
■ Colombia: + 57 1 344-1422 +57 2 8912476 +57 4 2040519
■ Costa Rica: + 506 4000-1655
■ República Dominicana: +1 8292353047
■ El Salvador: + 503 21368703
■ Guatemala: + 502 22681206
■ Panamá: + 507 836-6265
■ Mexico: + 52 5585261801
■ Perú: + 511 6429707
■ Venezuela: + 58 212-720-2340
■ Buenos Aires: + 54 11 5199 3104
■ Santiago de Chile: + 56 2 3210 9662
■ Sao Paulo: + 55 11 3181 7377

C•CURE Database Migration Guide 9

 1

Chapter 1 - C•CURE 9000 Database Migration Utility

Overview and Installation

The C•CURE 9000 Database Migration Utility is a standalone software tool that you install and license separately from
C•CURE 9000. Use the procedures in this guide to prepare records for export, and to install, activate, and operate the
C•CURE 9000 Database Migration Utility.

In this chapter

C•CURE 9000 Database Migration Utility Overview 11

Installation 12
Configuring the ODBC Connection for C•CURE 800 Environments 14

C•CURE Database Migration Guide 10

C•CURE 9000 Database Migration Utility Overview
The C•CURE 9000 Database Migration Utility is a software tool provided by Software House to allow you to bring legacy
records currently stored in the C•CURE 800 database under management by C•CURE 9000. The utility exports the records
that you want to migrate, converting them into the XML format required for import into C•CURE 9000.

You purchase, license, and install this software utility separately from C•CURE 9000. Once installed, you can use the
C•CURE 9000 Database Migration Utility repeatedly on a specific database, but you cannot use the utility on more than one
database at a time, even for databases of the same type. You must purchase a unique activation key for each database that
requires a data migration. Each time you open and run the migration utility, you must enter the activation key to proceed. For
details about requesting and managing activation keys, see Obtaining an Activation Key for C•CURE 800 Database Migration
on Page 27.

C•CURE 9000 stores records in a Microsoft SQL Server database, and imports records as XML. However, C•CURE 800 does
not export records as XML. To be able to migrate records from this database to a C•CURE 9000 database, the records must
first be converted to XML files that conform to the C•CURE 9000 schema. The C•CURE 9000 Database Migration Utility
automatically establishes the necessary database connections, and converts specific C•CURE 800 records into the required
XML format.

The output of the C•CURE 9000 Database Migration Utility is a collection of XML files that conforms to the C•CURE 9000
schema. The migration utility places all files in a single folder. By placing all importable records in a single folder, you can use
the C•CURE 9000 Data Import function to add the records into C•CURE 9000. Because the migration utility performs the
necessary mapping from the legacy records to the C•CURE 9000 schema (in almost all cases), there is no need to configure
mapping during the data import.

When you run the C•CURE 9000 Database Migration Utility, it automatically creates a log file to indicate when records do not
export properly and to provide information about what occurred during the export. You can review these files and execute the
utility again to resolve export errors.

The C•CURE 9000 Database Migration Utility does not convert and export every type of record contained in C•CURE 800
databases. Although some records can be converted to objects that can be automatically mapped to the C•CURE 9000
schema, other record types cannot. For details about the migrated records, see the following:
■ Records from C•CURE 800 databases– Records Migrated from C•CURE 800 Databases on Page 19.

C•CURE Database Migration Guide 11

Installation
Software House provides an automated installer program to install the C•CURE 9000 Database Migration Utility on your
computer. The installer provides the application executable file, sub-folders for generated files, and documentation in PDF. If
necessary, the installer adds Microsoft .NET Framework to the system.

This section describes minimum requirements for the computer on which you install the C•CURE 9000 Database Migration
Utility. It also describes the procedures required to install and activate the utility.

Activating the migration utility requires entering an access code supplied upon request from Software House. For details, see
Obtaining an Activation Key for C•CURE 800 Database Migration on Page 27.

Installation Requirements
■ When migrating records from the C•CURE 800 database, install the C•CURE 9000 Database Migration Utility on the
C•CURE 800 server, or on a C•CURE 800 client. The C•CURE 800 server or client must be at version 10.2 or 10.3.
■ Before installing the C•CURE 9000 Database Migration Utility, ensure that the computer on which you want to install the
utility meets the following requirements and guidelines:
• Microsoft Windows 7, 8.1, or 10, Windows Server 2012 R2, Server 2016.
• 100 - 200 MB of available RAM
• Enough free disk space to store the records you are migrating
■ For installing the C•CURE 9000 Database Migration Utility, you must log in as a Windows Administrator.

Installing the C•CURE 9000 Database Migration Utility

The C•CURE 9000 Database Migration Utility is packaged on installation media that includes an automated installer. When
you insert the installation media, the installer displays a wizard to lead you through the necessary initial configurations.

Once the installation is complete, the Windows Start menu has two new menu items:
■ One for the migration utility.
■ One for the related documentation.

To Install the C•CURE 9000 Database Migration Utility

1. Insert the C•CURE 9000 Database Migration Utility installation media into the drive of the computer on which you want to
install it.
2. Double-click the .exe file to begin installation. The Database Migration Utility screen appears.
3. The SWHMigrationTool appears. If your system requires items installed on your computer, this dialog box displays the
components to install. Click Install to proceed with installation.
• If there is a problem with installation, a dialog box appears asking if you want to continue with installation.
4. The Welcome screen appears. Click Next to begin installation of the DMU.
5. A License Information dialog box opens. Select the I accept the terms in the license agreement radio button and
then click Next. You can also click Print to print a hard copy of the license for your records.
6. The Customer Information dialog box opens. Type the appropriate information in the User Name and Organization
entry fields. Select one of the Install this application for options and click Next.
7. The Destination Folder dialog box opens.
• To install the C•CURE 9000 Migration Utility in the default folder in the Destination Path dialog box, click Next.

C•CURE Database Migration Guide 12

 - or -
• To install the C•CURE 9000 Migration Utility in a different location, click Change. The Change Current Destination
Folder dialog box opens for you to enter the location. Click Next.
8. The Ready to Install the Program dialog box appears. Click Install to begin the installation of the C•CURE 9000
Migration Utility. When the InstallShield setup finishes, it begins installing the C•CURE 9000 Migration Utility and the
Installing C•CURE 9000 Migration Utility dialog box appears.
Once the installation process is done, the InstallShield Wizard Completed dialog box appears.
9. Click Finish to begin using the C•CURE 9000 Migration Utility.

C•CURE Database Migration Guide 13

Configuring the ODBC Connection for C•CURE 800 Environments
For C•CURE 800 environments, the C•CURE 9000 Database Migration Tool installation requires configuration of the ODBC
connection. The procedure for opening the ODBC Data Source Administrator differs depending on whether your C•CURE 800
system is on a 32-Bit or a 64-Bit Operating System, as detailed in the following steps.

To Configure an ODBC Connection for C•CURE 800

1. On a 32-Bit Operating System, click Start>Control Panel> Administrative Tools>Data Sources (ODBC).
- or -
On a 64-Bit Operating System, click C:\Windows\SysWOW64\odbcad32.exe executable program and then click Open.
The ODBC Data Source Administrator dialog box opens, as shown in Figure 1 on Page 14.
Figure 1: ODBC Data Source Administrator – User DSN Tab (32-Bit OS)

User DSN Tab (32-Bit OS) User DSN Tab (64-Bit OS)

2. Click the System DSN tab to open, shown in Figure 2 on Page 15.

C•CURE Database Migration Guide 14

 Figure 2: ODBC Data Source Administrator – System DSN Tab

3. Click Add to create the Data Source.

The Create New Data Source dialog box opens. (See Figure 3 on Page 15.)
Figure 3: Create New Data Source

4. Select Progress OpenEdge 10.2A Driver.

5. Click Finish. The ODBC Progress OpenEdge Wire Protocol Driver Setup dialog box appears, as shown in Figure 4 on
Page 16.

C•CURE Database Migration Guide 15

 Figure 4: ODBC Progress OpenEdge Wire Protocol Driver Setup - General Tab

6. Provide the following information to configure the appropriate driver, (see Figure 4 on Page 16):
• Data Source Name – must be the C•CURE option (must be upper case)
• Description – optional
• Host Name – can be localhost (must be one word, no space)
• Port Number– must be 2500
• Data Base Name – cf (must be lower case)
• User ID – any string (this ID will be replaced by the utility)
7. Click Apply and then OK to create the ODBC connection. (Ignore the Test Connect function since the utility uses a
proper User ID and Password by replacing the values in the ODBC dialog box.)
8. When the ODBC Data Source Administrator dialog box reappears, click OK again.

C•CURE Database Migration Guide 16

 2

Chapter 2 - C•CURE 9000 Database Migration

for C•CURE 800 Databases

This chapter describes the process for migrating records from Software House C•CURE 800 databases in a format suitable for
import into C•CURE 9000.

All records imported into C•CURE 9000 must be in XML format conforming to the C•CURE 9000 schema. Software House
provides the C•CURE 9000 Database Migration Utility, a separately licensed software tool, to export selected C•CURE 800
records as XML files in the C•CURE 9000 schema. The Data Import function provided by C•CURE 9000 then uses the
exported files as source for importing the objects into your C•CURE 9000 database.

Use the procedures in this chapter to prepare records for export from C•CURE 800 and to activate and operate the C•CURE
9000 Database Migration Utility.

In this chapter

Overview and General Requirements 18

Prerequisites for Migrating C•CURE 800 Databases 27
Migrating Records from C•CURE 800 Databases 30
Post-Export/Pre-Import Configuration Steps 35
Importing C•CURE 800 Records into the C•CURE 9000 System 38
Post-Import Steps for C•CURE 800 Records 41
CCURE.INI Entries/System Variables Imported to C•CURE 9000 43

C•CURE Database Migration Guide 17

Overview and General Requirements
Successfully migrating records from C•CURE 800 to C•CURE 9000 requires:
■ Advance preparation.
■ Understanding how to use the C•CURE 9000 Database Migration Utility to export files from C•CURE 800 databases as
XML files ready for import into C•CURE 9000.

Especially important is understanding which records the utility can convert for import, and the sequence for importing those
records into C•CURE 9000.

Once it is configured, the C•CURE 9000 Database Migration Utility automatically:

■ Performs the mapping that generates the output required to move records from the legacy databases into a C•CURE 9000
database.
■ Places the output files in a single directory.
■ Creates a CCURE800-Export.log file for review of the export.

Importing the records into C•CURE 9000 then requires using the
C•CURE 9000 Data Import function.

Software House Professional Services provides technical support and services for migrating legacy databases to C•CURE
9000, including support and activation information for the C•CURE 9000 Database Migration Utility.

When migrating a database from an Asian-language version of

NOTE C•CURE 800, the XML Export phase of the Data Migration must be run on the C•CURE 800 Asian-language
server, and not run remotely from an English-language system.

The Migration Process

To Move Data from C•CURE 800 to C•CURE 9000

1. Install the C•CURE 9000 Database Migration Utility and request a unique activation key for each database that you want
to migrate.
2. After meeting the prerequisites for the type of database being migrated:
a. Open the database migration utility and enter an activation key.
b. Run the C•CURE 9000 Database Migration Utility in verification mode repeatedly (as needed) to locate any fields with
bad characters and then fix the fields or delete the records.
c. Run the Migration Utility in normal mode to generate the XML files to use as an import source in C•CURE 9000.
3. To Complete the Migration
a. Perform any necessary post-export configuring.

If you need to configure certain system variables (those not associated with iSTAR Areas, iSTAR Intrusion
NOTE Zones, or Keypad Commands) or create blank card formats in C•CURE 9000, Software House recommends
completing those tasks before importing any files.
■ Stop the C•CURE 9000 driver (Server Component Framework).
■ Configure the system variables as needed in C•CURE 9000.
■ Create blank card formats, as needed.

b. Use the Data Import function in C•CURE 9000 to add the exported records to the C•CURE 9000 database.

C•CURE Database Migration Guide 18

 c. After the import has completed, restart the C•CURE 9000 driver.

Table 1 on Page 19 lists the general steps for migrating records from C•CURE 800 to C•CURE 9000. Perform the migration in
the sequence given.
Table 1: The Migration Process

Activity (Perform in sequence) Perform this in. . .

Satisfy all prerequisites for the C•CURE 9000 Database Migration Utility. (See C•CURE 800 Server or Client
Prerequisites for Migrating C•CURE 800 Databases on Page 27.)

Request an Activation Key from your Software House integrator. (See Obtaining an
Activation Key for C•CURE 800 Database Migration on Page 27.)

Install the C•CURE 9000 Database Migration Utility. (See Installation on Page 12.) C•CURE 800 Server or Client

Run the C•CURE 9000 Database Migration Utility, adjusting operating settings as
required. Check the CCURE800-Export.log file for errors. (See Migrating Records from
C•CURE 800 Databases on Page 30.)

As required, perform post-export/pre-import steps: C•CURE 9000 Client In the

• Configure certain System Variables. Administration Station

• Create blank Card Formats in C•CURE 9000 to correspond to card formats in the
source database.
• Prepare CHUID formats.
(See Post-Export/Pre-Import Configuration Steps on Page 35.)

Back up the C•CURE 9000 System database.

Import each XML file generated by the C•CURE 9000 Database Migration Utility
automatically, using the Import Watcher listening to external events.
• Review the import log and rejected records files.
• Resolve errors, if any, in each import before proceeding to the next.
(See Importing C•CURE 800 Records into the C•CURE 9000 System on Page 38.)

As required, perform post-import steps: C•CURE 9000 Client In the

• Reset apC and iSTAR Controllers. Administration Station

• Re-configure apC Dialup Panels, iSTAR Dialup Clusters, and iSTAR Dialup Panels
• Re-configure Card Formats.
• Re-configure (redesign) Badge Layouts or use C•CURE ID to import them.
• Edit certain migrated Events.
• Rename any Personnel Customer Field whose label was changed in C•CURE 800.
• Reconfigure Tour Stop Inputs.
• Assign Guards to Guard Tours.
(See Post-Import Steps for C•CURE 800 Records on Page 41.)

Records Migrated from C•CURE 800 Databases

The C•CURE 9000 Database Migration Utility can automatically convert and export certain C•CURE 800 database record
types in a format suitable for direct import into a clean C•CURE 9000 database. Other C•CURE 800 database records require
various degrees of manual intervention to move to C•CURE 9000.

C•CURE Database Migration Guide 19

Records Exported Automatically from C•CURE 800
Table 2 on Page 20 lists the C•CURE 800 database record types that the C•CURE 9000 Database Migration Utility converts
and exports automatically.
Table 2: Records Exported and Converted from C•CURE 800

C•CURE 800 C•CURE 9000

Notes
Terminology Terminology

Timespecs Schedules

iSTAR Clusters (and iSTAR Clusters

all associated modules
and boards)

iSTAR Cluster Dialup iSTAR Cluster Dialup iSTAR dialup clusters configurations are migrated to C•CURE 9000.
(DialIn, DialOut,
HostModem,
HostPhone, Remote
Phone objects)

iSTAR Controllers iSTAR Controllers

iSTAR Comm Port iSTAR Comm Port iSTAR Comm Ports are migrated to C•CURE 9000 to support iSTAR Dialup configurations.

apC Comm Ports and apC Comm Ports and apC/8X panels mistakenly labeled in C•CURE 800 as apCs are migrated to C•CURE 9000 as
apC Panels apC Controllers apCs.
In C•CURE 9000 you cannot change their type to apC/8X, and thus cannot perform firmware
downloads to them. See Special Considerations When Migrating Records from C•CURE 800 on
Page 30.
apC dialup panels are migrated to C•CURE 9000 like any other apC. You must then re-configure
them since C•CURE 9000 does not support dialup apCs.

Inputs apC Inputs

iSTAR Inputs

Outputs Outputs

Readers apC Readers After Hours Enabling Readers are supported in C•CURE 9000.
iSTAR Readers
After Hours Readers

Doors apC Doors If a Door/Elevator in C•CURE 800 is not associated with a controller, it is not migrated. Make sure
iSTAR Doors Doors/Elevators are assigned to a controller before running the Migration Utility.

Groups Door Groups apC Area Group members are not migrated; Area Groups totally made up of apC Areas are not
Area Groups migrated.
Door Groups
Elevator Groups Carpool Groups are migrated with Personnel Groups.
Event Groups
Floor Groups
Input Groups After Hours Enabling Readers are supported in C•CURE 9000.
Output Groups
The After Hours Reader feature defines a schedule, an enabling reader and an iSTAR reader
Personnel Groups
group.
After Hours
Reader Groups
Reader Groups

C•CURE Database Migration Guide 20

 Records Exported and Converted from C•CURE 800 (continued)

C•CURE 800 C•CURE 9000

Notes
Terminology Terminology

Floors Floors

Elevators Elevators If a Door/Elevator in C•CURE 800 is not associated with a controller, it is not migrated. Make sure
Doors/Elevators are assigned to a controller before running the Migration Utility.

Areas iSTAR Areas Carpool, Pass-through Area, Dynamic Area Manager, and Conditional Access configurations are
migrated.

Guard Tours Guard Tours All C•CURE 800 Guard Tour Stops Times, and Events are migrated. Stops associated with
Readers are replaced with a C•CURE 9000 Door definition—either as a Door (IN) or Door (OUT)
depending on whether the C•CURE 800 Reader was inbound or outbound. C•CURE 800 Readers
associated with Elevators are replaced by C•CURE 9000 Elevator device types.
Inputs associated with Tour Stops migrate as enabled, but not armed. You must arm these Inputs
for the Guard Tour to run successfully. See Reconfiguring Tour Stop Inputs on Page 42.
C•CURE 800 Guard Tours migrate without assigned Guards. On C•CURE 9000, Guard Tours
cannot run if they do not have an assigned Guard. You must assign Guards to the migrated Guard
Tours. See Assigning Guards to Guard Tours on Page 42.

Intrusion Zones iSTAR Intrusion

Zones

RM LCD Messages RM LCD Messages

Preset Messages Predefined Messages

Clearances (including Clearances

clearance items)

Personnel including: Personnel including:

Cards Credentials

Person/Clearance Person/Clearance
pairing pairing

Personnel Types Personnel For details about the export and conversion of C•CURE 800 Personnel Types, see Migrating
Types/Escort C•CURE 800 Personnel Types on Page 22.
Options

Personnel Event Personnel Action

Actions Items (in
Personnel
Personnel
Triggers tab)

Clearance Filters Clearance Filters

Custom Custom
Clearances Clearances

Images (optional) Images

Personnel including: Personnel including:

(continued) (continued)

Signatures Signatures
(optional)

C•CURE Database Migration Guide 21

 Records Exported and Converted from C•CURE 800 (continued)

C•CURE 800 C•CURE 9000

Notes
Terminology Terminology

Badge Layout Badge Layout

Names (optional) Names

User Defined User Defined

Fields Fields

Actions Action Items (either in Event Groups are not migrated for C•CURE 800 Arm Event and Activate Event Actions activated
Event Action tab or by C•CURE 800 Time Specs. If the migration encounters such a Group, it writes a warning to a log
rows on Hardware file, CCURE800-Export.log.
Triggers tabs) If more than one C•CURE 800 Time Spec activates the same Event, the Action for the first Time
Spec is migrated while the other Actions (caused by the other Time Specs) are discarded. For each
Action not migrated, a warning is written to the CCURE800-Export.log file.
C•CURE 800 Input Actions that activate events based on C•CURE 800 Time Specs migrate to
C•CURE 9000 using the Controller’s assigned Time Zone.

Events Events

Keypad Commands Keypad Commands

Elevator Outputs Buttons

IO Linkages (Door Event or Trigger

Forced, etc.) (Action Item)

Partitions Partitions

User Defined Field User Defined Field

Definitions Definitions

CCURE.INI (Diag System Variables Only certain CCURE.INI entries related to iSTAR Areas, iSTAR Intrusion Zones, and the Monitor
System) Entries Station are migrated. See CCURE.INI Entries/System Variables Imported to C•CURE 9000 on
Page 43.

System Variables System Variables Only one Monitoring, one iSTAR Controller, and the three Keypad Command System Variables are
migrated. See CCURE.INI Entries/System Variables Imported to C•CURE 9000 on Page 43.

Conditional Access Conditional Access The iSTAR Controller setting for Include Personnel without Clearance in Personnel
Downloads is migrated in the Cluster XML file to support Conditional Access.
If Conditional Access DownloadCardWOClearance is set to True for a Door on an
iSTAR Controller, three additional Access properties are migrated:
<ConditionalAccessDelay> (if set to 0 on C•CURE 800, it is set to the default value of 10 in C•CURE
9000)
<ConditionalAccessScheduleObjectKey>
<ConditionalAccessEventObjectKey>

Migrating C•CURE 800 Personnel Types

The C•CURE 800 database record types, Personnel Types, are automatically exported and converted into two different
C•CURE 9000 Personnel database record types, Personnel Types and Escort Options, as illustrated in Table 3 on Page 22.
Table 3: Relationship between C•CURE 800 Personnel Types and C•CURE 9000 Database Record Types

C•CURE 800 Personnel Type C•CURE 9000 Personnel Type C•CURE 9000 Escort Option

None None None

C•CURE Database Migration Guide 22

 Relationship between C•CURE 800 Personnel Types and C•CURE 9000 Database Record Types (continued)

C•CURE 800 Personnel Type C•CURE 9000 Personnel Type C•CURE 9000 Escort Option

Visitor None Unescorted Visitor

Escorted Visitor None Escorted Visitor

Escort None Escort

Employee Employee None

Contractor Contractor None

Records Not Exported Automatically from C•CURE 800

The C•CURE 9000 Database Migration Utility does not convert and export records related to features C•CURE 9000 does not
support. In addition, the utility does not automatically convert and export card formats. However, the utility does give you the
option to create references in the export files that allow you to re-create the card formats in C•CURE 9000—but only if you
created corresponding blank card formats in C•CURE 9000 prior to importing the records into the C•CURE 9000 database.
See Preparing Card Formats on Page 36.

Personnel records with credential expiration dates prior to January 1, 1990 0000 (12:00 AM) cannot be migrated
NOTE to C•CURE 9000. These expiration dates are changed to 1/1/1990 at 0000. In addition, expiration dates after
1/1/2038 0000 are set to 1/1/2038 0000.

Certain record types, although related to features C•CURE 9000 supports, cannot be converted and exported using the
C•CURE 9000 Database Migration Utility, including those found in Table 4 on Page 23.
Table 4: Records Not Exported and Converted from C•CURE 800

C•CURE 800 Terminology C•CURE 9000 Terminology

Historical Logs Historical Logs

Users and Privileges Operators and Privileges

Video (including cameras, protocols, switchers, CCTV) Video (including cameras, protocols, switchers, CCTV)

ASCII/Bidirectional ASCII/Bidirectional

Personnel Views Personnel Views

Reports Reports

Holidays Holidays

Maps Maps

iSTAR Controllers Not in a Cluster

iSTAR controllers not assigned to clusters in C•CURE 800 are not migrated. While objects referencing them—events, doors,
clearances, groups, floors, actions, elevators, etc.— migrate, they are not imported into C•CURE 9000. Consequently,
Software House recommends that you create a cluster in C•CURE 800 and put the controller(s) in it—even if there is only one.
This is especially important if there are many events, doors, clearances, groups, floors, actions, elevators, etc. associated
with the controller(s).

C•CURE Database Migration Guide 23

Unassigned Doors and Elevators

Doors and Elevators not assigned to iSTAR controllers/apC panels in C•CURE 800 are not migrated.

Actions

Certain Actions, not supported in C•CURE 9000, are not migrated. When the migration process encounters any of these in
the C•CURE 800 database, it writes them to a log file, CCURE800-Export.log. You can check this file to see which Actions
these were. The Actions in the following list are migrated:

Event Lock door Show intrusion zone status

Unlock door Show intrusion zone offnormal points
Momentarily unlock door Arm local intrusion zone
Secure door Disarm local intrusion zone
Activate event Toggle local intrusion zone
Deactivate event Force arm local intrusion zone
Arm event Show local intrusion zone status
Disarm event Show local intrusion zone off normal points
Latch event Enable keypad commands
Unlatch event Disable keypad commands
Toggle event Set clearance filter 1
Arm input Set clearance filter 2
Disarm input Set clearance filter 3
Activate output Set clearance filter 4
Deactivate output Control access Set clearance filter 5
Uncontrol access Set clearance filter 6
Disable PIN Enable counting (access restrictions)
iStar Database Backup Enable counting for events
Disarm intrusion zone Enable counting only
Arm intrusion zone Lock local door
Force arm intrusion zone Unlock local door
Toggle intrusion zone mode Secure local door
Allow conditional access cycle

Inputs Activation triggers event

Activation activates output
Deactivation
Supervision error

apC panel Comm failure

Panel full
Panel nearly full (w/%)

iSTAR cluster Primary Comm failure

iSTAR Comm failure

controller

Elevator All Admits

All Rejects
Card duress

C•CURE Database Migration Guide 24

 Area Entry Passback violation
Exit Passback violation
Area One Occupant
Failure to enter additional card
Maximum occupancy
Access over Maximum occupancy
Minimum occupancy
Access under Minimum occupancy
Personnel Group Maximum occupancy
Personnel Group Minimum occupancy
Area lockout violation

Door Door forced

Held open
Duress
All Admits
All Rejects
Noticed admit
Noticed reject

apC Comm Comm failure

Port

Importing Objects from C•CURE 800 and Partitioning

■ Most objects in C•CURE 800 cannot be partitioned. When imported into C•CURE 9000, they are imported into the
‘Default Partition’.
■ The following C•CURE 800 Objects migrate to C•CURE 9000 with their partitions:
• Personnel
• Clearances
• Door Groups
• Time Specs (schedules)
■ C•CURE 800 has a partition called ‘$Standard Partition’. Objects from this partition are imported into C•CURE 9000 to the
current operator’s ‘New Object Partition’.
■ All hardware migrated into C•CURE 9000 goes into the ‘Default Partition,’ even if the doors were configured to be in
another partition.
• In C•CURE 800, clusters and controllers do not have partitions, but doors and elevators may be in partitions.
• In C•CURE 9000, clusters, controllers, doors, and elevators will all be in the default partition of the hardware folder. So
when these objects types are imported, their partitions are set to the same Partition as that of the parent object.
• iSTAR Cluster Areas and Keypad Commands imported into
C•CURE 9000 have their partitions set to the same Partition as that of their iSTAR Cluster, while iSTAR Intrusion
Zones have their Partition set to the same Partition as that of their iSTAR Controller.

Partitioning Restrictions in C•CURE 800 Not in C•CURE 9000

The following partitioning restrictions in C•CURE 800 are not restrictions in C•CURE 9000:
■ Groups in a partition other than the ‘$Standard Partition’ allow group members only from the same partition as the group.
However, a group in the “$Standard Partition” can include group members from another partition.
Example:
If a Door group is in partition ‘P1,’ users can add doors to that group only if those doors are also in partition ‘P1.’
However, if a Door group is in the ‘$Standard Partition,’ users can add any door from any partition to that group.

C•CURE Database Migration Guide 25

■ Clearances that are in a partition other than the ‘$Standard Partition’ allow doors and time specs only from the same
partition as the group.

C•CURE Database Migration Guide 26

Prerequisites for Migrating C•CURE 800 Databases
The C•CURE 9000 Database Migration Utility is designed to create output that can be imported without additional modification
or mapping. You cannot use the utility to generate output that updates existing records.

In all cases, the C•CURE 9000 database must be free of pre-existing records that match the records you are
NOTE importing.
If a matching record exists, it will generate an import error, which you can examine in the Export.log file.

Before you run the C•CURE 9000 Database Migration Utility you must ensure that the legacy database containing the records
you want to migrate is properly prepared. The prerequisites you must satisfy depend on the type of database you are migrating.

Before using the C•CURE 9000 Database Migration Utility to prepare records in a C•CURE 800 database for migration, satisfy
the following requirements:
■ Ensure that your C•CURE 800 is version 10.2 or 10.3.
■ Ensure that C•CURE 800 and the driver are running.
■ Get an Activation Key. See, Obtaining an Activation Key for C•CURE 800 Database Migration on Page 27.
■ Handle any special considerations for migrating apC/8X panels, Card Formats, and PINs. See Special Considerations
When Migrating Records from C•CURE 800 on Page 30.

Obtaining an Activation Key for C•CURE 800 Database Migration

To operate the C•CURE 9000 Database Migration Utility, you must enter an Activation Key on the C•CURE 9000 Database
Migration Utility dialog box. (This activation key serves as a license to use the migration utility with a specific database and is
not related to the C•CURE 9000 software license.) See Default C•CURE 9000 Database Migration Utility Dialog Box on Page
28for the location of the Enter your activation key before continuing field.

To obtain an activation key, submit a request to your authorized Software House integrator and provide the following:
■ Name of the site where C•CURE 9000 is installed.
■ Physical address of the site, including street, city, state, and postal code.
■ Name of the organization performing the integration. (In most instances, Software House Professional Services or a
Software House dealer performs the migration.)
■ Name of the individual performing and managing the migration.
■ For C•CURE 800 databases, provide the system serial number, listed in the About Box, which you can access from the
Help menu.

After receiving your request, Software House Professional Services will issue an activation key for the specific database that
you identify.

The activation key is valid only for the specific database you identified in your request. You cannot use the
NOTE activation key to export records from another database, even one installed at the same site.

Accessing the C•CURE 9000 Database Migration Utility

Once you have installed the C•CURE 9000 Database Migration Utility, you can open it from the Windows Start menu. For
detailed information on installing the utility, see Installation on Page 12.

C•CURE Database Migration Guide 27

To Access the C•CURE 9000 Database Migration Utility
1. From the Windows Start menu, select All Programs (if using the classic Start menu, Programs)>Software
House>C•CURE 9000> Database Migration Utility.
The default C•CURE 9000 Database Migration Utility dialog box opens, as shown in Figure 5 on Page 28.
Figure 5: Default C•CURE 9000 Database Migration Utility Dialog Box

2. Type a valid Activation Key in the entry field at the top of the dialog box. The Activation Key is a unique identifier for each
database export. See Obtaining an Activation Key for C•CURE 800 Database Migration on Page 27 for more information.
3. Continue to the next section, Verifying Personnel Records on Page 28.

Verifying Personnel Records

Certain unprintable characters in the Personnel User-defined fields can cause the Database Migration to fail. This problem can
be circumvented by running the Database Migration Utility in verification mode before you actually run the migration to catch
and then correct or delete any of these problem fields.

To Verify C•CURE 800 Personnel Records

1. On the C•CURE 9000 Database Migration Utility dialog box, as shown in Figure 5 on Page 28, do the following in the
C•CURE 800 Migration Details box:
a. In the Path to C•CURE 800 CCURE.ini file field, select this
C•CURE 800 file by clicking .
b. Select the Verify Personnel Only check box. The Starting User ID field displays and the screen appears as shown in
on Page 28.

C•CURE Database Migration Guide 28

 Figure 6: C•CURE 9000 Database Migration Tool– for C•CURE 800 Verification

2. Click Start Database Export.

The Utility runs through the database in verification mode, displaying the progress of the records being validated in the
Status of Export box on the bottom of the screen—”Validating Personnel id 2344”, “Validating Personnel id 2345”, etc.
When the process finds a bad record, it stops at that record ID and displays an error message.
3. Fix the failed record or discard it.
4. Restart the verification process by entering the number of the last failed record in the Starting User ID field and clicking
Start Database Export (to ensure that record ID was fixed).

Optionally, you may specify another User ID from which to start—in order to skip that last User record. (The
NOTE User ID you enter does not need to exist; the system will skip to the next ID until it finds one that does exist.)

5. Repeat these steps until the entire database is clean. The Utility displays the following message:

6. Continue to the next section, Migrating Records from C•CURE 800 Databases on Page 30, to begin exporting a C•CURE
800 database.

When you are fixing a record on the C•CURE 800, you should remember that not all User-defined fields are
NOTE visible in all Views. You should create a View that has all the User-defined fields visible on the Administration
window.

C•CURE Database Migration Guide 29

Migrating Records from C•CURE 800 Databases
Before starting the migration, make sure you have satisfied all the prerequisites and fully understand the special considerations
related to migrating C•CURE 800 records into C•CURE 9000. See Figure 5 on Page 28 for an example of the Migration Utility
dialog box for a C•CURE 800 database migration source and Performing the Migration from C•CURE 800 on Page 32 for
information about the dialog box.

If you are migrating a database from an Asian-language version of C•CURE 800, the XML Export phase of the
NOTE Data Migration must be run on the C•CURE 800 Asian-language server, and not run remotely from an English-
language system.

Special Considerations When Migrating Records from C•CURE 800

When preparing a C•CURE 800 database for migration, you should first review the details in this section to reduce the chance
for errors after the migration.

Advanced Door Monitoring

For C•CURE 800 systems migrating to C•CURE 9000:
■ If the C•CURE 800 CCURE.INI Driver section entry, SuppressNonAlarmDoorInputReport is set to zero (0) ‘False’, in
C•CURE 9000 the ‘Send non-alarms input status to the host’ option in the Settings box on the iSTAR Door Editor
General tab is selected (set to ‘True’) for all existing iSTAR Doors.
■ If that same C•CURE 800 CCURE.INI Driver section entry is set to one (1) ‘True’, in C•CURE 9000 the option in the
Settings box on the iSTAR Door Editor General tab is not selected (set to ‘False’) for all existing iSTAR Doors.

apC/8X Panels
If your C•CURE 800 system has apC/8X panels mistakenly labeled with an apC Type of apC, they will be migrated into
C•CURE 9000 as apCs. In C•CURE 9000, you will then be unable to change their type back to apC/8X. Consequently, you
will not be able to perform firmware downloads from the context menu to these apC/8X controllers.

To avoid this situation, before performing the database migration, make sure that all apC/8X panels in your system have their
apC Type field in the General box on the apC dialog box set to apC/8X.

Card Formats
The C•CURE 9000 Database Migration Utility does not convert and export the card format associations with card readers as
they are defined in
C•CURE 800. You can, however, re-create the card format associations as follows:
1. Create corresponding card formats in C•CURE 9000 as follows:
a. Name each format with the same unique name used in C•CURE 800, as found in the CardFormat.txt file.
b. Select Card Only from the list for the CHUID Format.
2. When the card readers are then imported into C•CURE 9000, the imported readers will adopt the new card formats.

If you do not create these card formats in C•CURE 9000 before importing controllers, all records referencing
the missing card formats will fail.

C•CURE Database Migration Guide 30

Event Dual (Two) Phase Acknowledgment
The C•CURE 9000 Database Migration Utility migrates C•CURE 800 Two Phase Acknowledgment Event configurations to
C•CURE 9000 Dual Phase Acknowledgment Event configurations.

The Utility determines whether or not the C•CURE 800 system has Two Phase Acknowledgment configured, based on the
Driver CCURE.INI settings. If Two Phase Acknowledgment is configured, the following rules apply during migration:
■ Any Event configured in C•CURE 800 —
• To require
— Acknowledgment will have both the ‘This event requires acknowledgment’ and ‘This Event requires clearing’
options set to true in C•CURE 9000.
— A log message to acknowledge or to clear will be configured in the same way in C•CURE 9000.
• To ‘allow clear of event regardless of active causes’ will have both ‘Allow acknowledgment while causes are active’
and ‘Allow event to be cleared while causes are active’ set to true in C•CURE 9000.
• With an ‘overdue clear event’ will have the same Event configured for overdue clear in C•CURE 9000.
■ All migrated Events will have ‘Acknowledgment clears event regardless of active causes’ set to false.
■ Preset log messages will be migrated as C•CURE 9000 Predefined Log Messages. They will have ‘Use for Acknowledge’
and ‘Use for Clear’ properties both set to true in Predefined Messages.

PIN Migration
To migrate Personnel Identification Numbers (PINs), choose Allow PIN display in the C•CURE 800 application before
beginning the migration process. Select Options>System Variables. Then select the Allow PIN display check box in the
System Variables Personnel tab as shown in Figure 7 on Page 31. PIN Only access cards can be migrated.
Figure 7: C•CURE 800 System Variables – Personnel Tab

C•CURE Database Migration Guide 31

Performing the Migration from C•CURE 800

To Export C•CURE 800 Database Records

1. Launch the C•CURE 9000 Database Migration Utility following the information in Accessing the C•CURE 9000 Database
Migration Utility on Page 27.
The default C•CURE 9000 Database Migration Utility dialog box opens as shown in Figure 5 on Page 28.
2. Enter an activation key for the C•CURE 800 database you want to migrate.
You must have a unique activation key for each C•CURE 800 database you migrate. For details, see Obtaining an
Activation Key for C•CURE 800 Database Migration on Page 27.
3. In the Items to Export box, select either or both of the following:
All configuration objects To export all records that can be converted and imported
directly into C•CURE 9000, other than personnel records
Personnel To export and convert Personnel records

The PersonnelGroup.xml file updates some of the All configuration objects items. Consequently, when you
are migrating Configuration objects, always select both options in the Items to Export box.

For example, if you do not migrate Personnel, Personnel Groups for Area Occupancy are not migrated.

If you are only migrating Personnel objects, you can safely select the Personnel option only.

4. In the References to Manually Created Objects box, select either or both of the following:
Include reader reference to To maintain in C•CURE 9000 the card format associations
card formats that exist in the source database.
Include personnel To maintain in C•CURE 9000 the badge layout
reference to badge layouts associations that exist in the source database.

5. In the C•CURE 800 Migration Details box, do the following:

a. In the Path to C•CURE 800 CCURE.ini file field, select this
C•CURE 800 file by clicking .
b. In the Path to C•CURE 800 image directory field, select the folder used to store images for C•CURE 800 by clicking
.
c. In the Path to C•CURE 800 signature directory field, select the folder used to store signatures for C•CURE 800 by
clicking .
d. If necessary, choose an Extended Card format using the Select the C•CURE 9000 CHUID Format to use with
Extended Cards drop-down list shown below.

If you select a CHUID format, make sure to set it up in C•CURE 9000 exactly as it was in C•CURE 800.
6. In the Destination for exported files field, select the folder where you want to save the export files created by the utility
by clicking .
The CCURE800-Export.log file will be created automatically in the same folder. By default, the export files are saved in the
folder where you installed the migration utility.
To simplify the import into C•CURE 9000, the folder should be created on the C•CURE 9000 server.

C•CURE Database Migration Guide 32

7. To convert and export the C•CURE 800 records, click Start Database Export.
When the export has finished, the warning message shown in Figure 8 on Page 33 appears if the C•CURE 800 system you
are migrating has Global Antipassback (cross-cluster) Areas.
Figure 8: Global Antipassback Area Warning Message

8. Click OK.
A message such as that shown in Figure 9 on Page 33 then displays indicating whether or not there were any errors.
Figure 9: Export Complete Message

The migration utility creates the following files:

CCURE800-01-SystemVariable.xml
CCURE800-02-Partition.xml
CCURE800-03-Schedule.xml
CCURE800-04-RMLCDMessageSet.xml
CCURE800-05-Cluster.xml
CCURE800-06-ApcController.xml
CCURE800-07-PredefinedMessages.xml
CCURE800-08-Event.xml
CCURE800-09-IstarDoor.xml
CCURE800-10-ApcDoor.xml
CCURE800-11-Floor.xml
CCURE800-12-Elevator.xml
CCURE800-13-Area.xml
CCURE800-14-IntrusionZone.xml
CCURE800-15-Group.xml
CCURE800-16-GuardTour.xml
CCURE800-17-Action.xml
CCURE800-18-KeypadCommand.xml
CCURE800-19-UpdateGroup.xml
CCURE800-20-BadgeLayout.xml
CCURE800-21-Clearance.xml
CCURE800-22-UDF.xml

C•CURE Database Migration Guide 33

 CCURE800-23-Personnel_nnn.xml (where nnn is the number of the file, such as
Personnel_001.xml, Personnel_002.xml, etc. There can be many such files.)
NOTE: The migrated Personnel file is broken into smaller files to facilitate import into
C•CURE 9000.
CCURE800-24-PersonnelGroup.xml
CCURE800-25-AreaPersonnelGroup.xml
CardFormat.txt
CCURE800-Export.log

9. Review errors in the CCURE800-Export.log file (if any exist) and if necessary, make corrections and then re-run the utility.

When running the migration utility multiple times, both the previous log files and XML files are deleted by the
NOTE utility and replaced with the new files.

10. To exit the C•CURE 9000 Database Migration Utility, click Close.

To continue the migration process, you must now import the objects contained in the XML output into C•CURE 9000. For
information and import procedures, see Importing C•CURE 800 Records into the C•CURE 9000 System on Page 38.

C•CURE Database Migration Guide 34

Post-Export/Pre-Import Configuration Steps
Once the export of database records from C•CURE 800 has completed, you should do the following in C•CURE 9000 before
importing the data from the .xml files into C•CURE 9000:
■ Configure certain apC Driver and Personnel System Variables in C•CURE 9000, if necessary. (Certain CCURE.INI
entries related to Areas and Intrusion Zones are migrated from C•CURE 800 to C•CURE 9000, as are the Keypad
Command System Variables. For information, see CCURE.INI Entries/System Variables Imported to C•CURE 9000 on
Page 43.)
■ Configure the System Variables for iSTAR Dialup, if necessary. Needs updating for 800-9000 iSTAR Dialup sys
varibles/ini entries/TBD
■ Set up Card Formats.
■ Prepare CHUID Formats for Extended Card Formats.

Configuring System Variables in C•CURE 9000

You may need to configure some of the apC Driver and Personnel System Variables in C•CURE 9000 so their value is either
the same as (or optionally for a numeric value, greater than) the value set in the C•CURE 800 being migrated. The relevant
C•CURE 800 values are set in either the System Variables or Diag System (CCURE.INI). See Table 5 on Page 35 for the
equivalencies between the C•CURE 800 and C•CURE 9000 settings and To Configure C•CURE 9000 System Variables on
Page 36 for directions on making your changes.
Table 5: System Setting Equivalencies for C•CURE 800/C•CURE 9000 Data Migration

C•CURE 800 C•CURE 9000 Notes

System Variable or System Variable
Diag System Option

Driver/IsUsingActivationDates apC Driver/Is Using

Activation Dates

Driver/IsUsingDeactivationDates apC Driver/Is Using

Deactivation Dates

Driver/MaxNumberOfClearances apC Driver/Maximum

Number of apC
Clearances

Driver/MaxNumberOfClearancesPerCardDl apC Driver/Maximum

Clearances Per Person
on an apC

Driver/MaxIssueCode apC Driver/Maximum

Issue Code

System Variables Personnel Personnel/Maximum If using multiple cards or more than 10 clearances per person, increase the
option/Maximum number of Card(s) per Cards Per Person number so it equals (or optionally is greater than) the number of credentials
person set in C•CURE 800.

Driver/MaxNumberClearancesPerCard Personnel/Maximum Set to same value or (optionally) greater than set in C•CURE 800.
Clearances Per Person

4GLInterface/PinFormat Personnel/PIN Length Format for a 4-digit PIN:

• C•CURE 800: 9999
• C•CURE 9000: 4

C•CURE Database Migration Guide 35

 System Setting Equivalencies for C•CURE 800/C•CURE 9000 Data Migration (continued)

C•CURE 800 C•CURE 9000 Notes

System Variable or System Variable
Diag System Option

System Variables/RAS/ RAS Connection iSTAR Dialup Double-click on this system Variable to open a dialog box with four fields.
Information Domain Domain, Username, Password, Confirm Password can be set from this
User Name Username dialog box.
Password Password
Confirm Password Confirm Password
Domain Name

If you are migrating C•CURE 800 Personnel records whose expiration dates are before their activation dates,
NOTE you must first set the C•CURE 9000 Personnel system variable “Allow activation after expiration” to True. If
you do not set this value for the C•CURE 9000 variable, the import will fail.

To Configure C•CURE 9000 System Variables

1. In the C•CURE 9000 Administration Station, select Options & Tools>System Variables.
The System Variables Dynamic View opens on the General tab.
2. Click to expand the category of variable you want to configure.
3. Click in the Value field next to the variable name, and edit the value as needed.
4. Tab to the next line before closing the dialog box.
5. After using the C•CURE 9000 Data Import function to add the migrated records to the C•CURE 9000, restart the C•CURE
9000 driver.

Preparing Card Formats

The C•CURE 9000 Database Migration Utility does not convert and export card format associations with card readers as
defined in C•CURE 800. However, you can import the card format associations by first re-creating the card formats
themselves in C•CURE 9000.

Then, when the card readers are imported into C•CURE 9000 (through the import of the Cluster.xml and ApcController.xml
files), the imported readers will adopt the same card format they had in C•CURE 800.

To ensure format associations are migrated correctly, before importing readers associated with card formats do the following:
■ Create Card Formats in C•CURE 9000. The Card Formats can be created empty and configured after the import is
complete.
■ Name each format with the same unique name in C•CURE 9000 that was used in C•CURE 800. The file, CardFormat.txt,
contains the names of all the Card Formats used in C•CURE 800.

If you do not create blank Card Formats in C•CURE 9000 before importing the file with the iSTAR clusters and
controllers and the file with the apCs, all records referencing the missing card formats will fail.

C•CURE Database Migration Guide 36

Preparing CHUID Formats
If your C•CURE 800 database uses Extended Card formats and you have selected a C•CURE 9000 CHUID format as a
placeholder for the replacement of the Extended Cards, you will need to enable the chosen C•CURE 9000 CHUID Format and
configure it to match the C•CURE 800 Extended Card format. See the C•CURE 9000 Personnel Configuration Guide for more
information.

C•CURE Database Migration Guide 37

Importing C•CURE 800 Records into the C•CURE 9000 System
To import records exported by the C•CURE 9000 Database Migration Utility into C•CURE 9000, use the C•CURE 9000 Data
Import function, preferably with the Automation Mode of “Listening on data”.
■ When you use the automated “Listening on data” method, the system automatically imports the records in the correct
order.

You can also choose to import the records into C•CURE 9000 using the “Manual only” Automation Mode.
■ If you are importing the records into C•CURE 9000 manually, the order in which you import them is especially important.
Due to multiple parent-child dependencies between record types, attempting to import objects in any order other than the
specified sequence may cause the import to fail. For details, see The Import Sequence for C•CURE 800 Records on Page
39.

You access the C•CURE 9000 Data Import function in the Configuration pane of the C•CURE 9000 Administration Station.
Your ability to use this function to import records into the C•CURE 9000 database depends on your
C•CURE 9000 Operator Access Privileges. These Privileges are usually assigned by the system administrator.

C•CURE 9000 logs all imports and provides a separate file to accept rejected records. If records fail to import, you can identify
the cause and access each rejected record to make necessary modifications. You can repeat the import until you can
successfully add all records to C•CURE 9000.

For a limited overview of the Data Import process, see Chapter Appendix A, Importing Records into C•CURE 9000. For a
detailed description of how to import files into C•CURE 9000, see the C•CURE 9000 online help for the Data Import function
and the Data Import chapter in the C•CURE 9000 Software Configuration Guide.

Preparation for Importing C•CURE 800 Records into C•CURE 9000

Before starting the migration, do either of the following depending on the circumstances:
■ If you are importing migrated C•CURE 800 files for the first time, back up the C•CURE 9000 database.
■ If you are repeating an import of already migrated C•CURE 800 files, restore your C•CURE 9000 database.

Do not perform the migration while modifications to the C•CURE 800 system records are being processed.

The Import Process

In C•CURE 9000, successfully importing records requires a specific preparation, execution, and review. The process depends
on a set of parameters referred to as an Import Definition that you configure in advance. Depending on the information you are
importing, the data’s conformance to the C•CURE 9000 schema, and the configuration of your Import Definition, some records
may not import successfully. C•CURE 9000 provides tools that allow you to review and correct the import results.

To Import Records into C•CURE 9000

1. Configure an Import Definition that describes how to retrieve the new records you want to add.
a. With an Automation Mode of Listening on data (automated) – In this mode, the import source object is initialized by the
Import Watcher server component and starts listening for external events, such as the creation of new files in a
specified folder. When an external event is received, the import source initiates import of the received data.
-or-
With an Automation Mode of Manual only.
b. Save the Import Definition as a named object in C•CURE 9000.

C•CURE Database Migration Guide 38

2. Examine the results of the import to confirm what was added or updated, and to identify records that did not import as
expected.

For details about preparing C•CURE 800 records for import, see Migrating Records from C•CURE 800 Databases on Page 30.

The Import Sequence for C•CURE 800 Records

For each Import Definition used to import records converted and exported by the C•CURE 9000 Database Migration Utility,
ensure that the Default Import Mode is set to Add only; do not match records. You cannot use C•CURE 9000 Database
Migration Utility output to update existing records in C•CURE 9000.

Import the XML files created by the C•CURE 9000 Database Migration Utility in the following sequence—if you are importing
them manually. If you configured the Import Definition to import the migration files automatically, Listening on data, files are
automatically imported in the correct sequence.
1. CCURE800-01-SystemVariable.xml
2. CCURE800-02-Partition.xml
3. CCURE800-03-Schedule.xml
4. CCURE800-04-RMLCDMessageSet.xml
5. CCURE800-05-Cluster.xml
6. CCURE800-06-ApcController.xml
7. CCURE800-07-PredefinedMessages.xml
8. CCURE800-08-Event.xml
9. CCURE800-09-IstarDoor.xml
10. CCURE800-10-ApcDoor.xml
11. CCURE800-11-Floor.xml
12. CCURE800-12-Elevator.xml
13. CCURE800-13-Area.xml
14. CCURE800-14-IntrusionZone.xml
15. CCURE800-15-Group.xml
16. CCURE800-16-GuardTour.xml
17. CCURE800-17-Action.xml
18. CCURE800-18-KeypadCommand.xml
19. CCURE800-19-UpdateGroup.xml
20. CCURE800-20-BadgeLayout.xml
21. CCURE800-21-Clearance.xml
22. CCURE800-22-UDF.xml
23. CCURE800-23-Personnel_nnn.xml (where nnn is the number of the file, such as Personnel_001.xml, Personnel_002.xml,
etc. There can be many such files.)

The migrated Personnel file is broken into smaller files to facilitate import into C•CURE 9000.
NOTE

C•CURE Database Migration Guide 39

24. CCURE800-24-PersonnelGroup.xml
25. CCURE800-25-AreaPersonnelGroup.xml

Perform the import for each file until all its records are imported without error before proceeding to the next file, if you are
importing manually.

C•CURE Database Migration Guide 40

Post-Import Steps for C•CURE 800 Records
Once you have finished importing the database records, you must do the following in C•CURE 9000:
■ Reset apC and iSTAR Controllers
■ Re-configure previously Dialup iSTAR Clusters and previously Dialup apC Panels.
■ Re-configure Card Formats
■ Re-configure or import Badge Layouts
■ Rename Customer Fields whose labels were changed in C•CURE 800
■ Reconfigure Tour Stop Inputs
■ Assign Guards to Guard Tours

Resetting apC and iSTAR Controllers

After importing the migrated C•CURE 800 records, you must select the appropriate “Memory Clear” switch on each apC
panel/iSTAR controller, push the Reset button, and follow the instruction on the LCD readout (if any).

Re-configuring Card Formats

After importing the files migrated from C•CURE 800, you must re-configure the design of the Card Formats (the Card Data
fields) in C•CURE 9000.

Re-configuring/Importing Badge Layouts

The C•CURE 9000 Database Migration Utility exports empty badge layouts, but the migrated personnel records still include
the references to the person’s badges from C•CURE 800. You can either use the C•CURE ID import feature to import the
Badge Layouts from C•CURE 800 or configure the Badge Layouts anew in C•CURE 9000. For details, see the C•CURE ID
User’s Guide.

Renaming Customer Field Labels

The 42 Customer Fields—Text1 through Text25, Int1 through Int9, Logical1 through Logical4, and Date1 through Date4—
migrate from C•CURE 800 (where they are also known as user-named fields) with the original field labels stored in the
C•CURE 800 database. This is true even if one of these fields had its label changed in C•CURE 800—from Text2 to Site, for
example.

With the exception described in Importing of Unique Customer Text Fields on Page 42, the first 22 Customer Fields—Text1
through Text12, Int1 through Int6, Logical1 and Logical2, and Date1 and Date2—are imported to the C•CURE 9000 Customer
tab on the Personnel Editor; while the additional Customer user-named fields—Text13 through Text25, Int7 through Int9,
Logical3 and Logical4, and Date3 and Date4—are imported to the Customer Extended tab on the Personnel Editor.

Once all the migrated files have been imported into C•CURE 9000, you must change their Field labels back to the C•CURE
800 name, being careful to account for the reversal of the unique fields described in Importing of Unique Customer Text Fields
on Page 42.

A ‘unique’ field is a field required to have a ‘one-of-a-kind’ text value for each record in the database. Such fields
NOTE are useful for storing data such as salary, employee number, and other types of ID numbers.

C•CURE Database Migration Guide 41

Importing of Unique Customer Text Fields
Text7, a unique field in C•CURE 800, is imported to Text13 on the Personnel Editor Customer Extended tab, a unique field
in C•CURE 9000; while Text13, not a unique field in C•CURE 800, is imported to Text7 on the Customer tab, also not a
unique field in C•CURE 9000.

Text6, a unique field in C•CURE 800, is imported to Text12, a unique field in C•CURE 9000; while Text12, not a unique field in
C•CURE 800, is imported to Text6, also not a unique field in C•CURE 9000. (Both of these field exchanges are limited to the
Personnel Editor Customer Extended tab.)

User-Defined Field Names

NOTE
User-defined fields that are SQL keywords in C•CURE 800/8000 are renamed to FN_”xxx” by the Data
Migration process.

Field names that begin with a punctuation mark character, such as a “, [comma]” or “? [question mark]”, for
example, or a numeric character are also renamed to FN_x.

The “Date3” or “Date4” User-defined fields are also prefixed with FN_” date3” or FN_”date4”.

Reconfiguring Tour Stop Inputs

In C•CURE 800, Inputs used within a Guard Tour must be enabled, but not armed. The C•CURE 9000 Guard Tour
implementation requires Inputs used in a Guard Tour to be armed as well as enabled. After importing the migrated C•CURE
800 records, you must arm the Inputs associated with the Guard Tour Stops. For detailed information, see the C•CURE 9000
Guard Tours Guide and the C•CURE 9000 Hardware Configuration Guide.

Assigning Guards to Guard Tours

In C•CURE 800, Guards were assigned to a Guard Tour when the Tour was started. The C•CURE 9000 Guard Tour
implementation requires that you configure all Guards allowed to run a Tour as part of the Tour configuration. The Tour cannot
be run if no Guards are configured. Consequently, after importing the migrated records, you must configure Guards for each
migrated Tour. For detailed information, see the C•CURE 9000 Guard Tours Guide.

C•CURE Database Migration Guide 42

CCURE.INI Entries/System Variables Imported to C•CURE 9000
Some C•CURE 800 CCURE.INI entries migrate as do some System Variables: one for Monitoring and iSTAR Controller and
all those for Keypad Command. Table 6 on Page 43 shows equivalencies between C•CURE 800/C•CURE 9000 settings.
Table 6: System Setting Equivalencies for C•CURE 800/C•CURE 9000 Data Migration

C•CURE 800 C•CURE 9000

Diag System Option/System Variable System Variable/Editor Tab

Driver/DisableiSTAR_IZCabinetTamperUse iSTAR Driver/Disable the Intrusion Zone Cabinet Tamper

Driver/EscortCount iSTAR Driver/Maximum Visitor Count

Driver/EscortTimer Hardware Driver/Next Card Time

Driver/HostGAPBResponseTimeoutMS Host Global APB Response Timeout

Driver/iSTARAPBResponseTimeoutMS iSTAR APB response timeout

Driver/iSTARBadPinReaderLockoutTime iSTAR Driver/Length of Reader Lockout after bad PIN retries

reached

Driver/iSTARBadPinReaderRetryNumber iSTAR Driver/Number of bad PIN retries allowed before the

door/elevator is disabled

Driver/iSTARTimedAPBEnforcesTimeOnly iSTAR Driver/iSTAR Cluster Area Editor Antipassback Tab/Enforce

Timed Antipassback Only check box

Driver/iSTARValidExitClearsTimedAPB iSTAR Driver/iSTAR Cluster Area Editor Antipassback Tab/Valid Exit

Clears Timer check box

Driver/iSTARAPBMaxPingRoundTripMS* iSTAR Driver/iSTAR APB Maximum Ping Round Trip

Driver/iSTARAPBPingIntervalMS* iSTAR Driver/iSTAR APB Ping Interval

Driver/iSTARAPBResponseTimeoutMS* iSTAR Driver/iSTAR APB Response Timeout

MonitorStation/ManualActionDefaultTimeInterval Monitoring/Manual Action Default Time Interval

*Entry only displays when Diag System is in debug mode.

System Variables Monitoring/ option/Display person in admitted access iSTAR Driver/Display person in admitted access messages only when
messages only when PIN used after card swipe PIN used after card swipe

System Variables Controller option/iSTAR Global Antipassback Comm. failure iSTAR Driver/iSTAR Global Antipassback Communication Failure
mode Mode

System Variables Keypad Command options/ iSTAR Driver/

Maximum Length of Command Code Maximum Length of Command Code in Keypad Entry
Maximum Length of Prompt 1 Code Maximum Length of Prompt 1 Code in Keypad Entry
Maximum Length of Prompt 2 Code Maximum Length of Prompt 2 Code in Keypad Entry

C•CURE Database Migration Guide 43

 Appendix A - Importing Records into C•CURE 9000

This Appendix provides a limited overview of the Data Import process, describing how to create Import Definitions, run
imports, and examine the results of importing data into C•CURE 9000. It is a mini-synopsis of the Data Import chapter in the
C•CURE 9000 Software Configuration Guide, and is meant to provide a quick reference for completing the database migration
process to the C•CURE 9000 system. For complete detailed information about importing data into C•CURE 9000, see the
Data Import chapter and the appendix in the C•CURE 9000 Software Configuration Guide.

In this appendix

Importing Records into C•CURE 9000 Overview 45

Creating an Import Definition in C•CURE 9000 46
Running Imports 50
Viewing Import Results History 54

C•CURE Database Migration Guide 44

Importing Records into C•CURE 9000 Overview
The C•CURE 9000 Administration Station Data Import function lets you update the C•CURE 9000 database by importing
records contained in external databases. Depending on your C•CURE 9000 access privileges, you can use the Data Import
function to create an Import Definition:
■ To import migrated C•CURE 800 files with an Automation Mode of Listening on data. (The import source object is
initialized by the Import Watcher server component whenever new files are created in a specified folder.)

When you create an Import Definition, you specify data source input (usually files containing the data you want to import) and
establish rules used to add that information to the C•CURE 9000 database. C•CURE 9000 maintains a record of imports to the
system and provides a means to let you review the import history at any time.

For the complete information about the Data Import function and importing data into C•CURE 9000, see the C•CURE 9000
Software Configuration Guide.

C•CURE Database Migration Guide 45

Creating an Import Definition in C•CURE 9000
To run a manual import, you must create an appropriate Import Definition in the C•CURE 9000 Administration Station using the
Data Import Editor. You can also create an Import Definition from an Import Definition template.

To Create a New Import Definition

1. In the Administration Station, on the Navigation pane, select Configuration.
2. Click the Configuration drop-down list and select Data Import.
3. Click New.
A blank Data Import Editor opens with the General tab displayed, as shown in Figure 10 on Page 46.
Figure 10: Data Import Editor - General Tab

4. In the Name field, enter a unique name to identify the Import Definition when you run the import. You can enter up to 100
characters.
5. In the Description field, describe the import. You can enter up to 500 characters.
6. On the General tab:
a. Select the Source Type, which modifies the fields/options/buttons displayed in the Data Source Configuration box:

— Click to display a list of supported Import source types: CSV file, LDAP, ODBC, or XML file (the default).
— Click a Source type—to import:
- C•CURE 800 fields: XML file import source.
b. In the Automation Mode field, click the down-arrow to display the list of modes in which the Import can operate:
Manual only, Polling on schedule, or Listening on data. (The mode you select can also modify the Data Source
Configuration box.)
— Click an Automation Mode—to import:
- C•CURE 800 fields: Listening on data.

C•CURE Database Migration Guide 46

Data Source Configuration
The parameters requiring entry in the Data Source Configuration box change depending on whether you are configuring an
Import for an XML, CSV, LDAP, or ODBC file source type and whether you have selected manual mode or one of the two
automated modes.

Configuring a CSV Import Source

The CSV file source assumes the input file has data in the CSV format. The system reads the CSV file record by record,
converting it into a well- formatted XML document.
■ The first line in the CSV file is interpreted as a list of column names.
■ All other lines are interpreted as rows in the table with the specified column names.
■ The CSV file source reads every data row and puts the value from every column in the row into a tag with a proper column
name within the XML document being created.
■ If CSV has a column called ‘ClassType’, its content is used for each record converted, instead of Default Tag.
■ During the import, if the .CSV input file contains duplicate column names, the first column is used but the following occurs:
• Its name is automatically preceded by “‘filename’_x0023_csv.”
• The xml page shows it as an unrecognized field.
• The second duplicate column is ignored.

To Configure the Data Source for a CSV File Import Source

1. Create an Import Definition following Step 1 through Step 6b on Page 46 through Page 46:
The Data Source Configuration box then displays as shown in Figure 11 on Page 47.
Figure 11: Data Source Configuration Box – CSV Import in Manual Mode

2. In the Data Source Configuration box, enter information as follows:

a. In the File pattern field, for a Manual mode CSV import, specify a pattern to be used as the default pattern in the Open
File dialog boxes for selecting the import file or sample input files.

You can override the pattern in the Open File dialog boxes and select a file that does not match the pattern.
NOTE

b. Select the Create log files on errors option to indicate that once the import process has completed, the system will
create a special error log file in the same folder where the original import source file is located.
This error log file will contain all records rejected during the import operation, stored in the internal XML format.
Whether you select this option or not, the same rejected records will be stored on the server, attached to the proper
Import Result.

C•CURE Database Migration Guide 47

 If you select the Create log files on errors option, the format in which the rejected records are stored will differ
NOTE from the format of the incoming records since the import process converted the data from CSV to internal XML
format.

c. Click the Advanced button. The Advanced Properties sheet opens, as shown in Figure 12 on Page 48.
Figure 12: Import Advanced Properties Sheet

— For the Default Culture property, change the entry or leave the default to control how the CSV date format is
parsed.
Example:
mo/day/year for en-US or day/mo/year for en-UK
— For the Default Tag property, replace ‘ExternalObject’ with the name of the top-level object being imported—if you
know it; or Click to select a type from the drop-down list.
Example:
Personnel
— For the Keep Duplicate Columns property, set as False—the default—(recommended) to have the import
concatenate (combine) the values from the duplicate columns into one pipe-delimited value; or change the property
to True to have the import put the values into separate entries.

— Click Save to return to the Data Import Editor or to cancel the changes.

Selecting the Default Import Mode

An Import must have a defined Import mode rule to follow, whether the process only adds records to the C•CURE 9000
database without doing any matching or updates the database after doing matching in either of two ways.
■ Add only; do not match records: all records in the import source are imported into C•CURE 9000. No matching is
performed.

C•CURE Database Migration Guide 48

 ■ Update when matched; otherwise add: If the import source contains records that exactly match existing records in
C•CURE 9000, the records in C•CURE 9000 are updated using imported records. If C•CURE 9000 does not contain
records that exactly match those being imported, the import adds records from the source to C•CURE 9000.
■ Update only matched; do not add records: only records that exactly match records in the import source are updated. If
the records in the import source do not exactly match those already in C•CURE 9000, the records are not imported.

If you select either of the update options, you must specify matching fields.

To Choose the Default Import Mode

1. In the Default Import Mode box, select one of the following three options:
• Add only; do not match records
• Update when matched; Otherwise add
• Update only matched; do not add records
If you select the Update only matched; do not add records option, the Match Fields tab is selected on the Data
Import Editor and the following message displays:

2. If you do not want to select match fields right now, click No. (You must then click the Match Fields tab to open it later on.)
For information about matching fields, see Specifying Matching Fields on Page 49.
- or -
Click Yes to select match fields immediately.
The Select File with Sample dialog box opens for selecting (if you have not yet selected a sample input file). For detailed
information, see “Selecting and Viewing a Sample Input” in the Data Import chapter of the C•CURE 9000 Software
Configuration Guide.

Specifying Matching Fields

When you define an import that requires updating records, you must specify the fields that you want to match. The fields in the
source must match fields in the C•CURE 9000 schema. When matching records, C•CURE 9000 evaluates each record
individually. The system considers a record a match only if all fields designated as matching fields match only one record in the
C•CURE 9000 database. If more than one record is found, the system logs an error and rejects the record

To specify the fields that you want to match, use the Match fields tab of the Data Import editor. For detailed procedures, see
the Data Import chapter of the C•CURE 9000 Software Configuration Guide.

C•CURE Database Migration Guide 49

Running Imports
When running an import, you must specify a pre-configured Import Definition. For details about creating an Import Definition,
see Creating an Import Definition in C•CURE 9000 on Page 46.

The order in which you import objects into C•CURE 9000 is important.
■ When you use the automated “Listening on data” method, the system automatically imports the records in the correct
order.
■ If you are importing manually, import objects in the sequence detailed in The Import Sequence for C•CURE 800 Records
on Page 39.

Due to multiple parent-child dependencies between object types, attempting to import objects in any order other
NOTE than the sequence described in that section may cause the import to fail.

For further details on running these imports, see the Data Import chapter in the C•CURE 9000 Software Configuration Guide.

Running an Import by Listening on Data from the Import Watcher

Import Watcher is a special server component that can run on a separate computer, but usually starts on the same computer
as the main server. This component lets you import records into C•CURE 9000 on demand without Operator intervention,
predetermined Schedule, or Event notification. Import Watcher constantly monitors external events, usually for creation of new
files in a specified folder.

The Import Watcher component does the following:

1. Loads all the Import Definitions at start time and initializes the import sources configured for listening to external events.
2. Listens for any changes to the listening import sources and re-initializes them if the server or one of the clients modifies
their configuration.

Import Watcher also cleans up the status of the Import Definitions so they all have a ‘Disconnected’ value before initialization
(After initialization, the status is ‘Listening’). This provides needed recovery from any abnormal termination of the server’s
process, which could leave the statuses in the wrong state indicating that the Imports were active.

To Run an Import by Listening on Data from Import Watcher

1. Open an existing Import Definition on the Data Import Editor, or create a new one.
2. Configure your Import Definition appropriately according to the directions in this appendix, making sure that on the General
tab (shown in Figure 10 on Page 46) you specify the following:
• Automation mode as Listening on data
• Path to a folder on the server where the files you are importing will be placed
• File pattern to be used as a filter when retrieving files from the preceding

3. Save the Import Definition by clicking .

4. To confirm that Import Watcher is running on the C•CURE 9000 Server computer, click Start>All Programs>Software
House>
C•CURE 9000>Server Configuration.
5. On the Services tab, make sure that the Software House CrossFire Import Watcher has a status of Running.
6. If the Import Watcher needs to be started, click Start Service.

C•CURE Database Migration Guide 50

You can also stop/start the Import Watcher from listening for selected Import Definitions from the Data Import Dynamic View
context menu. For information, see the next section, Stopping/Starting Listening from the Import Watcher on Page 51.

Stopping/Starting Listening from the Import Watcher

Two menu selections on the Data Import Dynamic View context menu let you select one or multiple Import Definitions with an
automation mode of ‘Listening on data” to stop or start the Import Watcher listening for these Imports, as follows:
■ Stop Listening – available for an Import Definition with ‘Listening’ status
■ Start Listening – available for an Import Definition with ‘Disconnected’ status

When you select multiple Import Definitions on the Dynamic View, as long as one of them has the required automation mode
and required status, the ‘Stop Listening’ and/or ‘Start Listening’ selections become available on the context menu. However,
the relevant action will not be applied to Imports that do not actually meet the criteria.

Once you have stopped the Import Watcher listening for specific Import(s), you must use the ‘Start Listening’ selection to
reactivate listening for the import(s).

■ The Stop/Start Listening menu selections work only when the Import Watcher server component is
NOTE running.
■ Restarting the C•CURE 9000 driver automatically restarts the Import Watcher listening for any Import
Definition(s) stopped by the ‘Stop Listening’ selection.

To Stop Listening for an Import from Import Watcher

1. In the Navigation Pane of the Administration Workstation, click the Configuration pane button

.
2. Click the Configuration drop-down list and select Data Import.

3. Click to open a Dynamic View showing a list of all Data Import objects.
4. Select one or more Import Definitions with the ‘listening on data’ automation mode and ‘Listening’ status and right-click to
open the Data Import Context menu.

5. From the Import Context menu, select Stop Listening.

The Import Watcher stops listening for data for the selected Import Definition(s).

C•CURE Database Migration Guide 51

To Start Listening for an Import from Import Watcher
1. In the Navigation Pane of the Administration Workstation, click the Configuration pane button

.
2. Click the Configuration drop-down list and select Data Import.

3. Click to open a Dynamic View showing a list of all Data Import objects.
4. Select one or more Import Definitions with the ‘listening on data’ automation mode and ‘Disconnected’ status and right-
click to open the Data Import Context menu).
5. From the Import Context menu, select Start Listening.
The Import Watcher starts listening again for data for the selected Import Definition(s).

Running an Import Manually

To Run an Import Manually

1. In the Administration Station, on the Navigation pane, select Configuration.
2. Click the Configuration drop-down list and select Data Import.

3. On the Search pane, in the Name field, enter the name of the import you want to run, or click to display a list of
imports in the dynamic view and select the one you want to run.
4. To run the selected Import:
• Right-click the selection to open the Data Import context menu and click Manual Import.
-or -
• Double-click the selection to open the Data Import Editor for the selected import and click the Manual Import button.

When you click Manual Import, you are running the selected Import on the client computer. Consequently, the
NOTE system does not use the Default Import Directory Path—which is on the server. It opens a directory on the
client, reverting to the last directory used.

You can navigate to the default import server directory, if you wish. For more information, see “Import and
Export Settings” in the C•CURE 9000 System Maintenance Guide.

5. On the Open file to Import dialog box, select the desired file and click Open.
The progress of the import displays in the Importing Data dialog box, shown in the example in Figure 13 on Page 53 for a
completed import.
• If you want to stop the import process while the import is running, click the Cancel button that is available.

Completed Imports
Once the import has completed, a message displays in the Importing Data dialog box.

C•CURE Database Migration Guide 52

 Figure 13: Importing Data Dialog Box

The information given includes: the duration of the process and the number of records imported, rejected, deleted, and
updated.
• Click or to expand and contract the information as necessary.

You can use the buttons on the dialog box to do any of the following:
• Click Print to print a copy of the information on this dialog box.
— On the standard Windows Print dialog box, click OK.

— On the Print Preview dialog box that displays, click .

• Click Email to send a copy of the information on this dialog box.
• Click View Logs to review rejected records and errors encountered during the import.
Example:
You can examine rejected records to determine how to modify them so you can successfully re-import them.

• Click OK to close the Importing Data dialog box.

C•CURE Database Migration Guide 53

Viewing Import Results History
You can view the history of one or more completed Data Imports from the Data Import Context menu. The Import History log
displays records of all completed import operations for the selected Data Import Definition(s). The information displayed for
each historical record is detailed in a list, as shown in Figure 15 on Page 55, and includes the number of records added,
updated, deleted, and/or rejected. In addition, you can choose which of this information to display.

This Import History Log also lets you open the actual error log file generated during the import, an XML file that lists records that
did not import properly. You can use the information in the log to troubleshoot these failures: where possible, the log indicates
why the object did not import. C•CURE 9000 allows you to review and repair rejected files until they import successfully.

To review the import history for the entire C•CURE 9000, you would use the Data Import/Export History option on the
Options and Tools pane. For information, see the C•CURE 9000 System Maintenance Guide.

To View Data Import History

1. In the Navigation Pane of the Administration Workstation, click the Configuration pane button
.
2. Click the Configuration drop-down list and select Data Import.

3. Click to open a Dynamic View listing all existing Data Import objects, as shown in Figure 14 on Page 54.
Figure 14: Data Import objects in Dynamic View

4. Right-click the Data Import(s) whose history you want to view and click Find Import History from the context menu that
displays.
The Import results history opens on a Query Result list similar to that shown in Figure 15 on Page 55.

C•CURE Database Migration Guide 54

 Figure 15: Import History List

Details about Import result(s) for each Import Definition you selected are displayed in a Dynamic View. By default, not all
the columns display at first.
• Right-click in the column headings of the view to choose to display more or fewer columns. The Import history includes
the following:

Name Unique name that identifies the import in the system.

Not the name of the file containing data being imported.

Operator Name Name of the operator performing the import. (For an automated import or any import initiated by an
Event, this is the name of the operator who configured the Event Action, or last modified it.)

Created at time Time when the import was started.

Status The current status of the import, Completed, for example.

# Rejected Number of records that were rejected during the import.

# Added Number of records that were added into the system.

# Updated Number of records that were updated during the import.

# Deleted Number of records that were deleted during the import.

Description Description given to the import when configured.

No more than 500 characters.

End at time Time when the import finished.

Error Log File Name of the file containing the error log messages that were generated during the import. This
location is defined in the Import editor when defining the import.

Import File Name Name of the file containing the XML data being imported.

Partition Name of the partition of the import. (If your system is non-partitioned, ‘Default’ is entered.)

C•CURE Database Migration Guide 55

5. To view the error log for a particular import result, as shown in Figure 16 on Page 56, right-click the import in the Import
History List and click popup view from the context menu that appears.

If the size of the error log is greater than 10MB, a warning such as the following displays instead: “The size of
NOTE the error log file is n MB. It could take a long time for the file to open. Do you want continue?”
■ If you click Yes, the system tries to open the file—which could fail.
■ If you click No, the popup window displays the message, “Error Log File is too large to be displayed.”

Figure 16: Error log for selected import

6. To delete one or more import results, right-click the import result(s) in the Import History List, and click Delete from the
context menu that displays. (This does not delete the Import Object from the list in the Dynamic View.)
A confirmation message appears. Click Yes to delete the import result(s) or No to cancel the deletion.

Deleting an import result also deletes its error log file stored internally on the server.
NOTE

C•CURE Database Migration Guide 56