Browse Prior Art Database

Method and system to automatic restore applications

IP.com Disclosure Number: IPCOM000236354D
Publication Date: 2014-Apr-22
Document File: 3 page(s) / 32K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes a new way to manage business-critical applications running on the system. Starting from the understanding that a classical deamon-based methodology is not robust enough, the article presents how applications can centrally be managed by a system, installed on the OS, which ckecks the health of registered applications and then decides to restart them or even re-install them in case of persistent failures.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Method and system to automatic restore applications

It is common to have several different applications installed on computers . Many times some of these applications are mandatory, due to company security guidelines, or are needed for the proper working and usage of the machine . For such important applications, some methods to ensure that they are running as expected are in place . One example are the well known watch dogs that start the application service if it was previously stopped by the user or by some unexpected event . Some more complex cases exist. For example, a user could un-install the application or the application could, for some reason, be damaged. In this case the common solution is to have some sort of software (policy provisioning software) which is able to understand that the computer is missing an application or it is not working properly and which reinstall it . No solution is in place if these kind of things happen to the application that needs to control other applications.

The solution here disclosed provides a system and method to recover an application when it is damaged and cannot be reactivated . The idea is to have a new more efficient watch dog able not only to monitor the applications but also to restore them in case of disruption. To do this, it is needed to add a common stack to the operating system where information of the applications are saved together with the install executable files. This method could even be generalized for every application .

Three possible different paths can be exploited to save the information and binaries to perform the installation:


1) The common stack itself is able to capture the info when an install command is run
2) The information are manually added to the common stack library
3) Adding to the install commands (rpm, exe, etc) a new call to the common stack is created. Any time one of this commands is run, it not only execute the installation but also registers the proper info in the common stack .

The present solution chooses path 1).

Once that the tool according to the present solution is not able to restart the application it declares the application as not working properly or damaged and proceeds with an un-install and reinstall to have it working again in the proper way .

The idea of this disclosure is about a new more efficient and complete watch dog able not only to restart an application process if it is stopped , but also to eventually repair the application if it is damaged. To accom...