Abstract: The present invention is a process for intercepting a .NET™ method at runtime in order to enable modifying the method in order to capture data about the method, trace the method, modify the method's behavior, enforce constraints, modify the method's parameters and/or return, throw (halt method execution and let the user know that an error has occurred) user-defined exceptions, and in any other manner to affect the runtime behavior of the application without having to modify and re-deploy the application.

Abstract: A telemetry warehouse provides a consolidated system log in the form of a data warehouse which contains data collected from traditional sources such as system management tools, performance monitoring tools, and various system logs while allowing analysis across the entire range of management data.

Abstract: An embodiment of the present invention provides a method to establish and maintain response time goals for selected business logic contained in components, which results in chosen high priority methods that respond consistently under load, enable smoother server side resource utilization, and increased scalability. The analyzing and delaying of certain processes in order to expedite processing of more important business processes helps establish optimization of multiple business processes.

Abstract: A method in a computer system executing a repository program for dynamically linking two objects in two different models within the repository. The method includes the steps of receiving object identifiers of each of the two objects and an association name from a computer program using the method. The association name is then used to extract a namespace object from the repository program, wherein the namespace object is a part of the repository program for containing association names. Next, a determination is made as to whether or not an association already exists between either one of the two objects and the namespace object. If it is determined that no association exists, then the association name of a first of the two objects and the namespace are changed to an object identifier of a second of the two objects. Finally, the association name of the second of the two objects and the namespace are changed to an object identifier of the first of the two objects.

Abstract: A method is provided in a computer system, which employs a multiplicity of diverse software tools, for monitoring and capturing a pattern of all file usage of each of the software tools. The usage pattern for each of the software tools is migrated into the computer system. The method includes invoking a first process for interfacing with a first one of the software tools and the computer system. Next, the first one of the software tools is invoked through the first process inside the computer system. The first process and the first one of the software tools are then registered with a control module in the computer system. A second process is informed through the control module that the first one of the software tools is being operated upon and to start recording information about the tool. After this, the second process captures information about all files opened and closed by the first one of the software tools during its operation.

Abstract: A method and system for facilitating use of a tool in heterogeneous environments and application categories in a software development framework having a storage device. First, a context object is created for storing all intermediate information generated while the tool is being used. Next, the specific environment in which the tool is going to be used is identified information about the environment is stored in the context object. The specific tasks the tool typically performs are identified and searched for any previously accomplished tasks in the framework. The results of the search are stored in the context object. Information needed for the tool to operate is retrieved from the repository and the information is supplied as input files to the tool. The tool is run with the input files and the output derived is stored as a result of running the tool. The context object is updated by analyzing the output derived from the tool.

Abstract: A system and method in a computer system for integrating software development tools and applications into the computer system in order to build, deploy and maintain enterprise business process applications in a heterogeneous development framework. Integration of the applications and software development tools are achieved through integration of the key elements of the computer system which are business models, domain models and components. In the process of integration the origin of a first newly developed/modified/existing business model is traced to a first newly developed/modified/existing domain model and these models are linked together. Next, the constituent components of a second newly developed/modified/existing domain model are traced to a newly developed/modified/existing set of components created and linked together.

Abstract: The method and system of the present invention solves the problems of the prior art by creating several components to detect and correct an out of date component. A component is considered out of date if one of the constituent files is newer than the components. At that point a build of the component is in order. A component dependent on another is considered out of date if the public interfaces to the component change. The interfaces of the dependent component do not necessarily have to be used by the component in question to affect the build situation. A component is considered up to date if all constituent files have a time stamp earlier than the component and no dependent components have changed their interfaces. Each of the components involved will act upon one of the situations to determine if a build should be done.

Abstract: A programmed computer system transforms a distinctive representation of a business model into a generic representation format, such as the Unified Modeling Language ("UML") object model. The system also transforms legacy business processes, including legacy applications into UML format. The UML format of the business model and legacy components are stored in a central repository. The system also allows the reverse engineering and reverse transformation of UML models into a distinctive representation of business models and application components. The transformation of business model information into a UML model is achieved by identifying the differences between these models and creating a bidirectional mapping of the differences. The system also allows for selective movement of objects and models between business process models and UML. In other words, a user may select individual objects to be moved between models.

Abstract: A programmed computer system includes a set of development tools, each having a format used to store data and code files. The output data from a developmental tool is transformed into a generic format data which is saved in a repository. The repository also contains all output data, application components, and information as to the relationship between the entities and objects stored in the repository. Each tool employed during the development process puts information into the repository and takes information out of the repository. In this way, the system integrates the tools used in different parts of the development process by passing necessary information from one tool to another. Different tools are employed through each of the development stages, legacy integration, enterprise modeling, domain modeling, writing and editing of business logic, generating skeleton code, component building and wrapping and application deployment.

Abstract: A method in a repository coupled to a computer system that generates OLE automation and Interface Definition Language ("IDL") interfaces from metadata (i.e., information about data). Visual Basic programming language is used to develop a tool that generates the automation binding from the metadata in the repository. The method extends C++ programming language binding across networks, independent of the Object Request Broker (ORB) being used. A schema is provided that maps the types and features of a repository to OLE automation and member functions for Windows. The method also integrates the Application Programming Interface (API) of a repository with Windows scripting programming languages through Object Linking and Embedding (OLE).