Configure the softswitch system based on J2EE

The configuration of the softswitch system is worth learning. Here we mainly introduce the configuration of the softswitch system based on J2EE. The Softswitch technology uses a layered network architecture to separate the call control functions of traditional circuit switches from the media gateway, and implement call control functions such as connection control, call process selection, and call routing through software.

On the one hand, Softswitch creates network convergence, and on the other hand, Softswitch uses open application interface APIs), allowing users to be independent of device manufacturers, develop and introduce new services in the network as needed, this makes the Softswitch technology have obvious advantages in comprehensive access capabilities, service provision, network management, user authentication, authentication and billing. While building a new generation network, the Softswitch technology fully takes into account the smooth transition of various existing networks and integrates voice, data, multimedia, and other services to truly customize the business. The Softswitch-based network is open and programmable, Which is the development direction of the Next Generation Network.

Softswitch System Configuration

The configuration in the softswitch system network can be divided into functional configuration and performance configuration. The main task of function configuration is to determine which devices should be included in the system and what functions should be implemented by various devices. The main task of performance configuration is to make full use of the functions of various devices in the system. The solution discussed in this article is to set a Web configuration server 1 display in the softswitch system) to allow the system administrator to remotely configure functions and performance of the softswitch system using the Web browser interface, at the same time, it also provides users with Web-based online dynamic application services, personal customization, and billing information query functions.

The configuration design overview of the softswitch system. The system administrator can log on to the system configuration server on any computer terminal in the network through a browser. After passing identity authentication, the system administrator can perform configuration management for the entire Softswitch Network. For example: system meta parameter and performance configuration management) and daily maintenance work such as system billing information statistics and query); and common users such as: can be the owner of a SIP Phone ), the system can be used to dynamically change and manage the services applied for, such as long-distance calls, international long-distance calls, voice mailboxes, and call transfers.

J2EE technology Overview

The typical multi-layer application model in the J2EE architecture is divided into four layers: Client layer ClientTier), which is generally browser, applet or other applications. The customer layer generally supports the HTTP protocol, therefore, this layer is also called customer proxy; WEB application layer WEBTier). in J2EE, this layer is run by WEB containers, including JSP, Servlet, and other WEB Components; enterprise component layer EJBTier ), this layer is run by the EJB container and supports services and technologies such as EJB, JMS, and JTA. The enterprise information system layer (EIS Tier) includes traditional information systems such as finance and CRM in the enterprise, the feature is the support of the database system.

Currently, application frameworks are mainly used at the WEB application layer. When developing the J2EEWeb layer, MVCModel-View-Controller is usually used. Struts is a free OpenSource J2EEWeb layer application architecture that inherits various MVC features, including framework classes, help classes, and customized JSP tag libraries, and all application technologies based on J2EEModel2 design patterns. Struts aims to comprehensively reduce the burden on building an enterprise-level Web application. Struts features high configuration and a list of constantly increasing features. The implementation logic and templates constitute the soul of Struts.

Controller) the Servlet in the ActionServlet class accepts requests from the client, intercepts and distributes these requests to the corresponding response class, and the Controller is also responsible for filling the ActionForm with the corresponding request parameters, and send it to Action class Action ). The ingress class implements the core business logic. It can access JavaBean or call EJB. Finally, the controls class will pass the control to the subsequent JSP file to generate the view. All control logic is configured using the Struts-config.xml file.

Model) mainly exists in the form of one or more JavaBean indicating the application state. These beans are divided into three categories: ActionForm, Action, JavaBean, or EJB ), derive a specific Action processing object from the Action according to different requests, call the business logic built by Bean to process this object, and create a derived class of ActionForm to encapsulate the form data of the client.

View) is mainly created by JSP. Struts itself contains a set of scalable custom tag libraries (Taglib), which can simplify the process of creating user interfaces. These tag libraries include: beanTags, HTMLTags, LogicTags, and Template Tags. The Struts framework uses these custom Tags to establish the relationship between views and models.

Application of J2EE technology to implement Web-based softswitch system configuration management system

The process of various applications in the configuration management system of the softswitch system is roughly the same. First, the system administrator sends a request through the client webbrowser. The ServletFilter filters the request type. if the process is within the Struts range, forward it to the Controller); the Controller receives the request and forwards the request according to the ing rules defined in the Struts-config.xml. If ActionForm is required, an example of ActionForm will be created for it, and call the validate method for data verification. If ActionForm is not required, such as a link request, the excute method of Action will be called directly for processing. If the processing result is successful, action will return the ActionForword object, and the Controller will forward the results based on the defined ing rules and generate a View), and return the result of this operation request to the Administrator.

The development process is divided into three steps. First, create View). The key to using JSP and Struts label libraries in development is to design pages and establish the relationship between views and models according to software requirements. Secondly, define Controller), the core is the configuration of Struts-config.xml, is to define the user request intercepted by Servlet and ActionForm and Action ing rules. Finally, design Model), design the necessary JavaBean based on the functional requirements of the software to meet the business processing logic of different user requests.

In the specific development work, Tiles technology and DynaActionForm Struts1.1 are used ). The powerful template function of Tiles can maximize page reusability and flexibility. Using DynaActionForm classes, you do not have to create specific ActionForm classes to reduce the number of actionforms.

Conclusion

The J2EE StrutsMVC framework is used to develop a Web-based Configuration Management System for the softswitch system. It features high performance, high scalability, and high security. This mode separates the business logic from the display page, it simplifies the system development, management, and maintenance, improves the system development efficiency, and reflects the superior technical advantages of the J2EE system.