Special Configuration Requirements

Configure the License Reporting Manager (LRM) Application object and other applications in the Genesys Configuration Layer, in order to make various kinds of data available in the LRM Database (LRM DB).

LRM Application and Components

Each LRM application must have his own separate LRM application instance with a unique object name, as required by Genesys Configuration Server.

Each LRM instance has a list of DAPs that point to the ICON database in its connection list. The LRM application connects to each of the DAPs in the list that have their role set to icon. The LRM application extracts data from these ICON databases used to prepare the reporting data.

LRM must also have a single DAP with role set to main in its connection list. This DAP provides the information for the database the LRM application uses to store its calculated reporting data.

Defining Database Access Point objects

To configure the LRM solution properly, you must define Database Access Point (DAP) objects that describe the databases to which LRM has access. You must 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 following types of DAP objects are used by LRM:

• One for each ICON database from which LRM should read data. The ICON DAP object must have the value of the LRM role option set to icon.
• One for the LRM database used to store the LRM reporting data. The LRM DAP object must have the value of the LRM role option set to main.

Configure both DAP objects on the General tab as a JDBC Connection with the correct database server credentials for each DAP object.

Connecting to the GVP Reporting Server

LRM connections to the Genesys Voice Platform (GVP) Reporting Server are managed on the Connections tab of the LRM application. LRM uses the preliminary GVP data and might have one or several instances of GVP Reporting Server on the Connections tab. The LRM application must connect to all configured GVP Reporting Servers that transfer GVP data to LRM database.

Loading Configuration Objects from Configuration Server

To calculate certain sellable items, LRM loads some configuration information into the database, including the following configuration objects:

• Switch—For the calculation of all sellable items
• Person, Agent Group, Place Groups—For the calculation of the Outbound Contact - MS seats sellable item.
• Person’s Skills (as a part of Person)—For the calculation of the Skill Based Routing seats sellable item.

LRM looks for specific conditions and loads information into the LRM database about the tenants to whom these conditions apply before it starts data preprocessing. The following conditions are examined in order to determine eligibility of a sellable item:

• URS with a single tenant and DAP connection for CTI seats sellable item.
• WFM Data Aggregator application with connection to Stat Server for the Workforce Management Seat sellable item.
• All SIP Server and T-Server applications to determine if they are configured as an HA pair, for the High Availability Sellable Item.
• Info Mart applications for the Genesys Info Mart Server and Genesys Interactive Insights Sellable Items.

Storing Bundle and Entitlement Data on Configuration Server

LRM requires at least one entitlement file has been uploaded to function. Bundles and entitlement XML files may be uploaded to the Configuration Server by using the GAX interface. For more information, see Entitlement File and Bundles.

High Availability configuration

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.