What are the Minimum Acrolinx System Requirements?
- A modern multi-core CPU.
- 4 GB dedicated RAM with an extra 1.5 GB RAM for any additional language servers.
- Additional 4 GB of RAM for running the Analytics server.
- 5 GB of free hard disk space in the installation directory.
The hardware requirements for each language server, the Analytics server, and the core server in a distributed installation are the same as for a single-computer installation. These requirements also apply for installations in virtualized environments.
Best Practice System Requirements
- A modern multi-core CPU with one CPU core available per Acrolinx service.
- 8 GB dedicated RAM with an extra 4 GB RAM for any additional language servers.
- Additional 8 GB of RAM for running the Analytics server.
- 20 GB of free hard disk space in the installation directory.
The Acrolinx server or its components (core server, language servers) require a computer with a supported operating system. The Acrolinx server requires a compatible web browser and the Java Development Kit (JDK). You can either use Oracle Java SE 8 JDK x64 or IBM Java 8 SDK 64-bit.
For a full list of compatible software, see the Acrolinx compatibility guide .
Checking a document in a client requires a network or internet connection to the core server. To enable access to the Acrolinx server from outside the intranet, configure the internet router to forward incoming requests to port 8031 on the Acrolinx server.
TCP Port Assignments
By default, the TCP port number configuration is as follows:
|8031||Client connection to the core server.|
|8030 and below||All installed language servers connection to the core server.|
|8080 - 8091||Analytics server connection to the core server.|
If you install each language server on a separate computer, all language servers listen on TCP port 8030 by default.
You can Change the Port of an Acrolinx Server for each server type in the respective properties file.
When you install the Acrolinx server, the Terminology Manager, Analytics database, and the reporting database each come with a default database H2 or Derby . We don't recommend you use the default databases in production. The default databases are freely distributable but aren’t optimal for storing high volumes of data in combination with the Acrolinx server.
To use an external Analytics database, confirm that we support your database format. The Analytics database needs three connections for its JReport internal databases. For more information, see Connecting to External Analytics Databases.
You need a compatible enterprise database if you use the reporting database in a production capacity or store over 5,000 terms in the Terminology Manager.
Compatible Enterprise Databases
For an up-to-date list of supported database formats, see the Database tab of the Acrolinx compatibility guide .
Terminology Storage Capacity
The storage requirements for a terminology database depend on the number of terms you need to store. Each term requires approximately 5 KB storage space per term. The amount of space that a term requires depends on the number of linked terms and information stored in custom fields. For example, if you estimate that your database must store at least 30,000 terms, then you'll need at least 150 MBs on the computer that is hosting your terminology database.
Reporting and Analytics Storage Capacity
Initially reserve at least 10 GB on the computer that is hosting your reporting database.
The storage requirements for a reporting database depend on how many checks your users run and the number of issues they generate. Once your users start running checks, you can estimate the growth of your database by running queries to analyze the average number of issues per day. After you have an approximate measurement of the number of issues per day, you can allocate more storage space and update the database size limit accordingly.
These system requirements are based on a system that isn’t running any other memory or CPU intensive applications.
The storage capacity for the Analytics server is minimal.
Firewall Software Adjustments
Adjust your local firewall software to allow the servers to listen on their assigned port and allow network traffic to this port.
For example, the firewall software must allow the core server to listen on port 8031 and allow network traffic to this port.
Also ensure that your firewall and browser security settings don’t block the following software components:
- ActiveX Components