Skip to main content

Installation

publishing-server​

Data is the alpha and omega of marketing. Its not only vital for addressing target groups, but for automating marketing processes for both digital and offline media. The prerequisite for automation is the provision of data. Too often, product information is provided and revised repeatedly during the creation of marketing materials without referring back to the relevant data that’s being utilized throughout the organization, often leading to unsatisfactory quality, inconsistencies and substantial additional costs. The priint:hub connects the company’s existing data sources to the marketing process, eliminating the headache’s of error-prone and time-consuming additional work.

The priint:suite connects your content with the publishing process and generates automated print products, OnDemand publishing and Digital publishing.

A consumer encounters a multitude of “touchpoints“ on their customer journey. Around 20% of these are related to print and publishing. 20%! For this reason alone, these touchpoints remain essential components of a successful customer journey.

The modularity of the priint:suite allows the components to be used individually or collectively; enabling the users publishing platform to be successively built to meet their specific needs and requirements. This offers unique scaling possibilities.

priint-bpm​

priint-bpm is a business process management system for priint:suite 4. It is an application built around the embedded Camunda 7 BPMS. It adds functionalities providing some standard process definitions, Publishing Server integration and some standard delegates. It runs with JDK 17 and can be deployed on a machine separate from other priint applications.

Rendering-service​

The rendering-service (also sometimes referred to as the Rendering Worker Service) is an application providing worker threads for handling Camunda tasks that ships with priint:suite 4 - Publishing Server.

It requires one of the rendering-servers (the Adobe InDesign Server® or priint:pdf renderer) to fulfill its tasks.

The rendering-service creates a so-called worker (or worker thread) for each rendering-server instance it cooperates with. It subscribes to Camunda topics acquiring tasks as they appear and sending commands to the rendering-server instance a worker thread is assigned to.

There are a few things worth keeping in mind when installing and configuring that service.

  • The rendering-service requires JDK 17 to run.
  • Each configured worker should be connected to its own, separate rendering-server instance.
  • You can configure any number of Adobe InDesign Server® workers within a single rendering-service instance, but only up to 4 priint:pdf renderer workers per rendering-service instance.
  • You can start more than one rendering-service instance for fault tolerance and load distribution, but the rendering-server instances workers in each rendering-service instance connect to need to be separate, unique ones.
  • Adobe InDesign Server® workers are lightweight as most of the work-intensive processing is done on a separate Adobe InDesign Server® instance. 2GB heap is more than enough for an instance hosting 20 such worker threads. Note however that for priint:pdf renderer workers the heavy lifting is done within the rendering-service process, so reserve more RAM in that setup.
  • It is worth putting the rendering-service instance on a separate pod/VM/machine so that it does not compete for resources with other applications.
  • This application easily scales horizontally, especially with priint:pdf renderer workers. It is a good candidate for setting up autoscaling based on actual load.