CN108173711B - Data exchange monitoring method for internal system of enterprise - Google Patents
Data exchange monitoring method for internal system of enterprise Download PDFInfo
- Publication number
- CN108173711B CN108173711B CN201711427371.8A CN201711427371A CN108173711B CN 108173711 B CN108173711 B CN 108173711B CN 201711427371 A CN201711427371 A CN 201711427371A CN 108173711 B CN108173711 B CN 108173711B
- Authority
- CN
- China
- Prior art keywords
- data
- main
- main data
- module
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000012544 monitoring process Methods 0.000 title claims abstract description 41
- 238000012545 processing Methods 0.000 claims abstract description 28
- 238000001514 detection method Methods 0.000 claims abstract description 15
- 230000008569 process Effects 0.000 claims abstract description 11
- 230000005540 biological transmission Effects 0.000 claims abstract description 10
- 238000004140 cleaning Methods 0.000 claims description 60
- 238000013500 data storage Methods 0.000 claims description 6
- 238000003860 storage Methods 0.000 claims description 6
- 238000012216 screening Methods 0.000 claims description 5
- 238000001914 filtration Methods 0.000 claims description 2
- 230000001419 dependent effect Effects 0.000 claims 1
- 238000005516 engineering process Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 238000013523 data management Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000019771 cognition Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
- H04L41/0609—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on severity or priority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to the technical field of data monitoring systems, in particular to a data exchange monitoring method for an enterprise internal system, which comprises the following steps: a data acquisition step, wherein a service system sends a request and data to a service module through a data interface module; a service processing step, in which a service module receives a service request and data, processes the data according to the service system request and sends the data to a corresponding service system; a data monitoring step, wherein the data monitoring step comprises the following contents: an error detection step, in which an error detection submodule detects errors occurring in the data acquisition step, the service processing step and the data monitoring step; and a data statistics step, wherein the data statistics submodule is used for counting the use condition of information resources in the data transmission process of each service system. The data exchange monitoring method for the internal system of the enterprise can enable the enterprise to supervise and control data transmitted between the business systems.
Description
Technical Field
The invention relates to the technical field of data monitoring systems, in particular to a data exchange monitoring method for an enterprise internal system.
Background
Large-scale distributed enterprise applications require relatively simple and practical middleware technologies to simplify and unify increasingly complex, cumbersome enterprise-level information system platforms. Service Oriented Architecture (SOA) is a technology that can link different functional units of an application program through well-defined interfaces and contracts between services. SOA makes users able to repeatedly use software without limit, and interconnects various resources, so that other application systems can conveniently use the functional services as long as IT personnel select standard interfaces to package old application programs and build new application programs into services.
The key to supporting an SOA is its messaging architecture — the Enterprise Service Bus (ESB). The ESB is a product of the combination of the traditional middleware technology and technologies such as XML and Web service, and is used for realizing the accurate, efficient and safe transmission of different messages and information of enterprise application. Different application services are coordinated to operate, and communication and integration among different services are realized.
The ESB middleware is mainly used for completing information exchange among all business systems of the enterprise and ensuring that all business systems of the enterprise can work normally. The current ESB middleware is outside the core framework, and only provides basic function modules such as service routing, and in practical application, with the development of enterprises, more and more business systems and larger business data volume, managers often want to monitor and control information transmitted between each system of the enterprise through the ESB middleware, and obtain the use condition of information resources of each business system, so as to perform centralized management on the information resources.
Disclosure of Invention
The invention aims to provide a data exchange monitoring method for an enterprise internal system, which can enable an enterprise to supervise and control data transmitted between business systems.
In order to solve the technical problem, the patent provides the following basic technical scheme:
the data exchange monitoring method of the enterprise internal system comprises the following steps:
a data acquisition step, wherein a service system sends a request and data to a service module through a data interface module;
a service processing step, in which a service module receives a service request and data, processes the data according to the service system request and sends the data to a corresponding service system;
a data monitoring step, wherein the data monitoring step is used for monitoring and recording data of the data acquisition step and the service processing step, and the data monitoring step specifically comprises the following contents:
an error detection step, in which an error detection submodule detects errors occurring in the data acquisition step, the service processing step and the data monitoring step;
a data statistics step, wherein a data statistics submodule counts the use condition of information resources in the data transmission process of each service system;
and a log recording step, wherein the log recording submodule generates log data according to the data in the data acquisition step, the service processing step, the error detection step and the data statistics step.
In the technical scheme of the invention, a data interface module is used for establishing data connection between the data exchange monitoring method of the internal system of the enterprise and each service system, each service system can send a request or data to a service module through the data interface module, the service module sends data to each service system through the data interface module, an error detection submodule can detect errors in the operation process of a platform in real time, such as data format errors, service system errors, network connection errors, data transmission errors and the like, and a log recording submodule can record log data generated in the process of processing transmission data by the service module, such as transmission time, transmission content, data exchange quantity, error information and the like, so that managers can check the log data conveniently in the later period; the data statistics submodule counts the use condition of each information resource in the data exchange process between each service system and the platform, such as the access quantity and the access frequency of one data, the data exchange quantity of one service system, the request quantity of one service system and the like, so that an administrator can allocate each service system conveniently according to the use condition of the information resource, for example, the load capacity of the service system with large access quantity is improved, and the data exchange quantity of the service system is controlled.
Further, the method also comprises an alarming step, wherein the alarming step specifically comprises the following steps:
the method comprises the following steps: the alarm submodule acquires the error level and the number;
step two: the alarm submodule calculates the alarm level according to the error level and the quantity and preset weight;
step three: and the alarm submodule sends an alarm to a manager corresponding to the alarm level according to the alarm level.
The alarm sub-module can send an alarm to the manager when an error is detected, the manager can be reminded to process the error in the first time, the alarm is sent to the corresponding manager according to the number of times of the error level, the manager corresponding to each error level can be informed more accurately, and the responsibility range of the manager is determined.
And further, the method further comprises a data temporary storage step, wherein the data temporary storage module stores the data to be sent when detecting that the service module sends the data to the service system in an error.
The data to be sent can be stored through the data temporary storage module so as to be sent again after the service system is normal. Data loss is avoided.
Further, the log data comprises a request service system, a target service system, time, request content, data content and error records.
According to the request service system, the target service system and the time, the flow direction of the data is convenient to track, and errors can be conveniently checked and repaired according to the data content, the request content and the error record.
Further, the service processing step includes:
and a data format checking step, wherein a data format checking submodule judges whether the data format sent by the service system is correct or not, if so, the data format is continuously processed, and if not, the data format is stopped being processed and a format error signal is generated.
And detecting whether the data format sent by the service system is correct or not, screening out error data, and avoiding sending the error data to other service systems.
Further, the data format verifying step specifically includes:
the method comprises the following steps: the data format checking submodule acquires the data type and the data name of the data to be detected;
step two: the data format checking submodule searches a standard data format of the data according to the data type and the data name, if the data format is not found, the data format checking step is ended, and if the standard data format is found, the next step is executed;
step three: and the data format checking submodule compares the number of the data with a standard data format and judges whether the data are the same or not, if so, the data format is judged to be correct, the check is passed, if not, the data format is judged to be wrong, the check is not passed, and the data format checking submodule ends the service processing step of the data.
Drawings
Fig. 1 is a logic block diagram of a data monitoring system used in an embodiment of the data exchange monitoring method for an enterprise internal system according to the present invention.
Detailed Description
The present invention will be described in further detail below by way of specific embodiments:
as shown in fig. 1, the data exchange monitoring method for the internal system of the enterprise in this embodiment uses the following data monitoring system, where the data monitoring system includes a data interface module, a service module, a data monitoring module, and a data temporary storage module, where:
the data interface module is used for sending requests and data to the service module by each service system, and is also used for sending data to each service system by the service module;
the service module is used for processing the data according to the request of the service system and sending the data to the corresponding service system; the service module comprises a data format check submodule, the format check submodule is used for detecting and checking whether a data format sent by the service system is correct, the data format check submodule comprises a format matching unit and a format check unit, the format matching unit is used for obtaining the data format of the data standard according to the data type and the data name, and the format check unit is used for verifying whether the data format is correct according to the data format of the data standard.
The format matching unit acquires the format of the data standard according to the data type and the data name so as to verify the format of the data.
The data monitoring module comprises an error detection submodule, a log recording submodule, an alarm submodule and a data statistics submodule, and the error detection submodule is used for detecting errors in the data processing process of the service module.
The log recording submodule is used for recording log data generated in the data processing process of the service module, and the log data comprises a request service system, a target service system, time, request content, data content and error records. According to the request service system, the target service system and the time, the flow direction of the data is convenient to track, and errors can be conveniently checked and repaired according to the data content, the request content and the error record.
The data statistics submodule is used for counting the use condition of information resources in the data transmission process of each service system, and comprises a processing duration statistics unit, a data volume statistics unit, an access frequency statistics unit and an access volume statistics unit, wherein the processing duration statistics unit is the same as the total duration spent by the service module for processing each service system, the data volume statistics unit is used for counting the total data volume processed and transmitted by each service system through the service module, the access frequency statistics unit is used for counting the access frequency of each service system and data, and the access volume statistics unit is used for counting the access volume of each service system and data.
The activity and the importance degree of each business system can be judged by counting the total data amount, the total data processing time, the access frequency and the access amount of the business systems and the data, and data support is provided for managers when the business systems and the data are adjusted, so that enterprises can reasonably configure and manage resources of the enterprises.
The alarm submodule is used for sending an alarm to the corresponding manager according to the error grade and the number of times when the error detection submodule detects an error. The management personnel can be reminded to process at the first time, and the alarm is sent to the corresponding management personnel according to the number of times of the error level, so that the management personnel corresponding to each error level can be more accurately notified, and the responsibility range of the management personnel is determined.
The platform also comprises a data cleaning module, the data cleaning module is used for detecting, matching and cleaning the data content sent by each service system, and the data cleaning module comprises:
the main data management module comprises a main data storage submodule approval submodule and a main data newly-built submodule, wherein the main data storage submodule stores a main data list and a data cleaning rule list, main data in the main data list corresponds to cleaning rules in the cleaning rule list one by one, and the main data newly-built submodule is used for newly building main data and data cleaning rules corresponding to the main data and respectively storing the main data and the data cleaning rules in the main data list and the cleaning rule list;
and the data operation module is used for matching the data sent by each service system according to the data cleaning rule of the main data and cleaning and replacing the matched data.
In many cases, the same data may have different expression modes, especially between different regional companies, due to the difference of regions, different calls may be made for the same content, even if the same company is used, the cognition of the same content may also change in different development periods, and the problem of data non-uniformity often occurs in each business system of a company, for example, for the name of a client company, there is a short name and a full name in the business system; for the name of a product, along with the expansion of the product function, the product needs to be changed, so that a plurality of names and the like exist in the product in a business system;
the main data list is stored and managed through the main data management module, each main data in the main data list comprises a corresponding data cleaning rule, the data operation module cleans data sent by each business system according to the main data in the main data list, and each data meeting the data cleaning rule is replaced, so that key data finally returned to each business system by the service module are standard main data, and the problem of data confusion caused by the fact that the same data in the enterprise business system are different in existing form is solved.
The main data newly-built sub-module comprises a main data input unit, a main data searching unit, a keyword matching unit and a data cleaning rule generating unit.
The main data searching unit is used for searching and verifying whether the main data input by the user exists in the main data list or not, and repeated establishment of the main data is avoided.
The keyword matching unit can automatically acquire data similar to the main data input by the user from the log data in the data content records transmitted among all the service systems as the cleaning keywords for the user to select, so that the user can know the data similar to the main data in the data transmitted by all the service systems;
the data cleansing rule generating unit can generate a data cleansing rule according to the main data input by the user and the selected cleansing keyword. The data cleaning rule comprises cleaning keywords and matching associated keywords, the matching associated keywords are used for matching data with the cleaning keywords during data cleaning, the data cleaning rule generating unit can extract the matching associated keywords according to the cleaning keywords selected by a user for the user to select, for example, for a company name, after the user selects the cleaning keywords containing the company name, the data cleaning rule generating unit automatically groups the associated data according to the common other associated data of the keywords selected by the user, such as the company address, according to the similarity for the user to select, and the selection of the user is used as the matching associated keywords.
The data operation module comprises a data replacement sub-module and a backup reduction sub-module, the data replacement sub-module is used for matching data in data transmitted by each service system through the data read-write module according to a data cleaning rule of main data, specifically, firstly, cleaning keywords are used as matching keywords to select all matched data, then, matching associated keywords are used for screening all matched data to select data matched with the matching associated keywords, and then, the matched data are cleaned and replaced according to the data cleaning rule. The data operation module is used for cleaning the data transmitted by each business system and replacing each data which accords with the data cleaning rule, so that the problem of data confusion caused by inconsistent existing forms of the same data in the data transmitted by the enterprise business system is solved.
For example, two data in the data transmitted by the service system are both ' X companies ', but the data refer to different companies, have different addresses and operate services, then a Chongqing X technology Limited liability company ' is established through the system to clean the data of the service system, and the manager takes the ' X company ' as a cleaning keyword, and at the moment, the manager needs to select and confirm the corresponding matching associated keyword, for example, the company address is taken as the matching associated keyword, so that the system can correctly distinguish the two ' X companies ' and avoid misoperation.
The log data further comprises a main data cleaning record, the platform further comprises a data cleaning reminding module, the data cleaning reminding module can acquire the category corresponding to the cleaned data according to the data content transmitted according to the cleaning record in the log data, and sends reminding information to a responsible person in the corresponding category, for example, the data content is related to a contract, and then informs a financial department and a business department, and the data is related to a product, and then informs a production department and a sales department, so that the main data is rapidly popularized and applied, and the main data is convenient for a relevant person to trace after being modified by mistake.
The method comprises the following steps:
a data acquisition step, wherein a service system sends a request and data to a service module through a data interface module;
a service processing step, in which a service module receives a service request and data, processes the data according to the service system request and sends the data to a corresponding service system;
a data monitoring step, wherein the data monitoring step is used for monitoring and recording the data of the data acquisition step and the service processing step, and the data monitoring step specifically comprises the following contents:
an error detection step, in which an error detection submodule detects errors occurring in the data acquisition step, the service processing step and the data monitoring step;
a data statistics step, wherein a data statistics submodule counts the use condition of information resources in the data transmission process of each service system;
and a log recording step, wherein the log recording submodule generates log data according to the data in the data acquisition step, the service processing step, the error detection step and the data statistics step.
The method further comprises an alarming step, wherein the alarming step specifically comprises the following steps:
the method comprises the following steps: the alarm submodule acquires the error level and the number;
step two: the alarm submodule calculates the alarm level according to the error level and the quantity and preset weight;
step three: and the alarm submodule sends an alarm to a manager corresponding to the alarm level according to the alarm level.
The data temporary storage module stores the data to be sent when detecting that the service module sends the data to the service system in error.
The service processing step comprises:
and a data format checking step, wherein a data format checking submodule judges whether the data format sent by the service system is correct or not, if so, the data format is continuously processed, and if not, the data format is stopped being processed and a format error signal is generated.
The data format checking step specifically comprises the following steps:
the method comprises the following steps: the data format checking submodule acquires the data type and the data name of the data to be detected;
step two: the data format checking submodule searches a standard data format of the data according to the data type and the data name, if the data format is not found, the data format checking step is ended, and if the standard data format is found, the next step is executed;
step three: and the data format checking submodule compares the number of the data with a standard data format and judges whether the data are the same or not, if so, the data format is judged to be correct, the check is passed, if not, the data format is judged to be wrong, the check is not passed, and the data format checking submodule ends the service processing step of the data.
The method also comprises a data cleaning step, wherein the data cleaning step is used for cleaning and filtering the data input by the service system, and the data cleaning step comprises the following steps:
a main data newly building step, wherein a user builds new main data through a main data newly building submodule and stores the main data into a main data list of a main data storage submodule, wherein the main data comprises a data cleaning rule;
and a data cleaning step, namely reading the data sent by each service system by a data operation module, matching the read data with the main data in the main data list, and replacing the matched data according to the data cleaning rule of the corresponding main data.
The main data new building step comprises a main data checking step and a main data generating step, wherein the main data checking step specifically comprises the following steps:
the method comprises the following steps: a main data newly-built sub-module acquires main data keywords input by a user;
step two: the main data newly-built sub-module reads a main data list in the main data storage sub-module and matches the main data keywords input by the user with the main data in the main data list;
step three: the main data newly-built sub-module judges whether main data with completely the same key words exists in the main data input by the user, if yes, the main data is built, and if not, the next step is executed;
step four: the main data newly-built submodule screens out main data with the similarity exceeding a preset value with the main data keyword input by a user;
step five: and the main data newly-built sub-module executes the steps from six to eight on each screened main data:
step six: the main data newly-built sub-module obtains the difference between the main data key words input by the user and the main data transmitted by screening;
step seven: the main data newly building module obtains the corresponding score of each difference and calculates the total score of the differences;
step eight: the main data newly-built sub-module judges whether the total score of the difference is within a preset difference value range, if so, the main data is marked as suspect data, and if not, the main data is skipped;
step nine: and the master data newly building module screens out all the master data marked as suspect data for the user to check and confirm.
The main data generating step specifically comprises:
the method comprises the following steps: the main data newly-establishing module acquires data contents transmitted among all the service systems from the log data and matches main data keywords input by a user with the data of all the service systems;
step two: the main data newly-built sub-module screens out data with the similarity exceeding a preset value with the main data keyword input by a user as a cleaning keyword for the user to select;
step three: the main data newly-built sub-module screens out data with high relevance to the cleaning keywords from the contents transmitted by the service system according to the cleaning keywords selected by the user, classifies the data according to the similarity, and generates relevant matching keywords for the user to select;
step four: and the main data newly-built sub-module generates a data cleaning rule according to the main data selected by the user and input by the user, the selected cleaning keywords and the matched associated keywords.
The foregoing are merely exemplary embodiments of the present invention, and no attempt is made to show structural details of the invention in more detail than is necessary for the fundamental understanding of the art, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice with the teachings of the invention. It should be noted that, for those skilled in the art, without departing from the structure of the present invention, several changes and modifications can be made, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicability of the patent. The scope of the claims of the present application shall be determined by the contents of the claims, and the description of the embodiments and the like in the specification shall be used to explain the contents of the claims.
Claims (6)
1. The method for monitoring data exchange of the internal system of the enterprise is characterized in that: the method comprises the following steps:
a data acquisition step, wherein a service system sends a request and data to a service module through a data interface module;
a service processing step, in which a service module receives a service request and data, processes the data according to the service system request and sends the data to a dependent service system;
a data monitoring step, wherein the data monitoring step is used for monitoring and recording data of the data acquisition step and the service processing step, and the data monitoring step specifically comprises the following contents:
an error detection step, in which an error detection submodule detects errors occurring in the data acquisition step, the service processing step and the data monitoring step;
a data statistics step, wherein a data statistics submodule counts the use condition of information resources in the data transmission process of each service system;
a log recording step, in which a log recording submodule generates log data according to the data in the data acquisition step, the service processing step, the error detection step and the data statistics step;
the method also comprises a data cleaning step, wherein the data cleaning step is used for cleaning and filtering the data input by the service system, and the data cleaning step comprises the following steps:
a main data newly building step, wherein a user builds new main data through a main data newly building submodule and stores the main data into a main data list of a main data storage submodule, wherein the main data comprises a data cleaning rule;
a data cleaning step, namely reading data sent by each service system by a data operation module, matching the read data with main data in a main data list, and replacing the matched data according to a data cleaning rule of the corresponding main data;
the main data new building step comprises a main data checking step and a main data generating step, wherein the main data checking step specifically comprises the following steps:
the method comprises the following steps: a main data newly-built sub-module acquires main data keywords input by a user;
step two: the main data newly-built sub-module reads a main data list in the main data storage sub-module and matches the main data keywords input by the user with the main data in the main data list;
step three: the main data newly-built sub-module judges whether main data with completely the same key words exists in the main data input by the user, if yes, the main data is built, and if not, the next step is executed;
step four: the main data newly-built submodule screens out main data with the similarity exceeding a preset value with the main data keyword input by a user;
step five: and the main data newly-built sub-module executes the steps from six to eight on each screened main data:
step six: the main data newly-built sub-module obtains the difference between the main data key words input by the user and the main data transmitted by screening;
step seven: the main data newly building module obtains the corresponding score of each difference and calculates the total score of the differences;
step eight: the main data newly-built sub-module judges whether the total score of the difference is within a preset difference value range, if so, the main data is marked as suspect data, and if not, the main data is skipped;
step nine: the main data newly building module screens out all the main data marked as suspect data for the user to check and confirm;
the data cleaning rule comprises cleaning keywords and matching associated keywords, the matching associated keywords are used for matching data with the cleaning keywords during data cleaning, when the data is cleaned, the cleaning keywords are used as the matching keywords firstly, all matched data are selected, then the matching associated keywords are used for screening all matched data, the data matched with the matching associated keywords are selected, and then cleaning and replacing are carried out on the matched data according to the data cleaning rule.
2. The method for monitoring data exchange of an intra-enterprise system according to claim 1, wherein: the method further comprises an alarming step, wherein the alarming step specifically comprises the following steps:
the method comprises the following steps: the alarm submodule acquires the error level and the number;
step two: the alarm submodule calculates the alarm level according to the error level and the quantity and preset weight;
step three: and the alarm submodule sends an alarm to a manager corresponding to the alarm level according to the alarm level.
3. The method for monitoring data exchange of an intra-enterprise system according to claim 1, wherein: the data temporary storage module stores the data to be sent when detecting that the service module sends the data to the service system in error.
4. The method for monitoring data exchange of an intra-enterprise system according to claim 1, wherein: the log data comprises a request service system, a target service system, time, request content, data content and error records.
5. The method for monitoring data exchange of an intra-enterprise system according to claim 1, wherein: the service processing step includes:
and a data format checking step, wherein a data format checking submodule judges whether the data format sent by the service system is correct or not, if so, the data format is continuously processed, and if not, the data format is stopped being processed and a format error signal is generated.
6. The intra-enterprise system data exchange monitoring method of claim 5, wherein: the data format checking step specifically includes:
the method comprises the following steps: the data format checking submodule acquires the data type and the data name of the data to be detected;
step two: the data format checking submodule searches a standard data format of the data according to the data type and the data name, if the data format is not found, the data format checking step is ended, and if the standard data format is found, the next step is executed;
step three: and the data format checking submodule compares the number of the data with a standard data format and judges whether the data are the same or not, if so, the data format is judged to be correct, the check is passed, if not, the data format is judged to be wrong, the check is not passed, and the data format checking submodule ends the service processing step of the data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711427371.8A CN108173711B (en) | 2017-12-26 | 2017-12-26 | Data exchange monitoring method for internal system of enterprise |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711427371.8A CN108173711B (en) | 2017-12-26 | 2017-12-26 | Data exchange monitoring method for internal system of enterprise |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108173711A CN108173711A (en) | 2018-06-15 |
| CN108173711B true CN108173711B (en) | 2020-12-04 |
Family
ID=62520621
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711427371.8A Active CN108173711B (en) | 2017-12-26 | 2017-12-26 | Data exchange monitoring method for internal system of enterprise |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108173711B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110941536B (en) * | 2019-11-26 | 2021-02-26 | 北京沃东天骏信息技术有限公司 | Monitoring method and system, and first server cluster |
| CN112507008B (en) * | 2020-12-02 | 2022-06-14 | 贵州航天云网科技有限公司 | Data information resource sharing system and method based on dynamic interface service |
| CN114022279B (en) * | 2021-11-05 | 2024-09-24 | 税友软件集团股份有限公司 | Service data error correction method, device, equipment and readable storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102347983B (en) * | 2011-08-26 | 2014-01-29 | 四川长虹电器股份有限公司 | ESB (Enterprise Service Bus) system in SOA (Service-Oriented Architecture) |
| CN103873287B (en) * | 2012-12-17 | 2016-12-28 | 中车青岛四方机车车辆股份有限公司 | A kind of message compensation method based on ESB message monitoring platform |
| CN104699860A (en) * | 2015-04-09 | 2015-06-10 | 成都卡莱博尔信息技术有限公司 | Data processing and storage method for sharing-type master data |
-
2017
- 2017-12-26 CN CN201711427371.8A patent/CN108173711B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108173711A (en) | 2018-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190378073A1 (en) | Business-Aware Intelligent Incident and Change Management | |
| US6918059B1 (en) | Method and system for handling errors in a distributed computer system | |
| US8938421B2 (en) | Method and a system for synchronizing data | |
| US9049105B1 (en) | Systems and methods for tracking and managing event records associated with network incidents | |
| US8868441B2 (en) | Non-disruptively changing a computing environment | |
| US8428983B2 (en) | Facilitating availability of information technology resources based on pattern system environments | |
| CN111782345B (en) | Container cloud platform log collection and analysis alarm method | |
| CN110704231A (en) | A fault handling method and device | |
| US20020099786A1 (en) | Alarm management system and method thereof for network management system | |
| CN108156061B (en) | esb monitoring service platform | |
| CN106656536A (en) | Method and device for processing service invocation information | |
| CN101582812A (en) | Monitoring and operation managing system | |
| CN110222042B (en) | Method, device, equipment and system architecture for determining checked business data | |
| CN105635331A (en) | Service addressing method and apparatus in distributed environment | |
| CN101632093A (en) | Systems and methods for managing performance failures using statistical analysis | |
| CN101582811A (en) | Method for establishing integration of network monitoring and operating management | |
| CN110088744A (en) | A database maintenance method and system thereof | |
| CN1963780A (en) | Monotoring device, monotiring method, and monotoring system | |
| CN108173711B (en) | Data exchange monitoring method for internal system of enterprise | |
| US20180239341A1 (en) | System and method for automatic configuration of a data collection system and schedule for control system monitoring | |
| KR102093764B1 (en) | Managment server for managing the server and storage | |
| CN111835566A (en) | System fault management method, device and system | |
| US6615087B2 (en) | Supervisory control apparatus | |
| CN115718690B (en) | Data accuracy monitoring system and method | |
| CN113868096B (en) | Asynchronous data transmission monitoring method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Wang Wei Inventor after: Deng Fanya Inventor before: Deng Fanya |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201119 Address after: Room 901, 902, 903, 904, No. 1358, Zhongke Road, Lane 999, huanke Road, China (Shanghai) pilot Free Trade Zone, Pudong New Area, Shanghai, 200120 Applicant after: Redpay information technology (Shanghai) Co., Ltd Address before: 400039 Jiulongpo District of Chongqing Science Park Road No. 73 of No. 8-8 Applicant before: CHONGQING INLDA SOFTWARE Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |