You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Introduction

SOS provides JS7 - Patch Management in the event of severe bugs or Vulnerabilities.

Apply Patch to Controller On Premises

The Controller expects Java .jar libraries for patches in the following locations:

  • Unix
    • /opt/sos-berlin.com/js7/controller/lib/patches
  • Windows
    • C:\Program Files\sos-berlin.com\js7\controller\<controller-id>\lib\patches

The first part of the path including <controller-id> is specified during installation and defaults to controller, this can point to a different location. The lib/patches part will be the same for all installations.

Apply Patch

Apply the following steps for a Controller instance. If a Controller cluster is being operated then these steps are to be performed for all Controller instances.

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 Controller installation and is used for instructional purposes only - for details see JS-1984.


Example how to apply a patch to a Controller for Unix
# navigate to the target directory for patches
cd /opt/sos-berlin.com/js7/controller/lib/patches

# download the patch archive
curl https://download.sos-berlin.com/patches/patch-20220331-JS-1984-2.2.3.jar -O
Example how to apply a patch to a Controller for Windows
@rem navigate to the target directory for patches
cd %ProgramFiles%\sos-berlin.com\js7\controller\<controller-id>\lib\patches

@rem download from URL https://download.sos-berlin.com/patches/patch-20220331-JS-1984-2.2.3.jar
@rem copy from download location (could be different from this example)
copy %USERPROFILE%\Downloads\patch-20220331-JS-1984-2.2.3.jar .


Note: The Controller instance has to be restarted to apply patches.

Hint: For automated rollout of patches see JS7 - Automated Installation and Update.

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 removed by dropping the files in the patches sub-directory which holds the patch archives.

Note: The Controller has to be restarted before patches are removed.

Apply Patch to Controller Containers

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

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

Apply Patch

On start-up the Controller container checks the directory noted above for the existence of .jar files and applies the patches - for details see the On Premises section above.

Patches are not applied persistently to a container. Therefore patch files remain in place in the /var/sos-berlin.com/js7/controller/config/patches sub-directory (typically mounted to the config/patches volume directory) as long as the patch is to be applied.

Note: The Controller container has to be restarted before patches are applied.

Remove Patch

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

Patch files are automatically removed when updating or upgrading the Controller.

Note: The Controller container has to be restarted to apply removal of patches.



  • No labels