Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
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 (versions 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 Communications Administration 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 Version 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 a .ini file exported from a previous release)
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.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Communications Server Administration Guide Published: 23 June 2003 |