Skip to main content

Questions before an Installation of priint:publishing server

Installation​

Installation packages can be downloaded via priint FTP server in folders priint\_suite\_4.x.x. In case you have no FTP account please contact support@priint.com. Before you download any packages for installation you should plan your task. Please have a close look to our checklist:

Typically, an installation of Adobe® InDesign® Server or PDF renderer precedes installation of publishing server.

Adobe® InDesign® Server with priint::comet​

priint:comet PDF Renderer​

priint:publishing server​

Linux​

Windows​

Installation Preparation Sheet​

This checklist contains requirements for installing publishing server (optionally with Adobe® InDesign® Server) and additional components in a Windows domain. It serves as a help for planning the installation. Additionally please check the sizing documentation. This requirements are meant for production, acceptance or test system on the customer side. Developer systems on single machines with no outside connectivity can omit some steps. Before an installation session the customer needs to prepare the systems. All requirements stated below have to be fulfilled respectively questions to be answered. Requirements in this document are indicated by a checkbox or a textfield. After filling out the form, export the PDF (Print to PDF) to keep it documented.

1.1 People Involved​

  • Who is responsible for the fulfillment of this requirements:
  • Who does the installation?
  • Which additional internal personnel will be involved (please inform them ahead of time)?
    • domain admin
    • database admin
    • network admin
  • Which external personnel will support installation and by which means (e.g. screen sharing via VPN tunnel)?
  • Access to installation machines is ensured: Participants (internal or external can access all systems by some remote administration tool access (typically RDP client) or attend via screen sharing.

1.2 Components​

The following components are to be installed

Databases for publishing server running on MySQL, Microsoft SQL Server, Oracle Database
publishing server on top of Payara Application Server 5
priint:BPM server Object Storage rendering service on top of Adobe® InDesign® Server (optional)
rendering service on top of Embedded PDF Renderer (optional)

Publishing server and database are mandatory. Rendering server is optional. For this checklist we assume that all components are needed.

1.3 Infrastructure Overview​

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

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 Application Server as a Windows Service?

username
password

2.2 File Server​

Images and documents read or managed by the servers have to reside in network location accessible for 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 such EPS or JPEG images, etc.?

UNC path

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

UNC path
All UNC path can be accessed (read/write) by the Application Server and Adobe® InDesign® Server users.

2.3 Databases​

Several databases must be installed.

Database NameDescription
PubServerKernelmandatory for publishing server
PublishingHubDBused for data import, planning data, etc.
comet_adminplanner administrative data
comet_dataplanner project related data
comet_importplanner import control data

Typically all databases need the same user. Storage requirements for PubServerKernel, comet_admin and comet_import are low. Storage requirements for PublishingHubDB and comet_data can vary between low and high depending 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

Database connection information:
Depending on RDBMS Type you will need:
Host: Port:
Instance / Service name (MSSQL, Oracle)

Which prefix for database names should be used to differentiate databases in a cluster?
prefix

Which database user should be used for accessing print suite databases?
username
password

Database user needs permissions to read, write and administer the specific databases. E.g. in SQL Server
db_owner
db_datareader
db_datawriter
db_ddladmin

DBA credentials For installation of databases database admin (DBA) credentials are necessary.
DBA can run the installation either

through installer wizard
manually by executing SQL script

2.4 publishing server​

Publishing server will run on top of Payara application server.

2.4.1 Hardware​

Server can be virtual or dedicated machine. Virtualization is recommended.

For detailed hardware specifications, please refer to the sizing documentation. Basic recommendations:

  • CPU: 4+ cores per 20 concurrent users or 5 parallel server jobs
  • RAM: 8+ GB plus 1 GB additional per 5 concurrent users or 2 server jobs

Hardware requirements reviewed and planned according to sizing documentation

What is the actually needed RAM? GB

2.4.2 Software​

The following basic installation is expected:

Windows 64bit Operating System
       Windows Server 2016
       Windows Server 2019
       Windows Server 2022
Linux Operating System
       Linux Ubuntu 20.04 LTS
       Linux Ubuntu 22.04.2 LTS
.NET 3.5 has to be activated (to run Payara as Windows Service)

During installation the following components will be added:

Java
Payara Application Server
Eclipse + priint:ison (Windows Only)
Publishing server applications (kernel and plugins) and their dependency libraries
Jackrabbit repository
Configurations and administration scripts and tools

2.4.3 Firewall​

The firewall must be configured to accept at least the following requests:

incoming to port 8080 (or 40080) (HTTP) (mandatory user access)

incoming to port 8181 (or 40081) (HTTPS) (mandatory user access)

incoming to 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​

Rendering service will run on top of Adobe® InDesign® Server. Adobe® InDesign® Server will be supplemented by comet server plug-ins.

Adobe® InDesign® Server can be used in single or multi-instance mode depending on its license.

Rendering service will run with Embedded PDF Renderer.

Note: For more information check the detailed installation guidelines.

2.5.1 Hardware (virtual or dedicated machine)​

Server can be virtual or dedicated machine. Virtualization is recommended.

For detailed hardware requirements, please refer to the sizing documentation. General recommendations:

  • CPU: Multicore processor with sufficient cores for Adobe® InDesign® Server instances
  • RAM: Base 8+ GB plus 2-4 GB per Adobe® InDesign® Server instance

Hardware requirements reviewed and planned according to sizing documentation

What is the actually needed RAM? GB

2.5.2 Software​

The following basic installation is expected:

Windows 64bit Operating System
       Windows Server 2016
       Windows Server 2019
       Windows Server 2022
macOS Operating System
       Mac OS X 10.13 or higher
Microsoft .NET Framework Version 2.0 or higher is required

During installation the following components will be added:

Adobe® InDesign® Server 2022 - 2024 (Server 2022 sub-version 17.2 is needed at least!)
      Number of instances:
priint comet server plug-ins for Adobe® InDesign® Server 2022 - 2024
Java 17 (must be installed for rendering worker service)

2.5.3 Firewall​

The firewall must be configured to accept at least the following requests:

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 for each instance. Typically they start with 4711 for the first instance and increment by one for each additional instance.

To keep things simple it is recommended to configure firewall for the application in general not on port level.

2.6 Network and Accessibility Requirements​

Publishing server, rendering service, database server and file server must be accessible among each other. For each machine please check that:

ports are accessible
certificates are valid (if SSL/TSL is used)
servers can be administered from remote
publishing server can be accessed via RDP
rendering service can be accessed via RDP

For bandwidth requirements please check sizing documentation.

2.7 Licenses​

The following licenses are required in case rendering service in combination with Adobe® InDesign® Server is used.

  • 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 for Adobe® InDesign® Server (License keys for publishing server, comet server plug-ins will be created during installation)

Before installation please check that:

licenses for Windows servers and database are valid
licenses for database client are valid - if needed
Adobe® InDesign® Server license has been acquired and key is available during installation
licenses for publishing server, comet server plug-ins have been covered by contract with priint Group

2.8 Remote Access​

If the servers have are intended to be managed by contracted partners these partners (i.e. their personnel) must be provided constant remote access on the target machine/s.

2.8.1 VPN Access​

Is VPN access necessary?
       which client (how is client provided)
       which certificate
       username:
       password:

2.8.2 RDP Access​

Is remote desktop access necessary?
domain and machine name or IP address
username:
password:

2.9 Ports Used in Publishing Server​

This table contains necessary port openings. Default open ports for Windows are not mentioned (RDP, File Share, etc.)

ServerPort (listening on) (in brackets typical developer machine)
rendering server (SOAP service)4711, 4712, 4713... (depending on number of instances)
publishing server (Payara http access)8080 (40080)
publishing server (Payara https access)8181 (40081)
publishing server (Payara web admin access)4848 (40048)
publishing server (Payara debugging)9009 (40009)