System shutdown method and device, storage medium and electronic device

Abstract

The embodiment of the invention provides a system shutdown method and device, a storage medium and an electronic device.The method comprises the steps that the process of implementing shutdown of a target system is divided into a plurality of stages, and a plurality of target stages are obtained; operation and maintenance objects included in each operation and maintenance field of the target system are determined in each target stage, a plurality of operation and maintenance objects are obtained, and the operation and maintenance fields are the fields to which configuration applied for realizing functions of the target system belongs; determining a dependency relationship among the plurality of operation and maintenance objects; sorting the plurality of operation and maintenance objects based on the dependency relationship to obtain an operation and maintenance object control table; and performing shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table according to the execution sequence of the multiple target stages. According to the invention, the problem that the information system cannot be safely shut down is solved, and the effect of safely shutting down the information system is achieved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computers, and more particularly, to a method, apparatus, storage medium, and electronic device for shutting down a system. Background Art

[0002] In the related art, it is impossible to completely eliminate the potential risks and possible impacts during the shutdown process of an information system, and safe shutdown cannot be effectively guaranteed.

[0003] It can be seen that there is a technical problem in the related art that the information system cannot be safely shut down.

[0004] In view of the above problems existing in the related art, no effective solution has been proposed yet. Summary of the Invention

[0005] Embodiments of the present invention provide a method, apparatus, storage medium, and electronic device for shutting down a system, so as to at least solve the problem in the related art that an information system cannot be safely shut down.

[0006] According to an embodiment of the present invention, there is provided a method for shutting down a system, including: dividing the process of shutting down a target system into multiple stages to obtain multiple target stages; determining, in each of the target stages, operation and maintenance objects included in each operation and maintenance area of the target system to obtain multiple operation and maintenance objects, where the operation and maintenance area is an area to which the configuration applied to implement the functions of the target system belongs; determining the dependency relationships between the multiple operation and maintenance objects; sorting the multiple operation and maintenance objects based on the dependency relationships to obtain an operation and maintenance object control table; and performing a shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table in the execution order of the multiple target stages.

[0007] In an exemplary embodiment, determining, in each of the target stages, operation and maintenance objects included in each operation and maintenance area of the target system includes: when the target stage is an application shutdown stage and the operation and maintenance area is an application area, determining a first object included in the target system; and when there is a target service in the target system that depends on the first object, adjusting the object on which the target service depends to another object; after the object on which the target service depends is adjusted to the other object, determining whether the first object meets a first preset condition; and when the first object meets the first preset condition, determining the first object as the operation and maintenance object; where the first object includes at least one of the following: a transaction line, a data line, an object implementing a batch processing function, and an object implementing message passing.

[0008] In an exemplary embodiment, determining whether the first object meets the first preset condition includes: when the first object is a transaction line, determining whether the online transaction volume of the transaction line is zero and whether the duration of the zero online transaction volume is greater than a first preset duration; if the online transaction volume is zero and the duration of the zero online transaction volume is greater than the first preset duration, determining that the first object meets the first preset condition; when the first object is a data line, determining whether there is no data transmission on the data line and whether the duration of no data transmission is greater than a second preset duration; if there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determining that the first object meets the first preset condition; when the first object is an object implementing a batch processing function, determining whether the first object has no batch processing tasks and whether the duration of no batch processing tasks is greater than a third preset duration; if the first object has no batch processing tasks and the duration of no batch processing tasks is greater than the third preset duration, determining that the first object meets the first preset condition; when the first object is an object implementing message passing, determining whether the first object has no message passing tasks and whether the duration of no message passing tasks is greater than a fourth preset duration; if the first object has no message passing tasks and the duration of no message passing tasks is greater than the fourth preset duration, determining that the first object meets the first preset condition.

[0009] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the basic software shutdown phase and the operation and maintenance area is the software area, determining the second object included in the target system; determining whether the second object meets the second preset condition; if the second object meets the second preset condition, determining the second object as the operation and maintenance object; where the second object includes at least one of the following: transaction processing middleware software, message queue middleware software, database software, data transmission software, operating system software.

[0010] In an exemplary embodiment, determining whether the second object meets the second preset condition includes: when the second object is transaction processing middleware software, determining the transaction line corresponding to the transaction processing middleware software included in the application domain, and when the online transaction volume of the transaction line is zero and the duration of the zero online transaction volume is greater than the first preset duration, determining that the second object meets the second preset condition; when the second object is message queue middleware software, determining the object for implementing message passing corresponding to the message queue middleware software included in the application domain, and when there is no message passing task for the object for implementing message passing and the duration of no message passing task is greater than the fourth preset duration, determining that the second object meets the second preset condition; when the second object is database software, determining the shutdown state of the transaction processing middleware software, and when the shutdown state indicates that the transaction processing middleware software has been successfully shut down and the successful shutdown lasts for the fifth preset duration, determining that the second object meets the second preset condition; when the second object is data transmission software, determining the data line corresponding to the data transmission software included in the application domain, and when there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determining that the second object meets the second preset condition; when the second object is operating system software, determining the basic software included in the target system, and when all the basic software has been shut down and the shutdown lasts for the sixth preset duration, determining that the second object meets the second preset condition, where the basic software includes the transaction processing middleware software, the message queue middleware software, the database software, and the data transmission software.

[0011] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance domain of the target system in each of the target phases includes: when the target phase is the equipment shutdown phase and the operation and maintenance domain is the hardware storage domain, determining the third object included in the target system; determining whether the third object meets the third preset condition; and when the third object meets the third preset condition, determining the third object as the operation and maintenance object; where the third object includes at least one of the following: physical host, storage switch, disk device, tape library device, power module, computer room module.

[0012] In an exemplary embodiment, determining whether the third object meets the third preset condition includes: when the third object is a physical host, determining the operating system software running in the physical host; when the operating system software has been shut down and the shutdown duration lasts for a seventh preset duration, determining that the third object meets the third preset condition; when the third object is a storage switch, determining that the operating system of the target system has been shut down and the shutdown duration lasts for an eighth preset duration, determining that the third object meets the third preset condition; when the third object is a disk device, determining that the operating system of the target system has been shut down and the shutdown duration lasts for a ninth preset duration, determining that the third object meets the third preset condition; when the third object is a tape library device, determining that the operating system of the target system has been shut down and the shutdown duration lasts for a tenth preset duration, determining that the third object meets the third preset condition; when the third object is a power module, determining that the hardware devices included in the target system have been shut down and the shutdown duration lasts for an eleventh preset duration, determining that the third object meets the third preset condition, where the hardware devices include; when the third object is a computer room module, determining that the hardware devices included in the target system have been removed from the equipment rack, determining that the third object meets the third preset condition.

[0013] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the equipment shutdown phase and the operation and maintenance area is the security area, determining the fourth object included in the target system; determining whether the fourth object meets the fourth preset condition; when the fourth object meets the fourth preset condition, determining the fourth object as the operation and maintenance object; where the fourth object includes at least one of the following: an encryption software client, an encryption machine.

[0014] In an exemplary embodiment, determining whether the fourth object meets the fourth preset condition includes: when the fourth object is an encryption software client, determining the transaction line corresponding to the encryption software client included in the application field; when the online transaction volume of the transaction line is zero and the duration of the zero online transaction volume is greater than a first preset duration, determining that the fourth object meets the fourth preset condition; when the fourth object is an encryption machine, determining the data line for transmitting data corresponding to the encryption machine included in the target system; when there is no data transmission on the data line and the duration of no data transmission is greater than a second preset duration, determining that the fourth object meets the fourth preset condition.

[0015] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the equipment shutdown phase and the operation and maintenance area is the network area, determining the network switches included in the target system; when there is no network traffic in the network of the network switches and the physical hosts included in the target system have been shut down, determining the network switches as the operation and maintenance objects.

[0016] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the basic software shutdown phase and the operation and maintenance area is the batch scheduling area, determining the batch processing software included in the target system; when there is no batch processing task in the batch processing software and the duration without batch processing tasks is greater than the third predetermined duration, determining the batch processing software as the operation and maintenance object.

[0017] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the basic software shutdown phase and the operation and maintenance area is the monitoring tool area, determining the monitoring automation software included in the target system; when the transaction processing middleware software and the database software in the target system have both been shut down and the shutdown duration has lasted for the twelfth predetermined duration, determining the monitoring automation software as the operation and maintenance object.

[0018] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the resource recovery phase and the operation and maintenance area is the hardware storage area, determining at least one of the following included in the target system as the operation and maintenance object: physical machines, disk space, storage switches, disk devices, tape library devices, power modules, computer room modules.

[0019] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the resource recovery phase and the operation and maintenance area is the network operation and maintenance area, determining at least one of the following included in the target system as the operation and maintenance object: IP addresses, network bandwidth, network switches.

[0020] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the resource recovery phase and the operation and maintenance area is the security area, determining at least one of the following included in the target system as the operation and maintenance object: security certificates, encryption machines.

[0021] In an exemplary embodiment, when determining the operation and maintenance objects included in each operation and maintenance area of the target system in each target phase, it includes: when the target phase is the configuration cleaning phase and the operation and maintenance area is the application area, determining at least one of the following of the target system as the operation and maintenance object: the configuration entries of the system configuration of the target system, the automated change process of the target system, the configuration entries of the capacity configuration of the target system.

[0022] In an exemplary embodiment, when determining the operation and maintenance objects included in each operation and maintenance area of the target system in each target phase, it includes: when the target phase is the configuration cleaning phase and the operation and maintenance area is the security area, determining at least one of the following of the target system as the operation and maintenance object: the operation and maintenance login entries of the target system, the high-authority authorization media for system operation and maintenance of the target system.

[0023] In an exemplary embodiment, when determining the operation and maintenance objects included in each operation and maintenance area of the target system in each target phase, it includes: when the target phase is the configuration cleaning phase and the operation and maintenance area is the monitoring tool area, determining the monitoring policy of the target system as the operation and maintenance object.

[0024] In an exemplary embodiment, sorting multiple operation and maintenance objects based on the dependency relationship to obtain an operation and maintenance object control table includes: determining the phase operation and maintenance objects belonging to each target phase among the multiple operation and maintenance objects; performing the following operations for the phase operation and maintenance objects of each target phase to obtain the sub-control table of the target phase: determining the operation type of the phase operation and maintenance object; determining the implementation sequence number of the phase operation and maintenance object based on the dependency relationship; determining the quantity of the phase operation and maintenance object; determining the name of the operation and maintenance team for operating the phase operation and maintenance object; determining the operation effect of shutting down the phase operation and maintenance object; determining the task interval, where the task interval is used to indicate that after performing the shutdown operation on the phase operation and maintenance object, the next object of the phase operation and maintenance object is subjected to the shutdown operation after the task interval, generating the sub-control table based on the phase operation and maintenance object, the operation type, the implementation sequence number, the quantity, the operation and maintenance team name, the operation effect, and the task interval; sorting the multiple sub-control tables according to the execution order of the multiple target phases to obtain the operation and maintenance object control table.

[0025] In an exemplary embodiment, the process of shutting down the target system is divided into multiple stages, and the obtained multiple target stages include: dividing the process of shutting down the target system into an application shutdown stage, a basic software shutdown stage, a device shutdown stage, a device power-off stage, a resource recovery stage, and a configuration cleanup stage; and determining the application shutdown stage, the basic software shutdown stage, the device shutdown stage, the device power-off stage, the resource recovery stage, and the configuration cleanup stage as the target stages.

