<?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="About the RMS License Manager" 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>Locate the License Manager Computer</title>
        <link href="SkinSupport/MadCap.css" rel="stylesheet" />
        <link href="Resources/Stylesheets/SFNT_Flare.css" rel="stylesheet" />
        <script src="SkinSupport/MadCapAll.js">
        </script>
    </head>
    <body>
        <p class="MCWebHelpFramesetLink MCWebHelpFramesetLinkTop" style="display: none;"><a href="../Default_CSH.htm#Locate_the_License_Manager_Computer.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="RMS_License_Manager_Overview.htm">About the RMS License Manager</a><span class="MCBreadcrumbsDivider"> &gt; </span><span class="MCBreadcrumbs">Locate the License Manager Computer</span>
        </div>
        <h1>Locate the License Manager Computer</h1>
        <p>The application program must be able to identify a License Manager. This 
 can be done by having the application broadcast over the network for a 
 License Manager or by providing the application with the name of the License Manager computer. In most cases, it’s quicker to let the application use 
 the broadcast method of finding a License Manager. With this method, you 
 can change License Managers at any time and no changes are required at 
 the client computers. </p>
        <p>Sometimes you may want to direct an application program to a specific 
 License Manager. This may be done:</p>
        <ul>
            <li class="Bullets_1" value="1">To partition clients 
 between License Managers</li>
            <li class="Bullets_1" value="2">Because the License Manager 
 and client computer are located on different subnets or a large network 
 and broadcast messages are undesirable. &#160;</li>
        </ul>
        <div class="MCDropDown">
            <div class="MCDropDownHead_0"><a class="MCDropDownHotSpot_0" href="javascript:void(0);" id="MCDropDownHotSpot_859750555_0" onclick="FMCDropDown( this ); return false;"><img style="border: none;margin-right: 5px;" src="SkinSupport/DropDownClosed.gif" MadCap:altsrc="SkinSupport/DropDownOpen.gif" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( 'SkinSupport/DropDownOpen.gif' ); }" class="MCDropDownIcon" />Test the "Broadcast Method" of Locating a License Manager</a>
            </div>
            <div class="MCDropDownBody" id="MCDropDownBody_859750555_0" style="display: none;">
                <p>You can test the configuration using the following steps: </p>
                <ol>
                    <li class="Numbered_Steps" value="1">Verify the LSHOST 
 and LSFORCEHOST environmental variables are not set and the <span style="font-style: italic;">LSHOST</span> 
 or <span style="font-style: italic;">lshost</span> file does not exists 
 in the same directory as the licensed application.</li>
                    <li class="Numbered_Steps" value="2">Run either the lswhere or WlmAdmin utilities on the 
 client computer. These utilities do a network broadcast for License Managers 
 and display a list of all License Managers that are visible from the client 
 computer. WlmAdmin also displays a list of licenses; you can check that 
 list to verify there is a License Manager for the applications you want to run. 
 </li>
                    <li class="Numbered_Steps" value="3">If all expected 
 License Managers are present, then the application will be able to run 
 using the broadcast method. Of course, one of the License Managers that 
 is found must have a network license code that can be used to authorize 
 use of the client computer. </li>
                    <li class="Numbered_Steps" value="4">If you are not 
 able to see a particular License Manager, you should verify the network 
 connection by using a network diagnostic program like <span style="font-weight: bold;">ping</span>. 
 You can make this check by providing either the network address as a number 
 (192.33.22.2) or as a name (license_host). If you are unable to locate 
 the License Manager using <span style="font-weight: bold;">ping</span>, then you 
 have a network configuration problem that must be resolved before your 
 licensed application can be used with a network license. </li>
                </ol>
            </div>
        </div>
        <div class="MCDropDown">
            <div class="MCDropDownHead_0"><a class="MCDropDownHotSpot_0" href="javascript:void(0);" id="MCDropDownHotSpot_859750555_1" onclick="FMCDropDown( this ); return false;"><img style="border: none;margin-right: 5px;" src="SkinSupport/DropDownClosed.gif" MadCap:altsrc="SkinSupport/DropDownOpen.gif" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( 'SkinSupport/DropDownOpen.gif' ); }" class="MCDropDownIcon" />Test the "Named License Manager Method" of Locating a License Manager </a>
            </div>
            <div class="MCDropDownBody" id="MCDropDownBody_859750555_1" style="display: none;">
                <p>You can test the configuration using the following steps: </p>
                <ol>
                    <li class="Numbered_Steps" value="1">Follow the steps 
 given for the broadcast 
 method until the client computer is able to find each License Manager 
 that you want. If you are using the named License Manager method because 
 the client computer and License Manager are not on the same subnet, then 
 you may want to skip right to the last step and just use <span style="font-weight: bold;">ping</span>. 
 </li>
                    <li class="Numbered_Steps" value="2">If you can ping 
 a License Manager when you specify its address by number but can’t do this 
 when you specify the address as a name, then your client computer has 
 a problem with network domain name resolution. In this case you can either 
 solve this problem or just provide the numeric form of the address to 
 Sentinel RMS. Of course, if your License Manager is dynamically assigned 
 a numeric network address, you will have to solve the name resolution 
 problem. If you don’t, then the next time the License Manager is assigned 
 a new, numeric network address, the applications will no longer be able 
 to find the License Manager. </li>
                    <li class="Numbered_Steps" value="3">Now, set the 
 LSHOST or LSFORCEHOST environment on the client computer to the name of 
 the License Manager. The LSHOST and LSFORCEHOST naming conventions are: 
 </li>
                </ol>
                <ul>
                    <li class="Bullets_2" value="1">Any valid name recognized 
 by your network can be used.</li>
                    <li class="Bullets_2" value="2">IP addresses (like, 192.22.11.33) 
 can be used. </li>
                    <li class="Bullets_2" value="3">Host names (like, “dept.computer”) 
 can be used. </li>
                    <li class="Bullets_2" value="4">For LSFORCEHOST, you 
 can specify only a single License Manager. This will have priority over 
 LSHOST.</li>
                    <li class="Bullets_2" value="5">For LSHOST, you can provide 
 a list of License Manager names. Each must be separated by a ~<span style="font-weight: bold;">&#160;</span> 
 symbol. The application program will try each License Manager in the list, 
 beginning with the first listed, to find a License Manager that is serving 
 this feature/version. The traversal will not stop in case a License Manager 
 is found that services the feature/version but has no license tokens. 
 </li>
                </ul>
                <ol start="4">
                    <li class="Numbered_Steps" value="4">Test the LSHOST 
 setting by running the <a href="lsmon.htm">lsmon</a> 
 utility on the client computer or specifying the computer on which the 
 License Manager is running. If the name is correct, lsmon will be able 
 to report status on the selected License Manager. <br></br>	An application that supports both stand-alone and network license codes 
 treats LSHOST as advisory. The application will first try to obtain a 
 license by checking with all License Managers listed in LSHOST. </li>
                    <li class="Numbered_Steps" value="5">You can now test 
 the application. It should be able to obtain a license. If it does not, 
 then you should run WlmAdmin (for Windows) and verify that the license 
 server has a license that authorizes use of an application on the client 
 computer.</li>
                </ol>
            </div>
        </div>
        <p>&#160;</p>
        <script type="text/javascript" src="SkinSupport/MadCapBodyEnd.js">
        </script>
    </body>
</html>