Method and device for migrating business system to low-code platform, equipment and medium

By performing code analysis and function recognition on the target business system, combining syntax tree and function call diagram for migration risk detection, and migrating data and business logic, the compatibility of traditional intelligent production systems when migrating to low-code platforms is solved. The problem of sexual, complexity and scalability has achieved efficient and economical migration effects.

CN119396466AInactive Publication Date: 2025-02-07BEIJING LINGYI VISION TECH CO LTD

Patent Information

Application Number
CN202510005453.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-01-03
Publication Date
2025-02-07
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In the prior art, when migrating traditional intelligent production systems to low-code platforms, we face problems such as poor compatibility, high complexity of data migration and poor scalability.

Method used

By performing code analysis on the target business system, syntax tree and function recognition are obtained to obtain the function call diagram, and migration risk detection is carried out. Then, the target business system is mapped and converted to the low-code platform, and the business logic is migrated to generate a new system. Integration tests are performed on the new system, and if it fails, it is optimized and extended.

Benefits of technology

It realizes the secure and effective migration of business systems to low-code platforms, reduces development costs and time, and improves the scalability and updating of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119396466A_ABST
    Figure CN119396466A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of data processing, and provides a method, a device, equipment and a medium for migrating a service system to a low-code platform, on one hand, code analysis is performed on a target service system to obtain a syntax tree, and function identification is performed on the target service system to obtain a function call graph so as to obtain a minimum unit in the migration process; on one hand, migration risk detection is performed on a target business system according to a syntax tree and a function call graph to reduce the migration risk; on one hand, data mapping and conversion are carried out on the target service system to the low-code platform, service logic migration is carried out on the target service system to the low-code platform, the tedious manual coding process in traditional development is avoided through an automatic migration mode, and the development cost and time are reduced; on one hand, integration testing is performed on a new system to ensure normal operation of the migrated system; and on the other hand, the new system is optimized and expanded, so that the expandability and updatability of the system are improved while the compatibility is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, equipment and medium for migrating a business system to a low-code platform. Background Art

[0002] With the rapid development of information technology, traditional intelligent production systems are facing problems such as poor system scalability, long development cycle, and high maintenance costs when facing complex and changing production needs. As an emerging development technology, low-code platforms have gradually become an important tool for enterprise digital transformation with their visual programming, simple operation, and low threshold. Low-code platforms can help enterprises quickly build systems, simplify the development process, and reduce development costs, so they have received widespread attention and application from all walks of life.

[0003] However, in existing technologies, migrating traditional intelligent production systems to low-code platforms still faces many technical challenges, such as system compatibility, complexity of data migration, and automated reconstruction of business processes. Summary of the invention

[0004] In view of the above content, it is necessary to provide a method, device, equipment and medium for migrating a business system to a low-code platform, aiming to solve the problems of poor compatibility, high complexity of data migration and poor scalability when migrating the business system to a low-code platform.

[0005] A method for migrating a business system to a low-code platform, the method comprising: In response to an instruction to migrate a target business system to a low-code platform, code analysis is performed on the target business system to obtain a syntax tree, and function identification is performed on the target business system to obtain a function call graph; Performing migration risk detection on the target business system according to the syntax tree and the function call graph; When the target business system passes the migration risk detection, the target business system is mapped and converted to the low-code platform for data, and the business logic of the target business system is migrated to the low-code platform to obtain a new system corresponding to the business system after migration to the low-code platform; Performing integration testing on the new system; When the new system fails the integration test, the new system is optimized and expanded to obtain a target system.

[0006] According to a preferred embodiment of the present invention, the code analysis of the target business system to obtain a syntax tree and the function identification of the target business system to obtain a function call graph include: Parse the source code of the target business system to obtain each function of the source code and the calling relationship between functions, each class and the inheritance relationship between classes, and each functional module and the reference relationship between functional modules; Abstracting the statements corresponding to each function and each class into nodes, and abstracting the grammatical rules corresponding to the calling relationship between the functions and the inheritance relationship between the classes into edges, to obtain the grammatical tree; Determine the dependency relationship between subclasses, the call chain between subfunctions, the reference method between libraries, and the reference method between packages contained in each functional module according to the reference relationship between the functional modules; Constructing the function call graph according to the dependency relationship between subclasses, the call chain between subfunctions, the reference method between libraries, and the reference method between packages contained in each function module; wherein, each function, each class and each functional module of the source code are correspondingly identified based on the function identifier, the class identifier and the functional module identifier; Each functional module includes business logic, API interface and database operation functional units.

[0007] According to a preferred embodiment of the present invention, the performing migration risk detection on the target business system according to the syntax tree and the function call graph includes: Perform functional comparison and demand matching between the target business system and the low-code platform according to the syntax tree and the function call graph; When the functions of the low-code platform completely cover the syntax tree and the function call graph, it is determined that the target business system passes the migration risk detection; or When the functions of the low-code platform do not completely cover the syntax tree and the function call graph, it is determined that the target business system has failed the migration risk detection.

[0008] According to a preferred embodiment of the present invention, mapping and converting data from the target business system to the low-code platform includes: Creating a Processor plug-in for field mapping and format conversion in Apache NiFi; wherein the Processor plug-in is used to convert data into a configured data format; Package the code of the Processor plug-in into a JAR file; Add the JAR file to the lib directory of the Apache NiFi and restart the Apache NiFi; After restarting the Apache NiFi, creating a data flow of the Processor plug-in in the Web UI of the Apache NiFi to configure the Processor plug-in, and deploying the Processor plug-in to the Apache NiFi; Acquire data from the target business system using a first processor in the Apache NiFi; Using the Processor plug-in to convert the acquired data; Using a second processor in the Apache NiFi to load the converted data into the low-code platform; Wherein, the first processor includes GetFile, GetDatabaseRecord, and ConsumeKafka; The second processor includes PutDatabaseRecord and PutFile.

[0009] According to a preferred embodiment of the present invention, the business logic migration of the target business system to the low-code platform includes: Obtaining the configured business logic format and the business logic of the target business system; The business logic of the target business system is mapped to the low-code platform based on the business logic format, and bound to the data model obtained after data mapping and conversion.

[0010] According to a preferred embodiment of the present invention, the integration test of the new system includes: Obtain each API interface of the new system, and obtain the expected return value and actual return value of each API interface; Compare the expected return value of each API interface with the corresponding actual return value to perform API interface testing on the new system; Verify whether the data in the new system database completely covers the data in the target business system, so as to perform database consistency verification on the new system; Simulating a high-concurrency environment and performing a load test on the new system in the high-concurrency environment to perform a load test on the new system; Regression testing is performed on the new system according to the business logic of the target business system.

[0011] According to a preferred embodiment of the present invention, the optimization and expansion of the new system includes: Get the abnormal points and pre-configured abnormal optimization strategy table; Using the abnormal point to traverse the abnormal optimization strategy table, a target optimization strategy is obtained; Optimizing the new system based on the target optimization strategy; Obtaining expansion requirements for the new system; The new system is expanded according to the expansion requirements.

[0012] A device for migrating a business system to a low-code platform, the device for migrating a business system to a low-code platform comprising: An analysis and identification unit, configured to, in response to an instruction to migrate a target business system to a low-code platform, perform code analysis on the target business system to obtain a syntax tree, and perform function identification on the target business system to obtain a function call graph; A detection unit, configured to perform migration risk detection on the target business system according to the syntax tree and the function call graph; A migration unit, configured to perform data mapping and conversion on the target business system to the low-code platform and migrate the business logic of the target business system to the low-code platform when the target business system passes the migration risk detection, so as to obtain a new system corresponding to the business system after migration to the low-code platform; A testing unit, used for performing integration testing on the new system; The optimization and expansion unit is used to optimize and expand the new system to obtain a target system when the new system fails the integration test.

[0013] A computer device, comprising: a memory storing at least one instruction; and A processor executes instructions stored in the memory to implement a method for migrating the business system to a low-code platform.

[0014] A computer-readable storage medium stores at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement a method for migrating the business system to a low-code platform.

[0015] It can be seen from the above technical solutions that, on the one hand, the code analysis of the target business system is performed to obtain the syntax tree, and the function identification of the target business system is performed to obtain the function call graph to obtain the smallest unit in the migration process; on the one hand, the migration risk of the target business system is detected according to the syntax tree and the function call graph to reduce the migration risk; on the one hand, the data of the target business system is mapped and converted to the low-code platform, and the business logic of the target business system is migrated to the low-code platform. The automated migration mode avoids the tedious manual coding process in traditional development and reduces development costs and time; on the one hand, the new system is integrated tested to ensure the normal operation of the system after migration; on the other hand, the new system is optimized and expanded, which not only ensures compatibility, but also improves the scalability and updatability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a flow chart of a preferred embodiment of the method for migrating a business system to a low-code platform of the present invention; Figure 2 It is a functional module diagram of a preferred embodiment of a device for migrating a business system to a low-code platform of the present invention; Figure 3 It is a structural diagram of a computer device of a preferred embodiment of the method for migrating a business system to a low-code platform of the present invention. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the present invention more clear, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments.

