Specifications

Overview of Setting up Redundant License Servers
44
Chapter 3 - Setting up Redundant License Servers and License Balancing
When using the SentinelLM utilities, you must have administrator privileges on
Windows NT or Windows 2000, be logged into the root on UNIX, or be the user
who started the license server on Windows 95/98 to:
• Change distribution criteria.
• Shut down the license server (and on Windows NT/2000, if user name
Administrator started the license server, only user name Administrator
can shut it down using lsrvdown).
• Turn license server logging on and off.
• Turn token borrowing on and off.
• Add or delete license servers from the redundant license server pool.
For more details on user privileges, see “User Privileges” on page 28 of “Chap-
ter 2 - Configuring the License Server.”
Using Redundant Commuter Licensing
A commuter license enables your end user to “check out” an authorization for a
license for temporary use on a portable computer. (See “Chapter 4 - Commuter
Licensing” on page 69 for general information on using commuter licenses.)
Your vendor selects whether a network license code will be a commuter license
when creating the license code. Commuter licenses can also be redundant
licenses; if they are, their tokens can be distributed among the redundant license
servers just as with other redundant license codes.
Your end users can use Wcommute (for Windows) or lcommute (Windows or
UNIX) to check out a license authorization from any of the redundant license
servers. However, the customer must check that authorization back in to the
same license server from which it was checked out. Because commuter licenses
will automatically expire in 30 days or fewer after they are checked out, there is
no real reason for your customer to check the authorization back in unless the
redundant license server pool is running low on commuter license tokens (which
you can check by using lsmon or WlmAdmin).