Managing Dynamic Service Dependencies

Hasselmeyer, Peer

doi:10.3990/2.13

Cited by 32 publications

(12 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Other research work has additionally used dependencies to further an understanding of componentbased distributed applications [11,12]. As illustrated in figure 1 a dependency can be regarded as a directed relationship between two components in the sense that one component (the dependent) depends on the service provided by another component (the independent).…”

Section: Introductionmentioning

confidence: 99%

A deliberative model for self-adaptation middleware using architectural dependency

Badr¹,

Taleb-Bendiab²,

Randles³

et al. 2004

Proceedings. 15th International Workshop on Database and Expert Systems Applications, 2004.

View full text Add to dashboard Cite

A crucial prerequisite to externalized adaptation is an understanding of how components are interconnected, or more particularly how and why they depend on one another. Such dependencies can be used to provide an architectural model, which provides a reference point for externalized adaptation. In this paper, it is described how dependencies are used as a basis to systems' self-understanding and subsequent architectural reconfigurations.The approach is based on the combination of: instrumentation services, a dependency meta-model and a system controller. In particular, the latter uses self-healing repair rules (or conflict resolution strategies), based on an Extensible Beliefs, Desires and Intention (EBDI) model, to reflect reconfiguration changes back to a target application under examination.

show abstract

Section: Introductionmentioning

confidence: 99%

A deliberative model for self-adaptation middleware using architectural dependency

Badr¹,

Taleb-Bendiab²,

Randles³

et al. 2004

Proceedings. 15th International Workshop on Database and Expert Systems Applications, 2004.

View full text Add to dashboard Cite

show abstract

“…Tagging requires middleware-level instrumentation to pass the request ID between components, similar to ARM. There are certain other approaches [12], [15], and [18] that use instrumentation of application to get dependencies. They instrument the application code such that some probes or hooks are available to management application to get the data out of managed object and to exert control over the managed object.…”

Section: Related Workmentioning

confidence: 99%

Discovering Dynamic Dependencies in Enterprise Environments for Problem Determination

Gupta

Neogi

Agarwal

et al. 2003

Self-Managing Distributed Systems

View full text Add to dashboard Cite

Abstract. In order to reduce mean time to recovery (MTTR) in heterogeneous enterprise environments it should be possible to easily and quickly determine the root cause of a problem detected at a higher level, e.g. through response time violation of a transaction category, and resolve it. Many problem determination applications use a component dependency graph to pinpoint the root cause. However, such graphs are often manually constructed. This paper introduces a simple nonintrusive technique based on mining of existing runtime monitored data, to construct a dynamic dependency graph between the components of an enterprise environment. The graph is traversed to identify nodes that are the cause of response time related problems. IntroductionTypically dependency models of system hardware and software are analyzed for problem determination and impact analysis in complex enterprise environments. Prior work talks about explicit middleware instrumentation [5], or internal instrumentation of the components (via ARM [2]) for obtaining system dependencies. These methods are time consuming and are difficult to apply in legacy environments. The main contribution of this paper is in showing how existing performance monitoring infrastructure available in middleware, such as web application servers and database servers, can be used in discovering dependencies between the various components of a system. Management clients can poll the middleware for performance metrics, such as total number of requests to a component, average response time of a component, etc. This paper proposes a data-mining algorithm that uses this performance data for obtaining "probabilistic" dependencies between components. An online algorithm for discovering and updating these dependencies between components is provided. Because of the probabilistic nature of these dependencies, "false" dependencies may arise and therefore we show how a problem determination application can use the dependencies effectively. Dependencies can be of various types [17], but this paper focuses on finding runtime software/service dependencies among the following components: URLs, servlets, EJBs, and SQLs in a web application.

show abstract

“…Dynamic dependencies (considered further by Hasselmeyer in [5]) can be represented as the arcs or edges in a directed graph (digraph) in which components (and their services) represent the nodes. Conceptually, a dependency is a directed relationship between a set of components, as shown in Figure 1, that can be represented using the ideas of Hasselmeyer in [5] who defines the relationship based on two roles: the dependent component (a client) and the free or independent component(s) (service provider(s)).…”

Section: Dynamic Dependenciesmentioning

confidence: 99%

“…Conceptually, a dependency is a directed relationship between a set of components, as shown in Figure 1, that can be represented using the ideas of Hasselmeyer in [5] who defines the relationship based on two roles: the dependent component (a client) and the free or independent component(s) (service provider(s)).…”

Section: Dynamic Dependenciesmentioning

confidence: 99%

An instrumentation and control-based approach for distributed application management and adaptation

Reilly

Taleb-Bendiab

Laws

et al. 2002

Proceedings of the First Workshop on Self-Healing Systems

View full text Add to dashboard Cite

Distributed applications are notoriously difficult to develop and manage due to their inherent dynamics and heterogeneity of component technologies and network protocols. Middleware technologies dramatically simplify the development of distributed applications, but they still prove difficult to manage at runtime. This paper considers the "on-going" development of a framework that provides instrumentation and control services, which extend core middleware services, to realize the runtime management and adaptation of distributed applications. The instrumentation and control services are used in conjunction with dependency management utilities to measure performance, monitor behaviour and resolve the runtime inconsistencies and conflicts that may occur in distributed applications.

show abstract

Managing Dynamic Service Dependencies

Cited by 32 publications

References 4 publications

A deliberative model for self-adaptation middleware using architectural dependency

A deliberative model for self-adaptation middleware using architectural dependency

Discovering Dynamic Dependencies in Enterprise Environments for Problem Determination

An instrumentation and control-based approach for distributed application management and adaptation

Contact Info

Product

Resources

About