Open the Table of Contents
You are here: Setting Up the Redundant License Managers > Setting up the Redundant License Manager Pool
Setting up the Redundant License Manager Pool
- First,
install (but don’t run) the License Managers on different computers on
the network.
The RMS License Managers must be of the same version.
- Next, set each
client to access the preferred License Manager for that client by setting
the LSHOST or LSFORCEHOST environment variables on that client’s computer.
(Or, if preferred, you can choose not to set this environment variable
and allow the client to broadcast for an available License Manager.)
- If your vendor
has specified that the License Managers will be locked to specific computers,
you will need to run echoid
on each computer and record the locking code. You should also record the
host name of each computer and its IP address. You will then give the
locking codes, host names, and addresses to your vendor so that he or
she can create the license codes for these License Managers.
- You will now
install the licensed applications on the end user computers.
- If any license
servers are running that will be used as redundant License Managers, you
must shut them down before creating the redundant license file.
- After you receive
the license codes from your vendor that will be serviced by the redundant
License Manager pool, use WRlfTool or rlftool (or WlmAdmin to call WRlfTool)
to create a redundant license file to:
- Add the License Managers
to the redundant License Manager pool by specifying the host name and IP
address for each computer containing a redundant License Manager. This
defines which License Managers are in the redundant License Manager pool.
Tip
Specify at least two systems on which the License Manager will be running. If the redundant server pool is set up with only a single server specified in lservrlf, the redundant server pool will never be formed.
Make sure that you specify IP addresses in either IPv4 or IPv6 format. A redundant pool cannot have mixed servers (both IPv4 and IPv6). Consequently, a redundant server can work either in IPv6 or IPv4 mode—as long as the server is running or not removed from the redundant pool.
- Set the preference number
of the License Managers. The first License Manager added to the pool and
started up first is also known as the
leader and all other License Managers will be known as the followers. The preference order specifies
the order in which the leader will be chosen if License Managers go down.
- Use rlftool or
WRlfTool to add the redundant license codes received from the vendor into
the redundant license file (by default named as, lservrlf).
Tip:
By using the
lslic utility,
redundant licenses can be added dynamically. If the requested server is
the follower, it will forward the request to the leader; the leader server
will then check the validity of license. If the license can be added,
the leader will add that license and forward the license code to all the
followers.
- Since this is
the first time that the redundant License Manager pool has been set up,
you need to copy the redundant license file to each of the computers on
which the redundant License Managers resides. After this, changes to any
one of the redundant license files will automatically be transmitted to
each redundant License Manager when one of the License Managers is stopped
and restarted.
- Bring up each
of the License Managers in the pool. Because the redundant license file
is in the same directory as each License Manager, each License Manager will
automatically start up as a redundant License Manager.
Maintaining the Redundant License Manager Pool
Once redundant License Managers are set up, you can use lspool or WlmAdmin
from any computer on the network to view information about the redundant
License Manager pool. You must set the LHOST
environment variable to point to one of the redundant License Managers
when using lspool.
Some lspool options dynamically change the redundant License Manager
configuration, but do not write the changes permanently to the redundant
license file. When the redundant License Managers are restarted, the changes
are lost. However, other lspool options make permanent changes. See Using
lspool to Maintain a Redundant License Manager Pool for more details.