[0018] like Figure 1 As shown, it is a flow chart of a preferred embodiment of the method for migrating a business system to a low-code platform of the present invention. According to different requirements, the order of the steps in the flow chart can be changed, and some steps can be omitted.

[0019] The method for migrating the business system to a low-code platform is applied to one or more computer devices, where the computer device is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0020] The computer device may be any electronic product that can perform human-computer interaction with a user, such as a personal computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a game console, an interactive network television (IPTV), a smart wearable device, etc.

[0021] The computer device may also include a network device and / or a user device, wherein the network device includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud consisting of a large number of hosts or network servers based on cloud computing.

[0022] The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms.

[0023] Among them, Artificial Intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0024] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0025] The network where the computer device is located includes but is not limited to the Internet, a wide area network, a metropolitan area network, a local area network, a virtual private network (VPN), etc.

[0026] S10, in response to an instruction to migrate the target business system to a low-code platform, code analysis is performed on the target business system to obtain a syntax tree, and function identification is performed on the target business system to obtain a function call graph.

[0027] In this embodiment, the target business system may include, but is not limited to: a production system, a management information system, a supply chain management system, etc.

[0028] In this embodiment, the migration instruction may be triggered according to actual business needs.

[0029] In this embodiment, the code analysis of the target business system to obtain a syntax tree and the function identification of the target business system to obtain a function call graph include: Parse the source code of the target business system to obtain each function of the source code and the calling relationship between functions, each class and the inheritance relationship between classes, and each functional module and the reference relationship between functional modules; Abstracting the statements corresponding to each function and each class into nodes, and abstracting the grammatical rules corresponding to the calling relationship between the functions and the inheritance relationship between the classes into edges, to obtain the grammatical tree; Determine the dependency relationship between subclasses, the call chain between subfunctions, the reference method between libraries, and the reference method between packages contained in each functional module according to the reference relationship between the functional modules; Constructing the function call graph according to the dependency relationship between subclasses, the call chain between subfunctions, the reference method between libraries, and the reference method between packages contained in each function module; wherein, each function, each class and each functional module of the source code are correspondingly identified based on the function identifier, the class identifier and the functional module identifier; Each functional module includes business logic, API (Application Programming Interface) interface and database operation functional unit.

[0030] Of course, in other embodiments, a control flow graph may be constructed by parsing source code to display the control flow of code execution and help analyze the calling sequence and dependencies between functions or modules.

[0031] Among them, SonarQube can also be used to assist in detecting code quality, complexity and potential defects. SonarQube can support multiple languages. PMD, Checkstyle, etc. are used for code style and quality detection. PMD and Checkstyle support languages ​​such as Java. Therefore, multi-dimensional detection of the code can be performed before system migration to avoid affecting migration.

[0032] Wherein, Javaparser may be used to parse the Java source code to generate the syntax tree.

[0033] For example, for a Java project, you can use tools such as Javaparser to parse the code and generate the syntax tree, extract the definition of each class, method, and interface, and identify dependencies between modules through dependency injection, inheritance relationships, etc.

[0034] S11, performing migration risk detection on the target business system according to the syntax tree and the function call graph.

[0035] In this embodiment, the performing migration risk detection on the target business system according to the syntax tree and the function call graph includes: Perform functional comparison and demand matching between the target business system and the low-code platform according to the syntax tree and the function call graph; When the functions of the low-code platform completely cover the syntax tree and the function call graph, it is determined that the target business system passes the migration risk detection; or When the functions of the low-code platform do not completely cover the syntax tree and the function call graph, it is determined that the target business system has failed the migration risk detection.

[0036] Through the above-mentioned embodiments, a comprehensive demand analysis and evaluation can be conducted on the target business system. On the basis of clarifying the system functional modules, data structures, business processes, etc., the system can be compared with the functions of the low-code platform to ensure that the migrated system can meet existing needs.

[0037] S12, when the target business system passes the migration risk detection, the data of the target business system is mapped and converted to the low-code platform, and the business logic of the target business system is migrated to the low-code platform to obtain a new system corresponding to the business system after migration to the low-code platform.

[0038] In this embodiment, when the target business system fails the migration risk detection, the risk detection result can be sent to the designated platform, and the relevant migration data can be updated according to the feedback from the platform, and the migration risk can be re-detected after the update to effectively avoid abnormalities in the migration process.

