Jump to: navigation, search

run-export

Section: schedule
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Dependencies: None
Introduced: 8.5.005

Specifies whether Job_ExportGIM will run. When the value of this option is set to true, the scheduler will start and run the job at the time and intervals specified by the export-schedule option.

thread-pool-size

Section: gim-export
Default Value: 10
Valid Values: Any positive integer
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the maximum number of worker threads that are used to export data concurrently.

start-date

Section: gim-export
Default Value: No default value
Valid Values: Any date after 1970 in the format yyyy-mm-dd hh:mm:ss
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the earliest date for which Job_ExportGIM exports data. If no date is specified (the default), Job_ExportGIM starts exporting from the beginning of the Info Mart data.

retry-delay-seconds

Section: gim-export
Default Value: 30
Valid Values: Any non-negative integer
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the amount of time, in seconds, that the job waits in the case of intermittent failure before attempting to run again.

output-files-encoding

Section: gim-export
Default Value: utf8
Valid Values: Character encoding supported by Java
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the character encoding for exported files. For Java-supported encodings, see Supported Encodings.

max-retries

Section: gim-export
Default Value: 3
Valid Values: Any non-negative integer
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the maximum numbers of retries the job does in the case of intermittent failures before failing the job.

chunk-size-seconds

Section: gim-export
Default Value: 86400
Valid Values: Any positive integer
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the size of the time interval, in seconds, for which data is exported in each job.

export-schedule

Section: schedule
Default Value: 20 0/8
Valid Values: A valid CRON expression
Changes Take Effect: Immediately
Dependencies: run-export
Introduced: 8.5.005

Defines the time intervals at which Job_ExportGIM will run. The job will start and then run periodically in accordance with this schedule when the run-export option is set to true. By default, the job runs at 00:20, 08:20, and 16:20 every day.

The default schedule, run in conjunction with the default chunk-size-seconds option in the [gim-export] section, is designed to keep daily disruptions or delays from carrying over to the next day.

Job_ExportGIM can run in conjunction with the ETL jobs, but not in conjunction with Job_MaintainGIM.

The schedule is defined in the format of a CRON expression that represents a set. The expression comprises two fields, which are separated by whitespace:

  • The first field specifies minutes. Valid values are 0–59 and optional special characters (see below).
  • The second field specifies hours. Valid values are 0–23 and allowed special characters.

The following special characters are allowed in the CRON expression:

  • , (comma)—Separates items in a list.
  • - (hyphen)—Defines a range.
  • * (asterisk)—Indicates that the CRON expression will match for all values of the field.
  • / (forward slash)—Describes increments.

use-export-views

Section: gim-export
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.009.20

Controls whether Genesys Info Mart will export data using export views, which represent a snapshot of the Info Mart schema at the time the export views were created.

  • false—Genesys Info Mart will export data using the current schema. The export might include schema changes, such as new or renamed tables or columns, that occurred as part of a recent Info Mart migration.
  • true—Genesys Info Mart will export data using export views. The export will include the same tables and columns as the previous export(s), regardless of any schema changes resulting from migration(s) that may have occurred in the interim.

days-to-keep-output-files

Section: gim-export
Default Value: 14
Valid Values: Any positive integer
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies how many days to store exported files before deleting them.

output-directory

Section: gim-export
Default Value: output
Valid Values: Valid directory path (might not exist)
Changes Take Effect: On the next run of Job_ExportGIM
Dependencies: None
Introduced: 8.5.005

Specifies the directory where exported files are stored.

maintain-start-time

Section: schedule
Default Value: 03:00
Valid Values: 00:00-23:59
Changes Take Effect: Immediately
Dependencies: run-maintain

Specifies the time of day, in 24-hour format, when Job_MaintainGIM is started. This job is scheduled to start at this time when the run-maintain option is set to TRUE. The value that you specify must be outside the range that is specified by etl-start-time and etl-end-time.

more...

run-maintain

Section: schedule
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
Dependencies: None

Specifies whether to run Job_MaintainGIM at the scheduled time, as specified by the maintain-start-time option.

aggregation-engine-class-name

Section: gim-etl
Default Value: none
Valid Values: Any string
Changes Take Effect: On restart
Dependencies: None

Specifies the class name of the aggregation package, if it is installed. If your deployment uses GI2 or the separately installed RAA package, specify the following value: "GIMAgg.GimInterfaceImpl.AggregationImpl"

