Licenses

This whole page is updated.

Note: LRM has changed in 8.5 to create the entitlement file itself, and to be installed as a normal application (and therefore after CS and GA/GAX have been installed and are running).

Genesys Framework uses the Genesys License Reporting Manager (LRM) to manage application licensing, including maintaining usage data for licensed Genesys products and user-defined bundles. This data is used to provide Genesys users with license management reports, and Hosted Service Providers with billing data.

License Resource Manager

For a new deployment of Genesys Framework, LRM must be installed after Configuration Server and Genesys Administrator are installed. LRM then creates an Entitlement File that contains information about available and used licenses. Configuration Server uploads the license information into the Configuration Database. Additional applications can then be deployed, based on the validity of their licenses.

The License Resource Manager (LRM) Server connects only to the master Configuration Server running in primary mode.

Tip

Genesys strongly recommends that you start LRM before you install a backup Configuration Server. If you start LRM afterwards, restart the backup Configuration Server to avoid a period of downtime for clients of Configuration Server, other than LRM, when Configuration Server switchover occurs.

When the first LRM instance is connected (or reconnected) to this Configuration Server instance (that is enabled for LRM monitoring), Configuration Server generates the log event 21-25100 LRM Server connected successfully, system operating normally.

A connection between LRM Server and Configuration Server is not required for Configuration Server to accept connections from other Genesys Framework components. However, if Configuration Server is running on a new (or upgraded) database and is only in the first startup stage (LRM has not started yet), it will not accept a connection from any Genesys Business Application.

At initial startup only, when a Genesys Business Application tries to connect to Configuration Server and Configuration Server cannot validate the presence of LRM, Configuration Server generates log event 21-25101 Unable to accept connection: LRM Server has not been started. and refuses the connection request. After LRM has been detected at least once, connections are no longer refused because of this reason.

If the connection to the LRM Server is lost, Configuration Server generates log event 21-25102 LRM Server has disconnected. However, Configuration Server still continues to accept connections from Genesys Business Applications.

For more information about LRM, including how to install and use it, refer to LRM documentation.

Entitlement File

Framework licensing depends on a valid entitlement file that contains license information. This file is created and maintained by LRM. Configuration Server stores this information in the Configuration Database, and uses it as a sort of authentication certificate for the startup of every new deployment of Genesys Framework.

For a new deployment of Genesys Framework, LRM must be installed after Configuration Server and Genesys Administrator are installed. LRM then provides the entitlement file to Configuration Server, which uploads the license information into the database. Additional applications can then be deployed, based on the validity of their licenses.

Important

After the database is updated, it may take up to 10 minutes for the new license information to propagate to LRM and for Configuration Server to stop generating out-of-compliance log messages.

Configuration Server and LRM

At Intial Startup

After Configuration Server has started up for the first time against a new (or upgraded) database, Configuration Server is able to accept client applications of the following types:

• LRM Server
• Any other Management Framework components required to setup LRM
• Genesys Administrator and Genesys Administrator Extension
• ITC Utility (IP installer)

Attempting to start and connect any other application at this stage, before LRM has started, will result in Configuration Server generating an error and a log message 21-25101 Unable to accept connection: LRM Server has not been started..

Tip

Genesys recommends that if you want to configure a backup Configuration Server, you do so only after LRM has started.

At this point, LRM must be installed and started, after which Configuration Server uploads the Entitlement File to the Configuration Database.

Important

If the license has uploaded and Configuration Server initialized properly, the read-only option license is added automatically to the options of the Configuration Server object, in the <Configuration Server application name> section.

At Subsequent Restarts

After subsequent restarts (after LRM has started), all connections are allowed. If LRM does not connect within several minutes after the current Configuration Server switching to primary, Configuration Server will generate log message 21-25102 LRM Server has disconnected. When LRM finally reconnects, log message 21-25100 LRM Server connected successfully, system operating normally. will be generated, to clear the previous condition. Otherwise, there is no impact on Configuration Server functionality if LRM does not reconnect.

When restarting after switching from backup to primary, Configuration Server sometimes generates the log message 21-24500, Out of compliance due to invalid license file. It then reloads the Entitlement File into the Configuration Database.

It also re-uploads the entitlement file into the database when any of the following situations occur:

• Configuration Server instance restarts and initializes in primary mode (for any reason, in addition to after a switchover).
• Configuration Server is running in primary mode and one of the following is true:
  • 30 full calendar days have passed since the file was last uploaded.
  • The earlier of when validation is completed successfully, or the date on which the last validation was completed has passed.
    

Question: The second bullet is unclear - what exactly does it mean?

• Configuration Server is running in primary mode and it is discovered that the file was either uploaded to or unloaded from the system after the last validation was completed.
• Configuration Server is switched to run in primary mode, and the file was last reported as invalid.
• Configuration Server is running in primary mode with a known file status of invalid, and 60 minutes have elapsed.

Each time that Configuration Server connects to a client application, Configuration Server assigns to the client a random value for the validated license file. This value is stored by the license option in the <client server object name> section client's options of the client. It is stored as a binary value, so cannot be changed by the user. The random value is recalculated each time that Configuration Server detects that the license file has been changed. This change causes the clients application object to be updated. When the license file become invalid, the option is removed, and is restored again only if and when a valid license file is used for the connection.

For More Information

For more information about how Genesys licenses its products, refer to the ''Genesys Licensing Guide''.

For more information about LRM, refer to LRM documentation.

For more information about Genesys Log Events, refer to the Framework 8.5 Combined Log Events Help file.