libtcl.cfg and libtcl64.cfg (for 64-bit applications) contain information about three types of drivers:
Network (Net-Library)
Directory Services
Security
A driver is a Sybase library that provides an interface to an external service provider. Drivers are dynamically loaded so that you can change the driver used by an application without relinking the application.
The syntax for a network driver entry is:
driver=protocol description
where:
driver – is the name of the network driver.
protocol – is the name of the network protocol.
description – is a description of the entry. This element is optional.
If you do not specify a network driver, an appropriate
driver for your application and platform is automatically used.
For example, for UNIX platforms, a driver that can handle threads
is automatically chosen when security services are being used.
Directory Services entries apply if you want to use a Directory Service instead of the interfaces file. See the configuration documentation for your platform, and the Open Client/Server Configuration Guide for your platform.
The syntax for a security driver entry is:
provider=driver init-string
where:
provider – is the local name for the security mechanism. The mapping of the local name to a global object identifier is defined in objectid.dat.
The default local names are:
“csfkrb5” – for the CyberSAFE or MIT Kerberos security mechanism.
“LIBSMSSP” – for Windows LAN Manager on Windows NT or Windows 95 (clients only).
If you use a local mechanism name other than the default, change the local name in the objectid.dat file (For an example, see “The objectid.dat file”).
driver – is the name of the security driver. The default location of all drivers for UNIX platforms is $SYBASE/$SYBASE_OCS/lib. The default location for Windows platform is %SYBASE%\%SYBASE_OCS%\dll.
init-string – is an initialization string for the driver. This element is optional. The value for init-string varies by driver:
Kerberos driver – the following is the syntax for init-string, where realm is the default Kerberos realm name:
secbase=@realm
Windows NT LAN Manager – init-string is not applicable.
No special tools for editing the libtcl.cfg file are available. Use your favorite editor to comment and uncomment the entries that are already in place after you install Adaptive Server.
After you install Adaptive Server on a UNIX platform, the libtcl.cfg file already contains entries for the three sections of the file:
[DRIVERS]
[DIRECTORY]
[SECURITY]
The sections do not have to be in a specific order.
Make sure that the entries you do not want to use are commented (begin with “;”) and the entries you want are uncommented (do not begin with “;”).
For more information, see the Open Client/Server Configuration Guide for UNIX
[DRIVERS] ;libtli.so=tcp unused ; This is the non-threaded tli driver. ;libtli_r.so=tcp unused ; This is the threaded tli driver. [SECURITY] csfkrb5=libsybskrb.so secbase=@MYREALM libgss=/krb5/lib/libgss.so
This file does not use Directory Services because all [DIRECTORY] section entries are commented.
Because all entries in the [DRIVERS] section for network drivers are also commented, appropriate drivers are automatically chosen by the system. Adaptive Server automatically chooses a threaded driver when you use security services, and chooses an unthreaded driver for applications that cannot work with threaded drivers. For example, Backup Server does not support security services and does not work with a threaded driver.
The ocscfg utility automatically creates section headings for the libtcl.cfg file; you can also use osccfg to edit the libtcl.cfg file.
This is a sample libtcl.cfg file for desktop platforms:
[NT_DIRECTORY] ntreg_dsa=LIBDREG ditbase=software\sybase\serverdsa [DRIVERS] NLWNSCK=TCP Winsock TCP/IP Net-Lib driver NLMSNMP=NAMEPIPE Named Pipe Net-Lib driver NLNWLINK=SPX NT NWLINK SPX/IPX Net-Lib driver NLDECNET=DECNET DecNET Net-Lib driver [SECURITY] NTLM=LIBSMSSP
See the Open Client/Server Configuration Guide for Desktop Platforms.
