Troubleshooting and FAQs
Question: What is the difference between aggregate and additive licenses?
An additive license appends changes to an existing additive license of the same feature and version in a restrictive manner, so that only a single set of all the license properties is maintained. While the hard and soft limit of the two licenses are summed up for the entire duration of the license, only one set of start date (the latest of the two start dates) and expiry dates (the earliest of the two end dates) is maintained. Click here to see what happens to the license properties for two additive licenses.
In the case of aggregate licenses, the individual start date and end date remain valid and the limits (hard and soft) congregate only during the overlapping license tenure.
Unlike additive license, aggregate licenses with start dates in future can be added to the License Manager,
Additive licenses are a better choice when a permanent hike in license demand pattern is inevitable and more number of licenses are required round the clock. Aggregate licenses are more like top-up licenses and make best choice for short term hikes in license demand.
Question: How can the system administrator monitor the licenses in use?
RMS utilities lsmon (command-line) and WlmAdmin (graphic) display information about all features currently licensed by the Sentinel RMS License Manager and corresponding licenses and clients. For details about using these utilities, refer to the Sentinel RMS SDK System Administrator Guide.
Question: The existing license has expired, then what will happen during the period until the start date of the future-date license reaches?
Until the future-date license's start date is reached, the LS_LICENSE_EXPIRED error will appear on every license request \ query call.
Question:Can we aggregate licenses by providing different license software vendor info
License aggregation is possible only when the participating licenses have identical public and private vendor information. From RMS v9.4.1 onward, a new license property license_vendor_ info has been introduced. The participating licenses aggregate even when the value of this property is different. This field is applicable to version 19 licenses and above.
NOTE Furthermore, the license version has been upgraded from 18 to 19 to support this functionality.