Client Configuration Files

Starting in version 6.1, DATABridge Client uses binary configuration files for the following:

  • The service configuration file (dbcontrol.cfg). This file contains settings for the service (Windows) or daemon (UNIX), such as scheduling, passwords, and logs. (See Appendix E for details.)
  • Data source configuration files (dbridge.cfg). Each data source has its own configuration file, which contains settings specified from 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 both types of configuration files. The first time the service is started, it creates the service configuration file. When you add a data source in the Client Console, the service creates a binary configuration file for the data source. In an upgrade, the migrate program creates a new configuration file from an existing text configuration file. Configuration files are stored in the config subdirectory of the data source's working directory.

Binary configuration files are compatible with both service-initiated operations and command-line operations. Each time you initiate a Client run, the Client reads the configuration file.

If you use the service, you must use binary configuration files. Binary configuration files are updated when you change your settings in the Client Console or in the Client Configurator.

If you don't use the service, you can use either binary configuration files or text-based configuration files. You must convert binary configuration files to text files before you can update them and must then convert them back to binary. You can also export the file and force the export command to replace the binary file by an equivalent text file, if you do like the idea of using binary files for command-line operations.

How do I edit the configuration file?

Binary configuration files are edited any time you change your configuration settings in the Client Console. You should never directly modify a binary configuration file. This will corrupt the file.

If you need to change a parameter that is not supported by the Client Console, you can export the binary configuration file to a readable text file. After you edit the text file, you can import the updated file to create a new binary configuration file. The import command performs all the necessary checks to ensure that your changes are valid.

Because passwords are stored in the configuration file as encrypted information, the only way to read them is by exporting the configuration file to a text file format.