International Business Machines Corporation

Vadim Berestetsky

Cary Lee Bates

John Matthew Santosuosso

Allen V Chan

Suman Kumar Kalia

Stephen Rea

Peter A Lambros

Paul Reuben Day

Li Ding

Xuan Zhang Chen

Sean Eric Babineau

Steven Gene Halverson

Phil S Coulthard

Paul W Buenger

Dorian Birsan

David Kenneth McKnight

Gregory D Adams

Kushal Sayeed Munir

John Steinbacher

Aditya Jain

Hsing Gen Alexander Wu

Sami El Cheikh

Akshay Nair

Farhan Arshad

Guest-to-host virtual networking can include linking a virtual entity proxy to a network adapter of a host machine through a virtual bridge. In response to a request that starts a guest running on the host machine, the guest can be configured to point to the virtual entity proxy and to communicatively couple to a network through the virtual entity proxy linked to the network adapter of the host machine. The virtual entity proxy can be bound to the network, such that the virtual entity proxy intermediates communications between the guest and one or more other guests running on one or more different host machines that are also communicatively coupled to the network.

Guest-to-host virtual networking

A computer-implemented method, system, and computer program product for cross-domain mapping between a business process modeler domain and an implementation domain are provided. The method includes accessing a business concept registry on a data storage device including business concepts with mapping for the business process modeler domain and the implementation domain. The method also includes creating a model with one or more of the business concepts interconnected to represent a business process in the business process modeler domain, and exporting the model from the business process modeler domain to the implementation domain according to the business concept mapping of the business concept registry.

Conceptual representation of business processes for cross-domain mapping

An XML schema defining elements representing different point of variability (POV) types for points of variability of a pattern is provided. The elements belong to an XML schema POV data-type substitution group that allows the POV types to be substituted for one another. A pattern author is allowed to add new or custom POV data types to the substitution group, thereby allowing the pattern author to extend the pattern meta model to include new POV data types. Once the desired POV data types are defined, the pattern author is allowed to generate an instance of the pattern that applies programmatic operations of the new or custom POV data types created and substituted by the end user to each respective system object.

Extensible meta model for capturing solution patterns

A method for capturing patterns and associated points of variability includes providing an XML schema defining elements representing different point of variability (POV) types for a pattern. The elements belong to an XML schema 'substitution group' to enable the POV types to be substituted for one another. In selected embodiments, the method enables a pattern author to add new or custom POV types to the 'substitution group,' thereby allowing the pattern author to extend the pattern meta model to include new POV types. Once the desired POV types are defined, the method enables the pattern author to generate an instance of the XML schema, defining the points of variability for a specific pattern, using the elements defined in the XML schema &#x201c;substitution group.&#x201d; A corresponding apparatus and computer program product are also disclosed and claimed herein.

A method to trace a variable or other expression through a computer program is disclosed. A user determines the variable and the conditions upon which activity of the variable will be monitored. As a result of the invention, every time that variable is referenced in a memory operation or other activity by the program and the conditions set forth by the user are satisfied, the state of that variable is saved as a snapshot without interrupting or stopping execution of the program. The snapshots are accumulated in a history table. The history table can be retrieved and the state of the variable in any given snapshot can be restored. Other variables and expressions can be attached to the trigger variable and the states of these other variables at the time of the activity of the trigger variable may also be saved in the snapshot. The method may be incorporated into a program as a tracing device or a program product separate from the logical processing device executing the program.

Storing and restoring snapshots of a computer process

A source container for use in a computer system executing problem determination tools in an integrated environment across a computer network, the source container comprising a list of pathways to a plurality of source files and module objects. A software development may create the source container independently or within the front end of a problem determination tool. The front end of the problem determination tools sends the source container to its engine, and only source files and module objects having a pathway in the source container are analyzed within the engine of the problem determination tool. Furthermore, the results of the analysis of only those source files and module objects having a pathway in the source container are returned to the front end of the problem determination tool for viewing by the software developer. The front ends of the tools of the integrated development environment, the source files, the module objects, the engines of the tools, and different tools may all be located on different servers and/or clients across a computer network.

Constraining source code and objects for analysis tools

An automated way to detect differences in the values of program variables/expressions and the order of execution between one run and another. A collection mode saves the values of expressions/variables at collection points in the program. On a subsequent execution during the detection mode, these saved values of the same expressions/variables are recalled and compared with the current values. Advantageously, the user selects the collection points within the program at which variable information can be gathered and compared; and these collection points may include: breakpoints set by a debugging program or by the user; collection points set by the user, and entry and/or exit points and/or points within program structures, such as procedure calls, control blocks, etc. Setup of the collection mode includes the capability to modify the expressions/variables, the tolerance or the acceptable alternatives, and the position and number of collection points.

Collection and detection of differences of values of expressions/variables when debugging a computer process

On demand tracking of applications is provided by a mechanism of the present invention. After a user selects one or more units of execution of interest, a marker is assigned to each target object. Upon invocation of an application, an event is sent to an event handler if at least one target object is executed. The event handler gathers a process identifier and initiates a debugging, tracing or logging of the process on a target system.

Method and apparatus for on demand debugging, tracing, and logging of applications

A method and an apparatus within an integrated development environment to increase the efficiency of tracking changes made to source code. The method and apparatus comprise three modes: a constructor mode, a matchmaker mode, and an announcer mode. The constructor first determines what source code/programming constructs are contained within an executable sequence of instructions, evaluates the size of the constructs, and then parses the tokens of the constructs to construct a construct list. The matchmaker determines the degree of similarity between any two constructs in the construct list. If the degree of similarity is sufficient, that is, if the sequence of code between two constructs is so similar that the sections of code may be considered as related and/or derivatives of one another, the matchmaker then determines if any changes made to one section of code may impact the other construct by weighting the changed tokens between the two sets of code. If the change is deemed significant, then the announcer takes over and determines if the developer who owns the related/derived code will be notified that a change has occurred in the first code.

Tracking and maintaining related and derivative code

Method, apparatus and article of manufactured for debugging code. A user selects a function call (e.g., a method of object-oriented code) and a debugger parses the function call and sets breakpoints on the entry points of all instances of the method (assuming more than one). During execution, when one of the breakpoints is hit, the debugger determines whether the corresponding method is being called from the user-specified location in the code.

Run into function

A computer program debugger is disclosed which stores previous programs which have been debugged and the debug parameters which were considered when debugging. When a new computer program is to be debugged, the new debugger is invoked and it automatically compares the executing program to be debugged with the previous programs. When one or more of the debug parameters are so similar that it can be said that the computer program undergoing debugging matches a previously stored computer program, a user is given options to display the matching programs, the modules, the functions, the lines, and the debug parameters and to exchange debug parameters between the programs which can be used to mod4 the either or any of the programs. The user is further given the option to store the current program undergoing debugging as a new program to be considered in matching the next program to be debugged.

Growing community of inventors

North York, Canada

Vadim Berestetsky