CN117527896A - Method and system for interfacing multi-system data with third party electronic files - Google Patents
Method and system for interfacing multi-system data with third party electronic files Download PDFInfo
- Publication number
- CN117527896A CN117527896A CN202311468716.XA CN202311468716A CN117527896A CN 117527896 A CN117527896 A CN 117527896A CN 202311468716 A CN202311468716 A CN 202311468716A CN 117527896 A CN117527896 A CN 117527896A
- Authority
- CN
- China
- Prior art keywords
- data
- configuration
- field
- service
- information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000013506 data mapping Methods 0.000 claims abstract description 16
- 238000007726 management method Methods 0.000 claims abstract description 14
- 238000012545 processing Methods 0.000 claims description 22
- 238000013507 mapping Methods 0.000 claims description 18
- 230000001419 dependent effect Effects 0.000 claims description 15
- 238000003032 molecular docking Methods 0.000 claims description 13
- 238000003780 insertion Methods 0.000 claims description 6
- 230000037431 insertion Effects 0.000 claims description 6
- 238000001914 filtration Methods 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000012795 verification Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 abstract description 16
- 238000011161 development Methods 0.000 abstract description 12
- 230000006870 function Effects 0.000 abstract description 11
- 210000001503 joint Anatomy 0.000 abstract description 10
- 230000010354 integration Effects 0.000 abstract description 8
- 230000005540 biological transmission Effects 0.000 abstract description 4
- 238000004891 communication Methods 0.000 abstract description 2
- 230000001360 synchronised effect Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 3
- 230000004069 differentiation Effects 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a system for interfacing multi-system data with a third party electronic archive. Wherein the data source configuration: a data source that needs to be docked, such as a database of various systems within an enterprise, is first determined. According to the method, different data sources are abutted, data are integrated and integrated into a traditional function, and a third-party electronic file system is intensively abutted, so that unified management and sharing of the data are realized, development among non-communication modules is avoided, and learning cost is reduced. Each module is responsible for different data sources, and data synchronization and transmission are completed by setting a data mapping rule, a service bill sequence dependence sequence and an interface butt joint mode, so that service chain integrity is ensured. By the method, the data butt joint process can be simplified, and the efficiency and accuracy of data integration are improved.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method and a system for butting third-party electronic files by multi-system data.
Background
With the rapid development of information technology, more and more organizations and companies use electronic files for business and information management. However, in the enterprise informatization process, different information systems are built step by step, new and old information systems exist, development platforms of the systems are inconsistent, each system is respectively connected in a butt joint mode, development cost is high, difficulty is high, each system needs to be debugged when being connected in a butt joint mode, and operation and maintenance cost is high.
The traditional multi-system docking process integrates the systems through interfaces, and a plurality of systems are independently docked, so that the steps are complicated and multiple joint debugging is needed. Because different systems are developed based on different platforms, the same interface is docked, languages used by the systems are inconsistent, development teams are inconsistent, the level is high and low, and the integration cost is high. The method of the patent realizes unified management and sharing of data by using a single module to dock data sources of different systems and setting a data mapping rule and an interface docking mode. In this way, the data docking process becomes simplified and the possibility of human error is reduced, reducing the risk of inconsistent development teams.
Disclosure of Invention
Therefore, in order to reduce the cost of the enterprise information system for interfacing with the electronic file system, the problems of various enterprise information systems and weak association relationship between systems are solved. Meanwhile, in order to improve the development efficiency of developers and the code multiplexing rate, the invention provides a method and a system for butting third-party electronic files by multi-system data. Each module is responsible for different data sources, and data synchronization and transmission are completed by setting a data mapping rule, a service bill sequence dependence sequence and an interface butt joint mode, so that service chain integrity is ensured. By the method, the data butt joint process can be simplified, and the efficiency and accuracy of data integration are improved.
Based on the above object, in a first aspect, the present invention provides a system for interfacing multi-system data to third party electronic files, where the system includes a data source configuration module, a data mapping configuration module, an interface configuration module, a service type configuration module, a service flow configuration module, a service bill dependent information configuration module, and a data synchronization module;
the data source configuration module is used for configuring system names of different systems, and database connection information is used for later configuration function use;
the data mapping rule module is used for setting data mapping rules depending on a data source, mapping fields in a table in a system into corresponding electronic file system fields, defining conditions for acquiring a data set, and configuring a write-back field and a time stamp field;
the interface configuration module comprises interface address configuration, interface parameter configuration and data processing after interface calling;
the service type configuration module is used for defining service types according to the electronic file management requirements and the electronic file interface requirements, and whether the configuration requirement fields need to be filled or not and whether updating is needed or not;
the business bill dependent information configuration module is used for depending on the business type, defining the dependent relation of the business type and configuring whether field data are updated according to the filling of the type configuration field;
the data synchronization module is used for periodically inquiring the information of the data sources of each system, updating the field data to be updated according to the field 'whether update is allowed' in the service type configuration, and ensuring the synchronization of the data.
As a further scheme of the invention, the interface configuration module is used for calling the interface at regular time, reading the configured information, and after the interface is called, the analysis of the return value also supports the processing in the configuration mode and supports the update state and the processing time.
As a further scheme of the invention, in the service type configuration module, the necessary filling field is in the data acquired by the subsequent mapping rule for necessary filling verification.
As a further scheme of the invention, the business bill dependency information configuration module is provided with business bills with a sequence dependency relationship, and when the electronic file of the business bill is inquired through the business flow configuration, the file information of the previous business can be automatically carried out according to the configuration, so that the inquiry is convenient.
In a second aspect, the present invention provides a method for interfacing multi-system data to a third party electronic archive, the method comprising the steps of:
a101 service type configuration, according to the electronic archive management requirement, relying on the management scope, combing the butted system according to the service, classifying the service, and determining the service type number and the service type name.
A102 service field configuration, configuring different service field configurations based on document service types according to electronic file requirements. Each configuration may be configured to expose a different interface according to a different type. Basic configuration information: table name, field type, field length, whether padding is necessary, whether updates are allowed. And generating a corresponding service data table according to the type.
A103 is a field configured based on the A102 service field, and judges whether the value of the field allows updating according to the requirement of the electronic file interface. Subsequent data updates, the configuration is read, and the field data is selectively updated based on whether the field allows the configuration to be updated.
A104, whether or not to fill the configuration field, and whether or not to service necessity field based on the fields of A102. The filling is selected according to the requirement or not. The field must be filled, the mapping field must be configured in A108, and a check is made in A114, and if the field must be filled, but the acquired data is empty, prompt A115 is made.
A105 data source definition, based on multi-system docking, according to system name, compiling data source number, name, database type, user name and password, whether to start. Facilitating subsequent differentiation.
A106, configuring table information, namely configuring the names of tables in the database and the filtering conditions of the data based on the definition of the data source.
A107 field information configuration, namely, based on the field information of the A106 acquisition table, configuring the name and the type of the field, and identifying the fields such as ID, number, name, timestamp, unit and the like by special symbols.
And A108, mapping and configuring the field in A107 to correspond to the table and service field of A102, and establishing the association mapping relation between the third party system and the system. For subsequent fetching.
A109 business document dependent information configuration. And (3) referring to the information in the A104, configuring the order of the order dependence of the bills in the same service flow. For example, document a is to rely on document B. Then the configuration sequence is document B1 and document a 2. Settlement depends on the contract. The method is convenient for subsequent processing under the same service flow, and the problem of repeated uploading is reduced.
As a further aspect of the invention, the data is updated into the business data table at daily timing or manually, first A110 reads the configuration in the data source definition, determines whether the data source is A111 enabled, and if not, skips continuing to loop through to read the next enabled data source. If the data source is enabled, the database is connected, and if it fails, prompt A113 is returned. After the database is successfully connected, the configuration information under the data source is analyzed, and A114 is realized. And reading the table information configuration, the field information configuration and the field mapping configuration under the data source. And judging whether the field is filled or not according to the configuration information, and whether the value pulled by the field is filled or not. If there is a problem, a prompt message A115 is returned, and if normal, the data is obtained to the intermediate table A116.
As a further scheme of the invention, in the intermediate table of the A116 node, data are processed, and whether the data are newly added or updated is judged. If the primary key and the timestamp field of the intermediate table are consistent with those in the service data table, no processing is needed, and if the intermediate table and the timestamp field are not present in the service data table, direct insertion is performed. If the primary key and the timestamp field are consistent, and the timestamps are inconsistent, updating the field allowing updating of the configuration according to the configuration information A103.
As a further aspect of the present invention, after acquiring data according to the configuration, the data is updated to the service data node a120. And simultaneously, the data processing log A121 is synchronized, and the insertion of data and the update operation are recorded. And the later tracing is convenient.
As a further scheme of the invention, after the A120 acquires the service data, the button is supported to manually call the electronic file interface, and the timing call of the electronic file interface is also supported to synchronize the electronic file information; a121 is interface address information and interface address. The uploading interface can be configured, the interface is modified, and parameters such as an address, an interface key and the like of the interface are deleted; a122 interface parameter configuration, by means of A108, field access information is configured in A122, and the parameter entering format required by the interface is spliced.
As a further aspect of the invention, the interface is invoked by data timing or manually in A120, and the interface configuration information is read through A123. Firstly, judging whether the bill state of the service data in A120 is uploaded, if yes, skipping, if no, analyzing the selected data into a format required by an interface by A125, reading configuration information from A122, acquiring the data in A120, and assembling parameters according to the format of A122. And A125 calls an interface, reads the business dependency relationship in A109 when the interface is called, calls the interface according to the sequence of the dependency relationship, then executes the bill of the interface, transmits the electronic file number of the dependent bill, acquires a return value A126, updates to A119 in the intermediate table state field according to the return value information, updates the time stamp, finally updates the state to the business data, and finishes uploading the electronic file.
In yet another aspect of the present invention, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, performs any of the methods of interfacing multiple system data according to the present invention to a third party electronic archive.
In yet another aspect of the present invention, there is provided a computer readable storage medium storing computer program instructions that when executed implement a method of interfacing multi-system data according to any one of the above to third party electronic files.
Compared with the prior art, the method and the system for interfacing the multi-system data with the third-party electronic file have the following beneficial effects:
according to the method for butting the third-party electronic file by the multi-system data, disclosed by the invention, the data are integrated and integrated in the traditional function by butting different data sources, and the third-party electronic file system is intensively butted, so that unified management and sharing of the data are realized, development among non-communication modules is avoided, and the learning cost is reduced. Each module is responsible for different data sources, and data synchronization and transmission are completed by setting a data mapping rule, a service bill sequence dependence sequence and an interface butt joint mode, so that service chain integrity is ensured. By the method, the data butt joint process can be simplified, and the efficiency and accuracy of data integration are improved.
The method of the invention has the characteristics of flexibility and expandability, and can ensure the consistency and the accuracy of data by setting a data mapping rule for an independent data source of each system, and acquire fields of different data sources into a unified function. And the docking with a third-party electronic file system is facilitated.
Meanwhile, the method also supports timing data synchronization and ensures the accuracy of data. Through configuration function, the data of each data source can be conveniently searched and managed, and the integration and utilization efficiency of the data is improved.
In summary, the patent has the greatest advantages of reducing development among a plurality of systems, reducing learning cost, simplifying the data docking process among the systems and improving the efficiency and accuracy of data integration.
These and other aspects of the present application will be more readily apparent from the following description of the embodiments. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are necessary for the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention and that other embodiments may be obtained according to these drawings without inventive effort for a person skilled in the art.
In the figure:
FIG. 1 is a flowchart of a method for interfacing multi-system data to third party electronic files according to an embodiment of the present invention.
Detailed Description
The present application will be further described with reference to the drawings and detailed description, which should be understood that, on the premise of no conflict, the following embodiments or technical features may be arbitrarily combined to form new embodiments.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention will be described in further detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
It should be noted that, in the embodiments of the present invention, all the expressions "first" and "second" are used to distinguish two non-identical entities with the same name or non-identical parameters, and it is noted that the "first" and "second" are only used for convenience of expression, and should not be construed as limiting the embodiments of the present invention. Furthermore, the terms "comprise" and "have," and any variations thereof, are intended to cover a non-exclusive inclusion, such as a process, method, system, article, or other step or unit that comprises a list of steps or units.
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The flow diagrams depicted in the figures are merely illustrative and not necessarily all of the elements and operations/steps are included or performed in the order described. For example, some operations/steps may be further divided, combined, or partially combined, so that the order of actual execution may be changed according to actual situations.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
The traditional multi-system docking process integrates the systems through interfaces, and a plurality of systems are independently docked, so that the steps are complicated and multiple joint debugging is needed. Because different systems are developed based on different platforms, the same interface is docked, languages used by the systems are inconsistent, development teams are inconsistent, the level is high and low, and the integration cost is high. The method of the patent realizes unified management and sharing of data by using a single module to dock data sources of different systems and setting a data mapping rule and an interface docking mode. In this way, the data docking process becomes simplified and the possibility of human error is reduced, reducing the risk of inconsistent development teams.
In order to reduce the cost of the enterprise information system for docking the electronic file system, the problem of weak association relationship among the systems due to various enterprise information systems is solved. Meanwhile, in order to improve the development efficiency of developers and the code multiplexing rate, the invention provides a method and a system for butting third-party electronic files by multi-system data. Each module is responsible for different data sources, and data synchronization and transmission are completed by setting a data mapping rule, a service bill sequence dependence sequence and an interface butt joint mode, so that service chain integrity is ensured. By the method, the data butt joint process can be simplified, and the efficiency and accuracy of data integration are improved.
Referring to fig. 1, the invention provides a system for interfacing multi-system data with third party electronic files, which comprises a data source configuration module, a data mapping configuration module, an interface configuration module, a service type configuration module, a service flow configuration module, a service bill dependent information configuration module and a data synchronization module.
The data source configuration module is used for configuring system names of different systems, and database connection information is used for later configuration function use;
the data mapping rule module is used for setting data mapping rules depending on a data source, mapping fields in a table in a system into corresponding electronic file system fields, defining conditions for acquiring a data set, and configuring a write-back field and a time stamp field;
the interface configuration module comprises interface address configuration, interface parameter configuration and data processing after interface calling; the interface configuration module is used for calling the interface at regular time, reading the configured information, and after the interface is called, analyzing the return value also supports processing in a configuration mode and supports updating state and processing time.
The service type configuration module is used for defining service types according to the electronic file management requirements and the electronic file interface requirements, and whether the configuration requirement fields need to be filled or not and whether updating is needed or not; and in the service type configuration module, the necessary filling field is used for performing necessary filling check in the data acquired by the subsequent mapping rule.
The business bill dependent information configuration module is used for depending on the business type, defining the dependent relation of the business type and configuring whether field data are updated according to the filling of the type configuration field; the business bill dependency information configuration module has business bills with a sequence dependency relationship, and can automatically bring out the file information of the previous business according to the configuration when the electronic file of the business bill is queried through the configuration of the business flow, thereby facilitating the query.
The data synchronization module is used for periodically inquiring the information of the data sources of each system, updating the field data to be updated according to the field 'whether update is allowed' in the service type configuration, and ensuring the synchronization of the data.
Referring to fig. 1, the method for interfacing multi-system data with a third party electronic archive according to the present invention further includes the following steps:
a101 service type configuration, according to the electronic archive management requirement, relying on the management scope, combing the butted system according to the service, classifying the service, and determining the service type number and the service type name.
A102 service field configuration, configuring different service field configurations based on document service types according to electronic file requirements. Each configuration may be configured to expose a different interface according to a different type. Basic configuration information: table name, field type, field length, whether padding is necessary, whether updates are allowed. And generating a corresponding service data table according to the type.
A103 is a field configured based on the A102 service field, and judges whether the value of the field allows updating according to the requirement of the electronic file interface. Subsequent data updates, the configuration is read, and the field data is selectively updated based on whether the field allows the configuration to be updated.
A104, whether or not to fill the configuration field, and whether or not to service necessity field based on the fields of A102. The filling is selected according to the requirement or not. The field must be filled, the mapping field must be configured in A108, and a check is made in A114, and if the field must be filled, but the acquired data is empty, prompt A115 is made.
A105 data source definition, based on multi-system docking, according to system name, compiling data source number, name, database type, user name and password, whether to start. Facilitating subsequent differentiation.
A106, configuring table information, namely configuring the names of tables in the database and the filtering conditions of the data based on the definition of the data source.
A107 field information configuration, namely, based on the field information of the A106 acquisition table, configuring the name and the type of the field, and identifying the fields such as ID, number, name, timestamp, unit and the like by special symbols.
And A108, mapping and configuring the field in A107 to correspond to the table and service field of A102, and establishing the association mapping relation between the third party system and the system. For subsequent fetching.
A109 business document dependent information configuration. And (3) referring to the information in the A104, configuring the order of the order dependence of the bills in the same service flow. For example, document a is to rely on document B. Then the configuration sequence is document B1 and document a 2. Settlement depends on the contract. The method is convenient for subsequent processing under the same service flow, and the problem of repeated uploading is reduced.
Wherein, the data is updated to the business data table periodically or manually every day, firstly, the A110 reads the configuration in the definition of the data source, judges whether the data source is enabled to the A111, and if not, the data source is skipped to continue to circularly read the next enabled data source. If the data source is enabled, the database is connected, and if it fails, prompt A113 is returned. After the database is successfully connected, the configuration information under the data source is analyzed, and A114 is realized. And reading the table information configuration, the field information configuration and the field mapping configuration under the data source. And judging whether the field is filled or not according to the configuration information, and whether the value pulled by the field is filled or not. If there is a problem, a prompt message A115 is returned, and if normal, the data is obtained to the intermediate table A116.
In the intermediate table of the A116 node, the data is processed to judge whether the data is newly added or updated. If the primary key and the timestamp field of the intermediate table are consistent with those in the service data table, no processing is needed, and if the intermediate table and the timestamp field are not present in the service data table, direct insertion is performed. If the primary key and the timestamp field are consistent, and the timestamps are inconsistent, updating the field allowing updating of the configuration according to the configuration information A103.
After acquiring the data according to the configuration, the data is updated to the service data node a120. And simultaneously, the data processing log A121 is synchronized, and the insertion of data and the update operation are recorded. And the later tracing is convenient.
A120, after obtaining the service data, supporting the manual calling of the electronic file interface by the button, and supporting the timed calling of the electronic file interface and synchronizing the electronic file information; a121 is interface address information and interface address. The uploading interface can be configured, the interface is modified, and parameters such as an address, an interface key and the like of the interface are deleted; a122 interface parameter configuration, by means of A108, field access information is configured in A122, and the parameter entering format required by the interface is spliced.
The interface is called by the data timing or manual in A120, and the interface configuration information is read through A123. Firstly, judging whether the bill state of the service data in A120 is uploaded, if yes, skipping, if no, analyzing the selected data into a format required by an interface by A125, reading configuration information from A122, acquiring the data in A120, and assembling parameters according to the format of A122. And A125 calls an interface, reads the business dependency relationship in A109 when the interface is called, calls the interface according to the sequence of the dependency relationship, then executes the bill of the interface, transmits the electronic file number of the dependent bill, acquires a return value A126, updates to A119 in the intermediate table state field according to the return value information, updates the time stamp, finally updates the state to the business data, and finishes uploading the electronic file.
The configuration interface provides a copying function, supports the copying of the same type of configuration and carries out quick adjustment.
If the electronic file needs to change, only the field access needs to be modified, the configuration form is adjusted, and the other interfaces do not need to be adjusted. In addition, the configuration function data of the system is provided with relevant authorities, and the original data is accessed by a manager with specific authorities, so that the safety of the data is ensured. The system can ensure the configuration reliability and the real-time performance.
It is noted that the above-described figures are only schematic illustrations of processes involved in a method according to an exemplary embodiment of the invention, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
It should be understood that although described in a certain order, the steps are not necessarily performed sequentially in the order described. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, some steps of the present embodiment may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily sequential, but may be performed alternately or alternately with at least a part of the steps or stages in other steps or other steps.
In a third aspect of the embodiments of the present invention, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, implements the method of any of the embodiments described above.
A processor and a memory are included in the computer device, and may further include: an input system and an output system. The processor, memory, input system, and output system may be connected by a bus or other means, the input system may receive input numeric or character information, and generate signal inputs related to migration of the multi-system data interfacing third party electronic file. The output system may include a display device such as a display screen.
The memory is used as a non-volatile computer readable storage medium, and can be used for storing non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions/modules corresponding to the method for interfacing multi-system data to third-party electronic files in the embodiments of the present application. The memory may include a memory program area and a memory data area, wherein the memory program area may store an operating system, at least one application program required for a function; the storage data area may store data created by the use of the method of interfacing multi-system data to third party electronic files, and the like. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the local module through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The processor may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor is typically used to control the overall operation of the computer device. In this embodiment, the processor is configured to execute the program code stored in the memory or process the data. The processors of the multiple computer devices of the computer device of the present embodiment execute various functional applications and data processing of the server by running nonvolatile software programs, instructions and modules stored in the memory, that is, the steps of the method for implementing the multi-system data docking third party electronic file of the method embodiment described above.
It should be appreciated that all of the embodiments, features and advantages set forth above for the method of interfacing a third party electronic archive in accordance with the multi-system data of the present invention apply equally to the storage medium and the third party electronic archive in accordance with the multi-system data of the present invention without conflict.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
Finally, it should be noted that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of example, and not limitation, RAM may be available in a variety of forms such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with the following components designed to perform the functions herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP and/or any other such configuration.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items. The foregoing embodiment of the present invention has been disclosed with reference to the number of embodiments for the purpose of description only, and does not represent the advantages or disadvantages of the embodiments.
Those of ordinary skill in the art will appreciate that: the above discussion of any embodiment is merely exemplary and is not intended to imply that the scope of the disclosure of embodiments of the invention, including the claims, is limited to such examples; combinations of features of the above embodiments or in different embodiments are also possible within the idea of an embodiment of the invention, and many other variations of the different aspects of the embodiments of the invention as described above exist, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. of the embodiments should be included in the protection scope of the embodiments of the present invention.
Claims (10)
1. The system for butting the multi-system data with the third-party electronic files is characterized by comprising a data source configuration module, a data mapping configuration module, an interface configuration module, a service type configuration module, a service flow configuration module, a service bill dependent information configuration module and a data synchronization module;
the data source configuration module is used for configuring system names of different systems, and database connection information is used for later configuration function use;
the data mapping rule module is used for setting data mapping rules depending on a data source, mapping fields in a table in a system into corresponding electronic file system fields, defining conditions for acquiring a data set, and configuring a write-back field and a time stamp field;
the interface configuration module comprises interface address configuration, interface parameter configuration and data processing after interface calling;
the service type configuration module is used for defining service types according to the electronic file management requirements and the electronic file interface requirements, and whether the configuration requirement fields need to be filled or not and whether updating is needed or not;
the business bill dependent information configuration module is used for depending on the business type, defining the dependent relation of the business type and configuring whether field data are updated according to the filling of the type configuration field;
the data synchronization module is used for periodically inquiring information of data sources of each system and updating field data to be updated according to corresponding fields in service type configuration.
2. The method for interfacing multiple system data to a third party electronic archive of claim 1 wherein the interface configuration module is configured to read the configured information by invoking the interface at regular intervals, and after the interface is invoked, the analysis of the return value also supports processing by configuration, supporting update status and processing time.
3. The method for interfacing multi-system data to third party electronic files according to claim 1, wherein the mandatory field in the service type configuration module is used for mandatory verification in the data acquired by the subsequent mapping rule.
4. The method for interfacing multi-system data with third party electronic files according to claim 1, wherein the business bill dependency information configuration module has business bills with dependency relationships, and when the electronic files of the business bills are queried through business flow configuration, file information of previous business can be automatically carried out according to the configuration.
5. A method of interfacing a third party electronic archive based on multi-system data as claimed in any one of claims 1 to 4, the method being performed by a system for interfacing a third party electronic archive, the method comprising:
step 1) service type configuration, namely combing the butted systems according to services according to the electronic file management requirements and relying on a management range, classifying the services, and determining service type numbers and service type names;
step 2) configuring service fields, namely configuring different service field configurations based on document service types according to electronic file requirements; each configuration may be configured to expose a different interface according to a different type; basic configuration information: table name, field type, field length, whether filling is necessary, whether updating is allowed; meanwhile, a corresponding service data table is generated according to the type;
step 3) based on the field configured by the service field in step 2), judging whether the value of the field is allowed to be updated according to the requirement of the electronic file interface;
step 4) determining whether the configuration field is necessary to be filled and whether the service is necessary based on the field of step 2); selecting to be filled or not to be filled according to the requirement; configuring mapping fields for the field to be filled, checking, and returning prompt information if the fields are to be filled but the acquired data are empty;
step 5) defining the data source, compiling a data source number, a name, a database type, a user name and a password according to the system name based on multi-system docking, and judging whether to start;
step 6) configuring table information, configuring the names of tables in a database and the filtering conditions of the data based on the definition of data sources;
step 7) configuring field information, and based on the field information of the table obtained in the step 6), configuring the name and the type of the field, and marking the ID, the number, the name, the timestamp and the unit field by special symbols;
step 8) carrying out field mapping configuration, namely, corresponding the fields in the step 7) to the table and the service fields in the step 2), and establishing an association mapping relation between a third party system and the system;
step 9) carrying out business bill dependent information configuration: and (3) referring to the information in the step (4), configuring the order of the order dependence of the bill in the same service flow.
6. The system for interfacing multisystem data to third party electronic files of claim 5, wherein the daily timed or manual update of data to a business data table comprises the steps of:
step 10) reading configuration in the definition of the data source, and judging whether the data source is started or not;
step 11) if not enabled, skipping the continuing loop to read the next enabled data source;
step 12) if the data source is enabled, connecting the database;
step 13) if the step fails, returning a prompt message step;
step 14) after the database is successfully connected, analyzing the configuration information under the data source;
step 15) reading the table information configuration, the field information configuration and the field mapping configuration under the data source; judging whether the field is necessary to be filled and whether the value pulled by the field is necessary to be filled according to the configuration information;
step 16) if errors occur, a prompt message is returned, and if the errors are normal, the data are acquired to the intermediate table.
7. The system for interfacing multisystem data to third party electronic files of claim 6 wherein in step 16) the data is processed in the node intermediate table and whether the data is newly added or updated is determined;
if the main key and the timestamp field of the intermediate table are consistent with those in the service data table, no processing is needed, and if the intermediate table and the timestamp field do not exist in the service data table, direct insertion is performed;
if the primary key and the timestamp field are consistent, and the timestamps are inconsistent, updating the field which is allowed to be updated according to the configuration information.
8. The system for interfacing multisystem data to third party electronic files according to claim 5, wherein after data is acquired according to the configuration, the data is updated to the service data node while synchronizing the data processing log, the insertion of the data, and the update operation is recorded.
9. The system for interfacing multiple system data to a third party electronic file of claim 5 wherein after the service data is obtained, the support button manually invokes the electronic file interface and also supports timed invocation of the electronic file interface to synchronize electronic file information.
10. The system for interfacing multi-system data to third party electronic files of claim 5, further comprising:
reading the business dependency relationship in the step 9) when the interface is called, calling the interface according to the sequence of the dependency relationship, then executing the bill of the interface, transmitting the electronic file number of the dependent bill, acquiring a return value, updating the return value into an intermediate table state field and updating a time stamp according to the return value information, and finally updating the state into business data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311468716.XA CN117527896A (en) | 2023-11-06 | 2023-11-06 | Method and system for interfacing multi-system data with third party electronic files |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311468716.XA CN117527896A (en) | 2023-11-06 | 2023-11-06 | Method and system for interfacing multi-system data with third party electronic files |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117527896A true CN117527896A (en) | 2024-02-06 |
Family
ID=89761819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311468716.XA Pending CN117527896A (en) | 2023-11-06 | 2023-11-06 | Method and system for interfacing multi-system data with third party electronic files |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117527896A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117875299A (en) * | 2024-03-13 | 2024-04-12 | 南京智握信息技术有限公司 | Electronic file integrated processing method and system |
-
2023
- 2023-11-06 CN CN202311468716.XA patent/CN117527896A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117875299A (en) * | 2024-03-13 | 2024-04-12 | 南京智握信息技术有限公司 | Electronic file integrated processing method and system |
| CN117875299B (en) * | 2024-03-13 | 2024-05-24 | 南京智握信息技术有限公司 | Electronic file integrated processing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10095499B2 (en) | Optimization for multi-project package manager | |
| CN109885311B (en) | Application program generation method and device | |
| CN111259643B (en) | Method and equipment for generating graphic report | |
| CN117527896A (en) | Method and system for interfacing multi-system data with third party electronic files | |
| CN109885299B (en) | Template processing method, device, computer equipment and storage medium in model development | |
| CN111767704B (en) | Excel form template generation method and device | |
| CN111309593A (en) | JSON interface verification method, device and equipment and computer readable storage medium | |
| CN111818175B (en) | Enterprise service bus configuration file generation method, device, equipment and storage medium | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| CN111857777A (en) | System updating method and device based on double-core intelligent electric meter and computer equipment | |
| CN110198327B (en) | Data transmission method and related equipment | |
| CN111078274A (en) | Code development method and device, electronic equipment and computer storage medium | |
| US9411618B2 (en) | Metadata-based class loading using a content repository | |
| CN112306533A (en) | Front-end framework automatic conversion method and device, computer equipment and storage medium | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| CN115599359A (en) | Code generation method, device, equipment and medium | |
| CN115220697A (en) | API development management method, device, vehicle and storage medium | |
| CN111078213B (en) | Code generation method and code generation device | |
| CN114510262A (en) | Interface request parameter verification method and device | |
| CN113515303B (en) | Project transformation method, device and equipment | |
| CN113468143A (en) | Data migration method, system, computing device and storage medium | |
| CN112395339A (en) | Method and device for checking data access between systems, computer equipment and storage medium | |
| CN114819631A (en) | Multitask visualization method and device, computer equipment and storage medium | |
| CN115495527A (en) | Data synchronization management system and method | |
| CN105302586A (en) | Software upgrade processing method and device, terminal and server |
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 |