Use this configuration section to set Genesys Info Mart / RAA–related options on database access points (DAPs) that Genesys Info Mart uses:
- The extraction DAPs, which enable access to the databases from which Genesys Info Mart extracts data.
- The Info Mart DAP, which enables access to the Info Mart database, in which Genesys Info Mart stores reporting data.
You can configure Info Mart database access point (DAP) application options that pertain to aggregation. The section must be named [gim-etl].
Default Value: No default value
Valid Values: Any valid JDBC URL
Changes Take Effect: On restart of the Genesys Info Mart Server.
In an Oracle RAC configuration in which you want aggregation to use a separate node, specifies the connection parameters for the JDBC connection to the Info Mart database for Reporting & Analytics Aggregates (RAA). If this option is defined, the aggregation process uses the connection string specified by agg-jdbc-url instead of the jdbc-url connection string. For the required syntax for this option, consult the vendor documentation for your JDBC driver.
For performance reasons, Genesys recommends that you divide processing by function, allocating separate functions to specific nodes in the cluster. Use the Oracle RAC Server Control Utility (SRVCTL) to configure named services, including a named service for RAA, and associate those services with particular nodes. For more information, see Oracle RAC Configuration and DAP Objects for Genesys Info Mart in the Genesys Info Mart 8.x chapter in the Genesys Hardware Sizing Guide.
Example for Oracle
Oracle requires the following format to specify connection parameters for the Oracle thin client:
jdbc:oracle:thin:@(DESCRIPTION = (LOAD_BALANCE=OFF)(ADDRESS = (PROTOCOL = TCP)(HOST = <database_host_name>)(PORT = 1521))(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME=<named service>)))
To enable SSL or IPv6 over the JDBC connection, you must specify additional parameters, as described in your RDBMS vendor documentation. For an indication of the additional parameters you must provide, extrapolate from the examples shown in the Notes in the jdbc-url option description.