Page History

...

• The JS7 Agent can be installed and operated in any Unix and Windows environments that meet the prerequisites listed below.
• The Agent is installed on Unix systems without use of an installer by extracting a .tar.gz archive.
• The Agent can be installed on 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 Agent installer in headless mode.
  • by running the Agent graphical installer, see JS7 - Agent - Installation Using the Windows Graphical Installer.

...

• A Java Runtime Environment starting from version 1.8 is required. For details see Which Java versions is JobScheduler available for?
• It is recommended to operate that a time service is operated on the server that hosts the Agent in order to synchronize the system clock's time.

...

• Download the Agent archive for the target system from the JS7 - Download page.
  
  • For Unix systems:
    • A .tar.gz archive is available that is extracted to create the Agent's directory structure (see below).
      
      • js7_agent_unix.<release>.tar.gz
  • For Windows systems:
    • A .zip archive is available that is extracted to create the Agent's directory structure (see below).
      • js7_agent_windows.<release>.zip
    • A .zip archive including the installer is available that is used to run the installer in headless mode is available.
      • js7_agent_windows_installer.<release>.zip

...

• Extract the downloaded archive file to a directory.
• After extraction the resulting directory structure includes (only files and folders immediately relevant):
  • agent 
    • 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 Agent)
    • bin
      • agent.cmd|sh
        • The Start Script for Windows/Unix platforms
      • agent_credential_value.cmd|sh
        • The script for access to a credential store on Windows/Unix platforms
      • agent_instance.sh-example
        • The template for the Agent Instance Start Script
      • agent_watchdog.cmd|sh
        • Restarts the Agent for Windows/Unix platforms
    • lib (directory for Java libraries)
    • service (directory for operation as a Windows Service)
    • var (configuration directory)
      
      • config (directory for configuration files)
        • agent.conf (general Agent configuration) 
        • private (directory for security related configuration files)
          • private.conf-example  (security related configuration)
            • For setting up HTTPS connections see JS7 - Agent Configuration Items
            • 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)
          • trusted-x509-keys (directory to hold X.509 certificates for signing, see JS7 - Secure Deployment)
            • sos.intermediate-ca.pem (default certificate of SOS to allow deployment with JOC Cockpit)
      • logs (directory for log files)
      • state (directory for journal files, will be created on startup of the Agent)
      • work (directory for work files)
    • yade (directory for the YADE file transfer utility)
  • On Windows Systems:
    • You have to modify the directory permissions for the above .\logs and .\service directories if you extracted the Agent to e.g. , for example, C:\Program Files.
      • This step is not required if you extract the Agent e.g. to C:\ProgamData.

      • Start a command prompt with elevated administrative rights and execute e.g., for example:

        Code Block
        language bash title Allow full acces for "Users" on .\service and .\logs directories
        cd "path\to\installation-directory" icacls "service" /L /grant *S-1-5-32-545:(OI)(CI)F icacls "logs" /L /grant *S-1-5-32-545:(OI)(CI)F

  • If more than one run-time instance of an Agent starting from the same Agent installation is used then every instance has to use its individual ./var_<http-port of the instance> data directory, e.g. ./var_4445, ./var_4447 etc. as each Agent instance has to use an individual port when operated on the same server.
  • To start the Agent you can use the commands explained with in the JS7 - Agent - Command Line Operation article or your can automate startup from the instructions provided by the below chapter "Automated Startup and Shutdown" section below.

Update and Upgrade

Find detailed instructions from JS7 - Update and Patch Management.

...