Product Documentation

FairCom DB V12 Updates

Previous Topic

Next Topic

New ctsrvr.cfg Location and Default Additions

ctsrvr.cfg Moved to the New config Directory by Default

The ctsrvr.cfg file has been moved from the working directory (where faircom.exe is located) to the new config directory. This move centralizes all configuration files within a single directory for easier management. The server tries to load ctsrvr.cfg from the following directories:

<faircom>/config/ctsrvr.cfg

falling back to:
<faircom>/server/config/ctsrvr.cfg

and finally to:
<faircom>/server/ctsrvr.cfg

The configuration file can be placed in a directory of your choosing by using any of these procedures:

  • Passing a command-line parameter, e.g.:
    ctsrvr CTSRVR_CFG my_path/my_config_filename
  • Setting the CTSRVR_CFG environment variable
  • Calling ctdbSetConfigurationFile() before calling ctThrdInit() for embedded server models (not supported on FairCom RTG)

All Plug-In Settings and Config Files in config Directory by Default

By default, all of the current plug-ins' settings files and configuration are loaded from the config directory. This applies to Replication Manager, web server, ThingWorx, OPC, and Automatic System Time/TimeStamp) settings files.

Best Practice: User-created plug-ins do not have to follow this practice, because they can be written to load their settings from wherever you want. However, for consistency and simplicity of administration, it is strongly recommended as a best practice to place all settings files in the config directory.

Password Security Options (Commented Out) in Default Server Configuration File

Password security options have been added to the default ctsrvr.cfg file. These options are commented such they do not affect your configuration. They are easily enabled by removing the semicolon (";") at the beginning of the initial SUBSYSYEM line:

;SUBSYSTEM SECURITY PASSWORD {

MINIMUM_LENGTH 8

REQUIRED_CLASSES 3

EXPIRE_IN_DAYS 180

}

Dynamic Configuration Changes Now Persisted

FairCom DB now has the ability to store configuration options enabled or modified at run-time. A new file in FAIRCOM.FCS is automatically created (even in an existing FAIRCOM.FCS) at V12/V3 server startup. Stored keywords overwrite any setting in ctsrcr.cfg.

See

COMPATIBILITY NO_CONFIG_PERSISTENCE

As of this release, the only supported keyword for this option is READONLY SERVER. More keywords will be added in the future.

TOCIndex