Multi-environment application management system

Abstract

The invention relates to a multi-environment application management system, belongs to the technical field of application system development, and solves the problem that in the prior art, a micro-service architecture combined with an agile research and development system cannot support data isolation and environment switching and management. The input module is used for inputting an environment server IP address, an application identifier and service resource data which are determined based on service requirements; the central server sends the timestamp, the application identifier, the service resource data and the first authentication signature to an environment server corresponding to the environment server IP address; and the plurality of environment servers generate a second authentication signature based on the salt value, the timestamp, the application identifier, the second application program interface key and the service resource data, whether the first authentication signature is consistent with the second authentication signature is compared, if yes, the central server is allowed to enter the environment servers, reading operation is realized based on the application identifier, and if not, the central server is allowed to enter the environment servers. And if not, an authentication error is prompted. An application development system which supports data isolation and switching and management of various environments and combines a micro-service architecture with an agile research and development system is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of application system development, and in particular to a multi-environment application management system. Background Art

[0002] For large and complex projects, developers are increasingly inclined to adopt a development approach that combines a microservice architecture with an agile R&D system. This development approach can help companies respond quickly to market changes, improve development efficiency and product quality, reduce project risks, and increase customer satisfaction.

[0003] In the prior art, the systems developed based on the microservice architecture combined with the agile R&D system have the following main problems: (1) Security risks. Frequent communication between microservices may lead to security issues such as data leakage and denial of service attacks. For example, attackers may exploit service vulnerabilities to abuse resources, such as DDoS attacks. (2) Fault propagation. The failure of a service may quickly spread to other services, causing an avalanche effect. (3) Difficulty in maintenance and expansion. The dependencies between services become complex, making it difficult to maintain and expand them independently, which increases the maintenance cost of the system and reduces scalability. (4) The cost of maintaining data consistency is high. (5) Only a single environment is available, and management and switching between multiple environments cannot be achieved.

[0004] Therefore, it is necessary to provide an application development system that supports data isolation and switching and management of various environments combined with a microservice architecture and an agile R&D system. Summary of the invention

[0005] In view of the above analysis, an embodiment of the present invention aims to provide a multi-environment application management system to solve the problem that the existing microservice architecture combined with the agile R&D system cannot support data isolation and switching and management of various environments.

[0006] An embodiment of the present invention provides a multi-environment application management system, including:

[0007] An input module, used to input an environment server IP address, application identifier, and business resource data determined based on business requirements;

[0008] The central server obtains the first application program interface key corresponding to the IP address of the environment server, generates a first authentication signature based on the salt value, the timestamp, the application identifier, the first application program interface key and the business resource data, and sends the timestamp, the application identifier, the business resource data and the first authentication signature to the environment server corresponding to the IP address of the environment server;

[0009] Multiple environment servers determine whether the received data contains a timestamp, an application identifier, business resource data, and a first authentication signature. If so, determine whether the difference between the timestamp and the current system timestamp exceeds a preset threshold. If not, obtain a second application interface key corresponding to the environment server, generate a second authentication signature based on the salt value, timestamp, application identifier, second application interface key, and business resource data, and compare the first authentication signature with the second authentication signature to see if they are consistent. If they are consistent, allow the central server to enter the environment server and implement a read operation based on the application identifier. If they are inconsistent, prompt an authentication error.

[0010] Based on further improvement of the above method, the multiple environment servers are research and development environment servers, test environment servers, acceptance environment servers or production environment servers.

[0011] Based on the further improvement of the above method, the central server is used for public data management in a multi-environment application management system, data management of environmental servers, and supports remote call services; the public data includes application information data, service information data, and environmental service authority information data.

[0012] Based on the further improvement of the above method, the application identifier includes: dictionary data reading operation interface class identifier, form design reading operation interface class identifier, static resource reading operation interface class identifier, permission reading operation interface class identifier, aggregate table reading operation interface class identifier, and middleware reading operation interface class identifier.

[0013] Based on the further improvement of the above method, the environment server assigns an application identifier to each read service of the middleware based on business needs, thereby forming different middleware read operation interface class identifiers; the middleware includes: Gitlab, Apollo, Gateway, Xxljob; the read services include: paging query, detail query, save, modify, and delete.

[0014] Based on the further improvement of the above method, the central server also includes: a synchronization configuration module, which is used to achieve data synchronization between the current environment server and the target environment server.

