Show Hide

 

Feedback

  • Contents
 

About CIC Data Export and Import

Interaction Migrator allows you to export and import CIC configuration data. The procedures are the same for both migrations and recovery – the only distinction is that during an import, you select either Migration Mode or Recovery Mode.

Tracing

Interaction Migrator uses the same tracing functionality as CIC. The Interaction Migrator install includes the trace configuration and log viewer utilities. The default output directory for the trace logs is the inin_tracing folder under the user’s temp directory (%temp%\inin_tracing). Tracing is always on by default and it generates logs only when Interaction Migrator is running. Tracing levels are at 100% by default; however, you can adjust them as needed.

CIC Service

Interaction Migrator requires you to stop the CIC Service when exporting or importing CIC data. The export process can be processor intensive, so to avoid a Switchover or any call interruptions, stop the CIC Service. The import process can only run when the CIC Service isn’t running. If you cannot schedule a system outage for your CIC system, there are two options:

  • If you have a Switchover pair, you can stop CIC Service on the backup server and take the export from there.

  • If you only have a single CIC server (no Switchover pair), you can run Interaction Migrator Console to perform your export. For more information, see About Interaction Migrator Console.

When performing imports on Switchover pairs, stop the CIC Service on both the primary and backup servers. Do not import configuration data on a backup server, even if you stopped the CIC Service, while the other CIC server is running. If you did, the backup CIC server would overwrite the imported data with the replicated data from the primary CIC server, or worse, leave the pair in an invalid state.

Data Interdependencies

The following items have interdependencies. If you choose to export any of these items, their interdependent items export also to prevent an invalid configuration after the import.

  • AdminConfig — This item contains all of the license assignments. If you choose to export AdminConfig, the system selects Users and Workstations so license assignments don't import to Users/Stations that don't exist on the CIC 2015 R1 or later server.

    Note: If you are not importing at the same time, or have not imported the Tracker Config data already, do not import the AdminConfig file. The AdminConfig file pulls in User data so importing it without the Tracker Config data causes problems with the Tracker Config data.

  • IPA — If you choose to export this item, the system selects all of the other IPA-related items. If you don't import all the IPA configuration settings, IPA won't work after the import.

  • IP\Handlers — If you choose to export this item, the system selects <SERVER>\IP. Conversely, if you select <SERVER>\IP, the system selects IP\Handlers. Export these items together so that the Handlers function properly after the import.

  • IP Phones — If you choose to export IP Phones, the system selects IP Phone Proxy Groups. Export these items together to allow the IP Phones to function properly after the import.

  • Interaction Recorder Master Key File — If you choose to export the Interaction Recorder Master Key File, the system selects Interaction Recorder. Export these items together to allow Interaction Recorder to function properly after the import.

Export Data Encryption

Interaction Migrator encrypts the contents of export files using AES 256-bit encryption. AES256 encryption is PCI (Payment Card Industry) compliant.