The System Configuration enables the user to view and maintain configuration settings of various FraudOne systems and their components. The goal of this centralized configuration is to have a consolidated, and auditable way to track changes of the systems configuration settings.

All of the various configuration parameters are collected in a central configuration database. Changes to the configuration elements stored in the database can be subject to access control. They can also be limited to authenticated users. In all cases, they will be recorded by means of historisation as well as a protocol similar to the FraudOne reference database.

Components read their configuration from a configuration server using a client/server message interface provided solely for this purpose. The file name and, depending on the component and system topography, a machine name, an instance type, and an instance name are used as criteria to retrieve a particular configuration file from the configuration server. To allow proper access of the components to their configuration settings, a system administrator must make sure that the following things are installed correctly:

•A configuration server is installed and running

•On each machine hosting a component that requires configuration server access, the configuration server must be made available using the SetupCfg program

 

Important The file name is not case sensitive!

 

 

---