Jump to: navigation, search

Deploying LRM

<multistep> |-| LRM Deployment Overview= Use this overview of the deployment to serve as a License Reporting Manager (LRM) deployment quick reference. Select a link for more information or click Next Step to view details of each step. The browser back button is not supported on this page.

  1. Confirm platform support.
  2. Confirm installation requirements.
  3. Install GAX.
  4. Install the LRM Plug-in for GAX and add the LRM application to the Connections list for GAX.
  5. Import the LRM application template.
  6. Create a LRM DB and add a DAP.
  7. Create and configure the LRM application.
  8. Install LRM.
  9. Create the Entitlement File.
  10. Set the timezone to GMT on the LRM server and the GVP Reporting Server.
  11. Schedule the statistics gathering job.
  12. Plan data backup.
  13. Configure LRM High Availability (Optional).
  14. Enable Secure Connection Features (Optional).
  15. Configure Interaction Concentrator (ICON) and Interaction Workspace options.
  16. Install ICON.
  17. Add a DAP object for each ICON DB.
  18. Create a cron job to clean up old ICON data.
  19. Configure GVP Reporting Server for LRM.
  20. Start LRM.

|-| Confirm platform support= The Platforms Supported by LRM table lists the operating systems, databases, and virtualization that are supported by LRM in this release.

Platforms Supported by LRM

Platform category

Platform

Versions

OS Red Hat Linux
  • 5.0 (32-bit)
  • 5.0 (64-bit)
  • 6.0 (64-bit)
OS Windows 2008 64-bit
Database MS SQL Server 2008
Database Oracle
  • 11g
  • 11g RAC
Database PostgreSQL 9.0
Virtualization VMware ESX 3.5

|-| Confirm installation requirements=

  • Confirm hardware sizing and performance information in the Genesys Hardware Sizing Guide.
  • Confirm you are using:
    • Customer Interaction Management 8.x or Management Framework 8.x
    • Genesys Interaction Concentrator 8.x
    • Genesys Voice Platform Reporting Server 8.1.5 or later
    • Sun Java Runtime Environment (JRE) 6.0 Update 19 or later

LRM Architecture

LRM Arc 850.png

Any additional functionality not shown in the above diagram is designed to support ease of installation.

|-| Install GAX= Genesys recommends you install GAX release 8.1.0 or later. See the GAX Deployment Guide available on the Genesys Administrator page.

|-| Install LRM Plug-in for GAX= The LRM Plug-in for GAX is an add-on component that is hosted by an existing Genesys Administrator Extension (GAX) installation. The LRM Plug-in for GAX accesses data from the LRM database to provide on-demand reporting to Service Providers and tenant administrators in the GAX graphical user interface (GUI) application .

  1. Install the LRM plug-in files into the existing GAX directories to enable report generation of LRM statistics from GAX. See Installing a GAX compatible plug-in for details.
  2. In Configuration Manager, add the LRM Application object on the Connection tab of the GAX object.

Notes: Refer to GAX online help for

  • Report Generation – System Reports, Tenant reports, Agent and Place Group reports
  • Provisioning
  • Bundle upload
  • Viewing Entitlements

|-| Import the LRM application template= To import the required application templates before you configure License Reporting Manager to work in your Genesys environment. Configuration Manager or Genesys Administrator can be used for this and all other procedures that are related to configuration.

  1. Open the Environment folder and select the Application Templates folder.
  2. From the File menu, select Import Application Template.
  3. In the Open window that appears, import the following template from your CD:
    • templates/License_Reporting_Manager_812.apd.
  4. Click Open. The Properties window opens.
  5. Click OK. The template is imported into the Application Templates folder.

|-| Create a LRM DB and add a DAP=

  1. Create your LRM database.
  2. Configure the DAP object on the General tab as a JDBC connection with the correct database server credentials for the DAP object.
  3. Set the role configuration option in the [lrm] section to main.

    Exactly one of your DAPs must have the role value set to main for the LRM DAP. At least one of your DAPs must have the role value set to icon.
Tip
You do not need to run any SQL scripts create empty tables for LRM. LRM creates the tables automatically when the nightly job runs for the first time.

|-| Create and configure the LRM application=

  1. Open the Environment folder and select the Applications folder.
  2. From the File menu, select New > Application. The Browse window opens, listing all application templates that are present in the Configuration Database.
  3. Choose the License Reporting Manager application template.
  4. Click OK. The Properties window appears.
  5. On the General tab, add a unique name to the Name field for this instance of LRM.
  6. Select the Server Info tab. In the Host Name field, add the name of the host on which you are installing the application.
  7. Select the Start Info tab, and add “...” to each of the following fields:
    • Working Directory
    • Command Line

      These fields are automatically filled with the correct information when LRM is installed.
  8. Select the Connections tab. Right-click and select New. In the Server field, enter the name of each DAP. Add:
    • A DAP for the LRM database. Set the value of role to main in the DAP Application.
  9. Click OK. Configuration of your LRM instance is complete.

