Skip to main content
Version: v4

Requirements

Architecture

Each Rendition installation should be done on a dedicated server.

Operating system

CategoryRequirement
WindowsWindows Server 2016 or higher
LinuxKernel 2.6 or greater, glibc 2.14 or greater, minimal recommended version for Linux distributions (due to our software requirements): RedHat (7 or 8), CentOS (7), Debian (8), Ubuntu (14.04+), Amazon Linux AMI (2016.09+)

Minimal hardware

CategoryMinimumAdvised
Number of rendition server(s)12 (for high availability)
RAM8GB16GB
CPU (vCPU)48
CPU type64Bits64Bits
Storage20GoThe maximum between 20Go and a storage where a full day of temporary files can be stored

Port configuration

The ports of the different micro-services need to be free to use and are as follows:

ServiceProtocolsDefault listening port
Service brokerHTTP/HTTPS8761
Distant file storageHTTP8081
Text handlerHTTP8899
RendererHTTP9091
ConverterHTTP19999

Software requirement

SoftwareRequirement
Java RuntimeJRE 1.8 64 bits Minimum, OpenJDK 11 advised. Oracle JDK are supported, JRE IBM J9 is unsupported.
(Optional) Microsoft OfficeMicrosoft Office 2013 and up. Office 365 compatible if the server is connected to an internet connection. We recommend as well to keep Office up to date.
warning

If the JVM used is not 64 bits, the rendition will now stop its boot and warn in the logs/console that the version of the JVM used is incorrect.

Access rights

For the installation

  • The user must have the rights to create the rendition folder.
  • The user must have the necessary rights to create a service.

For the launch

The user that runs the service needs to have access to the files into the Rendition folder and the required third party softwares, as well as execution rights.

Antivirus configuration

Deactivate the scan of ARender Rendition tmp folder.