How Acrolinx Combines Customized and Default Configurations

When you start an Acrolinx server, the server first loads any files that are detected in the configurations directory. The server then checks the installed configuration files in the installation directory. All files that are loaded from the configuration directory are logged in the core server log file. Some files in the configuration directory override the installed versions completely. Other files override individual properties only.

When the server detects a file in the configuration directory, the server evaluates the file in the following steps:

  • If the file exists only in the configuration directory, the file is loaded without further action.

    For example, CSD files for server-side segmentation are not installed with the standard Acrolinx software files unless explicitly requested. You usually create these files in your configuration directory when you need them.

  • If the file exists in both the configuration directory and the installation directory, the server checks the file type.
    • If the file is a style sheet or XML file, the installed version of the file is ignored and the version in the configuration directory is loaded instead.

      For example, if you want to change the logging level for the core server, you would create copy of the filecoreserver.log4j.xml  in your configuration directory. The version of this file in the installation directory is ignored completely.

    • If the file is a properties file, the properties in the two sets of files are compared for any conflicting properties and merged.

      If there is a conflict, the properties in the configuration overlay take priority.

      For example, suppose you have created an overlay of the English language configuration file in your configuration directory. In your overlay, you have added the following properties to override the installed defaults for the writing guide "Standard US":

      Configured Properties:

      Standard_US.termharvesting.onlyServerSide=true 
      Standard_US.terminology.sources=att:Switches

      The installed version of the language configuration file contains the following set of properties for the writing guide "Standard US":

      Installed Properties:

      Standard_US.allowInitialCaseSwitchFallback=true 
      Standard_US.termharvesting.onlyServerSide=false 
      Standard_US.gazetteer=resources/TH.gzt,resources/entities.gzt 
      Standard_US.grammarRules=rules/grammar.rul 
      Standard_US.harvestingRules=rules/standard-extended.thrul 
      Standard_US.morphology=resources/EN-US.abb 
      Standard_US.styleRules=rules/style-
      Standard-Extended.rul 
      Standard_US.terminology.sources=att:Switches;att:Routers;att:Phone

      When loading the properties, the server loads the properties  termharvesting.onlyServerSide and  terminology.sources  from the configured version of the file. The settings for these properties in the installed version of the file are ignored. The server, then loads the remaining properties from the installed version of the file so that the following list reflects the complete set of loaded properties:

      Loaded Properties:

      Standard_US.allowInitialCaseSwitchFallback=true Standard_US.termharvesting.onlyServerSide=true
      Standard_US.gazetteer=resources/TH.gzt,resources/entities.gzt 
      Standard_US.grammarRules=rules/grammar.rul 
      Standard_US.harvestingRules=rules/standard-extended.thrul
      Standard_US.morphology=resources/EN-US.abb 
      Standard_US.styleRules=rules/style-
      Standard-Extended.rul 
      Standard_US.terminology.sources=att:Switches
      On a Windows-based server, you can see exactly what properties have been loaded for each properties file in the Dashboard. Navigate to  Maintenance  Configuration Properties  and select a properties file. The preview panel shows the configured and installed properties the selected properties file.