The SHARE directive specifies the type of license sharing that is in use. Share options are described in the following table.
Option | Description | Used for | network licensesNetwork Licenses | Used for | local licensesLocal Licenses |
|---|---|---|---|---|---|
HOST | This option specifies that processes running on the same host will share licenses and that processes running on different hosts will use different licenses. Using the HOST option allows a user to start multiple sessions of the same application on the same host, yet take licenses for only one session. | Yes | No | ||
USER | This option specifies that processes started by the same user on multiple machines will share the same license, regardless how many machines the license runs on, and processes started by different users will use different licenses. Using the USER option allows a user to start multiple sessions of the same application on multiple machines, yet take licenses for only one session. | Yes | No | ||
CUSTOM | This option specifies that processes started using the same custom sharing string will be shared. This option also specifies that processes started using different custom sharing strings will use different licenses. You can use the CUSTOM share option to custom-define when to enable sharing, thereby potentially making the license sharing more restrictive. | Yes | No | ||
VIRTUAL | This option allows an application to run in a virtual machine environment; for example, using VMware or Virtual Server. See Licensing for virtual machines and cloud computing for more information. | Yes | Yes | ||
TERMINALSERVER | This option specifies that the licensed application will work for remote terminal server clients. When TERMINALSERVER is not specified, remote clients will be blocked, thereby preventing a local license from being shared for multiple users via a terminal server. The TERMINALSERVER tag applies only to Windows and is ignored by Unix. (For information about problems that may occur when you set the SHARE=TERMINALSERVER directive, see Licensing issues.) | No | Yes | ||
SINGLE | This option limits checkouts to one instance of a feature across multiple sessions. A single-usage license is essentially a one-count floating license for a single host, but eliminates the need to setup a license server. | No | Yes |
...
For share options used with network licenses, the COUNT directive must be set.
Combining share options
For network licenses, HOST, USER, CUSTOM and VIRTUAL sharing can be used together. For local licenses, VIRTUAL, TERMINALSERVER and SINGLE sharing can be used together. When combining multiple share options, separate them with a vertical bar ( | ); for example, SHARE = HOST|USER|CUSTOM.
...