CN115082038A

CN115082038A - System integration method and device and electronic equipment

Info

Publication number: CN115082038A
Application number: CN202210825385.XA
Authority: CN
Inventors: 蒋金鑫; 王健; 刘发宾; 李飞; 李向东; 刘朝勇; 戴郑雄
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2022-07-14
Filing date: 2022-07-14
Publication date: 2022-09-20
Also published as: WO2024012567A1

Abstract

The present disclosure provides a system integration method, an apparatus and an electronic device, wherein a specific implementation manner of the method includes: acquiring first service data updated by a target service system; converting the first service data into first target data adapted to the unified service system according to a preset rule; the unified service system is used for providing a service processing interface so as to perform service processing on the first target data. According to the embodiment, on the premise that the target service system to be integrated is not required to be transformed in a large scale, the target service system and the unified service system are integrated to a certain degree based on user requirements, service processing in the unified service system is facilitated, and the integration effect is improved.

Description

System integration method and device and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a system integration method and apparatus, and an electronic device.

Background

At present, various enterprise-oriented business management systems are widely applied to various industries, and provide more convenience for business management of enterprises. For different services, enterprises usually adopt different service management systems. The user needs to spend time constantly switching different service systems to check and process the services of different systems, the operation is complicated and time is wasted, and omission is easily caused, so that some services cannot be processed in time, and the management efficiency of enterprises is influenced.

Disclosure of Invention

The disclosure provides a system integration method and device and electronic equipment.

According to a first aspect, there is provided a system integration method, the method comprising:

acquiring first service data updated by a target service system;

converting the first service data into first target data adapted to the unified service system according to a preset rule; the unified service system is used for providing a service processing interface so as to perform service processing on the first target data.

According to a second aspect, there is provided a system integration apparatus, the apparatus comprising:

the acquisition module is used for acquiring first service data updated by a target service system;

the adaptation module is used for converting the first service data into first target data adapted to the unified service system according to a preset rule; the unified service system is used for providing a service processing interface so as to perform service processing on the first target data.

According to a third aspect, there is provided a computer readable storage medium, storing a computer program which, when executed by a processor, implements the method of any of the first aspects above.

According to a fourth aspect, there is provided an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of the first aspects when executing the program.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:

according to the system integration method and device provided by the embodiment of the disclosure, the service data updated by the target service system to be integrated is obtained, and the service data is converted into the first target data adapted to the unified service system according to the preset rule, so that the service processing is performed in the unified service system based on the first target data, and therefore, on the premise that the target service system to be integrated is not required to be greatly modified, the target service system and the unified service system are integrated to a certain extent based on user requirements, the service processing is performed in the unified service system conveniently, and the integration effect is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and it is obvious for a person skilled in the art to obtain other drawings based on these drawings without inventive labor.

FIG. 1 is an illustration of an interaction scenario between a user and different approval service management systems according to an exemplary embodiment of the present disclosure;

FIG. 2 is an illustration of another scenario of interaction between a user and a different approval business management system, in accordance with an exemplary embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a system integration scenario shown in accordance with an exemplary embodiment of the present disclosure;

FIG. 4 is an interaction flow diagram illustrating a system integration method according to an exemplary embodiment of the present disclosure;

FIG. 5 is an interaction flow diagram illustrating another system integration method in accordance with an exemplary embodiment of the present disclosure;

FIG. 6 is a block diagram illustrating a system integration apparatus according to an exemplary embodiment of the present disclosure;

fig. 7 is a schematic block diagram of an electronic device provided by some embodiments of the present disclosure;

FIG. 8 is a schematic block diagram of another electronic device provided by some embodiments of the present disclosure;

fig. 9 is a schematic diagram of a storage medium provided by some embodiments of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.

When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this disclosure and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

