Statistics Adapter Service

The Statistics Adapter Service  processes the statistical data created by the Aggregate Stats ETL job and writes stat-types and filters in the configuration for Genesys Stat Server. CCPulse+ requests iWD statistics from Stat Server, and reads the stat-types and filters from the Stat Server configuration.

In addition to the options described in Service Details, the following properties are configurable for the Statistics Adapter:

startAutomatically

Indicates whether the service should be started automatically after the configuration deployment.

logLevel

The Service log level. This should be set to Default unless otherwise instructed by Genesys Technical Support. See "Service Log Levels" for a description of each log level.  Depending on the setting of this property, additional logging properties might be available. Refer to "Logging Service" for descriptions of these common properties.

triggerMode

How the ETL job is triggered (started):

  • Trigger using CRON expression: Starts a job automatically, based on a CRON scheduling expression.

  • Trigger after another scheduled service: Starts a job automatically after another scheduled job has finished.

  • Trigger manually: Job can be started manually on the Services Status screen.

triggerMode and startAutomatically

The startAutomatically property controls whether the service is started at all. If it is unchecked, the service will not start on any of these trigger events.

You can still start the service manually from the Services Status screen. In that case, the particular service is in a wait state. It will wait for the trigger event to happen in order to start.

Notes: If the triggerMode is set to Trigger manually and startAutomatically is unchecked, after deployment when you start the service it will be started but it will wait for a manual trigger. So, you will need to start it again so it can perform its tasks.

If startAutomatically is checked and the triggerMode is set to Trigger using CRON expression, the service will start according to the CRON expression.

cronExpression

Standard CRON scheduling expression when triggerMode is set to Trigger using CRON expression.

For example, the following expression will cause the job to be executed every 15 minutes:

 "0,15,30,45 * * * ?".

For more information about CRON scheduling, see
http://www.quartz-scheduler.org/docs/tutorials/crontrigger.html

executionQueueName

The execution queue is configured only for jobs that are triggered with a cron expression or triggered manually.

For chained jobs (Trigger after another scheduled service), the execution queue automatically assumes the value of the parent job. For example, if you have Load Intraday chained to Load Config and Aggregate Intraday chained to Load Intraday, Load Config will never start while Aggregate Intraday is still running.

Scheduled services that have the same executionQueueName will never be run in parallel within the same solution.

If a scheduled service is triggered while another scheduled service that has the same executionQueueName is in progress, it is queued until the other service has completed its processing.

Note: This only works within the boundaries of a single runtime node. If you have services on different nodes, this will have no effect across the nodes.

dimensionMapping

Defines how statistical dimensions are mapped.

Filter: Dimensions are mapped to CCPulse+ filters.

Virtual Queue: Dimensions are mapped to Genesys virtual queues.

datamartDatabase

A reference to the Database Service that points to the iWD Data Mart database.

virtualQueueName

Name of the Genesys virtual queue to which statistics are distributed.

configurationServerConnector

Mandatory dependency:

The Configuration Server Connector Service; provides access to Configuration Server.

CMETenantName

The name of the (Genesys Configuration Server) tenant in which the Stat Server application is defined.

statServerName

The  name of the Stat Server application.

serviceIndex

Statistical service index for configuration options. This should be unique inside the set of indexes, assigned to statistical services served by the one instance of Genesys Stat Server.

extensionSectionName

Required to support a Genesys reporting environment with multiple instances of Stat Server Java Extensions. This property maps to the section name for the specific Stat Server Java Extension in Stat Server configuration.

extensionFileName

Required to support a Genesys reporting environment with multiple instances of Stat Server Java Extensions. This is the name of the Stat Server Java extension jar file (BPR_iWD_Extension.jar). This file was saved to the Stat Server installation directory during installation of the iWD Stat Extensions. You can find the location of this file in Stat Server configuration options as the value of the java-libraries-dir option in the java-config section.