Standard Stack is the combination of software and hardware that we support for Acrolinx installations. It's a good solution for those who can't use Acrolinx Private Cloud for compliance reasons.
Before you download Acrolinx, make sure that your host system’s hardware has the following resources.
Memory and CPU requirements may increase in the future. This means you may need to scale up your system's reserved or dedicated resources to operate the Acrolinx Platform smoothly.
CPU with more than 8 cores (dedicated)
64 GB RAM for the platform (including core, language, and analytics servers)
2 TB disk space for the platform
To check your content in an Acrolinx Integration, you'll need a network or internet connection to the Acrolinx Platform.
Be sure to enable Internet Protocol version 6 (IPv6).
You can also enable access from outside the intranet. To do this, configure the internet router to forward incoming requests to port 80. If you plan to secure communication with TLS, you’ll need to do the same for port 443.
Adjust your local firewall software to allow the servers to listen on port 80 and allow network traffic to this port. Make sure that your firewall and browser security settings don’t block the software components
To install and maintain the Acrolinx Platform with the Helm chart, make sure that the host machine has internet access and can connect to the following sites:
The Standard Stack should cover most use cases with up to 9 language servers. If you need more than 9 language servers, Acrolinx suggests that you add 4 to 6 GB RAM and 100 GB additional disk space for each server.
Feel free to contact Acrolinx Support for more details.
To successfully download Acrolinx, you’ll need the software below. For a full list of compatible software, see the Standard Stack Compatibility Guide.
Though Acrolinx doesn't currently support RHEL 8, it will require migration to RHEL 8 in the next 16 months.
Be sure to set the operating system time zone to UTC. For time zones other than UTC to work, you'll need to install a zoneinfo database on your nodes.
The Acrolinx Platform deployment is only available on K3s. Acrolinx doesn’t support Kubernetes (K8s) or other local Kubernetes cluster setups like Minikube or kind.
This lightweight Kubernetes distribution is fully compliant and ready for you to use in production. For now, Acrolinx only supports a single-node cluster setup.
K3s version numbers are a combination of the implemented Kubernetes API version and a K3s-specific part. Keep in mind that future versions of the Acrolinx Platform will require K3s updates. Different versions of the Acrolinx Operator will require different Kubernetes API versions. Therefore, it's best to check the Standard Stack Compatibility Guide before you update to the latest version of K3s.
Alternative Database: Oracle 19c (Standard Edition or Enterprise Edition)
When you install Acrolinx, each database comes with a default format. Acrolinx doesn't recommend that you use the default databases in production. While Acrolinx freely distributes the default databases, you should only use them for test purposes.
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 an External Analytics Database.
You need a compatible enterprise database in the following cases:
You use the reporting database in a production capacity.
You store over 5,000 terms in the Terminology Manager.
For an up-to-date list of supported database formats, see the Database section of the Standard Stack Compatibility Guide.
The storage requirements for a Targets database depend on the number of Targets you need to store. The amount of space that a Target requires depends on the number of goals and information stored in its custom guidelines. In general, this equals about 1.6 MB storage for one Target.
For example, if you estimate that your database will store 70 Targets, you'll need at least 112 MB on the computer that hosts your Targets database.
The storage requirements for a Terminology database depend on the number of terms you need to store. The amount of space that a term requires depends on the number of linked terms and information stored in custom fields. In general, this equals about 5 KB storage for one term.
For example, if you estimate that your database will store at least 30,000 terms, you'll need at least 150 MBs on the computer that hosts your Terminology database.
The storage requirements for a Reuse database depend on the number of phrases you need to store. In general, this equals about 20 KB storage for one phrase.
For example, if you estimate that your database will store 7000 phrases, you'll need at least 140 MB on the computer that hosts your reuse database.
If you use Reuse Harvesting, you'll need additional storage for the harvested phrases.
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, the database will grow by 45 KB (on average) and by up to 500 KB (for large documents) with each check. You can configure the platform to purge old checks, though.
The storage capacity for the Analytics server is minimal.
Acrolinx is tested and works well with the latest versions of Chrome, Firefox, Safari, and Microsoft Edge.
See the Standard Stack Compatibility Guide for more detailed information.