For more information, see the Reporting and Analytics Aggregates Deployment Guide.

aggregate-duration

Section: schedule
Default Value: 5:00
Valid Values: 00:00-24:00
Changes Take Effect: Immediately
Dependencies: run-aggregates, aggregate-schedule

Specifies the amount of time, in 24-hour format, that Job_AggregateGIM will run after it is launched. When the run-aggregates option is set to TRUE, the scheduler will stop the aggregation job when this interval expires. The aggregation job is launched in accordance with a schedule defined by the aggregate-schedule option. After the aggregation job is launched, it runs continuously until the aggregation-duration interval expires.

aggregate-schedule

Section: schedule
Default Value: 0 1
Valid Values: A valid CRON expression
Changes Take Effect: Immediately
Dependencies: run-aggregates

Specifies the daily schedule for Job_AggregateGIM to start. The job will start in accordance with this schedule when aggregation is being controlled by the scheduler (in other words, the run-aggregates option is set to TRUE). Between them, the aggregate-schedule and aggregate-duration options define daily time intervals within which Job_AggregateGIM will run continuously.

The schedule is defined in the format of a CRON expression that represents a set. The expression comprises two fields, which are separated by whitespace:

  • The first field specifies minutes. Valid values are 0–59 and optional special characters (see below).
  • The second field specifies hours. Valid values are 0–23 and allowed special characters.

The following special characters are allowed in the CRON expression:

  • , (comma)—Separates items in a list. For example, specifying the first field (minutes) as 0,30,45 means the 0th, 30th, and 45th minutes of the hour.
  • - (hyphen)—Defines a range. For example, specifying the first field (minutes) as 30-35 means every minute between the 30th and 35th minute of the hour, inclusive; this is the same as specifying 30,31,32,33,34,35.
  • * (asterisk)—Indicates that the CRON expression will match for all values of the field. For example, specifying the second field (hours) as * means every hour in the day.</li>
  • / (forward slash)—Describes increments. For example, specifying the first field (minutes) as 0/10 means the 0th minute of the hour and every 10 minutes thereafter.
more...

run-aggregates

Section: schedule
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Dependencies: None

Specifies whether the scheduler will manage the aggregation job, to run the aggregation engine inside the Genesys Info Mart process.

more...

update-stats-schedule

Section: schedule
Default Value: 0/10 *
Valid Values: A valid CRON expression
Changes Take Effect: Immediately
Dependencies: run-update-stats

Defines the time intervals at which Job_UpdateStats will run. The job will start and then run periodically in accordance with this schedule. By default, the job runs every 10 minutes throughout the day. Job_UpdateStats can run in conjunction with the ETL jobs, but not in conjunction with Job_MaintainGIM.

The schedule is defined in the format of a CRON expression that represents a set. The expression comprises two fields, which are separated by whitespace:

  • The first field specifies minutes. Valid values are 0–59 and optional special characters (see below).
  • The second field specifies hours. Valid values are 0–23 and allowed special characters.

The following special characters are allowed in the CRON expression:

  • , (comma)—Separates items in a list. For example, specifying the first field (minutes) as 0,30,45 means the 0th, 30th, and 45th minutes of the hour.
  • - (hyphen)—Defines a range. For example, specifying the first field (minutes) as 30-35 means every minute between the 30th and 35th minute of the hour, inclusive; this is the same as specifying 30,31,32,33,34,35.
  • * (asterisk)—Indicates that the CRON expression will match for all values of the field. For example, specifying the second field (hours) as * means every hour in the day.
  • / (forward slash)—Describes increments. For example, specifying the first field (minutes) as 0/10 means the 0th minute of the hour and every 10 minutes thereafter.
more...

run-update-stats

Section: schedule
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Dependencies: None

Specifies whether Job_UpdateStats will run in PostgreSQL deployments, at the time and intervals specified by the update-stats-schedule option.

run-scheduler

Section: schedule
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Dependencies: None

Specifies whether to stop or start the scheduler. If the value of this option was set to true, so that the scheduler is currently scheduling jobs, and you change the value of this option to FALSE, the scheduler pauses, with no effect on any jobs that might already be running. If you then reset the value to TRUE, the scheduler resumes at the point at which it stopped.

etl-frequency

Section: schedule
Default Value: 1
Valid Values: 0-1440
Changes Take Effect: On the next ETL cycle
Dependencies: None

