Administer > Application setup > Controlling user access and security > License tracking

License tracking

Service Manager tracks floating and named licenses on the application level for reporting purposes.

The logon process determines which applications are authorized for each user, allocates a floating or named license for the duration of the session, and records usage information in the stathistory file. When the user logs out or ends the session, Service Manager deallocates the license. Because Service Manager tracks the highest daily license usage for each application, administrators can use this information to determine how many licenses are being used and when peak usage times occur. They can enable or disable user license tracking at any time.

The license tracking feature tracks the named and floating licenses on an application basis. Service Manager refreshes the license usage information whenever the user logs out, or the session terminates by inactivity or administrator action.

Service Manager calculates license usage for all types of client connections, including SOAP, Web Services, REST, and SCAuto. The calculation is based on the number of login user names and the number of client IP addresses. For example:

  • Two sessions that use the same login user name and two different client IP addresses consume two licenses.
  • Two sessions that use the same login user name and the same client IP address consume one license.
  • Two sessions that use two different login user names consume two licenses.

Authorized applications

The following applications monitor licenses:

  • Contract Management
  • Change Management
  • Incident Management
  • Configuration Management
  • Request Management
  • Problem Management
  • Service Desk
  • Knowledge Management
  • Service Level Management
  • Smart Analytics

The Database Administrator can enable and disable the application license tracking feature. Service Manager applications contain logic to ensure license usage accuracy.

License tracking

1. License count covers all sorts of usages, including SOAP/WS/REST/SCAUTO.

2. The license count the login user name and client IP:

Two sessions with the same login user name from different client IP will spend two counts,

Two sessions with the same login user name from the same client IP will spend only one count.

Of course two different login user names will spend two counts.

Related topics

Administration perspective
Calendars
Ongoing maintenance
Interoperability
Named users
Named users for applications
Stathistory table
Self-service licenses
Notifications
Regional settings
Security tables
System information record
Time zones

Determine the number of named users available
Make an individual operator a named user
Define named users for applications
Generate a user license report
View the stathistory table

License types
Profile fields for Change Management license tracking
Profile fields for Contract Management license tracking
Profile fields for Configuration Management license tracking
Profile fields for Incident Management license tracking
Profile fields for Problem Management license tracking
Profile fields for Request Management license tracking
Profile fields for Service Desk license tracking