Exporting and Importing Communications Configuration Data
This topic describes how to export and import configuration data. It contains the following information:
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:
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.
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)
The following table describes how driver and profile parameters are handled by the import process from a DEF file to the database.
| If the parameter ... | For example ... |
|---|---|
Does not exist in the database, then the import process adds it. |
If the DEF file contains an entry:
then the import process updates the database as follows:
|
Exists in the database, then the import process updates it. |
If the database contains an entry:
and the DEF file contains an entry:
then the import process updates the database as follows:
|
Is deleted from the DEF file, then it remains in the database after the import process is completed. |
If both the DEF file and the database contain the entry:
but then you delete the entry from the DEF file and run the import process, then the database retains the entry that you deleted from the DEF file. |
For more information about the DEF file format, see Communications DEF Files.