WebNMS is an industry leading framework for building network management applications. With over 25,000 deployments worldwide and in every Tier 1 Carrier, network equipment providers and service providers can customize, extend and rebrand WebNMS as a comprehensive Element Management System (EMS) or Network Management System (NMS). Carrier Grade with distributed data collection for extreme high performance and scalability and high availability capabilities

NOC Operators, Architects and Developers can customize the functional modules to fit their domain and network. Functional modules include Fault Correlation, Performance KPIs, Device Configuration, Service Provisioning and Security. WebNMS supports numerous Operating Systems, Application Servers, and databases.

Below diagram illustrates the distributed architecture of WebNMS Framework. Please refer WebNMS Framework architecture for more details.

• BE - Backend server which does core FCAPS functions.
• FE- Frontend servers which serves client requests.
• DB - Databases which can be any of the suportted databases like Oracle,MySQL,Postgress and more.
• Mediation - Mediation module is part of BE server and it takes care of all southbound protocol communication.

The WebNMS Framework back-end server (BE) performs core network facing functions such as topology , inventory, maps, fault management, device configuration, network provisioning, status polling, performance management, and report generation. The Backend server also provides framework services like database persistence framework, security, high availability, logging, policy management and more.

Mediation server is a BE server module which handles all south bound protocol communication. Mediation server has adapter designed for each protocol and keeps the BE modules transparent to the south bound protocols that are used.Mediation server components always resides within the BE server JVM.

The distributed Polling Engines are individual performance data collection engines that does data collection from devices. The distributed pollers offload the data collection load from BE to allow it to perform other functions like discovery, fault etc,.A single back end can have multiple distributed pollers connected to it. This distributed architecture enables massive scalability for the framework.

The front-end (FE) server provides the communication link between the BE and the Client. FE server processes the read-only requests of the client, and redirects the request to the BE server in case of write operation. Multiple FEs can be connected to a BE and each FE can have multiple clients connected to it in a distributed setup.

WebNMS Framework can interoperate with existing Operation Support Systems (OSS) and Network Management Systems (NMS) through northbound protocols, such as CORBA, SNMP, TL1, RMI, HTTP, and JMX. On the southbound, WebNMS Framework supports multiple protocols including SNMP, TL1, CLI, XML, and CORBA.

WebNMS Framework supports Java and Web (HTML) clients. The Java clients available as Application Client, Web Start, and Applet Client are dynamic and highly customizable with feature-rich and extensible client interface. The Web client built using technologies such as Ajax, Struts, Tiles, JSP, JSTL, and Servlet with easy-to-use tabbed interface has provision to plug-in user defined customizations.

WebNMS Framework benefits:

WebNMS Framework offer following benefits as a framework to build Network management applications like EMS, NMS,Mediation solution and others.

• Flexibility by offering wide range of choice in protocols,Operating systems, database and client flavours
• High level of customization to tailor make solutions quickly.
• Faster time to market
• Reliable framework providing High availability
• Enables to meet performance and scalability needs with minimal time and effort.

Please visit WebNMS Framework benefits page to learn more about how WebNMS Framework offers these benefits.