Skip to main content
Version: v2026.0.0

Spring Boot standalone

ARender can run directly on a host without Docker. The distribution ships two packages: a viewer UI package and a rendition installer. For production, Docker Compose or Kubernetes Helm are the recommended approaches.

Two packages to download​

PackageContents
arondor-arender-hmi-spring-boot-package-2026.0.0.zipViewer UI: a Spring Boot JAR, startup scripts, configuration files, and a lib/ directory for connector JARs
rendition-engine-installer-2026.0.0-rendition.jarRendition installer: extracts the Document Service Broker and all rendition microservices (converter, renderer, text handler) into a self-contained directory
ARender Rendition

ARender backend application installer

Sha256JAR
ARender Web-UI

ARender frontend application (Spring Boot)

Sha256ZIP

Prerequisites​

  • Java 25 installed on the host (verify with java -version)
  • LibreOffice installed if Office document conversion is needed
  • ImageMagick 7 installed if image conversion is needed
  • ffmpeg installed if video conversion is needed
  • wkhtmltopdf installed if HTML/email conversion is needed

Step 1: Install the rendition​

Run the installer JAR. It extracts the full rendition stack into the current directory:

java -jar rendition-engine-installer-2026.0.0-rendition.jar

This creates the following structure:

ARender-Rendition-2026.0.0/
  ARenderConsole.bat          # start script (Windows)
  ARenderConsole.sh           # start script (Linux)
  setenv.bat / setenv.sh      # JVM memory and arguments
  custom_setenv.bat / .sh     # user overrides
  versions.json               # third-party tool versions
  modules/
    RenditionEngine/           # service broker JAR + client_libs/
    TaskConversion/            # converter JAR + DirectOffice, AROMS2PDF
    PDFOwl/                    # renderer JAR + native PDFOwl library
    PDFBoxEngine/              # fallback PDF renderer JAR
    JNIPdfEngine/              # legacy JNI renderer (deprecated)
    fonts/                     # shared font directory
    tmp/                       # shared temporary directory
  samples/                     # sample documents for testing
  third_party/                 # LibreOffice, ImageMagick, FFmpeg, wkhtmltopdf

The installer also downloads and installs third-party tools (LibreOffice, ImageMagick, FFmpeg, wkhtmltopdf) into third_party/ based on the versions listed in versions.json. On Windows, an update.bat script handles this; on Linux, use update.sh.

Step 2: Configure memory and JVM arguments​

Edit setenv.bat (Windows) or setenv.sh (Linux) to adjust memory allocations:

export ARENDER_DFS_MEMORY=512m
export ARENDER_PDFBOX_MEMORY=4096m
export ARENDER_JNIRENDERER_MEMORY=512m
export ARENDER_CONVERSION_MEMORY=1024m
export ARENDER_BROKER_MEMORY=512m

JVM arguments are also set in this file. The defaults include:

export ARENDER_BROKER_JVM_ARGS="-Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dloader.path=client_libs/ -Dfile.encoding=UTF-8"

For custom overrides, use custom_setenv.bat or custom_setenv.sh instead of editing setenv directly. These files are not overwritten during updates.

Step 3: Start the rendition​

# Linux
./ARenderConsole.sh

# Windows
ARenderConsole.bat

The script sources the environment, clears the tmp/ directory, and starts the rendition engine JAR (modules/RenditionEngine/rendition-engine-micro-service-2026.0.0.jar). The rendition engine is the service broker: it discovers and orchestrates all other microservices in the modules/ directory.

Wait for the log line Started RenditionEngineApplication on port 8761.

Step 4: Extract the viewer UI​

Unzip the viewer UI package:

unzip arondor-arender-hmi-spring-boot-package-2026.0.0.zip

This creates:

arondor-arender-hmi-spring-boot-package-2026.0.0/
  ARenderConsole.bat / .sh       # start script
  arondor-arender-hmi-spring-boot-2026.0.0.jar
  configurations/
    arender-custom-client.properties    # viewer UI overrides
    arender-custom-server.properties    # server-side overrides
    arender-custom-integration.xml      # Spring XML overrides
    arender-custom-server-integration.xml
  lib/                                  # connector JARs (e.g. CMIS, FileNet)
  public/                               # static web resources

Step 5: Configure the viewer​

Edit configurations/arender-custom-server.properties to point the viewer to the rendition broker:

arender-custom-server.properties
arender.server.rendition.hosts=http://localhost:8761/

If the rendition runs on a different host, replace localhost with its hostname or IP.

To add a connector (e.g., CMIS for Alfresco), place the connector JAR in lib/:

lib/arondor-arender-cmis-2026.0.0-jar-with-dependencies.jar

Step 6: Start the viewer​

# Linux
./ARenderConsole.sh

# Windows
ARenderConsole.bat

The script finds the Spring Boot JAR and runs java -jar on it. The viewer is accessible at http://localhost:8080.

Verify the deployment​

Open a browser to http://localhost:8080. To test with a sample document:

http://localhost:8080/?url=file:///path/to/ARender-Rendition-2026.0.0/samples/arender.pdf

Check the rendition health:

curl http://localhost:8761/actuator/health

A healthy response returns {"status":"UP"}.

Installing as a system service​

Both packages include scripts to install ARender as a system service.

ARender Web-UI:

./ARenderHMIService-install.sh

ARender Rendition:

./installAsService.sh

On Linux, these scripts create systemd units. Start and enable with:

systemctl enable arender-hmi arender-rendition
systemctl start arender-rendition
# Wait for the broker to be ready, then:
systemctl start arender-hmi

OAuth2 authentication​

OAuth2 is supported in Spring Boot standalone mode. Add the following to configurations/arender-custom-server.properties:

arender-custom-server.properties
arender.server.oauth2.enabled=true
spring.security.oauth2.client.registration.arender.client-id=arender-client
spring.security.oauth2.client.registration.arender.client-secret=your-secret
spring.security.oauth2.client.registration.arender.provider=keycloak
spring.security.oauth2.client.registration.arender.authorization-grant-type=authorization_code
spring.security.oauth2.client.registration.arender.scope=openid
spring.security.oauth2.client.provider.keycloak.authorization-uri=https://keycloak.example.com/realms/arender/protocol/openid-connect/auth
spring.security.oauth2.client.provider.keycloak.token-uri=https://keycloak.example.com/realms/arender/protocol/openid-connect/token
spring.security.oauth2.client.provider.keycloak.jwk-set-uri=https://keycloak.example.com/realms/arender/protocol/openid-connect/certs
spring.security.oauth2.client.provider.keycloak.user-name-attribute=preferred_username
spring.security.oauth2.resourceserver.jwt.issuer-uri=https://keycloak.example.com/realms/arender
Last updated on