Java client in Telecom Network Management (2)

In Telecom Network ManagementJavaClient (2)

 

1. Overview

The previous article describes the difficulties encountered in developing the Telecommunication Network Management Interface System Using java. Creating a network topology is the first difficulty we must overcome. This topic describes how to use and create a network topology.

2. Requirements for telecom network topology Components

The network topology is the core of the telecom network management client. When using any network topology component of a telecom network, pay attention to the following characteristics:

· Large data volumes. Generally, the telecom network has a large scale, a large number of network devices, and a complex topology. The network topology page must consider the network nodes and connections that can process large amounts of data.

· Multi-layer network display. In a comprehensive telecommunications network, various types of devices are often interconnected and carried, and run in different network protocol layers. At the same time, telecom devices may be logically and physically distributed at different levels. A network topology must be able to organize various network resources in layers.

· High efficiency. The network topology must reflect the data changes of the network management system efficiently and quickly.

· Lightweight. After all, the topology is only part of the interface system. It should not be too "heavy" in the occupation of development, deployment, and running resources ". I think it is hard to accept modules with more than 10 megabytes of memory each.

· Easy to use. Simple is good. We do not want to use all the brain cells of developers for component usage, but for the architecture design of the network management system.

3. available products

Open-source products: the most unfortunate thing is that there is no open-source or free Java Component Product dedicated for telecom network management. Although there are jgraph and other excellent open-source projects, if you use it to create a network topology, you still need a lot of development and customization. We hope that open-source or free products will be available in the future.

Commercial Products: there are not many options, as listed below:

· Ilog jtgo: This is the most famous product in this field. You can search for this product on Google to see how many company recruitment information has been mentioned. This is a veteran Telecom interface component product that occupies a vast majority of the market share and features comprehensive and stable products. Jtgo is developed on jviews, another drawing product based on ilog. Therefore, jviews packages are required for development and operation. Therefore, jtgo is relatively large (about 11 Mb ). Jtgo provides ready-to-use components such as maps, device panel charts, trees, and tables, as well as a large number of documents and routines, providing great convenience for development. Jtgo supports XML data and thin client technology and is suitable for Web applications. However, the architecture design of jtgo is complicated, and there are many APIs. It takes a lot of effort to thoroughly master the use of this product.

· Jloox: jloox is a powerful java2d product. It has a jloox Telecom product package specifically provided for the telecom industry and is specially used for the development of OSS/EMS/NMS interfaces in the telecom industry. Jloox also has a small number of applications in China. However, ilog has recently officially acquired the jloox product line from engenuity. Ilog claims on the website that it encourages original jloox customers to transfer to the ilog jviews product for better support. Because the jloox product line and the ilog product line jviews/jtgo overlap too much, the prospect of jloox is very gloomy.

· Serva software twaver: twaver is a new product of serva software. Unlike the above-mentioned products, which have a complete java2d drawing function, twaver is designed with a very clear goal for the development of the telecom network management interface. It is similar to jtgo in terms of functions, including provided components, Business Objects, API design, XML data support, and editor programs. Twaver is lightweight, efficient, and easy to use. The release package of twaver is not only about 1 MB, but can carry thousands of nodes and connections. It also maintains a good response speed and occupies about 2.5 MB of memory/nodes.

4. Architecture

In the design of the telecom network management interface, the MVC design principles should be followed to separate the storage, presentation and control of data, so as to facilitate system expansion.

If the entire NMS system is regarded as an MVC Framework, the GUI part is the view of the system. In the GUI view, various interface rendering elements (dialog box, component package, etc.) are considered as views based on MVC principles, and various resources, business objects, and running information are considered as models. The frontend and backend interaction can be completed through EJB call and JMS messages.

The design of various network topology component products follows the MVC design principles. Therefore, you can design the entire GUI architecture in accordance with the "MVC layer-by-layer nesting" mode, to facilitate system expansion.

5. End

Next, we will use ilog's jtgo and Serva's twaver code to demonstrate how to create a simple network topology.