Page History
...
- Bugs, vulnerabilities and patches are communicated with the SOS Change Management System.
- This article provides information about how to apply patches to the JOC Cockpit.
Display feature availability StartingFromRelease 2.35.0 - For automated patching see JS7 - Automated Installation and Update.
The following information applies to patches of the JS7 - REST Web Service API (API Server). For patches of the JOC Cockpit GUI see see JS7 - Patches for JOC Cockpit GUI.
- The same patch files are applied for Unix and Windows.
- Patch files are provided from a single .jar file or from .tar.gz archives that hold a number of .jar files.
- Patch file names follow the schema:
- Unix, Windows:
js7_joc_linux.<release>-PATCH.API-<sequence>.<issue-key>[.<security-level>].jar - Unix, Windows:
js7_joc_windows.<release>-PATCH-.API-<sequence>.<issue-key>[.<security-level>].tar.jargz
- Unix, Windows:
- 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.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:
- Single .jar file for Unix, Windows:
js7_joc
.2.2.3-PATCH.API-1.JS-1984.jar- Tarball archive for Unix, Windows:
js7_joc.2.2.3-PATCH.API-1.JS-1984.tar.
gz
- Single .jar file for Unix, Windows:
| Anchor | ||||
|---|---|---|---|---|
|
...
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/WEB-INF/classes part of the path will remain the same for all installations.
Download Patch
Find the following example for a patch:
| Product | Type | Media | Download URL Example | Hash | Sig | TSR |
|---|---|---|---|---|---|---|
| JOC Cockpit | single .jar file | .jar | https://download.sos-berlin.com/patches/2.2.3-patch/js7_joc.2.3.3-PATCH.GUI-1.JS-1984.jar | sha256 | sig | tsr |
| tarball archive | .tar.gz | https://download.sos-berlin.com/patches/2.3.3-patch/js7_joc.2.3.3-PATCH.API-1.JS-1984.tar.gz | sha256 | sig | tsr |
Do not apply the patch from the above examples for any JOC Cockpit release different from 2.5.3, for details see JOC-1550.
Effective download links for JOC Cockpit patches are indicated with the respective Change Management issue.
Before applying patches users might want to verify the integrity and authenticity of downloaded files, see JS7 - Verifying releases.
The following example makes use of a patch available for
...
Overview
Content Tools