Page History

...

• Bugs, vulnerabilities and availability of patches are communicated with the SOS Change Management System.
• The article provides information about how to apply patches to the JOC Cockpit.
  

  Display feature availability
  StartingFromRelease 2.5.0

• The article applies explains how to manually apply patches. For automated patching see JS7 - Automated Installation and Update.

...

• Patches are offered from .tar.gz archives tarball archive files or from .jar Java archive files.
• The same patch files are applied for to Unix and Windows.
• Patch file names follow the scheme:
  • Unix, Windows: js7_joc.<release>-PATCH.API-<sequence>.<issue-key>[.<security-level>].[tar.gz|jar}
  • 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 key in the SOS Change Management System, for example: JS-1984.
    • security-level: The security level applies if the patch is specific for JOC Cockpit running in one of the security levels low, medium, high. For details see JS7 - Security Architecture.
  • Example:
    
    • Unix, Windows: js7_joc.2.2.3-PATCH.API-1.JS-1984.tar.gz, js7_joc.2.2.3-PATCH.API-1.JS-1984.joc
• Patch .tar.gz archive files do not include a directory hierarchy.

...

Download Patch

Find the following example examples for a patch:

This patch does not impact a JOC Cockpit installation and is used for instructional purposes only. For details see JS-1984.

...