Method and device for migrating embedded non-domestic middleware application to domestic middleware
Through the steps of decompression, removal, addition and compression, non-domestic middleware applications are migrated to domestic middleware, which solves the problems of low migration efficiency and difficult to ensure data consistency in the existing technology, and realizes an efficient and stable migration process.
Patent Information
- Application Number
- CN202510048771.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-13
- Publication Date
- 2025-05-09
AI Technical Summary
When the existing technology migrates non-domestic middleware applications to domestic middleware, there are problems such as low migration efficiency, difficulty in ensuring data consistency, and impact on system stability, which cannot support large-scale and complex systems migration.
By decompressing the application package of non-domestic middleware to a temporary folder, traversing and removing the non-domestic middleware module, adding the domestic middleware module, and compressing the application package of the domestic middleware to ensure the stability of the system and the integrity, security and consistency of the data.
It realizes efficient migration of non-domestic middleware applications to domestic middleware, ensures system stability and data consistency, avoids data loss or errors, and improves migration efficiency.
Smart Images
Figure CN119960942A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method and device for migrating an embedded non-domestic middleware application to a domestic middleware. Background Art
[0002] With the deepening of global informatization and the rapid development of the economic environment, the autonomy, controllability and security of key information system applications are of great significance to all walks of life. The middleware services in the systems used by many industries rely on non-domestic products, which poses a risk of data leakage and may fall into the dilemma of insufficient external supply. At the same time, high maintenance costs and potential technical barriers also limit the further development of the system.
[0003] At present, replacing non-domestic middleware applications with domestic service solutions is mostly achieved by directly replacing the middleware, rewriting the interface, or building an intermediate conversion layer. These methods have problems such as low migration efficiency, difficulty in ensuring data consistency, and affected system stability. They cannot support the migration of large-scale and complex systems. Summary of the invention
[0004] In view of this, the present application provides a method and device for migrating embedded non-domestic middleware applications to domestic middleware, removing the non-domestic middleware modules in the application package of the non-domestic middleware, and adding domestic middleware modules to migrate the application package of the non-domestic middleware to the domestic application server middleware, which can ensure the stability of the system and the integrity, security and consistency of the data, avoid data loss or errors, and improve the migration efficiency.
[0005] To solve the above problems, the technical solutions provided by this application are as follows:
[0006] In a first aspect, an embodiment of the present application provides a method for migrating an embedded non-domestic middleware application to a domestic middleware, the migration method comprising:
[0007] In response to executing the middleware migration instruction, decompressing the application package of the non-domestic middleware into a temporary folder;
[0008] Traverse the temporary folder and remove the non-domestic middleware modules;
[0009] Add the domestic middleware module to the temporary folder;
[0010] The temporary folder is compressed to generate an application package of the domestic middleware.
[0011] In a possible implementation, the middleware migration instruction is used to start a script for replacing the domestic middleware, and the script for replacing the domestic middleware carries a directory for placing the non-domestic middleware module;
[0012] The traversing of the temporary folder and removing the non-domestic middleware modules include:
[0013] Using the script for replacing the domestic middleware to traverse the temporary folder, determine the non-domestic middleware module;
[0014] The non-domestic middleware module is removed from the temporary folder.
[0015] In a possible implementation, before compressing the temporary folder to generate the application package of the domestic middleware, the migration method further includes:
[0016] In response to a deployment operation instruction triggered by a user, obtaining a new Web configuration file of the domestic middleware;
[0017] Add the newly added configuration file of the Web application of the domestic middleware to the temporary folder.
[0018] In a possible implementation, before compressing the temporary folder to generate the application package of the domestic middleware, the migration method further includes:
[0019] The Web application configuration file of the non-domestic middleware in the temporary folder is changed to a Web application adaptation configuration file adapted to the domestic middleware.
[0020] In a possible implementation, the migration method further includes:
[0021] In response to a compatible operation instruction triggered by a user, obtaining a new Web configuration file of the domestic middleware;
[0022] Based on the Web newly added configuration file of the domestic middleware, the Web application adaptation configuration file is updated.
[0023] In one possible implementation, the application package of the domestic middleware is any one of JAR or WAR.
[0024] In a second aspect, an embodiment of the present application provides a device for migrating an embedded non-domestic middleware application to a domestic middleware, the migration device comprising:
[0025] A decompression module, for decompressing the application package of the non-domestic middleware into a temporary folder in response to executing the middleware migration instruction;
[0026] A removal module, used to traverse the temporary folder and remove non-domestic middleware modules;
[0027] Adding module, used to add the domestic middleware module to the temporary folder;
[0028] The compression module is used to compress the temporary folder to generate an application package of the domestic middleware.
[0029] In a possible implementation, the middleware migration instruction is used to start a script for replacing the domestic middleware, and the script for replacing the domestic middleware carries a directory for placing the non-domestic middleware module;
[0030] The removal module is specifically used for:
[0031] Using the script for replacing the domestic middleware to traverse the temporary folder, determine the non-domestic middleware module;
[0032] The non-domestic middleware module is removed from the temporary folder.
[0033] In a possible implementation, before executing the compression module, the migration device further includes:
[0034] An acquisition module, used for acquiring a newly added Web configuration file of the domestic middleware in response to a deployment operation instruction triggered by a user;
[0035] The adding module is also used to add a new configuration file of the Web application of the domestic middleware to the temporary folder.
[0036] In a possible implementation, before executing the compression module, the migration device further includes:
[0037] The changing module is used to change the Web application configuration file of the non-domestic middleware in the temporary folder to a Web application adaptation configuration file adapted to the domestic middleware.
[0038] In a possible implementation, the migration device further includes:
[0039] The acquisition module is further used to obtain the Web newly added configuration file of the domestic middleware in response to the compatible operation instruction triggered by the user;
[0040] An update module is used to update the Web application adaptation configuration file based on the Web new configuration file of the domestic middleware.
[0041] In one possible implementation, the application package of the domestic middleware is any one of JAR or WAR.
[0042] In a third aspect, an embodiment of the present application provides a device for migrating an embedded non-domestic middleware application to a domestic middleware, the device comprising: a processor, a memory, and a system bus;
[0043] The processor and the memory are connected via the system bus;
[0044] The memory is used to store one or more programs, and the one or more programs include instructions. When the instructions are executed by the processor, the processor executes the method for migrating embedded non-domestic middleware applications to domestic middleware as described in the first aspect above.
[0045] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a device, the device executes the method of migrating an embedded non-domestic middleware application to a domestic middleware as described in the first aspect above.
[0046] It can be seen that this application has the following beneficial effects:
[0047] An embodiment of the present application provides a method for migrating an embedded non-domestic middleware application to a domestic middleware, executing a middleware migration instruction, decompressing the application package of the non-domestic middleware into a temporary folder, traversing the temporary folder, and removing the non-domestic middleware module. The domestic middleware module is added to the temporary folder, and the temporary folder is compressed to generate an application package for the domestic middleware. In this way, the non-domestic middleware module in the application package of the non-domestic middleware is removed, and the domestic middleware module is added to migrate the application package of the non-domestic middleware to the domestic application server middleware and transform it into an application suitable for a domestic application server. The replacement of modules can ensure the stability of the system and the integrity, security and consistency of the data, avoid data loss or errors, and improve migration efficiency.
[0048] The embodiment of the present application also provides a device corresponding to the above method, which has the same beneficial effects as the above method. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are some implementation methods of the present invention, and for ordinary technicians in this field, other drawings can also be obtained based on these drawings.
[0050] Figure 1 A flowchart of a method for migrating an embedded non-domestic middleware application to a domestic middleware provided in an embodiment of the present application;
[0051] Figure 2 A flowchart of another method for migrating an embedded non-domestic middleware application to a domestic middleware provided in an embodiment of the present application;
[0052] Figure 3A schematic diagram of the structure of a device for migrating an embedded non-domestic middleware application to a domestic middleware provided in an embodiment of the present application;
[0053] Figure 4 A structural diagram of a device for migrating an embedded non-domestic middleware application to a domestic middleware provided in an embodiment of the present application. DETAILED DESCRIPTION
[0054] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0055] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprise", "comprising" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of further restrictions, the elements defined by the statement "comprising a ..." do not exclude the presence of other identical elements in the process, method, article or equipment including the elements.
[0056] Replacing non-domestic middleware applications with domestic service solutions is mostly achieved by directly replacing the middleware, rewriting the interface, or building an intermediate conversion layer. These methods have problems such as low migration efficiency, difficulty in ensuring data consistency, and affected system stability. They cannot support the migration of large-scale and complex systems.
[0057] Therefore, how to efficiently and stably migrate the non-domestic middleware applications embedded in the existing system to the domestic application server middleware without affecting business continuity and user experience; and during the migration process, ensure the integrity, security and consistency of the data to avoid data loss or errors, has become an urgent problem that needs to be solved.
[0058] In view of this, an embodiment of the present application provides a method and device for migrating an embedded non-domestic middleware application to a domestic middleware, executing a middleware migration instruction, decompressing the application package of the non-domestic middleware into a temporary folder, traversing the temporary folder, and removing the non-domestic middleware module. Add the domestic middleware module to the temporary folder, compress the temporary folder to generate an application package for the domestic middleware. In this way, the non-domestic middleware module in the application package of the non-domestic middleware is removed, and the domestic middleware module is added to migrate the application package of the non-domestic middleware to the domestic application server middleware and transform it into an application suitable for a domestic application server. The replacement of modules can ensure the stability of the system and the integrity, security and consistency of the data, avoid data loss or errors, and improve migration efficiency.
[0059] The migration strategy involved in the embodiments of the present application can adapt to the system migration requirements of different scales and different architectures. By developing automated migration tools, streamlining and optimizing the migration process, etc., the migration efficiency can be greatly improved, while reducing manpower, material and time costs, providing users with a more economical and efficient migration solution.
[0060] It should be noted that the middleware mentioned in the embodiments of the present application is divided into domestic middleware and non-domestic middleware. The middleware is application server middleware, which is used to indicate software located between the operating system and the application program and provides a series of services to support the operation and development of enterprise-level applications.
[0061] To facilitate understanding of the technical solution provided by the embodiment of the present application, a method and device for migrating an embedded non-domestic middleware application to a domestic middleware provided by the embodiment of the present application will be described below in conjunction with the accompanying drawings.
[0062] See also Figure 1 , Figure 1 A flowchart of a method for migrating an embedded non-domestic middleware application to a domestic middleware provided in an embodiment of the present application. The method for migrating an embedded non-domestic middleware application to a domestic middleware specifically includes S101-S104.
[0063] S101: In response to executing the middleware migration instruction, the application package of the non-domestic middleware is decompressed into a temporary folder.
[0064] Obtain an application with embedded non-domestic middleware that needs to be modified, and the user issues a middleware migration instruction, or the system automatically issues a middleware migration instruction when non-domestic middleware is detected. The middleware migration instruction can be used to start a script to replace the domestic middleware.
[0065] After starting the script to replace the domestic middleware, the application package of the non-domestic middleware can be unzipped into a temporary folder. The temporary folder can be a pre-created designated folder or a folder automatically generated during the decompression process. The embodiment of the present application is not limited to this.
[0066] The application package of non-domestic middleware can be a JAR package or a WAR package. Unzip the application JAR or WAR package to a temporary folder.
[0067] S102: traverse the temporary folder and remove non-domestic middleware modules.
[0068] The script for replacing domestic middleware has special logic to determine non-domestic middleware modules. When the script is run, all files in the temporary folder after the application package of the non-domestic middleware is unzipped will be traversed to determine the application directory where the non-domestic middleware module is placed.
[0069] Traversing the temporary folder and removing the non-domestic middleware modules may specifically include: traversing the temporary folder using a script for replacing the domestic middleware and determining the non-domestic middleware modules; and removing the non-domestic middleware modules from the temporary folder.
[0070] After determining the application directory of non-domestic middleware modules, remove non-domestic middleware modules such as tomcat, undertow, jetty, etc.
[0071] S103: Add the domestic middleware module to the temporary folder.
[0072] The embodiment of the present application migrates an application package with embedded non-domestic middleware to domestic middleware. Specifically, the non-domestic middleware is removed, and domestic middleware is provided to replace the non-domestic middleware module without changing the low-level implementation logic of the original application package, so that the finally generated compressed package is an independent application with embedded domestic middleware.
[0073] Among them, the functions of domestic middleware modules and non-domestic middleware modules correspond one to one, and domestic middleware modules can be largely compatible with the operations of domestic application servers and have better security.
[0074] After step S103 is completed, the compression step can be automatically executed.
[0075] S104: compress the temporary folder to generate an application package of the domestic middleware.
[0076] When it is determined that all required domestic middleware modules have been added to the temporary folder, the temporary folder can be compressed according to the compression method carried by the middleware migration instruction when starting the middleware replacement to generate an application package of the domestic middleware. The temporary folder is compressed into an independent application embedded with the domestic middleware, and the independent application embedded with the domestic middleware can be a JAR package.
[0077] Specifically, when responding to the middleware migration instruction, the script for replacing the domestic middleware is started, and the replace command or convert command is entered in the script, and the compression method is automatically selected according to the above command. The embodiment of the present application can also obtain the replace command or convert command from the script.
[0078] Replace the non-domestic middleware inside the application JAR package of non-domestic middleware. The application JAR package of domestic middleware generated after replacement can ensure that business data is not lost or damaged during the migration process and maintains a high degree of consistency.
[0079] In one possible implementation, before performing the compression operation, the user can add a Web configuration file of the domestic middleware according to demand.
[0080] The user can trigger the deployment operation instruction, obtain the newly added Web configuration file of the domestic middleware, and add the newly added Web application configuration file of the domestic middleware to the temporary folder. The newly added Web configuration file of the domestic middleware is a file that supports the deployment of the domestic Web server.
[0081] You can also change the Web application configuration file of the non-domestic middleware in the temporary folder to a Web application adaptation configuration file that is adapted to the domestic middleware.
[0082] The Web application adaptation configuration file may not meet the user's needs. In one possible implementation method, the user can also trigger a compatible operation instruction, and executing the compatible operation instruction can obtain the newly added Web configuration file of the domestic middleware.
[0083] Based on the newly added Web configuration file of the domestic middleware, the Web application adaptation configuration file is updated. While supporting the deployment of domestic Web servers, it can be compatible with some functions of non-domestic Web servers to better meet user needs.
[0084] The above deployment operation instructions and compatible operation instructions indicate obtaining a Web application suitable for deployment on a domestic Web server, which can be a WAR package. By preparing the WAR package structure / META-INF / , adding the Web configuration file of the domestic middleware, etc., domestic Web server deployment is supported. Applications based on the non-domestic middleware JAR package structure are quickly and efficiently converted into Web application WAR packages suitable for deployment on domestic Web servers.
[0085] By removing non-domestic middleware application servers, providing domestic application server middleware, or converting them into applications (JAR packages or WAR packages) suitable for domestic application servers, efficient, secure and stable deployment can be achieved. This ensures that users are provided with a convenient and reliable migration path, and promotes the popularization and application of domestic middleware technology.
[0086] The deployed system after migration can maintain or improve the original performance, improve migration efficiency, and provide users with a more economical and efficient migration solution.
[0087] The application package of the above domestic middleware is any one of JAR or WAR.
[0088] See also Figure 2 , Figure 2 A flowchart of another method for migrating an embedded non-domestic middleware application to a domestic middleware is provided in an embodiment of the present application. The embedded non-domestic middleware application is determined, the application is decompressed and the non-domestic middleware module is deleted, the domestic middleware module is added, and finally the domestic middleware package required by the user is packaged according to the user's needs.
[0089] The embodiment of the present application provides both the conversion of non-domestic middleware application JAR packages into domestic middleware application JAR packages and the conversion of non-domestic middleware application JAR packages into domestic Web server deployment to reach Web application WAR packages. Users can choose to convert non-domestic middleware JAR packages into domestic middleware JAR packages, or into WAR packages adapted to domestic servers. The incoming non-domestic middleware WAR package can also be transferred from the deployment of non-domestic middleware to the deployment of adapted domestic middleware. In this way, efficient migration of embedded non-domestic middleware applications to domestic application server middleware is achieved.
[0090] Based on the contents described in S101 to S104 above, the non-domestic middleware is filtered out by decompressing the non-domestic middleware application and deleting the non-domestic middleware modules in the decompressed application. According to user needs, domestic middleware modules are automatically added to transform the embedded non-domestic middleware application into an independent application JAR package with embedded domestic middleware; or the application JAR package structure is converted into a Web application WAR package directory structure, and the Web configuration file of the domestic middleware is automatically added to be suitable for the Web application WAR package deployed by the domestic Web server. The reconstructed system is more stable, can meet the needs of business continuity, reduce manual intervention, and improve the accuracy of the migration process; reduce manpower, material and time costs, and improve the economic benefits of migration.
[0091] The above embodiment of the present application provides a method for migrating an embedded non-domestic middleware application to a domestic middleware based on the above. Next, an apparatus for migrating an embedded non-domestic middleware application to a domestic middleware provided in the embodiment of the present application is described, which is used to perform the above Figure 1 The function of the device for migrating embedded non-domestic middleware applications to domestic middleware is described. The structural schematic diagram of the device for migrating embedded non-domestic middleware applications to domestic middleware is shown in FIG. Figure 3 As shown, it includes a decompression module 301, a removal module 302, an adding module 303 and a compression module 304.
[0092] in,
[0093] The decompression module 301 is used to decompress the application package of the non-domestic middleware into a temporary folder in response to the execution of the middleware migration instruction;
[0094] A removal module 302 is used to traverse the temporary folder and remove non-domestic middleware modules;
[0095] An adding module 303 is used to add the domestic middleware module to the temporary folder;
[0096] The compression module 304 is used to compress the temporary folder to generate an application package of the domestic middleware.
[0097] In a possible implementation, the middleware migration instruction is used to start a script for replacing the domestic middleware, and the script for replacing the domestic middleware carries a directory for placing the non-domestic middleware module;
[0098] The removal module 302 is specifically used for:
[0099] Using the script for replacing the domestic middleware to traverse the temporary folder, determine the non-domestic middleware module;
[0100] The non-domestic middleware module is removed from the temporary folder.
[0101] In a possible implementation, before executing the compression module 304, the migration device further includes:
[0102] An acquisition module, used for acquiring a newly added Web configuration file of the domestic middleware in response to a deployment operation instruction triggered by a user;
[0103] The adding module 304 is also used to add a new configuration file of the Web application of the domestic middleware to the temporary folder.
[0104] In a possible implementation, before executing the compression module 304, the migration device further includes:
[0105] The changing module is used to change the Web application configuration file of the non-domestic middleware in the temporary folder to a Web application adaptation configuration file adapted to the domestic middleware.
[0106] In a possible implementation, the migration device further includes:
[0107] The acquisition module is further used to obtain the Web newly added configuration file of the domestic middleware in response to the compatible operation instruction triggered by the user;
[0108] An update module is used to update the Web application adaptation configuration file based on the Web new configuration file of the domestic middleware.
[0109] In one possible implementation, the application package of the domestic middleware is any one of JAR or WAR.
[0110] For an introduction to an apparatus for migrating an embedded non-domestic middleware application to a domestic middleware provided in an embodiment of the present application, please refer to the above method embodiment, which will not be repeated here.
[0111] The embodiment of the present application provides a device for migrating embedded non-domestic middleware applications to domestic middleware, including a decompression module, a removal module, an addition module and a compression module. The decompression module is used to decompress the application package of the non-domestic middleware into a temporary folder in response to the execution of the middleware migration instruction; the removal module is used to traverse the temporary folder and remove the non-domestic middleware modules; the addition module is used to add the domestic middleware modules to the temporary folder; the compression module is used to compress the temporary folder to generate the application package of the domestic middleware. In this way, the non-domestic middleware modules in the application package of the non-domestic middleware are removed, and the domestic middleware modules are added to migrate the application package of the non-domestic middleware to the domestic application server middleware and transform it into an application suitable for the domestic application server. The replacement of the module can quickly complete the migration, ensure the stability of the system and the integrity, security and consistency of the data, and avoid data loss or errors.
[0112] Based on the method provided in the above method embodiment, a method for migrating an embedded non-domestic middleware application to a domestic middleware is provided. The present application embodiment provides a device for migrating an embedded non-domestic middleware application to a domestic middleware. Figure 4 , the device includes: a processor, a memory, and a system bus;
[0113] The processor and the memory are connected via the system bus;
[0114] The memory is used to store one or more programs, and the one or more programs include instructions. When the instructions are executed by the processor, the processor executes the method of migrating the embedded non-domestic middleware application to the domestic middleware as described in any of the above embodiments.
[0115] Based on a method for migrating an embedded non-domestic middleware application to domestic middleware provided in the above method embodiment, an embodiment of the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a device, the device executes the method for migrating an embedded non-domestic middleware application to domestic middleware as described in any of the above embodiments.
[0116] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device or device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device and device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0117] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0118] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for migrating an embedded non-domestic middleware application to a domestic middleware, characterized in that: Migration methods include: In response to executing the middleware migration instruction, decompressing the application package of the non-domestic middleware into a temporary folder; Traverse the temporary folder and remove the non-domestic middleware modules; Add the domestic middleware module to the temporary folder; The temporary folder is compressed to generate an application package of the domestic middleware.
2. The migration method according to claim 1, characterized in that: The middleware migration instruction is used to start the script for replacing the domestic middleware, and the script for replacing the domestic middleware carries the directory for placing the non-domestic middleware module; The traversing of the temporary folder and removing the non-domestic middleware modules include: Using the script for replacing the domestic middleware to traverse the temporary folder, determine the non-domestic middleware module; The non-domestic middleware module is removed from the temporary folder.
3. The migration method according to claim 1, characterized in that: Before compressing the temporary folder to generate the application package of the domestic middleware, the migration method further includes: In response to a deployment operation instruction triggered by a user, obtaining a new Web configuration file of the domestic middleware; Add the newly added configuration file of the Web application of the domestic middleware to the temporary folder.
4. The migration method according to claim 1, characterized in that: Before compressing the temporary folder to generate the application package of the domestic middleware, the migration method further includes: The Web application configuration file of the non-domestic middleware in the temporary folder is changed to a Web application adaptation configuration file adapted to the domestic middleware.
5. The migration method according to claim 4, characterized in that: The migration method further comprises: In response to a compatible operation instruction triggered by a user, obtaining a new Web configuration file of the domestic middleware; Based on the Web newly added configuration file of the domestic middleware, the Web application adaptation configuration file is updated.
6. The migration method according to claim 1, characterized in that: The application package of the domestic middleware is any one of JAR or WAR.
7. A device for migrating an embedded non-domestic middleware application to a domestic middleware, characterized in that: The migration kit includes: A decompression module, for decompressing the application package of the non-domestic middleware into a temporary folder in response to executing the middleware migration instruction; A removal module, used to traverse the temporary folder and remove non-domestic middleware modules; Adding module, used to add the domestic middleware module to the temporary folder; The compression module is used to compress the temporary folder to generate an application package of the domestic middleware.
8. The migration device according to claim 7, characterized in that: The middleware migration instruction is used to start the script for replacing the domestic middleware, and the script for replacing the domestic middleware carries the directory for placing the non-domestic middleware module; The removal module is specifically used for: Using the script for replacing the domestic middleware to traverse the temporary folder, determine the non-domestic middleware module; The non-domestic middleware module is removed from the temporary folder.
9. The migration device according to claim 7, characterized in that: Before executing the compression module, the migration device further includes: An acquisition module, used for acquiring a newly added Web configuration file of the domestic middleware in response to a deployment operation instruction triggered by a user; The adding module is also used to add a new configuration file of the Web application of the domestic middleware to the temporary folder.
10. The migration device according to claim 7, characterized in that: Before executing the compression module, the migration device further includes: The changing module is used to change the Web application configuration file of the non-domestic middleware in the temporary folder to a Web application adaptation configuration file adapted to the domestic middleware.