In most production deployments it is desirable to run REM as a daemon.
Remd
The remd.sh
script starts the Rhino Element Manager as a background service and provides basic control actions.
This script does not provide control of REM instances started with the rem.sh
script, even if they share the same $REM_HOME
.
Usage: ./remd.sh {start|stop|restart|check}
Command | Action |
---|---|
start |
Start REM as the |
stop |
Stop the REM server process |
restart |
Restart the REM server |
check |
Check the REM process is running |
Init script
A sample init script is provided in init.d/rhino-element-manager
, offering similar functionality to remd.sh
for operating systems using a SystemV type init system.
This script is written for LSB compliant Linux systems and must be modified for other systems.
Command | Action |
---|---|
start |
Start REM as the |
stop |
Stop the REM server process |
restart |
Restart the REM server |
status |
Check the REM process is running |
Configuration of the init script may be provided in the system environment or by editing the values at the top of the file.
Variable |
Value |
REM_USER |
Username of the user to run the REM server as. |
REM_HOME |
Path to the |
JAVA_HOME |
Path to the base directory of the JDK used to run REM. Typically this will be a path like |