Page History

...

The Controller expects Java .jar libraries files holding patches in the following locations:

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

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

...

Apply the following steps for to a Controller instance. If a Controller cluster is operated then these the steps have to be performed for all Controller instances.

...

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

...

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

...

Patches are not applied persistently to a container. Therefore patch Patch files remain in place in the the /var/sos-berlin.com/js7/controller/config/patches sub-directory (typically mounted to a volume) as long as the patch is to be appliedfor the lifetime of the Controller release in use. Patch files have to be removed if a newer release of the Controller is used.

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

...

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

Patch files are not automatically removed when updating or upgrading the Controller image. If a newer Controller release is used then this includes any fixes provided by previous patches. Users have to remove patch files when applying new releases.

Note: The Controller container has to be restarted to apply removal of patches.

...