Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The information on this page refers to License Statistics v6.9 13 and newer, which introduced Custom Application monitoring, and now offers License Harvesting as an optional add-on to Custom Application monitoring.

Tip

Contact us to enable License Harvesting for your License Statistics license. If you're an existing customer you'll get a 2-month free trial period to check it out!

License Harvesting is a separately purchased License Statistics add-on, currently available only with the new licensing model and only for Windows installations of License Statistics.

When users neglect to log out of applications they’re not actively using, other users cannot access the blocked licenses. License Harvesting monitors your users and applications for idle licenses and automatically releases those licenses to be available for others, cutting down on underutilized licenses and associated costs.

License Harvesting uses License Statistics Agent, installed on the end-user host, to monitor whether a configured application is actively used. When an idle state is detected, License Harvesting releases the license automatically using one or more methods, such as asking the user to close the application or closing it automatically, depending on configuration. 

Normally, License Harvesting is used to monitor applications that are licensed using network, token or pay-per-use licensing models, but can be used for any application that you want to prevent from running outside of predefined hours or being idle for a predetermined length of time on the host machine.


Info

The Custom Applications feature is available only with Licensing Model 2019.

The Custom Applications feature lets you configure applications to be monitored by License Statistics Agents, as described in Setting up Custom Applications

After configuring a custom application for monitoring:

  • All Agents that belong to the assigned Agent Groups will start monitoring the application with the specified executable name.
  • When a user starts the configured application on any end-user host, the assigned Agents will start gathering information about its usage (time, duration, number of instances, username, host, etc.).
  • All of the collected data is periodically sent to the License Statistics server. 
  • Upon the first delivery of data to License Statistics, the license server retrieves the vendor name, and a feature with the name of the application is created.

The data that License Statistics collects can then be used for reporting statistics and/or License Harvesting. Reports will include standard statistics about the application usage, such as sessions, usage statistics, users, hosts, and number of licenses consumed (number of application instances opened).

Currently, each application requires one license server to be used. A single Agent can monitor multiple applications.

License Harvesting

You can optionally enable You must set up License Harvesting for the applications you want to monitor . After configuring applications to use License Harvesting, the Agents periodically connect to the License Statistics server to obtain the most current configuration information. It may take up to 1 minute to update the configuration on the Agents. If connection to the server is lost, the Agents will continue to operate with the last received configuration until the connection is reestablished.Image Removedwhen setting up Custom Applications. See License Harvesting for more information.

Session Tracking

License Statistics handles session tracking for Custom Application monitoring as described below.

  • Single processes are identified using a process ID (PID)
  • If there is no process for a monitored application, then no session is reported for Custom Application monitoring
  • If there is a single process instance on the host for a monitored application, a single session with a single license used will be reported for Custom Application monitoring, as shown in the following illustration:

    Image Added


  • If there are multiple process instances (with different PIDs), multiple sessions will be reported for Custom Application monitoring, with each using a single license, as shown in the following illustration: 

    Image Added