[0026] According to another embodiment of the present invention, there is provided a shutdown device for a system, including: a dividing module, configured to divide the process of shutting down the target system into multiple stages to obtain multiple target stages; a first determining module, configured to determine, in each of the target stages, the operation and maintenance objects included in each operation and maintenance area of the target system to obtain multiple operation and maintenance objects, where the operation and maintenance area is the area to which the configuration applied to implement the functions of the target system belongs; a second determining module, configured to determine the dependency relationships between the multiple operation and maintenance objects; a sorting module, configured to sort the multiple operation and maintenance objects based on the dependency relationships to obtain an operation and maintenance object control table; and an execution module, configured to perform a shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table in accordance with the execution order of the multiple target stages.

[0027] According to still another embodiment of the present invention, there is further provided a computer-readable storage medium, in which a computer program is stored, where the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0028] According to still another embodiment of the present invention, there is further provided an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0029] According to still another embodiment of the present invention, there is further provided a computer program product, including a computer program, where the steps of the methods in the various embodiments of the present application are implemented when the computer program is executed by a processor.

[0030] Through the present invention, first, the process of shutting down the target system can be divided to obtain multiple target stages. For each target stage, the operation and maintenance objects included in different operation and maintenance fields of the target system can be determined, and multiple operation and maintenance objects can be obtained. The dependency relationships between the multiple operation and maintenance objects are determined, and based on the dependency relationships, the multiple operation and maintenance objects are sorted to generate an operation and maintenance object control table. Finally, according to the sorting of the operation and maintenance objects in the operation and maintenance object control table and in combination with the execution order of the target stage, the shutdown operation is performed on the operation and maintenance objects. Since the entire shutdown process of the target system can be divided into different target stages, and then the operation and maintenance objects included in each operation and maintenance field in each target stage are determined, that is, all the operation and maintenance objects in the target system shutdown process can be comprehensively and effectively identified. Therefore, the technical problem of being unable to safely shut down the information system can be solved, and the effect of safely shutting down the information system can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 is a hardware structure block diagram of a mobile terminal for a system shutdown method according to an embodiment of the present invention;

[0032] Figure 2 is a flowchart of a system shutdown method according to an embodiment of the present invention;

[0033] Figure 3 is a schematic diagram of six stages of target system shutdown implementation according to an embodiment of the present invention;

[0034] Figure 4 is a schematic diagram of the implementation order of application shutdown according to an embodiment of the present invention;

[0035] Figure 5 is a schematic diagram of the implementation order of basic software shutdown according to an embodiment of the present invention;

[0036] Figure 6 is a schematic diagram of the implementation order of resource recovery according to an embodiment of the present invention;

[0037] Figure 7 is a schematic diagram of the implementation order of configuration cleaning according to an embodiment of the present invention;

[0038] Figure 8 is a structure block diagram of a system shutdown device according to a specific embodiment of the present invention;

[0039] Figure 9 is a structure block diagram of a system shutdown device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0040] In the following, embodiments of the present invention will be described in detail with reference to the drawings and in combination with the embodiments.

[0041] It should be noted that the terms "first", "second", etc. in the specification, claims and above-mentioned drawings of the present invention are used to distinguish similar objects and do not necessarily describe a specific order or sequence.

[0042] The method embodiments provided in the embodiments of the present application can be executed on a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 is a hardware structure block diagram of a mobile terminal for a system shutdown method according to an embodiment of the present invention. As Figure 1 shown, the mobile terminal may include one or more ( Figure 1 only one is shown in the figure) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Among them, the above-mentioned mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 1 the structure shown is only schematic and does not limit the structure of the above-mentioned mobile terminal. For example, the mobile terminal may further include more or fewer components than Figure 1 shown in the figure, or have a different configuration from Figure 1 shown in the figure.

[0043] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the system shutdown method in the embodiments of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implements the above-mentioned method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely provided with respect to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0044] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal. In one instance, the transmission device 106 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus communicate with the Internet. In one instance, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0045] In this embodiment, a method for shutting down a system is provided. Figure 2 It is a flowchart of the method for shutting down a system according to an embodiment of the present invention. As Figure 2 shown, the process includes the following steps:

[0046] Step S202: Divide the process of shutting down the target system into multiple stages to obtain multiple target stages;

[0047] Step S204: Determine the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target stages to obtain multiple operation and maintenance objects, where the operation and maintenance area is the area to which the configuration applied to implement the functions of the target system belongs;

[0048] Step S206: Determine the dependency relationships between the multiple operation and maintenance objects;

[0049] Step S208: Sort the multiple operation and maintenance objects based on the dependency relationships to obtain an operation and maintenance object control table;

[0050] Step S210: Perform a shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table in the execution order of the multiple target stages.

[0051] In the above embodiment, the target system may be an information system. To achieve centralized and effective management of a large number of information systems that provide business support services externally within an enterprise, various types of management systems are usually constructed, such as many enterprise information systems like the bank core business system: Recording the key configuration information of the bank core business system in the enterprise's configuration management system can realize online management of the key configuration information of all information systems within the enterprise. In the configuration management system, key information such as the software and hardware device types, models, quantities, online production dates, deployment location information, software version numbers, software quantities, and software configuration information such as IP of the bank core business system can be recorded and maintained to achieve itemized management of the key resources of the bank core business system. By building an enterprise-level capacity management system to record and archive the dynamic data of resources such as the bank core business system, management of performance indicators including transaction response duration, transaction concurrency, CPU, memory, disk storage capacity, network bandwidth, etc. can be realized.

[0052] In the above embodiments, an enterprise may also deploy an operation and maintenance tool system such as an operation and maintenance security management system. By means of functions such as account management, identity authentication, single sign-on, resource authorization, access control, and operation auditing of the operation and maintenance security management system, the process of operation and maintenance operations of the information system can be effectively audited. In the operation and maintenance work of systems such as the bank core business system, multiple login entries containing account information, identity authentication, access permission control, etc. can be pre-configured in the operation and maintenance security management system according to operation and maintenance requirements. The operation and maintenance personnel can click on the corresponding login entry as needed to complete the jump login operation to the target information system through the operation and maintenance security management system, so as to perform the maintenance operation of the target information system.

[0053] In the above embodiments, since the composition of the target system is extremely complex and the number of software and hardware components for business processing is huge, the total amount of operation and maintenance objects identified from the operation and maintenance perspective will also be large. The technical fields in operation and maintenance work are divided in detail, and the number of technical field teams participating in operation and maintenance is large. Therefore, the cross-team communication and collaboration level in operation and maintenance work will be even more important. In addition, the transaction path of the information system is complex, covering various business paths such as transaction lines, data lines, and batch processing, and the number of associated channel systems and data interaction systems is large; the number of management systems supporting the information system is also relatively large, resulting in a large number of management and operation and maintenance configuration entries for the bank core business system in information systems such as configuration management, capacity management systems, and operation and maintenance tool systems, and these entries are relatively scattered. Once a shutdown operation is performed on a complex business system, all the above-mentioned operation and maintenance objects need to be considered comprehensively.

[0054] In the above embodiments, in order to comprehensively identify the operation and maintenance objects in all technical fields included in the shutdown process of the target system, the process of implementing the shutdown operation on the target system can be divided into multiple target stages. For the operation and maintenance objects in each target stage, they are classified according to the perspective of the operation and maintenance technical fields (i.e., the above operation and maintenance fields), and the types of the operation and maintenance objects are identified. The specific types included in the system shutdown objects, resource recovery objects, and configuration cleaning objects in each technical field are identified, and the types of the system shutdown objects, resource recovery objects, and configuration cleaning objects in all technical fields can be integrated to generate a set of operation and maintenance objects for implementing shutdown, recovery, and cleaning operations. Among them, system shutdown can be understood as implementing shutdown on relevant transactions in the last stage of the system life cycle, closing relevant data transmissions, shutting down and powering off the software and hardware devices necessary for system operation, and completing the recovery of the information system resources originally used by the system after the software and hardware shutdown operations are completed, and cleaning the relevant configuration entries in the operation and maintenance management system. The operation and maintenance technical fields can include application fields, basic software fields, hardware storage fields, security fields, network fields, batch scheduling fields, and monitoring tool fields, etc. The operation and maintenance objects can include the hardware resources of the target system (hosts, storage, network switches, storage switches, tape libraries, etc., encryption machines, etc.), software resources (transaction processing middleware, message queue middleware, databases, operating systems, monitoring automation software, batch processing software, security software, data transmission software, etc.), corresponding records in the configuration management system such as the specific number of software instances and hardware instances, corresponding records in the capacity management system such as storage device information and space capacity records, corresponding records in the operation and maintenance tool system such as login permission entries, transaction channel systems associated with the target system such as gateways, and systems on the data line with a data interaction and transmission relationship with the target system such as data aggregation and dispersion systems.

[0055] In the above embodiments, the configuration information of the target system in the operation and maintenance management system can also be extracted to obtain the specific quantities of all operation and maintenance objects of the target system, including the quantity information of system shutdown objects, resource recovery objects, and configuration cleaning objects. According to the online transaction line composition, data line composition, and upstream and downstream associated channel system composition of the target system, shutdown dependency identification can be performed on the system shutdown objects in the target system. According to the shutdown dependency identification results, the shutdown operations of the system shutdown can be sorted to obtain an operation and maintenance object control table. Then, based on the type information and quantity information of the resource recovery objects and the type information and quantity information of the configuration cleaning objects, the recovery operation objects and the cleaning operation objects can be supplemented into the operation and maintenance object control table. According to the sorting in the operation and maintenance object control table, shutdown, recovery, and cleaning operations can be sequentially performed on the operation and maintenance objects.

[0056] Through the present invention, first, the process of shutting down the target system can be divided to obtain multiple target stages. For each target stage, the operation and maintenance objects included in different operation and maintenance fields of the target system can be determined, and multiple operation and maintenance objects can be obtained. The dependency relationships between the multiple operation and maintenance objects are determined, and based on the dependency relationships, the multiple operation and maintenance objects are sorted to generate an operation and maintenance object control table. Finally, according to the sorting of the operation and maintenance objects in the operation and maintenance object control table and combined with the execution order of the target stage, the shutdown operation is performed on the operation and maintenance objects. Since the entire shutdown process of the target system can be divided into different target stages, and then the operation and maintenance objects included in each operation and maintenance field in each target stage are determined, that is, all the operation and maintenance objects in the shutdown process of the target system can be comprehensively and effectively identified. Therefore, the technical problem of being unable to safely shut down the information system can be solved, and the effect of safely shutting down the information system can be achieved.

[0057] Optionally, the execution subject of the above steps may be a processor, a terminal, a server, etc., but is not limited thereto.

[0058] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance field of the target system in each target stage includes: when the target stage is the application shutdown stage and the operation and maintenance field is the application field, determining the first object included in the target system; when there is a target service in the target system that depends on the first object, adjusting the object on which the target service depends to another object; after the object on which the target service depends is adjusted to the other object, determining whether the first object meets a first preset condition; when the first object meets the first preset condition, determining the first object as the operation and maintenance object; where the first object includes at least one of the following: a transaction line, a data line, an object implementing a batch processing function, and an object implementing message passing.

[0059] In the above embodiments, during the process of shutting down the target system, the identification of the shutdown operation objects is crucial. Only by accurately identifying all operation and maintenance objects during the system shutdown process can the efficiency of the shutdown implementation be ensured, while preventing the impacts caused by incorrect shutdown operations. Therefore, the operation objects involved in the process of implementing the shutdown of the target system can be classified into three categories from the perspective of the implementation of operation and maintenance work: system shutdown objects, resource recovery objects, and configuration cleanup objects. Among them, the system shutdown objects can be understood as the basic components for the target system to maintain the software and hardware support required for transaction execution to provide external services. Shutting down some of these objects may cause some functions of the target system to be interrupted, or the external transactions to be completely unavailable; the resource recovery objects can be understood as information-based basic resources, which can include various hardware devices, disk storage spaces, network IPs, network bandwidths, etc.; the configuration cleanup objects can be understood as the entry information, monitoring configuration items, change configuration entries, etc. predefined for operation and maintenance management in various management systems of the shut-down target system, such as configuration management systems, capacity management systems, operation and maintenance tool systems, security operation and maintenance management systems, etc.

