Specifications

Configuring the License Server Client
SentinelLM System Administrator’s Guide 35
2. If you can ping a license server when you specify its address by number
but can’t do this when you specify the address as a name, then your cli-
ent 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 SentinelLM. Of course, if your license server 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
server is assigned a new, numeric network address, the applications will
no longer be able to find the license server.
3. Now set the LSHOST setting on the client computer to the name of the
license server.
The LSHOST naming conventions are:
• Any valid name recognized by your network can be used.
• Numeric names (192.22.11.33) can be used.
• Symbolic names (“dept.computer”) can be used.
• You can provide a list of license server names. Each must be sepa-
rated by a : symbol. The application program will try each license
server in the list, beginning with the first listed, to find a license
server that is serving this feature/version. The traversal will stop even
if a license server is located that services this feature/version but it
has no license tokens.
4. Test the LSHOST setting by running the lsmon utility on the client com-
puter or specifying the computer on which the license server is running.
If the name is correct, lsmon will be able to report status on the selected
license server.
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 servers listed in LSHOST.
5. You can now test the application. It should be able to obtain a license. If
it doesn’t then you should run WlmAdmin (for Windows) and verify