Patent application number | Description | Published |
20080275860 | Seamless design - A system and method for facilitating the interaction between a database application and a relational database is provided and includes accepting at least one object method argument in the form of at least one query variable, where the query variable has a database query encapsulated within. The method further includes modifying the query variable to generate a modified query variable and converting the modified query variable from a first type/class to a second type/class to generate a converted modified query variable. The method also includes passing the converted modified query variable through the call stack and modifying the content of the relational database responsive to the converted modified query variable. | 11-06-2008 |
20100037101 | EXPOSING APPLICATION PERFORMANCE COUNTERS FOR .NET APPLICATIONS THROUGH CODE INSTRUMENTATION - Disclosed is a method for adding performance counters to a .NET application after compilation of the .NET application to Common Intermediate Language code without a requirement for code changes to the original .NET application code or application recompilation from the development side. With regard to a further aspect of a particularly preferred embodiment, the invention may provide a method for adding the performance counters by declarative instrumentation of a .NET application at runtime or compile time, without the need for an application developer to hardcode instrumentation logic into the application. An instrumentation configuration file provides declarative definition for performance counters that are to be added to a particular application, and particularly includes a complete list of performance counters that need to be added and settings for each performance counter. | 02-11-2010 |
20100037211 | AUTOMATIC INCREMENTAL APPLICATION DEPENDENCY DISCOVERY THROUGH CODE INSTRUMENTATION - Disclosed is a method allowing the automatic discovery of application component dependencies by tracing application calls to dependant resources. The call tracing is embedded dynamically in an application at runtime using Common Intermediate Language (“CIL”) code instrumentation at compile time or runtime. Such a method reads an instrumentation configuration file to determine an address extraction code portion that is to be instrumented to an application method code, locates the CIL method body for the application method that is to be instrumented, instruments the application method by inserting the address extraction code portion into the appropriate .NET Application or .NET library at either compile time or at run time, extracts the address of one or more external service providers from the designated .NET library methods responsible for communication during execution of the application method that was instrumented, publishes any newly discovered dependencies to a management system in the form of the discovery event, and causes the management system to build an application dependency map based on the resource address information obtained. | 02-11-2010 |
20100131962 | Software application action monitoring - A system and method for collecting runtime resource information generated by an active software application is provided and includes identifying an occurrence of a function event generated for a software application operating on a predetermined platform, determining a duration of a monitored function called in response to the function event, comparing the duration with a threshold to determine if the duration exceeds the threshold, wherein if the duration is greater than or equal to the threshold then collecting runtime resource information responsive to the monitored function and processing the runtime resource information responsive to the monitored function. | 05-27-2010 |
20120005538 | Dynamic Discovery Algorithm - A system and method for identifying an application exception generated in response to a software application operating on a system is provided, wherein the method includes identifying an occurrence of an application exception, examining the application exception to identify characteristics of the application exception and processing the application exception, prior to the application exception being logged, responsive to the characteristics of the application exception. The processing includes determining whether application exception environment data is to be collected and if the application exception environment data is to be collected, logging the application exception environment data. | 01-05-2012 |
20120030517 | EXPOSING APPLICATION PERFORMANCE COUNTERS FOR .NET APPLICATIONS THROUGH CODE INSTRUMENTATION - Disclosed is a method for adding performance counters to a .NET application after compilation of the .NET application to Common Intermediate Language code without a requirement for code changes to the original .NET application code or application recompilation from the development side. With regard to a further aspect of a particularly preferred embodiment, the invention may provide a method for adding the performance counters by declarative instrumentation of a .NET application at runtime or compile time, without the need for an application developer to hardcode instrumentation logic into the application. An instrumentation configuration file provides declarative definition for performance counters that are to be added to a particular application, and particularly includes a complete list of performance counters that need to be added and settings for each performance counter. | 02-02-2012 |
20130297963 | EXPOSING APPLICATION PERFORMANCE COUNTERS FOR APPLICATIONS THROUGH CODE INSTRUMENTATION - Disclosed is a method for adding performance counters to an application after compilation of the application to Common Intermediate Language code without a requirement for code changes to the original application code or application recompilation from the development side. With regard to a further aspect of a particularly preferred embodiment, the invention may provide a method for adding the performance counters by declarative instrumentation of an application at runtime or compile time, without the need for an application developer to hardcode instrumentation logic into the application. An instrumentation configuration file provides declarative definition for performance counters that are to be added to a particular application, and particularly includes a complete list of performance counters that need to be added and settings for each performance counter. | 11-07-2013 |