A scheduling scheme configuration method includes performing state verification on a plurality of operation dimensions involved in generating a scheduling scheme, and, in response to one or more of the operation dimensions being abnormal, removing the one or more abnormal operation dimensions to generate a new scheduling scheme.

Approaches for managing applications in a cluster are described. In an example, a first agent may be executing on a first programmable network adapter card installed within a first computing node within a cluster. The first agent may isolate an application executing on the first computing node. Thereafter, the application may be managed by the second computing node.

The following description is directed to storing properties of requests to potentially block future requests having similar properties. In one example, a request can be received. A property of the request can be stored so that the property persists across an initialization sequence of a computer system. At least the property can be used to determine whether to block any future requests having similar properties.

A method includes receiving, by an electronic device, an instruction for wiping data or performing a factory reset, setting an identifier according to the instruction, shutting down or restarting electronic device, reading the identifier when the electronic device is powered on or is connected to a network, sending a request to a server to request the server to delete a security service from a secure element (SE), receiving a command from the server, where the command instructs the electronic device to delete a target security service from the SE, and the target security service is based on a security service installed in the SE and a list of deletable security services stored in the server, and deleting, a secure element applet corresponding to the target security service from the SE according to the first command.

Described embodiments include methods and systems for managing client-side services. An intermediary may receive metadata from a first client device of the plurality of client devices. The metadata can include runtime characteristics of a first instance of a service that is incorporated into a client-side application or a web application. The first instance may execute on the first client device and request service data from the at least one server. The intermediary can detect an anomaly in the operation of the first instance of the service. The intermediary can identify an operation of the first instance of the service causing the detected anomaly. The intermediary can, responsive to the detected anomaly, cause delay, removal or modification of operations corresponding to the identified operation, in other instances of the service executing on the plurality of client devices.

A computer-implemented runtime system is operable of providing a continuous product execution runtime environment for an application via a healthcare network. The system includes a focus machine and an action plan repository, to provide an autonomous runtime environment by at least: monitoring a running use case of at least one application on at least one device; taking over responsibility of a running use case of the at least one application, upon an error state being detected for the monitored running use case; analyzing the error state of the running use case detected; obtaining at least one suitable substitution action out of a plurality of actions deposited in the action plan repository, based on the error state of the running use case analyzed; and terminating and completing at least a part of the running use case, by employing the at least one substitution actions obtained, on the at least one application.

A tool for performing remote part reseat actions. Responsive to receiving a request for a scheduled operation, the tool generates an operation table in a push file. Responsive to a determination that there is at least one redundant component for the scheduled operation, the tool identifies the at least one redundant component. The tool determines one or more tolerable errors for the at least one redundant component. The tool appends the at least one redundant component and the one or more tolerable errors to the operation table in the push file. The tool schedules the push file to prescribe one or more recovery operations for the scheduled operation.

A system and method for compiling and dynamically reconfiguring the management of functionalities carried among a set of multiple common compute nodes. During the inoperation of one node of the set of multiple common compute nodes, higher-criticality functionalities can be reassigned to other common nodes to ensure maintained operation of the higher-criticality functionalities.

A method is provided. The method of resetting a system, comprising: receiving data from the electronic sub-system; determine if a non-hardware fault is detected; if a non-hardware fault is detected, then performing a software reset of the electronics sub-system; if no non-hardware fault has been detected, then determining if a hardware fault is detected; and if a hardware fault is detected, then performing a hardware reset of the system.

A system and method for compiling and dynamically reconfiguring the management of functionalities carried among a set of multiple common compute nodes. During the inoperation of one node of the set of multiple common compute nodes, higher-criticality functionalities can be reassigned to other common nodes to ensure maintained operation of the higher-criticality functionalities.