...

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

Anchor
on_premises on_premises

Apply Patch to JOC Cockpit

...

On Premises

JOC Cockpit expects Java .jar libraries for patches from the following location:

...

The JETTY_BASE part of the above path is specified during installation and can point to a different location. The remaining part webapps/joc/WEB-INF/classes is the same for any installation.

Apply Patch

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

...

Note: A restart of JOC Cockpit is required to apply the patchpatches.

Note: As an alternative for Windows you can download the .jar patch file to the target directory and use tools such as 7-Zip to extract the archive. Do not create a sub-folder from the archive name but extract directly to the directory hierarchy as indicated above.

Remove Patch

Patches are automatically removed when a JOC Cockpit release is installed.

...

Note: A restart of JOC Cockpit is required to apply removal of patches.

Docker® Containers

Apply Patch

Remove Patch

Apply Patch for Controller

On Premises

Anchor
docker_containers docker_containers

Apply Patch to JOC Cockpit Docker® Containers

JOC Cockpit The Controller expects Java .jar libraries for patching in patches from the following location:

• Unix/optvar/sos-berlin.com/js7/controller/lib/patchesWindowsC:\Program Files\/joc/jetty_base/resources/joc/patches
• The directory /var/sos-berlin.com\js7\controller\<controller-id>\lib\patches

The <controller-id> part of the above path is specified during installation and defaults to controller, this can point to a different location. The remaining part lib/patches is the same for any installation.

Apply Patch

Apply the following steps to a Controller instance. If a Controller cluster is operated the steps are performed for any Controller instance.

...

...

• /js7/joc/jetty_base/resources/joc typically is mounted to a Docker config volume when running the container: for details see JS7 - JOC Cockpit Installation for Docker Containers. The patches sub-directory should be created if it does not already exist before storing the patch file to this location.

Apply Patch

• On startup 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 On Premises.
• 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 be applied.

Note: A restart of the Controller instance JOC Cockpit container is required to apply the patchpatches.

Remove Patch

Patches are automatically removed when a Controller release is installed using the JS7 - Controller - Installation Using the Windows Graphical Installer.

Patches can be manually Patch files are removed by dropping the files in the the patches sub sub-directory that holds the extracted patch. 

Note: A restart of the Controller JOC Cockpit container is required to apply removal of patches.

...