Management Console setup


Install  LBL LManagement Console is very simple because it does not use any installer and is fully self-consistent.

Being the suite LBL a product intended for mission-critical environments  business-critical only certified people are authorized to maintain installation of the products. All certified individuals are equipped with a document issued by Oplon.

Preparing to install

The product file is a single file in a compressed format with names of the following example:

The first part indicates the distribution contained while the number indicates the release, the sub-release, the build. Once the file has been decompressed the content is as follows:

├LBLManagementConsole_aai_002_00x_00x (LBL_HOME)

├── Conf  (Directory with configuration file)

│ └── Template_rhe.xml

├── Confschemes  (Directory with XSD schemas of local verification)

│ └── License.xsd

Extlib ├── (Runtime Directory of external libraries)

│ ├── Jcommon-1.0.16 .jar

│ ├── Jfreechart-1.0.13 .jar

│ ├── Jfreechart-1.0.13 -swt.jar

│ └── Jlfgr-1_0.jar

├── LBL_LICENZA.txt  (License Management Console)

├── LBLManagementConsole_lib.jar (Library application LBLR)

├── LBLManagementConsole_start.jar  (Starter)

├── LBLManagementConsole_startCLI.jar  (Starter Command Line and SDK)

├── Legacybin  Directory (legacy)

├── Lib  (Directory system)

│ └── Hardlogs  (Logs)

├── RELEASE_NOTES.txt  (Release Notes)

├── Shouldfollow  (Third-party Directories licenses and libraries)

│ ├── Jfreechart-1.0.13 .zip

│ ├── JFreeChart_licence-LGPL.txt

│ └── Jlfgr-1_0_LICENSE.txt

└── THIRD_PARTY_LICENSE.txt  (Description list licenses third party)

Compatibility Matrix


Check the compatibility matrix in the white paper document.


MS Windows:

Use the Oracle JRE setup-


It is recommended to use JRE/JDK in Compressed Mode Binary tar.gz


It is recommended to use JRE/JDK in Compressed Mode Binary tar.gz


Use the JRE/JDK in MAC format and perform the installation


From release 2.0.3 LBL Management Console doesn’t need any license.

NB: If you proceed with an update from baring  release  delete the file from license.xml LBL_MANAGEMENT_CONSOLE_HOME directory/conf.

Start the application from MS Windows

From MS Windows if installed JRE/JDK from installation program is sufficient to perform double-click on the file:


If the associations of the extension .jar are correct should appear the splash screen  and then the login prompt:

If it does not appear the splash screen  and the application try to command dos es. :

C:\ cd (LBL_HOME)

C:\ LBLManagementConsole_aai_002_00x_00x\java -jar LBLManagementConsole_start.jar


Start the application from Linux/Unix

Go to the directory (LBL_HOME) and run:

$ Java -jar LBLManagementConsole_start.jar

Start the application from MAC OS

From MS Windows if installed JRE/JDK from installation program is sufficient to perform double-click on the file:


Connection and use of the main features

At the top of the console are 5 buttons:

The first makes a new connection to a node, the second performs the immediate closure of all the activities of the console, the third places the console in a state of lock requiring the password again to continue, the fourth allows you to change system parameters, the fifth starts the Regex Helper and the fifth shows the information relating to the management console. The pressure of the first button the following dialog appears:

The first time the window serves as ip address/name [localhost:54445]. As a result, storing up to 20 knots, will propose the last connection performed. Once you have typed the correct login and password the console requires to the node service processes LBL by displaying them in a tree.

The first level , highlighted in blue, identifies the connection, the second level identifies the node while the elements, to the third level, represent the processes.

If you are running the opening of the third level you can view the services that make up the processes. These services may be of type LBL Kernel, highlighted by a triangle orange when they are in a state of running, and type LBL User highlighted by a green triangle when you are in a state of running.

By pointing the mouse at the nodes of the tree, and pressing the right button and you can view the actions that simultaneously can be carried out:

In the leaf of the tree which identifies the node LBL you can do the following:

  1. Promote garbage

Promotes the garbage  of the LBL process Monitor®

  1. Clean all errors signalsPerforms the clean of the reporting of errors of all managed jobs from the monitor
  2. Import processImport a job in the format LBL®A. A.I.
  3. Export licenseDownloads of the license of the LBL process Monitor®
  4. Installs the licemza process of LBL®Monitor
  5.  Monitor Reinit configInitializes the values of the configuration of the monitor. This initialisation is in the part relating to configure notifications; email and HTTP post, and for the configurations of the nodes in the cluster. Paragraph <params> is not reloaded. Paragraph <params> can not be reinitialized during runtime  because it contains the values of the listener of management.
  6. Resource viewerOpens on the right side of the window display of resources relating to that process.