Specifies the number of minutes that pass between the start times of each ETL cycle. If the amount of time that it takes to complete a cycle is shorter than the specified value, the next cycle is delayed until the time elapses. If the amount of time that it takes to complete a cycle is longer than the specified value, the next cycle is started immediately.

more...

etl-end-time

Section: schedule
Default Value: 22:00
Valid Values: 00:00-23:59
Changes Take Effect: Immediately
Dependencies: run-scheduler, etl-start-time

Specifies the time of day, in 24-hour format, when the last ETL cycle can start running. If the value that you specify is before the ETL start time, the end time is for the next day (past midnight).

If etl-start-time=etl-end-time, the ETL cycle will run continuously.

more...

etl-start-time

Section: schedule
Default Value: 06:00
Valid Values: 00:00-23:59
Changes Take Effect: Immediately
Dependencies: run-scheduler

Specifies the time of day, in 24-hour format, when the first ETL cycle starts running.

timezone

Section: schedule
Default Value: GMT
Valid Values: Any valid Java time zone
Changes Take Effect: Immediately
Dependencies: None

Specifies the time zone in which the schedule is defined. Internally, Genesys Info Mart maintains the schedule in UTC time. For convenience, you can use this option to specify a local time zone that makes it easier for you to plan and manage the schedule. You can use any valid time zone that is supported by the version of the JRE that runs the Genesys Info Mart Server.

more...

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.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Genesys Interactive Insights

Also known as GI2. A presentation layer that extracts data from the Genesys Info Mart database, and presents it in readable reports to enable business and contact center managers to make better business decisions for streamlining operations, reducing costs, and providing better services.

For Genesys Cloud customers, depending on the release of Genesys Cloud that you are using, historical reporting is available through either the Genesys Interactive Insights (GI2) interface, or through Genesys CX Insights. See also Genesys Info Mart, Reporting and Analytics Aggregates (RAA), and Genesys CX Insights (GCXI).



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Genesys CX Insights

Genesys Customer Experience Insights (Genesys CX Insights or sometimes GCXI) provides a presentation layer that extracts data from the Genesys Info Mart database, and presents it in readable historical reports to enable business and contact center managers to make better business decisions for streamlining operations, reducing costs, and providing better services.

For Genesys Cloud customers, depending on the release of Genesys Cloud that you are using, historical reporting is available through either the Genesys Interactive Insights (GI2) interface, or through Genesys CX Insights. See also Genesys Info Mart, Reporting and Analytics Aggregates (RAA), and Genesys Interactive Insights (GI2).



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Extract, Transform, And Load

Also known as ETL. The ETL processes extract data from various data sources; transform the data into a format and structure that is suitable for subsequent business purposes; and load the data into a target data store (other database, data mart, or data warehouse).



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Managing and Scheduling Jobs

This page describes how to manage and schedule the Genesys Info Mart jobs, either automatically or manually, using Genesys Info Mart Server and Genesys Info Mart Manager.

For descriptions of the Genesys Info Mart jobs, see About Jobs. For information about how Genesys Info Mart handles errors that it might encounter during job execution, see Troubleshooting Genesys Info Mart jobs.

Important
  • Before you can execute any job, you must complete the tasks in the Genesys Info Mart Deployment Guide.
  • The Genesys Info Mart Server checks the integrity of the Genesys Info Mart deployment and prevents any new job from starting if the configuration check encounters errors in the items that it validates. For more information about when Genesys Info Mart performs the configuration check and which items it checks, see the section about deployment verification in the chapter about maintenance and other activities in the Genesys Info Mart 8.1 Deployment Guide (link available here).

Scheduling jobs with Genesys Info Mart Server

The Genesys Info Mart Server launches jobs based on the scheduling options that you configure in the Genesys Info Mart application, with any necessary adjustments to accommodate logical rules that guide scheduling. (For convenience, this function is called the Scheduler.) The basic unit of scheduling is the ETL cycle. The ETL cycle performs the following functions:

  • Extracts data from each data source.
  • Transforms the extracted data, and loads the transformed data into the Dimension tables and the Fact tables.

Additional jobs run on a scheduled basis to perform the following functions:

  • An optional aggregation process, which runs in parallel with the ETL cycle, runs continuously within configured time intervals to populate Aggregate tables, in an environment where either the Genesys historical reporting presentation layer (GCXI or GI2) or Reporting and Analytics Aggregates (RAA) package are deployed.
  • Job_MaintainGIM, which runs outside the ETL cycle, purges data from the Info Mart database, in accordance with configurable data retention policies. The job also maintains the default and custom calendars. In partitioned databases, the job also maintains the partitions.
  • In PostgreSQL deployments, Job_UpdateStats, which runs in parallel with the ETL cycle, performs supplementary database maintenance.

