CN104679894A - Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system - Google Patents
Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system Download PDFInfo
- Publication number
- CN104679894A CN104679894A CN201510117979.5A CN201510117979A CN104679894A CN 104679894 A CN104679894 A CN 104679894A CN 201510117979 A CN201510117979 A CN 201510117979A CN 104679894 A CN104679894 A CN 104679894A
- Authority
- CN
- China
- Prior art keywords
- maintenance data
- data
- acquisition
- maintenance
- erp system
- 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.)
- Pending
Links
Abstract
The invention discloses an acquisition method of operation and maintenance data in an ERP (Enterprise Resource Planning) system. The acquisition method comprises the concrete implementation procedures of defining the operation and maintenance data; capturing and transmitting the operation and maintenance data; receiving and storing the operation and maintenance data. Compared with the prior art, according to the acquisition method of the operation and maintenance data in the ERP system, an uniform data acquisition format and a configurable acquisition process are defined, so that the decentralized operation and maintenance data in the ERP system privately distributed in an enterprise local area network environment can be effectively acquired.
Description
Technical field
The present invention relates to large technical field of data processing, specifically the acquisition method of magnanimity operation/maintenance data in a kind of practical, ERP system.
Background technology
Along with the development of enterprise management informatization, in numerous enterprises, all implement ERP application system, generally comprise the operation systems such as Enterprise accounting, capital management, budget management, supply chain management, human resources, objective relation management (CRM).
As ERP software product manufacturer, through client's accumulation for many years, its software product has implemented the enterprise of even tens thousand of family of thousands of family.In the ERP software application process of these enterprises, ERP system can to the various log information of the logout of system, and in the exception such as, occurred in system and fault, system, runnability related data etc., can be referred to as system operation/maintenance data.
And ERP system service data does not have effective Collection and analysis method at present, main cause comprises:
(1) most of ERP system is in the privately owned deployment of enterprises, disposes dispersion, and may not link internet.
(2) client worries in the data of collecting with enterprise's sensitive data.
(3) daily record data is mass data, and the daily record of different software versions and different purposes, form is inconsistent.
If can overcome the above problems, set up a kind of effective acquisition method of ERP service data, to the Optimal improvements of ERP system, very valuable.
Summary of the invention
Technical assignment of the present invention is for above weak point, provides the acquisition method of magnanimity operation/maintenance data in a kind of practical, ERP system.
An acquisition method for magnanimity operation/maintenance data in ERP system, its specific implementation process is:
1) step of operation/maintenance data definition, this step comprises:
1.1) operation/maintenance data type is defined;
1.2) operation/maintenance data version information is defined;
1.3) operation/maintenance data acquisition configuration information is defined;
2) the operation/maintenance data step catching and send, this step comprises:
2.1) relevant data acquisition configuration information list is loaded;
2.2) following step is performed according to the data acquisition configuration information list circulation got;
2.3) according to data acquisition configuration information, capture systems operation/maintenance data also carries out persistence buffer memory;
2.4) operation/maintenance data that this captures is sent;
3) reception of operation/maintenance data and the step of storage, this step comprises:
3.1) packet of compressed format is received;
3.2) School Affairs decompress(ion) is carried out to packet;
3.3) operation/maintenance data is stored.
In described step 1), operation/maintenance data type comprises: unique identification, numbering, title, explanation; Operation/maintenance data version information comprises: unique identification, numbering, version name, explanation; Operation/maintenance data acquisition configuration information comprises: unique identification, operation/maintenance data type identification, operation/maintenance data version identifier, operation/maintenance data form, operation/maintenance data acquisition mode.
Described operation/maintenance data form is a field description set, and this field description comprises with properties: unique identification, title, Chinese, corresponding data literary name section, data type, descriptive information.
Described operation/maintenance data acquisition mode comprises with properties: drainage pattern, whether enable increment, increased time stamp field name, corresponding data table, Procedural reflection information, wherein,
Drainage pattern is an enumerated type property, comprises two enumerated values: table schema, program schema, and table schema is stored in the scene in tables of data for the raw data gathered, and program schema is the scene needing service routine to gather;
Whether whether enabling increment is Boolean type attribute, for representing when carrying out data acquisition, filtering, only gather the change data after acquisition time last time according to the time gathered last time;
Increased time stamp field name is under the scene of table schema at drainage pattern, when enabling increment, and the title of the timestamp field in the table of corresponding source;
Procedural reflection information is under the scene of program schema at drainage pattern, for gathering the reflection recalls information of the handling procedure of operation/maintenance data.
Described corresponding data literary name section, when the drainage pattern of operation/maintenance data acquisition mode is table schema, for the mating of source literary name section.
Described step 2.3) in,
When drainage pattern is table schema, adopt plug-in processing logic, read relevant system operation data according to the corresponding data table of specifying, and form the result set of standard based on operation/maintenance data form;
When drainage pattern is program schema, according to the Procedural reflection information of specifying, load corresponding acquisition process program and perform;
Be true time when whether enabling increment, then attempt to read acquisition time last time, if read less than, then think to gather first; If read, then with this time for screening conditions, be captured in the data after this time; And gathered rear automatic record acquisition time last time at every turn;
Above-mentioned data acquisition JSON text formatting of catching describes, and adopts compressed format buffer memory.
Described step 2.4) in, when sending the operation/maintenance data that this captures, user is automatically sent by option configuration or sends after manual confirmation; And directly use step 2.3) in compressed format transmission; When sending the operation/maintenance data that this captures, adopt digital signature technology, read the unique identification of current ERP system, send together with the operation/maintenance data captured, this unique identification is a GUID, for the running environment of unique identification existing customer; After this operation/maintenance data of catching sends successfully, automatic delete step 2.3) in the buffer memory of capture-data.
Described step 3.1) reception process data packet in, first packet is stored in temporary storage area, after the storage completing operation/maintenance data, then the packet of reception is deleted from temporary storage area.
Described step 3.2) in, verification is according to step 2.4) in digital signature verify, if checking do not pass through, then abandon this receiving course and feed back abnormal information, and from temporary storage area, deleting the packet received.
The acquisition method of magnanimity operation/maintenance data in a kind of ERP system of the present invention, has the following advantages:
The acquisition method of magnanimity operation/maintenance data in a kind of ERP system that the present invention proposes, three performing steps such as the method comprises operation/maintenance data definition, operation/maintenance data is caught and sent, the reception of operation/maintenance data and storage.By application the method, define unified data acquisition form and configurable gatherer process, effectively can gather dispersion and the privately owned ERP system operation/maintenance data be deployed in intranet environment, practical, be easy to promote.
Accompanying drawing explanation
Fig. 1 is performing step figure of the present invention.
Fig. 2 is the entity structure diagram of the operation/maintenance data definition defined in the present invention.
Embodiment
Below in conjunction with the drawings and specific embodiments, the invention will be further described.
The acquisition method of magnanimity operation/maintenance data in this kind of ERP system, as shown in accompanying drawing 1, Fig. 2, its specific implementation process comprises:
1) step of operation/maintenance data definition, this step comprises:
1.1) operation/maintenance data type is defined;
1.2) operation/maintenance data version information is defined;
1.3) operation/maintenance data acquisition configuration information is defined.
In described step 1), operation/maintenance data type comprises: unique identification, numbering, title, explanation; Operation/maintenance data version information comprises: unique identification, numbering, version name, explanation; Operation/maintenance data acquisition configuration information comprises: unique identification, operation/maintenance data type identification, operation/maintenance data version identifier, operation/maintenance data form, operation/maintenance data acquisition mode.
Described operation/maintenance data form is a field description set, and this field description comprises with properties: unique identification, title, Chinese, corresponding data literary name section, data type, descriptive information.
Described operation/maintenance data acquisition mode comprises with properties: drainage pattern, whether enable increment, increased time stamp field name, corresponding data table, Procedural reflection information, wherein,
Drainage pattern is an enumerated type property, comprises two enumerated values: table schema, program schema, and table schema is stored in the scene in tables of data for the raw data gathered, and program schema is the scene needing service routine to gather;
Whether whether enabling increment is Boolean type attribute, for representing when carrying out data acquisition, filtering, only gather the change data after acquisition time last time according to the time gathered last time;
Increased time stamp field name is under the scene of table schema at drainage pattern, when enabling increment, and the title of the timestamp field in the table of corresponding source;
Procedural reflection information is under the scene of program schema at drainage pattern, for gathering the reflection recalls information of the handling procedure of operation/maintenance data.
Described corresponding data literary name section, when the drainage pattern of operation/maintenance data acquisition mode is table schema, for the mating of source literary name section.
Described step 1.3) in, wherein " acquisition process program " the DLL (dynamic link library) false code that need follow is as follows:
DataSet GetOMData(ExtractConfig config, ExecutingContext context)；
Wherein ExtractConfig is the type definition of operation/maintenance data acquisition configuration information, and ExecutingContext is that program performs context variable set, and its inside is a key-value pair set, for transmitting the variable in implementation.DataSet is the result set of image data, and its form meets the requirement of " operation/maintenance data form ".
2) the operation/maintenance data step catching and send, this step comprises:
2.1) relevant data acquisition configuration information list is loaded;
2.2) following step is performed according to the data acquisition configuration information list circulation got;
2.3) according to data acquisition configuration information, capture systems operation/maintenance data also carries out persistence buffer memory;
2.4) operation/maintenance data that this captures is sent.
Whether the scope of the operation/maintenance data that operation/maintenance data is caught and sent, can set according to " operation/maintenance data type " and gather, be defaulted as and do not gather in each ERP system environment.
On the opportunity that operation/maintenance data is caught and sent, periodic timed task can be set in each ERP system environment and trigger, or manual activation.
When loading relevant data acquisition configuration information, need to filter according to system current version.
Described step 2.3) in,
When drainage pattern is table schema, adopt plug-in processing logic, read relevant system operation data according to the corresponding data table of specifying, and form the result set of standard based on operation/maintenance data form;
When drainage pattern is program schema, according to the Procedural reflection information of specifying, load corresponding acquisition process program and perform;
Be true time when whether enabling increment, then attempt to read acquisition time last time, if read less than, then think to gather first; If read, then with this time for screening conditions, be captured in the data after this time; And gathered rear automatic record acquisition time last time at every turn;
Above-mentioned data acquisition JSON (JavaScript Object Notation) text formatting of catching describes, and adopts compressed format buffer memory.
With a GUID mark in the data of catching, for identifying this acquisition procedure.
Described step 2.4) in, when sending the operation/maintenance data that this captures, user is automatically sent by option configuration or sends after manual confirmation; And directly use step 2.3) in compressed format transmission; When sending the operation/maintenance data that this captures, adopt digital signature technology, read the unique identification of current ERP system, send together with the operation/maintenance data captured, this unique identification is a GUID, for the running environment of unique identification existing customer; After this operation/maintenance data of catching sends successfully, automatic delete step 2.3) in the buffer memory of capture-data.
In concrete ERP product user rs environment, the configurable backup whether retaining transmission data, in order to examination & verification.
3) reception of operation/maintenance data and the step of storage, this step comprises:
3.1) packet of compressed format is received;
3.2) School Affairs decompress(ion) is carried out to packet;
3.3) operation/maintenance data is stored.
Described step 3.1) reception process data packet in, first packet is stored in temporary storage area, after the storage completing operation/maintenance data, then the packet of reception is deleted from temporary storage area.
When receiving packet, repeatability verification is carried out to the packet received.Main Basis is step 2.3) the middle GUID for identifying specific acquisition procedure defined.
Described step 3.2) in, verification is according to step 2.4) in digital signature verify, if checking do not pass through, then abandon this receiving course and feed back abnormal information, and from temporary storage area, deleting the packet received.
The storage of operation/maintenance data, stores based on distributed file system technology.
Embodiment:
First be set in ERP system and have two kinds of running log data, User operation log and system exception daily record.
User operation log comprises following field: row ID, session identification, user ID, Function Identification, action identification, relate to data message, time of origin, client information, server info.
System exception log packet is containing following field: row ID, user ID, Function Identification, abnormal information, exception catching time, data context information.
In the stage one, define two kinds of operation/maintenance data types: user operation, system exception:
In the stage one, define two operation/maintenance data version informations:
In the stage one, define two operation/maintenance data acquisition configuration information:
Operation/maintenance data format information:
As from the foregoing, for user sensitive information, system configuration acquiescence is not collected.This configuration ERP product client can carry out auditing, confirming.
Operation/maintenance data acquisition mode information:
In the stage two, in the environment of certain ERP product client, its system version is V2, administrator has audited above-mentioned relevant operation/maintenance data definition information and has tested, think without sensitive information, be configured to 1:00 in morning every day, automatically catch and send related data.
At the 1:00 in morning of every day, program starts to perform automatically, have read the list of data acquisition configuration information, get Config1, Config2 two operation/maintenance data acquisition configuration by stage two correlation step.And circulation performs data capture successively, the result of catching adopts JSON form to store, and carries out data compression, forms packet.After collection, according to setting, be automatically sent on server that ERP product development business specifies.
Above-mentioned embodiment is only concrete case of the present invention; scope of patent protection of the present invention includes but not limited to above-mentioned embodiment; in any a kind of ERP system according to the invention the acquisition method of magnanimity operation/maintenance data claims and the those of ordinary skill of any described technical field to its suitable change done or replacement, all should fall into scope of patent protection of the present invention.
Claims (8)
1. the acquisition method of magnanimity operation/maintenance data in ERP system, it is characterized in that, its specific implementation process is:
1) step of operation/maintenance data definition, this step comprises:
1.1) operation/maintenance data type is defined;
1.2) operation/maintenance data version information is defined;
1.3) operation/maintenance data acquisition configuration information is defined;
2) the operation/maintenance data step catching and send, this step comprises:
2.1) relevant data acquisition configuration information list is loaded;
2.2) following step is performed according to the data acquisition configuration information list circulation got;
2.3) according to data acquisition configuration information, capture systems operation/maintenance data also carries out persistence buffer memory;
2.4) operation/maintenance data that this captures is sent;
3) reception of operation/maintenance data and the step of storage, this step comprises:
3.1) packet of compressed format is received;
3.2) School Affairs decompress(ion) is carried out to packet;
3.3) operation/maintenance data is stored.
2. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 1, it is characterized in that, in described step 1), operation/maintenance data type comprises: unique identification, numbering, title, explanation; Operation/maintenance data version information comprises: unique identification, numbering, version name, explanation; Operation/maintenance data acquisition configuration information comprises: unique identification, operation/maintenance data type identification, operation/maintenance data version identifier, operation/maintenance data form, operation/maintenance data acquisition mode.
3. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 2, it is characterized in that, described operation/maintenance data form is a field description set, and this field description comprises with properties: unique identification, title, Chinese, corresponding data literary name section, data type, descriptive information;
Described operation/maintenance data acquisition mode comprises with properties: drainage pattern, whether enable increment, increased time stamp field name, corresponding data table, Procedural reflection information, wherein,
Drainage pattern is an enumerated type property, comprises two enumerated values: table schema, program schema, and table schema is stored in the scene in tables of data for the raw data gathered, and program schema is the scene needing service routine to gather;
Whether whether enabling increment is Boolean type attribute, for representing when carrying out data acquisition, filtering, only gather the change data after acquisition time last time according to the time gathered last time;
Increased time stamp field name is under the scene of table schema at drainage pattern, when enabling increment, and the title of the timestamp field in the table of corresponding source;
Procedural reflection information is under the scene of program schema at drainage pattern, for gathering the reflection recalls information of the handling procedure of operation/maintenance data.
4. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 3, is characterized in that, described corresponding data literary name section, when the drainage pattern of operation/maintenance data acquisition mode is table schema, for the mating of source literary name section.
5. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 3, is characterized in that, described step 2.3) in,
When drainage pattern is table schema, adopt plug-in processing logic, read relevant system operation data according to the corresponding data table of specifying, and form the result set of standard based on operation/maintenance data form;
When drainage pattern is program schema, according to the Procedural reflection information of specifying, load corresponding acquisition process program and perform;
Be true time when whether enabling increment, then attempt to read acquisition time last time, if read less than, then think to gather first; If read, then with this time for screening conditions, be captured in the data after this time; And gathered rear automatic record acquisition time last time at every turn;
Above-mentioned data acquisition JSON text formatting of catching describes, and adopts compressed format buffer memory.
6. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 5, is characterized in that, described step 2.4) in, when sending the operation/maintenance data that this captures, user automatically sent by option configuration or manual confirm after send; And directly use step 2.3) in compressed format transmission; When sending the operation/maintenance data that this captures, adopt digital signature technology, read the unique identification of current ERP system, send together with the operation/maintenance data captured, this unique identification is a GUID, for the running environment of unique identification existing customer; After this operation/maintenance data of catching sends successfully, automatic delete step 2.3) in the buffer memory of capture-data.
7. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 6, it is characterized in that, described step 3.1) reception process data packet in, first packet is stored in temporary storage area, after the storage completing operation/maintenance data, then the packet of reception is deleted from temporary storage area.
8. the acquisition method of magnanimity operation/maintenance data in a kind of ERP system according to claim 6, it is characterized in that, described step 3.2) in, verification is according to step 2.4) in digital signature verify, if checking is not passed through, then abandon this receiving course and feed back abnormal information, and from temporary storage area, deleting the packet received.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510117979.5A CN104679894A (en) | 2015-03-17 | 2015-03-17 | Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510117979.5A CN104679894A (en) | 2015-03-17 | 2015-03-17 | Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104679894A true CN104679894A (en) | 2015-06-03 |
Family
ID=53314936
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510117979.5A Pending CN104679894A (en) | 2015-03-17 | 2015-03-17 | Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104679894A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105549556A (en) * | 2015-12-17 | 2016-05-04 | 东北大学 | Data collection transmission system and method for real-time monitoring of industrial process |
| CN108418787A (en) * | 2018-01-02 | 2018-08-17 | 深圳壹账通智能科技有限公司 | Acquisition method, terminal device and the medium of Enterprise Resources Plan data |
| CN110298452A (en) * | 2019-05-14 | 2019-10-01 | 国网浙江省电力有限公司嘉兴供电公司 | A kind of power grid active O&M method for early warning based on big data |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996854A (en) * | 2006-12-22 | 2007-07-11 | 中国建设银行股份有限公司 | Integrated processing system and method for the data exchange between different application systems |
| CN101008952A (en) * | 2007-01-30 | 2007-08-01 | 华为技术有限公司 | Method and device for generating persistence layer |
| CN101018150A (en) * | 2006-02-09 | 2007-08-15 | 中兴通讯股份有限公司 | A collection method and system of the telecom device performance data |
| CN102542007A (en) * | 2011-12-13 | 2012-07-04 | 中国电子科技集团公司第十五研究所 | Method and system for synchronization of relational databases |
-
2015
- 2015-03-17 CN CN201510117979.5A patent/CN104679894A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101018150A (en) * | 2006-02-09 | 2007-08-15 | 中兴通讯股份有限公司 | A collection method and system of the telecom device performance data |
| CN1996854A (en) * | 2006-12-22 | 2007-07-11 | 中国建设银行股份有限公司 | Integrated processing system and method for the data exchange between different application systems |
| CN101008952A (en) * | 2007-01-30 | 2007-08-01 | 华为技术有限公司 | Method and device for generating persistence layer |
| CN102542007A (en) * | 2011-12-13 | 2012-07-04 | 中国电子科技集团公司第十五研究所 | Method and system for synchronization of relational databases |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105549556A (en) * | 2015-12-17 | 2016-05-04 | 东北大学 | Data collection transmission system and method for real-time monitoring of industrial process |
| CN105549556B (en) * | 2015-12-17 | 2018-06-26 | 东北大学 | A kind of data collection and transfering system and method for industrial process real time monitoring |
| CN108418787A (en) * | 2018-01-02 | 2018-08-17 | 深圳壹账通智能科技有限公司 | Acquisition method, terminal device and the medium of Enterprise Resources Plan data |
| CN110298452A (en) * | 2019-05-14 | 2019-10-01 | 国网浙江省电力有限公司嘉兴供电公司 | A kind of power grid active O&M method for early warning based on big data |
| CN110298452B (en) * | 2019-05-14 | 2022-07-22 | 国网浙江省电力有限公司嘉兴供电公司 | Power grid active operation and maintenance early warning method based on big data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109542733B (en) | High-reliability real-time log collection and visual retrieval method | |
| CN103685150B (en) | The method and apparatus of upload file | |
| US20100088197A1 (en) | Systems and methods for generating remote system inventory capable of differential update reports | |
| CN102780726A (en) | Log analysis method and log analysis system based on WEB platform | |
| CN107977473B (en) | Logback-based distributed system log retrieval method and system | |
| US20180159884A1 (en) | Dtat stream surveillance, intelligence and reporting | |
| CN108737549A (en) | A kind of log analysis method and device of big data quantity | |
| CN102209118A (en) | Distributed mass data gathering method | |
| CN105589782A (en) | User behavior collection method based on browser | |
| CN110209518A (en) | A kind of multi-data source daily record data, which is concentrated, collects storage method and device | |
| CN105577528A (en) | Wechat official account data collection method and device based on virtual machine | |
| CN105306261A (en) | Method, device and system for collecting logs | |
| CN104679894A (en) | Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system | |
| CN112257032B (en) | Method and system for determining APP responsibility main body | |
| US10915510B2 (en) | Method and apparatus of collecting and reporting database application incompatibilities | |
| CN111339471A (en) | Method and device for dynamically loading page buried point data | |
| CN113778810A (en) | Log collection method, device and system | |
| CN102521339A (en) | System and method for dynamic access of data sources | |
| CN109375923B (en) | Method and device for processing change data, storage medium, processor and server | |
| CN111367686A (en) | Service interface calling method and device, computer equipment and storage medium | |
| CN105007278A (en) | Automatic real-time acquisition system and acquisition method for network safety log | |
| CN110716938A (en) | Data aggregation method and device, storage medium and electronic device | |
| CN112685370B (en) | Log collection method, device, equipment and medium | |
| JP2016014980A (en) | Log acquisition extraction system | |
| JP6008406B2 (en) | Log management method, log management system, log management apparatus, and log management program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150603 |