At present, various enterprise-oriented business management systems are widely applied to various industries, and provide more convenience for business management of enterprises. The enterprise-oriented service management system may include a local management system deployed in a local area of the enterprise and a platform management system (e.g., a SaaS system) provided by a network platform.

For different services, enterprises generally adopt different service management systems. Taking an approval service as an example, fig. 1 shows an interaction scenario between a user and different approval service management systems, for example, an enterprise may manage a project approval service by using a project approval system, manage an attendance approval service by using an attendance approval system, manage a contract approval service by using a contract approval system, and the like. The project approval system, the attendance approval system and the contract approval system all belong to different approval business management systems. As shown in fig. 1, a user needs to spend time to constantly switch different approval service management systems to check and process the approval of different systems, which is tedious in operation and time-consuming, and is easy to miss, so that some approval services cannot be processed in time, and the management efficiency of an enterprise is affected.

Also taking the above approval service as an example, fig. 2 shows another interaction scenario between the user and different approval service management systems, as shown in fig. 2, the respective service data of the project approval system, the attendance approval system, and the contract approval system are integrated into a unified service system provided by, for example, a network platform. The user can check and process the approval services of different systems directly through the unified service system without spending time to continuously switch different approval service management systems, so that the management efficiency of the approval services is improved.

In the related art, generally, a service system to be integrated is modified to provide a better open interface, so that service data of the service system to be integrated is integrated into a unified service system. But the modification of the system also consumes a lot of resources and the integration effect is not ideal. Therefore, a scheme is needed for efficiently integrating the service system to be integrated with the unified service system to a certain extent based on user requirements, and facilitating service processing in the unified service system.

According to the system integration method, the service data updated by the target service system to be integrated is obtained, the service data is converted into the target data adaptive to the unified service system according to the preset rule, so that the service processing is performed in the unified service system based on the target data, the target service system and the unified service system are integrated to a certain extent based on user requirements on the premise of not modifying the target service system to be integrated, the service processing is performed in the unified service system conveniently, and the integration effect is improved.

Referring to fig. 3, a schematic diagram of a system integration scheme is shown in accordance with an exemplary embodiment.

The system integration scheme can be applied to a total business management system, and the total business management system can comprise a plurality of target business systems to be integrated. Wherein, each target service system is at least provided with an acquisition module, or an acquisition module and an adaptation module. The collection module may be, for example, a collector as a separate application program, and the adaptation module may be, for example, a service plug-in as a separate application program.

The acquisition module can acquire first service data updated by a target service system, the adaptation module can convert the first service data acquired by the acquisition module into first target data adapted to the unified service system according to a preset rule, and transmit the first target data or a first data update instruction generated based on the first target data to the unified service system, and the unified service system provides a service processing interface to perform service processing based on the first target data. The unified business system can be used for processing business data of a plurality of different target business systems.

Specifically, taking the project approval business as an example, as shown in fig. 3, for example, an enterprise manages the project approval business by using the project approval system, manages the attendance approval business by using the attendance approval system, and manages the contract approval business by using the contract approval system. A server of the local approval system (hereinafter referred to as a local server) is deployed in a local server/server cluster of an enterprise, and the local server includes a server of the project approval system, a server of the attendance approval system, and a server of the contract approval system.

For the project approval system, a connector 1 is installed in the local server, and the connector 1 may include a collector 1, a business plug-in 1 and a reconciliation device 1. For the attendance checking and approving system, a connector 2 is installed in the local server, and the connector 2 can comprise a collector 2, a business plug-in 2 and a reconciliation device 2. For the contract approval system, a connector 3 is installed in the local server, and the connector 3 may include a collector 3, a business plug-in 3 and a reconciliation machine 3. The collector, the business plug-in and the account checking device included in each connector can be independent application programs.

The following describes a process of processing approval business data by taking a project approval system as an example. Firstly, a user can perform operation of project approval business through a client of the project approval system, for example, submitting approval requirements, so as to update business data of a service end of the project approval system. Every time interval T1, collector 1 can request to obtain the service data A of the preset field updated in the time interval T1 from the database of the project approval system server.

