Message interception generally used in network management and processing method therefor

Abstract

Based on platform of Common Object Request Broker Architecture (CORBA), the method includes following procedures: after module of Object Request Broker (ORB) is initialized, application module registers a message capturer in ORB module; after receiving message, ORB module calls registered message capturer to capture the received message; processing the said message based on prearranged settings; dispatching the message to specific object in corresponding portable object adaptor (POA) to carry out process. Advantages are: simpler processing procedure, easy of maintenance, and expandability.

Description

technical field [0001] The invention relates to the technical field of network management, in particular to a general message interception and processing method in network management. Background technique [0002] In the current network management solutions based on the Common Object Request Broker Architecture (CORBA) bus technology, most network managements still use the method of adding log records or permission verification processing codes to the application code for network management operation logs and security management. . For example, when creating a network element, in order to record this operation log, the network management system often needs to add the corresponding log processing code in the application layer code of creating the network element; similarly, in order to determine whether the current operating user has the operation authority to create the network element, Then you also need to add the code for checking the operation permission in the applicat...

AI Technical Summary

Problems solved by technology

Existing technical solutions need to add code to the application layer code to deal with log and security verification issues, so the application layer business processing module and log security modules cannot be isolated, and the independence of business logic cannot be guaranteed

[0015] (2) Difficult to maintain

Because it is very cumbersome to insert logs and security processing codes into the processing code of each request in the application layer code, and these processing codes usually call some public functions or methods of logging or security processing, once the parameters of these public functions change , will undoubtedly bring a lot of code maintenance overhead

[0016] (3) Handling difficulties

The parameters of each operation are very different, which means that in order to record the detailed information of these operations, it is necessary to add code in the application layer to parse out the parameters of the operation and string them according to certain rules before calling public functions or object methods Recording, which directly increases the processing overhead, and once these request parameters change or the format of the record changes, the relevant code needs to be modified accordingly

[0017] (4) Poor scalability

Based on the existing technical solutions, the problem of logging and permission verification is only solved at present, and if it is necessary to expand functions on this basis, such as calculating the processing time of each request, it is necessary to redo each request processing code Add new code to support new functional requirements, and the functional scalability is very poor

Images