Commercial patching

The upgrade process applies to the major (1.6.X.0 -> 1.6.Y.0) and minor (1.6.X.Y -> 1.6.X.Z) versions. It requires individual analysis, the result of which is precise conditions and procedure of the upgrade process.



A patchset contains bug fixes and related small changes and is designed for particular version of JLupin Platform. Patchsets are differential, which means that all intermediate patchsets should be applied to get the latest version of JLupin Platform.

For example, to get JLP having the release version ( you have to apply the following patchsets in exact order:

  1. JLP160_ps1
  2. JLP160_ps2
  3. JLP160_ps3

The patchset number relates to release version (in this example: 1.6.0) and is reset after next release (for example: 1.6.1).

Patchsets are provided only for supported JLupin Platform installations and are available in download section.

NOTICE that also a patch can be provided as a bug resolution, in that case it's provided individually in our support portal, attached to the issue. Each patch provided in that way is also included in the next patchset.



  1. Get the patchset file (for example:
  2. Create $JLUPIN_HOME/platform/patches directory if doesn't exist.
  3. Unzip the patchset file in $JLUPIN_HOME/platform/patches
  4. Go to patchset directory (in this example: $JLUPIN_HOME/platform/patches/JLP160_ps2)
  5. Shutdown JLupin Platform (node shutdown using control tool)
  6. Start the patchset installation process (on Windows: patch.cmd, on Linux:
  7. Check the logs (in this example: $JLUPIN_HOME/patches/JLP160_p2/patch.log)
  8. Check if any individual tasks should be performed
  9. Start JLupin Platform and check if it's up and running.
  10. Raise an issue in case of any errors (through support portal), with patch.log and (optionally) any other problems that occurred.


There is now available patch for 1.6.0