The following topics provide additional information about scheduling jobs:

Scheduling the ETL cycle

ETL Cycle Configuration Options—The options that control the ETL cycle enable you to specify the:

  • Time of day that the first ETL cycle should begin
  • Time of day that the final ETL cycle should begin
  • Frequency of the ETL cycle

Non–ETL-Related Scheduling Options—You configure additional options to specify:

  • Whether calculation of aggregates occurs in parallel with the ETL cycle
  • The times of day when the purging of old Info Mart data should start and end
  • In PostgreSQL deployments, whether and when Job_UpdateStats will run
  • The time zone in which the schedule will be defined

The configuration options also enable you to:

  • Temporarily stop Genesys Info Mart Server from launching scheduled jobs
  • Stop Genesys Info Mart Server from launching the job that calculates the Aggregate tables
  • Stop Genesys Info Mart from launching the job that purges old data from the Info Mart database

Job sequencing rules

Genesys expects that jobs will usually follow an orderly sequence in accordance with a configured schedule: Job_ExtractICON followed by Job_TransformGIM in repeated ETL cycles, with Job_AggregateGIM (in deployments with Genesys-provided aggregation) and Job_UpdateStats (in PostgreSQL deployments) running in parallel with the ETL cycle, followed by a daily run of Job_MaintainGIM in a maintenance window during which no other jobs are running.

You can start a job manually at any time from Genesys Info Mart Manager—for example, you might need to run Job_MaintainGIM in order to populate a reconfigured calendar or, if your Info Mart database is partitioned, in order to create new partitions before the next extraction.

Job_TransformGIM has a logical dependence on Job_ExtractICON, and Job_AggregateGIM has a logical dependence on Job_TransformGIM. That is, until you perform an extraction, there is nothing to transform, and until you have performed extraction and transformation, there is no data to aggregate. Genesys Info Mart does not enforce any rules regarding logical dependence. If you manually run a job before the logically prior job has completed, the “later” job will simply not process any data.

To prevent deadlocks, it is important that no other jobs run while Job_MaintainGIM is running. Genesys Info Mart enforces this rule against parallel execution when jobs are run by the Scheduler.

Scheduler-run jobs

When you have Scheduler-run jobs on a configured schedule (see selow, Setting scheduling options for Genesys Info Mart Server), Scheduler manages jobs automatically according to the following rules:

  • The Genesys Info Mart Server does not start a job if there is another instance of that job already running.
  • During a scheduled ETL cycle, Scheduler launches the transformation job after the extraction job completes.
  • Scheduler ensures that the extraction and transformation jobs do not run at the same time as the maintenance job, which purges Info Mart data. If the last cycle of the extraction and transformation jobs is still running when the maintenance window starts, Scheduler waits for the extraction and transformation jobs to complete before it allows the maintenance job to start.
    If a scheduled ETL cycle is set to begin before a maintenance job is finished, Scheduler stops the maintenance job and starts the ETL cycle.
  • In PostgreSQL deployments, Scheduler allows Job_UpdateStats to run in conjunction with the ETL jobs. Scheduler will not wait for Job_UpdateStats to complete before it allows the maintenance job to start. However, once the maintenance job has started as part of the configured schedule, Scheduler suspends the schedule for Job_UpdateStats until the maintenance job finishes.

Jobs run from Genesys Info Mart Manager

When you start a job from Genesys Info Mart Manager (see below, Managing jobs with Genesys Info Mart Manager) the Genesys Info Mart Server manages the jobs according to the following rules:

  • The Genesys Info Mart Server does not start a job if there is another instance of that job already running.
  • You can launch the transformation job manually from Genesys Info Mart Manager while an extraction job is running, but the transformation job will not do anything if no data has been extracted.
  • The Genesys Info Mart Server does not prevent other jobs from running at the same time as the maintenance job. To prevent deadlocks that can lead to job failures, ensure that you suspend the ETL schedule and, in PostgreSQL deployments, the Job_UpdateStats schedule, before you run Job_MaintainGIM from Genesys Info Mart Manager.
  • In the case of the aggregation job, Genesys Info Mart Server does not allow an instance of the job to run outside the regularly scheduled intervals within which Job_AggregateGIM has been configured to run. For example, if Job_AggregateGIM has been configured to run every day between 01:00 AM and 06:00 AM, you will not be able to launch Job_AggregateGIM manually from Genesys Info Mart Manager at any time outside that time period (for example, at 08:00 AM).

