Page History

...

• Refer to the instructions in the JS7 - JOC Cockpit Installation On Premises article.
• Make a backup of the JOC Cockpit's installation directory.
• Extract the installer archive .tar.gz/.zip file. It will create a sub-directory that includes the maintenance release number, for example joc.2.2.2.
  • Users can re-use an existing joc_install.xml installer response file from a previous installation for the same minor release.
  • Consider copying 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

• Refer to the follwing articles:JS7 - Controller Installation On Premises,JS7 - Automated Update of Controller that performs the steps described below article.
• Make a backup of the Controller instance's installation directory.
• Extract the .tar.gz/.zip installer archive 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.
• Stop the Controller:
  • Standalone Controller
    • Stop the Controller instance.
  • Controller Cluster
    • Take a note which Controller instance is the active node when stopping the Controller instances.
    • Stop both Controller instances.
    • Stop the Cluster Watch Agent.
• Move or remove the lib sub-directory from the existing Controller installation 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 installer archive and therefore will not be overwritten, see JS7 - Controller - Command Line Operation for more inforamtion.
  
  • For a Controller Cluster consider performing 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

• Refer to the following articles:
  JS7 - Agent Installation On Premises,JS7 - Automated Update of Agent that performs the steps described below article.
• Make a backup of the Agent's installation directory.
• Extract the .tar.gz/.zip installer archive 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.
• Stop the Agent.
• Move or remove the lib sub-directory from the existing Agent installation directory.
• Copy the lib and bin sub-directories from the extracted installer archive to the Agent's installation directory. This will replace the previous lib sub-directory and will overwrite the existing bin sub-directory from the new release. The Agent's instance start script that can contain individual settings is not included with the installer archive and therefore will not be overwritten, see JS7 - Controller - Command Line Operation for more inforamtion.
• Start the Agent.

...