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>)))
Reporting And Analytics Aggregates
Also known as RAA. An optional Genesys Info Mart process that creates and populates predefined aggregation tables and views within an Info Mart database. RAA aggregation tables and views provide the metrics that summarize contact center activity to facilitate reporting, and serve as the primary source of data for the Genesys CX Insights (GCXI) and Genesys Interactive Insights (GI2) historical reports. RAA is required for Genesys CX Insights and GI2 environments.
How Do I Control Aggregation at Runtime?
In addition to the configuration options that you can set within the Genesys Info Mart Application object, you can also tailor how aggregation works by specifying certain runtime parameters when invoking the aggregation engine manually or from a batch or shell script.
Invoking Aggregation From the Command Line
Invoke the aggregation engine from the command line using this format:
- on UNIX platforms: java -jar agg/GIMAgg.jar -user=<dbo> -pass=<PASSWORD> -jdbcurl=<URL> <OTHERPARAMS>
- on Windows platforms: java.exe -jar agg\GIMAgg.jar -user=<dbo> -pass=<PASSWORD> -jdbcurl=<URL> <OTHERPARAMS>
where <OTHERPARAMS> are one or more of the following optional parameters:
Note that DATES_FROM:<FACT_TABLE> is supported in Release 8.5.003 and later. A hyphen (–) precedes each parameter, as shown in the preceding syntax. The options use camel case and are optional unless otherwise specified. Refer to the “Runtime Parameters” section below for a description of each parameter and its permissible values. Invoking aggregation is discussed further in the Reporting and Analytics Aggregates User’s Guide. Reporting and Analytics Aggregates (RAA) recognizes additional parameters that are reserved for use by the aggregation migration utility (which is described in the Genesys Migration Guide). These reserved parameters are for internal use only and are not described in the documentation.
RAA Aggregation Runtime Parameters
Most of the parameters listed in the table below are options that apply to aggregation in autonomous mode. However, when you invoke the following parameters, aggregation does not run, and the function associated with the parameter is performed instead:
You can invoke these parameters only one at a time; to invoke more than one, you must issue the aggregation command more than once.
|-agg-jdbc-url||Specifies the connection parameters for the JDBC connection to the Info Mart database for Reporting & Analytics Aggregates (RAA). More information: agg-jdbc-url|
|agg_level_<level>_delay||This parameter limits the frequency with which RAA performs aggregation. This parameter is available beginning with RAA release 8.5.001.45, and applies to materialized levels only (DAY and higher).
The value you specify represents a minimum period of time (in seconds) that must elapse between aggregation runs for data at a specified level, however, the actual time between aggregation runs is usually greater than the specified delay value. The exact time when aggregation occurs varies depending both on the time when the first aggregation run occurred, and on the Zone in which the data falls:
The time when aggregation occurs may also vary if the aggregation job is inserted using -insertPendingAgg.
For additional information refer to the description of the agg-level-<LEVEL>-delay option on the How Do I Configure Genesys Info Mart for Aggregation? page.
|conf||Specifies the file name from which the aggregation engine reads parameter values that are not specified at the command line. Precede this file with a relative path or absolute path, if the file is not located in the same directory as the aggregation jar archive. If this parameter or file is missing, the aggregation engine uses only those parameters that are issued at the command line—for example:
java -jar agg/GIMAgg.jar -conf runagg
|defaultTZoffsets||Specifies the winter and summer UTC offset, in seconds, of the time zone of the DATE_TIME table for environments whose offsets are in increments other than one hour—that is, whose offset is not evenly divisible by 3600, and that configure more than one time zone in aggregation.
For example: A time-zone offset of six and a half hours (UTC+06:30) with recognition of daylight saving time in the summer of one hour would be indicated as follows:
|deadlockThreshold||Specifies the time, in seconds, in which each aggregation writer thread must return the results of its aggregation of a batch of data. If a writer does not respond within this time frame, RAA assumes either that the process is deadlocked or that the database is too slow and cannot process aggregation in a timely fashion. When the deadlock time period has elapsed, RAA cancels all database queries and closes all sessions. To resume processing, aggregation must be restarted.
Refer to the description of the deadlock-threshold option (see What Options Can I Configure in the [agg] Section?) for additional information.
|delFeature=eServicesSM||Stops aggregation of social-media data.
To restart aggregation of social-media data, use the setFeature runtime parameter.
|delFeature=materialize-subhour-in-db||Instructs RAA not to materialize RAA subhour views as tables. To materialize the subhour level, see the setFeature=materialize-subhour-in-db option.|
|delFeature=excludeConsult||Includes consult interactions in ACC_* and ABN_* queue aggregates. To exclude consult interactions, see the setFeature=excludeConsult option.|
|getFeatures||Submits a request to display a list of the features currently enabled in the database.|
|insertPendingAgg||Submits a request to run the aggregation engine over the specified time period at some later time. The following formats are supported:
... -insertPendingAgg ALLSETS:2014-01-01:2014-12-31
Note that DATES_FROM:<FACT_TABLE> is supported in Release 8.5.003 and later.
Refer to the description in the Reporting and Analytics Aggregates User’s Guide for more information, and for information about performing re-aggregation.
|insertPendingAggRaw||Submits a request to run the aggregation engine over the specified time period at some later time. |
The following formats are supported:
-insertPendingAggRaw <TENANT>:<SET>:DATES_FROM:<FACT TABLE>
Note that DATES_FROM:<FACT_TABLE> is supported in Release 8.5.003 and later. Refer to the Reporting and Analytics Aggregates User’s Guide for examples of how to determine start-time and end-time keys.
|jdbcurl||Specifies the string that is sent to the JDBC driver to indicate the database that the Genesys Info Mart server is to use. Format this required parameter as follows:
For Microsoft SQL Server:
|levelOfLog||Specifies the detailed level of log messages that the GIM Server generates for aggregation-related activity. For example:
Refer to the description of the level-of-log option (see What Options Can I Configure in the [agg] Section?) for additional information.
|pass||The unencrypted password of the database owner. Format this required parameter as follows:
java -jar agg/GIMAgg.jar -user=Administrator -pass=$y5t3m
|printQuery||Displays or prints the SELECT statement of the specified aggregation query, based solely on its definition within internal RAA files.
java -jar ./agg/GIMAgg.jar -printQuery QUEUE_ACC_AGENT
java -jar ./agg/GIMAgg.jar -printQuery ALL> logfile.sql
The ALL argument is supported in Release 8.5.003 and later. In earlier releases, you must reissue the command for each desired SELECT statement. Because this parameter grabs the query’s definition entirely from internal files, it does not require that you specify database-connectivity parameters. Refer to the Reporting and Analytics Aggregates User’s Guide for the names of other RAA queries.
|realtimeOffset||Specifies the number of seconds that the upper boundary of Zone 1 is offset from aggregation. For example:
... -realtimeOffset 7200
Use this runtime parameter in conjunction with the realtimeOffset and writerSchedule parameters to fine-tune aggregation dispatching. Refer to the description of the realtime-offset configuration option (see What Options Can I Configure in the [agg] Section?) for the default and valid values of this parameter as well as an explanation as to why you should define a real-time offset.
|setFeature=eServicesSM||Maps IRF_USER_DATA_KEYS.GEN_ES_KEY to USER_DATA_KEY1 in the H_ID, H_AGENT, H_AGENT_GRP, and H_AGENT_QUEUE hierarchies, and turns on aggregation of the following social-media measures:
Not all of these measures exist in all of the aforementioned hierarchies. Refer to the Reporting and Analytics Aggregates Reference Manual for more information. To instruct RAA to cease aggregating social-media data, issue the delFeature runtime parameter.
|setFeature=excludeConsult||Excludes consult interactions in ACC_* and ABN_* queue aggregates, causing RAA to count only customer calls (thus mimicking release 8.1.1 behavior).|
|setFeature=materialize-subhour-in-db||Instructs RAA to materialize RAA subhour views as tables.|
|subHourInterval||Specifies the lowest time level of aggregation, in minutes, for the AG2_*_SUBHR tables. You must choose a value for this option at deployment and avoid changing it afterwards. The value for this parameter is either 15min or 30min—for example:
... -subHourInterval 15min
Refer to the description of the sub-hour-interval option (see What Options Can I Configure in the [agg] Section?) for additional information.
|updateAliases||Specifies the name of the file that defines which tenants map to which tenant accounts. Using tenant aliases enables automated maintenance of aliases in all configured tenant accounts. Precede this file by a relative path or, if the file is not located in the same directory as the aggregation jar archive, an absolute path.
The aggregation module only maintains those tables and views that are related to aggregation. You must run an alias update each time a tenant is added or removed from configuration or the definition of any of the aggregates changes—for example:
The Reporting and Analytics Aggregates User’s Guide describes how to format the alias mapping file.
|user||The account name of the database owner. Format this required parameter as follows:
java -jar agg/GIMAgg.jar -user=Administrator -pass=$y5t3m
|writerSchedule||Sets the schedule for the number of writers that RAA dedicates to the aggregation of notifications received in Zone 1 and Zone 2. The value for this parameter is a schedule of hours, without spaces, that defines writer assignments.
Refer to the description of the writer-schedule configuration option (see What Options Can I Configure in the [agg] Section?) for detailed information about the keywords available to you in order to define this parameter and for the definitions of Zone 1 and Zone 2.
This parameter also accepts the argument hour(#-#)=purge, which enables and schedules purging of aggregate data.
For information about configuring purging rules, see the Reporting and Analytics Aggregates User’s Guide. Prior to release 8.1.102, the number of writer threads dedicated to aggregation was controlled by the numberOfWriters configuration option.
|zoneOffset||Specifies the length of Zone 1 in seconds. This option also indirectly defines the boundary between Zone 2 and Zone 1.
Use this runtime parameter in conjunction with the realtimeOffset and writerSchedule parameters to fine-tune aggregation dispatching. Refer to the description of the zone-offset configuration option (see What Options Can I Configure in the [agg] Section?) for the default and valid values of this parameter as well as an explanation as to why you should define a zone offset.