User Interface :

    The Xconf-Angular-Admin(UI) provides the web interface for the user to define firmware configuration for different set top boxes with regards to their Model, Environment and MAC address. There are different features with different functionality for the user to define:

  • Common:   It lets the user define different types of Model, Environment, MAC Address
  • Firmware:  It lets the user define the firmware configuration for different set top boxes with respect to MAC address, Environment and Model.
  • DCM:         It lets the user define the device configuration by managing formulas, Device setting, log upload settings, voice on demand settings, Upload repository and Test page.
    • Where device setting is to specify set top box when to send swu/stb requirements in addition to reboot.
    • Log upload setting is to specify STB, when and where to upload logs.
      • There are three levels of logs based on the cron jobs selected
  • Telemetry:  It lets the user to analyze of trends more powerful with lot of metrics. The telemetry section has the permanent profile, targeting rules and Test page.


Application:

    Angular-Admin module in xconf-oss has all the code related to UI and its functionality. It uses spring framework‘s tools such as webmvc, spring-test. RESTful service to define all the web services. It uses maven as a project build tool and jetty plugin to deploy the application in jetty server. The User Interface is designed on AngularJS framework. JUNIT and Mockito for Unit testing and slf4j, log4j for logger. This module has dependency on other modules present in xconf-oss


Rest Controller:

    The rest controllers are responsible to create, delete, retrieve and update datasets from UI into Cassandra database. It is defined under controller in xconf-angular-admin. These controllers handle the request from UI and modify the data in Cassandra through dataservice. All the request are handled by dispatcher servlet and passed to other servlet as defined in web.xml. The logging functionality defined in web.xml as a filter logs every request handled by the controllers.

  • No labels