[0015] Based on the further improvement of the above method, the data synchronization between the current environment server and the target environment server is achieved, including: formulating a synchronization test plan on the central server, the synchronization test plan including the version number, the IP address of the current environment server, and the IP address of the target environment server; obtaining first configuration information of the current environment server and second configuration information of the target environment server, and obtaining configuration differences based on the first configuration information and the second configuration information, the configuration differences including application configuration differences, service configuration differences, middleware configuration differences, menu configuration differences, whitelist configuration differences, resource configuration differences, data dictionary configuration differences, IP address differences, domain name address differences, and account name and password differences; based on the configuration differences, the synchronization of the current environment server and the target environment server is achieved.

[0016] Based on the further improvement of the above method, the configuration difference is obtained based on the first configuration information and the second configuration information, including: for each data in the first configuration information, if the data exists in the first configuration information but not in the second configuration information, the first configuration information data is returned, marked as a newly added type, and stored in a newly added record; if the data does not exist in the first configuration information but exists in the second configuration information, the second configuration information data is returned, marked as a deleted type, and stored in a deleted record; if the data exists in the first configuration information and the second configuration information, the data is converted into JSON data format, the key value is read cyclically, and the value values ​​in the first configuration information and the second configuration information are compared. If they are consistent, they are skipped and no change record is made. If they are inconsistent, they are marked as modified, marked as a change type, and stored in a change record; the new record, the deletion record and the change record are used as configuration differences, and the configuration differences include middleware type, application identifier, data, new type / deletion type / change type, and the configuration differences are stored in a database.

[0017] Based on the further improvement of the above method, the synchronization of the current environment server and the target environment server is achieved based on configuration differences, including: the central server reads the configuration differences from the database, the tester checks and verifies the configuration differences based on business requirements, and if the verification passes, the central server sends the configuration differences to the target environment server, and the target environment server modifies the second configuration information of the target environment server according to the configuration differences.

[0018] Based on a further improvement of the above method, the target environment server modifies the second configuration information of the target environment server according to the configuration difference, including: the target environment server performs a backup operation on the second configuration information, and after the backup operation is completed, reads the configuration difference and modifies the second configuration information; if the configuration difference information is a new addition type or a change type, reads the middleware type in the current environment server in the configuration difference information, compares whether the middleware type is consistent with the middleware type in the target environment server, and if they are consistent, performs a new addition or change operation; if the configuration information is a deletion type, reads the middleware type in the current environment server in the configuration difference information, compares whether the middleware type is consistent with the middleware type in the target environment server, and if they are consistent, obtains the application identifier recorded in the configuration difference information, and deletes the corresponding data in this configuration information under the application identifier.

[0019] Compared with the prior art, the present invention can achieve at least one of the following beneficial effects:

[0020] 1. The present invention provides a multi-environment application management system. The central server accesses the corresponding environment server based on the environment server IP address determined by business needs. Only when the signature authentication is consistent can the central server be allowed to enter the environment corresponding to the IP address, thereby further improving the security of data management of the application management system.

[0021] 2. The present invention provides a multi-environment application management system, which is implemented using a 1+N technical development model, i.e., a development model of a central server and multiple environment servers. The management of public data and the loading and calling of environment switching are placed on the central server. The IP address of each environment is fixed, and it is only responsible for completing the development of the corresponding functions. The central server implements the switching and management of the environment based on the IP address of each environment, thereby isolating each sub-environment of the implementation class, further reducing the security risk and the risk of fault propagation. In addition, the exchange of data between each environment must be implemented through the central server, and each environment is independent of each other and does not affect each other, further reducing the difficulty of maintenance and expansion of the management system.

[0022] In the present invention, the above-mentioned technical solutions can also be combined with each other to achieve more preferred combination solutions. Other features and advantages of the present invention will be described in the subsequent description, and some advantages can become obvious from the description, or can be understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained through the contents particularly pointed out in the description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings are only used for the purpose of illustrating specific embodiments and are not to be considered as limiting the present invention. In the entire drawings, the same reference symbols represent the same components;

[0024] Figure 1 This is an example diagram of a multi-environment application management system in an embodiment of the present invention. DETAILED DESCRIPTION

[0025] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings, wherein the accompanying drawings constitute a part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not used to limit the scope of the present invention.

[0026] Microservice architecture is a software development architecture that decomposes a monolithic application into a set of small services. Each service runs in its own independent process and is usually built around specific business capabilities. These services can communicate through well-defined APIs, usually HTTP RESTful APIs or lightweight messaging systems.

