Configuring an On-Premises Redundant RMS License Manager Pool on Unix

To configure a Redundant RMS License Manager pool with an on-premises served network license, you need Root access to all machines you are using as a Sentinel license server to install the RMS License Manager and obtain the locking criteria of each machine. The utilities you need are provided in the Tools directory of your RMS installation.

Note: All RMS servers in your redundant RMS pool need fixed IP addresses. Dynamic IP addressing cannot be used for RMS servers running in a redundant setup.

To set up your redundant RMS License Manager pool on Unix machines:

Step 1: Install the RMS License Managers on each machine

Download the RMS installation package from Rocket Community: Downloads onto each machine where you want to run a redundant RMS License Manager.
Extract and install the package. During installation, choose the option Install RMS and I will configure the license later.

Do not start the RMS License Managers at this stage of the process. If you are configuring an existing RMS License Manager into a redundant RMS, stop the Sentinel RMS License Manager service.

For more detailed instructions on installing the RMS License Manager, see Installing the Sentinel RMS License Manager on Unix and Linux.

Step 2: Activate and download your License File

In the course of license activation, you will need to run the echoid command line utility (located in the Tools directory of the RMS installation) to generate a locking code for each RMS License Manager in the pool.

Log in to the Sentinel EMS customer portal with your Entitlement ID and click Activate. The activation screen shows the number of redundant RMS License Managers defined in your Entitlement, and the Primary criteria for each machine, in this example, Disk ID. Take note of these Primary criteria as you will need them in the next steps as your locking criteria.
For each machine where you have installed the RMS License Manager, enter the locking criteria (Primary criteria) and generate a Locking Code using the echoid tool, and copy it into the Primary n info field on the portal.
To obtain the Locking Code using echoid:
1. Open echoid.dat from the \Tools directory.
2. Edit the last line of the file to match the locking criteria listed on the Sentinel EMS customer portal's activation screen, and save the file. In case of multiple locking criteria, calculate the locking data by adding the hexadecimal values of the different criteria.
  For this example, enter 0x004 to select Disk ID as the locking criteria:
```
# Some Examples
# All criteria 0x3D9F or 11110110011111
# IP Address only 0000000000010 or 0x2
0x004
```
3. Run echoid or echoid64 from the command line. This reads the locking data from echoid.dat and generates a Locking Code.
```
[root@yellow tools]# ./echoid64

Sentinel RMS Development Kit 9.8.0.0048 Host Locking Code Information Utility
Copyright (C) 2021 Thales Group
All Rights Reserved.
 
       Locking Code 1     :   4-*1VH TTBW LQ4F AAAA 
       Locking Code 1 (Old Style) :   4-27679
						
```
4. Copy the generated Locking Code from * to the end and paste it into the Primary n info field on the Sentinel EMS customer portal.
When you have completed the previous step for all RMS License Manager hosts, click Activate.
Download the generated lservrc license file and make a note of the saved location.

Step 3: Configure your RMS License Manager Pool

To configure your redundant RMS License Manager pool, run the rlftool located in the \Tools directory of your RMS installation.

Run the rlftool from the command line.
Create a new file for the license using the following command: rlftool -l "file name". Enter the full path and name of the file, or point to an existing file.
For example:
```
rlftool -l /h/user/lservrlf
```
Note: You can choose your own file path and name. Take note of the location and name to refer to later.

Enter Y when prompted to create a new file. This loads the file with a number of menu options.

[root@yellow tools]# ./rlftool64 -l ~/lservrlf
 
  Sentinel RMS Development Kit 9.8.0.0048 REDUNDANT LICENSE FILE TOOL
  Copyright (C) 2021 Thales Group  
    All Rights Reserved.

File /root/lservrlf does not exist. Create New (Y/N) or Quit(Q): y
File [/root/lservrlf] loaded.
								
            [RLFTOOL MAIN  MENU]
1. OPEN                   Open or Create New Redundant License File.
2. ADD/DELETE SERVER      Add or Delete Server Names in pool.
3. POOL NAME              Edit pool name.
4. PREFERENCE ORDER       Change or View Preference Order.
5. SEQUENCE NUMBER        Change file sequence number.
6. TIME STAMP             Change file timestamps.
7. ADD LICENSE            Add new license.
8. VIEW LICENSE           View Licenses.
9. DELETE LICENSE         Delete license.
10. CONFLICTS              List or Resolve license Distribution conflicts.
11. REPORTS                Generate Licenses reports.
12. EXIT AND SAVE          Terminate tool.

Select Option (1..12):

Enter 2 for the option to add or delete a server.
1. Following the prompts, enter 1 to add a new server.
2. Enter the server name.
3. Enter the IP address of the server.
  Repeat this process for each server you are adding.
  Note: The order you list the servers determines the order of the redundant RMS server pool. The first server listed is the leader RMS in the pool and acts as the primary RMS. The next one is the first fallback, and so forth. To change this order, enter 4 from the main menu.
From the main menu, enter 3 to view and change the pool name.
Enter 7 to add the license.
1. Enter 1 to add the license file or 2 to add the license code.
2. If you select the license file, enter the full path to the saved license file. If you choose to use the license code, enter each line of the license file individually.
  Note: Each line in the license file is a license code for a particular feature. We recommend using the license file unless you wish to add only a few license features to your RMS.
Enter 12 to exit and save your changes.
Copy the lservrlf file you created using rlftool into the RMS installation (for example, /opt/Uniface/rms/) on each machine you installed the RMS License Manager.
Start the Sentinel RMS License Manager service on each machine.

Step 4: Configure your Uniface application

In your application's assignment file, add the hostname or IP address of each redundant RMS to your LM_LICENSE_FILE options, separated by a semi-colon. For example:
```
$license_options=LM_LICENSE_FILE=machinename1;machinename2;machinename3
```
Note: The order you list each RMS must match the order of the redundant RMS pool you configured in the Redundant License Manager Configuration file (lservrlf). If you change the order using rlftool or WRlftool, you need to change the order in the assignment file too.
Start your Uniface application.