Silently Installing the RMS License Manager on Unix and Linux

It is possible to install the Sentinel RMS License Manager without user interaction, which may be useful when deploying RMS License Managers to multiple users.

On some Linux systems (RedHat, SUSE, and Debian), it is also possible to install the Sentinel Cloud Licensing Add-on (also known as the Sentinel Cloud Plug-in) silently. This is used for cloud-served licenses.

You can silently install the RMS License Manager by running installrms.sh with arguments.

Arguments

When installing the RMS License Manager silently, use the arguments required for your license type and environment to configure your installation. The following arguments can be used:

  • -installtoDirectory

    Specify the directory in which to install the RMS License Manager, for example /opt/rms. If omitted, the current directory is used as the installation directory.

  • -licLicenseLocation

    For an on-premises network license, specify the full path to the license file location.

  • -eidEntitlementId

    Activate an Entitlement ID (EID) for a cloud-served network license. To activate more than one Entitlement ID, enter each one as a separate argument, for example: 

    ./installrms.sh -eid 12345abc -eid 67890def
  • -fnFriendlyName

    Optionally, specify a friendly name. If not specified, your default machine name is used.

    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.

  • -prxhostHostName 

    If using a proxy server for a cloud-served network license, specify the proxy host name. If not specified, no proxy is used. To further configure the proxy server, you can use the remaining optional arguments.

  • -prxportPortNumber—the proxy server's port number (optional).
  • -prxuserUserName—the proxy user name for the proxy server (optional).
  • -prxpwdPassword—the password for the proxy user name (optional).
  • -prxauto—automatically configure the proxy server.

    The script automatically uses the default URL https://wpad/wpad.dat if no .pac file is specified.

  • -installonly

    The RMS License Manager and the Sentinel Cloud Plug-in are installed but not started. This is equivalent to choosing the interactive installation option Install RMS and I will configure the license later.

Silent Installation from the Command Line

  1. Download the installation package onto your system.
  2. If you have a license file, also download it onto your system and take note of the directory location—you will need it later.
  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.
  6. Start the installation script installrms.sh, using the required parameters.

    For example, to install the RMS License Manager with the following parameters:

    • Installation location: /opt/rms
    • License type: Cloud-served network license
    • Entitlement ID: 12345abc
    • Friendly name: UserMachine1
    • Proxy server: None

    Run the installrms.sh file with the following arguments:

    ./installrms.sh -installto /opt/rms -eid 12345abc -fn UserMachine1
  7. 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.
  8. 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

Troubleshooting

The RMS License Manager installation script sets an exit code on completion when run silently. Errors are also reported in the log file.

The following exit codes indicate an error with the arguments used:

  • 1—missing argument value. This occurs if you provide an argument without entering a value.
  • 2—incorrect Entitlement ID.
  • 3—invalid friendly name.

Related Topics