Rhino Element Manager 3.2 :: Rhino Element Manager (REM) Guide :: Installing, Starting and Logging in to REM

This page has been updated to reflect that REM no longer includes Jetty in its distribution package. For REM versions 3.2.15 and earlier, which included Jetty 10, the Installing, Starting and Logging in to REM page in the REM 3.1 documentation set is more relevant.

Prerequisites

Running Rhino Element Manager 3.2.16 or later requires:

Java 17 or 21 (refer to the Rhino Compatibility Guide).
Jetty 12.1.x, downloaded separately from jetty.org. REM no longer bundles a Jetty distribution.

Set the following environment variables before running REM:

Variable Value

Variable	Value
`JAVA_HOME`	Path to JDK 17 or 21 installation directory (e.g. `/opt/jdk-21.0.4`).
`JETTY_HOME`	Path to the Jetty 12.1.x installation directory (e.g. `/opt/jetty-home-12.1.9`).

JAVA_HOME

Path to JDK 17 or 21 installation directory (e.g. /opt/jdk-21.0.4).

JETTY_HOME

Path to the Jetty 12.1.x installation directory (e.g. /opt/jetty-home-12.1.9).

Quick start for testing and development

To run the Rhino Element Manager:

Ensure the JAVA_HOME environment variable points to a Java 17 or 21 installation (refer to the Rhino Compatibility Guide).

Download Jetty 12.1.x from jetty.org, extract it, and set the JETTY_HOME environment variable to point to the extracted directory.

Run the rem.sh script.

Open http://localhost:8080/rem/. The Rhino Element Manager login page displays.

Derby database and Jetty web server

REM uses an Apache Derby instance to store Rhino instances and REM users. If it does not already exist, the REM installation creates this instance in a directory called rem_data (in the current working directory).
The database runs in embedded mode, so it does not accept incoming TCP connections.
REM runs as a web application inside the Jetty web server you provide. To change the port number, edit start.ini and uncomment the jetty.http.port property.

Logging in to REM

To login to REM:

Enter your username and password, and click Login. The REM menu displays.

The default administrator login (which you’ll want to change) is username emadm and password password.

Depending on your permissions, buttons display for up to four types of REM operations:

Manage a Rhino Element
Monitor all Rhino Elements
Edit Rhino Instances
Edit Element Manager Users.

If this is the first time REM has been used you will probably need to either:

add a Rhino instance; or
add a server certificate to the automatically created 'Local' Rhino instance.

Running REM as a production service

When installing REM as a production service, ensure REM availability and security by:

Running REM as a daemon, by either:
- Running REM as a daemon using the Jetty web server.
- Running REM on Apache Tomcat by deploying the REM web application resource (WAR) file.
Using only HTTPS to reach REM, either by Running REM over HTTPS directly, or by putting REM behind an HTTPS terminating application like Tomcat, nginx, or the Apache web server.
Using a centralized LDAP service for authentication to provide centralized account management and policy enforcement.

REM’s communication with Rhino is always protected by TLS, and REM will insist you provide a TLS server certificate to trust before allowing connection to Rhino.

Both rem.sh and remd.sh require JETTY_HOME to be set in addition to JAVA_HOME. When configuring the systemd unit file or SystemV init script, add a JETTY_HOME entry alongside JAVA_HOME and REM_HOME.

Previous page Next page