Automatic application management and control method and device

Abstract

The invention discloses an automatic application management and control method and device, resource isolation is carried out on each middleware WebLogic instance, each middleware WebLogic instance runs on different physical servers and shares respective state information, through transverse expansion and longitudinal expansion, optimization deployment is carried out on each middleware WebLogic instance set after resource isolation, and the management and control efficiency of each middleware WebLogic instance set after resource isolation is improved. The transverse extension is used for sharing loads by increasing the node servers, and when any node server breaks down, other node servers normally provide services; longitudinal expansion is used for ensuring consistency of node servers in load balancing of transverse expansion.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and more specifically, to an application automation management and control method and device. Background Art

[0002] A WebLogic cluster is a deployment method that uses multiple server instances (nodes) to distribute the processing load to provide high availability and scalability.

[0003] The existing WebLogic cluster deployment method requires the configuration and management of multiple nodes, involving resource sharing and failover. It is difficult to quickly respond to changes in business needs and is inconvenient to deploy and update, resulting in a long WebLogic cluster deployment time and poor flexibility.

[0004] Therefore, how to improve the efficiency and flexibility of the WebLogic cluster deployment method is an urgent problem to be solved in this application. Summary of the invention

[0005] In view of this, the present application discloses an application automation management and control method and device, aiming to improve the efficiency and flexibility of WebLogic cluster deployment.

[0006] In order to achieve the above purpose, the disclosed technical solution is as follows:

[0007] In a first aspect, the present application discloses an application automation management and control method, the method comprising:

[0008] Isolate resources for each WebLogic instance; each WebLogic instance runs on a different physical server and shares its status information with each other;

[0009] Through horizontal and vertical expansion, the WebLogic instances of each middleware are optimized and deployed after resource isolation to achieve load balancing, flexible expansion, failover and security management of the system;

[0010] The horizontal expansion is used to share the load by adding node servers. When any node server fails, other node servers provide services normally. The vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

[0011] Preferably, the resource isolation of each middleware WebLogic instance includes:

[0012] In the process of running each independently configured middleware WebLogic instance on a machine, resources of each middleware WebLogic instance are isolated through operating system user permissions.

[0013] Preferably, the WebLogic instances of each middleware after resource isolation are optimized and deployed through horizontal expansion and vertical expansion to achieve load balancing, flexible expansion, failover and security management of the system, including:

[0014] Through load balancing, automated deployment, centralized monitoring and unified management, the WebLogic instances of each middleware after resource isolation are optimized and deployed, so as to complete the process of optimizing the deployment of the WebLogic instances of each middleware after resource isolation through horizontal expansion;

[0015] The load balancing includes at least hardware load balancing and software load balancing; the automated deployment includes at least virtual machine replication deployment and script automation;

[0016] Through status checking, domain instance maintenance, domain instance creation, log query and auxiliary functions, the WebLogic instance sets of each middleware after resource isolation are optimized and deployed to complete the process of vertical expansion to optimize the deployment of each WebLogic instance set of middleware after resource isolation;

[0017] Among them, the status check at least includes refreshing the domain instance status and testing the health check; the domain instance maintenance at least includes starting the domain instance and stopping the domain instance; the domain instance creation at least includes creating a domain, saving the startup user password, setting rich socket rejection and setting management port separation; the auxiliary functions at least include authorizing querying user permissions and setting common commands.

[0018] Preferably, the load balancing process includes:

[0019] In the network layer, the hardware load balancing device is used to control the flow of user application requests so as to evenly distribute the application requests to the node servers corresponding to the hardware load balancing device;

[0020] In the process of evenly distributing application requests to the node servers corresponding to the hardware load balancing device, if it is detected that the application request is sent to the faulty node server, the application request sent to the faulty node server is blocked through the health check mechanism to complete the hardware load balancing process;

[0021] In a preset application scenario, the user's application request is flow controlled through a preset software mode to evenly distribute the application request to the corresponding node server to complete the software load balancing process; wherein the preset application scenario is an application scenario without a hardware load balancing device.

[0022] Preferably, the automated deployment process includes:

[0023] In the template machine that configures the non-cluster deployment mode and the management agent, the node server is horizontally expanded through virtual machine replication to complete the virtual machine replication deployment process;

[0024] Through automated scripts, batch deployment and management are achieved to complete the script automation process.

[0025] Preferably, the centralized monitoring process includes:

[0026] Monitor the operating status of multiple node servers in real time;

[0027] If the running state is a fault state, obtaining an error log of the node server in the fault state;

[0028] The node server in the fault state is diagnosed and processed according to the error log.

[0029] Preferably, the status check process includes:

[0030] Update and monitor the running status of WebLogic domain instances in real time, and monitor the running status of each WebLogic domain instance through the health monitoring uniform resource locator;

[0031] When a failure is detected in the operation status of each WebLogic domain instance, the WebLogic domain instance is restarted through the agent program deployed on the node server to implement fault repair and complete the status check process.

[0032] Preferably, the process of maintaining a domain instance includes:

[0033] The process of starting a domain instance can be realized through one-click operation of the operation and maintenance menu of the character interface;

[0034] For node servers in a faulty state, user connection requests in a faulty state are automatically blocked through health checks, and domain instances in a faulty state are stopped and isolated to complete the process of stopping domain instances.

[0035] Preferably, the process of creating a domain instance includes:

[0036] Through the character interface menu, a new WebLogic domain instance is automatically created with one click, and the startup user credentials of the new WebLogic domain instance are stored;

[0037] Set rich socket denial by configuring rich socket protocol access;

[0038] Set up rich sockets by configuring the rich sockets protocol port.

[0039] The second aspect of the present application discloses an application automation management and control device, the device comprising:

[0040] A resource isolation unit is used to isolate resources of each middleware WebLogic instance; wherein each middleware WebLogic instance runs on a different physical server and shares their state information with each other;

[0041] The optimized deployment unit is used to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion to achieve system load balancing, flexible expansion, failover and security management; wherein, the horizontal expansion is used to share the load by adding node servers, and when any node server fails, other node servers provide services normally; the vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

[0042] It can be known from the above technical scheme that the present application discloses an application automation management and control method and device, which performs resource isolation on each middleware WebLogic instance, wherein each middleware WebLogic instance runs on a different physical server and shares each other's status information. Through horizontal expansion and vertical expansion, each set of middleware WebLogic instances after resource isolation is optimized and deployed to achieve load balancing, flexible expansion, failover and security management of the system, wherein horizontal expansion is used to share the load by adding node servers. When any node server fails, other node servers provide services normally; vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

[0043] Through the above solution, there is no need to configure and manage multiple nodes and complex shared resources. It is only necessary to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion. Since horizontal expansion mainly focuses on the distributed deployment and management of the system, it realizes the horizontal expansion of the system through load balancing, automated deployment, monitoring and management, service orchestration and scheduling and other technical means, and improves the availability, fault tolerance and management efficiency of the system. Vertical expansion optimizes the resources and improves the performance of a single server node. Through status inspection, domain instance maintenance, domain instance creation, log query and auxiliary functions, it realizes the vertical expansion of the system and improves the rapid deployment processing capability, management efficiency and security of the application. Therefore, through horizontal expansion and vertical expansion, the cluster deployment of each set of middleware WebLogic instances after resource isolation is simplified, the deployment of management applications is optimized, the rapid deployment capability is improved, and a flexible expansion solution is provided, thereby improving the efficiency and flexibility of the WebLogic cluster deployment method. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0045] Figure 1 A structural block diagram of a WebLogic application automatic management and control system in a non-cluster deployment mode disclosed in an embodiment of the present application;

[0046] Figure 2 A schematic diagram of a horizontal module disclosed in an embodiment of the present application;

[0047] Figure 3 A schematic diagram of a longitudinal module disclosed in an embodiment of the present application;

[0048] Figure 4 A flowchart of an application automation management and control method disclosed in an embodiment of the present application;

[0049] Figure 5 A schematic diagram of the structure of an application automation control device disclosed in an embodiment of the present application;

[0050] Figure 6 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0052] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0053] As can be seen from the background technology, the existing WebLogic cluster deployment method requires configuration and management of multiple nodes, involving resource sharing and failover. Due to the need to configure multiple nodes and complex shared resources, it is difficult to quickly respond to changes in business needs, and deployment and updating are inconvenient, resulting in a long deployment time and poor flexibility of the WebLogic cluster deployment method. Therefore, how to improve the efficiency and flexibility of the WebLogic cluster deployment method is a problem that needs to be solved urgently in this application.

[0054] In order to solve the above problems, the present application discloses an application automation management and control method and device, which does not need to configure and manage multiple nodes and complex shared resources. It only needs to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion. Since horizontal expansion mainly focuses on the distributed deployment and management of the system, through load balancing, automatic deployment, monitoring and management, service orchestration and scheduling and other technical means, the horizontal expansion of the system is realized, and the availability, fault tolerance and management efficiency of the system are improved. And vertical expansion is aimed at the resource optimization and performance improvement of a single server node, and through status inspection, domain instance maintenance, domain instance creation, log query and auxiliary functions and other means, the vertical expansion of the system is realized, and the rapid deployment processing ability, management efficiency and security of the application are improved. Therefore, through horizontal expansion and vertical expansion, the cluster deployment of each set of middleware WebLogic instances after resource isolation is simplified, the deployment of management applications is optimized, the rapid deployment capability is improved, and a flexible expansion solution is provided, thereby improving the efficiency and flexibility of the WebLogic cluster deployment method. The task of this application is to simplify cluster deployment, optimize the deployment of management applications, improve the rapid deployment capability, and provide a flexible expansion solution to improve the overall efficiency and stability of the system. At the same time, it can be flexibly expanded vertically and horizontally to meet the needs of different business scenarios. The specific implementation method is specifically described through the following embodiments.

[0055] refer to Figure 1 As shown, it is a structural block diagram of the WebLogic application automatic control system of the non-cluster deployment mode disclosed in an embodiment of the present application. The WebLogic application automatic control system includes a load balancing module 101, an automatic deployment module 102, a monitoring and management module 103, a status checking module 104, a domain instance maintenance module 105, a domain instance creation module 106, a log query module 107 and an auxiliary function module 108.

[0056] The load balancing module 101 performs load balancing, which includes hardware load balancing and software load balancing.

[0057] Hardware load balancing:

[0058] Use F5 as a hardware load balancing device to control the flow of user requests at the network layer and distribute them to the corresponding node servers of F5. At the same time, use F5's health check mechanism to promptly block the requests from being sent to problematic node servers. Among them, the F5 hardware load balancing device is a high-performance, high-availability application delivery controller.

[0059] Software load balancing:

[0060] In a preset application scenario, the user's application request is flow controlled through a preset software mode to evenly distribute the application request to the corresponding node server to complete the software load balancing process; wherein, the preset application scenario is an application scenario without a hardware load balancing device.

[0061] The preset application scenario is an application scenario without a hardware load balancing device, and the preset software mode is the keepalived+nginx mode.

[0062] The keepalived+nginx model is used to implement low-cost software load balancing services. Specifically, keepalived is used to achieve high availability of the load balancing server, and nginx is used to control the flow of user requests and distribute them to the corresponding node servers.

[0063] The automated deployment module 102 performs automated deployment. Specifically, in the automated deployment process, a service orchestration tool is used to automatically manage the deployment, expansion and operation of services, thereby improving the adaptive capability of the system. Automated deployment also includes virtual machine replication deployment and script automation.

[0064] Virtual machine replication deployment:

[0065] You only need to configure a template machine with WebLogic and Webligc management agent installed and configured in non-cluster deployment mode, and achieve rapid horizontal expansion of node servers through VMware virtual machine replication.

[0066] Among them, the non-cluster deployment mode usually refers to the software architecture in which the various components or services of the system are not scattered across multiple nodes, but are concentrated on a single node. In this mode, the system load, data processing, and storage all rely on the performance and reliability of a single node.

[0067] Since there is no need to manage and configure through the WebLogic cluster, it not only simplifies the deployment and release of new node machines, but also the new servers and existing production node servers are deployed in isolation, with a lower impact. After the business peak period, the newly copied nodes can be shut down and recycled, thereby achieving rapid and isolated deployment of applications, improving resource utilization and expansion flexibility.

[0068] Script Automation:

[0069] Through automated scripts, batch deployment and management can be achieved, which improves expansion efficiency and reduces manual operation errors.

[0070] Centralized monitoring and unified management are performed through the monitoring and management module 103 .

[0071] Centralized monitoring:

[0072] Use a centralized monitoring system to monitor the operating status of multiple nodes in real time, quickly locate problems through the centralized error log overview, and then log in to the node server for further detailed diagnosis and problem solving. The operating status includes running, starting, stopped, and failed to start.

[0073] Unified management:

[0074] Through a unified management platform, multiple nodes and applications can be centrally managed to simplify operation and maintenance and improve management efficiency.

[0075] The load balancing module 101, the automated deployment module 102, and the monitoring and management module 103 are horizontal expansion modules. Figure 2 shown.

[0076] The horizontal expansion module focuses on the distributed deployment and management of the system. Through load balancing, automated deployment, monitoring and management, service orchestration and scheduling and other technical means, it realizes the horizontal expansion of the system and improves the system's availability, fault tolerance and management efficiency.

[0077] Advantages of horizontal expansion:

[0078] (1) Improve system availability and fault tolerance: Horizontal expansion shares the load by adding more server nodes. Even if a node fails, other nodes can still continue to provide services, thereby improving system availability and fault tolerance.

[0079] (2) On-demand expansion with high flexibility: Horizontal expansion allows enterprises to dynamically increase or decrease server nodes according to their own business needs, adapt to traffic fluctuations and changes in resource requirements, ensure that the system can handle a large number of requests during peak periods, and reduce resource waste during off-peak periods.

[0080] The status check module 104 performs a status check.

[0081] Status Check:

[0082] (1) Refresh domain instance status: Update and monitor the operating status of WebLogic domain instances in real time (including undeployed, deployment exception, running, starting, stopped, startup failure, etc.), ensuring that operation and maintenance personnel can accurately understand the working status of each instance and respond quickly to status changes.

[0083] (2) Test health check: Perform health checks regularly, test the operating status of each domain instance through the preset health check Uniform Resource Locator (URL), identify and solve potential problems in advance, and ensure the continuous and stable operation of the system. For example, the application provides a lightweight availability detection URL, and checks the availability of the URL every 1 minute. If it fails three times in a row (the specific number is set according to the actual situation, and this application does not make specific restrictions), the agent program deployed on the node server automatically restarts the service of the weblogic instance to achieve self-recovery of the fault.

[0084] The domain instance maintenance module 105 performs domain instance maintenance, which includes starting a domain instance and stopping a domain instance.

[0085] Domain instance maintenance:

[0086] (1) Start the domain instance: Through the one-click operation of the operation and maintenance menu of the character interface, since this one-click operation is a simplified management operation, it can quickly start the WebLogic domain instance, improve the system online speed, and ensure rapid business response.

[0087] (2) Stop domain instances: For applications in a faulty state, such as "fake live" (i.e., the service port is available but the application is not functioning properly, such as reporting an HTTP 502 error), F5 hardware load balancing can automatically block user connection requests to the "fake live" node server through health checks. However, in software load balancing mode, the node server's agent program can also perform a test health check to achieve self-recovery, but the response time is longer. The "fake live" domain instance can be quickly stopped through the character interface's operation and maintenance menu, and the faulty node server can be quickly isolated to prevent the problem from spreading and ensure the overall security and stability of the system.

[0088] The domain instance creation module 106 creates a domain instance. The domain instance creation includes creating a domain, saving a startup user password, setting rich socket (T3) rejection, and setting management port separation. Management port separation refers to the separation of management ports and application ports.

[0089] Domain creation: Through the menu of the character interface, an automated script is provided to automatically create a new WebLogic domain instance with one click (without interactive operations or configuration of complex silent installation scripts), significantly reducing the complexity and time cost of manual configuration and improving deployment efficiency.

[0090] Save the startup user password: Safely save the startup user credentials of the domain instance, which simplifies subsequent startup operations while ensuring the security of the startup process.

[0091] Set T3 rejection: By configuring to reject T3 protocol access, you can strengthen network security, prevent unauthorized protocol connections, and improve system security.

[0092] Set up management port separation: configure the management port and application port to run independently, optimize network resource management, and enhance the system's security protection capabilities.

[0093] The log query module 107 performs log query.

[0094] Log query:

[0095] (1) View console logs: Provides a convenient access interface to console logs, supports rapid location and analysis of system problems, and improves troubleshooting efficiency.

[0096] (2) View the AdminServer log: Supports detailed query of the AdminServer log to help administrators understand system management operations and background running status.

[0097] (3) View the switch port mode (Access) log: Provides access log query function. Through the access log query function, you can view the Access log to help analyze and audit system access status and improve system monitoring and management level.

[0098] The auxiliary function module 108 includes auxiliary functions.

[0099] Accessibility:

[0100] (1) Authorized query of user rights: Supports query and management of user rights information, ensures reasonable configuration of user rights, effectively prevents abuse of rights, and improves system security and management efficiency.

[0101] (2) Common commands: Provide quick access to common operation and maintenance commands, improve the efficiency and accuracy of operation and maintenance operations, simplify daily management work, and improve overall operation and maintenance efficiency. Common operation and maintenance commands include but are not limited to firewall configuration statements related to weblogic applications and ACL authorization statements for querying users related to weblogic applications.

[0102] By combining the functions of horizontal modules and vertical modules, this application can effectively improve the deployment efficiency, flexibility and security of WebLogic applications, thereby meeting the needs of modern enterprises for efficient, secure and flexible deployment.

[0103] The status check module 104, the domain instance maintenance module 105, the domain instance creation module 106, the log query module 107 and the auxiliary function module 108 belong to the vertical expansion module. The structure of the specific vertical expansion module is as follows: Figure 3shown.

[0104] The vertical expansion module mainly focuses on resource optimization and performance improvement of a single server node. Through status checking, domain instance maintenance, domain instance creation, log query and auxiliary functions, it realizes the vertical expansion of the system and improves the rapid deployment processing capability, management efficiency and security of the application.

[0105] Advantages of vertical expansion:

[0106] (1) Improving single-node performance: Vertical expansion improves the processing power of a single server node by increasing its resources (such as CPU, memory, and storage). This can significantly improve the performance of a single node and is suitable for applications that require high-performance computing or process large amounts of data.

[0107] (2) Simplified management and maintenance: Vertical expansion is concentrated on a small number of high-performance servers, reducing the number of nodes, thereby simplifying system management and maintenance and reducing network complexity and management costs.

[0108] (3) Improved security: The system security is improved through measures such as management port separation, protocol blocking, access whitelist control, and SSL encryption vulnerability rectification, meeting the high standards of information security required by the banking system.

[0109] (4) Enhanced stability: Through health checks and automatic recovery mechanisms, the system can be quickly restored when a failure occurs, thus improving the stability and reliability of the banking system.

[0110] (5) Flexible expansion: It supports running multiple WebLogic instances on a single machine, which can meet the needs of vertical expansion as well as horizontal expansion through hardware load balancing, thus meeting the needs of the banking system for flexible expansion.

[0111] The advantages of this application are as follows:

[0112] (1) Load balancing solution in non-cluster deployment mode: Combined with hardware load balancing devices, this solution can achieve uniform distribution of application requests in non-cluster deployment mode, solve the problem of lack of load balancing in traditional non-cluster deployment mode, and meet the needs of high concurrent processing.

[0113] (2) Independent operation of multiple instances and resource isolation: Run multiple independently configured and running WebLogic instances on a single machine, and implement resource isolation through operating system user permissions and operating system-level resource restriction tools to ensure that each instance does not interfere with each other, simplifying management and maintenance. Compared with the container mode, it has higher hardware resource utilization and simpler network configuration.

[0114] (3) Automated domain creation and security enhancement: Provides a one-click menu for automatic domain creation, and uses automated scripts to create and configure WebLogic domains. It also strengthens production mode settings, management port separation, protocol blocking, access whitelist control, and Secure Socket Layer (SSL) encryption vulnerability rectification to improve system security.

[0115] (4) Health check and automatic recovery mechanism: The status of the WebLogic instance is monitored through the health check URL, and automatic recovery is performed in the event of a failure, ensuring the continuous availability of the application and business continuity.

[0116] This application aims to simplify cluster deployment, optimize the deployment of management applications, improve rapid deployment capabilities, and provide flexible expansion solutions to improve the overall efficiency and stability of the system. At the same time, it can flexibly expand vertically and horizontally to meet the needs of different business scenarios.

[0117] In the embodiment of the present application, there is no need to configure and manage multiple nodes and complex shared resources. It is only necessary to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion. Since horizontal expansion mainly focuses on the distributed deployment and management of the system, through load balancing, automated deployment, monitoring and management, service orchestration and scheduling and other technical means, the horizontal expansion of the system is realized, and the availability, fault tolerance and management efficiency of the system are improved. And vertical expansion is for the resource optimization and performance improvement of a single server node, through status inspection, domain instance maintenance, domain instance creation, log query and auxiliary functions and other means, the vertical expansion of the system is realized, and the rapid deployment processing ability, management efficiency and security of the application are improved. Therefore, through horizontal expansion and vertical expansion, the cluster deployment of each set of middleware WebLogic instances after resource isolation is simplified, the deployment of management applications is optimized, the rapid deployment capability is improved, and a flexible expansion plan is provided, thereby improving the efficiency and flexibility of the WebLogic cluster deployment method.

[0118] refer to Figure 4 As shown, an application automation control method disclosed in an embodiment of the present application is applied to the above embodiment. Figure 1 The automatic control system of WebLogic application in non-cluster deployment mode is provided. The automatic control method of application mainly includes the following steps:

[0119] S401: Perform resource isolation on each middleware WebLogic instance; wherein each middleware WebLogic instance runs on a different physical server and shares their state information with each other.

[0120] In S401, during the process of running each independently configured middleware WebLogic instance on a machine, resource isolation is performed on each middleware WebLogic instance through operating system user permissions.

[0121] Run multiple independently configured and running WebLogic instances on one machine, and implement resource isolation through operating system user permissions and operating system-level resource limitation tools to ensure that each instance does not interfere with each other, simplifying management and maintenance.

[0122] S402: Through horizontal expansion and vertical expansion, the WebLogic instance sets of each middleware after resource isolation are optimized and deployed to achieve system load balancing, flexible expansion, failover and security management; among them, horizontal expansion is used to share the load by adding node servers. When any node server fails, other node servers provide services normally; vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

[0123] Specifically, the process of optimizing and deploying each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion is shown in A1-A2.

[0124] A1: Through load balancing, automated deployment, centralized monitoring and unified management, the WebLogic instances of each middleware after resource isolation are optimized and deployed, so as to complete the process of optimizing the deployment of the WebLogic instances of each middleware after resource isolation through horizontal expansion.

[0125] Among them, load balancing includes at least hardware load balancing and software load balancing; automated deployment includes at least virtual machine replication deployment and script automation;

[0126] A2: Through status checking, domain instance maintenance, domain instance creation, log query and auxiliary functions, the WebLogic instance sets of each middleware after resource isolation are optimized and deployed to complete the process of vertical expansion to optimize the deployment of each WebLogic instance set of middleware after resource isolation.

[0127] Among them, status check at least includes refreshing domain instance status and testing health check; domain instance maintenance at least includes starting domain instance and stopping domain instance; domain instance creation at least includes creating domain, saving startup user password, setting T3 rejection and setting management port separation; auxiliary functions at least include authorizing querying user permissions and setting common commands.

[0128] The load balancing process is shown in B1-B3.

[0129] B1: In the network layer, the flow of user application requests is controlled through the hardware load balancing device to evenly distribute the application requests to the node servers corresponding to the hardware load balancing device.

[0130] B2: In the process of evenly distributing application requests to the node servers corresponding to the hardware load balancing device, if it is detected that the application request is sent to the faulty node server, the application request sent to the faulty node server is blocked through the health check mechanism to complete the hardware load balancing process;

[0131] B3: In the preset application scenario, the preset software mode (exchange mechanism software (keepalived) + high-performance HTTP and reverse proxy web server (nginx) mode) is used to control the flow of user application requests so as to evenly distribute the application requests to the corresponding node servers to complete the software load balancing process; among them, the preset application scenario is an application scenario without a hardware load balancing device.

[0132] The execution process and execution principle of B1-B3 are similar to those of the above embodiment. Figure 1 The execution process and principle of load balancing are consistent, which can be referred to and will not be repeated here.

[0133] The process of automated deployment is shown in C1-C2.

[0134] C1: In the template machine that configures the non-cluster deployment mode and the management agent, the node server is horizontally expanded through virtual machine replication to complete the virtual machine replication deployment process.

[0135] C2: Use automated scripts to achieve batch deployment and management to complete the script automation process.

[0136] The execution process and execution principle of C1-C2 are similar to those of the above embodiment. Figure 1 The execution process and principle of the automated deployment are the same, which can be referred to and will not be described here.

[0137] The process of centralized monitoring is shown in D1-D3.

[0138] D1: monitor the operating status of multiple node servers in real time;

[0139] D2: If the running status is a faulty status (such as falsely active, that is, the service port is available but the application is abnormal, such as reporting an HTTP 502 error), obtain the error log of the node server in the faulty status.

[0140] D3: Diagnose and process the node server in fault state according to the error log.

[0141] The execution process and execution principle of D1-D3 are similar to those of the above embodiment. Figure 1 The execution process and principle of centralized monitoring are consistent, which can be referred to and will not be repeated here.

[0142] The status check process is shown in E1-E2.

[0143] E1: Update and monitor the running status of WebLogic domain instances in real time, and monitor the running status of each WebLogic domain instance through the health monitoring URL.

[0144] E2: When a failure is detected in the operation status of each WebLogic domain instance, the WebLogic domain instance is restarted through the agent program deployed on the node server to implement fault repair and complete the status check process.

[0145] The execution process and execution principle of E1-E2 are similar to those of the above embodiment. Figure 1 The execution process and principle of the status check are the same, which can be referred to and will not be repeated here.

[0146] The process of domain instance maintenance is shown in F1-F2.

[0147] F1: Use the one-click operation of the operation and maintenance menu in the character interface to start the domain instance;

[0148] F2: For node servers in a faulty state (i.e., the service port is available but the application is abnormal, such as reporting a Hypertext Transfer Protocol (HTTP) 502 error), health checks automatically block user connection requests in a faulty state, stop the domain instance in a faulty state, and isolate the node server in a faulty state to complete the process of stopping the domain instance.

[0149] The execution process and execution principle of F1-F2 are similar to those of the above embodiment. Figure 1 The execution process and execution principle of domain instance maintenance are consistent, which can be referred to and will not be repeated here.

[0150] The process of domain instance creation is shown in G1-G3.

[0151] G1: Through the character interface menu, a new WebLogic domain instance is automatically created with one click, and the startup user credentials of the new WebLogic domain instance are stored.

[0152] G2: Set rich socket denial by configuring rich socket protocol access.

[0153] G3: Set up rich sockets by configuring the rich socket protocol port.

[0154] The execution process and execution principle of G1-G3 are similar to those of the above embodiment. Figure 1 The execution process and execution principle of domain instance creation are consistent, which can be referred to and will not be repeated here.

[0155] This application aims to solve the problems of complexity, inadaptability, slow deployment and insufficient scalability in the traditional cluster mode. This application combines the functions of the horizontal and vertical modules to achieve efficient deployment, flexible expansion and secure management of the system, which is particularly suitable for scenarios that require rapid deployment and flexible expansion, especially internal management systems of banks.

[0156] This application aims to achieve uniform distribution of requests in non-cluster deployment mode by combining hardware load balancing devices, using operating system-level resource isolation tools to ensure resource isolation between multiple instances, and providing more complete security measures to improve system stability and security. In addition, automated scripts and health checks are used to achieve automatic fault detection and recovery of WebLogic instances, improve system availability and business continuity, thereby meeting the requirements of efficient, secure and flexible deployment, and is suitable for non-customer-oriented internal management application scenarios of banking systems.

[0157] This application aims to achieve uniform distribution of requests in non-cluster deployment mode by combining hardware load balancing devices, using operating system-level resource isolation tools to ensure resource isolation between multiple instances, and providing more complete security measures to improve system stability and security. In addition, automated scripts and health checks are used to achieve automatic fault detection and recovery of WebLogic instances, improve system availability and business continuity, thereby meeting the requirements of efficient, secure and flexible deployment, and is particularly suitable for non-customer-oriented internal management application scenarios of banking systems.

[0158] In the embodiment of the present application, there is no need to configure and manage multiple nodes and complex shared resources. It is only necessary to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion. Since horizontal expansion mainly focuses on the distributed deployment and management of the system, through load balancing, automated deployment, monitoring and management, service orchestration and scheduling and other technical means, the horizontal expansion of the system is realized, and the availability, fault tolerance and management efficiency of the system are improved. And vertical expansion is for the resource optimization and performance improvement of a single server node, through status inspection, domain instance maintenance, domain instance creation, log query and auxiliary functions and other means, the vertical expansion of the system is realized, and the rapid deployment processing ability, management efficiency and security of the application are improved. Therefore, through horizontal expansion and vertical expansion, the cluster deployment of each set of middleware WebLogic instances after resource isolation is simplified, the deployment of management applications is optimized, the rapid deployment capability is improved, and a flexible expansion plan is provided, thereby improving the efficiency and flexibility of the WebLogic cluster deployment method.

[0159] Based on the above embodiments Figure 4 The disclosed application automation control method, the embodiment of the present application also discloses an application automation control device, such as Figure 5 As shown, the application automation control device includes:

[0160] The resource isolation unit 501 is used to isolate resources for each middleware WebLogic instance; wherein each middleware WebLogic instance runs on a different physical server and shares their state information with each other;

[0161] The optimized deployment unit 502 is used to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion to achieve system load balancing, flexible expansion, failover and security management; wherein, horizontal expansion is used to share the load by adding node servers, and when any node server fails, other node servers provide services normally; vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

[0162] Furthermore, the resource isolation unit 501 is specifically used to isolate resources of each middleware WebLogic instance through operating system user permissions during the process of running each independently configured middleware WebLogic instance on the machine.

[0163] Further, the optimization deployment unit 502 includes:

[0164] The first optimization deployment module is used to optimize the deployment of each set of middleware WebLogic instances after resource isolation through load balancing, automated deployment, centralized monitoring and unified management, so as to complete the process of optimizing the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion; wherein, load balancing at least includes hardware load balancing and software load balancing; automated deployment at least includes virtual machine replication deployment and script automation;

[0165] The second optimization deployment module is used to optimize the deployment of each set of middleware WebLogic instances after resource isolation through status check, domain instance maintenance, domain instance creation, log query and auxiliary functions, so as to complete the process of vertical expansion to optimize the deployment of each set of middleware WebLogic instances after resource isolation; wherein, the status check at least includes refreshing the domain instance status and testing the health check; the domain instance maintenance at least includes starting the domain instance and stopping the domain instance; the domain instance creation at least includes creating a domain, saving the startup user password, setting rich socket rejection and setting management port separation; the auxiliary functions at least include authorizing querying user permissions and setting common commands.

[0166] Furthermore, the load balancing optimization deployment unit 502 includes:

[0167] The flow control module is used to control the flow of user application requests through the hardware load balancing device in the network layer, so as to evenly distribute the application requests to the node servers corresponding to the hardware load balancing device;

[0168] The monitoring and blocking module is used to evenly distribute application requests to the node servers corresponding to the hardware load balancing device. If it is detected that the application request is sent to the faulty node server, the application request sent to the faulty node server is blocked through the health check mechanism to complete the hardware load balancing process.

[0169] The uniform distribution module is used to control the flow of user application requests through a preset software mode under a preset application scenario, so as to evenly distribute the application requests to the corresponding node servers to complete the software load balancing process; wherein the preset application scenario is an application scenario without a hardware load balancing device.

[0170] Furthermore, the automatic deployment optimization deployment unit 502 includes:

[0171] The horizontal expansion module is used to achieve horizontal expansion of node servers through virtual machine replication in the template machine configured with non-cluster deployment mode and management agent to complete the process of virtual machine replication deployment;

[0172] The deployment management module is used to implement batch deployment and management through automated scripts to complete the script automation process.

[0173] Furthermore, the centralized monitoring optimization deployment unit 502 includes:

[0174] Real-time monitoring module, used to monitor the operating status of multiple node servers in real time;

[0175] An acquisition module is used to acquire the error log of the node server in the fault state if the running state is a fault state;

[0176] The diagnosis and processing module is used to diagnose and process the node server in the fault state according to the error log.

[0177] Furthermore, the state check optimization deployment unit 502 includes:

[0178] Update monitoring module, which is used to update and monitor the running status of WebLogic domain instances in real time, and monitor the running status of each WebLogic domain instance through health monitoring uniform resource locator;

[0179] The repair module is used to restart the WebLogic domain instance through the agent program deployed on the node server when the running status of each WebLogic domain instance is monitored to have a fault, so as to realize fault repair and complete the status check process.

[0180] Furthermore, the domain instance maintenance optimization deployment unit 502 includes:

[0181] The operation module is used to start the domain instance through one-click operation of the operation and maintenance menu of the character interface;

[0182] The blocking module is used to automatically block user connection requests in a faulty node server through health checks, stop the domain instance in a faulty state, and isolate the node server in a faulty state to complete the process of stopping the domain instance.

[0183] Furthermore, the domain instance creation optimization deployment unit 502 includes:

[0184] Create a storage module to automatically create a new WebLogic domain instance through a character interface menu and store the startup user credentials of the new WebLogic domain instance.

[0185] A first setting module, used for setting rich socket rejection by configuring rich socket protocol access;

[0186] The second setting module is used to set the rich socket by configuring the rich socket protocol port.

[0187] In the embodiment of the present application, there is no need to configure and manage multiple nodes and complex shared resources. It is only necessary to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion. Since horizontal expansion mainly focuses on the distributed deployment and management of the system, through load balancing, automated deployment, monitoring and management, service orchestration and scheduling and other technical means, the horizontal expansion of the system is realized, and the availability, fault tolerance and management efficiency of the system are improved. And vertical expansion is for the resource optimization and performance improvement of a single server node, through status inspection, domain instance maintenance, domain instance creation, log query and auxiliary functions and other means, the vertical expansion of the system is realized, and the rapid deployment processing ability, management efficiency and security of the application are improved. Therefore, through horizontal expansion and vertical expansion, the cluster deployment of each set of middleware WebLogic instances after resource isolation is simplified, the deployment of management applications is optimized, the rapid deployment capability is improved, and a flexible expansion plan is provided, thereby improving the efficiency and flexibility of the WebLogic cluster deployment method.

[0188] An embodiment of the present application further provides a storage medium, which includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the above-mentioned application automation management and control method.

[0189] The present application also provides an electronic device, whose structural diagram is as follows: Figure 6 As shown, it specifically includes a memory 601 and one or more instructions 602, wherein the one or more instructions 602 are stored in the memory 601 and are configured to be executed by one or more processors 603 to execute the one or more instructions 602 to perform the above-mentioned application automation management and control method.

[0190] For the aforementioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0191] It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0192] The steps in the methods of the embodiments of the present application can be adjusted in order, combined, and deleted according to actual needs.

[0193] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0194] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

[0195] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. An application automation management and control method, characterized in that: The method comprises: Isolate resources for each WebLogic instance; each WebLogic instance runs on a different physical server and shares its status information with each other; Through horizontal and vertical expansion, the WebLogic instances of each middleware are optimized and deployed after resource isolation to achieve load balancing, flexible expansion, failover and security management of the system; The horizontal expansion is used to share the load by adding node servers. When any node server fails, other node servers provide services normally. The vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

2. The method according to claim 1, characterized in that The resource isolation of each middleware WebLogic instance includes: In the process of running each independently configured middleware WebLogic instance on a machine, resources of each middleware WebLogic instance are isolated through operating system user permissions.

3. The method according to claim 1, characterized in that Through horizontal expansion and vertical expansion, each set of middleware WebLogic instances after resource isolation is optimized and deployed to achieve load balancing, flexible expansion, failover and security management of the system, including: Through load balancing, automated deployment, centralized monitoring and unified management, the WebLogic instances of each middleware after resource isolation are optimized and deployed, so as to complete the process of optimizing the deployment of the WebLogic instances of each middleware after resource isolation through horizontal expansion; The load balancing includes at least hardware load balancing and software load balancing; the automated deployment includes at least virtual machine replication deployment and script automation; Through status checking, domain instance maintenance, domain instance creation, log query and auxiliary functions, the WebLogic instance sets of each middleware after resource isolation are optimized and deployed to complete the process of vertical expansion to optimize the deployment of each WebLogic instance set of middleware after resource isolation; Among them, the status check at least includes refreshing the domain instance status and testing the health check; the domain instance maintenance at least includes starting the domain instance and stopping the domain instance; the domain instance creation at least includes creating a domain, saving the startup user password, setting rich socket rejection and setting management port separation; the auxiliary functions at least include authorizing querying user permissions and setting common commands.

4. The method according to claim 3, characterized in that: The load balancing process includes: In the network layer, the hardware load balancing device is used to control the flow of user application requests so as to evenly distribute the application requests to the node servers corresponding to the hardware load balancing device; In the process of evenly distributing application requests to the node servers corresponding to the hardware load balancing device, if it is detected that the application request is sent to the faulty node server, the application request sent to the faulty node server is blocked through the health check mechanism to complete the hardware load balancing process; In a preset application scenario, the user's application request is flow controlled through a preset software mode to evenly distribute the application request to the corresponding node server to complete the software load balancing process; wherein, the preset application scenario is an application scenario without a hardware load balancing device.

5. The method according to claim 3, characterized in that: The automated deployment process includes: In the template machine that configures the non-cluster deployment mode and the management agent, the node server is horizontally expanded through virtual machine replication to complete the virtual machine replication deployment process; Through automated scripts, batch deployment and management are achieved to complete the script automation process.

6. The method according to claim 3, characterized in that: The centralized monitoring process includes: Monitor the operating status of multiple node servers in real time; If the running state is a fault state, obtaining an error log of the node server in the fault state; The node server in the fault state is diagnosed and processed according to the error log.

7. The method according to claim 3, characterized in that The status check process includes: Update and monitor the running status of WebLogic domain instances in real time, and monitor the running status of each WebLogic domain instance through the health monitoring uniform resource locator; When a failure is detected in the operation status of each WebLogic domain instance, the WebLogic domain instance is restarted through the agent program deployed on the node server to implement fault repair and complete the status check process.

8. The method according to claim 3, characterized in that The process of domain instance maintenance includes: The process of starting a domain instance can be realized through one-click operation of the operation and maintenance menu of the character interface; For node servers in a faulty state, user connection requests in a faulty state are automatically blocked through health checks, and domain instances in a faulty state are stopped and isolated to complete the process of stopping domain instances.

9. The method according to claim 3, characterized in that: The process of creating a domain instance includes: Through the character interface menu, a new WebLogic domain instance is automatically created with one click, and the startup user credentials of the new WebLogic domain instance are stored; Set rich socket denial by configuring rich socket protocol access; Set up rich sockets by configuring the rich sockets protocol port.

10. An application automation control device, characterized in that: The device comprises: A resource isolation unit is used to isolate resources of each middleware WebLogic instance; wherein each middleware WebLogic instance runs on a different physical server and shares their state information with each other; The optimized deployment unit is used to optimize the deployment of each set of middleware WebLogic instances after resource isolation through horizontal expansion and vertical expansion to achieve system load balancing, flexible expansion, failover and security management; wherein, the horizontal expansion is used to share the load by adding node servers, and when any node server fails, other node servers provide services normally; the vertical expansion is used to ensure the consistency of node servers in the load balancing of horizontal expansion.

Images