...

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

• Bugs, vulnerabilities and patches are communicated with the SOS Change Management System.
• Find below the information This article provides information about how to apply patches to a JS7 Agent.

• Display feature availability
  StartingFromRelease 2.3.0

...

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

• Unix
  • /opt/sos-berlin.com/js7/agent/lib/patches
• Windows
  • C:\Program Files\sos-berlin.com\js7\agent\lib\patches

The paths noted above path is are specified during installation and can point to a different location. The remaining part  lib/patches part of the path is the same for any installation.

...

Apply the following steps for an Agent instance. If an Agent cluster is operated then these steps are to be performed for any all Agent cluster membermembers.

The 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 an Agent installation and is used for explanation purposes only , - for details see JS-1984.

# navigate to the target directory for patches
cd /opt/sos-berlin.com/js7/agent/lib/patches

# download the patch archive
curl https://download.sos-berlin.com/patches/patch-20220331-JS-1984-2.2.3.jar -O

@rem navigate to the target directory for patches
cd %ProgramFiles%\sos-berlin.com\js7\agent\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 Agent instance is required to apply patcheshas to be restarted before patches are applied.

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

...

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

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

Anchor
docker_containers docker_containers

Apply Patch to Agent Docker® Containers

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

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

...

On start-up the Agent 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/agent/config/patches sub-directory (typically mounted to the config/lib volume directory) as long as the patch should be applied.

Note: A restart of the  The Agent 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 Agent container is required to apply removal of patcheshas to be restarted before patches are removed.