Sun Microsystems, Inc.

Open Text S.a.

Oracle America, Inc.

Matthew Helgren

Paris E Bingham, Jr

Alan J Treece

Rex G Martin

Mike E Little

Mark R Scheevel

Kin-Chung Fung

John H Martin

Michael J Wookey

Ruslan V Belkin

Michael E Little

Systems and methods for invalidating and regenerating pages. In one embodiment, a method can include detecting content changes in a content database including various objects. The method can include causing an invalidation generator to generate an invalidation based on the modification and communicating the invalidation to a dependency manager. A cache manager can be notified that pages in a cache might be invalidated based on the modification via a page invalidation notice. In one embodiment, a method can include receiving a page invalidation notice and sending a page regeneration request to a page generator. The method can include regenerating the cached page. The method can include forwarding the regenerated page to the cache manager replacing the cached page with the regenerated page. In one embodiment, a method can include invalidating a cached page based on a content modification and regenerating pages which might depend on the modified content.

Event-driven invalidation of pages for web-based applications

Event-driven regeneration of pages for web-based applications

An SLO (service level objective) is represented by a model that includes nodes that represent elements in a system that are used to fulfill the SLO and information that represents dependencies between the elements. Telemetry information is received describing a condition of an element in the system. The telemetry information can be applied to a particular procedure associated with a particular node in the model to determine if there is a problem associated with the element represented by the particular node. At least a portion of the telemetry information is applied to procedures to determine problem cause information describing which elements have problems relating to the SLO. A relative contribution of elements to a problem associated with the SLO is determined by analyzing the problem cause information and the dependencies between the elements.

Method and apparatus for identifying problem causes in a multi-node system

A knowledge automation engine used to detect product issues on products. A knowledge automation engine may evaluate a check against one or more facts to detect a product issue. Facts used by the knowledge automation engine may include product configuration facts. A check may include one or more rules and reference one or more product check matrixes of facts, such as, but not limited to, identifiers for product packages and patches to be used by a check. As packages and/or patches become available for a product, they may be added to a product check matrix for the product. The packages and patches may be added to the database using predefined associations. The check may use the product check matrix to update packages and/or patches (including adding new packages/patches and removing old packages/patches) on a product accessible by the knowledge automation engine.

Product check matrix

Methods, systems, and articles of manufacture consistent with the present invention provide for managing exposure to failure for computer-based systems. Information about a computer-based system is asynchronously received. An exposure level to failure of the computer-based system is calculated based on the received information. A stability of the computer-based system is determined based on the exposure level. A stability indication is output responsive to the determined stability.

Managing exposure to failure for computer-based systems

Fact collection for a knowledge automation engine to use in detecting product issues on products. A knowledge automation engine may evaluate a check against a fact to detect a product issue on a product and provide a user of the product remediation information. A check may contain a product issue description, a rule to evaluate against a fact in order to detect the product issue, and remediation information to help a user address the product issue if the product issue is detected on the product. Product issues may include product installation validation and known product bugs. Facts used by the knowledge automation engine may include product configuration facts. Static facts may be collected into a fact repository. A fact collector may be used to collect facts not found in the fact repository but needed to execute checks on the knowledge automation engine.

Fact collection for product knowledge management

A system for creating and editing checks for a knowledge automation engine to use in detecting product issues on products. A knowledge automation engine may evaluate a check against a fact to detect a product issue on a product and provide a client of the product remediation information. A check may contain a product issue description, a rule to evaluate against a fact in order to detect the product issue, and remediation information to help a client address the product issue if the product issue is detected on the product. Product issues may include product installation validation and known product bugs. Facts used by the knowledge automation engine may include product configuration facts. Statistics on check execution results may be accumulated to provide additional information on products through their life cycle.

Product knowledge management

A system for creating and editing checks for a knowledge automation engine to use in detecting product issues on products. A knowledge automation engine may evaluate a check against a fact to detect a product issue on a product and provide a user of the product remediation information. A check may contain a product issue description, a rule to evaluate against a fact in order to detect the product issue, and remediation information to help a user address the product issue if the product issue is detected on the product. Product issues may include product installation validation and known product bugs. Facts used by the knowledge automation engine may include product configuration facts. Checks may be created and edited using a standard interface.

Check creation and maintenance for product knowledge management

A check for a knowledge automation engine to use in detecting product issues on products. A knowledge automation engine may evaluate a check against a fact to detect a product issue on a product and provide a user of the product remediation information. A check may contain a product issue description, a rule to evaluate against a fact in order to detect the product issue, and remediation information to help a user address the product issue if the product issue is detected on the product. Product issues may include product installation validation and known product bugs. Facts used by the knowledge automation engine may include product configuration facts.

Checks for product knowledge management

A system and method for identifying problems with a system configuration may evaluate system configuration information against one or more configuration recommendations or rules. The evaluated system configuration may include various types of software and hardware components which may impact the operations of the computer system. Rules may be any information identifying an issue or describing a recommended configuration for the software or hardware component. A knowledge-based language or a programming language analyzer may be used to specify the rules. In one embodiment, a rules engine may be used as part of the problem detection application to evaluate configuration data against associated rules. A rules engine may be any mechanism used to recognize, interpret and process the configuration data against the rules. The results of the evaluation process may be stored for further analysis.

Growing community of inventors

Austin, TX, United States of America

Matthew Helgren