Page History
...
- 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 installation archive .tar.gz/.zip files provided for initial installation of newer releases. Instructions provided by the the JS7 - Installation section apply to updates and upgrades.
- JS7 follows semantic versioning, therefore the wording is applied as follows:
- JS7 - Update to newer JS7 maintenance releases: 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 to newer JS7 releases: 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
- JS7 - Update to newer JS7 maintenance releases: switch to a maintenance release within the same branch, for example within minor release 2.2
...
- Consider instructions from JS7 - JOC Cockpit Installation On Premises.
- Take a backup of the JOC Cockpit's installation directory.
- Automated Upgrade
- 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 Installation Script
- 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 thejoc_install.xml
file after extraction of the installer archive. If in doubt copy settings from a previousjoc_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.
- Users basically can re-use an existing
- 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
- Invoke the installer script in the same way as for installation of a previous release, for example
- Start the JOC Cockpit daemon (Linux) or service (Windows)
- Extract the installer archive .tar.gz/.zip file. This will create a sub-directory that includes the maintenance release number, for example
Controller
- Consider instructions from
- JS7 - Controller Installation On Premises,
- JS7 - Automated Update of Controller that performs the below steps.
- Take a backup of the Controller instance's installation directory.
- Suspend all orders.
- Automated Upgrade
- Run the Controller Installation Script
- For a Controller Cluster consider to first stop both Controller instances and then to run the Controller Installation Script for both Controller instances.
- 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
. - Stop the Controller.
- Standalone Controller
- Stop the Controller instance.
- Controller Cluster
- Take a note which Controller instance is the active node when stopping Controller instances.
- Stop both Controller instances.
- Stop the Cluster Watch Agent.
- Standalone Controller
- From the existing Controller installation directory move or remove the
lib
directory. - Copy the
lib
andbin
sub-directories from the extracted installer archive to the Controller instance's installation directory. This will replace the previouslib
sub-directory and will overwrite the existingbin
- 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.
- 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
- For a Controller Cluster update the Cluster Watch Agent as explained below and start the Cluster Watch Agent.
- Start the Controller. For a Controller Cluster start both Controller instances.
- Resume all orders.
Agent
- Consider instructions from
- JS7 - Agent Installation On Premises,
- JS7 - Automated Update of Agent that performs the below steps.
- Take a backup of the Agent's installation directory.
- Suspend all orders related to the Agent in question.
- Automated Upgrade
- Run the Controller Installation Script
- Manual Upgrade
- 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
. - Stop the Agent.
- From the existing Agent installation directory move or remove the
lib
directory. - Copy the
lib
andbin
sub-directories from the extracted installer archive to the Agent's installation directory. This will replace the previouslib
sub-directory and will overwrite the existingbin
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. - Start the Agent.
- 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
- Resume orders for the related Agent.
Troubleshooting
Controller Cluster
...
Overview
Content Tools