Jump to: navigation, search

Data Mart

Important
To apply changes to Datamart settings, you must restart iWD Runtime Node.

Filters and Constraints

Configuration Server respects tenancy permission settings. You can access only those objects that you have been granted permissions and privileges to access.

You can filter the contents of this list in two ways:

  1. Type the name or partial name of an object in the Quick Filter field.
  2. Click the cube icon to open the Tenant Directory filter panel. In this panel, click the Tenant that you want to select. Use the Quick Filter field in this panel to filter the Tenant list.

You can sort the items in the list by clicking a column head. Clicking a column head a second time reverses the sort order. You can add or remove columns by clicking Select Columns.

To select or de-select multiple objects at once, click Select.

Data Fields

Each entry is shown with the following data fields:

  • Name — Name of the solution hosting iWD Data Mart.

Data Fields

  • Application—The name of iWD Runtime Node application attached to selected Solution. There is a one-to-one relationship between Solutions requiring Data Mart and iWD Runtime Node applications. The iWD Runtime Node can be detached from the Solution by entering a blank name in this field.
  • Host—Host where iWD Runtime Node is installed. Selectable from the list of hosts configured in GAX Configuration Manager.
  • Port—Port assigned to iWD Runtime Node. Numeric field, the value must be between 1 and 65535 inclusive. The port must be unique within host.
  • ETL Scripts Directory—The directory on the server in which iWD Data Mart ETL scripts are stored. For example, the default path used when iWD Data Mart is installed is C:\Program Files\GCTI\iWD Data Mart\etl.
  • Number of Threads—Performance tuning: The size of the thread pool.
  • Ignored Dimensions—Performance tuning: list of dimensions that will be ignored by Load Intraday job. One dimension per line.
  • Default Dimension Key—Performance tuning: default value which will be used for ignored dimensions' keys.

The Logging tab configures internal logging capabilities within the iWD Runtime Node.

  • Log Level — The Service log level. This should be set to Info unless otherwise instructed by Genesys Technical Support. The possible log levels are:
    • Debug — the most detailed informational events that are most useful in debugging an application.
    • Info — informational messages that highlight the progress of the application.
    • Warning — potentially harmful situations.
    • Error — error events that might not affect the application’s ability to run.
    • Trace — turns on all logging.
    • Off — turns off all logging.
  • Log Directory — The directory in which the log files will be stored, for all services. If it starts with / (on Unix-based operating systems) or a drive letter (on Windows), an absolute path will be used; otherwise, the path is relative from the iWD Runtime Node installation directory.
    Note: It is strongly recommended that you only set the file path to a directory on a local machine, not a remote location such as a shared network drive. Logging to a remote location can severely impact performance.
  • Log Age — Sets the number of days that log files should be kept in the system. A value of 0 disables this limit.
  • Log Size — Sets a limit on the size of a single log file, in megabytes. A value of 0 disables this limit.
  • Log Files — Sets a limit on the number of log files that are kept for this service, excluding the current log file. A value of 0 disables this limit.

The Database tab defines a connection to a Data Mart database server. The configured database and user must exist in the database server. The user must have read/write permissions to the database.

  • Application—The name of the Database Access Point application associated with Data Mart instance.
  • Database—The name of the database. This is available only for MS SQL Server.
  • SID—Oracle System ID of the database. The Oracle System ID (SID) is used to uniquely identify a particular database on a system. This is available only for Oracle database.
  • Server—The database server. Selectable from list of configured hosts.
  • Port—The TCP port number of the database server.
  • User Name mdash;The database user name.
  • Password—The password for the database.
  • Auto-Sync—The iWD Data Mart database will be initialized automatically the first time the Database Service and Kettle ETL Service are started. If the Auto-Sync option is selected, this initialization is automatic, and the Database Service will also check for updates to the iWD Data Mart database whenever a new version of iWD Data Mart is installed. The Auto-Sync option will also initialize ETL plug-ins.
  • Custom URL—Add a specific custom URL here to override any default value for Data Mart database.

The Stat Server tab configures Statistics Adapter job and defines the connection to Genesys Stat Server. Statistics Adapter 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.

  • Application—The Stat Server's application name. Selectable from the list of installed Stat Server applications. Each Data Mart requires a separate Stat Server instance, so only Stat Server that are not already associated appear on the list.
  • Dimension Mapping—Defines how statistical dimensions are mapped.
    • Filter—Dimensions are mapped to CCPulse+ filters.
    • Virtual Queue—Dimensions are mapped to Genesys virtual queues.
  • Virtual Queue Name—Name of the Genesys virtual queue to which statistics are distributed. Applicable only if Dimension Mapping is set to Virtual Queue.
  • Service Index—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.
  • Extension File Name—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 is 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.
  • Extension Section Name—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 the Stat Server configuration.

