JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

  • JS7 - Download offers current releases of the product for download. For initial installation see JS7 - Installation. 
  • Any updates or upgrades are performed using the installer archive .tar.gz/.zip files provided for initial installation of newer releases. Instructions provided by the JS7 - Installation section apply to updates and upgrades.
  • JS7 follows semantic versioning, therefore the wording is applied as follows:
    • Update: switch to a maintenance release within the same branch, for example within minor release 2.2
      • update from 2.2.1 to 2.2.2
      • update from 2.2.0 to 2.2.2 (the latest maintenance release includes any fixes of previous maintenance releases)
    • Upgrade: switch to a newer minor release, for example from minor release 2.1 to 2.2
      • upgrade from 2.1.0 to 2.2.0
      • upgrade from 2.1.1 to 2.2.2

Update

Applicability

  • For any update JOC Cockpit and the Controller are required to use the same release.
  • Existing Agents can continue to be operated with newer Controller releases within the same minor release.
    • No newer Agent minor releases can be used with a Controller operated for an older minor release, for example an Agent 2.2 will not work with a Controller 2.1.
    • No Agents using an older minor release can be used with Controllers of a newer minor release, for example an Agent 2.1 will not work with a Controller 2.2.

Order of Components

  • In a first step update JOC Cockpit.
  • In a second step update Controller and Agents.

Procedure

JOC Cockpit

  • Extract the installer archive .tar.gz/.zip file. It will create a directory that includes the maintenance release number, for example joc.2.2.2.
    •  Consider instructions from
    • Users can re-use an existing joc_install.xml installer response file from a previous installation for the same minor release.
    • Consider to copy additional resources to the directory of the extracted installer archive, for example to joc.2.2.2
      • any JDBC Drivers that you downloaded individually for installation with a previous JS7 release,
      • the Hibernate configuration file that holds the database connection and that has been used for a previous installation,
      • the JS7 license key *.pem file if JS7 is operated with a Commercial License. 
  • Stop the JOC Cockpit daemon (Linux) or service (Windows).
  • Run the JOC Cockpit installer
    • Invoke the installer script in the same way as for installation of a previous release, for example with headless installation
      • ./setup.sh|.cmd joc_install.xml
      • ./setup.sh|.cmd -u joc_install.xml
  • Start the JOC Cockpit daemon (Linux) or service (Windows)

Controller and Agents

  • Extract the installer archive .tar.gz/.zip file. It will create a directory that includes the maintenance release number, for example controller.2.2.2.
    • Consider instructions from
    • Headless Installation
    • Consider to copy additional resources to the directory of the extracted installer archive, for example to joc.2.2.2
      • any JDBC Drivers that you downloaded individually for installation with a previous JS7 release,
      • the Hibernate configuration file that holds the database connection and that has been used for a previous installation,
      • the JS7 license key *.pem file if JS7 is operated with a Commercial License. 
  • Standalone Controller
    • Stop the Controller
  • Controller Cluster
    • Stop the Controller: consider to stop both Controller instances.
    • Stop the Cluster Watch Agent
  • If 

Upgrade

  • No labels