priint:comet PDF Renderer - Setup Guide for Ubuntu 22.04.3 LTS
This guide outlines the steps to get the rendering-service 4.6 with PDF renderer up and running on a fresh Ubuntu 22.04.3 LTS system.
Prerequisites
- Ubuntu 22.04.3 LTS
- Internet connection
- Publishing Server - Version: >= 2025.1 (4.6)
- Rendering Service - Version: >= 4.6 - Latest version of
rendering-service.jar. - Latest version of the libs - Version: >= 5.0 (FTP) or (GitLab repository) (internal access only).
Installation Steps
1. Install Fonts and Applications
Run the following commands to install necessary fonts and applications:
locale-gen --lang en_US.UTF-8 && \
apt update && \
apt install software-properties-common -y && \
add-apt-repository ppa:deadsnakes/ppa -y && \
apt update && \
apt install -y msttcorefonts fonts-tlwg-garuda-ttf fontconfig unzip net-tools curl python3.8 libpython3.8 tidy libltdl7
2. Install JDK 17
Install Java Development Kit 17:
apt install openjdk-17-jdk
3. priint:comet PDF Renderer (Native Libraries)
Ensure you have a folder containing all native libraries. The libs can be found at this GitLab repository (internal access only) or on the priint FTP Server in the folder https://webftp.priint.com/#/Comet_PDF/5.0/latest/. The Libs ("lib/native/linux") can be found together with a "config" folder in the archive "priint-renderer-pdf-linux-5.0-RXXXXX.tar.gz".
Copy the "lib" and the "config" folder as a sub folder of your Rendering Service Application.
A checklist of the required libraries is as follows:
- comet_pdf.1.so
- comet_pdf.2.so
- comet_pdf.3.so
- comet_pdf.4.so
- libboost_date_time.a
- libboost_date_time.so -> libboost_date_time.so.1.71.0
- libboost_date_time.so.1.71.0
- libboost_filesystem.a
- libboost_filesystem.so -> libboost_filesystem.so.1.71.0
- libboost_filesystem.so.1.71.0
- libboost_locale.a
- libboost_locale.so -> libboost_locale.so.1.71.0
- libboost_locale.so.1.71.0
- libboost_program_options.a
- libboost_program_options.so -> libboost_program_options.so.1.71.0
- libboost_program_options.so.1.71.0
- libboost_system.a
- libboost_system.so -> libboost_system.so.1.71.0
- libboost_system.so.1.71.0
- libboost_thread.a
- libboost_thread.so
- libboost_thread.so.1.71.0
- libicudata.so.66 -> libicudata.so.66.1
- libicudata.so.66.1
- libicui18n.so.66 -> libicui18n.so.66.1
- libicui18n.so.66.1
- libicuuc.so.66 -> libicuuc.so.66.1
- libicuuc.so.66.1
- libodbc.a
- libodbccr.a
- libodbccr.so -> libodbccr.so.2.0.0
- libodbccr.so.1 -> libodbccr.so.2
- libodbccr.so.2 -> libodbccr.so.2.0.0
- libodbccr.so.2.0.0
- libodbcinst.a
- libodbcinst.so -> libodbcinst.so.2.0.0
- libodbcinst.so.1 -> libodbcinst.so.2
- libodbcinst.so.2 -> libodbcinst.so.2.0.0
- libodbcinst.so.2.0.0
- libodbc.so -> libodbc.so.2.0.0
- libodbc.so.1 -> libodbc.so.2
- libodbc.so.2 -> libodbc.so.2.0.0
- libodbc.so.2.0.0
- libxl.so
4. Environment Variable
Set the LD_LIBRARY_PATH environment variable:
export LD_LIBRARY_PATH=/path/to/native/libs
Replace /path/to/native/libs with the actual path to the native libraries.
Make sure this variable survives a system reboot. Consider placing it in /etc/environment or ~/.profile.
5. Configuration Files
Adjust the logback.xml, worker config JSON, and rendering-service config YAML to your preferences. Detailed setup instructions are available in the HELP.md file shipped with the rendering-service jar or here.
6. License Folder
Ensure the license and configuration folder is present, holds the required pdf-profiles and is correctly referenced in the rendering-service configuration YAML. In particular, the PDF renderer licence should be placed in the config folder.
7. Rendering-Service.jar
Make sure you have the latest version of 4.6 rendering-service.jar.
8. Run the Rendering-Service
Start the rendering-service with the following command:
java -Dspring.config.additional-location=file:application.yml -Dworkers.config=pdf-workers-config.json -jar rendering-service.jar
Conclusion
Following these steps should get your rendering-service 4.6 with PDF renderer successfully running on Ubuntu 22.04.3 LTS. For additional support, refer to the documentation or reach out to the support team.