Centralized management method after distributed deployment of single software

Abstract

The invention provides a centralized management method for single software after distributed deployment, which comprises the following steps of: separating a front-end interface and a back-end logic in a single software management platform, and interacting the separated front-end interface and back-end logic through a management interface; a remote managed agent service is integrated in each piece of single software; after receiving the management data, the separated front-end interface forwards the management data to a specified remote managed agent service; and the remote managed agent service routes the received remote management request to the local implementation of the management interface, executes a corresponding management operation and returns a corresponding result. The method is used for realizing centralized management of the remote single software.

Description

Technical Field

[0001] The present invention relates to the technical field of single software, and in particular to a centralized management method for single software after distributed deployment. Background Art

[0002] Monolithic software refers to software that runs in an independent process and does not need to interact or collaborate with other processes. Its management usually involves two components: a front-end interface and a back-end process. The management process is that the front-end interface receives parameters and passes them to the back-end for processing, and then the back-end processes the parameters and passes them back to the front-end. Monolithic software generally has its own management method. For example, after running, there is a Web console based on the HTTP protocol that can manage its own resource configuration, performance optimization, security settings, etc. In order to improve the efficiency of software services, etc., the monolithic software needs to be distributed and deployed to multiple other remote machines. At this time, the management of these distributed software becomes cumbersome and becomes a problem.

[0003] When the number of machines for distributed deployment is relatively small, such as no more than 10, the centralized management method is to log in to the management console of each single software in turn on a specific machine to manage it. When the number of machines for distributed deployment is large, it is difficult to implement single login for configuration. The general practice at this time is to develop a centralized management main program and a single software agent program at the same time. The main program establishes a connection with each agent program for centralized management. The scope of application of the single login configuration method is very limited. At the same time, it requires that each single software cannot change its identity authentication information by itself, otherwise the centralized management will fail to authenticate. Redeveloping the centralized management program requires additional work. At the same time, the centralized management capability is coupled to the management capability of the single software itself. When the management capability of the single software itself changes, the centralized management also needs to be changed accordingly. Therefore, there are disadvantages such as low development efficiency and difficult maintenance.

[0004] Therefore, the present invention provides a centralized management method after distributed deployment of single software. Summary of the invention

[0005] The invention provides a centralized management method for monomer software after distributed deployment, which realizes centralized management of multiple monomer software instances.

[0006] The present invention provides a centralized management method for distributed deployment of a single software, comprising the following steps:

[0007] Separate the front-end interface and back-end logic in the single software management platform. The separated front-end interface and back-end logic interact through the management interface; and integrate a remote managed agent service in each single software;

[0008] When the separated front-end interface receives the management data, it forwards it to the designated remote managed proxy service; the remote managed proxy service then routes the received remote management request to the local implementation of the management interface, performs the corresponding management operation and returns the corresponding result.

[0009] In an practicable manner, before the front-end interface and the back-end logic in the monolithic software management platform are separated, the method further includes:

[0010] When deploying single software in a distributed manner, an authentication key is installed for each single software, and the authentication key must be issued by a unified security center.

[0011] In an practicable manner, after the step of integrating a remote managed proxy service into each single software, the method further comprises:

[0012] According to the basic information of the target single software, a remote target list is constructed by automatic reporting registration and / or active entry, and the remote target list is used to manage the connection information of the remote managed proxy service of the target single software;

[0013] The target single software is single software that needs to be remotely managed, and the basic information includes connection information.

[0014] In an practicable manner, the separation-post-front end interface forwards the management request to the designated remote managed proxy service, specifically including:

[0015] Receive management data from the user, determine the target single software; and construct a management request according to the management data; the management request includes an authentication key and management data;

[0016] Management requests are sent to the remote managed agent service of the target monolith using an agreed protocol.

[0017] In one practicable manner, integrating a remote managed agent service into each monolithic software specifically includes:

[0018] Select a remote managed agent service that meets the requirements for receiving management requests;

[0019] Prepare the server and install the remote managed agent service on the server of the monolithic software;

[0020] After the installation is complete, configure the remote managed agent service;

[0021] After the configuration is complete, test whether the remote managed agent service can run correctly.

[0022] In an practicable manner, before the step of forwarding the front-end interface to the designated remote managed proxy service, the method further comprises:

[0023] Verify user identity using multi-factor authentication methods;

[0024] After successful authentication, the resources that the user can access are determined based on the user's role and permissions;

[0025] Receive the target software to be managed selected by the user on the front-end interface;

[0026] Based on the administrator's permissions and the selected remote target software, an authentication key associated with the selected target monomer software is retrieved.

[0027] In one practicable manner, after building the remote target list, the method further includes:

[0028] Use quantity monitoring mechanisms to track the size and growth trend of the target list;

[0029] When the size and / or growth trend of the target list exceeds a preset threshold, determine the key indicators affecting system performance and the corresponding weights;

[0030] Calculate the comprehensive score based on the weights of key indicators and actual performance values;

[0031] Compare the current weighted score with the standard score, and identify the important bottlenecks that have the greatest impact on system performance based on the comparison results;

[0032] Based on the weighted scores and bottleneck analysis results, the most appropriate strategy is selected from the predefined optimization strategy library.

[0033] In an implementable manner, the adjustment strategy includes target list index optimization, query optimization strategy, cache optimization strategy and load balancing strategy.

[0034] In one practicable manner, the single software management platform is a Web console based on the HTTP protocol.

[0035] The beneficial effects that can be achieved by the present invention are: the present application directly reuses the management interface of the single software for distributed management, so as to achieve the purpose of easy centralized management without the need for additional development of centralized management programs, and the management capabilities of the single software are automatically synchronized to the centralized management capabilities, thereby ultimately reducing the cost of centralized management.

[0036] Beneficial effects of the present invention:

[0037] The present application directly reuses the management interface of the single software, and forwards the received management request to the remote managed proxy service of the remote software through a specific protocol internally, thereby realizing the management of the remote software. Using the method of the present application, there is no need to develop additional centralized management programs, and no additional maintenance is required after the management capabilities of the single software change, so the cost of centralized management can be greatly reduced.

[0038] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description and the accompanying drawings.

[0039] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0041] Figure 1 This is a flow chart of a centralized management method after distributed deployment of a single software in Example 1 of the present invention;

[0042] Figure 2 This is a flowchart of determining the authentication key associated with the target single software in Example 1 of the present invention;

[0043] Figure 3 This is a flow chart for selecting the most appropriate adjustment strategy in Example 1 of the present invention. DETAILED DESCRIPTION

[0044] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0045] This embodiment 1 provides a centralized management method for distributed deployment of a single software, including the following steps:

[0046] Separate the front-end interface and back-end logic in the single software management platform. The separated front-end interface and back-end logic interact through the management interface; and integrate a remote managed agent service in each single software;

[0047] When the separated front-end interface receives the management data, it forwards it to the designated remote managed proxy service; the remote managed proxy service then routes the received remote management request to the local implementation of the management interface, performs the corresponding management operation and returns the corresponding result.

[0048] The working principle of the above technical solution is:

[0049] See also Figure 1 After the monolithic software is deployed in a distributed manner, the front-end interface and back-end logic in the original management platform of the monolithic software are separated, and a management interface is designed to realize the interaction between the two. The management interface should be designed to be sufficiently general, including three attributes: module name (target resource to be managed by the management request), operation name (specific operation to be performed on the target by the management request) and parameter list (parameters required for this operation). It is also necessary to integrate a remote managed agent service in each monolithic software to receive management requests from the remote. In this operation, the front-end interface belongs to the interface of the display layer; the back-end logic belongs to the business, and the two interact through the interface. The back-end logic of the back-end business layer is based on the docking of the front-end interface of the java interface, and the interface is provided internally. When facing the abstract java interface call process, it does not need to care about the specific interface implementation. When the remote managed agent service integrated in each monolithic software receives the business processing request sent by the remote management end, it directly calls the specific implementation of the above abstract interface (java interface).

[0050] The separated front-end interface is responsible for receiving the user's trigger operations, and the management data is various management tasks, such as configuration changes, data queries, etc. When the separated front-end receives the management data, it will generate a management request based on the management data and pass it to the remote managed agent service of the specified single software. When sending a management request, it needs to be sent according to the predetermined communication protocol. After receiving the management request, the remote managed agent service routes the management information to the local implementation of the management interface inside the single software according to the preset rules, performs the corresponding management operation and returns the corresponding result. In this way, the remote software can be managed.

[0051] Beneficial effects of the above technical solution:

[0052] The present application directly reuses the management interface of the single software, and forwards the received management request to the remote managed proxy service of the remote software through a specific protocol internally, thereby realizing the management of the remote software. Using the method of the present application, there is no need to develop additional centralized management programs, and no additional maintenance is required after the management capabilities of the single software change, so the cost of centralized management can be greatly reduced.

[0053] Based on Example 1, before the steps of separating the front-end interface and the back-end logic in the single software management platform, the method also includes: when the single software is deployed in a distributed manner, an authentication key is installed for it, and the authentication key must be issued by a unified security center.

[0054] The working principle and beneficial effects of the above technical solution:

[0055] In a distributed deployment, an authentication key is installed in each single software instance. The authentication key must be issued by a unified security center. The unified issuance of keys by the security center helps to centrally control the generation, distribution and revocation of keys, thereby improving security. When an administrator initiates a management request from a remote location, the request can include an authentication key. After receiving the authentication key, the single software can confirm the legitimacy of the request by verifying the key. If the key verification succeeds, the remote management request will be accepted and processed; if it fails, the request will be rejected. The above authentication method ensures that only authorized users with keys can perform remote management operations.

[0056] Based on the first embodiment, after the step of integrating a remote managed proxy service into each single software, the method further includes:

[0057] According to the basic information of the target single software, a remote target list is constructed by automatic reporting registration and / or active entry, and the remote target list is used to manage the connection information of the remote managed proxy service of the target single software;

[0058] The target single software is single software that needs to be remotely managed, and the basic information includes connection information.

[0059] The working principle and beneficial effects of the above technical solution:

[0060] This application uses automatic reporting registration and / or active entry to build a remote target list to manage the connection information of the remote managed proxy service of the target monomer software. When building the remote target list, it is necessary to determine the basic information of the target monomer software, which includes but is not limited to the target identification, connection information, authentication information, target description, network topology information, management interface information, status information, configuration information, etc. Then, the target list is constructed based on the basic information. When sending a management request, the request of the front-end interface can be forwarded to the remote managed proxy service according to the connection information corresponding to the target software.

[0061] Based on Example 1, the separation front-end interface forwards the management request to the designated remote managed proxy service specifically including:

[0062] Receive management data from the user, determine the target single software; and construct a management request according to the management data; the management request includes an authentication key and management data;

[0063] Management requests are sent to the remote managed agent service of the target monolith using an agreed protocol.

[0064] The working principle and beneficial effects of the above technical solution:

[0065] The user performs management operations through the front-end interface. When the front-end interface receives the management data, it will encapsulate the management data and the authentication key into a management request. Then, the target software to be managed is determined. After the target software is determined, the management request is sent to the remote managed agent service of the target software using the agreed protocol. Encapsulating the management data and the authentication key into a management request ensures the legitimacy and security of the request.

[0066] Based on Example 1, integrating a remote managed proxy service in each single software specifically includes:

[0067] Select a remote managed agent service that meets the requirements for receiving management requests;

[0068] Prepare the server and install the remote managed agent service on the server of the monolithic software;

[0069] After the installation is complete, configure the remote managed agent service;

[0070] After the configuration is complete, test whether the remote managed agent service can run correctly.

[0071] The working principle and beneficial effects of the above technical solution:

[0072] First, select a suitable remote agent service software; then, ensure that the server running the monolithic software is in a state that can accept installation and configuration. Specifically, the server has a suitable operating system installed and updated to the latest version. All dependent software or libraries required for the remote agent service have been installed on the server. The server has sufficient resources (CPU, memory, storage space) to run the remote agent service. The server is connected to the network, and the network settings are correct so that the remote agent service can receive connections from the Internet. After preparation, install the remote managed agent service on the server of the monolithic software. After the installation is complete, configure the remote managed agent service; including setting network parameters, authentication information, etc. After the configuration is complete, test whether the remote managed agent service can run correctly. When the remote managed agent service is installed, it can receive management requests from the separated front-end interface to achieve effective remote management.

[0073] Based on Embodiment 1, before the step of forwarding the data to the designated remote managed proxy service at the front-end interface, the method further includes:

[0074] Verify user identity using multi-factor authentication methods;

[0075] After successful authentication, the resources that the user can access are determined based on the user's role and permissions;

[0076] Receive the target software to be managed selected by the user on the front-end interface;

[0077] Based on the administrator's permissions and the selected remote target software, an authentication key associated with the selected target monomer software is retrieved.

[0078] The working principle and beneficial effects of the above technical solution:

[0079] See also Figure 2 , first use a multi-factor authentication method to verify the user's identity. Multi-factor authentication methods include but are not limited to username and password, digital certificates, or other multi-factor authentication methods. Once the authentication is successful, the resources that the user can access can be determined based on the role and permissions. Each user role is associated with a set of permissions. When the user selects a remote target to be managed, the corresponding authentication key is retrieved from the storage location. Through the above steps, the authentication keys required for the request can be securely and accurately determined and managed.

[0080] In one practicable manner, after building the remote target list, the method further includes:

[0081] Use quantity monitoring mechanisms to track the size and growth trend of the target list;

[0082] When the size and / or growth trend of the target list exceeds a preset threshold, determine the key indicators affecting system performance and the corresponding weights;

[0083] Calculate the comprehensive score based on the weights of key indicators and actual performance values;

[0084] Compare the current weighted score with the standard score, and identify the important bottlenecks that have the greatest impact on system performance based on the comparison results;

[0085] Based on the weighted scores and bottleneck analysis results, the most appropriate strategy is selected from the predefined optimization strategy library.

[0086] The working principle of the above technical solution is:

[0087] See also Figure 3, first use the quantity supervision mechanism to regularly check the size and growth of the target list; when the size and / or growth trend of the target list exceeds the preset threshold, it indicates that optimization is needed. Next, determine the key indicators that affect system performance, such as retrieval response time, resource utilization, etc. and assign weights to each performance indicator. Then, calculate the comprehensive score based on the weights and actual performance values ​​of the key indicators. Next, compare the current weighted score with the performance standard to evaluate the overall performance of the system; and identify the bottleneck that has the greatest impact on system performance by analyzing the scores of each indicator. For example, if the score of a certain indicator is much lower than other indicators, it indicates that the indicator is the main bottleneck of the current performance problem. For the identified bottlenecks, conduct a deeper analysis to determine the root cause of the problem. This includes reviewing system logs, analyzing query plans, checking resource usage, etc. Finally, based on the results of performance evaluation and bottleneck identification, select the most appropriate strategy from the predefined optimization strategy library. For example, if it is found that retrieval response time is the main bottleneck, then you can choose to optimize database queries or increase cache strategies. Adjustment strategies include target list index optimization, query optimization strategy, cache optimization strategy, and load balancing strategy.

[0088] Beneficial effects of the above technical solution:

[0089] This application dynamically selects and implements the most appropriate optimization strategy based on the importance and actual performance of different indicators to ensure that the performance of the system is effectively managed.

[0090] In one practicable manner, the single software management platform is a Web console based on the HTTP protocol.

[0091] The principle of the above technical solution is:

[0092] In the actual implementation process, because the monolithic software management platform integrates all functions into a single code base, development and testing are usually simpler. When developing, you only need to deploy the entire application to the server, without the need for a complex deployment process. Since all components run in the same process, performance tuning can be done more easily; the unified development framework and technology stack make the entire application consistent.

[0093] In actual implementation, the HTTP protocol itself is not secure, and additional measures (such as HTTPS) are required to ensure the security of data transmission. However, the present invention installs an authentication key for each single software, and the authentication key is issued by a unified security center. No additional measures are required.

[0094] In actual implementation, compared with applications based on other protocols (such as WebSocket), HTTP may have performance bottlenecks in processing a large number of concurrent connections and real-time communications. The present invention can achieve remote hosting through remote managed proxy services, and is not limited by performance bottlenecks.

[0095] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A centralized management method for distributed deployment of single software, characterized in that: The following steps are involved: Separate the front-end interface and back-end logic in the single software management platform. The separated front-end interface and back-end logic interact through the management interface. And integrate a remote managed proxy service into each monolithic software; When the separated front-end interface receives the management data, it forwards it to the designated remote managed proxy service; the remote managed proxy service then routes the received remote management request to the local implementation of the management interface, performs the corresponding management operation and returns the corresponding result.

2. The centralized management method after distributed deployment of a single software according to claim 1, characterized in that: Before the front-end interface and the back-end logic in the single software management platform are separated, the method further includes: When deploying single software in a distributed manner, an authentication key is installed for each single software, and the authentication key must be issued by a unified security center.

3. The centralized management method after distributed deployment of a single software according to claim 2, characterized in that: After the step of integrating a remote managed proxy service into each monolithic software, the method further comprises: According to the basic information of the target single software, a remote target list is constructed by automatic reporting registration and / or active entry, and the remote target list is used to manage the connection information of the remote managed proxy service of the target single software; The target single software is single software that needs to be remotely managed, and the basic information includes connection information.

4. The centralized management method after distributed deployment of a single software according to claim 3, characterized in that: After separation, the front-end interface forwards the management request to the designated remote managed proxy service, including: Receive management data from the user, determine the target single software; and construct a management request according to the management data; the management request includes an authentication key and management data; Management requests are sent to the remote managed agent service of the target monolith using an agreed protocol.

5. The centralized management method after distributed deployment of a single software according to claim 1, characterized in that: Integrating a remote managed proxy service into each monolithic software specifically includes: Select a remote managed agent service that meets the requirements for receiving management requests; Prepare the server and install the remote managed agent service on the server of the monolithic software; After the installation is complete, configure the remote managed agent service; After the configuration is complete, test whether the remote managed agent service can run correctly.

6. The centralized management method after distributed deployment of a single software according to claim 3, characterized in that: Before the step of forwarding the front-end interface to the designated remote managed proxy service, the method further includes: Verify user identity using multi-factor authentication methods; After successful authentication, the resources that the user can access are determined based on the user's role and permissions; Receive the target software to be managed selected by the user on the front-end interface; Based on the administrator's permissions and the selected remote target software, an authentication key associated with the selected target monomer software is retrieved.

7. The centralized management method after distributed deployment of a single software according to claim 3, characterized in that: After building the list of remote targets, the method also includes: Use quantity monitoring mechanisms to track the size and growth trend of the target list; When the size and / or growth trend of the target list exceeds a preset threshold, determine the key indicators affecting system performance and the corresponding weights; Calculate the comprehensive score based on the weights of key indicators and actual performance values; Compare the current weighted score with the standard score, and identify the important bottlenecks that have the greatest impact on system performance based on the comparison results; According to the weighted score and bottleneck analysis results, the most appropriate adjustment strategy is selected from the predefined optimization strategy library.

8. The centralized management method after distributed deployment of a single software according to claim 7, characterized in that: Adjustment strategies include target list index optimization, query optimization strategy, cache optimization strategy and load balancing strategy.

9. The centralized management method after distributed deployment of a single software according to claim 1, characterized in that: The single software management platform is a Web console based on the HTTP protocol.

Images