Jump to: navigation, search

Configuration Database Section

The Configuration Database section name is specified by the value of the server option. This section contains information about the Configuration Database. The options in this section can only be edited in the Configuration Server configuration file, not via an Application object's options.

dbengine

Default Value: No default value
Valid Values: oracle, mssql, db2, postgre
Changes Take Effect: After restart

Specifies the type of DBMS that handles the Configuration Database. You must specify a value for this option.

dbname

Default Value: No default value
Valid Values: Any valid database or DSN name
Changes Take Effect: After restart

Specifies the name of the Configuration Database to be accessed as specified in the DBMS that handles this database. You must specify a value for this option unless dbengine=oracle. For DB2, Microsoft SQL, and PostgreSQL, this value is the name of the database where the client will connect. For Windows Authentication using a Data Source Name (DSN) with an MS SQL database, set this option to the name of the DSN. Refer to the Windows Authentication with MS SQL Server section of the Framework Deployment Guide.

db-persistent-failover-tmout

Default Value: 60 seconds
Valid Values: Integer value in seconds
Changes Take Effect:

During persistent mode start, the Configuration Server Proxy tries a connection attempt with DBMS for up to db-persistent-failover-tmout period of time. This means that if within a configured period of time (-cs-persistent-failover-tmout), the Configuration Server Proxy is unable to connect to master Configuration Server, then the CS Proxy would alternatively try to connect to DBMS.

Again, if within a configured period of time (db-persistent-failover-tmout) the CS Proxy is unable to connect with DBMS, then the CS Proxy would alternatively try to connect to Master CS. It keep continuing until the connection with master/DBMS is successful.

Important
This option is applicable for Configuration Server Proxy.

dbserv-conn-async-timeout

Default Value: 20 Valid Values: 0–65535
Changes Take Effect: After restart

Specifies, in seconds, the time interval in which Configuration Server, when connecting to DB Server, waits for a response from DB Server if a TCP response has not been received because of a network issue. If this option is set to 0 (zero), this timeout is disabled.

dbserver

Default Value: No default value
Valid Values: Any valid DBMS name or dsn
Changes Take Effect: After restart

Specifies the name or alias identifying the DBMS that handles the Configuration Database, as follows:

  • For Oracle, the value is the name of the Listener service.
  • For Microsoft SQL, set this value to the SQL server name (usually the same as the host name of the computer on which the Microsoft SQL Server runs).
  • For DB2, set this value to the name or alias-name of the database specified in the db2 client configuration.
  • For PostgreSQL, set this value to the SQL server name (usually the same as the host name of the computer where PostgreSQL runs).

Set this option to dsn to trigger Configuration Server, in direct database access mode, to connect to the database using a Data Source Name (DSN) configured in the Windows operating system. The DSN name must be specified by the dbname option in this case. Refer to the Windows Authentication with MS SQL Server section of the Framework Deployment Guide.

dml-retry

Default Value: 1
Valid Values: Integer values in the range of 0 to 32766
Changes Take Effect: After restart of Configuration Server

Specifies the number of retries for issuing a DML statement or transaction to DB Server after receiving TAF range error from Oracle DBMS. When the number of retries has been attempted with no success, Configuration Server considers the database operation to have failed and reports the error to the database client. A value of zero (0) specifies that no retry is to be attempted, in which the error is reported to the client immediately, without any retries.

Important
The node failover procedure can be time- and resource-consuming, so take care to set this option to a reasonable value to avoid overloading DB Server.

mssql-multisubnet

Default Value: No
Valid Values: Yes, No
Changes Take Effect: After restart

Enables multi-subnet failover using MS SQL 2016 and later for disaster recovery and business continuity scenarios involving the Configuration Database. When set to Yes, subnet failover is supported; when set to No, subnet failover is not supported.

For more information about this feature, refer to the Framework Database Connectivity Guide.

password

Default Value: No default value
Valid Values: Any character string
Changes Take Effect: After restart

Specifies the password established in the SQL server to access the Configuration Database. You must specify a value for this option if you are not encrypting the password. If you are encrypting the password, Configuration Server sets this option to the encrypted password in its configuration file.

Important
The password option is visible only in the configuration file. It is not visible in Genesys Administrator.

response-timeout

Default Value: 600
Valid Values: Any positive integer
Changes Take Effect: After restart

Specifies the time interval, in seconds, Configuration Server waits for a response from the DBMS. If this timeout expires, Configuration Server generates log event 21-24402. Refer to Framework Combined Log Events Help for a full description of this log event.

username

Default Value: No default value
Valid Values: trusted or any valid username
Changes Take Effect: After restart

Specifies the user name established in the SQL server to access the Configuration Database.

If the Configuration Database is not an MS SQL database, or you are not using Windows authentication to access the Configuration Database, set this option to the name of a user account authorized to access the database.

If you are using Windows Authentication with a Data Name Source (DSN) to access an MS SQL Configuration Database, either do not set this value at all, or set it to a dummy value.

If you are using Windows Authentication with a Trusted User to access an MS SQL Configuration Database, set this option to trusted. The actual user account is based on the Configuration Server account for which the trusted user was configured. Refer to the Windows Authentication with MS SQL Server section of the Framework Deployment Guide.

This page was last edited on June 26, 2020, at 14:57.
Comments or questions about this documentation? Contact us for support!