CN113407611B - Data integration distribution platform and system - Google Patents

Data integration distribution platform and system Download PDF

Info

Publication number
CN113407611B
CN113407611B CN202110803028.9A CN202110803028A CN113407611B CN 113407611 B CN113407611 B CN 113407611B CN 202110803028 A CN202110803028 A CN 202110803028A CN 113407611 B CN113407611 B CN 113407611B
Authority
CN
China
Prior art keywords
data
service unit
json format
database
unit
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
Application number
CN202110803028.9A
Other languages
Chinese (zh)
Other versions
CN113407611A (en
Inventor
罗慧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to CN202110803028.9A priority Critical patent/CN113407611B/en
Publication of CN113407611A publication Critical patent/CN113407611A/en
Application granted granted Critical
Publication of CN113407611B publication Critical patent/CN113407611B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • G06F16/254—Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
    • 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/21—Design, administration or maintenance of databases
    • G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
    • 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
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/547—Messaging middleware
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/548—Queue
    • 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)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention discloses a data integration distribution platform, which comprises a data interface module, a data acquisition tool, a data processing module and a database; the data interface module is mounted on the data integration platform, and the data acquisition tool is embedded in the data integration platform; the data interface module is used for collecting first data of an external application system; the data acquisition tool is used for extracting second data of the database; the data processing module is used for processing the first data and the second data and/or providing data service for the external application system through the data interface module; the database is also used for storing the processed first data. The invention can support various data interfaces, so that the platform can configure, manage and monitor the data interfaces according to service requirements, thereby rapidly realizing data interaction with an external application system; the data interface module is arranged in a mounting mode, and can be newly added and deleted on the premise of not changing the main frame of the platform.

Description

Data integration distribution platform and system
Technical Field
The invention belongs to the technical field of data service, and particularly relates to a data integration distribution platform and system.
Background
Along with the rapid development of information technology, each industry is dedicated to informatization construction, a large number of application information systems are built based on different business requirements, rapid development of each industry is effectively promoted, a large number of information islands are brought, and isomerization and complexity of each application information system also bring more serious challenges to information management of enterprises.
In order to realize information intercommunication and data sharing among information systems and break information islands, the prior art solves the problem of data sharing among information systems by carrying out interface transformation on the systems needing information intercommunication, but related application systems need to be transformed in the way that the data sharing among the information systems can be solved, if a plurality of systems are involved, the transformation of system interfaces becomes extremely complex, and the coupling degree among the systems is increased; in addition, the method can only meet the sharing requirement of specific data among systems, and has poor expandability and low flexibility.
Disclosure of Invention
The invention aims to provide a modular data display platform and system, which are used for solving at least one technical problem existing in the prior art.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
in a first aspect, the present invention provides a data integration and distribution platform, including a data interface module, a data acquisition tool, a data processing module, and a database;
the data interface module is mounted on the data integration platform, and the data acquisition tool is embedded in the data integration platform;
the data interface module is used for collecting first data of an external application system;
the data acquisition tool is used for extracting second data of the database;
the data processing module is used for processing the first data and the second data and/or providing data service for the external application system through the data interface module;
the database is also used for storing the processed first data.
In one possible design, the data processing module includes a message queue server, a message service unit, a gateway service unit, and a core service unit;
the data interface module sends the collected first data to the core service unit through the message queue server and the message service unit in sequence; or the core business service unit is sent to the gateway service unit;
the message queue server is used for receiving the first data and sending the first data to the message service unit based on a queue mechanism;
the message service unit is used for processing the first data according to the subscription message of the first data and forwarding the first data to the core business service unit;
the gateway service unit is used for receiving the first data, processing the first data and forwarding the first data to the core service unit;
the core service unit is used for carrying out secondary processing on the received first data, returning the second data to the message queue server and storing the second data into the database.
In one possible design, the data interface module includes an MQ data interface unit, an HTTP data interface unit, and a DDS data interface unit; and the data processing module performs data interaction with the external application system through the MQ data interface unit, the HTTP data interface unit and/or the DDS data interface unit.
In one possible design, the data processing module is specifically configured to, when the first data is collected by the MQ data interface unit:
converting the first data into first JSON format data and sending the first JSON format data to the message queue server;
a first JSON adapter is configured in the message service unit, the first JSON format data is received and processed, and the first JSON format data is forwarded to the core service unit for secondary processing;
and returning the first JSON format data to the message queue server and storing the first JSON format data into the database.
In one possible design, the data processing module is specifically further configured to:
and receiving a first data service request of the external application system through the message queue server, and returning a first data service request result to the external application system.
In one possible design, when the first data is collected through the HTTP data interface unit, the data processing module is specifically configured to:
converting the first data into second JSON format data and sending the second JSON format data to the message queue server;
a second JSON adapter is configured in the gateway service unit, the second JSON format data is received and processed, and the second JSON format data is forwarded to the core service unit for secondary processing;
and returning the second JSON format data to the message queue server and storing the second JSON format data in the database.
In one possible design, the data processing module is specifically further configured to:
receiving a second data service request of an external application system through the gateway service unit and forwarding the second data service request to the core business service unit;
and calling corresponding data from the database by the core service unit according to the second data service request, and returning a second data request result to the external application system.
In one possible design, when the first data is collected by the DDS data interface unit, the data processing module is specifically configured to:
configuring a DDS adapter, receiving the first data through the DDS adapter, and converting the first data into third JSON format data;
transmitting the third JSON format data to the message queue server;
a third JSON adapter is configured in the message service unit, the third JSON format data is received and forwarded to the core service unit for secondary processing;
and returning the third JSON format data to the message queue server and storing the third JSON format data in the database.
In one possible design, the data collection tool extracts the second data from the database by way of ETL.
In a second aspect, the present invention provides a data integrated distribution system, including a data integrated distribution platform as described in any one of the possible designs of the first aspect, and further including a plurality of application systems.
The beneficial effects are that:
the data interface module is mounted on the data integration platform, and the data acquisition tool is embedded in the data integration platform; collecting first data of an external application system through a data interface module; extracting second data of the database through a data acquisition tool; processing the first data and the second data through a data processing module and/or providing data service for an external application system through a data interface module; and storing the processed first data through a database. The invention can support various data interfaces including but not limited to HTTP interface, MQ interface and DSS interface, and data acquisition tool for database, so that the platform can configure, manage and monitor the data interfaces according to service requirement, thereby realizing data interaction with external application system rapidly; the data interface module is arranged in a mounting mode, so that the data interface module can be added and deleted according to service requirements on the premise of not changing the main frame of the platform, and the expandability of the platform is improved.
Drawings
FIG. 1 is a block diagram of a data integration distribution platform according to an embodiment of the present invention;
FIG. 2 is a diagram of an architecture deployment of a data integration distribution platform according to an embodiment of the present invention;
FIG. 3 is a block flow diagram of data interaction with an external application system according to an embodiment of the present invention.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present specification more clear, the technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are some embodiments of the present specification, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present invention based on the embodiments herein.
Examples
1-3, in a first aspect, the present invention provides a data integration and distribution platform, including a data interface module, a data collection tool, a data processing module, and a database;
the data interface module is mounted on the data integration platform, and the data acquisition tool is embedded in the data integration platform; by mounting the data interface module on the data integration platform, the data interface can be configured, added or deleted according to service requirements, and the universality and the expandability of the platform are ensured.
The data interface module is used for collecting first data of an external application system;
the data interface module comprises a data interface with a general format and a self-defined data interface, wherein the general data interface can directly collect data provided by a system through an interface json format configured in data maintenance management and configuration information of an application system; the user-defined data interface can generate a corresponding interface Adapter (Adapter) through an extensible configuration interface provided in data maintenance management, and can perform corresponding data acquisition through the interface.
Wherein the data interface module includes, but is not limited to, an MQ data interface unit, an HTTP data interface unit, and a DDS data interface unit; the data processing module performs data interaction with the external application system through the MQ data interface unit, the HTTP data interface unit and/or the DDS data interface unit; correspondingly, the first data includes, but is not limited to, MQ (Message Queue) data, HTTP (Hypertext Transfer Prtcl, hypertext transfer protocol) data, and DDS (Data Distribution Service ) data.
It should be noted that, the HTTP data interface unit is an asynchronous interface, and returns a task ID calling end every time it is called by the platform, and whether the currently executed task is completed or not can be queried according to the task ID.
The HTTP data interface unit provides corresponding webservice for an external application system to call, and the application scene is as follows: the data is required to be actively acquired, and the next processing is carried out depending on the acquired data, namely, the data request and the response need to be synchronized; data access or acquisition of infrequent scenarios, such as initialized data, which is followed by rarely updated data; the method is suitable for a data exchange short connection scene.
The MQ interface unit provides a corresponding message queue interface mode and provides the corresponding message queue interface mode for an external application system to call. The application scene is as follows: real-time data such as alarm pushing, real-time data of acquisition equipment and the like; the data which can be processed asynchronously is basically data which can be processed asynchronously for the data of the integrated platform because the application system has own data storage; the method is suitable for a long connection scene with frequent data interaction; a scenario of application notification is required.
When the data interface unit is used for collecting the DDS data, the DDS data cannot cross routers (cross network segments), so that a corresponding DDS gateway is required to be installed in the same network segment of the DDS service, and after the DDS data is actively subscribed, the data is transmitted to the integrated platform for unified processing and storage through a standard MQ interface form.
The external application system includes, but is not limited to, a portal application system, an operation and maintenance system, a politics system, a data display system, an enterprise management system, etc., which are not specifically limited and will not be described herein.
The data acquisition tool is used for extracting second data of the database;
it should be noted that, the data collection tool extracts the second data from the database by way of ETL (Extract Transform Load, data warehouse technology), where the second data is heterogeneous data stored in the database, and includes but is not limited to: text files, CSV (Comma Separated Values) files, JMS (Java Message Service ) files, and WebService files.
Wherein, preferably, the database is a dream Database (DB).
In addition, it can be understood that, when the external application system cannot provide the data interface, the data integration distribution platform can also acquire the data of the external application system through the data acquisition tool.
The data processing module is used for processing the first data and the second data and/or providing data service for the external application system through the data interface module;
it should be noted that the data processing module includes, but is not limited to, a message queue server, a message service unit, a gateway service unit, and a core service unit. In addition, various third party components may be included, such as: a registry service component, a Redis data caching service component, a Zookeeper coordination component, a RocketMQ message service component, an Elastic-Job distributed scheduling component, and an Nginx load balancing component. Based on this, as shown in fig. 2, an architecture deployment diagram of the data integration distribution platform in this embodiment is shown, where each component or unit adopts clustered deployment and performs networking through a local area network, where other components or units except the dream database cluster may be deployed by using a virtual machine or a docker container.
The database is also used for storing the processed first data.
Based on the above disclosure, the present embodiment can support various data interfaces, including but not limited to HTTP interfaces, MQ interfaces, and DSS interfaces, and data collection tools for databases, so that the platform can configure, manage, and monitor the data interfaces according to service requirements, thereby rapidly implementing data interaction with external application systems; the data interface module is arranged in a mounting mode, so that the data interface module can be added and deleted according to service requirements on the premise of not changing the main frame of the platform, and the expandability of the platform is improved
As an optional implementation manner, the data processing module includes a message queue server, a message service unit, a gateway service unit and a core service unit;
the data interface module sends the collected first data to the core service unit through the message queue server and the message service unit in sequence; or the core business service unit is sent to the gateway service unit;
the message queue server is used for receiving the first data and sending the first data to the message service unit based on a queue mechanism;
the message service unit is used for processing the first data according to the subscription message of the first data and forwarding the first data to the core business service unit;
specifically, after receiving the first data, the message service unit performs current limiting, resource allocation, receiving, capacity expansion and message forwarding on the first data according to the subscription message of the first data.
The gateway service unit is used for receiving the first data, processing the first data and forwarding the first data to the core service unit;
specifically, after receiving the first data, the gateway service unit performs current limiting, fusing, log management, black and white list query, authentication and interface forwarding on the first data.
The core service unit is used for carrying out secondary processing on the received first data, returning the second data to the message queue server and storing the second data into the database.
Specifically, after receiving the first data, the core service unit analyzes, verifies, cleans, desensitizes, merges and sorts the first data and forwards the data.
In addition, the core business service unit is also provided with a data pipeline and a WEB management system, and the core business service unit performs data interaction with the database through the data pipeline and performs configuration management on a data interface and parameters through the WEB management system.
In an alternative embodiment, the data processing module is specifically configured to, when the first data is collected by the MQ data interface unit:
converting the first data into first JSON format data and sending the first JSON format data to the message queue server;
when the first data of the external application system is collected through the MQ data interface unit, the platform can provide a template number for each application system, wherein the template number describes the system information of the access application system and the description of the accessed parameters; the template number can be preconfigured in the background of the platform, so that the flow of parameter description information transmitted by a calling party is simplified.
The message queue server contains a subscription theme of the accessed application system, and the subscription theme contains an ID allocated to the application system.
The first JSON format data comprises a template number and a data set of an application system.
The JSON format includes a general JSON format and a custom JSON format.
A first JSON adapter is configured in the message service unit, the first JSON format data is received and processed, and the first JSON format data is forwarded to the core service unit for secondary processing;
the JSON adapter comprises a universal JSON adapter and a custom JSON adapter.
Specifically, the message service unit performs flow limiting, resource allocation, receiving, capacity expansion and message forwarding processing on the first JSON format data; and the core service unit analyzes, verifies, cleans, desensitizes, merges and sorts the first JSON format data and forwards the data.
And returning the first JSON format data to the message queue server and storing the first JSON format data into the database.
In an alternative embodiment, the data processing module is specifically further configured to:
and receiving a first data service request of the external application system through the message queue server, and returning a first data service request result to the external application system.
When an external application system initiates a first data service request to a platform, the first data service request carries a theme name, and the theme name can be specifically defined according to service requirements; the first data service request is a JSON format request and comprises a service number and specific service data; after receiving the first data service request, the message queue server returns corresponding data to the external application service system if the message queue server has data matched with the first data service request, otherwise returns a prompt of failed request to the external application system; wherein the data corresponding to the first data service request includes, but is not limited to: total number of records, current page number, size of each page, total number of pages, and specific business data.
In an alternative embodiment, when the first data is collected by the HTTP data interface unit, the data processing module is specifically configured to:
converting the first data into second JSON format data and sending the second JSON format data to the message queue server;
when the first data of the external application system is collected through the HTTP data interface unit, the platform may provide a template number for each application system, where the template number describes system information of the access application system and describes parameters of the access; the template number can be preconfigured in the background of the platform, so that the flow of parameter description information transmitted by a calling party is simplified.
A second JSON adapter is configured in the gateway service unit, the second JSON format data is received and processed, and the second JSON format data is forwarded to the core service unit for secondary processing;
specifically, the gateway service unit performs current limiting, fusing, log management, black and white list query, authentication and interface forwarding on the first data; and the core service unit analyzes, verifies, cleans, desensitizes, merges and sorts the first JSON format data and forwards the data.
And returning the second JSON format data to the message queue server and storing the second JSON format data in the database.
In an alternative embodiment, the data processing module is specifically further configured to:
receiving a second data service request of an external application system through the gateway service unit and forwarding the second data service request to the core business service unit;
and calling corresponding data from the database by the core service unit according to the second data service request, and returning a second data request result to the external application system.
When an external application system initiates a second data service request to a platform, the second data service request carries a service number, a field name, a starting page, each page size and a data filtering condition; the gateway service unit receives the second data service request and then forwards the second data service request to the core service unit, the core service unit calls data matched with the second data service request to the database according to the second data service request, if the data matched with the second data service request exists in the database, the corresponding data is returned to the external application service system, and otherwise, a prompt of failure request is returned to the external application system; wherein the data corresponding to the first data service request includes, but is not limited to: total number of records, current page number, size of each page, total number of pages, and specific business data.
In an alternative embodiment, when the first data is collected by the DDS data interface unit, the data processing module is specifically configured to:
configuring a DDS adapter, receiving the first data through the DDS adapter, and converting the first data into third JSON format data;
wherein, it should be noted that, the DDS adapter is written with DDS adapting programs, each DDS adapting program can subscribe various DDS data, then the platform will assign a plurality of template numbers to the DDS adapting program, each template number corresponds to a DDS data definition; then, the DDS adapter converts the received first data into data in a third JSON format and sends the data to the message queue server. How to subscribe, receive and parse the first data may be implemented by a JAVA tool library.
Transmitting the third JSON format data to the message queue server;
a third JSON adapter is configured in the message service unit, the third JSON format data is received and forwarded to the core service unit for secondary processing;
specifically, the message service unit performs flow limiting, resource allocation, receiving, capacity expansion and message forwarding processing on the first JSON format data; and the core service unit analyzes, verifies, cleans, desensitizes, merges and sorts the first JSON format data and forwards the data.
And returning the third JSON format data to the message queue server and storing the third JSON format data in the database.
In a second aspect, the present invention provides a data integrated distribution system, including a data integrated distribution platform as described in any one of the possible designs of the first aspect, and further including a plurality of application systems.
Finally, it should be noted that: the foregoing description is only of the preferred embodiments of the invention and is not intended to limit the scope of the invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (8)

