dbserver
client_stop_timeout
Default Value: 30
Valid Values: 0 or any positive integer
Changes Take Effect: After restart
Specifies the interval, in seconds, that DB Server waits for a client to stop before DB Server terminates the DB client process.
connect_break_time
Default Value: 1200
Valid Values: Any positive integer
Changes Take Effect: After restart
Specifies a timeout, in seconds, after which DB Server closes a connection to a DB client if DB Server could not send a request to the client. Do not set this option too small; if a value of 1 to 10 seconds is set, for example, network delay might prevent a request delivery. Genesys recommends that you set this option to a value equal to or greater than 60.
db2_name
Default Value: ./dbclient_db2
Valid Values: Any valid name
Changes Take Effect: After restart
Specifies the name of the DB client process for the DB2 server. This option is required for DB2 databases.
dbprocess_name
Default Value:
Valid Values: dbclient_db2 For DB2
dbclient_informix For Informix
dbclient_msql For Microsoft SQL
dbclient_oracle For Oracle
dbclient_postgre For PostgreSQL
dbclient_sybase For Sybase
Changes Take Effect: After restart
Specifies the type of a DB client process. This option works with dbprocesses_per_client and with the appropriate database name option (oracle_name, for example).
Note: Only enable the dbprocess_name option for compatibility with previous releases of client applications (5.1, 6.0, or 6.1).
dbprocess_number
Default Value: 255
Valid Values: 0 Does not impose restrictions to the number of running DB Client processes
1 and above Sets maximum number of simultaneously running DB Client processes
Changes Take Effect: After restart
Sets the maximum limit for the number of simultaneously running DB Client processes.
dbprocesses_per_client
Default Value: 1
Valid Values: From 1 to 255
Changes Take Effect: After restart
Specifies the number of database client processes that DB Server&s main process creates for each client if a user client does not make an explicit request. This option prioritizes client access to the database. For example, if multiple processes per client are set, DB Server spawns another child process if needed. This effectively gives the client application more of the database’s processing time. See documentation for a particular client application to verify whether that application supports the Multiple Processes mode. If unsure of the appropriate number, set this option to 1. Increasing the value up to 4 increases performance; more than 4 does not increase performance.
Note: Genesys recommends using the default value (1) for the dbprocesses_per_client option unless instructed otherwise by Technical Support or by the User&s Guide of the applicable Genesys solution. Changing the default value (1) of this option may cause data loss.
force_host
Default Value: 0
Valid Values: 1, 0, false, true, on, off, yes, no, y, n
Changes Take Effect: After restart
When set to 1, specifies that DB Server connects to the dbclient through a host network that is configured in the host option in the [dbserver] section.
When set to 0 (the default), the connection is established through the local host.
informix_name
Default Value: ./dbclient_informix
Valid Values: Any valid name
Changes Take Effect: After restart
Specifies the name of the DB client process for the Informix server if present. This option is required for Informix databases.
management-port
Default Value: 4051
Valid Values: Any valid TCP/IP port
Changes Take Effect: After restart
Specifies the TCP/IP port DB Server reserves for connections established by its SNMP (Simple Network Management Protocol) Option Management Client.
msql_name
Default Value: ./dbclient_mssql
Valid Values: Any valid name
Changes Take Effect: After restart
Specifies the name of the DB client process for the Microsoft SQL server. This option is required for MSSQL databases.
oracle_name
Default Value: ./dbclient_oracle
Valid Values: Any valid name
Changes Take Effect: After restart
Specifies the name of the DB client process for the Oracle server if present. This option is required for Oracle databases.
postgre_name
Default Value: ./dbclient_postgre
Valid Values: Any valid name
Changes Take Effect: After restart
Specifies the name of the DB client process for the PostgreSQL server if present. This option is required for PostgreSQL databases.
stored_proc_result_table
Default Value:
Valid Values: Any valid table name
Changes Take Effect: After restart
Used by earlier versions of DB Server that did not directly retrieve output data from stored procedures. This option specifies the name of a table that you design, to which a stored procedure that you have created writes output data (the maximum allowed size of an output parameter from a stored procedure is 2000 B). DB Server then retrieves the data stored in the specified table and sends it to the user application. Using a result table can slow down DB Server, because each stored procedure call causes an additional select statement.
sybase_name
Default Value: ./dbclient_sybase
Valid Values: Any valid name
Changes Take Effect: After restart
Specifies the name of the DB client process for the Sybase server if present.This option is required for Sybase databases.
tran_batch_mode
Default Value: off
Valid Values: on, off
Changes Take Effect: After restart
Valid only for Microsoft SQL and Sybase databases. If set to on, DB Server executes all transactions as SQL batches, which increases performance for insert and update statements.
Note: Genesys recommends using the default value (off) for the tran_batch_mode option unless instructed otherwise by Technical Support.
verbose
Default Value: 3
Valid Values: 0 DB Server writes no debug messages.
1 DB Server writes errors and SQL statements.
2 DB Server writes information about all messages it has received and sent.
3 DB Server writes debug messages at the most detailed level.
Changes Take Effect: After restart
Sets the level of detail with which DB Server writes the debug messages. The option is configured in the dbserver section and is enabled only when the verbose option in the log section is set to either all or debug. DB Server writes the debug messages to a log output specified for the all and/or debug logoutput options.