Page History

...

• Consider instructions from
  • JS7 - JOC Cockpit Installation for Docker Containers
  • JS7 - Controller Installation for Docker Containers
  • JS7 - Agent Installation for Docker Containers
• Tag the existing Docker® image for backup purposes.
• Pull the updated Docker® image.
• Stop and remove the container.
• Having stopped the JOC Cockpit container 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.
• Start the container.

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

Anchor
upgrade_procedure_docker_images upgrade_procedure_docker_images

Upgrade Procedure for Installation On Premises

Procedures include that upgrades can be performed automatically using installation scripts:

• JS7 - Installation and Update using Unix Shell: for Unix environments
• JS7 - Installation and Update using PowerShell: for Windows and Unix environments:

In addition, users can choose to manually upgrade as explained by the installation instructions.

Both options are indicated with the below upgrade procedures.

JOC Cockpit

• Consider instructions from JS7 - JOC Cockpit Installation On Premises.
• Take a backup of the JOC Cockpit's installation directory.
• Option 1: Automated Upgrade
  • Stop the JOC Cockpit daemon (Linux) or service (Windows) of any JOC Cockpit instances using the same database.
  • 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 Installation Script for Upgrade
    • JS7 - Unix Shell Installation Script - js7_install_joc.sh
    • JS7 - PowerShell Examples - Install-JS7Joc.ps1
• Option 2: Manual Upgrade
  • Extract the installer archive .tar.gz/.zip file. This will create a sub-directory that includes the maintenance release number, for example joc.2.2.2.
    • 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) of any JOC Cockpit instances using the same database.
  • 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)

...

• Consider instructions from JS7 - Controller Installation On Premises.
• Take a backup of the Controller instance's installation directory.
• Suspend all orders.
• Stop the Controller:
  • Standalone Controller
    • Stop the Controller instance's daemon (Linux) or service (Windows).
  • Controller Cluster
    • Take a note which Controller instance is the active node before stopping Controller instances.
    • Stop both Controller instances' daemon (Linux) or service (Windows).
    • Stop the Cluster Watch Agent daemon (Linux) or service (Windows) if an Agent is used as a Cluster Watch.
• Option 1: Automated Upgrade
  • Run the Controller Installation Script for Upgrade
    • JS7 - Unix Shell Installation Script - js7_install_controller.sh
    • JS7 - PowerShell Examples - Install-JS7Controller.ps1
  • For a Controller Cluster
    • run the Controller Installation Script for the active and then for the standby Controller instance.
    • update the Cluster Watch Agent as explained below and start the Cluster Watch Agent if an Agent is used as a Cluster Watch. This step is not performed if JOC Cockpit is used as a Cluster Watch.
• Option 2: Manual Upgrade
  • 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.
  • From the existing Controller installation directory move or remove the lib directory.
  • Copy the lib and bin sub-directories from the extracted installer archive to the Controller instance's installation directory. This will replace the previous lib sub-directory and will overwrite the existing bin sub-directory from the new release. The Controller's instance start script that can contain individual settings, is not included with the installation archive and therefore will not be overwritten, see JS7 - Controller - Command Line Operation.
  • For a Controller Cluster
    • consider to perform this step for both Controller instances.
    • update the Cluster Watch Agent as explained below and start the Cluster Watch Agent. This step is not performed if JOC Cockpit is used as a Cluster Watch.
• Start the Controller. For a Controller Cluster start both Controller instances.
• Update Agents.
• Resume all orders.

...