[0027] Agile R&D system is a human-centered, iterative, and step-by-step software development methodology. It emphasizes responding quickly to customer needs and continuously delivering high-quality software products through flexible and efficient teamwork in a rapidly changing market environment.

[0028] In view of the problems of security risks, fault propagation, inability to manage and switch between multiple environments, etc. in systems developed based on microservice architecture combined with agile R&D system, the present invention proposes a multi-environment application management system to solve the problem that the existing microservice architecture combined with agile R&D system cannot support data isolation and switching and management of various environments.

[0029] A specific embodiment of the present invention discloses a multi-environment application management system, such as Figure 1 As shown, including:

[0030] The input module is used to input the environment server IP address, application identifier and business resource data determined based on business requirements.

[0031] The central server obtains the first application program interface key corresponding to the IP address of the environment server, generates a first authentication signature based on the salt value, the timestamp, the application identifier, the first application program interface key and the business resource data, and sends the timestamp, the application identifier, the business resource data and the first authentication signature to the environment server corresponding to the IP address of the environment server.

[0032] Multiple environment servers determine whether the received data contains a timestamp, an application identifier, business resource data, and a first authentication signature. If so, determine whether the difference between the timestamp and the current system timestamp exceeds a preset threshold. If not, obtain a second application interface key corresponding to the environment server, generate a second authentication signature based on the salt value, timestamp, application identifier, second application interface key, and business resource data, and compare the first authentication signature with the second authentication signature to see if they are consistent. If they are consistent, allow the central server to enter the environment server and implement a read operation based on the application identifier. If they are inconsistent, prompt an authentication error.

[0033] The input module is usually located on the front-end operation interface of the application management system. System users can specify the environment server according to business needs, and then the central server communicates with the environment server according to the IP address of the specified environment server.

[0034] The application identifier includes the dictionary data read operation interface class identifier, the form design read operation interface class identifier, the static resource read operation interface class identifier, the permission read operation interface class identifier, the aggregate table read operation interface class identifier, and the middleware read operation interface class identifier. For example, the application management system developer pre-builds the dictionary data read operation interface class Dict.class, the form design read operation interface class Form.class, the static resource read operation interface class Resource.class, the form permission read operation interface class Auth.class, the form aggregate table read operation interface class View.class, the middleware read operation interface class Midd1eware.class (used to define configuration paging query, detail query, save, modify, delete interface, etc.), the configuration read operation interface class Config.class, etc. based on the business logic.

[0035] It can be understood that each environment server will have data reading operations. In order to distinguish the dictionary data reading operations, form design reading operations, etc. of each environment server, the environment server assigns an application identifier to each reading service based on business needs, thereby forming different reading operation interface class identifiers. Exemplarily, the environment server assigns an application identifier to each reading service of the middleware based on business needs, thereby forming different middleware reading operation interface class identifiers; the middleware includes: Gitlab, Apol11o, Gateway, Xxljob; the reading service includes: paging query, detail query, save, modify, delete. The implementation logic of each of the above interface classes is set according to actual business needs, and the present invention does not limit it here. The application identifier corresponds to each interface class identifier one by one, and is used to limit the specific operations of each environment server. System users can determine the operation of the specified environment server based on business needs, and thus determine the corresponding application identifier according to the operation.

[0036] The business resource data includes dictionary data information, form data information, static resource data information, permission data information, aggregate table data information, and middleware data information. It can be understood that the above data are all stored on each environment server, and the system user determines the target data of the specified environment server based on business needs, and then implements the reading operation according to the interface class corresponding to the application identifier.

[0037] The central server receives the request information sent by the input module, determines the environment server to be accessed based on the environment server IP address, and triggers the corresponding interface class based on the application identifier, thereby realizing the remote call to the environment server and performing corresponding operations according to the business resource data.

[0038] When accessing the environment server, signature authentication should be performed first. The central server generates a first authentication signature based on the salt value, timestamp, the application identifier, the first application program interface key, and the business resource data. After generating the first authentication signature, the central server sends the timestamp, application identifier, business resource data, and the first authentication signature to the environment server corresponding to the IP address of the environment server. The generation rule of the authentication signature is:

[0039] MD5 (salt value + timestamp + application identifier + first application program interface key + business resource data).

[0040] The central server is used for public data management in the multi-environment application management system, data management of the environment server, and supports remote call services; the public data includes application information data, service information data, and environment service authority information data. Specifically, the central server is responsible for managing all functional data in the application management system, including the management of public basic data, the loading and calling of environment data, and providing page functions for the first two types of data operations.

