<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" MadCap:tocPath="Redundant License Managers" MadCap:InPreviewMode="false" MadCap:PreloadImages="false" MadCap:RuntimeFileType="Topic" MadCap:TargetType="WebHelp" lang="en-US" xml:lang="en-US" MadCap:PathToHelpSystem="../" MadCap:HelpSystemFileName="Default.xml" MadCap:SearchType="Stem">
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>Setting up the Redundant License Manager Pool</title>
        <link href="SkinSupport/MadCap.css" rel="stylesheet" />
        <link href="Resources/Stylesheets/SFNT_Flare.css" rel="stylesheet" />
        <script src="SkinSupport/MadCapAll.js" type="text/javascript">
        </script>
    </head>
    <body>
        <p class="MCWebHelpFramesetLink MCWebHelpFramesetLinkTop" style="display: none;"><a href="../Default_CSH.htm#Setting_up_Redundant_Pool.htm" style="font-weight: bold;">Open the Table of Contents</a>
        </p>
        <div class="MCBreadcrumbsBox_0"><span class="MCBreadcrumbsPrefix">You are here: </span><a class="MCBreadcrumbsLink" href="Overview_Redundantlicserver.htm">Redundant License Managers</a><span class="MCBreadcrumbsDivider"> &gt; </span><span class="MCBreadcrumbs">Setting up the Redundant License Manager Pool</span>
        </div>
        <h1><a name="kanchor56"></a>Setting up the Redundant License Manager Pool</h1>
        <ol>
            <li class="Numbered_Steps" value="1"><span style="color: #000000;">First, 
 install (but don’t run) the License Managers on different computers on 
 the network</span>.</li>
        </ol>
        <ul start="2">
            <li class="Numbered_Steps" value="2">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.)</li>
            <li class="Numbered_Steps" value="3">If your vendor 
 has specified that the License Managers will be locked to specific computers, 
 you will need to run <a href="echoid_and_Wechoid.htm">echoid</a> 
 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.</li>
            <li class="Numbered_Steps" value="4">You will now 
 install the licensed applications on the end user computers.</li>
            <li class="Numbered_Steps" value="5">If any License Managers are running that will be used as redundant servers, you 
 must shut them down before creating the redundant license file.</li>
            <li class="Numbered_Steps" value="6">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:</li>
            <li class="Bullets_2" value="7">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. </li>
        </ul>
        <ul start="2">
            <li class="Bullets_2" value="2">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<span style="font-style: italic;"> 
 leader</span> and all other License Managers will be known as the <span style="font-style: italic;">followers</span>. The preference order specifies 
 the order in which the leader will be chosen if License Managers go down. 
 </li>
        </ul>
        <ol start="7" style="list-style: decimal;list-style-type: decimal;">
            <li class="Numbered_Steps" value="7">Use rlftool or 
 WRlfTool to add the redundant license codes received from the vendor into 
 the redundant license file (by default named as, <span style="font-style: italic;">lservrlf</span>).</li>
        </ol>
        <h3 class="SpacedHead"><span style="font-weight: bold;">Tip</span>: </h3>
        <p class="SpacedPara2">By using the 
 <a href="lslic.htm">lslic</a> 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.</p>
        <ol start="8" style="list-style: decimal;list-style-type: decimal;">
            <li class="Numbered_Steps" value="8">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. </li>
            <li class="Numbered_Steps" value="9">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.</li>
        </ol>
        <h3>Maintaining the Redundant License Manager Pool</h3>
        <p>Once redundant License Managers are set up, you can use lspool or <a href="WlmAdmin_Admin.htm">WlmAdmin</a> 
 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. </p>
        <p>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 <a href="lspool_for_Redundancy.htm">Using 
 lspool to Maintain a Redundant License Manager Pool</a> for more details.</p>
        <p>&#160;</p>
        <script type="text/javascript" src="SkinSupport/MadCapBodyEnd.js">
        </script>
    </body>
</html>