After you start using Acrolinx, you should back up important files and directories on a schedule consistent with your corporate usage and retention requirements. Also monitor directories that don’t contain essential files but can quickly grow in file size depending on your Acrolinx usage patterns.
Directories and Files
The following directories and files are important to the core functionality of your Core Platform and contain data that is specific to your installation:
The terminology database
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
This directory stores reuse repositories.
The server configuration files
The server configuration files control the performance, logging, and connectivity of the Core Platform.
The language configuration files
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
The Core Platform stores a Scorecard and a report of discovered terms found 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
The configuration directory stores all overlay copies of all files that you use to configure the Core Platform. 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 server temp directory
This directory stores files which users have uploaded for import in the Terminology Manager.
The export directory
This directory stores files which users have exported from the Terminology Manager.
Reporting database backup directory
This directory stores reporting database backup files that users have created when using Acrolinx Analytics.
The temporary terminology import file
These files contain the data that 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.
Backing Up Important Files and Directories
All important files and directories should be backed up regularly.
To back up each of these directories, follow these steps:
Stop the core server.Important: It’s necessary to stop the core server to make sure that the terminology database is in a consistent state.
- Copy or zip the directory and move it to a backup location.
- Restart the core server.
Changing the Maximum File Size Limit for Uploaded Files
There are several parts of the Dashboard where users can upload relatively large files. You can configure an upper size limit for such files. For example, terminology database backups or reporting database backups can take several minutes to upload. You might change this limit if you notice that file uploads are placing an unnecessary burden on your server.
- By default, the Core Platform accepts files up to a maximum of 1 GB.
- The maximum configurable value for this property is 2,147,483,648 bytes, which is about 2 GB.
- If you set the value to zero, there’s no upper size limit at all
This limit doesn’t apply to image uploads or license file uploads, which have their own hard-coded limit of 20 MB.
To change the maximum file size limit for uploaded files, follow these steps:
- Open your overlay of the core server properties file.
You find the overlay for the core server properties file in the following location:
Add the following property:
For example, to set a file size limit of 500 MB add the property as follows:
- Save your changes and restart the core server.