|
|
|
Multiple ANLM license servers configuration |
|
|
|
|
Multiple ANLM license servers configuration |
|
OptionsWhile using multiple ANLM (Alchemy Network License Manager) servers, 2 deployments are available:
In all cases, an effort should be made to select stable systems. Do not pick systems that are frequently rebooted or shut down.
Distributed model configurationEach individual ANLM server has its license activated separately. Go to Installing and Activating the ANLM server for instructions on setting up an ANLM server. With the different ANLM server setup and licensed, the ability to fall back on subsequent ANLM servers is possible using additional license files in the Catalyst client installations. No configuration is necessary on the ANLM servers themselves. Traditionally at Alchemy Software, the Catalyst client license file is named Client.lic (although not a requirement) and is located in the public folder: C:\Users\Public\Alchemy Software\Catalyst X.0 This licence file contains the ANLM server name in this format: SERVER server01 HOSTNAME=server01 For each additional ANLM server you want to check for licenses, add a new client.lic in your Catalyst public folder. The key is to name the license files in the appropriate alphabetical order so that the first ANLM server is requested first, the second ANLM server is requested second and so on... ExampleYou have 3 ANLM servers named server01, server02 and server03. You want your Catalyst 10 client to get a license from server1 first, then if no license are available query server2 and if still no license available check server03. No license available may mean that the server is down for any reason. To achieve this, 3 license files would be created in the Catalyst 10 public folder like so: filename: 1_Client.lic SERVER server01 HOSTNAME=server01 filename: 2_Client.lic SERVER server02 HOSTNAME=server02 filename: 3_Client.lic SERVER server03 HOSTNAME=server03 When launching Catalyst, the software looks at the first .lic file in alphabetical order in the Public folder. This will be 1_Client.lic. If no license is available on this server or the server is down, Catalyst will move to the second .lic file in the public folder and look for a license on that server. And the process continues on until the last available .lic file. IMPORTANT: This will work as long as all ANLM servers are on the same domain.
Redundant model configuration
Using the three-server redundancy capability, all three license servers operate to form a triad. The license servers send periodic messages to each other to ensure that at least two servers are running and communicating with each other. A quorum is formed when at least two of the three license servers are running and communicating with each other. The license servers are identified as primary, secondary, or tertiary. One license server is also designated as the master [m] and is responsible for:
If the master fails, then another license server becomes the master.
IMPORTANT: This will work as long as all ANLM servers are on the same domain and subnet.
Setting upContact support@alchemysoftware.com to deploy ANLM servers with the redundant model. The Support team will need to be involved in the configuration. Each individual ANLM server is first installed and has its license activated separately. One of each Catalyst Edition to be deployed must be included in this initial license activation. Go to Installing and Activating the ANLM server for instructions on setting up an ANLM server. You may skip setting up the service at this point. Once all licenses have been activated, send the 3 generated license files to support@alchemysoftware.com indicating which server will be the Primary (master). A new single license file will be created (makekey) to replace all 3 licenses files. For example: SERVER server01 0019d1090898 27009 SERVER server02 001cc0fc2603 27009 SERVER server03 001cc0075acb 27009 VENDOR ALCHEMY USE_SERVER FEATURE DeveloperPro_ ALCHEMY 10.4 permanent 3 BORROW=336 SIGN="0010 \ 9A82 2741 A3E6 6A30 4D0F 2002 8400 4382 CC4C 1593 3B06 4710 \ E7B3 A1F8" FEATURE Database ALCHEMY 10.4 permanent 3 BORROW=336 SIGN="002E DEED \ E09D 6B23 285A FE47 AC22 4600 E413 58C7 8C66 9DC5 B923 01D4 \ AFCA" [...] On all 3 servers, follow these steps: - Stop and Close ANLM - Delete the "Alchemy License server - Catalyst" service (if installed already) command: sc delete "service name here" - Overwrite ServerLicensesCat.lic found in the public folder of the server example: C:\Users\Public\Alchemy Software\NLM with the attach license file. - Recreate the service, starting with the Primary server ( server01 ) using the .bat file in the ANLM folder 32bit OS C:\Program Files\Alchemy Software\NLM\InstallServiceCat.bat You will need to first update the LicensePath and ExecutablePath - Start the created service, starting with the Primary server ( server01 )
Once the servers are up and running, create the license file to be used by the Catalyst clients on the network. This text based file should be created in the public folder: C:\Users\Public\Alchemy Software\Catalyst X.0 This client.lic file should have the following format, using the details from the example above: SERVER server01 HOSTNAME=server01 SERVER server02 HOSTNAME=server02 SERVER server03 HOSTNAME=server03 VENDOR ALCHEMY USE_SERVER
NotesInternal ref only: fnp_PR-LF
Related topics
Products or Versions Affected
|
 |
 |
|
|
In this configuration, only one license server supplies licenses to the Catalyst clients. The other two are available in case that one fails. When at least two of the three license servers are running and communicating, the system serves licenses to Catalyst clients.
When the initial communication has been established, each license server periodically sends a heartbeat to the others. Heartbeats are messages sent over TCP/IP. Each license server sends a heartbeat and waits for a response from the other license servers. If a license server does not receive a response, it shuts down the vendor daemon so that it cannot serve licenses.