...

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

• Display feature availability
  StartingFromRelease 2.3.0

Anchor
on_premises on_premises

Apply Patch to JOC Cockpit On Premises

The JOC Cockpit expects Java .jar libraries for patches to be extracted to the following location:

...

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

Apply Patch

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

The following example makes use of a patch available from https://download.sos-berlin.com/patches/patch-20220331-JS-1984-2.2.3.jar. This patch does not impact a JOC Cockpit installation and is used for instruction instructional purposes only , - for details see JS-1984.

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

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

# download the patch archive
curl https://download.sos-berlin.com/patches/patch-20220331-JS-1984-2.2.3.jar -O

# extract the patch archive (use "jar" or "unzip" command)
jar -xf patch-20220331-JS-1984-2.2.3.jar
# remove the patch archive
rm patch-20220331-JS-1984-2.2.3.jar

...

This example uses the jar command that is available from a Java JDK. Should no a Java JDK not be in place then the unzip command can be used.

...

• webapps/joc/WEB-INF/classes
  • com
    • sos
      • ...

Note: A restart of The JOC Cockpit is required to apply patcheshas to be restarted before patches are applied.

Hint: For automated rollout of patches see JS7 - Automated Update of JOC Cockpit.

...

Patches can be manually removed by dropping the com sub-directory that holds the extracted patch.

Note: A restart of The JOC Cockpit is required to apply removal of patcheshas to be restarted before patches are removed.

Anchor
docker_containers docker_containers

Apply Patch to JOC Cockpit Docker® Containers

...

On start-up the JOC Cockpit container checks the above directory for existence of *.jar files. If a file is found then:

• the file will be extracted to /var/sos-berlin.com/js7/joc/jetty_base/webapps/joc/WEB-INF/classes
• for details see chapter the On Premises section above.

Patches are applied on start-up of a container. Therefore patch files remain in place in the /var/sos-berlin.com/js7/joc/jetty_base/resources/joc/patches sub-directory (typically mounted to the config/patches volume directory) as long as the patch should is to be applied.

Note: A restart of the The JOC Cockpit container is required to apply patcheshas to be restarted before patches are applied.

Remove Patch

Patch files are removed by dropping the files in the patches sub-directory.

Note: A restart of the The JOC Cockpit container is required to apply removal of patcheshas to be restarted before patches are removed.