Supported server operating systems

Supported Languages (Print Management)

User Interface

External and Embedded Terminals: See Configuring supported languages in Embedded Terminal.

*Some of the languages are supported only for some vendor-specific Embedded Terminals.

Admin Interface

Chinese (simplified), Czech, Danish, Dutch, English, French, German, Hungarian, Italian, Japanese, Polish, Portuguese (Brazil), Portuguese (Portuguese), Romanian, Russian, Slovak, Spanish, Turkish

Supported Databases

System Requirements

• .NET Framework 4.8 or newer

• GhostScript (version 9.0 or higher) for proper PostScript analysis. For details, see Print language support and limitations.

• No other software that may interfere with the product installed on the servers, especially databases (unless intended for this installation), or other print solutions.

• IIS 7.0 or higher is required in order to use IIS Hostable Web Core (HWC) as a web server. (Terminal Server implements embedded web server based on IIS Hostable Web Core functionality. HWC web server is suitable even for environments with large number of devices connecting to one node. It provides necessary performance and stability.)

Database Sizing

Example based on real customer data (10 million pages per month):

• Management database: 16 GB per Dispatcher Paragon server

Database Settings and Configuration

Dispatcher Paragon provides automated database maintenance tools. Scheduled database maintenance is strongly recommended. The following configuration is required for different database types.

Common settings

• Login credentials for Dispatcher Paragon access, with ownership rights to its database

• Collation case-insensitive

• Reliable low-latency network connection (if the database server is on another server)

Microsoft SQL Server configuration:

• Server certificate with a matching FQDN with the hostname of the server

  • The certificate needs to be added to the MSSQL network configuration. To do that, open SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for MSSQLSERVER → Properties → in the Flags tab, set encryption to Yes and in the Certificate tab, the certificate should be visible in the dropdown menu.

  • An example of generating a certificate with the MakeCert tool:

    C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64> .\MakeCert.exe -r -pe -n "CN=<fqdn>" -b <before> -e <after> -eku 1.3.6.1.5.5.7.3.1 -ss <store_name> -sr localMachine -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12

• Correct collation: Case-Insensitive and Accent-Sensitive (language_CI_AS) where applicable

• The database should be in Snapshot Isolation level

• The user that Dispatcher Paragon uses to connect to the databases must have the default language set to English (but not British English) in the SQL Server

• Enabled TCP/IP connection or named pipes

• Enable Simple recovery model

• To install Dispatcher Paragon:

  • when installing with SQL account:

    • you can allow the installer to create the databases, this requires that account used for DB connection has server roles: public, securityadmin, dbcreator, sysadmin

    • you can create databases SQDB6, SQDB6_IMS, SQDB6_YPS, SQDB6_DWH in advance, this requires that account used for DB connection is mapped to them as db_owner and at the same time it has server roles: public, securityadmin

  • when installing with domain user credentials or when "AlwaysOn Availability group" is used:

    • Enable Contained Databases is set to True at the database server

    • Databases SQDB6, SQDB6_IMS, SQDB6_YPS, SQDB6_DWH are created in advance, CONTAINMENT is set to PARTIAL

    • A single domain user service account is available with the following rights:

      • account has db_owner rights for Dispatcher Paragon databases (its username and password should be specified during installation for DB connection)

      • account has administrative rights and "Log on as a service" at Dispatcher Paragon server (install package must be launched under this account by "run as"; Dispatcher Paragon services will be running under it once the installation finishes)

      • account is different from the account creating the databases but belongs to the same domain

      • account is not a sysadmin (SQL query "select CURRENT_USER" on master DB returns "guest", not "dbo")

• To update/upgrade Dispatcher Paragon the required rights are the same as for installation, except that CREATE ANY DATABASE permission is not needed.

• To run Dispatcher Paragon the following database roles are required:
  db_datareader, db_datawriter, db_ddladmin, db_accessadmin, db_securityadmin (or all can be replaced by db_owner).

• In case you are going to use the external MS SQL server with named instance, you will need the following to be allowed between the Dispatcher Paragon server and MS SQL server:

  • UDP, both directions, local port on MS SQL server is 1434. This communication is used to query the SQL server (its SQL Browser service). The SQL Browser service will respond and inform the requester about the port it shall connect to via TCP.

  • TCP communication, direction from SAFEQ to SQL, port "random". The port number is dynamically assigned by the SQL Browser service (http://technet.microsoft.com/en-us/library/cc646023.aspx).

• For SSL communication refer to Configuring MS SQL for SSL/TLS.

• If you need a specific database collation, refer to Installing Dispatcher Paragon Management Server on server with specific database collation for MS-SQL database.

• In the case of standalone data warehouse database deployment, refer to First server installation with standalone data warehouse database.

PostgreSQL configuration

• UTF-8 collation

• Version 18 (Embedded or External)

• Non-local-admin account for running PostgreSQL system service (Windows OS)

• To install, update or run the Dispatcher Paragon Management Server database user must have a super admin role.

• Database server timezone should be correctly configured: Configuring the PostgreSQL Time Zone for Correct Print Job and Report Data.

• In the case of standalone data warehouse database deployment, refer to Configuring PostgreSQL for remote database connection.

Host-based authentication (pg_hba.conf)

Dispatcher Paragon requires PostgreSQL to use password authentication (scram-sha-256, recommended on PostgreSQL 18, or the legacy md5) — not trust / peer / ident — for every address Dispatcher Paragon connects from, including loopback (127.0.0.1/32, ::1/128). Configure this in pg_hba.conf on every PostgreSQL server hosting the SQ and/or DWH database.

Broad form (simplest; restrict who can reach the port via the network/firewall):

Hardened form (scope to known Dispatcher Paragon node, DWH, and loopback addresses):

After editing, apply with SELECT pg_reload_conf();.

Notes:

• pg_hba.conf is matched top-to-bottom, first match wins — make sure no trust loopback line precedes and shadows your password line.

• listen_addresses must include the interfaces the nodes/DBLink use (the embedded installer sets listen_addresses = '*').

• If you previously used PostgreSQL version 13 or earlier, your passwords are likely stored as an md5. In that case, you will need to use the md5 method instead of scram-sha-256.

Database users

• Main database system user – required by Dispatcher Paragon installation. We usually use sa for MSSQL with role db_owner, security admin, and CREATE ANY DATABASE. We usually use Postgres for PGSQL with a super admin role. The database user is required by Dispatcher Paragon Management Service, Dispatcher Paragon Payment System, and Dispatcher Paragon Infrastructure Service. With a single-tenant license and for standard system run (not for installation and not for update) we require for MSSQL role db_owner and security admin.

• Cluster management database user – usually cluster_mngmt. User is created by Dispatcher Paragon installation. The database user is required by Dispatcher Paragon Management Service. For MSSQL is db_owner role required. For PGSQL a super admin role is required.

• Hibernate database user – usually cluster_guest. User is created by Dispatcher Paragon installation. The database user is required by Dispatcher Paragon Management Service.

• Tenant database users – usually tenantuser_1 and dwhtenantuser_1. Users are created by Dispatcher Paragon installation or Dispatcher Paragon Management Service. Database users are required by Dispatcher Paragon Management Service. A new couple of database users tenantuser_n and dwhtenantuser_n is created by Dispatcher Paragon Management Service For each new tenant "n".