Bookshelf Home | Contents | Index | PDF |
Siebel Communications Server 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 may 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 bin subdirectory of the Siebel Server. You can store them in another directory, if you specify an absolute path. 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 usually 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 UNIX PlatformsThe names of actual driver files to be loaded are obtained from the Library Name field in the Communications Drivers list. In some cases, the value for this field may be manipulated to obtain the name of the driver file to load. Driver File Naming on Microsoft Windows PlatformsOn Microsoft Windows platforms, 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, you can provide a Library Name value in either of two ways:
Driver File Naming on UNIX PlatformsOn UNIX, the name of the driver file to load is generally obtained by adding LIB (without a character space) 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, you can provide a Library Name value in either of two ways:
Additional Considerations for Driver File NamingFollowing are additional considerations for specifying driver file names.
|
Siebel Communications Server Administration Guide |