Requirements for Specifying Driver File Names
Some additional requirements for specifying driver file names are as follows:
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 Siebel Server that is to load the driver can locate the file.
On UNIX, if you install any custom driver file in a nondefault location, then this location cannot be the
bin
subdirectory of the Siebel Server installation directory. Thelib
subdirectory, the default location for the files provided with the Siebel Business Applications on UNIX, is preferable.If you create a custom driver that aggregates an existing Siebel driver, then 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, then it is assumed that the driver is located in the
bin
subdirectory of the Siebel Server installation directory on Windows, or in thelib
subdirectory on UNIX. The installation from which the driver file is loaded is the computer on which the channel manager runs.