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

Common settings

• Login credentials for YSoft SafeQ 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:

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

• The database should be in Snapshot Isolation level

• The user that YSoft SafeQ 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 YSoft SafeQ:

  • when installing with SQL account, db_owner and securityadmin server role are required. In case you will let YSoft SafeQ create a database following permission is required: CREATE ANY DATABASE.

  • 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 YSoft SafeQ databases (its username and password should be specified during installation for DB connection)

      • account has administrative rights and "Log on as a service" at YSoft SafeQ server (install package must be launched under this account by "run as"; YSoft SafeQ 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 YSoft SafeQ the required rights are the same as for installation, except that CREATE ANY DATABASE permission is not needed.

• To run YSoft SafeQ 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 YSoft 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 YSoft SafeQ 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.

• For domain users authentication refer to Installing YSoft SafeQ Management Server on external MSSQL using domain users.

• For AlwaysOn Availability group configuration refer to Installing YSoft SafeQ Management Server on MSSQL AlwaysOn Availability group.

PostgreSQL configuration

• UTF-8 collation

• Version 11 only

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

• To install, update or run the YSoft SafeQ 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.

Database users

• Main database system user – required by YSoft SafeQ 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 YSoft SafeQ Management Service, YSoft SafeQ Payment System, and YSoft SafeQ 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 YSoft SafeQ installation. The database user is required by YSoft SafeQ 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 YSoft SafeQ installation. The database user is required by YSoft SafeQ Management Service.

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