Page History
Table of Contents |
---|
Introduction
SOS provides JS7 - Patches 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 Agent.
Anchor | ||||
---|---|---|---|---|
|
The Agent expects Java .jar libraries for patches from the following location:
...
The above path is specified during installation and can point to a different location. The remaining part lib/patches
is the same for any installation.
Apply Patch
Apply the following steps to an Agent instance. If an Agent cluster is operated then steps are performed for any Agent cluster member.
...
Note: A restart of the Agent instance is required to apply patches.
Remove Patch
Patches are automatically removed when an Agent release is installed using the JS7 - Agent - Installation Using the Windows Graphical Installer.
...
Note: A restart of the Agent is required to apply removal of patches.
Anchor | ||||
---|---|---|---|---|
|
The Agent container expects Java .jar libraries for patches from the following location:
/var/sos-berlin.com/js7/agent/config/lib
- The directory
/var/sos-berlin.com/js7/agent
typically is mounted to a Dockervar
volume when running the container: for details see JS7 - Agent Installation for Docker Containers. - If the sub-directory
config/lib
does not exist then it can be created before storing the patch file.
Apply Patch
On start-up the Agent 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/agent/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 Agent container is required to apply patches.
Remove Patch
Patches are removed by dropping the files in the patches
sub-directory.
...