User Interface

Dispatcher Paragon Client: Catalan, Chinese (simplified/traditional), Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Indonesian, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Malaysian, Norwegian, Polish, Portuguese (Brazil/Portuguese), Romanian, Russian, Serbian (Latin/Cyrillic), Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian.

External and Embedded Terminals: Arabic, Bulgarian, Catalan, Chinese (simplified/traditional), Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Indonesian, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Malaysian, Norwegian, Polish, Portuguese (Brazil/Portuguese), Romanian, Russian, Serbian (Latin/Cyrillic), Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian.

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

Admin Interface

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

Common settings

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

• Collation case-insensitive

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

Microsoft SQL Server configuration:

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

• 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 the following database role is required: db_owner and following server role is required: securityadmin. In case you will let Dispatcher Paragon create a database following permission is required: CREATE ANY DATABASE.

• To update/upgrade Dispatcher Paragon the following database role is required: db_owner and following server role is required: securityadmin.

• To run Dispatcher Paragon the following database roles are required: db_datareader, db_datawriter, db_ddladmin, db_accessadmin, db_securityadmin, and following server role is required: securityadmin.

• In case that you are going to use the external MS SQL server with named instance, you will need following to be allowed between SafeQ 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 case of standalone data warehouse database deployment, refer to Configuring MS SQL for Server link

PostgreSQL configuration

• UTF-8 collation

• 9.4 version only

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

• To install, update or run Dispatcher Paragon Management Server database user must have superadmin role.

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

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

Database users

• Main database system user, user is required by Dispatcher Paragon installation. We usually use sa for MSSQL with role db_owner, securityadmin and CREATE ANY DATABASE. We usually use postgers for PGSQL with superadmin role. Database user is required by Dispatcher Paragon Management Service, Dispatcher Paragon Payment System and Dispatcher Paragon Infrastructure Service. With single tenant licence and for standard system run (not for installation and not for update) we require for MSSQL role db_owner and securityadmin.

• Cluster management database user, usually cluster_mngmt. User is created by Dispatcher Paragon installation. Database user is required by Dispatcher Paragon Management Service. For MSSQL is db_owner role required. For PGSQL is superadmin role required.

• Hibernate database user, usually cluster_guest. User is created by Dispatcher Paragon installation. 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. For each new tenant n is created new couple of database users tenantuser_n and dwhtenantuser_n by Dispatcher Paragon Management Service.