Error: Invalid spaceKey on retrieving a related space config.

Recording and tracking license usage

You record and track usage details of fixed and floating licenses using AR System Current License Usage form and AR System Historical License Usage form. By default, BMC Remedy AR System does not record data in these forms. You must turn on the Enable License Tracking option to record the data.

To get a report about license usage, see Generating a license usage report. You can also get information about what type of license a user has by searching the user form.

The following sections provide further details. In addition, this topic provides information specific to tracking server group license usage.

Recording and tracking data in the license usage forms

To record data in the license usage forms

  1. In the AR System Administration Console, click System > General > Server Information.
  2. On the Configuration tab, select the License Tracking option.
  3. Select Write Licenses or all Licenses from the drop-down, depending on your choice.
  4. Click Apply.
    BMC Remedy AR System immediately starts recording data in the license usage forms. You do not need to restart the AR System server.

To stop recording data in the license usage forms

Clear the Enable License Tracking option, and save your change.

All data in the AR System Current License Usage form is lost when

  • The Enable License Tracking option is switched off.
  • A standalone server is stopped.
  • All servers in a server group are stopped.

AR System Current License Usage form

The AR System Current License Usage form tracks all licenses in use on the server. From BMC Remedy AR System server version 9.1.00, the custom and base filters for the submit and modify execution options are not supported on the AR System Current License Usage form. You must modify the existing base filters to run on the merge execution option. However, from BMC Remedy AR System server version 9.1.02.004, you can also modify the existing custom filters to run on the merge execution option.

Fields in AR System Current License Usage form

Field

Description

User Name

Name of the user who acquired the license

Group ID

ID of the pool that the license belongs to (applies only to floating licenses)

Application Name

Application that the license applies to

License Type

Type of license (fixed, floating, read, restricted-read)

Note: AR System Current License Usage form tracks only fixed and floating licenses.

Server Name

Server to which the license is applied

Time Acquired

Time that the user acquired the license

Note

When BMC Remedy AR System starts recording data in this form, it creates records for every license in use. Those records include the time that each license was acquired (or consumed), not the time that recording started. For example, if a user acquires license A at 10:15 A.M. and BMC Remedy AR System starts recording data in this form at 10:30 A.M., the Time Acquired for license A is 10:15 A.M

Type of Record

Type of record used to track license usage:

  • Main— This record is used as follows:
    • For licenses not in server groups, this is the only record created to track usage.
    • For licenses in server groups. this is the parent record that tracks the total usage of a particular type of license.
  • Subrecord (server group only) — A child of a main record
    When a license is initially acquired in a server group, both a main record and a subrecord are created. If the user acquires another license of the same type on another server in the group without releasing the first license, the second license is recorded as another subrecord of the main record. The same is true for all additional licenses of that type acquired within the server group while the main record has at least one subrecord.

AR System Historical License Usage form

If a user releases a license while the Enable License Tracking option is on, an entry is added to the AR System Historical License Usage form. The entry contains information about the usage of that license.

Fields in AR System Historical License Usage form

Field

Description

User Name

Name of the user who acquired and released the license

Group ID

ID of the pool that the license belongs to. Applies only to floating licenses.

Application Name

Application that the license applies to

License Type

Type of license (fixed, floating, read, read-restricted)

Note: AR System Historical License Usage form tracks only fixed and floating licenses.

Time Acquired

Time that the user acquired the license

Time Released

Time that the user released the license

Total Use Time

The total amount of time in seconds that the license was in use

Tracking server group license usage

When a user first acquires a particular type of license in a server group, the acquisition is recorded in the AR System Current License Usage form as a main record and a subrecord. For example, for a user currently logged into the system, there is one main record, and for every server in the server group the user is logged, there is one subrecord.

If the user acquires another license of the same type on another server in the group without releasing the first license, the second license is recorded as another subrecord of the main record. The same is true of all additional licenses of that type acquired while the main record has at least one subrecord.

When the user logs out of the sessions from a server by releasing one of his licenses, its subrecord for the license is deleted. When the last subrecord is deleted, it indicates that the user has logged out and released all the licenses from the server, the main record is also deleted and an entry for the entire session tracked by the main record is added to the AR System Historical License Usage form.

If you stop any server in the server group, all the subrecords for that server are removed when the server is restarted or when another server recognizes that the cleanup is needed for the down server. When the cleanup is performed, the data is not considered valid for use.  If all subrecords for a user are removed in this type of cleanup operation, the main record is also removed without any Historical License usage entry being created.


Related Topics


Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Ryan Nicosia

    The step to Enable License Tracking is misleading.  The option as it exists on the Config form is labeled "License Tracking".


    As such, the step should reach, Update the License Tracking option to "Enabled" or something similar.

    Dec 13, 2016 01:28
    1. Anagha Deshpande

      Hello Ryan,

      Apologies for responding late. I have updated the topic.

      Regards,

      Anagha 

      Aug 22, 2017 05:41
  2. Scott Skeate

    For Current License Usage, it is stated "From BMC Remedy AR System server version 9.1.00, the custom and base filters for the submit and modify execution options are not supported on the AR System Current License Usage form. You must modify the existing base filters to run on the merge execution option. However, from BMC Remedy AR System server version 9.1.02.004, you can also modify the existing custom filters to run on the merge execution option." What are the base filters that need to be modified?

    Nov 26, 2018 05:10