Abstract: Systems, methods and computer readable media for implementing a Focus-Driven User Interface using a Focus-Driven MVC architecture are described. The Focus-Driven MVC architecture builds on the traditional MVC framework, adding a Focus component between the Controller and Model components. The Focus component implements Focus Logic to handle Focus-Driven features. The Focus component may receive access commands or requests from the Controller, relay those commands to the Model and, in response, obtain data from the Model. The Focus Logic applies rules to the data, determines relevancy rankings for the given property, and sends the processed data to the Controller which, in turn, may update the user interface with the processed data.

Abstract: According to one general aspect, a method may include determining the validity of a registry entry, wherein the registry entry is included in a deleted items registry, the deleted items registry including registry entries previously determined to be invalid. Upon determining the registry entry is valid, moving the registry entry to a valid items registry, and upon determining the registry entry is invalid, determine if the registry entry has been invalid more than a threshold number of times, upon determining the registry entry has not been invalid more than the threshold number of times, increase a period of time before a next determination as to whether the registry entry in the deleted items registry is valid, and upon determining the registry entry has been invalid more than the threshold number of times, remove the second registry entry from the deleted items registry.

Abstract: According to one general aspect, a method may include determining the validity of a registry entry, wherein the registry entry is included in a deleted items registry, the deleted items registry including registry entries previously determined to be invalid. Upon determining the registry entry is valid, moving the registry entry to a valid items registry, and upon determining the registry entry is invalid, determine if the registry entry has been invalid more than a threshold number of times, upon determining the registry entry has not been invalid more than the threshold number of times, increase a period of time before a next determination as to whether the registry entry in the deleted items registry is valid, and upon determining the registry entry has been invalid more than the threshold number of times, remove the second registry entry from the deleted items registry.

Abstract: According to one general aspect, a method may include maintaining a primary registry of registry entries. Each registry entry may include a description and a network address of a network service. The method may also include periodically determining the validity a registry entry, wherein the registry entry is included in the primary registry. The method may further include, if the registry entry is not valid, moving the registry entry to a deleted items registry of registry entries. The method may also include periodically determining the validity a registry entry that is included in the deleted items registry; and, if that registry entry is valid, moving that registry entry back to the primary registry.

Abstract: According to one general aspect, a method may include requesting, from a database and by a program executing on a mobile computing device, at least a portion of a business service context regarding a business service. The method may also include receiving, from the database, an aggregated database result regarding the business service. The aggregated database result may include the requested business service context and wherein the business service context includes information from a plurality of applications. The method may also include displaying, via the mobile computing device, at least a portion of the information included by the business service context.

Abstract: According to one general aspect, a method may include maintaining a primary registry of registry entries. Each registry entry may include a description and a network address of a network service. The method may also include periodically determining the validity a registry entry, wherein the registry entry is included in the primary registry. The method may further include, if the registry entry is not valid, moving the registry entry to a deleted items registry of registry entries. The method may also include periodically determining the validity a registry entry that is included in the deleted items registry; and, if that registry entry is valid, moving that registry entry back to the primary registry.

Abstract: A method and system to convert an existing web service from a first web services implantation type to a second web services implementation type. Example implementation types include SOAP and Representational State Transfer (REST). This conversion is achieved by recognizing and classifying available information from each of the distinct implementation types. After proper recognition and classification as disclosed herein, a deterministic process may be utilized to assist in converting or translating the exposed interface; thereby assisting in developing an interface, based on a different interface type than the one already exposed, may be provided.

Abstract: This disclosure relates generally to the field of federated configuration management databases (CMDBs). To claim compliance with the CMDBf Standard (“the Standard”), a CMDB implementation must provide working and interoperable implementations of the interfaces defined in the Standard. To make a working implementation, certain non-obvious features are required that are not addressed by the Standard. Among these requirements are: registering management data repositories (MDRs) so that they can be federated; managing/maintaining the list of federated MDRs; querying an MDR for its Data Model; using such MDR Data Models to define mappings of one or more attributes from the MDR data model to one or more attributes of one or more of the CMDB's data models; identifying attributes and defining rules to be used when reconciliation is performed; and managing as well as storing data representative of those mappings. This disclosure addresses these and other deficiencies.

Abstract: According to one general aspect, a method may include requesting, from a database and by a program executing on a mobile computing device, at least a portion of a business service context regarding a business service. The method may also include receiving, from the database, an aggregated database result regarding the business service. The aggregated database result may include the requested business service context and wherein the business service context includes information from a plurality of applications. The method may also include displaying, via the mobile computing device, at least a portion of the information included by the business service context.

Abstract: Systems, methods and computer readable media for implementing a Focus-Driven User Interface using a Focus-Driven MVC architecture are described. The Focus-Driven MVC architecture builds on the traditional MVC framework, adding a Focus component between the Controller and Model components. The Focus component implements Focus Logic to handle Focus-Driven features. The Focus component may receive access commands or requests from the Controller, relay those commands to the Model and, in response, obtain data from the Model. The Focus Logic applies rules to the data, determines relevancy rankings for the given property, and sends the processed data to the Controller which, in turn, may update the user interface with the processed data.

Abstract: Disclosed are methods and systems to automatically generate a model for pro-active rather than reactive enterprise systems management. In one embodiment, a Markov Chain model is constructed from a Configuration Management Database (CMDB), Service Impact models, event logs and system logs. The model can then be maintained and automatically updated or regenerated based on changing conditions and attributes of configuration items (CIs) being modeled. As part of model generations probabilities associated with potential state transitions of CIs can be calculated. The model can then be used to predict anticipated availability of a corporate enterprise or specific portions of a corporate information technology (IT) environment. In another embodiment, a model can be used to perform what-if scenarios to assist in planning or deferring change requests for the corporate IT environment.

Abstract: Disclosed are embodiments of systems and methods to derive a semantic network from a CMDB relationship graph which can then be queried in a natural way from a linguistic standpoint (i.e., using natural language queries). Because disclosed embodiments combine natural language queries with an inferencing engine the disclosed systems and methods automatically “connect the dots” between disparate pieces of information and can allow for a richer user experience. In general, CMDB graph relationships can be converted into semantic networks. Once a semantic network is created, queries can be phrased to leverage the inferential relationships between objects in the semantic network.

Abstract: A method and system to convert an existing web service from a first web services implantation type to a second web services implementation type. Example implementation types include SOAP and Representational State Transfer (REST). This conversion is achieved by recognizing and classifying available information from each of the distinct implementation types. After proper recognition and classification as disclosed herein, a deterministic process may be utilized to assist in converting or translating the exposed interface; thereby assisting in developing an interface, based on a different interface type than the one already exposed, may be provided.

Abstract: Disclosed are embodiments of a method and system to convert an existing web services request from a first web services implementation type to a second web services implementation type. Example implementation types include SOAP-based and Representational State Transfer (RESTful). Conversion may be achieved through use of a generic web services adaptor. The generic web services adaptor can provide a plurality of interface types and convert requests to a request type supported by an existing web service provider endpoint. In some embodiments, requests not requiring a conversion may be forwarded directly to an existing web service provider endpoint.

Abstract: This disclosure relates generally to the field of federated configuration management databases (CMDBs). To claim compliance with the CMDBf Standard (“the Standard”), a CMDB implementation must provide working and interoperable implementations of the interfaces defined in the Standard. To make a working implementation, certain non-obvious features are required that are not addressed by the Standard. Among these requirements are: registering management data repositories (MDRs) so that they can be federated; managing/maintaining the list of federated MDRs; querying an MDR for its Data Model; using such MDR Data Models to define mappings of one or more attributes from the MDR data model to one or more attributes of one or more of the CMDB's data models; identifying attributes and defining rules to be used when reconciliation is performed; and managing as well as storing data representative of those mappings. This disclosure addresses these and other deficiencies.