Abstract: A resource management infrastructure (200) is proposed, wherein every resource may be represented by multiple (specialized) objects (B1, C1, D1; C2), which instantiate corresponding (specialized) classes (315) modeling different aspects of the resources. In the proposed solution, an edge class (310) is associated with the specialized classes; each resource is associated with a corresponding edge object (A1; A2) instantiating the edge class (which object is identified by a corresponding edge name). More specifically, the classes are organized into a specialization tree (300); the edge classes directly depend on abstract classes, while the specialized classes in turn depend on the edge classes. Each specialized object is then associated with the edge name of the corresponding edge object. In this way, the specialized objects associated with each edge name represent the same corresponding resource. An optimized structure of a relational database (225, 230) implementing the proposed solution is also proposed.

Abstract: A solution for managing errors in software applications is proposed. Typically, the software application is represented (during its analysis and design phases) by means of different models—for example, of the UML type. The same models are also exploited to represent the impact of any errors in the software application. For this purpose, during the analysis and design phase, it gets determined the artifacts of the models that are directly impacted by each error (since it occurred in an object that participates in their implementation); the artifacts correlated thereto either directly or indirectly—are set as indirectly impacted by the error. It is then possible to display a diagram corresponding to the model, with the directly and indirectly impacted artifacts that are highlighted with different colors.

Abstract: Method and system for performance monitoring of distributed applications. A sensor intercepts every request of service for a server that is generated on a client. If the request meets a filtering condition (for example, defined by the address of the server, the web page from which the request is originated and/or the selected link) the measuring of a corresponding transaction on the client is enabled; at the same time, the request is updated by inserting a correlator. The request is then transmitted to the server. If the request includes the correlator, the measuring of a sub-transaction originating from the request is also enabled on the server. The parameters measured on the client and on the server are then associated with the correlator.

Abstract: A method and system for instantiating COM components in custom contexts are proposed. The solution of the invention is based on an auxiliary component, acting as a factory (215). Whenever a client (205) needs to instantiate a new target component in a desired custom context, it calls a dedicated method exposed by the factory, passing the identifier of the target component together with information about the custom context. The factory starts execution of an additional module, operating as an impersonator (225), in a new process (230) conforming to the custom context. The impersonator then instantiates the target component in its own process. The impersonator passes a pointer for the target component to the factory (calling a further method that is exposed by the factory); the factory in turn returns that pointer to the client.

Abstract: Method and a corresponding system for performance monitoring of distributed applications. A sensor intercepts every request of service for a server that is generated on a client. If the request meets a filtering condition (for example, defined by the address of the server, the web page from which the request is originated and/or the selected link) the measuring of a corresponding transaction on the client is enabled; at the same time, the request is updated by inserting a correlator. The request is then transmitted to the server. If the request includes the correlator, the measuring of a sub-transaction originating from the request is also enabled on the server. The parameters measured on the client and on the server are then associated with the correlator.

Abstract: Method and system for performance monitoring of distributed applications. A sensor intercepts every request of service for a server that is generated on a client. If the request meets a filtering condition (for example, defined by the address of the server, the web page from which the request is originated and/or the selected link) the measuring of a corresponding transaction on the client is enabled; at the same time, the request is updated by inserting a correlator. The request is then transmitted to the server. If the request includes the correlator, the measuring of a sub-transaction originating from the request is also enabled on the server. The parameters measured on the client and on the server are then associated with the correlator.

Abstract: A solution for managing errors in software applications is proposed. Typically, the software application is represented (during its analysis and design phases) by means of different models—for example, of the UML type. The same models are also exploited to represent the impact of any errors in the software application. For this purpose, during the analysis and design phase, it gets determined the artifacts of the models that are directly impacted by each error (since it occurred in an object that participates in their implementation); the artifacts correlated thereto either directly or indirectly—are set as indirectly impacted by the error. It is then possible to display a diagram corresponding to the model, with the directly and indirectly impacted artifacts that are highlighted with different colors.

Abstract: A resource management infrastructure (200) is proposed, wherein every resource may be represented by multiple (specialized) objects (B1,C1,D1;C2), which instantiate corresponding (specialized) classes (315) modeling different aspects of the resources. In the proposed solution, an edge class (310) is associated with the specialized classes; each resource is associated with a corresponding edge object (A1; A2) instantiating the edge class (which object is identified by a corresponding edge name). More specifically, the classes are organized into a specialization tree (300); the edge classes directly depend on abstract classes, while the specialized classes in turn depend on the edge classes. Each specialized object is then associated with the edge name of the corresponding edge object. In this way, the specialized objects associated with each edge name represent the same corresponding resource. An optimized structure of a relational database (225,230) implementing the proposed solution is also proposed.

Abstract: A method and system for instantiating COM components in custom contexts are proposed. The solution of the invention is based on an auxiliary component, acting as a factory (215). Whenever a client (205) needs to instantiate a new target component in a desired custom context, it calls a dedicated method exposed by the factory, passing the identifier of the target component together with information about the custom context. The factory starts execution of an additional module, operating as an impersonator (225), in a new process (230) conforming to the custom context. The impersonator then instantiates the target component in its own process. The impersonator passes a pointer for the target component to the factory (calling a further method that is exposed by the factory); the factory in turn returns that pointer to the client.

Abstract: A method and a corresponding system for monitoring performance of distributed applications are proposed. In the method of the invention, a sensor intercepts every request of service for a server that is generated on a client. If the request meets a filtering condition (for example, defined by the address of the server, the web page from which the request is originated and/or the selected link) the measuring of a corresponding transaction on the client is enabled; at the same time, the request is updated by inserting a correlator. The request is then transmitted to the server. If the request includes the correlator, the measuring of a sub-transaction originating from the request is also enabled on the server. The parameters measured on the client and on the server are then associated with the correlator.