A data acquisition general method and system of a business integration system

Abstract

This invention discloses a general method and apparatus for data acquisition in a business integration system, relating to the field of data processing technology. It enables data interaction between subsystems, is not limited by business scenarios, requires no significant modification costs to subsystems, and facilitates effective control of data interaction quality using a data integration system. The main technical solution of this invention is as follows: when a specified event is triggered on a subsystem, the event data corresponding to the triggered event is acquired, and the event data at least includes an event identifier; based on the event identifier, a preset callback function matching the event identifier is found, and the preset callback function includes the target entity data and the target address; based on the target entity data, content information corresponding to the entity attributes contained in the target entity data is obtained from one or more subsystems; and the content information is sent to the subsystem corresponding to the target address. This invention is mainly applied to realizing data interaction between subsystems within a business integration system.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a general method and system for data acquisition in a business integration system. Background Technology

[0002] Many modern large-scale information systems are formed by integrating multiple subsystems, which are often heterogeneous and require a large amount of data interaction between them.

[0003] Currently, designing customized solutions and implementing code for different integrated business scenarios typically begins with studying the data interaction of multiple subsystems and clarifying the business processes. Then, specific APIs are agreed upon and written within each subsystem, and the logical chain upon which the data is called is pre-written according to different business processes, thereby ensuring that data exchange can be successfully achieved through mutual calls.

[0004] However, pre-defining and writing specific APIs within each subsystem and pre-writing the logical chain upon which data is invoked according to different business processes usually requires pre-modification of the subsystems and incurs significant modification costs. Even if data interaction between different subsystems is successfully achieved, existing methods lack overall management of the entire data interaction operation, making it difficult to control the quality of the data interaction operation. Summary of the Invention

[0005] In view of this, the present invention provides a general method and system for data acquisition in a business integration system. The main purpose is that when a subsystem triggers a specified event, a data integration system can use a preset callback function to integrate relevant data from one or more subsystems and send it to another subsystem, thereby realizing data interaction between subsystems. This is not limited by business scenarios and does not require a lot of modification costs to the subsystems. The data integration system also facilitates effective control of the quality of data interaction.

[0006] To achieve the above objectives, the present invention mainly provides the following technical solutions:

[0007] The first aspect of this application provides a general method for data acquisition in a business integration system, the method comprising:

[0008] When a specified event is triggered on a subsystem, the event data corresponding to the specified event is obtained, and the event data includes at least an event identifier.

[0009] Based on the event identifier, a preset callback function matching the event identifier is found. The preset callback function contains the target entity data and the target address. The entity attributes contained in the target entity data are selected from the entity data pre-registered in different subsystems. The entity data pre-registered in each subsystem is used to describe the entity attributes of the data information stored in the subsystem. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function.

[0010] Based on the target entity data of the callback, obtain the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems;

[0011] The content information is sent to the subsystem corresponding to the target address.

[0012] In some modified embodiments of the first aspect of this application, the method further includes:

[0013] Obtain entity data corresponding to each subsystem. The entity data includes entity attributes that identify the primary key, other entity attributes, and interface addresses. The interface addresses are used to obtain the content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem.

[0014] If different entity data packets contain the same entity attribute, then an association relationship between the entity data packets is established based on the same entity attribute.

[0015] Perform a registration operation on the entity data and the relationships between the entity data.

[0016] In some modified embodiments of the first aspect of this application, before finding a preset callback function matching the event identifier based on the event identifier, the method further includes:

[0017] Set the event flag;

[0018] Based on the event identifier, one or more preset callback functions are pre-configured;

[0019] Establish a preset mapping relationship between the event identifier and the preset callback function.

[0020] In some modified embodiments of the first aspect of this application, the step of pre-configuring one or more callback functions based on the event identifier includes:

[0021] The system uses an interactive interface to push event identifiers and registered entity data to the user, wherein the registered entity data includes entity attributes.

[0022] Under different event identifiers, receive entity attributes selected by the user from the registered entity data, and establish a mapping relationship between the event identifier and the selected entity attribute;

[0023] The preset callback function is configured by filling the selected entity attributes into the preset callback function template and filling the preset target address into the preset callback function template.

[0024] Based on the mapping relationship between the event identifier and the selected entity attribute, the event identifier and the preset callback function are associated to obtain the preset callback function corresponding to the event identifier.

[0025] In some modified embodiments of the first aspect of this application, the step of finding a preset callback function that matches the event identifier includes:

[0026] When a specified event is triggered on a subsystem, the event identifier obtained from the event data corresponding to the specified event is used as the target event identifier;

[0027] The preset callback function corresponding to the target event identifier is determined by finding the preset mapping relationship between the event identifier and the preset callback function.

[0028] In some modified embodiments of the first aspect of this application, the step of obtaining content information corresponding to entity attributes contained in the target entity data from one or more subsystems based on the target entity data of the callback includes:

[0029] Retrieve the entity attributes contained in the target entity data;

[0030] By searching for entity data pre-registered in different subsystems, the target registered entity data to which the entity attribute belongs is determined;

[0031] Identify the target subsystem corresponding to the entity data that has been registered by the target;

[0032] Obtain the interface address from the registered entity data of the target;

[0033] Based on the interface address, obtain the content information corresponding to the entity attribute from the target subsystem.

[0034] A second aspect of this application provides a general data acquisition system for a business integration system, the system comprising:

[0035] The acquisition unit is used to acquire event data corresponding to the specified event when a specified event is triggered on a subsystem, wherein the event data includes at least an event identifier;

[0036] The lookup unit is used to find a preset callback function that matches the event identifier obtained by the acquisition unit. The preset callback function includes the target entity data and the target address. The entity attributes included in the target entity data are selected from the entity data pre-registered by different subsystems. The entity data pre-registered by each subsystem is used to describe the entity attributes of the data information stored in the subsystem. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function.

[0037] The acquisition unit is further configured to acquire, based on the target entity data of the callback, the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems;

[0038] The sending unit is used to send the content information acquired by the acquisition unit to the subsystem corresponding to the target address.

[0039] In some modified embodiments of the second aspect of this application, the system further includes:

[0040] The acquisition unit is further configured to acquire entity data corresponding to each subsystem. The entity data includes entity attributes identified as primary keys, other entity attributes, and interface addresses. The interface addresses are used to acquire content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem.

[0041] An establishment unit is used to establish an association relationship between entity data based on the same entity attribute if entity data packets obtained by different acquisition units contain the same entity attribute.

[0042] The registration unit is used to perform a registration operation on the relationship between the entity data acquired by the acquisition unit and the entity data established by the establishment unit.

[0043] In some modified embodiments of the second aspect of this application, the system includes:

[0044] The setting unit is used to set the event identifier;

[0045] A configuration unit is used to pre-configure one or more preset callback functions based on the event identifier;

[0046] The establishment unit is also used to establish a preset mapping relationship between the event identifier and the preset callback function.

[0047] In some modified embodiments of the second aspect of this application, the configuration unit includes:

[0048] The push module is used to push event identifiers and registered entity data to users through the interactive interface. The registered entity data includes entity attributes.

[0049] A module is established to establish a mapping relationship between the event identifier and the selected entity attribute by receiving the entity attribute selected by the user from the registered entity data under different event identifiers;

[0050] The configuration module is used to configure the preset callback function by filling the selected entity attributes into the preset callback function template and filling the preset target address into the preset callback function template.

[0051] The association module is used to establish an association between the event identifier and the preset callback function based on the mapping relationship between the event identifier and the selected entity attribute, so as to obtain the preset callback function corresponding to the event identifier.

[0052] In some modified embodiments of the second aspect of this application, the search unit includes:

[0053] The determination module is used to, when a specified event is triggered on a subsystem, obtain the event identifier from the event data corresponding to the specified event and use it as the target event identifier;

[0054] The acquisition module is also used to obtain the preset callback function corresponding to the target event identifier by finding the preset mapping relationship between the event identifier and the preset callback function.

[0055] In some modified embodiments of the second aspect of this application, the obtaining unit includes:

[0056] The acquisition module is used to obtain the entity attributes contained in the target entity data;

[0057] The determination module is used to determine the target registered entity data to which the entity attribute belongs by searching the entity data pre-registered in different subsystems;

[0058] The determining module is further configured to determine the target subsystem corresponding to the registered entity data of the target;

[0059] The acquisition module is also used to obtain the interface address from the target's registered entity data;

[0060] The acquisition module is further configured to acquire content information corresponding to the entity attribute from the target subsystem based on the interface address.

[0061] A third aspect of this application provides a storage medium comprising a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to perform the general data acquisition method of the business integration system described above.

[0062] A fourth aspect of this application provides an electronic device, the device including at least one processor, and at least one memory and bus connected to the processor;

[0063] The processor and the memory communicate with each other via the bus.

[0064] The processor is used to call program instructions in the memory to execute the general data acquisition method of the business integration system as described above.

[0065] By employing the above-described technical solution, the technical solution provided by the present invention has at least the following advantages:

[0066] This invention provides a general method and system for data acquisition in a business integration system. The invention pre-builds a data integration system. When a subsystem triggers a specified event within the business integration system, it obtains the event identifier corresponding to that event, which in turn triggers a pre-defined callback function. Based on the target entity data contained in the callback function, it retrieves the content information corresponding to the entity attributes of the target entity data from one or more subsystems and sends this content information to the subsystem corresponding to the target address pointed to by the callback function. Compared to existing technologies, this invention addresses the technical problems of significant subsystem modification costs and difficulty in controlling data interaction quality in business integration systems. It utilizes a data integration system with pre-defined callback functions to integrate relevant data from one or more subsystems and send it to another subsystem, thereby achieving data interaction between subsystems without being limited by business scenarios. The data interaction method provided by this invention is highly versatile, requires no significant subsystem modification costs, and facilitates effective control of data interaction quality.

[0067] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0068] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0069] Figure 1 A flowchart illustrating a general method for data acquisition in a business integration system, as provided in this embodiment of the invention;

[0070] Figure 2 A flowchart illustrating a general method for data acquisition in another business integration system provided in this embodiment of the invention;

[0071] Figure 3 This is a schematic diagram illustrating data interaction between a data integration system and its subsystems, as exemplified in an embodiment of the present invention.

[0072] Figure 4 A block diagram of a general data acquisition system for a business integration system provided in an embodiment of the present invention;

[0073] Figure 5 A block diagram of a general data acquisition system for another business integration system provided in this embodiment of the invention;

[0074] Figure 6 The present invention provides a general electronic device for data acquisition in a business integration system. Detailed Implementation

[0075] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0076] This invention provides a general method for data acquisition in a business integration system, such as... Figure 1 As shown, the execution entity of this method is a pre-built data integration system. When a subsystem triggers a specified event, the data integration system can use a pre-defined callback function to integrate relevant data from one or more subsystems and send it to another subsystem. The embodiments of this invention provide the following specific steps:

[0077] In this embodiment of the invention, a data integration system is pre-built, and data communication is established between the data integration system and the subsystems of the business integration system. The following steps 101-104 will explain in detail the general method for data acquisition of the business integration system implemented using the data integration system.

[0078] 101. When a specified event is triggered on a subsystem, obtain the event data corresponding to the event that triggered the specified event. The event data shall at least include the event identifier.

[0079] In this embodiment of the invention, the number of subsystems required in the business integration system and the functions of each subsystem vary depending on the specific business scenario. For example, a business integration system for an e-commerce business scenario may include a customer management subsystem, an online store management subsystem, and so on.

[0080] In this context, a designated event refers to an event that causes data exchange between different subsystems. Continuing with the example above, if a user places an order, the customer management subsystem will record the customer information corresponding to that event, and the online store management subsystem should maintain buyer information (i.e., customer information) based on that order. These two systems need to exchange designated customer information (i.e., buyer information). However, in this embodiment of the invention, the data exchange between subsystems is not performed directly but is achieved using a pre-built data integration system.

[0081] In this embodiment of the invention, a specified event can be triggered by an event trigger on a subsystem. The pre-built data integration system will obtain the event data of the specified event and further obtain the event identifier from the event data. For example, the event identifier of the user's order placement event is "place order".

[0082] 102. Based on the event identifier, find the preset callback function that matches the event identifier.

[0083] Among them, the preset callback function can be a user-defined HTTP callback function, such as a webhook. Webhooks are usually triggered by certain events. When an event is triggered, the system sends an HTTP request based on the URL configured by the user and the custom parameters. This allows the relevant data corresponding to the specified event in the current system to be sent to another system.

[0084] The preset callback function contains the target entity data and the target address of the callback. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function.

[0085] The target entity data in the preset callback function contains entity attributes selected from entity data pre-registered in different subsystems. This target entity data is the user-defined content that needs to be called back.

[0086] In this embodiment of the invention, each subsystem needs to pre-execute an operation to register entity data on the data integration system. This entity data is used to describe the entity attributes of the data information stored within the subsystem.

[0087] For example, in the customer management subsystem, its entity data is "customer information," which can contain multiple entity attributes such as "name," "phone number," and "address." In the online store management subsystem, its entity data is "online shopping information," which can contain multiple entity attributes such as "buyer's phone number," "buyer's address," "ordered items," and "order time." The entity data for each subsystem can be a relational database table, and different entity data (i.e., relational database tables) are related based on the same entity attributes. For instance, the "phone number" and "address" in the customer management subsystem's entity data are the same as the "buyer's phone number" and "buyer's address" in the online store management subsystem's entity data.

