Data integration method, system and device, storage medium and program product

Abstract

The invention discloses a data integration method, system and device, a storage medium and a program product, and relates to the technical field of enterprise application integration, and the method comprises the steps: receiving a data access interface and a debugging command defined by a user based on an SQL template through an integration platform of an SaaS end, and the debugging command is issued to a front service client of an enterprise local system through a secure communication channel. And the front service client constructs an actual SQL statement according to the debugging command in combination with the input and output parameters in the SQL template, and executes and returns debugging result information to the integrated platform for display when accessing the database. And after the user confirms that the SQL interface information is correct, the platform issues the SQL interface information to the front service client for analysis and storage. According to the scheme, efficient and safe data integration between the old enterprise system and the SaaS application is achieved through an integrated architecture based on cooperation of a remote debugging mechanism of an SQL template and a safe data channel.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of enterprise application integration, and in particular to a data integration method, system, device, storage medium and program product. BACKGROUND

[0002] In the process of providing services for enterprises by SaaS (Software as a Service) products, integration with some inventory systems already used by enterprises is often required. If the inventory systems of enterprises belong to well-maintained and open support, the system integration capability of the SaaS side can be directly used to realize system integration. However, at present, there are a large number of enterprises that have carried out digital transformation early, introduced traditional ERP (Enterprise Resource Planning) software such as SAP, and currently lack of continuous maintenance and upgrade, and they cannot open interfaces to the outside, but can only interact data through intermediate libraries; or even some small software companies customized software purchased by some enterprises, which cannot support intermediate libraries, and can only directly interact data with business libraries. Under the premise that enterprises still need to use these old systems for a certain period of time, how SaaS products integrate data with them becomes a key problem for the successful landing of SaaS products in enterprises. SUMMARY

[0003] The main purpose of the present application is to provide a data integration method, system, device, storage medium and program product, aiming to solve the technical problem of how to efficiently and safely integrate data between old enterprise systems and modern SaaS applications.

[0004] To achieve the above purpose, the present application provides a data integration method, which is applied to a Software as a Service (SaaS) side, the SaaS side at least includes an integration platform, and the data integration method comprises the following steps:

[0005] receiving, by the integration platform, a data access interface defined by a user based on a Structured Query Language (SQL) template, and receiving a debugging interface command input by the user;

[0006] sending, by a pre-constructed secure communication channel, the debugging interface command to a front-end service client of an enterprise local system, so that the front-end service client constructs an actually executed SQL according to the debugging interface command and in combination with input and output parameters in a pre-defined SQL template, executes the SQL in the process of accessing an enterprise local database, obtains debugging result information, and returns the debugging result information to the integration platform of the SaaS side through the pre-constructed secure communication channel;

[0007] receiving and displaying, by the integration platform, the debugging result information returned by the enterprise local system;

[0008] receive SQL interface information published by a user based on the debugging result information, and send the published SQL interface information to the front-end service client of the enterprise local system through the pre-constructed secure communication channel, so that the front-end service client parses and stores the received SQL interface information.

[0009] In an embodiment, before the step of sending the debugging interface command to the front-end service client of the enterprise local system through the pre-constructed secure communication channel, the method further comprises:

[0010] downloading a client certificate from the integration platform;

[0011] When receiving the front-end machine certificate sent by the enterprise local system, performing tenant identity and permission verification according to the front-end machine certificate and the client certificate to obtain a verification result;

[0012] returning the verification result to the enterprise local system, so that the enterprise local system establishes a long connection communication with the SaaS end in response to the verification result, and constructs a secure communication channel for data transmission protection using a national secret algorithm.

[0013] In an embodiment, after the step of sending the published SQL interface information to the front-end service client of the enterprise local system through the secure communication channel, the method further comprises:

[0014] receiving data synchronization task scheduling information defined by a user based on the integration platform;

[0015] sending the data synchronization task scheduling information to the front-end service client of the enterprise local system through the pre-constructed secure communication channel, so that the front-end service client parses and stores the data synchronization task scheduling information, and executes a data synchronization task according to a timing trigger condition in the data synchronization task scheduling information.

[0016] In addition, to achieve the above-mentioned purpose, the application also provides a data integration method, which is applied to an enterprise local system, wherein a front-end service client is deployed in the enterprise local system, and the data integration method comprises:

[0017] receiving a debugging interface command sent by the SaaS end through a pre-constructed secure communication channel, and constructing an actually executed SQL according to the debugging interface command and input and output parameters in a pre-defined SQL template;

[0018] executing the SQL in the process of accessing the enterprise local database, obtaining debugging result information, and returning the debugging result information to the integration platform of the SaaS end through the pre-constructed secure communication channel.

[0019] receiving published SQL interface information issued by the SaaS end, parsing the SQL interface information, and storing the same.

[0020] In an embodiment, before the step of receiving the debugging interface command sent by the SaaS end through the pre-constructed secure communication channel, the method further comprises:

[0021] When receiving a login instruction input by a currently logged-in person, performing a login authentication operation;

[0022] After the login authentication succeeds, obtaining user information and a remote cryptogram token of the currently logged-in user;

[0023] Based on the user information and the remote cryptogram token, importing a front-end machine certificate;

[0024] sending the front-end machine certificate to the SaaS end, so that the SaaS end performs tenant identity and permission verification according to the front-end machine certificate and a client certificate, obtains a verification result, and returns the verification result to the enterprise local system;

[0025] When identifying that the verification result returned by the SaaS end is a verification success, establishing a long connection communication with the SaaS end, and constructing a secure communication channel for data transmission protection using a national secret algorithm.

[0026] In an embodiment, the step of constructing an actually executed SQL according to the debugging interface command and in combination with input and output parameters in a pre-defined SQL template comprises:

[0027] parsing the debugging interface command to obtain an original command, wherein the original command comprises an interface identifier and input and output parameters;

[0028] Based on the interface identifier in the original command, searching for a corresponding pre-defined SQL template, and in combination with the input and output parameters and pre-configured database connection information, generating an actually executed SQL.

[0029] In an embodiment, after the step of receiving published SQL interface information issued by the SaaS end, parsing the SQL interface information, and storing the same, the method further comprises:

[0030] receiving data synchronization task scheduling information sent by the SaaS end through the pre-constructed secure communication channel;

[0031] The data synchronization task scheduling information is parsed and stored, and a data synchronization task is executed according to a timing trigger condition in the data synchronization task scheduling information, wherein the data synchronization task comprises timing data grabbing from an enterprise local database and pushing to the SaaS side, or timing data pulling from the SaaS side and synchronizing to the enterprise local database.

[0032] In an embodiment, the SQL interface corresponding to the SQL interface information allows to be called and accessed by application services in an enterprise intranet and the front-end service client itself.

[0033] In addition, to achieve the above-mentioned purpose, the application further provides a data integration system, which comprises a SaaS side and an enterprise local system,

[0034] The SaaS side comprises:

[0035] The receiving module is configured to receive a data access interface defined by a user based on a SQL template through the integration platform, and receive a debugging interface command input by the user.