Sample schedule

The figure Sample Genesys Info Mart Server Schedule depicts a sample Genesys Info Mart Server job schedule that runs repeated ETL cycles throughout the day. The deployment includes aggregation, and the aggregation job has been scheduled to run for 23 hours out of each day, leaving one hour each day when Job_AggregateGIM is stopped, providing an opportunity for Job_MaintainGIM to run. Sample Genesys Info Mart Server Schedule The schedule options are set as follows:

 
etl-start-time = 06:30 
etl-end-time = 00:30 
etl-frequency = 30 minutes 	
maintain-start-time = 03:00
aggregate-schedule = 0 4
aggregate-duration = 23:00 
timezone = <business user local time zone>

The schedule has been defined in the local time zone of the business user that will query the Info Mart data. Therefore, from the perspective of the business user, the Genesys Info Mart Server is in the same time zone, and the final extraction cycle, which begins at 00:30, contains all the reporting data from the previous day.

Important
Midnight in local time is considered to be the end of the reporting day for a particular time zone.

Setting scheduling options for Genesys Info Mart Server

The information in this subsection supplements information in the Genesys Info Mart Deployment Guide about configuring the Genesys Info Mart Application.

Use the following procedure to configure the Genesys Info Mart Server [schedule] options. Genesys Info Mart Server uses these options to launch the ETL, aggregation, maintenance, and, in PostgreSQL deployments, supplementary maintenance jobs. Each configuration option is related to one or more of the jobs.

The schedules for the ETL and maintenance jobs are defined in 24-hour time spans in the format HH:mm, where HH is the number of hours (00–23), and mm represents the number of minutes (00–59). The 24-hour schedule can span two calendar days. For example, if the etl-start-time is defined as 18:00 and the etl-end-time is defined as 06:00, the start time is 6:00 PM one day and the end time is 6:00 AM the following day.

For information about the functions of the jobs, see Understanding Genesys Info Mart jobs. For information on job interdependencies, see Job sequencing rules.

Procedure: Setting up the Genesys Info Mart jobs schedule

Purpose: To create or modify the schedule for running Genesys Info Mart jobs.

You can perform this procedure at any time, even while Genesys Info Mart jobs are running. Changes take effect immediately.

