An integrated method and system for service assembly, deployment and operation

Abstract

This application provides an integrated method and system for service assembly, deployment, and operation and maintenance. The service assembly process involves associating service definition information with the application based on the parsing results of the application package. The service deployment process involves collecting application status information through the host node's agent when the host node is online. The service operation and maintenance process involves sending operation and maintenance instructions to the agent to handle abnormal applications when the application status information does not meet alarm conditions. This system supports different operating systems, physical machines, virtual machines, cloud platforms, and various types of components, highly automating service development, deployment, and operation and maintenance, reducing the software deployment difficulty in the integration and deployment process, and improving the automation level of service assembly and deployment.

Description

Technical Field

[0001] This application relates to the field of application integration, and more specifically, to an integrated method and system for service assembly, deployment, and operation and maintenance. Background Technology

[0002] Current application integration platforms suffer from several problems: First, they are difficult to build. Before such platforms existed, developers had to handle all aspects of development themselves, including both business and operational issues. This placed extremely high demands on developers and significantly reduced the number of applications produced. Second, because many capabilities are reusable, traditional methods resulted in high costs and low efficiency in developing individual applications. Third, the application packaging process is complex. Component deployment and release heavily rely on application packaging tools, but these tools vary greatly in quality. Application packages generated by different tools can only use their respective deployment tools and are difficult to port to other platforms. Fourth, there is a lack of unified release and deployment tools for different types of components. Enterprise applications include various types such as web services, backend services, and EXE client plugins, all lacking a unified release and deployment tool. Fifth, operational capabilities are weak. Application integration tools on the market focus more on release and deployment, neglecting post-development operations. However, application development often requires more maintenance, leading to difficulties in software maintenance and frequent manual intervention, resulting in significant wasted maintenance costs.

[0003] To this end, this application provides a unified technical roadmap and solution for application deployment and supports the rapid service-oriented transformation of legacy systems. Summary of the Invention

[0004] The purpose of this application is to overcome the shortcomings of existing technologies and provide an integrated method and system for service assembly, deployment, and operation and maintenance. This purpose is achieved through the following technical solution:

[0005] In a first aspect, this application proposes an integrated method for service assembly, deployment, and operation and maintenance, applied to a service integration system, wherein the service integration system is connected to both an integration platform control center and host nodes, and the method includes:

[0006] The application packets sent by the integrated platform control center are parsed, and the service definition information is associated with the application based on the parsing results to complete the service assembly process.

[0007] The service for activating the assembly determines whether the host node is online based on the deployment instructions sent by the integration platform control center.

[0008] When the host node is online, the application package is sent to the proxy of the host node so that the proxy can collect application status information to complete the service deployment process;

[0009] The system determines whether the received application status information meets the alarm conditions based on the rules in the service integration system.

[0010] If the alarm conditions are not met, an operation and maintenance instruction is sent to the agent to handle the abnormal application in order to complete the operation and maintenance of the service.

[0011] Optionally, the step of parsing the application package sent by the integration platform control center and associating service definition information with the application based on the parsing result to complete the service assembly includes:

[0012] The application package sent by the integrated platform control center is parsed to obtain the basic information of the application package and the root directory tree;

[0013] The application package basic information and the root directory tree are sent to the integration platform control center for display and query, so that the integration platform control center can define services for the application deployment process based on the service definition information.

[0014] The service definition information sent by the integrated platform control center is associated with the application to complete the service assembly.

[0015] Optionally, the agent completes the steps of deploying the service, including:

[0016] The agent decompresses the application package to obtain application configuration information;

[0017] The agent parses the application configuration information and executes the service definition process script file;

[0018] The agent collects application status information and sends the application status information to the service integration system to complete the service deployment.

[0019] Optionally, the step of determining whether the received application status information meets the alarm conditions according to the rules in the service integration system includes:

[0020] Configure threshold monitoring rules, log monitoring rules, and runtime status monitoring rules;

[0021] Bind monitoring rules to applications and set system actions when alarm rules are triggered;

[0022] The activation rule is set by comparing the application status information with the activation rules in the system.

[0023] Optionally, before parsing the application packet sent by the integration platform control center, the method further includes:

[0024] The integrated platform control center receives application packages sent by the user terminal and determines whether the application package meets the application package format.

[0025] If the application package meets the application package format, the application package is uploaded to the service publishing, deployment and integration system.

[0026] Secondly, this application proposes a service integration system, characterized in that the service integration system is connected to both an integration platform control center and a host node, and the system includes:

[0027] The application assembly module is used to parse the application package sent by the integration platform control center, and associate the service definition information with the application based on the parsing result to complete the service assembly process.

[0028] The application deployment module is used to activate the assembled services and determine whether the host node is online based on the deployment instructions sent by the integration platform control center.

[0029] The application deployment module is also used to send the application package to the proxy of the host node when the host node is online, so that the proxy can collect application status information to complete the service deployment process;

[0030] The application operation and maintenance module is also used to determine whether the received application status information meets the alarm conditions according to the rules in the service integration system.

[0031] The application operation and maintenance module is also used to send operation and maintenance instructions to the agent to handle abnormal applications if the alarm conditions are not met, so as to complete the operation and maintenance of services.

[0032] Optionally, the application assembly module is specifically used for:

[0033] The application package sent by the integrated platform control center is parsed to obtain the basic information of the application package and the root directory tree;

[0034] The application package basic information and the root directory tree are sent to the integration platform control center for display and query, so that the integration platform control center can define services for the application deployment process based on the service definition information.

[0035] The service definition information sent by the integrated platform control center is associated with the application to complete the service assembly.

[0036] Optionally, the application operation and maintenance module is specifically used for:

[0037] Configure threshold monitoring rules, log monitoring rules, and runtime status monitoring rules;

[0038] Bind monitoring rules to applications and set system actions when alarm rules are triggered;

[0039] The activation rule is set by comparing the application status information with the activation rules in the system.

[0040] The main solution and its various further alternatives described above can be freely combined to form multiple solutions, all of which are solutions that can be adopted and are claimed in this application; furthermore, the (non-conflicting alternatives) can also be freely combined with each other and with other alternatives. Those skilled in the art, after understanding the solution of this application, will realize from the prior art and common general knowledge that there are many combinations, all of which are technical solutions to be protected by this application, and will not be exhaustively listed here.

[0041] This application provides an integrated method and system for service assembly, deployment, and operation and maintenance. The service assembly process involves associating service definition information with the application based on the parsing results of the application package. The service deployment process involves collecting application status information through the host node's agent when the host node is online. The service operation and maintenance process involves sending operation and maintenance instructions to the agent to handle abnormal applications when the application status information does not meet alarm conditions. This system supports different operating systems, physical machines, virtual machines, cloud platforms, and various types of components, highly automating service development, deployment, and operation and maintenance, reducing the software deployment difficulty in the integration and deployment process, and improving the automation level of service assembly and deployment. Attached Figure Description

[0042] Figure 1 A schematic diagram illustrating an application scenario of the service integration system proposed in this application is shown.

[0043] Figure 2 A schematic diagram of a service integration system proposed in an embodiment of this application is shown.

[0044] Figure 3 The illustration shows a flowchart of an integrated method for service assembly, deployment, and operation and maintenance provided in an embodiment of this application.

[0045] Figure 4 A flowchart illustrating step S110 of an embodiment of this application is shown. Detailed Implementation

[0046] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.

[0047] Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0048] In existing technologies, application integration platforms suffer from many problems, such as high application building difficulty, weak operation and maintenance capabilities, complex application packaging processes, and a lack of unified release and deployment tools for different types of components. To address these issues, this application proposes an integrated method and system for service assembly, deployment, and operation and maintenance. This system can support the rapid service-oriented transformation of legacy systems, as well as different operating systems, physical machines, virtual machines, cloud platforms, and various types of components. It reduces the difficulty of software deployment during the integration and deployment process, improves the automation level of service assembly and deployment, and thus solves the aforementioned problems. The integrated method and system for service assembly, deployment, and operation and maintenance will be described in detail below.

[0049] Please refer to Figure 1 , Figure 1 The illustration shows an application scenario diagram of the service integration system proposed in this application embodiment. The service assembly, deployment, and operation and maintenance integration method proposed in the application embodiment is applied to the service integration system, wherein the service integration system is connected to the integration platform control center and the host node respectively. In addition, the integration method can also be applied to the integrated deployment of server and client.

[0050] The integration platform control center provides users with various visualized operations for issuing commands to manage the service integration process, including host node management, application assembly, application monitoring, and application maintenance. Host node management involves communication between the service integration system and agents on each host, with the service integration system distributing host configuration information to the agents.

[0051] A host node consists of multiple hosts, each with a corresponding agent. The service integration system pushes services to each host through the agent on the host. The host agent also sends the application status information running on the host to the application service integration system for data support for operation and maintenance management. The host is the infrastructure that provides computing and storage resources for the system nodes. It can be a physical server, a virtual host, or a cloud server. The operating systems supported by the host include Linux and Windows.

[0052] based on Figure 1 Please refer to Figure 2 , Figure 2 The diagram shows a structural schematic of a service integration system proposed in an embodiment of this application. The service integration system includes not only an application assembly module, an application deployment module, and an application operation and maintenance module, but also a host node management module, an application monitoring module, and an application registration module.

[0053] The application registration module provides an application registration mechanism that offers services for various types of applications, including remote procedure calls, representational state transfers, and structures (MSG) in Windows programs. It also provides the function of automatically registering services with the service registry and acting as a proxy for accessing other services. The service registry is mainly used in the application development phase. By registering services with the service registry, open APIs can be provided for other services to call.

[0054] The host node management module communicates with the agents on each host to distribute host configuration information to the host nodes. This allows for host management before service assembly and deployment. Host management includes all host registration, host information collection, host operation and maintenance management, and host script execution. Host registration is accomplished through an agent installed on the client side, registering the host with the system. Different operating systems use a unified client agent.

[0055] After host registration is complete, the client agent first collects information on each host node, including host operation overview, host operation status, average load, disk usage, memory usage, swap space usage, etc., and sends it to the host node management module for caching. At the same time, it provides a display and query of the host information list, and filters the host list based on conditions such as status, operating system, and data center.

[0056] Host operation and maintenance management provides the necessary routine maintenance operations for the hosts on the system, including: starting monitoring, stopping monitoring, restarting monitoring, uninstalling a host, forcibly uninstalling a host, and upgrading agents. Commands are issued from the integration platform control center to the host node management module, which forwards them to the hosts. The hosts then send the instructions to the corresponding host nodes, which in turn execute the maintenance operations as agents.

[0057] Host script execution is used to extend system functionality and can support any operation that can be performed in script form, such as time synchronization, hostname modification, log cleanup, data backup, etc. The script form can be shell or Python script, which is written by the user. The script is uploaded to the host node management module through the integration platform control center. The host node management module then hands it over to the corresponding host node agent to execute the script and send the execution result back to the host node management module for display.

[0058] In addition, the host node management module can also perform host monitoring configuration, host basic information management, and host operation and maintenance management. Host monitoring configuration is used to configure the information collected by the host node, host basic information management is used to set aliases and other information for the host to facilitate the viewing of host information, and host operation and maintenance management is used to perform actions such as upgrading, restarting, uninstalling, and disabling.

[0059] The application assembly module is used to parse the application packages sent by the integration platform control center after the host node management module has completed the management of the host. Based on the parsing results, it associates the service definition information with the application to complete the service assembly process.

[0060] Optionally, the application assembly module can also store basic application maintenance information in JSON format and ultimately publish it as an application package that tools can recognize. The application assembly module packages the configured web application into a deployable web application package, packages the configured EXE application into a deployable client application package, and identifies the application package and application configuration information in the ZIP archive, verifies the format, and stores it on the application side as a deployable application package.

[0061] The application assembly module provides a service assembly process that eliminates the need for packaging. It uses description files to declare dependencies between services, configuration files, configuration items, and monitoring metrics, enabling the maintenance of relevant information and configuration details, thus completing service assembly. One-click configuration of application packages facilitates rapid application deployment and helps manage all components provided by enterprise developers. The application assembly module also supports custom aliases for services and components, making names more suitable for business system application scenarios.

[0062] The application deployment module is used to activate the assembled services. Based on the deployment instructions sent by the integration platform control center, it determines whether the host node is online. If the host node is online, it sends the application package to the host node's agent, enabling the agent to collect application status information to complete the service deployment process.

[0063] The application deployment module can obtain the web application deployable application package and client application deployable application package containing application version and version configuration information sent by the application assembly module. It generates an interface and sends the application package to the web application proxy and client application proxy (the proxy of the host node) through the generated interface. The proxy obtains the web service application instance and exe client application instance according to the application package and deploys them on the server and client respectively. After deployment, the proxy sends the application process information and proxy running information to the application deployment module to display the application process information, running status information and proxy running information.

[0064] Furthermore, during the service deployment process, the application deployment module uploads the packaged application package to the host node. The host node's proxy unzips the application package to a specified address and executes the scripts configured for the application package, including pre-installation scripts, installation process scripts, pre-startup scripts, and startup process scripts, completing the application deployment process. The application deployment module offers both batch deployment and single-application deployment modes. Single-application deployment involves selecting an application package, performing port checks before deployment, and then selecting an available host for deployment. After deployment, the application package runs on the host. Batch deployment allows selecting multiple application packages for application orchestration, and finally deploying them to the selected hosts with a single click. The application deployment module provides the ability to query application package information, modify related information, and delete application packages on the server. When querying application package information for an already deployed application, if an updated version of the application is found, an application upgrade function is provided.

[0065] The application monitoring module, after the application deployment module completes service deployment, sends application process information to the application operations and maintenance module to monitor the application status and dynamic state of the service. It collects component information in real time, monitors component status according to system rules, and handles component anomalies through automatic repair and user notification. Automatic repair automatically repairs components and handles alarms based on built-in system rules, while user notification allows users to manually repair components based on alarm prompts.

[0066] Optionally, the application monitoring module monitors the application's running status, runtime, and other operational information. It also issues commands to start, stop, and restart the application, and acquires application runtime data, CPU consumption, and memory consumption. It can retrieve and view application information running on each host. It controls the start, stop, and restart of each application process and views alarm information. It communicates with the host node's agent to obtain and manage service operation information. The application monitoring module manages the application status, and the front end controls the application status. The application monitoring module detects the application status and sends control information to the agent, which then starts or stops the service.

[0067] The application operation and maintenance module is used to determine whether the received application status information meets the alarm conditions according to the rules in the service integration system. If the alarm conditions are not met, operation and maintenance instructions are sent to the agent to handle the abnormal application in order to complete the operation and maintenance of the service.

[0068] The application operations and maintenance module primarily provides visualized monitoring of application and host information, and can handle application anomalies according to rules. The module is configured with alarm rules, including threshold monitoring rules, log monitoring rules, and runtime status monitoring rules, as well as alarm rule handling strategies, such as issuing announcements, restarting the application, backing up the application, starting backup services, and setting up application guardians. The module periodically scans application runtime information, and once an alarm is detected, it handles it according to the alarm rule handling strategies.

[0069] Optionally, the application assembly module is specifically used for:

[0070] The application package sent by the integration platform control center is parsed to obtain the basic information of the application package and the root directory tree.

[0071] The application package's basic information and root directory tree are sent to the integration platform control center for display and query, enabling the integration platform control center to define services for the application deployment process based on the service definition information.

[0072] The service definition information sent by the integrated platform control center is associated with the application to complete the service assembly.

[0073] Optionally, the application operation and maintenance module is specifically used for:

[0074] Configure threshold monitoring rules, log monitoring rules, and runtime status monitoring rules;

[0075] Bind monitoring rules to applications and set system actions when alarm rules are triggered;

[0076] Setting rules for activation compares the application's status information with the activation rules within the system.

[0077] The following section provides a detailed explanation of the integration methods for service assembly, deployment, and operation. Please refer to [link / reference]. Figure 3 , Figure 3 The diagram illustrates a flowchart of an integrated method for service assembly, deployment, and operation and maintenance provided in an embodiment of this application. The specific implementation steps of this integrated method for service assembly, deployment, and operation and maintenance are as follows:

[0078] Step S110: Parse the application package sent by the integration platform control center, and associate the service definition information with the application based on the parsing results to complete the service assembly process.

[0079] The user uploads the application package to the integration platform control center. The integration platform control center forwards the application package to the service integration system for parsing. The service integration system then associates the service definition information with the application based on the parsing results to complete the service assembly process.

[0080] Optionally, before step S110, the integration platform control center receives the application package sent by the user terminal, determines whether the application package meets the application package format, and uploads the application package to the service release and deployment integration system if the application package meets the application package format.

[0081] The application packaging process does not rely on specific packaging tools and supports common packaging tools on the market. The application package is also suitable for various distribution platforms. The corresponding applications include web services (zip, jar), backend services (zip, jar), application services (exe, qml), database services (MySQL, Oracle), and messaging services (RabbitMQ, Kafka), etc.

[0082] Please refer to the service assembly process. Figure 4 , Figure 4 A flowchart illustrating step S110 of an embodiment of this application is shown. Step S110 includes the following sub-steps:

[0083] Step S111: Parse the application package sent by the integration platform control center to obtain the basic information of the application package and the root directory tree.

[0084] Basic application information includes application type, application size, and application storage path. The integration platform control center displays this basic application information for users to view. The root directory tree is the file directory after the application is unzipped, used to select files or folders during software configuration definitions without repeatedly reading information from within the application package.

[0085] Step S112: Send the basic information of the application package and the root directory tree to the integration platform control center for display and query, so that the integration platform control center can define services for the application deployment process based on the service definition information.

[0086] Service definitions include descriptions of services and components, dependency information between components, external link information, configuration file information, configuration item information, and global variable definitions. Service definitions include component dependency definitions, configuration dependency definitions, default configuration definitions, and monitoring metric definitions. Component dependency definitions define the dependencies between components, performing dependency checks and corresponding operations during component installation, startup, stopping, restarting, and uninstallation. Configuration dependency definitions define configuration file dependencies between different services. Default configuration definitions provide default values ​​for configuration items, displayed during service installation and allowing modification during the process. Using appropriate default values ​​can significantly reduce configuration changes during service installation. Monitoring metric definitions include monitoring metrics, alarm triggers, metric charts, service summary information, and metric collection strategies.

[0087] Step S113: Associate the service definition information sent by the integration platform control center with the application to complete the service assembly.

[0088] During service installation, the system creates services based on the defined metrics and displays them in the integration platform control center in the form of line graphs, stacked graphs, etc. After the user completes the service definition, the information is submitted to the service integration system for storage and associated with the application (service) to complete the service assembly.

[0089] After assembly is complete, the client activates the service. Only activated services can be deployed and used. Services can also be disabled during activation. Services that have not been deployed can be disabled, and disabled services will be unavailable in the service integration system.

[0090] After the service is assembled, it is necessary to manage the host nodes to manage the application deployment. The management of host nodes has been described in the host node management module above, and will not be described again in this embodiment.

[0091] Step S120: Activate the assembled service and determine whether the host node is online based on the deployment instructions sent by the integration platform control center.

[0092] Step S130: With the host node online, send the application package to the host node's agent so that the agent can collect application status information to complete the service deployment process.

[0093] The user client issues deployment commands to the service integration system through the integration platform control center. The service integration system receives the deployment commands and checks if the host node is online. If online, it pushes the application package to the host node; otherwise, it provides an error message. The host node's agent collects application status information to complete the service deployment process as follows:

[0094] The agent decompresses the application package to obtain the application configuration information.

[0095] The agent parses the application configuration information and executes the service definition process script file.

[0096] The agent collects application status information and sends it to the service integration system to complete the service deployment.

[0097] The host node's agent receives the application package pushed by the service integration system, decompresses it to obtain application configuration information, and executes the service definition process script file. Additionally, the host node's agent can read the host configuration information and place the decompressed application package in the host's configured directory. After the script file is executed, the application monitoring module in the service integration system scans system processes in real time. When the system process information matches the monitoring parameters configured for application monitoring, it captures the process PID (Process Identifier in the operating system), running parameters, and monitors CPU and memory usage, determining whether the process is starting, has started successfully, is running, or is experiencing a fault. The host node's agent then sends the collected application status to the application monitoring module for application monitoring and subsequent maintenance.

[0098] Step S140: Determine whether the received application status information meets the alarm conditions according to the rules in the service integration system.

[0099] Step S150: If the alarm conditions are not met, an operation and maintenance instruction is sent to the agent to handle the abnormal application in order to complete the operation and maintenance of the service.

[0100] Optionally, after the service deployment process, the application operation and maintenance module receives application status information sent by the application monitoring module through a real-time interface, caches it, and determines whether the application status is normal according to the set rules.

[0101] Optionally, you can set threshold monitoring rules, log monitoring rules, and runtime status monitoring rules;

[0102] Bind monitoring rules to applications and set system actions when alarm rules are triggered;

[0103] Setting rules for activation compares the application's status information with the activation rules within the system.

[0104] The application operations and maintenance module configures various types of rules, such as thresholds, log monitoring, and heartbeat monitoring. After the rules are set, monitoring rules are bound to the application, and system actions are set when alarm rules are triggered. Rule information, rule handling information, and rule application information are stored in the database. When a user activates a rule, the application operations and maintenance module periodically scans the application status information and application log information in the application monitoring module and compares them with the activated rules. When the application status information meets the alarm conditions, the application operations and maintenance module marks the application as alarmed and displays it visually to the control center. If there is an alarm handling action, the instruction is sent to the host node agent to perform operations and maintenance handling on the abnormal application.

[0105] This application provides an integrated method and system for service assembly, deployment, and operation and maintenance. The service assembly process involves associating service definition information with the application based on the parsing results of the application package. The service deployment process is completed by collecting application status information through the host node's agent when the host node is online. When the application status information does not meet alarm conditions, operation and maintenance instructions are sent to the agent to handle the abnormal application, thus completing the service operation and maintenance process. This system supports different operating systems, physical machines, virtual machines, cloud platforms, and various types of components, highly automating service development, deployment, and operation and maintenance, reducing the software deployment difficulty in the integration and deployment process, and improving the automation level of service assembly and deployment.

[0106] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An integrated method of service assembly, deployment and operation, characterized in that, The method is applied to a service integration system connected with an integration platform control center and a host node, and comprises the following steps: Analyzing an application package sent by the integration platform control center to obtain application package basic information and a root directory tree; Sending the application package basic information and the root directory tree to the integration platform control center for display and query, so that the integration platform control center defines services according to service definition information to deploy the application; Associating service definition information sent by the integration platform control center with the application to complete assembly of the service; Activating the assembled service, and judging whether the host node is online according to a deployment instruction sent by the integration platform control center; In the case that the host node is online, sending the application package to an agent of the host node to enable the agent to collect application state information, so as to complete a service deployment process; Judging whether the received application state information meets an alarm condition according to a rule in the service integration system; If the alarm condition is not met, sending an operation and maintenance instruction to the agent to operate and maintain an abnormal application, so as to complete a service operation and maintenance process.

2. The method of claim 1, wherein the service assembly, deployment and operation integration method is characterized by, The step of completing deployment of the service by the agent comprises the following steps: The agent decompresses the application package to obtain application configuration information; The agent analyzes the application configuration information to execute a service definition process script file; The agent collects application state information and sends the application state information to the service integration system to complete deployment of the service.

3. The method of claim 1, wherein the service assembly, deployment and operation integration method is characterized by, The step of judging whether the received application state information meets an alarm condition according to a rule in the service integration system comprises the following steps: Setting threshold monitoring rules, log monitoring rules and running state monitoring rules; Binding monitoring rules for the application and setting system actions triggered when the alarm rules are triggered; Setting a rule activation, and comparing the application state information with activated rules in the system.

4. The method of claim 1, wherein the service assembly, deployment and operation integration method is characterized by, Before analyzing the application package sent by the integration platform control center, the method further comprises the following steps: The integration platform control center accepts an application package sent by a user end, and judges whether the application package meets an application package format; In the case that the application package meets the application package format, uploading the application package to the service publishing and deployment integration system.

5. A service integration system characterized by, The service integration system is connected with an integration platform control center and a host node, and comprises the following components: An application assembly module for analyzing an application package sent by the integration platform control center to obtain application package basic information and a root directory tree; Sending the application package basic information and the root directory tree to the integration platform control center for display and query, so that the integration platform control center defines services according to service definition information to deploy the application; Associating service definition information sent by the integration platform control center with the application to complete assembly of the service; An application deployment module for activating the assembled service, and judging whether the host node is online according to a deployment instruction sent by the integration platform control center; The application deployment module is further configured to, when the host node is online, send the application package to an agent of the host node, so that the agent collects application state information to complete a service deployment process. The application operation and maintenance module is further configured to determine whether the received application state information satisfies an alarm condition according to a rule in a service integration system. The application operation and maintenance module is further configured to, if the alarm condition is not satisfied, send an operation and maintenance instruction to the agent to operate and maintain an application that is abnormally disposed, to complete operation and maintenance of the service.

6. The service integration system of claim 5, wherein, The application operation and maintenance module is specifically configured to: set a threshold monitoring rule, a log monitoring rule and a running state monitoring rule; bind the monitoring rule to the application and set a system action triggered when the alarm rule is triggered; set a rule activation, and compare the application state information with an activated rule in the system.

Images