[0088] It's important to note that pre-registering entity data on the data integration system facilitates querying the entity attributes of different subsystems within the data integration system. However, the specific content information (attribute information) that these entity attributes represent does not need to be registered (i.e., not stored) on the data integration system. Instead, this content information is retrieved from the specified subsystem during subsequent operations using a pre-defined callback function. This design eliminates the need to store large amounts of data; instead, it registers only entity data. Consequently, even if data is updated on the subsystem side, as long as the entity attributes remain unchanged—meaning the entity attributes in the entity data registered on the data integration system side are consistent with those of the subsystem—the data updates on the subsystem side have no impact on the data integration system.

[0089] To further explain, in this embodiment of the invention, the entity attributes contained in the target entity data of the callback can be selected from entity data pre-registered in different subsystems. That is, depending on the specific business requirements achieved by triggering the specified event, the entity attributes contained in the target entity data of the callback can originate from the same subsystem or different subsystems.

[0090] In this embodiment of the invention, a preset mapping relationship between event identifiers and preset callback functions can be pre-defined. That is, one event identifier can correspond to one or more preset callback functions. According to different business needs, the preset callback function can be used to obtain the content information corresponding to the entity attribute from one or more subsystems and send it to the specified subsystem.

[0091] 103. Based on the target entity data of the callback, obtain the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems.

[0092] In this embodiment of the invention, since each subsystem registers entity data on the data integration system, rather than entity data containing content information (attribute information) corresponding to entity attributes, the target entity data to be called back according to the callback function contains entity attributes from one or more subsystems. Correspondingly, the data integration system operation also obtains the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems.

[0093] 104. Send the content information to the subsystem corresponding to the target address.

[0094] In this embodiment of the invention, after the data integration system obtains the content information of step 103, it sends the content information to the corresponding subsystem according to the target address in the preset callback function, thereby realizing that a data integration system can integrate relevant data from one or more subsystems and send it to another subsystem by using a preset callback function.

[0095] This invention provides a general method for data acquisition in a business integration system. The method involves pre-building a data integration system. When a subsystem triggers a specified event within the system, an event identifier corresponding to that event is obtained. This triggers a pre-defined callback function, which, based on the target entity data contained in the callback function, retrieves the content information corresponding to the entity attributes of the target entity from one or more subsystems. This content information is then sent to the subsystem corresponding to the target address pointed to by the callback function. Compared to existing technologies, this invention addresses the technical problems of significant subsystem modification costs and difficulty in controlling data interaction quality in business integration systems. It utilizes a data integration system with pre-defined callback functions to integrate relevant data from one or more subsystems and send it to another subsystem, thus achieving data interaction between subsystems. This method is not limited by business scenarios, has strong versatility, requires no significant subsystem modification costs, and facilitates effective control of data interaction quality.

[0096] To provide a more detailed explanation of the above embodiments, this invention also provides another general method for data acquisition in a business integration system, such as... Figure 2 As shown, the following specific steps are provided in this embodiment of the invention:

[0097] 201. Obtain the entity data corresponding to each subsystem. The entity data includes the entity attribute that identifies the primary key, other entity attributes, and the interface address. The interface address is used to obtain the content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem.

[0098] For entity data corresponding to a subsystem, the first step is to identify the entity itself. For example, the entity corresponding to the customer management subsystem is "customer," and the entity data is "customer information." The second step is to determine the entity attributes contained within this entity data. Specifically, the method for determining these entity attributes can be as follows: Use the original attribute fields of the data within the subsystem. Based on the attributes corresponding to these original attribute fields, determine the entity attributes contained within the entity data corresponding to the subsystem. Perform preprocessing (related operations) on the content information corresponding to the original attribute fields of the data within the subsystem. Based on the preprocessing results, add the corresponding attribute fields as entity attributes contained within the entity data corresponding to the subsystem.

[0099] For example, "Name" and "Phone Number" are original attribute fields within the subsystem, while "Number of Orders Corresponding to Purchase Category" is a newly defined attribute field derived from the data results obtained by retrieving multiple order records and performing data preprocessing. Specifically, based on business needs, the entity attributes contained within the entity data can be customized and maintained.

[0100] The interface address included in the entity data needs further explanation. Since the data integration system registers entity data rather than the content information corresponding to entity attributes (i.e., attribute information), in order to obtain the corresponding content information after the entity data is determined, the interface address corresponding to obtaining the entity data can also be registered during the registration operation. Specifically, an HTTP protocol REST API can be used for registration.

[0101] In this embodiment of the invention, each subsystem needs to pre-execute the operation of registering entity data on the data integration system. The specific operation process of obtaining entity data corresponding to a subsystem can be completed on the subsystem side or by using a third party to perform data preprocessing operations.

[0102] 202. If different entity data packets contain the same entity attributes, then establish the association relationship between the entity data based on the same entity attributes.