1. The data integration distribution platform is characterized by comprising a data interface module, a data acquisition tool, a data processing module and a database;
the data interface module is mounted on the data integration platform, and the data acquisition tool is embedded in the data integration platform;
the data interface module is used for collecting first data of an external application system;
the data acquisition tool is used for extracting second data of the database;
the data processing module is used for processing the first data and the second data and/or providing data service for the external application system through the data interface module;
the database is also used for storing the processed first data;
the data processing module comprises a message queue server, a message service unit, a gateway service unit and a core service unit;
the data interface module sends the collected first data to the core service unit through the message queue server and the message service unit in sequence; or the core business service unit is sent to the gateway service unit;
the message queue server is used for receiving the first data and sending the first data to the message service unit based on a queue mechanism;
the message service unit is used for processing the first data according to the subscription message of the first data and forwarding the first data to the core business service unit;
the gateway service unit is used for receiving the first data, processing the first data and forwarding the first data to the core service unit;
the core service unit is used for carrying out secondary processing on the received first data, returning the second data to the message queue server and storing the second data into the database;
the data interface module comprises an MQ data interface unit, an HTTP data interface unit and a DDS data interface unit; and the data processing module performs data interaction with the external application system through the MQ data interface unit, the HTTP data interface unit and/or the DDS data interface unit.
2. The data integrated distribution platform of claim 1, wherein the data processing module is specifically configured to, when the first data is collected via the MQ data interface unit:
converting the first data into first JSON format data and sending the first JSON format data to the message queue server;
a first JSON adapter is configured in the message service unit, the first JSON format data is received and processed, and the first JSON format data is forwarded to the core service unit for secondary processing;
and returning the first JSON format data to the message queue server and storing the first JSON format data into the database.
3. The data integrated distribution platform according to claim 2, wherein the data processing module is further specifically configured to:
and receiving a first data service request of the external application system through the message queue server, and returning a first data service request result to the external application system.
4. The data integrated distribution platform according to claim 1, wherein the data processing module is specifically configured to, when the first data is collected via the HTTP data interface unit:
converting the first data into second JSON format data and sending the second JSON format data to the message queue server;
a second JSON adapter is configured in the gateway service unit, the second JSON format data is received and processed, and the second JSON format data is forwarded to the core service unit for secondary processing;
and returning the second JSON format data to the message queue server and storing the second JSON format data in the database.
5. The data integrated distribution platform of claim 4, wherein the data processing module is further specifically configured to:
receiving a second data service request of an external application system through the gateway service unit and forwarding the second data service request to the core business service unit;
and calling corresponding data from the database by the core service unit according to the second data service request, and returning a second data request result to the external application system.
6. The data integrated distribution platform according to claim 1, wherein the data processing module is specifically configured to, when the first data is collected by the DDS data interface unit:
configuring a DDS adapter, receiving the first data through the DDS adapter, and converting the first data into third JSON format data;
transmitting the third JSON format data to the message queue server;
a third JSON adapter is configured in the message service unit, the third JSON format data is received and forwarded to the core service unit for secondary processing;
and returning the third JSON format data to the message queue server and storing the third JSON format data in the database.
7. The data integration distribution platform of claim 1, wherein the data collection tool extracts the second data from the database by way of ETL.
8. A data integrated distribution system, comprising a data integrated distribution platform according to any of claims 1-7, and further comprising a plurality of application systems.
CN202110803028.9A 2021-07-15 2021-07-15 Data integration distribution platform and system Active CN113407611B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110803028.9A CN113407611B (en) 2021-07-15 2021-07-15 Data integration distribution platform and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110803028.9A CN113407611B (en) 2021-07-15 2021-07-15 Data integration distribution platform and system

