Novell ADMINSTUDIO 9.5 User Manual page 1661

Table 21-18 • FLEXwrap License Parameters (cont.)
Parameter
License
Limit
Overdraft
Program
Suite
AdminStudio 9.5 User Guide
Description
This parameter is the license limit—the number of licenses that the License Server will allow to
be checked out simultaneously, not including overdraft.
To strictly enforce the license limit for this feature, enter the number of licenses that you are
licensed to run. If you do not wish to restrict licensing, but you want complete reports on all
usage of the wrapped application, enter the largest number of instances of this binary that you
think will be run simultaneously.
If you are just testing FLEXwrap's functionality, you might want to enter 2 here. The license
count will appear after the expiration date on the
or for the license limit.
uncounted
This parameter is the number of licenses above the license limit that the License Server will
allow to be checked out. Use this parameter if you want usage reports on usage and do not
want to enforce license limits. Reports will show the license limit as the maximum number of
licenses available, and any usage exceeding this limit will be overdraft usage.
Some vendors sell their products as a suite. FLEXwrap defines a suite as a group of
independent programs which must, for licensing purposes, be treated as a unit.
For example, if a product suite, Office, consists of programs Word, Paint, and Mail, and if you
have only one license for the suite, then while one user was using Word, that same user could
use products Paint or Mail, but a different user could not use any products—even Paint or Mail,
which are not currently in use.
Typically, to create the licenses for a product suite, you would create licenses with the
(duplicate license request) parameter set so that multiple requests from the same user (or
by
the same user on the same host) count as one license request.
When you create a suite license with FLEXwrap, the Wrapper checks out both the individual
program license (Word in the example above) and a suite license (Office in the example).
Since a second license request for Office does not require an additional license, when the
same user runs program Paint, he is able to check out the Office suite license, and is also
allowed to check out the Paint license. If another user attempts to check out a license for Paint,
she would be unable to get the Office suite license and her request would be denied (or
queued).
An application is made part of a suite by using the optional
license line.
FEATURE PREREQ
wrapped application will be executed.
To create a suite you must add a
must then create the suite's
FEATURE suite name swrap 1.0 expiration count 0 \
DUP_GROUP=[UHDS]
This is identical to an application's
attribute is pertinent.
ADS-0950-UG00
Chapter 21: License-Enabling Packages Using FLEXwrap
FEATURE
is set to a that must also be checked out before the
FEATURE
line to all
PREREQ FEATUREs
in the license file. A full suite
FEATURE
line except that only the
FEATURE
Managing FLEXwrap License Files
line. For uncounted licenses, enter
attribute of a FLEXwrap
PREREQ
that will be part of the suite. You
looks like:
FEATURE
optional
DUP_GROUP
0
Group
1661