[0103] It should be noted that the entity data corresponding to each subsystem can be a relational database table. In this case, the entity data can be defined to include entity attributes that identify the primary key (entity primary key). Then, based on the entity primary key and the fact that different entity data contain the same entity attributes, the relationship between the entity data corresponding to different subsystems can be established.

[0104] 203. Perform a registration operation on entity data and the relationships between entity data.

[0105] In this embodiment of the invention, the entity data registration operation is performed on the data integration system side. The registration content includes: entity data corresponding to the subsystem, the association between different entity data, and the interface address required to obtain entity data.

[0106] 204. When a specified event is triggered on a subsystem, obtain the event data corresponding to the event that triggered the specified event. The event data shall at least include the event identifier.

[0107] In this embodiment of the invention, for an explanation of this step, please refer to step 101, which will not be repeated here.

[0108] 205. Based on the event identifier, find the preset callback function that matches the event identifier.

[0109] The preset callback function contains the target entity data and the target address. The entity attributes included in the target entity data are selected from the entity data pre-registered by different subsystems. The entity data pre-registered by each subsystem describes the entity attributes of the data information stored within that subsystem. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function. For a detailed explanation, please refer to step 102; it will not be repeated here.

[0110] It should be noted that before the business integration system executes specific business operations, that is, after the data integration system completes entity data registration, some data configuration work is still required in the data integration system. Since the specific requirements for triggering callback operations vary depending on business needs, in order to meet different callback operation requirements, multiple callback functions can be pre-set on the data integration system side and stored in a list. A preset mapping relationship between different events and the pre-set callback functions can also be configured. Specific operations may include the following:

[0111] First, set an event identifier, and pre-configure one or more pre-defined callback functions based on this identifier. Specifically, the event identifier and registered entity data can be pushed to the user through an interactive interface. This registered entity data includes entity attributes. For example, using the UI components provided by the framework, the user can arbitrarily select any entity attribute contained in the registered entity data. This selection operation is a human-computer interaction operation. Then, by receiving user feedback, the data integration system obtains the entity attribute selected under this event identifier, thereby establishing a pre-defined mapping relationship between the event identifier and the entity attribute.

[0112] Secondly, a preset callback function template is populated using the selected entity attributes. This preset callback function template is a user-defined HTTP callback function, such as a webhook. Webhooks are usually triggered by certain events. When an event is triggered, the system sends an HTTP request based on the URL configured by the user and the custom parameters. This allows the relevant data corresponding to the specified event occurring in the current system to be sent to another system.

[0113] Furthermore, based on business needs, a preset target address is filled into the preset callback function template, which then points to the subsystem pointed to by the callback content.

[0114] The above steps involve filling the selected entity attributes into the preset callback function template and filling the preset target address into the preset callback function template to complete the configuration of the preset callback function.

[0115] Finally, based on the mapping relationship between the event identifier and the selected entity attribute, it is possible to establish an association between the event identifier and the configured preset callback function, thus completing the configuration of the preset callback function corresponding to an event.

[0116] In this embodiment of the invention, according to the specific implementation method of configuring callback functions described above, multiple callback functions can be configured for one event identifier to meet different business needs.

[0117] In this embodiment of the invention, when a specified event is triggered on a subsystem, the event identifier obtained from the event data corresponding to the specified event is used as the target event identifier.

[0118] By finding the preset mapping relationship between event identifiers and callback functions, the preset callback function corresponding to the target event identifier can be determined.

[0119] 206. Based on the target entity data of the callback, obtain the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems.

[0120] In this embodiment of the invention, a more detailed description of this step may include the following:

[0121] First, obtain the entity attributes contained in the target entity data. As can be seen from the configuration callback function steps, since the entity attributes filled in the callback function can come from one or more subsystems, the corresponding interface address of the entity data registered on the data integration system is used to find the corresponding content information (attribute information) of the entity attributes from the corresponding subsystem.

[0122] 207. Send the content information to the subsystem corresponding to the target address.

[0123] In this embodiment of the invention, after the data integration system obtains the content information of step 206, it sends the content information to the corresponding subsystem according to the target address in the preset callback function, thereby realizing that a data integration system can integrate relevant data from one or more subsystems and send it to another subsystem by using a preset callback function.

[0124] In embodiments of the present invention, using, for example Figure 3 The data integration system shown presents a general guideline and framework for data exchange, making it adaptable to most business scenarios. This approach is independent of specific business scenarios and data types; most business integration systems implementing the HTTP protocol can achieve data exchange between different subsystems through simple configuration and webhooks.

