The JS7 - Download page provides information and links to download current releases of the product. For the initial installation procedure see the JS7 - Installation articles.
Any updates or upgrades are performed using the .tar.gz/.zip installer installation archive files provided for the initial installation of newer releases. Instructions provided by the the JS7 - Installation section apply to updates and upgrades.
JS7 follows semantic versioning, with the wording being applied as follows:
- Update to newer JS7 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)
- JS7 - Upgrade to newer JS7 minor 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

Update

Applicability

For any update most updates the 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.
- Newer minor Agent releases cannot be used with an older minor Controller release: for example, an Agent 2.2 will not work with a Controller 2.1.
- Older minor Agents releases cannot be used with newer minor Controller releases: for example, an Agent 2.1 will not work with a Controller 2.2.

Before updating users should identify what versions are in use.

Users can click the JS7 logo available from any page in JOC Cockpit to identify the version in use:

Image Added

The Controller version is displayed per instance from the bottom of the Dashboard page:

Image Added

Consider the Image Added icon that acts as the compatibility indicator:

Agent versions are displayed from the Resources->Agents view. The meaning of the compatibility indicator is the same as for the Controller.

Image Added

...