Page History
...
- The Controller can be installed for Linux systems without use of an installer by extracting a .tar.gz archive.
- The Controller can be installed for Windows systems
- without use of an installer by extracting a .zip archive. This allows a portable installation that requires no administrative privileges or
- by running the Controller installer in headless mode .or
- by running the graphical installer see JS7 - Controller - Use of Windows Graphical Installer.
...
- A Java Runtime Environment starting from version 1.8 is required. For details see Which Java versions is JobScheduler available for?
- Technically the Controller can be operated for any Unix environmentenvironments, however, the JS7 - Platforms include support for Controller operation with Linux.
...
Directories for installation and configuration of the Controller might differ.
Installation Log
The installer creates a log file in the directory that is pointed to by the environment variable JS7_CONTROLLER_LOGS
or in the logs
sub-directory of the Controller configuration directory.
Update
Preparation
- Stop the JS7 Controller instance.
- Prepare to rollback in case that the update of the JS7 Controller is not successful.
- Take a backup of the Controller's installation directory and configuration directory, e.g. by creating a .zip archive.
- Installation Directory:
- The default installation directory for the Controller instance is
C:\Program Files
- The default installation directory for the Controller instance is
- Installation Directory:
logs
directory for the Controller is- C:\ProgramData
\sos-berlin.com\js7\controller\<controller-id>
- Take a backup of the Controller's installation directory and configuration directory, e.g. by creating a .zip archive.
- Installation log files are named according to the pattern
Install_V<release>_<date-time>_....log
where<
release>
is the release number and<
date-time>
refers to the point in time of installation. - For further information about logging see JS7 - Logging
Update
Preparation
- Configuration Directory
- The default configuration directory for the Controller instance is
C:\ProgramData\sos-berlin.com\js7\controller\<controller-id>
- The default configuration directory for the Controller instance is
Running the Update
The update procedure makes use of the same installer response file as explained for a fresh installation.
Steps to run the installer are the same as explained for a fresh installation.
Installation Log
The installer creates a log file in the directory that is pointed to by the environment variable JS7_CONTROLLER_LOGS
or in the logs
sub-folder of the Controller configuration directory.
- The default location of the
logs
directory for the Controller isC:\ProgramData
- Stop the JS7 Controller instance.
- Prepare to rollback in case that the update of the JS7 Controller is not successful.
- Take a backup of the Controller's installation directory and configuration directory, e.g. by creating a .zip archive.Installation Directory:The default installation directory for the Controller instance is
C:\Program Files\sos-berlin.com\js7\controller\<controller-id>
- Configuration Directory
- The default configuration directory for the Controller instance is
C:\ProgramData\sos-berlin.com\js7\controller\<controller-id>
- The default configuration directory for the Controller instance is
- Take a backup of the Controller's installation directory and configuration directory, e.g. by creating a .zip archive.Installation Directory:The default installation directory for the Controller instance is
Running the Update
The update procedure makes use of the same installer response file as explained for a fresh installation.
Steps to run the installer are the same as explained for a fresh installation.
Operation
...
- Installation log files are named according to the pattern
Install_V<release>_<date-time>_....log
where<
release>
is the release number and<
date-time>
refers to the point in time of installation. - For further information about logging see JS7 - Logging
Rollback
Rollback Installation from .tar.gz/.zip Archive
...
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 start-up and shutdown.
Initial Operation
- Having completed the installation or update of a JS7 Controller you can start the Controller either manually or from its Unix daemon/Windows Service, see JS7 - Controller Command Line Operation.
- Consider the following information about initial operation:
Further References
- JS7 - Controller - Use of Windows Graphical Installer
- JS7 - Controller - Command Line Operation
- JS7 - Controller Configuration
...