[0039] In this embodiment, mapping and converting data from the target business system to the low-code platform includes: Creating a Processor plug-in for field mapping and format conversion in Apache NiFi; wherein the Processor plug-in is used to convert data into a configured data format; Package the code of the Processor plug-in into a JAR (Java Archive) file; Add the JAR file to the lib directory of the Apache NiFi and restart the Apache NiFi; After restarting the Apache NiFi, creating a data flow of the Processor plug-in in the Web UI of the Apache NiFi to configure the Processor plug-in, and deploying the Processor plug-in to the Apache NiFi; Acquire data from the target business system using a first processor in the Apache NiFi; Using the Processor plug-in to convert the acquired data; Using a second processor in the Apache NiFi to load the converted data into the low-code platform; Wherein, the first processor includes GetFile, GetDatabaseRecord, and ConsumeKafka; The second processor includes PutDatabaseRecord and PutFile.

[0040] The data obtained from the target business system may include a database file, a CSV (Comma-Separated Values) file, an API (Application Programming Interface) file, and the like.

[0041] The Processor plug-in can be used for field mapping, data format conversion, merging, etc. to process data according to customized conversion logic.

[0042] For example: when you need to convert the content of each line of a CSV file to uppercase and then store it in the target folder, you can use GetFile to read the source file, use the created Processor plug-in DataTransformationProcessor to perform data conversion, and finally use PutFile to write the converted file to the target directory to complete the data mapping and conversion.

[0043] Among them, by converting data into the configured data format through the Processor plug-in, the data format can be unified, so that the data model between the low-code platform and the business system can ensure field consistency, data type compatibility and data mapping.

[0044] For example, the unified format can be defined as follows: Tables: used to define a collection of data tables; Columns: The field definition of each table, including field name, data type, and whether it is allowed to be empty; relationships: The relationships between tables, such as one-to-many, many-to-many, etc.

[0045] A unified format can be used to describe the data table structure and its field definitions.

[0046] The Processor plug-in is also used to define data mapping rules so that the data structure of the business system can be mapped to the data table of the low-code platform through the mapping rules during the migration process. For example: map the "employee information" table of the business system (including fields such as employee number, name, department, etc.) to the "employee" table of the low-code platform. The mapping rules can be implemented by defining the field correspondence between the "source table" and the "target table".

[0047] Through the above embodiments, the data model in the business system can be connected with the data model of the low-code platform to ensure seamless data migration. In addition, the use of automated tools to convert data can reduce manual operations and ensure data consistency and accuracy.

[0048] In this embodiment, migrating the business logic of the target business system to the low-code platform includes: Obtaining the configured business logic format and the business logic of the target business system; The business logic of the target business system is mapped to the low-code platform based on the business logic format, and bound to the data model obtained after data mapping and conversion.

[0049] For example: the original business logic can be automatically reconstructed through the visual design tools provided by the low-code platform, and then the original business process can be automatically converted using the process designer, rule engine and other functions of the low-code platform, thereby ensuring that the migrated system can run efficiently.

[0050] In this embodiment, the low-code platform can provide a visual interface design, but the business system may rely on more complex front-end code. Therefore, in order to define a common page structure between the two, the page layout and components can be described in JSON (JavaScript Object Notation) or XML (Extensible Markup Language) format.

[0051] For example, the page structure can be defined as follows: Pages: a collection of pages, used to define the name and layout of each page (such as grid, list, etc.); Components: components in the page. Each component can be a text box, drop-down box, button, etc., and is bound to the data source to form dynamic interaction; data_source: Data source, used to indicate which data table or field the component gets data from.

[0052] Furthermore, the interface elements (such as forms, lists, etc.) in the business system can be mapped to the components of the low-code platform through the page structure. For example, the "employee information" form in the business system can be bound to the data source through the text box component of the low-code platform to achieve data display and interaction.

[0053] In this embodiment, the business logic in the business system may use complex backend code or processes, and the low-code platform usually provides a graphical rule engine and process designer. Therefore, in order to make the business logic interoperable between the two systems, a standard business logic format can be defined, which can be expressed using rules, flowcharts, or scripts.

[0054] For example, the business logic can be defined as follows: business_logic: business logic collection, including the description of each business process; type: defines the logic type, such as workflow, rule, automation, etc. Steps: Describe each step of the business process, including the action, execution conditions, and next step of each step.

[0055] Furthermore, the low-code platform can represent the business system process (such as the approval process) in a unified business logic format (such as using a graphical workflow design tool to represent the approval process) and bind it to the data model. For example, the traditional leave approval process can be integrated with the "employee information form" and "leave application form" through the rule engine of the low-code platform to achieve automatic approval and process control.

