Skip to main content

Rendering Service Installation on Windows

Introduction​

Target Audience: System Administrators

This guide covers the base installation of the Rendering Service on Windows. After completing this guide, you will have the Rendering Service installed but unconfigured. You will then choose and configure your rendering-server in the Integration section.

Prerequisites​

  • Windows 10/11 or Windows Server 2019/2022/2025
  • Java 21 or later installed (verify with java -version)
  • Internet connection
  • Administrator access

Installation Steps​

1. Download Rendering Service JAR​

Get the latest rendering-service jar file here.

Unzip the downloaded zipped jar file into your rendering service application directory (e.g., C:\PubServer\rendering-service).

2. Create Directory Structure​

Create a dedicated directory for the Rendering Service if it doesn't exist:

mkdir C:\PubServer\rendering-service

Place the rendering-service.jar file in this directory.

3. Verify Java Installation​

Verify that Java 21 or later is installed:

java -version

You should see output indicating Java 21 or a newer version. If Java is not installed, download and install the appropriate JDK for Windows.

4. Configuration​

Choose your rendering-server and continue with configuration:

Rendering Server Options​

  1. Embedded PDF Renderer Configuration

    • Best for: PDF-only rendering, simpler deployments
    • Platform: Windows and Linux
    • Setup requirements: Java 21, Python 3.12, native libraries, configuration files

  2. Containerized PDF Renderer Configuration

    • Best for: Scalable deployments, cloud environments, cloud-native architectures
    • Platform: Windows with Docker, Linux (primary)
    • Setup requirements: Docker Desktop, configuration files

  3. InDesign Server Configuration

    • Best for: Complex layouts requiring InDesign features, professional publishing workflows
    • Platform: Windows / MacOS only (Adobe InDesign Server requirement)
    • Setup requirements: Adobe InDesign Server installation, configuration files

5. Optional: Create Windows Service​

If you want to run your Rendering Service automatically as a Windows Service:

  1. Download the WinSW (Windows Service Wrapper) executable from the rendering service package or from WinSW releases.

  2. Rename the executable to match your service (e.g., rendering-service-4.7.exe) and place it in your rendering service directory.

  3. Create a configuration file rendering-service-4.7.xml in the same directory with the following content:

<service>
    <id>rendering-service-4.7</id>
    <name>rendering-service-4.7</name>
    <description>Rendering Service for priint:suite 4.7</description>
    <executable>C:\PubServer\java\jdk\bin\java</executable>
    <arguments>-Dspring.config.additional-location=file:"%BASE%\{your-application-config}.yml" -Dworkers.config="%BASE%\{your-workers-config}.json" -jar "%BASE%\rendering-service.jar"</arguments>
    <logmode>rotate</logmode>
    <log>
        <mode>roll-by-size</mode>
        <sizeThreshold>10240</sizeThreshold>
        <keepFiles>8</keepFiles>
    </log>
</service>

Note: Replace {your-application-config} and {your-workers-config} with the actual file names you created during configuration. Adjust the paths to match your installation:

  • <executable> - Path to your Java executable
  • <arguments> - Configuration file names will be created when you configure your rendering server in the Integration section
  1. Install the service by opening a command prompt as Administrator and running:
cd C:\PubServer\rendering-service
rendering-service-4.7.exe install
  1. Start the service:
rendering-service-4.7.exe start
  1. To check service status:
rendering-service-4.7.exe status
  1. To stop the service:
rendering-service-4.7.exe stop
  1. To uninstall the service:
rendering-service-4.7.exe uninstall

Alternatively, you can manage the service through Windows Services (services.msc).

Validation and Monitoring​

After completing the configuration for your chosen rendering-server, start the Rendering Service. To find out more about how to monitor the rendering service and validate the output, please check the dedicated documentation.

Additional Resources​