JLupin CLI Console is a dedicated for JLupin Platform management tool that interacts with the environment using TRANSMISSION port, as show on the picture below.

Figure 1. JLupin CLI console and JLupin Platform.

JLupin CLI Console invokes services available on TRANSMISSION port, which are translates by Main Server into atomic actions performed on components of the platform or microservices. This model of integration is common for all management tools provided by JLupin.

Deployment plans

JLupin Platform CLI Console can be deployed in two ways:

  1. Embedded - it is included in JLupin PLatform package available on our site (download). By default, it is located in $JLUPIN_HOME/platform/start and executed through control.sh / control.cmd scripts, depending on the platform.

  2. Standalone - it can be deployed as an independent instance, located on different server than Main Server as shown on below picture.

Figure 2. JLupin CLI console deployed standalone.

In that case the address parameter should be changes in runtime configuration or address should be explicitly provided as an inline parameters during console execution (see next chapters to get to know more).


TRANSMISSION port is by default secured with SSL two-way authentication. It indicated that in order to establish the connection from client (JLupin CLI Console in this case) to the server you need:

  • locate server's certificate in the client's configuration, the server is trusted in that way for the client
  • locale client's certificate in the server's configuration, the client is trusted in that way for the server.

as presented on the below picture.

Figure 3. JLupin CLI console authorization.

Private key should be hidden from other components of the environment and their users.