Cisco Unified CCX Administration Guide, Release 9.0(1)
Unified CCX historical reporting management
Downloads: This chapterpdf (PDF - 1.22MB) The complete bookPDF (PDF - 5.84MB) | The complete bookePub (ePub - 1.04MB) | Feedback

Unified CCX historical reporting management

The following sections describe how to manage the Unified CCX Historical Datastore to accommodate historical reporting.

Unified CCX Historical Datastore

In a Unified CCX Cluster, there can be one or more Historical datastores.


Note


Support for High Availability and remote servers is available only in multiple-server deployments.


The Historical Unified CCX Datastore can be co-located only on the server with the Unified CCX Engine.


Note


For more information about Historical datastore, see Cisco Unified Contact Center Express Serviceability Guide.


Historical reporting configuration


Note


Verify that the Number of HR Session Licenses field is updated to reflect the licensed value. This value cannot be greater than the number of licensed Unified CCX seats. The default value is 0 for Unified CCX (Standard, Enhanced, and Premium), and 5 for Unified IP IVR.



Caution


If this value remains at 0 (default), you may encounter a licensing error and you cannot login to the Historical Reporting Client.


The Unified CCX Historical Reporting subsystem provides you with a way to set up and manage the purging of the Historical Reporting databases.

Setting up Unified CCX for Historical Reporting consists of the following tasks:

  1. Database server configuration
  2. Configure automatic purging

Configure database server limits

To limit the performance impact of historical reporting on a particular Unified CCX server, you can configure a maximum number of five client/scheduler database connections per server.

To do so, complete the following steps:

Procedure
    Step 1   From the Unified CCX Administration menu bar, choose Tools > Historical Reporting > Database Server Configuration.
    The Database Server Configuration web page opens with the following fields:

    Field

    Description

    Server Name

    The host name or IP Address of the database server.

    Maximum DB Connections for Report Clients Sessions

    The maximum number of client and scheduler connections that can access the Historical Reports Database server.

    There is a limit of instances for the reporting client sessions and the scheduler sessions based on the load that can be run on each server. The following are the limits:
    • Standalone Setup—1 to 8 instances
    • High Availability Setup—1 to 16 instances
    Step 2   Enter a value in the Maximum DB Connections for Report Client Sessions field next to a Server Name.
    Step 3   Click Update.

    The configuration changes take effect.


    View historical reports

    You can view historical reports through the Historical Reporting client or Unified Intelligence Center.

    Procedure
    Choose Tools > User Management > Reporting Capability View

    The User Configuration web page opens.


    Purge of historical data

    As the Unified CCX Engine runs, it collects information about the status and performance of the Unified CCX system. Historical information is stored in a database that can then be accessed to provide reports (see the Cisco Unified CCX Historical Reports User Guide for more information about Unified CCX Historical Reports).

    When the database approaches its maximum size, some or all of the data in it must be removed. Removing data from a database is called purging.

    When the system purges data, it removes data from the db_cra database. It determines what information to purge based on the number of months you specify and on the current date. For example, if you instruct the system to purge data older than 12 months, a purge on January 15 will purge data older than January 15 of the previous year.


    Note


    When you purge data, you permanently delete it. If you want to keep data that will be purged, back up the database.


    Unified CCX Administration provides the following features for purging historical reports from the database:

    • Daily comparison of the size of the database to a user-specified maximum size
    • User-specified time at which the system purges data
    • Automatic purging of the database when it exceeds the user-specified maximum sizes
    • Automatic purging of the database based on user-specified parameters
    • Manual purging of the database

    Configure automatic purging

    The Unified CCX Engine performs automatic purging each day at a preset time.

    To help keep your system running most efficiently, schedule automatic purging to run when your system is least busy. By default, daily purges are scheduled to run at 12:00 a.m. (00:00 Hrs), but you can change this time.

    The system bases its purging activities on a variety of parameters. You can change the default value for any parameter as needed.

    The following section contains the procedure for setting the daily purge schedule and auto purge.

    Configure purge schedule configuration parameters

    You can change the time of day that the system assesses the need to purge data and the age of data to purge.

    When data is purged, the Unified CCX sends a "Database purged" message. This message announces that a purge has taken place and includes an explanation of the purging activity. If the database is approaching its maximum size, then the Unified CCX sends the following message - "Database approaching maximum size".

    The system can send notifications through the following two methods:

    • Syslog (system log)
    • SNMP traps

    To set the purge schedule configuration parameters, complete the following steps.

    Procedure
      Step 1   From the Unified CCX Administration menu bar, choose Tools > Historical Reporting > Purge Schedule Configuration.

      The Purge Schedule Configuration area opens. The following fields are displayed in the Purge Schedule Configuration area.

      Field

      Description

      Purge Schedule

      Daily purge at

      Time of day for the daily purge along with the time zone. The time that appears here is based on the primary time zone, which is specified during initial setup of Unified CCX Administration.

      In a High Availability over WAN deployment, the purge schedule will happen at the time zone of the primary node.

      Purge data older than

      Data can persist for a number of months before being purged..

      Auto Purge Configuration

       

      Initiate automatic purge when database exceeds

      Percentage of the maximum database size at which an automatic purge is initiated (as compared to the total available size).

      Auto purge data for the oldest

      Age of data to be purged.

      Step 2   From the drop-down list in the Daily purge at field, choose a time of day at which the system determines if purging is necessary.
      Step 3   From the drop-down list in the Purge data older than field, choose the required number of months.

      If the system determines that purging is necessary, it will purge both databases of data that is older than the number of months specified in this field.

      Step 4   From the drop-down list in the Initiate automatic purge when database size exceeds field, accept the default, or choose another number.
      Step 5   From the drop-down menu in the Auto purge data for the oldest field, accept the default of 15, or choose another number.
      Step 6   Click Update icon that displays in the tool bar in the upper, left corner of the window or the Update button that displays at the bottom of the window.

      The new purge schedule configuration is added to the Unified CCX system.


      Purge manually

      You can manually purge the databases at any time. This action will not affect the automatic purging schedule.


      Note


      Support for High Availability is available only in multiple-server deployments.


      To manually purge historical data, complete the following steps.

      Procedure
        Step 1   From the Unified CCX Administration menu bar, choose Tools > Historical Reporting > Purge Now.

        The Purge Now web page opens. The Purge data older than field is displayed in the Purge Now web page. You can specify this field in months and days.

        Step 2   From the drop-down list in the Purge data older than N months field, keep the default (13 months) or specify the required number of months.

        If the system determines that purging is necessary, it will purge both databases of data that is older than the number of months specified in this field.

        The Initiate automatic purge when database exceeds field displays the current historical database size as compared to the total available size.

        Step 3   From the drop-down list in the Purge data older than N days field, keep the default (15 days) or specify the required number of days.

        If the system determines that purging is necessary, it will purge both databases of data that is older than the number of days specified in this field.

        Step 4   Click Purge Now.

        The database purge is initiated in the server and the Purge Now area refreshes.


        File Restore

        Use the File Restore menu option to restore the database records written to HR files when the database goes down.

        Related Tasks