Then, the collector 1 transmits the obtained service data a to the service plug-in 1, and the service plug-in 1 can convert the service data a into service data a adapted to the unified service system according to a rule set to the project approval system based on the unified service system in advance. The service plug-in 1 transmits the service data a or a first data updating indication generated based on the service data a to a service end of the unified service system so as to update a database of the service end of the unified service system. And the project approval service data in the project approval system and the project approval service data in the unified service system are kept synchronous.

In addition, optionally, every time interval T2, the reconciliation unit 1 may request, from the project approval system server, to acquire the update information B of the business data updated by the project approval system in the time interval T2, for example, the update information B may include, but is not limited to, identification information and update time of the business data updated in the time interval T2. The account checking device 1 may send a check request to the server of the unified service system to request the server of the unified service system to check whether the data of the unified service system and the data of the project approval system are synchronous according to the update information B. And if the data are determined to be synchronous, the verification is successful, and if the data are determined to be asynchronous, the verification is failed. The result of the verification success or failure is then returned by the unified business system to the ledger 1.

In case of a failure of the verification, the reconciliation machine 1 may send a synchronization request to the collector 1, and the collector 1 obtains the service data E of the preset field updated in the time period T2 from the database of the project approval system in response to the synchronization request. And transmitting the service data E to the service plug-in 1 for conversion to obtain target data E adapted to the unified service system, and transmitting the target data E or a second data updating indication generated based on the target data E to a server of the unified service system to indicate the server of the unified service system to update data in a database by using the target data E or the second data updating indication, so that project approval data in the project approval system and project approval data in the unified service system are synchronous.

Similarly, the management process of the examination and approval business data of the attendance examination and approval system and the contract examination and approval system is similar to that of the project examination and approval system, and is not described herein again. It is noted that in some embodiments, the time period T1 may be much smaller than the time period T2, the time period T1 may be, for example, several seconds or milliseconds, the time period T2 may be, for example, several hours or days, etc. By setting the time period T1, the service requirements of each target service system can be processed in time by the unified service system, and by setting the time period T2, the data synchronization condition between the unified service system and each target service system can be verified, thereby improving the system stability, and meanwhile, because T1 is less than T2, and in some embodiments, the time period T2 can be set to be much greater than T1, for example, T2 is greater than 50 times of T1, even 500 times, thereby further reducing the system load and improving the performance.

As can be seen from the foregoing embodiments, the unified service system may centrally manage part of the service data of each local approval system based on part of the service data information of each local approval system, for example, updated service data identifier, updated time information, and the like, and process the corresponding service requirements. The user can check the approval information of each local approval system through the client side of the unified service system, and the client side of the unified service system can also display the approval information of each local approval system to the user, and push the approval information of each local approval system and the like. For example, a user can check a project approval task, an attendance approval task and a contract approval task through a client of the unified business system. The client of the unified service system can also push the tasks to be handled of each local approval system to the user, and can remind the user at regular time. Therefore, on the premise that each local approval business system to be integrated is not required to be greatly transformed, the local approval system and the unified business system are integrated to a certain extent based on user requirements, approval business processing in the unified business system is facilitated, and the integration effect is improved.

The present disclosure will be described in detail with reference to specific examples.

FIG. 4 is an interaction flow diagram illustrating a system integration method in accordance with an exemplary embodiment. The embodiment relates to a server of a target business system, a connector and a server of a unified business system. The target business system is a business system to be integrated, and may be, for example, a local business system deployed locally in an enterprise. The connector is an application deployed for the target business system. The unified business system may be, for example, a cloud-based business management system such as a SaaS system provided by a network platform, and the unified business system may be used to manage business data from a plurality of different target business systems. The service related to the embodiment may be various services that are completed by multi-party interaction, for example, may be an approval service. The method may comprise the steps of:

