A task management method, apparatus, storage medium, and device

Abstract

This application provides a task management method, apparatus, storage medium, and device. In this method, a system command line is used as the unique format for global tasks. A task agent is deployed before the system command line entry point. This task agent verifies the correctness of issued tasks and schedules their execution. Furthermore, the task agent collects task and system information for querying by both remote and local management terminals. This allows both terminals to understand the current task and system status in real time, enabling the creation of planned tasks tailored to system and business characteristics. This optimizes task scheduling and management, effectively avoiding conflicts between remote and local management operations.

Description

Technical Field

[0001] This application relates to the field of task scheduling technology, and more specifically, to a task management method, apparatus, storage medium, and device. Background Technology

[0002] With the development of cloud computing technology, remote management has become the primary method of task scheduling, improving work efficiency by remotely distributing management tasks to business systems. However, in many cases, local management is also an indispensable management tool. If both local and remote management exist simultaneously, business conflicts can easily arise because local and remote administrators cannot understand each other's management operations. Summary of the Invention

[0003] The purpose of this application is to provide a task management method, apparatus, storage medium, and device, which aims to solve the problem of conflict between remote management and local management in related technologies.

[0004] In a first aspect, embodiments of this application provide a task management method, the method being applied to a task agent, the task agent being deployed in a business system, the method comprising:

[0005] When a command-line based task is received, it is verified whether the task matches the system type of the business system; the task is sent by a remote management terminal or a local management terminal, and the remote management terminal and the local management terminal have established communication channels with the business system respectively.

[0006] If the verification result is yes, extract the command line from the task and input it into the command line entry of the business system so that the business system executes the task.

[0007] Collect task information and system information, and provide the task information and system information to the remote management terminal and the local management terminal for querying; wherein the task information includes information representing the task status, and the system information includes information representing the system status.

[0008] In the above implementation, the system command line is used as the sole format for global tasks. A task agent is deployed before the system command line entry point. This task agent verifies the correctness of issued tasks and schedules their execution. It also collects task and system information for remote and local management terminals to query. This allows both terminals to understand the current task and system status in real time, enabling the creation of planned tasks tailored to system and business characteristics. This optimizes task scheduling and management, effectively avoiding conflicts between remote and local management processes.

[0009] Furthermore, in some embodiments, the task is sent based on a command set, which is established based on the system type of multiple business systems managed by the remote management terminal and the command format of each business system.

[0010] In the above implementation process, a command set based on system type is established. The management terminal can send commands to the corresponding business system based on this command set. The business system can then verify the correctness of the issued tasks, thereby solving the problems caused by changes in command format due to system upgrades and other business operations, which lead to changes in system type, as well as the problems caused by the remote management terminal issuing incorrect commands.

[0011] Furthermore, in some embodiments, the communication channel is composed of a trusted tunnel.

[0012] In the above implementation process, the local management terminal, remote management terminal, and system terminal form a linked task system through a trusted tunnel. This enables complex scheduling for various tasks, allows for division of labor and cooperation between remote and local administrators, and keeps the system in a healthy and stable state.

[0013] Furthermore, in some embodiments, the task agent provides a query interface, and the provision of the task information and system information to the remote management terminal and the local management terminal for querying includes:

[0014] The task information and system information are stored in the system database so that the remote management terminal and the local management terminal can query the task information and system information in the system database through the query interface.

[0015] In the above implementation process, the task agent stores the collected relevant information in the database and provides a unified query interface, so that remote management end and local management end can understand the current task status and system status in real time by calling the query interface, and build planned tasks suitable for system characteristics and business characteristics, while ensuring the consistency of query data between remote end and local end.

[0016] Furthermore, in some embodiments, the method further includes:

[0017] If a second task that is mutually exclusive with the first task is received before the first task is started, the execution of both the first and second tasks is stopped, and the result of the mutual exclusion task conflict is returned.

[0018] If a second task is received while the first task has already started executing, the execution of the second task is stopped, and a result indicating that the first task was successfully executed and a result indicating that the second task failed to execute are returned.

[0019] The first and second task distribution tasks are sent by different management terminals.

[0020] In the above implementation process, the above processing logic enables task collaboration for complex business operations by different administrators, increasing the flexibility of system management.

[0021] Furthermore, in some embodiments, the method further includes:

[0022] If the second task is received within a specified time after the first task has been completed, the second task will continue to be executed, and alarm information will be sent to the remote management terminal and the local management terminal.

[0023] In the above implementation process, the above processing logic more effectively avoids business conflicts.

[0024] Secondly, this application provides a task management device, which is applied to a task agent deployed in a business system. The device includes:

[0025] The task verification module is used to verify whether the task received in the command-line format matches the system type of the business system. The task is sent by a remote management terminal or a local management terminal, and the remote management terminal and the local management terminal have established communication channels with the business system respectively.

[0026] The scheduling and execution module is used to extract the command line from the task being issued and input it into the command line entry of the business system if the verification result is yes, so that the business system executes the task being issued.

[0027] An information collection module is used to collect task information and system information, and provide the task information and system information to the remote management terminal and the local management terminal for querying; wherein the task information includes information representing the task status, and the system information includes information representing the system status.

[0028] Thirdly, an electronic device provided in this application includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method as described in any of the first aspects.

[0029] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described in any of the first aspects.

[0030] Fifthly, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to perform the method described in any of the first aspects.

[0031] Other features and advantages disclosed in this application will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the above-described technology disclosed in this application.

[0032] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 A flowchart illustrating a task management method provided in an embodiment of this application;

[0035] Figure 2 A schematic diagram illustrating a collaborative task system constructed using a task scheduling scheme with a command-line call interface system, as provided in an embodiment of this application;

[0036] Figure 3 A block diagram of a task management device provided in an embodiment of this application;

[0037] Figure 4 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0039] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0040] As described in the background section, related technologies suffer from conflicts between remote management and local management operations. Therefore, this application provides a task management solution to address these issues.

[0041] The embodiments of this application will be described below:

[0042] like Figure 1 As shown, Figure 1 This is a flowchart illustrating a task management method provided in an embodiment of this application. The method is applied to a task agent, which is deployed in a business system. In a network security scenario, this business system can be any of a firewall system, intrusion prevention system, network audit system, or other similar systems. Of course, in other scenarios, the business system can be a hardware or software system that implements a specific function within that scenario. In this embodiment, a task agent is deployed in the business system. This task agent can be considered a script or executable program, used as an entry point for command invocation and status query, thereby resolving the conflict between remote and local management operations.

[0043] The method includes:

[0044] In step 101, when a command-line based task is received, it is verified whether the task matches the system type of the business system; the task is sent by a remote management terminal or a local management terminal, and the remote management terminal and the local management terminal have established communication channels with the business system respectively.

[0045] A command line, also known as a command prompt, is a prompt in an operating system that prompts for command input. In practical applications, multiple systems are remotely managed, and the command formats of different system types are inconsistent. Therefore, this embodiment solves the problem of frequent command format conversion by using the system command line as the unique format for global tasks. In some embodiments, the task distribution mentioned in this step can be sent from a command set, which is established based on the system type and command format of the multiple business systems managed by the remote management terminal. That is, in the preparation phase, a command set based on the system type can be established based on the system type and the command format of each system. Specifically, the command format of each system can be obtained through automated script parsing or manually exported by technicians. The established command set can include multiple commands, each of which can be equivalent to a task and can include information such as device type, task ID, task category, task duration, business type, and command line. The management terminal can send commands to the corresponding business system based on this command set. After receiving the command, the business system can verify whether the issued task matches the system type, thereby verifying the correctness of the issued task. This solves the problems caused by changes in command format due to system upgrades and other business operations, which lead to changes in system type, as well as the problems caused by the remote management terminal issuing incorrect commands.

[0046] The task agent serves as the communication channel between the business system and the two management endpoints to receive and distribute tasks. In some embodiments, this communication channel can be constructed using a trusted tunnel. A trusted tunnel is based on tunneling technology, which utilizes tunnels to achieve data transmission between networks. It uses one network protocol to transmit another, thereby supporting data transmission in incompatible or insecure networks. The establishment of a trusted tunnel typically relies on encrypted data transmission, integrity protection, and user authentication. The local management endpoint, remote management endpoint, and system endpoint form a collaborative task system through the trusted tunnel. This enables complex scheduling for various scenarios, including concurrent tasks, serial tasks, long-running tasks, short-running tasks, system states, and task states. It also allows for collaboration between remote and local administrators, ensuring a healthy and stable system state.

[0047] In step 102, if the verification result is yes, extract the command line from the task and input it into the command line entry of the business system so that the business system executes the task.

[0048] When the task assignment is verified to match the system type, indicating that the task is a correct command, the task agent extracts the command line from the task and inputs it into the command line entry point of the business system. The command line entry point is the interface that transmits the command line to the operating system so that the operating system can execute the corresponding operation. This achieves the scheduling and execution of the assigned task. Optionally, in implementation, the task agent can establish a task queue, with tasks assigned in a first-in, first-out order based on their assignment time. When the correctness verification of the assigned task passes, the task agent adds the assigned task to the task queue to await execution, thus ensuring the orderly execution of each task. Of course, in other embodiments, tasks can also be ordered and executed according to their priorities, and this application does not limit this.

[0049] In step 103, task information and system information are collected and provided to the remote management terminal and the local management terminal for querying; wherein the task information includes information representing the task status and the system information includes information representing the system status.

[0050] This embodiment deploys a task agent before the system command-line entry point and uses the task agent to collect task and system information, enabling both remote and local management terminals to query task and system information in real time. This allows for the selection of the appropriate time to issue tasks, thereby optimizing task scheduling and management in a timely manner and avoiding business conflicts.

[0051] Specifically, task information includes information representing task status, such as the length of the task queue, the execution time of each task, whether there is task blocking, the current number of tasks, and historical task statistics. System information includes information representing system status, such as which business processes the system is currently handling, whether system resource usage is stable, and whether customized planned tasks can be executed. In real-world scenarios, a system may have administrators with different identities performing different business processes, resulting in complex business requirements and scenarios. For example, some tasks consume a large amount of system resources, some tasks require a system restart, and some tasks are mutually exclusive. The solution in this embodiment uses a task agent to understand the system and task status in real time, which can help system administrators optimize task scheduling plans and avoid task conflicts.

[0052] In some embodiments, the task agent provides a query interface, and providing the task information and system information to the remote management terminal and the local management terminal for querying may include:

[0053] The task information and system information are stored in the system database so that the remote management terminal and the system can communicate with each other.

[0054] The local management terminal queries the system database for task information and system information through the query interface. In other words, the task agent stores the collected relevant information in the database and provides a unified query interface, allowing both remote and local management terminals to understand the current task and system status in real time by calling this interface. This enables the creation of planned tasks suitable for system and business characteristics, while ensuring consistency between remote and local query data. Optionally, this query...

[0055] The interface can be a RESTful API, that is, an API in the REST (Representational State Transfer) style (Application Programming Interface).

[0056] REST style is a web application interface style based on HTTP (Hypertext Transfer Protocol), which fully utilizes HTTP methods to achieve a unified style of interface service. This setup allows for decoupling between the front-end and back-end, improving security. Of course, in other embodiments, this query interface can also be other types of interfaces.

[0057] 5. In some embodiments, the above method may include: before the first task begins execution, if a second task mutually exclusive with the first task is received, the execution of the first task is stopped.

[0058] The system sends out the first task and the second task, and returns the result of the mutual exclusion task conflict; if the second task is received while the first task has already started executing, the execution of the first task is stopped.

[0059] The second task is issued, and a result indicating the success of the first task and a result indicating the failure of the second task are returned; wherein, the first task and the second task are...

[0060] Tasks are sent from different management endpoints. That is, when the task agent receives both a remote task and a local task, and these two tasks are mutually exclusive, if neither task has started executing, it will stop executing both tasks and return a result indicating a mutual exclusion task conflict. This result will then be handled by the remote administrator and...

[0061] The local administrator will handle the negotiation; if the proxy task received the remote task first and that remote task 5 has already started executing, then return a successful execution result for the remote task and a different result for the local task.

[0062] If the task fails to execute, the local administrator will contact the remote administrator to negotiate a solution. Conversely, if the proxy task first receives the local task and it has already started executing, then a successful execution result will be returned for the local task, while a failed execution result will be returned for the remote task, with the remote administrator contacting the local administrator to negotiate a solution. This enables task collaboration for complex business processes by different administrators, increasing the flexibility of system management.

[0063] Furthermore, in some embodiments, the above method may further include: if a second task is received within a specified time after the completion of the first task, the second task is executed, and an alarm message is sent to both the remote management terminal and the local management terminal. Continuing with the previous example, if a remote task has already been completed, and a local task is received within a specified time, such as one minute, the task agent continues to execute the local task, while simultaneously sending an alarm message to both the remote and local administrators, indicating a potential business conflict, allowing the local and remote administrators to confirm whether the business arrangement is reasonable. This more effectively avoids business conflicts.

[0064] In this embodiment, the system command line is used as the unique format for global tasks. A task agent is deployed before the system command line entry point. This task agent verifies the correctness of issued tasks and schedules their execution. Furthermore, the task agent collects task and system information for querying by both remote and local management terminals. This allows both terminals to understand the current task and system status in real time, enabling the creation of planned tasks tailored to system and business characteristics. This optimizes task scheduling and management, effectively avoiding conflicts between remote and local management processes.

[0065] To provide a more detailed explanation of the solution in this application, a specific embodiment is described below:

[0066] This embodiment provides a task scheduling scheme with a command-line interface system. A task system linking remote management, local management, and system terminals built using this scheme is as follows: Figure 2 As shown, remote management terminal 21 manages system A (marked as 22 in the figure) and system N (marked as 23 in the figure), first local management terminal 24 is the local management terminal of system A, and second local management terminal 25 is the local management terminal of system N. In this embodiment, task agent 222 is deployed before the command line entry 221 of system A, and database 223 is deployed within system A; similarly, task agent 232 is deployed before the command line entry 231 of system N, and database 233 is deployed within system N.

[0067] Specifically, the workflow for building this collaborative task system includes:

[0068] S201. Construct a command set based on system type;

[0069] S202. Construct a task agent, which includes the following four modules: a task verification module, used to verify the validity of a command by comparing the obtained system type with the system type in the issued command; a task management module, used to establish a task queue and perform first-in-first-out operations based on the task issuance time; a status collection module, used to obtain the status of system resources such as CPU, memory, and disk, task queue length, task execution time, etc., through customized plugins, and save the information for the day to the system database; and a status query module, used to provide a unified query interface using the status data in the system database.

[0070] S203. Establish a task linkage system between the local management terminal, the remote management terminal, and the system terminal based on a trusted tunnel; specifically, establish a secure communication system among the three parties based on security mechanisms such as SSL (Secure Socket Layer) and certificates. In this way, the two management terminals can issue tasks in real time and query the real-time status of the system based on the communication system.

[0071] S204. The status collection module of the task agent collects relevant information and stores it in the database. Specifically, the storage time limit is set according to the system's own capabilities and business capabilities.

[0072] S205, the local management terminal and the remote management terminal access the system's query interface through the HTTP protocol to understand the system's real-time status.

[0073] The process for resolving security policy conflicts between local and remote administrators using the solution in this embodiment includes:

[0074] S211. The remote management terminal queries the task agent and finds that there are no security policy tasks, the system status is normal, and security policy tasks can be issued.

[0075] S212. The local management terminal finds through the task agent that there are no security policy tasks, the system status is normal, and security policy tasks can be issued.

[0076] S213. The remote management terminal issues a security policy task to enable ping permission; the security policy task is {Device type: NGTOS, Task ID: 123, Task category: {mutual exclusion}, Task duration: {30 seconds}, Service type: {security policy}, Command line: "pf service add name ping area eth0"}.

[0077] S214. The local management terminal issues a security policy task to prohibit ping permission; the security policy task is {Device type: NGTOS, Task ID: 456, Task category: {mutual exclusion}, Task duration: {30 seconds}, Service type: {security policy}, Command line: "pf service clean name ping"}.

[0078] S215. If the task agent receives the remote security policy task first, it adds it to the task queue to wait for execution and processes it according to the following logic: If the local security policy task is received before the remote security policy task starts executing, the execution of both the remote and local security policy tasks is stopped, and a mutual exclusion task conflict result is returned, which is then negotiated and resolved by the remote and local administrators; If the remote security policy task has already started executing and the local security policy task is received at the same time, a successful execution result is returned for the remote security policy task, and a failed execution result is returned for the local security policy task, which is then negotiated and resolved by the local administrator with the remote administrator; If the local security policy task is received within 1 minute after the remote security policy task has been completed, the local security policy task continues to execute, and an alarm message is sent to both the remote and local administrators, indicating the possibility of a business conflict, which is then confirmed by the remote and local administrators to determine whether the business arrangement is reasonable.

[0079] S216. If the task agent receives the local security policy task first, it adds it to the task queue to wait for execution and processes it according to logic similar to S215.

[0080] This embodiment has at least the following advantages: First, by using the system command line as the unique format for global tasks, the problem of frequent command format conversion is solved; Second, by establishing a command set based on system type, the system can verify the correctness of tasks issued by the remote management terminal; Third, by deploying a task agent before the system command call interface, administrators can coordinate and resolve business conflicts between remote and local terminals, and optimize the task scheduling process; Fourth, by deploying a status database within the system and providing a unified query interface through the task agent, the data consistency problem caused by the distributed structure is avoided, and tasks within a certain period of time can be audited, facilitating the tracing of security issues. It can also realize task collaboration for complex businesses by different administrators, increasing the flexibility of system management.

[0081] Corresponding to the embodiments of the aforementioned methods, this application also provides embodiments of a synchronization strategy processing device and a terminal for its application:

[0082] like Figure 3 As shown, Figure 3 This is a block diagram of a synchronization strategy processing device provided in an embodiment of this application. The device is applied to a network gateway device and includes:

[0083] The strategy acquisition module 31 is used to acquire synchronization strategy information if a user's synchronization strategy operation is detected; the synchronization strategy operation is an addition operation, modification operation, and / or deletion operation of the original synchronization strategy information.

[0084] The strategy delivery module 32 is used to establish a connection with the target client based on the client address in the synchronization strategy information, and send the synchronization strategy information to the target client.

[0085] The result feedback module 33 is used to receive the policy loading result returned by the target client and feed the policy loading result back to the user.

[0086] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0087] This application also provides an electronic device, please refer to [link to application]. Figure 4 , Figure 4 This is a structural block diagram of an electronic device provided in an embodiment of this application. The electronic device may include a processor 410, a communication interface 420, a memory 430, and at least one communication bus 440. The communication bus 440 is used to enable direct communication between these components. In this embodiment, the communication interface 420 of the electronic device is used for signaling or data communication with other node devices. The processor 410 may be an integrated circuit chip with signal processing capabilities.

[0088] The processor 410 described above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The processor 410 described above can be a microprocessor, or it can be any conventional processor.

[0089] The memory 430 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc. The memory 430 stores computer-readable instructions. When these computer-readable instructions are executed by the processor 410, the electronic device can perform the aforementioned operations. Figure 1 The various steps involved in the method implementation examples.

[0090] Alternatively, the electronic device may also include a storage controller and an input / output unit.

[0091] The memory 430, storage controller, processor 410, peripheral interface, and input / output unit are electrically connected directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses 440. The processor 410 is used to execute executable modules stored in the memory 430, such as software function modules or computer programs included in electronic devices.

[0092] The input / output unit is used to provide users with the ability to create tasks and to set optional start periods or preset execution times for those tasks, thereby enabling user-server interaction. The input / output unit may be, but is not limited to, a mouse and keyboard.

[0093] Understandable. Figure 4 The structure shown is for illustrative purposes only; the electronic device may also include components that are more advanced than those shown. Figure 4 The more or fewer components shown, or having the same Figure 4 The different configurations shown. Figure 4 The components shown can be implemented using hardware, software, or a combination thereof.

[0094] This application also provides a storage medium storing instructions. When the instructions are run on a computer, the computer program is executed by a processor to implement the method described in the method embodiment. To avoid repetition, the method will not be described again here.

[0095] This application also provides a computer program product that, when run on a computer, causes the computer to perform the method described in the method embodiment.

[0096] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0097] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0098] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0099] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0100] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0101] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A task management method characterized by, The method is applied to a task agent, which is deployed in a business system. The method includes: When a command-line based task is received, it is verified whether the task matches the system type of the business system; the task is sent by a remote management terminal or a local management terminal, and the remote management terminal and the local management terminal have established communication channels with the business system respectively. If the verification result is yes, extract the command line from the task and input it into the command line entry of the business system so that the business system executes the task. Collect task information and system information, and provide the task information and system information to the remote management terminal and the local management terminal for querying; wherein the task information includes information representing the task status, and the system information includes information representing the system status.

2. The method according to claim 1, characterized in that, The task is sent based on a set of commands, which is established based on the system types and command formats of multiple business systems managed by the remote management terminal.

3. The method according to claim 1, characterized in that, The communication channel is composed of a trusted tunnel.

4. The method according to claim 1, characterized in that, The task agent provides a query interface, and the provision of the task information and system information to the remote management terminal and the local management terminal for querying includes: The task information and system information are stored in the system database so that the remote management terminal and the local management terminal can query the task information and system information in the system database through the query interface.

5. The method according to claim 1, characterized in that, The method further includes: If a second task that is mutually exclusive with the first task is received before the first task is started, the execution of both the first and second tasks is stopped, and the result of the mutual exclusion task conflict is returned. If a second task is received while the first task has already started executing, the execution of the second task is stopped, and a result indicating that the first task was successfully executed and a result indicating that the second task failed to execute are returned. The first and second task distribution tasks are sent by different management terminals.

6. The method according to claim 5, characterized in that, The method further includes: If the second task is received within a specified time after the first task has been completed, the second task will continue to be executed, and alarm information will be sent to the remote management terminal and the local management terminal.

7. A task management device, characterized in that, The device is used in a task agent, the task agent is deployed in a business system, and the device includes: The task verification module is used to verify whether the task received in the command-line format matches the system type of the business system. The task is sent by a remote management terminal or a local management terminal, and the remote management terminal and the local management terminal have established communication channels with the business system respectively. The scheduling and execution module is used to extract the command line from the task being issued and input it into the command line entry of the business system if the verification result is yes, so that the business system executes the task being issued. An information collection module is used to collect task information and system information, and provide the task information and system information to the remote management terminal and the local management terminal for querying; wherein the task information includes information representing the task status, and the system information includes information representing the system status.

8. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, It stores a computer program thereon, which, when executed by a processor, implements the method as described in any one of claims 1 to 6.

10. An electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as claimed in any one of claims 1 to 6.

Images