Catalog setup

Back

LBL Management Console is a client program (WebApp) that depending on the type of license you configure with the supported features.

The license LBL Catalog, installed in the service LBL Monitor, enable LBL Management Console to operate as a concentrator instances LBL SAAI within the datacenter, provides the ability to update cluster and allows group actions of services.

Being the suite LBL SAAI a product intended for mission-critical environments  business-critical staff only that has taken the course and has passed the exam and authorized to certify the installation and maintenance of the products. All certified individuals are equipped with a document issued by TCOGROUP SRL.

LBL Catalog: Preparing to install the license

To install the license LBL Catalog and then enable the capabilities of the management centralized and clusters of the LBL Management Console, you must acquire a license LBL Catalog .

If you are not in possession of a license   LBL Catalog, you can make a request to TCOGROUP SRL or an authorized reseller.

LBL Catalog: license Installation

Once you have initiated   LBL Management Console and login to the node designated to accommodate  LBL Catalog perform the following operations:

Select the first level of the tree of processes. This level will identify the node   LBL Catalog. With the right mouse button select Install license:


Select the license from appropriate that must necessarily be called license.xml .

Once confirmed your license will be displayed the result of the upload. If WE WOULD THEREFORE DO WELL go to the next step

Restart the process LBL Monitor

Once you have successfully installed the license it will be necessary to proceed with the restart of the  LBL process Monitor. To make the restart of the  LBL process Monitor is necessary to go on the guest operating system and run:

Linux/Unix:

1) Identification of process java with definition -DLBL_RUNLEVEL=0

2) Perform a kill  -15 of process identified in point 1

3) Wait until the end of the processes controlled by LBL Monitor

It is possible to see the situation evolves¬†through ¬†LBL Management Console¬†that highlights the shutdown¬†¬†controlled managed jobs ….

LBL Management Console : disconnect

Once all of the processes LBL SAAI have terminated their operation, highlighted by a showy red X prepend to the nodes of the tree, perform disconnect:


The status of the LBL Management Console should return to NO LOGGED.

LBL Monitor: Start with license Catalog

Depending on the selected operating system run the start of the main process LBL Monitor which will take the new license LBL Catalog.

LBL Management Console Connect to LBL Catalog


From the management console, select the Connect button:


Type your Login and Password and if successful will be the connection with Catalog feature …

LBL Catalog: configuration

The configuration of LBL Catalog and functional management using a single LBL Management Console more instances LBL SAAI distributed in the datacenter  or distributed in multiple datacenters .

LBL Catalog allows you to list in a very simple manner nodes LBL SAAI and  catalog the instances that must maintain the same configurations (Cluster).

To access the list, simply select the first element of the tree (root) that indicates a connection to a catalog, with the right button then select “Properties catalog”.


In the right pane will be possible to indicate the list of nodes LBL SAAI within the datacenter. The template provided sets as a comment some examples.

To begin moving the first paragraph <monitorid> outside of the comment and edit it with the address of the node that performs the functions of catalog.

FROM:

<Monitors>

< !-- ipv4 example

<Monitorid address="192.168.46.109 :54443" Description="Node TO" />

<Monitorid address="192.168.46.110 :54443" Description="Node B" />

<Monitorid address="192.168.46.111 :54443" Description="Node C" />

-->

< /Monitors>

 

TO:

<Monitors>

<Monitorid address="192.168.46.109 :54443" Description="Node TO" />

< !-- ipv4 example

<Monitorid address="192.168.46.110 :54443" Description="Node B" />

<Monitorid address="192.168.46.111 :54443" Description="Node C" />

-->

< /Monitors>

 

Then run the upload of the parameters of catalog:

After the upload by expanding the root element  will appear the first managed node which is also the same catalog.

It can be noticed immediately two symbols new and a different color.


These symbols indicate that the process management is a process “cluster”. It has not yet indicated nothing in paragraph ( <clusters>¬†LBL¬† Management Console¬†shows, however the processes that by their nature are clusters as for example instances¬†LBL Loadbalancer¬† Standard/Enterprise HAS¬†or¬†LBL Commander Decision¬†Engine.

Going to add in the catalog other nodes LBL SAAI these will appear in the order indicated in the parameter¬†Catalog, in the tree to the left ….

FROM:

<Monitors>

<Monitorid address="192.168.46.109 :54443" Description="Node TO" />

< !-- ipv4 example

<Monitorid address="192.168.46.110 :54443" Description="Node B" />

<Monitorid address="192.168.46.111 :54443" Description="Node C" />

-->

< /Monitors>

 

TO:

<Monitors>

<Monitorid address="192.168.46.109 :54443" Description="Node TO" />

<Monitorid address="192.168.46.110 :54443" Description="Node B" />

< !-- ipv4 example

<Monitorid address="192.168.46.111 :54443" Description="Node C" />

-->

< /Monitors>

 

Already by this time for the “Cluster” spontaneous and can perform common actions such as keeping aligned the configurations or perform¬†reinit¬†hot simultaneously …

For example, if we try to perform a configuration upload of the balancing system¬†LBL¬† Management Console¬†will ask us to run also in node/the “twin” in cluster.

In this case we also highlight that the “Catalog” is not aligned as configuration to “Cluster” spontaneous¬†LBL LoadBalancer Standard HAS (Match = false in the table of the nodes in the cluster).It is recommended to always keep aligned even the definitions of spontaneous cluster with the catalog, in complex environments have a point where this information is listed increases the order documentative very important for the operation. In any case for “Cluster spontaneous”, i.e. , for nature of the process, the alignment is still carried out in all the selected nodes of the cluster.

The first column proposal allows you to deselect update the/nodes in the cluster. This can be useful in case you want to first perform a test in a node, and then making it definitive with the next upload.

LBL Catalog: declaration of cluster

As we have seen from the preceding paragraphs¬†LBL¬† Management¬†Console recognizes¬†the “Cluster spontaneous” without the need of other parameters. However, it is often necessary to treat as cluster also processes that by their nature are not. An example for all and wanting to keep aligned the configurations of the CATALOG itself with a instance CATALOG of backup in case the main CATALOG was unavailable.

In this case we are talking about “Cluster declared” in CATALOG to allow the simultaneous updating. In paragraph <clusters> move the paragraph with description “catalog” outside of the comments:

FROM:

<Clusters>

< !-- cluster examples

<Clustergroup description="Catalog">

<Monitorid address="192.168.46.109 :54443" processname-="** CATALOG **" />

<Monitorid address="192.168.46.110 :54443" processname-="** CATALOG **" />

< /Clustergroup>

<Clustergroup description="Monitor ">

<Monitorid address="192.168.46.109 :54443" processname-="** MONITOR **" />

<Monitorid address="192.168.46.110 :54443" processname-="** MONITOR **" />

< /Clustergroup>

<Clustergroup description="LoadBalancer">

<Monitorid address="192.168.46.109 :54443" processname-="TO10_LBLGo" />

<Monitorid address="192.168.46.110 :54443" processname-="TO10_LBLGo" />

< /Clustergroup>

<Clustergroup description=" CommanderDecision Engine ">

<Monitorid address="192.168.46.109 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.110 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.111 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

< /Clustergroup>

-->

< /Clusters>

TO:

<Clusters>

<Clustergroup description="Catalog">

<Monitorid address="192.168.46.109 :54443" processname-="** CATALOG **" />

<Monitorid address="192.168.46.110 :54443" processname-="** CATALOG **" />

< /Clustergroup>

< !-- cluster examples

<Clustergroup description="Monitor ">

<Monitorid address="192.168.46.109 :54443" processname-="** MONITOR **" />

<Monitorid address="192.168.46.110 :54443" processname-="** MONITOR **" />

< /Clustergroup>

<Clustergroup description="LoadBalancer">

<Monitorid address="192.168.46.109 :54443" processname-="TO10_LBLGo" />

<Monitorid address="192.168.46.110 :54443" processname-="TO10_LBLGo" />

< /Clustergroup>

<Clustergroup description=" CommanderDecision Engine ">

<Monitorid address="192.168.46.109 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.110 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.111 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

< /Clustergroup>

-->

< /Clusters>

If we pass a few moments, max 3¬†¬†seconds as a rule, and let’s try again to perform the upload will be the proposal request to also update the node CATALOG declared as cluster:

Normally the¬†processname-¬†must be declared the name of the process e.g. : A10_LBLGo or03_LBLGoSurfaceClusterDE etc. There are two reserved keyword in order to be able to declare cluster both the¬†catalog¬†” ** CATALOG ** ” is the monitor ” ** MONITOR ** ” to allow simultaneous actions on multiple nodes also of these elements.

We repeat the same edit also to manage simultaneously configuration changes LBL Monitor .

FROM:

<Clusters>

< !-- cluster examples

<Clustergroup description="Catalog">

<Monitorid address="192.168.46.109 :54443" processname-="** CATALOG **" />

<Monitorid address="192.168.46.110 :54443" processname-="** CATALOG **" />

< /Clustergroup>

<Clustergroup description="Monitor ">

<Monitorid address="192.168.46.109 :54443" processname-="** MONITOR **" />

<Monitorid address="192.168.46.110 :54443" processname-="** MONITOR **" />

< /Clustergroup>

<Clustergroup description="LoadBalancer">

<Monitorid address="192.168.46.109 :54443" processname-="TO10_LBLGo" />

<Monitorid address="192.168.46.110 :54443" processname-="TO10_LBLGo" />

< /Clustergroup>

<Clustergroup description=" CommanderDecision Engine ">

<Monitorid address="192.168.46.109 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.110 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.111 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

< /Clustergroup>

-->

< /Clusters>

 

TO:

<Clusters>

<Clustergroup description="Catalog">

<Monitorid address="192.168.46.109 :54443" processname-="** CATALOG **" />

<Monitorid address="192.168.46.110 :54443" processname-="** CATALOG **" />

< /Clustergroup>

<Clustergroup description="Monitor ">

<Monitorid address="192.168.46.109 :54443" processname-="** MONITOR **" />

<Monitorid address="192.168.46.110 :54443" processname-="** MONITOR **" />

< /Clustergroup>

< !-- cluster examples

<Clustergroup description="LoadBalancer">

<Monitorid address="192.168.46.109 :54443" processname-="TO10_LBLGo" />

<Monitorid address="192.168.46.110 :54443" processname-="TO10_LBLGo" />

< /Clustergroup>

<Clustergroup description=" CommanderDecision Engine ">

<Monitorid address="192.168.46.109 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.110 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

<Monitorid address="192.168.46.111 :54443" processname-="TO03_LBLGoSurfaceClusterDE" />

< /Clustergroup>

-->

< /Clusters>

 


Then we upload the configuration …

From this moment even for configurations LBL Monitor will be proposed to align them during updates ..

In this regard the release 9 has been introduced the use of the variables that tipizzano the single node¬†LBL SAAI And the process within the node. This technology allows you to maintain configuration files identical on different nodes. Variables are used to indicate in the configuration files of symbolic values that during upload are replaced with the typical value of¬†LBL Monitor and¬†/or process¬†… and¬†it is possible to define the variables in the section¬†procproperties.

LBL Catalog: use of procproperties

Procproperties serves to define the symbolic values that can be used inside the configuration file. This technology allows you to describe the parameters not value but its symbol that varies from one instance to another.

Take, for example, the configuration file of the process LBL Monitor .The most important value is surely the address where LBL Monitor performs his listening (highlighted in yellow) e.g. :

< /Copyright>

  <Monitors>

<Params address="192.168.46.110" port ="54443"

Keymanagerfactory="SunX509"

Managementportrangemin="5850"

Managementportrangemax="5990"

Syscommandremoteurl="https://localhost:5992/syscommand"

Statisticbrokerwebcacheurl="http://localhost:5993">

< /Params>

…

This value is certainly different for each individual LBL Monitor and therefore a possible update of the configuration file on another LBL Monitor would cause a substantial problem in operation.

In¬†procproperties tab¬†(file) and then you can define the symbolic names¬†of typical instance ¬†LBL Monitor¬†such as the address of¬†listening¬†of the monitor …

<Variables>

<VAR name ="LBL_GLOBAL_ADDRESS_MANAGEMENT" value="192.168.46.110" />

And, once the upload, change the address in the file monitor parameters by replacing it with a symbolic name. N. B. You will notice that the upload file procproperties has not required the updating of the other cluster nodes. This is important because the procproperties are typical of the node LBL Monitor and/or process and should NOT be propagated to the other cluster nodes.

< /Copyright>

  <Monitors>

<Params address=" #LBL_GLOBAL_ADDRESS_MANAGEMENT#" port ="54443"

Keymanagerfactory="SunX509"

Managementportrangemin="5850"

Managementportrangemax="5990"

Syscommandremoteurl="https://localhost:5992/syscommand"

Statisticbrokerwebcacheurl="http://localhost:5993">

< /Params>

…

The template file  distributed with the rel 9 show already preset variables that serve to facilitate the work of initial setup.

LBL Monitor,for example, contains the following preset variables whose use is already arranged in configurations template:

<Variables>

  <VAR name ="LBL_GLOBAL_ADDRESS_MANAGEMENT" value="192.168.46.110" />

  <VAR name ="LBL_GLOBAL_ADDRESS_BROKERWEBCACHE" value="localhost" />

   <VAR name ="LBL_GLOBAL_URL_BROKERWEBCACHE" value="http://#lbl_global_address_brokerwebcache#:5993" />

  <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_LOADBALANCER" value="-XX: +UseParallelGC -XX: +UseParallelOldGC" />

  <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_WEB_CACHE_DWH" value="-XX: +UseParallelGC -XX: +UseParallelOldGC" />

< !-- Please NOTE: G1 garbage collector only with jdk 1.7 .0_xx You can find xx in LBL's compatibility matrix -->

< !-- <var name ="LBL_GLOBAL_GARBAGE_COLLECTOR_LOADBALANCER" value="-XX: +UseG1GC -XX:InitiatingHeapOccupancyPercent= 45" />

< !-- <var name ="LBL_GLOBAL_GARBAGE_COLLECTOR_WEB_CACHE_DWH" value="-XX: +UseG1GC -XX:InitiatingHeapOccupancyPercent= 45" />

   <VAR name ="LBL_GLOBAL_START_HEAP_LOADBALANCER" Value="-Xms1g -Xmx1g" />

< /Variables>

< /Copyright>

  <Monitors>

<Params address=" #LBL_GLOBAL_ADDRESS_MANAGEMENT#" port ="54443"

Keymanagerfactory="SunX509"

Managementportrangemin="5850"

Managementportrangemax="5990"

Syscommandremoteurl="https://localhost:5992/syscommand"

Statisticbrokerwebcacheurl=" #LBL_GLOBAL_URL_BROKERWEBCACHE#">

< /Params>

…

LBL Catalog: hierarchy, inheritance, and mops procproperties

FILES procproperties define symbolic names, which is given a value. The symbolic name can be used inside the configuration file and it is replaced at the time of loading the file with the values defined by symbolic name.

FILES procproperties are of two types:

1) At the level of LBL Monitor

