For License administrators to restrict the licensing activities based on the identity of system in use (Virtualization based or a Physical), can be achieved via 2 ways.
1.) Restricting the vendor daemon on virtual/physical machine.
This can be achieved by setting the vendor daemon attribute "ls_allow_vm", mentioned under lsvendor.c.
/*
* Virtualization support for vendor daemon.
* VM_ONLY - Vendor Daemon can be operated in Virtual machine only
* PHYSICAL - Vendor Daemon can be operated in Physical machine only
*/
FLEX_VM_TYPE ls_allow_vm = VM_ALL;
Specifies whether the vendor daemon is restricted to run only in a virtual environment or is restricted to run only on a physical machine. By default, the vendor daemon can operate in a virtual environment or on a physical machine.
To use the non-default values for the ls_allow_vm variable, you must have a set of vendor keys that provides for virtualization support.
| PHYSICAL | Restricts the license server to run only on a physical machine; the license server cannot be run in a virtual environment |
| VM_ONLY | Restricts the license server to run only in a supported virtual environment; the license server cannot be run on a physical machine. |
| VM_ALL | Allows the license server to run on both physical and virtual environments |
Documentation Reference: "Programming Reference for License File–Based Licensing", Chapter-5 : "Customizing the vendor daemon".
2.) Restricting the client access to licenses.
This can be achieved through license file 'optional keyword' VM_PLATFORMS.
VM_PLATFORMS=PHYSICAL | VM_ONLY | VM_ALL
Enables you to specify whether feature usage should be restricted to virtual machines or restricted to physical machines.
If the VM_PLATFORMS value differs in any way between two INCREMENT lines for the same feature name, they are pooled and counted separately.
| PHYSICAL | Restricts the application to run only on a physical machine; application cannot be run in a virtual environment. |
| VM_ONLY | Restricts the application to run only in a virtual environment; application cannot be run on a physical machine |
| VM_ALL | Allows running the FlexEnabled application on both physical and virtual machines (default behavior). This is equivalent to not specifying the VM_PLATFORMS keyword |
Documentation Referance: Programming Reference for License File–Based Licensing, Chapter-8 : "License File Syntax".
Related Articles
What is Oracle Universal Installer (OUI) evidence? 178Number of Views Can You Create a Binary That Contacts Both Server and Client Trusted Storage? 8Number of Views Upgrading Snow platform results in error: "Unable to activate client (for Risk Monitor customers)" 104Number of Views AdminStudio Client Tools Evaluation Restrictions 22Number of Views KRM agent does not gather data required to establish VM-host relationships in OpenShift Virtualization and similar environ… 2Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago