Jump to: navigation, search

thread-pool-size

Section: gim-export
Default Value: 10
Valid Values: Any positive integer
Changes Take Effect: On the next job run
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 job run
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 job run
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 job run
Dependencies: None
Introduced: 8.5.005

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

output-directory

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

Specifies the directory where exported files are stored.

max-retries

Section: gim-export
Default Value: 3
Valid Values: Any non-negative integer
Changes Take Effect: On the next job run
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.

days-to-keep-output-files

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

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

chunk-size-seconds

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

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

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.

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.

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 GI2 and Genesys CX Insights reports. RAA is required for GI2 and Genesys CX Insights 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.



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
Notes:
  • 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 Deployment Guide.

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 Genesys Interactive Insights (GI2) reports 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:

  • [+] Expand: Scheduling the ETL cycle
  • [+] Expand: Job sequencing rules
  • [+] Expand: Sample schedule
  • [+] Expand: Procedure: Setting scheduling options for Genesys Info Mart Server

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:

  • [+] Expand: Procedure: Running jobs one by one
  • [+] Expand: Procedure: Running a job immediately
  • [+] Expand: Procedure: Re-aggregating data
  • [+] Expand: Procedure: Canceling a scheduled job
  • [+] Expand: Procedure: Stopping a running job

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 1 March 2018, at 13:35.