CN112363845A - Data synchronization method of system integration middling station and integration middling station system - Google Patents
Data synchronization method of system integration middling station and integration middling station system Download PDFInfo
- Publication number
- CN112363845A CN112363845A CN202011149388.3A CN202011149388A CN112363845A CN 112363845 A CN112363845 A CN 112363845A CN 202011149388 A CN202011149388 A CN 202011149388A CN 112363845 A CN112363845 A CN 112363845A
- Authority
- CN
- China
- Prior art keywords
- event
- adaptation service
- request
- foreground adaptation
- foreground
- 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.)
- Withdrawn
Links
Images
Classifications
-
- 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/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a data synchronization method of a system integration middlebox and an integration middlebox system, wherein the method comprises the following steps: the foreground adaptation service corresponding to the third-party application system acquires annotation information of the event interface according to the annotation identifier, assembles event registration information according to the annotation information and configuration information of the foreground adaptation service, and sends a registration request to the system integration center according to the event registration information; the system integration center station scans the first event request through the timing task, matches the foreground adaptation service and the event interface to acquire data in the third-party application system, receives the second event request of the user, matches the foreground adaptation service and the event interface, and synchronizes the data to the third-party application system. The invention carries out timing and directional synchronization by the butt joint of the foreground adaptation service and the third-party application system, lightens the synchronization pressure of the server and facilitates the integration of a plurality of third-party application platforms.
Description
Technical Field
The invention relates to the technical field of third-party application system integration, in particular to a data synchronization method of a system integration middlebox and an integration middlebox system.
Background
At present, the market has a variety of commodity applications APP aiming at different services, the service data of the applications APP are usually independent, a user needs to use certain service data, at least one specific APP is usually required to be downloaded, and the user can check the APP after logging in; the user often can use multiple service data, just need download a large amount of APP, consumes cell-phone resources, and is also inconvenient in the use. Therefore, the system integration middle platform is constructed to be in butt joint with various third-party application platforms according to business requirements, and how to keep synchronization with data of the third-party application platforms becomes an important problem.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art. Therefore, the invention provides a data synchronization method of a system integration middlebox, which can synchronously interact with data of a third-party application platform.
The invention also provides an integrated middling station system with the data synchronization method of the system integrated middling station.
The data synchronization method of the system integration center according to the first aspect of the invention comprises the following steps: an event registration request step, in which a foreground adaptation service corresponding to a third-party application system acquires annotation information of an event interface according to an annotation identifier, assembles the event registration information according to the annotation information and configuration information of the foreground adaptation service, and sends a registration request to a system integration center according to the event registration information; an event registration executing step, in which the system integration central office receives the registration request, registers the event and persists the event registration information; and a data synchronization step, in which the system integration center scans a first event request through a timing task, matches the foreground adaptation service and the event interface according to the event registration information, calls the event interface through the foreground adaptation service to acquire data in the third-party application system, receives a second event request of a user, matches the corresponding foreground adaptation service and the event interface according to the event registration information, calls the event interface through the foreground adaptation service, and synchronizes the data to the third-party application system.
The data synchronization method of the system integration middle station according to the embodiment of the invention at least has the following beneficial effects: the system comprises a foreground adaptation service, a third-party application system, a client, a system integration center and a system integration center, wherein the foreground adaptation service corresponds to the third-party application system one by one, an event interface and corresponding annotation information are analyzed through annotation identification, the corresponding event interface is called back through timing scanning of an event request, timing synchronization is carried out, and synchronization is carried out on the third-party application system according to the event request generated by modifying data of the system integration center by a user, so that the synchronization pressure of a server can be relieved, and the normal operation of a normal service system; meanwhile, the synchronous logic is unified, code coupling is reduced, development time of developers is saved, and integration of a plurality of third-party application platforms is more convenient.
According to some embodiments of the invention, the event registration requesting step comprises: the foreground adaptation service analyzes the event interface by scanning the annotation identifier to acquire the annotation information corresponding to the event interface; based on a preset naming rule, acquiring the service type and the operation type of an event according to the event interface, and acquiring a callback parameter through the annotation information; and acquiring configuration information of the foreground adaptation service, assembling the event registration information according to the service type, the operation type and the callback parameter, and sending a registration request to the system integration center.
According to some embodiments of the invention, the configuration information of the foreground adaptation service comprises: adapter type, application identification, and access address.
According to some embodiments of the present invention, the method for matching the corresponding foreground adaptation service according to the event registration information comprises: the system integration center receives the first event request or the second event request, generates a corresponding request serial number, acquires configuration information of the foreground adaptation service according to the event registration information, and determines the foreground adaptation service to be accessed; the system integration central station acquires the service type, the operation type and the callback parameter according to the event registration information, determines the event interface according to the service type and the operation type, calls the event interface, records the current calling times, and records the event execution state according to the return result of the event interface.
According to some embodiments of the invention, the data synchronization step further comprises: and if the event execution state is execution failure, the event interface is repeatedly executed according to the request serial number until the return result of the event interface is successful or the repeated calling times exceed a preset value.
According to some embodiments of the present invention, the data synchronization step further includes the system integration middle station determining whether the foreground adaptation service has been recovered according to a heartbeat packet reported by the foreground adaptation service, and stopping triggering the call of the event interface of the foreground adaptation service according to a recovery result.
According to some embodiments of the present invention, the method for the system integration center to determine the foreground adaptation service includes: the system integration middle station configures the reporting frequency of the heartbeat packet reported by the foreground adaptation service, and the foreground adaptation service reports the heartbeat packet according to the reporting frequency; and the system integration middle station configures a first recovery time according to the reporting frequency, and if the heartbeat packet is not received within the first recovery time, the system integration middle station judges that the front station adaptation service is recovered.
An integrated staging system according to an embodiment of the second aspect of the invention comprises: the foreground adaptation service module is used for being connected with a corresponding third-party application system, constructing an event interface according to business data interaction requirements, acquiring annotation information of the event interface according to annotation identification, assembling event registration information according to the annotation information and configuration information of the foreground adaptation service, and sending a registration request according to the event registration information; the event registration module is used for receiving the registration request, registering an event and persisting the event registration information; and the data synchronization module is used for receiving a first event request generated by timing task scanning, matching the corresponding foreground adaptation service and the event interface according to the event registration information, calling the event interface through the foreground adaptation service to acquire data in the third-party application system, receiving a second event request of a user, matching the corresponding foreground adaptation service and the event interface according to the event registration information, calling the event interface through the foreground adaptation service, and synchronizing the data to the third-party application system.
The integrated middle platform system according to the embodiment of the invention has at least the following beneficial effects: the system comprises a foreground adaptation service, a third-party application system, a timing task scanning module, a synchronization module, a central processing module and a central processing module, wherein the foreground adaptation service corresponds to the third-party application system one by one, event interfaces and corresponding annotation information are analyzed through annotation identification, a first event request is obtained through timing task scanning, the corresponding event interfaces are called back, timing synchronization is carried out, and synchronization is carried out on the third-party application system according to a second event request generated by modifying data of a central processing unit of the system integration by a user, so that the synchronization pressure of; meanwhile, the synchronous logic is unified, code coupling is reduced, development time of developers is saved, and integration of a plurality of third-party application platforms is more convenient.
According to some embodiments of the invention, the data synchronization module further comprises: and the task management module is used for scanning and acquiring the event request at regular time, generating a request serial number of the event, inquiring the event execution state of the event request based on the request serial number, and repeatedly executing the event request according to the event execution state and the preset repeated execution times.
According to some embodiments of the invention, the data synchronization module further comprises: the heartbeat monitoring module is used for configuring the reporting frequency of the heartbeat package, receiving the heartbeat package reported by the foreground adaptation service module according to the reporting frequency, and monitoring whether the foreground adaptation service module is recovered or not according to the receiving state of the heartbeat package to obtain a recovery result; and the recovery control module is used for stopping triggering the calling of the event interface of the foreground adaptation service according to the recovery result.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The above and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a schematic flow chart of a method according to an embodiment of the present invention;
FIG. 2 is a block schematic diagram of modules of a system of an embodiment of the invention;
FIG. 3 is a schematic diagram of data interaction after module deployment in the system according to the embodiment of the present invention;
fig. 4 is a schematic diagram of a corresponding data structure managed by the task management module according to the event registration information in the system according to the embodiment of the present invention.
Reference numerals:
a foreground adaptation service module 100, an event registration module 200, and a data synchronization module 300;
an event interface editing module 110 and an event interface analyzing module 120;
a task management module 310, a heartbeat monitoring module 320, and a recovery control module 330.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention.
In the description of the present invention, the meaning of a plurality of means is one or more, the meaning of a plurality of means is two or more, and more than, less than, more than, etc. are understood as excluding the present number, and more than, less than, etc. are understood as including the present number. If the first and second are described for the purpose of distinguishing technical features, they are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated or implicitly indicating the precedence of the technical features indicated.
Referring to fig. 1, a method of an embodiment of the present invention includes: an event registration request step, in which a foreground adaptation service corresponding to a third-party application system acquires annotation information of an event interface according to an annotation identifier, assembles event registration information according to the annotation information and configuration information of the foreground adaptation service, and sends a registration request to a system integration center according to the event registration information; an event registration executing step, in which a system integration central office receives a registration request, registers an event and persists event registration information; a data synchronization step, comprising: the system integration center acquires data from the third-party application system and synchronizes the data to the third-party application system. The system integration middle desk scans a first event request through a timing task, matches a foreground adaptation service and an event interface according to event registration information, and calls the event interface through the foreground adaptation service to acquire data in a third-party application system; the system integration center receives a second event request of the user, matches corresponding foreground adaptation service and an event interface according to the event registration information, calls the event interface through the foreground adaptation service, and synchronizes data to a third-party application system.
In the event registration request step, the foreground adaptation service analyzes an event interface by scanning the annotation identifier and acquires annotation information of the event interface; based on a preset naming rule, acquiring the service type and the operation type of an event through the name of an event interface, and acquiring information such as callback parameters through annotation information; then, obtaining configuration information (including adapter type, application program identification and access address) of foreground adaptation service, according to service type, operation type and callback parameter, assembling event registration information, and sending registration request to system integration central station. Registering events according to business data interaction requirements, for example, if a third-party commodity is synchronized, commodity adding events need to be registered; in the embodiment of the present invention, a corresponding event interface in sdk integrated in the foreground adaptation service can be bound by the service type and the operation type. The corresponding interface of the SDK is realized in the foreground adaptation server by developers, obviously, different developers can develop the SDK based on the same annotation rule and naming rule aiming at different third-party application systems, and therefore development time is saved. For example, for an interface added to a commodity, a developer may implement the "executeAdd" method in the "ItemWkAdapter" in the foreground adaptation service. In some embodiments of the present invention, the annotation content may further include a data flow direction, where the adapter type of the consumer of the data identifies whether the data flows from the third-party system platform to the system integration staging (in this case, the consumer is the system integration staging) or from the system integration staging to the third-party system platform (in this case, the consumer is the third-party system platform); in other embodiments of the invention, the adapter type of the consumer of the data is parsed according to the naming convention.
The system integration center receives the registration request, registers the corresponding event according to the event registration information, and persists the event registration information. The system integration console starts a timing scanning task for synchronizing data from a third-party application system, and the data result of the first event request managed by the task refers to fig. 4, and includes an application ID (i.e., an application identifier), an event request serial number, an event execution state, the number of times of executing the event request serial number, an event callback parameter (i.e., a parameter required when an event is consumed), a service type, an operation type, an adapter type, and a program access address. If the system integration center receives the first event request or the second event request, generating a corresponding request serial number, initializing the event execution state to be executed, then acquiring configuration information of foreground adaptation service in the event registration information, and determining the adapter type, the application program identifier and the access address of the third-party application system to be accessed; and calling a corresponding event interface according to the service type and the operation type, updating the event execution state into an execution state, and recording the event execution state according to the return result state of the event interface. If the execution state of a certain event is failure, the event interface is repeatedly executed according to the request serial number until the execution is successful or the repeated calling times exceed a preset value.
In the embodiment of the invention, the system integration central station acquires a first event request through a timing task, matches with a corresponding foreground adaptation service, calls a corresponding event interface by the foreground adaptation service to consume the first event, acquires synchronous data from a third-party application system, assembles the synchronous data according to a preset data service rule of the system integration central station, throws out external synchronous events, is uniformly processed by a synchronous event consumption interface, calls a corresponding service synchronous interface of the system integration central station through a service type and an operation type, and writes the synchronous data into a database of the system integration central station. And if the user modifies the data in the database through the page of the system integration center, generating a second event request, and sending the second event request to the synchronous event consumption interface. The synchronous event consumption interface is used for analyzing the application program identifier, the service type and the operation type from the second event request, acquiring the adapter type and the access address according to the event registration information, filtering the event message through the application program identifier, the service type and the operation type and determining that the second event request is an event request for synchronizing data to a third-party application system; then, according to the application program identification, the service type, the operation type, the access address, the request serial number, the adapter type, the callback parameter and other event registration information, converting into a foreground adaptation service consumption event corresponding to the second event request, and sending to the foreground adaptation service. The foreground adaptation service receives the consumption event of the foreground adaptation service and synchronizes data in a database of the third-party application system by calling a corresponding event interface.
The foreground adaptation service also sends heartbeat packets according to the reporting frequency configured by the system integration middle station to indicate that the foreground adaptation service is available. For example, the heartbeat packet is reported every 5 minutes. The system integration middle station configures first recovery time (for example, 30 minutes), detects a heartbeat packet reported by the foreground adaptation service, determines that the foreground adaptation service is recovered if the first recovery time is exceeded and the heartbeat packet reported by the foreground adaptation service is not received, and stops triggering the call of a corresponding event interface of the foreground adaptation service. Obviously, the first recovery time is related to the setting of reporting frequency, and the first recovery time must be longer than the period of one reporting.
Referring to fig. 2, the system according to the embodiment of the present invention includes a foreground adaptation service module 100, an event registration module 200, and a data synchronization module 300. Wherein the foreground adaptation service module 100 includes: the event interface editing module 110 and the event interface analyzing module 120; the foreground adaptation service module 100 is configured to connect to a corresponding third-party application system, acquire and register an event, provide an event callback interface, and access third-party data of the third-party application system. The event interface editing module 110 is configured to provide an editing interface for a developer to construct an event interface according to a business data interaction requirement, where the writing of the event interface needs to be performed according to a fixed annotation standard and a command specification; the event interface parsing module 120 is configured to extract an event interface and related information from a code written by a developer, and perform an event request, where the event interface parsing module includes: and acquiring annotation information of the event interface according to the annotation identifier, assembling event registration information according to the annotation information and configuration information of foreground adaptation service, and sending a registration request according to the event registration information. An event registration module 200, configured to receive a registration request, register an event, and persist event registration information; the data synchronization module 300 is configured to receive a first event request generated by the timing task scanning, match a corresponding foreground adaptation service and an event interface according to the event registration information, call the event interface through the foreground adaptation service to obtain data in the third-party application system, receive a second event request of a user, match the corresponding foreground adaptation service and the event interface according to the event registration information, call the event interface through the foreground adaptation service, and synchronize the data with the third-party application system.
Referring to fig. 2, the data synchronization module 300 according to the embodiment of the present invention includes: a task management module 310, a heartbeat monitoring module 320, and a recovery control module 330. The task management module 310 is configured to scan and obtain an event request at regular time, generate a request serial number of the event, query an event execution state of the event request based on the request serial number, and repeatedly execute the event request according to the event execution state and a preset number of times of repeated execution. The task management module 310 manages event requests through a data structure as shown in FIG. 4. If an event request is received, generating a corresponding request serial number, initializing an event execution state as to-be-executed, then determining an adapter type, an application program identifier and an access address of a third-party application system to be accessed according to configuration information of foreground adaptation service in the acquired event registration information, calling a corresponding event interface according to the service type and the operation type, updating the event execution state as in-execution, and updating the event execution state according to a return result state of the event interface. If the execution state of a certain event is failure, the event interface is repeatedly executed according to the request serial number until the execution is successful or the repeated calling times exceed a preset value. If the preset value is 3 times, the three times of repeated execution of the call of the event interface fails, and the event request flow is not repeatedly executed. And a heartbeat monitoring module 320, configured to configure a reporting frequency of the heartbeat packet, receive the heartbeat packet reported by the foreground adaptation service module according to the reporting frequency, and monitor whether the foreground adaptation service module has been recovered according to a receiving state of the heartbeat packet, to obtain a recovery result. And the recovery control module 330 is configured to stop triggering the call of the event interface of the foreground adaptation service according to the recovery result.
Referring to fig. 3, in the embodiment of the present invention, a foreground adaptation service module 100 is deployed in a foreground adaptation service; the event registration module 200 and the data synchronization module 300 are deployed in a data synchronization middlebox. And the user requests to access the data of the third application platform system through respective terminal, the access request is processed by the background request, and corresponding response data is obtained from the database and returned to the user terminal. If the database does not have corresponding third-party data or the third-party data needs to be changed (such as adding, updating, deleting and the like), a corresponding event request is generated and sent to the data synchronization center. The data synchronization middle station scans the event request at regular time, and performs corresponding access operation (such as query, addition, update, deletion or self-definition operation) on the third-party data through a corresponding event interface in the foreground adaptation service corresponding to asynchronous callback, acquires the corresponding data, and synchronizes to the database through the data synchronization middle station. It should be noted that for ease of understanding, the data flow for obtaining third party data and synchronizing to the database is not identified in FIG. 3; nor does it identify the request flow for requesting data from the database at the time of background request processing.
Although specific embodiments have been described herein, those of ordinary skill in the art will recognize that many other modifications or alternative embodiments are equally within the scope of this disclosure. For example, any of the functions and/or processing capabilities described in connection with a particular device or component may be performed by any other device or component. In addition, while various illustrative implementations and architectures have been described in accordance with embodiments of the present disclosure, those of ordinary skill in the art will recognize that many other modifications of the illustrative implementations and architectures described herein are also within the scope of the present disclosure.
Certain aspects of the present disclosure are described above with reference to block diagrams and flowchart illustrations of systems, methods, systems, and/or computer program products according to example embodiments. It will be understood that one or more blocks of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by executing computer-executable program instructions. Also, according to some embodiments, some blocks of the block diagrams and flow diagrams may not necessarily be performed in the order shown, or may not necessarily be performed in their entirety. In addition, additional components and/or operations beyond those shown in the block diagrams and flow diagrams may be present in certain embodiments.
Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special purpose hardware and computer instructions.
Program modules, applications, etc. described herein may include one or more software components, including, for example, software objects, methods, data structures, etc. Each such software component may include computer-executable instructions that, in response to execution, cause at least a portion of the functionality described herein (e.g., one or more operations of the illustrative methods described herein) to be performed.
The software components may be encoded in any of a variety of programming languages. An illustrative programming language may be a low-level programming language, such as assembly language associated with a particular hardware architecture and/or operating system platform. Software components that include assembly language instructions may need to be converted by an assembler program into executable machine code prior to execution by a hardware architecture and/or platform. Another exemplary programming language may be a higher level programming language, which may be portable across a variety of architectures. Software components that include higher level programming languages may need to be converted to an intermediate representation by an interpreter or compiler before execution. Other examples of programming languages include, but are not limited to, a macro language, a shell or command language, a job control language, a scripting language, a database query or search language, or a report writing language. In one or more exemplary embodiments, a software component containing instructions of one of the above programming language examples may be executed directly by an operating system or other software component without first being converted to another form.
The software components may be stored as files or other data storage constructs. Software components of similar types or related functionality may be stored together, such as in a particular directory, folder, or library. Software components may be static (e.g., preset or fixed) or dynamic (e.g., created or modified at execution time).
The embodiments of the present invention have been described in detail with reference to the accompanying drawings, but the present invention is not limited to the above embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the gist of the present invention.
Claims (10)
1. A data synchronization method for a system integration center is characterized by comprising the following steps:
an event registration request step, in which a foreground adaptation service corresponding to a third-party application system acquires annotation information of an event interface according to an annotation identifier, assembles the event registration information according to the annotation information and configuration information of the foreground adaptation service, and sends a registration request to a system integration center according to the event registration information;
an event registration executing step, in which the system integration central office receives the registration request, registers the event and persists the event registration information;
and a data synchronization step, in which the system integration center scans a first event request through a timing task, matches the foreground adaptation service and the event interface according to the event registration information, calls the event interface through the foreground adaptation service to acquire data in the third-party application system, receives a second event request of a user, matches the corresponding foreground adaptation service and the event interface according to the event registration information, calls the event interface through the foreground adaptation service, and synchronizes the data to the third-party application system.
2. The data synchronization method of the system integration center according to claim 1, wherein the event registration request step comprises:
the foreground adaptation service analyzes the event interface by scanning the annotation identifier to acquire the annotation information corresponding to the event interface;
based on a preset naming rule, acquiring the service type and the operation type of an event according to the event interface, and acquiring a callback parameter through the annotation information;
and acquiring configuration information of the foreground adaptation service, assembling the event registration information according to the service type, the operation type and the callback parameter, and sending a registration request to the system integration center.
3. The data synchronization method of the system integration center according to claim 2, wherein the configuration information of the foreground adaptation service comprises: adapter type, application identification, and access address.
4. The data synchronization method of the system integration center according to claim 2, wherein the method for matching the corresponding foreground adaptation service according to the event registration information comprises:
the system integration center receives the first event request or the second event request, generates a corresponding request serial number, acquires configuration information of the foreground adaptation service according to the event registration information, and determines the foreground adaptation service to be accessed;
the system integration central station acquires the service type, the operation type and the callback parameter according to the event registration information, determines the event interface according to the service type and the operation type, calls the event interface, records the current calling times, and records the event execution state according to the return result of the event interface.
5. The data synchronization method of the system integration center according to claim 4, wherein the data synchronization step further comprises:
and if the event execution state is execution failure, the event interface is repeatedly executed according to the request serial number until the return result of the event interface is successful or the repeated calling times exceed a preset value.
6. The data synchronization method of the system integration center according to claim 4, wherein the data synchronization step further comprises:
and the system integration middle station judges whether the foreground adaptation service is recovered according to the heartbeat packet reported by the foreground adaptation service, and stops triggering the calling of the event interface of the foreground adaptation service according to a recovery result.
7. The method for data synchronization of a system integration center according to claim 6, wherein the method for the system integration center to determine the foreground adaptation service comprises:
the system integration middle station configures the reporting frequency of the heartbeat packet reported by the foreground adaptation service, and the foreground adaptation service reports the heartbeat packet according to the reporting frequency;
and the system integration middle station configures a first recovery time according to the reporting frequency, and if the heartbeat packet is not received within the first recovery time, the system integration middle station judges that the front station adaptation service is recovered.
8. An integrated staging system, comprising:
the foreground adaptation service module is used for being connected with a corresponding third-party application system, constructing an event interface according to business data interaction requirements, acquiring annotation information of the event interface according to annotation identification, assembling event registration information according to the annotation information and configuration information of the foreground adaptation service, and sending a registration request according to the event registration information;
the event registration module is used for receiving the registration request, registering an event and persisting the event registration information;
and the data synchronization module is used for receiving a first event request generated by timing task scanning, matching the corresponding foreground adaptation service and the event interface according to the event registration information, calling the event interface through the foreground adaptation service to acquire data in the third-party application system, receiving a second event request of a user, matching the corresponding foreground adaptation service and the event interface according to the event registration information, calling the event interface through the foreground adaptation service, and synchronizing the data to the third-party application system.
9. The integrated staging system of claim 8, wherein the data synchronization module further comprises: and the task management module is used for scanning and acquiring the event request at regular time, generating a request serial number of the event, inquiring the event execution state of the event request based on the request serial number, and repeatedly executing the event request according to the event execution state and the preset repeated execution times.
10. The integrated staging system of claim 8, wherein the data synchronization module further comprises:
the heartbeat monitoring module is used for configuring the reporting frequency of the heartbeat package, receiving the heartbeat package reported by the foreground adaptation service module according to the reporting frequency, and monitoring whether the foreground adaptation service module is recovered or not according to the receiving state of the heartbeat package to obtain a recovery result;
and the recovery control module is used for stopping triggering the calling of the event interface of the foreground adaptation service according to the recovery result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149388.3A CN112363845A (en) | 2020-10-23 | 2020-10-23 | Data synchronization method of system integration middling station and integration middling station system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149388.3A CN112363845A (en) | 2020-10-23 | 2020-10-23 | Data synchronization method of system integration middling station and integration middling station system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112363845A true CN112363845A (en) | 2021-02-12 |
Family
ID=74512000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011149388.3A Withdrawn CN112363845A (en) | 2020-10-23 | 2020-10-23 | Data synchronization method of system integration middling station and integration middling station system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112363845A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297218A (en) * | 2021-05-20 | 2021-08-24 | 广州光点信息科技有限公司 | Multi-system data interaction method, device and system |
| CN113791586A (en) * | 2021-07-27 | 2021-12-14 | 贵州元数通科技有限公司 | Novel industrial APP and identification registration analysis integration method |
| CN114510534A (en) * | 2022-01-28 | 2022-05-17 | 广东航宇卫星科技有限公司 | Data synchronization method, device, equipment and storage medium |
| WO2023098570A1 (en) * | 2021-11-30 | 2023-06-08 | 阿里云计算有限公司 | Model construction method, display platform, server and storage medium |
| CN117726148A (en) * | 2024-02-08 | 2024-03-19 | 中航信移动科技有限公司 | Method for determining adaptation degree of server, electronic equipment and storage medium |
-
2020
- 2020-10-23 CN CN202011149388.3A patent/CN112363845A/en not_active Withdrawn
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297218A (en) * | 2021-05-20 | 2021-08-24 | 广州光点信息科技有限公司 | Multi-system data interaction method, device and system |
| CN113297218B (en) * | 2021-05-20 | 2022-01-07 | 广州光点信息科技有限公司 | Multi-system data interaction method, device and system |
| CN113791586A (en) * | 2021-07-27 | 2021-12-14 | 贵州元数通科技有限公司 | Novel industrial APP and identification registration analysis integration method |
| WO2023098570A1 (en) * | 2021-11-30 | 2023-06-08 | 阿里云计算有限公司 | Model construction method, display platform, server and storage medium |
| CN114510534A (en) * | 2022-01-28 | 2022-05-17 | 广东航宇卫星科技有限公司 | Data synchronization method, device, equipment and storage medium |
| CN117726148A (en) * | 2024-02-08 | 2024-03-19 | 中航信移动科技有限公司 | Method for determining adaptation degree of server, electronic equipment and storage medium |
| CN117726148B (en) * | 2024-02-08 | 2024-04-26 | 中航信移动科技有限公司 | Method for determining adaptation degree of server, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112363845A (en) | Data synchronization method of system integration middling station and integration middling station system | |
| CN109542865B (en) | Method, device, system and medium for synchronizing configuration files of distributed cluster system | |
| US10649761B2 (en) | Application upgrade method and apparatus | |
| US8601466B2 (en) | Software deployment method and system, software deployment server and user server | |
| US7992132B2 (en) | Server side application integration framework | |
| CN102413022B (en) | Application debugging method and system | |
| CN111061643B (en) | SDK cluster compatibility detection method and device, electronic equipment and storage medium | |
| JP2011516987A (en) | Method and apparatus for managing mobile device software | |
| CN113515278A (en) | Low code model processing method, system, electronic device and storage medium | |
| US20070022154A1 (en) | Generating one or more clients for generating one or more synthetic transactions with one or more web service operations | |
| US11740886B2 (en) | Algorithm update method and apparatus | |
| CN111582824B (en) | Cloud resource synchronization method, device, equipment and storage medium | |
| CN112583630B (en) | Device management method, device, system, device and storage medium | |
| CN114020840A (en) | Data processing method, device, server, storage medium and product | |
| CN109739665A (en) | Interface managerial method, device, server and storage medium | |
| CN113419818A (en) | Basic component deployment method, device, server and storage medium | |
| CN112328317A (en) | Method for generating diagram by server based on node-canvas | |
| CN109005163B (en) | HTTP dynamic request service calling method | |
| CN113190565B (en) | Data updating method and device, storage medium and electronic device | |
| CN114610446A (en) | Method, device and system for automatically injecting probe | |
| CN114328152A (en) | Log recording method, device, equipment and medium | |
| CN114265638A (en) | Communication method, device, equipment and storage medium based on plug-in compatibility | |
| CN113179332A (en) | Method, electronic device and storage medium for acquiring configuration information | |
| CN111291101A (en) | Cluster management method and system | |
| CN108804236B (en) | AIDL file sharing method and 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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210212 |
|
| WW01 | Invention patent application withdrawn after publication |