An application migration method, device, equipment and storage medium thereof
Through automated parsing and adaptation of modification scripts, combined with a one-click migration tool, automated migration from WebLogic to domestic trusted Java application servers was achieved, solving the problem of large manual workload during the migration process and promoting the promotion of domestic trusted Java application servers.
Patent Information
- Application Number
- CN202411788329.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-05
- Publication Date
- 2025-10-10
- Estimated Expiration
- 2044-12-05
AI Technical Summary
In the existing technology, when migrating the application configuration of the WebLogic enterprise-level Java application server to the domestic trusted enterprise-level Java application server, there is a lack of automated and intelligent solutions, resulting in a large workload of manual work, which affects the promotion and application of the domestic trusted enterprise-level Java application server.
Adopt automated parsing, setting and adaptation modification scripts, obtain main configuration information and deployment location by parsing EAR files, use one-click migration tools for migration, and make adaptation modifications between WebLogic and RockyAS service environments to achieve automated migration.
It reduces the time for manual adaptation modifications, improves the automation and intelligence of the migration process, and promotes the promotion and application of domestic enterprise-level Java application servers.
Smart Images

Figure CN119621148B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of R&D and design technology, and is applied to enterprise-level application migration scenarios, and in particular to an application migration method, apparatus, device, and storage medium thereof. Background Art
[0002] In the current industry market, although there are some solutions for migrating application configurations on WebLogic enterprise-level Java application servers to other enterprise-level Java application servers, assuming that the application server is understood as a hosting "shell", most of the current migration solutions are only applicable to foreign shells corresponding to foreign shells.
[0003] However, there is still a lack of corresponding solutions for converting application servers from WebLogic enterprise-level Java application servers to application servers developed independently by the domestic information and communication technology industry. Or, when faced with domestic information and communication technology enterprise-level Java application servers, there is often a lack of necessary adaptation and optimization, resulting in a large amount of business-related special configuration adjustments and adaptation work during the migration process. This undoubtedly seriously increases the manual workload, is not automated and intelligent enough, and is not conducive to the promotion and application of domestic information and communication technology enterprise-level Java application servers. Summary of the Invention
[0004] The purpose of the embodiments of the present application is to propose an application migration method, device, equipment and storage medium thereof to solve the problem that when migrating the application configuration on the WebLogic enterprise-level Java application server to the domestic trusted enterprise-level Java application server, there is a large amount of manual workload, lack of automation and intelligence, and is not conducive to the promotion and application of the domestic trusted enterprise-level Java application server.
[0005] To solve the above technical problems, the present application provides an application migration method, which adopts the following technical solutions:
[0006] An application migration method includes the following steps:
[0007] Obtain the EAR file corresponding to the enterprise application to be migrated;
[0008] Using an automated parsing script to parse the EAR file, obtain the main configuration information of the enterprise-level application to be migrated, and the deployment locations and execution dependencies between all functional modules involved in the enterprise-level application to be migrated;
[0009] Based on the deployment locations and execution dependencies among all functional modules, an automated setting script is used to set the target deployment location after migration and the execution dependencies after migration;
[0010] Adaptively modify the main configuration information using an automated adaptation modification script to obtain modified main configuration information, wherein the automated adaptation modification script can adaptively modify the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment based on the differences between the WebLogic service environment and the RockyAS service environment;
[0011] Adding the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory specified by the preset one-key migration tool;
[0012] Based on the one-click migration tool, the enterprise-level application to be migrated is migrated, and the application version information of the enterprise-level application to be migrated after migration is obtained.
[0013] Furthermore, before executing the step of using an automated parsing script to parse the EAR file to obtain the main configuration information of the enterprise application to be migrated, as well as the deployment locations and execution dependencies between all functional modules involved in the enterprise application to be migrated, the method further includes:
[0014] encapsulate the automated parsing script and the automated setting script according to a processing logic relationship between the automated parsing script and the automated setting script to obtain a first automated processing subcomponent;
[0015] According to the processing logic relationship between the automated parsing script and the automated adaptation and modification script, the automated parsing script and the automated adaptation and modification script are encapsulated to obtain a second automated processing subcomponent;
[0016] The first automated processing subcomponent and the second automated processing subcomponent are merged to obtain a target automated processing component.
[0017] Furthermore, before executing the step of adding the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory corresponding to the preset one-key migration tool, the method further includes:
[0018] The modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency relationship output by the target automation processing component are obtained.
[0019] Furthermore, after performing the step of adding the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory corresponding to the preset one-key migration tool, the method further includes:
[0020] receiving a one-key migration instruction sent by a preset human-computer interaction interface;
[0021] starting the one-key migration tool according to the one-key migration instruction.
[0022] Further, the step of migrating the to-be-migrated enterprise-level application based on the one-key migration tool to obtain application version information of the to-be-migrated enterprise-level application after migration, specifically includes:
[0023] According to the target execution directory specified by the one-key migration tool, the modified main configuration information, the target deployment position after migration, and the execution dependency relationship after migration are identified.
[0024] According to the modified main configuration information, the target deployment position after migration, and the execution dependency relationship after migration, the to-be-migrated enterprise-level application is migrated.
[0025] Until the to-be-migrated enterprise-level application is migrated, the application version information of the to-be-migrated enterprise-level application after migration is obtained.
[0026] Further, after the step of migrating the to-be-migrated enterprise-level application based on the one-key migration tool to obtain application version information of the to-be-migrated enterprise-level application after migration, the method further includes:
[0027] Running an application program verification script under the RockyAS service environment;
[0028] Based on the application program verification script, the compatibility and program running stability of the to-be-migrated enterprise-level application corresponding to the application version information are verified.
[0029] Obtaining the compatibility and program running stability verification result of the to-be-migrated enterprise-level application.
[0030] Further, after the step of obtaining the to-be-migrated enterprise-level application corresponding to the EAR file, the method further includes:
[0031] Starting the target automation processing component;
[0032] Displaying the automation analysis result, automation setting result, and automation adaptation modification processed by the target automation processing component on the human-computer interaction interface;
[0033] After the step of starting the one-key migration tool according to the one-key migration instruction, the method further includes:
[0034] The migration result corresponding to the one-key migration tool and the verification result corresponding to the application verification script are displayed on the human-computer interaction interface.
[0035] In order to solve the above technical problems, the embodiment of the present application also provides an application migration device, which adopts the following technical solutions:
[0036] An application migration device, comprising:
[0037] EAR file acquisition module, used to obtain the EAR file corresponding to the enterprise-level application to be migrated;
[0038] An automated parsing module, configured to parse the EAR file using an automated parsing script to obtain the main configuration information of the enterprise-level application to be migrated, as well as the deployment locations and execution dependencies between all functional modules involved in the enterprise-level application to be migrated;
[0039] An automated setting module, configured to set a target deployment location after migration and execution dependencies after migration using an automated setting script based on the deployment locations and execution dependencies between all functional modules;
[0040] An automated modification module is configured to adaptively modify the master configuration information using an automated adaptation modification script to obtain the modified master configuration information, wherein the automated adaptation modification script can adaptively modify the master configuration information in the WebLogic service environment to the master configuration information in the RockyAS service environment based on the differences between the WebLogic service environment and the RockyAS service environment;
[0041] An execution adding module is used to add the modified main configuration information, the post-migration target deployment location and the post-migration execution dependency relationship to the target execution directory specified by the preset one-key migration tool;
[0042] The one-key migration module is used to migrate the enterprise-level application to be migrated based on the one-key migration tool and obtain the application version information of the enterprise-level application to be migrated after migration.
[0043] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:
[0044] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the above-mentioned application migration method when executing the computer-readable instructions.
[0045] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:
[0046] A computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the application migration method described above.
[0047] Compared with the prior art, the embodiments of the present application have the following beneficial effects:
[0048] The application migration method described in the embodiment of the present application obtains the EAR file corresponding to the enterprise-level application to be migrated; performs automatic parsing, automatic script setting and automatic adaptation modification on the EAR file, adapts the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment, and adds the target deployment location and execution dependency after migration to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, the enterprise-level application to be migrated is migrated to obtain the application version information after the migration of the enterprise-level application to be migrated. In the entire enterprise-level application migration processing flow, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptation modification time, and to control the migration, making it more automated and intelligent, and conducive to the promotion and application of domestic enterprise-level Java application servers. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] In order to more clearly illustrate the solutions in this application, a brief introduction will be given below to the drawings required for use in the description of the embodiments of this application. Obviously, the drawings described below are some embodiments of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0050] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;
[0051] Figure 2 is a flow chart of an embodiment of the application migration method according to the present application;
[0052] Figure 3 This is a flowchart of a specific embodiment of encapsulating and constructing a target automation processing component in the application migration method described in this application;
[0053] Figure 4 This is a flowchart of a specific embodiment of starting a one-key migration tool in the application migration method described in this application;
[0054] Figure 5 yes Figure 2 A flowchart of a specific embodiment of step 206 is shown;
[0055] Figure 6 This is a flowchart of a specific embodiment of verifying application migration results in the application migration method described in this application;
[0056] Figure 7 is a structural diagram of an embodiment of an application migration device according to the present application;
[0057] Figure 8 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION
[0058] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of the application are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.
[0059] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0060] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.
[0061] like Figure 1 As shown, system architecture 100 may include a terminal device 101, a network 102, and a server 103. Terminal device 101 may be a laptop computer 1011, a tablet computer 1012, or a mobile phone 1013. Network 102 is a medium for providing a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired or wireless communication links or fiber optic cables.
[0062] The user can use the terminal device 101 to interact with the server 103 via the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.
[0063] The terminal device 101 can be various electronic devices with a display screen and supporting web browsing. In addition to the laptop computer 1011, tablet computer 1012 or mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV) player, a laptop computer and a desktop computer, etc.
[0064] The server 103 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal device 101 .
[0065] It should be noted that the application migration method provided in the embodiment of the present application is generally executed by a server, and accordingly, the application migration device is generally set in the server.
[0066] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.
[0067] Continue to refer Figure 2 , shows a flow chart of an embodiment of the application migration method according to the present application. The application migration method includes the following steps:
[0068] Step 201: Obtain the EAR file corresponding to the enterprise application to be migrated.
[0069] In this embodiment, the EAR (Enterprise Archive File) file is a JAR file created for a Java EE application. It is an enterprise application-level JAR file and is a key component when deploying a service application to a production server. An EAR file is a compressed file that contains the libraries, enterprise beans, and JAR files required to deploy the application. An EAR file is a packaged file generated using a JAR (Java Archive) format and is typically packaged as an EAR from an EJB (Enterprise JavaBean). EJB is a Java EE server-side component model provided by Sun Microsystems. EJB is part of Java EE and defines a standard for developing component-based enterprise multi-applications.
[0070] Specifically, an EAR file consists of multiple functional modules, including EJB modules, web modules, and resource adapter modules. The EJB module contains EJB-related classes and configuration files, the web module contains web application classes and packaged static resources, and the resource adapter module contains resource adapter classes for connecting to back-end systems. The EAR file also requires a main configuration file, application.xml, which describes the location and dependencies of each functional module within the EAR file.
[0071] Therefore, by parsing the EAR file and the application.xml, the main configuration information and the dependency relationship between the functional modules can be determined, and the deployment locations of all functional modules can be determined based on the configuration files of the classes corresponding to all functional modules.
[0072] Step 202 : parse the EAR file using an automated parsing script to obtain the main configuration information of the enterprise application to be migrated, as well as the deployment locations and execution dependencies between all functional modules involved in the enterprise application to be migrated.
[0073] By parsing the EAR file, the main configuration information of the enterprise-level application to be migrated, as well as the deployment locations and execution dependencies between all functional modules involved in the enterprise-level application to be migrated, are obtained, so that the configuration information involved in the EAR file can be reset and modified during subsequent application migration.
[0074] Step 203 : Based on the deployment locations and execution dependencies among all the functional modules, an automated setting script is used to set the target deployment location after migration and the execution dependencies after migration.
[0075] By using the automatic setting script to set the post-migration target deployment location and the post-migration execution dependency, the manual setting workload is reduced, and the automation and human consumption are saved.
[0076] In step 204, the main configuration information is adaptively modified by using an automatic adaptive modification script to obtain the modified main configuration information, wherein the automatic adaptive modification script can adaptively modify the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment according to the difference between the WebLogic service environment and the RockyAS service environment.
[0077] In the embodiment, the automatic adaptive modification script is designed according to the difference between the WebLogic service environment and the RockyAS service environment. Currently, the application configuration on the enterprise Java application server in the WebLogic service environment is migrated to the domestic RockyAS enterprise Java application server, for example, the Java application server in the RockyAS service environment. During the migration, a large amount of manual configuration operation is required, which is not only tedious but also limits the development and promotion of the domestic RockyAS enterprise Java application server and lacks the operation and stability guarantee of the migrated enterprise application. Understandably, the development environment and programming language used in the development stage are more compatible with the WebLogic service environment. The WebLogic server is an enterprise Java application server developed by the American Oracle company. For the actual service environment developed by the domestic RockyAS server, which is a Pingan RockyAS enterprise Java application server, there are many limitations in the compatibility of domestic software due to the differences between domestic and foreign.
[0078] By designing the automatic adaptive modification script according to the difference between the WebLogic service environment and the RockyAS service environment, the main configuration information is adaptively modified by using the automatic adaptive modification script to obtain the modified main configuration information, which saves a large amount of manual configuration operation when migrating the application configuration on the enterprise Java application server in the WebLogic service environment to the domestic RockyAS enterprise Java application server.
[0079] In the embodiment, the automatic adaptive modification script, the automatic setting script and the automatic adaptive modification script are automatically processed scripts written according to actual business requirements. The scripts written according to different actual business requirements must have certain differences, which will not be described here.
[0080] Step 205: Add the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory specified by the preset one-key migration tool.
[0081] Specifically, the target execution directory specified by the preset one-key migration tool generally refers to the working directory executed after the one-key migration tool is started.
[0082] By adding the modified main configuration information, the post-migration target deployment location and the post-migration execution dependency to the target execution directory specified by the preset one-click migration tool, so as to follow the executed working directory, the modified main configuration information, the post-migration target deployment location and the post-migration execution dependency are migrated to the enterprise-level Java application server under the RockyAS service environment.
[0083] Step 206 : Migrate the enterprise-level application to be migrated based on the one-click migration tool, and obtain application version information of the enterprise-level application to be migrated after migration.
[0084] In this embodiment, the one-click migration tool is a one-click migration tool that is self-written according to actual business needs.
[0085] In this embodiment, by obtaining the EAR file corresponding to the enterprise-level application to be migrated; automatically parsing, automatically setting scripts and automatically adapting the EAR file, the main configuration information in the WebLogic service environment is adaptively modified to the main configuration information in the RockyAS service environment, and the target deployment location and execution dependencies after migration are added to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, the enterprise-level application to be migrated is migrated, and the application version information after the migration of the enterprise-level application to be migrated is obtained. In the entire enterprise-level application migration processing flow, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptation modification time, and to control the migration, making it more automated and intelligent, and conducive to the promotion and application of domestic enterprise-level Java application servers.
[0086] Continue to refer Figure 3 In some optional implementations, before step 202, a step of encapsulating and constructing a target automation processing component is also included. Figure 3 This is a flowchart of a specific embodiment of encapsulating and constructing a target automation processing component in the application migration method described in this application, including the following steps:
[0087] Step 301: encapsulate the automation parsing script and the automation setting script according to the processing logic relationship between the automation parsing script and the automation setting script to obtain a first automation processing subcomponent;
[0088] Step 302: encapsulate the automated parsing script and the automated adaptation and modification script according to the processing logic relationship between the automated parsing script and the automated adaptation and modification script to obtain a second automated processing subcomponent;
[0089] Step 303: merge the first automation processing subcomponent and the second automation processing subcomponent to obtain a target automation processing component.
[0090] By encapsulating and constructing the automated parsing script, the automated setting script, and the automated adaptation and modification script before one-click migration, a target automated processing component is obtained to encapsulate multiple processing scripts into a unified automated processing component. Only one instruction is required to realize automated processing of multiple scripts.
[0091] In this embodiment, before executing the step of adding the modified main configuration information, the post-migration target deployment location and the post-migration execution dependency to the target execution directory corresponding to the preset one-click migration tool, the method also includes: obtaining the modified main configuration information, the post-migration target deployment location and the post-migration execution dependency output by the target automation processing component.
[0092] Continue to refer Figure 4 In some optional implementations, after step 205, a step of starting a one-key migration tool is also included. Figure 4 This is a flowchart of a specific embodiment of starting a one-click migration tool in the application migration method described in this application, including the following steps:
[0093] Step 401: receiving a one-key migration instruction sent by a preset human-computer interaction interface;
[0094] Step 402: Start the one-key migration tool according to the one-key migration instruction.
[0095] The one-key migration tool is started by starting the command mode in the human-computer interaction interface, thereby realizing migration control during application migration after the automatic processing component completes processing the EAR file.
[0096] Continue to refer Figure 5 , Figure 5 yes Figure 2 The flowchart of a specific embodiment of step 206 includes the following steps:
[0097] Step 501: Identify the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency relationship according to the target execution directory specified by the one-key migration tool;
[0098] Step 502: Migrate the enterprise-level application to be migrated based on the modified main configuration information, the target deployment location after migration, and the execution dependency relationship after migration;
[0099] Step 503 : until the migration of the enterprise-level application to be migrated is completed, the application version information of the enterprise-level application to be migrated after migration is obtained.
[0100] By starting the one-click migration tool and according to the target execution directory, combined with the modified main configuration information under the target execution directory, the post-migration target deployment location and the post-migration execution dependency, the migration of the enterprise-level application to be migrated is achieved. In the entire migration process, only two manual operations are required, namely the startup instructions corresponding to the target automation processing component and the startup instructions corresponding to the one-click migration tool. The purpose of this design is to save time on manual adaptation modifications and to control the migration, making it more automated and in line with actual business needs.
[0101] Continue to refer Figure 6 In some optional implementations, after step 206, a step of verifying the application migration result is also included. Figure 6 This is a flowchart of a specific embodiment of verifying application migration results in the application migration method described in this application, including the following steps:
[0102] Step 601: Run the application verification script in the RockyAS service environment;
[0103] Step 602: Verify the compatibility and program operation stability of the migrated enterprise-level application corresponding to the application version information based on the application verification script;
[0104] Step 603: Obtain the compatibility and program running stability verification results corresponding to the migrated enterprise-level application.
[0105] By running the application verification script in the RockyAS service environment, after migrating the application configuration on the enterprise-level Java application server in the WebLogic service environment to the domestic enterprise-level Java application server, the compatibility of the application migration and the stability of the program operation can be verified, which can provide a certain guarantee for the application migration results.
[0106] In this embodiment, after executing the step of obtaining the EAR file corresponding to the enterprise-level application to be migrated, that is, after step 201, the method further includes: starting the target automation processing component; displaying the automation parsing results, automation setting results, and automation adaptation modification processed by the target automation processing component on the human-computer interaction interface;
[0107] In this embodiment, after executing the step of starting the one-key migration tool according to the one-key migration instruction, the method also includes: displaying the migration result corresponding to the one-key migration tool and the verification result corresponding to the application verification script on the human-computer interaction interface.
[0108] By configuring a human-computer interaction interface for integrated application migration, it is convenient for manual execution of the target automation processing component startup instructions and the one-click migration tool startup instructions in sequence, and it is also convenient for application migration personnel to view the automation processing results, migration results and verification results in real time. This can not only save manual adaptability modification time, but also control and view the migration, making it more automated and in line with actual business needs.
[0109] This application obtains the EAR file corresponding to the enterprise-level application to be migrated; performs automated parsing, automated script setting, and automated adaptive modification on the EAR file, adaptively modifies the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment, and adds the target deployment location and execution dependencies after migration to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, migrates the enterprise-level application to be migrated, and obtains the application version information after the migration of the enterprise-level application to be migrated. In the entire enterprise-level application migration process, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptive modification time, and to control the migration, making it more automated and intelligent, and conducive to the promotion and application of domestic enterprise-level Java application servers.
[0110] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. 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 achieve optimal results.
[0111] Fundamental AI technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interaction systems, and mechatronics. AI software technologies primarily encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.
[0112] In the embodiment of the present application, by obtaining the EAR file corresponding to the enterprise-level application to be migrated; automatically parsing, automatically setting the script and automatically adapting the EAR file, the main configuration information in the WebLogic service environment is adaptively modified to the main configuration information in the RockyAS service environment, and the target deployment location and execution dependency after migration are added to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, the enterprise-level application to be migrated is migrated, and the application version information after the migration of the enterprise-level application to be migrated is obtained. In the entire enterprise-level application migration processing flow, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptation modification time, and to control the migration, which is more automated and intelligent, and is conducive to the promotion and application of domestic enterprise-level Java application servers.
[0113] Further references Figure 7 , as a response to the above Figure 2 In order to realize the method shown in FIG, the present application provides an embodiment of an application migration device. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.
[0114] like Figure 7 As shown, the application migration device 700 of this embodiment includes: an EAR file acquisition module 701, an automatic parsing module 702, an automatic setting module 703, an automatic modification module 704, an execution addition module 705 and a one-key migration module 706.
[0115] EAR file acquisition module 701, used to obtain the EAR file corresponding to the enterprise application to be migrated;
[0116] An automated parsing module 702 is configured to parse the EAR file using an automated parsing script to obtain the main configuration information of the enterprise application to be migrated, as well as the deployment locations and execution dependencies between all functional modules involved in the enterprise application to be migrated;
[0117] An automated setting module 703 is configured to use an automated setting script to set a target deployment location after migration and execution dependencies after migration based on the deployment locations and execution dependencies between all functional modules;
[0118] The automated modification module 704 is configured to adaptively modify the primary configuration information using an automated adaptation modification script to obtain modified primary configuration information. The automated adaptation modification script is capable of adaptively modifying the primary configuration information in the WebLogic service environment to the primary configuration information in the RockyAS service environment based on the differences between the WebLogic service environment and the RockyAS service environment.
[0119] An execution adding module 705 is configured to add the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency relationship to the target execution directory specified by the preset one-key migration tool;
[0120] The one-click migration module 706 is configured to migrate the enterprise-level application to be migrated based on the one-click migration tool, and obtain application version information of the enterprise-level application to be migrated after migration.
[0121] This application obtains the EAR file corresponding to the enterprise-level application to be migrated; performs automated parsing, automated script setting, and automated adaptive modification on the EAR file, adaptively modifies the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment, and adds the target deployment location and execution dependencies after migration to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, migrates the enterprise-level application to be migrated, and obtains the application version information after the migration of the enterprise-level application to be migrated. In the entire enterprise-level application migration process, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptive modification time, and to control the migration, making it more automated and intelligent, and conducive to the promotion and application of domestic enterprise-level Java application servers.
[0122] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware via computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes in the above-described method embodiments. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
[0123] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0124] To solve the above technical problems, the present application also provides a computer device. Figure 8 , Figure 8 This is a basic structural block diagram of the computer device in this embodiment.
[0125] The computer device 8 includes a memory 8a, a processor 8b, and a network interface 8c that are interconnected via a system bus. Figure 8 Only a computer device 8 having components such as a memory 8a, a processor 8b, and a network interface 8c is shown. However, it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead. It should be understood by those skilled in the art that a computer device herein 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 a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), an embedded device, etc.
[0126] The computer device may be a desktop computer, notebook computer, PDA, cloud server, etc. The computer device may interact with the user via a keyboard, mouse, remote control, touchpad, or voice control device.
[0127] The memory 8a includes at least one type of readable storage medium, including flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 8a can be an internal storage unit of the computer device 8, such as the hard disk or memory of the computer device 8. In other embodiments, the memory 8a can also be an external storage device of the computer device 8, such as a plug-in hard disk equipped on the computer device 8, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Of course, the memory 8a can also include both the internal storage unit of the computer device 8 and its external storage device. In this embodiment, the memory 8a is generally used to store the operating system and various application software installed on the computer device 8, such as computer-readable instructions for an application migration method. In addition, the memory 8a can also be used to temporarily store various types of data that have been output or are to be output.
[0128] In some embodiments, the processor 8b may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 8b is generally used to control the overall operation of the computer device 8. In this embodiment, the processor 8b is used to execute computer-readable instructions stored in the memory 8a or process data, such as computer-readable instructions for executing the application migration method.
[0129] The network interface 8c may include a wireless network interface or a wired network interface. The network interface 8c is generally used to establish a communication connection between the computer device 8 and other electronic devices.
[0130] The computer device proposed in this embodiment belongs to the field of research and development design technology, and is used in enterprise-level application migration scenarios. This application obtains the EAR file corresponding to the enterprise-level application to be migrated; performs automatic parsing, automatic script setting and automatic adaptation modification on the EAR file, and adapts the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment, and adds the post-migration target deployment location and execution dependency to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, the enterprise-level application to be migrated is migrated, and the application version information after the migration of the enterprise-level application to be migrated is obtained. In the entire enterprise-level application migration processing flow, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptation modification time, control the migration, make it more automated and intelligent, and be conducive to the promotion and application of domestic enterprise-level Java application servers.
[0131] The present application also provides another embodiment, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by a processor to enable the processor to perform the steps of the application migration method as described above.
[0132] The computer-readable storage medium proposed in this embodiment belongs to the field of research and development design technology, and is applied to enterprise-level application migration scenarios. This application obtains the EAR file corresponding to the enterprise-level application to be migrated; performs automatic parsing, automatic script setting and automatic adaptation modification on the EAR file, and adapts the main configuration information in the WebLogic service environment to the main configuration information in the RockyAS service environment, and adds the post-migration target deployment location and execution dependency to the target execution directory specified by the preset one-click migration tool; based on the one-click migration tool, the enterprise-level application to be migrated is migrated, and the application version information after the migration of the enterprise-level application to be migrated is obtained. In the entire enterprise-level application migration processing flow, only two manual operations are required, namely the target automation processing component startup instruction and the one-click migration tool startup instruction. The purpose of this design is to save manual adaptation modification time, control the migration, make it more automated and intelligent, and be conducive to the promotion and application of domestic enterprise-level Java application servers.
[0133] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.
[0134] Obviously, the embodiments described above are only some of the embodiments of the present application, rather than all of the embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the aforementioned specific embodiments, or to make equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the present application specification and the accompanying drawings, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present application.
Claims
1. An application migration method, characterized in that: The steps include: Obtain the EAR file corresponding to the enterprise application to be migrated; According to the processing logic relationship between the automated parsing script and the automated setting script, the automated parsing script and the automated setting script are encapsulated to obtain a first automated processing subcomponent; According to the processing logic relationship between the automated parsing script and the automated adaptation and modification script, the automated parsing script and the automated adaptation and modification script are encapsulated to obtain a second automated processing subcomponent; Merging the first automated processing subcomponent and the second automated processing subcomponent to obtain a target automated processing component; Using the automated parsing script to parse the EAR file, obtain the main configuration information of the enterprise-level application to be migrated, and the deployment locations and execution dependencies between all functional modules involved in the enterprise-level application to be migrated; According to the deployment locations and execution dependencies among all the functional modules, the automated setting script is used to set the target deployment location after migration and the execution dependencies after migration; The automated adaptation modification script is used to perform adaptability modification on the master configuration information to obtain the modified master configuration information, wherein the automated adaptation modification script can adaptably modify the master configuration information in the WebLogic service environment to the master configuration information in the RockyAS service environment according to the differences between the WebLogic service environment and the RockyAS service environment, and the RockyAS server is a Ping An Xinchuang enterprise-level Java application server; Adding the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory specified by the preset one-key migration tool; Migrating the enterprise-level application to be migrated based on the one-click migration tool and obtaining application version information of the enterprise-level application to be migrated after migration specifically includes: identifying, according to the target execution directory specified by the one-click migration tool, the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency relationship; Migrating the enterprise-level application to be migrated according to the modified main configuration information, the target deployment location after migration, and the execution dependency relationship after migration; Until the migration of the enterprise-level application to be migrated is completed, the application version information of the enterprise-level application to be migrated after migration is obtained.
2. The application migration method according to claim 1, characterized in that: Before performing the step of adding the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory corresponding to the preset one-key migration tool, the method further includes: The modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency relationship output by the target automation processing component are obtained.
3. The application migration method according to claim 2, characterized in that: After performing the step of adding the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency to the target execution directory corresponding to the preset one-key migration tool, the method further includes: Receive a one-key migration instruction sent by a preset human-computer interaction interface; The one-key migration tool is started according to the one-key migration instruction.
4. The application migration method according to claim 3, characterized in that: After executing the steps of migrating the enterprise-level application to be migrated based on the one-click migration tool and obtaining the application version information of the enterprise-level application to be migrated after migration, the method further includes: Run the application verification script in the RockyAS service environment; Verify the compatibility and program operation stability of the migrated enterprise-level application corresponding to the application version information based on the application verification script; Obtain compatibility and program operation stability verification results corresponding to the migrated enterprise-level application.
5. The application migration method according to claim 4, characterized in that: After executing the step of obtaining the EAR file corresponding to the enterprise-level application to be migrated, the method further includes: Starting the target automation processing component; Displaying the automation parsing results, automation setting results, and automation adaptation modifications processed by the target automation processing component on the human-computer interaction interface; After executing the step of starting the one-key migration tool according to the one-key migration instruction, the method further includes: The migration result corresponding to the one-key migration tool and the verification result corresponding to the application verification script are displayed on the human-computer interaction interface.
6. An application migration device, characterized in that: include: EAR file acquisition module, used to obtain the EAR file corresponding to the enterprise-level application to be migrated; A first encapsulation processing module is configured to encapsulate the automation parsing script and the automation setting script according to a processing logic relationship between the automation parsing script and the automation setting script to obtain a first automation processing subcomponent; a second encapsulation processing module, configured to encapsulate the automated parsing script and the automated adaptation and modification script according to a processing logic relationship between the automated parsing script and the automated adaptation and modification script, to obtain a second automated processing subcomponent; an automated processing sub-component merging module, configured to merge the first automated processing sub-component and the second automated processing sub-component to obtain a target automated processing component; An automated parsing module, configured to parse the EAR file using the automated parsing script to obtain the main configuration information of the enterprise-level application to be migrated, as well as the deployment locations and execution dependencies between all functional modules involved in the enterprise-level application to be migrated; An automated setting module, configured to set a target deployment location after migration and execution dependencies after migration using the automated setting script according to the deployment locations and execution dependencies between all the functional modules; An automated modification module is configured to adaptively modify the master configuration information using the automated adaptation modification script to obtain the modified master configuration information, wherein the automated adaptation modification script is capable of adaptively modifying the master configuration information in the WebLogic service environment to the master configuration information in the RockyAS service environment based on the differences between the WebLogic service environment and the RockyAS service environment, wherein the RockyAS server is a Ping An Xinchuang enterprise-level Java application server; An execution adding module is used to add the modified main configuration information, the post-migration target deployment location and the post-migration execution dependency relationship to the target execution directory specified by the preset one-key migration tool; The one-click migration module is used to migrate the enterprise-level application to be migrated based on the one-click migration tool and obtain the application version information of the enterprise-level application to be migrated after migration, specifically including: identifying, according to the target execution directory specified by the one-click migration tool, the modified main configuration information, the post-migration target deployment location, and the post-migration execution dependency relationship; Migrating the enterprise-level application to be migrated according to the modified main configuration information, the target deployment location after migration, and the execution dependency relationship after migration; Until the migration of the enterprise-level application to be migrated is completed, the application version information of the enterprise-level application to be migrated after migration is obtained.
7. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the application migration method according to any one of claims 1 to 5 when executing the computer-readable instructions.
8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the application migration method according to any one of claims 1 to 5.
Citation Information
Patent Citations
Middleware platform migration method and system
CN110177125A
Application migration method and device, electronic equipment and computer readable medium
CN117311804A