|
|
Web NMS is a scalable and modular framework. Its open framework supports rapid development and deployment of element and network management solutions, provisioning systems, and mediation solutions. This overview aims at providing an overall look at the
The three essential constituents of Web NMS architecture are back-end server, front-end server and client.
The back-end server (BE) performs core, server-side network facing functionality tasks, such as discovery objects, receiving and processing notifications, data collection, report generation, and status polling. All updates to the database takes place through the BE server.
The front-end server (FE) provides scalability in terms of the number of clients that can be supported. High availability of the client can be achieved by increasing number of FEs that are connected to BE. FE server performs the following :
Channels all the clients' requests.
Generates the database views through database read operations using a completely stateless architecture which helps in providing the accurate information at all times.
The client acts as the user interface between the end-user or administrator and Web NMS server. The client interface is of four flavours, namely, Java Client, HTML Client, Web Start Client, and Application Client. The Client UI can be internationalized and the look and feel can be customized.
The following documents explain the functioning of BE server, FE server, different clients and their functions
Web NMS architecture supports a multiple deployment scenarios which provides high scalability. Web NMS can be deployed in a Combo setup to manage a small network or in a Distributed setup to manage large networks. The mode of deployment is dependent on certain factors, such as hardware, network size, and network management needs. The procedure to install the two modes of setup are explained as follows:
In the combo deployment, the BE server, the FE server, and the client are all present in the same physical system. This setup is useful if the network is small. In this setup, BE, FE and client are all in the same physical system and all the management is done through the local Java client.
If the network is large and involves multiple inter-networks, there will be a need to distribute the operations of Web NMS. The 3-tier architecture of Web NMS addresses this need by having BE server installed in system one or more FE servers installed in different systems, and the client in other systems. Different combinations are possible in the distributed setup i.e., there can be one BE, one FE and multiple clients connected to the FE. There could be one BE, multiple FEs, and different clients connected to different FEs. The setup is generally dependent on the network size and the management need.
Functionality Offered by Web NMS
Web NMS is an open standards-based comprehensive EMS/NMS platform. Its feature-rich support for FCPS functions and provisioning yields a high degree of customization with minimal coding. FCPS stands for fault, configuration, performance and security. These form the core services required for managing networks. Web NMS is packed with illustrative examples for a variety of application domains. Extensive Javadocs are available to enrich the programming experience.
The following are some key points to remember :
Each function in Web NMS is mapped to a Module, which is an entity that performs the function.
Each module has some controlling factors which are provided in the form of Configuration files.
Dependencies exist between the modules as the output of one module may serve as the input of another.
The following documents illustrate the various modules, the dependencies, and the associated files.
A quick glance at Web NMS Modules : Explains the various modules and the associated services provided.
Configuration Files : Explains the files which contain the parameters for customization.
Dependency between Web NMS Modules : Explains the inter-dependencies between the Web NMS modules.
|
|