[0125] It should be further noted that the data integration system provided in this embodiment of the invention does not need to concern itself with specific business requirements and can be applied to any scenario. Once a stable version is released, no modifications are required. Employing a loosely coupled integration scheme based on entity attribute mapping, different subsystems can achieve data integration without changing the current data structure by registering entity data and the relationships between them. The event-triggered and HTTP callback mechanism conforms to the technical architecture of most current systems, and in most cases, integration development can be completed without introducing additional technical frameworks and components. Furthermore, due to different business needs, multiple new subsystems can be integrated, allowing for dynamic expansion of new entities without altering the existing system structure.

[0126] Furthermore, as a response to the above Figure 1 , Figure 2 The implementation of the method shown in this embodiment of the invention provides a general data acquisition system for a business integration system. This system embodiment corresponds to the foregoing method embodiments. For ease of reading, this system embodiment will not repeat the details of the foregoing method embodiments, but it should be understood that the system in this embodiment can implement all the contents of the foregoing method embodiments. This system is used to realize data interaction between subsystems within a business integration system, specifically as follows... Figure 4 As shown, the device includes:

[0127] The acquisition unit 31 is used to acquire event data corresponding to the specified event when a specified event is triggered on a subsystem, wherein the event data includes at least an event identifier;

[0128] The lookup unit 32 is used to look up a preset callback function that matches the event identifier obtained by the acquisition unit 31. The preset callback function includes the target entity data and the target address. The entity attributes included in the target entity data are selected from the entity data pre-registered by different subsystems. The entity data pre-registered by each subsystem is used to describe the entity attributes of the data information stored in the subsystem. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function.

[0129] The acquisition unit 31 is further configured to acquire, based on the target entity data of the callback, the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems;

[0130] The sending unit 33 is used to send the content information acquired by the acquisition unit 31 to the subsystem corresponding to the target address.

[0131] Furthermore, such as Figure 5 As shown, the system also includes:

[0132] The acquisition unit 31 is also used to acquire entity data corresponding to each subsystem. The entity data includes entity attributes identified as primary keys, other entity attributes, and interface addresses. The interface addresses are used to acquire content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem.

[0133] Establishment unit 34 is used to establish an association relationship between entity data based on the same entity attribute if entity data packets obtained by different acquisition units 31 have the same entity attribute.

[0134] The registration unit 35 is used to perform a registration operation on the relationship between the entity data acquired by the acquisition unit 31 and the entity data established by the establishment unit 34.

[0135] Furthermore, such as Figure 5 As shown, the system includes:

[0136] Setting unit 36 ​​is used to set event identifiers;

[0137] Configuration unit 37 is configured to pre-configure one or more preset callback functions based on the event identifier;

[0138] The establishment unit 34 is also used to establish a preset mapping relationship between the event identifier and the preset callback function.

[0139] Furthermore, such as Figure 5 As shown, configuration unit 37 includes:

[0140] The push module 371 is used to push event identifiers and registered entity data to the user through the interactive interface, wherein the registered entity data includes entity attributes.

[0141] Module 372 is configured to establish a mapping relationship between the event identifier and the selected entity attribute by receiving the entity attribute selected by the user from the registered entity data under different event identifiers.

[0142] Configuration module 373 is used to configure a preset callback function by filling the selected entity attributes into a preset callback function template and filling the preset target address into the preset callback function template.

[0143] The association module 374 is used to establish an association between the event identifier and the preset callback function based on the mapping relationship between the event identifier and the selected entity attribute, so as to obtain the preset callback function corresponding to the event identifier.

[0144] Furthermore, such as Figure 5 As shown, the search unit 32 includes:

[0145] The determination module 321 is used to, when a specified event is triggered on a subsystem, obtain an event identifier from the event data corresponding to the specified event and use it as a target event identifier;

[0146] The acquisition module 322 is also used to acquire the preset callback function corresponding to the target event identifier by finding the preset mapping relationship between the event identifier and the preset callback function.

[0147] Furthermore, such as Figure 5 As shown, the acquisition unit 31 includes:

[0148] The acquisition module 311 is used to acquire the entity attributes contained in the target entity data;

[0149] The determination module 312 is used to determine the target registered entity data to which the entity attribute belongs by searching the entity data pre-registered in different subsystems;

[0150] The determining module 312 is further configured to determine the target subsystem corresponding to the registered entity data of the target;

[0151] The acquisition module 311 is further configured to acquire the interface address from the target registered entity data;

[0152] The acquisition module 311 is further configured to acquire the content information corresponding to the entity attribute from the target subsystem based on the interface address.