2) At the level of process managed by LBL Monitor

From the point of view including visual inspection we can set through LBL Management Console by selecting properties in the following levels of the tree:

LBL Monitor brooms

Process brooms

If you define a variable node level LBL Monitor this will be usable also by processes managed by him. The variables defined at the level of process will be used only in specific process. There are no differences in the level of symbolic name, is still recommended distinguish level variables LBL Monitor by the variables at the process level. In the templates  supplied is prepended a LBL_GLOBAL_xxxxx variables LBL Monitor with respect to only LBL_xxxx used in process variables.

It is possible to overwrite variables already declared simply declaring them again. The sequence of statement is the factor that determines the final value.

For example if we take away the comments of definition of G1¬†garbage collector¬†variables would assume the last declared value …

FROM:

<Variables>

  <VAR name ="LBL_GLOBAL_ADDRESS_MANAGEMENT" value="192.168.46.110" />

  <VAR name ="LBL_GLOBAL_ADDRESS_BROKERWEBCACHE" value="localhost" />

   <VAR name ="LBL_GLOBAL_URL_BROKERWEBCACHE" value="http://#lbl_global_address_brokerwebcache#:5993" />

  <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_LOADBALANCER" value="-XX: +UseParallelGC -XX: +UseParallelOldGC" />

  <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_WEB_CACHE_DWH" value="-XX: +UseParallelGC -XX: +UseParallelOldGC" />

