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

Compare with Current View Page History

« Previous Version 10 Next »

Introduction

SOS provides JS7 - Patch Management in a situation of severe bugs or Vulnerabilities.

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

Apply Patch to Controller On Premises

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

  • 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 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 then steps are performed for any Controller instance.

The examples makes use of a patch available from https://download.sos-berlin.com/patches/sos_ldap_for_2.2.2_patch.jar. Do not apply this patch that is used for explanation purposes only.


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/sos_ldap_for_2.2.2_patch.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/sos_ldap_for_2.2.2_patch.jar
@rem copy from download location (could be different from this example)
copy %USERPROFILE%\Downloads\sos_ldap_for_2.2.2_patch.jar .


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

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 that holds the patch archives.

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

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/patches
  • 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/patches does not exist then it should be created before storing the patch file.

Apply Patch

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

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 should be applied.

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

Remove Patch

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

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



  • No labels