What are multiple pools? #
The Flexera network license management system employs license files to track client license inventory. The license file is an account of purchased licensed features, each with respective attributes such as the licensing model, number of licenses, expiration date etc. Licenses for equivalent features may be bought separately, thus forming separate ‘pools’ in the license file, each pool determining specific attributes.
Benefits of multiple pool monitoring #
The OpenLM system can very well report license usage levels of multiple pool licenses. However, without applying the multiple pool monitoring capability it will not attribute a specific license usage session to a specific pool. This disadvantage is especially evident in the context of presenting the licensing model; Floating licenses, Node locked and Network named licenses all being presented equally, as part of a single pool. Keep in mind that licenses are priced differently per license model.
OpenLM as an active system #
OpenLM must be accepted as an active system:
- OpenLM will actively edit and sort the FlexLM license file. It is recommended to back up the FlexLM license file prior to monitoring multiple FlexLM license pools.
- If a manual change is done to the license file – OpenLM will actively restart the license server, in order to read the updated license information from that license server.
OpenLM Broker #
The OpenLM Broker needs to be installed on the license server machine. Please refer to this document.
License file #
The OpenLM Broker needs to access the FlexLM license file on the license manager of interest. Please refer to the paragraph “LICENSE MANAGER PORT; ADVANCED” on the same document.
Options file #
The OpenLM Broker needs to access the FlexLM Options file on the license manager of interest. Please refer to the paragraph “LICENSE SERVER – VENDORS” on the same document. Please note that accessing the FlexLM Options file will require a license for the OpenLM Options file management extension.
Debug log #
The OpenLM Broker needs to access the FlexLM Debug log file on the license manager of interest. Please refer to the paragraph “LICENSE SERVER – Log file” on the same document.
OpenLM License file #
Multiple pool monitoring is a new OpenLM extension, and requires a license. This license is presented in the OpenLM license file, and is provided per vendor. The presentation of license usage acts according to the OpenLM license and configuration as depicted below:
As described in the diagram above, if the OpenLM license file does not include a Multiple pool license monitoring extension per a specific vendor, license usage will be partially presented, or not presented altogether. The EasyAdmin ‘Licenses’ window will look as follows. Note the ‘0’ usage and warning signs:
When the OpenLM server is configured to monitor multiple pool licenses, it goes through the license file, and locates features that appear in multiple pools. It then backs up the license file, and edits the original file. OpenLM sorts the license pools according to the precedence of their usage, e.g. Network Named User based licenses will precede ordinary floating licenses. The licenses’ ‘Asset_info’ attribute is changed according to this sorting.
In order to enable OpenLM to sort the license file:
- Open the OpenLM Broker configuration tool
- Select the port of interest
- Set the license file path (manually or automatically)
- Click the ‘Sort‘ button – to apply license file sorting immediately, OR
- Check the “Allow to sort License File” box, to apply this action automatically
- Click the ‘Apply’ and “Restart Broker” buttons.
The backed up copy of the original license file will be found on the same directory, with the added .bak extension.
The OpenLM Broker then actively restarts the License server, so that the changes made in the license file would take effect.
Following this, OpenLM will compile usage information from multiple sources in order to match specific sessions with their respective license pools.
Note: The matching process is lengthy, and licenses will not be attributed to their license pool in real time. While the process is not yet complete, the session will be assigned an arbitrary pool, and an appropriate notification will be presented in both the “Currently consumed licenses” and “License activity” EasyAdmin windows:
Additional key #
Since OpenLM 3.0, we have introduced an additional key for filtering EasyAdmin report windows; It is now possible to filter reports according to licenses’ Asset info, and present usage according to license pools. This is available on the “Currently consumed licenses” , “License usage” and “License activity” EasyAdmin windows.
When matching does not succeed #
As noted above:
- if the matching process fails, license usage will be attributed to an arbitrary license pool, and a notification will be presented.
- If the client is not licensed by OpenLM to monitor multiple pool licenses – license usage will be partially presented
Options file changed manually #
OpenLM relies on the FlexLM Options file to associate licensed application usage with license pools.
- the Options file editing capability is utilized in ‘Write’ mode ( i.e. the user edits the license manager’s Options file via the OpenLM EasyAdmin Options file editor) and
- the Options file is manually edited on the license server machine
OpenLM will no longer be able to rely on the Options file, and will resort to license usage reporting regardless of license pools. Usage reporting will not include license pool attributes, and an appropriate warning message will pop up in EasyAdmin .
There are two manners to deal with this condition, and regain association of license usage to license pools. Either:
- Reload the Options file information by clicking: EasyAdmin Start → Administration → Options file → select the required Options file → Delete. The edited Options file will then be re-associated with that vendor.
- Override the external changes that were made to that Options file by selecting EasyAdmin Start → Options files → Options File Management → Deploy.
License file edited #
If a change is detected in the license file, OpenLM will initiate a license server restart, in order to ensure that the license manager reports are accurate.