[0153] In summary, this invention provides a general method and system for data acquisition in a business integration system. This invention pre-builds a data integration system. When a subsystem triggers a specified event within the business integration system, it obtains the event identifier corresponding to that event, thereby triggering a pre-defined callback function. Based on the target entity data contained in the callback function, it retrieves the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems and sends this content information to the subsystem corresponding to the target address pointed to by the callback function. Compared to existing technologies, this invention addresses the technical problems of significant subsystem modification costs and difficulty in controlling data interaction quality in business integration systems. It utilizes a data integration system with pre-defined callback functions to integrate relevant data from one or more subsystems and send it to another subsystem, thus achieving data interaction between subsystems without being limited by business scenarios. The data interaction method provided by this invention is highly versatile, requires no significant subsystem modification costs, and facilitates effective control of data interaction quality.

[0154] The general data acquisition system of the business integration system includes a processor and a memory. The acquisition unit, search unit and sending unit mentioned above are all stored as program units in the memory. The processor executes the program units stored in the memory to realize the corresponding functions.

[0155] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured. By adjusting kernel parameters, when a subsystem triggers a specified event, a data integration system can use preset callback functions to integrate relevant data from one or more subsystems and send it to another subsystem. This enables data interaction between subsystems, regardless of business scenarios, without requiring significant modifications to subsystems. Furthermore, this data integration system facilitates effective control over the quality of data interaction.

[0156] This invention provides a storage medium storing a program that, when executed by a processor, implements a general method for data acquisition in the business integration system.

[0157] This invention provides a processor for running a program, wherein the program executes a general data acquisition method for the business integration system during runtime.

[0158] This invention provides an electronic device 40, such as... Figure 6As shown, the device includes at least one processor 401, and at least one memory 402 and bus 403 connected to the processor 401; wherein the processor 401 and the memory 402 communicate with each other through the bus 403; the processor 401 is used to call program instructions in the memory 402 to execute the above-mentioned general method for data acquisition of the business integration system.

[0159] The devices mentioned in this article can be servers, PCs, tablets, mobile phones, etc.

[0160] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the following method steps:

[0161] A general method for data acquisition in a business integration system includes: when a specified event is triggered on a subsystem, acquiring event data corresponding to the specified event, the event data including at least an event identifier; based on the event identifier, searching for a preset callback function matching the event identifier, the preset callback function including target entity data and a target address, the entity attributes included in the target entity data being selected from entity data pre-registered in different subsystems, each pre-registered entity data being entity attributes used to describe data information stored within the subsystem, the target address referring to the address of the subsystem to which the data information is transmitted using the preset callback function; based on the target entity data of the callback, acquiring content information corresponding to the entity attributes included in the target entity data from one or more subsystems; and sending the content information to the subsystem corresponding to the target address.

[0162] Furthermore, the method also includes: obtaining entity data corresponding to each subsystem, wherein the entity data includes an entity attribute identified as a primary key, other entity attributes, and an interface address, wherein the interface address is used to obtain content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem; if different entity data packages contain the same entity attribute, then establish an association relationship between the entity data based on the same entity attribute; and perform a registration operation on the entity data and the association relationship between the entity data.

[0163] Furthermore, before finding a preset callback function that matches the event identifier, the method further includes: setting an event identifier; pre-configuring one or more preset callback functions based on the event identifier; and establishing a preset mapping relationship between the event identifier and the preset callback functions.

[0164] Furthermore, the step of pre-configuring one or more preset callback functions based on the event identifier includes: pushing the event identifier and registered entity data to the user through an interactive interface, wherein the registered entity data includes entity attributes; establishing a mapping relationship between the event identifier and the selected entity attribute by receiving the entity attribute selected by the user from the registered entity data under different event identifiers; configuring the preset callback function by filling the selected entity attribute into a preset callback function template and filling the preset callback function template with a preset target address; and associating the event identifier with the preset callback function based on the mapping relationship between the event identifier and the selected entity attribute to obtain the preset callback function corresponding to the event identifier.

[0165] Furthermore, the step of finding a preset callback function that matches the event identifier includes: when a specified event is triggered on a subsystem, obtaining the event identifier from the event data corresponding to the specified event as the target event identifier; and determining the preset callback function corresponding to the target event identifier by finding a preset mapping relationship between the event identifier and the preset callback function.

[0166] Furthermore, the step of obtaining the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems based on the target entity data of the callback includes: obtaining the entity attributes contained in the target entity data; determining the target registered entity data to which the entity attribute belongs by searching for entity data pre-registered in different subsystems; determining the target subsystem corresponding to the target registered entity data; obtaining the interface address from the target registered entity data; and obtaining the content information corresponding to the entity attribute from the target subsystem based on the interface address.

[0167] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0168] In a typical configuration, the device includes one or more processors (CPUs), memory, and a bus. The device may also include input / output interfaces, network interfaces, etc.

