Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ InTouch HMI

Manage consumption of a different license after startup

Manage consumption of a different license after startup

  • Last UpdatedJun 17, 2024
  • 2 minute read

As part of standard upgrade and maintenance activities, different licenses can be deactivated or activated on the License Manager. If WindowMaker or WindowViewer consumes a valid license after startup time and cannot renew the license, it can consume a different license, from the one initially assigned or consumed. If this occurs, InTouch must then validate if the capabilities of the newer license is appropriate. The comparison in license capabilities between the last good license and the currently consumed licenses will determine if the WindowMaker or WindowViewer can continue running without entering the Grace Period. See Work with the Grace Period for details on how to exit the Grace Period.

The two possible scenarios for a different license being consumed after startup are described below.

Scenario 1: A less capable license is consumed after startup

In this scenario, the license consumed after startup time is of lesser capabilities than the last good license. This is considered a license downgrade, and will result in WindowMaker or WindowViewer entering the Grace Period.

A license downgrade is considered when the new license's parameters fall into the below check:

The parameter changes that will trigger the Grace Period are described below:

  • Tag Count: if the tag count is reduced, the Grace Period is triggered.

  • Window Count: if the window count is reduced, the Grace Period is triggered.

  • Runtime Timeout: if the Timeout value changes from None to any other value, Grace Period is triggered.

  • Language Lock: if the Language Lock value changes from No to Yes, or vise versa, Grace Period is triggered.

  • ReadOnly: if the ReadOnly parameter is changed from No to Yes or vise versa, Grace Period is triggered.

If a license downgrade occurs, the downgraded, or "violated" parameters display in the View License dialog box. For example, if WindowMaker originally consumed a sixty-thousand tag count license and downgraded to a three thousand tag count license, the tag count parameter would display as follows:

Important: The application will continue to run with the capabilities of the last good license. In this example, the original sixty-thousand tag count will remain when entering the Grace Period.

Scenario 2: A more capable license is consumed after startup

In this scenario, the license consumed after startup time is of greater or equal capability than the original. This is a license upgrade, and will not cause WindowMaker or WindowViewer to enter the Grace Period.

If a license upgrade occurs, all parameters in the View License dialog box are updated to display the higher capability values.

In This Topic
TitleResults for “How to create a CRG?”Also Available in