Questions before an Installation of priint:publishing server

Installation

Installation packages can be downloaded via priint FTP server. In case you have no FTP account please contact support@priint.com.

• priint_suite_4.x.x — Windows installer and add-on packages (optional modules)
• priint_suite_4.x.x_Linux — Linux installer packages

Note: Add-on zips for optional modules (Data Manager, Web to Publish, etc.) are found in the folder without the _Linux suffix. Before you download any packages for installation you should check which modules you need.

Please have a close look at our checklist:

Recommended Installation Order

Install and configure the following components in this order:

1. Object Storage — prepare your object storage solution before installing Publishing Server
2. Publishing Server (including Database)
3. priint:bpm
4. Adobe® InDesign® Server with priint:comet plugins — or priint:comet PDF Renderer (optional, if server rendering is needed)
5. Rendering Service (worker connecting IDS or PDF Renderer to Publishing Server)
6. Data Manager, Web to Publish (optional modules, configured after Publishing Server is running)

Reverse Proxy Recommendation

It is strongly recommended to run priint:suite behind a reverse proxy. This improves security, enables clean HTTPS termination, and hides the Payara application server from the internet. Set up the reverse proxy after Publishing Server is installed. See Best Practice: priint:suite behind an Apache Reverse Proxy

Object Storage

Before installing the Publishing Server, prepare your object storage solution. The Publishing Server requires an S3-compatible object storage service. Bring your own provider. The priint:suite does not bundle one. Known working providers include Google Cloud Storage and MinIO. Other S3-compatible services may work but have not been tested by priint Group. The guides below use MinIO as an example setup.

Linux

• Example: MinIO setup on Linux

Windows

• Example: MinIO setup on Windows

priint:publishing server

Linux

• Quick Installation Guide

Windows

• Quick Installation Guide
• Additional Installation Options

priint:bpm

Linux

• priint:bpm on Linux

Windows

• priint:bpm on Windows

Adobe® InDesign® Server with priint::comet

• Installation of Adobe InDesign® Server
• Overview Adobe InDesign® Server priint:comet Plugins
• Adobe InDesign Server Integration Overview

priint:comet PDF Renderer

• Overview priint:comet PDF Renderer
• Configuration of Embedded PDF Renderer
• Configuration of Containerized PDF Renderer

Rendering Service

Linux

• Rendering Service on Linux

Windows

• Rendering Service on Windows

Data Manager, Web to Publish

Data Manager and Web to Publish are optional standalone modules, not deployed to Payara. Each runs as a self-contained JAR and must be registered in your reverse proxy and authentication service after the core installation.

After Installation: Integration and Configuration

Installation gets each component running on its target operating system. What comes next is integration and configuration, covered in a separate section.

Integration is not OS-specific. It documents how components connect to each other and what must be configured on a project-by-project basis. This includes advanced object storage configuration, rendering service setup, priint:bpm default processes, connectors, and the Data Manager and Web to Publish modules.

See Integration

Installation Preparation Sheet

Review the sizing documentation before filling this out. All hardware requirements are documented there.

This checklist captures the decisions, credentials, and access details needed for the installation session. Requirements in this document are indicated by a checkbox or a text field. After filling out the form, export the PDF (Print to PDF) to keep it documented.

Production, acceptance, and test systems must fulfill all requirements. Developer systems on single machines with no outside connectivity can omit some steps.

tip

Check our DTAP (DEV, TEST, ACCEPTANCE, PROD) guideline for guidance on setting up our recommended environments.

1.1 People Involved

• Who is responsible for fulfilling these requirements:
• Who does the installation?
• Additional internal personnel involved:
  • domain admin
  • database admin
  • network admin
• External personnel and means of access (e.g. screen sharing via VPN):
• Remote access to all installation machines is confirmed

1.2 Components

Databases for publishing server (MySQL, Microsoft SQL Server, or Oracle Database)
Publishing server on top of Payara Application Server
priint:bpm server
Object Storage
Rendering service on top of Adobe® InDesign® Server (optional)
Rendering service on top of Embedded PDF Renderer (optional)
Data Manager (optional)
Web to Publish (optional)

Publishing server, object storage, and database are mandatory. All other components are optional.

1.3 Infrastructure Overview

The typical infrastructure contains several machines (virtual or physical): one running the application server, priint:bpm, and object storage; a second running the rendering server. Together with an existing file server and database server they serve the client.

Planned RAM per server (refer to sizing documentation):

Server	Planned RAM (GB)
Publishing server
Rendering server
priint:bpm server

2 Domain Resources

2.1 User