|-| Install LRM=

[+] Install LRM on Linux

[+] Install LRM on Windows

|-| Create the Entitlement File= The entitlement file provides the reference entitled quantity on customer usage reports, provides the reference for calculating overuse, and adds the overuse flag to LRM reports. LRM uses the entitlement file as a reporting reference for a current list of valid customer-ordered sellable items. It does not control or restrict product use. For more information, see the Entitlement File overview on What is LRM?.

Creating an entitlement file using a template

Create a specific customer’s entitlement file using the templates provided in this procedure, which include all of the available LRM sellable items.

To create the entitlement file:

  1. Select the template below according to the customer’s license type:

    [+] Concurrent seat entitlement file template

  2. Copy and paste the entire entitlement file template into an xml editor.
  3. For the general and customer information, fill in the items following the format shown as highlighted in the samples below.
    • For customer_site_type, enter either SS or MS (single-site or multi-site, by means of the CIM Platform sellable).
    • For id, create a new unique id by incrementing the value id by one for each new entitlement file. For example, set the value of id to 2 for the second version of the entitlement file.

    [+] General and customer information sample code

  4. For each product the customer has purchased, fill in the quantity purchased as highlighted in the sample below for each sellable item (each sellable item section starts with <entitlement_data item= and ends with </entitlement_data> from the customer’s order information). The remaining fields do not need to be changed in the sellable item section.

    5. [+] Concurrent seat sample code

  5. Delete all sellable item sections that the customer does not use or has not purchased.
  6. Save the file as type .xml. This should be the complete entitlement file.
  7. To upload the Entitlement file to the Configuration Server using the GAX interface, select Configuration > Entitlements.

    Once the file is uploaded, LRM creates a transaction object on the Configuration Server under Environment > Transactions > lrm-entitlement-<random id>, where the random id is an autogenerated string (for example, 19a048ecb6fde21746d6ee25643059621).

Example of an entitlement file

[+] Example of an entitlement file

|-| Set the timezone to GMT= You must configure LRM server and GVP Reporting Server to use the GMT timezone, because LRM uses the GMT time zone to keep track of the days in the system.

|-| Schedule the statistics gathering job= Schedule the nightly statistics gathering job to run at the time each day when there is a low volume of interactions in the contact center (for example, at night).

Set the schedule option in the [lrm] section to an appropriate value for your contact center. The default value is 01:00 (1am GMT).

|-| Plan data backup= It is important to regularly backup the data in your License Reporting Manager database to prevent data loss. Backup of the LRM database is the responsibility of the Database Administrator. The following LRM tables can be backed up using the tools in your particular RDBMS:
   LRM_CONCURRENT_SEAT
   LRM_ENABLED_SEAT
   LRM_CONCURRENT_GROUP_USAGE
   LRM_ENABLED_GROUP_DETAILS
   LRM_ENABLED_GROUP_SUMMARY
   LRM_JOURNAL

|-| Configure LRM High Availability (Optional)=

You can set up LRM as a pair of primary-backup applications. Both applications must be installed, configured, and started. If both of these applications are up and running, the Solution Control Server determines which of the applications act as the Primary, while the other acts as the backup.

To configure the system, the system administrator must:

  1. Install and configure two separate instances of LRM.
  2. Select the Server Info tab in the Application object for the primary LRM application.
  3. Click the open folder icon next to the Backup Server field to choose the LRM application which is to serve as the backup.

|-| Enable Secure Connection Features (Optional)=

You can secure connections from LRM to Configuration Server. All of the security features are optional.

  1. Enable Transport Layer Security (TLS) protocol.
    1. UNIX only: Install the Genesys Security Pack on the LRM server host, and set the applicable environment variable to specify the path to the Security Pack libraries. See "Security Pack Installation" in the Genesys 8.1 Security Deployment Guide.
    2. Create and install certificates on the LRM server host and Configuration Server host. See "Certificate Generation and Installation" in the Genesys 8.1 Security Deployment Guide.
    3. If required, change the configurations of the Configuration Server applications:
      • Add a new port for secure connections. On the Configuration Server Application object, select the Auto Detect mode.
      • Use a host certificate.
        See "Genesys TLS Configuration" in the Genesys 8.1 Security Deployment Guide.
    4. On the LRM Application object, add connections to Configuration Server. When you add the connection(s), you must use the port that you created in the previous step.
  2. Enable client-side port definition.
    1. When you install LRM, select the connection parameters that LRM will use for the initial connection to Configuration Server. See "Client-Side Port Definition" in the Genesys 8.1 Security Deployment Guide.
    2. In the LRM Application object, add or modify the connection to Configuration Server, to specify the connection parameters (port number and, optionally, IP address) that LRM uses to reconnect to Configuration Server after a switchover or disconnection. Configure the parameters in the Transport Protocol Parameters text box on the Advanced tab of the connection properties. See "Client-Side Port Definition" in the Genesys 8.1 Security Deployment Guide.
  3. Enable the SSL protocol on the JDBC connections between LRM and its source and target databases. When you configure the extraction DAP(s) and the LRM DAP, use the jdbc-url option to specify the URL information as required by your RDBMS to implement JDBC over SSL.

