Release Note

License Reporting Manager

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2012–2014

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
8.1.200.06 [04/24/14] – Hot Fix     X     X
8.1.200.05 [10/30/13] – Hot Fix     X     X
8.1.200.04 [08/16/13] – General (Under Shipping Control)     X     X
8.1.100.28 [05/24/13] – Hot Fix     X     X
8.1.100.26 [03/26/13] – General (Under Shipping Control)     X     X
8.1.000.28 [08/16/12] – Hot Fix     X      
8.1.000.26 [06/25/12] – Hot Fix     X      
8.1.000.23 [04/25/12] – Hot Fix     X      
8.1.000.22 [04/03/12] – General (Under Shipping Control)     X      

Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.

This release note applies to all 8.1 releases of License Reporting Manager (LRM).

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Customer Care representative if you have any questions.


Release Number 8.1.200.06 [04/24/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In High Availability (HA) deployments, LRM now correctly starts the backup instance of LRM as Secondary. Previously in some scenarios, both instances of LRM started as Primary. (LRM-493)


LRM now correctly masks the database passwords in the log files. Previously when logging in debug mode, LRM wrote the database password in plain text in the log file. (LRM-492)


By upgrading the database schema in Oracle or Microsoft SQL Server, LRM can now work correctly with a replicated database containing preexisting data.

Previously, if the LRM database was replicated and another LRM instance connected to the replicated LRM database using a different database name, LRM could not work correctly.

Note: Only Oracle and Microsoft SQL databases can be upgraded to the new database schema, which supports using a replicated database with a different JDBC connection information.

(LRM-491)


Top of Page


Release Number 8.1.200.05 [10/30/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


LRM now correctly calculates the peak concurrent seat value for the sellable item Genesys Outbound Contact - Multi-Site. Previously, LRM might calculate an incorrect value. (LRM-449)


Top of Page


Release Number 8.1.200.04 [08/16/13] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of License Reporting Manager.

Refer to the License Reporting Manager 8.1.x Deployment Procedure to deploy the installation package within your environment.

This release contains the following new features and functionality:

Corrections and Modifications

There are no corrections or modifications for this release.

Top of Page


Release Number 8.1.100.28 [05/24/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


You can now successfully install LRM by using the Genesys Administrator Deployment Wizard. Previously in this scenario, the installation failed due to a format error in the LRM Template File. (LRM-392)


SQL*Plus and SQL Developer can now execute the upgrade810to811.sql script to upgrade the Oracle database from release 8.1.0 to 8.1.1. Previously, only SQL Developer could successfully execute the script. (LRM-391)


LRM now deletes data from its temporary tables after the automated nightly process. Previously, LRM might not truncate the LRM_LOGIN_SESSION and LRM_SESSION_ENDPOINT tables. (LRM-390)


Top of Page


Release Number 8.1.100.26 [03/26/13] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of License Reporting Manager.

Refer to the License Reporting Manager 8.1.x Deployment Procedure to deploy the installation package within your environment.

This release contains the following new features and functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


LRM now supports authentication to access the GVP Reporting Server. Previously, LRM did not support this authentication. (ER# 304730151)


LRM can now be configured to count the number of enabled seats by looking at objects configured in the Configuration Server and count the number of these objects. (ER# 297113581)


The lrm-network-switch configuration option is now updated in the "LRM Configuration Options" section in the License Reporting Manager 8.1 Deployment Guide.

lrm-network-switch
Default Value: false
Valid Value: false or true
Changes Take Effect: After restart
Specifies the presence of the network switch under LRM.

(ER# 258387823)


Entitlement and Bundle data is now stored only on the Configuration Server. Previously, LRM might not successfully import the data to its database. (ER# 257318223, 257260343)


LRM no longer requires the use of the lrm_init_db.sh initialization script. Previously, running the script might return errors. (ER# 246943821)


Top of Page


Release Number 8.1.000.28 [08/15/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


The aggregation procedure and the algorithm for extracting gap related data from ICON are now updated to prevent duplicate records in the LRM database. Previously, LRM might add a record to the LRM database, even if the record already existed. (ER# 305350633)


Top of Page


Release Number 8.1.000.26 [06/25/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


The algorithm for extracting gap related data from ICON and the aggregation procedure are now updated to prevent duplicate records in the LRM database.

Note: LRM might create duplicate records in the LRM_CONCSEAT_A_GAP table in the system LRM database if two or more ICON instances monitor the same switch and tenant, and if LRM obtains data from all those ICON instances.

(ER# 301608281)


Top of Page


Release Number 8.1.000.23 [04/25/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


LRM now successfully extracts purchased usage quantities for tenants after such data is entered or changed in Genesys Administrator Extension. (ER# 298612137)


Top of Page


Release Number 8.1.000.22 [04/03/12] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in the initial 8.1 release of License Reporting Manager.

Note: LRM was previously available as a Restricted 8.0.x release.

Refer to the License Reporting Manager 8.1.x Deployment Procedure to deploy the installation package within your environment.

This release contains the following new features and functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


LRM no longer produces the wrong report for the specified date when the connection between LRM and Configuration Server Proxy/Configuration Server Proxy backup is lost and re-established several times during the import of configuration data into the LRM database. Previously, this issue appeared on very rare instances. (ER# 281410671)


The IDX_LRM_SWITCH index for the LRM_SWITCH_TYPE table is no longer dropped and not recreated when you run the 03m_i_lrm_idb_create_db_oracle.sql script. (ER# 273657241)


The command for importing Entitlement and Bundle files to Configuration Server now works correctly (import-ent-to-cfg and import-bundle-to-cfg). Previously, as a workaround, the commands to import files into the LRM database were used (import-ent-to-db and import-bundle-to-db). (ER# 253678053)


While running an initialization script for the local LRM database, or running it a second time for the system LRM database, errors related to the G_LOG_* tables no longer occur. (ER# 252715392)


Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


LRM cannot provide authentication to access the GVP Reporting Server. If an administrator configured the GVP Reporting Server to require authentication, LRM HTTP requests to the GVP Reporting Server fail and LRM cannot access GVP reports. To use LRM with the GVP Reporting Server, an administrator must configure the GVP Reporting Server to not require authentication. (ER# 304730151)

Found In: 8.1.000.22 Fixed In: 8.1.100.26

LRM takes the list of required tenants for calculation of non-GVP-related metrics from the LRM Application's Tenant tab and the list of required tenants for calculation of GVP-related metrics from the Genesys Voice Platform Reporting Server Application. To be consistent, both lists of tenants should be the same. (LRM-262, ER# 297166227)

Found In: 8.1.000.22 Fixed In: 

LRM does not support the "enabled seats" license type. (ER# 297113581)

Found In: 8.1.000.22 Fixed In: 8.1.100.26

You can not use the recalculation process previously described in the License Reporting Manager 8.1 User's Guide. It might damage the integrity of internal data and cause incorrect final report data in the report file. To obtain a workaround, please contact Genesys Customer Care. (LRM-256, ER# 296883056)

Found In: 8.1.000.22 Fixed In: 

A substantial amount of time might elapse between the beginning of a switchover of the Genesys Voice Platform Reporting Server primary and backup servers and the end of the switchover. If LRM is running during that time it produces an empty report. Workaround: Do not run LRM during that period of time. (LRM-252, ER# 296845187)

Found In: 8.1.000.22 Fixed In: 

To stop calculation of Provisioned Counts values for a specified sellable item, create a new option in the Genesys Administrator Extension or the lrm-provisioned-counts object in the Configuration Layer, with the date equal to the date from which the calculation should be stopped, and set the purchased license quantity to 0. If there are records for that sellable item in the LRM_PROVISIONED_COUNT table with a date later than the date on which calculations should stop, their purchased license quantities should also be set to 0 by using the procedure above.

Note: Removing the provisioned counts option from the Genesys Administrator Extension interface or the Configuration Layer does not remove the record from the LRM_PROVISIONED_COUNT table if any LRM calculation was performed after the option was created. (LRM-250, ER# 296774860)

Found In: 8.1.000.22 Fixed In: 

When a Configuration Server Proxy (CS Proxy) switchover between primary and backup occurs after CS Proxy has been stopped and restarted, LRM sometimes is unable to restore its connection to CS Proxy and freezes. If this occurs, restart LRM. (LRM-247, ER# 296769728)

Found In: 8.1.000.22 Fixed In: 

To exclude a specified historical record for a sellable item in the LRM_PROVISIONED_COUNT table from further calculation, create a new option in the lrm-provisioned-counts object in the Configuration Layer with the date equal to the date of this record and a purchased license quantity equal to one of the following values:

For example, if there are three records for a sellable item in the LRM_PROVISIONED_COUNT table with the following effective dates and values:

To exclude the second record from the calculations, set its value to 444. (LRM-243, ER# 296238461)

Found In: 8.1.000.22 Fixed In: 

Due to a limitation in Genesys Voice Platform Reporting Server, LRM produces incorrect reports when Reporting Server is running on a host with any time zone other than the UTC time zone. (LRM-240, ER# 296194385)

Found In: 8.1.000.22 Fixed In: 

Due to a limitation in the architecture of the Genesys Voice Platform Reporting Server, LRM reports incorrect peak measurements for the system level data calculation. You should configure LRM to connect to only one Reporting Server (or one Reporting Server primary/backup pair). (LRM-239, ER# 296193819)

Found In: 8.1.000.22 Fixed In: 

Due to a limitation in the architecture of the Genesys Voice Platform Reporting Server, Reporting Server does not support a configuration using resource partitioning by tenant. As a result, LRM cannot provide correct GVP metrics for such a configuration. (LRM-236, ER# 296106671)

Found In: 8.1.000.22 Fixed In: 

If LRM is unable to establish a connection with Configuration Server Proxy after a number of unsuccessful attempts, LRM might stop responding. As a workaround, LRM's process must be stopped and restarted. (LRM-201, ER# 281121170)

Found In: 8.0.000.23 Fixed In: 

If LRM disconnects from DB Server while importing Entitlement or Bundle files to its databases, the import may not be successful for some of the LRM databases. If this happens, the import should be run once again. (ER# 257260343)

Found In: 8.0.000.23 Fixed In: 8.1.100.26

While running an initialization script for the local LRM database or the system LRM database for the first time, you may see "drop table" related errors. These errors can be ignored. (ER# 246943821)

Found In: 8.0.000.23 Fixed In: 8.1.100.26

The commands for importing Entitlement and Bundle files to Configuration Server do not work (–import-ent-to-cfg and –import-bundle-to-cfg). Instead, the commands to import files into the LRM database should be used (–import-ent-to-db and –import-bundle-to-db). (ER# 253678053)

Found In: 8.0.000.23 Fixed In: 8.1.000.22

LRM does not verify the uniqueness of a bundle ID while importing bundle descriptions. Only the first instance (bundle id) will be imported in the database. For this reason, a correctly defined bundle description must be provided. (LRM-161, ER# 257833220)

Found In: 8.0.000.23 Fixed In: 

LRM does not verify the size of a bundle name or other elements/attributes while importing bundle descriptions. When you are providing a bundle description, make sure the sizes of the bundle name and other elements/attributes do not exceed the sizes of corresponding database fields. Otherwise, the bundle is only partially imported. Refer to License Reporting Manager 8.1 Physical Data Model for Oracle for information about table field sizes. (ER# 257318223)

Found In: 8.0.000.23 Fixed In: 8.1.100.26

If you are using LRM in an environment with Network switches that are not configured in Configuration Database, keep in mind the following: In order to calculate the statistics for a Network switch, the lrm-network-switch configuration option must be set to true for both the LRM application with the local role and the LRM application with the system role. (ER# 258387823)

Found In: 8.0.000.23 Fixed In: 8.1.100.26

Top of Page


Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.


There are no discontinued items for this release.


Top of Page


Internationalization

Information in this section is included for international customers.


LRM does not support internationalization.


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the License Reporting Manager 8.1 Deployment Guide first.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page