Release Number | AIX | Linux | Solaris | Windows |
---|---|---|---|---|
8.5.000.07 [12/23/14] – Hot Fix | X | X | X | X |
8.5.000.06 [08/18/14] – Hot Fix | X | X | X | X |
8.5.000.04 [05/16/14] – Hot Fix | X | X | X | X |
8.5.000.02 [03/25/14] – General | X | X | X | X |
This release note applies to all 8.5 releases of License Reporting Manager (LRM).
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.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
Note: LRM 8.5 can no longer be integrated with Configuration Server 8.5.101.00 and higher. Refer to the Technical Advisory for more information.
This release includes the following correction or modification:
LRM now works correctly with a Configuration Server that has a Language Pack installed. Previously in this scenario, LRM was sometimes unable to import the license file correctly. (LRM-509)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This section describes new features that were introduced in this release of License Resource Manager:
LRM is now able to correctly handle a license file with uncounted
as the number of licenses, by treating it as having a value of 9,999,999
.
This release also includes the following correction or modification:
LRM is now able to properly import the license file when running on a system with a non-English locale. Previously in this scenario, LRM was unable to import the license file. (LRM-503)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
LRM now correctly recognizes permanent licenses. (LRM-499)
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-498)
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-497)
After you upgrade the database schema in Oracle or Microsoft SQL Server, LRM now works correctly with a replicated database containing pre-existing data.
upgrade_db_to_schema_8.5.sql
script is
installed in <LRM INSTALL DIR>/sql/oracle/
.upgrade_db_to_8.5.000.03.sql
script
is installed in <LRM INSTALL DIR>/sql/mssql/
.Previously, if the LRM database was replicated and another LRM instance connected to the replicated LRM database using a different database name, LRM sometimes did 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 different JDBC connection information.
(LRM-496)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in the 8.5 release of License Reporting Manager.
Refer to the License Reporting Manager 8.5.x Deployment Procedure to deploy the installation package within your environment.
This release contains the following new features and functionality:
Entitlement Data Automation—LRM uses the product information from the FlexNet Publisher license file to create and update LRM entitlement data.
Packaging—LRM and ICON are both included in the CIM Platform (ICON provides data required for LRM reporting).
Database Support—LRM adds database support for IBM DB2 Enterprise Server Edition 9.7, Microsoft SQL Server 2012, and Oracle 12c and 12c RAC.
Operating System Support—LRM adds support for IBM AIX 7.1 (64-bit), Solaris 10, and Windows Server 2012 (64-bit).
There are no corrections or modifications for this release.
This section provides the latest information on known issues and recommendations associated with this product.
For Agent Group and Place Group reports, LRM might incorrectly report a non-zero value of enabled seats for the following sellable items:
Genesys CIM Platform - MS
if the site is defined as
Single-SiteGenesys CIM Platform - SS
if the site is defined as
Multi-Site(LRM-386)
Found In: 8.1.100.26 | Fixed In: |
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: |
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 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:
0,
if the record date is the earliest for this sellable
item.For example, if there are three records for a sellable item in the
LRM_PROVISIONED_COUNT
table with the following effective dates
and values:
2011-02-25=444
2012-01-31=111
2012-05-31=222
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 GMT 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 must be stopped and restarted. (LRM-201, ER# 281121170)
Found In: 8.0.000.23 | Fixed In: |
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: |
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.
Integration with Configuration Server 8.5.101.00 or later is discontinued.
Discontinued As Of: 8.5.x |
Information in this section is included for international customers.
LRM does not support internationalization.
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.5 Deployment Guide first.
License Reporting Manager 8.5 Deployment Guide introduces License Reporting Manager and describes the interrelationships with other Genesys components; describes how to configure and install License Reporting Manager; and explains how to start and stop License Reporting Manager.
License Reporting Manager 8.5 Physical Data Model for an IBM DB2 Database describes the database tables that make up the License Reporting Manager schemas.
License Reporting Manager 8.5 Physical Data Model for a Microsoft SQL Database describes the database tables that make up the License Reporting Manager schemas.
License Reporting Manager 8.5 Physical Data Model for an Oracle Database describes the database tables that make up the License Reporting Manager schemas.
License Reporting Manager 8.5 Physical Data Model for a PostgreSQL Database describes the database tables that make up the License Reporting Manager schemas.
GAX Online Help contains instructions for using the GAX interface to generate reports.
The Framework 8.5 Combined Log Events Help contains a section which describes the log messages that License Reporting Manager and its procedures generate.
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.