Goto to download section and get your copy of JLupin Next Server Community Edition.


JLupin Next Server (JLNS) is distributed as zip file, in contains 'server' directory where all JLNS's resources are located. To order to install JLNS:

  1. Choose the name of the destination directory (ex. jln14ee). Please be advised that on Windows platform the name should not contain any whitespace characters.

  2. Create the destination directory (ex. /opt/JLupinNextServerEE1_4_0 or c:\Program Files\JLupinNextServerEE1_4_0)

  3. Extract downloaded archive into that directory. The full path, providing to JLNS resources (simply - files) is called JLUPIN_HOME. In our examples it would be:

on Windows:

JLUPIN_HOME = c:\Program Files\JLupinNextServerEE1_4_0\server

on Linux:

JLUPIN_HOME = /opt/JLupinNextServerEE1_4_0/server

  1. On Linux, please remember about proper rights for certain files:
chmod 750 server/start/
chmod 750 server/start/


Directory structure

- application - contains microservices files and microservices definitions by directory names.
- application_archive - contains older versions of microservices files
- logs - directory where servers are logging
- patches - directory where patches are located
- server-lib - contains Java libraries
  -- common - shared libraries across all microservices
  -- configuration - server configuration files, defined in start/configuration directory
  -- external - external, additional libraries
  -- patch - patch for server
  -- self - server library
  -- spring-boot-starter - initial libraries for webApp microservices (SpringBoot)
  -- third-party-extension - server extension library
- server-resources - xml, txt, properties and other configuration files.
- start - contains start server commands and:
  -- configuration - server configuration files
  -- control - local console libraries
  -- errors - contains error message from microservices
  -- lib - server start libraries
  -- temp - temporary directory for internal usage (scope: microservices)
- temp - temporary directory for internal usage (scope: Main Server)
- upload - default upload directory for microservice zip files.

Initial parameters

The initial configuration are provided by:


where the following parameters can be set: * JAVA_HOME - by default JLupin Next Server's start script tries to set the value automatically. Set the JAVA_HOME here when automatic mechanisms fail. * JAVA_OPTS - memory settings for Main Server' JVM process. The default value is enough for most use cases. Increase it only in case of performance issues and after consulting with support service.

Now, JLNS is ready to serve :)

Run and manage

How to start ?

Go to JLUPIN_HOME/start directory and execute:

  • on Windows: start.cmd
  • on Linux:

The starting script has its additional parameters:

  • on Windows: start.cmd [LOG_LEVEL]
  • on Linux: [-b|-i] [LOG_LEVEL]

Where LOG_LEVEL parameter can take the following values: * 'ERROR' - only errors are logged * 'WARN' - only errors, warnings are logged * 'INFO' - errors, warnings and informational messages are provided in logs (default) * 'DEBUG' - all messages, regarding DEBUG ones are provided in logs. Additionally the JVM is started with debug parameters:


On Linux, there are additional switches: * "-b" means "background mode", the JLNS starts as background process, the output of the console is redirected to log files. * "-i" means "interactive mode", the JLNS starts as foreground process, the output of the console is on the screen.

The default value is "-b".

How to check ?

If you go through this quickstart with Community Edition you can get to the example application in microservice architecture. Enter this URL to your browser:


You should get the following result:

Figure 1. The example application.

The diagram also shows the traffic flow of the request coming from you (your browser) :)

If you start JLupin Next Server on another node than your own workstations, modify the address in your browser accordingly.

The source code of this application is available at

How to manage ?

Go to $JLUPIN_HOME/start directory and execute:

  • on Windows: control.cmd
  • on Linux:

to get the list of available commands. The most popular use cases are presented below. The full description is available in further chapters.

Operate the microservice

NOTICE that all examples are prepared for Windows environment, in order to check it on Linux, please replace control.cmd to

  • Check status of the microservice

    control.cmd microservice status currency-converter-business-logic-microservice
  • Stop the microservice

    control.cmd microservice stop currency-converter-business-logic-microservice
  • Start the microservice

    control.cmd microservice start currency-converter-business-logic-microservice
  • Restart the microservice

    control.cmd microservice restart currency-converter-business-logic-microservice

If you would like to execute command in scope of all microservices (ex. restart all) don't specify the name of microservice. For example, to restart all execute:

control.cmd microservice restart

If you are interested in all management capabilities check the 'management' chapter.

Operate the node

  • Stop JLupin Next Server (and all microservices)

    control.cmd node shutdown
  • Stop force JLupin Next Server (and all microservices)

    control.cmd node terminate

What's next ?

  • Would you like to taste more with real example ? Take a look at our tutorials and start from this turorial.
  • How do you find our InteliiJ Plugin ? Try this tutorial if you like to do 'a deeper dive'.
  • Would you like to create your own microservice ? Take a look at documentation.