Versions Compared

Old Version 2

changes.mady.by.user Paul Metcalf (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Craig Bechelli (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
RMS does not support servers with numeric host names. The License Manager may not start on such machines due to external dependencies.


The License Manager usually runs on a computer within the network where users (clients) have installed the licensed application. See the diagram below:

Multiple Clients Accessing the Sentinel RMS License Manager

Usually the licenses reside on the License Manager in a license file. On startup, the License Manager reads the licenses from the file and creates a license table. Otherwise, these are added dynamically to the License Manager. The dynamically added licenses are only available in the License Manager memory. Once the License Manager is stopped these licenses are lost.

You program your application to look for a License Manager with available licenses.

When the licensed application is run on a client, a request is sent to the License Manager for obtaining an authorization. The License Manager processes the request (including the task of authenticating the clients, if required) and returns the status to the client. The License Manager maintains each request separately, treating these authorizations as separate clients.

Image Added

Client Requesting for a Network License



Here are some quick facts about the RMS License Manager:

Operating systems supported
Windows 32 and 64-bit
For specific versions, refer to the release notes or contact the Technical Support.

Installation Path
The default installation path on Windows is:
Windows 32-bit - <Osdrive>:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT. 
Windows 64-bit - <Osdrive>:\Program Files(x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT.

Network protocol       
A client can contact the License Manager using the IPv4 or IPv6 communication protocol. When the License Manager is hosted on a dual stack system, both IPv4 and IPv6 clients can communicate with it, however, not all combinations are supported (see the illustration below for more information):

License Manager           Host Protocol    Client-side Protocol      
                                       IPv4                  IPv6

IPv4                              Supported         Not supported
IPv6                              Not supported   Supported
Dual stack                    Supported         Supported

Network port (default)           
5093

Network reach            
Broadcasts within a subnet. Directed calls can access License Manager across subnets.