Jump to: navigation, search


Specifies the name of the persistent cache file that ICON creates and uses to store information about agent login sessions before writing the information to IDB.

  • Configured in: ICON Application, [callconcentrator] Section
  • Default value: apstorage.db
  • Valid values: Any valid file name
  • Changes take effect: After restart

Components and Their Functions

Interaction Concentrator consists of a server, known as the ICON Server or simply ICON, and the Interaction Database (IDB).

ICON Functions

This section provides a high-level overview of ICON data-handling.

ICON preprocesses events received from Configuration Server, T-Server, Interaction Server, and Outbound Contact Server (OCS), according to the role configured for the ICON instance. Preprocessing occurs in the in-memory queue (accumulator).

You can configure the size of the in-memory queue or the interval at which data is written from it to the persistent queue. You can also configure the total number of keep-in-memory interactions that can reside concurrently in an interaction queue or interaction workbin. (This functionality requires Interaction Server release 7.6.1 or higher.)

For more information about the relevant configurations, refer to the in-memory queue options.

Once data is processed in the in-memory queue, ICON performs the following functions:

  • Writes the data from the in-memory queue to the persistent queue and persistent caches.
  • Manages the data in the persistent queue and persistent caches.
  • Writes data from the persistent queue into IDB.
  • Writes data from the persistent cache for configuration data (cfg-sync.db) into IDB.
For detailed information about the configuration options that determine ICON functionality and performance, see Configuration Options.

The persistent queue is a file that ICON creates and uses to store data before writing it to IDB. The persistent queue also stores information about requests to write data to IDB. Data in the persistent queue survives a shutdown and restart of ICON. The size of the persistent queue is not formally limited by ICON, but the operating system may impose some limitations.

To reduce the possibility that Interaction Concentrator might lose connection with the PQ file you are required to locate it on a local drive rather than a network or removable drive.

Each ICON instance creates its own persistent queue file (default name icon.pq), which stores data for all the roles that are configured for that ICON. For more information, see ICON Roles.

Persistent Queue Configuration Options

ICON configuration options enable you to specify:

  • The file name of the persistent queue.
  • The frequency (in terms of number of committed transactions) with which ICON clears data out of the persistent queue.
  • Thresholds for environment failure alarms.
  • The alarm thresholds can be used to monitor ICON performance.
  • Persistent queue behavior at startup.

For more information, see persistent queue configuration options.

In addition to the regular persistent queue, the ICON instance that performs the cfg role creates and maintains a persistent cache for configuration data. The name of the persistent cache for configuration data is cfg-sync.db and it cannot be changed.

The cfg-sync.db persistent cache plays an important role in maintaining IDB synchronization with the Configuration Database. ICON keeps a timestamp in the persistent cache for configuration data changes and, on startup, requests from Configuration Server all configuration changes that occurred after that timestamp.

  • For more information about how the persistent queue and the cfg-sync.db persistent cache work to maintain up-to-date configuration information, see the section about populating configuration data in the Interaction Concentrator User's Guide.
Persistent Cache for Agent Login Session Data

In addition to the regular persistent queue, the ICON instances that perform the gcc, gls, and gud roles create and maintain a persistent cache for agent login session data. In High Availability (HA) deployments, ICON uses this cache to prevent duplicate storage of agent login sessions in IDB and to prevent stuck login sessions. For more information, see the chapter about agent states and login sessions in the Interaction Concentrator User's Guide.

A configuration option, agent-pstorage-name (see agent-pstorage-name Option), enables you to specify the name of this persistent cache. The default file name is apstorage.db.

Interaction Database (IDB)

The Interaction Database (IDB) stores data about contact center interactions and resources at a granular level of detail. IDB is a database optimized for storage (in other words, primarily for inserting data). Interaction Concentrator itself does not provide a reporting facility. You can use IDB as a consistent and reliable data source for downstream reporting applications.

  • For a high-level description of the IDB architecture, see the chapter about IDB schema in the Interaction Concentrator 8.1 User's Guide.
  • For a complete table structure and descriptions of all IDB tables and fields, see the Interaction Concentrator 8.1 Physical Data Model document for your particular relational database management system (RDBMS).

Stored Procedures

Interaction Concentrator uses a number of stored procedures. Most of these are entirely internal to Interaction Concentrator functioning. Therefore detailed information about them is not relevant for end users.

Most stored procedure names start with a schema-specific prefix, so that they constitute a schema-specific package. Each ICON 8.1.x version works only with the stored procedures package for the associated schema. This streamlines future migration by reducing the number and combinations of scripts that must be executed to upgrade the required stored procedures. A wrapper script links the stored procedures that are exposed for end-user use to the equivalent stored procedures in each schema-specific set.

The following stored procedures are exposed for end-user use and require user input or action:

[+] Merge Procedures
[+] Purge Procedures
[+] Time-Setting
[+] Custom Dispatchers

This page was last edited on September 11, 2014, at 14:13.


Comment on this article:

blog comments powered by Disqus