Jump to: navigation, search

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

Interaction Concentrator

Also known as ICON. A Genesys product that collects and stores detailed data from various sources in a contact center that is empowered by using Genesys software. Downstream reporting systems can access Interaction Concentrator data in near–real time.
Operating on top of Genesys Framework, the product consists of a server application that is called ICON and a database that is called Interaction Database (IDB). The server receives data from data sources such as Configuration Server, T-Server, or particular Genesys solutions; it then stores this data in IDB by using Genesys DB Server.



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

High Availability

Also known as HA. The use of Redundancy to enable contact centers to minimize interruptions that are due to hardware, software, or network connectivity issues.



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

Key-Value Pair

Also known as a KVP. A data structure that is used to communicate or store a piece of information. A KVP consists of a key, whose value is an S.100 symbol, and a value, which may be any of a variety of data types, including a key-value set (thus, making the structure recursive). The key identifies the meaning of the data that is contained in the value.



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

Interaction Database

Also known as IDB. The database that stores data about contact-center interactions and resources at a granular level of detail.
See also Interaction Concentrator.



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

Message Server

The Genesys Framework component that provides centralized processing and storage of every application’s maintenance events. Events are stored as log records in the Centralized Log Database, where they are available for further centralized processing. Message Server can also be set up to produce outbound messages (alarms) that are triggered by configured log events. If it detects a match, it sends the alarm to Solution Control Server for immediate processing.



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

Configuration Server

The Genesys Framework component that stores and manages Configuration Database data, which users access through Configuration Manager and Genesys Administrator. Configuration Server prevents entry of logically incorrect configuration data, enables user-privilege-based control of access to data, and notifies client applications dynamically about changes that are made to the data.



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

Local Control Agent

Also known as LCA. A daemon component of the Management Layer that controls all daemon applications that are running within Genesys Framework. A Genesys-supplied software module that is loaded to each server platform that hosts one or more Genesys server modules. The purpose of LCA is to monitor the operating status of all locally running Genesys software modules, report errors, and restart modules if they stop operating.



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

Solution Control Server

Also known as SCS. The Genesys Framework component that serves as the control point for which SCI is the interface. Together, SCS and SCI provide the services that are described in the definition of SCI.



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

Genesys Info Mart Components

This page provides a high-level overview of Genesys Info Mart functioning. Configuration options enable you to customize almost every aspect of Genesys Info Mart functioning. However, the default configuration settings provide a Genesys Info Mart application that is suitable for a wide range of standard deployments.

Genesys Info Mart consists of the following components:

Genesys Info Mart Server

The Genesys Info Mart Server, a Java-based component, is the main executable process in Genesys Info Mart 8.x. Its main function is to run various functional jobs, including but not limited to ETL jobs. These jobs run according to the schedule that is configured in the Genesys Info Mart ETL application in Genesys Configuration Layer. The Genesys Info Mart Server also processes requests from applications outside of the Genesys Info Mart Server, such as requests from the management GUI to launch a specific job.

The Genesys Info Mart Server interfaces with:

  • Solution Control Server (through Local Control Agent), to control when the Genesys Info Mart Server starts and stops.
  • Configuration Server, to read Genesys Info Mart application configuration options, as well as other configuration objects and options that affect Genesys Info Mart functionality.
  • The management GUI (Genesys Info Mart Manager), to start and stop jobs and to provide the status of ETL jobs.
  • Message Server, to log messages to the Centralized Log Database.
  • The log4j Java client, to log messages to the local log.

Genesys Info Mart Jobs

Genesys Info Mart jobs, which run under the Genesys Info Mart Server, perform the following tasks:

  • Initialize the Info Mart database — Set up your database and modify the IDB component of Interaction Concentrator for Info Mart use.
  • During each ETL cycle, extract raw configuration, interaction, and agent-activity data. [+] Tell me more
  • During each ETL cycle, transform and load the extracted data. [+] Tell me more
  • Perform database maintenance. [+] Tell me more
  • Migrate Genesys Info Mart — Run the necessary scripts to update your Info Mart database schema and IDB schema and also perform any other steps that are necessary to move from an earlier 8.x release to the current one.
  • Aggregate — In deployments that include GI2 or the separately installed RAA package, Genesys Info Mart also hosts the aggregation process. An aggregation job, which is implemented as a plug-in, runs the aggregation engine inside the Genesys Info Mart Server process, to calculate or recalculate the historical Aggregate tables in the Info Mart database.

    For a high-level description of how the aggregation job works in Genesys Info Mart release 8.x, see Job_AggregateGIM in the Genesys Info Mart Operations Guide. For more information about the aggregation package and running the aggregation process, see the Reporting and Analytics Aggregates Deployment Guide for your release.

Genesys Info Mart Manager

Genesys Info Mart Manager is a GUI that enables monitoring and real-time administration of some aspects of the Genesys Info Mart processes. Genesys Info Mart Manager is included on the Genesys Info Mart CD as a separate installation package (IP).

