Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


The information on this page refers to License Statistics v6.3 and newer, which consolidated group management into a single Groups page under the Administration section. If you are using a version previous to v6.3see documentation for previous versions.

Generally, license server groups are reported on in the same way as individual license servers. However, wherever status is reported, license server groups have the status "Unknown," because the license servers in a group can have various statuses.

To Administrative users can create and manage license server groups, use using the License Server Groups tabs on tab in the Administration Groups page, as shown below.found under the Administration section in the left navigation pane.

Image Added

This section discusses how License Statistics reports on existing license server groups.Image Removed

Visibility

All data for license server groups will be shown on reports regardless of visibility settings, so even if a feature or a license server is invisible for a particular user, that user will see usage information for it on reports. This ensures that all users viewing reports for a license server group see the same information instead of each seeing different information. 

...

Realtime data is reported for features on in a license server group only if each aggregated feature has realtime data. This could lead to problems in grids that display realtime data (such as Realtime Utilizationthe  Features - Realtime - Usage report), because realtime data would not be reported if a feature on one of the license servers in the group is no longer being used but has historical data. To avoid such problems, any feature on in a license server group that previously had aggregated realtime data that was previously aggregated is will no longer be included in the aggregation if its usage is older than 24 hours.

Example

Using our above example of three servers (PL, US, and DK) that each serve the WXPF feature and are in a license server group called XF, let's assume that after a couple of years, we move the DK server to a Mac OS Mavericks Nodelocked (MMN) and we . We do not renew the licenses for WXPF. However; however, we do not still want to delete retain the historical usage data for WXPF.

Now, only two of the three license servers in the XF license server group have group—PL and US—have realtime data. Instead of excluding the WXPF realtime data for WXPF for the XF license server group because one of the features has no realtime usage, the WXPF feature on the DK server is ignored (no realtime usage within 24 hours). As a result, the realtime data for license server group XF is an aggregation of WXPF realtime usage only for the PL and US servers, which still have realtime usage within 24 hours. In this way, the realtime usage for features on the license servers in the license server group is still reported.

Feature merging

If identical features (same name, version, and type) are hosted by more than one license server in a group, that feature's usage information is summed and reported as one feature for the entire license server group.