The Schedules tab configures execution schedule of three Data Mart job groups. The syntax follow standard CRON scheduling expression. For example, the following expression will cause the job to be executed every 15 minutes:

 0 0,15,30,45 * * * ?

For more information about CRON scheduling, see Quartz Scheduler documentation.

  • Intraday—The schedule for the Intraday job group: Load Config, Load Intraday, Aggregate Intraday, Aggregate Stats and Statistic Adapter. Typically scheduled to run every 15 minutes.
  • Historical—The schedule for the Historical job group: Load Historical, Aggregate Historical and Maintain. Typically scheduled to run once a day, after midnight.
  • Prune—The schedule for Prune job. Typically scheduled to run once a day, after Historical group.

The Expirations tab configures the Maintain job, which deletes expired facts from Data Mart tables.

  • Record Details—The number of days after which the detailed task (task_fact, task_event_fact, and task_work_fact) data will be removed from the database.
  • Aggregation 15 min—The number of days after which the data will be removed from 15-minute aggregation tables.

The Tenant Attributes tab enables selection of up to 5 of a tenant's custom attributes, that will be loaded into the CUSTOM_DIM dimension and associated to the tenant via the CUSTOM_DIM_KEY field.

  • Custom Attribute 1-5—User-configured custom Tenant attributes, selectable from the list of Custom Attributes attached to the Tenant.

The Department Attributes tab allows selection of up to 5 of a departments's custom attributes that will be loaded into the CUSTOM_DIM dimension and associated to the departments via the CUSTOM_DIM_KEY field.

  • Custom Attribute 1-5—User-configured custom Department attributes, selectable from the list of Custom Attributes attached to any Department within the Solution.

The Process Attributes tab allows selection of up to 5 of a process' custom attributes, that will be loaded into the CUSTOM_DIM dimension and associated to the processes via the CUSTOM_DIM_KEY field.

  • Custom Attribute 1-5—User-configured custom Process attributes, selectable from the list of Custom Attributes attached to any Process within the Solution.

The Task Attributes tab defines up to 10 names of a task's custom attributes that will be loaded into the task_fact custom attribute fields (CUSTOM_ATTRIBUTE 1-10). Names must start with a letter, and only underscores and alphanumeric characters are supported.

In order for Kettle to pick them up, it is necessary to create fields in the Event Log Database. In the rpt_interaction and rpt_esp tables, add the fields in the following format:

*: Name: <attribute_name>, type: varchar(length).

These fields should be added to the mappings in the Event Log DAP options in the esp-custom-data and itx-custom-data sections.

For example, in order to store a custom attribute with the name order_total in the iWD Data Mart, as a task custom attribute:

  1. Create a new column in the rpt_interaction table: order_total, type: varchar(50)
  2. Create a new column in the rpt_esp table: order_total, type: varchar(50)
  3. Create a new option in the esp-custom-data section of the Event Log DAP options: order_total=order_total
  4. Create a new entry option in the itx-custom-data section of the Event Log DAP options: order_total=order_total
  5. Add order_total to the Task Attributes list in iWD GAX Plugin.

The Dimension Mapping tab defines up to 5 comma-separated names of a task's custom attributes that will be loaded into the CUSTOM_DIM dimension and associated to the task via the CUSTOM_DIM_KEY field. Names must start with a letter, and only underscores and alphanumeric characters are supported.

In order for Kettle to pick them up, it is necessary to create fields in the Event Log Database. In the rpt_interaction and rpt_esp tables, add the fields in the following format:

*: Name: <attribute_name>, type: varchar(length).

These fields should be added to the mappings in the Event Log DAP options in the esp-custom-data and itx-custom-data sections.

For example, in order to store a custom attribute with the name order_total in the iWD Data Mart, as a task custom attribute:

  1. Create a new column in the rpt_interaction table: order_total, type: varchar(50)
  2. Create a new column in the rpt_esp table: order_total, type: varchar(50)
  3. Create a new option in the esp-custom-data section of the Event Log DAP options: order_total=order_total
  4. Create a new entry option in the itx-custom-data section of the Event Log DAP options: order_total=order_total
  5. Add order_total to Dimension Mapping list in iWD GAX Plugin.

Related Links


This page was last modified on November 13, 2014, at 03:31.

Feedback

Comment on this article:

blog comments powered by Disqus