Steps

  1. In the interface you use to configure your Genesys applications, navigate to the Options tab of the Genesys Info Mart Application object.
  2. Navigate to the [schedule] section.
  3. (Optional) Time Zone—Enter a value for timezone to specify a local time zone in which you want to define the schedule. You can use any valid time zone that is supported by the version of the Java Runtime Environment (JRE) that runs the Genesys Info Mart Server. The default time zone is GMT.
  4. ETL Schedule—Set the options that control the ETL schedule:
    1. Enter a value for etl-start-time to specify the time of day that the first ETL cycle begins.
    2. Enter a value for etl-end-time to specify the time of day that the final ETL cycle begins. The etl-end-time value should be a time of day when no other ETL cycles will begin.
    3. Enter a value for etl-frequency to specify the number of minutes between the start times of adjacent ETL cycles.
      If the time that it takes to complete a cycle is shorter than the ETL frequency, the next cycle is delayed until the time interval is met. If the time that it takes to complete a cycle is greater than this value, the next cycle starts immediately.
      Important
      Various extract-* options in the [gim-etl] section control aspects of extraction and transformation job functioning that significantly affect ETL cycle performance. When you set the ETL scheduling options, consider the values of these related options as well. For more information, see the configuration recommendations in the chapter about ETL processing in the Genesys Info Mart 8.1 Deployment Guide. See also the gim-etl Section option descriptions in the Genesys Info Mart Configuration Options Reference.
  5. To start or resume the ETL schedule, set run-scheduler to true. You can set this option to false to temporarily stop Genesys Info Mart Server launching jobs.
  6. Routine Maintenance for PostgreSQL—In PostgreSQL deployments, configure Genesys Info Mart to update statistics regularly and perform additional supplementary maintenance:
    1. Set run-update-stats to true. This option specifies whether the Genesys Info Mart Server launches the supplementary maintenance job, Job_UpdateStats, as scheduled.
    2. Set update-stats-schedule to the start time and time intervals at which you want the job to run every day. The value must be expressed as a valid CRON expression—a string, which in this case uses only two fields, minute and hour, separated by whitespace. For more information, see the extended description of the option in the Genesys Info Mart Configuration Options Reference.
      The default value (0/10 *) schedules the job to run every 10 minutes throughout the day. You do not need to consider the ETL and maintenance schedules when setting the Job_UpdateStats schedule, for reasons that are described in Job sequencing rules.
  7. Aggregation Schedule—If you plan to use the Info Mart historical Aggregate tables:
    1. Set run-aggregates to true. This option specifies whether the Genesys Info Mart Server launches the job, Job_AggregateGIM. This job calculates the Aggregate tables based on newly added or changed data in the fact tables.
    2. Set aggregate-schedule to the time that you want the aggregation job to start (as long as it is not currently running, such as following the initial deployment of the aggregates). The value must be expressed as a valid CRON expression—a string, which in this case uses only two fields, minute and hour, separated by whitespace.
      For example, to set the aggregation start time to 2:30 AM, enter the value 30 2. For another example, see Sample schedule. For more information, see the extended description of the option in the Genesys Info Mart Configuration Options Reference.
    3. Set aggregate-duration to the length of the period, in HH:mm format, during which the aggregation job will run after each launch. Within the time intervals defined by the aggregate-schedule and aggregate-duration options, the aggregation job runs continuously.
      For example, to have aggregation run for the twelve hours following the start time, set the value for the duration option to 12:00. For another example, see Sample schedule.
    4. Navigate to the [gim-etl] configuration section and set aggregation-engine-class-name. This option specifies the class name of the aggregation package.
      In order for Aggregate tables to be created and populated in the Info Mart database, you must deploy RAA. (RAA is bundled with GI2, and GI2 customers do not need to install RAA separately.)
      If you do not plan to use the Info Mart Aggregate tables, keep the default value of the run-aggregates option (false). This setting ensures that the Genesys Info Mart Server does not launch Job_AggregateGIM in deployments where the Genesys-provided aggregation engine is not deployed.
  8. Maintenance Schedule—If you plan to run the maintenance job daily, configure the maintenance job schedule:
    1. Set run-maintain to true. This option specifies whether the Genesys Info Mart Server launches the maintenance job, Job_MaintainGIM, as scheduled.
    2. Set maintain-start-time to the time of day that you want Genesys Info Mart to launch Job_MaintainGIM. The time of day must be outside the range that is specified by etl-start-time and etl-end-time. The Genesys Info Mart Server will not start Job_MaintainGIM until the maintain-start-time has been reached or when other jobs are running.
      Important
      You must run the maintenance job regularly if your Info Mart database is partitioned. Genesys strongly recommends that you configure a schedule for the maintenance job if your Info Mart database is partitioned, if you plan to purge eligible data from the Info Mart database, or if your deployment uses custom calendars.

      For information about setting the retention policy options that determine what data will be purged when Job_MaintainGIM executes, see the section about purging the Info Mart database in the chapter about maintenance and other activities in the Genesys Info Mart 8.1 Deployment Guide (link available here). See also the descriptions of the days-to-keep-* options on gim-etl Section in the Genesys Info Mart Configuration Options Reference.
  9. Export Schedule—Optionally, enable the export of data from the Info Mart database into local .csv files by modifying configuration settings in the Genesys Info Mart Application object to enable the export function for your deployment:
    1. Create a new [gim-export] configuration section, if it does not already exist. Within this section:
      1. Configure the output-directory configuration option with a value that defines the path to the export storage folder. By default, the folder is named output and is created within the Genesys Info Mart installation directory.
      2. Configure the days-to-keep-output-files configuration option with a value that defines the number of retention days for the exported data. The default value is 14 days.
      3. If you want Job_ExportGIM to use export views to export your data, set use-export-views to true.
    2. In the [schedule] configuration section, create a new export-schedule configuration option (if it does not already exist) and set a value that defines the schedule for Job_ExportGIM. The value must be a valid CRON expression. (For details on the format, see the extended export-schedule description in the Genesys Info Mart Configuration Options Reference.) By default, the export job runs at 00:20, 08:20, and 16:20 each day.
    3. If necessary, make changes to the default settings for other configuration options that control Job_ExportGIM:
    4. In the [schedule] section of the Genesys Info Mart Application object, create a new run-export configuration option (if it does not already exist) and set it to true, to start running the export job according to the schedule.