< !-- Please NOTE: G1 garbage collector only with jdk 1.7 .0_xx You can find xx in LBL's compatibility matrix -->

< !-- <var name ="LBL_GLOBAL_GARBAGE_COLLECTOR_LOADBALANCER" value="-XX: +UseG1GC -XX:InitiatingHeapOccupancyPercent= 45" />

< !-- <var name ="LBL_GLOBAL_GARBAGE_COLLECTOR_WEB_CACHE_DWH" value="-XX: +UseG1GC -XX:InitiatingHeapOccupancyPercent= 45" />

   <VAR name ="LBL_GLOBAL_START_HEAP_LOADBALANCER" Value="-Xms1g -Xmx1g" />

< /Variables>

TO:

<Variables>

  <VAR name ="LBL_GLOBAL_ADDRESS_MANAGEMENT" value="192.168.46.110" />

  <VAR name ="LBL_GLOBAL_ADDRESS_BROKERWEBCACHE" value="localhost" />

   <VAR name ="LBL_GLOBAL_URL_BROKERWEBCACHE" value="http://#lbl_global_address_brokerwebcache#:5993" />

  <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_LOADBALANCER" value="-XX: +UseParallelGC -XX: +UseParallelOldGC" />

  <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_WEB_CACHE_DWH" value="-XX: +UseParallelGC -XX: +UseParallelOldGC" />

