...

• Patch file names follow the schema:
  • Unix: js7_joc_linux.<release>-PATCH.GUI-<sequence>.<issue-key>.tar.gz
  • Windows: js7_joc_windows.<release>-PATCH.GUI-<sequence>.<issue-key>.zip
• The following placeholders are used:
  • release: The JS7 release number, see Releases.
  • sequence:  Patches for a given release are assigned ascending numbers starting from 1. Patches with a higher number include any patches with lower numbers.
  • issue-key: The issue in the SOS Change Management System, for example: JOC-1550.
• Example:
  • Unix:js7_joc_linux.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz
  • Windows:js7_joc_windows.2.5.3-PATCH.GUI-1.JOC-1550.zip

Anchor
on_premises on_premises

Patches for JOC Cockpit On Premises

...

The first part of the path including the jetty_base is specified during installation and can point to a different location. The remaining webapps/joc part of the path will remain the same for all installations.

Download Patch

The Find the following example makes use of a patch available for

...

for a patch:

...

Do not apply the patch from the example above examples for any JOC Cockpit release different from 2.5.3, for details see JOC-1550.

...