This a more advanced way of working with a node which allows more user control over node settings than starting a node from code.
One can say that this makes JMP node a "server" which is planned to be running for extended periods of time.
Starting a node from code, on the other hand, might be a good approach when a limited set of (parallel) tasks must be proceeded within one bigger program.
This node will be stopped either from code or automatically upon program exit. In theory, most of the commands available for node set-up via admin panel are available in code as well, e.g.
void Node.addSlaveNode(String slaveNodeIP)
void Node.setNodeSelectionPolicy(int nodeSelectionPolicy)
...
To start a node from terminal, call the class with one or multiple arguments:
Activate verbose mode (always recommended in a terminal):
java org.engitex.JMP.StartNodeAdminPanel -v
Load node setting from profile which is in ./profiles dir:
java org.engitex.JMP.StartNodeAdminPanel -l my_profile
Set custom security policy, otherwise the default JMP policy (very permissive!) will be used:
java org.engitex.JMP.StartNodeAdminPanel -p my_policy
After the node has been started, a user might interact with it (e.g. change the settings) with interactive commands.
To see the list of available commands, enter help