as shown in fig. 4, in step 401, the connector acquires the first service data updated by the target service system.

In this embodiment, the connector requests, based on the preset field, to acquire part of service data updated by the target service system from the server of the target service system, as the first service data. In one implementation, the connector starts a timed task and detects a signal that the timed task starts. When a signal for starting the timing task is detected, a target time for starting the timing task last time is obtained, and then service data corresponding to a preset field is obtained from service data updated in a target service system from the target time to the current time and is used as first service data. For example, the connector starts a timer, detects a signal of the start of the timing task at time t1, and acquires a pre-recorded timestamp t2 of the last data acquisition (i.e., time t2 of the start of the last timing task). Then, the connector may send a data acquisition request to the server of the target service system, requesting to acquire service data of a preset field updated in the target service system from time t2 to time t1 as the first service data. For example, the preset fields may include, but are not limited to, a field indicating a service status, a field indicating a service identification, a field indicating a service node, a field indicating a service update, etc. And the time t1 is recorded as the time stamp of the data acquisition for the next data acquisition.

In another implementation, the connector may further detect (e.g., detect, through a subscription mechanism), an update condition of the service data in the target service system, and after the service data in the target service system is updated, the connector may send a data acquisition request to a server of the target service system, requesting to acquire the updated first service data in the preset field.

In step 402, the connector converts the acquired first service data into first target data adapted to the unified service system according to a preset rule.

The preset rule may be a conversion rule preset for the local service system based on the unified service system. Specifically, data adapted to the business system corresponds to a plurality of fields, and includes field values and the like corresponding to the respective fields. For example, the field names or field values of the same fields included in the data adapted to the target business system and the data adapted to the unified business system may be partially different. A conversion rule may be preset, and then field values of preset fields corresponding to the acquired first service data are added to target fields adapted to the unified service system according to the conversion rule, so as to be converted into the first target data.

For example, the case where the field names of the same field are different is: in the preset rule, data adapted to the target service system includes one field with a field name of Remark, and data adapted to the unified service system includes the same field with a field name of status. If the field value of the field with the field name of Remark in the first service data acquired by the connector is m, the field value m can be added under the status field of the target data according to a preset rule.

For another example, the case where the field values of the same field are different is: in the preset rule, when the field value of the field with the field name F in the data adapted to the target service system is w, the field value adapted to the unified service system should be u correspondingly, that is, when the value of the field with the field name F is the same as that of the field, for the same field, the value of the field in the target service system may be different from that in the unified service system, for example, when the value of the approval state field in the target service system is w, the first-level approval is passed, and when the value of the field in the unified service system is u, the first-level approval is passed. If the field value with the field name F in the first service data acquired by the connector is w, the field value u may be added under the F field of the first target data according to a preset rule. The technical solutions in the case where the field values of the same field are different may be used in combination with the technical solutions in the case where the field names of the same field are different.

In step 403, the connector transmits the first target data to the server of the unified business system, and in step 404, the server of the unified business system updates data in the database of the unified business system with the first target data.

According to the system integration method, the service data updated by the target service system to be integrated is obtained, and the service data is converted into the target data adaptive to the unified service system according to the preset rule, so that the service processing is performed in the unified service system based on the target data, and therefore, the target service system and the unified service system are integrated to a certain extent based on user requirements on the premise that the target service system to be integrated is not required to be greatly improved, the service processing is performed in the unified service system conveniently, and the integration effect is improved.

Optionally, at intervals, the connector may instruct the server side of the unified service system to perform data verification on the data in the database, and receive a verification result returned by the server side of the unified service system. If the verification result indicates that the verification fails, the indication information for updating the data can be sent to the unified service system.

