Blansh
Technologies
Targeted applications:
Broadband Network System Management
Retail Chain and Warehouse System Management
Manufacturing System Management
Completeness of design and life cycle
List of tasks we have done for your project
Partnership opportunity - marketing
Intranet-based Management System Framework documentation (these pages require log-in authorization from Blansh Technologies):
Blansh Technologies Server
GUI Managed Elements Status Tree
Broadband Network Control Reference Implementation
Broadband Network Control: Modem Simulator
Blansh Technologies Server architecture
Below is depicted a detail architecture of the Blansh Server. It contains a complete set of the elements sufficient to configurable a Manager or Agent. Which Server is to be started as well as configuration parameters for all of it's elements are provided in the Vserver.properties file. Server reads this file at the start-up and configures itself. The WhoAmI configuration parameter defines the role of the Server:
WhoAmI = MGR Server starts only those threads and Proxies which build a Manager Server.
WhoAmI = AGENT Server starts only those threads and Proxies which build an Agent Server.
WhoAmI = BOTH Server starts all the threads and Proxies which perform both Manager and Agent functionality within the same JVM process. Still Manager's own threads establish connections with the Agent (identifying it according with persistent data) as any other Agent existing on the Internet, although this connection will be routed to the same JVM process back. Similarly with the Agent to Manager requests.
Web Server process.
Apache Web Server run as independent daemon with Jserv Servlet engine spawned during start-up. When a client browser loads the main entry Applet, it establishes a connection with Web Server / Servlet. Then all the requests from the Applet passed to the Servlet which process it and, if authorization succeed, passes request to the Manager Server ( Servlet Proxy ). Sessions between Client and Servlet are maintained based on the eligibility cookie.
Configuration parameters : Servlet.localHost, Servlet.localPort, Servlet.timeout
Servlet Proxy.
Processes requests from the Servlet engine and initiates a respective scenario.
Configuration parameters : ServletProxy.backlog, ServletProxy.localHost, ServletProxy.localPort
Manager / Agent Proxy.
Manages communications with Manager (if an Agent) or with Agent (if a Manager) . Initiates a respective scenario upon receiving a valid request.
Configuration parameters: ManagerProxy.backlog, ManagerProxy.localHost, ManagerProxy.localPort, AgentProxy.backlog, AgentProxy.localHost, AgentProxy.localPort
Database Access Manager.
Provides a JDBC type services to the Blansh Server. In addition to handling Database connections and running SQL queries, it performs conversions between Blansh Server messages and JDBC responses. Creates a response messages for all cases including failure of database query.
Configuration parameters: DbProxy.DbDriver, DbProxy.DbName, DbProxy.DbPort, DBProxy.HostName, DbProxy.UserName
Exporting Database Data.
When a command is received by the Database Access Manager to query database in order to export data, the result of the query is passed to the Exporting Database Data package . It formats the data into the 3 different files which names provided in the configuration parameters:
Export.exportUnixFilePath, Export.exportWinTextPath, Export.exportWinCsvPath
Message File Logger.
Provides a managed logging facility to the Blansh Server. Design of the Logger defines 5 levels of messages which are handled differently : FATAL, ERROR, WARNING, MESSAGE, DEBUG. DEBUG level can be filtered out by the configuration parameter: Logger.debug. Each level message is logged into the file defined in the configuration file. This way multiple levels can be merged into the same file, or be directed to the individual files.
Following message levels, if not filtered out by configuration parameters, are passed to the Operator Notification Manager : FATAL, ERROR, WARNING .
Configuration parameters: Logger.debug , Logger.errFileName , Logger.msgFileName , Logger.printStream
Operator Notification Manager.
Sends a notification provided by the File Logger to the Internet. It takes form of the E-Mail (or pager) notification .
Configuration parameters: Logger.mail.host, Logger.mailfrom, Logger.mailto
Agent Managed Subnet Proxy.
Handles communications with Subnet of Managed Elements and respective scenarios:
Encodes / decodes Java class representation of the data to be sent or received from the Subnet to match messages of the legacy equipment.
Spawns a respective scenarios upon receiving a valid message from the Subnet.
Updates Database records within running scenario.
Conducts a periodic polls of the managed elements as a background-daemon type of scenario with a respective database update.
Configuration parameters: ModemProxy.backlog, ModemProxy.localHost, ModemProxy.localPort, ModemProxy.remotePort, ModemProxy.timeToReportStatus
DHCP Server.
Provides a lease of the IP addresses to the managed elements in the Subnet.
