...

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

Anchor
on_premises on_premises

Apply Patch to Controller On Premises

The Controller expects Java .jar libraries for patches from the following location:

...

Note: A restart of the Controller instance 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.

...

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

Anchor
docker_containers docker_containers

Apply Patch to Controller Docker® Containers

The Controller container expects Java .jar libraries for patches from the following location:

...

• /var/sos-berlin.com/js7/controller/config/lib
• The directory /var/sos-berlin.com/js7/controller typically is mounted to a Docker var volume when running the container: for details see JS7 - Controller Installation for Docker Containers.
• If the sub-directory config/lib does not exist then it can be created it before storing the patch file.

Apply Patch

On startup the Controller container checks the above directory for existence of .jar files and applies the patches, 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/controller/config/lib sub-directory (typically mounted to the config/

...

lib volume directory) as long as the patch should be applied.

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

Remove Patch

Patches have to be manually are removed by dropping the files in the patches sub-directory that holds the patch archives.

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

...