Managing jobs with Genesys Info Mart Manager

Normally, the Genesys Info Mart Server launches scheduled jobs automatically. However, you can use the Genesys Info Mart Manager to:

  • Execute a single job as needed.
  • Cancel a job that is in Scheduled status. (A scheduled job is one that did not start immediately (for example because it cannot run while another job is running, and another job was already running), but it will start later.)
  • Stop a running job.

For example, you can use this functionality in Genesys Info Mart Manager to:

  • Execute one or more jobs to recover from job failures.
  • Execute Job_ExtractICON following the update of configuration data in Interaction Database (IDB) with the Interaction Concentrator (ICON) on-demand resynchronization feature.
  • Manually run the job that aggregates Info Mart data (Job_AggregateGIM), provided that Genesys Info Mart has not been configured to run the aggregation job on a schedule. (In other words, you can start or stop Job_AggregateGIM from the Genesys Info Mart Manager only if the run-aggregates configuration option, in the [schedule] section, has been set to false.)
  • Manually run Job_AggregateGIM to re-aggregate Info Mart data.
  • Run the maintenance job outside the scheduled time, provided that no instances of other jobs are running.
  • Execute a single job as needed.
  • Selectively shut down a running job.
Important
You cannot use Genesys Info Mart Manager to run Job_UpdateStats or Job_ExportGIM.

Job management procedures

The following procedures describe how to use Genesys Info Mart Manager to manage jobs:

Procedure: Running jobs one by one with Genesys Info Mart Manager

Purpose: This procedure describes how to run jobs manually, one by one, for testing or troubleshooting purposes.

Initially after deploying Genesys Info Mart, you may want to run the jobs one by one to test the best values for various configuration options, rather than immediately scheduling them to run routinely. Or, rarely, you may need to run jobs one by one while troubleshooting.

Steps

  1. ETL Cycle Jobs—Set the run-scheduler configuration option (in the [schedule] section on the Genesys Info Mart Options tab) to false.
  2. Follow the steps in Running a job immediately to run the jobs that perform ETL processing. Run the jobs in the following order:
    • Job_ExtractICON (see the following Note)
    • Job_TransformGIM
    Important
    The extraction job extracts data from all available IDBs, for all extraction roles. When you have completed your trial runs or troubleshooting, restore normal running conditions by setting the run-scheduler configuration option to true to have the Genesys Info Mart Server launch jobs based on a schedule you configure in the Genesys Info Mart application. For more information, see Setting scheduling options for Genesys Info Mart Server.
  3. Aggregation Job—If your deployment includes aggregation and you want to run Job_AggregateGIM as a non-scheduled job, set the run-aggregates configuration option (in the [schedule] section on the Genesys Info Mart Options tab) to false.
  4. Follow the steps in Running a job immediately to start Job_AggregateGIM. The job will run continuously until you manually stop it, or until you reset the run-aggregates configuration option from false to true and the configured daily schedule comes into effect.
  5. Maintenance Job—Set the run-maintain configuration option (in the [schedule] section on the Genesys Info Mart Options tab) to false.
  6. In the job list of the Genesys Info Mart Manager, verify that no other jobs are running.
  7. Follow the steps in Running a job immediately to start Job_MaintainGIM. After the initial run, you can set the run-maintain configuration option to true, so that the Genesys Info Mart Server launches the maintenance job based on the schedule you configured in the Genesys Info Mart application. For more information, see Setting scheduling options for Genesys Info Mart Server.

Procedure: Running a job immediately with Genesys Info Mart Manager

Purpose: This procedure describes how you can use Genesys Info Mart Manager to run a job immediately.

Steps

    Genesys Info Mart Manager Run Job Dialog Box
  1. In Genesys Info Mart Manager, click Run Job. The Run Job dialog box appears, as shown in the Figure Genesys Info Mart Manager Run Job Dialog Box.
  2. From the list, select the job that you wish to execute.
    Important
    Only Job_AggregateGIM supports parameters. For all other jobs, leave the Job Parameters field blank. For more information, see Re-aggregating data.
  3. Click OK.
    The job you have started appears in the job list. You can find it more easily by sorting the list (for example, by Start Time, or by Status). The job you ran will have one of the following status values:
    • Running
    • Scheduled—This indicates that the job did not start immediately (for example because it cannot run while another job is running, and another job was already running), but it will start later.
    • Failed—This indicates that an error occurred when the job tried to run.
    Important
    Job status is not automatically updated. To see the current status of a job (for instance, to see if a Running job has completed) click Refresh.

