Abstract:
A resource management method (300) and a corresponding system are proposed. In the solution of the invention, an authority publishes (324) multiple rules, each one defining a desired target configuration for a category of subjects (without any information about their dependencies). Each subject retrieves (320-322, 326) the rules corresponding to its category in a random order. The rules are then applied (427-439) on the subject according to a trial-and-fail approach. Particularly, the application of any failed rule is continually repeated (427-448), until all the rules are successfully applied (463) or a deadlock condition is detected (451). In this way, any dependency is automatically resolved on the subject at run time. Moreover, as soon as all the rules have been successfully applied the compliance of the subject to the rules is verified (455-57) again; should the subject be not compliant to one or more rules any longer, an infinite loop condition is detected (466).
Abstract:
A method (300;600) and system for monitoring distributed applications (for example, running on multiple WAS nodes of a cluster) is proposed. The solution of the invention is based on a self-adaptive resource management infrastructure. Particularly, an authority publishes (306-312) a plurality of rules, each one defining a desired target configuration for a category of subjects. A membership controller on each subject is responsible to assign (315-333) the subject to the respective category; a compliance engine then retrieves and applies (336-351) the rules corresponding to the category of the subject. The resource management infrastructure is used to implement a monitoring on-demand of the distributed application. For this purpose, two rules are defined (603-606) for the WAS nodes having the distributed application in a running condition and in a non-running condition, respectively. Each WAS node having the distributed application in the running condition applies (639-645) the first rule, so as to start the monitoring application; as soon as the distributed application switches to the non-running condition, the WAS node applies (654-657) the second rule, so as to stop the monitoring application automatically.