• Rating:
  • Views: 377
  • Author: JLupin
  • Comments: 0

"A picture is worth a thousand words"

That's way our last development sprint was focused on the web console for JLupin. Ladies and gentlemen, we are introducing the first public release of the web console for JLupin Platform. Our main goal was to provide a tool that:

  • Visualize architecture of the environment - nodes, microservices and (which was the most important challenging for us) relations between them. The goal was to show everything from the node's point of view, where webcontrol has been deployed, including remote microservices located on peers. Let's see how it works:

The view of independent node (on which webcontrol has been deployed):

The view of the node and its peers (after "node peer add" command):

  • Shows status of the environment in the simplest way, where one quick look is enough to determine if everything is OK and let users perform the basic administration tasks. We know that sometimes "the simplest" it's not enough, that's way you have also access to verbose information coming from performed actions ("Action log") and "Event log" to know what kind of action JLupin itself has performed. Let's see how it look like:

The overall status of the node:

The overall status microservices and the list of basic actions:

  • Does not limit the ability to perform any administration task on the nodes. That's way we've integrated JLupin Platform Console into the web edition, and provided through web terminal. Every command, known from control.sh/control.cmd is available here, even most advanced. Take a quick look at:

Do you like it ? If would like to taste it by in practice please refer to documentation to start quickly and easily.

What else can you find in the latest RC?

  • Startup controller that allows you to set which microservices to be started automatically when you start MainServer (start.sh / start.cmd), as well as their order of startup. It's very useful when there are dependencies between microservices and the proper order is necessary to provide services from microservice environment. Go to microservice documentation (native and servlet) to get to know how to set it in the configuration.
  • Named thread pools that keep internal processing completely under control. If you use thread pools defined in microservice configuration the process manager (internal component of Main Server) will take the state of that pool into account during graceful shutdown / restart. Total zero downtime deployment, indeed. Go to microservice documentation (native and servlet) to get to know how to set it in configuration and then look here who to use it in your code.
  • Additional startup classpath that can be added easily and safely through microservice configuration (native and servlet). Additionally, since RC6 the custom JDK can set for particular microservice much easier then before. The variety of JDKs convinced us to do it immediately :)

If you want to migrate your project from to RC6 please read this tutorial first. In case of any doubts or problems please contact us immediately.

The 1.4.1 is not finished... we are going to release this version in June 2018... we would like to encourage you to share your opinion about what we have done (use our contact form) and what we could do more (use "Your Ideas" in DevZone). Stay in touch !