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

« Previous Version 4 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 maintenance release, for example 2.2.2.
  • Existing Agents can continue to be operated with newer Controller releases within the same minor release, for example 2.2.
    • 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.

Update Procedure for Use of Docker Images

For any Docker® images for JOC Cockpit, Controller and Agents the following procedure applies:

Consider that the above procedure does not apply if you build your own images, see JS7 - Build Docker Images. Consider to map the steps explained with Update Procedure for Headless Installation On Premises.

Update Procedure for Headless Installation On Premises

JOC Cockpit

  • Take a backup of the JOC Cockpit's installation directory.
  • 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 JS7 - JOC Cockpit Installation On Premises
    • 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 JOC Cockpit 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
      • ./setup.sh|.cmd joc_install.xml
      • ./setup.sh|.cmd -u joc_install.xml
  • Start the JOC Cockpit daemon (Linux) or service (Windows)

Controller

  • Take a backup of the Controller instance's installation directory.
  • Extract the installer archive .tar.gz/.zip file from a neutral directory not related to the current Controller installation. This will create a sub-directory that includes the maintenance release number, for example controller.2.2.2.
  • Consider instructions from JS7 - Controller Installation On Premises
  • Stop the Controller.
    • Standalone Controller
      • Stop the Controller instance.
    • Controller Cluster
      • Stop both Controller instances.
      • Stop the Cluster Watch Agent.
  • From the existing Controller installation directory move or remove the lib directory.
  • Copy the lib and bin directories from the extracted installer archive to the Controller instance's installation directory. This will replace the previous lib directory and will overwrite the existing bin directory from the new release.
    • For a Controller Cluster consider to perform this step for both Controller instances.
  • For a Controller Cluster update the Cluster Watch Agent as explained below and start the Cluster Watch Agent.
  • Start the Controller.

Agent

  • Take a backup of the Agent's installation directory.
  • Extract the installer archive .tar.gz/.zip file from a neutral directory not related to the current Agent installation. This will create a sub-directory that includes the maintenance release number, for example agent.2.2.2.
  • Consider instructions from JS7 - Agent Installation On Premises
  • Stop the Agent.
  • From the existing Agent installation directory move or remove the lib directory.
  • Copy the lib and bin directories from the extracted installer archive to the Agent's installation directory. This will replace the previous lib directory and will overwrite the existing bin directory from the new release.
  • Start the Agent.

Upgrade

Applicability

  • For any upgrade JOC Cockpit, the Controller and Agents are required to use the same minor release, for example 2.2.
  • Existing Agents cannot continue to be operated with newer Controller releases across different minor releases.

Order of Components

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

Upgrade Procedure for Use of Docker Images

For any Docker® images for JOC Cockpit, Controller and Agents the following procedure applies:

Consider that the above procedure does not apply if you build your own images, see JS7 - Build Docker Images. Consider to map the steps explained with Upgrade Procedure for Headless Installation On Premises.

Upgrade Procedure for Headless Installation On Premises

JOC Cockpit

  • Take a backup of the JOC Cockpit's installation directory.
  • 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 JS7 - JOC Cockpit Installation On Premises
    • Users basically can re-use an existing joc_install.xml installer response file from a previous installation, however, users should check for changes, for example new or changed installer options that are available from the joc_install.xml file after extraction of the installer archive. If in doubt copy settings from a previous joc_install.xml file to the new version of this file.
    • 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 JOC Cockpit 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).
  • Take a backup of the JS7 - Database schema. During upgrade changes to the database schema might be applied that prevent to rollback to the previous JOC Cockpit release.
  • Run the JOC Cockpit installer
    • Invoke the installer script in the same way as for installation of a previous release, for example
      • ./setup.sh|.cmd joc_install.xml
      • ./setup.sh|.cmd -u joc_install.xml
  • Start the JOC Cockpit daemon (Linux) or service (Windows)

Controller

  • Take a backup of the Controller instance's installation directory.
  • Extract the installer archive .tar.gz/.zip file from a neutral directory not related to the current Controller installation. This will create a sub-directory that includes the maintenance release number, for example controller.2.2.2.
  • Consider instructions from JS7 - Controller Installation On Premises
  • Stop the Controller.
    • Standalone Controller
      • Stop the Controller instance.
    • Controller Cluster
      • Stop both Controller instances.
      • Stop the Cluster Watch Agent.
  • From the existing Controller installation directory move or remove the lib directory.
  • Copy the lib and bin directories from the extracted installer archive to the Controller instance's installation directory. This will replace the previous lib directory and will overwrite the existing bin directory from the new release.
    • For a Controller Cluster consider to perform this step for both Controller instances.
  • For a Controller Cluster update the Cluster Watch Agent as explained below and start the Cluster Watch Agent.
  • Start the Controller.

Agent

  • Take a backup of the Agent's installation directory.
  • Extract the installer archive .tar.gz/.zip file from a neutral directory not related to the current Agent installation. This will create a sub-directory that includes the maintenance release number, for example agent.2.2.2.
  • Consider instructions from JS7 - Agent Installation On Premises
  • Stop the Agent.
  • From the existing Agent installation directory move or remove the lib directory.
  • Copy the lib and bin directories from the extracted installer archive to the Agent's installation directory. This will replace the previous lib directory and will overwrite the existing bin directory from the new release.
  • Start the Agent.

Troubleshooting




  • No labels