Genesys Info Mart Manager provides the following functionality:

  • Displays the current job execution status.
  • Displays a history of job execution, including start time, stop time, duration, and final status.
  • Filters the job execution history that is displayed, based on time and/or status.
  • Executes a single job on an ad hoc basis.
  • Issues re-aggregation requests in deployments that include GI2 or the separately installed RAA package.
  • Shuts down a running job.

Genesys Info Mart Manager interfaces directly with the Genesys Info Mart Server to start and stop jobs on an ad hoc basis and to obtain job status and history from the Info Mart database.

Genesys Info Mart Manager, which is implemented as a plug-in for GAX, works with any operating system and is easy to deploy. No installation or configuration is required on client hosts. For information about deploying Genesys Info Mart Manager, see Installing Genesys Info Mart Manager.

Genesys Info Mart Manager can be localized. For links to information about installing language packs, see Next Steps in the procedure to install Genesys Info Mart Manager.

For more information about how to use Genesys Info Mart Manager to manage your Genesys Info Mart operations, see Managing Jobs with Genesys Info Mart Manager in the Genesys Info Mart Operations Guide.

Important
Genesys Info Mart Manager displays timestamps in the time zone selected in the GAX preferences for locale.

Genesys Info Mart Administration Console

In Genesys Info Mart releases earlier than 8.1.4, Genesys Info Mart provided the Genesys Info Mart Administration Console as the GUI for managing Genesys Info Mart jobs. While the Genesys Info Mart Administration Console is included in the Genesys Info Mart 8.5.x CD and you can continue to use it to manage Genesys Info Mart 8.5, Genesys recommends that you use Genesys Info Mart Manager instead of the Administration Console in Genesys Info Mart 8.5 deployments, particularly if your deployment already includes GAX. Therefore, the Genesys Info Mart 8.5 documentation does not provide information about installing and using the Genesys Info Mart Administration Console.

Tip
You can use both management GUIs in your deployment at the same time, if you want to enable additional administration resources but do not want to decommission an existing Administration Console.

For full information about installing the Administration Console and providing an Administration Console DAP, see the Genesys Info Mart 8.1 Deployment Guide. For information about using the Administration Console to manage Genesys Info Mart jobs, see the Genesys Info Mart 8.1 Operations Guide.

Info Mart Database

The Info Mart database contains all of the data that is populated by the ETL jobs. Info Mart data includes the low-level interaction data that is consolidated from one or more IDBs, as well as the processed data that is suitable for end-user reports.

Info Mart Tables

The Genesys Info Mart data resides in a database schema that includes the following tables:

  • Global Interaction Database (GIDB) tables — Store the low-level interaction data that is consolidated from one or more IDBs.

    There are separate sets of interaction-related GIDB tables for voice and multimedia interactions, to accommodate different requirements for transformation logic, indexes, data-retention periods, and so on.

    The low-level reporting data in GIDB supports the possibility of custom detailed reporting to drill down from the dimensional model.
  • Merge tables — Used for merge of voice interactions. After the merge, voice interactions are moved into GIDB tables.
  • Staging tables — Store information that is required in the transformation process. Staging tables contain data that has not yet been transformed or cannot be transformed because of incompleteness or inconsistency of source data and other auxiliary data that are necessary for the ETL process.
  • Temporary tables — Store data that is used only during the lifetime of one instance of a job.
  • Fact and dimension tables (collectively referred to as dimensional model) — Contain transformed data that downstream reporting applications can query and combine in meaningful reports.
  • Control tables — Store information that controls ETL execution, such as the status of running jobs, job schedules, execution history, audit logs, and similar bookkeeping information.
  • In deployments that use GI2 or RAA, the Info Mart database also includes aggregate tables and views that are used by GI2. For more information, see the Reporting and Analytics Aggregates Reference Manual for your release.

Info Mart Views

In addition to the previously mentioned tables that are used by Genesys Info Mart jobs, the following views are intended to simplify data retrieval for reports:

  • Predefined views — Read-only views of certain configuration dimensions and facts that are contained in GIDB tables. These views are created in the Info Mart database schema.
  • Tenant-specific, read-only views of the dimensions, facts, and predefined views in the dimensional model of the Info Mart schema. These views are created in a Genesys Info Mart schema.
  • Tenant-specific sets of views, which are created in a separate database schema for each tenant, so that each tenant user can access only its own data. In addition, these views shield business users from changes to the underlying database schema and prevent users from accidentally changing the contents of the underlying database. Customers should use these views to query Genesys Info Mart data.

For an illustration of the relationship between the tenant views and the Info Mart database schema, see Creating Genesys Info Mart Read-Only Tenant Views.

Genesys Info Mart provides SQL scripts that you execute to create the views that your reporting application can query. These views are created in the Genesys Info Mart and tenant user schemas.

For more information about the database schemas, see the Genesys Info Mart overview section in the Genesys Info Mart Reference Manual for your relational database management system (RDBMS).

RDBMS-Specific SQL Scripts

A set of SQL scripts is provided for each RDBMS type that is supported. The scripts perform a variety of tasks, including the following:

  • Create the Info Mart database objects.
  • Create the single-tenant and multi-tenant read-only views.
  • Update source databases for efficient data extraction.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 17 December 2015, at 15:34.