Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel CTI Administration Guide > Configuring Communications Drivers and Profiles > About Communications Drivers and Profiles > Communications Driver Files and Database RecordsCommunications drivers are usually based on library files, such as DLL (Dynamic Link Library) files on Microsoft Windows, or shared object files on UNIX. Alternatively, they might be executable files or other types of files. Each driver file must be written to support the Siebel Adaptive Communications API. Communications driver files are located by default in the Each communications driver file has one or more corresponding database records in the Communications Drivers and Profiles view of the Administration - Communications screen. NOTE: In this book, in discussions of configuration tasks in the Administration - Communications screen, the term communications driver or driver sometimes refers to a database record that references a driver file. In discussions of developing drivers, however, the term generally refers to the driver file itself, which is the direct product of the development process. Driver File Naming on Microsoft Windows and UNIXThe names of actual driver files to load are obtained from the Library Name field in the Communications Drivers list. In some cases, the value for this field might be manipulated to obtain the name of the driver file to load. Driver File Naming on Microsoft WindowsOn Microsoft Windows, the name of the driver file to load is generally obtained by appending .DLL to the value of the Library Name field. However, if the value of the Library Name field includes a period (.), then no manipulation of this value is performed to obtain the name of the driver file. If you add a new custom driver file that has the extension .DLL, then you can provide a Library Name value in either of two ways:
Driver File Naming on UNIXOn UNIX, the name of the driver file to load is generally obtained by adding lib (without a space character) immediately before the value of the Library Name field and, appending .so to the value of the Library Name field. However, if the value of the Library Name field includes a period (.), then no manipulation of this value is performed to obtain the name of the driver file. If you add a new custom driver file that starts with lib and has the extension .so, then you can provide a Library Name value in either of two ways:
Requirements for Specifying Driver File NamesSome additional requirements for specifying driver file names are as follows:
|
![]() ![]() |
Siebel CTI Administration Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |