Simple Server mode

Server mode

Purpose

To run JRomManager directly on headless devices, like NAS, without the overhead of network when processing files

How to install?

This is the same package than the "JRomManager standalone", so it is installed the same way, the difference may be that you will install it on your headless device or server instead of installing on your client machine

How to run (server side)?

Manual launch

• open a shell or a cmd window,
• then cd into the jrommanager install dir
• run the following: java -Dfile.encoding=UTF-8 -cp JRomManager.jar jrm.server.Server --port=8080 --client=webclient --workpath=.
  If you don't have rights to write into the install dir, then you will have to set --workpath to an absolute path with write access rights and also set --client to an absolute path too

As a service at boot

On Windows

• navigate into <jrommanager install dir>\wrapper\bin
• run InstallApp-NT.bat this will install the service and make it autorun at next reboot
• run StartApp-NT.bat to launch it immediately

On *nix

• open a terminal
• cd into <jrommanager install dir>/wrapper/bin
• sudo ./launcher.sh installstart

Arch Linux and derived

If launcher.sh fails to install then retry the script after creating either /etc/redhat-release or /etc/debian-release with touch command, then delete it after installation succeeded

Gentoo Linux and derived

openrc is not supported, use systemd or create your own openrc's service script

How to use (client side)

• Launch your favorite browser (chrome or firefox are preferred)
• Point to http://<yourserver>:8080
• You should start to see the web client app, otherwise something goes wrong and you should start to see at log files

Notable differences with standalone mode, limitations and words of caution

• The filesystem exposed from the file/dir chooser is the one from your server NOT your client
• If you need to send files or dir from your client machine to your server, then you can use "Manage file uploads" on "Profiles" tab, then drag & drop your files/dirs into the main file requester window
• You may get less refresh in the progress bar and lists, this is the best that we can get in a client/server environment, it would be worse without websockets usage, and it will be worse with high latency connections like non wired ones. As a side note, if you are frequently disconnected, then you connection is too bad, it's up to you to get the best connection with your server
• You should avoid to close or hide your client page, as it may break the link with the server due to some browser restrictions with websockets, and don't even think to let your laptop go into standby mode
• Using a proxy in between your client and your server may not work at all depending on the proxy, and no tests has been made
• You should avoid using it from the internet since it will expose your filesystem, furthermore communications are not currently encrypted