< !-- Please NOTE: G1 garbage collector only with jdk 1.7 .0_xx You can find xx in LBL's compatibility matrix -->

   <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_LOADBALANCER" value="-XX: +UseG1GC -XX:InitiatingHeapOccupancyPercent= 45" />

   <VAR name ="LBL_GLOBAL_GARBAGE_COLLECTOR_WEB_CACHE_DWH" value="-XX: +UseG1GC -XX:InitiatingHeapOccupancyPercent= 45" />

   <VAR name ="LBL_GLOBAL_START_HEAP_LOADBALANCER" Value="-Xms1g -Xmx1g" />

< /Variables>

In this case the variables highlighted will assume the values G1 overwriting values¬†ParallelGC …

The values at LBL Monitor are inherited by the individual processes. You can then use or overwrite process-level values   LBL Monitor. Eventual overwriting values   LBL Monitor to process level does not change the values for the other processes.

LBL Catalog: shares distributed

Once listed in the catalog nodes¬†LBL SAAI and the associations of cluster processes¬†LBL Management Console¬†reacts to commands by proposing shares distributed in the nodes that make up the cluster. So for example, if you want to perform a “reinit” hot of a configuration¬†LBL Management Console¬†we will propose to run also on the nodes components of the cluster, this independently if the cluster is spontaneous or declared.

After selection you will be prompted whether to perform the operation even in the other nodes of the cluster:

To confirm the cluster services will perform the action of¬†reinit¬†simultaneously. The action is directly visible on¬†LBL Management Console¬†if you expand the services of the affected process. It will be noted on the service in cluster, the symbol of the “reinit” act in the same manner as the selected node.

For all the actions provided for LBL Management Console will ask for confirmation to the operator with the list of nodes involved in the distributed and give you the possibility to select on which nodes perform the action