PostgreSQL Databases
Contents
You must make PostgreSQL client software accessible in the environment where the Genesys application is running. Genesys uses PostgreSQL 9.0 client software to access all supported versions of PostgreSQL.
Using PostgreSQL Client Software
The vendor client software must be in the folder specified in the environment variable PATH (for Windows), LIBPATH (for AIX), or LD_LIBRARY_PATH (for Linux and Solaris). Refer to PostgreSQL documentation for more information.
The following is an example of the configuration of Genesys Database Access Point parameters for PostgreSQL:
dbengine=postgre
dbserver=<postgresql server host>
dbname=<database name>
username=<user name>
password=<password>Connectivity to PostgreSQL relies on TCP/IP between server and client. PostgreSQL client software uses Operating System settings for the TCP/IP stack to determine how long to wait for a response form the PostgreSQL server after submitting a request to it. For example, on Linux it may take up to 2 hours to detect a disconnection, unless the Operating System parameter tcp_keepalive_time is adjusted. Refer to documentation for your operating system for more information.
When using PostgreSQL 9.X server, make sure the following parameters are set in the postgresql.conf file, as follows:
bytea_output =’escape’
standard_conforming_strings=’off’PostgreSQL Strings
Prior to PostgreSQL version 9.1, backslash characters in strings were treated as escape characters, and Configuration Server does the same, by default. In PostgreSQL 9.1 and later, backslashes are treated as ordinary characters. How PostgreSQL handles backslashes in strings is specified by the PostgreSQL configuration option standard_conforming_strings in the postgresql.conf file, in which a value of off indicates the backslashes are treated as escape characters, to provide backward-compatible behavior.
Normally, the PostgreSQL option is set to false, and no action is required. However, if the PostgreSQL option is set to true, meaning that backslashes in strings are treated as ordinary characters, enable the Configuration Server option postgre-standard-conforming-strings to force Configuration Server to do the same.
For more information about the Configuration Server option postgre-standard-conforming-strings, refer to the Framework 8.5 Configuration Options Reference Manual.
Using PostgreSQL Databases with National Languages
Single Language Deployment
You must create all PostgreSQL databases using the same character set, for example WIN1252. You must select encoding that matches Microsoft Windows Operating System default encoding for the selected language so applications, like Interaction Routing Designer, display data correctly.
On every host that has Genesys applications accessing PostgreSQL databases, make sure that the language and encoding environment variable (or the settings for non-Unicode applications, if you are using Windows) is set to match character encoding of data in the PostgreSQL database. If there is a discrepancy between the encoding that the database and the local client are using, set the environment variable PGCLIENTENCODING on the host where the client software is running to match the database (for example, PGCLIENTENCODING=Win1252), based on the following table:
With the environment set up this way, you can use character data in a single language (such as French) for all information stored and transmitted between Genesys applications.
Multiple Languages Deployment
To enable storage and processing of data in multiple languages using a PostgreSQL database, you must create all your database instances using the UTF8 character set.