Page History
...
Before updating users should identify the version in use by JS7 Components products and the indicated compatibility, see JS7 - Compatibility Indicator.
...
The information of the JS7 - Compatibility Indicator about compatibility is authoritative.
Order of
...
Products
- First, update the JOC Cockpit.
- In a second step, update Controller(s) and Agents.
Anchor | ||||
---|---|---|---|---|
|
...
Container Images
The following procedure applies for any Docker® to container images for the JOC Cockpit, Controller and Agents:
- Refer also to the instructions in the following articles:
- Tag the existing Docker® container image for backup purposes.
- Pull the updated Docker® container image.
- Stop and remove the container.
- Start the container.
Note that the above procedure does not apply if you build your own images, see the JS7 - Build Docker Container Images article for more information. Consider mapping the steps explained in the Update Procedure for Headless Installation On Premises article.
Anchor | ||||
---|---|---|---|---|
|
Procedures include that updates 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 update as explained by the installation instructions.
Both options are indicated with the below update procedures.
JOC Cockpit
- Refer to the instructions in the JS7 - JOC Cockpit Installation On Premises article.
- Make a backup of the JOC Cockpit's installation directory.
- Option 1: Automated Update
- 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 update 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 Update
- Option 2: Manual Update
- Extract the installation 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.
- Users can re-use an existing
- Stop the JOC Cockpit daemon (Linux) or service (Windows) of any JOC Cockpit instances using the same database.
- 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 installation archive .tar.gz/.zip file. It will create a sub-directory that includes the maintenance release number, for example
...