Specifications

Before Your User Checks an Authorization In or Out
70
Chapter 4 - Commuter Licensing
server startup options.) This makes sure that commuter licensing doesn’t use up
all of the license tokens needed by other users of the application on the network.
Commuter Licensing Authorization Checkin Policy
When checking out an authorization, the user may request authorization for a
specific number of days (the default is 30). Since the authorization expires after
that many days, you may choose to instruct the user not to bother checking the
authorization in after returning. On the other hand, if you are in danger of run-
ning out of license tokens for that application, you may want to encourage users
always to check authorizations back in as soon as possible.
Also, note that the commuter licensing user must check an authorization back
into the same license server from which the authorization was checked out.
Locking the Authorization
An authorization is locked to the portable computer using parameters set by your
application vendor. These parameters might be hard disk ID, host ID, or a variety
of other items. If for some reason you need to change which elements are used to
lock the authorization, contact your application vendor for assistance.
Before Your User Checks an Authorization In or Out
Before your network user checks out a commuter authorization, make sure that
the user’s portable computer:
• Has the protected application installed and ready to use. Remember that
the application must be able to run off the network.
• Has network access to the appropriate license server. (You do not need to
set the lshost file or LSHOST or LSFORCEHOST environment variables
to contact a specific license server because your user will be able to
request a specific license server when using the commuter licensing util-
ity.)