Session-based Client Connection License

Acquiring Client Connection License

• The maximum number of connections which can be active at a time depends on the value set for the AVEVA Concurrent Client Connection license limit. Each user logging in to an Enterprise Console will consume a license. If a user logs in through different browsers or repositories, then each login consumes one license.

  For example: If you have purchased the Client Connection License with a Quantity of 20 Pack, a maximum of 20 connections can be active at a time.

  Note:
  - You can view the details of the consumed licenses from the Usage Summary tab in the AVEVA License Manager Portal.
  - If the AVEVA Core Count license is activated, then the client connection license will not be consumed when the user logs on to Enterprise Console.
  - If the license limit is exceeded when logging in with the AIM based Active Directory provider, an alert message will be displayed. After clicking the OK button, the user will remain on the same page.

• The Unique Device ID maintained for the connection is the Host name or IP address of the machine from which the user logs on to the Enterprise Console. The user name for the connection is the user ID string used for logging on to the repository. For example: admin, corp\user1

  For example: If user "admin" logs in to the Enterprise Console in the Google Chrome browser, then the Device is displayed as <Unique Device ID>_<Appended Unique Characters> and User is displayed as admin.

• After a license is acquired and the user logs on to Enterprise console, the license gets acquired again after every 5 minutes for an active session.

Releasing Client Connection License

The connection license gets released in the following scenarios:

• When a user logs out from the Enterprise Console by clicking the Log Out menu option. The license is released based on the Device ID and the user, as explained in the Acquiring Client Connection License section.

• If the user has configured the Auto Log Off setting while creating the repository, and if the user does not perform any activity in the Enterprise Console for the time period specified in this setting.

  For example: If the time period in the Auto Log Off setting is configured as 5 minutes. The user is logged off if the user session is inactive for 5 minutes.

• If the user has logged in to the Enterprise Console and if the user closes the browser window without clicking the Log Out menu option.

Note: In some cases, when a user closes the browser window without logging out, the Client Connection License is not released immediately. In such cases, the Client Connection License is released after 40 minutes.

Releasing Client Connection License – Customized Log out

If a user has customized the logout option instead of using the Enterprise Console logout, then the client connection license consumed after logging in to the Enterprise Console is not released.

The user has to release the client connection license from their logout custom code.

The following code can be used to release the client connection license.

Skelta.Entity.UserContext UserCtx = new Skelta.Entity.UserContext();

string userName = UserCtx.GetUserName();

string deviceId = string.Empty;

if (HttpContext.Current.Request.Cookies[userName + "_skdeviceid"] != null)

{

deviceId = HttpContext.Current.Request.Cookies[userName + "_skdeviceid"].Value;

}

Workflow.NET.Security.Client.SELicensing.LicenseConnectionManager licManager

= new Workflow.NET.Security.Client.SELicensing.LicenseConnectionManager();

bool licenseReleased = licManager.ReleaseClientConnectionLicense(deviceId, userName);

if (licenseReleased)

{

HttpRuntime.Cache.Remove(deviceId);

Response.Cookies[userName + "_skdeviceid"].Expires = DateTime.Now.AddDays(-1);

}