Blansh Technologies

Home - who we are



Targeted applications:

Broadband Network System Management

Retail Chain and Warehouse System Management

Manufacturing System Management



Our philosophy:

Simplicity

Modularity

Completeness of design and life cycle

Right tools

Portability



List of tasks we have done for your project

Global architecture

Management Server

Tools

FAQ

Contact us

Partnership opportunity - marketing



Intranet-based Management System Framework documentation (these pages require log-in authorization from Blansh Technologies):

Blansh Technologies Server

Authorization process

Web Browser GUI

GUI login and administration

GUI System Queries

GUI Managed Elements Status Tree

GUI Customer Operations

GUI Exporting Data

Broadband Network Control Reference Implementation

Broadband Network Control : Modem Simulator


    Overview of the Blansh Management Server

    This section provides only a global view of the elements of the Blansh Server to see how it fits into the global architecture of the Intranet-based Management System. For simplicity purpose many internal elements are not shown here, but are shown in the Blansh Technologies Server page. A term of the <Interface Request Server> incorporates a server process which performs a list of the scenarios, each one initiated by the received message from the respective interface. Such a Server hosts all the code needed to process the scenarios and persistent data models associated with those scenarios.

        Server comprising elements

Web Server primarily serves the Browser Clients requests passing them to the Interface 1 Request Server. Before propagating request further, Web Server works as a second-level gate into the system by verifying eligibility of the user for each request.

Interface 1 Request Server performs scenarios triggered by either Web Server requests ( Manager ) or by requests from the Manager ( Agent Server ).

Interface 2 Request Server performs scenarios triggered by either requests from the Agent ( Manager Server ) or from the managed elements connected to the local subnet.

Database Access Manager provides database service to the Blansh Server. It is using Interface 1 for communication and incapsulates all the details of connecting to the database and encoding/decoding data.

        Communications

    Internet : connecting Browser-based client to the Manager Server ( type 2 of the System ) or connecting all the Servers of the system (type 1).

    Protocols : URL, TCP/IP , JAVA Serialization between JAVA Applet objects and Web Server's Servlet

    Manager to Agent communication: JAVA Serialization over TCP/IP

    Agent to the Local subnet ( to the Managed Elements): Blansh Server-based Agent Server is ready to interface with most of existent legacy servers and back end equipment due to our proprietary message modeling technique. Internally it is based on our <simple types big endian encoding/decoding over TCP/IP> library as this type works well with most legacy servers and embedded systems. Message modeling is the Blansh Technologies proprietary library based on our JAVA classes representing protocol messages for the managed elements. If needed, our decoding/encoding library can be updated to add other types of encoding over the IP network. All these in order to support any application layer protocols for the managed elements and to reuse our back end messages supporting libraries.

    Connection to the Database : SQL over TCP/IP

    Inter-process communications : Web Server to Manager uses a JAVA Serialization over TCP/IP .


Blansh Technologies Proprietary