Monitoring Plugin Developer Guide

Infrastructure, Model, Approach

The Monitoring PlugIn is implemented based in layered architecture, allowing to separate business logic from the logic of design. The architecture is divided into two main layers:

  1. Browser that represents the Presentation Layer.
  2. jWebSocket server representing Business Layer.

The Monitoring PlugIn does not have a data layer because it does not use a Database for operation. Furthermore, the development can be carried out at various levels. In case a change is required, this only affects the required level without having to check between codes mixing. Figure 1 Architecture of Monitoring PlugIn.

The Monitoring Demo application uses Bindows Gauges, as Java Script library which uses to display XML files called ADF (Application Description Files), for more information follow the next link: http://www.bindows.net/free_gauges/. It runs only on the client side. The Demo receives the data through the jWebSocket client and consumes features of the jQuery library. The jWebSocket client communicates with the server using the WebSocket protocol and the jWebSocket server contains the Monitoring PlugIn which communicates with the Sigar library that is responsible for obtaining any information of computer resources.

The Monitoring PlugIn was developed using the TokenPlugin model as it is a lower-level structure in which the user does not have many features and where it is easy to process messages, it is best to use since the application will work with higher performance.

Publications

Learn more about WebSockets in general, get background information and gain deeper insight!

Join jWebSocket

Wether developer, designer or translator – join the jWebSocket team and grow together with our success!

Copyright © 2013 Innotrade GmbH. All rights reserved.