|-| Configure ICON and Interaction Workspace options= In order for LRM to calculate statistics it is important that certain Interaction Concentrator and Interaction Workspace options be set correctly.

callconcentrator Section

  1. [role]—This option specifies the type of data that the Interaction Concentrator instance processes and stores in the Interaction Concentrator database.

    For Interaction Concentrator release 8.1 and later, the ICON instance can be configured to store your LRM-specific data. You must set the role option to lrm. Do not combine the lrm role with any other in the same instance of ICON.

    See the Interaction Concentrator 8.1 Deployment Guide for more information about using ICON for License Reporting Data.
  2. [use-dss-monitor]—This option must be used with LRM for the usage data gap processing. Set this option to 1 to populate the G_DSS_GLS_PROVIDER and G_DSS_GOS_PROVIDER tables with Interaction Concentrator release 8.0.000.25 or later.

    See the Interaction Concentrator 8.1 Deployment Guide for more information on the use-dss-monitor option.
  3. [dss-no-data-tout]— This option must be used with LRM for the usage data gap processing. Set this option to the preferred value. This option enables you to set the time interval after which Interaction Concentrator provides the NoData indication in the G_DSS_GLS_PROVIDER and G_DSS_GOS_PROVIDER tables. The NoData indication enables you to distinguish cases in which there was no data from those in which a connection problem prevented the data from being properly recorded.

    See the Interaction Concentrator 8.1 Deployment Guide for the default and valid values for the dss-no-data-tout option.

filter-data Section

Make sure that the gls data options are set to their default values (equal to 0).

  • [gls-all]
  • [gls-ivr]
  • [gls-no-person]
  • [gls-queue]

See the Interaction Concentrator 8.1 Deployment Guide for the full description of the filter-data options.

interaction-workspace Section

  • [license.lrm-enabled]—This option must be added and set to true to enable Interaction Workspace to support LRM. This feature might not work if Interaction Workspace is customized. Changes take effect after you restart Interaction Workspace.

|-| Install ICON= Install ICON and create a database for ICON if necessary. See the ICON Deployment Guide on the Interaction Concentrator page

Important
You can reuse ICON from other parts of your deployment.

|-| Add a DAP object for ICON=

To configure the LRM solution properly, you must define Database Access Point (DAP)objects that describe the databases to which LRM has access. Create a DAP object for each ICON to which you connect, and you cannot reuse the corresponding DAP object already in use by ICON, because LRM uses the JDBC options to configure the connection to the databases. The LRM application extracts data from these ICON databases used to prepare the reporting data.

  1. Configure the DAP object on the General tab as a JDBC connection with the correct database server credentials for the DAP object.
  2. Set the role configuration option in the [lrm] section to icon.
Important
Exactly one of your DAPs must have the role value set to main for the LRM DAP. At least one of your DAPs must have the role value set to icon.

|-| Create a cron job to clean up old ICON data=

Create a cron job to clean up old ICON data by using the DB purge script. See the ICON User's Guide on the Interaction Concentrator page for details.

|-| Configure GVP Reporting Server for LRM=

Important
  • Historical reporting must be enabled on the GVP Reporting Server for LRM and GVP to work together. To enable historical reporting on GVP Reporting Server, do not run GVP Reporting Server in nodb mode; that is, set the [persistence] rs.nodb.enabled option to false (the default value).
  • GVP Reporting Server must be running for LRM to collect data.
  1. Select the Connections tab. Right-click and select New. In the Server field, enter the name of the GVP Reporting Server. LRM uses the preliminary GVP data and might have an instance of GVP Reporting Server on the Connections tab. The LRM application must connect to the configured GVP Reporting Server that transfers GVP data to the LRM database. If your GVP Reporting Server is set up as an HA pair, add only the primary instance and not the backup GVP Reporting Server.

|-| Start LRM=

When the installation of License Reporting Manager (LRM) is verified, and the LRM databases have been initialized, you can start LRM by using Genesys Administrator.

  1. Select Operations > Applications > <LRM Application>.
  2. Right click on the LRM application name and select Start applications.


|-| </multistep>

This page was last edited on April 7, 2015, at 16:14.
Comments or questions about this documentation? Contact us for support!