Directories and Files

The following directories and files are important to the core functionality of your Acrolinx Server and contain data that is specific to your installation:

• The terminology database

  <INSTALL_DIR>\db\terminology

  The terminology database contains all terms, fields, categories, and filters. Images aren’t part of the database and are saved in the following directory: %ACROLINX_CONFIGURATION_ROOT%\server\www\uploaded Images\.

• Reporting database backup files

  <INSTALL_DIR>\server\www\output\reporting\backup\

• Reuse repositories

  <INSTALL_DIR>\data\reuse\<LANGUAGE_ID>\<REPOSITORY_NAME>

  This directory stores reuse repositories.

• The server configuration files

  %ACROLINX_CONFIGURATION_ROOT%\server\bin\

  The server configuration files control the performance, logging, and connectivity of the Acrolinx Server.

• The language configuration files

  %ACROLINX_CONFIGURATION_ROOT%\data\<LANGUAGE_ID>\configuration.properties

  Each installed language in the path %ACROLINX_CONFIGURATION_ROOT%\data\<LANGUAGE_ID>\ contains a copy of this file (where <LANGUAGE_ID> is a two-letter abbreviation of each installed language). Each of these files defines the behavior of the writing guidance for the given language.

• The server output directories

  <INSTALL_DIR>\server\www\output\<LANGUAGE_ID>

  Acrolinx stores reports for each file or directory that was checked here, for example the Scorecard and a report of new terms found. As these files consume an increasing amount of hard disk space, it’s necessary to move old files into a backup location.

  Additionally, the report files can be treated as formal records in any Six Sigma or ISO 9000 Certified Quality Management System and may be considered legal records in many regulated industries.

• The SEO reports directory

  <INSTALL_DIR>\components\seo\db\json\seofindings

  If you use Acrolinx to check your documents for SEO, Acrolinx stores a separate SEO report for each file or directory structure that was checked. As these files consume an increasing amount of hard disk space, it’s necessary to move old files into a backup location.

  Additionally, the report files can be treated as formal records in any Six Sigma or ISO 9000 Certified Quality Management System and may be considered legal records in many regulated industries.

• The configuration directory

  C:\ProgramData\Acrolinx\ServerConfiguration\

  The configuration directory stores all overlay copies of all files that you use to configure the Acrolinx Server. When you install the server, an empty configuration directory is created at a default location that is separate from the server installation directory. You create files in the configuration directory and restart the server. When the server restarts, the server loads updated settings from files that are detected in the configuration directory. All remaining standard settings are loaded from the installation directory as usual.

To Conserve Disk Space, You Can Periodically Remove Older Files from the Following Directories:

• The term export directory

  <INSTALL_DIR>\www\output\exportedTerms

  This directory stores files which users have exported from the Terminology Manager.

• Reporting database backup directory

  <INSTALL_DIR>\server\www\output\reporting\backup\

  This directory stores reporting database backup files that users have created when using Acrolinx Analytics.

• The temporary terminology import file

  <INSTALL_DIR>\data\temp\

  These files contain the data, which is imported when importing terminology. If you regularly import terminology data, the amount and size of these files increases. You can delete these files after the import is finished.

  You can open these files in any text editor to verify that the content is the imported data.

• Temporary dashboard downloads

  <INSTALL_DIR>\server\www\output\dashboardExport\

  When you've created terminology backups all terminology database backups are stored here. You can delete the older files, since the download should only be made once.

• Workload capture requests

  <​I​N​S​T​A​L​L​_​D​I​R​>​\server​\www​\output​\recorded​Requests​\

  When you've created workload captures all recorded requests are stored here. You can delete the older files, since the download should only be made once.