Client Licensing of a Web Interface Website
When you start a Web Interface website, the website takes the following Modeler licenses:
• A PTC Modeler Web Interface Server license.
This license is required to start the Web Interface website.
• A number of PTC Modeler Web Interface Client licenses (Web Interface Client licenses).
These licenses are used for each concurrent user of the Web Interface website.
 |
The administrator account can login to the Web Interface website even if all client licenses are in use.
|
The Web Interface administrator account can only access the Admin, Contact, and About pages of the Web Interface website. If you try to access other pages, you will be redirected to the Admin page. Accessing REST and OSLC services returns a 401 unauthorized response.
Client Licensing Process
Each time the Web Interface website is started, the website takes a specified number of Web Interface Client licenses from the license server.
These Web Interface Client licenses are stored in an internal pool for use with the Web Interface website:
• Each time a user logs in to the Web Interface website, the website takes a license from the internal pool (not the license server).
• Each time a user logs out of the Web Interface website, the website returns their license to the internal pool.
|
|
The license is returned only when the user clicks the Log Out link on the website. Closing the web browser or web browser tab does not return the license.
|
If the internal pool runs out of licenses, new users cannot log in to the Web Interface website.
A Web Interface website restarts automatically every 24 hours:
• When the Web Interface website stops, the licenses are removed from the internal pool, and the Web Interface website returns the Web Interface Client licenses to the license server.
• When the Web Interface website starts again, the Web Interface website takes the Web Interface Client licenses from the license server and stores them in the internal pool.
If a user is using a Web Interface website when it restarts, they will not have to log in again to continue using the website.
|
|
The Web Interface administrator account does not take a license.
The Web Interface administrator account can only access the Admin, Contact, and About pages of the Web Interface website. If you try to access other pages, you will be redirected to the Admin page. Accessing REST and OSLC services returns a 401 unauthorized response message.
|
Specifying how many Web Interface Client licenses a Web Interface website takes
Being able to specify how many licenses a Web Interface website can take is useful when you have many websites using the same license server.
The number of licenses that are taken by the website is determined by its web.config file. The <add key="UserLicenses"> entry specifies the value.
If the required number of licenses are not available, the Web Interface website takes as many licenses as it can. The status.log file records how many licenses are taken.
For more information about specifying how many Web Interface Client licenses a website can take, see Licensing a Web Interface website and selecting the databases it can access.
Returning of Client Licenses
As previously mentioned, a Web Interface website takes a license from the internal pool when a user logs in, and returns a license to the internal pool when a user logs out.
|
|
If a user is logged in to a Web Interface website and they close their web browser (or the web browser tab) without logging out of the Web Interface website, their license is not released.
|
When a user closes their web browser without logging out, their license becomes available for other users when either of the following events occurs:
• The Web Interface website is restarted.
• The license expires.
The administrator of the website can view when a license will expire through the Admin page of the website.
Note that by default a license expires after 240 minutes of inactivity. If desired, you can change the value of 240 minutes through the web.config file. For more information on how to do this, see Licensing a Web Interface website and selecting the databases it can access