Quick start for testing and development

To run the Rhino Element Manager:


Ensure the JAVA_HOME environment variable points to Java 11 or 17 (Refer to the Rhino Compatibility Guide).


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 in a Jetty web server. You can configure the web server (for example, if you need to change the port number), by editing jetty.xml.

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:

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.

Previous page Next page