Siebel Communications Server Administration Guide > Configuring Session Communications >

Exporting and Importing Configuration Data

Siebel Communications Server provides import and export mechanisms that enable administrators to move communications configuration data between the database and ASCII text files. You can use these mechanisms to:

• Upgrade your implementations from previous versions of Siebel CTI (release 6.x and earlier)
• Move configuration data between databases or between communications configurations within the same database
• Move configuration data and custom communications drivers obtained from another source such as a third-party vendor into Siebel Communications Server
• Edit or enter data in text files rather than directly within the Administration - Communications screen

For more information about adding custom communications drivers, see Configuring Communications Drivers and Profiles.

For more information about upgrading Siebel CTI from previous versions, see Upgrading from Release 6.x.

The basic options for exporting and importing are as follows:

• Export communications configuration data from the database to a .DEF file
• Import communications configuration data into the database from a .DEF file (or from an .ini file exported from a previous release)

  Table 6 describes how driver and profile parameters are handled by the import process from a .DEF file to the database.

  Table 6. Parameter Management by the Import Process

  If the parameter ...	For example ...
  Does not exist in the database, the import process adds it.	If the .DEF file contains an entry: Driver:CIMServer = "Blitzlab29" The import process updates the database as follows: Driver:CIMServer = "Blitzlab29"
  Exists in the database, the import process updates it.	If the database contains an entry: CIMServer = "CHANGE_ME" and the .DEF file contains an entry: Driver:CIMServer = "Blitzlab29" The import process updates the database as follows: Driver:CIMServer = "Blitzlab29"
  Is deleted from the .DEF file, it remains in the database after the import process is completed.	If both the .DEF file and the database contain the entry: Driver:CIMServer = "Blitzlab29" but then you delete the entry from the .DEF file and run the import process, the database retains the entry that you deleted from the .DEF file.

For more information about the .DEF file format, see Communications .DEF Files.

NOTE:  Using the Export Configuration and Import Configuration features, you can transfer all types of communications configuration data from one configuration to another except data for agents (and ACD queues) and telesets (and extensions). Driver and profile data could not be exported or imported prior to version 7.0.