...

• Patches are offered from from .jar Java archive files or from .tar.gz tarball archive files.
• The same patch files are applied to Unix and Windows.
• Patch file names follow the scheme:
  • Unix, Windows: js7_agent.<release>-PATCH.<issue-key>.[jar|tar.gz]
  • The following placeholders are used:
    • release: The JS7 release number, see Releases.
    • issue-key: The issue key in the SOS Change Management System, for example: JS-1984.
  • Example:
    
    • Unix, Windows: js7_agent.2.2.3-PATCH.JS-1984.jar, js7_agent.2.2.3-PATCH.JS-1984.tar.gz
• Patch .tar.gz archive files
  • include one or more .jar files that hold patches.
  • include a directory hierarchy for .jar files:
    • agent/lib/patches

Download

...

Patches

Find the following examples for a patch:

The patch examples will not impact an Agent installation and are used for instructional purposes only. For details see JS-1984.

...

The paths noted above are specified during installation and can point to a different location. The lib/patches part of the path will be the same for all installations.

...

Applying Patches

Apply the following steps to an Agent instance. If an Agent cluster is operated then the steps have to be performed for all Agent cluster members.

The patch examples will not impact an Agent installation and are used for instructional purposes only. For details see JS-1984.

...

Applying Patch on Unix

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

# download the patch file
curl https://download.sos-berlin.com/patches/2.2.3-patch/js7_agent.2.2.3-PATCH.JS-1984.jar -O

# 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/2.2.3-patch/js7_agent.2.2.3-PATCH.JS-1984.tar.gz -O

# extract the patch archive that includes .jar files
tar -xvzf js7_agent.2.2.3-PATCH.JS-1984.tar.gz

# remove the patch archive
rm js7_agent.2.2.3-PATCH.JS-1984.tar.gz

...

Applying Patch on Windows

@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/2.2.3-patch/js7_agent.2.2.3-PATCH.JS-1984.jar
@rem copy from download location (could be different from this example)
copy %USERPROFILE%\Downloads\js7_agent.2.2.3-PATCH.JS-1984.jar .

...

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

...

Removing Patch

Patches are automatically removed when an Agent release is updated or upgraded using the JS7 - Agent - Installation Using the Windows Graphical Installer or the installation scripts as indicated with JS7 - Automated Installation and Update.

...

• /var/sos-berlin.com/js7/agent/config/patches
• The directory /var/sos-berlin.com/js7/agent typically is mounted to a var volume when running the container: for details see the JS7 - Agent Installation for Containers article.
• If the config/patches sub-directorydoes not exist then it should be created before storing the patch file.
• If a patch is provided from a .tar.gz archive file then users should extract the archive and store the .jar files included to the config/patches sub-directory.

...

Applying Patches

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

...

Note: The Agent container has to be restarted to apply patches.

...

Removing Patches

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

...