Bookshelf Home | Contents | Index | PDF |
Siebel CTI Administration Guide > Configuring Siebel CTI > Exporting and Importing Communications Configuration Data > Importing Communications Configuration DataYou might have to import communications configuration data from a file into the database for several reasons. You can import data previously exported from the same Siebel CRM version or from a previous version. You can also use DEF files to import data that you previously exported from another configuration or another Siebel database, for example, exporting data from a test Siebel database and importing it into your production Siebel database. An import file must contain valid data and use correct DEF file notation. The import file must be consistent with files exported from the current Siebel CRM version, or consistent with previous versions. Each configuration file that you export has an entry like this: [Siebel] CAUTION: The preceding entry applies to any Siebel CRM version 7.x or 8.x software. For any communications configuration file that you import that does not contain an entry as shown, upgrade steps are performed on the file. Do not manually add such an entry to a configuration file unless the file is known to be valid and does not have to be upgraded. For files that were created in previous Siebel CRM versions (before version 7.0), the upgrade scenario applies. When importing files from previous versions, import the INI file first, and then the DEF file. For more information about the DEF file format, see Communications DEF Files. CAUTION: When you import communications configuration data, all existing data of the same type is first deleted from the database for the current configuration. New data is then inserted. You cannot cancel an import operation after you begin it. If you are not sure of the effects of importing configuration data, then export the old configuration data to a DEF file before you import the configuration data. To import communications configuration data
|
Siebel CTI Administration Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |