1. White Star Software
  2. Advanced Alerting Configuration

Configuration File Hierarchy

Configuration File Hierarchy

ProTop is configured via a series of configuration files [PROTOPDIR]/etc/*.cfg.

Default configuration files are provided but should not be modified directly as they will likely be overwritten by subsequent updates.

Instead, if you know you need non-default behavior from a given ProTop component (check with WSS or the forum if you are unsure), copy the default configuration file and rename it according to the following convention:

  1. [cfgType].friendlyName.cfg
  2. [cfgType].serverName.resrcType.cfg
  3. [cfgType].custId.resrcType.cfg
  4. [cfgType].resrcType.cfg
  5. [cfgType].ServerName.cfg
  6. [cfgType].custId.cfg
  7. [cfgType].cfg (the default file)

Where [cfgType] above is a configuration file type like alert, pt3agent, schedule etc.

NOTE: ProTop looks for configuration files in the order specified above and stops as soon as one is found. One exception is messages.cfg, the file that contains the ProTop responses to promsgs messages written to database log files. ProTop always uses the default messages.cfg file then looks for etc/messages.yourCustId.cfg and loads it if found. This allows a site to add and/or override responses to promsgs messages.

Examples:

For customer ID z8331, we might find the files etc/pt3agent.z8331.cfg and etc/alert.z8331.cfg. These files follow naming convention 6. above.

If our customer has a database with a friendly name of mb117sports (as defined in etc/dblist.cfg) then we might find etc/pt3agent.mb117sports.cfg and etc/alert.mb117sports.cfg which fiollow convention 1. above.