[0041] The central server is responsible for scheduling access to each environment server. Based on business needs, it reads dictionaries, form designs, static resources, form permission configurations, aggregation tables, middleware and other data information related to application information in different environment servers, thereby manipulating application functions in different environment servers based on business needs. In addition, each environment server cannot directly interact with data or business, and must be implemented through the scheduling of the central server, thereby achieving data isolation of each environment server.

[0042] In the R&D management cycle requirements of the microservice architecture and agile R&D system, four environments are usually divided into R&D, testing, acceptance, and production. This approach facilitates the continuous iteration of applications and realizes agile development and agile delivery of services. For example, after the software development is completed on the R&D environment server, the software needs to be tested, but the test environment server and the R&D environment server are data isolated. System users cannot directly deploy the software on the test environment server for testing. Data migration is required through the synchronization configuration function of the central server to ensure that the configuration data in the test environment server is consistent with the configuration data of the R&D environment server. Therefore, the central server also includes: a synchronization configuration module, which is used to achieve data synchronization between the current environment server and the target environment server. Specifically, data synchronization between the current environment server and the target environment server is achieved through the following steps:

[0043] A1: A synchronization test plan is formulated on the central server, wherein the synchronization test plan includes a version number, an IP address of a current environment server, and an IP address of a target environment server.

[0044] Among them, the version number is used to distinguish different software versions, making it easier for system users to distinguish test versions.

[0045] A2: Obtain the first configuration information of the current environment server and the second configuration information of the target environment server, and obtain configuration differences based on the first configuration information and the second configuration information. The configuration differences include application configuration differences, service configuration differences, middleware configuration differences, menu configuration differences, whitelist configuration differences, resource configuration differences, data dictionary configuration differences, IP address differences, domain name address differences, and account name and password differences.

[0046] The obtaining a configuration difference based on the first configuration information and the second configuration information includes:

[0047] For each piece of data in the first configuration information, if the data exists in the first configuration information but not in the second configuration information, the first configuration information data is returned, marked as a newly added type, and stored in a newly added record; if the data does not exist in the first configuration information but exists in the second configuration information, the second configuration information data is returned, marked as a deleted type, and stored in a deleted record; if the data exists in the first configuration information and in the second configuration information, the data is converted into JSON data format, the key value is read in a loop, and the value values ​​in the first configuration information and the second configuration information are compared. If they are consistent, they are skipped and no change record is made. If they are inconsistent, they are marked as modified, marked as a change type, and stored in a change record; the newly added record, the deleted record, and the change record are used as configuration differences, and the configuration differences include middleware type, application identifier, data, new type / deleted type / change type, and the configuration differences are stored in a database.

[0048] A3: Synchronizing the current environment server and the target environment server based on configuration differences; specifically, this step includes:

[0049] The central server reads the configuration difference from the database, and the tester verifies the configuration difference based on business requirements. If the verification is successful, the central server sends the configuration difference to the target environment server, and the target environment server modifies the second configuration information of the target environment server based on the configuration difference. If the verification fails, the tester can choose to regenerate the configuration difference or directly modify the generated configuration difference until it meets the verification requirements. Exemplarily, the configuration difference can be displayed on the front end in the 1ist data format.

[0050] Exemplarily, the tester's verification of the configuration difference can be the verification of the IP address of the environment server (i.e., judging whether the IP address of the current environment server is normal). Since the method proposed by the present invention is to achieve data isolation of each environment server, it is necessary to further check and verify the IP address of the target environment server; it can be the verification of login verification information such as account and password or user authority information to ensure that after the central server establishes a link with the environment server, the system user has the authority to perform corresponding interface operations on the environment server; it can be the data dictionary name, form name, etc., to ensure that the data operated in the environment server meets the business requirements. When the tester passes the verification, the target environment server can be entered through the central server. If the verification fails, the tester can choose to regenerate the configuration difference or directly modify the generated configuration difference until it meets the verification requirements. Preferably, verify whether the content in the synchronization test plan is wrong, and then modify the erroneous content and regenerate the configuration difference. Furthermore, the tester can also report the error and wait for the operation and maintenance personnel to solve it.

[0051] The target environment server modifies the second configuration information of the target environment server according to the configuration difference, including:

[0052] The target environment server performs a backup operation on the second configuration information, and after the backup operation is completed, reads the configuration difference and modifies the second configuration information;

[0053] If the configuration difference information is of a new addition type or a change type, read the middleware type in the current environment server in the configuration difference information, and compare whether the middleware type is consistent with the middleware type in the target environment server. If they are consistent, perform a new addition or change operation; if the configuration information is of a deletion type, read the middleware type in the current environment server in the configuration difference information, and compare whether the middleware type is consistent with the middleware type in the target environment server. If they are consistent, obtain the application identifier recorded in the configuration difference information, and delete the corresponding data in this configuration information under the application identifier.

[0054] Exemplarily, based on the method proposed by the present invention, each environment server is implemented based on one or more middlewares in Gitlab, Apollo, Gateway, and Xxljob. Therefore, after determining the target environment server, in order to ensure that the data is added or changed correctly, it is also necessary to further confirm whether the middleware type in the current environment server in the configuration information is consistent with the middleware type in the target environment server. Only when the middleware type in the current environment server is consistent with the middleware type in the target environment server, can the data addition and change operation be performed. If the IP address of the target environment server is correct when performing the operation of adding or changing the type, and the middleware type in the current environment server in the configuration information is inconsistent with the middleware type in the target environment server, the tester can check whether the current configuration difference data is wrong. If there is an error, the configuration difference can be modified directly, or the content in the synchronization test plan can be verified. Whether it is wrong, and then modify the error content, and regenerate the configuration difference, the above methods are all to ensure the correct execution of the data operation in the target environment server. Further, the tester can also report the error and wait for the operation and maintenance personnel to solve it.

[0055] It can be understood that the configuration information of the current target environment server is backed up to prevent the synchronization operation from modifying too much configuration information, making the modified configuration unsuitable for other operations. Therefore, when the user needs to use the configuration of the current target environment server to complete certain operations next time, the data can be quickly restored to ensure business continuity.

[0056] The multiple environment servers can be development environment servers, test environment servers, acceptance environment servers or production environment servers.

[0057] It is understandable that the data received by the environment server may come from the central server or from other servers. Whether it is the central server or other servers, there may be the following problems, for example, the central server sends an error, resulting in it not communicating data with the specified environment server, or the data sent by other servers may cause harm to the environment server, such as network attacks, etc. Therefore, the environment server needs to perform format verification and timestamp verification on the received data. Specifically, the environment server must first determine whether the received data contains a timestamp, an application identifier, business resource data, and a first authentication signature. If not, it prompts an authentication error. If it does, it performs timestamp verification to determine whether the difference between the timestamp and the current system timestamp exceeds a preset threshold. If it exceeds the preset threshold, it prompts an authentication error. If it does not exceed, the second application interface key corresponding to the environment server is obtained, and a second authentication signature is generated based on the salt value, timestamp, application identifier, second application interface key, and business resource data. Compare whether the first authentication signature is consistent with the second authentication signature. If they are consistent, the central server is allowed to enter the environment server and implement a read operation based on the application identifier. If they are inconsistent, an authentication error is prompted. The preset threshold is 2 minutes, and the rule for generating the second authentication signature is the same as the rule for generating the first authentication signature.

[0058] Compared with the prior art, the present invention provided in this embodiment provides a multi-environment application management system, in which the central server accesses the corresponding environment server based on the IP address of the environment server determined by business needs, and only when the signature authentication is consistent can the central server be allowed to enter the environment corresponding to the IP address, thereby further improving the security of data management of the application management system; it adopts a 1+N technical development model, that is, a development model of one central server and multiple environment servers, and places the management of public data and the loading and calling of environment switching on the central server. The IP address of each environment is fixed, and it is only responsible for completing the development of corresponding functions. The central server realizes the switching and management of the environment based on the IP address of each environment, thereby isolating the implementation class from each sub-environment, further reducing security risks and fault propagation risks; data exchange between each environment must be realized through the central server, and each environment is independent of each other and does not affect each other, further reducing the maintenance difficulty and expansion difficulty of the management system.

[0059] Those skilled in the art will appreciate that all or part of the processes of the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, wherein the computer-readable storage medium is a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0060] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by any technician familiar with the technical field within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention.

Claims

1. A multi-environment application management system, characterized in that: include: An input module, used to input an environment server IP address, application identifier, and business resource data determined based on business requirements; The central server obtains the first application program interface key corresponding to the IP address of the environment server, generates a first authentication signature based on the salt value, the timestamp, the application identifier, the first application program interface key and the business resource data, and sends the timestamp, the application identifier, the business resource data and the first authentication signature to the environment server corresponding to the IP address of the environment server; Multiple environment servers determine whether the received data contains a timestamp, an application identifier, business resource data, and a first authentication signature. If so, determine whether the difference between the timestamp and the current system timestamp exceeds a preset threshold. If not, obtain a second application interface key corresponding to the environment server, generate a second authentication signature based on the salt value, timestamp, application identifier, second application interface key, and business resource data, and compare the first authentication signature with the second authentication signature to see if they are consistent. If they are consistent, allow the central server to enter the environment server and implement a read operation based on the application identifier. If they are inconsistent, prompt an authentication error.

2. A multi-environment application management system according to claim 1, characterized in that: The multiple environment servers are research and development environment servers, test environment servers, acceptance environment servers or production environment servers.

3. A multi-environment application management system according to claim 2, characterized in that: The central server is used for public data management in the multi-environment application management system, data management of the environment server, and supports remote call services; The public data includes application information data, service information data, and environment service authority information data.

4. A multi-environment application management system according to claim 3, characterized in that: The application identifiers include: dictionary data reading operation interface class identifier, form design reading operation interface class identifier, static resource reading operation interface class identifier, permission reading operation interface class identifier, aggregate table reading operation interface class identifier, and middleware reading operation interface class identifier.

5. A multi-environment application management system according to claim 4, characterized in that: The environment server assigns an application identifier to each read service of the middleware based on business requirements, thereby forming different middleware read operation interface class identifiers; The middleware includes: Gitlab, Apollo, Gateway, Xxljob; the reading service includes: paging query, detail query, save, modify, and delete.

6. A multi-environment application management system according to claim 5, characterized in that: The central server also includes: The synchronization configuration module is used to synchronize data between the current environment server and the target environment server.

7. A multi-environment application management system according to claim 6, characterized in that: The step of implementing data synchronization between the current environment server and the target environment server includes: Formulate a synchronization test plan on the central server, wherein the synchronization test plan includes a version number, an IP address of a current environment server, and an IP address of a target environment server; Obtaining first configuration information of a current environment server and second configuration information of a target environment server, and obtaining configuration differences based on the first configuration information and the second configuration information, wherein the configuration differences include application configuration differences, service configuration differences, middleware configuration differences, menu configuration differences, whitelist configuration differences, resource configuration differences, data dictionary configuration differences, IP address differences, domain name address differences, and account name and password differences; The current environment server and the target environment server are synchronized based on the configuration difference.

8. A multi-environment application management system according to claim 7, characterized in that: The obtaining a configuration difference based on the first configuration information and the second configuration information includes: For each piece of data in the first configuration information, if the data exists in the first configuration information but not in the second configuration information, the first configuration information data is returned, marked as a newly added type, and stored in a newly added record; if the data does not exist in the first configuration information but exists in the second configuration information, the second configuration information data is returned, marked as a deleted type, and stored in a deleted record; if the data exists in the first configuration information and in the second configuration information, the data is converted into JSON data format, the key value is read in a loop, and the value values ​​in the first configuration information and the second configuration information are compared. If they are consistent, they are skipped and no change record is made. If they are inconsistent, they are marked as modified, marked as a change type, and stored in a change record; The newly added record, the deleted record and the changed record are used as configuration differences, the configuration differences include middleware type, application identifier, data, new added type / deleted type / changed type, and the configuration differences are stored in a database.

9. A multi-environment application management system according to claim 8, characterized in that: The synchronization of the current environment server and the target environment server based on configuration differences includes: The central server reads the configuration difference from the database, and the tester verifies the configuration difference based on business requirements. If the verification passes, the central server sends the configuration difference to the target environment server, and the target environment server modifies the second configuration information of the target environment server based on the configuration difference.

10. A multi-environment application management system according to claim 9, characterized in that: The target environment server modifies the second configuration information of the target environment server according to the configuration difference, including: The target environment server performs a backup operation on the second configuration information, and after the backup operation is completed, reads the configuration difference and modifies the second configuration information; If the configuration difference information is of a new addition type or a change type, read the middleware type in the current environment server in the configuration difference information, and compare whether the middleware type is consistent with the middleware type in the target environment server. If they are consistent, perform a new addition or change operation; if the configuration information is of a deletion type, read the middleware type in the current environment server in the configuration difference information, and compare whether the middleware type is consistent with the middleware type in the target environment server. If they are consistent, obtain the application identifier recorded in the configuration difference information, and delete the corresponding data in this configuration information under the application identifier.

Images