Design and evaluation of a wide-area event notification service
ACM Transactions on Computer Systems (TOCS)
A Taxonomy and Catalog of Runtime Software-Fault Monitoring Tools
IEEE Transactions on Software Engineering
Distributed Event-Based Systems
Distributed Event-Based Systems
Model driven development for business performance management
IBM Systems Journal - Model-driven software development
Patterns for business object model integration in process-driven and service-oriented architectures
Proceedings of the 2006 conference on Pattern languages of programs
Software Language Engineering: Creating Domain-Specific Languages Using Metamodels
Software Language Engineering: Creating Domain-Specific Languages Using Metamodels
A Model-Driven Approach for Monitoring Business Performance in Web Service Compositions
ICIW '09 Proceedings of the 2009 Fourth International Conference on Internet and Web Applications and Services
Event-based applications and enabling technologies
Proceedings of the Third ACM International Conference on Distributed Event-Based Systems
A DSL toolkit for deferring architectural decisions in DSL-based software design
Information and Software Technology
Hi-index | 0.00 |
An event-based solution that uses events to convey information to a monitoring tool is well suited to implementing a non-intrusive monitoring infrastructure. This enables an SOA system's stakeholders to observe the system aspects of interest to them. However, implementation of SOA today, let alone the monitoring infrastructure, is a complex task due to the heterogeneous environment consisting of multiple technologies, platforms and components. We propose an approach for implementing such an event-based SOA monitoring infrastructure, that introduces a dedicated event view model and an eventing domain-specific language in a model-driven framework. The event view model captures SOA artifacts and links them with the event domain, while the eventing domain-specific language enables a system developer to specify instances of the event view model. With our model-driven approach, most of the runtime monitoring infrastructure is generated. These two ingredients (view model and domain-specific language) focus implementation efforts on the concern of eventing, thereby helping to manage complexity. We apply and evaluate our approach in the context of a case study.