Specifically, in one implementation manner, the connector may obtain, from the target service system, service data D1 updated in a previous preset time period, then convert the obtained service data D1 to obtain data D2, and send the data D2 to the service end of the unified service system. The server of the unified service system searches whether the data updated in the previous preset time period is consistent with the received data D2 from the database. If the two are consistent, the verification is successful, and if the two are not consistent, the verification fails. If the check fails, the connector instructs the server of the unified service system to update the data in the database with data D2.

In another implementation manner, the connector may obtain, every preset time period, update information of the target service system that updates the service data in the preset time period. And sending a verification request carrying the update information to the server of the unified service system to indicate the server of the unified service system to perform data based on the update information, where the specific process may refer to the embodiment of fig. 5 in detail.

FIG. 5 is an interactive flow diagram illustrating another system integration method, according to an exemplary embodiment, which describes a process for data verification for a unified business system, comprising the steps of:

as shown in fig. 5, in step 501, the connector acquires update information that the target service system updates the service data within a preset time period. The update information may be information related to the updated service data, and the update information may include, but is not limited to, identification information of the updated service data, update time information, and the like. For example, in a preset time period, the user creates the approval task S1 and the process approval task S2 through the target business system, and the update information may include an ID of the approval task S1, a creation time of the approval task S1, an ID of the approval task S2, a processing time of the approval task S2, and the like.

Specifically, in this embodiment, the connector may send an update information acquisition request to the server of the target service system every preset time interval, and the server of the target service system acquires, in response to the update information acquisition request, update information of the update data in the preset time interval from the database, and returns the update information to the connector.

In step 502, the connector sends a verification request carrying the update information to the server of the unified service system to instruct the server of the unified service system to perform data verification based on the update information. And the server side of the unified service system responds to the received verification request, determines whether the data of the unified service system and the data of the target service system are synchronous or not based on the updating information so as to verify the data, and returns the verification result to the connector. Optionally, if the verification fails, the verification result may further include identification information of the unsynchronized data.

For example, the server of the unified service system may search the identifier information included in the update information from the database, and if the identifier information is not found, it indicates that the data of the unified service system and the data of the target service system are not synchronized, and the verification fails. If the identification information is found, the updating time corresponding to the identification information is further obtained from the database, and if the updating time corresponding to the identification information in the database is consistent with the updating time included in the updating information, the data synchronization between the unified service system and the target service system can be determined, and the verification is successful. If the updating time is not consistent, the verification fails. If the verification fails, the server side of the unified service system may return a verification result to the connector, where the verification result may include identification information of the unsynchronized data. For example, the identification information of the unsynchronized data may be identification information that is not found from the database or identification information corresponding to inconsistent update times.

In step 503, the connector receives the verification result, and if the verification fails, the connector may send a request to the server of the target service system to obtain the second service data updated within the preset time period. If the verification result only includes information about whether the verification is successful, the second service data may be service data of all preset fields updated within a preset time period. If the verification result further includes the identification information of the unsynchronized data, the second service data may be the unsynchronized data updated within the preset time period.

In step 504, the connector converts the second service data into second target data adapted to the unified service system according to a preset rule, and in step 505, the connector sends the second target data to the server of the unified service system to instruct the server of the unified service system to update the data in the database with the second target data.

For ease of understanding, an example application of the data verification process is provided below for illustrative purposes. First, the connector obtains the update information of the service data updated in the previous hour from the database of the target service system server. The update information may include the ID of the approval task S1, the creation time Ta1 of the approval task S1, the ID of the approval task S2, and the processing time Tb1 of the approval task S2.

And then, the connector sends a data verification request to a server of the unified service system, wherein the data verification request comprises the update information. After receiving the data verification request, the server of the unified service system searches the ID of the approval task S1 and the ID of the approval task S2 from the database of the unified service system. And then, obtaining the updating time Ta2 corresponding to the ID of the approval task S1 and the updating time Tb2 corresponding to the ID of the approval task S2, wherein if Ta1 is consistent with Ta2 and Tb1 is consistent with Tb2, it is indicated that the data of the target service system and the unified service system are synchronous, and the data verification is successful.

