Bookshelf v7.5: Driver File Naming on Microsoft Windows and UNIX Platforms

Siebel Communications Server Administration Guide > Configuring Communications Drivers and Profiles > About Communications Drivers and Profiles >

Driver File Naming on Microsoft Windows and UNIX Platforms

The 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 Platforms

On 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:

The value can correspond exactly to the name of the operating system file. For example, for a file named "driver.dll," you can enter "driver.dll" as the Library Name value. This approach is recommended.

The value can correspond to the name of the file but without the extension ".dll". For example, for a file named "driver.dll," you can enter "driver" as the Library Name value.

Driver File Naming on UNIX Platforms

On UNIX, the name of the driver file to load is generally obtained by prepending "lib" 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:

The value can correspond exactly to the name of the operating system file. For example, for a file named "libdriver.so," you can enter "libdriver.so" as the Library Name value. This approach is recommended.

The value can correspond to the name of the file but without the elements "lib" and ".so." For example, for a file named "libdriver.so," you can enter "driver" as the Library Name value.

Additional Considerations for Driver File Naming

Following are additional considerations for specifying driver file names.

If you add a new custom driver file with any other naming pattern, then the file name must include a dot, and you must provide a Library Name value that corresponds exactly to the name of the operating system file.

If you install any custom driver file in a nondefault location, then some element of the file or path name must include a dot, and you must provide a Library Name value that includes the full path where the file can be located by the Siebel Server or Siebel Dedicated Web Client that is to load the driver.

If you create a custom driver that aggregates an existing driver provided by Siebel Systems, reference the operating system file for the Siebel driver by its exact name, regardless of what text is displayed for the Siebel driver in the Library Name field.

If the file path is not specified, it is assumed that the driver is located in the bin subdirectory of the Siebel Server or Siebel Dedicated Web Client installation directory. The installation from which the driver file is loaded is the machine on which the channel manager runs.