The resource viewer displays 3 analysis mode:


Displays two quadrants with the indication of the employment of the system’s resources relating to the memory and swap area


Appear 4 quadrants that graphically expose the status of the Monitor process.


With this display shows the memory usage of the JVM.

  1. Network interface

Shows a window with the list of characteristics of the network interfaces. The display will automatically update the vary of the network configuration.

  1. View log

Allows you to view the log, search for information through regular expressions, save the log on locally for later processing.

  1. View continuous log

Allows you to view the log in a continuous manner. The log is colored to allow you to highlight significant events.

  1. Properties

It is the function that allows you to edit the configuration file and to verify their integrity formal.

THE integrated editor checks the syntax and is capable of can validate the contents. Content is not validated does not allow you to update the configuration. You can also save or load from the local configuration. Even in these cases, the validation is needed to carry out the update files.

The leaves of the tree representing the processes if you select open a window with the functionality to be able to perform the management. If the process is a process LBL features are fully enabled.

  1. Start processExecutes the start of the process
  2. Stop processPerforms the stop of the process
  3. Clone processPerforms the clone of the process with a new name
  4. Drop processPerforms the cancellation of the process
  5. Export processPerforms the export process
  6. Export licenseDownloads of the license
  7. Install licenseInstall the license of the process
  8. Promote Garbage

Promotes the garbage collector  in JAVA

  1. Clean error signal

In case you are experiencing abnormal events is triggered, a visual indicator on the shaft of the processes. Once you have verified that the type of event with this functionality, you can eliminate the visual indication.

  1. Resource viewer

Displays information about the process LBL. Basic Information, state of the memory, the number of threads and use as a % of the CPU are the same for all processes LBL. Are different instead the information provided by type of process.

  1. View log

Displays the log with the ability to search the contents

  1. View continuous log

Continuous display of the last entry of the log

  1. Properties

Edit the configuration files.

Regex Helper and functionality can be activated from the tools bar of the Management Console. This application assists in formulazzione of regular expressions to be used in the rules of rewritings or contexts match.

This tool performs exactly the same features used during the forwarding of the information by LBL LoadBalancer and is therefore essential to the correct setting up rules and their result.

The rules can be saved locally to facilitate the steps of prototyping.

Editing the properties of the management console, you can through the choice properties:

It is possible to modify the properties of a request for confirmation of identity to disuse of the console from a minimum of 3 minutes to a maximum of 480 minutes (8 hours). This change is temporary to the work session and is not stored. At the expiration of the set time the value of the lease  time is reported to 3 minutes, and then need a new edit if you want to set a different time. This behavior has been chosen to do so that we cannot forget of settings of lease time too high that are certainly useful in setup phase but potentially dangerous during production.

Each job can have its specific views that suggest the state of the type of service.

Panels [General] and [Memory] are always present in all processes LBL SAAI . The balancing process and routing proposes two additional panels related to the use of instantaneous engine of forwarding: [Tunnels & HighWater] and [Sessions].

The display [General] proposes the four quadrants already seen previously with the internal allocation of the memory of the JVM, the number of threads  and CPU utilization.

The state of the memory of the balancing process and routing assumes a certain importance to the sizing and optimization of the use of resources.

Process details displays in textual form the status of the process. The display is dynamic being updated every 3 seconds. Among the data more interesting we can see the uptime of the process, the parameters of start, on Linux systems Unix, the number of files descriptor maximum and open …

The panels [Tunnels & HighWater] displays real time status of the tunnels of forwarding that traverse the balancing layer and routing. The two dials at the bottom show the status of the queue filling of incoming request.

The panel concerning the user sessions is a good indicator of use of the services. This value is the number of named users that are using the services.

Cluster status and the panel that appears in the case of spontaneous clusters such as the processes for balancing LBL LoadBalancer and processes LBL Commander Decision Engine

CAPTHCA INPUT (decrease human error Briefs)

To decrease the chance of human error has been introduced for all operations potentially dangerous confirmation through CAPTCHA INPUT. The confirmation through this functionality in all critical operations allows you to significantly reduce the human error derived from automatism of the action (see definitions of human error – Underpants ).

Check release and updates

At the start of the processes LBL Management Console is checked the release on our site. The data sent to the site do not contain sensitive data but show only:

Rel=99.99.99 ; license:127123163 ***** ; IP= 99999999;

REL: it is the release and the version of the product

License: it is the distinctive part of the license in use

IP: and a digest of  control

The control of release can be deactivated through the creation of the file “nocheckrelease” in home installation directory.


The signaling of the did not check is registata in (LBL_HOME) /lib/hardLogs.