If the service end of the unified service system does not find the ID of the approval task S1, or Ta1 and Ta2 are inconsistent, it indicates that the data of the approval task S1 in the target service system and the unified service system are not synchronous, and the data check fails. The service end of the unified business system may return a verification result to the connector, the verification result including the ID of the approval task S1. And after receiving the verification result, the connector sends a data acquisition request carrying the ID of the approval task S1 to the server side of the target business system. In response to the data obtaining request, the server of the target service system obtains, from the database, the service data Da corresponding to the approval task S1 within a previous time period T2 (for example, within one hour) based on the ID of the approval task S1, and sends the service data Da to the connector.

And finally, the connector converts the service data Da into data Db adapted to the unified service system and sends the data Db to a server of the unified service system. The server of the unified business system can update the database with the data Db to keep data synchronization with the local business system.

The embodiment can perform data verification on the unified service system, and update the database of the unified service system under the condition of verification failure, so that the unified service system and the target service system can keep data synchronization, and the effect of the unified service system on data integration of the target service system is improved.

It should be noted that although in the above embodiments, the operations of the methods of the embodiments of the present disclosure have been described in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Rather, the steps depicted in the flowcharts may change the order of execution. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

As shown in fig. 6, fig. 6 is a block diagram of a system integration apparatus shown in the present disclosure according to an exemplary embodiment, which may include: an acquisition module 601 and an adaptation module 602.

The acquisition module 601 is configured to acquire first service data updated by the target service system.

The adaptation module 602 is configured to convert the first service data into first target data adapted to a unified service system according to a preset rule, where the unified service system is configured to provide a service processing interface to perform service processing on the first target data.

In some embodiments, the acquisition module 601 is configured to: and acquiring first service data from the service data updated by the target service system based on the preset field.

In other embodiments, the first service data is collected from the service data updated by the target service system based on the preset field by a pre-deployed application program.

In other embodiments, the pre-deployed application collects the first business data from the business data updated by the target business system based on the preset field by: the method comprises the steps of detecting a signal for starting a timing task, responding to the detected signal for starting the timing task, determining a target time for starting the timing task last time, and acquiring service data corresponding to a preset field from service data updated in a target service system from the target time to the current time to serve as first service data.

In other embodiments, the adaptation module 602 is configured to: and adding corresponding field values under all target fields adapted to the unified service system according to preset rules based on the field values of all preset fields included in the first service data to obtain the first target data.

In other embodiments, the apparatus may further comprise: a transmission module (not shown in the figure).

The transmission module is used for transmitting the first target data to the unified service system, so that the unified service system performs service processing based on the first target data.

In other embodiments, the apparatus may further comprise: a reconciliation module (not shown).

The reconciliation module is configured to instruct the unified service system to check whether data of the unified service system and data of the target service system are synchronous, receive a check result returned by the unified service system, and instruct the adaptation module 602 to send instruction information for updating the data to the unified service system when the check result indicates that the check fails.

In other embodiments, the reconciliation module instructs the unified service system to check whether the data of the unified service system and the target service system are synchronized by: and acquiring the updating information of the target service system updating data in a preset time interval at every preset time interval. And sending a check request carrying the update information to the unified service system to indicate the unified service system to check whether the data of the unified service system and the data of the target service system are synchronous or not based on the update information. And if the data are synchronous, the verification is successful, and if the data are asynchronous, the verification fails.

In other embodiments, the update information includes identification information of the updated service data and update time information.

In other embodiments, the reconciliation module instructs the adaptation module 602 to send the indication information for updating the business data to the unified business system by: the instruction acquisition module 601 acquires the second service data updated in the preset time period from the target service system. The indication adapting module 602 converts the second service data into second target data adapted to the unified service system according to a preset rule, and sends indication information carrying the second target data to the unified service system, where the indication information is used to indicate the unified service system to perform data update by using the second target data.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present disclosure. One of ordinary skill in the art can understand and implement it without inventive effort.