Publications (2)

Publication Number Publication Date
CN113407611A CN113407611A (en) 2021-09-17
CN113407611B true CN113407611B (en) 2023-05-26

Family

ID=77686659

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110803028.9A Active CN113407611B (en) 2021-07-15 2021-07-15 Data integration distribution platform and system

Country Status (1)

Country Link
CN (1) CN113407611B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999011043A1 (en) * 1997-08-25 1999-03-04 I2 Technologies, Inc. Universal adapter framework and providing a global user interface and global messaging bus

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103177156A (en) * 2013-02-27 2013-06-26 北京视博数字电视科技有限公司 Designer system for enterprise application integration adapter and design method thereof
CN109492040B (en) * 2018-11-06 2021-12-28 深圳航天智慧城市系统技术研究院有限公司 System suitable for processing mass short message data in data center
CN111383748A (en) * 2020-03-09 2020-07-07 武汉比邻软件有限公司 Medical integrated platform system based on elastic calculation and 5G technology
CN112256795A (en) * 2020-10-10 2021-01-22 广西电网有限责任公司 Data integration platform data service system
CN112631794A (en) * 2020-12-02 2021-04-09 红云红河烟草(集团)有限责任公司 Information integration method for cigarette manufacturing

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999011043A1 (en) * 1997-08-25 1999-03-04 I2 Technologies, Inc. Universal adapter framework and providing a global user interface and global messaging bus