[0056] In this embodiment, a unified interface definition can also be performed. It is very important to define standardized API interfaces in the process of integrating the low-code platform with the business system. These interfaces can allow data and logic to flow accurately and efficiently between different systems.

[0057] For example: The API interface definition format is as follows: api: a collection of API interfaces, each of which includes name, HTTP method (such as GET, POST, etc.), request URL, request parameters, and response data format; params: interface request parameter definition; response: format definition of interface response data.

[0058] Furthermore, the low-code platform can interact with the business system through the RESTful API. For example, the low-code platform can obtain employee information from the business system through the GET / api / employees / {employee_id} interface and display it on the page. Similarly, the low-code platform can also submit data to the business system through the interface to ensure data consistency.

[0059] This embodiment enables seamless integration and migration between low-code platforms and traditional business systems by defining a unified data model, page structure, business logic, and interface format. This set of standard formats can not only standardize the data, logic, interface, and interaction methods between systems, but also improve migration efficiency and ensure data consistency and functional integrity.

[0060] S13, performing integration testing on the new system.

[0061] In this embodiment, the integration test of the new system includes: Obtain each API interface of the new system, and obtain the expected return value and actual return value of each API interface; Compare the expected return value of each API interface with the corresponding actual return value to perform API interface testing on the new system; Verify whether the data in the new system database completely covers the data in the target business system, so as to perform database consistency verification on the new system; Simulating a high-concurrency environment and performing a load test on the new system in the high-concurrency environment to perform a load test on the new system; Regression testing is performed on the new system according to the business logic of the target business system.

[0062] For example, you can use JUnit and RestAssured as an integrated testing tool implemented as a testing framework to implement basic system capability testing to verify whether the migrated system collaborates smoothly with external systems, ensure that data can be transmitted and interacted accurately and timely, and enable the system to run stably under normal and abnormal conditions.

[0063] Among them, the correctness of the API interface can be verified through API interface testing. For example, you can make basic settings such as the API address and port for the interface to be tested, and verify whether the interface to be tested returns correct user information, whether the returned HTTP status code is 200, whether the returned user name is "testUser", whether the returned email address is the expected value, and whether the returned status code is 201 (successful creation), etc., so as to verify whether the interface can work normally.

[0064] Among them, database consistency verification can verify whether the data in the system is accurate after data migration. For example, you can use JDBC (Java Database Connectivity) to connect to the database for verification. Specifically, you can query whether there is a specific user in the data table, whether the data is consistent, etc., to verify whether the data after migration is correct.

[0065] Among them, load testing can verify the performance of the system under high concurrency. For example, if 100 concurrent requests are made, you can start multiple threads to simulate concurrent requests, use RestAssured to simulate HTTP requests, and check whether all requests are successfully executed through logs.

[0066] Among them, regression testing can be used to check whether the existing functions of the system have changed due to migration to ensure that the core business logic has not been damaged after migration. For example, the user registration process can be verified, and the return result of the registration can be verified to ensure that the business logic of user registration has not been damaged.

[0067] Through the integration test in the above embodiment, it can be ensured that the migrated system can be smoothly connected with other systems and complete data interaction and transmission.

[0068] S14, when the new system fails the integration test, optimizing and expanding the new system to obtain a target system.

[0069] In this embodiment, when the new system passes the integration test, the new system can be directly determined as the target system.

[0070] In this embodiment, the optimization and expansion of the new system includes: Get the abnormal points and pre-configured abnormal optimization strategy table; Using the abnormal point to traverse the abnormal optimization strategy table, a target optimization strategy is obtained; Optimizing the new system based on the target optimization strategy; Obtaining expansion requirements for the new system; The new system is expanded according to the expansion requirements.

[0071] In the above embodiment, the flexibility and scalability of the low-code platform are used to optimize and adjust the new system, thereby reducing development costs while improving system performance and ensuring that the system can be expanded according to future needs.

[0072] It can be seen from the above technical solutions that, on the one hand, the code analysis of the target business system is performed to obtain the syntax tree, and the function identification of the target business system is performed to obtain the function call graph to obtain the smallest unit in the migration process; on the one hand, the migration risk of the target business system is detected according to the syntax tree and the function call graph to reduce the migration risk; on the one hand, the data of the target business system is mapped and converted to the low-code platform, and the business logic of the target business system is migrated to the low-code platform. The automated migration mode avoids the tedious manual coding process in traditional development and reduces development costs and time; on the one hand, the new system is integrated tested to ensure the normal operation of the system after migration; on the other hand, the new system is optimized and expanded, which not only ensures compatibility, but also improves the scalability and updatability of the system.

[0073] like Figure 2 As shown, it is a functional module diagram of a preferred embodiment of the migration device of the business system to the low-code platform of the present invention. The migration device 11 of the business system to the low-code platform includes an analysis and identification unit 110, a detection unit 111, a migration unit 112, a testing unit 113, and an optimization and expansion unit 114. The module / unit referred to in the present invention refers to a series of computer program segments that can be executed by a processor and can perform fixed functions, which are stored in a memory. In this embodiment, the functions of each module / unit will be described in detail in subsequent embodiments.

[0074] The analysis and identification unit 110 is used to perform code analysis on the target business system to obtain a syntax tree, and perform function identification on the target business system to obtain a function call graph in response to an instruction to migrate the target business system to a low-code platform; The detection unit 111 is used to perform migration risk detection on the target business system according to the syntax tree and the function call graph; The migration unit 112 is used for, when the target business system passes the migration risk detection, mapping and converting the data of the target business system to the low-code platform, and migrating the business logic of the target business system to the low-code platform, to obtain a new system corresponding to the business system after migration to the low-code platform; The testing unit 113 is used to perform integration testing on the new system; The optimization and expansion unit 114 is used to optimize and expand the new system to obtain a target system when the new system fails the integration test.

[0075] It can be seen from the above technical solutions that, on the one hand, the code analysis of the target business system is performed to obtain the syntax tree, and the function identification of the target business system is performed to obtain the function call graph to obtain the smallest unit in the migration process; on the one hand, the migration risk of the target business system is detected according to the syntax tree and the function call graph to reduce the migration risk; on the one hand, the data of the target business system is mapped and converted to the low-code platform, and the business logic of the target business system is migrated to the low-code platform. The automated migration mode avoids the tedious manual coding process in traditional development and reduces development costs and time; on the one hand, the new system is integrated tested to ensure the normal operation of the system after migration; on the other hand, the new system is optimized and expanded, which not only ensures compatibility, but also improves the scalability and updatability of the system.

[0076] like Figure 3 The figure is a schematic diagram of the structure of a computer device of a preferred embodiment of the method for migrating a business system to a low-code platform of the present invention.

[0077] The computer device 1 may include a memory 12, a processor 13 and a bus, and may also include a computer program stored in the memory 12 and executable on the processor 13, such as a migration program for a business system to a low-code platform.

[0078] Those skilled in the art will appreciate that the schematic diagram is merely an example of the computer device 1 and does not constitute a limitation on the computer device 1. The computer device 1 may be a bus-type structure or a star-type structure. The computer device 1 may also include more or less other hardware or software than shown in the diagram, or a different arrangement of components. For example, the computer device 1 may also include input and output devices, network access devices, etc.

[0079] It should be noted that the computer device 1 is only an example, and other existing or future electronic products that are suitable for the present invention should also be included in the protection scope of the present invention and included here by reference.

[0080] Among them, the memory 12 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 12 can be an internal storage unit of the computer device 1, such as a mobile hard disk of the computer device 1. In other embodiments, the memory 12 can also be an external storage device of the computer device 1, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the computer device 1. Further, the memory 12 can also include both an internal storage unit and an external storage device of the computer device 1. The memory 12 can not only be used to store application software and various types of data installed on the computer device 1, such as the code of the migration program of the business system to the low-code platform, but also can be used to temporarily store data that has been output or is to be output.

[0081] In some embodiments, the processor 13 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and a combination of various control chips. The processor 13 is the control core (Control Unit) of the computer device 1, and uses various interfaces and lines to connect the various components of the entire computer device 1. It runs or executes programs or modules stored in the memory 12 (for example, executing a migration program for a business system to a low-code platform, etc.), and calls data stored in the memory 12 to execute various functions of the computer device 1 and process data.

[0082] The processor 13 executes the operating system of the computer device 1 and various installed applications. The processor 13 executes the application to implement the steps in the above-mentioned method of migrating each business system to the low-code platform, for example Figure 1 Steps shown.

[0083] Exemplarily, the computer program may be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 13 to complete the present invention. The one or more modules / units may be a series of computer-readable instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program in the computer device 1. For example, the computer program may be divided into an analysis and identification unit 110, a detection unit 111, a migration unit 112, a test unit 113, and an optimization and expansion unit 114.

[0084] The above-mentioned integrated unit implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a computer device, or a network device, etc.) or a processor to execute a part of the method for migrating a business system to a low-code platform described in various embodiments of the present invention.

[0085] If the module / unit integrated in the computer device 1 is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware devices through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of each of the above-mentioned method embodiments can be implemented.

[0086] The computer program includes computer program code, which may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory, etc.

[0087] Furthermore, the computer-readable storage medium may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to the use of the blockchain node, etc.

[0088] The blockchain referred to in this invention is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the blockchain underlying platform, platform product service layer, and application service layer.

[0089] The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 The bus is represented by only one straight line, but it does not mean that there is only one bus or one type of bus. The bus is configured to realize the connection and communication between the memory 12 and at least one processor 13, etc.

[0090] Although not shown, the computer device 1 may also include a power source (such as a battery) for supplying power to various components. Preferably, the power source may be logically connected to the at least one processor 13 through a power management device, so that the power management device can realize functions such as charging management, discharging management, and power consumption management. The power source may also include any components such as one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, and power status indicators. The computer device 1 may also include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

[0091] Furthermore, the computer device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is usually used to establish a communication connection between the computer device 1 and other computer devices.

[0092] Optionally, the computer device 1 may further include a user interface, which may be a display, an input unit (such as a keyboard), or a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode) touch device. The display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the computer device 1 and to display a visual user interface.

[0093] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited to this structure.

[0094] It can be understood by those skilled in the art that Figure 3 The structure shown does not constitute a limitation on the computer device 1, and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0095] Combination Figure 1 , the memory 12 in the computer device 1 stores a plurality of instructions to implement a method for migrating a business system to a low-code platform, and the processor 13 can execute the plurality of instructions to implement: In response to an instruction to migrate a target business system to a low-code platform, code analysis is performed on the target business system to obtain a syntax tree, and function identification is performed on the target business system to obtain a function call graph; Performing migration risk detection on the target business system according to the syntax tree and the function call graph; When the target business system passes the migration risk detection, the target business system is mapped and converted to the low-code platform for data, and the business logic of the target business system is migrated to the low-code platform to obtain a new system corresponding to the business system after migration to the low-code platform; Performing integration testing on the new system; When the new system fails the integration test, the new system is optimized and expanded to obtain a target system.

[0096] Specifically, the specific implementation method of the processor 13 for the above instructions can refer to Figure 1 The description of the relevant steps in the corresponding embodiments will not be repeated here.

[0097] It should be noted that the data involved in this case were all obtained legally.

[0098] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.

[0099] The present invention can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present invention can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present invention can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0100] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0101] In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional modules.

[0102] It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0103] Therefore, no matter from which point of view, the embodiments should be regarded as illustrative and non-restrictive, and the scope of the present invention is limited by the appended claims rather than the above description, so it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims are included in the present invention. Any attached figure mark in the claims should not be regarded as limiting the claims involved.

[0104] In addition, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the present invention can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

[0105] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solution of the present invention can be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present invention.

Claims

1. A method for migrating a business system to a low-code platform, characterized in that: The method for migrating the business system to the low-code platform includes: In response to an instruction to migrate a target business system to a low-code platform, code analysis is performed on the target business system to obtain a syntax tree, and function identification is performed on the target business system to obtain a function call graph; Performing migration risk detection on the target business system according to the syntax tree and the function call graph; When the target business system passes the migration risk detection, the target business system is mapped and converted to the low-code platform for data, and the business logic of the target business system is migrated to the low-code platform to obtain a new system corresponding to the business system after migration to the low-code platform; Performing integration testing on the new system; When the new system fails the integration test, the new system is optimized and expanded to obtain a target system.

2. The method for migrating a business system to a low-code platform according to claim 1, characterized in that: The code analysis of the target business system to obtain a syntax tree and the function identification of the target business system to obtain a function call graph include: Parse the source code of the target business system to obtain each function of the source code and the calling relationship between functions, each class and the inheritance relationship between classes, and each functional module and the reference relationship between functional modules; Abstracting the statements corresponding to each function and each class into nodes, and abstracting the grammatical rules corresponding to the calling relationship between the functions and the inheritance relationship between the classes into edges, to obtain the grammatical tree; Determine the dependency relationship between subclasses, the call chain between subfunctions, the reference method between libraries, and the reference method between packages contained in each functional module according to the reference relationship between the functional modules; Constructing the function call graph according to the dependency relationship between subclasses, the call chain between subfunctions, the reference method between libraries, and the reference method between packages contained in each function module; wherein, each function, each class and each functional module of the source code are correspondingly identified based on the function identifier, the class identifier and the functional module identifier; Each functional module includes business logic, API interface and database operation functional units.

3. The method for migrating a business system to a low-code platform according to claim 1, characterized in that: The performing migration risk detection on the target business system according to the syntax tree and the function call graph includes: Perform functional comparison and demand matching between the target business system and the low-code platform according to the syntax tree and the function call graph; When the functions of the low-code platform completely cover the syntax tree and the function call graph, it is determined that the target business system passes the migration risk detection; or When the functions of the low-code platform do not completely cover the syntax tree and the function call graph, it is determined that the target business system has failed the migration risk detection.

4. The method for migrating a business system to a low-code platform according to claim 1, characterized in that: The data mapping and conversion of the target business system to the low-code platform includes: Creating a Processor plug-in for field mapping and format conversion in Apache NiFi; wherein the Processor plug-in is used to convert data into a configured data format; Package the code of the Processor plug-in into a JAR file; Add the JAR file to the lib directory of the Apache NiFi and restart the Apache NiFi; After restarting the Apache NiFi, creating a data flow of the Processor plug-in in the Web UI of the Apache NiFi to configure the Processor plug-in, and deploying the Processor plug-in to the Apache NiFi; Acquire data from the target business system using a first processor in the Apache NiFi; Using the Processor plug-in to convert the acquired data; Using a second processor in the Apache NiFi to load the converted data into the low-code platform; Wherein, the first processor includes GetFile, GetDatabaseRecord, and ConsumeKafka; The second processor includes PutDatabaseRecord and PutFile.

5. The method for migrating a business system to a low-code platform according to claim 1, characterized in that: The migrating the business logic of the target business system to the low-code platform includes: Obtaining the configured business logic format and the business logic of the target business system; The business logic of the target business system is mapped to the low-code platform based on the business logic format, and bound to the data model obtained after data mapping and conversion.

6. The method for migrating a business system to a low-code platform as claimed in claim 5, characterized in that: The integration test of the new system includes: Obtain each API interface of the new system, and obtain the expected return value and actual return value of each API interface; Compare the expected return value of each API interface with the corresponding actual return value to perform API interface testing on the new system; Verify whether the data in the new system database completely covers the data in the target business system, so as to perform database consistency verification on the new system; Simulating a high-concurrency environment and performing a load test on the new system in the high-concurrency environment to perform a load test on the new system; Regression testing is performed on the new system according to the business logic of the target business system.

7. The method for migrating a business system to a low-code platform according to claim 1, characterized in that: The optimization and expansion of the new system includes: Get the abnormal points and pre-configured abnormal optimization strategy table; Using the abnormal point to traverse the abnormal optimization strategy table, a target optimization strategy is obtained; Optimizing the new system based on the target optimization strategy; Obtaining expansion requirements for the new system; The new system is expanded according to the expansion requirements.

8. A device for migrating a business system to a low-code platform, characterized in that: The device for migrating the business system to the low-code platform includes: An analysis and identification unit, configured to, in response to an instruction to migrate a target business system to a low-code platform, perform code analysis on the target business system to obtain a syntax tree, and perform function identification on the target business system to obtain a function call graph; A detection unit, configured to perform migration risk detection on the target business system according to the syntax tree and the function call graph; A migration unit, configured to perform data mapping and conversion on the target business system to the low-code platform and migrate the business logic of the target business system to the low-code platform when the target business system passes the migration risk detection, so as to obtain a new system corresponding to the business system after migration to the low-code platform; A testing unit, used for performing integration testing on the new system; The optimization and expansion unit is used to optimize and expand the new system to obtain a target system when the new system fails the integration test.

9. A computer device, characterized in that: The computer device comprises: a memory storing at least one instruction; and A processor executes instructions stored in the memory to implement a method for migrating a business system to a low-code platform as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: At least one instruction is stored in the computer-readable storage medium, and the at least one instruction is executed by a processor in a computer device to implement the method for migrating a business system to a low-code platform as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Pre-verification processing method and device applied to data source migration, equipment and medium

    CN113760946A

  • Low-code application reuse method, application analysis system, equipment and storage medium

    CN115016784A

  • Abnormal code identification method and system, electronic equipment and storage medium

    CN116361194A

  • Data processing method and device applied to low-code application and storage medium

    CN118567702A

  • Distributed ERP system service domain deployment reconstruction method and system

    CN118694812A

Cited By

  • Python dependency library API migration method based on large language model

    CN120429008A

  • Cross-platform software component lightweight migration method

    CN121255379A