Fig. 7 is a schematic block diagram of an electronic device provided in some embodiments of the present disclosure. As shown in fig. 7, the electronic device 910 includes a processor 911 and a memory 912, and can be used to implement a client or a server. The memory 912 is used to non-transitory store computer-executable instructions (e.g., one or more computer program modules). The processor 911 is configured to execute the computer-executable instructions, and when the computer-executable instructions are executed by the processor 911, the computer-executable instructions may perform one or more steps of the system integration method described above, thereby implementing the system integration management method described above. The memory 912 and the processor 911 may be interconnected by a bus system and/or other form of connection (not shown).

For example, the processor 911 may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU) or other form of processing unit having data processing capabilities and/or program execution capabilities. For example, the Central Processing Unit (CPU) may be an X86 or ARM architecture or the like. The processor 911 may be a general-purpose processor or a special-purpose processor that controls other components in the electronic device 910 to perform desired functions.

For example, memory 912 may include any combination of one or more computer program products that may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. Volatile memory can include, for example, Random Access Memory (RAM), cache memory (or the like). The non-volatile memory may include, for example, Read Only Memory (ROM), hard disk, Erasable Programmable Read Only Memory (EPROM), portable compact disk read only memory (CD-ROM), USB memory, flash memory, and the like. One or more computer program modules may be stored on the computer-readable storage medium and executed by processor 911 to implement various functions of electronic device 910. Various applications and various data, as well as various data used and/or generated by the applications, and the like, may also be stored in the computer-readable storage medium.

It should be noted that, in the embodiment of the present disclosure, reference may be made to the above description on the system integration method for specific functions and technical effects of the electronic device 910, and details are not described here.

Fig. 8 is a schematic block diagram of another electronic device provided by some embodiments of the present disclosure. The electronic device 920 is, for example, suitable for implementing the system integration method provided by the embodiments of the present disclosure. The electronic device 920 may be a terminal device or the like, and may be used to implement a client or a server. The electronic device 920 may include, but is not limited to, mobile terminals such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet), a PMP (portable multimedia player), a vehicle-mounted terminal (e.g., a car navigation terminal), a wearable electronic device, and the like, and fixed terminals such as a digital TV, a desktop computer, a smart home device, and the like. It should be noted that the electronic device 920 shown in fig. 8 is only an example, and does not bring any limitation to the functions and the scope of the application of the embodiments of the present disclosure.

As shown in fig. 8, electronic device 920 may include a processing device (e.g., central processing unit, graphics processor, etc.) 921 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)922 or a program loaded from a storage device 928 into a Random Access Memory (RAM) 923. In the RAM 923, various programs and data necessary for the operation of the electronic apparatus 920 are also stored. The processing device 921, the ROM922, and the RAM 923 are connected to each other via a bus 924. An input/output (I/O) interface 925 is also connected to bus 924.

Generally, the following devices may be connected to I/O interface 925: input devices 926 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 927 including, for example, a Liquid Crystal Display (LCD), speaker, vibrator, etc.; storage devices 928 including, for example, magnetic tape, hard disk, etc.; and a communication device 929. The communication device 929 may allow the electronic device 920 to communicate wirelessly or by wire with other electronic devices to exchange data. While fig. 8 illustrates an electronic device 920 having various means, it is to be understood that not all illustrated means are required to be implemented or provided, and that the electronic device 920 may alternatively be implemented or provided with more or less means.

For example, the system integration method described above may be implemented as a computer software program according to an embodiment of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program comprising program code for performing the system integration method described above. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 929, or installed from the storage device 928, or installed from the ROM 922. When the computer program is executed by the processing device 921, the functions defined in the system integration method provided by the embodiment of the present disclosure can be implemented.

