Abstract: The invention provides methods of forecasting functionality for clustered computing configurations that may be deployed across computer network systems and environments that may function in conjunction with a wide range of hardware and software configurations. An exemplary method of forecasting a forecast status of a clustered computing system is presented including: creating a current status model of the clustered computing system based on a start data set; applying an event input set to the current status model; and creating a forecast status based on the applying the event input set to the current status model. In some embodiments, the current status model may be represented by: a configured operational status, a current operational status, and a projected operational status of the clustered computing system.

Abstract: Mechanism for displaying a layout of graphic user interface properties in a panel. The data is stored in managed object format (MOF) files and defines how the data to be displayed is interrelated. The generic mechanism defines the layout of interrelated object properties, where the layout of similar panels appear differently based on the type of the object of focus. An object is associated with a defined set of properties that may correspond to properties of other objects, as well. The system isolates information that determines the look and feel of status and property layout displays of a GUI into one file. This file can be quickly edited to change the appearance when needed. The application source code utilizes a class schema and the modifiable file is read in and processed when the application is launched. Further changes require the application to be restarted to read in the modified file.

Abstract: A document reader program determines the existence of an updated version of a document file at a network location specified by an original version of the document file. The document reader program then presents the user a choice of rendering the original version or the updated version in human-cognizable form. For example, a user can request help for a host application, which accesses an original version of a help file via the document reader. Instead of displaying information from the original help file, the reader access a network location specified in the original help file, downloads an updated help file and then displays its information to the user. The updated help file can correspond to the local version of the host application or, in another embodiment, the most-recent help file for the most-recent version of the host application.

Abstract: A cluster simulator simulates reformation of a real cluster in response to failure events. Profile programs on the cluster can gather data useful to the simulation and transmit the profile data to the simulator. The simulator can generate a model of the real cluster, the model itself being a virtual cluster. A user can select virtual failure events from a menu to apply to the model and the simulator responds by generating a post-failure virtual cluster in the configuration that the real cluster would assume in the event of the corresponding real failure. Sequences of virtual failures can also be tested for a given cluster configuration to evaluate its robustness. Comprehensive testing using virtual failure sequences can also be applied to different cluster configuration so that an optimum configuration can be recommended.

Abstract: A rule based compatibility module provides a single unified mechanism for testing rules where testing results depend on various combinations of database queries, computable values, and/or run-string parameters. The testing results may be evaluated within a particular operational environment. The rule based compatibility module encapsulates all versions of compatibility issues, which are highly dependant on the operational context, into one simple mechanism, thereby reducing risks of unexpected behaviors caused by improper or incomplete handling of compatibility issues. In addition, the rule based compatibility module provides a simple mechanism for handling ad-hoc run-string switches used for debugging, or for optional enabling or disabling of features under development.

Abstract: Mechanism for displaying a layout of graphic user interface properties in a panel. The data is stored in managed object format (MOF) files and defines how the data to be displayed is interrelated. The generic mechanism defines the layout of interrelated object properties, where the layout of similar panels appear differently based on the type of the object of focus. An object is associated with a defined set of properties that may correspond to properties of other objects, as well. The system isolates information that determines the look and feel of status and property layout displays of a GUI into one file. This file can be quickly edited to change the appearance when needed. The application source code utilizes a class schema and the modifiable file is read in and processed when the application is launched. Further changes require the application to be restarted to read in the modified file.

Abstract: A mechanism for displaying a layout of graphic user interface properties in a panel. The generic mechanism defines the layout of interrelated object properties, where the layout of similar panels appear differently based on the type of the object of focus. An object is associated with a defined set of properties that may correspond to properties of other objects, as well. An item is selected from a control object, such as a table, and causes a controlled object, i.e., a second table, to be populated with appropriate data. Data Listeners are used to determine when data change events occur. When an event occurs, a unique identifier is used to determine what queries are necessary to populate the subordinate table data. Controller and controlled tables may be nested in a variety of ways using a table controller connection class to identify how the unique identifier is correlated with the subordinate tables.

Abstract: A rule based compatibility module provides a single unified mechanism for testing rules where testing results depend on various combinations of database queries, computable values, and/or run-string parameters. The testing results may be evaluated within a particular operational environment. The rule based compatibility module encapsulates all versions of compatibility issues, which are highly dependant on the operational context, into one simple mechanism, thereby reducing risks of unexpected behaviors caused by improper or incomplete handling of compatibility issues. In addition, the rule based compatibility module provides a simple mechanism for handling ad-hoc run-string switches used for debugging, or for optional enabling or disabling of features under development.