Procedure: Re-aggregating data with Genesys Info Mart Manager

Purpose: This procedure describes how you can use Genesys Info Mart Manager to re-aggregate data.

Important

Re-aggregation is possible only if aggregation is already running. If you attempt to run Job_AggregateGIM with the re-aggregation job parameters when aggregation is not running, Genesys Info Mart starts aggregation, ignoring the job parameters. In this case, you can re-aggregate by running the job, with the re-aggregation parameters, a second time.

A request to re-aggregate data for a specific time range first deletes aggregated data from that time range (to prevent duplicate data from being written to Info Mart). Before you issue a re-aggregation command, make sure that facts for your selected time range exist in the Info Mart database and have not been purged. Otherwise, you could be left with no aggregates at all for that time range.

Prerequisites: Job_AggregateGIM is running, either in accordance with the configured job schedule or else because you started it manually. If necessary, follow the steps in Running a job immediately to start Job_AggregateGIM.

Steps

  1. In Genesys Info Mart Manager, click Run Job. The Run Job dialog box appears (see the Figure Genesys Info Mart Manager Run Job Dialog Box).
  2. In the Run Job list, select Job_AggregateGIM.
  3. In the Job Parameters field, enter:
    -insertPendingAgg <AGR_SET>:<START>:<END>
    where:
    • <AGR_SET> indicates what set to aggregate (ALLSETS, or an aggregate set name). Aggregate set name is formatted as follows: <HIERARCHY_NAME>-<AGG_LEVEL> [.Flavor]
      where:
      • <HIERARCHY_NAME> is a comma-separated list that contains one or more of the following RAA hierarchies, or no value at all: H_AGENT, H_ID, H_I_STATE_RSN, H_QUEUE_GRP, H_QUEUE_ABN, H_AGENT_GRP, H_I_AGENT, H_QUEUE, H_AGENT_CAMPAIGN, H_AGENT_QUEUE, H_I_SESS_STATE, H_QUEUE_ACC_AGENT, H_CAMPAIGN
      • <AGG_LEVEL> is the aggregation level (SUBHOUR, HOUR, DAY, MONTH, QUARTER, YEAR).
      • [.Flavor] is an optional parameter indicating whether to include only online or offline data (Online or Offline).
    • <START> is a value (YYYY-MM-DD) from the DATE_TIME table that indicates the beginning of the reporting interval.
    • <END> is a value (YYYY-MM-DD) from the DATE_TIME table that indicates the end of the reporting interval.

    Re-Aggregation Parameter Examples—For example, to re-aggregate:

    • All aggregates for a one-month period:
      -insertPendingAgg ALLSETS:2014-05-01:2014-05-31
    • A particular hierarchy for a specific day:
      -insertPendingAgg H_QUEUE-HOUR:2014-05-01:2014-05-02
    • Only one flavor of aggregate for a specific day:
      -insertPendingAgg H_I_AGENT-SUBHOUR.Offline:2014-05-01:2014-05-02
  4. Click OK.
    Use the Genesys Info Mart log to monitor the status of re-aggregation.

Procedure: Canceling a scheduled job with Genesys Info Mart Manager

Purpose: This procedure describes how to cancel the Run Job command for a job that has not yet begun to run (in other words, that has a status of Scheduled).

Steps

  1. In Genesys Info Mart Manager, select the job (with the status Scheduled) that you want to cancel.
  2. Click Stop Job. The job disappears from the list. </li>

Procedure: Stopping a running job with Genesys Info Mart Manager

Purpose: This procedure describes how to stop a running job.

Steps

    Stop job
  1. To stop Job_AggregateGIM, first set the run-aggregates configuration option in the Genesys Info Mart Application to false.
    Important
    If run-aggregates is set to true, the scheduler ensures that Job_AggregateGIM runs continuously during the interval specified by the configured start time and duration. Thus, if Job_AggregateGIM is running under the control of the scheduler and you try to stop the job during the interval in which it has been configured to run, the scheduler automatically restarts the job almost immediately.
  2. In Genesys Info Mart Manager, select the job that you want to stop. You can stop jobs that have a status of Running or Scheduled.
  3. Click the Stop Job button, as shown in the Figure Stop Job.
    It may take a few moments for the job to stop.
This page was last modified on April 12, 2019, at 05:53.

Feedback

Comment on this article:

blog comments powered by Disqus