The easiest and most reliable way to get Acrolinx up and running at scale is to use the standard stack. This is the combination of software and hardware that we use for Cloud installations, and that we support for On-premise installations. It's tested, supported, and works best in production.
- 64 GB RAM
- CPU with 8+ cores
- 1 GB+ network connection
- 10 GB network connection to the database
- 2 TB Hard-drive
OS: Red Hat Enterprise Linux 7 (x64)
Note that the operating system time zone should be set to UTC.
- Standard Database: PostgreSQL 9.6
Alternative Database: Oracle (Standard Edition or Enterprise Edition)
- Standard Java: Open Java Development Kit (JDK) 8 64-bit
Alternative Java: Oracle JDK 8 64-bit
- Web browser: latest versions of Chrome, Firefox, Safari, Microsoft Edge
For a full list of compatible software, see the Acrolinx Compatibility Guide.
Need to Grow?
The standard stack should cover most use cases with up to 8 language servers. If you want more than 8 language servers, then a good rule of thumb is to add + 4 GB RAM for each additional language server. If you have specific requirements, feel free to contact Acrolinx Support for more details.
Checking a document in an integration requires a network or internet connection to the core server. To enable access to the core server from outside the intranet, configure the internet router to forward incoming requests to port 8031 on the core server.
TCP PORT ASSIGNMENTS
To enable easier firewalling and better security, the core server has two separate endpoints with different TCP ports for external and internal communication.
Core Server Ports
|Default TCP Port||Description|
|Core Server External |
|By default, the core server listens on TCP port 8031 for external communication (from Integrations).|
|Core Server Internal |
|By default, the core server listens on TCP port 8032 for internal communication (from language and Analytics servers).|
Other Server Ports
|Default TCP Port||Description|
|Language Servers |
8030 and below
|If you install each language server on a separate computer, all language servers listen on TCP port 8030 by default. |
If you install several language servers on the same computer, the language servers use TCP ports 8029 and below, depending on the installation sequence and the number of language servers.
|Analytics Server |
Two randomly defined port numbers
|The analytics server is assigned two random TCP port numbers on startup.|
You can change the port of the Core Platform for each server type in the respective properties file.
When you install Acrolinx, each database is included with a default format. By default, Acrolinx uses the H2 database format for Terminology and Reporting, and the Derby database format for Analytics. We don't recommend that you use the default databases in production. We freely distribute the default databases but they're intended for test purposes only.
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 Connect 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 section 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. 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: