A multi-environment application management system

Abstract

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

Description

TECHNICAL FIELD

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

[0002] For large and complex projects, developers increasingly tend to use microservice architecture combined with agile development system development methods, which can help enterprises quickly respond to market changes, improve development efficiency and product quality, reduce project risks, and improve customer satisfaction.

[0003] In the prior art, the system developed based on microservice architecture combined with agile development system mainly has the following problems: (1) security risk, frequent communication between microservices may cause security problems such as data leakage and denial of service attacks, for example, attackers may use service vulnerabilities to abuse resources, such as DDoS attacks; (2) fault propagation, a service failure may quickly spread to other services, causing an avalanche effect; (3) difficult to maintain and extend, the dependency relationship between services becomes complex, making it difficult to maintain and extend independently, which increases the maintenance cost of the system and reduces scalability; (4) high cost of maintaining data consistency; (5) only single environment, unable to manage and switch between multiple environments.

[0004] Therefore, it is necessary to provide a microservice architecture combined with agile development system application development system that supports data isolation and switching and management of each environment. SUMMARY

[0005] In view of the above analysis, the embodiments of the present application aim to provide a multi-environment application management system to solve the problem that the existing microservice architecture combined with agile development system cannot support data isolation and switching and management of each environment.

[0006] The embodiments of the present application provide a multi-environment application management system, comprising:

[0007] An input module for inputting environment server IP addresses, application identifiers and business resource data determined based on business requirements;

[0008] A central server for obtaining a first application program interface key corresponding to the environment server IP address, generating a first authentication signature based on a salt value, a timestamp, the application identifier, the first application program interface key and business resource data, and sending the timestamp, the application identifier, the business resource data and the first authentication signature to the environment server corresponding to the environment server IP address.

[0009] A plurality of environment servers judge whether the received data contains a timestamp, an application identifier, service resource data, and a first authentication signature, if it does, judge whether the difference between the timestamp and the current system timestamp exceeds a preset threshold, if it does not, obtain a second application program interface key corresponding to the environment server, 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, compare the first authentication signature and the second authentication signature, 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 not consistent, prompt an authentication error.

[0010] Based on the further improvement of the above method, the plurality of 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 the environment server, and supports remote calling services; the public data includes application information data, service information data, and environment service permission information data.

[0012] Based on the further improvement of the above method, the application identifier includes: a dictionary data read operation interface class identifier, a form design read operation interface class identifier, a static resource read operation interface class identifier, a permission read operation interface class identifier, an aggregate table read operation interface class identifier, and a middleware read 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 requirements, thereby forming different middleware read operation interface class identifiers; the middleware includes: Gitlab, Apollo, Gateway, and Xxljob; the read service includes: paging query, detail query, saving, modification, and deletion.

[0014] Based on the further improvement of the above method, the central server further includes a synchronization configuration module for realizing 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 realized, comprising: formulating a synchronization test plan on the central server, the synchronization test plan comprising a version number, an IP address of the current environment server, and an 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, obtaining configuration differences based on the first configuration information and the second configuration information, the configuration differences comprising application configuration differences, service configuration differences, middleware configuration differences, menu configuration differences, white list configuration differences, resource configuration differences, data dictionary configuration differences, IP address differences, domain name address differences, account name and password differences; and realizing the synchronization between the current environment server and the target environment server based on the configuration differences.

[0016] Based on the further improvement of the above method, the obtaining of the configuration differences based on the first configuration information and the second configuration information comprises: for each piece of data in the first configuration information, if the piece of data exists in the first configuration information and does not exist in the second configuration information, returning the first configuration information data and marking it as a new type and storing it in a new record; if the piece of data does not exist in the first configuration information and exists in the second configuration information, returning the second configuration information data and marking it as a deletion type and storing it in a deletion record; if the piece of data exists in the first configuration information and exists in the second configuration information, converting the piece of data into a JSON data format, cyclically reading key values, comparing value values in the first configuration information and the second configuration information, if consistent, skipping and not making a change record, if inconsistent, marking it as a modification and marking it as a change type and storing it in a change record; taking the new record, the deletion record and the change record as the configuration differences, the configuration differences comprising middleware types, application identifiers, data, new types / deletion types / change types, and storing the configuration differences in a database.

[0017] Based on the further improvement of the above method, the realizing of the synchronization between the current environment server and the target environment server based on the configuration differences comprises: the central server reading the configuration differences from the database, a test personnel checking and verifying the configuration differences based on business requirements, if the verification is passed, the central server sending the configuration differences to a target environment server, and the target environment server modifying the second configuration information of the target environment server according to the configuration differences.

[0018] Based on the 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, after the backup operation is completed, reading the configuration difference, modifying the second configuration information, if the configuration difference information is of an addition type or a change type, reading the middleware type in the current environment server in the configuration difference information, comparing the middleware type with the middleware type in the target environment server, if they are consistent, performing an addition or change operation, if the configuration information is of a deletion type, reading the middleware type in the current environment server in the configuration difference information, comparing the middleware type with the middleware type in the target environment server, if they are consistent, obtaining the application identifier recorded in the configuration difference information, and deleting the corresponding data in the configuration information under the application identifier.

[0019] Compared with the prior art, the application can at least realize one of the following beneficial effects:

[0020] 1. The application provides a multi-environment application management system, and a center server accesses a corresponding environment server based on an IP address of the environment server determined based on a business requirement, and only when signature authentication is consistent, the center server is allowed to enter the environment corresponding to the IP address, so that the security of data management of the application management system is further improved.

[0021] 2. The application provides a multi-environment application management system, and a 1+N technical development mode is adopted, that is, a development mode of one center server and multiple environment servers, the management of public data and the loading and calling of environment switching are placed in the center server, the IP addresses of various environments are fixed, and only the development of corresponding functions is responsible, the center server realizes the switching and management of the environment based on the IP addresses of various environments, so that the isolation of various sub-environments is realized, and the security risk and fault propagation risk are further reduced. In addition, data exchange between various environments must be realized through the center server, and various environments are independent of each other and do not affect each other, so that the maintenance difficulty and expansion difficulty of the management system are further reduced.

[0022] In the application, the above technical solutions can be combined with each other to realize more preferred combination solutions. Other features and advantages of the application will be described in the subsequent specification, and some advantages will become apparent from the specification, or will be understood by implementing the application. The purpose and other advantages of the application can be realized and obtained from the contents specifically pointed out in the specification and the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0023] The accompanying drawings are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and are used to explain the principles of the application, but are not intended to limit the scope of the application.

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

[0025] Preferred embodiments of the application will be described in detail with reference to the drawings, in which:

[0026] Microservices architecture is a software development architecture that breaks down a single application into a set of small services, each running in its own process, and usually built around specific business capabilities, these services can communicate through well-defined APIs, usually HTTP RESTful APIs or lightweight messaging systems.

[0027] Agile development system is a software development methodology that takes people as the core, iteration, and gradual progress. It emphasizes that in the rapidly changing market environment, through flexible and efficient team cooperation, it can quickly respond to customer needs and continuously deliver high-quality software products.

[0028] The application aims at the problems of security risks, fault propagation, and inability to realize management and switching between multiple environments in systems developed based on microservices architecture combined with agile development system, and proposes a multi-environment application management system to solve the problems that existing microservices architecture combined with agile development system cannot support data isolation and switching and management of each environment.

[0029] One specific embodiment of the application discloses a multi-environment application management system, as shown in Figure 1 The system comprises:

[0030] An input module is configured to input an environment server IP address, an application identifier, and business resource data determined based on business requirements.

[0031] A central server is configured to obtain a first application program interface key corresponding to the environment server IP address, generate a first authentication signature based on a salt value, a timestamp, the application identifier, the first application program interface key, and business resource data, and send the timestamp, the application identifier, the business resource data, and the first authentication signature to an environment server corresponding to the environment server IP address.

[0032] The plurality of environment servers judge whether the received data contains a timestamp, an application identifier, service resource data, and a first authentication signature. If the data contains the timestamp, the application identifier, the service resource data, and the first authentication signature, the environment servers judge whether the difference between the timestamp and a current system timestamp exceeds a preset threshold. If the difference does not exceed the preset threshold, the environment servers obtain a second application program interface key corresponding to the environment servers, generate a second authentication signature based on a salt value, the timestamp, the application identifier, the second application program interface key, and the service resource data, compare the first authentication signature with the second authentication signature, and if the first authentication signature is consistent with the second authentication signature, allow the central server to access the environment servers and implement a read operation based on the application identifier. If the first authentication signature is not consistent with the second authentication signature, the environment servers prompt an authentication error.

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

[0034] The application identifier includes a dictionary data read operation interface class identifier, a form design read operation interface class identifier, a static resource read operation interface class identifier, a permission read operation interface class identifier, an aggregate table read operation interface class identifier, and a middleware read operation interface class identifier. For example, an application management system developer pre-constructs a dictionary data read operation interface class Dict.class, a form design read operation interface class Form.class, a static resource read operation interface class Resource.class, a form permission read operation interface class Auth.class, a form aggregate table read operation interface class View.class, a middleware read operation interface class Middleware.class (used to define configuration page query, detail query, save, modification, and deletion interfaces), a configuration read operation interface class Config.class, and the like based on a business logic.

[0035] It can be understood that each environment server will have data reading operation, in order to distinguish the dictionary data reading operation, form design reading operation and the like of each environment server, the environment server allocates an application identifier to each reading service based on business requirements, so as to form different reading operation interface class identifiers. Exemplarily, the environment server allocates an application identifier to each reading service of the middleware based on business requirements, so as to form different middleware reading operation interface class identifiers; the middleware includes: Gitlab, ApollO, Gateway, Xxljob; the reading service includes: paging query, detail query, saving, modification, deletion. The implementation logic of each interface class is set according to actual business requirements, which is not limited by the application. The application identifier is one-to-one corresponding to each interface class identifier, which is used to limit the specific operation of each environment server, and the system user can determine the operation of the specified environment server based on business requirements, so as to 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 requirements, and then performs 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, calls the corresponding interface class based on the application identifier, so as to realize remote calling of the environment server, and executes the corresponding operation 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, the timestamp, the application identifier, the first application program interface key and the business resource data, and after generating the first authentication signature, the central server will send the timestamp, the application identifier, the business resource data and the first authentication signature to the environment server corresponding to the environment server IP address. 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 center server is used for public data management in the multi-environment application management system, data management of the environment server, and supports remote calling services; the public data includes application information data, service information data, and environment service permission information data. Specifically, the center server is responsible for managing all function data in the application management system, including management of public basic data, loading and calling of environment data, and providing page functions for operation of the above two types of data.

[0041] The center server is responsible for scheduling access to each environment server, reading dictionary, form design, static resources, form permission configuration, aggregation table, middleware, and other data information related to application information in different environment servers based on business requirements, thereby manipulating application functions in different environment servers based on business requirements, and each environment server cannot directly interact with data or business, and must be realized through scheduling of the center server, thereby realizing data isolation of each environment server.

[0042] In the development management cycle requirements of micro-service architecture and agile development system, four environments of development, testing, acceptance, and production are usually divided, which facilitates continuous iteration of the application and realizes agile development and delivery of services. For example, after software development is completed in the development environment server, the software needs to be tested, but the testing environment server is data isolated from the development environment server, and the system user cannot directly deploy the software in the testing environment server for testing, and needs to perform data migration through the synchronization configuration function of the center server, thereby ensuring that the configuration data in the testing environment server is consistent with the configuration data in the development environment server. Therefore, the center server further includes a synchronization configuration module for realizing 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 realized through the following steps:

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

[0044] The version number is used to distinguish different software versions, facilitating the system user to distinguish test versions.

[0045] A2: First configuration information of the current environment server and second configuration information of the target environment server are obtained, and configuration differences are obtained 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, white list configuration differences, resource configuration differences, data dictionary configuration differences, IP address differences, domain name address differences, account name and password differences.

[0046] The configuration difference is obtained based on the first configuration information and the second configuration information, and the configuration difference includes:

[0047] For each piece of data in the first configuration information, if the piece of data exists in the first configuration information but does not exist in the second configuration information, the first configuration information data is returned, marked as an added type, and stored in an added record; if the piece of 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 piece of data exists in the first configuration information and exists in the second configuration information, the piece of data is converted into a JSON data format, a key value is read in a loop, and a value in the first configuration information and a value in the second configuration information are compared; if the values are consistent, the piece of data is skipped and no change record is made; if the values are inconsistent, the piece of data is marked as modified and marked as a changed type, and stored in a changed record; the added record, the deleted record, and the changed record are taken as the configuration difference, the configuration difference includes a middleware type, an application identifier, data, an added type / deleted type / changed type, and the configuration difference is stored in a database.

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

[0049] The center server reads the configuration difference from the database, a tester checks and verifies the configuration difference based on a business requirement, if the verification is passed, the center server sends the configuration difference to a target environment server, and the target environment server modifies second configuration information of the target environment server according to the configuration difference, if the verification is not passed, the tester can select to regenerate the configuration difference or directly modify the generated configuration difference until the verification requirement is met. Exemplarily, the configuration difference can be displayed in a 1ist data format on a front end.

[0050] Exemplarily, the verification of the test personnel on the configuration difference can be the verification on the IP address of the environment server (i.e. judging whether the IP address of the current environment server is normal), because the method proposed in the present application is to realize the data isolation of the environment servers, and thus the IP address of the target environment server needs to be further checked and verified; can be the verification on the login verification information such as account, password or user permission information, to ensure that the system user has the permission to perform the corresponding interface operation on the environment server after the central server establishes the link with the environment server; 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 test personnel verifies through, the target environment server can be entered through the central server, and if the verification fails, the test personnel can choose to regenerate the configuration difference or directly modify the generated configuration difference until the verification requirement is met. Preferably, whether the content in the synchronization test plan is wrong is checked, and the error content is modified and the configuration difference is regenerated. Further, the test personnel 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 the addition type or the change type, the middleware type in the current environment server in the configuration difference information is read, and whether the middleware type is consistent with the middleware type in the target environment server is compared. If they are consistent, the addition or change operation is performed. If the configuration information is of the deletion type, the middleware type in the current environment server in the configuration difference information is read, and whether the middleware type is consistent with the middleware type in the target environment server is compared. If they are consistent, the application identifier recorded in the configuration difference information is obtained, and the corresponding data in the configuration information under the application identifier is deleted.

[0054] Exemplarily, based on the method provided in the present application, each environment server is implemented based on one or more middleware in Gitlab, Apolllo, Gateway, Xxljob, therefore, after determining the target environment server, in order to ensure that the data addition or change is correct, it is further needed to 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 in the case that the middleware type in the current environment server is consistent with the middleware type in the target environment server, the data addition and change operation can be performed. If in the case of performing the addition or change type operation, the IP address of the target environment server is correct, 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 incorrect, if incorrect, the configuration difference can be directly modified, or the content in the synchronization test plan can be checked whether incorrect, and then the error content is modified, and the configuration difference is regenerated, the above-mentioned manners are all for ensuring that the data operation in the target environment server is correctly performed. Further, the tester can report the error to wait for the operation and maintenance personnel to solve.

[0055] It can be understood that the configuration information of the current target environment server is backed up to prevent the modified configuration information in this synchronization operation from being too much, so that the modified configuration cannot be applied to other operations, therefore, when the user needs to use the configuration of the current target environment server to complete some operations next time, the data can be quickly recovered to ensure the continuity of the business.

[0056] The plurality of environment servers can be a research and development environment server, a test environment server, an acceptance environment server or a production environment server.

[0057] It can be understood that the data received by the environment server can be from the center server or from other servers. Whether it is a center server or other servers, there can be problems such as the center server sending errors, causing it to not communicate data with the designated environment server, or other servers sending data that can harm the environment server, such as network attacks, and the like. Therefore, the environment server needs to format and timestamp verification on the received data. Specifically, the environment server first determines whether the received data contains a timestamp, an application identifier, business resource data, and a first authentication signature. If not, an authentication error is prompted. If so, a timestamp verification is performed to determine whether the difference between the timestamp and the current system timestamp exceeds a preset threshold. If it exceeds the preset threshold, an authentication error is prompted. If it does not exceed, a second application program interface key corresponding to the environment server is obtained, a second authentication signature is generated based on the salt value, the timestamp, the application identifier, the second application program interface key, and the business resource data, and the first authentication signature and the second authentication signature are compared. If they are consistent, the center server is allowed to enter the environment server, and a read operation is implemented based on the application identifier. If they are not consistent, an authentication error is prompted. The preset threshold is 2 minutes, and the rule for generating the second authentication signature is the same as that for the first authentication signature.

[0058] Compared with the prior art, the application provided by the embodiment provides a multi-environment application management system. The center server accesses the corresponding environment server based on the environment server IP address determined by the business requirement. Only when the signature authentication is consistent, the center server can enter the environment corresponding to the IP address, thereby further improving the security of the data management of the application management system. The 1+N technical development mode is adopted, that is, the development mode of one center server and multiple environment servers. The management of public data and the loading and calling of environment switching are placed in the center server. The IP addresses of various environments are fixed and only responsible for completing the development of corresponding functions. The center server realizes the switching and management of the environment based on the IP addresses of various environments, thereby realizing the isolation of various sub-environments of the implementation class, further reducing the security risk and fault propagation risk. The exchange of data between various environments must be realized through the center server, and various environments are independent of each other and do not affect each other, further reducing the maintenance difficulty and expansion difficulty of the management system.

[0059] Those skilled in the art can understand that all or part of the processes of the above-mentioned embodiments can be completed by a computer program instructing related hardware. The program can be stored in a computer readable storage medium, such as a magnetic disk, an optical disk, a read-only memory, or a random access memory.

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

Claims

1. A multi-environment application management system, characterized by, The application comprises: an input module for inputting an environment server IP address, an application identifier and service resource data determined based on service requirements; a central server for obtaining a first application program interface key corresponding to the environment server IP address, generating a first authentication signature based on a salt value, a timestamp, the application identifier, the first application program interface key and service resource data, and sending 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; the application identifier comprises a dictionary data reading operation interface class identifier, a form design reading operation interface class identifier, a static resource reading operation interface class identifier, a permission reading operation interface class identifier, an aggregate table reading operation interface class identifier and a middleware reading operation interface class identifier; a plurality of environment servers for judging whether the received data contains a timestamp, an application identifier, service resource data and a first authentication signature, if it does, judging whether the difference between the timestamp and the current system timestamp exceeds a preset threshold, if it does not, obtaining a second application program interface key corresponding to the environment server, generating a second authentication signature based on a salt value, a timestamp, an application identifier, a second application program interface key and service resource data, comparing the first authentication signature with the second authentication signature, if they are consistent, allowing the central server to enter the environment server and implementing a reading operation based on the application identifier, if they are not consistent, prompting an authentication error; the central server further comprises: a synchronization configuration module for implementing data synchronization between a current environment server and a target environment server, comprising: formulating a synchronization test plan on the central server, the synchronization test plan comprising a version number, an IP address of the current environment server and an 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, obtaining configuration differences based on the first configuration information and the second configuration information, the configuration differences comprising application configuration differences, service configuration differences, middleware configuration differences, menu configuration differences, white list configuration differences, resource configuration differences, data dictionary configuration differences, IP address differences, domain name address differences, account name and password differences; implementing synchronization between the current environment server and the target environment server based on the configuration differences.

2. The multi-environment application management system of claim 1, wherein, The plurality of environment servers are development environment servers, test environment servers, acceptance environment servers or production environment servers.

3. The multi-environment application management system of claim 2, wherein, The central server is used for public data management in a multi-environment application management system, data management of environment servers and supports remote service invocation; the public data comprises application information data, service information data and environment service permission information data.

4. The multi-environment application management system of claim 3, wherein, The environment server assigns an application identifier to each reading service of the middleware based on service requirements, thereby forming different middleware reading operation interface class identifiers; the middleware comprises Gitlab, Apollo, Gateway and Xxljob; the reading services comprise page query, detail query, saving, modification and deletion.

5. The multi-environment application management system of claim 4, wherein, The configuration difference is obtained based on the first configuration information and the second configuration information, and includes: For each piece of data in the first configuration information, if the piece of data exists in the first configuration information but does not exist in the second configuration information, the first configuration information data is returned, marked as an added type, and stored in an added record; if the piece of 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 piece of data exists in the first configuration information and exists in the second configuration information, the piece of data is converted into a JSON data format, a key value is read in a loop, value values in the first configuration information and the second configuration information are compared, if the value values are consistent, the piece of data is skipped and no change record is made, and if the value values are inconsistent, the piece of data is marked as modified and as a changed type, and stored in a changed record; The added record, the deleted record, and the changed record are taken as the configuration difference, the configuration difference includes a middleware type, an application identifier, data, an added type / deleted type / changed type, and the configuration difference is stored in a database.

6. The multi-environment application management system of claim 5, wherein, The current environment server and the target environment server are synchronized based on the configuration difference, and includes: The center server reads the configuration difference from the database, a test personnel checks and verifies the configuration difference based on a business requirement, if the verification is passed, the center server sends the configuration difference to a target environment server, and the target environment server modifies second configuration information of the target environment server according to the configuration difference.

7. The multi-environment application management system of claim 6, wherein, The target environment server modifies the second configuration information of the target environment server according to the configuration difference, and includes: The target environment server performs a backup operation on the second configuration information, reads the configuration difference, and modifies the second configuration information after the backup operation is completed; If the piece of configuration difference is of an added type or a changed type, a middleware type in the current environment server in the piece of configuration difference is read, the middleware type is compared with a middleware type in the target environment server, if the middleware types are consistent, an added operation or a changed operation is performed, if the piece of configuration difference is of a deleted type, the middleware type in the current environment server in the piece of configuration difference is read, the middleware type is compared with the middleware type in the target environment server, if the middleware types are consistent, an application identifier recorded in the piece of configuration difference is obtained, and corresponding data in the piece of configuration information under the application identifier is deleted.

Images