Server external files

The DirectConnect server manages external files that reside in various subdirectories. For information on the ECDA Option for ODBC directory structure for your installation, see the appropriate installation guide for your database system and platform.

Following are brief descriptions of the server-managed external files.

License file

The license file contains licensing information entered by the client for the products and features that are being used. This site-specific file contains descriptions of server nodes that can run the license daemons, various vendor daemons, and licenses for the features and the supported products.

Log file

The log file is an active log file that contains operational information that you can use to correct problems. Although the file is maintained in U.S. English, any logged client messages appear in the client language. The log file resides in the server log subdirectory. For more information, see “Logging properties” in Chapter 2, “Configuring the Access Service Library.”

Server configuration file

The server configuration file server.cfg contains all server configuration information. It resides in the server cfg subdirectory. For more information on server configuration, refer to the Enterprise Connect Data Access and Mainframe Connect Server Administration Guide.

Access service library files

This dynamically-loaded shared library represents each access service library. The DirectConnect server identifies the library by the file name. To install, load, or access a library, verify that the executable file for that library exists in the server <install_dir>/DC-15_0/svclib subdirectory for UNIX, or the C:\<install_dir>\DC-15_0\svclib subdirectory for Windows.

Access service library configuration file

This file contains information for the access service library and all of its access services. Each access service library has a configuration collection. The server defines the file format, but each configuration property is defined by the access service library, regardless of whether the property is managed at the access service library or the access service level. The configuration files reside in the server cfg subdirectory.

For information on configuring access service library properties, see the appropriate Access Service Guide for your database system.

Service name redirection file

This optional file contains all information necessary to redirect incoming requests for access service names to other access services. The file resides in the server cfg subdirectory. For more information, see Chapter 6, “Using Service Name Redirection,” in the Enterprise Connect Data Access and Mainframe Connect Server Administration Guide.

Trace file

This file is the only active trace file for the system and it provides debugging information for Sybase Product Support Engineers and Technical Support personnel. You can turn it on and off through server configuration. Although the trace file is maintained in U.S. English, any logged client messages appear in the client language. The trace file resides in the log subdirectory. For tracing information, see “Tracing properties” in Chapter 2, “Configuring the Access Service Library.”