Which (domain) user should be used for running Adobe® InDesign® Server as a Windows Service? This user must have read/write access to media data and comet environment via UNC.

username
password

Which (domain) user should be used for running the Application Server as a Windows Service?

username
password

2.2 File Server

Images and documents read or managed by the servers must reside in a network location accessible to all components. This can be a dedicated file server or the publishing server (default) or rendering server.

Where are media data located that will be used by Adobe® InDesign® Server (EPS, JPEG, etc.)?

UNC path

Which location will be used for priint:comet cache and metadata files?

UNC path
All UNC paths are accessible (read/write) by the Application Server and Adobe® InDesign® Server users.

2.3 Databases

Database Name	Description
PubServerKernel	mandatory for publishing server
PublishingHubDB	used for data import, planning data, etc.
comet_admin	planner administrative data
comet_data	planner project related data
priint_bpm	priint BPM workflow engine related data

Storage requirements for PubServerKernel, comet_admin are low. The database comet_import is no longer actively used. Storage for PublishingHubDB and comet_data depends on the project.

Which database server will be used?

MySQL 8
Microsoft SQL Server 2016
Microsoft SQL Server 2019
Oracle 11g
Oracle 12c
Oracle 19c
Oracle 21c
Oracle 23c

Connection information: Host: Port:
Instance / Service name (MSSQL, Oracle)

Database name prefix (to differentiate databases in a cluster): prefix

Database user: username
password

User needs the following permissions (e.g. in SQL Server): db_owner
db_datareader
db_datawriter
db_ddladmin

DBA credentials are required for database installation. DBA will run installation: through installer wizard
manually by executing SQL script

2.4 Publishing Server

Which operating system?

Windows Server 2016 / 2019 / 2022
Linux Ubuntu 22.04 LTS / 24.04 LTS

Firewall — the following ports must be open:

incoming port 8080 or 40080 (HTTP, mandatory user access)
incoming port 8181 or 40081 (HTTPS, mandatory user access)
incoming port 4848 or 40048 (HTTPS, optional remote web administration)
outgoing to database server
outgoing to rendering server
outgoing to file server containing media data

2.5 Rendering Service

Which renderer?

Adobe® InDesign® Server with priint:comet plugins — number of instances:
Embedded PDF Renderer

Which operating system?

Windows Server 2016 / 2019 / 2022
macOS 10.13 or higher
Linux Ubuntu 22.04 / 24.04 LTS (Rendering Worker only)

Firewall:

incoming and outgoing to publishing server
outgoing to file server containing media data
outgoing to file server containing comet environment files

Ports of Adobe® InDesign® Server are configurable per instance. Typically starting at 4711, incrementing by one per additional instance.

2.6 priint:bpm

Which operating system?

Windows Server 2016 / 2019 / 2022
Linux Ubuntu 22.04 LTS / 24.04 LTS
Java 21 installed (required if priint:bpm runs on a separate machine from Publishing Server)

2.7 Object Storage

Storage provider chosen
Endpoint URL confirmed:
Accessible from Publishing Server
Access credentials (key / secret) available for configuration

2.8 Reverse Proxy

Reverse proxy server available
SSL certificate available (certificate file + private key)
Domain name confirmed:

2.9 Network and Accessibility

All servers must be accessible among each other. Confirm for each machine:

All required ports are open between servers
SSL/TLS certificates are valid (if used)
All servers can be administered remotely
Publishing server accessible via RDP or SSH
Rendering server accessible via RDP or SSH

2.10 Licenses

The following licenses are required when using the rendering service with Adobe® InDesign® Server:

• Windows Server license for publishing server
• Windows Server license for Adobe® InDesign® Server
• If using MSSQL: Database Client License for publishing server
• Adobe® InDesign® Server license
• comet server plug-in license (keys created during installation)

Licenses for Windows servers and database are valid
License for database client is valid (if needed)
Adobe® InDesign® Server license acquired and key available
Licenses for publishing server and comet server plug-ins covered by contract with priint Group

2.11 Remote Access

If servers are managed by contracted partners, those partners must have constant remote access to all target machines.

2.11.1 VPN Access

VPN access required
       client software available
       certificate available
       username:
       password:

2.11.2 RDP / SSH Access

Remote access confirmed for all servers
domain and machine name or IP address documented
username:
password:

2.12 Ports Reference

Server	Port
Rendering server (SOAP service)	4711, 4712, 4713... (depending on instances)
Publishing server (Payara HTTP)	8080 (40080)
Publishing server (Payara HTTPS)	8181 (40081)
Publishing server (Payara admin)	4848 (40048)
Publishing server (Payara debug)	9009 (40009)