...

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

  Display feature availability
  StartingFromRelease 2.5.0

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

The following information applies to patches of the JOC Cockpit GUI. For patches of the JS7 - REST Web Service API (API Server) see JS7 - Patches for JOC Cockpit API.

• Patches are offered from .tar.gz tarball archive files or from .jar Java archive files.
• The same patch files are applied tto Unix and Windows.
• Patch file names follow the schemascheme:
  • Unix, Windows: js7_joc.<release>-PATCH.GUI-<sequence>.<issue-key>.tar.gz
  • The same patch files are applied for Unix and 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 key in the SOS Change Management System, for example: JOC-1550.
  • Example:
    • Unix, Windows:js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz
• Patch .tar.gz archive files do not include a directory hierarchy.

Anchor
on_premises on_premises

Patches for JOC Cockpit On Premises

...

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

...

Apply the following steps to a JOC Cockpit instance. If a JOC Cockpit cluster is operated then the steps are to be performed for all JOC Cockpit instances.

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

...

# navigate to the target directory for patches
cd /var/sos-berlin.com/js7/joc/jetty_base/webapps/joc

# verify the directory by checking if this file is available
ls version.json

# take a backup
tar --exclude=./WEB-INF -cvzf /tmp/backup-joc-cockpit-$(date +"%Y%m%d-%H%M%S").tar.gz .

# remove existing files and directories
find . -maxdepth 1 -type f -delete && rm -d -r ./assets ./styles

# download the patch archive
curl https://download.sos-berlin.com/patches/2.5.3-patch/js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz -O

# extract the patch archive
tar -xvzf js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz

# remove the patch archive
rm js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz

...

@rem navigate to the target directory for patches
cd %ProgramData%\sos-berlin.com\js7\joc\webapps\joc

@rem verify the directory by checking if this file is available
dir version.json

@rem take a backup
set month=%date:~3,2%
set day=%date:~0,2%
set year=%date:~6,4%
set hour=%time:~0,2%
set minute=%time:~3,2%
set second=%time:~6,2%
tar.exe --exclude .\WEB-INF -cf %TEMP%\backup-joc-cockpit-%year%%month%%day%-%hour%%minute%%second%.zip .

@rem remove existing files and directories
del /q *.*
rmdir /q /s .\assets
rmdir /q /s .\styles

@rem download from URL https://download.sos-berlin.com/patches/2.5.3-patch/js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz
@rem copy from download location (could be different from this example)
copy %USERPROFILE%\Downloads\js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz .

@rem extract the patch archive
tar.exe -xf js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz

@rem remove the patch archive
del js7_joc.2.5.3-PATCH.GUI-1.JOC-1550.tar.gz

...