[0169] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and memory includes at least one memory chip. Memory is an example of computer-readable media.

[0170] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0171] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0172] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0173] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A general method for data acquisition in a business integration system, characterized in that, The method includes: Obtain entity data corresponding to each subsystem. The entity data includes entity attributes that identify the primary key, other entity attributes, and interface addresses. The interface addresses are used to obtain the content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem. If different entity data packets contain the same entity attribute, then an association relationship between the entity data packets is established based on the same entity attribute. Perform a registration operation on the entity data and the relationships between the entity data; Set an event identifier; pre-configure one or more preset callback functions based on the event identifier; establish a preset mapping relationship between the event identifier and the preset callback functions; When a specified event is triggered on a subsystem, the event data corresponding to the specified event is obtained, and the event data includes at least an event identifier. Based on the event identifier, a preset callback function matching the event identifier is found. The preset callback function contains the target entity data and the target address. The entity attributes contained in the target entity data are selected from the entity data pre-registered in different subsystems. The entity data pre-registered in each subsystem is used to describe the entity attributes of the data information stored in the subsystem. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function. Based on the target entity data of the callback, obtain the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems; The content information is sent to the subsystem corresponding to the target address.

2. The method according to claim 1, characterized in that, The step of pre-configuring one or more preset callback functions based on the event identifier includes: The system uses an interactive interface to push event identifiers and registered entity data to the user, wherein the registered entity data includes entity attributes. Under different event identifiers, by receiving entity attributes selected by the user from the registered entity data, a mapping relationship is established between the event identifier and the selected entity attribute; The preset callback function is configured by filling the selected entity attributes into the preset callback function template and filling the preset target address into the preset callback function template. Based on the mapping relationship between the event identifier and the selected entity attribute, the event identifier and the preset callback function are associated to obtain the preset callback function corresponding to the event identifier.

3. The method according to claim 1, characterized in that, The step of finding a preset callback function that matches the event identifier includes: When a specified event is triggered on a subsystem, the event identifier obtained from the event data corresponding to the specified event is used as the target event identifier; The preset callback function corresponding to the target event identifier is determined by finding the preset mapping relationship between the event identifier and the preset callback function.

4. The method according to claim 1, characterized in that, The step of obtaining content information corresponding to entity attributes contained in the target entity data from one or more subsystems based on the target entity data of the callback includes: Retrieve the entity attributes contained in the target entity data; By searching the entity data pre-registered in different subsystems, the target registered entity data to which the entity attribute belongs is determined; Identify the target subsystem corresponding to the entity data that has been registered by the target; Obtain the interface address from the registered entity data of the target; Based on the interface address, obtain the content information corresponding to the entity attribute from the target subsystem.

5. A general data acquisition system for a business integration system, characterized in that, The system includes: The acquisition unit is used to acquire entity data corresponding to each subsystem. The entity data includes entity attributes that identify the primary key, other entity attributes, and interface addresses. The interface addresses are used to acquire the content information corresponding to the entity attributes contained in the entity data from the corresponding subsystem. An establishment unit is used to establish an association relationship between entity data based on the same entity attribute if entity data packets obtained by different acquisition units contain the same entity attribute. The registration unit is used to perform a registration operation on the relationship between the entity data acquired by the acquisition unit and the entity data established by the establishment unit. The setting unit is used to set the event identifier; A configuration unit is used to pre-configure one or more preset callback functions based on the event identifier; The establishment unit is also used to establish a preset mapping relationship between the event identifier and the preset callback function; The acquisition unit is further configured to acquire event data corresponding to the specified event when a specified event is triggered on a subsystem, wherein the event data includes at least an event identifier; The lookup unit is used to find a preset callback function that matches the event identifier obtained by the acquisition unit. The preset callback function includes the target entity data and the target address. The entity attributes included in the target entity data are selected from the entity data pre-registered by different subsystems. The entity data pre-registered by each subsystem is used to describe the entity attributes of the data information stored in the subsystem. The target address refers to the address of the subsystem to which the data information is transmitted using the preset callback function. The acquisition unit is further configured to acquire, based on the target entity data of the callback, the content information corresponding to the entity attributes contained in the target entity data from one or more subsystems; The sending unit is used to send the content information acquired by the acquisition unit to the subsystem corresponding to the target address.

6. A storage medium, characterized in that, The storage medium includes a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to execute the general data acquisition method of the business integration system as described in any one of claims 1-4.

7. An electronic device, characterized in that, The device includes at least one processor, and at least one memory and bus connected to the processor; The processor and the memory communicate with each other via the bus. The processor is used to invoke program instructions in the memory to execute the general data acquisition method of the business integration system as described in any one of claims 1-4.

Images