Search
Close this search box.
Try RLM for Free
Search
Close this search box.
How Can We Help?
< All Topics
Print

RLM Server Ports

UpdatedJune 14, 2024

Default Ports

For a basic RLM server install with licenses from one Software Vendor (ISV), the server will use the following ports:

  • 5053 – Default RLM server port
  • 5054 – Default web administration port (embedded web server)
  • A port between 1024 and 65353 – The ISV server port, dynamically assigned at startup.

 

Setting custom ports

License File

The RLM and ISV server ports are set in the license file provided by the ISV. ISVs may elect to specify custom ports for their applications, and a single RLM server may contain licenses from multiple ISVs.

The RLM server port can be specified on the HOST line of the license file. For example, if specifying port 6053:

HOST dns-name server-hostid 6053

The ISV server port can be specified on the ISV line of the license file. For example, if specifying port 6055:

ISV isv-name port=6065

 

RLM Startup/Service

The web administration port is set in the RLM service, or at program launch. End users may want to configure the web service for their environment. The “-ws” option is used at startup, or when creating the RLM service. For example, if specifying port 6054:

rlm -ws 6054

The license server would then be accessed using the URL: http://dns-name:6054
 

UDP broadcast

By default, RLM servers will attempt to listen for broadcast requests from client applications looking for a license server. The broadcast method of finding a license server is the last attempt a client application will make when trying to find a license server, not all ISVs use this method.

Broadcast requests will always be sent on port 5053, this port cannot be changed.

The server administrator can instruct RLM not to listen to broadcast requests. This may be desired if there are multiple RLM servers on a network, or if multiple RLM processes are running on a single server. At startup, or when creating an RLM service you can specify “-noudp” to disable the broadcast listening. For example:

rlm –noudp

RLM and RLM
Activation Pro

What’s the difference?

Reprise License Manager (RLM)

Software License Manager

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

As a Software publisher, you integrate RLM into your product, and RLM keeps track at runtime of who is using the licenses of your software.

RLM can do this entirely within the client library (linked into your application), or, more commonly, your application makes a request of the RLM Lincese Server to check out a license.

The lincese server runs either on your customers network, or in the cloud if you are using our RLMCloud™ service.

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

RLM Activation Pro

Software Activation Manager

Activation Pro is
used once when your customer purchases your software in order to retrieve the license which is specific to that customer.

Software Activation’s purpose in life is to get the licenses for your product to your customers with a minimum of fuss.

Activation Pro also has a server component wich we call the activation server.

Your application contacts the activation server and supplies a short text activation key, and in exchange, the activation server returns the license which enables your product.

Generally, this is done once, right after your customer purchases your software, not every time your software is invoked.