License behavior for Web Client sessions

The Web Client acquires its own license and this license is different from the desktop application license. It uses a session-based licensing model. A Web Client session is defined as per user per machine. The number of users or connections allowed at one time depends on the total sessions permitted by the installed licenses.

You can install multiple licenses on the same node, and their session counts are cumulative. For example, if you install two licenses that allow 50 sessions each, the system permits up to 100 concurrent sessions in total. However, if an Unlimited session license is installed on the same node as one or more limited (counted) session licenses, the Unlimited license takes priority. In this case, the system allows unlimited sessions, and the limits defined by the counted licenses will no longer apply.

License

• Feature Name: webserver

• License Type: Server license

• Parameter: clientcount

  Here,

  • If clientcount = 100,000, means there is no limit on the number of licensed sessions.

  • If clientcount is any other non-negative number, that number represents the maximum allowed session

Deprecated licenses

The following InTouch license will no longer work in 2026 release or later:

• Enterprise: spe-i-enterprise

• Workspace license: it-i-webserverflex

• Previous unlimited R/W: it-i-webclientunlimrw

• Previous unlimited R/O: it-i-webclientunlimro

• Brand neutral license: avhmi-i-ocws

The followingOMI license will no longer work in 2026 release or later:

• Previous unlimited R/W: sp-i-webclientunlimrw

License scenario comparison with previous release

InTouch Web Client license behavior changes:

OMI Web Client license behavior changes:

Single session mode

If a valid license cannot be obtained and the web server is not running in Operations Control connected experience mode, only one read/write (R/W) licensed session is permitted. In this situation, one free client session is provided with full read/write capability and no time restriction. However, if a supervisory client license is not available on the web server node, the read/write connection to the Galaxy attribute is restricted to 2 hours demo mode of the data service. There is no demo mode for Web Client. If no license is acquired, then it will switch to single session mode.

Web Client connection

When you open the InTouch or OMI web application in a web browser, it is treated as a Web Client connection.

The system checks whether the user belongs to either the Read/Write (R/W) group or the Read-Only (R/O) group. If the user does not belong to either group, an error page is displayed. If the role check passes, the session continues.

If Operations Control connected experience is configured on the browser machine:

• For InTouch web:

  • If the underlying application is an InTouch View, the system tries to obtain a Supervisory entitlement.

  • Otherwise, it tries to obtain an Edge entitlement.

• For OMI web:

  • The system tries to obtain a Supervisory entitlement.

  • If the required entitlement is successfully obtained, a session is granted based on the user’s role (R/W or R/O).

  • If the entitlement cannot be obtained, a license error page is displayed.

If Operations Control connected experience is not configured on the browser machine:

• The system checks whether a licensed session is available.

• If a session is available, it is granted based on the user’s role (R/W or R/O).

• If no session is available, a license error page is displayed.

Behavior in Operations Control connected experience

The user associated with the Operations Control connected experience account must be part of the AVEVA Web RW Users or AVEVA Web RO Users group in order gain Web Client user session. A valid entitlement is not sufficient to gain access to Web Client.

In Operations Control connected experience mode if the user has a valid entitlement, a perpetual license is not required. The web server will rely on the client to perform the license check. In this case, the Galaxy data service license requirement is bypassed.

Note: If you change the license mode or license server, restart the InTouch Web Client services for the changes to take effect. You can do this by restarting the machine or by toggling the Web Client option off and on in Application Manager.

License renewal

If a license has been successfully acquired, the web server will try to renew the same license automatically. These settings apply to both InTouch Web Client and OMI Web Client. The license is renewed once every day.

If the same license cannot be renewed:

• A grace period timer will start.

• Existing licensed sessions will continue to work as before.

• New client sessions can still be granted, as long as licensed sessions are available.

If the license is successfully renewed:

• The grace period timer (if running) will stop.

• Everything continues to operate normally.

Note: License renewal does not apply when running in single session mode.

Grace period

Web server will go into grace period if valid license was acquired at startup but fails to renew. The grace period is 14 days. While in Grace Period:

• Web Server shall maintain the current licensed session count

• Existing client session continue to have same access and capability (R/W or R/O)

• New client session will be granted the same way as usual up to the current licensed session count.

If grace period has ended without acquiring back the license, then:

• Web server will immediately set licensed session count to 1.

• Web Client will only see this change of license status until there is a request from the web client to the web server.

For example: The Web Client session is in grace period mode and grace period has expired. If you do not refresh the Web Client page, the new license status will not be updated in the Web Client page.

Release of license

When the web server shuts down, it releases any license it has acquired, regardless of how many client sessions are active or the current license state. All active Web Client sessions are terminated immediately. After the web server is restarted, any previously connected clients must re-establish their sessions. This process should happen automatically, and the web server does not need to perform any special action other than responding to client requests as usual.