Understanding Configuration Files

Configuration files work with HTML files and the users database. The HTML file can be used to determine which configuration file will be used. Once a specific configuration file is requested, the CTCBridge session attributes are applied to the environments based on the information stored in the configuration file. These configuration files might contain the host connection information as well as information about the appearance and data handling of CTCBridge.

 

Configuration Parameters

Configuration files contain variable names for configuration settings you will normally determine through the graphical user interface of menu commands and dialog boxes in the CTCBridge applet.

 

CTCBridge assigns every missing parameter in a configuration file to a default setting. Those options set to a default setting will not necessarily appear in a configuration file. This default setting allows the least amount of authority to the user and the most security for MultiBridge. You can modify the default.cje with whatever configuration changes you want. A .cje file holds configuration values that differ from the default values.

 

Consequently, you might find that your configuration files vary quite a bit depending upon the options you have chosen to store in them. See 5T27 Config for more information.

 

Working with Configuration Files

Create and modify configuration files by using CTCBridge menu commands from a client site. We strongly recommend you do not use a text editor to modify configuration files by hand. It is easiest to get things right the first time by using the menus and windows in CTCBridge.

 

Configuration files are saved in the MultiBridge directory, jt27 subdirectory. The installation routine automatically creates a configuration file for you: "default.cje."

 

The “default.cje” file allows no administrative authority and requests the “Default” station from MultiBridge.

 

Related Topics: