Conclusion and future work  

The paper proposed an architecture for automation of management instrumentation of component based applications. Based on the experience that traditional techniques for application monitoring cannot deliver the information needed for service-oriented application management and that current instrumentation techniques require too much effort by far, a new approach was introduced.

This architecture greatly reduces the instrumentation effort for both the application developer and the component developer by automatically placing calls to the measurement correlator into the application. Therefore an extension of the development environment was necessary. A second major drawback of current instrumentation techniques, the cumbersome correlation of measurements, was overcome by utilizing the information about the control flows the application is executing in.

Our current work focuses on extending the solution to component architectures that do not use adapters for the wiring of the components. Especially Enterprise Java Beans [#!ejb20!#] and Corba Component Model [#!omg-orbos-99-07-01!#] will be taken into account. As in these architectures every call is intercepted by the container, an instrumentation of the container provides the information required. Also, the control flow based correlation of measurements will be examined for use in non-component environments. A further focus of our current work is to develop management applications that allow a user-based mapping from component failures to the probability of service outages based on statistical information about past component usage.