Installing the Sentinel RMS License Manager on Unix and Linux

The Sentinel Rights Management System (RMS) License Manager (also known as the RMS Server) enforces and manages licenses for Uniface in multi-user environments.

On some Linux systems (RedHat, SUSE, and CentOS), it is also possible to install the Sentinel Cloud Licensing Add-on (also known as the Sentinel Cloud Plug-in).

Prepare to Install

  1. Before starting, it is useful to have the Sentinel license file or license code, or the email from Uniface with your Entitlement ID (EID) for a cloud-served license. It is also possible to configure the license after installing the RMS License Manager.

    If you are using a license file, download it onto your system and take note of the directory location.

  2. Download the installation package onto your system.
  3. Extract the package, either into a temporary directory, or into the directory where the RMS License Manager is to be installed.
  4. Log in as root, or use su to become root.

    Root privileges are required to install the RMS License Manager and Cloud Plug-in.

  5. Change directory (cd) to the directory where you extracted the package.

Run the Installer

  1. Start the installation script installrms.sh, then press Enter on the first prompt.
    ./installrms.sh

    If the Sentinel Cloud Plug-in is not supported on your system, the script informs you of this.

    Note: To run the installation script non-interactively, run installrms.sh with arguments. For more information on how to do this, see Silently Installing the RMS License Manager on Unix and Linux.

  2. Read and accept the Thales RMS license agreement. You can choose to enter d to display it on screen, or view the RMS-EULA.txt file included in the extracted contents of the installation package.
    • d—display the License Agreement on screen. Page through the License Agreement on screen using the space bar or Enter key, or press q to quit.
    • y—accept the terms and continue with the installation.
    • n—reject the terms and stop the installation.
  3. Enter the path where you want the RMS License Manager installed (for example: /opt/rms), or press Enter to use the current directory as the installation directory.

    If the path you entered does not exist, you are asked to confirm that the directory will be created now.

    Note: If you enter a path with a space, a warning is displayed. We recommend that you not include spaces in your directory path because the script will not be able to start the RMS License Manager, and you will need to do so manually.

  4. When prompted, choose the type of license you will be using:
    • Cloud Served License—both the RMS License Manager and the Cloud Plug-in will be installed. This option will only appear on supported Linux platforms.
    • License File or License Code—only the RMS License Manager will be installed.
    • Install RMS and I will configure the license later—the RMS server and the Sentinel Cloud Plug-in will be installed but not started.
  5. For a cloud-served license, provide details to configure the Cloud Service Plug-in and proxy server:
    1. Enter your Entitlement ID (EID). You can copy and paste this ID from the email you received from Uniface containing license activation information.
    2. Enter an additional Entitlement ID, if applicable, or press Enter to continue. You can enter as many Entitlement IDs as required.
    3. You can now choose to configure a proxy server, if you use one.
      • No proxy will be used—proceed to the next step.
      • Proxy server needs to be configured—at the subsequent prompts, provide the proxy server's host name (mandatory), port number (optional), a proxy user name, (optional), and the password of that user (optional).
      • Automatic—at the subsequent prompt, enter the path or URL to a .pac file. If you don't provide a path or URL the default URL https://wpad/wpad.dat will be used.

        • If no proxy server is chosen, the installer tries to contact the Sentinel Cloud server before continuing. If it cannot be reached, the script will ask you to check your connection or firewall settings. Select yes (Y) to retry, or no (N) to exit the script and cancel the installation.

    4. Provide a unique name (friendly name) for this machine, or press Enter to use the default machine name.

      The friendly name is a human-readable fingerprint used to uniquely identify your machine in the EMS customer portal. You can change this to something that is meaningful to you. The friendly name is restricted to 30 characters, containing letters, digits, underscores, and hyphens.

      Note: If you use cloud-served licenses on more than one machine, ensure that you choose a friendly name that is not already used on another machine. Otherwise, this will interfere with the cloud license of both machines.

  6. For a license file, enter the full path of to the license file, including the license file name.

    If you don't have a license file yet, or you have a license code, or if you wish to use the Sentinel RMS License Manager Administration utility to upload your license, press Enter. You will then need to copy the file to the correct location yourself at a later stage, and use the provided lslic utility or Sentinel RMS License Manager Administration utility to configure the license file or code.

  7. The installer now proceeds to activate your entitlement (in the case of a cloud-served license), copy and generate files into the installation directory, and create service scripts. For more information, see Service Scripts.
  8. If prompted, choose whether to open port 5093 in your firewall now. This port must be open for incoming requests from Uniface applications, and must not be blocked by the firewall. You can choose to have the script do this now, or do it yourself manually later.

    On some systems (such as Solaris), you will have to open port 5093 protocol UDP manually when installation has finished. Otherwise you can choose to have the installation script do it now.

    • n—do not open the port. Choose this if you do not have a firewall running, or port 5093 is already open, or you plan to do this manually later. The script will print the commands you can use to manually open the port.
    • y—the port will be opened for the UDP protocol using firewall-cmd, ufw, or iptables (on Linux), or genfilt on AIX. If none of these commands is found, or if the command fails, you are informed that the port could not be opened.
  9. When prompted, choose whether to start the RMS License Manager now. If you want to do so later, see Starting and Stopping the Sentinel RMS License Manager on Unix and Linux.

Next Steps

  1. If you extracted the package to a temporary location, remove the extracted files; they have been copied to the installation directory.

    If you extracted the package into the permanent installation location, do not remove anything.

  2. To connect a Uniface application to the RMS License Manager, specify the location of the RMS in the application assignment file, as specified:

    $license_options = LM_LICENSE_FILE = RmsServerHostMachine

Service Scripts

During installation, service scripts are created. These scripts ensure that the RMS License Manager (and Cloud Plug-in, if applicable) is stopped when the system is shut down and that it is started automatically when the system starts up again.

On Linux systems, a service script is created in /etc/init.d

  • If your Linux system uses sytemd, systemd-sysv-install is used to convert the script in /etc/init.d into a service that can be started and stopped with systemctl start / stop.
  • If your Linux system does not use systemd, the rms service is created using insserv, chkconfig, or update-rc.d, depending on your distribution.
  • If available, ulic /act is started to activate your cloud-served license and generate a cloud configuration file in /etc/sentinel-scp.

On Solaris, a script called rms is created in /etc/init.d with hard links to it in /etc/rc0.d with names that end with rmsd.

On AIX, service scripts are generated in /etc/rc.d/rc2.d.

Troubleshooting

The installation script checks that the RMS License Manager and, if applicable, the Cloud Plug-in are running. If one of them is not running, it will report that it failed to start.

  • If the RMS License Manager failed to start, examine the log file it has produced:

    InstallationDirectory/rms.log

  • If the Cloud Plug-in failed to start, examine the log file it has produced:

    InstallationDirectory/scp.log

  • If both started correctly but after waiting for 10 seconds a license file still hasn't been downloaded, examine the Cloud Plug-in log file for errors:

    InstallationDirectory/scp.log

  • If you have entered an incorrect Entitlement ID, or if the proxy settings are incorrect, you do not have to run the installation script again. Instead, you can directly edit the sntlcloudp_configuration_unifacebv.xml file that resides in /etc/sentinel-scp.

    After correcting them in this file, stop and start the service as described in Starting and Stopping the Sentinel RMS License Manager on Unix and Linux. After a few seconds your license file should appear in your installation directory (lservrc).

If you encounter errors or unexpected messages when installing the RMS License Manager, examine the installation log install-DateTime.log in the current directory. When contacting support, please supply the installation log file.