Fig. 9 is a schematic diagram of a storage medium according to some embodiments of the present disclosure. For example, as shown in fig. 9, storage medium 930 may be a non-transitory computer-readable storage medium for storing non-transitory computer-executable instructions 931. The system integration method described in embodiments of the present disclosure may be implemented when the non-transitory computer-executable instructions 931 are executed by a processor, for example, one or more steps in the system integration method described above may be performed when the non-transitory computer-executable instructions 931 are executed by a processor.

For example, the storage medium 930 may be applied to the electronic device described above, and the storage medium 930 may include a memory in the electronic device, for example.

For example, the storage medium may include a memory card of a smart phone, a storage component of a tablet computer, a hard disk of a personal computer, a Random Access Memory (RAM), a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), a portable compact disc read only memory (CD-ROM), a flash memory, or any combination of the above, as well as other suitable storage media.

For example, the description of the storage medium 930 may refer to the description of the memory in the embodiment of the electronic device, and repeated descriptions are omitted. Specific functions and technical effects of the storage medium 930 may be referred to the above description of the system integration method, and will not be described herein again.

It should be noted that in the context of this disclosure, a computer-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable medium may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but is not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method of system integration, the method comprising:

acquiring first service data updated by a target service system;

2. The method of claim 1, wherein the obtaining the first service data updated by the target service system comprises:

and acquiring first service data from the service data updated by the target service system based on a preset field.

3. The method of claim 2, wherein the obtaining first service data from the service data updated by the target service system based on the preset field comprises:

and acquiring the first service data from the updated service data of the target service system based on a preset field through a pre-deployed application program.

4. The method of claim 3, wherein the pre-deployed application collects the first business data from the updated business data of the target business system based on preset fields by:

detecting a signal for starting a timing task;

and responding to a signal for detecting the start of the timing task, and acquiring service data corresponding to the preset field from service data updated in the target service system from a target time to the current time as the first service data, wherein the target time comprises the time of the last start of the timing task.

5. The method of claim 1, wherein the converting the first service data into first target data adapted to a unified service system according to a preset rule comprises:

and adding corresponding field values under all target fields adapted to the unified service system according to preset rules based on the field values of all preset fields corresponding to the first service data to obtain the first target data.

6. The method of claim 1, wherein the method further comprises:

and transmitting the first target data to the unified service system, so that the unified service system performs service processing based on the first target data.

7. The method of claim 6, wherein the method further comprises:

instructing the unified service system to check whether the data of the unified service system and the data of the target service system are synchronous or not;

receiving a check result returned by the unified service system;

and if the verification result indicates that the verification fails, sending indication information for updating data to the unified service system.

8. The method of claim 7, wherein said instructing the unified services system to verify whether the data of the unified services system and the target services system are synchronized comprises:

acquiring update information of the target service system for updating service data in a preset time interval at every preset time interval;

sending a verification request carrying the updating information to the unified service system to indicate the unified service system to verify whether the data of the unified service system and the data of the target service system are synchronous or not based on the updating information;

and if the data are synchronous, the verification is successful, and if the data are asynchronous, the verification fails.

9. The method of claim 8, wherein the update information includes identification information of the updated service data and update time information.

10. The method of claim 8, wherein the sending the indication information for updating data to the unified traffic system comprises:

acquiring second service data updated in the preset time period from the target service system;

converting the second service data into second target data adapted to the unified service system according to a preset rule;

and sending indication information carrying the second target data to the unified service system, wherein the indication information is used for indicating the unified service system to update data by using the second target data.

11. The method of any of claims 1-10, wherein the target business system comprises a local business system deployed at a local server/server cluster.

12. A system integration apparatus, the apparatus comprising:

13. A computer-readable storage medium, having stored thereon a computer program which, when executed in a computer, causes the computer to perform the method of any one of claims 1-11.

14. An electronic device comprising a memory having stored therein executable code and a processor that, when executing the executable code, implements the method of any of claims 1-11.