Client Configuration Files

The DATABridge Client 6.1 and later uses binary configuration files. Binary configuration files are compatible with both service-initiated operations and command-line operations. However, if you use the service, you must use binary configuration files. (Command-line operations can use either binary or text configuration files. For information about creating text configuration files, see Export or Import a Configuration File.)

The DATABridge Client software uses the following configuration files:

• The service configuration file (dbcontrol.cfg). This file contains settings for the service (Windows) or daemon (UNIX) that specify scheduling, passwords, logs, and more. For more information, see Appendix F.
• Data source configuration files (dbridge.cfg) used by the DATABridge Client programs (DBClient, DBClntCfgServer and dbutility). Each data source has its own configuration file, which can be updated using the Client Console and Client Configurator. The Client configuration file overrides any equivalent parameter settings on the host.

In a new installation, the service creates the service configuration file in the config directory of the service's working directory (also referred to as the global working directory) the first time the service is started. The service also creates the logs and scripts directories of the service's working directory at that time. When you add a data source in the Client Console, the service creates a binary configuration file (dbridge.cfg) for the data source. Data source configuration files are stored in the config subdirectory of the data source's working directory.

In an upgrade, the Migrate program takes your existing configuration files and creates new data source configuration files from them. It also creates a new service configuration file and adds your preexisting data sources to it.