You can configure various settings for the Licence Server including TCP/IP port, UDP ports, server timeout and thread cache size. Changing these settings will require the Win32 service to be restarted manually, and all currently granted licences will be lost.
Licence Server Administration
All other changes to the settings don't require the service to be restarted and can be performed while workstations are connected and have been granted licences. In some situations, workstations will be forced to reconnect and request new licences. Press the Apply button to save the changes to the licence service.
Server Settings
TCP/IP Address
[Default: {Blank}]
The IP address or domain name of the workstation hosting the Arden Licence Server service you want to connect to and administrate. If the service is running locally, you can also use 127.0.0.1 or localhost.
TCP/IP Port
[Default: 3000]
The primary TCP/IP that Licence Server will listen on for incoming licence requests. Once connected to Licence Server using Licence Server Administrator, this port can be altered, following which the Licence Server service will need to be restarted before it begins to listen on the newly assigned port. This may be useful to avoid conflicts with other applications listening on the same port.
First UDP Port
[Default: 3000]
The initial UDP port that will be assigned to a client that is allocated a licence. This is then used by the Licence Server service to listen for incoming messages from the client, including those need to keep alive or return (revoking) an allocated licence.
Total UDP Ports
[Default: 2]
The total UDP ports on the Licence Server that can be utilised, including the First UDP Port.
Note. The total UDP ports is not a sum of required UDP ports, and it is not affected by the number of licences (CALs) installed on the Licence Server. It is only influenced by the maximum number of client processes that will be connecting to your Licence Server from the workstation or server with the highest number of clients. See TCP/IP and UDP Ports for more information on suggested configuration.
Advanced Settings
Timeout (secs)
[Default: 60]
This Server timeout value specifies the time, in seconds, that a client socket stream should wait before timing out on a read or write call, under the assumption that the socket connection has failed.
A small timeout makes the server more responsive to dead peers, but risks dropping slow clients during large payloads.
A large timeout is friendlier to slow networks but increases the time to detect dead connections and can tie up threads longer.
Note, this server timeout does not affect the length of time a client can maintain an allocated licence without responding to the Licence Server. That timeout behaviour is hard-coded are works as follows:
After an initial delay of 10 seconds from granting the licence, the Licence Server continually PINGs each client (~every 30 seconds) to ensure they still require the granted licences. A message is sent for each licence granted to a client. The client should respond to these messages by returning an ACKP (ACKnowlege Ping) message. The server allows a maximum of three pings to go unanswered before the server revokes and deallocates the licence locally, whilst issuing a final revoke message to the client. Conversely, if the client doesn’t receive a PING from the Licence Server within the last 2 minutes, it will automatically revoke all its licences
Thread Cache
[Default: 10]
The cache size Is used by the licence server to save destroying/creating threads to respond to incoming requests for initial licences, it does not affect the UDP broadcast thread, of which there is only one. Unless you are experiencing a large number of simultaneous requests for licences and some are failing, the cache size shouldn’t need to be changed from the default of 10.
Administrator Passwords
It is possible to password protect the connection to the licence service; this is recommended if the server running the licence service is available on a WAN. It prevents unauthorized access to the service settings. Separate passwords can be supplied for the Full Administrator and View Only modes.
Only a single administrator can be connected to the licence service at once; other administrator users attempting to connect to the service do so in View Only mode. This allows them to view the licences being used and revoke licences if required, but prevents them from making changes to the service settings.
View Only
If you start the Licence Server Administrator when another user is already connected from a different workstation, then you will have View Only access and the form will display as follows, without the advanced information on the Server Administration tab and without the Installed Licences tab:
Licence Server Administration in 'View only' mode
Connection Logging
The licence service can provide two levels of logging operation. The Log File specified must be a valid path on the server running the Licence Server. The Verbose log messages option will produce detailed logging of all data transactions performed by the Licence Server.
The server logging should only be turned on when instructed by technical support staff; leaving it turned on can slow down the server and use large amounts of disk space.