Page History
...
- First of all, you don't need to read this article in all its parts. For most situations it is sufficient to check the prerequisites, download the software and run the installer that will guide you.
- In this article you find the details about available installer options, updates and rollback for interested parties.
- The Controller can be installed by use of the graphical installer, for headless installation see JS7 - Controller - Headless Installation on Linux /and Windows.
Prerequisites
- A Java Runtime Environment 1.8 or newer is required. For details see Which Java versions is JobScheduler available for?
- It is necessary that a time service is operated on the server which hosts the Controller. This is to synchronize the system clock's time.
- Technically the Controller can be operated in any Unix environment. Note, however, that the JS7 - Platforms article describes support for Controller operation in more detail.
...
The installer can be run in graphical mode or in headless mode, see JS7 - Controller - Headless Installation on Linux /and Windows.
- The installer asks for elevated 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.
- a Windows Service "
...
- The resulting directory structure after installation includes (only files and folders immediately relevant):
C:\Program Files\sos-berlin.com\js7\controller
(installation directory).js7controllerinstallinformation
(binary installer information).version
(release information)controller_install.xml
(installer response file used from previous installation)license.gpl
(copy of GPLv3 (General Public License) used for the Open Source JS7 - License)license.html
(HTML format of license terms for the commercial JS7 - License)license.txt
(plain text format of license terms for the commercial JS7 - License)ThirdParty.txt
(list of 3rd party components and licenses used by JS7)var
(symbolic link/junction to data directory)bin
anonymize-logs.cmd
(used to anonymize log files, see JS7 - Log Anonymization)controller.cmd
(Start Script)controller_instance.cmd-example
(Sample Instance Start Script to set individual environment variables. Drop the-example
extension to activate this file.)controller_watchdog.cmd
(restarts the Controller if not operated as a Windows Service, called by Start Script)
lib
(directory for Java libraries)log4j2.xml
(used for based console logging to stdout, see JS7 - Logging)patches
(used for JS7 - Patches for Controller, the directory is cleaned up when running the installer)user_lib (
used for licensed binary code, see JS7 - How to apply a JS7 License Key)- (additional directories for Java libraries)
service
(directory for operation as a Windows Service)install_controller_windows_service.cmd
(used by installer)js7_controller_<controller-id>.exe
js7_controller_<controller-id>w.exe
LICENSE.txt
(copy of Apache License, Version 2.0)NOTICE.txt
(Apache Commons Daemon license notice)RELEASE-NOTES.txt
(Apache Commons Daemon release notes)uninstall_controller_windows_service.cmd
(used by uninstaller)amd64
manager
x86
Uninstaller
(Uninstaller directory for Windows only, the empty directory remains in place after uninstall)install.log
(lists installed files)js7.ico
(uninstaller icon)shortcut.vbs
(creates shortcuts for the Windows start menu)uninstall.cmd
(used by uninstaller)uninstall_prepare.cmd
(used by uninstaller)uninstaller.jar
(used by uninstaller)
C:\ProgramData\sos-berlin.com\js7\controller
(data directory)
controller_home
(symbolic link junction to installation directory)config
(directory for configuration files)controller.conf
(general Controller configuration, see JS7 - Controller Configuration Items)lib
(optional directory for licensed binary code)license
(optional directory for license certificate files)private
(directory for security related configuration files)private.conf-example
(security related configuration, see JS7 - Controller Configuration Items)- For setting up JS7 - Controller HTTPS Connections
- For setting up authentication and digital signature checks
trusted-pgp-keys
(empty directory, can be used to add individual PGP public keys for signing, see JS7 - Secure Deployment of Scheduling Objects)trusted-x509-keys
(directory to hold X.509 certificates for signing, see JS7 - Secure Deployment of Scheduling Objects)sos.intermediate-ca.pem
(default certificate of SOS to allow deployment with JOC Cockpit)
logs
(directory for log files)state
(directory for journal files)work
(directory for work files)
...
- Consider use of the
JS7_CONTROLLER_USER
environment variable from the./bin/controller_instance.sh
script to run a Controller that is started byroot
for a different user account. - For use with
systemd
find a sample service file from./bin/controller.service-example
. - For details see JS7 - systemd Service Files for automated Startup / and Shutdown with Unix Systems
For Windows systems operation of the Controller by a Windows Service is recommended as such services can be configured to start/stop automatically on server startup and shutdown.
...
Further References
- Installation
- Operation
- Configuration
...
Overview
Content Tools