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



A patch contains bug fixes and related small changes and is designed for particular version of JLupin Next Server. Patches are differential, which means that all intermediate patches should be applied to get the latest version of JLupin Next Server.

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

  1. JLNSEE1_4_0_patch1
  2. JLNSEE1_4_0_patch2
  3. JLNSEE1_4_0_patch3

The patch number relates to release version and is reset after next release. Patches are available only for JLupin Next Server Enterprise Edition from support portal or download section.


  1. Get the patch file (let's assume patch 1 for 1.4.0 - JLNSEE1_4_0_patch1.zip)
  2. Create $JLUPIN_HOME/patches directory if doesn't exist.
  3. Unzip the patch file in $JLUPIN_HOME/patches
  4. Go to patch directory (in this example: $JLUPIN_HOME/patches/JLNSEE1_4_0_patch1)
  5. Shutdown Main Server ('node shutdown' through control tool)
  6. Run the patch (on Windows: patch.cmd, on Linux:patch.sh)
  7. Check the logs (in this example: $JLUPIN_HOME/patches/JLNSEE1_4_0_patch1/patch.log)
  8. Start Main Server and check if it's up and running.
  9. Raise an issue in case of any errors (through support portal), with patch.log and (optionally) any other problems that occurred.