Unix Service
This software contains two separate programs. An administrator user interface and a scheduler engine program which runs in the background. By default, the scheduler engine in the background is not started with the 'nohup' command. Hence, when you logout, the scheduler may shutdown. By using the 'nohup' command to launch the scheduler engine, the scheduler engine will keep running after user logout.
Restart engine using launch code
You can relaunch the engine using the 'Restart engine using launch
code' button. This will automatically shutdown the current instance
of scheduler engine and restart it using the new 'nohup' code.
Recommended nohup launch code
The recommended command to launch the engine using 'nohup' is shown
in the text box. You can edit it as you wish.
Save code and always launch scheduler engine using this launch
code
Select this checkbox, if you wish to always use nohup to launch the
scheduler engine.
Important Note
If you are relaunching the scheduler engine through a script or from
a terminal, make sure that you shut down the scheduler engine through the
user interface first.
Default Scheduler Engine Launch Code
If you used the install with JVM:
jre/bin/java -cp .:inputs:images:activation.jar:mail.jar:NetComponents.jar:jclasses.jar
JSEngine
or if you used the install without JVM and java is in your path
java -cp .:inputs:images:activation.jar:mail.jar:NetComponents.jar:jclasses.jar
JSEngine
Note: On some systems, like Linux Redhat 7.0, 'nohup' is not needed. The scheduler engine may keep running on logout, even if launched without 'nohup'. On Solaris 8.0, the scheduler engine will shut down if 'nohup' is not used.