Veracode, Inc.

Ca, Inc.

Robert Anthony Layzell

Christien Rioux

Todd David Anderson

Simon Cockayne

Ganesh Prasad Agrawal

Rahul Sharma

To facilitate runtime monitoring and analysis of an application without modifying the actual application code, an agent monitors and analyzes an application through detection and evaluation of invocations of an API of a runtime engine provided for execution of the application. The agent registers to receive events which are generated upon invocation of target functions of the runtime engine API based on its load. Once loaded, the agent initially determines the language and language version number of the runtime engine. The agent determines associations of events for which to monitor and corresponding analysis code to execute upon detection of the invocations based on the language and version number information. When the agent detects an event during execution of the application based on invocations of the runtime engine API, the agent can monitor and analyze execution of the application based on execution of analysis code corresponding to the detected event.

Runtime application monitoring without modifying application program code

To support adding functionality to applications at a layer of abstraction above language-specific implementations of AOP, a language for implementing AOP facilitates runtime monitoring and analysis of an application independent of the language of the application. Aspects can be created for applications written in any supported language. Program code underlying implementations of aspects can be executed based on detecting triggering events during execution of the application. Routines written with the AOP language comprise event-based aspect code triggers that indicate an event which may occur during execution of the application and the associated aspect code to be executed. An agent deployed to a runtime engine to monitor the application detects events and evaluates contextual information about the detected events against the aspect triggers to determine if aspect code should be executed to perform further monitoring and analysis of the executing application.

Language-independent application monitoring through aspect-oriented programming

Representations of hierarchical structures identified by source and target file storage directories are displayed on a display device. Inconsistencies are identified between the hierarchical structures identified by the source and target file storage directories. Graphical interconnections are displayed that extend at least partially between locations of at least some of the identified inconsistencies. Refactoring action indicia are displayed that are user selectable and are associated with defined actions performed by a file directory controller to modify the hierarchical structure identified by the target file storage directory to resolve at least some of the inconsistencies identified between the hierarchical structures identified by the source and target file storage directories. The source and target file storage directories are merged, including by performing the defined actions associated with user selected ones of the refactoring action indicia to generate a refactored target file storage directory that resolves the inconsistencies.

Merging file storage directory structures through user interface visualization of refactoring decisions

Designing an Application Programming Interface (API) may include parsing a first API definition for an input element, and outputting a user interface (UI) for display to a user. The UI may include a UI control set corresponding to the input element. The UI control set may include a text control for receiving a name for the input element in a second API definition, and a type control for receiving a type for the input element in the second API definition. Designing the API may also include receiving the name and type via the text control and the type control, respectively, and generating the second API definition. The generating may include positioning the received name within a command syntax of the second API definition according to the received type.

Growing community of inventors

Novato, CA, United States of America

Robert Anthony Layzell