TML setup

Back

LBL®Traffic Monetizer Light Virtual Appliance (VAPPS hereafter) is a tool for the collection of traffic data and log files of all components LBL®Global Distributed Gateway.

The system is composed of a VAPP that contains pre-installed the broker LBL®Traffic Monetizer Light, the MySQL database and a set of reports, distributed in source code form, based on TIBCO®Jasperreport preinstalled and configured to access the MySQL database.

The components are already preconfigured and it is sufficient to carry out the setup of the addresses to be able to put at the disposal of the other nodes LBL the ability to consolidate the traffic data and log on the centralized database.

Preparing to Use

To use LBL®Traffic Monetizer Light in version VAPP is enough to have performed the installation and assigned addresses to network interfaces. You can check if the addresses have been configured correctly through the console of the VAPP reachable with virtualization system used by typing your login and password:

The default login and password of Virtual Appliance:

Port number: 4444 LBL Console

5993 LBL statistic & trace broker

Login: administrator

Password: adminadmin

The default login and password MySQL:

Address: Any address of the virtual appliance

Port number: 3306

Login: root

Password: localpasswd

Default schema: LBL

The default userID and password TIBCO®Jasperreport:

Access by: http://yourAddress:8080/jasperserver

Userid: jasperadmin

Password: jasperadmin


Type: lblsetup, you will be prompted for your root password: adminadmin

Then check the address on which it is possible to connect the browser for configuration e.g.:

Then connect from your desk with the browser to port 4444 es.: https://192.168.56.11:4444

The authentication request, type the user name and password specified in the character console, optionally repeat es.:

 [root]

[adminadmin]

You will see the Dashboard to start the task:


 

Dashboard overview

LBL®Dashboard interface is designed to be used on all terminals available today that support HTML 5.

Browser & Mobile:

The Dashboard is composed by a component of choice visible or can be activated depending on the size of the screen. You can also use large monitors useful in the control room of the datacenter.

   Datacenter:

Setting the address of the service Statistic brokers

LBL®Traffic Monetizer Light has in its interior of licensing type Try&Buy which allow to use it in the cases provided for by the licenses (see legal in Http://www.oplon.net).

To their departure, VAPPS have already activated the service LBL®Traffic Monetizer Light with demo license is already started also MySQL containing the database schema LBL preconfigured.

The license type Try&Buy is unlimited in time but does not allow you to run in production.

In order to perform the first setup choose Modules >Statistic brokers> Edit:

Once you have selected the “Edit”, the system will display the parameters relative to the module LBL®Traffic Monetizer Light with his LBLGoStatisticsWebCache.

In particular, in the right pane the variable LBL_global_URL_BROKERWEBCACHE is enhanced with “localhost” that we have to change with the address where the broker will execute the listening to accept the traffic data and log to be part of the other nodes LBL.

In this case we are going to change the value of the variable to “localhost” with the IP address 192.168.56.103 to which we will then merge the data flows of traffic and log of VAPPS ADC already present in the datacenter.

 Once the change we save the change you made.

All services must be restarted to assume the new variable value:

From this moment it is possible to change in the nodes ADC or other nodes dedicated to other services, download statistics, traffic data or log on VAPP at the indicated address. In this case 192.168.56.103.

How to centralize data traffic to other nodes LBL

To centralize the downloading of data traffic and of the logs, from the local database to centralized database as soon as realized, it is sufficient to go on the console of the ADC Systems (or other services connected) and perform the following actions:

Dashboard>Modules>Statistic brokers>Edit

>General start parameters; change the mode of the start of the module from automatic to manual

Save the operation, and the module will automatically deactivate…

Repeat the operation for all modules Statistic Broker Web Cache of nodes that you want to consolidate into a centralized database.

Repeat the operation for changing from automatic to manual

All the local broker to nodes must be switched off or shutting down…


As soon as the broker you are arrested is sufficient to change the parameters to be able to download the information from the local database (now off) to centralized database previously arranged:

For each node that you want to consolidate centrally perform:

Module>Workspaces>Edit

Expand the panel with the variables of the node, if in the cluster can be more than one…

Edit variables LBL_global_URL_BROKERWEBCACHE with the address of the centralized broker In this case from localhost to 192.160.56.103



From  To

Save the operations …

When the operation is carried out to perform the restart one by one of the nodes to assume the new configuration on all modules in exercise on the node concerned. The operation lasts approximately 1 minute in which the services of that node will be suspended.

Reports

LBL Traffic Monetizer Light has pre-installed and configurator TIBCO® jasperreport open source server.

You can acecdere from http://yourAddress:8080/jasperserver console

The login and password are the default Jasperserver:

Userid: jasperadmin

Password: jasperadmin

After login to reach the reports go to:

Reports>LBLReports>choose the report

Licensing Notes Third Party

The pre-installed components MySQL and TIBCO®Jasperreports are the property of their respective manufacturers and are provided without any modification and are subject to the licenses of the respective manufacturers.

Licenses can be viewed in your installation directory as well as received from the manufacturer.

Is not provided no warranty/maintenance of components MySQL and TIBCO®Jasperreports to which reference is made to the respective manufacturers.