Page History

...

• A Java Runtime Environment starting from version 1.8 is required.
• For details see Which Java versions is JobScheduler available for?

Preparation

• Choose the Controller archive for the target system from the JobScheduler DownloadsDownload page.
  
  • For Unix systems :A an installer .tar.gz tarball archive is available that can be used for:manual installation of one or more instances on a small number of computers.
  • For Windows systems :A an installer .zip archive is available that can be used for:
  • manual installation on a small number of computers.
    (Described in the current article.)
  the installation of a large number of Agents using third-party deployment tools.An installer that can be used for manual installation of a small number of computers.
  (Explained in detail with the JS7 - Controller -

Installation

...

Installation

• • Unzip the downloaded file archive to an arbitrary directory.
  • Directory structure (only files and folders directly relevant):
    • bin
      • controller.cmd|sh
        • The start script for Windows platforms.
      • controller_watchdog.cmd|sh
        • Notes the task that is being forwarded for execution by a JS7 Controller to Agent
      • environment_variables.cmd|sh
        • includes environment variables used by JS7 Controller
    • lib
      • The directory for Java libraries.
      • Configure the settings in log4j2.xml file if you want to adjust the logger settings.
    • service (for Windows)
      • amd64 (directory)
      • manager (directory)
      • x86 (directory)
      • install_controller_windows_service.cmd
      • js7_controller_<Controller ID>.exe
      • js7_controller_<Controller ID>w.exe
      • LICENSE.txt
      • NOTICE.txt
      • RELEASE-NOTES.txt
      • set_java_home_for_jetty_windows_service.cmd
      • start_jetty_windows_service.cmd
      • uninstall_controller_windows_service.cmd
    • user_bin
      • environment_variables.cmd-example - example script to set the Controller environment variables (Microsoft Windows)
    • Uninstaller (the empty directory remains after uninstall)
      
      • install.log
      • js7.ico
      • shortcut.vbs
      • uninstall.cmd
      • uninstall_prepare.cmd
      • uninstaller.jar
    • var
      • logs
      • config
      • state

...

• The Controller log level can be increased using the Controller's Apache ProcRun Demon Service Manager demon/service.
• On Windows systems, this is installed in the Controller service Folder and will have a name such as js7_controller_<Controller ID>w.exe  where Controller ID is the unique ID for the Controller 
• Start the ProcRun Manager, select the Logging tab in the Manager interface and set the level to Debug. 
• The location of the log files has already been described above. 
• (Do not forget to set the debug level back to Info once finished.)

...

Behavior in the event of the Controller crashing

The Controller is the component in JS7 that holds the job-related configurations and orchestrates the Agent. The outage of a Controller instance does not prevent the execution of workflows having the jobs running on a single Agent. However, it affects the execution of workflows that include jobs that are running on a number of Agents as switching of Agents during workflow execution is performed by the Controller. Refer the article JS7 - Troubleshooting - How to troubleshoot the outage of a Controller for details.

...