Page History

...

• 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.

...

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

Anchor
update_procedure_docker_images update_procedure_docker_images

Update Procedure for Use of Docker Images

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

• Tag the existing Docker® image for backup purposes.
• Pull the updated Docker® image
  • Consider instructions from
    • JS7 - JOC Cockpit Installation for Docker Containers.
    • JS7 - Controller Installation for Docker Containers
    • JS7 - Agent Installation for Docker Containers
• Stop and remove the container.
• Start the container.

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.

Anchor
update_procedure_headless_on_premises update_procedure_headless_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)

...

• 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.

...

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

Anchor
upgrade_procedure_docker_images upgrade_procedure_docker_images

Upgrade Procedure for Use of Docker Images

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

• Tag the existing Docker® image for backup purposes.
• Pull the updated Docker® image
  • Consider instructions from
    • JS7 - JOC Cockpit Installation for Docker Containers.
    • JS7 - Controller Installation for Docker Containers
    • JS7 - Agent Installation for Docker Containers
• 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 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 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)

...