You are here: Setting Up the Redundant License Servers > Setting up the Redundant License Server Pool

Setting up the Redundant License Server Pool

First, install (but don’t run) the license servers on different computers on the network.

Note: The RMS license servers must be of the same version.

Next, set each client to access the preferred license server 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 server.)
If your vendor has specified that the license servers 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 servers.
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 servers, 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 server pool, use WRlfTool or rlftool (or WlmAdmin to call WRlfTool) to create a redundant license file to:
Add the license servers to the redundant license server pool by specifying the host name and IP address for each computer containing a redundant license server. This defines which license servers are in the redundant license server pool.

Note: 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 servers. The first license server added to the pool and started up first is also known as the leader and all other license servers will be known as the followers. The preference order specifies the order in which the leader will be chosen if license servers 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 server pool has been set up, you need to copy the redundant license file to each of the computers on which the redundant license servers resides. After this, changes to any one of the redundant license files will automatically be transmitted to each redundant license server when one of the license servers is stopped and restarted.
Bring up each of the license servers in the pool. Because the redundant license file is in the same directory as each license server, each license server will automatically start up as a redundant license server.

Maintaining the Redundant License Server Pool

Once redundant license servers are set up, you can use lspool or WlmAdmin from any computer on the network to view information about the redundant license server pool. You must set the LHOST environment variable to point to one of the redundant license servers when using lspool.

Some lspool options dynamically change the redundant license server configuration, but do not write the changes permanently to the redundant license file. When the redundant license servers are restarted, the changes are lost. However, other lspool options make permanent changes. See Using lspool to Maintain a Redundant License Server Pool for more details.