Also Published As

Publication number Publication date
CN113407611A (en) 2021-09-17

Similar Documents

Publication Publication Date Title
CN101719841B (en) Monitoring system and method of distributed type assemblies
CN102880475B (en) Based on the real-time event disposal system of cloud computing and method in computer software
CN111737329A (en) Unified data acquisition platform for rail transit
CN105338086A (en) Distributed message forwarding method
CN101502144A (en) Element management system in wireless communication network
US8478714B2 (en) Integrated distribution management system channel adapter
CN113596150B (en) Message pushing method, device, computer equipment and storage medium
CN110008267B (en) Data processing system and method
CN105183299A (en) Human-computer interface service processing system and method
CN101667932B (en) Method of network element equipment log management and device
CN109428745B (en) JMS message forwarding method, device, electronic equipment and storage medium
CN113407611B (en) Data integration distribution platform and system
CN113472848A (en) Network fusion method and device of virtual machine and container and related equipment
CN112417050A (en) Data synchronization method and device, system, storage medium and electronic device
CN102904739A (en) Method for realizing event transmission and common information model (CIM) server
CN115858196A (en) Agile event processing method and notification system thereof
CN114501347A (en) Information interaction method, device and system between heterogeneous systems
CN103957127A (en) Heterogeneous manufacturer transmission network interface adaptation method
CN111541667A (en) Method, equipment and storage medium for intersystem message communication
CN101557436B (en) Resource monitoring method and device thereof
CN112134636B (en) Remote centralized monitoring system and method for remote sensing satellite ground station network
CN117873758B (en) Communication method between DCS system stations based on message bus
JP5035286B2 (en) Bus-type message exchange system, bus-type message exchange method and program
CN102130944A (en) Method for monitoring and managing common use self and self-service system
JP3341707B2 (en) Autonomous cooperative distributed processing management information system

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
GR01 Patent grant
GR01 Patent grant