[0036] The debugging command sending module is configured to send the debugging interface command to the front-end service client of the enterprise local system through a pre-constructed secure communication channel, so that the front-end service client constructs an actually executed SQL according to the debugging interface command and in combination with input and output parameters in a pre-defined SQL template, executes the SQL in the process of accessing an enterprise local database, obtains debugging result information, and returns the debugging result information to the integration platform of the SaaS side through the pre-constructed secure communication channel.

[0037] The debugging information processing module is configured to receive the debugging result information returned by the enterprise local system through the integration platform, and display the debugging result information through the integration platform.

[0038] The interface configuration management module is configured to receive SQL interface information published by the user based on the debugging result information, and send the published SQL interface information to the front-end service client of the enterprise local system through the secure communication channel, so that the front-end service client parses and stores the received SQL interface information.

[0039] The enterprise local system comprises:

[0040] The construction module is configured to receive the debugging interface command sent by the SaaS side through the front-end service client, and construct an actually executed SQL according to the debugging interface command and in combination with input and output parameters in a pre-defined SQL template.

[0041] An execution module is configured to execute the SQL in a process of accessing the enterprise local database, obtain debugging result information, and return the debugging result information to the integration platform at the SaaS end through a pre-constructed secure communication channel.

[0042] An interface information processing module is configured to receive published SQL interface information issued by the SaaS end, parse and store the SQL interface information, wherein the SQL interface information corresponding to the SQL interface is allowed to be called and accessed by the application service in the enterprise internal network and the front service client itself.

[0043] In addition, to achieve the above object, the present application further provides a data integration device, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the data integration method as described above.

[0044] In addition, to achieve the above object, the present application further provides a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the data integration method as described above.

[0045] In addition, to achieve the above object, the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the data integration method as described above.

[0046] The application provides a data integration method, system, device, storage medium and program product. The method is applied to a SaaS end and a local system of an enterprise respectively. The method comprises the following steps: receiving a data access interface defined by a user based on a SQL template through an integration platform of the SaaS end, and receiving a debugging interface command input by the user; sending the debugging interface command to a front-end service client of the local system of the enterprise through a secure communication channel, so that the front-end service client constructs an actually executed SQL according to the debugging interface command and in combination with input and output parameters in the pre-defined SQL template, executes the SQL in a process of accessing a database, obtains debugging result information, and returns the debugging result information to the integration platform of the SaaS end through the secure communication channel; receiving the debugging result information returned by the local system of the enterprise through the integration platform, and displaying the debugging result information through the integration platform; receiving SQL interface information published by the user, and issuing the published SQL interface information to the front-end service client of the local system of the enterprise, so that the front-end service client parses and stores the received SQL interface information. The scheme realizes efficient and safe data integration between an old enterprise system and a SaaS application based on a remote debugging mechanism of the SQL template and an integrated architecture of cooperation of a secure data channel. BRIEF DESCRIPTION OF DRAWINGS

[0047] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained based on these drawings without creative labor.

[0049] Figure 1 A flowchart is provided for the data integration method embodiment one of the present application;

[0050] Figure 2 A flowchart is provided for the data integration method embodiment two of the present application;

[0051] Figure 3 A DB2 API editor diagram is provided for the embodiment two;

[0052] Figure 4 A flowchart is provided for the data integration method embodiment three of the present application;

[0053] Figure 5 A flowchart is provided for the data integration method embodiment four of the present application;

[0054] Figure 6 A flowchart provided for the fifth embodiment of the data integration method of the present application;

[0055] Figure 7 A flowchart provided for the sixth embodiment of the data integration method of the present application;

[0056] Figure 8 A schematic diagram of the overall architecture provided for the embodiment of the data integration method of the present application;

[0057] Figure 9 A schematic diagram of the front-end service client architecture in the enterprise system provided for the embodiment of the data integration method of the present application;

[0058] Figure 10 A hot update capability operation diagram provided for the embodiment of the data integration method of the present application;

[0059] Figure 11 A secure communication channel construction flowchart provided for the embodiment of the data integration method of the present application;

[0060] Figure 12 A schematic diagram of the openAPI proxy plug-in function implementation provided for the embodiment of the data integration method of the present application;

[0061] Figure 13 A schematic diagram of the DB2API plug-in function implementation provided for the embodiment of the data integration method of the present application;

[0062] Figure 14 A schematic diagram of the local runtime function implementation provided for the embodiment of the data integration method of the present application;

[0063] Figure 15 A schematic diagram of the module structure of the data integration system of the embodiment of the present application;

[0064] Figure 16 A schematic diagram of the device structure of the hardware operating environment involved in the data integration method of the embodiment of the present application.

[0065] The object implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0066] It should be understood that the specific embodiments described herein are merely intended to explain the technical solutions of the present application, and are not intended to limit the present application.

[0067] In order to better understand the technical solutions of the present application, the following will be described in detail in conjunction with the drawings and specific embodiments of the specification.

[0068] The main solution of the embodiment of the application is that the integration platform at the SaaS end receives a data access interface defined by a user based on a SQL template and receives a debugging interface command input by the user; the debugging interface command is sent to a front-end service client of an enterprise local system through a secure communication channel, so that the front-end service client constructs an actually executed SQL according to the debugging interface command and in combination with input and output parameters in the pre-defined SQL template, executes the SQL in the process of accessing the database, obtains debugging result information, returns the debugging result information to the integration platform at the SaaS end through the secure communication channel; the integration platform receives the debugging result information returned by the enterprise local system and displays the debugging result information through the integration platform; the SQL interface information that has been debugged and completed is received, and the published SQL interface information is sent to the front-end service client of the enterprise local system, so that the front-end service client parses and stores the received SQL interface information.

[0069] In the embodiment, for convenience of description, the following is described with the SaaS and the enterprise local system as the execution subject respectively.

[0070] Since some enterprise systems are old and cannot open interfaces to the Internet at present (for example, the service middleware version is old, has many vulnerabilities, and directly exposing to the Internet has too many security risks; or the enterprise system cannot provide https service, and directly exposing http service has too great security risk; or the enterprise system itself does not support opening interfaces, and directly using internal business interface permission cannot be controlled, etc.), the SaaS service and these services are integrated by directly reading and writing the local system business library or the intermediate library.

[0071] The application provides a solution of deploying a front-end runtime service locally at a client, realizing safe access of a SaaS product on the cloud through a long connection and a secure communication protocol, and avoiding directly exposing the local old service to the Internet. Meanwhile, the solution supports developing an SQL-based interface on a SaaS development platform on the cloud and pushing the interface to the enterprise local system, provides remote interface maintenance capability, and realizes transaction control and business arrangement based on visual arrangement. Data transmission is realized through bidirectional secure communication based on front-end capability, and the original data processing process does not go out of the enterprise local system, so as to ensure data security and privacy. These characteristics enable a SaaS product service provider to realize enterprise old system integration at limited cost, and solve the problem of data sensitivity of the enterprise local old system and inability to open interfaces for external system calling.

[0072] It should be noted that the execution subject of the embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, or an electronic device capable of realizing the above functions. The following takes a personal computer as an example to describe the embodiment and the following embodiments.

[0073] Based on this, the embodiment of the present application provides a data integration method, referring to Figure 1 , Figure 1 The flowchart of the first embodiment of the data integration method of the present application is shown in the figure.

[0074] In the embodiment, the data integration method is applied to the SaaS end, and the data integration method comprises steps S10-S40:

[0075] Step S10, receiving a data access interface defined by a user based on a structured query language (SQL) template through the integration platform, and receiving a debugging interface command input by the user;

[0076] It should be noted that the SaaS end at least comprises an API platform, an integration platform and a SaaS product module. The API platform is used to provide a standardized application programming interface for external system calling and data interaction; the integration platform is used to support the user to define the SQL template in a graphical interface, configure the data interface, arrange the data synchronization task, and manage the connection strategy with the enterprise local system; and the SaaS product module is a business function module for end users, which is used to realize the core business logic of the SaaS product and cooperates with the integration platform to complete the data linkage with the enterprise local system.

[0077] It can be understood that due to the technical difficulties such as network isolation, data format heterogeneity and access permission control between the enterprise local system and the SaaS application, directly exposing the database connection information or opening the original SQL interface will bring great security risks and operation and maintenance complexity when performing data integration across the network boundary. Therefore, step S10 can avoid random access to the database in the absence of a unified management mechanism, thereby realizing the security control and centralized management of the data interface definition process.

[0078] Specifically, before receiving a data access interface defined by a user based on a structured query language (SQL) template, the integration platform receives relevant integration parameters configured by the user, including but not limited to connection string information of an enterprise local DB (intermediate library / business library), which contains timeout configuration, maximum connection number configuration, and user password information; database driver file address in a pre-service client server of the enterprise local system; and authentication information required for connecting with an OpenAPI of a SaaS product, such as AppKey and AppSecret information. By introducing a unified configuration mechanism of integration parameters before interface definition, the flexibility and compatibility of system connection are improved, and the security vulnerability risk caused by manual splicing of connection information or hard-coded credentials is effectively reduced, further enhancing the stability and maintainability of an enterprise-level data integration solution.

[0079] After the above integration parameters are configured, the integration platform further receives a data access interface defined by a user based on a SQL template, and receives a debugging interface command input by the user, thereby laying a foundation for subsequent actual SQL construction and debugging operations performed by the pre-service client through a secure communication channel.

[0080] In step S20, the debugging interface command is sent to the pre-service client of the enterprise local system through a pre-constructed secure communication channel, so that the pre-service client constructs an actually executed SQL according to the debugging interface command and in combination with input and output parameters in the pre-defined SQL template, and executes the SQL in the process of accessing the enterprise local database to obtain debugging result information, and returns the debugging result information to the integration platform of the SaaS side through the pre-constructed secure communication channel.

[0081] It should be noted that the secure communication channel refers to a bidirectional trusted connection channel established by using an encrypted transmission protocol, which is used to ensure the confidentiality, integrity, and identity verifiability of data transmission between the SaaS side and the enterprise local system.

[0082] It can be understood that, since the enterprise local database is usually deployed in an intranet environment and cannot be directly exposed to an external network due to security considerations, and the traditional remote direct connection database method has risks such as high latency, abuse of rights, and data leakage, step S20 can be performed to realize secure delivery and result feedback of the debugging command, thereby ensuring that the data operation across the network boundary is both efficient and controllable.

[0083] Specifically, after receiving a user-initiated debugging interface command, the integration platform encapsulates and encrypts the debugging interface command and sends it to the front-end service client of the enterprise local system through the established secure communication channel. After receiving the debugging interface command, the front-end service client looks up the corresponding SQL template based on the interface identifier carried therein, and constructs an executable SQL statement in combination with the input and output parameters defined in the template. The debugging result information is generated after the execution of the SQL statement in the DB (intermediate library / business library) of the enterprise local system, and the result is returned to the integration platform through the same secure communication channel for display.

[0084] Through the above steps, the secure communication channel is used to realize the delivery of remote debugging commands and the return of execution results, effectively solving the problems of network penetration difficulty, poor security, low debugging efficiency and other problems in the traditional scheme, and improving the security, stability and response speed of the overall data integration process.

[0085] Step S30, receiving and displaying the debugging result information returned by the enterprise local system through the integration platform;

[0086] It should be noted that the debugging result information includes but is not limited to SQL statement execution status, execution time, returned data set content, error log information, and database connection health status, etc. These information are used to assist the user to determine whether the defined data access interface meets the expected function and performance requirements.

[0087] It can be understood that due to the design of data interaction across network boundaries in the debugging process, if there is no visual feedback mechanism, the user will have difficulty in timely mastering the interface execution effect and making corrections. Therefore, by performing step S30, centralized presentation and analysis of remote debugging results can be realized, thereby improving the interface development efficiency and debugging accuracy.

[0088] Specifically, the integration platform receives the debugging result information returned by the enterprise local system after executing the actual SQL, and the user can directly view the execution details in the graphical interface of the integration platform. After confirming that the debugging result is correct, the user can select the corresponding SQL interface based on the debugging result information to perform a publishing operation to trigger subsequent interface configuration delivery and automated execution processes.

[0089] In this step, a visual debugging result display mechanism is provided, so that the user can master the remote SQL execution in real time without entering the enterprise intranet environment, significantly reducing the interface debugging threshold and improving the development and operation efficiency.

[0090] Step S40, receiving the SQL interface information published by the user based on the debugging result information, and issuing the published SQL interface information to the front-end service client of the enterprise local system through the pre-constructed secure communication channel, so that the front-end service client parses and stores the received SQL interface information.

[0091] Specifically, after receiving the interface information corresponding to the completed debugging SQL interface confirmed by the user for publishing, the integration platform encapsulates the SQL interface information as executable configuration data, and transmits it to the front-end service client of the enterprise local system through the established secure communication channel. After receiving the interface information, the front-end service client parses it, extracts the interface identifier, SQL template definition, input / output parameter mapping relationship, and execution strategy, and stores it in a structured form in the local configuration database, so as to automatically call and execute the corresponding data access operation according to the scheduling task or external request in the future.

[0092] Through this step, after the user confirms that the debugging result is correct, the SQL interface information is safely issued to the enterprise local system, and is stored and managed by the front-end service client in the enterprise local system, realizing seamless connection from cloud definition to local execution, improving the deployment efficiency and running stability of the data interface, and at the same time guaranteeing the interface security and controllability across the network boundary.

[0093] Through the above embodiment method, the integration platform of the SaaS side receives the data access interface defined by the user based on the SQL template, and receives the debugging interface command input by the user; through the secure communication channel, the debugging interface command is sent to the front-end service client of the enterprise local system, so that the front-end service client constructs the actually executed SQL according to the debugging interface command and the input / output parameters in the pre-defined SQL template, and executes the SQL in the process of accessing the database to obtain the debugging result information. The debugging result information is returned to the integration platform of the SaaS side through the secure communication channel; the integration platform receives the debugging result information returned by the enterprise local system, and displays the debugging result information through the integration platform; receives the SQL interface information published by the user after debugging, and issues the published SQL interface information to the front-end service client of the enterprise local system, so that the front-end service client parses and stores the received SQL interface information. This scheme realizes efficient and secure data integration between old enterprise systems and SaaS applications based on the remote debugging mechanism of the SQL template and the integrated architecture of the secure data channel.

[0094] Based on this, the embodiment of the present application provides another data integration method, which refers to Figure 2 , Figure 2A flowchart of a second embodiment of the data integration method of the application.

[0095] In this embodiment, the data integration method is applied to an enterprise local system, and the data integration method comprises steps S50-S70:

[0096] In step S50, a debugging interface command sent by a SaaS end is received through a pre-constructed secure communication channel, and an actually executed SQL is constructed according to the debugging interface command and in combination with input and output parameters in a pre-defined SQL template.

[0097] It should be noted that the enterprise local system has a front-end service client deployed therein, and the front-end service client comprises an openAPI proxy module, a DB2API module, an interface orchestration module and a basic docking module.

[0098] In addition, it should also be noted that the SQL template refers to a structured query statement containing a placeholder variable pre-configured by a user in an integration platform, and is used to define a standard logical framework of a data access interface. The input and output parameters in the SQL template include, but are not limited to, input parameters required when an interface is requested, output field definitions and format requirements, parameter type checking rules and default value settings, etc.

[0099] The actually executed SQL refers to that after the front-end service client parses the debugging interface command, parameter values carried in the debugging interface command are extracted and substituted into the corresponding SQL template for variable replacement and syntax splicing, so as to generate an effective SQL statement that can be directly executed in a target database.

[0100] It can be understood that since an enterprise local database is usually deployed in an intranet environment and cannot be directly exposed to an external system for access, and a traditional manual splicing of SQL has the problems of security risks and high maintenance costs, therefore, in step S50, an actually executable SQL statement can be dynamically generated based on a remotely issued debugging command, so as to realize safe control and flexible scheduling of a cross-network boundary data access process.

[0101] In a feasible embodiment, step S50 can comprise steps S51-S52:

[0102] In step S51, the debugging interface command is parsed to obtain an original command, wherein the original command comprises an interface identifier and input and output parameters.

[0103] It should be noted that the interface identifier is used to uniquely identify a called data access interface; the input parameters include specific values transmitted by a user when the interface is called; and the output parameters are used to indicate a data structure or field expected to be returned.

[0104] Specifically, when the front-end service client of the enterprise local system receives the debugging interface command sent by the SaaS end, the debugging interface command is first decrypted and structurally parsed by the underlying interface module, wherein the debugging interface command can be transmitted in a structured data format (such as JSON, XML or Protobuf) and contains the following key fields: interface identifier, input parameter, output parameter, execution mode identifier, and authentication and context information.

[0105] By parsing these fields, a structured original command is generated, and the parsed original command is dispatched to the DB2API module for execution.

[0106] Step S52, based on the interface identifier in the original command, the corresponding predefined SQL template is found, and the actual executed SQL is generated in combination with the input and output parameters and the pre-configured database connection information.

[0107] It should be noted that the database connection information at least includes the connection string (including timeout configuration, connection number configuration, etc.) of the enterprise local DB (intermediate library or business library).

[0108] Specifically, after the DB2API module receives the original command information, the interface identifier carried in the original command is used to find the corresponding SQL template from the local cache or configuration file. Subsequently, the placeholder variables in the SQL template are replaced with the input and output parameters provided in the original command, and the database connection information is combined to complete the splicing and verification of the SQL statement, and finally an effective SQL statement that can be directly executed in the target database is generated.

[0109] The DB2API module can identify the input and output parameters from the predefined SQL template and complete the generation of the final SQL statement in combination with the actual parameter values in the debugging interface command. Please refer to the DB2API editor diagram shown in Figure 3 which shows the specific interface of interface parameter configuration and SQL parsing.

[0110] As shown in Figure 3 When updating or creating a data access interface, the user first defines the basic properties of the interface in the "basic information" page, including interface name, description, etc. Then enter the "SQL statement" page and input or select the corresponding SQL template content. When writing the SQL template, the developer can identify the parameter position to be replaced through a specific placeholder syntax. Then, in the "SQL parsing" page, the system will generate a corresponding input parameter list according to the placeholders in the SQL template, including but not limited to field code, type, whether required, and field name.

[0111] Through the above configuration, the DB2API module can accurately identify and extract the required input parameters and type constraints after receiving the debugging interface command, ensuring the correctness and security of the subsequent SQL construction process.

[0112] In the above steps, by introducing a structured database connection management mechanism and a secure SQL construction process in the DB2API module, the pre-service client can securely and efficiently execute the remotely issued data access instructions without exposing the real database connection information.

[0113] Step S60, execute the SQL in the process of accessing the enterprise local database, obtain the debugging result information, and return the debugging result information to the integration platform of the SaaS side through the pre-constructed secure communication channel;

[0114] It should be noted that the debugging result information includes SQL statement execution status (such as success, failure, timeout, etc.), execution time, database connection state and resource usage, query result set or affected row number, etc.

[0115] It can be understood that since the debugging command is initiated by the SaaS side and the actual execution occurs in the enterprise local database environment, if there is no effective result feedback mechanism, the user will not be able to timely grasp the interface execution effect and make corrections, therefore, the execution step S60 can obtain the execution result immediately after remote calling and return it to the SaaS side for display and analysis, thereby improving the interface debugging efficiency and accuracy.

[0116] Specifically, after the DB2API module generates an executable SQL statement, the system uses pre-configured database connection information to establish a local database connection and executes the SQL statement according to a pre-set strategy. After execution is completed, the system captures the complete execution result, which includes data set, execution status code and exception information, etc. debugging result information, and encapsulates these debugging result information into a structured data format and returns it to the basic interface module, and then returns the debugging result information to the integration platform of the SaaS side through the pre-constructed secure communication channel, so that the user can view the debugging result information in the integration platform and confirm the SQL interface to be published according to the debugging result information. Then, the debugged SQL interface is published. The integration platform of the SaaS side issues the SQL interface published by the user to the pre-service client of the enterprise local system through the pre-constructed secure communication channel.

[0117] In the above steps, by executing SQL in the enterprise local database and returning the debugging result information to the SaaS side, the remote interface debugging capability under the network boundary is realized, so that the user can master the interface execution state in real time without entering the intranet environment, and the development and debugging efficiency and system observability are significantly improved.

[0118] In step S70, the published SQL interface information issued by the SaaS side is received, and the SQL interface information is parsed and stored.

[0119] It should be noted that the SQL interface information includes but is not limited to interface identifier, interface description information, bound SQL statement or SQL template, request method type, etc.

[0120] It can be understood that since there are multiple service modules in the enterprise local system that depend on database operations, if manual construction of SQL and issuance through debugging commands are required each time, not only the efficiency is low, but also it is difficult to uniformly manage interface behavior. Therefore, by performing step S70, the standardized SQL interface defined and published by the SaaS side can be synchronized to the local environment, thereby forming a unified data access entry in the enterprise intranet, to solve the problem that the data of the enterprise local old system is sensitive and cannot be opened to the interface calling of external systems.

[0121] Specifically, after receiving the SQL interface information issued by the SaaS side, the pre-service client performs structured parsing on the interface information according to a preset data format, extracts key fields such as SQL statements, parameter templates, and permission policies, and stores them in a persistent manner according to a local recognizable manner. Subsequently, the system constructs a RESTful or RPC style local interface service based on the parsing result, so that the application services within the enterprise can directly access the SQL interface through standard HTTP requests or remote procedure calling methods without further forwarding through the SaaS side. At the same time, the pre-service client itself can also be used as a calling party to perform automatic operations such as timing tasks and event triggering using these published interfaces.

[0122] In addition, in order to ensure the security and controllability of interface calling, the pre-service client also performs identity verification, permission checking and access log recording when providing interface access capability, to ensure that the interface calling conforms to the enterprise security policy.

[0123] Through the above steps, the SQL interface information issued by the SaaS side is received and parsed, and a callable interface service is constructed in the enterprise local environment, realizing the unified publishing and local reuse of the database operation interface, and improving the data access efficiency and system autonomy of the enterprise in the local network environment.

[0124] Through the above embodiment method, the debugging interface command sent by the SaaS end is received through the secure communication channel, and an actually executed SQL is constructed according to the debugging interface command and in combination with input and output parameters in a predefined SQL template; the SQL is executed in the process of accessing the enterprise local database to obtain debugging result information, and the debugging result information is returned to the integration platform of the SaaS end through the secure communication channel; the published SQL interface information issued by the SaaS end is received, the SQL interface information is parsed and stored, and the SQL interface corresponding to the SQL interface information is allowed to be called and accessed by the application service in the enterprise internal network and the front-end service client itself. Through the integration architecture of the remote debugging mechanism based on the SQL template and the secure data channel, efficient and safe data integration between the old enterprise system and the SaaS application is realized.

[0125] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as the above embodiment one can be referred to the above introduction, and will not be described in detail. On this basis, please refer to Figure 4 , before step S20, the data integration method further includes steps S01-S03:

[0126] Step S01, downloading a client certificate from the integration platform;

[0127] Step S02, when receiving the front-end machine certificate sent by the enterprise local system, performing tenant identity and permission verification according to the front-end machine certificate and the client certificate to obtain a verification result;

[0128] Step S03, returning the verification result to the enterprise local system, so that the enterprise local system establishes a long connection communication with the SaaS end in response to the verification result, and constructs a secure communication channel for data transmission protection using a national secret algorithm.

[0129] It should be noted that the client certificate refers to an identity credential file issued by the integration platform of the SaaS end and distributed to the front-end service component, which includes but is not limited to enterprise tenant information, service end public key information, and front-end service unique identifier and other key information;

[0130] And the front-end machine certificate is an identity credential actively reported by the front-end service component deployed in the enterprise local system to the SaaS end, which is used to participate in the two-way identity authentication process.

[0131] It can be understood that compared with the first embodiment, the present embodiment also proposes a secure communication channel establishment method based on a double certificate system, which can realize accurate identification and permission control of tenant identity in a remote access scenario, ensure that the communication link established between the SaaS end and the enterprise local system has high security and compliance, and is especially suitable for enterprise-level application scenarios involving sensitive data interaction.

[0132] Specifically, first, the client certificate is downloaded from the integration platform server of the SaaS end and stored in a trusted certificate library. When the enterprise local system attempts to access the SaaS end, it sends the front-end certificate it holds to the SaaS end.

[0133] When the SaaS end receives the front-end certificate sent by the front-end service client of the enterprise local system, it performs two-way identity verification in combination with the client certificate and the front-end certificate, including but not limited to: certificate legality verification, digital signature verification, tenant identity matching, permission range comparison, and other operations, to obtain accurate verification results.

[0134] After completing the identity and permission verification, the SaaS end feeds back the verification results to the enterprise local system. If the verification is passed, the enterprise local system and the SaaS end can establish a stable and reliable long connection communication based on the results, and further use the national cryptographic algorithms SM2 / SM4 to encrypt the data in the communication process for transmission, thereby constructing a data security communication channel that meets the national cryptographic standards.

[0135] The above-mentioned embodiment method establishes a secure communication channel that uses national cryptographic algorithms for data transmission protection by introducing a double certificate mechanism combined with national cryptographic algorithms, realizing strong identity authentication and secure data transmission between the SaaS end and the enterprise local system.

[0136] Based on the second embodiment of the present application, in the fourth embodiment of the present application, the same or similar contents as the above-mentioned second embodiment can be referred to the above introduction, and will not be described in detail. On this basis, please refer to Figure 5 , before step S50, the data integration method further includes steps S05-S09:

[0137] Step S05, when receiving the login instruction input by the current login personnel, performing login authentication operation;

[0138] Step S06, after the login authentication is successful, obtaining the user information and the remote ciphertext token of the current login user;

[0139] Step S07, based on the user information and the remote ciphertext token, importing the front-end certificate;

[0140] Step S08, the front-end machine certificate is sent to the SaaS end, so that the SaaS end performs tenant identity and permission verification according to the front-end machine certificate and a client certificate, obtains a verification result, and returns the verification result to the enterprise local system;

[0141] Step S09, when it is identified that the verification result returned by the SaaS end is verification success, a long connection communication is established with the SaaS end, and a secure communication channel using a national encryption algorithm for data transmission protection is constructed.

[0142] It should be noted that the encryption algorithm designed in the embodiment is mainly a national encryption algorithm, and the algorithm used when performing encryption and decryption is SM2, using a public key for encryption and a private key for decryption; the algorithm used when performing signing and verifying is SM2WithSM3, using a private key for signing and a public key for verifying.

[0143] Specifically, first, the enterprise local system receives a login instruction input by a current login person through a graphical interface or a command line, including authentication information such as a username and a password. The system calls a local authentication service to verify the user identity, and if the verification is passed, the user information (such as user ID, role, permission level, etc.) of the current login user and a remote ciphertext token issued by an authentication center are obtained. The remote ciphertext token is a session credential processed by encryption, which is used for identity legitimacy verification when subsequent interface access or certificate import is performed.

[0144] Then, a front-end machine certificate import request is initiated to a local certificate management module based on the user information and the remote ciphertext token. The certificate management module analyzes and verifies the received information, confirms that there is no error, extracts the corresponding front-end machine certificate from a local storage or a remote certificate warehouse, and loads it into a running environment for subsequent communication.

[0145] Subsequently, the enterprise local system uploads the imported front-end machine certificate to the SaaS end. After the SaaS end receives the front-end machine certificate, it performs a two-way identity authentication and permission comparison operation in combination with the internal maintained client certificate, generates a verification result, and feeds back to the enterprise local system.

[0146] Finally, if the local system identifies that the verification result returned by the SaaS end is “verification success”, it indicates that the identities of both parties are legal and have communication permissions, and the system immediately establishes a stable and reliable long connection communication link with the SaaS end, and enables a national encryption algorithm to encrypt the data in the communication process.

[0147] The above embodiment method establishes a secure communication channel using a national encryption algorithm for data transmission protection by introducing a double-certificate mechanism combined with a national encryption algorithm, and realizes strong identity authentication and secure data transmission between the SaaS end and the enterprise local system.

[0148] Based on the first embodiment of the present application, in the fifth embodiment of the present application, the same or similar contents as the above embodiment one can be referred to the above introduction, and the subsequent will not be described. On this basis, please refer to Figure 6 , after step S40, the data integration method further comprises steps S401-S402:

[0149] Step S401, receiving the data synchronization task scheduling information defined by the user based on the integration platform;

[0150] Step S402, sending the data synchronization task scheduling information to the front-end service client of the enterprise local system through the pre-constructed secure communication channel, so that the front-end service client parses and stores the data synchronization task scheduling information, and executes the data synchronization task according to the timing trigger condition in the data synchronization task scheduling information.

[0151] It can be understood that, compared with the first embodiment, the present embodiment proposes an enterprise-level data synchronization management method based on a remote task scheduling mechanism, which can independently complete the parsing, scheduling and execution of tasks by the enterprise local system under the premise of unified configuration and issuance of data synchronization tasks on the SaaS side, thereby realizing asynchronous data processing capability across network boundaries and improving system flexibility and response efficiency.

[0152] Specifically, when the user edits the scheduling process of the SQL interface and the open interface of the SaaS product through the integration platform of the SaaS side, the data synchronization task scheduling information of the data synchronization task of the data synchronization task scheduling information is defined, which is defined by the data synchronization task of the data synchronization task scheduling information.

[0153] Then, these synchronization task scheduling information is published and issued to the front-end service client of the enterprise local system through the pre-constructed secure communication channel, so that the front-end service client parses and stores the data synchronization task scheduling information, thereby realizing the data synchronization process of the SaaS product and the enterprise local database.

[0154] Through the above embodiment method, the bidirectional data synchronization capability between the enterprise local database and the SaaS product can be realized, which not only retains the centralized management and visual scheduling advantages of SaaS on tasks, but also fully utilizes the efficient execution capability of the enterprise local system, and improves the heterogeneous system collaboration efficiency across network boundaries.

[0155] Based on the second embodiment of the present application, in the sixth embodiment of the present application, the same or similar contents as the above embodiment two can be referred to the above introduction, and the subsequent will not be described. On this basis, please refer to Figure 7After step S70, the data integration method further comprises steps S701-S702:

[0156] In step S701, data synchronization task scheduling information sent by the SaaS end through the pre-constructed secure communication channel is received.

[0157] In step S702, the data synchronization task scheduling information is parsed and stored, and data synchronization tasks are executed according to the timing trigger condition in the data synchronization task scheduling information, wherein the data synchronization tasks include periodically grabbing data from the enterprise local database and pushing to the SaaS end, or pulling data from the SaaS end and synchronizing to the enterprise local database.

[0158] It can be understood that, compared with the second embodiment, the enterprise local system independently completes the parsing and execution of the data synchronization task scheduling information issued by the SaaS, thereby realizing the asynchronous data processing capability across the network boundary and improving the system flexibility and response efficiency.

[0159] Specifically, after the enterprise local system receives the data synchronization task scheduling information sent by the SaaS end through the established secure communication channel, the data synchronization task scheduling information is parsed and stored by the basic interface module in the front-end service client. Subsequently, according to the timing trigger condition set in the data synchronization task scheduling information, the interface scheduling module in the front-end service client schedules the data synchronization task in a periodic form, thereby realizing the data synchronization process between the SaaS product and the enterprise local database.

[0160] Through the above-mentioned embodiment method, the unified management and issuance of the data synchronization task by the SaaS end are realized, and the enterprise local system independently parses and executes, thereby effectively solving the data intercommunication problem between heterogeneous systems across the network boundary. Not only the interface reusability and task scheduling flexibility are improved, but also the stability and operation convenience of the system are enhanced.

[0161] By way of example, in order to help understand the implementation process of the data integration method obtained after combining the above-mentioned embodiment one and embodiment two, please refer to Figure 8 , Figure 8 A schematic diagram of the overall architecture of a data integration method is provided, specifically:

[0162] by Figure 8It can be known that the overall architecture of the method of the embodiment includes two ends, namely a SaaS end and an enterprise local system. The SaaS end includes an API platform, an integration platform and SaaS product modules; the enterprise local system includes an enterprise network boundary and an enterprise intranet. The enterprise network boundary is deployed with a front service client, the front service client (front-end client) includes an openAPI proxy module, a DB2API module, an interface orchestration module and a basic interface module; the enterprise intranet includes a database (intermediate library / business library) and an old service system.

[0163] Further, please refer to Figure 9 , Figure 9 The front service client in the enterprise local system is shown in the schematic diagram. It can be known that the front service client adopts a monolithic architecture, including a service layer, a framework layer and a basic layer. The service layer includes: Figure 9

[0164] The plug-in system includes:

[0165] Database to API conversion plug-in: responsible for converting database operations into API interfaces.

[0166] Open API proxy plug-in: provides proxy functions for external API requests.

[0167] Local runtime environment: supports plug-in running in the local environment.

[0168] Static resources include:

[0169] Local management end web resources: contain static web page resources for the local management end.

[0170] Base system:

[0171] Login authentication: handles user login and identity verification.

[0172] Version management: manages different versions of software.

[0173] Operation and maintenance management: provides system operation and maintenance related functions.

[0174] Log management: manages and records system logs.

[0175] Communication module: responsible for communication between different components.

[0176] Security module: provides security related functions such as encryption, permission control, etc.

[0177] Storage module: manages data storage.

[0178] Hot update module: supports hot update function of the system.

[0179] ​The framework layer includes:

[0180] The backend:

[0181] springboot: Spring Boot framework, simplifying Spring-based application development.

[0182] springwebflux: Spring WebFlux framework, supporting reactive programming model.

[0183] tomcat-embed: Embedded Tomcat server, used for deploying Java Web applications.

[0184] websocket: WebSocket protocol, providing full-duplex communication channels.

[0185] The frontend:

[0186] React: React library, a JavaScript library for building user interfaces.

[0187] Antd: Ant Design, a set of enterprise-level UI design language and React component library.

[0188] The foundation layer includes:

[0189] JVM (JRE8): Java Virtual Machine (Java Runtime Environment 8), used for running Java programs.

[0190] SQLite (switchable mysql / tdsql): SQLite database, a lightweight relational database management system that can be switched to MySQL or TencentDB for MySQL (tdsql) and other database systems.

[0191] The front-end service client only supports single-machine deployment, and the foundation layer relies on JVM to achieve cross-physical device compatibility. At the same time, it supports plug-in system and static resource support for hot updates, where the hot update capability operation diagram is shown in FIG. 10. Through the hot update capability, the SaaS end can maintain metadata configuration and push it to the client with one key, making it easy to implement; the plug-in capability upgrade supports hot update capability, and component upgrade does not need to interrupt business.

[0192] In addition, the front-end service client is also based on the dual-protocol construction and the two-way communication capability of the SaaS, and uses the national secret algorithm for data encryption and signature for communication, to form a secure communication channel. At the same time, the client private key is only saved in the local front-end machine, and is bound with the front-end machine certificate, to ensure the security of the key. The front-end service client also supports configuring the openAPI, localAPI, and DB2API metadata on the SaaS management side, and issuing the metadata to the front-end service client through the management data control surface to take effect.

[0193] Further, refer to Figure 11 , Figure 11 The flowchart for constructing a secure communication channel is shown. Specifically, in the front-end machine registration stage, the user logs in through the APP scanning the front-end service client in the enterprise local system, and after successful login, distributes the remote request ciphertext token and user information through the front-end service client; and after the user imports the front-end machine certificate, the certificate and user identity are verified. Subsequently, the front-end service client in the enterprise local system and the front-end machine service end in the SssS side start the key exchange (this process uses the public key of the other party to encrypt the message in turn, to prevent being stolen). In the front-end machine running stage, the front-end service client in the enterprise local system and the front-end machine service end in the SssS side generate a random temporary symmetric encryption key for each request, to encrypt the data message, and then encrypt the symmetric encryption key using the asymmetric encryption key, and sign the whole message.

[0194] Further, refer to Figure 12 , Figure 12 The schematic diagram for the openAPI proxy plug-in function implementation is shown. The openAPI proxy plug-in supports the enterprise local system internal service block to quickly access the openAPI platform resources. Specifically, the enterprise internal service initiates a request through the front-end machine openAPI proxy, and after encryption and signature, forwards it to the SaaS side, which verifies and executes the business service, and after the encrypted response is returned, it is decrypted and restored by the front-end machine, to realize safe and efficient interface calling.

[0195] Further, refer to Figure 13 , Figure 13 The schematic diagram for the DB2API plug-in function implementation is shown. The DB2API plug-in has the function of database to API. Through this function, the enterprise intranet intermediate library can be directly exposed to the Internet without a special line, and the secure transmission of data can be realized. Specifically, the SaaS side configures the db2api definition, and after publishing, the metadata is issued to the front-end machine client through the control surface. At the same time, the integration platform runtime in the SaaS side pushes the parameter information to the front-end machine local when executing to the database node.

[0196] Further, refer to Figure 14, Figure 14 This is a schematic diagram for implementing the local runtime function. This function can prevent connection flows involving sensitive data operations from running on the enterprise's local system, further ensuring data security and compliance. Specifically, in the connector configured on the SaaS side, users can choose to publish the connection flow to the front-end machine for local execution. Environment variables and connection flows are sent to the local machine through a secure channel between the front-end server and the client; if the connection flow is triggered on a timer basis, its triggering rules will be managed by the local timer. The triggering behavior of the SaaS side will also be forwarded to the local execution, and operations such as event-driven or API calls will be completed locally. At the same time, the local runtime also supports components such as pAppFlow and pAppWow to achieve seamless migration and unified scheduling of connection flows between SaaS and local execution.

[0197] The above architecture and functions enable efficient and secure data integration between legacy enterprise systems and SaaS applications.

[0198] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the data integration method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0199] This application also provides a data integration system, please refer to Figure 15 , the data integration system includes SaaS end and enterprise local system,

[0200] The SaaS end includes:

[0201] The receiving module 10 is used to receive the data access interface defined by the user based on the SQL template through the integration platform, and receive the debugging interface command input by the user;

[0202] The debugging command sending module 20 is configured to send the debugging interface command to the front-end service client of the enterprise local system through a pre-established secure communication channel, so that the front-end service client can construct the actual SQL to be executed based on the debugging interface command and the input and output parameters in the pre-defined SQL template, execute the SQL in the process of accessing the enterprise local database, obtain debugging result information, and return the debugging result information to the SaaS-side integration platform through the pre-established secure communication channel;

[0203] The debugging information processing module 30 is used to receive and display the debugging result information returned by the enterprise local system through the integration platform;

[0204] The interface configuration management module 40 is configured to receive the published SQL interface information based on the debugging result information published by the user, and send the published SQL interface information to the front service client of the enterprise local system through the secure communication channel, so that the front service client parses and stores the received SQL interface information.

[0205] The enterprise local system comprises:

[0206] The construction module 50 is configured to receive the debugging interface command sent by the SaaS end through the front service client, and construct the SQL actually executed according to the debugging interface command and the input and output parameters in the pre-defined SQL template.

[0207] The execution module 60 is configured to execute the SQL in the process of accessing the enterprise local database, obtain the debugging result information, and return the debugging result information to the integration platform of the SaaS end through the pre-constructed secure communication channel.

[0208] The interface information processing module 70 is configured to receive the published SQL interface information sent by the SaaS end, parse and store the SQL interface information.

[0209] The data integration system provided by the application can solve the technical problem of how to efficiently and safely integrate data between an old enterprise system and a modern SaaS application by using the data integration method in the above embodiment. Compared with the prior art, the data integration system provided by the application has the same beneficial effects as the data integration method provided by the above embodiment, and other technical features in the data integration system are the same as the features disclosed in the above embodiment, which will not be repeated here.

[0210] The application provides a data integration device, comprising: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the data integration method in the above embodiment one.

[0211] The following refers to Figure 16, which shows a schematic diagram of the structure of a data integration device suitable for implementing embodiments of the present application. The data integration device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), and fixed terminals such as digital TVs and desktop computers. Figure 16 The data integration device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0212] like Figure 16 Figure 16 As shown, the data integration device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs loaded from a storage device 1003 into a random access memory 1004. Random access memory 1004 also stores various programs and data required for the operation of the data integration device. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: an input device 1007 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the data integration device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a data integration device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0213] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiments disclosed in the present application are executed.

[0214] The data integration device provided by the present application adopts the data integration method in the above-mentioned embodiments, and can solve the technical problem of how to perform efficient and secure data integration between old enterprise systems and modern SaaS applications. Compared with the prior art, the data integration device provided by the present application has the same beneficial effects as the data integration method provided by the above-mentioned embodiments, and other technical features in the data integration device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0215] It should be understood that parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0216] The above is merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0217] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for performing the data integration method in the above-mentioned embodiments.

[0218] The computer readable storage medium provided in the application may be, for example, a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination thereof. More specific examples of the computer readable storage medium may include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, 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 compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the embodiment, the computer readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), and the like, or any suitable combination thereof.

[0219] The computer readable storage medium described above may be contained in the data integration device, or may exist separately without being assembled into the data integration device.

[0220] The computer readable storage medium described above carries one or more programs, which, when executed by the data integration device, cause the data integration device to: receive a data access interface and a debugging command defined by a user based on a SQL template through an integration platform of a SaaS end, and send the debugging command to a front-end service client of an enterprise local system through a secure communication channel. The front-end service client constructs an actual SQL statement according to the debugging command in combination with input and output parameters in the SQL template, executes when accessing the database, and returns debugging result information to the integration platform for display. After the user confirms that there is no error, the SQL interface information is published, and the platform sends it to the front-end service client for parsing and storage.

[0221] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0222] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may

[0223] The modules involved in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0224] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e., a computer program) for executing the above-mentioned data integration method, and can solve the technical problem of how to efficiently and safely integrate data between an old enterprise system and a modern SaaS application. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the data integration method provided by the above-mentioned embodiments, which will not be described here.

[0225] The application further provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the data integration method as described above.

[0226] The computer program product provided by the application can solve the technical problem of how to efficiently and securely integrate data between an old enterprise system and a modern SaaS application. Compared with the prior art, the beneficial effects of the computer program product provided by the application are the same as those of the data integration method provided by the above-mentioned embodiments, and are not described here.

[0227] The above only describes some embodiments of the application, and does not limit the patent scope of the application. Any equivalent structural transformation, direct / indirect application in other related technical fields, or direct / indirect application in other related technical fields based on the technical concept of the application and the content of the specification and drawings are included in the patent protection scope of the application.

Claims

1. A data integration method, characterized in that: The data integration method is applied to a software as a service (SaaS) end, wherein the SaaS end includes at least one integration platform. The data integration method includes: Receiving, through the integration platform, a data access interface defined by a user based on a structured query language SQL template, and receiving a debugging interface command input by the user; The debugging interface command is sent to the front-end service client of the enterprise local system through a pre-established secure communication channel, so that the front-end service client can construct the actual SQL to be executed based on the debugging interface command and the input and output parameters in the pre-defined SQL template, execute the SQL in the process of accessing the enterprise local database, obtain debugging result information, and return the debugging result information to the SaaS end integration platform through the secure communication channel; Receiving and displaying debugging result information returned by the enterprise local system through the integration platform; Receive the debugged SQL interface information published by the user based on the debugging result information, and send the published SQL interface information to the front-end service client of the enterprise local system through the pre-built secure communication channel, so that the front-end service client parses and stores the received SQL interface information.

2. The data integration method according to claim 1, wherein: Before the step of sending the debugging interface command to the front-end service client of the enterprise local system through the pre-built secure communication channel, the method further includes: Downloading a client certificate from the integration platform; When receiving the front-end certificate sent by the enterprise local system, performing tenant identity and authority verification based on the front-end certificate and the client certificate to obtain a verification result; The verification result is returned to the enterprise local system, so that the enterprise local system establishes a long connection communication with the SaaS end in response to the verification result, and builds a secure communication channel that uses the national encryption algorithm to protect data transmission.

3. The data integration method according to claim 1, wherein: After the step of sending the published SQL interface information to the front-end service client of the enterprise local system through the secure communication channel, the method further includes: Receiving data synchronization task arrangement information defined by a user based on the integration platform; The data synchronization task scheduling information is sent to the front-end service client of the enterprise local system through the pre-built secure communication channel, so that the front-end service client can parse and store the data synchronization task scheduling information, and execute the data synchronization task according to the timing trigger condition in the data synchronization task scheduling information.

4. A data integration method, characterized in that: The data integration method is applied to an enterprise local system, in which a front-end service client is deployed. The data integration method includes: Receive the debugging interface command sent by the SaaS end through a pre-built secure communication channel, and build the actual SQL to be executed based on the debugging interface command and the input and output parameters in the pre-defined SQL template; Execute the SQL statement in the process of accessing the enterprise local database, obtain debugging result information, and return the debugging result information to the SaaS-side integration platform through the pre-built secure communication channel; Receive the published SQL interface information sent by the SaaS end, parse and store the SQL interface information.

5. The data integration method according to claim 4, wherein: Before receiving the debugging interface command sent by the SaaS end through the pre-built secure communication channel, the following steps are also included: When receiving a login instruction, perform the login authentication operation; After successful login authentication, obtain the user information of the currently logged-in user and the remote ciphertext token; Importing the front-end certificate based on the user information and the remote ciphertext token; Sending the front-end certificate to the SaaS end, so that the SaaS end performs tenant identity and authority verification based on the front-end certificate and the client certificate, obtains a verification result, and returns the verification result to the enterprise local system; When it is identified that the verification result returned by the SaaS end is successful, a long connection communication is established with the SaaS end to build a secure communication channel that uses the national encryption algorithm to protect data transmission.

6. The data integration method according to claim 4, wherein: The step of constructing the SQL actually executed according to the debugging interface command and combining the input and output parameters in the predefined SQL template includes: Parsing the debug interface command to obtain an original command, wherein the original command includes an interface identifier and input and output parameters; The corresponding predefined SQL template is searched based on the interface identifier in the original command, and the SQL to be actually executed is generated in combination with the input and output parameters and the pre-configured database connection information.

7. The data integration method according to claim 4, wherein: After the steps of receiving the published SQL interface information issued by the SaaS end, parsing and storing the SQL interface information, the method further includes: Receiving data synchronization task scheduling information sent by the SaaS end through the pre-built secure communication channel; Parse and store the data synchronization task scheduling information, and execute the data synchronization task according to the timing trigger conditions in the data synchronization task scheduling information, wherein the data synchronization task includes regularly grabbing data from the enterprise local database and pushing it to the SaaS end, or pulling data from the SaaS end and synchronizing it to the enterprise local database.

8. The data integration method according to claim 4, wherein: The SQL interface corresponding to the SQL interface information is allowed to be called and accessed by application services in the enterprise's internal network and the front-end service client itself.

9. A data integration system, characterized in that: The data integration system includes SaaS and enterprise local systems. The SaaS end includes: The receiving module is used to receive the data access interface defined by the user based on the SQL template through the integration platform, and receive the debugging interface command input by the user; A debugging command sending module is used to send the debugging interface command to the front-end service client of the enterprise local system through a pre-established secure communication channel, so that the front-end service client can construct the actual SQL to be executed based on the debugging interface command and the input and output parameters in the pre-defined SQL template, execute the SQL in the process of accessing the enterprise local database, obtain debugging result information, and return the debugging result information to the SaaS-side integration platform through the pre-established secure communication channel; A debugging information processing module, configured to receive and display debugging result information returned by the enterprise local system through the integration platform; an interface configuration management module, configured to receive debugged SQL interface information published by a user based on the debugging result information, and send the published SQL interface information to a front-end service client of the enterprise local system through the secure communication channel, so that the front-end service client parses and stores the received SQL interface information; The enterprise local system includes: A construction module is used to receive the debugging interface command sent by the SaaS end through the front-end service client, and construct the SQL actually executed according to the debugging interface command and the input and output parameters in the predefined SQL template; An execution module is used to execute the SQL in the process of accessing the enterprise local database, obtain debugging result information, and return the debugging result information to the SaaS end integration platform through a pre-built secure communication channel; The interface information processing module is used to receive the published SQL interface information sent by the SaaS end, parse and store the SQL interface information.

10. A data integration device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data integration method according to any one of claims 1 to 3 or claims 4 to 8.

11. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data integration method according to any one of claims 1 to 3 or claims 4 to 8 are implemented.

12. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the data integration method according to any one of claims 1 to 3 or claims 4 to 8 are implemented.

Images