Page History

...

• Choose the Controller archive for the target system Windows systems and the graphical installer from the JS7 - Download page.
• For Windows systems a .zip archive including the installer is available from js7_controller_windows_installer.<release>.zip.

Installation

Extract the downloaded archive to a directory, e.g. C:\Temp.

After extraction of the installer .zip archive

...

the directory structure includes:

• controller_install.xml (installer response file)
• install_controller.txt (installation hintsnotes)
• js7_controller_windows.<release>.jar (installer library for a given release)
• license.gpl (copy of  GPLv3 (General Public License) )
• license.txt, license.html (copy of JS7 JobScheduler Commercial License Agreement)
• setup.cmd (installer script)

Consider the following implications before running the installer:

• The installer can be run in graphical mode or in headless mode, see JS7 - Controller - Use of Linux/Windows Headless Installation.

• The installer asks for elevated administrator administrative privileges, therefore it is not required to change the permissions in the .\service directory and the installer sets read/write permissions for the .\logs directory.
• After the installation you will find
  
  • a Windows Service "SOS JS7 Controller -id=<controller-id>"
  • an executable file .\service\js7_controller_<controller-id>.exe that is started by the Windows Service.

...

• Run the installer for the JS7 Controller using

  Code Block
  language bash title Windows command to run the graphical installer
  > C:\Temp\controller.<release>\setup.cmd

• The installer asks for administrative permissionsprivileges.  
• Select the language to be used for the setup: English and German are available.
  
  

...

• With the next window specify the Controller ID that is a unique identifier for a Controller. You can use identifiers such as "controller-test", "controller-production" etc.
• If you intend to operate a Controller cluster with two Controller instances for the active and for the standby cluster member, then specify the same identifier during installation of each Controller instance as otherwise the instances will not be considered members of the same cluster. This identifier cannot be modified after installation, changes to the Controller ID require reinstallation of the Controller.
  • A checkbox allows to specify if the currently installed Controller instance will initially start with an active or standby role. Do not select this checkbox if you operate a standalone Controller instance.
  • Consider that operation of a Controller cluster requires to add a license certificate from a previous above step, see JS7 - Licensing.
• Add the HTTP port that is used by the JS7 Controller. Make sure that the HTTP port is available , i.e. and is not otherwise used. If you run other applications that use this port then choose a different port.
• If you specify a Windows Service account then make sure that this account has "Log on as service permissions". Consider that credentials that you enter to this window are stored in clear text with the installer response file. It is considered more secure not to add credentials with this step, but to add credentials directly with the Windows Service panel after installation.
  
  

...

• The resulting directory structure after installation includes (only files and folders immediately relevant):
  • C:\Program Files\sos-berlin.com\js7\controller (installation directory)
    • bin
      • controller.cmd|sh
        • The Start Script for Windows/Unix platforms
      • controller_watchdog.cmd|sh
        • Restarts the Controller for Windows/Unix platforms
      • environment_variables.cmd|sh
        • Environment Startup Script for the JS7 Controller
    • libThe lib (directory for Java libraries)
    • service (directory for operation as a Windows Service)
      • amd64
      • manager
      • x86
      • install_controller_windows_service.cmd
      • js7_controller_<Controller ID>.exe
      • js7_controller_<Controller ID>w.exe
      • LICENSE.txt
      • NOTICE.txt
      • RELEASE-NOTES.txt
      • uninstall_controller_windows_service.cmd
    • user_bin
      • environment_variables.cmd|sh-example 
        • Sample configuration file to set individual environment variables. Drop -example extension to activate this file.
    • Uninstaller (Windows only, the empty directory remains in place after uninstall)
      
      • install.log
      • js7.ico
      • shortcut.vbs
      • uninstall.cmd
      • uninstall_prepare.cmd
      • uninstaller.jar
    • license.gpl (copy of  GPLv3 (General Public License) )
    • license.html, license.txt (copy of JS7 JobScheduler Commercial License Agreement)
    • ThirdParty.txt (list of 3rd party components and licenses included with the JS7 Controller)
  • C:\ProgramData\sos-berlin.com\js7\controller (configuration directory)
    • var
      • logs (directory for log files)
      • config (directory for configuration files)
      • state (directory for Controller journal files)

...