[0060] In the above embodiments, when the target phase is the application shutdown phase and the operation and maintenance domain is the application domain, the operation and maintenance objects can be identified by combining the operation and maintenance work responsibilities of the application domain mainly responsible for capacity management, application version management, support for important business activities, daily monitoring of transaction running status, and organizing emergency response in various technical domains when system transactions are abnormal. The first object type identified can be seen in Table 1. As shown in Table 1, the first object type can include functions such as the adaptation and transformation function of the target system, online transaction volume (i.e., the above-mentioned transaction line), message passing function, batch processing function, data line (i.e., the above-mentioned data transmission function), etc., and there is no specific identification requirement for the number of instances corresponding to the shutdown object type. Among them, during the application shutdown phase, the shutdown operation of the original application processing function of the target system is mainly completed. If a certain shutdown task (i.e., the above-mentioned target business) has a pre-key dependency (i.e., the target business depends on the first object for cross-system message passing) and cannot be directly implemented, the corresponding adaptation and transformation function can be started in advance to migrate and transform the function of the first object on which the target business in the target system depends to other systems that undertake this function (i.e., adjusted to other objects). It is also possible to block the message passing relationship by canceling the registration of the target system in the enterprise message center system, so as to block the message passing between the target system and the enterprise message center system, and then meet the shutdown requirement that there is no message passing task in the message queue middleware of the target system. When further confirming through the software log of the message queue middleware that there is no message interaction between the target system and the peripheral message center system (i.e., the object on which the target business depends has been adjusted to other objects), it can be determined whether the first object meets the first preset condition, and the first object that meets the first preset condition is determined as the operation and maintenance object.

[0061] Table 1

[0062]

[0063] In an exemplary embodiment, determining whether the first object meets a first preset condition includes: when the first object is a transaction line, determining whether the online transaction volume of the transaction line is zero and whether the duration of the zero online transaction volume is greater than a first preset duration; if the online transaction volume is zero and the duration of the zero online transaction volume is greater than the first preset duration, determining that the first object meets the first preset condition; when the first object is a data line, determining whether there is no data transmission on the data line and whether the duration of no data transmission is greater than a second preset duration; if there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determining that the first object meets the first preset condition; when the first object is an object implementing a batch processing function, determining whether the first object has no batch processing tasks and whether the duration of no batch processing tasks is greater than a third preset duration; if the first object has no batch processing tasks and the duration of no batch processing tasks is greater than the third preset duration, determining that the first object meets the first preset condition; when the first object is an object implementing message passing, determining whether the first object has no message passing tasks and whether the duration of no message passing tasks is greater than a fourth preset duration; if the first object has no message passing tasks and the duration of no message passing tasks is greater than the fourth preset duration, determining that the first object meets the first preset condition.

[0064] In the above embodiment, in the specific discriminative implementation of shutdown that can be implemented, different types of operation and maintenance objects correspond to different determination rules. Continuing to refer to Table 1, when the first object is a transaction line, the daily monitoring results of the transaction operation status in the capacity management system can be combined to determine whether there is currently no online transaction operation in the target system, that is, whether the online transaction volume is zero, and whether the duration of the zero online transaction volume is greater than the first preset duration. Only when both the online transaction volume is zero and the duration of the zero online transaction volume is greater than the first preset duration can it be determined that the first object meets the first preset condition and the subsequent shutdown operation of the transaction line can be started. Among them, the first preset duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0065] In the above embodiments, when the first object is a data line, it is possible to determine whether there is currently no data transmission between the target system and the peripheral system by analyzing the data transmission software log, and whether the duration of no data transmission is greater than a second predetermined duration. Only when both conditions of no data transmission and the duration of no data transmission being greater than the second predetermined duration are met can it be determined that the first object meets the first preset condition, and only then can the subsequent operation of shutting down the data line be initiated. Among them, the second predetermined duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0066] In the above embodiments, when the first object is an object that implements a batch processing function, it is possible to determine whether the batch processing of the target system has stopped, that is, whether there are no batch processing tasks, and whether the duration of no batch processing tasks is greater than a third predetermined duration by analyzing the batch processing software log and the running status of the batch processing software. Only when both conditions of no batch processing tasks and the duration of no batch processing tasks being greater than the third predetermined duration are met can it be determined that the first object meets the first preset condition, and only then can the subsequent operation of shutting down the message queue middleware software be initiated. Among them, the third predetermined duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0067] In the above embodiments, when the first object is an object that implements a message passing function, it is possible to determine whether there are no message passing tasks between the target system and the peripheral system, and whether the duration of no message passing tasks is greater than a fourth predetermined duration. Only when both conditions of no message passing tasks and the duration of no message passing tasks being greater than the fourth predetermined duration are met can it be determined that the first object meets the first preset condition, and only then can the subsequent operation of shutting down the batch processing software be initiated. Among them, the fourth predetermined duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0068] In an exemplary embodiment, in each of the target stages, the operation and maintenance objects included in each operation and maintenance area of the target system include: when the target stage is the basic software shutdown stage and the operation and maintenance area is the software area, determining the second object included in the target system; determining whether the second object meets the second preset condition; when the second object meets the second preset condition, determining the second object as the operation and maintenance object; where the second object includes at least one of the following: transaction processing middleware software, message queue middleware software, database software, data transmission software, operating system software.

[0069] In the above embodiments, when the target stage is the basic software shutdown stage and the operation and maintenance field is the software field, the operation and maintenance objects can be identified in combination with the information system operation and maintenance work responsibilities of the target system. The second object types identified can be seen in Table 2. As shown in Table 2, the second object types can include transaction processing middleware software, message queue middleware software, database software, data transmission software, and operating system software, etc. The configuration quantity of each type can be obtained from the configuration management system. Among them, the basic software shutdown stage can mainly complete the operation and maintenance management work of the basic software. On the trading line, after receiving the gateway cluster trading request, the transaction processing middleware software can forward the request to the database software of the target system, and the database software can perform operations such as querying or updating account or customer information. After the database completes the request, it can return the result to the transaction processing middleware software, and then the transaction processing middleware software can feedback it to the gateway cluster. On the data line, the data transmission software deployed on the target system can realize data transmission and interaction with the peripheral system (such as the data aggregation and dispersion system). The message queue middleware software can realize cross-platform message passing between the target system and the peripheral message center system, and can meet the cross-system asynchronous information synchronization requirements. And the operating system software, monitoring automation software, security software, etc. as the basic software of the target system can provide underlying basic technical support for the upper-layer transaction processing middleware software, message queue middleware software, database software, batch processing software, etc., to ensure that the processing capabilities required for various transaction processes can be realized. When it is determined that the second object meets the second preset condition, the second object that meets the second preset condition can be determined as the operation and maintenance object.

[0070] Table 2

[0071]

[0072] In an exemplary embodiment, determining whether the second object meets the second preset condition includes: when the second object is transaction processing middleware software, determining the transaction line corresponding to the transaction processing middleware software included in the application domain, and when the online transaction volume of the transaction line is zero and the duration of the zero online transaction volume is greater than the first preset duration, determining that the second object meets the second preset condition; when the second object is message queue middleware software, determining the object for implementing message passing corresponding to the message queue middleware software included in the application domain, and when there is no message passing task for the object for implementing message passing and the duration of no message passing task is greater than the fourth preset duration, determining that the second object meets the second preset condition; when the second object is database software, determining the shutdown state of the transaction processing middleware software, and when the shutdown state indicates that the transaction processing middleware software has been successfully shut down and the successful shutdown lasts for the fifth preset duration, determining that the second object meets the second preset condition; when the second object is data transmission software, determining the data line corresponding to the data transmission software included in the application domain, and when there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determining that the second object meets the second preset condition; when the second object is operating system software, determining the basic software included in the target system, and when all the basic software has been shut down and the shutdown lasts for the sixth preset duration, determining that the second object meets the second preset condition, where the basic software includes the transaction processing middleware software, the message queue middleware software, the database software, and the data transmission software.

[0073] In the above embodiment, continuing to refer to Table 2, when the second object is transaction processing middleware software, it can be determined whether the online transaction volume corresponding to the transaction processing middleware software in the application domain is zero, and whether the duration of the zero online transaction volume is greater than the first preset duration. Only when both conditions of zero online transaction volume and the duration of zero online transaction volume being greater than the first preset duration are met can it be determined that the second object meets the second preset condition, and only then can the transaction processing middleware software be shut down to achieve the shutdown of the transaction line of the target system, and then the database software shutdown can be initiated.

[0074] In the above embodiments, when the second object is message queue middleware software, it is possible to analyze whether the object corresponding to the message queue middleware software in the application field for implementing message passing is zero, and whether the duration during which the object for message passing has no message passing task is greater than a fourth predetermined duration. Only when both conditions of having no message passing task and the duration of having no message passing task being greater than the fourth predetermined duration are satisfied can it be determined that the second object meets the second preset condition, and only then can the message queue middleware software be shut down to implement the shutdown of the message passing function of the target system.

[0075] In the above embodiments, when the second object is database software, it is possible to determine whether the transaction processing middleware software has been successfully shut down, and whether the duration of the successfully shut down transaction processing middleware software is greater than a fifth predetermined duration. Only when both conditions of the transaction processing middleware software having been successfully shut down and the duration of the successfully shut down being greater than the fifth predetermined duration are satisfied can it be determined that the second object meets the second preset condition, and only then can the database software be shut down, and then the monitoring automation software shutdown can be initiated. Among them, the fifth predetermined duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0076] In the above embodiments, when the second object is data transmission software, it is possible to analyze whether there is data transmission on the data line in the application field, and whether the duration during which the data line has no data transmission is greater than a second predetermined duration. Only when both conditions of the data line having no data transmission and the duration of the data line having no data transmission being greater than the second predetermined duration are satisfied can it be determined that the second object meets the second preset condition, and only then can the data transmission software be shut down.

[0077] In the above embodiments, when the second object is operating system software, it is possible to determine whether all the key basic software included in the target system has been shut down, and whether the duration of the shutdown of all the key basic software is greater than a second predetermined duration. Only when both conditions of all the key basic software being shut down and the duration of the shutdown being greater than the second predetermined duration are satisfied can it be determined that the second object meets the second preset condition, and only then can the operating system software be shut down, and then the hardware shutdown and power-off operation can be initiated. Among them, the key basic software may include transaction processing middleware software, message queue middleware software, database software, operating system software, monitoring automation software, batch processing software, security software, data transmission software, etc.

[0078] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the equipment shutdown phase and the operation and maintenance area is the hardware storage area, determining a third object included in the target system; determining whether the third object meets a third preset condition; when the third object meets the third preset condition, determining the third object as the operation and maintenance object; wherein, the third object includes at least one of the following: physical host, storage switch, disk device, tape library device, power module, computer room module.

[0079] In the above embodiment, when the target phase is the equipment shutdown phase and the operation and maintenance area is the hardware storage area, the operation and maintenance objects can be identified in combination with the job responsibilities of hardware device management, computer room management, storage management, etc. in the information system operation and maintenance work of the target system. The types of the identified third objects can be seen in Table 3. As shown in Table 3, the types of the third objects can include physical hosts, storage switches, disk devices, tape library devices, power modules, computer room modules, etc., and the configured quantity of each type can be obtained from the configuration management system. Among them, during the hardware storage shutdown phase, hardware device management, computer room management, storage management, etc. can be mainly completed. When it is determined that the third object meets the third preset condition, the third object that meets the third preset condition can be determined as the operation and maintenance object.

[0080] Table 3

[0081]

[0082]

[0083] In an exemplary embodiment, determining whether the third object meets the third preset condition includes: when the third object is a physical host, determining the operating system software running in the physical host; when the operating system software has been shut down and the shutdown duration lasts for a seventh preset duration, determining that the third object meets the third preset condition; when the third object is a storage switch, determining that the operating system of the target system has been shut down and the shutdown duration lasts for an eighth preset duration, determining that the third object meets the third preset condition; when the third object is a disk device, determining that the operating system of the target system has been shut down and the shutdown duration lasts for a ninth preset duration, determining that the third object meets the third preset condition; when the third object is a tape library device, determining that the operating system of the target system has been shut down and the shutdown duration lasts for a tenth preset duration, determining that the third object meets the third preset condition; when the third object is a power module, determining that the hardware devices included in the target system have been shut down and the shutdown duration lasts for an eleventh preset duration, determining that the third object meets the third preset condition, where the hardware devices include; when the third object is a computer room module, determining that the hardware devices included in the target system have completed equipment removal from the rack, determining that the third object meets the third preset condition.

[0084] In the above embodiment, continue to refer to Table 3. When the third object is a physical host, it can be determined whether the operating system software running in the physical host has been successfully shut down, and whether the duration of the shut-down operating system software is greater than the seventh preset duration. Only when both conditions are met, that is, the operating system software has been successfully shut down and the duration of the successful shutdown is greater than the seventh preset duration, can it be determined that the third object meets the third preset condition, and the shutdown operation can be implemented through the console, thereby initiating the power-off and rack-removal work of the device. Among them, the seventh preset duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0085] In the above embodiment, when the third object is a storage switch, it can be determined whether the operating system software of the storage switch in the target system has been successfully shut down, and whether the duration of the shut-down operating system software is greater than the eighth preset duration. Only when both conditions are met, that is, the operating system software has been successfully shut down and the duration of the successful shutdown is greater than the eighth preset duration, can it be determined that the third object meets the third preset condition, and the shutdown operation can be implemented through the console, thereby initiating the power-off and rack-removal work of the device. Among them, the eighth preset duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0086] In the above embodiments, when the third object is a disk device, it is possible to determine whether the operating system software of the disk device in the target system has been successfully shut down, and whether the duration of the shut-down operating system software is greater than the ninth preset duration. Only when both conditions are met, i.e., the operating system software has been successfully shut down and the duration of the successful shut-down is greater than the ninth preset duration, can it be determined that the third object meets the third preset condition, and only then can the shut-down operation be implemented through the console, thereby initiating the power-off and removal of the device. The ninth preset duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0087] In the above embodiments, when the third object is a tape library device, it is possible to determine whether the operating system software of the tape library device in the target system has been successfully shut down, and whether the duration of the shut-down operating system software is greater than the tenth preset duration. Only when both conditions are met, i.e., the operating system software has been successfully shut down and the duration of the successful shut-down is greater than the tenth preset duration, can it be determined that the third object meets the third preset condition, and only then can the shut-down operation be implemented through the console, thereby initiating the power-off and removal of the device. The tenth preset duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0088] In the above embodiments, when the third object is a power module, it is possible to determine whether the hardware device of the power module in the target system has been successfully shut down, and whether the duration of the shut-down hardware device is greater than the eleventh preset duration. Only when both conditions are met, i.e., the operating system software has been successfully shut down and the duration of the successful shut-down is greater than the eleventh preset duration, can it be determined that the third object meets the third preset condition, and only then can the power connector of the hardware device be disconnected, thereby initiating the evacuation of the computer room module. The eleventh preset duration can be 1 minute, 5 minutes, etc., but is not limited thereto.

[0089] In the above embodiments, when the third object is a computer room module, it is possible to determine whether all the hardware devices of the computer room module in the target system have been removed from the device. Only after all the hardware devices have been removed from the device can it be determined that the third object meets the third preset condition, and only then can the removed devices be cleaned in the computer room module.

[0090] In an exemplary embodiment, in each of the target stages, the operation and maintenance objects included in each operation and maintenance area of the target system are determined as follows: in the case where the target stage is the device shut-down stage and the operation and maintenance area is the security area, the fourth object included in the target system is determined; it is determined whether the fourth object meets the fourth preset condition; in the case where the fourth object meets the fourth preset condition, the fourth object is determined as the operation and maintenance object; wherein, the fourth object includes at least one of the following: an encryption software client, an encryption machine.

[0091] In the above embodiments, when the target stage is the equipment shutdown stage and the operation and maintenance field is the security field, the operation and maintenance object can be identified by combining the responsibilities of security software management, key management, intrusion detection management, etc. The fourth object type identified can be seen in Table 4. As shown in Table 4, the fourth object type can include encryption software clients and encryption machines, and the configuration quantity of each type can be obtained from the configuration management system. Among them, in the security field shutdown stage, the management of various encryption software and security software used by the target system, key management, intrusion detection management, etc. can be mainly completed. When it is determined that the fourth object meets the fourth preset condition, the fourth object that meets the fourth preset condition can be determined as the operation and maintenance object.

[0092] Table 4

[0093]

[0094]

[0095] In an exemplary embodiment, determining whether the fourth object meets the fourth preset condition includes: when the fourth object is an encryption software client, determining the transaction line corresponding to the encryption software client included in the application field. When the online transaction volume of the transaction line is zero and the continuous duration of the zero online transaction volume is greater than the first preset duration, it is determined that the fourth object meets the fourth preset condition; when the fourth object is an encryption machine, determining the data line for data transmission corresponding to the encryption machine included in the target system. When there is no data transmission on the data line and the continuous duration of no data transmission is greater than the second preset duration, it is determined that the fourth object meets the fourth preset condition.

[0096] In the above embodiments, continuing to refer to Table 4, when the fourth object is an encryption software client, the transaction line corresponding to the encryption software client included in the application field can be determined, that is, whether the online transaction volume in the application field is zero, and whether the continuous duration of the zero online transaction volume in the application field is greater than the first preset duration. Only when both the online transaction volume is zero and the continuous duration of the zero online transaction volume is greater than the first preset duration can it be determined that the fourth object meets the fourth preset condition, and the client software can be shut down, and then the encryption machine hardware device can be shut down.

[0097] In the above embodiments, when the fourth object is an encryption machine, it can be determined whether there is no data transmission on the data line for data transmission corresponding to the encryption machine included in the target system, and whether the continuous duration of no data transmission is greater than the second preset duration. Only when both there is no data transmission and the continuous duration of no data transmission is greater than the second preset duration can it be determined that the fourth object meets the fourth preset condition, and the shutdown operation can be implemented through the console, and then the equipment power-off and removal work can be started.

[0098] In an exemplary embodiment, when determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases, it includes: when the target phase is the equipment shutdown phase and the operation and maintenance area is the network area, determining the network switches included in the target system; when there is no network traffic in the network of the network switch and the physical hosts included in the target system have been shut down, determining the network switch as the operation and maintenance object.

[0099] In the above embodiment, when the target phase is the equipment shutdown phase and the operation and maintenance area is the network area, the operation and maintenance objects can be identified by combining the operation and maintenance responsibilities such as network capacity management and network operation monitoring in the network infrastructure management of the network area. The types of identified operation and maintenance objects can be seen in Table 5. As shown in Table 5, the types of operation and maintenance objects can include network switches, and the configured quantity can be obtained from the configuration management system. Among them, in the shutdown phase of the network area, the management of the network infrastructure can be mainly completed, and the network capacity management and network operation monitoring of the target system can be completed.

[0100] In the above embodiment, it can be determined whether there is no network traffic in the network switches of the target system and whether the physical hosts have been shut down. Only when both conditions of no network traffic in the network of the network switch and the physical hosts having been shut down are met can the network switch be determined as the operation and maintenance object, and then the network switch can be shut down, and further the power-off and removal of the network switch hardware can be started.

[0101] Table 5

[0102]

[0103]

[0104] In an exemplary embodiment, when determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases, it includes: when the target phase is the basic software shutdown phase and the operation and maintenance area is the batch scheduling area, determining the batch processing software included in the target system; when there is no batch processing task in the batch processing software and the duration without batch processing tasks is greater than the third predetermined duration, determining the batch processing software as the operation and maintenance object.

[0105] In the above embodiments, when the target phase is the equipment shutdown phase and the operation and maintenance area is the batch scheduling area, the operation and maintenance objects can be identified in combination with the batch scheduling area responsible for completing centralized batch processing tasks such as internal account posting within the non-business peak window of the bank core business system during the day. The types of identified operation and maintenance objects can be seen in Table 6. As shown in Table 6, the types of operation and maintenance objects can include batch processing software, and the configured quantity can be obtained from the configuration management system. Among them, during the shutdown phase of the batch scheduling area, it can mainly complete centralized batch processing tasks such as internal account posting within the non-business peak window of the target system during the day, and promote the use of batch scheduling tools to other application systems.

[0106] In the above embodiments, it can be determined whether there is no batch processing task for the batch processing software in the target system, and whether the duration without batch processing tasks is greater than the third predetermined duration. Only when both conditions are met, that is, the batch processing software has no batch processing tasks and the duration without batch processing tasks is greater than the third predetermined duration, can the batch processing software be determined as an operation and maintenance object, and the client of the batch processing software can be shut down, and then the shutdown operation of the basic software can be started.

[0107] Table 6

[0108]

[0109] In an exemplary embodiment, in each target phase, the operation and maintenance objects included in each operation and maintenance area of the target system are determined as follows: when the target phase is the basic software shutdown phase and the operation and maintenance area is the monitoring tool area, the monitoring automation software included in the target system is determined. When the transaction processing middleware software and the database software in the target system have both been shut down and the shutdown duration has lasted for the twelfth predetermined duration, the monitoring automation software is determined as the operation and maintenance object.

[0110] In the above embodiments, when the target phase is the equipment shutdown phase and the operation and maintenance area is the monitoring tool area, the operation and maintenance objects can be identified in combination with the operation and maintenance responsibilities of the monitoring automation software in the target system. The types of identified operation and maintenance objects can be seen in Table 7. As shown in Table 7, the types of operation and maintenance objects can include monitoring automation software, and the configured quantity can be obtained from the configuration management system. Among them, during the shutdown phase of the monitoring tool area, it can mainly complete the research and development and operation and maintenance of monitoring tools, including basic monitoring, transaction monitoring, operation and maintenance tools, etc., and is also responsible for the operation and maintenance management of the monitoring automation software of the core business system.

[0111] In the above embodiments, it is possible to determine whether the transaction processing middleware software and the database software in the monitoring automation software in the target system are both shut down, and the shutdown duration of both being shut down is greater than the twelfth predetermined duration. Only when both the transaction processing middleware software and the database software are shut down and the shutdown duration of both being shut down is greater than the twelfth predetermined duration can the monitoring automation software be determined as an operation and maintenance object, and the monitoring automation software can be shut down, and then the operating system software can be shut down.

[0112] Table 7

[0113]

[0114] In the foregoing embodiments, the type of the operation and maintenance object identified is the type during the shutdown operation process of the target system. Combining the development of the operation and maintenance work in each technical field, the specific identification process of each type of shutdown object can be achieved through centralized discussion, expert analysis, etc. The specific quantity information of different types of operation and maintenance shutdown objects can be extracted from the configuration management system, that is, the identification of the type of the operation and maintenance object for the shutdown operation and the acquisition of the specific quantity information are realized.

[0115] In an exemplary embodiment, in each of the target stages, the operation and maintenance objects included in each operation and maintenance area of the target system include: when the target stage is the resource recovery stage and the operation and maintenance area is the hardware storage area, at least one of the following included in the target system is determined as the operation and maintenance object: physical machine, disk space, storage switch, disk device, tape library device, power module, computer room module.

[0116] In the above embodiments, after the shutdown of various shutdown objects in the target system, the software and hardware infrastructure resources originally occupied during the operation of the target system can be released, and various reusable resources can be recycled and reused subsequently. The identification of the operation and maintenance object corresponding to the resource recovery operation is implemented using the same implementation method as the identification of the operation and maintenance object corresponding to the system shutdown operation, that is, in each technical field, the type of the operation and maintenance object for the resource recovery operation is identified according to the operation and maintenance work, and the identification of the type of each operation and maintenance object for the recovery operation and the acquisition of the specific quantity information are realized.

[0117] In the above embodiments, when the target stage is the resource recovery stage and the operation and maintenance area is the hardware storage area, the types of the operation and maintenance objects corresponding to the identified resource recovery operations can be seen in Table 8. As shown in Table 8, the types of the operation and maintenance objects can include physical machines, disk space, storage switches, disk devices, tape library devices, power modules, and computer room modules, and the configured quantities can be obtained from the configuration management system.

[0118] In the above embodiments, when the operation and maintenance object type is a physical machine, the physical machines that have been taken off the shelves can be included in the resource pool for re - shelving, or the physical machines that have not been taken off the shelves can be included in the resource pool for re - allocation. After that, re - shelving or re - allocation can be carried out in combination with new requirements.

[0119] In the above embodiments, when the operation and maintenance object is disk space, the disk space can be recycled first. After re - formatting, the disk space can be added to the resource pool for re - allocation, and then re - allocation can be carried out in combination with new requirements.

[0120] In the above embodiments, when the operation and maintenance object is a storage switch, the storage switches that have been taken off the shelves can be included in the resource pool for re - shelving, or the storage switches that have not been taken off the shelves can be included in the resource pool for re - allocation. After that, re - shelving or re - allocation can be carried out in combination with new requirements.

[0121] In the above embodiments, when the operation and maintenance object is a disk device, the disk devices that have been taken off the shelves can be included in the resource pool for re - shelving, or the disk devices that have not been taken off the shelves can be included in the resource pool for re - allocation. After that, re - shelving or re - allocation can be carried out in combination with new requirements.

[0122] In the above embodiments, when the operation and maintenance object is a tape library device, the tape library devices that have been taken off the shelves can be included in the resource pool for re - shelving, or the tape library devices that have not been taken off the shelves can be included in the resource pool for re - allocation. After that, re - shelving or re - allocation can be carried out in combination with new requirements.

[0123] In the above embodiments, when the operation and maintenance object is a power module, the power module can be included in the resource pool for re - allocation, and then re - allocation can be carried out in combination with new requirements.

[0124] In the above embodiments, when the operation and maintenance object is a computer room module, the computer room can be cleaned first, and then the computer room module can be added to the resource pool for re - allocation. After that, re - allocation can be carried out in combination with new requirements.

[0125] Table 8

[0126]

[0127]

[0128] In an exemplary embodiment, in each of the target stages, the operation and maintenance objects included in each operation and maintenance area of the target system include: when the target stage is the resource recovery stage and the operation and maintenance area is the network operation and maintenance area, at least one of the following included in the target system is determined as the operation and maintenance object: IP address, network bandwidth, network switch.

[0129] In the above embodiments, when the target phase is the resource recovery phase and the operation and maintenance area is the network operation and maintenance area, the operation and maintenance object types corresponding to the identified resource recovery operations can be seen in Table 9. As shown in Table 9, the operation and maintenance object types can include IP addresses, network bandwidth, and network switches, and the configured quantity can be obtained from the configuration management system.

[0130] In the above embodiments, when the operation and maintenance object type is an IP address, the IP address can be included in the IP address reallocatable resource pool, and then it can be reallocated in combination with new requirements.

[0131] In the above embodiments, when the operation and maintenance object type is network bandwidth, the preset network bandwidth quota can be recovered, and then the bandwidth quota can be readjusted in combination with new requirements.

[0132] In the above embodiments, when the operation and maintenance object type is a network switch, the network switch can be included in the network switch reallocatable resource pool, and then it can be reallocated in combination with new requirements.

[0133] Table 9

[0134]

[0135] In an exemplary embodiment, in each of the target phases, the operation and maintenance objects included in each operation and maintenance area of the target system are as follows: when the target phase is the resource recovery phase and the operation and maintenance area is the security area, at least one of the following included in the target system is determined as the operation and maintenance object: security certificate, encryption machine.

[0136] In the above embodiments, when the target phase is the resource recovery phase and the operation and maintenance area is the security operation and maintenance area, the operation and maintenance object types corresponding to the identified resource recovery operations can be seen in Table 10. As shown in Table 10, the operation and maintenance object types can include security certificates and encryption machines, and the configured quantity can be obtained from the configuration management system.

[0137] In the above embodiments, when the operation and maintenance object type is a security certificate, the security certificate can be included in the reallocatable resource pool, and then it can be reallocated in combination with new requirements.

[0138] In the above embodiments, when the operation and maintenance object type is an encryption machine, the encryption machine can be included in the reallocatable resource pool, and then it can be reallocated in combination with new requirements.

[0139] Table 10

[0140]

[0141] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the configuration cleanup phase and the operation and maintenance area is the application area, determining at least one of the following of the target system as the operation and maintenance object: the configuration entries of the system configuration of the target system, the automated change process of the target system, and the configuration entries of the capacity configuration of the target system.

[0142] In the above embodiment, various configuration entry information regarding the shutdown of the information system can be stored in management systems such as configuration management, capacity management, and operation and maintenance tools. After completing the shutdown of the information system and resource recovery, the identification of the operation and maintenance object types of the configuration cleanup category can be implemented, and all the configuration information of each cleanup category operation and maintenance object can be cleared from the management system, thereby ensuring the comprehensiveness of the implementation of the target system shutdown work.

[0143] In the above embodiment, when the target phase is the configuration cleanup phase and the operation and maintenance area is the application area, the operation and maintenance objects can be identified in combination with the current usage status of the operation and maintenance management system during the operation and maintenance process. The operation and maintenance object types corresponding to the configuration cleanup category can be seen in Table 11. As shown in Table 11, the operation and maintenance object types can include the configuration entries in the shutdown system directory of the configuration management system in the target system, the automated change process defined in the shutdown system directory of the process management system, and the configuration entries in the shutdown system directory of the capacity management system. The configuration quantity can be obtained from the corresponding configuration management system, process management system, and capacity management system.

[0144] In the above embodiment, when the operation and maintenance object type is the configuration entries in the shutdown system directory of the configuration management system, a directory-level cleanup operation can be implemented in the configuration management system.

[0145] In the above embodiment, when the operation and maintenance object type is the automated change process defined in the shutdown system directory of the process management system, a directory-level cleanup operation can be implemented in the process management system.

[0146] In the above embodiment, when the operation and maintenance object type is the configuration entries in the shutdown system directory of the capacity management system, a directory-level cleanup operation can be implemented in the capacity management system.

[0147] Table 11

[0148]

[0149] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the configuration cleanup phase and the operation and maintenance area is the security area, determining at least one of the following of the target system as the operation and maintenance object: the operation and maintenance login entry of the target system, the system operation and maintenance high-privilege authorization medium of the target system.

[0150] In the above embodiment, when the target phase is the configuration cleanup phase and the operation and maintenance area is the security area, the operation and maintenance objects can be identified in combination with the usage status of the operation and maintenance management system during the operation and maintenance process. The identified operation and maintenance object types corresponding to the configuration cleanup category can be seen in Table 12. As shown in Table 12, the operation and maintenance object types can include the operation and maintenance login entry under the shutdown system directory in the operation and maintenance security management system and the system operation and maintenance high-privilege authorization medium, and the configuration quantity can be obtained from the corresponding operation and maintenance security management system.

[0151] In the above embodiment, when the operation and maintenance object type is the operation and maintenance login entry under the shutdown system directory in the operation and maintenance security management system, a directory-level cleanup operation can be implemented in the operation and maintenance security management system.

[0152] In the above embodiment, when the operation and maintenance object type is the system operation and maintenance high-privilege authorization medium, a directory-level cleanup operation can be implemented in the operation and maintenance security management system, and the authorization medium can be physically destroyed.

[0153] Table 12

[0154]

[0155] In an exemplary embodiment, determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: when the target phase is the configuration cleanup phase and the operation and maintenance area is the monitoring tool area, determining the monitoring strategy of the target system as the operation and maintenance object.

[0156] In the above embodiment, when the target phase is the configuration cleanup phase and the operation and maintenance area is the monitoring tool area, the operation and maintenance objects can be identified in combination with the usage status of the operation and maintenance management system during the operation and maintenance process. The identified operation and maintenance object types corresponding to the configuration cleanup category can be seen in Table 13. As shown in Table 13, the operation and maintenance object types can include the monitoring strategy under the shutdown system directory in the monitoring system, and the configuration quantity can be obtained from the corresponding monitoring system.

[0157] In the above embodiment, when the operation and maintenance object type is the monitoring strategy under the shutdown system directory in the monitoring system, a monitoring strategy cleanup and offline operation can be implemented in the monitoring system.

[0158] In the foregoing embodiments, it is possible to identify the types of system shutdown objects, resource recovery objects, and configuration cleanup objects during the shutdown process of the target system, and it is also possible to extract the detailed quantities of each operation and maintenance object from the management system, so as to achieve the full-scale identification of the shutdown operation objects and ensure the integrity of the shutdown operation objects.

[0159] Table 13

[0160]

[0161] In an exemplary embodiment, sorting the multiple operation and maintenance objects based on the dependency relationship to obtain an operation and maintenance object control table includes: determining the stage operation and maintenance objects belonging to each target stage included in the multiple operation and maintenance objects; performing the following operations for the stage operation and maintenance objects of each target stage to obtain a sub-control table for the target stage: determining the operation type of the stage operation and maintenance object; determining the implementation sequence number of the stage operation and maintenance object based on the dependency relationship; determining the quantity of the stage operation and maintenance object; determining the name of the operation and maintenance team for maintaining the stage operation and maintenance object; determining the operation effect of shutting down the stage operation and maintenance object; determining the task interval, where the task interval is used to indicate that after the shutdown operation is performed on the stage operation and maintenance object, the next object of the stage operation and maintenance object is shut down after the task interval, generating the sub-control table based on the stage operation and maintenance object, the operation type, the implementation sequence number, the quantity, the name of the operation and maintenance team, the operation effect, and the task interval; sorting the multiple sub-control tables according to the execution order of the multiple target stages to obtain the operation and maintenance object control table.

[0162] In the above embodiments, according to the target stages divided by the target system and the identification of the types and quantities of stage operation and maintenance objects in each stage, an operation and maintenance object control table can be constructed to control the shutdown of the target system. The sub-control tables for each target stage included in the operation and maintenance object control table can be seen in Table 14. As shown in Table 14, the sub-control table may include the name of the stage operation and maintenance object type, the operation type of the stage operation and maintenance object, the implementation serial number of the stage operation and maintenance object, the quantity of the stage operation and maintenance object, the name of the operation and maintenance team for the stage operation and maintenance object, the operation effect of the stage operation and maintenance object, and the start time interval of the subsequent task (i.e., the task interval). Among them, the name of the stage operation and maintenance object type can be understood as the name description of the operation and maintenance objects involved in the target system, such as transaction processing middleware software, operating system software, database software, etc.; the operation type of the stage operation and maintenance object can be understood as the specific type of operation, which may include shutdown, recovery, and cleaning; the implementation serial number of the stage operation and maintenance object can be understood as the implementation sequence number determined according to the dependency relationship of the operation and maintenance objects. The corresponding specific operations of the operation type are implemented on all the operation and maintenance objects in the operation and maintenance object control table in ascending order of the sequence number. The implementation serial number of the operation and maintenance object can be encoded with 4 digits. For example, yxxx, where y = 1 can represent the implementation object of the shutdown operation, y = 2 can represent the implementation object of the recovery operation, and y = 3 can represent the implementation object of the cleaning operation; the quantity of the stage operation and maintenance object can be understood as the specific quantity corresponding to the operation and maintenance object. Only when all the instances of the quantity of this operation and maintenance object are completed can it be determined that the operation of this operation and maintenance object is completed; the name of the operation and maintenance team for the stage operation and maintenance object can be understood as the name of the operation and maintenance team corresponding to the technical field division of the operation and maintenance object. The technical operation and maintenance team implements operation tasks such as shutdown, recovery, and cleaning on the corresponding operation and maintenance objects; the operation effect of the stage operation and maintenance object can be understood as the expected result after the operation on the operation and maintenance object is completed. For example, after all the transaction processing middleware software is shut down, the shutdown of the transaction line can be achieved; the start time interval of the subsequent task can be understood as the minimum time interval for the shutdown operation type operation and maintenance object to start the shutdown operation after the operation is completed. The setting of this time interval can verify the conclusion that there is no impact on the shutdown of this operation and maintenance object to the greatest extent and reduce any adverse impact on business continuity caused by the shutdown operation of this operation and maintenance object.

[0163] In the above embodiments, for the specific embodiment of the operation and maintenance object control table adopted to shut down the target system, refer to Table 15. As shown in Table 15, multiple sub-control tables can be sorted according to the execution order of different target stages. For example, first perform the shutdown operation, then perform the recovery operation, and finally perform the cleaning operation. According to the sorting of the operation and maintenance object control table, under the constraint of meeting the time interval between the start times of subsequent tasks, the technical operation and maintenance team can sequentially perform the operations required for the shutdown implementation of the target system on the operation and maintenance object types in the operation and maintenance object control table in ascending order of the implementation serial numbers according to the operation and maintenance object types. After all the operations on all the operation and maintenance object types and all the operation and maintenance objects in the control table are completed, it is confirmed that the shutdown work of the target system is completed.

[0164] Table 14

[0165] Table 15

[0166]

[0167]

[0168]

[0169]

[0170]

[0171] In an exemplary embodiment, the process of shutting down the target system is divided into multiple stages, and multiple target stages are obtained, including: dividing the process of shutting down the target system into an application shutdown stage, a basic software shutdown stage, a device shutdown stage, a device power-off stage, a resource recovery stage, and a configuration cleaning stage; and determining the application shutdown stage, the basic software shutdown stage, the device shutdown stage, the device power-off stage, the resource recovery stage, and the configuration cleaning stage as the target stages.

[0172] In the above embodiments, the shutdown implementation process of the target system can be divided into six target stages. Figure 3 It is a schematic diagram of six stages of the shutdown implementation of the target system according to an embodiment of the present invention. As Figure 3As shown, the target phases may include the application shutdown phase, the basic software shutdown phase, the equipment shutdown phase, the equipment power-off phase, the resource recovery phase, and the configuration cleanup phase. During different target phases, control operations during the shutdown process can be sequentially performed on the operation and maintenance operation objects at time intervals. The control operation of the next phase starts only after the previous control operation is completed and the time interval is satisfied, so as to ensure that the conclusion of no business impact during different shutdown phases is fully verified. Among them, due to the complex composition of transactions in the target system and the periodic characteristics of some transactions, which are not executable in real time, setting the same operation time interval uniformly may not be able to fully verify the business continuity operation and maintenance requirements of no business impact during the shutdown operation process. Therefore, the time interval settings for verifying no business impact in each shutdown phase can be different.

[0173] In the above embodiment, the application shutdown phase can mainly complete the shutdown operation of the original application processing function of the target system. Figure 4 It is a schematic diagram of the application shutdown implementation sequence according to an embodiment of the present invention. As Figure 4 shown, the application shutdown phase may include business functions such as online transaction line shutdown, data line shutdown, message transmission function shutdown, and system batch processing function shutdown. Among them, if there is a shutdown task that cannot be directly implemented due to pre-key dependencies, the corresponding adaptation transformation work can be started in advance, and the functions of the system to be shut down can be migrated and transformed to other systems that undertake the functions through the adaptation transformation process. To ensure the verification goal of no impact after each step of implementation, multiple specific steps need to meet the time interval of each step before they can start.

[0174] In the above embodiment, after the time interval for the application shutdown is satisfied, the shutdown work of the target system can enter the basic software shutdown phase. Figure 5 It is a schematic diagram of the basic software shutdown implementation sequence according to an embodiment of the present invention. As Figure 5 shown, the basic software shutdown phase can mainly perform the shutdown operations of software such as database software, security software, monitoring tool software, and operating system software. Among them, in order to avoid the impact that may be brought by directly implementing the database software shutdown, all tables in the database can be adjusted from the read-write mode to the read-only mode in advance. After continuously observing that there is no update requirement for the database tables, the database software can be shut down, and the risk of database shutdown can be minimized.

[0175] In the above embodiments, after the shutdown of the target system and the underlying software, the target system can release the hardware devices originally required for operation. The shutdown of the target system can enter two stages: device shutdown and device power-off. In the device shutdown stage, the operation and maintenance personnel can sequentially perform shutdown operations on all devices through the hardware console. In the device power-off stage, the operation and maintenance personnel can power off by unplugging the power modules corresponding to all devices. Similarly to other shutdown stages, the device shutdown and device power-off operations need to meet the time interval after the shutdown of the underlying software before they can start, so as to avoid the need for emergency startup of the underlying software in the scenario of mis-shutdown operations caused by incomplete recognition of the business function support of the target system.

[0176] In the above embodiments, to ensure the integrity of the implementation of the information system shutdown work, the two work stages of resource recovery and configuration cleaning after the shutdown operation can also be incorporated into the overall implementation process of the shutdown. Since the resource recovery operation and the configuration cleaning operation, like the shutdown operation, require a full-scale identification of the operation and maintenance objects in advance, the implementation methods for identifying the operation and maintenance object types and determining the specific quantities can also be applied to the two shutdown stages of resource recovery and configuration cleaning.

[0177] In the above embodiments, the implementation order of the resource recovery stage for the operation and maintenance objects can be referred to Figure 6 , Figure 6 According to the schematic diagram of the resource recovery implementation order of the embodiments of the present invention, as Figure 6 shown, in the resource recovery stage, recovery operations can be performed on the hardware device resources, security resources, network resources, computer room module resources, etc. that are no longer used in the target system. After the recovered resources are re-initialized, they are added to the reallocable resource pool to realize the iterative management process of the target system resources.

[0178] In the above embodiments, since the actual work such as management, monitoring, and operation and maintenance in the target system requires the configuration of corresponding configuration entry information such as management, monitoring, and operation and maintenance categories, after the target system is shut down, the corresponding configuration entries in various management systems can be cleaned up. The implementation order of the configuration cleaning stage for the operation and maintenance objects can be referred to Figure 7 , Figure 7 which is the schematic diagram of the configuration cleaning implementation order according to the embodiments of the present invention, as Figure 7As shown in the figure, the configuration cleaning phase may mainly include cleaning the monitoring configuration objects in the monitoring system, cleaning the configuration objects in the configuration management system, cleaning the configuration objects in the capacity management system, cleaning the configuration objects in the operation and maintenance security management system, and cleaning the configuration objects in the process management system. Among them, the operation and maintenance objects for cleaning in the monitoring system may mainly include shutting down the monitoring policies corresponding to the target system, etc.; the operation and maintenance objects for cleaning in the configuration management system may mainly include shutting down the configuration information of software, hardware, etc. corresponding to the target system, etc.; the operation and maintenance objects for cleaning in the capacity management system may mainly include shutting down the data collection policies corresponding to the target system, etc.; the operation and maintenance objects for cleaning in the operation and maintenance security management system may mainly include shutting down the operation and maintenance login configuration entries corresponding to the target system, etc.; the operation and maintenance objects for cleaning in the process management system may mainly include shutting down the configuration entries of the automated change process corresponding to the target system, etc.

[0179] The shutdown method of the system will be described below in conjunction with specific embodiments:

[0180] Figure 8 It is a structural block diagram of a system shutdown device according to a specific embodiment of the present invention, as Figure 8 shown, the device includes:

[0181] An operation and maintenance object identification module 802, which includes a system shutdown object identification sub-module, a resource recovery object identification sub-module, and a configuration cleaning object identification sub-module. Among them, the system shutdown object identification sub-module is used to identify the types and specific quantities of operation and maintenance objects that need to be shut down and taken offline during the shutdown process of the target system; the resource recovery object identification sub-module is used to identify the types and quantities of operation and maintenance objects that need to be classified during the shutdown process of the target system; the configuration cleaning object identification sub-module is used to identify the types and quantities of configuration-based operation and maintenance objects that need to be cleaned during the shutdown process of the target system;

[0182] An operation and maintenance object control table generation module 804, which is used to generate an operation and maintenance object control table required for the shutdown operation of the target system;

[0183] An operation and maintenance object control module 806, which is used to perform shutdown, recovery, and cleaning operations on all types of operation and maintenance objects in the operation and maintenance object control table according to the operation and maintenance object control until the offline shutdown of the target system is completed.

[0184] In the above embodiments, the implementation process of shutting down the target system can be first divided into six target stages: application shutdown, basic software shutdown, device shutdown, device power-off, resource recovery, and configuration cleanup. This can facilitate the separate management of the system shutdown work by stage. In addition, adding the two stages of resource recovery and configuration cleanup to the overall system shutdown work is beneficial for timely recovering important system resource information and completely cleaning up the effective configuration entries in various management systems.

[0185] In the above embodiments, the types of operation and maintenance objects of the target system can be identified according to the technical fields in the operation and maintenance work. The types and quantity information of all operation and maintenance objects that need to be shut down, recovered, cleaned, etc. during the shutdown process can be identified. The determination of the types and quantity information of operation and maintenance objects can delimit the scope of work for each stage, reducing the risk of misoperation and the omission problems caused by incomplete object identification. According to the information such as the online transaction line, data line, and upstream and downstream associated channel systems of the target system, shutdown dependency identification can be implemented for all operation and maintenance objects that need to be shut down, recovered, cleaned, etc. According to the shutdown dependency results, the shutdown operations of the operation and maintenance objects can be sorted, and an operation control table for the operation and maintenance objects can be generated. By sorting the operation and maintenance objects, the dependencies of the shutdown operation objects of the system can be clarified, avoiding the impact on the system functions and business continuity caused by unreasonable collaboration of multiple teams due to the shutdown operations.

[0186] In the above embodiments, the shutdown operation of the target system can be implemented in the order of increasing implementation serial numbers of the operation and maintenance objects in the operation and maintenance object control table until the complete shutdown of the target system is achieved, that is, the planned shutdown of the target system is finally realized, eliminating the possible risks brought by the shutdown of the target system and improving the management level of the full life cycle of the target system.

[0187] Through the description of the above implementation manners, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention.

[0188] In this embodiment, a shutdown device for a system is further provided. This device is used to implement the above embodiments and preferred implementation manners, and those that have been described will not be repeated. As used hereinafter, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0189] Figure 9 is a structural block diagram of a shutdown device for a system according to an embodiment of the present invention. As Figure 9 shown, the device includes:

[0190] A division module 902, configured to divide the process of shutting down the target system into multiple stages to obtain multiple target stages;

[0191] A first determination module 904, configured to determine the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target stages, to obtain multiple operation and maintenance objects, where the operation and maintenance area is the area to which the configuration applied to implement the functions of the target system belongs;

[0192] A second determination module 906, configured to determine the dependency relationships between the multiple operation and maintenance objects;

[0193] A sorting module 908, configured to sort the multiple operation and maintenance objects based on the dependency relationships to obtain an operation and maintenance object control table;

[0194] An execution module 910, configured to perform a shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table in the execution order of the multiple target stages;

[0195] Among them, the division module 902 and the first determination module 904 correspond to the above-mentioned operation and maintenance object identification module 802, the second determination module 906 and the sorting module 908 correspond to the above-mentioned operation and maintenance object control table generation module 804, and the execution module 910 corresponds to the above-mentioned operation and maintenance object control module 806.

[0196] In an exemplary embodiment, the first determination module 904 may implement determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: when the target phase is the application shutdown phase and the operation and maintenance area is the application area, determine the first object included in the target system; when there is a target service depending on the first object in the target system, adjust the object on which the target service depends to another object; after the adjustment of the object on which the target service depends to the other object is completed, determine whether the first object meets a first preset condition; when the first object meets the first preset condition, determine the first object as the operation and maintenance object; wherein, the first object includes at least one of the following: transaction line, data line, object implementing batch processing function, object implementing message passing.

[0197] In an exemplary embodiment, the first determination module 904 may implement determining whether the first object meets the first preset condition in the following manner: when the first object is a transaction line, determine whether the online transaction volume of the transaction line is zero and whether the duration of the online transaction volume being zero is greater than a first preset duration; when the online transaction volume is zero and the duration of the online transaction volume being zero is greater than the first preset duration, determine that the first object meets the first preset condition; when the first object is a data line, determine whether there is no data transmission on the data line and whether the duration of no data transmission is greater than a second preset duration; when there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determine that the first object meets the first preset condition; when the first object is an object implementing a batch processing function, determine whether the first object has no batch processing tasks and whether the duration of no batch processing tasks is greater than a third preset duration; when the first object has no batch processing tasks and the duration of no batch processing tasks is greater than the third preset duration, determine that the first object meets the first preset condition; when the first object is an object implementing message passing, determine whether the first object has no message passing tasks and whether the duration of no message passing tasks is greater than a fourth preset duration; when the first object has no message passing tasks and the duration of no message passing tasks is greater than the fourth preset duration, determine that the first object meets the first preset condition.

[0198] In an exemplary embodiment, the first determination module 904 may also implement determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: when the target phase is the basic software shutdown phase and the operation and maintenance area is the software area, determine the second objects included in the target system; determine whether the second objects meet a second preset condition; when the second objects meet the second preset condition, determine the second objects as the operation and maintenance objects; where the second objects include at least one of the following: transaction processing middleware software, message queue middleware software, database software, data transmission software, and operating system software.

[0199] In an exemplary embodiment, the first determination module 904 may implement determining whether the second objects meet the second preset condition in the following manner: when the second object is the transaction processing middleware software, determine the transaction line corresponding to the transaction processing middleware software included in the application area. When the online transaction volume of the transaction line is zero and the duration for which the online transaction volume is zero is greater than a first preset duration, determine that the second object meets the second preset condition; when the second object is the message queue middleware software, determine the object for implementing message passing corresponding to the message queue middleware software included in the application area. When there is no message passing task for the object for implementing message passing and the duration for which there is no message passing task is greater than a fourth preset duration, determine that the second object meets the second preset condition; when the second object is the database software, determine the shutdown state of the transaction processing middleware software. When the shutdown state indicates that the transaction processing middleware software has been successfully shut down and the successful shutdown lasts for a fifth preset duration, determine that the second object meets the second preset condition; when the second object is the data transmission software, determine the data line corresponding to the data transmission software included in the application area. When there is no data transmission on the data line and the duration for which there is no data transmission is greater than a second preset duration, determine that the second object meets the second preset condition; when the second object is the operating system software, determine the basic software included in the target system. When all of the basic software has been shut down and the shutdown lasts for a sixth preset duration, determine that the second object meets the second preset condition, where the basic software includes the transaction processing middleware software, the message queue middleware software, the database software, and the data transmission software.

[0200] In an exemplary embodiment, the first determination module 904 may also implement determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: When the target phase is the equipment shutdown phase and the operation and maintenance area is the hardware storage area, determine the third object included in the target system; determine whether the third object meets the third preset condition; when the third object meets the third preset condition, determine the third object as the operation and maintenance object; wherein, the third object includes at least one of the following: physical host, storage switch, disk device, tape library device, power module, computer room module.

[0201] In an exemplary embodiment, the first determination module 904 may implement determining whether the third object meets the third preset condition in the following manner: When the third object is a physical host, determine the operating system software running in the physical host, and when the operating system software has been shut down and the shutdown duration lasts for the seventh preset duration, determine that the third object meets the third preset condition; when the third object is a storage switch, determine that the operating system of the target system has been shut down and the shutdown duration lasts for the eighth preset duration, determine that the third object meets the third preset condition; when the third object is a disk device, determine that the operating system of the target system has been shut down and the shutdown duration lasts for the ninth preset duration, determine that the third object meets the third preset condition; when the third object is a tape library device, determine that the operating system of the target system has been shut down and the shutdown duration lasts for the tenth preset duration, determine that the third object meets the third preset condition; when the third object is a power module, determine that the hardware devices included in the target system have been shut down and the shutdown duration lasts for the eleventh preset duration, determine that the third object meets the third preset condition, wherein the hardware devices include; when the third object is a computer room module, determine that the hardware devices included in the target system have completed equipment removal, determine that the third object meets the third preset condition.

[0202] In an exemplary embodiment, the first determination module 904 may also implement determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: When the target phase is the equipment shutdown phase and the operation and maintenance area is the security area, determine the fourth object included in the target system; determine whether the fourth object meets the fourth preset condition; when the fourth object meets the fourth preset condition, determine the fourth object as the operation and maintenance object; wherein, the fourth object includes at least one of the following: encryption software client, encryption machine.

[0203] In an exemplary embodiment, the first determination module 904 may determine whether the fourth object meets the fourth preset condition in the following manner: when the fourth object is an encryption software client, determine the transaction line corresponding to the encryption software client included in the application field; when the online transaction volume of the transaction line is zero and the duration of the zero online transaction volume is greater than a first preset duration, determine that the fourth object meets the fourth preset condition; when the fourth object is an encryption machine, determine the data line for data transmission corresponding to the encryption machine included in the target system; when there is no data transmission on the data line and the duration of no data transmission is greater than a second preset duration, determine that the fourth object meets the fourth preset condition.

[0204] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: when the target phase is the equipment shutdown phase and the operation and maintenance area is the network area, determine the network switches included in the target system; when there is no network traffic on the network switches and the physical hosts included in the target system have been shut down, determine the network switches as the operation and maintenance objects.

[0205] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: when the target phase is the basic software shutdown phase and the operation and maintenance area is the batch scheduling area, determine the batch processing software included in the target system; when there is no batch processing task for the batch processing software and the duration of no batch processing task is greater than a third preset duration, determine the batch processing software as the operation and maintenance objects.

[0206] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: when the target phase is the basic software shutdown phase and the operation and maintenance area is the monitoring tool area, determine the monitoring automation software included in the target system; when the transaction processing middleware software and the database software in the target system have both been shut down and the shutdown duration has lasted for a twelfth preset duration, determine the monitoring automation software as the operation and maintenance objects.

[0207] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each target stage in the following manner: when the target stage is the resource recovery stage and the operation and maintenance area is the hardware storage area, determine at least one of the following included in the target system as the operation and maintenance object: physical machine, disk space, storage switch, disk device, tape library device, power module, computer room module.

[0208] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each target stage in the following manner: when the target stage is the resource recovery stage and the operation and maintenance area is the network operation and maintenance area, determine at least one of the following included in the target system as the operation and maintenance object: IP address, network bandwidth, network switch.

[0209] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each target stage in the following manner: when the target stage is the resource recovery stage and the operation and maintenance area is the security area, determine at least one of the following included in the target system as the operation and maintenance object: security certificate, encryption machine.

[0210] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each target stage in the following manner: when the target stage is the configuration cleanup stage and the operation and maintenance area is the application area, determine at least one of the following of the target system as the operation and maintenance object: configuration entries of the system configuration of the target system, automated change process of the target system, configuration entries of the capacity configuration of the target system.

[0211] In an exemplary embodiment, the first determination module 904 may also determine the operation and maintenance objects included in each operation and maintenance area of the target system in each target stage in the following manner: when the target stage is the configuration cleanup stage and the operation and maintenance area is the security area, determine at least one of the following of the target system as the operation and maintenance object: operation and maintenance login entries of the target system, system operation and maintenance high-privilege authorization media of the target system.

[0212] In an exemplary embodiment, the first determination module 904 may also implement determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases in the following manner: when the target phase is the configuration cleanup phase and the operation and maintenance area is the monitoring tool area, determining the monitoring policy of the target system as the operation and maintenance object.

[0213] In an exemplary embodiment, the sorting module 906 may implement sorting multiple operation and maintenance objects based on the dependency relationship to obtain an operation and maintenance object control table in the following manner: determining the phase operation and maintenance objects belonging to each of the target phases among the multiple operation and maintenance objects; performing the following operations for the phase operation and maintenance objects of each of the target phases to obtain a sub-control table for the target phase: determining the operation type of the phase operation and maintenance object; determining the implementation sequence number of the phase operation and maintenance object based on the dependency relationship; determining the quantity of the phase operation and maintenance object; determining the name of the operation and maintenance team for operating the phase operation and maintenance object; determining the operation effect of shutting down the phase operation and maintenance object; determining the task interval, where the task interval is used to indicate that after performing the shutdown operation on the phase operation and maintenance object, the next object of the phase operation and maintenance object is to be shut down after the task interval, generating the sub-control table based on the phase operation and maintenance object, the operation type, the implementation sequence number, the quantity, the name of the operation and maintenance team, the operation effect, and the task interval; sorting the multiple sub-control tables according to the execution sequence of the multiple target phases to obtain the operation and maintenance object control table.

[0214] In an exemplary embodiment, the division module 902 may implement dividing the process of shutting down the target system into multiple phases to obtain multiple target phases in the following manner: dividing the process of shutting down the target system into an application shutdown phase, a basic software shutdown phase, a device shutdown phase, a device power-off phase, a resource recovery phase, and a configuration cleanup phase; determining the application shutdown phase, the basic software shutdown phase, the device shutdown phase, the device power-off phase, the resource recovery phase, and the configuration cleanup phase as the target phases.

[0215] It should be noted that the above-mentioned various modules may be implemented by software or hardware. For the latter, it may be implemented in the following manner, but not limited thereto: all the above-mentioned modules are located in the same processor; or, the above-mentioned various modules are separately located in different processors in any combination form.

[0216] An embodiment of the present invention also provides a computer-readable storage medium, in which a computer program is stored, and the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0217] In an exemplary embodiment, the above-mentioned computer-readable storage medium may include, but is not limited to: various media that can store computer programs such as USB flash drives, read-only memory (ROM for short), random access memory (RAM for short), mobile hard disks, magnetic disks, or optical discs.

[0218] An embodiment of the present invention also provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0219] In an exemplary embodiment, the above-mentioned electronic device may further include a transmission device and an input / output device. Among them, the transmission device is connected to the above-mentioned processor, and the input / output device is connected to the above-mentioned processor.

[0220] An embodiment of the present invention also provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the steps of the methods in various embodiments of the present application.

[0221] Specific examples in this embodiment may refer to the examples described in the above embodiments and exemplary embodiments, and will not be repeated here.

[0222] Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. They can be implemented by program codes executable by the computing device. Thus, they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described can be executed in a different order from here, or they can be separately made into individual integrated circuit modules, or multiple modules or steps among them can be made into a single integrated circuit module to implement. In this way, the present invention is not limited to any specific combination of hardware and software.

[0223] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A shutdown method for a system, characterized in that, Including: Dividing the process of implementing the shutdown of the target system into multiple stages to obtain multiple target stages; Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target stages to obtain multiple operation and maintenance objects, where the operation and maintenance area is the area to which the configuration applied to implement the functions of the target system belongs; Determining the dependency relationships between the multiple operation and maintenance objects; Sorting the multiple operation and maintenance objects based on the dependency relationships to obtain an operation and maintenance object control table; Performing a shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table in the execution order of the multiple target stages.

2. The method according to claim 1, characterized in that, Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target stages includes: When the target stage is the application shutdown stage and the operation and maintenance area is the application area, determining the first object included in the target system, and when there is a target service depending on the first object in the target system, adjusting the object on which the target service depends to another object; When the adjustment of the object on which the target service depends to the other object is completed, determining whether the first object meets a first preset condition; When the first object meets the first preset condition, determining the first object as the operation and maintenance object; Wherein, the first object includes at least one of the following: transaction line, data line, object implementing batch processing function, object implementing message passing.

3. The method according to claim 2, wherein Determining whether the first object meets the first preset condition includes: When the first object is a transaction line, determining whether the online transaction volume of the transaction line is zero and whether the duration of the online transaction volume being zero is greater than a first preset duration. When the online transaction volume is zero and the duration of the online transaction volume being zero is greater than the first preset duration, determining that the first object meets the first preset condition; When the first object is a data line, determining whether there is no data transmission on the data line and whether the duration of no data transmission is greater than a second preset duration. When there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determining that the first object meets the first preset condition; When the first object is an object implementing a batch processing function, determining whether the first object has no batch processing tasks and whether the duration of no batch processing tasks is greater than a third preset duration. When the first object has no batch processing tasks and the duration of no batch processing tasks is greater than the third preset duration, determining that the first object meets the first preset condition; When the first object is an object implementing message passing, determining whether the first object has no message passing tasks and whether the duration of no message passing tasks is greater than a fourth preset duration. When the first object has no message passing tasks and the duration of no message passing tasks is greater than the fourth preset duration, determining that the first object meets the first preset condition.

4. The method according to claim 1, characterized in that, In each of the target phases, the operation and maintenance objects included in each operation and maintenance area of the target system include: In the case where the target phase is the basic software shutdown phase and the operation and maintenance area is the software area, determine the second object included in the target system; Determine whether the second object meets the second preset condition; In the case where the second object meets the second preset condition, determine the second object as the operation and maintenance object; Wherein, the second object includes at least one of the following: transaction processing middleware software, message queue middleware software, database software, data transmission software, operating system software.

5. The method according to claim 4, characterized in that, Determining whether the second object meets the second preset condition includes: In the case where the second object is transaction processing middleware software, determine the transaction line corresponding to the transaction processing middleware software included in the application area. In the case where the online transaction volume of the transaction line is zero and the continuous duration of the zero online transaction volume is greater than the first preset duration, determine that the second object meets the second preset condition; In the case where the second object is message queue middleware software, determine the object for implementing message passing corresponding to the message queue middleware software included in the application area. In the case where there is no message passing task for the object for implementing message passing and the continuous duration of no message passing task is greater than the fourth preset duration, determine that the second object meets the second preset condition; In the case where the second object is database software, determine the shutdown state of the transaction processing middleware software. In the case where the shutdown state indicates that the transaction processing middleware software has been successfully shut down and the successful shutdown lasts for the fifth preset duration, determine that the second object meets the second preset condition; In the case where the second object is data transmission software, determine the data line corresponding to the data transmission software included in the application area. In the case where there is no data transmission on the data line and the continuous duration of no data transmission is greater than the second preset duration, determine that the second object meets the second preset condition; In the case where the second object is operating system software, determine the basic software included in the target system. In the case where all the basic software has been shut down and the shutdown lasts for the sixth preset duration, determine that the second object meets the second preset condition, where the basic software includes the transaction processing middleware software, the message queue middleware software, the database software, and the data transmission software.

6. The method according to claim 1, wherein In each of the target phases, the operation and maintenance objects included in each operation and maintenance area of the target system include: In the case where the target phase is the equipment shutdown phase and the operation and maintenance area is the hardware storage area, determine the third object included in the target system; Determine whether the third object meets the third preset condition; In the case where the third object meets the third preset condition, determine the third object as the operation and maintenance object; Wherein, the third object includes at least one of the following: physical host, storage switch, disk device, tape library device, power module, computer room module.

7. The method according to claim 6, characterized in that, Determining whether the third object meets the third preset condition includes: When the third object is a physical host, determine the operating system software running in the physical host. When the operating system software has been shut down and the shutdown duration lasts for the seventh preset duration, determine that the third object meets the third preset condition; When the third object is a storage switch, determine that the operating system of the target system has been shut down and the shutdown duration lasts for the eighth preset duration, determine that the third object meets the third preset condition; When the third object is a disk device, determine that the operating system of the target system has been shut down and the shutdown duration lasts for the ninth preset duration, determine that the third object meets the third preset condition; When the third object is a tape library device, determine that the operating system of the target system has been shut down and the shutdown duration lasts for the tenth preset duration, determine that the third object meets the third preset condition; When the third object is a power module, determine that the hardware devices included in the target system have been shut down and the shutdown duration lasts for the eleventh preset duration, determine that the third object meets the third preset condition; When the third object is a computer room module, determine that the hardware devices included in the target system have completed equipment removal, determine that the third object meets the third preset condition.

8. The method according to claim 1, wherein Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the equipment shutdown phase and the operation and maintenance area is the security area, determine the fourth object included in the target system; Determine whether the fourth object meets the fourth preset condition; When the fourth object meets the fourth preset condition, determine the fourth object as the operation and maintenance object; Wherein, the fourth object includes at least one of the following: encryption software client, encryption machine.

9. The method according to claim 8, wherein Determining whether the fourth object meets the fourth preset condition includes: When the fourth object is an encryption software client, determine the transaction line corresponding to the encryption software client included in the application field. When the online transaction volume of the transaction line is zero and the duration of the zero online transaction volume is greater than the first preset duration, determine that the fourth object meets the fourth preset condition; When the fourth object is an encryption machine, determine the data line for transmitting data corresponding to the encryption machine included in the target system. When there is no data transmission on the data line and the duration of no data transmission is greater than the second preset duration, determine that the fourth object meets the fourth preset condition.

10. The method according to claim 1, wherein Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the equipment shutdown phase and the operation and maintenance area is the network area, determine the network switch included in the target system; When there is no network traffic in the network switch and the physical hosts included in the target system have been shut down, the network switch is determined as the operation and maintenance object.

11. The method according to claim 1, wherein Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the basic software shutdown phase and the operation and maintenance area is the batch scheduling area, determine the batch processing software included in the target system. When there is no batch processing task in the batch processing software and the duration without batch processing tasks is greater than the third predetermined duration, the batch processing software is determined as the operation and maintenance object.

12. The method according to claim 1, wherein Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the basic software shutdown phase and the operation and maintenance area is the monitoring tool area, determine the monitoring automation software included in the target system. When the transaction processing middleware software and the database software in the target system have both been shut down and the shutdown duration has lasted for the twelfth predetermined duration, the monitoring automation software is determined as the operation and maintenance object.

13. The method according to claim 1, characterized in that, Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the resource recovery phase and the operation and maintenance area is the hardware storage area, at least one of the following included in the target system is determined as the operation and maintenance object: physical machine, disk space, storage switch, disk device, tape library device, power module, computer room module.

14. The method according to claim 1, characterized in that, Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the resource recovery phase and the operation and maintenance area is the network operation and maintenance area, at least one of the following included in the target system is determined as the operation and maintenance object: IP address, network bandwidth, network switch.

15. The method according to claim 1, characterized in that, Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the resource recovery phase and the operation and maintenance area is the security area, at least one of the following included in the target system is determined as the operation and maintenance object: security certificate, encryption machine.

16. The method according to claim 1, wherein Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the configuration cleaning phase and the operation and maintenance area is the application area, at least one of the following of the target system is determined as the operation and maintenance object: the configuration entries of the system configuration of the target system, the automated change process of the target system, the configuration entries of the capacity configuration of the target system.

17. The method according to claim 1, characterized in that, Determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases includes: When the target phase is the configuration cleaning phase and the operation and maintenance area is the security area, at least one of the following of the target system is determined as the operation and maintenance object: the operation and maintenance login entries of the target system, the system operation and maintenance high-privilege authorization medium of the target system.

18. The method according to claim 1, characterized in that, In each of the target phases, the operation and maintenance objects included in each operation and maintenance area of the target system include: In the case where the target phase is the configuration cleanup phase and the operation and maintenance area is the monitoring tool area, the monitoring policy of the target system is determined as the operation and maintenance object.

19. The method according to claim 1, wherein Sorting the multiple operation and maintenance objects based on the dependency relationship to obtain an operation and maintenance object control table includes: Determining the phase operation and maintenance objects belonging to each of the target phases among the multiple operation and maintenance objects; For the phase operation and maintenance objects of each target phase, the following operations are performed to obtain a sub-control table for the target phase: determining the operation type of the phase operation and maintenance object; determining the implementation sequence number of the phase operation and maintenance object based on the dependency relationship; determining the quantity of the phase operation and maintenance object; determining the name of the operation and maintenance team for operating the phase operation and maintenance object; determining the operation effect of shutting down the phase operation and maintenance object; determining the task interval, where the task interval is used to indicate that after the shutdown operation is performed on the phase operation and maintenance object, the next object of the phase operation and maintenance object is shut down after the task interval, and generating the sub-control table based on the phase operation and maintenance object, the operation type, the implementation sequence number, the quantity, the name of the operation and maintenance team, the operation effect, and the task interval; Sorting the multiple sub-control tables according to the execution order of the multiple target phases to obtain the operation and maintenance object control table.

20. The method according to claim 1, characterized in that Dividing the process of shutting down the target system into multiple phases to obtain multiple target phases includes: Dividing the process of shutting down the target system into an application shutdown phase, a basic software shutdown phase, a device shutdown phase, a device power-off phase, a resource recovery phase, and a configuration cleanup phase; Determining the application shutdown phase, the basic software shutdown phase, the device shutdown phase, the device power-off phase, the resource recovery phase, and the configuration cleanup phase as the target phases.

21. A shutdown device for a system, characterized in that, Including: A dividing module for dividing the process of shutting down the target system into multiple phases to obtain multiple target phases; A first determination module for determining the operation and maintenance objects included in each operation and maintenance area of the target system in each of the target phases to obtain multiple operation and maintenance objects, where the operation and maintenance area is the area to which the configuration applied to implement the functions of the target system belongs; A second determination module for determining the dependency relationship between the multiple operation and maintenance objects; A sorting module for sorting the multiple operation and maintenance objects based on the dependency relationship to obtain an operation and maintenance object control table; An execution module for performing a shutdown operation on the operation and maintenance objects included in the operation and maintenance object control table according to the execution order of the multiple target phases.

22. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, where the computer program is configured to execute the method described in any one of claims 1 to 20 when running.

23. An electronic device, comprising a memory and a processor, characterized in that, A computer program is stored in the memory, and the processor is configured to run the computer program to execute the method described in any one of claims 1 to 20.

24. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 20.

Images