Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

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

  • 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 part will be the same for any installationall 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 any all Controller 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 Controller installation and is used for instruction instructional purposes only , - for details see JS-1984.


Code Block
languagebash
titleExample how to apply a patch to a Controller for Unix
linenumberstrue
# 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
Code Block
languagebash
titleExample how to apply a patch to a Controller for Windows
linenumberstrue
@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: A restart of the The Controller instance is required to apply patches.has to be restarted before patches are applied..

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

...

Patches can be manually removed by dropping the files in the patches sub-directory that which holds the patch archives.

Note: A restart of the Controller is required to apply removal of patchesThe Controller has to be restarted before patches are removed.

Anchor
docker_containers
docker_containers
Apply Patch to Controller Docker® Containers

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

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

...

On start-up the Controller container checks the directory noted above directory for the existence of .jar files and applies the patches , - for details see chapter 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 should is to be applied.

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

Remove Patch

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

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