License Server Administration

The StrataBugs licence manager is RLM, from Reprise Software. Reprise provide comprehensive documentation.

Setting up the licence for a floating server

Download the latest version of the RLM License Administrator Bundle from the RLM site.
Unpack the zip into the destination folder e.g. C:\RLM

Do NOT install into "Program Files" on Windows as this is a protected area which will prevent the password process working.
Run the rlm application to find the hostid of your server:
```
rlmutil rlmhostid
```
Report the output code(s) to StrataData who will issue a licence file. Also report the host name, so this can be included in the licence file.
Download the StrataData licence daemon from here (or here for versions prior to 15.1), and extract the two files into the rlm binary folder.
When you receive the licence file, put it into the rlm folder, and run the licence manager from the command line:
```
rlm -c <licence file name>
```
If there are errors, report the error messages on rlm startup.

If there are no errors, then you should test this with your StrataBugs client application by setting the RLM_LICENSE environment variable, or copying the licence file to the StrataBugs application folder (or %PROGRAMDATA%\stratadata)

When the application starts, you should see an "OUT" message from rlm on the command line, and an "IN" message when you close StrataBugs.

There is a browser interface to the rlm process which should run on port 5054 by default http://hostname:5054
If there are no errors, stop the process wth Ctrl-C and go to the next step of installing RLM as a service.

Installing as a service

For version 15.1 and above

The service name parameter is optional. From v15.1, the web service will need a username and password to access. The default is admin/admin. The folder indicated in the dlog parameter must exist.

You must log in to the web interface (http://localhost:5054) within 10 minutes to set the admin password. If you don’t do this, the isv servers will shut down.

To add a new user you edit the file rlm.pw, add the user and within 10 minutes open the interface and set a password. See the RLM documentation for more details.

rlm -c <licence file> -install_service -service_name rlm-v15  -dlog C:\dev\rlm.v15.1BL1-x64_w4\log\server.log

Port setting

You might need to modify your firewall or Windows Defender to open the ports that RLM uses. You should open the incoming ports for the RLM and ISV servers, and for the web server if necessary. You can use the information from the web interface or the rlm startup command to see which ports it uses. The default ports are:

RLM 5053 - OR defined on the HOST line of the licence (.lic) file e.g.

HOST MYHOST 005046b54e87 5053

Web server 5054
ISV server - assigned at runtime OR set in the licence (.lic) file on the ISV line e.g.

ISV stratadata port=49695

Toubleshooting "Connection refused" errors

Sometimes in troubleshooting problems with clients connecting to license servers, it’s useful to have a tool outside RLM which can tell you whether messages can get through to the server. If a firewall or anti-virus package or proxy is blocking comms, a separate tool will have the same problems connecting to the server as RLM.

On Linux/Unix: Simply attempt to connect to the running RLM license server with telnet. Note the name of the license server you’re trying to check licenses out from, the main RLM port number, and the ISV server port number. The port numbers can be found in the server side diagnostics.

For example, if rlm running on the machine server123 and is listening on port 5053, and the ISV server is listening on port 12345, try:

telnet server123 5053
telnet server123 12345

If telnet can get through, you'll see a message like this:

Trying xxx.xxx.xxx.xxx...
Connected to server-123 (xxx.xxx.xxx.xxx).
Escape character is '^]'.
Type control-] and quit to exit telnet

But if telnet cannot get through you’ll see a message like this:

Trying xxx.xxx.xxx.xxx...
telnet: connect to address xxx.xxx.xxx.xxx: Connection refused
telnet: Unable to connect to remote host: Connection refused

On Windows: If you have telnet available you can use it as you would on Linux/Unix. If you have access to PowerShell on your system you can run Test-NetConnection. For example, if rlm is running on the machine server123 and listening on port 5053, and the ISV server is listening on port 12345 try:

Test-NetConnection -ComputerName server123 -Port 5053
Test-NetConnection -ComputerName server123 -Port 12345

If successful the response will look like:

ComputerName     : server123
RemoteAddress    : xxx.xxx.xxx.xxx
RemotePort       : 5053
InterfaceAlias   : Ethernet
SourceAddress    : xxx.xxx.xxx.xxx
TcpTestSucceeded : True

If not successful:

WARNING: TCP connect to (45.58.39.56 : 12345) failed

 ComputerName     : server123
RemoteAddress    : xxx.xxx.xxx.xxx
RemotePort       : 5053
InterfaceAlias   : Ethernet
SourceAddress    : xxx.xxx.xxx.xxx
PingSucceeded          : True
PingReplyDetails (RTT) : 94 ms
TcpTestSucceeded       : False